Bug#907335: marked as done (patsy FTBFS with Python 3.7 as supported version)

[Debian Bug Tracking System]

Your message dated Sun, 28 Oct 2018 05:55:30 +
with message-id 
and subject line Bug#907335: fixed in patsy 0.5.0+git13-g54dcf7b-1
has caused the Debian Bug report #907335,
regarding patsy FTBFS with Python 3.7 as supported version
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.)


-- 
907335: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907335
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: patsy
Version: 0.4.1+git34-ga5b54c2-1
Severity: serious
Tags: buster sid ftbfs

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

...
==
FAIL: patsy.test_build.test_DesignInfo_subset
--
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/nose/case.py", line 197, in runTest
self.test(*self.arg)
  File 
"/build/1st/patsy-0.4.1+git34-ga5b54c2/debian/tmp/usr/lib/python3/dist-packages/patsy/test_build.py",
 line 700, in test_DesignInfo_subset
t("~ 0 + x + y + z", ["x", "y", "z"], slice(None))
  File 
"/build/1st/patsy-0.4.1+git34-ga5b54c2/debian/tmp/usr/lib/python3/dist-packages/patsy/test_build.py",
 line 690, in t
sub_design_info = all_builder.subset(which_terms)
  File 
"/build/1st/patsy-0.4.1+git34-ga5b54c2/debian/tmp/usr/lib/python3/dist-packages/patsy/design_info.py",
 line 630, in subset
desc = ModelDesc.from_formula(which_terms)
  File 
"/build/1st/patsy-0.4.1+git34-ga5b54c2/debian/tmp/usr/lib/python3/dist-packages/patsy/desc.py",
 line 164, in from_formula
tree = parse_formula(tree_or_string)
  File 
"/build/1st/patsy-0.4.1+git34-ga5b54c2/debian/tmp/usr/lib/python3/dist-packages/patsy/parse_formula.py",
 line 148, in parse_formula
_atomic_token_types)
  File 
"/build/1st/patsy-0.4.1+git34-ga5b54c2/debian/tmp/usr/lib/python3/dist-packages/patsy/infix_parser.py",
 line 210, in infix_parse
for token in token_source:
  File 
"/build/1st/patsy-0.4.1+git34-ga5b54c2/debian/tmp/usr/lib/python3/dist-packages/patsy/parse_formula.py",
 line 94, in _tokenize_formula
yield _read_python_expr(it, end_tokens)
  File 
"/build/1st/patsy-0.4.1+git34-ga5b54c2/debian/tmp/usr/lib/python3/dist-packages/patsy/parse_formula.py",
 line 44, in _read_python_expr
for pytype, token_string, origin in it:
  File 
"/build/1st/patsy-0.4.1+git34-ga5b54c2/debian/tmp/usr/lib/python3/dist-packages/patsy/util.py",
 line 332, in next
return six.advance_iterator(self._it)
  File 
"/build/1st/patsy-0.4.1+git34-ga5b54c2/debian/tmp/usr/lib/python3/dist-packages/patsy/tokens.py",
 line 35, in python_tokenize
assert pytype not in (tokenize.NL, tokenize.NEWLINE)
AssertionError

==
FAIL: patsy.test_highlevel.test_formula_likes
--
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/nose/case.py", line 197, in runTest
self.test(*self.arg)
  File 
"/build/1st/patsy-0.4.1+git34-ga5b54c2/debian/tmp/usr/lib/python3/dist-packages/patsy/test_highlevel.py",
 line 255, in test_formula_likes
[[1], [2]], ["y"])
  File 
"/build/1st/patsy-0.4.1+git34-ga5b54c2/debian/tmp/usr/lib/python3/dist-packages/patsy/test_highlevel.py",
 line 87, in t
builders = incr_dbuilders(formula_like, data_iter_maker, depth)
  File 
"/build/1st/patsy-0.4.1+git34-ga5b54c2/debian/tmp/usr/lib/python3/dist-packages/patsy/highlevel.py",
 line 130, in incr_dbuilders
NA_action)
  File 
"/build/1st/patsy-0.4.1+git34-ga5b54c2/debian/tmp/usr/lib/python3/dist-packages/patsy/highlevel.py",
 line 62, in _try_incr_builders
formula_like = ModelDesc.from_formula(formula_like)
  File 
"/build/1st/patsy-0.4.1+git34-ga5b54c2/debian/tmp/usr/lib/python3/dist-packages/patsy/desc.py",
 line 164, in from_formula
tree = parse_formula(tree_or_string)
  File 
"/build/1st/patsy-0.4.1+git34-ga5b54c2/debian/tmp/usr/lib/python3/dist-packages/patsy/parse_formula.py",
 line 148, in parse_formula
_atomic_token_types)
  File 
"/build/1st/patsy-0.4.1+git34-ga5b54c2/debian/tmp/usr/lib/python3/dist-packages/patsy/infix_parser.py",
 line 210, in infix_parse
for token in token_source:
  File 
"/build/1st/patsy-0.4.1+git34-ga5b54c2/debian/tmp/usr/lib/python3/dist-packages/patsy/parse_formula.py",
 line 94, in _tokenize_formula
yield _read_python_expr(it, end_tokens)
  File 
"/build/1st/patsy-0.4.1+git34-ga5b54c2/debian/tmp/usr/lib/python3/dist-packages/patsy/parse_formula.py",
 line 44, in 

Bug#911976: bind-dyndb-ldap FTBFS with bind 9.11.5

[peter green]

Tags 911976 +patch
Thanks

This seems to be a simple case of a missing include, I just uploaded a fix to 
raspbian. A debdidf should appear soon at 
https://debdiffs.raspbian.org/main/b/bind-dyndb-ldap . No intent to NMU in 
Debian.

Bug#912061: marked as done (msgpack-c FTBFS with googletest 1.8.1-1)

[Debian Bug Tracking System]

Your message dated Sun, 28 Oct 2018 04:21:44 +
with message-id 
and subject line Bug#912061: fixed in msgpack-c 3.0.1-2
has caused the Debian Bug report #912061,
regarding msgpack-c FTBFS with googletest 1.8.1-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.)


-- 
912061: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912061
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: msgpack-c
Version: 3.0.1-1
Severity: serious
Tags: ftbfs

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

...
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/build/1st/msgpack-c-3.0.1'
mkdir build-gtest
cd build-gtest && \
  cmake -Wno-dev 
-DCMAKE_INSTALL_PREFIX=/build/1st/msgpack-c-3.0.1/build-gtest/install 
/usr/src/googletest/googletest && \
  make install
CMake Warning at CMakeLists.txt:47 (project):
  VERSION keyword not followed by a value or was followed by a value that
  expanded to nothing.


-- The CXX compiler identification is GNU 8.2.0
-- The C compiler identification is GNU 8.2.0
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Found PythonInterp: /usr/bin/python (found version "2.7.15") 
-- Looking for pthread.h
-- Looking for pthread.h - found
-- Looking for pthread_create
-- Looking for pthread_create - not found
-- Check if compiler accepts -pthread
-- Check if compiler accepts -pthread - yes
-- Found Threads: TRUE  
-- Configuring done
-- Generating done
-- Build files have been written to: /build/1st/msgpack-c-3.0.1/build-gtest
make[2]: Entering directory '/build/1st/msgpack-c-3.0.1/build-gtest'
make[2]: *** No rule to make target 'install'.  Stop.
--- End Message ---
--- Begin Message ---
Source: msgpack-c
Source-Version: 3.0.1-2

We believe that the bug you reported is fixed in the latest version of
msgpack-c, 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 912...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
James McCoy  (supplier of updated msgpack-c 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: Sat, 27 Oct 2018 23:57:16 -0400
Source: msgpack-c
Binary: libmsgpackc2 libmsgpack-dev libmsgpack-doc
Architecture: source
Version: 3.0.1-2
Distribution: unstable
Urgency: medium
Maintainer: James McCoy 
Changed-By: James McCoy 
Description:
 libmsgpack-dev - binary-based efficient object serialization library 
(development
 libmsgpack-doc - binary-based efficient object serialization library (docs)
 libmsgpackc2 - binary-based efficient object serialization library
Closes: 912061
Changes:
 msgpack-c (3.0.1-2) unstable; urgency=medium
 .
   * rules:
 + Do not fail build if build-gtest/ exists
 + Use -DBUILD_GMOCK=OFF to avoid building gmock, rather than trying to
   only build the googletest sub-directory (Closes: #912061)
 + Ensure dh_doxygen is called after dh_installdocs
   * Opt-in to debhelper 12 beta
   * Declare compliance with Policy 4.2.1, no changes needed
   * Add Build-Depends-Package to libmsgpackc2.symbols
Checksums-Sha1:
 11b1f0f0f1457f127ebfc7748355591ea0a88d08 2268 msgpack-c_3.0.1-2.dsc
 51039bd84db0d225514d257240f83c4453112a7d 7140 msgpack-c_3.0.1-2.debian.tar.xz
 4218a508df52a0b2879bfcdc4d7c034f90e8b656 10248 
msgpack-c_3.0.1-2_amd64.buildinfo
Checksums-Sha256:
 ff3c0cbc57b3a4f273beec1e4fc048110a0d0600409fc7f1a4cb02fdb9f252ff 2268 
msgpack-c_3.0.1-2.dsc
 85f64cb5fe6b39ceb0d34d7e637d87833e26d1066fc158af27e0ad7a1d34e711 7140 
msgpack-c_3.0.1-2.debian.tar.xz
 a5369292b4a41cbd47fd331a3f2af06cf1350c97035a5c817255220379f68c32 10248 
msgpack-c_3.0.1-2_amd64.buildinfo
Files:
 f99555e4c5dda152864095a79f494850 2268 libs optional msgpack-c_3.0.1-2.dsc
 

Bug#912061: Bug #912061 in msgpack-c marked as pending

[James McCoy]

Control: tag -1 pending

Hello,

Bug #912061 in msgpack-c reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below, and you can check the diff of the fix at:

https://salsa.debian.org/jamessan/msgpack-c/commit/aea33069def5664463e8cf197a45feea0271ba5f


rules: Use -DBUILD_GMOCK=OFF to avoid building gmock

googletest/googletest/CMakeLists.txt now depends on values set in
googletest/CMakeLists.txt, so pointing cmake at the sub-directory no
longer works.  Instead, explicitly use the option to avoid building
gmock.

Closes: #912061
Signed-off-by: James McCoy 



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/912061

Processed: Bug #912061 in msgpack-c marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #912061 [src:msgpack-c] msgpack-c FTBFS with googletest 1.8.1-1
Added tag(s) pending.

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

Bug#907335: similar issue

[Yaroslav Halchenko]

thanks!  upstream says the issue was fixed in
https://github.com/pydata/patsy/pull/131
so I will just build a fresh snapshot

Cheers!

On Sat, 27 Oct 2018, Julian Taylor wrote:

> this problem probably has the same python change as cause as this issue:

> https://github.com/PyCQA/pycodestyle/issues/786
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908700


-- 
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#905191: marked as done (libecm1-dev: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE)

[Debian Bug Tracking System]

Your message dated Sun, 28 Oct 2018 00:49:01 +
with message-id 
and subject line Bug#905191: fixed in gmp-ecm 7.0.4+ds-5
has caused the Debian Bug report #905191,
regarding libecm1-dev: unhandled symlink to directory conversion: 
/usr/share/doc/PACKAGE
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.)


-- 
905191: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905191
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libecm1-dev
Version: 7.0.4+ds-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

This was observed on the following upgrade paths:

  stretch -> buster

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

For other overwritten locations anything interesting may happen.

Note that dpkg intentionally does not replace directories with symlinks
and vice versa, you need the maintainer scripts to do this.
See in particular the end of point 4 in
https://www.debian.org/doc/debian-policy/#details-of-unpack-phase-of-installation-or-upgrade

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


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

0m29.3s ERROR: FAIL: silently overwrites files via directory symlinks:
  /usr/share/doc/libecm1-dev/AUTHORS (libecm1-dev:amd64) != 
/usr/share/doc/libecm1-dev-common/AUTHORS (?)
/usr/share/doc/libecm1-dev -> libecm1-dev-common
  /usr/share/doc/libecm1-dev/NEWS.gz (libecm1-dev:amd64) != 
/usr/share/doc/libecm1-dev-common/NEWS.gz (?)
/usr/share/doc/libecm1-dev -> libecm1-dev-common
  /usr/share/doc/libecm1-dev/README.gz (libecm1-dev:amd64) != 
/usr/share/doc/libecm1-dev-common/README.gz (?)
/usr/share/doc/libecm1-dev -> libecm1-dev-common
  /usr/share/doc/libecm1-dev/README.lib.gz (libecm1-dev:amd64) != 
/usr/share/doc/libecm1-dev-common/README.lib.gz (?)
/usr/share/doc/libecm1-dev -> libecm1-dev-common
  /usr/share/doc/libecm1-dev/changelog.Debian.gz (libecm1-dev:amd64) != 
/usr/share/doc/libecm1-dev-common/changelog.Debian.gz (libecm1-dev-common)
/usr/share/doc/libecm1-dev -> libecm1-dev-common
  /usr/share/doc/libecm1-dev/changelog.gz (libecm1-dev:amd64) != 
/usr/share/doc/libecm1-dev-common/changelog.gz (libecm1-dev-common)
/usr/share/doc/libecm1-dev -> libecm1-dev-common
  /usr/share/doc/libecm1-dev/copyright (libecm1-dev:amd64) != 
/usr/share/doc/libecm1-dev-common/copyright (libecm1-dev-common)
/usr/share/doc/libecm1-dev -> libecm1-dev-common
  /usr/share/doc/libecm1-dev/examples (libecm1-dev:amd64) != 
/usr/share/doc/libecm1-dev-common/examples (?)
/usr/share/doc/libecm1-dev -> libecm1-dev-common
  /usr/share/doc/libecm1-dev/examples/Makefile (libecm1-dev:amd64) != 
/usr/share/doc/libecm1-dev-common/examples/Makefile (?)
/usr/share/doc/libecm1-dev -> libecm1-dev-common
  /usr/share/doc/libecm1-dev/examples/ecmfactor.c (libecm1-dev:amd64) != 
/usr/share/doc/libecm1-dev-common/examples/ecmfactor.c (?)
/usr/share/doc/libecm1-dev -> libecm1-dev-common


cheers,

Andreas


libecm1-dev_7.0.4+ds-2.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: gmp-ecm
Source-Version: 7.0.4+ds-5

We believe that the bug you reported is fixed in the latest version of
gmp-ecm, 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 905...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Jerome Benoit  (supplier of updated 

Bug#906603: marked as done (joblib: FTBFS in buster/sid (failing tests))

[Debian Bug Tracking System]

Your message dated Sat, 27 Oct 2018 20:35:53 -0400
with message-id <20181028003553.gh3...@hopa.kiewit.dartmouth.edu>
and subject line Re: Bug#906603: Can't reproduce.
has caused the Debian Bug report #906603,
regarding joblib: FTBFS in buster/sid (failing 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.)


-- 
906603: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906603
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:joblib
Version: 0.12.1-1
Severity: serious
Tags: ftbfs

Hello Yaroslav.

I tried to build this package in buster but it failed:


[...]
 debian/rules build-indep
dh build-indep --buildsystem=python_distutils --with=python2,python3
dh: Compatibility levels before 9 are deprecated (level 7 in use)
   dh_update_autotools_config -i -O--buildsystem=python_distutils
   dh_auto_configure -i -O--buildsystem=python_distutils
dh_auto_configure: Compatibility levels before 9 are deprecated (level 7 in use)
dh_auto_configure: Please use the third-party "pybuild" build system instead of 
python-distutils
dh_auto_configure: This feature will be removed in compat 12.
   dh_auto_build -i -O--buildsystem=python_distutils
dh_auto_build: Compatibility levels before 9 are deprecated (level 7 in use)
dh_auto_build: Please use the third-party "pybuild" build system instead of 
python-distutils
dh_auto_build: This feature will be removed in compat 12.
python setup.py build --force
running build

[... snipped ...]

E [('ThreadingBackend', 0),
E +  ('ThreadingBackend', 1),
E -  ('SequentialBackend', 0),
E ?^
E +  ('SequentialBackend', 2),...
E 
E ...Full output truncated (7 lines hidden), use '-vv' to show

joblib/test/test_parallel.py:1316: AssertionError
== 2 failed, 1068 passed, 9 skipped in 68.41 seconds ===
[INFO:MainProcess:Dummy-466] process shutting down
[DEBUG:MainProcess:Dummy-466] running all "atexit" finalizers with priority >= 0
[DEBUG:MainProcess:Dummy-466] Interpreter shutting down. Waking up 
queue_manager_threads []
[DEBUG:MainProcess:Dummy-466] finalizing pool
[DEBUG:MainProcess:Dummy-466] helping task handler/workers to finish
[DEBUG:MainProcess:Dummy-466] removing tasks from inqueue until task handler 
finished
[DEBUG:MainProcess:Thread-40] worker handler exiting
[DEBUG:MainProcess:Thread-41] task handler got sentinel
[DEBUG:MainProcess:Thread-41] task handler sending sentinel to result handler
[DEBUG:MainProcess:Thread-41] task handler sending sentinel to workers
[DEBUG:MainProcess:Thread-41] task handler exiting
[DEBUG:MainProcess:Thread-42] result handler got sentinel
[DEBUG:MainProcess:Thread-42] ensuring that outqueue is not full
[DEBUG:MainProcess:Thread-42] result handler exiting: len(cache)=0, 
thread._state=0
[DEBUG:PoolWorker-78:MainThread] worker got sentinel -- exiting
[DEBUG:PoolWorker-78:MainThread] worker exiting after 1 tasks
[INFO:PoolWorker-78:MainThread] process shutting down
[DEBUG:PoolWorker-78:MainThread] running all "atexit" finalizers with priority 
>= 0
[DEBUG:PoolWorker-78:MainThread] running the remaining "atexit" finalizers
[INFO:PoolWorker-78:MainThread] process exiting with exitcode 0
[DEBUG:PoolWorker-79:MainThread] worker got sentinel -- exiting
[DEBUG:PoolWorker-79:MainThread] worker exiting after 0 tasks
[INFO:PoolWorker-79:MainThread] process shutting down
[DEBUG:PoolWorker-79:MainThread] running all "atexit" finalizers with priority 
>= 0
[DEBUG:PoolWorker-79:MainThread] running the remaining "atexit" finalizers
[INFO:PoolWorker-79:MainThread] process exiting with exitcode 0
[DEBUG:MainProcess:Dummy-466] joining worker handler
[DEBUG:MainProcess:Dummy-466] terminating workers
[DEBUG:MainProcess:Dummy-466] joining task handler
[DEBUG:MainProcess:Dummy-466] joining result handler
[DEBUG:MainProcess:Dummy-466] joining pool workers
[DEBUG:MainProcess:Dummy-466] cleaning up worker 9504
[DEBUG:MainProcess:Dummy-466] running the remaining "atexit" finalizers
make[1]: *** [debian/rules:25: python-test2.7] Error 1
make[1]: Leaving directory '/<>'
make: *** [debian/rules:10: build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


The build was made with "dpkg-buildpackage -A" in my autobuilder,
but it also fails here:

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

I have not checked 

Bug#894675: Info received (gdebi-gtk is not installing packages)

[Cagla Alican]

Opening

Bug#894675: gdebi-gtk is not installing packages

[Cagla Alican]

Opening

23 Eki 2018 ÖS 10:40 tarihinde cagla.bak...@hotmail.com yazdı:

On Sat, 23 Jun 2018 20:58:59 +0800 Boyuan Yang <073p...@gmail.com> wrote:
> Version: 0.9.5.7+nmu2
>
> On Tue, 3 Apr 2018 08:59:52 +0200 Narcis Garcia  wrote:
> > Package: gdebi
> > Version: 0.9.5.7+nmu1
> > Severity: grave
> >
> > Package structure interface appears and it's usable; if user tries
> > button [Install Package], gksu asks for authorisation and nothing more:
> > package is not installed and gdebi-gtk disappears.
> >
> > $ gdebi-gtk AnyPackage.deb
> > /home/user/.gtkrc-2.0:38: Unable to find include file: "main.rc"
> > /home/user/.gtkrc-2.0:39: Unable to find include file: "apps.rc"
> > /home/user/.gtkrc-2.0:40: Unable to find include file: "hacks.rc"
> > /home/user/.gtkrc-2.0:41: Unable to find include file: "hacks-dark.rc"
> > $ echo $?
> > 1
> >
> >
> > *.rc messages appear just when pressing [Install Package] button
> > Execution ends just after gksu authorisation.
>
> With the migration away from gksu in v0.9.5.7+nmu2, this bug should be fixed.
> I have tested installation with new version and no error took place. Closing
> this bug now.
>
> Please feel free to reopen this bug and provide with more information if you
> consider this bug still exists.
>
> --
> Regards,
> Boyuan Yang

Watch entire
The following URL
Lenovo TAB 2 A8-50

Bug#912081: Why/how is this package even in Debian?

[Steve McIntyre]

Package: mpi-testsuite
Version: 3.2+dfsg-1
Severity: grave

I've been trying to debug why this package is *semi-randomly* failing
for me when attempting to rebuild it for armel and armhf on arm64
systems. Looking at failed build logs, I can see lots and lots of
nasty-looking error messages warning about segmentation faults,
floating point exceptions etc. Then I checked in the "successful"
build logs and I'm seeing exactly the same stuff.

So I've just checked in the logs from Debian's buildds and I'm seeing
exactly the same kind of thing. These errors are not being picked up
on at all in the "successful" builds. Failed builds are typically
being failed for timing out, not for any error checking in the build.

What is this package even for? Why should it be in Debian in this state?

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

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

Processed: marble: diff for NMU version 4:17.08.3-3.1

[Debian Bug Tracking System]

Processing control commands:

> tags 879756 + pending
Bug #879756 [marble-maps] marble-maps: does not start
Added tag(s) pending.

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

Bug#879756: marble: diff for NMU version 4:17.08.3-3.1

[reiner]

Control: tags 879756 + pending

Dear maintainer,

I've prepared an NMU for marble (versioned as 4:17.08.3-3.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

Regards.

diff -Nru marble-17.08.3/debian/changelog marble-17.08.3/debian/changelog
--- marble-17.08.3/debian/changelog 2018-01-11 14:31:18.0 +0100
+++ marble-17.08.3/debian/changelog 2018-10-27 13:38:29.0 +0200
@@ -1,3 +1,11 @@
+marble (4:17.08.3-3.1) unstable; urgency=low
+
+  * Non-maintainer upload.
+  * Add missing qml-module dependencies for marble-maps. (Closes: #879756)
+  * Add patch to build with Qt 5.11 by including missing headers.
+
+ -- Reiner Herrmann   Sat, 27 Oct 2018 13:38:29 +0200
+
 marble (4:17.08.3-3) unstable; urgency=medium
 
   * Team upload.
diff -Nru marble-17.08.3/debian/control marble-17.08.3/debian/control
--- marble-17.08.3/debian/control   2018-01-02 20:00:03.0 +0100
+++ marble-17.08.3/debian/control   2018-10-27 13:37:34.0 +0200
@@ -145,7 +145,12 @@
 Section: misc
 Depends: marble-data (>= ${source:Version}),
  marble-plugins (= ${binary:Version}),
+ qml-module-qtgraphicaleffects,
  qml-module-qtmultimedia,
+ qml-module-qtquick-dialogs,
+ qml-module-qtquick-controls,
+ qml-module-qtquick-controls2,
+ qml-module-qtquick-window2,
  ${misc:Depends},
  ${shlibs:Depends},
 Suggests: gosmore, monav-routing-daemon, routino
diff -Nru marble-17.08.3/debian/patches/qt5.11.patch 
marble-17.08.3/debian/patches/qt5.11.patch
--- marble-17.08.3/debian/patches/qt5.11.patch  1970-01-01 01:00:00.0 
+0100
+++ marble-17.08.3/debian/patches/qt5.11.patch  2018-10-27 13:38:29.0 
+0200
@@ -0,0 +1,58 @@
+Author: Reiner Herrmann 
+Description: Fix build with Qt 5.11
+
+--- a/src/plugins/render/gpsinfo/GpsInfo.cpp
 b/src/plugins/render/gpsinfo/GpsInfo.cpp
+@@ -21,6 +21,8 @@
+ #include "ViewportParams.h"
+ #include "GeoDataAccuracy.h"
+ 
++#include 
++
+ namespace Marble
+ {
+ 
+--- a/src/plugins/render/speedometer/Speedometer.cpp
 b/src/plugins/render/speedometer/Speedometer.cpp
+@@ -19,6 +19,8 @@
+ #include "MarbleGraphicsGridLayout.h"
+ #include "ViewportParams.h"
+ 
++#include 
++
+ namespace Marble
+ {
+ 
+--- a/src/lib/marble/RenderPlugin.h
 b/src/lib/marble/RenderPlugin.h
+@@ -14,6 +14,9 @@
+ #ifndef MARBLE_RENDERPLUGIN_H
+ #define MARBLE_RENDERPLUGIN_H
+ 
++#include 
++#include 
++#include 
+ #include 
+ #include 
+ #include 
+@@ -22,10 +25,6 @@
+ #include "marble_export.h"
+ 
+ 
+-class QAction;
+-class QActionGroup;
+-class QStandardItem;
+-
+ namespace Marble
+ {
+ 
+--- a/src/plugins/render/satellites/SatellitesPlugin.cpp
 b/src/plugins/render/satellites/SatellitesPlugin.cpp
+@@ -25,6 +25,7 @@
+ 
+ #include "ui_SatellitesConfigDialog.h"
+ 
++#include 
+ #include 
+ #include 
+ 
diff -Nru marble-17.08.3/debian/patches/series 
marble-17.08.3/debian/patches/series
--- marble-17.08.3/debian/patches/series2016-06-04 10:59:56.0 
+0200
+++ marble-17.08.3/debian/patches/series2018-10-27 13:38:29.0 
+0200
@@ -1,2 +1,3 @@
 do_not_install_private_headers
 kubuntu_disable-MarbleRunnerManagerTest.diff
+qt5.11.patch

Bug#912078: libbenchmark-dev: libbenchmark_main.a referenced by benchmarkTargets-none.cmake is not shipped

[Adrian Bunk]

Package: libbenchmark-dev
Version: 1.4.1-1
Severity: serious
Control: affects -1 src:cctz

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

...
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/build/1st/cctz-2.2+dfsg1'
dh_auto_configure -- -DVERSION="2.2+dfsg1" -DSOVERSION="2"
cd obj-x86_64-linux-gnu && cmake -DCMAKE_INSTALL_PREFIX=/usr 
-DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc 
-DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON 
-DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON "-GUnix Makefiles" 
-DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu 
-DVERSION=2.2\+dfsg1 -DSOVERSION=2 ..
-- The C compiler identification is GNU 8.2.0
-- The CXX compiler identification is GNU 8.2.0
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
CMake Error at /usr/lib/cmake/benchmark/benchmarkTargets.cmake:96 (message):
  The imported target "benchmark::benchmark_main" references the file

 "/usr/lib/x86_64-linux-gnu/libbenchmark_main.a"

  but this file does not exist.  Possible reasons include:

  * The file was deleted, renamed, or moved to another location.

  * An install or uninstall procedure did not complete successfully.

  * The installation package was faulty and contained

 "/usr/lib/cmake/benchmark/benchmarkTargets.cmake"

  but not all the files it references.

Call Stack (most recent call first):
  /usr/lib/cmake/benchmark/benchmarkConfig.cmake:1 (include)
  CMakeLists.txt:16 (find_package)


-- Configuring incomplete, errors occurred!

Processed: libbenchmark-dev: libbenchmark_main.a referenced by benchmarkTargets-none.cmake is not shipped

[Debian Bug Tracking System]

Processing control commands:

> affects -1 src:cctz
Bug #912078 [libbenchmark-dev] libbenchmark-dev: libbenchmark_main.a referenced 
by benchmarkTargets-none.cmake is not shipped
Added indication that 912078 affects src:cctz

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

Bug#906855: gnome-chemistry-utils: diff for NMU version 0.14.17-1.1

[Adrian Bunk]

Control: tags 890980 + pending
Control: tags 906855 + patch
Control: tags 906855 + pending

Dear maintainer,

I've prepared an NMU for gnome-chemistry-utils (versioned as 0.14.17-1.1) and
uploaded it to DELAYED/15. Please feel free to tell me if I
should cancel it.

cu
Adrian

-- 

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

diff -Nru gnome-chemistry-utils-0.14.17/debian/changelog gnome-chemistry-utils-0.14.17/debian/changelog
--- gnome-chemistry-utils-0.14.17/debian/changelog	2018-01-14 01:50:37.0 +0200
+++ gnome-chemistry-utils-0.14.17/debian/changelog	2018-10-28 01:35:58.0 +0300
@@ -1,3 +1,11 @@
+gnome-chemistry-utils (0.14.17-1.1) unstable; urgency=low
+
+  * Non-maintainer upload.
+  * Add upstream fix for FTBFS with gnumeric >= 1.12.42.
+  * Drop the obsolete gcu-plugin. (Closes: #906855, #890980)
+
+ -- Adrian Bunk   Sun, 28 Oct 2018 01:35:58 +0300
+
 gnome-chemistry-utils (0.14.17-1) unstable; urgency=medium
 
   * New upstream release.
diff -Nru gnome-chemistry-utils-0.14.17/debian/control gnome-chemistry-utils-0.14.17/debian/control
--- gnome-chemistry-utils-0.14.17/debian/control	2018-01-14 01:50:31.0 +0200
+++ gnome-chemistry-utils-0.14.17/debian/control	2018-10-28 01:35:58.0 +0300
@@ -27,7 +27,6 @@
libtool (>= 2.2.6),
libx11-dev (>= 1.0.0),
libxml2-dev (>= 2.4.16),
-   npapi-sdk-dev,
shared-mime-info (>= 0.12),
xsltproc,
zlib1g-dev | libz-dev
@@ -69,20 +68,6 @@
   * a periodic table of the elements (GChemTable)
   * a spectra viewer (GSpectrum)
 
-Package: gcu-plugin
-Architecture: any
-Depends: libgcu0v5 (= ${binary:Version}),
- ${misc:Depends},
- ${shlibs:Depends},
- ${vendor:Browser}
-Description: GNOME chemistry utils (browser plugin)
- The GNOME Chemistry Utils provide C++ classes and Gtk+-2 widgets
- related to chemistry. They will be used in future versions of both
- gcrystal and gchempaint.
- .
- This package provides a browser plugin for Gecko-based browsers.
- It does not (yet) work with WebKit-based browsers.
-
 Package: gcrystal
 Architecture: any
 Depends: chemical-mime-data,
diff -Nru gnome-chemistry-utils-0.14.17/debian/gcu-plugin.install gnome-chemistry-utils-0.14.17/debian/gcu-plugin.install
--- gnome-chemistry-utils-0.14.17/debian/gcu-plugin.install	2016-10-03 13:58:51.0 +0300
+++ gnome-chemistry-utils-0.14.17/debian/gcu-plugin.install	1970-01-01 02:00:00.0 +0200
@@ -1,2 +0,0 @@
-usr/lib/*/gchemutils/chem-viewer
-usr/lib/*/mozilla/plugins/*.so
diff -Nru gnome-chemistry-utils-0.14.17/debian/patches/gnumeric-ftbfs.patch gnome-chemistry-utils-0.14.17/debian/patches/gnumeric-ftbfs.patch
--- gnome-chemistry-utils-0.14.17/debian/patches/gnumeric-ftbfs.patch	1970-01-01 02:00:00.0 +0200
+++ gnome-chemistry-utils-0.14.17/debian/patches/gnumeric-ftbfs.patch	2018-10-28 01:35:58.0 +0300
@@ -0,0 +1,47 @@
+Index: gchemutils/configure.ac
+===
+--- gchemutils/configure.ac	(revision 2072)
 gchemutils/configure.ac	(revision 2073)
+@@ -352,7 +352,7 @@
+   libspreadsheet=libspreadsheet-1.12
+ fi
+ 
+-PKG_CHECK_MODULES(gnumeric, [$libspreadsheet >= 1.11.6], [build_gnumeric_plugin=yes],
++PKG_CHECK_MODULES(gnumeric, [$libspreadsheet >= 1.12.42], [build_gnumeric_plugin=yes],
+ 		[build_gnumeric_plugin=no])
+ dnl --without is not handled
+ 
+Index: gchemutils/gnumeric/functions.cc
+===
+--- gchemutils/gnumeric/functions.cc	(revision 2072)
 gchemutils/gnumeric/functions.cc	(revision 2073)
+@@ -195,23 +195,23 @@
+ const GnmFuncDescriptor Chemistry_functions[] = {
+ 
+ { N_("molarmass"),   "s",
+-			help_molarmass, gnumeric_molarmass, NULL, NULL, NULL,
++			help_molarmass, gnumeric_molarmass, NULL,
+ 			GNM_FUNC_SIMPLE, GNM_FUNC_IMPL_STATUS_COMPLETE, GNM_FUNC_TEST_STATUS_NO_TESTSUITE},
+ { N_("monoisotopicmass"),   "s",
+-			help_monoisotopicmass, gnumeric_monoisotopicmass, NULL, NULL, NULL,
++			help_monoisotopicmass, gnumeric_monoisotopicmass, NULL,
+ 			GNM_FUNC_SIMPLE, GNM_FUNC_IMPL_STATUS_COMPLETE, GNM_FUNC_TEST_STATUS_NO_TESTSUITE},
+ { N_("chemcomposition"),   "ss",
+-			help_chemcomposition, gnumeric_chemcomposition, NULL, NULL, NULL,
++			help_chemcomposition, gnumeric_chemcomposition, NULL,
+ 			GNM_FUNC_SIMPLE, GNM_FUNC_IMPL_STATUS_COMPLETE, GNM_FUNC_TEST_STATUS_NO_TESTSUITE},
+ { N_("elementnumber"),   "s",
+-			help_elementnumber, gnumeric_elementnumber, NULL, NULL, NULL,
++			help_elementnumber, gnumeric_elementnumber, NULL,
+ 			GNM_FUNC_SIMPLE, GNM_FUNC_IMPL_STATUS_COMPLETE, GNM_FUNC_TEST_STATUS_NO_TESTSUITE},
+ 

Processed: gnome-chemistry-utils: diff for NMU version 0.14.17-1.1

[Debian Bug Tracking System]

Processing control commands:

> tags 890980 + pending
Bug #890980 [src:gnome-chemistry-utils] gnome-chemistry-utils: please downgrade 
dependency on browser
Added tag(s) pending.
> tags 906855 + patch
Bug #906855 [gcu-plugin] gcu-plugin: NPAPI plugins are no longer supported by 
firefox-esr
Added tag(s) patch.
> tags 906855 + pending
Bug #906855 [gcu-plugin] gcu-plugin: NPAPI plugins are no longer supported by 
firefox-esr
Added tag(s) pending.

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

Bug#912073: marked as done (No initramfs generated if new kernel package installed by upgrade)

[Debian Bug Tracking System]

Your message dated Sat, 27 Oct 2018 22:34:16 +
with message-id 
and subject line Bug#912073: fixed in pkgsel 0.61
has caused the Debian Bug report #912073,
regarding No initramfs generated if new kernel package installed by upgrade
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.)


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

While testing a fix for #908711, I found that pkgsel diverts
update-initramfs during the upgrade and installation process
and runs it once at the end.

By default, "update-initramfs -u" updates the new initramfs for the
newest kernel version that update-initramfs was previously run for.
If a new kernel package was installed due to an ABI bump, no new
initramfs will be generated.  This causes the system to fail to
boot.

Ben.

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

Kernel: Linux 4.18.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Source: pkgsel
Source-Version: 0.61

We believe that the bug you reported is fixed in the latest version of
pkgsel, 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 912...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Ben Hutchings  (supplier of updated pkgsel 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: Sat, 27 Oct 2018 23:19:13 +0100
Source: pkgsel
Binary: pkgsel
Architecture: source
Version: 0.61
Distribution: unstable
Urgency: medium
Maintainer: Debian Install System Team 
Changed-By: Ben Hutchings 
Description:
 pkgsel - Select and install packages (udeb)
Closes: 908711 912073
Changes:
 pkgsel (0.61) unstable; urgency=medium
 .
   * Install new dependencies when safe-upgrade (default) is selected
 (Closes: #908711)
   * Allow update-initramfs to run normally during package upgrade and
 installation (Closes: #912073)
Checksums-Sha1:
 f9a54e694d52ec258c24c13c57d60b408615e79d 1591 pkgsel_0.61.dsc
 9c4e1e0c424f837f81c80c530a215872fb42e126 51908 pkgsel_0.61.tar.xz
 0215d9dfd0637e797fa1002291d2e5392ed6da59 5153 pkgsel_0.61_source.buildinfo
Checksums-Sha256:
 ee9a00276026e44056b6d66e349d904fb8c5120f80cb0b2d120f266b95023191 1591 
pkgsel_0.61.dsc
 44e5afbb45fb8b341e1970d3b373835aa5f6a239c100ffa92dca96becda96190 51908 
pkgsel_0.61.tar.xz
 adaca32ee52cca5f1742f8fab1ab7bb7fdeabb4787b2748d72b3faaafce1a5a3 5153 
pkgsel_0.61_source.buildinfo
Files:
 2f365d94fc83e321d2370beddd47ec21 1591 debian-installer standard pkgsel_0.61.dsc
 50e06b4b69416f3e276558cab5005608 51908 debian-installer standard 
pkgsel_0.61.tar.xz
 357476cee3242b7ce9a7a3e84405256e 5153 debian-installer standard 
pkgsel_0.61_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEErCspvTSmr92z9o8157/I7JWGEQkFAlvU5MEACgkQ57/I7JWG
EQmQKg/+K6MQQygZZb9QbdY/JGZPSaUbGIqOv+/Te/xBqx/fWBpuX7IT+uHzAsk0
wKZ63v7ItTDtRoTZ4mxeciMPg8id8GIJvteji77VIknMDsYXVmvjVaU2lh1klQHB
XuLc0gQEjV/0MIj5vm/b0x9UsT1TNjXTz2WEjgMY1NeomO2O9iMKru6cs3G/Kv3B
mCakH/nTRtQz2BenL5yo6yqbJUK+toNnrTapZou8RjWmttjsaZRUSs18YrOiJ7EC
vtuH8qG6kly/rIv3/X4PD/LwzXhIKXeHssNdtr5bkwq4tA2MbNBCRzLvmxFZkMgd
/+0xmWCLHAtAK/DzDbaqmuZ0wBfn7oc3TsB608Yx6yfummkRIJ+t9irGztmzzcJ3
rjTfi0i7Y5V0fqMJd1//LkT3Bd/5aEmz/C9XluIBKYwXe7KNliBQTZRcwL0VvCPt
oAQ6+CqC/wQJP0pZRab2tYLvf3GLn0L8zB6rFEZl/uf8tdyBnX0BK3VzVaSfe3rH
FGCM2luynmrGGVDMxuITXJgEluQs5NScknfu+9URWWzSLqxuR4yFPKL9eK03P9lZ
DEevnyCIq8LgiqwsRG5lL5n90unJvMT8UbzX53YpD+rocjokWYPDbM2srQGp/nrW
eboPibLXxncyoQilbNCNXWU8QvwMGj9gaRDP28R/H/WXVpk1Szs=
=bWJU
-END PGP SIGNATURE End Message ---

Bug#912073: Bug #912073 in pkgsel marked as pending

[Ben Hutchings]

Control: tag -1 pending

Hello,

Bug #912073 in pkgsel reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below, and you can check the diff of the fix at:

https://salsa.debian.org/installer-team/pkgsel/commit/a98931788ac35cd6916cddffb2d5a13ac31edd74


Allow update-initramfs to run normally during package upgrade and installation

pkgsel's diversion of update-initramfs during package upgrade and
installation means that if a new kernel package is installed due to an
ABI bump, it won't have an initramfs image.

Running "update-initramfs -u" afterwards doesn't help, because that
only updates the most recent initramfs image that's already present.
For a new kernel package, we would need to run
"update-initramfs -c -k ".

Also, during package installation "update-initramfs -u" normally only
activates a trigger, so updates will be coalesced anyway.

Instead of making this hack more complicated, remove it:

* Don't divert update-initramfs
* Move the setup code needed for update-initramfs before the first upgrade
* Move the cleanup code to the cleanup function

Closes: #912073



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/912073

Processed: Bug #912073 in pkgsel marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #912073 [pkgsel] No initramfs generated if new kernel package installed by 
upgrade
Added tag(s) pending.

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

Bug#911943: marked as done (openhft-compiler FTBFS: missing Build-Depends: libeasymock-java)

[Debian Bug Tracking System]

Your message dated Sat, 27 Oct 2018 22:19:01 +
with message-id 
and subject line Bug#911943: fixed in openhft-compiler 2.2.4-2
has caused the Debian Bug report #911943,
regarding openhft-compiler FTBFS: missing Build-Depends: libeasymock-java
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.)


-- 
911943: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911943
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: openhft-compiler
Version: 2.2.4-1
Severity: serious
Tags: ftbfs patch

openhft-compiler fails to build from source in unstable:

https://tests.reproducible-builds.org/debian/rbuild/unstable/amd64/openhft-compiler_2.2.4-1.rbuild.log.gz

| [ERROR] Failed to execute goal on project compiler: Could not resolve 
dependencies for project net.openhft:compiler:bundle:2.2.4: Cannot access 
sonatype-nexus-staging (https://oss.sonatype.org/content/repositories/staging) 
in offline mode and the artifact org.easymock:easymock:jar:debian has not been 
downloaded from it before. -> [Help 1]

Please add "libeasymock-java" to Build-Depends. That makes it build
successfully.

Helmut
--- End Message ---
--- Begin Message ---
Source: openhft-compiler
Source-Version: 2.2.4-2

We believe that the bug you reported is fixed in the latest version of
openhft-compiler, 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 911...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
tony mancill  (supplier of updated openhft-compiler 
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: Sat, 27 Oct 2018 15:00:55 -0700
Source: openhft-compiler
Binary: libopenhft-compiler-java
Architecture: source
Version: 2.2.4-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: tony mancill 
Description:
 libopenhft-compiler-java - Java Runtime Compiler library
Closes: 911943
Changes:
 openhft-compiler (2.2.4-2) unstable; urgency=medium
 .
   * Team upload
   * Add missing Build-Depends on libeasymock-java (Closes: #911943)
 - Thank you to Helmut Grohne for the bug report
   * Update Vcs- fields for salsa.debian.org
   * Use debhelper 11
   * Bump Standards-Version to 4.2.1
Checksums-Sha1:
 2751788a4bbb0eaaf4f89af0540079768f990d2c 2188 openhft-compiler_2.2.4-2.dsc
 7f7ab96928a04e5596210f74612d099ae08ac305 2716 
openhft-compiler_2.2.4-2.debian.tar.xz
 2b032da2c2a4340b9cb5963364ea2116a9d78977 15387 
openhft-compiler_2.2.4-2_amd64.buildinfo
Checksums-Sha256:
 8bcfb36d471fd4c27049870498f8b2101e2041be6ec0c3a3f68fdaa319068241 2188 
openhft-compiler_2.2.4-2.dsc
 1f74b3188b7952931d4f6c259e6fc8c1ca313532769e569e5d356b135e80c5f7 2716 
openhft-compiler_2.2.4-2.debian.tar.xz
 f75f38d9ec5cdc5ef30fe8256a5d6c0e48a394600b1dcd647890de6b67885f97 15387 
openhft-compiler_2.2.4-2_amd64.buildinfo
Files:
 6c40f0031a1776aebf0f4979c9bd9e8c 2188 java optional 
openhft-compiler_2.2.4-2.dsc
 686325fda738a16e76d66a5c08cb71b7 2716 java optional 
openhft-compiler_2.2.4-2.debian.tar.xz
 3bcd260455bb15501330e86ee16cfe69 15387 java optional 
openhft-compiler_2.2.4-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJIBAEBCgAyFiEE5Qr9Va3SequXFjqLIdIFiZdLPpYFAlvU4J8UHHRtYW5jaWxs
QGRlYmlhbi5vcmcACgkQIdIFiZdLPpbaPRAArCj2/xKTNGcZRTy3f2dRJNtfD2Ze
GlxQUcjsRDIiHWxg4QBVISqD4Ad8MqAmoisS8JPKoFYtyDCoorgHIskcEPuIj29Y
CKiQouAqbWmjFjjd72bxMRX3HTo+aWH+RkIFG8+lwZed3Xd60sYOgQVjKmFAA1yr
25yOAj17Ydqae9JXTL6SA/qOxQ9wJlny2WgF6tR0F4OTyRLruuAZydzWhtauqZsY
HvjkZUteg7bC1b22x0qurp1zdlKRiGWTtagXQ9wBGIeHzmz6Qv7OruKBaS7YSQqR
fYkJlOVLscgOILts00p0rV2jG13tBklwUFHx3M/w7F/MK0BW+cb1hDd6by/AA1rz
Ku2SttbgJl2tbU8L1Z1mqJVFoIrq9uoneG7pqcGWzFZVhfBcFWNCB/Lg8PpxDVN/
fxxUswmzNcoItsGmvNeqWz/nmVSLXJda9bMmz4xBz+nMCfK0bi3NAP/QIqTT+bA6
Jxxytr09B6fyFxv5yFcQ6dV1wMbEYoRZM34xMcJsSUtKJA9xx4yFMm6iU+Xm0nhK
MDzwcfPaobJ4yFCgoqm6RKEsEepaxO+LonJqc8VUA9jiStItkTtk9L/4xYxL0/77
AV/ln8QJ1ZT3OAEs/nUoMRU2+16u64EwSCEHgfOrXyB1Fe0YX4G/s/+ZwQS2w3jh
6y3MhHLz6Vkjb18=
=DDNa
-END PGP SIGNATURE End Message ---

Bug#912077: libbiod FTBFS on i386: Error: cannot implicitly convert expression

[Adrian Bunk]

Source: libbiod
Version: 0.2.1-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=libbiod=i386=0.2.1-1=1539070612=0

...
[77/177] ldc2 -I=biod@sha -I=. -I=.. -I/usr/include/d -enable-color -O -g 
-release -wi -relocation-model=pic   -of='biod@sha/bio2_bgzf.d.o' -c 
../bio2/bgzf.d
FAILED: biod@sha/bio2_bgzf.d.o 
ldc2 -I=biod@sha -I=. -I=.. -I/usr/include/d -enable-color -O -g -release -wi 
-relocation-model=pic   -of='biod@sha/bio2_bgzf.d.o' -c ../bio2/bgzf.d
../bio2/bgzf.d(214): Error: cannot implicitly convert expression 
`tuple(Nullable(0LU, true), compressed_buf, 0LU, crc32)` of type 
`Tuple!(Nullable!ulong, ubyte[], ulong, immutable(uint))` to 
`Tuple!(Nullable!ulong, ubyte[], uint, immutable(uint))`
...

Bug#912076: kodiplatform FTBFS with debhelper 11.4

[Adrian Bunk]

Source: kodiplatform
Version: 17.1.0-1
Severity: serious
Tags: ftbfs

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

...
   dh_auto_install
cd obj-x86_64-linux-gnu && make -j1 install 
DESTDIR=/build/1st/kodiplatform-17.1.0/debian/tmp AM_UPDATE_INFO_DIR=no
make[1]: Entering directory 
'/build/1st/kodiplatform-17.1.0/obj-x86_64-linux-gnu'
/usr/bin/cmake -H/build/1st/kodiplatform-17.1.0 
-B/build/1st/kodiplatform-17.1.0/obj-x86_64-linux-gnu --check-build-system 
CMakeFiles/Makefile.cmake 0
/usr/bin/cmake -E cmake_progress_start 
/build/1st/kodiplatform-17.1.0/obj-x86_64-linux-gnu/CMakeFiles 
/build/1st/kodiplatform-17.1.0/obj-x86_64-linux-gnu/CMakeFiles/progress.marks
make -f CMakeFiles/Makefile2 all
make[2]: Entering directory 
'/build/1st/kodiplatform-17.1.0/obj-x86_64-linux-gnu'
make -f CMakeFiles/kodiplatform.dir/build.make 
CMakeFiles/kodiplatform.dir/depend
make[3]: Entering directory 
'/build/1st/kodiplatform-17.1.0/obj-x86_64-linux-gnu'
cd /build/1st/kodiplatform-17.1.0/obj-x86_64-linux-gnu && /usr/bin/cmake -E 
cmake_depends "Unix Makefiles" /build/1st/kodiplatform-17.1.0 
/build/1st/kodiplatform-17.1.0 
/build/1st/kodiplatform-17.1.0/obj-x86_64-linux-gnu 
/build/1st/kodiplatform-17.1.0/obj-x86_64-linux-gnu 
/build/1st/kodiplatform-17.1.0/obj-x86_64-linux-gnu/CMakeFiles/kodiplatform.dir/DependInfo.cmake
 --color=
make[3]: Leaving directory '/build/1st/kodiplatform-17.1.0/obj-x86_64-linux-gnu'
make -f CMakeFiles/kodiplatform.dir/build.make CMakeFiles/kodiplatform.dir/build
make[3]: Entering directory 
'/build/1st/kodiplatform-17.1.0/obj-x86_64-linux-gnu'
make[3]: Nothing to be done for 'CMakeFiles/kodiplatform.dir/build'.
make[3]: Leaving directory '/build/1st/kodiplatform-17.1.0/obj-x86_64-linux-gnu'
[100%] Built target kodiplatform
make[2]: Leaving directory '/build/1st/kodiplatform-17.1.0/obj-x86_64-linux-gnu'
/usr/bin/cmake -E cmake_progress_start 
/build/1st/kodiplatform-17.1.0/obj-x86_64-linux-gnu/CMakeFiles 0
make -f CMakeFiles/Makefile2 preinstall
make[2]: Entering directory 
'/build/1st/kodiplatform-17.1.0/obj-x86_64-linux-gnu'
make[2]: Nothing to be done for 'preinstall'.
make[2]: Leaving directory '/build/1st/kodiplatform-17.1.0/obj-x86_64-linux-gnu'
Install the project...
/usr/bin/cmake -P cmake_install.cmake
-- Install configuration: "None"
-- Installing: 
/build/1st/kodiplatform-17.1.0/debian/tmp/build/1st/kodiplatform-17.1.0/obj-x86_64-linux-gnu/lib/x86_64-linux-gnu/libkodiplatform.so.16.0.0
-- Installing: 
/build/1st/kodiplatform-17.1.0/debian/tmp/build/1st/kodiplatform-17.1.0/obj-x86_64-linux-gnu/lib/x86_64-linux-gnu/libkodiplatform.so.16
-- Installing: 
/build/1st/kodiplatform-17.1.0/debian/tmp/build/1st/kodiplatform-17.1.0/obj-x86_64-linux-gnu/lib/x86_64-linux-gnu/libkodiplatform.so
-- Installing: 
/build/1st/kodiplatform-17.1.0/debian/tmp/usr/include/kodi/util/XMLUtils.h
-- Installing: 
/build/1st/kodiplatform-17.1.0/debian/tmp/build/1st/kodiplatform-17.1.0/obj-x86_64-linux-gnu/lib/x86_64-linux-gnu/pkgconfig/kodiplatform.pc
-- Installing: 
/build/1st/kodiplatform-17.1.0/debian/tmp/build/1st/kodiplatform-17.1.0/obj-x86_64-linux-gnu/lib/x86_64-linux-gnu/kodiplatform/kodiplatform-config.cmake
make[1]: Leaving directory '/build/1st/kodiplatform-17.1.0/obj-x86_64-linux-gnu'
   dh_install
dh_install: Cannot find (any matches for) "usr/lib/*/*.so" (tried in ., 
debian/tmp)

dh_install: libkodiplatform-dev missing files: usr/lib/*/*.so
dh_install: Cannot find (any matches for) "usr/lib/*/pkgconfig/*.pc" (tried in 
., debian/tmp)

dh_install: libkodiplatform-dev missing files: usr/lib/*/pkgconfig/*.pc
dh_install: Cannot find (any matches for) "usr/lib/*/kodiplatform/*" (tried in 
., debian/tmp)

dh_install: libkodiplatform-dev missing files: usr/lib/*/kodiplatform/*
dh_install: Cannot find (any matches for) "usr/lib/*/*.so.*" (tried in ., 
debian/tmp)

dh_install: libkodiplatform16 missing files: usr/lib/*/*.so.*
dh_install: missing files, aborting
make: *** [debian/rules:16: binary] Error 25

Bug#910128: bash-completion: diff for NMU version 1:2.1-4.4

[Emmanouil Kampitakis]

Control: tags 910128 + pending
Control: user debian-rele...@lists.debian.org
Control: usertags -1 + bsp-2018-10-de-karlsruhe

Dear maintainer,

I've prepared an NMU for bash-completion (versioned as 1:2.1-4.4) and
uploaded it to DELAYED/5. Please feel free to tell me if I
should delay it longer.

Regards,
 Emmanouil

diff -Nru bash-completion-2.1/debian/changelog
bash-completion-2.1/debian/changelog ---
bash-completion-2.1/debian/changelog2016-04-12
14:06:38.0 + +++
bash-completion-2.1/debian/changelog2018-10-27
21:53:12.0 + @@ -1,3 +1,10 @@ +bash-completion (1:2.1-4.4)
unstable; urgency=medium +
+  * Non-maintainer upload.
+  * Use install-data-hook, not install-data-local (Closes: #910128) 
+
+ -- Emmanouil Kampitakis   Sat, 27 Oct 2018
21:53:12 + +
 bash-completion (1:2.1-4.3) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru
bash-completion-2.1/debian/patches/99-use-install-data-hook.patch
bash-completion-2.1/debian/patches/99-use-install-data-hook.patch ---
bash-completion-2.1/debian/patches/99-use-install-data-hook.patch
1970-01-01 00:00:00.0 + +++
bash-completion-2.1/debian/patches/99-use-install-data-hook.patch
2018-10-27 21:48:09.0 + @@ -0,0 +1,28 @@ +From:
=?UTF-8?q?Ville=20Skytt=C3=A4?=  +Date: Fri, 25
May 2018 17:38:59 +0200 +Subject: [PATCH] completions/Makefile.am: Use
install-data-hook, not
+ install-data-local
+Bug-Debian: https://bugs.debian.org/910128
+Forwarded: https://github.com/scop/bash-completion/issues/212
+Origin:
https://github.com/scop/bash-completion/commit/ee6b37ad7ff5b309cbb9b886a871252abd9398fa
+ +-hook is run after the main rule, while -local might end up before.
+https://www.gnu.org/software/automake/manual/html_node/Extending.html#index-hook-targets
+
+Closes #212
+---
+ completions/Makefile.am | 4 ++--
+ 1 file changed, 2 insertions(+), 2 deletions(-)
+
+Index: bash-completion-2.1/completions/Makefile.am
+===
+--- bash-completion-2.1.orig/completions/Makefile.am
 bash-completion-2.1/completions/Makefile.am
+@@ -869,5 +869,5 @@ symlinks: $(targetdir) $(DATA)
+ all-local: targetdir = .
+ all-local: symlinks
+ 
+-install-data-local: targetdir = $(DESTDIR)$(bashcompdir)
+-install-data-local: symlinks
++install-data-hook: targetdir = $(DESTDIR)$(bashcompdir)
++install-data-hook: symlinks
diff -Nru bash-completion-2.1/debian/patches/series
bash-completion-2.1/debian/patches/series ---
bash-completion-2.1/debian/patches/series   2014-03-22
20:57:44.0 + +++
bash-completion-2.1/debian/patches/series   2018-10-27
20:38:29.0 + @@ -11,3 +11,4 @@ 10-ifconfig_locale.patch
11-dont_return_from_sourced_script.patch 12-look_for_pod.patch
+99-use-install-data-hook.patch


pgpdavSQB0HiS.pgp
Description: OpenPGP digital signature

Processed (with 2 errors): bash-completion: diff for NMU version 1:2.1-4.4

[Debian Bug Tracking System]

Processing control commands:

> tags 910128 + pending
Bug #910128 [src:bash-completion] bash-completion parallel FTBFS
Added tag(s) pending.
> user debian-rele...@lists.debian.org
Unknown command or malformed arguments to command.

> usertags -1 + bsp-2018-10-de-karlsruhe
Unknown command or malformed arguments to command.


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

Bug#912075: ayatana-indicator-power FTBFS with googletest 1.8.1-1

[Adrian Bunk]

Source: ayatana-indicator-power
Version: 2.0.93-3
Severity: serious
Tags: ftbfs

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/ayatana-indicator-power.html

...
[ 99%] Linking CXX executable test-notify
cd /build/1st/ayatana-indicator-power-2.0.93/obj-x86_64-linux-gnu/tests && 
/usr/bin/cmake -E cmake_link_script CMakeFiles/test-notify.dir/link.txt 
--verbose=1
/usr/bin/c++  -g -O2 
-ffile-prefix-map=/build/1st/ayatana-indicator-power-2.0.93=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -std=c++11  -Wall -Wextra -Wpedantic -Wformat=2 
-Wno-missing-field-initializers -Wno-weak-vtables -Wno-global-constructors  
-Wl,-z,relro -Wl,-z,now -rdynamic CMakeFiles/test-notify.dir/test-notify.cc.o  
-o test-notify ../src/libayatanaindicatorpowerservice.a -ldbustest -lglib-2.0 
-lgio-2.0 -lnotify -lgdk_pixbuf-2.0 -lgio-2.0 -lgobject-2.0 -lglib-2.0 
-lgio-2.0 -lnotify -lgdk_pixbuf-2.0 -lgobject-2.0 gmock/gtest/libgtest.a 
-lpthread gmock/libgmock.a gmock/libgmock_main.a 
/usr/bin/ld: gmock/libgmock_main.a(gmock_main.cc.o): in function `main':
/usr/src/googletest/googlemock/src/gmock_main.cc:52: undefined reference to 
`testing::InitGoogleMock(int*, char**)'
collect2: error: ld returned 1 exit status
make[3]: *** [tests/CMakeFiles/test-notify.dir/build.make:91: 
tests/test-notify] Error 1

Processed: tagging 912072, tagging 846449

[Debian Bug Tracking System]

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

> tags 912072 + pending
Bug #912072 [src:srg] srg: FTBFS with GCC 8
Added tag(s) pending.
> tags 846449 + pending
Bug #846449 [src:srg] srg: add libfl-dev to Build-Depends
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#912074: libboost-stacktrace1.67-dev: header boost/stacktrace.hpp not included in libboost-stacktrace1.67-dev

[Martin Quinson]

Package: libboost-stacktrace1.67-dev
Version: 1.67.0-7
Severity: grave
Justification: renders package unusable

Dear maintainers,

I'm really pleased that this new stacktrace library made its way into boost and
into debian, but it seems that something went wrong when packaging it because
the header files seem to be missing.

Here is the content of my version:
$ dpkg -L libboost-stacktrace1.67-dev
/.
/usr
/usr/lib
/usr/lib/x86_64-linux-gnu
/usr/lib/x86_64-linux-gnu/libboost_stacktrace_addr2line.a
/usr/lib/x86_64-linux-gnu/libboost_stacktrace_backtrace.a
/usr/lib/x86_64-linux-gnu/libboost_stacktrace_basic.a
/usr/lib/x86_64-linux-gnu/libboost_stacktrace_noop.a
/usr/share
/usr/share/doc
/usr/share/doc/libboost-stacktrace1.67-dev
/usr/share/doc/libboost-stacktrace1.67-dev/changelog.Debian.gz
/usr/share/doc/libboost-stacktrace1.67-dev/copyright
/usr/lib/x86_64-linux-gnu/libboost_stacktrace_addr2line.so
/usr/lib/x86_64-linux-gnu/libboost_stacktrace_backtrace.so
/usr/lib/x86_64-linux-gnu/libboost_stacktrace_basic.so
/usr/lib/x86_64-linux-gnu/libboost_stacktrace_noop.so

As you can see, there is no headerfile while upstream seem to distribute some:
https://github.com/boostorg/stacktrace

Or maybe I missed something obvious?

Many thanks for your work,
Mt



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

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

Versions of packages libboost-stacktrace1.67-dev depends on:
ii  libboost-stacktrace1.67.0  1.67.0-7
ii  libboost1.67-dev   1.67.0-7

libboost-stacktrace1.67-dev recommends no packages.

libboost-stacktrace1.67-dev suggests no packages.

-- no debconf information

-- 
The great thing about TCP jokes is that you always get them.


signature.asc
Description: PGP signature

Bug#912073: No initramfs generated if new kernel package installed by upgrade

[Ben Hutchings]

Package: pkgsel
Version: 0.60
Severity: serious

While testing a fix for #908711, I found that pkgsel diverts
update-initramfs during the upgrade and installation process
and runs it once at the end.

By default, "update-initramfs -u" updates the new initramfs for the
newest kernel version that update-initramfs was previously run for.
If a new kernel package was installed due to an ABI bump, no new
initramfs will be generated.  This causes the system to fail to
boot.

Ben.

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

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

Bug#912072: srg: FTBFS with GCC 8

[Reiner Herrmann]

Source: srg
Version: 1.3.6-2
Severity: serious
Tags: ftbfs
User: debian-rele...@lists.debian.org
Usertags: bsp-2018-10-de-karlsruhe

Dear maintainer,

srg fails to build with GCC 8:

g++ -DHAVE_CONFIG_H -I. -I..  -I../include -I../libconfig 
-DDATADIR=\"/usr/share\" -DSYSCONFDIR=\"/etc\" -Wdate-time 
-D_FORTIFY_SOURCE=2  -g -O2 -fdebug-prefix-map=/tmp/debian/srg/tmp/srg-1.3.6=. 
-fstack-protector-strong -Wformat -Werror=format-security -MT srg-output.o -MD 
-MP -MF .deps/srg-output.Tpo -c -o srg-output.o `test -f 'output.cc' || echo 
'./'`output.cc
output.cc: In function ‘void init_file(const char*)’:
output.cc:101:26: error: invalid conversion from ‘char’ to ‘char*’ 
[-fpermissive]
   char *buf[4096] = {'\0'};
  ^
output.cc: In function ‘void html_header(FILE*, const char*)’:
output.cc:121:13: warning: ISO C++ forbids converting a string constant to 
‘char*’ [-Wwrite-strings]
  char *base="";
 ^~
output.cc: In function ‘void html_footer(FILE*, const char*)’:
output.cc:176:13: warning: ISO C++ forbids converting a string constant to 
‘char*’ [-Wwrite-strings]
  char *base="";
 ^~

A complete build log is also available on 
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/srg.html

Kind regards,
  Reiner


signature.asc
Description: PGP signature

Bug#892434: marked as done (scorched3d: Please use 'pkg-config' to find FreeType 2)

[Debian Bug Tracking System]

Your message dated Sat, 27 Oct 2018 21:26:44 +
with message-id 
and subject line Bug#892434: fixed in scorched3d 44+dfsg-3
has caused the Debian Bug report #892434,
regarding scorched3d: Please use 'pkg-config' to find FreeType 2
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.)


-- 
892434: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892434
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: scorched3d
Severity: important

Dear Maintainer,

The next release of libfreetype6-dev will *not* ship
`freetype-config', as the script has now been deprecated in favour of
`pkg-config'.

This is an upstream change:

"Use of the `freetype-config' script to get compilation and

linking options is deprecated since it doesn't support

cross-compiling, among other deficiencies. Instead, you should

use the `pkg-config' interface." [1]

Please use `pkg-config' to detect the FreeType 2 headers and
libraries in scorched3d.

If this bug is not resolved prior to the release of FreeType 2.9.1,
your package may FTBFS.

Thank you

[1]
http://git.savannah.gnu.org/cgit/freetype/freetype2.git/commit/?id=b0
a93839b52818abbfe9b4c8755b4aa0f5232063 
--- End Message ---
--- Begin Message ---
Source: scorched3d
Source-Version: 44+dfsg-3

We believe that the bug you reported is fixed in the latest version of
scorched3d, 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 892...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Markus Koschany  (supplier of updated scorched3d 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: Sat, 27 Oct 2018 21:54:57 +0200
Source: scorched3d
Binary: scorched3d scorched3d-data
Architecture: source
Version: 44+dfsg-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Games Team 
Changed-By: Markus Koschany 
Description:
 scorched3d - 3D artillery game similar to Scorched Earth
 scorched3d-data - data files for Scorched3D game
Closes: 892434
Changes:
 scorched3d (44+dfsg-3) unstable; urgency=medium
 .
   * Team upload.
   * Add freetype-config.patch and detect libraries with pkg-config instead of
 freetype-config.
 Thanks to Adrian Bunk for the patch. (Closes: #892434)
   * Declare compliance with Debian Policy 4.2.1.
Checksums-Sha1:
 597ffded3789cda60b4d6ac3c1027f719d87959d 2511 scorched3d_44+dfsg-3.dsc
 aabbb551e3137578fadbe3e9a58443dc3d35431a 121364 
scorched3d_44+dfsg-3.debian.tar.xz
 f11a60629f2b6ad623b583230e687df14229cd4c 12593 
scorched3d_44+dfsg-3_amd64.buildinfo
Checksums-Sha256:
 a381c6cf6319946c4d11a6d25cdb1634406decd0b7c12c8260eb463ac9a65280 2511 
scorched3d_44+dfsg-3.dsc
 6253be3986dfd33b60d19818ded392d87b6114654e9f190f0c48d9f3c9c7c581 121364 
scorched3d_44+dfsg-3.debian.tar.xz
 4bafcbf4406181239a9c7f5b68178b3cd1ab91325da84af9de1eb7be40982561 12593 
scorched3d_44+dfsg-3_amd64.buildinfo
Files:
 21e391357160a3a11d7a47225d75089a 2511 games optional scorched3d_44+dfsg-3.dsc
 b1ba47de4e69179e60ef7493572f40bb 121364 games optional 
scorched3d_44+dfsg-3.debian.tar.xz
 11f5eb570a52f80ffbcb3f72b87f2f5d 12593 games optional 
scorched3d_44+dfsg-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQKjBAEBCgCNFiEErPPQiO8y7e9qGoNf2a0UuVE7UeQFAlvUxkNfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEFD
RjNEMDg4RUYzMkVERUY2QTFBODM1RkQ5QUQxNEI5NTEzQjUxRTQPHGFwb0BkZWJp
YW4ub3JnAAoJENmtFLlRO1Hk/dUQAI0NXVz+r5Vzx38nR6zZ0bn1GQTuXdcHFDC9
8HdXtD5ida7OiImvy2CkNgof2Cuq7Ue7aD3zhvxMLZNNKeWi1Gt0R+2WQtIett7O
O0ARBympTocboLOAZOvc9mL4YHJD/vpZAPFv2Z+wOH6YH4bg/9o+HwJTPZlpZ3FI
fRkSqVyLbCXEezU8xKTV6W9Ox0/dXmi299XyHVNiigwLsk90zlhrPbxuXBKKsLux
M7aIf+Uy+RWS60CziFkj8KsfibFRLXu6a6FUlxvjBxp2VoJI8TgS1TZV0DLlU5ei
SwLH15vn99nhN8Gd94bF4axQpRVZABJ0fJps8rXFsMmq24INcmdMXltOKeyr7AQR
YKbLOIqTU5iZRzLfWN4s1RW3sShusVLxBdDdzicxIZuSDCwYzpwdEFvyWteGAPVF
ynAp8t02n+lbYK2q7IVYq4wEHIv3DLYwM+T6gEKm1G8idtq+uHS/1sncqsHTk4Lx
njlfT7NjkMQEeJQpFHNfAne7ivUN+L1hLhQ6uRLnvL5xc5eA6VSIqwl0G+HR+4kX
VZIbB4ws8sMyBz4QRZ49hwMQSsyVpB9BzP2PJi0JCuwp7DSfDeJUEk/eNvMtiEq9
sEVTwG+U6nOb/PScdHp8XVCP6BST2cIXemusfNYOlsmRo+yT6hoyE4yaLU7kGISw
qVsrQ2r7
=7xE4
-END PGP SIGNATURE End Message ---

Processed: bug 824229 is forwarded to https://github.com/schani/metapixel/issues/10

[Debian Bug Tracking System]

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

> forwarded 824229 https://github.com/schani/metapixel/issues/10
Bug #824229 [metapixel] metapixel-prepare fails - metapixel: rwpng.c:199: 
open_png_file_writing: Assertion `0' failed.
Set Bug forwarded-to-address to 'https://github.com/schani/metapixel/issues/10'.
> thanks
Stopping processing here.

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

Bug#912069: flask-wtf FTBFS: FAIL: test_i18n_enabled (tests.test_i18n.TestI18NCase)

[Adrian Bunk]

Source: flask-wtf
Version: 0.14.2-2
Severity: serious
Tags: ftbfs

Some recent change in unstable makes flask-wtf FTBFS:

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

...

==
FAIL: test_i18n_enabled (tests.test_i18n.TestI18NCase)
--
Traceback (most recent call last):
  File 
"/build/1st/flask-wtf-0.14.2/.pybuild/cpython2_2.7_flaskext.wtf/build/tests/test_i18n.py",
 line 32, in test_i18n_enabled
assert '\u8be5\u5b57\u6bb5\u662f' in to_unicode(response.data)
AssertionError

--
Ran 52 tests in 0.661s

FAILED (failures=1)
E: pybuild pybuild:338: test: plugin distutils failed with: exit code=1: cd 
/build/1st/flask-wtf-0.14.2/.pybuild/cpython2_2.7_flaskext.wtf/build; python2.7 
-m nose -v tests
dh_auto_test: pybuild --test --test-nose -i python{version} -p 2.7 returned 
exit code 13
make: *** [debian/rules:11: build] Error 25

Bug#892330: marked as done (cube2font: Please use 'pkg-config' to find FreeType 2)

[Debian Bug Tracking System]

Your message dated Sat, 27 Oct 2018 21:15:29 +
with message-id 
and subject line Bug#892330: fixed in cube2font 1.5.1-1
has caused the Debian Bug report #892330,
regarding cube2font: Please use 'pkg-config' to find FreeType 2
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.)


-- 
892330: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892330
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cube2font
Severity: important

Dear Maintainer,

The next release of libfreetype6-dev will *not* ship
`freetype-config', as the script has now been deprecated in favour of
`pkg-config'.

This is an upstream change:

"Use of the `freetype-config' script to get compilation and

linking options is deprecated since it doesn't support

cross-compiling, among other deficiencies. Instead, you should

use the `pkg-config' interface." [1]

Please use `pkg-config' to detect the FreeType 2 headers and
libraries in cube2font.

If this bug is not resolved prior to the release of FreeType 2.9.1,
your package may FTBFS.

Thank you

[1]
http://git.savannah.gnu.org/cgit/freetype/freetype2.git/commit/?id=b0
a93839b52818abbfe9b4c8755b4aa0f5232063 
--- End Message ---
--- Begin Message ---
Source: cube2font
Source-Version: 1.5.1-1

We believe that the bug you reported is fixed in the latest version of
cube2font, 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 892...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Reiner Herrmann  (supplier of updated cube2font 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: Fri, 19 Oct 2018 19:59:20 +0200
Source: cube2font
Binary: cube2font
Architecture: source
Version: 1.5.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Games Team 
Changed-By: Reiner Herrmann 
Description:
 cube2font  - utility program for creating font bitmaps for Cube Engine games
Closes: 892330
Changes:
 cube2font (1.5.1-1) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Martin Erik Werner ]
   * New minor upstream release
 - Fixes 0-border behaviour
 - Drop makefile-install.patch
   * Canonicalize VCS-urls
   * Imported Upstream version 1.5.1
 .
   [ Reiner Herrmann ]
   * Point Vcs-* URLs to salsa.
   * Use pkg-config for finding libraries. (Closes: #892330)
   * Replace -dbg package with -dbgsym.
   * Update debhelper to compat level 11.
   * Update URLs in d/copyright.
   * Use https in Homepage field.
   * Bump Standards-Version to 4.2.1.
Checksums-Sha1:
 b594f3bca4b20a1e0cb0ff9e6a29400d7505b8ed 2105 cube2font_1.5.1-1.dsc
 65d05ec9abbdcae744bedbfd1e95882d049d28f4 16512 cube2font_1.5.1.orig.tar.xz
 6e6ada994696348e83e7b87e4cd6070496e1b998 3808 cube2font_1.5.1-1.debian.tar.xz
 8d1872632fb526f70530c14bdbfbfbcba17f5108 6030 cube2font_1.5.1-1_amd64.buildinfo
Checksums-Sha256:
 aaa2a6279a8b59b1c331d592c373623b572ad146c9e4a3c89891f74e0d4dc1e4 2105 
cube2font_1.5.1-1.dsc
 55354662f158dbf02d4dee33b1109af43254aa51d78af3ad8dd9055081079550 16512 
cube2font_1.5.1.orig.tar.xz
 dab2998cde32e29b9faa8e2d68b6e992b563dd22d0b6e80611c68f3c06e53e1e 3808 
cube2font_1.5.1-1.debian.tar.xz
 01c5065ac94e48e9402be350857a0ece72433bd4962b953663187e2e19d4a6d3 6030 
cube2font_1.5.1-1_amd64.buildinfo
Files:
 f975bf1c5fae78a6f6e67417dc84065f 2105 graphics optional cube2font_1.5.1-1.dsc
 86c6427b8e2357553bb7b5e444973266 16512 graphics optional 
cube2font_1.5.1.orig.tar.xz
 516c9f990863ab454d929570ab488a57 3808 graphics optional 
cube2font_1.5.1-1.debian.tar.xz
 41ec05fafd2c932138dc5d7ac976f212 6030 graphics optional 
cube2font_1.5.1-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQKjBAEBCgCNFiEErPPQiO8y7e9qGoNf2a0UuVE7UeQFAlvUzTNfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEFD
RjNEMDg4RUYzMkVERUY2QTFBODM1RkQ5QUQxNEI5NTEzQjUxRTQPHGFwb0BkZWJp
YW4ub3JnAAoJENmtFLlRO1HkRZsP/2b7knzQX3yDvX1SUGoTL+WpI0J3t4U6MMXC
gFqV2gumtP6KDw9TOH5k5hFUYTiTYZV6d7asaq+okhfNBj75IpUj6hjSgQhHSIn1
fdNdqzqyQm9lH7kftMTNCoSEagq3fV5RideQAnNNX93Lt2sunTp/J3GiaeO/SNuy
bP0D7qwsLaabhaotdBus45EMG9JF+2viW8fok42y0OsZBK3NCcuBXOww+rdb5Opz
geFYtCfbQcL3e50+Gznf3itQ/KEkOdGZAJ5evkqGBJGP/1/AZKNvPJXOtar1rhjl

Bug#867277: marked as done (systraq: dpkg hook fails after package removal)

[Debian Bug Tracking System]

Your message dated Sat, 27 Oct 2018 21:11:35 +
with message-id 
and subject line Bug#867277: fixed in systraq 20160803-1+deb9u1
has caused the Debian Bug report #867277,
regarding systraq: dpkg hook fails after package removal
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.)


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

Hi,

during a test with piuparts I noticed your package fails to remove.

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

  Removing systraq (20160803-1) ...
[...]
  Removing make (4.1-9.1) ...
[...]
  Processing triggers for libc-bin (2.24-12) ...
  E: Problem executing scripts DPkg::Post-Invoke 'test -f /etc/systraq/Makefile 
&& command -v make >/dev/null && su -s /bin/sh -c 'make -s -C /etc/systraq' 
debian-systraq'
  E: Sub-process returned an error code


cheers,

Andreas


systraq_20160803-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: systraq
Source-Version: 20160803-1+deb9u1

We believe that the bug you reported is fixed in the latest version of
systraq, 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 867...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Andreas Beckmann  (supplier of updated systraq 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: Sun, 21 Oct 2018 15:00:06 +0200
Source: systraq
Binary: systraq
Architecture: source
Version: 20160803-1+deb9u1
Distribution: stretch
Urgency: medium
Maintainer: Joost van Baal-Ilić 
Changed-By: Andreas Beckmann 
Description:
 systraq- monitor your system and warn when system files change
Closes: 867277
Changes:
 systraq (20160803-1+deb9u1) stretch; urgency=medium
 .
   * Non-maintainer upload.
   * debian/20systraq: Invert logic in order to exit successfully in case
  /e/s/Makefile is missing.  (Closes: #867277)
Checksums-Sha1:
 8b103041021e1f3518e359d337afb675feea6d61 1914 systraq_20160803-1+deb9u1.dsc
 e24c23c4d84e2193b1fefa66af1a9cc2fd4f42f9 232488 
systraq_20160803-1+deb9u1.debian.tar.xz
 20b596adf5e4d373e1f577e704d2e68823369cb3 5586 
systraq_20160803-1+deb9u1_source.buildinfo
Checksums-Sha256:
 621be3f34c3a2cbe0e912e2135e5df3723f048aa6ff0afb5e9fce1f567cf3de5 1914 
systraq_20160803-1+deb9u1.dsc
 dbc89ec4521e7ac2fcd4e03e5412f90bc1c8e016b9989ae5285549df56222397 232488 
systraq_20160803-1+deb9u1.debian.tar.xz
 e9eeb4fc69e0966adda3d0a66ae8293794c3d784bd489e216faf10e604cf2558 5586 
systraq_20160803-1+deb9u1_source.buildinfo
Files:
 7349909516b9ffb0b6db3f815fb61657 1914 admin optional 
systraq_20160803-1+deb9u1.dsc
 5a37e2b4dc424f2814cb31ba17bfc234 232488 admin optional 
systraq_20160803-1+deb9u1.debian.tar.xz
 169debb22f84c9d6b7fdc9fe49bca4a9 5586 admin optional 
systraq_20160803-1+deb9u1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCAAuFiEE6/MKMKjZxjvaRMaUX7M/k1np7QgFAlvMfcIQHGFuYmVAZGVi
aWFuLm9yZwAKCRBfsz+TWentCLc+D/95djDxB5snwXcX+eIle+MVtr6JxxL9lfXV
YrnbQLFSRDcnBYwUM4fnLhW24enIAEPIZjjPCD4kXLPz3hw3ESc9t/6GRB39EWRY
3Jf3pMVu1syMVK+u97DdnwpuWtfopXl1CfD3AGCc3wQbw1DeNnEEhpZ7ZS5hLxmy
zUqi/a/UGivTtojnVUl0GWCK0TqfECVK4MS6/r/Xz+7TLAWid3hAzeyMil2ewWyG
bg4xQ2sIHwUnjy1Ii8SD6IlVe6/AFABIt519wwGp47CJUR9zis5cxU6DQJx1xf9a
u5gNGwuCOwNIdTWI9+7ITONk8vs20h/jm5Lg605jXmpO73IiiWhlRmuq9gk8ELcV
JKjNT/3lgYcZ6h3qf5VkDji1wQw7h+Osxw+W8lcQcP+kxCDMdW1+X3jowI+bn8Nu
ul0r+QGNRSSyH4W72QHm/xheQeKNKwYSYlig1qSvYIOX5SN0l4JE4CoJl+gPkbO/
fCDZkYBeSRvB9zKoJqIwuPdAfBkKBjXdy+9j7lSPASAFmVJAu1MWW3KsP3jJt0EW
ggXLkFjgag6JfWAOGxfX3G59u4qSyVOX+lODYnVAD2jgavsUeG4aRp/xTIGe9k0+
whwZrInWBfsiIk+oPXPjT3prJ6eEsqjDAh6S+KlcEPNFeWPUCml9WAXMHjMi7HZM
sCmcyPcCAA==
=UUqq
-END PGP SIGNATURE End Message ---

Bug#885542: marked as done (lxcfs: virtualizing the btime field of /proc/stat screws up process start times)

[Debian Bug Tracking System]

Your message dated Sat, 27 Oct 2018 21:11:32 +
with message-id 
and subject line Bug#885542: fixed in lxcfs 2.0.7-1+deb9u1
has caused the Debian Bug report #885542,
regarding lxcfs: virtualizing the btime field of /proc/stat screws up process 
start times
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.)


-- 
885542: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885542
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: lxcfs
Version: 2.0.7-1
Severity: normal
Tags: upstream

As reported here: https://github.com/lxc/lxd/issues/3517
which points to https://github.com/lxc/lxcfs/issues/164 (where is stated
that virtualizing the btime field has been reverted due to
https://github.com/lxc/lxcfs/issues/189), I'm experiencing wrong stimes 
for processes.

As I find having accurate start times of processes far more important
than having an accurate uptime counter for my containers, as do other
people as well apparently, I would like to see this reverted until a
better solution for the btime field /uptime is found.

# lxc-attach -n bla
bla# ls -l /run/apache2/apache2.pid 
-rw-r--r-- 1 root root 5 Dec 27 14:15 /run/apache2/apache2.pid
bla# ps -fp `cat /run/apache2/apache2.pid`
UIDPID  PPID  C STIME TTY  TIME CMD
root  5691 1  0 17:29 ?00:00:01 /usr/sbin/apache2 -k start
bla# uptime
 21:35:21 up 3 days,  2:57,  0 users,  load average: 0.15, 0.13, 0.17
bla# exit 
host# uptime
  21:35:33 up 3 days,  7:00,  5 users,  load average: 0.13, 0.13, 0.16

You can see the difference in time between starting the host and the
container is the difference between the time shown by ps and the actual
start time of the process.


Thanks,
Paul

-- System Information:
(reported from a different system as the LXC system has no email as yet)
--- End Message ---
--- Begin Message ---
Source: lxcfs
Source-Version: 2.0.7-1+deb9u1

We believe that the bug you reported is fixed in the latest version of
lxcfs, 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 885...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Michael Banck  (supplier of updated lxcfs 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, 09 Oct 2018 10:10:16 +0200
Source: lxcfs
Binary: lxcfs libpam-cgfs
Architecture: source amd64
Version: 2.0.7-1+deb9u1
Distribution: stable
Urgency: medium
Maintainer: pkg-lxc 
Changed-By: Michael Banck 
Description:
 libpam-cgfs - PAM module for managing cgroups for LXC
 lxcfs  - FUSE based filesystem for LXC
Closes: 885542
Changes:
 lxcfs (2.0.7-1+deb9u1) stretch; urgency=medium
 .
   * Non-maintainer upload.
   * debian/patches/revert-the-virtualization-of-btime-field.patch: New patch,
 reverts the uptime virtualiziation, fixing process start times, adopted
 from upstream commit 72dd97f7 (Closes: #885542).
Checksums-Sha1:
 8b63b59d9081a756bbc8a6ac968295cd015a521d 2171 lxcfs_2.0.7-1+deb9u1.dsc
 c6821c9d4071f50927107a6030457d6b6aa22621 63684 
lxcfs_2.0.7-1+deb9u1.debian.tar.xz
 d7447ac7e0ebee8154567aaad1d06eea8459690a 32614 
libpam-cgfs-dbgsym_2.0.7-1+deb9u1_amd64.deb
 b0f991e4483e39fe89200fe77cabab16a20bb926 18332 
libpam-cgfs_2.0.7-1+deb9u1_amd64.deb
 84c47bd3d34d6a0399cb78032edd3243f1ab97fd 92984 
lxcfs-dbgsym_2.0.7-1+deb9u1_amd64.deb
 a90d17c7fd40882d164c8f18918f0fe07cd086db 6993 
lxcfs_2.0.7-1+deb9u1_amd64.buildinfo
 be0bcd753fb417258cbd10cfc8e6ce553bb96c1a 42020 lxcfs_2.0.7-1+deb9u1_amd64.deb
Checksums-Sha256:
 680d5d365d077ba134c16e26ac19eeb1f322dbcbcec058c3061582d461926fbf 2171 
lxcfs_2.0.7-1+deb9u1.dsc
 cfb8205fbdda70925605ad0b807cbbcb915116561d3078d36b0479662141eccf 63684 
lxcfs_2.0.7-1+deb9u1.debian.tar.xz
 d4ff22592b2aa041d546563887cf11814e389e30e22082188f376820f127e369 32614 
libpam-cgfs-dbgsym_2.0.7-1+deb9u1_amd64.deb
 76e265bfb9a361db019c2fc1dc2ad6cf2b58cc62528f160c1107b77a6377af00 18332 
libpam-cgfs_2.0.7-1+deb9u1_amd64.deb
 400680ed6a72ab7d6ac68c56dc402f9365209696c5185d8b52f4925f716dd047 92984 
lxcfs-dbgsym_2.0.7-1+deb9u1_amd64.deb
 e84eb99253b3ed7ceb1f82178cebce74f60d7631ba897909dbb4b3b6a7a0261e 6993 
lxcfs_2.0.7-1+deb9u1_amd64.buildinfo
 

Bug#906316: marked as done (spice-gtk: CVE-2018-10873: Missing check in demarshal.py:write_validate_array_item() allows for buffer overflow and denial of service)

[Debian Bug Tracking System]

Your message dated Sat, 27 Oct 2018 21:11:34 +
with message-id 
and subject line Bug#906316: fixed in spice-gtk 0.33-3.3+deb9u1
has caused the Debian Bug report #906316,
regarding spice-gtk: CVE-2018-10873: Missing check in 
demarshal.py:write_validate_array_item() allows for buffer overflow and denial 
of service
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.)


-- 
906316: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906316
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: spice
Version: 0.14.0-1
Severity: grave
Tags: patch security upstream
Control: clone -1 -2
Control: reassign -2 src:spice-gtk 0.34-1.1
Control: retitle -2 spice-gtk: CVE-2018-10873: Missing check in 
demarshal.py:write_validate_array_item() allows for buffer overflow and denial 
of service

Hi,

The following vulnerability was published for spice.

CVE-2018-10873[0]:
|Missing check in demarshal.py:write_validate_array_item() allows for
|buffer overflow and 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-2018-10873
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-10873
[1] http://www.openwall.com/lists/oss-security/2018/08/17/1
[2] https://bugzilla.redhat.com/show_bug.cgi?id=1596008
[3] 
https://gitlab.freedesktop.org/spice/spice-common/commit/bb15d4815ab586b4c4a20f4a565970a44824c42c

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: spice-gtk
Source-Version: 0.33-3.3+deb9u1

We believe that the bug you reported is fixed in the latest version of
spice-gtk, 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 906...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Salvatore Bonaccorso  (supplier of updated spice-gtk 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: Fri, 26 Oct 2018 17:52:24 +0200
Source: spice-gtk
Binary: spice-client-gtk spice-client-glib-usb-acl-helper 
libspice-client-glib-2.0-8 gir1.2-spice-client-glib-2.0 
libspice-client-glib-2.0-dev libspice-client-gtk-3.0-5 
gir1.2-spice-client-gtk-3.0 libspice-client-gtk-3.0-dev
Architecture: source
Version: 0.33-3.3+deb9u1
Distribution: stretch
Urgency: medium
Maintainer: Liang Guo 
Changed-By: Salvatore Bonaccorso 
Closes: 906316
Description: 
 gir1.2-spice-client-glib-2.0 - GObject for communicating with Spice servers 
(GObject-Introspecti
 gir1.2-spice-client-gtk-3.0 - GTK3 widget for SPICE clients 
(GObject-Introspection)
 libspice-client-glib-2.0-8 - GObject for communicating with Spice servers 
(runtime library)
 libspice-client-glib-2.0-dev - GObject for communicating with Spice servers 
(development files)
 libspice-client-gtk-3.0-5 - GTK3 widget for SPICE clients (runtime library)
 libspice-client-gtk-3.0-dev - GTK3 widget for SPICE clients (development files)
 spice-client-glib-usb-acl-helper - Helper tool to validate usb ACLs
 spice-client-gtk - Simple clients for interacting with SPICE servers
Changes:
 spice-gtk (0.33-3.3+deb9u1) stretch; urgency=medium
 .
   * Non-maintainer upload.
   * Fix flexible array buffer overflow (CVE-2018-10873) (Closes: #906316)
Checksums-Sha1: 
 77cbf2f4916178f55880f97ccb407cc463f2c379 3504 spice-gtk_0.33-3.3+deb9u1.dsc
 df88adc61835558ef4018b3b4e8ec5c31cf04686 16956 
spice-gtk_0.33-3.3+deb9u1.debian.tar.xz
Checksums-Sha256: 
 b5ce27e4dc37b8b4e799535bbee2c690f939373dbc1d13e3ac245c6097d28894 3504 
spice-gtk_0.33-3.3+deb9u1.dsc
 bc3d6feeb6c127a700049eeb43094bf6a5f2ac6511bd85a5f71782a91c77d7aa 16956 
spice-gtk_0.33-3.3+deb9u1.debian.tar.xz
Files: 
 9b17a68c227dfff234aff3cb3b626f14 3504 misc optional 
spice-gtk_0.33-3.3+deb9u1.dsc
 eda31619287cbd8edcf168cfe1128d1b 16956 misc optional 
spice-gtk_0.33-3.3+deb9u1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQKmBAEBCgCQFiEERkRAmAjBceBVMd3uBUy48xNDz0QFAlvTPCRfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDQ2
NDQ0MDk4MDhDMTcxRTA1NTMxRERFRTA1NENCOEYzMTM0M0NGNDQSHGNhcm5pbEBk

Bug#911421: marked as done (linux: FTBFS on armel/armhf: ABI change for return_address)

[Debian Bug Tracking System]

Your message dated Sat, 27 Oct 2018 21:11:30 +
with message-id 
and subject line Bug#911421: fixed in linux 4.9.130-2
has caused the Debian Bug report #911421,
regarding linux: FTBFS on armel/armhf: ABI change for return_address
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.)


-- 
911421: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911421
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: linux
Version: 4.9.130-1
Severity: serious
Justification: FTBFS
Tags: patch

Hi,

The latest linux upload to stretch FTBFS on both armel and armhf due to
symbol changes. The only offending (non-ignored) change is the following:
> ABI has changed!  Refusing to continue.
> […]
> Changed symbols:
> […]
> return_address   module: vmlinux, version: 
> 0x0bbae511 -> 0x3244c143, export: EXPORT_SYMBOL_GPL

Full build logs:
  
https://buildd.debian.org/status/fetch.php?pkg=linux=armel=4.9.130-1=1539386797=0
  
https://buildd.debian.org/status/fetch.php?pkg=linux=armhf=4.9.130-1=1539388630=0

A cursory look at the source changes since 4.9.110-* didn't yield any
obvious reasons for that to happen, so I've spent some time trying to
figure out what was happening.

First I checked that the toolchain packages were the same between the
last successful builds and the first failing ones, and that the other
installed packages didn't see obvious updates that could account for
this change.

With the abel.debian.org porterbox I've been able to work with partial
builds (to speed up debugging) in an armel stretch chroot, comparing
4.9.110-3+deb9u6 and 4.9.130-1, after “make vmlinux” in the
debian/build/build_armel_none_marvell directory.

To get more information from genksyms, I've added the -d -D flags to the
genksyms calls in the scripts/Makefile.build file, and triggered another
build with:

touch ../../../arch/arm/kernel/return_address.c
make vmlinux 2>&1 | tee ~/build.txt

Comparing build.txt for both 4.9.110 and 4.9.130, this popped up:
-Export return_address == <__attribute__ ( ( always_inline ) ) __attribute__ ( 
( no_instrument_function ) ) void * return_address ( unsigned int ) >
+Export return_address == <__attribute__ ( ( always_inline , unused ) ) 
__attribute__ ( ( no_instrument_function ) ) void * return_address ( unsigned 
int ) >

along with many more lines accounting for the addition of the “unused”
attribute.

With this hint in mind, it was way easier to spot candidates:

git log --stat -p --pickaxe-all -Gunused v4.9.110..v4.9.130

in the upstream linux tree, which made me suspect:

  
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=29524a9d42f683ca7b67f07f1ac3f6049c8675cc

which aims at fixing inlining, but seems to introduce “unused” as a side
effect.

Since it couldn't be reverted directly, I've revert the following commit
as well:

  
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=02c89527b056301846bfdec4fabbad924d1ad59d

With both commits reverted, a partial build leads to the come back of
the wanted value for the return_address symbol (0x0bbae511), so this
should fix / work around the FTBFS. A full build wasn't attempted
though; feel free to ping me if you'd like that to happen for armel
and/or armhf on abel.


Cheers,
-- 
Cyril Brulebois -- Debian Consultant @ DEBAMAX -- https://debamax.com/


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: linux
Source-Version: 4.9.130-2

We believe that the bug you reported is fixed in the latest version of
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 911...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Ben Hutchings  (supplier of updated 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: Sat, 27 Oct 2018 19:46:16 +0100
Source: linux
Binary: linux-source-4.9 linux-support-4.9.0-8 linux-doc-4.9 linux-manual-4.9 
linux-kbuild-4.9 linux-cpupower libcpupower1 libcpupower-dev linux-perf-4.9 
libusbip-dev usbip hyperv-daemons linux-headers-4.9.0-8-common 
linux-headers-4.9.0-8-common-rt linux-libc-dev 

Processed: found 911557 in 2.0.0~M15-4

[Debian Bug Tracking System]

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

> found 911557 2.0.0~M15-4
Bug #911557 {Done: Dominik George } [apacheds] 
apacheds: broken symlinks: 
/usr/share/apacheds/lib/{log4j-1.2,commons-io,antlr}.jar
Marked as found in versions apache-directory-server/2.0.0~M15-4.
> thanks
Stopping processing here.

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

Bug#858172: marked as done (nanomsg FTBFS: tests/ipc_shutdown fails randomly)

[Debian Bug Tracking System]

Your message dated Sat, 27 Oct 2018 20:10:11 +
with message-id 
and subject line Bug#858172: fixed in nanomsg 1.1.5+dfsg-1
has caused the Debian Bug report #858172,
regarding nanomsg FTBFS: tests/ipc_shutdown fails randomly
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.)


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

https://buildd.debian.org/status/fetch.php?pkg=nanomsg=armel=0.8~beta%2Bdfsg-1%2Bb1=1489891037=0

...
make  check-TESTS
make[3]: Entering directory '/«BUILDDIR»/nanomsg-0.8~beta+dfsg'
make[4]: Entering directory '/«BUILDDIR»/nanomsg-0.8~beta+dfsg'
PASS: tests/inproc
PASS: tests/inproc_shutdown
PASS: tests/ipc
./test-driver: line 107: 12350 Aborted "$@" > $log_file 2>&1
FAIL: tests/ipc_shutdown
PASS: tests/ipc_stress
PASS: tests/tcp
PASS: tests/tcp_shutdown
PASS: tests/ws
PASS: tests/tcpmux
PASS: tests/pair
PASS: tests/pubsub
PASS: tests/reqrep
PASS: tests/pipeline
PASS: tests/survey
PASS: tests/bus
PASS: tests/async_shutdown
PASS: tests/block
PASS: tests/term
PASS: tests/timeo
PASS: tests/iovec
PASS: tests/msg
PASS: tests/prio
PASS: tests/poll
PASS: tests/device
PASS: tests/device4
PASS: tests/device5
PASS: tests/emfile
PASS: tests/domain
PASS: tests/trie
PASS: tests/list
PASS: tests/hash
PASS: tests/symbol
PASS: tests/separation
PASS: tests/zerocopy
PASS: tests/shutdown
PASS: tests/cmsg
PASS: tests/bug328

   nanomsg : ./test-suite.log


# TOTAL: 37
# PASS:  36
# SKIP:  0
# XFAIL: 0
# FAIL:  1
# XPASS: 0
# ERROR: 0

.. contents:: :depth: 2

FAIL: tests/ipc_shutdown


Unexpected source: state=5 source=1 action=5 
(src/transports/utils/streamhdr.c:306)
FAIL tests/ipc_shutdown (exit status: 134)


Testsuite summary for nanomsg 

# TOTAL: 37
# PASS:  36
# SKIP:  0
# XFAIL: 0
# FAIL:  1
# XPASS: 0
# ERROR: 0

See ./test-suite.log
Please report to nano...@freelists.org

Makefile:3350: recipe for target 'test-suite.log' failed
make[4]: *** [test-suite.log] Error 1
--- End Message ---
--- Begin Message ---
Source: nanomsg
Source-Version: 1.1.5+dfsg-1

We believe that the bug you reported is fixed in the latest version of
nanomsg, 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 858...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Harlan Lieberman-Berg  (supplier of updated nanomsg 
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: Sun, 21 Oct 2018 20:17:21 -0400
Source: nanomsg
Binary: libnanomsg-dev nanomsg-utils libnanomsg5
Architecture: source amd64
Version: 1.1.5+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Harlan Lieberman-Berg 
Changed-By: Harlan Lieberman-Berg 
Description:
 libnanomsg-dev - nanomsg development files
 libnanomsg5 - high-performance implementation of scalability libraries
 nanomsg-utils - nanomsg utilities
Closes: 822520 858172
Changes:
 nanomsg (1.1.5+dfsg-1) unstable; urgency=medium
 .
   * New watch file.
   * Update d/copyright
   * Drop patches applied upstream.
   * New upstream version 1.1.5+dfsg (Closes: #858172)
   * Bump symbols
   * Cleanup after nanomsg-utils changes.
   * Switch to salsa
   * Cleanup from major upstream changes.
   * Add missing Expat License directive.
   * Fix rpath issue with patch.
   * Dump the docs in the main docs.
   * Remove Google webfonts that are a privacy violation.
   * Make sure package is fully hardened. (Closes: #822520)
   * Add doc-base.
Checksums-Sha1:
 95e0b584d3cda1401188670b9ccf6e999b094837 2148 nanomsg_1.1.5+dfsg-1.dsc
 338012f34c02edfb52e612d557f4443d85ae8124 256511 nanomsg_1.1.5+dfsg.orig.tar.gz
 86b7b2667d996003b8af831400bf33eac55b16a4 7672 

Processed: Bug #892434 in scorched3d marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #892434 [src:scorched3d] scorched3d: Please use 'pkg-config' to find 
FreeType 2
Added tag(s) pending.

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

Bug#892434: Bug #892434 in scorched3d marked as pending

[Markus Koschany]

Control: tag -1 pending

Hello,

Bug #892434 in scorched3d reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below, and you can check the diff of the fix at:

https://salsa.debian.org/games-team/scorched3d/commit/c8c7da79722b29813ab23807e7063022b741881a


Add freetype-config.patch and detect libraries with pkg-config instead of

freetype-config.

Thanks: Adrian Bunk for the patch.
Closes: #892434



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/892434

Processed: your mail

[Debian Bug Tracking System]

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

> forwarded 887750 https://github.com/Ralnoc/pam-python/pull/3 
> https://sourceforge.net/p/pam-python/tickets/1/#069f/99f1
Bug #887750 [src:pam-python] pam-python FTBFS with glibc 2.26
Changed Bug forwarded-to-address to 
'https://github.com/Ralnoc/pam-python/pull/3 
https://sourceforge.net/p/pam-python/tickets/1/#069f/99f1' from 
'https://github.com/Ralnoc/pam-python/pull/3'.
>
End of message, stopping processing here.

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

Processed: your mail

[Debian Bug Tracking System]

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

> forwarded 887750 https://github.com/Ralnoc/pam-python/pull/3
Bug #887750 [src:pam-python] pam-python FTBFS with glibc 2.26
Changed Bug forwarded-to-address to 
'https://github.com/Ralnoc/pam-python/pull/3' from 
'https://sourceforge.net/p/pam-python/tickets/1/#069f/99f1'.
> tags 887750 + patch
Bug #887750 [src:pam-python] pam-python FTBFS with glibc 2.26
Added tag(s) patch.
>
End of message, stopping processing here.

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

Bug#882943: marked as done (php-guzzlehttp-psr7 FTBFS with phpunit 6.4.4-2)

[Debian Bug Tracking System]

Your message dated Sat, 27 Oct 2018 19:29:38 +
with message-id 
and subject line Bug#882943: fixed in php-guzzlehttp-psr7 1.3.1-1.1
has caused the Debian Bug report #882943,
regarding php-guzzlehttp-psr7 FTBFS with phpunit 6.4.4-2
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.)


-- 
882943: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=882943
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: php-guzzlehttp-psr7
Version: 1.3.1-1
Severity: serious

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/php-guzzlehttp-psr7.html

...
   dh_auto_test
make -j1 test
make[1]: Entering directory '/build/1st/php-guzzlehttp-psr7-1.3.1'
phpunit 
PHP Fatal error:  Class 'PHPUnit_Framework_TestCase' not found in 
/build/1st/php-guzzlehttp-psr7-1.3.1/tests/AppendStreamTest.php on line 7
Makefile:4: recipe for target 'test' failed
make[1]: *** [test] Error 255
--- End Message ---
--- Begin Message ---
Source: php-guzzlehttp-psr7
Source-Version: 1.3.1-1.1

We believe that the bug you reported is fixed in the latest version of
php-guzzlehttp-psr7, 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 882...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Dominik George  (supplier of updated 
php-guzzlehttp-psr7 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: Sat, 27 Oct 2018 20:45:27 +0200
Source: php-guzzlehttp-psr7
Binary: php-guzzlehttp-psr7
Architecture: source all
Version: 1.3.1-1.1
Distribution: unstable
Urgency: medium
Maintainer: Debian PHP PEAR Maintainers 
Changed-By: Dominik George 
Description:
 php-guzzlehttp-psr7 -
Closes: 882943
Changes:
 php-guzzlehttp-psr7 (1.3.1-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Fix tests for PHPUnit newer than 6.4-somewhat. (Closes: #882943)
Checksums-Sha1:
 3dfcf264bdbf6c78875b2c032afba15e29b858f7 2220 php-guzzlehttp-psr7_1.3.1-1.1.dsc
 5d4c01002053a45660aeb340435347e2b59df21e 5540 
php-guzzlehttp-psr7_1.3.1-1.1.debian.tar.xz
 bde5f981d6789a737994c3aa176afed988c7c274 32872 
php-guzzlehttp-psr7_1.3.1-1.1_all.deb
 a15e92b899418fd232f65eafd47e7dbe7f99e154 7593 
php-guzzlehttp-psr7_1.3.1-1.1_amd64.buildinfo
Checksums-Sha256:
 ad7875b8129652c5a5b5fd484647cd8ec37d38ea796292b58d3c3d90aac8cb2d 2220 
php-guzzlehttp-psr7_1.3.1-1.1.dsc
 3073280c214f092e5faa7a05c449c0c9fd0adc902d94c49bc1a18af0bc796287 5540 
php-guzzlehttp-psr7_1.3.1-1.1.debian.tar.xz
 8444686b4e8a225f5c76e2d9a1e2a566206b100d3c27c96982139ad26e8db66d 32872 
php-guzzlehttp-psr7_1.3.1-1.1_all.deb
 505f221c3bc84b1f2cc40c980a2f6f13ee02724ccfbf3cd86b6770b2f1aa019f 7593 
php-guzzlehttp-psr7_1.3.1-1.1_amd64.buildinfo
Files:
 b973ade055848b5e541ae7a62e360a4a 2220 php optional 
php-guzzlehttp-psr7_1.3.1-1.1.dsc
 078e11ffd8a9107050a12e89414910cb 5540 php optional 
php-guzzlehttp-psr7_1.3.1-1.1.debian.tar.xz
 d23024c5eec34b1e3519a8de165b3371 32872 php optional 
php-guzzlehttp-psr7_1.3.1-1.1_all.deb
 6ee34a722592abe38c8da9d933e5d93b 7593 php optional 
php-guzzlehttp-psr7_1.3.1-1.1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJlBAEBCABPFiEEPJ1UpHV1wCb7F/0mt5o8FqDE8pYFAlvUtVAxGmh0dHBzOi8v
d3d3LmRvbWluaWstZ2VvcmdlLmRlL2dwZy1wb2xpY3kudHh0LmFzYwAKCRC3mjwW
oMTylkDYEACodRd4lgrmX0IWbmedE7X1hXWl6R7d6mKz120VhmL+iQanzRfbfMAO
aMexRQZ0izMjOwJJ8O33RJnhsPK8QPZMGp44ZmoC8z/u1R2AGLDa1eSDhbZ074YN
Ba/Nt+W3Qc0m34qNsQ4vBWfMJKUJtm2lf7d9Z6moMzEDCGvK+uzuoe/GzCfLCNyq
zhGGFkxxgq+Lu6rwoiNU4IZobI256yLsKuaat9Q1yU5ePB8yLy34H5zohl7Rhv4L
y3pY/c7LIjVHH5xc9yQEcQODASN2PtRox64FL8dAn+PZ5Kgc6LZEwVcLZFBSim3X
yuHz8a2zTCl1cuwN0qWfXIe/BVJHah37qeO5xTeU19ZAy+1Hm7Yr+gmOUVWV3NNx
5pRAbvlGxOGQfgjK85RFeQYZWbic41wQ0wTvY3SfakGNyPG4ZK1bUrg+Oyxx3dQX
v1CoZxwBYENxapFUulmSfLWE+g9dCK5M+vbHOIiDpcwpAUoHgo0Frxy2xNdXxtEO
Ec3Z87102kSCa+XQCCelI7ezbj/BnhNAPa9GOaqpWQfbhtom4Ze69zEibzcw5PUU
ViUktN0h/+kQP2jzDQm2rEqg9tT+7SyROr75XL2BAdiok+vF2GlGknC3v+hdrlWb
SuZH3g1CUQ9rRcM4y9LBC9AvotW5fhdZv6S9L3HCul+OBgjmiplpFQ==
=KElI
-END PGP SIGNATURE End Message ---

Bug#906603: Can't reproduce.

[Santiago Vila]

On Sat, 27 Oct 2018, Hilko Bengen wrote:

> control: user debian-rele...@lists.debian.org
> control: usertags -1 + bsp-2018-10-de-karlsruhe
> control: tag -1 moreinfo
> control: tag -1 unreproducible
> 
> Hi Santiago,
> 
> greetings from the BSP in Karlsruhe.
> 
> I was going to try if the the FTBFS you reported might have been fixed
> in the new upstream version (0.12.5), but I cannot even reproduce it at
> all.

Thanks for testing. I can't reproduce this anymore, but this used to
fail all the time in August when I reported it:

https://tests.reproducible-builds.org/debian/history/joblib.html

> I have tried 0.12.1-1 (the version you reported against) and
> 0.12.3-1 (the version currently in unstable) on clean sid-amd64 and
> buster-amd64 chroots.

I guess then that the blame is likely to be on some of the build-depends.
To be sure, I would try next a chroot of buster in August from
snapshot.debian.org.

Thanks.

Bug#907335: similar issue

[Julian Taylor]

this problem probably has the same python change as cause as this issue:

https://github.com/PyCQA/pycodestyle/issues/786
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908700

Bug#909928: Marking as pending

[Hilko Bengen]

control: tag -1 pending

The sn package is being adopted and this bug has already been addressed;
see .

Cheers,
-Hilko

Processed: Marking as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #909928 [sn] sn: calls update-inetd with wrong arguments
Added tag(s) pending.

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

Bug#912053: marked as done (twms: FTBFS: UnicodeDecodeError)

[Debian Bug Tracking System]

Your message dated Sat, 27 Oct 2018 21:06:00 +0200
with message-id 

and subject line Re: Bug#912053: twms: FTBFS: UnicodeDecodeError
has caused the Debian Bug report #912053,
regarding twms: FTBFS: UnicodeDecodeError
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.)


-- 
912053: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912053
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: twms
Version: 0.06y-1
Severity: serious
Tags: ftbfs

>From my pbuilder build log:

...
 fakeroot debian/rules clean
dh clean --with=python3 --with=systemd --buildsystem=pybuild
  dh_auto_clean -O--buildsystem=pybuild
I: pybuild base:217: python3.7 setup.py clean
running clean
removing '/build/twms-0.06y/.pybuild/cpython3_3.7/build' (and
everything under it)
/usr/lib/python3/dist-packages/setuptools/dist.py:407: UserWarning:
The version specified ('0.06y') is an invalid version, this may not
work as expected with newer versions of setuptools, pip, and PyPI.
Please see PEP 440 for
more details.
 "details." % self.metadata.version
'build/bdist.linux-amd64' does not exist -- can't clean it
'build/scripts-3.7' does not exist -- can't clean it
I: pybuild base:217: python3.6 setup.py clean
Traceback (most recent call last):
 File "setup.py", line 48, in 
   long_description = read('README.md'),
 File "setup.py", line 14, in read
   return open(os.path.join(os.path.dirname(__file__), fname)).read()
 File "/usr/lib/python3.6/encodings/ascii.py", line 26, in decode
   return codecs.ascii_decode(input, self.errors)[0]
UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position
86: ordinal not in range(128)
E: pybuild pybuild:338: clean: plugin distutils failed with: exit
code=1: python3.6 setup.py clean
dh_auto_clean: pybuild --clean -i python{version} -p "3.7 3.6"
returned exit code 13
make: *** [debian/rules:3: clean] Error 25
dpkg-buildpackage: error: fakeroot debian/rules clean subprocess
returned exit status 2

(Also reproducible in the reproducible-builds.org log.)
-- 
Daniel Schepler
--- End Message ---
--- Begin Message ---
Version: 0.06y-2

On Sat, 27 Oct 2018 at 18:15, Daniel Schepler  wrote:
>
> Source: twms
> Version: 0.06y-1
> Severity: serious
> Tags: ftbfs
>
> From my pbuilder build log:
>
> ...
>  fakeroot debian/rules clean
> dh clean --with=python3 --with=systemd --buildsystem=pybuild
>   dh_auto_clean -O--buildsystem=pybuild
> I: pybuild base:217: python3.7 setup.py clean
> running clean
> removing '/build/twms-0.06y/.pybuild/cpython3_3.7/build' (and
> everything under it)
> /usr/lib/python3/dist-packages/setuptools/dist.py:407: UserWarning:
> The version specified ('0.06y') is an invalid version, this may not
> work as expected with newer versions of setuptools, pip, and PyPI.
> Please see PEP 440 for
> more details.
>  "details." % self.metadata.version
> 'build/bdist.linux-amd64' does not exist -- can't clean it
> 'build/scripts-3.7' does not exist -- can't clean it
> I: pybuild base:217: python3.6 setup.py clean
> Traceback (most recent call last):
>  File "setup.py", line 48, in 
>long_description = read('README.md'),
>  File "setup.py", line 14, in read
>return open(os.path.join(os.path.dirname(__file__), fname)).read()
>  File "/usr/lib/python3.6/encodings/ascii.py", line 26, in decode
>return codecs.ascii_decode(input, self.errors)[0]
> UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position
> 86: ordinal not in range(128)
> E: pybuild pybuild:338: clean: plugin distutils failed with: exit
> code=1: python3.6 setup.py clean
> dh_auto_clean: pybuild --clean -i python{version} -p "3.7 3.6"
> returned exit code 13
> make: *** [debian/rules:3: clean] Error 25
> dpkg-buildpackage: error: fakeroot debian/rules clean subprocess
> returned exit status 2
>
> (Also reproducible in the reproducible-builds.org log.)
> --
> Daniel Schepler

This has already been fixed in the latest upload which is still stuck in NEW.

-- 
Cheers,
  Andrej--- End Message ---

Processed: your mail

[Debian Bug Tracking System]

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

> forwarded 910625 https://github.com/HewlettPackard/netperf/issues/28
Bug #910625 [netperf] netperf: log files are not rotated
Set Bug forwarded-to-address to 
'https://github.com/HewlettPackard/netperf/issues/28'.
>
End of message, stopping processing here.

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

Bug#911504: marked as done (icedove-dev: uninstallable due to missing thunderbird-dev)

[Debian Bug Tracking System]

Your message dated Sat, 27 Oct 2018 18:35:46 +
with message-id 
and subject line Bug#911504: fixed in thunderbird 1:60.2.1-2~deb9u1
has caused the Debian Bug report #911504,
regarding icedove-dev: uninstallable due to missing thunderbird-dev
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.)


-- 
911504: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911504
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: icedove-dev
Version: 1:60.0-3~deb9u1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.

The thunderbird-dev package has been dropped in 1:58.0~b3-1, but the
transitional icedove-dev package is still built for stretch.


cheers,

Andreas
--- End Message ---
--- Begin Message ---
Source: thunderbird
Source-Version: 1:60.2.1-2~deb9u1

We believe that the bug you reported is fixed in the latest version of
thunderbird, 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 911...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Carsten Schoenert  (supplier of updated thunderbird 
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: Sun, 21 Oct 2018 09:42:27 +0200
Source: thunderbird
Binary: thunderbird thunderbird-dbg lightning calendar-google-provider 
thunderbird-l10n-all thunderbird-l10n-ar thunderbird-l10n-ast 
thunderbird-l10n-be thunderbird-l10n-bg thunderbird-l10n-br thunderbird-l10n-ca 
thunderbird-l10n-cs thunderbird-l10n-cy thunderbird-l10n-da thunderbird-l10n-de 
thunderbird-l10n-dsb thunderbird-l10n-el thunderbird-l10n-en-gb 
thunderbird-l10n-es-ar thunderbird-l10n-es-es thunderbird-l10n-et 
thunderbird-l10n-eu thunderbird-l10n-fi thunderbird-l10n-fr 
thunderbird-l10n-fy-nl thunderbird-l10n-ga-ie thunderbird-l10n-gd 
thunderbird-l10n-gl thunderbird-l10n-he thunderbird-l10n-hr 
thunderbird-l10n-hsb thunderbird-l10n-hu thunderbird-l10n-hy-am 
thunderbird-l10n-id thunderbird-l10n-is thunderbird-l10n-it thunderbird-l10n-ja 
thunderbird-l10n-kab thunderbird-l10n-kk thunderbird-l10n-ko 
thunderbird-l10n-lt thunderbird-l10n-ms thunderbird-l10n-nb-no 
thunderbird-l10n-nl thunderbird-l10n-nn-no thunderbird-l10n-pl 
thunderbird-l10n-pt-br thunderbird-l10n-pt-pt
 thunderbird-l10n-rm thunderbird-l10n-ro thunderbird-l10n-ru 
thunderbird-l10n-si thunderbird-l10n-sk thunderbird-l10n-sl thunderbird-l10n-sq 
thunderbird-l10n-sr thunderbird-l10n-sv-se thunderbird-l10n-tr 
thunderbird-l10n-uk thunderbird-l10n-vi thunderbird-l10n-zh-cn 
thunderbird-l10n-zh-tw lightning-l10n-ar lightning-l10n-ast lightning-l10n-be 
lightning-l10n-bg lightning-l10n-br lightning-l10n-ca lightning-l10n-cs 
lightning-l10n-cy lightning-l10n-da lightning-l10n-de lightning-l10n-dsb 
lightning-l10n-el lightning-l10n-es-ar lightning-l10n-es-es 
lightning-l10n-en-gb lightning-l10n-et lightning-l10n-eu lightning-l10n-fi 
lightning-l10n-fr lightning-l10n-fy-nl lightning-l10n-ga-ie lightning-l10n-gd 
lightning-l10n-gl lightning-l10n-he lightning-l10n-hr lightning-l10n-hsb 
lightning-l10n-hu lightning-l10n-hy-am lightning-l10n-id lightning-l10n-is 
lightning-l10n-it lightning-l10n-ja lightning-l10n-kab lightning-l10n-kk 
lightning-l10n-ko lightning-l10n-ms lightning-l10n-lt
 lightning-l10n-nb-no lightning-l10n-nl lightning-l10n-nn-no lightning-l10n-pl 
lightning-l10n-pt-br lightning-l10n-pt-pt lightning-l10n-rm lightning-l10n-ro 
lightning-l10n-ru lightning-l10n-si lightning-l10n-sk lightning-l10n-sl 
lightning-l10n-sr lightning-l10n-sq lightning-l10n-sv-se lightning-l10n-tr 
lightning-l10n-uk lightning-l10n-vi lightning-l10n-zh-cn lightning-l10n-zh-tw 
icedove icedove-dbg iceowl-extension icedove-l10n-all icedove-l10n-ar 
icedove-l10n-ast icedove-l10n-be icedove-l10n-bg icedove-l10n-br 
icedove-l10n-ca icedove-l10n-cs icedove-l10n-da icedove-l10n-de 
icedove-l10n-dsb icedove-l10n-el icedove-l10n-en-gb icedove-l10n-es-ar 
icedove-l10n-es-es icedove-l10n-et icedove-l10n-eu icedove-l10n-fi 
icedove-l10n-fr icedove-l10n-fy-nl icedove-l10n-ga-ie 

Bug#887602: details for test case crash

[Hilko Bengen]

user debian-rele...@lists.debian.org
usertags 887602 + bsp-2018-10-de-karlsruhe
thank you

Hi,

I am able to reproduce the mentioned test case crash when building dia
with freetype 2.9.1-2.

Running the test ("dia ../samples/render-test.dia --export=rt.shape")
after building, installing dia with freetype 2.9.1-2 also crashes.

Running the test after building, installing dia with freetype 2.9.1-2
and downgrading freetype to 2.8.1-2 also crashes.

Running the test after building, installing dia with freetype 2.8.1-2
does *not* crash.

Running the test after building, installing dia with freetype 2.8.1-2
and upgrading freetype to 2.9.1-2 does *not* crash.

Cheers,
-Hilko

Bug#912045: marked as done (mb2md: FTBFS: Test failures)

[Debian Bug Tracking System]

Your message dated Sat, 27 Oct 2018 17:56:40 +
with message-id 
and subject line Bug#912045: fixed in mb2md 3.20-9
has caused the Debian Bug report #912045,
regarding mb2md: FTBFS: Test failures
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.)


-- 
912045: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912045
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mb2md
Version: 3.20-8
Severity: serious
Tags: ftbfs

>From my pbuilder build log:

...
   debian/rules override_dh_auto_test
make[1]: Entering directory '/build/mb2md-3.20'
debian/tests/run-testsuite.sh perl `pwd`/mb2md-3.20.pl

#   Failed test 'Check return from 'perl
/build/mb2md-3.20/mb2md-3.20.pl -s example.mbox -d example.maildir' is
0'
#   at debian/tests/t/mb2md.t line 35.
#  got: '2'
# expected: '0'

#   Failed test 'Stdout as expected ($HOME)'
#   at debian/tests/t/mb2md.t line 36.
#  got: ''
# expected: 'Converting /tmp/TTcKFt21wi/home/example.mbox to
maildir: /tmp/TTcKFt21wi/home/example.maildir
# Source Mbox is /tmp/TTcKFt21wi/home/example.mbox
# Target Maildir is /tmp/TTcKFt21wi/home/example.maildir
# 2 messages.
#
# '

#   Failed test 'No stderr ($HOME)'
#   at debian/tests/t/mb2md.t line 37.
#  got: 'Can't locate Date/Parse.pm in @INC (you may need to
install the Date::Parse module) (@INC contains: /etc/perl
/usr/local/lib/x86_64-linux-gnu/perl/5.26.2
/usr/local/share/perl/5.26.2 /usr/lib/x86_64-linux-gnu
/perl5/5.26 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.26
/usr/share/perl/5.26 /usr/local/lib/site_perl
/usr/lib/x86_64-linux-gnu/perl-base .) at
/build/mb2md-3.20/mb2md-3.20.pl line 385.
# BEGIN failed--compilation aborted at /build/mb2md-3.20/mb2md-3.20.pl line 385.
# '
# expected: ''
Error opendir on '/tmp/TTcKFt21wi/home/example.maildir/cur': No such
file or directory at debian/tests/t/mb2md.t line 38.
# Tests were run but no plan was declared and done_testing() was not seen.
# Looks like your test exited with 2 just after 11.
debian/tests/t/mb2md.t ..
ok 1 - Created '/tmp/TTcKFt21wi/home'
ok 2 - Successfully copied example.mbox to fake home directory
/tmp/TTcKFt21wi/home/
ok 3 - Created '/tmp/TTcKFt21wi/1'
ok 4 - Successfully copied example.mbox to fake home directory
/tmp/TTcKFt21wi/1/
ok 5 - Created '/tmp/TTcKFt21wi/2'
ok 6 - Successfully copied example.mbox to fake home directory
/tmp/TTcKFt21wi/2/
ok 7 - Can run 'perl /build/mb2md-3.20/mb2md-3.20.pl -s example.mbox
-d example.maildir'
ok 8 - Process terminated without a signal
not ok 9 - Check return from 'perl /build/mb2md-3.20/mb2md-3.20.pl -s
example.mbox -d example.maildir' is 0
not ok 10 - Stdout as expected ($HOME)
not ok 11 - No stderr ($HOME)
Dubious, test returned 2 (wstat 512, 0x200)
Failed 3/11 subtests

Test Summary Report
---
debian/tests/t/mb2md.t (Wstat: 512 Tests: 11 Failed: 3)
 Failed tests:  9-11
 Non-zero exit status: 2
 Parse errors: No plan found in TAP output
Files=1, Tests=11,  1 wallclock secs ( 0.02 usr  0.01 sys +  0.08 cusr
 0.01 csys =  0.12 CPU)
Result: FAIL
make[1]: *** [debian/rules:12: override_dh_auto_test] Error 1
make[1]: Leaving directory '/build/mb2md-3.20'
make: *** [debian/rules:6: build] Error 2
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2

(Also reproducible in the reproducible-builds.org log.)
-- 
Daniel Schepler
--- End Message ---
--- Begin Message ---
Source: mb2md
Source-Version: 3.20-9

We believe that the bug you reported is fixed in the latest version of
mb2md, 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 912...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
gregor herrmann  (supplier of updated mb2md 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: Sat, 27 Oct 2018 18:15:22 +0200
Source: mb2md
Binary: mb2md
Architecture: source
Version: 3.20-9
Distribution: unstable
Urgency: medium
Maintainer: Debian Perl Group 
Changed-By: gregor herrmann 
Closes: 912045
Description: 
 mb2md  - Convert Mbox mailboxes to Maildir format
Changes:
 mb2md (3.20-9) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Salvatore 

Bug#853547: marked as done (mgen: ftbfs with GCC-7)

[Debian Bug Tracking System]

Your message dated Sat, 27 Oct 2018 17:56:51 +
with message-id 
and subject line Bug#853547: fixed in mgen 5.02.b+dfsg1-2.1
has caused the Debian Bug report #853547,
regarding mgen: ftbfs with GCC-7
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.)


-- 
853547: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853547
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:mgen
Version: 5.02.b+dfsg1-2
Severity: normal
Tags: sid buster
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-7

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-7/g++-7, but succeeds to build with gcc-6/g++-6. The
severity of this report may be raised before the buster release.
There is no need to fix this issue in time for the stretch release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc7-20170126/mgen_5.02.b+dfsg1-2_unstable_gcc7.log
The last lines of the build log are at the end of this report.

To build with GCC 7, either set CC=gcc-7 CXX=g++-7 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-7/porting_to.html

[...]
make[3]: Leaving directory '/<>/mgen-5.02.b+dfsg1/protolib/makefiles'
make[2]: Leaving directory '/<>/mgen-5.02.b+dfsg1/makefiles'
rm -rf build
make[1]: Leaving directory '/<>/mgen-5.02.b+dfsg1'
   dh_clean
 dpkg-source -b mgen-5.02.b+dfsg1
dpkg-source: info: using source format '3.0 (quilt)'
dpkg-source: info: building mgen using existing ./mgen_5.02.b+dfsg1.orig.tar.xz
dpkg-source: info: building mgen in mgen_5.02.b+dfsg1-2.debian.tar.xz
dpkg-source: info: building mgen in mgen_5.02.b+dfsg1-2.dsc
 debian/rules build
dh build 
   dh_testdir
   dh_update_autotools_config
   dh_auto_configure
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>/mgen-5.02.b+dfsg1'
cd makefiles && make -f Makefile.linux
make[2]: Entering directory '/<>/mgen-5.02.b+dfsg1/makefiles'
g++ -c -g -DPROTO_DEBUG -DHAVE_GPS -DUNIX -Wall -Wcast-align -pedantic -fPIC 
-DLINUX -DHAVE_PSELECT -DHAVE_SCHED -DHAVE_IPV6 -DHAVE_GETLOGIN -DHAVE_LOCKF 
-DHAVE_DIRFD -DHAVE_ASSERT  -D_FILE_OFFSET_BITS=64 -I/usr/X11R6/include  
-I../makefiles -I../include -I../protolib/include -g -O2 
-fdebug-prefix-map=/<>/mgen-5.02.b+dfsg1/makefiles=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -o ../src/common/mgenApp.o ../src/common/mgenApp.cpp
In file included from ../protolib/include/protoAddress.h:8:0,
 from ../protolib/include/protoSocket.h:4,
 from ../protolib/include/protokit.h:6,
 from ../include/mgen.h:4,
 from ../src/common/mgenApp.cpp:2:
../protolib/include/protoTree.h: In member function 'ITEM_TYPE* 
ProtoSortedTreeTemplate::Iterator::PeekPrevItem() const':
../protolib/include/protoTree.h:652:93: error: no matching function for call to 
'ProtoSortedTreeTemplate::Iterator::PeekPrevItem() const'
 {return 
static_cast(ProtoSortedTree::Iterator::PeekPrevItem());}

 ^
../protolib/include/protoTree.h:565:23: note: candidate: ProtoSortedTree::Item* 
ProtoSortedTree::Iterator::PeekPrevItem() 
 Item* PeekPrevItem()
   ^~~~
../protolib/include/protoTree.h:565:23: note:   passing 'const 
ProtoSortedTreeTemplate::Iterator*' as 'this' argument discards 
qualifiers
../protolib/include/protoTree.h: In member function 'ITEM_TYPE* 
ProtoSortedTreeTemplate::Iterator::PeekNextItem() const':
../protolib/include/protoTree.h:657:93: error: no matching function for call to 
'ProtoSortedTreeTemplate::Iterator::PeekNextItem() const'
 {return 
static_cast(ProtoSortedTree::Iterator::PeekNextItem());}

 ^
../protolib/include/protoTree.h:563:23: note: candidate: ProtoSortedTree::Item* 
ProtoSortedTree::Iterator::PeekNextItem() 

Bug#912039: marked as done (libpetail-utils-perl: FTBFS: Test failures)

[Debian Bug Tracking System]

Your message dated Sat, 27 Oct 2018 17:55:36 +
with message-id 
and subject line Bug#912039: fixed in libpetal-utils-perl 0.06-4
has caused the Debian Bug report #912039,
regarding libpetail-utils-perl: FTBFS: Test failures
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.)


-- 
912039: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912039
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libpetal-utils-perl
Version: 0.06-3
Severity: serious
Tags: ftbfs

>From my pbuilder build log:

...
   dh_auto_test
dh_auto_test: Compatibility levels before 9 are deprecated (level 8 in use)
   perl Build test --verbose 1

#   Failed test 'use set :default'
#   at t/01__import.t line 21.
#  got: 'Can't find Petal plugin: 'Date'! at
/build/libpetal-utils-perl-0.06/blib/lib/Petal/Utils.pm line 111.
# BEGIN failed--compilation aborted at (eval 13) line 1.
# '
# expected: ''
# Looks like you failed 1 test of 6.
t/01__import.t ...
ok 1 - use Petal::Utils
ok 2 - use set :none
not ok 3 - use set :default
ok 4 - use plugin UpperCase
ok 5 - error loading non-existent set
ok 6 - error loading non-existent plugin
1..6
Dubious, test returned 1 (wstat 256, 0x100)
Failed 1/6 subtests
t/02__debug.t 
ok 1 - dump
1..1
ok
t/03__text.t .
ok 1 - lc
ok 2 - uc
ok 3 - uc_first
1..3
ok
t/04__logic.t 
ok 1 - first
ok 2 - second
ok 3 - or
ok 4 - and
ok 5 - equal
ok 6 - like
ok 7 - if
ok 8 - if
1..8
ok
Can't find Petal plugin: 'Date'! at
/build/libpetal-utils-perl-0.06/blib/lib/Petal/Utils.pm line 111.
BEGIN failed--compilation aborted at t/05__date.t line 15.
t/05__date.t . skipped: (no reason given)
t/06__list.t .
ok 1 - sort
1..1
ok
t/07__hash.t .
ok 1 - each
ok 2 - each
ok 3 - each
ok 4 - keys
ok 5 - keys
ok 6 - keys
not ok 7 - dkeys # TODO Petal cannot use dynamic hash keys to look up values
#   Failed (TODO) test 'dkeys'
#   at t/07__hash.t line 45.
#   '
#   
#   
#
#   
#   ekey2 => evalue2ekey3 =>
evalue3ekey1 => evalue1
#   
#
#
#   
#
#   kkey3 => kkey2 =>
kkey1 => 
#   
#   
#   
# '
# doesn't match '(?^:kkey1 => kvalue1)'
1..7
ok
t/08__uri.t ..
ok 1 - &
ok 2 - ' '
ok 3 - ,
ok 4 - ;
ok 5 - /
ok 6 - ?
ok 7 - .
1..7
ok
t/20__Base.t .
ok 1 - split_first_arg - 'first second'
ok 2 - split_first_arg - 'first second'
ok 3 - split_first_arg - ''first' second'
ok 4 - split_first_arg - ''first' second'
ok 5 - split_first_arg - 'first second third'
ok 6 - split_first_arg - 'first second third'
ok 7 - split_first_arg - 'first second third'
ok 8 - split_first_arg - ''first' second third fourth'
ok 9 - split_first_arg - ''first' second third fourth'
ok 10 - split_first_arg - ''first' second third fourth'
ok 11 - split_first_arg - ''first' second third fourth'
ok 12 - split_first_arg - 'string: first second''
ok 13 - split_first_arg - 'string: first second''
ok 14 - split_args - 'first second'
ok 15 - split_args - 'first second'
ok 16 - split_args - ''first' second'
ok 17 - split_args - ''first' second'
ok 18 - split_args - 'first second third'
ok 19 - split_args - 'first second third'
ok 20 - split_args - 'first second third'
ok 21 - split_args - ''first' second third fourth'
ok 22 - split_args - ''first' second third fourth'
ok 23 - split_args - ''first' second third fourth'
ok 24 - split_args - ''first' second third fourth'
ok 25 - split_args - 'string: first second'
ok 26 - split_args - 'string: first second'
ok 27 - split_args - 'string: first second'
ok 28 - Fetch value of Dad
ok 29 - Fetch plaintext
ok 30 - Fetch number
ok 31 - Fetch number with decimal
1..31
ok
t/21__Limit.t 
ok 1 - no limit
ok 2 - limit 1
ok 3 - limit 2
1..3
ok
t/22__Limitr.t ...
ok 1 - no limit
ok 2 - limit 1
ok 3 - limit 2
1..3
ok
t/23__Create_Href.t ..
ok 1 - url1
ok 2 - url2
ok 3 - url3
ok 4 - url4
1..4
ok
t/24__Substr.t ...
ok 1 - substr1
ok 2 - substr2
ok 3 - substr3
ok 4 - substr4
ok 5 - substr4
1..5
ok
t/25__Decode.t ...
ok 1 - decode1
ok 2 - decode2
ok 3 - decode2a
ok 4 - decode2b
ok 5 - decode3 - true (1)
ok 6 - decode4 - false (0)
ok 7 - decode5 - false (false)
ok 8 - decode6
ok 9 - decode7
ok 10 - decode8
ok 11 - decode9
ok 12 - decode10
ok 13 - decode11
ok 14 - decode12
ok 15 - decode13
ok 16 - decode14
ok 17 - decode15
1..17
ok
t/26__Printf.t ...
ok 1 - printf1
ok 2 - printf2
ok 3 - printf3
ok 4 - printf4
ok 5 - printf5
ok 6 - printf6
1..6
ok

Bug#897496: python-pathlib: diff for NMU version 1.0.1-2.1

[Julian Taylor]

Control: tags 897496 + pending
Control: tags 897496 + patch
Control: user debian-rele...@lists.debian.org
Control: usertags 897496 + bsp-2018-10-de-karlsruhe

Dear maintainer,

I've prepared an NMU for python-pathlib (versioned as 1.0.1-2.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

Regards,
diff -Nru python-pathlib-1.0.1/debian/changelog
python-pathlib-1.0.1/debian/changelog
--- python-pathlib-1.0.1/debian/changelog   2015-06-25 10:02:25.0
+0200
+++ python-pathlib-1.0.1/debian/changelog   2018-10-27 19:02:33.0
+0200
@@ -1,3 +1,11 @@
+python-pathlib (1.0.1-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * socket-test-fix.patch:
+Adapt testcase to work with python2 exception type (Closes: #897496)
+
+ -- Julian Taylor   Sat, 27 Oct 2018
19:02:33 +0200
+
 python-pathlib (1.0.1-2) unstable; urgency=medium

   * Enable reproducible build py patching generation of manpage
diff -Nru python-pathlib-1.0.1/debian/patches/series
python-pathlib-1.0.1/debian/patches/series
--- python-pathlib-1.0.1/debian/patches/series  1970-01-01
01:00:00.0 +0100
+++ python-pathlib-1.0.1/debian/patches/series  2018-10-27
18:59:43.0 +0200
@@ -0,0 +1 @@
+socket-test-fix.patch
diff -Nru python-pathlib-1.0.1/debian/patches/socket-test-fix.patch
python-pathlib-1.0.1/debian/patches/socket-test-fix.patch
--- python-pathlib-1.0.1/debian/patches/socket-test-fix.patch   1970-01-01
01:00:00.0 +0100
+++ python-pathlib-1.0.1/debian/patches/socket-test-fix.patch   2018-10-27
19:02:33.0 +0200
@@ -0,0 +1,18 @@
+Description: adapt test exception to python2
+Author: Julian Taylor 
+Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897496
+Bug: https://bitbucket.org/pitrou/pathlib/issues/32
+
+Index: python-pathlib-1.0.1/test_pathlib.py
+===
+--- python-pathlib-1.0.1.orig/test_pathlib.py
 python-pathlib-1.0.1/test_pathlib.py
+@@ -1687,7 +1687,7 @@ class _BasePathTest(object):
+ self.addCleanup(sock.close)
+ try:
+ sock.bind(str(P))
+-except OSError as e:
++except (OSError, socket.error) as e:
+ if "AF_UNIX path too long" in str(e):
+ self.skipTest("cannot bind Unix socket: " + str(e))
+ self.assertTrue(P.is_socket())

Processed (with 2 errors): python-pathlib: diff for NMU version 1.0.1-2.1

[Debian Bug Tracking System]

Processing control commands:

> tags 897496 + pending
Bug #897496 [src:python-pathlib] python-pathlib: FTBFS: dh_auto_test: pybuild 
--test -i python{version} -p 2.7 returned exit code 13
Added tag(s) pending.
> tags 897496 + patch
Bug #897496 [src:python-pathlib] python-pathlib: FTBFS: dh_auto_test: pybuild 
--test -i python{version} -p 2.7 returned exit code 13
Added tag(s) patch.
> user debian-rele...@lists.debian.org
Unknown command or malformed arguments to command.

> usertags 897496 + bsp-2018-10-de-karlsruhe
Unknown command or malformed arguments to command.


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

Bug#911557: marked as done (apacheds: broken symlinks: /usr/share/apacheds/lib/{log4j-1.2,commons-io,antlr}.jar)

[Debian Bug Tracking System]

Your message dated Sat, 27 Oct 2018 17:50:46 +
with message-id 
and subject line Bug#911557: fixed in apache-directory-server 2.0.0~M24-2
has caused the Debian Bug report #911557,
regarding apacheds: broken symlinks: 
/usr/share/apacheds/lib/{log4j-1.2,commons-io,antlr}.jar
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.)


-- 
911557: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911557
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: apacheds
Version: 2.0.0~M24-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package ships (or creates)
a broken symlink.

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

0m43.2s ERROR: FAIL: Broken symlinks:
  /usr/share/apacheds/lib/log4j-1.2.jar -> ../../java/log4j-1.2.jar (apacheds)
  /usr/share/apacheds/lib/commons-io.jar -> ../../java/commons-io.jar (apacheds)
  /usr/share/apacheds/lib/antlr.jar -> ../../java/antlr.jar (apacheds)


Assuming that apacheds does not work correctly without these
libraries, I've set the severity to serious.


cheers,

Andreas


apacheds_2.0.0~M24-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: apache-directory-server
Source-Version: 2.0.0~M24-2

We believe that the bug you reported is fixed in the latest version of
apache-directory-server, 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 911...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Dominik George  (supplier of updated 
apache-directory-server 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: Sat, 27 Oct 2018 16:30:27 +0200
Source: apache-directory-server
Binary: libapacheds-java libapacheds-kerberos-codec-java libapacheds-i18n-java 
apacheds
Architecture: source all
Version: 2.0.0~M24-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: Dominik George 
Description:
 apacheds   - Apache Directory Server
 libapacheds-i18n-java - Apache Directory Server (i18n)
 libapacheds-java - Apache Directory Server (Libraries)
 libapacheds-kerberos-codec-java - Apache Directory Server (Kerberos Codec)
Closes: 909063 911557
Changes:
 apache-directory-server (2.0.0~M24-2) unstable; urgency=medium
 .
   * Team upload.
   * Fix command in systemd service file. (Closes: #909063)
   * Add missing dependencies to libraries. (Closes: #911557)
 + wrap-and-sort.
   * Install NOTICE file to docs as required by Apache licence.
Checksums-Sha1:
 e0d1b59023f45de1fdca3ba635a2ba7281572555 2794 
apache-directory-server_2.0.0~M24-2.dsc
 a76b13c011996cb77e86101f49b028a106e7f42d 10056 
apache-directory-server_2.0.0~M24-2.debian.tar.xz
 c1128489781ccb0c057e1dfd1012a6fad6c3b635 16851 
apache-directory-server_2.0.0~M24-2_amd64.buildinfo
 29b3c8a89f92369279725aa38ef9421277268b48 31596 apacheds_2.0.0~M24-2_all.deb
 fa5a9c37060900897471e03b891a685bd2c3bcd1 34856 
libapacheds-i18n-java_2.0.0~M24-2_all.deb
 e22c396ae2d6b708b3547bdf906aa8fc902ed7ea 1642464 
libapacheds-java_2.0.0~M24-2_all.deb
 35be4d801d4763a0f99a4d81e58a938e3f4da0b2 553804 
libapacheds-kerberos-codec-java_2.0.0~M24-2_all.deb
Checksums-Sha256:
 c7432df0c2504bbfca5f6f89c2fbe0b7cf86f678f93222dd6ff7420e72699be5 2794 
apache-directory-server_2.0.0~M24-2.dsc
 3bbced86ebc10c6e7696e599b14c34506e910efdeee6545b9d5811d12806304e 10056 
apache-directory-server_2.0.0~M24-2.debian.tar.xz
 06db4a6d29fc9cdbef33beaaf0e639d966b03b83c4b80052df9853906584a35e 16851 
apache-directory-server_2.0.0~M24-2_amd64.buildinfo
 1b69adeab50fded5658175a3ec93733218e9a9822d6b1b38d55f7bae8aa90d47 31596 
apacheds_2.0.0~M24-2_all.deb
 5132e2b209cb6536d1db1276f4b294ebe0ee35bb5f9ad0c3d30a3b9526c82ae6 34856 
libapacheds-i18n-java_2.0.0~M24-2_all.deb
 a9f99b5b74f4bad3875e7f1ca8edfcc312d7f55fc3278e8dcd51c3b070e7ac4c 1642464 
libapacheds-java_2.0.0~M24-2_all.deb
 5dc1056abaae1f6fdcc83ca5ea1a27c67c2e999feaaf4149c54befcaf668c1e3 553804 
libapacheds-kerberos-codec-java_2.0.0~M24-2_all.deb
Files:
 1002739bec7b33c2ba2f29532c12d817 2794 java optional 
apache-directory-server_2.0.0~M24-2.dsc
 c6b3bdccbea5803545c909f63e050222 10056 

Bug#909063: marked as done (apacheds: package installation fails due to incorrect apacheds.service unit)

[Debian Bug Tracking System]

Your message dated Sat, 27 Oct 2018 17:50:46 +
with message-id 
and subject line Bug#909063: fixed in apache-directory-server 2.0.0~M24-2
has caused the Debian Bug report #909063,
regarding apacheds: package installation fails due to incorrect 
apacheds.service unit
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.)


-- 
909063: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909063
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: apacheds
Version: 2.0.0~M15-4
Severity: grave
Justification: renders package unusable

Dear Maintainer,

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

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

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

I am unable to install the apacheds package. The installation fails
when dpkg attempts to start the service due to incorrect ExecStart=
directives in the apacheds.service system unit.

I have tried on both stretch and buster, the same problem happens on
both.

Below I have included the complete output of the apt-get command used,
as well as the output of "journalctl -u apacheds.service" after the
package failed to install.


*** apt-get-install-apacheds.txt

root@ldap01:~# apt-get install apacheds
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following additional packages will be installed:
  ant ant-optional ca-certificates-java default-jre-headless fontconfig-config 
fonts-dejavu-core java-common junit4 libantlr-java libapache-directory-api-java 
libapache-directory-jdbm-java libapache-pom-java
  libapacheds-i18n-java libapacheds-java libapacheds-kerberos-codec-java 
libavahi-client3 libavahi-common-data libavahi-common3 libbcprov-java 
libcommons-collections3-java libcommons-io-java
  libcommons-lang-java libcommons-logging-java libcommons-parent-java 
libcommons-pool-java libcups2 libdom4j-java libehcache-java libfontconfig1 
libhamcrest-java libisorelax-java libjaxen-java libjaxp1.3-java
  libjdom1-java libjetty9-java libjpeg62-turbo liblcms2-2 liblog4j1.2-java 
libmavibot-java libmina2-java libmsv-java libnspr4 libnss3 libpcsclite1 
librelaxng-datatype-java libservlet3.1-java libslf4j-java
  libxerces2-java libxi6 libxml-commons-external-java 
libxml-commons-resolver1.1-java libxom-java libxpp2-java libxpp3-java 
libxrender1 libxtst6 openjdk-8-jre-headless x11-common
Suggested packages:
  ant-doc ant-gcj default-jdk | java-compiler | java-sdk ant-optional-gcj antlr 
javacc junit jython libbcel-java libbsf-java libcommons-net-java libmail-java 
libjdepend-java libjsch-java liboro-java
  libregexp-java libxalan2-java default-jre libbcprov-java-doc 
libcommons-collections3-java-doc libcommons-io-java-doc 
libcommons-lang-java-doc libavalon-framework-java libcommons-logging-java-doc
  libexcalibur-logkit-java cups-common libdom4j-java-doc libjaxp1.3-java-gcj 
libjdom1-java-doc jetty9 liblcms2-utils liblog4j1.2-java-doc libmina-java-doc 
libspring-beans-java libjzlib-java libognl-java
  libtomcat8-java pcscd libxerces2-java-doc libxerces2-java-gcj 
libxml-commons-resolver1.1-java-doc libxom-java-doc libnss-mdns 
fonts-dejavu-extra fonts-ipafont-gothic fonts-ipafont-mincho fonts-wqy-microhei
  fonts-wqy-zenhei fonts-indic
The following NEW packages will be installed:
  ant ant-optional apacheds ca-certificates-java default-jre-headless 
fontconfig-config fonts-dejavu-core java-common junit4 libantlr-java 
libapache-directory-api-java libapache-directory-jdbm-java
  libapache-pom-java libapacheds-i18n-java libapacheds-java 
libapacheds-kerberos-codec-java libavahi-client3 libavahi-common-data 
libavahi-common3 libbcprov-java libcommons-collections3-java libcommons-io-java
  libcommons-lang-java libcommons-logging-java libcommons-parent-java 
libcommons-pool-java libcups2 libdom4j-java libehcache-java libfontconfig1 
libhamcrest-java libisorelax-java libjaxen-java libjaxp1.3-java
  libjdom1-java libjetty9-java libjpeg62-turbo liblcms2-2 liblog4j1.2-java 
libmavibot-java libmina2-java libmsv-java libnspr4 libnss3 libpcsclite1 
librelaxng-datatype-java libservlet3.1-java libslf4j-java
  libxerces2-java libxi6 libxml-commons-external-java 
libxml-commons-resolver1.1-java libxom-java libxpp2-java libxpp3-java 
libxrender1 libxtst6 openjdk-8-jre-headless x11-common
0 upgraded, 59 newly installed, 0 to remove and 1 not upgraded.
Need to get 53.3 MB of archives.
After this 

Bug#884856: marked as done (apacheds: deinstallation impossible without first configuring it)

[Debian Bug Tracking System]

Your message dated Sat, 27 Oct 2018 17:50:46 +
with message-id 
and subject line Bug#909063: fixed in apache-directory-server 2.0.0~M24-2
has caused the Debian Bug report #909063,
regarding apacheds: deinstallation impossible without first configuring it
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.)


-- 
909063: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909063
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: apacheds
Version: 2.0.0~M15-4
Severity: minor

Dear Maintainer,


   * What led up to the situation?

fresh installation using 9.3.0-amd64-netinst, using default options where
possible
then installed apacheds and just wanted to get rid of it again


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

apt-get install apacheds
apt-get purge apacheds


   * What was the outcome of this action?

deinstallation failed

root@debian:~# apt-get purge apacheds
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer required:
  libantlr-java libapache-directory-api-java libapache-directory-jdbm-java
libapacheds-i18n-java
  libapacheds-java libapacheds-kerberos-codec-java libcommons-io-java
libcommons-lang-java
  libcommons-pool-java libjetty9-java libmavibot-java libmina2-java
libslf4j-java
Use 'apt autoremove' to remove them.
The following packages will be REMOVED:
  apacheds*
0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
1 not fully installed or removed.
After this operation, 172 kB disk space will be freed.
Do you want to continue? [Y/n]
(Reading database ... 129867 files and directories currently installed.)
Removing apacheds (2.0.0~M15-4) ...
Failed to stop apacheds.service: Unit apacheds.service not loaded.
invoke-rc.d: initscript apacheds, action "stop" failed.
dpkg: error processing package apacheds (--remove):
 subprocess installed pre-removal script returned error exit status 5
Errors were encountered while processing:
 apacheds
E: Sub-process /usr/bin/dpkg returned an error code (1)
root@debian:~#



   * What outcome did you expect instead?

well, a removed package


Regards,
Carsten



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

Versions of packages apacheds depends on:
ii  adduser  3.115
ii  default-jre-headless [java7-runtime-headless]2:1.8-58
ii  libapacheds-java 2.0.0~M15-4
ii  openjdk-8-jre-headless [java7-runtime-headless]  8u151-b12-1~deb9u1

apacheds recommends no packages.

apacheds suggests no packages.

-- Configuration Files:
/etc/apacheds/config.ldif [Errno 13] Permission denied: 
'/etc/apacheds/config.ldif'
/etc/apacheds/log4j.properties [Errno 13] Permission denied: 
'/etc/apacheds/log4j.properties'

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: apache-directory-server
Source-Version: 2.0.0~M24-2

We believe that the bug you reported is fixed in the latest version of
apache-directory-server, 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 909...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Dominik George  (supplier of updated 
apache-directory-server 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: Sat, 27 Oct 2018 16:30:27 +0200
Source: apache-directory-server
Binary: libapacheds-java libapacheds-kerberos-codec-java libapacheds-i18n-java 
apacheds
Architecture: source all
Version: 2.0.0~M24-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: Dominik George 
Description:
 apacheds   - Apache Directory Server
 libapacheds-i18n-java - Apache Directory Server (i18n)
 libapacheds-java - Apache Directory Server (Libraries)
 

Bug#886872: agrep: does not properly clean after build

[Reiner Herrmann]

Control: severity -1 important

Lowering the severity as it doesn't FTBFS on the first build.
Failing to build the second time is not RC.


signature.asc
Description: PGP signature

Processed: Re: agrep: does not properly clean after build

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #886872 [src:agrep] agrep: does not properly clean after build
Severity set to 'important' from 'serious'

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

Bug#910031: fuse3: Incomplete debian/copyright?

[Fabio Pedretti]

It looks like this is fixed in 3.2.6-1 :
https://metadata.ftp-master.debian.org/changelogs/main/f/fuse3/fuse3_3.2.6-1_copyright
but missed closing this bug?

fuse3 (3.2.6-1) unstable; urgency=medium

  * New upstream release:
- fix CVE-2018-10906, restriction bypass of the allow_other option when
  SELinux is active (closes: #911343).
  * Honor nocheck in DEB_BUILD_OPTIONS (closes: #910029).
  * Don't force xz compression for source and binaries (closes: #910030).
  * Update copyright file.

 -- Laszlo Boszormenyi (GCS)   Thu, 18 Oct 2018 21:36:00 +

Bug#912061: msgpack-c FTBFS with googletest 1.8.1-1

[Adrian Bunk]

Source: msgpack-c
Version: 3.0.1-1
Severity: serious
Tags: ftbfs

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

...
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/build/1st/msgpack-c-3.0.1'
mkdir build-gtest
cd build-gtest && \
  cmake -Wno-dev 
-DCMAKE_INSTALL_PREFIX=/build/1st/msgpack-c-3.0.1/build-gtest/install 
/usr/src/googletest/googletest && \
  make install
CMake Warning at CMakeLists.txt:47 (project):
  VERSION keyword not followed by a value or was followed by a value that
  expanded to nothing.


-- The CXX compiler identification is GNU 8.2.0
-- The C compiler identification is GNU 8.2.0
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Found PythonInterp: /usr/bin/python (found version "2.7.15") 
-- Looking for pthread.h
-- Looking for pthread.h - found
-- Looking for pthread_create
-- Looking for pthread_create - not found
-- Check if compiler accepts -pthread
-- Check if compiler accepts -pthread - yes
-- Found Threads: TRUE  
-- Configuring done
-- Generating done
-- Build files have been written to: /build/1st/msgpack-c-3.0.1/build-gtest
make[2]: Entering directory '/build/1st/msgpack-c-3.0.1/build-gtest'
make[2]: *** No rule to make target 'install'.  Stop.

Bug#912060: botch FTBFS: W504 line break after binary operator

[Adrian Bunk]

Source: botch
Version: 0.21-6
Severity: serious
Tags: ftbfs

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

...
   debian/rules override_dh_auto_test-arch
make[1]: Entering directory '/build/1st/botch-0.21'
/usr/bin/make test
make[2]: Entering directory '/build/1st/botch-0.21'
# FIXME: add more tests
#./tests.py
#OCAMLPATH=/build/1st/botch-0.21/dose/_build ocamlbuild -classic-display 
-use-ocamlfind -cflags "-w +a-4-9-24" tests.native
#./tests.native
pyflakes3 tools/*.py
# E402 is triggered by the sys.path.append() statement in front of import of 
utils
# see https://github.com/PyCQA/pycodestyle/issues/264
pycodestyle --ignore=E402,E722 tools/*.py
tools/add-arch.py:33:22: W504 line break after binary operator
tools/build-order-from-zero.py:170:27: W504 line break after binary operator
tools/build-order-from-zero.py:203:27: W504 line break after binary operator
tools/buildgraph2packages.py:46:22: W504 line break after binary operator
tools/calcportsmetric.py:56:22: W504 line break after binary operator
tools/calcportsmetric.py:57:22: W504 line break after binary operator
tools/calcportsmetric.py:58:22: W504 line break after binary operator
tools/calcportsmetric.py:59:22: W504 line break after binary operator
tools/calcportsmetric.py:63:14: W504 line break after binary operator
tools/calcportsmetric.py:64:14: W504 line break after binary operator
tools/calcportsmetric.py:68:14: W504 line break after binary operator
tools/calcportsmetric.py:69:14: W504 line break after binary operator
tools/check-ma-same-versions.py:49:22: W504 line break after binary operator
tools/check-ma-same-versions.py:50:22: W504 line break after binary operator
tools/checkfas.py:31:22: W504 line break after binary operator
tools/checkfas.py:32:22: W504 line break after binary operator
tools/checkfas.py:35:30: W504 line break after binary operator
tools/checkfas.py:38:30: W504 line break after binary operator
tools/checkfas.py:39:30: W504 line break after binary operator
tools/convert-arch.py:34:22: W504 line break after binary operator
tools/dose2html.py:111:15: W504 line break after binary operator
tools/dose2html.py:112:15: W504 line break after binary operator
tools/dose2html.py:114:15: W504 line break after binary operator
tools/dose2html.py:115:15: W504 line break after binary operator
tools/dose2html.py:116:15: W504 line break after binary operator
tools/dose2html.py:139:11: W504 line break after binary operator
tools/dose2html.py:140:11: W504 line break after binary operator
tools/dose2html.py:141:11: W504 line break after binary operator
tools/dose2html.py:142:11: W504 line break after binary operator
tools/dose2html.py:143:11: W504 line break after binary operator
tools/dose2html.py:147:11: W504 line break after binary operator
tools/dose2html.py:174:19: W504 line break after binary operator
tools/dose2html.py:206:11: W504 line break after binary operator
tools/dose2html.py:207:11: W504 line break after binary operator
tools/dose2html.py:208:11: W504 line break after binary operator
tools/dose2html.py:209:11: W504 line break after binary operator
tools/dose2html.py:210:11: W504 line break after binary operator
tools/dose2html.py:216:9: W504 line break after binary operator
tools/dose2html.py:258:19: W504 line break after binary operator
tools/dose2html.py:340:11: W504 line break after binary operator
tools/dose2html.py:341:11: W504 line break after binary operator
tools/dose2html.py:348:15: W504 line break after binary operator
tools/dose2html.py:366:15: W504 line break after binary operator
tools/dose2html.py:521:25: W504 line break after binary operator
tools/dose2html.py:527:30: W504 line break after binary operator
tools/dose2html.py:530:30: W504 line break after binary operator
tools/dose2html.py:569:13: W504 line break after binary operator
tools/dose2html.py:570:13: W504 line break after binary operator
tools/droppable-diff.py:11:22: W504 line break after binary operator
tools/droppable-union.py:10:51: W504 line break after binary operator
tools/droppable-union.py:11:51: W504 line break after binary operator
tools/droppable-union.py:12:51: W504 line break after binary operator
tools/extract-scc.py:33:50: W504 line break after binary operator
tools/extract-scc.py:34:50: W504 line break after binary operator
tools/extract-scc.py:39:45: W504 line break after binary operator
tools/extract-scc.py:42:43: W504 line break after binary operator
tools/fix-cross-problems.py:73:22: W504 line break after binary operator
tools/fix-cross-problems.py:76:30: W504 line break after binary operator
tools/graph-difference.py:89:11: W504 line break after binary operator
tools/graph-difference.py:107:15: W504 line break after binary operator
tools/graph-difference.py:111:11: W504 line break after binary operator
tools/graph-info.py:12:22: W504 line break after binary operator
tools/latest-version.py:30:22: W504 line break after binary operator
tools/multiarch-interpreter-problem.py:164:22: W504 line break 

Processed: tagging 910856

[Debian Bug Tracking System]

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

> tags 910856 + ftbfs
Bug #910856 [src:sollya] sollya: test fails on most architectures
Added tag(s) ftbfs.
> thanks
Stopping processing here.

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

Processed: severity of 910856 is serious

[Debian Bug Tracking System]

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

> severity 910856 serious
Bug #910856 [src:sollya] sollya: test fails on most architectures
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

Processed: user debian-rele...@lists.debian.org, usertagging 853547, tagging 853547

[Debian Bug Tracking System]

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

> user debian-rele...@lists.debian.org
Setting user to debian-rele...@lists.debian.org (was rei...@reiner-h.de).
> usertags 853547 bsp-2018-10-de-karlsruhe
There were no usertags set.
Usertags are now: bsp-2018-10-de-karlsruhe.
> tags 853547 + pending
Bug #853547 [src:mgen] mgen: ftbfs with GCC-7
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#912053: marked as done (twms: FTBFS: UnicodeDecodeError)

[Debian Bug Tracking System]

Your message dated Sat, 27 Oct 2018 20:07:29 +0300
with message-id <20181027170729.GU24921@localhost>
and subject line Fixed in the version in NEW
has caused the Debian Bug report #912053,
regarding twms: FTBFS: UnicodeDecodeError
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.)


-- 
912053: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912053
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: twms
Version: 0.06y-1
Severity: serious
Tags: ftbfs

>From my pbuilder build log:

...
 fakeroot debian/rules clean
dh clean --with=python3 --with=systemd --buildsystem=pybuild
  dh_auto_clean -O--buildsystem=pybuild
I: pybuild base:217: python3.7 setup.py clean
running clean
removing '/build/twms-0.06y/.pybuild/cpython3_3.7/build' (and
everything under it)
/usr/lib/python3/dist-packages/setuptools/dist.py:407: UserWarning:
The version specified ('0.06y') is an invalid version, this may not
work as expected with newer versions of setuptools, pip, and PyPI.
Please see PEP 440 for
more details.
 "details." % self.metadata.version
'build/bdist.linux-amd64' does not exist -- can't clean it
'build/scripts-3.7' does not exist -- can't clean it
I: pybuild base:217: python3.6 setup.py clean
Traceback (most recent call last):
 File "setup.py", line 48, in 
   long_description = read('README.md'),
 File "setup.py", line 14, in read
   return open(os.path.join(os.path.dirname(__file__), fname)).read()
 File "/usr/lib/python3.6/encodings/ascii.py", line 26, in decode
   return codecs.ascii_decode(input, self.errors)[0]
UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position
86: ordinal not in range(128)
E: pybuild pybuild:338: clean: plugin distutils failed with: exit
code=1: python3.6 setup.py clean
dh_auto_clean: pybuild --clean -i python{version} -p "3.7 3.6"
returned exit code 13
make: *** [debian/rules:3: clean] Error 25
dpkg-buildpackage: error: fakeroot debian/rules clean subprocess
returned exit status 2

(Also reproducible in the reproducible-builds.org log.)
-- 
Daniel Schepler
--- End Message ---
--- Begin Message ---
Version: 0.06y-2

  * Temporarily work around the encoding issue by forcefully setting
LC_ALL to C.UTF-8.

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

Processed: tagging 817717, tagging 745200, tagging 641330

[Debian Bug Tracking System]

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

> tags 817717 + pending
Bug #817717 [src:vtgrab] vtgrab: Removal of debhelper compat 4
Added tag(s) pending.
> tags 745200 + pending
Bug #745200 [src:vtgrab] vtgrab: Please use arch:linux-any
Added tag(s) pending.
> tags 641330 + pending
Bug #641330 [vtgrab] package ftbfs with ld --as-needed
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: NMU for validns

[Debian Bug Tracking System]

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

> tags 859784 pending
Bug #859784 [validns] validns: Please migrate to openssl1.1 in Buster
Added tag(s) pending.
> tags 897882 pending
Bug #897882 [src:validns] validns: ftbfs with GCC-8
Added tag(s) pending.
> user debian-rele...@lists.debian.org
Setting user to debian-rele...@lists.debian.org (was 
debian.a...@manchmal.in-ulm.de).
> usertags 859784 + bsp-2018-10-de-karlsruhe
There were no usertags set.
Usertags are now: bsp-2018-10-de-karlsruhe.
> usertags 897882 + bsp-2018-10-de-karlsruhe
There were no usertags set.
Usertags are now: bsp-2018-10-de-karlsruhe.
> thanks
Stopping processing here.

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

Processed: severity of 911533 is serious

[Debian Bug Tracking System]

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

> severity 911533 serious
Bug #911533 [gandi-cli] gandi-cli: missing dependencies for python3 setuptools 
and ipy
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

Bug#912047: nullmailer: FTBFS: Test failure

[David Bremner]

Daniel Schepler  writes:

Control: severity -1 important
Control: tag -1 unpreproducible

> Source: nullmailer
> Version: 1:2.1-7
> Severity: serious
> Tags: ftbfs
>
> From my pbuilder build log:

It's not reproducible in for me sbuild. I guess there's something
pbuilder specific about this failer. Of course I'd like a fix, but I'll
need to be convinced it's RC.

cheers,

d

Bug#897882: NMU for validns

[Christoph Biedl]

tags 859784 pending
tags 897882 pending
user debian-rele...@lists.debian.org
usertags 859784 + bsp-2018-10-de-karlsruhe
usertags 897882 + bsp-2018-10-de-karlsruhe
thanks

Dear maintainer,

find attached a debdiff to fix both serious bugs in validns.

Also I've prepared an NMU for validns (versioned as 0.8+git20160720-3.1)
and uploaded it to DELAYED/5. Please feel free to tell me if I should
delay it longer.

Regards,

Christoph
diff -Nru validns-0.8+git20160720/debian/changelog 
validns-0.8+git20160720/debian/changelog
--- validns-0.8+git20160720/debian/changelog2016-12-14 16:01:55.0 
+0100
+++ validns-0.8+git20160720/debian/changelog2018-10-27 18:14:01.0 
+0200
@@ -1,3 +1,11 @@
+validns (0.8+git20160720-3.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Build against openssl 1.1. Closes: #859784
+  * Fix build error with GCC-8. Closes: #897882
+
+ -- Christoph Biedl   Sat, 27 Oct 2018 
18:14:01 +0200
+
 validns (0.8+git20160720-3) unstable; urgency=medium
 
   * debian/copyright Add License: statement.
diff -Nru validns-0.8+git20160720/debian/control 
validns-0.8+git20160720/debian/control
--- validns-0.8+git20160720/debian/control  2016-12-14 16:01:55.0 
+0100
+++ validns-0.8+git20160720/debian/control  2018-10-27 18:09:17.0 
+0200
@@ -3,7 +3,7 @@
 Priority: extra
 Maintainer: Casper Gielen 
 Uploaders: Joost van Baal-Ilić 
-Build-Depends: debhelper (>= 9), libssl1.0-dev, libjudy-dev, 
libtest-command-simple-perl, dpkg-dev (>= 1.16.1~)
+Build-Depends: debhelper (>= 9), libssl-dev, libjudy-dev, 
libtest-command-simple-perl, dpkg-dev (>= 1.16.1~)
 Standards-Version: 3.9.8
 Homepage: http://www.validns.net/
 Vcs-Git: https://anonscm.debian.org/git/collab-maint/validns.git
diff -Nru validns-0.8+git20160720/debian/patches/fix-ftbfs-gcc8.patch 
validns-0.8+git20160720/debian/patches/fix-ftbfs-gcc8.patch
--- validns-0.8+git20160720/debian/patches/fix-ftbfs-gcc8.patch 1970-01-01 
01:00:00.0 +0100
+++ validns-0.8+git20160720/debian/patches/fix-ftbfs-gcc8.patch 2018-10-27 
18:13:35.0 +0200
@@ -0,0 +1,19 @@
+Subject: Fix build error with GCC-8
+Author: Christoph Biedl 
+Date: 2018-10-27
+Bug-Debian: https://bugs.debian.org/897882
+
+--- a/ipseckey.c
 b/ipseckey.c
+@@ -111,8 +111,11 @@
+   default:
+   strcpy(gw, "??");
+   }
++#pragma GCC diagnostic push
++#pragma GCC diagnostic ignored "-Wformat-truncation"
+ snprintf(s, 1024, "( %d %d %d %s ... )",
+rr->precedence, rr->gateway_type, rr->algorithm, gw);
++#pragma GCC diagnostic pop
+ return quickstrdup_temp(s);
+ }
+ 
diff -Nru validns-0.8+git20160720/debian/patches/series 
validns-0.8+git20160720/debian/patches/series
--- validns-0.8+git20160720/debian/patches/series   2016-12-14 
16:01:55.0 +0100
+++ validns-0.8+git20160720/debian/patches/series   2018-10-27 
18:13:35.0 +0200
@@ -1,3 +1,5 @@
 fix-makefile-clean.patch
 fix-dont-overwrite-cflags.patch
 ignoreQuilt.patch
+use-openssl-1.1.patch
+fix-ftbfs-gcc8.patch
diff -Nru validns-0.8+git20160720/debian/patches/use-openssl-1.1.patch 
validns-0.8+git20160720/debian/patches/use-openssl-1.1.patch
--- validns-0.8+git20160720/debian/patches/use-openssl-1.1.patch
1970-01-01 01:00:00.0 +0100
+++ validns-0.8+git20160720/debian/patches/use-openssl-1.1.patch
2018-10-27 18:13:35.0 +0200
@@ -0,0 +1,184 @@
+Subject: Build against openssl 1.1.
+Author: Chris 
+Date: 2018-10-27
+Bug-Debian: https://bugs.debian.org/859784
+
+--- a/dnskey.c
 b/dnskey.c
+@@ -154,6 +154,7 @@
+   unsigned int e_bytes;
+   unsigned char *pk;
+   int l;
++   BIGNUM *n, *e;
+ 
+   rsa = RSA_new();
+   if (!rsa)
+@@ -174,11 +175,12 @@
+   if (l < e_bytes) /* public key is too short */
+   goto done;
+ 
+-  rsa->e = BN_bin2bn(pk, e_bytes, NULL);
++   e = BN_bin2bn(pk, e_bytes, NULL);
+   pk += e_bytes;
+   l -= e_bytes;
+ 
+-  rsa->n = BN_bin2bn(pk, l, NULL);
++   n = BN_bin2bn(pk, l, NULL);
++   RSA_set0_key(rsa, n, e, NULL);
+ 
+   pkey = EVP_PKEY_new();
+   if (!pkey)
+--- a/nsec3checks.c
 b/nsec3checks.c
+@@ -28,7 +28,7 @@
+ static struct binary_data name2hash(char *name, struct rr *param)
+ {
+ struct rr_nsec3param *p = (struct rr_nsec3param *)param;
+-  EVP_MD_CTX ctx;
++   EVP_MD_CTX *ctx;
+   unsigned char md0[EVP_MAX_MD_SIZE];
+   unsigned char md1[EVP_MAX_MD_SIZE];
+   unsigned char *md[2];
+@@ -45,22 +45,23 @@
+ 
+   /* XXX Maybe use Init_ex and Final_ex for speed? */
+ 
+-  EVP_MD_CTX_init();
+-  if (EVP_DigestInit(, EVP_sha1()) != 1)
++   ctx = EVP_MD_CTX_new();
++   if (EVP_DigestInit(ctx, EVP_sha1()) != 1)
+   return r;
+-  digest_size = EVP_MD_CTX_size();
+-  EVP_DigestUpdate(, 

Processed: severity of 911763 is serious

[Debian Bug Tracking System]

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

> severity 911763 serious
Bug #911763 [src:espresso] espresso: FTBFS on ppc64el, armhf, riscv64
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

Processed: found 911898 in 60.3.0esr-1

[Debian Bug Tracking System]

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

> found 911898 60.3.0esr-1
Bug #911898 [firefox-esr] firefox-esr: SIGSEGV on startup on ppc64el
Marked as found in versions firefox-esr/60.3.0esr-1.
> thanks
Stopping processing here.

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

Processed: severity of 911875 is serious

[Debian Bug Tracking System]

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

> severity 911875 serious
Bug #911875 [proftpd-basic] proftpd-basic (mod_sftp) is missing important 
upstream fixes for an OpenSSL API change
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

Processed: severity of 911898 is serious

[Debian Bug Tracking System]

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

> severity 911898 serious
Bug #911898 [firefox-esr] firefox-esr: SIGSEGV on startup on ppc64el
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Processed (with 2 errors): Can't reproduce.

[Debian Bug Tracking System]

Processing control commands:

> user debian-rele...@lists.debian.org
Unknown command or malformed arguments to command.

> usertags -1 + bsp-2018-10-de-karlsruhe
Unknown command or malformed arguments to command.

> tag -1 moreinfo
Bug #906603 [src:joblib] joblib: FTBFS in buster/sid (failing tests)
Added tag(s) moreinfo.
> tag -1 unreproducible
Bug #906603 [src:joblib] joblib: FTBFS in buster/sid (failing tests)
Added tag(s) unreproducible.

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

Bug#906603: Can't reproduce.

[Hilko Bengen]

control: user debian-rele...@lists.debian.org
control: usertags -1 + bsp-2018-10-de-karlsruhe
control: tag -1 moreinfo
control: tag -1 unreproducible

Hi Santiago,

greetings from the BSP in Karlsruhe.

I was going to try if the the FTBFS you reported might have been fixed
in the new upstream version (0.12.5), but I cannot even reproduce it at
all. I have tried 0.12.1-1 (the version you reported against) and
0.12.3-1 (the version currently in unstable) on clean sid-amd64 and
buster-amd64 chroots.

Cheers,
-Hilko

Bug#912056: xdffileio: FTBFS: Test failures

[Daniel Schepler]

Source: xdffileio
Version: 0.3-2
Severity: serious
Tags: ftbfs

>From my pbuilder build log:

...
make  check-TESTS
make[3]: Entering directory '/build/xdffileio-0.3/tests'
make[4]: Entering directory '/build/xdffileio-0.3/tests'
PASS: readcheck
PASS: errorcheck
FAIL: testbdf
PASS: testedf
PASS: testgdf2
FAIL: testgdf1
=
  xdffileio 0.3: tests/test-suite.log
=

# TOTAL: 6
# PASS:  4
# SKIP:  0
# XFAIL: 0
# FAIL:  2
# XPASS: 0
# ERROR: 0

.. contents:: :depth: 2

FAIL: testbdf
=

   Version : xdffileio 0.3
   One of the files cannot be opened
FAIL testbdf (exit status: 1)

FAIL: testgdf1
==

   Version : xdffileio 0.3
   The files are identical
   The files are identical

Cannot create an XDF file: (17) File exists
FAIL testgdf1 (exit status: 1)


Testsuite summary for xdffileio 0.3

# TOTAL: 6
# PASS:  4
# SKIP:  0
# XFAIL: 0
# FAIL:  2
# XPASS: 0
# ERROR: 0

See tests/test-suite.log
Please report to nicolas.burd...@epfl.ch

make[4]: *** [Makefile:918: test-suite.log] Error 1
make[4]: Leaving directory '/build/xdffileio-0.3/tests'
make[3]: *** [Makefile:1026: check-TESTS] Error 2
make[3]: Leaving directory '/build/xdffileio-0.3/tests'
make[2]: *** [Makefile:1135: check-am] Error 2
make[2]: Leaving directory '/build/xdffileio-0.3/tests'
make[1]: *** [Makefile:630: check-recursive] Error 1
make[1]: Leaving directory '/build/xdffileio-0.3'
dh_auto_test: make -j8 check VERBOSE=1 returned exit code 2
make: *** [debian/rules:26: build] Error 2
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2

It looks like reproducible-builds.org also got testsuite errors in
build2, though with somewhat different errors.  So, it looks like
there's probably some race condition in the testsuite that causes
random failures.
-- 
Daniel Schepler

Bug#912054: xapian-omega: FTBFS: can't parse dependency libxapian30 (>= 1.4.7) (>= 1.4.6~)

[Daniel Schepler]

Source: xapian-omega
Version: 1.4.7-1
Severity: serious
Tags: ftbfs

>From my pbuilder build log:

...
dh_makeshlibs
dh_installdeb
dh_shlibdeps
# Rewrite the dependency on libxapianN to be >= our version, since
# we may require features added in that version.
sed -i \
   's/^shlibs:Depends=.*libxapian[0-9][0-9a-z]*/& (>= 1.4.7)/' \
   debian/*.substvars
dh_gencontrol
dpkg-gencontrol: warning: can't parse dependency libxapian30 (>=
1.4.7) (>= 1.4.6~)
dpkg-gencontrol: error: error occurred while parsing Depends field:
libc6 (>= 2.15), libgcc1 (>= 1:3.0), libmagic1 (>= 5.12), libpcre3,
libstdc++6 (>= 5.2), libxapian30 (>= 1.4.7) (>= 1.4.6~), zlib1g (>=
1:1.1.4),
dh_gencontrol: dpkg-gencontrol -pxapian-omega -ldebian/changelog
-Tdebian/xapian-omega.substvars
-Pdebian/.debhelper/xapian-omega/dbgsym-root -UPre-Depends
-URecommends -USuggests -UEnhances -UProvides -UEssential -UConflicts
-DPriority=optional -UHomepage -UImportant
-DAuto-Built-Package=debug-symbols -DPackage=xapian-omega-dbgsym
"-DDepends=xapian-omega (= \${binary:Version})" "-DDescription=debug
symbols for xapian-omega" "-DBuild-Ids=00d9192b
51a1d49fa8968505670baec8e5cfd71b
30db2840f00652052da4c6fc234ffaa78ce204fc
49d4db29d9ae124e69ae7eb91d3cba05a742d51a
b511e8b16c908bf52b66447d9e119e0bbf191207" -DSection=debug -UMulti-Arch
-UReplaces -UBreaks returned exit code
25
dh_gencontrol: Aborting due to earlier error
make: *** [debian/rules:183: binary-arch] Error 25
dpkg-buildpackage: error: fakeroot debian/rules binary subprocess
returned exit status 2

(Also reproducible in the reproducible-builds.org log.)
-- 
Daniel Schepler

Bug#912045: Bug #912045 in mb2md marked as pending

[gregor herrmann]

Control: tag -1 pending

Hello,

Bug #912045 in mb2md reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below, and you can check the diff of the fix at:

https://salsa.debian.org/perl-team/modules/packages/mb2md/commit/970052f7b397111c3b6727307349a0ff3420b51b


Add build dependency on libtimedate-perl.

Thanks: Daniel Schepler for the bug report.
Closes: #912045



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/912045

Processed: Bug #912045 in mb2md marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #912045 [src:mb2md] mb2md: FTBFS: Test failures
Added tag(s) pending.

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

Processed: tagging 912045

[Debian Bug Tracking System]

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

> tags 912045 + buster sid
Bug #912045 [src:mb2md] mb2md: FTBFS: Test failures
Added tag(s) sid and buster.
> thanks
Stopping processing here.

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

Bug#912053: twms: FTBFS: UnicodeDecodeError

[Daniel Schepler]

Source: twms
Version: 0.06y-1
Severity: serious
Tags: ftbfs

>From my pbuilder build log:

...
 fakeroot debian/rules clean
dh clean --with=python3 --with=systemd --buildsystem=pybuild
  dh_auto_clean -O--buildsystem=pybuild
I: pybuild base:217: python3.7 setup.py clean
running clean
removing '/build/twms-0.06y/.pybuild/cpython3_3.7/build' (and
everything under it)
/usr/lib/python3/dist-packages/setuptools/dist.py:407: UserWarning:
The version specified ('0.06y') is an invalid version, this may not
work as expected with newer versions of setuptools, pip, and PyPI.
Please see PEP 440 for
more details.
 "details." % self.metadata.version
'build/bdist.linux-amd64' does not exist -- can't clean it
'build/scripts-3.7' does not exist -- can't clean it
I: pybuild base:217: python3.6 setup.py clean
Traceback (most recent call last):
 File "setup.py", line 48, in 
   long_description = read('README.md'),
 File "setup.py", line 14, in read
   return open(os.path.join(os.path.dirname(__file__), fname)).read()
 File "/usr/lib/python3.6/encodings/ascii.py", line 26, in decode
   return codecs.ascii_decode(input, self.errors)[0]
UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position
86: ordinal not in range(128)
E: pybuild pybuild:338: clean: plugin distutils failed with: exit
code=1: python3.6 setup.py clean
dh_auto_clean: pybuild --clean -i python{version} -p "3.7 3.6"
returned exit code 13
make: *** [debian/rules:3: clean] Error 25
dpkg-buildpackage: error: fakeroot debian/rules clean subprocess
returned exit status 2

(Also reproducible in the reproducible-builds.org log.)
-- 
Daniel Schepler

Processed: Bug #912039 in libpetal-utils-perl marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #912039 [src:libpetal-utils-perl] libpetail-utils-perl: FTBFS: Test failures
Added tag(s) pending.

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

Bug#912039: Bug #912039 in libpetal-utils-perl marked as pending

[gregor herrmann]

Control: tag -1 pending

Hello,

Bug #912039 in libpetal-utils-perl reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below, and you can check the diff of the fix at:

https://salsa.debian.org/perl-team/modules/packages/libpetal-utils-perl/commit/d17912d415c6963439f389cc106f32e3251c6724


Add build dependency on libtimedate-perl.

Thanks: Daniel Schepler for the bug report.
Closes: #912039



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/912039

Bug#912052: sslsplit: FTBFS: Failure in test -r session.pem

[Daniel Schepler]

Source: sslsplit
Version: 0.5.3-1
Severity: serious
Tags: ftbfs

>From my pbuilder build log:

...
make -C extra/pki testreqs session
make[2]: Entering directory '/build/sslsplit-0.5.3/extra/pki'
openssl genrsa -out rsa.key 2048
openssl genrsa -out server.key 2048
Generating RSA private key, 2048 bit long modulus (2 primes)
Generating RSA private key, 2048 bit long modulus (2 primes)
.
+
+++
+.+
+.
.e is 65537 (0x010001)
openssl req -new -nodes -x509 -sha256 -out server.crt -key server.key \
   -config x509v3ca.cnf -extensions v3_crt \
   -subj '/C=CH/O=SSLsplit Test Certificate/CN=daniel.roe.ch/' \
   -set_serial 42 -days 365
cat server.crt server.key >server.pem
openssl s_server -accept 46143 -cert server.pem -quiet  & \
   pid=$! ; \
   sleep 1 ; \
   echo q | openssl s_client -connect localhost:46143 \
   -quiet -no_ign_eof -sess_out session.pem ; \
   kill $pid
+
e is 65537 (0x010001)
openssl req -new -nodes -x509 -sha256 -out rsa.crt -key rsa.key \
   -config x509v3ca.cnf -extensions v3_ca \
   -subj '/C=CH/O=SSLsplit Root CA/CN=SSLsplit Root CA/' \
   -set_serial 1 -days 3650
cat rsa.crt rsa.key >rsa.pem
mkdir -p targets
mkdir -p targets
openssl genrsa -out targets/daniel.roe.ch.key 2048
openssl genrsa -out targets/wildcard.roe.ch.key 2048
Generating RSA private key, 2048 bit long modulus (2 primes)
Generating RSA private key, 2048 bit long modulus (2 primes)
..++.++.+
..+.++.++
...++.++.+
e is 65537 (0x010001)
openssl req -new -sha256 -subj '/C=CH/CN=*.roe.ch/' \
   -key targets/wildcard.roe.ch.key \
   -out targets/wildcard.roe.ch.csr
..Can't load /nonexistent/.rnd into RNG
139907575923136:error:2406F079:random number
generator:RAND_load_file:Cannot open
file:../crypto/rand/randfile.c:88:Filename=/nonexistent/.rnd
...openssl x509 -req -sha256 -CAcreateserial -days 365 \
   -CA rsa.crt -CAkey rsa.key \
   -in targets/wildcard.roe.ch.csr \
   -out targets/wildcard.roe.ch.crt
..Signature ok
subject=C = CH, CN = *.roe.ch
Getting CA Private Key
..cat targets/wildcard.roe.ch.crt targets/wildcard.roe.ch.key rsa.crt \
   >targets/wildcard.roe.ch.pem
.rm -f targets/wildcard.roe.ch.key targets/wildcard.roe.ch.csr \
   targets/wildcard.roe.ch.crt
+
e is 65537 (0x010001)
openssl req -new -sha256 -subj '/C=CH/CN=daniel.roe.ch/' \
   -key targets/daniel.roe.ch.key \
   -out targets/daniel.roe.ch.csr
Can't load /nonexistent/.rnd into RNG
140554678874560:error:2406F079:random number
generator:RAND_load_file:Cannot open
file:../crypto/rand/randfile.c:88:Filename=/nonexistent/.rnd
openssl x509 -req -sha256 -CAcreateserial -days 365 \
   -CA rsa.crt -CAkey rsa.key \
   -in targets/daniel.roe.ch.csr \
   -out targets/daniel.roe.ch.crt
Signature ok
subject=C = CH, CN = daniel.roe.ch
Getting CA Private Key
cat targets/daniel.roe.ch.crt targets/daniel.roe.ch.key rsa.crt \
   >targets/daniel.roe.ch.pem
rm -f targets/daniel.roe.ch.key targets/daniel.roe.ch.csr \
   targets/daniel.roe.ch.crt
rm -f rsa.srl
depth=0 C = CH, O = SSLsplit Test Certificate, CN = daniel.roe.ch
verify error:num=18:self signed certificate
verify return:1
depth=0 C = CH, O = SSLsplit Test Certificate, CN = daniel.roe.ch
verify return:1
DONE
test -r session.pem
make[2]: *** [GNUmakefile:117: session.pem] Error 1
make[2]: Leaving directory '/build/sslsplit-0.5.3/extra/pki'
make[1]: *** [GNUmakefile:410: test] Error 2
make[1]: Leaving directory '/build/sslsplit-0.5.3'
dh_auto_test: make -j8 test returned exit code 2
make: *** [debian/rules:13: build] Error 2
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2

(Also reproducible in the reproducible-builds.org log.)
-- 
Daniel Schepler

Bug#912051: rsyncrypto: FTBFS: aclocal-1.15: command not found

[Daniel Schepler]

Source: rsyncrypto
Version: 1.14-1
Severity: serious

>From my pbuilder build log:

...
   dh_auto_build
   make -j1
make[1]: Entering directory '/build/rsyncrypto-1.14'
CDPATH="${ZSH_VERSION+.}:" && cd . && /bin/bash
/build/rsyncrypto-1.14/missing aclocal-1.15
/build/rsyncrypto-1.14/missing: line 81: aclocal-1.15: command not found
WARNING: 'aclocal-1.15' is missing on your system.
You should only need it if you modified 'acinclude.m4' or
'configure.ac' or m4 files included by 'configure.ac'.
The 'aclocal' program is part of the GNU Automake package:

It also requires GNU Autoconf, GNU m4 and Perl in order to run:



make[1]: *** [Makefile:361: aclocal.m4] Error 127
make[1]: Leaving directory '/build/rsyncrypto-1.14'
dh_auto_build: make -j1 returned exit code 2
make: *** [debian/rules:19: build] Error 2
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2

(Also reproducible in the reproducible-builds.org log.)
-- 
Daniel Schepler

Bug#912050: bzr build depends on the removed python-lzma-dbg

[Adrian Bunk]

Source: bzr
Version: 2.7.0+bzr6622-13
Severity: serious
Tags: ftbfs

The following packages have unmet dependencies:
 builddeps:bzr : Depends: python-lzma-dbg but it is not going to be installed

Bug#912048: obs-build: FTBFS: Test failures

[Daniel Schepler]

Source: obs-build
Version: 20180831-1
Severity: serious
Tags: ftbfs

>From my pbuilder build log:

...
   dh_auto_test
   make -j1 test
make[1]: Entering directory '/build/obs-build-20180831'
PERL5LIB=. prove -v
Can't locate Date/Parse.pm in @INC (you may need to install the
Date::Parse module) (@INC contains: /usr/lib/build . /etc/perl
/usr/local/lib/x86_64-linux-gnu/perl/5.26.2
/usr/local/share/perl/5.26.2 /usr/lib/x86_64-linux-gnu
/perl5/5.26 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.26
/usr/share/perl/5.26 /usr/local/lib/site_perl
/usr/lib/x86_64-linux-gnu/perl-base .) at ./changelog2spec line 31.
BEGIN failed--compilation aborted at ./changelog2spec line 31.

#   Failed test 'changelog2spec --selftest rpm python-rpm.changes rpm.changes'
#   at t/changelog2spec.t line 10.
#  got: ''
# expected: 'rpm.changes'
Can't locate Date/Parse.pm in @INC (you may need to install the
Date::Parse module) (@INC contains: /usr/lib/build . /etc/perl
/usr/local/lib/x86_64-linux-gnu/perl/5.26.2
/usr/local/share/perl/5.26.2 /usr/lib/x86_64-linux-gnu
/perl5/5.26 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.26
/usr/share/perl/5.26 /usr/local/lib/site_perl
/usr/lib/x86_64-linux-gnu/perl-base .) at ./changelog2spec line 31.
BEGIN failed--compilation aborted at ./changelog2spec line 31.

#   Failed test 'changelog2spec --selftest python-rpm
python-rpm.changes rpm.changes'
#   at t/changelog2spec.t line 10.
#  got: ''
# expected: 'python-rpm.changes'
Can't locate Date/Parse.pm in @INC (you may need to install the
Date::Parse module) (@INC contains: /usr/lib/build . /etc/perl
/usr/local/lib/x86_64-linux-gnu/perl/5.26.2
/usr/local/share/perl/5.26.2 /usr/lib/x86_64-linux-gnu
/perl5/5.26 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.26
/usr/share/perl/5.26 /usr/local/lib/site_perl
/usr/lib/x86_64-linux-gnu/perl-base .) at ./changelog2spec line 31.
BEGIN failed--compilation aborted at ./changelog2spec line 31.

#   Failed test 'changelog2spec --selftest antlr antlr.changes
antlr-bootstrap.changes'
#   at t/changelog2spec.t line 10.
#  got: ''
# expected: 'antlr.changes'
Can't locate Date/Parse.pm in @INC (you may need to install the
Date::Parse module) (@INC contains: /usr/lib/build . /etc/perl
/usr/local/lib/x86_64-linux-gnu/perl/5.26.2
/usr/local/share/perl/5.26.2 /usr/lib/x86_64-linux-gnu
/perl5/5.26 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.26
/usr/share/perl/5.26 /usr/local/lib/site_perl
/usr/lib/x86_64-linux-gnu/perl-base .) at ./changelog2spec line 31.
BEGIN failed--compilation aborted at ./changelog2spec line 31.

#   Failed test 'changelog2spec --selftest antlr anyunrelated.changes'
#   at t/changelog2spec.t line 10.
#  got: ''
# expected: 'anyunrelated.changes'
Can't locate Date/Parse.pm in @INC (you may need to install the
Date::Parse module) (@INC contains: /usr/lib/build . /etc/perl
/usr/local/lib/x86_64-linux-gnu/perl/5.26.2
/usr/local/share/perl/5.26.2 /usr/lib/x86_64-linux-gnu
/perl5/5.26 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.26
/usr/share/perl/5.26 /usr/local/lib/site_perl
/usr/lib/x86_64-linux-gnu/perl-base .) at ./changelog2spec line 31.
BEGIN failed--compilation aborted at ./changelog2spec line 31.

#   Failed test 'changelog2spec --selftest antlr-bootstrap
antlr.changes antlr-bootstrap.changes'
#   at t/changelog2spec.t line 10.
#  got: ''
# expected: 'antlr-bootstrap.changes'
Can't locate Date/Parse.pm in @INC (you may need to install the
Date::Parse module) (@INC contains: /usr/lib/build . /etc/perl
/usr/local/lib/x86_64-linux-gnu/perl/5.26.2
/usr/local/share/perl/5.26.2 /usr/lib/x86_64-linux-gnu
/perl5/5.26 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.26
/usr/share/perl/5.26 /usr/local/lib/site_perl
/usr/lib/x86_64-linux-gnu/perl-base .) at ./changelog2spec line 31.
BEGIN failed--compilation aborted at ./changelog2spec line 31.

#   Failed test 'changelog2spec --selftest antlr-bootstrap antlr.changes'
#   at t/changelog2spec.t line 10.
#  got: ''
# expected: 'antlr.changes'
Can't locate Date/Parse.pm in @INC (you may need to install the
Date::Parse module) (@INC contains: /usr/lib/build . /etc/perl
/usr/local/lib/x86_64-linux-gnu/perl/5.26.2
/usr/local/share/perl/5.26.2 /usr/lib/x86_64-linux-gnu
/perl5/5.26 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.26
/usr/share/perl/5.26 /usr/local/lib/site_perl
/usr/lib/x86_64-linux-gnu/perl-base .) at ./changelog2spec line 31.
BEGIN failed--compilation aborted at ./changelog2spec line 31.

#   Failed test 'changelog2spec --selftest antlr-bootstrap
antlr.changes antlr-other.changes'
#   at t/changelog2spec.t line 10.
#  got: ''
# expected: 'antlr.changes'
Can't locate Date/Parse.pm in @INC (you may need to install the
Date::Parse module) (@INC contains: /usr/lib/build . /etc/perl
/usr/local/lib/x86_64-linux-gnu/perl/5.26.2
/usr/local/share/perl/5.26.2 /usr/lib/x86_64-linux-gnu
/perl5/5.26 /usr/share/perl5 

Bug#912038: closed by Bastian Blank (Re: Bug#912038: grub-cloud-amd64: fails to install)

[Holger Levsen]

reopen 912038
thanks

On Sat, Oct 27, 2018 at 03:33:07PM +, Debian Bug Tracking System wrote:
> Date: Sat, 27 Oct 2018 17:24:19 +0200
> From: Bastian Blank 
> To: 912038-d...@bugs.debian.org
> Subject: Re: Bug#912038: grub-cloud-amd64: fails to install
> User-Agent: NeoMutt/20170113 (1.7.2)
> 
> Hi
> 
> On Sat, Oct 27, 2018 at 05:13:52PM +0200, Holger Levsen wrote:
> > during a test in a schroot I noticed your package failed to install. As
> > per definition of the release team this makes the package too buggy for
> > a release, thus the severity.
> Which one?
 
https://release.debian.org/buster/rc_policy.txt

5. General

  (a) Supportable

Packages in the archive must not be so buggy or out of date that
we refuse to support them.



This package is too buggy. We expect all packages to install fine under
all circumstances.


> Anyway, it is the purpose of this package to work in specific
> environment only, so I'm closing this.  Please read the description.

you said so before, and yet its wrong. I also tried to explain what you
do instead, but you didnt listen, so I filed #912041 and described there
what you should do instead.

Please don't close this bug again, unless you coordinated with
debian-release that they suddenly want such buggy packages in the
release.


-- 
cheers,
Holger

---
   holger@(debian|reproducible-builds|layer-acht).org
   PGP fingerprint: B8BF 5413 7B09 D35C F026 FE9D 091A B856 069A AA1C


signature.asc
Description: PGP signature

Bug#912047: nullmailer: FTBFS: Test failure

[Daniel Schepler]

Source: nullmailer
Version: 1:2.1-7
Severity: serious
Tags: ftbfs

>From my pbuilder build log:

...
Making check in test
make[2]: Entering directory '/build/nullmailer-2.1/test'
./address-test
42 tests run, 0 failed.
./argparse-test
14 tests run, 0 failed.
sh ./clitest.sh
All tests passed.
./runtests `find /build/nullmailer-2.1/test/tests -type f -not -name '.*'`
Running test /build/nullmailer-2.1/test/tests/inject/from_...
Checking that inject ignores a leading "From " line
Checking that inject ignores a leading ">From " line
Done.
Running test /build/nullmailer-2.1/test/tests/inject/recips...
Checking that inject uses command line with -a.
Checking that inject ignores header lines with -a.
Checking that inject uses command line with -b.
Checking that inject uses header lines with -b.
Checking that inject ignores command line with -h.
Checking that inject uses header lines with -h.
Checking that inject uses command line with -e and no header.
Checking that inject uses command line with -e and header.
Checking that inject uses header with -e and no command line.
Checking that inject ignores header with -e and command line.
Checking that inject uses command line with no header by default.
Checking that inject uses command line with header by default.
Checking that inject uses header with no command line by default.
Checking that inject ignores header with command line by default.
Done.
Running test /build/nullmailer-2.1/test/tests/inject/from...
Checking that inject inserts a from line.
Checking that inject preserves an existing from line.
Checking that inject does not add more from lines.
Checking that inject will strip from lines.
Checking that inject obeys me
Checking that inject obeys config/defaulthost
Checking that inject obeys config/defaultdomain
Checking that inject ignores config/defaultdomain for localhost
Checking that inject obeys HOSTNAME.
Checking that inject obeys MAILHOST.
Checking that inject obeys NULLMAILER_HOST.
Checking that inject uses getpwnam
Checking that inject obeys LOGNAME.
Checking that inject obeys USER.
Checking that inject obeys MAILUSER.
Checking that inject obeys NULLMAILER_USER.
Checking that inject uses a blank name.
Checking that inject obeys NAME.
Checking that inject obeys MAILNAME.
Checking that inject obeys NULLMAILER_NAME.
Checking that inject will use address-comment form.
Done.
Running test /build/nullmailer-2.1/test/tests/inject/return-path...
Checking that inject does not inserts a return-path.
Checking that inject strips return-paths.
Done.
Running test /build/nullmailer-2.1/test/tests/inject/message-id...
Checking that inject inserts a message-id.
Checking that inject preserves an existing message-id.
Checking that inject does not add more message-ids.
Checking that inject will ignore an existing message-id.
Checking that inject obeys me
Checking that inject obeys config/idhost
Done.
Running test /build/nullmailer-2.1/test/tests/inject/date...
Checking that inject inserts a date line.
Checking that inject preserves an existing date line.
Checking that inject does not add more date lines.
Done.
Running test /build/nullmailer-2.1/test/tests/inject/sender...
Checking that inject obeys me
Checking that inject obeys config/defaulthost
Checking that inject obeys config/defaultdomain
Checking that inject ignores config/defaultdomain for localhost
Checking that inject obeys HOSTNAME.
Checking that inject canonicalizes HOSTNAME.
Checking that inject obeys MAILHOST.
Checking that inject canonicalizes MAILHOST.
Checking that inject obeys NULLMAILER_HOST.
Checking that inject canonicalizes NULLMAILER_HOST.
Checking that inject uses getpwnam
Checking that inject obeys LOGNAME.
Checking that inject obeys USER.
Checking that inject obeys MAILUSER.
Checking that inject obeys NULLMAILER_USER.
Checking that inject ignores Errors-To:
Checking that inject ignores From:
Checking that inject ignores Reply-To:
Checking that inject ignores Resent-From:
Checking that inject ignores Resent-Reply-To:
Checking that inject ignores Resent-Sender:
Checking that inject ignores Return-Receipt-To:
Checking that inject ignores Sender:
Checking that inject uses Return-Path:
Checking that inject ignores Return-Path:
Checking that inject honors -f ''
Checking that inject honors -f '<>'
Checking that inject honors -f 'a@b.c'
Checking that inject honors -f ''
Checking that inject honors -f 'a@b'
Checking that inject honors -f ''
Done.
Running test /build/nullmailer-2.1/test/tests/inject/queue...
Testing that inject queues messages properly.
Testing that inject honors $NULLMAILER_QUEUE.
Done.
Running test /build/nullmailer-2.1/test/tests/inject/bad-headers...
Checking that inject rejects leading continuation lines.
No recipients were listed.
Checking that inject rejects malformed RFC headers.
No recipients were listed.
No recipients were listed.
No recipients were listed.
Checking that inject rejects bad addresses.
nullmailer-inject: Invalid header line:
 from: foo to 
Testing queue from <@b.c> to 

Processed: Re: Bug#912038 closed by Bastian Blank (Re: Bug#912038: grub-cloud-amd64: fails to install)

[Debian Bug Tracking System]

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

> reopen 912038
Bug #912038 {Done: Bastian Blank } [grub-cloud-amd64] 
grub-cloud-amd64: fails to install
Bug reopened
Ignoring request to alter fixed versions of bug #912038 to the same values 
previously set
> thanks
Stopping processing here.

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

Bug#912046: debsums: Error: symlink loop detected in path 'sbin/ebtables'.

[Laurent Bigonville]

Package: ebtables
Version: 2.0.10.4-5
Severity: serious

Hi,

When running debsums -ac, it complains that:

debsums: Error: symlink loop detected in path 'sbin/ebtables'. Please file a 
bug against ebtables.

So here is the bug report.

Laurent Bigonville

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

Kernel: Linux 4.18.0-2-amd64 (SMP w/8 CPU cores)
Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_BE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: SELinux: enabled - Mode: Permissive - Policy name: refpolicy

Versions of packages ebtables depends on:
ii  libc6  2.27-6

Versions of packages ebtables recommends:
ii  iptables  1.8.1-2
ii  kmod  25-1

ebtables suggests no packages.

-- no debconf information

-- debsums errors found:
debsums: Error: symlink loop detected in path 'sbin/ebtables'. Please file a 
bug against ebtables.

Bug#912045: mb2md: FTBFS: Test failures

[Daniel Schepler]

Source: mb2md
Version: 3.20-8
Severity: serious
Tags: ftbfs

>From my pbuilder build log:

...
   debian/rules override_dh_auto_test
make[1]: Entering directory '/build/mb2md-3.20'
debian/tests/run-testsuite.sh perl `pwd`/mb2md-3.20.pl

#   Failed test 'Check return from 'perl
/build/mb2md-3.20/mb2md-3.20.pl -s example.mbox -d example.maildir' is
0'
#   at debian/tests/t/mb2md.t line 35.
#  got: '2'
# expected: '0'

#   Failed test 'Stdout as expected ($HOME)'
#   at debian/tests/t/mb2md.t line 36.
#  got: ''
# expected: 'Converting /tmp/TTcKFt21wi/home/example.mbox to
maildir: /tmp/TTcKFt21wi/home/example.maildir
# Source Mbox is /tmp/TTcKFt21wi/home/example.mbox
# Target Maildir is /tmp/TTcKFt21wi/home/example.maildir
# 2 messages.
#
# '

#   Failed test 'No stderr ($HOME)'
#   at debian/tests/t/mb2md.t line 37.
#  got: 'Can't locate Date/Parse.pm in @INC (you may need to
install the Date::Parse module) (@INC contains: /etc/perl
/usr/local/lib/x86_64-linux-gnu/perl/5.26.2
/usr/local/share/perl/5.26.2 /usr/lib/x86_64-linux-gnu
/perl5/5.26 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.26
/usr/share/perl/5.26 /usr/local/lib/site_perl
/usr/lib/x86_64-linux-gnu/perl-base .) at
/build/mb2md-3.20/mb2md-3.20.pl line 385.
# BEGIN failed--compilation aborted at /build/mb2md-3.20/mb2md-3.20.pl line 385.
# '
# expected: ''
Error opendir on '/tmp/TTcKFt21wi/home/example.maildir/cur': No such
file or directory at debian/tests/t/mb2md.t line 38.
# Tests were run but no plan was declared and done_testing() was not seen.
# Looks like your test exited with 2 just after 11.
debian/tests/t/mb2md.t ..
ok 1 - Created '/tmp/TTcKFt21wi/home'
ok 2 - Successfully copied example.mbox to fake home directory
/tmp/TTcKFt21wi/home/
ok 3 - Created '/tmp/TTcKFt21wi/1'
ok 4 - Successfully copied example.mbox to fake home directory
/tmp/TTcKFt21wi/1/
ok 5 - Created '/tmp/TTcKFt21wi/2'
ok 6 - Successfully copied example.mbox to fake home directory
/tmp/TTcKFt21wi/2/
ok 7 - Can run 'perl /build/mb2md-3.20/mb2md-3.20.pl -s example.mbox
-d example.maildir'
ok 8 - Process terminated without a signal
not ok 9 - Check return from 'perl /build/mb2md-3.20/mb2md-3.20.pl -s
example.mbox -d example.maildir' is 0
not ok 10 - Stdout as expected ($HOME)
not ok 11 - No stderr ($HOME)
Dubious, test returned 2 (wstat 512, 0x200)
Failed 3/11 subtests

Test Summary Report
---
debian/tests/t/mb2md.t (Wstat: 512 Tests: 11 Failed: 3)
 Failed tests:  9-11
 Non-zero exit status: 2
 Parse errors: No plan found in TAP output
Files=1, Tests=11,  1 wallclock secs ( 0.02 usr  0.01 sys +  0.08 cusr
 0.01 csys =  0.12 CPU)
Result: FAIL
make[1]: *** [debian/rules:12: override_dh_auto_test] Error 1
make[1]: Leaving directory '/build/mb2md-3.20'
make: *** [debian/rules:6: build] Error 2
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2

(Also reproducible in the reproducible-builds.org log.)
-- 
Daniel Schepler

Bug#912044: libterm-readline-ttytter-perl: FTBFS: Testsuite hangs

[Daniel Schepler]

Source: libterm-readline-ttytter-perl
Version: 1.4-2
Severity: serious
Tags: ftbfs

>From my pbuilder build log:

...
   dh_auto_test
   make -j8 test TEST_VERBOSE=1
make[1]: Entering directory '/build/libterm-readline-ttytter-perl-1.4'
PERL_DL_NONLAZY=1 "/usr/bin/perl" "-Iblib/lib" "-Iblib/arch" test.pl
Operator or semicolon missing before &__LEAF at (eval 63) line 1.
at (eval 63) line 1.
   eval 'sub __THROW () { &__attribute__ (( &__nothrow__
&__LEAF));}' called at
/usr/lib/x86_64-linux-gnu/perl/5.26/sys/cdefs.ph line 24
   require sys/cdefs.ph called at
/usr/lib/x86_64-linux-gnu/perl/5.26/features.ph line 229
   require features.ph called at
/usr/lib/x86_64-linux-gnu/perl/5.26/sys/ioctl.ph line 7
   require sys/ioctl.ph called at
blib/lib/Term/ReadLine/readline_ttytter.pm line 513
   eval {...} called at blib/lib/Term/ReadLine/readline_ttytter.pm line 513
   readline_ttytter::preinit called at
blib/lib/Term/ReadLine/readline_ttytter.pm line 222
   require Term/ReadLine/readline_ttytter.pm called at
blib/lib/Term/ReadLine/TTYtter.pm line 53
   eval {...} called at blib/lib/Term/ReadLine/TTYtter.pm line 53
   Term::ReadLine::TTYtter::new("Term::ReadLine", "Simple Perl
calc") called at test.pl line 20
Ambiguous use of & resolved as operator & at (eval 63) line 1.
at (eval 63) line 1.
   eval 'sub __THROW () { &__attribute__ (( &__nothrow__
&__LEAF));}' called at
/usr/lib/x86_64-linux-gnu/perl/5.26/sys/cdefs.ph line 24
   require sys/cdefs.ph called at
/usr/lib/x86_64-linux-gnu/perl/5.26/features.ph line 229
   require features.ph called at
/usr/lib/x86_64-linux-gnu/perl/5.26/sys/ioctl.ph line 7
   require sys/ioctl.ph called at
blib/lib/Term/ReadLine/readline_ttytter.pm line 513
   eval {...} called at blib/lib/Term/ReadLine/readline_ttytter.pm line 513
   readline_ttytter::preinit called at
blib/lib/Term/ReadLine/readline_ttytter.pm line 222
   require Term/ReadLine/readline_ttytter.pm called at
blib/lib/Term/ReadLine/TTYtter.pm line 53
   eval {...} called at blib/lib/Term/ReadLine/TTYtter.pm line 53
   Term::ReadLine::TTYtter::new("Term::ReadLine", "Simple Perl
calc") called at test.pl line 20
Operator or semicolon missing before &__inline at (eval 116) line 1.
at (eval 116) line 1.
   eval 'sub __extern_inline () {   &__inline
&__attribute__ (( &__gnu_inline__));}' called at
/usr/lib/x86_64-linux-gnu/perl/5.26/sys/cdefs.ph line 299
   require sys/cdefs.ph called at
/usr/lib/x86_64-linux-gnu/perl/5.26/features.ph line 229
   require features.ph called at
/usr/lib/x86_64-linux-gnu/perl/5.26/sys/ioctl.ph line 7
   require sys/ioctl.ph called at
blib/lib/Term/ReadLine/readline_ttytter.pm line 513
   eval {...} called at blib/lib/Term/ReadLine/readline_ttytter.pm line 513
   readline_ttytter::preinit called at
blib/lib/Term/ReadLine/readline_ttytter.pm line 222
   require Term/ReadLine/readline_ttytter.pm called at
blib/lib/Term/ReadLine/TTYtter.pm line 53
   eval {...} called at blib/lib/Term/ReadLine/TTYtter.pm line 53
   Term::ReadLine::TTYtter::new("Term::ReadLine", "Simple Perl
calc") called at test.pl line 20
Ambiguous use of & resolved as operator & at (eval 116) line 1.
at (eval 116) line 1.
   eval 'sub __extern_inline () {   &__inline
&__attribute__ (( &__gnu_inline__));}' called at
/usr/lib/x86_64-linux-gnu/perl/5.26/sys/cdefs.ph line 299
   require sys/cdefs.ph called at
/usr/lib/x86_64-linux-gnu/perl/5.26/features.ph line 229
   require features.ph called at
/usr/lib/x86_64-linux-gnu/perl/5.26/sys/ioctl.ph line 7
   require sys/ioctl.ph called at
blib/lib/Term/ReadLine/readline_ttytter.pm line 513
   eval {...} called at blib/lib/Term/ReadLine/readline_ttytter.pm line 513
   readline_ttytter::preinit called at
blib/lib/Term/ReadLine/readline_ttytter.pm line 222
   require Term/ReadLine/readline_ttytter.pm called at
blib/lib/Term/ReadLine/TTYtter.pm line 53
   eval {...} called at blib/lib/Term/ReadLine/TTYtter.pm line 53
   Term::ReadLine::TTYtter::new("Term::ReadLine", "Simple Perl
calc") called at test.pl line 20
Features present: minline 1 attribs 1 canSetTopHistory 1 getHistory 1
setHistory 1 newTTY 1 canHookUseAnsi 1 ornaments 1 canRepaint 1
canBackgroundSignal 1 canRemoveReadline 1 addHistory 1
canHookNoCounter 1 appname 1 tkRunni
ng 1 autohistory 1 preput 1

 Flipping rl_default_selected each line.

   Hint: Entering the word
   exit
   would exit the test. ;-)  (If feature 'preput' is present,
   this word should be already entered.)

Can't ioctl TIOCGETP: Inappropriate ioctl for device
Consider installing Term::ReadKey from CPAN site nearby
   at http://www.perl.com/CPAN
Or use
   perl -MCPAN -e shell
to reach CPAN. Falling back to 'stty'.
   If you do not want to see this warning, set PERL_READLINE_NOWARN
in your environment.
at blib/lib/Term/ReadLine/readline_ttytter.pm line 1815.
   

Bug#912038: marked as done (grub-cloud-amd64: fails to install)

[Debian Bug Tracking System]

Your message dated Sat, 27 Oct 2018 17:24:19 +0200
with message-id <20181027152419.7hvrxfyu2so2g...@shell.thinkmo.de>
and subject line Re: Bug#912038: grub-cloud-amd64: fails to install
has caused the Debian Bug report #912038,
regarding grub-cloud-amd64: fails to install
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.)


-- 
912038: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912038
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: grub-cloud-amd64
Version: 0.0.2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test in a schroot I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.

~$ sudo schroot apt install grub-cloud-amd64
Reading package lists... Done
Building dependency tree   
Reading state information... Done
The following additional packages will be installed:
  efibootmgr grub-efi-amd64-bin grub-efi-amd64-signed grub-pc-bin libefiboot1 
libefivar1
The following NEW packages will be installed:
  efibootmgr grub-cloud-amd64 grub-efi-amd64-bin grub-efi-amd64-signed 
grub-pc-bin libefiboot1 libefivar1
0 upgraded, 7 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/1969 kB of archives.
After this operation, 12.8 MB of additional disk space will be used.
Do you want to continue? [Y/n] 
E: Can not write log (Is /dev/pts mounted?) - posix_openpt (2: No such file or 
directory)
Selecting previously unselected package libefivar1:amd64.
(Reading database ... 293476 files and directories currently installed.)
Preparing to unpack .../0-libefivar1_34-1_amd64.deb ...
Unpacking libefivar1:amd64 (34-1) ...
Selecting previously unselected package libefiboot1:amd64.
Preparing to unpack .../1-libefiboot1_34-1_amd64.deb ...
Unpacking libefiboot1:amd64 (34-1) ...
Selecting previously unselected package efibootmgr.
Preparing to unpack .../2-efibootmgr_15-1_amd64.deb ...
Unpacking efibootmgr (15-1) ...
Selecting previously unselected package grub-efi-amd64-bin.
Preparing to unpack .../3-grub-efi-amd64-bin_2.02+dfsg1-6_amd64.deb ...
Unpacking grub-efi-amd64-bin (2.02+dfsg1-6) ...
Selecting previously unselected package grub-pc-bin.
Preparing to unpack .../4-grub-pc-bin_2.02+dfsg1-6_amd64.deb ...
Unpacking grub-pc-bin (2.02+dfsg1-6) ...
Selecting previously unselected package grub-cloud-amd64.
Preparing to unpack .../5-grub-cloud-amd64_0.0.2_amd64.deb ...
Unpacking grub-cloud-amd64 (0.0.2) ...
Selecting previously unselected package grub-efi-amd64-signed.
Preparing to unpack .../6-grub-efi-amd64-signed_1+2.02+dfsg1+6_amd64.deb ...
Unpacking grub-efi-amd64-signed (1+2.02+dfsg1+6) ...
Setting up grub-pc-bin (2.02+dfsg1-6) ...
Setting up libefivar1:amd64 (34-1) ...
Setting up grub-efi-amd64-signed (1+2.02+dfsg1+6) ...
Processing triggers for libc-bin (2.27-6) ...
Setting up libefiboot1:amd64 (34-1) ...
Processing triggers for man-db (2.8.4-2+b1) ...
Setting up efibootmgr (15-1) ...
Setting up grub-efi-amd64-bin (2.02+dfsg1-6) ...
Setting up grub-cloud-amd64 (0.0.2) ...
grub-probe: error: cannot find a device for /boot/ (is /dev mounted?).
Installing for i386-pc platform.
grub-install: error: cannot find a device for /boot/grub (is /dev mounted?).
dpkg: error processing package grub-cloud-amd64 (--configure):
 installed grub-cloud-amd64 package post-installation script subprocess 
returned error exit status 1
Processing triggers for libc-bin (2.27-6) ...
Errors were encountered while processing:
 grub-cloud-amd64
E: Sub-process /usr/bin/dpkg returned an error code (1)
~$ 


-- 
cheers,
Holger

---
   holger@(debian|reproducible-builds|layer-acht).org
   PGP fingerprint: B8BF 5413 7B09 D35C F026 FE9D 091A B856 069A AA1C


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Hi

On Sat, Oct 27, 2018 at 05:13:52PM +0200, Holger Levsen wrote:
> Package: grub-cloud-amd64
> Version: 0.0.2
> Severity: serious
> User: debian...@lists.debian.org
> Usertags: piuparts

This tag is wrong, no piuparts was used.

> during a test in a schroot I noticed your package failed to install. As
> per definition of the release team this makes the package too buggy for
> a release, thus the severity.

Which one?

Anyway, it is the purpose of this package to work in specific
environment only, so I'm closing this.  Please read the description.

Bastian

-- 
It is necessary to have purpose.
-- Alice #1, "I, Mudd", stardate 4513.3--- End