Bug#918206: Pandas new version (not?)
Given the soft freeze, the new upstream version is probably no longer an
option for buster.
Just setting __array_priority__ fails, but with a message that suggests
also including the test_analytics part of that upstream commit would
work; I haven't yet had time to try this.
left = one two
0 -1.365296 1.088132
1 -1.668353 3.025582
2 0.343140 -0.260306
right = array([[-1.36529629, 1.08813166],
[-1.66835336, 3.02558216],
[ 0.34314 , -0.26030576]])
cls =
def _check_isinstance(left, right, cls):
"""
Helper method for our assert_* methods that ensures that
the two objects being compared have the right type before
proceeding with the comparison.
Parameters
--
left : The first object being compared.
right : The second object being compared.
cls : The class type to check against.
Raises
--
AssertionError : Either `left` or `right` is not an instance of
`cls`.
"""
err_msg = "{name} Expected type {exp_type}, found {act_type}
instead"
cls_name = cls.__name__
if not isinstance(left, cls):
raise AssertionError(err_msg.format(name=cls_name,
exp_type=cls,
act_type=type(left)))
if not isinstance(right, cls):
raise AssertionError(err_msg.format(name=cls_name,
exp_type=cls,
> act_type=type(right)))
E AssertionError: DataFrame Expected type 'pandas.core.frame.DataFrame'>, found instead
../debian/tmp/usr/lib/python3/dist-packages/pandas/util/testing.py:296:
AssertionError
Bug#921016: marked as done (start-stop-daemon: matching only on non-root pidfile /var/run/amavis/amavisd.pid is insecure)
Your message dated Wed, 13 Feb 2019 07:34:04 + with message-id and subject line Bug#921016: fixed in amavisd-new 1:2.11.0-6 has caused the Debian Bug report #921016, regarding start-stop-daemon: matching only on non-root pidfile /var/run/amavis/amavisd.pid is insecure 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.) -- 921016: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921016 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: amavisd-new Version: 1:2.11.0-4 Severity: serious Restarting amavisd-new like it is done by a spamassassin hook doesn't work: start-stop-daemon: matching only on non-root pidfile /var/run/amavis/amavisd.pid is insecure If a restart i.e. triggerd by spamassassin it doesn't restart properly and has to be started by the sys-admin again. At least on a sysvinit-system. I don't know whether this is an issue from amavisd-new or dpkg (start-stop-daemon) but feel free to assign it properly. Thanks Elimar -- On the keyboard of life you have always to keep a finger at the escape key;-) --- End Message --- --- Begin Message --- Source: amavisd-new Source-Version: 1:2.11.0-6 We believe that the bug you reported is fixed in the latest version of amavisd-new, 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 921...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Brian May (supplier of updated amavisd-new 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: Wed, 13 Feb 2019 17:48:10 +1100 Source: amavisd-new Binary: amavisd-new Architecture: source Version: 1:2.11.0-6 Distribution: unstable Urgency: medium Maintainer: Brian May Changed-By: Brian May Description: amavisd-new - Interface between MTA and virus scanner/content filters Closes: 921016 Changes: amavisd-new (1:2.11.0-6) unstable; urgency=medium . * Fix start-stop-daemon insecure error. Closes: #921016. Checksums-Sha1: e9e2702134ac35af8adadcd9d9b0e28655b2143c 1971 amavisd-new_2.11.0-6.dsc c605100703c946f542d590370bef9fd16b417979 1092773 amavisd-new_2.11.0.orig.tar.gz abff3e5948c0b3b6518b226ea07bf26ab15ef1a5 58232 amavisd-new_2.11.0-6.debian.tar.xz 07f1ea131990a3d935134a170b4935031c2ef8cf 5589 amavisd-new_2.11.0-6_source.buildinfo Checksums-Sha256: f349fe76b2cc59f2b09eda48e25c14b268119238610774b9573e3ef39fa1f31a 1971 amavisd-new_2.11.0-6.dsc 642dc4bfd2b1cfd20aada05f9fc9e151af607ed0f3f02baf1933163af97c636d 1092773 amavisd-new_2.11.0.orig.tar.gz d06f6797a53a109805156136b070d0fb072f50b7051b37ad1d937ca71431bc40 58232 amavisd-new_2.11.0-6.debian.tar.xz 9a9c09e76d3e7971e676428ede31c33df3a34ecb9f3b042698e10c1a43475773 5589 amavisd-new_2.11.0-6_source.buildinfo Files: aebfe6fb86f3db0efce3f4b6e9815a87 1971 mail optional amavisd-new_2.11.0-6.dsc c412b55af77f930c6385f1e08412f865 1092773 mail optional amavisd-new_2.11.0.orig.tar.gz 71a8dbfc6b111af738e1b6e7795346c5 58232 mail optional amavisd-new_2.11.0-6.debian.tar.xz 383b793fe624b6dae4cb617cbc2ca9cd 5589 mail optional amavisd-new_2.11.0-6_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEKpwfR8DOwu5vyB4TKpJZkldkSvoFAlxjxMcACgkQKpJZkldk Svq5YA/+O6eSXhkFkHlyBZOhJhEUFCP2+BXIMbtdjX4XpOXon11iyDxJcGapxmTD hanCRVDTan9r085/pbmfh0E44+hrd9Cf/kBiifU3QaX+XbHVqrlgUykAh0yMhHzr /QshbW4EBchROJidpK8OJuQ/dpgEix1Ch1Tj3XN23bLxu8WqvoSQxqj/6D7zN18M ndxu/PKtOvRJeBbPRmOAfJQsyHn7gqGE70MiI/iRSFxGpziP+BSJFnrDCrlikJzZ Z9j/xF8Jx3gXl3YCV8Iqj+R78RoD4UAR1MYUcjUU82S8O3rsEuy5YXpwEIsjGg8U PU/iG5n5Yd3cPKoh7FuB6Y5sMuvHabKExzdooL93LR8bZMHew10ZzmsYOeH7IK/V x2rB8Lnu/oFwsKUyZ+LC5OGwpSgbOYLIngNSsJwe6gT2LpWcUv8cw7dLvTHVnzTz ShBCWk1QVd/vfsAiyDL9ES50SnWYPlyiYIi2wBw+lBOjDaeZG3JAyID8iypB81N8 a5QJl4msgQhxWaZbyCTcKF+vx6SGlURojfoJOL4EZuopcmuMii5D/tef4UNPtxl5 bi5t0Amu3ABxPLQs4ddRJU2Z+/HTmEieDgihsxby5Twt+ZJpc1sgZ5uxZpwZIclV N5SxkQs0M6MzGUeADcsyFeNZyzjLPaUfWQ9D/0FFsodqnPrWgBI= =1Aan -END PGP SIGNATURE End Message ---
Bug#918395: marked as done (thumbor FTBFS: test failure in test_redeye_applied)
Your message dated Wed, 13 Feb 2019 02:56:43 + with message-id and subject line Bug#918395: fixed in thumbor 6.5.1-4 has caused the Debian Bug report #918395, regarding thumbor FTBFS: test failure in test_redeye_applied 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.) -- 918395: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918395 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:thumbor Version: 6.5.1-3 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) Hi! I've been doing a full rebuild of the Debian archive, building all source packages targeting armel and armhf using arm64 hardware. We are planning in future to move all of our 32-bit armel/armhf builds to using arm64 machines, so this rebuild is to identify packages that might have problems with this configuration. I've found that thumbor exhibits test failures as armhf on aem64, but the problem is generic. I can see that it also shows the same failure in sid at the moment for amd64: == ERROR: test_redeye_applied (tests.filters.test_redeye.RedEyeFilterTestCase) -- Traceback (most recent call last): File "/work/stemci01/debian/build/thumbor/thumbor-6.5.1/.pybuild/cpython2_2.7_thumbor/build/tests/filters/test_redeye.py", line 43, in test_redeye_applied config_context File "/work/stemci01/debian/build/thumbor/thumbor-6.5.1/.pybuild/cpython2_2.7_thumbor/build/tests/base.py", line 279, in get_filtered fltr.run(dummy_callback) File "thumbor/filters/__init__.py", line 202, in run results.append(self.runnable_method(*self.params)) File "thumbor/filters/__init__.py", line 23, in wrapper return fn(self, *args2) File "thumbor/filters/redeye.py", line 38, in red_eye image.setflags(write=1) ValueError: cannot set WRITEABLE flag to True of this array >> begin captured logging << PIL.PngImagePlugin: DEBUG: STREAM 'IHDR' 16 13 PIL.PngImagePlugin: DEBUG: STREAM 'IDAT' 41 358237 PIL.PngImagePlugin: DEBUG: STREAM 'IHDR' 16 13 PIL.PngImagePlugin: DEBUG: STREAM 'IDAT' 41 65536 PIL.PngImagePlugin: DEBUG: STREAM 'IHDR' 16 13 PIL.PngImagePlugin: DEBUG: STREAM 'IDAT' 41 358944 - >> end captured logging << - Full log for armhf online at: https://www.einval.com/debian/arm/rebuild-logs/armhf/FAIL/thumbor_6.5.1-3_armhf.log -- System Information: Debian Release: 9.6 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-debug'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-8-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) --- End Message --- --- Begin Message --- Source: thumbor Source-Version: 6.5.1-4 We believe that the bug you reported is fixed in the latest version of thumbor, 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 918...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Marcelo Jorge Vieira (supplier of updated thumbor 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: Wed, 13 Feb 2019 00:14:29 -0200 Source: thumbor Binary: thumbor thumbor-dbgsym Architecture: source amd64 Version: 6.5.1-4 Distribution: unstable Urgency: high Maintainer: Debian Python Modules Team Changed-By: Marcelo Jorge Vieira Description: thumbor- Photo thumbnail service Closes: 891612 918395 Changes: thumbor (6.5.1-4) unstable; urgency=high . * dependency python-imaging is does-not-exist (Closes: #891612) * test failure in test_redeye_applied (numpy >= 1.16.0) (Closes: #918395) Checksums-Sha1: 1d3b38e4e05e045a5ffa1bc4ae5f6b4498f72071 2610 thumbor_6.5.1-4.dsc 7819e8e5839428f3e19c536eb2940d144c939246 19216 thumbor_6.5.1-4.debian.tar.xz 37ed3dff94423fa10a7dab1572d7102dfb30d616 214880 thumbor-dbgsym_6.5.1-4_amd64.
Bug#891612: marked as done (thumbor: uninstallable after python-imaging removal)
Your message dated Wed, 13 Feb 2019 02:56:43 + with message-id and subject line Bug#891612: fixed in thumbor 6.5.1-4 has caused the Debian Bug report #891612, regarding thumbor: uninstallable after python-imaging removal to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 891612: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891612 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: thumbor Version: 6.3.2-4 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package is no longer installable in sid: The following packages have unmet dependencies: thumbor : Depends: python-imaging but it is not installable Cheers, Andreas --- End Message --- --- Begin Message --- Source: thumbor Source-Version: 6.5.1-4 We believe that the bug you reported is fixed in the latest version of thumbor, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 891...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Marcelo Jorge Vieira (supplier of updated thumbor 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: Wed, 13 Feb 2019 00:14:29 -0200 Source: thumbor Binary: thumbor thumbor-dbgsym Architecture: source amd64 Version: 6.5.1-4 Distribution: unstable Urgency: high Maintainer: Debian Python Modules Team Changed-By: Marcelo Jorge Vieira Description: thumbor- Photo thumbnail service Closes: 891612 918395 Changes: thumbor (6.5.1-4) unstable; urgency=high . * dependency python-imaging is does-not-exist (Closes: #891612) * test failure in test_redeye_applied (numpy >= 1.16.0) (Closes: #918395) Checksums-Sha1: 1d3b38e4e05e045a5ffa1bc4ae5f6b4498f72071 2610 thumbor_6.5.1-4.dsc 7819e8e5839428f3e19c536eb2940d144c939246 19216 thumbor_6.5.1-4.debian.tar.xz 37ed3dff94423fa10a7dab1572d7102dfb30d616 214880 thumbor-dbgsym_6.5.1-4_amd64.deb 31d51008905b9537479fa396145438c08a8f2da4 19200 thumbor_6.5.1-4_amd64.buildinfo 5baba2742a96cc41884baf4ad8ac473aa33d4412 879868 thumbor_6.5.1-4_amd64.deb Checksums-Sha256: 419310d92d48b48967fc78b412e98ac4b0c746e52e9c6de403fa413008d95440 2610 thumbor_6.5.1-4.dsc 834794ff6ad286902cb1172103b414f1ed902a970ebc6deedcad1ee3add0d687 19216 thumbor_6.5.1-4.debian.tar.xz b23e648cc302356add6783423f030acb1a741c0b787c79e027c69e28e2a811e5 214880 thumbor-dbgsym_6.5.1-4_amd64.deb 710303b2f7675e917dd5dd20e1bb7a88ed3c5057533be754b1ee79f81b84ada7 19200 thumbor_6.5.1-4_amd64.buildinfo 9de0ba23ccfb6d85a585c25773ef874bb73d7f62b8f630cc9ae7961308058753 879868 thumbor_6.5.1-4_amd64.deb Files: 4238bc973155809037e2c0d0843d5d98 2610 python optional thumbor_6.5.1-4.dsc 5472bec14de75717a858e72b61ece8f1 19216 python optional thumbor_6.5.1-4.debian.tar.xz 9e91a75d1ae9ff2ea2643d5166c994f5 214880 debug optional thumbor-dbgsym_6.5.1-4_amd64.deb 9324fe74a2843259925142285ec8e6d5 19200 python optional thumbor_6.5.1-4_amd64.buildinfo 15fa44bb0b6db70a08b9c31ba49a983d 879868 python optional thumbor_6.5.1-4_amd64.deb -BEGIN PGP SIGNATURE- iQJFBAEBCAAvFiEEX659A8zSLhyNqcUJW5JO4xAFXNMFAlxjgU4RHG1ldGFsQGRl Ymlhbi5vcmcACgkQW5JO4xAFXNNNOBAAr0WvD4dqYjspS5kUjSR6aZygIDtd6Fo6 d3Ekc9wo3IcViNwbDOQJuQWMeTf3SoUGxvqENeLRq+Wwwro30zh+73w9nNLuc1uQ /cwPdDNdABtxY/DyMGXVBVD2pjS+r+bDZEGJKoZD8FY6rJAqQLHEtUSNEsJv717j MzoQeoSud4fofc84Qpz4ybZeYnluyiQkmgiFXbP0Pu6NNkXbLvEVP0HrP7tPtzMj xjtGMEg9+plZW6QLGJ6m3anq4haUenQVwFlrKsSOPAsqNx7P0nLX+2PJaHBUFR0W /VRH30mepZYLaeuV2DrMFIukUWu2keDi4uOOnqC5Xx7JN6At0Y5fs81/H6psag3M 2b2S/nhiBuKxpHcIGfrrPQtUF6Lnk/oRV1rKGIQNf71Q9eM7sQJ9HG/Gi2jjLFty GoYuRMgtjLQh1oQWRyezJcMdRZ6Q6WzoO/zRErWkwMchsZzv4+Qm5kB6rDJEnwsf d41PMqVrSItexdzUKBbi/bvaF4XDiwrnJ9IQLqYgAgKbFpywOPHYQSS/UygAdOgl 9rBQQmw+iJ1ufExjdr7BiKHMA5v9oQjGP8SRvxRtdJT7tpYwLmhly8imAcE7uf/V HfGRx5vU7tM5+g10jYm+vc4oRRCckYRynq+wC2OFNKAUfbxAxtv37sJL98ChGbCX diJYIPnCpHM= =ylzA -END PGP SIGNATURE End Message ---
Bug#917024: marked as done (CVE-2018-1000832 CVE-2018-1000833)
Your message dated Wed, 13 Feb 2019 11:41:36 +1100 with message-id <1769693.1KtlZ4lnj9@deblab> and subject line Done: CVE-2018-1000832 CVE-2018-1000833 has caused the Debian Bug report #917024, regarding CVE-2018-1000832 CVE-2018-1000833 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.) -- 917024: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917024 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: zoneminder Severity: grave Tags: security Please see http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-1000832 http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-1000833 Cheers, Moritz --- End Message --- --- Begin Message --- No longer affects "unstable" - closing. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 917...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. -- Best wishes, Dmitry Smirnov --- Good luck happens when preparedness meets opportunity. signature.asc Description: This is a digitally signed message part. --- End Message ---
Processed: reassign 922178 to libpam0g, forcibly merging 922178 922183
Processing commands for cont...@bugs.debian.org:
> reassign 922178 libpam0g
Bug #922178 {Done: Steve Langasek } [libpam-runtime]
/lib/security/pam_unix.so: cannot open shared object file: No such file or
directory
Bug reassigned from package 'libpam-runtime' to 'libpam0g'.
No longer marked as found in versions pam/1.3.1-1.
No longer marked as fixed in versions pam/1.3.1-2.
> forcemerge 922178 922183
Bug #922178 {Done: Steve Langasek } [libpam0g]
/lib/security/pam_unix.so: cannot open shared object file: No such file or
directory
Bug #922183 [libpam0g] libpam0g: upgrade to 1.3.1-1 breaks running
xscreensaver, locking user out of session
Severity set to 'serious' from 'grave'
Marked Bug as done
Added tag(s) confirmed.
Bug #922178 {Done: Steve Langasek } [libpam0g]
/lib/security/pam_unix.so: cannot open shared object file: No such file or
directory
Marked as found in versions pam/1.3.1-1.
Merged 922178 922183
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
922178: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922178
922183: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922183
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#896489: marked as done (python-zxcvbn,python3-zxcvbn: both ship /usr/bin/zxcvbn)
Your message dated Wed, 13 Feb 2019 00:51:45 + with message-id and subject line Bug#896489: fixed in python-zxcvbn 4.4.27-1 has caused the Debian Bug report #896489, regarding python-zxcvbn,python3-zxcvbn: both ship /usr/bin/zxcvbn 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.) -- 896489: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896489 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python-zxcvbn,python3-zxcvbn Version: 4.4.25-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install because it tries to overwrite other packages files. >From the attached log (scroll to the bottom...): Selecting previously unselected package python3-zxcvbn. Preparing to unpack .../python3-zxcvbn_4.4.25-1_all.deb ... Unpacking python3-zxcvbn (4.4.25-1) ... dpkg: error processing archive /var/cache/apt/archives/python3-zxcvbn_4.4.25-1_all.deb (--unpack): trying to overwrite '/usr/bin/zxcvbn', which is also in package python-zxcvbn 4.4.25-1 Errors were encountered while processing: /var/cache/apt/archives/python3-zxcvbn_4.4.25-1_all.deb cheers, Andreas python-zxcvbn=4.4.25-1_python3-zxcvbn=4.4.25-1.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: python-zxcvbn Source-Version: 4.4.27-1 We believe that the bug you reported is fixed in the latest version of python-zxcvbn, 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 896...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sabino Par (supplier of updated python-zxcvbn package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 13 Feb 2019 00:49:46 +0100 Source: python-zxcvbn Architecture: source Version: 4.4.27-1 Distribution: unstable Urgency: medium Maintainer: Sabino Par Changed-By: Sabino Par Closes: 896489 Changes: python-zxcvbn (4.4.27-1) unstable; urgency=medium . [ Sabino Par ] * New upstream release * d/control: Update std-version to 4.2.0 * d/watch: move from pypi to github. . [ Mattia Rizzolo ] * d/watch: Fix archive matching * d/rules: Do not install the zxcvbn binary in the python2 package. Closes: #896489 * d/control: + Bump Standards-Version to 4.3.0, no changes needed. + Use the new debhelper-compat notation and drop d/compat. + Bump the debhelper compat level to 12. + Set Rules-Requires-Root:no. + Set Testsuite:autopkgtest-pkg-python. + Tweak the descriptions to appease lintian. * Install the README.rst file in all packages. . [ Chris Lamb ] * Remove trailing whitespaces. . [ Ondřej Nový ] . * d/control: Remove ancient X-Python-Version field * d/control: Remove ancient X-Python3-Version field Checksums-Sha1: 899557f47d11a9632d5e6e83fa0920acc1f7cd4e 2188 python-zxcvbn_4.4.27-1.dsc 01875443ba099cc2d108cd58cc5c11afbc6a345f 366512 python-zxcvbn_4.4.27.orig.tar.xz c437abfec7fc8f008c00a2f89eb7b298be72401d 2976 python-zxcvbn_4.4.27-1.debian.tar.xz 5d76ec8c5b7d3ad1bfbf5fa5fe772ec17f63b483 6573 python-zxcvbn_4.4.27-1_amd64.buildinfo Checksums-Sha256: 2b598339271be315fe2db77252d272b1c9e72cfe98179015a2d53a11b07f1da2 2188 python-zxcvbn_4.4.27-1.dsc 78353139810b69d0a517356b6a567c14bbf3e32ea68956f3f1e7ef68a09b0952 366512 python-zxcvbn_4.4.27.orig.tar.xz ac49d5766e9e2b11c1cb34388ebe56d8d1d65829a718feca9e3e11b50e4b5f85 2976 python-zxcvbn_4.4.27-1.debian.tar.xz 431bfbb35e7b8952c104f6f2493f128d1ce537c3ccb9a2b31a21b7928494ccca 6573 python-zxcvbn_4.4.27-1_amd64.buildinfo Files: e85974dcd11dc8053d7d38655f30a35b 2188 python optional python-zxcvbn_4.4.27-1.dsc e707e6d350fc63071c2f13ff9482a254 366512 python optional python-zxcvbn_4.4.27.orig.tar.xz 910217dc66b14a97d5a593679cae13a5 2976 python optional python-zxcvbn_4.4.27-1.debian.tar.xz 3c6ffc03910568fa31a1de6bbb32a6d6 6573 python optional python-zxcvbn_4.4.27-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEi3hoeGwz5cZMTQpICBa54Yx2K60FAlxjZA8ACgkQCBa54Yx2 K628iA/+M/6i5AEMOgpeXpdfEsFY0JQkqT959C0PI6N5eCNIhPSq1ZbNpRnJnmmf /VmV8mKW9/kyniJ
Bug#896489: Bug #896489 in python-zxcvbn marked as pending
Control: tag -1 pending Hello, Bug #896489 in python-zxcvbn reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/python-team/modules/python-zxcvbn/commit/53d060af7b27b2a79bd8867e0bccca32b77ca67f d/rules: do not install the zxcvbn binary in the python2 package. Closes: #896489 Signed-off-by: Mattia Rizzolo (this message was generated automatically) -- Greetings https://bugs.debian.org/896489
Processed: Bug #896489 in python-zxcvbn marked as pending
Processing control commands: > tag -1 pending Bug #896489 [python-zxcvbn,python3-zxcvbn] python-zxcvbn,python3-zxcvbn: both ship /usr/bin/zxcvbn Added tag(s) pending. -- 896489: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896489 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#922178: marked as done (/lib/security/pam_unix.so: cannot open shared object file: No such file or directory)
Your message dated Wed, 13 Feb 2019 00:07:49 + with message-id and subject line Bug#922178: fixed in pam 1.3.1-2 has caused the Debian Bug report #922178, regarding /lib/security/pam_unix.so: cannot open shared object file: No such file or directory 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.) -- 922178: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922178 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libpam-runtime Version: 1.3.1-1 User does aptitude upgrade. Upgrade finishes normally. But user notes cronjobs no longer fire on time... Looking in the logs, Feb 13 05:59:01 jidanni5 cron[485]: Authentication failure Feb 13 05:59:01 jidanni5 CRON[5596]: Authentication failure Feb 13 06:09:01 jidanni5 CRON[5919]: PAM unable to dlopen(pam_unix.so): /lib/security/pam_unix.so: cannot open shared object file: No such file or directory Feb 13 06:09:01 jidanni5 CRON[5919]: PAM adding faulty module: pam_unix.so Feb 13 06:09:01 jidanni5 cron[485]: Authentication failure Feb 13 06:09:01 jidanni5 CRON[5919]: Authentication failure --- End Message --- --- Begin Message --- Source: pam Source-Version: 1.3.1-2 We believe that the bug you reported is fixed in the latest version of pam, 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 922...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Steve Langasek (supplier of updated pam package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 12 Feb 2019 23:52:04 + Source: pam Architecture: source Version: 1.3.1-2 Distribution: unstable Urgency: medium Maintainer: Steve Langasek Changed-By: Steve Langasek Closes: 922178 Changes: pam (1.3.1-2) unstable; urgency=medium . * Bump the version check for service restarts to 1.3.1-2. Closes: #922178. * Drop hard-coded pre-dep on libpam0g, now superseded by shlibdeps. Checksums-Sha1: 3a087decee745ceb1ec22b74048dcfe43a9205ef 2648 pam_1.3.1-2.dsc 286e78b32cbfd2cec1ef0cdf10a84e7ee65c2e69 113896 pam_1.3.1-2.debian.tar.xz Checksums-Sha256: 6e03f56d4b9ff39718b10068681d9e74ac58852056dad6f01301f5f3da5d5765 2648 pam_1.3.1-2.dsc 2b0bdead1a5e1af44ad635ad6b34f8e7cd5f4f74711dd8bb13de825473f3c06d 113896 pam_1.3.1-2.debian.tar.xz Files: d108a9537d0f8dacef2bcc43b7513665 2648 libs optional pam_1.3.1-2.dsc b433e3e5a293cde8089ca8fba79b0d92 113896 libs optional pam_1.3.1-2.debian.tar.xz -BEGIN PGP SIGNATURE- iQJGBAEBCgAwFiEErEg/aN5yj0PyIC/KVo0w8yGyEz0FAlxjXJkSHHZvcmxvbkBk ZWJpYW4ub3JnAAoJEFaNMPMhshM92OgP/0if+wsAG9URuUkD/szCudK47aCZzKQB x6DHggZgwz/4c11uiP6xrFvFHhbkNg+QfeaWTeFa8C1opKsudYt/sbm+N3KbuEr9 tQQzrKraqFTZo/83g3lDariQarBL1cdmuQrpwRx1lLxDpFH85PO02cKGoCYw/tAH +pBEJ0nzrf0BUw1EkRa4fFkVt9ISdAu90Y3Xpn+sskzKNXcBA1GEc3PZKK/+5wGV s1BpKT9Xuz6ENxYXQoN4UhVi7MtQZQkp2YTnVrqPN3cfnViBwmEcBXqfUboQ9GAM ndwAIqfbDkujJzuEOvMBsZsZR7V0i8QXdvVD3Ymi++jS+ksgWIoU8pvulJnseedV rRXKIPvO7+rBLUVfeYQrWFggHjGCOAJxqJJO8L4+vjvFsNoj0hGs0hwqg6KpaaW3 2p9vN5TqD3tP05gBGXP97/+nTs3bw4X/KCFWq6iCiunDczIJlKj7suClIEnMEbnq nYlDhTO5LrakqzxjNxmfhQaQZKI1aIzhhLX1NCpVLxeIl7TgU1QtW/MgppU95wah GmysRMYIDQQCZPAsqjMhHx5O+U6D3FH+pgOMea5mS7gGQfPk3Ytd2M5+J08Jhf0k MbYO/5hto+baOW8Ibabq8pd5TGVwVY3MH8dk5kdwlJnau3lJlD1brkEY7XDqrOut an3+DDFkLz75 =lugc -END PGP SIGNATURE End Message ---
Bug#918896: marked as done (matplotlib2: FTBFS with Sphinx 1.8: directive u'math' is already registered, it will be overridden)
Your message dated Wed, 13 Feb 2019 00:07:04 + with message-id and subject line Bug#918896: fixed in matplotlib2 2.2.3-6 has caused the Debian Bug report #918896, regarding matplotlib2: FTBFS with Sphinx 1.8: directive u'math' is already registered, it will be overridden 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.) -- 918896: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918896 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: matplotlib2 Version: 2.2.3-5 Severity: important User: python-modules-t...@lists.alioth.debian.org Usertags: sphinx1.8 Dear Maintainer, matplotlib2 fails to build with Sphinx 1.8, currently available in experimental: # build the doc [...] /usr/bin/make -C doc html make[1]: Entering directory '/<>/doc' Running Sphinx v1.8.3 Warning, treated as error: while setting up extension matplotlib.sphinxext.mathmpl: directive u'math' is already registered, it will be overridden make[1]: *** [Makefile:20: html] Error 2 This was fixed in matplotlib 3.x in this commit, please backport it: https://github.com/matplotlib/matplotlib/commit/f87e9f46daf42ad7 That commit switches from generating PNG images for math formulas to MathJax library, which renders the math formulas on client side. To package it for Debian, please add this line to conf.py: mathjax_path = 'file:///usr/share/javascript/mathjax/MathJax.js?config=TeX-AMS-MML_HTMLorMML' and make your documentation package depend on libjs-mathjax. Also upstream has noticed that some math renders incorrectly with MathJax, there is a follow-up commit which fixes it: https://github.com/matplotlib/matplotlib/commit/a101de79650e077a -- Dmitry Shachnev signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: matplotlib2 Source-Version: 2.2.3-6 We believe that the bug you reported is fixed in the latest version of matplotlib2, 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 918...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sandro Tosi (supplier of updated matplotlib2 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 12 Feb 2019 17:51:04 -0500 Source: matplotlib2 Binary: python-matplotlib python-matplotlib-dbg python-matplotlib2-data python-matplotlib2-doc Architecture: source amd64 all Version: 2.2.3-6 Distribution: unstable Urgency: medium Maintainer: Sandro Tosi Changed-By: Sandro Tosi Description: python-matplotlib - Python based plotting system in a style similar to Matlab python-matplotlib-dbg - Python based plotting system (debug extension) python-matplotlib2-data - Python based plotting system (data package) python-matplotlib2-doc - Python based plotting system (documentation package) Closes: 918819 918896 Changes: matplotlib2 (2.2.3-6) unstable; urgency=medium . * debian/control - update Vcs-* fields * debian/patches/bts918819-numpy-deprecates-asscalar-gh12508.patch - fix DeprecationWarnings with Numpy 1.16; Closes: #918819 * debian/patches/bts918896-doc-backports-for-2.2.x-gh13258.patch - import upstream doc backports patches for 2.2.x branch; Closes: #918896 * debian/control - bump Standards-Version to 4.3.0 (no changes needed) * debian/copyright - extend packaging copyright years Checksums-Sha1: 2a3f2d623a89a179f1b81a72cb3da6dbfdd23095 3587 matplotlib2_2.2.3-6.dsc ecda209be9975643bd2e502b9ac1a5efd27560e0 38256 matplotlib2_2.2.3-6.debian.tar.xz 844d5457712d5d375ec11a8156391d2ec0074f10 24223 matplotlib2_2.2.3-6_amd64.buildinfo 5c0f3a4a39c221cc900e958de48fa094b31bad2d 3693920 python-matplotlib-dbg_2.2.3-6_amd64.deb 54800ec6c81391f03714c383b8956cc02583b736 4123676 python-matplotlib2-data_2.2.3-6_all.deb c6a19252478188a0e02e252e3b3122ea9fefd3f0 64347796 python-matplotlib2-doc_2.2.3-6_all.deb 60f6ca9d3c146256e7d5965a809988f4ce65dc18 5072696 python-matplotlib_2.2.3-6_amd64.deb Checksums-Sha256: cdf818c26244b792f4224c851ea6a39ad51bf5869ef9783e558cf8586536932b 3587 matplotlib2_2.2.3-6.dsc 2498f0c8ebd2b9bb428d35ccd6b05084bc4eda3c0d078b5edd2f8fd969b9dec0 38256 matplotlib2_2.2.3-6.debian.ta
Bug#922184: Stretch-backports linux-image-cloud-amd64 broken
Package: linux-image-cloud-amd64 Severity: critical In stretch-backports the linux-image-cloud-amd64 package depends upon linux-image-4.19.0-0.bpo.2-cloud-amd64 however that package is not available See https://packages.debian.org/stretch-backports/linux-image-cloud-amd64 There does seem to be an unsigned version at https://packages.debian.org/stretch-backports/linux-image-4.19.0-0.bpo.2-cloud-amd64-unsigned
Processed: notfound 922145 in 1.1.2-1, found 922145 in 1.2.0-1
Processing commands for cont...@bugs.debian.org: > # Fix found version > notfound 922145 1.1.2-1 Bug #922145 [irssi] irssi: trying to overwrite '/usr/share/irssi/help/otr', which is also in package irssi-plugin-otr No longer marked as found in versions irssi/1.1.2-1. > found 922145 1.2.0-1 Bug #922145 [irssi] irssi: trying to overwrite '/usr/share/irssi/help/otr', which is also in package irssi-plugin-otr Marked as found in versions irssi/1.2.0-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 922145: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922145 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 922178, severity of 922178 is serious
Processing commands for cont...@bugs.debian.org: > tags 922178 + confirmed pending Bug #922178 [libpam-runtime] /lib/security/pam_unix.so: cannot open shared object file: No such file or directory Added tag(s) pending and confirmed. > severity 922178 serious Bug #922178 [libpam-runtime] /lib/security/pam_unix.so: cannot open shared object file: No such file or directory Severity set to 'serious' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 922178: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922178 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed (with 1 error): forcibly merging 922178 922183
Processing commands for cont...@bugs.debian.org: > forcemerge 922178 922183 Bug #922178 [libpam-runtime] /lib/security/pam_unix.so: cannot open shared object file: No such file or directory Unable to merge bugs because: package of #922183 is 'libpam0g' not 'libpam-runtime' Failed to forcibly merge 922178: Did not alter merged bugs. > thanks Stopping processing here. Please contact me if you need assistance. -- 922178: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922178 922183: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922183 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#922183: libpam0g: upgrade to 1.3.1-1 breaks running xscreensaver, locking user out of session
Package: libpam0g Version: 1.3.1-1 Severity: grave Justification: causes non-serious data loss Dear Maintainer, after upgrading: libpam-modules (1.1.8-4 => 1.3.1-1) libpam-modules-bin (1.1.8-4 => 1.3.1-1) libpam-runtime (1.1.8-4 => 1.3.1-1) libpam0g (1.1.8-4 => 1.3.1-1) libpam0g-dev (1.1.8-4 => 1.3.1-1) a running xscreensaver instance can no longer authenticate: Feb 13 10:46:22 ripley xscreensaver[977]: PAM unable to dlopen(pam_unix.so): /lib/security/pam_unix.so: cannot open shared object file: No such file or directory Feb 13 10:46:22 ripley xscreensaver[977]: PAM adding faulty module: pam_unix.so Feb 13 10:46:22 ripley xscreensaver[977]: FAILED LOGIN 1 ON DISPLAY ":0.0", FOR "ben" Workaround is using remote access to kill xscreensaver. After a system restart, xscreensaver works normally. In the absence of remote access, a system reset may be required, which may result in the loss of unsaved user data. libpam0g upgrade should test for a running xscreensaver instance and require it to be stopped before upgrade. Kind regards, Ben. -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-2-amd64 (SMP w/8 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 libpam0g depends on: ii debconf [debconf-2.0] 1.5.70 ii libaudit1 1:2.8.4-2 ii libc6 2.28-7 libpam0g recommends no packages. Versions of packages libpam0g suggests: pn libpam-doc -- debconf information: libpam0g/restart-services: * libraries/restart-without-asking: false libpam0g/xdm-needs-restart: libpam0g/restart-failed:
Bug#918623: marked as done (dizzy: Your vendor has not defined OpenGL macro GL_FRAMEBUFFER_EXT)
Your message dated Tue, 12 Feb 2019 23:22:41 + with message-id and subject line Bug#918623: fixed in libopengl-perl 0.7000+dfsg-2 has caused the Debian Bug report #918623, regarding dizzy: Your vendor has not defined OpenGL macro GL_FRAMEBUFFER_EXT 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.) -- 918623: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918623 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: dizzy Version: 0.3-3 Severity: normal Dear Maintainer, this is the output of dizzy when started on a desktop PC with amd graphics or a qemu amd64 VM, both running current buster: $ dizzy GPU features: [x] GLSL [x] FBOs Your vendor has not defined OpenGL macro GL_FRAMEBUFFER_EXT, used at /usr/share/perl5/Dizzy/TextureGenerator.pm line 101. I tested the same qemu VM with stretch and there it was working. After some tests I found it stopped working when libopengl-perl in version 0.7000+dfsg-1 entered testing in 2017-08-12. But I am uncertain if the fault is in package dizzy or libopengl-perl. Kind regards, Bernhard -- System Information: Debian Release: buster/sid APT prefers testing-debug APT policy: (500, 'testing-debug'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-1-amd64 (SMP w/16 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages dizzy depends on: ii libconvert-color-perl 0.11-2 ii libopengl-perl 0.7000+dfsg-1+b1 ii libsdl-perl2.548-1+b1 ii perl 5.28.1-3 dizzy recommends no packages. dizzy suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: libopengl-perl Source-Version: 0.7000+dfsg-2 We believe that the bug you reported is fixed in the latest version of libopengl-perl, 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 918...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Florian Schlichting (supplier of updated libopengl-perl package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 12 Feb 2019 23:03:05 +0100 Source: libopengl-perl Architecture: source Version: 0.7000+dfsg-2 Distribution: unstable Urgency: medium Maintainer: Debian Perl Group Changed-By: Florian Schlichting Closes: 886496 918623 Changes: libopengl-perl (0.7000+dfsg-2) unstable; urgency=medium . [ Damyan Ivanov ] * declare conformance with Policy 4.1.3 (no changes needed) . [ Salvatore Bonaccorso ] * Update Vcs-* headers for switch to salsa.debian.org . [ Florian Schlichting ] * Build without OpenGL Extension exclusions, as if dist=NO_EXCLUSIONS was given (closes: #918623) * Add a patch to prevent a segfault from pointer truncation, contributed by Thomas Kremer (closes: #886496) * Update years of packaging copyright * Bump dh compat to level 12 * Declare compliance with Debian Policy 4.3.0 * Fix another typo via spelling.patch * Remove x bit from more examples * Update repacking to the "modern way" Checksums-Sha1: ba7409e0da0007aa6105820e0ee80946aed63e0c 2271 libopengl-perl_0.7000+dfsg-2.dsc 71530e3e893c0f8cb2dfcb0acb8f8045d0801d3c 12324 libopengl-perl_0.7000+dfsg-2.debian.tar.xz a17c4dfc3fc37446720458e36729a480e3762e21 8569 libopengl-perl_0.7000+dfsg-2_amd64.buildinfo Checksums-Sha256: 9476d245be0d7bf29205ec0be6e48356bceeb1185e561cc8ac4f4a0f50c7c763 2271 libopengl-perl_0.7000+dfsg-2.dsc 48f0e1f7f106bb347a343c4714e6ed4360c2614e5f75dc7f5511bcd61729eef4 12324 libopengl-perl_0.7000+dfsg-2.debian.tar.xz 1ff63b096cf77e8ff4f983fb3c76473033e7a9ac0d8288f0752965f272bd2a9e 8569 libopengl-perl_0.7000+dfsg-2_amd64.buildinfo Files: d0a67e7d6460d2d0732b112043c8150b 2271 perl optional libopengl-perl_0.7000+dfsg-2.dsc bed3152878aa4bba2e9af19fbc5a5217 12324 perl optional libopengl-perl_0.7000+dfsg-2.debian.tar.xz 8b1ced2510104c83f3a318ad3e4790cf 8569 perl optional libopengl-perl_0.7000+dfsg-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAE
Processed: retitle 922059 to flatpak: CVE-2019-8308: vulnerability similar to runc CVE-2019-5736 involving /proc/self/exe
Processing commands for cont...@bugs.debian.org:
> retitle 922059 flatpak: CVE-2019-8308: vulnerability similar to runc
> CVE-2019-5736 involving /proc/self/exe
Bug #922059 {Done: Simon McVittie } [flatpak] flatpak:
vulnerability similar to runc CVE-2019-5736 involving /proc/self/exe
Changed Bug title to 'flatpak: CVE-2019-8308: vulnerability similar to runc
CVE-2019-5736 involving /proc/self/exe' from 'flatpak: vulnerability similar to
runc CVE-2019-5736 involving /proc/self/exe'.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
922059: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922059
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: Re: update-alternatives: error: /var/lib/dpkg/alternatives/mpi corrupt: slave link same as main link /usr/bin/mpicc
Processing control commands:
> reopen -1
Bug #896189 {Done: Alastair McKinstry } [openmpi-bin]
update-alternatives: error: /var/lib/dpkg/alternatives/mpi corrupt: slave link
same as main link /usr/bin/mpicc
Bug #896644 {Done: Alastair McKinstry } [openmpi-bin]
openmpi-bin: postinst script fails
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions openmpi/3.0.1-8.
No longer marked as fixed in versions openmpi/3.0.1-8.
--
896189: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896189
896644: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896644
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#896189: update-alternatives: error: /var/lib/dpkg/alternatives/mpi corrupt: slave link same as main link /usr/bin/mpicc
Control: reopen -1 Hi, On Fri, Apr 20, 2018 at 06:56:24PM +0300, Adrian Bunk wrote: [...] > Setting up openmpi-bin (3.0.1-6) ... > update-alternatives: using /usr/bin/mpirun.openmpi to provide /usr/bin/mpirun > (mpirun) in auto mode > update-alternatives: error: /var/lib/dpkg/alternatives/mpi corrupt: slave > link same as main link /usr/bin/mpicc > dpkg: error processing package openmpi-bin (--configure): > installed openmpi-bin package post-installation script subprocess returned > error exit status 2 It seems this issue is back in builds for netpipe: https://buildd.debian.org/status/fetch.php?pkg=netpipe&arch=amd64&ver=3.7.2-7.4%2Bb5&stamp=1550010019&raw=0 Setting up openmpi-bin (3.1.3-10) ... update-alternatives: using /usr/bin/mpirun.openmpi to provide /usr/bin/mpirun (mpirun) in auto mode update-alternatives: error: /var/lib/dpkg/alternatives/mpi corrupt: slave link same as main link /usr/bin/mpicc dpkg: error processing package openmpi-bin (--configure): installed openmpi-bin package post-installation script subprocess returned error exit status 2 Ivo
Processed: unarchive 896189
Processing commands for cont...@bugs.debian.org:
> unarchive 896189
Bug #896189 {Done: Alastair McKinstry } [openmpi-bin]
update-alternatives: error: /var/lib/dpkg/alternatives/mpi corrupt: slave link
same as main link /usr/bin/mpicc
Bug #896644 {Done: Alastair McKinstry } [openmpi-bin]
openmpi-bin: postinst script fails
Unarchived Bug 896189
Unarchived Bug 896644
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
896189: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896189
896644: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896644
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#882641: New version of statsmodels is out possibly fixing important bug - any volunteer
Hi Andreas, > Currently the package in Git does not build due to #921779. I admit I > have no idea why #917754 occures but my comparison with python-cycler > (which is able to find the module named > 'matplotlib.sphinxext.only_directives') Gave me some hope that switching > back from python3-sphinx to python-sphinx will solve this. matplotlib.sphinxext.only_directives was removed from matplotlib but you should be fairly easily able to fix up the documentation build, for example: https://sources.debian.org/src/python-periodictable/sid/debian/patches/sphinx-only-directive.patch/ cheers Stuart -- Stuart Prescotthttp://www.nanonanonano.net/ stu...@nanonanonano.net Debian Developer http://www.debian.org/ stu...@debian.org GPG fingerprint90E2 D2C1 AD14 6A1B 7EBB 891D BBC1 7EBB 1396 F2F7
Bug#916468: marked as done (dune: /usr/bin/dune is already provided by the whitedune package)
Your message dated Tue, 12 Feb 2019 22:56:06 + with message-id and subject line Bug#916468: fixed in whitedune 0.30.10-2.2 has caused the Debian Bug report #916468, regarding dune: /usr/bin/dune is already provided by the whitedune package to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 916468: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916468 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: dune Version: 1.6.2-1 Severity: serious User: trei...@debian.org Usertags: edos-file-overwrite 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 dune. Preparing to unpack .../dune_1.6.2-1_amd64.deb ... Unpacking dune (1.6.2-1) ... dpkg: error processing archive /var/cache/apt/archives/dune_1.6.2-1_amd64.deb (--unpack): trying to overwrite '/usr/bin/dune', which is also in package whitedune 0.30.10-2.1+b2 Errors were encountered while processing: /var/cache/apt/archives/dune_1.6.2-1_amd64.deb This is a serious bug as it makes installation fail, and violates sections 7.6.1 and 10.1 of the policy. An optimal solution would consist in only one of the packages installing that file, and renaming or removing the file in the other package. Depending on the circumstances you might also consider Replace relations or file diversions. If the conflicting situation cannot be resolved then, as a last resort, the two packages have to declare a mutual Conflict. Please take into account that Replaces, Conflicts and diversions should only be used when packages provide different implementations for the same functionality. Here is a list of files that are known to be shared by both packages (according to the Contents file for sid/amd64, which may be slightly out of sync): usr/bin/dune usr/share/man/man1/dune.1.gz 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 whitedune=0.30.10-2.1+b2_dune=1.6.2-1.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: whitedune Source-Version: 0.30.10-2.2 We believe that the bug you reported is fixed in the latest version of whitedune, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 916...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Paul Gevers (supplier of updated whitedune package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 12 Feb 2019 22:32:01 +0100 Source: whitedune Binary: whitedune whitedune-docs Architecture: source Version: 0.30.10-2.2 Distribution: unstable Urgency: medium Maintainer: Debian Multimedia Maintainers Changed-By: Paul Gevers Description: whitedune - graphical VRML97/X3D viewer, editor, 3D modeller and animation to whitedune-docs - documentation for whitedune Closes: 916468 Changes: whitedune (0.30.10-2.2) unstable; urgency=medium . * Non-maintainer upload. . [ Johannes Brandstätter ] * Update watch file to new upstream release page . [ Ondřej Nový ] * d/control: Set Vcs-* to salsa.debian.org . [ Felipe Sateler ] * Change maintainer address to debian-multime...@lists.debian.org . [ Ondřej Nový ] * d/rules: Remove trailing whitespaces . [ Paul Gevers ] * Drop /usr/bin/dune softlink and dune(1) man-page (Closes: #916468) Checksums-Sha1: 07145d5978badb1e8cc9e3089fa6ccec9f3fc756 1845 whitedune_0.30.10-2.2.dsc 18a6a177b53d6a4cfb026d70f7cbf860aa2837cd 9396 whitedune_0.30.10-2.2.debian.tar.xz Checksums-Sha256: b5d3fff5343b6eb62e5b09ab83533236cc7c35ec97df192e3e70fcea06b881ad 1845 whitedune_0.30.10-2.2.dsc 99b25399f890eb4ceaa27ccee4ab9cfe255a63328e522633f80a0b483c03 9396 whitedune_0.30.10-2.2.debian.tar.xz Files: 191de78a50607749d994eb736dea9e5c 1845 graphics optional whitedune_0.30.10-2.2.dsc 7d0feb6561778ebcdf02708e44651187 9396 graphics optional whitedune_0.30.10-2.2.debian.tar.xz -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAlxjP
Processed (with 1 error): Re: Bug#921343: nextcloud-desktop: Synchronisation fails with "PROPFIND Reply is not XML Formatted"
Processing control commands: > severity -1 normal Bug #921343 [nextcloud-desktop] nextcloud-desktop: Synchronisation fails with "PROPFIND Reply is not XML Formatted" Severity set to 'normal' from 'grave' > forwarded https://github.com/nextcloud/desktop/issues/1025 Unknown command or malformed arguments to command. -- 921343: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921343 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#921343: nextcloud-desktop: Synchronisation fails with "PROPFIND Reply is not XML Formatted"
Control: severity -1 normal Control: forwarded https://github.com/nextcloud/desktop/issues/1025 Hey, > Nextcloud client fails to synchronize files on an up to date Nextcloud > server (15.0.2.0) with this error: I can't reproduce this error with Nextcloud 15.0.4.0. This is surely not an client error it is a server one. That's why lowering the severity. > This completely breaks the client and makes it unusable, as > synchronization simply doesn't happen. It seems earlier versions of this > package didn't have this problem, as users online report downgrading to > 2.4.X successfully fixed the problem. There is no nextcloud desktop 2.4.X, before 2.5.0 there was only owncloud- client, that was themed for Nextcloud. regards, hefee signature.asc Description: This is a digitally signed message part.
Processed: Bug #918623 in libopengl-perl marked as pending
Processing control commands: > tag -1 pending Bug #918623 [libopengl-perl] dizzy: Your vendor has not defined OpenGL macro GL_FRAMEBUFFER_EXT Added tag(s) pending. -- 918623: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918623 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#918623: Bug #918623 in libopengl-perl marked as pending
Control: tag -1 pending Hello, Bug #918623 in libopengl-perl reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/perl-team/modules/packages/libopengl-perl/commit/17dfb723a4c87ddf8820e626bb5ddccea6e87646 Build without OpenGL Extension exclusions, as if dist=NO_EXCLUSIONS was given (closes: #918623) note that the exclusions we were using were generated with OpenGL v1.2 and do not exclude versions newer than 2.0, while OpenGL features and backward compatibility start to become interesting after 3.0 - which we didn't exclude. So presumably this does not actually affect the situation where the libraries would support an extension that the driver doesn't provide... (this message was generated automatically) -- Greetings https://bugs.debian.org/918623
Bug#919356: Licensing of include/linux/hash.h
Jens Axboe writes: > On 2/11/19 11:27 PM, Ben Finney wrote: > > If, on the other hand, the file is to be free software, there would need > > to be a clear grant of some free software license to that work. > > FWIW, fio.c includes the following mention: > > * The license below covers all files distributed with fio unless otherwise > * noted in the file itself. > > followed by the GPL v2 license. Great! That does appear to be a positive assertion from the copyright holder, that we have a grant to use that work under GPLv2. That written grant of license can be used in the Debian package to demonstrate our license to the work. > I'll go through and add SPDX headers to everything to avoid wasting > anymore time on this nonsense. Not necessary from my point of view for this specific case, because we have the clear explicit grant of license. Don't let me stop you from doing the good work of documenting more clearly :-) -- \ “Come on Milhouse, there’s no such thing as a soul! It’s just | `\ something they made up to scare kids, like the Boogie Man or | _o__) Michael Jackson.” —Bart, _The Simpsons_ | Ben Finney
Bug#918623: dizzy: Your vendor has not defined OpenGL macro GL_FRAMEBUFFER_EXT
> > It's probably a bit late in the release cycle to "just find out" by > > uploading a -2 with that modified patch. > > ... but its even worse to do nothing since this is an RC bug and this > package as well as its rdepends would be excluded from next release if > the bug is not fixed. I'm coming to the same conclusion, so here we go - upload coming shortly... Florian
Bug#922093: marked as done (node-commander: FTBFS in sid (AssertionError: expected '' to be 'SIGHUPn'))
Your message dated Tue, 12 Feb 2019 21:49:33 + with message-id and subject line Bug#922093: fixed in node-commander 2.12.2-3 has caused the Debian Bug report #922093, regarding node-commander: FTBFS in sid (AssertionError: expected '' to be 'SIGHUPn') 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.) -- 922093: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922093 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:node-commander Version: 2.12.2-2 Severity: serious Tags: ftbfs Dear maintainer: I tried to build this package in sid but it failed: [...] debian/rules build-indep dh build-indep --with nodejs dh_update_autotools_config -i dh_autoreconf -i dh_auto_configure -i dh_auto_test --buildsystem=nodejs -i /bin/sh -e debian/tests/pkg-js/test make[1]: Entering directory '/<>' [90m test.arguments.js[0m [36mâ[0m [90m test.command.action.js[0m [36mâ[0m [90m test.command.alias.help.js[0m [36mâ[0m [90m test.command.allowUnknownOption.js[0m [36mâ[0m [90m test.command.executableSubcommand.js[0m [36mâ[0m [90m test.command.executableSubcommand.signals.hup.js[0m [31mâ[0m /usr/lib/nodejs/should/lib/assertion.js:72 throw new AssertionError(params); ^ AssertionError: expected '' to be 'SIGHUP\n' at Assertion.fail (/usr/lib/nodejs/should/lib/assertion.js:92:17) at Assertion.value (/usr/lib/nodejs/should/lib/assertion.js:164:19) at Timeout._onTimeout (/<>/test/test.command.executableSubcommand.signals.hup.js:19:19) at ontimeout (timers.js:436:11) at tryOnTimeout (timers.js:300:5) at listOnTimeout (timers.js:263:5) at Timer.processTimers (timers.js:223:10) make[1]: *** [Makefile:5: test] Error 1 make[1]: Leaving directory '/<>' dh_auto_test: /bin/sh -e debian/tests/pkg-js/test returned exit code 2 make: *** [debian/rules:8: build-indep] Error 2 dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit status 2 The build was made in my autobuilder with "dpkg-buildpackage -A" and it also fails here: https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/node-commander.html If this is really a bug in one of the build-depends, please use reassign and affects, so that this is still visible in the BTS web page for this package. Thanks. --- End Message --- --- Begin Message --- Source: node-commander Source-Version: 2.12.2-3 We believe that the bug you reported is fixed in the latest version of node-commander, 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 922...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Xavier Guimard (supplier of updated node-commander package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 12 Feb 2019 22:25:03 +0100 Source: node-commander Binary: node-commander Architecture: source Version: 2.12.2-3 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Xavier Guimard Closes: 922093 Description: node-commander - Complete solution for Node.js command-line interfaces Changes: node-commander (2.12.2-3) unstable; urgency=medium . * Ignore signal based tests (Closes: #922093) Checksums-Sha1: 04c97683b1597d4d46478f0b8392794437240cab 2133 node-commander_2.12.2-3.dsc 8b9dc8a0265d1673b522970da6834fae5b39e360 3544 node-commander_2.12.2-3.debian.tar.xz Checksums-Sha256: 14b4d2eac5da2a0a1c15e635567945988521bf3c142911200a5867592f9da99c 2133 node-commander_2.12.2-3.dsc 0b48f681a6bf00a348af9ba6eae1e361cafe2eabc1b855c9c2ce7696740fae20 3544 node-commander_2.12.2-3.debian.tar.xz Files: 1768f68b0225223ec409328ef2380b9d 2133 javascript optional node-commander_2.12.2-3.dsc 0672cbb41282f1bce0ac47912e38a1f0 3544 javascript optional node-commander_2.12.2-3.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAlxjOjkACgkQ9tdMp8mZ 7ulXxRAAgVjvmelXLpX5fjwajZTQSRO6NLl36DhAepHyoLOyL4pb266tjsFTc58V yxMMcxSy
Processed: Bug #922093 in node-commander marked as pending
Processing control commands: > tag -1 pending Bug #922093 [src:node-commander] node-commander: FTBFS in sid (AssertionError: expected '' to be 'SIGHUPn') Added tag(s) pending. -- 922093: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922093 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#922093: Bug #922093 in node-commander marked as pending
Control: tag -1 pending Hello, Bug #922093 in node-commander reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/js-team/node-commander/commit/9b83abeb36f914793638fbfefa94e7e67158f7bf Ignore signal based tests Closes: #922093 (this message was generated automatically) -- Greetings https://bugs.debian.org/922093
Bug#919898: marked as done (ceph-common: missing Breaks+Replaces: ceph-base (<< 12.2.10+dfsg1-1~))
Your message dated Tue, 12 Feb 2019 21:05:52 + with message-id and subject line Bug#919898: fixed in ceph 12.2.11+dfsg1-1 has caused the Debian Bug report #919898, regarding ceph-common: missing Breaks+Replaces: ceph-base (<< 12.2.10+dfsg1-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.) -- 919898: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919898 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: ceph-common Version: 12.2.10+dfsg1-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Control: affects -1 + ceph-osd Hi, during a test with piuparts I noticed your package fails to upgrade from 'stretch'. It installed fine in 'stretch', then the upgrade to 'buster' 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#overwriting-files-and-replacing-packages-replaces >From the attached log (scroll to the bottom...): Preparing to unpack .../ceph-common_12.2.10+dfsg1-1_amd64.deb ... Unpacking ceph-common (12.2.10+dfsg1-1) over (10.2.5-7.2) ... dpkg: error processing archive /var/cache/apt/archives/ceph-common_12.2.10+dfsg1-1_amd64.deb (--unpack): trying to overwrite '/usr/share/bash-completion/completions/ceph', which is also in package ceph-base 10.2.5-7.2 Errors were encountered while processing: /var/cache/apt/archives/ceph-common_12.2.10+dfsg1-1_amd64.deb The bash completion was moved in the last upload without adding corresponding Breaks+Replaces. cheers, Andreas ceph-osd_12.2.10+dfsg1-1.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: ceph Source-Version: 12.2.11+dfsg1-1 We believe that the bug you reported is fixed in the latest version of ceph, 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 919...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Gaudenz Steinlin (supplier of updated ceph package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 12 Feb 2019 10:55:02 +0100 Source: ceph Binary: ceph ceph-base rbd-mirror rbd-nbd ceph-common ceph-mds ceph-mgr ceph-mon ceph-osd ceph-fuse rbd-fuse ceph-resource-agents librados2 librados-dev libradosstriper1 libradosstriper-dev librbd1 librbd-dev libcephfs2 libcephfs-dev librgw2 librgw-dev radosgw ceph-test python-ceph python3-ceph python-rados python3-rados python-rbd python3-rbd python-rgw python3-rgw python-cephfs python3-cephfs libcephfs-java libcephfs-jni rados-objclass-dev Architecture: source Version: 12.2.11+dfsg1-1 Distribution: unstable Urgency: medium Maintainer: Ceph Maintainers Changed-By: Gaudenz Steinlin Description: ceph - distributed storage and file system ceph-base - common ceph daemon libraries and management tools ceph-common - common utilities to mount and interact with a ceph storage cluste ceph-fuse - FUSE-based client for the Ceph distributed file system ceph-mds - metadata server for the ceph distributed file system ceph-mgr - Manager for the ceph distributed file system ceph-mon - monitor server for the ceph storage system ceph-osd - OSD server for the ceph storage system ceph-resource-agents - OCF-compliant resource agents for Ceph ceph-test - Ceph test and benchmarking tools libcephfs-dev - Ceph distributed file system client library (development files) libcephfs-java - Java library for the Ceph File System libcephfs-jni - Java Native Interface library for CephFS Java bindings libcephfs2 - Ceph distributed file system client library librados-dev - RADOS distributed object store client library (development files) librados2 - RADOS distributed object store client library libradosstriper-dev - RADOS striping interface (development files) libradosstriper1 - RADOS striping interface librbd-dev - RADOS block device client library (development files) librbd1- RADOS block device client library librgw-dev - RADOS client library (development files) librgw2- RADOS Gateway client library python-ceph - Meta-package for Python modules for the Ceph librar
Bug#922112: Fwd: Re: Bug#919356: Licensing of include/linux/hash.h
If bouncing does not work, this will do. -- Martin--- Begin Message --- On 2/11/19 11:27 PM, Ben Finney wrote: > Martin Steigerwald writes: > >> Well the file has in its header: >> >> /* Fast hashing routine for a long. >>(C) 2002 William Lee Irwin III, IBM */ >> >> /* >> * Knuth recommends primes in approximately golden ratio to the maximum >> * integer representable by a machine word for multiplicative hashing. >> * Chuck Lever verified the effectiveness of this technique: >> * http://www.citi.umich.edu/techreports/reports/citi-tr-00-1.pdf >> * >> * These primes are chosen to be bit-sparse, that is operations on >> * them can use shifts and additions instead of multiplications for >> * machines where multiplications are slow. >> */ >> >> It has been quite a while ago. I bet back then I did not regard this >> as license information since it does not specify a license. Thus I >> assumed it to be GPL-2 as the other files which have no license boiler >> plate. I.e.: Check file is it has different license, if not, then >> assume it has license as specified in COPYING. >> >> Not specifying a license can however also mean in this context that it >> has no license as the file contains copyright information from another >> author. > > If a work (even one file) “has no license”, that means no special > permissions are granted and normal copyright applies: All rights > reserved, i.e. not redistributable. So, no license is grounds to > consider a work non-free and non-redistributable. > > If, on the other hand, the file is to be free software, there would need > to be a clear grant of some free software license to that work. > > Given the confusion over this file, I would consider it a significant > risk to just assume we have GPLv2 permissions without being told that > explicitly by the copyright holder. Rather, the reason we are seeking a > clearly-granted free license for this one file, is because we are trying > to replace a probably non-free file with the same code in it. > > It seems we need to keep looking, and in the meantime assume we have no > free license in this file. FWIW, fio.c includes the following mention: * The license below covers all files distributed with fio unless otherwise * noted in the file itself. followed by the GPL v2 license. I'll go through and add SPDX headers to everything to avoid wasting anymore time on this nonsense. -- Jens Axboe --- End Message ---
Bug#919356: dwarves-dfsg: Copyright/licensing is unclear
Sorry, last mail should have gone to bug 922112 and have been a real bounce so that it is clear that it is from Jens. Somehow the initial bounce did not appear on bug 922112 so far. Sorry for the noise. -- Martin
Bug#919356: Licensing of include/linux/hash.h
On 2/11/19 11:27 PM, Ben Finney wrote: > Martin Steigerwald writes: > >> Well the file has in its header: >> >> /* Fast hashing routine for a long. >>(C) 2002 William Lee Irwin III, IBM */ >> >> /* >> * Knuth recommends primes in approximately golden ratio to the maximum >> * integer representable by a machine word for multiplicative hashing. >> * Chuck Lever verified the effectiveness of this technique: >> * http://www.citi.umich.edu/techreports/reports/citi-tr-00-1.pdf >> * >> * These primes are chosen to be bit-sparse, that is operations on >> * them can use shifts and additions instead of multiplications for >> * machines where multiplications are slow. >> */ >> >> It has been quite a while ago. I bet back then I did not regard this >> as license information since it does not specify a license. Thus I >> assumed it to be GPL-2 as the other files which have no license boiler >> plate. I.e.: Check file is it has different license, if not, then >> assume it has license as specified in COPYING. >> >> Not specifying a license can however also mean in this context that it >> has no license as the file contains copyright information from another >> author. > > If a work (even one file) “has no license”, that means no special > permissions are granted and normal copyright applies: All rights > reserved, i.e. not redistributable. So, no license is grounds to > consider a work non-free and non-redistributable. > > If, on the other hand, the file is to be free software, there would need > to be a clear grant of some free software license to that work. > > Given the confusion over this file, I would consider it a significant > risk to just assume we have GPLv2 permissions without being told that > explicitly by the copyright holder. Rather, the reason we are seeking a > clearly-granted free license for this one file, is because we are trying > to replace a probably non-free file with the same code in it. > > It seems we need to keep looking, and in the meantime assume we have no > free license in this file. FWIW, fio.c includes the following mention: * The license below covers all files distributed with fio unless otherwise * noted in the file itself. followed by the GPL v2 license. I'll go through and add SPDX headers to everything to avoid wasting anymore time on this nonsense. -- Jens Axboe
Bug#919356: Licensing of include/linux/hash.h
Jens Axboe - 12.02.19, 17:16: > On 2/11/19 11:27 PM, Ben Finney wrote: > > Martin Steigerwald writes: > >> Well the file has in its header: > >> > >> /* Fast hashing routine for a long. > >> > >>(C) 2002 William Lee Irwin III, IBM */ > >> > >> /* > >> > >> * Knuth recommends primes in approximately golden ratio to the > >> maximum * integer representable by a machine word for > >> multiplicative hashing. * Chuck Lever verified the effectiveness > >> of this technique: > >> * http://www.citi.umich.edu/techreports/reports/citi-tr-00-1.pdf > >> * > >> * These primes are chosen to be bit-sparse, that is operations on > >> * them can use shifts and additions instead of multiplications for > >> * machines where multiplications are slow. > >> */ > >> > >> It has been quite a while ago. I bet back then I did not regard > >> this > >> as license information since it does not specify a license. Thus I > >> assumed it to be GPL-2 as the other files which have no license > >> boiler plate. I.e.: Check file is it has different license, if > >> not, then assume it has license as specified in COPYING. > >> > >> Not specifying a license can however also mean in this context that > >> it has no license as the file contains copyright information from > >> another author. > > > > If a work (even one file) “has no license”, that means no special > > permissions are granted and normal copyright applies: All rights > > reserved, i.e. not redistributable. So, no license is grounds to > > consider a work non-free and non-redistributable. > > > > If, on the other hand, the file is to be free software, there would > > need to be a clear grant of some free software license to that > > work. > > > > Given the confusion over this file, I would consider it a > > significant > > risk to just assume we have GPLv2 permissions without being told > > that > > explicitly by the copyright holder. Rather, the reason we are > > seeking a clearly-granted free license for this one file, is > > because we are trying to replace a probably non-free file with the > > same code in it. > > > > It seems we need to keep looking, and in the meantime assume we have > > no free license in this file. > > FWIW, fio.c includes the following mention: > > * The license below covers all files distributed with fio unless > otherwise * noted in the file itself. > > followed by the GPL v2 license. I'll go through and add SPDX headers > to everything to avoid wasting anymore time on this nonsense. Thank you, Jens, for settling this. I did not remember that one. It may very well be that I have seen this note as I initially packaged fio as my first package for Debian about 10 years ago. I forwarded your mail and the one from Domenico with the SPDX patch to Debian bug #922112 fio: hash.h is not DFSG compliant https://bugs.debian.org/922112 which I closed before as you told already that hash.c is GPL-2. Thanks, -- Martin
Bug#922112: fio: hash.h is not DFSG compliant
Martin Steigerwald - 12.02.19, 21:08: > I am going to bounce two mails from Jens to this bug report, to > further clarify that hash.c is GPL-2. > > 1) Re: Bug#919356: Licensing of include/linux/hash.h > > 2) [PATCH] Add the SPDX header to include/linux/hash.h This second mail is from Domenico Andreoli. Sorry for attributing it to Jens. -- Martin
Bug#922112: Add the SPDX header to include/linux/hash.h
From: Domenico Andreoli It is unlikely that who contributes to this file is unaware of the kernel licensing but bringing the license statement into the file itself makes it properly reusable in different contexts. CC: Daniel Borkmann CC: Francesco Fusco CC: George Spelvin CC: Hannes Frederic Sowa CC: Ian Campbell CC: Jay Vosburgh CC: Jens Axboe CC: Linus Torvalds CC: Masami Hiramatsu CC: Matthew Wilcox CC: Nadia Yvette Chambers CC: Pavel Emelyanov Signed-off-by: Domenico Andreoli --- include/linux/hash.h |2 ++ 1 file changed, 2 insertions(+) Index: b/include/linux/hash.h === --- a/include/linux/hash.h +++ b/include/linux/hash.h @@ -1,3 +1,5 @@ +/* SPDX-License-Identifier: GPL-2.0 */ + #ifndef _LINUX_HASH_H #define _LINUX_HASH_H /* Fast hashing routine for ints, longs and pointers.
Bug#922112: fio: hash.h is not DFSG compliant
I am going to bounce two mails from Jens to this bug report, to further clarify that hash.c is GPL-2. 1) Re: Bug#919356: Licensing of include/linux/hash.h 2) [PATCH] Add the SPDX header to include/linux/hash.h I may clarify this in copyright file, in case it would be required, but for now I think that will suffice. Thanks, -- Martin signature.asc Description: This is a digitally signed message part.
Processed: severity of 922146 is important
Processing commands for cont...@bugs.debian.org: > severity 922146 important Bug #922146 [src:linux] after upgrade from jessie to stretch: hibernate leads to black screen and suspend to graphical glitches Severity set to 'important' from 'grave' > thanks Stopping processing here. Please contact me if you need assistance. -- 922146: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922146 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#918213: marked as done (python-skbio: autopkgtest fails with python-numpy (1:1.16.0~rc1-3))
Your message dated Tue, 12 Feb 2019 19:04:57 + with message-id and subject line Bug#918213: fixed in python-skbio 0.5.5-2 has caused the Debian Bug report #918213, regarding python-skbio: autopkgtest fails with python-numpy (1:1.16.0~rc1-3) 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.) -- 918213: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918213 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python-skbio Version: 0.5.5-1 Severity: normal Control: block 917323 by -1 Dear Maintainer, The autopkgtest for your package fail with python-numpy (1:1.16.0~rc1-3), this increased the required age of python-numpy which blocks the gdal transition. Please fix the autopkgtest of your package. Kind Regards, Bas --- End Message --- --- Begin Message --- Source: python-skbio Source-Version: 0.5.5-2 We believe that the bug you reported is fixed in the latest version of python-skbio, 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 918...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Tille (supplier of updated python-skbio package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 12 Feb 2019 19:34:10 +0100 Source: python-skbio Architecture: source Version: 0.5.5-2 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team Changed-By: Andreas Tille Closes: 917693 918213 Changes: python-skbio (0.5.5-2) unstable; urgency=medium . * Upstream has fixed numpy issue Closes: #917693, #918213 * debhelper 12 * Standards-Version: 4.3.0 Checksums-Sha1: 33c3c2ca0e11329f98c338c930b16c158faf3309 2608 python-skbio_0.5.5-2.dsc 68cd136d4685805edf3270cd716367e173cc2fd8 6760 python-skbio_0.5.5-2.debian.tar.xz 510b649de1e3e547e0abfd17c6523ceff3d84b44 9219 python-skbio_0.5.5-2_amd64.buildinfo Checksums-Sha256: 8106c8e86bb614da95449dfcaaa8f0b0ec3ad9a01d3839ab28e66b601e7bcd16 2608 python-skbio_0.5.5-2.dsc d5856ca9bc0525e6b8da316e1deb5ae055b2c9c6c6bbace2b30d5d5156004389 6760 python-skbio_0.5.5-2.debian.tar.xz 98aa656394615d1904e050674d9f38197c53916660364226e2c133626b69 9219 python-skbio_0.5.5-2_amd64.buildinfo Files: 09be211bfc333c975044caac25855a7b 2608 python optional python-skbio_0.5.5-2.dsc e8cd4968b8ca32cc12bd09e36137c688 6760 python optional python-skbio_0.5.5-2.debian.tar.xz c143bdaf9fafb83dd76f9d2dd11cf9dd 9219 python optional python-skbio_0.5.5-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJFBAEBCgAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAlxjFR4RHHRpbGxlQGRl Ymlhbi5vcmcACgkQV4oElNHGRtGGNA//UAlW4L3E307TJHuK80DcB2V6DCGTsUzL gGZ6zjMcvxoGTxOnZwSlSMw/QFQ+p800DpPqM+0BpPxC+sGUXluhXe+Wh0AZeGg6 4VsfSD+sWeiFV5wUhYFw4yAtV89z5URrhUxveIcWaHn/jY5WSlqAkqtTEjqGE2X1 q9TgY6QWIAYcSfe9eylHl0nRv6rcLAVvGPcZqQObAZVz3pSyDQ30lz1PG3E+/Nbp 0rLayg9y1B+0I+prgUjVMMtrkU/3qQTko2x1qC52n19Dsks+7xeFg2YjrFUaY7GO Qow9p3e0D/eoD9ZREcJYxm5t58Ky3356mhaYfCg+0xGfOycG0wImEXsukIKoB7Id Zdhpq08F+mLkciuv2SLlpqkgnzsvsSP8qcybAwCRak1jZ/c0HAFENnpROeCK77kj GDuRUPtU4Dk/vZjhb6z6YeRFsDaJULDC6FMFShxvYJ+Jo7bJV1s3ikxznXW0Ednu IAQia9SOrYAkffcoa31hEM0KZMWqm5xMg+LFb2MaoOxWcCaCxnw5ocgqiuyTiCWt rIl3wxda2iPzQS+SPVVG9xaM4MpWr8nkiSepJlrwBYWJl6M05YP+qDCpsTGtj14E tzeSdDDY+89RuLA64314foWJFVoRshXV8iPp29SMVT6INPttv8f2siTFXx08f+Yl C7xAiSXbE+U= =PSfI -END PGP SIGNATURE End Message ---
Bug#922149: marked as done (t-coffee ignores build failures)
Your message dated Tue, 12 Feb 2019 19:05:07 + with message-id and subject line Bug#922149: fixed in t-coffee 12.00.7fb08c2-3 has caused the Debian Bug report #922149, regarding t-coffee ignores build 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.) -- 922149: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922149 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: t-coffee Version: 12.00.7fb08c2-2 Severity: serious Justification: policy 4.6 t-coffee's debian/rules passes -i through dh_auto_build to make. That's the equivalent to ignoring all return codes of compiler invocations and thus violating the spirit of policy section 4.6. I argue that -i violates common sense. Its presence makes debugging build failures next to impossible. Please drop the -i flag. Helmut --- End Message --- --- Begin Message --- Source: t-coffee Source-Version: 12.00.7fb08c2-3 We believe that the bug you reported is fixed in the latest version of t-coffee, 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 922...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Tille (supplier of updated t-coffee package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 12 Feb 2019 19:37:40 +0100 Source: t-coffee Architecture: source Version: 12.00.7fb08c2-3 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team Changed-By: Andreas Tille Closes: 922149 Changes: t-coffee (12.00.7fb08c2-3) unstable; urgency=medium . * Do not use -i flag to ignore build failures Closes: #922149 * debhelper 12 * Secure URI in copyright format * Remove trailing whitespace in debian/changelog * Remove trailing whitespace in debian/rules Checksums-Sha1: 68c330f295050a1382bafe6f5461585662a4d8d7 2157 t-coffee_12.00.7fb08c2-3.dsc d9abd7fe36a91228ffa367050668b0e6d6000e3f 14740 t-coffee_12.00.7fb08c2-3.debian.tar.xz ae0c8707c0814b630578acad381eb5ec74f83faa 6072 t-coffee_12.00.7fb08c2-3_amd64.buildinfo Checksums-Sha256: 6a11826048d525e511cc9939e00055984330c91c1d8582c092b5f30f120f63bc 2157 t-coffee_12.00.7fb08c2-3.dsc 7d38af04638c09ebcc327c13a1273e49896e8885f5b21532c7bf4194eb14eda1 14740 t-coffee_12.00.7fb08c2-3.debian.tar.xz e292bf616a1161ea31015925525fc0bbdf5d1a3040118dab8dc4d0b375f022f1 6072 t-coffee_12.00.7fb08c2-3_amd64.buildinfo Files: b231f74605b5554c2ec110ded99f4f2b 2157 science optional t-coffee_12.00.7fb08c2-3.dsc 486fb70fd498c956e15afb61c74c231c 14740 science optional t-coffee_12.00.7fb08c2-3.debian.tar.xz cc8877f3ecde05851c5a3fd41baf1370 6072 science optional t-coffee_12.00.7fb08c2-3_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJFBAEBCgAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAlxjEy8RHHRpbGxlQGRl Ymlhbi5vcmcACgkQV4oElNHGRtGmohAAmeXlvSU9s3iFrIdPEnIPplbgdpUgMe6J IoA+x4hOfLjETwe3AV8a/T6q2ASH6iUOaenEJMXUkkJuTSrnF2BBop6LEZ4jXa7m cwJgMQw8M4LTN90s+AYoopupTFJ8LrOvycc//PGMBuxiKAKE8540XLDUiZ6dIF0v Xjv5ielWsbiotRQvGHAynv/rJT92SLNWooGGzAHh0RZbJex8REYQjpSjjeotNtZU yMljzVANzsFRz0ojbCtB+xi+DnE4fJlZowrW1Q5yvGmjKQ7Eg9qqebM7C6Ol4Etv /5lIf8Slo3jZbt6tZYSBq++EpyQO1JX5v9WfpA+CEkML8CjqghXeIztm6dmxahCc ss5F3xUlc2zyaWvHDJfeU5daseKYIStvSPDuvd8qOB3wz8hKwmsaAjiUgol3xcyo ai3yhwcBQ5iYw724sHa97H1LjeUBqr6HNxfhIzhEdx1C+lXX9cpByEYffOSzjoOc vvgji5Jydxp4/K8+wzd4IslsywPE0RmKZW9BXF3+VRhAHUiopC8s6a9mxRRPVW4R CCiRvrWh7DRvkJ/hchUMejGhJMbojajwmBTY7XX4Iy+gIizHldg6ImFkS2wuJY5L ZU+FZIDVlW+wP8bSbHZjgVKlZsdaVb4I3FyRb20bxnV5usJHbBRkYDeBvrwl9GWd dYMetyvMKgc= =CpAl -END PGP SIGNATURE End Message ---
Bug#882641: New version of statsmodels is out possibly fixing important bug - any volunteer
Hi, On Sun, Oct 28, 2018 at 07:32:43PM +0100, Andreas Tille wrote: > Hi Julian, > > On Sat, Oct 27, 2018 at 06:05:39PM +0200, Julian Taylor wrote: > > I have pushed an update to git that fixes the build for me and filed > > https://github.com/statsmodels/statsmodels/pull/5348 for the problem. > > I've uploaded statsmodels 0.9.0-1 to experimental. No idea whether we > might need a formal transition or whether we simply should upload to > unstable and "see what happens with dependencies". I'd welcome if > maintaniers with rdepends would give it a try and decide what might be > the best strategy. Unfortunately this issue went totally out of my focus and others obviously did not mind as well. Currently the package in Git does not build due to #921779. I admit I have no idea why #917754 occures but my comparison with python-cycler (which is able to find the module named 'matplotlib.sphinxext.only_directives') Gave me some hope that switching back from python3-sphinx to python-sphinx will solve this. Regarding bug #882641 I think droping the two tests containing the strings statsmodels/datasets/tests/test_utils.py:fn = "raw.github.com,vincentarelbundock,Rdatasets,master,csv,HistData,Guerry.csv.zip" statsmodels/datasets/tests/test_utils.py:fn = "raw.github.com,vincentarelbundock,Rdatasets,master,doc,HistData,rst,Guerry.rst.zip" should do the trick. Any help to fix this is really welcome. Kind regards Andreas. -- http://fam-tille.de
Bug#920339: matrix-synapse: installation process hangs with unknown reason
Control: tag -1 moreinfo Hi, On Thu, 24 Jan 2019 14:20:29 +0300 sergio wrote: > Package: matrix-synapse > Version: 0.34.1.1-3~bpo9+1 > Severity: serious > > > # apt -t stretch-backports install matrix-synapse > ... > Setting up matrix-synapse (0.34.1.1-3~bpo9+1) ... > > Synapse no longer includes a web client. To enable a web client, configure > web_client_location. To remove this warning, remove 'webclient' from the > 'listeners' > configuration. > > Config is missing missing macaroon_secret_key > > Synapse no longer includes a web client. To enable a web client, configure > web_client_location. To remove this warning, remove 'webclient' from the > 'listeners' > configuration. > > Config is missing missing macaroon_secret_key I was not able to reproduce that, is that still the case with newer uploads too? -- Cheers, Andrej
Processed: tagging 920339
Processing commands for cont...@bugs.debian.org: > tags 920339 + stretch Bug #920339 [matrix-synapse] matrix-synapse: installation process hangs with unknown reason Added tag(s) stretch. > thanks Stopping processing here. Please contact me if you need assistance. -- 920339: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920339 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: matrix-synapse: installation process hangs with unknown reason
Processing control commands: > tag -1 moreinfo Bug #920339 [matrix-synapse] matrix-synapse: installation process hangs with unknown reason Added tag(s) moreinfo. -- 920339: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920339 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#921176: redis-server service is failing to start in buster lxc container
Hi Pirate, > Initially I tried editing /lib/systemd/system/redis-server.service and > later I edited /lib/systemd/system/redis-server\@.service as well > (edited both these files) > > > b) Exactly how you are editing the shipped .service file. > > I tried adding changing true to false initially, then adding # in front > of the options Ah, so you are not using: systemctl edit --full You are likely not actually testing the service file you believe you are, leading to a misleading report. You might need a "systemctl daemon-reload" too. > apparmor was at 2.11.1-4, updating it to 2.13.2-7 fixed the above > error, but redis still can't be started like before (same error > message) even after stopping apparmor on the host. Don't you mean disabled with aa-disable or something? I'm not 100% certain but simply stopping the service may not be enough. A reboot with the service disabled, etc. might be what is needed (perhaps consult the Debian Wiki on this?) (ie. I don't think you can rule out apparmor either just yet.) Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org 🍥 chris-lamb.co.uk `-
Bug#921176: redis-server service is failing to start in buster lxc container
On Tue, Feb 12, 2019 at 9:44 PM, Chris Lamb wrote: Hi Pirate, https://wiki.debian.org/Packaging/Pre-Requisites#LXC has networking setup instructions. Still no dice and I don't really have the bandwidth to learn another container technology. :( May be ask lxc team for help? I tried removing all hardening features and it still won't start Please provide: a) The *exact* .service file you are trying. Initially I tried editing /lib/systemd/system/redis-server.service and later I edited /lib/systemd/system/redis-server\@.service as well (edited both these files) b) Exactly how you are editing the shipped .service file. I tried adding changing true to false initially, then adding # in front of the options So current snapshot look like this, root@redis:~# cat /lib/systemd/system/redis-server.service [Unit] Description=Advanced key-value store After=network.target Documentation=http://redis.io/documentation, man:redis-server(1) [Service] Type=forking ExecStart=/usr/bin/redis-server /etc/redis/redis.conf ExecStop=/bin/kill -s TERM $MAINPID PIDFile=/run/redis/redis-server.pid TimeoutStopSec=0 Restart=always User=redis Group=redis #RuntimeDirectory=redis #RuntimeDirectoryMode=2755 #UMask=007 #PrivateTmp=yes #LimitNOFILE=65535 #PrivateDevices=yes #ProtectHome=yes #ReadOnlyDirectories=/ #ReadWriteDirectories=-/var/lib/redis #ReadWriteDirectories=-/var/log/redis #ReadWriteDirectories=-/var/run/redis NoNewPrivileges=true CapabilityBoundingSet=CAP_SETGID CAP_SETUID CAP_SYS_RESOURCE MemoryDenyWriteExecute=true ProtectKernelModules=true #ProtectKernelTunables=true #ProtectControlGroups=true #RestrictRealtime=true #RestrictNamespaces=true #RestrictAddressFamilies=AF_INET AF_INET6 AF_UNIX # redis-server can write to its own config file when in cluster mode so we # permit writing there by default. If you are not using this feature, it is # recommended that you replace the following lines with "ProtectSystem=full". #ProtectSystem=true #ReadWriteDirectories=-/etc/redis [Install] WantedBy=multi-user.target Alias=redis.service c) uname -a root@redis:~# uname -a Linux redis 4.15.0-2-amd64 #1 SMP Debian 4.15.11-1 (2018-03-20) x86_64 GNU/Linux root@redis:~# This is reproduced on a second machine. On first machine, I tried with two kernels, one older and then 4.19. d) aa-status Anything in the global kernel log or dmesg...? In dmesg inside container (same error on the host as well), so it seems apparmor is blocking it. [14760.307180] audit: type=1400 audit(1549992481.311:156): apparmor="DENIED" operation="mount" info="failed flags match" error=-13 profile="lxc-container-default-cgns" name="/" pid=20531 comm="(s-server)" flags="rw, rslave" [14760.573458] audit: type=1400 audit(1549992481.579:157): apparmor="DENIED" operation="mount" info="failed flags match" error=-13 profile="lxc-container-default-cgns" name="/" pid=20532 comm="(s-server)" flags="rw, rslave" [14760.823723] audit: type=1400 audit(1549992481.827:158): apparmor="DENIED" operation="mount" info="failed flags match" error=-13 profile="lxc-container-default-cgns" name="/" pid=20533 comm="(s-server)" flags="rw, rslave" [14761.073770] audit: type=1400 audit(1549992482.079:159): apparmor="DENIED" operation="mount" info="failed flags match" error=-13 profile="lxc-container-default-cgns" name="/" pid=20534 comm="(s-server)" flags="rw, rslave" [14761.323944] audit: type=1400 audit(1549992482.327:160): apparmor="DENIED" operation="mount" info="failed flags match" error=-13 profile="lxc-container-default-cgns" name="/" pid=20536 comm="(s-server)" flags="rw, rslave" Though systemctl status apparmor on host showed it failed, Feb 12 18:23:25 nishumbha systemd[1]: Starting AppArmor initialization... Feb 12 18:23:30 nishumbha apparmor[600]: Starting AppArmor profiles:AppArmor parser error for /etc/apparmor.d/usr.lib.libreoffice.program.soffice.bin in /etc/apparmor.d/usr.lib.libreoffice.program.soffice.bin at line 89: Could not open 'abstractions/dri-enumerate' Feb 12 18:23:30 nishumbha apparmor[600]: AppArmor parser error for /etc/apparmor.d/usr.lib.libreoffice.program.soffice.bin in /etc/apparmor.d/usr.lib.libreoffice.program.soffice.bin at line 89: Could not open 'abstractions/dri-enumerate' Feb 12 18:23:30 nishumbha apparmor[600]: failed! Feb 12 18:23:30 nishumbha systemd[1]: apparmor.service: Main process exited, code=exited, status=123/n/a apparmor was at 2.11.1-4, updating it to 2.13.2-7 fixed the above error, but redis still can't be started like before (same error message) even after stopping apparmor on the host. pravi@nishumbha:~$ systemctl status apparmor ● apparmor.service - Load AppArmor profiles Loaded: loaded (/lib/systemd/system/apparmor.service; enabled; vendor preset: Active: inactive (dead) since Tue 2019-02-12 23:06:50 IST; 3min 56s ago Docs: man:apparmor(7) https://gitlab.com/apparmor/apparmor/wikis/home/ Process: 10021 ExecStop=/bin/true (code=
Bug#921667: Reproduced without lava-dev
notfound 921667 lava/2019.01-3 notfound 921667 lava/2019.01-4 affects 921667 - lava-server affects 921667 - lava-dispatcher affects 921667 + fuse affects 921667 + apparmor retitle 921667 lxc - fails to install alongside fuse and apparmor thanks Tested with salsa.debian.org - LXC fails to install: https://salsa.debian.org/pkg-lava-team/pkg-lava/-/jobs/126502 This command fails: apt -y install fuse apparmor lxc lxc-templates -- Neil Williams = http://www.linux.codehelp.co.uk/ pgpA4YGdV2db2.pgp Description: OpenPGP digital signature
Processed: Reproduced without lava-dev
Processing commands for cont...@bugs.debian.org: > notfound 921667 lava/2019.01-3 Bug #921667 [lxc,lava-dev] lxc,lava-dev: lxc fails to install along lava-dev --install-recommends No longer marked as found in versions lava/2019.01-3. > notfound 921667 lava/2019.01-4 Bug #921667 [lxc,lava-dev] lxc,lava-dev: lxc fails to install along lava-dev --install-recommends No longer marked as found in versions lava/2019.01-4. > affects 921667 - lava-server Bug #921667 [lxc,lava-dev] lxc,lava-dev: lxc fails to install along lava-dev --install-recommends Removed indication that 921667 affects lava-server > affects 921667 - lava-dispatcher Bug #921667 [lxc,lava-dev] lxc,lava-dev: lxc fails to install along lava-dev --install-recommends Removed indication that 921667 affects lava-dispatcher > affects 921667 + fuse Bug #921667 [lxc,lava-dev] lxc,lava-dev: lxc fails to install along lava-dev --install-recommends Added indication that 921667 affects fuse > affects 921667 + apparmor Bug #921667 [lxc,lava-dev] lxc,lava-dev: lxc fails to install along lava-dev --install-recommends Added indication that 921667 affects apparmor > retitle 921667 lxc - fails to install alongside fuse and apparmor Bug #921667 [lxc,lava-dev] lxc,lava-dev: lxc fails to install along lava-dev --install-recommends Changed Bug title to 'lxc - fails to install alongside fuse and apparmor' from 'lxc,lava-dev: lxc fails to install along lava-dev --install-recommends'. > thanks Stopping processing here. Please contact me if you need assistance. -- 921667: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921667 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed (with 2 errors): fixing ftbfs bug metadata
Processing commands for cont...@bugs.debian.org:
> # reassign to source package
> reassign 790912 src:kcov
Bug #790912 [kcov] FTBFS: ld: CMakeFiles/kcov.dir/capabilities.cc.o ..
recompile with -fPIC
Bug reassigned from package 'kcov' to 'src:kcov'.
No longer marked as found in versions kcov/25+dfsg-1.
Ignoring request to alter fixed versions of bug #790912 to the same values
previously set
> # reassign to source package
> reassign 804369 src:netexpect
Bug #804369 [netexpect] netexpect: FTBFS with wireshark 2.0
Bug reassigned from package 'netexpect' to 'src:netexpect'.
No longer marked as found in versions netexpect/0.22-2.
Ignoring request to alter fixed versions of bug #804369 to the same values
previously set
> # reassign to source package
> reassign 811639 src:choreonoid
Bug #811639 {Done: Dimitri John Ledkov } [choreonoid] FTBFS
with GCC 6: multiple errors
Bug reassigned from package 'choreonoid' to 'src:choreonoid'.
No longer marked as found in versions choreonoid/1.1.0+dfsg-6.2.
No longer marked as fixed in versions choreonoid/1.5.0+dfsg-0.1.
> # reassign to source package
> reassign 811845 src:doscan
Bug #811845 [doscan] doscan: FTBFS with GCC 6: no match for
Bug reassigned from package 'doscan' to 'src:doscan'.
No longer marked as found in versions doscan/0.3.3-1.
Ignoring request to alter fixed versions of bug #811845 to the same values
previously set
> # reassign to source package
> reassign 811887 src:duma
Bug #811887 [duma] duma: FTBFS with GCC 6: declaration of ... has a different
exception specifier
Bug reassigned from package 'duma' to 'src:duma'.
No longer marked as found in versions duma/2.5.15-1.1.
Ignoring request to alter fixed versions of bug #811887 to the same values
previously set
> # reassign to source package
> reassign 811896 src:src:percona-xtrabackup
Unknown command or malformed arguments to command.
> # reassign to source package
> reassign 811919 src:objcryst-fox
Bug #811919 [objcryst-fox] objcryst-fox: FTBFS with GCC 6: use of deleted
function
Bug reassigned from package 'objcryst-fox' to 'src:objcryst-fox'.
No longer marked as found in versions objcryst-fox/1.9.6.0-2.1.
Ignoring request to alter fixed versions of bug #811919 to the same values
previously set
> # reassign to source package
> reasign 811980 src:libusbtc08
Unknown command or malformed arguments to command.
> # reassign to source package
> reassign 812619 src:libtm-perl
Bug #812619 [libtm-perl] libtm-perl: FTBFS - Failed test 'assertions applying
to identical topics are found'
Bug reassigned from package 'libtm-perl' to 'src:libtm-perl'.
No longer marked as found in versions libtm-perl/1.56-9 and libtm-perl/1.56-7.
Ignoring request to alter fixed versions of bug #812619 to the same values
previously set
> # reassign to source package
> reassign 812704 src:nbibtex
Bug #812704 [nbibtex] nbibtex: FTBFS - nbib.dvi: file contents does not seem to
settle
Bug reassigned from package 'nbibtex' to 'src:nbibtex'.
No longer marked as found in versions nbibtex/0.9.18-11.
Ignoring request to alter fixed versions of bug #812704 to the same values
previously set
> # reassign to source package
> reassign 826473 src:kdesrc-build
Bug #826473 [kdesrc-build] kdesrc-build: FTBFS with Perl 5.26: Unescaped left
brace in regex is deprecated
Bug reassigned from package 'kdesrc-build' to 'src:kdesrc-build'.
No longer marked as found in versions kdesrc-build/1.15.1-1.
Ignoring request to alter fixed versions of bug #826473 to the same values
previously set
> # reassign to source package
> reassign 861550 src:docker-swarm
Bug #861550 [docker-swarm] docker-swarm: FTBFS with latest golang-go.crypto
Bug reassigned from package 'docker-swarm' to 'src:docker-swarm'.
No longer marked as found in versions docker-swarm/1.2.5+dfsg-2.
Ignoring request to alter fixed versions of bug #861550 to the same values
previously set
> # reassign to source package
> reassign 881897 src:mosh
Bug #881897 [mosh] Please avoid the unconditional locales build-dependency to
support cross-building
Bug reassigned from package 'mosh' to 'src:mosh'.
No longer marked as found in versions mosh/1.3.2-2.
Ignoring request to alter fixed versions of bug #881897 to the same values
previously set
> # reassign to source package
> reassign 883525 src:pdf2htmlex
Bug #883525 [pdf2htmlex] pdf2htmlex: FTBFS with poppler 0.61.1
Bug reassigned from package 'pdf2htmlex' to 'src:pdf2htmlex'.
No longer marked as found in versions pdf2htmlex/0.14.6+ds-3.
Ignoring request to alter fixed versions of bug #883525 to the same values
previously set
> # missing affects
> affects 891394 + src:src:kannel-sqlbox src:libdbi-drivers src:opensp
> src:pgpool2 src:plr src:slony1-2 src:gtkextra
Bug #891394 [libostyle1c2] multiarchify libostyle1c2
Added indication that 891394 affects src:src:kannel-sqlbox, src:libdbi-drivers,
src:opensp, src:pgpool2, src:plr, src:slony1-2, and src:gtkextra
> # installation failure, not ftbfs
> tags 891612 - ftbfs
Bug #891612 [thumbor] thumbor: uninst
Processed: severity of 921031 is grave
Processing commands for cont...@bugs.debian.org: > # Breaks autopkgtests and is therefore a migration blocker > severity 921031 grave Bug #921031 [libdpkg-perl] Dpkg::Source::Package missing use of ::Format Severity set to 'grave' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 921031: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921031 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#921841: wmweather: fails to fetch weather data
Processing commands for cont...@bugs.debian.org: > tags 921841 + pending Bug #921841 [wmweather] wmweather: fails to fetch weather data Added tag(s) pending. > End of message, stopping processing here. Please contact me if you need assistance. -- 921841: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921841 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#922149: t-coffee ignores build failures
Source: t-coffee Version: 12.00.7fb08c2-2 Severity: serious Justification: policy 4.6 t-coffee's debian/rules passes -i through dh_auto_build to make. That's the equivalent to ignoring all return codes of compiler invocations and thus violating the spirit of policy section 4.6. I argue that -i violates common sense. Its presence makes debugging build failures next to impossible. Please drop the -i flag. Helmut
Processed: Re: Bug#921841: wmweather: fails to fetch weather data
Processing commands for cont...@bugs.debian.org: > severity 921841 grave Bug #921841 [wmweather] wmweather: fails to fetch weather data Severity set to 'grave' from 'important' > End of message, stopping processing here. Please contact me if you need assistance. -- 921841: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921841 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#922145: irssi: trying to overwrite '/usr/share/irssi/help/otr', which is also in package irssi-plugin-otr
Hi! On 2/12/19 5:25 PM, Diederik de Haas wrote: > Got an update for version 1.2.0-1, but I also have irssi-plugin-otr > installed, which resulted in the following upgrade error: > > # aptitude safe-upgrade > The following packages will be upgraded: > bind9-host dnsutils irssi irssi-plugin-otr > ... > Get: 16 http://httpredir.debian.org/debian sid/main amd64 irssi amd64 1.2.0-1 > [1,178 kB] > Get: 17 http://httpredir.debian.org/debian sid/main amd64 irssi-plugin-otr > amd64 1.2.0-1 [480 kB] > ... > Preparing to unpack .../09-irssi_1.2.0-1_amd64.deb ... > Unpacking irssi (1.2.0-1) over (1.1.2-1) ... > dpkg: error processing archive > /tmp/apt-dpkg-install-9iSR4c/09-irssi_1.2.0-1_amd64.deb (--unpack): > trying to overwrite '/usr/share/irssi/help/otr', which is also in package > irssi-plugin-otr:amd64 1.0.2-4+b1 Good catch - sorry for the inconvenience! What you can do as a workaround: First upgrade irssi-plugin-otr and then install irssi. Or somehow force-install it with dpkg. I'll roll out a -2, and I'm sorry that I missed that part. The helpfile will move over to the irssi-plugin-otr package. Enjoy, Rhonda
Processed: Re: Bug#922145: irssi: trying to overwrite '/usr/share/irssi/help/otr', which is also in package irssi-plugin-otr
Processing control commands: > severity -1 serious Bug #922145 [irssi] irssi: trying to overwrite '/usr/share/irssi/help/otr', which is also in package irssi-plugin-otr Severity set to 'serious' from 'important' -- 922145: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922145 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#922146: after upgrade from jessie to stretch: hibernate leads to black screen and suspend to graphical glitches
Package: src:linux Version: 4.9.130-2 Severity: grave Tags: stretch Dear maintainer, After boot using "systemctl hibernate" the system seems to boot normal, but the screen stays black after logging in (into user account). Every single boot from hibernation leads to a black screen since updating from jessie to stretch. The laptop is still running and I can hear sound. However I am unable to recover from the black screen without forcing a reboot. While the screen is black, I tried to switch terminals using alt+ctrl+f*. This led to a total system freeze (no sound, no response, no switching back). I tried to use alt+f2, r, enter (resetting the gnome-shell). This didn't help. I can go into suspend and wake and the screen turns on. However, there are nasty graphical glitchs, which do not disappear until I reboot the system. Also some graphical programs crash or don't start at all, while these glitches are present. For my work with debian system I require a working hibernation. Not being able to hibernate, renders the upgrade to stretch (stable) a failure. I am using a lenovo thinkpad X230t. uname -a ouput is: Linux Azurus 4.9.0-8-amd64 #1 SMP Debian 4.9.130-2 (2018-10-27) x86_64 GNU/Linux I can upload my syslog (after hibernation, wake, suspend, wake) if that helps. I couldn't get a glue from it, what is going wrong. Any advices or help are appreciated. Thanks! -- Package-specific info: ** Version: Linux version 4.9.0-8-amd64 (debian-ker...@lists.debian.org) (gcc version 6.3.0 20170516 (Debian 6.3.0-18+deb9u1) ) #1 SMP Debian 4.9.130-2 (2018-10-27) ** Command line: BOOT_IMAGE=/vmlinuz-4.9.0-8-amd64 root=/dev/mapper/samsung_evo_850-root ro quiet ** Tainted: O (4096) * Out-of-tree module has been loaded. ** Kernel log: [12173.114812] sd 0:0:0:0: [sda] Stopping disk [12173.342579] e1000e: EEE TX LPI TIMER: 0011 [12173.567688] PM: suspend of devices complete after 608.010 msecs [12173.586471] PM: late suspend of devices complete after 18.774 msecs [12173.589737] ehci-pci :00:1d.0: System wakeup enabled by ACPI [12173.589824] ehci-pci :00:1a.0: System wakeup enabled by ACPI [12173.590029] xhci_hcd :00:14.0: System wakeup enabled by ACPI [12173.654309] PM: noirq suspend of devices complete after 67.831 msecs [12173.654604] ACPI: Preparing to enter system sleep state S3 [12173.998310] ACPI : EC: event blocked [12173.998310] ACPI : EC: EC stopped [12173.998311] PM: Saving platform NVS memory [12173.998326] Disabling non-boot CPUs ... [12173.998629] Broke affinity for irq 16 [12173.998632] Broke affinity for irq 18 [12173.998638] Broke affinity for irq 28 [12173.998643] Broke affinity for irq 32 [12173.68] smpboot: CPU 1 is now offline [12174.000598] Broke affinity for irq 16 [12174.000601] Broke affinity for irq 18 [12174.000610] Broke affinity for irq 28 [12174.000613] Broke affinity for irq 32 [12174.001627] smpboot: CPU 2 is now offline [12174.002112] Broke affinity for irq 1 [12174.002117] Broke affinity for irq 8 [12174.002120] Broke affinity for irq 9 [12174.002124] Broke affinity for irq 12 [12174.002128] Broke affinity for irq 16 [12174.002131] Broke affinity for irq 18 [12174.002136] Broke affinity for irq 23 [12174.002140] Broke affinity for irq 27 [12174.002143] Broke affinity for irq 28 [12174.002147] Broke affinity for irq 30 [12174.002151] Broke affinity for irq 32 [12174.003188] smpboot: CPU 3 is now offline [12174.005276] ACPI: Low-level resume complete [12174.005328] ACPI : EC: EC started [12174.005329] PM: Restoring platform NVS memory [12174.005629] Suspended for 914.085 seconds [12174.005685] Enabling non-boot CPUs ... [12174.005760] x86: Booting SMP configuration: [12174.005761] smpboot: Booting Node 0 Processor 1 APIC 0x1 [12174.008390] cache: parent cpu1 should not be sleeping [12174.008723] CPU1 is up [12174.008806] smpboot: Booting Node 0 Processor 2 APIC 0x2 [12174.011375] cache: parent cpu2 should not be sleeping [12174.011760] CPU2 is up [12174.011838] smpboot: Booting Node 0 Processor 3 APIC 0x3 [12174.014395] cache: parent cpu3 should not be sleeping [12174.014984] CPU3 is up [12174.018963] ACPI: Waking up from system sleep state S3 [12174.719761] sdhci-pci :02:00.0: MMC controller base frequency changed to 50Mhz. [12174.744083] ehci-pci :00:1a.0: System wakeup disabled by ACPI [12174.744090] xhci_hcd :00:14.0: System wakeup disabled by ACPI [12174.744154] ehci-pci :00:1d.0: System wakeup disabled by ACPI [12174.744232] PM: noirq resume of devices complete after 68.117 msecs [12174.744710] PM: early resume of devices complete after 0.453 msecs [12174.745003] ACPI : EC: event unblocked [12174.745311] rtc_cmos 00:02: System wakeup disabled by ACPI [12174.755323] sd 0:0:0:0: [sda] Starting disk [12174.755405] sd 2:0:0:0: [sdb] Starting disk [12174.755662] iwlwifi :03:00.0: RF_KILL bit toggled to disable radio. [12174.992063] usb 1-1.6: reset high-speed USB device number 4 using ehci-pci [12174.996117] usb 2-1.5: reset full-speed USB devic
Processed: 919477 is done
Processing commands for cont...@bugs.debian.org:
> severity 919477 normal
Bug #919477 {Done: Camm Maguire } [src:acl2] acl2 ftbfs on
armel, armhf, arm64 and ppc64el
Severity set to 'normal' from 'serious'
> tag 919477 - buster sid
Bug #919477 {Done: Camm Maguire } [src:acl2] acl2 ftbfs on
armel, armhf, arm64 and ppc64el
Removed tag(s) buster and sid.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
919477: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919477
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#921443: marked as done (ddnet FTBFS on architectures where char is unsigned)
Your message dated Tue, 12 Feb 2019 16:34:45 +
with message-id
and subject line Bug#921443: fixed in ddnet 11.7.2-2
has caused the Debian Bug report #921443,
regarding ddnet FTBFS on architectures where char is unsigned
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.)
--
921443: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921443
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ddnet
Version: 11.7.2-1
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/package.php?p=ddnet&suite=sid
...
/usr/bin/c++ -DCONF_AUTOUPDATE -DCONF_OPENSSL -DCONF_SQL -DCONF_WEBSOCKETS
-DGLEW_STATIC -D_FORTIFY_SOURCE=2 -I/<>/obj-aarch64-linux-gnu/src
-I/<>/src -I/usr/include/mariadb -g -O2
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat
-Werror=format-security -Wall -pedantic -O3 -Wdate-time -D_FORTIFY_SOURCE=2
-fstack-protector-all -Wall -Wextra -Wno-unused-parameter
-Wno-missing-field-initializers -Wformat=2 -std=gnu++11 -o
CMakeFiles/testrunner.dir/src/test/str.cpp.o -c
/<>/src/test/str.cpp
/<>/src/test/str.cpp: In member function 'virtual void
Str_Utf8ToLower_Test::TestBody()':
/<>/src/test/str.cpp:70:28: error: narrowing conversion of '-128'
from 'int' to 'char' inside { } [-Wnarrowing]
const char a[2] = {-128, 0};
^
make[5]: *** [CMakeFiles/testrunner.dir/build.make:183:
CMakeFiles/testrunner.dir/src/test/str.cpp.o] Error 1
--- End Message ---
--- Begin Message ---
Source: ddnet
Source-Version: 11.7.2-2
We believe that the bug you reported is fixed in the latest version of
ddnet, 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 921...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Yangfl (supplier of updated ddnet package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Tue, 12 Feb 2019 22:31:43 +0800
Source: ddnet
Architecture: source
Version: 11.7.2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Games Team
Changed-By: Yangfl
Closes: 921443
Changes:
ddnet (11.7.2-2) unstable; urgency=medium
.
* Fix FTBFS on architectures where char is unsigned (Closes: #921443)
* Disable autoupdater
Checksums-Sha1:
c709fba96c625cc18692329fb242e98fe915a638 2430 ddnet_11.7.2-2.dsc
7e79180895bb1ae20768fdeb7429a0bdee362bf8 21324 ddnet_11.7.2-2.debian.tar.xz
bdc40dc90eb657c7b1660f85340f8dd5572a7a79 13811 ddnet_11.7.2-2_amd64.buildinfo
Checksums-Sha256:
a36f5652317f80cf3656a07e80be7d1b647601653a36d5bb8dc64fadd37b8ef7 2430
ddnet_11.7.2-2.dsc
2eff358e81941b966a59654f6654f26f35db03e9b7ed4b947b93cf638e83a8fd 21324
ddnet_11.7.2-2.debian.tar.xz
6a2e140ad757e991edfae3be71e372d63689343acd16936f220b9f4363a85eba 13811
ddnet_11.7.2-2_amd64.buildinfo
Files:
d8571a4d486a33305d18297b3eb55f00 2430 games optional ddnet_11.7.2-2.dsc
431574f594b0f786646c641fd9eac331 21324 games optional
ddnet_11.7.2-2.debian.tar.xz
189285ac55c0a98c01c2f5cd91d67bc5 13811 games optional
ddnet_11.7.2-2_amd64.buildinfo
-BEGIN PGP SIGNATURE-
iQIzBAEBCgAdFiEEfncpR22H1vEdkazLwpPntGGCWs4FAlxi8SkACgkQwpPntGGC
Ws48JhAAxKsax7e1cqxiMtISJtrf01JkB2ThzDp5gxsNUlImyfZnWiiu9dC2lizZ
1Z4e4C2jXrEpQnzw/h57apTc1uroji4XlHIp/BziCG4HJOBEFOHWFEdgty8IusV0
bBsVwQjnpkHHzYAATzSlgKMmh5vhTW7UFS3WrTXL2BVzEs38AcWmnB+ALyrPIr9o
3YNnJHo4tTzh/9Uf6FelVwGGU024cbmVx5tERIEvf/iTPZS5OF/kfOkkeZtOW+Uw
wqefFuhW+xJRsHlD/nhrI87JS2X+p8oILiYZ9rKOBsoSykbRntu7aqEDDBD1Lc0H
wTCKbrNpAoDItbyxXr5HOgCZfmiNa6qbydTlUFDxPbDwyptQT9H/WatQtHoIcVsY
JTIMZqWg5+mL7YIPWEiwzeCqxnYDGiLVZMw9X7YW54+BuetlJdTg1tgb8eTM0GMW
DFJaw3WUzc+TPeqZGiDpelajQgr5L0fltIbsR19jBMSUWPXYZWVAHo8A/LRtsxkn
H2UW8oH/Mdv4CD4C94gfr6hf7D72CKbamsgzb83vdPyI1dTR/iwN8H0Ao78yiXYJ
TPyefczi5Z7yZat9Iist8nC7zFxOs1ZWNuhbr8zWTePbR7gOPwZmkZMzUUMkHnx8
FB3oKq0nU1jNV0264LNvfjVrvYBL4EF7osiO9CwbW2SdP6P5/cU=
=t2Jh
-END PGP SIGNATURE End Message ---
Bug#919356: Licensing of include/linux/hash.h
On 2/11/19 11:27 PM, Ben Finney wrote: > Martin Steigerwald writes: > >> Well the file has in its header: >> >> /* Fast hashing routine for a long. >>(C) 2002 William Lee Irwin III, IBM */ >> >> /* >> * Knuth recommends primes in approximately golden ratio to the maximum >> * integer representable by a machine word for multiplicative hashing. >> * Chuck Lever verified the effectiveness of this technique: >> * http://www.citi.umich.edu/techreports/reports/citi-tr-00-1.pdf >> * >> * These primes are chosen to be bit-sparse, that is operations on >> * them can use shifts and additions instead of multiplications for >> * machines where multiplications are slow. >> */ >> >> It has been quite a while ago. I bet back then I did not regard this >> as license information since it does not specify a license. Thus I >> assumed it to be GPL-2 as the other files which have no license boiler >> plate. I.e.: Check file is it has different license, if not, then >> assume it has license as specified in COPYING. >> >> Not specifying a license can however also mean in this context that it >> has no license as the file contains copyright information from another >> author. > > If a work (even one file) “has no license”, that means no special > permissions are granted and normal copyright applies: All rights > reserved, i.e. not redistributable. So, no license is grounds to > consider a work non-free and non-redistributable. > > If, on the other hand, the file is to be free software, there would need > to be a clear grant of some free software license to that work. > > Given the confusion over this file, I would consider it a significant > risk to just assume we have GPLv2 permissions without being told that > explicitly by the copyright holder. Rather, the reason we are seeking a > clearly-granted free license for this one file, is because we are trying > to replace a probably non-free file with the same code in it. > > It seems we need to keep looking, and in the meantime assume we have no > free license in this file. FWIW, fio.c includes the following mention: * The license below covers all files distributed with fio unless otherwise * noted in the file itself. followed by the GPL v2 license. I'll go through and add SPDX headers to everything to avoid wasting anymore time on this nonsense. -- Jens Axboe
Bug#921176: redis-server service is failing to start in buster lxc container
Hi Pirate, > https://wiki.debian.org/Packaging/Pre-Requisites#LXC has networking > setup instructions. Still no dice and I don't really have the bandwidth to learn another container technology. :( > I tried removing all hardening features and it still won't start Please provide: a) The *exact* .service file you are trying. b) Exactly how you are editing the shipped .service file. c) uname -a d) aa-status Anything in the global kernel log or dmesg...? Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org 🍥 chris-lamb.co.uk `-
Bug#922050: marked as done (runc: CVE-2019-5736)
Your message dated Tue, 12 Feb 2019 16:05:27 + with message-id and subject line Bug#922050: fixed in runc 1.0.0~rc6+dfsg1-2 has caused the Debian Bug report #922050, regarding runc: CVE-2019-5736 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.) -- 922050: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922050 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: runc Version: 1.0.0~rc6+dfsg1-1 Severity: grave Tags: security upstream Justification: user security hole Hi, The following vulnerability was published for runc. CVE-2019-5736[0]: runc container breakout 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-2019-5736 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-5736 [1] https://github.com/opencontainers/runc/commit/0a8e4117e7f715d5fbeef398405813ce8e88558b [2] https://www.openwall.com/lists/oss-security/2019/02/11/2 Please adjust the affected versions in the BTS as needed. Regards, Salvatore --- End Message --- --- Begin Message --- Source: runc Source-Version: 1.0.0~rc6+dfsg1-2 We believe that the bug you reported is fixed in the latest version of runc, 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 922...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Shengjing Zhu (supplier of updated runc package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 12 Feb 2019 23:45:09 +0800 Source: runc Architecture: source Version: 1.0.0~rc6+dfsg1-2 Distribution: unstable Urgency: medium Maintainer: Debian Go Packaging Team Changed-By: Shengjing Zhu Closes: 922050 Changes: runc (1.0.0~rc6+dfsg1-2) unstable; urgency=medium . * Team upload. * Apply upstream patch addressing CVE-2019-5736 (Closes: #922050) Thanks Noah Meyerhans! Checksums-Sha1: d12bd0a0de956ae1a7ab96c0a1ee9aafd44af09c 2460 runc_1.0.0~rc6+dfsg1-2.dsc b5f68ea4e338f71e7a8f0e05982ec0e3cb5944e8 10308 runc_1.0.0~rc6+dfsg1-2.debian.tar.xz 126bfdb3620363d1c325ad2417c1a6cacd3195df 7886 runc_1.0.0~rc6+dfsg1-2_amd64.buildinfo Checksums-Sha256: 8607734e77432594f427e10bfcc082fd782e38d5afafab4f9d0f9f415a272082 2460 runc_1.0.0~rc6+dfsg1-2.dsc da194164edb66bd865f0472e9b4588c8214ef12371307c1452d0ecf3a6becb00 10308 runc_1.0.0~rc6+dfsg1-2.debian.tar.xz 3b69ecf4a26882639f480e92286146966a27ce19e715fdfc8b5577b26bd668d2 7886 runc_1.0.0~rc6+dfsg1-2_amd64.buildinfo Files: b8de374a7e03ba461239f9d0f79889a1 2460 devel optional runc_1.0.0~rc6+dfsg1-2.dsc 839908f20673d0c7de21f6cab450a7ee 10308 devel optional runc_1.0.0~rc6+dfsg1-2.debian.tar.xz 9db1e3091431d02e118e1c9d08ffadf3 7886 devel optional runc_1.0.0~rc6+dfsg1-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQE+BAEBCgAoFiEE85F2DZP0aJKsSKyHONAPABi+PjUFAlxi6r4KHGlAemhzai5t ZQAKCRA40A8AGL4+NeDmB/4wziwjsq06khXWe7iItTRFfZaOXax/0IcJbzh/rUjv KXYXsZX4ODT2n2QZYuwiIVBgpLcFWhTmlLP/rSYnP8B8OkpGXGessi2U8f948F6o /GMmbOxJEoZ94uhFRXY3IvRxx2heOdCy4SgwcbZSY0TVO1XzXlsbnHYMrlRhqxE2 n0/H3+c4xPB5BWtSnsflPEiafoI8uIcAsIeCnz7E3Gc3VL/ItXtJttvQlLigYVkF rDCIG4DpGbmwTaJk2IW2HBYCsxQZVs6cyTNCd66ZT5kqmqvxL7Dv3rxrD46uW0G8 GC56pJrfqmFBI3tN+lfkKy+147P2QbSyoX/P2lc6lVYy =xKjg -END PGP SIGNATURE End Message ---
Bug#922080: borgbackup: fuse mount exposes backup to unauthorized users
On Mon, 11 Feb 2019 21:02:03 +0100 Salvatore Bonaccorso wrote: > Source: borgbackup > Version: 1.1.8-1 > Severity: grave > Tags: security upstream > Justification: user security hole > Forwarded: https://github.com/borgbackup/borg/issues/3903 > Control: fixed -1 1.1.9-1 > > As there is no CVE assigned for this issue, fill a bug for having an > unique identifier withing Debian. > > Upstream issue: https://github.com/borgbackup/borg/issues/3903 > > Please adjust found versions as needed, is stable affected? > Hello, yes, I think stable is affected. the patch doesn't apply cleanly but it shoult be easy to rebase it. Do you think you can go with a security update for stable? G. > Regards, > Salvatore > >
Processed: Re: cascade of FTBFS
Processing control commands: > tags -1 help Bug #921779 [src:doxygen] cascade of FTBFS Added tag(s) help. -- 921779: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921779 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#921779: cascade of FTBFS
Control: tags -1 help
Hi Paolo,
in my attempt to see what I can do for #921779 which breaks several
packages I stumbled upon your attempt to adopt doxygen. Thanks a lot
for this brave intention. ;-)
I realised that the watch file did not work properly - feel free to `git
am` the attached patch. I also noticed that there are remaining lintian
errors:
E: doxygen source: source-is-missing templates/html/jquery.js line length is
32401 characters (>512)
N:
N:The source of the following file is missing. Lintian checked a few
N:possible paths to find the source, and did not find it.
N:
N:Please repack your package to include the source or add it to
N:"debian/missing-sources" directory.
N:
N:If this is a false-positive, please report a bug against Lintian.
N:
N:Please note, that insane-line-length-in-source-file tagged files are
N:likely tagged source-is-missing. It is a feature not a bug.
N:
N:Severity: serious, Certainty: possible
N:
N:Check: cruft, Type: source
N:
E: doxygen source: source-is-missing templates/html/menu.js line length is 695
characters (>512)
E: doxygen source: source-is-missing templates/html/svgpan.js line length is
312 characters (>256)
You should override the latter two since these are false positives. I'm
not sure how to deal with the jquery.js one since this is potentially an
issue with lots of dependencies - I remember discussions about this
which I did not followed.
Regarding the ratt results[1] the issue
librostlab: ! LaTeX Error: File 'listofitems.sty' not found.
can be solved by a doxygen-latex Build-Depends - at least I added this
to frobby in Git[2] which helped against this very error but after this it
was running into:
[572]
! Undefined control sequence.
l.211 ...+t-1$. The inner slice will have $(a\text
{'},b)$, where $a^\prime$ ...
?.
! Emergency stop.
l.211 ...+t-1$. The inner slice will have $(a\text
{'},b)$, where $a^\prime$ ...
! ==> Fatal error occurred, no output PDF file produced!
I have no idea how to fix this.
Kind regards
Andreas.
[1] https://salsa.debian.org/paolog-guest/doxygen/wikis/ratt4
[2]
https://salsa.debian.org/science-team/frobby/commit/d2fd89875e8491a755ee702e710aa9e003982ee7
--
http://fam-tille.de
>From b0a8a6a14c391fbc40489ab6df984435efaba1c4 Mon Sep 17 00:00:00 2001
From: Andreas Tille
Date: Tue, 12 Feb 2019 16:02:57 +0100
Subject: [PATCH] Fix watch file
---
debian/changelog | 4
debian/watch | 4 ++--
2 files changed, 6 insertions(+), 2 deletions(-)
diff --git a/debian/changelog b/debian/changelog
index beb9ad6..6ca0d0b 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,5 +1,6 @@
doxygen (1.8.15-1) unstable; urgency=medium
+ [ Paolo Greppi ]
* doxygen 1.8.15 release. Closes: #920447.
* Do not produce "Directory Reference" man pages. Closes: #742871.
* Bump debhelper compat.
@@ -13,6 +14,9 @@ doxygen (1.8.15-1) unstable; urgency=medium
* Switch to llvm-toolchain-7. Closes: #912799.
* Make the output of $year reproducible. Closes: #863054
+ [ Andreas Tille ]
+ * Fix watch file
+
-- Paolo Greppi Tue, 05 Feb 2019 16:45:02 +0100
doxygen (1.8.13-10) unstable; urgency=medium
diff --git a/debian/watch b/debian/watch
index f688d00..2e294c4 100644
--- a/debian/watch
+++ b/debian/watch
@@ -1,4 +1,4 @@
-version=3
+version=4
-opts=filenamemangle=s/.+\/Release_(\d\S*)\.tar\.gz/doxygen-$1.tar\.gz/ \
+opts=uversionmangle=s/_/./g,filenamemangle=s/.+\/Release_(\d\S*)\.tar\.gz/doxygen-$1.tar\.gz/ \
https://github.com/doxygen/doxygen/tags .*/Release_(\d\S*)\.tar\.gz
--
2.20.1
Bug#921176: redis-server service is failing to start in buster lxc container
On Tue, Feb 12, 2019 at 6:09 PM, Chris Lamb wrote: Hi Pirate, > (However, I am not sure why I do not have working networking inside > my container so I cannot debug it better on my end.) But loopback is enough for redis-server, right? Yes, but I can't even install without network. :) https://wiki.debian.org/Packaging/Pre-Requisites#LXC has networking setup instructions. I tried removing all hardening features and it still won't start. I tried to start manually by running redis-server /etc/redis/redis.conf as root and that worked. Can you try with the redis user? That also works. root@redis:~# su redis -s /bin/sh -c 'redis-server /etc/redis/redis.conf' root@redis:~# ps ax |grep redis 1073 ?Ssl0:00 redis-server 127.0.0.1:6379 1078 pts/2S+ 0:00 grep redis root@redis:~# redis-cli 127.0.0.1:6379> help redis-cli 5.0.3 To get help about Redis commands type: "help @" to get a list of commands in "help " for help on "help " to get a list of possible help topics "quit" to exit To set redis-cli preferences: ":set hints" enable online hints ":set nohints" disable online hints Set your preferences in ~/.redisclirc 127.0.0.1:6379> > Also, perhaps enable some deeper logging? Or check the actual > redis-server.log file too? There is nothing in /var/log/redis. I think its failing even before redis-server gets a chance to log. Can you enable more systemd logging? If it's failing there, surely we can get more info than just "failed"? It was always the same error I mentioned in first mail. Anyway with LogLevel=debug set in systemd conf, I got a more verbose log, which is attached. -- A start job for unit redis-server.service has finished with a failure. -- -- The job identifier is 822 and the job result is failed. Feb 12 15:22:36 redis systemd[1]: redis-server.service: Changed dead -> failed Feb 12 15:22:41 redis systemd[1]: redis-server.service: Trying to enqueue job redis-server.service/start/replace Feb 12 15:22:41 redis systemd[1]: redis-server.service: Installed new job redis-server.service/start as 862 Feb 12 15:22:41 redis systemd[1]: redis-server.service: Enqueued job redis-server.service/start as 862 Feb 12 15:22:41 redis systemd[1]: redis-server.service: Passing 0 fds to service Feb 12 15:22:41 redis systemd[1]: redis-server.service: About to execute: /usr/bin/redis-server /etc/redis/redis.conf Feb 12 15:22:41 redis systemd[1]: redis-server.service: Forked /usr/bin/redis-server as 1047 Feb 12 15:22:41 redis systemd[1]: redis-server.service: Changed failed -> start Feb 12 15:22:41 redis systemd[1]: Starting Advanced key-value store... -- Subject: A start job for unit redis-server.service has begun execution -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit redis-server.service has begun execution. -- -- The job identifier is 862. Feb 12 15:22:41 redis systemd[1]: redis-server.service: User lookup succeeded: uid=105 gid=107 Feb 12 15:22:41 redis systemd[1047]: /run/systemd/unit-root/dev is duplicate. Feb 12 15:22:41 redis systemd[1047]: /run/systemd/unit-root/bin is redundant by /run/systemd/unit-root/ Feb 12 15:22:41 redis systemd[1047]: /run/systemd/unit-root/boot is redundant by /run/systemd/unit-root/ Feb 12 15:22:41 redis systemd[1047]: /run/systemd/unit-root/efi is redundant by /run/systemd/unit-root/ Feb 12 15:22:41 redis systemd[1047]: /run/systemd/unit-root/lib is redundant by /run/systemd/unit-root/ Feb 12 15:22:41 redis systemd[1047]: /run/systemd/unit-root/lib64 is redundant by /run/systemd/unit-root/ Feb 12 15:22:41 redis systemd[1047]: /run/systemd/unit-root/sbin is redundant by /run/systemd/unit-root/ Feb 12 15:22:41 redis systemd[1047]: /run/systemd/unit-root/usr is redundant by /run/systemd/unit-root/ Feb 12 15:22:41 redis systemd[1047]: Failed to remount '/' as SLAVE: Permission denied Feb 12 15:22:41 redis systemd[1047]: redis-server.service: Failed to set up mount namespacing: Permission denied Feb 12 15:22:41 redis systemd[1047]: redis-server.service: Failed at step NAMESPACE spawning /usr/bin/redis-server: Permission denied -- Subject: Process /usr/bin/redis-server could not be executed -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- The process /usr/bin/redis-server could not be executed and failed. -- -- The error number returned by this process is ERRNO. Feb 12 15:22:41 redis systemd[1]: redis-server.service: Child 1047 belongs to redis-server.service. Feb 12 15:22:41 redis systemd[1]: redis-server.service: Control process exited, code=exited, status=226/NAMESPACE -- Subject: Unit process exited -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- An ExecStart= process belonging to unit redis-server.service has exited. -- -- The process' exit code is 'exited' and its exit status is 226. Feb 12 15:22:41 redis systemd[1]: redis-server.service: Got final SIGCHLD for state start. Feb 12 15:22:41 redis sys
Bug#922050: Bug #922050 in runc marked as pending
Control: tag -1 pending Hello, Bug #922050 in runc reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/go-team/packages/runc/commit/01aaa0581c720e56f50aba9c00328d782ea9e9ca Apply upstream patch addressing CVE-2019-5736 (Closes: #922050) Thanks Noah Meyerhans! (this message was generated automatically) -- Greetings https://bugs.debian.org/922050
Processed: Bug #922050 in runc marked as pending
Processing control commands: > tag -1 pending Bug #922050 [src:runc] runc: CVE-2019-5736 Added tag(s) pending. -- 922050: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922050 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#922093: node-commander: Unable to reproduce FTBFS
Hi, even on a very slow machine with some parallel schroot builds, I'm unable to reproduce this FTBFS failure. Maybe related to LXC infrastructure. I'll test later. Cheers, Xavier
Bug#893227: marked as done (libbluray FTBFS with openjdk-9)
Your message dated Tue, 12 Feb 2019 14:59:25 +
with message-id
and subject line Bug#893227: fixed in libbluray 1:1.1.0-1
has caused the Debian Bug report #893227,
regarding libbluray FTBFS with openjdk-9
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.)
--
893227: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893227
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libbluray
Version: 1:1.0.2-2
Severity: serious
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/libbluray.html
...
compile:
[javac] /build/1st/libbluray-1.0.2/src/libbluray/bdj/build.xml:24: warning:
'includeantruntime' was not set, defaulting to build.sysclasspath=last; set to
false for repeatable builds
[javac] Using javac -source 1.4 is no longer supported, switching to 1.6
[javac] Using javac -target 1.4 is no longer supported, switching to 1.6
[javac] Compiling 664 source files to
/build/1st/libbluray-1.0.2/src/libbluray/bdj/build
[javac] warning: [options] bootstrap class path not set in conjunction with
-source 1.6
[javac] warning: [options] source value 1.6 is obsolete and will be removed
in a future release
[javac] warning: [options] target value 1.6 is obsolete and will be removed
in a future release
[javac] warning: [options] To suppress warnings about obsolete options, use
-Xlint:-options.
[javac]
/build/1st/libbluray-1.0.2/src/libbluray/bdj/java-j2se/java/awt/peer/BDFramePeer.java:176:
error: package sun.awt.CausedFocusEvent does not exist
[javac] public boolean requestFocus(Component c, boolean a, boolean b,
long l, sun.awt.CausedFocusEvent.Cause d) {
[javac]
^
[javac]
/build/1st/libbluray-1.0.2/src/libbluray/bdj/java/org/blurayx/s3d/ti/StereoscopicCodingType.java:37:
warning: non-varargs call of varargs method with inexact argument type for
last parameter;
[javac] type =
(CodingType)constructor.newInstance(new String[] { "MPEG4_MVC_VIDEO" });
[javac]^
[javac] cast to Object for a varargs call
[javac] cast to Object[] for a non-varargs call and to suppress this
warning
[javac]
/build/1st/libbluray-1.0.2/src/libbluray/bdj/java/org/blurayx/uhd/ti/UHDCodingType.java:38:
warning: non-varargs call of varargs method with inexact argument type for
last parameter;
[javac] type =
(CodingType)constructor.newInstance(new String[] { "HEVC_VIDEO" });
[javac]^
[javac] cast to Object for a varargs call
[javac] cast to Object[] for a non-varargs call and to suppress this
warning
[javac]
/build/1st/libbluray-1.0.2/src/libbluray/bdj/java/org/videolan/BDJSecurityManager.java:81:
warning: [removal] classDepth(String) in SecurityManager has been deprecated
and marked for removal
[javac] if (classDepth("javax.crypto.JceSecurityManager") <
3) {
[javac] ^
[javac]
/build/1st/libbluray-1.0.2/src/libbluray/bdj/java/org/videolan/BDJSecurityManager.java:88:
warning: [removal] classDepth(String) in SecurityManager has been deprecated
and marked for removal
[javac] if (classDepth("org.videolan.Libbluray") == 3) {
[javac] ^
[javac]
/build/1st/libbluray-1.0.2/src/libbluray/bdj/java/org/videolan/BDJSecurityManager.java:97:
warning: [removal] classDepth(String) in SecurityManager has been deprecated
and marked for removal
[javac] if (classDepth("sun.awt.AWTAutoShutdown") > 0) {
[javac] ^
[javac]
/build/1st/libbluray-1.0.2/src/libbluray/bdj/java/org/videolan/BDJSecurityManager.java:222:
warning: [removal] checkSystemClipboardAccess() in SecurityManager has been
deprecated and marked for removal
[javac] public void checkSystemClipboardAccess() {
[javac] ^
[javac]
/build/1st/libbluray-1.0.2/src/libbluray/bdj/java-j2se/java/io/BDFileSystemImpl.java:21:
error: BDFileSystemImpl is not abstract and does not override abstract method
getNameMax(String) in FileSystem
[javac] class BDFileSystemImpl extends BDFileSystem {
[javac] ^
[javac] Note: Some input files use or override a deprecated API.
[javac] Note: Recompile with -Xlint:deprecation for details.
[javac] Note: Some input files use unchecked or unsafe operations.
[java
Bug#913820: marked as done (cockpit-389-ds: Debian-packaged JS libs not sufficient to run cockpit-plugin)
Your message dated Tue, 12 Feb 2019 14:52:38 + with message-id and subject line Bug#913820: fixed in 389-ds-base 1.4.0.21-1 has caused the Debian Bug report #913820, regarding cockpit-389-ds: Debian-packaged JS libs not sufficient to run cockpit-plugin to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 913820: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913820 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: cockpit-389-ds Version: 1.4.0.18-1 Severity: grave Justification: renders package unusable At the momenent the package cockpit-389-ds applies a patch to use the Debian packaged JS libraries. In contrast to the vendored libraries the Debian versions do not work with the current version of the cockpit-389-plugin, c.f. the backtrace attached. Removing the Debian-specific patch and installing the vendored JS libs resolves the issue. Uncaught SyntaxError: Unexpected token < dataTables.select.min.js:1 Uncaught SyntaxError: Unexpected token < moment.min.js:1 Uncaught SyntaxError: Unexpected token < dataTables.datetime-moment.js:27 Uncaught ReferenceError: moment is not defined at dataTables.datetime-moment.js:27 at dataTables.datetime-moment.js:29 jstree.min.js:1 Uncaught SyntaxError: Unexpected token < bootstrap.min.js:1 Uncaught SyntaxError: Unexpected token < c3.min.js:1 Uncaught SyntaxError: Unexpected token < d3.min.js:1 Uncaught SyntaxError: Unexpected token < plugins.js:3 Uncaught TypeError: $(...).DataTable is not a function at HTMLDivElement. (plugins.js:3) at HTMLDivElement. (jquery-3.3.1.min.js:2) at Function.each (jquery-3.3.1.min.js:2) at w.fn.init.each (jquery-3.3.1.min.js:2) at Object. (jquery-3.3.1.min.js:2) at u (jquery-3.3.1.min.js:2) at Object.fireWith [as resolveWith] (jquery-3.3.1.min.js:2) at k (jquery-3.3.1.min.js:2) at XMLHttpRequest. (jquery-3.3.1.min.js:2) replication.js:244 Uncaught TypeError: $(...).DataTable is not a function at HTMLDivElement. (replication.js:244) at HTMLDivElement. (jquery-3.3.1.min.js:2) at Function.each (jquery-3.3.1.min.js:2) at w.fn.init.each (jquery-3.3.1.min.js:2) at Object. (jquery-3.3.1.min.js:2) at u (jquery-3.3.1.min.js:2) at Object.fireWith [as resolveWith] (jquery-3.3.1.min.js:2) at k (jquery-3.3.1.min.js:2) at XMLHttpRequest. (jquery-3.3.1.min.js:2) monitor.js:156 Uncaught TypeError: $(...).jstree is not a function at HTMLDivElement. (monitor.js:156) at HTMLDivElement. (jquery-3.3.1.min.js:2) at Function.each (jquery-3.3.1.min.js:2) at w.fn.init.each (jquery-3.3.1.min.js:2) at Object. (jquery-3.3.1.min.js:2) at u (jquery-3.3.1.min.js:2) at Object.fireWith [as resolveWith] (jquery-3.3.1.min.js:2) at k (jquery-3.3.1.min.js:2) at XMLHttpRequest. (jquery-3.3.1.min.js:2) servers.js:405 Uncaught TypeError: $(...).DataTable is not a function at HTMLDivElement. (servers.js:405) at HTMLDivElement. (jquery-3.3.1.min.js:2) at Function.each (jquery-3.3.1.min.js:2) at w.fn.init.each (jquery-3.3.1.min.js:2) at Object. (jquery-3.3.1.min.js:2) at u (jquery-3.3.1.min.js:2) at Object.fireWith [as resolveWith] (jquery-3.3.1.min.js:2) at k (jquery-3.3.1.min.js:2) at XMLHttpRequest. (jquery-3.3.1.min.js:2) security.js:60 Uncaught TypeError: $(...).DataTable is not a function at HTMLDivElement. (security.js:60) at HTMLDivElement. (jquery-3.3.1.min.js:2) at Function.each (jquery-3.3.1.min.js:2) at w.fn.init.each (jquery-3.3.1.min.js:2) at Object. (jquery-3.3.1.min.js:2) at u (jquery-3.3.1.min.js:2) at Object.fireWith [as resolveWith] (jquery-3.3.1.min.js:2) at k (jquery-3.3.1.min.js:2) at XMLHttpRequest. (jquery-3.3.1.min.js:2) backend.js:148 Uncaught TypeError: $(...).jstree is not a function at load_jstree (backend.js:148) at HTMLDivElement. (backend.js:210) at HTMLDivElement. (jquery-3.3.1.min.js:2) at Function.each (jquery-3.3.1.min.js:2) at w.fn.init.each (jquery-3.3.1.min.js:2) at Object. (jquery-3.3.1.min.js:2) at u (jquery-3.3.1.min.js:2) at Object.fireWith [as resolveWith] (jquery-3.3.1.min.js:2) at k (jquery-3.3.1.min.js:2) at XMLHttpRequest. (jquery-3.3.1.min.js:2) --- End Message --- --- Begin Message --- Source: 389-ds-base Source-Version: 1.4.0.21-1 We believe that the bug you reported is fixed in the latest version of 389-ds-base, 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
Processed: Re: Bug#919419: yatex: hangs while installing along xemacs21
Processing control commands: > tags -1 + patch Bug #919419 [yatex] yatex: hangs while installing along xemacs21 Added tag(s) patch. -- 919419: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919419 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#919419: yatex: hangs while installing along xemacs21
Control: tags -1 + patch
On January 16, 2019 at 8:27PM +0900, lurdan (at gmail.com) wrote:
> Anyway, I don't want be bothered by xemacs, I'll consider to exclude
> (or maybe conflict) xemacs21 from its dependency.
To avoid xemacs21, it's enough to skip old/unsupported flavors in
the install/remove scripts, though your yatex package seems
incompletely dh_elpa-fied. (old-style coexist and no byte-compilation)
Anyway, see the follwing patch to fix this bug.
```
--- a/debian/yatex.emacsen-install
+++ b/debian/yatex.emacsen-install
@@ -17,6 +17,11 @@
PACKAGE=yatex
FLAVOR=$1
+case $FLAVOR in
+*xemacs*|emacs2[0123]|emacs19|mule2)
+exit 0
+;;
+esac
ELDIR=/usr/share/emacs/site-lisp/${PACKAGE}/
ELCDIR=/usr/share/${FLAVOR}/site-lisp/${PACKAGE}/
diff -urN yatex-1.81/debian/yatex.emacsen-remove
yatex-1.81.new/debian/yatex.emacsen-remove
--- a/debian/yatex.emacsen-remove
+++ b/debian/yatex.emacsen-remove
@@ -8,6 +8,11 @@
PACKAGE=yatex
FLAVOR=$1
+case $FLAVOR in
+*xemacs*|emacs2[0123]|emacs19|mule2)
+exit 0
+;;
+esac
ELCDIR=/usr/share/$FLAVOR/site-lisp/$PACKAGE/
LOG=CompilationLog
```
Thanks,
--
Tatsuya Kinoshita
pgpvxnpJMbSi9.pgp
Description: PGP signature
Bug#922133: src:marionnet: build-depends/depends on cruft packages
Package: src:marionnet Version: 0.90.6+bzr508-1 Severity: serious Justification: fails to build from source (but built successfully in the past) liblablgtksourceview2-ocaml and liblablgtksourceview2-ocaml-dev are no longer built by lablgtk2 and will be removed. Marionnet build-depends on liblablgtksourceview2-ocaml-dev and as a result depends on liblablgtksourceview2-ocaml, which lablgtk2 no longer provides. The lablgtk2 maintainers have been asked to put it back, but in the mean time, it's a serious issue with this package. You may want to take it up with them. See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885677 Scott K
Bug#920839: marked as done (libmilib-java is uninstallable and will need rebuild with fixed libredberry-pipe-java)
Your message dated Tue, 12 Feb 2019 13:49:52 + with message-id and subject line Bug#920839: fixed in milib 1.10-1 has caused the Debian Bug report #920839, regarding libmilib-java is uninstallable and will need rebuild with fixed libredberry-pipe-java to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 920839: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920839 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libmilib-java Version: 1.9-1 Severity: serious Control: block -1 by 920838 Since binNMUs are not possible for binary-all this will require a maintainer upload. --- End Message --- --- Begin Message --- Source: milib Source-Version: 1.10-1 We believe that the bug you reported is fixed in the latest version of milib, 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 920...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Tille (supplier of updated milib package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 12 Feb 2019 14:22:59 +0100 Source: milib Binary: libmilib-java Architecture: source Version: 1.10-1 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team Changed-By: Andreas Tille Description: libmilib-java - library for Next Generation Sequencing (NGS) data processing Closes: 920839 Changes: milib (1.10-1) unstable; urgency=medium . * Team upload. * New upstream version * Build-Depends: libpicocli-java * Rebuild Closes: #920839 * Take over package to Debian Med team Checksums-Sha1: 013d9b518cb5b350040ed4adc06af8beb89f283d 2224 milib_1.10-1.dsc f03fac45e195897d0aef1125ed8db8c02a2292d8 241968 milib_1.10.orig.tar.xz 05ad699d4a7beaf0c4a5cbe793c959ab7f710dd3 3008 milib_1.10-1.debian.tar.xz Checksums-Sha256: 2c44225304b2f26ee0343fd7b1ccb726db4eae665b1677fb76db53a069b3c321 2224 milib_1.10-1.dsc 719691359a3e15084b589586adef6959c62f87a3acfc5f9c9f78ccbb5abcc8a2 241968 milib_1.10.orig.tar.xz 804f6ee50cd6b0b8491e3d4ed06e24ecbcc16384130842776e90af7a2c2af01e 3008 milib_1.10-1.debian.tar.xz Files: be9ae6bfb3b1e5fdd98a5d012ddedc1e 2224 java optional milib_1.10-1.dsc 8d538dd32a7007068adf82f97d103b2d 241968 java optional milib_1.10.orig.tar.xz e77716e6dbf445bda99259a4758407f1 3008 java optional milib_1.10-1.debian.tar.xz -BEGIN PGP SIGNATURE- iQJFBAEBCAAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAlxiyl0RHHRpbGxlQGRl Ymlhbi5vcmcACgkQV4oElNHGRtEuHBAAhOHqfGgP/gx6W6xEEl7avdNmvGu4Va4d mmGMWvGKgmD+AxYbbmAPzIRng+NE0s6GBXpr6xyKIa5SEtLS/H+gzgL/E1dsbcxh WuyhvJiAGiENnmtZNSA0ZGd8ufT4RzM5Kv8gR56ZGp/UC36PQNQxDQLUGcLbkf// c/CvW0A4LCvYIuPm3xnICYGM6b/vXOBXACh+wbp1LPLslZNkU1rE6UXFcD6u4nT9 fTom8X36pKTOuvOn86lf1nLZKG2iMVbpyPLU39gtIxQS+i3HIl+0ezMRYAytRm7q dRDGRAQRH3xSbm/1dhIxQUkhn29GCpRWsQpfhdv1LSusMzazJSy43d2E09tUXiGK v52ZQLqc4o+6Rw0wEVLUBGJ7XOlEUxcLtRgLOO8SSB3hT+MmgYvphWj3Lu6FG78L b9JgV3QvewKFgueanyYbtZv4/WXABLCG5BxBO+8Qz2GizXT9h9nGKS865byNKvni PewU20C6zWpOLqrH9N4CBMiAJWyVuT1lCWsSjPIb3uwZkMKB5Pg68RfoH4+zv4ax 7Sp/wO7wdvoxmNMa3+//QcZfu6i9WfGOFyVacZVaFHI/OSb41fqe1oS/y6hn3rGb 5z3mOdn4TyzZetDaLQARQJVH9Xtj/iGldZm0YnMVLoV8fNPYpZEqWjaQPw5irP3e ODupQbCQ8yg= =0Y6y -END PGP SIGNATURE End Message ---
Processed: found 922125 in 3.31.90-1
Processing commands for cont...@bugs.debian.org:
> found 922125 3.31.90-1
Bug #922125 {Done: Laurent Bigonville }
[gnome-settings-daemon] gtk-modules not loaded due to change in the path
Marked as found in versions gnome-settings-daemon/3.31.90-1 and reopened.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
922125: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922125
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#921495: Bioperl 1.7.4 should not migrate to Buster
On Mon, Feb 11, 2019 at 04:15:21PM +, Carnë Draug wrote: > > What do you think? > > All packages that depend on bioperl are being affected by this. The > current situation is a bit awkward because packaging and testing in > sid fails even though it would be fine in testing. This will cause > issues for new releases of such packages and for false positives in > Debian's ci. > > If you do make a new bioperl-run release, you can drop the following > dependencies: > > bowtie > bwa > maq > paml > t-coffee Done > but should add this new one (already packaged): > > libbio-tools-run-alignment-clustalw Arggg, no idea why I missed this in my upload. Just added in Git. Thanks for all your hints Andreas. -- http://fam-tille.de
Bug#922129: filemanager-actions: Incomplete debian/copyright?
Source: filemanager-actions Version: 3.4-2 Severity: serious Justication: Policy §12.5 X-Debbugs-CC: Carlos Maddela , ftpmas...@debian.org Hi, I just ACCEPTed filemanager-actions from NEW but noticed it was missing attribution in debian/copyright for at least Red Hat, Novell, etc. This is in no way exhaustive so please check over the entire package carefully and address these on your next upload. Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org 🍥 chris-lamb.co.uk `-
Bug#922128: gnome-books: Incomplete debian/copyright?
Source: gnome-books Version: 3.31.90-1 Severity: serious Justication: Policy §12.5 X-Debbugs-CC: Jeremy Bicha , ftpmas...@debian.org Hi, I just ACCEPTed gnome-books from NEW but noticed it was missing attribution in debian/copyright for at least Messrs Castellanos and Quinteiro. This is in no way exhaustive so please check over the entire package carefully and address these on your next upload. Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org 🍥 chris-lamb.co.uk `-
Bug#920604: marked as done (mongo-tools FTBFS with Go 1.11)
Your message dated Tue, 12 Feb 2019 13:20:51 + with message-id and subject line Bug#920604: fixed in mongo-tools 3.4.14-4 has caused the Debian Bug report #920604, regarding mongo-tools FTBFS with Go 1.11 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.) -- 920604: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920604 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: mongo-tools Version: 3.4.14-3 Severity: serious Tags: ftbfs https://buildd.debian.org/status/package.php?p=mongo-tools&suite=sid ... # _/<>/mongorestore ./filepath.go:357: Logvf call has arguments but no formatting directives FAIL_/<>/mongorestore [build failed] make[1]: *** [debian/rules:52: override_dh_auto_test] Error 2 --- End Message --- --- Begin Message --- Source: mongo-tools Source-Version: 3.4.14-4 We believe that the bug you reported is fixed in the latest version of mongo-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 920...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Apollon Oikonomopoulos (supplier of updated mongo-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: SHA256 Format: 1.8 Date: Tue, 12 Feb 2019 14:48:02 +0200 Source: mongo-tools Binary: mongo-tools Architecture: source amd64 Version: 3.4.14-4 Distribution: unstable Urgency: medium Maintainer: Debian MongoDB Maintainers Changed-By: Apollon Oikonomopoulos Description: mongo-tools - collection of tools for administering MongoDB servers Closes: 920604 Changes: mongo-tools (3.4.14-4) unstable; urgency=medium . * Fix FTBFS with Go 1.11 (Closes: #920604) * Bump Standards-Version to 4.3.0; no changes needed Checksums-Sha1: 9c21df8ce687271736ea2e687cdcb364a6231ab0 2393 mongo-tools_3.4.14-4.dsc 2e96c99067c8ca341000e219c940662c7f8d3a99 21652 mongo-tools_3.4.14-4.debian.tar.xz a2cb22afc5eab88f99db6859bf674b7565985765 19217832 mongo-tools-dbgsym_3.4.14-4_amd64.deb e68e19ee10c90cc4f82dde6d7039c098ebbf2736 6954 mongo-tools_3.4.14-4_amd64.buildinfo 4f6d62f882b256c1804d14610612a0e8a053f4f7 17868044 mongo-tools_3.4.14-4_amd64.deb Checksums-Sha256: 93efb9bffba26933f209a28f6dad287897b75cf49acea9623e8b92b59452717d 2393 mongo-tools_3.4.14-4.dsc dce5becf920f791da986d0f2467ae31da9eadaedf33315a5c79206ffc2b4e699 21652 mongo-tools_3.4.14-4.debian.tar.xz 16a43d96de2dec26eedc6d658a5d6fb373648752bfa350eac4e6ce7234d2fec8 19217832 mongo-tools-dbgsym_3.4.14-4_amd64.deb 10b835b7a20a036e5e231bb3584470aae890fe6de4db4d1dff21cd23788c5c12 6954 mongo-tools_3.4.14-4_amd64.buildinfo 4f80fff5d69d16f8edc17e32908a3b0768062475349978c0559e2b94ec46c380 17868044 mongo-tools_3.4.14-4_amd64.deb Files: 161b3f9620ab32b7a3e5c35941c8625a 2393 admin optional mongo-tools_3.4.14-4.dsc 449aa0cdc492088ce3e4c9d43e8f3dc8 21652 admin optional mongo-tools_3.4.14-4.debian.tar.xz 82b89fe18b8392c83fccfa2a856a050d 19217832 debug optional mongo-tools-dbgsym_3.4.14-4_amd64.deb df6b66a98e19dc8503799202aa2e0aec 6954 admin optional mongo-tools_3.4.14-4_amd64.buildinfo e7d76023222890f73c3db9c7033e4158 17868044 admin optional mongo-tools_3.4.14-4_amd64.deb -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEPgL9ZlYpWVIRC6uZ9RsYxyAkgiQFAlxiwpUACgkQ9RsYxyAk giR6hhAAnMtoiGOom8gM+F3fq+XcKBrbxzDs13Jb5xfF/it0BQrXI96LfERsaJgI ZWW2cEH4484ZyE9u9m2Jxx/pjV4MotDJX5j1yp/LS3nUaobve98gTCO7g82dgps+ JkKwMoXo3osJA9wECmq/Y3YDjbIWJ49M5s2SLpf1V3jGAvDBsjgqnTPNXeNa2v7K aYv2rKrON+myNDYlpTI5MZbsfZW1GH8q0cS5q32WYFaRCv0HSC/iMplu9AjgaJ91 FJY5mF9/SOFAI11Ho33o4y8yqPzwcdKv5eH7BCHYmK16MMT7mq14ugRJV1T5PFNy s/4BkPNrTRLUSaub18iGLzywzZU6eC5dWg/+m4KBpbwGHC/MbvPbr4O7aWAgBVRA OOQY+dONMZyRuCc3DaDS+GaPjENMxWKsDcF0L+wyLLhyvlbBHnktj6bVYUywvZpf f2KEYD6RsZ1YIhCF/YClPsNQThMzT49ccbol/TAZecMBKw2aH59OJBM1+VNYt/P3 tQgJg0kadwItZa7dPMDoHav0UCGgS0AXT2W+6qVswR8b5NZsMozxkqqkoqQhg2QQ B/4HlvIS/LDn8eeD6dbqAeDuIY2/I3PCvv/6+MxZijELzAxXXsmeN7lA5+imGHqf p7vgTSKLYB3/gP2UKTytIvQGyX+ZRfVA4RtLpqXKyZa8kTpMIu8= =9esw -END PGP SIGNATURE End Message ---
Bug#922125: marked as done (gtk-modules not loaded due to change in the path)
Your message dated Tue, 12 Feb 2019 13:19:18 + with message-id and subject line Bug#922125: fixed in gnome-settings-daemon 3.30.2-3 has caused the Debian Bug report #922125, regarding gtk-modules not loaded due to change in the path 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.) -- 922125: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922125 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: gnome-settings-daemon Version: 3.30.2-2 Severity: serious File: /usr/lib/gnome-settings-daemon/gsd-xsettings Hi, It seems that since the switch to meson, the path used in the gsd-xsettings for the gtk-modules is /usr/lib/*/gnome-settings-daemon-3.0/gtk-modules and not /usr/lib/gnome-settings-daemon-3.0/gtk-modules anymore. That means that all the modules (camberra, at-spi2,...) are not loaded anymore. We should probably set the libdir to /usr/lib/gnome-settings-daemon-3.0 -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-2-amd64 (SMP w/8 CPU cores) Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), LANGUAGE=fr_BE:fr (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages gnome-settings-daemon depends on: ii gnome-settings-daemon-common 3.30.2-2 ii gsettings-desktop-schemas 3.28.1-1 ii libasound21.1.8-1 ii libc6 2.28-7 ii libcairo2 1.16.0-2 ii libcanberra-gtk3-00.30-7 ii libcanberra0 0.30-7 ii libcolord21.4.3-4 ii libcups2 2.2.10-3 ii libfontconfig12.13.1-2 ii libgdk-pixbuf2.0-02.38.0+dfsg-7 ii libgeoclue-2-02.5.2-1 ii libgeocode-glib0 3.26.0-2 ii libglib2.0-0 2.58.3-1 ii libgnome-desktop-3-17 3.30.2.1-1 ii libgtk-3-03.24.5-1 ii libgudev-1.0-0232-2 ii libgweather-3-15 3.28.2-2 ii liblcms2-22.9-3 ii libnm01.14.4-4 ii libnotify40.7.7-4 ii libnspr4 2:4.20-1 ii libnss3 2:3.42-1 ii libpam-systemd240-5 ii libpango-1.0-01.42.4-6 ii libpangocairo-1.0-0 1.42.4-6 ii libpolkit-gobject-1-0 0.105-25 ii libpulse-mainloop-glib0 12.2-3 ii libpulse0 12.2-3 ii libupower-glib3 0.99.9-3 ii libwacom2 0.31-1 ii libwayland-client01.16.0-1 ii libx11-6 2:1.6.7-1 ii libxext6 2:1.3.3-1+b2 ii libxi62:1.7.9-1 Versions of packages gnome-settings-daemon recommends: ii iio-sensor-proxy 2.4-2 ii pulseaudio12.2-3 gnome-settings-daemon suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: gnome-settings-daemon Source-Version: 3.30.2-3 We believe that the bug you reported is fixed in the latest version of gnome-settings-daemon, 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 922...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Laurent Bigonville (supplier of updated gnome-settings-daemon package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 12 Feb 2019 13:24:57 +0100 Source: gnome-settings-daemon Architecture: source Version: 3.30.2-3 Distribution: unstable Urgency: medium Maintainer: Debian GNOME Maintainers Changed-By: Laurent Bigonville Closes: 922125 Changes: gnome-settings-daemon (3.30.2-3) unstable; urgency=medium . * debian/rules: Set libdir to /usr/lib, this is needed for the gtk-modules (Closes: #922125) Checksums-Sha1: b9d240ae35c3e0a22dd89b4222fc15b29618f034 3071 gnome-settings-daemon_3.30.2-3.dsc f65c1908a97e0280d5121449ca84c6a4eb890e2a 18672 gnome-settings-daemon_3.30.2-3.debian.tar.xz f981be3922d028be64fb1b556c35669c67d52f84 12355 gnome-setti
Processed: fixup bug metadata so britney knows bug is fixed.
Processing commands for cont...@bugs.debian.org:
> close 916615 0.10.0-2
Bug #916615 {Done: Sylvestre Ledru } [src:rust-ripgrep]
rust-ripgrep: FTBFS on big-endian targets due to testsuite failures
Marked as fixed in versions rust-ripgrep/0.10.0-2.
Bug #916615 {Done: Sylvestre Ledru } [src:rust-ripgrep]
rust-ripgrep: FTBFS on big-endian targets due to testsuite failures
Bug 916615 is already marked as done; not doing anything.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
916615: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916615
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: Bug #922125 in gnome-settings-daemon marked as pending
Processing control commands: > tag -1 pending Bug #922125 [gnome-settings-daemon] gtk-modules not loaded due to change in the path Added tag(s) pending. -- 922125: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922125 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#922125: Bug #922125 in gnome-settings-daemon marked as pending
Control: tag -1 pending Hello, Bug #922125 in gnome-settings-daemon reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/gnome-team/gnome-settings-daemon/commit/7a380f5b2162e4ffaebcf2f3b394a95ad36252be debian/rules: Set libdir to /usr/lib, this is needed for the gtk-modules Since the switch to meson, this has switched to /usr/lib/*/ by default, this is breaking the loading of some modules (at-spi2, canberra,...) Closes: #922125 (this message was generated automatically) -- Greetings https://bugs.debian.org/922125
Processed: Bug #922125 in gnome-settings-daemon marked as pending
Processing control commands: > tag -1 pending Bug #922125 [gnome-settings-daemon] gtk-modules not loaded due to change in the path Ignoring request to alter tags of bug #922125 to the same tags previously set -- 922125: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922125 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#922125: Bug #922125 in gnome-settings-daemon marked as pending
Control: tag -1 pending Hello, Bug #922125 in gnome-settings-daemon reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/gnome-team/gnome-settings-daemon/commit/91bd1267a129ab7362fca201b1779762980ff20f debian/rules: Set libdir to /usr/lib, this is needed for the gtk-modules Since the switch to meson, this has switched to /usr/lib/*/ by default, this is breaking the loading of some modules (at-spi2, canberra,...) Closes: #922125 (this message was generated automatically) -- Greetings https://bugs.debian.org/922125
Bug#921176: redis-server service is failing to start in buster lxc container
Hi Pirate, > > (However, I am not sure why I do not have working networking inside > > my container so I cannot debug it better on my end.) > > But loopback is enough for redis-server, right? Yes, but I can't even install without network. :) > I tried removing all hardening features and it still won't start. I > tried to start manually by running redis-server /etc/redis/redis.conf > as root and that worked. Can you try with the redis user? > > Also, perhaps enable some deeper logging? Or check the actual > > redis-server.log file too? > > There is nothing in /var/log/redis. I think its failing even before > redis-server gets a chance to log. Can you enable more systemd logging? If it's failing there, surely we can get more info than just "failed"? Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org 🍥 chris-lamb.co.uk `-
Bug#906476: marked as done (klystrack: FTBFS in buster/sid ('strncpy' output may be truncated))
Your message dated Tue, 12 Feb 2019 12:35:03 +
with message-id
and subject line Bug#906476: fixed in klystrack 0.20171212-4
has caused the Debian Bug report #906476,
regarding klystrack: FTBFS in buster/sid ('strncpy' output may be truncated)
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.)
--
906476: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906476
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:klystrack
Version: 0.20171212-3
Severity: serious
Tags: ftbfs
Dear maintainer:
I tried to build this package in buster but it failed:
[...]
debian/rules build-arch
dh build-arch --sourcedirectory=klystrack
dh_update_autotools_config -a -O--sourcedirectory=klystrack
dh_autoreconf -a -O--sourcedirectory=klystrack
dh_auto_configure -a -O--sourcedirectory=klystrack
debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
dh_auto_build -- CFG=release
cd klystrack && make -j1 "INSTALL=install --strip-program=true"
CFG=release
make[2]: Entering directory '/<>/klystrack'
Generating dependencies for timer.c...
Generating dependencies for sequence.c...
Generating dependencies for pattern.c...
Generating dependencies for wavetableview.c...
[... snipped ...]
src/gui/filebox.c:722:8: warning: 'strncpy' specified bound 256 equals
destination size [-Wstringop-truncation]
strncpy(data.field, data.files[data.selected_file].name,
sizeof(data.field));
^~~~
Compiling msgbox.c...
Compiling mouse.c...
Compiling menu.c...
Compiling dialog.c...
Compiling toolutil.c...
Compiling shortcuts.c...
src/gui/shortcuts.c: In function 'get_shortcut_string':
src/gui/shortcuts.c:67:3: warning: 'strncat' specified bound 100 equals
destination size [-Wstringop-overflow=]
strncat(buffer, "ctrl-", sizeof(buffer));
^~~~
src/gui/shortcuts.c:70:3: warning: 'strncat' specified bound 100 equals
destination size [-Wstringop-overflow=]
strncat(buffer, "alt-", sizeof(buffer));
^~~
src/gui/shortcuts.c:73:3: warning: 'strncat' specified bound 100 equals
destination size [-Wstringop-overflow=]
strncat(buffer, "shift-", sizeof(buffer));
^
Compiling bevel.c...
Linking engine...
make -C tools/makebundle
make[5]: Entering directory '/<>/klystron/tools/makebundle'
gcc -o ../bin/makebundle.exe -D_XOPEN_SOURCE makebundle.c -std=c99 -I ../../src
`sdl2-config --cflags` -Wall -O3
make[5]: Leaving directory '/<>/klystron/tools/makebundle'
make[4]: Leaving directory '/<>/klystron'
make[3]: Leaving directory '/<>/klystron'
make[3]: Entering directory '/<>/klystrack'
Generating dependencies for action.c...
Generating dependencies for main.c...
Generating dependencies for action.c...
Generating dependencies for main.c...
Compiling view.c...
src/view.c: In function 'info_line':
src/view.c:543:3: error: 'strncpy' output may be truncated copying 200 bytes
from a string of length 255 [-Werror=stringop-truncation]
strncpy(text, mused.info_message, sizeof text);
^~
cc1: all warnings being treated as errors
make[3]: *** [Makefile:158: objs.release/view.o] Error 1
make[3]: Leaving directory '/<>/klystrack'
make[2]: *** [Makefile:137: build] Error 2
make[2]: Leaving directory '/<>/klystrack'
dh_auto_build: cd klystrack && make -j1 "INSTALL=install --strip-program=true"
CFG=release returned exit code 2
make[1]: *** [debian/rules:15: override_dh_auto_build] Error 2
make[1]: Leaving directory '/<>'
make: *** [debian/rules:12: build-arch] Error 2
dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit
status 2
The build was made with "dpkg-buildpackage -B" in my autobuilder.
Most probably, it also fails here in reproducible builds:
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/klystrack.html
where you can get a full build log if you need it.
If this is really a bug in one of the build-depends, please use reassign and
affects,
so that this is still visible in the BTS web page for this package.
Thanks.
--- End Message ---
--- Begin Message ---
Source: klystrack
Source-Version: 0.20171212-4
We believe that the bug you reported is fixed in the latest version of
klystrack, which is due to be installed in the Debian FTP archive.
A summa
Processed: bug 921637 is forwarded to https://github.com/apjanke/ronn-ng/issues/24
Processing commands for cont...@bugs.debian.org: > forwarded 921637 https://github.com/apjanke/ronn-ng/issues/24 Bug #921637 [ronn] ronn 0.8.0-1 breaks man pages with numbered lists Set Bug forwarded-to-address to 'https://github.com/apjanke/ronn-ng/issues/24'. > thanks Stopping processing here. Please contact me if you need assistance. -- 921637: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921637 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#922125: gtk-modules not loaded due to change in the path
Package: gnome-settings-daemon Version: 3.30.2-2 Severity: serious File: /usr/lib/gnome-settings-daemon/gsd-xsettings Hi, It seems that since the switch to meson, the path used in the gsd-xsettings for the gtk-modules is /usr/lib/*/gnome-settings-daemon-3.0/gtk-modules and not /usr/lib/gnome-settings-daemon-3.0/gtk-modules anymore. That means that all the modules (camberra, at-spi2,...) are not loaded anymore. We should probably set the libdir to /usr/lib/gnome-settings-daemon-3.0 -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-2-amd64 (SMP w/8 CPU cores) Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), LANGUAGE=fr_BE:fr (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages gnome-settings-daemon depends on: ii gnome-settings-daemon-common 3.30.2-2 ii gsettings-desktop-schemas 3.28.1-1 ii libasound21.1.8-1 ii libc6 2.28-7 ii libcairo2 1.16.0-2 ii libcanberra-gtk3-00.30-7 ii libcanberra0 0.30-7 ii libcolord21.4.3-4 ii libcups2 2.2.10-3 ii libfontconfig12.13.1-2 ii libgdk-pixbuf2.0-02.38.0+dfsg-7 ii libgeoclue-2-02.5.2-1 ii libgeocode-glib0 3.26.0-2 ii libglib2.0-0 2.58.3-1 ii libgnome-desktop-3-17 3.30.2.1-1 ii libgtk-3-03.24.5-1 ii libgudev-1.0-0232-2 ii libgweather-3-15 3.28.2-2 ii liblcms2-22.9-3 ii libnm01.14.4-4 ii libnotify40.7.7-4 ii libnspr4 2:4.20-1 ii libnss3 2:3.42-1 ii libpam-systemd240-5 ii libpango-1.0-01.42.4-6 ii libpangocairo-1.0-0 1.42.4-6 ii libpolkit-gobject-1-0 0.105-25 ii libpulse-mainloop-glib0 12.2-3 ii libpulse0 12.2-3 ii libupower-glib3 0.99.9-3 ii libwacom2 0.31-1 ii libwayland-client01.16.0-1 ii libx11-6 2:1.6.7-1 ii libxext6 2:1.3.3-1+b2 ii libxi62:1.7.9-1 Versions of packages gnome-settings-daemon recommends: ii iio-sensor-proxy 2.4-2 ii pulseaudio12.2-3 gnome-settings-daemon suggests no packages. -- no debconf information
Bug#893227: libbluray FTBFS with openjdk-9
On 2019-02-12 13:04:57, Petri Hintukainen wrote: > Hello, > > On 2019-02-11 21:28, Sebastian Ramacher wrote: > > Thanks for working on this issue. What's the status of the release? > > Will it be available soon? > > 1.1.0 release has been tagged and should appear in downloads soon. > > I've tested a lot of BD-J apps with OpenJDK 11, and it seems to work > just well. I'd still expect some new issues when people start using it, > but we can fix those later. > > Looking at the diff between 1.0.2 and 1.1.0 I wouldn't expect much of > other regressions than those related to OpenJDK 11; there are no other > "significant" changes. I left out some other pending changes due to the > tight schedule. > > No changes to applications are required. ABI minor version has been > bumped because of there's one new field at the end of one libbluray- > allocated public struct. Thanks! That's good news. I'll upload it as soon as it appears in downloads. Cheers > > - Petri > -- Sebastian Ramacher signature.asc Description: PGP signature
Bug#893227: libbluray FTBFS with openjdk-9
Hello, On 2019-02-11 21:28, Sebastian Ramacher wrote: > Thanks for working on this issue. What's the status of the release? > Will it be available soon? 1.1.0 release has been tagged and should appear in downloads soon. I've tested a lot of BD-J apps with OpenJDK 11, and it seems to work just well. I'd still expect some new issues when people start using it, but we can fix those later. Looking at the diff between 1.0.2 and 1.1.0 I wouldn't expect much of other regressions than those related to OpenJDK 11; there are no other "significant" changes. I left out some other pending changes due to the tight schedule. No changes to applications are required. ABI minor version has been bumped because of there's one new field at the end of one libbluray- allocated public struct. - Petri
Bug#815393: marked as done (pypuppetdb: FTBFS: E: pybuild pybuild:274: test: plugin custom failed with: exit code=5: python2.7 -m pytest -m unit)
Your message dated Tue, 12 Feb 2019 10:53:21 +
with message-id
and subject line Bug#815393: fixed in pypuppetdb 0.3.3-1
has caused the Debian Bug report #815393,
regarding pypuppetdb: FTBFS: E: pybuild pybuild:274: test: plugin custom failed
with: exit code=5: python2.7 -m pytest -m unit
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
815393: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815393
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pypuppetdb
Version: 0.1.1+git080614-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org
Dear Maintainer,
pypuppetdb fails to build from source in unstable/amd64:
[..]
debian/rules override_dh_auto_test
make[1]: Entering directory
'/home/lamby/temp/cdt.20160221091633.CnPq7WYdDo/pypuppetdb-0.1.1+git080614'
PYBUILD_SYSTEM=custom \
PYBUILD_TEST_ARGS="{interpreter} -m pytest -m unit" \
dh_auto_test
I: pybuild base:184: python2.7 -m pytest -m unit
= test session starts
==
platform linux2 -- Python 2.7.11, pytest-2.8.7, py-1.4.31, pluggy-0.3.1
rootdir:
/home/lamby/temp/cdt.20160221091633.CnPq7WYdDo/pypuppetdb-0.1.1+git080614,
inifile: setup.cfg
collected 60 items
== 60 tests deselected by "-m 'unit'"
==
60 deselected in 0.13 seconds
=
E: pybuild pybuild:274: test: plugin custom failed with: exit code=5:
python2.7 -m pytest -m unit
dh_auto_test: pybuild --test --test-tox -i python{version} -p 2.7 --dir .
returned exit code 13
debian/rules:12: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 25
make[1]: Leaving directory
'/home/lamby/temp/cdt.20160221091633.CnPq7WYdDo/pypuppetdb-0.1.1+git080614'
debian/rules:6: recipe for target 'build' failed
make: *** [build] Error 2
[..]
The full build log is attached.
Regards,
--
,''`.
: :' : Chris Lamb
`. `'` la...@debian.org / chris-lamb.co.uk
`-
pypuppetdb.0.1.1+git080614-1.unstable.amd64.log.txt.gz
Description: Binary data
--- End Message ---
--- Begin Message ---
Source: pypuppetdb
Source-Version: 0.3.3-1
We believe that the bug you reported is fixed in the latest version of
pypuppetdb, 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 815...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Apollon Oikonomopoulos (supplier of updated pypuppetdb
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, 11 Feb 2019 22:59:56 +0200
Source: pypuppetdb
Binary: python-pypuppetdb python3-pypuppetdb
Architecture: source all
Version: 0.3.3-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team
Changed-By: Apollon Oikonomopoulos
Description:
python-pypuppetdb - interface to the PuppetDB REST API
python3-pypuppetdb - interface to the PuppetDB REST API (Python 3)
Closes: 815393
Changes:
pypuppetdb (0.3.3-1) unstable; urgency=medium
.
* New upstream version 0.3.3
* Add myself to Uploaders
* d/control: update Homepage URL
* d/watch: Use Github
* d/watch: ignore bogus upstream version 3.3.3
* Fix tests (Closes: #815393)
+ Drop B-D on python-tox to force using pytest
+ B-D on python-bandit and run the bandit tests
+ B-D on python-cov
* override_dh_auto_test: test for `nocheck' in DEB_BUILD_OPTIONS
* Bump Standards-Version to 4.3.0; no changes needed
* d/control: use HTTPS for Vcs-*
* Fix header name case for Python 3
* Disable tests for Python 2
* d/control: drop X-Python*-Version fields
* Bump dh compat to 11; no changes needed
* Switch Vcs-* URLs to salsa.d.o
* d/control: fix typo in description
Checksums-Sha1:
e0121212287ec0cca83751176482043109a96572 2405 pypuppetdb_0.3.3-1.dsc
13e59e7cf6aac64677d5f21441107631a5508605 45871 pypuppetdb_0.3.3.orig.tar.gz
5a0598287d49e67ecc5997f4f727ceb66cdd 2720 pypu
Bug#921736: marked as done (minissdpd: Script in d/minissdpd.config uses /sbin/ifconfig, but package does not depend on net-tools)
Your message dated Tue, 12 Feb 2019 10:52:41 + with message-id and subject line Bug#921736: fixed in minissdpd 1.5.20180223-6 has caused the Debian Bug report #921736, regarding minissdpd: Script in d/minissdpd.config uses /sbin/ifconfig, but package does not depend on net-tools 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.) -- 921736: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921736 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: minissdpd Version: 1.5.20180223-5 Severity: important Dear Maintainer, the script in debian/minissdpd.config uses /sbin/ifconfig, but the package does not depend on net-tools, causing the script to fail on upgrades if net-tools is not installed. -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.18.0-3-amd64 (SMP w/8 CPU cores) Kernel taint flags: TAINT_WARN Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages minissdpd depends on: ii debconf [debconf-2.0] 1.5.70 ii init-system-helpers1.56+nmu1 ii libc6 2.28-6 ii libnfnetlink0 1.0.1-3+b1 ii lsb-base 10.2018112800 minissdpd recommends no packages. minissdpd suggests no packages. --- End Message --- --- Begin Message --- Source: minissdpd Source-Version: 1.5.20180223-6 We believe that the bug you reported is fixed in the latest version of minissdpd, 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 921...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Thomas Goirand (supplier of updated minissdpd package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 12 Feb 2019 11:19:29 +0100 Source: minissdpd Binary: minissdpd minissdpd-dbgsym Architecture: source amd64 Version: 1.5.20180223-6 Distribution: unstable Urgency: medium Maintainer: Thomas Goirand Changed-By: Thomas Goirand Description: minissdpd - keep memory of all UPnP devices that announced themselves Closes: 921736 Changes: minissdpd (1.5.20180223-6) unstable; urgency=medium . * debian/minissdpd.config: do not use /sbin/ifconfig if it's not available. Fallback to reading /proc/net/route if we can read it. (Closes: #921736). Checksums-Sha1: f8825a36df63bb557935727e88e9a7bdb8c235db 2097 minissdpd_1.5.20180223-6.dsc 47dab94e4f87b10f86d05c7e359e36d7e4ad9e54 17084 minissdpd_1.5.20180223-6.debian.tar.xz b49e7eb1bf0ec830d07681caf6cf66397bc2d606 56156 minissdpd-dbgsym_1.5.20180223-6_amd64.deb 3d8062ac6dd4d0dcdc31fdf179b2a4a62ee34cad 5723 minissdpd_1.5.20180223-6_amd64.buildinfo 7d75e914ced1933eba6482cc9b7f42d4f55a1ec0 33396 minissdpd_1.5.20180223-6_amd64.deb Checksums-Sha256: 58e4afc8950ccd2c0c9047da00f563ea8f66bc8db7578d54efb470ffd7d9f3c0 2097 minissdpd_1.5.20180223-6.dsc 697ccb1b03e2f22576bbaeb798d3931fd433a45215524a31950268ebcf3b21ea 17084 minissdpd_1.5.20180223-6.debian.tar.xz 6152503f5cfb1cc6373ec6561ab910313831e3393748e1a4f935a7bcfcd46393 56156 minissdpd-dbgsym_1.5.20180223-6_amd64.deb 47a3b00e1bc4ee239b886f7ed678c1c7f0dbc5ba6a882fccf4263b41df32d041 5723 minissdpd_1.5.20180223-6_amd64.buildinfo f48ab549f7b58b90cebc3e3d7274ec5d2def34b8c3a17abea773883fd72284ba 33396 minissdpd_1.5.20180223-6_amd64.deb Files: 27e9d8b1b2194b527c319b40f44a008f 2097 net optional minissdpd_1.5.20180223-6.dsc 698d7d88f44d1eda7ec0ec61edeef328 17084 net optional minissdpd_1.5.20180223-6.debian.tar.xz 79961e310ca3398cdead21a669fc34bd 56156 debug optional minissdpd-dbgsym_1.5.20180223-6_amd64.deb 40f3bb2395363af255c39e6b7a6dffe8 5723 net optional minissdpd_1.5.20180223-6_amd64.buildinfo b533dccd086b0a36cc8fa6e531e40031 33396 net optional minissdpd_1.5.20180223-6_amd64.deb -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEoLGp81CJVhMOekJc1BatFaxrQ/4FAlxinpoACgkQ1BatFaxr Q/47aBAAoYtZTz5p94+FxzbSliSvky3qq+wFqjdILv//UjHXyYcY127Ry8I8C2Ns fDukBCYWILKz0QhOd//oyGDtgiPsUVMjOn8xJgUPvS7YwfeYrruQtVwihfwsa+TP NNrHgOBR3nXSvRgzMzr
Bug#922112: fio: hash.h is not DFSG compliant
Closing bug report for now as Jens, upstream maintainer of fio, claims that the file is GPL2. Feel free to reopen in case you have evidence that it is not *after* or *with* but not *before* you provided that evidence. Jens, I cc'd you cause this bug report has the potential to remove fio package from Debian, so… in case you could elaborate a bit more on the source of hash.c so that those who doubt it is GPL-2 can see that it is, it would be helpful. Dear Domenico. It would have been nice to at least give one or two days to clear up the issue before filing a bug report of grave severity. It is not that the file in fio has been there for *years* without anyone complaining or that Debian Buster would have been released today without the bug report in place. I am currently holding a training, thus there may be delays in replying. Domenico Andreoli - 12.02.19, 09:26: > Package: fio > Severity: grave > > According to debian/copyright, hash.h is licensed as GPL-2+ but this > is not true. There is not any mention of license attribution in its > verifiable history, not by its copyright holder or anybody else on > their behalf. I attach a mail from Jens Axboe, upstream maintainer of fio, where he claims that like any other files that have no special license information this file also is GPL-2. I do have the original mail complete with headers available. I also cc'd Jens. As I did not see any evidence that contradicts what Jens claims here I have no reason not to believe him. Of course feel free to provide such evidence and raise the severity of the bug again in case you do so. Mit freundlichen Grüßen / With kind regards Martin Steigerwald • Proact Deutschland GmbH Trainer Telefon: +49 911 30999 0 • Fax: +49 911 30999 99 Südwestpark 43 • 90449 Nürnberg • Germany martin.steigerw...@proact.de • www.proact.de Amtsgericht Nürnberg • HRB 18320 Geschäftsführer: Oliver Kügow • Richard Müller • Jakob Høholdt • Peter Mikael Javestad – Delivering Business Agility – -- Forwarded Message -- Betreff: Re: Licensing of include/linux/hash.h Datum: Montag, 11. Februar 2019, 23:55:22 CET Von: Jens Axboe An: Martin Steigerwald , Domenico Andreoli Kopie: Kristian Fiskerstrand , Ben Finney , Nadia Yvette Chambers , Arnaldo Carvalho de Melo , 919...@bugs.debian.org <919...@bugs.debian.org>, debian-le...@lists.debian.org , linux-ker...@vger.kernel.org , Jens Axboe On 2/11/19 3:50 AM, Martin Steigerwald wrote: > Adding in ax...@kernel.dk, as I am not sure whether the oracle.com address > from Jens is actually valid / up to date. > > Domenico Andreoli - 11.02.19, 08:22: >> On Mon, Feb 11, 2019 at 12:08:32AM +0100, Kristian Fiskerstrand wrote: >> > > Mit freundlichen Grüßen / With kind regards > > Martin Steigerwald • > Proact Deutschland GmbH [… mail signature …] > On 1/23/19 9:50 AM, Domenico Andreoli wrote: >> > > Ben Finney writes: >> > >> Domenico Andreoli writes: >> [...] >> >> > >>> the only knot left is now the license of hash.h >> > >>> >> > >>> This file is also present in the kernel [0] with an updated copyright >> > >>> but still without license. >> >> [...] >> >> > >> To know that work (that file) is free software, we need a clear grant >> > >> of >> > >> some specific license, for that work. >> > >> >> > >> If the work is not free, it would be incorrect to have the work in >> > >> Debian. >> > > >> > > Is it possible that for the kernel it is instead correct because it is, >> > > as whole, covered by its COPYING? >> > > >> > >> Alternatives, for complying with the Debian Free Software Guidelines >> > >> with >> > >> this package, include: >> > >> >> > >> * Find a credible grant of license under some GPL-compatible free >> > >> >> > >> license to that exact file. Document that explicit grant in the >> > >> Debian >> > >> package. This demonstrates the work is DFSG-free. >> > >> >> > >> * Convince ???dwarves-dfsg??? upstream to replace that file with a >> > >> different> >> >> > >> implementation (I don't know whether such an implementation exists) >> > >> under a license compatible with the same version of GNU GPL. Document >> > >> that explicit grant in the Debian package. This demonstrates the >> > >> modified work is DFSG-free. >> > >> >> > >> * Replace that file in Debian only, with a different implementation as >> > >> >> > >> above. Document that explicit grant in the Debian package. This >> > >> demonstrates the modified Debian package is DFSG-free. >> > >> >> > >> * Move the work to the ???non-free??? area. >> > >> >> > >> * Remove the work altogether. >> > >> >> > >> Those are in descending order of (my recommended) preference. >> >> [...] >> >> > It was [pointed out] by one of our license group that [hash.h] is the >> > same that has a GPL-2+ in [fio] which has a signed-off-by. >> > >> > References: >> > [pointed out] >> > https://bugs.gentoo.org/677586#c1 >> > >> > [hash.h] >> > https://git.kernel.org/pub/scm/linux/kernel/git/axboe/fio.git/commit/hash. >> > h?id=bdc7211
Bug#922112: marked as done (fio: hash.h is not DFSG compliant)
Your message dated Tue, 12 Feb 2019 10:39:08 + with message-id <1637429.ihVJye5Aa2@merkaba> and subject line Re: Bug#922112: fio: hash.h is not DFSG compliant has caused the Debian Bug report #922112, regarding fio: hash.h is not DFSG compliant 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.) -- 922112: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922112 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: fio Severity: grave According to debian/copyright, hash.h is licensed as GPL-2+ but this is not true. There is not any mention of license attribution in its verifiable history, not by its copyright holder or anybody else on their behalf. Thanks to Ulrich Mueller for the relevant research [0]. Similar bug is reported to package dwarves [1], which includes on older copy of this same file. Regards, Domenico [0] https://lkml.org/lkml/2019/2/11/773 [1] https://bugs.debian.org/919356 -- 3B10 0CA1 8674 ACBA B4FE FCD2 CE5B CF17 9960 DE13 signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Closing bug report for now as Jens, upstream maintainer of fio, claims that the file is GPL2. Feel free to reopen in case you have evidence that it is not *after* or *with* but not *before* you provided that evidence. Jens, I cc'd you cause this bug report has the potential to remove fio package from Debian, so… in case you could elaborate a bit more on the source of hash.c so that those who doubt it is GPL-2 can see that it is, it would be helpful. Dear Domenico. It would have been nice to at least give one or two days to clear up the issue before filing a bug report of grave severity. It is not that the file in fio has been there for *years* without anyone complaining or that Debian Buster would have been released today without the bug report in place. I am currently holding a training, thus there may be delays in replying. Domenico Andreoli - 12.02.19, 09:26: > Package: fio > Severity: grave > > According to debian/copyright, hash.h is licensed as GPL-2+ but this > is not true. There is not any mention of license attribution in its > verifiable history, not by its copyright holder or anybody else on > their behalf. I attach a mail from Jens Axboe, upstream maintainer of fio, where he claims that like any other files that have no special license information this file also is GPL-2. I do have the original mail complete with headers available. I also cc'd Jens. As I did not see any evidence that contradicts what Jens claims here I have no reason not to believe him. Of course feel free to provide such evidence and raise the severity of the bug again in case you do so. Mit freundlichen Grüßen / With kind regards Martin Steigerwald • Proact Deutschland GmbH Trainer Telefon: +49 911 30999 0 • Fax: +49 911 30999 99 Südwestpark 43 • 90449 Nürnberg • Germany martin.steigerw...@proact.de • www.proact.de Amtsgericht Nürnberg • HRB 18320 Geschäftsführer: Oliver Kügow • Richard Müller • Jakob Høholdt • Peter Mikael Javestad – Delivering Business Agility – -- Forwarded Message -- Betreff: Re: Licensing of include/linux/hash.h Datum: Montag, 11. Februar 2019, 23:55:22 CET Von: Jens Axboe An: Martin Steigerwald , Domenico Andreoli Kopie: Kristian Fiskerstrand , Ben Finney , Nadia Yvette Chambers , Arnaldo Carvalho de Melo , 919...@bugs.debian.org <919...@bugs.debian.org>, debian-le...@lists.debian.org , linux-ker...@vger.kernel.org , Jens Axboe On 2/11/19 3:50 AM, Martin Steigerwald wrote: > Adding in ax...@kernel.dk, as I am not sure whether the oracle.com address > from Jens is actually valid / up to date. > > Domenico Andreoli - 11.02.19, 08:22: >> On Mon, Feb 11, 2019 at 12:08:32AM +0100, Kristian Fiskerstrand wrote: >> > > Mit freundlichen Grüßen / With kind regards > > Martin Steigerwald • > Proact Deutschland GmbH [… mail signature …] > On 1/23/19 9:50 AM, Domenico Andreoli wrote: >> > > Ben Finney writes: >> > >> Domenico Andreoli writes: >> [...] >> >> > >>> the only knot left is now the license of hash.h >> > >>> >> > >>> This file is also present in the kernel [0] with an updated copyright >> > >>> but still without license. >> >> [...] >> >> > >> To know that work (that file) is free software, we need a clear grant >> > >> of >> > >> some specific license, for that work. >> > >> >> > >> If the work is not free, it would be incorrect to have the work in >> > >> Debian. >> > > >> > > Is it possible that for the kernel it is instead correct because it is, >> > > as whole, covered by its COPYING? >> > > >> > >> Alt
Bug#919974: marked as done (yapf: Python 2 removal breaks build dependencies of other packages)
Your message dated Tue, 12 Feb 2019 10:35:45 + with message-id and subject line Bug#919974: fixed in yapf 0.25.0-2.1 has caused the Debian Bug report #919974, regarding yapf: Python 2 removal breaks build dependencies of other packages 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.) -- 919974: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919974 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: yapf Version: 0.25.0-1 Severity: serious Control: affects -1 src:forensic-artifacts src:backblaze-b2 yapf (0.25.0-1) unstable; urgency=medium ... [ Ana C. Custura ] * debian/control: - updates standards version to 4.3.0 - bumps debhelper version to 12 - removes support for end-of-life Python 2 * debian/compat: - bumps debhelper vesion to 12 * debian/rules: - removes support for end-of-life Python 2 -- Ana Custura Sun, 06 Jan 2019 22:15:35 + Python 2 might become end-of-life next year, but Debian buster does fully (security) support Python 2 in buster until the EOL of buster mid-2022. Note that most of the software in a stable Debian release is no longer upstream supported during the lifetime of a Debian release. Does yapf upstream support 0.25 until mid-2022? Chances are yapf 0.25 might be as unsupported as Python 2.7 in 2022. This is only a problem when not-backportable security fixes are expected. The unnecessary removal of Python 2 support in yapf did break the build dependencies of other packages in buster. --- End Message --- --- Begin Message --- Source: yapf Source-Version: 0.25.0-2.1 We believe that the bug you reported is fixed in the latest version of yapf, 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 919...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Hilko Bengen (supplier of updated yapf package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 09 Feb 2019 18:12:41 +0100 Source: yapf Binary: python-yapf yapf python3-yapf yapf3 Architecture: source Version: 0.25.0-2.1 Distribution: unstable Urgency: medium Maintainer: Ana Custura Changed-By: Hilko Bengen Description: python-yapf - public modules for yapf (Python 2) python3-yapf - public modules for yapf (Python 3) yapf - Python code formatter for different styles (Python 2) yapf3 - Python code formatter for different styles (Python 3) Closes: 919974 Changes: yapf (0.25.0-2.1) unstable; urgency=medium . * Non-maintainer upload * Revert removal of Python2 support (Closes: #919974) * Re-add yapf documentation files Checksums-Sha1: 71bd87d8cf4ad86731c92d74e837e2ee987de4e3 2289 yapf_0.25.0-2.1.dsc 309da615ad14930ed4899170ddee4300fe70eaaf 4000 yapf_0.25.0-2.1.debian.tar.xz 5d9f2f2557c015ded78480e56b57f861a35e0cf7 7139 yapf_0.25.0-2.1_source.buildinfo Checksums-Sha256: 9705c30c80290776bb044b523b76598b76ffd7f172c40f421bafb76e94b59995 2289 yapf_0.25.0-2.1.dsc 95a3ef06f26bb52cc373da603ffc483e8cdbd5fdd5ba88417cf5c75177e93ca0 4000 yapf_0.25.0-2.1.debian.tar.xz ba983f37abf67e97484c9a1d858258e13176739a68b502ffbeedf0d68216b5af 7139 yapf_0.25.0-2.1_source.buildinfo Files: 743245abb4e7010dfdbe286ec4ef5531 2289 python optional yapf_0.25.0-2.1.dsc 15112791c7a8c4e393318792d721611d 4000 python optional yapf_0.25.0-2.1.debian.tar.xz 32808ad46261adb44293045267fe10ac 7139 python optional yapf_0.25.0-2.1_source.buildinfo -BEGIN PGP SIGNATURE- iQJGBAEBCAAwFiEErnMQVUQqHZbPTUx4dbcQY1whOn4FAlxinUkSHGJlbmdlbkBk ZWJpYW4ub3JnAAoJEHW3EGNcITp+7nEP/1kLd5pgkedWeKu037Xh5I0EhKfU+3wY 8EZjJfELQbYMIqfZKOSUzQxntE0SBI2CgMT89KOMGe8Ou8QVV9QtpwHvyQiHPBcZ EAo/bb08WNraxqIsPKp57D5w6LPjaTUqrM0OeheEcWE5iFqAaQZ6mUX7ySFDDXp6 pd8oRqCxptqmKU7WDf4sX/kawfUczYj+0u6oCPRlVyXQ89IlTizqM2y1LgdFd003 C/d6BnTDoxtWklXK0N+JXPR4P59OvC43hmFbUajvkOipCRO5wTOedZqDKbKuZ86e sbIBLBGF0HjjOXpRBW30L6/55mxOmd0KCnuOyW4F+r2naLEpKKaoLIUykFKNyPCa 9rL2kvIw0ZxrdJUM7XCv2577ceKAnZLBXt0wRfAqPOQb6lhEDGQfOlFH1mUZQUN7 CJXyvCawds3Shx2buA51+aZLawe9B7vEmSh/0AGhlGd0090vxCdiqjUFnG3NpszQ 1mDQcY8zmhaivy+AYykE+T01+WS/aNgO8Cu4H0JKih7g+Hzv5OQsfguRzKsl/1ID +OtDvCpNzveDN6cVuW/qh89nF9rHbgeQdgDJpgmJQbK/4UL9m1GM0UhNMFUimARW 2nApj1I9eJbcp
Bug#921176: redis-server service is failing to start in buster lxc container
On ചൊ, ഫെബ്രു 5, 2019 at 11:14 വൈകു, Chris Lamb wrote: severity 921176 serious thanks Hi Pirate, [Dropping severity as it only affects LXC right now] It is working on the same host machine with stretch(-backports) container (5:5.0.3-3~bpo9+2). So host machine seems fine. Thanks for looking into this and providing some LXC basics. (However, I am not sure why I do not have working networking inside my container so I cannot debug it better on my end.) But loopback is enough for redis-server, right? On the other hand, the first thing I would do if this was working would be to try removing more hardening features as previously discussed on this bug number until it (likely) worked. Could you try this please? I tried removing all hardening features and it still won't start. I tried to start manually by running redis-server /etc/redis/redis.conf as root and that worked. Also, perhaps enable some deeper logging? Or check the actual redis-server.log file too? There is nothing in /var/log/redis. I think its failing even before redis-server gets a chance to log. I found this https://github.com/systemd/systemd/issues/10032 and tried updating systemd on host to 240-5 (from 238-5) and also updating apparmor and disabling apparmor. But none of it worked.
