date:20170917

Hi Bas,

On Sun, Sep 17, 2017 at 12:01:53AM +0200, Sebastiaan Couwenberg wrote:
> Hi Salvatore,
> 
> On 09/13/2017 07:27 PM, Bas Couwenberg wrote:
> > Should be fixed in the new upstream release:
> > 
> > https://groups.google.com/forum/m/#!topic/spatialite-users/Wpj62XSzcZY
> > 
> > I'm not able to work on this until I return from VAC.
> 
> I've cherry-picked the changes from 1.0.4 and prepared updates for
> stretch, jessie & wheezy. The changes are available in git, and the
> debdiffs are attached.
> 
>  * https://anonscm.debian.org/cgit/pkg-grass/freexl.git/log/?h=stretch
>  * https://anonscm.debian.org/cgit/pkg-grass/freexl.git/log/?h=jessie
>  * https://anonscm.debian.org/cgit/pkg-grass/freexl.git/log/?h=wheezy
> 
> Are these OK to upload?

Thanks for those for jessie- and stretch-security, debdiffs look good
to me. Assuming you got a chance to test the resulting packages please
do upload the jessie- and stretch-security ones. Remember to build the
one for stretch-security with -sa since it's new to dak on
security-master.

For wheezy, there is a dedicated team taking care of LTS. So you might
want to contact debian-lts@l.d.o.

Thanks for your work, much appreciated!

Regards,
Salvatore

FTR, for future references, please Cc the security team when you have
debdiffs ready for a security-upload, this way we can distribute the
DSA load for the available team members :)

signature.asc
Description: PGP signature

Bug#758022: test_interpolate.TestPPoly.test_roots test fails on i386

2017-09-17 Thread Graham Inggs

Ignoring the test failures during the build has also allowed the i386
failure of test_orthogonal.test_j_roots in 0.18.1 to propagate, and
most recently, the failure of test_orthogonal.test_roots_jacobi in
0.19.1 (presumably the same test renamed):


==
FAIL: test_orthogonal.test_roots_jacobi
--
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/nose/case.py", line 198, in runTest
self.test(*self.arg)
  File 
"/<>/debian/python3-scipy/usr/lib/python3/dist-packages/scipy/special/tests/test_orthogonal.py",
line 321, in test_roots_jacobi
vgq(rf(0.9, 2), ef(0.9, 2), wf(0.9, 2), -1., 1., 100, atol=2e-13)
  File 
"/<>/debian/python3-scipy/usr/lib/python3/dist-packages/scipy/special/tests/test_orthogonal.py",
line 287, in verify_gauss_quad
assert_allclose(vv, np.eye(N), rtol, atol)
  File "/usr/lib/python3/dist-packages/numpy/testing/utils.py", line
1395, in assert_allclose
verbose=verbose, header=header, equal_nan=equal_nan)
  File "/usr/lib/python3/dist-packages/numpy/testing/utils.py", line
778, in assert_array_compare
raise AssertionError(msg)
AssertionError:
Not equal to tolerance rtol=1e-15, atol=2e-13

(mismatch 0.37545%)
 x: array([[  1.00e+00,   3.099016e-16,  -1.339924e-15, ...,
  1.060805e-16,   7.590133e-16,  -4.425680e-17],
   [  3.055861e-16,   1.00e+00,   5.293052e-16, ...,...
 y: array([[ 1.,  0.,  0., ...,  0.,  0.,  0.],
   [ 0.,  1.,  0., ...,  0.,  0.,  0.],
   [ 0.,  0.,  1., ...,  0.,  0.,  0.],...

--
Ran 24210 tests in 389.473s

FAILED (KNOWNFAIL=92, SKIP=1923, failures=1)
Running unit tests for scipy
NumPy version 1.13.1
NumPy relaxed strides checking option: True
NumPy is installed in /usr/lib/python3/dist-packages/numpy
SciPy version 0.19.1
SciPy is installed in
/<>/debian/python3-scipy/usr/lib/python3/dist-packages/scipy
Python version 3.6.2 (default, Sep  5 2017, 20:23:28) [GCC 7.2.0]
nose version 1.3.7
Optimization terminated successfully.(Exit mode 0)
Current function value: 0.0
Iterations: 1
Function evaluations: 5
Gradient evaluations: 1
failed: test_orthogonal.test_roots_jacobi
#errors: 1

Bug#875997: RFS: jclicmoodle/3.0.1 (package already in Debian from 2009)

2017-09-17 Thread Phil Wyett

On Sun, 2017-09-17 at 12:27 +0500, Andrey Rahmatullin wrote:
> On Sun, Sep 17, 2017 at 08:05:47AM +0200, Innocent De Marchi wrote:
> > jclicmoodle is an add-on for moodle: allows you to run jclic [0] on
> > moodle. Now, moodle is locked in sid due to lack of stable maintenance
> > [1]. Even so, moodle has been updated 3 times this year. Meanwhile, I
> > think it is necessary to continue updating jclicmoodle pending the
> > unlocking of moodle.
> 
> This doesn't look like an RFS. 
> 

Hi Innocent,

Log in to mentors.debian.net.

Go to your packages upload page on mentors:

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

Under 'Information' section, next to 'Version' on your upload you should see a
link inside brackets:

(View RFS template)

Use this link, it will supply info on how to layout your Request For Sponsorship
(RFS) bug mail.

Direct link to that template:

https://mentors.debian.net/sponsors/rfs-howto/jclicmoodle

Hopefully this information is helpful.

Regards

Phil

-- 
*** If this is a mailing list, I am subscribed, no need to CC me.***

Playing the game for the games sake.

Web: https://kathenas.org

Github: https://github.com/kathenas

Twitter: kathenasorg

Instagram: kathenasorg

GPG: 1B97 6556 913F 73F3 9C9B 25C4 2961 D9B6 2017 A57A

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

Bug#876003: lintian: Wrong description of tag unknown-testsuite


Package: lintian
Version: 2.5.52
Severity: normal

Dear Maintainer,

Please, change the description of tag unknown-testsuite.  It contains now:

  The dsc file sets Testsuite to a value other than autopkgtest, the
  only one allowed. This field is most probably copied by dpkg-source
  from Testsuite in debian/control.

but autopkgtest is not the only value allowed.

Best,

Rafael

-- System Information:

Debian Release: 9.0
  APT prefers testing
  APT policy: (650, 'testing'), (600, 'unstable'), (550, 'experimental'), (550, 
'stable'), (500, 'oldstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.9.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.utf8 (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 lintian depends on:
ii  binutils  2.28-5
ii  bzip2 1.0.6-8.1
ii  diffstat  1.61-1
ii  dpkg  1.18.22
ii  file  1:5.29-3
ii  gettext   0.19.8.1-2
ii  intltool-debian   0.35.0+20060710.4
ii  libapt-pkg-perl   0.1.33
ii  libarchive-zip-perl   1.59-1
ii  libclass-accessor-perl0.34-1
ii  libclone-perl 0.38-2+b2
ii  libdpkg-perl  1.18.22
ii  libemail-valid-perl   1.202-1
ii  libfile-basedir-perl  0.07-1
ii  libipc-run-perl   0.94-1
ii  liblist-moreutils-perl0.416-1+b3
ii  libparse-debianchangelog-perl 1.2.0-12
ii  libperl5.24 [libdigest-sha-perl]  5.24.1-1
ii  libperl5.26 [libdigest-sha-perl]  5.26.0-5
ii  libtext-levenshtein-perl  0.13-1
ii  libtimedate-perl  2.3000-2
ii  liburi-perl   1.71-1
ii  libxml-simple-perl2.24-1
ii  libyaml-libyaml-perl  0.63-2+b2
ii  man-db2.7.6.1-2
ii  patchutils0.3.4-2
ii  perl  5.26.0-5
ii  t1utils   1.40-2
ii  xz-utils  5.2.2-1.3

Versions of packages lintian recommends:
ii  libperlio-gzip-perl  0.19-1+b4

Versions of packages lintian suggests:
pn  binutils-multiarch 
ii  dpkg-dev   1.18.22
ii  libhtml-parser-perl3.72-3+b2
ii  libtext-template-perl  1.46-1

-- no debconf information

Bug#875985: lintian: Allow Testsuite: autopkgtest-pkg-octave


* Chris Lamb  [2017-09-17 09:29]:


 tags 875985 + pending
 thanks

Fixed in Git:

 
https://anonscm.debian.org/git/lintian/lintian.git/commit/?id=53a4a87cba1c2418001e654c28cb64f36c55acdf


Thanks for the prompt fix.

Notice that I have also addressed another issue in my bug report, 
regarding the description of tag unknown-testsuite.  Should I file a 
separate bug report for that?


Best,

Rafael

Bug#857341: dosbox: crashes with core=dynamic: DRC64:Unhandled memory reference

2017-09-17 Thread snfk

Hello. This also appears in unstable.
Downgrading dosbox to jessie's version 0.74-4 resolves the issue.
Linux version 4.9.0-3-amd64
AMD Phenom(tm) II X4 965 Processor

Bug#876003: lintian: Wrong description of tag unknown-testsuite

Hey Rafael,

> but autopkgtest is not the only value allowed.

Hm, are you sure? Note that this is referring to the *source*
package's .dsc file; which is, I believe, almost entirely separate
from the value in debian/control.

Note that the linked "Ref" link:

  
https://anonscm.debian.org/git/autopkgtest/autopkgtest.git/tree/doc/README.package-tests.rst

… says:

  To allow test execution environments to discover packages which provide
  tests, their source packages need to have a ``Testsuite:`` header
  containing ``autopkgtest`` (which is currently the only defined value).


Regards,

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

Bug#875432: s/python3-sphinx-intl/sphinx-intl

2017-09-17 Thread Hideki Yamane

On Wed, 13 Sep 2017 11:54:15 -0300
Antonio Terceiro  wrote:
> > > if sphinx-intl is primary application (cli tool, etc.), than binary pkg
> > > sphinx-intl is better. If it's library/module, than python3-sphinx-intl
> > > is better.
> > 
> > Based on the description of the project [1], it looks like it is the former.
> > 
> > [1] https://pypi.python.org/pypi/sphinx-intl
> 
> however sphinx itself is python*-sphinx, so maybe having those be
> consistent with each other is a good idea.

 Hmm. We don't have python-sphinx-intl for python2.x, so maybe just
 sphinx-intl is okay for users.


-- 
Regards,

 Hideki Yamane henrich @ debian.or.jp/org
 http://wiki.debian.org/HidekiYamane

Bug#876008: autopkgtest: Wrong statement about Testsuite field in documentation


Hi Martin,

Thanks for your prompt reaction.  Just one comment:

* Martin Pitt  [2017-09-17 12:48]:


Rafael Laboissière [2017-09-17 12:11 +0200]:

In file doc/README.package-tests.rst, there is this sentence:

   To allow test execution environments to discover packages which
   provide tests, their source packages need to have a ``Testsuite:``
   header containing ``autopkgtest`` (which is currently the only
   defined value).

This was true in 2014, before the autodep8 pacakge started introducing the 
autopkgtest-pkg-* values.  The statement is innacurate today.


Indeed, and I fixed that in git about a month ago already:

 https://anonscm.debian.org/git/autopkgtest/autopkgtest.git/commit/?id=f818619

(I'll add the Closes # for this bug). I didn't upload a new autopkgtest so far, 
as git has changes which need a newer debci. This just got unblocked yesterday, 
so I'll do an upload soon.


I may be getting it wrong, but the commit that you indicate above still 
preserves the phrase "which is currently the only defined value".  This 
is the inaccuracy that was referring to in my original bug report. 
Currently, autodep8 accepts the following values for the Testsuite field:


 autopkgtest
 autopkgtest-pkg-dkms
 autopkgtest-pkg-go
 autopkgtest-pkg-nodejs
 autopkgtest-pkg-octave
 autopkgtest-pkg-perl
 autopkgtest-pkg-python
 autopkgtest-pkg-r
 autopkgtest-pkg-ruby
 autopkgtest-pkg-elpa

Best,

Rafael

Bug#876015: liblldb-6.0-dev: circular dependency with python-lldb-6.0 and lldb-6.0

Package: liblldb-6.0-dev
Version: 1:6.0~svn311834-1
Severity: important

Hello LLVM Debian maintainers,

There is a circular dependency between liblldb-6.0-dev, lldb-6.0 and 
python-lldb-6.0:

liblldb-6.0-dev :Depends: lldb-6.0 (= 1:6.0~svn311834-1)
lldb-6.0:Depends: python-lldb-6.0
python-lldb-6.0 :Depends: liblldb-6.0-dev

Complex circular dependencies are known to cause problems during upgrade, so we
should try to avoid them.

Cheers,
-- 
Bill. 

Imagine a large red swirl here.

Bug#875982: RM: obsolete with current Perl?

2017-09-17 Thread gregor herrmann

On Sat, 16 Sep 2017 22:22:11 +0200, Florian Schlichting wrote:

> libsub-current-perl has no reverse dependencies and an extremely low
> popcon (7 installs, 0 votes currently). It would appear that it is
> obsolete and can be removed from Debian.

Makes sense to me.


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: Tom Waits: Shiver Me Timbers


signature.asc
Description: Digital Signature

Bug#876001: libwpd: CVE-2017-14226

Hi again,

On Sun, Sep 17, 2017 at 01:59:20PM +0200, Rene Engelhard wrote:
> On Sun, Sep 17, 2017 at 10:47:06AM +0200, Salvatore Bonaccorso wrote:
> > Source: libwpd
> > Version: 0.10.1-5
> > Severity: important
> > Tags: patch security upstream
> > Forwarded: https://sourceforge.net/p/libwpd/tickets/14/
> > 
> > Hi,
> > 
> > the following vulnerability was published for libwpd.
> >
> > CVE-2017-14226[0]:
> [...]
> 
> fixed in 0.10.2-1 for sid. Want this fixed as DSAs for jessie/stretch?

Ah, nevermind. I should have looked at the security tracker :):

[stretch] - libwpd  (Minor issue)
[jessie] - libwpd  (Minor issue)

OK.

It's in git now, for a possible later fix we can include this, too.

Regards,
 
Rene

Bug#827853: closed by Bastian Venthur <vent...@debian.org> (Bug#827853: fixed in python-debianbts 2.6.3)

Hi Bastian,

> I am using a custom sorting function, and it seems a waste to
> need to duplicate this in my own code.

Thanks for fixing this. But, now I need to find whatever code I was
writing at the time and update it, but I can't think of what it was!


Best wises

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

Bug#876018: expect: should not recommend tk8.6

2017-09-17 Thread Vincent Lefevre

Package: expect
Version: 5.45-8
Severity: normal

The expect package currently has:

  Recommends: tcl8.6, tk8.6

Recommending tk8.6 is too much as by default, it brings lots of
X11 related packages on machines where X11 is not used (e.g. misc
servers). Many Expect scripts do not use X.

FYI, I noticed this when I wanted to install maildrop, which is
not related to X11 at all.

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

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

Versions of packages expect depends on:
ii  libc6   2.24-17
ii  libtcl8.6   8.6.7+dfsg-1
ii  tcl-expect  5.45-8

Versions of packages expect recommends:
ii  tcl8.6  8.6.7+dfsg-1
ii  tk8.6   8.6.7-1

expect suggests no packages.

-- no debconf information

Bug#876001: libwpd: CVE-2017-14226

Hi Rene!

On Sun, Sep 17, 2017 at 02:54:12PM +0200, Rene Engelhard wrote:
> Hi again,
> 
> On Sun, Sep 17, 2017 at 01:59:20PM +0200, Rene Engelhard wrote:
> > On Sun, Sep 17, 2017 at 10:47:06AM +0200, Salvatore Bonaccorso wrote:
> > > Source: libwpd
> > > Version: 0.10.1-5
> > > Severity: important
> > > Tags: patch security upstream
> > > Forwarded: https://sourceforge.net/p/libwpd/tickets/14/
> > > 
> > > Hi,
> > > 
> > > the following vulnerability was published for libwpd.
> > >
> > > CVE-2017-14226[0]:
> > [...]
> > 
> > fixed in 0.10.2-1 for sid. Want this fixed as DSAs for jessie/stretch?
> 
> Ah, nevermind. I should have looked at the security tracker :):
> 
> [stretch] - libwpd  (Minor issue)
> [jessie] - libwpd  (Minor issue)
> 
> OK.

Thanks for the quick updates, impressing :)

> It's in git now, for a possible later fix we can include this, too.

Sicne the point releases are approaching, can you shedule the fixes
since already prepared in the next point release?

Regards and thanks again for your work,
Salvatore

Bug#876022: mate-panel: Right clicking fcitx icon in notification area is responded extremely slow.

2017-09-17 Thread Takashi Yano

Package: mate-panel
Version: 1.18.4-2
Severity: normal

Dear Maintainer,

I'm using fcitx and fcitx-mozc under mate desktop environment.
Usually, fcitx menu appears when I right-click on fcitx icon in
notification area. However, with mate-panel 1.18.4-2, the menu
appears 30 seconds after clicking the icon. Until menu is showed,
mate stops responding to any UI operations. This problem disappears
if mate-panel is downgraded to 1.16.2-1. Furthermore, when input
method is switched to mozc, mozc icon is not displayed. Usually,
mozc icon is displayed instead of fcitx icon when input method is
switched to mozc.

I hope this bug will be fixed in next release.
Thanks in advance.

Best regards,
Takashi Yano

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

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

Versions of packages mate-panel depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.26.0-2+b1
ii  libatk1.0-0  2.26.0-2
ii  libc62.24-17
ii  libcairo-gobject21.14.10-1
ii  libcairo21.14.10-1
ii  libdbus-1-3  1.11.16+really1.10.22-1
ii  libdbus-glib-1-2 0.108-2
ii  libdconf10.26.0-2+b1
ii  libgdk-pixbuf2.0-0   2.36.5-4
ii  libglib2.0-0 2.54.0-1
ii  libgtk-3-0   3.22.21-1
ii  libice6  2:1.0.9-2
ii  libmate-desktop-2-17 1.18.0-1
ii  libmate-menu21.18.0-2
ii  libmate-panel-applet-4-1 1.18.4-2
ii  libmateweather1  1.18.1-1
ii  libpango-1.0-0   1.40.12-1
ii  libpangocairo-1.0-0  1.40.12-1
ii  librsvg2-2   2.40.18-1
ii  libsm6   2:1.2.2-1+b3
ii  libstartup-notification0 0.12-4+b2
ii  libwnck-3-0  3.24.1-1
ii  libx11-6 2:1.6.4-3
ii  libxau6  1:1.0.8-1+b2
ii  libxrandr2   2:1.5.1-1
ii  mate-desktop 1.18.0-1
ii  mate-menus   1.18.0-2
ii  mate-panel-common1.18.4-2
ii  mate-polkit  1.18.1-1
ii  menu-xdg 0.5

mate-panel recommends no packages.

mate-panel suggests no packages.

-- no debconf information


-- 
Takashi Yano

Bug#876024: dpkg-buildpackage tries to sign buildinfo despite --unsigned-buildinfo or --no-sign passed to debuild

2017-09-17 Thread jean-christophe manciot

Package: dpkg-dev
Version: 1.18.24

With --unsigned-buildinfo:
...
Finished running lintian.
Now signing changes and any dsc files...
 signfile buildinfo apr_1.6.2-1_amd64.buildinfo x
gpg: signing failed: Permission denied
gpg: /tmp/debsign.8axXeL81/apr_1.6.2-1_amd64.buildinfo: clear-sign failed:
Permission denied
debsign: gpg error occurred!  Aborting
debuild: fatal error at line 1053:
running debsign failed
gbp:error: 'debuild -i -I --unsigned-source --unsigned-changes
--unsigned-buildinfo --build=binary' failed: it exited with 29

With --no-sign:
Now signing changes and any dsc files...
 signfile buildinfo apr_1.6.2-1_amd64.buildinfo xxx
gpg: signing failed: Permission denied
gpg: /tmp/debsign.Lu3ErY9E/apr_1.6.2-1_amd64.buildinfo: clear-sign failed:
Permission denied
debsign: gpg error occurred!  Aborting
debuild: fatal error at line 1053:
running debsign failed
gbp:error: 'debuild -i -I --no-sign --build=binary' failed: it exited with
29


-- 
Jean-Christophe Manciot

Bug#872620: anarchism: add Suggests: fortune-anarchism

2017-09-17 Thread Holger Levsen

On Sat, Sep 16, 2017 at 08:28:37PM -0300, Samuel Henrique wrote:
> All solved, package is on mentors Holger :)

...and uploaded and git tagged!

Thanks for your nice work, Samuel!


-- 
cheers,
Holger


signature.asc
Description: Digital signature

Bug#779623: debmake-doc has been released

control: tags -1 - moreinfo
control: tags -1 + wontfix

Since debmake offer better UI for packaging into multiple binary
packages and debmake-doc documents these facts, I will not update this
NM guide as requested.

I will keep this as wontfix to make people aware changes.

Osamu

Bug#641314: debhelper: dh_auto_test should support standard python cli for running tests

2017-09-17 Thread Niels Thykier

On Wed, 14 Sep 2011 16:08:40 -0400 Joey Hess  wrote:
> Barry Warsaw wrote:
> > I'd be happy to write a little helper script (probably in Python?) which 
> > could
> > make the checks I enumerate above.  You could then call that script and use
> > the return code to see if you should do `python setup.py test -vv` or 
> > fallback
> > to what it does now.
> 
> I suppose that could be put in an appropriate package. Not sure what
> would be appropriate but not debhelper. And debhelper could use it. I'm
> not really thrilled by adding more heuristics. If you're working on this
> upstream it would be ever so much better if "python setup.py test"
> simply exited nonzero when there's no test suite.
> 
> -- 
> see shy jo

Hi Barry,

Is there an update to the situation here?  Can we assume that the test
target is (generally) always available ?  (even if we limit it to just
python3 related calls).

Thanks,
~Niels

Bug#867729: /usr/share/icons/hicolor/symbolic/apps/firefox-symbolic.svg: Symbolic icon file empty

2017-09-17 Thread Laurent Bigonville

Package: firefox
Version: 55.0.3-1
Followup-For: Bug #867729

Hello,

Any news about this bug?

-- Package-specific info:

-- Extensions information
Name: Application Update Service Helper
Location: ${PROFILE_EXTENSIONS}/aushel...@mozilla.org.xpi
Status: enabled

Name: Click-to-Play staged rollout
Location: ${PROFILE_EXTENSIONS}/clicktoplay-roll...@mozilla.org.xpi
Status: enabled

Name: Compact clair theme
Status: user-disabled

Name: Compact sombre theme
Status: user-disabled

Name: Firefox Screenshots
Location: ${PROFILE_EXTENSIONS}/screensh...@mozilla.org.xpi
Status: enabled

Name: Follow-on Search Telemetry
Location: ${PROFILE_EXTENSIONS}/followonsea...@mozilla.com.xpi
Status: enabled

Name: Français Language Pack locale
Location: 
/usr/lib/firefox/browser/extensions/langpack...@firefox.mozilla.org.xpi
Package: firefox-l10n-fr
Status: enabled

Name: GNOME Keyring integration
Location: /usr/share/xul-ext/gnome-keyring
Package: xul-ext-gnome-keyring
Status: enabled

Name: Greasemonkey
Location: ${PROFILE_EXTENSIONS}/{e4a8a97b-f2ed-450b-b12d-ee082ba24781}.xpi
Status: enabled

Name: HTTPS Everywhere
Location: ${PROFILE_EXTENSIONS}/https-everywh...@eff.org.xpi
Status: enabled

Name: Intégration à GNOME Shell
Location: ${PROFILE_EXTENSIONS}/chrome-gnome-sh...@gnome.org.xpi
Status: enabled

Name: Modify Header Value (HTTP Headers)
Location: ${PROFILE_EXTENSIONS}/jid0-oewf5zcskghjfv4kk4...@jetpack.xpi
Status: enabled

Name: Multi-process staged rollout
Location: ${PROFILE_EXTENSIONS}/e10sroll...@mozilla.org.xpi
Status: enabled

Name: Pinterest without registration greasemonkey-user-script
Status: enabled

Name: Pocket
Location: ${PROFILE_EXTENSIONS}/fire...@getpocket.com.xpi
Status: enabled

Name: Reddit Enhancement Suite
Location: ${PROFILE_EXTENSIONS}/jid1-xufzosoflzs...@jetpack.xpi
Status: enabled

Name: Shield Recipe Client
Location: ${PROFILE_EXTENSIONS}/shield-recipe-cli...@mozilla.org.xpi
Status: enabled

Name: Thème par défaut theme
Location: 
/usr/lib/firefox/browser/extensions/{972ce4c6-7e08-4474-a285-3208198ce6fd}.xpi
Package: firefox
Status: enabled

Name: uBlock Origin
Location: /usr/share/xul-ext/ublock-origin
Package: xul-ext-ublock-origin
Status: enabled

Name: Web Compat
Location: ${PROFILE_EXTENSIONS}/webcom...@mozilla.org.xpi
Status: enabled

-- Plugins information
Name: Shockwave Flash (26.0.0.151)
Location: /home/bigon/.mozilla/plugins/libflashplayer.so
Status: enabled


-- Addons package information
ii  firefox55.0.3-1 amd64Mozilla Firefox web browser
ii  firefox-l10n-f 55.0.3-1 all  French language package for Firef
ii  xul-ext-gnome- 0.12-1   all  Store mozilla passwords in GNOME 
ii  xul-ext-ublock 1.13.8+dfsg- all  general-purpose lightweight ads, 

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

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

Versions of packages firefox depends on:
ii  debianutils   4.8.2
ii  fontconfig2.12.3-0.2
ii  libatk1.0-0   2.26.0-2
ii  libc6 2.24-17
ii  libcairo-gobject2 1.14.10-1
ii  libcairo2 1.14.10-1
ii  libdbus-1-3   1.11.16+really1.10.22-1
ii  libdbus-glib-1-2  0.108-2
ii  libevent-2.1-62.1.8-stable-4
ii  libffi6   3.2.1-6
ii  libfontconfig12.12.3-0.2
ii  libfreetype6  2.8-0.2
ii  libgcc1   1:7.2.0-5
ii  libgdk-pixbuf2.0-02.36.5-4
ii  libglib2.0-0  2.54.0-1
ii  libgtk-3-03.22.21-1
ii  libgtk2.0-0   2.24.31-2
pn  libhunspell-1.6-0 
ii  libjsoncpp1   1.7.4-3
ii  libnspr4  2:4.16-1
ii  libnss3   2:3.32-2
ii  libpango-1.0-01.40.12-1
ii  libsqlite3-0  3.20.1-1
ii  libstartup-notification0  0.12-4+b2
ii  libstdc++67.2.0-5
ii  libvpx4   1.6.1-3
ii  libx11-6  2:1.6.4-3
ii  libx11-xcb1   2:1.6.4-3
ii  libxcb-shm0   1.12-1
ii  libxcb1   1.12-1
ii  libxcomposite11:0.4.4-2
ii  libxdamage1   1:1.1.4-3
ii  libxext6  2:1.3.3-1+b2
ii  libxfixes31:5.0.3-1
ii  libxrender1   1:0.9.10-1
ii  libxt61:1.1.5-1
ii  procps2:3.3.12-3
ii  zlib1g1:1.2.8.dfsg-5

firefox recommends no packages.

Versions of packages firefox suggests:
ii  fonts-lmodern  2.004.5-3
ii  fonts-stix [otf-stix]  1.1.1-4
ii  libcanberra0   0.30-3
ii

Bug#821088: reassign #821088 to live-wrapper?

2017-09-17 Thread Steve McIntyre

On Sun, Sep 17, 2017 at 05:45:18PM +0300, Lars Wirzenius wrote:
>This bug has a message from Iain that says "This bug should be
>reassigned to live-wrapper once it has entered the archives".
>live-wrapper is in Debian (stable onwards). Should we reassign this
>bug to live-wrapper?

I'm not sure yet. There's a series of these bugs open against various
Debian packages, basically as place-holders for now. vmdebootstrap is
the bit that installs kernelss, but live-wrapper is in charge of
it. They might both need changes yet, tbh...

-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
Can't keep my eyes from the circling sky,
Tongue-tied & twisted, Just an earth-bound misfit, I...

Bug#821088: reassign #821088 to live-wrapper?

2017-09-17 Thread Lars Wirzenius

This bug has a message from Iain that says "This bug should be
reassigned to live-wrapper once it has entered the archives".
live-wrapper is in Debian (stable onwards). Should we reassign this
bug to live-wrapper?

-- 
I want to build worthwhile things that might last. --joeyh


signature.asc
Description: PGP signature

Bug#868496: Policy and dh_foo etc.

control: tags -1 moreinfo

Hi,

RE: https://bugs.debian.org/868496

As I reflect on this bug report, I realize this is not just
dh_installxfonts.  Many other dh_foo commands do the similar things.

So I decided to document it genetically by adding a bit more pointers to
debhelper and describing it as *declarative* and it to insert maintainer
scripts.

Also, this is xfont which is dying species.  (I thought you were talking
ttf/otf fonts.)  Many ttf/otf font packages use dh_installdeb with -Xxz
etc. as override.  But that seems to be default anyway.

I didn't add even an packaging example since I can't make a small
TTF/OTF font to be included in this package.  If you have EXTREMELY
small font (Maybe having only "A" in it with example packaging as MIT
license, I will add it to example.  Please send me such ;-) Thus more
info.

Osamu

Bug#876005: Script to remap microphone to mono for Skype

2017-09-17 Thread Damien


Package: pulseaudio
Version: 1:8.0-0ubuntu3.3

Hello

On my laptop Lenovo G70-80 with Conexant 20751/2 audio chipset, the microphone 
input doesn't work with Skype. It seems that Pulseaudio confuses stereo and 
mono with that chipset.
Here is a solution to remap the microphone to mono and to solve that trouble: 
it works for me on  my system.

At first, you have to get the source input name with:
$ pacmd list-sources

You pick up among other lines:
alsa_input.pci-_00_1b.0.analog-stereo

Then you add the following lines to the file /etc/pulse/default.pa :

### Remap microphone to mono
load-module module-remap-source 
master=alsa_input.pci-_00_1b.0.analog-stereo master_channel_map=front-left 
channel_map=mono
set-default-source record_mono

Restart the daemon:
pulseaudio -k
pulseaudio --start

Can you create a script who processes that automatically during the 
installation of the pulseaudio package?

Thank you in advance.

I am using Ubuntu 16.04 LTS, kernel 4.4.0-93-generic libc 2.23-0ubuntu9

Bug#875733: [pkg-lxc-devel] Bug#875733: lxc.mount.auto = cgroup:mixed doesn't seem to work in Stretch anymore

2017-09-17 Thread Evgeni Golov

On Sun, Sep 17, 2017 at 10:40:27AM +0200, Evgeni Golov wrote:
> TL;DR: I can reproduce the "does not create cgroups" behaviour, but I
> don't know why yet.
> 
> Either way, you are right, the cgroups are missing in Stretch, and I don't 
> yet understand why.

This happens because cgfsng_mount() is a NOOP when cgroup namespaces are
supported [4].

This seems intentional, but I don't know who is suposed to used the
namespaced cgroups then.

[4] https://github.com/lxc/lxc/blob/master/src/lxc/cgroups/cgfsng.c#L1627-L1628

Bug#876007: [patch] fix autopkg tests with M-A'd openblas/atlas

Package: src:python-scipy
Tags: patch sid buster
Severity important

patch at
http://launchpadlibrarian.net/337074560/python-scipy_0.18.1-2ubuntu3_0.18.1-2ubuntu4.diff.gz

Bug#876001: CVE-2017-14226

for reference respective traces:

0.10.1-5:

ASAN:DEADLYSIGNAL
=
==19356==ERROR: AddressSanitizer: SEGV on unknown address 0x55959d2ac260 (pc 
0x55959d04d55f bp 0x7ffcf9f1c3c0 sp 0x7ffcf9f1c368 T0)
==19356==The signal is caused by a WRITE memory access.
#0 0x55959d04d55e in WPXTableList::WPXTableList(WPXTableList const&) 
/root/libwpd-0.10.1/src/lib/WPXTable.cpp:169
#1 0x55959d043484 in WPXHeaderFooter::getTableList() const 
/root/libwpd-0.10.1/src/lib/WPXPageSpan.h:66
#2 0x55959d043484 in WP5StylesListener::insertBreak(unsigned char) 
/root/libwpd-0.10.1/src/lib/WP5StylesListener.cpp:94
#3 0x55959d0414f3 in WP5Parser::parseDocument(librevenge::RVNGInputStream*, 
WPXEncryption*, WP5Listener*) /root/libwpd-0.10.1/src/lib/WP5Parser.cpp:102
#4 0x55959d04162f in 
WP5Parser::parseSubDocument(librevenge::RVNGTextInterface*) 
/root/libwpd-0.10.1/src/lib/WP5Parser.cpp:234
#5 0x55959d037c2a in 
libwpd::WPDocument::parseSubDocument(librevenge::RVNGInputStream*, 
librevenge::RVNGTextInterface*, libwpd::WPDFileFormat) 
/root/libwpd-0.10.1/src/lib/WPDocument.cpp:460
#6 0x55959d053637 in WP3ContentListener::insertWP51Table(double, double, 
double, double, unsigned char, unsigned char, unsigned short, WP3SubDocument 
const*, WP3SubDocument const*) 
/root/libwpd-0.10.1/src/lib/WP3ContentListener.cpp:867
#7 0x55959d03f45b in WP3WindowGroup::parse(WP3Listener*) 
/root/libwpd-0.10.1/src/lib/WP3WindowGroup.cpp:144
#8 0x55959d03c431 in WP3Parser::parseDocument(librevenge::RVNGInputStream*, 
WPXEncryption*, WP3Listener*) /root/libwpd-0.10.1/src/lib/WP3Parser.cpp:107
#9 0x55959d03c492 in WP3Parser::parse(librevenge::RVNGInputStream*, 
WPXEncryption*, WP3Listener*) /root/libwpd-0.10.1/src/lib/WP3Parser.cpp:76
#10 0x55959d03c887 in WP3Parser::parse(librevenge::RVNGTextInterface*) 
/root/libwpd-0.10.1/src/lib/WP3Parser.cpp:153
#11 0x55959d037ead in 
libwpd::WPDocument::parse(librevenge::RVNGInputStream*, 
librevenge::RVNGTextInterface*, char const*) 
/root/libwpd-0.10.1/src/lib/WPDocument.cpp:345
#12 0x55959d037560 in main 
/root/libwpd-0.10.1/src/conv/html/wpd2html.cpp:116
#13 0x7f0b7533d2e0 in __libc_start_main 
(/lib/x86_64-linux-gnu/libc.so.6+0x202e0)
#14 0x55959d037719 in _start 
(/root/libwpd-0.10.1/src/conv/html/wpd2html+0x10719)

AddressSanitizer can not provide additional info.
SUMMARY: AddressSanitizer: SEGV /root/libwpd-0.10.1/src/lib/WPXTable.cpp:169 in 
WPXTableList::WPXTableList(WPXTableList const&)
==19356==ABORTING

0.10.0-2:

ASAN:DEADLYSIGNAL
=
==19364==ERROR: AddressSanitizer: SEGV on unknown address 0x563045443b58 (pc 
0x5630451e51c3 bp 0x7ffe20d01590 sp 0x7ffe20d01538 T0)
==19364==The signal is caused by a WRITE memory access.
#0 0x5630451e51c2 in WPXTableList::WPXTableList(WPXTableList const&) 
/root/source-libwpd/libwpd-0.10.0/src/lib/WPXTable.cpp:169
#1 0x5630451db304 in WPXHeaderFooter::getTableList() const 
/root/source-libwpd/libwpd-0.10.0/src/lib/WPXPageSpan.h:66
#2 0x5630451db304 in WP5StylesListener::insertBreak(unsigned char) 
/root/source-libwpd/libwpd-0.10.0/src/lib/WP5StylesListener.cpp:94
#3 0x5630451d9583 in WP5Parser::parseDocument(librevenge::RVNGInputStream*, 
WPXEncryption*, WP5Listener*) 
/root/source-libwpd/libwpd-0.10.0/src/lib/WP5Parser.cpp:102
#4 0x5630451d96bf in 
WP5Parser::parseSubDocument(librevenge::RVNGTextInterface*) 
/root/source-libwpd/libwpd-0.10.0/src/lib/WP5Parser.cpp:234
#5 0x5630451cfc72 in 
libwpd::WPDocument::parseSubDocument(librevenge::RVNGInputStream*, 
librevenge::RVNGTextInterface*, libwpd::WPDFileFormat) 
/root/source-libwpd/libwpd-0.10.0/src/lib/WPDocument.cpp:452
#6 0x5630451eb317 in WP3ContentListener::insertWP51Table(double, double, 
double, double, unsigned char, unsigned char, unsigned short, WP3SubDocument 
const*, WP3SubDocument const*) 
/root/source-libwpd/libwpd-0.10.0/src/lib/WP3ContentListener.cpp:867
#7 0x5630451d74db in WP3WindowGroup::parse(WP3Listener*) 
/root/source-libwpd/libwpd-0.10.0/src/lib/WP3WindowGroup.cpp:144
#8 0x5630451d4491 in WP3Parser::parseDocument(librevenge::RVNGInputStream*, 
WPXEncryption*, WP3Listener*) 
/root/source-libwpd/libwpd-0.10.0/src/lib/WP3Parser.cpp:107
#9 0x5630451d44f2 in WP3Parser::parse(librevenge::RVNGInputStream*, 
WPXEncryption*, WP3Listener*) 
/root/source-libwpd/libwpd-0.10.0/src/lib/WP3Parser.cpp:76
#10 0x5630451d48e7 in WP3Parser::parse(librevenge::RVNGTextInterface*) 
/root/source-libwpd/libwpd-0.10.0/src/lib/WP3Parser.cpp:153
#11 0x5630451cfefd in 
libwpd::WPDocument::parse(librevenge::RVNGInputStream*, 
librevenge::RVNGTextInterface*, char const*) 
/root/source-libwpd/libwpd-0.10.0/src/lib/WPDocument.cpp:340
#12 0x5630451cf600 in main 
/root/source-libwpd/libwpd-0.10.0/src/conv/html/wpd2html.cpp:112
#13 0x7f757c8b32e0 in __libc_start_main

Bug#876003: lintian: Wrong description of tag unknown-testsuite

* Chris Lamb [2017-09-17 10:32]:

but autopkgtest is not the only value allowed.

Hm, are you sure? Note that this is referring to the *source*
package's .dsc file; which is, I believe, almost entirely separate
from the value in debian/control.

Note that the linked "Ref" link:

https://anonscm.debian.org/git/autopkgtest/autopkgtest.git/tree/doc/README.package-tests.rst

… says:

To allow test execution environments to discover packages which provide
tests, their source packages need to have a ``Testsuite:`` header
containing ``autopkgtest`` (which is currently the only defined value).

Please, note the word "currently" in the sentence above. That part of
the document (as revealed by git blame) was not changed since 2014-06-25.
This predates the inclusion of autokgtest-pkg-* valid values by the
autodep8 package whose development, according to git log, started on
2014-09-14.

IMHO, the description in README.package-tests.rst is wrong. BTW, I am
going to file a bug report on this issue against autopkgtest.

At any rate, your explanation is incoherent with the current behavior of
Lintian (v 2.5.52). With the current version of the octave-image
package, the following warning is triggered:

W: octave-image source: unknown-testsuite autopkgtest-pkg-octave

However, if the Testsuite field contained autopkgtest-pkg-go,
autopkgtest-pkg-elpa, etc., then the warning would not triggered, which
proves that Lintian *_does_* accept other values than just "autopkgtest".

Best,

Rafael

Bug#876012: libcanberra-pulse: No system sound with libcanberra + pulseaudio and gtk+ apps

2017-09-17 Thread Stefan Mueller

Package: libcanberra-pulse
Version: 0.30-3
Severity: normal

Dear Maintainer,

some gtk apps (eg. Emacs "window-close", "window-minimized" ... ) have no
system sound with libcanberra and pulseaudio. Other apps works fine without any
problems.

When trying to play sounds there are strange error messages in
/etc/log/user.log

-
Sep 17 13:07:21 onyx pulseaudio[1861]: [pulseaudio] pstream.c: Ignoring
received block reference with non-registered memfd ID = 2314287233
Sep 17 13:07:21 onyx pulseaudio[1861]: [pulseaudio] pstream.c: Ignoring
received block reference with non-registered memfd ID = 2314287233
Sep 17 13:07:21 onyx pulseaudio[1861]: [pulseaudio] pstream.c: Ignoring
received block reference with non-registered memfd ID = 2314287233
Sep 17 13:07:52 onyx pulseaudio[1861]: [pulseaudio] pstream.c: Ignoring
received block reference with non-registered memfd ID = 2314287233
Sep 17 13:07:52 onyx pulseaudio[1861]: [pulseaudio] pstream.c: Ignoring
received block reference with non-registered memfd ID = 2314287233
Sep 17 13:07:52 onyx pulseaudio[1861]: [pulseaudio] pstream.c: Ignoring
received block reference with non-registered memfd ID = 2314287233


Sep 17 13:28:47 onyx pulseaudio[1861]: [pulseaudio] shm.c: mmap() failed: Nicht
genügend Hauptspeicher verfügbar
Sep 17 13:28:47 onyx pulseaudio[1861]: [pulseaudio] protocol-native.c:
Disabling srbchannel, reason: Failed to allocate shared writable memory p
Sep 17 13:28:47 onyx pulseaudio[1861]: [pulseaudio] shm.c: mmap() failed: Nicht
genügend Hauptspeicher verfügbar
Sep 17 13:28:47 onyx pulseaudio[1861]: [pulseaudio] pstream.c: Failed to create
permanent mapping for memfd region with ID = 1792534231
Sep 17 13:29:21 onyx pulseaudio[1861]: [pulseaudio] shm.c: mmap() failed: Nicht
genügend Hauptspeicher verfügbar
Sep 17 13:29:21 onyx pulseaudio[1861]: [pulseaudio] pstream.c: Failed to create
permanent mapping for memfd region with ID = 1453188473
Sep 17 13:29:21 onyx pulseaudio[1861]: [pulseaudio] protocol-native.c: Failed
to register memfd mempool. Reason: could not attach memfd SHM ID t
Sep 17 13:29:21 onyx pulseaudio[1861]: [pulseaudio] shm.c: mmap() failed: Nicht
genügend Hauptspeicher verfügbar
Sep 17 13:29:21 onyx pulseaudio[1861]: [pulseaudio] protocol-native.c:
Disabling srbchannel, reason: Failed to allocate shared writable memory p
Sep 17 13:29:21 onyx pulseaudio[1861]: [pulseaudio] shm.c: mmap() failed: Nicht
genügend Hauptspeicher verfügbar
Sep 17 13:29:21 onyx pulseaudio[1861]: [pulseaudio] pstream.c: Failed to create
permanent mapping for memfd region with ID = 642093521
-


There are other bug reports which describe same problem like this:
https://bugzilla.redhat.com/show_bug.cgi?id=1460517




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

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

Versions of packages libcanberra-pulse depends on:
ii  libc6 2.24-11+deb9u1
ii  libcanberra0  0.30-3
ii  libpulse0 10.0-1+deb9u1
ii  pulseaudio10.0-1+deb9u1

libcanberra-pulse recommends no packages.

libcanberra-pulse suggests no packages.

-- no debconf information

Bug#714925: nmap: [REGRESSION 5.00-3 -> 6.00-0.3] -sP fails with "nexthost: failed to determine route to X.X.X.X"

2017-09-17 Thread Lukas Schwaighofer

Hi Timo,

thanks for the very thorough bug report and for discussing it with
upstream.  I'm doing a bit of housekeeping of the nmap bugs and tried
to determine if this bug is still present.

According to upstream [1], this issue might have been mitigated by
newer versions of the Linux kernel, in particular since Linux version
3.9.  I also wasn't able to reproduce the issue myself (using nmap
7.60-1 and Linux 4.12).

Do you still have a similar setup and would you mind checking if that
problem is still present?

Thank you
Lukas

[1] http://seclists.org/nmap-dev/2013/q3/247

Bug#876013: golang-google-genproto-dev has circular Depends on golang-google-grpc-dev

2017-09-17 Thread Shengjing Zhu

> Hello Debian Go Packaging Team,
>
> There is a circular dependency between golang-google-genproto-dev
> and golang-google-grpc-dev:
>
> golang-google-genproto-dev  :Depends: golang-google-grpc-dev
> golang-google-grpc-dev  :Depends: golang-google-genproto-dev
>
> Circular dependencies are known to cause problems during upgrade between
> stable releases, so we should try to avoid them.
>

I previously try to avoid such circular, but seems failed.

In src:golang-google-grpc, the package tried to avoid Build-Depends
golang-google-genproto-dev, so vendored some files when building.

I put three files in
debian/vendor/google.golang.org/genproto/googleapis/rpc and copy them
to $(BUILDDIR)/src/

However the -dev package can't just do that.

Maybe we need to break the golang-google-genproto-dev to two package,
one that only contains google.golang.org/genproto/googleapis/rpc? like
golang-google-cloud-compute-metadata-dev?

And if we break golang-google-genproto-dev to two -dev package, one is
golang-google-genproto-rpc-dev. Can the src:golang-google-grpc
Build-Depends google-genproto-rpc-dev, maybe the src packages
Build-Depends still have circular?

-- 
Best regards,
Shengjing Zhu

Bug#868279: Replace with --allow-downgrades

Hi,

Since this is for chroot throw-away system, don't worry too much.  We
can take *dangerous* operations ;-)

I have updated pertinent parts with --allow-downgrades for
maint-guide and debmake-doc

Let's keep changes to maint-guide minimum considering it to be replaced
by debmake-doc.

Regards,

Osamu

Bug#851456: Please document this changelog convention

On Sun, Sep 17, 2017 at 09:51:19PM +0900, Osamu Aoki wrote:
> control: reassign -1 debmake-doc
...
> The current text is 
>   https://www.debian.org/doc/manuals/debmake-doc/ch05.en.html#changelog

Since then (1.9-1), I have added few words around there:

diff --git a/asciidoc/25-changelog.txt b/asciidoc/25-changelog.txt
index b0dd43f..0c83d95 100644
--- a/asciidoc/25-changelog.txt
+++ b/asciidoc/25-changelog.txt
@@ -1,12 +1,14 @@
 [[changelog]]
 === debian/changelog

-The *debian/changelog* file records the Debian package history and defines the 
upstream package version and the Debian revision in its first line.
+The *debian/changelog* file records the Debian package history and defines the 
upstream package version and the Debian revision in its first line.  The 
changes need to be documented in the specific, formal, and concise style.

 The *debmake* command creates the initial template file with the upstream 
package version and the Debian revision.  The distribution is set to 
*UNRELEASED* to prevent accidental upload to the Debian archive.

 The *debchange* command (alias *dch*) is used to edit this.

+TIP: You can edit the *debian/changelog* file manually with any text editor as 
long as you follow the formatting convention used by the *debchange* command.
+ 
 TIP: The date string used in the *debian/changelog* file can be manually 
generated by the ``*LC_ALL=C date -R*'' command.

 This is installed in the */usr/share/doc/*'binarypackage' directory as 
*changelog.Debian.gz* by the *dh_installchangelogs* command.

Osamu

Bug#875999: gworldclock : Menu is not translated

2017-09-17 Thread Takeshi Hamasaki

Package: gworldclock
Version: 1.4.4-10
Severity: minor
Tags: patch

Dear Maintainer,

current GTK application needs to use gtk_action_group_set_translation_domain ()
for menu to be translated. Attached patch is to add the function to main.c .

Regards,
Takeshi Hamasaki

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

Kernel: Linux 4.9.30tuxonice (SMP w/4 CPU cores)
Locale: LANG=ja_JP.UTF-8, LC_CTYPE=ja_JP.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to ja_JP.UTF-8), LANGUAGE=ja_JP.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set 
to ja_JP.UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)
--- a/main.c
+++ b/main.c
@@ -376,6 +376,7 @@
 
   /* set up menu */
   action_group = gtk_action_group_new ("UIActions");
+  gtk_action_group_set_translation_domain (action_group, PACKAGE_NAME);
   gtk_action_group_add_actions (action_group, entries, G_N_ELEMENTS (entries), 
clocklist);  
   gtk_action_group_add_toggle_actions (action_group, toggle_entries, 
G_N_ELEMENTS (toggle_entries), clocklist);
   g_object_set_data(G_OBJECT(clocklist), ACTIONS, action_group);

Bug#875733: lxc.mount.auto = cgroup:mixed doesn't seem to work in Stretch anymore

2017-09-17 Thread Evgeni Golov

control: found -1 1:2.0.8-2

Hi,

TL;DR: I can reproduce the "does not create cgroups" behaviour, but I
don't know why yet.

On Thu, Sep 14, 2017 at 10:01:41AM +0200, Yves-Alexis Perez wrote:
> On Thu, 2017-09-14 at 09:23 +0200, Yves-Alexis Perez wrote:
> > Package: lxc
> > Version: 1:2.0.7-2
> > Severity: normal
> > 
> > I'll setup a more simple container and config so I can provide it and
> > some logs to you so you can reproduce.
> 
> lxc-create -n test -t debian
> 
> I added:
> 
> lxc.autodev = 1
> lxc.mount.auto = proc:mixed
> lxc.mount.auto = sys:mixed
> lxc.mount.auto = cgroup:mixed

This is default in LXC 2.0 [3].

> lxc.cap.drop = sys_admin
> 
> to the lxc configuration but I think for now only the two last line matter:
> dropping CAP_SYS_ADMIN will prevent systemd to do the mounts itself,
> lxc.mount.auto = cgroup:mixed should have lxc mount /sys/fs/cgroup properly
> (and thus systemd should be happy), but it's not working.
> 
> I'm starting with:
> 
> lxc-start -n test -o /tmp/lxc.log -l DEBUG -F
> Failed to mount tmpfs at /dev/shm: Operation not permitted
> Failed to mount tmpfs at /run: Operation not permitted
> Failed to mount tmpfs at /run/lock: Operation not permitted
> Failed to mount tmpfs at /sys/fs/cgroup: Operation not permitted
> Failed to mount cgroup at /sys/fs/cgroup/systemd: No such file or directory
> [!!] Failed to mount API filesystems, freezing.
> Freezing execution.

as mentioned on IRC, the behaviour I see is a bit different.
I am using the official Debian Vagrant boxes [1][2], where I just did:
# apt install lxc (1:1.0.6-6+deb8u6 on jessie, 1:2.0.7-2 on stretch)
# lxc-create -n debian8onX -t debian -- -r jessie
# lxc-create -n debian9onX -t debian -- -r stetch

The Jessie version needed two small tweaks to the Debian template to be able to 
bootstrap Stretch.

Without any config changes of the containers, they start just fine with 
`lxc-start -n  -d` and I can attach to them using `lxc-attach -n `.

Jessie host:

root@debian8on8:~# ps aux
USER   PID %CPU %MEMVSZ   RSS TTY  STAT START   TIME COMMAND
root 1  0.3  0.0  27900  4316 ?Ss   11:10   0:00 /sbin/init
root19  0.2  0.0  32968  4348 ?Ss   11:10   0:00 
/lib/systemd/systemd-journald
root68  0.0  0.0  55188  5448 ?Ss   11:10   0:00 /usr/sbin/sshd 
-D
root71  0.0  0.0  12668  1852 tty4 Ss+  11:10   0:00 /sbin/agetty 
--noclear tty4 linux
root72  0.0  0.0  12668  1864 tty1 Ss+  11:10   0:00 /sbin/agetty 
--noclear tty1 linux
root73  0.0  0.0  12668  1860 tty3 Ss+  11:10   0:00 /sbin/agetty 
--noclear tty3 linux
root74  0.0  0.0  12668  1872 tty2 Ss+  11:10   0:00 /sbin/agetty 
--noclear tty2 linux
root75  0.0  0.0  14240  2244 console  Ss+  11:10   0:00 /sbin/agetty 
--noclear --keep-baud console 115200 38400 9600 vt102
root82  0.0  0.0  21868  3704 ?S11:10   0:00 /bin/bash
root83  0.0  0.0  19076  2332 ?R+   11:10   0:00 ps aux

root@debian8on8:~# mount |grep cgroup
cgroup on /sys/fs/cgroup/systemd type cgroup 
(rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/lib/systemd/systemd-cgroups-agent,name=systemd)
cgroup on /sys/fs/cgroup/cpuset type cgroup 
(rw,nosuid,nodev,noexec,relatime,cpuset,clone_children)
cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup 
(rw,nosuid,nodev,noexec,relatime,cpu,cpuacct)
cgroup on /sys/fs/cgroup/devices type cgroup 
(rw,nosuid,nodev,noexec,relatime,devices)
cgroup on /sys/fs/cgroup/freezer type cgroup 
(rw,nosuid,nodev,noexec,relatime,freezer)
cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup 
(rw,nosuid,nodev,noexec,relatime,net_cls,net_prio)
cgroup on /sys/fs/cgroup/blkio type cgroup 
(rw,nosuid,nodev,noexec,relatime,blkio)
cgroup on /sys/fs/cgroup/perf_event type cgroup 
(rw,nosuid,nodev,noexec,relatime,perf_event)

root@debian9on8:~# ps aux
USER   PID %CPU %MEMVSZ   RSS TTY  STAT START   TIME COMMAND
root 1  0.6  0.0  56664  6564 ?Ss   11:49   0:00 /sbin/init
root16  0.1  0.0  46092  5744 ?Ss   11:49   0:00 
/lib/systemd/systemd-journald
root46  0.0  0.0  69944  5704 ?Ss   11:49   0:00 /usr/sbin/sshd 
-D
root48  0.0  0.0  12672  1756 tty4 Ss+  11:49   0:00 /sbin/agetty 
--noclear tty4 linux
root49  0.0  0.0  12672  1664 tty2 Ss+  11:49   0:00 /sbin/agetty 
--noclear tty2 linux
root50  0.0  0.0  12672  1740 tty3 Ss+  11:49   0:00 /sbin/agetty 
--noclear tty3 linux
root51  0.0  0.0  12672  1660 tty1 Ss+  11:49   0:00 /sbin/agetty 
--noclear tty1 linux
root52  0.0  0.0  14316  2076 console  Ss+  11:49   0:00 /sbin/agetty 
--noclear --keep-baud console 115200,38400,9600 vt220
root54  0.0  0.0  19828  3560 ?S11:50   0:00 /bin/bash
root55  0.0  0.0  38276  3268 ?R+   11:50   0:00 ps aux

root@debian9on8:~# mount |grep cgroup
cgroup on /sys/fs/cgroup/systemd type cgroup

Bug#869098: python2.7 2.7.13-4 causes EOFError breakage in python-sphinx

Control: reassign -1 python-sphinx

On 14.09.2017 14:18, Julian Andres Klode wrote:
> On Thu, Jul 20, 2017 at 03:40:52PM +0100, Neil Williams wrote:
>> Package: python2.7
>> Version: 2.7.13-4
>> Severity: serious
>> Justification: causes other packages to FTBFS
>>
>> With 2.7.13-4 installed, I am unable to build documentation as sphinx
>> errors out:
>>
>> sphinx-build -b html -d _build/doctrees  -n -j 4 . _build/html
>> Running Sphinx v1.4.9
>> making output directory...
>> loading pickled environment... not yet created
>> loading intersphinx inventory from https://docs.python.org/2/objects.inv...
>> building [mo]: targets for 0 po files that are out of date
>> building [html]: targets for 91 source files that are out of date
>> updating environment: 91 added, 0 changed, 0 removed
>> reading sources... [100%] test-repositories .. writing-tests 
>>  
>> waiting for workers...
>>
>> Exception occurred:
>>   File "/usr/lib/python2.7/dist-packages/sphinx/util/parallel.py", line 97, 
>> in _join_one
>> exc, result = pipe.recv()
>> EOFError
> 
> Given that this is a regression in 2.7.13-4, can we please revert
> unstable to 2.7.13-3 again (as 2.7.14~rc1+really2.7.13-1 or something).

... and now identified as an issue in sphinx. reassigning.

> Having an rc-buggy python in unstable that breaks reverse dependencies for 
> two months
> is not really acceptable

the only thing here which is not really acceptable is your behaviour of finger
pointing.

Bug#876001: libwpd: CVE-2017-14226

Source: libwpd
Version: 0.10.1-5
Severity: important
Tags: patch security upstream
Forwarded: https://sourceforge.net/p/libwpd/tickets/14/

Hi,

the following vulnerability was published for libwpd.

CVE-2017-14226[0]:
| WP1StylesListener.cpp, WP5StylesListener.cpp, and
| WP42StylesListener.cpp in libwpd 0.10.1 mishandle iterators, which
| allows remote attackers to cause a denial of service (heap-based buffer
| over-read in the WPXTableList class in WPXTable.cpp). This
| vulnerability can be triggered in LibreOffice before 5.3.7. It may lead
| to suffering a remote attack against a LibreOffice application.

If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2017-14226
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-14226
[1] https://sourceforge.net/p/libwpd/tickets/14/
[2] https://bugzilla.redhat.com/show_bug.cgi?id=1489337
[3] 
https://cgit.freedesktop.org/libreoffice/core/commit/?id=dd89afa6ee8166b69e7a1e86f22616ca8fc122c9
[4] 
https://sourceforge.net/p/libwpd/code/ci/0329a9c57f9b3b0efa0f09a5235dfd90236803a5/
[5] 
https://sourceforge.net/p/libwpd/code/ci/f40827b3eae260ce657c67d9fecc855b09dea3c3/
[6] https://bugs.documentfoundation.org/show_bug.cgi?id=112269

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

Bug#876004: newsbeuter: CVE-2017-14500: Podbeuter podcast fetcher: remote code execution

Source: newsbeuter
Version: 2.8-2
Severity: grave
Tags: upstream patch security
Justification: user security hole
Forwarded: https://github.com/akrennmair/newsbeuter/issues/598

Hi,

the following vulnerability was published for newsbeuter.

CVE-2017-14500[0]:
| Improper Neutralization of Special Elements used in an OS Command in
| the podcast playback function of Podbeuter in Newsbeuter 0.3 through
| 2.9 allows remote attackers to perform user-assisted code execution by
| crafting an RSS item with a media enclosure (i.e., a podcast file) that
| includes shell metacharacters in its filename, related to
| pb_controller.cpp and queueloader.cpp, a different vulnerability than
| CVE-2017-12904.

If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2017-14500
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-14500
[1] https://github.com/akrennmair/newsbeuter/issues/598
[2] http://openwall.com/lists/oss-security/2017/09/16/1
[3] 
https://github.com/akrennmair/newsbeuter/commit/26f5a4350f3ab5507bb8727051c87bb04660f333

Regards,
Salvatore

Bug#876006: fix build with glibc-2.26, fix autopkg tests with M-A'd openblas/atlas

Package: src:python-numpy
Severity: important
Tags: patch sid buster

  * Fix autopkg test dependencies.
  * Fix build with glibc-2.26.
  * Fix atlas and openblas tests for openblas and atlas multiarch
locations.


  * Fix autopkg test dependencies.
  * Fix build with glibc-2.26.
  * Fix atlas and openblas tests for openblas and atlas multiarch
locations.

diff -pruN 1:1.12.1-3.1/debian/patches/glibc-include.diff 1:1.12.1-3.1ubuntu4/debian/patches/glibc-include.diff
--- 1:1.12.1-3.1/debian/patches/glibc-include.diff	1970-01-01 00:00:00.0 +
+++ 1:1.12.1-3.1ubuntu4/debian/patches/glibc-include.diff	2017-09-15 06:16:10.0 +
@@ -0,0 +1,13 @@
+Index: b/numpy/core/src/multiarray/numpyos.c
+===
+--- a/numpy/core/src/multiarray/numpyos.c
 b/numpy/core/src/multiarray/numpyos.c
+@@ -15,7 +15,7 @@
+ 
+ #ifdef HAVE_STRTOLD_L
+ #include 
+-#include 
++#include 
+ #endif
+ 
+ 
diff -pruN 1:1.12.1-3.1/debian/tests/atlas 1:1.12.1-3.1ubuntu4/debian/tests/atlas
--- 1:1.12.1-3.1/debian/tests/atlas	2017-05-27 23:44:59.0 +
+++ 1:1.12.1-3.1ubuntu4/debian/tests/atlas	2017-09-15 05:57:43.0 +
@@ -1,7 +1,8 @@
 #!/bin/sh
 set -efu
-blaslib=$(update-alternatives --list libblas.so.3 | grep $(basename $0))
-update-alternatives --set libblas.so.3 $blaslib
+ma=$(dpkg-architecture -qDEB_HOST_MULTIARCH)
+blaslib=$(update-alternatives --list libblas.so.3-$ma | grep $(basename $0))
+update-alternatives --set libblas.so.3-$ma $blaslib
 
 # one python is enough
 PYS=${PYS:-"$(pyversions -d 2>/dev/null)"}
diff -pruN 1:1.12.1-3.1/debian/tests/control 1:1.12.1-3.1ubuntu4/debian/tests/control
--- 1:1.12.1-3.1/debian/tests/control	2017-05-27 23:44:59.0 +
+++ 1:1.12.1-3.1ubuntu4/debian/tests/control	2017-09-15 12:19:13.0 +
@@ -1,23 +1,24 @@
 Tests: python2
-Depends: python-numpy, python-all, python-nose, python-tz
+Depends: build-essential, python-numpy, python-all, python-nose, python-tz
 
 Tests: python3
-Depends: python3-numpy, python3-all, python3-nose, python3-tz
+Depends: build-essential, python3-numpy, python3-all, python3-nose, python3-tz
 
 #needs root for update-alternatives
 Tests: openblas
 Restrictions: needs-root
-Depends: python-numpy, python-all, python-nose, python-tz, libopenblas-base
+Depends: python-numpy, python-all, python-nose, python-tz, libopenblas-base, dpkg-dev, gcc
 
 #needs root for update-alternatives
 Tests: atlas
 Restrictions: needs-root
-Depends: python-numpy, python-all, python-nose, python-tz, libatlas3-base
+Depends: python-numpy, python-all, python-nose, python-tz, libatlas3-base, dpkg-dev, gcc
 
 Tests: f2py
 Depends: build-essential, gfortran, python-numpy, python-numpy-dbg, python-all, python-all-dbg, python-all-dev, python3-numpy, python3-numpy-dbg, python3-all, python3-all-dbg, python3-all-dev
 
 Tests: distutils
+Restrictions: allow-stderr
 Depends: build-essential, libfftw3-dev, python-numpy
 
 Tests: capi
diff -pruN 1:1.12.1-3.1/debian/tests/openblas 1:1.12.1-3.1ubuntu4/debian/tests/openblas
--- 1:1.12.1-3.1/debian/tests/openblas	2017-05-27 23:44:59.0 +
+++ 1:1.12.1-3.1ubuntu4/debian/tests/openblas	2017-09-15 05:56:28.0 +
@@ -1,7 +1,8 @@
 #!/bin/sh
 set -efu
-blaslib=$(update-alternatives --list libblas.so.3 | grep $(basename $0))
-update-alternatives --set libblas.so.3 $blaslib
+ma=$(dpkg-architecture -qDEB_HOST_MULTIARCH)
+blaslib=$(update-alternatives --list libblas.so.3-$ma | grep $(basename $0))
+update-alternatives --set libblas.so.3-$ma $blaslib
 
 # one python is enough
 PYS=${PYS:-"$(pyversions -d 2>/dev/null)"}

Bug#876003: lintian: Wrong description of tag unknown-testsuite


* Rafael Laboissière  [2017-09-17 11:59]:

IMHO, the description in README.package-tests.rst is wrong.  BTW, I am 
going to file a bug report on this issue against autopkgtest.


Done: https://bugs.debian.org/876008

Rafael

Bug#876008: autopkgtest: Wrong statement about Testsuite field in documentation

2017-09-17 Thread Martin Pitt

Control: tag -1 pending

Hello Rafael,

Rafael Laboissière [2017-09-17 12:11 +0200]:
> In file doc/README.package-tests.rst, there is this sentence:
> 
>To allow test execution environments to discover packages which
>provide tests, their source packages need to have a ``Testsuite:``
>header containing ``autopkgtest`` (which is currently the only
>defined value).
> 
> This was true in 2014, before the autodep8 pacakge started introducing the
> autopkgtest-pkg-* values.  The statement is innacurate today.

Indeed, and I fixed that in git about a month ago already:

  https://anonscm.debian.org/git/autopkgtest/autopkgtest.git/commit/?id=f818619

(I'll add the Closes # for this bug). I didn't upload a new autopkgtest so far,
as git has changes which need a newer debci. This just got unblocked yesterday,
so I'll do an upload soon.

Thanks,

Martin

Bug#876011: ITP: gtk+4.0 -- GTK+ graphical user interface library

2017-09-17 Thread Jeremy Bicha

Package: wnpp
Severity: wishlist
X-Debbugs-CC: debian-de...@lists.debian.org
Owner: jbi...@debian.org

Package Name: gtk+4.0
Version: 3.91.2
Upstream Authors : Many. See debian/copyright
License : LGPL-2+
Programming Lang: C

Description: GTK+ graphical user interface library
 GTK+ is a multi-platform toolkit for creating graphical user
 interfaces. Offering a complete set of widgets, GTK+ is suitable
 for projects ranging from small one-off tools to complete application
 suites.

Other Info
--
The Debian GNOME team intends to maintain this package.

Since gtk4 is still in beta development and we aren't aware of any
apps that require gtk4 yet, we will be uploading this to experimental.

Packaging is currently in svn at
svn://anonscm.debian.org/pkg-gnome/desktop/unstable/gtk+4.0/
You can browse at
https://anonscm.debian.org/viewvc/pkg-gnome/desktop/experimental/gtk%2B4.0/

Thanks,
Jeremy Bicha

Bug#876001: libwpd: CVE-2017-14226

Hi,


On Sun, Sep 17, 2017 at 10:47:06AM +0200, Salvatore Bonaccorso wrote:
> Source: libwpd
> Version: 0.10.1-5
> Severity: important
> Tags: patch security upstream
> Forwarded: https://sourceforge.net/p/libwpd/tickets/14/
> 
> Hi,
> 
> the following vulnerability was published for libwpd.
>
> CVE-2017-14226[0]:
[...]

fixed in 0.10.2-1 for sid. Want this fixed as DSAs for jessie/stretch?

Prepared packages. Debdiffs attached...

Regards,

Rene
diff -Nru libwpd-0.10.1/debian/changelog libwpd-0.10.1/debian/changelog
--- libwpd-0.10.1/debian/changelog  2016-09-12 22:58:36.0 +0200
+++ libwpd-0.10.1/debian/changelog  2017-09-17 13:20:30.0 +0200
@@ -1,3 +1,10 @@
+libwpd (0.10.1-5+deb9u1) stretch; urgency=medium
+
+  * debian/patches/libwpd-tdf112269.diff: backport patch to fix
+CVE-2017-14226 (closes: #876001)
+
+ -- Rene Engelhard   Sun, 17 Sep 2017 13:20:30 +0200
+
 libwpd (0.10.1-5) unstable; urgency=medium
 
   * [7d35591] move Maintainer: to Debian LibreOffice Maintainers
diff -Nru libwpd-0.10.1/debian/patches/libwpd-tdf112269.diff 
libwpd-0.10.1/debian/patches/libwpd-tdf112269.diff
--- libwpd-0.10.1/debian/patches/libwpd-tdf112269.diff  1970-01-01 
01:00:00.0 +0100
+++ libwpd-0.10.1/debian/patches/libwpd-tdf112269.diff  2017-09-17 
13:20:30.0 +0200
@@ -0,0 +1,43 @@
+--- libwpd/src/lib/WP5StylesListener.cpp
 libwpd/src/lib/WP5StylesListener.cpp
+@@ -85,8 +85,9 @@
+   m_currentPage = WPXPageSpan(m_pageList.back(), 0.0, 0.0);
+   m_currentPage.setPageSpan(1);
+ 
+-  for (std::vector::const_iterator HFiter = 
(m_nextPage.getHeaderFooterList()).begin();
+-  HFiter != (m_nextPage.getHeaderFooterList()).end(); 
++HFiter)
++  std::vector headerFooterList = 
m_nextPage.getHeaderFooterList();
++  for (std::vector::const_iterator HFiter = 
headerFooterList.begin();
++  HFiter != headerFooterList.end(); ++HFiter)
+   {
+   if ((*HFiter).getOccurrence() != NEVER)
+   {
+--- libwpd/src/lib/WP42StylesListener.cpp
 libwpd/src/lib/WP42StylesListener.cpp
+@@ -84,8 +84,9 @@
+   m_currentPage = WPXPageSpan(m_pageList.back(), 0.0, 
0.0);
+   m_currentPage.setPageSpan(1);
+ 
+-  for (std::vector::const_iterator 
HFiter = (m_nextPage.getHeaderFooterList()).begin();
+-  HFiter != 
(m_nextPage.getHeaderFooterList()).end(); ++HFiter)
++  std::vector headerFooterList = 
m_nextPage.getHeaderFooterList();
++  for (std::vector::const_iterator 
HFiter = headerFooterList.begin();
++  HFiter != headerFooterList.end(); ++HFiter)
+   {
+   if ((*HFiter).getOccurrence() != NEVER)
+   {
+--- libwpd/src/lib/WP1StylesListener.cpp
 libwpd/src/lib/WP1StylesListener.cpp
+@@ -83,8 +83,9 @@
+   m_currentPage = WPXPageSpan(m_pageList.back(), 0.0, 
0.0);
+   m_currentPage.setPageSpan(1);
+ 
+-  for (std::vector::const_iterator 
HFiter = (m_nextPage.getHeaderFooterList()).begin();
+-  HFiter != 
(m_nextPage.getHeaderFooterList()).end(); ++HFiter)
++  std::vector headerFooterList = 
m_nextPage.getHeaderFooterList();
++  for (std::vector::const_iterator 
HFiter = headerFooterList.begin();
++  HFiter != headerFooterList.end(); ++HFiter)
+   {
+   if ((*HFiter).getOccurrence() != NEVER)
+   {
+
diff -Nru libwpd-0.10.1/debian/patches/series 
libwpd-0.10.1/debian/patches/series
--- libwpd-0.10.1/debian/patches/series 1970-01-01 01:00:00.0 +0100
+++ libwpd-0.10.1/debian/patches/series 2017-09-17 13:20:30.0 +0200
@@ -0,0 +1 @@
+libwpd-tdf112269.diff
diff -Nru libwpd-0.10.0/debian/changelog libwpd-0.10.0/debian/changelog
--- libwpd-0.10.0/debian/changelog  2014-08-08 00:36:00.0 +0200
+++ libwpd-0.10.0/debian/changelog  2017-09-17 13:20:30.0 +0200
@@ -1,3 +1,10 @@
+libwpd (0.10.0-2+deb8u1) jessie; urgency=medium
+
+  * debian/patches/libwpd-tdf112269.diff: backport patch to fix
+CVE-2017-14226 (closes: #876001)
+
+ -- Rene Engelhard   Sun, 17 Sep 2017 13:20:30 +0200
+
 libwpd (0.10.0-2) unstable; urgency=low
 
   * upload to unstable
diff -Nru libwpd-0.10.0/debian/patches/libwpd-tdf112269.diff 
libwpd-0.10.0/debian/patches/libwpd-tdf112269.diff
--- libwpd-0.10.0/debian/patches/libwpd-tdf112269.diff  1970-01-01 
01:00:00.0 +0100
+++ libwpd-0.10.0/debian/patches/libwpd-tdf112269.diff  2017-09-17 
13:20:30.0 +0200
@@ -0,0 +1,43 @@
+--- libwpd/src/lib/WP5StylesListener.cpp

Bug#876014: Debian mirror mirror.units.it: permission denied

2017-09-17 Thread Peter Palfrader

Package: mirrors
User: mirr...@packages.debian.org
Usertags: mirror-problem may-auto-close
Control: submitter -1 mirr...@debian.org

Hi!

It seems your mirror started returning 403 Forbidden - You don't have
permission to access /debian/ on this server.

Status: https://mirror-master.debian.org/status/mirror-info/mirror.units.it.html

Please investigate
-- 
|  .''`.   ** Debian **
  Peter Palfrader   | : :' :  The  universal
 https://www.palfrader.org/ | `. `'  Operating System
|   `-https://www.debian.org/

Bug#853548: mgetty: diff for NMU version 1.1.36-3.1

2017-09-17 Thread Adrian Bunk

Control: tags 853548 + pending

Dear maintainer,

I've prepared an NMU for mgetty (versioned as 1.1.36-3.1) and uploaded 
it to DELAYED/10. Please feel free to tell me if I should cancel it.

cu
Adrian

-- 

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

diff -u mgetty-1.1.36/debian/changelog mgetty-1.1.36/debian/changelog
--- mgetty-1.1.36/debian/changelog
+++ mgetty-1.1.36/debian/changelog
@@ -1,3 +1,11 @@
+mgetty (1.1.36-3.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Add patch from Hilko Bengen to fix FTBFS with gcc 7.
+(Closes: #853548)
+
+ -- Adrian Bunk   Sun, 17 Sep 2017 15:06:51 +0300
+
 mgetty (1.1.36-3) unstable; urgency=medium
 
   * Add build-arch and build-indep targets in debian/rules. Closes: #822056
diff -u mgetty-1.1.36/debian/patches/00list mgetty-1.1.36/debian/patches/00list
--- mgetty-1.1.36/debian/patches/00list
+++ mgetty-1.1.36/debian/patches/00list
@@ -31,0 +32,2 @@
+
+81-gcc7
only in patch2:
unchanged:
--- mgetty-1.1.36.orig/debian/patches/81-gcc7
+++ mgetty-1.1.36/debian/patches/81-gcc7
@@ -0,0 +1,79 @@
+#! /bin/sh /usr/share/dpatch/dpatch-run
+## by Hilko Bengen 
+## see #853548
+##
+## All lines beginning with `## DP:' are a description of the patch.
+## DP: make some functions static
+
+@DPATCH@
+index 8a4b708..4205d33 100644
+--- a/g3/g3cat.c
 b/g3/g3cat.c
+@@ -67,6 +67,7 @@ void putcode _P2( (code, len), int code, int len )
+ }
+ 
+ #ifdef __GNUC__
++static
+ inline
+ #endif
+ void putwhitespan _P1( (l), int l )
+@@ -98,6 +99,7 @@ void putwhitespan _P1( (l), int l )
+ }
+ 
+ #ifdef __GNUC__
++static
+ inline
+ #endif
+ void putblackspan _P1( (l), int l )
+@@ -129,6 +131,7 @@ void putblackspan _P1( (l), int l )
+ }
+ 
+ #ifdef __GNUC__
++static
+ inline
+ #endif
+ void puteol _P0( void )			/* write byte-aligned EOL */
+diff --git a/g3/pbm2g3.c b/g3/pbm2g3.c
+index 283a728..1641782 100644
+--- a/g3/pbm2g3.c
 b/g3/pbm2g3.c
+@@ -40,6 +40,7 @@ static unsigned int out_hibit = 0;
+ static int out_byte_tab[ 256 ];			/* for g3 byte reversal */
+ 
+ #ifdef __GNUC__
++static
+ inline
+ #endif
+ void putcode _P2( (code, len), int code, int len )
+@@ -60,6 +61,7 @@ void putcode _P2( (code, len), int code, int len )
+ }
+ 
+ #ifdef __GNUC__
++static
+ inline
+ #endif
+ void puteol _P0( void )			/* write byte-aligned EOL */
+@@ -69,6 +71,7 @@ void puteol _P0( void )			/* write byte-aligned EOL */
+ }
+ 
+ #ifdef __GNUC__
++static
+ inline
+ #endif
+ void putwhitespan _P1( (l), int l )
+@@ -99,9 +102,10 @@ void putwhitespan _P1( (l), int l )
+ putcode( t_white[l].bit_code, t_white[l].bit_length );
+ }
+ 
+ #ifdef __GNUC__
++static
+ inline
+ #endif
+ void putblackspan _P1( (l), int l )
+ {
+ if ( l >= 64 )
+-- 
+2.14.1
+
+
+--=-=-=--

Bug#875990: [Qa-jenkins-dev] Bug#875990: reproducible: i/o issues with profitbricks-build2-i386 since stretch upgrade

2017-09-17 Thread Holger Levsen

Hi Vagrant,

thanks for filling this bug and thus properly documenting what we had 
discovered,
discussed and lost on IRC already…

On Sat, Sep 16, 2017 at 07:48:42PM -0700, Vagrant Cascadian wrote:
> My *hunch* is that build2 and build12 are running a PAE kernel with more
> than 8GB of ram, and affected by this kernel bug (introduced in linux
> ~4.2, possibly):
>   https://bugzilla.kernel.org/show_bug.cgi?id=196157
>   https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1698118
 
indeed!

> Reducing the ram of the affected builders to 8GB and having more PAE
> builders with lighter workloads might be a workaround that would get
> better performance... while still testing 32/64-bit kernel
> variation.

we lack the diskspace to do so.
 
> Alternately, switching to only amd64 kernels might also fix the issue,
> though wouldn't test 32/64-bit kernel variations.

indeed.

> Running a linux 4.1 kernel from snapshot.debian.org might be another way
> to test the issue, even if not running long-term.

yeah.

another option is to just wait. :/


-- 
cheers,
Holger


signature.asc
Description: Digital signature

Bug#876016: node-babel-core has circular Depends on node-babel-register

Package: node-babel-core
Version: 6.25.0+dfsg-2
Severity: important

Hello Debian Javascript Maintainers,

There is a circular dependency between node-babel-core and node-babel-register:

node-babel-core :Depends: node-babel-register (>= 6.18.0)
node-babel-register :Depends: node-babel-core (>= 6.18.0)

Circular dependencies involving shared libraries are known to cause problems
during upgrade between stable releases, so we should try to avoid them.

See threads 
http://lists.debian.org/debian-devel/2005/06/msg02111.html
http://lists.debian.org/debian-devel/2005/11/msg01101.html

Cheers,
-- 
Bill. 

Imagine a large red swirl here.

Bug#851456: Processed: Please document this changelog convention

control: retitle -1 Document the changelog convention
control: severity -1 wishlist
control: tags -1 moreinfo
control: reassign -1 debmake-doc

Hi,

Please note these are tutorial docs.

I will place maint-guide to be about-to-be -deprecated.  I am replacing
it as debmake-doc.  So I don't accept non-critical changes on
maint-guide.  (Thus reassigning)

> > found -1 maint-guide/1.2.37
> Bug #851456 [maint-guide] Please document this changelog convention
> Marked as found in versions maint-guide/1.2.37.

https://bugs.debian.org/844184 discussion seems to be that Sean Whitton
is asking d/changelog entry to be "sensible and understandable".

As for normative documentation, that should happen in "Debian Policy"
(Hi Sean!).

https://www.debian.org/doc/debian-policy/index.html#s-dpkgchangelog

This seems to be OK except for the fact it lacks multi-maintainer
changelog format normally generated by dch command.

In terms of writing style, that is something developers reference should
elaborate but policy may provide cursory guidance.

I don't go into such details unless someone gives me a concise list of
such guidelines which fits into the tutorial.  To be honest, I don't
write a good changelog.

The current text is 
  https://www.debian.org/doc/manuals/debmake-doc/ch05.en.html#changelog

Regards,

Osamu

Bug#876021: libreoffice-writer: launching writer makes libreoffice crash

2017-09-17 Thread Jérôme

Package: libreoffice-writer
Version: 1:5.2.7-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,


I tried to launch Libreoffice Writer by the desktop menu entry, nothing
happends. However, I successfully ran Calc, Impress and Draw.

Next, I opened a terminal and launched the "libreoffice" command.
Then only warning error I got was :
---
** (soffice:1099): WARNING **: Error retrieving accessibility bus address:
org.freedesktop.DBus.Error.ServiceUnknown: The name org.a11y.Bus was not
provided by any .service files
---
Next the Libreoffice window appeared and I achieved to run Calc, Impress and
Draw. However, if I try to open a new Writer document, then all Libreoffice
window disappear.

The next time I'm running "libreoffice", a window proposes to restore the Calc,
Impress and Draw documents.

I can reproduce this bug always.



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

Kernel: Linux 4.9.0-3-686 (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 libreoffice-writer depends on:
ii  dpkg   1.18.24
ii  libabw-0.1-1   0.1.1-4
ii  libc6  2.24-11+deb9u1
ii  libe-book-0.1-10.1.2-4
ii  libetonyek-0.1-1   0.1.6-5
ii  libgcc11:6.3.0-18
ii  libicu57   57.1-6
ii  libmwaw-0.3-3  0.3.9-2
ii  libodfgen-0.1-10.1.6-2
ii  libreoffice-base-core  1:5.2.7-1
ii  libreoffice-core   1:5.2.7-1
ii  librevenge-0.0-0   0.0.4-6
ii  libstdc++6 6.3.0-18
ii  libwpd-0.10-10 0.10.1-5
ii  libwpg-0.3-3   0.3.1-3
ii  libwps-0.4-4   0.4.5-1
ii  libxml22.9.4+dfsg1-2.2+deb9u1
ii  uno-libs3  5.2.7-1
ii  ure5.2.7-1
ii  zlib1g 1:1.2.8.dfsg-5

Versions of packages libreoffice-writer recommends:
ii  libreoffice-math  1:5.2.7-1

Versions of packages libreoffice-writer suggests:
ii  default-jre [java5-runtime]2:1.8-58
ii  fonts-crosextra-caladea20130214-1
ii  fonts-crosextra-carlito20130920-1
ii  libreoffice-base   1:5.2.7-1
pn  libreoffice-gcj
ii  libreoffice-java-common1:5.2.7-1
ii  openjdk-8-jre [java5-runtime]  8u141-b15-1~deb9u1

Versions of packages libreoffice-core depends on:
ii  fontconfig2.11.0-6.7+b1
ii  fonts-opensymbol  2:102.7+LibO5.2.7-1
ii  libboost-date-time1.62.0  1.62.0+dfsg-4
ii  libc6 2.24-11+deb9u1
ii  libcairo2 1.14.8-1
ii  libclucene-contribs1v52.3.3.4+dfsg-1
ii  libclucene-core1v52.3.3.4+dfsg-1
ii  libcmis-0.5-5v5   0.5.1+git20160603-3+b1
ii  libcups2  2.2.1-8
ii  libcurl3-gnutls   7.52.1-5
ii  libdbus-1-3   1.10.18-1
ii  libdbus-glib-1-2  0.108-2
ii  libdconf1 0.26.0-2+b1
ii  libeot0   0.01-4+b1
ii  libexpat1 2.2.0-2+deb9u1
ii  libexttextcat-2.0-0   3.4.4-2+b1
ii  libfontconfig12.11.0-6.7+b1
ii  libfreetype6  2.6.3-3.2
ii  libgcc1   1:6.3.0-18
ii  libgl1-mesa-glx [libgl1]  13.0.6-1+b2
ii  libglew2.02.0.0-3+b1
ii  libglib2.0-0  2.50.3-2
ii  libgltf-0.0-0v5   0.0.2-5
ii  libglu1-mesa [libglu1]9.0.0-2.1
ii  libgraphite2-31.3.10-1
ii  libharfbuzz-icu0  1.4.2-1
ii  libharfbuzz0b 1.4.2-1
ii  libhunspell-1.4-0 1.4.1-2+b2
ii  libhyphen02.8.8-5
ii  libice6   2:1.0.9-2
ii  libicu57  57.1-6
ii  libjpeg62-turbo   1:1.5.1-2
ii  liblangtag1   0.6.2-1
ii  liblcms2-22.8-4
ii  libldap-2.4-2 2.4.44+dfsg-5
ii  libmythes-1.2-0   2:1.2.4-3
ii  libneon27-gnutls  0.30.2-2
ii  libnspr4  2:4.12-6
ii  libnss3   2:3.26.2-1.1
ii  libodfgen-0.1-1   0.1.6-2
ii  libpcre3  2:8.39-3
ii  libpng16-16   1.6.28-1
ii  librdf0   1.0.17-1.1
ii  libreoffice-common1:5.2.7-1
ii  librevenge-0.0-0  0.0.4-6
ii  libsm62:1.2.2-1+b3
ii  libstdc++66.3.0-18
ii  libx11-6  2:1.6.4-3
ii  libxext6  2:1.3.3-1+b2
ii  libxinerama1  2:1.1.3-1+b3
ii  libxml2   2.9.4+dfsg1-2.2+deb9u1
ii  libxrandr22:1.5.1-1
ii  libxrender1   1:0.9.10-1
ii  libxslt1.11.1.29-2.1
ii  uno-libs3 5.2.7-1
ii  ure   5.2.7-1
ii  zlib1g1:1.2.8.dfsg-5

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

-- no debconf information

Bug#876019: jessie-pu: package libwpd/0.10.0-2+deb8u1

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

Hi,

See http://bugs.debian.org/876001. CVE classified as no-dsa (minor issue).

Salvatore writes:

"Sicne the point releases are approaching, can you shedule the fixes
since already prepared in the next point release?"

So here I am.

Debdiff attached.

Regards,

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

Kernel: Linux 3.18.0-trunk-rpi2 (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
diff -Nru libwpd-0.10.0/debian/changelog libwpd-0.10.0/debian/changelog
--- libwpd-0.10.0/debian/changelog  2014-08-08 00:36:00.0 +0200
+++ libwpd-0.10.0/debian/changelog  2017-09-17 13:20:30.0 +0200
@@ -1,3 +1,10 @@
+libwpd (0.10.0-2+deb8u1) jessie; urgency=medium
+
+  * debian/patches/libwpd-tdf112269.diff: backport patch to fix
+CVE-2017-14226 (closes: #876001)
+
+ -- Rene Engelhard   Sun, 17 Sep 2017 13:20:30 +0200
+
 libwpd (0.10.0-2) unstable; urgency=low
 
   * upload to unstable
diff -Nru libwpd-0.10.0/debian/patches/libwpd-tdf112269.diff 
libwpd-0.10.0/debian/patches/libwpd-tdf112269.diff
--- libwpd-0.10.0/debian/patches/libwpd-tdf112269.diff  1970-01-01 
01:00:00.0 +0100
+++ libwpd-0.10.0/debian/patches/libwpd-tdf112269.diff  2017-09-17 
13:20:30.0 +0200
@@ -0,0 +1,43 @@
+--- libwpd/src/lib/WP5StylesListener.cpp
 libwpd/src/lib/WP5StylesListener.cpp
+@@ -85,8 +85,9 @@
+   m_currentPage = WPXPageSpan(m_pageList.back(), 0.0, 0.0);
+   m_currentPage.setPageSpan(1);
+ 
+-  for (std::vector::const_iterator HFiter = 
(m_nextPage.getHeaderFooterList()).begin();
+-  HFiter != (m_nextPage.getHeaderFooterList()).end(); 
++HFiter)
++  std::vector headerFooterList = 
m_nextPage.getHeaderFooterList();
++  for (std::vector::const_iterator HFiter = 
headerFooterList.begin();
++  HFiter != headerFooterList.end(); ++HFiter)
+   {
+   if ((*HFiter).getOccurrence() != NEVER)
+   {
+--- libwpd/src/lib/WP42StylesListener.cpp
 libwpd/src/lib/WP42StylesListener.cpp
+@@ -84,8 +84,9 @@
+   m_currentPage = WPXPageSpan(m_pageList.back(), 0.0, 
0.0);
+   m_currentPage.setPageSpan(1);
+ 
+-  for (std::vector::const_iterator 
HFiter = (m_nextPage.getHeaderFooterList()).begin();
+-  HFiter != 
(m_nextPage.getHeaderFooterList()).end(); ++HFiter)
++  std::vector headerFooterList = 
m_nextPage.getHeaderFooterList();
++  for (std::vector::const_iterator 
HFiter = headerFooterList.begin();
++  HFiter != headerFooterList.end(); ++HFiter)
+   {
+   if ((*HFiter).getOccurrence() != NEVER)
+   {
+--- libwpd/src/lib/WP1StylesListener.cpp
 libwpd/src/lib/WP1StylesListener.cpp
+@@ -83,8 +83,9 @@
+   m_currentPage = WPXPageSpan(m_pageList.back(), 0.0, 
0.0);
+   m_currentPage.setPageSpan(1);
+ 
+-  for (std::vector::const_iterator 
HFiter = (m_nextPage.getHeaderFooterList()).begin();
+-  HFiter != 
(m_nextPage.getHeaderFooterList()).end(); ++HFiter)
++  std::vector headerFooterList = 
m_nextPage.getHeaderFooterList();
++  for (std::vector::const_iterator 
HFiter = headerFooterList.begin();
++  HFiter != headerFooterList.end(); ++HFiter)
+   {
+   if ((*HFiter).getOccurrence() != NEVER)
+   {
+
diff -Nru libwpd-0.10.0/debian/patches/series 
libwpd-0.10.0/debian/patches/series
--- libwpd-0.10.0/debian/patches/series 1970-01-01 01:00:00.0 +0100
+++ libwpd-0.10.0/debian/patches/series 2017-09-17 13:20:30.0 +0200
@@ -0,0 +1 @@
+libwpd-tdf112269.diff

Bug#876020: jessie-pu: package libwpd/0.10.1-5+deb9u1

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

Hi,

See http://bugs.debian.org/876001. CVE classified as no-dsa (minor issue).

Salvatore writes:

"Sicne the point releases are approaching, can you shedule the fixes
since already prepared in the next point release?"

So here I am.

Debdiff attached.

Regards,

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

Kernel: Linux 3.18.0-trunk-rpi2 (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
diff -Nru libwpd-0.10.1/debian/changelog libwpd-0.10.1/debian/changelog
--- libwpd-0.10.1/debian/changelog  2016-09-12 22:58:36.0 +0200
+++ libwpd-0.10.1/debian/changelog  2017-09-17 13:20:30.0 +0200
@@ -1,3 +1,10 @@
+libwpd (0.10.1-5+deb9u1) stretch; urgency=medium
+
+  * debian/patches/libwpd-tdf112269.diff: backport patch to fix
+CVE-2017-14226 (closes: #876001)
+
+ -- Rene Engelhard   Sun, 17 Sep 2017 13:20:30 +0200
+
 libwpd (0.10.1-5) unstable; urgency=medium
 
   * [7d35591] move Maintainer: to Debian LibreOffice Maintainers
diff -Nru libwpd-0.10.1/debian/patches/libwpd-tdf112269.diff 
libwpd-0.10.1/debian/patches/libwpd-tdf112269.diff
--- libwpd-0.10.1/debian/patches/libwpd-tdf112269.diff  1970-01-01 
01:00:00.0 +0100
+++ libwpd-0.10.1/debian/patches/libwpd-tdf112269.diff  2017-09-17 
13:20:30.0 +0200
@@ -0,0 +1,43 @@
+--- libwpd/src/lib/WP5StylesListener.cpp
 libwpd/src/lib/WP5StylesListener.cpp
+@@ -85,8 +85,9 @@
+   m_currentPage = WPXPageSpan(m_pageList.back(), 0.0, 0.0);
+   m_currentPage.setPageSpan(1);
+ 
+-  for (std::vector::const_iterator HFiter = 
(m_nextPage.getHeaderFooterList()).begin();
+-  HFiter != (m_nextPage.getHeaderFooterList()).end(); 
++HFiter)
++  std::vector headerFooterList = 
m_nextPage.getHeaderFooterList();
++  for (std::vector::const_iterator HFiter = 
headerFooterList.begin();
++  HFiter != headerFooterList.end(); ++HFiter)
+   {
+   if ((*HFiter).getOccurrence() != NEVER)
+   {
+--- libwpd/src/lib/WP42StylesListener.cpp
 libwpd/src/lib/WP42StylesListener.cpp
+@@ -84,8 +84,9 @@
+   m_currentPage = WPXPageSpan(m_pageList.back(), 0.0, 
0.0);
+   m_currentPage.setPageSpan(1);
+ 
+-  for (std::vector::const_iterator 
HFiter = (m_nextPage.getHeaderFooterList()).begin();
+-  HFiter != 
(m_nextPage.getHeaderFooterList()).end(); ++HFiter)
++  std::vector headerFooterList = 
m_nextPage.getHeaderFooterList();
++  for (std::vector::const_iterator 
HFiter = headerFooterList.begin();
++  HFiter != headerFooterList.end(); ++HFiter)
+   {
+   if ((*HFiter).getOccurrence() != NEVER)
+   {
+--- libwpd/src/lib/WP1StylesListener.cpp
 libwpd/src/lib/WP1StylesListener.cpp
+@@ -83,8 +83,9 @@
+   m_currentPage = WPXPageSpan(m_pageList.back(), 0.0, 
0.0);
+   m_currentPage.setPageSpan(1);
+ 
+-  for (std::vector::const_iterator 
HFiter = (m_nextPage.getHeaderFooterList()).begin();
+-  HFiter != 
(m_nextPage.getHeaderFooterList()).end(); ++HFiter)
++  std::vector headerFooterList = 
m_nextPage.getHeaderFooterList();
++  for (std::vector::const_iterator 
HFiter = headerFooterList.begin();
++  HFiter != headerFooterList.end(); ++HFiter)
+   {
+   if ((*HFiter).getOccurrence() != NEVER)
+   {
+
diff -Nru libwpd-0.10.1/debian/patches/series 
libwpd-0.10.1/debian/patches/series
--- libwpd-0.10.1/debian/patches/series 1970-01-01 01:00:00.0 +0100
+++ libwpd-0.10.1/debian/patches/series 2017-09-17 13:20:30.0 +0200
@@ -0,0 +1 @@
+libwpd-tdf112269.diff

Bug#876001: libwpd: CVE-2017-14226

On Sun, Sep 17, 2017 at 03:08:19PM +0200, Salvatore Bonaccorso wrote:
> Sicne the point releases are approaching, can you shedule the fixes
> since already prepared in the next point release?

*sigh* :). Just that I need to build that again without -sa..

Bugs filed.

Regards,

Rene

Bug#861147: sbuild

control: tags -1 wontfix

Hi,

sbuild is mentioned in 
 https://www.debian.org/doc/manuals/maint-guide/build.en.html#ftn.idm2850
 https://www.debian.org/doc/manuals/debmake-doc/ch03.en.html#ftn.idm627

I know the code of sbuild is organized nicely and good for building some
purpose build chroot system, pbuilder is better for novice for package
building.

So current level of mention is appropriate for tutorial document like
maint-guide and debmake-doc.

Regards,

Osamu

Bug#876026: libxine2-dev: move libxine.pc to a multiarch location

2017-09-17 Thread Helmut Grohne

Package: libxine2-dev
Version: 1.2.6-1.3
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap
Control: affects -1 + src:xine

xine fails to cross build from source, because its ./configure fails to
find libxine.pc. During cross compilation, pkg-config does not search
/usr/lib/pkgconfig and only considers /usr/share/pkgconfig and
/usr/lib//pkgconfig. Since the former doesn't make sense
for libxine.pc, please move it to the latter directory.

The attached patch implements that in a minimal way, but passing a
multiarch --libdir to ./configure would solve this bug as well.

Helmut
diff --minimal -Nru xine-lib-1.2-1.2.6/debian/changelog 
xine-lib-1.2-1.2.6/debian/changelog
--- xine-lib-1.2-1.2.6/debian/changelog 2017-01-10 18:43:36.0 +0100
+++ xine-lib-1.2-1.2.6/debian/changelog 2017-09-17 15:51:41.0 +0200
@@ -1,3 +1,10 @@
+xine-lib-1.2 (1.2.6-1.4) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Move libxine.pc to a multiarch location. (Closes: #-1)
+
+ -- Helmut Grohne   Sun, 17 Sep 2017 15:51:41 +0200
+
 xine-lib-1.2 (1.2.6-1.3) unstable; urgency=medium
 
   * Non-maintainer upload.
diff --minimal -Nru xine-lib-1.2-1.2.6/debian/rules 
xine-lib-1.2-1.2.6/debian/rules
--- xine-lib-1.2-1.2.6/debian/rules 2017-01-10 18:32:42.0 +0100
+++ xine-lib-1.2-1.2.6/debian/rules 2017-09-17 15:51:41.0 +0200
@@ -12,9 +12,7 @@
 
 # These are used for cross-compiling and for saving the configure script
 # from having to guess our platform (since we know it already)
-DEB_HOST_GNU_TYPE  ?= $(shell dpkg-architecture -qDEB_HOST_GNU_TYPE)
-DEB_BUILD_GNU_TYPE ?= $(shell dpkg-architecture -qDEB_BUILD_GNU_TYPE)
-DEB_HOST_ARCH  ?= $(shell dpkg-architecture -qDEB_HOST_ARCH)
+include /usr/share/dpkg/architecture.mk
 
 ifneq ($(DEB_HOST_GNU_TYPE),$(DEB_BUILD_GNU_TYPE))
   $(error cross compiling is not supported by xine)
@@ -112,6 +110,10 @@
dh_testdir
dh_testroot
dh_install
+   set -e; if test "$(DH_PACKAGE)" = libxine2-dev; then \
+   mkdir debian/libxine2-dev/usr/lib/$(DEB_HOST_MULTIARCH); \
+   mv debian/libxine2-dev/usr/lib/pkgconfig 
debian/libxine2-dev/usr/lib/$(DEB_HOST_MULTIARCH)/pkgconfig; \
+   fi
test ! -f debian/overrides/$(DH_PACKAGE) || \
  install -Dm644 \
   debian/overrides/$(DH_PACKAGE) \

Bug#808379: please consider patch to customize E-Mail Subject

2017-09-17 Thread Marc Haber

On Mon, Aug 01, 2016 at 11:05:17AM +0200, Marc Haber wrote:
> On Sun, Jul 31, 2016 at 07:55:26PM +0200, Ola Lundqvist wrote:
> > I have looked at your contribution and it looks good. However for the last
> > update I have only considered corrections, not new functions (things that
> > have impact on config file).
> 
> I understand.
> 
> > I hope i´ll be able to look into a feture update soon.
> 
> I hope so as well ;-)

Hi, after another 13 months, may I remind?

Greetings
Marc

Bug#876027: RFS: libcgicc/3.2.19-0.2 [NMU] -- C++ class library for writing CGI applications

2017-09-17 Thread Thomas Pircher


Package: sponsorship-requests
Severity: normal

Dear mentors,

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

* Package name: libcgicc
  Version : 3.2.19-0.2
  Upstream Author : Sebastien Diaz 
* URL : http://www.gnu.org/software/cgicc/
* License : GPL-2+
  Section : libs

It builds those binary packages:

  libcgicc-dev - C++ class library for writing CGI applications 
(development files
  libcgicc-doc - C++ class library for writing CGI applications 
(documentation)

  libcgicc3  - C++ class library for writing CGI applications (library)

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

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


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


  dget -x 
https://mentors.debian.net/debian/pool/main/libc/libcgicc/libcgicc_3.2.19-0.2.dsc


More information about cgicc can be obtained from 
http://www.gnu.org/software/cgicc/.


Changes since the last upload:

  * Non-maintainer upload.
  * Updated to Standards-Version 4.1.0 (no changes required).
  * Move the old-style config file to the multi-arch directory under 
/usr/lib

(Closes: #874225).

I have deferred the package by 10 days to give the maintainer the 
opportunity to intervene, should he wish to do so.


Regards,
 Thomas Pircher

Bug#856467: davical: Fails to create principals for LDAP users with modifyTimestamp configured since 1.1.5

2017-09-17 Thread Philipp Marek

Source: davical
Version: 1.1.5-1
Followup-For: Bug #856467

Fixed upstream, please cut a new release in Debian.

Thank you!



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

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

--

Bug#876000: ocamlbuild: Package description has some invalid characters/encoding

2017-09-17 Thread Beatrice Torracca

Package: ocamlbuild
Severity: minor

Hi!

the package description of ocamlbuild currently has some (2?) strange
characters (encoding?) that probably are not correctly handled.

You can see the results here:
https://packages.debian.org/sid/ocamlbuild

Thanks,

beatrice

Bug#875744: Debian.asis.io mirror

2017-09-17 Thread Bastian Blank

Hi

On Sun, Sep 17, 2017 at 12:01:33PM +0430, factoreal wrote:
> Hey!The debian.asis.io is updated and up and 
> running. So please remove the issue. dir="auto">Thanks

>From what I see you mirror is not up-to-date, nor does it look right.
It never finished a complete run, so it shows informations of two
upstream mirrors:
- free.hands.com (ftp.uk.debian.org) and
- ftp.halifax.rwth-aachen.de

Please make sure you get the error mails from ftpsync (yes, this
software cries if something goes wrong) and check the logs.

Some more infos about the timeline can be found on the mirror info page:
https://mirror-master.debian.org/status/mirror-info/debian.asis.io.html

Also: Please get a name, we like to know who we are talking with.
Please don't send HTML only email.

Regards,
Bastian
Debian mirror team

-- 
Bones: "The man's DEAD, Jim!"

Bug#729956: Python 3 Statsmodels & Pandas

On 16.09.2017 22:59, Yuri D'Elia wrote:
> On Sat, Sep 16 2017, Diane Trout wrote:
>> python3-pandas: Pandas is not installable
>> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875723
> 
> I would have expected the rebuild of python packages affected by the
> fpectl extension with a transition, but it doesn't seem to be the case?

no, we don't want to rename the python2.7 package.

> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874253
> 
> More Breaks where added to {python,python3}-stdlib itself, but there are
> still packages which didn't rebuild.

fix them, they fail for unrelated reasons ;)

Bug#876008: autopkgtest: Wrong statement about Testsuite field in documentation


Package: autopkgtest
Version: 4.4
Severity: minor

Dear Maintainer,

In file doc/README.package-tests.rst, there is this sentence:

   To allow test execution environments to discover packages which
   provide tests, their source packages need to have a ``Testsuite:``
   header containing ``autopkgtest`` (which is currently the only
   defined value).

This was true in 2014, before the autodep8 pacakge started introducing 
the autopkgtest-pkg-* values.  The statement is innacurate today.


One of the reasons it is a good idea to reformulate the sentence is to 
avoid the confusion that it caused to the Lintian maintainers (see 
https://bugs.debian.org/876003).


Best,

Rafael Laboissière


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

Kernel: Linux 4.9.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.utf8 (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 autopkgtest depends on:
ii  apt-utils   1.5~beta2
ii  libdpkg-perl1.18.22
ii  procps  2:3.3.12-3
ii  python3 3.5.3-1
ii  python3-debian  0.1.30

Versions of packages autopkgtest recommends:
ii  autodep8  0.9

Versions of packages autopkgtest suggests:
pn  lxc  
pn  lxd-client   
pn  qemu-system  
ii  qemu-utils   1:2.8+dfsg-2
pn  schroot  

-- no debconf information

Bug#875617: pan: Crashes when launching

2017-09-17 Thread Dominique Dumont

On mardi 12 septembre 2017 17:24:36 CEST you wrote:
>  08:02 918537
> /lib/x86_64-linux-gnu/libgpg-error.so.0.21.0 Thread 4 "pool" received
> signal SIGABRT, Aborted.
> [Switching to Thread 0x7fffe3fff700 (LWP 24971)]

I can't reproduce this crash on my system. This bug looks like this upstream 
report:

https://bugzilla.gnome.org/show_bug.cgi?id=754921

Can you try the workaroung shown there ?

All the best
-- 
https://github.com/dod38fr/config-model/ -o- http://search.cpan.org/~ddumont/
http://ddumont.wordpress.com/-o-   irc: dod at irc.debian.org

Bug#876023: ITP: node-babel-plugin-transform-define -- replace member expressions and typeof statements with strings

2017-09-17 Thread Pirate Praveen

Package: wnpp
Severity: wishlist
Owner: Pirate Praveen 
X-Debbugs-CC: debian-de...@lists.debian.org

* Package name: node-babel-plugin-transform-define
  Version : 1.3.0
  Upstream Author : FIX_ME upstream author
* URL :
https://github.com/FormidableLabs/babel-plugin-transform-define
* License : Expat
  Programming Lang: JavaScript
  Description : replace member expressions and typeof statements
with strings
 Babel is a JavaScript compiler to use next generation JavaScript, today.
 .
 ES2015 and beyond: Babel has support for the latest version of JavaScript
 through syntax transformers. These plugins allow you to use new syntax,
right
 now without waiting for browser support.
 .
 Node.js is an event-based server-side JavaScript engine.



signature.asc
Description: OpenPGP digital signature

Bug#875985: lintian: Allow Testsuite: autopkgtest-pkg-octave

tags 875985 + pending
thanks

Fixed in Git:

  
https://anonscm.debian.org/git/lintian/lintian.git/commit/?id=53a4a87cba1c2418001e654c28cb64f36c55acdf


Regards,

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

Bug#875941: closed by Gianfranco Costamagna <locutusofb...@debian.org> (Re: virtualbox-guest-dkms module build fails)

2017-09-17 Thread Gianfranco Costamagna

>But that kernel came from neither testing nor unstable:
>$ apt-cache policy linux-image-4.9.0-3-amd64
>500 http://security.debian.org stretch/updates/main amd64
>Surely stable should have mutually compatible versions of kernel and at
>least virtualbox guest tools?


there is *no* vbox in stable.

rmadison -u debian virtualbox
virtualbox | 4.1.42-dfsg-1+deb7u1 | oldoldstable| 
source, amd64, i386
virtualbox | 4.3.18-dfsg-3| oldstable-kfreebsd/contrib  | 
source
virtualbox | 4.3.36-dfsg-1+deb8u1~bpo70+1 | wheezy-backports/contrib| 
source, amd64, i386
virtualbox | 4.3.36-dfsg-1+deb8u1 | oldstable/contrib   | 
source, amd64, i386
virtualbox | 5.1.8-dfsg-6~bpo8+2  | jessie-backports/contrib| 
source, amd64, i386
virtualbox | 5.1.26-dfsg-2~bpo9+1 | stretch-backports-debug/contrib | 
source
virtualbox | 5.1.26-dfsg-2~bpo9+1 | stretch-backports/contrib   | 
source, amd64, i386
virtualbox | 5.1.26-dfsg-2| testing/contrib | 
source, amd64, i386
virtualbox | 5.1.28-dfsg-1| unstable-debug/contrib  | 
source
virtualbox | 5.1.28-dfsg-1| unstable/contrib| 
source, amd64, i386


just use virtualbox in stable-backports (aka stretch-backports).

5.1.28 will go there in two/three days, as soon as it reaches Buster (aka 
testing).

G.

Bug#875985: lintian: Allow Testsuite: autopkgtest-pkg-octave

Hi Rafael,

> Notice that I have also addressed another issue in my bug report, 

Oh, I didn't see that...

> regarding the description of tag unknown-testsuite.  Should I file a 
> separate bug report for that?

Yes; please do.

... And please prefer to do this in future; not only is it more
explicit and less likely for someone to miss the issues, it allows
them to be fixed at different times with the proper tracking. :)


Regards,

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

Bug#876000: ocamlbuild: Package description has some invalid characters/encoding

2017-09-17 Thread Ralf Treinen

Hello,

On Sun, Sep 17, 2017 at 10:44:18AM +0200, Beatrice Torracca wrote:
> Package: ocamlbuild
> Severity: minor
> 
> Hi!
> 
> the package description of ocamlbuild currently has some (2?) strange
> characters (encoding?) that probably are not correctly handled.

thanks, fixed in git (but not uploaded due to an ongoing ocaml
transition).

-Ralf.

Bug#876002: ITP: node-gulp-babel -- gulp plugin to use babel

2017-09-17 Thread Pirate Praveen

Package: wnpp
Severity: wishlist
Owner: Pirate Praveen 
X-Debbugs-CC: debian-de...@lists.debian.org

* Package name: node-gulp-babel
  Version : 7.0.0
  Upstream Author : Sindre Sorhus 
(sindresorhus.com)
* URL : https://github.com/babel/gulp-babel#readme
* License : Expat
  Programming Lang: JavaScript
  Description : gulp plugin to use babel

 gulp is a toolkit that helps you automate painful or time-consuming
tasks in
 your development workflow.
 .
 Babel is a JavaScript compiler to use next generation JavaScript, today.
 .
 Node.js is an event-based server-side JavaScript engine.



signature.asc
Description: OpenPGP digital signature

Bug#874782: UFW build error: AssertionError: not thrown

2017-09-17 Thread jean-christophe manciot

In the meantime, I successfully built it in a sid chroot.
The first attempt was made iwithn another environment (Ubuntu 17.04).
You can close this report.

On Fri, Sep 15, 2017 at 8:45 PM, Jamie Strandboge 
wrote:

> On Sat, 2017-09-09 at 16:36 +0200, jean-christophe manciot wrote:
> > Package: ufw
> > Version: 0.35-5
> > sources: https://packages.debian.org/source/sid/ufw
> >
> > Building with:
> > dpkg-buildpackage --unsigned-source --unsigned-changes --build=binary
> > -m"Jean-Christophe Manciot "
> >
> > leads to:
> > ==
> > FAIL: test_get_netfilter_capabilities (tests.unit.test_util.
> UtilTestCase)
> > Test get_netfilter_capabilities()
> > --
> > Traceback (most recent call last):
> >   File "/home/actionmystique/src/UFW/ufw-0.35-5/tests/unit/test_
> util.py",
> > line 929, in test_get_netfilter_capabilities
> > ufw.util.get_netfilter_capabilities)
> >   File "/home/actionmystique/src/UFW/ufw-0.35-5/tests/unit/support.py",
> > line 159, in check_for_exception
> > t.fail('%s not thrown' % str(expectedException))
> > AssertionError:  not thrown
> >
> > --
> > Ran 45 tests in 0.346s
>
> I'm unable to reproduce this in an up to date sid chroot:
>
> test_get_netfilter_capabilities (tests.unit.test_util.UtilTestCase)
> Test get_netfilter_capabilities() ... ok
>
> Can you provide more details (eg, how you fetched the source, changes you
> made,
> exact command used to lead to the error, etc).
>
> Thanks!
>
> --
> Jamie Strandboge | http://www.canonical.com




-- 
Jean-Christophe

Bug#869098: python2.7 2.7.13-4 causes EOFError breakage in python-sphinx

2017-09-17 Thread Julian Andres Klode

Control: forwarded -1 https://github.com/sphinx-doc/sphinx/issues/4006

On Sun, Sep 17, 2017 at 10:48:27AM +0200, Matthias Klose wrote:
> Control: reassign -1 python-sphinx
> 
> On 14.09.2017 14:18, Julian Andres Klode wrote:
> > On Thu, Jul 20, 2017 at 03:40:52PM +0100, Neil Williams wrote:
> >> Package: python2.7
> >> Version: 2.7.13-4
> >> Severity: serious
> >> Justification: causes other packages to FTBFS
> >>
> >> With 2.7.13-4 installed, I am unable to build documentation as sphinx
> >> errors out:
> >>
> >> sphinx-build -b html -d _build/doctrees  -n -j 4 . _build/html
> >> Running Sphinx v1.4.9
> >> making output directory...
> >> loading pickled environment... not yet created
> >> loading intersphinx inventory from https://docs.python.org/2/objects.inv...
> >> building [mo]: targets for 0 po files that are out of date
> >> building [html]: targets for 91 source files that are out of date
> >> updating environment: 91 added, 0 changed, 0 removed
> >> reading sources... [100%] test-repositories .. writing-tests   
> >>
> >> waiting for workers...
> >>
> >> Exception occurred:
> >>   File "/usr/lib/python2.7/dist-packages/sphinx/util/parallel.py", line 
> >> 97, in _join_one
> >> exc, result = pipe.recv()
> >> EOFError
> > 
> > Given that this is a regression in 2.7.13-4, can we please revert
> > unstable to 2.7.13-3 again (as 2.7.14~rc1+really2.7.13-1 or something).
> 
> ... and now identified as an issue in sphinx. reassigning.

And here's the upstream commit fixing it, to provide some context:

https://github.com/sphinx-doc/sphinx/commit/2f8a342839bb36dd3622fb4ce3f874121b22c7ab

> 
> > Having an rc-buggy python in unstable that breaks reverse dependencies for 
> > two months
> > is not really acceptable
> 
> the only thing here which is not really acceptable is your behaviour of finger
> pointing.

I was merely suggesting that you do the same I'd do for my
packages - if there's an RC critical bug I can't find the
cause of for weeks, I'd move it to experimental, and
revert unstable to the last known good version. Especially
if it breaks building reverse deps.

One major annoyance for me personally was that this RC bug
interacted awfully with apt and apt-listbugs. apt-listbugs
pinned python2.7 to prevent the upgrade, and apt then wanted
to remove python2.7-dev and python2.7-dbg and friends every
single dist-upgrade. This is of course apt's stupidity. I
expect things get a bit better when we can pin by Source.

-- 
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#874782: UFW build error: AssertionError: not thrown

2017-09-17 Thread jean-christophe manciot

In the meantime, I successfully built it in a clean sid chroot.
The first attempt was made iwithn another environment (Ubuntu 17.04).
You can close this report.

On Sun, Sep 17, 2017 at 11:34 AM, jean-christophe manciot <
actionmysti...@gmail.com> wrote:

> In the meantime, I successfully built it in a sid chroot.
> The first attempt was made iwithn another environment (Ubuntu 17.04).
> You can close this report.
>
> On Fri, Sep 15, 2017 at 8:45 PM, Jamie Strandboge 
> wrote:
>
>> On Sat, 2017-09-09 at 16:36 +0200, jean-christophe manciot wrote:
>> > Package: ufw
>> > Version: 0.35-5
>> > sources: https://packages.debian.org/source/sid/ufw
>> >
>> > Building with:
>> > dpkg-buildpackage --unsigned-source --unsigned-changes --build=binary
>> > -m"Jean-Christophe Manciot "
>> >
>> > leads to:
>> > ==
>> > FAIL: test_get_netfilter_capabilities (tests.unit.test_util.UtilTest
>> Case)
>> > Test get_netfilter_capabilities()
>> > --
>> > Traceback (most recent call last):
>> >   File "/home/actionmystique/src/UFW/ufw-0.35-5/tests/unit/test_uti
>> l.py",
>> > line 929, in test_get_netfilter_capabilities
>> > ufw.util.get_netfilter_capabilities)
>> >   File "/home/actionmystique/src/UFW/ufw-0.35-5/tests/unit/support.py",
>> > line 159, in check_for_exception
>> > t.fail('%s not thrown' % str(expectedException))
>> > AssertionError:  not thrown
>> >
>> > --
>> > Ran 45 tests in 0.346s
>>
>> I'm unable to reproduce this in an up to date sid chroot:
>>
>> test_get_netfilter_capabilities (tests.unit.test_util.UtilTestCase)
>> Test get_netfilter_capabilities() ... ok
>>
>> Can you provide more details (eg, how you fetched the source, changes you
>> made,
>> exact command used to lead to the error, etc).
>>
>> Thanks!
>>
>> --
>> Jamie Strandboge | http://www.canonical.com
>
>
>
>
> --
> Jean-Christophe
>



-- 
Jean-Christophe

Bug#876009: shebang incorrectly set to /usr/bin/env python3

Package: libglib2.0-dev-bin
Version: 2.54.0-1
Severity: important
File: /usr/bin/glib-genmarshal

https://www.debian.org/doc/packaging-manuals/python-policy/ch-python.html#s-interpreter
states that the shebang of python scripts should not use /usr/bin/env,
yet we have /usr/bin/glib-genmarshal and /usr/bin/glib-mkenums which do
exactly that.

dh_python or dh_python3 are supposed to rewrite such a shebang which
apparently didn't happen in this case. I suppose this is due to
debian/rules overriding dh_python3 like this:

override_dh_python3:
dh_python3 -plibglib2.0-dev-bin /usr/share/glib-2.0/codegen

I.e. we do explicitly skip the scripts in /usr/bin


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

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

Versions of packages libglib2.0-dev-bin depends on:
ii  libc6 2.24-17
ii  libglib2.0-0  2.54.0-1
ii  python3   3.5.3-3

libglib2.0-dev-bin recommends no packages.

libglib2.0-dev-bin suggests no packages.

-- no debconf information

Bug#876010: lxde: LXDE session doesn't properly load - desktop is managed but no panel is loaded.

2017-09-17 Thread Jonathan Carter

Package: lxde
Version: lxde session doesn't properly load on live/installed media
Severity: important

Dear Maintainer,

While testing the latest Debian Live builds for alpha 1 pre-testing[1],
it was discovered that the LXDE session does not start properly. It displays
a non-debian wallpaper, and no LXDE panel. The desktop seems managed though
and the desktop menu displays when right-clicking on the desktop.

[1] 
http://cdimage.debian.org/images/.buster_di_alpha1/live-free/amd64/iso-hybrid/debian-live-buster-DI-a1-amd64-lxde.iso

Thanks,

 -Jonathan on behalf of the debian-live team

Bug#875617: pan: Crashes when launching

2017-09-17 Thread Sam Morris

On Sun, 2017-09-17 at 12:22 +0200, Dominique Dumont wrote:
> On mardi 12 septembre 2017 17:24:36 CEST you wrote:
> >  08:02 918537
> > /lib/x86_64-linux-gnu/libgpg-error.so.0.21.0 Thread 4 "pool"
> > received
> > signal SIGABRT, Aborted.
> > [Switching to Thread 0x7fffe3fff700 (LWP 24971)]
> 
> I can't reproduce this crash on my system. This bug looks like this
> upstream 
> report:
> 
> https://bugzilla.gnome.org/show_bug.cgi?id=754921
> 
> Can you try the workaroung shown there ?
> 
> All the best

Thanks for that idea. Unfortunately the groups files as suggested in
that bug didn't do anything. However... I have found that removing the
article-cache directory causes pan to launch successfully. On selecting
an article, however, it crashed again.

I noticed during a couple of iterations that the same filename, e6e618a
a-387f-d253-4bf4-e9ab27001...@gmail.com.msg, was always present in the
article-cache directory after a crash. This file was one of three
mentioned in tasks.nzb:

   /home/sam
   0

 gmane.linux.debian.devel.general
 gmane.linux.debian.devel.wnpp

e6e618aa-387f-d253-4bf4-e9ab27001...@gmail.com

At this point I blew away tasks.nzb and now the crash is gone. The bad
news is that viewing each article in the problematic thread no longer
caused the crash! However, if I restore the problematic tasks.nzb file
then the crash is back.

I've attached that file in case it's useful. I'm unable to reproduce
the crash from a fresh (non-existing) tasks.nzb file, even if I view
each of the articles that are listed in the attached file. 

-- 
Sam Morris 
PGP: rsa4096/CAAA AA1A CA69 A83A 892B  1855 D20B 4202 5CDA 27B9

tasks.nzb
Description: application/nzb

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

Bug#876013: golang-google-genproto-dev has circular Depends on golang-google-grpc-dev

Package: golang-google-genproto-dev
Version: 0.0~git20170731.0.09f6ed2-1
Severity: important

Hello Debian Go Packaging Team,

There is a circular dependency between golang-google-genproto-dev
and golang-google-grpc-dev:

golang-google-genproto-dev  :Depends: golang-google-grpc-dev
golang-google-grpc-dev  :Depends: golang-google-genproto-dev

Circular dependencies are known to cause problems during upgrade between
stable releases, so we should try to avoid them.

Cheers,
-- 
Bill. 

Imagine a large red swirl here.

Bug#876017: openbox has circular Depends on openbox-menu

Package: openbox
Version: 3.6.1-5
Severity: important

Hello Mateusz,

There is a circular dependency between openbox and openbox-menu:

openbox :Depends: openbox-menu
openbox-menu:Depends: openbox

Circular dependencies involving shared libraries are known to cause problems
during upgrade between stable releases, so we should try to get rid of them.

See threads 
http://lists.debian.org/debian-devel/2005/06/msg02111.html
http://lists.debian.org/debian-devel/2005/11/msg01101.html

Cheers,
-- 
Bill. 

Imagine a large red swirl here.

Bug#875860: please enable crossbuild-essential for all release architectures

Control: tags -1 - patch

On 15.09.2017 12:04, Helmut Grohne wrote:
> Source: build-essential
> Version: 12.3
> Severity: wishlist
> Tags: patch
> User: helm...@debian.org
> Usertags: rebootstrap
> 
> Hi Matthias,
> 
> I am using crossbuild-essential-$arch for performing cross build tests
> and we want to push such testing to official infrastructure to integrate
> it with tracker.d.o.
> 
> In doing so I am using all present crossbuild-essential-$arch packages
> and keep finding architecture-specific bugs (e.g. toolchain bugs) that
> would only be found by performing an archive rebuild for those other
> architectures. However my testing is currently limited to arm64, armel,
> armhf, mipsel, powerpc, and ppc64el, because the other architectures are
> missing in cross-targets. Please consider adding them. The attached
> patch implements that.

you can't add packages with unmet dependencies. Therefore dropping amd64 and
i386 again.

I see I already added these missing archs in January, but didn't upload due to
the freeze. Now uploaded.

> In principle, I can test any non-ports architecture in unstable. Adding
> hurd-i386, kfreebsd-amd64 and kfreebsd-i386 may make sense eventually,
> but such testing won't go far before #798955 is fixed, so I am not
> adding them in my patch.

and yes, these would block migration to testing as well.

Bug#876003: lintian: Wrong description of tag unknown-testsuite

tags 876003 + pending
thanks

Hi Rafael,

> At any rate, your explanation is incoherent with the current behavior of 
> Lintian (v 2.5.52).  With the current version of the octave-image 
> package, the following warning 

It might be "incoherent" but the goal here is surely to either fix the
description, fix Lintian, or merely to fix our understanding to a point
where they all agree!

ie. What Lintian currently does is — from that point of view — somewhat
of a side-issue and doesn't really add anything useful IMHO.

> >  To allow test execution environments to discover packages which provide
> >  tests, their source packages need to have a ``Testsuite:`` header
> >  containing ``autopkgtest`` (which is currently the only defined value).
> 
> Please, note the word "currently" in the sentence above.

Mmm, but then it immediately goes on to mention "autopkgtest-pkg-perl"
so it felt like they were orthogonal.

Anyway, thanks for the clarification and I've fixed this in Git here:

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


Regards,

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

Bug#876025: "ip address show up" displays DOWN interfaces

2017-09-17 Thread François Lafont

Package: iproute2
Version: 4.9.0-1
Severity: minor

Hi,

Here is an example on my (updated) Debian Stretch where eth1
and wlan0 have the state DOWN but they are still displayed
by the "ip" command:

~$ /bin/ip address show up
1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
   valid_lft forever preferred_lft forever
inet6 ::1/128 scope host 
   valid_lft forever preferred_lft forever
2: eth0:  mtu 1500 qdisc pfifo_fast state UP 
group default qlen 1000
link/ether 20:cf:30:52:6a:56 brd ff:ff:ff:ff:ff:ff
inet 192.168.0.1/24 brd 192.168.0.255 scope global dynamic eth0
   valid_lft 79732sec preferred_lft 79732sec
inet6 fe80::22cf:30ff:fe52:6a56/64 scope link 
   valid_lft forever preferred_lft forever
3: eth1:  mtu 1500 qdisc pfifo_fast state 
DOWN group default qlen 1000
link/ether 00:14:d1:2f:6c:ac brd ff:ff:ff:ff:ff:ff
4: wlan0:  mtu 1500 qdisc mq state DOWN 
group default qlen 1000
link/ether 7a:ba:f9:69:f7:65 brd ff:ff:ff:ff:ff:ff

Regards.


-- System Information:
Debian Release: 9.1
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (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.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages iproute2 depends on:
ii  libc62.24-11+deb9u1
ii  libdb5.3 5.3.28-12+b1
ii  libelf1  0.168-1
ii  libmnl0  1.0.4-2
ii  libselinux1  2.6-3+b1

Versions of packages iproute2 recommends:
pn  libatm1   
ii  libxtables12  1.6.0+snapshot20161117-6

Versions of packages iproute2 suggests:
pn  iproute2-doc  

-- no debconf information

Bug#873857: 'Screenshot' option of Graphical installer not accessible through keyboard

2017-09-17 Thread Holger Wansing

Hi,

Kaartic Sivaraam  wrote:
> Hello all,
> 
> I recently tried to install Debian 9 using the graphical installer. Due
> to some unknown reason my mouse did not work in the graphical
> installer. It wasn't a big deal as I could manage well just with my
> keyboard BUT I was unable to capture a screen shot of an error as the
> option for taking screen shot wasn't accessible through the keyboard
> like the 'Continue' and 'Back' options. It would be nice to make it
> accessible through the keyboard as it would be helpful in situations
> like this.

Thanks for your mail.
This has already been reported in 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873857

And it turns out that this bug already exists from the very beginning in 
Debian 4.0, where the graphical installer was introduced ...

Holger

-- 

Created with Sylpheed 3.5.1 under the   n e w
D E B I A N   L I N U X   9   " S T R E T C H " .

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

Bug#821088: reassign #821088 to live-wrapper?

2017-09-17 Thread Iain R. Learmonth

Hi,

On 17/09/17 15:50, Steve McIntyre wrote:
> I'm not sure yet. There's a series of these bugs open against various
> Debian packages, basically as place-holders for now. vmdebootstrap is
> the bit that installs kernelss, but live-wrapper is in charge of
> it. They might both need changes yet, tbh...

The bug was cloned, or otherwise filed independently, on live-wrapper.
Changes will likely be required in both.

Thanks,
Iain.

Bug#876027: RFS: libcgicc/3.2.19-0.2 [NMU] -- C++ class library for writing CGI applications

2017-09-17 Thread Gianfranco Costamagna

control: owner -1 !
control: tags -1 moreinfo

>* Package name: libcgicc

hello, I find this approach a little bit too invasive

-cxxflags="-Wall -W -pedantic -g -O2 
-fdebug-prefix-map=/build/libcgicc-GEfIf8/libcgicc-3.2.19=. 
-fstack-protector-strong -Wformat -Werror=format-security"
+cxxflags="-Wall -W -pedantic -g -O2 
-fdebug-prefix-map=/build/libcgicc-pUjh6F/libcgicc-3.2.19=. 
-fstack-protector-strong -Wformat -Werror=format-security"


changes are just about that debug-prefix-map variable.. couldn't we just get 
rid of it and leave the file in that directory?

Moving the file outside $PATH is useless for its purpose.

maybe some sed magic can do the trick?


-fdebug-prefix-map=old=new
When compiling files in directory old, record debugging information describing 
them as in new instead.

so, probably not needed at runtime :)

G.

Bug#874521: fwupd segfaults at start

2017-09-17 Thread Laurent Bigonville

forwarded 874521 https://github.com/hughsie/fwupd/issues/259
thanks

On Fri, 8 Sep 2017 15:54:42 +  wrote:
> So I can't reproduce this. More details will be needed. If you can 
please file a bug upstream (https://github.com/hughsie/fwupd/) it would 
be best for upstream to work on solving this.

>
> The following items are needed:
>
>
> 1. /usr/lib/fwupd/fwupd -v output

See attachment

> 2. Information about the hardware you're running on (OEM, model)?

Custom build

> 3. Is this a notebook? Are you docked? What dock?

It's a desktop

> 4. Any USB devices that you have plugged in. Especially interesting 
is if you have a USB Logitech unifying dongle plugged in.
> 5. If you have a Logitech unifying dongle plugged in can you 
reproduce this without it plugged in?

I'm using an USB Logitech unifying dongle. Unpluging in fixes the crash.

Also I'm pretty sure this was not happening in 0.8.2 from unstable, and 
that's why I set the bug RC
06:56:47:0505 Fu  Verbose debugging enabled (on console 0)
06:56:47:0505 Fu  loading config values from /etc/fwupd.conf
06:56:47:0507 Fu  using config path of /etc/fwupd
06:56:47:0507 Fu  loading from /etc/fwupd/remotes.d/fwupd.conf
06:56:47:0507 Fu  loading from /etc/fwupd/remotes.d/lvfs.conf
06:56:47:0507 Fu  loading from /etc/fwupd/remotes.d/vendor.conf
06:56:47:0507 Fu  loading from /etc/fwupd/remotes.d/lvfs-testing.conf
06:56:47:0507 Fu  using config path of /usr/lib/fwupd
06:56:47:0507 Fu  ordering lvfs=fwupd+1
06:56:47:0507 Fu  ordering lvfs-testing=lvfs+1
06:56:47:0507 Fu  remote lvfs-testing not enabled, so skipping
06:56:47:0508 Fu  no /var/lib/fwupd/remotes.d/lvfs/metadata.xml.gz, so skipping
06:56:47:0508 As  run 
AsStore:store-from-file{/usr/share/fwupd/remotes.d/fwupd/metadata.xml}
06:56:47:0508 As  run AsStore:store-from-root
06:56:47:0508 As  using icon path /usr/share/fwupd/remotes.d/fwupd/icons
06:56:47:0508 As  run AsStore:match-addons
06:56:47:0508 As  Emitting ::changed() [from-root]
06:56:47:0508 As  Emitting ::changed() [add-app]
06:56:47:0508 As  Emitting ::changed() [add-app]
06:56:47:0508 Fu  remote vendor not enabled, so skipping
06:56:47:0508 Fu  devices now in store:
06:56:47:0508 Fu  1 UEFI-dummy-dev0 UEFI Updates
06:56:47:0508 Fu  2 com.via.VL811.firmware  VL811 Firmware
06:56:47:0508 Fu  3 com.via.VL811+.firmware VL811+ Firmware
06:56:47:0508 Fu  4 com.via.VL812.firmware  VL812 Firmware
06:56:47:0508 Fu  5 com.via.VL812_B2.firmware   VL812 B2 Firmware
06:56:47:0516 Fu  smbios property /sys/class/dmi/id/sys_vendor=System 
manufacturer
06:56:47:0516 Fu  smbios property /sys/class/dmi/id/chassis_type=3
06:56:47:0516 Fu  smbios property /sys/class/dmi/id/product_family=To Be Filled 
By O.E.M.
06:56:47:0516 Fu  smbios property /sys/class/dmi/id/product_name=System Product 
Name
06:56:47:0516 Fu  no /sys/class/dmi/id/product_sku so ignoring
06:56:47:0516 Fu  smbios property /sys/class/dmi/id/bios_vendor=American 
Megatrends Inc.
06:56:47:0516 Fu  smbios property /sys/class/dmi/id/bios_version=0406   
06:56:47:0516 Fu  no /sys/class/dmi/id/bios_major_release so ignoring
06:56:47:0516 Fu  no /sys/class/dmi/id/bios_minor_release so ignoring
06:56:47:0516 Fu  smbios property /sys/class/dmi/id/board_vendor=ASUSTeK 
Computer INC.
06:56:47:0516 Fu  smbios property /sys/class/dmi/id/board_name=P6T DELUXE V2
06:56:47:0517 Fu  HardwareID-0 is not available, not available as 'ProductSku' 
unknown
06:56:47:0517 Fu  HardwareID-1 is not available, not available as 
'BiosMajorRelease' unknown
06:56:47:0517 Fu  HardwareID-2 is not available, not available as 
'BiosMajorRelease' unknown
06:56:47:0517 Fu  HardwareID-3 is not available, not available as 'ProductSku' 
unknown
06:56:47:0517 Fu  HardwareID-4 is not available, not available as 'ProductSku' 
unknown
06:56:47:0517 Fu  {9e62b197-7959-5a62-aa3f-f0df9ccd9101}   <- System 
manufacturer Be Filled By O.E.M. Product Name
06:56:47:0517 Fu  HardwareID-6 is not available, not available as 'ProductSku' 
unknown
06:56:47:0517 Fu  HardwareID-7 is not available, not available as 'ProductSku' 
unknown
06:56:47:0517 Fu  {1a8e9d8e-d496-5da0-b07c-ca4a6e27d88a}   <- System 
manufacturer Product Name Computer INC. DELUXE V2
06:56:47:0517 Fu  {0dcce594-e561-59aa-9e30-21077acb429c}   <- System 
manufacturer Product Name
06:56:47:0517 Fu  {12c41cc8-982b-52fb-aa7d-9d30a397f955}   <- System 
manufacturer Be Filled By O.E.M. Computer INC. DELUXE V2
06:56:47:0517 Fu  {3f215d45-e15d-5d3d-b0d2-6be10b435a44}   <- System 
manufacturer Be Filled By O.E.M.
06:56:47:0517 Fu  {a7aaa273-f280-513a-b907-919359a44175}   <- System 
manufacturer&3
06:56:47:0517 Fu  {c0137d84-afb1-539d-8d55-a795376c13ef}   <- System 
manufacturer Computer INC. DELUXE V2
06:56:47:0517 Fu  {035a20a6-fccf-5040-bc3e-b8b794c57f52}   <- System 
manufacturer
06:56:47:0517 Fu  adding plugin 
/usr/lib/x86_64-linux-gnu/fwupd-plugins-2/libfu_plugin_amt.so
06:56:47:0517 Fu  adding plugin

Bug#874693: Is this still an issue?

Am 17.09.2017 um 01:40 schrieb Dean Loros:
> I see that gjs 1.50  has been released. Is this bug still applicable?

Yes. Why do you think it should not be?


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



signature.asc
Description: OpenPGP digital signature

Bug#875992: haskell-lens: unsatisfiable B-D: libghc-vector-dev (< 0.12) but 0.12.0.1-1 is to be installed

2017-09-17 Thread peter green



There appears to be a new version in git that updates the package and fixes 
this build-dependency issue.

I presume the reason it hasn't been uploaded yet is 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875396

Bug#876027: RFS: libcgicc/3.2.19-0.2 [NMU] -- C++ class library for writing CGI applications

2017-09-17 Thread Andrey Rahmatullin

On Sun, Sep 17, 2017 at 02:59:48PM +, Gianfranco Costamagna wrote:
> hello, I find this approach a little bit too invasive
> 
> -cxxflags="-Wall -W -pedantic -g -O2 
> -fdebug-prefix-map=/build/libcgicc-GEfIf8/libcgicc-3.2.19=. 
> -fstack-protector-strong -Wformat -Werror=format-security"
> +cxxflags="-Wall -W -pedantic -g -O2 
> -fdebug-prefix-map=/build/libcgicc-pUjh6F/libcgicc-3.2.19=. 
> -fstack-protector-strong -Wformat -Werror=format-security"
> 
> 
> changes are just about that debug-prefix-map variable.. 
What's that? Have you diffed the build logs instread of the source
packages?

-- 
WBR, wRAR


signature.asc
Description: PGP signature

Bug#420890: Tree for packaging tutorial

Hi,

This is FYI:

There is a new debmake-doc package and its web page which should replace
maint-guide.  It uses tree command.

https://www.debian.org/doc/devel-manuals#debmake-doc
https://packages.qa.debian.org/d/debmake-doc.html

Osamu

Bug#847389: bash: /etc/skel/.bashrc should contain line "export GPG_TTY=$(tty)"

2017-09-17 Thread Teemu Likonen

Daniel Kahn Gillmor [2017-09-06 13:43:14-04] wrote:

> On Wed 2016-12-07 19:59:07 +0200, Teemu Likonen wrote:
>> GnuPG agent's (package: gpg-agent) man/info page says that
>>
>> You should always add the following lines to your .bashrc or
>> whatever initialization file is used for all shell invocations:
>>
>>  GPG_TTY=$(tty)
>>  export GPG_TTY

> I'm not convinced this is a good idea, though i confess i've always
> been a bit confused about bash's initialization process, with the
> distinctions between interactive shells, login shells, etc.

> Users who need this setting are generally special cases, and can
> figure out how to put it in themselves if they need it (and they might
> not need it at all anyway).

Maybe you are right. I just based my suggestion on the gpg-agent manual
which says "You should always add the following lines to your .bashrc
[...]". The manual is then misleading and should be rewritten to be more
specific about the issue.

I don't know whether I need GPG_TTY or not. I read the manual but I
doesn't give any answers to "why".

signature.asc
Description: PGP signature

Bug#721138: New packaging tutorial

Hi,

This is FYI:

There is a new debmake-doc package and its web page which should replace
maint-guide.  It is now getting mature.

https://www.debian.org/doc/devel-manuals#debmake-doc
https://packages.qa.debian.org/d/debmake-doc.html

Osamu

Bug#873596: avahi FTCBFS: uninstallable python Build-Depends, fails to figure out what distribution Debian is

Hi Helmut

On Tue, 29 Aug 2017 13:41:43 +0200 Helmut Grohne  wrote:
> Source: avahi
> Version: 0.6.32-2
> Tags: patch
> User: helm...@debian.org
> Usertags: rebootstrap
> 
> avahi fails to cross build from source. Since xmltoman became
> M-A:foreign. avahi's Build-Depends are almost installable. Its python
> dependencies still fail with postinst errors. For cross building, one
> typically wants libpython from the host architecture and the rest from
> the build architecture.

Given that python-all-dev already depends on libpython-all-dev,
shouldn't python-all-dev ensure to pull in the correct version?


After annotating all of those dependencies,
> ./configure fails figuring out the target distribution. After telling it
> that we build for Debian, it cross builds successfully. 

Hm, that would make the package not syncable to Ubuntu and other
derivatives.
I wonder if it would be better to conditionalize on dpkg-vendor
(DEB_VENDOR, /usr/share/dpkg/vendor.mk) instead.

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



signature.asc
Description: OpenPGP digital signature

Bug#876037: [Pkg-utopia-maintainers] Bug#876037: Bug#874585: dpkg-shlibdeps: does not parse Version References