Bug#833322: maint-guide: don't suggest low urgency for uploads of new packages

[Paul Hardy]

Also, FWIW, "low" urgency packages are now only held in unstable for 5
days before migrating, not 10 days.  I don't know whether this is
temporary or permanent.  If permanent, there isn't much of a reason
for "low" urgency anymore.

I recently prepared a package and set the urgency to "low" because I
made changes in a number of source code files all at once to support a
data file structure change.  I intended the package to sit in
"unstable" for 10 days to give time for any catastrophic error to
surface, which is how I discovered this.

I just mentioned this as an aside at the end of bug report #868281 but
figured I should also add that info to this bug report.


Thanks,


Paul Hardy

Bug#868277: maint-guide: Typos, Typography, and Grammar Patches

[Paul Hardy]

Because there are so many patches in the original attachment for this
bug report, I am attaching a GPG signature of the gzipped patch file
in this message for verification.

Thanks,


Paul Hardy


doc-patches.txt.gz.sig
Description: PGP signature

Bug#867231: stretch-pu: package openstack-debian-images/1.19

[Adam D. Barratt]

Control: tags -1 + confirmed

On Wed, 2017-07-05 at 10:41 +0200, Thomas Goirand wrote:
> On 07/05/2017 07:42 AM, Cyril Brulebois wrote:
> >> As usual, please provide a debdiff of the proposed source package,
> >> built and tested on stable, so that it can be confirmed.
> > 
> > Yeah, following the usual procedure, that has existed for years, *will*
> > save everyone time. Please do that.
> 
> Sorry for this, my bad. Debdiff attached for version 1.20~deb9u1 built
> on a stretch sbuild chroot. The built package is available here:
> 
> http://sid.gplhost.com/stretch-proposed-updates/openstack-debian-images/

Thanks.

+openstack-debian-images (1.20~deb9u1) stretch-proposed-updates; urgency=medium

Simply "stretch" is generally preferred there.

Please go ahead, bearing in mind that the upload window for 9.1 closes
over this weekend.

Regards,

Adam

Bug#868282: virtualbox-dkms: kernel modules fail to build due to missing files

[James Lu]

Hi everyone,

I ran into this issue today as well and can confirm that downgrading to
virtualbox-dkms 5.1.22-dfsg-2 fixes it.

Best,
James



signature.asc
Description: OpenPGP digital signature

Bug#868194: Stop building python3-trollius-redis

[Michael Hudson-Doyle]

On 13 July 2017 at 13:46, Sergio Durigan Junior 
wrote:

> On Wednesday, July 12 2017, Michael Hudson-Doyle wrote:
>
> > Hi,
> >
> > trollius does not build with Python 3.6 as a supported version and is
> > deprecated upstream. The sensible way forward seems to be to stop
> building
> > python3-trollius and the only non-trivial dependency on that
> > is python3-trollius-redis. I think it makes sense to stop
> > building python3-trollius-redis too, on the assumption that as and when
> > pagure moves to Python 3, it will move to asyncio-redis as part of that.
> >
> > Cheers,
> > mwh
>
> Thanks for the bug report.  I'll take care of this ASAP.


 I just noticed that my patch neglected to remove the python3
build-dependencies...

Cheers,
mwh

Bug#868150: imapproxy: fails to start

[Richard Laager]

Is the PIDFile line actually necessary for you? Can you re-test without
the PIDFile line in the service?

With that line, I get additional errors/warnings. Without it, systemd is
still able to detect the main PID of the process.

On 07/13/2017 02:52 AM, Marc Dequènes (duck) wrote:
> So better would be to change the path where the pidfile is created, but
> you can do this when you have time.

Sure, that's trivial. I have that change ready.

> Search the word "Thanks" in /usr/share/doc/dpkg/changelog.Debian.gz for
> plenty of examples.

gbp-dch supports a Thanks meta tag, which has this result, so that seems
like the correct answer.

> Also please use "Marc Dequènes (Duck)".

Noted and done.

-- 
Richard

Bug#866938: ITA: note -- small program managing notes from commandline

[Simon Quigley]

Control: retitle -1 ITA: note -- small program managing notes from commandline
Control: owner -1 tsimo...@ubuntu.com

I would like to adopt this package, as upstream has released a few new versions 
that should be included in Debian.

Bug#843207: ITP: man2texi -- man page to texinfo file converter

[Paul Hardy]

This is a status update.  With the Stretch release, work is picking up
on this ITP again.

I have send Nelson Beebe some files he requested for testing with the
latest version of texinfo.  I will be continuing to work with him on
getting a new and improved man2texi into Debian that carries his
approval.

Thanks,


Paul Hardy

Bug#868282: virtualbox-dkms: kernel modules fail to build due to missing files

[Jon]

Package: virtualbox-dkms
Version: 5.1.22-dfsg-3
Severity: grave
Justification: renders package unusable

Dear Maintainer,

My apologies if I misjudged the impact, but I'm pretty sure this
failure is universal.

4 files are missing from the virtualbox-source and virtualbox-dkms
packages that render the driver unbuildable. These files were present in
5.1.22-dfsg-2 but are now missing in 5.1.22-dfsg-3.

./include/VBox/vmm/cpumctx.h
./include/VBox/vmm/hm_svm.h
./include/VBox/vmm/hm_vmx.h
./include/VBox/vmm/pdmnetinline.h

(The full path varies between the -dkms and -source package variants,
but they are missing in both)

Here is the DKMS log against 4.9.0-3-amd64. DKMS against 4.11.0-1-amd64
and manual building via virtualbox-source against 4.9.0-3-amd64 get the
same result.

DKMS make.log for virtualbox-5.1.22 for kernel 4.9.0-3-amd64 (x86_64)
Thu Jul 13 22:18:58 EDT 2017
make: Entering directory '/usr/src/linux-headers-4.9.0-3-amd64'
  LD  /var/lib/dkms/virtualbox/5.1.22/build/built-in.o
  LD  /var/lib/dkms/virtualbox/5.1.22/build/vboxdrv/built-in.o
  CC [M]  /var/lib/dkms/virtualbox/5.1.22/build/vboxdrv/linux/SUPDrv-linux.o
  CC [M]  /var/lib/dkms/virtualbox/5.1.22/build/vboxdrv/SUPDrv.o
  CC [M]  /var/lib/dkms/virtualbox/5.1.22/build/vboxdrv/SUPDrvGip.o
  CC [M]  /var/lib/dkms/virtualbox/5.1.22/build/vboxdrv/SUPDrvSem.o
/var/lib/dkms/virtualbox/5.1.22/build/vboxdrv/SUPDrv.c:67:29: fatal error: 
VBox/vmm/hm_vmx.h: No such file or directory
 #include 
 ^
compilation terminated.
/usr/src/linux-headers-4.9.0-3-common/scripts/Makefile.build:298: recipe for 
target '/var/lib/dkms/virtualbox/5.1.22/build/vboxdrv/SUPDrv.o' failed
make[4]: *** [/var/lib/dkms/virtualbox/5.1.22/build/vboxdrv/SUPDrv.o] Error 1
make[4]: *** Waiting for unfinished jobs
/usr/src/linux-headers-4.9.0-3-common/scripts/Makefile.build:549: recipe for 
target '/var/lib/dkms/virtualbox/5.1.22/build/vboxdrv' failed
make[3]: *** [/var/lib/dkms/virtualbox/5.1.22/build/vboxdrv] Error 2
/usr/src/linux-headers-4.9.0-3-common/Makefile:1507: recipe for target 
'_module_/var/lib/dkms/virtualbox/5.1.22/build' failed
make[2]: *** [_module_/var/lib/dkms/virtualbox/5.1.22/build] Error 2
Makefile:150: recipe for target 'sub-make' failed
make[1]: *** [sub-make] Error 2
Makefile:8: recipe for target 'all' failed
make: *** [all] Error 2
make: Leaving directory '/usr/src/linux-headers-4.9.0-3-amd64'


I downgraded virtualbox-dkms to 5.1.22-dfsg-2 and the drivers build succesfully.


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

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

Versions of packages virtualbox-dkms depends on:
ii  dkms  2.3-3

Versions of packages virtualbox-dkms recommends:
ii  virtualbox  5.1.22-dfsg-3

virtualbox-dkms suggests no packages.

-- no debconf information

Bug#843207: ITP: man2texi -- man page to texinfo file converter

[Paul Hardy]

This is a status update.  With Debian 9 ("Stretch") released, I am
picking up work on this ITP again.

I have sent Nelson Beebe some files he requested for testing with the
latest version of texinfo.  I will be continuing to work with him on
getting a version of man2texi into Debian that carries his approval.

Thanks,


Paul Hardy

Bug#868281: maint-guide: Priority "extra" is gone

[Paul Hardy]

Package: maint-guide
Version: 1.2.39
Severity: normal

--

The maint-guide package mentions (and recommends) using priority
"extra" in several places, with examples.  The FTP Masters have
removed this priority.  If a package is loaded with priority "extra"
now, that will generate a lintian warning.

Please consider changing priority "extra" to priority "optional"
wherever it appears in the maint-guide package.

Also, the maint-guide package mentions using urgency "low".  Be aware
that "low" urgency only seems to leave packages in unstable now for 5
days, not 10 days.  I don't know if that is a temporary change or is
permanent.  If a permanent change, you might also consider changing
the text to use "normal" urgency.

Thanks,


Paul Hardy

Bug#864650: transition: mumps

[Drew Parsons]

On Tue, 2017-06-27 at 18:51 +0100, Jonathan Wiltshire wrote:
> On Mon, Jun 26, 2017 at 09:10:17PM +0800, Drew Parsons wrote:
> > 
> > That's right.  But it makes it simpler for stable users to just
> > grab
> > dolfin 2016.2.0-4 from snapshot archives if it hasn't been built
> > against new libraries like mumps 5.1.  Minimises the number of
> > codependent packages they'd have to pull in.
> 
> In that case, please come back when you're ready to proceed, in case
> there
> is by then a collision with another transition.

I'm happy with the state of dolfin in testing now.  I'd like to proceed
with the MUMPS 5.1 transition now.

Since petsc and slepc will be rebuilt as part of the mumps transition
anyway, I'll also upgrade petsc 3.7.6 and slepc 3.7.4. These are not a
true transition since their soname does not change.

Drew

Bug#868279: maint-guide: deprecated "--force-yes" apt-get option in pbuilder hooks script

[Paul Hardy]

Package: maint-guide
Version: 1.2.39
Severity: wishlist

--

In Chapter 6 of the maint-guide package, the B90lintian hooks script
for pbuilder contains the line

apt-get -y --force-yes install "$@"

The "--force-yes" option is deprecated; apt-get recommends replacing
it with one of the "--allow-*" options.  However, the apt-get man page
warns that all of those options are "dangerous".

The example B90lintian script in
/usr/share/doc/pbuilder/examples/B90lintian simply omits the
"--force-yes" option and does not replace it with an "--allow-*'
option.

Please consider just removing the "--force-yes" option in the
B90lintian example in maint-guide Chapter 6.

Thanks,


Paul Hardy

Bug#868280: torbrowser-launcher: after update torbrowser-launcher doesn't work, the binary is not in its place.

[shirish शिरीष]

Package: torbrowser-launcher
Version: 0.2.7-2
Severity: grave
Justification: renders package unusable

Dear Maintainer,

Thank you for maintaining torbrowser-launcher as long as you have. As
a privacy advocate and user, I appreciate the security the browser
brings.

I had been ill for a while and then few days I started the launcher
and came to know that the browser was out of date. I updated it and
then was unable to start it.

It seems that the path has been changed to -

/home/shirish/.local/share/torbrowser/tbb/x86_64/tor-browser_en-US/start-tor-browser.desktop

Trying to run that either as an alias or via console I get the following -

┌─[shirish@debian] -
[~/.local/share/torbrowser/tbb/x86_64/tor-browser_en-US] - [10018]
└─[$] ./start-tor-browser.desktop
Launching './Browser/start-tor-browser --detach'...
./Browser/execdesktop: line 14: ./Browser/start-tor-browser: No such
file or directory

So it seems that the file/executable/binary has been deleted.

One option I have is purging torbrowser-launcher and start afresh but
would await further instructions from you before trying that out. I do
have a backup of all the usernames and passwords for websites that I
might need.

Look forward to knowing (if any debugging can be done) what to do next
before purging and reinstalling and seeing if the browser works.

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

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

Versions of packages torbrowser-launcher depends on:
ii  ca-certificates  20161130+nmu1
ii  gnupg2.1.18-8
ii  python   2.7.13-2
ii  python-gtk2  2.24.0-5.1
ii  python-lzma  0.5.3-3
ii  python-parsley   1.2-1
ii  python-psutil5.0.1-1+b1
ii  python-twisted   16.6.0-2
ii  python-txsocksx  1.15.0.2-1
ii  wmctrl   1.07-7+b1

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

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

-- no debconf information


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

Bug#868278: maint-guide: Please Recommend Debhelper 10

[Paul Hardy]

Package: maint-guide
Version: 1.2.39
Severity: wishlist

--

Debhelper 10 is now in stable.  Please consider updating maint-guide
to recommend its use in debian/control and debian/compat instead of
using Debhelper 9.  See debhelper(7) and
https://nthykier.wordpress.com/2016/09/11/debhelper-10-is-now-available/.

Thanks,


Paul Hardy

Bug#868277: maint-guide: Typos, Typography, and Grammar Patches

[Paul Hardy]

Package: maint-guide
Version: 1.2.39
Severity: normal
Tags: patch

--

I have read the Maintainer's Guide, and while reading it also
proofread it.  The patch file addresses typos and some grammar (such
as "which" versus "that").  I also made some typography-related
changes:

"..." became a horizontal ellipsis ("" aka Unicode code point U+2026)

"-" became, according to context, an en-dash ("" aka U+2013),
an em-dash ("" aka U+2014), or remained a hyphen.

The HTML5 entities for the above symbols are not defined in the
maint-guide files; for reference, they are:

U+2026: 
U+2013: 
U+2014: 

See, for example, "https://www.w3schools.com/charsets/ref_utf_punctuation.asp;.

If not a huge effort, it would be good to add XML entities defining
those code points to match their HTML5 entity definitions, since
maint-guide uses them frequently.

On the various types of dashes, a good reference is _The TeXbook_ by
Donald Knuth.  On p. 4 of my copy, he says:

"Book printing differs significantly from ordinary typing with respect
to dashes, hyphens, and minus signs.  In good math books, these
symbols are all different; in fact there usually are at least four
different symbols:

 a hyphen (-);
 an en-dash (–);
 an em-dash (—);
 a minus sign (−).

"Hyphens are used for compound words like 'daughter-in-law' and
'X-rated'.  En-dashes are used for number ranges like 'pages 13–34',
and also in contexts like 'exercise 1.26–52'.  Em-dashses are used for
punctuation in sentences—they are what we often call simply dashes.
And minus signs are used in formulas."


If more convenient, I could send an attachment of the entire gzipped
"doc-new" directory.  There are over 100 changes, and all the chapters
are modified.  I have not changed anything substantive, but will file
a couple of non-typo-related bugs for other aspects of maint-guide.

Thanks,


Paul Hardy


doc-patches.txt.gz
Description: GNU Zip compressed data

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

[Christoph Anton Mitterer]

Just one more thing:

You used "/etc/systemd/network/dmz.link"

Wouldn't it be better to use something like 10-dmz.link?

Otherwise people may choose a name which is lexically after
/lib/systemd/network/99-default.link


Cheers,
Chris.

smime.p7s
Description: S/MIME cryptographic signature

Bug#826008: xserver-xorg-input-multitouch -- new version available

[Nobuhiro Iwamatsu]

Hi,

2017-05-17 10:05 GMT+09:00 Nicholas D Steeves :
> Hi Nobuhiro,
>
> On Mon, May 08, 2017 at 08:10:59AM +0900, Nobuhiro Iwamatsu wrote:
>> Hi,
>>
>> 2017-05-03 7:11 GMT+09:00 Nicholas D Steeves :
>> > Control: retitle -1 xserver-xorg-input-multitouch -- new version available
>> >
>>
>> Current installed vetsion is 1.0~rc2+git20110312-2, not 1.0~rc2.
>> This version includes following commit:
>>
>> > git log --pretty=oneline v1.0-rc2..v1.0-rc3
>> > 55ab6c4ecb43e6f2ec34b36533ef308d00a709e4 xf86-input-multitouch v1.0-rc3
>> > 4d87c041f6a232aa30528d70d4b9946d1824b4ed Four finger swipes in multitouch
>> > afbbc4b9470869933223e3970c7a63f1c52c1d69 Makefile: make LIBDIR configurable
>> > 161026ce49526593d0ebfd96a7c087e3e1b0f9f5 Add missing thumb reset at state 
>> > extraction
>> > 1db2e14bed379bbf1c5f3140a903437b146c5cce Fix event flood in tap handling
>> > a12ed738095819beab0b42c6c8a1566c063bb79e Support XINPUT 12
>
> So 1.0~rc2+git20110312-2 is equivalent to upstream's rc3 and includes
> these six commits?

Yes.

>
>> > Are these features available using another driver?  Given how I've
>> > seen Macbook powerusers use their touchpads, four finger swipes are
>> > fairly important.  Also, what is the severity of missing XINPUT 12
>> > support?
>> >
>>
>> We can use xserver-xorg-input-mtrack instead of 
>> xserver-xorg-input-multitouch.
>> Could you use xserver-xorg-input-mtrack?
>
> I had to read up on the mtrack driver.  Yes, from what I've been able
> to find it would work.  Is it an upstream fork of
> xserver-xorg-input-multitouch?

Yes, mtrack driver forked from multitouch.

> I'll have to ask my Macbook using
> friends to test this, because I only have an old Thinkpad.
> Unfortunately this also means I can't responsibly write Debian on
> Macbook documentation either.
>
> If git20110312 is really rc3 than this bug be closed, but if
> xserver-xorg-input-multitouch isn't depreciated (and replaced) by
> xserver-xorg-input-mtrack then I think our wiki would benefit from an
> explanation of when it's better (or necessary) to use one rather than
> the other.
>
> https://wiki.debian.org/SynapticsTouchpad
>
> A really nice document:
> https://wiki.archlinux.org/index.php/Mac#Touchpad
>
> Configuration example for xserver-xorg-input-multitouch that is
> apparently feels very similar to OS X:
> https://ubuntuforums.org/showthread.php?t=1334696=36=10557093#post10557093
>

The multitouch driver can not set detailed settings compared with mtrack.
I don't have a Thinkpad, but I am using this driver on my Macbook.

By the way, as Debian 9 was released, I plan to immediately upload RC
3 to unstable.
Please contact me if you want to use this in stable. I will upload
this to backports.

> Sincerely,
> Nicholas
>
> P.S. Please CC Bug #826008 and me

Best regards,
  Nobuhiro

-- 
Nobuhiro Iwamatsu
   iwamatsu at {nigauri.org / debian.org}
   GPG ID: 40AD1FA6

Bug#839621: libmojolicious-plugin-renderfile-perl: clashes w/libm-p-basicauth-perl over M::P::README(3pm)

[Hideki Yamane]

On Sun, 02 Oct 2016 23:14:56 -0400 "Aaron M. Ucko"  wrote:
> libmojolicious-plugin-renderfile-perl is impossible to install
> alongside libmojolicious-plugin-basicauth-perl because both
> (inappropriately) duplicate their actual man page as
> Mojolicious::Plugin::README(3pm):
>
>   dpkg: error processing archive 
> /.../libmojolicious-plugin-renderfile-perl_0.10-1_all.deb (--unpack):
>trying to overwrite 
> '/usr/share/man/man3/Mojolicious::Plugin::README.3pm.gz', which is also in 
> package libmojolicious-plugin-basicauth-perl 0.08-1
>
> Could you please take a look?  Meanwhile, I see *README pages
> in a number of other packages, and will file a Lintian bug accordingly.


$ apt-file search /usr/share/man/man3/Mojolicious::Plugin::README.3pm.gz
libmojolicious-plugin-basicauth-perl:
/usr/share/man/man3/Mojolicious::Plugin::README.3pm.gz
libmojolicious-plugin-renderfile-perl:
/usr/share/man/man3/Mojolicious::Plugin::README.3pm.gz

It should be
libmojolicious-plugin-basicauth-perl:
/usr/share/man/man3/Mojolicious::Plugin::basicauth::README.3pm.gz

and

libmojolicious-plugin-renderfile-perl:
/usr/share/man/man3/Mojolicious::Plugin::renderfile::README.3pm.gz


Both packages have README.pod, not README, and renaming it to README
fix this issue.



Makefile says
--
(snip)
manifypods : pure_all  \
README.pod \
lib/Mojolicious/Plugin/RenderFile.pm
$(NOECHO) $(POD2MAN) --section=$(MAN3EXT) --perm_rw=$(PERM_RW) -u \
  README.pod $(INST_MAN3DIR)/Mojolicious::Plugin::README.$(MAN3EXT) \
  lib/Mojolicious/Plugin/RenderFile.pm
$(INST_MAN3DIR)/Mojolicious::Plugin::RenderFile.$(MAN3EXT)
(snip)
--

README.pod $(INST_MAN3DIR)/Mojolicious::Plugin::README.$(MAN3EXT)
   
   It should be Mojolicious::Plugin::RenderFile::README

Bug#866965: (no subject)

[David Griffith]

This kernel commit might be relevant vis-a-vis switching in and out of 
64-bit contexts:


https://github.com/torvalds/linux/commit/6c25da5ad55d48c41b8909bc1f4e3cd5d85bb499

Bug#868171: here's the debugged output

[shirish शिरीष]

I hope the debugging with gdb.txt helps. I have cut normal exits and
normal creation of new threads as program goes on. Please let me know
if any more info. is needed.

-- 
  Regards,
  Shirish Agarwal  शिरीष अग्रवाल
  My quotes in this email licensed under CC 3.0
http://creativecommons.org/licenses/by-nc/3.0/
http://flossexperiences.wordpress.com
EB80 462B 08E1 A0DE A73A  2C2F 9F3D C7A4 E1C4 D2D8
[$] gdb qbittorrent 
[6:13:00]
GNU gdb (Debian 7.12-6) 7.12.0.20161007-git
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from qbittorrent...Reading symbols from 
/usr/lib/debug/.build-id/00/d1f26ff29cae66bd58e99ebf5ebc6cd3fea248.debug...done.
done.
(gdb) set logging on
Copying output to gdb.txt.
(gdb) set pagination 0
(gdb) handle SIG33 pass nostop noprint
SignalStop  Print   Pass to program Description
SIG33 NoNo  Yes Real-time event 33
(gdb) run
Starting program: /usr/bin/qbittorrent 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffea9a9700 (LWP 3824)]
[New Thread 0x7fffdfc2c700 (LWP 3825)]
.
QXcbConnection: XCB error: 3 (BadWindow), sequence: 4813, resource id: 
12743136, major code: 40 (TranslateCoords), minor code: 0
[New Thread 0x7fffb5e7e700 (LWP 3986)]
 (You also get stuff like above)

Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged. 
(As well as this)

QXcbConnection: XCB error: 3 (BadWindow), sequence: 27625, resource id: 
13147413, major code: 40 (TranslateCoords), minor code: 0
pure virtual method called
terminate called without an active exception

Thread 1 "qbittorrent" received signal SIGABRT, Aborted.
__GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51
51  ../sysdeps/unix/sysv/linux/raise.c: No such file or directory.
(gdb) bt
#0  0x753e3fcf in __GI_raise (sig=sig@entry=6) at 
../sysdeps/unix/sysv/linux/raise.c:51
#1  0x753e53fa in __GI_abort () at abort.c:89
#2  0x75cfcbb5 in __gnu_cxx::__verbose_terminate_handler() () at 
/usr/lib/x86_64-linux-gnu/libstdc++.so.6
#3  0x75cfa986 in  () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#4  0x75cfa9d1 in  () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#5  0x75cfb72f in  () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#6  0x55695b89 in BitTorrent::Session::handleAlert(libtorrent::alert*) 
(this=this@entry=0x5623dbf0, a=0x7fffc097b530) at 
../../src/base/bittorrent/session.cpp:2363
#7  0x55695e4b in BitTorrent::Session::readAlerts() 
(this=0x5623dbf0) at ../../src/base/bittorrent/session.cpp:2353
#8  0x557f1055 in BitTorrent::Session::qt_static_metacall(QObject*, 
QMetaObject::Call, int, void**) (_o=, _c=, 
_id=, _a=) at moc_session.cpp:293
#9  0x764b0c41 in QObject::event(QEvent*) () at 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#10 0x76ecdbec in QApplicationPrivate::notify_helper(QObject*, QEvent*) 
() at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#11 0x76ed5381 in QApplication::notify(QObject*, QEvent*) () at 
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#12 0x5562a252 in Application::notify(QObject*, QEvent*) 
(this=, receiver=0x5623dbf0, event=) at 
../../src/app/application.cpp:497
#13 0x76484850 in QCoreApplication::notifyInternal2(QObject*, QEvent*) 
() at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#14 0x76486fed in QCoreApplicationPrivate::sendPostedEvents(QObject*, 
int, QThreadData*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#15 0x764d7fb3 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#16 0x72988a17 in g_main_dispatch (context=0x7fffe40016f0) at 
././glib/gmain.c:3234
#17 0x72988a17 in g_main_context_dispatch 
(context=context@entry=0x7fffe40016f0) at ././glib/gmain.c:3899
#18 0x72988c80 in g_main_context_iterate 
(context=context@entry=0x7fffe40016f0, block=block@entry=1, 
dispatch=dispatch@entry=1, self=) at ././glib/gmain.c:3972
#19 0x72988d2c in g_main_context_iteration (context=0x7fffe40016f0, 
may_block=1) at ././glib/gmain.c:4033
#20 0x764d83bf in 

Bug#868179: xserver-xorg-video-radeon: SEGV when starting X11

[Michel Dänzer]

On 14/07/17 03:13 AM, bartek 'basz' szurgot wrote:
> On 07/13/2017 04:43 AM, Michel Dänzer wrote:
>> This bug is https://bugs.freedesktop.org/show_bug.cgi?id=100276 , fixed
>> by
>> https://cgit.freedesktop.org/xorg/driver/xf86-video-amdgpu/commit/?id=981bac185cfd74ae50dffc28f57cf34623a9595f
> 
> thanks for the prompt reply! :)
> 
> this bug is reported against video-radeon, while linked one is about
> video-amdgpu.

Indeed, my bad. The corresponding radeon commit is
https://cgit.freedesktop.org/xorg/driver/xf86-video-ati/commit/?id=4c91f36d3058180b5a2d6a23e9b82f5c933d8716
.


> is the affected code base common for both drivers?

Not common, but regularly synced.


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



signature.asc
Description: OpenPGP digital signature

Bug#868102: stretch-pu: package devscripts/2.17.6+deb9u1

[James McCoy]

On Thu, Jul 13, 2017 at 10:09:46AM +0100, Adam D. Barratt wrote:
> On 2017-07-12 3:27, James McCoy wrote:
> > * debchange:
> >   + Target stretch-backports with --bpo.  Closes: #867662
> >   + Support $codename{,-{proposed-updates,security}} as well.
> 
> I think there's a bug (or two?) that could be closed there?

Indeed.  Add the bug reference to the changelog.

> > * bts:
> >   + Add support for the new 'a11y' tag.  Closes: #867416
> 
> Please go ahead.

Done.

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

Bug#868260: devscripts: phantom script debdiff-apply

[James McCoy]

On Thu, Jul 13, 2017 at 10:59:43PM +0200, gregor herrmann wrote:
> I looked at the source package, without finding anything obvious.
> And rebuilding the package fails without internet access in the
> chroot (and/or with http_proxy set in the chroot).

It certainly shouldn't require internet access.  However, we do run some
uscan tests and uscan honors proxy settings in the environment.

I guess we should be clearing any of those when testing, just in case
they happen to leak into the test environment.

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

Bug#808226: [/master] debian/control: Updated dependency from python-twisted-web to python-twisted-core (Closes: #808226). Thanks to Diederik de Haas.

[Andrew Starr-Bochicchio]

tag 808226 pending
thanks

Date: Thu Jul 13 20:05:38 2017 -0400
Author: Andrew Starr-Bochicchio 
Commit ID: df8ec0cd9d6ec9274c0833bc9aaf9c0e9763cf2a
Commit URL: 
https://anonscm.debian.org/cgit/collab-maint/deluge.git;a=commitdiff;h=df8ec0cd9d6ec9274c0833bc9aaf9c0e9763cf2a
Patch URL: 
https://anonscm.debian.org/cgit/collab-maint/deluge.git;a=commitdiff_plain;h=df8ec0cd9d6ec9274c0833bc9aaf9c0e9763cf2a

debian/control: Updated dependency from python-twisted-web to 
python-twisted-core (Closes: #808226). Thanks to Diederik de Haas.

  

Bug#857357: [/master] New upstream release (Closes: #857357).

[Andrew Starr-Bochicchio]

tag 857357 pending
thanks

Date: Thu Jul 13 20:08:14 2017 -0400
Author: Andrew Starr-Bochicchio 
Commit ID: 7902584412d345e30dd3561ddf220f5132ea3c0f
Commit URL: 
https://anonscm.debian.org/cgit/collab-maint/deluge.git;a=commitdiff;h=7902584412d345e30dd3561ddf220f5132ea3c0f
Patch URL: 
https://anonscm.debian.org/cgit/collab-maint/deluge.git;a=commitdiff_plain;h=7902584412d345e30dd3561ddf220f5132ea3c0f

New upstream release (Closes: #857357).

  

Bug#833957: btrfs-progs: btrfs ERROR send ioctl failed with -2: No such file or directory

[Nicholas D Steeves]

Hi Jokobus,

On Wed, Aug 10, 2016 at 10:36:21PM +0200, Jakobus Schürz wrote:
> Dear Maintainer,
> 
> Since the last upgrade btrfs send fails with the error-message from the
> subject.
> 
> It occurs on a "normal" 
> btrfs send -p snapshot-older snapshot-newer -f transferfile
> 
> 
> Maybe it is the same problem as described here: 
> https://patchwork.kernel.org/patch/4238131/
[...]
> -- System Information:
> Debian Release: stretch/sid
>   APT prefers testing
>   APT policy: (990, 'testing'), (800, 'unstable')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
> 
> Kernel: Linux 4.6.0-1-rt-amd64 (SMP w/4 CPU cores; PREEMPT)
> Locale: LANG=de_AT.utf8, LC_CTYPE=de_AT.utf8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)

Wow, I can't believe this bug was ignored for almost a whole
year... :-/ During this time it looks like Filipe Manana's patch was
superseded by another patch, but I'm having trouble tracking the new
one down.  Based on that patch it looks like the bug is in src:linux
rather than btrfs-progs and should probably be reassigned...and
probably closed, because I'm guessing the fix is in Stretch's kernel.

Does the problem still occur with Stretch's linux-image
4.9.30-2+deb9u2 and btrfs-progs 4.7.3-1?

Sincerely,
Nicholas


signature.asc
Description: Digital signature

Bug#868275: perl: add debug symbols packages

[gregor herrmann]

On Fri, 14 Jul 2017 09:50:15 +1000, Paul Wise wrote:

> I have recently been getting some crashes in perl when it is running
> dpkg-architecture. I'd like to report them but there are no debug
> symbols packages for perl, it would be good to enable this.

There's /usr/bin/debugperl in the perl-debug package, maybe that
helps? 

Cheers,
gregor

-- 
 .''`.  https://info.comodo.priv.at/ - Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe
   `-   NP: Sinéad O'Connor: Fire On Babylon


signature.asc
Description: Digital Signature

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

[Steve McIntyre]

Control: reassign -1 867804 os-prober
Control: severity -1 important
Control: retitle -1 os-prober fails to parse lilo.conf correctly

Hi again Hazel,

Hint: please try to also CC @bugs.debian.org on all bug
discussion - that way the conversation is logged and others can see
the mails too.

On Wed, Jul 12, 2017 at 07:29:49AM +0100, Hazel Russman wrote:
>On Wed, 12 Jul 2017 01:25:26 +0100
>Steve McIntyre  wrote:
>> 
>> Could you attach those too, please? This looks like a bug for upstream
>> to look into, and they're going to need those files too I assume...
>> 
>OK, here they are. Sorry my setup is so complicated. btw none of the
>actual lilo.conf files has missing quotes as far as I can see.

Awesome, thanks. Using these, I've found the problem. os-prober is the
piece of software which attempts to automatically find and add GRUB
boot entries for the other operating systems on your
computer. Unfortunately, in your case it's mis-parsing valid lilo.conf
config files and it's then creating invalid GRUB boot entries from
them.

I've added debug to demonstrate the problem. Using your Crux lilo.conf
as an example, I now see the data it's trying to use:

  ::Crux:/boot/vmlinuz-4.9.6::root /dev/sda1 ro vga normal append "quiet

including the broken missing quote.

I'm attaching your config files and the temporary grub.cfg again to
this email, so that the os-prober developer has them as a reference.

>Could you also point me to an explanation of why grub-mkconfig
>creates so many duplicate entries for my system? It looks weird to
>me, quite apart from the errors.

Looking at what you have (picking crux again) it's adding:

  * a "normal" entry for it (in theory the same as lilo would be using)
  * an "advanced" submenu, containing
+ the "normal" entry again (no, I don't know why)
+ a version without the kernel command line options (to remove
 "quiet" etc.)
+ a .old version

It's doing a very bad job of parsing your config, clearly.

The normal for a Debian GRUB system is to add:

 * the "normal" boot entry, complete with "quiet"
 * an "advanced" submenu, containing entries for that kernel and other
   kernels found, typically giving options for init (systemd /
   sysvinit) and "recovery" (adding "single" to the command line)

For now, I'd suggest you disable the lilo.conf parsing maybe? To do
that, you can simply do

 $ sudo chmod -x /usr/lib/linux-boot-probes/mounted/50lilo

Hope that helps!

-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
"Managing a volunteer open source project is a lot like herding
 kittens, except the kittens randomly appear and disappear because they
 have day jobs." -- Matt Mackall
# /etc/lilo.conf  -   systemwide LILO configuration (LILO 23)
# details see in manpages: lilo(8) and lilo.conf(5)

# +-+
# |!! Reminder !!   |
# | |
# | Don't forget to run 'lilo' after you make changes to this   |
# | conffile or you have installed a new kernel.|
# +-+


#  LILO global section ##

# With all newer systems (until year 2004) you can use the RAM
# above 15 MB. This option allows the use of this range of RAM.
#large-memory

# With all newer systems you can boot from any partition on disks 
# with more than 1024 cylinders. This option allows the use of 
# partitions above 1024 cylinders.
lba32
# install=text
# boot=/dev/#DEVICE#
# image=/boot/vmlinuz
#label=CRUX
#read-only
#append="root=/dev/#ROOT_DEVICE#"

# Specifies the boot device.  This is where Lilo installs its boot
# block.  It can be either a partition, or the raw device, in which
# case it installs in the MBR, and will overwrite the current MBR.
# With newer kernel you should use the ID of the boot device, which
# can be found here: /dev/disks/by-id/ata*.
boot = /dev/sda
#boot = /dev/disk/by-id/ata-SAMSUNG_SV2042H_0273J1FR295888

# This option may be needed for some software RAID installs.
#raid-extra-boot = mbr-only

# Enable map compaction.  This tries to merge read requests for 
# adjacent sectors into a single read request. This drastically 
# reduces load time and keeps the map smaller.  Using 'compact' 
# is especially recommended when booting from a floppy disk.  
# It is disabled here by default because it doesn't always work.
#compact

# Set the verbose level for bootloader installation. Value range:
# 0 to 5. Default value is 0.
#verbose = 1

# Specifies the location of the map file. Lilo creates the (sector) 
# map file of direct sector addresses which are independent of any
# filesystem.
map = /boot/map

# ---

# Specifies the menu interface. You have the choice between:
#   text: simple text menu with 

Bug#868276: apt_preferences(5): explain how one would combine e.g. origin, version and release Pins

[Christoph Anton Mitterer]

Package: apt
Version: 1.5~beta1
Severity: wishlist


Hi.

Looking at apt_preferences(5), it does, AFAICS, not explain the following:

a) What happen if multiple e.g. Pin: directives are found? It seems only
   the last one is taken and the former ones ignored (per block).
   btw: Perhaps it would be even good, if apt gives warnings in such cases.


b) How can one combine origin, version and release Pins?
   e.g. for a package named foo, when it's from Origin ACME, the version 10 
shall get Priority 600:
Is this:
Package: foo
Pin: version 10 release o=ACME
Pin-Priority: 600

or would it be
Pin: version 10, release o=ACME

or would swapping work?
Pin: release o=ACME version 10
What if my Origin contains spaces?


Cheers,
Chris.

Bug#868258: [V2] Patches or pull request before updating to 4.11.1

[Nicholas D Steeves]

I re-factored the patches slightly to group more logically and added
in a minor "don't be redundant" item for the switch to debhelper 10.
I'm not sure why "bts show --mbox" is providing bogus metadata about
the patches.  Here is the new summary.  The new patches at attached
and I force pushed to the remote I mentioned in my last email:

Summary (Important, Normal, Minor, Wishlist):

I 0001-Override-dh_auto_clean-to-work-around-upstream-bug-w.patch
M 0002-Ignore-.pc-the-quilt-state-tracking-dir.patch
  * I read that this is supposed to be standard in dgit repos
I 0003-Drop-btrfs-convert-Closes-824895-854489.patch
  * And also apply this for stretch-update
N 0004-Move-all-binaries-back-to-sbin-Closes-786893.patch
  * Completely up to you, of course ;-)
N 0005-Update-Source-because-Chris-Mason-s-branch-hasn-t-be.patch
I 0006-Exclude-non-free-RFC-BCP78-files-affects-test-suite.patch
I 0007-4.6.1-1-did-not-fix-package-license.patch
  * And also apply this for stretch-update
I 0008-Add-dversionmangle-to-handle-dfsg-version-suffix.patch
I 0009-Update-copyright-for-new-locations-of.patch
  * And also apply this for stretch-update
W 0010-d-control-add-whitespace-cosmetic-fix.patch
N 0011-debian-watch-Switch-to-version-4-and-add-repacksuffi.patch
N 0012-Drop-btrfs-tools-transitional-dummy-package.patch
  * Can be safely dropped now, because Stretch was released with
the transitional package
N 0013-Switch-to-debhelper-10-and-automatically-generated-d.patch
  * No time like the present, right? :-)
N 0014-Update-changelog.patch
  * Please delete entries for patches you reject

Cheers,
Nicholas
From a2f1850869b63e1244778718f620accdf81c9c79 Mon Sep 17 00:00:00 2001
From: Nicholas D Steeves 
Date: Sat, 11 Mar 2017 20:04:35 -0500
Subject: [PATCH 01/14] Override dh_auto_clean to work around upstream bug
 where make clean cannot be run before ./configure

---
 debian/rules | 5 +
 1 file changed, 5 insertions(+)

diff --git a/debian/rules b/debian/rules
index 265ef280..6be097c8 100755
--- a/debian/rules
+++ b/debian/rules
@@ -36,3 +36,8 @@ override_dh_auto_test:
 
 override_dh_strip:
 	dh_strip --dbg-package=btrfs-progs-dbg
+
+override_dh_auto_clean:
+	if test -f Makefile.inc; then \
+		dh_auto_clean; \
+	fi
-- 
2.11.0

From dbf42a8606559212902f628cd71b69aba0cd4376 Mon Sep 17 00:00:00 2001
From: Nicholas D Steeves 
Date: Sat, 11 Mar 2017 20:27:13 -0500
Subject: [PATCH 02/14] Ignore .pc, the quilt state tracking dir

---
 .gitignore | 1 +
 1 file changed, 1 insertion(+)

diff --git a/.gitignore b/.gitignore
index 98b3657b..ba8c8590 100644
--- a/.gitignore
+++ b/.gitignore
@@ -76,3 +76,4 @@ stamp-h.in
 stamp-h1
 config/*
 
+.pc
-- 
2.11.0

From f714d2925caed58936d6e068ca206cf40499af37 Mon Sep 17 00:00:00 2001
From: Nicholas D Steeves 
Date: Sat, 11 Mar 2017 20:34:22 -0500
Subject: [PATCH 03/14] Drop btrfs-convert (Closes: #824895, #854489)

Rationale: the test failed
...
[TEST]   convert-tests.sh
[TEST/conv]   001-ext2-basic
[TEST/conv] ext2 4k nodesize, btrfs defaults
failed: /scratch/btrfs-progs-v4.10/btrfs-convert --rollback /scratch/btrfs-progs-v4.10/tests/test.img
test failed for case 001-ext2-basic
Makefile:271: recipe for target 'test-convert' failed
make: *** [test-convert] Error 1
---
 debian/rules | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/debian/rules b/debian/rules
index 6be097c8..f6181164 100755
--- a/debian/rules
+++ b/debian/rules
@@ -19,7 +19,7 @@ override_dh_autoreconf:
 	dh_autoreconf ./autogen.sh
 
 override_dh_auto_configure:
-	dh_auto_configure -- --bindir=/bin
+	dh_auto_configure -- --bindir=/bin --disable-convert
 
 override_dh_auto_build:
 	dh_auto_build -- V=1
-- 
2.11.0

From 568af50aee8a58dbfc5ac21f3a6a623cc0c54e29 Mon Sep 17 00:00:00 2001
From: Nicholas D Steeves 
Date: Sat, 11 Mar 2017 21:14:15 -0500
Subject: [PATCH 04/14] Move all binaries back to /sbin (Closes: #786893)

---
 debian/btrfs-progs-udeb.install | 4 ++--
 debian/rules| 2 +-
 2 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/debian/btrfs-progs-udeb.install b/debian/btrfs-progs-udeb.install
index 3effab9e..f06a6498 100644
--- a/debian/btrfs-progs-udeb.install
+++ b/debian/btrfs-progs-udeb.install
@@ -1,2 +1,2 @@
-btrfs		/bin
-mkfs.btrfs	/bin
+btrfs		/sbin
+mkfs.btrfs	/sbin
diff --git a/debian/rules b/debian/rules
index f6181164..0ac43c76 100755
--- a/debian/rules
+++ b/debian/rules
@@ -19,7 +19,7 @@ override_dh_autoreconf:
 	dh_autoreconf ./autogen.sh
 
 override_dh_auto_configure:
-	dh_auto_configure -- --bindir=/bin --disable-convert
+	dh_auto_configure -- --bindir=/sbin --disable-convert
 
 override_dh_auto_build:
 	dh_auto_build -- V=1
-- 
2.11.0

From e87b785f7b137221212148f2083a0755803f6cb7 Mon Sep 17 00:00:00 2001
From: Nicholas D Steeves 
Date: Sun, 19 Mar 2017 15:03:32 -0400
Subject: [PATCH 05/14] Update Source, because Chris Mason's branch hasn't 

Bug#868275: perl: add debug symbols packages

[Paul Wise]

Source: perl
Severity: wishlist

I have recently been getting some crashes in perl when it is running
dpkg-architecture. I'd like to report them but there are no debug
symbols packages for perl, it would be good to enable this.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#868246: ditto

[Mark Hedges]

found 868246 8.13.11+dfsg1-8
tags 868246 buster
thanks

I just upgraded Stretch to Buster and found the same problem in Buster.

Thanks.
Mark

Bug#868274: ITP: lxqt-themes-extra -- Extra themes for LXQt (debian and derivatives)

[Alf Gaida]

Package: wnpp
Severity: wishlist
Owner: Alf Gaida 

* Package name : lxqt-themes-extra
  Version : 0.11.96
  Upstream Author : Alf Gaida  
* URL : https://anonscm.debian.org/cgit/pkg-lxqt/lxqt-themes-extra.git/ 
* License : LGPL
  Programming Lang: n.A.
  Description : Extra themes for LXQt (debian and derivatives)

Theme for debian which uses the background of desktop-base, planned something 
similar for Lubuntu

Bug#868181: closed by Salvo 'LtWorf' Tomaselli <tipos...@tiscali.it> (Bug#868181: fixed in weborf 0.13.5-1)

[Axel Beckert]

Hi Salvo!

>* New upstream release (Closes: #868181, #868182)

Thanks! This indeed fixed accessing weborf-served directory indexes
with my Kobo Aura H20 e-book reader. :-)

And also thanks for implementing my suggestion to just prepend
":::" to IPv4 addresses if weborf is compiled with IPv6 support!
Makes using weborf much more "do what I mean". :-)

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

Bug#849850: encfs: same problem

[Joe Pfeiffer]

I'm seeing the same problem following an upgrade today, with version
1.9.1-4.  My log message is
Message-ID: <149998600914.4028.4334536845084459008.reportbug@snowball>
X-Mailer: reportbug 7.1.7
Date: Thu, 13 Jul 2017 16:46:49 -0600

Package: encfs
Followup-For: Bug #849850

Jul 13 16:28:19 snowball kernel: [  545.053729] encfs[3542]: segfault at 0 ip 
7fe2ba2d4e62 sp 7fe2b8819960 error 4 in 
libencfs.so.1.9.1[7fe2ba27b000+75000]

I'm running it on top of ext4, using pam_mount

I've reverted to 1.7.4-5 and seem to be running OK.

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

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

Versions of packages encfs depends on:
ii  debconf   1.5.62
ii  fuse  2.9.7-1
ii  libboost-filesystem1.55.0 1.55.0+dfsg-3
ii  libboost-serialization1.55.0  1.55.0+dfsg-3
ii  libboost-system1.55.0 1.55.0+dfsg-3
ii  libc6 2.24-12
ii  libfuse2  2.9.7-1
ii  libgcc1   1:7.1.0-9
ii  librlog5  1.4-2.1
ii  libssl1.0.0   1.0.2d-1
ii  libstdc++67.1.0-9

encfs recommends no packages.

encfs suggests no packages.

-- debconf-show failed

Bug#868273: open-vm-tools: clean up legacy conffiles

[Christoph Anton Mitterer]

Source: open-vm-tools
Version: 2:10.1.5-5055683-4
Severity: normal


Hi.

The package once contained the conffiles:
/etc/modprobe.d/open-vm-tools.conf
/etc/xdg/autostart/vmware-user.desktop
but apparently no longer does.

These files have however not been cleaned up properly and dpkg still things
they're conffiles (and the files are still there).

Please clean them up properly in once on the next uploads using the
dpkg-maintscript-helper.

Thanks,
Chris.

Bug#865224: uwsgi: ftbfs with multiple supported python3 versions

[Scott Kitterman]

On Friday, July 14, 2017 12:37:12 AM Niko Tyni wrote:
> On Fri, Jun 30, 2017 at 10:28:09PM +0200, Jonas Smedegaard wrote:
> > Quoting Scott Kitterman (2017-06-30 08:25:19)
> > 
> > > On Tue, 20 Jun 2017 11:26:35 +1200 Michael Hudson-Doyle
> > > 
> > >  wrote:
> > > > This may well turn out to be a cdbs bug in the end, but uwsgi does
> > > > not build when pysupport -r returns more than one version:
> > > > 
> > > > https://launchpadlibrarian.net/323025281/buildlog_ubuntu-artful-amd64.
> > > > uwsgi_2.0.15-1ubuntu3_BUILDING.txt.gz
> > > > 
> > > > Picking out the failing lines:
> > > > 
> > > > *** asyncio_python27 plugin built and available in
> > > > ./asyncio_python27_plugin.so *** touch
> > > > debian/stamp-uwsgi-plugin-asyncio-python
> > > > debian/rules:452: *** no python implementation resolved from flavor
> > > > "python3.6" among packages python-uwsgidecorators
> > > > python3-uwsgidecorators.  Stop.
> > > > 
> > > > In this build python 3.5 is the default and python 3.6 is supported.
> > > > In a build where python 3.6 is default and python 3.5 is supported,
> > > > the error complains about python 3.5 instead. And if python 3.6 is
> > > > the only supported version, the build completes successfully. So I
> > > > think this is really a problem in uwsgi or cdbs' handling of
> > > > multiple supported python versions.
> > > 
> > > We now have this in Debian, so bumping to serious.
> > 
> > Thanks, both for reporting initially and for bumping!
> 
> It looks like a cdbs issue to me,
>   $(call cdbs_expand_pythonruntime,,python3.6)
> breaks while
>   $(call cdbs_expand_pythonruntime,,python3.5)
> works (and results in "python3" as expected.)
> 
> A workaround that seems to help is putting
>  X-Python3-Version: 3.5
> in the Source paragraph of debian/control to prevent it from trying 3.6
> at all. This makes the build work for me (but doesn't help the python3.6
> transition of course.)
> 
> This is the worst blocker for the Perl 5.26 transition too (uwsgi needs
> to be rebuilt because uwsgi-plugin-psgi links against libperl), so even
> a temporary ugly workaround would be appreciated from this side :)

Changing the python3-all-dev build-depends to python3-dev would accomplish the 
same thing while allowing a binNMU to work when we make python3.6 default.  
Since this is blocking your work, I would recommend you NMU with that change 
(I have forgotten approximately everything I ever new about CDBS, so I don't 
mess with CDBS packages if I can possibly avoid it - I don't plan to do this 
NMU).

Scott K


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

Bug#868099: rkhunter: clean up legacy conffile

[Christoph Anton Mitterer]

>Do you know what the correct to do this is?

Uhm... sorry... not really...
Perhaps something like backuping the current file, then using dpkg-
maintscript-helper rm_conffile to remove the conffile, and then move
the backup back as manually managed file.

But really better ask at d-d on how to do it... there is likely a
proper way for it and the above is easily prone to /tmp attacks and so.


Cheers,
Chris.

smime.p7s
Description: S/MIME cryptographic signature

Bug#864858: strace: Please don't do unaligned access in the testsuite on ARM

[Dmitry V. Levin]

Hi Steve,

On Thu, Jun 15, 2017 at 10:01:55PM -0700, Steve Langasek wrote:
> Package: strace
> Version: 4.15-2
> Severity: normal
> Tags: patch
> User: ubuntu-de...@lists.ubuntu.com
> Usertags: origin-ubuntu artful ubuntu-patch
> 
> Hi Steve,
> 
> As you're probably aware, unaligned access on ARM is not guaranteed to
> succeed; depending on the CPU and the kernel configuration, in may raise
> SIGBUS instead.
> 
> The strace test suite avoids unaligned accesses for POWER and Sparc, but for
> other archs, including ARM, it deliberately tests with unaligned access. 
> This is not a problem on Debian's builders, but it is on Ubuntu's. 
> Therefore, I've uploaded the attached patch to Ubuntu.
> 
> Please consider whether this is appropriate to apply in Debian as well.
> 
> Thanks,
> -- 
> Steve Langasek   Give me a lever long enough and a Free OS
> Debian Developer   to set it on, and I can move the world.
> Ubuntu Developerhttp://www.debian.org/
> slanga...@ubuntu.com vor...@debian.org

> diff -Nru strace-4.15/debian/patches/no-arm-unaligned-access 
> strace-4.15/debian/patches/no-arm-unaligned-access
> --- strace-4.15/debian/patches/no-arm-unaligned-access1969-12-31 
> 16:00:00.0 -0800
> +++ strace-4.15/debian/patches/no-arm-unaligned-access2017-06-15 
> 21:57:38.0 -0700
> @@ -0,0 +1,18 @@
> +Description: Don't allow unaligned access on ARM in the tests
> + The testsuite already handles alignment requirements on POWER and Sparc, add
> + ARM to the list as well.  Not all ARM enviroments raise SIGBUS on unaligned
> + access, but some (including the Ubuntu autobuilders) do.
> +Author: Steve Langasek 
> +Last-Update: 2017-06-16
> +
> +--- strace-4.15.orig/tests/perf_event_open.c
>  strace-4.15/tests/perf_event_open.c
> +@@ -500,7 +500,7 @@ end:
> + }
> + 
> + /* These require aligned access, so no byte-grain checks possible */
> +-# if defined SPARC || defined SPARC64 || defined POWERPC || defined 
> POWERPC64
> ++# if defined SPARC || defined SPARC64 || defined POWERPC || defined 
> POWERPC64 || defined ARM
> + #  define ATTR_REC(sz) { tail_alloc((sz + 7) & ~7), sz }
> + # else
> + #  define ATTR_REC(sz) { tail_alloc(sz), sz }
> diff -Nru strace-4.15/debian/patches/series strace-4.15/debian/patches/series
> --- strace-4.15/debian/patches/series 2017-01-19 06:02:56.0 -0800
> +++ strace-4.15/debian/patches/series 2017-06-15 21:57:38.0 -0700
> @@ -1,1 +1,2 @@
>  disable-failing-tests.patch
> +no-arm-unaligned-access

Could you submit the patch in a git-am friendly form to the mailing list,
please?  Thanks.


-- 
ldv


signature.asc
Description: PGP signature

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

[alberto fuentes]

Systemd maintainer has told me that systemd is not responsible for
this bug because

> This bug is misfiled. systemd is not involved with 
> /var/lib/dhcp/dhclient.leases

/var/lib/dhcp/ belongs to this package. Is this the right place? :)

Bug#868272: postgresql-common: clean up legacy conffiles

[Christoph Anton Mitterer]

Source: postgresql-common
Version: 181
Severity: normal


Hi.

Apparently the package used to contain:
/etc/logrotate.d/postgresql-common
as a dpkg conffile but no longer does and ships it manually managed instead.

This file was however not properly cleaned up as conffile and is still marked 
as such.
Could you please to so in one of the next versions, so that
people will get the clean up? :-)

Thanks,
Chris.

Bug#868271: ITP: erlang-asciideck -- Erlang library for asciidoc

[Nobuhiro Iwamatsu]

Package: wnpp
Severity: wishlist
Owner: Nobuhiro Iwamatsu 

* Package name: erlang-asciideck
  Version : 0
  Upstream Author : Loïc Hoguin 
* URL : https://github.com/ninenines/asciideck
* License : ISC
  Programming Lang: Erlang
  Description : Erlang library for asciidoc

The asciideck project aims to provide a parser for Asciidoc
files returning an abstract syntax tree that can be further
manipulated or used to convert documents to different formats.

Bug#867190: stretch-pu: package apt/1.4.7

[Julian Andres Klode]

On Thu, Jul 13, 2017 at 09:00:06PM +0100, Adam D. Barratt wrote:
> Control: tags -1 -moreinfo +confirmed
> 
> On Sun, 2017-07-09 at 17:08 +0200, Julian Andres Klode wrote:
> > The first one by David, the second by me, so this would end up
> > something like the following (order may be different, it's auto-generated
> > from git commits):
> > 
> > apt (1.4.7) stretch; urgency=medium
> > 
> >   [ Robert Luberda ]
> >   * fix a "critical" typo in old changelog entry (Closes: 866358)
> > 
> >   [ David Kalnischkies ]
> >   * use port from SRV record instead of initial port
> >   * travis: ignore profiling warning in progress lines  
> >
> > 
> >   [ Julian Andres Klode ]
> >   * Reset failure reason when connection was successful
> 
> maybe "... ensuring errors are correctly reported" or something similar?
> 
> >   * debian/gbp.conf: Set debian-branch to 1.4.y
> >   * http: Do not try reading content if Content-Length is 0
> >   * travis: Migrate to Docker
> >   * Release 1.4.7 (LP: #1702326)
> 
> Having the release item at the end looks slightly odd, imho. :-)
> 
> Please feel free to upload something like the above (bearing in mind
> that the window for 9.1 closes this weekend).

Uploaded with:

 apt (1.4.7) stretch; urgency=medium
 .
   * New release with important fixes up to 1.5~beta1; also see LP: #1702326
 .
   [ Robert Luberda ]
   * fix a "critical" typo in old changelog entry (Closes: 866358)
 .
   [ David Kalnischkies ]
   * test suite/travis CI: ignore profiling warning in progress lines
   * use port from SRV record instead of initial port
 .
   [ Julian Andres Klode ]
   * Reset failure reason when connection was successful, so later errors are
 reported as such and not as "connection failure" warnings.
   * debian/gbp.conf: Set debian-branch to 1.4.y
   * http: A response with Content-Length: 0 has no content, so don't try to
 read it - it will either timeout or the server closes the connection.
   * travis CI: Migrate to Docker



-- 
Debian Developer - deb.li/jak | jak-linux.org - free software dev
  |  Ubuntu Core Developer |
When replying, only quote what is necessary, and write each reply
directly below the part(s) it pertains to ('inline').  Thank you.

Bug#864940: strace: Testsuite needs to skip kexec_file_load on powerpc << 4.11

[Dmitry V. Levin]

Hi Adam,

On Sat, Jun 17, 2017 at 11:31:12AM -0600, Adam Conrad wrote:
> Package: strace
> Version: 4.15-2
> Severity: important
> Tags: patch
> User: ubuntu-de...@lists.ubuntu.com
> Usertags: origin-ubuntu artful ubuntu-patch
> 
> In Ubuntu, the attached patch was applied to achieve the following:
> 
>   * kexec_file_load.patch: Skip kexec_file_load test on ppc* before 4.11.
> 
> During 4.11 development, the kexec_file_load syscall was wired up on
> ppc.  The result of this is that if you build strace with 4.11 headers,
> but on a runtime kernel << 4.11, the testsuite will fail.  This patch
> addresses that issue.
> 
> ... Adam

The test is designed to behave properly on older kernels and does not have
to be disabled just because the kernel has no kexec_file_load syscall
support.  What's the problem you experience on ppc*?


-- 
ldv


signature.asc
Description: PGP signature

Bug#868042: poedit: Texts become right-aligned after upgrade onto poedit2

[Olly Betts]

Control: tags -1 + pending

On Thu, Jul 13, 2017 at 11:31:38AM +0200, Gianfranco Costamagna wrote:
> Olly, do you have any advice against updating wx?

I'm already working on an update to 3.0.3.1.

> I know you would like to transition to gtk3, maybe we can
> do them together?

A transition to gtk3 will need a lot of preparation, so it doesn't make
sense to block uploading a new upstream for that.

> (and drop the 0v5 rename hack :) )

That's not a "hack", and we can only drop it if we're making an
incompatible ABI change, which it isn't yet clear if a switch to
gtk3 would entail.

Cheers,
Olly

Bug#825348: lintian: check for packages containing upstart configuration in /etc/init/

[Paul Wise]

On Thu, 2017-07-13 at 09:23 +0100, Chris Lamb wrote:

> Sorry, I should have written a much better question; what actually
> *are* the markers of a package shipping upstart configuration?

As I understand it, shipping files in the /etc/init/ directory.

> Is it simply the package checking init_is_upstart (etc.) in scripts
> under /etc/init.d? Linking to an example package might be ideal here.

$ apt-file search /etc/init/ | wc -l
197
$ apt-file search /etc/init/ | head
anacron: /etc/init/anacron.conf
aodh-
api: /etc/init/aodh-api.conf
aodh-evaluator: /etc/init/aodh-
evaluator.conf
aodh-expirer: /etc/init/aodh-expirer.conf
aodh-listener:
/etc/init/aodh-listener.conf
aodh-notifier: /etc/init/aodh-notifier.conf
apertium-apy: /etc/init/apertium-apy.conf
apparmor:
/etc/init/apparmor.conf
aptitude-robot: /etc/init/aptitude-robot.conf
bar
bican-api: /etc/init/barbican-api.conf

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#868270: Upgrade from kama 4 to kama 5 fails

[James Cloos]

Package: kamailio
Version: 4.4.4-3+b1
Severity: important

Trying to upgrade kamailio with apt dist-upgrade failed.

The kama packages which were installed are:

The following packages will be upgraded:
   kamailio (4.4.4-3+b1 => 5.0.2-1)
   kamailio-geoip-modules (4.4.4-3+b1 => 5.0.2-1)
   kamailio-json-modules (4.4.4-3+b1 => 5.0.2-1)
   kamailio-outbound-modules (4.4.4-3+b1 => 5.0.2-1)
   kamailio-perl-modules (4.4.4-3+b1 => 5.0.2-1)
   kamailio-postgres-modules (4.4.4-3+b1 => 5.0.2-1)
   kamailio-tls-modules (4.4.4-3+b1 => 5.0.2-1)
   kamailio-utils-modules (4.4.4-3+b1 => 5.0.2-1)
   kamailio-websocket-modules (4.4.4-3+b1 => 5.0.2-1)
   kamailio-xmpp-modules (4.4.4-3+b1 => 5.0.2-1)

And these are the errors dpkg reported:

Unpacking kamailio-perl-modules:amd64 (5.0.2-1) over (4.4.4-3+b1) ...
dpkg: error processing archive 
/tmp/apt-dpkg-install-mhUp00/03-kamailio-perl-modules_5.0.2-1_amd64.deb 
(--unpack):
 trying to overwrite '/usr/lib/kamailio/libsrdb1.so.1.0', which is also in 
package kamailio-utils-modules:amd64 5.0.2-1
dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)

Unpacking kamailio-postgres-modules:amd64 (5.0.2-1) over (4.4.4-3+b1) ...
dpkg: error processing archive 
/tmp/apt-dpkg-install-mhUp00/09-kamailio-postgres-modules_5.0.2-1_amd64.deb 
(--unpack):
 trying to overwrite '/usr/lib/kamailio/libsrdb1.so.1.0', which is also in 
package kamailio-utils-modules:amd64 5.0.2-1
dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)

dpkg: error processing archive 
/tmp/apt-dpkg-install-mhUp00/11-kamailio_5.0.2-1_amd64.deb (--unpack):
 trying to overwrite '/usr/lib/kamailio/libsrdb1.so.1.0', which is also in 
package kamailio-utils-modules:amd64 5.0.2-1
dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
Kamailio not yet configured. Edit /etc/default/kamailio first. ... failed!
Errors were encountered while processing:
 /tmp/apt-dpkg-install-mhUp00/03-kamailio-perl-modules_5.0.2-1_amd64.deb
 /tmp/apt-dpkg-install-mhUp00/09-kamailio-postgres-modules_5.0.2-1_amd64.deb
 /tmp/apt-dpkg-install-mhUp00/11-kamailio_5.0.2-1_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)



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

Kernel: Linux 3.2.0-4-amd64 (SMP w/2 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: sysvinit (via /sbin/init)

Versions of packages kamailio depends on:
ii  adduser  3.115
ii  init-system-helpers  1.48
ii  libc62.24-12
ii  libncurses5  6.0+20170708-1
ii  libpcre3 2:8.39-3
ii  libreadline7 7.0-3
ii  libtinfo56.0+20170708-1
ii  lsb-base 9.20161125
ii  python   2.7.13-2

kamailio recommends no packages.

Versions of packages kamailio suggests:
pn  kamailio-berkeley-modules  
pn  kamailio-carrierroute-modules  
pn  kamailio-cpl-modules   
pn  kamailio-ldap-modules  
pn  kamailio-lua-modules   
pn  kamailio-mono-modules  
pn  kamailio-mysql-modules 
ii  kamailio-perl-modules  4.4.4-3+b1
ii  kamailio-postgres-modules  4.4.4-3+b1
pn  kamailio-presence-modules  
pn  kamailio-python-modules
pn  kamailio-radius-modules
pn  kamailio-redis-modules 
pn  kamailio-snmpstats-modules 
pn  kamailio-unixodbc-modules  
pn  kamailio-xml-modules   
iu  kamailio-xmpp-modules  5.0.2-1
pn  stun-server | turn-server  

-- Configuration Files:
/etc/kamailio/kamailio.cfg [Errno 2] No such file or directory: 
'/etc/kamailio/kamailio.cfg'

-- no debconf information

Bug#868269: Regression from jessie to stretch in handling of %u, %U, %s, and %h

[Josh Triplett]

Package: systemd
Version: 233-10
Severity: normal

I'm not suggesting a change here, but I do think this could use
documentation in the release notes and NEWS.Debian file.

Commit 79413b673b45adc98dfeaec882bbdda2343cb2f9 in systemd 228 (between
jessie and stretch) effectively broke/disabled the %u, %U, %s and %h
specifiers in units.  I ran into this with a local unit that used %u,
which went from expanding to the value of User to expanding to "root".
It took quite a bit of investigating to figure out the cause.

At a minimum, I would suggest adding something to the stretch release
notes about this, as well as a NEWS.Debian entry.

You might also consider, in your next stretch-proposed-updates upload,
including the same NEWS.Debian entry.

Bug#868268: initramfs-tools: Please add raid1 to the module added when MODULES=most

[Jean-Yves LENHOF]

Package: initramfs-tools
Version: 0.130
Severity: normal

Dear Maintainer,

When using raid1 lvm root, the raid1 module is not added to the initrd
built (raid456 module is in).
This will make the system unbootable and goind to the initramfs debug mode
Please add raid1 in when selecting MODULES=most

As a workaround you can add raid1 to /etc/initramfs-tools/modules and do
update-initramfs -k all -u

-- Package-specific info:
-- initramfs sizes
-rw-r--r-- 1 root root 18M Jul 13 23:24 /boot/initrd.img-4.9.0-3-amd64
-- /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-4.9.0-3-amd64 root=/dev/mapper/VGroot-LVslash
ro quiet

-- resume
RESUME=none
-- /proc/filesystems
xfs

-- lsmod
Module  Size  Used by
snd_hda_codec_generic69632  1
snd_hda_intel  36864  0
snd_hda_codec 135168  2 snd_hda_intel,snd_hda_codec_generic
snd_hda_core   81920  3
snd_hda_intel,snd_hda_codec,snd_hda_codec_generic
snd_hwdep  16384  1 snd_hda_codec
snd_pcm   110592  3 snd_hda_intel,snd_hda_codec,snd_hda_core
snd_timer  32768  1 snd_pcm
snd86016  6
snd_hda_intel,snd_hwdep,snd_hda_codec,snd_timer,snd_hda_codec_generic,snd_pcm
soundcore  16384  1 snd
qxl69632  1
ttm98304  1 qxl
drm_kms_helper155648  1 qxl
edac_mce_amd   28672  0
drm   360448  4 qxl,ttm,drm_kms_helper
ppdev  20480  0
edac_core  57344  0
pcspkr 16384  0
evdev  24576  1
serio_raw  16384  0

joydev 20480  0
virtio_balloon 16384  0
parport_pc 28672  0
virtio_console 24576  0
parport49152  2 parport_pc,ppdev
sg 32768  0
acpi_cpufreq   20480  0
button 16384  0
ip_tables  24576  0
x_tables   36864  1 ip_tables
autofs440960  2
xfs  1208320  1
raid1  36864  1
dm_raid40960  1
raid456   106496  1 dm_raid
async_raid6_recov  20480  1 raid456
async_memcpy   16384  2 raid456,async_raid6_recov
async_pq   16384  2 raid456,async_raid6_recov
async_xor  16384  3 async_pq,raid456,async_raid6_recov
async_tx   16384  5
async_xor,async_pq,raid456,async_memcpy,async_raid6_recov
md_mod131072  3 dm_raid,raid1,raid456
xor24576  1 async_xor
raid6_pq  110592  3 async_pq,raid456,async_raid6_recov
libcrc32c  16384  2 xfs,raid456
crc32c_generic 16384  1
dm_mod118784  16 dm_raid
hid_generic16384  0
usbhid 53248  0
hid   122880  2 hid_generic,usbhid
sr_mod 24576  0
cdrom  61440  1 sr_mod
ata_generic16384  0
virtio_net 28672  0
virtio_blk 20480  4
psmouse   135168  0
floppy 69632  0
ata_piix   36864  0
ehci_pci   16384  0
uhci_hcd   45056  0
ehci_hcd   81920  1 ehci_pci
usbcore   249856  4 usbhid,ehci_hcd,uhci_hcd,ehci_pci
usb_common 16384  1 usbcore
virtio_pci 24576  0
virtio_ring24576  5
virtio_blk,virtio_net,virtio_balloon,virtio_console,virtio_pci
virtio 16384  5
virtio_blk,virtio_net,virtio_balloon,virtio_console,virtio_pci
i2c_piix4  24576  0
libata249856  2 ata_piix,ata_generic
scsi_mod  225280  3 libata,sr_mod,sg

-- /etc/initramfs-tools/modules
raid1

- /etc/kernel-img.conf
# Kernel image management overrides
# See kernel-img.conf(5) for details
do_symlinks = yes
do_bootloader = no
do_initrd = yes
link_in_boot = no

-- /etc/initramfs-tools/initramfs.conf
MODULES=most
BUSYBOX=auto
KEYMAP=n
COMPRESS=gzip
DEVICE=
NFSROOT=auto

-- /etc/initramfs-tools/update-initramfs.conf
update_initramfs=yes
backup_initramfs=no

-- /proc/mdstat
Personalities : [raid6] [raid5] [raid4] [raid1]
unused devices: 

-- mkinitramfs hooks
/etc/initramfs-tools/hooks/:

/usr/share/initramfs-tools/hooks:
dmsetup
fsck
keymap
klibc-utils
kmod
lvm2
resume
thermal
udev
zz-busybox

-- 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/1 CPU core)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8),
LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages initramfs-tools depends on:
ii  initramfs-tools-core  0.130
ii  linux-base4.5

initramfs-tools recommends no packages.

Versions of packages initramfs-tools suggests:
ii  bash-completion  1:2.1-4.3


-- no debconf information

Bug#868245: RFS: python-latexcodec/1.0.5-1

[Daniel Stender]

On 13.07.2017 17:56, Ghislain Vaillant wrote:
> Package: sponsorship-requests
> Severity: wishlist
> 
> Dear mentors,
> 
> I am looking for a sponsor for the following package:
> 
> * Package name: python-latexcodec
>   Version : 1.0.5-1
>   Upstream Author : Matthias C. M. Troffaes
> * URL : https://pypi.python.org/pypi/latexcodec/
> * License : Expat
>   Section : python

In. That's a decent package. Thanks for adopting this. Let me know when
Pybtex is ready to follow.

Best,
DS

-- 
4096R/DF5182C8 (sten...@debian.org)
http://www.danielstender.com/

Bug#868239: virtualbox-dkms: Error building initial module for 4.9.0-3-amd64 kernel.

[Gianfranco Costamagna]

control: reassign -1 src:debhelper
control: forcemerge -1 868169


fix is ongoing

G.


Il Giovedì 13 Luglio 2017 16:18, Mladen Mijatov  ha 
scritto:



Package: virtualbox-dkms
Version: 5.1.22-dfsg-3
Severity: grave
Justification: renders package unusable

Dear Maintainer,

After installing VirtualBox I get the following message:

   Loading new virtualbox-5.1.22 DKMS files...
   Building for 4.9.0-3-amd64
   Building initial module for 4.9.0-3-amd64
   Error! Bad return status for module build on kernel: 4.9.0-3-amd64 (x86_64)
   Consult /var/lib/dkms/virtualbox/5.1.22/build/make.log for more information.

Content of the log file is attached.



-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable')
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:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages virtualbox-dkms depends on:
ii  dkms  2.3-3

Versions of packages virtualbox-dkms recommends:
ii  virtualbox  5.1.22-dfsg-3

virtualbox-dkms suggests no packages.

-- no debconf information

Bug#868260: devscripts: phantom script debdiff-apply

[gregor herrmann]

Control: tag -1 + pending

On Thu, 13 Jul 2017 23:49:25 +0200, Mattia Rizzolo wrote:

> > I looked at the source package, without finding anything obvious.
> > And rebuilding the package fails without internet access in the
> > chroot (and/or with http_proxy set in the chroot).
> Yes, apparently it's not so obvious how to install a new python-based
> script, but it's already fixed in git :)
> https://anonscm.debian.org/git/collab-maint/devscripts.git/commit/?id=116beb7d45907ef9d01fea4c1907e8b8a93ef666

Ah, cool.

Actually I saw this in git but as the package doesn't build for me I
couldn't verify :)


Cheers,
gregor

-- 
 .''`.  https://info.comodo.priv.at/ - Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe
   `-   NP: Funny Van Dannen: Ich bin nicht mehr ping


signature.asc
Description: Digital Signature

Bug#868169: [debhelper-devel] Bug#868169: debhelper regression: virtualbox-dkms: Fail to build (kernel 4.1.42)

[Gianfranco Costamagna]

Hello Niels,

>I believe this will be fixed by [50366a30], which I have to pushed to
>master.  I would be happy if you can confirm this.



find . -name hm_vmx.h
./out/bin/src/vboxdrv/include/VBox/vmm/hm_vmx.h
./include/VBox/vmm/hm_vmx.h
./debian/virtualbox-dkms/usr/src/virtualbox-5.1.22/include/VBox/vmm/hm_vmx.h

I would say yes, this fixed the issue!

thanks a lot!

G.

Bug#868267: fai-client: fetch-basefile breaks for hostnames with hyphens

[Arcady Genkin]

Package: fai-client
Version: 5.3.6
Severity: normal

Dear Maintainer,

I cannot get fetch-basefile to work. Investigating, I tried running
/usr/lib/fai/fetch-basefile by hand, and it breaks in line 59

root@eddie-vm:/usr/lib/fai# ./fetch-basefile 
Fetching basefile from http://pkgmirror0.teach.cs.toronto.edu/basefiles/
./fetch-basefile: line 59: found_eddie-vm.teach.cs.toronto.edu: bad substitution
No basefile matching a class name was found at 
http://pkgmirror0.teach.cs.toronto.edu/basefiles/

Line 59 contains a Bash variable substitution "if [ X${!id} != X ]; then", I am
guessing that the hyphen in the host name is causing the problem (the hostname
is "eddie-vm.teach.cs.toronto.edu" which defines a FAI class of the same name).

Thanks!

-- 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/1 CPU core)
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 fai-client depends on:
ii  debconf-utils1.5.61
ii  file 1:5.30-1
ii  iproute2 4.9.0-1
ii  libapt-pkg-perl  0.1.32
ii  libfile-lchown-perl  0.02-2+b2
ii  perl 5.24.1-3

Versions of packages fai-client recommends:
ii  libgraph-perl  1:0.96-2

Versions of packages fai-client suggests:
pn  logtail  

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

-- no debconf information

Bug#868260: devscripts: phantom script debdiff-apply

[Mattia Rizzolo]

On Thu, Jul 13, 2017 at 10:59:43PM +0200, gregor herrmann wrote:
> d/changelog mentions a new script debdiff-apply (renamed from
> debpatch), but:
> 
> % which debdiff-apply
> debdiff-apply not found
> 
> % dpkg -L devscripts | egrep "(debpatch|debdiff-apply)"
> /usr/share/man/de/man1/debdiff-apply.1.gz
> /usr/share/man/fr/man1/debdiff-apply.1.gz
> /usr/share/man/man1/debdiff-apply.1.gz
> 
> I looked at the source package, without finding anything obvious.
> And rebuilding the package fails without internet access in the
> chroot (and/or with http_proxy set in the chroot).

Yes, apparently it's not so obvious how to install a new python-based
script, but it's already fixed in git :)

https://anonscm.debian.org/git/collab-maint/devscripts.git/commit/?id=116beb7d45907ef9d01fea4c1907e8b8a93ef666

-- 
regards,
Mattia Rizzolo

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


signature.asc
Description: PGP signature

Bug#868264: fwd

[Bastien ROUCARIÈS]

control: retitle -1 CVE-2017-11141 memory exhaustion in ReadMATImage
control: forwarded -1 https://github.com/ImageMagick/ImageMagick/issues/469

Bug#868263: fwd

[Bastien ROUCARIÈS]

control: retitle -1 CVE-2017-11166 memory exhaustion in ReadXWDImage
control: forwarded -1 https://github.com/ImageMagick/ImageMagick/issues/471

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

[Henrique de Moraes Holschuh]

On Thu, 13 Jul 2017, Adam D. Barratt wrote:
> Please go ahead.

Uploaded, thank you very much!

-- 
  Henrique Holschuh

Bug#863682: superseeding with new version

[Henrique de Moraes Holschuh]

On Thu, 13 Jul 2017, Adam D. Barratt wrote:
> > 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.
> 
> Please go ahead.

I've just uploaded it.  Thank you very much!

-- 
  Henrique Holschuh

Bug#868266: ncurses-bin,perl-doc: perldoc broken with latest ncurses

[gregor herrmann]

Package: ncurses-bin,perl-doc
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

perl-doc 5.24.1-7
ncurses-bin 6.0+20170708-1

Since the upgrade of ncurses (I'm not sure if already with 6.0+20170701-1
but for sure with 6.0+20170708-1) `perldoc $foo' doesn't work
anymore, as in: looks ugly.

To reproduce:

`perldoc perldoc' will show the same in $PAGER as `PAGER=cat perldoc
perldoc':

1NAME1
perldoc - Look up Perl documentation in Pod format.

1SYNOPSIS1
perldoc [-h] [-D] [-t] [-u] [-m] [-l] [-F]
[-i] [-V] [-T] [-r]
[-d destination_file]
[-o formatname]
[-M FormatterClassName]
[-w formatteroption:value]
[-n nroff-replacement]
[-X]
[-L language_code]
PageName|ModuleName|ProgramName|URL


So no *roff markup, and the =head1 formatted as "1$whatever1".

Niko mentioned on IRC:
"I'm guessing it's something to do with Term::Cap running infocmp -C",
so it's not clear if this is actually a bug in ncurses or in perl ...


Cheers,
gregor


-BEGIN PGP SIGNATURE-

iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAlln6B9fFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx
RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ
qgajQRAAiwf56bfBkOMEpPr9rAz3B+eABM+TjInQ1JsRSfaCe77zo9c9TypcWVe3
VIc3XUtKssadiBsDQNI3CL3O4149qgipDOgci40eeGd4L1HgGEZPpBZfiK2l2IzL
tKjqSrYUgliayDdehjKyCOM3pIt8xIuQhTHc49XO7M6vmHM9Qy+22+/37boV3nO1
8ZvIwIvLEUXhng2usimfnuqUcOO1KIGE7KGx2Nh8rvLTKWdIKNHiI1FoAcDTxsvC
6tSp/A1w8ARzZk5QEaFeeQzK3lgD1UMgZW0FRLrMm/oHHEApiDjMU2+IfDuFNYBG
xGMKmJht13Hxzs62xbbycrqQZqg0TqCthu/ttnkJrMzHHxhQyfbC8mJ/rnd5F7LK
ZZYYsYUG4u/7FXS2V71cxS2JfkbD6UvpFHqJ9Y7kTrXi3+H4Cvg7BaEnB2mbjnn7
kwX0ipRu/eE1Ipw7s3hj9Qzdm2Xq4b2thOPwSLz0B8mDrX07EnAU5z74qM/b1sEg
NMHXMtBT3n9/wIVpRpRaDFVXeaUdBSuy9hdGzoyZ5dLODe4m3oUVmDRY+MpBwWCQ
oCehnfEj78eb7Cx9Pd1EPPbDTu47bVDd3N9W8lqL85LPEqAYNNdE+bhibcUgBVKT
5OaZXc1vsFjdbmxWMeK1e83TMQ7IbZsTn5ZBOlECkBOSyKSSkgE=
=USQO
-END PGP SIGNATURE-

Bug#865224: uwsgi: ftbfs with multiple supported python3 versions

[Niko Tyni]

On Fri, Jun 30, 2017 at 10:28:09PM +0200, Jonas Smedegaard wrote:
> Quoting Scott Kitterman (2017-06-30 08:25:19)
> > On Tue, 20 Jun 2017 11:26:35 +1200 Michael Hudson-Doyle 
> >  wrote:
> > > This may well turn out to be a cdbs bug in the end, but uwsgi does 
> > > not build when pysupport -r returns more than one version:
> > > 
> > > https://launchpadlibrarian.net/323025281/buildlog_ubuntu-artful-amd64.uwsgi_2.0.15-1ubuntu3_BUILDING.txt.gz
> > > 
> > > Picking out the failing lines:
> > > 
> > > *** asyncio_python27 plugin built and available in 
> > > ./asyncio_python27_plugin.so ***
> > > touch debian/stamp-uwsgi-plugin-asyncio-python
> > > debian/rules:452: *** no python implementation resolved from flavor 
> > > "python3.6" among packages python-uwsgidecorators 
> > > python3-uwsgidecorators.  Stop.
> > > 
> > > In this build python 3.5 is the default and python 3.6 is supported. 
> > > In a build where python 3.6 is default and python 3.5 is supported, 
> > > the error complains about python 3.5 instead. And if python 3.6 is 
> > > the only supported version, the build completes successfully. So I 
> > > think this is really a problem in uwsgi or cdbs' handling of 
> > > multiple supported python versions.
> > 
> > We now have this in Debian, so bumping to serious.
> 
> Thanks, both for reporting initially and for bumping!

It looks like a cdbs issue to me,
  $(call cdbs_expand_pythonruntime,,python3.6)
breaks while
  $(call cdbs_expand_pythonruntime,,python3.5)
works (and results in "python3" as expected.)

A workaround that seems to help is putting
 X-Python3-Version: 3.5
in the Source paragraph of debian/control to prevent it from trying 3.6
at all. This makes the build work for me (but doesn't help the python3.6
transition of course.)

This is the worst blocker for the Perl 5.26 transition too (uwsgi needs
to be rebuilt because uwsgi-plugin-psgi links against libperl), so even
a temporary ugly workaround would be appreciated from this side :)
-- 
Niko Tyni   nt...@debian.org

Bug#868263: fwd

[Bastien ROUCARIÈS]

control: retitle -1 CVE-2017-11166 memory exhaustion in ReadXWDImage
control: forwarded -1 https://github.com/ImageMagick/ImageMagick/issues/471

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

Bug#868265: sane-utils: Don't recommend sane-backends-extra

[Jeremy Bicha]

Package: sane-utils
Version: 1.0.27-1~experimental1

sane-utils recommends sane-backends-extra but…

sane-backends-extra has been orphaned for years.
It contains 2 drivers, 1 for the Nikon CoolScan 5000
and the other (genius-vp2) for the Genius ColorPage-Vivid Pro II but
the geniusvp2 driver has been disabled by default for a decade.

The definition of Recommends from Debian Policy 7.2 is "This declares
a strong, but not absolute, dependency. The Recommends field should
list packages that would be found together with this one in all but
unusual installations."

I don't believe that the Recommends is appropriate here.

Also, this would allow Ubuntu to sync sane-backends-extra directly
from Debian. (sane-backends-extra is in 'universe' and it is not
permitted for a 'main' package to depend on a 'universe' package.)

Thanks,
Jeremy Bicha

Bug#868184: retitle

[Bastien ROUCARIÈS]

control: clone -1 -2
control: clone -1 -3
control: retitle -1 CVE-2017-11166 memory exhaustion in ReadTGAImage
control: retitle -2 CVE-2017-11170  memory exhaustion in ReadXWDImage
control: retitle -3 CVE-2017-11188 memory exhaustion in ReadMATImage 

CVE-2017-11188:
https://github.com/ImageMagick/ImageMagick/issues/509
is already filled

Fill remaining bug

Bug#868184: [Pkg-gmagick-im-team] Bug#868184: CVE-2017-11141 CVE-2017-11166 CVE-2017-11170 CVE-2017-11188

[Salvatore Bonaccorso]

Hi

On Thu, Jul 13, 2017 at 12:46:06AM +0200, roucaries bastien wrote:
> I suppose I have already fille bug and are under TEMP under tracker

CVE-2017-11188 should be already covered by #867806.

Regards,
Salvatore

Bug#868262: python2.7: invalid pointer (free())

[Alexander Schier]

Package: python2.7
Version: 2.7.13-2
Severity: normal

Dear Maintainer,
python 2.7 as an invalid free() when running duplicity.
My usual backup script ran like every day, but it ended with a python
crash. here is the backtrace:

*** Error in `/usr/bin/python': free(): invalid pointer:
0x7f3fc5a58fa8 ***
=== Backtrace: =
/lib/x86_64-linux-gnu/libc.so.6(+0x70bcb)[0x7f3fc8828bcb]
/lib/x86_64-linux-gnu/libc.so.6(+0x76f96)[0x7f3fc882ef96]
/lib/x86_64-linux-gnu/libc.so.6(+0x777de)[0x7f3fc882f7de]
/usr/bin/python(+0xebc28)[0x55e6f8501c28]
/usr/bin/python(+0xdce5a)[0x55e6f84f2e5a]
/usr/bin/python(+0x11e277)[0x55e6f8534277]
/usr/bin/python(+0xdce5a)[0x55e6f84f2e5a]
/usr/bin/python(+0x11e277)[0x55e6f8534277]
/usr/bin/python(+0xebbf3)[0x55e6f8501bf3]
/usr/bin/python(+0x11e277)[0x55e6f8534277]
/usr/bin/python(+0x110917)[0x55e6f8526917]
/usr/bin/python(PyEval_EvalFrameEx+0x5f10)[0x55e6f8516c40]
/usr/bin/python(PyEval_EvalFrameEx+0x5eef)[0x55e6f8516c1f]
/usr/bin/python(PyEval_EvalFrameEx+0x5eef)[0x55e6f8516c1f]
/usr/bin/python(PyEval_EvalCodeEx+0x255)[0x55e6f850f535]
/usr/bin/python(PyEval_EvalCode+0x19)[0x55e6f850f2d9]
/usr/bin/python(+0x128e3f)[0x55e6f853ee3f]
/usr/bin/python(PyRun_FileExFlags+0x82)[0x55e6f8539d52]
/usr/bin/python(PyRun_SimpleFileExFlags+0x19e)[0x55e6f853989e]
/usr/bin/python(Py_Main+0x6c1)[0x55e6f84eaaf1]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf1)[0x7f3fc87d82b1]
/usr/bin/python(_start+0x2a)[0x55e6f84ea31a]
=== Memory map: 
55e6f8416000-55e6f8739000 r-xp  fe:01 4594308
/usr/bin/python2.7
55e6f8939000-55e6f893b000 r--p 00323000 fe:01 4594308
/usr/bin/python2.7
55e6f893b000-55e6f89b2000 rw-p 00325000 fe:01 4594308
/usr/bin/python2.7
55e6f89b2000-55e6f89d5000 rw-p  00:00 0 
55e6f9a3d000-55e6fadb3000 rw-p  00:00 0
[heap]
7f3fbf10e000-7f3fbff0e000 rw-p  00:00 0 
7f3fc000-7f3fc0021000 rw-p  00:00 0 
7f3fc0021000-7f3fc400 ---p  00:00 0 
7f3fc4019000-7f3fc4119000 rw-p  00:00 0 
7f3fc41f-7f3fc42b rw-p  00:00 0 
7f3fc42f7000-7f3fc4377000 rw-p  00:00 0 
7f3fc4394000-7f3fc43aa000 r-xp  fe:01 5505901
/lib/x86_64-linux-gnu/libgcc_s.so.1
7f3fc43aa000-7f3fc45a9000 ---p 00016000 fe:01 5505901
/lib/x86_64-linux-gnu/libgcc_s.so.1
7f3fc45a9000-7f3fc45aa000 r--p 00015000 fe:01 5505901
/lib/x86_64-linux-gnu/libgcc_s.so.1
7f3fc45aa000-7f3fc45ab000 rw-p 00016000 fe:01 5505901
/lib/x86_64-linux-gnu/libgcc_s.so.1
7f3fc45ab000-7f3fc45b6000 r-xp  fe:01 5505945
/lib/x86_64-linux-gnu/libnss_nis-2.24.so
7f3fc45b6000-7f3fc47b5000 ---p b000 fe:01 5505945
/lib/x86_64-linux-gnu/libnss_nis-2.24.so
7f3fc47b5000-7f3fc47b6000 r--p a000 fe:01 5505945
/lib/x86_64-linux-gnu/libnss_nis-2.24.so
7f3fc47b6000-7f3fc47b7000 rw-p b000 fe:01 5505945
/lib/x86_64-linux-gnu/libnss_nis-2.24.so
7f3fc47b7000-7f3fc47f7000 rw-p  00:00 0 
7f3fc4917000-7f3fc4957000 rw-p  00:00 0 
7f3fc49ff000-7f3fc4a13000 r-xp  fe:01 5505935
/lib/x86_64-linux-gnu/libnsl-2.24.so
7f3fc4a13000-7f3fc4c13000 ---p 00014000 fe:01 5505935
/lib/x86_64-linux-gnu/libnsl-2.24.so
7f3fc4c13000-7f3fc4c14000 r--p 00014000 fe:01 5505935
/lib/x86_64-linux-gnu/libnsl-2.24.so
7f3fc4c14000-7f3fc4c15000 rw-p 00015000 fe:01 5505935
/lib/x86_64-linux-gnu/libnsl-2.24.so
7f3fc4c15000-7f3fc4c57000 rw-p  00:00 0 
7f3fc4c8e000-7f3fc4d0e000 rw-p  00:00 0 
7f3fc4d0e000-7f3fc4d15000 r-xp  fe:01 5505936
/lib/x86_64-linux-gnu/libnss_compat-2.24.so
7f3fc4d15000-7f3fc4f14000 ---p 7000 fe:01 5505936
/lib/x86_64-linux-gnu/libnss_compat-2.24.so
7f3fc4f14000-7f3fc4f15000 r--p 6000 fe:01 5505936
/lib/x86_64-linux-gnu/libnss_compat-2.24.so
7f3fc4f15000-7f3fc4f16000 rw-p 7000 fe:01 5505936
/lib/x86_64-linux-gnu/libnss_compat-2.24.so
7f3fc4f16000-7f3fc6316000 rw-p  00:00 0 
7f3fc6316000-7f3fc6326000 r-xp  fe:01 4858701
/usr/lib/python2.7/lib-dynload/_json.x86_64-linux-gnu.so
7f3fc6326000-7f3fc6525000 ---p 0001 fe:01 4858701
/usr/lib/python2.7/lib-dynload/_json.x86_64-linux-gnu.so
7f3fc6525000-7f3fc6526000 r--p f000 fe:01 4858701
/usr/lib/python2.7/lib-dynload/_json.x86_64-linux-gnu.so
7f3fc6526000-7f3fc6527000 rw-p 0001 fe:01 4858701
/usr/lib/python2.7/lib-dynload/_json.x86_64-linux-gnu.so
7f3fc6527000-7f3fc6528000 ---p  00:00 0 
7f3fc6528000-7f3fc6de8000 rw-p  00:00 0 
7f3fc6de8000-7f3fc6dec000 r-xp  fe:01 4858743
/usr/lib/python2.7/lib-dynload/termios.x86_64-linux-gnu.so
7f3fc6dec000-7f3fc6feb000 ---p 4000 fe:01 4858743
/usr/lib/python2.7/lib-dynload/termios.x86_64-linux-gnu.so
7f3fc6feb000-7f3fc6fec000 r--p 3000 fe:01 4858743
/usr/lib/python2.7/lib-dynload/termios.x86_64-linux-gnu.so
7f3fc6fec000-7f3fc6fee000 rw-p 4000 fe:01 4858743
/usr/lib/python2.7/lib-dynload/termios.x86_64-linux-gnu.so
7f3fc6fee000-7f3fc702e000 rw-p  00:00 0 
7f3fc702e000-7f3fc703b000 r-xp  fe:01 4616899
/usr/lib/x86_64-linux-gnu/librsync.so.1.0.2

Bug#868259: opendkim: systemctl does not create $RUNDIR

[Martin Godisch]

retitle 868259 opendkim: please add permissions configuration for $RUNDIR
thanks

It is impossible to configure other permissions than 0750 for $RUNDIR,
since it is hard-coded in /lib/opendkim/opendkim.service.generate.

I need it to grant postfix access to the opendkim unix socket. I cannot
add the postfix user to the opendkim group. opendkim will complain about
postfix being able to read its private key then. opendkim also refuses
to create its socket in /var/spool/postfix/private, as opendmarc,
policy-spf, postgrey etc. do. How to do this with opendkim?

Kind regards,

Martin

On Thu, Jul 13, 2017 at 22:56:06 +0200, Martin Godisch wrote:

> Package: opendkim
> Version: 2.11.0~alpha-10
> Severity: normal
> 
> If $RUNDIDR does not exist, "systemctl start opendkim.service" does not
> create it and fails.
> 
> Kind regards,
> 
> Martin

Bug#868260: devscripts: phantom script debdiff-apply

[gregor herrmann]

Package: devscripts
Version: 2.17.8
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

d/changelog mentions a new script debdiff-apply (renamed from
debpatch), but:

% which debdiff-apply
debdiff-apply not found

% dpkg -L devscripts | egrep "(debpatch|debdiff-apply)"
/usr/share/man/de/man1/debdiff-apply.1.gz
/usr/share/man/fr/man1/debdiff-apply.1.gz
/usr/share/man/man1/debdiff-apply.1.gz


I looked at the source package, without finding anything obvious.
And rebuilding the package fails without internet access in the
chroot (and/or with http_proxy set in the chroot).


Cheers,
gregor

-BEGIN PGP SIGNATURE-

iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAlln3z9fFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx
RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ
qgbPEQ/8D4xFpxYkogjYwUJu5PP8mt39LSRtjaYvw/t55SM3JOuIO+MCjQRpWTXc
mvlq6gC4l7+gB+JGkYmKOLiF6okq+VAWNyDtEJ7O3bUN6mi0nLwEoKaZzsBSuuaX
eQ3ndjcBkx8SP8ot6By2ywzRK+T3gYg5rWca3tMHzQfUqEXOgQ3QLcrOXLgIfVyr
vQtBCHv6FOO76CzCpVd8wjx9JLwFWuPtpDiT7GIYnMT0YG1MwJKbY1vCG0Yp3O6X
rMJR2dZOfPS3u1oOSsp/pOr0fWfQf9T7ODcFh+DTsY4kJ9uCdMkJLEzchbvQ7T1D
7maGLs+GLbxkKtclxcQNRuM2yIGpF/hwitRBXafK2UySWYsixxZirtstGaPbSLju
EdD+Z7/jFnq5JVvTpBtQR9sYjXxi/HfUOc+Q2P5ojMnVd3tF4nF6TMQt2ydpVs4k
wjLZBMgCYtXGCyA9uXPBkblYd1xWB49j+HQUoDZz62Lc8tbFHZflw17tacaiVvnp
T6Eyuy/G1xX/pjXY8TwYrihdJSknVyVemnZcrI8A9c4l9vMLNCWvCusOwNbclJVJ
wnmUm6UaMpfs4IPUrfXvskfaJ/HQkFe/fGJACnpLLzSXtDKx43n+GbNwkuo9Y7F2
wTRSWuE3ex3Fi2WrX52JsFMA/II7A/BqyW2krcxlxSb9Kau48ps=
=9L5R
-END PGP SIGNATURE-

Bug#868261: ansible: hostname module fails with "Failed to create bus connection: Connection refused" if dbus is not installed on remote machine

[Axel Beckert]

Package: ansible
Version: 2.2.1.0-2
Control: forwarded -1 https://github.com/ansible/ansible/issues/25543

Dear Maintainer,

the following trivial task fails if dbus is not installed on a remote
machine (e.g. a server):

- name: Set the hostname
  hostname:
name: "{{ ansible_host }}"

It fails as follows despite dbus is (obviously) not necessary to set the
hostname under Linux:

fatal: […]: FAILED! => {"changed": false, "failed": true, "msg": "Command 
failed rc=1, out=, err=Failed to create bus connection: Connection refused\n"}

If dbus is installed on the remote machine, the module works
fine. According to the upstream bug report at
https://github.com/ansible/ansible/issues/25543 this only happens with
systemd as init system (or at least if systemd is installed and dbus is
not).

-- 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/8 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: sysvinit (via /sbin/init)

Versions of packages ansible depends on:
ii  python2.7.13-2
ii  python-crypto 2.6.1-7
ii  python-httplib2   0.9.2+dfsg-1
ii  python-jinja2 2.8-1
ii  python-netaddr0.7.18-2
ii  python-paramiko   2.0.0-1
ii  python-pkg-resources  33.1.1-1
ii  python-yaml   3.12-1

Versions of packages ansible recommends:
ii  python-kerberos   1.1.5-2+b2
ii  python-selinux2.6-3+b1
pn  python-winrm  
ii  python-xmltodict  0.10.2-1

Versions of packages ansible suggests:
ii  cowsay   3.03+dfsg2-3
ii  sshpass  1.06-1

-- no debconf information

Bug#868259: opendkim: systemctl does not create $RUNDIR

[Martin Godisch]

Package: opendkim
Version: 2.11.0~alpha-10
Severity: normal

If $RUNDIDR does not exist, "systemctl start opendkim.service" does not
create it and fails.

Kind regards,

Martin

Bug#866950: fontconfig: upgrade radically changes font-rendering style with no warning or hint of how to revert

[Bob Bib]

On Wed, 12 Jul 2017 23:44:42 -0300 Adriano Vilela Barbosa 
 wrote:

On Sat, 8 Jul 2017 09:41:02 +0200 Laurent Bigonville  wrote:
> Le 08/07/17 à 00:30, Soeren D. Schulze a écrit :
> >>> Changing the value in debconf question in fontconfig also helped,
> >>> correct?
> >>
> >> In my case (fontconfig 2.12.3-0.2, libfreetype6 2.8-0.2), setting
> >> FREETYPE_PROPERTIES was not enough. Only after I've also
> >> dpkg-reconfigured fontconfig to 'Full' hinting style everything got back
> >> to normal (pre 2.12 style).
> >
> > I can confirm this.  You need both full hinting in debconf as well as
> > having FREETYPE_PROPERTIES set.  Having only one of them does not do
> > anything.
> OK thanks for the precisions. I'll upload my fontconfig update and clone
> this bug
>
>

Hi,

I also follow testing and started seeing this after a dist-upgrade
yesterday (I hadn't done any upgrades since the release of stretch).
Some applications weren't affected by the upgrade (e.g., Gimp). Others
(e.g., Firefox) were affected by could be fixed by upgrading
fontconfig to 2.12.3-0.2 and setting FREETYPE_PROPERTIES. And there is
a third group of applications (all KDE applications, Emacs) that could
only be fixed by downgrading libfreetype6 to 2.6.3-3.2.

Adriano




BTW, for freetype, it's bug #867657...

--
Best wishes,
Bob

Bug#774553: exim4: Do not scan outgoing mail for spam

[Alexander Wirt]

On Thu, 13 Jul 2017, Andreas Metzler wrote:

> On 2017-07-13 Alexander Wirt  wrote:
> > On Thu, 13 Jul 2017, Marc Haber wrote:
> 
> >> On Thu, Jul 13, 2017 at 08:47:56AM +0200, Alexander Wirt wrote:
> >>> I am talking about the report:
> >>> X-Amavis-Alert: BAD HEADER SECTION, Improper folded header field made up
> >>> entirely of whitespace (char 20 hex): X-Spam_report: ...T_ADDRESS@@
> >>> for details.  Content previ[...]
>  
> >> Just making sure, this is a report generated by Amavis on
> >> lists.debian.org, not on the bug reporter's exim, right?
> > No. Its generated by the spamd exim is calling. No amavis involved. It just
> > catches the broken header on arrival. 
> 
> What we are trying to point out is that exim does not add an
> "X-Amavis-Alert" header. Is your issue about a broken "X-Amavis-Alert"
> header or is it about an X-Spam_report that amavis does not like?
It is about Exim/Spamassassin adding non rfc conform headers. 

"No amavis involved. It just catches the broken header on arrival."

Please forget you ever heard amavis. 

Alex

Bug#868258: Patches or pull request before updating to 4.11.1

[Nicholas D Steeves]

Package: btrfs-progs
Version: 4.9.1-1

Hi Dmitri,

Attached are a number of patches against 4.9.1-1.

I took care to ensure that you could merge the batch of them, then
merge a new upstream version, then dch -r, and finally add your "New
Upstream version (Closes: #867146)" line at the top.

The importance varies from patch to patch.  If you prefer to pull from
a git remote, pull from:

git remote add -t proposed sten0 g...@github.com:sten0/btrfs-progs.git

Summary (Important, Normal, Minor, Wishlist):

I 0001-Override-dh_auto_clean-to-work-around-upstream-bug-w.patch
N 0002-Ignore-.pc-the-quilt-state-tracking-dir.patch
  * I read that this is supposed to be standard in dgit repos
I 0003-Drop-btrfs-convert-Closes-824895-854489.patch
  * And also apply this for stretch-update
N 0004-Move-all-binaries-back-to-sbin-Closes-786893.patch
  * Completely up to you, of course ;-)
N 0005-Update-Source-because-Chris-Mason-s-branch-hasn-t-be.patch
I 0006-Exclude-non-free-RFC-BCP78-files-affects-test-suite.patch
I 0007-4.6.1-1-did-not-fix-package-license.patch
  * And also apply this for stretch-update
I 0008-Add-dversionmangle-to-handle-dfsg-version-suffix.patch
I 0009-Update-copyright-for-new-locations-of.patch
  * And also apply this for stretch-update
W 0010-d-control-add-whitespace-cosmetic-fix.patch
N 0011-debian-watch-Switch-to-version-4-and-add-repacksuffi.patch
N 0012-Drop-btrfs-tools-transitional-dummy-package.patch
  * Can be safely dropped now
N 0013-Switch-to-automatically-generated-dbgsym-package.patch
  * No time like the present, right? :-)
N 0014-Bump-compat-to-10.patch
  * apply either both 13 and 14 or drop both
N 0015-Update-changelog.patch
  * Please delete entries for patches you reject


Sincerely,
Nicholas
>From a2f1850869b63e1244778718f620accdf81c9c79 Mon Sep 17 00:00:00 2001
From: Nicholas D Steeves 
Date: Sat, 11 Mar 2017 20:04:35 -0500
Subject: [PATCH 01/15] Override dh_auto_clean to work around upstream bug
 where make clean cannot be run before ./configure

---
 debian/rules | 5 +
 1 file changed, 5 insertions(+)

diff --git a/debian/rules b/debian/rules
index 265ef280..6be097c8 100755
--- a/debian/rules
+++ b/debian/rules
@@ -36,3 +36,8 @@ override_dh_auto_test:
 
 override_dh_strip:
 	dh_strip --dbg-package=btrfs-progs-dbg
+
+override_dh_auto_clean:
+	if test -f Makefile.inc; then \
+		dh_auto_clean; \
+	fi
-- 
2.11.0

>From dbf42a8606559212902f628cd71b69aba0cd4376 Mon Sep 17 00:00:00 2001
From: Nicholas D Steeves 
Date: Sat, 11 Mar 2017 20:27:13 -0500
Subject: [PATCH 02/15] Ignore .pc, the quilt state tracking dir

---
 .gitignore | 1 +
 1 file changed, 1 insertion(+)

diff --git a/.gitignore b/.gitignore
index 98b3657b..ba8c8590 100644
--- a/.gitignore
+++ b/.gitignore
@@ -76,3 +76,4 @@ stamp-h.in
 stamp-h1
 config/*
 
+.pc
-- 
2.11.0

>From f714d2925caed58936d6e068ca206cf40499af37 Mon Sep 17 00:00:00 2001
From: Nicholas D Steeves 
Date: Sat, 11 Mar 2017 20:34:22 -0500
Subject: [PATCH 03/15] Drop btrfs-convert (Closes: #824895, #854489)

Rationale: the test failed
...
[TEST]   convert-tests.sh
[TEST/conv]   001-ext2-basic
[TEST/conv] ext2 4k nodesize, btrfs defaults
failed: /scratch/btrfs-progs-v4.10/btrfs-convert --rollback /scratch/btrfs-progs-v4.10/tests/test.img
test failed for case 001-ext2-basic
Makefile:271: recipe for target 'test-convert' failed
make: *** [test-convert] Error 1
---
 debian/rules | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/debian/rules b/debian/rules
index 6be097c8..f6181164 100755
--- a/debian/rules
+++ b/debian/rules
@@ -19,7 +19,7 @@ override_dh_autoreconf:
 	dh_autoreconf ./autogen.sh
 
 override_dh_auto_configure:
-	dh_auto_configure -- --bindir=/bin
+	dh_auto_configure -- --bindir=/bin --disable-convert
 
 override_dh_auto_build:
 	dh_auto_build -- V=1
-- 
2.11.0

>From 568af50aee8a58dbfc5ac21f3a6a623cc0c54e29 Mon Sep 17 00:00:00 2001
From: Nicholas D Steeves 
Date: Sat, 11 Mar 2017 21:14:15 -0500
Subject: [PATCH 04/15] Move all binaries back to /sbin (Closes: #786893)

---
 debian/btrfs-progs-udeb.install | 4 ++--
 debian/rules| 2 +-
 2 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/debian/btrfs-progs-udeb.install b/debian/btrfs-progs-udeb.install
index 3effab9e..f06a6498 100644
--- a/debian/btrfs-progs-udeb.install
+++ b/debian/btrfs-progs-udeb.install
@@ -1,2 +1,2 @@
-btrfs		/bin
-mkfs.btrfs	/bin
+btrfs		/sbin
+mkfs.btrfs	/sbin
diff --git a/debian/rules b/debian/rules
index f6181164..0ac43c76 100755
--- a/debian/rules
+++ b/debian/rules
@@ -19,7 +19,7 @@ override_dh_autoreconf:
 	dh_autoreconf ./autogen.sh
 
 override_dh_auto_configure:
-	dh_auto_configure -- --bindir=/bin --disable-convert
+	dh_auto_configure -- --bindir=/sbin --disable-convert
 
 override_dh_auto_build:
 	dh_auto_build -- V=1
-- 
2.11.0

>From e87b785f7b137221212148f2083a0755803f6cb7 Mon Sep 17 00:00:00 2001
From: Nicholas D 

Bug#864508: btrfs-progs: Please consider upgrading btrfs-progs to match the kernel in Stretch

[Nicholas D Steeves]

Control: owner -1 !
Control: block -1 by 868254

On Fri, Jun 09, 2017 at 07:28:11PM +0200, waxhead wrote:
> 
> > On Fri, 09 Jun 2017 19:12:51 +0200 Svein Engelsgjerd
> >  wrote:
> > > Package: btrfs-progs
> > > Version: 4.7.3-1
> > > Severity: wishlist
> > > 
> > > Dear Maintainer,
> > > 
> > > btrfs-progs in Stretch is v4.7.3
> > > The kernel is 4.9.25-1
[...]
> > > Lots of fixes since 4.7.3 - the changelog is here:
> > > https://btrfs.wiki.kernel.org/index.php/Changelog#btrfs-progs_4.7.1_.28Aug_2016.29
> > > 
> > > Please consider pulling in the latest btrfs-progs in Stretch
> > > 
> > > [...]
> > Hi Svein,
> > 
> > The maintainer requested this in #855121 and it was rejected by the
> > release team.
> > 
> > Thanks,
> > ~Niels
> I think it is a wrong decision, but ok. Read and understood.
> Good luck with releasing Stretch :)

Hi Svein,

I will provide a backport of btrfs-progs for stretch as I am already
doing for jessie.  https://backports.debian.org/Instructions/

The jessie-backport version must never be greater than the version in
stretch, and the stretch-backport will be a couple of days behind the
version in testing.  The version in testing will usually be five days
behind the version in unstable, but this changes during a freeze.

The unblock request denied by release team wouldn't have been
necessary if the version in unstable was kept up to date.

Sincerely,
Nicholas

Bug#867538: fop: Please implement sidebars floating at the side of the body of the text

[Petter Reinholdtsen]

Control: reopen -1
Control: forward -1 https://issues.apache.org/jira/browse/FOP-2727

[Mathieu Malaterre]
> Please re-open and forward it upstream.

Done.

-- 
Happy hacking
Petter Reinholdtsen

Bug#868257: opendkim: opendkim.service.generate fails to generate override.conf

[Martin Godisch]

Package: opendkim
Version: 2.11.0~alpha-10
Severity: normal

If /etc/systemd/system/opendkim.service.d/override.conf exists with some
non-standard configuration and /etc/default/opendkim is reset to the
standard configuration then /lib/opendkim/opendkim.service.generate
fails to adjust (or: remove) the non-standard override.conf because of
this condition

if [ "$SOCKET" != "$_SOCKET" ] || [ "$RUNDIR" != "$_RUNDIR" ] || [
"$DAEMON_OPTS" != "" ] ...

which detects a standard setup in /etc/default/opendkim and erroneously
thinks there is nothing to do.

Kind regards,

Martin

Bug#741889: Sort kernels by version in 90fallback, newest first.

[Samuel Rakitničan]

Dear maintainers,

Please accept attached patch that should fix this behavior.

I am using coreutils sort to sort the list by version. As it is turning
this:

/dev/sdb5:/dev/sdb5::/boot/vmlinuz-4.10.0-0.rc2.git2.1.fc26.x86_64:/boot/initramfs-4.10.0-0.rc2.git2.1.fc26.x86_64.img:root=/dev/sdb5
/dev/sdb5:/dev/sdb5::/boot/vmlinuz-4.11.0-2.fc26.x86_64:/boot/initramfs-4.11.0-2.fc26.x86_64.img:root=/dev/sdb5
/dev/sdb5:/dev/sdb5::/boot/vmlinuz-4.9.0-0.rc0.git7.1.fc26.x86_64:/boot/initramfs-4.9.0-0.rc0.git7.1.fc26.x86_64.img:root=/dev/sdb5

Into this

/dev/sdb5:/dev/sdb5::/boot/vmlinuz-4.11.0-2.fc26.x86_64:/boot/initramfs-4.11.0-2.fc26.x86_64.img:root=/dev/sdb5
/dev/sdb5:/dev/sdb5::/boot/vmlinuz-4.10.0-0.rc2.git2.1.fc26.x86_64:/boot/initramfs-4.10.0-0.rc2.git2.1.fc26.x86_64.img:root=/dev/sdb5
/dev/sdb5:/dev/sdb5::/boot/vmlinuz-4.9.0-0.rc0.git7.1.fc26.x86_64:/boot/initramfs-4.9.0-0.rc0.git7.1.fc26.x86_64.img:root=/dev/sdb5


That change is necessary for grub2 to keep the most recent kernel in main
menu.


Also, I am not sure how it is working for other distributions, but on
Fedora I am seeing the same description for main menu, as well as
sub-menus. I was thinking that in this case it should return only the most
recent kernel.
From a725d9d91b92aaa3a1a3332824191a03c91bc4e6 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Samuel=20Rakitni=C4=8Dan?= 
Date: Thu, 13 Jul 2017 21:57:48 +0200
Subject: [PATCH] Sort kernels by version in 90fallback, newest first. Closes:
 #741889

---
 linux-boot-probes/mounted/common/90fallback | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/linux-boot-probes/mounted/common/90fallback b/linux-boot-probes/mounted/common/90fallback
index 9ff78e1..5692d90 100755
--- a/linux-boot-probes/mounted/common/90fallback
+++ b/linux-boot-probes/mounted/common/90fallback
@@ -19,7 +19,7 @@ for kernpat in /vmlinuz /vmlinux /boot/vmlinuz /boot/vmlinux "/boot/vmlinuz*" \
 	else
 		kernbootpart="$partition"
 	fi
-	for kernfile in $(eval ls "$mpoint$kernpat" 2>/dev/null); do
+	for kernfile in $(eval ls "$mpoint$kernpat" 2>/dev/null | sort -rV); do
 		kernbasefile=$(echo "$kernfile" | sed "s!^$mpoint!!")
 		if [ -f "$kernfile" ] && [ ! -L "$kernfile" ]; then
 			initrdname=$(echo "$kernfile" | sed "s/vmlinu[zx]/initrd\*/")
-- 
2.9.4

Bug#868256: sendxmpp: does not sending any message

[Joao Eriberto Mota Filho]

Package: sendxmpp
Version: 1.23-1.1
Severity: grave
Tags: upstream
Justification: renders package unusable

sendxmpp is unusable now. It was tested over Debian Stretch/Sid.

root@crazy:~# echo ok | sendxmpp --tls-ca-path=/etc/ssl/certs/ -t 
eribe...@xyz.abc
Use of uninitialized value $sid in hash element at 
/usr/share/perl5/XML/Stream.pm line 1829.
Use of uninitialized value $sid in concatenation (.) or string at 
/usr/share/perl5/XML/Stream.pm line 2740.
Use of uninitialized value $sid in hash element at 
/usr/share/perl5/XML/Stream.pm line 2742.
Use of uninitialized value $sid in concatenation (.) or string at 
/usr/share/perl5/XML/Stream.pm line 1668.
Use of uninitialized value $sid in hash element at 
/usr/share/perl5/XML/Stream.pm line 1669.
Use of uninitialized value in concatenation (.) or string at 
/usr/share/perl5/XML/Stream.pm line 1669.
Use of uninitialized value $sid in hash element at 
/usr/share/perl5/XML/Stream.pm line 1671.
Use of uninitialized value $sid in hash element at 
/usr/share/perl5/XML/Stream.pm line 1673.
Use of uninitialized value in numeric eq (==) at /usr/share/perl5/XML/Stream.pm 
line 1673.
Use of uninitialized value $sid in hash element at 
/usr/share/perl5/XML/Stream.pm line 1675.
Use of uninitialized value $sid in hash element at 
/usr/share/perl5/XML/Stream.pm line 1678.
Use of uninitialized value $sid in hash element at 
/usr/share/perl5/XML/Stream.pm line 2620.
Use of uninitialized value $sid in concatenation (.) or string at 
/usr/share/perl5/XML/Stream.pm line 2740.
Use of uninitialized value $sid in hash element at 
/usr/share/perl5/XML/Stream.pm line 2742.
Use of uninitialized value in concatenation (.) or string at 
/usr/share/perl5/XML/Stream.pm line 1440.
Use of uninitialized value in numeric eq (==) at /usr/share/perl5/XML/Stream.pm 
line 1443.
Use of uninitialized value within %status in numeric eq (==) at 
/usr/share/perl5/XML/Stream.pm line 1506.
Use of uninitialized value in subtraction (-) at /usr/share/perl5/XML/Stream.pm 
line 1507.
Use of uninitialized value in concatenation (.) or string at 
/usr/share/perl5/XML/Stream.pm line 1669.
Use of uninitialized value in numeric eq (==) at /usr/share/perl5/XML/Stream.pm 
line 1673.
Use of uninitialized value in hash element at 
/usr/share/perl5/Net/XMPP/Connection.pm line 433.
Use of uninitialized value in hash element at 
/usr/share/perl5/Net/XMPP/Connection.pm line 440.
Use of uninitialized value in hash element at 
/usr/share/perl5/Net/XMPP/Connection.pm line 433.
Use of uninitialized value in string eq at /usr/bin/sendxmpp line 496.
Error 'AuthSend': [?]
Use of uninitialized value $sid in concatenation (.) or string at 
/usr/share/perl5/XML/Stream.pm line 1668.
Use of uninitialized value $sid in hash element at 
/usr/share/perl5/XML/Stream.pm line 1669.
Use of uninitialized value $sid in hash element at 
/usr/share/perl5/XML/Stream.pm line 1671.
Use of uninitialized value $sid in hash element at 
/usr/share/perl5/XML/Stream.pm line 1673.
Use of uninitialized value $sid in hash element at 
/usr/share/perl5/XML/Stream.pm line 1266.
Use of uninitialized value in string eq at /usr/share/perl5/XML/Stream.pm line 
1266.
Use of uninitialized value $sid in hash element at 
/usr/share/perl5/XML/Stream.pm line 1266.
Use of uninitialized value in string eq at /usr/share/perl5/XML/Stream.pm line 
1266.
Use of uninitialized value $sid in hash element at 
/usr/share/perl5/XML/Stream.pm line 1267.
Use of uninitialized value in delete at /usr/share/perl5/XML/Stream.pm line 
1267.
Use of uninitialized value $sid in hash element at 
/usr/share/perl5/XML/Stream.pm line 1268.
Use of uninitialized value $sid in hash element at 
/usr/share/perl5/XML/Stream.pm line 1270.
Use of uninitialized value $sid in hash element at 
/usr/share/perl5/XML/Stream.pm line 1270.
Use of uninitialized value $sid in hash element at 
/usr/share/perl5/XML/Stream.pm line 1270.
Use of uninitialized value $sid in hash element at 
/usr/share/perl5/XML/Stream.pm line 1270.
Use of uninitialized value $sid in hash element at 
/usr/share/perl5/XML/Stream.pm line 1270.
Use of uninitialized value $sid in delete at /usr/share/perl5/XML/Stream.pm 
line 1272.

Regards,

Eriberto

-- 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/8 CPU cores)
Locale: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8), 
LANGUAGE=pt_BR:pt:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages sendxmpp depends on:
pn  libnet-xmpp-perl  
ii  perl  5.24.1-3

sendxmpp recommends no packages.

sendxmpp suggests no packages.

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

[Adam D. Barratt]

Control: tags -1 + confirmed

On Mon, 2017-07-10 at 18:30 -0300, Henrique de Moraes Holschuh wrote:

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

Please go ahead.

Regards,

Adam

Bug#863682: superseeding with new version

[Adam D. Barratt]

Control: tags -1 + confirmed

On Mon, 2017-07-10 at 18:19 -0300, Henrique de Moraes Holschuh wrote:
> 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.

Please go ahead.

Regards,

Adam

Bug#867190: stretch-pu: package apt/1.4.7

[Adam D. Barratt]

Control: tags -1 -moreinfo +confirmed

On Sun, 2017-07-09 at 17:08 +0200, Julian Andres Klode wrote:
> The first one by David, the second by me, so this would end up
> something like the following (order may be different, it's auto-generated
> from git commits):
> 
> apt (1.4.7) stretch; urgency=medium
> 
>   [ Robert Luberda ]
>   * fix a "critical" typo in old changelog entry (Closes: 866358)
> 
>   [ David Kalnischkies ]
>   * use port from SRV record instead of initial port
>   * travis: ignore profiling warning in progress lines
>  
> 
>   [ Julian Andres Klode ]
>   * Reset failure reason when connection was successful

maybe "... ensuring errors are correctly reported" or something similar?

>   * debian/gbp.conf: Set debian-branch to 1.4.y
>   * http: Do not try reading content if Content-Length is 0
>   * travis: Migrate to Docker
>   * Release 1.4.7 (LP: #1702326)

Having the release item at the end looks slightly odd, imho. :-)

Please feel free to upload something like the above (bearing in mind
that the window for 9.1 closes this weekend).

Regards,

Adam

Bug#868255: openjdk-9: Please build with --with-debug-level=slowdebug on Zero-only architectures

[John Paul Adrian Glaubitz]

Source: openjdk-9
Version: 9~b177-3
Severity: normal

Hi!

openjdk-9 currently FTBFS on architectures which exclusively rely on the Zero
VM. This happens because the JVM segfaults during build at some point [1].

The exact reason for the segmentation fault has not been discovered yet, but
we know that building with "--with-debug-level=slowdebug" instead of "=release"
resolves the issue.

Thus, I suggest building openjdk-9 on Zero-only architectures for the time
being as a work-around.

Thanks,
Adrian

> [1] http://mail.openjdk.java.net/pipermail/hotspot-dev/2017-June/027117.html

--
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

Bug#868254: RFS: btrfs-progs/4.9.1-1~bpo9+1 [I intend to keep the bpo up-to-date]

[Nicholas D Steeves]

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my no-change bpo of "btrfs-progs".

 * Package name: btrfs-progs
   Version : 4.9.1-1~bpo9+1
   Section : admin

It builds these binary packages:

  btrfs-progs - Checksumming Copy on Write Filesystem utilities
  btrfs-progs-dbg - Checksumming Copy on Write Filesystem utilities (debug)
  btrfs-progs-udeb - Checksumming Copy on Write Filesystem utilities (udeb) 
(udeb)
  btrfs-tools - transitional dummy package
  btrfs-tools-dbg - transitional dummy package

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

  https://mentors.debian.net/package/btrfs-progs


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

  dget -x 
https://mentors.debian.net/debian/pool/main/b/btrfs-progs/btrfs-progs_4.9.1-1~bpo9+1.dsc


Alternatively, one can use the stretch-backports branch of my git repo:

   git clone -b stretch-backports --single-branch 
g...@github.com:sten0/btrfs-progs.git


Changes since the last upload:

btrfs-progs (4.9.1-1~bpo9+1) stretch-backports; urgency=medium

  * Rebuild for stretch-backports. (Closes: #864508)

 -- Nicholas D Steeves   Thu, 13 Jul 2017 15:28:09 -0400

btrfs-progs (4.9.1-1) unstable; urgency=medium


Thank you,
Nicholas

Bug#867104: wanna-build issue with src:perl versioned Provides

[gregor herrmann]

On Thu, 13 Jul 2017 08:49:06 +0200, Ralf Treinen wrote:

> On Tue, Jul 11, 2017 at 11:43:08PM +0200, gregor herrmann wrote:
> > Now that all cases, including the 6th one, are clear, is there
> > anything that's missing before the behaviour of dose-builddebcheck
> > can be adapted?
> I am working on it. -Ralf.

Excellent, thanks alot! 


Cheers,
gregor

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


signature.asc
Description: Digital Signature

Bug#867335: stretch-pu: package systemd/232-25

[Adam D. Barratt]

Control: tags -1 + confirmed d-i

On Wed, 2017-07-05 at 23:25 +0200, Michael Biebl wrote:
> systemd (232-25+deb9u1) stretch; urgency=medium
> 
>   [ Dimitri John Ledkov ]
>   * Fix out-of-bounds write in systemd-resolved.
> CVE-2017-9445 (Closes: #866147, LP: #1695546)
[...]
>   [ Michael Biebl ]
>   * Be truly quiet in systemctl -q is-enabled (Closes: #866579)
[...]
>   * Improve RLIMIT_NOFILE handling.
> Use /proc/sys/fs/nr_open to find the current limit of open files
> compiled into the kernel instead of using a hard-coded value of 65536
> for RLIMIT_NOFILE. (Closes: #865449)
[...]
>   [ Nicolas Braud-Santoni ]
>   * debian/extra/rules: Use updated U2F ruleset.
> This ruleset comes from Yubico's libu2f-host. (Closes: #824532)

I'm okay with the diff, but as mentioned:

> The changes shouldn't affect the installer. CCed debian-boot nonetheless for
> a KiBi ack.

Regards,

Adam

Bug#868253: libpoe-component-client-mpd-perl: FTBFS: test suite failures

[Niko Tyni]

Package: libpoe-component-client-mpd-perl
Version: 2.001-1
Severity: serious

This package fails to build from source on current sid due to
testsuite failures. The build also hangs for me consistently, though
tests.reproducible-builds.org seems to get past that every now and then.

This probably regressed with the new mpd around 2017-06-19.

Log excerpt (ending with a SIGINT after hanging for ten minutes or so):

  t/21-conn-non_mpd.t .. 
  1..1
  ok 1 - wrong server
  ok
  Can't locate object method "duration" via package 
"Audio::MPD::Common::Item::Song" at 
/<>/blib/lib/POE/Component/Client/MPD/Connection.pm line 228.
  # Looks like you planned 34 tests but ran 9.
  t/23-conn-dialog.t ... 
  1..34
  ok 1 - got a mpd_error event
  ok 2 - unknown command
  ok 3 - got a mpd_error event
  ok 4 - bad password
  ok 5 - got a mpd_data event
  ok 6 - no error message
  ok 7 - got a mpd_data event
  ok 8 - no error message
  ok 9 - commands return stuff
  Dubious, test returned 255 (wstat 65280, 0xff00)
  Failed 25/34 subtests 
  [...]
  t/43-cmds-settings.t . 
  1..30
  ok 1 - command 'repeat' returned an ok status
  ok 2 - command 'status' returned an ok status
  ok 3 - repeat is on
  ok 4 - command 'repeat' returned an ok status
  ok 5 - command 'status' returned an ok status
  ok 6 - repeat is off
  ok 7 - command 'repeat' returned an ok status
  ok 8 - command 'status' returned an ok status
  ok 9 - repeat is on
  ok 10 - command 'repeat' returned an ok status
  ok 11 - command 'status' returned an ok status
  ok 12 - repeat is off
  ok 13 - command 'fade' returned an ok status
  ok 14 - command 'status' returned an ok status
  ok 15 - enabling fading
  ok 16 - command 'fade' returned an ok status
  ok 17 - command 'status' returned an ok status
  ok 18 - disabling fading by default
  ok 19 - command 'random' returned an ok status
  ok 20 - command 'status' returned an ok status
  ok 21 - random is on
  ok 22 - command 'random' returned an ok status
  ok 23 - command 'status' returned an ok status
  ok 24 - random is off
  ok 25 - command 'random' returned an ok status
  ok 26 - command 'status' returned an ok status
  ok 27 - random is on
  ok 28 - command 'random' returned an ok status
  ok 29 - command 'status' returned an ok status
  ok 30 - random is off
  ok
  E: ABORT: Received INT signal (requesting cleanup and shutdown)
 
-- 
Niko Tyni   nt...@debian.org

Bug#861575: libgtkd-3-0 and libvted-3-0 shlibs need a version

[Matthias Klumpp]

Okay, the actual problem here is not the shlibs file, but upstream
breaking API without bumping the SONAME of the library.
I will raise this upstream, so we can find a way to deal with this
issue for all distros and not just Debian (the result might be that we
just always bump the version each time a new library is released).

Meanwhile, I think it's safe to let the package (and Tilix) migrate
back to testing.

Cheers,
Matthias

Bug#863734: unblock: gnupg2/2.1.18-8

[Adam D. Barratt]

On Tue, 2017-07-11 at 11:16 -0400, Daniel Kahn Gillmor wrote:
> On Sun 2017-06-25 18:39:34 -0400, Daniel Kahn Gillmor wrote:
> > On Sat 2017-06-17 17:36:39 +0100, Adam D. Barratt wrote:
> >> Unfortunately we ran out of time to handle this before the release, so
> >> converting it to a proto-p-u request.
> >
> > Thanks for this conversion, Adam.  Please let me know if you need any
> > feedback from on it from me or anyone else on the pkg-gnupg-maint team.
> 
> ping on https://bugs.debian.org/863734 (sending gnupg2/2.1.18-8 to
> stretch proposed-updates) -- please let me know if you need anything
> else.

To be entirely honest, the size of the diff and the number of patches
still worries me, as it makes it very difficult to review. I'm assuming
that there haven't been any relevant regressions or follow-up fixes
since the -8 upload?

In any case, we can't simply transplant -8 to p-u, so would need to see
a debdiff for either a -6+deb9u1 or -8~deb9u1 upload (depending on how
you structure the changelog), built against and tested on stretch,
before confirming an upload.

Finally, unless I missed one when checking back through the thread, we
also need a d-i ack.

Regards,

Adam

Bug#690763: installation-guide: sudo and no password for root user situation

[Holger Wansing]

Hi,

Nicholas D Steeves  wrote:
> Hi Holger,
> 
> On 11 July 2017 at 19:11, Holger Wansing  wrote:
> > Baptiste Jammet  wrote:
> >> Hello,
> >>
> >> I don't know the implementation detail of this (no root password
> >> installs sudo and allow user to use it), but I suspect that only the
> >> first user (created in the next step) will be allowed to use sudo.
> >>
> >> Maybe add something like :
> >> By default, only the first user, that will be created in the next step,
> >> will be allowed to use sudo to perform these
> >> administrative tasks.
> >
> > Yes, you are right, it works exactly this way.
> >
> > I have committed a change to document this clearer:
> > https://anonscm.debian.org/viewvc/d-i?view=revision=70801
> 
> Quick question about this change:  Is the first user given sudo
> privileges now when the root account is enabled (eg: first user always
> has admin privileges irregardless of root account status)?  IIRC when
> the root account is enabled the first user needs to be granted
> permissions with visudo.  I'm not up-to-date with the new installation
> procedure though! ;-)

1. there has been no recent code change in this regard, so the implementation
has been the same for a long time.

2. Reading the whole paragraph gives the answer to your question:

Setting up your clock and time zone is followed by the creation of user 
accounts. By
default you are asked to provide a password for the root
(administrator) account and information necessary to create one regular user
account. If you do not specify a password for the root user, this
account will be disabled but the sudo package will be 
installed
later to enable administrative tasks to be carried out on the new system.
By default, the first user created on the system will be allowed to use the
sudo command to become root.



Long story short: 
functionality of the Debian installer is:
the first user only gains sudo rights, if root account is disabled.


Regards
Holger

-- 

Created with Sylpheed 3.5.0 under
D E B I A N   L I N U X   8 . 0   " J E S S I E " .

Registered Linux User #311290 - https://linuxcounter.net/

Bug#868241: jessie-pu: package netcfg/1.131+deb8u2

[Cyril Brulebois]

Adam D. Barratt  (2017-07-13):
> s/prevents/prevent/, fwiw.

Oopsie, missed it before building & uploading.

> Please go ahead.

Done, thanks.


KiBi.


signature.asc
Description: Digital signature

Bug#868243: jessie-pu: package partman-ext3/84+deb8u1

[Cyril Brulebois]

Adam D. Barratt  (2017-07-13):
> Please go ahead.

Thanks, uploaded.


KiBi.


signature.asc
Description: Digital signature

Bug#868230: jessie-pu: package os-prober/1.65+deb8u1

[Cyril Brulebois]

Adam D. Barratt  (2017-07-13):
> Not as much as I feared from that comment. :-)

It made me unhappy anyway. :)

> Please go ahead.

Thanks, uploaded.


KiBi.


signature.asc
Description: Digital signature

Bug#868228: stretch-pu: package os-prober/1.76~deb9u1

[Cyril Brulebois]

Adam D. Barratt  (2017-07-13):
> Please go ahead.

Thanks, uploaded.


KiBi.


signature.asc
Description: Digital signature

Bug#868252: vim-nox: pressing on last line of a foldmethod=manual behaves differently at end of file

[Daniel Shahaf]

Package: vim-nox
Version: 2:8.0.0197-5
Severity: normal

Dear Maintainer,

I use foldmethod=manual.  When I want to add a line following the last
line of a fold, I use «A» if I want the line new to be included in
the fold, and «o» if I want the new line not to be included in the fold.

However, I find that «A» behaves differently in the following two
cases:

1. The current line is the last line of a fold and of the file

2. The current line is the last line of a fold but not the last line of the file

In case #2, «A» and «o» behave as I described above.

In case #1, «A» adds a new line to the file but doesn't make it part
of the fold, i.e., it behaves as «o» does.

I expected «A» in case #1 to add a new line to the file *and to make
it part of the fold*, as it does in case #2.

Case #1 (the problem case) is:

% vim.nox -Nu NONE -c 'set fdc=2' -c 'normal! zf0' -c 'execute "normal! 
A\"'

Case #2 (the role model / reference case) is:

% vim.nox  -Nu NONE -c 'set fdc=2' -c 'normal! 2o' -c 'normal! ggzfjzRggj' 
-c 'execute "normal! A\"'

To be clear, the incumbent behaviour — adding a line to the file but not
to the fold — should continue to be available under the «o» normal mode
command, for the same reason: consistency with the not-end-of-file case.

I reproduced this in an uptodate sid chroot.

Cheers,

Daniel


-- Package-specific info:

--- real paths of main Vim binaries ---
/usr/bin/vi is /usr/bin/vim.nox
/usr/bin/vim is /usr/bin/vim.nox

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

Kernel: Linux 4.9.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968), LANGUAGE=C 
(charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
Init: unable to detect

Versions of packages vim-nox depends on:
ii  libacl1   2.2.52-3+b1
ii  libc6 2.24-12
ii  libgpm2   1.20.4-6.2+b1
ii  liblua5.2-0   5.2.4-1.1+b2
ii  libperl5.24   5.24.1-7
ii  libpython3.5  3.5.3-3
ii  libruby2.32.3.3-1
ii  libselinux1   2.6-3+b2
ii  libtcl8.6 8.6.6+dfsg-1+b1
ii  libtinfo5 6.0+20170708-1
ii  vim-common2:8.0.0197-5
ii  vim-runtime   2:8.0.0197-5

vim-nox recommends no packages.

Versions of packages vim-nox suggests:
pn  cscope   
pn  vim-doc  

-- no debconf information

Bug#868243: jessie-pu: package partman-ext3/84+deb8u1

[Adam D. Barratt]

Control: tags -1 + confirmed

On Thu, 2017-07-13 at 17:40 +0200, Cyril Brulebois wrote:
> | partman-ext3 (84+deb8u1) jessie; urgency=low
> | 
> |   [ Christian Perrier ]
> |   * Force ext3|ext4 filesystem creation with "-F" so that D-I doesn't
> | "hang" when re-using an existing partition in some situations.
> | Closes: #767682

Please go ahead.

Regards,

Adam

Bug#784619: Linked my Qt4-Qt5 fork to upstream Creepy issue

[Ross Gammon]

tag 784619 - |fixed-upstream
thanks

|Hi,

I just pushed my unfinished Qt4 > Qt5 work to my fork of creepy on
Github (https://github.com/RossGammon/creepy/tree/qt4-qt5) and added a
link to the upstream issue (No. 9 - which was closed as "Won't fix").
They are the same patches I pushed to the Debian GIS repo on Alioth.

As Creepy looks totally unmaintained upstream these days, I recommend we
remove it from unstable.

I will keep watching the Github repo, and if I ever see some commits,
and a release we can work with, then we can always ITP > NEW queue
again. But is doesn't look likely.

I know Bas will probably support this - he is no doubt tired of seeing
Creepy at the top of the GIS Team Dashboard.

What do you think Petter?

Regards,

Ross


signature.asc
Description: OpenPGP digital signature

Bug#868241: jessie-pu: package netcfg/1.131+deb8u2

[Adam D. Barratt]

Control: tags -1 + confirmed

On Thu, 2017-07-13 at 17:33 +0200, Cyril Brulebois wrote:
> | netcfg (1.131+deb8u2) jessie; urgency=medium
> | 
> |   * IPv6 autoconfiguration: fix NTP server name handling, which would be
> | stored as the DHCP-provided hostname, with many thanks to Malcolm
> | Scott for the bug report and the patch (Closes: #862745).
> |   * Stop queueing rdnssd's installation with IPv6 setups. This component
> | conflicts with network-manager and installing it from the network
> | configuration step might prevents large parts of desktop environments
> | from being installed. This isn't a perfect solution but this should be
> | way better than the current status quo (Closes: #854801).

s/prevents/prevent/, fwiw.

Please go ahead.

Regards,

Adam

Bug#868228: stretch-pu: package os-prober/1.76~deb9u1

[Adam D. Barratt]

Control: tags -1 + confirmed

On Thu, 2017-07-13 at 13:17 +0200, Cyril Brulebois wrote:
> | os-prober (1.76~deb9u1) stretch; urgency=medium
> | 
> |   * Rebuild for stretch.
> | 
> |  -- Cyril Brulebois   Thu, 13 Jul 2017 13:12:22 +0200
> | 
> | os-prober (1.76) unstable; urgency=medium
> | 
> |   [ Cyril Brulebois ]
> |   * os-probes/mounted/x86/05efi: Fix check on ID_PART_ENTRY_SCHEME, to
> | look for "dos" instead of "msdos" (Closes: #817023).
> | 
> |  -- Christian Perrier   Wed, 28 Jun 2017 07:08:36 +0200

Please go ahead.

Regards,

Adam

Bug#868230: jessie-pu: package os-prober/1.65+deb8u1

[Adam D. Barratt]

Control: tags -1 + confirmed

On Thu, 2017-07-13 at 13:29 +0200, Cyril Brulebois wrote:
> I'd like to fix a few things in os-prober in jessie:
>  - dos vs. msdos check, leading to misdetections with EFI systems
>  - improve robustness with Windows detection by adding the -a flag
>to grep (this generates much diff noise, sorry)

Not as much as I feared from that comment. :-)

>  - add support for Windows 10 (at the top of said noise)

Please go ahead.

Regards,

Adam