Bug#865283: fontmake

[James Godfrey-Kittle]

I was happy to have just now found this thread, while making a table of
fontmake and all its dependencies at https://wiki.debian.org/Fonts#
Font_Tools.

RFPs have now been filed for all of fontmake's dependencies, so now I
suppose the only thing to do is create those packages.

--
James Godfrey-Kittle
jamesg...@gmail.com


On Fri, 23 Jun 2017 08:09:28 +0200 Alex Myczko  wrote:
> Hi
>
> I've got a working version at
> http://sid.ethz.ch/debian/fontmake/
>
> However it also needs python packages like otf2ft, glyphsLib,
> booleanOperations to work.
> Tested with leage of spartan font:
> (fontmake -g the.glyph)
> http://sid.ethz.ch/debian/fonts-leaguespartan/fonts-
leaguespartan-0.1/_source/
>
> --
> Alex Myczko support: +41 44 633 2668
<+41%2044%20633%2026%2068>
> IT Support Group, HPT H 7voice:   +41 44 633 6604
<+41%2044%20633%2066%2004>
> Departement Physik, ETH Zurich
> CH-8093 Zurich, Switzerland
>
>

Bug#868006: RFP: ufo2ft -- A bridge from UFOs to fonttools objects

[James Godfrey-Kittle]

Package: wnpp
Severity: wishlist

* Package name: ufo2ft
  Version : 0.5.3
  Upstream Author : Tal Leming
* URL : https://github.com/googlei18n/ufo2ft
* License : MIT
  Programming Lang: Python
  Description : A bridge from UFOs to fonttools objects

This library converts fonts from UFO, a common font source format, to
fonttools Python objects, which can subsequently saved as OTF or TTF
binaries.

Bug#868005: RFP: glyphsLib -- Library for opening and converting Glyphs font sources

[James Godfrey-Kittle]

Package: wnpp
Severity: wishlist

* Package name: glyphsLib
  Version : 1.7.5
  Upstream Author : Google Internationalization Team
* URL : https://github.com/googlei18n/glyphsLib
* License : Apache-2.0
  Programming Lang: Python
  Description : Library for opening and converting Glyphs font sources

This library can open and manipulate Glyphs font source files
(.glyphs), and provides a tool for exporting these sources to the UFO
format.

Bug#867909: [Pkg-utopia-maintainers] Bug#867909: network-manager: NetworkManager doesn not write search domains to resolv.conf

[Vladimir K]

dchlient.conf is stock from the package.
With dhcp=internal  Network manager ignores option 119 completely and does not 
even list search domains via `nmcli con show`

If I manually launch dhclient on the interface, it successfully writes search 
domains to resolv.conf/

Bug#868004: RFP: cu2qu -- Python library for cubic-to-quadratic bezier curve conversion

[James Godfrey-Kittle]

Package: wnpp
Severity: wishlist

* Package name: cu2qu
  Version : 1.2.0
  Upstream Author : Google Internationalization Team
* URL : https://github.com/googlei18n/cu2qu
* License : Apache-2.0
  Programming Lang: Python
  Description : Python library for cubic-to-quadratic bezier curve
conversion

cu2qu is a library that approximates cubic bezier curves with quadratic
splines. This has general utility, but is especially useful for generating
fonts.

Bug#868003: RFS: ircii/20170704-1 (QA Upload)

[Daniel Echeverry]

Package: sponsorship-requests
Severity: normal

Dear mentors,

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

* Package name: ircii
* Version : 20170704-1
* Upstream Author : Matthew R. Green
* URL : http://ircii.warped.com/
* License : BSD-3-Clause
* Section : net

It builds those binary packages:

ircii - Internet Relay Chat client

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

https://mentors.debian.net/package/ircii
https://anonscm.debian.org/cgit/collab-maint/ircii.git

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

dget -x 
https://mentors.debian.net/debian/pool/main/i/ircii/ircii_20170704-1.dsc

More information about hello can be obtained from http://ircii.warped.com/

Changes since the last upload:

  * QA Upload.
  * New upstream release.
  * debian/control
+ Change debhelper to 10 in B-D.
+ Bump Standards-Version to 4.0.0 (no changes).
  * debian/compat
+ Switch compat level 9 to 10.
  * debian/copyright
+ Extend copyright holders years.
+ Add missing copyright holders.
  * debian/patches
+ Refresh 0008-fix-spelling-error.diff
+ Refresh 0006-fix-some-spelling-errors.patch
+ Refresh 0007-fix_security_problems.diff

 Regards,

-- 
Daniel Echeverry
http://wiki.debian.org/DanielEcheverry
http://rinconinformatico.net
Linux user: #477840
Debian user

Bug#862125: patch

[Rene Engelhard]

Hi,

On Mon, May 15, 2017 at 10:25:38PM +0200, Rene Engelhard wrote:
> the following trivial patch fixes this:
[...]

Of course you also need (just noticed now, my bad):

diff -Nru libfilezilla-0.9.0/debian/control libfilezilla-0.9.0/debian/control
--- libfilezilla-0.9.0/debian/control   2017-01-17 15:58:51.0 +
+++ libfilezilla-0.9.0/debian/control   2017-07-11 02:33:52.0 +
@@ -1,7 +1,7 @@
 Source: libfilezilla
 Priority: optional
 Maintainer: Adrien Cunin 
-Build-Depends: debhelper (>= 9), dh-autoreconf, libcppunit-dev
+Build-Depends: debhelper (>= 9), dh-autoreconf, libcppunit-dev, pkg-config
 Standards-Version: 3.9.8
 Section: libs
 Homepage: https://lib.filezilla-project.org/

Regards,
 
Rene

Bug#868002: udev: README.Debian interface naming improvements

[Christoph Anton Mitterer]

Package: udev
Version: 233-10
Severity: wishlist


Hi.

Some possible improvements:


1)
README.Debian, mentions:
/lib/systemd/network/01-mac-for-usb.link
however this seems to no longer exist.


2)
Also it mentions "on VMs remove the file 
/etc/udev/rules.d/80-net-setup-link.rules instead".

Is this still up to date? I've checked a number of legacy installations (i.e. 
such that had
/etc/udev/rules.d/70-persistent-net.rules), with different KVM and VMware and 
non of them had
such file generated.


3) As for the "new" stable interface naming.
While I've never observed any real issues with the old way of doing it, I see 
the points why
this was done and don't really care on the name of the my interfaces.

There is however at least one scneario, where the new path-based naming makes 
troubles:

If I take my large computing and storage clusters at the university, it doesn't 
really happen
that often that a network card breaks, is replaced (at the same location) and 
then things
work out of the box, without having to change the MAC in some udev rule.
Actually the bigger server vendors seem to send you replacements with the same 
MACs than one
had before.

What I do however have is many bunches of nodes from different vendors or 
different generations
in which the position is different, and thus I get different names.
I do however want to have the primary network card have the same name accross 
the whole cluster
(whether it's eth0 or foobar), which brings one back to the MAC based way of 
naming, I guess,
especially since these servers all typically have n NICs ... e.g. 2 "good" 10 
GbEs and 4 on-board
1GbEs.

Now README.Debian already gives example how to do that with an udev rule... 
even as "first" way,
but it gives no example on doing it the systemd-way, which is AFAIU with a 
.link file, isn't it?

So perhaps for the custom naming, tell people how they can convert their old
70-persistent-net.rule to a .link file first (before the udev way) andgive an 
example like:
[Match]
MACAddress=11:22:aa:bb:cc:33

[Link]
Name=eth0

Which, AFAIU, is the intended way of doing it?


Cheers,
Chris.

Bug#868001: RFS: btrfsmaintenance/0.3.1-1 [ITP]

[Nicholas D Steeves]

Package: sponsorship-requests
Severity: wishlist

Package: sponsorship-requests
Severity: normal [important for RC bugs, wishlist for new packages]

Dear mentors,

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

* Package name: btrfsmaintenance
  Version : 0.3.1-1
  Upstream Author : David Sterba 
* URL : https://github.com/kdave/btrfsmaintenance
* License : GPL-2
  Section : admin

It builds this binary package:

  btrfsmaintenance - Automate btrfs maintenance tasks on mountpoints or 
directories

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

  https://mentors.debian.net/package/btrfsmaintenance

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

  dget -x 
https://mentors.debian.net/debian/pool/main/b/btrfsmaintenance/btrfsmaintenance_0.3.1-1.dsc

Additionally, this package's repository can be cloned with this command:

  git clone ssh://git.debian.org/git/collab-maint/btrfsmaintenance.git

Please note that I haven't pushed and upstream branch yet.

Cheers,
Nicholas

Bug#868000: xorg: xserver-xorg-legacy causes Xorg to start as root even when capable of running as a normal user w/ Nvidia hardware

[Jason Cohen]

Package: xorg
Version: 1:7.7+19
Severity: normal

Dear Maintainer,

Per Bug #861683, xserver-xorg-legacy is a "recommend" for xserver-xorg, and as
such, is likely to be installed by default.  Section 2.2.10 of the Debian
Stretch Release Notes indicates that Xorg will now run as a non-root user for
most setups, indicating 3 requirements for this to function correctly.
However, there is no mention of the need to remove xserver-xorg-legacy. The
Releases Notes currently indicate that Xorg will run as a regular user if:

1) logind and libpam-systemd are installed

2) The system supports Kernel Mode Setting

3) GDM3 is used as the display manager (if X is started from the DM)

However, after spending 30 minutes trying to figure out why a newly installed
Debian Stretch system refused to start Xorg as a regular user, I realized it
was *also* necessary to remove xserver-xorg-legacy.  This is not
documented in the Release Notes or at https://wiki.debian.org/Xorg. Rather, the
release notes gives the strong impression that the aforementioned items are
sufficient to ensure Xorg will not run as root.

After further investigation, and a discussion on the debian-users mailing list,
I realized that this only occurs with some hardware.  When using Intel Graphics
with an Ivy Bridge Core i5, Xorg starts as a normal user when if xserver-xorg-
legacy is installed.  However, on two systems running Nvidia hardware (GTX 1070
for one, GTX770 for another), xserver-xorg-legacy causes Xorg to start as a
root user.  Removing this package allows Xorg to start as a normal user with
both nouveau and the proprietary nvidia-driver.

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

Removing xserver-xorg-legacy on two systems with NVIDIA GPUs allowed Xorg to
run as a non-root user.

   * What outcome did you expect instead?

I expected Xorg to start as a non-root user because: 1) the Release Notes make
no mention of the need to remove this package; and 2) the hardware is capable
of running Xorg as a non-root user when used with either the open source
nouveau driver or the proprietary Nvidia driver.

If this assumption is correct, the proper solution would be to ensure Xorg is
run as a non-root user when it is possible to do so.  However, until that is
the case, an interim solution would be to amend the Release Notes to notify
users that certain hardware setups may require the xserver-xorg-legacy package
to be removed in order to allow Xorg to run as a non-root user.



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

Diversions concerning libGL are in place

diversion of /usr/lib/arm-linux-gnueabihf/libGL.so.1.2.0 to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGL.so.1.2.0 by glx-diversions
diversion of /usr/lib/libGL.so.1 to /usr/lib/mesa-diverted/libGL.so.1 by 
glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGLESv2.so.2.0.0 to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGLESv2.so.2.0.0 by glx-diversions
diversion of /usr/lib/libGLESv2.so.2 to /usr/lib/mesa-diverted/libGLESv2.so.2 
by glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGL.so to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGL.so by glx-diversions
diversion of /usr/lib/x86_64-linux-gnu/libGLESv1_CM.so.1.1.0 to 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGLESv1_CM.so.1.1.0 by glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGLESv1_CM.so to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGLESv1_CM.so by glx-diversions
diversion of /usr/lib/i386-linux-gnu/libGLESv2.so.2 to 
/usr/lib/mesa-diverted/i386-linux-gnu/libGLESv2.so.2 by glx-diversions
diversion of /usr/lib/x86_64-linux-gnu/libGLESv2.so.2 to 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGLESv2.so.2 by glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGL.so.1.2 to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGL.so.1.2 by glx-diversions
diversion of /usr/lib/libGLESv1_CM.so.1.1.0 to 
/usr/lib/mesa-diverted/libGLESv1_CM.so.1.1.0 by glx-diversions
diversion of /usr/lib/i386-linux-gnu/libGLESv1_CM.so.1 to 
/usr/lib/mesa-diverted/i386-linux-gnu/libGLESv1_CM.so.1 by glx-diversions
diversion of /usr/lib/x86_64-linux-gnu/libGLESv1_CM.so to 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGLESv1_CM.so by glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGLESv1_CM.so.1.1.0 to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGLESv1_CM.so.1.1.0 by 
glx-diversions
diversion of /usr/lib/libGL.so.1.2.0 to /usr/lib/mesa-diverted/libGL.so.1.2.0 
by glx-diversions
diversion of /usr/lib/libGLESv2.so to /usr/lib/mesa-diverted/libGLESv2.so by 
glx-diversions
diversion of /usr/lib/libGL.so.1.2 to /usr/lib/mesa-diverted/libGL.so.1.2 by 
glx-diversions
diversion of /usr/lib/i386-linux-gnu/libGLESv1_CM.so.1.1.0 to 
/usr/lib/mesa-diverted/i386-linux-gnu/libGLESv1_CM.so.1.1.0 by glx-diversions
diversion of /usr/lib/x86_64-linux-gnu/libGL.so.1.2.0 to 

Bug#843448: linux-image-4.8.0-1-armmp-lpae: fails to boot on Odroid-Xu4 with rootfs on USB

[Vagrant Cascadian]

On 2017-07-08, Steinar H. Gunderson wrote:
> On Sat, Jul 08, 2017 at 07:50:03AM +0200, Jochen Sprickerhof wrote:
>> For v4.9 the only patch needed is:
>> 
>> https://bugs.debian.org/cgi-bin/bugreport.cgi?att=1;bug=843448;filename=0001-usb-dwc3-core-setup-phy-before-trying-to-read-from-i.patch;msg=97
>
> Don't you also want this?
>
> https://bugs.debian.org/cgi-bin/bugreport.cgi?att=1;bug=843448;filename=2166ffd004e04a61887eb2a39f8639dc12140c58-updated.diff;msg=75

I've built patched linux 4.9 packages using the above two patches, and
am running them on several odroid-xu4 boards used in the reproducible
builds builders, running rootfs and a build partition on USB. So that
should test USB reasonably well... I'll report if there are any major
stability issues.

I'll also try to switch one of them over to a patched 4.11 or 4.12
soonish... to make sure there aren't further regressions there.


Thanks everyone for working on this!


live well,
  vagrant


signature.asc
Description: PGP signature

Bug#867895: e2fsprogs: man ext4: it seems you document "commit" option for ext4 wrong

[Theodore Ts'o]

On Mon, Jul 10, 2017 at 02:36:22PM +0300, Askar Safin wrote:
> 
> Hi. Currently "commit" for ext3 documented so:
> 
> .BI commit= nrsec
> Sync all data and metadata every
> .I nrsec
> seconds.  The default value is 5 seconds.  Zero means default.

This is actually wrong for ext3.  It happens to be true for
data=ordered (which is the default), but if you use data=writeback, it
won't sync all data.

So what this should be reworded to say is "Initiate a jbd2 journal
commit every nrsec seconds".  After a journal commit, file system
metadata operations issued before the commit will be persisted after a
crash.  In order to guarantee that data should be persisted after a
crash, the application must use fsync(2)."

> So, it seems from man that ext4 has same "commit" option and its default 
> value is 5 seconds (even if I don't specify "commit" at command line at all). 
> But it seems that this is wrong ( https://lwn.net/Articles/322823/ ). So, 
> please, fix the man.

Well, the *primary* definition of the commit option is that we will
start a jbd2 commit option every N seconds.  This is the same for ext3
and ext4.

So I would say that the description you referenced in the ext4 portion
of the document is corret, and the part of the document that you
referenced in the ext3 section was incorrect.

The ext4 man page was actually copied from
Documentation/filesystems/ext4.txt, and there are certainly some
changes we could make to improve the man page.

Thanks for pointing this out,

- Ted

Bug#867909: [Pkg-utopia-maintainers] Bug#867909: network-manager: NetworkManager doesn not write search domains to resolv.conf

[Michael Biebl]

Am 10.07.2017 um 16:23 schrieb Vladimir Kudrya:
> Package: network-manager
> Version: 1.8.0-5
> Severity: normal
> 
> Dear Maintainer, NetworkManager, supposedly after upgrade to 1.8, does not
> write domain information acquired via DHCP into resolv.conf. 'domain' and 
> 'search'
> lines are missing.
> I use dnsmasq on LAN which provides options 15 and 119.
> NetworkManager correctly lists both acquired options in journal and in 
> connection info,
> but silently fails to write them to resolv.conf

Could you attach your /etc/dhcp/dhclient.conf please

What happens if you switch to the internal dhcp implementation.

$ cat /etc/NetworkManager/conf.d/dhcp.conf
[main]
dhcp=internal

$ systemctl restart NetworkManager.service

-- 
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#867541: please build ruby binding of grpc

[Andrew Pollock]

On Mon, Jul 10, 2017 at 10:59:07AM +0200, László Böszörményi (GCS) wrote:
> Andrew, please link me to the grpc-packages link/account if possible.
> It's bad that I can't follow this package from the first hand.
> 

Sorry, can you please clarify what you're asking for here?


signature.asc
Description: Digital signature

Bug#858888: flashplugin-nonfree: Can confirm, 404 when wget tries to grab package

[aska]

Package: flashplugin-nonfree
Version: 1:3.6.1+deb8u1
Followup-For: Bug #85

Dear Maintainer,

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

   * What led up to the situation? 
Tried to install flashplugin-nonfree; got a 404 when the script tried 
to wget the plugin from Adobe's website. 


-- Package-specific info:
Debian version: 8.7
Architecture: amd64
Package version: 1:3.6.1+deb8u1
MD5 checksums:
29c85bc8504422120cf89702986ff8e1  
/var/cache/flashplugin-nonfree/get-upstream-version.pl
md5sum: /usr/lib/flashplugin-nonfree/libflashplayer.so: No such file or 
directory
Alternatives:
update-alternatives: error: no alternatives for flash-mozilla.so
ls: cannot access /usr/lib/mozilla/plugins/flash-mozilla.so: No such 
file or directory
/usr/lib/mozilla/plugins/flash-mozilla.so: cannot open 
`/usr/lib/mozilla/plugins/flash-mozilla.so' (No such file or directory)

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

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

Versions of packages flashplugin-nonfree depends on:
ii  binutils   2.25-5
ii  ca-certificates20141019+deb8u2
ii  debconf [debconf-2.0]  1.5.56
ii  gnupg  1.4.18-7+deb8u3
ii  libatk1.0-02.14.0-1
ii  libcairo2  1.14.0-2.1+deb8u2
ii  libcurl3-gnutls7.38.0-4+deb8u5
ii  libfontconfig1 2.11.0-6.3+deb8u1
ii  libfreetype6   2.5.2-3+deb8u1
ii  libgcc11:4.9.2-10
ii  libglib2.0-0   2.42.1-1+b1
ii  libgtk2.0-02.24.25-3+deb8u1
ii  libnspr4   2:4.12-1+debu8u1
ii  libnss32:3.26-1+debu8u1
ii  libpango1.0-0  1.36.8-3
ii  libstdc++6 4.9.2-10
ii  libx11-6   2:1.6.2-3
ii  libxext6   2:1.3.3-1
ii  libxt6 1:1.1.4-1+b1
ii  wget   1.16-1+deb8u1

flashplugin-nonfree recommends no packages.

Versions of packages flashplugin-nonfree suggests:
ii  fonts-dejavu   2.34-1
pn  hal
ii  iceweasel  45.9.0esr-1~deb8u1
pn  konqueror-nsplugins
pn  ttf-mscorefonts-installer  
pn  ttf-xfree86-nonfree

-- no debconf information

Bug#864676: [Pkg-phototools-devel] Bug#864676: [darktable] Freezes when trying to operate on RAW images

[Antonio Marcos López Alonso]

Have revisited darktable since last upgrades and it seems the issue is gone. 
Anyway, for the record, having several USB devices plugged in (as I often 
have) has no noticeable effect in my case. Whenever the issue happened a 
reboot should do the trick to have darktable working again. And it seemed 
suspending to RAM forth and back was a major source of trouble on this matter.

Antonio

El lunes, 10 de julio de 2017 7:27:13 (WEST) David Bremner escribió:
> Another user reported freezes due to interaction with gphoto and a
> charging USB phone. If you have a phone charging in your computer, can
> you verify that the freezes still happen without any phones or
> non-essential USB devices attached.
> 
> d

Bug#813901: ITP: btrfsmaintenance -- Btrfs maintenance toolbox

[Nicholas D Steeves]

Control: owner -1 !

As it has been almost two months without any objections or any
followup from Ioan, I am claiming this bug.  Expect to see
btrfsmaintenance in Debian very soon :-)

On Mon, Oct 24, 2016 at 07:29:40AM +0200, Marc Haber wrote:
> On Sat, Feb 06, 2016 at 05:41:06PM +0200, Ioan Eugen Stan wrote:
> > I've uploaded the package and took the reccomendations into consideration.
> > 
> > http://mentors.debian.net/package/btrfsmaintenance
> 
> what is the state of this package? I don't see it any more on
> mentors.debian.net, and it is not in the archive, and the bug is still
> open.
> 
> Is a sponsor still needed?

Hi Marc,

I'm planning to push to a git repo in the collab-maint after just a
bit more work.  Are you interested in sponsoring this upload?

Sincerely,
Nicholas


signature.asc
Description: Digital signature

Bug#867998: mnemosyne: AttributeError on PageDown

[Jeffrey Cliff]

package: mnemosyne
X-Debbugs-Cc: jeffrey.cl...@gmail.com
version: 2.4-0.1
severity: minor

Dear Maintainer,

On main mnemosyne screen, typing 'PageDown' key consistently results in:

"An unexpected error has occurred.
Please forward the following info to the developers:

Traceback (innermost last):
  File "/usr/lib/python3/dist-packages/mnemosyne/pyqt_ui/review_wdgt.py",
line
326, in keyPressEvent
self.scroll_down()
  File "/usr/lib/python3/dist-packages/mnemosyne/pyqt_ui/review_wdgt.py",
line
362, in scroll_down
self.review_controller().card.fact_view.a_on_top_of_q:
 AttributeError: 'NoneType' object has no attribute 'fact_view'"

what should happen:
if the pane in question has a vertical scroll bar, it could either go down
or
not go down, but not error out





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

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

Versions of packages mnemosyne depends on:
ii  libjs-sphinxdoc 1.4.9-2
ii  libqt5sql5-sqlite   5.7.1+dfsg-3+b1
ii  python3 3.5.3-1
ii  python3-cherrypy3   3.5.0-2
ii  python3-matplotlib  2.0.0+dfsg1-2
ii  python3-pyqt5   5.7+dfsg-5
ii  python3-pyqt5.qtsql 5.7+dfsg-5
ii  python3-pyqt5.qtwebchannel  5.7+dfsg-5
ii  python3-pyqt5.qtwebengine   5.7+dfsg-5
ii  python3-webob   1:1.6.2-2

mnemosyne recommends no packages.

mnemosyne suggests no packages.

-- no debconf information

Bug#867997: jessie->stretch, all apt clients break with /var/lib/dpkg/status realpath error

[Alan Schwartz]

Package: upgrade-reports
Version: 9
Severity: grave

Followed the Debian 9 release notes to upgrade a jessie i386 (686) machine
to stretch. No apt sources except official debian ones. Following the apt-get
dist-upgrade step, attempts to use apt-get, apt-cache, aptitude
produce the following error:

# apt-get update
Hit:1 http://ftp.us.debian.org/debian stretch-updates InRelease
Ign:2 http://ftp.debian.org/debian stretch InRelease
Get:3 http://security.debian.org stretch/updates InRelease [62.9 kB]
Hit:4 http://ftp.debian.org/debian stretch Release
Fetched 62.9 kB in 1s (38.2 kB/s)
Reading package lists... Error!
E: flAbsPath on /var/lib/dpkg/status failed - realpath (22: Invalid
argument)
E: Could not open file  - open (2: No such file or directory)
E: Problem opening
E: The package lists or status file could not be parsed or opened.


Error persists after reboot of the system.

However, dpkg -l and similar still work. The /var/lib/dpkg structure
appears to be intact:

$ ls -l /var/lib/dpkg
total 6904
drwxr-xr-x 2 root root4096 Jul  7 16:39 alternatives
-rw-r--r-- 1 root root 1379057 Apr 28  2015 available
-rw-r--r-- 1 root root 1361618 Apr 28  2015 available-old
-rw-r--r-- 1 root root   8 Feb 20  2006 cmethopt
-rw-r--r-- 1 root root 953 Jul  7 15:54 diversions
-rw-r--r-- 1 root root1034 Jul  7 15:54 diversions-old
drwxr-xr-x 2 root root  339968 Jul  7 16:03 info
-rw-r- 1 root root   0 Jul  7 16:44 lock
-rw-r- 1 root root   0 Feb 20  2006 methlock
drwxr-xr-x 7 root root4096 Feb  7  2011 methods
drwxr-xr-x 2 root root4096 May 26  2005 parts
-rw-r--r-- 1 root root 460 Jul  7 16:40 statoverride
-rw-r--r-- 1 root root 421 Jul  7 16:40 statoverride-old
-rw-r--r-- 1 root root 1961225 Jul  7 16:44 status
-rw-r--r-- 1 root root 1961225 Jul  7 16:44 status-old
drwxr-xr-x 2 root root4096 Jul  7 16:43 triggers
drwxr-xr-x 2 root root4096 Jul  7 16:44 updates


I am using Debian GNU/Linux 2.2, kernel 2.2.17-pre-patch-13 and libc6
2.1.3-10.

Earlier in the week, I did a similar upgrade on another system with same
hardware and didn't experience a problem.

Bug#867996: haskell-aeson FTBFS: undefined symbol: aesonzm1zi0zi2zi1zmATVva2eon9U8IQdb5aU6Rk_DataziAesonziEncodingziInternal_utcTime1_closure

[Adrian Bunk]

Source: haskell-aeson
Version: 1.0.2.1-2
Severity: serious

https://buildd.debian.org/status/package.php?p=haskell-aeson

...
Preprocessing test suite 'tests' for aeson-1.0.2.1...
[ 1 of 13] Compiling Types( tests/Types.hs, 
dist-ghc/build/tests/tests-tmp/Types.o )
[ 2 of 13] Compiling Options  ( tests/Options.hs, 
dist-ghc/build/tests/tests-tmp/Options.o )
[ 3 of 13] Compiling Functions( tests/Functions.hs, 
dist-ghc/build/tests/tests-tmp/Functions.o )
[ 4 of 13] Compiling Instances( tests/Instances.hs, 
dist-ghc/build/tests/tests-tmp/Instances.o )
[ 5 of 13] Compiling Encoders ( tests/Encoders.hs, 
dist-ghc/build/tests/tests-tmp/Encoders.o )
: can't load .so/.DLL for: 
/<>/dist-ghc/build/libHSaeson-1.0.2.1-ATVva2eon9U8IQdb5aU6Rk-ghc8.0.2.so
 
(/<>/dist-ghc/build/libHSaeson-1.0.2.1-ATVva2eon9U8IQdb5aU6Rk-ghc8.0.2.so:
 undefined symbol: 
aesonzm1zi0zi2zi1zmATVva2eon9U8IQdb5aU6Rk_DataziAesonziEncodingziInternal_utcTime1_closure)
/usr/share/cdbs/1/class/hlibrary.mk:147: recipe for target 'build-ghc-stamp' 
failed
make: *** [build-ghc-stamp] Error 1
dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2

Bug#866712: moonshot-gss-eap FTBFS on arm64: libeap/src/utils/common.h:429:0: error: "__bitwise" redefined [-Werror]

[Sam Hartman]

I'm starting the process of updating to new upstream.
I think that is reasonably likely to fix this.  If not, I'll look into
the issue after the update.
I'm OK if moonshot-gss-eap falls out of testing for a few weeks.

--Sam

Bug#867995: bsdmainutils: cal fails with error when invoked with '-h'

[Felix Crux]

Package: bsdmainutils
Version: 9.0.12+nmu1
Severity: normal

Dear Maintainer,

The `cal` binary that is part of `bsdmainutils` has stopped supporting the '-h'
flag (documented in the man page as "Turns off highlighting of today").

Specifically, when invoked as `cal -h`, a calendar of the current month (without
any highlighting) is not printed. Instead, the "Usage" message describing valid
parameters is shown.

It is perhaps interesting that it *does* work for `ncal` -- only the `cal` form
is affected.

It is also interesting that when attempting to use a genuinely invalid flag
(like, for example, '-a'), `cal` prints the error "invalid option -- 'a'" before
the "Usage" message, but no such error is printed for '-h'.

I can confirm that this option did work in Debian jessie, but I don't know when
the problem was introduced.

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

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

Versions of packages bsdmainutils depends on:
ii  bsdutils 1:2.29.2-1
ii  debianutils  4.8.1.1
ii  libbsd0  0.8.3-1
ii  libc62.24-11+deb9u1
ii  libncurses5  6.0+20161126-1
ii  libtinfo56.0+20161126-1

bsdmainutils recommends no packages.

Versions of packages bsdmainutils suggests:
ii  cpp   4:6.3.0-4
pn  vacation  
ii  wamerican [wordlist]  7.1-1
pn  whois 

-- no debconf information

Bug#867994: libllvm-ocaml-dev: unhandled symlink to directory conversion: /usr/lib/ocaml/llvm

[Andreas Beckmann]

Package: libllvm-ocaml-dev
Version: 1:4.0-37~exp2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

an upgrade test with piuparts revealed that your package installs files
over existing symlinks and possibly overwrites files owned by other
packages. This usually means an old version of the package shipped a
symlink but that was later replaced by a real (and non-empty)
directory. This kind of overwriting another package's files cannot be
detected by dpkg.

This was observed on the following upgrade paths:

  sid -> experimental

For /usr/share/doc/PACKAGE this may not be problematic as long as both
packages are installed, ship byte-for-byte identical files and are
upgraded in lockstep. But once one of the involved packages gets
removed, the other one will lose its documentation files, too,
including the copyright file, which is a violation of Policy 12.5:
https://www.debian.org/doc/debian-policy/ch-docs.html#s-copyrightfile

For other overwritten locations anything interesting may happen.

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

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


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

1m5.1s ERROR: FAIL: silently overwrites files via directory symlinks:
  /usr/lib/ocaml/llvm/libllvm.a (libllvm-4.0-ocaml-dev) != 
/usr/lib/ocaml/llvm-3.8/libllvm.a (libllvm-3.8-ocaml-dev)
/usr/lib/ocaml/llvm -> llvm-3.8
  /usr/lib/ocaml/llvm/libllvm_AArch64.a (libllvm-4.0-ocaml-dev) != 
/usr/lib/ocaml/llvm-3.8/libllvm_AArch64.a (libllvm-3.8-ocaml-dev)
/usr/lib/ocaml/llvm -> llvm-3.8
  /usr/lib/ocaml/llvm/libllvm_AMDGPU.a (libllvm-4.0-ocaml-dev) != 
/usr/lib/ocaml/llvm-3.8/libllvm_AMDGPU.a (libllvm-3.8-ocaml-dev)
/usr/lib/ocaml/llvm -> llvm-3.8
  /usr/lib/ocaml/llvm/libllvm_ARM.a (libllvm-4.0-ocaml-dev) != 
/usr/lib/ocaml/llvm-3.8/libllvm_ARM.a (libllvm-3.8-ocaml-dev)
/usr/lib/ocaml/llvm -> llvm-3.8
  /usr/lib/ocaml/llvm/libllvm_BPF.a (libllvm-4.0-ocaml-dev) != 
/usr/lib/ocaml/llvm-3.8/libllvm_BPF.a (libllvm-3.8-ocaml-dev)
/usr/lib/ocaml/llvm -> llvm-3.8
  /usr/lib/ocaml/llvm/libllvm_Hexagon.a (libllvm-4.0-ocaml-dev) != 
/usr/lib/ocaml/llvm-3.8/libllvm_Hexagon.a (libllvm-3.8-ocaml-dev)
/usr/lib/ocaml/llvm -> llvm-3.8
[...]
  /usr/lib/ocaml/llvm/llvm_vectorize.cma (libllvm-4.0-ocaml-dev) != 
/usr/lib/ocaml/llvm-3.8/llvm_vectorize.cma (libllvm-3.8-ocaml-dev)
/usr/lib/ocaml/llvm -> llvm-3.8
  /usr/lib/ocaml/llvm/llvm_vectorize.cmi (libllvm-4.0-ocaml-dev) != 
/usr/lib/ocaml/llvm-3.8/llvm_vectorize.cmi (libllvm-3.8-ocaml-dev)
/usr/lib/ocaml/llvm -> llvm-3.8
  /usr/lib/ocaml/llvm/llvm_vectorize.cmx (libllvm-4.0-ocaml-dev) != 
/usr/lib/ocaml/llvm-3.8/llvm_vectorize.cmx (libllvm-3.8-ocaml-dev)
/usr/lib/ocaml/llvm -> llvm-3.8
  /usr/lib/ocaml/llvm/llvm_vectorize.cmxa (libllvm-4.0-ocaml-dev) != 
/usr/lib/ocaml/llvm-3.8/llvm_vectorize.cmxa (libllvm-3.8-ocaml-dev)
/usr/lib/ocaml/llvm -> llvm-3.8
  /usr/lib/ocaml/llvm/llvm_vectorize.mli (libllvm-4.0-ocaml-dev) != 
/usr/lib/ocaml/llvm-3.8/llvm_vectorize.mli (?)
/usr/lib/ocaml/llvm -> llvm-3.8


cheers,

Andreas


libllvm-ocaml-dev_1:4.0-37~exp2.log.gz
Description: application/gzip

Bug#867973: jessie-pu: package wordgrinder/0.5.1-1

[Cyril Brulebois]

David Given  (2017-07-10):
> Well, I actually approached backports, and they firmly told me to come
> here instead (and even provided instructions)...
> 
> Okay, so what now? I don't really want a backport anyway; I just want
> the version that's currently in stable pushed to jessie as well. That
> version has been in Debian since late 2015, so it's not precisely new;
> it's not like I'm proposing an unstable version.
> 
> I do *not* want the package removed from jessie. It turns out there's
> still a fair number of people who use it, on jessie, and I want to make
> sure that they're supported.

Then extract targeted patches to fix specific bugs in jessie, and propose
a smaller debdiff/diffstat than the one Adam pointed out.


KiBi.


signature.asc
Description: Digital signature

Bug#867232: debian-installer: Does not ask for network mirror when installing from DLBD image

[Cyril Brulebois]

Control: tag -1 - d-i

Hi,

M. Buecher  (2017-07-05):
> when installing Debian from a DLBD image, then debian-installer does not
> ask if a network mirror should be used, leaving /etc/apt/sources.list only
> populated with the security repository and missing the standard and
> stretch-update repositories.
> 
> I would expect to be asked for a network error, as it is when using a DVD
> image, so that the normal and stretch-update repositories are correctly
> set up in /etc/apt/sources.list.

Please attach installer logs, see:
  https://www.debian.org/releases/stretch/armhf/ch05s04.html.en#problem-report


KiBi.


signature.asc
Description: Digital signature

Bug#554794: badblocks -c and -n

[Matt Taggart]

#554794 concerns the time it takes to run badblocks for any particular
value of the -c option (count of blocks to do at once).

At the time (2009) it wasn't clear if larger values of -c improved runtime,
although one user (in 2011) reports 10% improvement.

The current -c (block count) default is 64 blocks.
The current -b (block size) default is 1024 bytes.

AFAICT the last time they were increased was 2004 (#232240, -c from 16 to
64).

A related bug (#764636) when running badblocks on a 14tb device was solved
by switching to -b 4096.

Given the device size increases and RAM/CPU improvements since all these
things occurred, is there any value to increasing the defaults? Does anyone
have any data? If not then what tests would be valuable?

I often run many badblocks instances at once on separate SATA devices (so
no bus contention), what are the optimal settings for that case?

Thanks,

--
Matt Taggart
tagg...@debian.org




pgp0xF0cpiIyb.pgp
Description: PGP signature

Bug#865362:

[Matthias Klumpp]

2017-07-10 23:35 GMT+02:00  :
> Is there any chance in getting this done soon?  I’d like to update fwupd in
> unstable, but I’m blocked by this still.  Upstream has release 0.7.0 since
> this was filed and that can also update experimental from the git snapshot.

It's blocked on other parts of GNOME, mainly gobject-introspection.
You also don't need to file bugs like this seconds after the release,
usually it takes a bit of time to get all things in order to do bigger
transitions again.

I hope we can rule out issues soonish and get gobject-introspection
updated in unstable.
Meanwhile, you can always upload to experimental.

Bug#867993: RFP: pyscada -- SCADA system with web interface

[W. Martin Borgert]

Package: wnpp
Severity: wishlist

* Package name: pyscada
  Version : 0.7.0b17
  Upstream Author : Martin Schröder 
* URL : https://github.com/trombastic/PyScada
* License : GPL3
  Programming Lang: Python
  Description : SCADA system with web interface

>From the README:

> A Open Source SCADA System with HTML5 HMI, build using the
> Django framework. If you like to setup your own SCADA system
> head over to the
> http://pyscada.readthedocs.io/en/dev-0.7.x/installation.html
> section.
>
> Features
>
> HTML5 based HMI
>
> Supports the following industrial Protocols
>  * Modbus TCP/IP
>  * Modbus RTU
>  * Modbus ASCII
>  * Modbus Binary
>  * Phant http://phant.io/
>  * VISA https://pypi.python.org/pypi/PyVISA
>  * 1-Wire (only experimental only RPi3)
>  * BACNet/IP (in development)
>  * Meter-Bus, MBus (in development)
>
> very low Hardware requirements for the Server

Bug#867992: ycmd FTBFS: jedihttp.tests.handlers_test.test_good_gotoassignment_do_not_follow_imports fails

[Adrian Bunk]

Source: ycmd
Version: 0+20161219+git486b809-2.1
Severity: serious
Tags: buster sid

Some recent change in unstable makes ycmd FTBFS:

https://tests.reproducible-builds.org/debian/history/ycmd.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/ycmd.html

...
# Test JediHTTP
HOME=/build/1st/ycmd-0+20161219+git486b809 nosetests -w third_party/JediHTTP -v 
--with-id -d --no-byte-compile --exclude=test_good_gotoassignment_follow_imports
#1 jedihttp.tests.end_to_end_test.test_client_bad_request_with_parameters ... ok
#2 
jedihttp.tests.end_to_end_test.test_client_python3_specific_syntax_completion 
... ok
#3 jedihttp.tests.end_to_end_test.test_client_request_with_parameters ... ok
#4 jedihttp.tests.end_to_end_test.test_client_request_without_parameters ... ok
#5 jedihttp.tests.handlers_test.test_healthy ... ok
#6 jedihttp.tests.handlers_test.test_ready ... ok
#7 jedihttp.tests.handlers_test.test_completion ... ok
#8 jedihttp.tests.handlers_test.test_py3 ... SKIP: Python 3.x only test
#9 jedihttp.tests.handlers_test.test_good_gotodefinition ... ok
#10 jedihttp.tests.handlers_test.test_bad_gotodefinitions_blank_line ... ok
#11 jedihttp.tests.handlers_test.test_bad_gotodefinitions_not_on_valid_position 
... ok
#12 jedihttp.tests.handlers_test.test_good_gotoassignment ... ok
#13 jedihttp.tests.handlers_test.test_good_gotoassignment_do_not_follow_imports 
... FAIL
#14 jedihttp.tests.handlers_test.test_usages ... ok

==
FAIL: 
jedihttp.tests.handlers_test.test_good_gotoassignment_do_not_follow_imports
--
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/nose/case.py", line 197, in runTest
self.test(*self.arg)
  File 
"/build/1st/ycmd-0+20161219+git486b809/third_party/JediHTTP/jedihttp/tests/handlers_test.py",
 line 184, in test_good_gotoassignment_do_not_follow_imports
assert_that( definitions, has_item( expected_definition ) )
AssertionError: 
Expected: a sequence containing <{'name': 'imported_function', 'is_keyword': 
False, 'in_builtin_module': False, 'column': 21, 'module_path': 
'/build/1st/ycmd-0+20161219+git486b809/third_party/JediHTTP/jedihttp/tests/fixtures/follow_imports/importer.py',
 'line': 1, 'docstring': '', 'description': 'from imported import 
imported_function'}>
 but: was <[{u'name': u'imported_function', u'column': 21, u'docstring': 
u'', u'is_keyword': False, u'module_path': 
u'/build/1st/ycmd-0+20161219+git486b809/third_party/JediHTTP/jedihttp/tests/fixtures/follow_imports/importer.py',
 u'in_builtin_module': False, u'line': 1, u'description': u'def 
imported_function'}]>

.describe_mismatch([{u'name': u'imported_function', 
u'column': 21, u'docstring': u'', u'is_keyword': False, u'module_path': 
u'/build/1st/ycmd-0+20161219+git486b809/third_party/JediHTTP/jedihttp/tests/fixtures/follow_imports/importer.py',
 u'in_builtin_module': False, u'line': 1, u'description': u'def 
imported_function'}], )
.append_text('\n')
>>  raise 
>> AssertionError(str(> object at 0x7f30d730e790>))

 >> begin captured logging << 
jedihttp.handlers: DEBUG: received /gotoassignment request
- >> end captured logging << -

--
Ran 14 tests in 2.157s

FAILED (SKIP=1, failures=1)
debian/rules:42: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 1

Bug#865362:

[Mario.Limonciello]

Hi,

Is there any chance in getting this done soon?  I'd like to update fwupd in 
unstable, but I'm blocked by this still.  Upstream has release 0.7.0 since this 
was filed and that can also update experimental from the git snapshot.

Thanks,

Bug#867990: python-pika FTBFS: rm: cannot remove version_history.txt: No such file or directory

[Adrian Bunk]

Source: python-pika
Version: 0.10.0-1
Severity: serious
Tags: buster sid

Some recent change in usntable makes python-pika FTBFS:

https://tests.reproducible-builds.org/debian/history/python-pika.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/python-pika.html

...
   debian/rules override_dh_installchangelogs
make[1]: Entering directory '/build/1st/python-pika-0.10.0'
dh_installchangelogs docs/version_history.rst
make[1]: Leaving directory '/build/1st/python-pika-0.10.0'
   dh_installexamples -O--buildsystem=pybuild
   dh_python2 -O--buildsystem=pybuild
   dh_python3 -O--buildsystem=pybuild
   dh_perl -O--buildsystem=pybuild
   debian/rules override_dh_link
make[1]: Entering directory '/build/1st/python-pika-0.10.0'
rm 
/build/1st/python-pika-0.10.0/debian/python-pika-doc/usr/share/doc/python-pika-doc/html/_sources/version_history.txt
rm: cannot remove 
'/build/1st/python-pika-0.10.0/debian/python-pika-doc/usr/share/doc/python-pika-doc/html/_sources/version_history.txt':
 No such file or directory
debian/rules:25: recipe for target 'override_dh_link' failed
make[1]: *** [override_dh_link] Error 1

Bug#861785: (no subject)

[Denis Prost]

I faced a similar problem on Stretch with libreoffice-calc 5.2.7-1 :

selecting a column with fifty lines filled, then copying in order to
paste it in another calc window, made calc eat all memory and then swap,
making the OS unusable.

Bug#867991: should provide xorg-driver-video

[Michael Biebl]

Package: xserver-xorg-core
Version: 2:1.19.3-2
Severity: normal
Tags: patch

I use the modesetting driver provided by xserver-xorg-core for my Intel
hardware.
Yet xserver-xorg insist on pulling in other video drivers due to
Depends: xserver-xorg-video-all | xorg-driver-video

xserver-xorg-core should have a
Provides: xserver-xorg-video
so unneeded drivers can be uninstalled


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

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

Versions of packages xserver-xorg-core depends on:
ii  keyboard-configuration1.166
ii  libaudit1 1:2.7.7-1+b1
ii  libbsd0   0.8.5-1
ii  libc6 2.24-12
ii  libdbus-1-3   1.10.20-1
ii  libdrm2   2.4.81-2
ii  libegl1-mesa  17.1.4-1
ii  libepoxy0 1.3.1-3
ii  libgbm1   17.1.4-1
ii  libgcrypt20   1.7.8-2
ii  libgl1-mesa-glx [libgl1]  17.1.4-1
ii  libpciaccess0 0.13.4-1+b2
ii  libpixman-1-0 0.34.0-1
ii  libselinux1   2.6-3+b2
ii  libsystemd0   233-10
ii  libudev1  233-10
ii  libxau6   1:1.0.8-1
ii  libxdmcp6 1:1.1.2-3
ii  libxfont2 1:2.0.1-3
ii  libxshmfence1 1.2-1+b2
ii  udev  233-10
ii  xserver-common2:1.19.3-2

Versions of packages xserver-xorg-core recommends:
ii  libgl1-mesa-dri  17.1.4-1
ii  libpam-systemd   233-10

Versions of packages xserver-xorg-core suggests:
ii  xfonts-100dpi1:1.0.4+nmu1
ii  xfonts-75dpi 1:1.0.4+nmu1
ii  xfonts-scalable  1:1.0.3-1.1

-- no debconf information
diff --git a/debian/control b/debian/control
index ccbefd65f..5f8203a5f 100644
--- a/debian/control
+++ b/debian/control
@@ -134,6 +134,7 @@ Provides:
  ${videoabi},
  ${inputabi},
  xserver-xorg-video-modesetting,
+ xorg-driver-video,
 Description: Xorg X server - core server
  The Xorg X server is an X server for several architectures and operating
  systems, which is derived from the XFree86 4.x series of X servers.

Bug#867877: clamav-daemon: please respect manual configuration

[Sebastian Andrzej Siewior]

On 2017-07-10 11:40:20 [+0200], Luca Capello wrote:
> Hi there,
Hi,

> while debugging why the TCP socket was not responding, I discovered that
> everything was fine if clamd was manually started via the CLI.  And then
> I found .
> 
> Please, this is becoming ridiculous:
> 
> - clamd works as expected with *its* own configuration
> - there is no documentation in /usr/share/doc/clamav-daemon about the
>   need to dpkg-reconfigure clamav-daemon to change parameters (and even
>   worse behavior)
> - non-Debian configuration via manual modifications or automatic tools
>   (e.g. ) is not respected

so what is the problem? You want additional documentation or somehow
changed behavior?
You have systemd as init that means that systemd will open the
TCP-socket. Initially we had socket activation but this was disabled -
however it still has the socket configuration via systemd. Using
dpkg-reconfigure will do the right thing and properly create
  /etc/systemd/system/clamav-daemon.socket.d/extend.conf
with the socket information. If you run under systemd then this part of
clamd.conf will be ignored. If you start this via CLI then it won't run
under systemd (same goes for systemV as init) and the arguments are
parsed again.

> The combination of all the above factors suggests me that the severity
> is higher than important, but leaving at it for now.

That systemd service file is part of upstream since a few releases. You
could argue if systemd's socket "feature" should be used or not or third
party tools extended to the extend.conf file in systemd's case. Or the
documentation updated.

> Thx, bye,
> Gismo / Luca

Sebastian

Bug#867989: stretch-pu: package intel-microcode/3.20170707.1~deb9u1

[Henrique de Moraes Holschuh]

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


I'd like to update the intel-microcode package in Debian stretch.

This s-p-u request is related to the os-p-u request at:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863682

This package update is related to:
https://lists.debian.org/debian-devel/2017/06/msg00308.html

This microcode update fixes the SKL150 and KBL095 errata
(hyper-threading bug) on every Skylake and Kaby Lake processor affected
by the issue.

It also fixes other undisclosed errata on Kaby Lake processors.


As usual, I have removed the noise caused by the binary blob changes
from upstream from the debdiff output for clarity.  The abridged debdiff
is attached.

Full diffstat:
 changelog  |7 
 debian/changelog   |   26 
 microcode-20170511.dat |61886 -
 microcode-20170707.dat |81602 +
 releasenote|   18 
 5 files changed, 81641 insertions(+), 61898 deletions(-)

Abridged diffstat:
 changelog|7 +++
 debian/changelog |   26 ++
 releasenote  |   18 ++
 3 files changed, 39 insertions(+), 12 deletions(-)

Other than the microcode blob, the changes are only to documentation and
the changelogs.

Please note that the new upstream "releasenote" file is not going to be
shipped in the binary packages, since it has way too much incorrect
information.  It is present only in the source package.

Thank you!

-- 
  Henrique Holschuh
diff -Nru intel-microcode-3.20170511.1/changelog intel-microcode-3.20170707.1~deb9u1/changelog
--- intel-microcode-3.20170511.1/changelog	2017-05-13 20:09:28.0 -0300
+++ intel-microcode-3.20170707.1~deb9u1/changelog	2017-07-08 19:47:45.0 -0300
@@ -1,3 +1,10 @@
+2017-07-07:
+  * New Microcodes:
+sig 0x00050654, pf_mask 0x97, 2017-06-01, rev 0x222, size 25600
+sig 0x000806e9, pf_mask 0xc0, 2017-04-27, rev 0x0062, size 97280
+sig 0x000806ea, pf_mask 0xc0, 2017-05-23, rev 0x0066, size 95232
+sig 0x000906e9, pf_mask 0x2a, 2017-04-06, rev 0x005e, size 97280
+
 2017-05-11:
   * Updated Microcodes:
 sig 0x000306c3, pf_mask 0x32, 2017-01-27, rev 0x0022, size 22528
diff -Nru intel-microcode-3.20170511.1/debian/changelog intel-microcode-3.20170707.1~deb9u1/debian/changelog
--- intel-microcode-3.20170511.1/debian/changelog	2017-05-15 15:12:25.0 -0300
+++ intel-microcode-3.20170707.1~deb9u1/debian/changelog	2017-07-08 19:47:45.0 -0300
@@ -1,3 +1,29 @@
+intel-microcode (3.20170707.1~deb9u1) stretch; urgency=medium
+
+  * Rebuild for stretch (no changes)
+
+ -- Henrique de Moraes Holschuh   Sat, 08 Jul 2017 19:47:45 -0300
+
+intel-microcode (3.20170707.1) unstable; urgency=high
+
+  * New upstream microcode datafile 20170707
++ New Microcodes:
+  sig 0x00050654, pf_mask 0x97, 2017-06-01, rev 0x222, size 25600
+  sig 0x000806e9, pf_mask 0xc0, 2017-04-27, rev 0x0062, size 97280
+  sig 0x000806ea, pf_mask 0xc0, 2017-05-23, rev 0x0066, size 95232
+  sig 0x000906e9, pf_mask 0x2a, 2017-04-06, rev 0x005e, size 97280
++ This release fixes the nightmare-level errata SKZ7/SKW144/SKL150/
+  SKX150 (Skylake) KBL095/KBW095 (Kaby Lake) for all affected Kaby
+  Lake and Skylake processors: Skylake D0/R0 were fixed since the
+  previous upstream release (20170511).  This new release adds the
+  fixes for Kaby Lake Y0/B0/H0 and Skylake H0 (Skylake-E/X).
++ Fix undisclosed errata in Skylake H0 (0x50654), Kaby Lake Y0
+  (0x806ea), Kaby Lake H0 (0x806e9), Kaby Lake B0 (0x906e9)
+  * source: remove unneeded intel-ucode/ directory
+  * source: remove superseded upstream data file: 20170511
+
+ -- Henrique de Moraes Holschuh   Sat, 08 Jul 2017 19:04:27 -0300
+
 intel-microcode (3.20170511.1) unstable; urgency=medium
 
   * New upstream microcode datafile 20170511
diff -Nru intel-microcode-3.20170511.1/releasenote intel-microcode-3.20170707.1~deb9u1/releasenote
--- intel-microcode-3.20170511.1/releasenote	2017-05-13 20:09:28.0 -0300
+++ intel-microcode-3.20170707.1~deb9u1/releasenote	2017-07-08 19:47:45.0 -0300
@@ -1,17 +1,11 @@
 Intel Processor Microcode Package for Linux
-20170511 Release
+20170707 Release
 
--- Updates --
-BDX-ML B0/M0/R0 (06-4f-01:ef) b1f->b21
-Skylake D0 (06-4e-03:c0) 9e->ba
-Broadwell ULT/ULX E/F-step (06-3d-04:c0) 24->25
-ULT Cx/Dx (06-45-01:72) 1f->20
-Crystalwell Cx (06-46-01:32) 16->17
-Broadwell Halo E/G-step (06-47-01:22) 16->17
-HSX EX E0 (06-3f-04:80) d->f
-Skylake R0 (06-5e-03:36) 9e->ba
-Haswell Cx/Dx (06-3c-03:32) 20->22
-HSX C0 (06-3f-02:6f) 39->3a
+-- New Platforms --
+KBL H0 (06-8e-09:c0) 62
+KBL Y0 (06-8e-0a:c0) 66
+KBL B0 (06-9e-09:2a) 5e
+SKX H0 (06-55-04:97) 222
 
 -- Microcode update instructions --
 This package contains Intel microcode files in two formats:

Bug#867973: jessie-pu: package wordgrinder/0.5.1-1

[David Given]

Well, I actually approached backports, and they firmly told me to come here
instead (and even provided instructions)...

Okay, so what now? I don't really want a backport anyway; I just want the
version that's currently in stable pushed to jessie as well. That version
has been in Debian since late 2015, so it's not precisely new; it's not
like I'm proposing an unstable version.

I do *not* want the package removed from jessie. It turns out there's still
a fair number of people who use it, on jessie, and I want to make sure that
they're supported.

On Mon, 10 Jul 2017 at 22:27 Adam D. Barratt 
wrote:

> On Mon, 2017-07-10 at 22:21 +0200, Alexander Wirt wrote:
> > On Mon, 10 Jul 2017, Adam D. Barratt wrote:
> >
> > > Control: tags -1 + moreinfo
> > >
> > > On Mon, 2017-07-10 at 19:44 +, David Given wrote:
> > > > The version in jessie of my package WordGrinder is painfully old and
> has a
> > > > number of showstopping bugs (document corruption and loss of data).
> The next
> > > > available version in Debian is the version in stable, 0.6-3, which
> has fixed
> > > > these bugs and also contains major functionality improvements.
> > > >
> > > > 0.6-3 builds on jessie out-of-the-box with no repackaging required,
> and so I
> > > > would like to propose the version from stable to be included in the
> next jessie
> > > > point release.
> > >
> > > That sounds like you're looking for jessie-backports, rather than a
> > > stable update.
> > jessie-backports is not for fixing critical bugs like document
> corruption.
> > Those should really get fixed in stable (of course not with an upload of
> the
> > version in testing).
>
> Yes, true, and sorry for being imprecise.
>
> I meant that if the reporter was looking to get newer upstream versions
> available to users of jessie, rather than specific bug fixes, then
> backports was a more applicable approach.
>
> Regards,
>
> Adam
>
> --
┌─── http://cowlark.com ───
│ "There is nothing in the world so dangerous --- and I mean *nothing*
│ --- as a children's story that happens to be true." --- Master Li Kao,
│ _The Bridge of Birds_

Bug#867988: CVE-2017-11111 CVE-2017-10686

[Moritz Muehlenhoff]

Package: nasm
Severity: grave
Tags: security

Please see
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-1
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-10686

Cheers,
Moritz

Bug#863682: superseeding with new version

[Henrique de Moraes Holschuh]

retitle 863682 jessie-pu: package intel-microcode/3.20170707.1~deb8u1
thanks

Intel released the fixes for Kaby Lake as well, so I am updating this
s-p-u bug for the newer version of the intel-microcode package.

Attached are the new diffs and diffstats.  The reasoning for the stable
update is still the same, so I will quote it below.

Thank you!

For the record, this is related to:
https://lists.debian.org/debian-devel/2017/06/msg00308.html

On Mon, 29 May 2017, Henrique de Moraes Holschuh wrote:
> I'd like to update the intel-microcode package in Debian jessie.
> 
> Usually, I'd wait for an extra month before sending this request,
> however I have received word from the OCamn community that this
> microcode update fixes an extremely serious erratum...  and that OCaml
> code compiled with the gcc backend (including the OCaml compiler itself)
> could trivially trigger it.
> 
> The OCaml bug report is here:
> https://caml.inria.fr/mantis/view.php?id=7452
> 
> From the intel-microcode package changelog:
> 
>SKL150 - Short loops using both the AH/BH/CH/DH registers and
>the corresponding wide register *may* result in unpredictable
>system behavior.  Requires both logical processors of the same
>core (i.e. sibling hyperthreads) to be active to trigger, as
>well as a "complex set of micro-architectural conditions"
> 
> This microcode update also fixes other important errata, including one
> that makes it safe to have intel-microcode installed on some recent
> high-end models of the E7v4 and possibly E5v4 Xeons (previous versions
> of intel-microcode are likely to hang these processors during boot,
> refer to bug #862606 for details[1])... but the SKL150 fix takes the
> cake.
> 
> [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=862606

As usual, I have removed the noise caused by the binary blob changes
from upstream from the debdiff output for clarity.  The abridged debdiff
is attached.

Full diffstat:
 changelog  |   20 
 debian/changelog   |   68 
 microcode-20161104.dat |61630 -
 microcode-20170707.dat |81602 +
 releasenote|   35 
 5 files changed, 81725 insertions(+), 61630 deletions(-)

Abridged diffstat:
 changelog|   20 
 debian/changelog |   68 +++
 releasenote  |   35 
 3 files changed, 123 insertions(+)

Other than the microcode blob, the changes are only to documentation and
the changelogs.

Please note that the new upstream "releasenote" file is not going to be
shipped in the binary packages, since it has way too much incorrect
information.  It is present only in the source package.

Thank you!

-- 
  Henrique Holschuh
diff -Nru intel-microcode-3.20161104.1~deb8u1/changelog intel-microcode-3.20170707.1~deb8u1/changelog
--- intel-microcode-3.20161104.1~deb8u1/changelog	2016-12-16 08:53:58.0 -0200
+++ intel-microcode-3.20170707.1~deb8u1/changelog	2017-07-08 20:18:26.0 -0300
@@ -1,3 +1,23 @@
+2017-07-07:
+  * New Microcodes:
+sig 0x00050654, pf_mask 0x97, 2017-06-01, rev 0x222, size 25600
+sig 0x000806e9, pf_mask 0xc0, 2017-04-27, rev 0x0062, size 97280
+sig 0x000806ea, pf_mask 0xc0, 2017-05-23, rev 0x0066, size 95232
+sig 0x000906e9, pf_mask 0x2a, 2017-04-06, rev 0x005e, size 97280
+
+2017-05-11:
+  * Updated Microcodes:
+sig 0x000306c3, pf_mask 0x32, 2017-01-27, rev 0x0022, size 22528
+sig 0x000306d4, pf_mask 0xc0, 2017-01-27, rev 0x0025, size 17408
+sig 0x000306f2, pf_mask 0x6f, 2017-01-30, rev 0x003a, size 32768
+sig 0x000306f4, pf_mask 0x80, 2017-01-30, rev 0x000f, size 16384
+sig 0x00040651, pf_mask 0x72, 2017-01-27, rev 0x0020, size 20480
+sig 0x00040661, pf_mask 0x32, 2017-01-27, rev 0x0017, size 24576
+sig 0x00040671, pf_mask 0x22, 2017-01-27, rev 0x0017, size 11264
+sig 0x000406e3, pf_mask 0xc0, 2017-04-09, rev 0x00ba, size 98304
+sig 0x000406f1, pf_mask 0xef, 2017-03-01, rev 0xb21, size 26624
+sig 0x000506e3, pf_mask 0x36, 2017-04-09, rev 0x00ba, size 98304
+
 2016-11-04:
   * New Microcodes:
 sig 0x00050663, pf_mask 0x10, 2016-10-12, rev 0x70d, size 20480
diff -Nru intel-microcode-3.20161104.1~deb8u1/debian/changelog intel-microcode-3.20170707.1~deb8u1/debian/changelog
--- intel-microcode-3.20161104.1~deb8u1/debian/changelog	2016-12-16 09:42:12.0 -0200
+++ intel-microcode-3.20170707.1~deb8u1/debian/changelog	2017-07-08 20:25:31.0 -0300
@@ -1,3 +1,71 @@
+intel-microcode (3.20170707.1~deb8u1) jessie; urgency=high
+
+  * Upload to jessie (no changes)
+
+ -- Henrique de Moraes Holschuh   Sat, 08 Jul 2017 20:25:31 -0300
+
+intel-microcode (3.20170707.1) unstable; urgency=high
+
+  * New upstream microcode datafile 20170707
++ New Microcodes:
+  sig 0x00050654, pf_mask 0x97, 2017-06-01, rev 0x222, size 25600
+  sig 

Bug#867987: h5py: FTBFS on sparc64 due to unaliged accesses in test suite

[James Clarke]

Source: h5py
Version: 2.7.0-1
Tags: upstream patch
Forwarded: https://github.com/h5py/h5py/pull/904
User: debian-sp...@lists.debian.org
Usertags: sparc64
X-Debbugs-Cc: debian-sp...@lists.debian.org

Hi,
Currently h5py FTBFS on sparc64 (and has done for as long as sparc64 has
been building packages without nocheck), as the test suite crashes with
SIGBUS due to unaligned memory accesses. I have submitted a fix upstream
at the above URL; please include the patch in the Debian package.

Regards,
James

Bug#867986: CVE-2016-10396

[Moritz Muehlenhoff]

Package: racoon
Severity: grave
Tags: security

Please see http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-10396   

Cheers,
Moritz

Bug#867912: fusiondirectory: unusable after upgrade from jessie to stretch

[Mike Gabriel]

Hi Johannes,

On  Mo 10 Jul 2017 16:35:47 CEST, IOhannes m zmoelnig wrote:


Package: fusiondirectory
Version: 1.0.19-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

after upgrading my fusiondirectory installation from jessie (1.0.8.2-5)
to stretch (1.0.19-1) the package has become practically unusable.
(that's after adding workarounds for #854398 and ).


Been there, had that...


e.g. trying to edit anything, i get the following on saving:

LDAP operation failed!

[...]



no warning has been emitted when I upgraded from jessie to stretch.
esp. no NEWS have indicated that anything could possibly go wrong.


Indeed, this would have been a good idea. Sorry for that. The  
packaging was done last minute unfortunately, so such delays got lost  
while being "in a hurry".



there are some upstream notes in /usr/share/doc/fusiondirectory/docs/ about
upgrading, indicating that this will require quite a lot of
schema-changes and similar.
however, the upstream notes are very incremental (e.g. 1.0.8.1 ->
1.0.8.2) and do not make it easy to upgrade from jessie to stretch.


That incremental upgrade path is exactly your way to go. Been there,  
done that. Complained to upstream loudly on that (as it sucks IMHO).



since fusiondirectory is a package to manage core infrastructure (like
user databases and networking devices), extra should be taken to allow
smooth upgrades between releases.


Yes, I agree.


please fix this for the next point release (and please provide some
instructions for the 9.0-users on how to handle their broken
installations)


Will give it a shot when back at work next week.


PS: thanks for packaging fusiondirectory!


;-)

Mike
--

DAS-NETZWERKTEAM
mike gabriel, herweg 7, 24357 fleckeby
mobile: +49 (1520) 1976 148
landline: +49 (4354) 8390 139

GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22  0782 9AF4 6B30 2577 1B31
mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de



pgpXh5NJsVUgi.pgp
Description: Digitale PGP-Signatur

Bug#867982: libfile-stripnondeterminism-perl: [PATCH] Optimize load times of File::StripNondeterminism

[Chris Lamb]

tags 867982 + pending
thanks

Niels Thykier wrote:

> dh_strip-nondeterminism accounts for ~4.5% of the total runtime for a
> (mostly) no-op dh package build

Whoops!

> Attached, I have included a few patches to optimize the start up time

Thanks so much; applied in Git. :)


Best wishes,

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

Bug#867961: osc: Uses deprecated python-gnomekeyring

[Michael Biebl]

Am 10.07.2017 um 19:56 schrieb Michal Čihař:
> Already reported by you as #844158 (and fixed in Git).


Sorry for that. Somehow missed that.
Thanks for your quick reply.

-- 
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#867222: pdf-presenter-console: [regression] movies are expanded full screen, cover the presentation, and never disappear

[Francesco Poli]

Control: forwarded 867222 https://github.com/pdfpc/pdfpc/issues/240


On Tue, 04 Jul 2017 23:20:31 +0200 Francesco Poli (wintermute) wrote:

[...]
> the movie is expanded full screen and covers the actual presentation
> page. The movie may be played, but there seems to be no way to make it
> disappear again.
[...]

Hello,
I see that you forwarded this report upstream as #248, which was closed
as duplicate of #240.
Thanks for doing so!

I am accordingly marking the report as forwarded...


-- 
 http://www.inventati.org/frx/
 There's not a second to spare! To the laboratory!
. Francesco Poli .
 GnuPG key fpr == CA01 1147 9CD2 EFDF FB82  3925 3E1C 27E1 1F69 BFFE


pgpFaWiLjo6Y_.pgp
Description: PGP signature

Bug#867952: system-config-printer-common: Uses deprecated gir1.2-gnomekeyring-1.0

[Andreas Henriksson]

Control: forwarded -1 https://github.com/zdohnal/system-config-printer/pull/67
Control: tags -1 + fixed-upstream

On Mon, Jul 10, 2017 at 06:27:52PM +0200, bi...@debian.org wrote:
> Package: system-config-printer-common
> Version: 1.5.9-2
> Severity: important
> User: pkg-gnome-maintain...@lists.alioth.debian.org
> Usertags: oldlibs libgnome-keyring-removal
> 
> Hi,
> 
> The libgnome-keyring library is deprecated and its usage is strongly
> discouraged [1].
[...]

Fwiw, This has been fixed in upstream git master already and should
(hopefully) be part of next release. (See above forwarded url for
further info.)

Regards,
Andreas Henriksson

Bug#867985: RM: cppunit1.13/experimental -- ROM; obsolete

[Rene Engelhard]

Package: ftp.debian.org
Severity: normal

Hi,

please remove src:cppunit1.13.

Was originally intended as a compatibity measure for gnuradio and ola,
but the release team thinks they should - if the can't be adapted -
disable the testsuite.
See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=862696

Thus please remove it. Sorry for the nagging on IRC for something which
doesn't live even 1 day, but I apparently was more cautious than I should
have been :)

Regards,

Rene

Bug#867984: libclass-load-xs-perl: FTBFS: t/012-without-implementation.t failure

[Niko Tyni]

Package: libclass-load-xs-perl
Version: 0.09-2
Severity: serious
Tags: sid buster
Control: block 866389 with -1

This package fails its test suite on current sid. It looks like it broke
with libtest-without-module-perl_0.20-1.

  #   Failed test 'error when loading Class::Load and no implementation is 
available includes errors from trying to load modules'
  #   at t/012-without-implementation.t line 15.
  #   'Could not find a suitable Class::Load implementation: 
Can't locate Class/Load/XS.pm in @INC (you may need to install the 
Class::Load::XS module) (@INC contains: CODE(0x560520488868) 
/<>/blib/lib /<>/blib/arch /etc/perl 
/usr/local/lib/x86_64-linux-gnu/perl/5.24.1 /usr/local/share/perl/5.24.1 
/usr/lib/x86_64-linux-gnu/perl5/5.24 /usr/share/perl5 
/usr/lib/x86_64-linux-gnu/perl/5.24 /usr/share/perl/5.24 
/usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base .) at 
/usr/share/perl5/Module/Runtime.pm line 317.
  # Can't locate Class/Load/PP.pm in @INC (you may need to install the 
Class::Load::PP module) (@INC contains: CODE(0x560520488868) 
/<>/blib/lib /<>/blib/arch /etc/perl 
/usr/local/lib/x86_64-linux-gnu/perl/5.24.1 /usr/local/share/perl/5.24.1 
/usr/lib/x86_64-linux-gnu/perl5/5.24 /usr/share/perl5 
/usr/lib/x86_64-linux-gnu/perl/5.24 /usr/share/perl/5.24 
/usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base .) at 
/usr/share/perl5/Module/Runtime.pm line 317.
  #  at /usr/share/perl5/Class/Load.pm line 21.
  # Compilation failed in require at t/012-without-implementation.t line 14.
  # '
  # doesn't match '(?^:Class.Load.PP\.pm did not return a true value)'
  # Looks like you failed 1 test of 1.
  [...]
  Test Summary Report
  ---
  t/012-without-implementation.t (Wstat: 256 Tests: 1 Failed: 1)
Failed test:  1
Non-zero exit status: 1
  Files=16, Tests=127,  0 wallclock secs ( 0.03 usr  0.01 sys +  0.41 cusr  
0.02 csys =  0.47 CPU)
  Result: FAIL

-- 
Niko Tyni   nt...@debian.org

Bug#867874: closed by Clint Adams <cl...@debian.org> (Bug#867874: fixed in haskell-hledger-lib 1.1-2)

[Adrian Bunk]

Control: reopen -1

On Mon, Jul 10, 2017 at 12:42:12PM +, Debian Bug Tracking System wrote:
>...
>  haskell-hledger-lib (1.1-2) unstable; urgency=medium
>  .
>* Patch for newer megaparsec.  closes: #867874.
>...
> Source: haskell-hledger-lib
> Version: 1.1-1
> Severity: serious
> 
> The following packages have unmet dependencies:
>  builddeps:haskell-hledger-lib : Depends: libghc-megaparsec-dev (< 5.2) but 
> 5.2.0-2 is to be installed

It seems something went wrong with the build-dependencies part of the fix.

cu
Adrian

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed

Bug#867490: stretch-pu: package perl/5.24.1-3+deb9u1

[Adam D. Barratt]

Control: tags -1 + confirmed

On Thu, 2017-07-06 at 20:52 +0100, Dominic Hargreaves wrote:
> We would like to apply the following fixes to perl in stretch for the
> next point release:
> 
>   * Backport various Getopt-Long fixes from upstream 2.49..2.51.
> (Closes: #855532, #864544)
>   * Backport upstream patch fixing regexp "Malformed UTF-8 character"
> crashes. (Closes: #864782)
>   * Apply upstream base.pm no-dot-in-inc fix (from 5.24.2-RC1)
> (Closes: #867170)

Please go ahead.

Regards,

Adam

Bug#867983: libclass-load-perl: FTBFS: t/012-without-implementation.t failure

[Niko Tyni]

Package: libclass-load-perl
Version: 0.23-1
Severity: serious
Tags: sid buster

This package fails its test suite on current sid. It looks like it broke
with libtest-without-module-perl_0.20-1.

  #   Failed test 'error when loading Class::Load and no implementation is 
available includes errors from trying to load modules'
  #   at t/012-without-implementation.t line 15.
  #   'Could not find a suitable Class::Load implementation: 
Can't locate Class/Load/XS.pm in @INC (you may need to install the 
Class::Load::XS module) (@INC contains: CODE(0x5645284258d0) 
/<>/blib/lib /<>/blib/arch /etc/perl 
/usr/local/lib/x86_64-linux-gnu/perl/5.24.1 /usr/local/share/perl/5.24.1 
/usr/lib/x86_64-linux-gnu/perl5/5.24 /usr/share/perl5 
/usr/lib/x86_64-linux-gnu/perl/5.24 /usr/share/perl/5.24 
/usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base .) at 
/usr/share/perl5/Module/Runtime.pm line 317.
  # Can't locate Class/Load/PP.pm in @INC (you may need to install the 
Class::Load::PP module) (@INC contains: CODE(0x5645284258d0) 
/<>/blib/lib /<>/blib/arch /etc/perl 
/usr/local/lib/x86_64-linux-gnu/perl/5.24.1 /usr/local/share/perl/5.24.1 
/usr/lib/x86_64-linux-gnu/perl5/5.24 /usr/share/perl5 
/usr/lib/x86_64-linux-gnu/perl/5.24 /usr/share/perl/5.24 
/usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base .) at 
/usr/share/perl5/Module/Runtime.pm line 317.
  #  at /<>/blib/lib/Class/Load.pm line 21.
  # Compilation failed in require at t/012-without-implementation.t line 14.
  # '
  # doesn't match '(?^:Class.Load.PP\.pm did not return a true value)'
  # Looks like you failed 1 test of 1.
  
  [...]
  Test Summary Report
  ---
  t/012-without-implementation.t (Wstat: 256 Tests: 1 Failed: 1)
Failed test:  1
Non-zero exit status: 1
  Files=16, Tests=127,  0 wallclock secs ( 0.04 usr  0.00 sys +  0.52 cusr  
0.04 csys =  0.60 CPU)
  Result: FAIL
 
-- 
Niko Tyni   nt...@debian.org

Bug#867982: libfile-stripnondeterminism-perl: [PATCH] Optimize load times of File::StripNondeterminism

[Niels Thykier]

Package: libfile-stripnondeterminism-perl
Version: 0.035-2
Severity: normal
Tags: upstream patch

Hi,

Thanks to a very minimalistic performance test case for dh from Adam
Borowski, I realised that dh_strip-nondeterminism accounts for ~4.5%
of the total runtime for a (mostly) no-op dh package build[1].  This
cost applies even to packages for which dh_strip-nondeterminism does
not normalize any files.

Attached, I have included a few patches to optimize the start up time
a bit (Feel free to squash them into a single commit).
  In my simplified testing, the start up time is reduced to ~0.075s
(down from ~0.170s) in the no-op case.  The impact should be minimal
in the case where dh_strip-nondeterminism actually need to do
anything.

Thanks,
~Niels

[1] dpkg-buildpackage -us -uc -tc -b
>From 5a1ffdd72f55b17b11869b10a85529a0048fec91 Mon Sep 17 00:00:00 2001
From: Niels Thykier 
Date: Mon, 10 Jul 2017 20:19:54 +
Subject: [PATCH 1/3] File::SND: Lazy load most handlers

This reduces the start up time of dh_strip_nondeterminism to ~0.10s
from ~0.17s in a "no-op" case.

Signed-off-by: Niels Thykier 
---
 lib/File/StripNondeterminism.pm | 73 -
 1 file changed, 42 insertions(+), 31 deletions(-)

diff --git a/lib/File/StripNondeterminism.pm b/lib/File/StripNondeterminism.pm
index c29d4df..c153b0e 100644
--- a/lib/File/StripNondeterminism.pm
+++ b/lib/File/StripNondeterminism.pm
@@ -22,16 +22,9 @@ use strict;
 use warnings;
 
 use POSIX qw(tzset);
-use File::StripNondeterminism::handlers::ar;
-use File::StripNondeterminism::handlers::cpio;
-use File::StripNondeterminism::handlers::gettext;
-use File::StripNondeterminism::handlers::gzip;
-use File::StripNondeterminism::handlers::jar;
 use File::StripNondeterminism::handlers::javadoc;
 use File::StripNondeterminism::handlers::pearregistry;
-use File::StripNondeterminism::handlers::png;
 use File::StripNondeterminism::handlers::javaproperties;
-use File::StripNondeterminism::handlers::zip;
 
 our($VERSION, $canonical_time, $clamp_time);
 
@@ -59,29 +52,29 @@ sub get_normalizer_for_file($) {
 
# ar
if (m/\.a$/ && _get_file_type($_) =~ m/ar archive/) {
-   return \::StripNondeterminism::handlers::ar::normalize;
+   return _handler('ar');
}
# cpio
if (m/\.cpio$/ && _get_file_type($_) =~ m/cpio archive/) {
-   return \::StripNondeterminism::handlers::cpio::normalize;
+   return _handler('cpio');
}
# gettext
if (m/\.g?mo$/ && _get_file_type($_) =~ m/GNU message catalog/) {
-   return 
\::StripNondeterminism::handlers::gettext::normalize;
+   return _handler('gettext');
}
# gzip
if (m/\.(gz|dz)$/ && _get_file_type($_) =~ m/gzip compressed data/) {
-   return \::StripNondeterminism::handlers::gzip::normalize;
+   return _handler('gzip');
}
# jar
if (m/\.(jar|war|hpi|apk)$/
&& _get_file_type($_) =~ m/(Java|Zip) archive data/) {
-   return \::StripNondeterminism::handlers::jar::normalize;
+   return _handler('jar');
}
# javadoc
if (m/\.html$/
&& 
File::StripNondeterminism::handlers::javadoc::is_javadoc_file($_)) {
-   return 
\::StripNondeterminism::handlers::javadoc::normalize;
+   return _handler('javadoc');
}
# pear registry
if (
@@ -89,11 +82,11 @@ sub get_normalizer_for_file($) {
&& 
File::StripNondeterminism::handlers::pearregistry::is_registry_file(
$_)
  ) {
-   return 
\::StripNondeterminism::handlers::pearregistry::normalize;
+   return _handler('pearregistry');
}
# PNG
if (m/\.png$/ && _get_file_type($_) =~ m/PNG image data/) {
-   return \::StripNondeterminism::handlers::png::normalize;
+   return _handler('png');
}
# pom.properties, version.properties
if (
@@ -101,32 +94,50 @@ sub get_normalizer_for_file($) {
&& 
File::StripNondeterminism::handlers::javaproperties::is_java_properties_file(
$_)
  ) {
-   return
- 
\::StripNondeterminism::handlers::javaproperties::normalize;
+   return _handler('javaproperties');
}
# zip
if (m/\.(zip|pk3|epub|whl|xpi|htb|zhfst|par)$/
&& _get_file_type($_) =~ m/Zip archive data|EPUB document/) {
-   return \::StripNondeterminism::handlers::zip::normalize;
+   return _handler('zip');
}
return undef;
 }
 
-our %typemap = (
-   ar  => \::StripNondeterminism::handlers::ar::normalize,
-   cpio=> \::StripNondeterminism::handlers::cpio::normalize,
-   gettext => 

Bug#843450: lxc: Corrupt /proc/self/cgroup / Failed to get list of controllers

[Kevin Locke]

On Sat, 2016-11-12 at 10:30 +0100, Evgeni Golov wrote:
> Can you please try systemd 232-3?
> You should not need to pass systemd.legacy_systemd_cgroup_controller anymore 
> as the offending change was reverted.

I am observing the "PAM-CGFS: Failed to get list of controllers" error
message as well, but not "PAM-CGFS: Corrupt /proc/self/cgroup", on a
system running systemd 233-10, libpam-cgfs 2.0.7-1, and kernel 4.12.

Adding systemd.legacy_systemd_cgroup_controller to the kernel command
line does avoid the error messages.

For reference, I have attached the relevant portion of
/proc/1/mountinfo and /proc/self/cgroup as previously requested, both
booting with and without systemd.legacy_systemd_cgroup_controller.

-- 
Cheers,  |  ke...@kevinlocke.name| XMPP: ke...@kevinlocke.name
Kevin|  https://kevinlocke.name  | IRC:   kevinoid on freenode
26 17 0:22 / /sys/fs/cgroup rw shared:9 - tmpfs tmpfs rw,mode=755
27 26 0:23 / /sys/fs/cgroup/unified rw,nosuid,nodev,noexec,relatime shared:10 - 
cgroup2 cgroup rw
28 26 0:24 / /sys/fs/cgroup/systemd rw,nosuid,nodev,noexec,relatime shared:11 - 
cgroup cgroup rw,xattr,name=systemd
30 26 0:26 / /sys/fs/cgroup/freezer rw,nosuid,nodev,noexec,relatime shared:14 - 
cgroup cgroup rw,freezer
31 26 0:27 / /sys/fs/cgroup/blkio rw,nosuid,nodev,noexec,relatime shared:15 - 
cgroup cgroup rw,blkio
32 26 0:28 / /sys/fs/cgroup/cpu,cpuacct rw,nosuid,nodev,noexec,relatime 
shared:16 - cgroup cgroup rw,cpu,cpuacct
33 26 0:29 / /sys/fs/cgroup/cpuset rw,nosuid,nodev,noexec,relatime shared:17 - 
cgroup cgroup rw,cpuset
34 26 0:30 / /sys/fs/cgroup/net_cls,net_prio rw,nosuid,nodev,noexec,relatime 
shared:18 - cgroup cgroup rw,net_cls,net_prio
35 26 0:31 / /sys/fs/cgroup/memory rw,nosuid,nodev,noexec,relatime shared:19 - 
cgroup cgroup rw,memory
36 26 0:32 / /sys/fs/cgroup/devices rw,nosuid,nodev,noexec,relatime shared:20 - 
cgroup cgroup rw,devices
37 26 0:33 / /sys/fs/cgroup/pids rw,nosuid,nodev,noexec,relatime shared:21 - 
cgroup cgroup rw,pids
38 26 0:34 / /sys/fs/cgroup/perf_event rw,nosuid,nodev,noexec,relatime 
shared:22 - cgroup cgroup rw,perf_event
10:perf_event:/
9:pids:/user.slice/user-1000.slice/session-1.scope
8:devices:/user.slice
7:memory:/user.slice
6:net_cls,net_prio:/
5:cpuset:/
4:cpu,cpuacct:/user.slice
3:blkio:/user.slice
2:freezer:/
1:name=systemd:/user.slice/user-1000.slice/session-1.scope
0::/user.slice/user-1000.slice/session-1.scope
26 17 0:22 / /sys/fs/cgroup rw shared:9 - tmpfs tmpfs rw,mode=755
27 26 0:23 / /sys/fs/cgroup/systemd rw,nosuid,nodev,noexec,relatime shared:10 - 
cgroup cgroup 
rw,xattr,release_agent=/lib/systemd/systemd-cgroups-agent,name=systemd
29 26 0:25 / /sys/fs/cgroup/net_cls,net_prio rw,nosuid,nodev,noexec,relatime 
shared:13 - cgroup cgroup rw,net_cls,net_prio
30 26 0:26 / /sys/fs/cgroup/cpu,cpuacct rw,nosuid,nodev,noexec,relatime 
shared:14 - cgroup cgroup rw,cpu,cpuacct
31 26 0:27 / /sys/fs/cgroup/cpuset rw,nosuid,nodev,noexec,relatime shared:15 - 
cgroup cgroup rw,cpuset,clone_children
32 26 0:28 / /sys/fs/cgroup/perf_event rw,nosuid,nodev,noexec,relatime 
shared:16 - cgroup cgroup rw,perf_event
33 26 0:29 / /sys/fs/cgroup/memory rw,nosuid,nodev,noexec,relatime shared:17 - 
cgroup cgroup rw,memory
34 26 0:30 / /sys/fs/cgroup/pids rw,nosuid,nodev,noexec,relatime shared:18 - 
cgroup cgroup rw,pids
35 26 0:31 / /sys/fs/cgroup/blkio rw,nosuid,nodev,noexec,relatime shared:19 - 
cgroup cgroup rw,blkio
36 26 0:32 / /sys/fs/cgroup/freezer rw,nosuid,nodev,noexec,relatime shared:20 - 
cgroup cgroup rw,freezer
37 26 0:33 / /sys/fs/cgroup/devices rw,nosuid,nodev,noexec,relatime shared:21 - 
cgroup cgroup rw,devices
10:devices:/user.slice
9:freezer:/user/kevin/0
8:blkio:/user.slice
7:pids:/user.slice/user-1000.slice/session-1.scope
6:memory:/user/kevin/0
5:perf_event:/
4:cpuset:/
3:cpu,cpuacct:/user.slice
2:net_cls,net_prio:/
1:name=systemd:/user.slice/user-1000.slice/session-1.scope

Bug#867981: glibc: [INTL:nl] Dutch translation of debconf messages

[Frans Spiesschaert]

 
 
Package: glibc 
Severity: wishlist 
Tags: l10n patch 
 
 
Dear Maintainer, 
 
===

Please find attached the updated Dutch translation of glibc debconf
messages. 
It has been submitted for review to the debian-l10n-dutch mailing
list. 
Please add it to your next package revision. 
It should be put as debian/po/nl.po in your package build tree. 
===


-- 
Regards,
Frans


nl.po.gz
Description: application/gzip


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

Bug#867973: jessie-pu: package wordgrinder/0.5.1-1

[Adam D. Barratt]

On Mon, 2017-07-10 at 22:21 +0200, Alexander Wirt wrote:
> On Mon, 10 Jul 2017, Adam D. Barratt wrote:
> 
> > Control: tags -1 + moreinfo
> > 
> > On Mon, 2017-07-10 at 19:44 +, David Given wrote:
> > > The version in jessie of my package WordGrinder is painfully old and has a
> > > number of showstopping bugs (document corruption and loss of data). The 
> > > next
> > > available version in Debian is the version in stable, 0.6-3, which has 
> > > fixed
> > > these bugs and also contains major functionality improvements.
> > > 
> > > 0.6-3 builds on jessie out-of-the-box with no repackaging required, and 
> > > so I
> > > would like to propose the version from stable to be included in the next 
> > > jessie
> > > point release.
> > 
> > That sounds like you're looking for jessie-backports, rather than a
> > stable update.
> jessie-backports is not for fixing critical bugs like document corruption.
> Those should really get fixed in stable (of course not with an upload of the
> version in testing).

Yes, true, and sorry for being imprecise.

I meant that if the reporter was looking to get newer upstream versions
available to users of jessie, rather than specific bug fixes, then
backports was a more applicable approach.

Regards,

Adam

Bug#867979: aqbanking-tools: aqhbci-tool4 cannot load shared library,libaqhbci.so.24

[Peter Zimmerer]

Package: aqbanking-tools
Version: 5.6.12-1+b1
Severity: normal

Dear Maintainer,

if program aqhbci-tool4 is executed it will fail with error message:

aqhbci-tool4: error while loading shared libraries: libaqhbci.so.24:
cannot open shared object file: No such file or directory

If is sufficient to execute

aqhbci-tool4 --help

to reproduce the issue.

If I create a symbolic link as

sudo ln -s libaqhbci.so.23 /usr/lib/libaqhbci.so.24

the program will execute successfully.

Kind regards,
Peter

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

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

Versions of packages aqbanking-tools depends on:
ii  libaqbanking35  5.6.12-1+b1
ii  libaqbanking35-plugins  5.6.12-1+b1
ii  libaqebics0 5.6.12-1+b1
ii  libaqhbci23 5.6.12-1+b1
ii  libc6   2.24-11+deb9u1
ii  libgcc1 1:6.3.0-18
ii  libgwenhywfar60 4.15.3-5+b1
ii  libstdc++6  6.3.0-18

aqbanking-tools recommends no packages.

Versions of packages aqbanking-tools suggests:
pn  gwenhywfar-tools  

-- no debconf information

Bug#864745: jessie-pu: package perl/5.20.2-3+deb8u6

[Adam D. Barratt]

Control; tags -1 + confirmed

On Wed, 2017-06-14 at 00:14 +0100, Dominic Hargreaves wrote:
> In July 2016 we released a security update for perl to fix an optional
> module loading related vulnerability:
> 
> https://www.debian.org/security/2016/dsa-3628
> 
> This update included a change that has been since improved by upstream
> for better compatibility with existing code. The original update caused
> a few packages to FTBFS:
> 
> #864302
> #864299
> #832862
> #832866
> #832845
> 
> As such we believe that it makes sense to update perl in jessie to
> include the improved fix, which is scheduled for inclusion in upstream
> maintenance releases soon.

Please go ahead.

Regards,

Adam

Bug#867973: jessie-pu: package wordgrinder/0.5.1-1

[Alexander Wirt]

On Mon, 10 Jul 2017, Adam D. Barratt wrote:

> Control: tags -1 + moreinfo
> 
> On Mon, 2017-07-10 at 19:44 +, David Given wrote:
> > The version in jessie of my package WordGrinder is painfully old and has a
> > number of showstopping bugs (document corruption and loss of data). The next
> > available version in Debian is the version in stable, 0.6-3, which has fixed
> > these bugs and also contains major functionality improvements.
> > 
> > 0.6-3 builds on jessie out-of-the-box with no repackaging required, and so I
> > would like to propose the version from stable to be included in the next 
> > jessie
> > point release.
> 
> That sounds like you're looking for jessie-backports, rather than a
> stable update.
jessie-backports is not for fixing critical bugs like document corruption.
Those should really get fixed in stable (of course not with an upload of the
version in testing).

 
Alex - Backports ftpmaster

Bug#867966: stretch-pu: package python3-colorlog/2.10.0-1

[Philipp Huebner]

debdiff attached

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


debdiff python-colorlog_2.10.0-1.dsc python-colorlog_2.10.0-1+deb9u1.dsc

diff -Nru python-colorlog-2.10.0/debian/changelog 
python-colorlog-2.10.0/debian/changelog
--- python-colorlog-2.10.0/debian/changelog 2016-11-23 22:49:49.0 
+0100
+++ python-colorlog-2.10.0/debian/changelog 2017-07-10 21:23:44.0 
+0200
@@ -1,3 +1,9 @@
+python-colorlog (2.10.0-1+deb9u1) stable; urgency=medium
+
+  * Fix python3 dependencies (Closes: #867422)
+
+ -- Philipp Huebner   Mon, 10 Jul 2017 21:23:44 +0200
+
 python-colorlog (2.10.0-1) unstable; urgency=medium
 
   * New upstream version 2.10.0
diff -Nru python-colorlog-2.10.0/debian/control 
python-colorlog-2.10.0/debian/control
--- python-colorlog-2.10.0/debian/control   2016-11-23 22:40:16.0 
+0100
+++ python-colorlog-2.10.0/debian/control   2017-07-10 20:38:56.0 
+0200
@@ -20,7 +20,7 @@
 
 Package: python3-colorlog
 Architecture: all
-Depends: ${misc:Depends}, ${python:Depends}
+Depends: ${misc:Depends}, ${python3:Depends}
 Description: formatter to use with the logging module of Python 3
  python-colorlog allows colors to be placed in the format string, which is
  mostly useful when paired with a StreamHandler that is outputting to a


signature.asc
Description: OpenPGP digital signature

Bug#867970: stretch-pu: package python3-plumbum/1.6.2-1

[Philipp Huebner]

debdiff attached

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

debdiff python-plumbum_1.6.2-1.dsc python-plumbum_1.6.2-1+deb9u1.dsc

diff -Nru python-plumbum-1.6.2/debian/changelog 
python-plumbum-1.6.2/debian/changelog
--- python-plumbum-1.6.2/debian/changelog   2016-06-26 15:33:39.0 
+0200
+++ python-plumbum-1.6.2/debian/changelog   2017-07-10 21:24:42.0 
+0200
@@ -1,3 +1,9 @@
+python-plumbum (1.6.2-1+deb9u1) stable; urgency=medium
+
+  * Fix python3 dependencies (Closes: #867449)
+
+ -- Philipp Huebner   Mon, 10 Jul 2017 21:24:42 +0200
+
 python-plumbum (1.6.2-1) unstable; urgency=medium
 
   * Imported Upstream version 1.6.2
diff -Nru python-plumbum-1.6.2/debian/control 
python-plumbum-1.6.2/debian/control
--- python-plumbum-1.6.2/debian/control 2016-05-01 13:29:41.0 +0200
+++ python-plumbum-1.6.2/debian/control 2017-07-10 21:14:17.0 +0200
@@ -22,7 +22,7 @@
 
 Package: python3-plumbum
 Architecture: all
-Depends: ${misc:Depends}, ${python:Depends}
+Depends: ${misc:Depends}, ${python3:Depends}
 Description: library for writing shell script-like programs in Python 3
  python-plumbum provides shell-like syntax and handy shortcuts for writing 
shell
  script one-liners in Python using shell combinators. It supports local and


signature.asc
Description: OpenPGP digital signature

Bug#867973: jessie-pu: package wordgrinder/0.5.1-1

[Adam D. Barratt]

Control: tags -1 + moreinfo

On Mon, 2017-07-10 at 19:44 +, David Given wrote:
> The version in jessie of my package WordGrinder is painfully old and has a
> number of showstopping bugs (document corruption and loss of data). The next
> available version in Debian is the version in stable, 0.6-3, which has fixed
> these bugs and also contains major functionality improvements.
> 
> 0.6-3 builds on jessie out-of-the-box with no repackaging required, and so I
> would like to propose the version from stable to be included in the next 
> jessie
> point release.

That sounds like you're looking for jessie-backports, rather than a
stable update.

> (No debdiff is attached as it's empty!)

It's really not. The relevant debdiff is between the package currently
in jessie and the package you're proposing for jessie. Even if it were
only the diff for the rebuild that was required, there'd still be at
least a debian/changelog entry.

$ debdiff /srv/mirrors/debian/pool/main/w/wordgrinder/wordgrinder_0.5.1-1.dsc \
  /srv/mirrors/debian/pool/main/w/wordgrinder/wordgrinder_0.6-3.dsc | diffstat 
-s
 139 files changed, 352240 insertions(+), 5172 deletions(-)

Filtering out the dictionaries, tests, Windows-related files and
embedded copy of the minizip library drops that quite a bit, but still
leaves

85 files changed, 6931 insertions(+), 1017 deletions(-)

> Disclaimer: as well as being the package maintainer I'm also the upstream
> author of WordGrinder (and it's my considered opinion that WordGrinder 0.5.1
> needs to be taken out of circulation as quickly as possible before it starts
> hurting people).

If it's that bad, we can remove it from jessie if you'd prefer.

Regards,

Adam

Bug#867978: /usr/bin/qemu-system-x86_64: virtio-net with vhost is broken with legacy interrupts

[Stefan Fritsch]

Package: qemu-system-x86
Version: 1:2.8+dfsg-6
Severity: normal
File: /usr/bin/qemu-system-x86_64
Tags: patch

Hi,

updating from jessie to stretch causes a regression with guests that do
use virtio-net but don't support MSI-X [1], like openbsd 32 bit. There
are no rx interrupts triggered in the guest. A workaround is to disable
vhost.

By testing with vanilla qemu (not the debian packaged version), I have
found that cherry-picking this upstream commit on top of v2.8.1.1 fixes
the problem:

commit b4b9862b536f41fcdf6ad193a306a852c5b5b71a
Author: Michael S. Tsirkin 
Date:   Fri Feb 17 04:52:16 2017 +0200

virtio: Fix no interrupt when not creating msi controller

For ARM virt machine, if we use virt-2.7 which will not create ITS node,
the virtio-net can not recieve interrupts so it can't get ip address
through dhcp.
This fixes commit 83d768b(virtio: set ISR on dataplane notifications).

Signed-off-by: Shannon Zhao 
Reviewed-by: Michael S. Tsirkin 
Signed-off-by: Michael S. Tsirkin 

This commit is contained in 2.9.  It would be great if that fix could be
added to stretch's qemu, too, so that openbsd 32bit guests (and older
openbsd 64bit guesets) work out of the box again. Thanks in advance.

Cheers,
Stefan

[1] http://marc.info/?l=openbsd-misc=149951878107145=2


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

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

Versions of packages qemu-system-x86 depends on:
ii  ipxe-qemu   1.0.0+git-20161027.b991c67-1
ii  libaio1 0.3.110-3
ii  libasound2  1.1.3-5
ii  libbluetooth3   5.45-1
ii  libbrlapi0.65.4-7+b1
ii  libc6   2.24-12
ii  libcacard0  1:2.5.0-3
ii  libfdt1 1.4.2-1
ii  libgcc1 1:7.1.0-9
ii  libglib2.0-02.52.3-1
ii  libgnutls30 3.5.14-2
ii  libjpeg62-turbo 1:1.5.1-2
ii  libncursesw56.0+20170701-1
ii  libnettle6  3.3-1+b1
ii  libnuma12.0.11-2.1
ii  libpixman-1-0   0.34.0-1
ii  libpng16-16 1.6.30-2
ii  libpulse0   10.0-2
ii  libsasl2-2  2.1.27~101-g0780600+dfsg-3
ii  libsdl1.2debian 1.2.15+dfsg1-4
ii  libseccomp2 2.3.1-2.1
ii  libspice-server10.12.8-2.1
ii  libtinfo5   6.0+20170701-1
ii  libusb-1.0-02:1.0.21-2
ii  libusbredirparser1  0.7.1-1
ii  libvdeplug2 2.3.2+r586-2.1
ii  libx11-62:1.6.4-3
ii  libxen-4.8  4.8.1-1+deb9u1
ii  libxenstore3.0  4.8.1-1+deb9u1
ii  qemu-system-common  1:2.8+dfsg-6
ii  seabios 1.10.2-1
ii  zlib1g  1:1.2.8.dfsg-5

Versions of packages qemu-system-x86 recommends:
ii  qemu-utils  1:2.8+dfsg-6

Versions of packages qemu-system-x86 suggests:
ii  kmod  24-1
pn  ovmf  
pn  qemu-block-extra  
pn  samba 
ii  sgabios   0.0~svn8-4
pn  vde2  

-- no debconf information

Bug#867977: youtube-dl: Arbitary JavaScript execution?

[Joonas Kylmälä]

Package: youtube-dl
Version: 2017.05.18.1-1
Severity: normal

Dear Maintainer,

Recently Trisquel GNU/Linux users discovered that youtube-dl might in
some cases execute (as far as I understood) arbitary JavaScript served
by the web server it connects to, and thus be harmful for the
user. See
. Can
we somehow work around these JavaScript requirements? At least I think
it would be a good thing to warning the user about arbitary JavaScript
being run as I, for example, didn't expect that a cli application
would run JavaScript.

Joonas

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

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

Versions of packages youtube-dl depends on:
ii  dpkg   1.18.24
ii  python33.5.3-1
ii  python3-pkg-resources  33.1.1-1

Versions of packages youtube-dl recommends:
ii  ca-certificates  20161130+nmu1
ii  curl 7.52.1-5
ii  ffmpeg   7:3.2.5-1
ii  mplayer  2:1.3.0-6
ii  rtmpdump 2.4+20151223.gitfa8646d.1-1+b1
ii  wget 1.18-5

youtube-dl suggests no packages.

-- no debconf information

Bug#867827: Incremental regexp search crashes after pressing backslash

[Gavin Smith]

On 10 July 2017 at 16:19, Norbert Preining  wrote:
> Dear texinfo team,
>
> (please keep cc)
>
> down at Debian we got the following bug report:
>
> On Sun, 09 Jul 2017, Ben Hutchings wrote:
>> When I press C-s, \, info writes:
>>
>> regexp error: Trailing backslash
>>
>> and then segfaults.

This was fixed in SVN revision 7907 on 2017-07-05.

Because it is quite a bad bug, I have made a pretest release available
with it fixed (as well as a few other fixes):

http://alpha.gnu.org/gnu/texinfo/texinfo-6.4.90.tar.xz.sig

Hopefully we will be able to release Texinfo 6.5 soon without any very
bad bugs in it. Please feel free to try the test release.

Bug#867976: mate-tweak: fails to start, missing dependency

[dimitris]

Package: mate-tweak
Version: 16.10.5-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

   * What led up to the situation?
installed mate-tweak and trying to open mate-tweak from mate 
control panel or mate-terminal
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
-
   * What was the outcome of this action?
$ mate-tweak
mate-tweak Traceback (most recent call last): File 
"/usr/bin/mate-tweak", line 24, in  import gi 
ImportError: No module named 'gi'

   * What outcome did you expect instead?
mate-tweak to start as expected

after installing python3-gi package, mate-tweak works as expected, so i 
guess its a missing dependency issue.

thanks,
dimitris


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

Kernel: Linux 4.11.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (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 mate-tweak depends on:
ii  compton0.1~beta2+20150922-1
ii  dconf-cli  0.26.0-2+b1
ii  gir1.2-gtk-3.0 3.22.16-1
ii  gir1.2-notify-0.7  0.7.7-2
ii  mate-desktop-common1.16.2-2
ii  mesa-utils 8.3.0-5
ii  python-gobject-2   2.28.6-13
ii  python33.5.3-3
ii  python3-pkg-resources  36.0.1-1
ii  python3-psutil 5.0.1-1+b1
ii  python3-setproctitle   1.1.10-1+b1
ii  x11-xserver-utils  7.7+7+b1
ii  zenity 3.22.0-1+b1

Versions of packages mate-tweak recommends:
ii  mate-indicator-applet  1.16.0-1

Versions of packages mate-tweak suggests:
pn  indicator-application  
pn  indicator-messages 
pn  indicator-sounds   
pn  metacity   
pn  xcompmgr   

-- no debconf information

Bug#867975: endless-sky: Request for update of Endless Sky in unstable and testing to version 0.9.6

[Marco Oliva]

Source: endless-sky
Version: 0.8.11-1
Severity: important

Dear Maintainer,

Thank you very much for maintaining this Spectacular game.

I'd like to ask you, please, to upgrade the version game to 0.9.6 because the
0.8.11-1 is outdated and the new version has new and awesome features.

Thanks!
Best regards,
Marco Oliva




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

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

Bug#867973: jessie-pu: package wordgrinder/0.5.1-1

[David Given]

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

The version in jessie of my package WordGrinder is painfully old and has a
number of showstopping bugs (document corruption and loss of data). The next
available version in Debian is the version in stable, 0.6-3, which has fixed
these bugs and also contains major functionality improvements.

0.6-3 builds on jessie out-of-the-box with no repackaging required, and so I
would like to propose the version from stable to be included in the next jessie
point release.

(No debdiff is attached as it's empty!)

Disclaimer: as well as being the package maintainer I'm also the upstream
author of WordGrinder (and it's my considered opinion that WordGrinder 0.5.1
needs to be taken out of circulation as quickly as possible before it starts
hurting people).

-- System Information:
Debian Release: 8.8
  APT prefers oldstable
  APT policy: (500, 'oldstable')
Architecture: armhf (armv7l)

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

Bug#867974: libqt5gui5: new-delete-type-mismatch in QOpenGLContext destructor

[Sergey Sharybin]

Package: libqt5gui5
Version: 5.7.1+dfsg-3+b1
Severity: normal

Dear Maintainer,

When building Qt5 application which uses QOpenGL classes with ASAN support 
there is
a new-delete-type-mismatch reported by the ASAN.

In order to reproduce the issue, it is enough to compile threadedqopenglwidget 
demo
application with -fsanitize=address, run the application, close all windows. 
See the
ASAN report in console after that.

This is likely the same exact issue as reported there:

  https://bugreports.qt.io/browse/QTBUG-57773

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

Kernel: Linux 4.11.5-vanilla (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (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 libqt5gui5 depends on:
ii  fontconfig   2.11.0-6.7+b1
ii  libc62.24-11+deb9u1
ii  libdrm2  2.4.74-1
ii  libegl1-mesa [libegl1-x11]   13.0.6-1+b2
ii  libfontconfig1   2.11.0-6.7+b1
ii  libfreetype6 2.6.3-3.2
ii  libgbm1  13.0.6-1+b2
ii  libgcc1  1:7.1.0-7
ii  libgl1-mesa-glx [libgl1] 13.0.6-1+b2
ii  libglib2.0-0 2.50.3-2
ii  libharfbuzz0b1.4.2-1
ii  libice6  2:1.0.9-2
ii  libinput10   1.6.3-1
ii  libjpeg62-turbo  1:1.5.1-2
ii  libmtdev11.1.5-1+b1
ii  libpng16-16  1.6.28-1
ii  libqt5core5a [qtbase-abi-5-7-1]  5.7.1+dfsg-3+b1
ii  libqt5dbus5  5.7.1+dfsg-3+b1
ii  libqt5network5   5.7.1+dfsg-3+b1
ii  libsm6   2:1.2.2-1+b3
ii  libstdc++6   7.1.0-7
ii  libudev1 232-25
ii  libx11-6 2:1.6.4-3
ii  libx11-xcb1  2:1.6.4-3
ii  libxcb-glx0  1.12-1
ii  libxcb-icccm40.4.1-1
ii  libxcb-image00.4.0-1+b2
ii  libxcb-keysyms1  0.4.0-1+b2
ii  libxcb-randr01.12-1
ii  libxcb-render-util0  0.3.9-1
ii  libxcb-render0   1.12-1
ii  libxcb-shape01.12-1
ii  libxcb-shm0  1.12-1
ii  libxcb-sync1 1.12-1
ii  libxcb-xfixes0   1.12-1
ii  libxcb-xinerama0 1.12-1
ii  libxcb-xkb1  1.12-1
ii  libxcb1  1.12-1
ii  libxi6   2:1.7.9-1
ii  libxkbcommon-x11-0   0.7.1-1
ii  libxkbcommon00.7.1-1
ii  zlib1g   1:1.2.8.dfsg-5

Versions of packages libqt5gui5 recommends:
ii  libqt5svg5 5.7.1~20161021-2+b2
ii  mesa-utils 8.3.0-3
pn  qt5-gtk-platformtheme  

Versions of packages libqt5gui5 suggests:
pn  qt5-image-formats-plugins  
pn  qtwayland5 

-- no debconf information

Bug#867972: keychain: adding a GPG key fails

[Dave Love]

Package: keychain
Version: 2.8.2-0.1
Severity: normal

Trying to add a GPG key according to the documentation fails.  It's
fixed in version 2.8.3 by
.

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

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

Versions of packages keychain depends on:
ii  openssh-client [ssh-client]  1:7.4p1-10

keychain recommends no packages.

Versions of packages keychain suggests:
ii  gnupg-agent  2.1.18-6
pn  ssh-askpass  

-- no debconf information

Bug#867971: RFP: vobsub2srt -- converts vobsub (.idx/.sub) into .srt subtitles

[Matt Zagrabelny]

Package: wnpp
Severity: wishlist

* Package name: vobsub2srt
  Version : 2017.07.10
  Upstream Author : Rüdiger Sonderfeld 
* URL : https://github.com/ruediger/VobSub2SRT
* License : GPL3+
  Programming Lang: C++
  Description : converts vobsub (.idx/.sub) into .srt subtitles

vobsub2srt converts subtitles in vobsub (.idx/.sub) format into the .srt
format. VobSub subtitles contain images and srt is a text format. OCR
is used to extract the text from the subtitles.  vobsub2srt uses
tesseract for OCR and is based on code from the MPlayer project.

vobsub2srt is a useful piece of software for converting DVD subtitles from an
image-based format to a text-based format. To my knowledge, the Debian
archive does not have an equivalent piece of software.

If a team was interested in maintaining this software, the Debian
Multimedia Maintainers 
would be a logical team to do so.

Thanks for your consideration.

-m

Bug#867966: stretch-pu: packages python3-colorlog/2.10.0-1 and python3-plumbum/1.6.2-1

[Adam D. Barratt]

Control: tags -1 + moreinfo
Control: clone -1 -2
Control: retitle -1 stretch-pu: package python3-colorlog/2.10.0-1
Control: retitle -2 stretch-pu: package python3-plumbum/1.6.2-1

On Mon, 2017-07-10 at 21:01 +0200, Philipp Huebner wrote:
> due to bugs #867422 and #867449 the Python 3 versions of my packages
> ended up without any dependencies.
> 
> The fix is to add a single "3" in debian/control:
> -Depends: ${misc:Depends}, ${python:Depends}
> +Depends: ${misc:Depends}, ${python3:Depends}

Even if that's the only change, we'd still like to see a debdiff of the
proposed source package, as built and tested on stretch before
confirming, please.

(When doing so, note that I've cloned a copy of this bug, as each p-u
bug tracks a single source package.)

> I have already fixed this in unstable and would like to fix this in
> Stretch, too. Maybe Jessie as well.

If you'd like to look at jessie then please file separate bugs for that,
so we can track the individual fixes.

Regards,

Adam

Bug#867969: ITP: sdformat5 -- Simulation Description Format (SDF) parser

[Jose Luis Rivero]

Package: wnpp
Severity: wishlist
Owner: Jose Luis Rivero 

* Package name: sdformat5
Version   : 5.1.0
Upstream Author   : Open Source Robotics Foundation
* URL : http://sdformat.org
* License : BSD
Programming Lang  : C++
Description   : Simulation Description Format (SDF) parser

SDF is an XML file format that describes environments, objects, and
robots in a manner suitable for robotic applications. SDF is capable of
representing and describing different physic engines, lighting
properties, terrain, static or dynamic objects, and articulated robots
with various sensors, and acutators.  The format of SDF is also
described by XML, which facilitates updates and allows conversion from
previous versions. A parser is also contained within this package that
reads SDF files and returns a C++ interface.

Version 4 is already in debian.

Bug#867968: ITP: ign-transport3 -- Ignition Transport library v3

[Jose Luis Rivero]

Package: wnpp
Severity: wishlist
Owner: Jose Luis Rivero 

* Package name: ign-transport3
  Version : 3.0.1
  Upstream Author : Open Source Robotics Foundation
* URL : http://ignitionrobotics.org/libraries/transport
* License : Apache
  Programming Lang: C++
  Description : Transport library which combines ZeroMQ and Protobuf

ignition transport library combines ZeroMQ with Protobufs to create a
fast and efficient message passing system. Asynchronous message
publication and subscription is provided along with service calls and
discovery.

The version 1 is already in Debian. Here is the version 3.

Bug#867967: apt: The key(s) in the keyring are ignored. Not readable by user '_apt'.

[Adam Smith]

Package: apt
Version: 1.4.6
Severity: important

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

After adding contrib and non-free sources in synaptic and refreshing the
repositories I am presented with the following error message:

"http://debian.mirror.constant.com/debian/dists/stretch-updates/InRelease: The
key(s) in the keyring /etc/apt/trusted.gpg are ignored as the file is not
readable by user '_apt' executing apt-key.The repository
'http://debian.mirror.constant.com/debian stretch/updates Release' does not
have a Release file.Updating from such a repository can't be done securely, and
is therefore disabled by default.See apt-secure(8) manpage for repository
creation and user configuration
details.http://debian.mirror.constant.com/debian/dists/stretch/Release.gpg: The
key(s) in the keyring /etc/apt/trusted.gpg are ignored as the file is not
readable by user '_apt' executing apt-key."

I have tried installing Stretch via both the netintsaller and live ISO and
encountered the same problem, also installing without root and also with. I am
a linux noob, first starting out on Jessie which I ran into no problems with
and served my basic desktop needs well. Therefore I can only try to find
solutions online and could not find anything that worked.



-- Package-specific info:

-- apt-config dump --

APT "";
APT::Architecture "amd64";
APT::Build-Essential "";
APT::Build-Essential:: "build-essential";
APT::Install-Recommends "true";
APT::Install-Suggests "0";
APT::Sandbox "";
APT::Sandbox::User "_apt";
APT::Authentication "";
APT::Authentication::TrustCDROM "true";
APT::NeverAutoRemove "";
APT::NeverAutoRemove:: "^firmware-linux.*";
APT::NeverAutoRemove:: "^linux-firmware$";
APT::NeverAutoRemove:: "^linux-image-4\.9\.0-3-amd64$";
APT::NeverAutoRemove:: "^linux-headers-4\.9\.0-3-amd64$";
APT::NeverAutoRemove:: "^linux-image-extra-4\.9\.0-3-amd64$";
APT::NeverAutoRemove:: "^linux-signed-image-4\.9\.0-3-amd64$";
APT::NeverAutoRemove:: "^kfreebsd-image-4\.9\.0-3-amd64$";
APT::NeverAutoRemove:: "^kfreebsd-headers-4\.9\.0-3-amd64$";
APT::NeverAutoRemove:: "^gnumach-image-4\.9\.0-3-amd64$";
APT::NeverAutoRemove:: "^.*-modules-4\.9\.0-3-amd64$";
APT::NeverAutoRemove:: "^.*-kernel-4\.9\.0-3-amd64$";
APT::NeverAutoRemove:: "^linux-backports-modules-.*-4\.9\.0-3-amd64$";
APT::NeverAutoRemove:: "^linux-tools-4\.9\.0-3-amd64$";
APT::VersionedKernelPackages "";
APT::VersionedKernelPackages:: "linux-image";
APT::VersionedKernelPackages:: "linux-headers";
APT::VersionedKernelPackages:: "linux-image-extra";
APT::VersionedKernelPackages:: "linux-signed-image";
APT::VersionedKernelPackages:: "kfreebsd-image";
APT::VersionedKernelPackages:: "kfreebsd-headers";
APT::VersionedKernelPackages:: "gnumach-image";
APT::VersionedKernelPackages:: ".*-modules";
APT::VersionedKernelPackages:: ".*-kernel";
APT::VersionedKernelPackages:: "linux-backports-modules-.*";
APT::VersionedKernelPackages:: "linux-tools";
APT::Never-MarkAuto-Sections "";
APT::Never-MarkAuto-Sections:: "metapackages";
APT::Never-MarkAuto-Sections:: "contrib/metapackages";
APT::Never-MarkAuto-Sections:: "non-free/metapackages";
APT::Never-MarkAuto-Sections:: "restricted/metapackages";
APT::Never-MarkAuto-Sections:: "universe/metapackages";
APT::Never-MarkAuto-Sections:: "multiverse/metapackages";
APT::Move-Autobit-Sections "";
APT::Move-Autobit-Sections:: "oldlibs";
APT::Move-Autobit-Sections:: "contrib/oldlibs";
APT::Move-Autobit-Sections:: "non-free/oldlibs";
APT::Move-Autobit-Sections:: "restricted/oldlibs";
APT::Move-Autobit-Sections:: "universe/oldlibs";
APT::Move-Autobit-Sections:: "multiverse/oldlibs";
APT::Periodic "";
APT::Periodic::Update-Package-Lists "1";
APT::Periodic::Unattended-Upgrade "1";
APT::Update "";
APT::Update::Post-Invoke-Success "";
APT::Update::Post-Invoke-Success:: "/usr/bin/test -e 
/usr/share/dbus-1/system-services/org.freedesktop.PackageKit.service && 
/usr/bin/test -S /var/run/dbus/system_bus_socket && /usr/bin/gdbus call 
--system --dest org.freedesktop.PackageKit --object-path 
/org/freedesktop/PackageKit --timeout 4 --method 
org.freedesktop.PackageKit.StateHasChanged cache-update > /dev/null; /bin/echo 
> /dev/null";
APT::Update::Post-Invoke-Success:: "if /usr/bin/test -w /var/cache/app-info -a 
-e /usr/bin/appstreamcli; then appstreamcli refresh-cache > /dev/null; fi";
APT::Architectures "";
APT::Architectures:: "amd64";
APT::Compressor "";
APT::Compressor::. "";
APT::Compressor::.::Name ".";
APT::Compressor::.::Extension "";
APT::Compressor::.::Binary "";
APT::Compressor::.::Cost "0";
APT::Compressor::lz4 "";
APT::Compressor::lz4::Name "lz4";
APT::Compressor::lz4::Extension ".lz4";
APT::Compressor::lz4::Binary "false";

Bug#608648: dpkg-reconfigure should chdir("/") before running maintainer scripts

[Andreas Beckmann]

Followup-For: Bug #608648

This change causes regressions, e.g. #867256. I might find more until
sid has seen a complete recheck in piuparts.

That change sounds sensible and should not be reverted, just the
affected packages should be fixed.


Andreas

Bug#867818: No printer listed in some applications when no default printer is set

[Didier 'OdyX' Raboud]

Control: tags -1 +patch +pending

Le lundi, 10 juillet 2017, 09.28:00 h CEST Viktor Jägersküpper a écrit :
> Brian Potkin:
> > On Sun 09 Jul 2017 at 17:41:00 +, Viktor Jägersküpper wrote:
> >> The bug is already fixed upstream.
> > 
> > Reference, please.
> 
> https://github.com/apple/cups/commit/
b2f85109da901eb652babdc4f2a846c1c28228ff

Ah, great, thank you for the reference! Will include in the next upload!

Cheers,
OdyX

Bug#867966: stretch-pu: packages python3-colorlog/2.10.0-1 and python3-plumbum/1.6.2-1

[Philipp Huebner]

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

Hi,

due to bugs #867422 and #867449 the Python 3 versions of my packages
ended up without any dependencies.

The fix is to add a single "3" in debian/control:
-Depends: ${misc:Depends}, ${python:Depends}
+Depends: ${misc:Depends}, ${python3:Depends}

I have already fixed this in unstable and would like to fix this in
Stretch, too. Maybe Jessie as well.

Regards,
Philipp

Bug#867256: monitoring-plugins-basic: fails to install: Error: The new file apt.cfg does not exist!

[Andreas Beckmann]

Control: tag -1 sid buster - moreinfo unreproducible

On 2017-07-10 15:39, Jan Wagner wrote:
> I did run a "apt install monitoring-plugins-basic" on a fresh stretch
> container.

Looking at my logs, the problem was only reproducible in sid at the time
I filed the bug, but now it also happens in buster.

OK, let me debug a bit more after the failure occurred

# sed -i '2iset -x' /var/lib/dpkg/info/monitoring-plugins-basic.postinst
# dpkg --configure --pending
Setting up monitoring-plugins-basic (2.2-3) ...
+ set -e
+ templdir=/usr/share/monitoring-plugins/templates-basic
+ . /usr/share/monitoring-plugins/dpkg/functions
+ npconfdir=/etc/nagios-plugins/config
+ plugindir=/usr/lib/nagios/plugins/
+ [ configure = configure ]
+ register_cfgs
+ cd /usr/share/monitoring-plugins/templates-basic
+ dest=/etc/nagios-plugins/config/apt.cfg
+ ucf apt.cfg /etc/nagios-plugins/config/apt.cfg
Error: The new file apt.cfg does not exist!
dpkg: error processing package monitoring-plugins-basic (--configure):
 subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
 monitoring-plugins-basic

extending the error message in ucf to also print $(pwd), reveals that
the current directory of the process is /, which leads us to


debconf (1.5.62) unstable; urgency=medium
...
  * Change directory to / before executing maintainer scripts (closes:
#608648).
...


So address your configuration files with absolute paths.



Andreas

Bug#866797: transition: gdal

[Sebastiaan Couwenberg]

On 07/10/2017 05:45 PM, Emilio Pozuelo Monfort wrote:
> On 04/07/17 21:43, Emilio Pozuelo Monfort wrote:
>> On 01/07/17 21:17, Bas Couwenberg wrote:
>>> For the Debian GIS team I'd like to transition to GDAL 2.2.1.
>>>
>>> Like the previous transition to GDAL 2.1.2 (#842288), there is no SONAME
>>> bump, only the virtual ABI package changed to account for the C++ symbol
>>> changes.
>>>
>>> All reverse dependencies rebuilt successfully with GDAL 2.2.1 from
>>> experimental as summarized below, except rasterio & vtk6.
>>>
>>> rasterio cannot be built yet because python-numpy hasn't been built with
>>> Python 3.6 yet as part of the python3-defaults transition (#866335).
>>> rasterio built successfully with Python 3.5 and GDAL 2.2.1~rc1, so this
>>> will likely be resolved with the rebuild of python-numpy.
>>>
>>> vtk6 FTBFS due to missing build dependencies: texlive-math-extra.
>>> The recent texlive-extra source packages no longer build with binary
>>> package. Dropping the build dependency was sufficient to build vtk6
>>> successfully with GDAL 2.2.1. The patch has been submitted in #866723.
>>>
>>> A new revision of qgis has been uploaded to unstable which includes the
>>> changes from 2.14.16 (currently in NEW) for GDAL 2.2 support, which
>>> allow the package the build successfully with GDAL 2.2.1 too.
>>>
>>>
>>> libgdal-grass doesn't need a binNMU as the 2.2.1 version will be
>>> uploaded to unstable instead. liblas likewise doesn't need a binNMU,
>>> the version is experimental will be moved to unstable instead.
>>>
>>> Please also binNMU mapnik in experimental as part of the transition.
>>
>> Let's wait a bit for this, I want the octave transition to finish
>> first (and to make sure the python3.6 one won't be a problem). In
>> the meantime you can get vtk6 fixed and qgis accepted.
> 
> octave is in and the python transition shouldn't be a problem anymore, so 
> please
> go ahead if you're ready to do the necessary NMUs.

Thanks, gdal (2.2.1+dfsg-1), liblas (1.8.1-4) & libgdal-grass (2.2.1-1)
have been uploaded to unstable.

Hopefully no NMUs will be necessary. vtk6 has been fixed, but has not
migrated to testing yet. None of the other packages had issues when the
rebuilds were performed, if anything has cropped up since then I'll have
a go at fixing that.

Kind Regards,

Bas

-- 
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1

Bug#867723: ejabberd: `dpkg-reconfigure ejabberd` fails with `Can't register admin user`

[Soren Stoutner]

Phillip,

Thank you for your quick response.  Before submitting the bug, I had tried to 
manually register a user with version 16.09-4 and received the same error you 
documented.  However, I am able to manually register the admin user with 
17.04-1~exp2, so it would be appropriate to lower the severity.

Thanks for your assistance.

Soren

P.S.  Note that I still get an `erl_crash.dump` file every time `dpkg-
reconfigure ejabberd` is run on 17.04-1~exp2, so there are likely some other 
incompatibilities introduced with the Erlang 20 transition.

On Sunday, July 9, 2017 12:55:36 PM MST you wrote:
> Am 08.07.2017 um 23:33 schrieb Soren Stoutner:
> > Package: ejabberd
> > Version: 17.04-1~exp2
> 
> I just tried this version, and it still works for me!

-- 
Soren Stoutner
Small Business Tech Solutions
623-262-6169
so...@smallbusinesstech.net
www.smallbusinesstech.net

Bug#867965: stretch-pu: package pykde4/4.14.3-2+deb9u1

[Scott Kitterman]

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

QtWebKit support was removed from PyQt4 as part of an attempt to (originally)
remove it for stretch and later reduce its use to a minimum due to scads of
unfixed security issues (QtWebKit for Qt4 has been unmaintained upstream for
quite some time).  I neglected to remove QtWebKit usages from PyKDE4 before
release (see the bug this fixes).

All this patch does is remove usage of the not available functionality so that
the bindings work at all.  Regression risk is nil.  The same change is already
in sid and buster with no issues reported.

The package is ready to upload.  I would appreciate an ack in time to get this
in for 9.1 (but understand that I might not get that).

Debdiff attached.

Thanks,

Scott K
diff -Nru pykde4-4.14.3/debian/changelog pykde4-4.14.3/debian/changelog
--- pykde4-4.14.3/debian/changelog	2016-06-29 13:54:34.0 -0400
+++ pykde4-4.14.3/debian/changelog	2017-07-10 14:01:23.0 -0400
@@ -1,3 +1,13 @@
+pykde4 (4:4.14.3-2+deb9u1) stable; urgency=medium
+
+  * Team upload.
+  * Drop bindings for plasma webview bindings: No longer functional due to
+QtWebKit being dropped from PyQt4 and obsolete (Closes: #865861)
+- Add debian/patches/no_webview_webkit.patch
+- Drop libqtwebkit-dev from build-depends
+
+ -- Scott Kitterman   Mon, 10 Jul 2017 14:00:50 -0400
+
 pykde4 (4:4.14.3-2) unstable; urgency=medium
 
   * Team upload.
diff -Nru pykde4-4.14.3/debian/control pykde4-4.14.3/debian/control
--- pykde4-4.14.3/debian/control	2016-06-26 01:05:03.0 -0400
+++ pykde4-4.14.3/debian/control	2017-06-26 14:52:30.0 -0400
@@ -10,7 +10,6 @@
libphonon-dev (>= 4:4.6.0really4.4.4),
libqt4-dev (>= 4:4.7.1),
libqt4-opengl-dev (>= 4:4.7.1),
-   libqtwebkit-dev,
libsoprano-dev (>= 2.7.0),
pkg-config,
pkg-kde-tools (>= 0.12),
diff -Nru pykde4-4.14.3/debian/patches/no_webview_webkit.patch pykde4-4.14.3/debian/patches/no_webview_webkit.patch
--- pykde4-4.14.3/debian/patches/no_webview_webkit.patch	1969-12-31 19:00:00.0 -0500
+++ pykde4-4.14.3/debian/patches/no_webview_webkit.patch	2017-06-26 14:52:30.0 -0400
@@ -0,0 +1,158 @@
+--- pykde4-4.14.3.orig/CMakeLists.txt
 pykde4-4.14.3/CMakeLists.txt
+@@ -91,7 +91,6 @@ include_directories(
+ ${QT_QTSQL_INCLUDE_DIR}
+ ${QT_QTXML_INCLUDE_DIR}
+ ${QT_QTSVG_INCLUDE_DIR}
+-${QT_QTWEBKIT_INCLUDE_DIR}
+ ${KDE4_INCLUDE_DIR}
+ ${KDE4_INCLUDE_DIR}/solid
+ ${KDE4_INCLUDE_DIR}/kio
+--- pykde4-4.14.3.orig/sip/plasma/abstractrunner.sip
 pykde4-4.14.3/sip/plasma/abstractrunner.sip
+@@ -94,7 +94,6 @@
+ #include 
+ #include 
+ #include 
+-#include 
+ %End
+ 
+ namespace Plasma
+@@ -288,8 +287,6 @@ protected:
+ sipType = sipType_Plasma_SvgWidget;
+ else if (dynamic_cast(sipCpp))
+ sipType = sipType_Plasma_TabBar;
+-else if (dynamic_cast(sipCpp))
+-sipType = sipType_Plasma_WebView;
+ else if (dynamic_cast(sipCpp))
+ sipType = sipType_Plasma_CheckBox;
+ else if (dynamic_cast(sipCpp))
+--- pykde4-4.14.3.orig/sip/plasma/animation.sip
 pykde4-4.14.3/sip/plasma/animation.sip
+@@ -163,8 +163,6 @@ protected:
+ sipType = sipType_Plasma_SvgWidget;
+ else if (dynamic_cast(sipCpp))
+ sipType = sipType_Plasma_TabBar;
+-else if (dynamic_cast(sipCpp))
+-sipType = sipType_Plasma_WebView;
+ else if (dynamic_cast(sipCpp))
+ sipType = sipType_Plasma_CheckBox;
+ else if (dynamic_cast(sipCpp))
+@@ -292,5 +290,4 @@ public:
+ #include 
+ #include 
+ #include 
+-#include 
+ %End
+--- pykde4-4.14.3.orig/sip/plasma/plasmamod.sip
 pykde4-4.14.3/sip/plasma/plasmamod.sip
+@@ -27,7 +27,6 @@
+ %Import QtGui/QtGuimod.sip
+ %Import QtNetwork/QtNetworkmod.sip
+ %Import QtSvg/QtSvgmod.sip
+-%Import QtWebKit/QtWebKitmod.sip
+ %Import QtXml/QtXmlmod.sip
+ %Import QtDeclarative/QtDeclarativemod.sip
+ %Import QtScript/QtScriptmod.sip
+@@ -116,5 +115,4 @@
+ %Include toolbutton.sip
+ %Include treeview.sip
+ %Include videowidget.sip
+-%Include webview.sip
+ %Include windoweffects.sip
+--- pykde4-4.14.3.orig/sip/plasma/webview.sip
 /dev/null
+@@ -1,93 +0,0 @@
+-// Copyright 2008 Simon Edwards 
+-
+-// Generated by twine
+-
+-// This program is free software; you can redistribute it and/or modify
+-// it under the terms of the GNU Library General Public License as
+-// published by the Free Software Foundation; either version 2, or
+-// (at your option) any later version.
+-
+-// This program is distributed in the hope that it will be useful,
+-// but WITHOUT ANY WARRANTY; without even the implied warranty of

Bug#800573: heimdall-flash: fails to download PIT for Galaxy S5 (G900T3)

[Mathias Behrle]

Package: heimdall-flash
Version: 1.4.1-2+b1
Followup-For: Bug #800573

I also just ran into the same problem, and can confirm that building from
the current release works for me (SM-G900F).

Please consider updating to version 1.4.2.


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

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

Versions of packages heimdall-flash depends on:
ii  libc6 2.24-12
ii  libgcc1   1:7.1.0-7
ii  libstdc++67.1.0-7
ii  libusb-1.0-0  2:1.0.21-2

heimdall-flash recommends no packages.

heimdall-flash suggests no packages.

-- no debconf information

Bug#862755: RFS: golang-github-go-ini-ini/1.27.0-1

[Félix Sipma]

Hi!

Sorry for the delay, I was offline during the last weeks.

On 2017-06-15 22:15+0200, Gianfranco Costamagna wrote:
> Hello,
> 
>>gbp clone --pristine-tar 
>> https://anonscm.debian.org/git/pkg-go/packages/golang-go-ini-ini.git
> 
> lets review (the mentors link)
> +golang-github-go-ini-ini (1.27.0-1) experimental; urgency=medium
> +
> +  * New upstream version 1.27.0
> +  * update Standards-Version and debhelper version
> +  * add myself to the uploaders
> +  * use https in the Vcs-Browser field
> +
> + -- Félix Sipma   Tue, 16 May 2017 16:22:10 +0200
> +
> +golang-github-go-ini-ini (1.8.6-3) unstable; urgency=medium
> +
> +  * Team upload.
> +  * Use a secure transport for the Vcs-Git and Vcs-Browser URL
> +
> + -- Paul Tagliamonte   Wed, 29 Jun 2016 20:21:03 -0400
> +
> 
> please merge the two changelog entries together

done

> please ask your comaintainers (in cc), if you can add yourself in uploaders 
> list

will do

>>2017/05/16 18:21:46 FAILED: grafana_2.6.0+dfsg-3 (see 
>> buildlogs/grafana_2.6.0+dfsg-3)
>>2017/05/16 18:21:46 FAILED: nomad_0.4.0+dfsg-1 (see 
>> buildlogs/nomad_0.4.0+dfsg-1)
>>2017/05/16 18:21:46 FAILED: packer_0.10.2+dfsg-5 (see 
>> buildlogs/packer_0.10.2+dfsg-5)
>>2017/05/16 18:21:46 FAILED: goiardi_0.11.4-1 (see 
>> buildlogs/goiardi_0.11.4-1)
>> 
>> grafana and nomad fails for unrelated reasons (see attached logs)
>> 
>> I don't get why goiardi and packer fail.
> 
> this should be sorted out before uploading in unstable, please ask upstream 
> or relative maintainers
> and fix this

not done yet... I also changed the target from experimental to unstable.

>> If the person who sponsors the upload could also give me upload permissions 
>> for
>> this package, that would be great!
> 
> after updating it, prod me if I forget :)
> 
> review:
> 
> +Vcs-Browser: 
> https://anonscm.debian.org/gitweb/?p=pkg-go/packages/golang-github-go-ini-ini.git;a=summary
> 
> please use cgit

done

> + ${misc:Depends},
> + golang-go
> 
> not mentioned in changelog

I just changed the indentation, this was already there :-).

> +version=3
> + https://github.com/go-ini/ini/releases \
> + .*/v?(\d[\d\.]*)\.tar\.gz
> 
> please mention in changelog

I have not done anything to this...

> and then we should be good :)
> 
> G.

Thanks for your review! Other people have expressed interest in getting an
updated restic in sid, so I hope to get help to fix the build failures... I've
uploaded the new package to mentors.


signature.asc
Description: PGP signature

Bug#867898: debian-installer-netboot-images: debian-installer-9-netboot-amd64 scsi modules missing. Netboot image unusable

[Cyril Brulebois]

Control: severity -1 important

Hi Robert & kernel maintainers,

Paschedag, Robert  (2017-07-10):
> Package: debian-installer-netboot-images
> Version: 20170615
> Severity: serious
> 
> Trying to perform a PXE installation with the debian 9 (stretch)
> netboot image and a Debian 9.0.0 Release DVD 1 (amd64) fails, because
> no disks get detected by the installer.
> 
> There are no "scsi" module .udeb files downloaded by the installer.
> Also the scsi-core-modules udeb package is missing on the realease
> image disk (DVD). I also cannot find it within your cd image search
> tool (https://cdimage-search.debian.org/). Searching
> "scsi-core-modules" does not find a package for the "amd64"
> architecture.

There's a udeb for amd64 anyway:
  
https://packages.debian.org/stretch/amd64/scsi-core-modules-4.9.0-3-amd64-di/download

It seems to be used to build the cdrom initramfses on the following archs:
| kibi@armor:~/debian-installer/installer/build$ git grep scsi-core-modules|sort
| pkg-lists/cdrom/alpha.cfg:scsi-core-modules-${kernel:Version}
| pkg-lists/cdrom/amd64.cfg:scsi-core-modules-${kernel:Version}
| pkg-lists/cdrom/arm64.cfg:scsi-core-modules-${kernel:Version}
| pkg-lists/cdrom/i386.cfg:scsi-core-modules-${kernel:Version}
| pkg-lists/hd-media/armhf.cfg:scsi-core-modules-${kernel:Version}

(That's in src:debian-installer)

So it looks to me we only need to have the extra module in this udeb, and
the release images will automatically get it.


> The installation has been tried on a simple VMware VM with the LSI
> logic parallel controller. The driver that is used is the "mptspi.ko"
> module. This module (and other scsi) modules are missing.)

Kernel maintainers (in copy): maybe this wasn't added to one of the scsi
udebs because the module is below the drivers/message/fusion directory?

Feel free to steal the bug report away from us if the required change is
just about shipping extra .ko('s) into your udebs.


KiBi.


signature.asc
Description: Digital signature

Bug#867890: apache-directory-jdbm FTBFS: patch

[Hans Joachim Desserud]

tags 867890 patch
thanks

Adding junit4 as a build dependency resolves the issue.
No further build dependencies needed (built successfully in pbuilder)

--
mvh / best regards
Hans Joachim Desserud
http://desserud.orgdiff --git a/debian/control b/debian/control
index cb1b1cc..f13bdc7 100644
--- a/debian/control
+++ b/debian/control
@@ -6,6 +6,7 @@ Uploaders: Emmanuel Bourg 
 Build-Depends: cdbs,
debhelper (>= 9),
default-jdk,
+   junit4,
libmaven-bundle-plugin-java,
libslf4j-java,
maven-debian-helper (>= 1.5)

Bug#867716: stretch-pu: package debsecan/0.4.19~deb9u1

[Cyril Brulebois]

Hi,

Salvatore Bonaccorso  (2017-07-08):
> Hi SRM, X-Debbug-CC'ed Florian Weimer
> 
> The upload of debsecan to unstable fixed two bugs with respect to
> 0.4.18 as in stretch. One is the use of https_proxy which is needed
> for proxy configuration with https:// URLs. This was #749424.
> 
> Then there was as well #789196, which adds support for stretch (and
> buster), as well to be choosen from the debconf menu.
> 
> Unfortunately the 0.4.18 source tarball, contained .git and some out
> files in testsuite. I'm attaching only the result from:
> 
> debdiff debsecan_0.4.18.dsc debsecan_0.4.19~deb9u1.dsc | filterdiff -x 
> '*/.git/*'
> 
> Alternatively if that's prefered, we can cherry pick the two commits
> and do a 0.4.18.1 upload, but doing a rebuild from 0.4.19 from
> unstable for stretch would resolve as well the .git and
> testsuite/*.out files.
> 
> Any preference on your end?

My first impression would be that your proposed approach (0.4.19~deb9u1)
is cleaner, but I'd welcome a second look from someone else.


KiBi.


signature.asc
Description: Digital signature

Bug#867964: systemd: dhcp ips are not renewed after waking up from hibernation

[alberto fuentes]

I filed to systemd because these files

/lib/systemd/system/systemd-hibernate-resume@.service
/lib/systemd/system/systemd-hibernate.service

belong to systemd

I did mentioned '/var/lib/dhcp/dhclient.leases' but im not sure who is in
charge of renewing ips or what file are used

I understand systemd services are in charge of bring up the network
interfaces... and as it is in charge of the hibernation service as well,
shouldnt it be in charge of renew the ip if its due after waking up?

Probably this bug happens because nobody took responsibility of renewing
the ip if the computer is not up when it expires

/var/lib/dhcp belongs to isc-dhcp-client

Please, could you help me find out whose package this bug should be
redirected to instead of closing it? Probably isc-dhcp-client if this
problem is not systemds


On Mon, Jul 10, 2017 at 7:45 PM, Michael Biebl  wrote:

> Am 10.07.2017 um 19:30 schrieb Alberto Fuentes:
> > Package: systemd
> > Version: 233-9
> > Severity: normal
> >
> > After waking up from hibernation I expect the system to check
> > /var/lib/dhcp/dhclient.leases and renew ip if needed
> >
> > It does not loses connection, since the old ip still works, but dhcp-dns
> server
> > doesnt know about the computer because it doesnt renew
>
> This bug is misfiled. systemd is not involved with
> /var/lib/dhcp/dhclient.leases
>
>
> --
> Why is it that all of the instruments seeking intelligent life in the
> universe are pointed away from Earth?
>
>

Bug#867961: osc: Uses deprecated python-gnomekeyring

[Michal Čihař]

Hello

bi...@debian.org píše v Po 10. 07. 2017 v 18:42 +0200:
> Source: osc
> Version: 0.156.0-1
> Severity: important
> User: pkg-gnome-maintain...@lists.alioth.debian.org
> Usertags: oldlibs libgnome-keyring-removal python-gnomekeyring
> 
> Hi,
> 
> The libgnome-keyring library is deprecated and its usage is strongly
> discouraged [1].
> 
> Your package osc recommends or suggests python-gnomekeyring.

Already reported by you as #844158 (and fixed in Git).

-- 
Michal Čihař | https://cihar.com/ | https://weblate.org/


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

Bug#866511: kernel BUG at nvme/host/pci.c

[Ben Hutchings]

On Mon, 2017-07-10 at 17:30 +0200, Andreas Pflug wrote:
> Bug reported upstream as https://bugzilla.kernel.org/show_bug.cgi?id=196315

That seems to be the wrong place.  "Flash/Memory Technology Devices" is
for host-managed flash chips, not high-level interfaces like NVMe.  It
doesn't look like nvme driver bugs are accepted through Bugzilla.  Try
sending mail to linux-n...@lists.infradead.org instead.

Ben.

-- 
Ben Hutchings
Absolutum obsoletum. (If it works, it's out of date.) - Stafford Beer


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

Bug#867964: systemd: dhcp ips are not renewed after waking up from hibernation

[Alberto Fuentes]

Package: systemd
Version: 233-9
Severity: normal

After waking up from hibernation I expect the system to check
/var/lib/dhcp/dhclient.leases and renew ip if needed

It does not loses connection, since the old ip still works, but dhcp-dns server
doesnt know about the computer because it doesnt renew

Thanks for considering



-- Package-specific info:

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

Kernel: Linux 4.9.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)

Versions of packages systemd depends on:
ii  adduser 3.115
ii  libacl1 2.2.52-3+b1
ii  libapparmor12.11.0-6
ii  libaudit1   1:2.7.7-1+b1
ii  libblkid1   2.29.2-1
ii  libc6   2.24-12
ii  libcap2 1:2.25-1
ii  libcryptsetup4  2:1.7.3-4
ii  libgcrypt20 1.7.8-1
ii  libgpg-error0   1.27-3
ii  libidn111.33-1
ii  libip4tc0   1.6.1-2
ii  libkmod224-1
ii  liblz4-10.0~r131-2+b1
ii  liblzma55.2.2-1.2+b1
ii  libmount1   2.29.2-1
ii  libpam0g1.1.8-3.6
ii  libseccomp2 2.3.1-2.1
ii  libselinux1 2.6-3+b2
ii  libsystemd0 233-9
ii  mount   2.29.2-1
ii  procps  2:3.3.12-3
ii  util-linux  2.29.2-1

Versions of packages systemd recommends:
ii  dbus1.10.20-1
ii  libpam-systemd  233-9

Versions of packages systemd suggests:
ii  policykit-10.105-18
pn  systemd-container  

Versions of packages systemd is related to:
pn  dracut   
ii  initramfs-tools  0.130
ii  udev 233-9

-- no debconf information

Bug#866026: volunteer for pygpgme to python[3]-gpg pivot

[Mike Gabriel]

Hi,

On  Do 06 Jul 2017 06:41:08 CEST, draeath wrote:


One month does not seem like a lot of turnaround time for this. Does this
package have an active maintainer? I'm willing to look into updating this
and providing a patch, but I might need some handholding on the process
side. (I'm familiar with casual site-local usage of debuild, but I do not
currently have a PGP key I can readily sign anything with)

This would be my first time contributing more than bug reports.

I'd imagine this package does see some use, as it's currently the only good
way to hook Dropbox into the Mate desktop without dragging a whole lot of
gnome3 components along for the ride.

Regards,
Paul Bransford


Please go ahead, Paul. Don't know how many of us devs are active  
caja-dropbox users. I don't particularly like Dropbox, so I avoid  
using it.


I'd be greatful, if you could get this issue resolved, as caja-dropbox  
is a nice to have for many non-geek users.


Thanks and looking forward to here back from you. If you won't take up  
this task, please drop a note to the bug, thanks.


Mike
--

DAS-NETZWERKTEAM
mike gabriel, herweg 7, 24357 fleckeby
mobile: +49 (1520) 1976 148
landline: +49 (4354) 8390 139

GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22  0782 9AF4 6B30 2577 1B31
mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de



pgpLmN7e22ywI.pgp
Description: Digitale PGP-Signatur

Bug#862696: transition: cppunit

[Rene Engelhard]

Hi,

On Mon, Jul 10, 2017 at 05:44:22PM +0200, Emilio Pozuelo Monfort wrote:
> Control: tags -1 confirmed
> 
> On 10/07/17 16:50, Rene Engelhard wrote:
> > a status update:
> 
> Thanks, it all sounds good now, please go ahead.

OK; uploaded.

> >> retitle 862133 src:gnuradio: FTBFS with cppunit 1.14 (no C++11 support, 
> >> required by cppunit)
> > 
> > Reintroduced cppunit1.13 for it...
> 
> > Can NMU those with Patch available and do a "Team upload" for drumgizmo. 
> > Wonder what we should
> > do with gnuradio? Keep cppunit1.13? Disable the tests?
> 
> I wouldn't reintroduce cppunit1.13 just for this. Bump the severity to serious
> and propose to disable the tests until it gets ported upstream, I'd say.

Mmh, OK.

Regards,

Rene

Bug#867963: symlinks to bootstrap.min and jquery.min do not work

[Don Armstrong]

Package: r-cran-shiny
Severity: normal
Control: tag -1 patch

resolve() (utils.R) will not resolve paths which aren't subdirectories
of www/shared, which breaks the inclusion of CSS, etc. by default.

The attached hack fixes this; perhaps upstream may want to make a more
general method to make resolve() more granular, but for the time being,
this should work.

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

If a nation values anything more than freedom, it will lose its
freedom; and the irony of it is that if it is comfort or money it
values more, it will lose that, too.
 -- W. Somerset Maugham
Description: Hack for symlinks to twitter-bootstrap and javascript
 Also allow serving /usr/share/javascript and
 /usr/share/twitter-boostrap/ from shiny apps by default
Author: Don Armstrong 
Origin: vendor
Bug-Debian: unfiled
Forwarded: not-needed
Last-Update: 2017-07-10
---
This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
--- a/R/utils.R
+++ b/R/utils.R
@@ -298,6 +298,12 @@
   dir <- normalizePath(dir, winslash='/', mustWork=TRUE)
   # trim the possible trailing slash under Windows (#306)
   if (isWindows()) dir <- sub('/$', '', dir)
+  ## Debian specific hack for /usr/share/javascript symlinks
+  if 
(substr(abs.path,1,nchar('/usr/share/javascript/'))=='/usr/share/javascript/')
+  return(abs.path)
+  ## Debian specific hack for /usr/share/twitter-bootstrap symlinks
+  if 
(substr(abs.path,1,nchar('/usr/share/twitter-bootstrap/'))=='/usr/share/twitter-bootstrap/')
+  return(abs.path)
   if (nchar(abs.path) <= nchar(dir) + 1)
 return(NULL)
   if (substr(abs.path, 1, nchar(dir)) != dir ||

Bug#862125: cppunit 1.14 now in unstable

[Rene Engelhard]

severity 862135 serious
severity 862134 serious
severity 862133 serious
severity 862132 serious
severity 862131 serious
severity 862130 serious
severity 862129 serious
severity 862128 serious
severity 862127 serious
severity 862126 serious
severity 862125 serious
thanks

Hi,

cppunit 1.14 is now in unstable; thus raising the severity of these bugs
to serious.

I intend to NMU very soon.

For gnuradio and ola:

gnuradio will not be able to build against cppunit 1.14 as 1.14 requires c++11.
I pondered introducing cppunit1.13 and actually did so but the RT 
(understandably)
doesn't want two versions of cppunit.

So if that stays as-is you either need to 
 - port gnuradio to supporting building with c++11
 - disable the testsuite

Same for ola, though that one's fixed-upstream and just needs a actual release
to support cppunit 1.14...

Regards,

Rene

Bug#867853: closed by Gianfranco Costamagna <locutusofb...@debian.org> (Re: Bug#867853: gcc: error: unrecognized command line option ‘-no-pie’)

[Brian Sammon]

On Mon, 10 Jul 2017 16:50:03 + (UTC)
Gianfranco Costamagna  wrote:

> updating control file, adding version constraints with versions not in the > 
> archive anymore is kind of useless, speaking about Buster we won't have suc
> gcc versions anymore since at least two stable releases.

Hmmm... the gcc packages involved (gcc 4.9.2-4 and gcc-5 5.2.1-23) are 
definitely newer than Jessie -- I would think that means they're "technically" 
Stretch, but I'm not too clear on debian policies.

> >Last question:
> >If I contribute a patch to the debian/control file to do this, would it 
> get applied?
> 
> nobody complained so far about this issue, so you are probably one of the > 
> few people not updating their compiler :)
> 
> I'm really not sure this is worth the effort

Well, I don't think it's much effort, and I'm (still) volunteering to 
contribute most of the effort.
I'm not sure waiting until more people have a problem with this is the way to 
go.  And of course, not everyone who has a problem will complain (or will 
complain somewhere that you would hear them)

Bug#867853: closed by Gianfranco Costamagna <locutusofb...@debian.org> (Re: Bug#867853: gcc: error: unrecognized command line option ‘-no-pie’)

[Gianfranco Costamagna]

Hello,




>I'm not sure I understand this response.
>
>When you say "gcc-specific", are you saying that the Debian Haskell package 
>supports compilers other than gcc?  It appears to me that it specifically 
>requires gcc.


I mean, that the flag has been added by gcc, and a lot of programs in the 
archive are supplying it to the build, with a backward incompatible
change.

e.g. you can think about all the -dkms packages, because pie is something that 
the kernel can't use.

So, instead of patching every single control file of a tool using no-pie, I 
would suggest to patch gcc if there still are supported configurations
without the -f-no-pie switch.
(I mean, implement that switch and do nothing when used)

>When you say "fix the whole archive" what do you mean?


the above :)
>I suggest only a update to the "debian/control" file to prevent/discourage 
>users from trying to use ghc with older, unsupported compilers.


updating control file, adding version constraints with versions not in the 
archive anymore is kind of useless, speaking about Buster we won't have such
gcc versions anymore since at least two stable releases.
>Last question:

>If I contribute a patch to the debian/control file to do this, would it get 
>applied?

nobody complained so far about this issue, so you are probably one of the few 
people not updating their compiler :)

I'm really not sure this is worth the effort

G.

Bug#867804: cdrom: Stretch netinst CD installs grub config file incorrectly

[Steve McIntyre]

Control: reassign -1 grub-common

On Mon, Jul 10, 2017 at 05:27:08PM +0100, Steve McIntyre wrote:
>
>>The Debian partition is sda7, formatted ext4. I created it in partman
>>during the installation. As far as I can see from today's explorations,
>>installation has been fine except for this one glitch, which was more of
>>an irritation than a serious problem. I've attached the installation
>>syslog to this email.
>
>Thanks, I'm looking at it now to see if there's anything obvious.

OK, I can see you have lots of OSes installed on your computer. I can
see os-prober parsing lilo config files from other installations. :-)

What I *don't* see is any indication of any failures, though. Instead,
grub-install claims to have succeeded:

Jul  8 07:42:53 grub-installer: info: Installing grub on '/dev/sda'
Jul  8 07:42:53 grub-installer: info: grub-install does not support --no-floppy
Jul  8 07:42:53 grub-installer: info: Running chroot /target grub-install  
--force "/dev/sda"
Jul  8 07:42:54 grub-installer: Installing for i386-pc platform.
Jul  8 07:43:05 grub-installer: Installation finished. No error reported.
Jul  8 07:43:05 grub-installer: info: grub-install ran successfully

I'm wondering if *maybe* something has been confused by those lilo
setups, but I'll admit that I'm not sure what's happening there.

>>I normally prefer lilo to grub, so I reinstalled lilo from one of my
>>other Linuxen, but I could do a grub-install in Debian to test out the
>>grub.cfg file, which I've now renamed. Would you like me to do that?
>
>I'll get back to you...

Yes please, that might be very helpful. Run as

 "grub-install -v /dev/sda"

and capture the output please?

-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
  Armed with "Valor": "Centurion" represents quality of Discipline,
  Honor, Integrity and Loyalty. Now you don't have to be a Caesar to
  concord the digital world while feeling safe and proud.

Bug#867962: setserial: legacy files not cleaned up correctly

[Christoph Anton Mitterer]

Package: setserial
Version: 2.17-50
Severity: normal


Hi.

Both in sid and stable (as upgraded from oldstable).

setserial apparently once had:
/etc/modutils/setserial
as config file:
# dpkg -S /etc/modutils/setserial
setserial: /etc/modutils/setserial

(and not /etc/modutils).

Now /etc/modutils was apparently dropped, but not the conffile, whic
leads to:
Unpacking setserial (2.17-50) over (2.17-48) ...
dpkg: warning: unable to delete old directory '/etc/modutils': Directory not 
empty

Could you clean this please up in one of the next
versions for sid and stretch?

Cheers,
Chris.

Bug#867853: closed by Gianfranco Costamagna <locutusofb...@debian.org> (Re: Bug#867853: gcc: error: unrecognized command line option ‘-no-pie’)

[Brian Sammon]

> I guess it is better to patch older gccs to understand such flag and give
> no-op in this case.
> There is no point in:
> 1) fixing the whole archive for a gcc-specific change
> 2) using ghc with older, unsupported compilers.

I'm not sure I understand this response.
When you say "gcc-specific", are you saying that the Debian Haskell package 
supports compilers other than gcc?  It appears to me that it specifically 
requires gcc.

When you say "fix the whole archive" what do you mean?
I suggest only a update to the "debian/control" file to prevent/discourage 
users from trying to use ghc with older, unsupported compilers.

Last question:
If I contribute a patch to the debian/control file to do this, would it get 
applied?

Bug#867311: Info received (Log from a jessie system (gdm3-3.14.1-7))

[John Hughes]

Further debugging by printf shows that:

On Jessie when libpam_krb5 gets to "pam_sm_setcred: entry (reinit)" the 
ticket cache name is in the environment (KRB5CCNAME) (the real 
environment, not the PAM args one).


On Stretch at the same place KRB5CCNAME is unset.

Bug#867210: Pending fixes for bugs in the libtext-mecab-perl package

[pkg-perl-maintainers]

tag 867210 + pending
thanks

Some bugs in the libtext-mecab-perl package are closed in revision
1355fe48ad091faa29a0ded81b34da47c4261093 in branch 'master' by gregor
herrmann

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-perl/packages/libtext-mecab-perl.git/commit/?id=1355fe4

Commit message:

Build-depend on mecab-jumandic >= 7.0-20130310-3 (cf. #867689).

Closes: #867210