Bug#917496: marked as done (keyrings.alt: FTBFS ('module' object has no attribute 'ResourceNotFoundError'))

[Debian Bug Tracking System]

Your message dated Fri, 28 Dec 2018 07:19:23 +
with message-id 
and subject line Bug#917496: fixed in keyrings.alt 3.1.1-1
has caused the Debian Bug report #917496,
regarding keyrings.alt: FTBFS ('module' object has no attribute 
'ResourceNotFoundError')
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.)


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

Dear maintainer:

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


[...]
 debian/rules build-indep
dh build-indep --with python2,python3 --buildsystem pybuild
   dh_update_autotools_config -i -O--buildsystem=pybuild
   dh_autoreconf -i -O--buildsystem=pybuild
   dh_auto_configure -i -O--buildsystem=pybuild
I: pybuild base:217: python2.7 setup.py config 
running config
I: pybuild base:217: python3.7 setup.py config 
running config
   dh_auto_build -i -O--buildsystem=pybuild
I: pybuild base:217: /usr/bin/python setup.py build 
running build
running build_py
creating /<>/.pybuild/cpython2_2.7_keyrings.alt/build/keyrings

[... snipped ...]

service = random_string(20, UNICODE_CHARS)
>   self.check_set_get(service, username, password)

/usr/lib/python2.7/dist-packages/keyring/tests/test_backend.py:113: 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
/usr/lib/python2.7/dist-packages/keyring/tests/test_backend.py:60: in 
check_set_get
assert keyring.get_password(service, username) is None
keyrings/alt/pyfs.py:181: in get_password
password_base64 = self.config.get(service, username).encode()
keyrings/alt/pyfs.py:166: in config
f = self._open()
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 

self = , mode = 'r'

def _open(self, mode='r'):
"""Open the password file in the specified mode
"""
open_file = None
writeable = 'w' in mode or 'a' in mode or '+' in mode
try:
# NOTE: currently the MemOpener does not split off any filename
#   which causes errors on close()
#   so we add a dummy name and open it separately
if (self.filename.startswith('mem://') or
self.filename.startswith('ram://')):
open_file = fs.opener.fsopendir(self.filename).open('kr.cfg',
mode)
else:
if not hasattr(self, '_pyfs'):
# reuse the pyfilesystem and path
self._pyfs, self._path = fs.opener.opener.parse(
self.filename, writeable=writeable)
# cache if permitted
if self._cache_timeout is not None:
self._pyfs = fs.remote.CacheFS(
self._pyfs, cache_timeout=self._cache_timeout)
open_file = self._pyfs.open(self._path, mode)
>   except fs.errors.ResourceNotFoundError:
E   AttributeError: 'module' object has no attribute 'ResourceNotFoundError'

keyrings/alt/pyfs.py:108: AttributeError
=== 64 failed, 23 passed, 39 skipped in 3.85 seconds ===
E: pybuild pybuild:338: test: plugin distutils failed with: exit code=1: cd 
/<>/.pybuild/cpython2_2.7_keyrings.alt/build; python2.7 -m pytest 
--ignore=keyrings/alt/_win_crypto.py --ignore=tests/test_crypto.py 
--ignore=tests/test_file.py --ignore=tests/test_Windows.py
dh_auto_test: pybuild --test --test-pytest -i python{version} -p 2.7 returned 
exit code 13
make: *** [debian/rules:13: build-indep] Error 25
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


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

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

where you can get a full build log if you need it.

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the BTS web page for this package.

Thanks.
--- End Message ---
--- Begin Message ---
Source: keyrings.alt
Source-Version: 3.1.1-1

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

A summary of the 

Processed: Re: Bug#917518: python-matplotlib: WxAgg backend cannot find fonts

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #917518 [python-matplotlib] python-matplotlib: WxAgg backend cannot find 
fonts
Severity set to 'serious' from 'important'

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

Processed: Bug #917496 in keyrings.alt marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #917496 [src:keyrings.alt] keyrings.alt: FTBFS ('module' object has no 
attribute 'ResourceNotFoundError')
Added tag(s) pending.

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

Bug#917496: Bug #917496 in keyrings.alt marked as pending

[Dmitry Shachnev]

Control: tag -1 pending

Hello,

Bug #917496 in keyrings.alt 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/python-team/modules/keyrings.alt/commit/2394ffbf5694562672bc8921ce2f0897133639ac


New upstream release.

- pyfs backend is disabled with pyfs 2.
Closes: #917496.


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/917496

Bug#880351: trapperkeeper-status-clojure: FTBFS: Test failures

[Cyril Brulebois]

Control: tag -1 patch


Hi Apollon & Java team,

Lucas Nussbaum  (2017-10-30):
> Relevant part (hopefully):
> > at clojure.lang.Var.applyTo(Var.java:700)
> > at clojure.main.main(main.java:37)
> > Caused by: java.io.IOException: No such file or directory
> > at java.io.UnixFileSystem.createFileExclusively(Native Method)
> > at java.io.File.createNewFile(File.java:1012)
> > at me.raynes.fs$create.invokeStatic(fs.clj:283)
> > at me.raynes.fs$create.invoke(fs.clj:280)
> > at me.raynes.fs$touch.invokeStatic(fs.clj:412)
> > at me.raynes.fs$touch.doInvoke(fs.clj:408)
> > at clojure.lang.RestFn.invoke(RestFn.java:410)
> > at 
> > puppetlabs.trapperkeeper.testutils.bootstrap$eval24901.invokeStatic(bootstrap.clj:11)
> > at 
> > puppetlabs.trapperkeeper.testutils.bootstrap$eval24901.invoke(bootstrap.clj:11)
> > at clojure.lang.Compiler.eval(Compiler.java:6927)
> > at clojure.lang.Compiler.load(Compiler.java:7379)
> > ... 42 more
> > debian/rules:44: recipe for target 'override_dh_auto_test' failed

It was a bit curious at first since I couldn't reproduce it in my sid
amd64 devel chroot, but could in my sid amd64 sbuild chroot… Checking
strace's output, it seemed like it might be that some leftover from a
previous test might have been missing:

[…]/test/./target/empty.ini

so I've tried sorting the tests to run, and I've got a reproducible
success, both inside devel & sbuild chroots.

You'll find attached two patches: one for the FTBFS, one for the Vcs-*
fields.

I can upload an NMU and/or push those to git if you give me permission
on salsa (username = kibi), or prepare a merge request; whatever works
for you. :)


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant
From 60a00eebb3574ebdb81df7615f8948bd3ccdbc7f Mon Sep 17 00:00:00 2001
From: Cyril Brulebois 
Date: Fri, 28 Dec 2018 07:32:16 +0100
Subject: [PATCH 1/2] Fix/work around FTBFS by running tests in order (Closes:
 #880351).

---
 debian/changelog | 9 +
 debian/rules | 3 ++-
 2 files changed, 11 insertions(+), 1 deletion(-)

diff --git a/debian/changelog b/debian/changelog
index c2f0797..00e501a 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,12 @@
+trapperkeeper-status-clojure (0.7.1-2) UNRELEASED; urgency=medium
+
+  * Insert a “sort” call between the find and the xargs calls in the
+dh_auto_test override: tests are apparently picky about who ran
+before who, which can lead to ENOENT depending on find's output,
+triggering an FTBFS (Closes: #880351).
+
+ -- Cyril Brulebois   Fri, 28 Dec 2018 07:30:02 +0100
+
 trapperkeeper-status-clojure (0.7.1-1) unstable; urgency=medium
 
   * Initial release (Closes: #855744)
diff --git a/debian/rules b/debian/rules
index 0b9cb2c..d7e758c 100755
--- a/debian/rules
+++ b/debian/rules
@@ -41,5 +41,6 @@ override_jh_clean:
 	cat debian/footer.html >> $@
 
 override_dh_auto_test:
-	(cd test && find . -name "*.clj" | \
+	# Make sure to run tests in order, to avoid ENOENT issues (#880351):
+	(cd test && find . -name "*.clj" | LC_ALL=C sort | \
 		xargs --verbose clojure -cp $(CURDIR)/$(PRODUCED_JAR):$(CLASSPATH):$(TEST_CLASSPATH))
-- 
2.20.1

From d2e8c9340e2a4a95314ef9bdba4bbe74cd1128e1 Mon Sep 17 00:00:00 2001
From: Cyril Brulebois 
Date: Fri, 28 Dec 2018 07:34:17 +0100
Subject: [PATCH 2/2] Update Vcs-{Browser,Git} to point to salsa (alioth's
 replacement).

---
 debian/changelog | 1 +
 debian/control   | 4 ++--
 2 files changed, 3 insertions(+), 2 deletions(-)

diff --git a/debian/changelog b/debian/changelog
index 00e501a..48f98ed 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -4,6 +4,7 @@ trapperkeeper-status-clojure (0.7.1-2) UNRELEASED; urgency=medium
 dh_auto_test override: tests are apparently picky about who ran
 before who, which can lead to ENOENT depending on find's output,
 triggering an FTBFS (Closes: #880351).
+  * Update Vcs-{Browser,Git} to point to salsa (alioth's replacement).
 
  -- Cyril Brulebois   Fri, 28 Dec 2018 07:30:02 +0100
 
diff --git a/debian/control b/debian/control
index ec4a21b..0d1df05 100644
--- a/debian/control
+++ b/debian/control
@@ -32,8 +32,8 @@ Build-Depends:
  libtext-markdown-perl | markdown,
  default-jdk
 Standards-Version: 4.0.0
-Vcs-Git: https://anonscm.debian.org/git/pkg-java/trapperkeeper-status-clojure.git
-Vcs-Browser: https://anonscm.debian.org/cgit/pkg-java/trapperkeeper-status-clojure.git
+Vcs-Git: https://salsa.debian.org/java-team/trapperkeeper-status-clojure
+Vcs-Browser: https://salsa.debian.org/java-team/trapperkeeper-status-clojure
 Homepage: https://github.com/puppetlabs/trapperkeeper-status
 
 Package: libtrapperkeeper-status-clojure
-- 
2.20.1



signature.asc
Description: PGP signature

Processed: Re: Bug#880351: trapperkeeper-status-clojure: FTBFS: Test failures

[Debian Bug Tracking System]

Processing control commands:

> tag -1 patch
Bug #880351 [src:trapperkeeper-status-clojure] trapperkeeper-status-clojure: 
FTBFS: Test failures
Added tag(s) patch.

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

Processed: Bug #917315 in libtgvoip marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #917315 [libtgvoip] libtgvoip: FTBFS on several arches (i386, mips, 
ppc64el, s390x) after recent upload
Added tag(s) pending.

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

Bug#917315: Bug #917315 in libtgvoip marked as pending

[Nicholas Guriev]

Control: tag -1 pending

Hello,

Bug #917315 in libtgvoip 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/debian/libtgvoip/commit/bc7b55d9f250ab40cca6dd4f32849fd6a5ba4a0e


Fix porting issues

Closes: #917315


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/917315

Bug#917261: linux-image-4.19.0-1-amd64: /dev/mapper symlink for dm-crypt volume containing / not created on system startup

[Ben Hutchings]

On Wed, 2018-12-26 at 21:57 -0500, Celejar wrote:
> On Wed, 26 Dec 2018 15:39:19 +
> Ben Hutchings  wrote:
> 
> > On Tue, Dec 25, 2018 at 09:58:33PM -0500, Celejar wrote:
> > > On Tue, 25 Dec 2018 20:52:46 +
> > > Ben Hutchings  wrote:
> > > 
> > > > Control: reassign -1 udev 240-1
> > > > Control: forcemerge 917124 -1
> > > > 
> > > > This seems to be a bug in udev, not the kernel.  You will only have
> > > > noticed it once you rebooted for the kernel upgrade.
> > > 
> > > Nope - in my system's current state, when rebooting into 4.19 there's
> > > no /dev/mapper symlink, but when rebooting into 4.18 there is. I've
> > > gone back and forth several times, and the behavior is consistent.
> > > There's clearly something that 4.19 is doing differently from 4.18. [I
> > > guess it might still be a udev bug, which is being exposed by some
> > > change in 4.19.]
> > 
> > This is probably because the initramfs for 4.18 contains the old
> > version of udev.
> 
> Okay, I think I understand. So if I were to update the 4.18 initramfs
> (with update-initramfs -k 4.18-nnn) now, I would expect to see the same
> problem with that kernel?

Yes.

And if you downgrade udev and libudev1 to version 239-15, that will
trigger an update of the 4.19 initramfs (only) and you should then be
able to boot with Linux 4.19.

Ben.

-- 
Ben Hutchings
Life is what happens to you while you're busy making other plans.
  - John Lennon




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

Bug#917505: marked as done (python-certbot-dns-ovh: FTBFS (failing tests))

[Debian Bug Tracking System]

Your message dated Fri, 28 Dec 2018 05:21:17 +
with message-id 
and subject line Bug#917505: fixed in python-certbot-dns-ovh 0.28.0-1
has caused the Debian Bug report #917505,
regarding python-certbot-dns-ovh: FTBFS (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.)


-- 
917505: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917505
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:python-certbot-dns-ovh
Version: 0.27.1-1
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules binary-indep
dh binary-indep --with python3,sphinxdoc --buildsystem=pybuild
   dh_update_autotools_config -i -O--buildsystem=pybuild
   dh_autoreconf -i -O--buildsystem=pybuild
   dh_auto_configure -i -O--buildsystem=pybuild
I: pybuild base:217: python3.7 setup.py config 
running config
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
dh_auto_build
I: pybuild base:217: /usr/bin/python3 setup.py build 
running build
running build_py
creating 
/<>/.pybuild/cpython3_3.7_certbot-dns-ovh/build/certbot_dns_ovh

[... snipped ...]

Traceback (most recent call last):
  File "/<>/certbot_dns_ovh/dns_ovh_test.py", line 54, in setUp
ENDPOINT, APPLICATION_KEY, APPLICATION_SECRET, CONSUMER_KEY, 0
  File "/<>/certbot_dns_ovh/dns_ovh.py", line 85, in __init__
'ttl': ttl,
  File "/usr/lib/python3/dist-packages/lexicon/providers/ovh.py", line 45, in 
__init__
super(Provider, self).__init__(config)
  File "/usr/lib/python3/dist-packages/lexicon/providers/base.py", line 42, in 
__init__
self.config = legacy_config_resolver(config)
  File "/usr/lib/python3/dist-packages/lexicon/config.py", line 349, in 
legacy_config_resolver
return 
ConfigResolver().with_legacy_dict(legacy_dict).with_env().with_config_dir(os.getcwd())
  File "/usr/lib/python3/dist-packages/lexicon/config.py", line 195, in 
with_legacy_dict
return self.with_config_source(LegacyDictConfigSource(legacy_dict_object))
  File "/usr/lib/python3/dist-packages/lexicon/config.py", line 312, in __init__
raise AttributeError('Error, key provider_name is not defined.'
AttributeError: Error, key provider_name is not defined.LegacyDictConfigSource 
cannot scope correctly the provider specific options.

==
ERROR: test_del_txt_record_fail_to_find_domain 
(certbot_dns_ovh.dns_ovh_test.OVHLexiconClientTest)
--
Traceback (most recent call last):
  File "/<>/certbot_dns_ovh/dns_ovh_test.py", line 54, in setUp
ENDPOINT, APPLICATION_KEY, APPLICATION_SECRET, CONSUMER_KEY, 0
  File "/<>/certbot_dns_ovh/dns_ovh.py", line 85, in __init__
'ttl': ttl,
  File "/usr/lib/python3/dist-packages/lexicon/providers/ovh.py", line 45, in 
__init__
super(Provider, self).__init__(config)
  File "/usr/lib/python3/dist-packages/lexicon/providers/base.py", line 42, in 
__init__
self.config = legacy_config_resolver(config)
  File "/usr/lib/python3/dist-packages/lexicon/config.py", line 349, in 
legacy_config_resolver
return 
ConfigResolver().with_legacy_dict(legacy_dict).with_env().with_config_dir(os.getcwd())
  File "/usr/lib/python3/dist-packages/lexicon/config.py", line 195, in 
with_legacy_dict
return self.with_config_source(LegacyDictConfigSource(legacy_dict_object))
  File "/usr/lib/python3/dist-packages/lexicon/config.py", line 312, in __init__
raise AttributeError('Error, key provider_name is not defined.'
AttributeError: Error, key provider_name is not defined.LegacyDictConfigSource 
cannot scope correctly the provider specific options.

--
Ran 18 tests in 0.009s

FAILED (errors=13)
Test failed: 
error: Test failed: 
E: pybuild pybuild:338: test: plugin distutils failed with: exit code=1: 
python3.7 setup.py test 
dh_auto_test: pybuild --test -i python{version} -p 3.7 returned exit code 13
make: *** [debian/rules:6: binary-indep] Error 25
dpkg-buildpackage: error: debian/rules binary-indep subprocess returned exit 
status 2


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

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/python-certbot-dns-ovh.html

where you can get a full build log if you need it.

If this is 

Bug#906552: marked as done (watcher: FTBFS in buster/sid (failing tests))

[Debian Bug Tracking System]

Your message dated Fri, 28 Dec 2018 05:06:45 +
with message-id 
and subject line Bug#906552: fixed in watcher 1.12.0-1
has caused the Debian Bug report #906552,
regarding watcher: 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.)


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

Dear maintainer:

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


[...]
 debian/rules build-indep
pyversions: missing X(S)-Python-Version in control file, fall back to 
debian/pyversions
pyversions: missing debian/pyversions file, fall back to supported versions
py3versions: no X-Python3-Version in control file, using supported versions
dh build-indep --buildsystem=python_distutils --with python3,systemd,sphinxdoc
   dh_update_autotools_config -i -O--buildsystem=python_distutils
   dh_autoreconf -i -O--buildsystem=python_distutils
   dh_auto_configure -i -O--buildsystem=python_distutils
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.
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
pyversions: missing X(S)-Python-Version in control file, fall back to 
debian/pyversions
pyversions: missing debian/pyversions file, fall back to supported versions

[... snipped ...]

--
_StringException: Traceback (most recent call last):
  File 
"/<>/watcher/tests/decision_engine/strategy/strategies/test_zone_migration.py",
 line 96, in setUp
model = self.fake_c_cluster.generate_scenario_1()
  File 
"/<>/watcher/tests/decision_engine/model/faker_cluster_state.py", 
line 119, in generate_scenario_1
return self.load_model('scenario_1.xml')
  File 
"/<>/watcher/tests/decision_engine/model/faker_cluster_state.py", 
line 50, in load_model
return modelroot.ModelRoot.from_xml(self.load_data(filename))
  File "/<>/watcher/decision_engine/model/model_root.py", line 
224, in from_xml
model.add_node(node)
  File "/usr/lib/python3/dist-packages/oslo_concurrency/lockutils.py", line 
274, in inner
return f(*args, **kwargs)
  File "/<>/watcher/decision_engine/model/model_root.py", line 60, 
in add_node
super(ModelRoot, self).add_node(node.uuid, node)
TypeError: add_node() takes 2 positional arguments but 3 were given


==
FAIL: 
watcher.tests.decision_engine.test_scheduling.TestDecisionEngineSchedulingService.test_start_de_scheduling_service
watcher.tests.decision_engine.test_scheduling.TestDecisionEngineSchedulingService.test_start_de_scheduling_service
--
_StringException: Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/mock/mock.py", line 1305, in patched
return func(*args, **keywargs)
  File "/<>/watcher/tests/decision_engine/test_scheduling.py", 
line 54, in test_start_de_scheduling_service
self.assertTrue(bool(fake_collector.cluster_data_model))
  File "/<>/watcher/decision_engine/model/collector/base.py", line 
137, in cluster_data_model
self._cluster_data_model = self.execute()
  File 
"/<>/watcher/tests/decision_engine/model/faker_cluster_state.py", 
line 56, in execute
return self._cluster_data_model or self.build_scenario_1()
  File 
"/<>/watcher/tests/decision_engine/model/faker_cluster_state.py", 
line 82, in build_scenario_1
model.add_node(node)
  File "/usr/lib/python3/dist-packages/oslo_concurrency/lockutils.py", line 
274, in inner
return f(*args, **kwargs)
  File "/<>/watcher/decision_engine/model/model_root.py", line 60, 
in add_node
super(ModelRoot, self).add_node(node.uuid, node)
TypeError: add_node() takes 2 positional arguments but 3 were given


--
Ran 1697 tests in 118.448s

FAILED (failures=262)
make[1]: *** [debian/rules:31: override_dh_install] Error 1
make[1]: Leaving directory '/<>'
make: *** [debian/rules:6: binary-indep] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary-indep subprocess 
returned exit status 2


The build was made with "dpkg-buildpackage -A" in my autobuilder.
Most probably, 

Bug#917428: Python 2 matplotlib package required for sagemath

[Sandro Tosi]

there is a python-matplotlib binary package at 2.2.3 so i'm not sure
what is the problem you're having - check again?

On Thu, Dec 27, 2018 at 12:08 PM Tobias Hansen  wrote:
>
> Hi Sandro,
>
> I was just about to finish an update to the sagemath package when you 
> uploaded matplotlib 3.0.2 to unstable. We need the Python 2 package for 
> sagemath (see #917428). Would you be ok with me uploading matplotlib 2.2.3 as 
> a separate source package that provides python-matplotlib? Or would you even 
> want to maintain it?
>
> Best,
>
> Tobias
>
>


-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
G+: https://plus.google.com/u/0/+SandroTosi

Bug#917502: Can't reproduce

[Thomas Goirand]

severity 917502 important
tags 917502 moreinfo unreproducible
thanks

I'm sorry but I can't reproduce this in a "normal" sbuild environment. I
tried under both Sid and Buster.

Unless I'm provided with a way to reproduce, I'll keep this bug with
severity "important", as it doesn't look like it's the standard build
environment, meaning it wont affect most users.

Cheers,

Thomas Goirand (zigo)

Processed: Can't reproduce

[Debian Bug Tracking System]

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

> severity 917502 important
Bug #917502 [src:nova] nova: FTBFS (name 'sqlite3' is not defined)
Severity set to 'important' from 'serious'
> tags 917502 moreinfo unreproducible
Bug #917502 [src:nova] nova: FTBFS (name 'sqlite3' is not defined)
Added tag(s) unreproducible and moreinfo.
> thanks
Stopping processing here.

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

Bug#880320: marked as done (ssl-utils-clojure: FTBFS: Test failures)

[Debian Bug Tracking System]

Your message dated Fri, 28 Dec 2018 04:30:14 +0100
with message-id <20181228033014.frugm6yodciqh...@mraw.org>
and subject line Re: Bug#880320: ssl-utils-clojure: FTBFS: Test failures
has caused the Debian Bug report #880320,
regarding ssl-utils-clojure: 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.)


-- 
880320: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=880320
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ssl-utils-clojure
Version: 0.8.3-1
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20171030 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
>   at clojure.core$load_libs.invokeStatic(core.clj:5775)
>   at clojure.core$load_libs.doInvoke(core.clj:5758)
>   at clojure.lang.RestFn.applyTo(RestFn.java:137)
>   at clojure.core$apply.invokeStatic(core.clj:648)
>   at clojure.core$apply.invoke(core.clj:641)
>   at clojure.core$require.invokeStatic(core.clj:5858)
>   at clojure.core$require.doInvoke(core.clj:5796)
>   at clojure.lang.RestFn.invoke(RestFn.java:457)
>   at 
> puppetlabs.ssl_utils.extensions_utils_test$eval4329$loading__1497__auto4330.invoke(extensions_utils_test.clj:1)
>   at 
> puppetlabs.ssl_utils.extensions_utils_test$eval4329.invokeStatic(extensions_utils_test.clj:1)
>   at 
> puppetlabs.ssl_utils.extensions_utils_test$eval4329.invoke(extensions_utils_test.clj:1)
>   at clojure.lang.Compiler.eval(Compiler.java:6927)
>   at clojure.lang.Compiler.eval(Compiler.java:6916)
>   at clojure.lang.Compiler.load(Compiler.java:7379)
>   ... 12 more
> debian/rules:28: recipe for target 'override_dh_auto_test' failed

The full build log is available from:
   http://aws-logs.debian.net/2017/10/30/ssl-utils-clojure_0.8.3-1_unstable.log

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

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
[ Not the maintainer, just passing by. ]

Hi Lucas,

Lucas Nussbaum  (2017-10-30):
> Source: ssl-utils-clojure
> Version: 0.8.3-1
> Severity: serious
> Tags: buster sid
> User: debian...@lists.debian.org
> Usertags: qa-ftbfs-20171030 qa-ftbfs
> Justification: FTBFS on amd64
> 
> Hi,
> 
> During a rebuild of all packages in sid, your package failed to build on
> amd64.
> 
> Relevant part (hopefully):
> > at clojure.core$load_libs.invokeStatic(core.clj:5775)
> > at clojure.core$load_libs.doInvoke(core.clj:5758)
> > at clojure.lang.RestFn.applyTo(RestFn.java:137)
> > at clojure.core$apply.invokeStatic(core.clj:648)
> > at clojure.core$apply.invoke(core.clj:641)
> > at clojure.core$require.invokeStatic(core.clj:5858)
> > at clojure.core$require.doInvoke(core.clj:5796)
> > at clojure.lang.RestFn.invoke(RestFn.java:457)
> > at 
> > puppetlabs.ssl_utils.extensions_utils_test$eval4329$loading__1497__auto4330.invoke(extensions_utils_test.clj:1)
> > at 
> > puppetlabs.ssl_utils.extensions_utils_test$eval4329.invokeStatic(extensions_utils_test.clj:1)
> > at 
> > puppetlabs.ssl_utils.extensions_utils_test$eval4329.invoke(extensions_utils_test.clj:1)
> > at clojure.lang.Compiler.eval(Compiler.java:6927)
> > at clojure.lang.Compiler.eval(Compiler.java:6916)
> > at clojure.lang.Compiler.load(Compiler.java:7379)
> > ... 12 more
> > debian/rules:28: recipe for target 'override_dh_auto_test' failed
> 
> The full build log is available from:
>
> http://aws-logs.debian.net/2017/10/30/ssl-utils-clojure_0.8.3-1_unstable.log
> 
> A list of current common problems and possible solutions is available at
> http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
> 
> About the archive rebuild: The rebuild was done on EC2 VM instances from
> Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
> failed build was retried once to eliminate random failures.

I can't reproduce this issue in sid today, so I'm closing this bug
report for the time being. Feel free to cc me, should this FTBFS
be reproducible on your side.


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance 

Bug#915991: marked as done (vzctl FTBFS with glibc 2.28)

[Debian Bug Tracking System]

Your message dated Fri, 28 Dec 2018 03:02:56 +
with message-id 
and subject line Bug#915991: fixed in vzctl 4.9.4-6
has caused the Debian Bug report #915991,
regarding vzctl FTBFS with glibc 2.28
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.)


-- 
915991: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915991
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: vzctl
Version: 4.9.4-5
Severity: serious
Tags: ftbfs

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

...
config.c: In function 'store_dev':
config.c:1250:10: error: called object 'major' is not a function or function 
pointer
  major = major(res->dev); \
  ^
--- End Message ---
--- Begin Message ---
Source: vzctl
Source-Version: 4.9.4-6

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

Debian distribution maintenance software
pp.
Adam Borowski  (supplier of updated vzctl 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, 28 Dec 2018 02:12:17 +0100
Source: vzctl
Binary: vzctl
Architecture: source
Version: 4.9.4-6
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Adam Borowski 
Description:
 vzctl  - server virtualization solution - control tools
Closes: 884653 915991
Changes:
 vzctl (4.9.4-6) unstable; urgency=medium
 .
   * QA upload.
   * Fix FTBFS with glibc 2.28 due to makedev macros no longer included in
 sys/types.h (Closes: #915991)
 .
   [ Helmut Grohne ]
   * Fix FTCBFS: Let dh_auto_configure pass cross compilers. Closes: #884653.
Checksums-Sha1:
 9198d4ebd45d4f502511f48de12c19f3b0713c4d 1797 vzctl_4.9.4-6.dsc
 04f2a662500390d19d55207d1b3c77624c7251a0 16196 vzctl_4.9.4-6.debian.tar.xz
 ae6a591cac2f87c4a94249704e343749e02f085a 5351 vzctl_4.9.4-6_source.buildinfo
Checksums-Sha256:
 37cf15d382ac9ebfc7ae6f0fb2b61e8a277be7b7f6b7a01a52438362b30c601e 1797 
vzctl_4.9.4-6.dsc
 3dd6c036ea293de3387aa75d012913e0481b27a3d718e39329b242b5746c698c 16196 
vzctl_4.9.4-6.debian.tar.xz
 a5800055b05bedd03d429418a2ef357441f8c9edb1eaff07ded127efe7d20012 5351 
vzctl_4.9.4-6_source.buildinfo
Files:
 d0ee3f1388272353cd8c3babf7d4ff8b 1797 admin optional vzctl_4.9.4-6.dsc
 bc652545087260ed557834aac3a6b0a3 16196 admin optional 
vzctl_4.9.4-6.debian.tar.xz
 de5348ab26979e81ebb1f32209ee5294 5351 admin optional 
vzctl_4.9.4-6_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJIBAEBCgAyFiEEkjZVexcMh/iCHArDweDZLphvfH4FAlwlfUoUHGtpbG9ieXRl
QGFuZ2JhbmQucGwACgkQweDZLphvfH7FQQ/+KLDr+j9PS+TWlJ2bIW10FoTtQk8e
tCxOxBWwvbA+j4E/qo5Cq+E1DV1EAWiWMizJwQ5ovOkC4SENE85VObwGJjSY5NMy
ZLwDjd1iFZq0MiQ7qv8d05RCDH10ZeFgDmo9gj+fcS2XrEazXYRHRVtTbtabAvu5
xHo8zJFacbqf8UmcVNWGJFoSfWeb3YmmqSUhyZxX7cWZlZb3mqHt3QO1YsJin0CB
1e6KCxaAc4qcm9zkZXeGke0e5zM+CS6Cw3EdFLTlVJVTjx6lzBkcppPPf+mA8bZZ
uj0F9qYG3nWYPiCK2N0kn81fp/63AMWpYc5lKXI92KSfSuyHchBWRMw+e4P6xD4j
3GCGGsvL5b8mmYuvziuzoXyDaydVjPNk1bafvhT7XTLuiaWSMIJaCp5c3/OqVsbj
F5L6priJ80+8Y5J+T3MPTj6BcI2Gb56vFOzZ1AHfXKIib2rNwl8hTLWzM6N1kUrj
v4LPrZ/41ACd/00W9mc7MRmIKXrRMi78HbztINCvYDIWUvulXDDPUdybuA7RXg+w
0fpqH/mXCXQY0hH4XbilhLd9Jv0Zp5dljUbWGVtmj6rNGxzS4SuixGCXSdOFJPMf
mOm5hpmAzSjWs+GL93fP8L8zLKg0tBIvKXks562b5dqXp+h8+HHdEgiCVKgsxX6p
ReAjC23bLYKTyfM=
=VPcA
-END PGP SIGNATURE End Message ---

Bug#907765: honeysql-clojure: FTBFS in buster/sid (Could not locate honeysql/format_test__init.class or honeysql/format_test.clj on classpath.)

[Cyril Brulebois]

[ Not the maintainer, passing by.]

Hi Santiago,

Santiago Vila  (2018-09-01):
> Exception in thread "main" java.io.FileNotFoundException: Could not locate 
> honeysql/format_test__init.class or honeysql/format_test.clj on classpath. 
> Please check that namespaces with dashes use underscores in the Clojure file 
> name., compiling:(/<>/test/./honeysql/core_test.cljc:1:1)
>   at clojure.lang.Compiler.load(Compiler.java:7526)
>   at clojure.lang.Compiler.loadFile(Compiler.java:7452)
>   at clojure.main$load_script.invokeStatic(main.clj:278)
>   at clojure.main$script_opt.invokeStatic(main.clj:338)
>   at clojure.main$script_opt.invoke(main.clj:333)
>   at clojure.main$main.invokeStatic(main.clj:424)
>   at clojure.main$main.doInvoke(main.clj:387)
>   at clojure.lang.RestFn.applyTo(RestFn.java:137)
>   at clojure.lang.Var.applyTo(Var.java:702)
>   at clojure.main.main(main.java:37)
> Caused by: java.io.FileNotFoundException: Could not locate 
> honeysql/format_test__init.class or honeysql/format_test.clj on classpath. 
> Please check that namespaces with dashes use underscores in the Clojure file 
> name.
>   at clojure.lang.RT.load(RT.java:463)
>   at clojure.lang.RT.load(RT.java:426)
>   at clojure.core$load$fn__9115.invoke(core.clj:6046)
>   at clojure.core$load.invokeStatic(core.clj:6045)
>   at clojure.core$load.doInvoke(core.clj:6029)
>   at clojure.lang.RestFn.invoke(RestFn.java:408)
>   at clojure.core$load_one.invokeStatic(core.clj:5848)
>   at clojure.core$load_one.invoke(core.clj:5843)
>   at clojure.core$load_lib$fn__9060.invoke(core.clj:5888)
>   at clojure.core$load_lib.invokeStatic(core.clj:5887)
>   at clojure.core$load_lib.doInvoke(core.clj:5868)
>   at clojure.lang.RestFn.applyTo(RestFn.java:142)
>   at clojure.core$apply.invokeStatic(core.clj:659)
>   at clojure.core$load_libs.invokeStatic(core.clj:5925)
>   at clojure.core$load_libs.doInvoke(core.clj:5909)
>   at clojure.lang.RestFn.applyTo(RestFn.java:137)
>   at clojure.core$apply.invokeStatic(core.clj:659)
>   at clojure.core$require.invokeStatic(core.clj:5947)
>   at clojure.core$require.doInvoke(core.clj:5947)
>   at clojure.lang.RestFn.invoke(RestFn.java:457)
>   at 
> honeysql.core_test$eval2694$loading__9001__auto2695.invoke(core_test.cljc:1)
>   at honeysql.core_test$eval2694.invokeStatic(core_test.cljc:1)
>   at honeysql.core_test$eval2694.invoke(core_test.cljc:1)
>   at clojure.lang.Compiler.eval(Compiler.java:7062)
>   at clojure.lang.Compiler.eval(Compiler.java:7051)
>   at clojure.lang.Compiler.load(Compiler.java:7514)
>   ... 9 more
> make[1]: *** [debian/rules:26: override_dh_auto_test] Error 123
> make[1]: Leaving directory '/<>'
> make: *** [debian/rules:11: build-indep] Error 2
> dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
> status 2
> 
> 
> The build was made in my autobuilder with "dpkg-buildpackage -A"

I can't reproduce this locally in a sid sbuild schroot, with -A.

> but it also fails here:
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/honeysql-clojure.html

Last build there seems OK as well.

> In reproducible builds it seems to be random, but I tried to build it
> 50 times on GCE n1-standard-1 machines today and it failed each and
> every time.  If you need a test machine to reproduce please say so.

Can you please double check what happens on your end, and close if this
went away?


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature

Processed: your mail

[Debian Bug Tracking System]

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

> tags 857298 + fixed
Bug #857298 [python-cassandra-dbg] python-cassandra-dbg is an empty package on 
hppa, m68k, mips, powerpc, powerpcspe, ppc64, s390x, and sparc64
Added tag(s) fixed.
> --
Stopping processing here.

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

Bug#917513: recommonmark-scripts: trying to overwrite '/usr/share/man/man1/cm2html.1.gz', which is also in package python-recommonmark 0.4.0+ds-2

[Axel Beckert]

Hi,

Axel Beckert wrote:
> This is basically the same issue as https://bugs.debian.org/917378, just
> now with recommonmark-scripts instead of python3-recommonmark.

JFTR, here's the full error output for the issue with 0.4.0+ds-4:

Preparing to unpack .../recommonmark-scripts_0.4.0+ds-4_all.deb ...
Unpacking recommonmark-scripts (0.4.0+ds-4) over (0.4.0+ds-2) ...
dpkg: error processing archive 
/var/cache/apt/archives/recommonmark-scripts_0.4.0+ds-4_all.deb (--unpack):
 trying to overwrite '/usr/share/man/man1/cm2html.1.gz', which is also in 
package python-recommonmark 0.4.0+ds-2
Errors were encountered while processing:
 /var/cache/apt/archives/recommonmark-scripts_0.4.0+ds-4_all.deb

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

Bug#917513: recommonmark-scripts: trying to overwrite '/usr/share/man/man1/cm2html.1.gz', which is also in package python-recommonmark 0.4.0+ds-2

[Axel Beckert]

Package: recommonmark-scripts
Version: 0.4.0+ds-2
Severity: serious

This is basically the same issue as https://bugs.debian.org/917378, just
now with recommonmark-scripts instead of python3-recommonmark.

recommonmark-scripts needs versioned Breaks and Replaces headers (see
the Policy for details), now against python-recommonmark _and_
python3-recommonmark, because it now seems to contain files which were
previously in python-recommonmark (up to 0.4.0+ds-2) and
python3-recommonmark (in 0.4.0+ds-3), given #917378 and this changelog
entry in 0.4.0+ds-4:

- debian/python3-recommonmark.manpages, rename to
- debian/recommonmark-scripts.manpages.

Oh, and btw., from the same changelog entry:

- debian/control:
  - Breaks/Replaces fields, add to manage transition;

I though see no Breaks or Replaces header in neither
recommonmark-scripts nor python3-recommonmark (nor python-recommonmark
where it wouldn't make sense):

→ acs recommonmark-scripts python-recommonmark python3-recommonmark | egrep 
'Breaks|Replaces'
→ 

-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (980, 'unstable-debug'), (600, 'testing'), 
(111, 'buildd-unstable'), (111, 'buildd-experimental'), (110, 'experimental'), 
(105, 'experimental-debug')
Architecture: amd64 (x86_64)

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

Versions of packages recommonmark-scripts depends on:
ii  python   2.7.15-3
pn  python-recommonmark  

recommonmark-scripts recommends no packages.

recommonmark-scripts suggests no packages.

-- no debconf information

Bug#914546: failing test skipped in 3.7.1-2; decreasing bug severity

[Cédric Boutillier]

Control: severity -1 normal
Control: tag -1 - ftbfs

Hi,

The bug has been reported upstream, and while waiting for a fix, the
failing test is skipped in 3.7.1-2, so that this won't cause a ftbs. The bug is
kept open, but severity is lowered to normal.

Thanks,

Cédric


signature.asc
Description: PGP signature

Processed: failing test skipped in 3.7.1-2; decreasing bug severity

[Debian Bug Tracking System]

Processing control commands:

> severity -1 normal
Bug #914546 [src:ruby-oj] ruby-oj FTBFS on 32bit: test failure
Severity set to 'normal' from 'serious'
> tag -1 - ftbfs
Bug #914546 [src:ruby-oj] ruby-oj FTBFS on 32bit: test failure
Removed tag(s) ftbfs.

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

Bug#916054: marked as done (procmeter3 FTBFS with glibc 2.28)

[Debian Bug Tracking System]

Your message dated Fri, 28 Dec 2018 00:04:27 +
with message-id 
and subject line Bug#916054: fixed in procmeter3 3.6-1.1
has caused the Debian Bug report #916054,
regarding procmeter3 FTBFS with glibc 2.28
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.)


-- 
916054: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916054
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: procmeter3
Version: 3.6-1
Severity: serious
Tags: ftbfs buster sid

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

...
longrun.c:41:24: error: unknown type name 'loff_t'; did you mean 'off_t'?
 static void read_cpuid(loff_t address, int *eax, int *ebx, int *ecx, int *edx) 
{
^~
--- End Message ---
--- Begin Message ---
Source: procmeter3
Source-Version: 3.6-1.1

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

Debian distribution maintenance software
pp.
Aurelien Jarno  (supplier of updated procmeter3 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: Wed, 26 Dec 2018 00:22:40 +0100
Source: procmeter3
Binary: procmeter3
Architecture: source
Version: 3.6-1.1
Distribution: unstable
Urgency: medium
Maintainer: Wences Arana 
Changed-By: Aurelien Jarno 
Description:
 procmeter3 - graphical system status monitor
Closes: 916054
Changes:
 procmeter3 (3.6-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * debian/patches/loff_t.patch
+ Fix build with glibc 2.28 Closes: #916054.
Checksums-Sha1:
 7188988cc1d4c625bbb8d66fdf2bb81526ca197b 1992 procmeter3_3.6-1.1.dsc
 3ad78b6d2bf1ed0fd409afadd19967dd220a2bde 9628 procmeter3_3.6-1.1.debian.tar.xz
 8cebe8ce4a880f5e9d667311f397ec46511ec115 13371 
procmeter3_3.6-1.1_source.buildinfo
Checksums-Sha256:
 fac54697903bcca33b8e6adda655734627b4748fa2668a6bb151aa62426967b5 1992 
procmeter3_3.6-1.1.dsc
 1496284bcc2028e7f486575bce7f97436a2dc0c0dd865a3c4c873d2ecbe03030 9628 
procmeter3_3.6-1.1.debian.tar.xz
 e388aac385981cc6dba489db06d4d4466baa6f08943c6cde42d1473da66c4d09 13371 
procmeter3_3.6-1.1_source.buildinfo
Files:
 625780b26d16eb68f2f9371aeb099bc1 1992 utils optional procmeter3_3.6-1.1.dsc
 db99e2d6a2bca8798537e1dabbe48e07 9628 utils optional 
procmeter3_3.6-1.1.debian.tar.xz
 a58d985d6fdf6e5a753b2ba3fb118970 13371 utils optional 
procmeter3_3.6-1.1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEUryGlb40+QrX1Ay4E4jA+JnoM2sFAlwiu/cACgkQE4jA+Jno
M2thThAAjYL1kjrL3lEBTTylC+E9Fr661GLtVx0H8b6j8gbPeNBopO8RWeDuChkF
slSEcTT7S0S3A49VCbx282oLe/E2ng+b6gPFh7iMVznKCELfLlZ3gAFSbHEeKL4e
puXPJwIuUUFbkoa3o0V7deMLlgJr6JZOOnmaW5dlIh/WP8si+xnDRmwH/L52ef0X
9XgLPdzrYxCAKjyFFSsccg6mdJpYLsEHOvfxqZJU+GbfFHWI7GvVPpk2rt1EWoBs
KB0tAAAF+UVlGYiv+mCjFxwswAyfrCMfrQpWiWAyDVs7SAoH6SK0DiVORizNGoKW
KhH0RwJt1s4uk/MYU/a3Gup1BIQCkJ+W+E8ugdK111OR1/Rrl95uzWqanyERZt7k
CGcrNZ3oJuJCYc2kt/OTiYZFI0oIfTzYcQtKex4UjDwXVIoTbWgdH71IBSoTnFSF
uD+VypYGlYIc7gW27cJ8vSAYR8g/Jz0U3IYyT3AgIJWXe1Y4t6lUt05kKj78de0c
H4mzFgPcOFDHM92pANVOa7Wj0n+mtTsrOHaROQq6eADkGl64ZojQ5lOcH6AV+dLx
sAmdao/GX1eVROihKZIJLbZuHWm4pVXuH+KMnrmIkV7VfuYUNLJBBbS5Laf5+vQB
Vvx3Y8zyCGyb0NixpxGYtLde37ovl9j7b6VGoOR0LygIBqycku4=
=iJ6K
-END PGP SIGNATURE End Message ---

Bug#917505: python-certbot-dns-ovh: FTBFS (failing tests)

[Santiago Vila]

Package: src:python-certbot-dns-ovh
Version: 0.27.1-1
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules binary-indep
dh binary-indep --with python3,sphinxdoc --buildsystem=pybuild
   dh_update_autotools_config -i -O--buildsystem=pybuild
   dh_autoreconf -i -O--buildsystem=pybuild
   dh_auto_configure -i -O--buildsystem=pybuild
I: pybuild base:217: python3.7 setup.py config 
running config
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
dh_auto_build
I: pybuild base:217: /usr/bin/python3 setup.py build 
running build
running build_py
creating 
/<>/.pybuild/cpython3_3.7_certbot-dns-ovh/build/certbot_dns_ovh

[... snipped ...]

Traceback (most recent call last):
  File "/<>/certbot_dns_ovh/dns_ovh_test.py", line 54, in setUp
ENDPOINT, APPLICATION_KEY, APPLICATION_SECRET, CONSUMER_KEY, 0
  File "/<>/certbot_dns_ovh/dns_ovh.py", line 85, in __init__
'ttl': ttl,
  File "/usr/lib/python3/dist-packages/lexicon/providers/ovh.py", line 45, in 
__init__
super(Provider, self).__init__(config)
  File "/usr/lib/python3/dist-packages/lexicon/providers/base.py", line 42, in 
__init__
self.config = legacy_config_resolver(config)
  File "/usr/lib/python3/dist-packages/lexicon/config.py", line 349, in 
legacy_config_resolver
return 
ConfigResolver().with_legacy_dict(legacy_dict).with_env().with_config_dir(os.getcwd())
  File "/usr/lib/python3/dist-packages/lexicon/config.py", line 195, in 
with_legacy_dict
return self.with_config_source(LegacyDictConfigSource(legacy_dict_object))
  File "/usr/lib/python3/dist-packages/lexicon/config.py", line 312, in __init__
raise AttributeError('Error, key provider_name is not defined.'
AttributeError: Error, key provider_name is not defined.LegacyDictConfigSource 
cannot scope correctly the provider specific options.

==
ERROR: test_del_txt_record_fail_to_find_domain 
(certbot_dns_ovh.dns_ovh_test.OVHLexiconClientTest)
--
Traceback (most recent call last):
  File "/<>/certbot_dns_ovh/dns_ovh_test.py", line 54, in setUp
ENDPOINT, APPLICATION_KEY, APPLICATION_SECRET, CONSUMER_KEY, 0
  File "/<>/certbot_dns_ovh/dns_ovh.py", line 85, in __init__
'ttl': ttl,
  File "/usr/lib/python3/dist-packages/lexicon/providers/ovh.py", line 45, in 
__init__
super(Provider, self).__init__(config)
  File "/usr/lib/python3/dist-packages/lexicon/providers/base.py", line 42, in 
__init__
self.config = legacy_config_resolver(config)
  File "/usr/lib/python3/dist-packages/lexicon/config.py", line 349, in 
legacy_config_resolver
return 
ConfigResolver().with_legacy_dict(legacy_dict).with_env().with_config_dir(os.getcwd())
  File "/usr/lib/python3/dist-packages/lexicon/config.py", line 195, in 
with_legacy_dict
return self.with_config_source(LegacyDictConfigSource(legacy_dict_object))
  File "/usr/lib/python3/dist-packages/lexicon/config.py", line 312, in __init__
raise AttributeError('Error, key provider_name is not defined.'
AttributeError: Error, key provider_name is not defined.LegacyDictConfigSource 
cannot scope correctly the provider specific options.

--
Ran 18 tests in 0.009s

FAILED (errors=13)
Test failed: 
error: Test failed: 
E: pybuild pybuild:338: test: plugin distutils failed with: exit code=1: 
python3.7 setup.py test 
dh_auto_test: pybuild --test -i python{version} -p 3.7 returned exit code 13
make: *** [debian/rules:6: binary-indep] Error 25
dpkg-buildpackage: error: debian/rules binary-indep subprocess returned exit 
status 2


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

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/python-certbot-dns-ovh.html

where you can get a full build log if you need it.

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the BTS web page for this package.

Thanks.

Bug#917506: python-crank: FTBFS (failing tests)

[Santiago Vila]

Package: src:python-crank
Version: 0.7.2-3
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules build-indep
pyversions: missing X(S)-Python-Version in control file, fall back to 
debian/pyversions
pyversions: missing debian/pyversions file, fall back to supported versions
py3versions: no X-Python3-Version in control file, using supported versions
dh /usr/share/openstack-pkg-tools/pkgos.make --buildsystem=python_distutils 
--with python2,python3
dh: Unknown sequence /usr/share/openstack-pkg-tools/pkgos.make (choose from: 
binary binary-arch binary-indep build build-arch build-indep clean install 
install-arch install-indep)
dh build-indep --buildsystem=python_distutils --with python2,python3
   dh_update_autotools_config -i -O--buildsystem=python_distutils
   dh_auto_configure -i -O--buildsystem=python_distutils
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: Please use the third-party "pybuild" build system instead of 
python-distutils
dh_auto_build: This feature will be removed in compat 12.

[... snipped ...]

tests.test_util.test_method_matches_args_fails_no_params ... ok
tests.test_util.test_method_matches_args_fails_more_remainder_than_argspec ... 
ok
tests.test_util.test_method_matches_args_with_default_values ... ok
tests.test_util.test_path_path ... ok
tests.test_util.test_path_list(.MockOb 
object at 0x7f67b4b4ce10>, ['', '']) ... ok
tests.test_util.test_path_list(.MockOb 
object at 0x7f67b4b51630>, ['', 'foo']) ... ok
tests.test_util.test_path_list(.MockOb 
object at 0x7f67b4b51668>, ['', 'foo', 'bar']) ... ok
tests.test_util.test_path_list(.MockOb 
object at 0x7f67b4b51630>, ['', 'foo', 'bar', '']) ... ok
tests.test_util.test_path_list(.MockOb 
object at 0x7f67b4b51668>, ['', 'foo', '', 'bar', '']) ... ok
tests.test_util.test_path_list(.MockOb 
object at 0x7f67b4b51630>, ['foo']) ... ok
tests.test_util.test_path_list(.MockOb 
object at 0x7f67b4b51668>, ['foo', 'bar']) ... ok
tests.test_util.test_path_str(.MockOb 
object at 0x7f67b4b51668>, '/', ) ... ok
tests.test_util.test_path_str(.MockOb 
object at 0x7f67b4bb7ac8>, '/foo', ) ... ok
tests.test_util.test_path_str(.MockOb 
object at 0x7f67b4bb7a20>, '/foo/bar', ) ... ok
tests.test_util.test_path_str(.MockOb 
object at 0x7f67b4bb79b0>, '/foo/bar/', ) ... ok
tests.test_util.test_path_str(.MockOb 
object at 0x7f67b4bb7b38>, '/foo//bar/', ) ... ok
tests.test_util.test_path_str(.MockOb 
object at 0x7f67b4bb7ac8>, 'foo', ) ... ok
tests.test_util.test_path_str(.MockOb 
object at 0x7f67b4bb7a20>, 'foo/bar', ) ... ok
tests.test_util.test_path_str(.MockOb 
object at 0x7f67b4b4cd30>, '', 
) ... FAIL
tests.test_util.test_path_unicode(.MockOb
 object at 0x7f67b4bb7b38>, '/', ) ... ok
tests.test_util.test_path_unicode(.MockOb
 object at 0x7f67b4bb7a20>, '/©', ) ... ok
tests.test_util.test_path_unicode(.MockOb
 object at 0x7f67b4bb7be0>, '/©/™', ) ... ok
tests.test_util.test_path_unicode(.MockOb
 object at 0x7f67b4bb7d30>, '/©/™/', ) ... ok
tests.test_util.test_path_unicode(.MockOb
 object at 0x7f67b4bb7c88>, '¡', ) ... ok
tests.test_util.test_path_unicode(.MockOb
 object at 0x7f67b4bb7a20>, 'foo/¡', ) ... ok
tests.test_util.test_path_slicing ... ok
tests.test_util.test_path_comparison ... ok
tests.test_util.test_path_translation ... ok

==
FAIL: 
tests.test_util.test_path_str(.MockOb 
object at 0x7f67b4b4cd30>, '', 
)
--
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/nose/case.py", line 197, in runTest
self.test(*self.arg)
  File "/<>/tests/test_util.py", line 126, in assert_path
assert kind(instance.path) == expected, (kind(instance.path), expected)
AssertionError: ('', '')

--
Ran 135 tests in 0.062s

FAILED (failures=1)
make[1]: *** [debian/rules:26: override_dh_auto_test] 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 in my autobuilder with "dpkg-buildpackage -A"
but it also fails here:

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

where you can get a full build log if you need it.

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the BTS web page for this package.

Thanks.

Bug#917510: trigger-rally: FTBFS (conflicting declaration)

[Santiago Vila]

Package: src:trigger-rally
Version: 0.6.5+dfsg-3
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules build-indep
dh build-indep -D src/
   dh_testdir -i -O-Dsrc/
   dh_update_autotools_config -i -O-Dsrc/
   dh_autoreconf -i -O-Dsrc/
   dh_auto_configure -i -O-Dsrc/
   dh_auto_build -i -O-Dsrc/
cd src && make -j1 "INSTALL=install --strip-program=true"
make[1]: Entering directory '/<>/trigger-rally-0.6.5+dfsg/src'

current values of user-set variables:
DESTDIR  ?= 
prefix   ?= /usr
exec_prefix  ?= /usr

[... snipped ...]

In file included from ./include/pengine.h:197,
 from PEngine/vmath.cpp:8:
./include/hiscore1.h: In member function 'void HiScore1::loadAllTimes()':
./include/hiscore1.h:238:75: warning: 'PHYSFS_sint64 PHYSFS_read(PHYSFS_File*, 
void*, PHYSFS_uint32, PHYSFS_uint32)' is deprecated [-Wdeprecated-declarations]
 PHYSFS_read(pfile, (), sizeof (char), pdata.size());
   ^
In file included from ./include/pengine.h:28,
 from PEngine/vmath.cpp:8:
/usr/include/physfs.h:1333:27: note: declared here
 PHYSFS_DECL PHYSFS_sint64 PHYSFS_read(PHYSFS_File *handle,
   ^~~
In file included from ./include/pengine.h:197,
 from PEngine/vmath.cpp:8:
./include/hiscore1.h:238:75: warning: 'PHYSFS_sint64 PHYSFS_read(PHYSFS_File*, 
void*, PHYSFS_uint32, PHYSFS_uint32)' is deprecated [-Wdeprecated-declarations]
 PHYSFS_read(pfile, (), sizeof (char), pdata.size());
   ^
In file included from ./include/pengine.h:28,
 from PEngine/vmath.cpp:8:
/usr/include/physfs.h:1333:27: note: declared here
 PHYSFS_DECL PHYSFS_sint64 PHYSFS_read(PHYSFS_File *handle,
   ^~~
In file included from ./include/pengine.h:197,
 from PEngine/vmath.cpp:8:
./include/hiscore1.h: In member function 'void HiScore1::writePlayerData(const 
string&) const':
./include/hiscore1.h:803:86: warning: 'PHYSFS_sint64 PHYSFS_write(PHYSFS_File*, 
const void*, PHYSFS_uint32, PHYSFS_uint32)' is deprecated 
[-Wdeprecated-declarations]
 PHYSFS_write(pfile, sspdata.str().data(), sizeof (char), 
sspdata.str().size());

  ^
In file included from ./include/pengine.h:28,
 from PEngine/vmath.cpp:8:
/usr/include/physfs.h:1362:27: note: declared here
 PHYSFS_DECL PHYSFS_sint64 PHYSFS_write(PHYSFS_File *handle,
   ^~~~
In file included from ./include/pengine.h:197,
 from PEngine/vmath.cpp:8:
./include/hiscore1.h:803:86: warning: 'PHYSFS_sint64 PHYSFS_write(PHYSFS_File*, 
const void*, PHYSFS_uint32, PHYSFS_uint32)' is deprecated 
[-Wdeprecated-declarations]
 PHYSFS_write(pfile, sspdata.str().data(), sizeof (char), 
sspdata.str().size());

  ^
In file included from ./include/pengine.h:28,
 from PEngine/vmath.cpp:8:
/usr/include/physfs.h:1362:27: note: declared here
 PHYSFS_DECL PHYSFS_sint64 PHYSFS_write(PHYSFS_File *handle,
   ^~~~
make[1]: *** [GNUmakefile:152: PEngine/vmath.o] Error 1
make[1]: Leaving directory '/<>/trigger-rally-0.6.5+dfsg/src'
dh_auto_build: cd src && make -j1 "INSTALL=install --strip-program=true" 
returned exit code 2
make: *** [debian/rules:20: build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


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

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

where you can get a full build log if you need it.

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the BTS web page for this package.

Thanks.

Bug#917509: theme-d-gnome: FTBFS (dh_auto_configure fails)

[Santiago Vila]

Package: src:theme-d-gnome
Version: 0.7.3-1
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules build-indep
dh build-indep --with autoreconf
   dh_update_autotools_config -i
   dh_autoreconf -i
find ! -ipath "./debian/*" -a ! \( -path '*/.git/*' -o -path '*/.hg/*' 
-o -path '*/.bzr/*' -o -path '*/.svn/*' -o -path '*/CVS/*' \) -a  -type f -exec 
md5sum {} + -o -type l -printf "symlink  %p
" > debian/autoreconf.before
grep -q ^XDT_ configure.ac
autoreconf -f -i
gnome/Makefile.am:14: warning: ':='-style assignments are not portable
gnome/Makefile.am:26: warning: '%'-style pattern rules are a GNU make extension
gnome/Makefile.am:29: warning: '%'-style pattern rules are a GNU make extension
find ! -ipath "./debian/*" -a ! \( -path '*/.git/*' -o -path '*/.hg/*' 
-o -path '*/.bzr/*' -o -path '*/.svn/*' -o -path '*/CVS/*' \) -a  -type f -exec 
md5sum {} + -o -type l -printf "symlink  %p
" > debian/autoreconf.after
   debian/rules override_dh_auto_configure

[... snipped ...]

datadir='${datarootdir}'
datarootdir='${prefix}/share'
docdir='${datarootdir}/doc/${PACKAGE_TARNAME}'
dvidir='${docdir}'
exec_prefix='NONE'
host_alias=''
htmldir='${docdir}'
includedir='${prefix}/include'
infodir='${prefix}/share/info'
install_sh='${SHELL} /<>/install-sh'
libdir='${prefix}/lib/x86_64-linux-gnu'
libexecdir='${prefix}/lib/x86_64-linux-gnu'
localedir='${datarootdir}/locale'
localstatedir='/var'
mandir='${prefix}/share/man'
mkdir_p='$(MKDIR_P)'
oldincludedir='/usr/include'
pdfdir='${docdir}'
prefix='/usr'
program_transform_name='s,x,x,'
psdir='${docdir}'
runstatedir='/run'
sbindir='${exec_prefix}/sbin'
sharedstatedir='${prefix}/com'
sysconfdir='/etc'
target_alias=''

## --- ##
## confdefs.h. ##
## --- ##

/* confdefs.h */
#define PACKAGE_NAME "Theme-D-Gnome"
#define PACKAGE_TARNAME "theme-d-gnome"
#define PACKAGE_VERSION "0.7.3"
#define PACKAGE_STRING "Theme-D-Gnome 0.7.3"
#define PACKAGE_BUGREPORT "tommi.hoynalanmaa at iki.fi"
#define PACKAGE_URL "http://www.iki.fi/tohoyn/theme-d/theme-d-gnome.html;
#define PACKAGE "theme-d-gnome"
#define VERSION "0.7.3"

configure: exit 1
dh_auto_configure: ./configure --build=x86_64-linux-gnu --prefix=/usr 
--includedir=\${prefix}/include --mandir=\${prefix}/share/man 
--infodir=\${prefix}/share/info --sysconfdir=/etc --localstatedir=/var 
--disable-silent-rules --libdir=\${prefix}/lib/x86_64-linux-gnu 
--libexecdir=\${prefix}/lib/x86_64-linux-gnu --runstatedir=/run 
--disable-maintainer-mode --disable-dependency-tracking --with-guile=2.0 
--with-guile-gnome=2.16.4 returned exit code 1
make[1]: *** [debian/rules:22: override_dh_auto_configure] Error 2
make[1]: Leaving directory '/<>'
make: *** [debian/rules:16: build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


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

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/theme-d-gnome.html

where you can get a full build log if you need it.

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the BTS web page for this package.

Thanks.

Bug#917507: python-os-faults: FTBFS (Unable to create /sbuild-nonexistent/.ansible/tmp)

[Santiago Vila]

Package: src:python-os-faults
Version: 0.1.17-2
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules build-indep
pyversions: missing X(S)-Python-Version in control file, fall back to 
debian/pyversions
pyversions: missing debian/pyversions file, fall back to supported versions
py3versions: no X-Python3-Version in control file, using supported versions
dh build-indep --buildsystem=python_distutils --with python2,python3,sphinxdoc
   dh_update_autotools_config -i -O--buildsystem=python_distutils
   dh_autoreconf -i -O--buildsystem=python_distutils
   dh_auto_configure -i -O--buildsystem=python_distutils
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: Please use the third-party "pybuild" build system instead of 
python-distutils
dh_auto_build: This feature will be removed in compat 12.
pyversions: missing X(S)-Python-Version in control file, fall back to 
debian/pyversions

[... snipped ...]

raise AnsibleError("Unable to create local directories(%s): %s" % 
(to_native(rpath), to_native(e)))
AnsibleError: Unable to create local 
directories(/sbuild-nonexistent/.ansible/tmp): [Errno 13] Permission denied: 
'/sbuild-nonexistent'



Configuration error:
There is a programable error in your configuration file:

Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/sphinx/config.py", line 161, in 
__init__
execfile_(filename, config)
  File "/usr/lib/python2.7/dist-packages/sphinx/util/pycompat.py", line 150, in 
execfile_
exec_(code, _globals)
  File "/usr/lib/python2.7/dist-packages/six.py", line 709, in exec_
exec("""exec _code_ in _globs_, _locs_""")
  File "", line 1, in 
  File "conf.py", line 18, in 
import os_faults
  File "/<>/os_faults/__init__.py", line 22, in 
from os_faults.ansible import executor
  File "/<>/os_faults/ansible/executor.py", line 19, in 
from ansible.executor import task_queue_manager
  File 
"/usr/lib/python2.7/dist-packages/ansible/executor/task_queue_manager.py", line 
26, in 
from ansible import constants as C
  File "/usr/lib/python2.7/dist-packages/ansible/constants.py", line 184, in 

config = ConfigManager()
  File "/usr/lib/python2.7/dist-packages/ansible/config/manager.py", line 243, 
in __init__
self.update_config_data()
  File "/usr/lib/python2.7/dist-packages/ansible/config/manager.py", line 499, 
in update_config_data
raise AnsibleError("Invalid settings supplied for %s: %s\n%s" % (config, 
to_native(e), traceback.format_exc()))
AnsibleError: Invalid settings supplied for DEFAULT_LOCAL_TMP: Unable to create 
local directories(/sbuild-nonexistent/.ansible/tmp): [Errno 13] Permission 
denied: '/sbuild-nonexistent'
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/ansible/config/manager.py", line 487, 
in update_config_data
value, origin = self.get_config_value_and_origin(config, configfile)
  File "/usr/lib/python2.7/dist-packages/ansible/config/manager.py", line 439, 
in get_config_value_and_origin
value = ensure_type(value, defs[config].get('type'), origin=origin)
  File "/usr/lib/python2.7/dist-packages/ansible/config/manager.py", line 91, 
in ensure_type
makedirs_safe(value, 0o700)
  File "/usr/lib/python2.7/dist-packages/ansible/utils/path.py", line 81, in 
makedirs_safe
raise AnsibleError("Unable to create local directories(%s): %s" % 
(to_native(rpath), to_native(e)))
AnsibleError: Unable to create local 
directories(/sbuild-nonexistent/.ansible/tmp): [Errno 13] Permission denied: 
'/sbuild-nonexistent'


make[1]: *** [debian/rules:20: override_dh_sphinxdoc] Error 2
make[1]: Leaving directory '/<>'
make: *** [debian/rules:7: binary-indep] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary-indep subprocess 
returned exit status 2


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

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/python-os-faults.html

where you can get a full build log if you need it.

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the BTS web page for this package.

Thanks.

Bug#917508: supertux: FTBFS (conflicting declaration)

[Santiago Vila]

Package: src:supertux
Version: 0.5.1-1
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules build-indep
dh build-indep --buildsystem=cmake
   dh_update_autotools_config -i -O--buildsystem=cmake
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
dh_auto_configure -- -DBUILD_SHARED_LIBS=OFF \
 -DENABLE_BOOST_STATIC_LIBS=OFF
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 
-DBUILD_SHARED_LIBS=OFF -DENABLE_BOOST_STATIC_LIBS=OFF ..
-- 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

[... snipped ...]

 from /<>/src/video/texture_manager.hpp:31,
 from /<>/src/video/texture.hpp:26,
 from /<>/src/video/font.hpp:28,
 from /<>/src/video/drawing_context.hpp:29,
 from /<>/src/video/drawing_request.hpp:30,
 from /<>/src/object/moving_sprite.hpp:23,
 from /<>/src/badguy/badguy.hpp:22,
 from /<>/src/badguy/angrystone.hpp:20,
 from /<>/src/badguy/angrystone.cpp:17:
/usr/include/GL/glew.h:18743:28: note: previous declaration as 'typedef void (* 
PFNGLGETFRAGMENTMATERIALFVSGIXPROC)(GLenum, GLenum, const GLfloat*)'
 typedef void (GLAPIENTRY * PFNGLGETFRAGMENTMATERIALFVSGIXPROC) (GLenum face, 
GLenum pname, const GLfloat* data);
^~
In file included from /<>/src/video/glutil.hpp:47,
 from /<>/src/video/texture_manager.hpp:31,
 from /<>/src/video/texture.hpp:26,
 from /<>/src/video/font.hpp:28,
 from /<>/src/video/drawing_context.hpp:29,
 from /<>/src/video/drawing_request.hpp:30,
 from /<>/src/object/moving_sprite.hpp:23,
 from /<>/src/badguy/badguy.hpp:22,
 from /<>/src/badguy/angrystone.hpp:20,
 from /<>/src/badguy/angrystone.cpp:17:
/usr/include/GL/glext.h:12080:102: error: conflicting declaration 'typedef void 
(* PFNGLGETFRAGMENTMATERIALIVSGIXPROC)(GLenum, GLenum, GLint*)'
 typedef void (APIENTRYP PFNGLGETFRAGMENTMATERIALIVSGIXPROC) (GLenum face, 
GLenum pname, GLint *params);

  ^
In file included from /<>/src/video/glutil.hpp:36,
 from /<>/src/video/texture_manager.hpp:31,
 from /<>/src/video/texture.hpp:26,
 from /<>/src/video/font.hpp:28,
 from /<>/src/video/drawing_context.hpp:29,
 from /<>/src/video/drawing_request.hpp:30,
 from /<>/src/object/moving_sprite.hpp:23,
 from /<>/src/badguy/badguy.hpp:22,
 from /<>/src/badguy/angrystone.hpp:20,
 from /<>/src/badguy/angrystone.cpp:17:
/usr/include/GL/glew.h:18744:28: note: previous declaration as 'typedef void (* 
PFNGLGETFRAGMENTMATERIALIVSGIXPROC)(GLenum, GLenum, const GLint*)'
 typedef void (GLAPIENTRY * PFNGLGETFRAGMENTMATERIALIVSGIXPROC) (GLenum face, 
GLenum pname, const GLint* data);
^~
make[3]: *** [CMakeFiles/supertux2_lib.dir/build.make:223: 
CMakeFiles/supertux2_lib.dir/src/badguy/angrystone.cpp.o] Error 1
make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu'
make[2]: *** [CMakeFiles/Makefile2:303: CMakeFiles/supertux2_lib.dir/all] Error 
2
make[2]: Leaving directory '/<>/obj-x86_64-linux-gnu'
make[1]: *** [Makefile:155: all] Error 2
make[1]: Leaving directory '/<>/obj-x86_64-linux-gnu'
dh_auto_build: cd obj-x86_64-linux-gnu && make -j1 returned exit code 2
make: *** [debian/rules:4: build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


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

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

where you can get a full build log if you need it.

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the BTS web page for this package.

Thanks.

Bug#917500: liggghts: FTBFS (style_atom.h: No such file or directory)

[Santiago Vila]

Package: src:liggghts
Version: 3.8.0+repack1-1
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules build-indep
dh build-indep --buildsystem=cmake 
--builddirectory=/<>/liggghts-3.8.0+repack1/debian/build
   dh_update_autotools_config -i -O--buildsystem=cmake 
-O--builddirectory=/<>/liggghts-3.8.0\+repack1/debian/build
   dh_autoreconf -i -O--buildsystem=cmake 
-O--builddirectory=/<>/liggghts-3.8.0\+repack1/debian/build
   dh_auto_configure -i -O--buildsystem=cmake 
-O--builddirectory=/<>/liggghts-3.8.0\+repack1/debian/build
cd debian/build && 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 -DCMAKE_INSTALL_RUNSTATEDIR=/run 
"-GUnix Makefiles" -DCMAKE_VERBOSE_MAKEFILE=ON 
-DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu ../..
-- 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

[... snipped ...]

CMAKE_EXPORT_NO_PACKAGE_REGISTRY


-- Build files have been written to: 
/<>/liggghts-3.8.0+repack1/debian/build
   dh_auto_build -i -O--buildsystem=cmake 
-O--builddirectory=/<>/liggghts-3.8.0\+repack1/debian/build
cd debian/build && make -j1 "INSTALL=install --strip-program=true"
make[1]: Entering directory '/<>/liggghts-3.8.0+repack1/debian/build'
/usr/bin/cmake -S/<>/liggghts-3.8.0+repack1 
-B/<>/liggghts-3.8.0+repack1/debian/build --check-build-system 
CMakeFiles/Makefile.cmake 0
/usr/bin/cmake -E cmake_progress_start 
/<>/liggghts-3.8.0+repack1/debian/build/CMakeFiles 
/<>/liggghts-3.8.0+repack1/debian/build/CMakeFiles/progress.marks
make -f CMakeFiles/Makefile2 all
make[2]: Entering directory '/<>/liggghts-3.8.0+repack1/debian/build'
make -f src/CMakeFiles/libliggghts.dir/build.make 
src/CMakeFiles/libliggghts.dir/depend
make[3]: Entering directory '/<>/liggghts-3.8.0+repack1/debian/build'
cd /<>/liggghts-3.8.0+repack1/debian/build && /usr/bin/cmake -E 
cmake_depends "Unix Makefiles" /<>/liggghts-3.8.0+repack1 
/<>/liggghts-3.8.0+repack1/src 
/<>/liggghts-3.8.0+repack1/debian/build 
/<>/liggghts-3.8.0+repack1/debian/build/src 
/<>/liggghts-3.8.0+repack1/debian/build/src/CMakeFiles/libliggghts.dir/DependInfo.cmake
 --color=
Scanning dependencies of target libliggghts
make[3]: Leaving directory '/<>/liggghts-3.8.0+repack1/debian/build'
make -f src/CMakeFiles/libliggghts.dir/build.make 
src/CMakeFiles/libliggghts.dir/build
make[3]: Entering directory '/<>/liggghts-3.8.0+repack1/debian/build'
[  0%] Building CXX object src/CMakeFiles/libliggghts.dir/angle.cpp.o
cd /<>/liggghts-3.8.0+repack1/debian/build/src && /usr/bin/mpicxx  
-Dlibliggghts_EXPORTS -DvtkIOGeometry_AUTOINIT="1(vtkIOMPIParallel)" 
-DvtkIOParallel_AUTOINIT="1(vtkIOMPIParallel)" 
-DvtkRenderingCore_AUTOINIT="3(vtkInteractionStyle,vtkRenderingFreeType,vtkRenderingOpenGL)"
 -I/usr/include/vtk-6.3 -I/usr/include/freetype2 
-I/usr/include/x86_64-linux-gnu -I/usr/include/hdf5/openmpi 
-I/usr/lib/x86_64-linux-gnu/openmpi/include/openmpi 
-I/usr/lib/x86_64-linux-gnu/openmpi/include -I/usr/include/jsoncpp 
-I/usr/include/eigen3 -I/<>/liggghts-3.8.0+repack1 
-I/<>/liggghts-3.8.0+repack1/src  -g -O2 
-fdebug-prefix-map=/<>/liggghts-3.8.0+repack1=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2  -DLAMMPS_VTK6 -DLAMMPS_VTK -std=c++0x -DLAMMPS_JPEG -fPIC  
 -o CMakeFiles/libliggghts.dir/angle.cpp.o -c 
/<>/liggghts-3.8.0+repack1/src/angle.cpp
[  0%] Building CXX object src/CMakeFiles/libliggghts.dir/angle_hybrid.cpp.o
cd /<>/liggghts-3.8.0+repack1/debian/build/src && /usr/bin/mpicxx  
-Dlibliggghts_EXPORTS -DvtkIOGeometry_AUTOINIT="1(vtkIOMPIParallel)" 
-DvtkIOParallel_AUTOINIT="1(vtkIOMPIParallel)" 
-DvtkRenderingCore_AUTOINIT="3(vtkInteractionStyle,vtkRenderingFreeType,vtkRenderingOpenGL)"
 -I/usr/include/vtk-6.3 -I/usr/include/freetype2 
-I/usr/include/x86_64-linux-gnu -I/usr/include/hdf5/openmpi 
-I/usr/lib/x86_64-linux-gnu/openmpi/include/openmpi 
-I/usr/lib/x86_64-linux-gnu/openmpi/include -I/usr/include/jsoncpp 
-I/usr/include/eigen3 -I/<>/liggghts-3.8.0+repack1 
-I/<>/liggghts-3.8.0+repack1/src  -g -O2 
-fdebug-prefix-map=/<>/liggghts-3.8.0+repack1=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2  -DLAMMPS_VTK6 -DLAMMPS_VTK -std=c++0x -DLAMMPS_JPEG -fPIC  
 -o CMakeFiles/libliggghts.dir/angle_hybrid.cpp.o -c 
/<>/liggghts-3.8.0+repack1/src/angle_hybrid.cpp
/<>/liggghts-3.8.0+repack1/src/angle_hybrid.cpp: In member function 
'virtual void 

Bug#917499: libtemplates-parser: FTBFS (gprbuild: unable to locate archive builder "unknown-ar")

[Santiago Vila]

Package: src:libtemplates-parser
Version: 19-2
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules build-indep
/usr/share/ada/debian_packaging-8.mk:71: adding -Wl,--as-needed to LDFLAGS for 
compatibility, but please use DEB_LDFLAGS_MAINT_APPEND instead.
/usr/share/ada/debian_packaging-8.mk:81: adding -Wl,--no-undefined to LDFLAGS 
for compatibility, but please use DEB_LDFLAGS_MAINT_APPEND instead.
dh build-indep --with ada-library
   dh_update_autotools_config -i
   dh_autoreconf -i
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
/usr/share/ada/debian_packaging-8.mk:71: adding -Wl,--as-needed to LDFLAGS for 
compatibility, but please use DEB_LDFLAGS_MAINT_APPEND instead.
/usr/share/ada/debian_packaging-8.mk:81: adding -Wl,--no-undefined to LDFLAGS 
for compatibility, but please use DEB_LDFLAGS_MAINT_APPEND instead.
rm -f makefile.setup tp_xmlada.gpr
make[1]: Leaving directory '/<>'
   debian/rules override_dh_auto_build-indep
make[1]: Entering directory '/<>'
/usr/share/ada/debian_packaging-8.mk:71: adding -Wl,--as-needed to LDFLAGS for 
compatibility, but please use DEB_LDFLAGS_MAINT_APPEND instead.
/usr/share/ada/debian_packaging-8.mk:81: adding -Wl,--no-undefined to LDFLAGS 
for compatibility, but please use DEB_LDFLAGS_MAINT_APPEND instead.
/usr/bin/make build-doc VERSION=18 DEFAULT_LIBRARY_TYPE=relocatable 
GPRBUILD="gprbuild -R -v -eS '-XADAFLAGS= -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong ' 
'-XLDFLAGS=-Wl,-z,relro -Wl,-z,now -Wl,--as-needed -Wl,--no-undefined'" 
PROCESSORS=1 DOC_FORMATS="html info latexpdf text"
make[2]: Entering directory '/<>'
cp config/tp_xmlada_installed.gpr tp_xmlada.gpr
printf " DEBUG = false\n DEFAULT_LIBRARY_TYPE = relocatable\n ENABLE_SHARED = 
true\n ENABLE_STATIC = true\n GNAT = gnat\n GPRBUILD = gprbuild -R -v -eS 
'-XADAFLAGS= -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong ' '-XLDFLAGS=-Wl,-z,relro -Wl,-z,now -Wl,--as-needed 
-Wl,--no-undefined'\n GPRCLEAN = gprclean\n PRJ_BUILD = release\n PROCESSORS = 
1\n SDIR = x86_64-linux-gnu/release\n TARGET = x86_64-linux-gnu\n TP_XMLADA = 
Installed\n VERSION = 18\n prefix = /usr/bin/..\n" > makefile.setup
/usr/bin/make -C docs html info latexpdf text
make[3]: Entering directory '/<>/docs'
gprbuild -R -v -eS '-XADAFLAGS= -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong ' '-XLDFLAGS=-Wl,-z,relro -Wl,-z,now -Wl,--as-needed 
-Wl,--no-undefined' -p -m -Pdocs user1 table_section table_inline if_inline 
demo macro table user2 matrix table_if \
  "-XPRJ_BUILD=release" "-XTARGET=x86_64-linux-gnu" "-XVERSION=18"
object directory "/<>/.build/obj/x86_64-linux-gnu/release/static" 
created for project Templates_Parser
library directory "/<>/.build/lib/x86_64-linux-gnu/release/static" 
created for project Templates_Parser
object directory 
"/<>/docs/build/obj/x86_64-linux-gnu/release/static" created for 
project Docs
exec directory 
"/<>/docs/build/bin/x86_64-linux-gnu/release/static" created for 
project Docs

==Error messages for file: /<>/docs/docs.gpr
22. project Docs is
|
>>> warning: there are no sources of language "Project file" in this 
project
Changing to object directory of "Docs": 
"/<>/docs/build/obj/x86_64-linux-gnu/release/static/"
/usr/bin/gnatgcc -c -x ada -gnatA -gnat05 -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong 
-gnatec=/tmp/GNAT-TEMP-03.TMP -gnatem=/tmp/GNAT-TEMP-04.TMP 
/<>/docs/src/user1.adb
/usr/bin/gnatgcc -c -x ada -gnatA -gnat05 -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong 
-gnatec=/tmp/GNAT-TEMP-03.TMP -gnatem=/tmp/GNAT-TEMP-04.TMP 
/<>/docs/src/table_section.adb
/usr/bin/gnatgcc -c -x ada -gnatA -gnat05 -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong 
-gnatec=/tmp/GNAT-TEMP-03.TMP -gnatem=/tmp/GNAT-TEMP-04.TMP 
/<>/docs/src/table_inline.adb
/usr/bin/gnatgcc -c -x ada -gnatA -gnat05 -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong 
-gnatec=/tmp/GNAT-TEMP-03.TMP -gnatem=/tmp/GNAT-TEMP-04.TMP 
/<>/docs/src/if_inline.adb
/usr/bin/gnatgcc -c -x ada -gnatA -gnat05 -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong 
-gnatec=/tmp/GNAT-TEMP-03.TMP -gnatem=/tmp/GNAT-TEMP-04.TMP 
/<>/docs/src/demo.adb
/usr/bin/gnatgcc -c -x ada -gnatA -gnat05 -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong 
-gnatec=/tmp/GNAT-TEMP-03.TMP -gnatem=/tmp/GNAT-TEMP-04.TMP 
/<>/docs/src/macro.adb
/usr/bin/gnatgcc -c -x ada -gnatA -gnat05 -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong 
-gnatec=/tmp/GNAT-TEMP-03.TMP -gnatem=/tmp/GNAT-TEMP-04.TMP 
/<>/docs/src/table.adb
/usr/bin/gnatgcc -c -x ada -gnatA -gnat05 -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong 
-gnatec=/tmp/GNAT-TEMP-03.TMP -gnatem=/tmp/GNAT-TEMP-04.TMP 
/<>/docs/src/user2.adb

Bug#917503: prometheus-alertmanager: FTBFS (cannot use *logLevel as type *promlog.Config)

[Santiago Vila]

Package: src:prometheus-alertmanager
Version: 0.15.1+ds-1
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules build-indep
dh build-indep --buildsystem=golang --with=golang,bash-completion \
--builddirectory=build
   dh_update_autotools_config -i -O--buildsystem=golang -O--builddirectory=build
   dh_autoreconf -i -O--buildsystem=golang -O--builddirectory=build
   dh_auto_configure -i -O--buildsystem=golang -O--builddirectory=build
install -d build
Copy silence/silence_test.go -> 
build/src/github.com/prometheus/alertmanager/silence/silence_test.go
Copy silence/silence.go -> 
build/src/github.com/prometheus/alertmanager/silence/silence.go
Copy silence/silencepb/silence.proto -> 
build/src/github.com/prometheus/alertmanager/silence/silencepb/silence.proto
Copy silence/silencepb/silence.pb.go -> 
build/src/github.com/prometheus/alertmanager/silence/silencepb/silence.pb.go
Copy cli/root.go -> 
build/src/github.com/prometheus/alertmanager/cli/root.go
Copy cli/check_config_test.go -> 
build/src/github.com/prometheus/alertmanager/cli/check_config_test.go
Copy cli/config.go -> 
build/src/github.com/prometheus/alertmanager/cli/config.go

[... snipped ...]

github.com/prometheus/alertmanager/silence
github.com/prometheus/alertmanager/template
github.com/prometheus/common/version
golang.org/x/net/context/ctxhttp
net/mail
net/smtp
github.com/prometheus/alertmanager/notify
github.com/prometheus/alertmanager/provider
github.com/prometheus/alertmanager/vendor/github.com/prometheus/prometheus/pkg/labels
github.com/prometheus/alertmanager/dispatch
github.com/prometheus/alertmanager/pkg/parse
github.com/julienschmidt/httprouter
github.com/prometheus/common/route
github.com/prometheus/alertmanager/api
github.com/alecthomas/units
go/token
go/scanner
go/ast
go/doc
gopkg.in/alecthomas/kingpin.v2
github.com/prometheus/alertmanager/cli/config
github.com/prometheus/client_golang/api
github.com/prometheus/alertmanager/client
github.com/prometheus/alertmanager/cli/format
os/user
github.com/prometheus/alertmanager/cli
github.com/prometheus/alertmanager/vendor/github.com/oklog/oklog/pkg/group
github.com/prometheus/alertmanager/inhibit
github.com/prometheus/alertmanager/provider/mem
github.com/prometheus/client_golang/prometheus/promhttp
runtime/pprof
runtime/trace
net/http/pprof
github.com/prometheus/alertmanager/ui
github.com/prometheus/common/promlog
github.com/prometheus/alertmanager/cmd/alertmanager
# github.com/prometheus/alertmanager/cmd/alertmanager
src/github.com/prometheus/alertmanager/cmd/alertmanager/main.go:173:24: cannot 
use *logLevel (type promlog.AllowedLevel) as type *promlog.Config in argument 
to promlog.New
github.com/prometheus/alertmanager/cmd/amtool
flag
testing
github.com/prometheus/alertmanager/test
dh_auto_build: cd build && go install 
-gcflags=all=\"-trimpath=/<>/prometheus-alertmanager-0.15.1\+ds/build/src\"
 
-asmflags=all=\"-trimpath=/<>/prometheus-alertmanager-0.15.1\+ds/build/src\"
 -v -p 1 -ldflags " -X github.com/prometheus/common/version.Version=0.15.1+ds 
-X github.com/prometheus/common/version.Revision=0.15.1+ds-1 -X 
github.com/prometheus/common/version.Branch=debian/sid -X 
github.com/prometheus/common/version.BuildUser=pkg-go-maintain...@lists.alioth.debian.org
 -X github.com/prometheus/common/version.BuildDate=20180805-18:58:17 -X 
github.com/prometheus/common/version.GoVersion=go1.10.7" 
github.com/prometheus/alertmanager/api github.com/prometheus/alertmanager/cli 
github.com/prometheus/alertmanager/cli/config 
github.com/prometheus/alertmanager/cli/format 
github.com/prometheus/alertmanager/client 
github.com/prometheus/alertmanager/cluster 
github.com/prometheus/alertmanager/cluster/clusterpb 
github.com/prometheus/alertmanager/cmd/alertmanager github.com
 /prometheus/alertmanager/cmd/amtool github.com/prometheus/alertmanager/config 
github.com/prometheus/alertmanager/dispatch 
github.com/prometheus/alertmanager/inhibit 
github.com/prometheus/alertmanager/nflog 
github.com/prometheus/alertmanager/nflog/nflogpb 
github.com/prometheus/alertmanager/notify 
github.com/prometheus/alertmanager/pkg/parse 
github.com/prometheus/alertmanager/provider 
github.com/prometheus/alertmanager/provider/mem 
github.com/prometheus/alertmanager/silence 
github.com/prometheus/alertmanager/silence/silencepb 
github.com/prometheus/alertmanager/template 
github.com/prometheus/alertmanager/test 
github.com/prometheus/alertmanager/types github.com/prometheus/alertmanager/ui 
returned exit code 2
make[1]: *** [debian/rules:38: override_dh_auto_build] Error 2
make[1]: Leaving directory '/<>/prometheus-alertmanager-0.15.1+ds'
make: *** [debian/rules:31: build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2

Bug#917504: pycoast: FTBFS (failing tests)

[Santiago Vila]

Package: src:pycoast
Version: 1.2.1+dfsg-1
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules build-indep
dh build-indep --with python2,python3,sphinxdoc --buildsystem=pybuild
   dh_update_autotools_config -i -O--buildsystem=pybuild
   dh_autoreconf -i -O--buildsystem=pybuild
   dh_auto_configure -i -O--buildsystem=pybuild
I: pybuild base:217: python2.7 setup.py config 
running config
I: pybuild base:217: python3.7 setup.py config 
running config
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>/pycoast-1.2.1+dfsg'
dh_auto_build --buildsystem=pybuild
I: pybuild base:217: /usr/bin/python setup.py build 
running build

[... snipped ...]

test_add_shapefile_shapes (pycoast.tests.test_pycoast.TestPIL) ... skipped 
'dataset not available: test_data/shapes/Metareas.shp'
test_dateline_boundary_cross (pycoast.tests.test_pycoast.TestPIL) ... ok
test_dateline_cross (pycoast.tests.test_pycoast.TestPIL) ... ok
test_europe (pycoast.tests.test_pycoast.TestPIL) ... ok
test_europe_file (pycoast.tests.test_pycoast.TestPIL) ... ok
test_geos (pycoast.tests.test_pycoast.TestPIL) ... ok
test_grid (pycoast.tests.test_pycoast.TestPIL) ... ok
test_grid_file (pycoast.tests.test_pycoast.TestPIL) ... ok
test_grid_geos (pycoast.tests.test_pycoast.TestPIL) ... ok
test_grid_nh (pycoast.tests.test_pycoast.TestPIL) ... ok
test_add_polygon_agg (pycoast.tests.test_pycoast.TestPILAGG) ... ok
test_add_shapefile_shapes_agg (pycoast.tests.test_pycoast.TestPILAGG) ... 
skipped 'dataset not available: test_data/shapes/Metareas.shp'
test_europe_agg (pycoast.tests.test_pycoast.TestPILAGG) ... ok
test_europe_agg_file (pycoast.tests.test_pycoast.TestPILAGG) ... ok
test_geos_agg (pycoast.tests.test_pycoast.TestPILAGG) ... ok
test_grid_agg (pycoast.tests.test_pycoast.TestPILAGG) ... ok
test_grid_agg_file (pycoast.tests.test_pycoast.TestPILAGG) ... ok
test_grid_agg_txt (pycoast.tests.test_pycoast.TestPILAGG) ... ERROR
test_grid_geos_agg (pycoast.tests.test_pycoast.TestPILAGG) ... ok
test_grid_nh_agg (pycoast.tests.test_pycoast.TestPILAGG) ... ERROR

==
ERROR: test_grid_agg_txt (pycoast.tests.test_pycoast.TestPILAGG)
--
Traceback (most recent call last):
  File "/<>/pycoast-1.2.1+dfsg/pycoast/tests/test_pycoast.py", line 
471, in test_grid_agg_txt
opacity=200)
IOError: cannot load font (no text renderer)

==
ERROR: test_grid_nh_agg (pycoast.tests.test_pycoast.TestPILAGG)
--
Traceback (most recent call last):
  File "/<>/pycoast-1.2.1+dfsg/pycoast/tests/test_pycoast.py", line 
543, in test_grid_nh_agg
'DejaVuSerif.ttf'), size=10)
IOError: cannot load font (no text renderer)

--
Ran 21 tests in 44.499s

FAILED (errors=2, skipped=2)
Test failed: 
error: Test failed: 
E: pybuild pybuild:338: test: plugin distutils failed with: exit code=1: 
python2.7 setup.py test 
dh_auto_test: pybuild --test -i python{version} -p 2.7 returned exit code 13
make: *** [debian/rules:13: build-indep] Error 25
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


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

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

where you can get a full build log if you need it.

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the BTS web page for this package.

Thanks.

Bug#917502: nova: FTBFS (name 'sqlite3' is not defined)

[Santiago Vila]

Package: src:nova
Version: 2:18.0.3-4
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules build-indep
pyversions: missing X(S)-Python-Version in control file, fall back to 
debian/pyversions
pyversions: missing debian/pyversions file, fall back to supported versions
py3versions: no X-Python3-Version in control file, using supported versions
dh build-indep --buildsystem=python_distutils --with python3,sphinxdoc,systemd
   dh_update_autotools_config -i -O--buildsystem=python_distutils
   dh_autoreconf -i -O--buildsystem=python_distutils
   dh_auto_configure -i -O--buildsystem=python_distutils
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.
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
pyversions: missing X(S)-Python-Version in control file, fall back to 
debian/pyversions
pyversions: missing debian/pyversions file, fall back to supported versions

[... snipped ...]

self._cache_schema()
  File "/<>/nova/tests/fixtures.py", line 607, in _cache_schema
migration.db_sync(database=self.database)
  File "/<>/nova/db/migration.py", line 26, in db_sync
return IMPL.db_sync(version=version, database=database, context=context)
  File "/<>/nova/db/sqlalchemy/migration.py", line 61, in db_sync
repository, version)
  File "/usr/lib/python3/dist-packages/migrate/versioning/api.py", line 186, in 
upgrade
return _migrate(url, repository, version, upgrade=True, err=err, **opts)
  File "", line 2, in _migrate
  File "/usr/lib/python3/dist-packages/migrate/versioning/util/__init__.py", 
line 167, in with_engine
return f(*a, **kw)
  File "/usr/lib/python3/dist-packages/migrate/versioning/api.py", line 366, in 
_migrate
schema.runchange(ver, change, changeset.step)
  File "/usr/lib/python3/dist-packages/migrate/versioning/schema.py", line 93, 
in runchange
change.run(self.engine, step)
  File "/usr/lib/python3/dist-packages/migrate/versioning/script/py.py", line 
148, in run
script_func(engine)
  File 
"/<>/nova/db/sqlalchemy/api_migrations/migrate_repo/versions/007_instance_mapping_nullable_cellid.py",
 line 22, in upgrade
instance_mapping.c.cell_id.alter(nullable=True)
  File "/usr/lib/python3/dist-packages/migrate/changeset/schema.py", line 540, 
in alter
return alter_column(self, *p, **k)
  File "/usr/lib/python3/dist-packages/migrate/changeset/schema.py", line 141, 
in alter_column
engine._run_visitor(visitorcallable, delta)
  File "/usr/lib/python3/dist-packages/sqlalchemy/engine/base.py", line 1940, 
in _run_visitor
conn._run_visitor(visitorcallable, element, **kwargs)
  File "/usr/lib/python3/dist-packages/sqlalchemy/engine/base.py", line 1549, 
in _run_visitor
**kwargs).traverse_single(element)
  File "/usr/lib/python3/dist-packages/migrate/changeset/ansisql.py", line 56, 
in traverse_single
ret = super(AlterTableVisitor, self).traverse_single(elem)
  File "/usr/lib/python3/dist-packages/sqlalchemy/sql/visitors.py", line 121, 
in traverse_single
return meth(obj, **kw)
  File "/usr/lib/python3/dist-packages/migrate/changeset/databases/sqlite.py", 
line 124, in visit_column
self.recreate_table(table,column,delta)
  File "/usr/lib/python3/dist-packages/migrate/changeset/databases/sqlite.py", 
line 99, in recreate_table
tup = sqlite3.sqlite_version_info
NameError: name 'sqlite3' is not defined


--
Ran 16500 tests in 439.425s

FAILED (failures=6571, skipped=52, expected failures=1)
make[1]: *** [debian/rules:56: override_dh_install] Error 1
make[1]: Leaving directory '/<>'
make: *** [debian/rules:8: binary-indep] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary-indep subprocess 
returned exit status 2


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

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

where you can get a full build log if you need it.

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the BTS web page for this package.

Thanks.

Bug#917494: golang-github-jaytaylor-html2text: FTBFS (failing tests)

[Santiago Vila]

Package: src:golang-github-jaytaylor-html2text
Version: 0.0~git20170918.0.0ee88d3-4
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules build-indep
dh build-indep --buildsystem=golang --with=golang
   dh_update_autotools_config -i -O--buildsystem=golang
   dh_autoreconf -i -O--buildsystem=golang
   dh_auto_configure -i -O--buildsystem=golang
   dh_auto_build -i -O--buildsystem=golang
cd obj-x86_64-linux-gnu && go install 
-gcflags=all=\"-trimpath=/<>/golang-github-jaytaylor-html2text-0.0\~git20170918.0.0ee88d3/obj-x86_64-linux-gnu/src\"
 
-asmflags=all=\"-trimpath=/<>/golang-github-jaytaylor-html2text-0.0\~git20170918.0.0ee88d3/obj-x86_64-linux-gnu/src\"
 -v -p 1 github.com/jaytaylor/html2text
errors
internal/cpu
internal/race
runtime/internal/atomic
runtime/internal/sys
runtime
sync/atomic

[... snipped ...]




Output:

+--+-+
| Row-1-Col-1-Msg1 | Row-1-Col-2 |
| Row-1-Col-1-Msg2 | |
| Row-2-Col-1  | Row-2-Col-2 |
+--+-+


Expected:

++-+
| Row-1-Col-1-Msg1   | Row-1-Col-2 |
| Row-1-Col-1-Msg2   | |
| Row-2-Col-1| Row-2-Col-2 |
++-+

=== RUN   TestStrippingLists
--- PASS: TestStrippingLists (0.00s)
=== RUN   TestLinks
--- PASS: TestLinks (0.00s)
=== RUN   TestImageAltTags
--- PASS: TestImageAltTags (0.00s)
=== RUN   TestHeadings
--- PASS: TestHeadings (0.00s)
=== RUN   TestBold
--- PASS: TestBold (0.00s)
=== RUN   TestDiv
--- PASS: TestDiv (0.00s)
=== RUN   TestBlockquotes
--- PASS: TestBlockquotes (0.00s)
=== RUN   TestIgnoreStylesScriptsHead
--- PASS: TestIgnoreStylesScriptsHead (0.00s)
=== RUN   TestText
--- PASS: TestText (0.00s)
=== RUN   TestPeriod
--- PASS: TestPeriod (0.00s)
=== RUN   Example
--- PASS: Example (0.00s)
FAIL
FAILgithub.com/jaytaylor/html2text  0.020s
dh_auto_test: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 1 
github.com/jaytaylor/html2text returned exit code 1
make: *** [debian/rules:4: build-indep] Error 1
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


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

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

where you can get a full build log if you need it.

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the BTS web page for this package.

Thanks.

Bug#917501: meson: FTBFS (failing tests)

[Santiago Vila]

Package: src:meson
Version: 0.49.0-1
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules build-indep
dh build-indep --with python3 --buildsystem=pybuild
   dh_update_autotools_config -i -O--buildsystem=pybuild
   dh_autoreconf -i -O--buildsystem=pybuild
   dh_auto_configure -i -O--buildsystem=pybuild
I: pybuild base:217: python3.7 setup.py config 
running config
   dh_auto_build -i -O--buildsystem=pybuild
I: pybuild base:217: /usr/bin/python3 setup.py build 
running build
running build_py
creating /<>/.pybuild/cpython3_3.7_meson/build/mesonbuild
copying mesonbuild/mconf.py -> 
/<>/.pybuild/cpython3_3.7_meson/build/mesonbuild
copying mesonbuild/mesonmain.py -> 
/<>/.pybuild/cpython3_3.7_meson/build/mesonbuild

[... snipped ...]

Unexpected Pass:   0
Skipped:   0
Timeout:   0

Full log written to /<>/b 8fd956165c/meson-logs/testlog.txt
No tests defined.
[0/1] /usr/bin/python3 /<>/meson.py --internal regenerate 
'/<>/test cases/nasm/1 configure file' '/<>/b 
8fd956165c' --backend ninja
The Meson build system
Version: 0.49.0
Source dir: /<>/test cases/nasm/1 configure file
Build dir: /<>/b 8fd956165c
Build type: native build
Project name: nasm config file
Project version: undefined
Native C compiler: cc (gcc 8.2.0 "cc (Debian 8.2.0-12) 8.2.0")
Build machine cpu family: x86_64
Build machine cpu: x86_64
Program nasm found: YES (/usr/bin/nasm)
Configuring config.asm using configuration
Compiler for C supports link arguments -no-pie: YES
Build targets in project: 2
Found ninja-1.8.2 at /usr/bin/ninja
[0/1] /usr/bin/python3 /<>/meson.py install --no-rebuild
[1/1] ninja -t clean
Cleaning... 3 files.


Total configuration time: 80.44s
Total build time: 352.49s
Total test time: 7.89s

Total passed tests: 412
Total failed tests: 0
Total skipped tests: 35
System information.
Architecture: ('64bit', 'ELF')
Machine: x86_64
Platform: Linux
Processor: 
System: Linux

Running unittests.

make[1]: *** [debian/rules:19: override_dh_auto_test] Error 1
make[1]: Leaving directory '/<>'
make: *** [debian/rules:15: build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


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

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

where you can get a full build log if you need it.

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the BTS web page for this package.

Thanks.

Bug#917496: keyrings.alt: FTBFS ('module' object has no attribute 'ResourceNotFoundError')

[Santiago Vila]

Package: src:keyrings.alt
Version: 3.1-1
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules build-indep
dh build-indep --with python2,python3 --buildsystem pybuild
   dh_update_autotools_config -i -O--buildsystem=pybuild
   dh_autoreconf -i -O--buildsystem=pybuild
   dh_auto_configure -i -O--buildsystem=pybuild
I: pybuild base:217: python2.7 setup.py config 
running config
I: pybuild base:217: python3.7 setup.py config 
running config
   dh_auto_build -i -O--buildsystem=pybuild
I: pybuild base:217: /usr/bin/python setup.py build 
running build
running build_py
creating /<>/.pybuild/cpython2_2.7_keyrings.alt/build/keyrings

[... snipped ...]

service = random_string(20, UNICODE_CHARS)
>   self.check_set_get(service, username, password)

/usr/lib/python2.7/dist-packages/keyring/tests/test_backend.py:113: 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
/usr/lib/python2.7/dist-packages/keyring/tests/test_backend.py:60: in 
check_set_get
assert keyring.get_password(service, username) is None
keyrings/alt/pyfs.py:181: in get_password
password_base64 = self.config.get(service, username).encode()
keyrings/alt/pyfs.py:166: in config
f = self._open()
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 

self = , mode = 'r'

def _open(self, mode='r'):
"""Open the password file in the specified mode
"""
open_file = None
writeable = 'w' in mode or 'a' in mode or '+' in mode
try:
# NOTE: currently the MemOpener does not split off any filename
#   which causes errors on close()
#   so we add a dummy name and open it separately
if (self.filename.startswith('mem://') or
self.filename.startswith('ram://')):
open_file = fs.opener.fsopendir(self.filename).open('kr.cfg',
mode)
else:
if not hasattr(self, '_pyfs'):
# reuse the pyfilesystem and path
self._pyfs, self._path = fs.opener.opener.parse(
self.filename, writeable=writeable)
# cache if permitted
if self._cache_timeout is not None:
self._pyfs = fs.remote.CacheFS(
self._pyfs, cache_timeout=self._cache_timeout)
open_file = self._pyfs.open(self._path, mode)
>   except fs.errors.ResourceNotFoundError:
E   AttributeError: 'module' object has no attribute 'ResourceNotFoundError'

keyrings/alt/pyfs.py:108: AttributeError
=== 64 failed, 23 passed, 39 skipped in 3.85 seconds ===
E: pybuild pybuild:338: test: plugin distutils failed with: exit code=1: cd 
/<>/.pybuild/cpython2_2.7_keyrings.alt/build; python2.7 -m pytest 
--ignore=keyrings/alt/_win_crypto.py --ignore=tests/test_crypto.py 
--ignore=tests/test_file.py --ignore=tests/test_Windows.py
dh_auto_test: pybuild --test --test-pytest -i python{version} -p 2.7 returned 
exit code 13
make: *** [debian/rules:13: build-indep] Error 25
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


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

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

where you can get a full build log if you need it.

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the BTS web page for this package.

Thanks.

Bug#917498: libexplain: FTBFS (failing tests)

[Santiago Vila]

Package: src:libexplain
Version: 1.4.D001-7
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules build-indep
dh build-indep --with autoreconf --no-parallel
   dh_update_autotools_config -i
   dh_autoreconf -i
configure.ac:1102: warning: AC_LANG_CONFTEST: no AC_LANG_SOURCE call detected 
in body
../../lib/autoconf/lang.m4:193: AC_LANG_CONFTEST is expanded from...
../../lib/autoconf/general.m4:2740: _AC_RUN_IFELSE is expanded from...
../../lib/m4sugar/m4sh.m4:639: AS_IF is expanded from...
../../lib/autoconf/general.m4:2759: AC_RUN_IFELSE is expanded from...
configure.ac:1102: the top level
configure.ac:1102: warning: AC_LANG_CONFTEST: no AC_LANG_SOURCE call detected 
in body
../../lib/autoconf/lang.m4:193: AC_LANG_CONFTEST is expanded from...
../../lib/autoconf/general.m4:2740: _AC_RUN_IFELSE is expanded from...
../../lib/m4sugar/m4sh.m4:639: AS_IF is expanded from...

[... snipped ...]

PASSED
PATH=`pwd`/bin:$PATH /bin/sh test/06/t0642a.sh
This system does not VIDIOCGCAP, therefore this test is declared to pass by
default.
PASSED
PATH=`pwd`/bin:$PATH /bin/sh test/06/t0643a.sh
This system does not VIDIOCGCAP, therefore this test is declared to pass by
default.
PASSED
PATH=`pwd`/bin:$PATH /bin/sh test/06/t0644a.sh
This system does not VIDIOCGCAP, therefore this test is declared to pass by
default.
PASSED
PATH=`pwd`/bin:$PATH /bin/sh test/06/t0645a.sh
This system does not VIDIOCGCAP, therefore this test is declared to pass by
default.
PASSED
PATH=`pwd`/bin:$PATH /bin/sh test/06/t0646a.sh
This system does not VIDIOCGCAP, therefore this test is declared to pass by
default.
PASSED
PATH=`pwd`/bin:$PATH /bin/sh test/06/t0648a.sh
This system does not VIDIOCGCAP, therefore this test is declared to pass by
default.
PASSED
PATH=`pwd`/bin:$PATH /bin/sh test/06/t0649a.sh
This system does not VIDIOCGCAP, therefore this test is declared to pass by
default.
PASSED
PATH=`pwd`/bin:$PATH /bin/sh test/06/t0650a.sh
This system does not VIDIOCGCAP, therefore this test is declared to pass by
default.
PASSED
PATH=`pwd`/bin:$PATH /bin/sh test/06/t0652a.sh
2,4c2,3
< the fp argument does not refer to an object that is open for writing;
< this is more likely to be a software error (a bug) than it is to be a
< user error
---
> the fildes argument does not refer to an object that is open for writing
> (O_RDONLY | O_LARGEFILE)
FAILED test of fputs("yuck", stdin);
make[1]: *** [Makefile:42571: t0652a] Error 1
make[1]: Leaving directory '/<>'
dh_auto_test: make -j1 check VERBOSE=1 returned exit code 2
make: *** [debian/rules:7: build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


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

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

where you can get a full build log if you need it.

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the BTS web page for this package.

Thanks.

Bug#917492: fam: FTBFS ('minor' was not declared in this scope)

[Santiago Vila]

Package: src:fam
Version: 2.7.0-17.2
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules build-indep
CDBS: parsing fam-2.7.0.tar.gz ...
CDBS WARNING:tarball.mk is deprecated since 0.4.85 - please use source 
format 3.0 instead
CDBS WARNING:simple-patchsys.mk is deprecated since 0.4.85 - please use 
source format 3.0 (quilt) instead
test -x debian/rules
mkdir -p "build-tree/fam-2.7.0"
CDBS WARNING:DEB_UPDATE_RCD_PARAMS is deprecated since 0.4.85
tar -C build-tree  -x -z -f fam-2.7.0.tar.gz
touch debian/stamp-fam-2.7.0.tar.gz
if test -e /usr/share/misc/config.guess ; then \
for i in fam-2.7.0/config.guess ; do \
cp --remove-destination /usr/share/misc/config.guess \
build-tree/$i ; \
done ; \

[... snipped ...]

 ^
DNotify.c++:536:32: error: 'minor' was not declared in this scope
 major(status->st_dev), minor(status->st_dev),
^
DNotify.c++:536:32: note: suggested alternative: 'mknod'
 major(status->st_dev), minor(status->st_dev),
^
mknod
DNotify.c++:486:9: warning: unused variable 'res' [-Wunused-variable]
 int res;
 ^~~
DNotify.c++: In static member function 'static void DNotify::read_handler(int, 
void*)':
DNotify.c++:641:11: error: 'major' was not declared in this scope
   major(dw->dir_dev), minor(dw->dir_dev), dw->dir_ino);
   ^
DNotify.c++:641:31: error: 'minor' was not declared in this scope
   major(dw->dir_dev), minor(dw->dir_dev), dw->dir_ino);
   ^
DNotify.c++:641:31: note: suggested alternative: 'mknod'
   major(dw->dir_dev), minor(dw->dir_dev), dw->dir_ino);
   ^
   mknod
DNotify.c++:602:16: warning: unused variable 'fw' [-Wunused-variable]
 FileWatch *fw;
^~
DNotify.c++: In static member function 'static void 
DNotify::overflow_signal_handler(int, siginfo_t*, void*)':
DNotify.c++:233:11: warning: ignoring return value of 'ssize_t write(int, const 
void*, size_t)', declared with attribute warn_unused_result [-Wunused-result]
 write (STDERR_FILENO, str, strlen(str));
 ~~^
DNotify.c++:239:12: warning: ignoring return value of 'ssize_t write(int, const 
void*, size_t)', declared with attribute warn_unused_result [-Wunused-result]
   write(pipe_write_fd, , 1);
   ~^~
DNotify.c++: In static member function 'static void 
DNotify::signal_handler(int, siginfo_t*, void*)':
DNotify.c++:260:8: warning: ignoring return value of 'ssize_t write(int, const 
void*, size_t)', declared with attribute warn_unused_result [-Wunused-result]
  write (STDERR_FILENO, str, strlen(str));
  ~~^
DNotify.c++:270:12: warning: ignoring return value of 'ssize_t write(int, const 
void*, size_t)', declared with attribute warn_unused_result [-Wunused-result]
   write(pipe_write_fd, , 1);
   ~^~
make[3]: *** [Makefile:453: DNotify.o] Error 1
make[3]: Leaving directory '/<>/build-tree/fam-2.7.0/src'
make[2]: *** [Makefile:327: all-recursive] Error 1
make[2]: Leaving directory '/<>/build-tree/fam-2.7.0'
make[1]: *** [Makefile:258: all] Error 2
make[1]: Leaving directory '/<>/build-tree/fam-2.7.0'
make: *** [/usr/share/cdbs/1/class/makefile.mk:77: debian/stamp-makefile-build] 
Error 2
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


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

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

where you can get a full build log if you need it.

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the BTS web page for this package.

Thanks.

Bug#917491: debian-installer-netboot-images: FTBFS (BAD signature from "Debian Archive Automatic Signing Key (8/jessie) ")

[Santiago Vila]

Package: src:debian-installer-netboot-images
Version: 20170615+deb9u5
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules build-indep
dh build-indep
   dh_update_autotools_config -i
 fakeroot debian/rules binary-indep
dh binary-indep
   dh_testroot -i
   dh_prep -i
   debian/rules override_dh_auto_install
make[1]: Entering directory 
'/<>/debian-installer-netboot-images-20170615+deb9u5'
if ! ./get-images.sh amd64 && [ -n "stretch" ]; then\
echo; echo; echo; \
echo "Version not found in stretch-proposed-updates, falling back to 
stretch"; \
echo; echo; echo; \
sleep 5; \

[... snipped ...]




--2018-12-20 03:03:08--  http://deb.debian.org/debian/dists/stretch/Release.gpg
Resolving deb.debian.org (deb.debian.org)... 149.20.4.15, 130.89.148.14, 
128.31.0.62, ...
Connecting to deb.debian.org (deb.debian.org)|149.20.4.15|:80... connected.
HTTP request sent, awaiting response... 302 Found
Location: http://cdn-fastly.deb.debian.org/debian/dists/stretch/Release.gpg 
[following]
--2018-12-20 03:03:08--  
http://cdn-fastly.deb.debian.org/debian/dists/stretch/Release.gpg
Resolving cdn-fastly.deb.debian.org (cdn-fastly.deb.debian.org)... 
151.101.120.204, 2a04:4e42:1d::204
Connecting to cdn-fastly.deb.debian.org 
(cdn-fastly.deb.debian.org)|151.101.120.204|:80... connected.
HTTP request sent, awaiting response... 206 Partial Content
Length: 2434 (2.4K), 833 remaining
Saving to: 
'/<>/debian-installer-netboot-images-20170615+deb9u5/Release.gpg'

 0K ,.100% 44.9M=0s

2018-12-20 03:03:08 (44.9 MB/s) - 
'/<>/debian-installer-netboot-images-20170615+deb9u5/Release.gpg' 
saved [2434/2434]

--2018-12-20 03:03:08--  http://deb.debian.org/debian/dists/stretch/Release
Resolving deb.debian.org (deb.debian.org)... 149.20.4.15, 130.89.148.14, 
128.31.0.62, ...
Connecting to deb.debian.org (deb.debian.org)|149.20.4.15|:80... connected.
HTTP request sent, awaiting response... 302 Found
Location: http://cdn-fastly.deb.debian.org/debian/dists/stretch/Release 
[following]
--2018-12-20 03:03:08--  
http://cdn-fastly.deb.debian.org/debian/dists/stretch/Release
Resolving cdn-fastly.deb.debian.org (cdn-fastly.deb.debian.org)... 
151.101.120.204, 2a04:4e42:1d::204
Connecting to cdn-fastly.deb.debian.org 
(cdn-fastly.deb.debian.org)|151.101.120.204|:80... connected.
HTTP request sent, awaiting response... 206 Partial Content
Length: 117946 (115K), 23339 (23K) remaining
Saving to: 
'/<>/debian-installer-netboot-images-20170615+deb9u5/Release'

[ skipping 50K ]
50K ,, ,, ,, ,, ,, 86% 2.13G 0s
   100K .. .  100% 16.8M=0.001s

2018-12-20 03:03:08 (24.6 MB/s) - 
'/<>/debian-installer-netboot-images-20170615+deb9u5/Release' saved 
[117946/117946]

gpgv: Signature made Wed Dec 19 20:22:50 2018 UTC
gpgv:using RSA key A1BD8E9D78F7FE5C3E65D8AF8B48AD6246925553
gpgv: Can't check signature: No public key
gpgv: Signature made Wed Dec 19 20:22:50 2018 UTC
gpgv:using RSA key 126C0D24BD8A2942CC7DF8AC7638D0442B90D010
gpgv: BAD signature from "Debian Archive Automatic Signing Key (8/jessie) 
"
make[1]: *** [debian/rules:20: get-images-amd64] Error 1
make[1]: Leaving directory 
'/<>/debian-installer-netboot-images-20170615+deb9u5'
make: *** [debian/rules:15: binary-indep] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary-indep subprocess 
returned exit status 2


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

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/debian-installer-netboot-images.html

where you can get a full build log if you need it.

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the BTS web page for this package.

Thanks.

Bug#917493: fenix: FTBFS (conflicting types for 'fmul')

[Santiago Vila]

Package: src:fenix
Version: 0.92a.dfsg1-11.1
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules build-indep
dh build-indep --with autotools_dev
dh: Compatibility levels before 9 are deprecated (level 8 in use)
dh: The autotools-dev sequence is deprecated and replaced by dh in debhelper 
(>= 9.20160115)
dh: This feature will be removed in compat 12.
   dh_update_autotools_config -i
   dh_autotools-dev_updateconfig -i
dh_autotools-dev_updateconfig: Compatibility levels before 9 are deprecated 
(level 8 in use)
dh_autotools-dev_updateconfig: dh_autotools-dev_updateconfig is deprecated; 
please see dh_autotools-dev_updateconfig(1) for a replacement
dh_autotools-dev_updateconfig: This feature will be removed in compat 12.
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
chmod +x configure
dh_auto_configure -- \

[... snipped ...]

^
i_func.c: In function 'fxi_regex':
i_func.c:4360:25: warning: unsigned conversion from 'int' to 'unsigned char:2' 
changes value from '16' to '0' [-Woverflow]
 pb.regs_allocated = 16;
 ^~
i_func.c: In function 'fxi_regex_replace':
i_func.c:4448:25: warning: unsigned conversion from 'int' to 'unsigned char:2' 
changes value from '16' to '0' [-Woverflow]
 pb.regs_allocated = 16;
 ^~
i_func.c: In function 'fxi_split':
i_func.c:4585:26: warning: cast to pointer from integer of different size 
[-Wint-to-pointer-cast]
 int * result_array = (int *)params[2];
  ^
i_func.c:4602:25: warning: unsigned conversion from 'int' to 'unsigned char:2' 
changes value from '16' to '0' [-Woverflow]
 pb.regs_allocated = 16;
 ^~
i_func.c: In function 'fxi_join':
i_func.c:4652:26: warning: cast to pointer from integer of different size 
[-Wint-to-pointer-cast]
 int * string_array = (int *)params[1];
  ^
i_func.c: In function 'fxi_copy_struct':
i_func.c:5008:29: warning: cast to pointer from integer of different size 
[-Wint-to-pointer-cast]
 return (int) copytypes ((void *)params[0], (void *)params[1], (DCB_TYPEDEF 
*)params[2], params[3], params[4]);
 ^
i_func.c:5008:48: warning: cast to pointer from integer of different size 
[-Wint-to-pointer-cast]
 return (int) copytypes ((void *)params[0], (void *)params[1], (DCB_TYPEDEF 
*)params[2], params[3], params[4]);
^
i_func.c:5008:67: warning: cast to pointer from integer of different size 
[-Wint-to-pointer-cast]
 return (int) copytypes ((void *)params[0], (void *)params[1], (DCB_TYPEDEF 
*)params[2], params[3], params[4]);
   ^
In file included from ../inc/fxi.h:58,
 from i_func.c:62:
At top level:
../inc/fmath.h:129:16: warning: 'fdiv' defined but not used [-Wunused-function]
 __INLINE fixed fdiv(int x, int y)
^~~~
make[4]: *** [Makefile:345: i_func.o] Error 1
make[4]: Leaving directory '/<>/fxi/src'
make[3]: *** [Makefile:174: all-recursive] Error 1
make[3]: Leaving directory '/<>/fxi'
make[2]: *** [Makefile:196: all-recursive] Error 1
make[2]: Leaving directory '/<>'
dh_auto_build: make -j1 "CFLAGS=-g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wall 
-fno-strict-aliasing -DUSE_GETTEXT" returned exit code 2
make[1]: *** [debian/rules:31: override_dh_auto_build] Error 2
make[1]: Leaving directory '/<>'
make: *** [debian/rules:65: build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


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

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

where you can get a full build log if you need it.

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the BTS web page for this package.

Thanks.

Bug#917489: buildbot: FTBFS (name 'sqlite3' is not defined)

[Santiago Vila]

Package: src:buildbot
Version: 1.6.0-1
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules build-indep
dh build-indep --with python3,bash-completion,sphinxdoc
   dh_update_autotools_config -i
   dh_autoreconf -i
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
dh_auto_configure --buildsystem=pybuild --sourcedirectory=master \
--package=python3-buildbot -- --name=buildbot
pybuild --configure -i python{version} -p 3.7 --name=buildbot --dir 
master
I: pybuild base:217: python3.7 setup.py config 
running config
/usr/lib/python3/dist-packages/setuptools/dist.py:470: UserWarning: Normalizing 
'1.6.0-1' to '1.6.0.post1'
  normalized_version,
dh_auto_configure --buildsystem=pybuild --sourcedirectory=worker \

[... snipped ...]

  File 
"/<>/debian/python3-buildbot/usr/lib/python3.7/dist-packages/buildbot/db/migrate/versions/050_cascading_deletes_all.py",
 line 58, in upgrade
fk.drop()
  File "/usr/lib/python3/dist-packages/migrate/changeset/constraint.py", line 
59, in drop
self.__do_imports('constraintdropper', *a, **kw)
  File "/usr/lib/python3/dist-packages/migrate/changeset/constraint.py", line 
32, in __do_imports
run_single_visitor(engine, visitorcallable, self, *a, **kw)
  File "/usr/lib/python3/dist-packages/migrate/changeset/databases/visitor.py", 
line 85, in run_single_visitor
fn(element, **kwargs)
  File "/usr/lib/python3/dist-packages/migrate/changeset/databases/sqlite.py", 
line 211, in visit_migrate_foreign_key_constraint
self.recreate_table(p[0].table, omit_constraints=[p[0].name])
  File "/usr/lib/python3/dist-packages/migrate/changeset/databases/sqlite.py", 
line 99, in recreate_table
tup = sqlite3.sqlite_version_info
builtins.NameError: name 'sqlite3' is not defined

buildbot.test.unit.test_db_migrate_versions_050_cascading_deletes_all.Migration.test_update
---
Ran 5578 tests in 56.221s

FAILED (skips=303, errors=16, successes=5267)
/usr/lib/python3/dist-packages/sqlalchemy/util/langhelpers.py:374: 
DeprecationWarning: `formatargspec` is deprecated since Python 3.5. Use 
`signature` and the `Signature` object directly
  args = inspect.formatargspec(*spec)
/usr/lib/python3/dist-packages/sqlalchemy/util/langhelpers.py:384: 
DeprecationWarning: `formatargspec` is deprecated since Python 3.5. Use 
`signature` and the `Signature` object directly
  spec[2], None, spec[4])
/usr/lib/python3/dist-packages/sqlalchemy/util/langhelpers.py:405: 
DeprecationWarning: `formatargspec` is deprecated since Python 3.5. Use 
`signature` and the `Signature` object directly
  formatvalue=lambda x: '=' + x)
/usr/lib/python3/dist-packages/sqlalchemy/engine/result.py:182: 
DeprecationWarning: Using or importing the ABCs from 'collections' instead of 
from 'collections.abc' is deprecated, and in 3.8 it will stop working
  from collections import Sequence
/usr/lib/python3/dist-packages/sqlalchemy/util/langhelpers.py:374: 
DeprecationWarning: `formatargspec` is deprecated since Python 3.5. Use 
`signature` and the `Signature` object directly
  args = inspect.formatargspec(*spec)
/usr/lib/python3/dist-packages/sqlalchemy/util/langhelpers.py:384: 
DeprecationWarning: `formatargspec` is deprecated since Python 3.5. Use 
`signature` and the `Signature` object directly
  spec[2], None, spec[4])
/usr/lib/python3/dist-packages/sqlalchemy/util/langhelpers.py:405: 
DeprecationWarning: `formatargspec` is deprecated since Python 3.5. Use 
`signature` and the `Signature` object directly
  formatvalue=lambda x: '=' + x)
Exception ignored in: 
RuntimeError: generator ignored GeneratorExit
Exception ignored in: 
RuntimeError: generator ignored GeneratorExit
Exception ignored in: 
RuntimeError: generator ignored GeneratorExit
Exception ignored in: <_io.FileIO name='/dev/null' mode='rb' closefd=True>
ResourceWarning: unclosed file <_io.TextIOWrapper name='/dev/null' mode='r' 
encoding='UTF-8'>
E: pybuild pybuild:338: test: plugin custom failed with: exit code=1: 
PYTHONPATH=/<>/pkg:/<>/debian/python3-buildbot//usr/lib/python3.7/dist-packages:/<>/debian/python3-buildbot-worker//usr/lib/python3.7/dist-packages
 LC_ALL=C.UTF-8 trial3 --reporter=text buildbot.test buildbot_worker.test
dh_auto_test: pybuild --test -i python{version} -p 3.7 --system=custom 
"--test-args=PYTHONPATH=/<>/pkg:/<>/debian/python3-buildbot/{install_dir}:/<>/debian/python3-buildbot-worker/{install_dir}
 LC_ALL=C.UTF-8 trial3 --reporter=text buildbot.test buildbot_worker.test" 
returned exit code 13
make[1]: *** [debian/rules:31: override_dh_auto_install] Error 25
make[1]: Leaving directory '/<>'
make: *** [debian/rules:55: binary-indep] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary-indep subprocess 
returned exit status 2

Bug#917497: libanyevent-termkey-perl: FTBFS (failing tests)

[Santiago Vila]

Package: src:libanyevent-termkey-perl
Version: 0.02-2
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules build-indep
dh build-indep
   dh_update_autotools_config -i
   dh_auto_configure -i
perl -I. Build.PL --installdirs vendor --config "optimize=-g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2" --config 
"ld=x86_64-linux-gnu-gcc -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wl,-z,relro"
Created MYMETA.yml and MYMETA.json
Creating new 'Build' script for 'AnyEvent-TermKey' version '0.02'
   dh_auto_build -i
perl Build
Building AnyEvent-TermKey
   debian/rules override_dh_auto_test
make[1]: Entering directory '/<>'
TERM=vt100 dh_auto_test
perl Build test --verbose 1
t/00use.t .. 
1..1
ok 1 - use AnyEvent::TermKey;
ok
t/01passthrough.t .. 
1..7
Failed 7/7 subtests 
t/02on_key.t ... 
1..6
ok 1 - $key->termkey after h
ok 2 - $key->type_is_unicode after h
ok 3 - $key->codepoint after h
ok 4 - $key->modifiers after h
ok 5 - $key->utf8 after h
ok 6 - $key->format after h
ok
t/03timeout.t .. 
1..4
ok 1 - $key still not defined after 1/2 waittime
ok 2 - $key->type_is_keysym after Escape timeout
ok 3 - $key->keysym after Escape timeout
ok 4 - $key->modifiers after Escape timeout
ok
t/99pod.t .. skipped: Test::Pod 1.00 required for testing POD

Test Summary Report
---
t/01passthrough.t (Wstat: 11 Tests: 0 Failed: 0)
  Non-zero wait status: 11
  Parse errors: Bad plan.  You planned 7 tests but ran 0.
Files=5, Tests=11,  1 wallclock secs ( 0.07 usr  0.01 sys +  0.73 cusr  0.12 
csys =  0.93 CPU)
Result: FAIL
Failed 1/5 test programs. 0/11 subtests failed.
dh_auto_test: perl Build test --verbose 1 returned exit code 255
make[1]: *** [debian/rules:7: override_dh_auto_test] Error 2
make[1]: Leaving directory '/<>'
make: *** [debian/rules:4: build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


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

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/libanyevent-termkey-perl.html

where you can get a full build log if you need it.

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the BTS web page for this package.

Thanks.

Bug#917495: hhsuite: FTBFS ('ffsort_index' was not declared in this scope)

[Santiago Vila]

Package: src:hhsuite
Version: 3.0~beta3+dfsg-1
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules build-indep
dh build-indep --builddirectory=mybuild
   dh_update_autotools_config -i -O--builddirectory=mybuild
   dh_autoreconf -i -O--builddirectory=mybuild
   dh_auto_configure -i -O--builddirectory=mybuild
cd mybuild && 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 ..
-- The CXX 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
-- Compiler is GNU 

[... snipped ...]

make[1]: Entering directory '/<>/hhsuite-3.0~beta3+dfsg'
dh_auto_build -- NO_PNG=1
cd mybuild && make -j1 NO_PNG=1
make[2]: Entering directory '/<>/hhsuite-3.0~beta3+dfsg/mybuild'
/usr/bin/cmake -S"/<>/hhsuite-3.0~beta3+dfsg" 
-B"/<>/hhsuite-3.0~beta3+dfsg/mybuild" --check-build-system 
CMakeFiles/Makefile.cmake 0
/usr/bin/cmake -E cmake_progress_start 
"/<>/hhsuite-3.0~beta3+dfsg/mybuild/CMakeFiles" 
"/<>/hhsuite-3.0~beta3+dfsg/mybuild/CMakeFiles/progress.marks"
make -f CMakeFiles/Makefile2 all
make[3]: Entering directory '/<>/hhsuite-3.0~beta3+dfsg/mybuild'
make -f src/CMakeFiles/A3M_COMPRESS_OBJECT.dir/build.make 
src/CMakeFiles/A3M_COMPRESS_OBJECT.dir/depend
make[4]: Entering directory '/<>/hhsuite-3.0~beta3+dfsg/mybuild'
cd "/<>/hhsuite-3.0~beta3+dfsg/mybuild" && /usr/bin/cmake -E 
cmake_depends "Unix Makefiles" "/<>/hhsuite-3.0~beta3+dfsg" 
"/<>/hhsuite-3.0~beta3+dfsg/src" 
"/<>/hhsuite-3.0~beta3+dfsg/mybuild" 
"/<>/hhsuite-3.0~beta3+dfsg/mybuild/src" 
"/<>/hhsuite-3.0~beta3+dfsg/mybuild/src/CMakeFiles/A3M_COMPRESS_OBJECT.dir/DependInfo.cmake"
 --color=
Scanning dependencies of target A3M_COMPRESS_OBJECT
make[4]: Leaving directory '/<>/hhsuite-3.0~beta3+dfsg/mybuild'
make -f src/CMakeFiles/A3M_COMPRESS_OBJECT.dir/build.make 
src/CMakeFiles/A3M_COMPRESS_OBJECT.dir/build
make[4]: Entering directory '/<>/hhsuite-3.0~beta3+dfsg/mybuild'
[  1%] Building CXX object 
src/CMakeFiles/A3M_COMPRESS_OBJECT.dir/a3m_compress.cpp.o
cd "/<>/hhsuite-3.0~beta3+dfsg/mybuild/src" && /usr/bin/c++  -DOPENMP 
-DSSE -I"/<>/hhsuite-3.0~beta3+dfsg/src" 
-I"/<>/hhsuite-3.0~beta3+dfsg/src/cs" 
-I"/<>/hhsuite-3.0~beta3+dfsg/mybuild"  -g -O2 
-fdebug-prefix-map=/<>/hhsuite-3.0~beta3+dfsg=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2  -march=native -msse4.2 -mfpmath=sse -fopenmp 
-fno-strict-aliasing   -o CMakeFiles/A3M_COMPRESS_OBJECT.dir/a3m_compress.cpp.o 
-c "/<>/hhsuite-3.0~beta3+dfsg/src/a3m_compress.cpp"
make[4]: Leaving directory '/<>/hhsuite-3.0~beta3+dfsg/mybuild'
[  1%] Built target A3M_COMPRESS_OBJECT
make -f src/CMakeFiles/a3m_database_filter.dir/build.make 
src/CMakeFiles/a3m_database_filter.dir/depend
make[4]: Entering directory '/<>/hhsuite-3.0~beta3+dfsg/mybuild'
cd "/<>/hhsuite-3.0~beta3+dfsg/mybuild" && /usr/bin/cmake -E 
cmake_depends "Unix Makefiles" "/<>/hhsuite-3.0~beta3+dfsg" 
"/<>/hhsuite-3.0~beta3+dfsg/src" 
"/<>/hhsuite-3.0~beta3+dfsg/mybuild" 
"/<>/hhsuite-3.0~beta3+dfsg/mybuild/src" 
"/<>/hhsuite-3.0~beta3+dfsg/mybuild/src/CMakeFiles/a3m_database_filter.dir/DependInfo.cmake"
 --color=
Scanning dependencies of target a3m_database_filter
make[4]: Leaving directory '/<>/hhsuite-3.0~beta3+dfsg/mybuild'
make -f src/CMakeFiles/a3m_database_filter.dir/build.make 
src/CMakeFiles/a3m_database_filter.dir/build
make[4]: Entering directory '/<>/hhsuite-3.0~beta3+dfsg/mybuild'
[  2%] Building CXX object 
src/CMakeFiles/a3m_database_filter.dir/a3m_database_filter.cpp.o
cd "/<>/hhsuite-3.0~beta3+dfsg/mybuild/src" && /usr/bin/c++  -DOPENMP 
-DSSE -I"/<>/hhsuite-3.0~beta3+dfsg/src" 
-I"/<>/hhsuite-3.0~beta3+dfsg/src/cs" 
-I"/<>/hhsuite-3.0~beta3+dfsg/mybuild"  -g -O2 
-fdebug-prefix-map=/<>/hhsuite-3.0~beta3+dfsg=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2  -march=native -msse4.2 -mfpmath=sse -fopenmp 
-fno-strict-aliasing   -o 
CMakeFiles/a3m_database_filter.dir/a3m_database_filter.cpp.o -c 
"/<>/hhsuite-3.0~beta3+dfsg/src/a3m_database_filter.cpp"
/<>/hhsuite-3.0~beta3+dfsg/src/a3m_database_filter.cpp: In function 
'int main(int, char**)':
/<>/hhsuite-3.0~beta3+dfsg/src/a3m_database_filter.cpp:206:3: error: 
'ffsort_index' was not declared in this scope
   ffsort_index(oa3mIndexFile.c_str());
   ^~~~
/<>/hhsuite-3.0~beta3+dfsg/src/a3m_database_filter.cpp:206:3: note: 
suggested alternative: 

Bug#917490: coccinelle: FTBFS (LaTeX Error: Option clash for package color)

[Santiago Vila]

Package: src:coccinelle
Version: 1.0.4.deb-3
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules build-indep
dh build-indep --with ocaml,python2 --parallel
dh: Compatibility levels before 9 are deprecated (level 8 in use)
   dh_update_autotools_config -i -O--parallel
   dh_ocamlinit -i -O--parallel
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
./configure --prefix=/usr --sysconfdir=/etc --libdir=/usr/lib --enable-ocaml 
--enable-release
configure: configuring coccinelle 1.0.4 in /<>
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... no
checking for mawk... mawk

[... snipped ...]

(/usr/share/texlive/texmf-dist/tex/generic/xypic/xypdf-fr.tex loaded)
Xy-pic pdf driver: `line' extension support
(/usr/share/texlive/texmf-dist/tex/generic/xypic/xypdf-li.tex loaded)
Xy-pic pdf driver: `rotate' extension support
(/usr/share/texlive/texmf-dist/tex/generic/xypic/xypdf-ro.tex loaded) loaded))
(/usr/share/texlive/texmf-dist/tex/latex/fancyvrb/fancyvrb.sty
Style option: `fancyvrb' v3.1a <2018/11/20> (tvz)
(/usr/share/texlive/texmf-dist/tex/latex/xcolor/xcolor.sty
(/usr/share/texlive/texmf-dist/tex/latex/graphics-cfg/color.cfg)))
(/usr/share/texlive/texmf-dist/tex/latex/moreverb/moreverb.sty
(/usr/share/texlive/texmf-dist/tex/latex/tools/verbatim.sty))
(/usr/share/texlive/texmf-dist/tex/latex/base/alltt.sty)
(/usr/share/texlive/texmf-dist/tex/latex/boxedminipage/boxedminipage.sty)
(/usr/share/texlive/texmf-dist/tex/latex/tools/xspace.sty)
(/usr/share/texlive/texmf-dist/tex/latex/endnotes/endnotes.sty)
(/usr/share/texlive/texmf-dist/tex/latex/multirow/multirow.sty)
(/usr/share/texlive/texmf-dist/tex/latex/listings/listings.sty
(/usr/share/texlive/texmf-dist/tex/latex/listings/lstmisc.sty)
(/usr/share/texlive/texmf-dist/tex/latex/listings/listings.cfg))
(/usr/share/texlive/texmf-dist/tex/latex/hyperref/hyperref.sty
(/usr/share/texlive/texmf-dist/tex/generic/oberdiek/hobsub-hyperref.sty
(/usr/share/texlive/texmf-dist/tex/generic/oberdiek/hobsub-generic.sty))
(/usr/share/texlive/texmf-dist/tex/generic/ifxetex/ifxetex.sty)
(/usr/share/texlive/texmf-dist/tex/latex/oberdiek/auxhook.sty)
(/usr/share/texlive/texmf-dist/tex/latex/oberdiek/kvoptions.sty)
(/usr/share/texlive/texmf-dist/tex/latex/hyperref/pd1enc.def)
(/usr/share/texlive/texmf-dist/tex/latex/latexconfig/hyperref.cfg)
(/usr/share/texlive/texmf-dist/tex/latex/url/url.sty))
(/usr/share/texlive/texmf-dist/tex/latex/hyperref/hpdftex.def
(/usr/share/texlive/texmf-dist/tex/latex/oberdiek/rerunfilecheck.sty))

! LaTeX Error: Option clash for package color.

See the LaTeX manual or LaTeX Companion for explanation.
Type  H   for immediate help.
 ...  
  
l.57 
 
!  ==> Fatal error occurred, no output PDF file produced!
Transcript written on manual.log.
make[2]: *** [Makefile:35: manual.pdf] Error 1
make[2]: Leaving directory '/<>/docs/manual'
make[1]: *** [debian/rules:36: override_dh_auto_build-indep] Error 2
make[1]: Leaving directory '/<>'
make: *** [debian/rules:18: build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


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

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

where you can get a full build log if you need it.

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the BTS web page for this package.

Thanks.

Bug#906865: xul-ext-refcontrol no longer works with firefox-esr 60

[Moritz Mühlenhoff]

On Sat, Sep 08, 2018 at 03:42:28PM +0800, Paul Wise wrote:
> On Tue, 21 Aug 2018 21:19:52 +0300 Adrian Bunk wrote:
> 
> > Package: xul-ext-refcontrol
> > 
> > XUL addons are no longer supported.
> 
> I think it should be removed from Debian in favour of this:
> 
> https://addons.mozilla.org/en-US/firefox/addon/referer-modifier/

I filed a removal bug now.

Cheers,
Moritz

Bug#864820: xul-ext-greasemonkey: userscripts no longer available with firefox 54

[Moritz Mühlenhoff]

On Tue, Dec 04, 2018 at 12:09:59AM +0100, Moritz Mühlenhoff wrote:
> On Thu, Jun 15, 2017 at 01:02:47PM +0200, Ingo Saitz wrote:
> > Package: xul-ext-greasemonkey
> > Version: 3.8-1
> > Severity: important
> > 
> > Dear Maintainer,
> > 
> > After updating firefox to version 54.0, the list of userscripts in
> > about:addons is empty, and the installed scripts aren't applied to the
> > webpages anymore. This seems to be issue #2488 in greasemonkey, which is
> > solved in version 3.11 of greasemonkey.
> > 
> > https://github.com/greasemonkey/greasemonkey/issues/2488
> > 
> > When started from a terminal, firefox outputs the following error:
> > 
> > 1497523208324   addons.manager  ERROR   Exception calling provider 
> > .getAddonsByTypes: TypeError: GM_util.getPreferredLocale 
> > is not a function (chrome://greasemonkey-modules/content/script.js:148:9) 
> > JS Stack trace: getbestlocalizat...@script.js:148:9 < 
> > script_getlocalizeddescript...@script.js:156:20 < 
> > scriptad...@addons4.js:98:3 < scriptaddonfactorybyscr...@addons4.js:74:28 < 
> > AddonProvider_getAddonsByTypes/<@addons4.js:50:27 < 
> > addonprovider_getaddonsbyty...@addons4.js:49:7 < 
> > callprovideras...@addonmanager.jsm:298:12 < 
> > promiseCallProvider/<@AddonManager.jsm:322:53 < 
> > prom...@promise-backend.js:390:5 < 
> > promisecallprovi...@addonmanager.jsm:321:10 < 
> > getAddonsByTypes/<@AddonManager.jsm:2556:36
> > 
> > Also, setting intl.locale.matchOS to false does get the scripts working
> > again. But since the default in firefox is true, this should only be a
> > workaround an greasemonkey should be updated to a fixed version.
> 
> There's a web extension compatible with current releases (4.7), but
> this package wasn't updated for a long time.
> 
> Does anyone intend/plan to switch the package to the web extension?
> Otherwise it should be removed from the archive.

I've filed a removal bug now. The web extension can still be packaged
independantly.

Cheers,
Moritz
 

Bug#917485: ckermit: please rebuild Stretch against new OpenSSL

[Jonathan Lane]

Package: ckermit
Version: 302-5.3
Severity: grave
Tags: security
Justification: user security hole

Dear Maintainer,

Please rebuild C-Kermit against the new OpenSSL in Stretch.  Currently all 
SSL/TLS functionality in C-Kermit is disabled due to detecting mismatching 
libraries.


-- System Information:
Debian Release: 9.6
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: arm64 (aarch64)

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

Versions of packages ckermit depends on:
ii  debconf [debconf-2.0]  1.5.61
ii  libc6  2.24-11+deb9u3
ii  libcomerr2 1.43.4-2
ii  libgssapi-krb5-2   1.15-1+deb9u1
ii  libk5crypto3   1.15-1+deb9u1
ii  libkrb5-3  1.15-1+deb9u1
ii  libncurses56.0+20161126-1+deb9u2
ii  libpam0g   1.1.8-3.6
ii  libssl1.0.21.0.2q-1~deb9u1
ii  libtinfo5  6.0+20161126-1+deb9u2

Versions of packages ckermit recommends:
ii  openbsd-inetd [inet-superserver]  0.20160825-2
ii  openssh-client [ssh-client]   1:7.4p1-10+deb9u4

ckermit suggests no packages.

-- debconf information:
  ckermit/iksd-anon: false
  ckermit/iksd-no-inetd:
  ckermit/iksd: false
  ckermit/iksd-anondir: /home/ftp

Bug#906870: xul-ext-certificatepatrol no longer works with firefox-esr 60

[Moritz Mühlenhoff]

On Sat, Sep 08, 2018 at 03:07:14PM +0800, Paul Wise wrote:
> On Tue, 21 Aug 2018 21:31:45 +0300 Adrian Bunk wrote:
> 
> > Package: xul-ext-certificatepatrol
> > Severity: serious
> > 
> > XUL addons are no longer supported.
> 
> Mozilla are still discussing if WebExtensions or NSS extensions are
> going to be allowed to access and modify TLS validation results:
> 
> https://bugzilla.mozilla.org/show_bug.cgi?id=1489080
> https://bugzilla.mozilla.org/show_bug.cgi?id=1435951

This hasn't seen any traction and the package is broken for
quite a while now, let's remove it from the archive? If some
web extension-compatible interface arises, it can still
be packaged separately.

Cheers,
Moritz

Bug#906870: xul-ext-certificatepatrol no longer works with firefox-esr 60

[Christoph Biedl]

Moritz Mühlenhoff wrote...

> On Sat, Sep 08, 2018 at 03:07:14PM +0800, Paul Wise wrote:

> > Mozilla are still discussing if WebExtensions or NSS extensions are
> > going to be allowed to access and modify TLS validation results:
> >
> > https://bugzilla.mozilla.org/show_bug.cgi?id=1489080
> > https://bugzilla.mozilla.org/show_bug.cgi?id=1435951
>
> This hasn't seen any traction and the package is broken for
> quite a while now, let's remove it from the archive? If some
> web extension-compatible interface arises, it can still
> be packaged separately.

My bit of information on this is a remark by certpatrol upstream a while
ago Firefox 62 was to introduce new API to access cert data, as
documented in


To be honest, I lack the skills to check whether this actually happened
(probably yes), and is usable to re-create certpatrol for webext
(hopefully yes). And I haven't checked yet whether certpatrol upstream
is willing to do the job. Allow me some time to resolve this.

Otherwise, I wouldn't mind to keep this in unstable for the sake of some
spin-offs/forks that still support xul, like pale moon - but I
understand if people consider this something Debian isn't intended for.

Cheers,

Christoph


signature.asc
Description: PGP signature

Bug#890804: xul-ext-tabmixplus: add WebExtensions version

[Moritz Mühlenhoff]

On Tue, Dec 04, 2018 at 12:02:55AM +0100, Moritz Mühlenhoff wrote:
> On Tue, Aug 14, 2018 at 06:12:43PM +0200, Christoph Anton Mitterer wrote:
> > Control: severity -1 grave
> > 
> > Since FF ESR 52 has now left Debian unstable, the XUL version of this
> > is no longer usable in Debian.
> > Please upgrade to the WebExtensions version ASAP.
> 
> Does anyone intend/plan to switch the package to the web extention?
> Otherwise it should be removed from the archive.

I've filed a removal bug now.

Cheers,
Moritz

Bug#917482: jhove: FTBFS in buster at least since 2018-12-07

[Santiago Vila]

Package: src:jhove
Version: 1.20.1-4
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules build-indep
dh build-indep
   dh_update_autotools_config -i
   dh_autoreconf -i
   dh_auto_configure -i
mh_patchpoms -pjhove --debian-build --keep-pom-version 
--maven-repo=/<>/debian/maven-repo
   dh_auto_build -i
/usr/lib/jvm/default-java/bin/java -noverify -cp 
/usr/share/maven/boot/plexus-classworlds-2.x.jar -Dmaven.home=/usr/share/maven 
-Dmaven.multiModuleProjectDirectory=/<> 
-Dclassworlds.conf=/etc/maven/m2-debian.conf 
-Dproperties.file.manual=/<>/debian/maven.properties 
org.codehaus.plexus.classworlds.launcher.Launcher 
-s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian 
-Dmaven.repo.local=/<>/debian/maven-repo --batch-mode package 
-DskipTests -Dnotimestamp=true -Dlocale=en_US
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by 
com.google.inject.internal.cglib.core.$ReflectUtils$1 
(file:/usr/share/maven/lib/guice.jar) to method 
java.lang.ClassLoader.defineClass(java.lang.String,byte[],int,int,java.security.ProtectionDomain)
WARNING: Please consider reporting this to the maintainers of 
com.google.inject.internal.cglib.core.$ReflectUtils$1
WARNING: Use --illegal-access=warn to enable warnings of further illegal 
reflective access operations
WARNING: All illegal access operations will be denied in a future release
[INFO] Scanning for projects...

[... snipped ...]

[INFO] JHOVE - JSTOR/Harvard Object Validation Environment  SUCCESS [  0.009 s]
[INFO] JHOVE Core . SUCCESS [  4.465 s]
[INFO] JHOVE Validation Modules ... FAILURE [  2.348 s]
[INFO] JHOVE Applications . SKIPPED
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time:  7.061 s
[INFO] Finished at: 2018-12-25T23:16:10Z
[INFO] 
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-compiler-plugin:3.8.0:compile (default-compile) 
on project jhove-modules: Compilation failure: Compilation failure: 
[ERROR] 
/<>/jhove-modules/src/main/java/edu/harvard/hul/ois/jhove/module/wave/BroadcastExtChunk.java:[13,22]
 package javax.xml.bind does not exist
[ERROR] 
/<>/jhove-modules/src/main/java/edu/harvard/hul/ois/jhove/module/wave/FormatChunk.java:[13,22]
 package javax.xml.bind does not exist
[ERROR] 
/<>/jhove-modules/src/main/java/edu/harvard/hul/ois/jhove/module/wave/BroadcastExtChunk.java:[216,29]
 cannot find symbol
[ERROR]   symbol:   variable DatatypeConverter
[ERROR]   location: class 
edu.harvard.hul.ois.jhove.module.wave.BroadcastExtChunk
[ERROR] 
/<>/jhove-modules/src/main/java/edu/harvard/hul/ois/jhove/module/wave/BroadcastExtChunk.java:[219,29]
 cannot find symbol
[ERROR]   symbol:   variable DatatypeConverter
[ERROR]   location: class 
edu.harvard.hul.ois.jhove.module.wave.BroadcastExtChunk
[ERROR] 
/<>/jhove-modules/src/main/java/edu/harvard/hul/ois/jhove/module/wave/FormatChunk.java:[261,21]
 cannot find symbol
[ERROR]   symbol:   variable DatatypeConverter
[ERROR]   location: class edu.harvard.hul.ois.jhove.module.wave.FormatChunk
[ERROR] 
/<>/jhove-modules/src/main/java/edu/harvard/hul/ois/jhove/module/wave/FormatChunk.java:[265,21]
 cannot find symbol
[ERROR]   symbol:   variable DatatypeConverter
[ERROR]   location: class edu.harvard.hul.ois.jhove.module.wave.FormatChunk
[ERROR] 
/<>/jhove-modules/src/main/java/edu/harvard/hul/ois/jhove/module/wave/FormatChunk.java:[269,21]
 cannot find symbol
[ERROR]   symbol:   variable DatatypeConverter
[ERROR]   location: class edu.harvard.hul.ois.jhove.module.wave.FormatChunk
[ERROR] 
/<>/jhove-modules/src/main/java/edu/harvard/hul/ois/jhove/module/wave/FormatChunk.java:[273,21]
 cannot find symbol
[ERROR]   symbol:   variable DatatypeConverter
[ERROR]   location: class edu.harvard.hul.ois.jhove.module.wave.FormatChunk
[ERROR] 
/<>/jhove-modules/src/main/java/edu/harvard/hul/ois/jhove/module/wave/FormatChunk.java:[277,21]
 cannot find symbol
[ERROR]   symbol:   variable DatatypeConverter
[ERROR]   location: class edu.harvard.hul.ois.jhove.module.wave.FormatChunk
[ERROR] -> [Help 1]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please 
read the following articles:
[ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
[ERROR] 
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR]   mvn  -rf :jhove-modules

Bug#915805: Should this package be removed?

[Moritz Mühlenhoff]

On Fri, Dec 07, 2018 at 01:41:47PM +, Kevin Smith wrote:
> Apologies, I’d forgotten that we’d prepared an update from upstream and not 
> gotten it submitted. We’ll try to address this in the next week or so.

What's the status :-)

Cheers,
Moritz

Bug#917483: tangerine-icon-theme: FTBFS in buster at least since 2018-12-06

[Santiago Vila]

Package: src:tangerine-icon-theme
Version: 0.26.debian-4
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]

dpkg-buildpackage
-

dpkg-buildpackage: info: source package tangerine-icon-theme
dpkg-buildpackage: info: source version 0.26.debian-4
dpkg-buildpackage: info: source distribution unstable
dpkg-buildpackage: info: source changed by Michael Biebl 
 dpkg-source --before-build .
 fakeroot debian/rules clean
CDBS WARNING:simple-patchsys.mk is deprecated since 0.4.85 - please use 
source format 3.0 (quilt) instead
debian/rules:7: /usr/share/gnome-pkg-tools/1/rules/ubuntu-get-source.mk: No 
such file or directory
make: *** No rule to make target 
'/usr/share/gnome-pkg-tools/1/rules/ubuntu-get-source.mk'.  Stop.
dpkg-buildpackage: error: fakeroot debian/rules clean subprocess returned exit 
status 2


The build was made in my autobuilder with "dpkg-buildpackage -A"
but I don't think such detail is really relevant.

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the BTS web page for this package.

Thanks.

Bug#853992: xul-ext-requestpolicy: update requestpolicy to 1.0 beta12.4 - compatibility with web extensions

[Moritz Mühlenhoff]

On Sat, Sep 08, 2018 at 03:45:20PM +0800, Paul Wise wrote:
> Control: forwarded -1 
> https://github.com/RequestPolicyContinued/requestpolicy/issues/704
> Control: tags -1 + fixed-upstream # partially
> 
> On Fri, 3 Feb 2017 03:00:02 +0530 shirish शिरीष wrote:
> 
> > First of all thank you for taking care of xul-ext-requestpolicy for so
> > long. Was just browsing today and saw that 1.0beta12.4 was introduced
> > few months back. The only addition according to the changelog
> > https://github.com/RequestPolicyContinued/requestpolicy/blob/dev-1.0/ChangeLog.md
> > 
> > is being compatible with WebExtensions which Mozilla is going to come
> > up in the next few releases.
> 
> This has now happened and upstream has partially fixed this,
> status is at the listedURL above.

The current package is broken for a long time now and hasn't seen
an upload since 2016. Does anyone intent to package the web extension?
Otherwise the package should be removed.

Cheers,
Moritz

Bug#881894: xul-ext-cookie-monster: dead upstream, broken in FF57

[Moritz Mühlenhoff]

On Wed, Oct 03, 2018 at 05:20:16PM +0200, Moritz Mühlenhoff wrote:
> On Thu, Nov 16, 2017 at 06:21:56AM +0100, Christoph Anton Mitterer wrote:
> > Package: xul-ext-cookie-monster
> > Version: 1.3.0.5-1
> > Severity: normal
> > 
> > 
> > 
> > Hi.
> > 
> > Seems this addon is dead upstream (at least:
> > https://addons.mozilla.org/en-US/firefox/addon/cookie-monster/
> > says "This add-on has been removed by its author.").
> > 
> > Also it won't work with FF >57 anymore.
> 
> Let's remove it from the archive?

I've filed a removal bug now.

Cheers,
Moritz

Bug#917273: marked as done (overwritting files from libservlet2.5-java)

[Debian Bug Tracking System]

Your message dated Thu, 27 Dec 2018 22:34:03 +
with message-id 
and subject line Bug#917273: fixed in el-api 3.0.0-2
has caused the Debian Bug report #917273,
regarding overwritting files from libservlet2.5-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.)


-- 
917273: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917273
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libel-api-java
Version: 3.0.0-1
Severity: grave

The usual story, not installable, breaks upgrade.
Please resolve this conflict:

Unpacking libel-api-java (3.0.0-1) ...
dpkg: error processing archive 
/var/cache/apt/archives/libel-api-java_3.0.0-1_all.deb (--unpack):
 trying to overwrite 
'/usr/share/maven-repo/javax/el/el-api/debian/el-api-debian.pom', which is also 
in package libservlet2.5-java 6.0.45+dfsg-1
Errors were encountered while processing:
 /var/cache/apt/archives/libel-api-java_3.0.0-1_all.deb

-- 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.20.0-rc7 (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), 
LANGUAGE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)

-- 
"Lassen Sie sich 'Sklaventreiber' auf die Stirn tätowieren. Das ist
ehrlich, da wissen wir alle woran wir sind".
-- Volker Pispers
--- End Message ---
--- Begin Message ---
Source: el-api
Source-Version: 3.0.0-2

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

Debian distribution maintenance software
pp.
Emmanuel Bourg  (supplier of updated el-api 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: Thu, 27 Dec 2018 23:17:57 +0100
Source: el-api
Binary: libel-api-java
Architecture: source
Version: 3.0.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: Emmanuel Bourg 
Description:
 libel-api-java - Expression Language API
Closes: 917273
Changes:
 el-api (3.0.0-2) unstable; urgency=medium
 .
   * Use a real pom for the 3.0 artifacts to improve the compatibility
 with Gradle and Ivy
   * libel-api-java also Breaks/Replaces libservlet2.5-java (Closes: #917273)
   * Standards-Version updated to 4.3.0
Checksums-Sha1:
 2e43c0db0b1ae7908e49a4bc817104edb1c01672 2003 el-api_3.0.0-2.dsc
 b7af363ea245b224d2847dc979562545adcfd072 8536 el-api_3.0.0-2.debian.tar.xz
 5d1f05165b3d9cca4a265b575159149597ba2003 15181 el-api_3.0.0-2_source.buildinfo
Checksums-Sha256:
 4ffcf93fe27f152a0ff3f0cb5d2ea62bde4066cfe808d285fcd0a3a9e20a1a63 2003 
el-api_3.0.0-2.dsc
 f84e529f024dc992a2a9045aefb78aeec1329da033ca37a3f8319ccf2d9a621f 8536 
el-api_3.0.0-2.debian.tar.xz
 f5bb3339a78243ee40bdfcb48548a335465267a542dc6a0811cfb80bb02e20bc 15181 
el-api_3.0.0-2_source.buildinfo
Files:
 91a35ddb344d421c719a833d1cb1fbe7 2003 java optional el-api_3.0.0-2.dsc
 c17a459506cb8e32317b75bd7f3319bf 8536 java optional 
el-api_3.0.0-2.debian.tar.xz
 8b6f44e655068db1798d186dcbf1b54e 15181 java optional 
el-api_3.0.0-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJGBAEBCgAwFiEEuM5N4hCA3PkD4WxA9RPEGeS50KwFAlwlT6gSHGVib3VyZ0Bh
cGFjaGUub3JnAAoJEPUTxBnkudCs64YP/ilPdv9fE2MsJ1dx0HYJTdxCdL0gl0Re
ErvhcSFIfL3KTY04iZWAkOKIf7vxGAorePPfbnsnhh7FiRNeHoG6u7JaK3ttngQy
ZzpboEUIJTuSm3cUntcZUm3/G0sL+cyueLbFcvJXJswiItq9dOYlYTrqQ9uogq2S
YUp6A+4pAeCvBuAm319yXo/AHWLiZSk695O8kGE/HwlKWYZ2jQSX+nu5/Jn+CmSF
66lRfdMOArR8xXBkVUCfXx33WUoLB/B6p+ofyDglExqrDK5dRJUlfIW8rPVh2xrk
p0QQDpivnUJKg5HWraenIcxaVOcK5q6EZFrEh+s8yje0D7G1fEjA2dal5FawMPqp
Rba/s7A6HIZydvJvNWF4mu5Aypm9G99xMw+ogPJ199rEpF7h3nWWLxloQWxGBJOL
Zh4tsOX1NqddbIR8aYTBcK67tziSMyaoZd//j2urhohZ5/FmEnw0gnxdsMOGtCWm
DEAfcpLAEHoezpQacLccf2BSyCEPQ6Rf+7iQFUh35KiaRwZemrIYtQRsoPQcXdnz
Js85OXB8ohwzoJQTSuH/AbX1bZmhSOZNItOcBVhx57EPjyBOckBbMfqNZTebWChB

Bug#917124: lvm2 logical volumes are not properly initialized

[Michael Biebl]

Am 27.12.18 um 23:09 schrieb Ben Caradoc-Davies:
> And I am also please to report that the two-minute wait on shutdown seen
> here after upgrade to 240-1 and also after upgrade to 240-2 occurs only
> on the first shutdown after upgrade:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?att=1;bug=917124;filename=img_20181223_130610.jpg;msg=27
> 
> 
> Subsequent shutdowns do not seem to be affected.

Yes, I've seen that as well.

I've tested an upgrade from v232 (i.e. stretch) to v240, which is
seemingly not affected by this shutdown issue, so I don't plan to
further investigate this, as it won't affect upgrades from stretch → buster.

Regards,
Michael



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



signature.asc
Description: OpenPGP digital signature

Bug#881972: xul-ext-webdeveloper: new upstream version (WebExtensions support)

[Moritz Mühlenhoff]

On Tue, Dec 04, 2018 at 12:06:11AM +0100, Moritz Mühlenhoff wrote:
> On Fri, Nov 17, 2017 at 01:50:10AM +0100, Christoph Anton Mitterer wrote:
> > Package: xul-ext-webdeveloper
> > Version: 1.2.13-1
> > Severity: wishlist
> > 
> > 
> > Hi.
> > 
> > There is a new upstream version (2.0.1) which is a complete
> > rewrite with webextensions support, making the addon work again
> > in FF57+.
> 
> Does anyone intend/plan to switch the package to the web extention?
> Otherwise it should be removed from the archive.

I've filed a removal bug now.

Cheers,
Moritz

Bug#917273: Bug #917273 in el-api marked as pending

[Emmanuel Bourg]

Control: tag -1 pending

Hello,

Bug #917273 in el-api 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/java-team/el-api/commit/0b2165d1f163d0c08782d66e88a89b1523dd1ca5


libel-api-java also Breaks/Replaces libservlet2.5-java (Closes: #917273)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/917273

Processed: Bug #917273 in el-api marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #917273 [libel-api-java] overwritting files from libservlet2.5-java
Added tag(s) pending.

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

Bug#917167: Bug #917167 in systemd marked as pending

[Eric Valette]

On 27/12/2018 14:34, Michael Biebl wrote:

Control: tag -1 pending

Hello,

Bug #917167 in systemd 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:


Thanks. Happily tested -2 version successfully. Keep up the good work 
and enjoy your vacation if you have some.



-- eric

Bug#917124: lvm2 logical volumes are not properly initialized

[Michael Biebl]

Am 27.12.18 um 22:59 schrieb Ben Caradoc-Davies:
> Thanks, Michael. Confirmed fixed for me in 240-2.

Thanks for the confirmation.


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



signature.asc
Description: OpenPGP digital signature

Bug#906830: xul-ext-colorfultabs no longer works with firefox-esr 60

[Moritz Mühlenhoff]

On Tue, Dec 04, 2018 at 12:04:18AM +0100, Moritz Mühlenhoff wrote:
> On Tue, Aug 21, 2018 at 07:07:51PM +0300, Adrian Bunk wrote:
> > Package: xul-ext-colorfultabs
> > Version: 31.1.0+dfsg-1
> > Severity: serious
> > 
> > XUL addons are no longer supported.
> 
> There's a web extension available (v32.7).
> 
> Does anyone intend/plan to switch the package to the web extention?
> Otherwise it should be removed from the archive.

I've filed a removal bug. If there's renewed interested in
packaging the web extension it can be done separately.
 
Cheers,
Moritz

Bug#917124: lvm2 logical volumes are not properly initialized

[Ben Caradoc-Davies]

And I am also please to report that the two-minute wait on shutdown seen 
here after upgrade to 240-1 and also after upgrade to 240-2 occurs only 
on the first shutdown after upgrade:

https://bugs.debian.org/cgi-bin/bugreport.cgi?att=1;bug=917124;filename=img_20181223_130610.jpg;msg=27

Subsequent shutdowns do not seem to be affected.

Kind regards

--
Ben Caradoc-Davies 
Director
Transient Software Limited 
New Zealand

Bug#827310: xul-ext-pwdhash from stable is not compatible to firefox-esr and gets disabled

[Moritz Mühlenhoff]

On Tue, Dec 04, 2018 at 12:02:09AM +0100, Moritz Mühlenhoff wrote:
> On Fri, Oct 05, 2018 at 04:03:09PM +0200, Michal Politowski wrote:
> > Package: xul-ext-pwdhash
> > Version: 1.7.4-1
> > Followup-For: Bug #827310
> > 
> > There appears to exist a webextension version 2.0 of PwdHash,
> > which should work with current Firefox.
> > 
> > https://addons.mozilla.org/en-GB/firefox/addon/pwdhash/
> > https://github.com/pwdhash/pwdhash-webextension
> 
> Does anyone intend/plan to switch the package to the web extention?
> Otherwise it should be removed from the archive.

I've filed a removal bug now.

Cheers,
Moritz

Bug#906869: xul-ext-uppity no longer works with firefox-esr 60

[Moritz Mühlenhoff]

On Tue, Dec 04, 2018 at 12:06:57AM +0100, Moritz Mühlenhoff wrote:
> On Thu, Sep 06, 2018 at 10:28:23PM +0800, Paul Wise wrote:
> > Control: tags -1 fixed-upstream
> > 
> > On Tue, 21 Aug 2018 21:27:13 +0300 Adrian Bunk wrote:
> > 
> > > Package: xul-ext-uppity
> > > XUL addons are no longer supported.
> > 
> > Upstream has rewritten it as a WebExtension:
> > 
> > https://github.com/arantius/uppity
> 
> Does anyone intend/plan to switch the package to the web extension?
> Otherwise it should be removed from the archive.

I've now filed a removal bug.

Cheers,
Moritz

Bug#910756: xul-ext-useragentswitcher: Firefox 60esr breaks user-agent-switcher. Please upgrade to upstream version which works.

[Moritz Mühlenhoff]

On Tue, Dec 04, 2018 at 01:12:27PM +0800, Paul Wise wrote:
> On Tue, 2018-12-04 at 00:05 +0100, Moritz Mühlenhoff wrote:
> 
> > Does anyone intend/plan to switch the package to the web extention?
> > Otherwise it should be removed from the archive.'
> 
> This package has no web extension version available.
> 
> There are other similar web extensions available but
> they are from different upstream projects and
> are very different from this one.

I've filed a removal bug.

Cheers,
Moritz

Bug#917124: lvm2 logical volumes are not properly initialized

[Ben Caradoc-Davies]

Thanks, Michael. Confirmed fixed for me in 240-2.

Kind regards,

--
Ben Caradoc-Davies 
Director
Transient Software Limited 
New Zealand

Bug#917303: Request for help with MariaDB 10.3 / libdbd-mysql-perl packaging

[gregor herrmann]

On Thu, 27 Dec 2018 19:52:02 +0200, Otto Kekäläinen wrote:

> The recent upload of MariadB 10.3 to Debian unstable and also the new
> mysql-defaults break the Debian CI tests of your package
> libdbd-mysql-perl.

True. And not only the CI tests.
There's already a bug for it:
https://bugs.debian.org/917303
and an upstream issue:
https://github.com/perl5-dbi/DBD-mysql/issues/275

(CC'ing the bug report to get the discussion into the right place.)

> I would appreciate very much if you can debug what exactly goes wrong
> in the libdbd-mysql-perl tests and perhaps even file a merge request
> on Salsa against mariadb-10.3 to get it fixed.

Looks like this is an issue in DBD-mysql; maybe other distributions
have found something already (I haven't looked yet)?
It might help to know what has changed in MariaDB between 10.1 and
10.3 …
 

Cheers,
gregor

-- 
 .''`.  https://info.comodo.priv.at -- Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
   `-   NP: Rolling Stones: Tumbling


signature.asc
Description: Digital Signature

Bug#917457: marked as done (libilmbase23: 2.3.0-3 bumped so name without transition (breaks digikam, gimp, ...))

[Debian Bug Tracking System]

Your message dated Thu, 27 Dec 2018 21:17:18 +0100
with message-id <87imzevi5t.fsf@localhost>
and subject line Re: Bug#917457: libilmbase23: 2.3.0-3 bumped so name without 
transition (breaks digikam, gimp, ...)
has caused the Debian Bug report #917457,
regarding libilmbase23: 2.3.0-3 bumped so name without transition (breaks 
digikam, gimp, ...)
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.)


-- 
917457: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917457
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libilmbase23
Version: 2.3.0-3
Severity: critical
Justification: breaks unrelated software

ldd /usr/bin/digikam | grep libIlmImf-2_2.so.23
libIlmImf-2_2.so.23 => not found
ldd /usr/bin/digikam | grep 'not found'
libImath-2_2.so.23 => not found
libIlmImf-2_2.so.23 => not found
libIex-2_2.so.23 => not found
libHalf.so.23 => not found
libIlmThread-2_2.so.23 => not found

I think gimp is also affected...

valette@tri-yann4:~$ dpkg -L  libilmbase23
/.
/usr
/usr/lib
/usr/lib/x86_64-linux-gnu
/usr/lib/x86_64-linux-gnu/libHalf.so.24.0.0
/usr/lib/x86_64-linux-gnu/libIex-2_3.so.24.0.0
/usr/lib/x86_64-linux-gnu/libIexMath-2_3.so.24.0.0
/usr/lib/x86_64-linux-gnu/libIlmThread-2_3.so.24.0.0
/usr/lib/x86_64-linux-gnu/libImath-2_3.so.24.0.0
/usr/share
/usr/share/doc
/usr/share/doc/libilmbase23
/usr/share/doc/libilmbase23/AUTHORS
/usr/share/doc/libilmbase23/NEWS.gz
/usr/share/doc/libilmbase23/README.md.gz
/usr/share/doc/libilmbase23/changelog.Debian.gz
/usr/share/doc/libilmbase23/changelog.gz
/usr/share/doc/libilmbase23/copyright
/usr/share/lintian
/usr/share/lintian/overrides
/usr/share/lintian/overrides/libilmbase23
/usr/lib/x86_64-linux-gnu/libHalf.so.24
/usr/lib/x86_64-linux-gnu/libIex-2_3.so.24
/usr/lib/x86_64-linux-gnu/libIexMath-2_3.so.24
/usr/lib/x86_64-linux-gnu/libIlmThread-2_3.so.24
/usr/lib/x86_64-linux-gnu/libImath-2_3.so.24


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

Kernel: Linux 4.14.90 (SMP w/8 CPU cores; PREEMPT)
Locale: LANG=fr_FR.UTF8, LC_CTYPE=fr_FR.UTF8 (charmap=UTF-8), LANGUAGE= 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages libilmbase23 depends on:
ii  libc6   2.28-3
ii  libgcc1 1:8.2.0-13
ii  libstdc++6  8.2.0-13

libilmbase23 recommends no packages.

libilmbase23 suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Hi!

On 2018-12-27 at 19:38 (+01), Eric Valette wrote:
> Package: libilmbase23
> Version: 2.3.0-3
> Severity: critical
> Justification: breaks unrelated software

[...]

Well, 2.3.0-3 revision is still in the experimental suite.
That's the right place to prepare a transition, indeed.
We're working on it, along with openexr.

Simply, be patient.

Cheers.

-- 
Matteo F. Vescovi || Debian Developer
GnuPG KeyID: 4096R/0x8062398983B2CF7A


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

Processed: reassign 917459 to mmm-mode, forcibly merging 917072 917459

[Debian Bug Tracking System]

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

> reassign 917459 mmm-mode
Bug #917459 [emacs] emacs: 1:26.1+1-2 hangs on byte-compiling mmm-mode, breaks 
proofgeneral
Bug reassigned from package 'emacs' to 'mmm-mode'.
No longer marked as found in versions emacs/1:26.1+1-2.
Ignoring request to alter fixed versions of bug #917459 to the same values 
previously set
> forcemerge 917072 917459
Bug #917072 {Done: Alexander Zangerl } [mmm-mode] mmm-mode: 
fails to byte-compile with emacs-26
Bug #917050 {Done: Alexander Zangerl } [mmm-mode] 
elpa-markdown-mode: Hangs infinitely when compiling for emacs 1:26.1+1-2
Bug #917052 {Done: Alexander Zangerl } [mmm-mode] 
elpa-xml-rpc: Hangs infinitely when compiling for emacs 1:26.1+1-2
Bug #917459 [mmm-mode] emacs: 1:26.1+1-2 hangs on byte-compiling mmm-mode, 
breaks proofgeneral
Severity set to 'serious' from 'normal'
Marked Bug as done
Added indication that 917459 affects 
emacs-gtk,elpa-xml-rpc,elpa-lua-mode,emacs,elpa-markdown-mode
Marked as fixed in versions mmm-mode/0.5.7-3.
Marked as found in versions mmm-mode/0.5.7-2.
Bug #917050 {Done: Alexander Zangerl } [mmm-mode] 
elpa-markdown-mode: Hangs infinitely when compiling for emacs 1:26.1+1-2
Bug #917052 {Done: Alexander Zangerl } [mmm-mode] 
elpa-xml-rpc: Hangs infinitely when compiling for emacs 1:26.1+1-2
Merged 917050 917052 917072 917459
> thanks
Stopping processing here.

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

Bug#917375: marked as done (wget: CVE-2018-20483)

[Debian Bug Tracking System]

Your message dated Thu, 27 Dec 2018 21:13:04 +0100
with message-id <20181227201304.GA21453@eldamar.local>
and subject line Re: Bug#917375: wget: CVE-2018-20483
has caused the Debian Bug report #917375,
regarding wget: CVE-2018-20483
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.)


-- 
917375: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917375
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: wget
Version: 1.20-1
Severity: important
Tags: security upstream

Hi,

The following vulnerability was published for wget.

CVE-2018-20483[0]:
| set_file_metadata in xattr.c in GNU Wget through 1.20 stores a file's
| origin URL in the user.xdg.origin.url metadata attribute of the
| extended attributes of the downloaded file, which allows local users to
| obtain sensitive information (e.g., credentials contained in the URL)
| by reading this attribute, as demonstrated by getfattr. This also
| applies to Referer information in the user.xdg.referrer.url metadata
| attribute. According to 2016-07-22 in the Wget ChangeLog,
| user.xdg.origin.url was partially based on the behavior of fwrite_xattr
| in tool_xattr.c in curl.

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

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: wget
Source-Version: 1.20.1-1

On Wed, Dec 26, 2018 at 09:24:23PM +0100, Salvatore Bonaccorso wrote:
> Source: wget
> Version: 1.20-1
> Severity: important
> Tags: security upstream
> 
> Hi,
> 
> The following vulnerability was published for wget.
> 
> CVE-2018-20483[0]:
> | set_file_metadata in xattr.c in GNU Wget through 1.20 stores a file's
> | origin URL in the user.xdg.origin.url metadata attribute of the
> | extended attributes of the downloaded file, which allows local users to
> | obtain sensitive information (e.g., credentials contained in the URL)
> | by reading this attribute, as demonstrated by getfattr. This also
> | applies to Referer information in the user.xdg.referrer.url metadata
> | attribute. According to 2016-07-22 in the Wget ChangeLog,
> | user.xdg.origin.url was partially based on the behavior of fwrite_xattr
> | in tool_xattr.c in curl.

Fixed with the 1.20.1 upstream version upload to sid today.

Regards,
Salvatore--- End Message ---

Bug#917375: wget: CVE-2018-20483

[Salvatore Bonaccorso]

Source: wget
Source-Version: 1.20.1-1

On Wed, Dec 26, 2018 at 09:24:23PM +0100, Salvatore Bonaccorso wrote:
> Source: wget
> Version: 1.20-1
> Severity: important
> Tags: security upstream
> 
> Hi,
> 
> The following vulnerability was published for wget.
> 
> CVE-2018-20483[0]:
> | set_file_metadata in xattr.c in GNU Wget through 1.20 stores a file's
> | origin URL in the user.xdg.origin.url metadata attribute of the
> | extended attributes of the downloaded file, which allows local users to
> | obtain sensitive information (e.g., credentials contained in the URL)
> | by reading this attribute, as demonstrated by getfattr. This also
> | applies to Referer information in the user.xdg.referrer.url metadata
> | attribute. According to 2016-07-22 in the Wget ChangeLog,
> | user.xdg.origin.url was partially based on the behavior of fwrite_xattr
> | in tool_xattr.c in curl.

Fixed with the 1.20.1 upstream version upload to sid today.

Regards,
Salvatore

Processed (with 1 error): forcibly merging 917072 917459

[Debian Bug Tracking System]

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

> forcemerge 917072 917459
Bug #917072 {Done: Alexander Zangerl } [mmm-mode] mmm-mode: 
fails to byte-compile with emacs-26
Bug #917050 {Done: Alexander Zangerl } [mmm-mode] 
elpa-markdown-mode: Hangs infinitely when compiling for emacs 1:26.1+1-2
Bug #917052 {Done: Alexander Zangerl } [mmm-mode] 
elpa-xml-rpc: Hangs infinitely when compiling for emacs 1:26.1+1-2
Unable to merge bugs because:
package of #917459 is 'emacs' not 'mmm-mode'
Failed to forcibly merge 917072: Did not alter merged bugs.

> thanks
Stopping processing here.

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

Bug#863675: Bug #863675 in mariadb-10.3 marked as pending

[Otto Kekäläinen]

Control: tag -1 pending

Hello,

Bug #863675 in mariadb-10.3 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/mariadb-team/mariadb-10.3/commit/01d12e97ed51233535fc8762c806d6240ef1b053


Make libmariadb-dev breaks/replaces libmysqlclient-dev (Closes: #863675)

This mimics how libmariadbclient-dev used to breaks/replaces the same
libmysqlclient-dev package. These packages are not supposed to be
co-installable anyway.

Among others, the following files conflict:
- /usr/bin/mysql_config
- libmysqlservices.a
- mysql.m4

Also, wrap-and-sort -a in this commit.


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/863675

Processed: Bug #863675 in mariadb-10.3 marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #863675 [src:mariadb-10.3] libmariadbd-dev: fails to upgrade from 'sid' - 
trying to overwrite /usr/bin/mysql_config
Ignoring request to alter tags of bug #863675 to the same tags previously set

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

Bug#917457: libilmbase23: 2.3.0-3 bumped so name without transition (breaks digikam, gimp, ...)

[Eric Valette]

Package: libilmbase23
Version: 2.3.0-3
Severity: critical
Justification: breaks unrelated software

ldd /usr/bin/digikam | grep libIlmImf-2_2.so.23
libIlmImf-2_2.so.23 => not found
ldd /usr/bin/digikam | grep 'not found'
libImath-2_2.so.23 => not found
libIlmImf-2_2.so.23 => not found
libIex-2_2.so.23 => not found
libHalf.so.23 => not found
libIlmThread-2_2.so.23 => not found

I think gimp is also affected...

valette@tri-yann4:~$ dpkg -L  libilmbase23
/.
/usr
/usr/lib
/usr/lib/x86_64-linux-gnu
/usr/lib/x86_64-linux-gnu/libHalf.so.24.0.0
/usr/lib/x86_64-linux-gnu/libIex-2_3.so.24.0.0
/usr/lib/x86_64-linux-gnu/libIexMath-2_3.so.24.0.0
/usr/lib/x86_64-linux-gnu/libIlmThread-2_3.so.24.0.0
/usr/lib/x86_64-linux-gnu/libImath-2_3.so.24.0.0
/usr/share
/usr/share/doc
/usr/share/doc/libilmbase23
/usr/share/doc/libilmbase23/AUTHORS
/usr/share/doc/libilmbase23/NEWS.gz
/usr/share/doc/libilmbase23/README.md.gz
/usr/share/doc/libilmbase23/changelog.Debian.gz
/usr/share/doc/libilmbase23/changelog.gz
/usr/share/doc/libilmbase23/copyright
/usr/share/lintian
/usr/share/lintian/overrides
/usr/share/lintian/overrides/libilmbase23
/usr/lib/x86_64-linux-gnu/libHalf.so.24
/usr/lib/x86_64-linux-gnu/libIex-2_3.so.24
/usr/lib/x86_64-linux-gnu/libIexMath-2_3.so.24
/usr/lib/x86_64-linux-gnu/libIlmThread-2_3.so.24
/usr/lib/x86_64-linux-gnu/libImath-2_3.so.24


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

Kernel: Linux 4.14.90 (SMP w/8 CPU cores; PREEMPT)
Locale: LANG=fr_FR.UTF8, LC_CTYPE=fr_FR.UTF8 (charmap=UTF-8), LANGUAGE= 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages libilmbase23 depends on:
ii  libc6   2.28-3
ii  libgcc1 1:8.2.0-13
ii  libstdc++6  8.2.0-13

libilmbase23 recommends no packages.

libilmbase23 suggests no packages.

-- no debconf information

Bug#916424: marked as done (rust-crossbeam-channel: Incomplete debian/copyright?)

[Debian Bug Tracking System]

Your message dated Thu, 27 Dec 2018 18:22:30 +
with message-id 
and subject line Bug#916424: fixed in rust-crossbeam-channel 0.3.2-2
has caused the Debian Bug report #916424,
regarding rust-crossbeam-channel: Incomplete debian/copyright?
to be marked as done.

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

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


-- 
916424: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916424
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rust-crossbeam-channel
Version: 0.3.2-1
Severity: serious
Justication: Policy 12.5
X-Debbugs-CC: Sylvestre Ledru , 
ftpmas...@debian.org

Hi,

I just ACCEPTed rust-crossbeam-channel from NEW but noticed it was 
missing attribution in debian/copyright for at least Dmitry Vyukov.

This is in no way exhaustive so please check over the entire package 
carefully and address these on your next upload.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
--- End Message ---
--- Begin Message ---
Source: rust-crossbeam-channel
Source-Version: 0.3.2-2

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

Debian distribution maintenance software
pp.
Ximin Luo  (supplier of updated rust-crossbeam-channel 
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: Thu, 27 Dec 2018 10:03:18 -0800
Source: rust-crossbeam-channel
Binary: librust-crossbeam-channel-dev
Architecture: source
Version: 0.3.2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Rust Maintainers 

Changed-By: Ximin Luo 
Description:
 librust-crossbeam-channel-dev - Multi-producer multi-consumer channels for 
message passing - Rust
Closes: 916424
Changes:
 rust-crossbeam-channel (0.3.2-2) unstable; urgency=medium
 .
   * Team upload.
   * Package crossbeam-channel 0.3.2 from crates.io using debcargo 2.2.9
 .
   [ Sylvestre Ledru ]
   * Add a missing dev in the copyright file (Closes: #916424)
Checksums-Sha1:
 7280d53033f2143b78ef7ed40c1ec32b1e199bdd 1892 
rust-crossbeam-channel_0.3.2-2.dsc
 6ac2005a1cd958dd59c6757e929066f2da9d6f54 2628 
rust-crossbeam-channel_0.3.2-2.debian.tar.xz
 a10d60b5bd5ff78589d0fb79e95dcee2e63cc8a8 6259 
rust-crossbeam-channel_0.3.2-2_source.buildinfo
Checksums-Sha256:
 39c140218b880974e436d00fae625bddb2d819b250aee1c21cca608d1c8332b3 1892 
rust-crossbeam-channel_0.3.2-2.dsc
 4cd59920157fe64217353ee628997515fa0d3ed0ecfd342390a0c075d065fb20 2628 
rust-crossbeam-channel_0.3.2-2.debian.tar.xz
 9236e09ae237a0ba21e162e6c2567afa51eb48787e8951c1c52733566b2570a2 6259 
rust-crossbeam-channel_0.3.2-2_source.buildinfo
Files:
 3b75d02c53698a167f413f7846f06055 1892 rust optional 
rust-crossbeam-channel_0.3.2-2.dsc
 f9ecf4813de1a25e3dcbd866e024b591 2628 rust optional 
rust-crossbeam-channel_0.3.2-2.debian.tar.xz
 bfdfb4cfbde4feb4720ac3838d176a05 6259 rust optional 
rust-crossbeam-channel_0.3.2-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iHUEARYKAB0WIQReYinNQ9GpZ9TYcRrrH8jaRfspMAUCXCUT8QAKCRDrH8jaRfsp
MBrNAQC9XNM9a2T0XPcK/GZfx91XpDKpTK1HBdngiAE20HzqWgEApvWEMxnmaVoT
h79i9a6Ppn86FaWTQXy8s2dHo6LEag8=
=+WWY
-END PGP SIGNATURE End Message ---

Bug#902505: marked as done (node-cross-spawn: FTBFS in buster/sid (Cannot find module 'which'))

[Debian Bug Tracking System]

Your message dated Thu, 27 Dec 2018 18:19:19 +
with message-id 
and subject line Bug#902505: fixed in node-cross-spawn 5.1.0-2
has caused the Debian Bug report #902505,
regarding node-cross-spawn: FTBFS in buster/sid (Cannot find module 'which')
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.)


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

Dear maintainer:

I tried to build this package in buster with "dpkg-buildpackage -A"
but it failed:


[...]
 debian/rules build-indep
dh build-indep
   dh_update_autotools_config -i
   debian/rules override_dh_auto_test
make[1]: Entering directory '/<>'
nodejs test/prepare && mocha --bail -R spec test/test
module.js:549
throw err;
^

Error: Cannot find module 'which'
at Function.Module._resolveFilename (module.js:547:15)
at Function.Module._load (module.js:474:25)
at Module.require (module.js:596:17)
at require (internal/module.js:11:18)
at Object. (/<>/lib/util/resolveCommand.js:4:13)
at Module._compile (module.js:652:30)
at Object.Module._extensions..js (module.js:663:10)
at Module.load (module.js:565:32)
at tryModuleLoad (module.js:505:12)
at Function.Module._load (module.js:497:3)
debian/rules:11: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 1
make[1]: Leaving directory '/<>'
debian/rules:8: recipe for target 'build-indep' failed
make: *** [build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


The above is how the build ends in my autobuilder and it's not
necessarily the relevant part.

The failure is not, however, related to using dpkg-buildpackage -A,
as it also fails in reproducible builds:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/node-cross-spawn.html

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the page for this package.

Thanks.
--- End Message ---
--- Begin Message ---
Source: node-cross-spawn
Source-Version: 5.1.0-2

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

Debian distribution maintenance software
pp.
Ross Gammon  (supplier of updated node-cross-spawn 
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: Thu, 27 Dec 2018 18:54:48 +0100
Source: node-cross-spawn
Binary: node-cross-spawn
Architecture: source
Version: 5.1.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Ross Gammon 
Description:
 node-cross-spawn - Cross platform drop-in replacement for spawn
Closes: 902505
Changes:
 node-cross-spawn (5.1.0-2) unstable; urgency=medium
 .
   * Fix FTBFS by adding which & lru-cache to Build-Depends (Closes: #902505)
   * Use my Debian email address
   * Add a debian/gitlab-ci.yml file for Salsa CI
   * Remove whitespace from changelog
   * Use recommended compatibility level for current stable
   * Use new Salsa Vcs URLs
   * Bump standards version, no changes required
   * Check DEB_BUILD_OPTIONS against nocheck
   * Add patch from Ubuntu to increase timer in tests which time out on arm*
Checksums-Sha1:
 36f3fa5c22c7e9fa115bc96ebd98583bd8987dc4 2154 node-cross-spawn_5.1.0-2.dsc
 6dc25165290c3981684d72e57c165ed7aebfb875 4660 
node-cross-spawn_5.1.0-2.debian.tar.xz
 bf820b49f951d8f57e6e57f4210348eb7901ab43 7599 
node-cross-spawn_5.1.0-2_amd64.buildinfo
Checksums-Sha256:
 b1eef529610d4e9248a479dd8ae87dbbdc29023fa130afbc524d6aec7122fa59 2154 
node-cross-spawn_5.1.0-2.dsc
 de1eb6fdec4ac0009cb8afb835da93567b3e900e06fac43c45b9a6f12399e450 4660 
node-cross-spawn_5.1.0-2.debian.tar.xz
 b67ffc489a31114bf006e43798668b1ace8c603988449045dde75af7deaeb516 7599 

Bug#917456: urgent need to upgrade upstream

[PICCORO McKAY Lenz]

Package: rtpproxy
Version: 1.2.1-2.2
Severity: grave

current debian packages are unusable behind nat, due advertise option,
Back in 2009, Daniel Goepp posted a patch to RTPproxy to support
putting rtpproxy behind NAT.

today the debian package are unuseless with packaged kamailio , due
does not retransmid the calls in NAT:

Dec 27 17:04:24] WARNING[1009]: chan_sip.c:4065 retrans_pkt:
Retransmission timeout reached on transmission
1859282381-3255...@bjc.bgi.b.bah for seqno 21 (Critical Response) --
See https://wiki.asterisk.org/wiki/display/AST/SIP+Retransmissions
Packet timed out after 6912ms with no response
[Dec 27 17:04:24] WARNING[1009]: chan_sip.c:4089 retrans_pkt: Hanging
up call 1859282381-3255...@bjc.bgi.b.bah - no reply to our critical
packet (see https://wiki.asterisk.org/wiki/display/AST/SIP+Retransmissions).
-- Channel SIP/101206000-0007 left 'simple_bridge' basic-bridge


after install manually the lasted seems problems are gone

Lenz McKAY Gerardo (PICCORO)
http://qgqlochekone.blogspot.com

Bug#916582: marked as done (parl-desktop depends on the removed xfce4-linelight-plugin)

[Debian Bug Tracking System]

Your message dated Thu, 27 Dec 2018 18:04:24 +
with message-id 
and subject line Bug#916582: fixed in debian-parl 1.9.17
has caused the Debian Bug report #916582,
regarding parl-desktop depends on the removed xfce4-linelight-plugin
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.)


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

The following packages have unmet dependencies:
 parl-desktop : Depends: xfce4-linelight-plugin but it is not installable
--- End Message ---
--- Begin Message ---
Source: debian-parl
Source-Version: 1.9.17

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

Debian distribution maintenance software
pp.
Jonas Smedegaard  (supplier of updated debian-parl 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: Thu, 27 Dec 2018 18:50:04 +0100
Source: debian-parl
Binary: parl-data parl-desktop parl-desktop-world parl-desktop-eu 
parl-desktop-strict
Architecture: source
Version: 1.9.17
Distribution: unstable
Urgency: medium
Maintainer: DebianParl team 
Changed-By: Jonas Smedegaard 
Description:
 parl-data  - recipes to install DebianParl blends
 parl-desktop - DebianParl desktop for parliamentary work
 parl-desktop-eu - DebianParl desktop for parliamentary work - EU
 parl-desktop-strict - DebianParl desktop for parliamentary work - strict
 parl-desktop-world - DebianParl desktop for parliamentary work - global
Closes: 916582
Changes:
 debian-parl (1.9.17) unstable; urgency=medium
 .
   * Rebuild using newer boxer-data.
 + Include catfish (not xfce4-linelight-plugin).
   Closes: Bug#916582. Thanks to Adrian Bunk.
 + Stop explicitly include gvfs (handled in thunar since long).
 + Include xfce4-pulseaudio-plugin (GStreamer 0.10 is long gone).
   * Declare compliance with Debian Policy 4.3.0.
Checksums-Sha1:
 1968b21966c3c409d3b99ed200f05857a850b17c 1969 debian-parl_1.9.17.dsc
 bf9c1f476021bcb9bba5754246d26b2a8e19204c 10096 debian-parl_1.9.17.tar.xz
 668864a39f9f7c08a465793c1a7402461acf23e6 9026 
debian-parl_1.9.17_amd64.buildinfo
Checksums-Sha256:
 1a443e0cdff9065cff7dbe8120765d1702d22025143bac8a61b6c83c9525d639 1969 
debian-parl_1.9.17.dsc
 67f6d44885136af967a5eecc91b325efa252af621a934596607610cdf4df61bb 10096 
debian-parl_1.9.17.tar.xz
 fb484ea0dcb313a720ceb19d7dca3721cca94cb5d9983c297a1912d291e1 9026 
debian-parl_1.9.17_amd64.buildinfo
Files:
 17484775a210155bd093b587f34ce9aa 1969 misc optional debian-parl_1.9.17.dsc
 af496231a035f1e21abe0c1e3d305376 10096 misc optional debian-parl_1.9.17.tar.xz
 6c451d16f65f97726b38ee01548f5b70 9026 misc optional 
debian-parl_1.9.17_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAlwlEXMACgkQLHwxRsGg
ASGnNw//U6cD9UJHkjpYVlXxXR3gkqf9pBZxE6yBO+qtNqBJozmwSVGwEpvk7j/1
DUAiXyj1eVsu57ltKlvzFCFZIlV9MPHpg4yiQBfUoITgEyk2Z01Jt2YbOn19+Cs8
QZ+tsGPrp7H4WyT83176galr4kCLtCd4BRSY39QH0g3R1sCzrtdBu1nojGMTLDhQ
BHWY68bEz8kBHm4GUeYE3NXea7C+F279zXlgbCw9X8R6s/BbP+2PBGxTrnZIwQiN
eR8eHTRmFmbH35xlglMXpnTEXeOsevBS9lYnMKaqLla9sdfHCxsMCoeA5v7tWlPJ
l2v06dMvls76xmFLWtTxNd3N0sJC2xVPkeQ26v+XVeamEh7rXPX1XK3WzgpRyIi2
23gTIawmFgNhEpVfefXFW4pl7WLK/+ST/cZEeq3ZZjzWZzFh2pZs5erW2cdLDkOL
LiNkSd8muXsoHN4PpK4sydQdL89fyVnjacarAH30dRp2NE7QM5B141whGHyznxLt
IY1MENjD+YYYe+Bb02WOrMNqdRKl0M+KGDYmRO2CVbi4HxmqZeoSDOUJsgbg3c30
7vatYohwDmSel/aHUYXjfqYRtg3HC7DFX3nExVmEWFfHlUyPC7cvi2RQJHtlhSvl
DzTz6gm9Kw9zk44Kw3e/WQleLyyEpHdKhkJnd9ZNCkBi7Emj5p4=
=uzLm
-END PGP SIGNATURE End Message ---

Processed: [bts-link] source package nocache

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package nocache
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Setting user to debian-bts-l...@lists.debian.org (was 
debian-bts-l...@lists.debian.org).
> # remote status report for #916415 (http://bugs.debian.org/916415)
> # Bug title: nocache broken with glibc 2.28: several programs just hang in 
> call to futex(..., FUTEX_WAIT_PRIVATE, 2, NULL)
> #  * https://github.com/Feh/nocache/issues/34
> #  * remote status changed: open -> closed
> #  * closed upstream
> tags 916415 + fixed-upstream
Bug #916415 [nocache] nocache broken with glibc 2.28: several programs just 
hang in call to futex(..., FUTEX_WAIT_PRIVATE, 2, NULL)
Added tag(s) fixed-upstream.
> usertags 916415 - status-open
Usertags were: status-open.
Usertags are now: .
> usertags 916415 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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

Bug#917428: Python 2 matplotlib package required for sagemath

[Tobias Hansen]

Hi Sandro,

I was just about to finish an update to the sagemath package when you uploaded 
matplotlib 3.0.2 to unstable. We need the Python 2 package for sagemath (see 
#917428). Would you be ok with me uploading matplotlib 2.2.3 as a separate 
source package that provides python-matplotlib? Or would you even want to 
maintain it?

Best,

Tobias

Processed: Mark bugs as pending

[Debian Bug Tracking System]

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

> tags 890231 + pending
Bug #890231 [src:sagemath] sagemath should use gdb, not gdb-python2, to be 
removed for buster
Added tag(s) pending.
> tags 912980 + pending
Bug #912980 [src:sagemath] sagemath is incompatible with GAP 4.9
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: sagemath depends on python 2 version of matplotlib (which was removed from unstable)

[Debian Bug Tracking System]

Processing control commands:

> block 912980 by -1
Bug #912980 [src:sagemath] sagemath is incompatible with GAP 4.9
912980 was blocked by: 916640 912862
912980 was blocking: 912593 916586
Added blocking bug(s) of 912980: 917428
> block 912593 by -1
Bug #912593 [src:sagemath] sagemath has unfulfillable build-dependencies
Bug #916586 [src:sagemath] sagemath: depends on specific libsingular4 which is 
no longer being built in unstable
912593 was blocked by: 912980
912593 was not blocking any bugs.
Added blocking bug(s) of 912593: 917428
916586 was blocked by: 912980
916586 was not blocking any bugs.
Added blocking bug(s) of 916586: 917428
> block 890231 by -1
Bug #890231 [src:sagemath] sagemath should use gdb, not gdb-python2, to be 
removed for buster
890231 was not blocked by any bugs.
890231 was not blocking any bugs.
Added blocking bug(s) of 890231: 917428

-- 
890231: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890231
912593: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912593
912980: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912980
916586: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916586
917428: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917428
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#917430: libconfig-model-dpkg-perl: test failures with newer Config::Model

[gregor herrmann]

Source: libconfig-model-dpkg-perl
Version: 2.119
Severity: serious
Justification: fails to build from source

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

libconfig-model-dpkg-perl (both 2.119 in the archive and the version
in git) doesn't build anymore, probably due to changes in or around
Config::Model. The same test failures appear for autopkgtests
(locally or on ci.d.n.).

#   Failed test 'Log4perl test'
#   at /usr/share/perl5/Config/Model/Tester.pm line 160.
# Message 1 logged wasn't what we expected:
#   message was 'Warning in 'source Standards-Version': Current standards 
version is '4.3.0'. Please read https://www.debian.org/doc/debian-policy/up$
# 
# Offending value: '4.2.1''
#  not like '(?^:Invalid value)'
#  (Offending log call from line 1198 in /usr/share/perl5/Config/Model/Value.pm)
#   Failed test 'Log4perl test'
#   at /usr/share/perl5/Config/Model/Tester.pm line 160.
# Message 1 logged wasn't what we expected:
#   message was 'Warning in 'source Standards-Version': Current standards 
version is '4.3.0'. Please read https://www.debian.org/doc/debian-policy/up$
# 
# Offending value: '4.2.1''
#  not like '(?^:Invalid value)'
#  (Offending log call from line 1198 in /usr/share/perl5/Config/Model/Value.pm)
#   Failed test 'Log4perl test'
#   at /usr/share/perl5/Config/Model/Tester.pm line 160.
# Message 1 logged wasn't what we expected:
#   message was 'Warning in 'source Standards-Version': Current standards 
version is '4.3.0'. Please read https://www.debian.org/doc/debian-policy/up$
#
# Offending value: '4.2.1''
#  not like '(?^:Invalid value)'
#  (Offending log call from line 1198 in /usr/share/perl5/Config/Model/Value.pm)
#   Failed test 'Log4perl test'
#   at /usr/share/perl5/Config/Model/Tester.pm line 160.
# Message 1 logged wasn't what we expected:
#   message was 'Warning in 'source Standards-Version': Current standards 
version is '4.3.0'. Please read https://www.debian.org/doc/debian-policy/up$
#
# Offending value: '4.2.1''
#  not like '(?^:Invalid value)'
#  (Offending log call from line 1198 in /usr/share/perl5/Config/Model/Value.pm)


Backend error: YAML::XS::Load Error: The problem:

invalid trailing UTF-8 octet

was found at document: 0
Prototype mismatch: sub Config::Model::Tester::DEBUG () vs none at 
/usr/share/perl5/Log/Log4perl.pm line 564.


Test Summary Report
- ---
t/model_tests.t(Wstat: 65280 Tests: 889 Failed: 5)
  Failed tests:  283, 294, 305, 316, 887
  Non-zero exit status: 255
  Parse errors: No plan found in TAP output
Files=14, Tests=1120, 61 wallclock secs ( 0.27 usr  0.06 sys + 58.74 cusr  1.17 
csys = 60.24 CPU)



I tried to do something about the "Invalid value" in
t/model_tests.d/dpkg-control-test-conf.pl but that only lead to
different failures :/


Cheers,
gregor

-BEGIN PGP SIGNATURE-

iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAlwlBE5fFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx
RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ
qgasHA/+KDHbT5jcmMPfZyiKV57cgTGn6OQckEgdxLLF193R4Y3ZXcsETKasl2nB
Nl+49Jsc+Y7HWZI6O+DUxKaMLRs6f9lSIqj1LwjhRCUTQ1siX/2hpowie6NvHWV7
bSy6ZIa6JehwRtNPBAOfFNsrViA2V5pYYbj7Fl/Qrubx28eE3/uk+Omq50UYf2MN
fgYp127uwJSFJEm/TC7nXVOiU5K2dnmT549xgv+E0fK7D5y57VzvVjPI+KvGuHC/
teG9DKxL5y8CQ0xaCThtUsqzhuCpQ0h3+D+4m2DjMvpAV7U7c9XlicwLkS3pNGWA
0S3PyacvuNc1O+lYyJmZDY12KAxFVJmfP17JWNsTZcpmfTqX5IQmg66Uc3AF0cjj
+FDKlmq3B77A59gYtyyg7VChvUQmukSiM86vksTMjSz0lDPqHdNjF/agusRP8fAM
oUCT6YMakk+5J1vePasyEN0YrOXf7tBM7l+UCnPSY8tv7bJ5bCrxtUkUt+udQ2Xs
M23ZJ19Vi22XkG/YQ0eZiDzLHaR0rwQFIcvmSLzc5ViYZ5iCtlYFQxP1BBMFgUg5
ddJcsniWSUMz+PTUVVxBxaySDubbwvmJA5CgqV93V/egFTHqz6EV37wWLJDZN0TN
ttEBuPOYDCevuxxB1uhnZrXwunwUHEhZxPuspxPX/srp6eWNCMc=
=UyHg
-END PGP SIGNATURE-

Bug#917428: sagemath depends on python 2 version of matplotlib (which was removed from unstable)

[Tobias Hansen]

Package: src:sagemath
Version: 8.4-2
Severity: serious
Tags: sid buster
Control: block 912980 by -1
Control: block 912593 by -1
Control: block 890231 by -1

matplotlib 3.0 was recently uploaded to Debian unstable. This version requires 
Python 3 and hence the package python-matplotlib was removed. Sagemath still 
uses Python 2 and I don't think there is any chance to change that before the 
buster freeze. Hence I think the only way forward is to upload matplotlib 2.2.3 
as a separate source package to provide the Python 2 package python-matplotlib.
All other RC bugs of sagemath are fixed in git, this is the bug preventing an 
upload.

Best,
Tobias

Bug#874727: marked as done (libcoin80v5: Program using libcoin80v5 and any other library that uses lebexpat1 segfaults.)

[Debian Bug Tracking System]

Your message dated Thu, 27 Dec 2018 17:20:43 +0100
with message-id <143377b1-70db-3ddd-2321-96fe1e98a...@alaxarxa.net>
and subject line Embed expat is not used
has caused the Debian Bug report #874727,
regarding libcoin80v5: Program using libcoin80v5 and any other library that 
uses lebexpat1 segfaults.
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.)


-- 
874727: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874727
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libcoin80v5
Version: 3.1.4~abc9f50+dfsg1-2
Severity: critical
Justification: breaks unrelated software

Dear Maintainer,

Due to the change in libexpat1 (since 2.2.0, currently at 2.2.3) the included 
copy of it in libcoin results in segfaults of any program that uses libexpat1. 
Specifically any program that uses xml from python and links against libcoin 
will segfault.

The stacktrace looks like it is a problem with libexpat1 leading to a segfault 
in XML_SetHashSalt - however looking at that function there is no way it could 
possibly segfault - unless of course the provided XMLParser pointer does not 
actually point to what expat expects to be an XMLParser - which is indeed the 
case because the XMLParser instance was created by a call into lobcoin which is 
still on libexpat 2.2.0.

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

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

Versions of packages libcoin80v5 depends on:
ii  libc6 2.24-17
ii  libgcc1   1:7.2.0-3
ii  libgl1-mesa-glx [libgl1]  13.0.6-1+b2
ii  libice6   2:1.0.9-2
ii  libsm62:1.2.2-1+b3
ii  libstdc++67.2.0-3
ii  libx11-6  2:1.6.4-3
ii  libxext6  2:1.3.3-1+b2

libcoin80v5 recommends no packages.

Versions of packages libcoin80v5 suggests:
ii  libbz2-1.0 1.0.6-8.1
ii  libfreetype6   2.8-0.2
pn  libopenal0a
ii  libsimage-dev  1.7.1~2c958a6.dfsg-4
ii  zlib1g 1:1.2.8.dfsg-5

-- no debconf information
--- End Message ---
--- Begin Message ---
Since version 4.0.0~CMake~6f54f1602475+ds1-1~exp1 coin3 is not used the embed
version of expat and used the system one.





signature.asc
Description: OpenPGP digital signature
--- End Message ---

Bug#902505: Bug #902505 in node-cross-spawn marked as pending

[Ross Gammon]

Control: tag -1 pending

Hello,

Bug #902505 in node-cross-spawn 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/js-team/node-cross-spawn/commit/54bf04a4b8c0d6c55a85223d0d85d2c3544a7820


Fix FTBFS by adding which & lru-cache to Build-Depends

Closes: #902505


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/902505

Processed: Bug #902505 in node-cross-spawn marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #902505 [src:node-cross-spawn] node-cross-spawn: FTBFS in buster/sid 
(Cannot find module 'which')
Added tag(s) pending.

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

Bug#902452: Kamailio TLS module in Debian Stretch is unusable

[Victor Seva]

upstream fix included at 4.4.6
https://github.com/kamailio/kamailio/commit/406c02f7b76ada56d6e1f73e763fecb05c1f51c5

Bug#899728: marked as done (xfce4: Invalid maintainer address pkg-xfce-de...@lists.alioth.debian.org)

[Debian Bug Tracking System]

Your message dated Thu, 27 Dec 2018 15:07:41 +
with message-id 
and subject line Bug#899728: fixed in xfce4 4.12.5
has caused the Debian Bug report #899728,
regarding xfce4: Invalid maintainer address 
pkg-xfce-de...@lists.alioth.debian.org
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.)


-- 
899728: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899728
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:xfce4
Version: 4.12.4
Severity: serious
User: ad...@alioth-lists.debian.net
Usertag: alioth-lists-maintainer

Dear uploader of xfce4,

as you've probably heard, Debian's alioth services are shutting down.
This affects your package xfce4 since the list address
pkg-xfce-de...@lists.alioth.debian.org used in the Maintainer: field
was not transferred to the alioth-lists service that provides a
continuation for the lists in the @lists.alioth.debian.org domain.

Addresses that were not migrated have been disabled some time  ago. As
a result your package is now in violation of a "must" in the Debian
policy (3.3, working email address), making it unfit for release.

Please fix this before long. Among other reasons, keep in mind bug
reports and important notifications about your package might not reach
you.

Your options:

* Upload another version with a new maintainer address of your choice,

* Migrate the list to the new system. This is still possible,
  please appoint a Debian developer as a list owner first, then
  contact the alioth lists migration team 
  and provide all the necessary information.

  More information about the new service can be found here:
  

* More options, even if imperfect, can be found at
  


The first option is probably suitable only if the address was used just
in a small number of packages since this requires an upload for each of
them. To our knowledge, the usage count of
pkg-xfce-de...@lists.alioth.debian.org is 55.

The second option is available for a limited time only, by end of
May 2018 the most. So if you're interested in going this way, start the
process as soon as possible.

Note, as mails to the maintainer address will not get through, this
bugreport is Cc'ed (X-Debbugs-CC:) to all uploaders of the package.

Regards,

Christoph and some alioth-lists maintainers


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: xfce4
Source-Version: 4.12.5

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

Debian distribution maintenance software
pp.
Yves-Alexis Perez  (supplier of updated xfce4 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: Thu, 27 Dec 2018 15:39:12 +0100
Source: xfce4
Binary: xfce4
Architecture: source
Version: 4.12.5
Distribution: unstable
Urgency: medium
Maintainer: Debian Xfce Maintainers 
Changed-By: Yves-Alexis Perez 
Description:
 xfce4  - Meta-package for the Xfce Lightweight Desktop Environment
Closes: 899728
Changes:
 xfce4 (4.12.5) unstable; urgency=medium
 .
   * Moved the package to git on salsa.debian.org
   * Updated the maintainer address to debian-x...@lists.debian.org
 closes: #899728
   * d/gbp.conf added, following DEP-14
   * run wrap-and-sort
   * d/control: drop Lionel from uploaders, thanks!
   * d/control: update standards version to 4.3.0
   * d/control: use HTTPS protocol for homepage field
   * d/control: drop dependency on orage since it's unmaintained
   * d/control: fix typo in long description
   * d/source.lintian-overrides dropped, now useless
   * update debhelper compat to 10
Checksums-Sha1:
 a407ad6df0862243e90f430cd6a0390ecbaf9d37 1265 xfce4_4.12.5.dsc
 898e060d3e047e611818e48a3597e51d63a853b7 6776 xfce4_4.12.5.tar.xz
 c7f8d3a66a5f872321b98ea6934c732bd49dd956 5121 xfce4_4.12.5_amd64.buildinfo
Checksums-Sha256:
 a5769729b9d628786b87a2cd7cbc26bf771cac66ce9e4b89aeb5765f2f83d857 1265 

Bug#916171: marked as done (uml-utilities FTBFS with glibc 2.28)

[Debian Bug Tracking System]

Your message dated Thu, 27 Dec 2018 15:07:35 +
with message-id 
and subject line Bug#916171: fixed in uml-utilities 20070815.2-1
has caused the Debian Bug report #916171,
regarding uml-utilities FTBFS with glibc 2.28
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.)


-- 
916171: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916171
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: uml-utilities
Version: 20070815.1-3
Severity: serious
Tags: ftbfs

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

...
host.c: In function 'mk_node':
host.c:215:51: warning: implicit declaration of function 'makedev' 
[-Wimplicit-function-declaration]
   return(mknod(devname, S_IFCHR|S_IREAD|S_IWRITE, makedev(major, minor)));
   ^~~
...
cc -g -Wall -DTUNTAP -o uml_net ethertap.o host.o output.o slip.o uml_net.o 
tuntap.o
/usr/bin/ld: host.o: in function `mk_node':
/build/1st/uml-utilities-20070815.1/uml_net/host.c:215: undefined reference to 
`makedev'
collect2: error: ld returned 1 exit status
make[2]: *** [Makefile:18: uml_net] Error 1
--- End Message ---
--- Begin Message ---
Source: uml-utilities
Source-Version: 20070815.2-1

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

Debian distribution maintenance software
pp.
Ritesh Raj Sarraf  (supplier of updated uml-utilities 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: Thu, 27 Dec 2018 19:31:55 +0530
Source: uml-utilities
Binary: uml-utilities
Architecture: source amd64
Version: 20070815.2-1
Distribution: unstable
Urgency: medium
Maintainer: User Mode Linux Maintainers 
Changed-By: Ritesh Raj Sarraf 
Description:
 uml-utilities - User-mode Linux (utility programs)
Closes: 916171
Changes:
 uml-utilities (20070815.2-1) unstable; urgency=medium
 .
   [ New Maintenance Release ]
   * Don't delete uml_util.spec in clean target
   * Allow creation of tun IFF_TUN devices
   * Don't link against ncurses
   * Cleanup and re-add debian/ work
   * Fix debian/gbp.conf
   * Fix reference to makedev (Closes: #916171)
Checksums-Sha1:
 e3377ca60f33f860dd5d45ef51b5defd3ce9e95f 2089 uml-utilities_20070815.2-1.dsc
 5c7ffa4e61a6d3424ca790c84a2f5b5a6bb287c0 59084 
uml-utilities_20070815.2.orig.tar.gz
 c9b30c3f6dd703f158224f7d8ac98f5c91ef8a84 16416 
uml-utilities_20070815.2-1.debian.tar.xz
 cb0427a99878baabd47b19f90466dc417adb8cb9 6027 
uml-utilities_20070815.2-1_amd64.buildinfo
 52695431a7a7417273296adbc26fe7a627a5f43d 52436 
uml-utilities_20070815.2-1_amd64.deb
Checksums-Sha256:
 f651964d99c5f4da54d9ce4fc5b0b0b6c000172584b6c686faf0ebad12ecc7f3 2089 
uml-utilities_20070815.2-1.dsc
 e0a2e6d5bef99ee37d5127a6205e974c4ce01000358ae25980ee364aa5b6df67 59084 
uml-utilities_20070815.2.orig.tar.gz
 0ccea5e40ffb122cad0d9169a5a264192931fef0583dac3363129296d1085663 16416 
uml-utilities_20070815.2-1.debian.tar.xz
 dfdbaf9596f13f1a072c96d6e71ee40553a72b74e973003871410f06f43675c4 6027 
uml-utilities_20070815.2-1_amd64.buildinfo
 2c5d6939bbe48fac1c30abed4eb58e90620372745481970e27b2d33dbc81bad3 52436 
uml-utilities_20070815.2-1_amd64.deb
Files:
 87cdb31109164a73d28c6739607ebbe8 2089 otherosfs extra 
uml-utilities_20070815.2-1.dsc
 7b80f556f7b4bd9704a88cb4fbf4ea66 59084 otherosfs extra 
uml-utilities_20070815.2.orig.tar.gz
 4e0300a1b62601ffe6b1720e585d055c 16416 otherosfs extra 
uml-utilities_20070815.2-1.debian.tar.xz
 4ab2d26e2285ee73975ed550216ddf70 6027 otherosfs extra 
uml-utilities_20070815.2-1_amd64.buildinfo
 66290dc8db1b96f46afffbe9d959a6b1 52436 otherosfs extra 
uml-utilities_20070815.2-1_amd64.deb

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEQCVDstmIVAB/Yn02pjpYo/LhdWkFAlwk3aYACgkQpjpYo/Lh
dWkk0Q/+IHW09RbU8owoa9yzgCjp0AvrIPCgE8w1o+t5zvbvLnBgujXnOVwozoU/
K0u280RiK0pBiWzQqSX/ieYje1QKMwUMdUbbASuMF0450TERkf9NGHN+A1Y8ll34
7YvA1VTO+FlE3kE2NseCtAjtihPMXlFdb87/WFSnFPiYujes+nhE4IDoFTCZ135o
fQxsJkIQr6iDq8eX9TfIVY5jVYwsawrsvRWjKYZPLHCQFljOjZUoA15sh+KQ4iDL

Bug#899848: marked as done (xfce4-dev-tools: Invalid maintainer address pkg-xfce-de...@lists.alioth.debian.org)

[Debian Bug Tracking System]

Your message dated Thu, 27 Dec 2018 15:07:47 +
with message-id 
and subject line Bug#899848: fixed in xfce4-dev-tools 4.12.0-3
has caused the Debian Bug report #899848,
regarding xfce4-dev-tools: Invalid maintainer address 
pkg-xfce-de...@lists.alioth.debian.org
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.)


-- 
899848: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899848
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:xfce4-dev-tools
Version: 4.12.0-2
Severity: serious
User: ad...@alioth-lists.debian.net
Usertag: alioth-lists-maintainer

Dear uploader of xfce4-dev-tools,

as you've probably heard, Debian's alioth services are shutting down.
This affects your package xfce4-dev-tools since the list address
pkg-xfce-de...@lists.alioth.debian.org used in the Maintainer: field
was not transferred to the alioth-lists service that provides a
continuation for the lists in the @lists.alioth.debian.org domain.

Addresses that were not migrated have been disabled some time  ago. As
a result your package is now in violation of a "must" in the Debian
policy (3.3, working email address), making it unfit for release.

Please fix this before long. Among other reasons, keep in mind bug
reports and important notifications about your package might not reach
you.

Your options:

* Upload another version with a new maintainer address of your choice,

* Migrate the list to the new system. This is still possible,
  please appoint a Debian developer as a list owner first, then
  contact the alioth lists migration team 
  and provide all the necessary information.

  More information about the new service can be found here:
  

* More options, even if imperfect, can be found at
  


The first option is probably suitable only if the address was used just
in a small number of packages since this requires an upload for each of
them. To our knowledge, the usage count of
pkg-xfce-de...@lists.alioth.debian.org is 55.

The second option is available for a limited time only, by end of
May 2018 the most. So if you're interested in going this way, start the
process as soon as possible.

Note, as mails to the maintainer address will not get through, this
bugreport is Cc'ed (X-Debbugs-CC:) to all uploaders of the package.

Regards,

Christoph and some alioth-lists maintainers


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: xfce4-dev-tools
Source-Version: 4.12.0-3

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

Debian distribution maintenance software
pp.
Yves-Alexis Perez  (supplier of updated xfce4-dev-tools 
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: Thu, 27 Dec 2018 15:07:08 +0100
Source: xfce4-dev-tools
Binary: xfce4-dev-tools
Architecture: source
Version: 4.12.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Xfce Maintainers 
Changed-By: Yves-Alexis Perez 
Description:
 xfce4-dev-tools - Script to help building Xfce from git
Closes: 899848
Changes:
 xfce4-dev-tools (4.12.0-3) unstable; urgency=medium
 .
   * Moved the package to git on salsa.debian.org
   * Updated the maintainer address to debian-x...@lists.debian.org
 closes: #899848
   * d/gbp.conf added, following DEP-14
   * d/watch: use HTTPS protocol
   * run wrap-and-sort
   * d/control: drop Lionel from uploaders, thanks!
   * d/control: update standards version to 4.3.0
   * d/control: use HTTPS protocol
   * d/copyright: fix typo
   * Update debhelper compat to 10
Checksums-Sha1:
 d757334f0d8ecfd536635cafacbcd88252ddd588 1651 xfce4-dev-tools_4.12.0-3.dsc
 8ad02f98d4474161ab535f95df17bb8eb1debb58 4340 
xfce4-dev-tools_4.12.0-3.debian.tar.xz
 ead3282e76420544c295e749661e64c6284637e0 6303 
xfce4-dev-tools_4.12.0-3_amd64.buildinfo
Checksums-Sha256:
 

Bug#897482: marked as done (brailleutils: FTBFS with Java 10 due to return type change of javax.xml.namespace.NamespaceContext.getPrefixes​())

[Debian Bug Tracking System]

Your message dated Thu, 27 Dec 2018 14:53:36 +
with message-id 
and subject line Bug#897482: fixed in brailleutils 1.2.3-4
has caused the Debian Bug report #897482,
regarding brailleutils: FTBFS with Java 10 due to return type change of 
javax.xml.namespace.NamespaceContext.getPrefixes​()
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.)


-- 
897482: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897482
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: brailleutils
Version: 1.2.3-3
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20180502 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> mkdir lib # [empty] lib directory is assumeed by build.xml
> ant -DuseExternalJarsOnLinux=true
> Buildfile: /<>/build.xml
> 
> detectOS:
> 
> buildZip:
> 
> detectOS:
> 
> debianProperties:
> 
> setClasspath:
> 
> createDistDir:
> [mkdir] Created dir: /<>/ant-build/output/dist
> 
> buildCoreJar:
> [mkdir] Created dir: /<>/ant-build/output/build.temp
> [javac] Using javac -source 1.5 is no longer supported, switching to 1.7
> [javac] Using javac -target 1.5 is no longer supported, switching to 1.7
> [javac] Compiling 123 source files to 
> /<>/ant-build/output/build.temp
> [javac] warning: [options] bootstrap class path not set in conjunction 
> with -source 7
> [javac] 
> /<>/src/org/daisy/braille/pef/PEFNamespaceContext.java:37: 
> error: PEFNamespaceContext is not abstract and does not override abstract 
> method getPrefixes(String) in NamespaceContext
> [javac] public class PEFNamespaceContext implements NamespaceContext {
> [javac]^
> [javac] 
> /<>/src/org/daisy/braille/pef/PEFNamespaceContext.java:73: 
> error: getPrefixes(String) in PEFNamespaceContext cannot implement 
> getPrefixes(String) in NamespaceContext
> [javac]   public Iterator> getPrefixes(String 
> namespaceURI) {
> [javac]  ^
> [javac]   return type Iterator> is not compatible 
> with Iterator
> [javac] Note: /<>/src/org/daisy/braille/pef/TextHandler.java 
> uses or overrides a deprecated API.
> [javac] Note: Recompile with -Xlint:deprecation for details.
> [javac] 2 errors
> [javac] 1 warning
> 
> BUILD FAILED
> /<>/build.xml:354: The following error occurred while executing 
> this line:
> /<>/build.xml:209: Compile failed; see the compiler error output 
> for details.
> 
> Total time: 1 second
> make[1]: *** [debian/rules:28: override_dh_auto_build] Error 1

The full build log is available from:
   http://aws-logs.debian.net/2018/05/02/brailleutils_1.2.3-3_unstable.log

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

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

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

Debian distribution maintenance software
pp.
Samuel Thibault  (supplier of updated brailleutils 
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: Thu, 27 Dec 2018 14:53:41 +0100
Source: brailleutils
Binary: libbrailleutils-java libbrailleutils-java-doc brailleutils
Architecture: source
Version: 1.2.3-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Accessibility Team 
Changed-By: Samuel Thibault 
Description:
 brailleutils - command-line interface for the brailleutils library
 libbrailleutils-java - cross platform library for embossing/converting 
PEF-files
 libbrailleutils-java-doc - javadoc for brailleUtils for converting/embossing 
PEF files
Closes: 897482
Changes:
 brailleutils 

Bug#902452: Kamailio TLS module in Debian Stretch is unusable

[Victor Seva]

> kamailio[4041]: INFO: tls [tls_init.c:633]: init_tls_h(): tls:
_init_tls_h:  compiled  with  openssl  version "OpenSSL 1.1.0f  25 May
2017" (0x1010006f), kerberos support: on, compression: on
kamailio[4041]: INFO: tls [tls_init.c:641]: init_tls_h(): tls: init_tls_h:
installed openssl library version > "OpenSSL 1.1.0j  20 Nov 2018"
(0x101000af), kerberos support: off,  zlib compression: off
 compiler: gcc -DDSO_DLFCN -DHAVE_DLFCN_H -DNDEBUG -DOPENSSL_THREADS
-DOPENSSL_NO_STATIC_ENGINE -DOPENSSL_PIC -DOPENSSL_IA32_SSE2
-DOPENSSL_BN_ASM_MONT -DOPENSSL_BN_ASM_MONT5 -DOPENSSL_BN_ASM_GF2m
-DSHA1_ASM -DSHA256_ASM -DSHA512_ASM -DRC4_ASM -DMD5_ASM -DAES_ASM
-DVPAES_ASM -DBSAES_ASM -DGHASH_ASM -DECP_NISTZ256_ASM -DPADLOCK_ASM
-DPOLY1305_ASM -DOPENSSLDIR="\"/usr/lib/ssl\""
-DENGINESDIR="\"/usr/lib/x86_64-linux-gnu/engines-1.1\""
> kamailio[4041]: : tls [tls_init.c:651]: init_tls_h(): ERROR: tls:
init_tls_h: openssl compile options mismatch: library has kerberos support
disabled and Kamailio tls enabled (unstable configuration)
 (tls_force_run in kamailio.cfg will override this check)
> kamailio[4041]: CRITICAL:  [main.c:2592]: main(): could not
initialize tls, exiting...
> kamailio[4041]: INFO:  [sctp_core.c:53]: sctp_core_destroy(): SCTP
API not initialized

Full error output

Processed: merge

[Debian Bug Tracking System]

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

> forcemerge 917167 917357
Bug #917167 {Done: Michael Biebl } [systemd] systemd: 240 
breaks kde (rakes ages to launch)
Bug #917168 {Done: Michael Biebl } [systemd] systemd: fail to 
start kde after 240-1 upgrade
Bug #917173 {Done: Michael Biebl } [systemd] systemd 240-1 
breaks Plasma
Bug #917357 [systemd] systemd: nfs mount not possible with systemd 240-1
Severity set to 'grave' from 'normal'
Marked Bug as done
The source systemd and version 240-2 do not appear to match any binary packages
Marked as fixed in versions systemd/240-2.
Bug #917168 {Done: Michael Biebl } [systemd] systemd: fail to 
start kde after 240-1 upgrade
Bug #917173 {Done: Michael Biebl } [systemd] systemd 240-1 
breaks Plasma
Merged 917167 917168 917173 917357
>
End of message, stopping processing here.

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

Bug#917173: marked as done (systemd 240-1 breaks Plasma)

[Debian Bug Tracking System]

Your message dated Thu, 27 Dec 2018 13:55:36 +
with message-id 
and subject line Bug#917167: fixed in systemd 240-2
has caused the Debian Bug report #917167,
regarding systemd 240-1 breaks Plasma
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.)


-- 
917167: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917167
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: systemd
Version: 240-1
Severity: critical

Installing systemd 240-1 breaks plasma-workspace: xinit
/usr/bin/startkde hangs with a black screen, with kdeinit5 stuck at
100% CPU usage. Attaching strace to kdeinit5 reveals that it's trying
to close bogus file descriptors:

[..]
close(39936688) = -1 EBADF (Bad file descriptor)
close(39936688) = -1 EBADF (Bad file descriptor)
close(39936688) = -1 EBADF (Bad file descriptor)
close(39936688) = -1 EBADF (Bad file descriptor)
close(39936688) = -1 EBADF (Bad file descriptor)
close(39936688) = -1 EBADF (Bad file descriptor)
--- End Message ---
--- Begin Message ---
Source: systemd
Source-Version: 240-2

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

Debian distribution maintenance software
pp.
Michael Biebl  (supplier of updated systemd 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: Thu, 27 Dec 2018 14:03:57 +0100
Source: systemd
Binary: systemd systemd-sysv systemd-container systemd-journal-remote 
systemd-coredump systemd-tests libpam-systemd libnss-myhostname 
libnss-mymachines libnss-resolve libnss-systemd libsystemd0 libsystemd-dev udev 
libudev1 libudev-dev udev-udeb libudev1-udeb
Architecture: source
Version: 240-2
Distribution: unstable
Urgency: medium
Maintainer: Debian systemd Maintainers 

Changed-By: Michael Biebl 
Description:
 libnss-myhostname - nss module providing fallback resolution for the current 
hostname
 libnss-mymachines - nss module to resolve hostnames for local container 
instances
 libnss-resolve - nss module to resolve names via systemd-resolved
 libnss-systemd - nss module providing dynamic user and group name resolution
 libpam-systemd - system and service manager - PAM module
 libsystemd-dev - systemd utility library - development files
 libsystemd0 - systemd utility library
 libudev-dev - libudev development files
 libudev1   - libudev shared library
 libudev1-udeb - libudev shared library (udeb)
 systemd- system and service manager
 systemd-container - systemd container/nspawn tools
 systemd-coredump - tools for storing and retrieving coredumps
 systemd-journal-remote - tools for sending and receiving remote journal logs
 systemd-sysv - system and service manager - SysV links
 systemd-tests - tests for systemd
 udev   - /dev/ and hotplug management daemon
 udev-udeb  - /dev/ and hotplug management daemon (udeb)
Closes: 917124 917167 917195 917215
Changes:
 systemd (240-2) unstable; urgency=medium
 .
   * Pass seperate dev_t var to device_path_parse_major_minor.
 Fixes FTBFS on mips/mipsel (MIPS/O32). (Closes: #917195)
   * test-json: Check absolute and relative difference in floating point test.
 Fixes FTBFS due to test-suite failures on armel, armhf and hppa.
 (Closes: #917215)
   * sd-device: Fix segfault when error occurs in 
device_new_from_{nulstr,strv}()
 Fixes a segfault in systemd-udevd when debug logging is enabled.
   * udev-event: Do not read stdout or stderr if the pipefd is not created.
 This fixes problems with device-mapper symlinks no longer being created
 or certain devices not being marked as ready. (Closes: #917124)
   * Don't bump fs.nr_open in PID 1.
 In v240, systemd bumped fs.nr_open in PID 1 to the highest possible
 value. Processes that are spawned directly by systemd, will have
 RLIMIT_NOFILE be set to 512K (hard).
 pam_limits in Debian defaults to "set_all", i.e. for limits which are
 not explicitly configured in /etc/security/limits.conf, the value from
 PID 1 is taken, which means for login sessions, RLIMIT_NOFILE is set to
 the highest possible value instead of 512K. Not every 

Bug#917215: marked as done (systemd: FTBFS on armel and armhf (failing test))

[Debian Bug Tracking System]

Your message dated Thu, 27 Dec 2018 13:55:36 +
with message-id 
and subject line Bug#917215: fixed in systemd 240-2
has caused the Debian Bug report #917215,
regarding systemd: FTBFS on armel and armhf (failing test)
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.)


-- 
917215: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917215
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: systemd
Severity: serious
Justification: FTBFS

Hi

systemd/240-1 FTBFS on armel and armhf due to one failing test
accordin to the build log:

https://buildd.debian.org/status/fetch.php?pkg=systemd=armel=240-1=1545498332=0
https://buildd.debian.org/status/fetch.php?pkg=systemd=armhf=240-1=1545495147=0

(not checked if this might be a transient issue only).

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: systemd
Source-Version: 240-2

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

Debian distribution maintenance software
pp.
Michael Biebl  (supplier of updated systemd 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: Thu, 27 Dec 2018 14:03:57 +0100
Source: systemd
Binary: systemd systemd-sysv systemd-container systemd-journal-remote 
systemd-coredump systemd-tests libpam-systemd libnss-myhostname 
libnss-mymachines libnss-resolve libnss-systemd libsystemd0 libsystemd-dev udev 
libudev1 libudev-dev udev-udeb libudev1-udeb
Architecture: source
Version: 240-2
Distribution: unstable
Urgency: medium
Maintainer: Debian systemd Maintainers 

Changed-By: Michael Biebl 
Description:
 libnss-myhostname - nss module providing fallback resolution for the current 
hostname
 libnss-mymachines - nss module to resolve hostnames for local container 
instances
 libnss-resolve - nss module to resolve names via systemd-resolved
 libnss-systemd - nss module providing dynamic user and group name resolution
 libpam-systemd - system and service manager - PAM module
 libsystemd-dev - systemd utility library - development files
 libsystemd0 - systemd utility library
 libudev-dev - libudev development files
 libudev1   - libudev shared library
 libudev1-udeb - libudev shared library (udeb)
 systemd- system and service manager
 systemd-container - systemd container/nspawn tools
 systemd-coredump - tools for storing and retrieving coredumps
 systemd-journal-remote - tools for sending and receiving remote journal logs
 systemd-sysv - system and service manager - SysV links
 systemd-tests - tests for systemd
 udev   - /dev/ and hotplug management daemon
 udev-udeb  - /dev/ and hotplug management daemon (udeb)
Closes: 917124 917167 917195 917215
Changes:
 systemd (240-2) unstable; urgency=medium
 .
   * Pass seperate dev_t var to device_path_parse_major_minor.
 Fixes FTBFS on mips/mipsel (MIPS/O32). (Closes: #917195)
   * test-json: Check absolute and relative difference in floating point test.
 Fixes FTBFS due to test-suite failures on armel, armhf and hppa.
 (Closes: #917215)
   * sd-device: Fix segfault when error occurs in 
device_new_from_{nulstr,strv}()
 Fixes a segfault in systemd-udevd when debug logging is enabled.
   * udev-event: Do not read stdout or stderr if the pipefd is not created.
 This fixes problems with device-mapper symlinks no longer being created
 or certain devices not being marked as ready. (Closes: #917124)
   * Don't bump fs.nr_open in PID 1.
 In v240, systemd bumped fs.nr_open in PID 1 to the highest possible
 value. Processes that are spawned directly by systemd, will have
 RLIMIT_NOFILE be set to 512K (hard).
 pam_limits in Debian defaults to "set_all", i.e. for limits which are
 not explicitly configured in /etc/security/limits.conf, the value from
 PID 1 is taken, which means for login sessions, RLIMIT_NOFILE is set to
 the highest possible value instead of 512K. Not every software is able
 to deal with such an RLIMIT_NOFILE properly.
 While this is arguably a questionable default in Debian's pam_limit,
 work around this problem