Bug#879071: fixed in 0ad 0.0.22-2
[Ludovic Rousseau] > 0ad (0.0.22-2) unstable; urgency=medium > . >* Fix "0ad FTBFS with on armhf with gcc 7: error: call of overloaded > 'abs(unsigned int)' is ambiguous" by removing support of armhf > (Closes: #879071) Note, this "fix" did not work, as there are armhf binaries in the archive and the new version is not allowed to propagate into testing until the armhf binaries are updated to the latest version or removed. Did you file a request for removal? This bug just caused 0ad to be removed from testing. -- Happy hacking Petter Reinholdtsen
Bug#790600:
Hi, I'm the upstream author of Rapid Photo Downloader. As of version 0.9.0, released earlier this year, it has been ported to use the gobject introspection bindings, as well as python 3. The current version is 0.9.5. Let me know if you need any information. Best, Damon Lynch -- http://www.damonlynch.net
Bug#881208: marked as done (networking-arista FTBFS: ValueError: Unexpected boolean value 'value')
Your message dated Fri, 17 Nov 2017 23:49:26 +
with message-id
and subject line Bug#881208: fixed in networking-arista 2017.2.1-1
has caused the Debian Bug report #881208,
regarding networking-arista FTBFS: ValueError: Unexpected boolean value 'value'
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.)
--
881208: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881208
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: networking-arista
Version: 2016.2.0-1
Severity: serious
Tags: buster sid
Some recent change in unstable makes networking-arista FTBFS:
https://tests.reproducible-builds.org/debian/history/networking-arista.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/networking-arista.html
...
==
FAIL:
networking_arista.tests.unit.l3Plugin.test_arista_l3_driver.AristaL3DriverTestCasesMlagConfig.test_add_interface_to_router_on_eos
networking_arista.tests.unit.l3Plugin.test_arista_l3_driver.AristaL3DriverTestCasesMlagConfig.test_add_interface_to_router_on_eos
--
_StringException: stderr: {{{
/usr/lib/python2.7/dist-packages/neutron/common/rpc.py:72: DeprecationWarning:
Using function/method 'oslo_messaging.transport.get_transport()' is deprecated:
use get_rpc_transport or get_notification_transport
aliases=TRANSPORT_ALIASES)
/usr/lib/python2.7/dist-packages/neutron/common/rpc.py:72: DeprecationWarning:
Using function/method 'oslo_messaging.transport.get_transport()' is deprecated:
use get_rpc_transport or get_notification_transport
aliases=TRANSPORT_ALIASES)
}}}
Traceback (most recent call last):
File "networking_arista/tests/unit/l3Plugin/test_arista_l3_driver.py", line
190, in setUp
setup_arista_config('value', mlag=True)
File "networking_arista/tests/unit/l3Plugin/test_arista_l3_driver.py", line
32, in setup_arista_config
cfg.CONF.set_override('mlag_config', value, "l3_arista")
File "/usr/lib/python2.7/dist-packages/oslo_messaging/conffixture.py", line
88, in _wrapper
return wrapped_function(*args, **kwargs)
File "/usr/lib/python2.7/dist-packages/debtcollector/removals.py", line 261,
in wrapper
return f(*args, **kwargs)
File "/usr/lib/python2.7/dist-packages/oslo_config/cfg.py", line 2402, in
__inner
result = f(self, *args, **kwargs)
File "/usr/lib/python2.7/dist-packages/oslo_config/cfg.py", line 2729, in
set_override
opt_info['opt'], override, enforce_type)
File "/usr/lib/python2.7/dist-packages/oslo_config/cfg.py", line 2758, in
_get_enforced_type_value
converted = self._convert_value(value, opt)
File "/usr/lib/python2.7/dist-packages/oslo_config/cfg.py", line 3036, in
_convert_value
return opt.type(value)
File "/usr/lib/python2.7/dist-packages/oslo_config/types.py", line 235, in
__call__
raise ValueError('Unexpected boolean value %r' % value)
ValueError: Unexpected boolean value 'value'
==
FAIL:
networking_arista.tests.unit.l3Plugin.test_arista_l3_driver.AristaL3DriverTestCasesMlagConfig.test_create_router_on_eos
networking_arista.tests.unit.l3Plugin.test_arista_l3_driver.AristaL3DriverTestCasesMlagConfig.test_create_router_on_eos
--
_StringException: stderr: {{{
/usr/lib/python2.7/dist-packages/neutron/common/rpc.py:72: DeprecationWarning:
Using function/method 'oslo_messaging.transport.get_transport()' is deprecated:
use get_rpc_transport or get_notification_transport
aliases=TRANSPORT_ALIASES)
/usr/lib/python2.7/dist-packages/neutron/common/rpc.py:72: DeprecationWarning:
Using function/method 'oslo_messaging.transport.get_transport()' is deprecated:
use get_rpc_transport or get_notification_transport
aliases=TRANSPORT_ALIASES)
}}}
Traceback (most recent call last):
File "networking_arista/tests/unit/l3Plugin/test_arista_l3_driver.py", line
190, in setUp
setup_arista_config('value', mlag=True)
File "networking_arista/tests/unit/l3Plugin/test_arista_l3_driver.py", line
32, in setup_arista_config
cfg.CONF.set_override('mlag_config', value, "l3_arista")
File "/usr/lib/python2.7/dist-packages/oslo_messaging/conffixture.py", line
88, in _wrapper
return wrapped_function(*args, **kwargs)
File "/usr/lib/python2.7/dist-packages/debtcollector/removals.py", line 261,
in wrapper
return f(*args, **kwargs)
File "/usr/lib/python2.7/dist-packages/oslo_config/cfg.py", line 2402, in
__
Processed: severity of 870635 is wishlist
Processing commands for cont...@bugs.debian.org: > severity 870635 wishlist Bug #870635 [mutt] mutt package is not using the official mutt tarball Severity set to 'wishlist' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 870635: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=870635 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#881247: marked as done (python3-gnocchi: fails to upgrade from 'sid' - trying to overwrite /usr/bin/gnocchi-api)
Your message dated Fri, 17 Nov 2017 23:19:32 + with message-id and subject line Bug#881247: fixed in gnocchi 4.0.3-3 has caused the Debian Bug report #881247, regarding python3-gnocchi: fails to upgrade from 'sid' - trying to overwrite /usr/bin/gnocchi-api 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.) -- 881247: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881247 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python3-gnocchi Version: 4.0.3-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'sid' to 'experimental'. It installed fine in 'sid', then the upgrade to 'experimental' 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/ch-relationships.html#s-replaces >From the attached log (scroll to the bottom...): Selecting previously unselected package python3-gnocchi. Preparing to unpack .../113-python3-gnocchi_4.0.3-1_all.deb ... Unpacking python3-gnocchi (4.0.3-1) ... dpkg: error processing archive /tmp/apt-dpkg-install-X04I5y/113-python3-gnocchi_4.0.3-1_all.deb (--unpack): trying to overwrite '/usr/bin/gnocchi-api', which is also in package python-gnocchi 3.0.4-4 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Errors were encountered while processing: /tmp/apt-dpkg-install-X04I5y/113-python3-gnocchi_4.0.3-1_all.deb cheers, Andreas python-gnocchi=3.0.4-4_python3-gnocchi=4.0.3-1.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: gnocchi Source-Version: 4.0.3-3 We believe that the bug you reported is fixed in the latest version of gnocchi, 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 881...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Thomas Goirand (supplier of updated gnocchi 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: Fri, 17 Nov 2017 22:40:08 + Source: gnocchi Binary: gnocchi-api gnocchi-common gnocchi-metricd python3-gnocchi Architecture: source all Version: 4.0.3-3 Distribution: unstable Urgency: medium Maintainer: Debian OpenStack Changed-By: Thomas Goirand Description: gnocchi-api - Metric as a Service - API daemon gnocchi-common - Metric as a Service - common files gnocchi-metricd - Metric as a Service - metric daemon python3-gnocchi - Metric as a Service - Python 3.x Closes: 881247 Changes: gnocchi (4.0.3-3) unstable; urgency=medium . * python3-gnocchi breaks+replaces python-gnocchi, therefore allowing upgrades from older Gnocchi that was using Python 2.7 (Closes: #881247). * Fixed encoding of pt.po. Checksums-Sha1: f217df44dfb7472b6d80ca0d692572110fca7326 3573 gnocchi_4.0.3-3.dsc 2109a43a741a885bffd72be1ec8c89c530e82c65 24764 gnocchi_4.0.3-3.debian.tar.xz 7a413f2ca420b6eec1ade090ffb8bad0983fd60b 19944 gnocchi-api_4.0.3-3_all.deb 0e13ab59ba826669a56ce95dfb007ee13eab2c5d 23332 gnocchi-common_4.0.3-3_all.deb c2f0802dc17352a92f19c223abf898d9ad209d13 6724 gnocchi-metricd_4.0.3-3_all.deb 32f2743ac315eb30d17fba76da8d612f7e3822f4 15228 gnocchi_4.0.3-3_amd64.buildinfo b7958c37c6e6fbf64be43900ee066f6611fe1372 111336 python3-gnocchi_4.0.3-3_all.deb Checksums-Sha256: 21d41ebfb0f2a5b5c524b0e769c89d3f13b308f124b71953ea34338d2de7b615 3573 gnocchi_4.0.3-3.dsc c3e4c6d6cdc7a9cc186928a9fa91a995b46e6fdfffbd31e74d142190ac4fdcbd 24764 gnocchi_4.0.3-3.debian.tar.xz dd57f6af7930698db3493e41f80bbdf0f50c6780f571216008c697d8519bba9c 19944 gnocchi-api_4.0.3-3_all.deb 28080a79eee3eb528399759ea4d6c49ceecb7878da15874ef1f6821d2e895999 23332 gnocchi-common_4.0.3-3_all.deb da248b24a5e740119808dfb5cdf7c64cbadd0cc52b62068a04bb793f27edc6f2 6724 gnocchi-metricd_4.0.3-3_all.deb c940771655bbdf751d4fb8fc4d9f879521863282fb62bd0fba78a7dc5d066252 15228 gnocchi_4.0.3-3_amd64.buildinfo 4bcba45710446769139443a518be4b1fa0c086568ed9aac095de567770b75c00 111336 python3-gnocchi_4.0.3-3_all.deb Files: fbe982a6605c7d30927bc9870c8db427 3573 net optional gnocchi_4.0.3-3.dsc
Bug#881247: marked as pending
tag 881247 pending thanks Hello, Bug #881247 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/openstack/services/gnocchi.git/commit/?id=acc762a --- commit acc762ab61129b249d56a829efc7a30b1b5b3872 Author: Thomas Goirand Date: Fri Nov 17 22:41:37 2017 + * python3-gnocchi breaks+replaces python-gnocchi, therefore allowing upgrades from older Gnocchi that was using Python 2.7 (Closes: #881247). diff --git a/debian/changelog b/debian/changelog index c094dfd..6471351 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,10 @@ +gnocchi (4.0.3-3) unstable; urgency=medium + + * python3-gnocchi breaks+replaces python-gnocchi, therefore allowing +upgrades from older Gnocchi that was using Python 2.7 (Closes: #881247). + + -- Thomas Goirand Fri, 17 Nov 2017 22:40:08 + + gnocchi (4.0.3-2) unstable; urgency=medium * Fixed version of python-sqlalchemy-utils (>= 0.32.14).
Processed: Bug#881247 marked as pending
Processing commands for cont...@bugs.debian.org: > tag 881247 pending Bug #881247 [python3-gnocchi] python3-gnocchi: fails to upgrade from 'sid' - trying to overwrite /usr/bin/gnocchi-api Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 881247: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881247 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Version tracking fix
Processing commands for cont...@bugs.debian.org:
> fixed 881210 1:11.0.1-1
Bug #881210 {Done: Thomas Goirand } [src:neutron-lbaas]
neutron-lbaas FTBFS: TypeError: isinstance() arg 2 must be a class, type, or
tuple of classes and types
Marked as fixed in versions neutron-lbaas/1:11.0.1-1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
881210: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881210
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#881210: marked as done (neutron-lbaas FTBFS: TypeError: isinstance() arg 2 must be a class, type, or tuple of classes and types)
Your message dated Fri, 17 Nov 2017 23:34:04 +0100
with message-id <343baec1-16bb-36da-cd70-df4962bf5...@debian.org>
and subject line Done
has caused the Debian Bug report #881210,
regarding neutron-lbaas FTBFS: TypeError: isinstance() arg 2 must be a class,
type, or tuple of classes and types
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.)
--
881210: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881210
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: neutron-lbaas
Version: 1:9.1.0-2
Severity: serious
Tags: buster sid
Some recent change in unstable makes neutron-lbaas FTBFS:
https://tests.reproducible-builds.org/debian/history/neutron-lbaas.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/neutron-lbaas.html
...
==
FAIL:
neutron_lbaas.tests.unit.common.cert_manager.barbican_auth.test_barbican_acl.TestBarbicanACLAuth.test_get_barbican_client
neutron_lbaas.tests.unit.common.cert_manager.barbican_auth.test_barbican_acl.TestBarbicanACLAuth.test_get_barbican_client
--
_StringException: stderr: {{{
/usr/lib/python2.7/dist-packages/neutron/common/rpc.py:72: DeprecationWarning:
Using function/method 'oslo_messaging.transport.get_transport()' is deprecated:
use get_rpc_transport or get_notification_transport
aliases=TRANSPORT_ALIASES)
/usr/lib/python2.7/dist-packages/neutron/common/rpc.py:72: DeprecationWarning:
Using function/method 'oslo_messaging.transport.get_transport()' is deprecated:
use get_rpc_transport or get_notification_transport
aliases=TRANSPORT_ALIASES)
}}}
Traceback (most recent call last):
File
"neutron_lbaas/tests/unit/common/cert_manager/barbican_auth/test_barbican_acl.py",
line 43, in test_get_barbican_client
barbican_client.Client
File "/usr/lib/python2.7/dist-packages/testtools/testcase.py", line 462, in
assertIsInstance
self.assertThat(obj, matcher, msg)
File "/usr/lib/python2.7/dist-packages/testtools/testcase.py", line 496, in
assertThat
mismatch_error = self._matchHelper(matchee, matcher, message, verbose)
File "/usr/lib/python2.7/dist-packages/testtools/testcase.py", line 547, in
_matchHelper
mismatch = matcher.match(matchee)
File "/usr/lib/python2.7/dist-packages/testtools/matchers/_basic.py", line
275, in match
if isinstance(other, self.types):
TypeError: isinstance() arg 2 must be a class, type, or tuple of classes and
types
--
Ran 513 tests in 233.866s
FAILED (failures=1)
debian/rules:43: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 1
--- End Message ---
--- Begin Message ---
Hi,
Since version 1:11.0.1-1 was uploaded, I believe the issue is fixed. Let
me know if that's not the case.
Cheers,
Thomas Goirand (zigo)--- End Message ---
Bug#881643: spacefm not updated after libavfilter update, broken link.
Hi, OK, the lib was from debian multimedia, from a looong time ago !! (removed debian multimedia from source.list about one or two years ago ??) Using debian version of the lib fixes the problem. Thanks a lot ! You can close the bug. +++ On 17/11/2017 19:19, Mateusz Łukasik wrote: > On 13.11.2017 20:58 +0100, Nathael Pajani wrote: >> Package: spacefm-gtk3 >> Version: 1.0.5-2 >> Severity: grave >> Source: spacefm >> Tags: sid >> >> $ spacefm >> spacefm: relocation error: /usr/lib/x86_64-linux-gnu/libavfilter.so.6: symbol >> av_hwframe_map, version LIBAVUTIL_55 not defined in file libavutil.so.55 >> with link time >> reference >> $ >> >> Looks like the spacefm shoul dbe re-built using the new version of >> libavfilter >> (libavfilter6 is in version 7:3.4-2) and libavutil (libavutil55 in version >> 10:3.2.2-dmo1), >> or that libavutil is missing some symbols. >> >> >> $ ls /usr/lib/x86_64-linux-gnu/libavutil.so* >> /usr/lib/x86_64-linux-gnu/libavutil.so.55 >> /usr/lib/x86_64-linux-gnu/libavutil.so.55.34.100 >> >> $ls /usr/lib/x86_64-linux-gnu/libavfilter.so.6* >> /usr/lib/x86_64-linux-gnu/libavfilter.so.6 >> /usr/lib/x86_64-linux-gnu/libavfilter.so.6.107.100 >> >> >> libc6 : Version: 2.24-17 >> >> > > control: severity -1 normal > > At first please run spacefm based on Debian's official packages > libavutil55 in version 10:3.2.2-dmo1 is not from Debian repository. > > > -- Nathaël PAJANI - ED3L - Techno-Innov Internet : http://www.ed3l.fr - http://www.techno-innov.fr
Bug#881821: marked as done (stylish-haskell build depends on libghc-syb-dev (< 0.7) but 0.7-1 is to be installed)
Your message dated Fri, 17 Nov 2017 21:19:23 + with message-id and subject line Bug#881821: fixed in stylish-haskell 0.8.1.0-1 has caused the Debian Bug report #881821, regarding stylish-haskell build depends on libghc-syb-dev (< 0.7) but 0.7-1 is to be installed 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.) -- 881821: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881821 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: stylish-haskell Version: 0.7.1.0-1 Severity: serious The following packages have unmet dependencies: builddeps:stylish-haskell : Depends: libghc-syb-dev (< 0.7) but 0.7-1 is to be installed --- End Message --- --- Begin Message --- Source: stylish-haskell Source-Version: 0.8.1.0-1 We believe that the bug you reported is fixed in the latest version of stylish-haskell, 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 881...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sean Whitton (supplier of updated stylish-haskell package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 17 Nov 2017 13:56:04 -0700 Source: stylish-haskell Binary: stylish-haskell Architecture: source Version: 0.8.1.0-1 Distribution: unstable Urgency: medium Maintainer: Sean Whitton Changed-By: Sean Whitton Description: stylish-haskell - Haskell code prettifier Closes: 881821 Changes: stylish-haskell (0.8.1.0-1) unstable; urgency=medium . * New upstream release (Closes: #881821). * Declare compliance with Debian Policy version 4.1.1. - Update Priority: 'extra' -> 'optional' Checksums-Sha1: 998129de090ffaf3a564bc702f42f33761459fb6 2947 stylish-haskell_0.8.1.0-1.dsc be18b502c96e6b6f5a238b4f5d9af120e8dd49bc 26348 stylish-haskell_0.8.1.0.orig.tar.xz 7744d65eaf89274577604fb8a7b41e2a6b90d8dd 4456 stylish-haskell_0.8.1.0-1.debian.tar.xz Checksums-Sha256: 00d2feebf6bbb138b3971de1008432852746f59c6d5774bb40c5475fd2d0e494 2947 stylish-haskell_0.8.1.0-1.dsc 023f830b00382ccf871c56e01d03951d52ee6ccfe839c0dc327e1b2388410b51 26348 stylish-haskell_0.8.1.0.orig.tar.xz 579303cc4e43605095c503528275ea239491bde487c93d40cf91b4d1ff2b4004 4456 stylish-haskell_0.8.1.0-1.debian.tar.xz Files: 6c223bfe577e6e421818f6cdc46bf4c6 2947 haskell optional stylish-haskell_0.8.1.0-1.dsc 7e9e98e0d1e17810014a3e7193cbfa78 26348 haskell optional stylish-haskell_0.8.1.0.orig.tar.xz ff5adfb862fdbfd1eda21a31838abe7a 4456 haskell optional stylish-haskell_0.8.1.0-1.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEm5FwB64DDjbk/CSLaVt65L8GYkAFAloPTREACgkQaVt65L8G YkD8EQ/8DmX2bSfhsQhZO6hCMZ+eoaxfnRUeN35inMJh9QFoYsKYsUF+MgbzkgkQ Qsm8YmKUjEfTH8zsg3zW0rnO8wMaPe8pWRwIFR8ocdPXtYXoXqQ0KFkYm5JFM2Pi r9igISE6XURtHbSFfpbsdQmHhwQ3RiVMfa/koo4vHnY/cCFv3DQlPswGyhB9VNZy oaCVJxyDw9LV3m866exrwYzYJ5Igm633huaBRbTJq2DYN2x0+PwsYILec9tUa2O4 lrVU8teQ/drcXM3vyh/ksjihfjoo7CQDaw7H1+t7bMgsQHhj2JoUJpLibL/2VhA0 6g4kyPufxNLbSCXPMZQ7UZvH2PkPOJV8cRHPikV6oEKTcMHoq5mysruRx/syUoUV bvXuav9p/zwVDP2I1tt52CmYhrgkmqtJ6BFCK3WKlz5LHnff3k9EQo1GKcBNCEGu 6yBecTC0b6ZDrbd4qvE+/JW5Wd9e0SeSSB22aSvKMzss+74zc0IKy1s/8TqM1gCA s3+OuLhIwzV8bh77gB8IpoG/FW925cL/QO0Tlz+1MeEqnA9hemu/Be4OtJvqArPA Abi+5gAmJCDU+uUMjWHrySWpiOzceRZVINUqPY8et3k8SIIIzce4eMFThJOfRgt9 FyMdiFUETDPkyAd5aVXugXblezwaJ6AMT/fFzSPTwZEJZZdoB1Y= =mUC9 -END PGP SIGNATURE End Message ---
Processed: severity of 872039 is grave
Processing commands for cont...@bugs.debian.org: > # "serious" is primarily for policy violations, not for functionality bugs > severity 872039 grave Bug #872039 [initscripts] initscripts: umountfs leaves /var mounted (rw) Severity set to 'grave' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 872039: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872039 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: severity of 882009 is grave
Processing commands for cont...@bugs.debian.org:
> severity 882009 grave
Bug #882009 {Done: Thomas Goirand } [src:nova] CVE-2017-16239:
Nova Filter Scheduler bypass through rebuild action
Severity set to 'grave' from 'important'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
882009: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=882009
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: libpmi2-0-dev,libpmix-dev: error when trying to install together: both ship libpmi2.so
Processing control commands: > found -1 2.1.0~rc1-1 Bug #882033 [libpmi2-0-dev,libpmix-dev] libpmi2-0-dev,libpmix-dev: error when trying to install together: both ship libpmi2.so There is no source info for the package 'libpmi2-0-dev' at version '2.1.0~rc1-1' with architecture '' Marked as found in versions pmix/2.1.0~rc1-1. > found -1 17.02.9-1 Bug #882033 [libpmi2-0-dev,libpmix-dev] libpmi2-0-dev,libpmix-dev: error when trying to install together: both ship libpmi2.so There is no source info for the package 'libpmix-dev' at version '17.02.9-1' with architecture '' Marked as found in versions slurm-llnl/17.02.9-1. -- 882033: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=882033 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#882033: libpmi2-0-dev,libpmix-dev: error when trying to install together: both ship libpmi2.so
Package: libpmi2-0-dev,libpmix-dev Severity: serious User: trei...@debian.org Usertags: edos-file-overwrite Control: found -1 2.1.0~rc1-1 Control: found -1 17.02.9-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 libpmix-dev:amd64. Preparing to unpack .../12-libpmix-dev_2.1.0~rc1-1_amd64.deb ... Unpacking libpmix-dev:amd64 (2.1.0~rc1-1) ... dpkg: error processing archive /tmp/apt-dpkg-install-Y3Z8bF/12-libpmix-dev_2.1.0~rc1-1_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/libpmi2.so', which is also in package libpmi2-0-dev 17.02.9-1 Errors were encountered while processing: /tmp/apt-dpkg-install-Y3Z8bF/12-libpmix-dev_2.1.0~rc1-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/lib/x86_64-linux-gnu/libpmi2.so 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 libpmi2-0-dev=17.02.9-1_libpmix-dev=2.1.0~rc1-1.log.gz Description: application/gzip
Bug#882034: ruby-redis-store: CVE-2017-1000248
Source: ruby-redis-store Version: 1.1.6-1 Severity: grave Tags: patch security upstream Forwarded: https://github.com/redis-store/redis-store/issues/289 Control: found -1 1.3.0-1 Hi, the following vulnerability was published for ruby-redis-store. CVE-2017-1000248[0]: | Redis-store <=v1.3.0 allows unsafe objects to be loaded from redis If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2017-1000248 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-1000248 [1] https://github.com/redis-store/redis-store/issues/289 Regards, Salvatore
Processed: ruby-redis-store: CVE-2017-1000248
Processing control commands: > found -1 1.3.0-1 Bug #882034 [src:ruby-redis-store] ruby-redis-store: CVE-2017-1000248 Marked as found in versions ruby-redis-store/1.3.0-1. -- 882034: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=882034 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#881998: marked as done (asc FTBFS with libphysfs-dev 3.0.1-1)
Your message dated Fri, 17 Nov 2017 19:19:25 + with message-id and subject line Bug#881998: fixed in asc 2.6.1.0-3 has caused the Debian Bug report #881998, regarding asc FTBFS with libphysfs-dev 3.0.1-1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 881998: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881998 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: asc Version: 2.6.1.0-2 Severity: serious https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/asc.html ... In file included from physfsrwops.cpp:23:0: physfsrwops.h:42:1: error: '__EXPORT__' does not name a type; did you mean '__FXSR__'? __EXPORT__ SDL_RWops *PHYSFSRWOPS_openRead(const char *fname); ^~ __FXSR__ physfsrwops.h:54:1: error: '__EXPORT__' does not name a type; did you mean '__FXSR__'? __EXPORT__ SDL_RWops *PHYSFSRWOPS_openWrite(const char *fname); ^~ __FXSR__ physfsrwops.h:66:1: error: '__EXPORT__' does not name a type; did you mean '__FXSR__'? __EXPORT__ SDL_RWops *PHYSFSRWOPS_openAppend(const char *fname); ^~ __FXSR__ physfsrwops.h:78:1: error: '__EXPORT__' does not name a type; did you mean '__FXSR__'? __EXPORT__ SDL_RWops *PHYSFSRWOPS_makeRWops(PHYSFS_file *handle); ^~ __FXSR__ --- End Message --- --- Begin Message --- Source: asc Source-Version: 2.6.1.0-3 We believe that the bug you reported is fixed in the latest version of asc, 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 881...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Markus Koschany (supplier of updated asc package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 17 Nov 2017 19:10:22 +0100 Source: asc Binary: asc asc-data Architecture: source Version: 2.6.1.0-3 Distribution: unstable Urgency: medium Maintainer: Debian Games Team Changed-By: Markus Koschany Description: asc- turn-based strategy game asc-data - data files for the Advanced Strategic Command game Closes: 881998 Changes: asc (2.6.1.0-3) unstable; urgency=medium . * Declare compliance with Debian Policy 4.1.1. * Drop deprecated autotools-dev from Build-Depends. * Add libphysfs-3.0.1.patch and fix FTBFS with libphysfs 3.0.1. Thanks to Adrian Bunk for the report. (Closes: #881998) Checksums-Sha1: 96343097a7fdfcd6627a57e6b7e175b9610940cf 2440 asc_2.6.1.0-3.dsc a3c539d6c36c253e0f7423587ce9ee6d329fb5a2 20984 asc_2.6.1.0-3.debian.tar.xz 84c8c855f24c282f83e3a425aa653dfbaf5b5763 11345 asc_2.6.1.0-3_source.buildinfo Checksums-Sha256: 79f5d1f1a0e61c8e9a24bb1a3509ef5b6a6e41537aaa5b25c9ff266b26dd283f 2440 asc_2.6.1.0-3.dsc 9d668c6e4e319a7192c20785f8bb5a6180c94edb263053078db2a1cd9f3da38b 20984 asc_2.6.1.0-3.debian.tar.xz 97ff11db1dd2e175fcdaf7e216d4501e499484c3b7d061fcb9781d37ffa64460 11345 asc_2.6.1.0-3_source.buildinfo Files: d5058a66f29773fc65f1ed80e6455b5e 2440 games optional asc_2.6.1.0-3.dsc 7c67dd4099cd364799bf3b3bab6cf3cc 20984 games optional asc_2.6.1.0-3.debian.tar.xz ac4466901098702f10a3399653fe92bf 11345 games optional asc_2.6.1.0-3_source.buildinfo -BEGIN PGP SIGNATURE- iQKjBAEBCgCNFiEErPPQiO8y7e9qGoNf2a0UuVE7UeQFAloPMDtfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEFD RjNEMDg4RUYzMkVERUY2QTFBODM1RkQ5QUQxNEI5NTEzQjUxRTQPHGFwb0BkZWJp YW4ub3JnAAoJENmtFLlRO1Hkl0QQAJE72PJcQFYAVyN+CkiCJ19yJUU/u4ntpg1B GMvfqjPWTmhfbjP/OOOoSRYWLKpxUe53+rwGJ+kvYsUzrmwCZgexme+iYuceetxW MNOVYdQQjv+83UWzFGCc5oNJUkkRexXWziAZbhyzYTATapfu3BwCiHZmjlr8IVM3 zqWhOH5ACB3To3FFX8asaAvmZ4XLQgnI04vZo694LR58771RIk9mwWuKHyAZR/rE cpncFkbRb4uOf1wazVZ21+2JFUpgSwAZcBmI1f6fYyi3dZFiEC1mnFyUR0rgUpCU B0U8YT7f9NkzSkA9clI2EiEMBus4UgAcQcnXKKDMWvw4o/UhA6XGqxtlhVaF/haM kCTMpWg368PMAKd8oImd4FWD35oyBm/yPOmAp1bKW2ui8f8fl5mXguzqckkllbn1 G6/foAwGN2PmCjvHcVPdwJrgsf78p/tjTgzx03mxPvN6Fp+Xc2azis1oMLxMONNJ 0IMlsm2pHTC2Qbta/ZZvcOn8xG5lGNKzvDyQJ9S7Eo0KmVPff7G3khMj/VXSH7Fc vgX+OM0ThEyYvn0uTuIPm5+2o8V+N+CXcvgPdC6zTxuqCkjEM/xz/9rzbG2julRz Oe1CReb4EDdGlt8TarbuClktwB/rkUm+yQguEmdkgweZgvBGTxGub3TGTX1MZwHB v/P6JR6b =j6t1 -END PGP SIGNATURE End Message ---
Processed: Re: d2x-rebirth: FTBFS: include/physfsrwops.h:47:1: error: unknown type name '__EXPORT__'
Processing control commands: > tags -1 patch Bug #881589 [src:d2x-rebirth] d2x-rebirth: FTBFS: include/physfsrwops.h:47:1: error: unknown type name '__EXPORT__' Added tag(s) patch. -- 881589: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881589 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#881589: d2x-rebirth: FTBFS: include/physfsrwops.h:47:1: error: unknown type name '__EXPORT__'
Control: tags -1 patch Hi, I had to fix the same issue in asc. https://anonscm.debian.org/git/pkg-games/asc.git/tree/debian/patches/libphysfs-3.0.1.patch Regards, Markus signature.asc Description: OpenPGP digital signature
Processed: Re: Bug#873182: please drop transitional package libav-tools
Processing commands for cont...@bugs.debian.org: > severity 873192 serious Bug #873192 [libgfs-dev] libgfs-dev: please switch to ffmpeg Severity set to 'serious' from 'important' > severity 873195 serious Bug #873195 [zoomer] zoomer: please switch to ffmpeg Severity set to 'serious' from 'important' > severity 873191 serious Bug #873191 [ffdiaporama] ffdiaporama: please switch to ffmpeg Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 873191: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873191 873192: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873192 873195: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873195 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#873535: zoomer: should zoomer be removed?
Control: clone -1 -2 Control: retitle -2 RM: zoomer -- RoQA; unmaintained, dead upstream Control: severity -2 normal Control: reassign -2 ftp.debian.org On 2017-08-28 21:01:33, Sebastian Ramacher wrote: > Source: zoomer > Version: 0.1-1.1 > Severity: serious > Tags: sid buster > > zoomer has only ever seen one maintainer upload in 2008 and we had to NMU it > while switching from to ffmpeg to libav in 2013. It seems that we now have to > NMU again to switch back from libav to ffmpeg. Since it's evident that zoomer > is > unmaintained and also appears to be dead upstream, I think it is time to get > it > removed from the archive. > > If you agree, please reassign this bug to ftp.debian.org: No answer, so let's get zoomer removed. Cheers -- Sebastian Ramacher signature.asc Description: PGP signature
Processed: Re: Bug#873535: zoomer: should zoomer be removed?
Processing control commands: > clone -1 -2 Bug #873535 [src:zoomer] zoomer: should zoomer be removed? Bug 873535 cloned as bug 882031 > retitle -2 RM: zoomer -- RoQA; unmaintained, dead upstream Bug #882031 [src:zoomer] zoomer: should zoomer be removed? Changed Bug title to 'RM: zoomer -- RoQA; unmaintained, dead upstream' from 'zoomer: should zoomer be removed?'. > severity -2 normal Bug #882031 [src:zoomer] RM: zoomer -- RoQA; unmaintained, dead upstream Severity set to 'normal' from 'serious' > reassign -2 ftp.debian.org Bug #882031 [src:zoomer] RM: zoomer -- RoQA; unmaintained, dead upstream Bug reassigned from package 'src:zoomer' to 'ftp.debian.org'. No longer marked as found in versions zoomer/0.1-1.1. Ignoring request to alter fixed versions of bug #882031 to the same values previously set -- 873535: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873535 882031: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=882031 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#881643: spacefm not updated after libavfilter update, broken link.
On 13.11.2017 20:58 +0100, Nathael Pajani wrote: Package: spacefm-gtk3 Version: 1.0.5-2 Severity: grave Source: spacefm Tags: sid $ spacefm spacefm: relocation error: /usr/lib/x86_64-linux-gnu/libavfilter.so.6: symbol av_hwframe_map, version LIBAVUTIL_55 not defined in file libavutil.so.55 with link time reference $ Looks like the spacefm shoul dbe re-built using the new version of libavfilter (libavfilter6 is in version 7:3.4-2) and libavutil (libavutil55 in version 10:3.2.2-dmo1), or that libavutil is missing some symbols. $ ls /usr/lib/x86_64-linux-gnu/libavutil.so* /usr/lib/x86_64-linux-gnu/libavutil.so.55 /usr/lib/x86_64-linux-gnu/libavutil.so.55.34.100 $ls /usr/lib/x86_64-linux-gnu/libavfilter.so.6* /usr/lib/x86_64-linux-gnu/libavfilter.so.6 /usr/lib/x86_64-linux-gnu/libavfilter.so.6.107.100 libc6 : Version: 2.24-17 control: severity -1 normal At first please run spacefm based on Debian's official packages libavutil55 in version 10:3.2.2-dmo1 is not from Debian repository. -- .''`. Mateusz Łukasik : :' : https://l0calh0st.pl `. `' Debian Member - mat...@linuxmint.pl `-GPG: D93B 0C12 C8D0 4D7A AFBC FA27 CCD9 1D61 11A0 6851
Bug#881479: marked as done (atop FTBFS with recent debhelper: dh_systemd_enable: Requested unit "atop.service" but it was not found in any package acted on)
Your message dated Fri, 17 Nov 2017 18:19:29 + with message-id and subject line Bug#881479: fixed in atop 2.2.6-5 has caused the Debian Bug report #881479, regarding atop FTBFS with recent debhelper: dh_systemd_enable: Requested unit "atop.service" but it was not found in any package acted on 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.) -- 881479: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881479 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: atop Version: 2.2.6-4 Severity: serious Tags: buster sid https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/atop.html ... dh_systemd_enable atop.service dh_systemd_enable: Requested unit "atop.service" but it was not found in any package acted on. dh_systemd_enable: Could not handle all of the requested services debian/rules:12: recipe for target 'override_dh_systemd_enable' failed make[1]: *** [override_dh_systemd_enable] Error 2 < nthykier> atop => installs the service after calling dh_systemd_enable, which makes dh_systemd_enable unable to figure out what it should do => bug in atop < nthykier> (a --name for atop could probably solve that situation) --- End Message --- --- Begin Message --- Source: atop Source-Version: 2.2.6-5 We believe that the bug you reported is fixed in the latest version of atop, 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 881...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Marc Haber (supplier of updated atop 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: Fri, 17 Nov 2017 18:52:51 +0100 Source: atop Binary: atop Architecture: source Version: 2.2.6-5 Distribution: unstable Urgency: medium Maintainer: Marc Haber Changed-By: Marc Haber Description: atop - Monitor for system resources and process activity Closes: 881479 Changes: atop (2.2.6-5) unstable; urgency=medium . * install systemd unit and initscript in dh_auto_install. Thanks to Adrian Bunk and nthykier (Closes: #881479) * get rid of dh-systemd dependency, bump debhelper dependency * bump debhelper level to 10 Checksums-Sha1: 7da2a21375c6001df136eccbedbea517cada039d 1837 atop_2.2.6-5.dsc f5d9ac0273b8a086441e2c5c8cd5e8703a3ac490 11836 atop_2.2.6-5.debian.tar.xz 8d28c430169cd57611f1c5eed927a35ff8f904ea 5468 atop_2.2.6-5_source.buildinfo Checksums-Sha256: ea0379eb998264edac4c13f6ab28d4a4aaa6bd0dea821cf58c6b81f5efd151bb 1837 atop_2.2.6-5.dsc 0376450376a513a03c26fd9e55a5b8a21559d0a8acd6b97dd8c9815aff7f 11836 atop_2.2.6-5.debian.tar.xz 5c52887d3c3195fff40a1854423586aa69471c0fc938cc50f7602caeb1b8cbce 5468 atop_2.2.6-5_source.buildinfo Files: 9d7f19399268a6da45c3f22134ef14eb 1837 admin optional atop_2.2.6-5.dsc 9b84ee3ac9b6feac7cb4e1902ad51a7a 11836 admin optional atop_2.2.6-5.debian.tar.xz 2023db0c4abc8ce79cd878fbc372642c 5468 admin optional atop_2.2.6-5_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEE6QL5UJ/L0pcuNEbjj3cgEwEyBEIFAloPI5QACgkQj3cgEwEy BEInKA/6A/ciidW9j5GUby8k0QgYThSSdMOBXvpb6FV+xCwaXU5v39hDQxqcVIuG 2392jBH99Wt7inqg9K5dAqfZsvJT0UAPkO55SNFukqRlnuZENUyWiJ6qNQ5BfIgM 2kgcFNp/gPNVrGQrB1nnGNJLI5BdcyGSx1JJd9IVOc7X9agnpe2pzkxAITeJKMbM zRB3bExKOazAq5HVYaa94IRtDDgszJRycrTXcBbzR4HBocjxHS15Q7yJrT4Ox7yx gJcytgjFrH60qlEUpyMdEnY7o5Q7K6Mf+j2L67miAmm2noqXFxnQVSm1TUcFJQ1G p6/csdDZdolKXXD7pOLHVsUMvPhMxoHwhRVaNX6Y2Q5xFjxpQxLUpYyMoAfyaHq2 p4Qk5OddHBWWqfJKLcFv03pBzdY0Zy9bXC756cxZcDjZ5dfHfKI7hKseNdz33Kiy T9XZxfGBVIiEJ3uE+10uOJYFK0a254sUUPHutcadt3hPtt2W8jQAmtuj26IlGCT6 BGVLxBRbZsN4QkmUG8CL+Vx0s8bAtgNTaAoefntORMbNFCM0iiikv81mK/aNPhca wgYViKPkzgkAS6TdVYYzRe+Qjgsqbal3SAeqsINGbLhXcYvM2Ndw5/WHzWFMAbHE 6FH6vTjq4LED/OT25CMwBsefbm/GvL6CIYvU7cvagICHHu78L6Q= =RgMx -END PGP SIGNATURE End Message ---
Bug#882026: qtiplot FTBFS: fatal error: sipAPIqti.h: No such file or directory
Source: qtiplot Version: 0.9.8.9-16 Severity: serious Some recent change in unstable makes qtiplot FTBFS: https://tests.reproducible-builds.org/debian/history/qtiplot.html https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/qtiplot.html ... src/scripting/PythonScripting.cpp:61:10: fatal error: sipAPIqti.h: No such file or directory #include "sipAPIqti.h" ^
Bug#882025: libvirt-php FTBFS: ../tools/generate-api-docs: No such file or directory
Source: libvirt-php Version: 0.5.2~30-g64dca6f-3 Severity: serious Tags: buster sid Some recent change in unstable makes libvirt-php FTBFS: https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/libvirt-php.html ... cd build-7.0 && make -j1 make[2]: Entering directory '/build/1st/libvirt-php-0.5.2~30-g64dca6f/build-7.0' make all-recursive make[3]: Entering directory '/build/1st/libvirt-php-0.5.2~30-g64dca6f/build-7.0' Making all in tools make[4]: Entering directory '/build/1st/libvirt-php-0.5.2~30-g64dca6f/build-7.0/tools' gcc -DHAVE_CONFIG_H -I. -I../../tools -I.. -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -c -o generate-api-docs.o ../../tools/generate-api-docs.c /bin/bash ../libtool --tag=CC --mode=link gcc -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wl,-z,relro -Wl,-z,now -o ../../tools/generate-api-docs generate-api-docs.o libtool: link: gcc -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wl,-z -Wl,relro -Wl,-z -Wl,now -o ../../tools/generate-api-docs generate-api-docs.o ../tools/generate-api-docs ../../src/libvirt-php.c ../docs/api-reference.html.in /bin/bash: ../tools/generate-api-docs: No such file or directory Makefile:614: recipe for target '../../tools/.stamp' failed make[4]: *** [../../tools/.stamp] Error 127
Bug#882023: php-stomp FTBFS with PHP 7.1
Source: php-stomp
Version: 2.0.0+1.0.9-1
Severity: serious
Tags: buster sid
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/php-stomp.html
...
/build/1st/php-stomp-2.0.0+1.0.9/build-7.1/php_stomp.c: In function
'zif_stomp_read_frame':
/build/1st/php-stomp-2.0.0+1.0.9/build-7.1/php_stomp.c:966:9: error:
'zend_fcall_info {aka struct _zend_fcall_info}' has no member named
'function_table'; did you mean 'function_name'?
fci.function_table = &ce->function_table;
^~
function_name
/build/1st/php-stomp-2.0.0+1.0.9/build-7.1/php_stomp.c:967:8: error:
'zend_fcall_info {aka struct _zend_fcall_info}' has no member named
'symbol_table'
fci.symbol_table = NULL;
^
In file included from /usr/include/php/20160303/Zend/zend_globals.h:28:0,
from /usr/include/php/20160303/Zend/zend_compile.h:688,
from /usr/include/php/20160303/Zend/zend_modules.h:26,
from /usr/include/php/20160303/Zend/zend_API.h:27,
from /usr/include/php/20160303/main/php.h:40,
from /build/1st/php-stomp-2.0.0+1.0.9/build-7.1/php_stomp.c:25:
/usr/include/php/20160303/Zend/zend_globals_macros.h:46:33: error:
'zend_executor_globals {aka struct _zend_executor_globals}' has no member named
'scope'
# define EG(v) (executor_globals.v)
^
/build/1st/php-stomp-2.0.0+1.0.9/build-7.1/php_stomp.c:983:25: note: in
expansion of macro 'EG'
fcc.calling_scope = EG(scope);
^~
Makefile:195: recipe for target 'php_stomp.lo' failed
make[2]: *** [php_stomp.lo] Error 1
Bug#874708: marked as done (libanthy0: Package libanthy0 1:0.3-5 missing from unstable repository.)
Your message dated Fri, 17 Nov 2017 19:40:03 +0200 with message-id <20171117174003.gbhw6cqbmzlxbmef@localhost> and subject line Re: Bug#874708: anthy (EUCJP->UTF-8) and *-anthy packages has caused the Debian Bug report #874708, regarding libanthy0: Package libanthy0 1:0.3-5 missing from unstable repository. 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.) -- 874708: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874708 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libanthy0 Version: 1:0.3-5 Severity: important Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * I would like to install ibus-anthy fom the unstable repository. * Pacakge dependecies are preventing me from installing this package. * I am unable to install ibus-anthy. The problem appears to me to be caused by libanthy0 1:0.3-5 is missing from the unstable repository. libanthyinput0 and libanthy0 come from same source package, but libanthy0 is built from an older source package in the unstable repository, and libanthyinput0 breaks this older version of libanthy0. I think if libanthy0 is built with the new source 1:0.3-5 and added to the unstable repository then my problem may be fixed. -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.12.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), LANGUAGE=en_AU:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages libanthy0 depends on: pn anthy-common ii libc6 2.24-17 libanthy0 recommends no packages. libanthy0 suggests no packages. --- End Message --- --- Begin Message --- I'm closing this bug to give anthy a chance to migrate to testing. cu Adrian On Wed, Nov 15, 2017 at 10:20:31PM +0200, Adrian Bunk wrote: > On Tue, Nov 07, 2017 at 11:44:45PM +0900, Osamu Aoki wrote: > >... > > Even these are updated with manual patches, all these updated package > > needs to move together from unstable to testing. > > Not necessarily - the old library will can kept in testing until all > reverse dependencies have migrated. > > > I am not very familiar > > with this ABI breaking library update. We may need to add BREAKS: to > > anthy to ensure this. (I am not sure) That may reqire to upload -7 for > > anthy. > > > > Anyway, these need to be properly coordinated. > >... > > It might be enough to just close this bug - this bug is currently the > main blocker for the testing migration. > > > Osamu > > cu > Adrian--- End Message ---
Bug#881883: marked as done (libnormaliz-dev-common: fails to upgrade from 'testing' - trying to overwrite /usr/include/libnormaliz/HilbertSeries.h)
Your message dated Fri, 17 Nov 2017 17:35:23 + with message-id and subject line Bug#881883: fixed in normaliz 3.4.1+ds-2 has caused the Debian Bug report #881883, regarding libnormaliz-dev-common: fails to upgrade from 'testing' - trying to overwrite /usr/include/libnormaliz/HilbertSeries.h 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.) -- 881883: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881883 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libnormaliz-dev-common Version: 3.4.1+ds-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts 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/ch-relationships.html#s-replaces >From the attached log (scroll to the bottom...): Selecting previously unselected package libnormaliz-dev-common. Preparing to unpack .../libnormaliz-dev-common_3.4.1+ds-1_all.deb ... Unpacking libnormaliz-dev-common (3.4.1+ds-1) ... dpkg: error processing archive /var/cache/apt/archives/libnormaliz-dev-common_3.4.1+ds-1_all.deb (--unpack): trying to overwrite '/usr/include/libnormaliz/HilbertSeries.h', which is also in package libnormaliz0-dev-common 3.1.1+ds-1 Errors were encountered while processing: /var/cache/apt/archives/libnormaliz-dev-common_3.4.1+ds-1_all.deb cheers, Andreas libnormaliz0-dev-common=3.1.1+ds-1_libnormaliz-dev-common=3.4.1+ds-1.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: normaliz Source-Version: 3.4.1+ds-2 We believe that the bug you reported is fixed in the latest version of normaliz, 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 881...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jerome Benoit (supplier of updated normaliz package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 17 Nov 2017 15:07:15 + Source: normaliz Binary: normaliz libnormaliz3 libnormaliz-dev libnormaliz-dev-common normaliz-bin normaliz-doc Architecture: source Version: 3.4.1+ds-2 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers Changed-By: Jerome Benoit Description: libnormaliz-dev - math computing tools for affine monoids, rational polytopes and c libnormaliz-dev-common - math computing tools for affine monoids, rational polytopes and c libnormaliz3 - math computing tools for affine monoids, rational polytopes and c normaliz - math computing tools for affine monoids, rational polytopes and c normaliz-bin - math computing tools for affine monoids, rational polytopes and c normaliz-doc - math computing tools for affine monoids, rational polytopes and c Closes: 881869 881883 Changes: normaliz (3.4.1+ds-2) unstable; urgency=medium . * Debianization: - debian/control: - Breaks+Replaces field, add (Closes: #881883); - debian/patches/*: - d/p/upstream-test-extremely_sensitive_tests-neutralize.patch, introduce and submit (Closes: #881869); - d/p/debianization.patch, refresh. Checksums-Sha1: da507b56087d5049a693bccceeed4ad225829b1b 3078 normaliz_3.4.1+ds-2.dsc 0124cc9064f51c79c6de576467e743a2c24210ca 5308 normaliz_3.4.1+ds-2.debian.tar.xz f28ce53f2b3fa2d8a0efd0ec6269162fc63706f2 6113 normaliz_3.4.1+ds-2_source.buildinfo Checksums-Sha256: 38e5caf365ead46680b1e8125c4af0a08639705fae196811ac3bc944148b1b33 3078 normaliz_3.4.1+ds-2.dsc 8ff408e76da049b6947405fa131e4579ada12972619d8e9d963b8199cfa58fe0 5308 normaliz_3.4.1+ds-2.debian.tar.xz 5d496f45e619469e2096074fca64fcd3ca905c01e7d659e0b08f9c4fc83b3c64 6113 normaliz_3.4.1+ds-2_source.buildinfo Files: 1382f97eb267605ee216499b49c3c139 3078 math optional normaliz_3.4.1+ds-2.dsc 0dbe861d76dc5eb3dc6e640a124f792f 5308 math optional normaliz_3.4.1+ds-2.debian.tar.xz bee8633a420dc9dad41e4c121a8a4d84 6113 math optional normaliz_3.4.1+ds-2_source.buildinfo -BEGIN PGP SIGN
Bug#880883: FTBFS on arm64: test suite times out (on arm-arm-04)
On 12/11/17 15:02, Michael Biebl wrote: > Am 05.11.2017 um 13:14 schrieb Michael Biebl: >> Looking through past build logs, it consistently seems to fail at this >> point: >> >> make[7]: Entering directory >> '/<>/debian/build/deb/tests/refcount' >> make closures objects objects2 properties properties2 properties3 >> properties4 signal1 signal2 signal3 signal4 \ >> > > .. > >> make[8]: Leaving directory >> '/<>/debian/build/deb/tests/refcount' >> make check-TESTS check-local >> make[8]: Entering directory >> '/<>/debian/build/deb/tests/refcount' >> make[9]: Entering directory >> '/<>/debian/build/deb/tests/refcount' >> E: Build killed with signal TERM after 150 minutes of inactivity > I'm not sure if the arm porters already had time to look into this. But > since a week has passed without further feedback and glib2.0 starting to > block other packages, this is another plea for help from the arm porters > regarding this issue. I gave it back again, and it again got picked by arm-arm-04. With the help from jcristau (as I don't have access to that machine) I determined that the build gets killed while running the closures test, which gets executed by is way too slow on that machine (it'd take around 200 minutes to complete it). I'm not sure where it's taking so much time on this machine (can't know without access or some debugging logs) but I wonder if it's on g_closure_ref/unref, which happen quite a lot. Maybe atomic operations are too slow on this hardware? Cheers, Emilio
Bug#881869: marked as done (FTBFS: recipe for target 'test-/5x5PF.diff' failed)
Your message dated Fri, 17 Nov 2017 17:35:23 + with message-id and subject line Bug#881869: fixed in normaliz 3.4.1+ds-2 has caused the Debian Bug report #881869, regarding FTBFS: recipe for target 'test-/5x5PF.diff' failed 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.) -- 881869: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881869 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: normaliz Version: 3.4.1+ds-1 Severity: serious Tags: upstream Justification: fails to build from source (but built successfully in the past) User: debian-powe...@lists.debian.org Usertags: powerpc ppc64 ppc64el Builds of normaliz 3.4 for arm64, ppc64el, s390x, and the non-release architectures powerpc and ppc64 (but for some reason not powerpcspe) have been failing: /<>/normaliz-3.4.1+ds/_build/../test/Makefile.classic:52: recipe for target 'test-/5x5PF.diff' failed I don't know what the diff turned out to read (or even whether it's the same on all of these architectures!), but perhaps you can reproduce the problem on a porter box. Could you please take a look? Thanks! -- Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org) http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu --- End Message --- --- Begin Message --- Source: normaliz Source-Version: 3.4.1+ds-2 We believe that the bug you reported is fixed in the latest version of normaliz, 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 881...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jerome Benoit (supplier of updated normaliz package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 17 Nov 2017 15:07:15 + Source: normaliz Binary: normaliz libnormaliz3 libnormaliz-dev libnormaliz-dev-common normaliz-bin normaliz-doc Architecture: source Version: 3.4.1+ds-2 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers Changed-By: Jerome Benoit Description: libnormaliz-dev - math computing tools for affine monoids, rational polytopes and c libnormaliz-dev-common - math computing tools for affine monoids, rational polytopes and c libnormaliz3 - math computing tools for affine monoids, rational polytopes and c normaliz - math computing tools for affine monoids, rational polytopes and c normaliz-bin - math computing tools for affine monoids, rational polytopes and c normaliz-doc - math computing tools for affine monoids, rational polytopes and c Closes: 881869 881883 Changes: normaliz (3.4.1+ds-2) unstable; urgency=medium . * Debianization: - debian/control: - Breaks+Replaces field, add (Closes: #881883); - debian/patches/*: - d/p/upstream-test-extremely_sensitive_tests-neutralize.patch, introduce and submit (Closes: #881869); - d/p/debianization.patch, refresh. Checksums-Sha1: da507b56087d5049a693bccceeed4ad225829b1b 3078 normaliz_3.4.1+ds-2.dsc 0124cc9064f51c79c6de576467e743a2c24210ca 5308 normaliz_3.4.1+ds-2.debian.tar.xz f28ce53f2b3fa2d8a0efd0ec6269162fc63706f2 6113 normaliz_3.4.1+ds-2_source.buildinfo Checksums-Sha256: 38e5caf365ead46680b1e8125c4af0a08639705fae196811ac3bc944148b1b33 3078 normaliz_3.4.1+ds-2.dsc 8ff408e76da049b6947405fa131e4579ada12972619d8e9d963b8199cfa58fe0 5308 normaliz_3.4.1+ds-2.debian.tar.xz 5d496f45e619469e2096074fca64fcd3ca905c01e7d659e0b08f9c4fc83b3c64 6113 normaliz_3.4.1+ds-2_source.buildinfo Files: 1382f97eb267605ee216499b49c3c139 3078 math optional normaliz_3.4.1+ds-2.dsc 0dbe861d76dc5eb3dc6e640a124f792f 5308 math optional normaliz_3.4.1+ds-2.debian.tar.xz bee8633a420dc9dad41e4c121a8a4d84 6113 math optional normaliz_3.4.1+ds-2_source.buildinfo -BEGIN PGP SIGNATURE- iQRJBAEBCgAzFiEEriiuFXEN/x2H5adiP5IZpn82xosFAloO/T8VHGNhbGN1bHVz QHJlem96ZXIubmV0AAoJED+SGaZ/NsaLIsIgAK0tDyiZGxEWKcYgl3XqvYRl63zq YffAFQQv6v1wiJL5JlkRxAC+AVyIzCQWTnezLFmqZaeltNj0bpO8Ya/7N5mKcAXb Enegw+QZ0zJawYJ0AFCrieu+mKHo2rz5m6icBCZYgAYOtDrjiudp0GF/nSD77SF7 ZDIGOF19i8YRJQxGMYsGFTB2DZhZg0Jswreju14gIBzmQx+ILgdpb3mohLZivpbn n/Tn2HP7F93s6GQj7vEDXwjJHr5GohbeOhCGjkbVV2WuG4DFdwukwKgka4rsWHEE 9KwdB9RIUGvYjRi
Bug#882017: asyncpg FTBFS with postgresql-10 10.1
Source: asyncpg
Version: 0.13.0-1
Severity: serious
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/asyncpg.html
...
=== FAILURES ===
_ TestSettings.test_server_version_01 __
self =
async def test_server_version_01(self):
version = self.con.get_server_version()
version_num = await self.con.fetchval("SELECT current_setting($1)",
'server_version_num', column=0)
ver_maj = int(version_num[:-4])
ver_min = int(version_num[-4:-2])
ver_fix = int(version_num[-2:])
> self.assertEqual(version[:3], (ver_maj, ver_min, ver_fix))
E AssertionError: Tuples differ: (10, 1, 0) != (10, 0, 1)
E
E First differing element 1:
E 1
E 0
E
E - (10, 1, 0)
E + (10, 0, 1)
tests/test_connect.py:47: AssertionError
== 1 tests deselected ==
1 failed, 202 passed, 1 skipped, 1 deselected in 67.91 seconds
E: pybuild pybuild:283: test: plugin distutils failed with: exit code=1: cd
/build/1st/asyncpg-0.13.0/.pybuild/pythonX.Y_3.6/build; python3.6 -m pytest
-k-test_flake8
dh_auto_test: pybuild --test --test-pytest -i python{version} -p 3.6 returned
exit code 13
debian/rules:8: recipe for target 'build' failed
make: *** [build] Error 25
Bug#881857: add CVE
On 11/17/17, 11:48 AM, "Pkg-shibboleth-devel on behalf of Ferenc Wágner" wrote: > Now, this is still ongoing: > https://release.debian.org/transitions/html/auto-xerces-c.html > The upstream fixes for this issue appeared as new patch level releases > for XMLTooling (1.6.2), OpenSAML (2.6.1) and the SP (2.6.1). Shall I > wait for the transition to finish before uploading them? Sorry if I'm misinterpreting, but is this a source level issue or just a question of ABI/build decision? SP 2.6.0/etc. definitely should build against Xerces 3.2, and probably many older SP versions would also. But if you're just referring to what they were built with in Debian packaging cases to date, disregard. -- Scott
Bug#882016: python{,3}-cryptography lost dependencies
Source: python-cryptography
Version: 2.1.3-1
Severity: serious
Control: affects -1 python-cryptography python3-cryptography
Looking at the changelog, it doesn't seem to be intentional
that python{,3}-cryptography lost their cffi dependencies
as well as some other dependencies.
Processed: python{,3}-cryptography lost dependencies
Processing control commands:
> affects -1 python-cryptography python3-cryptography
Bug #882016 [src:python-cryptography] python{,3}-cryptography lost dependencies
Added indication that 882016 affects python-cryptography and
python3-cryptography
--
882016: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=882016
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#881756: Re: Bug#881756: swi-prolog: FTBFS on mips: Build killed with signal TERM
Hi,
On 15/11/17 10:35, Adrian Bunk wrote:
> On Wed, Nov 15, 2017 at 02:30:54PM +0500, Lev Lamberov wrote:
>> Ср 15 ноя 2017 @ 08:06 Adrian Bunk :
>> ...
>>> Same randomness on powerpcspe, and both have it already with 7.6.1+dfsg-1:
>>> https://buildd.debian.org/status/logs.php?pkg=swi-prolog&arch=powerpc
>>> https://buildd.debian.org/status/logs.php?pkg=swi-prolog&arch=powerpcspe
>> ...
>> At least, I cannot think of any other reason that 7.6.1-1
>> was built successfully on mips and 7.6.1-2 failed, where the only one
>> change is disabling Java tests (due to CVE-2017-1000364). I've uploaded
>> 7.6.1-2 on the next day after 7.6.1-1 upload.
>
> you already quoted the reason:
>
>> The main issue
>> seems to be weaker read/write ordering constraints that break our
>> lock-free data structures, resulting in more or less random bugs.
>
> Based on the mips/powerpc/powerpcspe results one could say that there
> is a 50% chance that a build attempt fails.
I had a look at this and indeed the build fails on mips randomly usually
hanging in the test_cgc test (as mentioned earlier).
One thread always hangs in the global_generation function which is only
enabled if ATOMIC_GENERATION_HACK is enabled (only on arches without
64-bit atomics).
Excerpt from pl-inline.h:465
> static inline gen_t
> global_generation(void)
> { gen_t g;
> gen_t last;
>
> do
> { last = GD->_last_generation;
> g = (gen_t)GD->_generation.gen_u<<32 | GD->_generation.gen_l;
> } while ( unlikely(g < last) );
>
> if ( unlikely(last != g) )
> GD->_last_generation = g;
>
> return g;
> }
In the above loop, GD->_generation and GD->_last_generation are not
modified within the loop, nor are they declared volatile. Therefore the
"last" and "g" assignments are invariant and GCC will hoist them out of
the loop (into something like what is shown below). This causes the
hangs on mips if g < last for some reason.
last = GD->_last_generation;
g = (gen_t)GD->_generation.gen_u<<32 | GD->_generation.gen_l;
do {} while (g < last);
As a side note, I also notice GD->_generation is loaded without any
memory barriers on all architectures (pl-incl.h:999) which looks a bit
dodgy (although I don't know if it actually breaks anything).
IMO the best solution is to remove all the ATOMIC_GENERATION_HACK code
and use libatomic, but this will take some porting work because
swi-prolog uses the old __sync primitives everywhere.
I have attached a hack which marks _generation and _last_generation as
volatile. This seems to work but isn't a long term solution.
James
--- a/src/pl-global.h
+++ b/src/pl-global.h
@@ -105,9 +105,9 @@ struct PL_global_data
} signals;
#endif
#ifdef O_LOGICAL_UPDATE
- ggen_t _generation;/* generation of the database */
+ volatile ggen_t _generation;/* generation of the database */
#ifdef ATOMIC_GENERATION_HACK
- gen_t_last_generation; /* see pl-inline.h, global_generation() */
+ volatile gen_t _last_generation; /* see pl-inline.h, global_generation() */
#endif
#endif
signature.asc
Description: OpenPGP digital signature
Bug#870635: mutt package is not using the official mutt tarball
debian-de...@lists.debian.org Bcc: Subject: Re: Bug#870635: mutt package is not using the official mutt tarball Reply-To: In-Reply-To: <2017074105.iz5bje4kgkl3q...@cherubino.dyne.org> CCing -devel because I think this might be of wider interest. On Sat, Nov 11, 2017 at 07:41:05AM +, Antonio Radici wrote: Sorry for the delay, my plan of action is to stop packaging neomutt with this name, I'll create a new neomutt package (TBD by end of the month) and I'll think if there is the need of a transitional package, the problem of a transitional package is that mutt won't be packaged as mutt in stretch. To prevent that from happening we will need two packages (mutt and neomutt) from two different upstream sources. So far the only thing which is certainly going to happen is the creation of the neomutt package, then I could package the newest mutt as 'mutt' and think about whether mutt needs to become a transitional package (which in that case will remove mutt). I think there are a facts you should seriously consider before continuing with this approach. Firstly, the existing package is neomutt, but called mutt. So the existing package users are neomutt users, and the existing reported bugs are bugs in neomutt. (The wisdom of having moved the package *to* neomutt at this point is irrelevant, because it has happened whether we like it or not.) If you are suggesting that the package name "mutt" is going to be real "mutt" in future, then what happens to existing users? What are their expectations? Do you reassign all existing bugs to a new neomutt package name? Do you attempt to triage all bugs to figure out whether they apply to one, the other, or both? Would users who are using neomutt features not find the change to be a regression from their point of view? Secondly, is there a need for both mutt and neomutt in Debian? Our mission is not to package every piece of software on earth, but to build a useful operating system. Is there sufficient distinction between the two, from a user's perspective, that there is a genuine need for both in the archive? (Of course, the distinction is very important for the authors of the software. But that's not the same thing.) For enough users to justify the work? I've been a daily mutt (and now neomutt) user in Debian for nearly 20 years, and I don't think there is. Thirdly, let's look honestly at how well the existing package maintenance is working. This particular issue was raise in late June[1], and you said at the time that'd you have come up with a transition plan within a couple of weeks[2]. For my pet neomutt bug[3] (which coincidentally I reported at around the same time) you expected to have the patch applied shortly, possibly even within a week[4], but it remains unfixed. I am not trying to criticise your personal contributions to Debian. We are all volunteers, and we all do what we can and nobody should expect more from us than we are prepared or able to give. I am extremely grateful for the work you have done and continue to do. But I think it's important to communicate as realistically as possible what we are able to do. I am very guilty of getting this wrong, and over-promising and under-delivering for my own efforts in Debian. I simply wish to point out that the existing Mutt packaging team appears to be stretched. It seems to me that having two mutt packages to manage is only going to make this situation much worse. [1] https://marc.info/?l=mutt-users&m=149886522430053&w=2 [2] https://marc.info/?l=mutt-users&m=149889708628480&w=2 [3] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866366 [4] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866366#24 -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Jonathan Dowland ⢿⡄⠘⠷⠚⠋⠀ https://jmtd.net ⠈⠳⣄ Please do not CC me, I am subscribed to the list.
Bug#881857: add CVE
Salvatore Bonaccorso writes: > Thanks, need to check why my mail for 881857 did not went trough > (since I retitled both with the CVE assignments). I think you used the same bug number in both. Now, this is still ongoing: https://release.debian.org/transitions/html/auto-xerces-c.html The upstream fixes for this issue appeared as new patch level releases for XMLTooling (1.6.2), OpenSAML (2.6.1) and the SP (2.6.1). Shall I wait for the transition to finish before uploading them? -- Thanks, Feri
Bug#881307: agda-stdlib FTBFS: : commitBuffer: invalid argument (invalid character)
Hi,
On Fri, Nov 10, 2017 at 01:18:07AM +0200, Adrian Bunk wrote:
> Source: agda-stdlib
> Version: 0.13-1
> Severity: serious
>
> Some recent change in unstable makes agda-stdlib FTBFS:
>
> https://tests.reproducible-builds.org/debian/history/agda-stdlib.html
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/agda-stdlib.html
>
> ...
>debian/rules override_dh_auto_build
> make[1]: Entering directory '/build/1st/agda-stdlib-0.13'
> ghc --make GenerateEverything.hs
> [1 of 1] Compiling Main ( GenerateEverything.hs,
> GenerateEverything.o )
> Linking GenerateEverything ...
> ./GenerateEverything
> agda +RTS -K1G -RTS -i /build/1st/agda-stdlib-0.13 -i
> /build/1st/agda-stdlib-0.13/src /build/1st/agda-stdlib-0.13/Everything.agda
> Checking Everything (/build/1st/agda-stdlib-0.13/Everything.agda).
> Checking Algebra (/build/1st/agda-stdlib-0.13/src/Algebra.agda).
> Checking Relation.Binary
> (/build/1st/agda-stdlib-0.13/src/Relation/Binary.agda).
>Checking Data.Product (/build/1st/agda-stdlib-0.13/src/Data/Product.agda).
> Checking Function (/build/1st/agda-stdlib-0.13/src/Function.agda).
> Checking Level (/build/1st/agda-stdlib-0.13/src/Level.agda).
> Finished Level.
> Finished Function.
> Checking Relation.Nullary
> (/build/1st/agda-stdlib-0.13/src/Relation/Nullary.agda).
> Checking Data.Empty (/build/1st/agda-stdlib-0.13/src/Data/Empty.agda).
> /build/1st/agda-stdlib-0.13/src/Data/Empty.agda:13,1-31
> The HASKELL pragma has been deprecated. Use
> {-# FOREIGN GHC data AgdaEmpty #-} instead. This will be an error
> in Agda 2.6.
> when scope checking the declaration
> {-# HASKELL
> data AgdaEmpty
> #-}
> /build/1st/agda-stdlib-0.13/src/Data/Empty.agda:14,1-58
> The COMPILED_DATA pragma has been deprecated. Use
> {-# COMPILE GHC /build/1st/agda-stdlib-0.13/src/Relation/Nullary.agda:11,13-23
> : commitBuffer: invalid argument (invalid character)
> debian/rules:13: recipe for target 'override_dh_auto_build' failed
> make[1]: *** [override_dh_auto_build] Error 1
This seems to be related to
https://github.com/commercialhaskell/stack/issues/793 and setting
LC_ALL=C.UTF-8 makes the build continue, but the agda-stdlib is no
longer compatible with present agda and thus fails with a type check
error:
| Checking Data.Nat.LCM (/<>/src/Data/Nat/LCM.agda).
| /<>/src/Data/Nat/LCM.agda:119,1-125,23
| q₁ * q₂ * d′ !=
| proj₁
| (lcm (q₁ * d′) (q₂ * d′)
| | proj₁
|(gcd (q₁ * d′) (q₂ * d′)
| | .Data.Nat.GCD.Bézout.gcd (q₁ * d′) (q₂ * d′) (q₁ * d′ , q₂ * d′)
| ((λ y y>'
| debian/rules:29: recipe for target 'build' failed
| make: *** [build] Error 2
| dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2
I guess we'll need a new upstream release here.
I'm attaching the patch I have, but it doesn't make it build.
Helmut
diff --minimal -Nru agda-stdlib-0.13/debian/changelog
agda-stdlib-0.13/debian/changelog
--- agda-stdlib-0.13/debian/changelog 2017-07-06 11:16:33.0 +0200
+++ agda-stdlib-0.13/debian/changelog 2017-11-17 15:14:14.0 +0100
@@ -1,3 +1,12 @@
+agda-stdlib (0.13-2) UNRELEASED; urgency=medium
+
+ * Team upload.
+ * Address FTBFS: export LC_ALL=C.UTF-8. (Addresses: #881307)
+ * Bump agda-bin Breaks due to agdai incompatibility.
+ * Tighten up agda relation ships to detect incompatibility next time.
+
+ -- Helmut Grohne Fri, 17 Nov 2017 15:14:14 +0100
+
agda-stdlib (0.13-1) unstable; urgency=medium
[ Gianfranco Costamagna ]
diff --minimal -Nru agda-stdlib-0.13/debian/control
agda-stdlib-0.13/debian/control
--- agda-stdlib-0.13/debian/control 2017-07-06 11:16:33.0 +0200
+++ agda-stdlib-0.13/debian/control 2017-11-17 15:14:14.0 +0100
@@ -4,10 +4,10 @@
Maintainer: Iain Lane
Uploaders: Debian Haskell Group
Build-Depends: debhelper (>= 10),
- agda-bin (>= 2.5.1),
- agda-bin (<< 2.6.0),
- libghc-agda-dev (>= 2.5.1),
- libghc-agda-dev (<< 2.6.0),
+ agda-bin (>= 2.5.3),
+ agda-bin (<< 2.5.4~),
+ libghc-agda-dev (>= 2.5.3),
+ libghc-agda-dev (<< 2.5.4~),
libghc-filemanip-dev
Standards-Version: 4.0.0
Vcs-Browser: https://anonscm.debian.org/cgit/collab-maint/agda-stdlib.git
@@ -17,9 +17,9 @@
Package: agda-stdlib
Architecture: all
Depends: ${misc:Depends},
- libghc-agda-dev (>= 2.5.1),
- libghc-agda-dev (<< 2.6.0)
-Breaks: agda-bin (<< 2.5.1)
+ libghc-agda-dev (>= 2.5.3),
+ libghc-agda-dev (<< 2.5.4~)
+Breaks: agda-bin (<< 2.5.3)
Enhances: elpa-agda2-mode
Description: standard library for Agda
Agda is a dependently typed functional programming language: It has inductive
diff --minimal -Nru agda-stdlib-0.13/debian/rules agda-stdlib-0.13/debian/rules
--- agda-stdlib-0.13/debian/rules 2017-07-06 11:16:33.0 +0200
+++ agda-stdlib-0.13/debian/rules 2017-11-17 15:14:14.0
Bug#882011: python-cryptography: no longer depends on cffi-backend, offlineimap fails to start
Package: python-cryptography
Version: 2.1.3-1
Severity: grave
Justification: renders package unusable (I think, please drop severity if not)
I use offlineimap with python-keyring, retrieving my IMAP password from
gnome-keyring. This uses python-secretstorage and python-cryptography
behind the scenes.
I recently upgraded python[3]-cryptography from 1.9-1 to 2.1.3-1. During
this transaction, the python[3]-cffi-backend packages were removed as
"no longer used". This causes a previously-working offlineimap configuration
to fail:
ERROR: While attempting to sync account ''
No module named _cffi_backend
...
File "", line 1, in
File "/usr/lib/python2.7/dist-packages/keyring/core.py", line 41, in
get_password
return _keyring_backend.get_password(service_name, username)
File "/usr/lib/python2.7/dist-packages/keyring/backends/SecretService.py",
line 65, in get_password
return item.get_secret().decode('utf-8')
File "/usr/lib/python2.7/dist-packages/secretstorage/item.py", line 102, in
get_secret
decryptor = Cipher(aes, modes.CBC(aes_iv), default_backend()).decryptor()
File
"/usr/lib/python2.7/dist-packages/cryptography/hazmat/backends/__init__.py",
line 15, in default_backend
from cryptography.hazmat.backends.openssl.backend import backend
File
"/usr/lib/python2.7/dist-packages/cryptography/hazmat/backends/openssl/__init__.py",
line 7, in
from cryptography.hazmat.backends.openssl.backend import backend
File
"/usr/lib/python2.7/dist-packages/cryptography/hazmat/backends/openssl/backend.py",
line 16, in
from cryptography import utils, x509
File "/usr/lib/python2.7/dist-packages/cryptography/x509/__init__.py", line
8, in
from cryptography.x509.base import (
File "/usr/lib/python2.7/dist-packages/cryptography/x509/base.py", line 16,
in
from cryptography.x509.extensions import Extension, ExtensionType
File "/usr/lib/python2.7/dist-packages/cryptography/x509/extensions.py", line
18, in
from cryptography.hazmat.primitives import constant_time, serialization
File
"/usr/lib/python2.7/dist-packages/cryptography/hazmat/primitives/constant_time.py",
line 9, in
from cryptography.hazmat.bindings._constant_time import lib
I've set a release-critical severity to block testing migration, on
the assumption that this breaks all other uses of python-cryptography.
If that isn't true, please drop the severity.
Regards,
smcv
-- System Information:
Debian Release: buster/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'buildd-unstable'), (500,
'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental-debug'), (1,
'buildd-experimental'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.13.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8), LANGUAGE=en_GB:en
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages python-cryptography depends on:
ii libc6 2.24-17
ii libssl1.1 1.1.0g-2
ii python 2.7.14-1
ii python-asn1crypto 0.22.0-1
ii python-idna2.5-1
ii python-six 1.11.0-1
python-cryptography recommends no packages.
Versions of packages python-cryptography suggests:
pn python-cryptography-doc
pn python-cryptography-vectors
-- no debconf information
Bug#881221: marked as done (sdcv FTBFS on big endian: test failures)
Your message dated Fri, 17 Nov 2017 15:36:27 +
with message-id
and subject line Bug#881221: fixed in sdcv 0.5.2-2
has caused the Debian Bug report #881221,
regarding sdcv FTBFS on big endian: 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.)
--
881221: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881221
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sdcv
Version: 0.5.2-1
Severity: serious
https://buildd.debian.org/status/package.php?p=sdcv&suite=sid
...
debian/rules override_dh_auto_test
make[1]: Entering directory '/<>'
mkdir -p tmphome/.stardict/dic
# Exclude json test as it's broken in both bash and dash
export HOME=`pwd`/tmphome/; dh_auto_test -- ARGS+="--output-on-failure"
cd obj-mips-linux-gnu && make -j1 test ARGS\+=--output-on-failure
ARGS\+=-j1
make[2]: Entering directory '/<>/obj-mips-linux-gnu'
Running tests...
/usr/bin/ctest --force-new-ctest-process --output-on-failure -j1
Test project /<>/obj-mips-linux-gnu
Start 1: t_list
1/10 Test #1: t_list ... Passed0.03 sec
Start 2: t_use
2/10 Test #2: t_use Passed0.04 sec
Start 3: t_only_data_dir
3/10 Test #3: t_only_data_dir .. Passed0.03 sec
Start 4: t_synonyms
4/10 Test #4: t_synonyms ... Passed0.07 sec
Start 5: t_json
5/10 Test #5: t_json ...***Failed0.10 sec
sdcv: /<>/src/stardict_lib.cpp:542: const gchar*
{anonymous}::OffsetIndex::read_first_on_page_key(glong): Assertion `(nitems ==
1)' failed.
Aborted
expected [
{
"dict": "Test synonyms",
"word": "test",
"definition": "
result of test"
}
] but got
Start 6: t_exact
6/10 Test #6: t_exact .. Passed0.05 sec
Start 7: t_interactive
7/10 Test #7: t_interactive Passed1.01 sec
Start 8: t_utf8output
8/10 Test #8: t_utf8output . Passed0.02 sec
Start 9: t_utf8input
9/10 Test #9: t_utf8input ..***Failed0.03 sec
Aborted
/<>/tests/t_utf8input: empty results of search: test failed
Start 10: t_datadir
10/10 Test #10: t_datadir Passed0.03 sec
80% tests passed, 2 tests failed out of 10
Total Test time (real) = 1.43 sec
The following tests FAILED:
5 - t_json (Failed)
9 - t_utf8input (Failed)
Errors while running CTest
Makefile:110: recipe for target 'test' failed
make[2]: *** [test] Error 8
make[2]: Leaving directory '/<>/obj-mips-linux-gnu'
dh_auto_test: cd obj-mips-linux-gnu && make -j1 test ARGS\+=--output-on-failure
ARGS\+=-j1 returned exit code 2
debian/rules:15: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 2
--- End Message ---
--- Begin Message ---
Source: sdcv
Source-Version: 0.5.2-2
We believe that the bug you reported is fixed in the latest version of
sdcv, 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 881...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Michal Čihař (supplier of updated sdcv 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: Fri, 17 Nov 2017 15:58:22 +0100
Source: sdcv
Binary: sdcv
Architecture: source
Version: 0.5.2-2
Distribution: unstable
Urgency: medium
Maintainer: Michal Čihař
Changed-By: Michal Čihař
Description:
sdcv - StarDict Console Version
Closes: 881221
Changes:
sdcv (0.5.2-2) unstable; urgency=medium
.
* Add patch to fix FTBFS on big endian machines (Closes: #881221).
Checksums-Sha1:
ae89aa1a36ff88988a689c2d9c98f188c6af9182 2045 sdcv_0.5.2-2.dsc
667e5a38e63f8b8a492ba215296c9ad43d627f5e 5500 sdcv_0.5.2-2.debian.tar.xz
dbac2a395268ed6f83212e109a93407f990496be 7507 sdcv_0.5.2-2_amd64.buildinfo
Checksums-Sha256:
8c28a1708d9cb7d5a75ed6caa89ceb18d6aade96fee612bf5e8aaeddb31994db 2045
sdcv_0.5.2-2.dsc
d835f7f68ac5fc66a3753a6a22e466bea6d07891fda1040f6dec3293e426990e 5500
sdcv_0.5.2-2.debian.tar.xz
c7f8983e7b216f72fe6b0c3ab0060e98aa748efa519c2054def9f466f
Bug#881967: marked as done (libopenmpi3: ships libpmix.so.* which has a different SOVERSION than all other libs)
Your message dated Fri, 17 Nov 2017 15:35:40 + with message-id and subject line Bug#881967: fixed in openmpi 3.0.0-2 has caused the Debian Bug report #881967, regarding libopenmpi3: ships libpmix.so.* which has a different SOVERSION than all other libs 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.) -- 881967: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881967 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libopenmpi3 Version: 3.0.0-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'sid' to 'experimental'. It installed fine in 'sid', then the upgrade to 'experimental' 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/ch-relationships.html#s-replaces >From the attached log (scroll to the bottom...): Selecting previously unselected package libopenmpi3:amd64. Preparing to unpack .../9-libopenmpi3_3.0.0-1_amd64.deb ... Unpacking libopenmpi3:amd64 (3.0.0-1) ... dpkg: error processing archive /tmp/apt-dpkg-install-EFFXvG/9-libopenmpi3_3.0.0-1_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/libpmix.so.2', which is also in package libpmix2:amd64 2.0.1-1 Errors were encountered while processing: /tmp/apt-dpkg-install-EFFXvG/9-libopenmpi3_3.0.0-1_amd64.deb Given that libpmix.so.2 has SOVERSION 2, but all other libraries in libopenmpi3 have SOVERSION 40, this should be in a separate package as in sid. cheers, Andreas libpmix2=2.0.1-1_libopenmpi3=3.0.0-1.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: openmpi Source-Version: 3.0.0-2 We believe that the bug you reported is fixed in the latest version of openmpi, 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 881...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Alastair McKinstry (supplier of updated openmpi 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: Fri, 17 Nov 2017 14:56:53 + Source: openmpi Binary: openmpi-bin libopenmpi-dev libopenmpi3 openmpi-common openmpi-doc Architecture: source amd64 all Version: 3.0.0-2 Distribution: experimental Urgency: medium Maintainer: Alastair McKinstry Changed-By: Alastair McKinstry Description: libopenmpi-dev - high performance message passing library -- header files libopenmpi3 - high performance message passing library -- shared library openmpi-bin - high performance message passing library -- binaries openmpi-common - high performance message passing library -- common files openmpi-doc - high performance message passing library -- man pages Closes: 881967 Changes: openmpi (3.0.0-2) experimental; urgency=medium . * Build against external pmix. Closes: #881967 * Standatds-Version: 4.1.1 * Change Priority: extra to Priority: optional * Fix for Hurd FTBFS. Checksums-Sha1: a09c43d320f7dcf13c920425f6ae7a6ce0d63e86 2652 openmpi_3.0.0-2.dsc c99379a91fa85b4d7862edd22ebfec40f7e3509f 60112 openmpi_3.0.0-2.debian.tar.xz 2d89713aacea2fb38d4151e96e6feb3b584e1063 27208 libopenmpi-dev-dbgsym_3.0.0-2_amd64.deb 81d51a1da33c131812f6496854739625b3ba3816 965908 libopenmpi-dev_3.0.0-2_amd64.deb 167ff3d794a10ebd9810b0cdb036ac6b7a508c6f 26960028 libopenmpi3-dbgsym_3.0.0-2_amd64.deb 4fca80fb48fda6d9315bd30cae4bbc1fae835f88 2043260 libopenmpi3_3.0.0-2_amd64.deb a25ccad3a5335aecea01f29093182509762309d4 210004 openmpi-bin-dbgsym_3.0.0-2_amd64.deb 5f321bde554caf6341eead70e501ed8214193910 179584 openmpi-bin_3.0.0-2_amd64.deb 3b5125d87818a33dab59283ccbad38938a02e85f 157868 openmpi-common_3.0.0-2_all.deb 67db356992b5a815fd6f9b0e127a85c2d130 755360 openmpi-doc_3.0.0-2_all.deb f37a4cca16e46ecbb2ec3f7b60fde503c8db30e5 13882 openmpi_3.0.0-2_amd64.buildinfo Checksums-Sha256: ed56beccbf07c491c7460e5b8dda38ac2213d037a15b13d9012445209a6a00e0 2652 openmpi_3.0.0-2.dsc 9c5d8a2d0a6e914ea060974552a3cbc20484297d6ac889584d6f057a5c7cb477 60112 openmpi_3.0.0-2.debian.tar.xz b549cf3dba84be22791b81
Bug#882002: marked as done (gpaste FTBFS with appstream-glib 0.7.4-1)
Your message dated Fri, 17 Nov 2017 15:05:08 + with message-id and subject line Bug#882002: fixed in gpaste 3.26.0-4 has caused the Debian Bug report #882002, regarding gpaste FTBFS with appstream-glib 0.7.4-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.) -- 882002: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=882002 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gpaste Version: 3.26.0-3 Severity: serious Tags: patch https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/gpaste.html ... dh_install dh_install: Cannot find (any matches for) "usr/share/appdata/org.gnome.GPaste.Ui.appdata.xml" (tried in ., debian/tmp) dh_install: gpaste missing files: usr/share/appdata/org.gnome.GPaste.Ui.appdata.xml dh_install: missing files, aborting debian/rules:7: recipe for target 'binary' failed make: *** [binary] Error 25 Matthias Klumpp already pushed the fix to the collab-maint git. --- End Message --- --- Begin Message --- Source: gpaste Source-Version: 3.26.0-4 We believe that the bug you reported is fixed in the latest version of gpaste, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 882...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jérémy Lal (supplier of updated gpaste package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 17 Nov 2017 15:32:21 +0100 Source: gpaste Binary: gpaste libgpaste9 libgpaste-common libgpaste-dev gir1.2-gpaste-1.0 gnome-shell-extensions-gpaste Architecture: source Version: 3.26.0-4 Distribution: unstable Urgency: medium Maintainer: Jérémy Lal Changed-By: Jérémy Lal Description: gir1.2-gpaste-1.0 - GObject introspection data for the libgpaste6 library gnome-shell-extensions-gpaste - GPaste extension for GNOME Shell gpaste - Clipboard management system for GNOME libgpaste-common - Clipboard management system for GNOME - shared files libgpaste-dev - Clipboard management system for GNOME - development files libgpaste9 - Clipboard management system for GNOME - library Closes: 882002 Changes: gpaste (3.26.0-4) unstable; urgency=medium . [ Matthias Klumpp ] * Fix metainfo install location (Closes: #882002) Checksums-Sha1: 6ee011d31147c61b48eaff8cd9c4fc66d25cfa1b 2580 gpaste_3.26.0-4.dsc 9f46c7568147632edeb5ae0b1a337f22e527f878 6528 gpaste_3.26.0-4.debian.tar.xz b6e5eb949aa621412f01a18011dcd342ddab18e9 16808 gpaste_3.26.0-4_source.buildinfo Checksums-Sha256: 9263301cf0f8be9d113632656628699a287bdc6e8c85447e684c72c4b1e0175f 2580 gpaste_3.26.0-4.dsc 24cf85259c52476c300872de22dfa25950d5149c328960e3b8ba2f62e80fa2b8 6528 gpaste_3.26.0-4.debian.tar.xz 084f27c56f07d8228ac598b155b4772a725eeec01700147f68f63a6d2d082f7c 16808 gpaste_3.26.0-4_source.buildinfo Files: 27628f1d8932a997e8dc4cd41ea85f14 2580 gnome optional gpaste_3.26.0-4.dsc 73d2aefe02079241c6e996086060df9e 6528 gnome optional gpaste_3.26.0-4.debian.tar.xz 036d4ff5cc5688e8f25a69dff11e4495 16808 gnome optional gpaste_3.26.0-4_source.buildinfo -BEGIN PGP SIGNATURE- iQJGBAEBCgAwFiEEA8Tnq7iA9SQwbkgVZhHAXt0583QFAloO8xISHGthcG91ZXJA bWVsaXgub3JnAAoJEGYRwF7dOfN0o+MQALrHu8i3nADeXZspMTgBRHWVrne/8kXL nyYnwBrblxyI1FmsxIZVO9BMrSqluFoCBd0Si+BkGvMuSRqlHsUHA6YTwqE5NtU3 dG51q04YVjEvBju3WCRvOsPLTc/8z9l7adons0QVpvW4XzTVqsfycSY1vVBcj9qV 9e+MeC61TrYvmdeTlUD8yqapOGxbRE9nIfkcBvtSurs1hRCS3PT/BebBJzfv1cbg TVh8iyMePtsRpTfHrBJCsk8kjwmaJD1Rxt9kcuGFJVNcldX50OC8YUve0KFPKZTk oGble2ZJ0+HawSd6MAemO6+oHep3zbCDYoBc4TjKsi4rZmYVNYmQLXuoHnVtt158 kDGWBCmn3OBpe1AbcKTXMAYx8iX9TDid+oc416qWhCwuJ0WdUK7XdPkE9hVpjU3g KwfAbY5Du66w3UrkJJLa/nq2k08Q4gHAL0tlO8owT/g4uwJc23GQBcHmbnmeX03K MXm5F8vBOpxbsV+ZSFyQ+vYS4PNnZALzlkYj0I0Gs2MQuUhC2E8welqL1DxWFHRL oa2/91O+0gESvuaA6VUHEE6MjnPvc2ISYvjbbF50zjxR1zvV/pwvhK+113cIqLV8 IfPALZqblf10EOg6Pdq+cfNATJMaiwRpzwzPcWkYh8yc5x/ZA0MwYvLNAAzWXdJ1 tD+/C9CZ0l4Q =1rHA -END PGP SIGNATURE End Message ---
Bug#882004: marked as done (atomix FTBFS with appstream-glib 0.7.4-1)
Your message dated Fri, 17 Nov 2017 15:04:41 + with message-id and subject line Bug#882004: fixed in atomix 3.22.0-2 has caused the Debian Bug report #882004, regarding atomix FTBFS with appstream-glib 0.7.4-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.) -- 882004: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=882004 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: atomix Version: 3.22.0-1 Severity: serious Tags: buster sid https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/atomix.html ... debian/rules override_dh_install make[1]: Entering directory '/build/1st/atomix-3.22.0' dh_install --fail-missing dh_install: Please use dh_missing --list-missing/--fail-missing instead dh_install: This feature will be removed in compat 12. dh_install: Cannot find (any matches for) "usr/share/games/appdata" (tried in ., debian/tmp) dh_install: atomix-data missing files: usr/share/games/appdata dh_install: missing files, aborting debian/rules:19: recipe for target 'override_dh_install' failed make[1]: *** [override_dh_install] Error 25 See also the corresponding lintian warning. --- End Message --- --- Begin Message --- Source: atomix Source-Version: 3.22.0-2 We believe that the bug you reported is fixed in the latest version of atomix, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 882...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Markus Koschany (supplier of updated atomix package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 17 Nov 2017 15:28:42 +0100 Source: atomix Binary: atomix atomix-data Architecture: source Version: 3.22.0-2 Distribution: unstable Urgency: medium Maintainer: Debian Games Team Changed-By: Markus Koschany Description: atomix - puzzle game for building molecules out of separate atoms atomix-data - puzzle game for building molecules out of separate atoms -- data Closes: 882004 Changes: atomix (3.22.0-2) unstable; urgency=medium . * Declare compliance with Debian Policy 4.1.1. * Use dh_missing override instead of dh_install. * d/copyright: Use https for Format field. * Drop deprecated menu file and xpm icon. * Install metainfo directory instead of appdata. This was apparently changed in appstream-glib 0.7.4-1. Thanks to Adrian Bunk for the report. (Closes: #882004) Checksums-Sha1: 2b6fe9bc432057aa3e04c8dce1f3c0929ff00d95 2191 atomix_3.22.0-2.dsc 1b3940df7cb9193402913d27871445edc5adb792 9024 atomix_3.22.0-2.debian.tar.xz dbcd53ef8cb81c02868b972e07a65f4883c1f699 14883 atomix_3.22.0-2_amd64.buildinfo Checksums-Sha256: 7f4e7372be400459e1a1c0c666dc609b99fd1140a1329a85dad5ebf5a8ee092a 2191 atomix_3.22.0-2.dsc cd9cf90c797e620720afce0b6ddce0bab8a03c5d23acd2310d5b3315c2ba998a 9024 atomix_3.22.0-2.debian.tar.xz a0ea9a51a3f6169e1606759cbb7c85abafbed95e75359c60993b95f698df8d06 14883 atomix_3.22.0-2_amd64.buildinfo Files: 84eb2ff814dca097f5ba49ca21b53914 2191 games optional atomix_3.22.0-2.dsc 01de8795089a1c31a09ead87d04fadbb 9024 games optional atomix_3.22.0-2.debian.tar.xz cf4a169e5a9dec14942571f9357194fb 14883 games optional atomix_3.22.0-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQKjBAEBCgCNFiEErPPQiO8y7e9qGoNf2a0UuVE7UeQFAloO9T5fFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEFD RjNEMDg4RUYzMkVERUY2QTFBODM1RkQ5QUQxNEI5NTEzQjUxRTQPHGFwb0BkZWJp YW4ub3JnAAoJENmtFLlRO1HktacP/1YwmhBCLv3Vj3tlxtyt2LCw4wOpYawdXiSQ 1+q8TuO4paiYf9IUg7Zl2vgLj/qhKbU8tscOJzVEYHFSzxREwqlMh4bKMmEpxuB4 lkA4MUGNJxEDTb7/LFRqzd0YJzAYnDRmhEsg3EZuGKGjC4yhKpvle95H+o3UYKEr 1rMOa1W7SkMNCXoT1p5kl2JeXBeYdaU3mPp2SL0cRgDMFdZUNzMsFPy5ZcWR4aG6 r50nHOAKG+OHIcWYIHRNj8ULWGH0U5vvSn5Gc9fjUnvqsq33dx11QCHvsEds4rmD eLlPGcRSKr0WK5bW10Mk7sNwSjIPdq+lG/XsQxmipwyH9h3mi55Dx+07uDv4637c Ohp7nlp/kvT8NKv2Lb19xHOhIScXLET0lz0TA280Me82J7iQnPnr4TFJhfkJBkHo sxmjytQJNG8FUkHj7tlg9m+T4cZSUT2vAuusXA2XieuCy+JVT8hmpCnDHhV61aMq raQJ6K2TB2qp5X+OF+BGsVyO6XI7IuhVeZ3FNlt6o8HZ3pLf8jKfe0Q209uSit0r gQA0hLQBWotB6nuAqArRCxzksY1D7r7pvYF7+hvYh2zCP1kDCkEZVExbRmMHZGse gTUb/WzhySV8jbkle5GJsQU8aB2l1TMBokF73GNyGdalbfhKBuHSwKnjr4MZZjvq PwmPTPyB =9DK/ -EN
Bug#882005: gnome-shell-pomodoro FTBFS with appstream-glib 0.7.4-1
Source: gnome-shell-pomodoro Version: 0.13.3-1 Severity: serious https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/gnome-shell-pomodoro.html ... dh_install --fail-missing dh_install: Please use dh_missing --list-missing/--fail-missing instead dh_install: This feature will be removed in compat 12. dh_install: Cannot find (any matches for) "usr/share/appdata/org.gnome.Pomodoro.appdata.xml" (tried in ., debian/tmp) dh_install: gnome-shell-pomodoro-data missing files: usr/share/appdata/org.gnome.Pomodoro.appdata.xml dh_install: missing files, aborting debian/rules:20: recipe for target 'override_dh_install' failed make[1]: *** [override_dh_install] Error 25 The AppStream XML files should be placed in /usr/share/metainfo/, not /usr/share/appdata/. Refer to https://wiki.debian.org/AppStream/Guidelines for details.
Bug#882004: atomix FTBFS with appstream-glib 0.7.4-1
Source: atomix Version: 3.22.0-1 Severity: serious Tags: buster sid https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/atomix.html ... debian/rules override_dh_install make[1]: Entering directory '/build/1st/atomix-3.22.0' dh_install --fail-missing dh_install: Please use dh_missing --list-missing/--fail-missing instead dh_install: This feature will be removed in compat 12. dh_install: Cannot find (any matches for) "usr/share/games/appdata" (tried in ., debian/tmp) dh_install: atomix-data missing files: usr/share/games/appdata dh_install: missing files, aborting debian/rules:19: recipe for target 'override_dh_install' failed make[1]: *** [override_dh_install] Error 25 See also the corresponding lintian warning.
Bug#880704: bumblebee-nvidia: Upgrading mesa and nvidia drivers with bumblebee-nvidia installed breaks the desktop
On Fri, 2017-11-17 at 07:47 -0500, John M. wrote: > On Sun, 2017-11-05 at 17:35 +, Luca Boccassi wrote: > > On Fri, 2017-11-03 at 19:41 -0500, JWM wrote: > > > Package: bumblebee-nvidia > > > Version: 3.2.1-16 > > > Severity: grave > > > Justification: renders package unusable > > > > > > Dear Maintainer, > > > > > > My system is a Thinkpad T440p, with both an Intel and an NVIDIA > > > Optimus cards. > > > On Wednesday, upgrading both the Mesa libraries and the NVIDIA > > > driver > > > broke the > > > desktop ---i.e., after reboot, the GDM target never showed up due > > > to > > > a Clutter > > > error. > > > > > > Synaptic's history shows the following as > > > installed/upgraded/removed > > > on that > > > day: > > > > > > - > > > --- > > > Commit Log for Wed Nov 1 08:23:33 2017 > > > > > > > > > Removed the following packages: > > > libegl1-glvnd-nvidia > > > libegl1-mesa-dev > > > libgl1-mesa-glx:i386 > > > libgtk-3-dev > > > primus > > > primus-libs-ia32:i386 > > > primus-libs:i386 > > > > > > Upgraded the following packages: > > > debconf (1.5.63) to 1.5.64 > > > debconf-i18n (1.5.63) to 1.5.64 > > > eog-plugin-map (3.25.92-1) to 3.26.1-1 > > > epiphany-browser (3.24.3-1) to 3.26.1-1 > > > epiphany-browser-data (3.24.3-1) to 3.26.1-1 > > > giada (0.14.1~dfsg1-1) to 0.14.3~dfsg1-1 > > > gir1.2-javascriptcoregtk-4.0 (2.16.6-1) to 2.18.1-1 > > > gir1.2-webkit2-4.0 (2.16.6-1) to 2.18.1-1 > > > gnome-maps (3.25.91-1) to 3.26.1-1 > > > gnome-session (3.24.1-2) to 3.26.1-1 > > > gnome-session-bin (3.24.1-2) to 3.26.1-1 > > > gnome-session-common (3.24.1-2) to 3.26.1-1 > > > gnome-software (3.22.5-1) to 3.26.1-2 > > > gnome-software-common (3.22.5-1) to 3.26.1-2 > > > gnome-software-plugin-flatpak (3.22.5-1) to 3.26.1-2 > > > gstreamer1.0-plugins-bad (1.12.2-1+b1) to 1.12.3-2 > > > libegl-nvidia0 (375.82-5) to 375.82-7 > > > libegl1-mesa (13.0.6-1+b2) to 17.2.3-1 > > > libgbm1 (13.0.6-1+b2) to 17.2.3-1 > > > libgl1-glvnd-nvidia-glx (375.82-5) to 375.82-7 > > > libgl1-mesa-dri (13.0.6-1+b2) to 17.2.3-1 > > > libgl1-mesa-dri:i386 (13.0.6-1+b2) to 17.2.3-1 > > > libgl1-mesa-glx (13.0.6-1+b2) to 17.2.3-1 > > > libgl1-nvidia-glvnd-glx (375.82-5) to 375.82-7 > > > libglapi-mesa (13.0.6-1+b2) to 17.2.3-1 > > > libglapi-mesa:i386 (13.0.6-1+b2) to 17.2.3-1 > > > libgles-nvidia1 (375.82-5) to 375.82-7 > > > libgles-nvidia2 (375.82-5) to 375.82-7 > > > libgles1-glvnd-nvidia (375.82-5) to 375.82-7 > > > libgles1-nvidia (375.82-5) to 375.82-7 > > > libgles2-glvnd-nvidia (375.82-5) to 375.82-7 > > > libgles2-mesa (13.0.6-1+b2) to 17.2.3-1 > > > libgles2-nvidia (375.82-5) to 375.82-7 > > > libglx-nvidia0 (375.82-5) to 375.82-7 > > > libglx0-glvnd-nvidia (375.82-5) to 375.82-7 > > > libgstreamer-plugins-bad1.0-0 (1.12.2-1+b1) to 1.12.3-2 > > > libharfbuzz-dev (1.5.1-1) to 1.6.2-1 > > > libharfbuzz-gobject0 (1.5.1-1) to 1.6.2-1 > > > libharfbuzz-icu0 (1.5.1-1) to 1.6.2-1 > > > libharfbuzz0b (1.5.1-1) to 1.6.2-1 > > > libjavascriptcoregtk-4.0-18 (2.16.6-1) to 2.18.1-1 > > > libnetcdf-c++4 (4.2-7) to 4.2-7+b1 > > > libnvidia-cfg1 (375.82-5) to 375.82-7 > > > libnvidia-eglcore (375.82-5) to 375.82-7 > > > libnvidia-glcore (375.82-5) to 375.82-7 > > > libnvidia-ml1 (375.82-5) to 375.82-7 > > > libosmesa6 (13.0.6-1+b2) to 17.2.3-1 > > > libwayland-egl1-mesa (13.0.6-1+b2) to 17.2.3-1 > > > libwebkit2gtk-4.0-37 (2.16.6-1) to 2.18.1-1 > > > libwebkit2gtk-4.0-37-gtk2 (2.16.6-1) to 2.18.1-1 > > > libxatracker2 (13.0.6-1+b2) to 17.2.3-1 > > > mesa-vdpau-drivers (13.0.6-1+b2) to 17.2.3-1 > > > netcdf-bin (1:4.4.1.1-2) to 1:4.5.0-1 > > > nvidia-alternative (375.82-5) to 375.82-7 > > > nvidia-driver (375.82-5) to 375.82-7 > > > nvidia-driver-bin (375.82-5) to 375.82-7 > > > nvidia-driver-libs (375.82-5) to 375.82-7 > > > nvidia-egl-icd (375.82-5) to 375.82-7 > > > nvidia-kernel-support (375.82-5) to 375.82-7 > > > nvidia-smi (375.82-5) to 375.82-7 > > > nvidia-vdpau-driver (375.82-5) to 375.82-7 > > > nvidia-vulkan-icd (375.82-5) to 375.82-7 > > > primus-libs (0~20150328-4) to 0~20150328-5 > > > xserver-xorg-video-nvidia (375.82-5) to 375.82-7 > > > xwayland (2:1.19.3-2) to 2:1.19.5-1 > > > > > > Installed the following packages: > > > gir1.2-harfbuzz-0.0 (1.6.2-1) > > > libegl1 (0.2.999+git20170802-5) > > > libfwupd2 (1.0.0-4) > > > libglvnd-core-dev (0.2.999+git20170802-5) > > > libglvnd0:i386 (0.2.999+git20170802-5) > > > libglx-mesa0 (17.2.3-1) > > > libglx-mesa0:i386 (17.2.3-1) > > > libllvm5.0 (1:5.0~+rc2-1) > > > libllvm5.0:i386 (1:5.0~+rc2-1) > > > libnetcdf13 (1:4.5.0-1) > > > librtmidi4 (3.0.0~ds1-2) > > > libxcb-xfixes0:i386 (1.12-1) > > > python3-debconf (1.5.64) > > > - > > > --- > > > > > > > > > > > > In order to solved the issue, I uninstalled all the NVIDIA- > > > related > > > packages, > > > reinstalled GDM and blacklisted nouveau. > > > > > > After that, I tried installing bu
Bug#880704: marked as done (bumblebee-nvidia: Upgrading mesa and nvidia drivers with bumblebee-nvidia installed breaks the desktop)
Your message dated Fri, 17 Nov 2017 14:12:35 + with message-id <1510927955.11864.9.ca...@debian.org> and subject line Re: Bug#880704: bumblebee-nvidia: Upgrading mesa and nvidia drivers with bumblebee-nvidia installed breaks the desktop has caused the Debian Bug report #880704, regarding bumblebee-nvidia: Upgrading mesa and nvidia drivers with bumblebee-nvidia installed breaks the desktop 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.) -- 880704: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=880704 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: bumblebee-nvidia Version: 3.2.1-16 Severity: grave Justification: renders package unusable Dear Maintainer, My system is a Thinkpad T440p, with both an Intel and an NVIDIA Optimus cards. On Wednesday, upgrading both the Mesa libraries and the NVIDIA driver broke the desktop ---i.e., after reboot, the GDM target never showed up due to a Clutter error. Synaptic's history shows the following as installed/upgraded/removed on that day: Commit Log for Wed Nov 1 08:23:33 2017 Removed the following packages: libegl1-glvnd-nvidia libegl1-mesa-dev libgl1-mesa-glx:i386 libgtk-3-dev primus primus-libs-ia32:i386 primus-libs:i386 Upgraded the following packages: debconf (1.5.63) to 1.5.64 debconf-i18n (1.5.63) to 1.5.64 eog-plugin-map (3.25.92-1) to 3.26.1-1 epiphany-browser (3.24.3-1) to 3.26.1-1 epiphany-browser-data (3.24.3-1) to 3.26.1-1 giada (0.14.1~dfsg1-1) to 0.14.3~dfsg1-1 gir1.2-javascriptcoregtk-4.0 (2.16.6-1) to 2.18.1-1 gir1.2-webkit2-4.0 (2.16.6-1) to 2.18.1-1 gnome-maps (3.25.91-1) to 3.26.1-1 gnome-session (3.24.1-2) to 3.26.1-1 gnome-session-bin (3.24.1-2) to 3.26.1-1 gnome-session-common (3.24.1-2) to 3.26.1-1 gnome-software (3.22.5-1) to 3.26.1-2 gnome-software-common (3.22.5-1) to 3.26.1-2 gnome-software-plugin-flatpak (3.22.5-1) to 3.26.1-2 gstreamer1.0-plugins-bad (1.12.2-1+b1) to 1.12.3-2 libegl-nvidia0 (375.82-5) to 375.82-7 libegl1-mesa (13.0.6-1+b2) to 17.2.3-1 libgbm1 (13.0.6-1+b2) to 17.2.3-1 libgl1-glvnd-nvidia-glx (375.82-5) to 375.82-7 libgl1-mesa-dri (13.0.6-1+b2) to 17.2.3-1 libgl1-mesa-dri:i386 (13.0.6-1+b2) to 17.2.3-1 libgl1-mesa-glx (13.0.6-1+b2) to 17.2.3-1 libgl1-nvidia-glvnd-glx (375.82-5) to 375.82-7 libglapi-mesa (13.0.6-1+b2) to 17.2.3-1 libglapi-mesa:i386 (13.0.6-1+b2) to 17.2.3-1 libgles-nvidia1 (375.82-5) to 375.82-7 libgles-nvidia2 (375.82-5) to 375.82-7 libgles1-glvnd-nvidia (375.82-5) to 375.82-7 libgles1-nvidia (375.82-5) to 375.82-7 libgles2-glvnd-nvidia (375.82-5) to 375.82-7 libgles2-mesa (13.0.6-1+b2) to 17.2.3-1 libgles2-nvidia (375.82-5) to 375.82-7 libglx-nvidia0 (375.82-5) to 375.82-7 libglx0-glvnd-nvidia (375.82-5) to 375.82-7 libgstreamer-plugins-bad1.0-0 (1.12.2-1+b1) to 1.12.3-2 libharfbuzz-dev (1.5.1-1) to 1.6.2-1 libharfbuzz-gobject0 (1.5.1-1) to 1.6.2-1 libharfbuzz-icu0 (1.5.1-1) to 1.6.2-1 libharfbuzz0b (1.5.1-1) to 1.6.2-1 libjavascriptcoregtk-4.0-18 (2.16.6-1) to 2.18.1-1 libnetcdf-c++4 (4.2-7) to 4.2-7+b1 libnvidia-cfg1 (375.82-5) to 375.82-7 libnvidia-eglcore (375.82-5) to 375.82-7 libnvidia-glcore (375.82-5) to 375.82-7 libnvidia-ml1 (375.82-5) to 375.82-7 libosmesa6 (13.0.6-1+b2) to 17.2.3-1 libwayland-egl1-mesa (13.0.6-1+b2) to 17.2.3-1 libwebkit2gtk-4.0-37 (2.16.6-1) to 2.18.1-1 libwebkit2gtk-4.0-37-gtk2 (2.16.6-1) to 2.18.1-1 libxatracker2 (13.0.6-1+b2) to 17.2.3-1 mesa-vdpau-drivers (13.0.6-1+b2) to 17.2.3-1 netcdf-bin (1:4.4.1.1-2) to 1:4.5.0-1 nvidia-alternative (375.82-5) to 375.82-7 nvidia-driver (375.82-5) to 375.82-7 nvidia-driver-bin (375.82-5) to 375.82-7 nvidia-driver-libs (375.82-5) to 375.82-7 nvidia-egl-icd (375.82-5) to 375.82-7 nvidia-kernel-support (375.82-5) to 375.82-7 nvidia-smi (375.82-5) to 375.82-7 nvidia-vdpau-driver (375.82-5) to 375.82-7 nvidia-vulkan-icd (375.82-5) to 375.82-7 primus-libs (0~20150328-4) to 0~20150328-5 xserver-xorg-video-nvidia (375.82-5) to 375.82-7 xwayland (2:1.19.3-2) to 2:1.19.5-1 Installed the following packages: gir1.2-harfbuzz-0.0 (1.6.2-1) libegl1 (0.2.999+git20170802-5) libfwupd2 (1.0.0-4) libglvnd-core-dev (0.2.999+git20170802-5) libglvnd0:i386 (0.2.999+git20170802-5) libglx-mesa0 (17.2.3-1) libglx-mesa0:i386 (17.2.3-1) libllvm5.0 (1:5.0~+rc2-1) libllvm5.0:i386 (1:5.0~+rc2-1) libnetcdf13 (1:4.5.0-1) librtmidi4 (3.0.0~ds1-2) libxcb-xfixes0:i386 (1.12-1) python3-debconf (1.5.64) In order to solved the issue, I uninstalled all the NVIDIA-related packages, reinstalled GDM
Bug#882002: gpaste FTBFS with appstream-glib 0.7.4-1
Source: gpaste Version: 3.26.0-3 Severity: serious Tags: patch https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/gpaste.html ... dh_install dh_install: Cannot find (any matches for) "usr/share/appdata/org.gnome.GPaste.Ui.appdata.xml" (tried in ., debian/tmp) dh_install: gpaste missing files: usr/share/appdata/org.gnome.GPaste.Ui.appdata.xml dh_install: missing files, aborting debian/rules:7: recipe for target 'binary' failed make: *** [binary] Error 25 Matthias Klumpp already pushed the fix to the collab-maint git.
Bug#881998: asc FTBFS with libphysfs-dev 3.0.1-1
Source: asc Version: 2.6.1.0-2 Severity: serious https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/asc.html ... In file included from physfsrwops.cpp:23:0: physfsrwops.h:42:1: error: '__EXPORT__' does not name a type; did you mean '__FXSR__'? __EXPORT__ SDL_RWops *PHYSFSRWOPS_openRead(const char *fname); ^~ __FXSR__ physfsrwops.h:54:1: error: '__EXPORT__' does not name a type; did you mean '__FXSR__'? __EXPORT__ SDL_RWops *PHYSFSRWOPS_openWrite(const char *fname); ^~ __FXSR__ physfsrwops.h:66:1: error: '__EXPORT__' does not name a type; did you mean '__FXSR__'? __EXPORT__ SDL_RWops *PHYSFSRWOPS_openAppend(const char *fname); ^~ __FXSR__ physfsrwops.h:78:1: error: '__EXPORT__' does not name a type; did you mean '__FXSR__'? __EXPORT__ SDL_RWops *PHYSFSRWOPS_makeRWops(PHYSFS_file *handle); ^~ __FXSR__
Bug#881997: vboot-utils FTBFS on 32bit: test failure
Source: vboot-utils Version: 0~R63-10032.B-1 Severity: serious https://buildd.debian.org/status/package.php?p=vboot-utils&suite=sid ... Testing prog... /<>/build/utility/bmpblk_utility tests/futility/run_test_scripts.sh /<>/build/install_for_test/bin -- builtin -- test_bdb.sh ... [31;1mFAILED. Stdout is recorded in /<>/build/tests/futility_test_results/test_bdb.sh.stdout[0;m + me=test_bdb.sh + TMP=test_bdb.sh.tmp + cd /<>/build/tests/futility_test_results + BDB_FILE=bdb.bin + TESTKEY_DIR=/<>/tests/testkeys + TESTDATA_DIR=/<>/tests/testdata + BDBKEY_PUB=/<>/tests/testkeys/bdbkey.keyb + BDBKEY_PRI=/<>/tests/testkeys/bdbkey.pem + DATAKEY_PUB=/<>/tests/testkeys/datakey.keyb + DATAKEY_PRI=/<>/tests/testkeys/datakey.pem + BDBKEY_DIGEST=/<>/tests/testdata/bdbkey_digest.bin + DATAKEY_DIGEST=/<>/tests/testdata/datakey_digest.bin + DATA_FILE=/<>/tests/testdata/sp-rw.bin + declare -i num_hash + load_address=0x60061ec0de + /<>/build/install_for_test/bin/futility bdb --create bdb.bin --bdbkey_pri /<>/tests/testkeys/bdbkey.pem --bdbkey_pub /<>/tests/testkeys/bdbkey.keyb --datakey_pub /<>/tests/testkeys/datakey.keyb --datakey_pri /<>/tests/testkeys/datakey.pem --load_address 0x60061ec0de BDB is created successfully + verify + local key_digest=/<>/tests/testdata/bdbkey_digest.bin + local extra_option= + /<>/build/install_for_test/bin/futility bdb --verify bdb.bin --key_digest /<>/tests/testdata/bdbkey_digest.bin BDB is successfully verified. + check_field 'Load Address:' 0x60061ec0de ++ /<>/build/install_for_test/bin/futility show bdb.bin ++ grep 'Load Address:' + x=' Load Address: 0x' + '[' ' Load Address: 0x' ']' + x=' 0x' + '[' ' 0x' ']' + x=0x + '[' 0x == 0x60061ec0de ']' + return 1 test_create.sh ... [32;1mPASSED[0;m test_dump_fmap.sh ... [32;1mPASSED[0;m test_gbb_utility.sh ... [32;1mPASSED[0;m test_load_fmap.sh ... [32;1mPASSED[0;m test_main.sh ... [32;1mPASSED[0;m test_rwsig.sh ... 1024 2048 2048_exp3 3072_exp3 4096 8192 [32;1mPASSED[0;m test_show_contents.sh ... [32;1mPASSED[0;m test_show_kernel.sh ... [32;1mPASSED[0;m test_show_vs_verify.sh ... [32;1mPASSED[0;m test_show_usbpd1.sh ... 1024 2048 4096 8192 [32;1mPASSED[0;m test_sign_firmware.sh ... 1 2 3 4 5 6 [32;1mPASSED[0;m test_sign_fw_main.sh ... [32;1mPASSED[0;m test_sign_kernel.sh ... amd64: 1 2 3 4 5 6 arm: 1 2 3 4 5 6 [32;1mPASSED[0;m test_sign_keyblocks.sh ... [32;1mPASSED[0;m test_sign_usbpd1.sh ... 1 2 3 4 [32;1mPASSED[0;m test_file_types.sh ... [32;1mPASSED[0;m [31;1mFAIL: 16 / 17 passed[0;m Makefile:1490: recipe for target 'runfutiltests' failed make[2]: *** [runfutiltests] Error 1 make[2]: Leaving directory '/<>' debian/rules:23: recipe for target 'override_dh_auto_test' failed make[1]: *** [override_dh_auto_test] Error 2
Bug#881990: marked as done (nvidia-kernel-common: install fails: "version ... has bad syntax: invalid character in version number")
Your message dated Fri, 17 Nov 2017 13:05:06 + with message-id and subject line Bug#881990: fixed in nvidia-support 20151021+6 has caused the Debian Bug report #881990, regarding nvidia-kernel-common: install fails: "version ... has bad syntax: invalid character in version number" 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.) -- 881990: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881990 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: nvidia-kernel-common Version: 20151021+5 Severity: grave Justification: renders package unusable I got the following error: [...] Preparing to unpack .../14-nvidia-kernel-common_20151021+5_amd64.deb ... dpkg-maintscript-helper: error: dpkg: warning: version '20051028\+1\+nmu2\~' has bad syntax: invalid character in version number dpkg: error processing archive /tmp/apt-dpkg-install-uFJqP4/14-nvidia-kernel-common_20151021+5_amd64.deb (--unpack): new nvidia-kernel-common package pre-installation script subprocess returned error exit status 1 dpkg-maintscript-helper: error: dpkg: warning: version '20051028\+1\+nmu2\~' has bad syntax: invalid character in version number dpkg: error while cleaning up: new nvidia-kernel-common package post-removal script subprocess returned error exit status 1 [...] Errors were encountered while processing: /tmp/apt-dpkg-install-uFJqP4/14-nvidia-kernel-common_20151021+5_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'stable-updates'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.13.0-1-amd64 (SMP w/12 CPU cores) Locale: LANG=POSIX, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=POSIX (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -- no debconf information --- End Message --- --- Begin Message --- Source: nvidia-support Source-Version: 20151021+6 We believe that the bug you reported is fixed in the latest version of nvidia-support, 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 881...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Luca Boccassi (supplier of updated nvidia-support 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: Fri, 17 Nov 2017 12:46:20 + Source: nvidia-support Binary: nvidia-support nvidia-installer-cleanup nvidia-kernel-common Architecture: source Version: 20151021+6 Distribution: unstable Urgency: medium Maintainer: Debian NVIDIA Maintainers Changed-By: Luca Boccassi Description: nvidia-installer-cleanup - cleanup after driver installation with the nvidia-installer nvidia-kernel-common - NVIDIA binary kernel module support files nvidia-support - NVIDIA binary graphics driver support files Closes: 881990 Changes: nvidia-support (20151021+6) unstable; urgency=medium . [ Andreas Beckmann ] * Set Rules-Requires-Root: no. . [ Luca Boccassi ] * Drop quotes from maintscript to fix dpkg-maintscript-helper error on installation. (Closes: #881990) * Add myself to Uploaders. Checksums-Sha1: 1e73d4a4b7a8cbb4bc0871494a7da7f2b4bbdc9c 1654 nvidia-support_20151021+6.dsc 18b4230bf056298b4d787b408ca51bb302b9f239 33888 nvidia-support_20151021+6.tar.xz 3ef7b92e54b26c6fc97aee6892056ce122666bc8 6249 nvidia-support_20151021+6_source.buildinfo Checksums-Sha256: ff428650ddcd6628ea5b952b916c745d38e57104ddc7005a8885b72777c51831 1654 nvidia-support_20151021+6.dsc 8e1d4823c2220bf45930cd88b6e45fb1f3b067393ee5dd837893258bcf92def6 33888 nvidia-support_20151021+6.tar.xz a4aa032d7561882b4a709e3e489f0c86e706842e4bfab28070ef0ad1bbf5f970 6249 nvidia-support_20151021+6_source.buildinfo Files: a0349e7b25e6d959cf3c4f2a804c8b4d 1654 contrib/misc optional nvidia-support_20151021+6.dsc 9a90f0e58f0becc9cd0f40fc1caa12f5 33888 contrib/misc optional nvidia-support_20151021+6.tar.xz 7a2a84a9bd512305fda5c1c56e058e47 6249 contrib/misc optional nvidia-support_20151021+6_source.buildinfo -BEGI
Bug#881983: marked as done (nvidia-kernel-common: fails upon upgrade)
Your message dated Fri, 17 Nov 2017 13:05:06 + with message-id and subject line Bug#881990: fixed in nvidia-support 20151021+6 has caused the Debian Bug report #881990, regarding nvidia-kernel-common: fails upon upgrade to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 881990: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881990 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: nvidia-kernel-common Version: 20151021+4 Severity: important Dear Maintainer, * What led up to the situation? Upgrading Debian Sid system. * What exactly did you do (or not do) that was effective (or ineffective)? sudo apt upgrade * What was the outcome of this action? Preparing to unpack .../nvidia-kernel-common_20151021+5_amd64.deb ... dpkg-maintscript-helper: error: dpkg: warning: version '20051028\+1\+nmu2\~' has bad syntax: invalid character in version number dpkg: error processing archive /var/cache/apt/archives/nvidia-kernel-common_20151021+5_amd64.deb (--unpack): new nvidia-kernel-common package pre-installation script subprocess returned error exit status 1 dpkg-maintscript-helper: error: dpkg: warning: version '20051028\+1\+nmu2\~' has bad syntax: invalid character in version number dpkg: error while cleaning up: new nvidia-kernel-common package post-removal script subprocess returned error exit status 1 Errors were encountered while processing: /var/cache/apt/archives/nvidia-kernel-common_20151021+5_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) * What outcome did you expect instead? Sucessfully installed package dpkg 1.19.0.4 is installed in this system. Regards -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.13.0-1-amd64 (SMP w/16 CPU cores) Locale: LANG=ca_AD.UTF-8, LC_CTYPE=ca_AD.UTF-8 (charmap=UTF-8), LANGUAGE=ca_AD:ca (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -- no debconf information --- End Message --- --- Begin Message --- Source: nvidia-support Source-Version: 20151021+6 We believe that the bug you reported is fixed in the latest version of nvidia-support, 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 881...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Luca Boccassi (supplier of updated nvidia-support 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: Fri, 17 Nov 2017 12:46:20 + Source: nvidia-support Binary: nvidia-support nvidia-installer-cleanup nvidia-kernel-common Architecture: source Version: 20151021+6 Distribution: unstable Urgency: medium Maintainer: Debian NVIDIA Maintainers Changed-By: Luca Boccassi Description: nvidia-installer-cleanup - cleanup after driver installation with the nvidia-installer nvidia-kernel-common - NVIDIA binary kernel module support files nvidia-support - NVIDIA binary graphics driver support files Closes: 881990 Changes: nvidia-support (20151021+6) unstable; urgency=medium . [ Andreas Beckmann ] * Set Rules-Requires-Root: no. . [ Luca Boccassi ] * Drop quotes from maintscript to fix dpkg-maintscript-helper error on installation. (Closes: #881990) * Add myself to Uploaders. Checksums-Sha1: 1e73d4a4b7a8cbb4bc0871494a7da7f2b4bbdc9c 1654 nvidia-support_20151021+6.dsc 18b4230bf056298b4d787b408ca51bb302b9f239 33888 nvidia-support_20151021+6.tar.xz 3ef7b92e54b26c6fc97aee6892056ce122666bc8 6249 nvidia-support_20151021+6_source.buildinfo Checksums-Sha256: ff428650ddcd6628ea5b952b916c745d38e57104ddc7005a8885b72777c51831 1654 nvidia-support_20151021+6.dsc 8e1d4823c2220bf45930cd88b6e45fb1f3b067393ee5dd837893258bcf92def6 33888 nvidia-support_20151021+6.tar.xz a4aa032d7561882b4a709e3e489f0c86e706842e4bfab28070ef0ad1bbf5f970 6249 nvidia-support_20151021+6_source.buildinfo Files: a0349e7b25e6d959cf3c4f2a804c8b4d 1654 contrib/misc optional nvidia-support_20151021+6.dsc 9a90f0e58f0becc9cd0f40fc1caa12f5 33888 contrib/misc optional nvidia-support_201510
Processed: fix found-version
Processing commands for cont...@bugs.debian.org: > notfound 881990 20151021+4 Bug #881990 [nvidia-kernel-common] nvidia-kernel-common: install fails: "version ... has bad syntax: invalid character in version number" Bug #881983 [nvidia-kernel-common] nvidia-kernel-common: fails upon upgrade No longer marked as found in versions nvidia-support/20151021+4. No longer marked as found in versions nvidia-support/20151021+4. > thanks Stopping processing here. Please contact me if you need assistance. -- 881983: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881983 881990: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881990 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#880704: bumblebee-nvidia: Upgrading mesa and nvidia drivers with bumblebee-nvidia installed breaks the desktop
On Sun, 2017-11-05 at 17:35 +, Luca Boccassi wrote: > On Fri, 2017-11-03 at 19:41 -0500, JWM wrote: > > Package: bumblebee-nvidia > > Version: 3.2.1-16 > > Severity: grave > > Justification: renders package unusable > > > > Dear Maintainer, > > > > My system is a Thinkpad T440p, with both an Intel and an NVIDIA > > Optimus cards. > > On Wednesday, upgrading both the Mesa libraries and the NVIDIA > > driver > > broke the > > desktop ---i.e., after reboot, the GDM target never showed up due > > to > > a Clutter > > error. > > > > Synaptic's history shows the following as > > installed/upgraded/removed > > on that > > day: > > > > - > > --- > > Commit Log for Wed Nov 1 08:23:33 2017 > > > > > > Removed the following packages: > > libegl1-glvnd-nvidia > > libegl1-mesa-dev > > libgl1-mesa-glx:i386 > > libgtk-3-dev > > primus > > primus-libs-ia32:i386 > > primus-libs:i386 > > > > Upgraded the following packages: > > debconf (1.5.63) to 1.5.64 > > debconf-i18n (1.5.63) to 1.5.64 > > eog-plugin-map (3.25.92-1) to 3.26.1-1 > > epiphany-browser (3.24.3-1) to 3.26.1-1 > > epiphany-browser-data (3.24.3-1) to 3.26.1-1 > > giada (0.14.1~dfsg1-1) to 0.14.3~dfsg1-1 > > gir1.2-javascriptcoregtk-4.0 (2.16.6-1) to 2.18.1-1 > > gir1.2-webkit2-4.0 (2.16.6-1) to 2.18.1-1 > > gnome-maps (3.25.91-1) to 3.26.1-1 > > gnome-session (3.24.1-2) to 3.26.1-1 > > gnome-session-bin (3.24.1-2) to 3.26.1-1 > > gnome-session-common (3.24.1-2) to 3.26.1-1 > > gnome-software (3.22.5-1) to 3.26.1-2 > > gnome-software-common (3.22.5-1) to 3.26.1-2 > > gnome-software-plugin-flatpak (3.22.5-1) to 3.26.1-2 > > gstreamer1.0-plugins-bad (1.12.2-1+b1) to 1.12.3-2 > > libegl-nvidia0 (375.82-5) to 375.82-7 > > libegl1-mesa (13.0.6-1+b2) to 17.2.3-1 > > libgbm1 (13.0.6-1+b2) to 17.2.3-1 > > libgl1-glvnd-nvidia-glx (375.82-5) to 375.82-7 > > libgl1-mesa-dri (13.0.6-1+b2) to 17.2.3-1 > > libgl1-mesa-dri:i386 (13.0.6-1+b2) to 17.2.3-1 > > libgl1-mesa-glx (13.0.6-1+b2) to 17.2.3-1 > > libgl1-nvidia-glvnd-glx (375.82-5) to 375.82-7 > > libglapi-mesa (13.0.6-1+b2) to 17.2.3-1 > > libglapi-mesa:i386 (13.0.6-1+b2) to 17.2.3-1 > > libgles-nvidia1 (375.82-5) to 375.82-7 > > libgles-nvidia2 (375.82-5) to 375.82-7 > > libgles1-glvnd-nvidia (375.82-5) to 375.82-7 > > libgles1-nvidia (375.82-5) to 375.82-7 > > libgles2-glvnd-nvidia (375.82-5) to 375.82-7 > > libgles2-mesa (13.0.6-1+b2) to 17.2.3-1 > > libgles2-nvidia (375.82-5) to 375.82-7 > > libglx-nvidia0 (375.82-5) to 375.82-7 > > libglx0-glvnd-nvidia (375.82-5) to 375.82-7 > > libgstreamer-plugins-bad1.0-0 (1.12.2-1+b1) to 1.12.3-2 > > libharfbuzz-dev (1.5.1-1) to 1.6.2-1 > > libharfbuzz-gobject0 (1.5.1-1) to 1.6.2-1 > > libharfbuzz-icu0 (1.5.1-1) to 1.6.2-1 > > libharfbuzz0b (1.5.1-1) to 1.6.2-1 > > libjavascriptcoregtk-4.0-18 (2.16.6-1) to 2.18.1-1 > > libnetcdf-c++4 (4.2-7) to 4.2-7+b1 > > libnvidia-cfg1 (375.82-5) to 375.82-7 > > libnvidia-eglcore (375.82-5) to 375.82-7 > > libnvidia-glcore (375.82-5) to 375.82-7 > > libnvidia-ml1 (375.82-5) to 375.82-7 > > libosmesa6 (13.0.6-1+b2) to 17.2.3-1 > > libwayland-egl1-mesa (13.0.6-1+b2) to 17.2.3-1 > > libwebkit2gtk-4.0-37 (2.16.6-1) to 2.18.1-1 > > libwebkit2gtk-4.0-37-gtk2 (2.16.6-1) to 2.18.1-1 > > libxatracker2 (13.0.6-1+b2) to 17.2.3-1 > > mesa-vdpau-drivers (13.0.6-1+b2) to 17.2.3-1 > > netcdf-bin (1:4.4.1.1-2) to 1:4.5.0-1 > > nvidia-alternative (375.82-5) to 375.82-7 > > nvidia-driver (375.82-5) to 375.82-7 > > nvidia-driver-bin (375.82-5) to 375.82-7 > > nvidia-driver-libs (375.82-5) to 375.82-7 > > nvidia-egl-icd (375.82-5) to 375.82-7 > > nvidia-kernel-support (375.82-5) to 375.82-7 > > nvidia-smi (375.82-5) to 375.82-7 > > nvidia-vdpau-driver (375.82-5) to 375.82-7 > > nvidia-vulkan-icd (375.82-5) to 375.82-7 > > primus-libs (0~20150328-4) to 0~20150328-5 > > xserver-xorg-video-nvidia (375.82-5) to 375.82-7 > > xwayland (2:1.19.3-2) to 2:1.19.5-1 > > > > Installed the following packages: > > gir1.2-harfbuzz-0.0 (1.6.2-1) > > libegl1 (0.2.999+git20170802-5) > > libfwupd2 (1.0.0-4) > > libglvnd-core-dev (0.2.999+git20170802-5) > > libglvnd0:i386 (0.2.999+git20170802-5) > > libglx-mesa0 (17.2.3-1) > > libglx-mesa0:i386 (17.2.3-1) > > libllvm5.0 (1:5.0~+rc2-1) > > libllvm5.0:i386 (1:5.0~+rc2-1) > > libnetcdf13 (1:4.5.0-1) > > librtmidi4 (3.0.0~ds1-2) > > libxcb-xfixes0:i386 (1.12-1) > > python3-debconf (1.5.64) > > - > > --- > > > > > > > > In order to solved the issue, I uninstalled all the NVIDIA-related > > packages, > > reinstalled GDM and blacklisted nouveau. > > > > After that, I tried installing bumblebee-nvidia again, which > > effectively broke > > the system once again. > > > > So it seems the bumblebee-nvidia package is not compatible with the > > newest mesa > > and NVIDIA drivers. > > With nvidia-driver 375.82-8 it should all be installable again, > please > re-try when you have time. Sorry for the
Bug#881990: nvidia-kernel-common: install fails: "version ... has bad syntax: invalid character in version number"
Control: tags -1 pending Control: forcemerge -1 881983 On Fri, 2017-11-17 at 12:13 +0100, Vincent Lefevre wrote: > Package: nvidia-kernel-common > Version: 20151021+5 > Severity: grave > Justification: renders package unusable > > I got the following error: > > [...] > Preparing to unpack .../14-nvidia-kernel-common_20151021+5_amd64.deb > ... > dpkg-maintscript-helper: error: dpkg: warning: version > '20051028\+1\+nmu2\~' has bad syntax: invalid character in version > number > dpkg: error processing archive /tmp/apt-dpkg-install-uFJqP4/14- > nvidia-kernel-common_20151021+5_amd64.deb (--unpack): > new nvidia-kernel-common package pre-installation script subprocess > returned error exit status 1 > dpkg-maintscript-helper: error: dpkg: warning: version > '20051028\+1\+nmu2\~' has bad syntax: invalid character in version > number > dpkg: error while cleaning up: > new nvidia-kernel-common package post-removal script subprocess > returned error exit status 1 > [...] > Errors were encountered while processing: > /tmp/apt-dpkg-install-uFJqP4/14-nvidia-kernel- > common_20151021+5_amd64.deb > E: Sub-process /usr/bin/dpkg returned an error code (1) > > -- System Information: > Debian Release: buster/sid > APT prefers unstable-debug > APT policy: (500, 'unstable-debug'), (500, 'stable-updates'), (500, > 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') > Architecture: amd64 (x86_64) > Foreign Architectures: i386 > > Kernel: Linux 4.13.0-1-amd64 (SMP w/12 CPU cores) > Locale: LANG=POSIX, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), > LANGUAGE=POSIX (charmap=UTF-8) > Shell: /bin/sh linked to /bin/dash > Init: systemd (via /run/systemd/system) > > -- no debconf information Looks like in compat 10 special characters are added in the generated scripts, and since nvidia-kernel-common maintscript single quotes the version they are passed down. Removing the quotes is the simple solution, will upload shortly. -- Kind regards, Luca Boccassi signature.asc Description: This is a digitally signed message part
Bug#881820: marked as done (pkg-haskell-tools build depends on libghc-concurrent-output-dev (< 1.8) but 1.9.2-1 is to be installed)
Your message dated Fri, 17 Nov 2017 12:34:27 + with message-id and subject line Bug#881820: fixed in pkg-haskell-tools 0.11.1 has caused the Debian Bug report #881820, regarding pkg-haskell-tools build depends on libghc-concurrent-output-dev (< 1.8) but 1.9.2-1 is to be installed 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.) -- 881820: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881820 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: pkg-haskell-tools Version: 0.11.0 Severity: serious The following packages have unmet dependencies: builddeps:pkg-haskell-tools : Depends: libghc-concurrent-output-dev (< 1.8) but 1.9.2-1 is to be installed --- End Message --- --- Begin Message --- Source: pkg-haskell-tools Source-Version: 0.11.1 We believe that the bug you reported is fixed in the latest version of pkg-haskell-tools, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 881...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ilias Tsitsimpis (supplier of updated pkg-haskell-tools package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 17 Nov 2017 13:39:46 +0200 Source: pkg-haskell-tools Binary: pkg-haskell-tools Architecture: source Version: 0.11.1 Distribution: unstable Urgency: medium Maintainer: Debian Haskell Group Changed-By: Ilias Tsitsimpis Description: pkg-haskell-tools - Debian Haskell Group tools Closes: 881820 Changes: pkg-haskell-tools (0.11.1) unstable; urgency=medium . [ Joachim Breitner ] * dht upload: Prefer a _source changes files over an _arch changes files. . [ Ilias Tsitsimpis ] * dht what-to-upgrade: Support HTTPS URLs in watchfiles. * Drop upper bound on concurrent-output (Closes: #881820) * Change Priority to optional. Since Debian Policy version 4.0.1, priority extra has been deprecated. * Use the HTTPS form of the copyright-format URL * Declare compliance with Debian policy 4.1.1 Checksums-Sha1: d1f572c554495394ce7e45683c95940f0511e021 2159 pkg-haskell-tools_0.11.1.dsc dd9ff44c9c78f8bbbef7da4398a16516c4ff5881 20548 pkg-haskell-tools_0.11.1.tar.xz ec37281a6a68ebb820e4ccb1ea253bbbfce3d56e 9775 pkg-haskell-tools_0.11.1_amd64.buildinfo Checksums-Sha256: b8a24f5daa4a1806789804cc5289ae7e4bc5922c2393a8529213a3cb33d20d79 2159 pkg-haskell-tools_0.11.1.dsc f7a775e9f1694f8d2c862d12b8bbfb43db2636422c5d25b5be528a2b014fc662 20548 pkg-haskell-tools_0.11.1.tar.xz 2471bb000488806ae5a3a9e669568435a2823b5e8994bdf55705c8ee1608da53 9775 pkg-haskell-tools_0.11.1_amd64.buildinfo Files: bc981813e188155c98d56e0b9d553f91 2159 haskell optional pkg-haskell-tools_0.11.1.dsc 303c838c8538be0efd6d6d01200e2dc5 20548 haskell optional pkg-haskell-tools_0.11.1.tar.xz 9291f111b5d50aa9f8c53a8b94d23bd4 9775 haskell optional pkg-haskell-tools_0.11.1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJIBAEBCgAyFiEEJ9c8pfW11+AaUTb116hngMxkQDwFAloO0qwUHGlsaWFzdHNp QGRlYmlhbi5vcmcACgkQ16hngMxkQDyGhhAAwUA8J60+vHkBaknXbDOYZJhQqFo6 MNNLRmcat68UAH6yAo3+7CZnFKTtqVNGAsdQckpFsa4GMWQdRkyTKwJl1+cl4v0Q zZu88ZGiLe8ITiQ8XQu7AKLXoPTRm37zLWcwT/wop1/r7M/RxK4iksrVYDtQzDPD 1zVUaAD9NxrL0SUKX4T9rXfHuQKSGvJF0kFZ+2f2BaCudkjRmhK58K9cegXOqUsN IaPm/JQTL4g64LW97mJLP1CZC1DwuIRMRsDBeqyTWkBtlbfV/ABHsq7kGGWrKz4u dC1ell/wF98RQ3penaxf7LBSeN6s3/Dl2qWRAk2euSzYeXN4H13ARKuf5EV5hv46 IUg4cQiOoORqkKSK6DHwf/e3alxbw9z8fAUugmjf7kywFzVErIIqQxWUO1pNO1c0 FpEWOjCJTVgqhZD4HnTJOvl8DItEYbT1feqT/g6gZ2Pou4hpsUOMq0mdngEbYmkg hJQK/ZiCr4OgA+w0bBslaYbMWtayYKIK7Q0w3nSqxTnvXc822Z+Cimu4Qnd4hEmN 5LtI8vb4T3vI0362yJFitEyLDK4mz79EfKHYWwWRGAXgtRW1TTw5NytGb219HrV9 nwTzqqEnxymtqX6+0rrFhLRLsxqhikT29Ofgm7YwVOJ0k1hwv2XzM99YvumM1viG 0YDCuOx29+8TikE= =qBZf -END PGP SIGNATURE End Message ---
Processed: Re: Bug#881990: nvidia-kernel-common: install fails: "version ... has bad syntax: invalid character in version number"
Processing control commands: > tags -1 pending Bug #881990 [nvidia-kernel-common] nvidia-kernel-common: install fails: "version ... has bad syntax: invalid character in version number" Added tag(s) pending. > forcemerge -1 881983 Bug #881990 [nvidia-kernel-common] nvidia-kernel-common: install fails: "version ... has bad syntax: invalid character in version number" Bug #881983 [nvidia-kernel-common] nvidia-kernel-common: fails upon upgrade Severity set to 'grave' from 'important' Marked as found in versions nvidia-support/20151021+5. Added tag(s) pending. Bug #881990 [nvidia-kernel-common] nvidia-kernel-common: install fails: "version ... has bad syntax: invalid character in version number" Marked as found in versions nvidia-support/20151021+4. Merged 881983 881990 -- 881983: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881983 881990: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881990 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#881990: Same here
Just to confirm... -- eric
Bug#881977: [PKG-Openstack-devel] Bug#881977: FTBFS: TypeError: 'str' object is not callable
On 11/17/2017 05:39 AM, Adam Borowski wrote: > Source: manila-ui > Version: 2.5.1-0 > Severity: serious > Justification: fails to build from source > > Hi! > I'm afraid manila-ui fails to build with: That's because it's still the old OpenStack Newton version, we need to upgrade it to Pike, and it should build without trouble with the newer Horizon version. I'll take care of it "soon" (whatever that means). Thanks for your valuable bug reports. Cheers, Thomas Goirand (zigo)
Bug#881630: vdr-plugin-xineliboutput: FTBFS with multiarchified xine-lib-1.2 >= 1.2.6-2
Control: tags -1 + patch On Mon, Nov 13, 2017 at 06:43:37PM +0100, Mattia Rizzolo wrote: > I multiarchified xine-lib-1.2 (i.e. just using dh_auto_configure with > compat level >= 9), and that apparently also affects how other packages > places their files. > In particular, vdr-plugin-xineliboutput seems to fail with it (log at > the bottom). > Fix should be as easy as declaring a stricter build-dep on libxine2-dev > and changing the .install files to use a multiarchified path. Patch attached. -- 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 `- diffstat for vdr-plugin-xineliboutput-2.0.0 vdr-plugin-xineliboutput-2.0.0 changelog |8 control |2 +- libxine2-xvdr.install |2 +- 3 files changed, 10 insertions(+), 2 deletions(-) diff -Nru vdr-plugin-xineliboutput-2.0.0/debian/changelog vdr-plugin-xineliboutput-2.0.0/debian/changelog --- vdr-plugin-xineliboutput-2.0.0/debian/changelog 2017-09-16 08:54:16.0 +0200 +++ vdr-plugin-xineliboutput-2.0.0/debian/changelog 2017-11-17 12:13:34.0 +0100 @@ -1,3 +1,11 @@ +vdr-plugin-xineliboutput (2.0.0-1.1) unstable; urgency=medium + + * Non-maintainer upload. + * Fix FTBFS with multi-archified xine-lib-1.2. Closes: #881630 + * Bump build-depends on libxine2-dev to assure we pull a multi-arch libxine2. + + -- Mattia Rizzolo Fri, 17 Nov 2017 12:13:34 +0100 + vdr-plugin-xineliboutput (2.0.0-1) unstable; urgency=medium * New upstream release (Closes: #872496) diff -Nru vdr-plugin-xineliboutput-2.0.0/debian/control vdr-plugin-xineliboutput-2.0.0/debian/control --- vdr-plugin-xineliboutput-2.0.0/debian/control 2017-09-16 08:54:16.0 +0200 +++ vdr-plugin-xineliboutput-2.0.0/debian/control 2017-11-17 12:13:34.0 +0100 @@ -6,7 +6,7 @@ Build-Depends: debhelper (>= 9), gettext, pkg-config, txt2man, vdr-dev (>= 2.2.0), x11proto-core-dev, - libxine2-dev, + libxine2-dev (>= 1.2.6-2), libavutil-dev, libxext-dev, libjpeg-dev, diff -Nru vdr-plugin-xineliboutput-2.0.0/debian/libxine2-xvdr.install vdr-plugin-xineliboutput-2.0.0/debian/libxine2-xvdr.install --- vdr-plugin-xineliboutput-2.0.0/debian/libxine2-xvdr.install 2017-09-16 08:54:16.0 +0200 +++ vdr-plugin-xineliboutput-2.0.0/debian/libxine2-xvdr.install 2017-11-17 01:15:00.0 +0100 @@ -1 +1 @@ -usr/lib/xine +usr/lib/*/xine signature.asc Description: PGP signature
Processed: Re: Bug#881630: vdr-plugin-xineliboutput: FTBFS with multiarchified xine-lib-1.2 >= 1.2.6-2
Processing control commands: > tags -1 + patch Bug #881630 [src:vdr-plugin-xineliboutput] vdr-plugin-xineliboutput: FTBFS with multiarchified xine-lib-1.2 >= 1.2.6-2 Added tag(s) patch. -- 881630: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881630 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#881990: nvidia-kernel-common: install fails: "version ... has bad syntax: invalid character in version number"
Package: nvidia-kernel-common Version: 20151021+5 Severity: grave Justification: renders package unusable I got the following error: [...] Preparing to unpack .../14-nvidia-kernel-common_20151021+5_amd64.deb ... dpkg-maintscript-helper: error: dpkg: warning: version '20051028\+1\+nmu2\~' has bad syntax: invalid character in version number dpkg: error processing archive /tmp/apt-dpkg-install-uFJqP4/14-nvidia-kernel-common_20151021+5_amd64.deb (--unpack): new nvidia-kernel-common package pre-installation script subprocess returned error exit status 1 dpkg-maintscript-helper: error: dpkg: warning: version '20051028\+1\+nmu2\~' has bad syntax: invalid character in version number dpkg: error while cleaning up: new nvidia-kernel-common package post-removal script subprocess returned error exit status 1 [...] Errors were encountered while processing: /tmp/apt-dpkg-install-uFJqP4/14-nvidia-kernel-common_20151021+5_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'stable-updates'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.13.0-1-amd64 (SMP w/12 CPU cores) Locale: LANG=POSIX, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=POSIX (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -- no debconf information
Bug#881881: libtrilinos-kokkos-kernels-dev: fails to upgrade from 'testing' - trying to overwrite /usr/include/trilinos/Kokkos_ArithTraits.hpp
Ah, yes, these files seem to have moved from Tpetra to Kokkos. These two upstream packages are tightly related, so no surprise there. I'll see if I can get this fixed. Cheers, Nico On Thu, Nov 16, 2017 at 2:15 AM Andreas Beckmann wrote: > Package: libtrilinos-kokkos-kernels-dev > Version: 12.12.1-1 > Severity: serious > User: debian...@lists.debian.org > Usertags: piuparts > > 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/ch-relationships.html#s-replaces > > From the attached log (scroll to the bottom...): > > Selecting previously unselected package > libtrilinos-kokkos-kernels-dev:amd64. > Preparing to unpack > .../libtrilinos-kokkos-kernels-dev_12.12.1-1_amd64.deb ... > Unpacking libtrilinos-kokkos-kernels-dev:amd64 (12.12.1-1) ... > dpkg: error processing archive > /var/cache/apt/archives/libtrilinos-kokkos-kernels-dev_12.12.1-1_amd64.deb > (--unpack): >trying to overwrite '/usr/include/trilinos/Kokkos_ArithTraits.hpp', > which is also in package libtrilinos-tpetra-dev 12.10.1-4+b1 > dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) > Errors were encountered while processing: > > /var/cache/apt/archives/libtrilinos-kokkos-kernels-dev_12.12.1-1_amd64.deb > > > cheers, > > Andreas >
Bug#881986: python-kafka FTBFS with python-lz4 0.10.1
Source: python-kafka
Version: 1.3.3-2
Severity: serious
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/python-kafka.html
...
=== FAILURES ===
_ test_lz4_old _
@pytest.mark.skipif(not has_lz4() or platform.python_implementation() ==
'PyPy',
reason="python-lz4 crashes on old versions of pypy")
def test_lz4_old():
for i in xrange(1000):
b1 = random_string(100).encode('utf-8')
> b2 = lz4_decode_old_kafka(lz4_encode_old_kafka(b1))
test/test_codec.py:101:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
payload =
'eEHdGSeNDtPGdsFoZBWbyPtfiLuqDexMGJjalmLGbflCQlRlJSUkIOlNjprhcByztKullDShkZWcZmimcirvBRYfVAaABLjGAaPy'
def lz4_encode_old_kafka(payload):
"""Encode payload for 0.8/0.9 brokers -- requires an incorrect header
checksum."""
> assert xxhash is not None
E AssertionError
kafka/codec.py:229: AssertionError
== 1 failed, 231 passed, 81 skipped in 21.66 seconds ===
debian/rules:14: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 1
Bug#881599: marked as done (gitit: unsatisfiable B-D: libghc-hoauth2-dev (< 0.6), but sid has 1.3.0-1)
Your message dated Fri, 17 Nov 2017 09:05:35 +
with message-id
and subject line Bug#881599: fixed in gitit 0.12.2.1+dfsg-1
has caused the Debian Bug report #881599,
regarding gitit: unsatisfiable B-D: libghc-hoauth2-dev (< 0.6), but sid has
1.3.0-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.)
--
881599: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881599
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gitit
Version: 0.12.2.1-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)
gitit cannot be built in sid any longer since haskell-hoauth2 has been
upgraded to 1.3.0.
Andreas
--- End Message ---
--- Begin Message ---
Source: gitit
Source-Version: 0.12.2.1+dfsg-1
We believe that the bug you reported is fixed in the latest version of
gitit, 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 881...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Sean Whitton (supplier of updated gitit 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, 04 Sep 2017 19:59:06 -0700
Source: gitit
Binary: gitit libghc-gitit-dev libghc-gitit-prof libghc-gitit-doc
libghc-gitit-data
Architecture: source
Version: 0.12.2.1+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Haskell Group
Changed-By: Sean Whitton
Description:
gitit - ${haskell:ShortDescription}${haskell:ShortBlurb}
libghc-gitit-data - ${haskell:ShortDescription} - Data files
libghc-gitit-dev - ${haskell:ShortDescription}${haskell:ShortBlurb}
libghc-gitit-doc - ${haskell:ShortDescription}${haskell:ShortBlurb}
libghc-gitit-prof - ${haskell:ShortDescription}${haskell:ShortBlurb}
Closes: 881599
Changes:
gitit (0.12.2.1+dfsg-1) unstable; urgency=medium
.
[ Gianfranco Costamagna ]
* Team upload, import Ubuntu patch
.
[ Mathieu Trudel-Lapierre ]
* debian/patches/git_bump_hoauth2_3f6252d7.patch: cherry-pick the bump for
minimal hoauth2 to 1.3.0 and uri-bytestring addition.
* debian/control: update Build-Depends for hoauth2 and uri-bytestring.
(Closes: #881599)
.
[ Sean Whitton ]
* Upload again with correct version number.
This was breaking `dht make-all`.
.
[ Ilias Tsitsimpis ]
* Change Priority to optional. Since Debian Policy version 4.0.1,
priority extra has been deprecated.
* Use the HTTPS form of the copyright-format URL
* Modify d/watch and Source field in d/copyright to use HTTPS
* Declare compliance with Debian policy 4.1.1
Checksums-Sha1:
6e273b52dec1a4e75080e97bf736dc52f5777e39 6163 gitit_0.12.2.1+dfsg-1.dsc
a3a2c2c32d1138fc7ff5c17095057bf149dc4d5e 188942 gitit_0.12.2.1+dfsg.orig.tar.gz
170fb9c66d4927238d1e509034c2d13878a7d544 12888
gitit_0.12.2.1+dfsg-1.debian.tar.xz
caeae29aac034afaabeb833e4ade31c763d501df 10053
gitit_0.12.2.1+dfsg-1_source.buildinfo
Checksums-Sha256:
04b818508a0427afb2811471278c5a5dc3de6a3cf2fb1821d458fb958764114d 6163
gitit_0.12.2.1+dfsg-1.dsc
3888eed79fe7277f70ec0aa6b8795c2f7a5e9cd830a96856bf0bd5ae01aec12f 188942
gitit_0.12.2.1+dfsg.orig.tar.gz
295a11ede237c837b9a9010fdfc1715caecdd9275658862b949966173b6b510b 12888
gitit_0.12.2.1+dfsg-1.debian.tar.xz
3a22821d77e6707347696e55db371414baef15870e09439db0a40cf42dc6ba0a 10053
gitit_0.12.2.1+dfsg-1_source.buildinfo
Files:
c8ce1b5f55a9fcf7dbf4c032047a90c0 6163 haskell optional
gitit_0.12.2.1+dfsg-1.dsc
9090f4c7de7186fc86ada35530518f35 188942 haskell optional
gitit_0.12.2.1+dfsg.orig.tar.gz
d4e1d309087d1e1b347509b68ef7247a 12888 haskell optional
gitit_0.12.2.1+dfsg-1.debian.tar.xz
19d396c1c8ecfbf3efa98164f5a49e53 10053 haskell optional
gitit_0.12.2.1+dfsg-1_source.buildinfo
-BEGIN PGP SIGNATURE-
iQIcBAEBCAAGBQJaDpq4AAoJEPNPCXROn13Z5r4P/RnFY0Tqku8mMKzBrC455VRS
JA63AMJNlPJRKGgni+xBMcc6E3krjgIM5fJdtt0rrbjAURgnylTB0Nvta6D/5llB
AfNHJfQQQCKC7z8PtYLnYOPQtoDlOFC1ftawxZIGQk0FCPMw8sUg9UF90uHMwvvw
vvhRG+ZJ3NTAM/9fCSFph/QFi3KLFRn1rAKOwVKP5KD/sBQ/a5cBT4drAvZCu04/
sIcSlbubZZ2EkFa476Q+3zD3YYFQj0kVKLYMJSt5LSQysbbmJ7AGT2chqRrtvG4E
bWRIm8gOzhdw3/JmTOFuB03lxw6NK4dYpYl2kq0fX1uwwGO0R2XTPjorkjurpd7n
QB+3Cwwl877Euyn6NKRa1HZ9oemMBzOf
Bug#835801: marked as done (vboot-utils: FTBFS with openssl 1.1.0)
Your message dated Fri, 17 Nov 2017 09:07:32 + with message-id and subject line Bug#835801: fixed in vboot-utils 0~R63-10032.B-1 has caused the Debian Bug report #835801, regarding vboot-utils: FTBFS with openssl 1.1.0 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.) -- 835801: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=835801 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: vboot-utils Version: 0~R52-8350.B-1 Severity: important Hi, OpenSSL 1.1.0 is about to released. During a rebuild of all packages using OpenSSL this package fail to build. A log of that build can be found at: https://breakpoint.cc/openssl-1.1-rebuild-2016-08-26/failed/vboot-utils_0~R52-8350.B-1_amd64-2016-08-26T19%3A57%3A20Z On https://wiki.openssl.org/index.php/1.1_API_Changes you can see various of the reasons why it might fail. There are also updated man pages at https://www.openssl.org/docs/manmaster/ that should contain useful information. Experimental has the libssl-dev 1.1.0 packages in it. I suggest you try building against that to see if everything works. If you have problems making things work, feel free to contact us. Kurt --- End Message --- --- Begin Message --- Source: vboot-utils Source-Version: 0~R63-10032.B-1 We believe that the bug you reported is fixed in the latest version of vboot-utils, 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 835...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sophie Brun (supplier of updated vboot-utils package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 16 Nov 2017 09:21:28 +0100 Source: vboot-utils Binary: vboot-utils cgpt vboot-kernel-utils Architecture: source Version: 0~R63-10032.B-1 Distribution: unstable Urgency: medium Maintainer: Sophie Brun Changed-By: Sophie Brun Description: cgpt - GPT manipulation tool with support for Chromium OS extensions vboot-kernel-utils - Chrome OS verified boot utils required to sign kernels vboot-utils - Chrome OS verified u-boot utilities Closes: 835801 Changes: vboot-utils (0~R63-10032.B-1) unstable; urgency=medium . * Fix debian/watch * New upstream version 0~R63-10032.B * Build against openssl 1.1 (Closes: #835801) * Remove useless patch 0001-use-zu-as-appropriate-for-size_t (fixed upstream) * Update debian/copyright * Remove useless patch 0009-drop-failing-test.patch * Add a patch to fix failing tests-show-contents * Bump Standards-version to 4.1.1: update Priority to optional, use https * Fix perms for usr/share/vboot/bin/common_minimal.sh Checksums-Sha1: cf23bfe474a74748f6d735f9b77de6ae39a68138 2000 vboot-utils_0~R63-10032.B-1.dsc b964ea15bc9a14e449500c422a69c4d8e7045f51 35831751 vboot-utils_0~R63-10032.B.orig.tar.gz 48d0ed4c3486838ef1ab96d3907205b5f215de63 11848 vboot-utils_0~R63-10032.B-1.debian.tar.xz 986e4084a3f65fda704c12de46218547c5aa6f15 5587 vboot-utils_0~R63-10032.B-1_source.buildinfo Checksums-Sha256: e49485fb2847fe1d6a1397039b4815ad64a997d7335307df3ac5274d66208cd8 2000 vboot-utils_0~R63-10032.B-1.dsc 7612a7b09a35a8287d15d307549b3e8118815712e52c2dde9b2146031bde7b95 35831751 vboot-utils_0~R63-10032.B.orig.tar.gz 29a0aa4ca2d74923f01a3cf014fb735bfa148823f723e7ba709d118b78775152 11848 vboot-utils_0~R63-10032.B-1.debian.tar.xz 44d6224539cae2cf20563b7fdf01d1d5dcbc3e1dbbdc198c19cbd4936e03043f 5587 vboot-utils_0~R63-10032.B-1_source.buildinfo Files: 5f5feea218f704f6067a747d99b0b732 2000 admin optional vboot-utils_0~R63-10032.B-1.dsc 698408cfa5f07e9e1ebf29660ec6f09f 35831751 admin optional vboot-utils_0~R63-10032.B.orig.tar.gz 74803c1ce851495235bca3740ca7ec39 11848 admin optional vboot-utils_0~R63-10032.B-1.debian.tar.xz a98ccb35404b797b9890925cf3513d65 5587 admin optional vboot-utils_0~R63-10032.B-1_source.buildinfo -BEGIN PGP SIGNATURE- Comment: Signed by Raphael Hertzog iQEzBAEBCgAdFiEE1823g1EQnhJ1LsbSA4gdq+vCmrkFAloOofQACgkQA4gdq+vC mrn5NAf9GDTa2XPQrxHQ4ahbPx/Nmea8xvNtPCwJfvBIYmIg5LLVEC+eETRVbq/x FFV6DIgc3VyD2mCaw1m/F1LPJDKb+VWx5IB3+qk3Ld2R0rlDLgt9jQ8/0+Omdons xeDcOg2Vd2tVESvEoM9OGgya/rlyZMZYRkxKtptsrtKDTDGECUZqaX28z9Y
Bug#881967: libopenmpi3: ships libpmix.so.* which has a different SOVERSION than all other libs
Thanks for this report. With openmpi3, I intend to use the external package pmix (which will then be used by both openmpi and mpich). pmix was accepted into unstable yesterday, and I am doing test builds of openmpi3 against it. I need to fix arch regressions on both pmix and openmpi3 in experimental before it is fit to proceed to a transition. best regards Alastair On 16/11/2017 23:37, Andreas Beckmann wrote: > Package: libopenmpi3 > Version: 3.0.0-1 > Severity: serious > User: debian...@lists.debian.org > Usertags: piuparts > > Hi, > > during a test with piuparts I noticed your package fails to upgrade from > 'sid' to 'experimental'. > It installed fine in 'sid', then the upgrade to 'experimental' fails > because it tries to overwrite other packages files without declaring a > Breaks+Replaces relation.
