Bug#888919: healpix-cxx FTBFS on armel: hpxtest runs into 150m timeout

[Adrian Bunk]

Source: healpix-cxx
Version: 3.30.0-7
Severity: serious

https://buildd.debian.org/status/fetch.php?pkg=healpix-cxx=armel=3.30.0-7=1516966560=0

...
make  check-TESTS
make[2]: Entering directory '/<>'
make[3]: Entering directory '/<>'
E: Build killed with signal TERM after 150 minutes of inactivity


This is caused by:

healpix-cxx (3.30.0-7) unstable; urgency=medium

  * Use Automake parallel test harness, but print test log after
test summary
...


The tests do finish, but on the non-FPU armel port hpxtest needs
longer than 150 minutes.

The timeout is for 150 minutes without console output,
making the build succeed with the serial harness that
outputs during the hpxtest run.

Bug#887004: marked as done (liborcus: segfaults while running tests)

[Debian Bug Tracking System]

Your message dated Wed, 31 Jan 2018 07:36:53 +
with message-id 
and subject line Bug#887004: fixed in liborcus 0.13.2-1
has caused the Debian Bug report #887004,
regarding liborcus: segfaults while running tests
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
887004: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887004
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: liborcus
Version: 0.13.1-3
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Hi,

liborcus/experimental recently started to FTBFS since it reproducibly
segfaults while running the tests. This is in an up-to-date
sid+experimental minimal pbuilder environment on amd64.


Making check in python
make[4]: Entering directory '/build/liborcus-0.13.1/src/python'
make  check-TESTS
make[5]: Entering directory '/build/liborcus-0.13.1/src/python'
make[6]: Entering directory '/build/liborcus-0.13.1/src/python'
PASS: ../../test/python/module.py
../../test-driver: line 107: 25497 Segmentation fault  "$@" > $log_file 2>&1
FAIL: ../../test/python/xlsx.py
PASS: ../../test/python/json.py

   liborcus 0.13.1: src/python/test-suite.log


# TOTAL: 3
# PASS:  2
# SKIP:  0
# XFAIL: 0
# FAIL:  1
# XPASS: 0
# ERROR: 0

.. contents:: :depth: 2

FAIL: ../../test/python/xlsx.py
===

FAIL ../../test/python/xlsx.py (exit status: 139)


Testsuite summary for liborcus 0.13.1

# TOTAL: 3
# PASS:  2
# SKIP:  0
# XFAIL: 0
# FAIL:  1
# XPASS: 0
# ERROR: 0

See src/python/test-suite.log

Makefile:894: recipe for target 'test-suite.log' failed
make[6]: *** [test-suite.log] Error 1
make[6]: Leaving directory '/build/liborcus-0.13.1/src/python'
Makefile:1000: recipe for target 'check-TESTS' failed
make[5]: *** [check-TESTS] Error 2
make[5]: Leaving directory '/build/liborcus-0.13.1/src/python'


Andreas


liborcus_0.13.1-3.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: liborcus
Source-Version: 0.13.2-1

We believe that the bug you reported is fixed in the latest version of
liborcus, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 887...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Rene Engelhard  (supplier of updated liborcus package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 30 Jan 2018 14:55:08 +0100
Source: liborcus
Binary: liborcus-dev liborcus-0.13-0 liborcus-spreadsheet-model-0.13-0 
python3-orcus liborcus-doc
Architecture: source amd64 all
Version: 0.13.2-1
Distribution: unstable
Urgency: medium
Maintainer: Debian LibreOffice Maintainers 
Changed-By: Rene Engelhard 
Description:
 liborcus-0.13-0 - library for processing spreadsheet documents
 liborcus-dev - library for processing spreadsheet documents -- development
 liborcus-doc - library for processing spreadsheet documents - documentation
 liborcus-spreadsheet-model-0.13-0 - library for processing spreadsheet 
documents - spreadsheet model
 python3-orcus - library for processing spreadsheet documents - python bindings
Closes: 887004
Changes:
 liborcus (0.13.2-1) unstable; urgency=medium
 .
   * New upstream version 0.13.2
 .
   * upload to unstable
 .
   * doesn't segfault anymore against a rebuilt libixion (closes: #887004=
Checksums-Sha1:
 e109474c6ed3518604966baf5b06f167c0c242e4 2485 liborcus_0.13.2-1.dsc
 2aca559bb16d76f0bc4d1ee39b30d7635a9e5aff 1816884 liborcus_0.13.2.orig.tar.xz
 db37b4b24fdcaf403850b30abb7dff5d1d10fdf9 11048 liborcus_0.13.2-1.debian.tar.xz
 e54f90d9379bee2f2754c24a6bc7b470b237afb4 5499344 
liborcus-0.13-0-dbgsym_0.13.2-1_amd64.deb
 

Bug#888915: marked as done (didjvu fails its tests in unstable)

[Debian Bug Tracking System]

Your message dated Wed, 31 Jan 2018 09:09:58 +0200
with message-id <20180131070958.GA8573@localhost>
and subject line Re: Bug#888915: didjvu fails its tests in unstable
has caused the Debian Bug report #888915,
regarding didjvu fails its tests in unstable
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
888915: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888915
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:didjvu
Version: 0.8.1-2
Severity: serious
Tags: sid buster

didjvu fails its tests in unstable,

cd tests && set -e -x; \
for python in python2.7; do \
$python /usr/bin/nosetests --all-modules --verbose; \
done
+ python2.7 /usr/bin/nosetests --all-modules --verbose
tests.test_cli.test_argument_parser.test_action_defaults('bundle',) ... ok
tests.test_cli.test_argument_parser.test_action_defaults('encode',) ... ok
tests.test_cli.test_argument_parser.test_action_defaults('separate',) ... ok
tests.test_cli.test_argument_parser.test_action_no_args('separate',) ... ok
tests.test_cli.test_argument_parser.test_action_no_args('bundle',) ... ok
tests.test_cli.test_argument_parser.test_action_no_args('encode',) ... ok
tests.test_cli.test_argument_parser.test_bad_action ... ok
tests.test_cli.test_argument_parser.test_help ... ok
tests.test_cli.test_argument_parser.test_help('bundle',) ... ok
tests.test_cli.test_argument_parser.test_help('encode',) ... ok
tests.test_cli.test_argument_parser.test_help('separate',) ... ok
tests.test_cli.test_argument_parser.test_init ... ok
tests.test_cli.test_argument_parser.test_no_args ... ok
tests.test_cli.test_range_int.test_gt_max ... ok
tests.test_cli.test_range_int.test_lt_min ... ok
tests.test_cli.test_range_int.test_max ... ok
tests.test_cli.test_range_int.test_min ... ok
tests.test_cli.test_range_int.test_non_int ... ok
tests.test_cli.test_slice_type.test_comma ... ok
tests.test_cli.test_slice_type.test_comma_1 ... ok
tests.test_cli.test_slice_type.test_comma_eq ... ok
tests.test_cli.test_slice_type.test_comma_lt ... ok
tests.test_cli.test_slice_type.test_negative ... ok
tests.test_cli.test_slice_type.test_non_int ... ok
tests.test_cli.test_slice_type.test_plus ... ok
tests.test_cli.test_slice_type.test_plus_1 ... ok
tests.test_cli.test_slice_type.test_plus_eq ... ok
tests.test_cli.test_slice_type.test_plus_lt ... ok
tests.test_cli.test_slice_type.test_positive ... ok
tests.test_cli.test_slice_type.test_positive_1 ... ok
tests.test_cli.test_slice_type.test_zero ... ok
tests.test_cli.test_slice_type.test_zero_1 ... ok
tests.test_cli.test_slice_repr ... ok
tests.test_cli.test_intact ... ok
tests.test_cli.test_replace_underscores ... ok
tests.test_djvu.test_multichunk.test_incl ... ok
tests.test_djvu.test_multichunk.test_sjbz ... ok
tests.test_djvu.test_validate_page_id.test_bad_char ... ok
tests.test_djvu.test_validate_page_id.test_bad_extension ... ok
tests.test_djvu.test_validate_page_id.test_dot_dot ... ok
tests.test_djvu.test_validate_page_id.test_empty ... ok
tests.test_djvu.test_validate_page_id.test_leading_bad_char ... ok
tests.test_djvu.test_validate_page_id.test_ok ... ok
tests.test_djvu.test_bitonal_to_djvu ... ok
tests.test_djvu.test_photo_to_djvu ... TIFFReadScanline: scanline oriented
access is not supported for downsampled JPEG compressed images, consider
enabling TIFF_JPEGCOLORMODE as JPEGCOLORMODE_RGB..
ERROR
tests.test_djvu.test_djvu_iw44 ... ok
tests.test_filetype.test_djvu ... ok
tests.test_filetype.test_bad ... ok
tests.test_fs.test_copy_file ... ok
tests.test_fs.test_replace_ext ... ok
tests.test_gamera.test_methods.test_color('bernsen',) ... TIFFReadScanline:
scanline oriented access is not supported for downsampled JPEG compressed
images, consider enabling TIFF_JPEGCOLORMODE as JPEGCOLORMODE_RGB..
ERROR
tests.test_gamera.test_methods.test_color('tsai',) ... TIFFReadScanline:
scanline oriented access is not supported for downsampled JPEG compressed
images, consider enabling TIFF_JPEGCOLORMODE as JPEGCOLORMODE_RGB..
ERROR
tests.test_gamera.test_methods.test_color('global', {'threshold': 42}) ...
TIFFReadScanline: scanline oriented access is not supported for downsampled JPEG
compressed images, consider enabling TIFF_JPEGCOLORMODE as JPEGCOLORMODE_RGB..
ERROR
tests.test_gamera.test_methods.test_color('djvu',) ... TIFFReadScanline:
scanline oriented access is not supported for downsampled JPEG compressed
images, consider enabling TIFF_JPEGCOLORMODE as JPEGCOLORMODE_RGB..
ERROR
tests.test_gamera.test_methods.test_color('white-rohrer',) ... TIFFReadScanline:
scanline oriented access is not supported for 

Processed: Correct the found version

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> notfound 888912 8.2-1
Bug #888912 [src:sagemath] sagemath test failures with mpfr 4.0.0 and several 
architectures
The source 'sagemath' and version '8.2-1' do not appear to match any binary 
packages
No longer marked as found in versions sagemath/8.2-1.
> found 888912 8.1-2
Bug #888912 [src:sagemath] sagemath test failures with mpfr 4.0.0 and several 
architectures
Marked as found in versions sagemath/8.1-2.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
888912: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888912
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#888917: ocrmypdf fails to run it's testsuite

[Matthias Klose]

Package: src:ocrmypdf
Version: 5.5-2
Severity: serious
Tags: sid buster

The recent changelog reads:

  * Disable test suite at package build time.
It now takes a prohibitively long time to run, so we are relying on
autopkgtest instead.

Sorry, but this is one of the most lame excuses I have ever seen. Trying to run
it on my laptop in unstable needs 30 seconds.  However re-enabling it and
running it reveals

  === 122 failed, 24 passed, 4 skipped in 33.92 seconds 

these results are after adding tesseract-ocr qpdf unpaper as build dependencies.

doubting that the primary reason for this change was build time ...

dpkg-buildpackage: info: source package ocrmypdf
dpkg-buildpackage: info: source version 5.5-2
dpkg-buildpackage: info: source distribution unstable
dpkg-buildpackage: info: source changed by Sean Whitton 

 dpkg-source --before-build ocrmypdf-5.5
dpkg-buildpackage: info: host architecture amd64
dpkg-source: info: using options from ocrmypdf-5.5/debian/source/options:
--single-debian-patch --auto-commit --extend-diff-ignore=\.git_archival\.txt
 fakeroot debian/rules clean
dh clean --with python3,sphinxdoc --buildsystem=pybuild
   dh_auto_clean -O--buildsystem=pybuild
I: pybuild base:184: python3.6 setup.py clean
Skipping external program tests because of --force
running clean
removing '/home/packages/tmp/ocrmypdf-5.5/.pybuild/pythonX.Y_3.6/build' (and
everything under it)
'build/bdist.linux-amd64' does not exist -- can't clean it
'build/scripts-3.6' does not exist -- can't clean it
   dh_clean -O--buildsystem=pybuild
 debian/rules build
dh build --with python3,sphinxdoc --buildsystem=pybuild
   dh_update_autotools_config -O--buildsystem=pybuild
   dh_autoreconf -O--buildsystem=pybuild
   dh_auto_configure -O--buildsystem=pybuild
I: pybuild base:184: python3.6 setup.py config
Skipping external program tests because of --force
running config
   debian/rules override_dh_auto_build
make[1]: Entering directory '/home/packages/tmp/ocrmypdf-5.5'
mkdir -p debian/.debhelper
cp -R ocrmypdf debian/.debhelper
sed -i debian/.debhelper/ocrmypdf/__init__.py -e \
"s|^__version__ =.*|__version__ = \"5.5\"|"
PYTHONPATH=debian/.debhelper sphinx-build docs html
Running Sphinx v1.6.6
making output directory...
loading pickled environment... not yet created
building [mo]: targets for 0 po files that are out of date
building [html]: targets for 10 source files that are out of date
updating environment: 10 added, 0 changed, 0 removed
reading sources... [ 10%] advanced
reading sources... [ 20%] batch
reading sources... [ 30%] cookbook
reading sources... [ 40%] errors
reading sources... [ 50%] index
reading sources... [ 60%] installation
reading sources... [ 70%] introduction
reading sources... [ 80%] languages
reading sources... [ 90%] release_notes
reading sources... [100%] security

/home/packages/tmp/ocrmypdf-5.5/docs/installation.rst:2: WARNING: Duplicate
explicit target name: "docker".
/home/packages/tmp/ocrmypdf-5.5/docs/introduction.rst:108: WARNING: Unknown
target name: "using ocrmypdf online".
looking for now-outdated files... none found
pickling environment... done
checking consistency... /home/packages/tmp/ocrmypdf-5.5/docs/installation.rst:
WARNING: document isn't included in any toctree
done
preparing documents... done
writing output... [ 10%] advanced
writing output... [ 20%] batch
writing output... [ 30%] cookbook
writing output... [ 40%] errors
writing output... [ 50%] index
writing output... [ 60%] installation
writing output... [ 70%] introduction
writing output... [ 80%] languages
writing output... [ 90%] release_notes
writing output... [100%] security

generating indices... genindex
writing additional pages... search
copying images... [100%] bitmap_vs_svg.svg

copying static files... WARNING: html_static_path entry
'/home/packages/tmp/ocrmypdf-5.5/docs/_static' does not exist
done
copying extra files... done
dumping search index in English (code: en) ... done
dumping object inventory... done
build succeeded, 4 warnings.
dh_auto_build -O--buildsystem=pybuild
I: pybuild base:184: /usr/bin/python3 setup.py build
Skipping external program tests because of --force
running build
running build_py
creating /home/packages/tmp/ocrmypdf-5.5/.pybuild/pythonX.Y_3.6/build/ocrmypdf
copying ocrmypdf/_unicodefun.py ->
/home/packages/tmp/ocrmypdf-5.5/.pybuild/pythonX.Y_3.6/build/ocrmypdf
copying ocrmypdf/__main__.py ->
/home/packages/tmp/ocrmypdf-5.5/.pybuild/pythonX.Y_3.6/build/ocrmypdf
copying ocrmypdf/pdfa.py ->
/home/packages/tmp/ocrmypdf-5.5/.pybuild/pythonX.Y_3.6/build/ocrmypdf
copying ocrmypdf/leptonica.py ->
/home/packages/tmp/ocrmypdf-5.5/.pybuild/pythonX.Y_3.6/build/ocrmypdf
copying ocrmypdf/__init__.py ->
/home/packages/tmp/ocrmypdf-5.5/.pybuild/pythonX.Y_3.6/build/ocrmypdf
copying ocrmypdf/hocrtransform.py ->
/home/packages/tmp/ocrmypdf-5.5/.pybuild/pythonX.Y_3.6/build/ocrmypdf
copying ocrmypdf/helpers.py ->

Bug#888915: didjvu fails its tests in unstable

[Matthias Klose]

Package: src:didjvu
Version: 0.8.1-2
Severity: serious
Tags: sid buster

didjvu fails its tests in unstable,

cd tests && set -e -x; \
for python in python2.7; do \
$python /usr/bin/nosetests --all-modules --verbose; \
done
+ python2.7 /usr/bin/nosetests --all-modules --verbose
tests.test_cli.test_argument_parser.test_action_defaults('bundle',) ... ok
tests.test_cli.test_argument_parser.test_action_defaults('encode',) ... ok
tests.test_cli.test_argument_parser.test_action_defaults('separate',) ... ok
tests.test_cli.test_argument_parser.test_action_no_args('separate',) ... ok
tests.test_cli.test_argument_parser.test_action_no_args('bundle',) ... ok
tests.test_cli.test_argument_parser.test_action_no_args('encode',) ... ok
tests.test_cli.test_argument_parser.test_bad_action ... ok
tests.test_cli.test_argument_parser.test_help ... ok
tests.test_cli.test_argument_parser.test_help('bundle',) ... ok
tests.test_cli.test_argument_parser.test_help('encode',) ... ok
tests.test_cli.test_argument_parser.test_help('separate',) ... ok
tests.test_cli.test_argument_parser.test_init ... ok
tests.test_cli.test_argument_parser.test_no_args ... ok
tests.test_cli.test_range_int.test_gt_max ... ok
tests.test_cli.test_range_int.test_lt_min ... ok
tests.test_cli.test_range_int.test_max ... ok
tests.test_cli.test_range_int.test_min ... ok
tests.test_cli.test_range_int.test_non_int ... ok
tests.test_cli.test_slice_type.test_comma ... ok
tests.test_cli.test_slice_type.test_comma_1 ... ok
tests.test_cli.test_slice_type.test_comma_eq ... ok
tests.test_cli.test_slice_type.test_comma_lt ... ok
tests.test_cli.test_slice_type.test_negative ... ok
tests.test_cli.test_slice_type.test_non_int ... ok
tests.test_cli.test_slice_type.test_plus ... ok
tests.test_cli.test_slice_type.test_plus_1 ... ok
tests.test_cli.test_slice_type.test_plus_eq ... ok
tests.test_cli.test_slice_type.test_plus_lt ... ok
tests.test_cli.test_slice_type.test_positive ... ok
tests.test_cli.test_slice_type.test_positive_1 ... ok
tests.test_cli.test_slice_type.test_zero ... ok
tests.test_cli.test_slice_type.test_zero_1 ... ok
tests.test_cli.test_slice_repr ... ok
tests.test_cli.test_intact ... ok
tests.test_cli.test_replace_underscores ... ok
tests.test_djvu.test_multichunk.test_incl ... ok
tests.test_djvu.test_multichunk.test_sjbz ... ok
tests.test_djvu.test_validate_page_id.test_bad_char ... ok
tests.test_djvu.test_validate_page_id.test_bad_extension ... ok
tests.test_djvu.test_validate_page_id.test_dot_dot ... ok
tests.test_djvu.test_validate_page_id.test_empty ... ok
tests.test_djvu.test_validate_page_id.test_leading_bad_char ... ok
tests.test_djvu.test_validate_page_id.test_ok ... ok
tests.test_djvu.test_bitonal_to_djvu ... ok
tests.test_djvu.test_photo_to_djvu ... TIFFReadScanline: scanline oriented
access is not supported for downsampled JPEG compressed images, consider
enabling TIFF_JPEGCOLORMODE as JPEGCOLORMODE_RGB..
ERROR
tests.test_djvu.test_djvu_iw44 ... ok
tests.test_filetype.test_djvu ... ok
tests.test_filetype.test_bad ... ok
tests.test_fs.test_copy_file ... ok
tests.test_fs.test_replace_ext ... ok
tests.test_gamera.test_methods.test_color('bernsen',) ... TIFFReadScanline:
scanline oriented access is not supported for downsampled JPEG compressed
images, consider enabling TIFF_JPEGCOLORMODE as JPEGCOLORMODE_RGB..
ERROR
tests.test_gamera.test_methods.test_color('tsai',) ... TIFFReadScanline:
scanline oriented access is not supported for downsampled JPEG compressed
images, consider enabling TIFF_JPEGCOLORMODE as JPEGCOLORMODE_RGB..
ERROR
tests.test_gamera.test_methods.test_color('global', {'threshold': 42}) ...
TIFFReadScanline: scanline oriented access is not supported for downsampled JPEG
compressed images, consider enabling TIFF_JPEGCOLORMODE as JPEGCOLORMODE_RGB..
ERROR
tests.test_gamera.test_methods.test_color('djvu',) ... TIFFReadScanline:
scanline oriented access is not supported for downsampled JPEG compressed
images, consider enabling TIFF_JPEGCOLORMODE as JPEGCOLORMODE_RGB..
ERROR
tests.test_gamera.test_methods.test_color('white-rohrer',) ... TIFFReadScanline:
scanline oriented access is not supported for downsampled JPEG compressed
images, consider enabling TIFF_JPEGCOLORMODE as JPEGCOLORMODE_RGB..
ERROR
tests.test_gamera.test_methods.test_color('abutaleb',) ... TIFFReadScanline:
scanline oriented access is not supported for downsampled JPEG compressed
images, consider enabling TIFF_JPEGCOLORMODE as JPEGCOLORMODE_RGB..
ERROR
tests.test_gamera.test_methods.test_color('shading-subtraction',) ...
TIFFReadScanline: scanline oriented access is not supported for downsampled JPEG
compressed images, consider enabling TIFF_JPEGCOLORMODE as JPEGCOLORMODE_RGB..
ERROR
tests.test_gamera.test_methods.test_color('otsu',) ... TIFFReadScanline:
scanline oriented access is not supported for downsampled JPEG compressed
images, consider enabling TIFF_JPEGCOLORMODE as JPEGCOLORMODE_RGB..
ERROR
tests.test_gamera.test_methods.test_color('brink',) ... 

Bug#887010: telegram-desktop segfaults on debian buster (amd64) using Gnome3

[Коля Гурьев]

Hi,

12.01.2018 16:31, Robin пишет:
> Versions of packages telegram-desktop depends on:
...
> pn  libtgvoip1.0 

It seems you have no installed package with libtgvoip. This may have led
to such crash.

> Setting the environment variabel 'XDG_CURRENT_DESKTOP' to 'NONE' solves the
> issue temporarily.

Does I understand correctly, Telegram works fine *some time* and then
crashes? This may be related to an incoming call that cannot be handle
properly without libtgvoip, and it's unlikely affected by the
XDG_CURRENT_DESKTOP environment variable.

Bug#880793: closed by Yaroslav Halchenko <deb...@onerussian.com> (Bug#880793: fixed in pymvpa2 2.6.4-1)

[Yaroslav Halchenko]

On Tue, 30 Jan 2018, Yaroslav Halchenko wrote:


> On Tue, 30 Jan 2018, Adrian Bunk wrote:

> > Control: reopen -1

> > On Tue, Jan 30, 2018 at 03:39:04AM +, Debian Bug Tracking System wrote:
> > >...
> > >  pymvpa2 (2.6.4-1) unstable; urgency=medium
> > >...
> > >* debian/rules
> > >  - run tests under fixed MVPA_SEED=1 to avoid surprises, so should
> > >resolve spurious FTBFS (Closes: #880793)
> > >...

> > Unfortunately this didn't fix the problem:
> >   https://buildd.debian.org/status/package.php?p=pymvpa2=sid

> Thanks for spotting it!
> yeah -- I will look "inside"

> Note that for mips64el, previous version included, failures happen on
> aql builder but not on manda:
> https://buildd.debian.org/status/logs.php?pkg=pymvpa2=mips64el
> so it is something relating to available resources on the box.  might be
> that we need to skip the test if resources are tight

FTR, I think it is an issue to be fixed in numpy itself -- that error is caused
by specifying step in np.float dtype, which leads to ValueError instead
of ZeroDivisionError as in the case of regular float:

(sid_mips64el-dchroot)yoh@eller:~/pymvpa2-2.6.4$ python -c 'import numpy as np; 
print(np.arange(-1, -1+0, 0.))'
Traceback (most recent call last):
  File "", line 1, in 
ZeroDivisionError: float division by zero

(sid_mips64el-dchroot)yoh@eller:~/pymvpa2-2.6.4$ python -c 'import numpy as np; 
print(np.arange(-1, -1+0, np.float16(0.)))'
-c:1: RuntimeWarning: invalid value encountered in true_divide
Traceback (most recent call last):
  File "", line 1, in 
ValueError: array is too big; `arr.size * arr.dtype.itemsize` is larger than 
the maximum possible size.


on my x64 laptop it is yet another kind of fun with the same version of numpy
1:1.13.3-2 :

$> python -c 'import numpy as np; print(np.arange(-1, -1+0, np.float(0.)))'
Traceback (most recent call last):
  File "", line 1, in 
ZeroDivisionError: float division by zero

$> python -c 'import numpy as np; print(np.arange(-1, -1+0, np.float64(0.)))'
-c:1: RuntimeWarning: invalid value encountered in double_scalars
[]

$> python -c 'import numpy as np; print(np.arange(-1, -1+0, np.float32(0.)))'
-c:1: RuntimeWarning: invalid value encountered in true_divide


in current numpy git, unfortunately they release from releaase branches
so hard to say 'version':

pre-removal-numpybook-5689-gbb7b12672

it is a bit more consistent but still varying:

$> PYTHONPATH=. python -c 'import numpy as np; print(np.arange(-1, -1+0, 0.))'
Traceback (most recent call last):
  File "", line 1, in 
ZeroDivisionError: float division by zero

$> PYTHONPATH=. python -c 'import numpy as np; print(np.arange(-1, -1+0, 
np.float(0.)))'
Traceback (most recent call last):
  File "", line 1, in 
ZeroDivisionError: float division by zero

$> PYTHONPATH=. python -c 'import numpy as np; print(np.arange(-1, -1+0, 
np.float64(0.)))'
-c:1: RuntimeWarning: invalid value encountered in double_scalars
Traceback (most recent call last):
  File "", line 1, in 
ValueError: arange: cannot compute length

$> PYTHONPATH=. python -c 'import numpy as np; print(np.arange(-1, -1+0, 
np.float32(0.)))'
-c:1: RuntimeWarning: invalid value encountered in true_divide
Traceback (most recent call last):
  File "", line 1, in 
ValueError: arange: cannot compute length

asked upstream: https://github.com/numpy/numpy/issues/10496

will fix up pymvpa with my patches tomorrow or so
-- 
Yaroslav O. Halchenko
Center for Open Neuroscience http://centerforopenneuroscience.org
Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755
Phone: +1 (603) 646-9834   Fax: +1 (603) 646-1419
WWW:   http://www.linkedin.com/in/yarik

Bug#866415: marked as done (basemap: depends on obsolete python-imaging (replace with python3-pil or python-pil))

[Debian Bug Tracking System]

Your message dated Wed, 31 Jan 2018 06:15:40 +0100
with message-id <44de05b4-3506-27e6-e992-3c344af6b...@debian.org>
and subject line Fixed
has caused the Debian Bug report #866415,
regarding basemap: depends on obsolete python-imaging (replace with python3-pil 
or python-pil)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
866415: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866415
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:basemap
Version: 1.0.7+dfsg-4
Severity: important
Tags: sid buster
User: d...@debian.org
Usertags: imaging-pillow

One or more binary packages built from this source depends on or
recommends python-imaging, which is obsolete for some years now.
Please build the source using the python-pil package. If your
package doesn't need to be built with Python2, please consider using
Python3 and depend on python3-pil.

Planning to remove python-imaging for the buster release, so the
severity of this issues might be raised.
--- End Message ---
--- Begin Message ---
Version: 1.1.0+dfsg-1--- End Message ---

Bug#888912: sagemath test failures with mpfr 4.0.0 and several architectures

[Matthias Klose]

Package: src:sagemath
Version: 8.2-1
Severity: serious
Tags: sid buster

see https://buildd.debian.org/status/package.php?p=sagemath=unstable

test failures on every architecture.

Bug#888911: giac test failures with mpfr 4.0.0 on several architectures

[Matthias Klose]

Package: src:giac
Version: 1.2.3.57+dfsg1-2
Severity: serious
Tags: sid buster

see https://buildd.debian.org/status/package.php?p=giac

failing tests at least on the release architectures amd64 and armhf.

Processed: tagging 887998

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 887998 + fixed-upstream
Bug #887998 {Done: Kyle Robbertze } 
[src:gnome-shell-extension-show-ip] Port from deprecated libnm-glib bindings to 
libnm
Added tag(s) fixed-upstream.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
887998: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887998
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: tagging 888000

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 888000 + fixed-upstream
Bug #888000 [src:gnome-shell-extension-disconnect-wifi] Port from deprecated 
libnm-glib bindings to libnm
Added tag(s) fixed-upstream.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
888000: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888000
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#887744: redeclipse FTBFS with glibc 2.26

[Miriam Ruiz]

I had a similar error compiling lamiae [1] and I solved it by removing
the  -ffast-math flag from src/makefile

I don't know if it would work for you, but the code base is the same,
so I assume it might be that.

Greetings,
Miry




[1] https://github.com/Hirato/lamiae

Bug#888903: jsbeautifier,node-js-beautify: both ship /usr/bin/js-beautify

[Andreas Beckmann]

Package: jsbeautifier,node-js-beautify
Severity: serious
Tags: buster sid
User: trei...@debian.org
Usertags: edos-file-overwrite
Control: found -1 1.6.4-6
Control: found -1 1.7.5+dfsg-1

Hi,

automatic installation tests of packages that share a file and at the
same time do not conflict by their package dependency relationships has
detected the following problem:

  Selecting previously unselected package node-js-beautify.
  Preparing to unpack .../12-node-js-beautify_1.7.5+dfsg-1_all.deb ...
  Unpacking node-js-beautify (1.7.5+dfsg-1) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-Vb7dNE/12-node-js-beautify_1.7.5+dfsg-1_all.deb 
(--unpack):
   trying to overwrite '/usr/bin/js-beautify', which is also in package 
jsbeautifier 1.6.4-6
  Errors were encountered while processing:
   /tmp/apt-dpkg-install-Vb7dNE/12-node-js-beautify_1.7.5+dfsg-1_all.deb


This is a serious bug as it makes installation fail, and violates
sections 7.6.1 and 10.1 of the policy. An optimal solution would
consist in only one of the packages installing that file, and renaming
or removing the file in the other package. Depending on the
circumstances you might also consider Replace relations or file
diversions. If the conflicting situation cannot be resolved then, as a
last resort, the two packages have to declare a mutual
Conflict. Please take into account that Replaces, Conflicts and
diversions should only be used when packages provide different
implementations for the same functionality.

Here is a list of files that are known to be shared by both packages
(according to the Contents file for sid/amd64, which may be
slightly out of sync):

  usr/bin/js-beautify

This bug is assigned to both packages. If you, the maintainers of
the two packages in question, have agreed on which of the packages will
resolve the problem please reassign the bug to that package. You may
also register in the BTS that the other package is affected by the bug.

If this is a source package rename, you'll need a ftp.d.o RM request
for the old package and Breaks+Replaces in the new one.


Cheers,

Andreas

PS: for more information about the detection of file overwrite errors
of this kind see https://qa.debian.org/dose/file-overwrites.html


jsbeautifier=1.6.4-6_node-js-beautify=1.7.5+dfsg-1.log.gz
Description: application/gzip

Processed: jsbeautifier,node-js-beautify: both ship /usr/bin/js-beautify

[Debian Bug Tracking System]

Processing control commands:

> found -1 1.6.4-6
Bug #888903 [jsbeautifier,node-js-beautify] jsbeautifier,node-js-beautify: both 
ship /usr/bin/js-beautify
There is no source info for the package 'node-js-beautify' at version '1.6.4-6' 
with architecture ''
Marked as found in versions python-jsbeautifier/1.6.4-6.
> found -1 1.7.5+dfsg-1
Bug #888903 [jsbeautifier,node-js-beautify] jsbeautifier,node-js-beautify: both 
ship /usr/bin/js-beautify
There is no source info for the package 'jsbeautifier' at version 
'1.7.5+dfsg-1' with architecture ''
Marked as found in versions node-js-beautify/1.7.5+dfsg-1.

-- 
888903: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888903
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#888403: ld: /usr/lib/crt0-efi-aarch64.o: relocation R_AARCH64_ABS16 against `EFI_SUBSYSTEM' can not be used when making a shared object

[Vagrant Cascadian]

Control: affects 888789 src:u-boot

On 2018-01-29, Michael Biebl wrote:
> With latest versions of binutils (including 2.30-1), ld fails to
> properly link systemd-boot on arm64.
...
> /usr/lib/crt0-efi-aarch64.o: relocation R_AARCH64_ABS16 against
> `EFI_SUBSYSTEM' can not be used when making a shared object
>
> See also 
> https://buildd.debian.org/status/fetch.php?pkg=systemd=arm64=236-4=1517247349=0
> https://buildd.debian.org/status/fetch.php?pkg=systemd=arm64=236-4=1517178536=0

This also affects u-boot with a nearly identical error:

  https://bugs.debian.org/888403

With binutils 2.29.1-13 from buster, u-boot builds fine.


live well,
  vagrant


signature.asc
Description: PGP signature

Bug#888893: password-gorilla: After upgrade, password-gorilla refuses to start with "Couldn't find the package Itcl" message

[Alexandre Raymond]

Hi Tom,

I have been able to reproduce your bug.

It will be fixed very soon.

As a workaround, you can modify the file:
/usr/share/password-gorilla/gorilla.tcl

exec tclsh8.5 "$0" ${1+"$@"}

to

exec tclsh "$0" ${1+"$@"}

to patch the issue.

Regards,
Alexandre


On Tue, Jan 30, 2018 at 4:24 PM, Tom  wrote:

> Package: password-gorilla
> Version: 1.5.3.7-1
> Severity: grave
> Justification: renders package unusable
>
> Dear Maintainer,
>
>* What led up to the situation?
>
> # apt-get update && apt-get upgrade && apt-get dist-upgrade
>
> Now, starting password-gorilla gives an error message:
> Couldn't find the package Itcl.
> Itcl is required for Password Gorilla
> The file /home/user/gorilla-debug-log was created for debugging purposes.
> Password Gorilla will now terminate.
>
>* What exactly did you do (or not do) that was effective (or
>  ineffective)?
>
> checked that itcl is indeed installed:
>
> # dpkg -l itcl3
> Desired=Unknown/Install/Remove/Purge/Hold
> | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/
> trig-aWait/Trig-pend
> |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
> ||/ Name   Version  Architecture
>Description
> +++-==--
> -===
> ===
> ii  itcl3:amd643.4.3-2  amd64
>   [incr Tcl] OOP extension for Tcl - run-time files
>
>
> -- System Information:
> Debian Release: buster/sid
>   APT prefers testing
>   APT policy: (500, 'testing')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
>
> Kernel: Linux 4.14.0-3-amd64 (SMP w/8 CPU cores)
> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
> LANGUAGE=en_US:en (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: sysvinit (via /sbin/init)
> LSM: AppArmor: enabled
>
> Versions of packages password-gorilla depends on:
> ii  itcl3   3.4.3-2
> ii  tcl8.5  8.5.19-3
> ii  tcllib  1.18-dfsg-3
> ii  tk8.5   8.5.19-2
> ii  tklib   0.6-3
>
> password-gorilla recommends no packages.
>
> password-gorilla suggests no packages.
>
> -- no debconf information
>

Bug#880793: closed by Yaroslav Halchenko <deb...@onerussian.com> (Bug#880793: fixed in pymvpa2 2.6.4-1)

[Yaroslav Halchenko]

On Tue, 30 Jan 2018, Yaroslav Halchenko wrote:


> On Tue, 30 Jan 2018, Adrian Bunk wrote:

> > Control: reopen -1

> > On Tue, Jan 30, 2018 at 03:39:04AM +, Debian Bug Tracking System wrote:
> > >...
> > >  pymvpa2 (2.6.4-1) unstable; urgency=medium
> > >...
> > >* debian/rules
> > >  - run tests under fixed MVPA_SEED=1 to avoid surprises, so should
> > >resolve spurious FTBFS (Closes: #880793)
> > >...

> > Unfortunately this didn't fix the problem:
> >   https://buildd.debian.org/status/package.php?p=pymvpa2=sid

> Thanks for spotting it!
> yeah -- I will look "inside"

> Note that for mips64el, previous version included, failures happen on
> aql builder but not on manda:
> https://buildd.debian.org/status/logs.php?pkg=pymvpa2=mips64el
> so it is something relating to available resources on the box.  might be
> that we need to skip the test if resources are tight

ah -- and I was chasing the same issue today on conda builds with newer
numpy, it was giving me a different exception though.  I might just
adopt the same patches I did for conda.  Should resolve without me
digging in (unless I could reproduce since I am still intrigued what is
the actual reason)

-- 
Yaroslav O. Halchenko
Center for Open Neuroscience http://centerforopenneuroscience.org
Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755
Phone: +1 (603) 646-9834   Fax: +1 (603) 646-1419
WWW:   http://www.linkedin.com/in/yarik


signature.asc
Description: PGP signature

Bug#880793: closed by Yaroslav Halchenko <deb...@onerussian.com> (Bug#880793: fixed in pymvpa2 2.6.4-1)

[Yaroslav Halchenko]

On Tue, 30 Jan 2018, Adrian Bunk wrote:

> Control: reopen -1

> On Tue, Jan 30, 2018 at 03:39:04AM +, Debian Bug Tracking System wrote:
> >...
> >  pymvpa2 (2.6.4-1) unstable; urgency=medium
> >...
> >* debian/rules
> >  - run tests under fixed MVPA_SEED=1 to avoid surprises, so should
> >resolve spurious FTBFS (Closes: #880793)
> >...

> Unfortunately this didn't fix the problem:
>   https://buildd.debian.org/status/package.php?p=pymvpa2=sid

Thanks for spotting it!
yeah -- I will look "inside"

Note that for mips64el, previous version included, failures happen on
aql builder but not on manda:
https://buildd.debian.org/status/logs.php?pkg=pymvpa2=mips64el
so it is something relating to available resources on the box.  might be
that we need to skip the test if resources are tight

-- 
Yaroslav O. Halchenko
Center for Open Neuroscience http://centerforopenneuroscience.org
Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755
Phone: +1 (603) 646-9834   Fax: +1 (603) 646-1419
WWW:   http://www.linkedin.com/in/yarik

Bug#888893: password-gorilla: After upgrade, password-gorilla refuses to start with "Couldn't find the package Itcl" message

[Tom]

Package: password-gorilla
Version: 1.5.3.7-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

   * What led up to the situation?

# apt-get update && apt-get upgrade && apt-get dist-upgrade

Now, starting password-gorilla gives an error message:
Couldn't find the package Itcl.
Itcl is required for Password Gorilla
The file /home/user/gorilla-debug-log was created for debugging purposes.
Password Gorilla will now terminate.

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

checked that itcl is indeed installed:

# dpkg -l itcl3
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name   Version  Architecture 
Description
+++-==---==
ii  itcl3:amd643.4.3-2  amd64
[incr Tcl] OOP extension for Tcl - run-time files 


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

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

Versions of packages password-gorilla depends on:
ii  itcl3   3.4.3-2
ii  tcl8.5  8.5.19-3
ii  tcllib  1.18-dfsg-3
ii  tk8.5   8.5.19-2
ii  tklib   0.6-3

password-gorilla recommends no packages.

password-gorilla suggests no packages.

-- no debconf information

Processed: Re: Bug#888877: llvm-toolchain-6.0: FTBFS on arm64: /usr/bin/ld.gold: unsupported TLSLE reloc 549 in shared code

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> forwarded 77 https://bugs.llvm.org/show_bug.cgi?id=36051
Bug #77 [src:llvm-toolchain-6.0] llvm-toolchain-6.0: FTBFS on arm64: 
/usr/bin/ld.gold: unsupported TLSLE reloc 549 in shared code
Set Bug forwarded-to-address to 'https://bugs.llvm.org/show_bug.cgi?id=36051'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
77: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=77
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#888877: llvm-toolchain-6.0: FTBFS on arm64: /usr/bin/ld.gold: unsupported TLSLE reloc 549 in shared code

[Sylvestre Ledru]

forwarded 77 https://bugs.llvm.org/show_bug.cgi?id=36051
thanks

On 30/01/2018 20:57, Emilio Pozuelo Monfort wrote:
> Source: llvm-toolchain-6.0
> Version: 1:6.0~+rc1-1
> Severity: serious
> 
> Hi,
> 
> There are old 6.0 binaries lying around from old llvm-toolchain-snapshot
> versions, so this is RC as those binaries will prevent llvm-toolchain-6.0
> from migrating to testing.
> 

I forwarded this a week ago and it should be fixed in rc2.

Sylvestre

Bug#888890: [libtk-img] Undefined symbol: inflateValidate

[Ole Streicher]

Package: libtk-img
Version: 1:1.4.7+dfsg-1
Severity: serious
Affects: saods9

Dear maintainer,

The newly uploaded libtk-img cannot be loaded from within tk:

$ wish
% package require img::tiff
couldn't load file
"/usr/lib/tcltk/x86_64-linux-gnu/Img1.4.7/libzlibtcl1.2.11.so":
/usr/lib/tcltk/x86_64-linux-gnu/Img1.4.7/libzlibtcl1.2.11.so: undefined
symbol: inflateValidate
%

This affects saods9, which shows this as a failure in the last CI test

https://ci.debian.net/data/autopkgtest/unstable/amd64/s/saods9/20180130_115901/log.gz

Cheers

Ole

Bug#880793: closed by Yaroslav Halchenko <deb...@onerussian.com> (Bug#880793: fixed in pymvpa2 2.6.4-1)

[Adrian Bunk]

Control: reopen -1

On Tue, Jan 30, 2018 at 03:39:04AM +, Debian Bug Tracking System wrote:
>...
>  pymvpa2 (2.6.4-1) unstable; urgency=medium
>...
>* debian/rules
>  - run tests under fixed MVPA_SEED=1 to avoid surprises, so should
>resolve spurious FTBFS (Closes: #880793)
>...

Unfortunately this didn't fix the problem:
  https://buildd.debian.org/status/package.php?p=pymvpa2=sid

cu
Adrian

-- 

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

Processed: Re: Bug#880793 closed by Yaroslav Halchenko <deb...@onerussian.com> (Bug#880793: fixed in pymvpa2 2.6.4-1)

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #880793 {Done: Yaroslav Halchenko } [src:pymvpa2] 
pymvpa2 FTBFS on mips64el: ValueError: array is too big; `arr.size * 
arr.dtype.itemsize` is larger than the maximum possible size.
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions pymvpa2/2.6.4-1.

-- 
880793: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=880793
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#888881: php-mongodb FTBFS with PHP 7.2: error: 'timelib_time {aka struct _timelib_time}' has no member named 'f'

[Adrian Bunk]

Source: php-mongodb
Version: 1.2.3-1
Severity: serious
Tags: buster sid

https://buildd.debian.org/status/package.php?p=php-mongodb=sid

...
/<>/build-7.2/src/BSON/UTCDateTime.c: In function 
'php_phongo_utcdatetime_init_from_date':
/<>/build-7.2/src/BSON/UTCDateTime.c:145:43: error: 'timelib_time 
{aka struct _timelib_time}' has no member named 'f'
  usec = (int64_t) floor(datetime_obj->time->f * 100 + 0.5);
   ^~
/<>/build-7.2/src/BSON/UTCDateTime.c: In function 
'zim_UTCDateTime_toDateTime':
/<>/build-7.2/src/BSON/UTCDateTime.c:276:20: error: 'timelib_time 
{aka struct _timelib_time}' has no member named 'f'
  datetime_obj->time->f = (double) (intern->milliseconds % 1000) / 1000;
^~
Makefile:345: recipe for target 'src/BSON/UTCDateTime.lo' failed
make[2]: *** [src/BSON/UTCDateTime.lo] Error 1

Bug#888880: php-solr FTBFS with PHP 7.2: error: 'ZEND_ACC_CLONE' undeclared here

[Adrian Bunk]

Source: php-solr
Version: 2.4.0-4
Severity: serious
Tags: buster sid

https://buildd.debian.org/status/package.php?p=php-solr=sid

...
In file included from /usr/include/php/20170718/main/php.h:40:0,
 from /<>/build-7.2/src/php7/php_solr.h:28,
 from /<>/build-7.2/src/php7/php_solr.c:23:
/<>/build-7.2/src/php7/php_solr.c:560:56: error: 'ZEND_ACC_CLONE' 
undeclared here (not in a function); did you mean 'ZEND_AST_CLONE'?
  PHP_ME(SolrDocument, __clone, NULL, ZEND_ACC_PUBLIC | ZEND_ACC_CLONE)
^
/usr/include/php/20170718/Zend/zend_API.h:70:157: note: in definition of macro 
'ZEND_FENTRY'
 #define ZEND_FENTRY(zend_name, name, arg_info, flags) { #zend_name, name, 
arg_info, (uint32_t) (sizeof(arg_info)/sizeof(struct 
_zend_internal_arg_info)-1), flags },

 
^
/usr/include/php/20170718/main/php.h:423:25: note: in expansion of macro 
'ZEND_ME'
 #define PHP_ME  ZEND_ME
 ^~~
/<>/build-7.2/src/php7/php_solr.c:560:2: note: in expansion of 
macro 'PHP_ME'
  PHP_ME(SolrDocument, __clone, NULL, ZEND_ACC_PUBLIC | ZEND_ACC_CLONE)
  ^~

Bug#888879: rheolef FTBFS on several architectures: test runs forever

[Adrian Bunk]

Source: rheolef
Version: 6.7-5
Severity: serious

https://buildd.debian.org/status/package.php?p=rheolef=sid

...
  mpirun -np 1 ./form_mass_bdr_tst -app P2 -weight yz -I my_cube_TP-5-v2 
left >/dev/null 2>/dev/null
  mpirun -np 2 ./form_mass_bdr_tst -app P2 -weight yz -I my_cube_TP-5-v2 
left >/dev/null 2>/dev/null
  mpirun -np 3 ./form_mass_bdr_tst -app P2 -weight yz -I my_cube_TP-5-v2 
left >/dev/null 2>/dev/null
  mpirun -np 1 ./form_mass_bdr_tst -app P2 -weight yz -I my_cube_TP-5-v2 
right >/dev/null 2>/dev/null
  mpirun -np 2 ./form_mass_bdr_tst -app P2 -weight yz -I my_cube_TP-5-v2 
right >/dev/null 2>/dev/null
E: Build killed with signal TERM after 150 minutes of inactivity


I've reproduced this on i386, two processes are running
forever (aborted after 6 hours on a fast CPU) with 100% CPU.

Backtraces:

Thread 3 (Thread 0xf50ffb40 (LWP 29032)):
#0  0xf7ed6db9 in __kernel_vsyscall ()
#1  0xf70fabd3 in __GI___poll (fds=0xf47005d0, nfds=2, timeout=360) at 
../sysdeps/unix/sysv/linux/poll.c:29
#2  0xf5caed4a in poll (__timeout=360, __nfds=2, __fds=0xf47005d0) at 
/usr/include/i386-linux-gnu/bits/poll2.h:46
#3  poll_dispatch (base=0x578eb9c0, tv=0xf50f9bfc) at poll.c:165
#4  0xf5ca59e9 in opal_libevent2022_event_base_loop (base=, 
flags=) at event.c:1630
#5  0xf5c6b3bd in progress_engine (obj=0x578eb950) at 
runtime/opal_progress_threads.c:105
#6  0xf5df6316 in start_thread (arg=0xf50ffb40) at pthread_create.c:465
#7  0xf7105296 in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:108

Thread 2 (Thread 0xf5ac5b40 (LWP 29031)):
#0  0xf7ed6db9 in __kernel_vsyscall ()
#1  0xf71053fa in __GI_epoll_pwait (epfd=7, events=0x578ea930, maxevents=32, 
timeout=-1, set=0x0)
at ../sysdeps/unix/sysv/linux/epoll_pwait.c:42
#2  0xf710569a in epoll_wait (epfd=7, events=0x578ea930, maxevents=32, 
timeout=-1)
at ../sysdeps/unix/sysv/linux/epoll_wait.c:30
#3  0xf5ca199a in epoll_dispatch (base=0x578ea7a0, tv=0x0) at epoll.c:407
#4  0xf5ca59e9 in opal_libevent2022_event_base_loop (base=, 
flags=) at event.c:1630
#5  0xf5af23eb in progress_engine (obj=0x578ea7a0) at 
src/util/progress_threads.c:52
#6  0xf5df6316 in start_thread (arg=0xf5ac5b40) at pthread_create.c:465
#7  0xf7105296 in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:108

Thread 1 (Thread 0xf5b4fe00 (LWP 29002)):
#0  0xf7ed67f5 in ?? ()
#1  0xf7ed6b43 in __vdso_clock_gettime ()
#2  0xf7112961 in __GI___clock_gettime (clock_id=1, tp=0xffb74194) at 
../sysdeps/unix/clock_gettime.c:115
#3  0xf5cc3297 in opal_timer_linux_get_usec_clock_gettime () at 
timer_linux_component.c:197
#4  0xf5c669c3 in opal_progress () at runtime/opal_progress.c:197
#5  0xf74b5e05 in sync_wait_st (sync=) at 
../opal/threads/wait_sync.h:80
#6  ompi_request_default_wait_all (count=2, requests=0xffb742e4, statuses=0x0) 
at request/req_wait.c:221
#7  0xf750640d in ompi_coll_base_allreduce_intra_recursivedoubling 
(sbuf=0x57951030, rbuf=0x57a9b400, count=2, 
dtype=0xf7565140 , op=0xf7573e60 , 
comm=0xf7569520 , 
module=0x57976fa0) at base/coll_base_allreduce.c:225
#8  0xe991f640 in ompi_coll_tuned_allreduce_intra_dec_fixed (sbuf=0x57951030, 
rbuf=0x57a9b400, count=2, 
dtype=0xf7565140 , op=0xf7573e60 , 
comm=0xf7569520 , 
module=0x57976fa0) at coll_tuned_decision_fixed.c:66
#9  0xf74c5b77 in PMPI_Allreduce (sendbuf=0x57951030, recvbuf=0x57a9b400, 
count=2, 
datatype=0xf7565140 , op=0xf7573e60 , 
comm=0xf7569520 )
at pallreduce.c:107
#10 0xf7b476cf in boost::mpi::detail::all_reduce_impl > (comm=..., 
in_values=0x57951030, n=n@entry=2, out_values=0x57a9b400) at 
/usr/include/boost/mpi/collectives/all_reduce.hpp:36
#11 0xf7b58fc0 in boost::mpi::all_reduce 
> (out_values=, n=2, 
in_values=, comm=..., op=...) at 
/usr/include/boost/mpi/collectives/all_reduce.hpp:93
#12 rheolef::mpi_assembly_begin >, rheolef::disarray_rep::message_type, 
rheolef::apply_iterator, rheolef::first_op > > (stash=..., first_stash_idx=..., 
last_stash_idx=..., ownership=..., receive=..., send=...) at 
../../include/rheolef/mpi_assembly_begin.h:113
#13 0xf7b5a346 in rheolef::disarray_rep::dis_entry_assembly_begin 
(this=0x57acab70, my_set_op=...)
at ../../include/rheolef/disarray_mpi.icc:223
#14 rheolef::disarray::dis_entry_assembly_begin (this=) at ../../include/rheolef/disarray.h:592
#15 rheolef::disarray::dis_entry_assembly (this=) 
at ../../include/rheolef/disarray.h:594
#16 rheolef::geo_rep::set_element_side_index 
(this=, 
side_dim=) at geo_mpi_get.cc:461
#17 0xf7b5f25a in rheolef::geo_rep::get 
(this=, 

Bug#888878: fails to restore signed backup

[Erwan David]

Package: duplicity
Version: 0.7.11-1
Severity: grave

When trying to restore a signed backup, with -v 8 I get following
error
Volume was signed by key EE04D0D2B40F856F, not 0xEE04D0D2B40F856F

Then duplicity hangs (in a futex system call checked by strace).

Command was generated by duply as :
duplicity --archive-dir /var/cache/duplicity --name duply_nextcloud
--encrypt-key 0xEE04D0D2B40F856F --encrypt-key 0xB80EAC15E40FFD0F
--sign-key 0xEE04D0D2B40F856F --verbosity 8 --full-if-older-than 3M
--volsize 512 --asynchronous-upload --restore-time now
--file-to-restore appdata_octkce7gulir
pexpect+sftp://syno-bac...@rotonde.depot.rail.eu.org/home/nextcloud
appdata_octkce7gulir



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

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

Versions of packages duplicity depends on:
ii  libc62.19-18+deb8u10
ii  librsync10.9.7-10
ii  python   2.7.9-1
ii  python-lockfile  1:0.12.2-2
pn  python:any   

Versions of packages duplicity recommends:
ii  python-oauthlib  0.6.3-1
ii  python-paramiko  1.15.1-1
ii  python-urllib3   1.16-1~bpo8+1
ii  rsync3.1.1-3+deb8u1

Versions of packages duplicity suggests:
ii  lftp4.6.0-1+deb8u1
ii  ncftp   2:3.2.5-1.1
ii  python-boto 2.34.0-2
ii  python-cloudfiles   1.7.11-3
ii  python-gdata2.0.18+dfsg1-2
pn  python-swiftclient  
pn  tahoe-lafs  

-- no debconf information

Processed: raising severity of this report

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #885407 [cdbs] debhelper class broken in compat level 11 (dh_systemd_enable 
deprecated)
Severity set to 'serious' from 'normal'

-- 
885407: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885407
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#888877: llvm-toolchain-6.0: FTBFS on arm64: /usr/bin/ld.gold: unsupported TLSLE reloc 549 in shared code

[Emilio Pozuelo Monfort]

Source: llvm-toolchain-6.0
Version: 1:6.0~+rc1-1
Severity: serious

Hi,

There are old 6.0 binaries lying around from old llvm-toolchain-snapshot
versions, so this is RC as those binaries will prevent llvm-toolchain-6.0
from migrating to testing.

[ 42%] Linking CXX shared library 
../../../../lib/clang/6.0.0/lib/linux/libclang_rt.hwasan-aarch64.so
cd 
"/<>/llvm-toolchain-6.0-6.0~+rc1/build-llvm/projects/compiler-rt/lib/hwasan"
 && /usr/bin/cmake -E cmake_link_script 
CMakeFiles/clang_rt.hwasan-dynamic-aarch64.dir/link.txt --verbose=1
/usr/bin/g++-7 -fPIC -std=c++0x -fuse-ld=gold -Wl,--no-keep-files-mapped 
-Wl,--no-map-whole-files -fPIC -fvisibility-inlines-hidden -Werror=date-time 
-std=c++11 -Wall -W -Wno-unused-parameter -Wwrite-strings -Wcast-qual 
-Wno-missing-field-initializers -pedantic -Wno-long-long 
-Wno-maybe-uninitialized -Wdelete-non-virtual-dtor -Wno-comment 
-ffunction-sections -fdata-sections -Wall -std=c++11 -Wno-unused-parameter -O2 
-DNDEBUG  -march=armv8-a -nodefaultlibs 
-Wl,--version-script,/<>/llvm-toolchain-6.0-6.0~+rc1/build-llvm/projects/compiler-rt/lib/hwasan/clang_rt.hwasan-dynamic-aarch64.vers
 -Wl,-z,relro -Wl,-z,defs -Wl,-z,nodelete -shared 
-Wl,-soname,libclang_rt.hwasan-aarch64.so -o 
../../../../lib/clang/6.0.0/lib/linux/libclang_rt.hwasan-aarch64.so 
CMakeFiles/RTHwasan_dynamic.aarch64.dir/hwasan.cc.o 
CMakeFiles/RTHwasan_dynamic.aarch64.dir/hwasan_allocator.cc.o 
CMakeFiles/RTHwasan_dynamic.aarch64.dir/hwasan_interceptors.cc.o 
CMakeFiles/RTHwasan_dynamic.aarch64.dir/hwasan_linux.cc.o 
CMakeFiles/RTHwasan_dynamic.aarch64.dir/hwasan_report.cc.o 
CMakeFiles/RTHwasan_dynamic.aarch64.dir/hwasan_thread.cc.o 
CMakeFiles/RTHwasan_dynamic.aarch64.dir/hwasan_poisoning.cc.o 
../interception/CMakeFiles/RTInterception.aarch64.dir/interception_linux.cc.o 
../interception/CMakeFiles/RTInterception.aarch64.dir/interception_mac.cc.o 
../interception/CMakeFiles/RTInterception.aarch64.dir/interception_win.cc.o 
../interception/CMakeFiles/RTInterception.aarch64.dir/interception_type_test.cc.o
 
../sanitizer_common/CMakeFiles/RTSanitizerCommon.aarch64.dir/sanitizer_allocator.cc.o
 
../sanitizer_common/CMakeFiles/RTSanitizerCommon.aarch64.dir/sanitizer_common.cc.o
 
../sanitizer_common/CMakeFiles/RTSanitizerCommon.aarch64.dir/sanitizer_deadlock_detector1.cc.o
 
../sanitizer_common/CMakeFiles/RTSanitizerCommon.aarch64.dir/sanitizer_deadlock_detector2.cc.o
 
../sanitizer_common/CMakeFiles/RTSanitizerCommon.aarch64.dir/sanitizer_errno.cc.o
 
../sanitizer_common/CMakeFiles/RTSanitizerCommon.aarch64.dir/sanitizer_file.cc.o
 
../sanitizer_common/CMakeFiles/RTSanitizerCommon.aarch64.dir/sanitizer_flags.cc.o
 
../sanitizer_common/CMakeFiles/RTSanitizerCommon.aarch64.dir/sanitizer_flag_parser.cc.o
 
../sanitizer_common/CMakeFiles/RTSanitizerCommon.aarch64.dir/sanitizer_fuchsia.cc.o
 
../sanitizer_common/CMakeFiles/RTSanitizerCommon.aarch64.dir/sanitizer_libc.cc.o
 
../sanitizer_common/CMakeFiles/RTSanitizerCommon.aarch64.dir/sanitizer_libignore.cc.o
 
../sanitizer_common/CMakeFiles/RTSanitizerCommon.aarch64.dir/sanitizer_linux.cc.o
 
../sanitizer_common/CMakeFiles/RTSanitizerCommon.aarch64.dir/sanitizer_linux_s390.cc.o
 
../sanitizer_common/CMakeFiles/RTSanitizerCommon.aarch64.dir/sanitizer_mac.cc.o 
../sanitizer_common/CMakeFiles/RTSanitizerCommon.aarch64.dir/sanitizer_persistent_allocator.cc.o
 
../sanitizer_common/CMakeFiles/RTSanitizerCommon.aarch64.dir/sanitizer_platform_limits_linux.cc.o
 
../sanitizer_common/CMakeFiles/RTSanitizerCommon.aarch64.dir/sanitizer_platform_limits_netbsd.cc.o
 
../sanitizer_common/CMakeFiles/RTSanitizerCommon.aarch64.dir/sanitizer_platform_limits_posix.cc.o
 
../sanitizer_common/CMakeFiles/RTSanitizerCommon.aarch64.dir/sanitizer_platform_limits_solaris.cc.o
 
../sanitizer_common/CMakeFiles/RTSanitizerCommon.aarch64.dir/sanitizer_posix.cc.o
 
../sanitizer_common/CMakeFiles/RTSanitizerCommon.aarch64.dir/sanitizer_printf.cc.o
 
../sanitizer_common/CMakeFiles/RTSanitizerCommon.aarch64.dir/sanitizer_procmaps_common.cc.o
 
../sanitizer_common/CMakeFiles/RTSanitizerCommon.aarch64.dir/sanitizer_procmaps_freebsd.cc.o
 
../sanitizer_common/CMakeFiles/RTSanitizerCommon.aarch64.dir/sanitizer_procmaps_linux.cc.o
 
../sanitizer_common/CMakeFiles/RTSanitizerCommon.aarch64.dir/sanitizer_procmaps_mac.cc.o
 
../sanitizer_common/CMakeFiles/RTSanitizerCommon.aarch64.dir/sanitizer_procmaps_solaris.cc.o
 
../sanitizer_common/CMakeFiles/RTSanitizerCommon.aarch64.dir/sanitizer_solaris.cc.o
 
../sanitizer_common/CMakeFiles/RTSanitizerCommon.aarch64.dir/sanitizer_stackdepot.cc.o
 
../sanitizer_common/CMakeFiles/RTSanitizerCommon.aarch64.dir/sanitizer_stacktrace.cc.o
 
../sanitizer_common/CMakeFiles/RTSanitizerCommon.aarch64.dir/sanitizer_stacktrace_printer.cc.o
 
../sanitizer_common/CMakeFiles/RTSanitizerCommon.aarch64.dir/sanitizer_stoptheworld_mac.cc.o
 
../sanitizer_common/CMakeFiles/RTSanitizerCommon.aarch64.dir/sanitizer_suppressions.cc.o
 

Processed: nodejs: s390x uses illegal instructions on Z10

[Debian Bug Tracking System]

Processing control commands:

> block 886294 with -1
Bug #886294 [release.debian.org] transition: nodejs
886294 was not blocked by any bugs.
886294 was not blocking any bugs.
Added blocking bug(s) of 886294: 76

-- 
886294: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886294
76: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=76
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#888876: nodejs: s390x uses illegal instructions on Z10

[Emilio Pozuelo Monfort]

Source: nodejs
Version: 8.9.3~dfsg-11
Severity: serious
Control: block 886294 with -1

Hi,

Adding a bug against nodejs to track it.

The newer version of nodejs in unstable has introduced a regression
on Z10 and older processors, as it's using instructions only available
on newer processors, causing illegal instructions on Z10 and older.

See #886294 for more details.

Cheers,
Emilio

Bug#888874: exiv2: CVE-2017-11553

[Salvatore Bonaccorso]

Source: exiv2
Version: 0.26-1
Severity: grave
Tags: security upstream
Forwarded: https://github.com/Exiv2/exiv2/issues/54

Hi,

the following vulnerability was published for exiv2, only experimental
is affected.

CVE-2017-11553[0]:
| There is an illegal address access in the extend_alias_table function
| in localealias.c of Exiv2 0.26. A crafted input will lead to remote
| denial of service.

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-11553
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-11553
[1] https://github.com/Exiv2/exiv2/issues/54

Regards,
Salvatore

Bug#888873: exiv2: CVE-2017-12955

[Salvatore Bonaccorso]

Source: exiv2
Version: 0.26-1
Severity: grave
Tags: security upstream
Forwarded: https://github.com/Exiv2/exiv2/issues/58

Hi,

the following vulnerability was published for exiv2, only affecting
experimental version.

CVE-2017-12955[0]:
| There is a heap-based buffer overflow in basicio.cpp of Exiv2 0.26. The
| vulnerability causes an out-of-bounds write in
| Exiv2::Image::printIFDStructure(), which may lead to remote denial of
| service or possibly unspecified other impact.

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-12955
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-12955
[1] https://github.com/Exiv2/exiv2/issues/58

Regards,
Salvatore

Bug#888872: exiv2: CVE-2017-12956

[Salvatore Bonaccorso]

Source: exiv2
Version: 0.26-1
Severity: grave
Tags: security upstream
Forwarded: https://github.com/Exiv2/exiv2/issues/59

Hi,

the following vulnerability was published for exiv2, only affecting
experimental.

CVE-2017-12956[0]:
| There is an illegal address access in Exiv2::FileIo::path[abi:cxx11]()
| in basicio.cpp of libexiv2 in Exiv2 0.26 that will lead to remote
| denial of service.

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-12956
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-12956
[1] https://github.com/Exiv2/exiv2/issues/59

Regards,
Salvatore

Bug#888869: exiv2: CVE-2017-14857

[Salvatore Bonaccorso]

Source: exiv2
Version: 0.26-1
Severity: grave
Tags: security upstream
Forwarded: https://github.com/Exiv2/exiv2/issues/76

Hi,

the following vulnerability was published for exiv2, only affecting
the experimental version.

CVE-2017-14857[0]:
| In Exiv2 0.26, there is an invalid free in the Image class in image.cpp
| that leads to a Segmentation fault. A crafted input will lead to a
| denial of service attack.

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-14857
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-14857
[1] https://github.com/Exiv2/exiv2/issues/76

Regards,
Salvatore

Bug#888867: exiv2: CVE-2017-14860

[Salvatore Bonaccorso]

Source: exiv2
Version: 0.26-1
Severity: grave
Tags: security upstream
Forwarded: https://github.com/Exiv2/exiv2/issues/71

Hi,

the following vulnerability was published for exiv2, only affecting
the experimental version.

CVE-2017-14860[0]:
| There is a heap-based buffer over-read in the
| Exiv2::Jp2Image::readMetadata function of jp2image.cpp in Exiv2 0.26. A
| Crafted input will lead to a denial of service attack.

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-14860
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-14860
[1] https://github.com/Exiv2/exiv2/issues/71

Regards,
Salvatore

Bug#888866: exiv2: CVE-2017-14863

[Salvatore Bonaccorso]

Source: exiv2
Version: 0.26-1
Severity: grave
Tags: security upstream
Forwarded: https://github.com/Exiv2/exiv2/issues/132

Hi,

the following vulnerability was published for exiv2, only affecting
the experimental version.

CVE-2017-14863[0]:
| A NULL pointer dereference was discovered in
| Exiv2::Image::printIFDStructure in image.cpp in Exiv2 0.26. The
| vulnerability causes a segmentation fault and application crash, which
| leads to denial of service.

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-14863
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-14863
[1] https://github.com/Exiv2/exiv2/issues/132

Regards,
Salvatore

Bug#888865: exiv2: CVE-2017-14865

[Salvatore Bonaccorso]

Source: exiv2
Version: 0.26-1
Severity: grave
Tags: security upstream
Forwarded: https://github.com/Exiv2/exiv2/issues/134

Hi,

the following vulnerability was published for exiv2, only affecting
the experimental version.

CVE-2017-14865[0]:
| There is a heap-based buffer overflow in the Exiv2::us2Data function of
| types.cpp in Exiv2 0.26. A Crafted input will lead to a denial of
| service attack.

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-14865
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-14865
[1] https://github.com/Exiv2/exiv2/issues/134

Regards,
Salvatore

Bug#888862: exiv2: CVE-2018-5772

[Salvatore Bonaccorso]

Source: exiv2
Version: 0.26-1
Severity: grave
Tags: security upstream

Hi,

the following vulnerability was published for exiv2, and is only
affecting experimental version. Marking grave to indicate should not
go into unstable (the issue itself does not really warrant grave
severity, so if you strongly disagree downgrade, important is just
that no unfixed version goes to unstable :)).

CVE-2018-5772[0]:
| In Exiv2 0.26, there is a segmentation fault caused by uncontrolled
| recursion in the Exiv2::Image::printIFDStructure function in the
| image.cpp file. Remote attackers could leverage this vulnerability to
| cause a denial of service via a crafted tif file.

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-2018-5772
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-5772
[1] https://github.com/Exiv2/exiv2/issues/216

Regards,
Salvatore

Bug#888863: exiv2: CVE-2017-1000127

[Salvatore Bonaccorso]

Source: exiv2
Version: 0.26-1
Severity: grave
Tags: security upstream
Forwarded: https://github.com/Exiv2/exiv2/issues/176

Hi,

the following vulnerability was published for exiv2, only affecting
experimental version.

CVE-2017-1000127[0]:
| Exiv2 0.26 contains a heap buffer overflow in tiff parser

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-1000127
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-1000127
[1] https://github.com/Exiv2/exiv2/issues/176

Regards,
Salvatore

Bug#888864: exiv2: CVE-2017-1000126

[Salvatore Bonaccorso]

Source: exiv2
Version: 0.26-1
Severity: grave
Tags: security upstream
Forwarded: https://github.com/Exiv2/exiv2/issues/175

Hi,

the following vulnerability was published for exiv2, only affecting
experimental version.

CVE-2017-1000126[0]:
| exiv2 0.26 contains a Stack out of bounds read in webp parser

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-1000126
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-1000126
[1] https://github.com/Exiv2/exiv2/issues/175

Regards,
Salvatore

Bug#887866: marked as done (cxref FTBFS on amd64/i386 with glibc 2.26)

[Debian Bug Tracking System]

Your message dated Tue, 30 Jan 2018 18:19:44 +
with message-id 
and subject line Bug#887866: fixed in cxref 1.6e-3
has caused the Debian Bug report #887866,
regarding cxref FTBFS on amd64/i386 with glibc 2.26
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
887866: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887866
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cxref
Version: 1.6e-2
Severity: serious
Tags: buster sid

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

...
../src/cxref -O. -NREADME-TMP -xref README.c
/usr/include/x86_64-linux-gnu/bits/mathcalls-helper-functions.h:21: cxref: 
syntax error, unexpected IDENTIFIER, expecting ')'

The previous 10, current and next 10 symbols are:
-10 | 297 : LONG : long
 -9 | 301 :   DOUBLE : double
 -8 | 258 :   IDENTIFIER : __n
 -7 |  41 :  ')' : )
 -6 |  59 :  ';' : ;
 -5 | 286 :   EXTERN : extern
 -4 | 296 :  INT : int
 -3 | 258 :   IDENTIFIER : __fpclassifyf128
 -2 |  40 :  '(' : (
 -1 | 258 :   IDENTIFIER : _Float128
  0 | 258 :   IDENTIFIER : __value
  1 |  41 :  ')' : )
  2 |  59 :  ';' : ;
  3 | 286 :   EXTERN : extern
  4 | 296 :  INT : int
  5 | 258 :   IDENTIFIER : __signbitf128
  6 |  40 :  '(' : (
  7 | 258 :   IDENTIFIER : _Float128
  8 | 258 :   IDENTIFIER : __value
  9 |  41 :  ')' : )
 10 |  59 :  ';' : ;

../src/cxref -O. -NREADME-TMP -xref README.c -latex -html-src -rtf -sgml
/usr/include/x86_64-linux-gnu/bits/mathcalls-helper-functions.h:21: cxref: 
syntax error, unexpected IDENTIFIER, expecting ')'

The previous 10, current and next 10 symbols are:
-10 | 297 : LONG : long
 -9 | 301 :   DOUBLE : double
 -8 | 258 :   IDENTIFIER : __n
 -7 |  41 :  ')' : )
 -6 |  59 :  ';' : ;
 -5 | 286 :   EXTERN : extern
 -4 | 296 :  INT : int
 -3 | 258 :   IDENTIFIER : __fpclassifyf128
 -2 |  40 :  '(' : (
 -1 | 258 :   IDENTIFIER : _Float128
  0 | 258 :   IDENTIFIER : __value
  1 |  41 :  ')' : )
  2 |  59 :  ';' : ;
  3 | 286 :   EXTERN : extern
  4 | 296 :  INT : int
  5 | 258 :   IDENTIFIER : __signbitf128
  6 |  40 :  '(' : (
  7 | 258 :   IDENTIFIER : _Float128
  8 | 258 :   IDENTIFIER : __value
  9 |  41 :  ')' : )
 10 |  59 :  ';' : ;

mv README.c.tex README_c.tex
mv: cannot stat 'README.c.tex': No such file or directory
Makefile:100: recipe for target 'readme' failed
make[2]: *** [readme] Error 1
--- End Message ---
--- Begin Message ---
Source: cxref
Source-Version: 1.6e-3

We believe that the bug you reported is fixed in the latest version of
cxref, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 887...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Camm Maguire  (supplier of updated cxref package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 30 Jan 2018 16:50:37 +
Source: cxref
Binary: cxref cxref-doc cxref-emacs
Architecture: source amd64 all
Version: 1.6e-3
Distribution: unstable
Urgency: high
Maintainer: Camm Maguire 
Changed-By: Camm Maguire 
Description:
 cxref  - Generates LaTeX and HTML documentation for C programs
 cxref-doc  - Generates LaTeX and HTML documentation for C programs
 cxref-emacs - Generates LaTeX and HTML documentation for C programs
Closes: 748116 843271 866264 887866 888483
Changes:
 cxref (1.6e-3) unstable; urgency=high
 .
   * Bug fix: "cxref FTBFS on amd64/i386 with glibc 2.26", thanks to Adrian
 Bunk (Closes: #887866). Added defined to doc/Makefile.in, no doubt a
 better way.
   * Added homepage entry to control
   * Bug fix: "please add Homepage field", thanks to Juhani Numminen
 (Closes: #888483).
   * Bug fix: "Duplicate and conflicting definition of function
 check_assertion", thanks 

Bug#888860: node-js-beautify: cannot install: wants to overwrite /usr/bin/js-beautify from package jsbeautifier

[Jonas Smedegaard]

Package: node-js-beautify
Version: 1.7.5+dfsg-1
Severity: serious
Justification: Policy 10.1

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

node-js-beautify tries to overwrite the file /usr/bin/js-beautify, which
(when installed) is already provided by the package jsbeautifier.

Please see Debian Policy §10.1 for ways to solve this:
file:///usr/share/doc/debian-policy/policy.html/ch-files.html#binaries

 - Jonas

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAlpwtDEACgkQLHwxRsGg
ASEQzg//Wz255p1CMXS3YGJ0ehkUzmI6Gpcr5lIEcLmf1jy0tF7ejm0rEE9znvj9
tMqGxzU1kscGKypEA90owxt1BgerziyBtl/l1K6vnupRv6L+EnMxleX1ACDdAMhN
b3E78A74lhGx5D+xXzCxwROvf70MdZ5Nfw7EEWIJ3Ejj8J/mHGa6e3cTJw01rnQF
+udaiQ3Oqbun2ji9cAud9SzXyyKHZQV9YwjhpLqps+Xvd+23TWy6WiIzxeiQreFh
VwMpCUnDbvGESkbgidXkF1s10a2dY0vhDJBlYdOSX4XmSVnrYrQ/LHlONtASc7Rv
Kzo+EK/uo1V1177z1zmQZApEGBDk2oVjYLWUYuIsZDulaGsSJ+Yy+737f2mOUVjf
+qKEW5zQBJy6hlkmabnj81zagC5i+GXtugqkYkLBMtEojMnU8BXlqWh/ZzUbCJCG
KVTZOH20ee90v1FhJwe4Ql2UBTvDsuSgcyfrd29Qts2WMgEJgjhNdW/Jf0DzDSeh
2u82IaTRDmmvrmIEu0dOR2wM1phjWeNXJDe9CLVCpOWCco2kqh29ZMamM+0I1TyL
/wCJ3ICElZLCkfMp/0ZcWWPNwEZ/bgFDwP+BnsChs2CtQXqWH7G/1BNdMYPrIJ8L
fEHq8KFEbQ57+NN1J3snFtHl0h6mQ02FWTxyeG+G8JdnPbqC01Q=
=f92K
-END PGP SIGNATURE-

Bug#884222: valabind: Fails to build with vala 0.38

[Rico Tzschichholz]

On Mon, 22 Jan 2018 06:52:24 -0500 Jeremy Bicha  wrote:
> https://salsa.debian.org/jbicha/valabind
> 
> Sebastian, could you take a look?
> 

Afaics this looks good and should be uploaded asap.

This is the only bit which blocks the vala 0.38 introduction in testing.

Regards,
Rico



signature.asc
Description: OpenPGP digital signature

Bug#888837: spamassassin: sa-update failed, spamd does not start anymore

[Noah Meyerhans]

Control: severity -1 normal

Resetting severity to normal, since we don't ship with updates enabled
at all by default.

On Tue, Jan 30, 2018 at 09:07:26AM -0700, Will Aoki wrote:
> forwarded 37 https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7540
> thanks
> 
> We hit this bug this morning with an sa-update. I'd hazard a guess that
> it's the faulty ruleset described in upstream bug #7540 (fixed less than
> two hours ago) and will clear up soon, when upstream publishes new
> rules.

Yeah, it's been fixed upstream according to that bug report.

This does hilight a need to be a little more thorough in our cleanup of
failed updates, though. If, as Niccolo found, the system reboots or
spamd is otherwise restarted before the fix is pulled down, it won't
properly start. If you're using spamassassin directly, rather than
spamd+spamc, then it simply won't work until the upstream fix is
downloaded.

We currently detect the case where the update results in an invalid
ruleset, and in that case we skip the spamd reload. The theory is that
we'll naturally pick up the fix when it's published via the update
channel. However, that's not far enough. We need to actually roll back
to a valid ruleset. Or better yet, we need to stage the ruleset and
validate it before we ever expose it to the runtime environment.

noah



signature.asc
Description: PGP signature

Processed: Re: Bug#888837: spamassassin: sa-update failed, spamd does not start anymore

[Debian Bug Tracking System]

Processing control commands:

> severity -1 normal
Bug #37 [spamassassin] spamassassin: sa-update failed, spamd does not start 
anymore
Severity set to 'normal' from 'grave'

-- 
37: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=37
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#853668: closed by Santiago Garcia Mantinan <ma...@debian.org> (Bug#853668: fixed in squid 4.0.21-1~exp5)

[Helmut Grohne]

Control: clone -1 -2
Control: reopen -2
Control: reassign -2 src:squid3

On Tue, Nov 21, 2017 at 10:03:22AM +, Debian Bug Tracking System wrote:
> #853668: squid3: ftbfs with GCC-7

This bug report is very confusing now. src:squid3 FTBFS. The bug is
fixed in src:squid/experimental though. src:squid does not have the
found version, so udd thinks this bug is fixed in unstable and
src:squid3 does not have any rc bugs despite the fact that it still
FTBFS.

So I think this should be two bugs (for two source packages). The
original bug remains fixed in src:squid and I clone one for src:squid3.
Thus squid3 can be autoremoved from testing. I guess that src:squid3
should be removed at some point (when the experimental src:squid moves
to unstable), and then you can simply reassign the cloned bug to ftp.d.o
as a removal bug. Until then it documents the fact that src:squid3 FTBFS
in unstable. I hope this makes sense.

Helmut

Processed: Re: Bug#853668 closed by Santiago Garcia Mantinan <ma...@debian.org> (Bug#853668: fixed in squid 4.0.21-1~exp5)

[Debian Bug Tracking System]

Processing control commands:

> clone -1 -2
Bug #853668 {Done: Santiago Garcia Mantinan } [src:squid] 
squid3: ftbfs with GCC-7
Bug 853668 cloned as bug 55
> reopen -2
Bug #55 {Done: Santiago Garcia Mantinan } [src:squid] 
squid3: ftbfs with GCC-7
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions squid/4.0.21-1~exp5.
> reassign -2 src:squid3
Bug #55 [src:squid] squid3: ftbfs with GCC-7
Bug reassigned from package 'src:squid' to 'src:squid3'.
No longer marked as found in versions squid/3.5.23-1.
Ignoring request to alter fixed versions of bug #55 to the same values 
previously set

-- 
853668: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853668
55: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=55
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#874009: marked as done (rkt FTBFS: cannot find package "github.com/aws/aws-sdk-go/private/signer/v4")

[Debian Bug Tracking System]

Your message dated Tue, 30 Jan 2018 17:00:15 +
with message-id 
and subject line Bug#874009: fixed in rkt 1.29.0+dfsg-1
has caused the Debian Bug report #874009,
regarding rkt FTBFS: cannot find package 
"github.com/aws/aws-sdk-go/private/signer/v4"
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
874009: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874009
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rkt
Version: 1.21.0+dfsg-1
Severity: serious

Some recent change in unstable makes rkt FTBFS:

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

...
/usr/bin/make -C _build/src/github.com/coreos/rkt manpages 
GOPATH="/build/1st/rkt-1.21.0+dfsg"/_build/src2
make[2]: Entering directory 
'/build/1st/rkt-1.21.0+dfsg/_build/src/github.com/coreos/rkt'
mkdir -p dist/manpages/
ls 
/build/1st/rkt-1.21.0+dfsg/_build/src/github.com/coreos/rkt/build-rkt-1.21.0/gopath/src/github.com/coreos/rkt/rkt/*.go
 | \
grep -vE '_test.go|main.go|_gen.go|_stub.go' | \
GO15VENDOREXPERIMENT=1 GOARCH="amd64" CGO_ENABLED=1 CC="gcc" CXX="g++" 
GOPATH="/build/1st/rkt-1.21.0+dfsg/_build/src2" GOARCH=amd64 CC= xargs "go" run 
/build/1st/rkt-1.21.0+dfsg/_build/src/github.com/coreos/rkt/build-rkt-1.21.0/gopath/src/github.com/coreos/rkt/rkt/manpages_gen.go
../../../../src2/src/github.com/coreos/rkt/rkt/config/auth.go:25:2: cannot find 
package "github.com/aws/aws-sdk-go/private/signer/v4" in any of:

/build/1st/rkt-1.21.0+dfsg/_build/src2/src/github.com/coreos/rkt/vendor/github.com/aws/aws-sdk-go/private/signer/v4
 (vendor tree)
/usr/lib/go-1.8/src/github.com/aws/aws-sdk-go/private/signer/v4 (from 
$GOROOT)

/build/1st/rkt-1.21.0+dfsg/_build/src2/src/github.com/aws/aws-sdk-go/private/signer/v4
 (from $GOPATH)
rkt/rkt.mk:37: recipe for target 'manpages' failed
make[2]: *** [manpages] Error 123
make[2]: Leaving directory 
'/build/1st/rkt-1.21.0+dfsg/_build/src/github.com/coreos/rkt'
debian/rules:45: recipe for target 'override_dh_auto_build' failed
make[1]: *** [override_dh_auto_build] Error 2
--- End Message ---
--- Begin Message ---
Source: rkt
Source-Version: 1.29.0+dfsg-1

We believe that the bug you reported is fixed in the latest version of
rkt, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 874...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Michael Stapelberg  (supplier of updated rkt package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 30 Jan 2018 09:00:08 +0100
Source: rkt
Binary: golang-github-rkt-rkt-dev rkt
Architecture: source all amd64
Version: 1.29.0+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Dmitry Smirnov 
Changed-By: Michael Stapelberg 
Description:
 golang-github-rkt-rkt-dev - rkt API source
 rkt- CLI for running App Containers
Closes: 874009
Changes:
 rkt (1.29.0+dfsg-1) unstable; urgency=medium
 .
   * New upstream release (Closes: #874009)
   * Reflect upstream organization move (coreos → rkt)
   * Add myself as uploader
   * d/copyright: remove all vendoring (no explicit listing needed)
   * bump standards-version to 4.1.1 (no changes necessary)
   * priority extra was replaced by priority optional
Checksums-Sha1:
 b5fd2768c84cdd714098ae2221da8be9e5778ef4 3889 rkt_1.29.0+dfsg-1.dsc
 a6d06d1441f472254f2e5a4eedefcc65de57eaa4 1103912 rkt_1.29.0+dfsg.orig.tar.xz
 5311260e6a123aea88e585e4172405bb96c44353 7496 rkt_1.29.0+dfsg-1.debian.tar.xz
 8670f784c662d1d339ab75916ff4510268d82ee1 131012 
golang-github-rkt-rkt-dev_1.29.0+dfsg-1_all.deb
 c2ae1a9c5e61346f825373138e7898ddc61f5f39 1619232 
rkt-dbgsym_1.29.0+dfsg-1_amd64.deb
 6e3643c770cd4034d36dd8c4fd5508c67610210e 17484 
rkt_1.29.0+dfsg-1_amd64.buildinfo
 7bf8d0b209ed9a9bcbb78d6d33a4d144ca0b4520 39822596 rkt_1.29.0+dfsg-1_amd64.deb
Checksums-Sha256:
 6c8a1075dba8d79dd07435909c9138275d5e07a96c9d3d258aa8b48b7a32e726 3889 
rkt_1.29.0+dfsg-1.dsc
 

Bug#882066: ansible-lint fails with ansible 2.4

[Louis-Philippe Véronneau]

Yeah, I can confirm this bug too. It is documented here:
https://github.com/willthames/ansible-lint/issues/278

If it can help, here's two CI jobs trying to do the same thing, one with
the Debian Sid package (fail) and one with the the latest pip version
(working):

Sid (3.4.13): https://salsa.debian.org/pollo-guest/ansible/-/jobs/5503
Pip (3.4.20): https://salsa.debian.org/pollo-guest/ansible/-/jobs/5507

Thanks for packaging this!

-- 
pollo



signature.asc
Description: OpenPGP digital signature

Processed: Fixing up the title for #253513

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> retitle 253513 sender (From:) - policy specifies use of /etc/mailname on 
> Debian
Bug #253513 [mailutils] sender (From:) - policy specifies use of /etc/mailname 
on
Changed Bug title to 'sender (From:) - policy specifies use of /etc/mailname on 
Debian' from 'sender (From:) - policy specifies use of /etc/mailname on'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
253513: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=253513
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Re: dietlibc-dev: linux-libc-dev 4.14.2-1 linux/fs.h does not compile with dietlibc-dev linux/types.h

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> block 885961 by 883534
Bug #885961 [src:util-vserver] FTBFS: __kernel_rwf_t in 4.14 kernel headers
885961 was not blocked by any bugs.
885961 was not blocking any bugs.
Added blocking bug(s) of 885961: 883534
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
885961: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885961
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#888837: spamassassin: sa-update failed, spamd does not start anymore

[Will Aoki]

forwarded 37 https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7540
thanks

We hit this bug this morning with an sa-update. I'd hazard a guess that
it's the faulty ruleset described in upstream bug #7540 (fixed less than
two hours ago) and will clear up soon, when upstream publishes new
rules.

Processed: Re: spamassassin: sa-update failed, spamd does not start anymore

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> forwarded 37 https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7540
Bug #37 [spamassassin] spamassassin: sa-update failed, spamd does not start 
anymore
Set Bug forwarded-to-address to 
'https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7540'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
37: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=37
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Mark as forwarded

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> forwarded 886018 https://projects.universe-factory.net/issues/251
Bug #886018 [fastd] fastd: FTBFS with libsodium-dev >= 1.0.15
Set Bug forwarded-to-address to 
'https://projects.universe-factory.net/issues/251'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
886018: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886018
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

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

[Roger Shimizu]

On Wed, Jan 31, 2018 at 12:55 AM, Antoine Beaupré  wrote:
> On 2018-01-30 23:53:47, Roger Shimizu wrote:
>> On Tue, Jan 30, 2018 at 4:13 PM, intrigeri  wrote:
>>> Antoine Beaupre:
 This bug makes torbrowser-launcher completely unusable on Debian
 stretch, as soon as the browser is updated (as it should).
>>>
 What's expected from stable users here? Is there going to be a stable
 update for this?
>>>
>>> torbrowser-launcher is not included in Debian Stretch.
>>
>> Yes, it's not included in stretch.
>> However, it can be included into stretch-backports and
>> jessie-backports-sloppy repo.
>> I'll make the bpo release when 0.2.9-1 hit testing.
>
> Ah. Duh. Sorry for messing that one up. :)
>
> Let me know if you need help with the backports - i'll try to fix things
> instead of complaining here... ;)

Almost all backports version were uploaded by me [0].

[0] https://tracker.debian.org/pkg/torbrowser-launcher

And since it already passed the backports new queue, no help is need
here so far.

However if you really want to help backports, here's one :P
 - https://bugs.debian.org/882126

Cheers,
--
Roger Shimizu, GMT +9 Tokyo
PGP/GPG: 4096R/6C6ACD6417B3ACB1

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

[Antoine Beaupré]

On 2018-01-30 23:53:47, Roger Shimizu wrote:
> On Tue, Jan 30, 2018 at 4:13 PM, intrigeri  wrote:
>> Antoine Beaupre:
>>> This bug makes torbrowser-launcher completely unusable on Debian
>>> stretch, as soon as the browser is updated (as it should).
>>
>>> What's expected from stable users here? Is there going to be a stable
>>> update for this?
>>
>> torbrowser-launcher is not included in Debian Stretch.
>
> Yes, it's not included in stretch.
> However, it can be included into stretch-backports and
> jessie-backports-sloppy repo.
> I'll make the bpo release when 0.2.9-1 hit testing.

Ah. Duh. Sorry for messing that one up. :)

Let me know if you need help with the backports - i'll try to fix things
instead of complaining here... ;)

a.

-- 
If you have come here to help me, you are wasting our time.
But if you have come because your liberation is bound up with mine, then
let us work together.- Aboriginal activists group, Queensland, 1970s

Processed: Re: Not in python-tackerclient

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> forwarded 888080 https://github.com/python-cmd2/cmd2/issues/230
Bug #888080 [python-cmd2] python-tackerclient FTBFS: AttributeError: 'module' 
object has no attribute 'exceptions'
Set Bug forwarded-to-address to 
'https://github.com/python-cmd2/cmd2/issues/230'.
> tags 888080 fixed-upstream
Bug #888080 [python-cmd2] python-tackerclient FTBFS: AttributeError: 'module' 
object has no attribute 'exceptions'
Added tag(s) fixed-upstream.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
888080: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888080
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: node-webpack-sources FTBFS with node-source-map 0.7.0+dfsg-1

[Debian Bug Tracking System]

Processing control commands:

> forwarded -1 https://github.com/webpack/webpack-sources/issues/34
Bug #46 [node-webpack-sources] node-webpack-sources FTBFS with 
node-source-map 0.7.0+dfsg-1
Set Bug forwarded-to-address to 
'https://github.com/webpack/webpack-sources/issues/34'.
> tag -1 help
Bug #46 [node-webpack-sources] node-webpack-sources FTBFS with 
node-source-map 0.7.0+dfsg-1
Added tag(s) help.

-- 
46: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=46
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#888846: node-webpack-sources FTBFS with node-source-map 0.7.0+dfsg-1

[Pirate Praveen]

Package: node-webpack-sources
Version: 1.0.1-1
Severity: serious
Control: forwarded -1 https://github.com/webpack/webpack-sources/issues/34
Control: tag -1 help

With the last upload of node-source-map, node-webpack-sources has 2
tests failing and hence FTBFS.

0.7 has many breaking changes including dropping support for node < 8,
so upstream is not willing to move to this version.



signature.asc
Description: OpenPGP digital signature

Bug#888252: marked as done (py-radix: Incomplete debian/copyright?)

[Debian Bug Tracking System]

Your message dated Tue, 30 Jan 2018 15:11:28 +
with message-id 
and subject line Bug#888252: fixed in py-radix 0.10.0-2
has caused the Debian Bug report #888252,
regarding py-radix: Incomplete debian/copyright?
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
888252: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888252
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: py-radix
Version: 0.10.0-1
Severity: serious
Justication: Policy 12.5
X-Debbugs-CC: Aggelos Avgerinos 

Hi,

I just ACCEPTed py-radix from NEW but noticed it was missing 
attribution in debian/copyright for at least Michael J. Schultz

(This is not exhaustive so please check over the entire package 
carefully and address these on your next upload.)


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
--- End Message ---
--- Begin Message ---
Source: py-radix
Source-Version: 0.10.0-2

We believe that the bug you reported is fixed in the latest version of
py-radix, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 888...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Aggelos Avgerinos  (supplier of updated py-radix 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 29 Jan 2018 22:55:15 +0200
Source: py-radix
Binary: python-radix python3-radix
Architecture: source amd64
Version: 0.10.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Aggelos Avgerinos 
Description:
 python-radix - radix tree implementation for storage of IPv4 and IPv6 networks 
(
 python3-radix - radix tree implementation for storage of IPv4 and IPv6 
networks (
Closes: 888252
Changes:
 py-radix (0.10.0-2) unstable; urgency=medium
 .
   * d/control: Change homepage since upstream has been moved
   * d/copyright: Fix copyright and licenses (Closes: #888252)
Checksums-Sha1:
 16c8d8e98b90cc6e66563a1ac72c001e5b5d6100 2235 py-radix_0.10.0-2.dsc
 28f9dbb80255c7dab5f354584a68e70a58e63ef2 3568 py-radix_0.10.0-2.debian.tar.xz
 1ac5237dcc87a87b69ab53eb196476d3b3da47b6 7939 py-radix_0.10.0-2_amd64.buildinfo
 92a7299a88ee50a547c8cc7c0baf20ca36ba4f15 32476 
python-radix-dbgsym_0.10.0-2_amd64.deb
 f3df06a98e437038db3a3afdd0dddcca1fcadbfe 21856 python-radix_0.10.0-2_amd64.deb
 a6a720b95e95880f30551206e99eda495753271e 34592 
python3-radix-dbgsym_0.10.0-2_amd64.deb
 dd651e4038c7254b4dc05a74681132f6b04dc72f 19816 python3-radix_0.10.0-2_amd64.deb
Checksums-Sha256:
 d4642b8c89f84d3ffeb2a25b2a670b6b9ecca020d4bf94c8c7557e1621b9001f 2235 
py-radix_0.10.0-2.dsc
 d881aaa989cb826386a7c0f5e9057bb5d0d074ad153b70695fc91d6253391219 3568 
py-radix_0.10.0-2.debian.tar.xz
 8499c31407bc126ee45ba96d1692dec1b5ad47915f7816d9cc66eb25a3d262d3 7939 
py-radix_0.10.0-2_amd64.buildinfo
 e23f34e5ebe03426cbba83981d8f21d696303eb50b3720de5181ab1db0e4e91b 32476 
python-radix-dbgsym_0.10.0-2_amd64.deb
 f22122638ed7660156b0daf43ccc2153d9b9a9b7e373fe1298520dc95fa00d39 21856 
python-radix_0.10.0-2_amd64.deb
 cfd3df071cdf90d142421351337a28fbf093f22d8bef128a80db0c87d490ef27 34592 
python3-radix-dbgsym_0.10.0-2_amd64.deb
 d0658bde3971129aebad6fdfb1ca7dcba24aeef3180770f2727ddcba69d5917e 19816 
python3-radix_0.10.0-2_amd64.deb
Files:
 be60b97abf07f33507deb919f5dd6873 2235 python optional py-radix_0.10.0-2.dsc
 55a55bb1f42091e19844401154913d85 3568 python optional 
py-radix_0.10.0-2.debian.tar.xz
 3ab5abe7a5c9475192b890e532e65c4e 7939 python optional 
py-radix_0.10.0-2_amd64.buildinfo
 9cf6ac7598043bac2f8499490ea8365b 32476 debug optional 
python-radix-dbgsym_0.10.0-2_amd64.deb
 ef993cf5f6e8814506eeb8f7aa138561 21856 python optional 
python-radix_0.10.0-2_amd64.deb
 aefe016135d83e32adcc9359d683e2f2 34592 debug optional 
python3-radix-dbgsym_0.10.0-2_amd64.deb
 724cc7188399b80e2834192be92c1318 19816 python optional 
python3-radix_0.10.0-2_amd64.deb

-BEGIN PGP SIGNATURE-

Bug#887323: dewalls i386 test failure

[Wookey]

On 2018-01-30 06:48 +, Philip Schuchardt wrote:
> I know I’ve been dragging my feet on this. Let’s see if I can figure this out,
> this week.

I fished out an old netbook which is actually i386. And installed an
unstable chroot on it (very slowly!) last night. Hopefully this will
enable some bottom-getting-to.

I should probbaly just have used a debian porter-box, but that machine
needed updating anyway.

Wookey
-- 
Principal hats:  Linaro, Debian, Wookware, ARM
http://wookware.org/


signature.asc
Description: PGP signature

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

[Roger Shimizu]

On Tue, Jan 30, 2018 at 4:13 PM, intrigeri  wrote:
> Antoine Beaupre:
>> This bug makes torbrowser-launcher completely unusable on Debian
>> stretch, as soon as the browser is updated (as it should).
>
>> What's expected from stable users here? Is there going to be a stable
>> update for this?
>
> torbrowser-launcher is not included in Debian Stretch.

Yes, it's not included in stretch.
However, it can be included into stretch-backports and
jessie-backports-sloppy repo.
I'll make the bpo release when 0.2.9-1 hit testing.

Cheers,
-- 
Roger Shimizu, GMT +9 Tokyo
PGP/GPG: 4096R/6C6ACD6417B3ACB1

Bug#888811: dnscrypt-proxy: upstream gone, new package

[Juhani Numminen]

Control: severity -1 minor

On Mon, 29 Jan 2018 22:51:23 -0800 Brian Clinkenbeard 
 wrote:
> Source: dnscrypt-proxy
> Severity: serious
> Tags: upstream
> Justification: fails to build from source (but built successfully in the past)

It succeeds to build from source for me, on amd64 and i386.
Therefore I'm lowering the severity. Since no actual problem was reported,
I believe "minor" is appropriate:
https://www.debian.org/Bugs/Developer#severities

Regards,
Juhani

Processed: Re: dnscrypt-proxy: upstream gone, new package

[Debian Bug Tracking System]

Processing control commands:

> severity -1 minor
Bug #11 [src:dnscrypt-proxy] dnscrypt-proxy: upstream gone, new package
Severity set to 'minor' from 'serious'

-- 
11: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=11
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#888837: spamassassin: sa-update failed, spamd does not start anymore

[Niccolo Rigacci]

Package: spamassassin
Version: 3.4.1-6+deb9u1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

I enabled CRON=1 in /etc/default/spamassassin, to enable the cron job to
automatically update spamassassin's rules.

Then I run /etc/cron.daily/spamassassin, which failed with this error
message:

rules: failed to run FORGED_GMAIL_RCVD test, skipping:
(Can't locate object method "check_for_forged_gmail_received_headers" 
via package "Mail::SpamAssassin::PerMsgStatus" at (eval 1325) line 71.
)
channel: lint check of update failed, channel failed
sa-update failed for unknown reasons

After this, the spamassassin service is unable to restart, trying
systemctl restart spamassassin.service I get the following errors in
syslog:

spamd[2365]: logger: removing stderr method
spamd[2367]: config: no rules were found! Do you need to run 'sa-update'?
spamd[2365]: child process [2367] exited or timed out without signaling 
production of a PID file: e
systemd[1]: spamassassin.service: Control process exited, code=exited status=255
systemd[1]: Failed to start Perl-based spam filter using text analysis.

To be able to restart spamd, I had to remove the directory:

rm -r /var/lib/spamassassin/3.004001/


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

Kernel: Linux 4.9.0-5-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 spamassassin depends on:
ii  adduser  3.115
ii  curl 7.52.1-5+deb9u4
ii  init-system-helpers  1.48
ii  libhtml-parser-perl  3.72-3
ii  libhttp-date-perl6.02-1
ii  libmail-dkim-perl0.40-1
ii  libnet-dns-perl  1.07-1
ii  libnetaddr-ip-perl   4.079+dfsg-1+b1
ii  libsocket6-perl  0.27-1+b1
ii  libsys-hostname-long-perl1.5-1
ii  lsb-base 9.20161125
ii  perl 5.24.1-3+deb9u2
ii  perl-modules-5.24 [libarchive-tar-perl]  5.24.1-3+deb9u2

Versions of packages spamassassin recommends:
ii  gnupg 2.1.18-8~deb9u1
ii  libio-socket-inet6-perl   2.72-2
ii  libmail-spf-perl  2.9.0-4
ii  libperl5.24 [libsys-syslog-perl]  5.24.1-3+deb9u2
ii  sa-compile3.4.1-6+deb9u1
ii  spamc 3.4.1-6+deb9u1

Versions of packages spamassassin suggests:
pn  libdbi-perl  
pn  libencode-detect-perl
pn  libgeo-ip-perl   
ii  libio-socket-ssl-perl2.044-1
pn  libnet-patricia-perl 
ii  libperl5.24 [libcompress-zlib-perl]  5.24.1-3+deb9u2
pn  pyzor
pn  razor

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

-- no debconf information

Bug#888252: marked as pending

[Aggelos Avgerinos]

tag 888252 pending
thanks

Hello,

Bug #888252 reported by you has been fixed in the Git repository. You can
see the changelog below, and you can check the diff of the fix at:


https://anonscm.debian.org/cgit/python-modules/packages/py-radix.git/commit/?id=f235185

---
commit f23518514d3524786722f3161c1d978429542431
Author: Aggelos Avgerinos 
Date:   Mon Jan 29 22:55:48 2018 +0200

Release version 0.10.0-2

diff --git a/debian/changelog b/debian/changelog
index 17339bd..4dfa637 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+py-radix (0.10.0-2) unstable; urgency=medium
+
+  * d/control: Change homepage since upstream has been moved
+  * d/copyright: Fix copyright and licenses (Closes: #888252)
+
+ -- Aggelos Avgerinos   Mon, 29 Jan 2018 
22:55:15 +0200
+
 py-radix (0.10.0-1) unstable; urgency=medium
 
   [ Christoph Berg ]

Bug#887761: marked as done (user-mode-linux FTBFS with glibc 2.26)

[Debian Bug Tracking System]

Your message dated Tue, 30 Jan 2018 13:55:49 +
with message-id 
and subject line Bug#887761: fixed in user-mode-linux 4.14-1um-2
has caused the Debian Bug report #887761,
regarding user-mode-linux FTBFS with glibc 2.26
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
887761: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887761
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: user-mode-linux
Version: 4.14-1um-1
Severity: serious

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/user-mode-linux.html

...
  CC  arch/um/os-Linux/signal.o
arch/um/os-Linux/signal.c: In function 'hard_handler':
arch/um/os-Linux/signal.c:163:22: error: dereferencing pointer to incomplete 
type 'struct ucontext'
  mcontext_t *mc = >uc_mcontext;
  ^~
scripts/Makefile.build:319: recipe for target 'arch/um/os-Linux/signal.o' failed
make[2]: *** [arch/um/os-Linux/signal.o] Error 1
--- End Message ---
--- Begin Message ---
Source: user-mode-linux
Source-Version: 4.14-1um-2

We believe that the bug you reported is fixed in the latest version of
user-mode-linux, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 887...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Ritesh Raj Sarraf  (supplier of updated user-mode-linux 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 30 Jan 2018 17:39:04 +0530
Source: user-mode-linux
Binary: user-mode-linux
Architecture: source amd64
Version: 4.14-1um-2
Distribution: unstable
Urgency: medium
Maintainer: User Mode Linux Maintainers 
Changed-By: Ritesh Raj Sarraf 
Description:
 user-mode-linux - User-mode Linux (kernel)
Closes: 887761
Changes:
 user-mode-linux (4.14-1um-2) unstable; urgency=medium
 .
   * [5b667b5] Use POSIX ucontext_t instead of struct ucontext
 (Closes: #887761)
Checksums-Sha1:
 67505f6bc766451e50c02e3dba9725ba4816968c 1904 user-mode-linux_4.14-1um-2.dsc
 6c7789432e3d57779761855fb952bdc1ed1335b2 293332 
user-mode-linux_4.14-1um-2.tar.gz
 868dd6b4de15ba61b82d230c800933a17d070afa 378428 
user-mode-linux-dbgsym_4.14-1um-2_amd64.deb
 6d79d548ff026d0cc7272fb4565e9685a43ed095 6224 
user-mode-linux_4.14-1um-2_amd64.buildinfo
 e55aa79d6f1de1eb86bc262a7a87d30b57c7c4be 9710728 
user-mode-linux_4.14-1um-2_amd64.deb
Checksums-Sha256:
 b3d5c876165cb0fe98e3861a0506c48cbac4cf4dce238b28a2dbe612667bfac9 1904 
user-mode-linux_4.14-1um-2.dsc
 91ca088a674c409d4453dfb0a326838fac6c65b5b8fcde007d8a05fd34916b9f 293332 
user-mode-linux_4.14-1um-2.tar.gz
 0ca0e913e65333d5972e61591e29ef02340b63fc72d79aa3eeab7603dd371966 378428 
user-mode-linux-dbgsym_4.14-1um-2_amd64.deb
 a734248cbc3e683027008f2b0c979ec533e5ed335fb0155846ab1eb29d82d80b 6224 
user-mode-linux_4.14-1um-2_amd64.buildinfo
 e7314f11940734e1a0db6bb9b693dcebe539c21d2e2af8da0b8ae751d9bca4f2 9710728 
user-mode-linux_4.14-1um-2_amd64.deb
Files:
 074f1daf8ea64c82241202d674baa6b1 1904 kernel extra 
user-mode-linux_4.14-1um-2.dsc
 b96c265fbfa28531bca45fde4ff6fa56 293332 kernel extra 
user-mode-linux_4.14-1um-2.tar.gz
 6e3316cdf932028279ba71ae8b96840b 378428 debug optional 
user-mode-linux-dbgsym_4.14-1um-2_amd64.deb
 1361e83b839f00b30668676fcd1fccf6 6224 kernel extra 
user-mode-linux_4.14-1um-2_amd64.buildinfo
 29f5ebb37f1273b7211d86195fad0664 9710728 kernel extra 
user-mode-linux_4.14-1um-2_amd64.deb

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEQCVDstmIVAB/Yn02pjpYo/LhdWkFAlpwcyQACgkQpjpYo/Lh
dWkOGhAAivyXfwCaykCk16fqoZjeCXt+xCq/MU0/vkYxS28DMNRUL1pHHSee7ZbH
5ecPDKFvlZpWEBTAQMomXwOigAIRvLMMMbHtD21Aos3Tatpen9YZOToKjofA2Hw5
ZXixrkK0CcXFpLAsSWpqi9sXOj79h8wq0/P2pA1Gpc2abYjEtAYalpMqMFpUxPil
7juE38a29qyuASdMN9nsoOEP2F9T6IJuqvyr/W9qGJXTb7x8LcZ7Qm85GIDAiqkS
kBm9XvL/XDOhKBkmV+wFvWjlYKzaA3nTKP0+I/udHT+MSLlILSXfOK8/n2qJyWgb
lSUQVr2nYeAdCcvNz3p5G8RB5IAz0MtFZo9Hoz4Q3YAer5Z4k1DuvxTsM9bHciHD
6n6kykhRHUlQueaddXBhlxmcJuiJIno37CwrKtzO/pGSRcYM1jtv178Cpk0PckFY
NHC6kU0xJKuDQNg4dxP6TRI7Gg8S48HBlPduI2ck3m8gqGa8xMdUmwYU9SrIv02/
/jcn5Y3ZMDVCIk8m0cm1vCeRA053UUv+VOnp+6IYJDtBECTM+zUqav6Mce5NS+ev

Processed: Bug#888252 marked as pending

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tag 888252 pending
Bug #888252 [src:py-radix] py-radix: Incomplete debian/copyright?
Ignoring request to alter tags of bug #888252 to the same tags previously set
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
888252: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888252
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#885136: 4digits: Depends on unmaintained pygtk

[Jeremy Bicha]

On Tue, Jan 30, 2018 at 4:51 AM, Pan Yongzhi  wrote:
> I have updated the code to use gobject
> (https://github.com/fossilet/4digits/commit/ffc2e3fe55ca73335e12b0ded42a52d21e555e9e),
> though not yet released a version. How should I update it? Am I supposed to
> release a new version and file a RFP for it?

Yes, that sounds like a good plan.

You're aware of https://mentors.debian.net/ right?

Thank you for working on this!

Jeremy Bicha

Bug#888831: [firefox-esr] NS_ERROR_NET_INADEQUATE_SECURITY for https sites - libnss3 dependency

[Philipp Klaus Krause]

Package: firefox-esr
Version: 52.6.0esr-2
Severity: grave

--- Please enter the report below this line. ---

After upgrading firefox-esr today, it now refuses to access any https
sites (e.g. google, bing are affected, including the results from the
search bar in firefox itself). I get an error message

NS_ERROR_NET_INADEQUATE_SECURITY

This is with libnss3 2:3.33-1.

firefox-esr seems to work normally with libnss3 2:3.34.1-1. So I guess
the bug is in the dependency on the libnss3 version.

--- System information. ---
Architecture: Kernel:   Linux 4.14.0-2-amd64

Debian Release: buster/sid
  500 unstableftp.de.debian.org   500 testing
ftp.de.debian.org 1 experimentalftp.de.debian.org
--- Package information. ---
Depends  (Version) | Installed
==-+-==
libasound2 (>= 1.0.16) | libatk1.0-0
   (>= 1.12.4) | libc6(>= 2.17)
| libcairo-gobject2  (>= 1.10.0) | libcairo2
 (>= 1.10.0) | libdbus-1-3(>=
1.9.14) | libdbus-glib-1-2 (>= 0.78) |
libevent-2.1-6   (>= 2.1.8-stable) | libffi6
(>= 3.0.4) | libfontconfig1   (>= 2.12)
| libfreetype6(>= 2.2.1) | libgcc1
  (>= 1:4.0) | libgdk-pixbuf2.0-0 (>=
2.22.0) | libglib2.0-0   (>= 2.31.8) | libgtk-3-0
  (>= 3.0.0) | libgtk2.0-0
(>= 2.10) | libhunspell-1.6-0  | libjsoncpp1
(>= 1.7.4) | libnspr4
(>= 2:4.10.9) | libnss3(>= 2:3.28) |
libpango-1.0-0 (>= 1.14.0) | libsqlite3-0
   (>= 3.14.0) | libstartup-notification0  (>= 0.8)
| libstdc++6(>= 5.2) | libvpx4
  (>= 1.6.0) | libx11-6
 | libx11-xcb1| libxcb-shm0
  | libxcb1
  | libxcomposite1(>= 1:0.3-1) | libxdamage1
(>= 1:1.1) | libxext6
   | libxfixes3 | libxrender1
| libxt6
| zlib1g  (>= 1:1.2.3.4) | fontconfig
 | procps
 | debianutils  (>= 1.16) |

Package's Recommends field is empty.

Suggests  (Version) | Installed
===-+-===
fonts-stix  | 1.1.1-4
 OR otf-stix| fonts-lmodern   |
2.004.5-3
mozplugger  | libgssapi-krb5-2|  OR
libkrb53| libcanberra0|


--- Output from package bug script ---

-- Extensions information
Name: Adblock Plus
Location: /{d10d0bf8-f5b5-c8b4-a8b2-2b9879e08c5d}.xpi
Status: enabled

Name: Application Update Service Helper
Location: /aushel...@mozilla.org.xpi
Status: enabled

Name: Deutsch (DE) Language Pack locale
Location:
/usr/lib/firefox-esr/browser/extensions/langpack...@firefox-esr.mozilla.org.xpi
Package: firefox-esr-l10n-de
Status: enabled

Name: English (GB) Language Pack locale
Location:
/usr/lib/firefox-esr/browser/extensions/langpack-en...@firefox-esr.mozilla.org.xpi
Package: firefox-esr-l10n-en-gb
Status: enabled

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

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

Name: Pocket
Location: /fire...@getpocket.com.xpi
Status: enabled

Name: Standard theme
Location:
/usr/lib/firefox-esr/browser/extensions/{972ce4c6-7e08-4474-a285-3208198ce6fd}.xpi
Package: firefox-esr
Status: enabled

Name: Web Compat
Location: /webcom...@mozilla.org.xpi
Status: enabled

-- Plugins information
Name: IcedTea-Web Plugin (using IcedTea-Web 1.6.2 (1.6.2-3.1))
Location: /usr/lib/jvm/java-8-openjdk-amd64/jre/lib/amd64/IcedTeaPlugin.so
Package: icedtea-8-plugin:amd64
Status: enabled


-- Addons package information
ii  firefox-esr52.6.0esr-2  amd64Mozilla Firefox web browser
- Ext
ii  firefox-esr-l1 52.6.0esr-2  all  German language package for
Firef
ii  firefox-esr-l1 52.6.0esr-2  all  English (United Kingdom)
language
ii  firefox-esr-l1 52.6.0esr-2  all  French language package for
Firef
ii  icedtea-8-plug 1.6.2-3.1amd64web browser plugin based on
OpenJ

Processed: severity of 888162 is serious, tagging 888742

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 888162 serious
Bug #888162 [cryptsetup] cryptsetup: `loopaesOpen --key-file=-` doesn't read 
the key from stdin but tries to open key file "./-"
Severity set to 'serious' from 'important'
> tags 888742 + pending
Bug #888742 [cryptsetup] cryptsetup: Please use dh_autoreconf for build
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
888162: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888162
888742: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888742
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#887623: marked as done (fastnetmon FTBFS with libndpi-dev 2.2-1)

[Debian Bug Tracking System]

Your message dated Tue, 30 Jan 2018 11:50:01 +
with message-id 
and subject line Bug#887623: fixed in fastnetmon 1.1.3+dfsg-5
has caused the Debian Bug report #887623,
regarding fastnetmon FTBFS with libndpi-dev 2.2-1
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
887623: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887623
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: fastnetmon
Version: 1.1.3+dfsg-4
Severity: serious

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

...
/usr/bin/c++  -DENABLE_DPI -DENABLE_LUA_HOOKS -DFASTNETMON_ENABLE_AFPACKET 
-DMONGO -DNETMAP_PLUGIN -DREDIS -I/usr/include/libndpi-2.2.0 
-I/usr/include/luajit-2.1 
-I/build/1st/fastnetmon-1.1.3+dfsg/src/netmap_plugin/netmap_includes 
-I/usr/include/libmongoc-1.0 -I/usr/include/libbson-1.0  -g -O2 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2   -o CMakeFiles/fastnetmon.dir/fastnetmon.cpp.o -c 
/build/1st/fastnetmon-1.1.3+dfsg/src/fastnetmon.cpp
/build/1st/fastnetmon-1.1.3+dfsg/src/fastnetmon.cpp: In function 'void 
produce_dpi_dump_for_pcap_dump(std::__cxx11::string, std::stringstream&, 
std::__cxx11::string)':
/build/1st/fastnetmon-1.1.3+dfsg/src/fastnetmon.cpp:3635:85: error: 
'ndpi_protocol {aka struct ndpi_proto}' has no member named 'protocol'; did you 
mean 'app_protocol'?
 char* protocol_name = ndpi_get_proto_name(my_ndpi_struct, 
detected_protocol.protocol);

 ^~~~

 app_protocol
/build/1st/fastnetmon-1.1.3+dfsg/src/fastnetmon.cpp:3638:31: error: 
'ndpi_protocol {aka struct ndpi_proto}' has no member named 'protocol'; did you 
mean 'app_protocol'?
 if (detected_protocol.protocol == NDPI_PROTOCOL_DNS) {
   ^~~~
   app_protocol
/build/1st/fastnetmon-1.1.3+dfsg/src/fastnetmon.cpp:3644:38: error: 
'ndpi_protocol {aka struct ndpi_proto}' has no member named 'protocol'; did you 
mean 'app_protocol'?
 } else if (detected_protocol.protocol == NDPI_PROTOCOL_NTP) {
  ^~~~
  app_protocol
/build/1st/fastnetmon-1.1.3+dfsg/src/fastnetmon.cpp:3649:38: error: 
'ndpi_protocol {aka struct ndpi_proto}' has no member named 'protocol'; did you 
mean 'app_protocol'?
 } else if (detected_protocol.protocol == NDPI_PROTOCOL_SSDP) {
  ^~~~
  app_protocol
/build/1st/fastnetmon-1.1.3+dfsg/src/fastnetmon.cpp:3652:38: error: 
'ndpi_protocol {aka struct ndpi_proto}' has no member named 'protocol'; did you 
mean 'app_protocol'?
 } else if (detected_protocol.protocol == NDPI_PROTOCOL_SNMP) {
  ^~~~
  app_protocol
CMakeFiles/fastnetmon.dir/build.make:65: recipe for target 
'CMakeFiles/fastnetmon.dir/fastnetmon.cpp.o' failed
make[3]: *** [CMakeFiles/fastnetmon.dir/fastnetmon.cpp.o] Error 1
--- End Message ---
--- Begin Message ---
Source: fastnetmon
Source-Version: 1.1.3+dfsg-5

We believe that the bug you reported is fixed in the latest version of
fastnetmon, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 887...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Benjamin Drung  (supplier of updated 
fastnetmon package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 30 Jan 2018 12:29:33 +0100
Source: fastnetmon
Binary: fastnetmon
Architecture: source
Version: 1.1.3+dfsg-5
Distribution: unstable
Urgency: medium
Maintainer: Benjamin Drung 
Changed-By: Benjamin Drung 
Description:
 fastnetmon - fast DDoS analyzer with sflow/netflow/mirror support (community e
Closes: 869805 887623
Changes:
 fastnetmon (1.1.3+dfsg-5) unstable; 

Bug#888816: marked as done (libdbus-glib-1-doc: fails to upgrade from 'stable' to 'sid' - trying to overwrite /usr/share/doc/libdbus-glib-1-dev/AUTHORS)

[Debian Bug Tracking System]

Your message dated Tue, 30 Jan 2018 11:19:41 +
with message-id 
and subject line Bug#16: fixed in dbus-glib 0.110-2
has caused the Debian Bug report #16,
regarding libdbus-glib-1-doc: fails to upgrade from 'stable' to 'sid' - trying 
to overwrite /usr/share/doc/libdbus-glib-1-dev/AUTHORS
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
16: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=16
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libdbus-glib-1-doc
Version: 0.110-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'stable'.
It installed fine in 'stable', then the upgrade to 'sid' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/#overwriting-files-and-replacing-packages-replaces

This test intentionally skipped 'testing' to find file overwrite
problems before packages migrate from 'unstable' to 'testing'.

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

  Selecting previously unselected package libdbus-glib-1-doc.
  Preparing to unpack .../134-libdbus-glib-1-doc_0.110-1_all.deb ...
  Unpacking libdbus-glib-1-doc (0.110-1) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-rMgxvR/134-libdbus-glib-1-doc_0.110-1_all.deb (--unpack):
   trying to overwrite '/usr/share/doc/libdbus-glib-1-dev/AUTHORS', which is 
also in package libdbus-glib-1-dev 0.108-2
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /tmp/apt-dpkg-install-rMgxvR/134-libdbus-glib-1-doc_0.110-1_all.deb

This is probably caused by a behavioral change in dh_installdocs
in debhelper compat level 11.


cheers,

Andreas


libdbus-glib-1-dev=0.108-2_libdbus-glib-1-doc=0.110-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: dbus-glib
Source-Version: 0.110-2

We believe that the bug you reported is fixed in the latest version of
dbus-glib, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 888...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Simon McVittie  (supplier of updated dbus-glib package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 30 Jan 2018 10:37:38 +
Source: dbus-glib
Binary: libdbus-glib-1-2 libdbus-glib-1-dev libdbus-glib-1-doc
Architecture: source
Version: 0.110-2
Distribution: unstable
Urgency: medium
Maintainer: Utopia Maintenance Team 

Changed-By: Simon McVittie 
Description:
 libdbus-glib-1-2 - deprecated library for D-Bus IPC
 libdbus-glib-1-dev - deprecated library for D-Bus IPC (development files)
 libdbus-glib-1-doc - deprecated library for D-Bus IPC (API documentation)
Closes: 16
Changes:
 dbus-glib (0.110-2) unstable; urgency=medium
 .
   * d/rules: Transcode to UTF-8
   * libdbus-glib-1-doc Breaks/Replaces libdbus-glib-1-dev (<< 0.110)
 due to the documentation rearrangement in debhelper compat level 11
 (Policy §12.3) (Closes: #16)
Checksums-Sha1:
 c8cced6ab9b8abca3fabdf9ed61f96608682dfd8 2601 dbus-glib_0.110-2.dsc
 15dd9efa4cebde2e142313d4771b76305b46c14e 31200 dbus-glib_0.110-2.debian.tar.xz
 c45520f74d3ba8bb1b9f2140e9b5f93524718b35 6840 
dbus-glib_0.110-2_source.buildinfo
Checksums-Sha256:
 c9174cc67a04dd43ab5cc0811940836a4f1cf884c1c61b42da8acad1b42452bf 2601 
dbus-glib_0.110-2.dsc
 d5bbfd3eb875f8625b8a096f2e6ad2d95065e14dc2c4893b21fefa66f1c21aec 31200 
dbus-glib_0.110-2.debian.tar.xz
 6fafb64227b4dd9bb8a77ba09366d88282af63ed769181c8cce30c27f9ba2489 6840 
dbus-glib_0.110-2_source.buildinfo
Files:
 dfedbd7fa00809ca08a08d63baa6b090 2601 devel optional dbus-glib_0.110-2.dsc
 9bf2e5b1f98f9ff04e498cb51c72a5af 31200 devel optional 
dbus-glib_0.110-2.debian.tar.xz
 92e34415d6b19a0a2014fce3d72b2020 6840 devel optional 
dbus-glib_0.110-2_source.buildinfo

-BEGIN PGP SIGNATURE-

Bug#885136: 4digits: Depends on unmaintained pygtk

[Pan Yongzhi]

Hi Jeremy,

I have updated the code to use gobject 
(https://github.com/fossilet/4digits/commit/ffc2e3fe55ca73335e12b0ded42a52d21e555e9e
 
),
  though not yet released a version. How should I update it? Am I supposed to 
release a new version and file a RFP for it?

Best regards,
P

> 在 2017年12月24日，22:19，Jeremy Bicha  写道：
> 
> Package: 4digits
> Version: 1.1.4-1
> Severity: serious
> User: pkg-gnome-maintain...@lists.alioth.debian.org
> Usertags: oldlibs pygtk
> Tags: sid buster
> 
> pygtk is unmaintained upstream. It has not had a release since GNOME 3
> was released in 2011.
> 
> The way forward is to port your app to use GObject Introspection
> bindings.
> 
> For more information on GObject Introspection see [1] and [2].
> 
> Please try to do this before the Buster release as we're going to
> try to remove pygtk this cycle.
> 
> If you have any question don't hesitate to ask.
> 
> [1] https://wiki.gnome.org/Projects/GObjectIntrospection
> [2] https://wiki.gnome.org/Projects/PyGObject
> 
> On behalf of the Debian GNOME team,
> Jeremy Bicha

Bug#888818: marked as done ([blt] Binary (probably) incompatible with new Tcl/Tk versions (8.6))

[Debian Bug Tracking System]

Your message dated Tue, 30 Jan 2018 09:34:52 +
with message-id 
and subject line Bug#18: fixed in blt 2.5.3+dfsg-4
has caused the Debian Bug report #18,
regarding [blt] Binary (probably) incompatible with new Tcl/Tk versions (8.6)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
18: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=18
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: tk8.6-blt2.5
Version: 2.5.3+dfsg-3
Severity: serious
Affects: skycat

Dear maintainer,

Somewhere in the upgrade of Tcl/Tk 8.6, BLT got binary incompatible and
skycat (which uses BLT) crashes on start. Simply recompiling BLT helps here.

Due to the age of the binary package (last upload: 12/2015), it may be
worth to update the package to the newest Standards-Version instead of
just a binNMU.

Cheers

Ole
--- End Message ---
--- Begin Message ---
Source: blt
Source-Version: 2.5.3+dfsg-4

We believe that the bug you reported is fixed in the latest version of
blt, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 888...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Sergei Golovan  (supplier of updated blt package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 30 Jan 2018 11:57:16 +0300
Source: blt
Binary: tk8.6-blt2.5 blt blt-dev blt-demo
Architecture: source all amd64
Version: 2.5.3+dfsg-4
Distribution: unstable
Urgency: medium
Maintainer: Sergei Golovan 
Changed-By: Sergei Golovan 
Description:
 blt- graphics extension library for Tcl/Tk - run-time
 blt-demo   - graphics extension library for Tcl/Tk - demos and examples
 blt-dev- graphics extension library for Tcl/Tk - development files
 tk8.6-blt2.5 - graphics extension library for Tcl/Tk - library
Closes: 18
Changes:
 blt (2.5.3+dfsg-4) unstable; urgency=medium
 .
   * Rebuild to restore binary compatibility with the current Tcl/Tk 8.6
 (closes: #18).
   * Bump the debhelper compatibility level to 10.
   * Remove usage of autotools-dev and dh_autoreconf since they aren't
 necessary for debhelper compatibility level 10.
   * Bump the standards version to 4.1.3.
Checksums-Sha1:
 e19d24c83f5983696e3b8516535145c6014f9a10 1885 blt_2.5.3+dfsg-4.dsc
 393cdfadc808071bf944a9331c2bf35a42f468cb 57976 blt_2.5.3+dfsg-4.debian.tar.xz
 df3796dc129c736bba9a47aefb9b0580a289860c 494052 blt-demo_2.5.3+dfsg-4_all.deb
 12758fb558c86502e6c35f81a494041741cdd1e7 1061000 blt-dev_2.5.3+dfsg-4_amd64.deb
 176021265d3fc4af64c33b589105db3f6f851abc 7976 blt_2.5.3+dfsg-4_amd64.buildinfo
 cea6b4deef76dc6d933270a6c5209fb4ec6f1fec 14792 blt_2.5.3+dfsg-4_amd64.deb
 bd1e8cc5bc3639d40718ae4fa819662fa1364b11 4290224 
tk8.6-blt2.5-dbgsym_2.5.3+dfsg-4_amd64.deb
 923571559749bd20021fb12fee1345f704f5bb38 586520 
tk8.6-blt2.5_2.5.3+dfsg-4_amd64.deb
Checksums-Sha256:
 91166bfb0464fe92fcde3e8897a80613ae780a9d16aa6e6b3a81690f04e5cb99 1885 
blt_2.5.3+dfsg-4.dsc
 4aadc1682f5a26406e59540afead9ff7dfd1584da1a0ca1ec806426d88067524 57976 
blt_2.5.3+dfsg-4.debian.tar.xz
 58300f9285a26e458a840d5bcf0bae1753281389a7864a39d1d095a6c78bc9b9 494052 
blt-demo_2.5.3+dfsg-4_all.deb
 f3ed186d3da0e3fb4f44cf989472342de252b13afd59a5a22196700527fdff54 1061000 
blt-dev_2.5.3+dfsg-4_amd64.deb
 010252af5cdbbf2a3d710597fea75bee505efd08e29e24015a003dcdb485 7976 
blt_2.5.3+dfsg-4_amd64.buildinfo
 624e1c02bc1e72fa77523f514a606b7b7da3399def37995d016955b8d950584b 14792 
blt_2.5.3+dfsg-4_amd64.deb
 bdb49d11db2b27e7f98b85aa8c1519cba8d89808b286252d5633fdedda0375ac 4290224 
tk8.6-blt2.5-dbgsym_2.5.3+dfsg-4_amd64.deb
 752ed35d41bc98a1b79c61b196cfd479a695b6c8d6e6756a18221c4ece501f95 586520 
tk8.6-blt2.5_2.5.3+dfsg-4_amd64.deb
Files:
 7d769186a2e14949d0854ec7822be9d9 1885 devel optional blt_2.5.3+dfsg-4.dsc
 81e877c0308540fe00ea10435e7b1885 57976 devel optional 
blt_2.5.3+dfsg-4.debian.tar.xz
 2f89953c010177ebf2c5497508365729 494052 devel optional 
blt-demo_2.5.3+dfsg-4_all.deb
 b92411f6728a449e7b23a08f7b95a51d 1061000 devel optional 
blt-dev_2.5.3+dfsg-4_amd64.deb
 

Bug#887969: Problem has been fixed

[Hilko Bengen]

Control: fixed -1 1.1.28-1

The root cause for this bug had to do with the parameters that
libguestfs passes to qemu. A versioned build dependency on libguestfs
fixes this.

Cheers,
-Hilko

Processed: Problem has been fixed

[Debian Bug Tracking System]

Processing control commands:

> fixed -1 1.1.28-1
Bug #887969 [src:nbdkit] nbdkit FTBFS: test failures
Marked as fixed in versions nbdkit/1.1.28-1.

-- 
887969: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887969
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: found 888199 in 1.50.2-3, tagging 888199

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> found 888199 1.50.2-3
Bug #888199 {Done: Simon McVittie } [libgjs0g] gnome-shell 
crashes at different circumstances (not usable anymore)
Marked as found in versions gjs/1.50.2-3.
> tags 888199 - moreinfo
Bug #888199 {Done: Simon McVittie } [libgjs0g] gnome-shell 
crashes at different circumstances (not usable anymore)
Removed tag(s) moreinfo.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
888199: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888199
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#888422: marked as done (Mixing libmpfr4 and libmpfr6 doesn't work well)

[Debian Bug Tracking System]

Your message dated Tue, 30 Jan 2018 09:20:58 +
with message-id <e1egs66-00070w...@fasolo.debian.org>
and subject line Bug#888422: fixed in mpfr4 4.0.0-6
has caused the Debian Bug report #888422,
regarding Mixing libmpfr4 and libmpfr6 doesn't work well
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
888422: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888422
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libmpfr6
Version: 4.0.0-5
Severity: serious

Mixing libmpfr4 and libmpfr6 doesn't work well:

flint-arb FTBFS with:
/usr/bin/ld: warning: libmpfr.so.4, needed by /usr/lib/libflint.so, may 
conflict with libmpfr.so.6
/usr/bin/ld: mpfr_free_func: TLS definition in 
//usr/lib/x86_64-linux-gnu/libmpfr.so.4 section .tbss mismatches non-TLS 
definition in 
/usr/lib/gcc/x86_64-linux-gnu/7/../../../x86_64-linux-gnu/libmpfr.so section 
.text
//usr/lib/x86_64-linux-gnu/libmpfr.so.4: error adding symbols: Bad value
collect2: error: ld returned 1 exit status

Some packages like fractalnow FTBFS when gcc and libmpc3 use
different mpfr libraries, with a gcc ICE:
../../src/init2.c:52: MPFR assertion failed: p >= 2 && p <= 
((mpfr_prec_t)((mpfr_uprec_t)(~(mpfr_uprec_t)0)>>1))
src/fractal_compute_engine.c: In function 
'FractalLoopMANDELBROTPINTAVERAGECOLORINGDISCRETECURVATURENONESINGLE':
src/fractal_compute_engine.c:285:1: internal compiler error: Aborted

It is not even obvious in the latter case that this is always only an ICE,
and not sometimes a miscompilation.

The libmpc3 issue is also expected to hit users who have older gcc versions
still installed, e.g. gcc-6 still installed after stretch->buster upgrade.

When the dependencies are fulfilled users can expect to have working software,
even a forced removal on stretch->buster upgrades is better than runtime 
problems.
--- End Message ---
--- Begin Message ---
Source: mpfr4
Source-Version: 4.0.0-6

We believe that the bug you reported is fixed in the latest version of
mpfr4, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 888...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Matthias Klose <d...@debian.org> (supplier of updated mpfr4 package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 30 Jan 2018 09:33:00 +0100
Source: mpfr4
Binary: libmpfr6 libmpfr-dev libmpfr-doc
Architecture: source
Version: 4.0.0-6
Distribution: unstable
Urgency: medium
Maintainer: Debian GCC Maintainers <debian-...@lists.debian.org>
Changed-By: Matthias Klose <d...@debian.org>
Description:
 libmpfr-dev - multiple precision floating-point computation developers tools
 libmpfr-doc - multiple precision floating-point computation documentation
 libmpfr6   - multiple precision floating-point computation
Closes: 888422
Changes:
 mpfr4 (4.0.0-6) unstable; urgency=medium
 .
   * Update to the 4.0 branch 20180130.
   * libmpfr6: Break libmpc3 (<< 1.1.0-1~). Closes: #888422.
Checksums-Sha1:
 3fe3cebdc094623bad32c4255ce1d18fd24e5000 1972 mpfr4_4.0.0-6.dsc
 3fab8426f68e1082836b78a4db514f6c09b03bca 33472 mpfr4_4.0.0-6.debian.tar.xz
 675ef1b86b32d7f00053151ec116c9e9536d9e0f 5397 mpfr4_4.0.0-6_source.buildinfo
Checksums-Sha256:
 b1217fcb2bccf5374b9abe6f7a5c417b75950271fd7512ff3d367164b157f945 1972 
mpfr4_4.0.0-6.dsc
 8381734618b8bdebd553bef7d2cdf450a292cd5a9fd2dec3dd09d16f7146991b 33472 
mpfr4_4.0.0-6.debian.tar.xz
 94a149ec94515768285628999e9a414dc1a5e65db5009b51df90abf87035b9fd 5397 
mpfr4_4.0.0-6_source.buildinfo
Files:
 14b836ae977c84aa27e0c3d36d40594c 1972 math optional mpfr4_4.0.0-6.dsc
 560ab12bd6ecd3a9335d70f268b20b86 33472 math optional 
mpfr4_4.0.0-6.debian.tar.xz
 659ad29fe23d99821e19e0c96ff62827 5397 math optional 
mpfr4_4.0.0-6_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCAAuFiEE1WVxuIqLuvFAv2PWvX6qYHePpvUFAlpwMGcQHGRva29AZGVi
aWFuLm9yZwAKCRC9fqpgd4+m9dmPEACimoUZ6SmYhUhuFn5Bd206xdqcc4mz1VjM
P2cOwuSsInhs2eaguKspYAhChd4J3UYyZPUdi32Sv3k8iJTnfk6tZA6ZtdXtOEDT
+k6UwZEs9ESScdnQDwSXejE7RRf0NMDIiagmVIN3woSEjUbUjVNR8TQh+iqxJs9x
gcb4ippDEZPgqEedvpk2tV5pPiOK+nEjTgl9vKGBqxFWSCWRNLaBCtB+cVpSAA/5
oZHE+reK

Processed: notfixed 146113 in 0.15.1, fixed 146113 in 0.14.2.git20100726-1, notfixed 802509 in 1.60.0+dfsg-1 ...

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> # use fixed versions the bts knows about ...
> notfixed 146113 0.15.1
Bug #146113 {Done: Marc Haber } [aide] aide: 
sorted output 
There is no source info for the package 'aide' at version '0.15.1' with 
architecture ''
Unable to make a source version for version '0.15.1'
No longer marked as fixed in versions 0.15.1.
> fixed 146113 0.14.2.git20100726-1
Bug #146113 {Done: Marc Haber } [aide] aide: 
sorted output 
Marked as fixed in versions aide/0.14.2.git20100726-1.
> notfixed 802509 1.60.0+dfsg-1
Bug #802509 {Done: "Steve M. Robbins" } 
[libboost-coroutine-dev] libboost-coroutine-dev: The boost-coroutine library is 
only compiled as a static library
There is no source info for the package 'libboost-coroutine-dev' at version 
'1.60.0+dfsg-1' with architecture ''
Unable to make a source version for version '1.60.0+dfsg-1'
No longer marked as fixed in versions 1.60.0+dfsg-1.
> fixed 802509 1.60.0.1
Bug #802509 {Done: "Steve M. Robbins" } 
[libboost-coroutine-dev] libboost-coroutine-dev: The boost-coroutine library is 
only compiled as a static library
Marked as fixed in versions boost-defaults/1.60.0.1.
> fixed 820305 0.7.18-1
Bug #820305 {Done: Vincent Bernat } [python-netaddr] 
python-netaddr: IPSet is awfully slow
Marked as fixed in versions python-netaddr/0.7.18-1.
> fixed 85 3.1.2-3
Bug #85 {Done: Georg Faerber } [schleuder] schleuder: 
Create stretch backport
Marked as fixed in versions schleuder/3.1.2-3.
> fixed 876656 4.0.7+dfsg1-1
Bug #876656 {Done: Carsten Schoenert } [kicad] kicad: 
Bacport of version 4.0.8 to Jessie
Marked as fixed in versions kicad/4.0.7+dfsg1-1.
> notfixed 874876 0.8.2
Bug #874876 {Done: Innocent De Marchi } 
[src:fractalnow] [fractalnow] Future Qt4 removal from Buster
The source 'fractalnow' and version '0.8.2' do not appear to match any binary 
packages
No longer marked as fixed in versions fractalnow/0.8.2.
> fixed 874876 0.8.2-1
Bug #874876 {Done: Innocent De Marchi } 
[src:fractalnow] [fractalnow] Future Qt4 removal from Buster
Marked as fixed in versions fractalnow/0.8.2-1.
> notfixed 838995 1:1.35.7
Bug #838995 {Done: Marco d'Itri } [libguestfs0] No support for 
"/usr merge"
There is no source info for the package 'libguestfs0' at version '1:1.35.7' 
with architecture ''
Unable to make a source version for version '1:1.35.7'
No longer marked as fixed in versions 1:1.35.7.
> fixed 838995 1:1.35.7-1
Bug #838995 {Done: Marco d'Itri } [libguestfs0] No support for 
"/usr merge"
There is no source info for the package 'libguestfs0' at version '1:1.35.7-1' 
with architecture ''
Unable to make a source version for version '1:1.35.7-1'
Marked as fixed in versions 1:1.35.7-1.
> notfixed 880220 2007.11.08
Bug #880220 {Done: micah anderson } [leap-archive-keyring] 
should not install a globally valid trust anchor
There is no source info for the package 'leap-archive-keyring' at version 
'2007.11.08' with architecture ''
Unable to make a source version for version '2007.11.08'
No longer marked as fixed in versions 2007.11.08.
> fixed 880220 2017.11.08
Bug #880220 {Done: micah anderson } [leap-archive-keyring] 
should not install a globally valid trust anchor
Marked as fixed in versions leap-archive-keyring/2017.11.08.
> notfound 843347 0.10.0-6
Bug #843347 {Done: Ondrej Novy } [python-migrate-doc] 
python-migrate-doc: Section should be “doc”
No longer marked as found in versions migrate/0.10.0-6.
> fixed 873503 6.30.223.271-7
Bug #873503 {Done: Mathieu Malaterre } [src:broadcom-sta] 
broadcom-sta: Please backport 6.30.223.271-7 to stretch and jessie (sloppy)
Marked as fixed in versions broadcom-sta/6.30.223.271-7.
> reassign 853668 src:squid
Bug #853668 {Done: Santiago Garcia Mantinan } [src:squid3] 
squid3: ftbfs with GCC-7
Bug reassigned from package 'src:squid3' to 'src:squid'.
No longer marked as found in versions squid3/3.5.23-1.
No longer marked as fixed in versions squid/4.0.21-1~exp5.
> fixed 853668 4.0.21-1~exp5
Bug #853668 {Done: Santiago Garcia Mantinan } [src:squid] 
squid3: ftbfs with GCC-7
Marked as fixed in versions squid/4.0.21-1~exp5.
> found 853668 3.5.23-1
Bug #853668 {Done: Santiago Garcia Mantinan } [src:squid] 
squid3: ftbfs with GCC-7
The source 'squid' and version '3.5.23-1' do not appear to match any binary 
packages
Marked as found in versions squid/3.5.23-1.
> notfixed 873570 enlightenment/0.22.0-1
Bug #873570 {Done: Ross Vandegrift } [enlightenment] 
enlightenment: Crashes when toggling guake
The source enlightenment and version 0.22.0-1 do not appear to match any binary 
packages
No longer marked as fixed in versions 

Bug#888199: marked as done (gnome-shell crashes at different circumstances (not usable anymore))

[Debian Bug Tracking System]

Your message dated Tue, 30 Jan 2018 09:00:43 +
with message-id <20180130090043.ga8...@perpetual.pseudorandom.co.uk>
and subject line Re: Bug#888199: gnome-shell crashes at different circumstances 
(not usable anymore)
has caused the Debian Bug report #888199,
regarding gnome-shell crashes at different circumstances (not usable anymore)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
888199: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888199
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gnome-shell
Version: 3.26.2-4
Severity: grave
Justification: renders package unusable

Dear Maintainer,

(it began with 3.26.2-3 with today's apt-upgrade before 3.26.2-4 but
intel-microcode?? it crashes way more often)

For me actual gnome shell crashes

- seconds after establishing my network connection (which does not
  establish by itself anymore - bug with network-manager - time for
  another bug report)
- after resuming suspend
- and after one of the last circumstances it crashes directly after
  login

Nevertheless if on Wayland or X.

Because of these crashes gnome-shell gets unusable. Because of this I may have
problems to send you useful mails (journalctl attachment available, I hope
I can send it with reportbug, will try to send it via gnus with the next
post then). I can reproduce this problem
on two machines.


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

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

Versions of packages gnome-shell depends on:
ii  caribou  0.4.21-4
ii  dconf-gsettings-backend [gsettings-backend]  0.26.1-2
ii  evolution-data-server3.26.3-4
ii  gir1.2-accountsservice-1.0   0.6.45-1
ii  gir1.2-atspi-2.0 2.26.2-2
ii  gir1.2-caribou-1.0   0.4.21-4
ii  gir1.2-freedesktop   1.54.1-4
ii  gir1.2-gcr-3 3.20.0-6
ii  gir1.2-gdesktopenums-3.0 3.24.1-2
ii  gir1.2-gdm-1.0   3.26.2.1-3
ii  gir1.2-geoclue-2.0   2.4.7-1
ii  gir1.2-glib-2.0  1.54.1-4
ii  gir1.2-gnomebluetooth-1.03.26.1-2
ii  gir1.2-gnomedesktop-3.0  3.26.2-4
ii  gir1.2-gtk-3.0   3.22.26-2
ii  gir1.2-gweather-3.0  3.26.1-2
ii  gir1.2-ibus-1.0  1.5.17-3
ii  gir1.2-mutter-1  3.26.2-1
ii  gir1.2-nm-1.01.10.2-3
ii  gir1.2-nma-1.0   1.8.10-2
ii  gir1.2-pango-1.0 1.40.14-1
ii  gir1.2-polkit-1.00.105-18
ii  gir1.2-rsvg-2.0  2.40.20-2
ii  gir1.2-soup-2.4  2.60.2-2
ii  gir1.2-upowerglib-1.00.99.7-1
ii  gjs  1.50.2-3
ii  gnome-backgrounds3.26.2-2
ii  gnome-settings-daemon3.26.2-1
ii  gnome-shell-common   3.26.2-4
ii  gsettings-desktop-schemas3.24.1-2
ii  libasound2   1.1.3-5
ii  libatk-bridge2.0-0   2.26.1-1
ii  libatk1.0-0  2.26.1-2
ii  libc62.26-4
ii  libcairo21.15.8-3
ii  libcanberra-gtk3-0   0.30-6
ii  libcanberra0 0.30-6
ii  libcroco30.6.12-2
ii  libecal-1.2-19   3.26.3-4
ii  libedataserver-1.2-223.26.3-4
ii  libgcr-base-3-1  3.20.0-6
ii  libgdk-pixbuf2.0-0   2.36.11-1
ii  libgirepository-1.0-11.54.1-4
ii  libgjs0g [libgjs0-libmozjs-52-0] 1.50.3-1
ii  libglib2.0-0 2.54.3-1
ii  libglib2.0-bin   2.54.3-1
ii  libgstreamer1.0-0

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

[shirish शिरीष]

On 30/01/2018, intrigeri  wrote:
> Antoine Beaupre:
>> This bug makes torbrowser-launcher completely unusable on Debian
>> stretch, as soon as the browser is updated (as it should).
>
>> What's expected from stable users here? Is there going to be a stable
>> update for this?
>
> torbrowser-launcher is not included in Debian Stretch.

Its included in buster and the new fix has come in sid/unstable just
yesterday -

s> apt-cache policy torbrowser-launcher
torbrowser-launcher:
  Installed: 0.2.9-1
  Candidate: 0.2.9-1
  Version table:
 *** 0.2.9-1 100
  1 http://httpredir.debian.org/debian unstable/contrib amd64 Packages
100 /var/lib/dpkg/status
 0.2.8-6 900
900 http://httpredir.debian.org/debian buster/contrib amd64 Packages

>
> Cheers,
> --
> intrigeri
>
> --
> To unsubscribe, send mail to 888236-unsubscr...@bugs.debian.org.
>


-- 
  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#888818: [blt] Binary (probably) incompatible with new Tcl/Tk versions (8.6)

[Ole Streicher]

Package: tk8.6-blt2.5
Version: 2.5.3+dfsg-3
Severity: serious
Affects: skycat

Dear maintainer,

Somewhere in the upgrade of Tcl/Tk 8.6, BLT got binary incompatible and
skycat (which uses BLT) crashes on start. Simply recompiling BLT helps here.

Due to the age of the binary package (last upload: 12/2015), it may be
worth to update the package to the newest Standards-Version instead of
just a binNMU.

Cheers

Ole

Bug#887696: likwid FTBFS with glibc 2.26

[Christoph Martin]

Hi Juhani,

Am 29.01.2018 um 16:02 schrieb Juhani Numminen:
> 
> The directory ext/hwloc seems to be an embedded code copy of src:hwloc that
> is not listed by security-tracker-team.[1]
> 
> The failing file seems to be for hwloc private use only. Is it possible to
> use the package libhwloc-dev instead of the embedded copy?
> 
> [1] https://wiki.debian.org/EmbeddedCodeCopies
> 
> https://salsa.debian.org/security-tracker-team/security-tracker/blob/master/data/embedded-code-copies
> 

I've talked with upstream about this issue and they are working on build
with hwloc from the distribution.

Christoph

-- 

Christoph Martin, Leiter Unix-Systeme
Zentrum für Datenverarbeitung, Uni-Mainz, Germany
 Anselm Franz von Bentzel-Weg 12, 55128 Mainz
 Telefon: +49(6131)3926337
 Instant-Messaging: Jabber/XMPP: mar...@jabber.uni-mainz.de

<>

signature.asc
Description: OpenPGP digital signature

Bug#888816: libdbus-glib-1-doc: fails to upgrade from 'stable' to 'sid' - trying to overwrite /usr/share/doc/libdbus-glib-1-dev/AUTHORS

[Andreas Beckmann]

Package: libdbus-glib-1-doc
Version: 0.110-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'stable'.
It installed fine in 'stable', then the upgrade to 'sid' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/#overwriting-files-and-replacing-packages-replaces

This test intentionally skipped 'testing' to find file overwrite
problems before packages migrate from 'unstable' to 'testing'.

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

  Selecting previously unselected package libdbus-glib-1-doc.
  Preparing to unpack .../134-libdbus-glib-1-doc_0.110-1_all.deb ...
  Unpacking libdbus-glib-1-doc (0.110-1) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-rMgxvR/134-libdbus-glib-1-doc_0.110-1_all.deb (--unpack):
   trying to overwrite '/usr/share/doc/libdbus-glib-1-dev/AUTHORS', which is 
also in package libdbus-glib-1-dev 0.108-2
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /tmp/apt-dpkg-install-rMgxvR/134-libdbus-glib-1-doc_0.110-1_all.deb

This is probably caused by a behavioral change in dh_installdocs
in debhelper compat level 11.


cheers,

Andreas


libdbus-glib-1-dev=0.108-2_libdbus-glib-1-doc=0.110-1.log.gz
Description: application/gzip

Processed: reopening 886816, reassign 886816 to golang-go.uber-zap-dev ...

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reopen 886816
Bug #886816 {Done: Debian FTP Masters } 
[golang-go.uber-zap-dev,zap] golang-go.uber-zap-dev,zap: duplicate packages
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions 1.5.0+git20170802.3.e68420e-2+rm.
> reassign 886816 golang-go.uber-zap-dev 1.7.1+git20171031.f85c78b-3
Bug #886816 [golang-go.uber-zap-dev,zap] golang-go.uber-zap-dev,zap: duplicate 
packages
Bug reassigned from package 'golang-go.uber-zap-dev,zap' to 
'golang-go.uber-zap-dev'.
No longer marked as found in versions 
golang-go.uber-zap/1.7.1+git20171031.f85c78b-3, 
golang-go.uber-zap/1.7.1+git20171031.f85c78b-4, and 
zap/1.5.0+git20170802.3.e68420e-2.
Ignoring request to alter fixed versions of bug #886816 to the same values 
previously set
Bug #886816 [golang-go.uber-zap-dev] golang-go.uber-zap-dev,zap: duplicate 
packages
Marked as found in versions golang-go.uber-zap/1.7.1+git20171031.f85c78b-3.
> retitle 886816 golang-go.uber-zap-dev: needs Breaks+Replaces: zap
Bug #886816 [golang-go.uber-zap-dev] golang-go.uber-zap-dev,zap: duplicate 
packages
Changed Bug title to 'golang-go.uber-zap-dev: needs Breaks+Replaces: zap' from 
'golang-go.uber-zap-dev,zap: duplicate packages'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
886816: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886816
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#887696: likwid FTBFS with glibc 2.26

[Christoph Martin]

Hi Adrian,

Am 29.01.2018 um 10:55 schrieb Adrian Bunk:
> On Mon, Jan 29, 2018 at 10:50:20AM +0100, Christoph Martin wrote:
>> So, it should never be tried to be included. Could you please try to
>> find out why this is different in your setup?
>>
>> I can't reproduce this.
> 
> Please send me the log of your successful build in an up-to-date unstable.
> 
Sorry. You are right. I just found out that I already had a newer
version which fixes this issue.

I'll upload the fix soon.

Christoph

-- 

Christoph Martin, Leiter Unix-Systeme
Zentrum für Datenverarbeitung, Uni-Mainz, Germany
 Anselm Franz von Bentzel-Weg 12, 55128 Mainz
 Telefon: +49(6131)3926337
 Instant-Messaging: Jabber/XMPP: mar...@jabber.uni-mainz.de

<>

signature.asc
Description: OpenPGP digital signature