Processed: Bug#933002 marked as pending in docker.io
Processing control commands: > tag -1 pending Bug #933002 [src:docker.io] docker.io: CVE-2019-13139 Added tag(s) pending. -- 933002: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933002 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#933002: marked as pending in docker.io
Control: tag -1 pending Hello, Bug #933002 in docker.io 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/docker-team/docker/commit/10054348c2e9dcb9a1c26689921adb9cb809f452 Add upstream patch for CVE-2019-13139 (Closes: #933002) Signed-off-by: Arnaud Rebillout (this message was generated automatically) -- Greetings https://bugs.debian.org/933002
Bug#933923: marked as done (src:valinor: Incompatible with safe load changes in new pyyaml)
Your message dated Mon, 05 Aug 2019 08:44:08 +
with message-id
and subject line Bug#933923: fixed in valinor 1.1.0-2
has caused the Debian Bug report #933923,
regarding src:valinor: Incompatible with safe load changes in new pyyaml
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.)
--
933923: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933923
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:valinor
Version: 1.1.0-1
Severity: grave
Justification: renders package unusable
FAIL: testARMNoneEABIGDB (test.test_outputdir.TestCLIOutputDirectory)
--
Traceback (most recent call last):
File
"/tmp/autopkgtest-lxc.eh9dq_op/downtmp/autopkgtest_tmp/test/test_outputdir.py",
line 48, in testARMNoneEABIGDB
runWithDir()
File
"/tmp/autopkgtest-lxc.eh9dq_op/downtmp/autopkgtest_tmp/test/test_outputdir.py",
line 46, in runWithDir
out = self.runCheck(args)
File
"/tmp/autopkgtest-lxc.eh9dq_op/downtmp/autopkgtest_tmp/test/test_outputdir.py",
line 33, in runCheck
self.assertEqual(status, 0)
AssertionError: 1 != 0
>> begin captured stdout << -
Traceback (most recent call last):
File "", line 1, in
File "/usr/share/valinor/valinor/main.py", line 36, in main
version=pkg_resources.require("valinor")[0].version,
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 900, in
require
needed = self.resolve(parse_requirements(requirements))
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 791, in
resolve
raise VersionConflict(dist, req).with_context(dependent_req)
pkg_resources.ContextualVersionConflict: (PyYAML 5.1.2
(/usr/lib/python3/dist-packages), Requirement.parse('pyyaml<4,>=3'),
{'valinor'})
The new version of pyyaml no longer allows use of yaml.load() without a
loader being specifed. This raises a deprecation warning which has
caused and autopkgtest failure on this package. These are generally
trivial to fix, see the upstream guidance [1].
That's likely the change that caused upstream to have <4 for the pyyaml
version. You ought to be able to fix it pretty easily and then remove
the upper version constraint, assuming there's no upstream fix yet.
Scott K
[1] https://github.com/yaml/pyyaml/wiki/PyYAML-yaml.load(input)-Deprecation
--- End Message ---
--- Begin Message ---
Source: valinor
Source-Version: 1.1.0-2
We believe that the bug you reported is fixed in the latest version of
valinor, 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 933...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Scott Kitterman (supplier of updated valinor 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, 05 Aug 2019 03:53:10 -0400
Source: valinor
Architecture: source
Version: 1.1.0-2
Distribution: unstable
Urgency: medium
Maintainer: Python Applications Packaging Team
Changed-By: Scott Kitterman
Closes: 933923
Changes:
valinor (1.1.0-2) unstable; urgency=medium
.
* Team upload.
.
[ Nick Morrott ]
* d/gbp.conf: use pristine-tar
.
[ Ondřej Nový ]
* Use debhelper-compat instead of debian/compat.
* Bump Standards-Version to 4.4.0.
.
[ Scott Kitterman ]
* Add patch to relax pyyaml version requirements to fix autopkgtest failure
with pyyaml 5.1.2 (Closes: #933923)
- Add d/patches/0005-pyyaml-version-fix.patch
Checksums-Sha1:
512f7ce023096f5af1ce8ff3a764e6282e9637b5 2186 valinor_1.1.0-2.dsc
89ddcc834f2d8827cd647e2d8a2eda6fe7039ad9 6136 valinor_1.1.0-2.debian.tar.xz
06645e1df0fdcdaaaeda231065620682015f6a85 5909 valinor_1.1.0-2_source.buildinfo
Checksums-Sha256:
375db2d94da1e1dafc0e668ee35b0c7fff6b0b52676c1b7eff20b180ebbecca2 2186
valinor_1.1.0-2.dsc
9ffd3181d04df82c53bae033142a296c51489668c42e53bb2688101bbdb2c3ee 6136
valinor_1.1.0-2.debian.tar.xz
052ae5631d3f31e6a59ff7f7cab43792ff7be38ea04039a64d85661dd8fbdd82 5909
valinor_1.1.0-2_source.buildinfo
Files:
9e212e6ed8c0ba01aaab102a47b99ef4 2186 devel optional valinor_1.1.0-2.dsc
a6e96965b5a6fee5f97e9c7f8a9f4850 6136 devel optiona
Bug#933914: marked as done (python3-pytest: pytest v4 breaks existing tests)
Your message dated Mon, 5 Aug 2019 08:37:11 + with message-id and subject line Re: python3-pytest: pytest v4 breaks existing tests has caused the Debian Bug report #933914, regarding python3-pytest: pytest v4 breaks existing tests to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 933914: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933914 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python3-pytest Version: 4.6.4-1 Severity: serious Justification: breaks autopkgtest tests Control: affects -1 + src:apipkg src:betamax src:ccdproc src:chardet Control: affects -1 + src:dask src:django-axes src:doit src:drms Control: affects -1 + src:fiat src:mpi4py src:pandas src:pygalmesh Control: affects -1 + src:pyjwt src:pytest-sugar src:pytest-xdist Control: affects -1 + src:pytest-xvfb src:python-dbfread Control: affects -1 + src:python-dugong src:python-graphviz Control: affects -1 + src:python-hypothesis src:python-parameterized Control: affects -1 + src:python-transliterate src:setuptools-scm Control: affects -1 + src:spyder-line-profiler src:spyder-reports Control: affects -1 + src:spyder-unittest src:sudsy python3-pytest v4 has changed the pytest API, causing many existing tests to fail. This upgrade should be treated as a Transition, uploading the package to experimental first. -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-5-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), LANGUAGE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages python3-pytest depends on: ii python3 3.7.3-1 ii python3-atomicwrites1.1.5-2 ii python3-attr18.2.0-1 ii python3-importlib-metadata 0.18-2 ii python3-more-itertools 4.2.0-1 ii python3-packaging 19.0-1 ii python3-pkg-resources 41.0.1-1 ii python3-pluggy 0.12.0-1 ii python3-py 1.8.0-1 ii python3-six 1.12.0-1 ii python3-wcwidth 0.1.7+dfsg1-6 python3-pytest recommends no packages. python3-pytest suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Tags: wontfix Hi Drew, On Mon, 05 Aug 2019 11:43:39 +0800 Drew Parsons wrote:> This upgrade should be treated as a Transition, uploading the package to> experimental first. We are not using Transitions for Python upgrades because almost every module upgrade breaks something. It's too much overhead for us. Last time I uploaded pytest to experimental first and send information to ML, nothing happened [1]. Because we have autopkgtest migration test, this package will not migrate to testing until compatibility issues are fixed. So there is not breakage of testing. Because this is build-depends related and we don't have "build-depends- break" there is nothing I can do in pytest package itself. Please create individual FTBFS bugs for affected packages and maybe tag them with something like "pytest4". Thank you. [1] https://lists.debian.org/debian-python/2018/11/msg00016.html -- Best regards Ondřej Nový signature.asc Description: This is a digitally signed message part --- End Message ---
Bug#933868: marked as done (grunt should look for tasks in /usr/share/nodejs as well)
Your message dated Mon, 05 Aug 2019 09:08:50 + with message-id and subject line Bug#933868: fixed in grunt 1.0.1-9 has caused the Debian Bug report #933868, regarding grunt should look for tasks in /usr/share/nodejs as well 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.) -- 933868: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933868 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: grunt version: 1.0.1-8 severity: grave node-grunt-webpack and others now install in /usr/share/nodejs and this patch -> https://salsa.debian.org/js-team/grunt/blob/master/debian/patches/add-root-variable.patch should be updated to handle the new path. --- End Message --- --- Begin Message --- Source: grunt Source-Version: 1.0.1-9 We believe that the bug you reported is fixed in the latest version of grunt, 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 933...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Pirate Praveen (supplier of updated grunt package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 05 Aug 2019 08:39:22 + Source: grunt Architecture: source Version: 1.0.1-9 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Pirate Praveen Closes: 933868 Changes: grunt (1.0.1-9) unstable; urgency=medium . [ Marcelo Jorge Vieira ] * Update Vcs-* fields: Maintenance moved to Salsa . [ Pirate Praveen ] * Resolve in /usr/share/nodejs (Closes: #933868) * Bump Standards-Version to 4.4.0 (no changes needed) * Bump debhelper compat to 12 Checksums-Sha1: 6da7b57fe5495ba7a381e4a46684a6ba61aebf54 2610 grunt_1.0.1-9.dsc 79a88e22fe3a2f5b132c91a57258c34ca82a 4448 grunt_1.0.1-9.debian.tar.xz ee682a4ba9388f28a618da099dcbe7efde68b1dc 10678 grunt_1.0.1-9_amd64.buildinfo Checksums-Sha256: 330718cfbe5eb53c2e755a7e24e7069adc308aae759929928560ef9055e5d02b 2610 grunt_1.0.1-9.dsc f7a86a90bab90be070216ba8277d0cb53ce5dbcd5b6285995c3e281c684ca3e4 4448 grunt_1.0.1-9.debian.tar.xz 1e615749feb0acba7073b02ec2a1523d2a8a8077b820062a1b5c2c419835ff6e 10678 grunt_1.0.1-9_amd64.buildinfo Files: 75848ba4f7a0841c267f96b69a712a7b 2610 javascript optional grunt_1.0.1-9.dsc fcb80054316fe22984aefecf4dd0b6f6 4448 javascript optional grunt_1.0.1-9.debian.tar.xz dbc38a5a4e851aa3db25f280e34525ca 10678 javascript optional grunt_1.0.1-9_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEE/OFtr184QaN6dPMgC3aSB2Kmt4UFAl1H7W0ACgkQC3aSB2Km t4U7tBAAvMn11QpU9AGr6pqFVrhzjeZzmNgf81qumvheNkhUCKL2EL4dX0sxlujE o8+1ChkvdQpJvXwVwsrhhe4WBYx5USuYJOXBpZGUh5BJ9H64H2u8Tp+bjlJ44IHA V1ojFJtsZnQXxo8ZfL3W3PcrMHtcYXwtgaWblqoYYNOGdW+fM3W00zUlXXVbO5PT u2w7tQRiK1Zu/rgWrwcbYF0UJMRn3iUF68cuSg2jQSFMrX7GErb+DFBogN8s1kVY 5Fx1Upmdn9wZwm9K040iq4Zl3tZrTNf142OtPYQnObOukaOCA/0rDYXDnN67Jl77 z849aaznUUqBVDqOMyqAqtX4rbjWXDs4VyRIVy8nliFxj7LpCDE9twKHE4V/9M/A 1srrLJCwfKBN+Bh5xIcN/XCXPw/elpEiQfuimeT1PlHA0p+GA10iGBH8iwuOa0SZ nWnrIWqBQLwGqMKfpCMaw892uOSvC2KIARdHJiEQVdt7Oge5iT6kuBHHTLHRpF+p EVpiiKJHVjCS5j/0bbHQwc8xxhsVjUlyoTgabxLauO06DiXjAYlFNo6OcKL8jj07 aD4F3pRAa4vmCQ4sTAhrNYla8SoPemITWG+ahRYVjvdQEPjGYPpNrr0FXNfqNDG4 K58nOPQow3wIBIeE40FkH12cOtNFdYyaPQ77dfiGzJWvf+cEZGU= =PBYp -END PGP SIGNATURE End Message ---
Bug#924311: marked as done (miredo: Fails to stop with sysvinit: start-stop-daemon: matching only on non-root pidfile /var/run/miredo.pid is insecure)
Your message dated Mon, 05 Aug 2019 09:09:12 + with message-id and subject line Bug#924311: fixed in miredo 1.2.6-7.1 has caused the Debian Bug report #924311, regarding miredo: Fails to stop with sysvinit: start-stop-daemon: matching only on non-root pidfile /var/run/miredo.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.) -- 924311: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924311 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: miredo Version: 1.2.6-7 Severity: serious Hi, stopping or restarting miredo on systems with sysvinit (or probably also any other init system using start-stop-daemon) fails as follows for me: invoke-rc.d miredo restart [] Stopping Teredo IPv6 tunneling daemon: miredostart-stop-daemon: matching only on non-root pidfile /var/run/miredo.pid is insecure failed! And miredo is indeed not stopped: root 1225 0.0 0.0 12100 0 ?Ss Jan13 0:00 /usr/sbin/miredo miredo1226 0.0 0.0 110556 0 ?Sl Jan13 0:33 /usr/sbin/miredo root 1228 0.0 0.0 6904 316 ?SJan13 0:00 /usr/libexec/miredo/miredo-privproc B This is caused by the following change in dpkg 1.19.3 from 22 Jan 2019: * start-stop-daemon: Check whether standalone --pidfile use is secure. Prompted by Michael Orlitzky . The usual fix seems to be to also specify the binary to be stopped with IIRC the --exec option. -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (990, 'unstable'), (600, 'testing'), (500, 'unstable-debug'), (500, 'buildd-unstable'), (110, 'experimental'), (1, 'experimental-debug'), (1, 'buildd-experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.18.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) LSM: AppArmor: enabled Versions of packages miredo depends on: ii adduser 3.118 ii init-system-helpers 1.56+nmu1 ii iproute2 4.20.0-2 ii libc62.28-8 ii libcap2 1:2.25-2 ii libjudydebian1 1.0.5-5 ii lsb-base 10.2018112800 ii makedev 2.3.1-94 ii udev 241-1 miredo recommends no packages. miredo suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: miredo Source-Version: 1.2.6-7.1 We believe that the bug you reported is fixed in the latest version of miredo, 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 924...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Stéphane Glondu (supplier of updated miredo package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 26 Jul 2019 09:57:06 +0200 Source: miredo Architecture: source Version: 1.2.6-7.1 Distribution: unstable Urgency: medium Maintainer: Tomasz Buchert Changed-By: Stéphane Glondu Closes: 924311 Changes: miredo (1.2.6-7.1) unstable; urgency=medium . * Non-maintainer upload * Always call start-stop-daemon --stop with --exec (Closes: #924311) Checksums-Sha1: abe4457f1bfc449165a51977281b31ba5e69fa8b 1714 miredo_1.2.6-7.1.dsc a60fde484e7a3bdd3dafd03d1869dab7921d 9468 miredo_1.2.6-7.1.debian.tar.xz Checksums-Sha256: a3efc82b385427b30dfe7087b503768679b920f31d10dfc2955f7c7aa0459e58 1714 miredo_1.2.6-7.1.dsc ae2075bb622b4ff964085683a638d5d519b77b3ed04830ac3e8a72900438ca6a 9468 miredo_1.2.6-7.1.debian.tar.xz Files: 237689eb6aabd3d3c63411791300827c 1714 net optional miredo_1.2.6-7.1.dsc 30b7035c6e5d3a787ab92219b25f9b9f 9468 net optional miredo_1.2.6-7.1.debian.tar.xz -BEGIN PGP SIGNATURE- iQEzBAEBCgAdFiEEbeJOl+yohsxW5iUOIbju8bGJMIEFAl06tXcACgkQIbju8bGJ MIFvMgf+KrqcIMTwVyE6XULXBhF5M5UyL+Ib+LHkGCsnw5Vy0heenRGl7ZD3Nzp2 imDUnv3i/zmJ4E1enM/lIWKxdn0rOMptj2bqZDcgd2p8p+S4OrLGgJHapAE0IvpH o+FtJKZP5Q4iQ6hj3HC1BeuczF64cQAtMIHOwKPFL48J58rGrbBSg7ydxjRFdVY4 Sez1TCMJAGpysx4BnkY/eHquY8hxoARbJu6hg+Vp7yTaSSdfU+VfYHAYd3P4NtK1 tRgMlilUUxGukVrd+fPF4qLbvixilO4Lv9ukZjreg8QWoiZt5WsnQ0Gil67
Bug#933930: network-manager: Ethernet connection no longer works
Package: network-manager Version: 1.19.90-2 Severity: grave Justification: renders package unusable After upgrading to 1.19.90-2 and rebooting my machine, I completely lost Ethernet connection. cventin:~> journalctl -b -2 -g network -- Logs begin at Tue 2016-04-19 07:35:01 CEST, end at Mon 2019-08-05 11:12:14 CEST. -- Aug 05 10:52:53 cventin kernel: e1000e: Intel(R) PRO/1000 Network Driver - 3.2.6-k Aug 05 10:52:53 cventin kernel: e1000e :00:19.0 eth0: Intel(R) PRO/1000 Network Connection Aug 05 10:52:53 cventin ifup[485]: /bin/run-parts --exit-on-error --verbose /etc/network/if-pre-up.d Aug 05 10:52:53 cventin ifup[485]: run-parts: executing /etc/network/if-pre-up.d/ethtool Aug 05 10:52:53 cventin ifup[485]: run-parts: executing /etc/network/if-pre-up.d/wpasupplicant Aug 05 10:52:53 cventin ifup[485]: /bin/run-parts --exit-on-error --verbose /etc/network/if-pre-up.d Aug 05 10:52:53 cventin ifup[485]: run-parts: executing /etc/network/if-pre-up.d/ethtool Aug 05 10:52:53 cventin ifup[485]: run-parts: executing /etc/network/if-pre-up.d/wpasupplicant Aug 05 10:52:53 cventin ifup[485]: /bin/run-parts --exit-on-error --verbose /etc/network/if-up.d Aug 05 10:52:53 cventin ifup[485]: run-parts: executing /etc/network/if-up.d/avahi-daemon Aug 05 10:52:53 cventin ifup[485]: run-parts: executing /etc/network/if-up.d/ethtool Aug 05 10:52:53 cventin ifup[485]: run-parts: executing /etc/network/if-up.d/mountnfs Aug 05 10:52:53 cventin ifup[485]: run-parts: executing /etc/network/if-up.d/wpasupplicant Aug 05 10:52:53 cventin ifup[485]: /bin/run-parts --exit-on-error --verbose /etc/network/if-up.d Aug 05 10:52:53 cventin ifup[485]: run-parts: executing /etc/network/if-up.d/avahi-daemon Aug 05 10:52:53 cventin ifup[485]: run-parts: executing /etc/network/if-up.d/ethtool Aug 05 10:52:53 cventin ifup[485]: run-parts: executing /etc/network/if-up.d/mountnfs Aug 05 10:52:53 cventin ifup[485]: run-parts: executing /etc/network/if-up.d/wpasupplicant Aug 05 10:52:54 cventin systemd[1]: Starting Network Time Synchronization... Aug 05 10:52:55 cventin systemd[1]: Started Network Time Synchronization. Aug 05 10:52:55 cventin systemd[1]: Starting Network Manager... Aug 05 10:52:55 cventin NetworkManager[789]: [1564995175.9222] NetworkManager (version 1.19.90) is starting... (for the first time) Aug 05 10:52:55 cventin NetworkManager[789]: [1564995175.9223] Read config: /etc/NetworkManager/NetworkManager.conf (lib: no-mac-addr-change.conf) Aug 05 10:52:55 cventin NetworkManager[789]: [1564995175.9223] config: unknown key 'wifi.cloned-mac-address' in section [device-mac-addr-change-wifi] of file '/usr/lib/NetworkManager/conf.d/no-mac-addr-change.conf' Aug 05 10:52:55 cventin NetworkManager[789]: [1564995175.9223] config: unknown key 'ethernet.cloned-mac-address' in section [device-mac-addr-change-wifi] of file '/usr/lib/NetworkManager/conf.d/no-mac-addr-change.conf' Aug 05 10:52:55 cventin NetworkManager[789]: [1564995175.9251] bus-manager: acquired D-Bus service "org.freedesktop.NetworkManager" Aug 05 10:52:55 cventin NetworkManager[789]: [1564995175.9316] monitoring ifupdown state file '/run/network/ifstate'. Aug 05 10:52:55 cventin dbus-daemon[788]: [system] Activating systemd to hand-off: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.5' (uid=0 pid=789 comm="/usr/sbin/NetworkManager --no-daemon ") Aug 05 10:52:56 cventin avahi-daemon[780]: Network interface enumeration completed. Aug 05 10:52:56 cventin systemd[1]: Started Network Manager. Aug 05 10:52:56 cventin systemd[1]: Starting Network Manager Wait Online... Aug 05 10:52:56 cventin systemd[1]: Reached target Network. Aug 05 10:52:57 cventin NetworkManager[789]: [1564995177.3253] Loaded device plugin: NMWifiFactory (/usr/lib/x86_64-linux-gnu/NetworkManager/1.19.90/libnm-device-plugin-wifi.so) Aug 05 10:52:57 cventin NetworkManager[789]: [1564995177.3309] Loaded device plugin: NMBluezManager (/usr/lib/x86_64-linux-gnu/NetworkManager/1.19.90/libnm-device-plugin-bluetooth.so) Aug 05 10:52:57 cventin NetworkManager[789]: [1564995177.3316] Loaded device plugin: NMWwanFactory (/usr/lib/x86_64-linux-gnu/NetworkManager/1.19.90/libnm-device-plugin-wwan.so) Aug 05 10:52:57 cventin NetworkManager[789]: [1564995177.3348] Loaded device plugin: NMTeamFactory (/usr/lib/x86_64-linux-gnu/NetworkManager/1.19.90/libnm-device-plugin-team.so) Aug 05 10:52:57 cventin NetworkManager[789]: [1564995177.3358] Loaded device plugin: NMAtmManager (/usr/lib/x86_64-linux-gnu/NetworkManager/1.19.90/libnm-device-plugin-adsl.so) Aug 05 10:52:57 cventin NetworkManager[789]: [1564995177.3363] manager: Networking is enabled by state file Aug 05 10:52:57 cventin dbus-daemon[788]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.5' (uid=0 pid=789 comm="/usr/sbin/NetworkManager --no-daemon
Bug#933930: network-manager: Ethernet connection no longer works
Oops, bad copy-paste for the working old version.
The correct one...
On 2019-08-05 11:20:24 +0200, Vincent Lefevre wrote:
> Downgrading to 1.14.6-2 solved the issue. As a comparison with this working
> version:
cventin:~> journalctl -b -g network
-- Logs begin at Tue 2016-04-19 07:35:01 CEST, end at Mon 2019-08-05 11:30:01
CEST. --
Aug 05 11:09:46 cventin kernel: e1000e: Intel(R) PRO/1000 Network Driver -
3.2.6-k
Aug 05 11:09:46 cventin kernel: e1000e :00:19.0 eth0: Intel(R) PRO/1000
Network Connection
Aug 05 11:09:46 cventin ifup[544]: /bin/run-parts --exit-on-error --verbose
/etc/network/if-pre-up.d
Aug 05 11:09:46 cventin ifup[544]: run-parts: executing
/etc/network/if-pre-up.d/ethtool
Aug 05 11:09:46 cventin ifup[544]: run-parts: executing
/etc/network/if-pre-up.d/wpasupplicant
Aug 05 11:09:46 cventin ifup[544]: /bin/run-parts --exit-on-error --verbose
/etc/network/if-pre-up.d
Aug 05 11:09:46 cventin ifup[544]: run-parts: executing
/etc/network/if-pre-up.d/ethtool
Aug 05 11:09:46 cventin ifup[544]: run-parts: executing
/etc/network/if-pre-up.d/wpasupplicant
Aug 05 11:09:46 cventin ifup[544]: /bin/run-parts --exit-on-error --verbose
/etc/network/if-up.d
Aug 05 11:09:46 cventin ifup[544]: run-parts: executing
/etc/network/if-up.d/avahi-daemon
Aug 05 11:09:46 cventin ifup[544]: run-parts: executing
/etc/network/if-up.d/ethtool
Aug 05 11:09:46 cventin ifup[544]: run-parts: executing
/etc/network/if-up.d/mountnfs
Aug 05 11:09:46 cventin ifup[544]: run-parts: executing
/etc/network/if-up.d/wpasupplicant
Aug 05 11:09:46 cventin ifup[544]: /bin/run-parts --exit-on-error --verbose
/etc/network/if-up.d
Aug 05 11:09:46 cventin ifup[544]: run-parts: executing
/etc/network/if-up.d/avahi-daemon
Aug 05 11:09:46 cventin ifup[544]: run-parts: executing
/etc/network/if-up.d/ethtool
Aug 05 11:09:46 cventin ifup[544]: run-parts: executing
/etc/network/if-up.d/mountnfs
Aug 05 11:09:46 cventin ifup[544]: run-parts: executing
/etc/network/if-up.d/wpasupplicant
Aug 05 11:09:47 cventin systemd[1]: Starting Network Time Synchronization...
Aug 05 11:09:48 cventin systemd[1]: Started Network Time Synchronization.
Aug 05 11:09:48 cventin systemd[1]: Starting Network Manager...
Aug 05 11:09:48 cventin NetworkManager[809]: [1564996188.9412]
NetworkManager (version 1.14.6) is starting... (for the first time)
Aug 05 11:09:48 cventin NetworkManager[809]: [1564996188.9413] Read
config: /etc/NetworkManager/NetworkManager.conf (lib: no-mac-addr-change.conf)
Aug 05 11:09:48 cventin NetworkManager[809]: [1564996188.9472]
bus-manager: acquired D-Bus service "org.freedesktop.NetworkManager"
Aug 05 11:09:48 cventin NetworkManager[809]: [1564996188.9487]
monitoring ifupdown state file '/run/network/ifstate'.
Aug 05 11:09:48 cventin dbus-daemon[787]: [system] Activating systemd to
hand-off: service name='org.freedesktop.hostname1'
unit='dbus-org.freedesktop.hostname1.service' requested by ':1.3' (uid=0
pid=809 comm="/usr/sbin/NetworkManager --no-daemon ")
Aug 05 11:09:49 cventin avahi-daemon[834]: Network interface enumeration
completed.
Aug 05 11:09:50 cventin systemd[1]: Started Network Manager.
Aug 05 11:09:50 cventin systemd[1]: Reached target Network.
Aug 05 11:09:50 cventin systemd[1]: Starting Network Manager Wait Online...
Aug 05 11:09:50 cventin dbus-daemon[787]: [system] Activating via systemd:
service name='org.freedesktop.nm_dispatcher'
unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.3' (uid=0
pid=809 comm="/usr/sbin/NetworkManager --no-daemon ")
Aug 05 11:09:50 cventin systemd[1]: Starting Network Manager Script Dispatcher
Service...
Aug 05 11:09:50 cventin NetworkManager[809]: [1564996190.6900]
ifupdown: interface-parser: parsing file /etc/network/interfaces
Aug 05 11:09:50 cventin NetworkManager[809]: [1564996190.6900]
ifupdown: interface-parser: source line includes interfaces file(s)
/etc/network/interfaces.d/*
Aug 05 11:09:50 cventin NetworkManager[809]: [1564996190.6900]
ifupdown: interfaces file /etc/network/interfaces.d/* doesn't exist
Aug 05 11:09:50 cventin NetworkManager[809]: [1564996190.6901]
ifupdown: interface-parser: finished parsing file /etc/network/interfaces
Aug 05 11:09:50 cventin NetworkManager[809]: [1564996190.6901]
settings: Loaded settings plugin: SettingsPluginIfupdown
("/usr/lib/x86_64-linux-gnu/NetworkManager/1.14.6/libnm-settings-plugin-ifupdown.so")
Aug 05 11:09:50 cventin NetworkManager[809]: [1564996190.6933] keyfile:
new connection /etc/NetworkManager/system-connections/Wired connection 1
(c89d3bc3-8d9e-44f8-ac86-7e6884d08219,"Wired connection 1")
Aug 05 11:09:50 cventin NetworkManager[809]: [1564996190.6999] manager:
Networking is enabled by state file
Aug 05 11:09:50 cventin systemd[1]: Started Network Manager Script Dispatcher
Service.
Aug 05 11:09:50 cventin NetworkManager[809]: [1564996190.7078] Loaded
device plugin: NMWifiFactory
(/usr/lib/x86_64-linux-gnu/NetworkManager/1.14.6/libnm
Bug#933932: strongwind: State of the package, remove?
Source: strongwind Version: 0.9-2 Severity: serious Justification: unmaintained Hello, The state of the strongwind package is questionable. It has not been updated since feb 2012, and upstream does not exist any more. It is still using python2 syntax, and depends on python-pyatspi which is to be removed. strongwind happened to be removed from testing in 2018 due to some pyatspi2 dependency (see #896341), but that was fixed. I'm however questioning whether we should keep the package at all given its abandon state? Samuel -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'stable-debug'), (500, 'proposed-updates-debug'), (500, 'proposed-updates'), (500, 'oldstable-proposed-updates-debug'), (500, 'oldstable-proposed-updates'), (500, 'oldoldstable'), (500, 'buildd-unstable'), (500, 'unstable'), (500, 'stable'), (500, 'oldstable'), (1, 'experimental-debug'), (1, 'buildd-experimental'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.2.0 (SMP w/8 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
Bug#933921: src:python-tablib: Unsafe use of yaml.load()
On 8/5/19 7:35 AM, Scott Kitterman wrote: > Package: src:python-tablib > Version: 0.12.1-2 > Severity: grave > Tags: security > Justification: user security hole > > The new version of pyyaml no longer allows use of yaml.load() without a > loader being specifed. This raises a deprecation warning which has > caused and autopkgtest failure on this package. These are generally > trivial to fix, see the upstream guidance [1]. > > Scott K > > [1] https://github.com/yaml/pyyaml/wiki/PyYAML-yaml.load(input)-Deprecation > > Hi, FYI, I have just filed a removal bug for this one, as it's not used by any OpenStack things anymore. Cheers, Thomas Goirand (zigo)
Bug#933821: python-tuskarclient (build-)depends on cruft package.
On 8/4/19 1:07 AM, Peter Michael Green wrote: > Package: python-tuskarclient > Severity: serious > Version: 0.1.18-1 > Tags: bullseye, sid > > python-tuskarclient depends on the python-cliff, python-keystoneclient, > python-openstackclient and python-stevedore binary packages which are no > longer built by the corresponding source packages. > > If this is going to stay around it looks like it needs to migrate to > python 3. Hi, I've filled an RM bug for this package, so it will go away... The Tuskar project has been retired a long time ago, so this is overdue. Thomas Goirand (zigo)
Bug#933937: biobambam2: /usr/bin/fastaexplode is already provided by exonerate
Package: biobambam2 Version: 2.0.95-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 biobambam2. Preparing to unpack .../biobambam2_2.0.95-1_amd64.deb ... Unpacking biobambam2 (2.0.95-1) ... dpkg: error processing archive /var/cache/apt/archives/biobambam2_2.0.95-1_amd64.deb (--unpack): trying to overwrite '/usr/bin/fastaexplode', which is also in package exonerate 2.4.0-4 Errors were encountered while processing: /var/cache/apt/archives/biobambam2_2.0.95-1_amd64.deb cheers, Andreas exonerate=2.4.0-4_biobambam2=2.0.95-1.log.gz Description: application/gzip
Bug#933746: marked as done (tika: CVE-2019-10094: tackOverflow from Crafted Package/Compressed Files in Apache Tika's RecursiveParserWrapper)
Your message dated Mon, 05 Aug 2019 10:09:53 + with message-id and subject line Bug#933746: fixed in tika 1.22-1 has caused the Debian Bug report #933746, regarding tika: CVE-2019-10094: tackOverflow from Crafted Package/Compressed Files in Apache Tika's RecursiveParserWrapper 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.) -- 933746: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933746 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: tika Version: 1.20-1 Severity: grave Tags: security upstream Control: found -1 1.21-1 Hi, The following vulnerability was published for tika. CVE-2019-10094[0]: | A carefully crafted package/compressed file that, when | unzipped/uncompressed yields the same file (a quine), causes a | StackOverflowError in Apache Tika's RecursiveParserWrapper in versions | 1.7-1.21. Apache Tika users should upgrade to 1.22 or later. 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-10094 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-10094 [1] https://www.openwall.com/lists/oss-security/2019/08/02/4 Regards, Salvatore --- End Message --- --- Begin Message --- Source: tika Source-Version: 1.22-1 We believe that the bug you reported is fixed in the latest version of tika, 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 933...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Emmanuel Bourg (supplier of updated tika package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 05 Aug 2019 11:41:25 +0200 Source: tika Architecture: source Version: 1.22-1 Distribution: unstable Urgency: medium Maintainer: Debian Java Maintainers Changed-By: Emmanuel Bourg Closes: 933744 933745 933746 Changes: tika (1.22-1) unstable; urgency=medium . * New upstream release - Fixes CVE-2019-10088: A carefully crafted or corrupt zip file can cause an out of memory error in RecursiveParserWrapper (Closes: #933744) - Fixes CVE-2019-10094: A carefully crafted package/compressed file that, when unzipped/uncompressed yields the same file (a quine), causes a stack overflow error in RecursiveParserWrapper (Closes: #933746) - Fixes CVE-2019-10093: A carefully crafted 2003ml or 2006ml file could consume all available SAXParsers in the pool and lead to very long hangs. (Closes: #933745) - Refreshed the patches - Ignore the new dependency on c3p0 (not used) Checksums-Sha1: 69ec0990d617453dfe50b66c1fad682e3f11326c 2754 tika_1.22-1.dsc 88c6cc8d3b91c77a12f7eb421acc94cf65ee4fd4 2532 tika_1.22.orig.tar.xz e29a2e8fea3fd6b4554404d1ea742bee78b0 7640 tika_1.22-1.debian.tar.xz 454be34f89e6dfaccb2cc0f5f8d91da6a6c7b355 13207 tika_1.22-1_source.buildinfo Checksums-Sha256: ade5061dae979d66afa77b99e498c29ba6cec0e902f3700f6c87430e52030453 2754 tika_1.22-1.dsc 0407432e3581a65530fd8bff13f2848894b03b28fd46dc0dd7b16daa60b0f559 2532 tika_1.22.orig.tar.xz b4820f6b2d679f81256d584b96e26487e804b9448b0030808d4a87973d53b41f 7640 tika_1.22-1.debian.tar.xz 857a247817eb93f5d160a51df9b1aea56ef331633d7230b42312281e167ad6fd 13207 tika_1.22-1_source.buildinfo Files: 9a53af116bd589963b241af204cb2db2 2754 java optional tika_1.22-1.dsc ac1619d5a5612b5c2f2fb878225354ce 2532 java optional tika_1.22.orig.tar.xz e738ec8a00850fd72c579dfbbf15daee 7640 java optional tika_1.22-1.debian.tar.xz 0255bed2399db3962e55bcadaab90b20 13207 java optional tika_1.22-1_source.buildinfo -BEGIN PGP SIGNATURE- iQJGBAEBCgAwFiEEuM5N4hCA3PkD4WxA9RPEGeS50KwFAl1H+ssSHGVib3VyZ0Bh cGFjaGUub3JnAAoJEPUTxBnkudCsE+EQALAtKL/wuLNvZUK82WgK54pVUbdR7Igm l2t9iv8JSbIWh3tqaOpQfORHzDNpOsy8sDmnaUaKB2pRl/GFLgvyWLoglc/nyLN+ Uq4PriQP2WfynEjyN5cDTe0BPX+YMO20Sd85ki/6cgF31i3KdAeH7wKob4Jc60/p QRahBbDNVum8KB16+DQTv0Lzrx0tMpCcwRWSMGhPv0BFpOzDF5HdtWg33YG+1ysW z8ev1eBunIuglxpPfX5muCluBv6V9skrNTTHypD+eumsOSwE2AI+VGNtfGcOioIh 1q0BD8kBK0iG+VSiy91QaH83ADt4cIHfeKnC+svrHA9aZM5cf4X2qtKILuCDuuQv YXsHm/VX/YgNFkZ1j
Bug#933744: marked as done (tika: CVE-2019-10088: OOM from a crafted Zip File in Apache Tika's RecursiveParserWrapper)
Your message dated Mon, 05 Aug 2019 10:09:53 + with message-id and subject line Bug#933744: fixed in tika 1.22-1 has caused the Debian Bug report #933744, regarding tika: CVE-2019-10088: OOM from a crafted Zip File in Apache Tika's RecursiveParserWrapper 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.) -- 933744: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933744 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: tika Version: 1.21-1 Severity: grave Tags: security upstream Control: found -1 1.20-1 Hi, The following vulnerability was published for tika. CVE-2019-10088[0]: | A carefully crafted or corrupt zip file can cause an OOM in Apache | Tika's RecursiveParserWrapper in versions 1.7-1.21. Users should | upgrade to 1.22 or later. 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-10088 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-10088 [1] https://www.openwall.com/lists/oss-security/2019/08/02/2 Regards, Salvatore --- End Message --- --- Begin Message --- Source: tika Source-Version: 1.22-1 We believe that the bug you reported is fixed in the latest version of tika, 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 933...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Emmanuel Bourg (supplier of updated tika package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 05 Aug 2019 11:41:25 +0200 Source: tika Architecture: source Version: 1.22-1 Distribution: unstable Urgency: medium Maintainer: Debian Java Maintainers Changed-By: Emmanuel Bourg Closes: 933744 933745 933746 Changes: tika (1.22-1) unstable; urgency=medium . * New upstream release - Fixes CVE-2019-10088: A carefully crafted or corrupt zip file can cause an out of memory error in RecursiveParserWrapper (Closes: #933744) - Fixes CVE-2019-10094: A carefully crafted package/compressed file that, when unzipped/uncompressed yields the same file (a quine), causes a stack overflow error in RecursiveParserWrapper (Closes: #933746) - Fixes CVE-2019-10093: A carefully crafted 2003ml or 2006ml file could consume all available SAXParsers in the pool and lead to very long hangs. (Closes: #933745) - Refreshed the patches - Ignore the new dependency on c3p0 (not used) Checksums-Sha1: 69ec0990d617453dfe50b66c1fad682e3f11326c 2754 tika_1.22-1.dsc 88c6cc8d3b91c77a12f7eb421acc94cf65ee4fd4 2532 tika_1.22.orig.tar.xz e29a2e8fea3fd6b4554404d1ea742bee78b0 7640 tika_1.22-1.debian.tar.xz 454be34f89e6dfaccb2cc0f5f8d91da6a6c7b355 13207 tika_1.22-1_source.buildinfo Checksums-Sha256: ade5061dae979d66afa77b99e498c29ba6cec0e902f3700f6c87430e52030453 2754 tika_1.22-1.dsc 0407432e3581a65530fd8bff13f2848894b03b28fd46dc0dd7b16daa60b0f559 2532 tika_1.22.orig.tar.xz b4820f6b2d679f81256d584b96e26487e804b9448b0030808d4a87973d53b41f 7640 tika_1.22-1.debian.tar.xz 857a247817eb93f5d160a51df9b1aea56ef331633d7230b42312281e167ad6fd 13207 tika_1.22-1_source.buildinfo Files: 9a53af116bd589963b241af204cb2db2 2754 java optional tika_1.22-1.dsc ac1619d5a5612b5c2f2fb878225354ce 2532 java optional tika_1.22.orig.tar.xz e738ec8a00850fd72c579dfbbf15daee 7640 java optional tika_1.22-1.debian.tar.xz 0255bed2399db3962e55bcadaab90b20 13207 java optional tika_1.22-1_source.buildinfo -BEGIN PGP SIGNATURE- iQJGBAEBCgAwFiEEuM5N4hCA3PkD4WxA9RPEGeS50KwFAl1H+ssSHGVib3VyZ0Bh cGFjaGUub3JnAAoJEPUTxBnkudCsE+EQALAtKL/wuLNvZUK82WgK54pVUbdR7Igm l2t9iv8JSbIWh3tqaOpQfORHzDNpOsy8sDmnaUaKB2pRl/GFLgvyWLoglc/nyLN+ Uq4PriQP2WfynEjyN5cDTe0BPX+YMO20Sd85ki/6cgF31i3KdAeH7wKob4Jc60/p QRahBbDNVum8KB16+DQTv0Lzrx0tMpCcwRWSMGhPv0BFpOzDF5HdtWg33YG+1ysW z8ev1eBunIuglxpPfX5muCluBv6V9skrNTTHypD+eumsOSwE2AI+VGNtfGcOioIh 1q0BD8kBK0iG+VSiy91QaH83ADt4cIHfeKnC+svrHA9aZM5cf4X2qtKILuCDuuQv YXsHm/VX/YgNFkZ1jJER4gmiNkcMMI5ufUAAAIxeuhiovtywLC2QdqplwHB6HpuK IQt2N/1jVXoPvZWcivuYyx3QW1fVi69ItlXqq1RxwjPFh3MVCiL7xNDFBnQyGdLH bpw5
Bug#933930: network-manager: Ethernet connection no longer works
On 2019-08-05 11:32:59 +0200, Vincent Lefevre wrote:
> On 2019-08-05 11:20:24 +0200, Vincent Lefevre wrote:
> > Downgrading to 1.14.6-2 solved the issue. As a comparison with this working
> > version:
1.18.0-3 is also working.
cventin:~> journalctl -b -g network
-- Logs begin at Tue 2016-04-19 07:35:01 CEST, end at Mon 2019-08-05 12:21:38
CEST. --
Aug 05 12:05:44 cventin kernel: e1000e: Intel(R) PRO/1000 Network Driver -
3.2.6-k
Aug 05 12:05:44 cventin kernel: e1000e :00:19.0 eth0: Intel(R) PRO/1000
Network Connection
Aug 05 12:05:44 cventin ifup[456]: /bin/run-parts --exit-on-error --verbose
/etc/network/if-pre-up.d
Aug 05 12:05:44 cventin ifup[456]: run-parts: executing
/etc/network/if-pre-up.d/ethtool
Aug 05 12:05:44 cventin ifup[456]: run-parts: executing
/etc/network/if-pre-up.d/wpasupplicant
Aug 05 12:05:44 cventin ifup[456]: /bin/run-parts --exit-on-error --verbose
/etc/network/if-pre-up.d
Aug 05 12:05:44 cventin ifup[456]: run-parts: executing
/etc/network/if-pre-up.d/ethtool
Aug 05 12:05:44 cventin ifup[456]: run-parts: executing
/etc/network/if-pre-up.d/wpasupplicant
Aug 05 12:05:44 cventin ifup[456]: /bin/run-parts --exit-on-error --verbose
/etc/network/if-up.d
Aug 05 12:05:44 cventin ifup[456]: run-parts: executing
/etc/network/if-up.d/avahi-daemon
Aug 05 12:05:44 cventin ifup[456]: run-parts: executing
/etc/network/if-up.d/ethtool
Aug 05 12:05:44 cventin ifup[456]: run-parts: executing
/etc/network/if-up.d/mountnfs
Aug 05 12:05:44 cventin ifup[456]: run-parts: executing
/etc/network/if-up.d/wpasupplicant
Aug 05 12:05:44 cventin ifup[456]: /bin/run-parts --exit-on-error --verbose
/etc/network/if-up.d
Aug 05 12:05:44 cventin ifup[456]: run-parts: executing
/etc/network/if-up.d/avahi-daemon
Aug 05 12:05:44 cventin ifup[456]: run-parts: executing
/etc/network/if-up.d/ethtool
Aug 05 12:05:44 cventin ifup[456]: run-parts: executing
/etc/network/if-up.d/mountnfs
Aug 05 12:05:44 cventin ifup[456]: run-parts: executing
/etc/network/if-up.d/wpasupplicant
Aug 05 12:05:45 cventin systemd[1]: Starting Network Time Synchronization...
Aug 05 12:05:46 cventin systemd[1]: Started Network Time Synchronization.
Aug 05 12:05:46 cventin systemd[1]: Starting Network Manager...
Aug 05 12:05:46 cventin NetworkManager[758]: [1564999546.7164]
NetworkManager (version 1.18.0) is starting... (for the first time)
Aug 05 12:05:46 cventin NetworkManager[758]: [1564999546.7166] Read
config: /etc/NetworkManager/NetworkManager.conf (lib: no-mac-addr-change.conf)
Aug 05 12:05:46 cventin NetworkManager[758]: [1564999546.7166] config:
unknown key 'wifi.cloned-mac-address' in section [device-mac-addr-change-wifi]
of file '/usr/lib/NetworkManager/conf.d/no-mac-addr-change.conf'
Aug 05 12:05:46 cventin NetworkManager[758]: [1564999546.7166] config:
unknown key 'ethernet.cloned-mac-address' in section
[device-mac-addr-change-wifi] of file
'/usr/lib/NetworkManager/conf.d/no-mac-addr-change.conf'
Aug 05 12:05:46 cventin NetworkManager[758]: [1564999546.7221]
bus-manager: acquired D-Bus service "org.freedesktop.NetworkManager"
Aug 05 12:05:46 cventin NetworkManager[758]: [1564999546.7239]
monitoring ifupdown state file '/run/network/ifstate'.
Aug 05 12:05:46 cventin dbus-daemon[753]: [system] Activating systemd to
hand-off: service name='org.freedesktop.hostname1'
unit='dbus-org.freedesktop.hostname1.service' requested by ':1.4' (uid=0
pid=758 comm="/usr/sbin/NetworkManager --no-daemon ")
Aug 05 12:05:47 cventin avahi-daemon[787]: Network interface enumeration
completed.
Aug 05 12:05:47 cventin systemd[1]: Started Network Manager.
Aug 05 12:05:47 cventin systemd[1]: Starting Network Manager Wait Online...
Aug 05 12:05:47 cventin systemd[1]: Reached target Network.
Aug 05 12:05:48 cventin dbus-daemon[753]: [system] Activating via systemd:
service name='org.freedesktop.nm_dispatcher'
unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.4' (uid=0
pid=758 comm="/usr/sbin/NetworkManager --no-daemon ")
Aug 05 12:05:48 cventin systemd[1]: Starting Network Manager Script Dispatcher
Service...
Aug 05 12:05:48 cventin systemd[1]: Started Network Manager Script Dispatcher
Service.
Aug 05 12:05:48 cventin NetworkManager[758]: [1564999548.2743]
ifupdown: interface-parser: parsing file /etc/network/interfaces
Aug 05 12:05:48 cventin NetworkManager[758]: [1564999548.2744]
ifupdown: interface-parser: source line includes interfaces file(s)
/etc/network/interfaces.d/*
Aug 05 12:05:48 cventin NetworkManager[758]: [1564999548.2744]
ifupdown: interfaces file /etc/network/interfaces.d/* doesn't exist
Aug 05 12:05:48 cventin NetworkManager[758]: [1564999548.2745]
ifupdown: interface-parser: finished parsing file /etc/network/interfaces
Aug 05 12:05:48 cventin NetworkManager[758]: [1564999548.2745]
settings: Loaded settings plugin: SettingsPluginIfupdown
("/usr/lib/x86_64-linux-gnu/NetworkManager/1.18.0/libnm-settings-plugin-ifupdown.so")
Aug 05 12:05:48 cv
Bug#933002: marked as done (docker.io: CVE-2019-13139)
Your message dated Mon, 05 Aug 2019 10:50:10 + with message-id and subject line Bug#933002: fixed in docker.io 18.09.1+dfsg1-8 has caused the Debian Bug report #933002, regarding docker.io: CVE-2019-13139 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.) -- 933002: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933002 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: docker.io Version: 18.09.1+dfsg1-7.1 Severity: grave Tags: security upstream Forwarded: https://github.com/moby/moby/pull/38944 Control: fixed -1 18.09.5+dfsg1-1 Hi, The following vulnerability was published for docker.io. CVE-2019-13139[0]: command injection due to a missing validation of the git ref command 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-13139 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-13139 [1] https://github.com/moby/moby/pull/38944 [2] https://staaldraad.github.io/post/2019-07-16-cve-2019-13139-docker-build/ Regards, Salvatore --- End Message --- --- Begin Message --- Source: docker.io Source-Version: 18.09.1+dfsg1-8 We believe that the bug you reported is fixed in the latest version of docker.io, 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 933...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Arnaud Rebillout (supplier of updated docker.io package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 05 Aug 2019 15:27:57 +0700 Source: docker.io Architecture: source Version: 18.09.1+dfsg1-8 Distribution: unstable Urgency: medium Maintainer: Arnaud Rebillout Changed-By: Arnaud Rebillout Closes: 932673 933002 Changes: docker.io (18.09.1+dfsg1-8) unstable; urgency=medium . * Make myself the maintainer, and Dmitry uploader. (see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908868) * Add upstream patches for CVE-2019-13509 (Closes: #932673). * Add upstream patch for CVE-2019-13139 (Closes: #933002). Checksums-Sha1: 91511db1c88d949f537599c93d4468d87a72842f 8976 docker.io_18.09.1+dfsg1-8.dsc 272d2865048e4cf609fe28be8ebbe9ba32e58371 51164 docker.io_18.09.1+dfsg1-8.debian.tar.xz 9beaf7c51b8b8ee69515b2dd50d4d61dd67f4e31 7145 docker.io_18.09.1+dfsg1-8_source.buildinfo Checksums-Sha256: 776b87288940d0edee6d84e12d65f6363a914ae06513b30a70fa201f44c6a01e 8976 docker.io_18.09.1+dfsg1-8.dsc 602ae70c7880c231fb7f0aaf2abd15ffa188dd3aafba1c8f943e625d10068a39 51164 docker.io_18.09.1+dfsg1-8.debian.tar.xz c00cd7742477a1eae7a5b931a31313b207a0e9f0acb6c3e346744f7cd0f4f047 7145 docker.io_18.09.1+dfsg1-8_source.buildinfo Files: 2532282651d4c1e5b6521c99cf4e84f1 8976 admin optional docker.io_18.09.1+dfsg1-8.dsc 03e729db977bcc4f3214c76463185a04 51164 admin optional docker.io_18.09.1+dfsg1-8.debian.tar.xz 63d32952f619d5cb016966b4ca6d4630 7145 admin optional docker.io_18.09.1+dfsg1-8_source.buildinfo -BEGIN PGP SIGNATURE- iQJTBAEBCgA9FiEE0Kl7ndbut+9n4bYs5yXoeRRgAhYFAl1IBn4fHGFybmF1ZC5y ZWJpbGxvdXRAY29sbGFib3JhLmNvbQAKCRDnJeh5FGACFth7D/4lct1ivGkbzyN3 aw9Gk6iXgh4Vkk5gbnPANtb/Maky2g7fNO1gBQDibr+/WVZ5ZadmuhgvSh6HqK1F LnzvQKiUJ7iwtJTy3/mBItmrxB3gRE7OJMuQwY57aZy4V9ayN+7E/Exerz4HA4vk 7220f31rdK8JDiwJMG1dFjEFvlvh4Rvnic8iW49p78NSr+b1GjOBkqFiKx99ZMDF PORhOieFbFjxyeQTmiveFx22vLW+SW+WQjJvlpIMGmP7LUZNkGeFq0thdnau1C3k R6P1mckZbauJW7JWddUAUsOf0uEHYwtRhuCPNjH7xQUl4auINCXUHunxhQWkD7Eg mapg1GOttKrC/JxwVF9Q57vYXWN1fBzf0plulJ7MejTSHjmHO+2dWFF3f8m2Fmq2 hnnf01zzP6wNpyCcdF6gjeO8iTAmrtfqOxD5pA+vLyTHy/NHSqL650yC+S9bdv+H FlZaI43UmkcBarJ1UI7U1jOCLkA6O+reDgcFwt1VbTh4TNZ1N0gS9xi1sy4+W9Ts o8z8sj6D5ld11+pLyhRDoKNq4L1Al6URqljZxCnNntMzIeq5W0kS8SQAKDpA5T9v 0cnU3ZfimyjQKilVNXxOUGwYHlgyUjVfHL+2sPzkE4fP7jksIyvYkpuaZsJV/0hy eD+8wSpYfx1X+orGoPqxgbRcxC2giQ== =NP8A -END PGP SIGNATURE End Message ---
Processed: forcibly merging 933018 933314
Processing commands for cont...@bugs.debian.org: > forcemerge 933018 933314 Bug #933018 [ubuntu-dev-tools] ubuntu-dev-tools: `reverse-depends -b' ends with a traceback Bug #933314 [ubuntu-dev-tools] reverse-depends -b is broken: KeyError: 'Architectures' Severity set to 'normal' from 'grave' Merged 933018 933314 > thanks Stopping processing here. Please contact me if you need assistance. -- 933018: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933018 933314: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933314 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#932650: marked as done (swift-bench: (build-)depends on cruft package.)
Your message dated Mon, 5 Aug 2019 13:18:23 +0200 with message-id and subject line has caused the Debian Bug report #932650, regarding swift-bench: (build-)depends on cruft 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.) -- 932650: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932650 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: swift-bench Severity: serious Tags: bullseye, sid swift-bench (build-)depends on the python-swiftclient binary package which is no longer built by the python-swiftclient source package. You probably need to migrate to python3 --- End Message --- --- Begin Message --- Version: 1.2.0-5 Migrated. Thanks. -- Best regards Ondřej Nový --- End Message ---
Bug#933937: Exonerate conflicts with biobambam
On Sun, Jul 28, 2019 at 01:40:33AM +0200, Steffen Möller wrote: > > Am 27.07.2019 um 20:09 schrieb Andreas Tille: > > On Sat, Jul 27, 2019 at 07:40:45PM +0200, Steffen Möller wrote: > > > dpkg: error processing archive > > > /var/cache/apt/archives/exonerate_2.4.0-4_amd64.deb (--unpack): > > > trying to overwrite '/usr/bin/fastaexplode', which is also in package > > > biobambam2 2.0.95-1 > > > > > > Grummel. Does anybody have any insights on what is going on? > > Just guessing: You have some local package biobambam2 with a file name > > conflict? > > This one https://salsa.debian.org/med-team/biobambam2 > > I lack insights thought if the two are doing the very same thing or if > this is some coincidence of some sort. We did not have too many > conflicts without our community, yet. A stackoverflow entry points to > the exonerate package: > > https://bioinformatics.stackexchange.com/questions/7326/downloading-fasta-for-each-chromosome-of-a-complete-genome > > I am tempted to put fastaexplode into a separate package . Does anybody > by chance know if > https://github.com/gt1/biobambam2/blob/master/src/programs/fastaexplode.cpp > is doing the same thing? I'd otherwise contact upstream about it. Any news about this? We have now bug #933937 and need to care about it. Did you contacted upstream (of both packages)? The fastaexplode from exonerate[1] is definitely a different codebase than the one from biobambam2[2]. The command line interface is definitely different when looking at the command line parsing code. So serving both software packages with only one pick will most probably not work. Kind regards Andreas. [1] https://salsa.debian.org/med-team/exonerate/blob/master/src/util/fastaexplode.c [2] https://salsa.debian.org/med-team/biobambam2/blob/master/src/programs/fastaexplode.cpp -- http://fam-tille.de
Bug#895990: has there been any update on this as it still shows up a bug in debian testing
Dear all, I have been trying to install the package without much success. I did read the bug-report but it doesn't tell whether libgjs have been fixed in testing or not. Can somebody share an update on the situation please. -- Regards, Shirish Agarwal शिरीष अग्रवाल My quotes in this email licensed under CC 3.0 http://creativecommons.org/licenses/by-nc/3.0/ http://flossexperiences.wordpress.com E493 D466 6D67 59F5 1FD0 930F 870E 9A5B 5869 609C
Bug#932299: closed by Vincent Danjean (Bug#932299: fixed in owfs 3.2p3+dfsg1-3)
On Thu, Jul 25, 2019 at 10:54:04AM +, Debian Bug Tracking System wrote: Hi Vincent, > This is an automatic notification regarding your Bug report > which was filed against the src:owfs package: > > #932299: owfs: FTBFS: relocation R_X86_64_32 against symbol `_Py_NoneStruct' > can not be used > > It has been closed by Vincent Danjean . It won't migrate to testing because it was not a source-only upload. See https://lists.debian.org/debian-release/2019/07/msg00053.html second paragraph. Could you perform a source-only upload? Thanks, Bernhard
Processed: Re: Bug#933331: devscripts: FTBFS in buster (failing tests)
Processing control commands: > fixed -1 2.19.5+deb10u1 Bug #91 [src:devscripts] devscripts: FTBFS in buster (failing tests) The source 'devscripts' and version '2.19.5+deb10u1' do not appear to match any binary packages Marked as fixed in versions devscripts/2.19.5+deb10u1. > close -1 Bug #91 [src:devscripts] devscripts: FTBFS in buster (failing tests) Marked Bug as done -- 91: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=91 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#933331: devscripts: FTBFS in buster (failing tests)
Control: fixed -1 2.19.5+deb10u1
Control: close -1
On Mon, Jul 29, 2019 at 10:22:55AM +, Santiago Vila wrote:
> I tried to build this package in buster but it failed:
>
>
> ./test_debchange
> testDebianDistributions
> testDebianIncrement
> testUbuntuIncrement
> testUbuntuRebuild
> testEncoding
> testEmptyMessage
> testGuessedDistribution
> ASSERT:error output of perl -I ./../lib ./../scripts/debchange.pl --no-conf
> -c "/tmp/shunit.a65OSr/tmp/changelog" --vendor Debian --create -D
> jessie-backports --package test-package -v 1.0-1 'First upload'\n expected:<>
> but was: experimental, unstable, testing, stable, oldstable, oldoldstable,
> {bullseye,buster,stretch,jessie,wheezy}-proposed-updates,
> {testing,stable,oldstable,oldoldstable}-proposed-updates,
> {bullseye,buster,stretch,jessie,wheezy}-security,
> {testing,stable,oldstable,oldoldstable}}-security, stretch-backports,
> buster-backports and UNRELEASED.
> Using your request anyway.
> debchange.pl: Did you see that warning? Press RETURN to continue...>
I'm not entirely of what happened, but this seems to not happen after
the small patch placing buster-bpo as default --bpo.
So, I'm closing with that version (it's still in stable-new).
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`.
more about me: https://mapreri.org : :' :
Launchpad user: https://launchpad.net/~mapreri `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia `-
signature.asc
Description: PGP signature
Bug#933948: courier-mta randomly stops, cannot restart or start services, it just appears started, but it exists
Package: courier-mta Version: 1.0.6-1 Severity: critical Justification: causes serious data loss Dear Maintainer, * What led up to the situation? I have made dist-upgrade from 9 to Debian 10 * What exactly did you do (or not do) that was effective (or ineffective)? Just upgraded the system. Courier MTA apparently randomly stops and cannot be restarted. This includes courier-imap-ssl If I use web administrationa and click SAVE on IMAP or incoming ESMTP, and install new configuration, services start working. If I just use service courier-imap-ssl start this does not work, even if service is enabled. Example for courier-imap-ssl I have restarted from web administration, so this works: Executing /usr/sbin/imapd-ssl stop ; . /etc/courier/imapd-ssl ; test "$IMAPDSSLSTART" != YES || /usr/sbin/imapd-ssl start... Executing /usr/sbin/imapd stop ; . /etc/courier/imapd ; test "$IMAPDSTART" != YES || /usr/sbin/imapd start... root@stw1:/tmp# service courier-imap-ssl status ● courier-imap-ssl.service - LSB: Courier IMAP server (TLS) Loaded: loaded (/etc/init.d/courier-imap-ssl; generated) Active: active (exited) since Sun 2019-08-04 11:28:14 MST; 17h ago Docs: man:systemd-sysv-generator(8) Tasks: 0 (limit: 2379) Memory: 0B CGroup: /system.slice/courier-imap-ssl.service Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable. root@stw1:/tmp# lsof -i :993 COMMAND PIDUSER FD TYPE DEVICE SIZE/OFF NODE NAME couriertc 31390root3u IPv6 332900 0t0 TCP *:imaps (LISTEN) Now if I do following: root@stw1:/tmp# service courier-imap-ssl stop root@stw1:/tmp# service courier-imap-ssl start root@stw1:/tmp# lsof -i :993 root@stw1:/tmp# This does not work. root@stw1:/tmp# service courier-imap-ssl status ● courier-imap-ssl.service - LSB: Courier IMAP server (TLS) Loaded: loaded (/etc/init.d/courier-imap-ssl; generated) Active: active (exited) since Mon 2019-08-05 05:28:47 MST; 16s ago Docs: man:systemd-sysv-generator(8) Process: 31976 ExecStart=/etc/init.d/courier-imap-ssl start (code=exited, status=0/SUCCESS) Aug 05 05:28:47 stw1.rcdrun.com systemd[1]: Starting LSB: Courier IMAP serve…... Aug 05 05:28:47 stw1.rcdrun.com systemd[1]: Started LSB: Courier IMAP server…S). Hint: Some lines were ellipsized, use -l to show in full. So if I do simple: /usr/sbin/imapd-ssl start This works. It broke my email system and I need to install third party supervision to make sure that services are running. -- System Information: Debian Release: 10.0 APT prefers stable APT policy: (500, 'stable'), (90, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-8-amd64 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages courier-mta depends on: ii courier-authlib0.69.0-2 ii courier-base 1.0.6-1 ii debconf [debconf-2.0] 1.5.71 ii libc6 2.28-10 ii libcourier-unicode42.1-3 ii libgcc11:8.3.0-6 ii libgdbm6 1.18.1-4 ii libidn11 1.33-2.2 ii libnet-cidr-perl 0.19-1 ii libperl5.285.28.1-6 ii libstdc++6 8.3.0-6 ii sysvinit-utils 2.93-8 courier-mta recommends no packages. Versions of packages courier-mta suggests: ii bsd-mailx [mail-reader] 8.1.2-0.20180807cvs-1 pn courier-doc pn courier-filter-perl pn couriergrey ii emacs-nox [mail-reader] 1:26.1+1-3.2 ii mailutils [mail-reader] 1:3.5-3 ii mutt [mail-reader] 1.10.1-2.1 -- Configuration Files: /etc/courier/aliases/system changed: root: postmaster mailer-daemon: postmaster MAILER-DAEMON: postmaster uucp: postmaster www-data: postmaster postmaster: admin /etc/courier/courierd changed: prefix="/usr" exec_prefix="/usr" . /etc/environment PATH=/usr/bin:/bin:/usr/bin:/usr/local/bin SHELL=/bin/sh DSNTOAUTHADDR=0 DYNAMICDELIVERIES=1 DEFAULTDELIVERY="|| /usr/bin/dotforward ./Maildir" MAILDROPDEFAULT=./Maildir ESMTP_CORK=1 ESMTP_BLOCKBACKSCATTER=smtp/dsn UUXFLAGS="-j -g C" ESMTP_USE_STARTTLS=1 COURIERTLS=/usr/bin/couriertls ESMTP_TLS_VERIFY_DOMAIN=0 ESMTP_PREFER_IPV6_MX=1 TLS_TRUSTCERTS=/etc/ssl/cert.pem TLS_VERIFYPEER=NONE /etc/courier/enablefiltering changed: esmtp local /etc/courier/esmtpauthclient [Errno 13] Permission denied: '/etc/courier/esmtpauthclient' /etc/courier/esmtpd changed: PATH=/usr/bin:/bin:/usr/bin:/usr/local/bin SHELL=/bin/sh ULIMIT=32768 BOFHCHECKDNS="1" BOFHNOEXPN=1 BOFHNOVRFY=1 TARPIT=1 NOADDMSGID="1" NOADDDATE="1" NOADDRREWRITE=0 ESMTP_LOG_DIALOG=0 AUTH_REQUIRED="0" COURIERTLS=/usr/bin/couriertls TLS_CERTFILE=/etc/courier/esmtpd.pem TLS_DHPARAMS=/etc/courier/dhparams.pem TLS_TRUSTCERTS=/etc/ssl/cert.pem TLS_VERIFYPEER=NONE MAILUSER=courier MAILGROUP=courier PORT=smtp BLACKLISTS="-block=zen.
Processed: fixed 933254 in 0.8.2
Processing commands for cont...@bugs.debian.org:
> fixed 933254 0.8.2
Bug #933254 {Done: Xavier } [pkg-js-tools] Auto detection of
components is broken when used in webpack
Marked as fixed in versions pkg-js-tools/0.8.2.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
933254: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933254
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: notfound 933254 in 0.8.2
Processing commands for cont...@bugs.debian.org:
> notfound 933254 0.8.2
Bug #933254 {Done: Xavier } [pkg-js-tools] Auto detection of
components is broken when used in webpack
No longer marked as found in versions pkg-js-tools/0.8.2.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
933254: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933254
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#933958: golang-1.12: ftbfs with golang-1.12
Package: src:golang-1.12 Version: 1.12.7-2 Severity: serious As golang defaults has been upgrade to golang-1.12. With the test of build golang-1.12, I meet the same problem on amd64 as currently mipsel. failed to initialize build cache at /sbuild-nonexistent/.cache/go-build: mkdir /sbuild-nonexistent: permission denied https://buildd.debian.org/status/fetch.php?pkg=golang-1.12&arch=mipsel&ver=1.12.7-2&stamp=1564842229&raw=0 -- YunQiang Su
Bug#933785: gitlab: CVE-2019-5470 CVE-2019-5469 CVE-2019-5468 CVE-2019-5466 CVE-2019-5465 CVE-2019-5464 CVE-2019-5463 CVE-2019-5462 CVE-2019-5461
Control: block -1 by 933795 Control: block -1 by 933778 On Sat, 03 Aug 2019 15:41:53 +0200 Salvatore Bonaccorso wrote: The following vulnerabilities were published for gitlab, see [9]. Since these fixes are not backported to 11.10 branch, we will have to update to 11.11 branch. Currently blocked by gitaly build failure reported upstream https://gitlab.com/gitlab-org/gitaly/issues/1840
Processed: Re: gitlab: CVE-2019-5470 CVE-2019-5469 CVE-2019-5468 CVE-2019-5466 CVE-2019-5465 CVE-2019-5464 CVE-2019-5463 CVE-2019-5462 CVE-2019-5461
Processing control commands: > block -1 by 933795 Bug #933785 [src:gitlab] gitlab: CVE-2019-5470 CVE-2019-5469 CVE-2019-5468 CVE-2019-5466 CVE-2019-5465 CVE-2019-5464 CVE-2019-5463 CVE-2019-5462 CVE-2019-5461 933785 was not blocked by any bugs. 933785 was not blocking any bugs. Added blocking bug(s) of 933785: 933795 > block -1 by 933778 Bug #933785 [src:gitlab] gitlab: CVE-2019-5470 CVE-2019-5469 CVE-2019-5468 CVE-2019-5466 CVE-2019-5465 CVE-2019-5464 CVE-2019-5463 CVE-2019-5462 CVE-2019-5461 933785 was blocked by: 933795 933785 was not blocking any bugs. Added blocking bug(s) of 933785: 933778 -- 933785: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933785 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Unarchive because the FTBFS is still in stretch
Processing commands for cont...@bugs.debian.org:
> unarchive 915270
Bug #915270 {Done: Giovanni Mascellani } [src:libgovirt]
libgovirt: FTBFS because https-cert/ca-cert.pem is expired
Unarchived Bug 915270
>
End of message, stopping processing here.
Please contact me if you need assistance.
--
915270: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915270
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: Re: libgovirt: diff for NMU version 0.3.4-3.1
Processing commands for cont...@bugs.debian.org:
> reopen 915270
Bug #915270 {Done: Giovanni Mascellani } [src:libgovirt]
libgovirt: FTBFS because https-cert/ca-cert.pem is expired
'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 libgovirt/0.3.4-3.1.
> found 915270 0.3.4-2
Bug #915270 [src:libgovirt] libgovirt: FTBFS because https-cert/ca-cert.pem is
expired
Ignoring request to alter found versions of bug #915270 to the same values
previously set
> fixed 915270 0.3.4-3.1
Bug #915270 [src:libgovirt] libgovirt: FTBFS because https-cert/ca-cert.pem is
expired
Marked as fixed in versions libgovirt/0.3.4-3.1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
915270: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915270
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#915270: libgovirt: diff for NMU version 0.3.4-3.1
reopen 915270 found 915270 0.3.4-2 fixed 915270 0.3.4-3.1 thanks Hi. Could we please fix this in stretch as well? (Packages in buster must build in buster, packages in stretch must build in stretch). Would your diff apply cleanly to the version in stretch? (I have not tested this yet). Thanks.
Bug#877496: explib310 FTBFS
control: tags -1 patch pending
I went ahead and uploaded the patch for this.
Feel free to package the new release on top of this upload!
(at least we can now unblock reverse-deps)
G.
diff -Nru sexplib310-113.33.03/debian/changelog
sexplib310-113.33.03/debian/changelog
--- sexplib310-113.33.03/debian/changelog 2016-08-19 09:11:38.0
+0200
+++ sexplib310-113.33.03/debian/changelog 2019-08-05 18:06:14.0
+0200
@@ -1,3 +1,11 @@
+sexplib310 (113.33.03-3.1) unstable; urgency=medium
+
+ * Non-maintainer upload
+ * Cherry-pick upstream fix for new ocaml (From Ubuntu)
+Closes: #877496
+
+ -- Gianfranco Costamagna Mon, 05 Aug 2019
18:06:14 +0200
+
sexplib310 (113.33.03-3) unstable; urgency=medium
* Team upload
diff -Nru
sexplib310-113.33.03/debian/patches/1c3df4807e71f39d064941d5fc527fe3c2e2bda7.patch
sexplib310-113.33.03/debian/patches/1c3df4807e71f39d064941d5fc527fe3c2e2bda7.patch
---
sexplib310-113.33.03/debian/patches/1c3df4807e71f39d064941d5fc527fe3c2e2bda7.patch
1970-01-01 01:00:00.0 +0100
+++
sexplib310-113.33.03/debian/patches/1c3df4807e71f39d064941d5fc527fe3c2e2bda7.patch
2019-08-05 18:06:14.0 +0200
@@ -0,0 +1,80 @@
+From 1c3df4807e71f39d064941d5fc527fe3c2e2bda7 Mon Sep 17 00:00:00 2001
+From: Thomas Refis
+Date: Tue, 22 Mar 2016 14:13:51 +
+Subject: [PATCH] 113.33.00+4.03
+
+---
+ CHANGES.md | 4
+ _oasis | 4 ++--
+ opam| 2 +-
+ src/conv.ml | 13 +
+ 4 files changed, 16 insertions(+), 7 deletions(-)
+
+--- a/CHANGES.md
b/CHANGES.md
+@@ -1,3 +1,7 @@
++## 113.33.00+4.03
++
++Various updates to work with OCaml 4.03.0
++
+ ## 113.33.00
+
+ - Changes `Sexp.to_string` to escape all non-ASCII characters.
+--- a/_oasis
b/_oasis
+@@ -1,5 +1,5 @@
+ OASISFormat: 0.4
+-OCamlVersion: >= 4.02.3
++OCamlVersion: >= 4.03.0
+ FindlibVersion:>= 1.3.2
+ Name: sexplib
+ Version: 113.33.03
+--- a/opam
b/opam
+@@ -15,4 +15,4 @@
+ "ocamlfind" {build & >= "1.3.2"}
+ "js-build-tools" {build}
+ ]
+-available: [ ocaml-version = "4.02.3" ]
++available: [ ocaml-version = "4.03.0" ]
+--- a/src/conv.ml
b/src/conv.ml
+@@ -185,7 +185,7 @@
+
+ (* [Obj.extension_id] works on both the exception itself, and the extension
slot of the
+ exception. *)
+- let rec clean_up_handler (slot : Obj.t) =
++ let rec clean_up_handler (slot : extension_constructor) =
+ let id = Obj.extension_id slot in
+ let old_exn_id_map = !exn_id_map in
+ let new_exn_id_map = Exn_ids.remove id old_exn_id_map in
+@@ -196,7 +196,7 @@
+ exn_id_map := new_exn_id_map
+
+ let add_auto ?(finalise = true) exn sexp_of_exn =
+-let id = Obj.extension_id exn in
++let id = Obj.extension_id (Obj.extension_constructor exn) in
+ let rec loop () =
+ let old_exn_id_map = !exn_id_map in
+ let new_exn_id_map = Exn_ids.add id sexp_of_exn old_exn_id_map in
+@@ -205,13 +205,18 @@
+ loop ()
+ else begin
+ exn_id_map := new_exn_id_map;
+-if finalise then Gc.finalise clean_up_handler (Obj.extension_slot exn)
++if finalise then
++ try
++Gc.finalise clean_up_handler (Obj.extension_constructor exn)
++ with Invalid_argument _ ->
++(* Pre-allocated extension constructors cannot be finalised *)
++()
+ end
+ in
+ loop ()
+
+ let find_auto exn =
+-let id = Obj.extension_id exn in
++let id = Obj.extension_id (Obj.extension_constructor exn) in
+ match Exn_ids.find id !exn_id_map with
+ | exception Not_found -> None
+ | sexp_of_exn -> Some (sexp_of_exn exn)
diff -Nru sexplib310-113.33.03/debian/patches/series
sexplib310-113.33.03/debian/patches/series
--- sexplib310-113.33.03/debian/patches/series 1970-01-01 01:00:00.0
+0100
+++ sexplib310-113.33.03/debian/patches/series 2019-08-05 18:06:14.0
+0200
@@ -0,0 +1 @@
+1c3df4807e71f39d064941d5fc527fe3c2e2bda7.patch
Processed: Re: explib310 FTBFS
Processing control commands: > tags -1 patch pending Bug #877496 [src:sexplib310] sexplib310 FTBFS: Error: This expression has type Obj.t but an expression was expected of type extension_constructor Added tag(s) patch and pending. -- 877496: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=877496 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: explib310 FTBFS
Processing control commands: > tags -1 -patch -pending Bug #877496 [src:sexplib310] sexplib310 FTBFS: Error: This expression has type Obj.t but an expression was expected of type extension_constructor Removed tag(s) patch. Bug #877496 [src:sexplib310] sexplib310 FTBFS: Error: This expression has type Obj.t but an expression was expected of type extension_constructor Removed tag(s) pending. -- 877496: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=877496 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#877496: explib310 FTBFS
control: tags -1 -patch -pending After updating the chroot, looks like the Ubuntu patch is not enough anymore. G.
Bug#933958: The golang FTBFS on amd64 should be fixed
control: reassign -1 dh-golang control: found -1 1.39 control: fixed -1 1.41 control: close -1 Hi, the FTBFS of golang should be fixed. It was due to the GOCACHE changes from Go 1.11 to Go 1.12. Anthony Fok has just fixed this in dh-golang. I can confirm that golang-1.12 builds fine in an updated sid chroot on amd64 for me. Regards, Tobias signature.asc Description: OpenPGP digital signature
Processed: The golang FTBFS on amd64 should be fixed
Processing control commands: > reassign -1 dh-golang Bug #933958 [src:golang-1.12] golang-1.12: ftbfs with golang-1.12 Bug reassigned from package 'src:golang-1.12' to 'dh-golang'. No longer marked as found in versions golang-1.12/1.12.7-2. Ignoring request to alter fixed versions of bug #933958 to the same values previously set > found -1 1.39 Bug #933958 [dh-golang] golang-1.12: ftbfs with golang-1.12 Marked as found in versions dh-golang/1.39. > fixed -1 1.41 Bug #933958 [dh-golang] golang-1.12: ftbfs with golang-1.12 Marked as fixed in versions dh-golang/1.41. > close -1 Bug #933958 [dh-golang] golang-1.12: ftbfs with golang-1.12 Marked Bug as done -- 933958: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933958 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#933979: gnutls28: FTBFS on i386: Build killed with signal TERM after 150 minutes of inactivity after dtls/dtls test
Source: gnutls28 Version: 3.6.9-3 Severity: serious Justification: FTBFS on release arch From: https://buildd.debian.org/status/fetch.php?pkg=gnutls28&arch=i386&ver=3.6.9-3&stamp=1564822578&raw=0 […] SKIP: p11-kit-trust.sh PASS: system-override-kx.sh PASS: certtool-pkcs11.sh PASS: danetool.sh PASS: gnutls-cli-invalid-crl.sh PASS: dtls/dtls E: Build killed with signal TERM after 150 minutes of inactivity Build finished at 2019-08-03T08:56:12Z
Processed: huh, that’s new…
Processing commands for cont...@bugs.debian.org: > tags 933979 + ftbfs Bug #933979 [src:gnutls28] gnutls28: FTBFS on i386: Build killed with signal TERM after 150 minutes of inactivity after dtls/dtls test Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 933979: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933979 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#933920: src:python-markdown: Unsafe use of yaml.load()
Hi Scott! On Mon, Aug 05, 2019 at 01:32:46AM -0400, Scott Kitterman wrote: > Package: src:python-markdown > Version: 3.0.1-3 > Severity: grave > Tags: security > Justification: user security hole > > The new version of pyyaml no longer allows use of yaml.load() without a > loader being specifed. This raises a deprecation warning which has > caused and autopkgtest failure on this package. These are generally > trivial to fix, see the upstream guidance [1]. I will now fix the use of yaml.load() for compatibility with pyyaml 5.1 (by uploading the new upstream release to unstable), but the new version will still use unsafe_load(). Please see this upstream change: https://github.com/Python-Markdown/markdown/pull/806 As the upstream comment explains, “We use unsafe_load because users may need to pass in actual Python objects. As this is only available from the CLI, the user has much worse problems if an attacker can use this as an attack vector”. -- Dmitry Shachnev signature.asc Description: PGP signature
Bug#933981: cdrom: USB, KVM create connect/disconnect loop in level1 (repair) install
Package: cdrom Severity: grave Tags: d-i Justification: renders package unusable Dear Maintainer, * What led up to the situation? I had another machine that gave kernel panic while upgrading from Stretch to Buster. Use of Graphical install was also a problem during re-install due to destroyed system. (I reported this issue in another report.) Thus, I chose to upgrade an identical machine from level 1 (Debain Repair in GRUB2 boot menu). * What exactly did you do (or not do) that was effective (or ineffective)? The scrolling log in the command line display showed repeated connect/disconnect loops for USB devices (of many kinds). This applied also to USB mice and keyboards connected via KVM. For what it was worth, I used a local cache of the DVDs on the machine's hard drive. Unplugged all USB, plugged in single USB keyboard only, and directly, not via KVM. * What was the outcome of this action? Upgraded fine with just the keyboard directly plugged into USB. * What outcome did you expect instead? Correct handling of USB, without issues. -- System Information: Debian Release: 10.0 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-5-amd64 (SMP w/8 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#933958: The golang FTBFS on amd64 should be fixed
Hi, On Tue, Aug 6, 2019 at 2:03 AM Dr. Tobias Quathamer wrote: > > the FTBFS of golang should be fixed. It was due to the GOCACHE changes > from Go 1.11 to Go 1.12. Anthony Fok has just fixed this in dh-golang. > The golang compiler doesn't build depends dh-golang. So any change in dh-golang won't fix the compiler itself. -- Shengjing Zhu
Bug#933988: kubernetes: CVE-2019-11247: API server allows access to custom resources via wrong scope
Source: kubernetes Version: 1.7.16+dfsg-1 Severity: grave Tags: security upstream Forwarded: https://github.com/kubernetes/kubernetes/issues/80983 Hi, The following vulnerability was published for kubernetes. CVE-2019-11247[0]: API server allows access to custom resources via wrong scope 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-11247 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-11247 [1] https://github.com/kubernetes/kubernetes/issues/80983 Regards, Salvatore
Processed: [bts-link] source package mutter
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package mutter > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org Setting user to debian-bts-l...@lists.debian.org (was debian-bts-l...@lists.debian.org). > # remote status report for #932428 (http://bugs.debian.org/932428) > # Bug title: gnome-shell: sometimes crashes on lid close in > wayland_output_update_for_output() > # * https://gitlab.gnome.org/GNOME/mutter/merge_requests/538 > # * remote status changed: (?) -> merged > # * closed upstream > tags 932428 + fixed-upstream Bug #932428 [libmutter-3-0] gnome-shell: sometimes crashes on lid close in wayland_output_update_for_output() Added tag(s) fixed-upstream. > usertags 932428 + status-merged There were no usertags set. Usertags are now: status-merged. > # remote status report for #932767 (http://bugs.debian.org/932767) > # Bug title: gnome-shell: crash on monitor unplug > # * https://gitlab.gnome.org/GNOME/mutter/merge_requests/538 > # * remote status changed: (?) -> merged > # * closed upstream > tags 932767 + fixed-upstream Bug #932767 [libmutter-3-0] gnome-shell: crash on monitor unplug Bug #933842 [libmutter-3-0] crashes when switching monitor input under wayland Added tag(s) fixed-upstream. Added tag(s) fixed-upstream. > usertags 932767 + status-merged There were no usertags set. Usertags are now: status-merged. > # remote status report for #932781 (http://bugs.debian.org/932781) > # Bug title: gnome-shell crashed on laptop lid close > # * https://gitlab.gnome.org/GNOME/mutter/merge_requests/538 > # * remote status changed: (?) -> merged > # * closed upstream > tags 932781 + fixed-upstream Bug #932781 [libmutter-3-0] gnome-shell crashed on laptop lid close Added tag(s) fixed-upstream. > usertags 932781 + status-merged There were no usertags set. Usertags are now: status-merged. > thanks Stopping processing here. Please contact me if you need assistance. -- 932428: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932428 932767: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932767 932781: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932781 933842: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933842 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#933958: The golang FTBFS on amd64 should be fixed
Processing control commands:
> reopen -1
Bug #933958 {Done: "Dr. Tobias Quathamer" } [dh-golang]
golang-1.12: ftbfs with golang-1.12
'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 dh-golang/1.41.
> reassign -1 src:golang-1.12
Bug #933958 [dh-golang] golang-1.12: ftbfs with golang-1.12
Bug reassigned from package 'dh-golang' to 'src:golang-1.12'.
No longer marked as found in versions dh-golang/1.39.
Ignoring request to alter fixed versions of bug #933958 to the same values
previously set
> found -1 1.12.7-2
Bug #933958 [src:golang-1.12] golang-1.12: ftbfs with golang-1.12
Marked as found in versions golang-1.12/1.12.7-2.
--
933958: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933958
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#933958: The golang FTBFS on amd64 should be fixed
control: reopen -1 control: reassign -1 src:golang-1.12 control: found -1 1.12.7-2 Am 05.08.19 um 20:59 schrieb Shengjing Zhu: > Hi, > > On Tue, Aug 6, 2019 at 2:03 AM Dr. Tobias Quathamer wrote: >> >> the FTBFS of golang should be fixed. It was due to the GOCACHE changes >> from Go 1.11 to Go 1.12. Anthony Fok has just fixed this in dh-golang. >> > > The golang compiler doesn't build depends dh-golang. So any change in > dh-golang won't fix the compiler itself. You're right, of course. I jumped to that conclusion due to the error message "failed to initialize build cache". I don't know why my first build succeeded -- now I can reproduce the FTBFS :-( However, I think I have found the solution for golang-1.12 (very similar to dh-golang). I'm currently building the package and will upload the fix soon. Regards, Tobias signature.asc Description: OpenPGP digital signature
Bug#933992: FTBFS without lwt.syntax
Source: obus Version: 1.1.5-6 Severity: serious Hello, As lwt is a key package and because of [1], its camlp4 dependency has been removed, removing lwt.syntax. Now, obus FTBFS because it depends on lwt.syntax. Please provide an obus package that does not depend on lwt.syntax or, better, on camlp4. [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933722 Cheers, -- Stéphane -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-5-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system)
Bug#933993: FTBFS because depends on lwt.syntax
Source: ocaml-usb Version: 1.3.0-4 Severity: serious Hello, As lwt is a key package and because of [1], its camlp4 dependency has been removed, removing lwt.syntax. Now, ocaml-usb FTBFS because it depends on lwt.syntax. Please provide an ocaml-usb package that does not depend on lwt.syntax or, better, on camlp4. [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933722 Cheers, -- Stéphane -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-5-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system)
Bug#933994: FTBFS because depends on lwt.syntax
Source: ocaml-sqlexpr Version: 0.5.5-3 Severity: serious Hello, As lwt is a key package and because of [1], its camlp4 dependency has been removed, removing lwt.syntax. Now, ocaml-sqlexpr FTBFS because it depends on lwt.syntax. Please provide an ocaml-usb package that does not depend on lwt.syntax or, better, on camlp4. [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933722 Cheers, -- Stéphane -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-5-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system)
Processed: block 933722 with 933992 933993 933994
Processing commands for cont...@bugs.debian.org: > block 933722 with 933992 933993 933994 Bug #933722 [camlp4] camlp4 is deprecated and almost dead upstream (and a key package) 933722 was not blocked by any bugs. 933722 was not blocking any bugs. Added blocking bug(s) of 933722: 933992, 933994, and 933993 > thanks Stopping processing here. Please contact me if you need assistance. -- 933722: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933722 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: retitle 933994 to ocaml-sqlexpr FTBFS because it depends on lwt.syntax
Processing commands for cont...@bugs.debian.org: > retitle 933994 ocaml-sqlexpr FTBFS because it depends on lwt.syntax Bug #933994 [src:ocaml-sqlexpr] FTBFS because depends on lwt.syntax Changed Bug title to 'ocaml-sqlexpr FTBFS because it depends on lwt.syntax' from 'FTBFS because depends on lwt.syntax'. > thanks Stopping processing here. Please contact me if you need assistance. -- 933994: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933994 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: retitle 933993 to ocaml-usb FTBFS because it depends on lwt.syntax
Processing commands for cont...@bugs.debian.org: > retitle 933993 ocaml-usb FTBFS because it depends on lwt.syntax Bug #933993 [src:ocaml-usb] FTBFS because depends on lwt.syntax Changed Bug title to 'ocaml-usb FTBFS because it depends on lwt.syntax' from 'FTBFS because depends on lwt.syntax'. > thanks Stopping processing here. Please contact me if you need assistance. -- 933993: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933993 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: retitle 933992 to obus FTBFS because it depends on lwt.syntax
Processing commands for cont...@bugs.debian.org: > retitle 933992 obus FTBFS because it depends on lwt.syntax Bug #933992 [src:obus] FTBFS without lwt.syntax Changed Bug title to 'obus FTBFS because it depends on lwt.syntax' from 'FTBFS without lwt.syntax'. > thanks Stopping processing here. Please contact me if you need assistance. -- 933992: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933992 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#927165: luks 2 in Buster
Hello, I just wanted to mention, that this situation of version-change, from luks 1 to luks 2, makes a multi-boot Stretch-Buster impossible - at least in my situation. I had sda1 as /boot, sda2 as encrypted Stretch (luks 1), Grub in MBR and installed Buster (I used the XFCE4-installation-CD) encrypted (luks 2) to sda3 (all primary Partitions). Now the fact is, that I cannot start Stretch on sda2 anymore, not with the installed Grub, nor with any "Rescuedisks", or similar... I had to chroot in Stretch, install Grub from there again and build the "initram.img" new, e.g. update it with "dpkg-reconfigure cryptsetup" afterwards - now I can start Stretch again, but not at all Buster... Theres also a second bug about this: after installation of Buster, I can see "cryptsetup" as package installed, but I cannot fetch the command in a terminal (as root). Neighter "cryptsetup"-command, nor "dpkg-reconfigure"-command is available in terminal, even if the packages are shown as installed. But if I use the XFCE4-installation-CD in "rescue/repair-mode" on sda3 (Buster) as root, these commands are available again... Greetings, Jack
Processed: notfound 933254 in 0.7
Processing commands for cont...@bugs.debian.org:
> notfound 933254 0.7
Bug #933254 {Done: Xavier } [pkg-js-tools] Auto detection of
components is broken when used in webpack
Ignoring request to alter found versions of bug #933254 to the same values
previously set
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
933254: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933254
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#933280: marked as done (BD on texlive-generic-extra which isn't build anymore and isn't in bullseye)
Your message dated Mon, 05 Aug 2019 21:48:25 + with message-id and subject line Bug#933280: fixed in breathe 4.12.0-2 has caused the Debian Bug report #933280, regarding BD on texlive-generic-extra which isn't build anymore and isn't in bullseye 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.) -- 933280: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933280 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: breathe Version: 4.11.1-1 Severity: serious Tags: ftbfs sid bullseye Recently the texlive-base package has stopped building the transitional package texlive-generic-extra. This is an issue for your package as it build-depends on it. Please update the building of your package to use texlive-plain-generic instead. Unfortunately the migration software doesn't detected this kind of situation yet, so your package also FTBFS in bullseye since 2019-07-16. Paul signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: breathe Source-Version: 4.12.0-2 We believe that the bug you reported is fixed in the latest version of breathe, 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 933...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sebastian Ramacher (supplier of updated breathe package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 05 Aug 2019 23:03:31 +0200 Source: breathe Architecture: source Version: 4.12.0-2 Distribution: unstable Urgency: medium Maintainer: Sebastian Ramacher Changed-By: Sebastian Ramacher Closes: 933280 Changes: breathe (4.12.0-2) unstable; urgency=medium . * Upload to unstable. * debian/: Replace texlive-generic-extra with texlive-plain-generic (Closes: #933280) * debian/control: Bump Standards-Version. Checksums-Sha1: c5dbfc41fe1a2f92cfe3ca8367ccb47638c1310f 2400 breathe_4.12.0-2.dsc ad35cc6e07f3ab441f2874be7ae44c6a3454b3df 5852 breathe_4.12.0-2.debian.tar.xz Checksums-Sha256: 937b51ab4a049bc1c85e2a259977b0544df9182c13453da308a9f9dc0f686dad 2400 breathe_4.12.0-2.dsc 211efbb6dcd47766be61ae0c3ccc46ea16706259893326631004132b607ab6d9 5852 breathe_4.12.0-2.debian.tar.xz Files: bca212b752641dd89a2980b3ea2ef69b 2400 python optional breathe_4.12.0-2.dsc 7453baef695a0af6aedcb4050f9c76ce 5852 python optional breathe_4.12.0-2.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEE94y6B4F7sUmhHTOQafL8UW6nGZMFAl1ImkMACgkQafL8UW6n GZPfphAAvD75x3X+y1VLe6yv+h8MpUb0ionUU0ysuadB1nnTcvVo6YpFQPJWFD7r JYACAwlQd1qQ8KMSor1SnNs0Z/5lC8GzAzFKHqo8ba6ipbmjztBJbbJIXzKKDnWs h/c0FJ+EnOdqaFY25bsHnNKIgb6PnS7cFWSWL2IgguadhTeHQSGCn+KuiNXuxIXo L/UUsJikB3E2IZCCHa98s7CPdaSr5dUeDCgRREh3s3FBM2QlMBFqAvYGPVIrjbaw pOdErGTSK1/V0Tr4L8ZuTXYn7iubI/W1Kkmyb6Srbpu9vVmzuzoTsHiIDEdBvmkS Jyb+f+Ps3TonZ7o0v5eQaXy2fRn8H9Epb1ydRG0zOHOvA1BWBNCZjn8D8d28RTVX m4mrymRPaHmL/CbLioWkTMbU/MqFGMBYQv65ZzcAtAbJpdeTKoCKEmyqrh0E0UUy Qhx1DgZLxnoMyedvMXqcsGWYnCFb6VCTEgvyMh0O8JjHdaFD8sdeD6em3BO9Wprl /NOpkpk2+Ez8aD42UDRxH6zNWPC+1EKKPE+/5YARF6RX294TZcqSAg89ggwIVdN9 oraYQ59z70XRiIVQjjkgKG3NnzdYM2ZJQm24q5ZPcjgN6OtOVzej7FoLAxeqZsnQ D9CIWdkAl/iS7Kowtat0wKGZiA8o0IpuX/4e2jekVfuXd1HH9g4= =OaAz -END PGP SIGNATURE End Message ---
Bug#933359: marked as done (metview: FTBFS after eccodes update)
Your message dated Mon, 05 Aug 2019 21:57:37 + with message-id and subject line Bug#933359: fixed in eccodes 2.13.0-3 has caused the Debian Bug report #933359, regarding metview: FTBFS after eccodes update 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.) -- 933359: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933359 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: metview Version: 5.3.0-3 Severity: serious. Hello, after eccodes update, the package now FTBFS. please see the build log: http://debomatic-amd64.debian.net/distribution#unstable/metview/5.3.0-3/buildlog ^~~ strsep make[3]: *** No rule to make target 'eccodes-NOTFOUND', needed by 'lib/libMvMars.so.0.0.0'. Stop. make[3]: *** Waiting for unfinished jobs [ 13%] Building CXX object src/libMvQtGui/CMakeFiles/MvQtGui.dir/moc_MvQKeyMimeData.cpp.o [ 13%] Building C object src/libMars/CMakeFiles/MvMars.dir/mars_client_version.c.o the library seems somewhat at least partially detected, but I couldn't figure out what is going on -- Looking for xdr_pointer - found -- [eccodes] (2.13.0) -- [odb_api] (0.18.1) --ODB_API_INCLUDE_DIRS : [/usr/lib/include /build/odb-api/eckit/src /build/odb-api/debian/build/eckit/src /usr/include /usr/include/eigen3 /usr/include/x86_64-linux-gnu /build/odb-api/metkit/src /build/odb-api/debian/build/metkit/src /usr/lib/include /usr/lib/python3/dist-packages/numpy/core/include /usr/include/openjpeg-2.1 /usr/include/python3.7m] --ODB_API_LIBRARIES : [Odb_fortran Odb eckit eckit_geometry eckit_linalg eckit_maths eckit_web eckit_cmd metkit -L/usr/lib/python3.7/config-3.7m-x86_64-linux-gnu -L/usr/lib -lpython3.7m -lcrypt -lpthread -ldl -lutil -lm -Xlinker -export-dynamic -Wl,-O1 -Wl,-Bsymbolic-functions] -- [ODB] (1.0.10) --ODB_INCLUDE_DIRS : [/usr/lib/include /usr/lib/x86_64-linux-gnu/cmake/odb/../../../module] --ODB_DEFINITIONS : [LITTLE LINUX] --ODB_LIBRARIES : [odb_lib /usr/lib/x86_64-linux-gnu/openmpi/lib/libmpi_cxx.so /usr/lib/x86_64-linux-gnu/openmpi/lib/libmpi.so /usr/lib/x86_64-linux-gnu/libdl.so] -- [magics] (4.0.3) --MAGICS_INCLUDE_DIRS : [/usr/include/magics /usr/include/terralib /usr/include/terralib/kernel /usr/lib/include /usr/include /usr/lib/python3/dist-packages/numpy/core/include /usr/include/openjpeg-2.1 /usr/include/hdf5/serial /usr/include/pango-1.0 /usr/include/harfbuzz /usr/include/fribidi /usr/include/cairo /usr/include/glib-2.0 /usr/lib/x86_64-linux-gnu/glib-2.0/include /usr/include/pixman-1 /usr/include/uuid /usr/include/freetype2 /usr/include/libpng16 /build/odb-api/eckit/src /build/odb-api/debian/build/eckit/src /usr/include/eigen3 /usr/include/x86_64-linux-gnu /build/odb-api/metkit/src /build/odb-api/debian/build/metkit/src /usr/include/python3.7m] --MAGICS_DEFINITIONS : [MAGICS_QT5] --MAGICS_LIBRARIES : [MagPlus eccodes eccodes_f90 /usr/lib/x86_64-linux-gnu/libpng.so /usr/lib/x86_64-linux-gnu/libz.so /usr/lib/x86_64-linux-gnu/libaec.so /usr/lib/x86_64-linux-gnu/libm.so /usr/lib/x86_64-linux-gnu/libopenjp2.so /usr/lib/x86_64-linux-gnu/libexpat.so debug optimized /usr/lib/x86_64-linux-gnu/libnetcdf.so /usr/lib/x86_64-linux-gnu/hdf5/serial/libhdf5.so /usr/lib/x86_64-linux-gnu/libpthread.so /usr/lib/x86_64-linux-gnu/libsz.so /usr/lib/x86_64-linux-gnu/libdl.so /usr/lib/x86_64-linux-gnu/libproj.so -lpangocairo-1.0 -lpango-1.0 -lgobject-2.0 -lglib-2.0 -lcairo Odb_fortran Odb eckit eckit_geometry eckit_linalg eckit_maths eckit_web eckit_cmd metkit -L/usr/lib/python3.7/config-3.7m-x86_64-linux-gnu -L/usr/lib -lpython3.7m -lcrypt -lpthread -ldl -lutil -lm -Xlinker -export-dynamic -Wl,-O1 -Wl,-Bsymbolic-functions] G. --- End Message --- --- Begin Message --- Source: eccodes Source-Version: 2.13.0-3 We believe that the bug you reported is fixed in the latest version of eccodes, 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 933...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Alastair McKinstry (supplier of updated eccodes 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
Bug#933958: marked as done (golang-1.12: ftbfs with golang-1.12)
Your message dated Mon, 05 Aug 2019 22:33:16 + with message-id and subject line Bug#933958: fixed in golang-1.12 1.12.7-3 has caused the Debian Bug report #933958, regarding golang-1.12: ftbfs with golang-1.12 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.) -- 933958: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933958 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:golang-1.12 Version: 1.12.7-2 Severity: serious As golang defaults has been upgrade to golang-1.12. With the test of build golang-1.12, I meet the same problem on amd64 as currently mipsel. failed to initialize build cache at /sbuild-nonexistent/.cache/go-build: mkdir /sbuild-nonexistent: permission denied https://buildd.debian.org/status/fetch.php?pkg=golang-1.12&arch=mipsel&ver=1.12.7-2&stamp=1564842229&raw=0 -- YunQiang Su --- End Message --- --- Begin Message --- Source: golang-1.12 Source-Version: 1.12.7-3 We believe that the bug you reported is fixed in the latest version of golang-1.12, 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 933...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Dr. Tobias Quathamer (supplier of updated golang-1.12 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, 05 Aug 2019 21:49:35 +0200 Source: golang-1.12 Architecture: source Version: 1.12.7-3 Distribution: unstable Urgency: medium Maintainer: Go Compiler Team Changed-By: Dr. Tobias Quathamer Closes: 933958 Changes: golang-1.12 (1.12.7-3) unstable; urgency=medium . * Set GOCACHE to fix a FTBFS. (Closes: #933958) Checksums-Sha1: 6b2f746db796877b85235ced9339d9eed842e040 2589 golang-1.12_1.12.7-3.dsc 4477a40780fd0c27e9f642b0af4ac14d7310a990 36044 golang-1.12_1.12.7-3.debian.tar.xz 2be92f289a8a4876e310410320eedda753e19321 6546 golang-1.12_1.12.7-3_amd64.buildinfo Checksums-Sha256: c0e4528a4e9b20f90941df520d46ea6fa5508c25674aee2b97b6059a53489911 2589 golang-1.12_1.12.7-3.dsc 23ce577db700e01c50b5735fcee4b0bb86f84345c4c73c8508f4f556654d8175 36044 golang-1.12_1.12.7-3.debian.tar.xz 69222b09c4d944ce3e518c82b36cd29645933cc5cacff7baf54baadb7287c391 6546 golang-1.12_1.12.7-3_amd64.buildinfo Files: 9b8a88eb77bebd333d8780686f0441fb 2589 devel optional golang-1.12_1.12.7-3.dsc 144e0d6dc538f167de61c70f94dd315b 36044 devel optional golang-1.12_1.12.7-3.debian.tar.xz 934e81ccb619b62ad1188572bcdfb9e9 6546 devel optional golang-1.12_1.12.7-3_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEE0cuPObxd7STF0seMEwLx8Dbr6xkFAl1Iik0ACgkQEwLx8Dbr 6xnI7w/+MZluhtw6PyD9SWDQSveZr5nNxOgec4ON8z2XBUjc6NAAcMpYSw52ojFD XHjLsEom/2ZE0yARBl91tDImSfqRwilomWq/2olJD4638QiO4td4c8oNLuKJItOw K2O1YmimfYotgfhlMHKRuZO7KDro/5CRO+eBS97MZCO4PlVblL48Zp0rtuRDH9le 563AvJJ1iJZpc9hHtjDWh/zxSfuqKynbNvyu+S2rrJU0mf+uXcqVnbFb5gbEBaQS v99Lw9NJpqiFFD8BwjF9i6geYF5NFy+/csWVhCiUvqHCj4TzcOxQGaELGOGbGrjO IBCMdoOJjykK1eAW6SU7Kn5zrRIzh3E6hSQqSUbXdhls1ZppqpwhOiOl3JHIOjmZ GhEd3ohliA/gLx4MC8GVWRS7surXiR5xSzaIm9jgaYwhSf8apbwXSeBpjMvoDsqs ojFJOME+VuAsdMe1Ii4PhKabdp7F0p5H4ESgyzTVPahV2+jmHsQxFDrSCrkhvZ/4 Dz+ARMJIleZuR9LO7Vz++j/YwbJI+0oh9hQqLqswYOzP7uRJrh2Yu8qr5YFIf7qi p7GsE3Pm3nzdMMkxEDL4qUH9XJC6QRfXim5IR4esaGRHlVj2799AfhtmkCgyUZRN wu2oYq0wE2kpr/mPpeBkPZBpy2wMO8AmqEyRf2YbS/hlwDOMUJc= =eAGr -END PGP SIGNATURE End Message ---
Bug#933287: marked as done (BD on texlive-generic-extra which isn't build anymore and isn't in bullseye)
Your message dated Mon, 05 Aug 2019 22:53:25 + with message-id and subject line Bug#933287: fixed in macsyfinder 1.0.5-3 has caused the Debian Bug report #933287, regarding BD on texlive-generic-extra which isn't build anymore and isn't in bullseye 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.) -- 933287: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933287 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: breathe Version: 4.11.1-1 Severity: serious Tags: ftbfs sid bullseye Recently the texlive-base package has stopped building the transitional package texlive-generic-extra. This is an issue for your package as it build-depends on it. Please update the building of your package to use texlive-plain-generic instead. Unfortunately the migration software doesn't detected this kind of situation yet, so your package also FTBFS in bullseye since 2019-07-16. Paul signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: macsyfinder Source-Version: 1.0.5-3 We believe that the bug you reported is fixed in the latest version of macsyfinder, 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 933...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Tille (supplier of updated macsyfinder 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, 05 Aug 2019 15:35:07 +0200 Source: macsyfinder Binary: macsyfinder Architecture: source Version: 1.0.5-3 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team Changed-By: Andreas Tille Description: macsyfinder - detection of macromolecular systems in protein datasets Closes: 933287 Changes: macsyfinder (1.0.5-3) unstable; urgency=medium . * Team upload. * Build-Depends: s/texlive-generic-extra/texlive-plain-generic/ Closes: #933287 * debhelper-compat 12 * Standards-Version: 4.4.0 * Trim trailing whitespace. * buildsystem=pybuild * Build-Depends: hmmer * Fix / ignore failing tests Checksums-Sha1: e4ae801f255818dc606f51b30941f1f55a9cd267 2167 macsyfinder_1.0.5-3.dsc bcc0137c6ab52be9842e7bebbee489f49b59ba12 7548 macsyfinder_1.0.5-3.debian.tar.xz Checksums-Sha256: 6a4e415cd93447749d72792353396fcab17fdc3598a92042ad2aced782229612 2167 macsyfinder_1.0.5-3.dsc bfbc13207469ecbedb51c6a81c48332ae2bed7c63410eb77d9d1a4e0d8786ece 7548 macsyfinder_1.0.5-3.debian.tar.xz Files: aa8b305b45ca39667927f54ba064c5da 2167 science optional macsyfinder_1.0.5-3.dsc 5c869fc4bf0c7d81c982f6b1e053c596 7548 science optional macsyfinder_1.0.5-3.debian.tar.xz -BEGIN PGP SIGNATURE- iQJFBAEBCAAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAl1IMgIRHHRpbGxlQGRl Ymlhbi5vcmcACgkQV4oElNHGRtH86Q//XiQKZPPdnrVg7jB4JxIH2M7ErWI9VI8v JnJ3DR47TyUr62EpFfGL2477YAUC9S/oK0+C+WxbZH+1gLGSApQbv4pSe9XnPNjd mIgjlCTM8cY2OicoNs9R//RAMeny6bjmHCTCBagSTUGIBYatGy4Wj3sAYpvTw+9H y5yDelABoev3fq3ToAscBBxY30BD+HxdqCRJqLrPBZijcfUuH6gh9rVt8LAGJbrk WRQF0+Sz8iqnmJBG8BJxH0PQK0Wv+jfzKxqQRSYSpKkeeTOBcWGAuGW+xTPNx5uE zXDk2C81rQBEgB6bfhePJbnxJfh+0yonZ14anpU80Htwl3KoB26m1mnlBbNRJRrn GfSnZnj5LhqhtmmgCyEbpaXsuFis9129bly9NW1jGuzB+eHCQHkBwORjSD94UEqy p1OWBSRnBH2hG0BVO5/qRPKgP51hs7rVBgUdJGLuESUAFo/clEKfa1PBxpJQzWeJ VwFZEckKgPxoJdZLvcaMqnj5ZrYpvnVy6+b0EZxnYlKLV88yH8PmdkjJYfYSnpAH JUCm0xsYlg2g92GsGmRnEBD3d/GNBuCOpS15qvXVIr4K49z2tblb8XYcBmH+q4oN sj1wHrw0wPcsHou55OigOSSWSB8EHkjgG5VKi+6hLhwI/CQGiLSbkWtZUGa42YdT YcoTxYyPQJI= =DRuk -END PGP SIGNATURE End Message ---
Bug#933289: marked as done (BD on texlive-generic-extra which isn't build anymore and isn't in bullseye)
Your message dated Mon, 05 Aug 2019 23:05:37 + with message-id and subject line Bug#933289: fixed in opencolorio 1.1.1~dfsg0-3 has caused the Debian Bug report #933289, regarding BD on texlive-generic-extra which isn't build anymore and isn't in bullseye 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.) -- 933289: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933289 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: breathe Version: 4.11.1-1 Severity: serious Tags: ftbfs sid bullseye Recently the texlive-base package has stopped building the transitional package texlive-generic-extra. This is an issue for your package as it build-depends on it. Please update the building of your package to use texlive-plain-generic instead. Unfortunately the migration software doesn't detected this kind of situation yet, so your package also FTBFS in bullseye since 2019-07-16. Paul signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: opencolorio Source-Version: 1.1.1~dfsg0-3 We believe that the bug you reported is fixed in the latest version of opencolorio, 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 933...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Matteo F. Vescovi (supplier of updated opencolorio package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 05 Aug 2019 22:52:38 +0200 Source: opencolorio Architecture: source Version: 1.1.1~dfsg0-3 Distribution: unstable Urgency: medium Maintainer: Debian PhotoTools Maintainers Changed-By: Matteo F. Vescovi Closes: 933289 Changes: opencolorio (1.1.1~dfsg0-3) unstable; urgency=medium . * debian/control: - S-V bump 4.3.0 -> 4.4.0 (no changes needed) - switch to texlive-plain-generic as b-dep (Closes: #933289) Checksums-Sha1: 1ee9de04b1ce88e2e717de4d0a31867fb83ff360 2874 opencolorio_1.1.1~dfsg0-3.dsc d7ebd637106e8a7e535e48d3f5ae6cd37375656d 17336 opencolorio_1.1.1~dfsg0-3.debian.tar.xz aa6210623a112a019e54657ea2aa889f70b77588 6909 opencolorio_1.1.1~dfsg0-3_source.buildinfo Checksums-Sha256: 131bcc1732b5b8501718357b4a5f6da1f126c4f631f1ad3b62601736cb845ff4 2874 opencolorio_1.1.1~dfsg0-3.dsc 1032569c686c2367a0fa7454a48fbe53d26ce62bc99d8d719388cc8703099c2d 17336 opencolorio_1.1.1~dfsg0-3.debian.tar.xz b1db0a756e192a9f6216f9b12f46b5a947f5e40bc13ea6bcbec272c793a41851 6909 opencolorio_1.1.1~dfsg0-3_source.buildinfo Files: fd7ba551feb53843984b471715e55fd6 2874 libs optional opencolorio_1.1.1~dfsg0-3.dsc c82596ff65182e31d319e761fd4a0f3c 17336 libs optional opencolorio_1.1.1~dfsg0-3.debian.tar.xz e43f29c8c3bb63fc400ba32a6f7fd19f 6909 libs optional opencolorio_1.1.1~dfsg0-3_source.buildinfo -BEGIN PGP SIGNATURE- Comment: Debian powered! iQKTBAEBCgB9FiEE890J+NqH0d9QRsmbBhL0lE7NzVoFAl1ImKlfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEYz REQwOUY4REE4N0QxREY1MDQ2Qzk5QjA2MTJGNDk0NEVDRENENUEACgkQBhL0lE7N zVqZQA//SvyUmYEqGWEsLgYauzn/ztlmWwrSpdihLaFiGP8VMt5R9/w2AdvXnQOD QsBn8QIdtQHc4ETS7q2N01mkwjhLlYowAGsQO7V1azW734hyFA6BhBwwxRQFBzVQ ekFCNDNi31fWQcWbIhpZW1pJaCGNOVyh2tR5kRmzcUbAQusJrUeKyJBglTP65pxV JK1JOEd23jzGzvx6/dFV3ZlQCitTPwGJ1HhXSxrmZI7fhtTb1W5MUPWutjI7TBRC NOGGNQDtJlSf8KtVjCy3pVgT31pj8DPKkPikvVswVhINNDxdXsgSrllLgQDDFDsu gC+6Xk7uMqHpbesihiCXDOAf0LNwZNexKgEd8MAIfPVXDbtHEJornGZYsZF+lhJz GodgWWMn3rk6WxZzmFEDX47qCrjUUe+BGtsHvqf4O/eWbxXor3cA9PLAmy8GHnb3 VXE7Z7in1zgZTpjD6SWamDyU6bzmKR2eYs44mglev9iL7HzulvRL2TGiyYrabPyP B5Aai/h1taC1DUOhdOw68JNG81k4qU5Qxo3ayOXzDZsCxsuC+8f2DBViLRd4QEik 0fQbtkTBcT1qpOdpnO9qfD9ovBawVbouZEF1u/HkZKw91ia6t4IcaKe64NVjKXT5 YhqcrN1N8yj8Hlr+EIAnJRIaSNafX376uuWUMQQfbmtZkkPx0k4= =gm84 -END PGP SIGNATURE End Message ---
Bug#933920: marked as done (src:python-markdown: Unsafe use of yaml.load())
Your message dated Mon, 05 Aug 2019 23:13:43 + with message-id and subject line Bug#933920: fixed in python-markdown 3.1.1-2 has caused the Debian Bug report #933920, regarding src:python-markdown: Unsafe use of yaml.load() 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.) -- 933920: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933920 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:python-markdown Version: 3.0.1-3 Severity: grave Tags: security Justification: user security hole The new version of pyyaml no longer allows use of yaml.load() without a loader being specifed. This raises a deprecation warning which has caused and autopkgtest failure on this package. These are generally trivial to fix, see the upstream guidance [1]. Scott K [1] https://github.com/yaml/pyyaml/wiki/PyYAML-yaml.load(input)-Deprecation --- End Message --- --- Begin Message --- Source: python-markdown Source-Version: 3.1.1-2 We believe that the bug you reported is fixed in the latest version of python-markdown, 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 933...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Dmitry Shachnev (supplier of updated python-markdown package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 05 Aug 2019 22:03:47 +0300 Source: python-markdown Architecture: source Version: 3.1.1-2 Distribution: unstable Urgency: medium Maintainer: Debian Python Modules Team Changed-By: Dmitry Shachnev Closes: 933920 Changes: python-markdown (3.1.1-2) unstable; urgency=medium . * Upload to unstable. - The 3.1 release is compatible with PyYaml 5.1 (closes: #933920). . [ Ondřej Nový ] * Bump Standards-Version to 4.4.0. Checksums-Sha1: 0c3939e523f5d3630a1f029b8cc3cfbd860bf816 2673 python-markdown_3.1.1-2.dsc 38db3be0366fdcd952abca9d2b88ae68f49f2622 8628 python-markdown_3.1.1-2.debian.tar.xz c577e6e1995c160562c2aec5c7ebee4e091bb136 7936 python-markdown_3.1.1-2_source.buildinfo Checksums-Sha256: c630757c569a32e9a97124453f4d610276d0a642b140e52f0ec4cc37cb09d44b 2673 python-markdown_3.1.1-2.dsc 6fcc715a967f5e9c437648a54f3e167805539749f56f0b9423f847d73bb0e572 8628 python-markdown_3.1.1-2.debian.tar.xz a6b9c59bbd6ed9a96e446abca0a606c50790846861fee6f0a7054d3720ada7e3 7936 python-markdown_3.1.1-2_source.buildinfo Files: 21725a953e0764920227a7a0f9884f8f 2673 python optional python-markdown_3.1.1-2.dsc c805dc9eec47ad4aba940a28a57b5cfc 8628 python optional python-markdown_3.1.1-2.debian.tar.xz a4f85126236abd1e87195fa0a6ff66d5 7936 python optional python-markdown_3.1.1-2_source.buildinfo -BEGIN PGP SIGNATURE- iQJHBAEBCgAxFiEE8kKZ/xu8kBi5BqTLYCaTbS8ciuAFAl1IgD4THG1pdHlhNTdA ZGViaWFuLm9yZwAKCRBgJpNtLxyK4GNyD/9jlvtJPDdW748oe68v7W8fi5PwNIc/ XuCFAbTUyqMRURjhMKg30PShjC5O+M2lxfVIGNyNVbmtQ5/HApw1F1oNs4wfeMWz EmEwjp8s3UQvCY0iajKZeB2/MJ2ysx0LMp4x+CiTS+nlYng/R9TL4vcksDNUUYLs /Icf0PKAXdQnzrYirIKD9Q5blQk7zsGzWI88nhTiQolSQSDdTY/f/Yd5r1VAVNpp 7hYcV8oYl2yA1vrg5sB4Pp8v3R2xBVmDZOQRw2/IwzCt92mEkXHhdZ82eHtQXfeF yXYZKWBNP8LvVk5bjlKkFs+eVl7HXhfEQ4ntsDvL1uQWyes/dl9+K8OlpwsG5xt8 /ojRWtW8ocaZz9v91IWM/B0U75Ky78sCANxBkPZmkcuwwkQC3+2OILsBe1IvGJfw a2m8KBo8et2YLfR0CGVpkX/hI8DupsrPD9Mn3lXvzoSKxnQdnBi7Gh3n/YtIpZhj a3d3dLVdvJ+fWbOQ+zEJgQ2N9WWXLNqEyHIFT7LNicpMZK75Pi0ZUYYNbEhVbn53 TzjeW+NL91qR6X5Q9PKf1mvPRKtrtFRVN3sNJn+vd1QKYu00tYJFWpZcMdD8xhwa KQJbqiPxjlVDeP0585y+74EGvT5Wd5CF7Cw+NEi51HxoPTwJerXNvzGXOFI6jqy4 F35+UNV1+LjPWA== =Hbfa -END PGP SIGNATURE End Message ---
Bug#892620: marked as done (pytest-bdd FTBFS with pytest 3.3.2-2)
Your message dated Mon, 05 Aug 2019 23:13:17 +
with message-id
and subject line Bug#892620: fixed in pytest-bdd 3.1.1-1
has caused the Debian Bug report #892620,
regarding pytest-bdd FTBFS with pytest 3.3.2-2
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
892620: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892620
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pytest-bdd
Version: 2.18.2-1
Severity: serious
Tags: fixed-upstream
Forwarded: https://github.com/pytest-dev/pytest-bdd/pull/232
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/pytest-bdd.html
...
== 25 failed, 125 passed, 2 warnings in 55.41 seconds ==
E: pybuild pybuild:283: test: plugin custom failed with: exit code=1: python2.7
-m pytest
dh_auto_test: pybuild --test --test-pytest -i python{version} -p 2.7
--system=custom "--test-args={interpreter} -m pytest" returned exit code 13
make[1]: *** [debian/rules:10: override_dh_auto_test] Error 25
--- End Message ---
--- Begin Message ---
Source: pytest-bdd
Source-Version: 3.1.1-1
We believe that the bug you reported is fixed in the latest version of
pytest-bdd, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 892...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Scott Talbert (supplier of updated pytest-bdd package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Fri, 26 Jul 2019 21:54:38 -0400
Source: pytest-bdd
Architecture: source
Version: 3.1.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team
Changed-By: Scott Talbert
Closes: 892620
Changes:
pytest-bdd (3.1.1-1) unstable; urgency=medium
.
* Team upload.
.
[ Scott Talbert ]
* Update to new upstream release 3.1.1 (Closes: #892620)
* d/control: Update Standards Version to 4.4.0
* d/control: Update debhelper compat version to 12
* Remove Python 2 subpackage
* d/control: Fix capitalization in description
* d/control: Remove unnecessary period in description
.
[ Ondřej Nový ]
* d/control: Set Vcs-* to salsa.debian.org
* d/copyright: Fix Format URL to correct one
* Use debhelper-compat instead of debian/compat.
.
[ Mattia Rizzolo ]
* Run wrap-and-sort.
Checksums-Sha1:
70371a0447d3b5daf8b37027680d14bac2647573 2155 pytest-bdd_3.1.1-1.dsc
65d37c2f92be7be9ba7f44d38b9577c6be5b5e29 63696 pytest-bdd_3.1.1.orig.tar.gz
7bf6afb3cfe052cb9a903df28ade597a0e986396 2460 pytest-bdd_3.1.1-1.debian.tar.xz
eb4174981ff7115dda8e11475a73095e75f62a58 6686
pytest-bdd_3.1.1-1_amd64.buildinfo
Checksums-Sha256:
737313e6076d6aecaf78f792512efa467063d7b450673b29c2b8474b61e7535e 2155
pytest-bdd_3.1.1-1.dsc
764874d712d2d7ab07df47d81b47d23a077f81ed1fd54ef1fe6b7e03893b318e 63696
pytest-bdd_3.1.1.orig.tar.gz
e6d454457643afd321de87baa98da5c1fd45b6f7682171bbb5714223442f0714 2460
pytest-bdd_3.1.1-1.debian.tar.xz
1e57a583ebe697d7027f6b62dbcc91f37f77dd31e02ae573cac1d345f55cdd99 6686
pytest-bdd_3.1.1-1_amd64.buildinfo
Files:
48a9ce6ed74c72ad388626e447d3bd00 2155 python optional pytest-bdd_3.1.1-1.dsc
d4976a67efafb5cc98fb351e8d32987e 63696 python optional
pytest-bdd_3.1.1.orig.tar.gz
c8ce23a65128f2274fe45b7e698afcf8 2460 python optional
pytest-bdd_3.1.1-1.debian.tar.xz
820512af7e3164929794d2fc2ae1a94b 6686 python optional
pytest-bdd_3.1.1-1_amd64.buildinfo
-BEGIN PGP SIGNATURE-
iQIzBAEBCgAdFiEEi3hoeGwz5cZMTQpICBa54Yx2K60FAl1II7AACgkQCBa54Yx2
K624yBAAi6LgHZQq1OlBblfQ9tQifnsbzT/9wWSPGqQox0ozoSqgSQ9m5AMrQEMO
WMlW5qfIiKwb0WO+U0XTIOGJd6QN0Yql5xXE9HeJD/U44YzVfIJ5ZTpdmA036ZOD
X+vB7X226BWAJVIfnsr2LKSmfcoS2DsOPq2UMsj8Vlty7Lu6CyWS3ox9BIaKOPS2
mf8pGep3fa+VwrwhcZq/bktPEK4GK6q83ViR4lKIQVCHD4HSrr0PEtnAAOIbIbEH
kfH1mf+mfrZvdcVyG7xp5my/7s2KVd7khkDKJqk5IGmHCouMmV2ZFTTHH2JzmtgM
y3LOX6I9mWTS8fHeL0P1DLLxE3YmGtu6cJHlNbjLpDlH/6BkB/tYBZRUHU2IlVHI
XjgJngkkK+7rmN2lB2HtAi/hLLVY7QUsJei8MgqdO+oo88fHkPWwmCD3uhDB4e/W
BkQvwl8NwLMvAdR4tNbSHzgJkKghRIOsfgtU9uQP19va5VXx1FRE5Md8LIEv5lSh
gaK6iMFugy777DrxOUqtUYa8/RpYwCcsOwDH6nVq5Nf/09msARb51qBJ8dcWDpko
pGilXqwIL/Q9TMw+4/gTmDqZDDmX+OjYtOPDbF+jIs96xr3gMcdDMoC+tvVrrxHM
tD70GpRlCMgmF4zZixy89W9dt8w8BHTfqY+
Bug#933667: sagemath: FTBFS in sid
Build log from https://launchpad.net/ubuntu/+source/sagemath/8.6-6build1/+build/17348800 shows SIGSEGV in sage.libs.gap.util.initialize. That makes this a duplicate of https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932367 I believe. Merge?
Bug#933921: src:python-tablib: Unsafe use of yaml.load()
Hi, Thanks Scott for the report. Tomas: the repository in Openstack was archived long ago because it was ported to https://salsa.debian.org/python-team/modules/python-tablib The module is used by other packages than openstack (like django-tables if I remember correctly), so could you please hold off the removal request please? If the repo in the openstack group bother you, you can drop it but please don't drop tablib (at least not the python3 version). Thanks, Joseph
Bug#932598: Upgrade to buster fails with start-stop-daemon error
On 7/30/19 4:14 PM, Andreas Beckmann wrote: > Hi Ron, > > On 21/07/2019 05.42, Ron Murray wrote: >> On upgrade to buster, sendmail upgrade failed with this message: >> >>> start-stop-daemon: matching only on non-root pidfile >>> /var/run/sendmail/mta/sendmail.pid is insecure >> Some work with Google found Debian bug #922395, which, although not >> for sendmail, pointed the way to the solution. > I've just uploaded sendmail 8.15.2-13 to unstable, it would be great if > you could test this s.t. I have a datapoint whether this fix should be > applied to buster, too. > > Thanks > > Andreas Thanks for the update. The same problem occurred when I upgraded to 8.15.2-13 on my two testing (bullseye) boxes. Deleting the /var/run/sendmail/mta/sendmail.pid file and re-running aptitude fixed it. Sadly, I wasn't smart enough to get the details on the file before I deleted it. I'm not even certain why it was there: I would have thought that shutting down sendmail before the upgrade should have deleted it. Perhaps this was the problem all along. After getting sendmail started, the file looks like this: > -rw-r- 1 root smmta 53 Aug 5 22:14 sendmail.pid Thanks, ,Ron -- Ron Murray PGP Fingerprint: 4D99 70E3 2317 334B 141E 7B63 12F7 E865 B5E2 E761 signature.asc Description: OpenPGP digital signature
Bug#933268: marked as done (Failures during upgrade, rpcbind.socket fails to (re)start)
Your message dated Tue, 06 Aug 2019 02:46:53 + with message-id and subject line Bug#933268: fixed in rpcbind 1.2.5-5 has caused the Debian Bug report #933268, regarding Failures during upgrade, rpcbind.socket fails to (re)start 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.) -- 933268: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933268 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: rpcbind Version: 1.2.5-4 Severity: serious Hi, during an upgrade from -3 to -4, I got the following failure (sorry for the German locale) rpcbind (1.2.5-4) wird eingerichtet ... Neue Version der Konfigurationsdatei /etc/init.d/rpcbind wird installiert ... Job for rpcbind.socket failed. See "systemctl status rpcbind.socket" and "journalctl -xe" for details. A dependency job for rpcbind.service failed. See 'journalctl -xe' for details. After that, I get: # systemctl status rpcbind.socket ● rpcbind.socket - RPCbind Server Activation Socket Loaded: loaded (/lib/systemd/system/rpcbind.socket; enabled; vendor preset: enabled) Active: inactive (dead) since Sun 2019-07-28 14:31:17 CEST; 3min 28s ago Listen: /run/rpcbind.sock (Stream) 0.0.0.0:111 (Stream) 0.0.0.0:111 (Datagram) [::]:111 (Stream) [::]:111 (Datagram) Jul 28 14:31:17 pluto systemd[1]: rpcbind.socket: Succeeded. Jul 28 14:31:17 pluto systemd[1]: Closed RPCbind Server Activation Socket. Jul 28 14:31:17 pluto systemd[1]: Stopping RPCbind Server Activation Socket. Jul 28 14:31:17 pluto systemd[1]: rpcbind.socket: Socket service rpcbind.service already active, refusing. Jul 28 14:31:17 pluto systemd[1]: Failed to listen on RPCbind Server Activation Socket. -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (200, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-5-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages rpcbind depends on: ii adduser 3.118 ii init-system-helpers 1.57 ii libc62.28-10 ii libsystemd0 241-7 ii libtirpc31.1.4-0.4 ii libwrap0 7.6.q-28 ii lsb-base 10.2019051400 rpcbind recommends no packages. rpcbind suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: rpcbind Source-Version: 1.2.5-5 We believe that the bug you reported is fixed in the latest version of rpcbind, 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 933...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Josue Ortega (supplier of updated rpcbind 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, 05 Aug 2019 19:31:11 -0600 Source: rpcbind Architecture: source Version: 1.2.5-5 Distribution: unstable Urgency: medium Maintainer: Josue Ortega Changed-By: Josue Ortega Closes: 933268 Changes: rpcbind (1.2.5-5) unstable; urgency=medium . * debian/rules: Add --no-restart-after-upgrade option to dh_installsystemd to avoid race condition at rpcbind.socket initialization (Closes: #933268) Checksums-Sha1: 7954b8fd9e592a415ce27838cc7fa5e01dc30637 1923 rpcbind_1.2.5-5.dsc 20af645f623ff7778e1887ee5b6f344ba43c2ee6 10972 rpcbind_1.2.5-5.debian.tar.xz bb001f1a1e388e323877185c8aa95022e76917a8 6207 rpcbind_1.2.5-5_amd64.buildinfo Checksums-Sha256: cf4c1f770518cbd460d1250ddd12a54f14c4f6df9b601a280851429b50d27ca7 1923 rpcbind_1.2.5-5.dsc cb1d5d99a1bb2d28c61902100e4a3704e82a9c94a614db478bd6f4630f3c6196 10972 rpcbind_1.2.5-5.debian.tar.xz 16c15c73ca56fb041841040a151b17c334bf5b7c61d2d18f6dbf33c82fc9e873 6207 rpcbind_1.2.5-5_amd64.buildinfo Files: 1ea5e97062af3f8f15fc2b8de9cecad2 1923 net optional rpcbind_1.2.5-5.dsc 3d9d3e26f0044a9d04c439c56e54606e 10972 net optional rpcbind_1.2.5-5.debian.tar.xz d4979a6c15b121dde301744c21bb4afe 6207 net optional rpcbind_1.2.5-5_amd64.buildinf
Bug#934013: boost-defaults: Boost license file is not found
Source: boost-defaults Version: 1.67.0.1 Severity: serious Justification: Policy 4.5 -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear Maintainer, Every boost packages, libboost*, contains debian/copyright file which says: ``` copyright & license for Boost-Defaults for Debian. The license for Boost itself may be found in file /usr/share/doc/libboost-doc/HTML/LICENSE_1_0.txt ``` However, even if I installed libboost-doc package, the above path does not exist at all. I cannot find the license for Boost itself. I believe that the license for Boost itself should also be available when only one e.g. libboost-test1.67 package is installed. P.S. I know that The license for the original Boost is the same as the license for Boost-Defaults for Debian so that editing the wording might be enough. Best regards, - -- Ryo IGARASHI, Ph.D. rigar...@gmail.com - -- System Information: Debian Release: 10.0 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.4.0-17763-Microsoft Locale: LANG=ja_JP.UTF-8, LC_CTYPE=ja_JP.UTF-8 (charmap=UTF-8), LANGUAGE=ja_JP.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: unable to detect -BEGIN PGP SIGNATURE- iIkEARYKADEWIQSQVQWnJ6dEuIxNmESAtgFFC/hXNwUCXUj3WBMccmlnYXJhc2hA Z21haWwuY29tAAoJEIC2AUUL+Fc35goA/1QXwA5BjOmWINst3Izx7Gv7k4KcTB/6 hR5Kqd3SiIS4AP9UjY3TWHdGVXZmDdk/5ZvD0s/kLMrdLBvvuolyxe44Dg== =7nMT -END PGP SIGNATURE-
Bug#933921: marked as done (src:python-tablib: Unsafe use of yaml.load())
Your message dated Tue, 06 Aug 2019 00:12:30 -0400 with message-id <2807841.dfmYRgPtWv@l5580> and subject line Re: src:python-tablib: Unsafe use of yaml.load() has caused the Debian Bug report #933921, regarding src:python-tablib: Unsafe use of yaml.load() 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.) -- 933921: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933921 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:python-tablib Version: 0.12.1-2 Severity: grave Tags: security Justification: user security hole The new version of pyyaml no longer allows use of yaml.load() without a loader being specifed. This raises a deprecation warning which has caused and autopkgtest failure on this package. These are generally trivial to fix, see the upstream guidance [1]. Scott K [1] https://github.com/yaml/pyyaml/wiki/PyYAML-yaml.load(input)-Deprecation --- End Message --- --- Begin Message --- I investigated this some more and tablib uses safe load, the problem is something else. It fails with both pyyaml 3.13 and 5.1.2. I also checked and it has no rdepends. It seems buggy, so unless someone really wants to take over maintenance, rm is probably best. Scott K--- End Message ---
Bug#898406: marked as done (flif: CVE-2018-10971)
Your message dated Tue, 6 Aug 2019 07:06:57 +0200 with message-id <227ae243-9c22-6af2-8db3-bfa35489e...@debian.org> and subject line Removed package(s) from experimental has caused the Debian Bug report #898406, regarding flif: CVE-2018-10971 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.) -- 898406: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898406 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: flif Version: 0.3-1 Severity: important Tags: security upstream Forwarded: https://github.com/FLIF-hub/FLIF/issues/501 Hi, The following vulnerability was published for flif. CVE-2018-10971[0]: | An issue was discovered in Free Lossless Image Format (FLIF) 0.3. The | Plane function in image/image.hpp allows remote attackers to cause a | denial of service (attempted excessive memory allocation) via a crafted | file. If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2018-10971 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-10971 [1] https://github.com/FLIF-hub/FLIF/issues/501 Regards, Salvatore --- End Message --- --- Begin Message --- Version: 0.3-7+rm Dear submitter, as the package flif has just been removed from the Debian archive experimental we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/933898 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#898407: marked as done (flif: CVE-2018-10972)
Your message dated Tue, 6 Aug 2019 07:06:57 +0200 with message-id <227ae243-9c22-6af2-8db3-bfa35489e...@debian.org> and subject line Removed package(s) from experimental has caused the Debian Bug report #898407, regarding flif: CVE-2018-10972 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.) -- 898407: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898407 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: flif Version: 0.3-1 Severity: important Tags: security upstream Forwarded: https://github.com/FLIF-hub/FLIF/issues/503 Hi, The following vulnerability was published for flif. CVE-2018-10972[0]: | An issue was discovered in Free Lossless Image Format (FLIF) 0.3. The | TransformPaletteC::process function in transform/palette_C.hpp allows | remote attackers to cause a denial of service (heap-based buffer | overflow) or possibly have unspecified other impact via a crafted file. If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2018-10972 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-10972 [1] https://github.com/FLIF-hub/FLIF/issues/503 Regards, Salvatore --- End Message --- --- Begin Message --- Version: 0.3-7+rm Dear submitter, as the package flif has just been removed from the Debian archive experimental we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/933898 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Processed: severity of 933254 is normal
Processing commands for cont...@bugs.debian.org:
> severity 933254 normal
Bug #933254 {Done: Xavier } [pkg-js-tools] Auto detection of
components is broken when used in webpack
Severity set to 'normal' from 'grave'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
933254: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933254
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: notfound 933254 in 0.5
Processing commands for cont...@bugs.debian.org:
> notfound 933254 0.5
Bug #933254 {Done: Xavier } [pkg-js-tools] Auto detection of
components is broken when used in webpack
Ignoring request to alter found versions of bug #933254 to the same values
previously set
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
933254: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933254
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#934014: python3-demjson: missing Breaks+Replaces: python-demjson
Package: python3-demjson Version: 2.2.4-3 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'testing'. It installed fine in 'testing', then the upgrade to 'sid' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces >From the attached log (scroll to the bottom...): Selecting previously unselected package python3-demjson. Preparing to unpack .../python3-demjson_2.2.4-3_all.deb ... Unpacking python3-demjson (2.2.4-3) ... dpkg: error processing archive /var/cache/apt/archives/python3-demjson_2.2.4-3_all.deb (--unpack): trying to overwrite '/usr/share/man/man1/jsonlint.1.gz', which is also in package python-demjson 2.2.4-2 Errors were encountered while processing: /var/cache/apt/archives/python3-demjson_2.2.4-3_all.deb cheers, Andreas python-demjson=2.2.4-2_python3-demjson=2.2.4-3.log.gz Description: application/gzip
Bug#866371: marked as done (FP register corruption on ppc64el with lock elision)
rnelnewbies.org/Linux_5.2 . * New upstream stable update: https://www.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.2.1 https://www.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.2.2 https://www.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.2.3 https://www.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.2.4 https://www.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.2.5 https://www.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.2.6 . [ Bastian Germann ] * [armhf] Enable C_CAN as a module. (Closes: #929968) . [ Ben Hutchings ] * Drop "x86/boot: Add ACPI RSDP address to setup_header", which should not have been applied to 4.20 or later * Drop redundant part of "Install perf scripts non-executable" * Drop "kbuild: Use -nostdinc in compile tests", which is no longer needed * debian/rules.d/scripts/kconfig: Update for upstream file renaming * debian/rules.d/scripts/mod: Add uuid_t and UUID_STRING_LEN definitions * liblockdep: Disable until it can be built again * libcpupower: Bump soversion since 2 exported functions have been removed * libbpf: Stop overriding upstream soname; rename shlib package to libbpf0 * vfs: Enable FS_ENCRYPTION as built-in; disable on armel/marvell * net: Enable NET_DEVLINK as built-in; disable on armel/marvell * aufs: Update support patchset to aufs5.2 20190805 * lockdown: Update for 5.2: - Update "acpi: Ignore acpi_rsdp kernel param when the kernel ..." - Add "tracefs: Restrict tracefs when the kernel is locked down" - Add "efi: Restrict efivar_ssdt_load when the kernel is locked down" - Drop "MODSIGN: Import certificates from UEFI Secure Boot" * [rt] Rebase onto 5.2.6, and re-enable * [armhf,arm64] gpu: Enable DRM_LIMA, DRM_PANFROST as modules * sched: Enable PSI (Closes: #931247) * [armhf,arm64] power: Enable ENERGY_MODEL * [armhf,arm64] cpufreq: Enable CPU_FREQ_DEFAULT_GOV_SCHEDUTIL (instead of CPU_FREQ_DEFAULT_GOV_PERFORMANCE) * hamradio: Disable auto-loading as mitigation against local exploits * hamradio: Enable most options in top-level config: - [arm64,ia64,mips*,riscv64,s390x,sh4,sparc64] Enable AX25, NETROM, ROSE, and all possible drivers (Closes: #920651) - [alpha,amd64,armel] ax25: Enable AX25_DAMA_SLAVE - [armhf] Enable BPQETHER, BAYCOM_SER_FDX, BAYCOM_SER_HDX, BAYCOM_PAR, BAYCOM_EPP, YAM as modules * [armel/rpi,armhf] media: Enable VIDEO_BCM2835 as module * usb/typec: Enable TYPEC_DP_ALTMODE, TYPEC_NVIDIA_ALTMODE as modules (Closes: #931752) * [amd64/cloud-amd64] hwrandom: Enable HW_RANDOM_VIRTIO (Closes: #914511) * [ppc64*] crypto: Enable CRYPTO_DEV_NX, and CRYPTO_DEV_NX_ENCRYPT, CRYPTO_DEV_NX_COMPRESS, CRYPTO_DEV_NX_COMPRESS_PSERIES, CRYPTO_DEV_NX_COMPRESS_POWERNV as modules (Closes: #931374) * [ppc64*] Disable PPC_TRANSACTIONAL_MEM (Closes: #866122) . [ Vagrant Cascadian ] * [arm64] Enable modules to support audio on pinebook: SND_SUN4I_I2S, SND_SUN8I_CODEC, SND_SUN50I_CODEC_ANALOG, SND_SIMPLE_CARD, SND_SOC_SIMPLE_AMPLIFIER. (Closes: #921019) . [ Romain Perier ] * Refreshed patches: - debian/revert-objtool-fix-config_stack_validation-y-warning.patch - debian/dfsg/video-remove-nvidiafb-and-rivafb.patch - debian/gitignore.patch - debian/mips-disable-werror.patch - bugfix/all/firmware-remove-redundant-log-messages-from-drivers.patch - bugfix/arm/arm-mm-export-__sync_icache_dcache-for-xen-privcmd.patch - bugfix/powerpc/powerpc-lib-makefile-don-t-pull-in-quad.o-for-32-bit.patch - bugfix/all/ radeon-amdgpu-firmware-is-required-for-drm-and-kms-on-r600-onward.patch - bugfix/all/disable-some-marvell-phys.patch - debian/overlayfs-permit-mounts-in-userns.patch - bugfix/all/tools-perf-remove-shebangs.patch - debian/ntfs-mark-it-as-broken.patch - features/all/db-mok-keyring/ 0003-MODSIGN-checking-the-blacklisted-hash-before-loading-a-kernel-module.patch - features/all/db-mok-keyring/ 0004-MODSIGN-Import-certificates-from-UEFI-Secure-Boot.patch - debian/android-enable-building-ashmem-and-binder-as-modules.patch - features/all/aufs5/aufs5-mmap.patch - features/all/aufs5/aufs5-standalone.patch - features/all/lockdown/ 0029-efi-Lock-down-the-kernel-if-booted-in-secure-boot-mo.patch * Enable coreboot memconsole (Closes: #872069) * [rt] Update to 5.2-rt1 . [ Karsten Merker ] * [riscv64] Change the kernel image format from ELF to flat Image. (Closes: #928451) * [riscv64] Update config and image format (Closes: #933603): - Enable SiFive UART and UART console support - Enable clock drivers for the SiFive FU540 - Backport kernel image header support from kernel 5.3 . [ Uwe Kleine-König ] * [armhf] Add support for all i.MX6 variants. * enable XFRM_STATISTICS (Closes: #929938
Bug#866122: marked as done (FP register corruption on ppc64el with lock elision)
s://kernelnewbies.org/Linux_5.1 https://kernelnewbies.org/Linux_5.2 . * New upstream stable update: https://www.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.2.1 https://www.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.2.2 https://www.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.2.3 https://www.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.2.4 https://www.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.2.5 https://www.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.2.6 . [ Bastian Germann ] * [armhf] Enable C_CAN as a module. (Closes: #929968) . [ Ben Hutchings ] * Drop "x86/boot: Add ACPI RSDP address to setup_header", which should not have been applied to 4.20 or later * Drop redundant part of "Install perf scripts non-executable" * Drop "kbuild: Use -nostdinc in compile tests", which is no longer needed * debian/rules.d/scripts/kconfig: Update for upstream file renaming * debian/rules.d/scripts/mod: Add uuid_t and UUID_STRING_LEN definitions * liblockdep: Disable until it can be built again * libcpupower: Bump soversion since 2 exported functions have been removed * libbpf: Stop overriding upstream soname; rename shlib package to libbpf0 * vfs: Enable FS_ENCRYPTION as built-in; disable on armel/marvell * net: Enable NET_DEVLINK as built-in; disable on armel/marvell * aufs: Update support patchset to aufs5.2 20190805 * lockdown: Update for 5.2: - Update "acpi: Ignore acpi_rsdp kernel param when the kernel ..." - Add "tracefs: Restrict tracefs when the kernel is locked down" - Add "efi: Restrict efivar_ssdt_load when the kernel is locked down" - Drop "MODSIGN: Import certificates from UEFI Secure Boot" * [rt] Rebase onto 5.2.6, and re-enable * [armhf,arm64] gpu: Enable DRM_LIMA, DRM_PANFROST as modules * sched: Enable PSI (Closes: #931247) * [armhf,arm64] power: Enable ENERGY_MODEL * [armhf,arm64] cpufreq: Enable CPU_FREQ_DEFAULT_GOV_SCHEDUTIL (instead of CPU_FREQ_DEFAULT_GOV_PERFORMANCE) * hamradio: Disable auto-loading as mitigation against local exploits * hamradio: Enable most options in top-level config: - [arm64,ia64,mips*,riscv64,s390x,sh4,sparc64] Enable AX25, NETROM, ROSE, and all possible drivers (Closes: #920651) - [alpha,amd64,armel] ax25: Enable AX25_DAMA_SLAVE - [armhf] Enable BPQETHER, BAYCOM_SER_FDX, BAYCOM_SER_HDX, BAYCOM_PAR, BAYCOM_EPP, YAM as modules * [armel/rpi,armhf] media: Enable VIDEO_BCM2835 as module * usb/typec: Enable TYPEC_DP_ALTMODE, TYPEC_NVIDIA_ALTMODE as modules (Closes: #931752) * [amd64/cloud-amd64] hwrandom: Enable HW_RANDOM_VIRTIO (Closes: #914511) * [ppc64*] crypto: Enable CRYPTO_DEV_NX, and CRYPTO_DEV_NX_ENCRYPT, CRYPTO_DEV_NX_COMPRESS, CRYPTO_DEV_NX_COMPRESS_PSERIES, CRYPTO_DEV_NX_COMPRESS_POWERNV as modules (Closes: #931374) * [ppc64*] Disable PPC_TRANSACTIONAL_MEM (Closes: #866122) . [ Vagrant Cascadian ] * [arm64] Enable modules to support audio on pinebook: SND_SUN4I_I2S, SND_SUN8I_CODEC, SND_SUN50I_CODEC_ANALOG, SND_SIMPLE_CARD, SND_SOC_SIMPLE_AMPLIFIER. (Closes: #921019) . [ Romain Perier ] * Refreshed patches: - debian/revert-objtool-fix-config_stack_validation-y-warning.patch - debian/dfsg/video-remove-nvidiafb-and-rivafb.patch - debian/gitignore.patch - debian/mips-disable-werror.patch - bugfix/all/firmware-remove-redundant-log-messages-from-drivers.patch - bugfix/arm/arm-mm-export-__sync_icache_dcache-for-xen-privcmd.patch - bugfix/powerpc/powerpc-lib-makefile-don-t-pull-in-quad.o-for-32-bit.patch - bugfix/all/ radeon-amdgpu-firmware-is-required-for-drm-and-kms-on-r600-onward.patch - bugfix/all/disable-some-marvell-phys.patch - debian/overlayfs-permit-mounts-in-userns.patch - bugfix/all/tools-perf-remove-shebangs.patch - debian/ntfs-mark-it-as-broken.patch - features/all/db-mok-keyring/ 0003-MODSIGN-checking-the-blacklisted-hash-before-loading-a-kernel-module.patch - features/all/db-mok-keyring/ 0004-MODSIGN-Import-certificates-from-UEFI-Secure-Boot.patch - debian/android-enable-building-ashmem-and-binder-as-modules.patch - features/all/aufs5/aufs5-mmap.patch - features/all/aufs5/aufs5-standalone.patch - features/all/lockdown/ 0029-efi-Lock-down-the-kernel-if-booted-in-secure-boot-mo.patch * Enable coreboot memconsole (Closes: #872069) * [rt] Update to 5.2-rt1 . [ Karsten Merker ] * [riscv64] Change the kernel image format from ELF to flat Image. (Closes: #928451) * [riscv64] Update config and image format (Closes: #933603): - Enable SiFive UART and UART console support - Enable clock drivers for the SiFive FU540 - Backport kernel image header support from kernel 5.3 . [ Uwe Kleine-König ] * [armhf] Add support
Bug#934016: clangd-8: missing Breaks+Replaces: clang-tools-8 (<< 1:8.0.1)
Package: clangd-8 Version: 1:8.0.1-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'testing'. It installed fine in 'testing', then the upgrade to 'sid' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces >From the attached log (scroll to the bottom...): Preparing to unpack .../clangd-8_1%3a8.0.1-1_amd64.deb ... Unpacking clangd-8 (1:8.0.1-1) ... dpkg: error processing archive /var/cache/apt/archives/clangd-8_1%3a8.0.1-1_amd64.deb (--unpack): trying to overwrite '/usr/lib/llvm-8/bin/clangd', which is also in package clang-tools-8 1:8.0.1~+rc4-1 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/clangd-8_1%3a8.0.1-1_amd64.deb cheers, Andreas clang-tools-8=1:8.0.1~+rc4-1_clangd-8=1:8.0.1-1.log.gz Description: application/gzip
Bug#908678: Update on the security-tracker git discussion
Moin On Tue, Jul 02, 2019 at 01:38:10PM +0200, Moritz Muehlenhoff wrote: > On Tue, Jul 02, 2019 at 01:25:43PM +0200, Salvatore Bonaccorso wrote: > > p.s.: Question is if we should do a split as well for the other types of > > files which are supported (DSA, TDSA, ...) while at it. > We can axe out DTSA/* while we're at it. > For DSA/list (and DLA/list) we can initially keep it as a single file, it can > still be split later on if necessary. Following up to | Please provide a plan how and when to fix this before 2019-06-30. We have now one month later. Please provide the plan. Bastian -- We do not colonize. We conquer. We rule. There is no other way for us. -- Rojan, "By Any Other Name", stardate 4657.5
Processed: Bug#933731 marked as pending in audacity
Processing control commands: > tag -1 pending Bug #933731 [audacity] audacity: FTBFS on 32-bit arches (except i386) Added tag(s) pending. -- 933731: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933731 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#933731: marked as pending in audacity
Control: tag -1 pending Hello, Bug #933731 in audacity 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/multimedia-team/audacity/commit/600d50b2ee5f0c0b31aa72c456b8bde4259776dd d/p/0006-Link-atomic-if-needed.patch: Link atomic if needed. Closes: #933731 (this message was generated automatically) -- Greetings https://bugs.debian.org/933731
Bug#908678: Update on the security-tracker git discussion
Hi Bastian, Thanks for keeping track and following up. On Tue, Aug 06, 2019 at 08:05:11AM +0200, Bastian Blank wrote: > Moin > > On Tue, Jul 02, 2019 at 01:38:10PM +0200, Moritz Muehlenhoff wrote: > > On Tue, Jul 02, 2019 at 01:25:43PM +0200, Salvatore Bonaccorso wrote: > > > p.s.: Question is if we should do a split as well for the other types of > > > files which are supported (DSA, TDSA, ...) while at it. > > We can axe out DTSA/* while we're at it. > > For DSA/list (and DLA/list) we can initially keep it as a single file, it > > can > > still be split later on if necessary. > > Following up to > > | Please provide a plan how and when to fix this before 2019-06-30. > > We have now one month later. Please provide the plan. The items in https://salsa.debian.org/security-tracker-team/security-tracker-service/issues/1 needs further detailed and then sorted/prioritized. Later actual implementation work on making the split possible on tracker and other tooling side needs to happen. We cannot depend on a non-functional instance for the day to day work, so all of the above basically will need to be ported in some sensible way. Progress is slow due to other time limitations in day to day tasks. Still if it is going to be too much burden for salsa admin and needs to be fast, then I only see that we temporarily switch away from salsa to gitlab or another hosting (github will not work) and then move back once the split has finally happened. Regards, Salvatore
Bug#933731: marked as done (audacity: FTBFS on 32-bit arches (except i386))
Your message dated Tue, 06 Aug 2019 06:34:43 + with message-id and subject line Bug#933731: fixed in audacity 2.3.2-2 has caused the Debian Bug report #933731, regarding audacity: FTBFS on 32-bit arches (except i386) 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.) -- 933731: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933731 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: audacity Version: 2.3.2-1 Severity: serious Justification: fails to build from source (but built successfully in the past) Dear Maintainer, audacity 2.3.2-1 appears to FTBFS on 32-bit arches (except for i386): /usr/include/c++/8/atomic:250: undefined reference to `__atomic_load_8' /usr/bin/ld: /usr/include/c++/8/atomic:250: undefined reference to `__atomic_load_8' /usr/bin/ld: audacity-AudioIO.o: in function `std::atomic::store(double, std::memory_order)': /usr/include/c++/8/atomic:239: undefined reference to `__atomic_store_8' /usr/bin/ld: audacity-AudioIO.o: in function `std::atomic::load(std::memory_order) const': /usr/include/c++/8/atomic:250: undefined reference to `__atomic_load_8' collect2: error: ld returned 1 exit status make[3]: *** [Makefile:2800: audacity] Error 1 make[3]: Leaving directory '/<>/src' make[2]: *** [Makefile:1989: all] Error 2 make[2]: Leaving directory '/<>/src' make[1]: *** [Makefile:820: all-recursive] Error 1 make[1]: Leaving directory '/<>' dh_auto_build: make -j4 returned exit code 2 make: *** [debian/rules:37: build-arch] Error 255 Could you please take a look? --- End Message --- --- Begin Message --- Source: audacity Source-Version: 2.3.2-2 We believe that the bug you reported is fixed in the latest version of audacity, 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 933...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Unit193 (supplier of updated audacity 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: SHA384 Format: 1.8 Date: Tue, 06 Aug 2019 02:01:08 -0400 Source: audacity Binary: audacity audacity-data Architecture: source Version: 2.3.2-2 Distribution: unstable Urgency: medium Maintainer: Debian Multimedia Maintainers Changed-By: Unit193 Description: audacity - fast, cross-platform audio editor audacity-data - fast, cross-platform audio editor (data) Closes: 933731 Changes: audacity (2.3.2-2) unstable; urgency=medium . * Team upload. * d/p/0006-Link-atomic-if-needed.patch: Link atomic if needed. (Closes: #933731) Checksums-Sha1: 3f2f851d2ba7ab88dc6e609c105e963cc7a5b91e 2983 audacity_2.3.2-2.dsc b91b88aa68521a03fa5cc7dacaf5eb39f92e3b6f 61972597 audacity_2.3.2.orig.tar.gz 5a6784a739353a99af1f8b0f0d1bd131b5703fde 40336 audacity_2.3.2-2.debian.tar.xz a215d3952b3c4e2411aaf91f287289a2eadf2b5d 6453 audacity_2.3.2-2_source.buildinfo Checksums-Sha256: 2b91c90c0b997f36cfc3bee169995d343c2bacd69b9f1aa2e5b73ae079d158d4 2983 audacity_2.3.2-2.dsc cc477a71ff5571c72887a7a155365b07a1a50bcea1abf490a4de7b884376c731 61972597 audacity_2.3.2.orig.tar.gz 123e236db7c744d391099125033f6a0a018cb0f2bf1c9ad7cbb7d87a60548e92 40336 audacity_2.3.2-2.debian.tar.xz 560e59843a61567a2d12a6d4112c409cce3a9e964348e52c6a27b378d198f225 6453 audacity_2.3.2-2_source.buildinfo Files: 9dcb3af590f2fe12e6e105e993387876 2983 sound optional audacity_2.3.2-2.dsc ca1b5b5258e7a8839ca72bb20093b31b 61972597 sound optional audacity_2.3.2.orig.tar.gz 2244722c6a6b65b8b64c5dfead6687a6 40336 sound optional audacity_2.3.2-2.debian.tar.xz d140378cb777ac32bb3b5b1a9af3fd76 6453 sound optional audacity_2.3.2-2_source.buildinfo Checksums-Sha512: 0da619aa3bc1e7aeb6f5f4cf5b95894aee3e50c587e5f0e7418c5e06505b88c0570e689da6ff98e534eeb8336aa79b7efb66c12e2f04b55480318c4a82114c78 2983 audacity_2.3.2-2.dsc a59d6e9e974d5f78f5ca561e3bea31fc1b3e88f9ea60b2df7ce8bcec264d886f3fdc8f20030e11a86daff8ffeb735850b5e5f73c45fbef0bfcc58692423e7cd0 61972597 audacity_2.3.2.orig.tar.gz f60ac0e1c197c6ed3cfc3d45ad78a94a868d2bb7db0114eddbc172397beab89e61a1b81ede8ba6e22335f69baec21087419dd8a8b15373fb940c3a3c8cb34bda 40336 audacity_2.3.2-2.debian.tar.xz 3dcd0ae643d8ae99b1381b0e135a99a4a86cf121b8a29ea7ee48b398e880c7c27f7a5579d1638
Bug#934021: libsidplayfp5: missing Breaks+Replaces: libsidplayfp4
Package: libsidplayfp5 Version: 2.0.0-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'sid' to 'experimental'. It installed fine in 'sid', then the upgrade to 'experimental' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces >From the attached log (scroll to the bottom...): Preparing to unpack .../libsidplayfp5_2.0.0-1_amd64.deb ... Unpacking libsidplayfp5:amd64 (2.0.0-1) ... dpkg: error processing archive /var/cache/apt/archives/libsidplayfp5_2.0.0-1_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/libstilview.so.0', which is also in package libsidplayfp4:amd64 1.8.8-1 Errors were encountered while processing: /var/cache/apt/archives/libsidplayfp5_2.0.0-1_amd64.deb Mixing shared libraries with uncorrelated SOVERSIONS in one binary package is not recommended, since it requires strict Breaks+Replaces, preventing co-installability and smooth upgrades. cheers, Andreas libsidplayfp4=1.8.8-1_libsidplayfp5=2.0.0-1.log.gz Description: application/gzip
