Bug#933163: marked as done (cyrus-imapd: Data loss possible when upgrading to buster)
Your message dated Mon, 05 Aug 2019 05:49:29 + with message-id and subject line Bug#933163: fixed in cyrus-imapd 3.0.11-1 has caused the Debian Bug report #933163, regarding cyrus-imapd: Data loss possible when upgrading to buster 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.) -- 933163: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933163 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: cyrus-imapd Version: 3.0.8-6 Severity: grave Tags: upstream Dear Maintainer, After upgrading a cyrus-imapd system from 2.4.17 (jessie-era) to 3.0.8 (buster), I discovered many missing messages. It appears that index records with MODSEQ set to zero (e.g., records for messages which predated the addition of the MODSEQ field) are being ignored. The data is still there, but not served to IMAP clients. Unfortunately, if the 3.0.8 cyrus "reconstruct" is executed to naively try to fix the missing messages, those index records (and the metadata they contain, e.g., seen flags) are lost for good! I tagged this report as "grave" because of the potential for irreversible data loss. There may be a one-line fix for this; I have filed an upstream bug report with more details: https://github.com/cyrusimap/cyrus-imapd/issues/2839 Fortunately, I have backups of the original cyrus.index files and didn't permanently lose any state, but I don't know of any way to safely upgrade to v3.x.x until this issue is fixed. -m -- System Information: Debian Release: 10.0 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-5-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages cyrus-imapd depends on: ii cyrus-common 3.0.8-6 ii dpkg 1.19.7 ii libc6 2.28-10 ii libcom-err2 1.44.5-1 ii libsasl2-22.1.27+dfsg-1 ii libssl1.1 1.1.1c-1 ii libwrap0 7.6.q-28 ii zlib1g1:1.2.11.dfsg-1 cyrus-imapd recommends no packages. cyrus-imapd suggests no packages. -- Configuration Files: /etc/pam.d/imap changed [not included] -- no debconf information --- End Message --- --- Begin Message --- Source: cyrus-imapd Source-Version: 3.0.11-1 We believe that the bug you reported is fixed in the latest version of cyrus-imapd, 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. Xavier Guimard (supplier of updated cyrus-imapd 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 07:12:47 +0200 Source: cyrus-imapd Architecture: source Version: 3.0.11-1 Distribution: unstable Urgency: medium Maintainer: Debian Cyrus Team Changed-By: Xavier Guimard Closes: 933163 Changes: cyrus-imapd (3.0.11-1) unstable; urgency=medium . * Back to unstable * New upstream version 3.0.11 (Closes: #933163) * Add spelling errors patch * Refresh patches * Add rsync in recommended dependencies Checksums-Sha1: 56c72e744cc5108763420420f65093771b2ac057 3377 cyrus-imapd_3.0.11-1.dsc 0a012087ecb0bfe23e7f8f9006895dd3fb71fe7a 10797507 cyrus-imapd_3.0.11.orig.tar.gz 30a4ac863547a9fa9e228c63ee6e571a022d55cf 488 cyrus-imapd_3.0.11.orig.tar.gz.asc 75489536ae0d6a82d9c8aaa8672c45bff82ee437 93336 cyrus-imapd_3.0.11-1.debian.tar.xz Checksums-Sha256: 35b0dbc06009c24566953543fc409e187df797c3a6bf3c3ead61e65a13022a9f 3377 cyrus-imapd_3.0.11-1.dsc f1bb5734032d399dab9af6a3f2738950286089f1d1cb7a6b50b4744d9d707a04 10797507 cyrus-imapd_3.0.11.orig.tar.gz 32e10ecab7a32857d13df0fe516abed60fa04aa1cf816525fb6f6f15bf229e3b 488 cyrus-imapd_3.0.11.orig.tar.gz.asc 5d59ec0c174ffc08d2c1307a3d46dc851d33fd6b56031e1c08f9ce2f614f0c3a 93336 cyrus-imapd_3.0.11-1.debian.tar.xz Files: 604ff924a03b6cbbfff5fec378339b78 3377 mail optional cyrus-imapd_3.0.11-1.dsc 7731f79f39cc017dfc98e45922996a84 10797507 mail optional cyrus-imapd_3.0.11.orig.tar.gz 1303ab81acca181baadf5e1a6be369cb 488 mail optional
Bug#933282: 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 05:49:35 + with message-id and subject line Bug#933282: fixed in cysignals 1.8.1+ds-3 has caused the Debian Bug report #933282, 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.) -- 933282: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933282 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: cysignals Source-Version: 1.8.1+ds-3 We believe that the bug you reported is fixed in the latest version of cysignals, 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. Jerome Benoit (supplier of updated cysignals 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 05:34:17 + Source: cysignals Architecture: source Version: 1.8.1+ds-3 Distribution: unstable Urgency: medium Maintainer: Jerome Benoit Changed-By: Jerome Benoit Closes: 933282 Changes: cysignals (1.8.1+ds-3) unstable; urgency=medium . [ Ondřej Nový ] * Use debhelper-compat instead of debian/compat. * Bump Standards-Version to 4.4.0. . [ Jerome Benoit ] * Migrate to texlive-plain-generic (Closes: #933282). Checksums-Sha1: c16ba121796883a3afe99a8a87b016a414cbae72 3629 cysignals_1.8.1+ds-3.dsc b290a6d9e794a83181d9bf40c83d396354dadb5a 12752 cysignals_1.8.1+ds-3.debian.tar.xz ef3aaf08c2d02816d1fb22290ce50678e1930efc 8622 cysignals_1.8.1+ds-3_source.buildinfo Checksums-Sha256: 46d6f278b97ddab3b94caa56e4149d2e5f4edeb7b246ea20cc6579807b22e84f 3629 cysignals_1.8.1+ds-3.dsc 91be5a0d0a95947b5d9c9ace100f19649ed4d07822165f91cd0e043f856f1717 12752 cysignals_1.8.1+ds-3.debian.tar.xz a24a01cdfe8d51ede34d776e3009a55ef8571fd44d6cb5108ed9471a4ecc556f 8622 cysignals_1.8.1+ds-3_source.buildinfo Files: 85ffdd928dd662b89156d6cb6eb46a89 3629 python optional cysignals_1.8.1+ds-3.dsc b95b7f734df454e4a3b6f340aa36e975 12752 python optional cysignals_1.8.1+ds-3.debian.tar.xz 209475d185956907e19456a95c872a20 8622 python optional cysignals_1.8.1+ds-3_source.buildinfo -BEGIN PGP SIGNATURE- iQRJBAEBCgAzFiEEriiuFXEN/x2H5adiP5IZpn82xosFAl1HwlIVHGNhbGN1bHVz QHJlem96ZXIubmV0AAoJED+SGaZ/NsaLERof/0A7HhI6KMADszJEzVA1KGSlpuw1 bSGlkmTtHjgN5ak4ToGFXI4bowScTbzGacGwWCVLY6ziZ8K2LIDivHHJVzUJqZjl o+KCwoIXQ/mtO86mzXnxVSZM0erN5Niwz5d3YVOOKvASXOM0x+ZtkFsXbGfXl1Bu vNSzds01TNni12UoS1K93Lng/ou43SjujBCts7Xt6agdbQWse7hMU6ZTdz6BuUrQ oZc4QMoxDmYGjbwU/DBCt36A5t5ECSsSG5eVek2dUQXOTB8/uQyg+I58YX9+WRET LLIXLhiHFq1NPUTU3wX0l+QQonolReZmWfHugy1Z3Q1XoVXbjeJl0Rpss07oc7sb 2qOZMIKx79PjBnVT0jYElfQ0Vq/rTgSbVw2fInBdkKroxZp9aDikEcAhr1F0/7z9 vWdB4IAj9QguXH9OOL2ZMGTyOQhsGPitvh50BH4apc0ooqBxlEnrl5/+skSun6p1 7vVnb+/grMb01U4zqdD01hutNtcHRDvmYTbmUxmc5LD7bXbeiDtL18DW9JmYPTsi zik07RFjTo886MujzlgsHmLIdGpObfU8ewMN3Wlq1dZkocQf4JuoRwSZaYshGRZ5 heOctsdFEs5YDJWT9KfwxJUpY9/V9E6d00vYysduZDcyRbCWhTdVLq9nG++PChqR m6XAa6Cv8RcJTnCwNWNE8DIgz/YoYwTfFXOV+EAd8mSiCA0a/CShsDtSP4TohRgc r6/lPMykcpeo5WCfTAXKSPpj502y3ODRpkMFt9ao9eo0oLn2m0d7Ai1gLtezHR0z dw9ZNLoizvkHVQNmavdZXcQ0aELvjFz3w6ihIaGUs9QCs9Mb7upBS4oktkKhYvZT 3x8JN1lbZEsx5PvtQDddbfu2K4Q6BjMNZoKHgBcUinBEnfztra91W1JnzlR47sQF 7KbBe+4RT2HFBXffmJxuXWxqP+dngdygQy69OD1r9VQy5nYDHavAe8rNHN6OpB70 PZ6/h1OUgmduQG6lR4L+d9RdaCg/VtgZxUmCP+S3EwTrKRdgUEMZQ0vkIbus8OLW UMqSn+p1dQ+K83Qw3l8O6hoC/N4HBHyaptGo7RzZaA0nZQAsN8gIFiTo+mEMfeK/ v8qWfaqwH2sj21ynuy9iuIx/agFtEaNYjkfaITbQtFbBOMgKS7HJayPKgZDGolZN sb5AA/MHRjQJWvGug2Y1n58RSA7XaBOJ6Wfu6MjWbtLZ2frSQCpDO3EZvj3ahqTm
Bug#933923: src:valinor: Incompatible with safe load changes in new pyyaml
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
Bug#933922: src:salt: Unsafe use of yaml.load()
Package: src:salt Version: 2018.3.4+dfsg1-6 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
Bug#933921: src:python-tablib: Unsafe use of yaml.load()
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
Bug#933920: src:python-markdown: Unsafe use of yaml.load()
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
Bug#933918: src:lava: Unsafe use of yaml.load()
Package: src:lava Version: 2019.01-5 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
Bug#933919: src:lavacli: Unsafe use of yaml.load()
Package: src:lavacli Version: 0.9.7-1 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
Bug#933917: src:knot: Unsafe use of yaml.load()
Package: src:knot Version: 2.7.6-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
Processed: severity of 933592 is serious
Processing commands for cont...@bugs.debian.org: > severity 933592 serious Bug #933592 [node-node-forge,node-jsonld,node-rdf-canonize] Webpack 4 transition: node-node-forge fail to build with webpack 4 Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 933592: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933592 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: severity of 933626 is serious
Processing commands for cont...@bugs.debian.org: > severity 933626 serious Bug #933626 [node-trust-json-document] node-trust-json-document: build fails with upcoming webpack 4 Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 933626: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933626 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: severity of 933666 is serious
Processing commands for cont...@bugs.debian.org: > severity 933666 serious Bug #933666 [leaflet-image] leaflet-image: fails to build with webpack 4 Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 933666: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933666 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: severity of 933662 is serious
Processing commands for cont...@bugs.debian.org: > severity 933662 serious Bug #933662 [node-matrix-js-sdk] node-matrix-js-sdk: build with webpack 4 failing Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 933662: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933662 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: python3-pytest: pytest v4 breaks existing tests
Processing control commands: > affects -1 + src:apipkg src:betamax src:ccdproc src:chardet Bug #933914 [python3-pytest] python3-pytest: pytest v4 breaks existing tests Added indication that 933914 affects src:apipkg, src:betamax, src:ccdproc, and src:chardet > affects -1 + src:dask src:django-axes src:doit src:drms Bug #933914 [python3-pytest] python3-pytest: pytest v4 breaks existing tests Added indication that 933914 affects src:dask, src:django-axes, src:doit, and src:drms > affects -1 + src:fiat src:mpi4py src:pandas src:pygalmesh Bug #933914 [python3-pytest] python3-pytest: pytest v4 breaks existing tests Added indication that 933914 affects src:fiat, src:mpi4py, src:pandas, and src:pygalmesh > affects -1 + src:pyjwt src:pytest-sugar src:pytest-xdist Bug #933914 [python3-pytest] python3-pytest: pytest v4 breaks existing tests Added indication that 933914 affects src:pyjwt, src:pytest-sugar, and src:pytest-xdist > affects -1 + src:pytest-xvfb src:python-dbfread Bug #933914 [python3-pytest] python3-pytest: pytest v4 breaks existing tests Added indication that 933914 affects src:pytest-xvfb and src:python-dbfread > affects -1 + src:python-dugong src:python-graphviz Bug #933914 [python3-pytest] python3-pytest: pytest v4 breaks existing tests Added indication that 933914 affects src:python-dugong and src:python-graphviz > affects -1 + src:python-hypothesis src:python-parameterized Bug #933914 [python3-pytest] python3-pytest: pytest v4 breaks existing tests Added indication that 933914 affects src:python-hypothesis and src:python-parameterized > affects -1 + src:python-transliterate src:setuptools-scm Bug #933914 [python3-pytest] python3-pytest: pytest v4 breaks existing tests Added indication that 933914 affects src:python-transliterate and src:setuptools-scm > affects -1 + src:spyder-line-profiler src:spyder-reports Bug #933914 [python3-pytest] python3-pytest: pytest v4 breaks existing tests Added indication that 933914 affects src:spyder-line-profiler and src:spyder-reports > affects -1 + src:spyder-unittest src:sudsy Bug #933914 [python3-pytest] python3-pytest: pytest v4 breaks existing tests Added indication that 933914 affects src:spyder-unittest and src:sudsy -- 933914: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933914 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#933914: python3-pytest: pytest v4 breaks existing tests
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
Bug#932584: Epydoc and Pydoctor
Hi Kenneth, Ian, On Wed, Jul 31, 2019 at 08:45:54PM -0500, Kenneth Pronovici wrote: > On Wed, Jul 31, 2019 at 10:46 AM Ian Jackson > wrote: > > > Otherwise, I will see if I can determine how well the package works > > > without epydoc installed. If it works (i.e. doesn't blow up) and I > > > don't hear back with other instructions, I will eventually NMU my > > > changes to remove the epydoc dependency. Given that I haven't gotten > > > any replies for more than 18 months now, I won't wait that long before > > > doing this NMU. > > > > That sounds really good to me for now. I think you can do this NMU > > whenever you like. > > I tested pydoctor against my own cedar-backup2 code, which I never converted > away from Epydoc since it's Python 2-only. It seems to work fine: > > mars:~/projects/dev/software/cedar-backup2> pydoctor CedarBackup2/ > adding directory > /home/pronovic/projects/dev/software/cedar-backup2/CedarBackup2 > 41/41 modules processed 0 warnings > WARNING: guessing CedarBackup2 for project name > writing html to apidocs using pydoctor.templatewriter.writer.TemplateWriter > starting ModuleIndexPage ... > Error trying to import 'epytext' parser: > > ImportError: No module named epydoc.markup.epytext > > Using plain text formatting only. > took 0.006452s > starting ClassIndexPage ... took 0.011512s > starting IndexPage ... took 0.002281s > starting NameIndexPage ... took 0.079562s > starting UndocumentedSummaryPage ... took 0.004314s > 125/125 pages written > Generating objects inventory at apidocs/objects.inv > > The generated HTML documentation is legible, if not as pretty as it > would have been before. Given that it works, I am going to NMU the > version of the package that doesn't depend on epydoc. I'll also > create a PR on salsa. On salsa, master has diverged from the released > package, but I am *not* going to integrate those changes, because I > don't want to take responsibility for them. Sorry for the delayed reply and thanks for working on Pydoctor without epydoc. I'm happy for you to NMU a new version, but can also merge a patch and do an upload - as you prefer. As far as I know pydoctor upstream is pretty dormant, but not completely inactive. Pull requests do get looked at and there is the occasional fix to keep it running, but that's about it. Cheers, Jelmer
Bug#932584: Epydoc and Pydoctor
I decided to NMU and uploaded a few days ago, so things are in good shape now, I think. You can integrate my changes whenever you have time. Thanks for confirming that your ok with the NMU. I was hoping you would be. KEN
Bug#933743: LibXSLT in Debian stable has three unpatched security vulnerabilities
On Sun, 2019 Aug 4 03:20-04:00, Salvatore Bonaccorso wrote: > > Sure it might have been overlooked, but pinging the existing bug would > have been less overhead to now as well start tracking this one as well > adjusting metadata etc. But no worries. Just so that I understand, there was an existing bug? I checked the open bugs before filing this one, but didn't see anything relating to those CVEs. Do you mean something with the security tracker? > CVSS severity scores are really very dependent and who assess it. I > guess you are refering to the ones as assessed by NVD. Agreed though > that Felix Wilhelm has provided a nice exploiting vector example in > the upstream issue for local file access depending on context of how > libxslt would be used. And I figure LibXSLT is used in a number of ways that may result in security exposure, not just within Debian itself, but also user applications built on top of it. > Anyway I prepared a non-maintainer upload for libxslt adressing all > three CVEs in unstable and uploaded it to DELAYED/2 and create a merge > request on salsa. Thank you, I will watch for it in sid :)
Bug#933710: marked as done (crosshurd: fails to download any packages)
Your message dated Sun, 04 Aug 2019 23:49:40 + with message-id and subject line Bug#933710: fixed in crosshurd 1.7.53 has caused the Debian Bug report #933710, regarding crosshurd: fails to download any packages to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 933710: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933710 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: crosshurd Version: 1.7.52 Severity: grave Tags: upstream Justification: renders package unusable -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear Maintainer, * What led up to the situation? using crosshurd * What exactly did you do (or not do) that was effective (or ineffective)? made a directory, issued the 'crosshurd' command, inside crosshurd I chose a dir, and then i386 architecture (my system is x86_64, but first of all i386 is the default option for Hurd and secondly behavior for x86_64 is identical). * What was the outcome of this action? crosshurd breaks citing the lack of i386 architecture. It seems this program is abandonware, and the repos it points to don't exist. * What outcome did you expect instead? Download of Hurd packages and setting up a bootable system in the directory of invocation Complete output of crosshurd: , |dpkg-architecture: warning: default GNU system type i686-gnu for Debian arch hurd-i386 does not match specified GNU system type i386-gnu |Get:2 http://cdn-fastly.deb.debian.org/debian unstable InRelease [149 kB] |Get:1 http://ftp.ports.debian.org/debian-ports unreleased InRelease [56.6 kB] |Get:3 http://ftp.ports.debian.org/debian-ports unreleased/main hurd-i386 Packages [86.2 kB] |Get:4 http://cdn-fastly.deb.debian.org/debian unstable/main Translation-en [6,287 kB] |Fetched 6,578 kB in 36s (184 kB/s) |Reading package lists... Done |W: --force-yes is deprecated, use one of the options starting with --allow instead. |N: Skipping acquire of configured file 'main/binary-hurd-i386/Packages' as repository 'http://httpredir.debian.org/debian unstable InRelease' doesn't support architecture 'hurd-i386' |Reading package lists... Done |Building dependency tree |Reading state information... Done |Package libc0.3 is not available, but is referred to by another package. |This may mean that the package is missing, has been obsoleted, or |is only available from another source | | Package debianutils is not available, but is referred to by another package. | This may mean that the package is missing, has been obsoleted, or | is only available from another source | | Package dpkg is not available, but is referred to by another package. | This may mean that the package is missing, has been obsoleted, or | is only available from another source `[cut the outher names of packages] , | W: --force-yes is deprecated, use one of the options starting with --allow instead. | E: Package 'adduser' has no installation candidate | E: Unable to locate package apt | E: Unable to locate package apt-utils | E: Unable to locate package base-files | E: Unable to locate package base-passwd | E: Unable to locate package bash | E: Unable to locate package bsdutils `[cut the outher names of packages] Output obtained by typing in the "i686" architecture, and proposing crosshurd the /root/jail dir: , | Get:1 http://cdn-fastly.deb.debian.org/debian unstable InRelease [149 kB] | Get:3 http://cdn-fastly.deb.debian.org/debian unstable/main Translation-en [6,287 kB] | Get:2 http://ftp.ports.debian.org/debian-ports unreleased InRelease [56.6 kB] | Get:4 http://ftp.ports.debian.org/debian-ports unreleased/main hurd-i386 Packages [86.2 kB] | Fetched 6,578 kB in 36s (185 kB/s) | Reading package lists... Done | W: --force-yes is deprecated, use one of the options starting with --allow instead. | W: Download is performed unsandboxed as root as file '/root/jail/var/cache/apt/lists/partial/ftp.debian-ports.org_debian_dists_unreleased_InRelease' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied) | N: Skipping acquire of configured file 'main/binary-hurd-i386/Packages' as repository 'http://httpredir.debian.org/debian unstable InRelease' doesn't support architecture 'hurd-i386' | Reading package lists... Done | Building dependency tree | Reading state information... Done | Package libc0.3 is not available, but is referred to by another package. | This may mean that the package is missing, has been obsoleted, or | is only available
Processed: Re: Bug#933710: crosshurd: fails to download any packages
Processing control commands: > tags -1 + pending Bug #933710 [crosshurd] crosshurd: fails to download any packages Added tag(s) pending. -- 933710: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933710 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#933710: crosshurd: fails to download any packages
Control: tags -1 + pending Hello, Wojciech Aniszewski, le ven. 02 août 2019 11:57:34 +0200, a ecrit: >crosshurd breaks citing the lack of i386 architecture. Yes. > |N: Skipping acquire of configured file 'main/binary-hurd-i386/Packages' > as repository 'http://httpredir.debian.org/debian unstable InRelease' doesn't > support architecture 'hurd-i386' That repository doesn't support hurd-i386 any more indeed. > It seems this program is abandonware, and the repos it points to don't exist. It's not abandonware. It's just part of the so many dozens of places which need updating now that ftpmaster has removed hurd from the main archive. Samuel
Processed: Re: Bug#933802: /usr/bin/mandb: SIGSEGV, Segmentation fault on updating database.
Processing control commands: > severity -1 serious Bug #933802 [man-db] /usr/bin/mandb: SIGSEGV, Segmentation fault on updating database. Severity set to 'serious' from 'important' > tag -1 fixed-upstream Bug #933802 [man-db] /usr/bin/mandb: SIGSEGV, Segmentation fault on updating database. Added tag(s) fixed-upstream. -- 933802: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933802 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: severity of 933580 is serious
Processing commands for cont...@bugs.debian.org: > severity 933580 serious Bug #933580 [debian-edu-config] etc/network/if-up.d/hostname causes loss of dynamic v4 IP address Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 933580: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933580 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#783936: marked as done (FTBFS: build-depends on removed python-uno)
Your message dated Sun, 04 Aug 2019 22:05:21 + with message-id and subject line Bug#933881: Removed package(s) from unstable has caused the Debian Bug report #783936, regarding FTBFS: build-depends on removed python-uno 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.) -- 783936: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=783936 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:libswe-doc Version: 1.80.00.0001-1 Severity: serious Hi, sorry, it seems I forgot libswe-doc when I filed bugs against stuff depending on python-uno long before jessies release. See e.g. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707342 Now, though, the time came when python-uno is dead: LO 4.4.2 uploaded to sid after the jessie release already disabled python-uno, as announced: $ rmadison -s unstable python3-uno,python-uno debian: python-uno | 1:4.3.3-2 | sid | amd64, arm64, armel, armhf, i386, kfreebsd-amd6 +4, kfreebsd-i386, mips, mipsel, powerpc, ppc64el, s390x, sparc python3-uno | 1:4.3.3-2 | sid | sparc python3-uno | 1:4.4.2-1 | sid | amd64, arm64, armel, armhf, i386, kfreebsd-amd6 +4, kfreebsd-i386, mips, mipsel, powerpc, ppc64el, s390x And thus everything build-depending on python-uno is now even unbuildable, as: # apt-get install python-uno Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: python-uno : Depends: libreoffice-core (= 1:4.3.3-2) but 1:4.4.2-1 is to be installed E: Unable to correct problems, you have held broken packages. So libswe-doc either - needs to be fixed to use python3-uno - needs to stop using python-uno for whatever it is needed - needs to get removef Again, sorry for the missed pre-warning... Regards, Rene -- System Information: Debian Release: stretch/sid APT prefers buildd-unstable APT policy: (500, 'buildd-unstable'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) --- End Message --- --- Begin Message --- Version: 1.80.00.0001-1+rm Dear submitter, as the package libswe-doc has just been removed from the Debian archive unstable 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/933881 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#933496: marked as done (libminini: doesn't ship needed headers files)
Your message dated Sun, 04 Aug 2019 20:44:57 +
with message-id
and subject line Bug#933496: fixed in libminini 1.2.a+ds-4
has caused the Debian Bug report #933496,
regarding libminini: doesn't ship needed headers files
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.)
--
933496: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933496
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libminini
Version 1.2.a+ds-2
Severity: serious
tags: patch
Hello, I discovered libminini stopped using cmake and switched to plain
Makefiles...
but is not installing anymore the required headers
diff -Nru libminini-1.2.a+ds/debian/patches/Makefile.patch
libminini-1.2.a+ds/debian/patches/Makefile.patch
--- libminini-1.2.a+ds/debian/patches/Makefile.patch2019-07-29
05:32:00.0 +0200
+++ libminini-1.2.a+ds/debian/patches/Makefile.patch2019-07-30
21:54:11.0 +0200
@@ -12,7 +12,7 @@
+
+CPPFLAGS += -fPIC
+
-+HEADERS := minIni.h
++HEADERS := *.h
+SRCS := minIni.cc
+OBJS := $(SRCS:.cc=.o)
+
this makes utox FTBFS in sid...
btw what is the rationale behind dropping the cmake file? I can help fixing it
if needed... not sure why you dropped it!
/usr/bin/cc -isystem /usr/include/minIni -isystem /usr/include/qrcodegen -g
-O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Wextra
-Wpointer-arith -Wimplicit-fallthrough=5 -Werror=implicit-function-declaration
-Wno-misleading-indentation -fno-strict-aliasing -fPIC -flto -std=gnu11 -o
CMakeFiles/utox.dir/src/messages.c.o -c /<>/src/messages.c
[ 82%] Building C object CMakeFiles/utox.dir/src/notify.c.o
/usr/bin/cc -isystem /usr/include/minIni -isystem /usr/include/qrcodegen -g
-O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Wextra
-Wpointer-arith -Wimplicit-fallthrough=5 -Werror=implicit-function-declaration
-Wno-misleading-indentation -fno-strict-aliasing -fPIC -flto -std=gnu11 -o
CMakeFiles/utox.dir/src/notify.c.o -c /<>/src/notify.c
[ 83%] Building C object CMakeFiles/utox.dir/src/qr.c.o
/usr/bin/cc -isystem /usr/include/minIni -isystem /usr/include/qrcodegen -g
-O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Wextra
-Wpointer-arith -Wimplicit-fallthrough=5 -Werror=implicit-function-declaration
-Wno-misleading-indentation -fno-strict-aliasing -fPIC -flto -std=gnu11 -o
CMakeFiles/utox.dir/src/qr.c.o -c /<>/src/qr.c
/<>/src/messages.c: In function ???messages_draw_filetransfer???:
/<>/src/messages.c:907:47: warning: format ???%lu??? expects
argument of type ???long unsigned int???, but argument 4 has type
???uint64_t??? {aka ???long long unsigned int???} [-Wformat=]
907 | p += snprintf(p, speed - p, "/s %lus",
| ~~^
| |
| long unsigned int
| %llu
908 |file->speed ? (file->size -
file->progress) / file->speed : 0);
|
~
|
|
|
uint64_t {aka long long unsigned int}
[ 85%] Building C object CMakeFiles/utox.dir/src/screen_grab.c.o
/usr/bin/cc -isystem /usr/include/minIni -isystem /usr/include/qrcodegen -g
-O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Wextra
-Wpointer-arith -Wimplicit-fallthrough=5 -Werror=implicit-function-declaration
-Wno-misleading-indentation -fno-strict-aliasing -fPIC -flto -std=gnu11 -o
CMakeFiles/utox.dir/src/screen_grab.c.o -c
Bug#933883: Should zope2.13 be removed?
Source: zope2.13 Severity: serious Should zope2.13 be removed? - Unmaintained (last upload in 2014) - FTBFS for a long time, missed two stable releases Cheers, Moritz
Bug#933882: Should percona-xtrabackup be removed?
Source: percona-xtrabackup Severity: serious Should percona-xtrabackup be removed? - Unmaintained (last maintainer upload in 2014) - FTBFS with GCC 6 and later (#811896) and #917583 - Missed two stable releases because of that - Broken with current Mariadb (#903043) - Replacement exists (mariabackup) Cheers, Moritz
Bug#933618: marked as done (python-crypto: Epydoc will be removed)
Your message dated Sun, 04 Aug 2019 19:36:18 + with message-id and subject line Bug#933618: fixed in python-crypto 2.6.1-10 has caused the Debian Bug report #933618, regarding python-crypto: Epydoc will be removed 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.) -- 933618: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933618 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python-crypto Version: 2.6.1-7 Severity: serious Justification: Policy 5.9.2 Hi, This is one of 20+ packages in the archive that still depend on Epydoc. I have filed a bug with ftp.debian.org to have epydoc removed from unstable. Besides its lack of support for Python 3, epydoc has been completely unsupported upstream for close to a decade. It really should have been removed from the archive years ago. I apologize for the late notice on this. I filed bugs against all of the dependencies I could find over 18 months ago, but the FTP Master list included some additional packages. If I don't hear back from you, I will NMU a version of your package that removes the build dependency. I will accomplish this by simply not building the API documentation. If you don't want me to do this, please reply and let me know how you want me to proceed. Thanks, KEN --- End Message --- --- Begin Message --- Source: python-crypto Source-Version: 2.6.1-10 We believe that the bug you reported is fixed in the latest version of python-crypto, 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 python-crypto 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: Sun, 04 Aug 2019 20:56:28 +0200 Source: python-crypto Architecture: source Version: 2.6.1-10 Distribution: unstable Urgency: medium Maintainer: Sebastian Ramacher Changed-By: Sebastian Ramacher Closes: 933618 Changes: python-crypto (2.6.1-10) unstable; urgency=medium . [ Kenneth J. Pronovici ] * Eliminate dependency on epydoc, which will be removed (Closes: #933618) - Update debian/rules to no longer build epydoc documentation - Update debian/control to remove Build-Depends: python-epydoc - Update debian/control to remove now-empty python-crypto-doc package - Update debian/control to remove Suggests: python-crypto-doc - Remove debian/python-crypto-doc.doc-base - Remove debian/python-crypto-doc.docs . [ Sebastian Ramacher ] * debian/control: Bump Standards-Version. * debian/: Bump debhelper compat to 12. Checksums-Sha1: 3955e4cf4b52da377749efdae9b3034d8f504236 2287 python-crypto_2.6.1-10.dsc f126f842a86aa9656d9d5299d5477d784cae9aef 23400 python-crypto_2.6.1-10.debian.tar.xz Checksums-Sha256: 8d0acef822647d95ee8adc59d65683dd20a3839e49427670b114af24a31306b0 2287 python-crypto_2.6.1-10.dsc f6d9e72293858b26c85ab4cbc5f32a67f9f3ebcc2de23ef4175ae17040e28189 23400 python-crypto_2.6.1-10.debian.tar.xz Files: 957d4b3514b2f6add546cb933d051c25 2287 python optional python-crypto_2.6.1-10.dsc 07f66da89c40494ead208f3be8819e88 23400 python optional python-crypto_2.6.1-10.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEE94y6B4F7sUmhHTOQafL8UW6nGZMFAl1HK38ACgkQafL8UW6n GZOujRAAhwuF0pcsBlKElSOWY2eCTIAPG00xEnULqxeqA4T1Hvqs4/SMxcAOCsBH HdOCiu4PJgX91DweDpbZvZqQCBmDWrjGXETyUaTdZxnP7FhVAWzFyV4VhFVgmsFl tcYvzm9P1s+O4pVayJlK+MXK39nMaEHNfvOt97bx7KGiKzO9Gc/tnsofHzVNBe+p rfMKvBI9/ACOmiYRGOhcXpb7ds62BBttPW+94ZjHhZzpmvYG/cKK2Ld840dcL4uk kcGvtzmnO4EVvKq0p+2L8LshLmrDJtiyVfd/m/F01GgyVqTdsECCTQMGkxc6Uutn BGb+aFCUC33FbCtjDuF4wi2eQBBKOEZt6s6Xi+GgvgfQYZyRzul++/bYDMDhwX+y 4HbfACbDfE0BEjkV1AmDU1rIbYC5frqJ+SOXK9gL/ryUvfN0QyyTS2RzBcqAbfqf nM+47yIQ7fFs2alvffVx/5ygq+vdzUnAFrXrJ3cDWtSOIBdo4yBC1nBy+AtKWV3g HzJ4xLsD6ZrOd5rzAGv3SBUqLb6xdlHjYh0+x89K1rjanEp3DcKdJis3LSz3jkh8 PDm2hNdFdRSgLUcqxHocPJEDlgpXq0i9k2fLiZDV3TQSyMlGH4JmFPV5f2UeZifQ d+buWn7floymTqxtvfw1c2qmFjaN2TBvNKder1oNIGrFQ5IwQxw= =Q/lo -END PGP SIGNATURE End Message ---
Bug#911688: marked as done (willow FTBFS: ModuleNotFoundError: No module named 'cv2')
Your message dated Sun, 4 Aug 2019 20:54:15 +0200
with message-id
and subject line Fixed
has caused the Debian Bug report #911688,
regarding willow FTBFS: ModuleNotFoundError: No module named 'cv2'
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.)
--
911688: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911688
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: willow
Version: 1.1-3
Severity: serious
Tags: ftbfs
willow fails to build from source in unstable for multiple
architectures, e.g. amd64:
https://tests.reproducible-builds.org/debian/rbuild/unstable/amd64/willow_1.1-3.rbuild.log.gz
| ==
| ERROR: test_has_animation (tests.test_opencv.TestOpenCVOperations)
| --
| Traceback (most recent call last):
| File
"/build/1st/willow-1.1/.pybuild/cpython3_3.7_willow/build/willow/plugins/opencv.py",
line 10, in _cv2
| import cv2
| ModuleNotFoundError: No module named 'cv2'
|
| During handling of the above exception, another exception occurred:
|
| Traceback (most recent call last):
| File
"/build/1st/willow-1.1/.pybuild/cpython3_3.7_willow/build/tests/test_opencv.py",
line 16, in setUp
| colour_image = OpenCVColorImage.from_buffer_rgb(buffer_rgb)
| File
"/build/1st/willow-1.1/.pybuild/cpython3_3.7_willow/build/willow/plugins/opencv.py",
line 58, in from_buffer_rgb
| cv2 = _cv2()
| File
"/build/1st/willow-1.1/.pybuild/cpython3_3.7_willow/build/willow/plugins/opencv.py",
line 12, in _cv2
| from cv import cv2
| ModuleNotFoundError: No module named 'cv'
|
| --
| Ran 96 tests in 2.393s
|
| FAILED (errors=5, expected failures=7)
| E: pybuild pybuild:338: test: plugin distutils failed with: exit code=1: cd
/build/1st/willow-1.1/.pybuild/cpython3_3.7_willow/build; python3.7 -m unittest
discover -v
| dh_auto_test: pybuild --test -i python{version} -p "3.7 3.6" returned exit
code 13
| make: *** [debian/rules:6: build] Error 25
| dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2
Helmut
--- End Message ---
--- Begin Message ---
Version: 1.1-4
Fixed.
--
Best regards
Ondřej Nový
--- End Message ---
Bug#910902: Please test again: my_print_defaults and Akonadi for a freash installation
For some strange reason page https://tracker.debian.org/pkg/mariadb-10.3 still says "Updating mariadb-10.3 introduces new bugs: #910902". Do you Sandro have any ideas why that is?
Bug#933848: pygalmesh: 1
Source: pygalmesh Severity: important Tags: moreinfo,unreproducible Followup-For: Bug #933848 I'm quite confused by this bug report. pygalmesh is configured to build using pybuild not cmake, and it does build that way without cmake (whether built via 'fakeroot debian/rules binary' or 'dpkg-buildpackage'), whether cmake is installed or not. Your log snippet shows dh_auto_install -O--buildsystem=pybuild I: pybuild base:217: dh_auto_install --buildsystem=cmake So your system starts building with pybuild, but in the middle of it triggers cmake instead. That's not normal, and not expected. It doesn't behave that way for me. -- 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
Bug#932539:
I just released v4.1.7 which contains the fix for this bug. Please package it as you see fit.
Processed: affects 933868
Processing commands for cont...@bugs.debian.org: > affects 933868 node-axios Bug #933868 [grunt] grunt should look for tasks in /usr/share/nodejs as well Added indication that 933868 affects node-axios > thanks Stopping processing here. Please contact me if you need assistance. -- 933868: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933868 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: affects 933868
Processing commands for cont...@bugs.debian.org: > affects 933868 node-handlebars Bug #933868 [grunt] grunt should look for tasks in /usr/share/nodejs as well Added indication that 933868 affects node-handlebars > thanks Stopping processing here. Please contact me if you need assistance. -- 933868: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933868 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#933868: grunt should look for tasks in /usr/share/nodejs as well
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.
Bug#933865: adb crashes on startup with SIGBUS
Package: adb
Version: 1:8.1.0+r23-5
Severity: grave
Justification: renders package unusable
Dear Maintainer,
the problem appears to be a regression between 9 (Stretch) and 10 (Buster) as
adb worked fine under Stretch and doesn't work anymore under Buster.
When I try to start 'adb' using 'adb devices -l' I get
--- snip ---
user@box:~> adb devices -l
List of devices attached
* daemon not running; starting now at tcp:5037
ADB server didn't ACK
Full server startup log: /tmp/adb.1000.log
Server had pid: 16703
--- adb starting (pid 16703) ---
adb I 08-04 11:37:16 16703 16703 main.cpp:57] Android Debug Bridge version
1.0.39
adb I 08-04 11:37:16 16703 16703 main.cpp:57] Version 1:8.1.0+r23-5
adb I 08-04 11:37:16 16703 16703 main.cpp:57] Installed as
/usr/lib/android-sdk/platform-tools/adb
adb I 08-04 11:37:16 16703 16703 main.cpp:57]
adb I 08-04 11:37:16 16703 16703 adb_auth_host.cpp:416] adb_auth_init...
adb I 08-04 11:37:16 16703 16703 adb_auth_host.cpp:174] read_key_file
'/home/till/.android/adbkey'...
adb I 08-04 11:37:16 16703 16703 adb_auth_host.cpp:391] adb_auth_inotify_init...
adb I 08-04 11:37:16 16703 16703 adb_auth_host.cpp:467] Calling
send_auth_response
* failed to start daemon
error: cannot connect to daemon
--- snap ---
Note: /tmp/adb.1000.log shows exactly what's on stdout/stderr (seen above).
The problem appears to be that adb gets killed by SIGBUS:
--- snip ---
user@box:~> strace - -o adb adb devices -l
[...]
* failed to start daemon
error: cannot connect to daemon
user@box:~> grep killed adb.167*
adb.16702:--- SIGCHLD {si_signo=SIGCHLD, si_code=CLD_KILLED, si_pid=16703,
si_uid=1000, si_status=SIGBUS, si_utime=2, si_stime=8} ---
adb.16703:+++ killed by SIGBUS +++
adb.16705:+++ killed by SIGBUS +++
adb.16706:+++ killed by SIGBUS +++
adb.16713:+++ killed by SIGBUS +++
adb.16715:+++ killed by SIGBUS +++
adb.16716:+++ killed by SIGBUS +++
user@box:~> cat adb.16703
set_robust_list(0xb6b25540, 12) = 0
close(3)= 0
execve("/usr/lib/android-sdk/platform-tools/adb", ["adb", "-L", "tcp:5037",
"fork-server", "server", "--reply-fd", "4"], 0xbecde0d4 /* 30 vars */) = 0
brk(NULL) = 0xde9000
[...]
bind(6, {sa_family=AF_INET, sin_port=htons(5037),
sin_addr=inet_addr("127.0.0.1")}, 16) = 0
listen(6, 4)= 0
[...]
futex(0xb6bd9860, FUTEX_WAKE_PRIVATE, 2147483647) = 0
getrandom("\xd6\x33\x59\xbc\xf7\x11\x33\x14\x38\x2d\x14\x48\x24\x14\xfb\xe0\x17\x40\xfd\x73\x07\x9a\xec\x6e\x89\x28\x25\xb6\x3e\x41\x04\x94",
32, 0) = 32
futex(0xb6bd9bec, FUTEX_WAKE_PRIVATE, 2147483647) = 0
getrandom("\xd2\x6f\x66\x87\x1c\x98\x22\x65\xd0\x70\x74\x8d\x8e\xd6\xe6\xa8\x83\xce\xc5\x63\x09\x25\x63\xe4\xbf\x97\x95\xfe\x6c\x3a\x9b\x89"...,
48, 0) = 48
--- SIGBUS {si_signo=SIGBUS, si_code=BUS_ADRALN, si_addr=0xb6b9dba1} ---
+++ killed by SIGBUS +++
--- snap ---
Forcibly installing these packages gives me a working adb:
adb_7.0.0+r33-1_armhf.deb
android-libadb_7.0.0+r33-1_armhf.deb
android-libbase_7.0.0+r33-1_armhf.deb
android-libcutils_7.0.0+r33-1_armhf.deb
-- System Information:
Debian Release: 10.0
APT prefers stable
APT policy: (500, 'stable')
Architecture: armhf (armv7l)
Kernel: Linux 4.19.0-5-armmp-lpae (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=C (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages adb depends on:
ii android-libadb 1:8.1.0+r23-5
ii android-libbase 1:8.1.0+r23-5
ii libc62.28-10
ii libgcc1 1:8.3.0-6
ii libstdc++6 8.3.0-6
Versions of packages adb recommends:
ii android-sdk-platform-tools-common 27.0.0+10
adb suggests no packages.
-- no debconf information
Bug#930996: marked as done (cloudkitty: FTBFS in buster (Can't resolve label reference for ORDER BY / GROUP BY))
Your message dated Sun, 04 Aug 2019 14:12:34 + with message-id and subject line Bug#930996: fixed in cloudkitty 8.0.0-4+deb10u1 has caused the Debian Bug report #930996, regarding cloudkitty: FTBFS in buster (Can't resolve label reference for ORDER BY / GROUP BY) 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.) -- 930996: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930996 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:cloudkitty Version: 8.0.0-4 Severity: serious Tags: ftbfs Dear maintainer: I tried to build this package in buster but it failed: [...] debian/rules build-indep pyversions: missing X(S)-Python-Version in control file, fall back to debian/pyversions pyversions: missing debian/pyversions file, fall back to supported versions py3versions: no X-Python3-Version in control file, using supported versions dh build-indep --buildsystem=python_distutils --with python3,sphinxdoc,systemd dh_update_autotools_config -i -O--buildsystem=python_distutils dh_autoreconf -i -O--buildsystem=python_distutils dh_auto_configure -i -O--buildsystem=python_distutils dh_auto_configure: Please use the third-party "pybuild" build system instead of python-distutils dh_auto_configure: This feature will be removed in compat 12. debian/rules override_dh_auto_build make[1]: Entering directory '/<>' pyversions: missing X(S)-Python-Version in control file, fall back to debian/pyversions pyversions: missing debian/pyversions file, fall back to supported versions [... snipped ...] INFO [alembic.runtime.migration] Running upgrade 464e951dc3b8 -> 2ac2217dcbd9, Added support for meta collector INFO [alembic.runtime.migration] Running upgrade 2ac2217dcbd9 -> 385e33fef139, Added priority to modules_state. cloudkitty.tests.transformers.test_gnocchi.GnocchiTransformerTest.test_strip_gnocchi_volume(sqlite) cloudkitty.tests.transformers.test_gnocchi.GnocchiTransformerTest.test_strip_gnocchi_volume(sqlite) ... ok == FAIL: cloudkitty.tests.storage.v1.test_storage.StorageTotalTest.test_get_total_groupby_tenant_and_restype(sqlite,sqlalchemy,sqlalchemy) cloudkitty.tests.storage.v1.test_storage.StorageTotalTest.test_get_total_groupby_tenant_and_restype(sqlite,sqlalchemy,sqlalchemy) -- _StringException: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/sqlalchemy/sql/compiler.py", line 758, in visit_textual_label_reference col = with_cols[element.element] KeyError: 'res_type,tenant_id' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/<>/cloudkitty/tests/storage/v1/test_storage.py", line 249, in test_get_total_groupby_tenant_and_restype groupby=['project_id', 'type']) File "/<>/cloudkitty/storage/__init__.py", line 122, in total groupby=storage_gby) File "/<>/cloudkitty/storage/v1/sqlalchemy/__init__.py", line 134, in get_total results = q.all() File "/usr/lib/python3/dist-packages/sqlalchemy/orm/query.py", line 2925, in all return list(self) File "/usr/lib/python3/dist-packages/sqlalchemy/orm/query.py", line 3081, in __iter__ return self._execute_and_instances(context) File "/usr/lib/python3/dist-packages/sqlalchemy/orm/query.py", line 3106, in _execute_and_instances result = conn.execute(querycontext.statement, self._params) File "/usr/lib/python3/dist-packages/sqlalchemy/engine/base.py", line 980, in execute return meth(self, multiparams, params) File "/usr/lib/python3/dist-packages/sqlalchemy/sql/elements.py", line 273, in _execute_on_connection return connection._execute_clauseelement(self, multiparams, params) File "/usr/lib/python3/dist-packages/sqlalchemy/engine/base.py", line 1090, in _execute_clauseelement else None, File "", line 1, in File "/usr/lib/python3/dist-packages/sqlalchemy/sql/elements.py", line 448, in compile return self._compiler(dialect, bind=bind, **kw) File "/usr/lib/python3/dist-packages/sqlalchemy/sql/elements.py", line 454, in _compiler return dialect.statement_compiler(dialect, self, **kw) File "/usr/lib/python3/dist-packages/sqlalchemy/sql/compiler.py", line 553, in __init__ Compiled.__init__(self, dialect, statement, **kwargs) File "/usr/lib/python3/dist-packages/sqlalchemy/sql/compiler.py", line 310, in __init__ self.string =
Bug#933279: marked as done (pytables: BD on texlive-generic-extra which isn't build anymore and isn't in bullseye)
Your message dated Sun, 04 Aug 2019 13:53:19 + with message-id and subject line Bug#933279: fixed in pytables 3.5.2-2 has caused the Debian Bug report #933279, regarding pytables: 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.) -- 933279: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933279 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: pytables Version: 3.4.4-2 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. This is currently also blocking migration of your package to testing. Paul signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: pytables Source-Version: 3.5.2-2 We believe that the bug you reported is fixed in the latest version of pytables, 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. Antonio Valentino (supplier of updated pytables package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 03 Aug 2019 16:24:07 + Source: pytables Binary: python-tables python-tables-lib python-tables-dbg python3-tables python3-tables-lib python3-tables-dbg python-tables-doc python-tables-data Architecture: source Version: 3.5.2-2 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers Changed-By: Antonio Valentino Description: python-tables - hierarchical database for Python based on HDF5 python-tables-data - hierarchical database for Python based on HDF5 - test data python-tables-dbg - hierarchical database for Python based on HDF5 (debug extension) python-tables-doc - hierarchical database for Python based on HDF5 - documentation python-tables-lib - hierarchical database for Python based on HDF5 (extension) python3-tables - hierarchical database for Python3 based on HDF5 python3-tables-dbg - hierarchical database for Python 3 based on HDF5 (debug extension python3-tables-lib - hierarchical database for Python3 based on HDF5 (extension) Closes: 933279 Changes: pytables (3.5.2-2) unstable; urgency=medium . * debian/control: - replace the deprecated build dependency texlive-generic-extra, with texlive-plain-generic (Closes: #933279) - sort dependency lists * debian/patches: - new 0006-Skip-index-backcompat-tests-on-bingendian.patch * drop debian/compat file, and depend on debelper-compat. Checksums-Sha1: 6de4b28012c6496ca46bb14edb3d208eaee3d0bf 3249 pytables_3.5.2-2.dsc caa3561f71719322f8102b33ad96693bab9e5ed6 19524 pytables_3.5.2-2.debian.tar.xz Checksums-Sha256: 72ac1dbfbd65dc25f0d88d5f96fec1d431e9a48515f1aa628c16c9e1f8f704be 3249 pytables_3.5.2-2.dsc 624aa492df9f33daea424cfde8682394c9bbce9db77db3f7ce67903698dd6809 19524 pytables_3.5.2-2.debian.tar.xz Files: 1485f130a68ae22b3b805552251286fd 3249 python optional pytables_3.5.2-2.dsc 825e6ff92df83714c7592caa26ece3ff 19524 python optional pytables_3.5.2-2.debian.tar.xz -BEGIN PGP SIGNATURE- iQJCBAEBCAAsFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAl1G2hsOHHRpbGxlYUBy a2kuZGUACgkQV4oElNHGRtE8NBAAka57JF6cMYwulYnGuR9iip6CkwXSDorTkorJ tKostMeZLMlabuIzH3ePXJSflLqq1p/dR78/aZSGWt9mT0YIfktXGdC9lVurGSvB e+arby3/v2Fj+kZ+53Mze+Td1cAFwZQClV7TSjMUL1L304ERZAbT99MV38/WF16f WTE9SRKubHrpW63XfCdih/Bv76xZJdE90FuQOHFS2hitUNNQfRWyXskm4iQrld53 qEG8/I14iVwh68CfbFSleNrh4I/K1D+W/EDrJfpOw+RaU2GjKUwEYYTxRhai3Zi+ Xwdt1424ZC4x0itYbjvHWMCKUmFVy7Qbk6M3XU8cDvp7pXfZWdRupwyvGNWMUGAs ds+q8T8lxbJ1ZQFJ3TwwxKtgXcctnC5CaR4ukDnkJt1DqFESqw6YCmqEQnRU8Xc0 3BBZuPPG1MptvNtMA0VZOMgDaqpm2eToAjzotv3L1t5VtrwQAvh18PTNlVoD6X3X PDQ+ZwNVbHCttZkSch7ny2t/rv6zYs1/QtqTCn/H+o9930F9dtZehm0dUQyQ93gz iEs9jU7tjtd8+MnXar780dPD16EDql0tPzDdYlf+iMFJOoedzrzvFMnIHyV9s6SA
Bug#933845: marked as done (libpmi-pmix-dev: MPI failure in dolfin tests)
Your message dated Sun, 04 Aug 2019 13:25:50 + with message-id and subject line Bug#933845: fixed in petsc 3.11.3+dfsg1-2 has caused the Debian Bug report #933845, regarding libpmi-pmix-dev: MPI failure in dolfin 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.) -- 933845: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933845 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libpmi-pmix-dev Version: 3.1.4~rc2-1 Severity: serious Justification: breaks MPI client tests Hi Alistair and Debian science, I'm upgrading dolfin/fenics to 2019.1.0 alongside HYPRE 2.16.0, PETSc 3.11.3, pybind11 2.3.0. The tests of the libraries have passed, but the build is failing badly with an MPI error: Run C++ regressions tests (serial) Test project /home/projects/fenics/build/dolfin/obj-x86_64-linux-gnu ... Start 13: demo_eigenvalue_serial 3/51 Test #13: demo_eigenvalue_serial ***Failed0.02 sec *** The MPI_Comm_rank() function was called before MPI_INIT was invoked. *** This is disallowed by the MPI standard. *** Your MPI job will now abort. [grendel:16518] Local abort before MPI_INIT completed completed successfully, but am not able to aggregate error messages, and not able to guarantee that all other processes were killed! The same error is also triggered when running with mpirun, so the problem is not due to running an MPI-linked program as a serial job. I tested the build last week before proceeding with the upgrades and package uploads, all was fine then. The nature and the timing of the error suggests to me that pmix 3.1.4~rc2-1 (built last Thursday 1/8/2019) might be involved. It doesn't make sense that pmix should trigger an error like this, but I've filed this RC bug against pmix to halt migration while we look into it. I've raised a discussion thread with FEniCS upstream at https://fenicsproject.slack.com/archives/C26N589GV/p1564913720002300 Drew -- 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 libpmi-pmix-dev depends on: ii libpmi1-pmix 3.1.4~rc2-1 ii libpmi2-pmix 3.1.4~rc2-1 libpmi-pmix-dev recommends no packages. libpmi-pmix-dev suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: petsc Source-Version: 3.11.3+dfsg1-2 We believe that the bug you reported is fixed in the latest version of petsc, 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. Drew Parsons (supplier of updated petsc package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 04 Aug 2019 19:56:06 +0800 Source: petsc Architecture: source Version: 3.11.3+dfsg1-2 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers Changed-By: Drew Parsons Closes: 933845 Changes: petsc (3.11.3+dfsg1-2) unstable; urgency=medium . * debian patch HDF5_refactor_6a0bd752.diff applies upstream patch 6a0bd752 to keep HDF5 support from interfering with PETSc clients that do not use HDF5. Closes: #933845. Checksums-Sha1: ecc0fca30883755ac9448114230bccc4e46e9dd7 3364 petsc_3.11.3+dfsg1-2.dsc ef75086b2b29a6b9ebd3cdbb1b2f86710bca7ccd 67276 petsc_3.11.3+dfsg1-2.debian.tar.xz Checksums-Sha256: b77d197b12a41b043a0cffd53cf059578d240b0e80c79596f9ae427244837ee3 3364 petsc_3.11.3+dfsg1-2.dsc c644cd9e40b863e1777900f84a0bc5f4d0b27b6b74acb68f3d6d39663e56a317 67276 petsc_3.11.3+dfsg1-2.debian.tar.xz Files: 7f4a92831afb60930e710b249a9d756d 3364 devel optional petsc_3.11.3+dfsg1-2.dsc 95b0bbcc1fe644926a45fe6372b423f0 67276 devel optional petsc_3.11.3+dfsg1-2.debian.tar.xz -BEGIN PGP
Bug#933854: solr-jetty: Jetty refuses to start SOLR due to a probably depreceated Call
Package: solr-jetty Version: 3.6.2+dfsg-20 Severity: grave Justification: renders package unusable Hi Maintainers, Jetty refuses to start SOLR due to a (probably) depreceated call in /etc/solr/solr-jetty.xml: Here is the relevant part from journalctl: Aug 04 14:55:00 srv1 jetty9[3616]: 2019-08-04 14:55:00.970:WARN:oejx.XmlConfiguration:main: Config error at | http://www.eclipse.org/jetty/configure.dtd;> /solr /usr/share/solr/web solr.solr.home /usr/share/solr -- no debconf information
Bug#933845: Bug#933844: libpmi-pmix-dev: MPI failure in dolfin tests
On 2019-08-04 19:19, Drew Parsons wrote: Probably this is a clue: libdolfin.so should link to libpetsc.so. But it is missing in the new libdolfin.so. That means pmix is not the problem, so I'll close the bug against pmix once I can confirm. CMake logs confirm the that petsc test fail linking with /usr/lib/petscdir/petsc3.11/x86_64-linux-gnu-real/include/petscis.h:317:10: fatal error: H5Ipublic.h: No such file or directory #include ^ compilation terminated. PETSC 3.11.3 inserted H5Ipublic.h into petscis.h, requiring hdf5 header paths be included for compilation. Fixed upstream with commit 6a0bd7522af7eb76a79ca5f1af77fc9a30e8cdb2 Drew
Bug#884974: marked as done (sdpa: hardcoded mumps runtime dependency)
Your message dated Sun, 04 Aug 2019 12:22:56 + with message-id and subject line Bug#884974: fixed in sdpa 7.3.11+dfsg-1.1 has caused the Debian Bug report #884974, regarding sdpa: hardcoded mumps runtime dependency 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.) -- 884974: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884974 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: sdpa Severity: serious Version: 7.3.11+dfsg-1 Tags: patch Justification: hardcoded cruft library Hello, *please* *please* *please* drop the runtime dependency, and maybe stop using static mumps libraries, unless *really* necessary. I provided a patch in [1] but it seems to have been applied very differently, and I don't understand the reasons. [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=868505;msg=27 thanks G. signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: sdpa Source-Version: 7.3.11+dfsg-1.1 We believe that the bug you reported is fixed in the latest version of sdpa, 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 884...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Gianfranco Costamagna (supplier of updated sdpa package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 02 Aug 2019 13:46:12 +0200 Source: sdpa Binary: sdpa libsdpa-dev sdpam Architecture: source Version: 7.3.11+dfsg-1.1 Distribution: unstable Urgency: medium Maintainer: Makoto Yamashita Changed-By: Gianfranco Costamagna Description: libsdpa-dev - Callable library and examples of SDPA sdpa - High-performance package for SemiDefinite Programs sdpam - Matlab/Octave interface of SDPA Closes: 884974 Changes: sdpa (7.3.11+dfsg-1.1) unstable; urgency=medium . * Non-maintainer upload. * Drop runtime dependency on mups (Closes: #884974) Checksums-Sha1: c6c52e702b39030c9dbfceda6e4b57006443e5d7 1937 sdpa_7.3.11+dfsg-1.1.dsc 5e7b056761eeb2e2726e7dfb1b1d07bf8e5f02ce 4488 sdpa_7.3.11+dfsg-1.1.debian.tar.xz 34178d960cf92c086a082939abbe07cbeb83dc60 8738 sdpa_7.3.11+dfsg-1.1_source.buildinfo Checksums-Sha256: 76b11c31048a65a3fe622ea31ef19d72f170e96410fdaa8b2f4b6537bfed5cb0 1937 sdpa_7.3.11+dfsg-1.1.dsc 82040fcb4b3b26875430bfc966278eb2402d6a931c501f656864ecd928874f24 4488 sdpa_7.3.11+dfsg-1.1.debian.tar.xz 75050c5b117f522cf42a206134ea18dc0a487cf9031ae48307c9295489c79529 8738 sdpa_7.3.11+dfsg-1.1_source.buildinfo Files: 06b63bfa12daa28db92082f87198af62 1937 math extra sdpa_7.3.11+dfsg-1.1.dsc 27d50e8286780b457e0df366d974f689 4488 math extra sdpa_7.3.11+dfsg-1.1.debian.tar.xz 92f512b1b0df4de17443d4fab4499ad6 8738 math extra sdpa_7.3.11+dfsg-1.1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEkpeKbhleSSGCX3/w808JdE6fXdkFAl1EIpgACgkQ808JdE6f XdnKSBAAt/cv6nKRUwB7vNeHIlSWcpgBTBop3zx3HKdI3KpXS+Z8FDZibgLI94iS trNgkNcZiZ4FaUv0h6x8V+RPb1b/YJsv1vzlNxRJPOJ//b2llNQP7good6xDfj1l DD+YOI+8/Jd+z8H2lFar3vfyp49stQfvwoX8Snl8ELUVFG8PQCAg0Sbk+sfW/RBM uLBhliAXT20jNHsqUN1IZD3ivetl0yGTAk43TEF8Hxdrknh1yZlMPnkJLOjT+zS4 km5EFEUScc5ebdGWubJ3Rb0RlI9ocVGp+IXFIO2hdoucUpCr80EGvsBUoMoTqCCF Zn/fE3ssVzCVBkFHlyR0+ZxpmnOs/HZls0GJF9UngcbFAl5w1BXkaTqeHNJoYEe7 fNpKYUQ/JaVyut1Fgm4jJy34zsQGn8nTsR1scs3bgtdeN/ESd3uRrw3rm50PonIh 7XCx50WzmI1BVbo9TNGtmqvgp36uXZd2JuLAgpTgO2DlX6rqP9CdLowxvyr2KOQ/ VRxPP73ynXDGZftJHUT+xjXKXSBilGa5ZzqbFzb6idJD5IoBy/RtnXeEssJyAISu hdtxPWXAk8KEuAZ64lahPJFImAAwIK6C48UZn4E99Azhsau3CXsoYH/VJB3MPrdX wx0k6GXtZLt4CjnK/rFfOvDO0P6gBSFvZTaj6jjbD5ZZ2MXbX2s= =qZmU -END PGP SIGNATURE End Message ---
Bug#933844: marked as done (libpmi-pmix-dev: MPI failure in dolfin tests)
Your message dated Sun, 04 Aug 2019 19:32:29 +0800 with message-id <64264f585bb8c5b5e8a480981ea7d...@debian.org> and subject line Re: Bug#933844: libpmi-pmix-dev: MPI failure in dolfin tests has caused the Debian Bug report #933844, regarding libpmi-pmix-dev: MPI failure in dolfin 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.) -- 933844: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933844 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libpmi-pmix-dev Version: 3.1.4~rc2-1 Severity: serious Justification: breaks MPI client tests Hi Alistair and Debian science, I'm upgrading dolfin/fenics to 2019.1.0 alongside HYPRE 2.16.0, PETSc 3.11.3, pybind11 2.3.0. The tests of the libraries have passed, but the build is failing badly with an MPI error: Run C++ regressions tests (serial) Test project /home/projects/fenics/build/dolfin/obj-x86_64-linux-gnu ... Start 13: demo_eigenvalue_serial 3/51 Test #13: demo_eigenvalue_serial ***Failed0.02 sec *** The MPI_Comm_rank() function was called before MPI_INIT was invoked. *** This is disallowed by the MPI standard. *** Your MPI job will now abort. [grendel:16518] Local abort before MPI_INIT completed completed successfully, but am not able to aggregate error messages, and not able to guarantee that all other processes were killed! The same error is also triggered when running with mpirun, so the problem is not due to running an MPI-linked program as a serial job. I tested the build last week before proceeding with the upgrades and package uploads, all was fine then. The nature and the timing of the error suggests to me that pmix 3.1.4~rc2-1 (built last Thursday 1/8/2019) might be involved. It doesn't make sense that pmix should trigger an error like this, but I've filed this RC bug against pmix to halt migration while we look into it. I've raised a discussion thread with FEniCS upstream at https://fenicsproject.slack.com/archives/C26N589GV/p1564913720002300 Drew -- 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 libpmi-pmix-dev depends on: ii libpmi1-pmix 3.1.4~rc2-1 ii libpmi2-pmix 3.1.4~rc2-1 libpmi-pmix-dev recommends no packages. libpmi-pmix-dev suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- On 2019-08-04 19:17, Drew Parsons wrote: On 2019-08-04 19:04, Drew Parsons wrote: Probably this is a clue: libdolfin.so should link to libpetsc.so. But it is missing in the new libdolfin.so. That means pmix is not the problem, so I'll close this bug once I can confirm. Yes, dolfin's cmake could not link against the new PETSc so the build proceeded without petsc. The failing tests use petsc. The error message was misleading, it should have traced back to a petsc call. Closing the pmix bug now. This bug is a dialogue between petsc and dolfin. Drew--- End Message ---
Bug#933845: Bug#933844: libpmi-pmix-dev: MPI failure in dolfin tests
On 2019-08-04 19:04, Drew Parsons wrote: I'm upgrading dolfin/fenics to 2019.1.0 alongside HYPRE 2.16.0, PETSc 3.11.3, pybind11 2.3.0. The tests of the libraries have passed, but the build is failing badly with an MPI error: Run C++ regressions tests (serial) Test project /home/projects/fenics/build/dolfin/obj-x86_64-linux-gnu ... Start 13: demo_eigenvalue_serial 3/51 Test #13: demo_eigenvalue_serial ***Failed0.02 sec *** The MPI_Comm_rank() function was called before MPI_INIT was invoked. *** This is disallowed by the MPI standard. *** Your MPI job will now abort. [grendel:16518] Local abort before MPI_INIT completed completed successfully, but am not able to aggregate error messages, and not able to guarantee that all other processes were killed! Probably this is a clue: libdolfin.so should link to libpetsc.so. But it is missing in the new libdolfin.so. That means pmix is not the problem, so I'll close the bug against pmix once I can confirm. Drew
Bug#933848: FTBFS if cmake is installed or if built twice in a row
Source: pygalmesh Version: 0.3.6-1 Severity: serious 1) pygalmesh FTBFS if cmake is installed. Actually the build succeeds, but the resulting binary package is almost empty. With cmake installed: fakeroot debian/rules clean dh clean --with python3 --buildsystem=pybuild dh_auto_clean -O--buildsystem=pybuild I: pybuild base:217: dh_auto_clean --buildsystem=cmake dh_autoreconf_clean -O--buildsystem=pybuild dh_clean -O--buildsystem=pybuild [...] fakeroot debian/rules binary dh binary --with python3 --buildsystem=pybuild dh_testroot -O--buildsystem=pybuild dh_prep -O--buildsystem=pybuild dh_auto_install -O--buildsystem=pybuild I: pybuild base:217: dh_auto_install --buildsystem=cmake --builddirectory="/mnt/debian/packages/pygalmesh/pygalmesh-0.3.6/.pybuild/cpython3_3.7_pygalmesh/build" --destdir="/mnt/debian/packages/pygalmesh/pygalmesh-0.3.6/debian/python3-pygalmesh" -- dh_installdocs -O--buildsystem=pybuild Without cmake installed: fakeroot debian/rules clean dh clean --with python3 --buildsystem=pybuild dh_auto_clean -O--buildsystem=pybuild I: pybuild base:217: python3.7 setup.py clean running clean removing '/build/pygalmesh-0.3.6/.pybuild/cpython3_3.7_pygalmesh/build' (and everything under it) 'build/bdist.linux-amd64' does not exist -- can't clean it 'build/scripts-3.7' does not exist -- can't clean it [...] fakeroot debian/rules binary dh binary --with python3 --buildsystem=pybuild dh_testroot -O--buildsystem=pybuild dh_prep -O--buildsystem=pybuild dh_auto_install -O--buildsystem=pybuild I: pybuild base:217: /usr/bin/python3 setup.py install --root /build/pygalmesh-0.3.6/debian/python3-pygalmesh running install [... many more lines following ...] dh_installdocs -O--buildsystem=pybuild I don't understand why the bare existence of cmake causes the build process to behave differently. At least, the package should declare a Build-Conflicts: on cmake. 2) pygalmesh FTBFS when built twice in a row. This can be fixed by putting pygalmesh-from-inr.1 pygalmesh-volume-from-surface.1 in debian/clean. Best regards, Joachim -- System Information: Debian Release: 10.0 APT prefers stable-debug APT policy: (800, 'stable-debug'), (800, 'stable'), (700, 'testing-debug'), (700, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-5-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
Bug#933845: Bug#933844: libpmi-pmix-dev: MPI failure in dolfin tests
On 2019-08-04 19:17, Drew Parsons wrote: On 2019-08-04 19:04, Drew Parsons wrote: Probably this is a clue: libdolfin.so should link to libpetsc.so. But it is missing in the new libdolfin.so. That means pmix is not the problem, so I'll close this bug once I can confirm. Yes, dolfin's cmake could not link against the new PETSc so the build proceeded without petsc. The failing tests use petsc. The error message was misleading, it should have traced back to a petsc call. Closing the pmix bug now. This bug is a dialogue between petsc and dolfin. Drew
Bug#933598: marked as done (Most extensions now crash upon browser start)
Dear Michael! Debian Bug Tracking System - 03.08.19, 19:15:08 CEST: > Your message dated Sat, 03 Aug 2019 17:13:41 + > with message-id > and subject line Bug#933598: fixed in chromium 76.0.3809.87-2 > has caused the Debian Bug report #933598, > regarding Most extensions now crash upon browser start > to be marked as done. Thank you very much for the timely fix on this issue. I really appreciate it. Have a wonderful rest of the weekend. -- Martin
Bug#933844: libpmi-pmix-dev: MPI failure in dolfin tests
On 2019-08-04 19:04, Drew Parsons wrote: I'm upgrading dolfin/fenics to 2019.1.0 alongside HYPRE 2.16.0, PETSc 3.11.3, pybind11 2.3.0. The tests of the libraries have passed, but the build is failing badly with an MPI error: Run C++ regressions tests (serial) Test project /home/projects/fenics/build/dolfin/obj-x86_64-linux-gnu ... Start 13: demo_eigenvalue_serial 3/51 Test #13: demo_eigenvalue_serial ***Failed0.02 sec *** The MPI_Comm_rank() function was called before MPI_INIT was invoked. *** This is disallowed by the MPI standard. *** Your MPI job will now abort. [grendel:16518] Local abort before MPI_INIT completed completed successfully, but am not able to aggregate error messages, and not able to guarantee that all other processes were killed! Probably this is a clue: libdolfin.so should link to libpetsc.so. But it is missing in the new libdolfin.so. That means pmix is not the problem, so I'll close this bug once I can confirm. Drew
Processed: MPI failure in dolfin build tests
Processing commands for cont...@bugs.debian.org: > clone 933844 -1 Bug #933844 [libpmi-pmix-dev] libpmi-pmix-dev: MPI failure in dolfin tests Bug 933844 cloned as bug 933845 > reassign -1 libpetsc-real3.11-dev Bug #933845 [libpmi-pmix-dev] libpmi-pmix-dev: MPI failure in dolfin tests Bug reassigned from package 'libpmi-pmix-dev' to 'libpetsc-real3.11-dev'. No longer marked as found in versions pmix/3.1.4~rc2-1. Ignoring request to alter fixed versions of bug #933845 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 933844: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933844 933845: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933845 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#933844: libpmi-pmix-dev: MPI failure in dolfin tests
Package: libpmi-pmix-dev Version: 3.1.4~rc2-1 Severity: serious Justification: breaks MPI client tests Hi Alistair and Debian science, I'm upgrading dolfin/fenics to 2019.1.0 alongside HYPRE 2.16.0, PETSc 3.11.3, pybind11 2.3.0. The tests of the libraries have passed, but the build is failing badly with an MPI error: Run C++ regressions tests (serial) Test project /home/projects/fenics/build/dolfin/obj-x86_64-linux-gnu ... Start 13: demo_eigenvalue_serial 3/51 Test #13: demo_eigenvalue_serial ***Failed0.02 sec *** The MPI_Comm_rank() function was called before MPI_INIT was invoked. *** This is disallowed by the MPI standard. *** Your MPI job will now abort. [grendel:16518] Local abort before MPI_INIT completed completed successfully, but am not able to aggregate error messages, and not able to guarantee that all other processes were killed! The same error is also triggered when running with mpirun, so the problem is not due to running an MPI-linked program as a serial job. I tested the build last week before proceeding with the upgrades and package uploads, all was fine then. The nature and the timing of the error suggests to me that pmix 3.1.4~rc2-1 (built last Thursday 1/8/2019) might be involved. It doesn't make sense that pmix should trigger an error like this, but I've filed this RC bug against pmix to halt migration while we look into it. I've raised a discussion thread with FEniCS upstream at https://fenicsproject.slack.com/archives/C26N589GV/p1564913720002300 Drew -- 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 libpmi-pmix-dev depends on: ii libpmi1-pmix 3.1.4~rc2-1 ii libpmi2-pmix 3.1.4~rc2-1 libpmi-pmix-dev recommends no packages. libpmi-pmix-dev suggests no packages. -- no debconf information
Processed: Re: Bug#933835: libreoffice not start with fatal exception signal 11
Processing commands for cont...@bugs.debian.org: > tag 933835 + moreinfo Bug #933835 [libreoffice] libreoffice not start with fatal exception signal 11 Added tag(s) moreinfo. > tag 933835 + unreproducible Bug #933835 [libreoffice] libreoffice not start with fatal exception signal 11 Added tag(s) unreproducible. > tag 933835 - a11y Bug #933835 [libreoffice] libreoffice not start with fatal exception signal 11 Removed tag(s) a11y. > severity 933835 important Bug #933835 [libreoffice] libreoffice not start with fatal exception signal 11 Severity set to 'important' from 'grave' > thanks Stopping processing here. Please contact me if you need assistance. -- 933835: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933835 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#933835: libreoffice not start with fatal exception signal 11
Package: libreoffice Version: 1:6.3.0~rc2-1 Severity: grave Tags: a11y Justification: renders package unusable After normal upgradin a system from apt libre office wont start any more. Program not start and when put libreoffoce at console there is info: sanskryt@sauron:~$ libreoffice Fatal exception: Signal 11 Stack: /usr/lib/libreoffice/program/libuno_sal.so.3(+0x3bf83)[0x7fc06a40af83] /usr/lib/libreoffice/program/libuno_sal.so.3(+0x3c193)[0x7fc06a40b193] /lib/x86_64-linux-gnu/libc.so.6(+0x37840)[0x7fc06a1e9840] /usr/lib/libreoffice/program/libuno_cppu.so.3(+0x14322)[0x7fc06740b322] /usr/lib/libreoffice/program/libuno_cppu.so.3(uno_type_any_assign+0x97)[0x7fc06740a717] /usr/lib/libreoffice/program/libmergedlo.so(+0x299f047)[0x7fc06cdcb047] /usr/lib/libreoffice/program/libmergedlo.so(+0x299fe85)[0x7fc06cdcbe85] /usr/lib/libreoffice/program/libmergedlo.so(_ZN3utl10ConfigItemC2ERKN3rtl8OUStringE14ConfigItemMode+0x7b)[0x7fc06cdc104b] /usr/lib/libreoffice/program/libmergedlo.so(+0x29f0725)[0x7fc06ce1c725] /usr/lib/libreoffice/program/libmergedlo.so(_ZN19SvtSysLocaleOptionsC1Ev+0x11f)[0x7fc06ce1dc1f] /usr/lib/libreoffice/program/libmergedlo.so(_Z7InitVCLv+0x1a2)[0x7fc06d1ddab2] /usr/lib/libreoffice/program/libmergedlo.so(_Z10ImplSVMainv+0x105)[0x7fc06d1df395] /usr/lib/libreoffice/program/libmergedlo.so(soffice_main+0x91)[0x7fc06c28db41] /usr/lib/libreoffice/program/soffice.bin(+0x107b)[0x555ea9ad007b] /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xeb)[0x7fc06a1d609b] /usr/lib/libreoffice/program/soffice.bin(+0x10ba)[0x555ea9ad00ba] Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these template lines *** -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (500, 'oldstable') 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=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to pl_PL.UTF-8), LANGUAGE=pl_PL.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to pl_PL.UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libreoffice depends on: ii libreoffice-base1:6.3.0~rc2-1 ii libreoffice-calc1:6.3.0~rc2-1 ii libreoffice-core1:6.3.0~rc2-1 ii libreoffice-draw1:6.3.0~rc2-1 ii libreoffice-impress 1:6.3.0~rc2-1 ii libreoffice-math1:6.3.0~rc2-1 ii libreoffice-report-builder-bin 1:6.3.0~rc2-1 ii libreoffice-writer 1:6.3.0~rc2-1 ii python3-uno 1:6.3.0~rc2-1 Versions of packages libreoffice recommends: ii fonts-crosextra-caladea 20130214-2 ii fonts-crosextra-carlito 20130920-1 ii fonts-dejavu2.37-1 ii fonts-liberation1:1.07.4-10 ii fonts-liberation2 2.00.5-2 ii fonts-linuxlibertine5.3.0-4 ii fonts-noto-core 20181227-1 ii fonts-noto-mono 20181227-1 ii fonts-noto-ui-core 20181227-1 ii fonts-sil-gentium-basic 1.102-1 ii libreoffice-java-common 1:6.3.0~rc2-1 ii libreoffice-nlpsolver 0.9+LibO6.3.0~rc2-1 ii libreoffice-report-builder 1:6.3.0~rc2-1 ii libreoffice-script-provider-bsh 1:6.3.0~rc2-1 ii libreoffice-script-provider-js 1:6.3.0~rc2-1 ii libreoffice-script-provider-python 1:6.3.0~rc2-1 ii libreoffice-sdbc-mysql 1:6.3.0~rc2-1 ii libreoffice-sdbc-postgresql 1:6.3.0~rc2-1 ii libreoffice-wiki-publisher 1.2.0+LibO6.3.0~rc2-1 Versions of packages libreoffice suggests: ii cups-bsd 2.2.10-6 ii default-jre [java6-runtime]2:1.11-72 pn firefox-esr | thunderbird | firefox ii ghostscript9.27~dfsg-3 ii gnupg 2.2.17-3 pn gpa ii gstreamer1.0-libav 1:1.14.4-dmo3 ii gstreamer1.0-plugins-bad 1:1.14.4-dmo7 ii gstreamer1.0-plugins-base 1.14.4-dmo2 ii gstreamer1.0-plugins-good 1.14.4-dmo2 ii gstreamer1.0-plugins-ugly 1:1.14.4-dmo2 ii hunspell-en-us [hunspell-dictionary] 1:2018.04.16-1 ii hunspell-pl [hunspell-dictionary] 1:6.3.0~rc1-1 ii hunspell-ru
Bug#933792: ocaml-nox/ocaml-base-nox: missing Breaks+Replaces: ocaml-base-nox/ocaml-nox (<< 4.08)
Control: retitle -1 ocaml-base-nox: missing Breaks+Replaces: ocaml-base (<< 4.08.0-4) On 04/08/2019 05.48, Stéphane Glondu wrote: >> Preparing to unpack .../ocaml-nox_4.08.0-3_amd64.deb ... >> Unpacking ocaml-nox (4.08.0-3) over (4.05.0-11) ... >> dpkg: error processing archive >> /var/cache/apt/archives/ocaml-nox_4.08.0-3_amd64.deb (--unpack): >>trying to overwrite '/usr/lib/ocaml/VERSION', which is also in package >> ocaml-base-nox 4.05.0-11 > > No, VERSION should be in ocaml-base-nox! OK, I assumed this was an intentional move to ocaml-nox. Expecting you'll move VERSION back to ocaml-base-nox in the -4 upload, I retitled accordingly. Andreas
Processed: Re: Bug#933792: ocaml-nox/ocaml-base-nox: missing Breaks+Replaces: ocaml-base-nox/ocaml-nox (<< 4.08)
Processing control commands: > retitle -1 ocaml-base-nox: missing Breaks+Replaces: ocaml-base (<< 4.08.0-4) Bug #933792 [ocaml-nox,ocaml-base-nox] ocaml-nox/ocaml-base-nox: missing Breaks+Replaces: ocaml-base-nox/ocaml-nox (<< 4.08) Changed Bug title to 'ocaml-base-nox: missing Breaks+Replaces: ocaml-base (<< 4.08.0-4)' from 'ocaml-nox/ocaml-base-nox: missing Breaks+Replaces: ocaml-base-nox/ocaml-nox (<< 4.08)'. -- 933792: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933792 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: libxslt: diff for NMU version 1.1.32-2.1
Processing control commands: > tags 926895 + patch Bug #926895 [src:libxslt] libxslt: CVE-2019-11068 Added tag(s) patch. > tags 926895 + pending Bug #926895 [src:libxslt] libxslt: CVE-2019-11068 Added tag(s) pending. > tags 931320 + patch Bug #931320 [src:libxslt] libxslt: CVE-2019-13118 Added tag(s) patch. > tags 931320 + pending Bug #931320 [src:libxslt] libxslt: CVE-2019-13118 Added tag(s) pending. > tags 931321 + patch Bug #931321 [src:libxslt] libxslt: CVE-2019-13117 Added tag(s) patch. > tags 931321 + pending Bug #931321 [src:libxslt] libxslt: CVE-2019-13117 Added tag(s) pending. > tags 933743 + patch Bug #933743 [libxslt1.1] LibXSLT in Debian stable has three unpatched security vulnerabilities Added tag(s) patch. > tags 933743 + pending Bug #933743 [libxslt1.1] LibXSLT in Debian stable has three unpatched security vulnerabilities Added tag(s) pending. -- 926895: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926895 931320: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931320 931321: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931321 933743: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933743 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#933743: libxslt: diff for NMU version 1.1.32-2.1
Control: tags 926895 + patch
Control: tags 926895 + pending
Control: tags 931320 + patch
Control: tags 931320 + pending
Control: tags 931321 + patch
Control: tags 931321 + pending
Control: tags 933743 + patch
Control: tags 933743 + pending
Dear maintainer,
I've prepared an NMU for libxslt (versioned as 1.1.32-2.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.
Regards,
Salvatore
diff -Nru libxslt-1.1.32/debian/changelog libxslt-1.1.32/debian/changelog
--- libxslt-1.1.32/debian/changelog 2018-05-26 23:12:37.0 +0200
+++ libxslt-1.1.32/debian/changelog 2019-08-04 08:14:05.0 +0200
@@ -1,3 +1,14 @@
+libxslt (1.1.32-2.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Fix security framework bypass (CVE-2019-11068) (Closes: #926895, #933743)
+ * Fix uninitialized read of xsl:number token (CVE-2019-13117)
+(Closes: #931321, #933743)
+ * Fix uninitialized read with UTF-8 grouping chars (CVE-2019-13118)
+(Closes: #931320, #933743)
+
+ -- Salvatore Bonaccorso Sun, 04 Aug 2019 08:14:05 +0200
+
libxslt (1.1.32-2) unstable; urgency=medium
* Team upload.
diff -Nru libxslt-1.1.32/debian/patches/0006-Fix-security-framework-bypass.patch libxslt-1.1.32/debian/patches/0006-Fix-security-framework-bypass.patch
--- libxslt-1.1.32/debian/patches/0006-Fix-security-framework-bypass.patch 1970-01-01 01:00:00.0 +0100
+++ libxslt-1.1.32/debian/patches/0006-Fix-security-framework-bypass.patch 2019-08-04 08:14:05.0 +0200
@@ -0,0 +1,124 @@
+From: Nick Wellnhofer
+Date: Sun, 24 Mar 2019 09:51:39 +0100
+Subject: Fix security framework bypass
+Origin: https://gitlab.gnome.org/GNOME/libxslt/commit/e03553605b45c88f0b4b2980adfbbb8f6fca2fd6
+Bug-Debian-Security: https://security-tracker.debian.org/tracker/CVE-2019-11068
+Bug: https://gitlab.gnome.org/GNOME/libxslt/issues/12
+Bug-Debian: https://bugs.debian.org/926895
+Bug-Debian: https://bugs.debian.org/933743
+
+xsltCheckRead and xsltCheckWrite return -1 in case of error but callers
+don't check for this condition and allow access. With a specially
+crafted URL, xsltCheckRead could be tricked into returning an error
+because of a supposedly invalid URL that would still be loaded
+succesfully later on.
+
+Fixes #12.
+
+Thanks to Felix Wilhelm for the report.
+---
+ libxslt/documents.c | 18 ++
+ libxslt/imports.c | 9 +
+ libxslt/transform.c | 9 +
+ libxslt/xslt.c | 9 +
+ 4 files changed, 25 insertions(+), 20 deletions(-)
+
+diff --git a/libxslt/documents.c b/libxslt/documents.c
+index 3f3a7312ca8e..4aad11bbd1a9 100644
+--- a/libxslt/documents.c
b/libxslt/documents.c
+@@ -296,10 +296,11 @@ xsltLoadDocument(xsltTransformContextPtr ctxt, const xmlChar *URI) {
+ int res;
+
+ res = xsltCheckRead(ctxt->sec, ctxt, URI);
+- if (res == 0) {
+- xsltTransformError(ctxt, NULL, NULL,
+- "xsltLoadDocument: read rights for %s denied\n",
+- URI);
++ if (res <= 0) {
++if (res == 0)
++xsltTransformError(ctxt, NULL, NULL,
++ "xsltLoadDocument: read rights for %s denied\n",
++ URI);
+ return(NULL);
+ }
+ }
+@@ -372,10 +373,11 @@ xsltLoadStyleDocument(xsltStylesheetPtr style, const xmlChar *URI) {
+ int res;
+
+ res = xsltCheckRead(sec, NULL, URI);
+- if (res == 0) {
+- xsltTransformError(NULL, NULL, NULL,
+- "xsltLoadStyleDocument: read rights for %s denied\n",
+- URI);
++ if (res <= 0) {
++if (res == 0)
++xsltTransformError(NULL, NULL, NULL,
++ "xsltLoadStyleDocument: read rights for %s denied\n",
++ URI);
+ return(NULL);
+ }
+ }
+diff --git a/libxslt/imports.c b/libxslt/imports.c
+index 874870cca90e..3783b2476d9e 100644
+--- a/libxslt/imports.c
b/libxslt/imports.c
+@@ -130,10 +130,11 @@ xsltParseStylesheetImport(xsltStylesheetPtr style, xmlNodePtr cur) {
+ int secres;
+
+ secres = xsltCheckRead(sec, NULL, URI);
+- if (secres == 0) {
+- xsltTransformError(NULL, NULL, NULL,
+- "xsl:import: read rights for %s denied\n",
+- URI);
++ if (secres <= 0) {
++if (secres == 0)
++xsltTransformError(NULL, NULL, NULL,
++ "xsl:import: read rights for %s denied\n",
++ URI);
+ goto error;
+ }
+ }
+diff --git a/libxslt/transform.c b/libxslt/transform.c
+index 13793914f5d3..0636dbd0a242 100644
+--- a/libxslt/transform.c
b/libxslt/transform.c
+@@ -3493,10 +3493,11 @@ xsltDocumentElem(xsltTransformContextPtr ctxt, xmlNodePtr node,
+ */
+ if (ctxt->sec != NULL) {
+ ret = xsltCheckWrite(ctxt->sec, ctxt, filename);
+- if (ret == 0) {
+- xsltTransformError(ctxt, NULL, inst,
+- "xsltDocumentElem: write rights for %s denied\n",
+- filename);
++ if (ret <= 0) {
++if (ret == 0)
++xsltTransformError(ctxt, NULL,
Processed: libxslt: diff for NMU version 1.1.32-2.1
Processing control commands: > tags 926895 + patch Bug #926895 [src:libxslt] libxslt: CVE-2019-11068 Ignoring request to alter tags of bug #926895 to the same tags previously set > tags 926895 + pending Bug #926895 [src:libxslt] libxslt: CVE-2019-11068 Ignoring request to alter tags of bug #926895 to the same tags previously set > tags 931320 + patch Bug #931320 [src:libxslt] libxslt: CVE-2019-13118 Ignoring request to alter tags of bug #931320 to the same tags previously set > tags 931320 + pending Bug #931320 [src:libxslt] libxslt: CVE-2019-13118 Ignoring request to alter tags of bug #931320 to the same tags previously set > tags 931321 + patch Bug #931321 [src:libxslt] libxslt: CVE-2019-13117 Ignoring request to alter tags of bug #931321 to the same tags previously set > tags 931321 + pending Bug #931321 [src:libxslt] libxslt: CVE-2019-13117 Ignoring request to alter tags of bug #931321 to the same tags previously set > tags 933743 + patch Bug #933743 [libxslt1.1] LibXSLT in Debian stable has three unpatched security vulnerabilities Ignoring request to alter tags of bug #933743 to the same tags previously set > tags 933743 + pending Bug #933743 [libxslt1.1] LibXSLT in Debian stable has three unpatched security vulnerabilities Ignoring request to alter tags of bug #933743 to the same tags previously set -- 926895: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926895 931320: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931320 931321: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931321 933743: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933743 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: libxslt: diff for NMU version 1.1.32-2.1
Processing control commands: > tags 926895 + patch Bug #926895 [src:libxslt] libxslt: CVE-2019-11068 Ignoring request to alter tags of bug #926895 to the same tags previously set > tags 926895 + pending Bug #926895 [src:libxslt] libxslt: CVE-2019-11068 Ignoring request to alter tags of bug #926895 to the same tags previously set > tags 931320 + patch Bug #931320 [src:libxslt] libxslt: CVE-2019-13118 Ignoring request to alter tags of bug #931320 to the same tags previously set > tags 931320 + pending Bug #931320 [src:libxslt] libxslt: CVE-2019-13118 Ignoring request to alter tags of bug #931320 to the same tags previously set > tags 931321 + patch Bug #931321 [src:libxslt] libxslt: CVE-2019-13117 Ignoring request to alter tags of bug #931321 to the same tags previously set > tags 931321 + pending Bug #931321 [src:libxslt] libxslt: CVE-2019-13117 Ignoring request to alter tags of bug #931321 to the same tags previously set > tags 933743 + patch Bug #933743 [libxslt1.1] LibXSLT in Debian stable has three unpatched security vulnerabilities Ignoring request to alter tags of bug #933743 to the same tags previously set > tags 933743 + pending Bug #933743 [libxslt1.1] LibXSLT in Debian stable has three unpatched security vulnerabilities Ignoring request to alter tags of bug #933743 to the same tags previously set -- 926895: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926895 931320: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931320 931321: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931321 933743: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933743 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: libxslt: diff for NMU version 1.1.32-2.1
Processing control commands: > tags 926895 + patch Bug #926895 [src:libxslt] libxslt: CVE-2019-11068 Ignoring request to alter tags of bug #926895 to the same tags previously set > tags 926895 + pending Bug #926895 [src:libxslt] libxslt: CVE-2019-11068 Ignoring request to alter tags of bug #926895 to the same tags previously set > tags 931320 + patch Bug #931320 [src:libxslt] libxslt: CVE-2019-13118 Ignoring request to alter tags of bug #931320 to the same tags previously set > tags 931320 + pending Bug #931320 [src:libxslt] libxslt: CVE-2019-13118 Ignoring request to alter tags of bug #931320 to the same tags previously set > tags 931321 + patch Bug #931321 [src:libxslt] libxslt: CVE-2019-13117 Ignoring request to alter tags of bug #931321 to the same tags previously set > tags 931321 + pending Bug #931321 [src:libxslt] libxslt: CVE-2019-13117 Ignoring request to alter tags of bug #931321 to the same tags previously set > tags 933743 + patch Bug #933743 [libxslt1.1] LibXSLT in Debian stable has three unpatched security vulnerabilities Ignoring request to alter tags of bug #933743 to the same tags previously set > tags 933743 + pending Bug #933743 [libxslt1.1] LibXSLT in Debian stable has three unpatched security vulnerabilities Ignoring request to alter tags of bug #933743 to the same tags previously set -- 926895: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926895 931320: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931320 931321: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931321 933743: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933743 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#933743: LibXSLT in Debian stable has three unpatched security vulnerabilities
Hi Daniel, On Sat, Aug 03, 2019 at 08:57:56PM -0400, Daniel Richard G. wrote: > Hi Salvatore, > > On Sat, 2019 Aug 3 09:32-04:00, Salvatore Bonaccorso wrote: > > > > As you can see from the security-tracker btw, for all three there are > > bugs filled already. So why a new bug for all three together? :) > > The earliest CVE is nearly four months old, and patches already exist. I > filed the bug since it seems a sid/stable update has been overlooked... Sure it might have been overlooked, but pinging the existing bug would have been less overhead to now as well start tracking this one as well adjusting metadata etc. But no worries. > > Btw, they do not warrant a DSA, but LTS might not classify them > > similarly as for stretch and buster, so there was a DLA because there > > is no point release in LTS. > > The CVSS severity scores are fairly high for CVE-2019-11068... don't > DSAs include less-exploitable issues than this? (I'm pretty sure a > number of network-facing applications use LibXSLT) CVSS severity scores are really very dependent and who assess it. I guess you are refering to the ones as assessed by NVD. Agreed though that Felix Wilhelm has provided a nice exploiting vector example in the upstream issue for local file access depending on context of how libxslt would be used. Anyway I prepared a non-maintainer upload for libxslt adressing all three CVEs in unstable and uploaded it to DELAYED/2 and create a merge request on salsa. Regards, Salvatore
