Bug#858373: help needed to complete regression fix for apache2 Bug#858373

2017-07-21 Thread Stefan Fritsch
Hi Antoine,

On Wednesday, 19 July 2017 15:45:20 CEST Antoine Beaupre wrote:
> As I mentioned in the #858373 bug report, I started looking at fixing
> the regression introduced by the 2.2.22-13+deb7u8 upload, part of
> DLA-841-1. The problem occurs when a CGI(d) ErrorDocument is configured
> to handle 400 error messages that can be triggered with a simple "GET /
> HTTP/1.0\n\n". Such a request segfaults Apache in Wheezy right now.

> Unfortunately, re-introducing the protocol initialization code isn't
> sufficient: it does fix the segfaults, but the ErrorDocument handling is
> not quite working yet. Instead of seeing the output of the
> ErrorDocument, after 10 seconds, I get the raw 400 message, doubled with
> a 500 error document warning:

> Note that I have also tried to see if sending "\r\n" instead of just
> "\n" in my "hello world" example would work around the issue: it
> doesn't, unfortunately.
> 
> I am at a loss as where to go from here, to be honest. The patch
> (attached) at least fixes the segfault, which resolves the primary issue
> at hand here (DoS by crashing processes!) but it would be nice to
> actually fix the ErrorDocument as well..

This sounds familiar. Maybe it's simply broken in 2.2.22. Can you compare with 
2.2.22-13+deb7u7 if that bug has been there already?

In 2.2.30, there is this fix, which is obviously missing from 2.2.22:

  *) core, modules: Avoid error response/document handling by the core if some
 handler or input filter already did it while reading the request (causing
 a double response body).  [Yann Ylavic]

I could not find a changelog entry about the 10s delay, but it's possible that 
that has been fixed as well. If the issue is not a regression, you should 
simply release the patch that you have. The fix for the error document seems 
rather invasive:

https://svn.apache.org/r1683808

Cheers,
Stefan



Bug#868840: krb5-config.heimdal --libs defines -rpath

2017-07-21 Thread Brian May
Ryan Tandy  writes:

> Only the dev symlinks (.so) are in .../heimdal. So it seems like it 
> would be enough for consumers to build with -L and pick up the libraries 
> from the standard path at runtime, right?

IIRC, this strangeness is required so that it is possible to install
heimdal-multidev and krb5-multidev at the same time, and have
/usr/bin/krb5-config.heimdal guaranteed to find the correct Heimdal
libraries. e.g. for build depends when you want to build two versions
for the two Kerberos implementations.

That explains the -L parameter.

I can't think of any reason why we need rpath set however. Which doesn't
mean reasons don't exist...

Patches to fix this welcome!
-- 
Brian May 



Bug#868842: please respect DEB_BUILD_OPTIONS=nocheck

2017-07-21 Thread Brian May
Ryan Tandy  writes:

> Simply removing override_dh_auto_test should be enough. 01ee541a31 looks 
> like an unnecessary change to me; AFAICT, debhelper has always supported 
> 'make check'.

With this change, the tests fail. Still trying to understand why.
-- 
Brian May 



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

2017-07-21 Thread Neil Williams
On Thu, 20 Jul 2017 22:12:31 +0200
Matthias Klose  wrote:

> On 20.07.2017 16:40, 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
> > The full traceback has been saved in /tmp/sphinx-err-o8zX9U.log, if
> > you want to report the issue to the developers. Please also report
> > this if it was a user error, so that a better error message can be
> > provided next time. A bug report can be filed in the tracker at
> > . Thanks! ^CError in
> > atexit._run_exitfuncs:
> > 
> > The problem now is that lava-server and potentially other packages
> > which build documentation with python-sphinx will FTBFS with this
> > version of python2.7 in unstable.
> > 
> > Downgrading python-sphinx to the version in Stretch makes no
> > difference.
> > 
> > Downgrading python2.7 to the version in testing fixes the problem
> > entirely.
> > 
> > $ sudo apt install python2.7=2.7.13-2 python2.7-minimal=2.7.13-2
> > libpython2.7-stdlib=2.7.13-2 libpython2.7-minimal=2.7.13-2
> > 
> > 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...
> > looking for now-outdated files... none found
> > pickling environment... done
> > checking consistency... done
> > preparing documents... done
> > writing output... [100%] user-notifications ..
> > writing-tests waiting for workers...
> > generating indices... genindex
> > writing additional pages... search
> > copying images... [100%]
> > images/micro-instance-lab.svg copying static files... done
> > copying extra files... done
> > dumping search index in English (code: en) ... done
> > dumping object inventory... done
> > build succeeded.
> > 
> > Build finished. The HTML pages are in _build/html.
> > 
> > To reproduce, it should be enough to install lava-dev to get the
> > correct build dependencies, and try to rebuild lava-server. A
> > quicker test would be to get the lava-server source and run:
> > 
> > $ make -C doc/v2 clean
> > $ make -C doc/v2 html
> > 
> > in the top level directory.
> > 
> > One of the sphinx error logs:
> > 
> > # Sphinx version: 1.5.6
> > # Python version: 2.7.13+ (CPython)
> > # Docutils version: 0.13.1 release
> > # Jinja2 version: 2.9.6
> > # Last messages:
> > #   91 added, 0 changed, 0 removed
> > #   reading sources... [ 14%] actions-boot .. data-export
> > #   reading sources... [ 28%] debian .. explain_first_job
> > #   reading sources... [ 42%] first-devices .. ipxe
> > #   reading sources... [ 57%] lava-dashboard-image-reports ..
> > migrate-lava #   reading sources... [ 71%]
> > migrating-admin-example .. pipeline-writer #   reading sources...
> > [ 85%] pipeline-writer-secondary .. tables #   reading sources...
> > [100%] test-repositories .. writing-tests #   
> > #   waiting for workers...
> > # Loaded extensions:
> > #   sphinx.ext.coverage (1.5.6)
> > from /usr/lib/python2.7/dist-packages/sphinx/ext/coverage.pyc #
> > sphinx.ext.viewcode (1.5.6)
> > from /usr/lib/python2.7/dist-packages/sphinx/ext/viewcode.pyc #
> > sphinx.ext.todo (1.5.6)
> > from /usr/lib/python2.7/dist-packages/sphinx/ext/todo.pyc #
> > sphinx.ext.autodoc (1.5.6)
> > from /usr/lib/python2.7/dist-packages/sphinx/ext/autodoc.pyc #
> > sphinx.ext.intersphinx (1.5.6)
> > from /usr/lib/python2.7/dist-packages/sphinx/ext/intersphinx.pyc
> > #   sphinx.ext.doctest (1.5.6)
> > from /usr/lib/python2.7/dist-packages/sphinx/ext/doctest.pyc #
> > alabaster (0.7.8)
> > from /usr/lib/python2.7/dist-packages/alabaster/__init__.pyc
> > Traceback (most recent call last): File
> > "/usr/lib/python2.7/dist-packages/sphinx/cmdline.py", line 296, in
> > main app.build(opts.force_all, filenames) File
> > "/usr/lib/pyt

Bug#576998: [Pkg-javascript-devel] why not

2017-07-21 Thread Petter Reinholdtsen
Hi.

Any progress on getting Etherpad into Debian?  I would love to add
support for Etherpad to FreedomBox, but for that to happen there
need to be maintainable packages in Debian.

Yesteday, the Software Freedom Conservancy announced that Etherpad
join the Conservancy as a member, see
https://sfconservancy.org/news/2017/jul/20/etherpad/ >.  Perhaps
that might motivate more people to get Etherpad into Debian?
-- 
Happy hacking
Petter Reinholdtsen



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

2017-07-21 Thread Neil Williams
On Thu, 20 Jul 2017 22:23:31 +0200
Matthias Klose  wrote:

> On 20.07.2017 16:40, 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:  
> 
> please could you check if it builds with the debug interpreter?
> 

$ make SPHINXBUILD="python -m pdb 
/usr/share/sphinx/scripts/python2/sphinx-build" -C doc/v2 html
make: Entering directory '/home/neil/code/lava/lava-server/doc/v2'
python -m pdb /usr/share/sphinx/scripts/python2/sphinx-build -b html -d 
_build/doctrees  -n -j 4 . _build/html
> /usr/share/sphinx/scripts/python2/sphinx-build(9)()
-> """
(Pdb) run
Restarting /usr/share/sphinx/scripts/python2/sphinx-build with arguments:
-b html -d _build/doctrees -n -j 4 . _build/html
> /usr/share/sphinx/scripts/python2/sphinx-build(9)()
-> """
(Pdb) continue
Running Sphinx v1.5.6
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 98, in 
_join_one
exc, result = pipe.recv()
EOFError
The full traceback has been saved in /tmp/sphinx-err-hrke62.log, if you want to 
report the issue to the developers.
Please also report this if it was a user error, so that a better error message 
can be provided next time.
A bug report can be filed in the tracker at 
. Thanks!
The program exited via sys.exit(). Exit status:  1
> /usr/share/sphinx/scripts/python2/sphinx-build(9)()
-> """
(Pdb) w
  /usr/lib/python2.7/bdb.py(400)run()
-> exec cmd in globals, locals
  (1)()
> /usr/share/sphinx/scripts/python2/sphinx-build(9)()
-> """
(Pdb) p
*** SyntaxError: SyntaxError('unexpected EOF while parsing', ('', 0, 0, 
''))
(Pdb) where
  /usr/lib/python2.7/bdb.py(400)run()
-> exec cmd in globals, locals
  (1)()
> /usr/share/sphinx/scripts/python2/sphinx-build(9)()
-> """
(Pdb) u
> (1)()
(Pdb) u
> /usr/lib/python2.7/bdb.py(400)run()
-> exec cmd in globals, locals
(Pdb) u
*** Oldest frame
(Pdb) d
> (1)()
(Pdb) d
> /usr/share/sphinx/scripts/python2/sphinx-build(9)()
-> """
(Pdb) d
*** Newest frame
(Pdb) 

So, no, it doesn't build with -m pdb and the output from the debugger
is even less helpful than from sphinx.


$ cat /tmp/sphinx-err-hrke62.log
# Sphinx version: 1.5.6
# Python version: 2.7.13+ (CPython)
# Docutils version: 0.13.1 release
# Jinja2 version: 2.9.6
# Last messages:
#   91 added, 0 changed, 0 removed
#   reading sources... [ 14%] actions-boot .. data-export
#   reading sources... [ 28%] debian .. explain_first_job
#   reading sources... [ 42%] first-devices .. ipxe
#   reading sources... [ 57%] lava-dashboard-image-reports .. migrate-lava
#   reading sources... [ 71%] migrating-admin-example .. pipeline-writer
#   reading sources... [ 85%] pipeline-writer-secondary .. tables
#   reading sources... [100%] test-repositories .. writing-tests
#   
#   waiting for workers...
# Loaded extensions:
#   sphinx.ext.coverage (1.5.6) from 
/usr/lib/python2.7/dist-packages/sphinx/ext/coverage.pyc
#   sphinx.ext.viewcode (1.5.6) from 
/usr/lib/python2.7/dist-packages/sphinx/ext/viewcode.pyc
#   sphinx.ext.todo (1.5.6) from 
/usr/lib/python2.7/dist-packages/sphinx/ext/todo.pyc
#   sphinx.ext.autodoc (1.5.6) from 
/usr/lib/python2.7/dist-packages/sphinx/ext/autodoc.pyc
#   sphinx.ext.intersphinx (1.5.6) from 
/usr/lib/python2.7/dist-packages/sphinx/ext/intersphinx.pyc
#   sphinx.ext.doctest (1.5.6) from 
/usr/lib/python2.7/dist-packages/sphinx/ext/doctest.pyc
#   alabaster (0.7.8) from 
/usr/lib/python2.7/dist-packages/alabaster/__init__.pyc
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/sphinx/cmdline.py", line 296, in main
app.build(opts.force_all, filenames)
  File "/usr/lib/python2.7/dist-packages/sphinx/application.py", line 333, in 
build
self.builder.build_update()
  File "/usr/lib/python2.7/dist-packages/sphinx/builders/__init__.py", line 
251, in build_update
'out of date' % len(to_build))
  File "/usr/lib/python2.7/dist-packages/sphinx/builders/__init__.py", line 
265, in build
self.doctreedir, self.app))
  File "/usr/lib/python2.7/dist-packages/sphinx/environment/__init__.py", line 
554, in update
self._read_parallel(docnames, app, nproc=app.parallel)
  File "/usr/lib/python2.7/dist-packages/sphinx/environment/__init__.py", line 
612, in _read_parallel
tasks.join()
  File "/usr/lib/python2.7/dist-packages/sphinx/util/parallel.py", line 93, in 
join
self._

Bug#853513: libvigraimpex: ftbfs with GCC-7

2017-07-21 Thread Daniel Stender
There's currently another build break happening:


{standard input}: Assembler messages:
{standard input}:512533: Warning: end of file not at end of a line; newline 
inserted
{standard input}: Error: open CFI at the end of file; missing .cfi_endproc 
directive
c++: internal compiler error: Killed (program cc1plus)
Please submit a full bug report,
with preprocessed source if appropriate.
See  for instructions.
vigranumpy/src/core/CMakeFiles/vigranumpy_analysis.dir/build.make:185: recipe 
for target 
'vigranumpy/src/core/CMakeFiles/vigranumpy_analysis.dir/accumulator-region-multiband.cxx.o'
 failed
make[4]: *** 
[vigranumpy/src/core/CMakeFiles/vigranumpy_analysis.dir/accumulator-region-multiband.cxx.o]
 Error 4
make[4]: Leaving directory 
'/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg/obj.python2.7'
CMakeFiles/Makefile2:3800: recipe for target 
'vigranumpy/src/core/CMakeFiles/vigranumpy_analysis.dir/all' failed


This might be realed to this issue. I'll get into it shortly.

Thanks,
DS

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



Bug#868843: xorg-server: please make the BUILD_{DATE,TIME} reproducible

2017-07-21 Thread Chris Lamb
forwarded 868843 https://lists.x.org/pipermail/xorg-devel/2017-July/054127.html
thanks

Updating URL.


Regards,

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



Bug#868638: heimdal-kdc: m-key installed by postinst apparently not used

2017-07-21 Thread Brian May
CCed the security team.

Security-team: Do you think this is a security issue?

I can't remember the point of encrypting the database with the key in
the same directory right now. Maybe it protects against certain types of
mistakes, not sure.

Regards.


Ryan Tandy  writes:

> On Tue, Jul 18, 2017 at 05:35:07PM +1000, Brian May wrote:
>>Does the attached patch look good to you?
>
> Yes, that's exactly what I had in mind. Tested here and looks fine.
>
> Changelog typo: "explicity". Guessing you already spotted it.
>
> The path would also need updating in the heimdal-kdc/password debconf 
> template.
>
>>Do you consider this a security issue? Do we need to investigate fixes
>>for Wheezy, Jessie, and Stretch (depending on when this bug was first
>>introduced)?
>
> I would guess it's worth getting the security team's opinion on.
>
> Problem is, fixing the postinst doesn't help existing installs. A NEWS 
> entry explaining the impact and how to introduce an mkey to an existing 
> install might be more valuable than the actual postinst fix.
>
> (I've been through a similar exercise with openldap in #761406.)
-- 
Brian May 



Bug#869160: libgap-sage build-depends on gap (< 4r8p7) but 4r8p7-1 is to be installed

2017-07-21 Thread Adrian Bunk
Source: libgap-sage
Version: 4.8.6+3+20160327g69a66f0+dsx-2
Severity: serious
Tags: buster sid

The following packages have unmet dependencies:
 builddeps:libgap-sage : Depends: gap (< 4r8p7) but 4r8p7-1 is to be installed



Bug#869161: libreoffice-base crashes with code 139 when creating a new base or opening an existing one

2017-07-21 Thread thierry
Package: libreoffice-base
Version: 1:5.2.7-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

I have just upgraded from Jessie to Stretch and libreoffice-base always crashes 
when creating a new file or opening a file created with Jessie.
strace shows an error code 139


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

Kernel: Linux 4.9.0-3-686 (SMP w/1 CPU core)
Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8), 
LANGUAGE=fr_FR.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages libreoffice-base depends on:
ii  dpkg  1.18.24
ii  libc6 2.24-11+deb9u1
ii  libgcc1   1:6.3.0-18
ii  libreoffice-base-core 1:5.2.7-1
ii  libreoffice-base-drivers  1:5.2.7-1
ii  libreoffice-core  1:5.2.7-1
ii  libstdc++66.3.0-18
ii  uno-libs3 5.2.7-1
ii  ure   5.2.7-1

Versions of packages libreoffice-base recommends:
ii  default-jre [java5-runtime]2:1.8-58
ii  libreoffice-java-common1:5.2.7-1
ii  libreoffice-writer 1:5.2.7-1
ii  openjdk-8-jre [java5-runtime]  8u131-b11-2

Versions of packages libreoffice-base suggests:
pn  libreoffice-gcj 
ii  libreoffice-report-builder  1:5.2.7-1
pn  unixodbc

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

Versions of packages libreoffice-base is related to:
pn  libmyodbc
pn  libmysql-java
pn  libpg-java   
pn  libsapdbc-java   
pn  libsqliteodbc
pn  mdbtools 
pn  odbc-postgresql  
pn  tdsodbc  
pn  unixodbc 

-- no debconf information



Bug#869162: ros-rosinstall FTBFS: CalledProcessError: Command '[u'git', u'commit', u'-m', u'initial']' returned non-zero exit status 128

2017-07-21 Thread Adrian Bunk
Source: ros-rosinstall
Version: 0.7.7-4
Severity: serious

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/ros-rosinstall.html

...
test_get_with_rosinstall (test.local.test_locate.LocateTest) ... ok
test_getters (test.local.test_locate.LocateTest) ... ok
test_getters_empty (test.local.test_locate.LocateTest) ... Warning: No specific 
branch data for branch "devel" found, falling back on default checkout
Warning: No specific branch data for branch "release" found, falling back on 
default checkout
ok
test_getters_invalid (test.local.test_locate.LocateTest) ... Warning: No 
specific branch data for branch "devel" found, falling back on default checkout
ok

==
ERROR: setUpClass (test.local.test_ros_cli.RosinstallCommandLineGenerationTest)
--
Traceback (most recent call last):
  File "test/scm_test_base.py", line 167, in setUpClass
_create_fake_ros_dir(self.test_root_path)
  File "test/scm_test_base.py", line 64, in _create_fake_ros_dir
subprocess.check_call(["git", "commit", "-m", "initial"], cwd=ros_path)
  File "/usr/lib/python2.7/subprocess.py", line 186, in check_call
raise CalledProcessError(retcode, cmd)
CalledProcessError: Command '[u'git', u'commit', u'-m', u'initial']' returned 
non-zero exit status 128

==
ERROR: setUpClass (test.local.test_ros_cli.RosinstallCommandlineTest)
--
Traceback (most recent call last):
  File "test/scm_test_base.py", line 167, in setUpClass
_create_fake_ros_dir(self.test_root_path)
  File "test/scm_test_base.py", line 64, in _create_fake_ros_dir
subprocess.check_call(["git", "commit", "-m", "initial"], cwd=ros_path)
  File "/usr/lib/python2.7/subprocess.py", line 186, in check_call
raise CalledProcessError(retcode, cmd)
CalledProcessError: Command '[u'git', u'commit', u'-m', u'initial']' returned 
non-zero exit status 128

==
ERROR: setUpClass (test.local.test_rosinstall.RosinstallCommandlineOverlays)
--
Traceback (most recent call last):
  File "test/scm_test_base.py", line 167, in setUpClass
_create_fake_ros_dir(self.test_root_path)
  File "test/scm_test_base.py", line 64, in _create_fake_ros_dir
subprocess.check_call(["git", "commit", "-m", "initial"], cwd=ros_path)
  File "/usr/lib/python2.7/subprocess.py", line 186, in check_call
raise CalledProcessError(retcode, cmd)
CalledProcessError: Command '[u'git', u'commit', u'-m', u'initial']' returned 
non-zero exit status 128

==
ERROR: setUpClass 
(test.local.test_rosinstall.RosinstallCommandlineOverlaysWithSetup)
--
Traceback (most recent call last):
  File "test/scm_test_base.py", line 167, in setUpClass
_create_fake_ros_dir(self.test_root_path)
  File "test/scm_test_base.py", line 64, in _create_fake_ros_dir
subprocess.check_call(["git", "commit", "-m", "initial"], cwd=ros_path)
  File "/usr/lib/python2.7/subprocess.py", line 186, in check_call
raise CalledProcessError(retcode, cmd)
CalledProcessError: Command '[u'git', u'commit', u'-m', u'initial']' returned 
non-zero exit status 128

==
ERROR: setUpClass (test.local.test_rosws.RosWsTest)
--
Traceback (most recent call last):
  File "test/scm_test_base.py", line 167, in setUpClass
_create_fake_ros_dir(self.test_root_path)
  File "test/scm_test_base.py", line 64, in _create_fake_ros_dir
subprocess.check_call(["git", "commit", "-m", "initial"], cwd=ros_path)
  File "/usr/lib/python2.7/subprocess.py", line 186, in check_call
raise CalledProcessError(retcode, cmd)
CalledProcessError: Command '[u'git', u'commit', u'-m', u'initial']' returned 
non-zero exit status 128

==
ERROR: setUpClass (test.local.test_setupfiles.GenerateTest)
--
Traceback (most recent call last):
  File "test/scm_test_base.py", line 167, in setUpClass
_create_fake_ros_dir(self.test_root_path)
  File "test/scm_test_base.py", line 64, in _create_fake_ros_dir
subprocess.check_call(["git", "commit", "-m", "initial"], cwd=ros_path)
  File "/usr/lib/python2.7/subprocess.py", line 186, in check_call
raise CalledProcessError(retcode, cmd)
CalledProcessError: Command '[u'git', u'commit', u'-m', u'initial']' returned 
non-zero exit status 128

--
Ran 14 te

Bug#869163: skrooge: Missing icons in Skrooge in Debian Stretch

2017-07-21 Thread thierry
Package: skrooge
Version: 2.7.0-1
Severity: normal

Dear Maintainer,

I have just upgraded from Jessie to Stretch, and many icons are missing in the 
new Skrooge version.
I have installed the breeze-icon-theme package as recommended by the
upstream to no avail.
I am using the XCFE desktop


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

Kernel: Linux 4.9.0-3-686 (SMP w/1 CPU core)
Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8), 
LANGUAGE=fr_FR.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages skrooge depends on:
ii  kinit5.28.0-1
ii  kio  5.28.0-2
ii  libc62.24-11+deb9u1
ii  libgcc1  1:6.3.0-18
ii  libgrantlee-templates5   5.1.0-2
ii  libkf5archive5   5.28.0-2
ii  libkf5completion55.28.0-1
ii  libkf5configcore55.28.0-2
ii  libkf5configgui5 5.28.0-2
ii  libkf5configwidgets5 5.28.0-2
ii  libkf5coreaddons55.28.0-2
ii  libkf5dbusaddons55.28.0-1
ii  libkf5i18n5  5.28.0-2
ii  libkf5iconthemes55.28.0-2
ii  libkf5itemviews5 5.28.0-1
ii  libkf5kiocore5   5.28.0-2
ii  libkf5kiofilewidgets55.28.0-2
ii  libkf5newstuff5  5.28.0-1
ii  libkf5notifications5 5.28.0-1
ii  libkf5notifyconfig5  5.28.0-1
ii  libkf5parts5 5.28.0-1
ii  libkf5runner55.28.0-1
ii  libkf5service-bin5.28.0-1
ii  libkf5service5   5.28.0-1
ii  libkf5textwidgets5   5.28.0-1
ii  libkf5wallet-bin 5.28.0-3
ii  libkf5wallet55.28.0-3
ii  libkf5widgetsaddons5 5.28.0-3
ii  libkf5xmlgui55.28.0-1
ii  libofx6  1:0.9.10-2
ii  libqca-qt5-2 2.1.1-4+b2
ii  libqca-qt5-2-plugins 2.1.1-4+b2
ii  libqt5concurrent55.7.1+dfsg-3+b1
ii  libqt5core5a [qtbase-abi-5-7-1]  5.7.1+dfsg-3+b1
ii  libqt5dbus5  5.7.1+dfsg-3+b1
ii  libqt5gui5   5.7.1+dfsg-3+b1
ii  libqt5printsupport5  5.7.1+dfsg-3+b1
ii  libqt5qml5   5.7.1-2+b2
ii  libqt5quick5 5.7.1-2+b2
ii  libqt5quickwidgets5  5.7.1-2+b2
ii  libqt5script55.7.1~20161021+dfsg-2
ii  libqt5sql5   5.7.1+dfsg-3+b1
ii  libqt5sql5-sqlite5.7.1+dfsg-3+b1
ii  libqt5svg5   5.7.1~20161021-2+b2
ii  libqt5webkit55.7.1+dfsg-1
ii  libqt5widgets5   5.7.1+dfsg-3+b1
ii  libqt5xml5   5.7.1+dfsg-3+b1
ii  libsqlcipher03.2.0-2
ii  libstdc++6   6.3.0-18
ii  skrooge-common   2.7.0-1

Versions of packages skrooge recommends:
ii  poppler-utils  0.48.0-2

skrooge suggests no packages.

-- no debconf information



Bug#869164: ruby-net-scp FTBFS: test failures

2017-07-21 Thread Adrian Bunk
Source: ruby-net-scp
Version: 1.2.1-4
Severity: serious
Tags: buster sid

Some recent change in unstable makes ruby-net-scp FTBFS:

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

...
┌──┐
│ Run tests for ruby2.3 from debian/ruby-tests.rake│
└──┘

RUBYLIB=/build/1st/ruby-net-scp-1.2.1/debian/ruby-net-scp/usr/lib/ruby/vendor_ruby:.
 
GEM_PATH=debian/ruby-net-scp/usr/share/rubygems-integration/all:/var/lib/gems/2.3.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.3.0:/usr/share/rubygems-integration/2.3.0:/usr/share/rubygems-integration/all
 ruby2.3 -S rake -f debian/ruby-tests.rake
/usr/bin/ruby2.3 -w  "/usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb" 
"test/test_all.rb" "test/test_download.rb" "test/test_scp.rb" 
"test/test_upload.rb" -v
/build/1st/ruby-net-scp-1.2.1/test/test_download.rb:16: warning: assigned but 
unused variable - file
/build/1st/ruby-net-scp-1.2.1/test/test_download.rb:30: warning: assigned but 
unused variable - file
/build/1st/ruby-net-scp-1.2.1/lib/net/scp.rb:365: warning: shadowing outer 
local variable - ch
/build/1st/ruby-net-scp-1.2.1/lib/net/scp.rb:366: warning: shadowing outer 
local variable - ch
/build/1st/ruby-net-scp-1.2.1/lib/net/scp.rb:367: warning: shadowing outer 
local variable - ch
/build/1st/ruby-net-scp-1.2.1/lib/net/scp.rb:368: warning: shadowing outer 
local variable - ch
/usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55: warning: loading in 
progress, circular require considered harmful - 
/build/1st/ruby-net-scp-1.2.1/test/test_all.rb
from /usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb:4:in  `'
from /usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb:4:in  `select'
from /usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb:15:in  `block 
in '
from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in  
`require'
from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in  
`require'
from /build/1st/ruby-net-scp-1.2.1/test/test_all.rb:1:in  `'
from /build/1st/ruby-net-scp-1.2.1/test/test_all.rb:1:in  `chdir'
from /build/1st/ruby-net-scp-1.2.1/test/test_all.rb:2:in  `block in 
'
from /build/1st/ruby-net-scp-1.2.1/test/test_all.rb:2:in  `each'
from /build/1st/ruby-net-scp-1.2.1/test/test_all.rb:2:in  `block (2 
levels) in '
from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in  
`require'
from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in  
`require'
Loaded suite /usr/lib/ruby/vendor_ruby/rake/rake_test_loader
Started
Net::SCP::TestCase: 
  default_test: .: (0.000337)
  TestDownload: 
test_download_bang_without_target_should_return_string:.: (0.010297)
test_download_directory_should_create_directory_and_files_locally:E
===
Error: 
test_download_directory_should_create_directory_and_files_locally(TestDownload):
 TypeError: no implicit conversion of Net::SSH::Test::Socket into IO
/build/1st/ruby-net-scp-1.2.1/test/common.rb:151:in `scp'
/build/1st/ruby-net-scp-1.2.1/test/test_download.rb:181:in 
`test_download_directory_should_create_directory_and_files_locally'
F
===
Failure:
  unexpected invocation: 
File.open('/build/1st/ruby-net-scp-1.2.1/test/test_download.rb')
  satisfied expectations:
  - allowed any number of times, not yet invoked: 
Dir.entries('/path/to/local/remote/sub')
  - allowed any number of times, not yet invoked: Dir.mkdir()
  - allowed any number of times, not yet invoked: 
Dir.entries('/path/to/local/remote')
  - allowed any number of times, not yet invoked: Dir.mkdir()
  - allowed any number of times, not yet invoked: Dir.entries('/path/to/local')
  - allowed any number of times, not yet invoked: Dir.mkdir()
  - allowed any number of times, not yet invoked: 
File.new('/path/to/local/remote/sub/remote.txt', 'wb', 438)
  - allowed any number of times, not yet invoked: 
File.open('/path/to/local/remote/sub/remote.txt', 'rb')
  - allowed any number of times, not yet invoked: 
File.file?('/path/to/local/remote/sub/remote.txt')
  - allowed any number of times, not yet invoked: 
File.directory?('/path/to/local/remote/sub/remote.txt')
  - allowed any number of times, not yet invoked: 
File.stat('/path/to/local/remote/sub/remote.txt')
  - allowed any number of times, not yet invoked: 
File.file?('/path/to/local/remote/sub')
  - allowed any number of times, not yet invoked: 
File.directory?('/path/to/local/remote/sub')
  - allowed any number of times, not yet invoked: 
File.stat('/path/to/local/remote/sub')
  - allowed any num

Bug#866389: transition: perl 5.26

2017-07-21 Thread Emilio Pozuelo Monfort
On 20/07/17 22:51, Niko Tyni wrote:
> Control: block -1 with 869139
> 
> On Thu, Jul 20, 2017 at 09:16:41PM +0200, Emilio Pozuelo Monfort wrote:
>> On 20/07/17 21:01, Niko Tyni wrote:
>>> On Thu, Jun 29, 2017 at 07:51:33PM +0200, Emilio Pozuelo Monfort wrote:
 Control: forwarded -1 
 https://release.debian.org/transitions/html/perl5.26.html
> 
>>> Please let us know when it would be OK to upload Perl 5.26 to sid.
>>
>> Awesome. Now is a good time. I have added some hints for the gsoap and
>> libprelude transitions, so they don't get entangled with this one.
> 
> Thanks. I have an upload (almost) ready, but a last minute issue popped
> up as the fixed syslog-ng-incubator fails to build on s390x. See #869139.
> 
> Do you want me to hold off because of that?

I think we can go ahead and worst case remove it as we were planning to before
it got fixed.

Cheers,
Emilio



Bug#868283: cups-browsed ignores "DefaultPolicy authenticated" from cupsd.conf

2017-07-21 Thread Christoph Pleger

Hello,


cups-browsed now saves a copy of the remote printer's PPD in
/var/cache/cups. "Operation Policy" is one of the options which
can set there using the web interface (say).


I cannot find where to change the operation policy in the web interface.



I wonder whether we really have a bug here if this is the way
it is designed to work now.


If cups-browsed is designed to take invalid data from a self-created 
cache, than that is a bug in design.


Regards
  Christoph



Bug#803013: systemd should not destroy application created cgroups

2017-07-21 Thread Paul Szabo

Dear Martin,


... the official and documented mechanism is to set
"Delegate=yes" in a unit which wants to do its own cgroup management.
Everything else is just a hack prone to bitrotting...


Where would I set that? My cgrulesengd (from package cgroup-tools) is
started from /etc/init.d/cgred, not from some systemd *.service thing.
My cgrulesengd sets things under
  /sys/fs/cgroup/cpu,cpuacct/
and I do not see that mentioned in any systemd config-type files.


(Distressing how this bug did not get fixed in two years...)


Like it apparently happened to the previous patch that we've been
carrying for three years already:

https://anonscm.debian.org/cgit/pkg-systemd/systemd.git/tree/debian/patches/debian/cgroup-don-t-trim-cgroup-trees-created-by-someone-el.patch

Seems this is not sufficient any more?


You mean file

debian/patches/debian/cgroup-don-t-trim-cgroup-trees-created-by-someone-el.patch
within
  systemd_232-25.debian.tar.xz
or already in say
  systemd_215-17+deb8u2.debian.tar.xz
No, it is not (and was never) sufficient: that is a different bug.

Thanks, Paul
--
Paul Szabo   p...@maths.usyd.edu.au   http://www.maths.usyd.edu.au/u/psz/
School of Mathematics and Statistics   University of SydneyAustralia



Bug#869165: nemo: Nemo crash when exploring folders

2017-07-21 Thread William MARTIN
Package: nemo
Version: 3.2.2-3
Severity: grave
Justification: renders package unusable

Dear Maintainer,

I have fresh install of Debian Stretch with Cinnamon.
I have no extra theme, just visual effets disabled.

Nemo crash randomly very often.

Here a backtrace :

Thread 1 "nemo" received signal SIGSEGV, Segmentation fault.
0x7f4e1a2b195a in g_type_check_instance_cast () from /usr/lib/x86_64-linux-
gnu/libgobject-2.0.so.0
(gdb) bt
#0  0x7f4e1a2b195a in g_type_check_instance_cast () from
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#1  0x55ec17d23cfb in ?? ()
#2  0x7f4e1bd53ba1 in ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
#3  0x7f4e1a28d1a4 in ?? () from /usr/lib/x86_64-linux-
gnu/libgobject-2.0.so.0
#4  0x7f4e1a2a73a1 in g_signal_emit_valist () from /usr/lib/x86_64-linux-
gnu/libgobject-2.0.so.0
#5  0x7f4e1a2a7fbf in g_signal_emit () from /usr/lib/x86_64-linux-
gnu/libgobject-2.0.so.0
#6  0x7f4e1bea057c in ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
#7  0x7f4e1bd50b2e in ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
#8  0x7f4e1bd52bee in gtk_main_do_event () from /usr/lib/x86_64-linux-
gnu/libgtk-3.so.0
#9  0x7f4e1b863e15 in ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
#10 0x7f4e1b894ea2 in ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
#11 0x7f4e19fb37f7 in g_main_context_dispatch () from /lib/x86_64-linux-
gnu/libglib-2.0.so.0
#12 0x7f4e19fb3a60 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#13 0x7f4e19fb3b0c in g_main_context_iteration () from /lib/x86_64-linux-
gnu/libglib-2.0.so.0
#14 0x7f4e1a56f72d in g_application_run () from /usr/lib/x86_64-linux-
gnu/libgio-2.0.so.0
#15 0x55ec17c3abcd in ?? ()
#16 0x7f4e190bc2b1 in __libc_start_main (main=0x55ec17c3aaf0, argc=1,
argv=0x7ffd9740c9c8, init=, fini=,
rtld_fini=, stack_end=0x7ffd9740c9b8)
at ../csu/libc-start.c:291
#17 0x55ec17c3ac3a in ?? ()

I have produce a core dump (~ 600 MB), i can provide it privatly to the
maintainer.

Best regards,





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

Kernel: Linux 4.9.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=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 nemo depends on:
ii  desktop-file-utils 0.23-1
ii  gsettings-desktop-schemas  3.22.0-1
ii  gvfs   1.30.4-1
ii  libatk1.0-02.22.0-1
ii  libc6  2.24-11+deb9u1
ii  libcairo-gobject2  1.14.8-1
ii  libcairo2  1.14.8-1
ii  libcinnamon-desktop4   3.2.4-4
ii  libexempi3 2.4.1-1
ii  libexif12  0.6.21-2+b2
ii  libgail-3-03.22.11-1
ii  libgdk-pixbuf2.0-0 2.36.5-2
ii  libglib2.0-0   2.50.3-2
ii  libglib2.0-data2.50.3-2
ii  libgtk-3-0 3.22.11-1
ii  libnemo-extension1 3.2.2-3
ii  libnotify4 0.7.7-2
ii  libpango-1.0-0 1.40.5-1
ii  libpangocairo-1.0-01.40.5-1
ii  libx11-6   2:1.6.4-3
ii  libxml22.9.4+dfsg1-2.2
ii  nemo-data  3.2.2-3
ii  shared-mime-info   1.8-1

Versions of packages nemo recommends:
ii  cinnamon-l10n3.2.2-2
ii  gvfs-backends1.30.4-1
ii  gvfs-fuse1.30.4-1
ii  librsvg2-common  2.40.16-1+b1
ii  nemo-fileroller  3.2.1-2

Versions of packages nemo suggests:
ii  eog  3.20.5-1+b1
ii  evince [pdf-viewer]  3.22.1-3+deb9u1
ii  totem3.22.1-1
ii  xdg-user-dirs0.15-2+b1

-- no debconf information



Bug#576998: [Pkg-javascript-devel] why not

2017-07-21 Thread Paolo Greppi
Hallo yes it's still on my todo list.

It's not in the npm registry so we can't easily (i.e. with the js_task_edit.py 
script) create a task page as for the other nodejs packages [1].

But it has quite a few  node dependencies.

As libjs-tinycon and node-jsonminify are in the archive we're left with 7 
direct dependencies:
- require-kernel, ITP #710057
- socket.io ITP [2]
- ueberdb
- express-session ITP #751885
- cheerio ITP #848315
- swagger-node-express
- measured

But then as Mike pointed out [3], there are recursive dependencies, so the 
count is higher.

For example there's 7 socket.io deps already listed as blocking bugs in the 
socket.io's ITP [2].

Then there is more which the last time I looked lacked IPTs:

Ueberdb2 deps:
node-cassandra-driver
node-rethinkdb
node-nano
node-elasticsearch

Cassandra-driver deps:
Node-long

rethinkdb deps:
bluebird

nano deps:
follow

And beware that I may have left out a few.

Finally one more difficulty is that it's hard to grasp what this stuff is all 
about.
For example from what I can tell there are several DB middlewares, so the 
question is: is this all really used ?

Anyway any help is welcome !

Paolo

[1] https://wiki.debian.org/Javascript/Nodejs/Tasks
[2] https://bugs.debian.org/707166
[3] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=576998#138

Il 21/07/2017 09:39, Petter Reinholdtsen ha scritto:
> Hi.
> 
> Any progress on getting Etherpad into Debian?  I would love to add
> support for Etherpad to FreedomBox, but for that to happen there
> need to be maintainable packages in Debian.
> 
> Yesteday, the Software Freedom Conservancy announced that Etherpad
> join the Conservancy as a member, see
> https://sfconservancy.org/news/2017/jul/20/etherpad/ >.  Perhaps
> that might motivate more people to get Etherpad into Debian?
> 



Bug#869166: Heap buffer overflows in psf_binheader_writef

2017-07-21 Thread Guido Günther
Source: libsndfile
Version: 1.0.25-9.1+deb7u3
Severity: important

Hi,
Looking at

 https://security-tracker.debian.org/tracker/TEMP-000-1EDB2D

(temporary ID, will change iff a CVE gets assigned) libsndfile has
several heap buffer overflows affecting all versions so filing a bug to
track this.
Cheers,
 -- Guido
   

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

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



Bug#576998: [Pkg-javascript-devel] why not

2017-07-21 Thread Mike Gabriel

Hi Petter,

On  Fr 21 Jul 2017 09:39:03 CEST, Petter Reinholdtsen wrote:


Hi.

Any progress on getting Etherpad into Debian?  I would love to add
support for Etherpad to FreedomBox, but for that to happen there
need to be maintainable packages in Debian.

Yesteday, the Software Freedom Conservancy announced that Etherpad
join the Conservancy as a member, see
https://sfconservancy.org/news/2017/jul/20/etherpad/ >.  Perhaps
that might motivate more people to get Etherpad into Debian?


the Linux Hotel (Ingo Wichmann) had plans to sponsor the upload of  
etherpad to Debian. I discourged the request because of the following:


```
rough statistics:

   140 marked as "not in Debian" (maybe with some false positives)
   2h per package (absolutely the minimum required time) -> 280 h
   280h * 75?/h -> 21.000 EUR

... we are talking of 35 days of full time work.

```

This raw calculation was made by me around April 2016.

Greets,
Mike
--

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

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



pgpxBBfl6G71K.pgp
Description: Digitale PGP-Signatur


Bug#860040: [Pkg-utopia-maintainers] Bug#866612: network-manager: no permission to toggle network/wifi

2017-07-21 Thread Yves-Alexis Perez
On Fri, 2017-06-30 at 16:23 +0200, Michael Biebl wrote:
> Am 30.06.2017 um 16:09 schrieb Yves-Alexis Perez:
> > Package: network-manager
> > Version: 1.8.0-5
> > Severity: normal
> > 
> > Hi,
> > 
> > I'm running Debian sid, with Xfce desktop environment and
> > network-manager. Since few days after Stretch release (and with a lot of
> > post-release upgrades), I can't toggle the network and wifi in
> > network-manager.
> 
> I'm not using lightdm or stretch and it works fine under GNOME here, so
> it doesn't seem to be a problem specific to network-manager.
> 
> Do you have dbus-user-session installed? A polkit agent successfully
> running in your desktop session?

Hi Michael,

I've managed to debug this a bit further, and it seems to actually be #860040

When /proc is mounted with hidepid>0 /proc/1/cgroup can't be read (either
because /proc/1 doesn't exist, if hidepid=2, or because /proc/1/cgroup is not
readable, if hidepid=1).

In that case, polkit-gnome-authentication-agent-1 (or lxpolkit, for that
matter) bails out early.

I'm not entirely sure why it needs to get information about init cgroups but
the behavior looks wrong to me at first sight.

In any case, the bug is indeed not in network-manager.

Regards,
-- 
Yves-Alexis

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


Bug#869167: rbldnsd: on service restart the old process does not exit on time so new process fails to bind to the IP

2017-07-21 Thread Lucian A.
Package: rbldnsd
Version: 0.998b~pre1-1
Severity: normal

Dear Maintainer,

During service restart the old rbldnsd process does not exit on time.
When the new process is started it fails to bind to the same IP address on port 
53.


-- System Information:
Debian Release: 9.0
Architecture: amd64 (x86_64)

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

Versions of packages rbldnsd depends on:
ii  adduser   3.115
ii  libc6 2.24-12
ii  lsb-base  9.20161125
ii  zlib1g1:1.2.8.dfsg-5

rbldnsd recommends no packages.

rbldnsd suggests no packages.

-- Configuration Files:
/etc/default/rbldnsd changed [not included]

-- no debconf information



Bug#869161: libreoffice-base crashes with code 139 when creating a new base or opening an existing one

2017-07-21 Thread Rene Engelhard
reassign 869161 src:linux
severity 865303 grave
forcemerge 865303 869161
affects 869161 libreoffice-base
thanks

Hi,

On Fri, Jul 21, 2017 at 10:00:15AM +0200, thierry wrote:
> I have just upgraded from Jessie to Stretch and libreoffice-base always 
> crashes when creating a new file or opening a file created with Jessie.
> strace shows an error code 139

Backtrace please?

I believe you ran into

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865303
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865866
https://lwn.net/Articles/727206/

and more (e.g. the LO build on i386 also is affected when running its
tests)

Short: Anything using Java in LO will crash on i386 after the Stack Clash
security fixes which happened after the stretch release.

> -- System Information:
> Debian Release: 9.0
>   APT prefers unstable
>   APT policy: (500, 'unstable'), (500, 'stable')
> Architecture: i386 (i686)

You might want to use amd64...

Anyways: Reassigning to the kernel.

Regards,

Rene



Bug#803013: systemd should not destroy application created cgroups

2017-07-21 Thread Martin Pitt
Hello Paul,

Paul Szabo [2017-07-21 18:25 +1000]:
> Where would I set that? My cgrulesengd (from package cgroup-tools) is
> started from /etc/init.d/cgred, not from some systemd *.service thing.

You can create a drop-in like /etc/systemd/system/cgred.service.d/delegate.conf
with

[Service]
Delegate=yes

> > https://anonscm.debian.org/cgit/pkg-systemd/systemd.git/tree/debian/patches/debian/cgroup-don-t-trim-cgroup-trees-created-by-someone-el.patch
> No, it is not (and was never) sufficient: that is a different bug.

OK, thanks for the heads-up.

Martin



Bug#867192: [Pkg-dns-devel] Bug#867192: let systemd know about the pid file

2017-07-21 Thread Simon Deziel
On 2017-07-14 06:15 PM, Robert Edmonds wrote:
> Simon Deziel wrote:
>> When unbound is stopped, its PID file is left behind causing subsequent
>> service starts to complain like that:
>>
>>  unbound[178]: [178:0] warning: did not exit gracefully last time (124)
>>
>> Please find a patch that tells systemd where the PID is so that it can
>> delete it once unbound is stopped.
> 
> Hi, Simon:
> 
> Are you sure about this? When I "systemctl stop unbound", "systemctl
> start unbound", I get the following output in the journal:
> 
> Jul 14 18:12:52 chase systemd[1]: Stopping Unbound DNS server...
> Jul 14 18:12:52 chase unbound[26190]: [26190:0] info: service stopped 
> (unbound 1.6.4).
> Jul 14 18:12:52 chase unbound[26190]: [26190:0] info: server stats for thread 
> 0: 0 queries, 0 answers from cache, 0 recursions, 0 prefetch, 0 rejected by 
> ip ratelimiting
> Jul 14 18:12:52 chase unbound[26190]: [26190:0] info: server stats for thread 
> 0: requestlist max 0 avg 0 exceeded 0 jostled 0
> Jul 14 18:12:52 chase systemd[1]: Stopped Unbound DNS server.
> Jul 14 18:13:00 chase systemd[1]: Starting Unbound DNS server...
> Jul 14 18:13:00 chase package-helper[26343]: /var/lib/unbound/root.key has 
> content
> Jul 14 18:13:00 chase package-helper[26343]: success: the anchor is ok
> Jul 14 18:13:00 chase unbound[26347]: [26347:0] notice: init module 0: 
> validator
> Jul 14 18:13:00 chase unbound[26347]: [26347:0] notice: init module 1: 
> iterator
> Jul 14 18:13:00 chase unbound[26347]: [26347:0] info: start of service 
> (unbound 1.6.4).
> Jul 14 18:13:00 chase systemd[1]: Started Unbound DNS server.
> 
> It also looks like unbound truncates the pidfile when it shuts down?
> 

It only happens when using Apparmor as the profile prevents unbound from
chown'ing the pidfile which then prevents the truncation from happening.
For the rational of denying the chown, please see:

https://code.launchpad.net/~sdeziel/apparmor-profiles/unbound-refresh/+merge/282230

Sorry for not mentioning Apparmor before, I only realized this now and
was in PTO for the past week.

Regards,
Simon



Bug#721976: ca-certificates contains both server and email certificates

2017-07-21 Thread Jacob Hoffman-Andrews
Hi, sending you a gentle ping on this. Would love to get this fix
landed. Thanks!



Bug#868041: [Pkg-freeradius-maintainers] Bug#868041: freeradius: jessie-backports available

2017-07-21 Thread Maxime Lareo
Hi there,

On 07/11/2017 04:02 PM, Michael Stapelberg wrote:
> 
> 
> On Tue, Jul 11, 2017 at 3:52 PM, Maxime Lareo
> mailto:maxime.la...@infomaniak.com>> wrote:
> 
> Package: freeradius
> Version: 3.0.12+dfsg-5~bpo8+1
> Severity: wishlist
> User: product...@infomaniak.com 
> Usertag: infomaniak.com-packaging
> 
> Dear Maintainer,
> 
> We needed freeradius 3.X on jessie at work, therefore we backported it:
> 
> --8<---cut here---start->8---
> freeradius (3.0.12+dfsg-5~bpo8+1) jessie-backports; urgency=medium
> 
>   * Rebuild for jessie-backports.
>   * Revert freeradius-dbg package removal
> - control: revert removal of freeradius-dbg package
> - rules: revert dh_strip options to dh_strip -a --dbg-package
>   * control: revert debhelper version dependency to (>=9)
>   * rules: remove --fail-missing option from dh_install
> 
>  -- Maxime Lareo  >  Fri, 07 Jul 2017
> 09:41:13 +0200
> 
> --8<---cut here---end--->8---
> 
> All the modifications have been made to a Git checkout of the official
> Debian repositories, with signed commits and tags. And I can provide
> read-only access to such repositories, if someone would like to
> integrate the modifications.
> 
> 
> Please do.

I was waiting to test this backports in production before share you my
work, and its been running for more than a week now, without any troubles.

So here is the promised link to the git repository :
https://gitlab-ext.infomaniak.com/debpkg-public/freeradius.git

Thank you, bye
Maxime Lareo

-- 
Maxime Lareo
Administrateur Systèmes et Réseaux Junior
Infomaniak Network SA



signature.asc
Description: OpenPGP digital signature


Bug#866120: diffoscope: please add an xml comparator

2017-07-21 Thread Chris Lamb
forcemerge 866120 869154
tags 866120 + patch
thanks

Woo, thanks! First, am going to merge this into the existing wishlist bug…


Regards,

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



Bug#869171: slirp: out-of-bounds read while parsing dhcp options

2017-07-21 Thread Guido Günther
Package: qemu
X-Debbugs-CC: t...@security.debian.org 
secure-testing-t...@lists.alioth.debian.org
Severity: important
Tags: security

Hi,

the following vulnerability was published for qemu.

CVE-2017-11434[0]:
slirp: out-of-bounds read while parsing dhcp options

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-11434
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-11434

Please adjust the affected versions in the BTS as needed.



Bug#869170: coyim: Gtk warnings on stderr

2017-07-21 Thread Daniel Kahn Gillmor
Package: coyim
Version: 0.3.8+ds-2
Severity: normal

running coyim, i see the following reports from gtk to stderr (or
maybe it's stdout):

(CoyIM:8135): Gtk-CRITICAL **: gtk_tree_model_get_iter_first: assertion 
'GTK_IS_TREE_MODEL (tree_model)' failed

(CoyIM:8135): Gtk-WARNING **: Failed to set text '' from markup due to 
error parsing markup: Error on line 1 char 24: Element 'markup' was closed, but 
the currently open element is 'UNSET'

(CoyIM:8135): Gtk-WARNING **: Failed to set text '' from markup due to 
error parsing markup: Error on line 1 char 24: Element 'markup' was closed, but 
the currently open element is 'UNSET'

(CoyIM:8135): Gtk-WARNING **: GtkBox does not have a child property called 
left-attach

(CoyIM:8135): Gtk-WARNING **: GtkBox does not have a child property called 
top-attach

(CoyIM:8135): Gtk-WARNING **: GtkBox does not have a child property called width


That's worth cleaning up so that real errors are more visible.

   --dkg

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

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

Versions of packages coyim depends on:
ii  libatk1.0-0  2.24.0-1
ii  libc62.24-12
ii  libcairo-gobject21.14.10-1
ii  libcairo21.14.10-1
ii  libgdk-pixbuf2.0-0   2.36.5-2
ii  libglib2.0-0 2.52.3-1
ii  libgtk-3-0   3.22.16-1
ii  libpango-1.0-0   1.40.6-1
ii  libpangocairo-1.0-0  1.40.6-1

Versions of packages coyim recommends:
ii  tor  0.3.0.9-1

coyim suggests no packages.

-- no debconf information



Bug#869169: ITP: minisign -- A dead simple tool to sign files and verify signatures

2017-07-21 Thread Daniel Kahn Gillmor
Package: wnpp
Severity: wishlist
Owner: Daniel Kahn Gillmor 

* Package name: minisign
  Version : 0.7
  Upstream Author : Frank Denis 
* URL : https://jedisct1.github.io/minisign/
* License : ISC (like Expat)
  Programming Lang: C
  Description : A dead simple tool to sign files and verify signatures

Minisign is a dead simple tool to sign files and verify signatures.

It is portable, lightweight, and uses the highly secure Ed25519
public-key signature system.

--

This can be useful for people interested in packaging software that is
distributed by authors who use Minisign keys, such as dnscrypt.



Bug#869172: RFP: exploitable -- GDB extension for classification of bugs

2017-07-21 Thread Daniel Stender
Package: wnpp
Severity: wishlist
Control: block 845133 by -1

* Package name: exploitable
  Version : 1.32
  Upstream Author : Jonathan Foote 
* URL : https://github.com/jfoote/exploitable
* License : Expat
  Programming Lang: Python
  Description : GDB extension for classification of bugs

>From the site: "'exploitable' is a GDB extension that classifies Linux 
>application bugs by
severity. The extension inspects the state of a Linux application that has 
crashed and outputs a
summary of how difficult it might be for an attacker to exploit the underlying 
software bug to gain
control of the system. The extension can be used to prioritize bugs for 
software developers so that
they can address the most severe ones first."

This hasn't been updated since 2015, but it's required by afl-utils.

Thanks,
Daniel Stender



Bug#869173: exec: oob access during dma operation

2017-07-21 Thread Guido Günther
Package: qemu
X-Debbugs-CC: t...@security.debian.org 
secure-testing-t...@lists.alioth.debian.org
Severity: important
Tags: security

Hi,

the following vulnerability was published for qemu.

CVE-2017-11334[0]:
exec: oob access during dma operation

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-11334
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-11334

Please adjust the affected versions in the BTS as needed.



Bug#869177: ruby-serverspec: FTBFS: can't satisfy 'net-ssh (< 4.0, >= 2.7)', already activated 'net-ssh-4.1.0' (Gem::LoadError)

2017-07-21 Thread Lucas Nussbaum
Source: ruby-serverspec
Version: 2.37.2-1
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170721 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
> Invalid gemspec in [serverspec.gemspec]: No such file or directory - git
> GEM_PATH=debian/ruby-serverspec/usr/share/rubygems-integration/all:/var/lib/gems/2.3.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.3.0:/usr/share/rubygems-integration/2.3.0:/usr/share/rubygems-integration/all
>  ruby2.3 -e gem\ \"serverspec\"
> /usr/lib/ruby/2.3.0/rubygems/specification.rb:1436:in `block in 
> activate_dependencies': can't satisfy 'net-ssh (< 4.0, >= 2.7)', already 
> activated 'net-ssh-4.1.0' (Gem::LoadError)
>   from /usr/lib/ruby/2.3.0/rubygems/specification.rb:1428:in `each'
>   from /usr/lib/ruby/2.3.0/rubygems/specification.rb:1428:in 
> `activate_dependencies'
>   from /usr/lib/ruby/2.3.0/rubygems/specification.rb:1410:in `activate'
>   from /usr/lib/ruby/2.3.0/rubygems/specification.rb:1442:in `block in 
> activate_dependencies'
>   from /usr/lib/ruby/2.3.0/rubygems/specification.rb:1428:in `each'
>   from /usr/lib/ruby/2.3.0/rubygems/specification.rb:1428:in 
> `activate_dependencies'
>   from /usr/lib/ruby/2.3.0/rubygems/specification.rb:1410:in `activate'
>   from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_gem.rb:68:in `block 
> in gem'
>   from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_gem.rb:67:in 
> `synchronize'
>   from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_gem.rb:67:in `gem'
>   from -e:1:in `'
> bcrypt_pbkdf (1.0.0)
> bigdecimal (1.2.8)
> did_you_mean (1.0.0)
> diff-lcs (1.3)
> ffi (1.9.10)
> io-console (0.4.5)
> json (1.8.3)
> minitest (5.10.2)
> multi_json (1.12.1)
> net-scp (1.2.1)
> net-ssh (4.1.0)
> net-telnet (0.1.1)
> power_assert (0.2.7)
> psych (2.1.0)
> rake (12.0.0)
> rbnacl (5.0.0)
> rdoc (4.2.1)
> rspec (3.5.0)
> rspec-core (3.5.3)
> rspec-expectations (3.5.0)
> rspec-its (1.2.0)
> rspec-mocks (3.5.0)
> rspec-support (3.5.0)
> specinfra (2.66.0)
> test-unit (3.2.5)
> thread_order (1.1.0)
> ERROR: Test "ruby2.3" failed: 

The full build log is available from:
   http://aws-logs.debian.net/2017/07/21/ruby-serverspec_2.37.2-1_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.



Bug#869176: itamae: FTBFS: can't satisfy 'net-ssh (< 4.0, >= 2.7)', already activated 'net-ssh-4.1.0' (Gem::LoadError)

2017-07-21 Thread Lucas Nussbaum
Source: itamae
Version: 1.9.10-1
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170721 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
> /usr/bin/ruby2.3 /usr/bin/gem2deb-test-runner
> 
> ┌──┐
> │ Checking Rubygems dependency resolution on ruby2.3  
>  │
> └──┘
> 
> GEM_PATH=debian/itamae/usr/share/rubygems-integration/all:/var/lib/gems/2.3.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.3.0:/usr/share/rubygems-integration/2.3.0:/usr/share/rubygems-integration/all
>  ruby2.3 -e gem\ \"itamae\"
> /usr/lib/ruby/2.3.0/rubygems/specification.rb:1436:in `block in 
> activate_dependencies': can't satisfy 'net-ssh (< 4.0, >= 2.7)', already 
> activated 'net-ssh-4.1.0' (Gem::LoadError)
>   from /usr/lib/ruby/2.3.0/rubygems/specification.rb:1428:in `each'
>   from /usr/lib/ruby/2.3.0/rubygems/specification.rb:1428:in 
> `activate_dependencies'
>   from /usr/lib/ruby/2.3.0/rubygems/specification.rb:1410:in `activate'
>   from /usr/lib/ruby/2.3.0/rubygems/specification.rb:1442:in `block in 
> activate_dependencies'
>   from /usr/lib/ruby/2.3.0/rubygems/specification.rb:1428:in `each'
>   from /usr/lib/ruby/2.3.0/rubygems/specification.rb:1428:in 
> `activate_dependencies'
>   from /usr/lib/ruby/2.3.0/rubygems/specification.rb:1410:in `activate'
>   from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_gem.rb:68:in `block 
> in gem'
>   from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_gem.rb:67:in 
> `synchronize'
>   from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_gem.rb:67:in `gem'
>   from -e:1:in `'
> ansi (1.5.0)
> asciidoctor (1.5.5)
> bcrypt_pbkdf (1.0.0)
> bigdecimal (1.2.8)
> did_you_mean (1.0.0)
> diff-lcs (1.3)
> fakefs (0.6.7)
> ffi (1.9.10)
> hashie (3.4.4)
> io-console (0.4.5)
> json (1.8.3)
> minitest (5.10.2)
> net-scp (1.2.1)
> net-ssh (4.1.0)
> net-telnet (0.1.1)
> power_assert (0.2.7)
> psych (2.1.0)
> rake (12.0.0)
> rbnacl (5.0.0)
> rdoc (4.2.1)
> rspec (3.5.0)
> rspec-core (3.5.3)
> rspec-expectations (3.5.0)
> rspec-mocks (3.5.0)
> rspec-support (3.5.0)
> schash (0.1.2)
> specinfra (2.66.0)
> test-unit (3.2.5)
> thor (0.19.4)
> thread_order (1.1.0)
> ERROR: Test "ruby2.3" failed.

The full build log is available from:
   http://aws-logs.debian.net/2017/07/21/itamae_1.9.10-1_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.



Bug#869178: test-kitchen: FTBFS: can't satisfy 'net-ssh (< 4.0, >= 2.9)', already activated 'net-ssh-4.1.0' (Gem::LoadError)

2017-07-21 Thread Lucas Nussbaum
Source: test-kitchen
Version: 1.11.1-1
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170721 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
> /usr/bin/ruby2.3 /usr/bin/gem2deb-test-runner
> 
> ┌──┐
> │ Checking Rubygems dependency resolution on ruby2.3  
>  │
> └──┘
> 
> fatal: Not a git repository (or any of the parent directories): .git
> GEM_PATH=debian/test-kitchen/usr/share/rubygems-integration/all:/var/lib/gems/2.3.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.3.0:/usr/share/rubygems-integration/2.3.0:/usr/share/rubygems-integration/all
>  ruby2.3 -e gem\ \"test-kitchen\"
> /usr/lib/ruby/2.3.0/rubygems/specification.rb:1436:in `block in 
> activate_dependencies': can't satisfy 'net-ssh (< 4.0, >= 2.9)', already 
> activated 'net-ssh-4.1.0' (Gem::LoadError)
>   from /usr/lib/ruby/2.3.0/rubygems/specification.rb:1428:in `each'
>   from /usr/lib/ruby/2.3.0/rubygems/specification.rb:1428:in 
> `activate_dependencies'
>   from /usr/lib/ruby/2.3.0/rubygems/specification.rb:1410:in `activate'
>   from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_gem.rb:68:in `block 
> in gem'
>   from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_gem.rb:67:in 
> `synchronize'
>   from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_gem.rb:67:in `gem'
>   from -e:1:in `'
> aruba (0.14.2)
> bcrypt_pbkdf (1.0.0)
> bigdecimal (1.2.8)
> blankslate (3.1.3)
> builder (3.2.2)
> childprocess (0.5.9)
> coderay (1.1.1)
> contracts (0.14.0)
> cucumber (2.4.0)
> cucumber-core (1.5.0)
> cucumber-wire (0.0.1)
> did_you_mean (1.0.0)
> diff-lcs (1.3)
> fakefs (0.6.7)
> ffi (1.9.10)
> gherkin (4.0.0)
> io-console (0.4.5)
> json (1.8.3)
> metaclass (0.0.4)
> method_source (0.8.2)
> minitest (5.10.2)
> mixlib-install (1.1.0)
> mixlib-shellout (2.2.6)
> mixlib-versioning (1.1.0)
> mocha (1.2.1)
> multi_json (1.12.1)
> multi_test (0.1.2)
> net-scp (1.2.1)
> net-ssh (4.1.0)
> net-ssh-gateway (1.2.0)
> net-telnet (0.1.1)
> power_assert (0.2.7)
> pry (0.10.3)
> psych (2.1.0)
> rake (12.0.0)
> rbnacl (5.0.0)
> rdoc (4.2.1)
> rspec-expectations (3.5.0)
> rspec-support (3.5.0)
> safe_yaml (1.0.4)
> test-unit (3.2.5)
> thor (0.19.4)
> ERROR: Test "ruby2.3" failed.

The full build log is available from:
   http://aws-logs.debian.net/2017/07/21/test-kitchen_1.11.1-1_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.



Bug#869179: chef: FTBFS: Could not find 'net-ssh' (< 4.0, >= 2.9) - did find: [net-ssh-4.1.0] (Gem::LoadError)

2017-07-21 Thread Lucas Nussbaum
Source: chef
Version: 12.14.60-2
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170721 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
> /usr/bin/ruby2.3 /usr/bin/gem2deb-test-runner
> 
> ┌──┐
> │ Checking Rubygems dependency resolution on ruby2.3  
>  │
> └──┘
> 
> GEM_PATH=debian/ruby-chef-config/usr/share/rubygems-integration/all:debian/chef/usr/share/rubygems-integration/all:/var/lib/gems/2.3.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.3.0:/usr/share/rubygems-integration/2.3.0:/usr/share/rubygems-integration/all
>  ruby2.3 -e gem\ \"chef\"
> /usr/lib/ruby/2.3.0/rubygems/dependency.rb:319:in `to_specs': Could not find 
> 'net-ssh' (< 4.0, >= 2.9) - did find: [net-ssh-4.1.0] (Gem::LoadError)
> Checked in 
> 'GEM_PATH=debian/ruby-chef-config/usr/share/rubygems-integration/all:debian/chef/usr/share/rubygems-integration/all:/var/lib/gems/2.3.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.3.0:/usr/share/rubygems-integration/2.3.0:/usr/share/rubygems-integration/all',
>  execute `gem env` for more information
>   from /usr/lib/ruby/2.3.0/rubygems/specification.rb:1439:in `block in 
> activate_dependencies'
>   from /usr/lib/ruby/2.3.0/rubygems/specification.rb:1428:in `each'
>   from /usr/lib/ruby/2.3.0/rubygems/specification.rb:1428:in 
> `activate_dependencies'
>   from /usr/lib/ruby/2.3.0/rubygems/specification.rb:1410:in `activate'
>   from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_gem.rb:68:in `block 
> in gem'
>   from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_gem.rb:67:in 
> `synchronize'
>   from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_gem.rb:67:in `gem'
>   from -e:1:in `'
> addressable (2.4.0)
> bcrypt_pbkdf (1.0.0)
> bigdecimal (1.2.8)
> bundler (1.15.1)
> chef-config (12.14.60)
> chef-zero (5.1.1)
> cheffish (4.0.0)
> compat_resource (12.10.5)
> did_you_mean (1.0.0)
> diff-lcs (1.3)
> erubis (2.7.0)
> ffi (1.9.10)
> ffi-yajl (2.2.3)
> fuzzyurl (0.8.0)
> hashie (3.4.4)
> highline (1.7.8)
> iniparse (1.4.2)
> io-console (0.4.5)
> ipaddress (0.8.3)
> json (1.8.3)
> minitest (5.10.2)
> mixlib-archive (0.2.0)
> mixlib-authentication (1.4.1)
> mixlib-cli (1.7.0)
> mixlib-config (2.2.1)
> mixlib-log (1.7.1)
> mixlib-shellout (2.2.6)
> molinillo (0.5.0)
> multi_json (1.12.1)
> net-http-persistent (2.9.4)
> net-scp (1.2.1)
> net-sftp (2.1.2)
> net-ssh (4.1.0)
> net-ssh-gateway (1.2.0)
> net-ssh-multi (1.2.1)
> net-telnet (0.1.1)
> ohai (8.21.0)
> plist (3.2.0)
> power_assert (0.2.7)
> proxifier (1.0.3)
> psych (2.1.0)
> rack (1.6.4)
> rake (12.0.0)
> rbnacl (5.0.0)
> rdoc (4.2.1)
> rspec (3.5.0)
> rspec-core (3.5.3)
> rspec-expectations (3.5.0)
> rspec-its (1.2.0)
> rspec-mocks (3.5.0)
> rspec-support (3.5.0)
> serverspec (2.37.2)
> specinfra (2.66.0)
> syslog-logger (1.6.8)
> systemu (2.6.5)
> test-unit (3.2.5)
> thor (0.19.4)
> thread_order (1.1.0)
> uuidtools (2.1.5)
> ERROR: Test "ruby2.3" failed.

The full build log is available from:
   http://aws-logs.debian.net/2017/07/21/chef_12.14.60-2_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.



Bug#869174: ruby-net-sftp: FTBFS: ERROR: Test "ruby2.3" failed: => 142: assert_raises(ArgumentError) { sftp.download("/path/to/remote", StringIO.new, :recursive => true) }

2017-07-21 Thread Lucas Nussbaum
Source: ruby-net-sftp
Version: 1:2.1.2-3
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170721 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
>   => 142: assert_raises(ArgumentError) { sftp.download("/path/to/remote", 
> StringIO.new, :recursive => true) }
>  143:   end
>  144: 
>  145:   private
> 
>  expected but was
> )>
> 
> diff:
> ? ArgumentError
> ? Typ  ()
> ===
> : (0.006559)
> test_download_directory_with_progress_should_report_progress:.: (0.008648)
> test_download_file_should_transfer_remote_to_local:   .: (0.005581)
> test_download_file_should_transfer_remote_to_local_buffer:.: (0.005837)
> 
> test_download_file_should_transfer_remote_to_local_in_spite_of_fragmentation:.:
>  (0.003106)
> test_download_large_file_should_handle_too_large_read_size:.: (0.009755)
> test_download_large_file_should_transfer_remote_to_local:.: (0.017387)
> test_download_large_file_with_progress_should_report_progress:.: 
> (0.007272)
>   FileFactoryTest: 
> test_directory_should_be_false_for_non_directory: .: (0.000422)
> test_directory_should_be_true_for_directory:  .: (0.000312)
> test_open_with_block_should_close_file_even_if_exception_is_raised:.: 
> (0.000386)
> test_open_with_block_should_yield_and_close_handle:   .: (0.000339)
> test_open_without_block_should_return_new_file:   .: (0.000327)
>   FileOperationsTest: 
> test_close_should_close_handle_and_set_handle_to_nil:.: (0.000314)
> test_eof_should_be_false_if_at_eof_but_data_remains_in_buffer:.: 
> (0.000202)
> test_eof_should_be_true_if_at_eof_and_no_data_in_buffer:.: (0.000209)
> test_gets_at_EOF_should_return_nil:   .: (0.000218)
> test_gets_when_no_such_delimiter_exists_in_stream_should_read_to_EOF:.: 
> (0.000220)
> test_gets_with_argument_should_read_until_first_instance_of_argument:.: 
> (0.000217)
> test_gets_with_empty_argument_should_read_until_double_dollar_fslash:.: 
> (0.000220)
> test_gets_without_argument_should_read_until_first_dollar_fslash:.: 
> (0.000220)
> test_pos_assignment_should_reset_eof: .: (0.000213)
> test_pos_assignment_should_set_position:  .: (0.000105)
> test_print_with_arguments_should_write_all_arguments:.: (0.000326)
> 
> test_print_with_no_arguments_should_write_dollar_bslash_if_dollar_bslash_is_not_nil:.:
>  (0.000190)
> 
> test_print_with_no_arguments_should_write_nothing_if_dollar_bslash_is_nil:.: 
> (0.000206)
> test_puts_should_not_append_newline_if_argument_ends_in_newline:.: 
> (0.000479)
> test_puts_should_recursively_puts_array_arguments:.: (0.002200)
> test_read_after_pos_assignment_should_read_from_specified_position:.: 
> (0.000223)
> test_read_with_argument_should_read_and_return_n_bytes_and_set_pos:.: 
> (0.000206)
> 
> test_read_without_argument_should_read_and_return_remainder_of_file_and_set_pos:.:
>  (0.000212)
> test_readline_should_raise_exception_on_EOF:  .: (0.000238)
> test_stat_should_return_attributes_object_for_handle:.: (0.000211)
> test_write_after_pos_assignment_should_write_at_position:.: (0.000203)
> test_write_should_write_data_and_increment_pos_and_return_data_length:.: 
> (0.000213)
>   PacketTest: 
> test_packet_should_auto_read_type_byte:   .: (0.000196)
>   Protocol::TestBase: 
> test_parse_with_attrs_packet_should_delegate_to_parse_attrs_packet:.: 
> (0.000537)
> test_parse_with_data_packet_should_delegate_to_parse_data_packet:.: 
> (0.000821)
> test_parse_with_handle_packet_should_delegate_to_parse_handle_packet:.: 
> (0.000513)
> test_parse_with_name_packet_should_delegate_to_parse_name_packet:.: 
> (0.000389)
> test_parse_with_status_packet_should_delegate_to_parse_status_packet:.: 
> (0.000390)
> test_parse_with_unknown_packet_should_raise_exception:.: (0.000295)
>   Protocol::V01::TestAttributes: 
> test_attributes_to_s_should_build_binary_representation:.: (0.000273)
> 
> test_attributes_to_s_should_build_binary_representation_when_subset_is_present:.:
>  (0.000124)
> 
> test_attributes_to_s_with_owner_and_group_should_translate_to_uid_and_gid:.: 
> (0.000715)
> 
> test_from_buffer_should_correctly_parse_buffer_and_return_attribute_object:.: 
> (0.000216)
> 
> test_from_buffer_should_correctly_parse_buff

Bug#869175: ruby-specinfra: FTBFS: can't satisfy 'net-ssh (< 4.0, >= 2.7)', already activated 'net-ssh-4.1.0' (Gem::LoadError)

2017-07-21 Thread Lucas Nussbaum
Source: ruby-specinfra
Version: 2.66.0-1
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170721 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
> Invalid gemspec in [specinfra.gemspec]: No such file or directory - git
> GEM_PATH=debian/ruby-specinfra/usr/share/rubygems-integration/all:/var/lib/gems/2.3.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.3.0:/usr/share/rubygems-integration/2.3.0:/usr/share/rubygems-integration/all
>  ruby2.3 -e gem\ \"specinfra\"
> /usr/lib/ruby/2.3.0/rubygems/specification.rb:1436:in `block in 
> activate_dependencies': can't satisfy 'net-ssh (< 4.0, >= 2.7)', already 
> activated 'net-ssh-4.1.0' (Gem::LoadError)
>   from /usr/lib/ruby/2.3.0/rubygems/specification.rb:1428:in `each'
>   from /usr/lib/ruby/2.3.0/rubygems/specification.rb:1428:in 
> `activate_dependencies'
>   from /usr/lib/ruby/2.3.0/rubygems/specification.rb:1410:in `activate'
>   from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_gem.rb:68:in `block 
> in gem'
>   from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_gem.rb:67:in 
> `synchronize'
>   from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_gem.rb:67:in `gem'
>   from -e:1:in `'
> bcrypt_pbkdf (1.0.0)
> bigdecimal (1.2.8)
> bundler (1.15.1)
> did_you_mean (1.0.0)
> diff-lcs (1.3)
> ffi (1.9.10)
> io-console (0.4.5)
> json (1.8.3)
> minitest (5.10.2)
> molinillo (0.5.0)
> net-http-persistent (2.9.4)
> net-scp (1.2.1)
> net-ssh (4.1.0)
> net-telnet (0.1.1)
> power_assert (0.2.7)
> psych (2.1.0)
> rake (12.0.0)
> rbnacl (5.0.0)
> rdoc (4.2.1)
> rspec (3.5.0)
> rspec-core (3.5.3)
> rspec-expectations (3.5.0)
> rspec-its (1.2.0)
> rspec-mocks (3.5.0)
> rspec-support (3.5.0)
> test-unit (3.2.5)
> thor (0.19.4)
> thread_order (1.1.0)
> ERROR: Test "ruby2.3" failed: 

The full build log is available from:
   http://aws-logs.debian.net/2017/07/21/ruby-specinfra_2.66.0-1_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.



Bug#866120: diffoscope: please add an xml comparator

2017-07-21 Thread Chris Lamb
tags 866120 + pending
thanks

Chris Lamb wrote:

> Woo, thanks! First, am going to merge this into the existing
> wishlist bug…

… And I've now also merged the code into our Git repo. Thanks!

I did make some changes after committing which might be useful
to know/understand for next time. First two (easy) style fixups
that should be fairly self-explanatory:

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

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

Next, I had to add MissingFile support to your comparator; did you run
the entire testsuite? *g*  In particular, the epub tests were failing
for me before I added:

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

Anyway, thank you again for your contribution. Let me know if you have
any questions on the above, but we all look forward to future patches
from yourself…


Best wishes,

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



Bug#869180: src:hydrogen-drumkits: source contains unlicensed material (bogusly treated as GPL-2)

2017-07-21 Thread Jonas Smedegaard
Package: src:hydrogen-drumkits
Version: 2015.09.28-1
Severity: serious
Justification: Policy 2.2.1

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

These drumkits are in upstream metadata listed _without_ license:

ColomboAcousticDrumkit (sf)
EasternHop (sf)
Electric Empire (sf)
HardElectro (sf)
HipHop-1 (sf)
HipHop-2 (sf)
Millo's MultiLayered 2 (sf)
Synthie-1 (sf)
VariBreaks (sf)

In Debian copyright file those are listed as licensed GPL-2.

 - Jonas

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAllxzkMACgkQLHwxRsGg
ASElKBAApwwOF1ii7YQvV3qaTvt6MwfMUkARW4+FII9CEsqf2UQEbNUwm7oN07jL
4faAXhQ94Xdb1NwmTKmq82QmmD9y8MuaEps8EvfLn5cvML21+54Kwr5upt8uEnF+
wKFKD/6nRqab8qGnu0u6cryGKFLE6jyV7dEGYrh4NB0DKcpv6f322c970v9p9wqK
tx8hBklGm+cWH9aZ/91avuAQJQ/wLhEESKohWTGfUSWQJn6bw0gEgqw+xI1QCi04
L+6brY7cck5T0ZomebDOfCcm05fshBsi7XuYxL4WnVtDGcwiDWkhEvTIDXcVPUbN
WzVyhn78e1aCtZ5wGT73OmaJXMhHzM1N3dRxg9JY+uB2I6uA65bxIj6EAkxXDMge
3lZUgO6ETSQS250AH4k2jcEMC6FPIK/KEEI7iWWa/7jIvT7uhM3cchs2fQZXxFLy
EgL2RCn/sGtPHvaefCyMNYFPhZDcGYPeGCONKPzg9y+K35iihc7BM0KmVwHSUQ9r
ScaUdOuUWUg9RocpAEKbVTxkn5E0ygrtH7eIb/GBK/qJVoRh1+xKOjp9BqYgHVHe
eGsEvSV1WIACzc3XU8uLa0NmInPbSGtKNMGbfT7MCrrtwtSSEFsuoHL4pRcibs1v
Z3ooVdnfz9K4Serzd4+o2+2E9ZBrpyQ9L3CDuLlHwEV0Hkn1lSM=
=YS/0
-END PGP SIGNATURE-



Bug#869181: librospack-dev: Incorrect libtinyxml dependency

2017-07-21 Thread Adrian Bunk
Package: librospack-dev
Version: 2.4.1-1
Severity: serious
Control: affects -1 src:ros-pluginlib src:ros-resource-retriever

$ pkg-config --libs rospack
-lrospack -l:/usr/lib/x86_64-linux-gnu/libpython2.7.so 
-l:/usr/lib/x86_64-linux-gnu/libboost_filesystem.so 
-l:/usr/lib/x86_64-linux-gnu/libboost_program_options.so 
-l:/usr/lib/x86_64-linux-gnu/libboost_system.so 
-l:/usr/lib/x86_64-linux-gnu/libtinyxml2.so
$

libtinyxml2.so is in libtinyxml2-dev, but librospack-dev
still depends on libtinyxml-dev.



Bug#869180: src:hydrogen-drumkits: source contains unlicensed material (bogusly treated as GPL-2)

2017-07-21 Thread James Cowgill
Hi,

On 21/07/17 10:49, Jonas Smedegaard wrote:
> Package: src:hydrogen-drumkits
> Version: 2015.09.28-1
> Severity: serious
> Justification: Policy 2.2.1
> 
> These drumkits are in upstream metadata listed _without_ license:
> 
> ColomboAcousticDrumkit (sf)
> EasternHop (sf)
> Electric Empire (sf)
> HardElectro (sf)
> HipHop-1 (sf)
> HipHop-2 (sf)
> Millo's MultiLayered 2 (sf)
> Synthie-1 (sf)
> VariBreaks (sf)
> 
> In Debian copyright file those are listed as licensed GPL-2.

The fact that the metadata doesn't contain a license, does not imply
that these files are not GPL-2. Have you actually checked the license of
any of these?

For instance, a brief google search seems to indicate that the first one
on your list (ColomboAcousticDrumkit) is GPL-2 licensed:
http://freepats.zenvoid.org/Percussion/acoustic-drum-kit.html

James



signature.asc
Description: OpenPGP digital signature


Bug#869182: php-common: Trouble running phpsessionclean.service on a LXC Container...

2017-07-21 Thread Marco Gaiarin
Package: php-common
Version: 1:49
Severity: normal


I've setup a LXC stretch container in a Proxmox virtualization cluster, and
after installing apache/PHP i've start to have in logs of the container rows
like:

 Jul 21 10:09:14 vglpi systemd[1]: phpsessionclean.service: Failed to reset 
devices.list: Operation not permitted
 Jul 21 10:09:14 vglpi systemd[24929]: phpsessionclean.service: Failed at step 
NETWORK spawning /usr/lib/php/sessionclean: Permission denied
 Jul 21 10:09:14 vglpi systemd[1]: phpsessionclean.service: Main process 
exited, code=exited, status=225/NETWORK
 Jul 21 10:09:14 vglpi systemd[1]: Failed to start Clean php session files.
 Jul 21 10:09:14 vglpi systemd[1]: phpsessionclean.service: Unit entered failed 
state.
 Jul 21 10:09:14 vglpi systemd[1]: phpsessionclean.service: Failed with result 
'exit-code'.
 Jul 21 10:39:14 vglpi systemd[1]: phpsessionclean.service: Failed to reset 
devices.list: Operation not permitted
 Jul 21 10:39:14 vglpi systemd[24948]: phpsessionclean.service: Failed at step 
NETWORK spawning /usr/lib/php/sessionclean: Permission denied
 Jul 21 10:39:14 vglpi systemd[1]: phpsessionclean.service: Main process 
exited, code=exited, status=225/NETWORK
 Jul 21 10:39:14 vglpi systemd[1]: Failed to start Clean php session files.
 Jul 21 10:39:14 vglpi systemd[1]: phpsessionclean.service: Unit entered failed 
state.
 Jul 21 10:39:14 vglpi systemd[1]: phpsessionclean.service: Failed with result 
'exit-code'.

and, on the same time, on the host that run the container:

 Jul 21 10:09:14 tessier kernel: [22515856.189072] audit: type=1400 
audit(1500624554.627:384): apparmor="DENIED" operation="file_lock" 
profile="lxc-container-default-cgns" pid=20780 comm="(ionclean)" family="unix" 
sock_type="dgram" protocol=0 addr=none
 Jul 21 10:09:14 tessier kernel: [22515856.189077] audit: type=1400 
audit(1500624554.627:385): apparmor="DENIED" operation="file_lock" 
profile="lxc-container-default-cgns" pid=20780 comm="(ionclean)" family="unix" 
sock_type="dgram" protocol=0 addr=none
 Jul 21 10:09:14 tessier kernel: [22515856.189082] audit: type=1400 
audit(1500624554.627:386): apparmor="DENIED" operation="file_lock" 
profile="lxc-container-default-cgns" pid=20780 comm="(ionclean)" family="unix" 
sock_type="dgram" protocol=0 addr=none
 Jul 21 10:09:14 tessier kernel: [22515856.189085] audit: type=1400 
audit(1500624554.627:387): apparmor="DENIED" operation="file_lock" 
profile="lxc-container-default-cgns" pid=20780 comm="(ionclean)" family="unix" 
sock_type="dgram" protocol=0 addr=none
 Jul 21 10:39:14 tessier kernel: [22517656.161803] audit: type=1400 
audit(1500626354.625:388): apparmor="DENIED" operation="file_lock" 
profile="lxc-container-default-cgns" pid=23425 comm="(ionclean)" family="unix" 
sock_type="dgram" protocol=0 addr=none
 Jul 21 10:39:14 tessier kernel: [22517656.161808] audit: type=1400 
audit(1500626354.625:389): apparmor="DENIED" operation="file_lock" 
profile="lxc-container-default-cgns" pid=23425 comm="(ionclean)" family="unix" 
sock_type="dgram" protocol=0 addr=none
 Jul 21 10:39:14 tessier kernel: [22517656.161812] audit: type=1400 
audit(1500626354.625:390): apparmor="DENIED" operation="file_lock" 
profile="lxc-container-default-cgns" pid=23425 comm="(ionclean)" family="unix" 
sock_type="dgram" protocol=0 addr=none
 Jul 21 10:39:14 tessier kernel: [22517656.161815] audit: type=1400 
audit(1500626354.625:391): apparmor="DENIED" operation="file_lock" 
profile="lxc-container-default-cgns" pid=23425 comm="(ionclean)" family="unix" 
sock_type="dgram" protocol=0 addr=none

I've tried to run the script by hand, as root, and no error appears
(on container and on host).

For now, i've disabled the service:

root@vglpi:~# systemctl disable phpsessionclean


Thanks.

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

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

Versions of packages php-common depends on:
ii  init-system-helpers  1.48
ii  psmisc   22.21-2.1+b2
ii  sed  4.4-1

php-common recommends no packages.

php-common suggests no packages.

-- no debconf information



Bug#864603: gufw does not launch

2017-07-21 Thread Leandro Noferini
Package: gufw
Version: 17.04.1-1.1
Followup-For: Bug #864603

I can confirm this bug.

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

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

Versions of packages gufw depends on:
ii  gir1.2-gtk-3.0  3.22.16-1
ii  gir1.2-webkit2-4.0  2.16.5-1
ii  net-tools   1.60+git20161116.90da8a0-1
ii  policykit-1 0.105-18
ii  python3 3.5.3-3
ii  python3-gi  3.22.0-2+b1
ii  ufw 0.35-4

gufw recommends no packages.

gufw suggests no packages.

-- no debconf information


signature.asc
Description: PGP signature


Bug#869183: puppet: Fix "No supported formats are acceptable (Accept: s, pson)" while bucketing from Puppet Agent v3

2017-07-21 Thread Mathieu Parent
Package: puppet
Version: 4.10.4-2
Severity: important

Dear Maintainer,

With the following code in site.pp or similar:

  filebucket { 'main':
path => false, # Remote filebucket
  }
  File {
backup => 'main',
  }

Bucketing fails from puppet3 agent to puppet master 4 (stretch/sid) with:
  Error: Could not back up /etc/puppet/auth.conf: Error 406 on SERVER:
{"message":"Not Acceptable: No supported formats are acceptable
(Accept: s, pson)","issue_kind":"UNSUPPORTED_FORMAT"}

The attached patch fixes this and matches the behavior of:
https://github.com/puppetlabs/puppetserver/blob/ff0e5e84860ea9b035839e77e9b27d4c3a923e36/src/clj/puppetlabs/services/legacy_routes/legacy_routes_core.clj#L27-L42

NB: I think this should also go in stretch-pu.

Regards

Mathieu Parent
From eb03e3dcaad385660bf95d692c9bd5acbb8996ea Mon Sep 17 00:00:00 2001
From: Mathieu Parent 
Date: Fri, 21 Jul 2017 12:16:28 +0200
Subject: [PATCH] Fix "No supported formats are acceptable (Accept: s, pson)"
 while bucketing from Puppet Agent v3

---
 debian/patches/0001-Adjust-default-paths.patch |  4 +-
 .../0004-add-puppet3-compat-middleware.patch   | 10 ++---
 ...e-systemd-as-the-default-service-provider.patch | 19 
 .../0006-debian-service-provider-use-service.patch | 18 +---
 ...vice-listing-and-enable-disable-in-Debian.patch | 52 +++---
 debian/patches/0008-fix-locale-loading.patch   | 16 ---
 6 files changed, 67 insertions(+), 52 deletions(-)

diff --git a/debian/patches/0001-Adjust-default-paths.patch b/debian/patches/0001-Adjust-default-paths.patch
index 1bc3df858..de7b33ea8 100644
--- a/debian/patches/0001-Adjust-default-paths.patch
+++ b/debian/patches/0001-Adjust-default-paths.patch
@@ -8,10 +8,10 @@ Subject: Adjust default paths
  2 files changed, 6 insertions(+), 6 deletions(-)
 
 diff --git a/lib/puppet/defaults.rb b/lib/puppet/defaults.rb
-index f63a08a..f76ce1e 100644
+index 8669913..d41d9be 100644
 --- a/lib/puppet/defaults.rb
 +++ b/lib/puppet/defaults.rb
-@@ -1206,7 +1206,7 @@ EOT
+@@ -1250,7 +1250,7 @@ EOT
:desc   => "File that provides mapping between custom SSL oids and user-friendly names"
  },
  :basemodulepath => {
diff --git a/debian/patches/0004-add-puppet3-compat-middleware.patch b/debian/patches/0004-add-puppet3-compat-middleware.patch
index 04b6f3f53..33117629e 100644
--- a/debian/patches/0004-add-puppet3-compat-middleware.patch
+++ b/debian/patches/0004-add-puppet3-compat-middleware.patch
@@ -4,10 +4,11 @@ Description: Add Puppet 3 client compatibility under rack
  per[1]. This should restore compatibility with Puppet 3 clients when
  run under any rack-enabled server (including Passenger).
 Forwarded: no (deprecated upstream)
-Last-Update: 2017-01-11
+Last-Update: 2017-07-21
+
 --- a/ext/rack/config.ru
 +++ b/ext/rack/config.ru
-@@ -25,6 +25,74 @@
+@@ -25,6 +25,73 @@
  # delivered during catalog compilation.
  ARGV << "--always_cache_features"
  
@@ -62,9 +63,8 @@ Last-Update: 2017-01-11
 +  env['QUERY_STRING'] = Rack::Utils.build_query(@req.params)
 +end
 +
-+if @api =~ /^file_(content|bucket_file)/ && @req.get?
-+  env["HTTP_ACCEPT"] = "binary"
-+elsif @api == "file_bucket_file" && (@req.post? || @req.put?)
++env["HTTP_ACCEPT"] = env["HTTP_ACCEPT"].split(/\s*,\s*/).map { |a| a.sub(/^raw|s$/, 'binary') }.join(', ')
++if @api == "file_bucket_file" && (@req.post? || @req.put?)
 +  env["CONTENT_TYPE"] = "application/octet-stream"
 +end
 +
diff --git a/debian/patches/0005-use-systemd-as-the-default-service-provider.patch b/debian/patches/0005-use-systemd-as-the-default-service-provider.patch
index 2871e72ae..d4bc82698 100644
--- a/debian/patches/0005-use-systemd-as-the-default-service-provider.patch
+++ b/debian/patches/0005-use-systemd-as-the-default-service-provider.patch
@@ -1,13 +1,16 @@
-Author: Apollon Oikonomopoulos 
-Description: Mark systemd as the default service provider for Debian
- Currently systemd is marked as the default service provider only for Jessie.
- Instead of extending this to Stretch, mark it as the default for Debian and
- let the provider confinement blacklist systemd if /run/systemd/system does not
- exist.
-Last-Update: 2017-02-09
+From: Puppet Package Maintainers 
+Date: Fri, 21 Jul 2017 12:12:55 +0200
+Subject: use-systemd-as-the-default-service-provider
+
+---
+ lib/puppet/provider/service/systemd.rb | 4 ++--
+ 1 file changed, 2 insertions(+), 2 deletions(-)
+
+diff --git a/lib/puppet/provider/service/systemd.rb b/lib/puppet/provider/service/systemd.rb
+index 9e09f45..6139341 100644
 --- a/lib/puppet/provider/service/systemd.rb
 +++ b/lib/puppet/provider/service/systemd.rb
-@@ -23,8 +23,8 @@
+@@ -23,8 +23,8 @@ Puppet::Type.type(:service).provide :systemd, :parent => :base do
defaultfor :osfamily => :redhat, :operatingsystem => :fedora
defaultfor :osfamily => :suse
defaultfor :osfamily => :coreos
diff --git a/debian/patches/0006-debian-service-provider-use-service.patch

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

2017-07-21 Thread Mike Gabriel

HI Paul

On  Mi 12 Jul 2017 19:09:59 CEST, draeath wrote:


Thanks Mike.

I'm working on the refactor. It'll take me some time to get it done, but
I've absorbed what it's doing and how to accomplish it with the new
bindings.

As soon as I have it tested and verified to work with the other patches,
I'll send it your way. Will you handle the changes to the control file,
quilt, etc, once you've got it in your hands?

I also noticed an error potentially further down in the as-installed
script, line 1395. urllib is not imported (urllib2 is, and doesn't have a
declaration for _urlopener) and DropboxURLopener isn't declared anywhere
that I can see. I wonder if this is proxy code is even utilized?

One final question. The public key has a URL commented above it. They do
not match currently. Leave the key as is, or include the new public key?

Thanks,
Paul Bransford


Thanks for providing this patch. I have been afk for the last two  
weeks forcefully, due to illness.


Trying to catch up with things now... I'll forward your patch to  
upstream (if they haven't spotted it, yet).


Greets,
Mike
--

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

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



pgpto0_oPFmqh.pgp
Description: Digitale PGP-Signatur


Bug#869184: dpkg: source uploads including _amd64.buildinfo cause problems

2017-07-21 Thread Ansgar Burchardt
Package: dpkg
Version: 1.18.24
Severity: important

source-only uploads sometimes include a _amd64.buildinfo (or other
architecture).  This sometimes causes problems as the amd64 buildd
upload will include a file using the same name.

In particular, it breaks any uploads going to policy queues
(e.g. security's embargoed, proposed-updates) and the sync of uploads
from security-master to ftp-master.

The same is true for maintainer source+all uploads: if the source also
builds arch-indep binaries, the .buildinfo files from maintainer and
buildd might end using the same name.

Please don't include _amd64.buildinfo in source-only or source+all
uploads.  Just changing the name is enough to make me happy
(e.g. _source.buildinfo).

It might also be worth having an option to change the suffix of all
such names (.changes, .buildinfo) easily so that buildds could use
_${arch}-buildd.changes or something.

Ansgar



Bug#869180: src:hydrogen-drumkits: source contains unlicensed material (bogusly treated as GPL-2)

2017-07-21 Thread Jonas Smedegaard
Control: retitle -1 src:hydrogen-drumkits: Some sources lack licensing

Quoting James Cowgill (2017-07-21 11:56:15)
> On 21/07/17 10:49, Jonas Smedegaard wrote:
> > Package: src:hydrogen-drumkits
> > Version: 2015.09.28-1
> > Severity: serious
> > Justification: Policy 2.2.1
> > 
> > These drumkits are in upstream metadata listed _without_ license:
> > 
> > ColomboAcousticDrumkit (sf)
> > EasternHop (sf)
> > Electric Empire (sf)
> > HardElectro (sf)
> > HipHop-1 (sf)
> > HipHop-2 (sf)
> > Millo's MultiLayered 2 (sf)
> > Synthie-1 (sf)
> > VariBreaks (sf)
> > 
> > In Debian copyright file those are listed as licensed GPL-2.
> 
> The fact that the metadata doesn't contain a license, does not imply 
> that these files are not GPL-2. Have you actually checked the license 
> of any of these?

The issue here is that information about licensing is unavailable in the 
source package.  Title now rephrased to not avoid assumption.

If licensing is based on external information and/or guesswork, then 
that should be documented in debian/copyright.


> For instance, a brief google search seems to indicate that the first one
> on your list (ColomboAcousticDrumkit) is GPL-2 licensed:
> http://freepats.zenvoid.org/Percussion/acoustic-drum-kit.html

Thanks for the valuable info - now added to debian/copyright.

Do you have similar info for the other sources?


 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private


signature.asc
Description: signature


Bug#869121: ITP: dragonfire -- Dragonfire is an open source virtual assistant project for Debian based Linux distributions

2017-07-21 Thread Jonas Smedegaard
Quoting Mehmet Mert Yildiran (2017-07-20 19:26:04)
> * Package name: dragonfire
>   Version : 0.9.5
>   Upstream Author : Mehmet Mert Yildiran 
> * URL : https://github.com/DragonComputer/Dragonfire
> * License : MIT
>   Programming Lang: Python, C
>   Description : Dragonfire is an open source virtual assistant project for
> Debian based Linux distributions
> 
> Please take a look at these documentation files to get further information:
> https://github.com/DragonComputer/Dragonfire/blob/master/README.md
> https://github.com/DragonComputer/Dragonfire/blob/master/CONTRIBUTING.md

The long description should _contain_ description, not refer to it.  So 
please write (e.g. based on those online references) more elaborate what 
the package does, in the long description for the package.

Kind regards, and thanks for your packaging effort!

 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private


signature.asc
Description: signature


Bug#866762: gpsprune: FTBFS with metadata-extractor 2.10.1

2017-07-21 Thread Markus Koschany
On Mon, 3 Jul 2017 23:42:27 +0200 Markus Koschany  wrote:
> Am 03.07.2017 um 23:34 schrieb Sebastiaan Couwenberg:
> [...]
> > 
> > When are you planning to move libmetadata-extractor-java to unstable?
> > 
> > I've applied your patch in git, and added my own to disable the
> > thumbnail support.
> > 
> > The package is ready for upload to unstable. Please let me know when
> > you've moved libmetadata-extractor-java to unstable.
> 
> Hi Bas,
> 
> I am waiting for the FTP team to process all new dependencies for
> pdfsam. As soon as the whole stack is in unstable we are ready to go.
> I'll ping you and then it should be safe to upload the new revision of
> gpsprune. Thanks for your quick response!

I have just uploaded libmetadata-extractor-java 2.10.1 to unstable. It
should be available on the mirrors in a few hours.

Cheers,

Markus






signature.asc
Description: OpenPGP digital signature


Bug#869185: /usr/share/texlive/texmf-dist/scripts/texdoctk/texdoctk.pl: kpsewhich cannot find the configuration file, texdoctk dies

2017-07-21 Thread boffi
Package: texlive-base
Version: 2017.20170629-1
Severity: normal
File: /usr/share/texlive/texmf-dist/scripts/texdoctk/texdoctk.pl

Dear Maintainer,

I started texdoctk from the command line, a dialog popped out stating

Couldn't open system-wide default config file texdocrc.defaults

and the only possible action consisted in a button that, clicked, closed
the program.

The problem lies in the following line, line 73 in /usr/bin/texdoctk

my $sysrc=`kpsewhich --progname=texdoctk --format=${qq}other text 
files${qq} ${TeXDocRcDefaults}`;

When I try, from the command line, the equivalent(?) command

$ kpsewhich --progname=texdoctk --format='other text files' 
texdocrc.defaults

all I get is nothing, i.e., kpsewhich cannot tell the location of
texdocrc.defaults file (it's in /etc/texmf/texdoctk/texdocrc.defaults
but you know that).

As a temporary measure I simply hardwired the actual location of the
configuration file into the executable script, because I have always
kept myself away from everything kpathsea related ...

Thank you in advance,
  gb
##
 List of ls-R files

-rw-r--r-- 1 root root 2513 Jul 19 09:34 /var/lib/texmf/ls-R
lrwxrwxrwx 1 root root 29 Jun 24 14:20 /usr/share/texmf/ls-R -> 
/var/lib/texmf/ls-R-TEXMFMAIN
lrwxrwxrwx 1 root root 31 Jun 29 04:30 /usr/share/texlive/texmf-dist/ls-R -> 
/var/lib/texmf/ls-R-TEXLIVEDIST
lrwxrwxrwx 1 root root 31 Jun 29 04:30 /usr/share/texlive/texmf-dist/ls-R -> 
/var/lib/texmf/ls-R-TEXLIVEDIST
##
 Config files
lrwxrwxrwx 1 root root 40 Jun 29 04:30 /usr/share/texmf/web2c/texmf.cnf -> 
../../texlive/texmf-dist/web2c/texmf.cnf
lrwxrwxrwx 1 root root 33 Jun 29 04:30 /usr/share/texmf/web2c/fmtutil.cnf -> 
/var/lib/texmf/fmtutil.cnf-DEBIAN
lrwxrwxrwx 1 root root 32 Jun 29 04:30 /usr/share/texmf/web2c/updmap.cfg -> 
/var/lib/texmf/updmap.cfg-DEBIAN
-rw-r--r-- 1 root root 4359 Jul 19 09:33 
/var/lib/texmf/tex/generic/config/language.dat
##
 Files in /etc/texmf/web2c/
total 8
-rw-r--r-- 1 root root 283 Oct 14  2015 mktex.cnf
-rw-r--r-- 1 root root 475 Jun 30 16:19 texmf.cnf
##
 md5sums of texmf.d
ca40c66f144b4bafc3e59a2dd32ecb9c  /etc/texmf/texmf.d/00debian.cnf

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

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

Versions of packages texlive-base depends on:
ii  debconf   1.5.63
ii  libpaper-utils1.1.24+nmu5
ii  tex-common6.07
ii  texlive-binaries  2017.20170613.44572-3
ii  ucf   3.0036
ii  xdg-utils 1.1.1-1

Versions of packages texlive-base recommends:
ii  lmodern  2.004.5-3

Versions of packages texlive-base suggests:
ii  evince [postscript-viewer]   3.22.1-4
ii  ghostscript [postscript-viewer]  9.21~dfsg-1
ii  gv [postscript-viewer]   1:3.7.4-1+b1
ii  mupdf [pdf-viewer]   1.9a+ds1-4
ii  perl-tk  1:804.033-2
ii  xpdf [pdf-viewer]3.04-4

Versions of packages tex-common depends on:
ii  dpkg  1.18.24
ii  ucf   3.0036

Versions of packages tex-common suggests:
ii  debhelper  10.6.4

Versions of packages texlive-base is related to:
ii  tex-common6.07
ii  texlive-binaries  2017.20170613.44572-3

-- debconf information:
  texlive-base/binary_chooser: pdftex, dvips, dvipdfmx, xdvi
  texlive-base/texconfig_ignorant:



Bug#866120: diffoscope: please add an xml comparator

2017-07-21 Thread Juliana Rodrigues
Hi Chris!

I see. I'll be more careful with python coding style
next time. (:

About the testsuite: Firstly I ran all tests, but some were naturally
failing (like test_debian, I guess). Then I focused on getting to work at
least the one test I was writting, since I don't know much about the
project yet.

Thank you very much for your support and for your quick fixes. I hope to be
able to contribute more in the future. :D

Juliana




Em sex, 21 de jul de 2017 06:48, Chris Lamb  escreveu:

> tags 866120 + pending
> thanks
>
> Chris Lamb wrote:
>
> > Woo, thanks! First, am going to merge this into the existing
> > wishlist bug…
>
> … And I've now also merged the code into our Git repo. Thanks!
>
> I did make some changes after committing which might be useful
> to know/understand for next time. First two (easy) style fixups
> that should be fairly self-explanatory:
>
>
> https://anonscm.debian.org/git/reproducible/diffoscope.git/commit/?id=9d89fdda0101915eedf931a4c9127918cdfea79c
>
>
> https://anonscm.debian.org/git/reproducible/diffoscope.git/commit/?id=9123eb091c49db4d7685e36d33f539bcbecefae1
>
> Next, I had to add MissingFile support to your comparator; did you run
> the entire testsuite? *g*  In particular, the epub tests were failing
> for me before I added:
>
>
> https://anonscm.debian.org/git/reproducible/diffoscope.git/commit/?id=2422e0f0f8a8ae66da0438f9fc64376faa154b53
>
> Anyway, thank you again for your contribution. Let me know if you have
> any questions on the above, but we all look forward to future patches
> from yourself…
>
>
> Best wishes,
>
> --
>   ,''`.
>  : :'  : Chris Lamb, Debian Project Leader
>  `. `'`  la...@debian.org / chris-lamb.co.uk
>`-
>


Bug#869183: Updated patch

2017-07-21 Thread Mathieu Parent
Hello,

Here is an updated patch with comments from Ewoud Kohl van Wijngaarden [1].

[1]: https://github.com/theforeman/puppet-puppet/pull/520#discussion_r128732270

Regards

-- 
Mathieu Parent
From 7e0ef6b59020a96d6736f05efc717442e4f7052a Mon Sep 17 00:00:00 2001
From: Mathieu Parent 
Date: Fri, 21 Jul 2017 12:16:28 +0200
Subject: [PATCH] Fix "No supported formats are acceptable (Accept: s, pson)"
 while bucketing from Puppet Agent v3

---
 debian/patches/0004-add-puppet3-compat-middleware.patch | 10 +-
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/debian/patches/0004-add-puppet3-compat-middleware.patch b/debian/patches/0004-add-puppet3-compat-middleware.patch
index 04b6f3f53..04b72f7d7 100644
--- a/debian/patches/0004-add-puppet3-compat-middleware.patch
+++ b/debian/patches/0004-add-puppet3-compat-middleware.patch
@@ -4,10 +4,11 @@ Description: Add Puppet 3 client compatibility under rack
  per[1]. This should restore compatibility with Puppet 3 clients when
  run under any rack-enabled server (including Passenger).
 Forwarded: no (deprecated upstream)
-Last-Update: 2017-01-11
+Last-Update: 2017-07-21
+
 --- a/ext/rack/config.ru
 +++ b/ext/rack/config.ru
-@@ -25,6 +25,74 @@
+@@ -25,6 +25,73 @@
  # delivered during catalog compilation.
  ARGV << "--always_cache_features"
  
@@ -62,9 +63,8 @@ Last-Update: 2017-01-11
 +  env['QUERY_STRING'] = Rack::Utils.build_query(@req.params)
 +end
 +
-+if @api =~ /^file_(content|bucket_file)/ && @req.get?
-+  env["HTTP_ACCEPT"] = "binary"
-+elsif @api == "file_bucket_file" && (@req.post? || @req.put?)
++env["HTTP_ACCEPT"] = env["HTTP_ACCEPT"].split(/\s*,\s*/).map { |a| a.sub(/^raw|s$/, 'binary') }.uniq.join(', ')
++if @api == "file_bucket_file" && (@req.post? || @req.put?)
 +  env["CONTENT_TYPE"] = "application/octet-stream"
 +end
 +
-- 
2.13.2



Bug#869186: mutt: Install missing required dependencies (libxapian30)

2017-07-21 Thread Boruch Baum
Subject: mutt: Install missing required dependencies (libxapian30)
Package: mutt
Version: 1.7.2-1
Severity: serious

Dear Maintainer,

Upon upgrading `mutt' from the stable to testing repositories, mutt
ceased to function, offering the following error message:

   #+BEGIN_SRC conf
   mutt: symbol lookup error:  /usr/lib/x86_64-linux-gnu/libnotmuch.so.4:
   undefined symbol:
_ZN6Xapian9Compactor26resolve_duplicate_metadataERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEmPS7_
   #+End_SRC

Performing the following fixed the problem for me:

   #+BEGIN_SRC conf
   apt-get install libxapian30

   The following packages will be upgraded:
 libxapian-dev libxapian30 xapian-tools
   #+END_SRC


-- Package-specific info:
NeoMutt 20170113 (1.7.2)
Copyright (C) 1996-2016 Michael R. Elkins and others.
Mutt comes with ABSOLUTELY NO WARRANTY; for details type `mutt -vv'.
Mutt is free software, and you are welcome to redistribute it
under certain conditions; type `mutt -vv' for details.

System: Linux 4.9.0-2-grsec-amd64 (x86_64)
libidn: 1.29 (compiled with 1.33)
hcache backends: tokyocabinet

Compiler:
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/6/lto-wrapper
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Debian 6.3.0-2' 
--with-bugurl=file:///usr/share/doc/gcc-6/README.Bugs 
--enable-languages=c,ada,c++,java,go,d,fortran,objc,obj-c++ --prefix=/usr 
--program-suffix=-6 --program-prefix=x86_64-linux-gnu- --enable-shared 
--enable-linker-build-id --libexecdir=/usr/lib --without-included-gettext 
--enable-threads=posix --libdir=/usr/lib --enable-nls --with-sysroot=/ 
--enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes 
--with-default-libstdcxx-abi=new --enable-gnu-unique-object 
--disable-vtable-verify --enable-libmpx --enable-plugin --enable-default-pie 
--with-system-zlib --disable-browser-plugin --enable-java-awt=gtk 
--enable-gtk-cairo --with-java-home=/usr/lib/jvm/java-1.5.0-gcj-6-amd64/jre 
--enable-java-home --with-jvm-root-dir=/usr/lib/jvm/java-1.5.0-gcj-6-amd64 
--with-jvm-jar-dir=/usr/lib/jvm-exports/java-1.5.0-gcj-6-amd64 
--with-arch-directory=amd64 --with-ecj-jar=/usr/share/java/eclipse-ecj.jar 
--with-target-system-zlib --enable-objc-gc=auto --enable-multiarch 
--with-arch-32=i686 --with-abi=m64 --with-multilib-list=m32,m64,mx32 
--enable-multilib --with-tune=generic --enable-checking=release 
--build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu
Thread model: posix
gcc version 6.3.0 20161229 (Debian 6.3.0-2)

Configure options: '--build=x86_64-linux-gnu' '--prefix=/usr' 
'--includedir=\${prefix}/include' '--mandir=\${prefix}/share/man' 
'--infodir=\${prefix}/share/info' '--sysconfdir=/etc' '--localstatedir=/var' 
'--disable-silent-rules' '--libdir=\${prefix}/lib/x86_64-linux-gnu' 
'--libexecdir=\${prefix}/lib/x86_64-linux-gnu' '--disable-maintainer-mode' 
'--disable-dependency-tracking' '--with-mailpath=/var/mail' 
'--enable-compressed' '--enable-debug' '--enable-fcntl' '--enable-hcache' 
'--enable-gpgme' '--enable-imap' '--enable-smtp' '--enable-pop' 
'--enable-sidebar' '--enable-nntp' '--enable-notmuch' '--disable-fmemopen' 
'--with-curses' '--with-gnutls' '--with-gss' '--with-idn' '--with-mixmaster' 
'--with-sasl' '--without-gdbm' '--without-bdb' '--without-qdbm' 
'--with-tokyocabinet' 'build_alias=x86_64-linux-gnu' 'CFLAGS=-g -O2 
-fdebug-prefix-map=/build/mutt-K2ak0h/mutt-1.7.2=. -fstack-protector-strong 
-Wformat -Werror=format-security' 'LDFLAGS=-Wl,-z,relro -Wl,-z,now' 
'CPPFLAGS=-Wdate-time -D_FORTIFY_SOURCE=2'

Compilation CFLAGS: -Wall -pedantic -Wno-long-long -g -O2 
-fdebug-prefix-map=/build/mutt-K2ak0h/mutt-1.7.2=. -fstack-protector-strong 
-Wformat -Werror=format-security -fno-delete-null-pointer-checks

Compile options:
+CRYPT_BACKEND_CLASSIC_PGP +CRYPT_BACKEND_CLASSIC_SMIME +CRYPT_BACKEND_GPGME
+DEBUG +DL_STANDALONE +ENABLE_NLS -EXACT_ADDRESS -HOMESPOOL -LOCALES_HACK
-SUN_ATTACHMENT +HAVE_BKGDSET +HAVE_COLOR +HAVE_CURS_SET +HAVE_FUTIMENS
+HAVE_GETADDRINFO +HAVE_GETSID +HAVE_ICONV +HAVE_LANGINFO_CODESET
+HAVE_LANGINFO_YESEXPR +HAVE_LIBIDN +HAVE_META +HAVE_REGCOMP +HAVE_RESIZETERM
+HAVE_START_COLOR +HAVE_TYPEAHEAD +HAVE_WC_FUNCS +ICONV_NONTRANS
+USE_COMPRESSED +USE_DOTLOCK +USE_FCNTL -USE_FLOCK -USE_FMEMOPEN -USE_GNU_REGEX
+USE_GSS +USE_HCACHE +USE_IMAP +USE_NOTMUCH +USE_NNTP +USE_POP +USE_SASL
+USE_SETGID +USE_SIDEBAR +USE_SMTP +USE_SSL_GNUTLS -USE_SSL_OPENSSL
-DOMAIN
MIXMASTER="mixmaster"
-ISPELL
SENDMAIL="/usr/sbin/sendmail"
MAILPATH="/var/mail"
PKGDATADIR="/usr/share/mutt"
SYSCONFDIR="/etc"
EXECSHELL="/bin/sh"

patch-attach-headers-color-neomutt
patch-compose-to-sender-neomutt
patch-compress-neomutt
patch-cond-date-neomutt
patch-encrypt-to-self-neomutt
patch-fmemopen-neomutt
patch-forgotten-attachments-neomutt
patch-forwref-neomutt
patch-ifdef-neomutt
patch-index-color-neomutt
patch-initials-neomutt
patch-keywords-neomutt
patch-kyoto-neomutt
patch-limit-curren

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

2017-07-21 Thread Matthias Klose
On 21.07.2017 09:43, Neil Williams wrote:
> On Thu, 20 Jul 2017 22:23:31 +0200
> Matthias Klose  wrote:
> 
>> On 20.07.2017 16:40, 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:  
>>
>> please could you check if it builds with the debug interpreter?
>>
> 
> $ make SPHINXBUILD="python -m pdb 
> /usr/share/sphinx/scripts/python2/sphinx-build" -C doc/v2 html
> make: Entering directory '/home/neil/code/lava/lava-server/doc/v2'
> python -m pdb /usr/share/sphinx/scripts/python2/sphinx-build -b html -d 
> _build/doctrees  -n -j 4 . 

no, not debugging the standard interpreter, but using the debug interpreter,
calling python-dbg



Bug#869132: curvedns: Incomplete debian/copyright?

2017-07-21 Thread Stéphane Neveu
Hi Chris,

Thank you for your review. I had a look at the entire package but I
did not see anything else.
I hope the copyright is fine now :
https://anonscm.debian.org/cgit/pkg-security/curvedns.git/commit/?id=dccc20efc28f4bfbf1d157bedaa46a6d9b56676b

I also used cme update dpkg-copyright command and license-reconcile.

Just tell me if it's ok for you and I'll ask my DD to re-upload it.

Best regards,

Stephane


2017-07-20 20:55 GMT+02:00 Chris Lamb :
> Source: curvedns
> Version: 0.87-1
> Severity: serious
> Justication: Policy 12.5
> X-Debbugs-CC: NEVEU Stephane 
>
> Hi,
>
> I just ACCEPTed curvedns from NEW but noticed it was missing
> attribution in debian/copyright for at least:
>
>   nacl/crypto_scalarmult/curve25519/donna_c64/smult.c
>
>
> (This is not exhaustive so please check over the entire package
> carefully and address these on your next upload.)
>
>
> Regards,
>
> --
>   ,''`.
>  : :'  : Chris Lamb, Debian Project Leader
>  `. `'`  la...@debian.org / chris-lamb.co.uk
>`-



Bug#869187: gnome-online-accounts: Can't integrate Facebook with gnome-online-accounts

2017-07-21 Thread =Sensei1304
Package: gnome-online-accounts
Version: 3.22.5-1
Severity: normal
Tags: upstream

Dear Maintainer,

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

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

*** End of the template - remove these template lines ***
I use Debian 9 with gnome 3.22
Steps to reproduce:
1. Open settings
2. Enter "online accounts".
3. Click on "+" and select Facebook
4. In window that appeared enter the credentials.
5. Click on "Login" button

Actual results:
Window with text "error getting identify: could not parse response" appeared.

Expected results:
Facebook succesfully integrated with gnome.

Additional info:

When I start gnome control-center with G_MESSAGES_DEBUG=all? it shows this:

(gnome-control-center:2715): Json-CRITICAL **: json_object_get_string_member:
assertion 'node != NULL' failed

(gnome-control-center:2715): Json-CRITICAL **: json_object_get_string_member:
assertion 'node != NULL' failed

(gnome-control-center:2715): GoaBackend-WARNING **: Did not find email or
username in JSON data


I tried to logout and login again - result is the same.



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

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

Versions of packages gnome-online-accounts depends on:
ii  libc6 2.24-11+deb9u1
ii  libgcr-base-3-1   3.20.0-5.1
ii  libglib2.0-0  2.50.3-2
ii  libgoa-1.0-0b 3.22.5-1
ii  libgoa-backend-1.0-1  3.22.5-1
ii  libkrb5-3 1.15-1
ii  librest-0.7-0 0.8.0-2
ii  libsoup2.4-1  2.56.0-2
ii  libwebkit2gtk-4.0-37  2.16.3-2

Versions of packages gnome-online-accounts recommends:
ii  dleyna-server 0.4.0-1.1
ii  gnome-control-center  1:3.22.2-3
ii  realmd0.16.3-1

gnome-online-accounts suggests no packages.

-- no debconf information



Bug#869188: notmuch-addrlookup: -dbgsym package is missing actual debug symbols

2017-07-21 Thread David Bremner
Package: notmuch-addrlookup
Version: 8-1
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

% lintian notmuch-addrlookup-dbgsym_8-1_amd64.deb 
W: notmuch-addrlookup-dbgsym: debug-file-with-no-debug-symbols 
usr/lib/debug/.build-id/5e/1619ddb490fa332c710fe60026ab4f1f5dbaae.debug

I think this is because of a missing -g in upstream's CFLAGS, but I didn't 
verify.

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

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

Versions of packages notmuch-addrlookup depends on:
ii  libc6 2.24-12
ii  libglib2.0-0  2.52.3-1
ii  libnotmuch5   0.25~rc0-1

notmuch-addrlookup recommends no packages.

notmuch-addrlookup suggests no packages.

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQGzBAEBCAAdFiEE3VS2dnyDRXKVCQCp8gKXHaSnniwFAllx5E8ACgkQ8gKXHaSn
nixhKQv/fOoLj7OU4jZOkeqyStOmVIodkixt8Xoyg/ZWb3VcnX8noROpwnxLXOks
Tb4OkEPnIcTNgsj/enbGljHP8hkLC4HDe1K/xDfy1tS8ucBRNylVe9K0/uDx/bVj
LwfyMur2g40pG/gfGSmgk8XktCSRbM3eoH2hS+HfbuNJFmjOr2YmaiZChNpKeaL1
fGVdBahUNkJ+FcT0W6Dpnjl4rFIMwe0FDM2bL75KVhQCDZFbHcX8/uAsXfowFOgm
RJiA0JHQPG2WktzJW9ktyWijU4NIb7xPq03RywiYpPYCQleX8RXaLEuiIgFIgQZg
roBkIIb/c2XuoMI8Zj1kZ2qcWsIC8BYwqIjHXe0gwIGS7aXFA7E7qDATNND0K4jn
xUlPGs+ayugNQARhSkKNIFdPM8jjACutlsDHbQJIugAqj/MoKdyjgDqd4OYE//bV
DtJg6BoVxEX1tSbNbv5lTvHY5SkdkUtgn5KifpVKk+kQf4AYttuEyDbm8CovUzrr
aov8mY23
=PZQW
-END PGP SIGNATURE-



Bug#869132: curvedns: Incomplete debian/copyright?

2017-07-21 Thread Chris Lamb

Stéphane, 

Please upload your (built)  package somewhere and I will have a look. 

/lamby

> Hi Chris,
> 
> Thank you for your review. I had a look at the entire package but I
> did not see anything else.
> I hope the copyright is fine now :
> https://anonscm.debian.org/cgit/pkg-security/curvedns.git/commit/?id=dccc20efc28f4bfbf1d157bedaa46a6d9b56676b
> 
> I also used cme update dpkg-copyright command and license-reconcile.
> 
> Just tell me if it's ok for you and I'll ask my DD to re-upload it.
> 
> Best regards,
> 
> Stephane
> 
> 
> 2017-07-20 20:55 GMT+02:00 Chris Lamb :
> > Source: curvedns
> > Version: 0.87-1
> > Severity: serious
> > Justication: Policy 12.5
> > X-Debbugs-CC: NEVEU Stephane 
> >
> > Hi,
> >
> > I just ACCEPTed curvedns from NEW but noticed it was missing
> > attribution in debian/copyright for at least:
> >
> >   nacl/crypto_scalarmult/curve25519/donna_c64/smult.c
> >
> >
> > (This is not exhaustive so please check over the entire package
> > carefully and address these on your next upload.)
> >
> >
> > Regards,
> >
> > --
> >   ,''`.
> >  : :'  : Chris Lamb, Debian Project Leader
> >  `. `'`  la...@debian.org / chris-lamb.co.uk
> >`-


Regards,

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



Bug#865692: Suggested patch

2017-07-21 Thread Dirk Eddelbuettel

On 21 July 2017 at 07:08, Andreas Tille wrote:
| Hi Dirk,
| 
| I stumbled upon this since the Debian Med package tree-puzzle
| is affected.  Wouldn't the patch as easy as
| 
| cd $somewhere && $(MAKE) && cd ..

Sure.

The bigger problem is that SPRNG is really outdated, as is the package itself
(and its packaging).  We have better parallel RNGs now, and those should
probably be used.  So maybe it is time for this package to die ...

Dirk

-- 
http://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org



Bug#869186: [Pkg-mutt-maintainers] Bug#869186: mutt: Install missing required dependencies (libxapian30)

2017-07-21 Thread Evgeni Golov
Hi,

On Fri, Jul 21, 2017 at 07:02:50AM -0400, Boruch Baum wrote:
> Upon upgrading `mutt' from the stable to testing repositories, mutt
> ceased to function, offering the following error message:

There is no mutt 1.7.2-1 in testing. Did you mean upgrading
jessie→stretch?

>#+BEGIN_SRC conf
>mutt: symbol lookup error:  /usr/lib/x86_64-linux-gnu/libnotmuch.so.4:
>undefined symbol:
> _ZN6Xapian9Compactor26resolve_duplicate_metadataERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEmPS7_
>#+End_SRC
> 
> Performing the following fixed the problem for me:
> 
>#+BEGIN_SRC conf
>apt-get install libxapian30
> 
>The following packages will be upgraded:
>  libxapian-dev libxapian30 xapian-tools
>#+END_SRC

¯\_(ツ)_/¯

mutt has a dependency on libnotmuch4, libnotmuch4 has a dependency on
libxapian30, mutt is not using any xapian directly AFAIK.

so we might discuss this as being a not-strong-enough dep between
libnotmuch4 and libxapian30, but not a serios bug in mutt.

> -- System Information:
> Distributor ID:   Devuan
> Description:  Devuan GNU/Linux 1.0 (jessie)
> Release:  1.0
> Codename: jessie
> Architecture: x86_64

Why do you have mutt from stretch on a jessie(-derived) system?



Bug#868958: [Debian-med-packaging] Bug#868958: bcftools FTBFS on 32bit: test failures

2017-07-21 Thread Graham Inggs

On 19/07/2017 23:12, Adrian Bunk wrote:

test_vcf_query:
/<>/bcftools view -Ob /tmp/f0hqBlggDJ/view.filter.vcf.gz | 
/<>/bcftools query -f'%POS %CIGAR\n' -i'strlen(CIGAR[*])=4'
*** Error in `/<>/bcftools': free(): invalid next size (fast): 
0x80abd7a0 ***
/bin/bash: line 1: 11930 Done/<>/bcftools view 
-Ob /tmp/f0hqBlggDJ/view.filter.vcf.gz
  11931 Aborted | /<>/bcftools query -f'%POS 
%CIGAR\n' -i'strlen(CIGAR[*])=4'

Non-zero status 134
.. failed ...
...


The crash in test_vcf_query is already fixed upstream in the following 
commit:


https://github.com/samtools/bcftools/commit/8bfb9d5a94aaab4617bc38cfefa8332729dbd837#diff-f200ee7e516d3b752a03f395b72c8cd5


The two test_vcf_norm failures are caused by the following differing 
output on 32-bit architectures:


--- test/norm.out
+++ test/norm.out.new
@@ -55,4 +55,5 @@
 3  17  .   CA  C   999 PASSINDEL;AN=0 
GT:DP   ./.:0   ./.:0
 4  25  .   T   TT,*999 PASSINDEL;AN=0 
GT:DP   ./.:0   ./.:0
 4  36  .   TC  C,TT,TTC999 PASS 
INDEL;AN=0  GT:DP   ./.:0   ./.:0
+4  37  .   C   I   999 PASSINDEL;AN=0 
GT:DP   ./.:0   ./.:0
 5  21  .   A   AAG 999 PASSINDEL;AN=0 
GT:DP   ./.:0   ./.:0




Bug#869189: ITP: git-annex-remote-rclone -- rclone-based git annex special remote

2017-07-21 Thread Yaroslav Halchenko
Package: wnpp
Severity: wishlist
Owner: Yaroslav Halchenko 

* Package name: git-annex-remote-rclone
  Version : 0.5
  Upstream Author : Daniel Dent 
* URL : https://github.com/DanielDent/git-annex-remote-rclone
* License : GPL
  Programming Lang: bash
  Description : rclone-based git annex special remote

 This is a wrapper around rclone to make any destination supported by rclone
 usable with git-annex.
 .
 Cloud storage providers supported by rclone currently include:
   * Google Drive
   * Amazon S3
   * Openstack Swift / Rackspace cloud files / Memset Memstore
   * Dropbox
   * Google Cloud Storage
   * Microsoft One Drive
   * Hubic
   * Backblaze B2
   * Yandex Disk
 .
 Note: although Amazon Cloud Drive support is implemented, it is broken ATM
 see https://github.com/DanielDent/git-annex-remote-rclone/issues/22 .



Bug#869190: golang-github-minio-cli FTBFS: FAIL: TestFlagsFromEnv

2017-07-21 Thread Adrian Bunk
Source: golang-github-minio-cli
Version: 1.3.0+git20170313.0.8683fa7-1
Severity: serious

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/golang-github-minio-cli.html

...
=== RUN   TestFlagsFromEnv
--- FAIL: TestFlagsFromEnv (0.00s)
flag_test.go:102: expected error could not parse 1.2,2 as int slice 
value for flag seconds: strconv.ParseInt: parsing "1.2": invalid syntax, got 
error could not parse 1.2,2 as int slice value for flag seconds: strconv.Atoi: 
parsing "1.2": invalid syntax
flag_test.go:102: expected error could not parse foobar as int slice 
value for flag seconds: strconv.ParseInt: parsing "foobar": invalid syntax, got 
error could not parse foobar as int slice value for flag seconds: strconv.Atoi: 
parsing "foobar": invalid syntax
...
dh_auto_test: go test -v -p 16 github.com/minio/cli github.com/minio/cli/altsrc 
returned exit code 1
debian/rules:4: recipe for target 'build' failed
make: *** [build] Error 1



Bug#869192: golang-github-pingcap-check FTBFS: FAIL: benchmark_test.go:40: BenchmarkS.TestBenchmark

2017-07-21 Thread Adrian Bunk
Source: golang-github-pingcap-check
Version: 0.0~git20161122.0.9b26663-1
Severity: serious

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/golang-github-pingcap-check.html

...
--
FAIL: benchmark_test.go:40: BenchmarkS.TestBenchmark

benchmark_test.go:60:
c.Assert(output.value, Matches, expected)
... value string = "PASS: check_test.go:144: FixtureHelper.Benchmark1\t 
100\t393348 ns/op\n"
... regex string = "PASS: check_test\\.go:[0-9]+: FixtureHelper\\.Benchmark1\t 
*100\t *[12][0-9]{5} ns/op\n"

OOPS: 129 passed, 1 FAILED
--- FAIL: Test (0.59s)
FAIL
exit status 1
FAILgithub.com/pingcap/check0.598s
dh_auto_test: go test -v -p 15 github.com/pingcap/check returned exit code 1
debian/rules:4: recipe for target 'build' failed
make: *** [build] Error 1



Bug#869191: pristine-tar: pristine-xz failed to reproduce build of ../util-linux_2.30.1.orig.tar.xz

2017-07-21 Thread Andreas Henriksson
Package: pristine-tar
Version: 1.38
Severity: important

Dear Maintainer,

I see there's already many bug reports open that basically contains the
same description I'm about to give below. Not sure how to tell if it's
the same underlying issue though, so reporting yet another one...

I'm setting the severity as important as I can't see any way to work
around this issue (other than stop using pristine-tar), which means
I can't update the packaging of the sources I'm working on.
Suggestions on a workaround very welcome!

Anyway, here's how to reproduce the problem I'm seeing:

ah@mbpah:/tmp$ debcheckout --git-track '*' util-linux
declared git repository at 
git://anonscm.debian.org/collab-maint/pkg-util-linux.git
git clone git://anonscm.debian.org/collab-maint/pkg-util-linux.git util-linux 
...
Cloning into 'util-linux'...
remote: Counting objects: 89010, done.
remote: Compressing objects: 100% (26132/26132), done.
remote: Total 89010 (delta 68415), reused 82207 (delta 61984)
Receiving objects: 100% (89010/89010), 135.53 MiB | 1.31 MiB/s, done.
Resolving deltas: 100% (68415/68415), done.
Branch debian-2.24 set up to track remote branch debian-2.24 from origin.
Branch debian-2.25 set up to track remote branch debian-2.25 from origin.
Branch debian-2.26 set up to track remote branch debian-2.26 from origin.
Branch debian-2.27 set up to track remote branch debian-2.27 from origin.
Branch l10n set up to track remote branch l10n from origin.
Branch patch-queue/l10n set up to track remote branch patch-queue/l10n from 
origin.
Branch patches-v2.20.1 set up to track remote branch patches-v2.20.1 from 
origin.
Branch pristine-tar set up to track remote branch pristine-tar from origin.
Branch upstream set up to track remote branch upstream from origin.
Branch upstream-2.24 set up to track remote branch upstream-2.24 from origin.
Branch upstream-2.25 set up to track remote branch upstream-2.25 from origin.
Branch upstream-2.26 set up to track remote branch upstream-2.26 from origin.
Branch upstream-2.27 set up to track remote branch upstream-2.27 from origin.
ah@mbpah:/tmp$ cd util-linux
ah@mbpah:/tmp/util-linux$ git remote add kzak 
https://git.kernel.org/pub/scm/utils/util-linux/util-linux.git
ah@mbpah:/tmp/util-linux$ git fetch kzak
remote: Counting objects: 2122, done.
remote: Compressing objects: 100% (1646/1646), done.
remote: Total 2122 (delta 1394), reused 763 (delta 473)
Receiving objects: 100% (2122/2122), 4.25 MiB | 1.70 MiB/s, done.
Resolving deltas: 100% (1394/1394), done.
>From https://git.kernel.org/pub/scm/utils/util-linux/util-linux
 * [new branch]  master -> kzak/master
 * [new branch]  stable/v2.13   -> kzak/stable/v2.13
 * [new branch]  stable/v2.13.0 -> kzak/stable/v2.13.0
 * [new branch]  stable/v2.13.1 -> kzak/stable/v2.13.1
 * [new branch]  stable/v2.14   -> kzak/stable/v2.14
 * [new branch]  stable/v2.15   -> kzak/stable/v2.15
 * [new branch]  stable/v2.16   -> kzak/stable/v2.16
 * [new branch]  stable/v2.17   -> kzak/stable/v2.17
 * [new branch]  stable/v2.19   -> kzak/stable/v2.19
 * [new branch]  stable/v2.20   -> kzak/stable/v2.20
 * [new branch]  stable/v2.21   -> kzak/stable/v2.21
 * [new branch]  stable/v2.22   -> kzak/stable/v2.22
 * [new branch]  stable/v2.23   -> kzak/stable/v2.23
 * [new branch]  stable/v2.24   -> kzak/stable/v2.24
 * [new branch]  stable/v2.25   -> kzak/stable/v2.25
 * [new branch]  stable/v2.26   -> kzak/stable/v2.26
 * [new branch]  stable/v2.27   -> kzak/stable/v2.27
 * [new branch]  stable/v2.28   -> kzak/stable/v2.28
 * [new branch]  stable/v2.29   -> kzak/stable/v2.29
 * [new branch]  stable/v2.30   -> kzak/stable/v2.30
 * [new tag] v2.30.1-> v2.30.1
ah@mbpah:/tmp/util-linux$ gbp import-orig  --uscangbp:info: Launching uscan...
uscan: Newest version of util-linux on remote site is 2.30.1, local version is 
2.29.2
uscan:=> Newer package available from
  
https://www.kernel.org/pub/linux/utils/util-linux/v2.30/util-linux-2.30.1.tar.xz
gbp:info: using ../util-linux_2.30.1.orig.tar.xz
What is the upstream version? [2.30.1] 
gbp:info: Importing '../util-linux_2.30.1.orig.tar.xz' to branch 'upstream'...
gbp:info: Source package is util-linux
gbp:info: Upstream version is 2.30.1
gbp:error: Couldn't commit to 'pristine-tar' with upstream 
'86e26620149b211d9cfbd9c03871cc6b363a3d67': pristine-xz failed to reproduce 
build of ../util-linux_2.30.1.orig.tar.xz
(Please file a bug report.)
pristine-tar: command failed: pristine-xz --no-verbose --no-debug --no-keep 
gendelta ../util-linux_2.30.1.orig.tar.xz /tmp/pristine-tar.dzze8xAZbE/wrapper
pristine-tar: failed to generate delta
gbp:error: Import of ../util-linux_2.30.1.orig.tar.xz failed: Couldn't commit 
to 'pristine-tar' with upstream '86e26620149b211d9cfbd9c03871cc6b363a3d67': 
pristine-xz failed to reproduce build of ../util-

Bug#869186: [Pkg-mutt-maintainers] Bug#869186: mutt: Install missing required dependencies (libxapian30)

2017-07-21 Thread Boruch Baum
Thanks Evgeni for the quick response. It's gratifying to see a debian
maintainer so alert and responsive.

This may *possibly* be what some folks say is _my bad_, so let me add
some details, that I didn't realize until after I hit 'send'.

On 2017-07-21 13:32, Evgeni Golov wrote:
> On Fri, Jul 21, 2017 at 07:02:50AM -0400, Boruch Baum wrote:
> > Upon upgrading `mutt' from the stable to testing repositories, mutt
> > ceased to function, offering the following error message:
>
> There is no mutt 1.7.2-1 in testing. Did you mean upgrading
> jessie→stretch?

I meant upgrading from 1.5.xx to 1.7.2-1.

This next indented section is tangential, but important:

  My bug report may be valid for debian, or not. The main problem with
  my report is that it was intended to be sent to your ?evil? or at
  least "more-challenged" twin, the devuan project. I am running their
  version of 'stable' which has mutt 1.5.xxx and upgraded to their
  'testing' version 1.7.2-1.

  Their package `reportbug' in their stable repository sends bug reports
  to debian, not devuan (aaargh!). I have since upgraded to their
  'testing' version, and filed a bug report against their 'stable'
  version, but I see that even their 'testing' version is flawed in that
  it seems to always send reports to BOTH devuan and debian (aaargh!).
  So, I will file another bug report (manually) to them.

  It might be a good idea if you could join me in complaining to the
  devuan folks. For me this is embarassing, but really, I wasn't
  expecting this incompetence.

> mutt has a dependency on libnotmuch4, libnotmuch4 has a dependency on
> libxapian30, mutt is not using any xapian directly AFAIK.

This issue is that libnotmuch4 links to a whole lot of xapian symbols
that will be undefined until the correct version of the xapian library
is installed.

> so we might discuss this as being a not-strong-enough dep between
> libnotmuch4 and libxapian30, but not a serios bug in mutt.

Agreed. Can you re-assign it, or should I re-file, or should we drop
this? There is still the possibility that this really isn't a debian
issue at all, but a devuan one, but its something easy to check.

Apologies again,

-- 
hkp://keys.gnupg.net
CA45 09B5 5351 7C11 A9D1  7286 0036 9E45 1595 8BC0



Bug#869193: easy-rsa: New upsteam version, which enables ECC support

2017-07-21 Thread Lynoure Braakman
Package: easy-rsa
Version: 2.2.2-2
Severity: wishlist

Dear Maintainer,

thank you for looking after easy-rsa. I've been using it for some things
so far, but now am switching to ECC in some uses and alas, that support
is not in Debian yet. Could you consider bringing the new stable
version, v3.0.0 or v3.0.1 into Debian?

-- 
Lynoure Braakman

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

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

*** End of the template - remove these template lines ***


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

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

Versions of packages easy-rsa depends on:
ii  openssl  1.1.0f-3

Versions of packages easy-rsa recommends:
ii  opensc  0.16.0-3

easy-rsa suggests no packages.

-- no debconf information



Bug#869194: awscli: seek() takes 2 positional arguments but 3 were given

2017-07-21 Thread Olaf van der Spek
Package: awscli
Version: 1.11.13-1
Severity: normal

Dear Maintainer,

$ aws s3 cp --acl public-read --content-type image/jpeg z.jpg s3://blah

upload failed: ./z.jpg to s3://blah seek() takes 2 positional arguments but 3 
were given

When input file is empty / 0 bytes.

Gr,

Olaf

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

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

Versions of packages awscli depends on:
ii  python3 3.5.3-1
ii  python3-botocore1.4.70-1
ii  python3-colorama0.3.7-1
ii  python3-docutils0.13.1+dfsg-2
ii  python3-rsa 3.4.2-1
ii  python3-s3transfer  0.1.9-1

awscli recommends no packages.

awscli suggests no packages.

-- no debconf information



Bug#865692: Suggested patch

2017-07-21 Thread Dirk Eddelbuettel

On 21 July 2017 at 07:08, Andreas Tille wrote:
| I stumbled upon this since the Debian Med package tree-puzzle
| is affected.  Wouldn't the patch as easy as
| 
| cd $somewhere && $(MAKE) && cd ..

I went with   $(MAKE) -C somewhereas suggested in the original report.

Dirk

-- 
http://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org



Bug#869195: python-blosc: building of sphinx-docs breaks

2017-07-21 Thread Daniel Stender
Package: python-blosc
Version: 1.4.4+ds1-3+b1
Severity: serious
Justification: fails to build from source (but built successfully in the past)
Control: forwarded -1 https://github.com/Blosc/python-blosc/issues/125

The building of python-blosc currenty breaks:


Running Sphinx v1.5.6
making output directory...
loading pickled environment... not yet created
loading intersphinx inventory from http://docs.python.org/objects.inv...
WARNING: intersphinx inventory 'http://docs.python.org/objects.inv' not 
fetchable due to : 
HTTPConnectionPool(host='127.0.0.1', port=9): Max retries exceeded with url: 
http://docs.python.org/objects.inv (Caused by ProxyError('Cannot connect to 
proxy.', 
NewConnectionError(': Failed to establish a new connection: [Errno 111] 
Connection refused',)))
building [mo]: targets for 0 po files that are out of date
building [html]: targets for 5 source files that are out of date
updating environment: 5 added, 0 changed, 0 removed
reading sources... [ 20%] index
reading sources... [ 40%] install
reading sources... [ 60%] intro
reading sources... [ 80%] reference

Exception occurred:
  File "/usr/lib/python2.7/re.py", line 155, in sub
return _compile(pattern, flags).sub(repl, string, count)
TypeError: expected string or buffer
The full traceback has been saved in /tmp/sphinx-err-A00fVX.log, if you want to 
report the issue to the developers.
Please also report this if it was a user error, so that a better error message 
can be provided next time.
A bug report can be filed in the tracker at 
. Thanks!
debian/rules:12: recipe for target 'override_dh_auto_install' failed


The package builds on python3-sphinx, but this happens with python-sphinx 
either.

Thanks,
DS

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

Kernel: Linux 4.5.0-2-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 python-blosc depends on:
ii  libblosc1  1.11.1+ds2-2
ii  libc6  2.24-12
ii  python 2.7.13-2

python-blosc recommends no packages.

Versions of packages python-blosc suggests:
ii  python-blosc-doc  1.4.4+ds1-3

-- no debconf information



Bug#869121: ITP: dragonfire -- Dragonfire is an open source virtual assistant project for Debian based Linux distributions

2017-07-21 Thread Mehmet Mert Yıldıran
Mr. Smedegaard,

I don't know how to edit the description. I have updated the subject
and summary by sending retitle 869121 bla bla and summary 869121 bla
bla to cont...@bugs.debian.org, but I have no idea about how to update
the description. Please tell me if there is a method about it that I
do not know.

Best regards.



Bug#869196: plank: new upstream 0.11.4

2017-07-21 Thread Jonatan Nyberg
package: plank
severity: normal

Please consider to upgrade to the current upstream version
(0.11.4).

Regards,
Jonatan



Bug#869132: curvedns: Incomplete debian/copyright?

2017-07-21 Thread Chris Lamb
(readding bug to CC) 

Please directly  link to a .dsc instead, or the mentors.debian.net entry. 

/lamby 

Stéphane Neveu wrote:

> Of course, you can download it here :
> http://dl.free.fr/g5zaQBZcy
> 
> Regards,
> Stéphane
> 
> 2017-07-21 13:23 GMT+02:00 Chris Lamb :
> >
> > Stéphane,
> >
> > Please upload your (built)  package somewhere and I will have a look.
> >
> > /lamby
> >
> >> Hi Chris,
> >>
> >> Thank you for your review. I had a look at the entire package but I
> >> did not see anything else.
> >> I hope the copyright is fine now :
> >> https://anonscm.debian.org/cgit/pkg-security/curvedns.git/commit/?id=dccc20efc28f4bfbf1d157bedaa46a6d9b56676b
> >>
> >> I also used cme update dpkg-copyright command and license-reconcile.
> >>
> >> Just tell me if it's ok for you and I'll ask my DD to re-upload it.
> >>
> >> Best regards,
> >>
> >> Stephane
> >>
> >>
> >> 2017-07-20 20:55 GMT+02:00 Chris Lamb :
> >> > Source: curvedns
> >> > Version: 0.87-1
> >> > Severity: serious
> >> > Justication: Policy 12.5
> >> > X-Debbugs-CC: NEVEU Stephane 
> >> >
> >> > Hi,
> >> >
> >> > I just ACCEPTed curvedns from NEW but noticed it was missing
> >> > attribution in debian/copyright for at least:
> >> >
> >> >   nacl/crypto_scalarmult/curve25519/donna_c64/smult.c
> >> >
> >> >
> >> > (This is not exhaustive so please check over the entire package
> >> > carefully and address these on your next upload.)
> >> >
> >> >
> >> > Regards,
> >> >
> >> > --
> >> >   ,''`.
> >> >  : :'  : Chris Lamb, Debian Project Leader
> >> >  `. `'`  la...@debian.org / chris-lamb.co.uk
> >> >`-
> >
> >
> > Regards,
> >
> > --
> >   ,''`.
> >  : :'  : Chris Lamb, Debian Project Leader
> >  `. `'`  la...@debian.org / chris-lamb.co.uk
> >`-


Regards,

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



Bug#869197: awscli: 'Connection aborted.', ConnectionResetError(104, 'Connection reset by peer')

2017-07-21 Thread Olaf van der Spek
Package: awscli
Version: 1.11.13-1
Severity: normal

Dear Maintainer,

After updating credentials I'm seeing from the CLI: An error occurred 
(AccessDenied) when calling the PutObject operation: Access Denied
or An error occurred (AccessDenied) when calling the CreateMultipartUpload 
operation: Access Denied

So far so good. But when invoking the same command from a C++ program via 
popen: ('Connection aborted.', ConnectionResetError(104, 'Connection reset by 
peer'))
Not sure what causes the difference..

Gr,

Olaf

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

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

Versions of packages awscli depends on:
ii  python3 3.5.3-1
ii  python3-botocore1.4.70-1
ii  python3-colorama0.3.7-1
ii  python3-docutils0.13.1+dfsg-2
ii  python3-rsa 3.4.2-1
ii  python3-s3transfer  0.1.9-1

awscli recommends no packages.

awscli suggests no packages.

-- no debconf information



Bug#868507: Re : Re : Re : Re : Re : Bug#868507: libreoffice-writer: Crash after the last upgrade

2017-07-21 Thread nicolas . patrois
Le 17/07/2017 07:34:11, Rene Engelhard a écrit :

> Did you try without the binary nvidia drivers?

I had a bug with libreoffice-gtk3 a long while ago so I uninstalled it.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=838596

When I upgraded libreoffice this morning, I just saw that libreoffice-gtk3 was 
recommended so I installed it back.

Now, LO works fine even if the console prints this:
> lowriter 
error
xsltParseStylesheetFile : cannot parse 
I/O warning : failed to load external entity ""
error
xsltParseStylesheetFile : cannot parse 
error
xsltParseStylesheetFile : cannot parse 
I/O warning : failed to load external entity ""
error
xsltParseStylesheetFile : cannot parse 

I think that you can close the bug.

nicolas patrois : pts noir asocial
-- 
RÉALISME

M : Qu'est-ce qu'il nous faudrait pour qu'on nous considère comme des humains ? 
Un cerveau plus gros ?
P : Non... Une carte bleue suffirait...



Bug#869199: knot binary-all FTBFS: dh_missing: missing files, aborting

2017-07-21 Thread Adrian Bunk
Source: knot
Version: 2.5.3-1
Severity: serious

https://buildd.debian.org/status/package.php?p=knot&suite=sid

...
   dh_install -i -O--parallel "-O--dbgsym-migration=knot-dbg (<< 2.2.0-2~)" 
-O--exclude=.la -O--exclude=example.com.zone -O--fail-missing
dh_install: Please use dh_missing --list-missing/--fail-missing instead
dh_install: This feature will be removed in compat 11.
dh_missing: etc/knot/knot.sample.conf exists in debian/tmp but is not installed 
to anywhere
dh_missing: missing files, aborting
The following debhelper tools have reported what they installed (with 
files per package)
 * dh_install: knot (17), knot-dnsutils (4), knot-doc (26), knot-host 
(2), libdnssec4 (2), libknot-dev (11), libknot6 (2), libzscanner1 (2)
If the missing files are installed by another tool, please file a bug 
against it.
When filing the report, if the tool is not part of debhelper itself, 
please reference the
"Logging helpers and dh_missing" section from the "PROGRAMMING" guide 
for debhelper (10.6.3+).
  (in the debhelper package: /usr/share/doc/debhelper/PROGRAMMING.gz)
Be sure to test with dpkg-buildpackage -A/-B as the results may vary 
when only a subset is built
For a short-term work-around: Add the files to debian/not-installed
dh_install: dh_missing --exclude .la --exclude example.com.zone --fail-missing 
returned exit code 255
debian/rules:33: recipe for target 'binary-indep' failed
make: *** [binary-indep] Error 25



Bug#869198: RFS: golang-github-shibukawa-configdir/0.0~git20170330.0.e180dbd-1 [ITP]

2017-07-21 Thread Diego M . Rodriguez


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

  Dear mentors,

  I am looking for a sponsor for my package "golang-github-shibukawa-configdir"

 * Package name: golang-github-shibukawa-configdir
   Version : 0.0~git20170330.0.e180dbd-1
   Upstream Author : Yoshiki Shibukawa
 * URL : https://github.com/shibukawa/configdir
 * License : Expat
   Section : devel

  It builds those binary packages:

golang-github-shibukawa-configdir-dev - Configuration directories handling 
for Go

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

  https://mentors.debian.net/package/golang-github-shibukawa-configdir


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

dget -x 
https://mentors.debian.net/debian/pool/main/g/golang-github-shibukawa-configdir/golang-github-shibukawa-configdir_0.0~git20170330.0.e180dbd-1.dsc

  Or on the following repository:

https://anonscm.debian.org/cgit/pkg-go/packages/golang-github-shibukawa-configdir.git

  Changes since the last upload:

* Initial release. (Closes: #868050)


  Regards,
   Diego M. Rodriguez



Bug#865765: [qtcurve] Crash when using QtCurve widget style and Breeze preset

2017-07-21 Thread Boris Pek
Hi Sergey,

> Patch had some malformed header (was mixing information from previous
> maintainer patch and residue of some older description). Here is an
> updated patch with hopefully all headers filled correct.
>
> Hopefully this one will work fine :)

Please discuss this patch with QtCurve developers in upstream BTS.

Best regards,
Boris



Bug#864074: defaults.vim: broken configuration

2017-07-21 Thread Igor Sverkos
Hi,

On Thu, 20 Jul 2017 22:24:01 -0400 James McCoy  wrote:

> There's no need to disable defaults.vim.  As I have also suggested (in
> this very bug report), you can explicitly load defaults.vim and then
> disable whatever settings you don't like.

I hit the same problem. Maybe I don't understand your suggestion. Could
you please explain it in more details?

My problem:
===
We have a network running ~600 Debian boxes at the moment.

We are using Puppet for configuration management.

I now want to deploy a default system-wide VIM configuration which can
be overwritten by the user using ~/.vimrc.

How am I supposed to do that?

I would expect to alter "/etc/vim/vimrc" respective
"/etc/vim/vimrc.local" but this doesn't work when
"/usr/share/vim/vim80/defaults.vim" will be sourced as last
configuration file.


-- 
Regards,
Igor



Bug#858353: ITP: k6 -- A modern load testing tool, using Go and JavaScript

2017-07-21 Thread Diego M . Rodríguez
An update on the status of the packaging:
* a new dependency (configdir at #869198) has been added as part of
packaging the newest v0.17.0 version.
* for the ITP to be completed, node-babel-standalone should be
packaged as well as the application includes the .js files directly on
the source tarballs. There is an ongoing ITP for packaging node-babel
which I have not marked yet as a dependency as I'm awaiting
confirmation [1], but it would be the only blocker at the moment.

[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=84#29

Best regards,
Diego M. Rodríguez



Bug#865765: [qtcurve] Crash when using QtCurve widget style and Breeze preset

2017-07-21 Thread Sergey Sharybin
Hi Boris,

I don't think there is anything to be discussed actually.

After closer studying of the latest upstream sources of QtCurve it
appears same exact bug was submitted a while back to them. Same exact
patch was committed to the upstream, see [1]. And here is an original
bug report [2].

So guess it's either matter downstreaming the fix or waiting for 1.9.0
to be out (it is at RC1 state atm).

[1] https://cgit.kde.org/qtcurve.git/commit/?id=f164a4b69
[2] https://bugs.kde.org/show_bug.cgi?id=374046

On Fri, Jul 21, 2017 at 2:19 PM, Boris Pek  wrote:
> Hi Sergey,
>
>> Patch had some malformed header (was mixing information from previous
>> maintainer patch and residue of some older description). Here is an
>> updated patch with hopefully all headers filled correct.
>>
>> Hopefully this one will work fine :)
>
> Please discuss this patch with QtCurve developers in upstream BTS.
>
> Best regards,
> Boris



-- 
With best regards, Sergey Sharybin



Bug#867778: imagemagick: CVE-2017-9500: assertion failed in ResetImageProfileIterator

2017-07-21 Thread Salvatore Bonaccorso
Control: reopen -1
Control: found -1 8:6.8.9.9-5
Control: found -1 8:6.8.9.9-5+deb8u10
Control: found -1 8:6.9.7.4+dfsg-11+deb9u1

Hi

Marc Deslauriers noticed that the patch for this issue wasn't actually
applied to any release as mentioned for DSA-3914-1.

Reopening the bug, and updating the security-tracker accordingly.

Regards,
Salvatore



Bug#869135: Please consider switching to giza

2017-07-21 Thread Ole Streicher
Hi Gregory,

On 20.07.2017 23:03, gregor herrmann wrote:
> - Build-Depend on giza-dev instead of pgplot5 -> the package builds
>   and the dependencies look reasonable.
> - When I enable the tests, I get:
>   + success in autopkgtest
>   + a segfault in perl during the build:
> 
> Program terminated with signal SIGSEGV, Segmentation fault.
> #0  __strcat_sse2_unaligned () at 
> ../sysdeps/x86_64/multiarch/strcpy-sse2-unaligned.S:313
> 313   ../sysdeps/x86_64/multiarch/strcpy-sse2-unaligned.S: No such file or 
> directory.
> (gdb) bt full
> #0  __strcat_sse2_unaligned () at 
> ../sysdeps/x86_64/multiarch/strcpy-sse2-unaligned.S:313
> No locals.
> #1  0x7f66f422bf45 in ?? ()
> No symbol table info available.
> #2  0x59711419 in ?? ()
> No symbol table info available.
> #3  0x5603c8025c22 in Perl_safesysmalloc (size=) at 
> util.c:153
> ptr = 
> #4  0x5603c86c45b8 in ?? ()
> No symbol table info available.
> #5  0x0100 in ?? ()
> No symbol table info available.
> #6  0x5603c860c010 in ?? ()
> No symbol table info available.
> #7  0x0100 in ?? ()
> No symbol table info available.
> #8  0x in ?? ()
> No symbol table info available.

How did you get the stacktrace? And/or could I ask you to run the same
with the giza dbgsym packages (libcpgplot0-dbgsym, libpgplot0-dbgsym,
libgiza0-dbgsym)? Unfortunately they are not in the archive yet, so this
would require a rebuild of giza.

I also tried it and I also get a segmentation fault when I built with
pbuilder, but not when just using debuild. I also don't get the segfault
when I run the test suite directly from the shell -- but in the latter
cases, I am asked to press RETURN after each test. So, some code in
test.pl seems to disable this under some conditions; however my limited
knowledge of perl doesn't help here.

Do you have an idea how to reproduce the segfault on the command line?
Or can you re-create the stacktrace with the -dbgsym packages? Or tell
me what I should do to create them in pdebuild?

Best regards

Ole



Bug#869132: curvedns: Incomplete debian/copyright?

2017-07-21 Thread Gianfranco Costamagna
Hello,

>Please directly  link to a .dsc instead, or the mentors.debian.net entry. 


I did sponsor the package once I saw the pending tag, it was looking good
to me
https://incoming.debian.org/debian-buildd/pool/main/c/curvedns/curvedns_0.87-2.dsc

G.



Bug#868507: Re : Re : Re : Re : Re : Bug#868507: libreoffice-writer: Crash after the last upgrade

2017-07-21 Thread rene
Hi,

On Fri, Jul 21, 2017 at 02:14:42PM +0200, nicolas.patr...@gmail.com wrote:
> Le 17/07/2017 07:34:11, Rene Engelhard a écrit :
> 
> > Did you try without the binary nvidia drivers?
> 
> I had a bug with libreoffice-gtk3 a long while ago so I uninstalled it.
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=838596
> 
> When I upgraded libreoffice this morning, I just saw that libreoffice-gtk3 
> was recommended so I installed it back.

Ah, OK.

Geoff, does installing libreoffice-gtk3 fix it for you, too (assuming you
use a Gtk3-using desktop or export SAL_USE_VCLPLUGIN=gtk3 or
export OOO_FORCE_DESKTOP="gnome")?

> Now, LO works fine even if the console prints this:
> > lowriter 
> error
> xsltParseStylesheetFile : cannot parse 
> I/O warning : failed to load external entity ""
> error
> xsltParseStylesheetFile : cannot parse 
> error
> xsltParseStylesheetFile : cannot parse 
> I/O warning : failed to load external entity ""
> error
> xsltParseStylesheetFile : cannot parse 

Yeah, those are known since ages:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=688487

> I think that you can close the bug.

It would have been better if you  didn't file it to begin with. And you didn't
eben answer my intial question.. I'll repeat:

Does it also happen without the binary nvidia drivers?

_Then_ I would feel more comfortable just closing it, yeah.

Regards,

Rene



Bug#869200: netdata: adequate tells about obsolete conffiles in netdata

2017-07-21 Thread shirish शिरीष
Package: netdata
Version: 1.6.0+dfsg-3
Severity: normal

Dear Maintainer,

I was upgrading netdata when was hit with the following via adequate.

[$] adequate netdata | grep obsolete-conffile
netdata: obsolete-conffile /etc/netdata/python.d/gunicorn_log.conf
netdata: obsolete-conffile /etc/netdata/python.d/nginx_log.conf

didn't share the whole run as other errors were about
py-file-not-bytecompiled which I don't know much about.

Please fix the above.

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

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

Versions of packages netdata depends on:
ii  adduser  3.115
ii  init-system-helpers  1.48
ii  libc62.24-12
ii  libcap2-bin  1:2.25-1
ii  libuuid1 2.29.2-2
ii  lsb-base 9.20161125
ii  netdata-data 1.6.0+dfsg-3
ii  python   2.7.13-2
ii  python-yaml  3.12-1+b1
ii  zlib1g   1:1.2.8.dfsg-5

Versions of packages netdata recommends:
ii  fping   4.0-2
ii  nodejs  4.8.3~dfsg-1

netdata suggests no packages.

-- no debconf information


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



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

2017-07-21 Thread Neil Williams
On Fri, 21 Jul 2017 13:17:36 +0200
Matthias Klose  wrote:

> On 21.07.2017 09:43, Neil Williams wrote:
> > On Thu, 20 Jul 2017 22:23:31 +0200
> > Matthias Klose  wrote:
> >   
> >> On 20.07.2017 16:40, 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:
> >>
> >> please could you check if it builds with the debug interpreter?
> >>  
> > 
> > $ make SPHINXBUILD="python -m
> > pdb /usr/share/sphinx/scripts/python2/sphinx-build" -C doc/v2 html
> > make: Entering directory '/home/neil/code/lava/lava-server/doc/v2'
> > python -m pdb /usr/share/sphinx/scripts/python2/sphinx-build -b
> > html -d _build/doctrees  -n -j 4 .   
> 
> no, not debugging the standard interpreter, but using the debug
> interpreter, calling python-dbg

Sorry.

I don't see a change:

$ make SPHINXBUILD='python-dbg /usr/bin/sphinx-build' -C doc/v2 html
make: Entering directory '/home/neil/code/lava/lava-server/doc/v2'
python-dbg /usr/bin/sphinx-build -b html -d _build/doctrees  -n -j 4 . 
_build/html
Running Sphinx v1.5.6
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 98, in 
_join_one
exc, result = pipe.recv()
EOFError
The full traceback has been saved in /tmp/sphinx-err-gq8BHS.log, if you want to 
report the issue to the developers.
Please also report this if it was a user error, so that a better error message 
can be provided next time.
A bug report can be filed in the tracker at 
. Thanks!
^CError in atexit._run_exitfuncs:
Traceback (most recent call last):
  File "/usr/lib/python2.7/atexit.py", line 24, in _run_exitfuncs
func(*targs, **kargs)
  File "/usr/lib/python2.7/multiprocessing/util.py", line 328, in _exit_function
p.join()
  File "/usr/lib/python2.7/multiprocessing/process.py", line 148, in join
res = self._popen.wait(timeout)
  File "/usr/lib/python2.7/multiprocessing/forking.py", line 154, in wait
return self.poll(0)
  File "/usr/lib/python2.7/multiprocessing/forking.py", line 135, in poll
pid, sts = os.waitpid(self.pid, flag)
KeyboardInterrupt
Error in sys.exitfunc:
Traceback (most recent call last):
  File "/usr/lib/python2.7/atexit.py", line 24, in _run_exitfuncs
func(*targs, **kargs)
  File "/usr/lib/python2.7/multiprocessing/util.py", line 328, in _exit_function
p.join()
  File "/usr/lib/python2.7/multiprocessing/process.py", line 148, in join
res = self._popen.wait(timeout)
  File "/usr/lib/python2.7/multiprocessing/forking.py", line 154, in wait
return self.poll(0)
  File "/usr/lib/python2.7/multiprocessing/forking.py", line 135, in poll
pid, sts = os.waitpid(self.pid, flag)
KeyboardInterrupt
[357925 refs]
Makefile:45: recipe for target 'html' failed
make: *** [html] Error 1


$ cat /tmp/sphinx-err-gq8BHS.log
# Sphinx version: 1.5.6
# Python version: 2.7.13+ (CPython)
# Docutils version: 0.13.1 release
# Jinja2 version: 2.9.6
# Last messages:
#   91 added, 0 changed, 0 removed
#   reading sources... [ 14%] actions-boot .. data-export
#   reading sources... [ 28%] debian .. explain_first_job
#   reading sources... [ 42%] first-devices .. ipxe
#   reading sources... [ 57%] lava-dashboard-image-reports .. migrate-lava
#   reading sources... [ 71%] migrating-admin-example .. pipeline-writer
#   reading sources... [ 85%] pipeline-writer-secondary .. tables
#   reading sources... [100%] test-repositories .. writing-tests
#   
#   waiting for workers...
# Loaded extensions:
#   sphinx.ext.coverage (1.5.6) from 
/usr/lib/python2.7/dist-packages/sphinx/ext/coverage.pyc
#   sphinx.ext.viewcode (1.5.6) from 
/usr/lib/python2.7/dist-packages/sphinx/ext/viewcode.pyc
#   sphinx.ext.todo (1.5.6) from 
/usr/lib/python2.7/dist-packages/sphinx/ext/todo.pyc
#   sphinx.ext.autodoc (1.5.6) from 
/usr/lib/python2.7/dist-packages/sphinx/ext/autodoc.pyc
#   sphinx.ext.intersphinx (1.5.6) from 
/usr/lib/python2.7/dist-packages/sphinx/ext/intersphinx.pyc
#   sphinx.ext.doctest (1.5.6) from 
/usr/lib/python2.7/dist-packages/sphinx/ext/doctest.pyc
#   alabaster (0.7.8) from 
/usr/lib/python2.7/dist-packages/alabaster/__init__.pyc
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/sphinx/cmdline.py", line 296, in main
app.build(opts.force_all, filenames)
  File "/usr/lib/python2.7/dist-packages/sphinx/application.py", line 333, in 
build
self.builder.build_update()
  File "/usr/lib/python2

Bug#865765: [qtcurve] Crash when using QtCurve widget style and Breeze preset

2017-07-21 Thread Boris Pek
control: forwarded -1 https://bugs.kde.org/show_bug.cgi?id=374046

> I don't think there is anything to be discussed actually.
>
> After closer studying of the latest upstream sources of QtCurve it
> appears same exact bug was submitted a while back to them. Same exact
> patch was committed to the upstream, see [1]. And here is an original
> bug report [2].
>
> So guess it's either matter downstreaming the fix or waiting for 1.9.0
> to be out (it is at RC1 state atm).
>
> [1] https://cgit.kde.org/qtcurve.git/commit/?id=f164a4b69
> [2] https://bugs.kde.org/show_bug.cgi?id=374046

I had not time to check last commits in upstream VCS, so I was not aware of 
this.
Thanks for the links, I'll update the package soon.

Best regards,
Boris



Bug#869121: ITP: dragonfire -- Dragonfire is an open source virtual assistant project for Debian based Linux distributions

2017-07-21 Thread Jonas Smedegaard
Hi Mehmet,

Quoting Mehmet Mert Yıldıran (2017-07-21 14:02:13)
> I don't know how to edit the description. I have updated the subject 
> and summary by sending retitle 869121 bla bla and summary 869121 bla 
> bla to cont...@bugs.debian.org, but I have no idea about how to update 
> the description. Please tell me if there is a method about it that I 
> do not know.

Seems we a talking about two related but different things here:

 a) package of Dragonfire officially for Debian
 b) bugreport aboout creation of Debian package dragonfire

You filed a bugreport of type "ITP", which means you intend to create 
the package officially for Debian.

In your bugreport, you shared a description of the package - i.e. what 
you intend to put into so-called "long description" field of the 
package.

I comment on the bugreport that the long description field need to be 
more, well, desriptive.  Here is what Debian Policy says in section 
3.4.2:

> The extended description should describe what the package does and how 
> it relates to the rest of the system (in terms of, for example, which 
> subsystem it is which part of).


In your comment above it seems you tried correct this _bugreport_.  You 
do that by simply posting another email with the additional info.  Also, 
it is not crucial that the bugreport is perfect - what matters is the 
package :-)


Hope that helps,

 - Jonas

P.S.

Since it seems you are new to this: If you did not intend to make this 
package yourself, but only wanted to suggest that others make a package, 
then please tell us (technically you should then instead have filed a 
so-called "RFP" package, but don't worry - we cam simply adjust that).

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private


signature.asc
Description: signature


Bug#868283: cups-browsed ignores "DefaultPolicy authenticated" from cupsd.conf

2017-07-21 Thread Brian Potkin
On Fri 21 Jul 2017 at 10:21:23 +0200, Christoph Pleger wrote:

> Hello,
> 
> >cups-browsed now saves a copy of the remote printer's PPD in
> >/var/cache/cups. "Operation Policy" is one of the options which
> >can set there using the web interface (say).
> 
> I cannot find where to change the operation policy in the web interface.

Isn't it under "Policies"?

-- 
Brian.



Bug#868507: Re : Re : Re : Re : Re : Re : Bug#868507: libreoffice-writer: Crash after the last upgrade

2017-07-21 Thread nicolas . patrois
Le 21/07/2017 14:40:00, r...@debian.org a écrit :

> It would have been better if you  didn't file it to begin with. And
> you didn't eben answer my intial question.. I'll repeat:

> Does it also happen without the binary nvidia drivers?

I wouldn’t have filed it if other games crashed too.
I won’t remove libreoffice-gtk3 if it works with it. The solution was in the 
presence of this recommended package. If LO crashes back when other games crash 
too, I’ll tell you but I never saw LO crash because of the nVidia driver (I use 
the long life version) or a conflict with X but I understand that it may happen 
(you’re the maintainer, after all, not me).
Note that there is no composite mode in my XFCE session.

nicolas patrois : pts noir asocial
-- 
RÉALISME

M : Qu'est-ce qu'il nous faudrait pour qu'on nous considère comme des humains ? 
Un cerveau plus gros ?
P : Non... Une carte bleue suffirait...



Bug#864074: defaults.vim: broken configuration

2017-07-21 Thread Martin Steigerwald
Igor Sverkos - 21.07.17, 14:25:
> Hi,
> 
> On Thu, 20 Jul 2017 22:24:01 -0400 James McCoy  wrote:
> > There's no need to disable defaults.vim.  As I have also suggested (in
> > this very bug report), you can explicitly load defaults.vim and then
> > disable whatever settings you don't like.
> 
> I hit the same problem. Maybe I don't understand your suggestion. Could
> you please explain it in more details?
> 
> My problem:
> ===
> We have a network running ~600 Debian boxes at the moment.
> 
> We are using Puppet for configuration management.
> 
> I now want to deploy a default system-wide VIM configuration which can
> be overwritten by the user using ~/.vimrc.
> 
> How am I supposed to do that?
> 
> I would expect to alter "/etc/vim/vimrc" respective
> "/etc/vim/vimrc.local" but this doesn't work when
> "/usr/share/vim/vim80/defaults.vim" will be sourced as last
> configuration file.

Well that one is actually documented in README.Debian as pointed out here in 
this bug report several times already. Add

let g:skip_defaults_vim = 1

at the beginning of "/etc/vim/vimrc.local".

And that is not really the issue of this bug report.

The issue is, that it is required to have a work-around like this, or the one 
James suggested – where it will if I understand correctly load defaults.vim 
before making changes to it –, in order to have a sane behavior. Since I use 
Linux, configuration loading always worked from global to local. Here it does 
not, unless you add a work-around.

This has been an upstream decision according to James and I think its best to 
bring this issue to upstream. If upstream does not adapt the behavior, I am 
all for a patch in the Debian package, but it seems James thinks differently 
on that one. Another option would be to vote about that new behavior by 
switching to neovim.

Thanks,
-- 
Martin

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


Bug#869132: curvedns: Incomplete debian/copyright?

2017-07-21 Thread Stéphane Neveu
Chris,

Is it ok on debomatic ?
http://debomatic-amd64.debian.net/distribution#unstable/curvedns/0.87-2/buildlog
My package on mentors has been removed...

Regards,
Stephane

2017-07-21 14:13 GMT+02:00 Chris Lamb :
> (readding bug to CC)
>
> Please directly  link to a .dsc instead, or the mentors.debian.net entry.
>
> /lamby
>
> Stéphane Neveu wrote:
>
>> Of course, you can download it here :
>> http://dl.free.fr/g5zaQBZcy
>>
>> Regards,
>> Stéphane
>>
>> 2017-07-21 13:23 GMT+02:00 Chris Lamb :
>> >
>> > Stéphane,
>> >
>> > Please upload your (built)  package somewhere and I will have a look.
>> >
>> > /lamby
>> >
>> >> Hi Chris,
>> >>
>> >> Thank you for your review. I had a look at the entire package but I
>> >> did not see anything else.
>> >> I hope the copyright is fine now :
>> >> https://anonscm.debian.org/cgit/pkg-security/curvedns.git/commit/?id=dccc20efc28f4bfbf1d157bedaa46a6d9b56676b
>> >>
>> >> I also used cme update dpkg-copyright command and license-reconcile.
>> >>
>> >> Just tell me if it's ok for you and I'll ask my DD to re-upload it.
>> >>
>> >> Best regards,
>> >>
>> >> Stephane
>> >>
>> >>
>> >> 2017-07-20 20:55 GMT+02:00 Chris Lamb :
>> >> > Source: curvedns
>> >> > Version: 0.87-1
>> >> > Severity: serious
>> >> > Justication: Policy 12.5
>> >> > X-Debbugs-CC: NEVEU Stephane 
>> >> >
>> >> > Hi,
>> >> >
>> >> > I just ACCEPTed curvedns from NEW but noticed it was missing
>> >> > attribution in debian/copyright for at least:
>> >> >
>> >> >   nacl/crypto_scalarmult/curve25519/donna_c64/smult.c
>> >> >
>> >> >
>> >> > (This is not exhaustive so please check over the entire package
>> >> > carefully and address these on your next upload.)
>> >> >
>> >> >
>> >> > Regards,
>> >> >
>> >> > --
>> >> >   ,''`.
>> >> >  : :'  : Chris Lamb, Debian Project Leader
>> >> >  `. `'`  la...@debian.org / chris-lamb.co.uk
>> >> >`-
>> >
>> >
>> > Regards,
>> >
>> > --
>> >   ,''`.
>> >  : :'  : Chris Lamb, Debian Project Leader
>> >  `. `'`  la...@debian.org / chris-lamb.co.uk
>> >`-
>
>
> Regards,
>
> --
>   ,''`.
>  : :'  : Chris Lamb, Debian Project Leader
>  `. `'`  la...@debian.org / chris-lamb.co.uk
>`-



Bug#840643: jessie-pu: package cups/1.7.5-11+deb8u1

2017-07-21 Thread Didier 'OdyX' Raboud
Le mardi, 27 juin 2017, 20.32:11 h CEST Cyril Brulebois a écrit :
> Assuming that this was successfully tested (including by setting those
> two options to restore support for insecure crypto) on a jessie system,
> and once you've fixed the codename in debian/changelog (you want jessie
> rather than jessie-security), feel free to upload.

Uploaded now after testing. I also fixed a typo in the changelog: AllowSSLv3 
vs AllowSSL3 (superfluous 'v').

Sorry for the delay.

Cheers,
OdyX

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


Bug#868507: Re : Re : Re : Re : Re : Re : Bug#868507: libreoffice-writer: Crash after the last upgrade

2017-07-21 Thread rene
Hi,

On Fri, Jul 21, 2017 at 02:49:00PM +0200, nicolas.patr...@gmail.com wrote:
> Le 21/07/2017 14:40:00, r...@debian.org a écrit :
> 
> > It would have been better if you  didn't file it to begin with. And
> > you didn't eben answer my intial question.. I'll repeat:
> 
> > Does it also happen without the binary nvidia drivers?
> 
[...]
> I won’t remove libreoffice-gtk3 if it works with it.

I haven't asked to do that.

> I wouldn’t have filed it if other games crashed too.
[...]
> If LO crashes back when other games crash too, I’ll tell you but I never saw 
> LO crash because of the nVidia drive
> (I use the long life version) or a conflict with X but I understand that it 
> may happen

The point why I Cc'ed Geoff in my reply was his comment to this bug:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=868507#69

--- snip ---
Running the dkms nvidia drivers.

I can run libreoffice if I start with --safe-mode and turn off opengl 
acceleration so at least there's a work-around.
--- snip ---

So is that is true it's definitely a OpenGL-problem. And either a bug in LO or 
in the nvidia drivers
(or both.)

That's why I ask again and the last time: does it work without the binary 
nvidia drivers?

Regards,

Rene



Bug#869201: [sponsorship-requests] RFS: etcd/3.1.8+dfsg-3 [NMU]

2017-07-21 Thread Harish Sriram
Package: sponsorship-requests
Severity: important

Dear Mentors,

I am looking for a sponsor for my patch fixing the bug #857842 in the package 
"etcd".
I asked in #857842 on July 11 for someone to upload the fix.

* Package name : etcd
Version : 3.1.8+dfsg-3

It builds those binary packages:

etcd
etcd-client
etcd-server
golang-etcd-server-dev

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

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

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

dget -x http://mentors.debian.net/debian/pool/main/e/etcd/etcd_3.1.8+dfsg-3.dsc

I have attached the debdiff in the bug.

diff -Nru etcd-3.1.8+dfsg/debian/changelog etcd-3.1.8+dfsg/debian/changelog
--- etcd-3.1.8+dfsg/debian/changelog2017-06-04 18:03:52.0 -0500
+++ etcd-3.1.8+dfsg/debian/changelog2017-07-21 05:49:30.0 -0500
@@ -1,3 +1,10 @@
+etcd (3.1.8+dfsg-3) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix etcd service start issue. (Closes: #866194)
+
+ -- Harish Sriram   Fri, 21 Jul 2017 05:49:30 -0500
+
 etcd (3.1.8+dfsg-2) unstable; urgency=medium
 
   * Fix upgrade problem caused by client/server package split. Thanks 
diff -Nru etcd-3.1.8+dfsg/debian/patches/etcd-service-start.patch 
etcd-3.1.8+dfsg/debian/patches/etcd-service-start.patch
--- etcd-3.1.8+dfsg/debian/patches/etcd-service-start.patch 1969-12-31 
18:00:00.0 -0600
+++ etcd-3.1.8+dfsg/debian/patches/etcd-service-start.patch 2017-07-21 
05:49:30.0 -0500
@@ -0,0 +1,15 @@
+Description: Fixes service start issue in etcd
+ This patch fixes service start for ppc64le architecture
+---
+This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
+--- a/etcdmain/etcd.go
 b/etcdmain/etcd.go
+@@ -399,7 +399,7 @@ func setupLogging(cfg *config) {
+ 
+ func checkSupportArch() {
+   // TODO qualify arm64
+-  if runtime.GOARCH == "amd64" {
++  if runtime.GOARCH == "amd64" || runtime.GOARCH == "ppc64le" {
+   return
+   }
+   if env, ok := os.LookupEnv("ETCD_UNSUPPORTED_ARCH"); ok && env == 
runtime.GOARCH {
diff -Nru etcd-3.1.8+dfsg/debian/patches/series 
etcd-3.1.8+dfsg/debian/patches/series
--- etcd-3.1.8+dfsg/debian/patches/series   2017-06-04 18:03:52.0 
-0500
+++ etcd-3.1.8+dfsg/debian/patches/series   2017-07-21 05:49:30.0 
-0500
@@ -1,3 +1,4 @@
 disable-network-tests.patch
 test_path.patch
 skip-dev-ptmx-error.patch
+etcd-service-start.patch

Harish Sriram



Bug#869202: iputils-tracepath: tracepath(8) man page mentions tracepath6, which no longer exists

2017-07-21 Thread Vincent Lefevre
Package: iputils-tracepath
Version: 3:20161105-1
Severity: minor

The tracepath(8) man page mentions tracepath6:

NAME
   tracepath, tracepath6 - traces path to a network host discovering MTU
  ^^
   along this path
[...]
   tracepath6 is good replacement for traceroute6 and classic example of
   ^^
[...]
   -l Sets  the initial packet length to pktlen instead of 65535 for
  tracepath or 128000 for tracepath6.
  ^^
[...]
OUTPUT
   root@mops:~ # tracepath6 3ffe:2400:0:109::2
 ^^

However, tracepath6 no longer exists. The Debian changelog file says:

  * Merge IPv6 support into tracepath, drop tracepath6 binary.

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

Kernel: Linux 4.11.0-2-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 iputils-tracepath depends on:
ii  libc6 2.24-12
ii  libcap2   1:2.25-1
ii  libidn11  1.33-1

iputils-tracepath recommends no packages.

Versions of packages iputils-tracepath suggests:
ii  traceroute  1:2.1.0-2

-- no debconf information



  1   2   3   >