Bug#892799: libtgvoip: Incomplete debian/copyright?

[Chris Lamb]

Source: libtgvoip
Version: 1.0.3-1
Severity: serious
Justication: Policy 12.5
X-Debbugs-CC: Nicholas Guriev 

Hi,

I just ACCEPTed libtgvoip from NEW but noticed it was missing 
attribution in debian/copyright for at least common_audio/fft4g.c
which looks like an embedded code copy.

I would also prefer to see some clarification in debian/copyright
about common_audio/signal_processing/spl_sqrt_floor.c.

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


Regards,

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

Bug#892798: ruby-crack FTBFS uninitialized constant SafeYAML::Parse::Date::DateTime (NameError)

[Pirate Praveen]

Package: ruby-crack
version: 0.4.3-2
Severity: serious

Autopkgtest also fails
https://ci.debian.net/data/packages/unstable/amd64/r/ruby-crack/latest-autopkgtest/log.gz

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

RUBYLIB=/<>/debian/ruby-crack/usr/lib/ruby/vendor_ruby:.
GEM_PATH=debian/ruby-crack/usr/share/rubygems-integration/all:/var/lib/gems/2.5.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.5.0:/usr/share/rubygems-integration/2.5.0:/usr/share/rubygems-integration/all
ruby2.5 -S rake -f debian/ruby-tests.rake
/usr/bin/ruby2.5 -w -I"lib:test"
"/usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb" "test/hash_test.rb"
"test/json_test.rb" "test/parser_test.rb" "test/string_test.rb"
"test/xml_test.rb"
/<>/test/hash_test.rb:10: warning: ambiguous first
argument; put parentheses or a space even after `/' operator
/<>/test/hash_test.rb:11: warning: ambiguous first
argument; put parentheses or a space even after `/' operator
/<>/test/hash_test.rb:12: warning: ambiguous first
argument; put parentheses or a space even after `/' operator
/<>/test/hash_test.rb:22: warning: ambiguous first
argument; put parentheses or a space even after `/' operator
/<>/test/hash_test.rb:23: warning: ambiguous first
argument; put parentheses or a space even after `/' operator
/<>/test/hash_test.rb:24: warning: ambiguous first
argument; put parentheses or a space even after `/' operator
/usr/lib/ruby/vendor_ruby/safe_yaml/parse/date.rb:22:in `':
uninitialized constant SafeYAML::Parse::Date::DateTime (NameError)
Did you mean?  SafeYAML::Parse::Date::DATE_MATCHER
from /usr/lib/ruby/vendor_ruby/safe_yaml/parse/date.rb:3:in 
`'
from /usr/lib/ruby/vendor_ruby/safe_yaml/parse/date.rb:2:in
`'
from /usr/lib/ruby/vendor_ruby/safe_yaml/parse/date.rb:1:in `'
from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in
`require'
from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in
`require'
from /usr/lib/ruby/vendor_ruby/safe_yaml/load.rb:14:in `'
from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in
`require'
from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in
`require'
from /<>/lib/crack/json.rb:6:in `'
from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in
`require'
from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in
`require'
from /<>/lib/crack.rb:6:in `'
from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in
`require'
from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in
`require'
from /<>/test/test_helper.rb:3:in `'
from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in
`require'
from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in
`require'
from /<>/test/hash_test.rb:1:in `'
from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in
`require'
from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in
`require'
from /usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb:17:in `block in
'
from /usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb:5:in `select'
from /usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb:5:in `'
rake aborted!
Command failed with status (1): [ruby -w -I"lib:test"
"/usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb" "test/hash_test.rb"
"test/json_test.rb" "test/parser_test.rb" "test/string_test.rb"
"test/xml_test.rb" ]

Tasks: TOP => default => test
(See full trace by running task with --trace)
ERROR: Test "ruby2.5" failed. Exiting.
dh_auto_install: dh_ruby --install /<>/debian/ruby-crack
returned exit code 1
make: *** [debian/rules:6: binary] Error 1
dpkg-buildpackage: error: fakeroot debian/rules binary subprocess
returned exit status 2

Build finished at 2018-03-13T04:58:47Z




signature.asc
Description: OpenPGP digital signature

Bug#892643: marked as done (deepin-image-viewer FTBFS with libdtkwidget-dev 2.0.7-1)

[Debian Bug Tracking System]

Your message dated Tue, 13 Mar 2018 03:34:27 +
with message-id 
and subject line Bug#892643: fixed in deepin-image-viewer 1.2.16.9-1
has caused the Debian Bug report #892643,
regarding deepin-image-viewer FTBFS with libdtkwidget-dev 2.0.7-1
to be marked as done.

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

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


-- 
892643: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892643
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: deepin-image-viewer
Version: 1.2.16.8-1
Severity: serious

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/deepin-image-viewer.html

...
main.cpp: In function 'int main(int, char**)':
main.cpp:36:5: error: 'DWIDGET_INIT_RESOURCE' was not declared in this scope
 DWIDGET_INIT_RESOURCE();
 ^
--- End Message ---
--- Begin Message ---
Source: deepin-image-viewer
Source-Version: 1.2.16.9-1

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

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

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

Debian distribution maintenance software
pp.
Boyuan Yang <073p...@gmail.com> (supplier of updated deepin-image-viewer 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 13 Mar 2018 09:46:26 +0800
Source: deepin-image-viewer
Binary: deepin-image-viewer
Architecture: source
Version: 1.2.16.9-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Deepin Packaging Team 

Changed-By: Boyuan Yang <073p...@gmail.com>
Description:
 deepin-image-viewer - Image Viewer for Deepin Desktop Environment
Closes: 892643
Changes:
 deepin-image-viewer (1.2.16.9-1) unstable; urgency=medium
 .
   * New upstream release.
   * Rebuild to fix FTBFS against new dtkwidget.
 Closes: #892643.
Checksums-Sha1:
 c4881fb4d666b8b7b03147761ae9ae3637a42c21 2523 
deepin-image-viewer_1.2.16.9-1.dsc
 bdb3859bd76dfb995af1a02811c98dc6302b9dc2 5320372 
deepin-image-viewer_1.2.16.9.orig.tar.gz
 c4ce1097213915dd60959d97e256788ab8588c19 2636 
deepin-image-viewer_1.2.16.9-1.debian.tar.xz
 569bf1fd0b38a43d59b8117ce0b6a43bd382f02e 14142 
deepin-image-viewer_1.2.16.9-1_amd64.buildinfo
Checksums-Sha256:
 6fa72373aad583b00ba7808b960d02fa326c85d45e2ec5b8da8b6ac0e3239d5b 2523 
deepin-image-viewer_1.2.16.9-1.dsc
 6f9e9565e648b924a84d1b16aeba7acd8462d3a1dca5b321f2ad14987c53478a 5320372 
deepin-image-viewer_1.2.16.9.orig.tar.gz
 648b7ecd0c02efcb70d8df519f8601f792215619656fb737aa97d6a034079d9d 2636 
deepin-image-viewer_1.2.16.9-1.debian.tar.xz
 f359df9d023277b81bd4d645162b1e7c08fd4417aca0e53c68aa359370f59dce 14142 
deepin-image-viewer_1.2.16.9-1_amd64.buildinfo
Files:
 90fbfa2000a10d81b526224b8ea6d6f1 2523 graphics optional 
deepin-image-viewer_1.2.16.9-1.dsc
 476544f3a16126bf9812c013651d7ca1 5320372 graphics optional 
deepin-image-viewer_1.2.16.9.orig.tar.gz
 0be0d618376edaccb22481680f35ec09 2636 graphics optional 
deepin-image-viewer_1.2.16.9-1.debian.tar.xz
 5e46b177384e4bc931f4398938b651e4 14142 graphics optional 
deepin-image-viewer_1.2.16.9-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEfncpR22H1vEdkazLwpPntGGCWs4FAlqnMDIACgkQwpPntGGC
Ws69kBAAjtnUxBIKr2nVoh06yW4aUj8fblQHFj51ZkQuPvAM2+y74rWOB0KxC2xy
15FQ2mliy4cjuyJHq3prODmVpSG7DE+/tDfblkAe6NE6ORZg1DlIx4uZqIP7JIfv
clGiJmjC0Qo70nPoporV4Qt+6Z0cpmCmJRR3m33IrmjSsPG/v8qjqfNTIuy4IjID
2yy8rIgZfbF42NoVW/W5IpNQuKvaDn+mDHVaa5ZbhaCFpSdvrPWinnc/6N7hEqsF
9k1dHpO26FEMcJu5CR26gxVbDABDbwkaQw1uUUiIrBqttrC7JsvORYhmHHyyWtMA
ozYjiU+ddvn0k27CLEyzBcL/rspWwPLE3Q2dUUhrXyNjnVvCKOX2lBBZ94IKQX5I
qeg2+Jt6A7voM0F9EpP/n4TNEDa8WaNj2R1JO/IkieHlFSq97zyYJfkmH4BSaJTU
uHJBvzfBWF5iM6V04VqFzBPu3lcxVODWS1Knwyg2dSAChMiiT2JVsUxCfIb8nzY5
Oy6p+Rq2iEmEag4auqk7X3MlfPYOdKzIFdLEI5gRGngQPC5DYimwFahdeUlhPGkR
iNmSEGSQHanrMArF6ta7o9b0BLIv3xdZDDN/8k+LHAPb1RYtDAlSenY5Fb8HFNPZ
sYlK/1/gMgR8Ksg/ryjXJyjxclVCZ5ScI1aoB/6UiPSjxfL0KG4=
=2iIt
-END PGP SIGNATURE End Message ---

Processed: #892743: patch for hg 4.0

[Debian Bug Tracking System]

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

> tags 892743 +patch
Bug #892743 [mercurial] permissions bypass on http server
Added tag(s) patch.
> thanks
Stopping processing here.

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

Bug#892711: marked as done (python-pymodbus-doc: fails to upgrade from 'stable' to 'sid' - trying to overwrite /usr/share/doc/python-pymodbus/examples/common/README.rst)

[Debian Bug Tracking System]

Your message dated Mon, 12 Mar 2018 22:55:29 +
with message-id 
and subject line Bug#892711: fixed in pymodbus 1.4.0+dfsg-2
has caused the Debian Bug report #892711,
regarding python-pymodbus-doc: fails to upgrade from 'stable' to 'sid' - trying 
to overwrite /usr/share/doc/python-pymodbus/examples/common/README.rst
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.)


-- 
892711: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892711
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-pymodbus-doc
Version: 1.4.0+dfsg-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

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

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

  Selecting previously unselected package python-pymodbus-doc.
  Preparing to unpack .../6-python-pymodbus-doc_1.4.0+dfsg-1_all.deb ...
  Unpacking python-pymodbus-doc (1.4.0+dfsg-1) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-Y42ubM/6-python-pymodbus-doc_1.4.0+dfsg-1_all.deb 
(--unpack):
   trying to overwrite 
'/usr/share/doc/python-pymodbus/examples/common/README.rst', which is also in 
package python-pymodbus 1.2.0+git20151013-1
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /tmp/apt-dpkg-install-Y42ubM/6-python-pymodbus-doc_1.4.0+dfsg-1_all.deb


cheers,

Andreas


python-pymodbus=1.2.0+git20151013-1_python-pymodbus-doc=1.4.0+dfsg-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: pymodbus
Source-Version: 1.4.0+dfsg-2

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

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

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

Debian distribution maintenance software
pp.
W. Martin Borgert  (supplier of updated pymodbus 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: Mon, 12 Mar 2018 22:00:03 +
Source: pymodbus
Binary: python-pymodbus python3-pymodbus python-pymodbus-doc
Architecture: source all
Version: 1.4.0+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: W. Martin Borgert 
Description:
 python-pymodbus - full Modbus protocol implementation for Python 2
 python-pymodbus-doc - full Modbus protocol implementation, documentation
 python3-pymodbus - full Modbus protocol implementation for Python 3
Closes: 892711
Changes:
 pymodbus (1.4.0+dfsg-2) unstable; urgency=medium
 .
   * Move docs back into -doc package (Closes: #892711)
Checksums-Sha1:
 759d72b81037a172ddc5f0c0dbe2d989a1872276 2522 pymodbus_1.4.0+dfsg-2.dsc
 19e6da4a60023bfe64f0cb3877963f4ad7a5b846 5480 
pymodbus_1.4.0+dfsg-2.debian.tar.xz
 a1df9392375476b1fc1d7747d43ab2ec7c28685d 9496 
pymodbus_1.4.0+dfsg-2_amd64.buildinfo
 64bedfc5084090d29aec22d39ea10fd8db623704 201840 
python-pymodbus-doc_1.4.0+dfsg-2_all.deb
 260a7d5923132783391c9d1cc0eb1e86c6eca6db 57284 
python-pymodbus_1.4.0+dfsg-2_all.deb
 16851f7118cb01becc861bf7799d12725c49d65f 57364 
python3-pymodbus_1.4.0+dfsg-2_all.deb
Checksums-Sha256:
 38c11caf0b642abd5b9c34fa86b0a0ac5dfa69e7bd8e719f582f0d244aff52e7 2522 
pymodbus_1.4.0+dfsg-2.dsc
 cd7bd3e132d8d3f3f5d939950981904705429c6f0af5516d22e7daf394c54953 5480 
pymodbus_1.4.0+dfsg-2.debian.tar.xz
 8e1663ee07705bb8c8221593aad8718f47fb46826e6ae71991efbd725f5a19dd 9496 
pymodbus_1.4.0+dfsg-2_amd64.buildinfo
 a29a6c3cdf5c9599e7d6767a801be3473bc6465463fcf59fd54424f4a4be1b85 201840 
python-pymodbus-doc_1.4.0+dfsg-2_all.deb
 

Bug#874220: stretch update for openni2

[Jochen Sprickerhof]

* Adrian Bunk  [2018-03-12 20:52]:

On Mon, Sep 11, 2017 at 09:18:05PM +, Debian Bug Tracking System wrote:

...
 openni2 (2.2.0.33+dfsg-10) unstable; urgency=medium
 .
   * Add patch for arm.
 Thanks to Adrian Bunk (Closes: #874220)
...


Thanks a lot for fixing this bug for unstable.

It is still present in stretch, could you also fix it there?
Alternatively, I can fix it for stretch if you don't object.


Fell free to fix it :).

Thanks

Jochen


signature.asc
Description: PGP signature

Bug#880886: maven-bundle-plugin FTBFS with libmaven-dependency-tree-java

[Emmanuel Bourg]

Le 08/03/2018 à 13:29, 殷啟聰 | Kai-Chung Yan a écrit :

> I tried building Maven Dependency Tree 2.2 against Maven 3.x and found that 
> it uses removed APIs, and that patching it would make a huge code change. 
> Maybe someone else would have a better skill than me to do the job, but I 
> simply don't think this is a good or sustainable idea...

It looks like Fedora has already done the job:

https://src.fedoraproject.org/rpms/maven-plugin-bundle/blob/master/f/0001-Port-to-current-maven-dependency-tree.patch

With this patch they build the bundle plugin 3.5.0 with
maven-dependency-tree 3.0.

Bug#892787: python-asyncssh: CVE-2018-7749

[Salvatore Bonaccorso]

Source: python-asyncssh
Version: 1.11.1-1
Severity: grave
Tags: patch security upstream

Hi,

the following vulnerability was published for python-asyncssh,
although there should be not "servers" implemented in Debian
depending on python3-asyncssh, still chosed an RC severity to have the
fix certain included in next stable release (but expect that 1.12.1
land soon anyhow in unstable).

CVE-2018-7749[0]:
| The SSH server implementation of AsyncSSH before 1.12.1 does not
| properly check whether authentication is completed before processing
| other requests. A customized SSH client can simply skip the
| authentication step.

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-7749
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-7749
[1] 
https://github.com/ronf/asyncssh/commit/c161e26cdc0d41b745b63d9f17b437f073bf7ba4

Regards,
Salvatore

Bug#892785: zaqar-ui FTBFS: ImportError: No module named openstack_dashboard.test.settings

[Adrian Bunk]

Source: zaqar-ui
Version: 1.0.0~rc1-2
Severity: serious
Tags: buster sid

Some recent change in unstable makes zaqar-ui FTBFS:

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

...
   debian/rules override_dh_auto_test
make[1]: Entering directory '/build/1st/zaqar-ui-1.0.0~rc1'
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
bash run_tests.sh -N --no-pep8
Running Zaqar UI tests
Traceback (most recent call last):
  File "/build/1st/zaqar-ui-1.0.0~rc1/manage.py", line 23, in 
execute_from_command_line(sys.argv)
  File "/usr/lib/python2.7/dist-packages/django/core/management/__init__.py", 
line 364, in execute_from_command_line
utility.execute()
  File "/usr/lib/python2.7/dist-packages/django/core/management/__init__.py", 
line 308, in execute
settings.INSTALLED_APPS
  File "/usr/lib/python2.7/dist-packages/django/conf/__init__.py", line 56, in 
__getattr__
self._setup(name)
  File "/usr/lib/python2.7/dist-packages/django/conf/__init__.py", line 41, in 
_setup
self._wrapped = Settings(settings_module)
  File "/usr/lib/python2.7/dist-packages/django/conf/__init__.py", line 110, in 
__init__
mod = importlib.import_module(self.SETTINGS_MODULE)
  File "/usr/lib/python2.7/importlib/__init__.py", line 37, in import_module
__import__(name)
ImportError: No module named openstack_dashboard.test.settings
Tests failed.
make[1]: *** [debian/rules:10: override_dh_auto_test] Error 1

Bug#892784: zaqar FTBFS: test failures

[Adrian Bunk]

Source: zaqar
Version: 6.0.0-1
Severity: serious

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

...
==
FAIL: 
zaqar.tests.unit.transport.websocket.v2.test_claims.ClaimsBaseTest.test_bad_claim_2___
zaqar.tests.unit.transport.websocket.v2.test_claims.ClaimsBaseTest.test_bad_claim_2___
--
_StringException: pythonlogging:'zaqar': {{{Response: API v2 txt, 204. Request: 
action "queue_create", body {"queue_name": "skittle"}.}}}

Traceback (most recent call last):
  File 
"/build/1st/zaqar-6.0.0/zaqar/tests/unit/transport/websocket/v2/test_claims.py",
 line 50, in setUp
self.assertEqual(201, resp['headers']['status'])
  File "/usr/lib/python3/dist-packages/testtools/testcase.py", line 411, in 
assertEqual
self.assertThat(observed, matcher, message)
  File "/usr/lib/python3/dist-packages/testtools/testcase.py", line 498, in 
assertThat
raise mismatch_error
testtools.matchers._impl.MismatchError: 201 != 204


==
FAIL: 
zaqar.tests.unit.transport.websocket.v2.test_claims.ClaimsBaseTest.test_bad_claim_4__fail_
zaqar.tests.unit.transport.websocket.v2.test_claims.ClaimsBaseTest.test_bad_claim_4__fail_
--
_StringException: pythonlogging:'zaqar': {{{Response: API v2 txt, 204. Request: 
action "queue_create", body {"queue_name": "skittle"}.}}}

Traceback (most recent call last):
  File 
"/build/1st/zaqar-6.0.0/zaqar/tests/unit/transport/websocket/v2/test_claims.py",
 line 50, in setUp
self.assertEqual(201, resp['headers']['status'])
  File "/usr/lib/python3/dist-packages/testtools/testcase.py", line 411, in 
assertEqual
self.assertThat(observed, matcher, message)
  File "/usr/lib/python3/dist-packages/testtools/testcase.py", line 498, in 
assertThat
raise mismatch_error
testtools.matchers._impl.MismatchError: 201 != 204


==
FAIL: 
zaqar.tests.unit.transport.websocket.v2.test_claims.ClaimsBaseTest.test_get_claim_nonexistent_queue
zaqar.tests.unit.transport.websocket.v2.test_claims.ClaimsBaseTest.test_get_claim_nonexistent_queue
--
_StringException: pythonlogging:'zaqar': {{{Response: API v2 txt, 204. Request: 
action "queue_create", body {"queue_name": "skittle"}.}}}

Traceback (most recent call last):
  File 
"/build/1st/zaqar-6.0.0/zaqar/tests/unit/transport/websocket/v2/test_claims.py",
 line 50, in setUp
self.assertEqual(201, resp['headers']['status'])
  File "/usr/lib/python3/dist-packages/testtools/testcase.py", line 411, in 
assertEqual
self.assertThat(observed, matcher, message)
  File "/usr/lib/python3/dist-packages/testtools/testcase.py", line 498, in 
assertThat
raise mismatch_error
testtools.matchers._impl.MismatchError: 201 != 204


==
FAIL: 
zaqar.tests.unit.transport.websocket.v2.test_claims.ClaimsBaseTest.test_bad_claim_3__
zaqar.tests.unit.transport.websocket.v2.test_claims.ClaimsBaseTest.test_bad_claim_3__
--
_StringException: pythonlogging:'zaqar': {{{Response: API v2 txt, 204. Request: 
action "queue_create", body {"queue_name": "skittle"}.}}}

Traceback (most recent call last):
  File 
"/build/1st/zaqar-6.0.0/zaqar/tests/unit/transport/websocket/v2/test_claims.py",
 line 50, in setUp
self.assertEqual(201, resp['headers']['status'])
  File "/usr/lib/python3/dist-packages/testtools/testcase.py", line 411, in 
assertEqual
self.assertThat(observed, matcher, message)
  File "/usr/lib/python3/dist-packages/testtools/testcase.py", line 498, in 
assertThat
raise mismatch_error
testtools.matchers._impl.MismatchError: 201 != 204


==
FAIL: 
zaqar.tests.unit.transport.websocket.v2.test_messages.MessagesBaseTest.test_post_invalid_ttl
zaqar.tests.unit.transport.websocket.v2.test_messages.MessagesBaseTest.test_post_invalid_ttl
--
_StringException: pythonlogging:'zaqar': {{{Response: API v2 txt, 204. Request: 
action "queue_create", body {"queue_name": "kitkat"}.}}}

Traceback (most recent call last):
  File 
"/build/1st/zaqar-6.0.0/zaqar/tests/unit/transport/websocket/v2/test_messages.py",
 line 56, in setUp
self.assertEqual(201, resp['headers']['status'])
  File "/usr/lib/python3/dist-packages/testtools/testcase.py", line 411, in 
assertEqual
self.assertThat(observed, matcher, message)
  File "/usr/lib/python3/dist-packages/testtools/testcase.py", line 498, in 
assertThat
raise mismatch_error
testtools.matchers._impl.MismatchError: 201 != 204

Bug#892783: watcher FTBFS: test failures

[Adrian Bunk]

Source: watcher
Version: 1.4.1-3
Severity: serious

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

...
==
FAIL: watcher.tests.common.test_clients.TestClients.test_clients_gnocchi_cached
watcher.tests.common.test_clients.TestClients.test_clients_gnocchi_cached
--
_StringException: Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/mock/mock.py", line 1305, in patched
return func(*args, **keywargs)
  File "watcher/tests/common/test_clients.py", line 218, in 
test_clients_gnocchi_cached
gnocchi = osc.gnocchi()
  File "watcher/common/exception.py", line 46, in wrapped
return func(*args, **kw)
  File "watcher/common/clients.py", line 115, in gnocchi
session=self.session)
  File "/usr/lib/python2.7/dist-packages/gnocchiclient/client.py", line 24, in 
Client
return client_class(*args, **kwargs)
TypeError: __init__() got an unexpected keyword argument 'interface'


==
FAIL: 
watcher.tests.common.test_clients.TestClients.test_clients_gnocchi_diff_endpoint
watcher.tests.common.test_clients.TestClients.test_clients_gnocchi_diff_endpoint
--
_StringException: Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/mock/mock.py", line 1305, in patched
return func(*args, **keywargs)
  File "watcher/tests/common/test_clients.py", line 211, in 
test_clients_gnocchi_diff_endpoint
osc.gnocchi()
  File "watcher/common/exception.py", line 46, in wrapped
return func(*args, **kw)
  File "watcher/common/clients.py", line 115, in gnocchi
session=self.session)
  File "/usr/lib/python2.7/dist-packages/gnocchiclient/client.py", line 24, in 
Client
return client_class(*args, **kwargs)
TypeError: __init__() got an unexpected keyword argument 'interface'


==
FAIL: 
watcher.tests.common.test_clients.TestClients.test_clients_gnocchi_diff_vers
watcher.tests.common.test_clients.TestClients.test_clients_gnocchi_diff_vers
--
_StringException: Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/mock/mock.py", line 1305, in patched
return func(*args, **keywargs)
  File "watcher/tests/common/test_clients.py", line 202, in 
test_clients_gnocchi_diff_vers
osc.gnocchi()
  File "watcher/common/exception.py", line 46, in wrapped
return func(*args, **kw)
  File "watcher/common/clients.py", line 115, in gnocchi
session=self.session)
  File "/usr/lib/python2.7/dist-packages/gnocchiclient/client.py", line 24, in 
Client
return client_class(*args, **kwargs)
TypeError: __init__() got an unexpected keyword argument 'interface'


==
FAIL: watcher.tests.common.test_service.TestService.test_build_topic_handler
watcher.tests.common.test_service.TestService.test_build_topic_handler
--
_StringException: Traceback (most recent call last):
  File "watcher/tests/common/test_service.py", line 94, in 
test_build_topic_handler
dummy_service = service.Service(DummyManager)
  File "watcher/common/service.py", line 204, in __init__
self.conductor_topic, self.conductor_endpoints)
  File "watcher/common/service.py", line 249, in build_topic_handler
access_policy=access_policy)
  File "/usr/lib/python2.7/dist-packages/oslo_messaging/rpc/server.py", line 
208, in get_rpc_server
access_policy)
  File "/usr/lib/python2.7/dist-packages/oslo_messaging/rpc/dispatcher.py", 
line 161, in __init__
raise TypeError("%s: endpoint=%s" % (errmsg, ep))
TypeError: 'target' is a reserved Endpoint attribute used for namespace and 
version filtering.  It must be of type oslo_messaging.Target. Do not define an 
Endpoint method named 'target': endpoint=


==
FAIL: watcher.tests.common.test_service.TestService.test_init_service
watcher.tests.common.test_service.TestService.test_init_service
--
_StringException: Traceback (most recent call last):
  File "watcher/tests/common/test_service.py", line 101, in test_init_service
dummy_service = service.Service(DummyManager)
  File "watcher/common/service.py", line 204, in __init__
self.conductor_topic, self.conductor_endpoints)
  File "watcher/common/service.py", line 249, in build_topic_handler
access_policy=access_policy)
  File "/usr/lib/python2.7/dist-packages/oslo_messaging/rpc/server.py", line 
208, in get_rpc_server
access_policy)
  File 

Bug#892690: marked as done (autoconf-archive: ax_lib_postgresql.m4 must be updated to work with the Debian-specific version string)

[Debian Bug Tracking System]

Your message dated Mon, 12 Mar 2018 20:51:05 +
with message-id 
and subject line Bug#892690: fixed in autoconf-archive 20170928-2
has caused the Debian Bug report #892690,
regarding autoconf-archive: ax_lib_postgresql.m4 must be updated to work with 
the Debian-specific version string
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.)


-- 
892690: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892690
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libpq-dev
Version: 10.1-3
Severity: serious
Control: affects -1 src:libpreludedb

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

...
checking for ... checking for pg_config... /usr/bin/pg_config
checking for PostgreSQL libraries... yes
./configure: line 19300: test: too many arguments
...
   dh_install
dh_install: Cannot find (any matches for) 
"debian/tmp/usr/lib/*/libpreludedb/plugins/sql/pgsql*" (tried in ., debian/tmp)

dh_install: libpreludedb7-pgsql missing files: 
debian/tmp/usr/lib/*/libpreludedb/plugins/sql/pgsql*
dh_install: missing files, aborting
debian/rules:27: recipe for target 'binary' failed
make: *** [binary] Error 25


Root cause:

postgresql-10 (10.1-3) unstable; urgency=medium
...
  * Include package version number in "extra version" so it is reported by
"psql --version" and friends.

https://sources.debian.org/src/autoconf-archive/20170321-1/m4/ax_lib_postgresql.m4/#L97
--- End Message ---
--- Begin Message ---
Source: autoconf-archive
Source-Version: 20170928-2

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

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

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

Debian distribution maintenance software
pp.
Bastien Roucariès  (supplier of updated autoconf-archive 
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: Mon, 12 Mar 2018 21:41:18 +0100
Source: autoconf-archive
Binary: autoconf-archive
Architecture: source
Version: 20170928-2
Distribution: unstable
Urgency: medium
Maintainer: Bastien Roucariès 
Changed-By: Bastien Roucariès 
Description:
 autoconf-archive - Autoconf Macro Archive
Closes: 892690
Changes:
 autoconf-archive (20170928-2) unstable; urgency=medium
 .
   * Bug fix: "ax_lib_postgresql.m4 must be updated to work with the
 Debian-specific version string", thanks to Adrian Bunk (Closes:
 #892690).
Checksums-Sha1:
 e14413f4fbd618ff7a3be64229a0d79afb0871c2 2320 autoconf-archive_20170928-2.dsc
 57fb2206dc55dcc8d6ea8a3854c133d6d88c8978 41728 
autoconf-archive_20170928-2.debian.tar.xz
 873e0f76ad56576ab1fadeae0d5d2d11ec906265 5979 
autoconf-archive_20170928-2_source.buildinfo
Checksums-Sha256:
 9f899d7e2e3944eedc51d3781dd9c577362a66297c9abc5bf574aaf7fa96dde7 2320 
autoconf-archive_20170928-2.dsc
 3e8fa718e4f8398d6998f40d4694cabc2feae7a08a1365873876b03af69a710d 41728 
autoconf-archive_20170928-2.debian.tar.xz
 330c604a1ac3160ac2520a09c8de496d2b120cab741db90de7cbd9ccb3584474 5979 
autoconf-archive_20170928-2_source.buildinfo
Files:
 5e6a7387a5c231fc8a600d50de906120 2320 devel optional 
autoconf-archive_20170928-2.dsc
 494002006428e5efd684db2fb81551ad 41728 devel optional 
autoconf-archive_20170928-2.debian.tar.xz
 b64fbfabc0a16f5a5d1a40e36c6fa16a 5979 devel optional 
autoconf-archive_20170928-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEXQGHuUCiRbrXsPVqADoaLapBCF8FAlqm5tEACgkQADoaLapB
CF+N4hAAsuxUSiJg5NVWf2JxwhMG0S+PhKlB8RDrASDirPzVxKfcNLMfzoCWu8rA
lcLakVimfZ5iYiFZag7/hSXATA1oCNMoeGr0CFPTpp8BQ2qkZ8vRqkvYu+QqJUvd
KFqzZFFzFJ8wWRDQALZ8WlntpOvptsfeOeatmUfQkUyXus6sSE7DUXB35sB1ZBiF
9stz2d05W9M1o+7cpRvks3y/Dsvq/HMV7lgskOBATB7aB1iPTR3MyJ/T3wXUm/OT
8lW1PVeD+UAHjIZyllNuvxYDVEcsRkPE+byKXes492Abaepm3gnxIBPZbPaW2+d1
VwzNwR7ypkuFS6Xys8f98NLAw88NbvzECuIWMV9ay1TfK6Bs8e3iZykyICsCicEW
P0C6htF3Mw0Zqrs1UvST5mBlxMElu7lJF0nJz7XmPKNq1r2LjeUDhQ6pS/dDz2L/
NMxJLthIX+KMKgbut+uM/8GdgreplSl0SbnBkO1xpMYzA1Csp03MkhVOQzed1iD/
midfEsCGZNEsa7/0YfEP9vnRxpJmhFJa4kxr0UK628PLR0uzHHBIXNstYUoAZkAj

Bug#890954: upload 65.0.3325.146-2

[積丹尼 Dan Jacobson]

Please upload 65.0.3325.146-2 to experimental so we can test. Thanks.

Processed: found 892766 in 57.1-1

[Debian Bug Tracking System]

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

> found 892766 57.1-1
Bug #892766 [src:icu] CVE-2017-15422
Marked as found in versions icu/57.1-1.
> thanks
Stopping processing here.

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

Processed: found 892766 in 52.1-8

[Debian Bug Tracking System]

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

> found 892766 52.1-8
Bug #892766 [src:icu] CVE-2017-15422
Marked as found in versions icu/52.1-8.
> thanks
Stopping processing here.

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

Processed: bug 892766 is forwarded to https://bugs.chromium.org/p/chromium/issues/detail?id=774382

[Debian Bug Tracking System]

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

> forwarded 892766 https://bugs.chromium.org/p/chromium/issues/detail?id=774382
Bug #892766 [src:icu] CVE-2017-15422
Set Bug forwarded-to-address to 
'https://bugs.chromium.org/p/chromium/issues/detail?id=774382'.
> thanks
Stopping processing here.

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

Processed: fixed 892766 in 60.1-1

[Debian Bug Tracking System]

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

> fixed 892766 60.1-1
Bug #892766 [src:icu] CVE-2017-15422
Marked as fixed in versions icu/60.1-1.
> thanks
Stopping processing here.

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

Bug#892766: CVE-2017-15422

[Salvatore Bonaccorso]

Control: tags 892766 + upstream fixed-upstream

Hi Moritz, hi Laszlo,

On Mon, Mar 12, 2018 at 07:54:37PM +0100, Moritz Muehlenhoff wrote:
> Source: icu
> Severity: grave
> Tags: security
> 
> Hi Laszlo,
> https://chromereleases.googleblog.com/2017/12/stable-channel-update-for-desktop.html
> refers to a ICU vulnerability, but there's little information what 
> fixes/fixed that.
> 
> Could you reach out to upstream whether they've been in touch with them so 
> that
> we can pinpoint this a specific task/commit?

The upstream issue is now accessible, at
https://bugs.chromium.org/p/chromium/issues/detail?id=774382 which
refers to the interger overflow related to the persian calendar
integer overflow, leading to oob read. The comment #16 indicates which
change fixed the bug:
https://bugs.chromium.org/p/chromium/issues/detail?id=774382#c16 which
in turns would be integrated in the following upstream change:
https://ssl.icu-project.org/trac/changeset/40654

Regards,
Salvatore

Processed: Re: Bug#892766: CVE-2017-15422

[Debian Bug Tracking System]

Processing control commands:

> tags 892766 + upstream fixed-upstream
Bug #892766 [src:icu] CVE-2017-15422
Added tag(s) fixed-upstream and upstream.

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

Bug#892372: proftpd-mod-msg FTBFS with proftpd 1.3.6-1

[Hilmar Preuße]

On 09.03.2018 16:35, Francesco P. Lovergine wrote:
> On Thu, Mar 08, 2018 at 05:27:10PM +0200, Adrian Bunk wrote:

Hi,

>> mod_msg.c:56:3: error: #error "mod_msg requires Controls support
>> (--enable-ctrls)"
>> # error "mod_msg requires Controls support (--enable-ctrls)"
>>   ^
>>
> 
> This is another trivial fix, just s/USE_CTRLS/PR_USE_CTRLS/ in source.
> 
Sorry, was not that easy. I'll contact tj directly; this module is not
on github.

Hilmar
-- 
#206401 http://counter.li.org

Processed: found 892766 in 57.1-8

[Debian Bug Tracking System]

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

> found 892766 57.1-8
Bug #892766 [src:icu] CVE-2017-15422
Marked as found in versions icu/57.1-8.
> thanks
Stopping processing here.

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

Bug#892373: [INFO] Bug#892373: proftpd-mod-fsync FTBFS with proftpd 1.3.6-1

[Hilmar Preuße]

On 10.03.2018 08:44, Francesco Paolo Lovergine wrote:

Hi Francesco,

> Nave a look onto  Castaglia's github repo
> 
I've updated the git repo to 0.3, attached is the new orig.tar.gz.

Hilmar
-- 
#206401 http://counter.li.org


proftpd-mod-fsync_0.3.orig.tar.gz
Description: application/gzip

Bug#892371: proftpd-mod-vroot FTBFS with proftpd 1.3.6-1

[Hilmar Preuße]

On 09.03.2018 16:19, Francesco P. Lovergine wrote:
> On Thu, Mar 08, 2018 at 05:25:20PM +0200, Adrian Bunk wrote:

Hi Francesco,

>> mod_vroot.c: In function 'vroot_pre_pass':
>> mod_vroot.c:1651:7: error: 'pr_fs_t {aka struct fs_rec}' has no member
>> named 'creat'; did you mean 'read'?
>>   fs->creat = vroot_creat;
>>   ^
>>
> 
> This is fixed in 0.9.7, better upgrading.
> 
I've pulled the two patches from github fixing this bug. They are in our
git, feel free to upload. The new version does not bring many
improvement IMHO, so this can be delayed.

Hilmar
-- 
#206401 http://counter.li.org

Processed: evolution-rss: raising severity of gconf dependency bug

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #885823 [src:evolution-rss] evolution-rss: Depends on gconf
Severity set to 'serious' from 'important'

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

Processed: bump severity

[Debian Bug Tracking System]

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

> severity 846938 serious
Bug #846938 [src:dhcpcd5] dhcpcd5: CVE-2014-7913
Severity set to 'serious' from 'important'
>
End of message, stopping processing here.

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

Processed: set blocker bugs

[Debian Bug Tracking System]

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

> block 892771 by 892768
Bug #892771 [ftp.debian.org] RM: libgksu -- RoM; RoQA; unmaintained, 
security-sensitive
892771 was not blocked by any bugs.
892771 was not blocking any bugs.
Added blocking bug(s) of 892771: 892768
> block 892768 by 892767
Bug #892768 [ftp.debian.org] RM: gksu -- RoM; RoQA; unmaintained
892768 was not blocked by any bugs.
892768 was blocking: 892771
Added blocking bug(s) of 892768: 892767
> block 892709 by 870418
Bug #892709 [src:libgtk2-imageview-perl] libgtk2-imageview-perl: Remove 
libgtk2-imageview-perl during the Buster cycle
892709 was not blocked by any bugs.
892709 was not blocking any bugs.
Added blocking bug(s) of 892709: 870418
>
End of message, stopping processing here.

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

Bug#890254: stretch update for gf2x

[Adrian Bunk]

On Mon, Feb 12, 2018 at 05:51:03PM +, Debian Bug Tracking System wrote:
>...
>  gf2x (1.2-4) unstable; urgency=medium
>  .
>* Team upload.
>* Actually disable HW-specific code also on i386. (Closes: #890254)
>...

Thanks a lot for fixing this bug for unstable.

It is still present in stretch, could you also fix it there?
Alternatively, I can fix it for stretch if you don't object.

Thanks
Adrian

-- 

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

Bug#892766: CVE-2017-15422

[Moritz Muehlenhoff]

Source: icu
Severity: grave
Tags: security

Hi Laszlo,
https://chromereleases.googleblog.com/2017/12/stable-channel-update-for-desktop.html
refers to a ICU vulnerability, but there's little information what fixes/fixed 
that.

Could you reach out to upstream whether they've been in touch with them so that
we can pinpoint this a specific task/commit?

Cheers,
Moritz

Bug#874220: stretch update for openni2

[Adrian Bunk]

On Mon, Sep 11, 2017 at 09:18:05PM +, Debian Bug Tracking System wrote:
>...
>  openni2 (2.2.0.33+dfsg-10) unstable; urgency=medium
>  .
>* Add patch for arm.
>  Thanks to Adrian Bunk (Closes: #874220)
>...

Thanks a lot for fixing this bug for unstable.

It is still present in stretch, could you also fix it there?
Alternatively, I can fix it for stretch if you don't object.

Thanks
Adrian

-- 

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

Bug#822603: Remove network-config from Debian?

[Jeremy Bicha]

I am filing a removal bug now. Please reply immediately if you object.

Thanks,
Jeremy Bicha

On Tue, Jan 16, 2018 at 10:16 PM, Jeremy Bicha  wrote:
> On Sun, Dec 31, 2017 at 7:21 PM, Jeremy Bicha  wrote:
>> Hi,
>>
>> network-config was removed from Debian Testing because it depends on
>> gksu [1]. The Debian GNOME team would like to remove gksu from Debian
>> Unstable too but we need to fix or remove the reverse depends first.
>>
>> Can I file a Debian removal bug for network-config now?
>>
>> [1] https://bugs.debian.org/822603
>>
>> Thanks,
>> Jeremy Bicha
>
> network-config is now the last thing in Debian depending on gksu. The
> Debian GNOME team wants to remove gksu since it is deprecated and no
> longer maintained. Because network-config has already been removed
> from Debian Testing since July for this issue and there has been no
> response from the Debian maintainer for this package, I intend to
> request that network-config be removed from Debian soon. It can be
> reintroduced to Debian if this bug is fixed.
>
> Thanks
> Jeremy Bicha

Processed: reopening 886853, reassign 886853 to mariadb-plugin-rocksdb ...

[Debian Bug Tracking System]

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

> reopen 886853
Bug #886853 {Done: László Böszörményi (GCS) } 
[mariadb-plugin-rocksdb,rocksdb-tools] mariadb-plugin-rocksdb,rocksdb-tools: 
both ship /usr/bin/sst_dump
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions 5.10.4-2.
> reassign 886853 mariadb-plugin-rocksdb 10.3.0-0+exp2
Bug #886853 [mariadb-plugin-rocksdb,rocksdb-tools] 
mariadb-plugin-rocksdb,rocksdb-tools: both ship /usr/bin/sst_dump
Bug reassigned from package 'mariadb-plugin-rocksdb,rocksdb-tools' to 
'mariadb-plugin-rocksdb'.
No longer marked as found in versions mariadb-10.3/10.3.0-0+exp2 and 
rocksdb/5.9.2-1.
Ignoring request to alter fixed versions of bug #886853 to the same values 
previously set
Bug #886853 [mariadb-plugin-rocksdb] mariadb-plugin-rocksdb,rocksdb-tools: both 
ship /usr/bin/sst_dump
Marked as found in versions mariadb-10.3/10.3.0-0+exp2.
> retitle 886853 mariadb-plugin-rocksdb: use sst_dump from rocksdb-tools
Bug #886853 [mariadb-plugin-rocksdb] mariadb-plugin-rocksdb,rocksdb-tools: both 
ship /usr/bin/sst_dump
Changed Bug title to 'mariadb-plugin-rocksdb: use sst_dump from rocksdb-tools' 
from 'mariadb-plugin-rocksdb,rocksdb-tools: both ship /usr/bin/sst_dump'.
> thanks
Stopping processing here.

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

Processed: tagging 892326

[Debian Bug Tracking System]

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

> tags 892326 + upstream pending
Bug #892326 [src:herisvm] herisvm FTBFS with Ruby 2.5
Added tag(s) pending and upstream.
> thanks
Stopping processing here.

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

Processed: tagging 892326

[Debian Bug Tracking System]

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

> tags 892326 + fixed-upstream
Bug #892326 [src:herisvm] herisvm FTBFS with Ruby 2.5
Added tag(s) fixed-upstream.
> thanks
Stopping processing here.

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

Bug#880047: stretch update for postgrey

[Adrian Bunk]

On Sat, Nov 25, 2017 at 10:36:10AM +, Debian Bug Tracking System wrote:
>...
>  postgrey (1.36-5) unstable; urgency=medium
>  .
>* debian/postgrey.init: create /var/run/postgrey if it
>  does not exist, patch provided by Laurent Bigonville .
>  (Closes: 756813, 880047)
>...

Thanks a lot for fixing this bug for unstable.

It is still present in stretch, could you also fix it there?
Alternatively, I can fix it for stretch if you don't object.

An open question would be whether #867201 should then also be fixed
in stretch, I've added Julien to the Cc.

cu
Adrian

-- 

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

Bug#858819: marked as done (Typo causes error with Trac 1.2)

[Debian Bug Tracking System]

Your message dated Mon, 12 Mar 2018 17:49:10 +
with message-id 
and subject line Bug#858819: fixed in email2trac 2.10.0-2
has caused the Debian Bug report #858819,
regarding Typo causes error with Trac 1.2
to be marked as done.

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

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


-- 
858819: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=858819
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: trac-email2trac
Version: 2.10.0-1
Severity: normal
Tags: upstream, patch

Hi,

the email2trac program contains this line:

if version in ['0.12', '0.13', '1.0', '1.1', '1,2' ]:

Note the comma in '1,2', which should be a dot.

As it is, it complains that Trac 1.2 is unsupported; replacing the comma
with a dot fixes the problem.

Andras

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

Kernel: Linux 4.1.37-vs2.3.8.5.2-caeeng (SMP w/8 CPU cores)
Locale: LANG=C, LC_CTYPE=hu_HU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: unable to detect

Versions of packages trac-email2trac depends on:
ii  python  2.7.13-1
pn  python:any  
ii  trac1.2+dfsg-1

trac-email2trac recommends no packages.

Versions of packages trac-email2trac suggests:
pn  getmail4  

-- 
 Well, the source can't be modified because it's encrypted using C++.
--- End Message ---
--- Begin Message ---
Source: email2trac
Source-Version: 2.10.0-2

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

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

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

Debian distribution maintenance software
pp.
Adrian Bunk  (supplier of updated email2trac 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: Mon, 12 Mar 2018 19:20:11 +0200
Source: email2trac
Binary: trac-email2trac
Architecture: source
Version: 2.10.0-2
Distribution: unstable
Urgency: high
Maintainer: Debian QA Group 
Changed-By: Adrian Bunk 
Description:
 trac-email2trac - Creates and amends Trac tickets from e-mail
Closes: 858819
Changes:
 email2trac (2.10.0-2) unstable; urgency=high
 .
   * QA upload.
   * Set maintainer to Debian QA Group. (see #891353)
   * Add upstream fix for Trac 1.2. (Closes: #858819)
   * Install the upstream NOTICE.
Checksums-Sha1:
 f617a47568dbbef578d94147e7c2e920cfaf3df4 1934 email2trac_2.10.0-2.dsc
 9eb7dec19ba2a9fec0a925b3bfbe312ca3af69e9 3796 email2trac_2.10.0-2.debian.tar.xz
Checksums-Sha256:
 4732bd862852f569983c40dc8887af3b3237c68e3e9229bd62b43e9bb3052b64 1934 
email2trac_2.10.0-2.dsc
 0e432ff9260ea18960900caff1d1537da1aab4f5ab9e96bc40cfdfca04f0975b 3796 
email2trac_2.10.0-2.debian.tar.xz
Files:
 046826a594dcf727a010c56d4eaad6d1 1934 web optional email2trac_2.10.0-2.dsc
 cae330b1b8e46bd8d10ce2b44feb973f 3796 web optional 
email2trac_2.10.0-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAlqmuVcACgkQiNJCh6LY
mLH/ixAApI2Odbuoank2Pzs7/U61qj/+4YDWYfFog7XxXXe8NM5Cv1QUrZflCgDV
2ygA2rbaKrOdJPQT5CADi1CQZdZdhGBG5saCrZ0Dir5+gYA7cgFu/v+O6jdIH/mm
MF8Ey/C4SeOkdFbiLOmSs2UIW2Fba+iFRlrZNsRx5NYF70oFVuwvJX8IUfndOx0O
KcKwVFEPxS16lJJtUpEiSA7GF5boAgFue/SZ7tqYcIsR5wsXNz2LaeH8Z/hXKDsT
xv8WWG9zSidXvd1Y1Emj1YosbTYk96undmndeHVL41q2vrlQkwxmIOYTitchYqIl
so/xwwguOAB8qrw0Ic35BzvqhVaaBlrAOwsYDuGFMUn1stXXZh+wTO06qDwRPccP
SpTjrY6VVqeZHLlBfE3kULsDrOMSMSbrNK3AiaygPd4awJDUuUaJGE2yhQnCa+Ov
UefcDAGud9oov2NbnpubHrFxfief4soaYdZ1MGJwrZUc3fdCjl7Pc9hmgtjGnaMj
zIb6iS00scdL7R9A3C4ndKHSGCc9bdWZ8bMhp1ZDBP5PDetbwtS9AvXMjSWT9xOL
+1VI1zietyI6XAGzDYKFoRUKcNyJrMlpQFZUNYxvXfrGhWzpBK99kb4G2sgxRjEU
2l8tt4dqIEzZGPNUDLG2G7Skeh3f6gj8ZHstbkJ7aUCr4GHohw8=
=z1aa
-END PGP SIGNATURE End Message ---

Bug#873160: python-pymad: pymad in stretch decodes to noise

[Adrian Bunk]

On Wed, Aug 30, 2017 at 11:19:22AM +1000, Jamie Wilkinson wrote:
> Bug 873673 contains the request to the release team.

Did you make any progress preparing a 0.9-1+deb9u1 as advised by the 
release team?

Thanks
Adrian

-- 

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

Bug#874213: marked as done (mercurial: please Build-Depend on rename)

[Debian Bug Tracking System]

Your message dated Mon, 12 Mar 2018 18:00:53 +0200
with message-id <20180312160052.GG20833@localhost>
and subject line Already fixed since 4.4.1-1
has caused the Debian Bug report #874213,
regarding mercurial: please Build-Depend on rename
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.)


-- 
874213: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874213
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mercurial
Version: 4.3.1-3
Severity: serious
Justification: FTBFS with impending change
User: debian-p...@lists.debian.org
Usertags: rename-deprecation

As announced last year[1] and as advised by deprecation messages,
rename(1) will be removed from the perl package after the stretch
release, and this is now imminent.

Your package FTBFS with perl from experimental as a result. Please
add a Build-Depends: rename to your package, and all will be well
again:

Skipped test-debian-packages.t: missing feature: debian packaging tools
# Ran 564 tests, 57 skipped, 0 failed.
# Cleaning up HGTMP /tmp/hgtests.1d5pdA 
make[2]: Leaving directory '/<>'
rename 's/\.deb-backup$//' /<>/tests/*
/bin/sh: 1: rename: not found
debian/rules:46: recipe for target 'override_dh_auto_test' failed

Let me know if you would prefer an NMU to get this trivial change made. 

Cheers,
Dominic.

[1] 
--- End Message ---
--- Begin Message ---
Version: 4.4.1-1

mercurial 4.4.1-1 already added the build dependency on rename.

cu
Adrian

-- 

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

Bug#892757: openstack-trove FTBFS: FAIL: common.test_context.TestTroveContext.test_create_with_bogus

[Adrian Bunk]

Source: openstack-trove
Version: 1:8.0.0-4
Severity: serious

Some recent change in unstable makes openstack-trove FTBFS:

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

...
==
FAIL: common.test_context.TestTroveContext.test_create_with_bogus
common.test_context.TestTroveContext.test_create_with_bogus
--
_StringException: Traceback (most recent call last):
  File 
"/build/1st/openstack-trove-8.0.0/trove/tests/unittests/common/test_context.py",
 line 81, in test_create_with_bogus
'key': 'blah_blah'})
  File "/usr/lib/python2.7/dist-packages/mock/mock.py", line 937, in 
assert_called_with
six.raise_from(AssertionError(_error_message(cause)), cause)
  File "/usr/lib/python2.7/dist-packages/six.py", line 737, in raise_from
raise value
AssertionError: Expected call: warning('Argument being removed before 
instantiating TroveContext object - %(key)s = %(value)s', {'key': 'blah_blah', 
'value': 'blah blah'})
Actual call: warning(u'Argument being removed before instantiating TroveContext 
object - %(key)s = %(value)s', {'value': 'abc', 'key': 'tenant'})


--
Ran 1635 tests in 1846.323s

FAILED (failures=1, skipped=1)
make[1]: *** [debian/rules:57: override_dh_auto_test] Error 1

Processed: found 892743 in 3.1.2-1

[Debian Bug Tracking System]

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

> found 892743 3.1.2-1
Bug #892743 [mercurial] permissions bypass on http server
Marked as found in versions mercurial/3.1.2-1.
> thanks
Stopping processing here.

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

Bug#892133: [Pkg-javascript-devel] Bug#892133: Bug#892133: node-rollup: does not work after a no-change rebuild (the one in the archive is not suitable for main?)

[Gianfranco Costamagna]

Hello,


>Can you check again with node-rollup-plugin-commonjs 8.3.0-2?

nack, I did the same no change rebuilds and it failed

root@Unimatrix04-Artful:/node-rollup-0.50.0# dpkg -l |grep node
ii  node-acorn   5.4.1+ds1-1   
all  ECMAScript parser for Node.js
ii  node-acorn-dynamic-import3.0.0-1   
all  Support dynamic imports in acorn
ii  node-acorn-jsx   4.1.0-1   
all  JSX parser based on node-acorn
ii  node-acorn-object-spread 5.1.2-1   
all  Plugin for object spread in acorn for Node.js
ii  node-amdefine0.1.0-1   
all  Asynchronous Module Definition (AMD) for Node.js
ii  node-ansi-escapes3.0.0-1   
all  ANSI escape codes for manipulating the terminal
ii  node-ansi-styles 3.2.0-1   
all  ANSI escape codes for styling strings in the terminal with Node.js
ii  node-arr-diff4.0.0-1   
all  Returns an array with only the unique values from the first array
ii  node-arr-flatten 1.1.0-1   
all  Recursively flatten an array or arrays
ii  node-arr-union   3.1.0-1   
all  Combines list of arrays, returning single array with unique values
ii  node-array-unique0.3.2-1   
all  Return an array free of duplicate values
ii  node-balanced-match  0.4.2-1   
all  Match balanced character pairs in Node.js
ii  node-base0.11.1-1  
all  foundation for creating modular, unit testable node.js application
ii  node-brace-expansion 1.1.8-1   
all  Brace expansion as known from sh/bash for Node.js
ii  node-braces  2.0.2-2   
all  Fast, comprehensive, bash-like brace expansion implemented in JS
ii  node-browser-resolve 1.11.2-1  
all  node.js resolve algorithm with browser mapping support
ii  node-buble   0.19.3-1  
all  Fast ES2015 compiler for Node.js
ii  node-builtin-modules 1.1.1-1   
all  List of the Node.js builtin modules
ii  node-cache-base  0.8.4-1   
all  Basic object cache for node.js/javascript projects
ii  node-chalk   2.3.0-1   
all  Terminal string styling for Node.js
ii  node-class-utils 0.3.5-1   
all  Utils for working with JavaScript classes and prototype methods
ii  node-collection-visit1.0.0-1   
all  Visit a method over items in object, or map visit over the objects
ii  node-color-convert   1.9.0-2build2 
all  Plain color conversion functions
ii  node-color-name  1.1.3-1   
all  list of color names and its values
ii  node-component-emitter   1.2.1-1   
all  Event emitter for Node.js
ii  node-concat-map  0.0.1-1   
all  concatenative mapdashery for Node.js
ii  node-copy-descriptor 0.1.1-1   
all  Copy a descriptor from one object to another
ii  node-css 2.1.0-2   
all  JavaScript CSS parser and stringifier - Node.js module
ii  node-date-time   2.1.0-1   
all  Pretty datetime like 2014-01-09 06:46:01
ii  node-debug   3.1.0-1   
all  small debugging utility for Node.js
ii  node-define-property 1.0.0-1   
all  Define property on an object
ii  node-escape-string-regexp1.0.5-1   
all  Escape RegExp special characters in Node.js
ii  node-estree-walker   0.5.1-1   
all  traverse an ESTree-compliant AST in Node.js
ii  node-expand-brackets 2.1.4-1   
all  Expand POSIX bracket expressions
ii  node-extend-shallow  3.0.1-1   
all  extend an 

Processed: affects 892462

[Debian Bug Tracking System]

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

> affects 892462 src:pyresample
Bug #892462 {Done: Bas Couwenberg } [src:proj] PROJ 5.0.0 
causes regression in python-mpop
Added indication that 892462 affects src:pyresample
> thanks
Stopping processing here.

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

Processed: python-mpop FTBFS and Debci failure: FAIL: test_boundaries_to_extent (mpop.tests.test_satin_helpers.TestSatinHelpers)

[Debian Bug Tracking System]

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

> retitle 892462 PROJ 5.0.0 causes regression in python-mpop
Bug #892462 [src:python-mpop] python-mpop FTBFS and Debci failure: FAIL: 
test_boundaries_to_extent (mpop.tests.test_satin_helpers.TestSatinHelpers)
Changed Bug title to 'PROJ 5.0.0 causes regression in python-mpop' from 
'python-mpop FTBFS and Debci failure: FAIL: test_boundaries_to_extent 
(mpop.tests.test_satin_helpers.TestSatinHelpers)'.
> reassign 892462 src:proj
Bug #892462 [src:python-mpop] PROJ 5.0.0 causes regression in python-mpop
Bug reassigned from package 'src:python-mpop' to 'src:proj'.
No longer marked as found in versions python-mpop/1.5.0-2.
Ignoring request to alter fixed versions of bug #892462 to the same values 
previously set
> affects 892462 src:python-mpop
Bug #892462 [src:proj] PROJ 5.0.0 causes regression in python-mpop
Added indication that 892462 affects src:python-mpop
> found 892462 proj/5.0.0-1
Bug #892462 [src:proj] PROJ 5.0.0 causes regression in python-mpop
Marked as found in versions proj/5.0.0-1.
> fixed 892462 proj/5.0.0-4~exp1
Bug #892462 [src:proj] PROJ 5.0.0 causes regression in python-mpop
The source proj and version 5.0.0-4~exp1 do not appear to match any binary 
packages
Marked as fixed in versions proj/5.0.0-4~exp1.
> thanks
Stopping processing here.

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

Bug#892462: marked as done (PROJ 5.0.0 causes regression in python-mpop)

[Debian Bug Tracking System]

Your message dated Mon, 12 Mar 2018 15:34:44 +0100
with message-id <3fd0e8a8c4fe85b287ad0626dc808...@xs4all.nl>
and subject line python-mpop FTBFS and Debci failure: FAIL: 
test_boundaries_to_extent (mpop.tests.test_satin_helpers.TestSatinHelpers)
has caused the Debian Bug report #892462,
regarding PROJ 5.0.0 causes regression in python-mpop
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.)


-- 
892462: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892462
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-mpop
Version: 1.5.0-2
Severity: serious

https://ci.debian.net/packages/p/python-mpop/unstable/amd64/
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/python-mpop.html

...
==
FAIL: test_boundaries_to_extent (mpop.tests.test_satin_helpers.TestSatinHelpers)
Test conversion of area boundaries to area extent.
--
Traceback (most recent call last):
  File "/build/1st/python-mpop-1.5.0/mpop/tests/test_satin_helpers.py", line 
194, in test_boundaries_to_extent
correct_values_afgh[i], 2)
AssertionError: 0.0 != 3053894.9120028536 within 2 places

--
Ran 69 tests in 4.178s

FAILED (failures=1, skipped=1)
Test failed: 
error: Test failed: 
make[1]: *** [debian/rules:22: override_dh_auto_test] Error 1
--- End Message ---
--- Begin Message ---

retitle 892462 PROJ 5.0.0 causes regression in python-mpop
reassign 892462 src:proj
affects 892462 src:python-mpop
found 892462 proj/5.0.0-1
fixed 892462 proj/5.0.0-4~exp1
thanks

As discussed in the upstream issue, this is a regression in PROJ 5.0.0.

This issue is fixed the 
Make-sure-that-transient-errors-are-returned-correctly.patch included in 
proj (5.0.0-4~exp1).


Kind Regards,

Bas--- End Message ---

Processed: tagging 892500

[Debian Bug Tracking System]

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

> tags 892500 + confirmed
Bug #892500 [mitmproxy] mitmproxy: Doesn't start with dependency versions 
currently available in Debian
Added tag(s) confirmed.
> thanks
Stopping processing here.

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

Bug#892091: [Pkg-ayatana-devel] Bug#892091: ayatana-indicator-power: FTBFS randomly - gschemas.compiled generated twice

[Mike Gabriel]

Hi James,

On  Mo 12 Mär 2018 15:08:11 CET, James Cowgill wrote:


Hi,

On 12/03/18 13:47, Mike Gabriel wrote:

On  Mo 12 Mär 2018 14:29:18 CET, James Cowgill wrote:

On 11/03/18 15:40, Mike Gabriel wrote:

On  Mo 05 Mär 2018 12:31:34 CET, James Cowgill wrote:

From cmake-commands(7) - add_custom_command:
"Do not list the output in more than one independent target that may
build in parallel or the two instances of the rule may conflict
(instead
use the add_custom_target() command to drive the command and make the
other targets depend on that one)."

There are three independent targets here which use gschemas.compiled
(the three tests).

I found this blog which tries to explain it (number 4):
https://samthursfield.wordpress.com/2015/11/21/cmake-dependencies-between-targets-and-files-and-custom-commands/



James


Thanks for your research on this.

Would this feel like a valid fix?

```
diff --git a/tests/CMakeLists.txt b/tests/CMakeLists.txt
index 2c45057..714fa6c 100644
--- a/tests/CMakeLists.txt
+++ b/tests/CMakeLists.txt
@@ -32,6 +32,14 @@ add_custom_command (OUTPUT gschemas.compiled
 COMMAND cp -f ${CMAKE_BINARY_DIR}/data/*gschema.xml
${SCHEMA_DIR}
 COMMAND ${COMPILE_SCHEMA_EXECUTABLE} ${SCHEMA_DIR})

+add_custom_target(
+    test-notify-gschemas ALL DEPENDS gschemas.compiled
+)
+
+add_custom_target(
+    test-device-gschemas ALL DEPENDS gschemas.compiled
+)


I don't think this will work because these two targets might be built in
parallel and we end up with the same problem as before. I think you want
a single custom target which all the tests depend on.

James


Hmm, but what you say above would contradict the howto provided under
(4.) at this URL [1] (the one you quoted earlier).

I think, I exactly immitated what Sam Thursfield wrote on his blog.
Don't you think?


I think the code directly under the section 4 heading is a failing test
case and an example of what you should _not_ do.

James


Then this would be the next approach:

```
commit 891b1549a3d20db69e4335c1a74bcba1c84c3bb3
Author: Mike Gabriel 
Date:   Sun Mar 11 21:32:24 2018 +0100

tests/CMakeLists.txt: Prohibit gschemas.compiled to be generated  
multiple times.


 Spotted by James Cogwill, see https://bugs.debian.org/892091.

diff --git a/tests/CMakeLists.txt b/tests/CMakeLists.txt
index 651ddf4..bf53ee3 100644
--- a/tests/CMakeLists.txt
+++ b/tests/CMakeLists.txt
@@ -32,6 +32,10 @@ add_custom_command (OUTPUT gschemas.compiled
 COMMAND cp -f  
${CMAKE_BINARY_DIR}/data/*gschema.xml ${SCHEMA_DIR}

 COMMAND ${COMPILE_SCHEMA_EXECUTABLE} ${SCHEMA_DIR})

+add_custom_target(
+gschemas-compiled ALL DEPENDS gschemas.compiled
+)
+
 # look for headers in our src dir, and also in the directories where  
we autogenerate files...

 include_directories (${CMAKE_SOURCE_DIR}/src)
 include_directories (${CMAKE_BINARY_DIR}/src)
@@ -42,9 +46,9 @@ include_directories (${CMAKE_CURRENT_BINARY_DIR})

 function(add_test_by_name name)
   set (TEST_NAME ${name})
-  add_executable (${TEST_NAME} ${TEST_NAME}.cc gschemas.compiled)
+  add_executable (${TEST_NAME} ${TEST_NAME}.cc)
   add_test (${TEST_NAME} ${TEST_NAME})
-  add_dependencies (${TEST_NAME} ayatanaindicatorpowerservice)
+  add_dependencies (${TEST_NAME} ayatanaindicatorpowerservice  
gschemas-compiled)
   target_link_libraries (${TEST_NAME} ayatanaindicatorpowerservice  
gtest ${DBUSTEST_LIBRARIES} ${SERVICE_DEPS_LIBRARIES} ${GTEST_LIBS}  
${URLDISPATCHER_LIBRARIES})

 endfunction()
 add_test_by_name(test-notify)
```

(and when re-reading the blog post, I realized that the example was  
indeed the bad test case.)


Mike
--

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

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



pgpM_hVgooaXF.pgp
Description: Digitale PGP-Signatur

Bug#892747: python-tempest-lib FTBFS: ImportError: cannot import name mockpatch

[Adrian Bunk]

Source: python-tempest-lib
Version: 0.14.0-3
Severity: serious

Some recent change in unstable makes python-tempest-lib FTBFS:

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

...
==
FAIL: 
unittest2.loader._FailedTest.tempest_lib.tests.services.compute.test_agents_client
unittest2.loader._FailedTest.tempest_lib.tests.services.compute.test_agents_client
--
_StringException: Traceback (most recent call last):
ImportError: Failed to import test module: 
tempest_lib.tests.services.compute.test_agents_client
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/unittest2/loader.py", line 456, in 
_find_test_path
module = self._get_module_from_name(name)
  File "/usr/lib/python2.7/dist-packages/unittest2/loader.py", line 395, in 
_get_module_from_name
__import__(name)
  File "tempest_lib/tests/services/compute/test_agents_client.py", line 17, in 

from tempest_lib.tests.services.compute import base
  File "tempest_lib/tests/services/compute/base.py", line 17, in 
from oslotest import mockpatch
ImportError: cannot import name mockpatch


==
FAIL: 
unittest2.loader._FailedTest.tempest_lib.tests.services.compute.test_aggregates_client
unittest2.loader._FailedTest.tempest_lib.tests.services.compute.test_aggregates_client
--
_StringException: Traceback (most recent call last):
ImportError: Failed to import test module: 
tempest_lib.tests.services.compute.test_aggregates_client
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/unittest2/loader.py", line 456, in 
_find_test_path
module = self._get_module_from_name(name)
  File "/usr/lib/python2.7/dist-packages/unittest2/loader.py", line 395, in 
_get_module_from_name
__import__(name)
  File "tempest_lib/tests/services/compute/test_aggregates_client.py", line 17, 
in 
from tempest_lib.tests.services.compute import base
  File "tempest_lib/tests/services/compute/base.py", line 17, in 
from oslotest import mockpatch
ImportError: cannot import name mockpatch


==
FAIL: 
unittest2.loader._FailedTest.tempest_lib.tests.services.compute.test_availability_zone_client
unittest2.loader._FailedTest.tempest_lib.tests.services.compute.test_availability_zone_client
--
_StringException: Traceback (most recent call last):
ImportError: Failed to import test module: 
tempest_lib.tests.services.compute.test_availability_zone_client
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/unittest2/loader.py", line 456, in 
_find_test_path
module = self._get_module_from_name(name)
  File "/usr/lib/python2.7/dist-packages/unittest2/loader.py", line 395, in 
_get_module_from_name
__import__(name)
  File "tempest_lib/tests/services/compute/test_availability_zone_client.py", 
line 17, in 
from tempest_lib.tests.services.compute import base
  File "tempest_lib/tests/services/compute/base.py", line 17, in 
from oslotest import mockpatch
ImportError: cannot import name mockpatch
...
==
FAIL: unittest2.loader._FailedTest.tempest_lib.tests.test_rest_client
unittest2.loader._FailedTest.tempest_lib.tests.test_rest_client
--
_StringException: Traceback (most recent call last):
ImportError: Failed to import test module: tempest_lib.tests.test_rest_client
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/unittest2/loader.py", line 456, in 
_find_test_path
module = self._get_module_from_name(name)
  File "/usr/lib/python2.7/dist-packages/unittest2/loader.py", line 395, in 
_get_module_from_name
__import__(name)
  File "tempest_lib/tests/test_rest_client.py", line 20, in 
from oslotest import mockpatch
ImportError: cannot import name mockpatch


--
Ran 125 tests in 16.535s

FAILED (failures=37, skipped=2)
make[1]: *** [debian/rules:35: override_dh_auto_test] Error 1

Bug#892091: [Pkg-ayatana-devel] Bug#892091: ayatana-indicator-power: FTBFS randomly - gschemas.compiled generated twice

[James Cowgill]

Hi,

On 12/03/18 13:47, Mike Gabriel wrote:
> On  Mo 12 Mär 2018 14:29:18 CET, James Cowgill wrote:
>> On 11/03/18 15:40, Mike Gabriel wrote:
>>> On  Mo 05 Mär 2018 12:31:34 CET, James Cowgill wrote:
 From cmake-commands(7) - add_custom_command:
 "Do not list the output in more than one independent target that may
 build in parallel or the two instances of the rule may conflict
 (instead
 use the add_custom_target() command to drive the command and make the
 other targets depend on that one)."

 There are three independent targets here which use gschemas.compiled
 (the three tests).

 I found this blog which tries to explain it (number 4):
 https://samthursfield.wordpress.com/2015/11/21/cmake-dependencies-between-targets-and-files-and-custom-commands/



 James
>>>
>>> Thanks for your research on this.
>>>
>>> Would this feel like a valid fix?
>>>
>>> ```
>>> diff --git a/tests/CMakeLists.txt b/tests/CMakeLists.txt
>>> index 2c45057..714fa6c 100644
>>> --- a/tests/CMakeLists.txt
>>> +++ b/tests/CMakeLists.txt
>>> @@ -32,6 +32,14 @@ add_custom_command (OUTPUT gschemas.compiled
>>>  COMMAND cp -f ${CMAKE_BINARY_DIR}/data/*gschema.xml
>>> ${SCHEMA_DIR}
>>>  COMMAND ${COMPILE_SCHEMA_EXECUTABLE} ${SCHEMA_DIR})
>>>
>>> +add_custom_target(
>>> +    test-notify-gschemas ALL DEPENDS gschemas.compiled
>>> +)
>>> +
>>> +add_custom_target(
>>> +    test-device-gschemas ALL DEPENDS gschemas.compiled
>>> +)
>>
>> I don't think this will work because these two targets might be built in
>> parallel and we end up with the same problem as before. I think you want
>> a single custom target which all the tests depend on.
>>
>> James
> 
> Hmm, but what you say above would contradict the howto provided under
> (4.) at this URL [1] (the one you quoted earlier).
> 
> I think, I exactly immitated what Sam Thursfield wrote on his blog.
> Don't you think?

I think the code directly under the section 4 heading is a failing test
case and an example of what you should _not_ do.

James



signature.asc
Description: OpenPGP digital signature

Bug#892746: python-zake FTBFS: FAIL: zake.tests.test_client.TestClient.test_child_watch_no_create

[Adrian Bunk]

Source: python-zake
Version: 0.1.6-1
Severity: serious
Tags: buster sid

Some recent change in unstable makes python-zake FTBFS:

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

...
   debian/rules override_dh_auto_test
make[1]: Entering directory '/build/1st/python-zake-0.1.6'
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)
set -ex && for pyvers in 2.7; do \
PYTHON=python$pyvers nosetests ; \
done
+ PYTHON=python2.7 nosetests
...F
==
FAIL: zake.tests.test_client.TestClient.test_child_watch_no_create
--
_StringException: Traceback (most recent call last):
  File "/build/1st/python-zake-0.1.6/zake/tests/test_client.py", line 462, in 
test_child_watch_no_create
self.client, "/b", cb)
  File "/usr/lib/python2.7/dist-packages/testtools/testcase.py", line 485, in 
assertRaises
self.assertThat(our_callable, matcher)
  File "/usr/lib/python2.7/dist-packages/testtools/testcase.py", line 498, in 
assertThat
raise mismatch_error
testtools.matchers._impl.MismatchError:  returned 



--
Ran 44 tests in 5.276s

FAILED (failures=1)
make[1]: *** [debian/rules:27: override_dh_auto_test] Error 1

Bug#892745: python-os-testr FTBFS: test failure

[Adrian Bunk]

Source: python-os-testr
Version: 1.0.0-2
Severity: serious

Some recent change in unstable makes python-os-testr FTBFS:

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

...
==
FAIL: os_testr.tests.test_return_codes.TestReturnCodes.test_list
os_testr.tests.test_return_codes.TestReturnCodes.test_list
--
_StringException: Traceback (most recent call last):
  File "os_testr/tests/test_return_codes.py", line 104, in test_list
self.assertRunExit('ostestr --list', 0)
  File "os_testr/tests/test_return_codes.py", line 65, in assertRunExit
"Stdout: %s; Stderr: %s" % (out, err))
  File "/usr/lib/python2.7/dist-packages/testtools/testcase.py", line 411, in 
assertEqual
self.assertThat(observed, matcher, message)
  File "/usr/lib/python2.7/dist-packages/testtools/testcase.py", line 498, in 
assertThat
raise mismatch_error
testtools.matchers._impl.MismatchError: 1 != 0: Stdout: ; Stderr: Traceback 
(most recent call last):
  File "/build/1st/python-os-testr-1.0.0/debian/bin/ostestr", line 5, in 

from os_testr.os_testr import main
ImportError: No module named os_testr


==
FAIL: os_testr.tests.test_return_codes.TestReturnCodes.test_default_passing
os_testr.tests.test_return_codes.TestReturnCodes.test_default_passing
--
_StringException: Traceback (most recent call last):
  File "os_testr/tests/test_return_codes.py", line 72, in test_default_passing
self.assertRunExit('ostestr --regex passing', 0)
  File "os_testr/tests/test_return_codes.py", line 65, in assertRunExit
"Stdout: %s; Stderr: %s" % (out, err))
  File "/usr/lib/python2.7/dist-packages/testtools/testcase.py", line 411, in 
assertEqual
self.assertThat(observed, matcher, message)
  File "/usr/lib/python2.7/dist-packages/testtools/testcase.py", line 498, in 
assertThat
raise mismatch_error
testtools.matchers._impl.MismatchError: 1 != 0: Stdout: ; Stderr: Traceback 
(most recent call last):
  File "/build/1st/python-os-testr-1.0.0/debian/bin/ostestr", line 5, in 

from os_testr.os_testr import main
ImportError: No module named os_testr


==
FAIL: 
os_testr.tests.test_return_codes.TestReturnCodes.test_default_serial_passing
os_testr.tests.test_return_codes.TestReturnCodes.test_default_serial_passing
--
_StringException: Traceback (most recent call last):
  File "os_testr/tests/test_return_codes.py", line 84, in 
test_default_serial_passing
self.assertRunExit('ostestr --serial --regex passing', 0)
  File "os_testr/tests/test_return_codes.py", line 65, in assertRunExit
"Stdout: %s; Stderr: %s" % (out, err))
  File "/usr/lib/python2.7/dist-packages/testtools/testcase.py", line 411, in 
assertEqual
self.assertThat(observed, matcher, message)
  File "/usr/lib/python2.7/dist-packages/testtools/testcase.py", line 498, in 
assertThat
raise mismatch_error
testtools.matchers._impl.MismatchError: 1 != 0: Stdout: ; Stderr: Traceback 
(most recent call last):
  File "/build/1st/python-os-testr-1.0.0/debian/bin/ostestr", line 5, in 

from os_testr.os_testr import main
ImportError: No module named os_testr


==
FAIL: 
os_testr.tests.test_return_codes.TestReturnCodes.test_testr_no_pretty_passing
os_testr.tests.test_return_codes.TestReturnCodes.test_testr_no_pretty_passing
--
_StringException: Traceback (most recent call last):
  File "os_testr/tests/test_return_codes.py", line 98, in 
test_testr_no_pretty_passing
self.assertRunExit('ostestr --no-pretty --regex passing', 0)
  File "os_testr/tests/test_return_codes.py", line 65, in assertRunExit
"Stdout: %s; Stderr: %s" % (out, err))
  File "/usr/lib/python2.7/dist-packages/testtools/testcase.py", line 411, in 
assertEqual
self.assertThat(observed, matcher, message)
  File "/usr/lib/python2.7/dist-packages/testtools/testcase.py", line 498, in 
assertThat
raise mismatch_error
testtools.matchers._impl.MismatchError: 1 != 0: Stdout: ; Stderr: Traceback 
(most recent call last):
  File "/build/1st/python-os-testr-1.0.0/debian/bin/ostestr", line 5, in 

from os_testr.os_testr import main
ImportError: No module named os_testr


==
FAIL: 
os_testr.tests.test_return_codes.TestReturnCodes.test_default_passing_no_slowest
os_testr.tests.test_return_codes.TestReturnCodes.test_default_passing_no_slowest

Bug#892741: llvmlite: FTBFS on mips64el - testsuite segfaults

[Daniel Stender]

On 03/12/2018 02:03 PM, James Cowgill wrote:

Source: llvmlite
Version: 0.22.0-1
Severity: serious
Tags: sid buster

Hi,

llvmlite FTBFS on mips64el with this segmentation fault:

debian/rules override_dh_auto_test
make[1]: Entering directory '/<>'
PYBUILD_SYSTEM=custom PYBUILD_TEST_ARGS="{interpreter} -m unittest discover -v" 
dh_auto_test
I: pybuild base:184: python2.7 -m unittest discover -v
test_function_cfg_on_llvm_value (llvmlite.tests.test_binding.TestAnalysis) ... 
ok
test_get_function_cfg_on_ir (llvmlite.tests.test_binding.TestAnalysis) ... ok
test_linux (llvmlite.tests.test_binding.TestDependencies) ... skipped 
'Distribution-specific test'
test_bad_library (llvmlite.tests.test_binding.TestDylib) ... ok
test_libm (llvmlite.tests.test_binding.TestDylib) ... ok
test_close (llvmlite.tests.test_binding.TestFunctionPassManager) ... ok
test_initfini (llvmlite.tests.test_binding.TestFunctionPassManager) ... ok
test_run (llvmlite.tests.test_binding.TestFunctionPassManager) ... ok
test_add_module (llvmlite.tests.test_binding.TestGlobalConstructors) ... ok
test_add_module_lifetime (llvmlite.tests.test_binding.TestGlobalConstructors) 
... ok
test_add_module_lifetime2 (llvmlite.tests.test_binding.TestGlobalConstructors) 
... ok
test_close (llvmlite.tests.test_binding.TestGlobalConstructors) ... ok
test_emit_assembly (llvmlite.tests.test_binding.TestGlobalConstructors)
Test TargetMachineRef.emit_assembly() ... ok
test_emit_object (llvmlite.tests.test_binding.TestGlobalConstructors)
Test TargetMachineRef.emit_object() ... ok
test_global_ctors_dtors (llvmlite.tests.test_binding.TestGlobalConstructors) 
... Segmentation fault
E: pybuild pybuild:283: test: plugin custom failed with: exit code=139: 
python2.7 -m unittest discover -v
dh_auto_test: pybuild --test -i python{version} -p 2.7 returned exit code 13
make[1]: *** [debian/rules:11: override_dh_auto_test] Error 25


I did a bit of investigation and I'm fairly certain this is an LLVM bug
which was fixed in LLVM 6 (although I'm not sure what commit fixes it).
Since LLVM 6 has now been released, I suspect you will be upgrading soon
so I have not tried to backport anything to LLVM 5 at this time.

James


Thanks for checking that over. It appears current LLVMlite doesn't support later
versions of LLVM but no problem it could be removed until it builds again in 
the future.

DS

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

Processed: severity of 892737 is important

[Debian Bug Tracking System]

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

> severity 892737 important
Bug #892737 [puppet] puppet: 
/usr/lib/ruby/vendor_ruby/puppet/gettext/config.rb:156:in 
`copy_default_translations': undefined method `chain'
Severity set to 'important' from 'grave'
> thanks
Stopping processing here.

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

Bug#892091: [Pkg-ayatana-devel] Bug#892091: ayatana-indicator-power: FTBFS randomly - gschemas.compiled generated twice

[Mike Gabriel]

Hi James,

On  Mo 12 Mär 2018 14:29:18 CET, James Cowgill wrote:


Hi,

On 11/03/18 15:40, Mike Gabriel wrote:

On  Mo 05 Mär 2018 12:31:34 CET, James Cowgill wrote:

From cmake-commands(7) - add_custom_command:
"Do not list the output in more than one independent target that may
build in parallel or the two instances of the rule may conflict (instead
use the add_custom_target() command to drive the command and make the
other targets depend on that one)."

There are three independent targets here which use gschemas.compiled
(the three tests).

I found this blog which tries to explain it (number 4):
https://samthursfield.wordpress.com/2015/11/21/cmake-dependencies-between-targets-and-files-and-custom-commands/


James


Thanks for your research on this.

Would this feel like a valid fix?

```
diff --git a/tests/CMakeLists.txt b/tests/CMakeLists.txt
index 2c45057..714fa6c 100644
--- a/tests/CMakeLists.txt
+++ b/tests/CMakeLists.txt
@@ -32,6 +32,14 @@ add_custom_command (OUTPUT gschemas.compiled
 COMMAND cp -f ${CMAKE_BINARY_DIR}/data/*gschema.xml
${SCHEMA_DIR}
 COMMAND ${COMPILE_SCHEMA_EXECUTABLE} ${SCHEMA_DIR})

+add_custom_target(
+    test-notify-gschemas ALL DEPENDS gschemas.compiled
+)
+
+add_custom_target(
+    test-device-gschemas ALL DEPENDS gschemas.compiled
+)


I don't think this will work because these two targets might be built in
parallel and we end up with the same problem as before. I think you want
a single custom target which all the tests depend on.

James


Hmm, but what you say above would contradict the howto provided under  
(4.) at this URL [1] (the one you quoted earlier).


I think, I exactly immitated what Sam Thursfield wrote on his blog.  
Don't you think?


Mike

[1]  
https://samthursfield.wordpress.com/2015/11/21/cmake-dependencies-between-targets-and-files-and-custom-commands/

--

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

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



pgpqMTfTfvGQ8.pgp
Description: Digitale PGP-Signatur

Bug#892737: [Pkg-puppet-devel] Bug#892737: Bug#892737: puppet: /usr/lib/ruby/vendor_ruby/puppet/gettext/config.rb:156:in `copy_default_translations': undefined method `chain'

[Apollon Oikonomopoulos]

Control: tags -1 unreproducible moreinfo
Control: tags -1 severity important

Hi Jan,

[Downgrading severity as it does not seem to be affecting all systems 
ATM]

On 13:54 Mon 12 Mar , Jan Huijsmans wrote:
> Hi Apollon,
> 
> On Mon, 12 Mar 2018 13:57:03 +0200 Apollon Oikonomopoulos
>  wrote:
> > Hi,
> > 
> > Thanks for the report,
> > 
> > On 12:33 Mon 12 Mar , Jan Huijsmans wrote:
> > > Would love tips on how to get this setup working or downgrade back
> > > to 4.10.4.
> > 
> > I'll have a look at the issue as soon as possible. In the meantime,
> > you can obtain 4.10.4 from
> > http://snapshot.debian.org/package/puppet/4.10.4-2/
> 
> Thanks for the link, great to be able to get the packages. Reinstalled
> the old version and everything works again as expected.
> 
> I'll compare the debian (a few clients) and the raspbian
> (puppet-master) to see if I can find differences. Iy looks like
> gettext(-setup) is a dependency. (but have it installed and it gives
> the error)

It's not a strict dependency: puppet tries to load it, but it works fine 
without it. It's this line that worries me most to be honest:

> /usr/lib/ruby/vendor_ruby/puppet/gettext/config.rb:156:in 
> `copy_default_translations': undefined method `chain' for 
> # (NoMethodError)

It seems that somehow it has managed to get the internal state mixed up, as the
object should be a FastGettext::TranslationRepository::Chain, and not
FastGettext::TranslationRepository::Po. I have no idea how that 
happened, but you can help me find out. Can you please run the attached 
script (ruby puppet-locale-test.rb) on your master and reply with the 
output?

Regards,
Apollon


puppet-locale-test.rb
Description: application/ruby


signature.asc
Description: PGP signature

Processed (with 1 error): Re: [Pkg-puppet-devel] Bug#892737: Bug#892737: puppet: /usr/lib/ruby/vendor_ruby/puppet/gettext/config.rb:156:in `copy_default_translations': undefined method `chain'

[Debian Bug Tracking System]

Processing control commands:

> tags -1 unreproducible moreinfo
Bug #892737 [puppet] puppet: 
/usr/lib/ruby/vendor_ruby/puppet/gettext/config.rb:156:in 
`copy_default_translations': undefined method `chain'
Added tag(s) moreinfo and unreproducible.
> tags -1 severity important
Unknown tag/s: severity, important.
Recognized are: patch wontfix moreinfo unreproducible fixed potato woody sid 
help security upstream pending sarge sarge-ignore experimental d-i confirmed 
ipv6 lfs fixed-in-experimental fixed-upstream l10n newcomer a11y etch 
etch-ignore lenny lenny-ignore squeeze squeeze-ignore wheezy wheezy-ignore 
jessie jessie-ignore stretch stretch-ignore buster buster-ignore bullseye 
bullseye-ignore.


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

Bug#892091: [Pkg-ayatana-devel] Bug#892091: ayatana-indicator-power: FTBFS randomly - gschemas.compiled generated twice

[James Cowgill]

Hi,

On 11/03/18 15:40, Mike Gabriel wrote:
> On  Mo 05 Mär 2018 12:31:34 CET, James Cowgill wrote:
>> From cmake-commands(7) - add_custom_command:
>> "Do not list the output in more than one independent target that may
>> build in parallel or the two instances of the rule may conflict (instead
>> use the add_custom_target() command to drive the command and make the
>> other targets depend on that one)."
>>
>> There are three independent targets here which use gschemas.compiled
>> (the three tests).
>>
>> I found this blog which tries to explain it (number 4):
>> https://samthursfield.wordpress.com/2015/11/21/cmake-dependencies-between-targets-and-files-and-custom-commands/
>>
>>
>> James
> 
> Thanks for your research on this.
> 
> Would this feel like a valid fix?
> 
> ```
> diff --git a/tests/CMakeLists.txt b/tests/CMakeLists.txt
> index 2c45057..714fa6c 100644
> --- a/tests/CMakeLists.txt
> +++ b/tests/CMakeLists.txt
> @@ -32,6 +32,14 @@ add_custom_command (OUTPUT gschemas.compiled
>  COMMAND cp -f ${CMAKE_BINARY_DIR}/data/*gschema.xml
> ${SCHEMA_DIR}
>  COMMAND ${COMPILE_SCHEMA_EXECUTABLE} ${SCHEMA_DIR})
> 
> +add_custom_target(
> +    test-notify-gschemas ALL DEPENDS gschemas.compiled
> +)
> +
> +add_custom_target(
> +    test-device-gschemas ALL DEPENDS gschemas.compiled
> +)

I don't think this will work because these two targets might be built in
parallel and we end up with the same problem as before. I think you want
a single custom target which all the tests depend on.

James



signature.asc
Description: OpenPGP digital signature

Bug#892133: [Pkg-javascript-devel] Bug#892133: Bug#892133: node-rollup: does not work after a no-change rebuild (the one in the archive is not suitable for main?)

[Pirate Praveen]

On Tue, 6 Mar 2018 18:18:05 +0530 Pirate Praveen
 wrote:
> On ചൊവ്വ 06 മാർച്ച് 2018 04:17 വൈകു, Gianfranco Costamagna wrote:
> > Hello,
> > I can reproduce with both Debian and Ubuntu, with clean environments in 
> > both cases.
> > (I use pbuilder clean environments)
> 
> I could not reproduce it using sbuild and then sbuild --extra-package
> options. I was able to reproduce it in my local system and in an
> uptodate lxc container.

This issue seems to be fixed, but #892742 makes it hard to confirm in a
clean system.

Can you check again with node-rollup-plugin-commonjs 8.3.0-2?



signature.asc
Description: OpenPGP digital signature

Bug#891582: Dependency missing in vulkan-utils

[Timo Aaltonen]

severity 891582 normal
thanks

On 26.02.2018 22:09, Brett Johnson wrote:
> Package: vulkan
> Version: 1.0.65.2+dfsg1-1
> Severity: serious
> Justification: 1
> 
> 
> The utility "vulkan-smoketest" in the vulkan-utils package depends on
> layers in the libvulkan-dev package, but there is no dependency.  This
> can be easily verified by running it with the "--validate" option:
> 
> $ vulkan-smoketest --validate
> terminate called after throwing an instance of 'std::runtime_error'
>   what():  instance layer VK_LAYER_LUNARG_standard_validation is missing
> Aborted
> 
> 
> The easiest way to fix this is simply add a dependency, but it raises
> the question of why the vulkan-utils package exists.  Both vulkaninfo
> and smoketest could reasonably just be part of libvulkan-dev, as both
> are really vulkan developer utilities, rather than general purpose
> utilities.
But vulkan-smoketest runs fine without the dev package. Smoketest and
vulkaninfo are useful as a quick way to test the driver and/or the system.


-- 
t

Processed: Re: Bug#891582: Dependency missing in vulkan-utils

[Debian Bug Tracking System]

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

> severity 891582 normal
Bug #891582 [vulkan] Dependency missing in vulkan-utils
Severity set to 'normal' from 'serious'
> thanks
Stopping processing here.

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

Bug#892742: rollup FTBFS with node-rollup-plugin-commonjs 9.0

[Pirate Praveen]

Package: src:node-rollup
Version: 0.50.0-1
Severity: serious

dh_auto_build
echo 0.50.0-1 > .commithash \
&& rollup -c

src/node-entry.js → dist/rollup.js, dist/rollup.es.js...
[!] (commonjs plugin) TypeError: parse is not a function in
/<>/src/node-entry.js
src/node-entry.js
TypeError: parse is not a function in /<>/src/node-entry.js
at error (/usr/lib/nodejs/rollup/dist/rollup.js:192:14)
at Promise.resolve.then.catch.err
(/usr/lib/nodejs/rollup/dist/rollup.js:4201:6)
at 
at process._tickCallback (internal/process/next_tick.js:188:7)
at Function.Module.runMain (module.js:678:11)
at startup (bootstrap_node.js:187:16)
at bootstrap_node.js:608:3

Such breakages could be found before upload by using
https://salsa.debian.org/ruby-team/meta/blob/master/build-and-upload
(and I have shared this earlier too when node-source-map 0.7 broke a lot
of reverse dependencies). A major version really means introducing a
breaking change.



signature.asc
Description: OpenPGP digital signature

Bug#892737: [Pkg-puppet-devel] Bug#892737: puppet: /usr/lib/ruby/vendor_ruby/puppet/gettext/config.rb:156:in `copy_default_translations': undefined method `chain'

[Jan Huijsmans]

Hi Apollon,

On Mon, 12 Mar 2018 13:57:03 +0200 Apollon Oikonomopoulos
 wrote:
> Hi,
> 
> Thanks for the report,
> 
> On 12:33 Mon 12 Mar , Jan Huijsmans wrote:
> > Would love tips on how to get this setup working or downgrade back
> > to 4.10.4.
> 
> I'll have a look at the issue as soon as possible. In the meantime,
> you can obtain 4.10.4 from
> http://snapshot.debian.org/package/puppet/4.10.4-2/

Thanks for the link, great to be able to get the packages. Reinstalled
the old version and everything works again as expected.

I'll compare the debian (a few clients) and the raspbian
(puppet-master) to see if I can find differences. Iy looks like
gettext(-setup) is a dependency. (but have it installed and it gives
the error)

Regards,

Jan

Bug#892741: llvmlite: FTBFS on mips64el - testsuite segfaults

[James Cowgill]

Source: llvmlite
Version: 0.22.0-1
Severity: serious
Tags: sid buster

Hi,

llvmlite FTBFS on mips64el with this segmentation fault:
>debian/rules override_dh_auto_test
> make[1]: Entering directory '/<>'
> PYBUILD_SYSTEM=custom PYBUILD_TEST_ARGS="{interpreter} -m unittest discover 
> -v" dh_auto_test
> I: pybuild base:184: python2.7 -m unittest discover -v
> test_function_cfg_on_llvm_value (llvmlite.tests.test_binding.TestAnalysis) 
> ... ok
> test_get_function_cfg_on_ir (llvmlite.tests.test_binding.TestAnalysis) ... ok
> test_linux (llvmlite.tests.test_binding.TestDependencies) ... skipped 
> 'Distribution-specific test'
> test_bad_library (llvmlite.tests.test_binding.TestDylib) ... ok
> test_libm (llvmlite.tests.test_binding.TestDylib) ... ok
> test_close (llvmlite.tests.test_binding.TestFunctionPassManager) ... ok
> test_initfini (llvmlite.tests.test_binding.TestFunctionPassManager) ... ok
> test_run (llvmlite.tests.test_binding.TestFunctionPassManager) ... ok
> test_add_module (llvmlite.tests.test_binding.TestGlobalConstructors) ... ok
> test_add_module_lifetime (llvmlite.tests.test_binding.TestGlobalConstructors) 
> ... ok
> test_add_module_lifetime2 
> (llvmlite.tests.test_binding.TestGlobalConstructors) ... ok
> test_close (llvmlite.tests.test_binding.TestGlobalConstructors) ... ok
> test_emit_assembly (llvmlite.tests.test_binding.TestGlobalConstructors)
> Test TargetMachineRef.emit_assembly() ... ok
> test_emit_object (llvmlite.tests.test_binding.TestGlobalConstructors)
> Test TargetMachineRef.emit_object() ... ok
> test_global_ctors_dtors (llvmlite.tests.test_binding.TestGlobalConstructors) 
> ... Segmentation fault
> E: pybuild pybuild:283: test: plugin custom failed with: exit code=139: 
> python2.7 -m unittest discover -v
> dh_auto_test: pybuild --test -i python{version} -p 2.7 returned exit code 13
> make[1]: *** [debian/rules:11: override_dh_auto_test] Error 25

I did a bit of investigation and I'm fairly certain this is an LLVM bug
which was fixed in LLVM 6 (although I'm not sure what commit fixes it).
Since LLVM 6 has now been released, I suspect you will be upgrading soon
so I have not tried to backport anything to LLVM 5 at this time.

James



signature.asc
Description: OpenPGP digital signature

Bug#892690: Autoconf-archive bug

[Adrian Bunk]

On Sun, Mar 11, 2018 at 11:48:32PM +0100, Bastien ROUCARIES wrote:
> Hi,
> 
> Could you recheck with newer version just uploaded ?

Yes, the problem is still present in 20170928-1.

> And close if not found
> 
> Bastien

cu
Adrian

-- 

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

Bug#892460: marked as done (ruby-parslet: FTBFS and Debci failure with Ruby 2.5)

[Debian Bug Tracking System]

Your message dated Mon, 12 Mar 2018 12:55:04 +
with message-id 
and subject line Bug#892460: fixed in ruby-parslet 1.8.2-2
has caused the Debian Bug report #892460,
regarding ruby-parslet: FTBFS and Debci failure with Ruby 2.5
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.)


-- 
892460: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892460
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-parslet
Version: 1.8.2-1
Severity: serious

https://ci.debian.net/packages/r/ruby-parslet/unstable/amd64/
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/ruby-parslet.html

...
Failures:

  1) Regression on example/mathn.rb runs successfully
 Failure/Error: io.read.strip.should == File.read(name).strip

   expected: "it terminates before we require mathn\nrequiring mathn 
now\nand trying again (will hang without the fix)\nokay!"
got: "it terminates before we require mathn\nrequiring mathn now" 
(using ==)
   Diff:
   @@ -1,5 +1,3 @@
it terminates before we require mathn
requiring mathn now
   -and trying again (will hang without the fix)
   -okay!
 # ./spec/acceptance/examples_spec.rb:25:in `block (5 levels) in '
 # ./spec/acceptance/examples_spec.rb:21:in `any?'
 # ./spec/acceptance/examples_spec.rb:21:in `block (4 levels) in '

Finished in 1 minute 1.22 seconds (files took 8.01 seconds to load)
436 examples, 1 failure

Failed examples:

rspec ./spec/acceptance/examples_spec.rb[1:3:1] # Regression on 
example/mathn.rb runs successfully

/usr/bin/ruby2.5 /usr/bin/rspec --pattern ./spec/\*\*/\*_spec.rb --format 
documentation failed
ERROR: Test "ruby2.5" failed. Exiting.
dh_auto_install: dh_ruby --install 
/build/1st/ruby-parslet-1.8.2/debian/ruby-parslet returned exit code 1
make: *** [debian/rules:6: binary] Error 1
--- End Message ---
--- Begin Message ---
Source: ruby-parslet
Source-Version: 1.8.2-2

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

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

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

Debian distribution maintenance software
pp.
HIGUCHI Daisuke (VDR dai)  (supplier of updated ruby-parslet 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 12 Mar 2018 21:09:56 +0900
Source: ruby-parslet
Binary: ruby-parslet
Architecture: source all
Version: 1.8.2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers 

Changed-By: HIGUCHI Daisuke (VDR dai) 
Description:
 ruby-parslet - Parser construction library with great error reporting in Ruby
Closes: 892460
Changes:
 ruby-parslet (1.8.2-2) unstable; urgency=medium
 .
   * Team upload.
 .
   [ HIGUCHI Daisuke (VDR dai) ]
   * d/p/002_remove-ruby2.5-deprecated-mathn.patch: remove deprecated mathn
 library (Closes: #892460).
   * d/tests: use quilt.
Checksums-Sha1:
 6855419b56b856fe44ba7601ca5f8795f81974bf 2201 ruby-parslet_1.8.2-2.dsc
 485fc6302332d4bf99be7bb2edd1b1599cf77eec 5204 
ruby-parslet_1.8.2-2.debian.tar.xz
 9d7276948a09eb9cd33c23476dca92dae5d23b52 53376 ruby-parslet_1.8.2-2_all.deb
 028c6749b0c70bc3c9e3cdf99aa4dac033f7c8e0 6990 
ruby-parslet_1.8.2-2_amd64.buildinfo
Checksums-Sha256:
 6dbf541576a49fdd9e370d473c56aea139046de62f1818b51783cc2b7250ad4e 2201 
ruby-parslet_1.8.2-2.dsc
 2173c14cfb01b156ac2ca7d78baf6b15d6503d1864fe7defc3e94eea877b601d 5204 
ruby-parslet_1.8.2-2.debian.tar.xz
 e0a08298dcbc3c423023bda3ee844e36171cbdca553a7904aa7f1887ad396004 53376 
ruby-parslet_1.8.2-2_all.deb
 96696e9a573b8fd3e50167d49b3c59b016654311fb7c17976123d92865285cc6 6990 
ruby-parslet_1.8.2-2_amd64.buildinfo
Files:
 5b4c7f265888a02464a7a6f0e905e2f0 2201 ruby optional ruby-parslet_1.8.2-2.dsc
 473a9e0ffa2ae2520d67f8f2074f1d89 5204 ruby optional 
ruby-parslet_1.8.2-2.debian.tar.xz
 e840bd076c7bb3b31837e72852559082 53376 ruby optional 
ruby-parslet_1.8.2-2_all.deb
 2ce769018d191bdf5032f2c2e0f88d16 6990 ruby optional 
ruby-parslet_1.8.2-2_amd64.buildinfo

-BEGIN PGP 

Processed: Bug#892091 marked as pending

[Debian Bug Tracking System]

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

> tag 892091 pending
Bug #892091 [src:ayatana-indicator-power] ayatana-indicator-power: FTBFS 
randomly - gschemas.compiled generated twice
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#892091: marked as pending

[Mike Gabriel]

tag 892091 pending
thanks

Hello,

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


https://anonscm.debian.org/cgit/pkg-ayatana/ayatana-indicator-power.git/commit/?id=505f5ae

---
commit 505f5ae05e420079e59d371a9f01a78d31e020c2
Author: Mike Gabriel 
Date:   Mon Mar 12 13:46:37 2018 +0100

prepare new upstream release

diff --git a/debian/changelog b/debian/changelog
index 3035a71..41322ba 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,9 @@
+ayatana-indicator-power (2.0.93-1) UNRELEASED; urgency=medium
+
+  * New upstream release. (Closes: #892091, #878093).
+
+ -- Mike Gabriel   Mon, 12 Mar 2018 13:45:33 +0100
+
 ayatana-indicator-power (2.0.92-1) unstable; urgency=medium
 
   * New upstream release.

Bug#889108: [Pkg-ayatana-devel] Bug#889108: libgtk2-appindicator-perl: Remove libgtk2-appindicator-perl during the Buster cycle

[Mike Gabriel]

Hi Jeremy,

On  Fr 02 Feb 2018 03:15:44 CET, Jeremy Bicha wrote:


Package: libgtk2-appindicator-perl
Severity: important
User: pkg-perl-maintain...@lists.alioth.debian.org
Usertags: gnome2-removal
X-Debbugs-CC: a...@debian.org

libgtk2-appindicator-perl has no reverse-depends and its only
reverse-recommends is shutter. Although shutter is a popular package,
it is unmaintained and seems unlikely to be included in the Buster
release without major work to port it to gtk3.

See https://bugs.debian.org/870418

I don't think it makes sense to include a deprecated unmaintained
library in Debian with no reverse dependencies. The replacement is
GObject Introspection and either gir1.2-appindicator3-0.1 or
gir1.2-ayatanaappindicator3-0.1. That requires developers to use gtk3
instead of gtk2.

Thanks,
Jeremy Bicha


Please go ahead with the removal of libgtk2-appindicator-perl. The new  
Ayatana Indicators stack does not depend on this package and it really  
seems unmaintained.


Will you file the removal request once shutter is gone from the archive?

Cheers,
Mike
--

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

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



pgpDQDbIu5MY2.pgp
Description: Digitale PGP-Signatur

Processed (with 2 errors): Merge bugs

[Debian Bug Tracking System]

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

> merge 892720 892721 89724
Bug #892720 [cron] Warning: * is not a regular file!
Unable to merge bugs because:
severity of #89724 is 'serious' not 'important'
done of #89724 is 'Karl Bartel ' not ''
package of #89724 is 'penguin-command' not 'cron'
severity of #892721 is 'normal' not 'important'
Failed to merge 892720: Did not alter merged bugs.

> tags -1 pending
Failed to alter tags of Bug -1: The 'bug' parameter ("-1") to 
Debbugs::Control::set_tag did not pass regex check
.

> thanks
Stopping processing here.

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

Bug#892460: Bug #892460 in ruby-parslet marked as pending

[dai]

Control: tag -1 pending

Hello,

Bug #892460 in ruby-parslet 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/ruby-team/ruby-parslet/commit/99eba30d95e2fcc5a618c064c0b45bf38cf49dc0


remove deprecated mathn library (Closes: #892460).



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/892460

Processed: Bug #892460 in ruby-parslet marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #892460 [src:ruby-parslet] ruby-parslet: FTBFS and Debci failure with Ruby 
2.5
Added tag(s) pending.

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

Processed: severity of 892736 is normal

[Debian Bug Tracking System]

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

> severity 892736 normal
Bug #892736 [udev] udev: systemd-udevd.service include is wrong
Severity set to 'normal' from 'grave'
> thanks
Stopping processing here.

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

Bug#892737: [Pkg-puppet-devel] Bug#892737: puppet: /usr/lib/ruby/vendor_ruby/puppet/gettext/config.rb:156:in `copy_default_translations': undefined method `chain'

[Apollon Oikonomopoulos]

Hi,

Thanks for the report,

On 12:33 Mon 12 Mar , Jan Huijsmans wrote:
> Would love tips on how to get this setup working or downgrade back to 
> 4.10.4.

I'll have a look at the issue as soon as possible. In the meantime, you 
can obtain 4.10.4 from http://snapshot.debian.org/package/puppet/4.10.4-2/

Regards,
Apollon

Bug#892738: consolekit: consolekit removal causes a regression

[Benedikt Spranger]

Package: consolekit
Version: 0.4.6-6
Severity: serious

Dear Maintainer,

please readd consolekit to the archive. Without consolekit the
dependency to libpam-systemd as alternative to consolekit forces me to
install systemd without any further benefit.

Since my systems works fine before (and till now, since consolekit
0.4.6-6 is installed) the removal of consolekit from the archive causes
a regression. As my understanding of init system dependencies this is a
serious bug, since it forces a dependency to a special system init
system without any need. So please readd consolekit to the archive.

Sincerly yours
Bene

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

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

Versions of packages consolekit depends on:
ii  dbus   1.12.6-2
ii  libacl12.2.52-3+b1
ii  libc6  2.27-1
ii  libck-connector0   0.4.6-6
ii  libdbus-1-31.12.6-2
ii  libdbus-glib-1-2   0.110-2
ii  libglib2.0-0   2.54.3-2
ii  libpolkit-gobject-1-0  0.105-18
ii  libudev1   237-4
ii  libx11-6   2:1.6.4-3
ii  zlib1g 1:1.2.8.dfsg-5

Versions of packages consolekit recommends:
pn  libpam-ck-connector  

consolekit suggests no packages.

-- no debconf information

Bug#892737: puppet: /usr/lib/ruby/vendor_ruby/puppet/gettext/config.rb:156:in `copy_default_translations': undefined method `chain'

[Jan Huijsmans]

Package: puppet
Version: 5.4.0-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

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

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

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

Situation:

My puppet environment broke after dist-upgrade of buster, changing puppet
related packages from 4.10.4-2 to 5.4.0-1. (date 2018-03-02)

All action from the clients that connect to the master (passenger mode)
fail with error:

Error: Could not retrieve catalog from remote server: Error 500 on SERVER: 
Server Error: undefined method `chain' for 
#

Trying a clean install of 5.4.0-1 results in the error below when trying to 
regenerate the certs:

puppet cert generate trillian --allow-dns-alt-names --debug --verbose
Traceback (most recent call last):
4: from /usr/bin/puppet:5:in `'
3: from /usr/lib/ruby/vendor_ruby/puppet/util/command_line.rb:73:in 
`execute'
2: from /usr/lib/ruby/vendor_ruby/puppet/util/command_line.rb:126:in 
`run'
1: from /usr/lib/ruby/vendor_ruby/puppet/gettext/config.rb:70:in 
`reset_text_domain'
/usr/lib/ruby/vendor_ruby/puppet/gettext/config.rb:156:in 
`copy_default_translations': undefined method `chain' for 
# (NoMethodError)

Reinstall was attempted to see if some config had changed, which it didn't.
Tested with personal configuration as well as clean setup.

At the moment puppet naster operations fail, regeneration of cert fails.
Can't test more, as I need a working puppet-master setup for this.

Did an update of all gems to see if this would help, no result. (debian
packages of all gems were up-to-date as well)

Downgrade to 4.10 is not possible, as it's not obtainable anumore, 4.8 in 
stable is to old as I need 4.9 or 4.10 due to functionality I've installed in 
my puppet code.

Would love tips on how to get this setup working or downgrade back to 4.10.4.
Looks like a dependency is missing in the 5.4 package.

-- System Information:
Distributor ID: Raspbian
Description:Raspbian GNU/Linux testing (buster)
Release:testing
Codename:   buster
Architecture: armv7l

Kernel: Linux 4.9.59-v7+ (SMP w/4 CPU cores)
Locale: LANG=en_US.ISO8859-15, LC_CTYPE=en_US.ISO8859-15 (charmap=ISO-8859-15) 
(ignored: LC_ALL set to en_US.ISO8859-15), LANGUAGE=en_US.ISO8859-15 
(charmap=ISO-8859-15) (ignored: LC_ALL set to en_US.ISO8859-15)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages puppet depends on:
ii  adduser 3.117
ii  facter  3.10.0-3
ii  hiera   3.2.0-2
ii  init-system-helpers 1.51
ii  lsb-base9.20161125+rpi1
ii  ruby1:2.5.0
ii  ruby-augeas 1:0.5.0-3+b2
ii  ruby-deep-merge 1.1.1-1
ii  ruby-shadow 2.5.0-1
ii  ruby2.0 [ruby-interpreter]  2.0.0.484+really457-3
ii  ruby2.1 [ruby-interpreter]  2.1.5-2+deb8u3

Versions of packages puppet recommends:
ii  debconf-utils  1.5.66
ii  lsb-release9.20161125+rpi1
pn  ruby-selinux   

Versions of packages puppet suggests:
pn  ruby-hocon  
pn  ruby-rrd

-- Configuration Files:
/etc/puppet/hiera.yaml changed [not included]
/etc/puppet/puppet.conf changed [not included]

-- no debconf information

-- gem list

*** LOCAL GEMS ***

bigdecimal (default: 1.3.4)
cmath (default: 1.0.0)
colored (1.2)
cri (2.10.1)
csv (default: 1.0.0)
date (default: 1.0.0)
deep_merge (1.1.1)
did_you_mean (1.0.0)
etc (default: 1.0.0)
faraday (0.9.2)
faraday_middleware (0.12.2)
fast_gettext (1.2.0)
fcntl (default: 1.0.0)
fiddle (default: 1.0.0)
fileutils (default: 1.0.2)
gdbm (default: 2.0.0)
gettext (3.2.4)
gettext-setup (0.7)
hiera (3.2.0)
io-console (default: 0.4.6)
ipaddr (default: 1.2.0)
json (default: 2.1.0)
locale (2.1.2)
log4r (1.1.10)
minitar (0.6.1)
minitest (5.10.3)
multi_json (1.12.1)
multipart-post (1.2.0)
net-telnet (0.1.1)
nokogiri (1.8.2)
openssl (default: 2.1.0)
pkg-config (1.2.9)
power_assert (0.2.7)
psych (default: 3.0.2)
puppet_forge (2.2.9)
r10k (2.6.2)
rack (1.6.4)
rake (12.3.0)
rdoc (default: 6.0.1)
rgen (0.8.0)
ruby-shadow (2.5.0)
safe_yaml (1.0.4)
scanf (default: 1.0.0)
sdbm (default: 1.0.0)
semantic_puppet (1.0.1)
soap4r-ruby1.9 (2.0.5)
stringio (default: 0.0.1)
strscan (default: 1.0.0)
systemu (2.6.5)
test-unit (3.2.5)
text (1.3.0)
webrick (default: 1.4.2)
zlib (default: 1.0.0)

Processed: Close the correct bug

[Debian Bug Tracking System]

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

> notfixed 891539 openstack-pkg-tools/72
Bug #891539 {Done: Thomas Goirand } 
[src:python-murano-pkg-check] python-murano-pkg-check FTBFS: test failures
No longer marked as fixed in versions openstack-pkg-tools/72.
> close 892697 72
Bug #892697 [openstack-pkg-tools] broken it.po leads to FTBFS of 
build-dependencies
Bug #892702 [openstack-pkg-tools] broken it.po leads to FTBFS of 
build-dependencies
Marked as fixed in versions openstack-pkg-tools/72.
Marked as fixed in versions openstack-pkg-tools/72.
Bug #892697 [openstack-pkg-tools] broken it.po leads to FTBFS of 
build-dependencies
Bug #892702 [openstack-pkg-tools] broken it.po leads to FTBFS of 
build-dependencies
Marked Bug as done
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#892736: udev: systemd-udevd.service include is wrong

[Jaap van Wingerde]

Package: udev
Version: 232-25+deb9u2
Severity: grave
Justification: renders package unusable

Dear Maintainer,

After upgrading, systemd reports udev errors.

The problem is a wrong include in /etc/systemd/system/systemd-udevd.service:
#.include /usr/lib/systemd/system/systemd-udevd.service
.include /lib/systemd/system/systemd-udevd.service
[Service]
MountFlags=shared

After changing '/usr/lib/...'  in '/lib/...' udev starts normally.

Kind regards,
Jaap van Wingerde.


-- Package-specific info:

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

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

Versions of packages udev depends on:
ii  adduser  3.115
ii  dpkg 1.18.24
ii  libacl1  2.2.52-3+b1
ii  libblkid12.29.2-1+deb9u1
ii  libc62.24-11+deb9u3
ii  libkmod2 23-2
ii  libselinux1  2.6-3+b3
ii  libudev1 232-25+deb9u2
ii  lsb-base 9.20161125
ii  procps   2:3.3.12-3
ii  util-linux   2.29.2-1+deb9u1

udev recommends no packages.

udev suggests no packages.

Versions of packages udev is related to:
ii  systemd  232-25+deb9u2

-- Configuration Files:
/etc/udev/udev.conf changed:
udev_log="info"


-- debconf information:
  udev/sysfs_deprecated_incompatibility:
  udev/new_kernel_needed: false
  udev/reboot_needed:
  udev/title/upgrade:
P: /devices/LNXSYSTM:00
E: DEVPATH=/devices/LNXSYSTM:00
E: ID_VENDOR_FROM_DATABASE=The Linux Foundation
E: MODALIAS=acpi:LNXSYSTM:
E: SUBSYSTEM=acpi
E: USEC_INITIALIZED=8104336

P: /devices/LNXSYSTM:00/LNXCPU:00
E: DEVPATH=/devices/LNXSYSTM:00/LNXCPU:00
E: ID_VENDOR_FROM_DATABASE=The Linux Foundation
E: MODALIAS=acpi:LNXCPU:
E: SUBSYSTEM=acpi
E: USEC_INITIALIZED=8106545

P: /devices/LNXSYSTM:00/LNXCPU:01
E: DEVPATH=/devices/LNXSYSTM:00/LNXCPU:01
E: ID_VENDOR_FROM_DATABASE=The Linux Foundation
E: MODALIAS=acpi:LNXCPU:
E: SUBSYSTEM=acpi
E: USEC_INITIALIZED=8108966

P: /devices/LNXSYSTM:00/LNXCPU:02
E: DEVPATH=/devices/LNXSYSTM:00/LNXCPU:02
E: ID_VENDOR_FROM_DATABASE=The Linux Foundation
E: MODALIAS=acpi:LNXCPU:
E: SUBSYSTEM=acpi
E: USEC_INITIALIZED=8108966

P: /devices/LNXSYSTM:00/LNXCPU:03
E: DEVPATH=/devices/LNXSYSTM:00/LNXCPU:03
E: ID_VENDOR_FROM_DATABASE=The Linux Foundation
E: MODALIAS=acpi:LNXCPU:
E: SUBSYSTEM=acpi
E: USEC_INITIALIZED=8113152

P: /devices/LNXSYSTM:00/LNXPWRBN:00
E: DEVPATH=/devices/LNXSYSTM:00/LNXPWRBN:00
E: DRIVER=button
E: ID_VENDOR_FROM_DATABASE=The Linux Foundation
E: MODALIAS=acpi:LNXPWRBN:
E: SUBSYSTEM=acpi
E: USEC_INITIALIZED=8111617

P: /devices/LNXSYSTM:00/LNXPWRBN:00/input/input2
E: DEVPATH=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2
E: EV=3
E: ID_FOR_SEAT=input-acpi-LNXPWRBN_00
E: ID_INPUT=1
E: ID_INPUT_KEY=1
E: ID_PATH=acpi-LNXPWRBN:00
E: ID_PATH_TAG=acpi-LNXPWRBN_00
E: KEY=10 0
E: MODALIAS=input:b0019vp0001e-e0,1,k74,ramlsfw
E: NAME="Power Button"
E: PHYS="LNXPWRBN/button/input0"
E: PRODUCT=19/0/1/0
E: PROP=0
E: SUBSYSTEM=input
E: TAGS=:seat:
E: USEC_INITIALIZED=8886907

P: /devices/LNXSYSTM:00/LNXPWRBN:00/input/input2/event2
N: input/event2
E: DEVNAME=/dev/input/event2
E: DEVPATH=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2/event2
E: ID_INPUT=1
E: ID_INPUT_KEY=1
E: ID_PATH=acpi-LNXPWRBN:00
E: ID_PATH_TAG=acpi-LNXPWRBN_00
E: MAJOR=13
E: MINOR=66
E: SUBSYSTEM=input
E: TAGS=:power-switch:
E: USEC_INITIALIZED=9014351

P: /devices/LNXSYSTM:00/LNXSYBUS:00
E: DEVPATH=/devices/LNXSYSTM:00/LNXSYBUS:00
E: ID_VENDOR_FROM_DATABASE=The Linux Foundation
E: MODALIAS=acpi:LNXSYBUS:
E: SUBSYSTEM=acpi
E: USEC_INITIALIZED=8127828

P: /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00
E: DEVPATH=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00
E: ID_VENDOR_FROM_DATABASE=The Linux Foundation
E: MODALIAS=acpi:PNP0A03:
E: SUBSYSTEM=acpi
E: USEC_INITIALIZED=8137677

P: /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/PNP0003:00
E: DEVPATH=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/PNP0003:00
E: ID_VENDOR_FROM_DATABASE=The Linux Foundation
E: MODALIAS=acpi:PNP0003:
E: SUBSYSTEM=acpi
E: USEC_INITIALIZED=8140148

P: /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/PNP0103:00
E: DEVPATH=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/PNP0103:00
E: ID_VENDOR_FROM_DATABASE=The Linux Foundation
E: MODALIAS=acpi:PNP0103:
E: SUBSYSTEM=acpi
E: USEC_INITIALIZED=8147821

P: /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/PNP0C02:00
E: DEVPATH=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/PNP0C02:00
E: ID_VENDOR_FROM_DATABASE=The Linux Foundation
E: MODALIAS=acpi:PNP0C02:
E: SUBSYSTEM=acpi
E: USEC_INITIALIZED=8150800

P: /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/device:00
E: DEVPATH=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/device:00
E: SUBSYSTEM=acpi

P: /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/device:01
E: 

Bug#892735: beets tests pull in resources from the network, and fail as well

[Matthias Klose]

Package: src:beets
Version: 1.4.6-1.1
Severity: serious
Tags: sid buster

the beets tests pull in resources from the network, and then fail as well.

[...]
running test
Searching for discogs-client
Reading https://pypi.python.org/simple/discogs-client/
Downloading
https://pypi.python.org/packages/1f/1f/62a8cee111ff72c5ad379039adef8c872813602ffd516ba35368726f14c2/discogs-client-2.2.1.tar.gz#md5=c82be8006e1c02fcfc2bb42a2e312151
Best match: discogs-client 2.2.1
Processing discogs-client-2.2.1.tar.gz
Writing /tmp/easy_install-zu0tmzvm/discogs-client-2.2.1/setup.cfg
Running discogs-client-2.2.1/setup.py -q bdist_egg --dist-dir
/tmp/easy_install-zu0tmzvm/discogs-client-2.2.1/egg-dist-tmp-38vd56jf
warning: no previously-included files matching 'make_symlinks.py' found under
directory 'discogs_client/tests'
zip_safe flag not set; analyzing archive contents...
Moving discogs_client-2.2.1-py3.6.egg to /home/packages/tmp/beets-1.4.6/.eggs

Installed /home/packages/tmp/beets-1.4.6/.eggs/discogs_client-2.2.1-py3.6.egg
Searching for pathlib
Reading https://pypi.python.org/simple/pathlib/
Downloading
https://pypi.python.org/packages/ac/aa/9b065a76b9af472437a0059f77e8f962fe350438b927cb80184c32f075eb/pathlib-1.0.1.tar.gz#md5=5099ed48be9b1ee29b31c82819240537
Best match: pathlib 1.0.1
Processing pathlib-1.0.1.tar.gz
Writing /tmp/easy_install-94hca6pr/pathlib-1.0.1/setup.cfg
Running pathlib-1.0.1/setup.py -q bdist_egg --dist-dir
/tmp/easy_install-94hca6pr/pathlib-1.0.1/egg-dist-tmp-5ghf0vkb
zip_safe flag not set; analyzing archive contents...
Moving pathlib-1.0.1-py3.6.egg to /home/packages/tmp/beets-1.4.6/.eggs

Installed /home/packages/tmp/beets-1.4.6/.eggs/pathlib-1.0.1-py3.6.egg
Searching for oauthlib
Reading https://pypi.python.org/simple/oauthlib/
Downloading
https://pypi.python.org/packages/a5/8a/212e9b47fb54be109f3ff0684165bb38c51117f34e175c379fce5c7df754/oauthlib-2.0.6.tar.gz#md5=277a9a966cc8c72e492b4eeb41332445
Best match: oauthlib 2.0.6
Processing oauthlib-2.0.6.tar.gz
Writing /tmp/easy_install-kz2hycyj/oauthlib-2.0.6/setup.cfg
Running oauthlib-2.0.6/setup.py -q bdist_egg --dist-dir
/tmp/easy_install-kz2hycyj/oauthlib-2.0.6/egg-dist-tmp-nrkifwe0
zip_safe flag not set; analyzing archive contents...
Moving oauthlib-2.0.6-py3.6.egg to /home/packages/tmp/beets-1.4.6/.eggs

Installed /home/packages/tmp/beets-1.4.6/.eggs/oauthlib-2.0.6-py3.6.egg


that's a lot of missing test dependencies ...


[...]
==
FAIL: test_asciify_variable (test_library.DestinationFunctionTest)
--
Traceback (most recent call last):
  File "/home/packages/tmp/beets-1.4.6/test/test_library.py", line 594, in
test_asciify_variable
self._assert_dest(b'/base/abC_1_2d')
  File "/home/packages/tmp/beets-1.4.6/test/test_library.py", line 565, in
_assert_dest
self.assertEqual(actual, dest)
AssertionError: b'/base/abC_ 1_2 d' != b'/base/abC_1_2d'

==
FAIL: test_asciify_character_expanding_to_slash (test_library.DestinationTest)
--
Traceback (most recent call last):
  File "/home/packages/tmp/beets-1.4.6/test/test_library.py", line 430, in
test_asciify_character_expanding_to_slash
self.assertEqual(self.i.destination(), np('lib/abC_1_2d'))
AssertionError: b'/home/packages/tmp/beets-1.4.6/test/lib/abC_ 1_2 d' !=
b'/home/packages/tmp/beets-1.4.6/test/lib/abC_1_2d'

--
Ran 1788 tests in 45.117s

FAILED (failures=2, skipped=31)
Test failed: 
error: Test failed: 
make[1]: *** [debian/rules:16: override_dh_auto_test] Error 1

Bug#892723: dehydrated: Dehydrated broken in stable due to unhandled redirect

[Mattia Rizzolo]

On Mon, Mar 12, 2018 at 11:41:01AM +0100, Mattia Rizzolo wrote:
> I'll see about making a stable update

Attached what I plan on uploading to stable if I get an ACK from the
Stable Release Managers.
(also for you if you need a fixed package - and to help give it wider
testing)

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


dehydrated_0.3.1-3+deb9u2_all.deb
Description: application/vnd.debian.binary-package
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.0
Source: dehydrated
Binary: dehydrated dehydrated-apache2 letsencrypt.sh letsencrypt.sh-apache2
Architecture: all source
Version: 0.3.1-3+deb9u2
Checksums-Md5:
 166d7c4b41ee2c169e654e69c7e75ce7 2495 dehydrated_0.3.1-3+deb9u2.dsc
 06144cac5fb7273fde67a1befd11f7cb 5910 dehydrated-apache2_0.3.1-3+deb9u2_all.deb
 e11e4973866e70b79a7fc67bbd356404 71744 dehydrated_0.3.1-3+deb9u2_all.deb
 3ab6f406576a80593abb34d43ac3606f 6470 
letsencrypt.sh-apache2_0.3.1-3+deb9u2_all.deb
 6615d0994c66fb949c8c8ebeaef81bba 9392 letsencrypt.sh_0.3.1-3+deb9u2_all.deb
Checksums-Sha1:
 ef3537da0c0f7c524b7825c7927d204bf51db195 2495 dehydrated_0.3.1-3+deb9u2.dsc
 c7dea97423219874864c9c7a7804b606ec72d072 5910 
dehydrated-apache2_0.3.1-3+deb9u2_all.deb
 cb8b492ab18f8c755684b0209268a6d70c9d8ea5 71744 
dehydrated_0.3.1-3+deb9u2_all.deb
 12717a1853432993bf4ed964185fa3bd86993cc9 6470 
letsencrypt.sh-apache2_0.3.1-3+deb9u2_all.deb
 7b06c8a3d47089c4ff6381e4448b99ce5ebec2e7 9392 
letsencrypt.sh_0.3.1-3+deb9u2_all.deb
Checksums-Sha256:
 f4cbe4fb741438eea8d3deca2a1b92efd3e14d53102ee65d411d38e433aa6b68 2495 
dehydrated_0.3.1-3+deb9u2.dsc
 3d57dfaf28b62af7d4cc84b5ed053a80057b100ed7b089a7399fcbd748d9f280 5910 
dehydrated-apache2_0.3.1-3+deb9u2_all.deb
 ba6db0965aa89b3a9b230a8dbe817b212ff7e7fc54c611dc1dec67fc6cd52643 71744 
dehydrated_0.3.1-3+deb9u2_all.deb
 604454c6977ec055f6af97d4e309f6d69005983633f60f4c70ae6c1df1f0ca77 6470 
letsencrypt.sh-apache2_0.3.1-3+deb9u2_all.deb
 97829122076ced27f31c70b754150cef5a414a0d0b5e58f92404f3f11f691a2c 9392 
letsencrypt.sh_0.3.1-3+deb9u2_all.deb
Build-Origin: Debian
Build-Architecture: amd64
Build-Date: Mon, 12 Mar 2018 10:57:26 +
Build-Path: /build/dehydrated-0.3.1
Installed-Build-Depends:
 apache2-dev (= 2.4.25-3+deb9u3),
 autoconf (= 2.69-10),
 automake (= 1:1.15-6),
 autopoint (= 0.19.8.1-2),
 autotools-dev (= 20161112.1),
 base-files (= 9.9+deb9u4),
 base-passwd (= 3.5.43),
 bash (= 4.4-5),
 binutils (= 2.28-5),
 bsdmainutils (= 9.0.12+nmu1),
 bsdutils (= 1:2.29.2-1+deb9u1),
 build-essential (= 12.3),
 bzip2 (= 1.0.6-8.1),
 coreutils (= 8.26-3),
 cpp (= 4:6.3.0-4),
 cpp-6 (= 6.3.0-18+deb9u1),
 dash (= 0.5.8-2.4),
 debconf (= 1.5.61),
 debhelper (= 10.2.5),
 debianutils (= 4.8.1.1),
 dh-autoreconf (= 14),
 dh-exec (= 0.23+b1),
 dh-strip-nondeterminism (= 0.034-1),
 diffutils (= 1:3.5-3),
 dpkg (= 1.18.24),
 dpkg-dev (= 1.18.24),
 e2fslibs (= 1.43.4-2),
 e2fsprogs (= 1.43.4-2),
 file (= 1:5.30-1+deb9u1),
 findutils (= 4.6.0+git+20161106-2),
 g++ (= 4:6.3.0-4),
 g++-6 (= 6.3.0-18+deb9u1),
 gcc (= 4:6.3.0-4),
 gcc-6 (= 6.3.0-18+deb9u1),
 gcc-6-base (= 6.3.0-18+deb9u1),
 gettext (= 0.19.8.1-2),
 gettext-base (= 0.19.8.1-2),
 grep (= 2.27-2),
 groff-base (= 1.22.3-9),
 gzip (= 1.6-5+b1),
 hostname (= 3.18+b1),
 init-system-helpers (= 1.48),
 intltool-debian (= 0.35.0+20060710.4),
 libacl1 (= 2.2.52-3+b1),
 libapr1 (= 1.5.2-5),
 libapr1-dev (= 1.5.2-5),
 libaprutil1 (= 1.5.4-3),
 libaprutil1-dev (= 1.5.4-3),
 libarchive-zip-perl (= 1.59-1),
 libasan3 (= 6.3.0-18+deb9u1),
 libatomic1 (= 6.3.0-18+deb9u1),
 libattr1 (= 1:2.4.47-2+b2),
 libaudit-common (= 1:2.6.7-2),
 libaudit1 (= 1:2.6.7-2),
 libblkid1 (= 2.29.2-1+deb9u1),
 libbsd0 (= 0.8.3-1),
 libbz2-1.0 (= 1.0.6-8.1),
 libc-bin (= 2.24-11+deb9u3),
 libc-dev-bin (= 2.24-11+deb9u3),
 libc6 (= 2.24-11+deb9u3),
 libc6-dev (= 2.24-11+deb9u3),
 libcap-ng0 (= 0.7.7-3+b1),
 libcc1-0 (= 6.3.0-18+deb9u1),
 libcilkrts5 (= 6.3.0-18+deb9u1),
 libcomerr2 (= 1.43.4-2),
 libcroco3 (= 0.6.11-3),
 libdb5.3 (= 5.3.28-12+deb9u1),
 libdebconfclient0 (= 0.227),
 libdpkg-perl (= 1.18.24),
 libexpat1 (= 2.2.0-2+deb9u1),
 libexpat1-dev (= 2.2.0-2+deb9u1),
 libfdisk1 (= 2.29.2-1+deb9u1),
 libffi6 (= 3.2.1-6),
 libfile-stripnondeterminism-perl (= 0.034-1),
 libgcc-6-dev (= 6.3.0-18+deb9u1),
 libgcc1 (= 1:6.3.0-18+deb9u1),
 libgcrypt20 (= 1.7.6-2+deb9u2),
 libgdbm3 (= 1.8.3-14),
 libglib2.0-0 (= 2.50.3-2),
 libgmp10 (= 2:6.1.2+dfsg-1),
 libgnutls30 (= 3.5.8-5+deb9u3),
 libgomp1 (= 6.3.0-18+deb9u1),
 libgpg-error0 (= 1.26-2),
 libhogweed4 (= 3.3-1+b2),
 libicu57 (= 57.1-6+deb9u1),
 libidn11 (= 1.33-1),
 libisl15 (= 0.18-1),
 libitm1 (= 6.3.0-18+deb9u1),
 libldap-2.4-2 (= 2.4.44+dfsg-5+deb9u1),
 libldap-common (= 2.4.44+dfsg-5+deb9u1),
 

Bug#392251: marked as done (xchat: please don't depend on gconf2)

[Debian Bug Tracking System]

Your message dated Mon, 12 Mar 2018 11:06:26 +
with message-id 
and subject line Bug#375500: fixed in xchat 2.8.8-14
has caused the Debian Bug report #375500,
regarding xchat: please don't depend on gconf2
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.)


-- 
375500: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=375500
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: xchat-common
Version: 2.6.4-2.1
Severity: important
I don't understand why xchat-common depends on gconf2. gconf2 is a GNOME
configuration software which I do not wish to have installed on my
system. There is already an xchat-gnome package for a version of xchat
polluted with GNOME depends. I believe that xchat-common should not
depend on gconf2.

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)

Versions of packages xchat-common depends on:
ii  gconf22.14.0-4   GNOME configuration
database syste

Versions of packages xchat-common recommends:
ii  xchat 2.6.4-2.1  IRC client for X similar
to AmIRC

-- no debconf information
-- 
Misha Nasledov
mi...@nasledov.com
GPG: A063 B99A 2BD3 2D48 F2D7 8E68 0F27 4D21 948F 8F06

--- End Message ---
--- Begin Message ---
Source: xchat
Source-Version: 2.8.8-14

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

Debian distribution maintenance software
pp.
Gianfranco Costamagna  (supplier of updated xchat 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 12 Mar 2018 10:55:23 +0100
Source: xchat
Binary: xchat xchat-common
Architecture: source
Version: 2.8.8-14
Distribution: unstable
Urgency: medium
Maintainer: Gianfranco Costamagna 
Changed-By: Gianfranco Costamagna 
Description:
 xchat  - IRC client for X similar to AmIRC
 xchat-common - Common files for X-Chat
Closes: 375500
Changes:
 xchat (2.8.8-14) unstable; urgency=medium
 .
   * Do not depend on gconf2 (Closes: #375500)
Checksums-Sha1:
 259bf96b95ddc3369151ccb32939ea67396d9915 1884 xchat_2.8.8-14.dsc
 91747f8afe68fd42f9ce5d327dfde9fad3aa7f59 96992 xchat_2.8.8-14.debian.tar.xz
 69435e46fe416e1017231dae4b32c055efbd124b 7473 xchat_2.8.8-14_source.buildinfo
Checksums-Sha256:
 f5c41a18ce17e8d48a2c19d7388931ab6e37220ce17d7379209642e87134235e 1884 
xchat_2.8.8-14.dsc
 7079cb05200eacee8fc70a8618468818d642df36bca27e76031d806e72a20cad 96992 
xchat_2.8.8-14.debian.tar.xz
 9970621abc686e3772aebb4e43766afd91cee489911e385a97cdca8e4dee3679 7473 
xchat_2.8.8-14_source.buildinfo
Files:
 64232791abafb9f042fbdd06d677ca90 1884 net optional xchat_2.8.8-14.dsc
 9dd3c39a39f589940e749c76bab4db66 96992 net optional 
xchat_2.8.8-14.debian.tar.xz
 85bb0621696553884090dd5b0c898e3c 7473 net optional 
xchat_2.8.8-14_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIcBAEBCAAGBQJapljDAAoJEPNPCXROn13ZvhwQAJaigQ2cv/ft6nxN6I3klxP5
XXx/9lCmhYx+Z4iSIpij/7DAT6tlMlQuNOevnXnEMg10X7EDzdcCtDE8DajlyUM9
xxWG0tQjboAz1I8acacgJsXI2BzoZpCEtiJ5nBp6K+h7ogQ1gaRAfaXdRkidLxuC
yobQaLP5wgiH4dOyBamz4eiaQMnUTL8lWC5weu82elyndwgE/qXFh95cBhA1W5Jy
PXP5FOzKdePB0oZrOPvjxi10nQMhVSVr+KnqSVbj6iKFVvzxNLOvn4zU7Lhj+dRM
VnOv6IglmwXm3UR/4Z6MIJGLyeulK58hQ1JiTs4HXjdsjSKuxWDZ/+UpiycrTwAw
i+v6wtgnuJJ7wfjEN/9SaEiQzlj0+QNZ5IfPHiMArAh0DDociUOEBn6l2I3QGS9e
N65OhHVm9JzZEwQZ6cDtHSdlpQuJxP4JkfXN/P9qplx+3v1BpgvwlGaj0K7HChD8
1/kuNZ6xBG936DvI6OaOa5vtU5g/lHnxMb7ct0weEpXMWZ/9MrbyNG2fSmzGSHPa
y1s8wKI+XPvfdt/z6974AukV/hJM0lpUobXyFavllx9wstnY1C+VSQpJ/iCwK83i
PyPHBvzPsUnlCNumPbhjupKpihW0HoHbE3QDyK9T2jmrSQc6MuAmKP6Dx/mFii+4
gkUlvtp9ZuvP4uaUXOZQ
=Nf1H
-END PGP SIGNATURE End Message ---

Bug#375500: marked as done (xchat: please don't depend on gconf2)

[Debian Bug Tracking System]

Your message dated Mon, 12 Mar 2018 11:06:26 +
with message-id 
and subject line Bug#375500: fixed in xchat 2.8.8-14
has caused the Debian Bug report #375500,
regarding xchat: please don't depend on gconf2
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.)


-- 
375500: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=375500
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: xchat
Version: 2.6.4-2
Severity: normal


xchat now depends on gnome and gconf2.


People who do not want to use gnome thus cannot upgrade.


-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'stable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.16-2-k7
Locale: LANG=C, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)

Versions of packages xchat depends on:
ii  libatk1.0-0 1.11.4-2 The ATK accessibility toolkit
ii  libc6   2.3.6-15 GNU C Library: Shared libraries
ii  libcairo2   1.0.4-2  The Cairo 2D vector graphics libra
ii  libfontconfig1  2.3.2-7  generic font configuration library
ii  libfreetype62.2.1-2  FreeType 2 font engine, shared lib
ii  libglib2.0-02.10.3-1 The GLib library of C routines
ii  libgtk2.0-0 2.8.18-1 The GTK+ graphical user interface 
ii  libpango1.0-0   1.12.3-1 Layout and rendering of internatio
ii  libperl5.8  5.8.8-6  Shared Perl library
ii  libpng12-0  1.2.8rel-5.1 PNG library - runtime
ii  libssl0.9.8 0.9.8b-2 SSL shared libraries
ii  libx11-62:1.0.0-6X11 client-side library
ii  libxcursor1 1.1.5.2-5X cursor management library
ii  libxext61:1.0.0-4X11 miscellaneous extension librar
ii  libxi6  1:1.0.0-5X11 Input extension library
ii  libxinerama11:1.0.1-4X11 Xinerama extension library
ii  libxrandr2  2:1.1.0.2-4  X11 RandR extension library
ii  libxrender1 1:0.9.0.2-4  X Rendering Extension client libra
ii  python2.3   2.3.5-14 An interactive high-level object-o
ii  tcl8.4  8.4.12-1 Tcl (the Tool Command Language) v8
ii  xchat-common2.6.1-1  Common files for X-Chat
ii  zlib1g  1:1.2.3-12   compression library - runtime

xchat recommends no packages.

-- no debconf information

--- End Message ---
--- Begin Message ---
Source: xchat
Source-Version: 2.8.8-14

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

Debian distribution maintenance software
pp.
Gianfranco Costamagna  (supplier of updated xchat 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 12 Mar 2018 10:55:23 +0100
Source: xchat
Binary: xchat xchat-common
Architecture: source
Version: 2.8.8-14
Distribution: unstable
Urgency: medium
Maintainer: Gianfranco Costamagna 
Changed-By: Gianfranco Costamagna 
Description:
 xchat  - IRC client for X similar to AmIRC
 xchat-common - Common files for X-Chat
Closes: 375500
Changes:
 xchat (2.8.8-14) unstable; urgency=medium
 .
   * Do not depend on gconf2 (Closes: #375500)
Checksums-Sha1:
 259bf96b95ddc3369151ccb32939ea67396d9915 1884 xchat_2.8.8-14.dsc
 91747f8afe68fd42f9ce5d327dfde9fad3aa7f59 96992 xchat_2.8.8-14.debian.tar.xz
 69435e46fe416e1017231dae4b32c055efbd124b 7473 xchat_2.8.8-14_source.buildinfo
Checksums-Sha256:
 f5c41a18ce17e8d48a2c19d7388931ab6e37220ce17d7379209642e87134235e 1884 
xchat_2.8.8-14.dsc
 7079cb05200eacee8fc70a8618468818d642df36bca27e76031d806e72a20cad 96992 
xchat_2.8.8-14.debian.tar.xz
 9970621abc686e3772aebb4e43766afd91cee489911e385a97cdca8e4dee3679 7473 
xchat_2.8.8-14_source.buildinfo
Files:
 64232791abafb9f042fbdd06d677ca90 1884 net 

Bug#891628: marked as done (diodon: Fails to build with vala 0.40)

[Debian Bug Tracking System]

Your message dated Mon, 12 Mar 2018 11:04:56 +
with message-id 
and subject line Bug#891628: fixed in diodon 1.8.0-1
has caused the Debian Bug report #891628,
regarding diodon: Fails to build with vala 0.40
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.)


-- 
891628: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891628
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: birdfont
Version:  1.7.0-1
Severity: serious
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: vala-0.40
Tags: buster sid

diodon fails to build from source with vala 0.37.91 which is currently
in experimental and will be uploaded to unstable soon.

You can find a build log from Ubuntu 18.04 Alpha at
https://launchpad.net/~jbicha/+archive/ubuntu/vala40/+build/14327110

On behalf of the Debian GNOME Team,
Jeremy Bicha
--- End Message ---
--- Begin Message ---
Source: diodon
Source-Version: 1.8.0-1

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

Debian distribution maintenance software
pp.
Oliver Sauder  (supplier of updated diodon package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 11 Mar 2018 20:37:08 +0100
Source: diodon
Binary: diodon libdiodon0 gir1.2-diodon-1.0 diodon-dev
Architecture: source
Version: 1.8.0-1
Distribution: unstable
Urgency: medium
Maintainer: Oliver Sauder 
Changed-By: Oliver Sauder 
Description:
 diodon - GTK+ Clipboard manager
 diodon-dev - GTK+ Clipboard manager (development files)
 gir1.2-diodon-1.0 - GTK+ Clipboard manager (GObject introspection data)
 libdiodon0 - GTK+ Clipboard manager (main library)
Closes: 891628
Launchpad-Bugs-Fixed: 1745877
Changes:
 diodon (1.8.0-1) unstable; urgency=medium
 .
   * New upstream release.
   * Remove gee dependency (LP: #1745877)
   * Add support for valac 0.40 (Closes: #891628)
   * Set Section of libdiodon to libs
   * Set Section of diodon-dev to libdevel
   * Bump Standard Version to 4.1.3
   * Fix debian-watch-uses-insecure-uri
   * Use compat version 11
Checksums-Sha1:
 1bd295c7c4bb6f4ea35ed9126cb1f36a97c46651 2131 diodon_1.8.0-1.dsc
 f72be625bdf58f404a9728c6a2f1938080b73e3d 495568 diodon_1.8.0.orig.tar.gz
 66d8508df5acc467d1fc879aed4b31b571f9d8b3 7152 diodon_1.8.0-1.debian.tar.xz
 8f1aa2c69443b272b603d3bca3c60c770fa64fb1 9986 diodon_1.8.0-1_source.buildinfo
Checksums-Sha256:
 b9019ef30e771627f397e99b0a0db8bd1fc5d17ae8fa5d093688598465b7aa27 2131 
diodon_1.8.0-1.dsc
 71299f936e51dde882022abce9adb89c47283646935a203395c8a596770abcb3 495568 
diodon_1.8.0.orig.tar.gz
 54f1fa09fa4de1b92c28ef5974e45b753529188792692c620c0ece62091b9280 7152 
diodon_1.8.0-1.debian.tar.xz
 daf6d07745990448f3c1befc02b6881737a81de6845f1d6c98ca001696f3d3b7 9986 
diodon_1.8.0-1_source.buildinfo
Files:
 84a36a1fb8d922ca9cdb7cc911ee7a7f 2131 utils optional diodon_1.8.0-1.dsc
 ff7c63eb57b226dd4569574f91f5fa1a 495568 utils optional diodon_1.8.0.orig.tar.gz
 e4b2b16fd29c591bd855d028ba4d2daa 7152 utils optional 
diodon_1.8.0-1.debian.tar.xz
 d4a0662e2b8387c71f0eb889415af3e4 9986 utils optional 
diodon_1.8.0-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIcBAEBCAAGBQJapltKAAoJEPNPCXROn13Ze2IQANUi0gPzFr55WzeUJC5Qeunv
J8MlcVTaVwBJUj1ZE+8+k48xCiklaZ9ZlrqM5XPz6Ff8xT9gbpvDI6bnOiN6Kdnm
TrolTZ6gpLa8SfqqvOKWSWn/fqNtsxe21uCRdwHDb9wW5U/13kyetWvc17nzwD7z
B/s+grV6rpyF9/uN028f3JJnwT73qz/SKhrebZgro04TGCYAbXDDcjGlNGvpv7Vv
v2FAURB9OvTh/gR68EQ1Q6C9Igzf28Gzs3RghR/aOX1f/eUXyGnBCsmJ0tFooxiM
ez8HueXI1gEdBfAeA0/Yja3D+gFndkEMQynFp0SJNsgZ15lLHP5edXSElIgbwxNN
Mp92F4wnr+h3PfxuKug1BD7C1rdEsaRxIe7iEDN1GoCay7CAdddC3okFaCFUY5nZ
iYKbRwFOS2nCalLZ8Cz/ZqGbuMFC5LgLwNGG1cpq/WTStagIIwtIcaO2i0XC4mP+
HRLK7JLwNGrKjw73J8nePo25ojBhfvSyJiZll98333upng1tAXkeNlPh+J5dOGaN
nDPJP+HbiyLUzWqulQ0XH2fMH3egyQ4KlpG2/5UyeShECSrZO/XJcc7ASUvDFqxs
Ps6/xPrLLmEWiMdw3thVusNp/oVm2qQBhxfw4jLFRJL+nF/pL5+7vFUMUauV67ZZ
AOiQcoNHeKa0ADUqqy6t
=geR9
-END PGP SIGNATURE End Message ---

Processed: your mail

[Debian Bug Tracking System]

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

> severity 892723 grave
Bug #892723 [dehydrated] dehydrated: Dehydrated broken in stable due to 
unhandled redirect
Severity set to 'grave' from 'important'
> thanks
Stopping processing here.

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

Processed: tagging 375500

[Debian Bug Tracking System]

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

> tags 375500 + buster sid
Bug #375500 [xchat] xchat: please don't depend on gconf2
Bug #392251 [xchat] xchat: please don't depend on gconf2
Added tag(s) sid and buster.
Added tag(s) buster and sid.
> thanks
Stopping processing here.

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

Processed: tagging 698032

[Debian Bug Tracking System]

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

> tags 698032 + buster sid
Bug #698032 [gkdebconf] Migrate from GConf to GSettings
Added tag(s) sid and buster.
> thanks
Stopping processing here.

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

Bug#892710: marked as done ({tcl,tk}-i{tcl,tk}4-{dev,doc}: missing Conflicts: i{tcl,tk}-{dev,doc})

[Debian Bug Tracking System]

Your message dated Mon, 12 Mar 2018 10:36:31 +
with message-id 
and subject line Bug#892710: fixed in itk4 4.1.0-2
has caused the Debian Bug report #892710,
regarding {tcl,tk}-i{tcl,tk}4-{dev,doc}: missing Conflicts: i{tcl,tk}-{dev,doc}
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.)


-- 
892710: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892710
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: tcl-itcl4-dev,tcl-itcl4-doc,tk-itk4-doc,tk-itk4-dev
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: found -1 4.1.0-1
Control: found -1 4.1.1-1

Hi,

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

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

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

  Selecting previously unselected package tcl-itcl4-dev:amd64.
  Preparing to unpack .../tcl-itcl4-dev_4.1.1-1_amd64.deb ...
  Unpacking tcl-itcl4-dev:amd64 (4.1.1-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/tcl-itcl4-dev_4.1.1-1_amd64.deb (--unpack):
   trying to overwrite '/usr/lib/x86_64-linux-gnu/itclConfig.sh', which is also 
in package itcl3-dev:amd64 3.4.3-2
  Errors were encountered while processing:
   /var/cache/apt/archives/tcl-itcl4-dev_4.1.1-1_amd64.deb

  Selecting previously unselected package tcl-itcl4-doc.
  Preparing to unpack .../tcl-itcl4-doc_4.1.1-1_all.deb ...
  Unpacking tcl-itcl4-doc (4.1.1-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/tcl-itcl4-doc_4.1.1-1_all.deb (--unpack):
   trying to overwrite '/usr/share/man/man3/body.3itcl.gz', which is also in 
package itcl3-doc 3.4.3-2
  Errors were encountered while processing:
   /var/cache/apt/archives/tcl-itcl4-doc_4.1.1-1_all.deb

  Selecting previously unselected package tcl-itcl4-dev:amd64.
  Preparing to unpack .../3-tcl-itcl4-dev_4.1.1-1_amd64.deb ...
  Unpacking tcl-itcl4-dev:amd64 (4.1.1-1) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-u8Krl5/3-tcl-itcl4-dev_4.1.1-1_amd64.deb (--unpack):
   trying to overwrite '/usr/lib/x86_64-linux-gnu/itclConfig.sh', which is also 
in package itcl3-dev:amd64 3.4.3-2
  Selecting previously unselected package tk-itk4:amd64.
  Preparing to unpack .../4-tk-itk4_4.1.0-1_amd64.deb ...
  Unpacking tk-itk4:amd64 (4.1.0-1) ...
  Selecting previously unselected package tk-itk4-dev:amd64.
  Preparing to unpack .../5-tk-itk4-dev_4.1.0-1_amd64.deb ...
  Unpacking tk-itk4-dev:amd64 (4.1.0-1) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-u8Krl5/5-tk-itk4-dev_4.1.0-1_amd64.deb (--unpack):
   trying to overwrite '/usr/lib/x86_64-linux-gnu/itkConfig.sh', which is also 
in package itk3-dev:amd64 3.4.2-2
  Errors were encountered while processing:
   /tmp/apt-dpkg-install-u8Krl5/3-tcl-itcl4-dev_4.1.1-1_amd64.deb
   /tmp/apt-dpkg-install-u8Krl5/5-tk-itk4-dev_4.1.0-1_amd64.deb

  Selecting previously unselected package tk-itk4-doc.
  Preparing to unpack .../tk-itk4-doc_4.1.0-1_all.deb ...
  Unpacking tk-itk4-doc (4.1.0-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/tk-itk4-doc_4.1.0-1_all.deb (--unpack):
   trying to overwrite '/usr/share/man/man3/Archetype.3itk.gz', which is also 
in package itk3-doc 3.4.2-2
  Errors were encountered while processing:
   /var/cache/apt/archives/tk-itk4-doc_4.1.0-1_all.deb

The new packages also need a Conflicts against the old virtual package
names (i{tcl,tk}-*) used in stretch and buster to ensure clean upgrade paths.


cheers,

Andreas


itcl3-dev=3.4.3-2_tcl-itcl4-dev=4.1.1-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: itk4
Source-Version: 4.1.0-2

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

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

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

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

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive

Bug#892710: marked as done ({tcl,tk}-i{tcl,tk}4-{dev,doc}: missing Conflicts: i{tcl,tk}-{dev,doc})

[Debian Bug Tracking System]

Your message dated Mon, 12 Mar 2018 10:36:20 +
with message-id 
and subject line Bug#892710: fixed in itcl4 4.1.1-2
has caused the Debian Bug report #892710,
regarding {tcl,tk}-i{tcl,tk}4-{dev,doc}: missing Conflicts: i{tcl,tk}-{dev,doc}
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.)


-- 
892710: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892710
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: tcl-itcl4-dev,tcl-itcl4-doc,tk-itk4-doc,tk-itk4-dev
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: found -1 4.1.0-1
Control: found -1 4.1.1-1

Hi,

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

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

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

  Selecting previously unselected package tcl-itcl4-dev:amd64.
  Preparing to unpack .../tcl-itcl4-dev_4.1.1-1_amd64.deb ...
  Unpacking tcl-itcl4-dev:amd64 (4.1.1-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/tcl-itcl4-dev_4.1.1-1_amd64.deb (--unpack):
   trying to overwrite '/usr/lib/x86_64-linux-gnu/itclConfig.sh', which is also 
in package itcl3-dev:amd64 3.4.3-2
  Errors were encountered while processing:
   /var/cache/apt/archives/tcl-itcl4-dev_4.1.1-1_amd64.deb

  Selecting previously unselected package tcl-itcl4-doc.
  Preparing to unpack .../tcl-itcl4-doc_4.1.1-1_all.deb ...
  Unpacking tcl-itcl4-doc (4.1.1-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/tcl-itcl4-doc_4.1.1-1_all.deb (--unpack):
   trying to overwrite '/usr/share/man/man3/body.3itcl.gz', which is also in 
package itcl3-doc 3.4.3-2
  Errors were encountered while processing:
   /var/cache/apt/archives/tcl-itcl4-doc_4.1.1-1_all.deb

  Selecting previously unselected package tcl-itcl4-dev:amd64.
  Preparing to unpack .../3-tcl-itcl4-dev_4.1.1-1_amd64.deb ...
  Unpacking tcl-itcl4-dev:amd64 (4.1.1-1) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-u8Krl5/3-tcl-itcl4-dev_4.1.1-1_amd64.deb (--unpack):
   trying to overwrite '/usr/lib/x86_64-linux-gnu/itclConfig.sh', which is also 
in package itcl3-dev:amd64 3.4.3-2
  Selecting previously unselected package tk-itk4:amd64.
  Preparing to unpack .../4-tk-itk4_4.1.0-1_amd64.deb ...
  Unpacking tk-itk4:amd64 (4.1.0-1) ...
  Selecting previously unselected package tk-itk4-dev:amd64.
  Preparing to unpack .../5-tk-itk4-dev_4.1.0-1_amd64.deb ...
  Unpacking tk-itk4-dev:amd64 (4.1.0-1) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-u8Krl5/5-tk-itk4-dev_4.1.0-1_amd64.deb (--unpack):
   trying to overwrite '/usr/lib/x86_64-linux-gnu/itkConfig.sh', which is also 
in package itk3-dev:amd64 3.4.2-2
  Errors were encountered while processing:
   /tmp/apt-dpkg-install-u8Krl5/3-tcl-itcl4-dev_4.1.1-1_amd64.deb
   /tmp/apt-dpkg-install-u8Krl5/5-tk-itk4-dev_4.1.0-1_amd64.deb

  Selecting previously unselected package tk-itk4-doc.
  Preparing to unpack .../tk-itk4-doc_4.1.0-1_all.deb ...
  Unpacking tk-itk4-doc (4.1.0-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/tk-itk4-doc_4.1.0-1_all.deb (--unpack):
   trying to overwrite '/usr/share/man/man3/Archetype.3itk.gz', which is also 
in package itk3-doc 3.4.2-2
  Errors were encountered while processing:
   /var/cache/apt/archives/tk-itk4-doc_4.1.0-1_all.deb

The new packages also need a Conflicts against the old virtual package
names (i{tcl,tk}-*) used in stretch and buster to ensure clean upgrade paths.


cheers,

Andreas


itcl3-dev=3.4.3-2_tcl-itcl4-dev=4.1.1-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: itcl4
Source-Version: 4.1.1-2

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

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

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

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

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive

Bug#892695: marked as done ([node-acorn] Create failure in other package)

[Debian Bug Tracking System]

Your message dated Mon, 12 Mar 2018 11:06:55 +0100
with message-id 

Bug#891539: marked as done (python-murano-pkg-check FTBFS: test failures)

[Debian Bug Tracking System]

Your message dated Mon, 12 Mar 2018 09:56:10 +
with message-id 
and subject line Bug#891539: fixed in openstack-pkg-tools 72
has caused the Debian Bug report #891539,
regarding python-murano-pkg-check 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.)


-- 
891539: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891539
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-murano-pkg-check
Version: 0.3.0-2
Severity: serious

Some recent change in unstable makes python-murano-pkg-check FTBFS:

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

...
==
FAIL: 
muranopkgcheck.tests.test_code_structure_checker.CodeStructureTest.test_bad_assigment_case2
muranopkgcheck.tests.test_code_structure_checker.CodeStructureTest.test_bad_assigment_case2
--
_StringException: Traceback (most recent call last):
  File "muranopkgcheck/tests/test_code_structure_checker.py", line 72, in 
test_bad_assigment_case2
self.assertIn('"res" is not valid variable name', p.message)
  File "/usr/lib/python2.7/unittest/case.py", line 804, in assertIn
self.fail(self._formatMessage(msg, standardMsg))
  File "/usr/lib/python2.7/unittest/case.py", line 410, in fail
raise self.failureException(msg)
AssertionError: '"res" is not valid variable name' not found in '"$.deploy()" 
is not valid yaql expression'


==
FAIL: 
muranopkgcheck.tests.test_code_structure_checker.CodeStructureTest.test_bad_assigment_case2
muranopkgcheck.tests.test_code_structure_checker.CodeStructureTest.test_bad_assigment_case2
--
_StringException: Traceback (most recent call last):
  File "muranopkgcheck/tests/test_validator_helpers.py", line 27, in tearDown
self.assertEqual(len(problems), 0)
  File "/usr/lib/python2.7/unittest/case.py", line 513, in assertEqual
assertion_func(first, second, msg=msg)
  File "/usr/lib/python2.7/unittest/case.py", line 506, in _baseAssertEqual
raise self.failureException(msg)
AssertionError: 2 != 0


==
FAIL: 
muranopkgcheck.tests.test_code_structure_checker.CodeStructureTest.test_multiline
muranopkgcheck.tests.test_code_structure_checker.CodeStructureTest.test_multiline
--
_StringException: Traceback (most recent call last):
  File "muranopkgcheck/tests/test_validator_helpers.py", line 27, in tearDown
self.assertEqual(len(problems), 0)
  File "/usr/lib/python2.7/unittest/case.py", line 513, in assertEqual
assertion_func(first, second, msg=msg)
  File "/usr/lib/python2.7/unittest/case.py", line 506, in _baseAssertEqual
raise self.failureException(msg)
AssertionError: 2 != 0


==
FAIL: 
muranopkgcheck.tests.test_code_structure_checker.CodeStructureTest.test_simple
muranopkgcheck.tests.test_code_structure_checker.CodeStructureTest.test_simple
--
_StringException: Traceback (most recent call last):
  File "muranopkgcheck/tests/test_validator_helpers.py", line 27, in tearDown
self.assertEqual(len(problems), 0)
  File "/usr/lib/python2.7/unittest/case.py", line 513, in assertEqual
assertion_func(first, second, msg=msg)
  File "/usr/lib/python2.7/unittest/case.py", line 506, in _baseAssertEqual
raise self.failureException(msg)
AssertionError: 1 != 0


==
FAIL: 
muranopkgcheck.tests.test_code_structure_checker.CodeStructureTest.test_not_empty
muranopkgcheck.tests.test_code_structure_checker.CodeStructureTest.test_not_empty
--
_StringException: Traceback (most recent call last):
  File "muranopkgcheck/tests/test_code_structure_checker.py", line 173, in 
test_not_empty
next(self.g).message)
  File "/usr/lib/python2.7/unittest/case.py", line 804, in assertIn
self.fail(self._formatMessage(msg, standardMsg))
  File "/usr/lib/python2.7/unittest/case.py", line 410, in fail
raise self.failureException(msg)
AssertionError: 

Bug#875505: marked as done (doxygen: build-dependency ruby-compass obsolete and broken)

[Debian Bug Tracking System]

Your message dated Mon, 12 Mar 2018 09:20:37 +
with message-id 
and subject line Bug#875505: fixed in doxygen 1.8.13-10
has caused the Debian Bug report #875505,
regarding doxygen: build-dependency ruby-compass obsolete and broken
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.)


-- 
875505: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875505
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: doxygen
Severity: normal
Tags: serious

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

I made a mistake that cause FTBFS of doxygen, but would prefer to fix it
in doxygen as that would be needed anyway at a later point:

ruby-compass is obsolete and will likely not be released with Buster.
Its replacement is Sass - either the reference Ruby implementation or
alternatives linked with libsass including sassc.

Today I accidentally released to unstable (not experimental as intended)
ruby-sass too new for ruby-compass. I can fix that by re-uploading older
ruby-sass with a fake newer version number, but since only 5 packages
(build-)depend on ruby-compass I would much prefer to instead speedup
the removal of ruby-compass.

Attached is a patch to make doxygen use sassc instead of ruby-compass.

Please consider applying this, and accept my apology for rushing things.
Alternatively I can make an NMU.  Or if neither is acceptable I will do
the more substantial work of postponing this change by reverting
ruby-sass to the older version for now.


 - Jonas

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAlm2694ACgkQLHwxRsGg
ASGs6A//XPN19uTDQWyDIBQ3DQ9t0dTFtZD2AVj3ln6gVuaZ1149ofBd+lOTMRpQ
H2oKo5yI19zjXwe6x3xECpIaZn5AScZoEzJ9zNrq5QhjuFD+LR39ERv5QMogcEH0
oS1hNE84lMaZ4MO1tjX0lurP7ImIZy7X6LjSasjUvyfmzqdoxiCxQcIHmmLGpLb+
/eC1RiOf+0ZVbo6qAT40DVWJPFtXsSSCcH/PyUocEQbRAxKPiN6Rwv4G/Y7n5Jzz
BlOpDOWXjR86OXvIqHzUjxvBzAhaNnfE19oNTTYCBucVwa1kD/AlwXk4/D/4rBtA
UyT/VKFmTMalij/DQSjh3W3tnnR0ZYXR/m7bzLaqmD87KcKQ22cy+7dL+im0ketr
3FoKbqT/JNG0HbjEiiOBpd4O3RD27zkHMGo7GU36GX5DxUiVKFKcyJMyp6GGZu3+
mLpMHRe4qkNY4h7xyilFmhV7LTLBw+7OkTExPNHhfAPqTJpFSyE6dujAbMOEJHUM
VEde6NO8tqz5V1EjDsCPnlXKW9i/5C/Qp5L2CDVF581DbYhUX5QyIkCqWGxuGVLL
ro0ATsRY7UAfTGZnh79UVZiwQP1gV+z8Gl9jAF4N0e6yU0tXN19USdC0cc7HcNQs
qSRdISbb9h12AdZFHrjwoPrEKmXubcjws0zkaAWofUt3Z+NMsyE=
=QEGb
-END PGP SIGNATURE-
Description: Avoid use of compass
 Compass is obsoleted by Sass and its reimplementation in C, sassc.
 .
 This patch avoids use of sass mixins border-radius and box-shadow
 shipped in libraries part of Compass, and adapts build rules to use
 sassc instead of Compass and YUI Compressor.
 .
 Sass mixins border-radius and box-shadow added vendored selectors now
 obsolete: Would help only browsers released in 2011 or earlier, used by
 0.02% of public web browsing today according to .
 .
 If the reference Ruby implementation of Sass is preferred over sassc,
 simply replace "sassc" with "scss" in the Makefile rule.
Author: Jonas Smedegaard 
Last-Update: 2017-09-11
---
This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
--- a/jquery/Makefile
+++ b/jquery/Makefile
@@ -35,10 +35,7 @@
  sass/_round-corners-last-item.scss \
  sass/_sm-dox.scss \
  sass/_sub-items-indentation.scss
-   compass compile --css-dir . --force sass/sm-dox.scss
-   cat sm-core-css.css sm-dox.css > doxmenu.css
-   java -jar $(MINIFIER).jar doxmenu.css > doxmenu-min.css
-   rm -f sm-dox.css doxmenu.css
+   cat sm-core-css.css sass/sm-dox.scss | sassc -I sass --style compressed 
> doxmenu-min.css
 
 scripts: $(SCRIPTS_MIN)
 
--- a/jquery/sass/_round-corners-last-item.scss
+++ b/jquery/sass/_round-corners-last-item.scss
@@ -8,7 +8,7 @@
$selector: $selector + ', ' + $chain + ' a, ' + $chain + 
'*:not(ul) a, ' + $chain + ' ul';
}
#{$selector} {
-   @include border-radius(0 0 $amount $amount);
+   border-radius: 0 0 $amount $amount;
}
// highlighted items, don't need rounding since their sub is open
$chain: $chain_prefix;
@@ -18,6 +18,6 @@
$selector: $selector + ', ' + $chain + ' a.highlighted, ' + 
$chain + '*:not(ul) a.highlighted';
}
#{$selector} {
-   @include border-radius(0);
+   border-radius: 0;
}
 }
--- a/jquery/sass/_sm-dox.scss
+++ b/jquery/sass/_sm-dox.scss
@@ -1,5 +1,3 @@
-@import 'compass';
-
 // This file is best viewed with Tab size 4 code indentation
 
 
@@ 

Processed: reassign 892702 openstack-pkg-tools / retitle 892702 broken it.po leads to FTBFS of build-dependencies

[Debian Bug Tracking System]

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

> reassign 892702 openstack-pkg-tools
Bug #892702 [openstack-pkg-tools] cloudkitty: Fails to build, syntax error in 
po/it.po
Bug #892697 [openstack-pkg-tools] openstack-pkg-tools: Italian debconf 
translation update appears to be broken
Ignoring request to reassign bug #892702 to the same package
Ignoring request to reassign bug #892697 to the same package
> retitle 892702 broken it.po leads to FTBFS of build-dependencies
Bug #892702 [openstack-pkg-tools] cloudkitty: Fails to build, syntax error in 
po/it.po
Bug #892697 [openstack-pkg-tools] openstack-pkg-tools: Italian debconf 
translation update appears to be broken
Changed Bug title to 'broken it.po leads to FTBFS of build-dependencies' from 
'cloudkitty: Fails to build, syntax error in po/it.po'.
Changed Bug title to 'broken it.po leads to FTBFS of build-dependencies' from 
'openstack-pkg-tools: Italian debconf translation update appears to be broken'.
>
End of message, stopping processing here.

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

Bug#886853: marked as done (mariadb-plugin-rocksdb,rocksdb-tools: both ship /usr/bin/sst_dump)

[Debian Bug Tracking System]

Your message dated Mon, 12 Mar 2018 09:45:16 +0100
with message-id 

and subject line Re: Bug#886853: [debian-mysql] Bug#886853: 
mariadb-plugin-rocksdb, rocksdb-tools: both ship /usr/bin/sst_dump
has caused the Debian Bug report #886853,
regarding mariadb-plugin-rocksdb,rocksdb-tools: both ship /usr/bin/sst_dump
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.)


-- 
886853: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886853
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: mariadb-plugin-rocksdb,rocksdb-tools
Severity: serious
User: trei...@debian.org
Usertags: edos-file-overwrite
Control: found -1 10.3.0-0+exp2
Control: found -1 5.9.2-1

Hi,

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

  Selecting previously unselected package rocksdb-tools.
  Preparing to unpack .../rocksdb-tools_5.9.2-1_amd64.deb ...
  Unpacking rocksdb-tools (5.9.2-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/rocksdb-tools_5.9.2-1_amd64.deb (--unpack):
   trying to overwrite '/usr/bin/sst_dump', which is also in package 
mariadb-plugin-rocksdb 10.3.0-0+exp2
  Errors were encountered while processing:
   /var/cache/apt/archives/rocksdb-tools_5.9.2-1_amd64.deb


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

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

  usr/bin/sst_dump

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

Cheers,

Andreas

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


mariadb-plugin-rocksdb=10.3.0-0+exp2_rocksdb-tools=5.9.2-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Version: 5.10.4-2

On Thu, Jan 11, 2018 at 10:57 AM, Otto Kekäläinen  wrote:
> I have filed this upstream as well: https://jira.mariadb.org/browse/MDEV-14918
 Thanks. It seems your upstream doesn't respond to that.

> MariaDB RocksDB engine could start using this sst_dump binary when it
> is available from rocksdb-tools. Currently it is still only in
> experimental though.
 It is in Sid for some days now. Closing this part of the bugreport.

Cheers,
Laszlo/GCS--- End Message ---

Processed: tagging 892643

[Debian Bug Tracking System]

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

> tags 892643 + confirmed
Bug #892643 [src:deepin-image-viewer] deepin-image-viewer FTBFS with 
libdtkwidget-dev 2.0.7-1
Added tag(s) confirmed.
> thanks
Stopping processing here.

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

Bug#888167: marked as done (ruby-recursive-open-struct: FTBFS on ruby2.5: indifferent access overwriting values)

[Debian Bug Tracking System]

Your message dated Mon, 12 Mar 2018 07:49:50 +
with message-id 
and subject line Bug#888167: fixed in ruby-recursive-open-struct 1.1.0-1
has caused the Debian Bug report #888167,
regarding ruby-recursive-open-struct: FTBFS on ruby2.5:  indifferent access 
overwriting values
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.)


-- 
888167: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888167
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-recursive-open-struct
Version: 1.0.2-1
Severity: important
User: debian-r...@lists.debian.org
Usertags: ruby2.5

Dear Maintainer,

This package fails to build against ruby2.5. Soon, there will
be a transition to ruby2.5, and this package will FTBFS in sid.

There may be some details on the wiki about common problems:
https://wiki.debian.org/Teams/Ruby/Ruby25Transition

Build log excerpt:

Failures:

  1) RecursiveOpenStruct indifferent access overwriting values when 
preserve_original_keys is enabled preserves the original keys after resetting 
value
 Failure/Error: expect(recursive.to_h).to eq modified_hash

   expected: {:foo=>[{"bar"=>[{"foo"=>:foo}]}]}
got: {:foo=>[{"bar"=>[{"foo"=>:bar, :foo=>:foo}]}]}

   (compared using ==)

   Diff:
   @@ -1,2 +1,2 @@
   -:foo => [{"bar"=>[{"foo"=>:foo}]}],
   +:foo => [{"bar"=>[{"foo"=>:bar, :foo=>:foo}]}],
 # ./spec/recursive_open_struct/indifferent_access_spec.rb:158:in `block (6 
levels) in '

Finished in 0.0499 seconds (files took 0.25849 seconds to load)
102 examples, 1 failure

Failed examples:

rspec ./spec/recursive_open_struct/indifferent_access_spec.rb:156 # 
RecursiveOpenStruct indifferent access overwriting values when 
preserve_original_keys is enabled preserves the original keys after resetting 
value

/usr/bin/ruby2.5 /usr/bin/rspec --pattern ./spec/\*\*/\*_spec.rb --format 
documentation failed
ERROR: Test "ruby2.5" failed. Exiting.
dh_auto_install: dh_ruby --install 
/build/ruby-recursive-open-struct-1.0.2/debian/ruby-recursive-open-struct 
returned exit code 1
make: *** [binary] Error 1
debian/rules:6: recipe for target 'binary' failed
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2

Full build log:
https://rbuild.fau.xxx/2018-01-23/ruby-recursive-open-struct.log

Please fix it!

Cheers,
Chris.
--- End Message ---
--- Begin Message ---
Source: ruby-recursive-open-struct
Source-Version: 1.1.0-1

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

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

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

Debian distribution maintenance software
pp.
Pirate Praveen  (supplier of updated 
ruby-recursive-open-struct package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 12 Mar 2018 13:04:49 +0530
Source: ruby-recursive-open-struct
Binary: ruby-recursive-open-struct
Architecture: source
Version: 1.1.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers 

Changed-By: Pirate Praveen 
Description:
 ruby-recursive-open-struct - OpenStruct subclass that returns nested hash 
attributes as Recurs
Closes: 888167
Changes:
 ruby-recursive-open-struct (1.1.0-1) unstable; urgency=medium
 .
   * New upstream version 1.1.0 (Closes: #888167)
   * Bump debhelper compat to 11 and standards version to 4.1.3
Checksums-Sha1:
 6e85081914dbbbc60f76a2067299a5c751a7ff9f 2245 
ruby-recursive-open-struct_1.1.0-1.dsc
 6942e707f3812f193381bcefe9711d9653888b3d 14894 
ruby-recursive-open-struct_1.1.0.orig.tar.gz
 a52af3441746768c588addadcdd48cb1169c894c 2044 
ruby-recursive-open-struct_1.1.0-1.debian.tar.xz
 b2eb89eebdf71cb42e641c343a3f619f7a8efe60 7143 
ruby-recursive-open-struct_1.1.0-1_source.buildinfo
Checksums-Sha256:
 fe04f7f60ce6c45fca5ab4a25a7d155e638073de926b0728cc3ec187f1de52e4 2245 
ruby-recursive-open-struct_1.1.0-1.dsc
 b15e88528b90dd85296f39f0cff5214e93ff8aabb67e5dcf552dde589758cf8c 14894 

Bug#892699: marked as done (doris: switch B-D to libepr-api-dev)

[Debian Bug Tracking System]

Your message dated Mon, 12 Mar 2018 06:49:19 +
with message-id 
and subject line Bug#892699: fixed in doris 5.0.3~beta+dfsg-4
has caused the Debian Bug report #892699,
regarding doris: switch B-D to libepr-api-dev
to be marked as done.

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

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


-- 
892699: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892699
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: doris
Version: 5.0.3~beta+dfsg-3
Severity: serious
Justification: fails to build from source

Hi,

the transitional package libepr-api2-dev has been removed, please update
your Build-Depends to use libepr-api-dev instead.


Andreas
--- End Message ---
--- Begin Message ---
Source: doris
Source-Version: 5.0.3~beta+dfsg-4

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

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

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

Debian distribution maintenance software
pp.
Bas Couwenberg  (supplier of updated doris 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: Mon, 12 Mar 2018 07:25:23 +0100
Source: doris
Binary: doris
Architecture: source amd64
Version: 5.0.3~beta+dfsg-4
Distribution: unstable
Urgency: medium
Maintainer: Debian GIS Project 
Changed-By: Bas Couwenberg 
Description:
 doris  - Delft object-oriented radar interferometric software
Closes: 892699
Changes:
 doris (5.0.3~beta+dfsg-4) unstable; urgency=medium
 .
   * Team upload.
   * Change libepr-api2-dev build dependency to libepr-api-dev.
 (closes: #892699)
Checksums-Sha1:
 ee591fbb7cd4dce5e100a732587c0dc41f156b18 2212 doris_5.0.3~beta+dfsg-4.dsc
 f827817982048608081e67217488a6a366c79d6f 24680 
doris_5.0.3~beta+dfsg-4.debian.tar.xz
 57f73b1c3b15fbfeb9ee0b1e68acadbbce2becb1 2747696 
doris-dbgsym_5.0.3~beta+dfsg-4_amd64.deb
 c5929fbcd0a4d5bcdfbc8546ef72233e5c8fa0bd 10531 
doris_5.0.3~beta+dfsg-4_amd64.buildinfo
 b87b7c4511a8c915fc2b3775f1775672da398013 767288 
doris_5.0.3~beta+dfsg-4_amd64.deb
Checksums-Sha256:
 9185c4cc7584552a4b68910a5d485e7803ac5da13e0a0bec82b73b2055eadacb 2212 
doris_5.0.3~beta+dfsg-4.dsc
 1c9c6bdbf9ff90aea309ef812e11a55947a194ccc1d852e84e33c392817e8693 24680 
doris_5.0.3~beta+dfsg-4.debian.tar.xz
 619e651daeccdb56f060eb266fc2685a747ab226a9d8a3cfa809eb3e54d09c5f 2747696 
doris-dbgsym_5.0.3~beta+dfsg-4_amd64.deb
 81b79479f6d058909f11a7286080770780f762182ae2f65670d7a36663b67fbd 10531 
doris_5.0.3~beta+dfsg-4_amd64.buildinfo
 a001935c4fa1e4e9278d2e338a224fac6a6d9a4c655440e30b347999141645bc 767288 
doris_5.0.3~beta+dfsg-4_amd64.deb
Files:
 2a6ea51d956c0e1eac839c9d0393f563 2212 contrib/science optional 
doris_5.0.3~beta+dfsg-4.dsc
 ad026e39052001dbdaba40178b143c14 24680 contrib/science optional 
doris_5.0.3~beta+dfsg-4.debian.tar.xz
 eb195a02c1a46e9af21c09221d9ab046 2747696 contrib/debug optional 
doris-dbgsym_5.0.3~beta+dfsg-4_amd64.deb
 3688c2fc556c7b25aac52f384ca0b5dc 10531 contrib/science optional 
doris_5.0.3~beta+dfsg-4_amd64.buildinfo
 a5187b40107f83608943a04b51f1eb38 767288 contrib/science optional 
doris_5.0.3~beta+dfsg-4_amd64.deb

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEgYLeQXBWQI1hRlDRZ1DxCuiNSvEFAlqmH8UACgkQZ1DxCuiN
SvFCphAAlU/gl068HatBJExowlkoVzBm0YS7TLNVzFUqt0th833jxxfD2A7W6o3V
oWAIENxesQ+x2ei/OSioHQjnNf8aoI9O0Y5g8qaUz4MHN8d5BogyR9esEppR/FLB
ksXNWi+zlnhPlOkahEHQX4+MNehzGDZPR/m+ApaIWOf9NWu+5OOc1EH3CYIdntyV
vBPXOs06FaA1LwTfdfhKTJeU6mEN9P50ra7a7aWcX0H1IkXAapwIsKVNJsJ69OVU
lpYhuWxqfhXKCfHeMN8zxIOA1y3H1bEJEfWGDN5Qth5tvF0gteGgOwz6m9RpnUmk
k7QK5GHDKHOYF+wRCIwey1l8q04npsmBhjqX3AR8hij56g9ausA6PNF8gIw4AYVf
NOXmiJL/xx4CLsQ2gb4bET7QsnaI8UhCyu1ifal7SW+yMal/ktw763WqQqNE+4Sn
+NUC7OheJojzN6ucZ7KPW9Ecd4DNrRUu78AeDD7Xj5YbbKJi5n/Dct/JTk4bjBiD
lE3vLiqv45i0xFj2kfAyreDe6+hPcTP7tY8LT8x+Bg5C7AddgnuqTWEPMsHrZWY6
33ovmQP/DOPL1g68BnXymCjJ5817eOxGmDBZHIeScuMG6oBArXIr2svXFKAw0Jje
p8VinIUxtYQypNTwQiFapLYzXc7aFGq8+TBbrcILpidmrzU6TbU=
=7HrR
-END PGP SIGNATURE End Message ---

Bug#892699: doris: switch B-D to libepr-api-dev

[Sebastiaan Couwenberg]

Control: tags -1 pending

Fixed in git and a new upload to unstable will follow shortly.

Kind Regards,

Bas

Processed: Re: Bug#892699: doris: switch B-D to libepr-api-dev

[Debian Bug Tracking System]

Processing control commands:

> tags -1 pending
Bug #892699 [src:doris] doris: switch B-D to libepr-api-dev
Added tag(s) pending.

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

Bug#888508: gitlab: multiple CVEs from GitLab Security Release: 10.3.4, 10.2.6, and 10.1.6 advisory

[Balasankar C]

Hi,

As per the upstream blogpost,
https://about.gitlab.com/2018/01/16/gitlab-10-dot-3-dot-4-released/ ,
the applicability of the CVEs listed at
https://security-tracker.debian.org/tracker/source-package/gitlab to
version of GitLab in Stretch is as follows.

CVE-2018-3710 - Applicable to version in Stretch (8.13.11)
CVE-2017-0927 - Applicable to version in Stretch (8.13.11)
CVE-2017-0926 - Applicable to version in Stretch (8.13.11)
CVE-2017-0925 - Applicable to version in Stretch (8.13.11)
CVE-2017-0923 - Applicable to version in Stretch (8.13.11)
CVE-2017-0918 - Applicable to version in Stretch (8.13.11)
CVE-2017-0916 - Applicable to version in Stretch (8.13.11)
CVE-2017-0915 - Applicable to version in Stretch (8.13.11)

CVE-2017-0914 - Not applicable to version in Stretch (8.13.11)
CVE-2017-0917 - Not applicable to version in Stretch (8.13.11)

Regarding CVE-2017-0923, I will confirm if it is indeed applicable or
not, since the feature was introduced in version 9.1 only
(https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/10017) .


Regards
Balasankar C



signature.asc
Description: OpenPGP digital signature