Bug#1082700: marked as done (txtorcon: FTBFS: failing tests)
Your message dated Sun, 10 Nov 2024 09:19:28 +
with message-id
and subject line Bug#1082700: fixed in txtorcon 24.8.0-1
has caused the Debian Bug report #1082700,
regarding txtorcon: FTBFS: failing 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.)
--
1082700: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1082700
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:txtorcon
Version: 23.11.0-1
Severity: serious
Tags: ftbfs
Dear maintainer:
During a rebuild of all packages in unstable, your package failed to build:
[...]
debian/rules binary
dh binary --with=python3,sphinxdoc --buildsystem=pybuild
dh_update_autotools_config -O--buildsystem=pybuild
dh_autoreconf -O--buildsystem=pybuild
dh_auto_configure -O--buildsystem=pybuild
I: pybuild base:311: python3.12 setup.py config
running config
debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
PYTHONPATH=. http_proxy='127.0.0.1:9' sphinx-build -N -bhtml docs/
docs/_build/html # HTML generator
Running Sphinx v7.4.7
loading translations [en]... done
making output directory... done
Converting `source_suffix = '.rst'` to `source_suffix = {'.rst':
'restructuredtext'}`.
[autosummary] generating autosummary for: examples.rst, guide.rst, hacking.rst,
index.rst, installing.rst, interop_asyncio.rst, introduction.rst,
release-checklist.rst, releases.rst, txtorcon-config.rst,
txtorcon-controller.rst, txtorcon-endpoints.rst, txtorcon-interface.rst,
txtorcon-onion.rst, txtorcon-protocol.rst, txtorcon-socks.rst,
txtorcon-state.rst, txtorcon-util.rst, txtorcon.rst
building [mo]: targets for 0 po files that are out of date
writing output...
building [html]: targets for 19 source files that are out of date
updating environment: [new config] 19 added, 0 changed, 0 removed
reading sources... [ 5%] examples
reading sources... [ 11%] guide
reading sources... [ 16%] hacking
reading sources... [ 21%] index
reading sources... [ 26%] installing
reading sources... [ 32%] interop_asyncio
reading sources... [ 37%] introduction
reading sources... [ 42%] release-checklist
reading sources... [ 47%] releases
reading sources... [ 53%] txtorcon
reading sources... [ 58%] txtorcon-config
reading sources... [ 63%] txtorcon-controller
reading sources... [ 68%] txtorcon-endpoints
reading sources... [ 74%] txtorcon-interface
reading sources... [ 79%] txtorcon-onion
reading sources... [ 84%] txtorcon-protocol
reading sources... [ 89%] txtorcon-socks
reading sources... [ 95%] txtorcon-state
reading sources... [100%] txtorcon-util
/<>/docs/guide.rst:209: ERROR: Unknown directive type "fixme".
.. fixme:: why doesn't dir() work; fix it, or mention it here
/<>/docs/guide.rst:429: ERROR: Unexpected indentation.
/<>/docs/index.rst:18: ERROR: Unknown directive type "comment".
.. comment::
+---+-+-+
| Twisted | 15.5.0+ | 16.3.0+ |
+===+=+=+
| Python 2.7+ |✓|✓|
+---+-+-+
| Python 3.5+ |✓|✓|
+---+-+-+
| PyPy 5.0.0+ |✓|✓|
+---+-+-+
/<>/docs/release-checklist.rst:39: ERROR: Unexpected indentation.
/<>/docs/release-checklist.rst:41: WARNING: Block quote ends
without a blank line; unexpected unindent.
/<>/docs/releases.rst:38: WARNING: Block quote ends without a
blank line; unexpected unindent.
/<>/docs/releases.rst:4: WARNING: Duplicate explicit target name:
"pypi".
/<>/docs/releases.rst:4: WARNING: Duplicate explicit target name:
"github-sig".
/<>/docs/releases.rst:4: WARNING: Duplicate explicit target name:
"source".
/<>/docs/releases.rst:4: WARNING: Duplicate explicit target name:
"pypi".
/<>/docs/releases.rst:4: WARNING: Duplicate explicit target name:
"github-sig".
/<>/docs/releases.rst:4: WARNING: Duplicate explicit target name:
"source".
/<>/docs/releases.rst:4: WARNING: Duplicate explicit target name:
"pypi".
/<>/docs/releases.rst:4: WARNING: Duplicate explicit target name:
"github-sig".
/<>/docs/releases.rst:4: WARNING: Duplicate explicit target name:
"source".
/<>/docs/releases.rst:4: WARNING: Duplicate explicit target name:
"
Bug#1086779: marked as done (lskat depends on kdegames-card-data-kf6 but only kdegames-card-data 4:24.08.2-2 exists)
Your message dated Sun, 10 Nov 2024 09:06:29 + with message-id and subject line Bug#1086779: fixed in lskat 4:24.08.2-2 has caused the Debian Bug report #1086779, regarding lskat depends on kdegames-card-data-kf6 but only kdegames-card-data 4:24.08.2-2 exists 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.) -- 1086779: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1086779 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: lskat Version: 4:24.08.2-1 Severity: important apt -t experimental install lskat 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: Unsatisfied dependencies: lskat : Depends: kdegames-card-data-kf6 but it is not installable apt-cache search card-data libchipcard-data - configuration files for libchipcard kdegames-card-data-kf5 - card decks for KDE games belcard-data - VCard standard format manipulation library kdegames-card-data - card decks for KDE games apt -s -t experimental install kdegames-card-data The following packages were automatically installed and are no longer required: libfreecell-solver0 lskat-data Use 'apt autoremove' to remove them. Installing: kdegames-card-data REMOVING: kdegames-card-data-kf5 kpat lskat -- System Information: Debian Release: trixie/sid APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.6.59 (SMP w/16 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE Locale: LANG=fr_FR.UTF8, LC_CTYPE=fr_FR.UTF8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/bash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages lskat depends on: ii kdegames-card-data-kf5 4:22.12.3-1 ii libc6 2.40-3 ii libkf5configcore5 5.115.0-2+b1 ii libkf5coreaddons5 5.115.0-2+b1 ii libkf5crash55.115.0-2+b1 ii libkf5guiaddons55.115.0-4 ii libkf5i18n5 5.115.1-2+b3 ii libkf5kdegames7 4:22.12.3-1+b2 ii libkf5widgetsaddons55.115.0-2+b1 ii libkf5xmlgui5 5.115.0-2+b3 ii libqt5core5t64 5.15.15+dfsg-2 ii libqt5gui5t64 5.15.15+dfsg-2 ii libqt5svg5 5.15.15-2 ii libqt5widgets5t64 5.15.15+dfsg-2 ii libstdc++6 14.2.0-8 ii lskat-data 4:24.08.2-1 lskat recommends no packages. lskat suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: lskat Source-Version: 4:24.08.2-2 Done: Aurélien COUDERC We believe that the bug you reported is fixed in the latest version of lskat, 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 1086...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Aurélien COUDERC (supplier of updated lskat package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 07 Nov 2024 11:55:10 +0100 Source: lskat Architecture: source Version: 4:24.08.2-2 Distribution: experimental Urgency: medium Maintainer: Debian Qt/KDE Maintainers Changed-By: Aurélien COUDERC Closes: 1086779 Changes: lskat (4:24.08.2-2) experimental; urgency=medium . [ Aurélien COUDERC ] * Fix dependency on kdegames-card-data. (Closes: #1086779) * Switch to declarative KF6 debhelper build sequence. * Drop obsolete Breaks/Replaces. * Build with hardening=+all build hardening flag. * Refresh upstream metadata. Checksums-Sha1: b20f8c79ed3204ae4d3b3bc81dcd548d6d7dd3fc 2884 lskat_24.08.2-2.dsc 15bafdfdfc41e9503aac7ba34c69ec255a625cf3 16020 lskat_24.08.2-2.debian.tar.xz 5d5194770471befb9dd45012a80fffa77abe61e8 18236 lskat_24.08.2-2_amd64.buildinfo Checksums-Sha256: 25ac3242142d5476f727
Bug#985017: marked as done (python3-whoosh: SyntaxWarning during package installation)
Your message dated Sun, 10 Nov 2024 04:04:20 + with message-id and subject line Bug#985017: fixed in python-whoosh 2.7.4+git6-g9134ad92-9 has caused the Debian Bug report #985017, regarding python3-whoosh: SyntaxWarning during package installation 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.) -- 985017: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985017 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python3-whoosh Version: 2.7.4+git6-g9134ad92-5 Severity: important User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package emits a SyntaxWarning during installation: Setting up python3-whoosh (2.7.4+git6-g9134ad92-5) ... /usr/lib/python3/dist-packages/whoosh/codec/whoosh3.py:1116: SyntaxWarning: "is" with a literal. Did you mean "=="? elif fixedsize is 0: Andreas --- End Message --- --- Begin Message --- Source: python-whoosh Source-Version: 2.7.4+git6-g9134ad92-9 Done: Emmanuel Arias We believe that the bug you reported is fixed in the latest version of python-whoosh, 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 985...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Emmanuel Arias (supplier of updated python-whoosh 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, 10 Nov 2024 00:24:28 -0300 Source: python-whoosh Architecture: source Version: 2.7.4+git6-g9134ad92-9 Distribution: unstable Urgency: medium Maintainer: Debian Python Team Changed-By: Emmanuel Arias Closes: 985017 1078666 Changes: python-whoosh (2.7.4+git6-g9134ad92-9) unstable; urgency=medium . * Team upload. * d/upstream/metadata: Remove Homepage key from metadata. * d/patches/0005-fix-weird-non-idiomatic-line.patch: Add patch to avoid SytanxWarning for the use of 'is' during the comparation between numbers (Closes: #985017). * d/patches/0006-avoid-syntax-warning.patch: Add patch to avoid Syntax warning on scape string (Closes: #1078666). Checksums-Sha1: d00603ae45453eb2ea569027a7272cf5ad27ce90 2313 python-whoosh_2.7.4+git6-g9134ad92-9.dsc 9e0008731907a6c30e4368890b3dbadbba6c111d 12580 python-whoosh_2.7.4+git6-g9134ad92-9.debian.tar.xz e751c19791ebe3901c133b28c4098b6dce374ee3 8606 python-whoosh_2.7.4+git6-g9134ad92-9_amd64.buildinfo Checksums-Sha256: fea76c714e13d2a321c67d0c1426e8304e27a26f1841706b4eceef675aed8e70 2313 python-whoosh_2.7.4+git6-g9134ad92-9.dsc 0bade3c8747bcc913044e4d7bae21d62076860c0232cb5e00c02e5762df3b61a 12580 python-whoosh_2.7.4+git6-g9134ad92-9.debian.tar.xz 8ac5d55e062cc9285d1d7bb9d6948b2b0f777bb58bf4c019b0b7824933a096ba 8606 python-whoosh_2.7.4+git6-g9134ad92-9_amd64.buildinfo Files: f018c4985333fe35e34b1142178459c1 2313 python optional python-whoosh_2.7.4+git6-g9134ad92-9.dsc 5815942e3923f8b77a3b28c84667c0d9 12580 python optional python-whoosh_2.7.4+git6-g9134ad92-9.debian.tar.xz 286e4cf11946df91a1d56d008c26e4f2 8606 python optional python-whoosh_2.7.4+git6-g9134ad92-9_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJGBAEBCgAwFiEEE3lnVbvHK7ir4q61+p3sXeEcY/EFAmcwKz0SHGVhbWFudUBk ZWJpYW4ub3JnAAoJEPqd7F3hHGPxDFMQALvO9QOy9oALhVClrR23IfAeezgxc0Cj ubyIM9lYdiPt6AsPf/7uYVYR0tTw4eurMvt+nsPg88xvFHGTwQvJ6c3IUrSOeU1L 7qONrjDbo57wuQ5MJCQVNNYoY6njEHqWcZBryuWF7MmGKYkdziCzula6wFLNIHJb m6pojFTfz8oYAvKRRP5wOdLeBpMaQ6CfdB19ct816lzsgDXYn3Ozb/zuMXRuogdh QaAS6sc143vdjUPeF631GQFEHoXP8UUdUqyMdOuTik6lG5NQRGxXz19dyAq5lyB5 7k811fsa26oBki4jjet1b5VtKBrWFzdvfd9XnHAiWojWYHxgbTILKBq75NR12B4C GIjdv/7T+k1A8ng2LHhhwHr0eXHOlcH27hc0mHSTRQu/W0tTQb3WspEPwJ4lQYUS XD9euq/wU05dZ2d+/pW/z7+o452ol0lxdIF1hUcrI1HKz/TfYF4PkD20Jr1uwhzm m6nToc59YI2GYd0RvsENYMxvpzvgJVgzI0DS0Do4TCD668mCtm1Dkq4bSu35MZ9l Zo1NU1yU3hqUgCRT/Fts08kEjWNi0MSS1drWXGJXM7oxOaTmBM92ZIfQmP+SZMlo 76vDAeFysHowG2LbNaKelIuSSQANrAx0xAdEAJulZyx2cWxeASEBdZKx6TwgPk4n TPx543XbJjIE =Xeh7 -END PGP SIGNATURE- pgpRl96xGDux8.pgp Description: PGP signature --- End Message ---
Bug#1078666: marked as done (python3-whoosh: Many syntax errors with Python12)
Your message dated Sun, 10 Nov 2024 04:04:21 +
with message-id
and subject line Bug#1078666: fixed in python-whoosh 2.7.4+git6-g9134ad92-9
has caused the Debian Bug report #1078666,
regarding python3-whoosh: Many syntax errors with Python12
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.)
--
1078666: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1078666
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-whoosh
Version: 2.7.4+git6-g9134ad92-8
Severity: normal
Tags: patch
Dear Maintainer,
I have whoosh installed as a dependency for the mailman3 suite.
Whenever it runs I see:
/usr/lib/python3/dist-packages/whoosh/analysis/filters.py:50: SyntaxWarning:
invalid escape sequence '\w'
url_pattern = rcompile("""
/usr/lib/python3/dist-packages/whoosh/analysis/filters.py:148: SyntaxWarning:
invalid escape sequence '\S'
"""Interleaves the results of two or more filters (or filter chains).
/usr/lib/python3/dist-packages/whoosh/analysis/intraword.py:37: SyntaxWarning:
invalid escape sequence '\S'
"""Given a set of words (or any object with a ``__contains__`` method),
/usr/lib/python3/dist-packages/whoosh/analysis/intraword.py:224: SyntaxWarning:
invalid escape sequence '\S'
"""Splits words into subwords and performs optional transformations on
/usr/lib/python3/dist-packages/whoosh/analysis/intraword.py:285: SyntaxWarning:
invalid escape sequence '\|'
def __init__(self, delims=u("-_'\"()!@#$%^&*[]{}<>\|;:,./?`~=+"),
/usr/lib/python3/dist-packages/whoosh/codec/whoosh3.py:1116: SyntaxWarning:
"is" with 'int' literal. Did you mean "=="?
elif fixedsize is 0:
I get my email inbox spammed with this once an hour as part of
the indexing process for mailman3-web.
-- System Information:
Debian Release: trixie/sid
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500,
'unstable'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 6.10.4-cloud-amd64 (SMP w/1 CPU thread; PREEMPT)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages python3-whoosh depends on:
ii python3 3.12.5-1
python3-whoosh recommends no packages.
Versions of packages python3-whoosh suggests:
pn python-whoosh-doc
-- no debconf information
Index: python-whoosh-2.7.4+git6-g9134ad92/src/whoosh/analysis/filters.py
===
--- python-whoosh-2.7.4+git6-g9134ad92.orig/src/whoosh/analysis/filters.py
+++ python-whoosh-2.7.4+git6-g9134ad92/src/whoosh/analysis/filters.py
@@ -47,11 +47,11 @@ STOP_WORDS = frozenset(('a', 'an', 'and'
# Simple pattern for filtering URLs, may be useful
-url_pattern = rcompile("""
+url_pattern = rcompile(r"""
(
[A-Za-z+]+:// # URL protocol
-\\S+? # URL body
-(?=\\s|[.]\\s|$|[.]$) # Stop at space/end, or a dot followed by space/end
+\S+? # URL body
+(?=\s|[.]\s|$|[.]$) # Stop at space/end, or a dot followed by space/end
) | ( # or...
\w+([:.]?\w+)* # word characters, with opt. internal colons/dots
)
@@ -155,7 +155,7 @@ class TeeFilter(Filter):
>>> f1 = LowercaseFilter()
>>> # In the other branch, we'll reverse the tokens
>>> f2 = ReverseTextFilter()
->>> ana = RegexTokenizer(r"\S+") | TeeFilter(f1, f2)
+>>> ana = RegexTokenizer(r"\\S+") | TeeFilter(f1, f2)
>>> [token.text for token in ana(target)]
["alfa", "AFLA", "bravo", "OVARB", "charlie", "EILRAHC"]
@@ -164,7 +164,7 @@ class TeeFilter(Filter):
>>> f1 = PassFilter()
>>> f2 = BiWordFilter()
->>> ana = RegexTokenizer(r"\S+") | TeeFilter(f1, f2) | LowercaseFilter()
+>>> ana = RegexTokenizer(r"\\S+") | TeeFilter(f1, f2) | LowercaseFilter()
>>> [token.text for token in ana(target)]
["alfa", "alfa-bravo", "bravo", "bravo-charlie", "charlie"]
"""
Index
Bug#1075684: marked as done (xshisen: ftbfs with GCC-14)
Your message dated Sun, 10 Nov 2024 03:34:15 +
with message-id
and subject line Bug#1075684: fixed in xshisen 1:1.51-10
has caused the Debian Bug report #1075684,
regarding xshisen: ftbfs with GCC-14
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.)
--
1075684: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075684
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:xshisen
Version: 1:1.51-9
Severity: important
Tags: sid trixie
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-14
[This bug is targeted to the upcoming trixie release]
Please keep this issue open in the bug tracker for the package it
was filed for. If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.
The package fails to build in a test rebuild on at least amd64 with
gcc-14/g++-14, but succeeds to build with gcc-13/g++-13. The
severity of this report will be raised before the trixie release.
The full build log can be found at:
http://qa-logs.debian.net/2024/07/01/xshisen_1.51-9_unstable_gccexp.log
The last lines of the build log are at the end of this report.
To build with GCC 14, either set CC=gcc-14 CXX=g++-14 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.
apt-get -t=experimental install g++
Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-14/porting_to.html
[...]
APT_CONFIG=/var/lib/sbuild/apt.conf
HOME=/sbuild-nonexistent
LANG=C.UTF-8
LC_ALL=C.UTF-8
LOGNAME=user42
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
SCHROOT_ALIAS_NAME=unstable
SCHROOT_CHROOT_NAME=sid-amd64-sbuild
SCHROOT_COMMAND=env
SCHROOT_GID=1001
SCHROOT_GROUP=user42
SCHROOT_SESSION_ID=sid-amd64-sbuild-9f0f4bdf-aaea-4ea0-b606-04ea78554ca4
SCHROOT_UID=1001
SCHROOT_USER=user42
SHELL=/bin/sh
USER=user42
dpkg-buildpackage
-
Command: dpkg-buildpackage --sanitize-env -us -uc -b -rfakeroot
dpkg-buildpackage: info: source package xshisen
dpkg-buildpackage: info: source version 1:1.51-9
dpkg-buildpackage: info: source distribution unstable
dpkg-buildpackage: info: source changed by Petter Reinholdtsen
dpkg-source --before-build .
dpkg-buildpackage: info: host architecture amd64
debian/rules clean
dh clean --without autoreconf
dh_clean
debian/rules binary
dh binary --without autoreconf
dh_update_autotools_config
debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
dh_auto_configure -- --sharedstatedir="/var/games" \
--bindir="/usr/games" \
--datadir="/usr/share/games" \
--with-x11-resource=/etc/X11 \
--x-includes=/usr/X11R6/include \
--x-libraries=/usr/X11R6/lib \
--with-motif
./configure --build=x86_64-linux-gnu --prefix=/usr
--includedir=\${prefix}/include --mandir=\${prefix}/share/man
--infodir=\${prefix}/share/info --sysconfdir=/etc --localstatedir=/var
--disable-option-checking --disable-silent-rules
--libdir=\${prefix}/lib/x86_64-linux-gnu
--libexecdir=\${prefix}/lib/x86_64-linux-gnu --disable-maintainer-mode
--disable-dependency-tracking --sharedstatedir=/var/games --bindir=/usr/games
--datadir=/usr/share/games --with-x11-resource=/etc/X11
--x-includes=/usr/X11R6/include --x-libraries=/usr/X11R6/lib --with-motif
creating cache ./config.cache
checking for gcc... x86_64-linux-gnu-gcc
checking whether the C compiler (x86_64-linux-gnu-gcc -g -O2
-Werror=implicit-function-declaration -ffile-prefix-map=/<>=.
-fstack-protector-strong -fstack-clash-protection -Wformat
-Werror=format-security -fcf-protection -Wl,-z,relro) works... no
configure: error: installation or configuration problem: C compiler cannot
create executables.
tail -v -n \+0 config.log
==> config.log <==
This file contains any messages produced by compilers while
running configure, to aid debugging if configure makes a mistake.
configure:547: checking for gcc
configure:660: checking whether the C compiler (x86_64-linux-gnu-gcc -g -O2
-Werror=implicit-function-declaration -ffile-prefix-map=/<>=.
-fstack-protector-strong -fstack-clash-protection -Wformat
-Werror=format-security -fcf-prote
Bug#671343: marked as done (mayavi2: FTBFS if built twice in a row: unrepresentable changes to source)
Your message dated Sun, 10 Nov 2024 02:49:34 + with message-id and subject line Re: mayavi2: FTBFS if built twice in a row: unrepresentable changes to source has caused the Debian Bug report #671343, regarding mayavi2: FTBFS if built twice in a row: unrepresentable changes to source 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.) -- 671343: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=671343 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: mayavi2 Version: 4.1.0-1 Severity: important User: debian...@lists.debian.org Usertags: qa-doublebuild mayavi2 FTBFS if built twice in a row: | dpkg-source -b mayavi2-4.1.0 | dpkg-source: info: using source format `3.0 (quilt)' | dpkg-source: info: building mayavi2 using existing ./mayavi2_4.1.0.orig.tar.gz | dpkg-source: warning: ignoring deletion of file mayavi/images/m2_about.jpg | dpkg-source: error: cannot represent change to mayavi2-4.1.0/tvtk/tvtk_classes.zip: binary file contents changed | dpkg-source: error: add tvtk/tvtk_classes.zip in debian/source/include-binaries if you want to store the modified binary in the debian tarball | dpkg-source: warning: file mayavi2-4.1.0/mayavi.egg-info/requires.txt has no final newline (either original or modified version) | dpkg-source: warning: file mayavi2-4.1.0/mayavi.egg-info/SOURCES.txt has no final newline (either original or modified version) | dpkg-source: warning: file mayavi2-4.1.0/docs/build/tvtk/html/searchindex.js has no final newline (either original or modified version) | dpkg-source: warning: file mayavi2-4.1.0/docs/build/tvtk/html/objects.inv has no final newline (either original or modified version) | dpkg-source: warning: file mayavi2-4.1.0/docs/build/tvtk/html/devel.html has no final newline (either original or modified version) [SNIP - tons of similar warnings and errors] | dpkg-source: error: unrepresentable changes to source | dpkg-buildpackage: error: dpkg-source -b mayavi2-4.1.0 gave error exit status 2 -- Jakub Wilk --- End Message --- --- Begin Message --- Hi Jakub, This bug was fixed in a previous version. The latest fail to build after successful build will be fixed when the below merge request is accepted. https://salsa.debian.org/python-team/packages/mayavi2/-/merge_requests/1 Regards Phil -- "I play the game for the game’s own sake" Arthur Conan Doyle - The Adventure of the Bruce-Partington Plans -- Donations... Buy Me A Coffee: https://buymeacoffee.com/kathenasorg -- Internet Relay Chat (IRC): kathenas Matrix: #kathenas:matrix.org Website: https://kathenas.org Instagram: https://instagram.com/kathenasorg/ Threads: https://www.threads.net/@kathenasorg -- signature.asc Description: This is a digitally signed message part --- End Message ---
Bug#1086265: marked as done (eztrace-contrib: FTBFS: error: ‘CUPTI_RUNTIME_TRACE_CBID_cuda439_v12000’ undeclared here (not in a function))
Your message dated Sun, 10 Nov 2024 01:34:18 + with message-id and subject line Bug#1086265: fixed in eztrace-contrib 2.1.1-1 has caused the Debian Bug report #1086265, regarding eztrace-contrib: FTBFS: error: ‘CUPTI_RUNTIME_TRACE_CBID_cuda439_v12000’ undeclared here (not in a function) 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.) -- 1086265: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1086265 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:eztrace-contrib Version: 2.1-1 Severity: serious Tags: ftbfs Dear maintainer: During a rebuild of all packages in unstable, your package failed to build: [...] debian/rules binary dh binary dh_update_autotools_config dh_autoreconf debian/rules override_dh_auto_configure make[1]: Entering directory '/<>' CUPTI_ROOT=/usr dh_auto_configure -Bbuild-mpich -- -DCMAKE_INSTALL_INCLUDEDIR=/usr/include/x86_64-linux-gnu -DEZTRACE_ENABLE_CUDA=ON \ -DEZTRACE_ENABLE_CUDA=ON \ -DEZTRACE_ENABLE_MPI=OFF \ -DEZTRACE_ENABLE_STARPU=OFF \ -DEZTRACE_ENABLE_OPENMP=OFF \ -DEZTRACE_ENABLE_POSIXIO=OFF \ -DEZTRACE_ENABLE_PTHREAD=OFF \ -DEZTRACE_ENABLE_MEMORY=OFF \ -DEZTRACE_ENABLE_OMPT=OFF \ -DEZTRACE_ENABLE_PNETCDF=OFF \ -DEZTRACE_ENABLE_NETCDF=OFF \ -DEZTRACE_ENABLE_IOTRACER=OFF \ -DCMAKE_INSTALL_INCLUDEDIR=/usr/include/x86_64-linux-gnu -DEZTRACE_ENABLE_CUDA=ON cd build-mpich && DEB_PYTHON_INSTALL_LAYOUT=deb PKG_CONFIG=/usr/bin/pkg-config cmake -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON -DCMAKE_FIND_USE_PACKAGE_REGISTRY=OFF -DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON -DFETCHCONTENT_FULLY_DISCONNECTED=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run "-GUnix Makefiles" -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu -DCMAKE_INSTALL_INCLUDEDIR=/usr/include/x86_64-linux-gnu -DEZTRACE_ENABLE_CUDA=ON -DEZTRACE_ENABLE_CUDA=ON -DEZTRACE_ENABLE_MPI=OFF -DEZTRACE_ENABLE_STARPU=OFF -DEZTRACE_ENABLE_OPENMP=OFF -DEZTRACE_ENABLE_POSIXIO=OFF -DEZTRACE_ENABLE_PTHREAD=OFF -DEZTRACE_ENABLE_MEMORY=OFF -DEZTRACE_ENABLE_OMPT=OFF -DEZTRACE_ENABLE_PNETCDF=OFF -DEZTRACE_ENABLE_NETCDF=OFF -DEZTRACE_ENABLE_IOTRACER=OFF -DCMAKE_INSTALL_INCLUDEDIR=/usr/include/x86_64-linux-gnu -DEZTRACE_ENABLE_CUDA=ON .. -- The C compiler identification is GNU 14.2.0 -- Detecting C compiler ABI info -- Detecting C compiler ABI info - done -- Check for working C compiler: /usr/bin/cc - skipped -- Detecting C compile features -- Detecting C compile features - done -- Found PkgConfig: /usr/bin/pkg-config (found version "1.8.1") -- OTF2 installation found. (using /usr/bin/otf2-config) -- Found OTF2: /usr/bin/otf2-config (found version "3.0.3") -- Looking for a Fortran compiler -- Looking for a Fortran compiler - /usr/bin/f95 -- The Fortran compiler identification is GNU 14.2.0 -- Detecting Fortran compiler ABI info -- Detecting Fortran compiler ABI info - done -- Check for working Fortran compiler: /usr/bin/f95 - skipped -- Looking for cplus_demangle in iberty -- Looking for cplus_demangle in iberty - found CMake Warning (dev) at CMakeLists.txt:129 (find_package): Policy CMP0146 is not set: The FindCUDA module is removed. Run "cmake --help-policy CMP0146" for policy details. Use the cmake_policy command to set the policy and suppress this warning. This warning is for project developers. Use -Wno-dev to suppress it. -- Performing Test CMAKE_HAVE_LIBC_PTHREAD -- Performing Test CMAKE_HAVE_LIBC_PTHREAD - Success -- Found Threads: TRUE -- Found CUDA: /usr (found version "12.2") -- Looking for include file sys/prctl.h -- Looking for include file sys/prctl.h - found -- Looking for include file libbacktrace/backtrace.h -- Looking for include file libbacktrace/backtrace.h - not found -- The CXX compiler identification is GNU 14.2.0 -- Detecting CXX compiler ABI info -- Detecting CXX compiler ABI info - done -- Check for working CXX compiler: /usr/bin/c++ - skipped -- Detecting CXX compile features -- Detecting CXX compile features - done CMake Warning (dev) at src/modules/cuda/CMakeLists.txt:12 (find_package): Policy CMP0146 is not set: The FindCUDA module is removed. Run "cmake --help-policy CMP0146" for policy details. Use the cmake_policy command to set the policy
Bug#1067468: marked as done (eztrace fails openmpi tests on arm64, amd64, ppc64el)
Your message dated Sun, 10 Nov 2024 01:34:05 + with message-id and subject line Bug#1067468: fixed in eztrace 2.1.1-1 has caused the Debian Bug report #1067468, regarding eztrace fails openmpi tests on arm64, amd64, ppc64el 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.) -- 1067468: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067468 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:eztrace Version: 2.1-7 Severity: serious Tags: sid trixie ftbfs eztrace fails openmpi tests on arm64: 67% tests passed, 2 tests failed out of 6 Total Test time (real) = 22.42 sec The following tests FAILED: 2 - mpi_tests (Failed) 6 - mpi_tests (Failed) Errors while running CTest make[2]: *** [Makefile:74: test] Error 8 make[2]: Leaving directory '/<>/build-openmpi' maybe you could try to run all test suites before failing, if one of the test suites fails? --- End Message --- --- Begin Message --- Source: eztrace Source-Version: 2.1.1-1 Done: Samuel Thibault We believe that the bug you reported is fixed in the latest version of eztrace, 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 1067...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Samuel Thibault (supplier of updated eztrace 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, 10 Nov 2024 02:21:32 +0100 Source: eztrace Architecture: source Version: 2.1.1-1 Distribution: unstable Urgency: medium Maintainer: Samuel Thibault Changed-By: Samuel Thibault Closes: 1067468 Changes: eztrace (2.1.1-1) unstable; urgency=medium . * New upstream release. - debian/patches/git-self-link: Upstreamed. - debian/patches/git-starpu-1.4: Upstreamed. - debian/patches/git-starpu-1.4-task_submit: Upstreamed. - debian/patches/git-eztrace_avail: Upstreamed. - debian/patches/git-starpu-install: Upstreamed. - debian/patches/implicit: Upstreamed. * debian/rules: Run all testsuites before reporting the failures (Closes: Bug#1067468) * debian/rules: Add mpi smoketest rules. * debian/control: Depend on pkgconf instead of pkg-config. Checksums-Sha1: 2bfa21413160ae02e8ae715fddf4f66b9a068bf3 2712 eztrace_2.1.1-1.dsc aaa850dd2d077013b62bafa8b1e73d7a4a8e080b 517020 eztrace_2.1.1.orig.tar.gz 059715922b072fe37f4078abdd25a9764548f322 13212 eztrace_2.1.1-1.debian.tar.xz 48c7a4493b15b132dfb8b533fd74652ba0048026 13727 eztrace_2.1.1-1_amd64.buildinfo Checksums-Sha256: ca87069de3473292bc559d633b2913504198050077b703cc4aab050d268eb679 2712 eztrace_2.1.1-1.dsc 70ff299e4cbdee6995ebad4b3c4c80c23511d5c5d2474da871e48400b1198024 517020 eztrace_2.1.1.orig.tar.gz ae39ba01688ef1a53a0833725b0f0e2156dc0346b2a24697c619117841bc1099 13212 eztrace_2.1.1-1.debian.tar.xz 94303a648645ec25820a8dca8ca533a846cdb2de337e510491d5c6740b30ae9a 13727 eztrace_2.1.1-1_amd64.buildinfo Files: 3ad9897cb3cfddfd4eb22e7ac7c83af3 2712 devel optional eztrace_2.1.1-1.dsc 70eccb1fcc6acf0b99d029ef587d2f65 517020 devel optional eztrace_2.1.1.orig.tar.gz de819a83a1f1a0a6c1fabb87c2a7415d 13212 devel optional eztrace_2.1.1-1.debian.tar.xz e94c4431634ecd347beefe7a7ac890d8 13727 devel optional eztrace_2.1.1-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEZTSF1IMOAGwT71n/aHTOWK4tfj8FAmcwC04ACgkQaHTOWK4t fj/ALw//S6yKFlkibCS+pBwoogHgIR3SZ54ervJllHf1FJv+6tvpFH6/s9r81B5Q qija6DfUNWej2TW5gBQQh2AgMPGWmiB6085HzKcFwtE7upVb5/s6Lf8Cvfpl9pMD PrBUIb4FFlWruiO8Yk+5idoimM1CTtG0gL5gsdzPrQiFv8Sf9nYycwCsDvdDquzk xgS3oBOdJaLb8MX/wAZGj4dOOpwxl/Eqz7o/ibdueEI7nKi9THP2Ku9tx8ohybum Le3SgruP3UuOhRiJeDuJk73Z31hYRz40EEbyRpvLOCr9et9HlX3HW4gZCaRtztSi HcLgAc6AfK1OMNEtlDcYZjul1HJs2iz6wmYQIFdbNsxXpCbIuhsp5Ug+UUVyvAih s02o1MPy7QgS1fKQUrJbk2sYUOF2+0A3chpYtDN1zk2eZT2Tu9gGPCCWtH7OlXjE dYG4ePdt9HqkkfubcYpsSMEa7XEGz7gqkXPlRN0ppdQCpZdzy5Es5owFEoGb4V92 m2dMK3tQNIFU5Dm1+srwwUZ936Z2wrm+O078sEbC1Fh7Qor9c5wSluQ97gQcS5c0 reVsZBlgusnmGOGbti55cvyXnF8HYKSD0tviYOOtce2ot3sHY4PTgVYk1sSuujOm 4FOV8qaiGS0T22/Fs7GeSwLvpPVmcjFjG8T4CPf5vTqvWxWrAok= =8cpP -END PGP SIGNATURE- pgp6a5Z5CZ7Rc.pgp Description: PGP signature --- End Message ---
Bug#1070900: marked as done (valentina: FTBFS: Error copying /<>/src/app/tape/bin/tape to /<>/debian/tmp/usr/bin/tape: Cannot create /<>/debian/tmp/usr/bin/tape
Your message dated Sun, 10 Nov 2024 01:51:29 + with message-id and subject line Bug#1070900: fixed in valentina 0.7.53~dfsg-1 has caused the Debian Bug report #1070900, regarding valentina: FTBFS: Error copying /<>/src/app/tape/bin/tape to /<>/debian/tmp/usr/bin/tape: Cannot create /<>/debian/tmp/usr/bin/tape for output 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.) -- 1070900: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070900 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:valentina Version: 0.7.52~dfsg-1 Severity: serious Tags: ftbfs Dear maintainer: During a rebuild of all packages in unstable, your package failed to build: [...] debian/rules binary dh binary dh_update_autotools_config dh_autoreconf debian/rules override_dh_auto_configure make[1]: Entering directory '/<>' QT_SELECT=5 dh_auto_configure -- \ PREFIX_LIB=/usr/lib/valentina \ QMAKE_LFLAGS_RELEASE+=-Wl,-rpath,/usr/lib/valentina \ QMAKE_LFLAGS_DEBUG+=-Wl,-rpath,/usr/lib/valentina \ CONFIG+=noStripDebugSymbols CONFIG+=no_ccache CONFIG+=release qmake -makefile "QMAKE_CFLAGS_RELEASE=-g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2" "QMAKE_CFLAGS_DEBUG=-g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2" "QMAKE_CXXFLAGS_RELEASE=-g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2" "QMAKE_CXXFLAGS_DEBUG=-g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2" QMAKE_LFLAGS_RELEASE=-Wl,-z,relro QMAKE_LFLAGS_DEBUG=-Wl,-z,relro QMAKE_STRIP=: PREFIX=/usr PREFIX_LIB=/usr/lib/valentina QMAKE_LFLAGS_RELEASE\+=-Wl,-rpath,/usr/lib/valentina QMAKE_LFLAGS_DEBUG\+=-Wl,-rpath,/usr/lib/valentina CONFIG\+=noStripDebugSymbols CONFIG\+=no_ccache CONFIG\+=release Info: creating stash file /<>/.qmake.stash Project MESSAGE: g++ version 13.x found [... snipped ...] ln -s -f /<>/src/app/../../share/translations/measurements_p48_fi_FI.qm /<>/src/app/tape/bin/translations/measurements_p48_fi_FI.qm & ln -s -f /<>/src/app/../../share/translations/measurements_p49_fi_FI.qm /<>/src/app/tape/bin/translations/measurements_p49_fi_FI.qm & ln -s -f /<>/src/app/../../share/translations/measurements_p50_fi_FI.qm /<>/src/app/tape/bin/translations/measurements_p50_fi_FI.qm & ln -s -f /<>/src/app/../../share/translations/measurements_p51_fi_FI.qm /<>/src/app/tape/bin/translations/measurements_p51_fi_FI.qm & ln -s -f /<>/src/app/../../share/translations/measurements_p52_fi_FI.qm /<>/src/app/tape/bin/translations/measurements_p52_fi_FI.qm & ln -s -f /<>/src/app/../../share/translations/measurements_p53_fi_FI.qm /<>/src/app/tape/bin/translations/measurements_p53_fi_FI.qm & ln -s -f /<>/src/app/../../share/translations/measurements_p54_fi_FI.qm /<>/src/app/tape/bin/translations/measurements_p54_fi_FI.qm & ln -s -f /<>/src/app/../../share/translations/measurements_p998_fi_FI.qm /<>/src/app/tape/bin/translations/measurements_p998_fi_FI.qm & ln -s -f /<>/src/app/../../share/translations/measurements_p0_en_US.qm /<>/src/app/tape/bin/translations/measurements_p0_en_US.qm & ln -s -f /<>/src/app/../../share/translations/measurements_p1_en_US.qm /<>/src/app/tape/bin/translations/measurements_p1_en_US.qm & ln -s -f /<>/src/app/../../share/translations/measurements_p2_en_US.qm /<>/src/app/tape/bin/translations/measurements_p2_en_US.qm & ln -s -f /<>/src/app/../../share/translations/measurements_p3_en_US.qm /<>/src/app/tape/bin/translations/measurements_p3_en_US.qm & ln -s -f /<>/src/app/../../share/translations/measurements_p4_en_US.qm /<>/src/app/tape/bin/translations/measurements_p4_en_US.qm & ln -s -f /<>/src/app/../../share/translations/measurements_p5_en_US.qm /<>/src/
Bug#1081681: marked as done (FTBFS with Python 3.13)
Your message dated Sun, 10 Nov 2024 01:49:46 +
with message-id
and subject line Bug#1081681: fixed in python-pint 0.24.4-1
has caused the Debian Bug report #1081681,
regarding FTBFS with Python 3.13
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.)
--
1081681: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1081681
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-pint
Version: 0.24.3-2
Severity: normal
Tags: upstream
User: debian-pyt...@lists.debian.org
Usertags: python3.13
Forwarded: https://github.com/hgrecco/pint/issues/1969
Affects: silx
This package failed build from source when test-built against a version of
python3-defaults that includes 3.13 as a supported version.
To reproduce this issue, build against python3-defaults (python3-all-dev etc.)
from Debian experimental.
What's new in Python 3.13:
https://docs.python.org/3.13/whatsnew/3.13.html
Log snippet:
I: pybuild plugin_pyproject:144: Unpacking wheel built for python3.12 with
"installer" module
dh_auto_test -O--buildsystem=pybuild
I: pybuild base:311: cd /<>/.pybuild/cpython3_3.13_pint/build;
python3.13 -m pytest -k "not test_load_definitions_stage_2 and not
test_dataset_operation_with_unit and not test_quantification" --pyargs pint
ImportError while loading conftest
'/<>/.pybuild/cpython3_3.13_pint/build/pint/testsuite/conftest.py'.
pint/__init__.py:18: in
from .delegates.formatter._format_helpers import formatter
pint/delegates/__init__.py:12: in
from . import txt_defparser
pint/delegates/txt_defparser/__init__.py:12: in
from .defparser import DefParser
pint/delegates/txt_defparser/defparser.py:10: in
from . import block, common, context, defaults, group, plain, system
pint/delegates/txt_defparser/common.py:23: in
@dataclass(frozen=True)
/usr/lib/python3.13/dataclasses.py:1295: in wrap
return _process_class(cls, init, repr, eq, order, unsafe_hash,
/usr/lib/python3.13/dataclasses.py:1043: in _process_class
raise TypeError('cannot inherit frozen dataclass from a '
E TypeError: cannot inherit frozen dataclass from a non-frozen one
E: pybuild pybuild:389: test: plugin pyproject failed with: exit code=4: cd
/<>/.pybuild/cpython3_3.13_pint/build; python3.13 -m pytest -k
"not test_load_definitions_stage_2 and not test_dataset_operation_with_unit and
not test_quantification" --pyargs pint
If required, the full build log is available here (for the next 30 days):
https://debusine.debian.net/artifact/712512/
This bug has been filed at "normal" severity, as we haven't started the
transition to add 3.13 as a supported version, yet. This will be raised to RC
as soon as that happens, hopefully well before trixie.
Thanks,
Stefano
--- End Message ---
--- Begin Message ---
Source: python-pint
Source-Version: 0.24.4-1
Done: Stefano Rivera
We believe that the bug you reported is fixed in the latest version of
python-pint, 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 1081...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Stefano Rivera (supplier of updated python-pint 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: Sat, 09 Nov 2024 17:36:08 -0800
Source: python-pint
Architecture: source
Version: 0.24.4-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team
Changed-By: Stefano Rivera
Closes: 1081681 1083680
Changes:
python-pint (0.24.4-1) unstable; urgency=medium
.
* Team upload
* New upstream point release.
- Supports Python 3.13 (Closes: #1081681)
* Drop 0007-Use-platformdirs-instead-of-the-deprecated-appdirs.patch,
superseded upstream.
* Drop Depends on python3-pkg-resources, no longer needed.
(Closes: #1083680)
* Use the default Sphinx theme for now. (See #1085947)
Checksums-Sha1:
fb47df9606e874aede3a40641e15e64c192e738c 2187 python-pint_0.24.4-1.dsc
e37529f244618df50ff6a3e9aa65b1a224d703f0 338057 python-pint_0.24.4.orig.tar.gz
002aaecbd5dd683e079a9ea517bc9028e0cd4def 7796
python-pint_0.24.4-1.debian.tar.xz
310d872edb3f8
Bug#1083680: marked as done (python-pint: (build-)depends on deprecated module python3-pkg-resources)
Your message dated Sun, 10 Nov 2024 01:49:46 + with message-id and subject line Bug#1083680: fixed in python-pint 0.24.4-1 has caused the Debian Bug report #1083680, regarding python-pint: (build-)depends on deprecated module python3-pkg-resources 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.) -- 1083680: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1083680 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:python-pint Version: 0.24.3-2 Severity: normal Tags: sid trixie User: debian-pyt...@lists.debian.org Usertags: pkg-resources-deprecation [This bug is targeted to the upcoming trixie release] The package build-depends or depends on python3-pkg-resources, which is deprecated upstream. Details can be found at https://setuptools.pypa.io/en/latest/pkg_resources.html Use of pkg_resources is deprecated in favor of importlib.resources, importlib.metadata and their backports (importlib_resources, importlib_metadata). Some useful APIs are also provided by packaging (e.g. requirements and version parsing). Users should refrain from new usage of pkg_resources and should work to port to importlib-based solutions. Python 3.12 in unstable provides both importlib_resources and importlib_metadata, so no additional dependencies on those packages are needed. --- End Message --- --- Begin Message --- Source: python-pint Source-Version: 0.24.4-1 Done: Stefano Rivera We believe that the bug you reported is fixed in the latest version of python-pint, 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 1083...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Stefano Rivera (supplier of updated python-pint 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: Sat, 09 Nov 2024 17:36:08 -0800 Source: python-pint Architecture: source Version: 0.24.4-1 Distribution: unstable Urgency: medium Maintainer: Debian Python Team Changed-By: Stefano Rivera Closes: 1081681 1083680 Changes: python-pint (0.24.4-1) unstable; urgency=medium . * Team upload * New upstream point release. - Supports Python 3.13 (Closes: #1081681) * Drop 0007-Use-platformdirs-instead-of-the-deprecated-appdirs.patch, superseded upstream. * Drop Depends on python3-pkg-resources, no longer needed. (Closes: #1083680) * Use the default Sphinx theme for now. (See #1085947) Checksums-Sha1: fb47df9606e874aede3a40641e15e64c192e738c 2187 python-pint_0.24.4-1.dsc e37529f244618df50ff6a3e9aa65b1a224d703f0 338057 python-pint_0.24.4.orig.tar.gz 002aaecbd5dd683e079a9ea517bc9028e0cd4def 7796 python-pint_0.24.4-1.debian.tar.xz 310d872edb3f8d61d305707116070a86824dc98c 8941 python-pint_0.24.4-1_source.buildinfo Checksums-Sha256: bb1fb54cabc02cc323b29f3a1b4926c26031750cf3720a5e8b5754c453ca7f19 2187 python-pint_0.24.4-1.dsc acac4475d812a538f89f64b8372c0fbe86aeb6acf756684ace91b283cdc55f6b 338057 python-pint_0.24.4.orig.tar.gz 0642ff032fbd71ef77e8978f25fd1da28cb015b3b032e1ae628893353c602aeb 7796 python-pint_0.24.4-1.debian.tar.xz e5c0a08f59a7b0ab94e7f353ae0935f894cbdfccf192adb8a7948e5dcab9f141 8941 python-pint_0.24.4-1_source.buildinfo Files: 3af535168f5a09b6c698047a6b2d1142 2187 python optional python-pint_0.24.4-1.dsc 19696a11ded18a3e45bbaf83ac75b194 338057 python optional python-pint_0.24.4.orig.tar.gz d5927924abd98935b81f39a27f1ee3c2 7796 python optional python-pint_0.24.4-1.debian.tar.xz 2885fa5f861e34aa1d92feebf2e18afc 8941 python optional python-pint_0.24.4-1_source.buildinfo -BEGIN PGP SIGNATURE- iIoEARYKADIWIQTumtb5BSD6EfafSCRHew2wJjpU2AUCZzAOJxQcc3RlZmFub3JA ZGViaWFuLm9yZwAKCRBHew2wJjpU2H+SAP9BlvMXpSwIAuSLuw4e6ZdOSzE/RcA5 aoGbcmk/veCD6QD+OTFxQsMDnfNqbY4jbzBoxNmfTmkvt5hN7Mq3MLqtQgk= =3jwz -END PGP SIGNATURE- pgpH3GXr4kCWq.pgp Description: PGP signature --- End Message ---
Bug#1067468: marked as done (eztrace fails openmpi tests on arm64, amd64, ppc64el)
Your message dated Sun, 10 Nov 2024 01:34:18 + with message-id and subject line Bug#1067468: fixed in eztrace-contrib 2.1.1-1 has caused the Debian Bug report #1067468, regarding eztrace fails openmpi tests on arm64, amd64, ppc64el 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.) -- 1067468: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067468 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:eztrace Version: 2.1-7 Severity: serious Tags: sid trixie ftbfs eztrace fails openmpi tests on arm64: 67% tests passed, 2 tests failed out of 6 Total Test time (real) = 22.42 sec The following tests FAILED: 2 - mpi_tests (Failed) 6 - mpi_tests (Failed) Errors while running CTest make[2]: *** [Makefile:74: test] Error 8 make[2]: Leaving directory '/<>/build-openmpi' maybe you could try to run all test suites before failing, if one of the test suites fails? --- End Message --- --- Begin Message --- Source: eztrace-contrib Source-Version: 2.1.1-1 Done: Samuel Thibault We believe that the bug you reported is fixed in the latest version of eztrace-contrib, 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 1067...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Samuel Thibault (supplier of updated eztrace-contrib 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, 10 Nov 2024 02:21:32 +0100 Source: eztrace-contrib Binary: libeztrace0-contrib libeztrace0-contrib-dbgsym Architecture: source amd64 Version: 2.1.1-1 Distribution: unstable Urgency: medium Maintainer: Samuel Thibault Changed-By: Samuel Thibault Description: libeztrace0-contrib - Automatic execution trace generation for HPC - runtime libraries Closes: 1067468 1086265 Changes: eztrace-contrib (2.1.1-1) unstable; urgency=medium . * New upstream release (Closes: Bug#1086265) - debian/patches/git-self-link: Upstreamed. - debian/patches/git-starpu-1.4: Upstreamed. - debian/patches/git-starpu-1.4-task_submit: Upstreamed. - debian/patches/git-eztrace_avail: Upstreamed. - debian/patches/git-starpu-install: Upstreamed. - debian/patches/implicit: Upstreamed. * debian/rules: Run all testsuites before reporting the failures (Closes: Bug#1067468) * debian/rules: Add mpi smoketest rules. * debian/control: Depend on pkgconf instead of pkg-config. Checksums-Sha1: fd15cb400b8c3d3ffa2b9911c9a7cf34eb17c6d8 2591 eztrace-contrib_2.1.1-1.dsc aaa850dd2d077013b62bafa8b1e73d7a4a8e080b 517020 eztrace-contrib_2.1.1.orig.tar.gz c2c7090ccab98556a0ed5230e505e6e9c75ceadf 12904 eztrace-contrib_2.1.1-1.debian.tar.xz 1b8f7aebe9f09fbcfe382eba5d31fe0e9dc1bce8 16525 eztrace-contrib_2.1.1-1_amd64.buildinfo a0fd6040adab1d04152af1bc6eafd0e6c9aa3789 65080 libeztrace0-contrib-dbgsym_2.1.1-1_amd64.deb e35d93469508a62f7b04db3a496ec80a824da8cc 166380 libeztrace0-contrib_2.1.1-1_amd64.deb Checksums-Sha256: 401e7c7de207dda17473e2ecb4be3fb41d3ebc5e02e4b37992baf7ffe6385fe0 2591 eztrace-contrib_2.1.1-1.dsc 70ff299e4cbdee6995ebad4b3c4c80c23511d5c5d2474da871e48400b1198024 517020 eztrace-contrib_2.1.1.orig.tar.gz 8168cbb8acde5e4b3c5c759a87b18a2cfe74faf61a03beee7dbd6f1ba957a2af 12904 eztrace-contrib_2.1.1-1.debian.tar.xz 9ee7dd67ffeed9179904c5ff1f858f37c26a8d135dfc811025ad340fd85779fe 16525 eztrace-contrib_2.1.1-1_amd64.buildinfo 80178e34681a43e9aff61cff71f5de9458271d119e368c025ff7054d5096b70d 65080 libeztrace0-contrib-dbgsym_2.1.1-1_amd64.deb 49b9abfa9641aec95c05d3439c2edfd3c5b0f1677a3120f674bcc8f2983cd97f 166380 libeztrace0-contrib_2.1.1-1_amd64.deb Files: 4df0f770244fadca5d73a0d4b7d7b00d 2591 contrib/devel optional eztrace-contrib_2.1.1-1.dsc 70eccb1fcc6acf0b99d029ef587d2f65 517020 contrib/devel optional eztrace-contrib_2.1.1.orig.tar.gz 8de0639329e35b1417b70ea31cae470b 12904 contrib/devel optional eztrace-contrib_2.1.1-1.debian.tar.xz 9fe633e7e300b233a4b718e926f1bcd2 16525 contrib/devel optional eztrace-contrib_2.1.1-1_amd64.buildinfo 4df57287ea5eb78a17e30cf159e44d56 65080 contrib/debug optional libeztrace0-contrib-dbgsym_2
Bug#1080892: marked as done (Missing Build-Depends on python3-setuptools)
Your message dated Sun, 10 Nov 2024 00:19:26 + with message-id and subject line Bug#1080892: fixed in getfem 5.4.2+dfsg1-5.1 has caused the Debian Bug report #1080892, regarding Missing Build-Depends on python3-setuptools 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.) -- 1080892: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1080892 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: getfem Version: 5.4.2+dfsg1-5 Severity: important User: debian-pyt...@lists.debian.org Usertags: dh-python-no-setuptools Tags: sid, trixie This package failed build from source when test-built against a version of dh-python without a python3-setuptools dependency. distutils is no longer part of the Python standard library, since 3.12. But a minimal version of it becomes available when the python3-setuptools package is installed. Please add a Build-Depends on python3-setuptools to your package, or migrate the package's build system away from setuptools/distutils. If you run into any difficulties, please raise them on debian-pyt...@lists.debian.org. This bug has been filed at "important" severity, as the change hasn't been made in dh-python yet, but this may be raised to RC before the trixie release. Thanks, Stefano --- End Message --- --- Begin Message --- Source: getfem Source-Version: 5.4.2+dfsg1-5.1 Done: Alexandre Detiste We believe that the bug you reported is fixed in the latest version of getfem, 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 1080...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Alexandre Detiste (supplier of updated getfem 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, 10 Nov 2024 00:01:26 +0100 Source: getfem Architecture: source Version: 5.4.2+dfsg1-5.1 Distribution: unstable Urgency: medium Maintainer: Debian Science Team Changed-By: Alexandre Detiste Closes: 1080892 Changes: getfem (5.4.2+dfsg1-5.1) unstable; urgency=medium . * Team upload. * Add dependency on python3-setuptools (Closes: #1080892) Checksums-Sha1: 36da520ca4816d51e5748ebbfa49efa6a92f6e52 2773 getfem_5.4.2+dfsg1-5.1.dsc be74af263b18d9e0200f84589bd783c2f22bc93b 16852 getfem_5.4.2+dfsg1-5.1.debian.tar.xz 4af3a3cbfa09a9a86aec017b56f96f406c0fe0c5 11235 getfem_5.4.2+dfsg1-5.1_source.buildinfo Checksums-Sha256: a67d3b5a0e0e62bf338a8f56bf427692073f3842fdf7d24884dd35790bdd8f2b 2773 getfem_5.4.2+dfsg1-5.1.dsc 0c891f149da23a245665ff339c3ff4b02cb4f6ddfab9b7e585440fcaa635f301 16852 getfem_5.4.2+dfsg1-5.1.debian.tar.xz e50b577c26c7dada2754ce2c6263ede375eef301442d2e22e9b1da9c54d6bdd2 11235 getfem_5.4.2+dfsg1-5.1_source.buildinfo Files: 444277dcbcc24d07bae10328d4cee3cb 2773 libs optional getfem_5.4.2+dfsg1-5.1.dsc 18912e5ae6af536ad79bbc73aad6ef42 16852 libs optional getfem_5.4.2+dfsg1-5.1.debian.tar.xz 04a863b6a79a77465f9131a648e786a0 11235 libs optional getfem_5.4.2+dfsg1-5.1_source.buildinfo -BEGIN PGP SIGNATURE- iQJFBAEBCgAvFiEEj23hBDd/OxHnQXSHMfMURUShdBoFAmcv9rQRHHRjaGV0QGRl Ymlhbi5vcmcACgkQMfMURUShdBpneA//ZODIIVMdrWWns/SjaIqwcOp4c0TUJizo AfcooTTKHZ6/8nGD6gHGUbVNa7fcj2AAH2ftzGJAhluXf15Uhh/715AJe8qxAI7G Jb7zsCq/kocTSrgbDjAUQrHQDC4Ra0m42od1KxUg3zLv49rxEIRsjiaKqJsaRjVC k81y+9CRPkTZRetu3EXhHeq0k/x4d7m9hcAVjIe4NoUliVNmpWoW7nY3bGKgbFM8 FTQKeywv0xgvV9yo6Wz6ogL1/GO3bK3tTXp1Gucsvr5XgpiGdGz5sZ7YZQwpDmqx KvLQygFO2gIupc5ETQaI3YK5Nl0WpTwbaFjf0kGJrjXr+r17TwkKttKoQySYai8b pQvBhxVSpYs0Pqjj8RlzPI6cFbqrnA7WWa+ahqhoe0R7IGTJH7AwV6PyvNHCVCZc wqd6WOTwklKgXfvsDpWB6DzGjrkRRCbsAxSIm3K7FgQDI0olMOtl8RLwqfAGhKL2 kZSYWy1xAWCvbatwKdEhgr5X6KOl2JXvpozGgIibn6JY9Zlu9obm6008wpm83trZ v9UrsZSMeaE0HRIEDxTqaKZw/zvGNTT/bMRI5yNgHkSGLCtnaGnBsav4dc1GoIO9 q2BSx+sR6WMKPoJZYN6WLyM/9qZePKFl8rfWml0TDBIzhp83JTkx0ZVE9eLXlAbr K3DHI4GP5Cc= =Q5TP -END PGP SIGNATURE- pgpNBWJqPUKkr.pgp Description: PGP signature --- End Message ---
Bug#1081432: marked as done (FTBFS with Python 3.13)
Your message dated Sun, 10 Nov 2024 00:05:22 +
with message-id
and subject line Bug#1081432: fixed in py-lmdb 1.4.1-3
has caused the Debian Bug report #1081432,
regarding FTBFS with Python 3.13
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.)
--
1081432: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1081432
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: py-lmdb
Version: 1.4.1-2
Severity: normal
Tags: upstream patch
User: debian-pyt...@lists.debian.org
Usertags: python3.13
Forwarded: https://github.com/jnwatson/py-lmdb/issues/362
This package failed build from source when test-built against a version of
python3-defaults that incudes 3.13 as a supported version.
To reproduce this issue, build against python3-defaults (python3-all-dev etc.)
from Debian experimental.
What's new in Python 3.13:
https://docs.python.org/3.13/whatsnew/3.13.html
Log snippet:
creating build/temp.linux-aarch64-cpython-313/lmdb
aarch64-linux-gnu-gcc -fno-strict-overflow -Wsign-compare -DNDEBUG -g -O2 -Wall
-g -O2 -Werror=implicit-function-declaration
-ffile-prefix-map=/<>=. -fstack-protector-strong
-fstack-clash-protection -Wformat -Werror=format-security
-mbranch-protection=standard -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC
-Ilib/py-lmdb -I/usr/include/python3.13 -c lmdb/cpython.c -o
build/temp.linux-aarch64-cpython-313/lmdb/cpython.o -UNDEBUG -w
lmdb/cpython.c: In function ‘val_from_buffer’:
lmdb/cpython.c:586:12: error: implicit declaration of function
‘PyObject_AsReadBuffer’; did you mean ‘PyObject_GetBuffer’?
[-Wimplicit-function-declaration]
586 | return PyObject_AsReadBuffer(buf,
|^
|PyObject_GetBuffer
error: command '/usr/bin/aarch64-linux-gnu-gcc' failed with exit code 1
E: pybuild pybuild:389: build: plugin distutils failed with: exit code=1:
/usr/bin/python3.13 setup.py build
I: pybuild base:311: /usr/bin/python3 setup.py build
py-lmdb: Using system version of liblmdb.
py-lmdb: Using CPython extension; override with LMDB_FORCE_CFFI=1.
running build
running build_py
creating /<>/.pybuild/cpython3_3.12_lmdb/build/lmdb
copying lmdb/tool.py -> /<>/.pybuild/cpython3_3.12_lmdb/build/lmdb
copying lmdb/cffi.py -> /<>/.pybuild/cpython3_3.12_lmdb/build/lmdb
copying lmdb/_config.py ->
/<>/.pybuild/cpython3_3.12_lmdb/build/lmdb
copying lmdb/__main__.py ->
/<>/.pybuild/cpython3_3.12_lmdb/build/lmdb
copying lmdb/__init__.py ->
/<>/.pybuild/cpython3_3.12_lmdb/build/lmdb
running build_ext
building 'cpython' extension
creating build/temp.linux-aarch64-cpython-312
creating build/temp.linux-aarch64-cpython-312/lmdb
aarch64-linux-gnu-gcc -fno-strict-overflow -Wsign-compare -DNDEBUG -g -O2 -Wall
-g -O2 -Werror=implicit-function-declaration
-ffile-prefix-map=/<>=. -fstack-protector-strong
-fstack-clash-protection -Wformat -Werror=format-security
-mbranch-protection=standard -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC
-Ilib/py-lmdb -I/usr/include/python3.12 -c lmdb/cpython.c -o
build/temp.linux-aarch64-cpython-312/lmdb/cpython.o -UNDEBUG -w
aarch64-linux-gnu-gcc -shared -Wl,-O1 -Wl,-Bsymbolic-functions -Wl,-z,relro -g
-fwrapv -O2 -Wl,-z,relro -g -O2 -Werror=implicit-function-declaration
-ffile-prefix-map=/<>=. -fstack-protector-strong
-fstack-clash-protection -Wformat -Werror=format-security
-mbranch-protection=standard -Wdate-time -D_FORTIFY_SOURCE=2
build/temp.linux-aarch64-cpython-312/lmdb/cpython.o
-L/usr/lib/aarch64-linux-gnu -llmdb -o
/<>/.pybuild/cpython3_3.12_lmdb/build/lmdb/cpython.cpython-312-aarch64-linux-gnu.so
dh_auto_build: error: pybuild --build -i python{version} -p "3.13 3.12"
returned exit code 13
make: *** [debian/rules:8: build] Error 25
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2
Build finished at 2024-09-11T14:56:50Z
If required, the full build log is available here (for the next 30 days):
https://debusine.debian.net/artifact/700684/
This bug has been filed at "normal" severity, as we haven't started the
transition to add 3.13 as a supported version, yet. This will be raised to RC
as soon as that happens, hopefully well before trixie.
Thanks,
Stefano
--- End Message ---
--- Begin Message ---
Source: py-lmdb
Source-Version: 1.4.1-3
Done: Stefano Rivera
We believe that the bug you reported is fixed in the latest version of
py-lmdb, which is due to be install
Bug#1080686: marked as done (Missing Build-Depends on python3-setuptools)
Your message dated Sun, 10 Nov 2024 00:05:14 + with message-id and subject line Bug#1080686: fixed in ompl 1.6.0+ds1-1 has caused the Debian Bug report #1080686, regarding Missing Build-Depends on python3-setuptools 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.) -- 1080686: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1080686 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ompl Version: 1.5.2+ds1-1.1 Severity: important User: debian-pyt...@lists.debian.org Usertags: dh-python-no-setuptools Tags: sid, trixie This package failed build from source when test-built against a version of dh-python without a python3-setuptools dependency. distutils is no longer part of the Python standard library, since 3.12. But a minimal version of it becomes available when the python3-setuptools package is installed. Please add a Build-Depends on python3-setuptools to your package, or migrate the package's build system away from setuptools/distutils. If you run into any difficulties, please raise them on debian-pyt...@lists.debian.org. This bug has been filed at "important" severity, as the change hasn't been made in dh-python yet, but this may be raised to RC before the trixie release. Thanks, Stefano --- End Message --- --- Begin Message --- Source: ompl Source-Version: 1.6.0+ds1-1 Done: Alexandre Detiste We believe that the bug you reported is fixed in the latest version of ompl, 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 1080...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Alexandre Detiste (supplier of updated ompl 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: Sat, 09 Nov 2024 23:15:01 +0100 Source: ompl Architecture: source Version: 1.6.0+ds1-1 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers Changed-By: Alexandre Detiste Closes: 1080686 Changes: ompl (1.6.0+ds1-1) unstable; urgency=medium . * Team Upload * New upstream version 1.6.0+ds1 * Add dependency on python3-setuptools (Closes: #1080686) . [ Debian Janitor ] * Set upstream metadata fields: Bug-Database, Bug-Submit, Repository-Browse. * Update standards version to 4.6.1, no changes needed. Checksums-Sha1: 921147ddf1054ba837f920dfaad1eb15151dec5a 2488 ompl_1.6.0+ds1-1.dsc 6c55fc36111de55dc2a333054f1850c40853b430 18749336 ompl_1.6.0+ds1.orig.tar.xz cf9f735bbe9d589d6553ea69a4132d7e2012e080 7312 ompl_1.6.0+ds1-1.debian.tar.xz e1ef7159280fbf196b3d6b25df6061d635d8987b 15495 ompl_1.6.0+ds1-1_source.buildinfo Checksums-Sha256: 1b0be9ebbd2a099f615d35890a30598341007a2028e4ae13870a3c6f22c63bcb 2488 ompl_1.6.0+ds1-1.dsc 505ba9093e685b2b4bcc26c5c82843d21e7ed5483b0cfad48730cdf9341ce1c9 18749336 ompl_1.6.0+ds1.orig.tar.xz f989037e747af7c265b08e84b835a4a1ac2dfa2837971c9340047e39e49b163b 7312 ompl_1.6.0+ds1-1.debian.tar.xz 420b6e97f9d36087d3e81d4b33a237b531fcdc3469d9ec9ca0f75de10faf9e21 15495 ompl_1.6.0+ds1-1_source.buildinfo Files: d304fc5894aa89b3727bf05e6fcfe4ea 2488 libs optional ompl_1.6.0+ds1-1.dsc 027d8717823b545f9aecad0e649b32d4 18749336 libs optional ompl_1.6.0+ds1.orig.tar.xz 1dd360ec5a5b48e6d1cfba207a9a075c 7312 libs optional ompl_1.6.0+ds1-1.debian.tar.xz 1f563cb20619edbe67d5eefd849270b3 15495 libs optional ompl_1.6.0+ds1-1_source.buildinfo -BEGIN PGP SIGNATURE- iQJFBAEBCgAvFiEEj23hBDd/OxHnQXSHMfMURUShdBoFAmcv8r0RHHRjaGV0QGRl Ymlhbi5vcmcACgkQMfMURUShdBpDGw/+LEddvW9EqCNVlG/G8RMfVdfR7YUlhs+G Gavh6DridDUEHahaqMYbJrK9VL5SR6X+LR8ssPWdJN7MeMWg+gkaSUlz6kIl8jzK 6enP7SxAkZ5AvZNgNoTqVutNTLDGDjCSQCFVAWHbPKwVsVdjRMOZFt3FalM7PMGH rgN5t05zjtx56oiLHRc82+5U8ChxaruuKFrL9vYyQXs6oA/syHfAIAQYercwnu/X kzePEabYCh4fNzzDi38ciodEwFml4k+7rIArXfvvVpgLFI/04XIk7bu4D7hyvASS iZAEDcsE/AsCLtPyl4keKUqZ6UjUeucTac5/RsjePWedskXpj4TIWkvgGPW1Ld9n AEv6i1vzLQrYD9lwCuH+9XZ4C4RHuPWX6K+WQ1sJ0RfMqLGge4Os2YabbvBnSi7V owS11fmpEwRl2MUO+bcIIftuRfraT+tQ+G8JjV6eIL9Y60lhuRUqBfxnui2iRVas VAyfFm9M+qb88Er5JoQ/2uilI5stqltjZ+lYiec4dTXStq7jAl/SHfkIZVp5DnuU JwyTtNmCS6ENFAvQ/q0Ds2jekm41GmcQIkwyyt8+v58QkAo535Ptl4+PW+er89Aj OwDK2uav4mlxY5rkqEl9Km3gkAtkfareSw9Sf+Q00M00EhxbpiZ6g//Z
Bug#1018836: marked as done (toilet: please add Homepage field)
Your message dated Sat, 09 Nov 2024 23:49:13 + with message-id and subject line Bug#1018836: fixed in toilet 0.3-2 has caused the Debian Bug report #1018836, regarding toilet: please add Homepage field 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.) -- 1018836: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1018836 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: toilet Version: 0.3-1.4 Severity: wishlist Please add: Homepage: http://caca.zoy.org/wiki/toilet to debian/control. -- Jakub Wilk --- End Message --- --- Begin Message --- Source: toilet Source-Version: 0.3-2 Done: Chris Hofstaedtler We believe that the bug you reported is fixed in the latest version of toilet, 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 1018...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Chris Hofstaedtler (supplier of updated toilet 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, 10 Nov 2024 00:22:26 +0100 Source: toilet Architecture: source Version: 0.3-2 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Chris Hofstaedtler Closes: 1018836 Changes: toilet (0.3-2) unstable; urgency=medium . * Orphan package, per #1011572 * d/control: set Homepage (Closes: #1018836) * Switch Build-Depends from pkg-config to pkgconf Checksums-Sha1: e2967e902534cfa1bfd8841473450d03c7f95fc9 1928 toilet_0.3-2.dsc d40a8223d2f7ed80af2d24275605364afd310727 3512 toilet_0.3-2.debian.tar.xz Checksums-Sha256: fae781fa6ed95e92ee67089f052365cba2dcc60a3705308090309b9344a30584 1928 toilet_0.3-2.dsc 401a4448fde4c849ae48f16de574337e1cadc365cd7aa8efab19518c4c6080e5 3512 toilet_0.3-2.debian.tar.xz Files: 94e50a27906209d763e0036ff4c65c0f 1928 libs optional toilet_0.3-2.dsc 3f71068652efff3630c3293f8b236d02 3512 libs optional toilet_0.3-2.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEfRrP+tnggGycTNOSXBPW25MFLgMFAmcv8EYACgkQXBPW25MF LgP7SA/+KP0Hx36SBln/TQAj4QbkWUNCMWdWnZhF8gt3gmmheDi+66ifFEO+qQr6 DLlzj6idnoWRxUB7SlP05PLCS2/Bwr3lzvqiyeaKya9sicabsOIYvcp765Bycqgl Vwf4Ub4Q6c3zyn2m+oerHoFRBKrfWdO98aAK2us4fua4si9hM1i8l2XygRwPTwXw elFjQz9Dq5ZQHkjPQIJv+/Y1yp4hmuareivHoGccD+IXWqtGcENDI4NCcKdPnuvf OoSjg7Ca6BNi3jJYfQJMMKiAK5ueFjtmrzauGoZqW1GlTwDMgaTW5uKS3ZAsH2VN qeWGmZXuXb/4FEPG1gtqGQ53iC0Cd2wXYg5rwu9bkchZgQ6d2rbxM+RnXgO1Hq4W 8nBdwAb0RkubVrAKxSEYrZBll6FzcFNRrTysYv1KrSE5e72kQpXuUHGvnJDja0uG uPaETtN58/g3i7yiARER27ZUvRlnJanMXWOHp2FrGzVZQ3knyHJLAnz34Jb0qzV8 CGA8+4DB965MvxN91A2+KzedBg3zzMmAPdFz6z5ZIhjsgcmPZXP4gVNhFkVw9B9d j5XkxQVImzKsceohpQd59NRQsxLkDJZ+MpKCvj6N+mkrlhLYjPvgziT4F8rVRGW8 hiNGQ/DvyhRhuVFegxwXUWOy7Z2ETF8OFrhx32r2ldv5nKm1nSU= =V+bc -END PGP SIGNATURE- pgp7pa6S9x4UP.pgp Description: PGP signature --- End Message ---
Bug#1081428: marked as done (FTBFS with Python 3.13)
Your message dated Sat, 09 Nov 2024 23:49:01 + with message-id and subject line Bug#1081428: fixed in mod-wsgi 5.0.1-1 has caused the Debian Bug report #1081428, regarding FTBFS with Python 3.13 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.) -- 1081428: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1081428 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: mod-wsgi Version: 5.0.0-1 Severity: normal User: debian-pyt...@lists.debian.org Usertags: python3.13 Forwarded: https://github.com/GrahamDumpleton/mod_wsgi/issues/907 This package failed build from source when test-built against a version of python3-defaults that incudes 3.13 as a supported version. To reproduce this issue, build against python3-defaults (python3-all-dev etc.) from Debian experimental. What's new in Python 3.13: https://docs.python.org/3.13/whatsnew/3.13.html Log snippet: /usr/share/apr-1.0/build/libtool --mode=compile --tag=disable-static aarch64-linux-gnu-gcc -prefer-pic -pipe -g -O2 -Werror=implicit-function-declaration -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -mbranch-protection=standard -Wdate-time -D_FORTIFY_SOURCE=2 -DLINUX -D_REENTRANT -D_GNU_SOURCE -I/usr/include/apache2 -I/usr/include/apr-1.0 -I/usr/include/apr-1.0 -I/usr/include -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -mbranch-protection=standard -I/usr/include/python3.13 -D_FORTIFY_SOURCE=2 -DNDEBUG -c -o src/server/wsgi_interp.lo src/server/wsgi_interp.c && touch src/server/wsgi_interp.slo libtool: compile: aarch64-linux-gnu-gcc -pipe -g -O2 -Werror=implicit-function-declaration -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -mbranch-protection=standard -Wdate-time -D_FORTIFY_SOURCE=2 -DLINUX -D_REENTRANT -D_GNU_SOURCE -I/usr/include/apache2 -I/usr/include/apr-1.0 -I/usr/include/apr-1.0 -I/usr/include -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -mbranch-protection=standard -I/usr/include/python3.13 -D_FORTIFY_SOURCE=2 -DNDEBUG -c src/server/wsgi_interp.c -fPIC -DPIC -o src/server/.libs/wsgi_interp.o src/server/wsgi_interp.c: In function 'newInterpreterObject': src/server/wsgi_interp.c:733:46: warning: 'Py_FileSystemDefaultEncoding' is deprecated [-Wdeprecated-declarations] 733 | Py_FileSystemDefaultEncoding, | ^~~~ In file included from /usr/include/python3.13/Python.h:95, from src/server/wsgi_python.h:26, from src/server/wsgi_interp.h:24, from src/server/wsgi_interp.c:21: /usr/include/python3.13/fileobject.h:22:46: note: declared here 22 | Py_DEPRECATED(3.12) PyAPI_DATA(const char *) Py_FileSystemDefaultEncoding; | ^~~~ src/server/wsgi_interp.c:751:46: warning: 'Py_FileSystemDefaultEncoding' is deprecated [-Wdeprecated-declarations] 751 | Py_FileSystemDefaultEncoding, | ^~~~ /usr/include/python3.13/fileobject.h:22:46: note: declared here 22 | Py_DEPRECATED(3.12) PyAPI_DATA(const char *) Py_FileSystemDefaultEncoding; | ^~~~ src/server/wsgi_interp.c:769:46: warning: 'Py_FileSystemDefaultEncoding' is deprecated [-Wdeprecated-declarations] 769 | Py_FileSystemDefaultEncoding, | ^~~~ /usr/include/python3.13/fileobject.h:22:46: note: declared here 22 | Py_DEPRECATED(3.12) PyAPI_DATA(const char *) Py_FileSystemDefaultEncoding; | ^~~~ src/server/wsgi_interp.c:821:46: warning: 'Py_FileSystemDefaultEncoding' is deprecated [-Wdeprecated-declarations] 821 | Py_FileSystemDefaultEncoding, | ^~~~ /usr/include/python3.13/fileobject.h:22:46: note: declared here 22 |
Bug#1084928: marked as done (garli: Please move from openmpi to mpich for 32-bit systems)
Your message dated Sat, 09 Nov 2024 23:34:07 + with message-id and subject line Bug#1084928: fixed in garli 2.1-8 has caused the Debian Bug report #1084928, regarding garli: Please move from openmpi to mpich for 32-bit systems 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.) -- 1084928: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1084928 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: garli Version: 2.1-7 Severity: normal OpenMPI is moving to 64-bit only for 5+, so Debian is moving to mpich-only for 32-bit systems. Please move to using mpi-default-dev rather than openmpi. Best regards Alastair -- System Information: Debian Release: 12.7 APT prefers stable-security APT policy: (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-25-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_IE.UTF-8), LANGUAGE=en_IE:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled --- End Message --- --- Begin Message --- Source: garli Source-Version: 2.1-8 Done: Étienne Mollier We believe that the bug you reported is fixed in the latest version of garli, 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 1084...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Étienne Mollier (supplier of updated garli 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: Sat, 09 Nov 2024 23:34:46 +0100 Source: garli Architecture: source Version: 2.1-8 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team Changed-By: Étienne Mollier Closes: 1044308 1084928 Changes: garli (2.1-8) unstable; urgency=medium . * Team upload. * d/control: migrate to mpi-default-*. (Closes: #1084928) * d/clean: also clean debian/mpi/Garli-mpi. (Closes: #1044308) * d/control: declare compliance to standards version 4.7.0. Checksums-Sha1: c7e1bb7e579f545de55e3e23410686c9c8af630f 2186 garli_2.1-8.dsc 814a8022142225579f0cbfa76b78f9593da39808 4912 garli_2.1-8.debian.tar.xz Checksums-Sha256: 68894a9d317ed53bc8c46589d271916896ddafa5089704654d5f74183fe3 2186 garli_2.1-8.dsc cefd24a1fd4eea484b2b0df5da32eb85047d6962aa15179b716f0bed8008c825 4912 garli_2.1-8.debian.tar.xz Files: 768b5b114712645bb054846319755b22 2186 science optional garli_2.1-8.dsc 921292b575a872b1945eb69ac7e8bb33 4912 science optional garli_2.1-8.debian.tar.xz -BEGIN PGP SIGNATURE- iQJIBAEBCgAyFiEEj5GyJ8fW8rGUjII2eTz2fo8NEdoFAmcv7gEUHGVtb2xsaWVy QGRlYmlhbi5vcmcACgkQeTz2fo8NEdoHxg/9HJYmXShgmRcJ/kScQPfY5V0eWi6A iCiLU+CfEkAw7yXidVScfoHNw1LBbPusOZNGMadiKsTzQw3AOWV9A75qUhm0AMDi IyghV5wHkhFQ52ZovNZoPJhUuA2di39lcG6MaPdNoPergqckcp4yCA9xpfAv9jr+ sRpG0OW+Z3/SOtntn0ZUtrbDjJciuu0/GlKtnSZr3WOncY3Ir/9v15y/e17fPISg +A3htXBcQw3/TXiyxsN5Qbm7+g31vv9GCHef9dvjsAActEtYWMnf1y0r25Ou4Uz1 0oy+Rb5pJEBeccBRNN6ttnMK/4oqFAMSxHsZa9izbLHKCP12Rc/8MYej88MVfP7g lstVYn0BMAvor/mIdKeBQNsPZ1RcW7+6AyHpoIPTzAx0j/0H+sDnl1zmyHrcIshU gXWPhRdFc2HI4JgIcxbz6hseTB1ggZ+DONnmfx1MsfWril04d1MvEOM0+jAr0rER brpMOVvX2wPNhqXr5HpWoPsInyXB3o7kXx6KCDTC9nzAoN36gIKRmfD8GpDRnvE0 9TgGioQHhimGoO3kevOIhA+2sLLXRXcj8ggwVtrycgBUCvK/K/53Odqjqqd/PlJs X51COBBADttqZiHwjTZJtpjJAjcJpp2Phh1qsamikGfLzb1sfw9Dx7mpNctsUMub WUPNtM92FtkGbOM= =rWaW -END PGP SIGNATURE- pgp7jetJI4qYH.pgp Description: PGP signature --- End Message ---
Bug#1080858: marked as done (Missing Build-Depends on python3-setuptools)
Your message dated Sat, 09 Nov 2024 23:34:31 + with message-id and subject line Bug#1080858: fixed in python-demgengeo 1.4-6 has caused the Debian Bug report #1080858, regarding Missing Build-Depends on python3-setuptools 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.) -- 1080858: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1080858 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python-demgengeo Version: 1.4-5 Severity: important User: debian-pyt...@lists.debian.org Usertags: dh-python-no-setuptools Tags: sid, trixie This package failed build from source when test-built against a version of dh-python without a python3-setuptools dependency. distutils is no longer part of the Python standard library, since 3.12. But a minimal version of it becomes available when the python3-setuptools package is installed. Please add a Build-Depends on python3-setuptools to your package, or migrate the package's build system away from setuptools/distutils. If you run into any difficulties, please raise them on debian-pyt...@lists.debian.org. This bug has been filed at "important" severity, as the change hasn't been made in dh-python yet, but this may be raised to RC before the trixie release. Thanks, Stefano --- End Message --- --- Begin Message --- Source: python-demgengeo Source-Version: 1.4-6 Done: Alexandre Detiste We believe that the bug you reported is fixed in the latest version of python-demgengeo, 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 1080...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Alexandre Detiste (supplier of updated python-demgengeo 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: Sat, 09 Nov 2024 23:46:07 +0100 Source: python-demgengeo Architecture: source Version: 1.4-6 Distribution: unstable Urgency: medium Maintainer: Debian Science Team Changed-By: Alexandre Detiste Closes: 1080858 Changes: python-demgengeo (1.4-6) unstable; urgency=medium . * Team upload * Add dep on python3-setuptools (Closes: #1080858) * Use dh-sequence-python3 Checksums-Sha1: 23595dd72b52b61c875bb6789a5f26ae28777e3f 2241 python-demgengeo_1.4-6.dsc 2bcf3aa2a3a16fea95dd8d5b37c8923fec0197db 9256 python-demgengeo_1.4-6.debian.tar.xz fbe0b12465c8d4361ec0ca07b4d527c9215bbb49 9081 python-demgengeo_1.4-6_source.buildinfo Checksums-Sha256: 44183e5ff4211f926cb0e4d304cdbad25658719ec3da3dc8e02ae76f84a29aa4 2241 python-demgengeo_1.4-6.dsc e2525a2dafd8db3f0d2f098b61c3076d12fd8531312778157344a6245318c649 9256 python-demgengeo_1.4-6.debian.tar.xz 777b832d0f66229b315dcc256aabd17a48d73b607f562256ffd36e80508b226e 9081 python-demgengeo_1.4-6_source.buildinfo Files: db585dcbe438f02d19c39d00a0e28ec0 2241 python optional python-demgengeo_1.4-6.dsc d4c2e32648082555405e2a1e0150781e 9256 python optional python-demgengeo_1.4-6.debian.tar.xz 504d3b53f9179e1d3306dc162b8227aa 9081 python optional python-demgengeo_1.4-6_source.buildinfo -BEGIN PGP SIGNATURE- iQJFBAEBCgAvFiEEj23hBDd/OxHnQXSHMfMURUShdBoFAmcv7XgRHHRjaGV0QGRl Ymlhbi5vcmcACgkQMfMURUShdBpYQA//a7vnVUKnBBZveoZQiDb/wtCsddM8MRFC 0P5hwrUXKd5fXaeqaYeYTOi4n7zl8Q8mmH+JMT/xD/FaYf22hqCbTLjWDTHEEgTm XvfChfWj7hln0iDqLVSFk0oUIpn7L8Kg4A6+9v+TAP+GO8r6aOYknFoMe7hk1EOS qvKolJhoOWOLJR+MyLOSDK/D1/pKqQPpsLRGEcVy2iJplU+QjUFn7sdK8oiZz2X9 Cpz/M20RKix68l2HT52FgV3vcWu+d5fAL5Ig/lMATFrVKwIXbXA1GdO6VNdw5BOy Di6NO0kMO1oueY+KOQjUnIV5AjxV0P6+IYvmgFK+QNaOimOJsUNCSKB9d0n84lL8 J+X9DHqXMbJT+IBPDwxaEpvv2qAx504aTQDuBd52CA57V+6dApguHWlY+R5Mo7Ns xgf7ZElDbG6G5CEvCgbwsDbKSIZHqj3EiR9hlkDOt1ugmkRQiRkzc0Kz9MLSzkxF KP0FJwF4klpoo8p09pslfwlxuLs/8cn1kflYo48MsRtOZcMo6smYG4QZmNc/u9Nq QvLavjSrfIvNnNqW2qtGjh1VGgaxrotBhNduWYE4HvLxD+mJg+obw1k+W00Xxy2f nh8n17ycrLhRiSZcWy5NVJlVO+kKooEmKAfwqmLs/mcJSN6Ke518X/otO4hf2+5n +CJBUBlY4/o= =4NTD -END PGP SIGNATURE- pgpjrkFQT6EtK.pgp Description: PGP signature --- End Message ---
Bug#1044308: marked as done (garli: Fails to build source after successful build)
Your message dated Sat, 09 Nov 2024 23:34:06 + with message-id and subject line Bug#1044308: fixed in garli 2.1-8 has caused the Debian Bug report #1044308, regarding garli: Fails to build source after successful build 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.) -- 1044308: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1044308 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: garli Version: 2.1-7 Severity: minor Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-sab-20230813 ftbfs-source-after-build User: debian...@lists.debian.org Usertags: qa-doublebuild Hi, This package fails to build a source package after a successful build (dpkg-buildpackage ; dpkg-buildpackage -S). This is probably a clear violation of Debian Policy section 4.9 (clean target), but this is filed as severity:minor for now, because a discussion on debian-devel showed that we might want to revisit the requirement of a working 'clean' target. More information about this class of issues, included common problems and solutions, is available at https://wiki.debian.org/qa.debian.org/FTBFS/SourceAfterBuild Relevant part of the build log: > cd /<> && runuser -u user42 -- dpkg-buildpackage --sanitize-env > -us -uc -rfakeroot -S > --- > > dpkg-buildpackage: info: source package garli > dpkg-buildpackage: info: source version 2.1-7 > dpkg-buildpackage: info: source distribution unstable > dpkg-buildpackage: info: source changed by Sascha Steinbiss > dpkg-source --before-build . > debian/rules clean > dh clean >dh_auto_clean > make -j8 distclean > make[1]: Entering directory '/<>' > Making distclean in src > make[2]: Entering directory '/<>/src' > test -z "Garli" || rm -f Garli > rm -f *.o > rm -f *.tab.c > test -z "" || rm -f > rm -f TAGS ID GTAGS GRTAGS GSYMS GPATH tags > test . = "." || test -z "" || rm -f > rm -f ./.deps/adaptation.Po > rm -f ./.deps/bipartition.Po > rm -f ./.deps/condlike.Po > rm -f ./.deps/configoptions.Po > rm -f ./.deps/configreader.Po > rm -f ./.deps/datamatr.Po > rm -f ./.deps/funcs.Po > rm -f ./.deps/garlimain.Po > rm -f ./.deps/garlireader.Po > rm -f ./.deps/individual.Po > rm -f ./.deps/linalg.Po > rm -f ./.deps/model.Po > rm -f ./.deps/mpitrick.Po > rm -f ./.deps/optimization.Po > rm -f ./.deps/population.Po > rm -f ./.deps/rng.Po > rm -f ./.deps/sequencedata.Po > rm -f ./.deps/set.Po > rm -f ./.deps/translatetable.Po > rm -f ./.deps/tree.Po > rm -f ./.deps/treenode.Po > rm -f Makefile > make[2]: Leaving directory '/<>/src' > Making distclean in tests > make[2]: Entering directory '/<>/tests' > test -z "" || rm -f > test . = "." || test -z "" || rm -f > rm -f Makefile > make[2]: Leaving directory '/<>/tests' > make[2]: Entering directory '/<>' > test -z "" || rm -f > rm -f config.h stamp-h1 > rm -f TAGS ID GTAGS GRTAGS GSYMS GPATH tags > test . = "." || test -z "" || rm -f > rm -f cscope.out cscope.in.out cscope.po.out cscope.files > make[2]: Leaving directory '/<>' > rm -f config.status config.cache config.log configure.lineno > config.status.lineno > rm -f Makefile > make[1]: Leaving directory '/<>' >dh_autoreconf_clean >dh_clean > dpkg-source -b . > dpkg-source: error: unwanted binary file: debian/mpi/Garli-mpi > dpkg-source: error: detected 1 unwanted binary file (add it in > debian/source/include-binaries to allow its inclusion). > dpkg-source: info: using source format '3.0 (quilt)' > dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 255 > > E: Command 'cd /<> && runuser -u user42 -- dpkg-buildpackage > --sanitize-env -us -uc -rfakeroot -S' failed to run. The full build log is available from: http://qa-logs.debian.net/2023/08/13/garli_2.1-7_unstable.log If you reassign this bug to another package, please mark it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that w
Bug#1080845: marked as done (Missing Build-Depends on python3-setuptools)
Your message dated Sat, 09 Nov 2024 23:09:49 + with message-id and subject line Bug#1080845: fixed in yp-svipc 0.16-7 has caused the Debian Bug report #1080845, regarding Missing Build-Depends on python3-setuptools 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.) -- 1080845: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1080845 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: yp-svipc Version: 0.16-6 Severity: important User: debian-pyt...@lists.debian.org Usertags: dh-python-no-setuptools Tags: sid, trixie This package failed build from source when test-built against a version of dh-python without a python3-setuptools dependency. distutils is no longer part of the Python standard library, since 3.12. But a minimal version of it becomes available when the python3-setuptools package is installed. Please add a Build-Depends on python3-setuptools to your package, or migrate the package's build system away from setuptools/distutils. If you run into any difficulties, please raise them on debian-pyt...@lists.debian.org. This bug has been filed at "important" severity, as the change hasn't been made in dh-python yet, but this may be raised to RC before the trixie release. Thanks, Stefano --- End Message --- --- Begin Message --- Source: yp-svipc Source-Version: 0.16-7 Done: Alexandre Detiste We believe that the bug you reported is fixed in the latest version of yp-svipc, 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 1080...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Alexandre Detiste (supplier of updated yp-svipc 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: Sat, 09 Nov 2024 23:36:00 +0100 Source: yp-svipc Architecture: source Version: 0.16-7 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers Changed-By: Alexandre Detiste Closes: 1080845 Changes: yp-svipc (0.16-7) unstable; urgency=medium . * Team Upload * Add explicit dependency on python3-setuptools (Closes: #1080845) Checksums-Sha1: ff2a44b0adc0b022788faf88e9e3492967c4a6a7 2095 yp-svipc_0.16-7.dsc ec5e3986dfcb50c26108a77cedb1bdacb6a7c52a 4304 yp-svipc_0.16-7.debian.tar.xz 74f31365d0a000ba069d0eb1cdb0a923f6007b76 8662 yp-svipc_0.16-7_source.buildinfo Checksums-Sha256: c3edf4d613d481324f2158fcc81895fe7956c3c7a26258ed932409d7ceb8d342 2095 yp-svipc_0.16-7.dsc fb52f09f5fdbfcf62ad5d5d911aca50f54090f986b95f5305acb78b37141cd6a 4304 yp-svipc_0.16-7.debian.tar.xz eea5be078df8823b1346fd84efdeba7078be48656c3e4c24e07a2d51103bc1f4 8662 yp-svipc_0.16-7_source.buildinfo Files: 6fd3bc55273b736cb4cac4745c09469c 2095 science optional yp-svipc_0.16-7.dsc 8cf9a54ece1bcae62ea5496e169f7161 4304 science optional yp-svipc_0.16-7.debian.tar.xz d1ab39f8b5f9ee0ae53e78961b043175 8662 science optional yp-svipc_0.16-7_source.buildinfo -BEGIN PGP SIGNATURE- iQJFBAEBCgAvFiEEj23hBDd/OxHnQXSHMfMURUShdBoFAmcv5WYRHHRjaGV0QGRl Ymlhbi5vcmcACgkQMfMURUShdBoyWQ//R5xGGHjNmMDikRJACCjxjLSMeuMXTOeB jWVemevcBSpof3yAk6BT7efWaTG7285N1hvf62ZEocyCitUBpTVMPyvOTAZJMCSv A/mBWefrOGGnFtVvJN4JvkoSVG4Ks44SZ1ZgGm5yFaRHcqZd2QmuZybVKH1rou2p njo9bkAR5o2Ql/qXZ4sT3xQx/6f9RgMjfdSA5q4dYWq+q/HacmBDK74T1PfbE7eW qa99wVkUFADxfFINob8+o4TvJpo3WyefO/Khc94EmwdmhwaMI4OO9jjd13WOzXMp b+MOXEELpFD1FIl0VdvEzD31WxmbJF83+Haz8jic+/qwvdK1hiEtBVMjfs18tFY2 vmD76+vE7XCwK8jND14aCpPOHY+cQNP3B4Bk2Hgsac7dTfyRYrORns3F/Zd7a/QW f8Y6nO/mO94J7w96/OvhYG1i5sXQg3byBVorxyciFEqCJ0buCuQsYpxk3PDGUmhg 7Gs9qxU7XueafE25C7kjzXlN7aqQcAZfT8ZtKdHryRV03d3LwKDhAcps/AwWr3NS BN5qjEJYK7PLt34GWMJKeZQqim9hbA5TtFPuLIv+qXLTnnUhePxPwnV8WmqTNKNP WJ3983ZnHziok/y/mWwNPg8ziSdzCiXTsVMPXGNywaFS8AYCqY3fvEpxYi5tlGz1 JUHa+fjtx7g= =kFfa -END PGP SIGNATURE- pgpWoIia9073c.pgp Description: PGP signature --- End Message ---
Bug#1049030: marked as done (nfdump: Fails to build source after successful build)
Your message dated Sat, 09 Nov 2024 22:04:52 + with message-id and subject line Bug#1049030: fixed in nfdump 1.7.5-2 has caused the Debian Bug report #1049030, regarding nfdump: Fails to build source after successful build 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.) -- 1049030: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1049030 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: nfdump Version: 1.7.1-3 Severity: minor Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-sab-20230813 ftbfs-source-after-build User: debian...@lists.debian.org Usertags: qa-doublebuild Hi, This package fails to build a source package after a successful build (dpkg-buildpackage ; dpkg-buildpackage -S). This is probably a clear violation of Debian Policy section 4.9 (clean target), but this is filed as severity:minor for now, because a discussion on debian-devel showed that we might want to revisit the requirement of a working 'clean' target. More information about this class of issues, included common problems and solutions, is available at https://wiki.debian.org/qa.debian.org/FTBFS/SourceAfterBuild Relevant part of the build log: > cd /<> && runuser -u user42 -- dpkg-buildpackage --sanitize-env > -us -uc -rfakeroot -S > --- > > dpkg-buildpackage: info: source package nfdump > dpkg-buildpackage: info: source version 1.7.1-3 > dpkg-buildpackage: info: source distribution unstable > dpkg-buildpackage: info: source changed by Bernhard Schmidt > dpkg-source --before-build . > debian/rules clean > dh clean >dh_auto_clean > make -j8 clean > make[1]: Entering directory '/<>' > Making clean in src/lib > make[2]: Entering directory '/<>/src/lib' > test -z "lex.yy.c grammar.c grammar.h scanner.c scanner.h *.gch" || rm -f > lex.yy.c grammar.c grammar.h scanner.c scanner.h *.gch > test -z "libnfdump.la" || rm -f libnfdump.la > rm -rf .libs _libs > rm -f *.o > rm -f *.lo > rm -f sgregex/*.o > rm -rf sgregex/.libs sgregex/_libs > rm -f ./so_locations > rm -f sgregex/*.lo > make[2]: Leaving directory '/<>/src/lib' > Making clean in src/output > make[2]: Entering directory '/<>/src/output' > test -z "*.gch" || rm -f *.gch > rm -rf .libs _libs > test -z "liboutput.a" || rm -f liboutput.a > rm -f *.o > rm -f *.lo > make[2]: Leaving directory '/<>/src/output' > Making clean in src/conf > make[2]: Entering directory '/<>/src/conf' > test -z "*.gch" || rm -f *.gch > rm -rf .libs _libs > test -z "libconf.a" || rm -f libconf.a > rm -f *.o > rm -f *.lo > make[2]: Leaving directory '/<>/src/conf' > Making clean in src/netflow > make[2]: Entering directory '/<>/src/netflow' > test -z "*.gch" || rm -f *.gch > rm -rf .libs _libs > test -z "libnetflow.a" || rm -f libnetflow.a > rm -f *.o > rm -f *.lo > make[2]: Leaving directory '/<>/src/netflow' > Making clean in src/collector > make[2]: Entering directory '/<>/src/collector' > test -z "*.gch" || rm -f *.gch > rm -rf .libs _libs > test -z "libcollector.a" || rm -f libcollector.a > rm -f *.o > rm -f *.lo > make[2]: Leaving directory '/<>/src/collector' > Making clean in src/maxmind > make[2]: Entering directory '/<>/src/maxmind' > test -z "*.gch" || rm -f *.gch > rm -rf .libs _libs > test -z "libmaxmind.a" || rm -f libmaxmind.a > rm -f *.o > rm -f *.lo > make[2]: Leaving directory '/<>/src/maxmind' > Making clean in src/nfdump > make[2]: Entering directory '/<>/src/nfdump' > test -z "*.gch" || rm -f *.gch > rm -rf .libs _libs > rm -f *.o > rm -f *.lo > rm -f nfdump > make[2]: Leaving directory '/<>/src/nfdump' > Making clean in src/nfcapd > make[2]: Entering directory '/<>/src/nfcapd' > test -z " *.gch" || rm -f *.gch > rm -rf .libs _libs > rm -f *.o > rm -f *.lo > rm -f nfcapd > make[2]: Leaving directory '/<>/src/nfcapd' > Making clean in src/nfanon
Bug#1086366: marked as done (nfdump: FTBFS: FAIL: runtest.sh)
Your message dated Sat, 09 Nov 2024 22:04:52 + with message-id and subject line Bug#1086366: fixed in nfdump 1.7.5-2 has caused the Debian Bug report #1086366, regarding nfdump: FTBFS: FAIL: runtest.sh 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.) -- 1086366: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1086366 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:nfdump Version: 1.7.4-1 Severity: serious Tags: ftbfs Dear maintainer: During a rebuild of all packages in unstable, your package failed to build: [...] debian/rules binary dh binary dh_update_autotools_config dh_autoreconf libtoolize: putting auxiliary files in '.'. libtoolize: copying file './ltmain.sh' libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'm4'. libtoolize: copying file 'm4/libtool.m4' libtoolize: copying file 'm4/ltoptions.m4' libtoolize: copying file 'm4/ltsugar.m4' libtoolize: copying file 'm4/ltversion.m4' libtoolize: copying file 'm4/lt~obsolete.m4' configure.ac:18: installing './compile' configure.ac:27: installing './config.guess' [... snipped ...] tcp flags= 0x02 ..S. src port =80 @@ -111,9 +111,9 @@ engine type =50 engine ID= 4 export sysid = 0 - first= 1562841031310 [2019-07-11 10:30:31.310] - last = 1562841031360 [2019-07-11 10:30:31.360] - received at = 1562841029361 [2019-07-11 10:30:29.361] + first= 1562833831310 [2019-07-11 10:30:31.310] + last = 1562833831360 [2019-07-11 10:30:31.360] + received at = 1562833829361 [2019-07-11 10:30:29.361] proto= 6 TCP tcp flags= 0x10 ...A src port =80 @@ -142,9 +142,9 @@ engine type =50 engine ID= 4 export sysid = 0 - first= 1562841032310 [2019-07-11 10:30:32.310] - last = 1562841032360 [2019-07-11 10:30:32.360] - received at = 1562841029361 [2019-07-11 10:30:29.361] + first= 1562833832310 [2019-07-11 10:30:32.310] + last = 1562833832360 [2019-07-11 10:30:32.360] + received at = 1562833829361 [2019-07-11 10:30:29.361] proto= 6 TCP tcp flags= 0x01 ...F src port =80 @@ -173,9 +173,9 @@ engine type =50 engine ID= 4 export sysid = 0 - first= 1562841032311 [2019-07-11 10:30:32.311] - last = 1562841032361 [2019-07-11 10:30:32.361] - received at = 1562841029361 [2019-07-11 10:30:29.361] + first= 1562833832311 [2019-07-11 10:30:32.311] + last = 1562833832361 [2019-07-11 10:30:32.361] + received at = 1562833829361 [2019-07-11 10:30:29.361] proto= 6 TCP tcp flags= 0x12 ...A..S. src port = 2 @@ -204,9 +204,9 @@ engine type =50 engine ID= 4 export sysid = 0 - first= 1562841033311 [2019-07-11 10:30:33.311] - last = 1562841033361 [2019-07-11 10:30:33.361] - received at = 1562841029361 [2019-07-11 10:30:29.361] + first= 1562833833311 [2019-07-11 10:30:33.311] + last = 1562833833361 [2019-07-11 10:30:33.361] + received at = 1562833829361 [2019-07-11 10:30:29.361] proto= 6 TCP tcp flags= 0x10 ...A src port = 2 @@ -235,9 +235,9 @@ engine type =50 engine ID= 4 export sysid = 0 - first= 1562841034311 [2019-07-11 10:30:34.311] - last = 1562841034361 [2019-07-11 10:30:34.361] - received at = 1562841029361 [2019-07-11 10:30:29.361] + first= 1562833834311 [2019-07-11 10:30:34.311] + last = 1562833834361 [2019-07-11 10:30:34.361] + received at = 1562833829361 [2019-07-11 10:30:29.361] proto= 6 TCP tcp flags= 0x01 ...F src port = 2 @@ -266,9 +266,9 @@ engine type =60 engine ID= 5 export sysid =
Bug#1086965: marked as done (python-treetime: Python SyntaxWarning)
Your message dated Sat, 09 Nov 2024 21:49:51 + with message-id and subject line Bug#1086965: fixed in python-treetime 0.11.4-1 has caused the Debian Bug report #1086965, regarding python-treetime: Python SyntaxWarning 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.) -- 1086965: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1086965 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python-treetime Version: 0.11.1-1 User: debian-pyt...@lists.debian.org Usertags: syntaxwarning Hi Maintainer The SyntaxWarning below were emitted when this package was tested with pipuarts[1]. Regards Graham [1] https://piuparts.debian.org/sid/source/p/python-treetime.html Setting up python3-treetime (0.11.1-1) ... /usr/lib/python3/dist-packages/treetime/merger_models.py:187: SyntaxWarning: invalid escape sequence '\k' ''' /usr/lib/python3/dist-packages/treetime/merger_models.py:197: SyntaxWarning: invalid escape sequence '\l' ''' /usr/lib/python3/dist-packages/treetime/merger_models.py:209: SyntaxWarning: invalid escape sequence '\l' ''' --- End Message --- --- Begin Message --- Source: python-treetime Source-Version: 0.11.4-1 Done: Étienne Mollier We believe that the bug you reported is fixed in the latest version of python-treetime, 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 1086...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Étienne Mollier (supplier of updated python-treetime 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: Sat, 09 Nov 2024 21:48:14 +0100 Source: python-treetime Architecture: source Version: 0.11.4-1 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team Changed-By: Étienne Mollier Closes: 1086965 Changes: python-treetime (0.11.4-1) unstable; urgency=medium . * New upstream version 0.11.4 * d/control: add myself to uploaders. * d/control: declare compliance to standards version 4.7.0. * syntaxwarning.patch: fix SyntaxWarning. (Closes: #1086965) Checksums-Sha1: 380ddd980335ba9909d450804b9fa7e73a97b2da 2611 python-treetime_0.11.4-1.dsc eb3751fd5c8419d20d297ee2b9b5a198e77c7a6b 5117294 python-treetime_0.11.4.orig-debian-tests-data.tar.gz e9098c4772d3d64b885e3fb167c7683f68ecb5ba 1290911 python-treetime_0.11.4.orig.tar.gz 6f49c6507a0994122d3553e81274c4c63417d445 8028 python-treetime_0.11.4-1.debian.tar.xz 0ba8d404074e6fd00ac1e0b5f08bdbbabc0665f2 8764 python-treetime_0.11.4-1_amd64.buildinfo Checksums-Sha256: 5b05bd1e62518f95d3c8aedb1914ed95bbfa4ad2bb3a936eb82f7fbbb69cf06c 2611 python-treetime_0.11.4-1.dsc 2f496507d1fccb378335bacd521adb2f7b70a5b32433a142b03804190ede85b6 5117294 python-treetime_0.11.4.orig-debian-tests-data.tar.gz 0b41c4a60e020ad7888693ebc4e7f8001df977243154bf577f1567a48f71b31c 1290911 python-treetime_0.11.4.orig.tar.gz 9127e8c3a9b92adbb3bf90365be01afbdd960db1cd4eb81ca8c3032a46bfe041 8028 python-treetime_0.11.4-1.debian.tar.xz 50fa7e5bd30e014ab9a1c86c2190748dabf5a8550df11d15f05bf11a865735ad 8764 python-treetime_0.11.4-1_amd64.buildinfo Files: 4edcac304ba7f03041cfcce4ece88099 2611 science optional python-treetime_0.11.4-1.dsc 6a060fc079163519d2249d309e30e27a 5117294 science optional python-treetime_0.11.4.orig-debian-tests-data.tar.gz c23032502b1929f8ad095be32dfa6e86 1290911 science optional python-treetime_0.11.4.orig.tar.gz 0fc5b9b1053e022f8ffe9b4d599b5fa5 8028 science optional python-treetime_0.11.4-1.debian.tar.xz c4170c52777c7290773806aec1f30494 8764 science optional python-treetime_0.11.4-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJIBAEBCgAyFiEEj5GyJ8fW8rGUjII2eTz2fo8NEdoFAmcv1MQUHGVtb2xsaWVy QGRlYmlhbi5vcmcACgkQeTz2fo8NEdoyvA//YZ1QdLSu02j2VfCLbbB9+oqrI/F3 8BQU+dc4zbyzYUEOPdg8ZebrYnUY+vAuGjqNtKDfw/n1J9LNUxM3VaVon4lpwp7P NnQzzTz64nw3sVpZrP7k9s9Y4EiatMmEXy9bYlln9TOhARgGbyZAv/c75hF8DGrE Ab59wrDr6TO/ualtiOKAIVyj6VqolvMijoFIxDC+7+9RYZdvcHvrGJl1y10q/0Bt dVV7BZU+ShegeRHqTiUuLKx583SkgcGyv7hAhf5LHCSMM0qXDI7NFZ3HDziObMlX E9Vj83Lr6lHYSq1m6/v6beTbIxyBuowOdn5DfGUw7Mwr74mQn5HFqe
Processed: Update bug fix information
Processing commands for cont...@bugs.debian.org:
> unarchive 1034800
Bug #1034800 {Done: Lena Voytek } [liblua5.4-0]
lualib5.4 is missing expected symbols
Unarchived Bug 1034800
> fixed 1034800 lua5.4/5.4.4-3+deb12u1
Bug #1034800 {Done: Lena Voytek } [liblua5.4-0]
lualib5.4 is missing expected symbols
Marked as fixed in versions lua5.4/5.4.4-3+deb12u1.
> fixed 1034800 lua5.4/5.4.6-2
Bug #1034800 {Done: Lena Voytek } [liblua5.4-0]
lualib5.4 is missing expected symbols
Marked as fixed in versions lua5.4/5.4.6-2; no longer marked as fixed in
versions lua5.4/5.4.6-2.
> close 1034800
Bug #1034800 {Done: Lena Voytek } [liblua5.4-0]
lualib5.4 is missing expected symbols
Bug 1034800 is already marked as done; not doing anything.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1034800: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034800
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1085394: marked as done (debiancontributors: Incorrect python code to post Data in README)
Your message dated Sat, 09 Nov 2024 21:19:20 +
with message-id
and subject line Bug#1085394: fixed in debiancontributors 0.7.11
has caused the Debian Bug report #1085394,
regarding debiancontributors: Incorrect python code to post Data in README
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.)
--
1085394: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1085394
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: debiancontributors
Version: 0.7.10
Severity: important
x-debbugs-cc: enr...@debian.org, ti...@debian.org, er...@debian.org
Tags: patch
Hi,
The current python example mentioned in the README.md does not work and gives a
few errors
with fallouts with change in API and newer datetime lib.
Please consider to apply attached patch.
Thanks,
Nilesh
From 8f09dfd6e06455d5eca8f83920159c4ea6883863 Mon Sep 17 00:00:00 2001
From: Nilesh Patra
Date: Sat, 19 Oct 2024 01:59:47 +0530
Subject: [PATCH] Fix python code to post Data in README
diff --git a/README.md b/README.md
index ab53f99..d4884f5 100644
--- a/README.md
+++ b/README.md
@@ -45,7 +45,7 @@ Assuming you [created a data source in the website][newds] called
`myteam.debian.net` with authentication token 'foobar'.
import debiancontributors as dc
- from datetime import Date
+ from datetime import date
# Create a Submission
s = dc.Submission("myteam.debian.net")
@@ -53,15 +53,17 @@ Assuming you [created a data source in the website][newds] called
# Add contribution data to it
s.add_contribution(
dc.Identifier("email", "enr...@debian.org"),
- dc.Contribution("shave_yaks", Date(2013, 1, 1), Date(2013, 12, 23)))
+ dc.Contribution("shave_yaks", date(2013, 1, 1), date(2013, 12, 23)))
# Post it to the site
- success, info = s.post("foobar")
+ s.set_auth_token("foobar")
+ success, info = s.post()
if not success:
import json
print("submission failed:")
print(json.dumps(info, indent=1))
-
+ else:
+ print("submission succeeded")
## Posting data the way you like
--
2.43.0
--- End Message ---
--- Begin Message ---
Source: debiancontributors
Source-Version: 0.7.11
Done: Tiago Bortoletto Vaz
We believe that the bug you reported is fixed in the latest version of
debiancontributors, 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 1085...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Tiago Bortoletto Vaz (supplier of updated debiancontributors
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: Sat, 09 Nov 2024 15:57:28 -0500
Source: debiancontributors
Architecture: source
Version: 0.7.11
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team
Changed-By: Tiago Bortoletto Vaz
Closes: 1085394
Changes:
debiancontributors (0.7.11) unstable; urgency=medium
.
* Team upload.
* Move from deprecated distutils to setuptools
* Fix instructions in README related to API changes and newer datetime
library. Thanks to Nilesh Patra. Closes: #1085394
* Bump Standards-Version to 4.7.0 (no changes).
Checksums-Sha1:
c8d64b210f6a7b9e632bd65b25212455746f642d 1944 debiancontributors_0.7.11.dsc
48c1b09d47ecab3b642ea24797634a7bf77ee395 39088 debiancontributors_0.7.11.tar.xz
2fa1779f2317a6cf821c181a525290c395d85117 7073
debiancontributors_0.7.11_amd64.buildinfo
Checksums-Sha256:
543e677cb0cfd3b6f9230fbd641f7f7ccc4ff9cdfa940bb9b213027c67ec6800 1944
debiancontributors_0.7.11.dsc
d47587d5ef544aaaf94967fa257f621ea305c2b1bc273f89a20cfdf5079f95b2 39088
debiancontributors_0.7.11.tar.xz
9d61c073e9511377a682789525b72e5b1e3353e07b02c502d2a6869806e642d0 7073
debiancontributors_0.7.11_amd64.buildinfo
Files:
737310f77e904ef1de073d8483df68bf 1944 python optional
debiancontributors_0.7.11.dsc
2e98b6f3c3cdf6392d4ec7b04211f6ff 39088 python optional
debiancontributors_0.7.11.tar.xz
57f87cc064c3f12b80cff972a35f4ef2 7073 python optional
debiancontributors_0.7.11_amd64.buildinfo
-BEGIN PGP SIGNATURE-
iQJFBAEBCgAvFiEEOAYLMZqeqHbTW
Processed: ITP: fritzconnection -- Communicate with the AVM FRITZ!Box router using TR-064 and HTTP protocols
Processing commands for cont...@bugs.debian.org: > close 1087217 Bug #1087217 [wnpp] ITP: fritzconnection -- Communicate with the AVM FRITZ!Box router using TR-064 and HTTP protocols Marked Bug as done > stop Stopping processing here. Please contact me if you need assistance. -- 1087217: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1087217 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1086912: marked as done (phyml: depends on openmpi on 32-bit architectures)
Your message dated Sat, 09 Nov 2024 19:34:13 + with message-id and subject line Bug#1086912: fixed in phyml 3:3.3.20220408-4 has caused the Debian Bug report #1086912, regarding phyml: depends on openmpi on 32-bit architectures 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.) -- 1086912: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1086912 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: phyml Severity: serious Hi, phyml depends on openmpi on 32-bit architectures, which has been removed in openmpi 5. Thus this package needs to stop depending on it on those architectures. There are a couple of options: - build-dep on mpi-default-dev instead of openmpi-dev, so that the MPICH implementation can be used on those architectures. - remove the package from 32-bit architectures (armel, armhf and i386) by filing an RM bug against ftp.debian.org See [1] for the transition bug and [2] for the tracker. Cheers, Emilio [1] https://bugs.debian.org/1064810 [2] https://release.debian.org/transitions/html/openmpi-rm32.html --- End Message --- --- Begin Message --- Source: phyml Source-Version: 3:3.3.20220408-4 Done: Étienne Mollier We believe that the bug you reported is fixed in the latest version of phyml, 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 1086...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Étienne Mollier (supplier of updated phyml 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: Sat, 09 Nov 2024 19:50:59 +0100 Source: phyml Architecture: source Version: 3:3.3.20220408-4 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team Changed-By: Étienne Mollier Closes: 1086912 Changes: phyml (3:3.3.20220408-4) unstable; urgency=medium . * d/p/series: disable cross.patch. The cross compilation procedure relies on mpi-c.pc to operate properly, but mpich misses it for the moment. * d/control: migrate to mpi-default-*. (Closes: #1086912) * d/control: declare compliance to standards version 4.7.0. * d/control: migrate to pkgconf. * d/patches/*: normalise header, notably Last-Update format. Checksums-Sha1: f3e5bfd1526abcdcf50714ba29beefb7b491a94e 2256 phyml_3.3.20220408-4.dsc 4ca11e948f0e7e8585f0daad5f709e2be3170331 27020 phyml_3.3.20220408-4.debian.tar.xz Checksums-Sha256: 1ffe5c6a981ec3c58605049aede36ed4967603d50f08918a035d6d2653cac2da 2256 phyml_3.3.20220408-4.dsc a76294e8f8b118a105217755ea67701870ffed751c8940b54168f3b578ff1fad 27020 phyml_3.3.20220408-4.debian.tar.xz Files: 1631708859c9d3e8cfffa4bfea94778d 2256 science optional phyml_3.3.20220408-4.dsc 48050b4235d2e54572c398938a25a5e4 27020 science optional phyml_3.3.20220408-4.debian.tar.xz -BEGIN PGP SIGNATURE- iQJIBAEBCgAyFiEEj5GyJ8fW8rGUjII2eTz2fo8NEdoFAmcvtLQUHGVtb2xsaWVy QGRlYmlhbi5vcmcACgkQeTz2fo8NEdrPCQ//ehaL9NVZxG/zBehcs9R+XPPTDDQp uPttAmuYzapGWuyjV/kdZLrHB75abBSjtU8xXHXNT/VeGJY60Uyc6HYi7hKQ6CQ+ yZhiYOXcJLcTnZ6dxGXpQpcDS2BVnnyb4uHGoNQTvAypOrsmgGMjnuAzwGsLJ6wC qi6GVxKGDtZkx3/bhoMliwqWWFAttV33dZHR4Wsb+3eYViI0BtLIfzpZXVaJQB2N wOGDgN1lEPFL9K+2foJ25QjsiOQumeD2cFKcgEx/v1FdwkyzG9qISjXOm2QU3rVS g3f53uA+Y8QDPR4svz/Soy03GYo6WgXqByBi/73jztmePCpuEKakuNuPugIN/AiN TuYIuMJnXVtmjo78mEdn9cZuR/ChB7nk0oOjrnuXbkjqaLrNfHB9/KgV8MWrdk1E EUaik5+TY8uYCfWKpU8vCJ9wfCkuyFbyDirtPvN+ZBOVLNGpqDUAzyKJ01/fts1s apIMZEBAv+sM1r1tU7n0Rh9bDzD+JFza3g9ardNzFiISdJUtq1Y5FMTy3h9p+rGU 4dnqPpUMGQvy5fA8669NOMmVrKUoumxCAV+IltPPLUeDepWk9Gxjhlm9GuXWsmy0 YHogVDHLdT8k5Ntvh3ZX2xEL97XZBWq3CEUVqZ2gPWOyZ0I52z6rqp/DLRRZ2F4W zadHtA52jx/Sg/k= =fudw -END PGP SIGNATURE- pgpONhq0VjtK7.pgp Description: PGP signature --- End Message ---
Bug#1063834: marked as done (displayfont man page: "showfont (no such manpage?)")
Your message dated Sat, 09 Nov 2024 19:19:30 + with message-id and subject line Bug#1063834: fixed in console-cyrillic 0.9-18 has caused the Debian Bug report #1063834, regarding displayfont man page: "showfont (no such manpage?)" 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.) -- 1063834: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063834 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: console-cyrillic Version: 0.9-17.2 Severity: minor The SEE ALSO section of the displayfont(1) manual page says: showfont (no such manpage?) But it does exist: $ dpkg -S showfont.1 x11-xfs-utils: /usr/share/man/man1/showfont.1.gz -- Jakub Wilk --- End Message --- --- Begin Message --- Source: console-cyrillic Source-Version: 0.9-18 Done: наб We believe that the bug you reported is fixed in the latest version of console-cyrillic, 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 1063...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. наб (supplier of updated console-cyrillic 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: Sat, 09 Nov 2024 18:57:28 +0100 Source: console-cyrillic Architecture: source Version: 0.9-18 Distribution: unstable Urgency: medium Maintainer: Anton Zinoviev Changed-By: наб Closes: 1030816 1063760 1063834 1086862 Changes: console-cyrillic (0.9-18) unstable; urgency=medium . [ наб ] * Standards-Version: 4.7.0 (routine-update) * Rules-Requires-Root: binary-targets (+ modernise root handling in d/rules) * d/rules: drop checkdir macro * List the files from debian/binary.tar.gz.uu in d/source/include-binaries and unpack permanently instead of unpacking/repacking each time (=> drop Build-Depends: sharutils) * d/rules: dpkg-gencontrol: warning: -isp is deprecated; it is without effect * debian/makeenc: mark executable, execute directly * d/rules: streamline installation * dumppsf: fix dumping mode 1 and mode 3 fonts (Closes: #1063760) * Remove d/conf*, d/init.d, d/po*, d/templates, d/postinst: not installed since 0.9-17 (=> Build-Depends-Indep: drop po-debconf) * d/control: drop versioned dependency on trscripts (>= 1.5 unneeded since woody) * displayfont: disable UTF-8 mode only if stty -iutf8 (Closes: #1030816) * Ignore lintian postrm-contains-additional-updaterc.d-calls (see 0.9-17) * Fix lintian bad-whatis-entry * Add myself as uploader and VCS fields (Closes: #1086862) * d/watch: add fake returning "0.No-Site" * d/copyright: DEP-5 + old-fsf-address-in-copyright-file . [ Jakub Wilk ] * Xref showconsolefont(8) instead of "(no such manpage?)" showfont Closes: #1063834 Checksums-Sha1: fc7c140bd6764ec3adcf68cc2b60951a7ef766c9 2062 console-cyrillic_0.9-18.dsc 30e741f648344aa67b50b08e3a0c5bc6ab14b54f 69884 console-cyrillic_0.9-18.debian.tar.xz df5e7e179746a077dd1abffb10b64c49247433b9 4882 console-cyrillic_0.9-18_amd64.buildinfo Checksums-Sha256: 0cee3f8ea4721c02397e46866d18f29f2d345a8f69537fb91e0670b48ea1b08e 2062 console-cyrillic_0.9-18.dsc 16bf10cb8cdbfaeb6d09d6e4cbab7019eeb0483070724cd550ca437b16501034 69884 console-cyrillic_0.9-18.debian.tar.xz cf7f8df5d0d4bf9ec2f447972f9f09eaad93a3ae71216e87e31dbc6f444efabc 4882 console-cyrillic_0.9-18_amd64.buildinfo Files: 09ca5e46da24dd19ae6579f703a9ce42 2062 misc optional console-cyrillic_0.9-18.dsc eeaa78023d06bd5580be05cc7e19625a 69884 misc optional console-cyrillic_0.9-18.debian.tar.xz 6baecbbaa27b52ef45644df7367dfbf7 4882 misc optional console-cyrillic_0.9-18_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJFBAEBCgAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAmcvsWwRHHRpbGxlQGRl Ymlhbi5vcmcACgkQV4oElNHGRtF8Ew//X75Ybm0uQrylZRKHdE1Cc1eQwAQ4SnWR T4J3I7Y2O6xAOm7yVdilwde0FIJps8aCjt8WDjYy6eabu3Wmt1v7MWyhcWXkJFLY MFVxPK/Ydd+pD/97aibHNEbZ3020XDZI8HibafYekXc+vBG50z1jrpMGDPzL4W2l lrm0sZdfELCwYHrtWIyl136UEa8N9nWB/+3jhSLRpNlb4ZVUFcO/fSX1aqr+vrED 9OtLHQ4RBSfOdY1pC5lgLFlyqzM6gbxZl+4158XUeTsA7PZsTHDoc49f591dQR+y XvEy0VHMnsQRcTywA4jsvK1PNf/vzn1LWxBS5OpjLTZs3q047I9+YOsFiCk85nH/ 9F1c
Bug#1081637: marked as done (FTBFS with Python 3.13)
Your message dated Sat, 09 Nov 2024 19:21:49 + with message-id and subject line Bug#1081637: fixed in nlopt 2.7.1-6 has caused the Debian Bug report #1081637, regarding FTBFS with Python 3.13 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.) -- 1081637: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1081637 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: nlopt Version: 2.7.1-5 Severity: normal Tags: upstream patch User: debian-pyt...@lists.debian.org Usertags: python3.13 Forwarded: https://github.com/stevengj/nlopt/issues/565 This package failed build from source when test-built against a version of python3-defaults that includes 3.13 as a supported version. To reproduce this issue, build against python3-defaults (python3-all-dev etc.) from Debian experimental. What's new in Python 3.13: https://docs.python.org/3.13/whatsnew/3.13.html Log snippet: cd /<>/obj-aarch64-linux-gnu-python3.13/src/octave && /usr/bin/c++ -DNLOPT_DLL -Dnlopt_optimize_EXPORTS -I/usr/include/octave-9.2.0 -I/usr/include/octave-9.2.0/octave -I/<>/obj-aarch64-linux-gnu-python3.13/src/octave -I/<>/src/api -I/<>/obj-aarch64-linux-gnu-python3.13 -std=c++11 -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -mbranch-protection=standard -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -MD -MT src/octave/CMakeFiles/nlopt_optimize.dir/nlopt_optimize-oct.cc.o -MF CMakeFiles/nlopt_optimize.dir/nlopt_optimize-oct.cc.o.d -o CMakeFiles/nlopt_optimize.dir/nlopt_optimize-oct.cc.o -c /<>/src/octave/nlopt_optimize-oct.cc /<>/obj-aarch64-linux-gnu-python3.13/src/swig/CMakeFiles/nlopt_python.dir/nloptPYTHON_wrap.cxx: In function ‘double func_python(unsigned int, const double*, double*, void*)’: /<>/obj-aarch64-linux-gnu-python3.13/src/swig/CMakeFiles/nlopt_python.dir/nloptPYTHON_wrap.cxx:5085:22: error: ‘PyEval_CallObject’ was not declared in this scope; did you mean ‘PyObject_CallObject’? 5085 | PyObject *result = PyEval_CallObject((PyObject *) f, arglist); | ^ | PyObject_CallObject /<>/obj-aarch64-linux-gnu-python3.13/src/swig/CMakeFiles/nlopt_python.dir/nloptPYTHON_wrap.cxx: In function ‘void mfunc_python(unsigned int, double*, unsigned int, const double*, double*, void*)’: /<>/obj-aarch64-linux-gnu-python3.13/src/swig/CMakeFiles/nlopt_python.dir/nloptPYTHON_wrap.cxx:5122:19: error: ‘PyEval_CallObject’ was not declared in this scope; did you mean ‘PyObject_CallObject’? 5122 | PyObject *res = PyEval_CallObject((PyObject *) f, arglist); | ^ | PyObject_CallObject /<>/obj-aarch64-linux-gnu-python3.13/src/swig/CMakeFiles/nlopt_python.dir/nloptPYTHON_wrap.cxx: In function ‘PyObject* _wrap_opt_optimize__SWIG_1(PyObject*, Py_ssize_t, PyObject**)’: /<>/obj-aarch64-linux-gnu-python3.13/src/swig/CMakeFiles/nlopt_python.dir/nloptPYTHON_wrap.cxx:8937:16: warning: argument 2 null where non-null expected [-Wnonnull] 8937 | std::memcpy(array_data(resultobj), (&result)->empty() ? NULL : &result[0], | ~~~^~~ 8938 | sizeof(double) * sz); | In file included from /usr/include/features.h:510, from /usr/include/assert.h:35, from /usr/include/python3.13/Python.h:19, from /<>/obj-aarch64-linux-gnu-python3.13/src/swig/CMakeFiles/nlopt_python.dir/nloptPYTHON_wrap.cxx:198: /usr/include/aarch64-linux-gnu/bits/string_fortified.h:26:1: note: in a call to function ‘void* memcpy(void*, const void*, size_t)’ declared ‘nonnull’ 26 | __NTH (memcpy (void *__restrict __dest, const void *__restrict __src, | ^ /<>/obj-aarch64-linux-gnu-python3.13/src/swig/CMakeFiles/nlopt_python.dir/nloptPYTHON_wrap.cxx: In function ‘PyObject* _wrap_opt_get_lower_bounds__SWIG_1(PyObject*, Py_ssize_t, PyObject**)’: /<>/obj-aarch64-linux-gnu-python3.13/src/swig/CMakeFiles/nlopt_python.dir/nloptPYTHON_wrap.cxx:11170:16: warning: argument 2 null where non-null expected [-Wnonnull] 11170 | std::memcpy(array_data(resultobj), (&result)->empty() ? NULL : &result[0], | ~~~^~~ 11171 | sizeof(double) * sz); | /usr/include/aarch64-linu
Bug#1063760: marked as done (dumppsf can't dump some fonts)
Your message dated Sat, 09 Nov 2024 19:19:30 + with message-id and subject line Bug#1063760: fixed in console-cyrillic 0.9-18 has caused the Debian Bug report #1063760, regarding dumppsf can't dump some fonts 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.) -- 1063760: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063760 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: console-cyrillic Version: 0.9-17.2 dumppsf fails to dump some fonts, e.g.: $ zcat /usr/share/consolefonts/Uni2-TerminusBold14.psf.gz > tmp.psf $ dumppsf tmp.psf PSF mode 3, charsize=14 Read 9776bytes of unicode table -- System Information: Architecture: i386 Versions of packages console-cyrillic depends on: ii perl-base 5.36.0-7+deb12u1 ii debconf 1.5.82 ii kbd 2.5.1-1+b1 Versions of packages console-cyrillic suggests: ii perl5.36.0-7+deb12u1 ii console-setup 1.221 -- Jakub Wilk --- End Message --- --- Begin Message --- Source: console-cyrillic Source-Version: 0.9-18 Done: наб We believe that the bug you reported is fixed in the latest version of console-cyrillic, 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 1063...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. наб (supplier of updated console-cyrillic 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: Sat, 09 Nov 2024 18:57:28 +0100 Source: console-cyrillic Architecture: source Version: 0.9-18 Distribution: unstable Urgency: medium Maintainer: Anton Zinoviev Changed-By: наб Closes: 1030816 1063760 1063834 1086862 Changes: console-cyrillic (0.9-18) unstable; urgency=medium . [ наб ] * Standards-Version: 4.7.0 (routine-update) * Rules-Requires-Root: binary-targets (+ modernise root handling in d/rules) * d/rules: drop checkdir macro * List the files from debian/binary.tar.gz.uu in d/source/include-binaries and unpack permanently instead of unpacking/repacking each time (=> drop Build-Depends: sharutils) * d/rules: dpkg-gencontrol: warning: -isp is deprecated; it is without effect * debian/makeenc: mark executable, execute directly * d/rules: streamline installation * dumppsf: fix dumping mode 1 and mode 3 fonts (Closes: #1063760) * Remove d/conf*, d/init.d, d/po*, d/templates, d/postinst: not installed since 0.9-17 (=> Build-Depends-Indep: drop po-debconf) * d/control: drop versioned dependency on trscripts (>= 1.5 unneeded since woody) * displayfont: disable UTF-8 mode only if stty -iutf8 (Closes: #1030816) * Ignore lintian postrm-contains-additional-updaterc.d-calls (see 0.9-17) * Fix lintian bad-whatis-entry * Add myself as uploader and VCS fields (Closes: #1086862) * d/watch: add fake returning "0.No-Site" * d/copyright: DEP-5 + old-fsf-address-in-copyright-file . [ Jakub Wilk ] * Xref showconsolefont(8) instead of "(no such manpage?)" showfont Closes: #1063834 Checksums-Sha1: fc7c140bd6764ec3adcf68cc2b60951a7ef766c9 2062 console-cyrillic_0.9-18.dsc 30e741f648344aa67b50b08e3a0c5bc6ab14b54f 69884 console-cyrillic_0.9-18.debian.tar.xz df5e7e179746a077dd1abffb10b64c49247433b9 4882 console-cyrillic_0.9-18_amd64.buildinfo Checksums-Sha256: 0cee3f8ea4721c02397e46866d18f29f2d345a8f69537fb91e0670b48ea1b08e 2062 console-cyrillic_0.9-18.dsc 16bf10cb8cdbfaeb6d09d6e4cbab7019eeb0483070724cd550ca437b16501034 69884 console-cyrillic_0.9-18.debian.tar.xz cf7f8df5d0d4bf9ec2f447972f9f09eaad93a3ae71216e87e31dbc6f444efabc 4882 console-cyrillic_0.9-18_amd64.buildinfo Files: 09ca5e46da24dd19ae6579f703a9ce42 2062 misc optional console-cyrillic_0.9-18.dsc eeaa78023d06bd5580be05cc7e19625a 69884 misc optional console-cyrillic_0.9-18.debian.tar.xz 6baecbbaa27b52ef45644df7367dfbf7 4882 misc optional console-cyrillic_0.9-18_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJFBAEBCgAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAmcvsWwRHHRpbGxlQGRl Ymlhbi5vcmcACgkQV4oElNHGRtF8Ew//X75Ybm0uQrylZRKHdE1Cc1eQwAQ4SnWR T4J3I7Y2O6xAOm7yVdilwde0FIJps8aCjt8WDjYy6
Bug#1030816: marked as done (displayfont turns off UTF-8 mode)
Your message dated Sat, 09 Nov 2024 19:19:29 + with message-id and subject line Bug#1030816: fixed in console-cyrillic 0.9-18 has caused the Debian Bug report #1030816, regarding displayfont turns off UTF-8 mode 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.) -- 1030816: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030816 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: console-cyrillic Version: 0.9-17.2 Apparently displayfont(1) turns off the UTF-8 mode: $ printf $'\u263A\n' # U+263A WHITE SMILING FACE ☺ $ displayfont | tail -n1 $ printf $'\u263A\n' âÿº -- Jakub Wilk --- End Message --- --- Begin Message --- Source: console-cyrillic Source-Version: 0.9-18 Done: наб We believe that the bug you reported is fixed in the latest version of console-cyrillic, 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 1030...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. наб (supplier of updated console-cyrillic 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: Sat, 09 Nov 2024 18:57:28 +0100 Source: console-cyrillic Architecture: source Version: 0.9-18 Distribution: unstable Urgency: medium Maintainer: Anton Zinoviev Changed-By: наб Closes: 1030816 1063760 1063834 1086862 Changes: console-cyrillic (0.9-18) unstable; urgency=medium . [ наб ] * Standards-Version: 4.7.0 (routine-update) * Rules-Requires-Root: binary-targets (+ modernise root handling in d/rules) * d/rules: drop checkdir macro * List the files from debian/binary.tar.gz.uu in d/source/include-binaries and unpack permanently instead of unpacking/repacking each time (=> drop Build-Depends: sharutils) * d/rules: dpkg-gencontrol: warning: -isp is deprecated; it is without effect * debian/makeenc: mark executable, execute directly * d/rules: streamline installation * dumppsf: fix dumping mode 1 and mode 3 fonts (Closes: #1063760) * Remove d/conf*, d/init.d, d/po*, d/templates, d/postinst: not installed since 0.9-17 (=> Build-Depends-Indep: drop po-debconf) * d/control: drop versioned dependency on trscripts (>= 1.5 unneeded since woody) * displayfont: disable UTF-8 mode only if stty -iutf8 (Closes: #1030816) * Ignore lintian postrm-contains-additional-updaterc.d-calls (see 0.9-17) * Fix lintian bad-whatis-entry * Add myself as uploader and VCS fields (Closes: #1086862) * d/watch: add fake returning "0.No-Site" * d/copyright: DEP-5 + old-fsf-address-in-copyright-file . [ Jakub Wilk ] * Xref showconsolefont(8) instead of "(no such manpage?)" showfont Closes: #1063834 Checksums-Sha1: fc7c140bd6764ec3adcf68cc2b60951a7ef766c9 2062 console-cyrillic_0.9-18.dsc 30e741f648344aa67b50b08e3a0c5bc6ab14b54f 69884 console-cyrillic_0.9-18.debian.tar.xz df5e7e179746a077dd1abffb10b64c49247433b9 4882 console-cyrillic_0.9-18_amd64.buildinfo Checksums-Sha256: 0cee3f8ea4721c02397e46866d18f29f2d345a8f69537fb91e0670b48ea1b08e 2062 console-cyrillic_0.9-18.dsc 16bf10cb8cdbfaeb6d09d6e4cbab7019eeb0483070724cd550ca437b16501034 69884 console-cyrillic_0.9-18.debian.tar.xz cf7f8df5d0d4bf9ec2f447972f9f09eaad93a3ae71216e87e31dbc6f444efabc 4882 console-cyrillic_0.9-18_amd64.buildinfo Files: 09ca5e46da24dd19ae6579f703a9ce42 2062 misc optional console-cyrillic_0.9-18.dsc eeaa78023d06bd5580be05cc7e19625a 69884 misc optional console-cyrillic_0.9-18.debian.tar.xz 6baecbbaa27b52ef45644df7367dfbf7 4882 misc optional console-cyrillic_0.9-18_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJFBAEBCgAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAmcvsWwRHHRpbGxlQGRl Ymlhbi5vcmcACgkQV4oElNHGRtF8Ew//X75Ybm0uQrylZRKHdE1Cc1eQwAQ4SnWR T4J3I7Y2O6xAOm7yVdilwde0FIJps8aCjt8WDjYy6eabu3Wmt1v7MWyhcWXkJFLY MFVxPK/Ydd+pD/97aibHNEbZ3020XDZI8HibafYekXc+vBG50z1jrpMGDPzL4W2l lrm0sZdfELCwYHrtWIyl136UEa8N9nWB/+3jhSLRpNlb4ZVUFcO/fSX1aqr+vrED 9OtLHQ4RBSfOdY1pC5lgLFlyqzM6gbxZl+4158XUeTsA7PZsTHDoc49f591dQR+y XvEy0VHMnsQRcTywA4jsvK1PNf/vzn1LWxBS5OpjLTZs3q047I9+YOsFiCk85nH/ 9F1cD23QeSIfo0PtTNv40DYCeAA+i855TfvNulky1Gu/X
Bug#1086862: marked as done (ITS: console-cyrillic)
Your message dated Sat, 09 Nov 2024 19:19:30 + with message-id and subject line Bug#1086862: fixed in console-cyrillic 0.9-18 has caused the Debian Bug report #1086862, regarding ITS: console-cyrillic 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.) -- 1086862: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1086862 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: console-cyrillic Severity: important X-Debbugs-Cc: Package Salvaging Team Dear Maintainer, I'm interested in salvaging your package console-cyrillic, in accordance with the Package Salvaging procedure outlined in the Developers Reference[1]. Your package meets the criteria for this process, and I would love to assist in preserving and maintaining it. As the Salvage process suggests, here is a list of the criteria that apply, in my opinion: - NMUs, especially if there has been more than one NMU in a row. - Bugs filed against the package do not have answers from the maintainer. I've set up a repository within the salvage-team space[2] to assist you with this initial setup. If you decide not to accept the ITS, this repository can easily be moved to another location, such as debian/, or any place of your choosing. I hope this service helps make the transition to using a Git repository on Salsa smoother and more convenient for you. Your package was highlighted in the Bug of the Day[3] initiative, which aims to introduce newcomers to manageable tasks and guide them through the workflow to solve them. The focus of this initiative is on migrating packages to Salsa, as it's a great way to familiarize newcomers with a consistent Git-based workflow. Best, наб [1] https://www.debian.org/doc/manuals/developers-reference/pkgs.en.html#package-salvaging [2] https://salsa.debian.org/salvage-team/console-cyrillic [3] https://salsa.debian.org/tille/tiny_qa_tools/-/wikis/Tiny-QA-tasks -- System Information: Debian Release: 12.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable-debug'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.1.0-12-amd64 (SMP w/24 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_FIRMWARE_WORKAROUND, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: console-cyrillic Source-Version: 0.9-18 Done: наб We believe that the bug you reported is fixed in the latest version of console-cyrillic, 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 1086...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. наб (supplier of updated console-cyrillic 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: Sat, 09 Nov 2024 18:57:28 +0100 Source: console-cyrillic Architecture: source Version: 0.9-18 Distribution: unstable Urgency: medium Maintainer: Anton Zinoviev Changed-By: наб Closes: 1030816 1063760 1063834 1086862 Changes: console-cyrillic (0.9-18) unstable; urgency=medium . [ наб ] * Standards-Version: 4.7.0 (routine-update) * Rules-Requires-Root: binary-targets (+ modernise root handling in d/rules) * d/rules: drop checkdir macro * List the files from debian/binary.tar.gz.uu in d/source/include-binaries and unpack permanently instead of unpacking/repacking each time (=> drop Build-Depends: sharutils) * d/rules: dpkg-gencontrol: warning: -isp is deprecated; it is without effect * debian/makeenc: mark executable, execute directly * d/rules: streamline installation * dumppsf: fix dumping mode 1 and mode 3 fonts (Closes: #1063760) * Remove d/conf*, d/init.d, d/po*, d/templates, d/postinst: not installed since 0.9-17 (=> Build-Depends-Indep: drop po-debconf) * d/control: drop versioned dependency on trscripts (>
Bug#670285: marked as done (libjrosetta-java: debcheckout fails)
Your message dated Sat, 09 Nov 2024 19:04:56 + with message-id and subject line Bug#670285: fixed in libjrosetta-java 1.0.4-5 has caused the Debian Bug report #670285, regarding libjrosetta-java: debcheckout fails 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.) -- 670285: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=670285 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libjrosetta-java Version: 1.0.4-4 Severity: minor Please drop "+ssh" protocol from debian/control::Vcs-* to make debcheckout work for everybody. --- End Message --- --- Begin Message --- Source: libjrosetta-java Source-Version: 1.0.4-5 Done: Andreas Tille We believe that the bug you reported is fixed in the latest version of libjrosetta-java, 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 670...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Tille (supplier of updated libjrosetta-java 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: Sat, 09 Nov 2024 19:27:03 +0100 Source: libjrosetta-java Architecture: source Version: 1.0.4-5 Distribution: unstable Urgency: medium Maintainer: Debian Java Maintainers Changed-By: Andreas Tille Closes: 670285 Changes: libjrosetta-java (1.0.4-5) unstable; urgency=medium . [ Miguel Landaeta ] * Use public access URL in Vcs-Svn field. (Closes: #670285). . [ tony mancill ] * Moved the package to Git * Use debhelper 10 * Bump Standards-Version to 3.9.8 * Add myself to Uploaders . [ Andreas Tille ] * Point Vcs fields to Salsa * Standards-Version: 4.7.0 (routine-update) * debhelper-compat 13 (routine-update) * Drop useless get-orig-source target (routine-update) * Remove trailing whitespace in debian/changelog (routine-update) * Remove trailing whitespace in debian/control (routine-update) * Remove trailing whitespace in debian/copyright (routine-update) * Rules-Requires-Root: no (routine-update) * Trim trailing whitespace. * watch file standard 4 (routine-update) * Switch from cdbs to dh Checksums-Sha1: 915c302565fbd4bf8228114e13a9ba96f981f32d 2169 libjrosetta-java_1.0.4-5.dsc 00010f3233f9822fce8254c6f9942894f7cc6e12 5028 libjrosetta-java_1.0.4-5.debian.tar.xz 2c319bfed07dc0114f52cd64eec1939de93d870f 14543 libjrosetta-java_1.0.4-5_amd64.buildinfo Checksums-Sha256: a08f46d4d9c6c5c0331cbb154383f6473257b7e685638d8c3d1b10142851d7e6 2169 libjrosetta-java_1.0.4-5.dsc b7ee6521a381897aced372f23d00f51836c63b6dd10437518b92d285269dd3c9 5028 libjrosetta-java_1.0.4-5.debian.tar.xz e94f13487d0ba7c51cf2ad8fbe948a3aa2b50e4b34b48a849769fcfddf65130d 14543 libjrosetta-java_1.0.4-5_amd64.buildinfo Files: f9689c4cf32c31efe48017354902dcec 2169 java optional libjrosetta-java_1.0.4-5.dsc e8e2bceddd2ca81e910b21a1f867c1e8 5028 java optional libjrosetta-java_1.0.4-5.debian.tar.xz 30bfb66dd4bfaff4ce4d7ffec42f71b6 14543 java optional libjrosetta-java_1.0.4-5_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJFBAEBCgAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAmcvr7QRHHRpbGxlQGRl Ymlhbi5vcmcACgkQV4oElNHGRtE0rQ/+MFAiUYGIztJ530ADjLYrjevNQVhpgcT8 WnOH9jwwDOER7QZjaenvr2DjEZ652GCP7zYwZZ7e2g/u8aASXLaUFT0tzksQb+kA redKG1Lh8dRFTMYmdRAiL9tsnfEj3IrswEVjBhsh7CKugW6hViA8N85IdcZFHlhQ /O/FLjy1NdBZpuKEe4VWDlYsq5TWvdsjf7RYQ7Lx/x+uq2Piu1UJL+tdFVePOLLU DrUrCPE+haGAzFIkFk/xwVqb3jgjgwyvXFua1ki/sNyiBv24qEAL+z0Pb7gGyHEY 6oRLVe0N5CbYY1Ih5jiHgxjWf3lQu8NZnBk+81D5+V78QZwrv3MiRigTy83q2Ym1 S83vCqBKmprosctI7yNE7ru7GK5Pf4WxQOI/XuO5bWzD79sNnt6JfIySxPbZMkkm vS3ravLG1X5Q1J0Ol72JhSfNlEyoPEZb1R/IHnG0V7kzTme6NisVfzolAIws1Rc7 9yIoXv6PQ6H8xcGSGQg+/1WZnF3GTXt9gHLbv6gdjupJ7X30ldrnKL1g0ZShPDWS s0ldC1fYvg9KbfoCfjw0nlD1E3MgoGeMHFzSakkM4uohVf6GxeER8G1UPrUu1P8K 08ii/+XNax4JOZixPBk6YbM0fzgoK/HbWcsMmTbEDgvIF734ZTIby4fodkgld0Qb LVUJflvere4= =ynUJ -END PGP SIGNATURE- pgpt8tds0VOf7.pgp Description: PGP signature --- End Message ---
Bug#1086804: marked as done (curl: CVE-2024-9681)
Your message dated Sat, 09 Nov 2024 18:50:05 + with message-id and subject line Bug#1086804: fixed in curl 8.11.0-1 has caused the Debian Bug report #1086804, regarding curl: CVE-2024-9681 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.) -- 1086804: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1086804 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: curl Version: 8.10.1-2 Severity: important Tags: security upstream X-Debbugs-Cc: car...@debian.org, Debian Security Team Control: found -1 7.88.1-10+deb12u8 Control: found -1 7.88.1-10 Hi, The following vulnerability was published for curl. CVE-2024-9681[0]: | When curl is asked to use HSTS, the expiry time for a subdomain | might overwrite a parent domain's cache entry, making it end sooner | or later than otherwise intended. This affects curl using | applications that enable HSTS and use URLs with the insecure | `HTTP://` scheme and perform transfers with hosts like | `x.example.com` as well as `example.com` where the first host is a | subdomain of the second host. (The HSTS cache either needs to have | been populated manually or there needs to have been previous HTTPS | accesses done as the cache needs to have entries for the domains | involved to trigger this problem.) When `x.example.com` responds | with `Strict-Transport-Security:` headers, this bug can make the | subdomain's expiry timeout *bleed over* and get set for the parent | domain `example.com` in curl's HSTS cache. The result of a | triggered bug is that HTTP accesses to `example.com` get converted | to HTTPS for a different period of time than what was asked for by | the origin server. If `example.com` for example stops supporting | HTTPS at its expiry time, curl might then fail to access | `http://example.com` until the (wrongly set) timeout expires. This | bug can also expire the parent's entry *earlier*, thus making curl | inadvertently switch back to insecure HTTP earlier than otherwise | intended. If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2024-9681 https://www.cve.org/CVERecord?id=CVE-2024-9681 [1] https://curl.se/docs/CVE-2024-9681.html Regards, Salvatore --- End Message --- --- Begin Message --- Source: curl Source-Version: 8.11.0-1 Done: Samuel Henrique We believe that the bug you reported is fixed in the latest version of curl, 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 1086...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Samuel Henrique (supplier of updated curl 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: Sat, 09 Nov 2024 17:34:22 + Source: curl Architecture: source Version: 8.11.0-1 Distribution: unstable Urgency: medium Maintainer: Debian Curl Maintainers Changed-By: Samuel Henrique Closes: 1086804 Changes: curl (8.11.0-1) unstable; urgency=medium . [ Samuel Henrique ] * New upstream version 8.11.0 * Fix CVE-2024-9681: HSTS subdomain overwrites parent cache entry (closes: #1086804) * Update patches for the new release * d/rules: Drop '--enable-websockets', it's enabled by default now * d/libcurl*.symbols: Remove HIDDEN@HIDDEN 7.16.2 * Add 5 upstream patches to fix regressions: - cmdline_ech_md_formatting_cleanups.patch - duphandle_also_init_netrc.patch - libssh_when_using_IPv6_numerical_address_add_brackets.patch - netrc_support_large_file_longer_lines_longer_tokens.patch - setopt_fix_CURLOPT_HTTP_CONTENT_DECODING.patch . [ Carlos Henrique Lima Melara ] * d/rules: add sed rule to make curl-config get CPPFLAGS in run-time * d/control: move libldap2-dev to Depends and use newer libldap-dev name * d/control: move libkrb5-dev from Suggests to Depends for -dev packages Checksums-Sha1: cef155a118c4b3600d6b44c105cff3a38753e06e 3252 curl_8.11.0-1.dsc 9648c31756362343f1a0daba881e189d6fe8b4f4 4167839 curl_8.11.0.orig.tar.gz f4280d937e832fbd7
Bug#1085709: marked as done (jwm: New upstream version 2.4.5)
Your message dated Sat, 09 Nov 2024 18:50:16 + with message-id and subject line Bug#1085709: fixed in jwm 2.4.6-1 has caused the Debian Bug report #1085709, regarding jwm: New upstream version 2.4.5 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1085709: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1085709 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: jwm Version: 2.4.3-1 Severity: wishlist X-Debbugs-Cc: a.t.chadw...@gmail.com Dear Maintainer, There is a new upstream version out: https://github.com/joewing/jwm/releases/tag/v2.4.5 Please can you consider updating the Debian package? many thanks, Andrew --- End Message --- --- Begin Message --- Source: jwm Source-Version: 2.4.6-1 Done: Samuel Henrique We believe that the bug you reported is fixed in the latest version of jwm, 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 1085...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Samuel Henrique (supplier of updated jwm 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: Sat, 09 Nov 2024 18:26:44 + Source: jwm Architecture: source Version: 2.4.6-1 Distribution: unstable Urgency: medium Maintainer: Samuel Henrique Changed-By: Samuel Henrique Closes: 1033491 1085709 Changes: jwm (2.4.6-1) unstable; urgency=medium . * New upstream version 2.4.6 (closes: #1085709) * d/p/01-example-jwmrc: s/xterm/x-terminal-emulator (closes: #1033491) Checksums-Sha1: bf3a69c5b0ab3c9f947e87d1896dddb684b0341d 1956 jwm_2.4.6-1.dsc 9872ba5ba462b17464000ddff46090c7a3140f01 253235 jwm_2.4.6.orig.tar.gz 077069fa16f97d664f702e68fcac0990ac87efd2 13484 jwm_2.4.6-1.debian.tar.xz b33f5eb40cd8a5ff7bba191a9fd5a593df0c68fb 11444 jwm_2.4.6-1_amd64.buildinfo Checksums-Sha256: 889917f2f9b4e6145a3a5e7fc8964eea9e59a808bbbea7bcf51cf7e7677d0ddc 1956 jwm_2.4.6-1.dsc adfdfc6c866852e970145ace58d6adbe3e4722c9413a90b22f8560620391ac7a 253235 jwm_2.4.6.orig.tar.gz dd36f730a8da875508bd20c323820da79d5ecc18bb1bea01ce5ac71ef0621076 13484 jwm_2.4.6-1.debian.tar.xz 10fd576d406debcf2fa9a7c385174cbb586bb97713e6bc00fc6fdd351da3d6ff 11444 jwm_2.4.6-1_amd64.buildinfo Files: 8a1475a9474f2f4052a81aed4661698c 1956 x11 optional jwm_2.4.6-1.dsc 7ff2301fd5c4c1e2483bac8079ae9ccb 253235 x11 optional jwm_2.4.6.orig.tar.gz 671cbd67723f9417c1f4795406be8966 13484 x11 optional jwm_2.4.6-1.debian.tar.xz 4b0ace09c2923a5b7f8e5f432c1c1f51 11444 x11 optional jwm_2.4.6-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEv66eMxqGenyA2Ot49OSs27jQi+AFAmcvqm4ACgkQ9OSs27jQ i+D/Wg//ZCa8K6iw99+rDAQ1ZiOcD8AjJrVhtFzJ5DMma2RtTwpodITezH92CuOV skkw56QAJK3G0TsTBu+ByOygHDs0/jlOIi9zmQ4LEqJPa+llTEhHNLkpNhgkXG/9 dwQIY00yMIFapIxd+5LvQIO2ovj+/31CPS4lkfrN0mQeAZF43AsdQrAvKZYO5yXw pJbroO4Oj8dxSllEd9BCceeEBfLN9oGHYorXLTVWK2+fLBCvpXkDvQiex0NcEJWE cke969mai7adlwYYBfyCbDLXB91R4sMWaxvcwGUSV3BVxp7tE/BP4Mss1arAhziC YWNTH9F4oCiuCyBnIzvGFdbCLbiU1o19yFJ9xmS9WPTB2IDrXqksrot3vCBiOn9x 6IfVzzBsUqEsRZpOS+oqaiW3ffAqi6V8tFQDXdvBtv9+xs/9mjcB8tVjA7CkpCjj KjuOHPpOxXrUsvUNeceMSGNbJFs8bLAc8wMWqtDLJxekSCkigaomqXTHlPh6ouFO Jwa3NsK1/M6MwzQD2TtTiAmctaYOI7CLMq5LLfZRpwWM+zKpJ2bq5xMWw1Q3qGf6 mDmTX+B9uGKMKhfOmjm5IjmnxVtpcp2s8w47o0sAkM0JcZmb7i+4dTh2pPGycfLH SQXeaNOe+0QhgFimDVM2XrtKmf9N0THsurIEJBo/30CCsTvtwc8= =Zjk6 -END PGP SIGNATURE- pgpaYsFRHJyt3.pgp Description: PGP signature --- End Message ---
Bug#1033491: marked as done (jwm: please replace xterm to x-terminal-emulator in system.jwmrc file)
Your message dated Sat, 09 Nov 2024 18:50:16 + with message-id and subject line Bug#1033491: fixed in jwm 2.4.6-1 has caused the Debian Bug report #1033491, regarding jwm: please replace xterm to x-terminal-emulator in system.jwmrc file 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.) -- 1033491: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033491 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: jwm Version: 2.4.3-1 Severity: minor X-Debbugs-Cc: thom1...@gmail.com Dear Maintainer, Please replace xterm to x-terminal-emulator in system.jwmrc file in some rare cases (for example if jwm installed before xorg) we have rxvt-unicode instead xterm See patch in attachments Thanks -- System Information: Debian Release: 12.0 APT prefers testing-security APT policy: (500, 'testing-security'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-6-amd64 (SMP w/1 CPU thread; PREEMPT) Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages jwm depends on: ii libc6 2.36-8 ii libcairo2 1.16.0-7 ii libglib2.0-02.74.6-1 ii libjpeg62-turbo 1:2.1.5-2 ii libpango-1.0-0 1.50.12+ds-1 ii libpangoft2-1.0-0 1.50.12+ds-1 ii libpangoxft-1.0-0 1.50.12+ds-1 ii libpng16-16 1.6.39-2 ii librsvg2-2 2.54.5+dfsg-1 ii libx11-62:1.8.4-2 ii libxext62:1.3.4-1+b1 ii libxft2 2.3.6-1 ii libxinerama12:1.1.4-3 ii libxmu6 2:1.1.3-3 ii libxpm4 1:3.5.12-1.1 ii libxrender1 1:0.9.10-1.1 ii rxvt-unicode [x-terminal-emulator] 9.30-2+b4 Versions of packages jwm recommends: pn menu Versions of packages jwm suggests: pn x11-apps -- Configuration Files: /etc/jwm/system.jwmrc changed [not included] -- no debconf information --- system.jwmrc2023-03-26 13:10:30.618632210 +1000 +++ system.jwmrc.edited 2023-03-26 13:11:45.975428038 +1000 @@ -4,7 +4,7 @@ /etc/jwm/debian-menu -xterm +x-terminal-emulator xscreensaver-command -lock --- End Message --- --- Begin Message --- Source: jwm Source-Version: 2.4.6-1 Done: Samuel Henrique We believe that the bug you reported is fixed in the latest version of jwm, 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 1033...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Samuel Henrique (supplier of updated jwm 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: Sat, 09 Nov 2024 18:26:44 + Source: jwm Architecture: source Version: 2.4.6-1 Distribution: unstable Urgency: medium Maintainer: Samuel Henrique Changed-By: Samuel Henrique Closes: 1033491 1085709 Changes: jwm (2.4.6-1) unstable; urgency=medium . * New upstream version 2.4.6 (closes: #1085709) * d/p/01-example-jwmrc: s/xterm/x-terminal-emulator (closes: #1033491) Checksums-Sha1: bf3a69c5b0ab3c9f947e87d1896dddb684b0341d 1956 jwm_2.4.6-1.dsc 9872ba5ba462b17464000ddff46090c7a3140f01 253235 jwm_2.4.6.orig.tar.gz 077069fa16f97d664f702e68fcac0990ac87efd2 13484 jwm_2.4.6-1.debian.tar.xz b33f5eb40cd8a5ff7bba191a9fd5a593df0c68fb 11444 jwm_2.4.6-1_amd64.buildinfo Checksums-Sha256: 889917f2f9b4e6145a3a5e7fc8964eea9e59a808bbbea7bcf51cf7e7677d0ddc 1956 jwm_2.4.6-1.dsc adfdfc6c866852e970145ace58d6adbe3e4722c9413a90b22f8560620391ac7a 253235 jwm_2.4.6.orig.tar.gz dd36f730a8da875508bd20c323820da79d5ecc18bb1bea01ce5ac71ef0621076 13484 jwm_2.4.6-1.debian.tar.xz 10fd576d406debcf2fa9a7c385174cbb586bb97713e6bc00fc6fdd351da3d6ff 11444 jwm_2.4.6-1_amd64.buildinfo Files: 8a1475a9474f2f4052a81aed4661698c 1956 x11 optional jwm_2.4.6-1.dsc 7ff2301fd5c4c1e2483bac8
Bug#1086914: marked as done (relion: depends on openmpi on 32-bit architectures)
Your message dated Sat, 09 Nov 2024 18:34:31 + with message-id and subject line Bug#1086914: fixed in relion 3.1.3-4 has caused the Debian Bug report #1086914, regarding relion: depends on openmpi on 32-bit architectures 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.) -- 1086914: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1086914 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: relion Severity: serious Hi, relion depends on openmpi on 32-bit architectures, which has been removed in openmpi 5. Thus this package needs to stop depending on it on those architectures. There are a couple of options: - build-dep on mpi-default-dev instead of openmpi-dev, so that the MPICH implementation can be used on those architectures. - remove the package from 32-bit architectures (armel, armhf and i386) by filing an RM bug against ftp.debian.org See [1] for the transition bug and [2] for the tracker. Cheers, Emilio [1] https://bugs.debian.org/1064810 [2] https://release.debian.org/transitions/html/openmpi-rm32.html --- End Message --- --- Begin Message --- Source: relion Source-Version: 3.1.3-4 Done: Étienne Mollier We believe that the bug you reported is fixed in the latest version of relion, 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 1086...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Étienne Mollier (supplier of updated relion 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: Sat, 09 Nov 2024 18:14:58 +0100 Source: relion Architecture: source Version: 3.1.3-4 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team Changed-By: Étienne Mollier Closes: 1086914 Changes: relion (3.1.3-4) unstable; urgency=medium . * Team upload. * d/control: migrate to mpi-default-*. (Closes: #1086914) * d/control: declare compliance to standards version 4.7.0. Checksums-Sha1: 5848cff6675f4d383e5e9566eaf8a0d8b2b5a06f 2141 relion_3.1.3-4.dsc cbd977bd73a6270bab2fc9aca5779296c528315b 12056 relion_3.1.3-4.debian.tar.xz e4bd97578f22da108e5ead56c9b2ebc883bb31ac 12248 relion_3.1.3-4_amd64.buildinfo Checksums-Sha256: 3dc9b108411961cf1540f8f556dc25292a24a273e3194aaee6319512a968c152 2141 relion_3.1.3-4.dsc 5dfd505bf26bb03602300ad0b21ed1e6459f97491725abdb5dfa79427972a46a 12056 relion_3.1.3-4.debian.tar.xz 28f4dc6fc49ee3daea2bb7e5c278654635304bd45fab949110a566ab6655ed4a 12248 relion_3.1.3-4_amd64.buildinfo Files: 78e3e1648f5e5aecccbc1784651e966b 2141 science optional relion_3.1.3-4.dsc d7e1621d2cf43aa84fc9c84f31ece31b 12056 science optional relion_3.1.3-4.debian.tar.xz 86ce057a9a34a3bf4127fef3f16d3e7b 12248 science optional relion_3.1.3-4_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJIBAEBCgAyFiEEj5GyJ8fW8rGUjII2eTz2fo8NEdoFAmcvqOQUHGVtb2xsaWVy QGRlYmlhbi5vcmcACgkQeTz2fo8NEdrl8g//dutKra5AT1IwB//MlGRiVtjTRHZq kelL2Dd5ZfXTSZYRX7R6RdSFW/YdWV3khdjQBdH9ARg2tD7zGyoxg8Hsp3c5htyN YwMrC26XJ0oAkJMJA1uvyYIpKcook64zKBFbyKJRLtMoaBdQCmYusrelCwSo3Zuw OBzrZnEAOKa/9urFw8SWJIuapUU4R3mao4k/j1Al/6T5HRn+4auGG6HXIcs8o4gD Mjm/TmftIiLYanGpmqxEar3mxSE6zBlV8Uih0b3OdQq+paE3VECIbHukArzemKLY bRVvH3ruIZNDzqrufdaY3jM2zbAx1bbm+V7bmYXExyLREsR7Q/c1XpStZD0W35uR ZWn8ZjvwVJFCZZM43jEmOtTfNdebzNliLnW5tBdfjs0JIRgGQ3u1YKVOei8WLa1T i+uZd30wWzdkcoFrxCUYYD6YOrEyX7xtNswb/ZTCNH1Sj8LxYx6WlWUA5x6Wnhuj MOyPfGU41M7tiTblh9bhkqTsKjb11HTKyuORjDeJThzjY6E8WYodZgPkEGtZPhcL qCbv+/7ttVf9AyQWwJJ4tA92okeqRJ1TLVn5XAZ440EnZaNA9FEo/Dhv3gChXDhf Gy75FVflavQrjh6OLE+AHhXijDelfZsU/hBuXkyxYOtmyxreQDoEHDUFmiRHxjWn fUPD44H5lQ9News= =Ilm7 -END PGP SIGNATURE- pgptiQw1jeAGp.pgp Description: PGP signature --- End Message ---
Bug#1086907: marked as done (tree-puzzle: depends on openmpi on 32-bit architectures)
Your message dated Sat, 09 Nov 2024 18:34:50 + with message-id and subject line Bug#1086907: fixed in tree-puzzle 5.3~rc16+dfsg-12 has caused the Debian Bug report #1086907, regarding tree-puzzle: depends on openmpi on 32-bit architectures 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.) -- 1086907: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1086907 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: tree-puzzle Severity: serious Hi, tree-puzzle depends on openmpi on 32-bit architectures, which has been removed in openmpi 5. Thus this package needs to stop depending on it on those architectures. There are a couple of options: - build-dep on mpi-default-dev instead of openmpi-dev, so that the MPICH implementation can be used on those architectures. - remove the package from 32-bit architectures (armel, armhf and i386) by filing an RM bug against ftp.debian.org See [1] for the transition bug and [2] for the tracker. Cheers, Emilio [1] https://bugs.debian.org/1064810 [2] https://release.debian.org/transitions/html/openmpi-rm32.html --- End Message --- --- Begin Message --- Source: tree-puzzle Source-Version: 5.3~rc16+dfsg-12 Done: Étienne Mollier We believe that the bug you reported is fixed in the latest version of tree-puzzle, 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 1086...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Étienne Mollier (supplier of updated tree-puzzle 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: Sat, 09 Nov 2024 18:44:04 +0100 Source: tree-puzzle Architecture: source Version: 5.3~rc16+dfsg-12 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team Changed-By: Étienne Mollier Closes: 1086907 Changes: tree-puzzle (5.3~rc16+dfsg-12) unstable; urgency=medium . * Team upload. * preserve-artifacts.patch: new: restore some test artifacts. This is necessary to bring autopkgtest support back into working conditions. * d/control: migrate to mpi-default-*. (Closes: #1086907) * d/patches/*: normalize Last-Update timestamp. * Patch fix-conftest.c renamed fix-conftest.patch. This unconfuses syntax highlighting, and file name. Checksums-Sha1: 77860810033a0149c41c385acd62e4a3da2f40ba 2366 tree-puzzle_5.3~rc16+dfsg-12.dsc c2ae52334454ad1a0a775820e7adbee9f6dc4dd4 32388 tree-puzzle_5.3~rc16+dfsg-12.debian.tar.xz Checksums-Sha256: 5040a5dcdc0d7af8c6cc65c6408d5562d146ca3e82f535e8571df0f0c4e777e8 2366 tree-puzzle_5.3~rc16+dfsg-12.dsc ffdf47fd85b5cb8a6cbdc0f4aea286107c6d3d5d9054ea9670f6a8efe2055c09 32388 tree-puzzle_5.3~rc16+dfsg-12.debian.tar.xz Files: 8f794b518130f33801a0442b61ce994b 2366 science optional tree-puzzle_5.3~rc16+dfsg-12.dsc df136ca2e1a9937bd6f7a51cf4d90a28 32388 science optional tree-puzzle_5.3~rc16+dfsg-12.debian.tar.xz -BEGIN PGP SIGNATURE- iQJIBAEBCgAyFiEEj5GyJ8fW8rGUjII2eTz2fo8NEdoFAmcvo4kUHGVtb2xsaWVy QGRlYmlhbi5vcmcACgkQeTz2fo8NEdr7kxAAoGz+53mp6G9tBTLd4pI/d5gz2iZN YfFCBeNstF05MYCzMB4eWfOd6zh4j40YLborOiWJ3Rq+tYhd5XA3tmODVbB2NLFU jpAcd0QWg4+MYmET2dc8oUQHoRrbIAl3Hfo1WPb/syhXLKLi7mpEQETJDLQe1lLD FoEJeozyTtwGkjO7gklzuEKjhoaJaBHHKy1CHoWonvm0RZTbyDxIP1qm19/Kmj9w LH4dnU0U/OdL7SvpI6OHZizht56G3KtD0ie6Vhho52JoEfOk+jFd8wry5jVur5/d qB3q3LADFdKEznE02f1TBkF0UFOLpjAlGCuSN2zBYC5YSiV9Rm3EYGE3gF+ZpKPM 5+wmlUxLT2WtNJ6Dw/4f0qVh33g0sRvmwFLsVHiUp7xQDjRxNytqrYO3p7R4ilUa TgpRhn4JiArm3/fDdfLaVY3pdzbzUy9CRPwhjOxPOyikqu7akGksO3GaaSZFa4l4 aBZ6apU0PB3slpsWTT+ooJBaF0wwjKhW+rnUn4D+5l7MmUtCWn+mneQA2m/ODBy5 6xrnbB53H7FNEIGhC+4+uRPAZVLMhtIcAiGcVp/4/PxY0WoHCWuf4xfTRVTDp7iX LMH3cOvsO7r+z3u26lqHqY1q/6ik859idYuvrBTTkdSqT3+VaUuCfCfL9Y3sGN7d /lAlfbrzlUeIMUY= =Mf0l -END PGP SIGNATURE- pgpNVCGNBToDB.pgp Description: PGP signature --- End Message ---
Bug#812941: marked as done (apcupsd: process goes into uninterruptable sleep)
Your message dated Sat, 9 Nov 2024 18:25:36 + (UTC) with message-id and subject line Re: apcupsd: process goes into uninterruptable sleep has caused the Debian Bug report #812941, regarding apcupsd: process goes into uninterruptable sleep 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.) -- 812941: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812941 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: apcupsd Version: 3.14.12-1.1 Severity: important Dear Maintainer, I find the apcupsd process goes into uninterruptable sleep causing erroneous 1.00+ load average. I haven't verified if the system would shutdown if a battery event were to occur. Rebooting the host doesn't resolve the issue, it returns to uninterruptable sleep. Unplugging the UPS USB cable resolves the issue for a few days but eventually lands back in uninterruptable sleep. -- System Information: Debian Release: 8.3 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=ANSI_X3.4-1968) (ignored: LC_ALL set to C) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages apcupsd depends on: ii libc6 2.19-18+deb8u2 ii libgcc1 1:4.9.2-10 ii libwrap0 7.6.q-25 Versions of packages apcupsd recommends: ii apcupsd-doc 3.14.12-1.1 Versions of packages apcupsd suggests: pn apcupsd-cgi ii udev 215-17+deb8u3 -- Configuration Files: /etc/apcupsd/apcupsd.conf changed: UPSCABLE smart UPSTYPE usb DEVICE LOCKFILE /var/lock SCRIPTDIR /etc/apcupsd PWRFAILDIR /etc/apcupsd NOLOGINDIR /etc ONBATTERYDELAY 6 BATTERYLEVEL 5 MINUTES 5 TIMEOUT 0 ANNOY 300 ANNOYDELAY 60 NOLOGON disable KILLDELAY 0 NETSERVER on NISIP 127.0.0.1 NISPORT 3551 EVENTSFILE /var/log/apcupsd.events EVENTSFILEMAX 10 UPSCLASS standalone UPSMODE disable STATTIME 0 STATFILE /var/log/apcupsd.status LOGSTATS off DATATIME 0 /etc/default/apcupsd changed: APCACCESS=/sbin/apcaccess ISCONFIGURED=yes -- no debconf information --- End Message --- --- Begin Message --- Package: apcupsd Version: 3.14.12-1.2 As there has been no reaction, I assume the bug was resolved meanwhile. Thorsten--- End Message ---
Bug#1087075: marked as done (scolasync: Python SyntaxWarning)
Your message dated Sat, 09 Nov 2024 18:15:22 +
with message-id
and subject line Bug#1087075: fixed in scolasync 5.6-1
has caused the Debian Bug report #1087075,
regarding scolasync: Python SyntaxWarning
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.)
--
1087075: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1087075
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: scolasync
Version: 5.5-1
User: debian-pyt...@lists.debian.org
Usertags: syntaxwarning
Hi Maintainer
The SyntaxWarning below were emitted when this package was tested with
pipuarts[1].
Regards
Graham
[1] https://piuparts.debian.org/sid/source/s/scolasync.html
Setting up python3 (3.12.6-1) ...
/usr/share/scolasync/mainWindow.py:392: SyntaxWarning: invalid
escape sequence '\S'
m = re.match("(\S+)\s+(\S+)\s+(\S+)\s+(\S+)\s+(\S+)\s+(\S+).*",
dfOutput).groups()
/usr/share/scolasync/test3.py:9: SyntaxWarning: invalid escape sequence '\.'
pattern=re.compile(".*\.py$")
--- End Message ---
--- Begin Message ---
Source: scolasync
Source-Version: 5.6-1
Done: Georges Khaznadar
We believe that the bug you reported is fixed in the latest version of
scolasync, 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 1087...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Georges Khaznadar (supplier of updated scolasync package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Sat, 09 Nov 2024 16:38:44 +0100
Source: scolasync
Architecture: source
Version: 5.6-1
Distribution: unstable
Urgency: medium
Maintainer: Georges Khaznadar
Changed-By: Georges Khaznadar
Closes: 1087075
Changes:
scolasync (5.6-1) unstable; urgency=medium
.
* new upstream version: fixed bad escaped characters. Closes: #1087075
Checksums-Sha1:
7fe146c473a6d73256ea23533f2bfeb61a2fe69d 2048 scolasync_5.6-1.dsc
066bbe028b9afe01a3236765b2e90d02358d4fa8 3868684 scolasync_5.6.orig.tar.xz
73d84d1037adef69c177147909dff30d5250933e 7448 scolasync_5.6-1.debian.tar.xz
ccb59ebd9bd5fb1d8756f1812916ebdfadc30562 14827 scolasync_5.6-1_source.buildinfo
Checksums-Sha256:
8626697a68633398096de90f679f34f502dff4165983dac0cfc240c94b706000 2048
scolasync_5.6-1.dsc
764052d1a862f2d523b14d6524f99032ac6a4e412c5dadcab765f2e33e975751 3868684
scolasync_5.6.orig.tar.xz
8470ed9a990e233009a19bd6ede53b266952bb9932b714674f2ab0d7d23bae03 7448
scolasync_5.6-1.debian.tar.xz
c220bb19b574a26af8425e2e580f8253535398275ec72ccdba00c4cac1d8 14827
scolasync_5.6-1_source.buildinfo
Files:
305c306e56314475d9da18e4294385b7 2048 x11 optional scolasync_5.6-1.dsc
1bc9a9d84a085b179af7dc1b378f7972 3868684 x11 optional scolasync_5.6.orig.tar.xz
033af8c063f169860e19888a8363eb25 7448 x11 optional
scolasync_5.6-1.debian.tar.xz
e12a5bf56319973b258bf57c366a75cb 14827 x11 optional
scolasync_5.6-1_source.buildinfo
-BEGIN PGP SIGNATURE-
iQJIBAEBCAAyFiEEM0CzZP9nFT+3zK6FHCgWkHE2rjkFAmcvjlEUHGdlb3JnZXNr
QGRlYmlhbi5vcmcACgkQHCgWkHE2rjmwQw//bPJiBpUgMrUM0ocXXWuAZLYHWeJk
83SvJCfEJIEYYbc5N97+N/xFCBV7O58XQaCbJzNDK5g+26KXi4fFob1ZavcWcIez
yZhOoomyxdpvTcPthe1aIHyOZ/SbBWjtgC3xkFc3YPFCYEC3xM3OISE7qfZ1ESkH
XVilQSECe2195FHS3PDIjNB3gbj6gSbeQDWBctqZTEYyt6HVNXIf+QHWpqS5K4h4
/AwZnRyMAcD/TO/hu/X8toesEiff6an5672Czj3ezxqguIpkSKyGz90IrC8d7rsp
wDiv6PEGOrl4zHwGWRJZyMBjL+hMllKJE2LEULdf6hlP1vU6LECd9i/lUNit+CpU
x263nlwxZ3nwfgxcI2EYjl37VUCbnyo//mxTfN9nYAdWw8pEG5uz3Fk4Md3MscMG
L/7k+YrktX4xEHDi/QD9C9O54B4hpk+Ug+CMwVwl2m6I72Ior2ImcVoBk9V477k1
iOvmjn5+EbkDC36MJqCI0+cF/Nxqi6pVXxRDoG3ULA42OKPFlsusjEBZMcSo
wNG2WEjRncOluAbbujO6Ot6S2LbwuR6R5crrAsqXcIxisVH8a4em1l9yl7c2d5hu
sCnJzQQ1G/skOsQXAFIS1pR7g3IrKGICwqQCWUOx3UoSGV26lDjwldOxhObGQt6z
ZDwbsihmVp/3Krk=
=dFq/
-END PGP SIGNATURE-
pgpPqBZ5nlwZN.pgp
Description: PGP signature
--- End Message ---
Bug#1084256: marked as done (flask-restful: FTBFS: failing tests)
Your message dated Sat, 09 Nov 2024 17:39:16 + with message-id and subject line Bug#1084256: fixed in flask-restful 0.3.10-3 has caused the Debian Bug report #1084256, regarding flask-restful: FTBFS: failing 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.) -- 1084256: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1084256 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:flask-restful Version: 0.3.10-2 Severity: serious Tags: ftbfs Dear maintainer: During a rebuild of all packages in unstable, your package failed to build: [...] debian/rules binary dh binary --buildsystem=pybuild --with=python3,sphinxdoc dh_update_autotools_config -O--buildsystem=pybuild dh_autoreconf -O--buildsystem=pybuild dh_auto_configure -O--buildsystem=pybuild I: pybuild base:311: python3.12 setup.py config /usr/lib/python3/dist-packages/setuptools/_distutils/dist.py:261: UserWarning: Unknown distribution option: 'test_suite' warnings.warn(msg) /usr/lib/python3/dist-packages/setuptools/_distutils/dist.py:261: UserWarning: Unknown distribution option: 'tests_require' warnings.warn(msg) running config debian/rules override_dh_auto_build make[1]: Entering directory '/<>' dh_auto_build I: pybuild base:311: /usr/bin/python3 setup.py build /usr/lib/python3/dist-packages/setuptools/_distutils/dist.py:261: UserWarning: Unknown distribution option: 'test_suite' warnings.warn(msg) /usr/lib/python3/dist-packages/setuptools/_distutils/dist.py:261: UserWarning: Unknown distribution option: 'tests_require' warnings.warn(msg) running build running build_py creating /<>/.pybuild/cpython3_3.12_flask-restful/build/flask_restful copying flask_restful/inputs.py -> /<>/.pybuild/cpython3_3.12_flask-restful/build/flask_restful copying flask_restful/reqparse.py -> /<>/.pybuild/cpython3_3.12_flask-restful/build/flask_restful copying flask_restful/__init__.py -> /<>/.pybuild/cpython3_3.12_flask-restful/build/flask_restful copying flask_restful/fields.py -> /<>/.pybuild/cpython3_3.12_flask-restful/build/flask_restful copying flask_restful/__version__.py -> /<>/.pybuild/cpython3_3.12_flask-restful/build/flask_restful creating /<>/.pybuild/cpython3_3.12_flask-restful/build/flask_restful/utils copying flask_restful/utils/crypto.py -> /<>/.pybuild/cpython3_3.12_flask-restful/build/flask_restful/utils copying flask_restful/utils/cors.py -> /<>/.pybuild/cpython3_3.12_flask-restful/build/flask_restful/utils copying flask_restful/utils/__init__.py -> /<>/.pybuild/cpython3_3.12_flask-restful/build/flask_restful/utils creating /<>/.pybuild/cpython3_3.12_flask-restful/build/flask_restful/representations copying flask_restful/representations/__init__.py -> /<>/.pybuild/cpython3_3.12_flask-restful/build/flask_restful/representations copying flask_restful/representations/json.py -> /<>/.pybuild/cpython3_3.12_flask-restful/build/flask_restful/representations running egg_info creating Flask_RESTful.egg-info writing Flask_RESTful.egg-info/PKG-INFO writing dependency_links to Flask_RESTful.egg-info/dependency_links.txt writing requirements to Flask_RESTful.egg-info/requires.txt writing top-level names to Flask_RESTful.egg-info/top_level.txt writing manifest file 'Flask_RESTful.egg-info/SOURCES.txt' reading manifest file 'Flask_RESTful.egg-info/SOURCES.txt' reading manifest template 'MANIFEST.in' warning: no files found matching 'CHANGES' warning: no previously-included files matching '*.pyc' found under directory 'docs' warning: no previously-included files matching '*.pyo' found under directory 'docs' warning: no previously-included files matching '*.pyc' found under directory 'tests' warning: no previously-included files matching '*.pyo' found under directory 'tests' warning: no previously-included files matching '*.pyc' found under directory 'examples' warning: no previously-included files matching '*.pyo' found under directory 'examples' no previously-included directories found matching 'docs/_build' adding license file 'LICENSE' adding license file 'AUTHORS.md' writing manifest file 'Flask_RESTful.egg-info/SOURCES.txt' cd docs; PYTHONPATH=..
Bug#1049170: marked as done (tree-puzzle: Fails to build source after successful build)
Your message dated Sat, 9 Nov 2024 18:48:25 +0100 with message-id and subject line Re: Bug#1049170: tree-puzzle: Fails to build source after successful build has caused the Debian Bug report #1049170, regarding tree-puzzle: Fails to build source after successful build 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.) -- 1049170: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1049170 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: tree-puzzle Version: 5.3~rc16+dfsg-9 Severity: minor Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-sab-20230813 ftbfs-source-after-build User: debian...@lists.debian.org Usertags: qa-doublebuild Hi, This package fails to build a source package after a successful build (dpkg-buildpackage ; dpkg-buildpackage -S). This is probably a clear violation of Debian Policy section 4.9 (clean target), but this is filed as severity:minor for now, because a discussion on debian-devel showed that we might want to revisit the requirement of a working 'clean' target. More information about this class of issues, included common problems and solutions, is available at https://wiki.debian.org/qa.debian.org/FTBFS/SourceAfterBuild Relevant part of the build log: > cd /<> && runuser -u user42 -- dpkg-buildpackage --sanitize-env > -us -uc -rfakeroot -S > - > > dpkg-buildpackage: info: source package tree-puzzle > dpkg-buildpackage: info: source version 5.3~rc16+dfsg-9 > dpkg-buildpackage: info: source distribution unstable > dpkg-buildpackage: info: source changed by Andreas Tille > dpkg-source --before-build . > debian/rules clean > dh clean --no-parallel >dh_auto_clean -O--no-parallel > make -j1 distclean > make[1]: Entering directory '/<>' > Making distclean in src > make[2]: Entering directory '/<>/src' > test -z "puzzle ppuzzle" || rm -f puzzle ppuzzle > rm -f *.o > rm -f *.tab.c > test -z "" || rm -f > test . = "." || test -z "" || rm -f > rm -f config.h stamp-h1 > rm -f TAGS ID GTAGS GRTAGS GSYMS GPATH tags > rm -f ./.deps/consensus.Po > rm -f ./.deps/gamma.Po > rm -f ./.deps/ml1.Po > rm -f ./.deps/ml2.Po > rm -f ./.deps/mlparam.Po > rm -f ./.deps/model1.Po > rm -f ./.deps/model2.Po > rm -f ./.deps/ppuzzle.Po > rm -f ./.deps/pstep.Po > rm -f ./.deps/puzzle1.Po > rm -f ./.deps/puzzle2.Po > rm -f ./.deps/sched.Po > rm -f ./.deps/treesort.Po > rm -f ./.deps/treetest.Po > rm -f ./.deps/util.Po > rm -f Makefile > make[2]: Leaving directory '/<>/src' > Making distclean in doc > make[2]: Entering directory '/<>/doc' > make[3]: Entering directory '/<>/doc' > test -z "" || rm -f > test . = "." || test -z "" || rm -f > rm -f TAGS ID GTAGS GRTAGS GSYMS GPATH tags > make[3]: Leaving directory '/<>/doc' > rm -f Makefile > make[2]: Leaving directory '/<>/doc' > Making distclean in data > make[2]: Entering directory '/<>/data' > test -z "" || rm -f > test . = "." || test -z "" || rm -f > rm -f Makefile > make[2]: Leaving directory '/<>/data' > Making distclean in tests > make[2]: Entering directory '/<>/tests' > test -z "build-puzzle.log qp-pure-bin.log qp-pure-nucl.log qp-tn-nucl.log > qp-hky-clock-nucl.log qp-hky-rhet-nucl.log qp-hky-rhet-clock-nucl.log > qp-pure-prot.log qp-mtrev-prot.log qp-vt-prot.log qp-wag-prot.log > qp-clock.log qp-jtt-prot.log qp-jtt-rhet-prot.log qp-jtt-rhet-clock-prot.log > lm-pure-prot.log ut-pure-prot.log cons-pure-prot.log build-remark.log" || rm > -f build-puzzle.log qp-pure-bin.log qp-pure-nucl.log qp-tn-nucl.log > qp-hky-clock-nucl.log qp-hky-rhet-nucl.log qp-hky-rhet-clock-nucl.log > qp-pure-prot.log qp-mtrev-prot.log qp-vt-prot.log qp-wag-prot.log > qp-clock.log qp-jtt-prot.log qp-jtt-rhet-prot.log qp-jtt-rhet-clock-prot.log > lm-pure-prot.log ut-pure-prot.log cons-pure-prot.log build-remark.log > test -z "build-puzzle.trs qp-pure-bin.trs qp-pure-nucl.trs qp-tn-nucl.trs > qp-hky-clock-nucl.trs qp-hky-rhet-nucl.trs qp-hky-rhet-clock-nucl.trs > qp-pure-prot.trs qp-
Processed: closing 1061642
Processing commands for cont...@bugs.debian.org: > close 1061642 4.4.1-1~exp1 Bug #1061642 [src:make-dfsg] make-dfsg: README file refers to nonexistent files Marked as fixed in versions make-dfsg/4.4.1-1~exp1. Bug #1061642 [src:make-dfsg] make-dfsg: README file refers to nonexistent files Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 1061642: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061642 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1075979: marked as done (molds: FTBFS with mpich as default MPI provider: /usr/bin/ld: cannot find -lmpi_cxx: No such file or directory)
Your message dated Sat, 09 Nov 2024 17:19:43 + with message-id and subject line Bug#1075979: fixed in molds 0.3.1-2 has caused the Debian Bug report #1075979, regarding molds: FTBFS with mpich as default MPI provider: /usr/bin/ld: cannot find -lmpi_cxx: No such file or directory to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1075979: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075979 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: molds Version: 0.3.1-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org https://buildd.debian.org/status/fetch.php?pkg=molds&arch=armhf&ver=0.3.1-1%2Bb12&stamp=1720428636&raw=0 mpicxx -I/usr/include/mpi -I/usr/lib/openblas-base//include/ -o obj/Main.o Main.cpp -g -Wall -fopenmp -O2 -fopenmp -c mpicxx -o molds -Wl,-rpath=/usr//lib/ -Wl,-rpath=/usr/lib/openblas-base obj/Enums.o obj/PrintController.oobj/MolDSException.o obj/MallocerFreer.o obj/MpiProcess.o obj/AsyncCommunicator.oobj/Blas.o obj/Lapack.oobj/Utilities.oobj/MathUtilities.oobj/EularAngle.o obj/Parameters.oobj/Atom.oobj/Hatom.o obj/Liatom.o obj/Catom.o obj/Natom.o obj/Oatom.o obj/Satom.o obj/EnvironmentalPointCharge.o obj/AtomFactory.oobj/Molecule.oobj/InputParser.o obj/GTOExpansionSTO.oobj/RealSphericalHarmonicsIndex.o obj/MOLogger.oobj/DensityLogger.o obj/HoleDensityLogger.oobj/ParticleDensityLogger.o obj/Cndo2.o obj/Indo.o obj/ZindoS.oobj/Mndo.o obj/Am1.o obj/Am1D.o obj/Pm3.o obj/Pm3D.o obj/Pm3Pddg.o obj/ElectronicStructureFactory.o obj/MD.o obj/MC.o obj/RPMD.o obj/NASCO.oobj/Optimizer.o obj/ConjugateGradient.oobj/SteepestDescent.oobj/BFGS.o obj/GEDIIS.o obj/OptimizerFactory.o obj/MolDS.o obj/Main.o -L/usr//lib/ -L/usr/lib/openblas-base -lstdc++ -lm -lpthread -lgomp -L/usr/lib/lapack/ -llapacke -lmpi -lmpi_cxx -lboost_serialization -lboost_mpi -lboost_thread -lboost_system -lopenblas /usr/bin/ld: cannot find -lmpi_cxx: No such file or directory collect2: error: ld returned 1 exit status Cheers -- Sebastian Ramacher --- End Message --- --- Begin Message --- Source: molds Source-Version: 0.3.1-2 Done: Andreas Tille We believe that the bug you reported is fixed in the latest version of molds, 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 1075...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Tille (supplier of updated molds 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: Sat, 09 Nov 2024 17:52:14 +0100 Source: molds Architecture: source Version: 0.3.1-2 Distribution: unstable Urgency: medium Maintainer: Debichem Team Changed-By: Andreas Tille Closes: 1075979 Changes: molds (0.3.1-2) unstable; urgency=medium . * Team upload . [ Michael Banck ] * debian/control (Vcs-Browser, Vcs-Svn): Updated. . [ Drew Parsons ] * d/rules: drop excess from LIBSBASE (Closes: #1075979) . [ наб ] * d/rules: cd;make -> $(MAKE) -C * d/rules: allow failure from make clean * Makefile seems to need mkdir -p src/obj * Add hardening . [ Andreas Tille ] * Standards-Version: 4.7.0 (routine-update) * debhelper-compat 13 (routine-update) * Remove trailing whitespace in debian/changelog (routine-update) * Remove trailing whitespace in debian/rules (routine-update) * Rules-Requires-Root: no (routine-update) * Drop fields with obsolete URLs. * Update renamed lintian tag names in lintian overrides. * watch file standard 4 (routine-update) * d/rules: Use dh_-tools instead of $(MAKE) * Add Homepage * d/watch: At least report new version (even if this is n
Bug#1072867: marked as done (rust-image: please upgrade to 0.25)
Your message dated Sat, 09 Nov 2024 17:05:10 + with message-id and subject line Bug#1072867: fixed in rust-image 0.25.4-2 has caused the Debian Bug report #1072867, regarding rust-image: please upgrade to 0.25 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.) -- 1072867: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072867 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: rust-image Version: 0.24.7-2 Severity: normal Tags: upstream -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Please upgrade to, or separately provide, upstream branch v0.25. -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmZluDAACgkQLHwxRsGg ASElqg//QVwF4cY3Ff7NZCWd6+XGHlbcjCVHWJBHsac4PuspqgggWaZ5BHxRNiqK hP7qV+X/y/d0sN8GQMnC9sq50Ge4d+5dNga4eotOjATwcAfXeEFtsY8vihcUPTaD fhjo7XPhoy+iClxzlAiTV8D0etV/FHo39Bsb2HoF5mlh4BxiOPXgMWJJrPeyWk92 MWr2P6uSts3/KGt3bd/yAoJFe0t+5ixp6/Vh00tMgWbq1lH+mXDx0ecDEKbr+re4 COSVbB/XLsGK0wkn9IknO/U0ERFH5sMsFCsOmYUxh1UomGTU+QDft+CfEghSSMWe Vl8BZhMvmE+Nx1Rfysd4hj0oVgPeA4wPDOiuCCuEAS8RV9FV1J7N/nKe7IYCs+8X GFhykjAOzRJMhWwdkqiYpckCBQvoiQW8+3m6BnQ5cDeMKmcD1UcqfJ5RSSdIWn4R 8xQs4sxr8cCgKmvzQ4qxP+cUFDuM+88RDMjovl9Mh/6nZTeEGzRal5uMOnPReLZo YAaeELzW1h2lc6L02gJARj4lhV9wNgw4gj+MCB4RFEDKDrdofy1RIb8/5oi3Hn+p UvT32rQ4FMDQ0fLXQtWE2OjjHsEurG6TORJ6mvxO+6E3UhvQpxmUPdzj2H/C+7OZ 6NBx6JBoCQaB/jmvlOAaB5lUkBXDffQYfNTdD5iRVJZrZjxNtZI= =WdDP -END PGP SIGNATURE- --- End Message --- --- Begin Message --- Source: rust-image Source-Version: 0.25.4-2 Done: Matthias Geiger We believe that the bug you reported is fixed in the latest version of rust-image, 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 1072...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Matthias Geiger (supplier of updated rust-image package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 09 Nov 2024 17:52:07 +0100 Source: rust-image Architecture: source Version: 0.25.4-2 Distribution: unstable Urgency: medium Maintainer: Debian Rust Maintainers Changed-By: Matthias Geiger Closes: 1072867 Changes: rust-image (0.25.4-2) unstable; urgency=medium . * Team upload. * Upload to unstable (Closes: #1072867) Checksums-Sha1: 687d97cd1ee4d0c84549339c79a1d3e5c550fd04 2389 rust-image_0.25.4-2.dsc 53ff8c267613182df266ad972cabf3ed67d7bff3 8216 rust-image_0.25.4-2.debian.tar.xz f9e220dfa8189078bb2a9da665fad6a4258d2000 6615 rust-image_0.25.4-2_source.buildinfo Checksums-Sha256: 32f59625b91911887340c9cefa5996b31c792c4c0d0a92737d06d6de758a8308 2389 rust-image_0.25.4-2.dsc 24e99ba5b5388fcc106250e0e5ab473615ff31606d23ea2b112a06e297f4a419 8216 rust-image_0.25.4-2.debian.tar.xz dddc8443841bb9f97484aae6109f5872e3efc83a0f25b52a002b5552388524da 6615 rust-image_0.25.4-2_source.buildinfo Files: 10c0abb5d8cb0dbecb1a9ff33b470e6e 2389 rust optional rust-image_0.25.4-2.dsc 29062d18df37ab2435250cca635bc83a 8216 rust optional rust-image_0.25.4-2.debian.tar.xz 3634408bcf587b86b973b16852fe34c1 6615 rust optional rust-image_0.25.4-2_source.buildinfo -BEGIN PGP SIGNATURE- iHUEARYIAB0WIQQUWTv/Sl6/b+DpcW7svtu2B7myvgUCZy+TOwAKCRDsvtu2B7my vpevAP4/mgGa/8CeQZ3fnKueFuXOHHz3HcbGAI/sKz7psFVsogEA53jB/Qf+zluL BVsPOD8Aw97dr6k3b3bz0d0VBCisxQg= =vuk5 -END PGP SIGNATURE- pgpWxlIjgl72g.pgp Description: PGP signature --- End Message ---
Bug#1084190: marked as done (breakage due to tzdata System V name removal)
Your message dated Sat, 9 Nov 2024 17:05:13 + with message-id <156c3f53-4a5a-4e81-b5dc-6357f33f9...@zoho.com> and subject line Re: Bug#1084190: breakage due to tzdata System V name removal has caused the Debian Bug report #1084190, regarding breakage due to tzdata System V name removal to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1084190: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1084190 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: tzdata Version: 2024b-2 Severity: serious Justification: fails multiple autopkgtests tadata 2024b changes the meaning of short names such as 'EST' from 'always this offset' to 'alias for a place that currently uses this offset'. This causes several autopkgtest failures: - pandas and dateparser: use python3-tz and create test reference objects by passing a pytz.timezone directly to datetime.datetime. This has never worked for non-constant time zones, and the python3-tz documentation explicitly warns against it (https://pythonhosted.org/pytz/). Because this is being done in the test reference and not the actual library, a likely fix is simply to change the test to either use a constant (Etc/GMT-x) timezone or use pytz localize(). I am attempting this on both of them, though my first build of dateparser failed: https://salsa.debian.org/science-team/pandas/-/commit/02fd14ebca5bf79f54e65a1a94df23361fa31a84 https://salsa.debian.org/rnpalmer-guest/dateparser - postgresql-16: is explicitly testing the handling of dates far in the past, which this really does (slightly) change the meaning of. I'm not sure what should be done here. gnustep-base doesn't display a detailed enough error to say, but plausibly might be a similar problem. --- End Message --- --- Begin Message --- Most of these are now fixed, and hence, I agree it no longer makes sense to have a bug open against tzdata itself. Please upload the fixed flask-restful. Fixed: dateparser, pandas, glib, gnustep-base, reposurgeon, g.g.-teambition-rrule-go (described above), g.g.-spf13-cast #1086269, cctz #1084245, g.g.-vulcand-oxy #1084262, neovim #1084888, moment-timezone.js #1084301 Not fixed but not in testing: lektor #1084286, khal #1084282 Ambiguous - I consider it not fixed but no longer RC: mariadb #1084293 Not fixed, has a fix in Salsa: flask-restful #1084256--- End Message ---
Bug#1087121: marked as done (turing: Python SyntaxWarning)
Your message dated Sat, 09 Nov 2024 17:05:22 +
with message-id
and subject line Bug#1087121: fixed in turing 0.11-1
has caused the Debian Bug report #1087121,
regarding turing: Python SyntaxWarning
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.)
--
1087121: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1087121
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: turing
Version: 0.11~beta-8
User: debian-pyt...@lists.debian.org
Usertags: syntaxwarning
Hi Maintainer
The SyntaxWarning below were emitted when this package was tested with
pipuarts[1].
Regards
Graham
[1] https://piuparts.debian.org/sid/source/t/turing.html
Setting up python3 (3.12.6-1) ...
/usr/share/turing/src/forms/help.py:47: SyntaxWarning: invalid
escape sequence '\g'
desc = re.sub(r"{{(\w+)\}\}", "\g<1>", escape(desc))
/usr/share/turing/src/forms/help.py:48: SyntaxWarning: invalid
escape sequence '\g'
desc = re.sub(r"//(\w+)//", "\g<1>", desc)
/usr/share/turing/src/forms/inline_code_editor.py:76: SyntaxWarning:
invalid escape sequence '\g'
desc = re.sub(r"{{(\w+)\}\}", "\g<1>", html.escape(f[2]))
/usr/share/turing/src/forms/inline_code_editor.py:77: SyntaxWarning:
invalid escape sequence '\g'
desc = re.sub(r"//(\w+)//", "\g<1>", desc)
/usr/share/turing/src/maths/parser.py:541: SyntaxWarning: invalid
escape sequence '\s'
return re.sub("\s\s+", " ", result)
/usr/share/turing/src/tools/docgen.py:53: SyntaxWarning: invalid
escape sequence '\g'
desc = re.sub(r"{{(\w+)\}\}", "`\g<1>`", function[2])
/usr/share/turing/src/tools/docgen.py:54: SyntaxWarning: invalid
escape sequence '\g'
desc = re.sub(r"//(\w+)//", "*\g<1>*", desc)
/usr/share/turing/src/tools/docgen.py:94: SyntaxWarning: invalid
escape sequence '\g'
desc = re.sub(r"//(\w+)//", "*\g<1>*", desc)
--- End Message ---
--- Begin Message ---
Source: turing
Source-Version: 0.11-1
Done: Georges Khaznadar
We believe that the bug you reported is fixed in the latest version of
turing, 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 1087...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Georges Khaznadar (supplier of updated turing package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Sat, 09 Nov 2024 16:52:47 +0100
Source: turing
Architecture: source
Version: 0.11-1
Distribution: unstable
Urgency: medium
Maintainer: Georges Khaznadar
Changed-By: Georges Khaznadar
Closes: 1087121
Changes:
turing (0.11-1) unstable; urgency=medium
.
* new upstream version:
+ fixed SyntaxWarnings. Closes: #1087121
+ all debian patches were applied
* bumped Standards-Version: 4.7.0
Checksums-Sha1:
0e959bb8209c8a00be46f3ab4c6133bb13f76857 1989 turing_0.11-1.dsc
f860adc8645b2d93cf74fd0576f127fe3d881a97 2756564 turing_0.11.orig.tar.xz
4409707ef3f2985070440da12750fb7496a2fe1d 11572 turing_0.11-1.debian.tar.xz
98d207304b198fccff120d720edbf4adbda42c2e 12203 turing_0.11-1_source.buildinfo
Checksums-Sha256:
9e4a7b7fcb909523d97ba7495deaa003ea37f0395ced7ff8243fa43bda1ca189 1989
turing_0.11-1.dsc
b8b63b5d01719cf026722fb95fd6ad0ab1392e67fbf07ffcab84e3f75cd79f48 2756564
turing_0.11.orig.tar.xz
4e1958008e240b2b6185d37a4c6a769b75e9611db285d29bbd64268d483f51e2 11572
turing_0.11-1.debian.tar.xz
25ea561a67c861baf6fbcdad88ca1b79bf4aebe69a433a94a143290bb49b2438 12203
turing_0.11-1_source.buildinfo
Files:
b8061f7536fdaf8295c4c6c706ca9360 1989 x11 optional turing_0.11-1.dsc
75bb04fc13054223f7197dac04fa758a 2756564 x11 optional turing_0.11.orig.tar.xz
9a3f7630fb64a7bf781785ab4ec2c168 11572 x11 optional turing_0.11-1.debian.tar.xz
769b3287d070714f3c057a468e453a58 12203 x11 optional
turing_0.11-1_source.buildinfo
-BEGIN PGP SIGNATURE-
iQJIBAEBCAAyFiEEM0CzZP9nFT+3zK6FHCgWkHE2rjkFAmcvjKQUHGdlb3JnZXNr
QGRlYmlhbi5vcmcACgkQHCgWkHE2rjlM5RAAoNn9PN
Processed: reopening 991982, notfixed 991982 in 5.9, tagging 991982, closing 991982
Processing commands for cont...@bugs.debian.org: > # not a debian version > notfixed 991982 5.9 Bug #991982 [nano] nano does not work with TERM unsetted There is no source info for the package 'nano' at version '5.9' with architecture '' Unable to make a source version for version '5.9' Ignoring request to alter fixed versions of bug #991982 to the same values previously set > tags 991982 + fixed-upstream Bug #991982 [nano] nano does not work with TERM unsetted Ignoring request to alter tags of bug #991982 to the same tags previously set > close 991982 5.9-1 Bug #991982 [nano] nano does not work with TERM unsetted Marked as fixed in versions nano/5.9-1. Bug #991982 [nano] nano does not work with TERM unsetted Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 991982: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991982 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#991982: marked as done (nano does not work with TERM unsetted)
Your message dated Sat, 9 Nov 2024 16:57:05 +0100 with message-id <8fcc09d5-6844-4f76-8ade-701965801...@telfort.nl> and subject line nano can work now with TERM unset has caused the Debian Bug report #991982, regarding nano does not work with TERM unsetted 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.) -- 991982: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991982 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: nano Version: 5.4-2 Severity: grave Tags: upstream buster-ignore bullseye-ignore Justification: Policy 11.4 Control: affects -1 sensible-utils Dear Maintainer, Feel free to downgrade to important, but this bug affects sensible utils in case of disaster recovery so mark as grave (nano is the default system editor) $env -i nano command fail because TERM is unset nano should warn in this case and do like vi fallback to some dumb terminal setting For now I will work around in sensible utils, but ping me back when solved Bastien --- End Message --- --- Begin Message --- Package: nano Version: 5.9 Since commit 46cdf8b745, nano will work on most terminals even when TERM is unset. Benno OpenPGP_signature.asc Description: OpenPGP digital signature --- End Message ---
Bug#1084312: marked as done (olm: FTBFS: emcc: error: --memory-init-file is no longer supported)
Your message dated Sat, 09 Nov 2024 15:39:37 + with message-id and subject line Bug#1084312: fixed in olm 3.2.16+dfsg-3 has caused the Debian Bug report #1084312, regarding olm: FTBFS: emcc: error: --memory-init-file is no longer supported 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.) -- 1084312: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1084312 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:olm Version: 3.2.16+dfsg-2 Severity: serious Tags: ftbfs Dear maintainer: During a rebuild of all packages in unstable, your package failed to build: [...] debian/rules binary dh binary --buildsystem=cmake --builddir=build --with pkgkde_symbolshelper dh_update_autotools_config -O--buildsystem=cmake -O--builddir=build dh_autoreconf -O--buildsystem=cmake -O--builddir=build dh_auto_configure -O--buildsystem=cmake -O--builddir=build cd build && DEB_PYTHON_INSTALL_LAYOUT=deb PKG_CONFIG=/usr/bin/pkg-config cmake -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON -DCMAKE_FIND_USE_PACKAGE_REGISTRY=OFF -DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON -DFETCHCONTENT_FULLY_DISCONNECTED=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run -DCMAKE_SKIP_INSTALL_ALL_DEPENDENCY=ON "-GUnix Makefiles" -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu .. CMake Deprecation Warning at CMakeLists.txt:1 (cmake_minimum_required): Compatibility with CMake < 3.5 will be removed from a future version of CMake. Update the VERSION argument value or use a ... suffix to tell CMake that the project does not need compatibility with older versions. -- The CXX compiler identification is GNU 14.2.0 -- The C compiler identification is GNU 14.2.0 -- Detecting CXX compiler ABI info -- Detecting CXX compiler ABI info - done -- Check for working CXX compiler: /usr/bin/c++ - skipped -- Detecting CXX compile features -- Detecting CXX compile features - done -- Detecting C compiler ABI info -- Detecting C compiler ABI info - done -- Check for working C compiler: /usr/bin/cc - skipped -- Detecting C compile features -- Detecting C compile features - done -- Performing Test COMPILER_HAS_HIDDEN_VISIBILITY -- Performing Test COMPILER_HAS_HIDDEN_VISIBILITY - Success -- Performing Test COMPILER_HAS_HIDDEN_INLINE_VISIBILITY -- Performing Test COMPILER_HAS_HIDDEN_INLINE_VISIBILITY - Success -- Performing Test COMPILER_HAS_DEPRECATED_ATTR -- Performing Test COMPILER_HAS_DEPRECATED_ATTR - Success -- Configuring done (0.6s) -- Generating done (0.0s) CMake Warning: Manually-specified variables were not used by the project: CMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY CMAKE_FIND_USE_PACKAGE_REGISTRY FETCHCONTENT_FULLY_DISCONNECTED -- Build files have been written to: /<>/build debian/rules override_dh_auto_build-indep make[1]: Entering directory '/<>' pandoc --from gfm-raw_html --to html --standalone --output javascript/README.html javascript/README.md [WARNING] This document format requires a nonempty element. Defaulting to 'README' as the title. To specify a title, use 'title' in metadata or --metadata title="...". pandoc --from gfm-raw_html --to plain --output javascript/README.txt javascript/README.md CFLAGS="-O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-clash-protection -Wformat -Werror=format-security" \ CXXFLAGS="-O2 -ffile-prefix-map=/<>=. -fstack-clash-protection -Wformat -Werror=format-security" \ LDFLAGS="-Wl,-z,relro" \ LDFLAGS="" \ make -j2 js make[2]: Entering directory '/<>' mkdir -p build/javascript/src/ mkdir -p build/javascript/src/ emcc -O2 -ffile-prefix-map=/<>=. -fstack-clash-protection -Wformat -Werror=format-security -O3 -Wdate-time -D_FORTIFY_SOURCE=2 -Iinclude -Ilib -DOLMLIB_VERSION_MAJOR=3 -DOLMLIB_VERSION_MINOR=2 -DOLMLIB_VERSION_PATCH=16 -MMD -c -DNDEBUG -DOLM_STATIC_DEFINE=1 -o build/javascript/src/account.o src/account.cpp emcc -O2 -ffile-prefix-map=/<>=. -fstack-clash-protection -Wformat -Werror=format-security -O3 -Wdate-time -D_FORTIFY_SOURCE=2 -Iinclude -Ilib -DOLMLIB_VERSION_MAJOR=3 -DOLMLIB_VERSION_MINOR=2 -DOLMLIB_VERSION_PATCH=16 -MMD -c -DNDEBUG -DOLM_STATIC_DEFINE=1 -o build/javascript/src/base64.o src/base64.cpp clang-18clang-18: warning: argument unused
Bug#1064206: marked as done (borgmatic: Invalid parameter raises : AttributeError: module 'logging' has no attribute 'DISABLED')
Your message dated Sat, 09 Nov 2024 15:34:58 +
with message-id
and subject line Bug#1064206: fixed in borgmatic 1.9.0-0.1
has caused the Debian Bug report #1064206,
regarding borgmatic: Invalid parameter raises : AttributeError: module
'logging' has no attribute 'DISABLED'
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.)
--
1064206: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064206
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: borgmatic
Version: 1.8.3-1
Severity: normal
Dear Maintainer,
TL;DR: A Python exception pollutes the output when using borgmatic 1.8.3 with
invalid parameters or other configuration problems.
This issue is corrected in later versions, but here is a small patch to correct
it.
I made a migration from a previous borgmatic version with different parameters
and faced this issue with bormatic 1.8.3 :
When using incorrect parameters (in CLI), borgmatic prints a Python exception
about the DISABLED property being undefined on the logging module.
By example :
> borgmatic prunee
usage: borgmatic [-h] [-c CONFIG_PATHS] [-n] [-nc] [-v {-2,-1,0,1,2}]
[--syslog-verbosity {-2,-1,0,1,2}] [--log-file-verbosity {-2,-1,0,1,2}]
[--monitoring-verbosity {-2,-1,0,1,2}] [--log-file LOG_FILE] [--log-file-format
LOG_FILE_FORMAT]
[--log-json] [--override OPTION.SUBOPTION=VALUE]
[--no-environment-interpolation] [--bash-completion] [--fish-completion]
[--version]
...
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/borgmatic/commands/borgmatic.py", line
816, in main
arguments = parse_arguments(*sys.argv[1:])
^^
File "/usr/lib/python3/dist-packages/borgmatic/commands/arguments.py", line
1283, in parse_arguments
raise ValueError(
ValueError: Unrecognized argument: prunee
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/bin/borgmatic", line 33, in
sys.exit(load_entry_point('borgmatic==1.8.3', 'console_scripts',
'borgmatic')())
^^
File "/usr/lib/python3/dist-packages/borgmatic/commands/borgmatic.py", line
818, in main
configure_logging(logging.CRITICAL)
File "/usr/lib/python3/dist-packages/borgmatic/logger.py", line 170, in
configure_logging
syslog_log_level = logging.DISABLED
AttributeError: module 'logging' has no attribute 'DISABLED'
This issue is, in a sense, cosmetic, but pollutes the logs with useless
stacktraces.
It comes from logger.py, where the custom DISABLED status is being used (line
170) before being defined (line 176).
This issue is corrected in borgmatic 1.8.4, but it can be corrected too in
1.8.3 with the following patch :
--- /usr/lib/python3/dist-packages/borgmatic/logger.py 2024-02-18
08:45:36.101652793 +0100
+++ /usr/lib/python3/dist-packages/borgmatic/logger-ok.py 2024-02-18
08:47:19.790311543 +0100
@@ -166,6 +166,9 @@
Raise FileNotFoundError or PermissionError if the log file could not be
opened for writing.
'''
+
+add_custom_log_levels()
+
if syslog_log_level is None:
syslog_log_level = logging.DISABLED
if log_file_log_level is None:
@@ -173,8 +176,6 @@
if monitoring_log_level is None:
monitoring_log_level = console_log_level
-add_custom_log_levels()
-
# Log certain log levels to console stderr and others to stdout. This
supports use cases like
# grepping (non-error) output.
console_disabled = logging.NullHandler()
Resulting in the following output for the same command :
> borgmatic -c /etc/borgmatic.d/wordpress-bb.yaml prunee --list --stats
usage: borgmatic [-h] [-c CONFIG_PATHS] [-n] [-nc] [-v {-2,-1,0,1,2}]
[--syslog-verbosity {-2,-1,0,1,2}] [--log-file-verbosity {-2,-1,0,1,2}]
[--monitoring-verbosity {-2,-1,0,1,2}] [--log-file LOG_FILE] [--log-file-format
LOG_FILE_FORMAT]
[--log-json] [--override OPTION.SUBOPTION=VALUE]
[--no-environment-interpolation] [--bash-completion] [--fish-completion]
[--version]
...
Unrecognized argument: prunee
Need some
Bug#1054605: marked as done (borgmatic: Systemd service ignores /etc/borgmatic.d/ when deciding whether to run)
Your message dated Sat, 09 Nov 2024 15:34:58 + with message-id and subject line Bug#1054605: fixed in borgmatic 1.9.0-0.1 has caused the Debian Bug report #1054605, regarding borgmatic: Systemd service ignores /etc/borgmatic.d/ when deciding whether to run 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.) -- 1054605: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054605 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: borgmatic Version: 1.7.7-1 Severity: normal X-Debbugs-Cc: t...@debian.org Hi, Today I realised that a borgmatic setup was not performing daily backups, despite not receiving any errors. Upon inspection, I noticed the borgmatic.service file has the following option: ConditionFileNotEmpty=/etc/borgmatic/config.yaml Since I have multiple backup configurations, I created separate files in /etc/borgmatic.d/, as recommended in the official documentation[1]. This means the backup is never launched automatically. This is not documented anywhere, and I am not even sure what would be the workaround, except removing the service option. [1]: https://torsion.org/borgmatic/docs/how-to/make-per-application-backups/ -- System Information: Debian Release: 12.2 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'proposed-updates'), (500, 'stable'), (50, 'unstable'), (49, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-13-amd64 (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_USER Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages borgmatic depends on: ii borgbackup 1.2.4-1 ii python33.11.2-1+b1 ii python3-colorama 0.4.6-2 ii python3-jsonschema 4.10.3-1 ii python3-pkg-resources 66.1.1-1 ii python3-requests 2.28.1+dfsg-1 ii python3-ruamel.yaml0.17.21-1 borgmatic recommends no packages. borgmatic suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: borgmatic Source-Version: 1.9.0-0.1 Done: Geoffroy Youri Berret We believe that the bug you reported is fixed in the latest version of borgmatic, 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 1054...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Geoffroy Youri Berret (supplier of updated borgmatic 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: Sat, 09 Nov 2024 15:59:26 +0100 Source: borgmatic Architecture: source Version: 1.9.0-0.1 Distribution: unstable Urgency: medium Maintainer: Debian Borg Collective Changed-By: Geoffroy Youri Berret Closes: 1054605 1064206 Changes: borgmatic (1.9.0-0.1) unstable; urgency=medium . * Non-maintainer upload. * Switch d/watch to official upstream forge * d/rules: add upstream changelog * Add systemd start condition on /etc/borgmatic.d/*.yaml (Closes: #1054605) * New upstream version 1.9.0 (Closes: #1064206) * Build-Depends on pybuild-plugin-pyproject * d/patches: refresh patches Checksums-Sha1: 5457b6023a1f4231949854a5c088bb455d5aadbf 2298 borgmatic_1.9.0-0.1.dsc 23fe356bf23774edfa1793aa15013afb5b7cec52 633842 borgmatic_1.9.0.orig.tar.gz 2bcc66791c7392ffd79ab8393173dddf1eedea2e 5860 borgmatic_1.9.0-0.1.debian.tar.xz e32c4ce709b5ee287999d11b843a3f176b953f90 8486 borgmatic_1.9.0-0.1_amd64.buildinfo Checksums-Sha256: 84148aae08e2b7cdd4c88aca87a5a90cc57f2069621453f167b0b5d6a5ff8c8b 2298 borgmatic_1.9.0-0.1.dsc 3779b7abe5d905d348a00265983d095041cbb4c6877b38680483d3c2db5a 633842 borgmatic_1.9.0.orig.tar.gz 6822e93ec56a292e6d3fa9259b791ce231725481b6f5fadc4316b31c79b413e4 5860 borgmatic_1.9.0-0.1.debian.tar.xz dd6c43e8184b89b8649a2b58ddf8d504944ce6d57660ee464f2689b9e678c6d1 8486 borgmatic_1.9.0-0.1_amd64.buildinfo Files: 351b6278b526f3e5838b307e5f3566f3 2298 utils optional borgmatic_1.9.0-0.1.dsc 49ff53559f374c98dd7caa6896e119ce 633842 utils optional borgmatic_1.
Bug#1086634: marked as done (veyon: FTBFS on armel: /usr/include/c++/14/bits/atomic_base.h:501:(.text+0xa5d0): undefined reference to `__atomic_load_8')
Your message dated Sat, 09 Nov 2024 15:20:16 +
with message-id
and subject line Bug#1086634: fixed in veyon 4.7.5+repack1-1.2
has caused the Debian Bug report #1086634,
regarding veyon: FTBFS on armel:
/usr/include/c++/14/bits/atomic_base.h:501:(.text+0xa5d0): undefined reference
to `__atomic_load_8'
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.)
--
1086634: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1086634
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: veyon
Version: 4.7.5+repack1-1.1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org
https://buildd.debian.org/status/fetch.php?pkg=veyon&arch=armel&ver=4.7.5%2Brepack1-1.1%2Bb2&stamp=1730436262&raw=0
[ 96%] Building CXX object
master/CMakeFiles/veyon-master.dir/src/RecursiveFilterProxyModel.cpp.o
cd /<>/obj-arm-linux-gnueabi/master && /usr/bin/g++
-DQT_CONCURRENT_LIB -DQT_CORE_LIB -DQT_DEPRECATED_WARNINGS
-DQT_DISABLE_DEPRECATED_BEFORE=0x050e00 -DQT_GUI_LIB -DQT_NETWORK_LIB
-DQT_NO_CAST_FROM_ASCII -DQT_NO_CAST_FROM_BYTEARRAY -DQT_NO_CAST_TO_ASCII
-DQT_NO_DEBUG -DQT_NO_KEYWORDS -DQT_NO_NARROWING_CONVERSIONS_IN_CONNECT
-DQT_STRICT_ITERATORS -DQT_USE_QSTRINGBUILDER -DQT_WIDGETS_LIB
-D_FORTIFY_SOURCE=2
-I/<>/obj-arm-linux-gnueabi/master/veyon-master_autogen/include
-I/<>/obj-arm-linux-gnueabi/master -I/<>/master/src
-I/<>/obj-arm-linux-gnueabi/core -I/<>/core/src
-I/<>/obj-arm-linux-gnueabi/core/src
-I/usr/include/arm-linux-gnueabi/qt5
-I/usr/include/arm-linux-gnueabi/qt5/QtConcurrent
-I/usr/include/arm-linux-gnueabi/qt5/QtCore
-I/usr/lib/arm-linux-gnueabi/qt5/mkspecs/linux-g++
-I/usr/include/arm-linux-gnueabi/qt5/QtGui
-I/usr/include/arm-linux-gnueabi/qt5/QtNetwork
-I/usr/include/arm-linux-gnueabi/qt5/QtWidgets -I/usr/include/Qca-qt5/QtCrypto
-g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong
-fstack-clash-protection -Wformat -Werror=format-security -D_LARGEFILE_SOURCE
-D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2
-fstack-protector-strong -fno-exceptions -O2 -g -DNDEBUG -std=gnu++14
-fvisibility=hidden -fvisibility-inlines-hidden -fPIE -Wall -Werror "-flto=8
-fno-fat-lto-objects" -fPIC -MD -MT
master/CMakeFiles/veyon-master.dir/src/RecursiveFilterProxyModel.cpp.o -MF
CMakeFiles/veyon-master.dir/src/RecursiveFilterProxyModel.cpp.o.d -o
CMakeFiles/veyon-master.dir/src/RecursiveFilterProxyModel.cpp.o -c
/<>/master/src/RecursiveFilterProxyModel.cpp
/usr/bin/ld: /tmp/ccsGNr3e.ltrans0.ltrans.o: in function
`WebApiController::getFramebuffer(WebApiController::Request const&)':
/usr/include/c++/14/bits/atomic_base.h:501:(.text+0xa5d0): undefined reference
to `__atomic_load_8'
/usr/bin/ld: /tmp/ccsGNr3e.ltrans0.ltrans.o: in function
`WebApiConnection::runFramebufferEncoder()::{lambda()#1}::operator()() const':
/usr/include/c++/14/bits/atomic_base.h:501:(.text+0xad34): undefined reference
to `__atomic_load_8'
/usr/bin/ld: /usr/include/c++/14/bits/atomic_base.h:501:(.text+0xad78):
undefined reference to `__atomic_load_8'
/usr/bin/ld: /usr/include/c++/14/bits/atomic_base.h:477:(.text+0xad90):
undefined reference to `__atomic_store_8'
collect2: error: ld returned 1 exit status
make[3]: *** [plugins/webapi/CMakeFiles/webapi.dir/build.make:237:
plugins/webapi/webapi.so] Error 1
make[3]: Leaving directory '/<>/obj-arm-linux-gnueabi'
make[2]: *** [CMakeFiles/Makefile2:2994:
plugins/webapi/CMakeFiles/webapi.dir/all] Error 2
make[2]: *** Waiting for unfinished jobs
Cheers
--
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Source: veyon
Source-Version: 4.7.5+repack1-1.2
Done: Dmitry Shachnev
We believe that the bug you reported is fixed in the latest version of
veyon, 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 1086...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Dmitry Shachnev (supplier of updated veyon 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-
Bug#1087113: marked as done (dhcpcd: flaky autopkgtest on amd64: test timesyncd-ntp-servers-from-dhcp)
Your message dated Sat, 09 Nov 2024 14:34:14 + with message-id and subject line Bug#1087113: fixed in dhcpcd 1:10.1.0-2 has caused the Debian Bug report #1087113, regarding dhcpcd: flaky autopkgtest on amd64: test timesyncd-ntp-servers-from-dhcp 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.) -- 1087113: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1087113 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: dhcpcd Version: 1:10.1.0-1 Severity: serious User: debian...@lists.debian.org Usertags: flaky Dear maintainer(s), The dhcpcd autopkgtest on amd64 are flaky, and fail roughly half of the runs. As per RT, flaky autopkgtest are RC. Example: 19s autopkgtest [04:11:44]: test timesyncd-ntp-servers-from-dhcp: [--- 220s Preparing virtual interfaces... 220s Actual changes: 220s tx-checksum-ip-generic: off 220s tx-tcp-segmentation: off [not requested] 220s tx-tcp-ecn-segmentation: off [not requested] 220s tx-tcp-mangleid-segmentation: off [not requested] 220s tx-tcp6-segmentation: off [not requested] 220s tx-udp-segmentation: off [not requested] 220s tx-checksum-sctp: off 220s Preparing dnsmasq configuration... 225s Obtaining network configuration for veth1 via dhcp... 255s timed out 256s autopkgtest [04:12:21]: test timesyncd-ntp-servers-from-dhcp: ---] ▾ test timesyncd-ntp-servers-from-dhcp: test results 256s autopkgtest [04:12:21]: test timesyncd-ntp-servers-from-dhcp: - - - - - - - - - - results - - - - - - - - - - 256s timesyncd-ntp-servers-from-dhcp FAIL non-zero exit status 1 https://ci.debian.net/packages/d/dhcpcd/testing/amd64/53381886/ https://ci.debian.net/packages/d/dhcpcd/testing/amd64/ --- End Message --- --- Begin Message --- Source: dhcpcd Source-Version: 1:10.1.0-2 Done: Martin-Éric Racine We believe that the bug you reported is fixed in the latest version of dhcpcd, 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 1087...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Martin-Éric Racine (supplier of updated dhcpcd 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: Sat, 09 Nov 2024 10:18:58 +0200 Source: dhcpcd Architecture: source Version: 1:10.1.0-2 Distribution: unstable Urgency: medium Maintainer: Martin-Éric Racine Changed-By: Martin-Éric Racine Closes: 1084139 1087113 Changes: dhcpcd (1:10.1.0-2) unstable; urgency=medium . * [autopkgtest] + Restrictions: timesyncd-ntp-servers-from-dhcp flaky (Closes: #1087113). Thanks to Luca Boccassi for this kludge against 'dnsmasq' timeouts. * [copyright] = Update according to latest Lintian results (Closes: #1084139). Thanks to Phil Wyett for the extensive copyright review. Checksums-Sha1: 4477e83e2e15a4f721f0f4e6d760134feb6661e3 2366 dhcpcd_10.1.0-2.dsc d27f0e243b5b156e734cb2a38f975582469deaab 271668 dhcpcd_10.1.0.orig.tar.xz 9878b17c9676dff4db3bce72d61d1a88c5e3e9f8 488 dhcpcd_10.1.0.orig.tar.xz.asc de99769f8dc8bdc630b46bf5626c334047f87830 17796 dhcpcd_10.1.0-2.debian.tar.xz c2b36e63b66449a772276af937157c2699969463 6788 dhcpcd_10.1.0-2_amd64.buildinfo Checksums-Sha256: c091fd02651f38f09495bb9937d0b28c09823ef37de6ff1686975e971183b4fe 2366 dhcpcd_10.1.0-2.dsc 97f6206de38e43684adb531d940283f1e8f35dafa03ee117456fb69132fcefb1 271668 dhcpcd_10.1.0.orig.tar.xz e98a3316efbfd1ce4f7a610213b4bf3c038ec07bdec4c97aabad77d52fef8998 488 dhcpcd_10.1.0.orig.tar.xz.asc de75f3bfa0def6801ba6401f1715b3515e8fc58a8990db2a27707f8ff7b01696 17796 dhcpcd_10.1.0-2.debian.tar.xz 3acf27db86282c4cd1fdc4ca0be4b40b9c9dc5cb83fa0f46f315e536f6654f8d 6788 dhcpcd_10.1.0-2_amd64.buildinfo Files: 2e1e917f1cff8b1905afff22b396ad86 2366 net optional dhcpcd_10.1.0-2.dsc 433a7dbc57c2d4b6ffa144b17397bb3f 271668 net optional dhcpcd_10.1.0.orig.tar.xz e834003e26c50d02058fc96d180e5d97 488 net optional dhcpcd_10.1.0.orig.tar.xz.asc edc30a11bd8517dc987527a1c9ae6c6e 17796 net optional dhcpcd_10.1.0-2.debian.tar.xz b34458dcdbcc508da30762bf6f5335e5 6788 net optional dhcpcd_10.1.0-2_amd64.buildinfo -BEGIN PGP
Bug#1086488: marked as done (autopkgtest: test command2 is failing)
Your message dated Sat, 9 Nov 2024 15:01:36 +0100 with message-id and subject line Re: Bug#1086488: autopkgtest: test command2 is failing has caused the Debian Bug report #1086488, regarding autopkgtest: test command2 is failing 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.) -- 1086488: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1086488 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: xtensor-blas Version: 0.21.0-1 Severity: important Dear Maintainer, Probably same as: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1080464 but an autopkgtest is failing with: 418s In file included from /tmp/autopkgtest-lxc.j47l5g8t/downtmp/autopkgtest_tmp/test_lstsq.cpp:15: 418s In file included from /usr/include/xtensor/xarray.hpp:19: 418s In file included from /usr/include/xtensor/xbuffer_adaptor.hpp:21: 418s In file included from /usr/include/xtensor/xstorage.hpp:23: 418s In file included from /usr/include/xtensor/xtensor_simd.hpp:17: 418s /usr/include/xtensor/xutils.hpp:896:31: error: ambiguous partial specializations of 'rebind_container>' 418s 896 | using type = typename rebind_container::type; 418s | ^ 418s /usr/include/xtensor/xutils.hpp:924:5: note: in instantiation of template class 'xt::get_strides_type>' requested here 418s 924 | using get_strides_t = typename get_strides_type::type; 418s | ^ Cheers S -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'oldstable'), (300, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.11.2-amd64 (SMP w/20 CPU threads; PREEMPT) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled --- End Message --- --- Begin Message --- This was a bug in xtensor not xtensor-blas. Now fixed.--- End Message ---
Processed: Re: please include pim6d binary
Processing commands for cont...@bugs.debian.org: > close 1071653 Bug #1071653 [frr] please include pim6d binary Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 1071653: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071653 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1086564: marked as done (ceph: FTBFS with fmtlib 10)
Your message dated Sat, 09 Nov 2024 13:40:22 +
with message-id
and subject line Bug#1086564: fixed in ceph 18.2.4+ds-8
has caused the Debian Bug report #1086564,
regarding ceph: FTBFS with fmtlib 10
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.)
--
1086564: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1086564
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ceph
Version: 18.2.4+ds-7
Severity: important
Tags: ftbfs
X-Debbugs-Cc: fmt...@packages.debian.org
Control: block 1072674 by -1
Control: affects -1 src:fmtlib
Dear maintainers,
fmtlib 10 transition will start soon, your package ceph FTBFS with
fmtlib 10.1.1+ds1-2 in experimental.
Here is some related log:
[ 82%] Building CXX object
CMakeFiles/rocksdb.dir/utilities/merge_operators/put.cc.o
/usr/bin/c++ -DHAVE_PCLMUL -DHAVE_SSE42 -DLZ4 -DOS_LINUX
-DROCKSDB_FALLOCATE_PRESENT -DROCKSDB_LIB_IO_POSIX -DROCKSDB_MALLOC_USABLE_SIZE
-DROCKSDB_NO_DYNAMIC_EXTENSION -DROCKSDB_PLATFORM_POSIX -DROCKSDB_PORTABLE
-DROCKSDB_PTHREAD_ADAPTIVE_MUTEX -DROCKSDB_RANGESYNC_PRESENT
-DROCKSDB_SCHED_GETCPU_PRESENT -DSNAPPY -DZLIB -I/<>/src/rocksdb
-I/<>/src/rocksdb/include -isystem
/<>/src/rocksdb/third-party/gtest-1.8.1/fused-src -g -O2
-ffile-prefix-map=/<>=. -fstack-protector-strong
-fstack-clash-protection -Wformat -Werror=format-security -fcf-protection
-DFMT_DEPRECATED_OSTREAM -fpermissive -Wdate-time -D_FORTIFY_SOURCE=2
-Wno-deprecated-copy -Wno-pessimizing-move -W -Wextra -Wall -pthread
-Wsign-compare -Wshadow -Wno-unused-parameter -Wno-unused-variable
-Woverloaded-virtual -Wnon-virtual-dtor -Wno-missing-field-initializers
-Wno-strict-aliasing -Wno-invalid-offsetof -fno-omit-frame-pointer
-momit-leaf-frame-pointer -fno-builtin-memcmp -O2 -g -DNDEBUG -std=gnu++17
-fPIC -MD -MT CMakeFiles/rocksdb.dir/utilities/merge_operators/put.cc.o -MF
CMakeFiles/rocksdb.dir/utilities/merge_operators/put.cc.o.d -o
CMakeFiles/rocksdb.dir/utilities/merge_operators/put.cc.o -c
/<>/src/rocksdb/utilities/merge_operators/put.cc
In file included from /usr/include/fmt/format.h:49,
from /<>/src/msg/msg_types.h:21,
from /<>/src/common/entity_name.h:22,
from /<>/src/auth/Auth.h:19,
from /<>/src/msg/async/crypto_onwire.h:22,
from /<>/src/msg/async/frames_v2.h:6,
from /<>/src/msg/async/frames_v2.cc:15:
/usr/include/fmt/core.h: In instantiation of ‘constexpr decltype (ctx.begin())
fmt::v10::detail::parse_format_specs(ParseContext&) [with T = ceph_le; ParseContext = compile_parse_context; decltype (ctx.begin()) =
const char*]’:
/usr/include/fmt/core.h:2639:51: required from here
2639 | return id >= 0 && id < num_args ? parse_funcs_[id](context_) :
begin;
| ^
/<>/src/msg/async/frames_v2.cc:308:33: in ‘constexpr’ expansion
of ‘fmt::v10::basic_format_string&>("bad preamble crc calculated={} expected={}")’
/usr/include/fmt/core.h:2740:40: in ‘constexpr’ expansion of
‘fmt::v10::detail::parse_format_string > >(((fmt::v10::basic_format_string&>*)this)->fmt::v10::basic_format_string&>::str_, fmt::v10::detail::format_string_checker >(fmt::v10::basic_string_view(((const
char*)s’
/usr/include/fmt/core.h:2523:36: in ‘constexpr’ expansion of
‘fmt::v10::detail::parse_replacement_field >&>(p, end, (* & handler))’
/usr/include/fmt/core.h:2457:33: in ‘constexpr’ expansion of ‘(&
handler)->fmt::v10::detail::format_string_checker >::on_replacement_field((&
handler)->fmt::v10::detail::format_string_checker >::on_arg_id(), begin)’
/usr/include/fmt/core.h:2632:20: in ‘constexpr’ expansion of
‘((fmt::v10::detail::format_string_checker >*)this)->fmt::v10::detail::format_string_checker >::on_format_specs(id, begin, begin)’
/usr/include/fmt/core.h:2548:45: error:
‘fmt::v10::detail::type_is_unformattable_for, char> _’
has incomplete type
2548 | type_is_unformattable_for _;
| ^
/usr/include/fmt/core.h: In instantiation of ‘constexpr
fmt::v10::detail::value fmt::v10::detail::make_arg(T&) [with bool
PACKED = true; Context = fmt::v10::basic_format_context; T = const ceph_le; typename std::enable_if::type = 0]’:
/usr/include/fmt/core.h:1808:51: required from ‘constexpr
fmt::v10::format_arg_store::form
Bug#1044119: marked as done (collectd: Fails to build source after successful build)
Your message dated Sat, 09 Nov 2024 12:49:06 + with message-id and subject line Bug#1044119: fixed in collectd 5.12.0-21 has caused the Debian Bug report #1044119, regarding collectd: Fails to build source after successful build 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.) -- 1044119: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1044119 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: collectd Version: 5.12.0-14 Severity: minor Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-sab-20230813 ftbfs-source-after-build User: debian...@lists.debian.org Usertags: qa-doublebuild Hi, This package fails to build a source package after a successful build (dpkg-buildpackage ; dpkg-buildpackage -S). This is probably a clear violation of Debian Policy section 4.9 (clean target), but this is filed as severity:minor for now, because a discussion on debian-devel showed that we might want to revisit the requirement of a working 'clean' target. More information about this class of issues, included common problems and solutions, is available at https://wiki.debian.org/qa.debian.org/FTBFS/SourceAfterBuild Relevant part of the build log: > cd /<> && runuser -u user42 -- dpkg-buildpackage --sanitize-env > -us -uc -rfakeroot -S > > > dpkg-buildpackage: info: source package collectd > dpkg-buildpackage: info: source version 5.12.0-14 > dpkg-buildpackage: info: source distribution unstable > dpkg-buildpackage: info: source changed by Bernd Zeimetz > dpkg-source --before-build . > fakeroot debian/rules clean > dh clean >dh_auto_clean > make -j8 distclean > make[1]: Entering directory '/<>' > test -z "libplugin_mock.la" || rm -f libplugin_mock.la > test -z ".perl-directory-stamp bindings/buildperl/Collectd.pm > bindings/buildperl/Collectd/Plugins/OpenVZ.pm > bindings/buildperl/Collectd/Unixsock.pm bindings/buildperl/Makefile.PL > collectd-api.jar collectd.grpc.pb.cc collectd.grpc.pb.h collectd.pb.cc > collectd.pb.h generic-jmx.jar org/collectd/api/*.class > org/collectd/java/*.class prometheus.pb-c.c prometheus.pb-c.h > src/pinba.pb-c.c src/pinba.pb-c.h types.grpc.pb.cc types.grpc.pb.h > types.pb.cc types.pb.h" || rm -f .perl-directory-stamp > bindings/buildperl/Collectd.pm bindings/buildperl/Collectd/Plugins/OpenVZ.pm > bindings/buildperl/Collectd/Unixsock.pm bindings/buildperl/Makefile.PL > collectd-api.jar collectd.grpc.pb.cc collectd.grpc.pb.h collectd.pb.cc > collectd.pb.h generic-jmx.jar org/collectd/api/*.class > org/collectd/java/*.class prometheus.pb-c.c > prometheus.pb-c.h src/pinba.pb-c.c src/pinba.pb-c.h types.grpc.pb.cc > types.grpc.pb.h types.pb.cc types.pb.h > test -z "libcollectdclient.la" || rm -f libcollectdclient.la > rm -rf .libs _libs > rm -rf buildperl > rm -f collectd-nagios collectd-tg collectdctl > rm -f *.class classnoinst.stamp > rm -f test_common test_format_graphite test_meta_data test_utils_avltree > test_utils_cmds test_utils_heap test_utils_latency test_utils_message_parser > test_utils_mount test_utils_subst test_utils_time test_utils_vl_lookup > test_libcollectd_network_parse test_utils_config_cores test_format_json > test_plugin_ceph test_utils_oauth test_format_stackdriver > test_plugin_capabilities test_plugin_curl_json test_plugin_intel_rdt > test_utils_proc_pids test_plugin_logparser test_plugin_mdevents > test_plugin_netlink test_plugin_network test_plugin_pcie_errors > test_plugin_smart test_plugin_snmp_agent test_plugin_virt > test -z "libavltree.la libcmds.la libcommon.la libformat_graphite.la > libformat_json.la libheap.la libignorelist.la liblatency.la libllist.la > liblookup.la libmetadata.la libmount.la liboconfig.la liboauth.la libgce.la > libformat_stackdriver.la libtaskstats.la" || rm -f libavltree.la libcmds.la > libcommon.la libformat_graphite.la libformat_json.la libheap.la > libignorelist.la liblatency.la libllist.la liblookup.la libmetadata.la > libmount.la liboconfig.la liboauth.la libgce.la libformat_stackdriver.la > libtaskstats.la > test -z "aggregation.la amqp.la amqp1.la apache.la apcups.la ascent.la > barometer.la battery.la bind.la buddyinfo.la capabilities.la ceph.la > cgroups.la chrony.la check_upti
Bug#1080660: marked as done (Missing Build-Depends on python3-setuptools)
Your message dated Sat, 09 Nov 2024 12:35:11 + with message-id and subject line Bug#1080660: fixed in lybniz 3.0.4-7 has caused the Debian Bug report #1080660, regarding Missing Build-Depends on python3-setuptools 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.) -- 1080660: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1080660 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: lybniz Version: 3.0.4-6 Severity: important User: debian-pyt...@lists.debian.org Usertags: dh-python-no-setuptools Tags: sid, trixie This package failed build from source when test-built against a version of dh-python without a python3-setuptools dependency. distutils is no longer part of the Python standard library, since 3.12. But a minimal version of it becomes available when the python3-setuptools package is installed. Please add a Build-Depends on python3-setuptools to your package, or migrate the package's build system away from setuptools/distutils. If you run into any difficulties, please raise them on debian-pyt...@lists.debian.org. This bug has been filed at "important" severity, as the change hasn't been made in dh-python yet, but this may be raised to RC before the trixie release. Thanks, Stefano --- End Message --- --- Begin Message --- Source: lybniz Source-Version: 3.0.4-7 Done: Alexandre Detiste We believe that the bug you reported is fixed in the latest version of lybniz, 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 1080...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Alexandre Detiste (supplier of updated lybniz 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: Sat, 09 Nov 2024 13:02:46 +0100 Source: lybniz Architecture: source Version: 3.0.4-7 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers Changed-By: Alexandre Detiste Closes: 1080660 Changes: lybniz (3.0.4-7) unstable; urgency=medium . * Team upload. * Add missing explicit dependency on python3-setuptools (Closes: #1080660) * Set Rules-Requires-Root: no Checksums-Sha1: 2d3e2bf430b9d861d2feb80ce03cb5d36852b32c 2108 lybniz_3.0.4-7.dsc f45b1ce56e8669a97bc5428c8b8b350f4f4b64d6 4668 lybniz_3.0.4-7.debian.tar.xz 3e2c16190b441d6d77cce19feff31efe111a8b34 12396 lybniz_3.0.4-7_source.buildinfo Checksums-Sha256: c7bf1d64dc8f0aaae7eb3d0ff56d6272cb5a2c4b29232786e9c05274bcb2e1ea 2108 lybniz_3.0.4-7.dsc ccc11aa38f79050cdc8f5a3bf878a95801d59e16087e38b06957609f6930cd56 4668 lybniz_3.0.4-7.debian.tar.xz d8a8f90e51bbfda3278b250bf1ea86160bf45a94873d977884082f0cf4f77363 12396 lybniz_3.0.4-7_source.buildinfo Files: ef0fd90a384dfaebd7376242390f3b6f 2108 math optional lybniz_3.0.4-7.dsc 95d22181ebe11b36df0df2c6591c9cb2 4668 math optional lybniz_3.0.4-7.debian.tar.xz 4e957f8b9dfbe13862bc45125cb72759 12396 math optional lybniz_3.0.4-7_source.buildinfo -BEGIN PGP SIGNATURE- iQJFBAEBCgAvFiEEj23hBDd/OxHnQXSHMfMURUShdBoFAmcvU2URHHRjaGV0QGRl Ymlhbi5vcmcACgkQMfMURUShdBrrwhAAhQTeV9BQxxsvlabPafn7PP+Yb1FJ1Rvd 74MZu+McSoUrEGZA5ROM9YCneJpVV9BIaJvqWlQOZFC74mxf79ncRpi67glQ+CMI 12d9NAzan0hN0TvOVH6dog0oa9VlD3zCUS9WGxUJaGSRJkqjeYNQK4U1Aihwj20f +CK3kCxWaTS3V9VVxgq9zHmp/dxF4BG8X3fCdCkfQwsPGrNqISwWQFqftxY5m+Qg 9b923vDCH9XOMAy0/TbdD6Xh700kduZMuK+LRL9G6LQM2PToWDPAlJIir+o41Sgr pMooMmZj/N6YE+2o1M1JZz4Ktczminb3fm5Wc/j5/DhBMrxrlmgGfgN+E4tV/dzP Sg3W5MHynVcwj3DNOPzPiuhjnpU0/APJU/EV20WbmbhMHdLxZSL+8nb4w8GetCBq KLQiugUhHxamchLCO15iMDwuP0sTbpaepElF1Kno3nSsW9HZ/NrOvosnTnEvobxy Q1E/+9bBnTpQowVBbjCP1tRYElbg40Izl+3FqIhavtv4QHnsHGjfQFPyYUP530Io WXumxCf4I9tpqUf5hc8f+Qmfr/o6MgsgtMnOCIjRIxn1yF8eHkD4N5B0UfEHgtGb e973T4hWCXpSrMi2GA5GmUyqjsCe+A/QkiIOwYnayRyzhc0eh5HTMIKmp0PMk61R ooqqrZDRLGE= =1nWl -END PGP SIGNATURE- pgpxzEPcJiObe.pgp Description: PGP signature --- End Message ---
Bug#1087098: marked as done (stac-check: Python SyntaxWarning)
Your message dated Sat, 09 Nov 2024 12:22:44 + with message-id and subject line Bug#1087098: fixed in stac-check 1.4.0+ds-2 has caused the Debian Bug report #1087098, regarding stac-check: Python SyntaxWarning 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.) -- 1087098: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1087098 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: stac-check Version: 1.4.0+ds-1 User: debian-pyt...@lists.debian.org Usertags: syntaxwarning Hi Maintainer The SyntaxWarning below were emitted when this package was tested with pipuarts[1]. Regards Graham [1] https://piuparts.debian.org/sid/source/s/stac-check.html Setting up python3-stac-check (1.4.0+ds-1) ... /usr/lib/python3/dist-packages/stac_check/logo.py:3: SyntaxWarning: invalid escape sequence '\ ' logo = """ --- End Message --- --- Begin Message --- Source: stac-check Source-Version: 1.4.0+ds-2 Done: Antonio Valentino We believe that the bug you reported is fixed in the latest version of stac-check, 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 1087...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Antonio Valentino (supplier of updated stac-check 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: Sat, 09 Nov 2024 11:46:58 + Source: stac-check Architecture: source Version: 1.4.0+ds-2 Distribution: unstable Urgency: medium Maintainer: Debian GIS Project Changed-By: Antonio Valentino Closes: 1087098 Changes: stac-check (1.4.0+ds-2) unstable; urgency=medium . * debian/patches: - New 0003-Fix-syntax-warning.patch (CLoses: #1087098). Checksums-Sha1: 42e02b0d1730b908f1d4c183debdd1e63bb81c7e 2779 stac-check_1.4.0+ds-2.dsc 8f86babe059fdba811b0d42c88cc866103b18156 8072 stac-check_1.4.0+ds-2.debian.tar.xz 4728fd66c2d571c8bb3cb79465868cedfad054ac 9079 stac-check_1.4.0+ds-2_amd64.buildinfo Checksums-Sha256: 5b43160f85d04debb896bbc52cd0d6a403ddf8d36e600825a8aeac859768fa72 2779 stac-check_1.4.0+ds-2.dsc 04bfcbe2dcd13205801c69647a04f1a7b558073a58cfc35a17431341825e29c7 8072 stac-check_1.4.0+ds-2.debian.tar.xz 736f6a4f885ddd37acd9c9dfb93670aae6aa69fcdd39a7632411aa0ac96cbae3 9079 stac-check_1.4.0+ds-2_amd64.buildinfo Files: bd9309fb7539d2105bafc5b2b7132dd6 2779 python optional stac-check_1.4.0+ds-2.dsc 0dd2cb5b9db192c2f5caa9a4d0fbeecc 8072 python optional stac-check_1.4.0+ds-2.debian.tar.xz 64077796ea9ae5506b44f6c45382ce86 9079 python optional stac-check_1.4.0+ds-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJRBAEBCgA7FiEEO3DyCaX/1okDxHLF6/SKslePmBIFAmcvTlYdHGFudG9uaW8u dmFsZW50aW5vQHRpc2NhbGkuaXQACgkQ6/SKslePmBIFohAAne7omMyVCgO+s+gP dWXSJXpoPFGyV8ldyaRL9wb21ed8yRTWLIC2Ibr/i80G0B0UtdAxqVwAtK0GDr2u FQxwG6vup2bVZk4kxSPilmn389554ofLHPoHGqfedxVa/GSCOL6WIgJlJhcKqJfL 7KOyfH43mY8lbRNWP8XMtPQRSubchDIrkWwDDxQLYvY/ZXrstTcPdYUETb/FmY6D H9+PQtZDi3+5r0o0lfADgrNvtxENz/AX2DYXUrQf3OjdntABwfsil4HSct8fbQCJ 0HbXVNoNdS1Eo+ABODscJdYE0Y/XFtQReIPocj3mgFxpzFpK6La5z/JaWykkZeyy oePBDa5SG4HYMEpKFbiHly8wDYNzsd5MKEF0sySCgsW77e/dAWHNtKwP4XKn3Xpy SlGJ82qOyVmXWI7hFimLgZGUJcmRzB6iiCVbYfdwiRUn4RMAJbatfpBtHjBpP7J3 dhIcOp+SxrHna5BIpctIXDfB9EoJRLOj/E9ex+ReaTc5Z3sncx2tcLQPTLMK1Qrh Bo/+tYBB7gaXUOq7yFny+phVJHdgOO62RxlZ2aZFlV+y9zTtj7O49x8eKVcOiFlR z6LepZpFzfgTm1hYvTlkIUJmt6kupdCmkSEXsbWTUnQ9nTcRE4bL5zV6t3P2iajG Czw42GkwNv06AZfyzlrQTdgvs3A= =l87l -END PGP SIGNATURE- pgps9gZS3OOYX.pgp Description: PGP signature --- End Message ---
Bug#1080893: marked as done (Missing Build-Depends on python3-setuptools)
Your message dated Sat, 09 Nov 2024 12:22:57 + with message-id and subject line Bug#1080893: fixed in xlsx2csv 1:0.8.3-1 has caused the Debian Bug report #1080893, regarding Missing Build-Depends on python3-setuptools 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.) -- 1080893: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1080893 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: xlsx2csv Version: 1:0.7.8-1 Severity: important User: debian-pyt...@lists.debian.org Usertags: dh-python-no-setuptools Tags: sid, trixie This package failed build from source when test-built against a version of dh-python without a python3-setuptools dependency. distutils is no longer part of the Python standard library, since 3.12. But a minimal version of it becomes available when the python3-setuptools package is installed. Please add a Build-Depends on python3-setuptools to your package, or migrate the package's build system away from setuptools/distutils. If you run into any difficulties, please raise them on debian-pyt...@lists.debian.org. This bug has been filed at "important" severity, as the change hasn't been made in dh-python yet, but this may be raised to RC before the trixie release. Thanks, Stefano --- End Message --- --- Begin Message --- Source: xlsx2csv Source-Version: 1:0.8.3-1 Done: Alexandre Detiste We believe that the bug you reported is fixed in the latest version of xlsx2csv, 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 1080...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Alexandre Detiste (supplier of updated xlsx2csv 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: Sat, 09 Nov 2024 12:02:58 +0100 Source: xlsx2csv Architecture: source Version: 1:0.8.3-1 Distribution: unstable Urgency: medium Maintainer: Debian Science Team Changed-By: Alexandre Detiste Closes: 1080893 Changes: xlsx2csv (1:0.8.3-1) unstable; urgency=medium . * Team Upload * New upstream version 0.8.3 (LP: #2061377) * Use dh-sequence-python3 * Set Rules-Requires-Root: no . [ Andrius Merkys ] * Add dependency on python3-setuptools (Closes: #1080893) * New upstream version 0.8.0 * Refresh python3.patch. * Adjust debian/copyright to relicensing to Expat. * Cleanup debian/rules. Checksums-Sha1: cbc611ffb80691b64e1f03e8ff01ddebe98bd755 2056 xlsx2csv_0.8.3-1.dsc f0db84651bb80d2dfc9179fdb6e5e574fbf09da5 215901 xlsx2csv_0.8.3.orig.tar.gz 56c3131087d4854315b05c33d982801d57a66192 4724 xlsx2csv_0.8.3-1.debian.tar.xz 81ff1293b620c6a0c71b528c6cd3a2befd667423 8156 xlsx2csv_0.8.3-1_source.buildinfo Checksums-Sha256: 8d5bd157c835aea380d7fc9c8bd36a23a32fb804a678fc12f83d6a3d5a80 2056 xlsx2csv_0.8.3-1.dsc d098b653ef35a6e4caa732168c06f74b8bd7f80593055dc17cfd8fcd88e49be7 215901 xlsx2csv_0.8.3.orig.tar.gz 92babe2e28215f217d4aa26fabe04f900d89ce7b3c2af288bb3a000edd2ca17c 4724 xlsx2csv_0.8.3-1.debian.tar.xz 98bf380724d53455bd3c1fc5fc62e009f6b8505fcb8b1857cfbc5f0ce38a12a6 8156 xlsx2csv_0.8.3-1_source.buildinfo Files: a5fc22f26d27802b9e60326c8d6e5384 2056 text optional xlsx2csv_0.8.3-1.dsc d5b6ddb3b24d1e0b6057139abd5516bb 215901 text optional xlsx2csv_0.8.3.orig.tar.gz d3b51ae8a08ff5f1b5de621306572256 4724 text optional xlsx2csv_0.8.3-1.debian.tar.xz 45069073ba9bdddb6cc2f842f86edeef 8156 text optional xlsx2csv_0.8.3-1_source.buildinfo -BEGIN PGP SIGNATURE- iQJEBAEBCgAvFiEEj23hBDd/OxHnQXSHMfMURUShdBoFAmcvTYYRHHRjaGV0QGRl Ymlhbi5vcmcACgkQMfMURUShdBr9MA/4lqv9zUmolYw2Hlmrs2F4Lddd2rkxN6/0 kbRDH8quBnRsWPNfGWOtD41Br9IU1rbmO5QYNpcGL1bJnpJ3H5EELXB7beCncRQ7 0oCN4/in6haqEqxgPYWydnA/NxUtvRKAOij/dC9XLMGI8L4P0vIHcRY/1wexo05I SYN1X9TbL7w+D0JsyRwL4Jbwo3asgaL2mcnVEM7o9cDYq1snQtvh5O2exu6J96Im 4HYRJB/A1WSlSVJiqZZHUZYjVmzelZbiTWrjnJWYv+/qraipDNJ7QzooH5QIsxUh W29x9lfTaNKt3J46plSQ0HPcAIXAn6zNtDxqQuL1Uf36/bwqC+Hudy7zAFCOmo9D eIlJZwtz+CbWmb9RsQAUnaThXm9vdb4EiYJh/3S3jk+YzW6DN1q36kgZx43+vhj5 ek9Mi1yQTOzvXMyQmGPZdgdCJxiwCd9f2nxduEoXfrd1CSSrRFojdLK/sQvndLv+ LCccXrpMJsoqPrFmQqvALvpLMRbbCa0xQxndxxCJbpx7mnq2uSBq/b4IfazKXYON 3HOidhw3OjVLc0n1UrAb7y+tWkmSeOdv5JmnvK4A8PVC
Bug#1087176: marked as done (webassets: Python SyntaxWarning)
Your message dated Sat, 09 Nov 2024 12:05:32 + with message-id and subject line Bug#1087176: fixed in webassets 3:2.0-0.3 has caused the Debian Bug report #1087176, regarding webassets: Python SyntaxWarning 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.) -- 1087176: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1087176 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: webassets Version: 3:2.0-0.2 User: debian-pyt...@lists.debian.org Usertags: syntaxwarning Hi Maintainer The SyntaxWarning below were emitted when this package was tested with pipuarts[1]. Regards Graham [1] https://piuparts.debian.org/sid/source/w/webassets.html Setting up python3-webassets (3:2.0-0.2) ... /usr/lib/python3/dist-packages/webassets/filter/__init__.py:42: SyntaxWarning: invalid escape sequence '\,' """Split while allowing escaping. /usr/lib/python3/dist-packages/webassets/filter/replace.py:9: SyntaxWarning: invalid escape sequence '\s' """ --- End Message --- --- Begin Message --- Source: webassets Source-Version: 3:2.0-0.3 Done: Alexandre Detiste We believe that the bug you reported is fixed in the latest version of webassets, 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 1087...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Alexandre Detiste (supplier of updated webassets 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: Sat, 09 Nov 2024 12:32:46 +0100 Source: webassets Architecture: source Version: 3:2.0-0.3 Distribution: unstable Urgency: medium Maintainer: Agustin Henze Changed-By: Alexandre Detiste Closes: 1087176 Changes: webassets (3:2.0-0.3) unstable; urgency=medium . * Non-maintainer upload. * Fix SyntaxWarning (Closes: #1087176) Checksums-Sha1: 2cbb3382f6e184b32abc7faadf9d9162df2b63a0 2103 webassets_2.0-0.3.dsc 03888e847e5b47948091f4207ff661c2a633ca71 14464 webassets_2.0-0.3.debian.tar.xz ae87c8094e3a0abec5a2b1b37090cf2d98b7e8fd 9059 webassets_2.0-0.3_source.buildinfo Checksums-Sha256: 84e6ac09b8083f71f9e5e442e8b939854a640cf1e6e1e8bf21762c236b30218c 2103 webassets_2.0-0.3.dsc 27322459c475072ae8447354c39ea9f22435ffe886321022eb955b4995635f2e 14464 webassets_2.0-0.3.debian.tar.xz 0ce0e79cc8a803a694488de4ed069b9e75434b4823a09b6454ff0aa880eb9a4b 9059 webassets_2.0-0.3_source.buildinfo Files: 83b10afd46d2970ac09c8cc135613a9d 2103 python optional webassets_2.0-0.3.dsc d0b43941e0e93b4fc84b7f65225b4afe 14464 python optional webassets_2.0-0.3.debian.tar.xz c12970d6805f85d5534c99d18cbe91ed 9059 python optional webassets_2.0-0.3_source.buildinfo -BEGIN PGP SIGNATURE- iQJFBAEBCgAvFiEEj23hBDd/OxHnQXSHMfMURUShdBoFAmcvS54RHHRjaGV0QGRl Ymlhbi5vcmcACgkQMfMURUShdBr1Mg//WBRPgc+fxPaVogMhX3do/b7MqY37ViIq viCnBh8CRoJcrDeftOk/nON3MqTi4jD41RoobNrnF+F+QpuCSR0tD+3piiL0Q5cB 9Zog1oOQR1n7OkO9iZ6IrLDxFJmC85VCIck4gWlQlC5WmZmrXMk4XhT6dK/zOQMb XAhseis84Qqj4ckEkWWB3ia15GZqJAlocikov75FEBx9LGt24JtydLGKamPmYH6p ulNgrTYx23JBw5w8EsgClPx8Fr/GgT9K+rTX9qvIxamDiKbs/z2S3g5yuWRljxXk oHZihNUhLzFfIIm0HI78BL2YiRP/pLLj7qhdXt/UX9/IxafGZ1FLX/ePR+21yd0+ SzmePQKodXtbyaj1KpfPEROT3CSLmlLZHpKoFBshZXeu9ArCyLuUjH19S3xonu0h Vz3cPbFwlZmtZJZ+OrTvFw5418KPMM1OSrV8+VdJutrfAno4JEjSVJuyAGFBOsNU 0kKcUj7K/DudefcHsY97I+YltMoueKHwLRiW53fP6RwkdWyTTECufPjmYcUVwv3H QVKxkZX7U76by++b2MVNohNO/I/AEb+1kpvrRjOuIqmTw43wiIJeNU6t07CumDL+ FnmdmycyVALPQq5wtWX7Vsvcxcqn+tJY0LQGhRzaqI16vYY+7yJwtE1KVeh4A/R3 0/EyfMEin60= =Z5n0 -END PGP SIGNATURE- pgpdxQWiJKgMI.pgp Description: PGP signature --- End Message ---
Bug#1084904: marked as done (examl: Please rebuild against mpich rather than openmpi, or default mpi)
Your message dated Sat, 09 Nov 2024 12:04:50 + with message-id and subject line Bug#1084904: fixed in examl 3.0.22-6 has caused the Debian Bug report #1084904, regarding examl: Please rebuild against mpich rather than openmpi, or default mpi 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.) -- 1084904: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1084904 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: examl Version: 3.0.22-5 Severity: normal As part of the openmpi transition to 64-bit only, examl is a blocker. In a test build, examl will build against mpich on 32-bit systems. Please build against either libmpich-dev or mpi-default-dev (which will use openmpi ofr 64--bit systems) Thanks Alastair -- System Information: Debian Release: 12.7 APT prefers stable-security APT policy: (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-25-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_IE.UTF-8), LANGUAGE=en_IE:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled --- End Message --- --- Begin Message --- Source: examl Source-Version: 3.0.22-6 Done: Étienne Mollier We believe that the bug you reported is fixed in the latest version of examl, 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 1084...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Étienne Mollier (supplier of updated examl 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: Sat, 09 Nov 2024 12:07:58 +0100 Source: examl Architecture: source Version: 3.0.22-6 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team Changed-By: Étienne Mollier Closes: 1084904 1086909 Changes: examl (3.0.22-6) unstable; urgency=medium . * d/control: migrate to mpi-default-* (Closes: #1084904, #1086909) * d/patches/*: normalize dep3 header, notably Last-Update timestamp. * d/control: add myself to uploaders. Checksums-Sha1: bcdaabc79b977b4b0693f32f82130187945b9f10 2169 examl_3.0.22-6.dsc 2eb4eb55b5776b859bfd608cb3b1a54e02a29453 27400 examl_3.0.22-6.debian.tar.xz Checksums-Sha256: 1809b6d55208edd61267a6e0b1af2ddd721a94bfc2517981690f3f4b74fe99a4 2169 examl_3.0.22-6.dsc fb9f88cb18b9432cc189ede0992814a8e7fefc23be08c424dd493d45516ad8a2 27400 examl_3.0.22-6.debian.tar.xz Files: 83b6e87792449d6495a00dfdad8743ae 2169 science optional examl_3.0.22-6.dsc 7600ccaf1fc6adee79b9d8ba1faa4019 27400 science optional examl_3.0.22-6.debian.tar.xz -BEGIN PGP SIGNATURE- iQJIBAEBCgAyFiEEj5GyJ8fW8rGUjII2eTz2fo8NEdoFAmcvTCUUHGVtb2xsaWVy QGRlYmlhbi5vcmcACgkQeTz2fo8NEdqhLQ/+NddgaJ6YFS6cfG45Y6KsmO1YrY3b J+3Amhe1xZaae+cYz7QVBPuB4S9ZPc7nlG4Ohh+YN3vJ+6aD71TKHTwcT96P7GNz a8kBfgxfpG/6jg9oNC+F7yBDCgaz9jH4mvKl7ODHomgw5F0Ps1KsYIgvKHpkfqIi v1mUrENZzXJ1L7W8gzHtv+4LMnn7AbMW90GpCmJNXc3JgJ/5KXoYMbUCyLGvBlXe LL9gWq6iIJd1Sb8P9DRXBykcMElW16U6FZjmolVYt/xn6yUcXN4fc8+03PwnXJdm Iucq9WJ4stkdeB/inoJA2aB8de1zICzR9B9udldjKBIvfnNOso24DNI4iFLCrVP2 +PkNsEOlf+N8aa6rZGoSYMlfnsJXZLO2Qi85mNuQ/pAL1uLdMeL+sfzwJ1OWPVuf hm/6InbcWZZBexmMf1fh5gyo9rlvwdVIVNMK89Hmy8Oe+FLwpU3C2Wbm9LYUh5yU GafI1dZ+SHznKa9nwo1QQaKzgtalI7n1gDju72XUvRxpVsjxE1mEyV0uZMgiS+RI 1si0Kmdj21H1wjT+rbyle/xF6igZEXR7mmoeH9mb/LRRAI4re1bqFC8PVjbJPL1S 7YTG+tuMKwCD8bAuYTXKNDrHcsJoGLB8/GYIMiM2+A0LpzfiSN7h0r7HKISqkj6W mOp9hUbRIIhy4sM= =UD4d -END PGP SIGNATURE- pgpxd0UQaPjON.pgp Description: PGP signature --- End Message ---
Bug#1086909: marked as done (examl: depends on openmpi on 32-bit architectures)
Your message dated Sat, 09 Nov 2024 12:04:51 + with message-id and subject line Bug#1086909: fixed in examl 3.0.22-6 has caused the Debian Bug report #1086909, regarding examl: depends on openmpi on 32-bit architectures 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.) -- 1086909: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1086909 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: examl Severity: serious Hi, examl depends on openmpi on 32-bit architectures, which has been removed in openmpi 5. Thus this package needs to stop depending on it on those architectures. There are a couple of options: - build-dep on mpi-default-dev instead of openmpi-dev, so that the MPICH implementation can be used on those architectures. - remove the package from 32-bit architectures (armel, armhf and i386) by filing an RM bug against ftp.debian.org See [1] for the transition bug and [2] for the tracker. Cheers, Emilio [1] https://bugs.debian.org/1064810 [2] https://release.debian.org/transitions/html/openmpi-rm32.html --- End Message --- --- Begin Message --- Source: examl Source-Version: 3.0.22-6 Done: Étienne Mollier We believe that the bug you reported is fixed in the latest version of examl, 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 1086...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Étienne Mollier (supplier of updated examl 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: Sat, 09 Nov 2024 12:07:58 +0100 Source: examl Architecture: source Version: 3.0.22-6 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team Changed-By: Étienne Mollier Closes: 1084904 1086909 Changes: examl (3.0.22-6) unstable; urgency=medium . * d/control: migrate to mpi-default-* (Closes: #1084904, #1086909) * d/patches/*: normalize dep3 header, notably Last-Update timestamp. * d/control: add myself to uploaders. Checksums-Sha1: bcdaabc79b977b4b0693f32f82130187945b9f10 2169 examl_3.0.22-6.dsc 2eb4eb55b5776b859bfd608cb3b1a54e02a29453 27400 examl_3.0.22-6.debian.tar.xz Checksums-Sha256: 1809b6d55208edd61267a6e0b1af2ddd721a94bfc2517981690f3f4b74fe99a4 2169 examl_3.0.22-6.dsc fb9f88cb18b9432cc189ede0992814a8e7fefc23be08c424dd493d45516ad8a2 27400 examl_3.0.22-6.debian.tar.xz Files: 83b6e87792449d6495a00dfdad8743ae 2169 science optional examl_3.0.22-6.dsc 7600ccaf1fc6adee79b9d8ba1faa4019 27400 science optional examl_3.0.22-6.debian.tar.xz -BEGIN PGP SIGNATURE- iQJIBAEBCgAyFiEEj5GyJ8fW8rGUjII2eTz2fo8NEdoFAmcvTCUUHGVtb2xsaWVy QGRlYmlhbi5vcmcACgkQeTz2fo8NEdqhLQ/+NddgaJ6YFS6cfG45Y6KsmO1YrY3b J+3Amhe1xZaae+cYz7QVBPuB4S9ZPc7nlG4Ohh+YN3vJ+6aD71TKHTwcT96P7GNz a8kBfgxfpG/6jg9oNC+F7yBDCgaz9jH4mvKl7ODHomgw5F0Ps1KsYIgvKHpkfqIi v1mUrENZzXJ1L7W8gzHtv+4LMnn7AbMW90GpCmJNXc3JgJ/5KXoYMbUCyLGvBlXe LL9gWq6iIJd1Sb8P9DRXBykcMElW16U6FZjmolVYt/xn6yUcXN4fc8+03PwnXJdm Iucq9WJ4stkdeB/inoJA2aB8de1zICzR9B9udldjKBIvfnNOso24DNI4iFLCrVP2 +PkNsEOlf+N8aa6rZGoSYMlfnsJXZLO2Qi85mNuQ/pAL1uLdMeL+sfzwJ1OWPVuf hm/6InbcWZZBexmMf1fh5gyo9rlvwdVIVNMK89Hmy8Oe+FLwpU3C2Wbm9LYUh5yU GafI1dZ+SHznKa9nwo1QQaKzgtalI7n1gDju72XUvRxpVsjxE1mEyV0uZMgiS+RI 1si0Kmdj21H1wjT+rbyle/xF6igZEXR7mmoeH9mb/LRRAI4re1bqFC8PVjbJPL1S 7YTG+tuMKwCD8bAuYTXKNDrHcsJoGLB8/GYIMiM2+A0LpzfiSN7h0r7HKISqkj6W mOp9hUbRIIhy4sM= =UD4d -END PGP SIGNATURE- pgpoSs5JpOCLU.pgp Description: PGP signature --- End Message ---
Bug#1086908: marked as done (murasaki: depends on openmpi on 32-bit architectures)
Your message dated Sat, 09 Nov 2024 12:05:23 +
with message-id
and subject line Bug#1086908: fixed in murasaki 1.68.6-14
has caused the Debian Bug report #1086908,
regarding murasaki: depends on openmpi on 32-bit architectures
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.)
--
1086908: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1086908
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: murasaki
Severity: serious
Hi,
murasaki depends on openmpi on 32-bit architectures, which has been
removed in openmpi 5. Thus this package needs to stop depending on it
on those architectures.
There are a couple of options:
- build-dep on mpi-default-dev instead of openmpi-dev, so that the
MPICH implementation can be used on those architectures.
- remove the package from 32-bit architectures (armel, armhf and i386)
by filing an RM bug against ftp.debian.org
See [1] for the transition bug and [2] for the tracker.
Cheers,
Emilio
[1] https://bugs.debian.org/1064810
[2] https://release.debian.org/transitions/html/openmpi-rm32.html
--- End Message ---
--- Begin Message ---
Source: murasaki
Source-Version: 1.68.6-14
Done: Étienne Mollier
We believe that the bug you reported is fixed in the latest version of
murasaki, 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 1086...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Étienne Mollier (supplier of updated murasaki 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: Sat, 09 Nov 2024 11:58:11 +0100
Source: murasaki
Architecture: source
Version: 1.68.6-14
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team
Changed-By: Étienne Mollier
Closes: 1086908
Changes:
murasaki (1.68.6-14) unstable; urgency=medium
.
* Team upload.
* d/{,t}/control: migrate to mpi-default-*. (Closes: #1086908)
* d/control: declare compliance to standards version 4.7.0.
* d/patches/*: normalize dep3 headers.
Most of the changes are normalisation of the Last-Update timestamp.
* d/s/lintian-overrides: delete: override is now unused.
Checksums-Sha1:
05b31cdb729ddb129db337b62c1b61234615d868 2910 murasaki_1.68.6-14.dsc
9403b175b189c614ea8a6347d0a4c3a50849806e 11224 murasaki_1.68.6-14.debian.tar.xz
Checksums-Sha256:
347d5047685767a2473200d86ef66c722ff8fa8f0e41bdd1716fb9dfe85c4342 2910
murasaki_1.68.6-14.dsc
0237d35c8703611985593569214901098fe7d98e2281ccdbfe4e27962a59f7f8 11224
murasaki_1.68.6-14.debian.tar.xz
Files:
916530e14199135516d9a78fa8ae2656 2910 science optional murasaki_1.68.6-14.dsc
96c84644f65aef0fcf53bc954300ab92 11224 science optional
murasaki_1.68.6-14.debian.tar.xz
-BEGIN PGP SIGNATURE-
iQJIBAEBCgAyFiEEj5GyJ8fW8rGUjII2eTz2fo8NEdoFAmcvS7IUHGVtb2xsaWVy
QGRlYmlhbi5vcmcACgkQeTz2fo8NEdr8xBAAylSNw3PtHGRmD65WRrM81HBVq28g
nWkktKWuzehY/Dpu3o83crdIuu2UR7aiwtQlSyMMX/2AMg/3I3Qr3P9b+GKwJcEP
cibMKEUQcw/STOgb8L5f2iI8oE5WiOv/vHn1rMF+9HFgmNQpGIT5Z9vQB70t53TI
FmjcNPcBrHQQhe0Z6OEX+FgvyeiiaVs3a1peIbRssYb76E88nOJ+IPwq8n/ZEJDF
eFbYV9vb64ndZ2DaEeFQVpELBzSMUI6Q4WTz5eFRLt9X8ib0zhdiWjtCqiX0YMPH
1fomXHnuYrAOgpJWO1aHxMrzGdzGbaHDTOLQGxYo1LpIC68Zx3As/BXKTBN7jAIl
EvkoHBCyEZyesxqhw0RI1GLRqaZVjcUQAnZCf4Gz2MF3xaYcSMKwXEsMlT7A/RQ1
Ifd+GbgY9GX+h1+8/MJagQG4EOjeQCBwI8gEl6msSbp0QUsq3s/7plqg7wFSnSJ6
4nE9BVM6+R2V3O1+yBoKsZz2W4j5Kq6Swute/T2KIHdqYZ2kYaJF+u8+kA67P0JT
ekiD5v44ucvvXGDwRXAaJPplfK7MYyBuxTMxjbrxzg+z6TOCbSJXvMPOViWUAWi1
NwqvMHueMDgBlYUar3HkwPCn6BxtHcz1X6JS002GCUqJJZjR5+FqCwPOq8mDg0gv
+svWeuylq2M6A+A=
=rv/9
-END PGP SIGNATURE-
pgp70mqEWCgAm.pgp
Description: PGP signature
--- End Message ---
Bug#1083354: marked as done (deluge: (build-)depends on deprecated module python3-pkg-resources)
Your message dated Sat, 09 Nov 2024 11:49:20 + with message-id and subject line Bug#1083354: fixed in deluge 2.1.2~dev0+20240910-1 has caused the Debian Bug report #1083354, regarding deluge: (build-)depends on deprecated module python3-pkg-resources 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.) -- 1083354: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1083354 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:deluge Version: 2.1.2~dev0+20240219-3 Severity: normal Tags: sid trixie User: debian-pyt...@lists.debian.org Usertags: pkg-resources-deprecation [This bug is targeted to the upcoming trixie release] The package build-depends or depends on python3-pkg-resources, which is deprecated upstream. Details can be found at https://setuptools.pypa.io/en/latest/pkg_resources.html Use of pkg_resources is deprecated in favor of importlib.resources, importlib.metadata and their backports (importlib_resources, importlib_metadata). Some useful APIs are also provided by packaging (e.g. requirements and version parsing). Users should refrain from new usage of pkg_resources and should work to port to importlib-based solutions. Python 3.12 in unstable provides both importlib_resources and importlib_metadata, so no additional dependencies on those packages are needed. --- End Message --- --- Begin Message --- Source: deluge Source-Version: 2.1.2~dev0+20240910-1 Done: Daniel Baumann We believe that the bug you reported is fixed in the latest version of deluge, 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 1083...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Daniel Baumann (supplier of updated deluge 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: Sat, 09 Nov 2024 12:37:26 +0100 Source: deluge Architecture: source Version: 2.1.2~dev0+20240910-1 Distribution: sid Urgency: medium Maintainer: Daniel Baumann Changed-By: Daniel Baumann Closes: 1083354 Changes: deluge (2.1.2~dev0+20240910-1) sid; urgency=medium . * Uploading to sid. * Merging upstream version 2.1.2~dev0+20240910. * Removing manual python3-pkg-resources depends (Closes: #1083354). Checksums-Sha1: 653b75e4a84b8c49bf5b08bb7290930e05597eb0 2355 deluge_2.1.2~dev0+20240910-1.dsc 2ccb61043b3864c24789da7e3cea4f29d15c5cc1 2354656 deluge_2.1.2~dev0+20240910.orig.tar.xz 606bda07debae2ebffa026d13e8ea3b066e94f0c 25128 deluge_2.1.2~dev0+20240910-1.debian.tar.xz fb7fb91954de01f8a0de38f7f5e6faa200467214 9412 deluge_2.1.2~dev0+20240910-1_amd64.buildinfo Checksums-Sha256: 312b0149b7ff1b3dd3682ef8f2c152d7165a759af0ac11b54794aaf2ae74e450 2355 deluge_2.1.2~dev0+20240910-1.dsc f80afc142250052651fc702ae98ab6de7b6384885030caa9384f4d94667f2b37 2354656 deluge_2.1.2~dev0+20240910.orig.tar.xz b2d0453580e325d40cc6997690b68ba40f1a81a054c573d07dc527141c8ea7eb 25128 deluge_2.1.2~dev0+20240910-1.debian.tar.xz 8b7613d6a8d14de14fc34faf6f77c9efe9fca3aef665c86280a57151873e672e 9412 deluge_2.1.2~dev0+20240910-1_amd64.buildinfo Files: 11c433ab58f119ff631b5b65cfbc3f82 2355 net optional deluge_2.1.2~dev0+20240910-1.dsc 5449806a588a7261fe203e4380194181 2354656 net optional deluge_2.1.2~dev0+20240910.orig.tar.xz 25ba29506d395b0d4e504ff833f17483 25128 net optional deluge_2.1.2~dev0+20240910-1.debian.tar.xz 5df7698826167959cf3ace404ea89ac6 9412 net optional deluge_2.1.2~dev0+20240910-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEgTbtJcfWfpLHSkKSVc8b+YaruccFAmcvSbUACgkQVc8b+Yar uceyVRAA1s/9nbug7VpaxIGifTKieGJ0m8qH4AZQRvN3/N2X4HkR10quVG/BGbHW oALpa16DgCaD5E0vGgz1nWUL3S52FDBFFMurLCGFPX2hA2ICWLcbfBDokHzr9M9l m2rF5lYmrlZeZwJx0FuuJWMu3zzNpqHW7H1k3WKgdvAVbuUAChBNcH7DbgygAyAW nt+tClN/k0kbfyRUgsg6qByPS9ozO+jOqS4t49V2j7VyXqOHH2+ZE6TkIMTXtoxt zgSLQkxqwYjMToR288iqA3VXf73LUMyL0Fj79LvdRGIVgqoWqInJ4p1MSB28OJMm TrnZgXMlTR3STBoyGhKXoeZiAZ6HEYHmQN7MmkFK42SReVoLRcadVIvrbiixKoWc SeZBaBXhK8OLNDNkDpxeeUN+AElH/K19iieqWQtWLJIsQveDEKMqkHvFdSCs9QWf XP+7ACiZXft2Z+ar3SRUbu28uXXp74mou3Hub1rhg6PxaXecDhyKXs0p02PCuHjP buoL1LSvA/Vw/nY7/IvJ2lAcXcSWhs0cev6FYfBIm+93oFtmdayseHWN5F4+lCST
Bug#1086532: marked as done (libzbar0t64: upgrade blocked due to bad Recommends)
Your message dated Sat, 09 Nov 2024 11:36:02 + with message-id and subject line Bug#1086532: fixed in zbar 0.23.93-6 has caused the Debian Bug report #1086532, regarding libzbar0t64: upgrade blocked due to bad Recommends 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.) -- 1086532: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1086532 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libzbar0t64 Version: 0.23.93-5+b2 Severity: serious libzbar0t64 0.23.93-5+b2 has Recommends: libmagickcore-6.q16-7-extra instead of Recommends: libmagickcore-7.q16-10-extra This blocks the upgrade to imagemagick 7 due to the unsatisfied Recommends. -- System Information: Debian Release: trixie/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable-debug'), (500, 'proposed-updates-debug'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.7.12-amd64 (SMP w/16 CPU threads; PREEMPT) Kernel taint flags: TAINT_WARN Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libzbar0t64 depends on: ii libc62.40-3 ii libdbus-1-3 1.14.10-6 ii libjpeg62-turbo 1:2.1.5-3+b1 ii libv4l-0t64 1.28.1-1 ii libx11-6 2:1.8.7-1+b2 Versions of packages libzbar0t64 recommends: ii libmagickcore-6.q16-7-extra 8:6.9.13.12+dfsg1-1+b1 libzbar0t64 suggests no packages. -- no debconf information -- Vincent Lefèvre - Web: <https://www.vinc17.net/> 100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/> Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon) --- End Message --- --- Begin Message --- Source: zbar Source-Version: 0.23.93-6 Done: Daniel Baumann We believe that the bug you reported is fixed in the latest version of zbar, 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 1086...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Daniel Baumann (supplier of updated zbar 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: Sat, 09 Nov 2024 12:01:25 +0100 Source: zbar Architecture: source Version: 0.23.93-6 Distribution: sid Urgency: medium Maintainer: Daniel Baumann Changed-By: Daniel Baumann Closes: 1086532 Changes: zbar (0.23.93-6) sid; urgency=medium . * Uploading to sid. * Updating recommends on imagemagick (Closes: #1086532). Checksums-Sha1: dd1353fb7214e3a63ed54582cb18e352187e8d93 2901 zbar_0.23.93-6.dsc 4ab895bb720ef3413e726a664cb1467e666ec897 13368 zbar_0.23.93-6.debian.tar.xz c164fbc463550439920181a9b20db6783b52115d 24311 zbar_0.23.93-6_amd64.buildinfo Checksums-Sha256: 4ba07b5a59ac8e315b1750b969167a3f69d7d7a20f96b1e404ddf4204960985b 2901 zbar_0.23.93-6.dsc de89f1cfc0097965bf8968084d4480141ce35e225866d8de2967da02cd65 13368 zbar_0.23.93-6.debian.tar.xz 15c0afc16ed38a79aff9ab586af2f88cce0fb3d08e1c53be6ab06af99295 24311 zbar_0.23.93-6_amd64.buildinfo Files: 6d1b46524048edb3300ae6fa6eda81cf 2901 libs optional zbar_0.23.93-6.dsc f03ddd9fcf23f191181918f71a6aa9cc 13368 libs optional zbar_0.23.93-6.debian.tar.xz 5c151b1f34f64db0487bd4e00fff6c77 24311 libs optional zbar_0.23.93-6_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEgTbtJcfWfpLHSkKSVc8b+YaruccFAmcvQ0sACgkQVc8b+Yar ucclDhAAk/rx4ovg2YhGHNAyhd/Ygkv/vmw/r07E+baa1yoXiUG/JMEBfjxwIoz7 lLVAcyfNZW+DSMOW3StZQ0Rm6xss6JGY0pj5kt+vJDf0rKJM4ntQh274w0WxVXnG OOlheqGFa/c/Py5fk1+xj4GAGGK/bd1yZF0Fo1ir+MZ6sLAr8yHRhTM7zWEX4MjP 1pcCKUt9vHbot/Nm3gbsA2XfVsfjENTq/WEjXk/6cvbBwiHgU/HHrffPTFYOS/PM 8dv3XpOk++Fr3TF/glCCZTOEQXVji94VoZRhhsHI5FWumoFyvT0G3J2gByyfb8zp fT0wc/NvE1CXVzQxQF2TX0FytK1koENhc+yYNmgP0FdhMW+gnnZWgBgtB1wUj54J 0E7LS38TFxX3gCv4saf+IPkDIikJ1pNUC8o7EEzc+34R6XHuFYnvV/SEM1G9l+DT jiV9FKHL0s0sv5Ye4V4Itpe5+6MUhZSHyxCmZHSz4HaXfwvRlzaUJVMp6TIwqPnt mjUWg9Mgwugts9Sl3ynQ6SS/R2s
Bug#1083497: marked as done (mycli: (build-)depends on deprecated module python3-pkg-resources)
Your message dated Sat, 09 Nov 2024 11:35:40 + with message-id and subject line Bug#1083497: fixed in mycli 1.27.2-2 has caused the Debian Bug report #1083497, regarding mycli: (build-)depends on deprecated module python3-pkg-resources 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.) -- 1083497: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1083497 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:mycli Version: 1.27.2-1 Severity: normal Tags: sid trixie User: debian-pyt...@lists.debian.org Usertags: pkg-resources-deprecation [This bug is targeted to the upcoming trixie release] The package build-depends or depends on python3-pkg-resources, which is deprecated upstream. Details can be found at https://setuptools.pypa.io/en/latest/pkg_resources.html Use of pkg_resources is deprecated in favor of importlib.resources, importlib.metadata and their backports (importlib_resources, importlib_metadata). Some useful APIs are also provided by packaging (e.g. requirements and version parsing). Users should refrain from new usage of pkg_resources and should work to port to importlib-based solutions. Python 3.12 in unstable provides both importlib_resources and importlib_metadata, so no additional dependencies on those packages are needed. --- End Message --- --- Begin Message --- Source: mycli Source-Version: 1.27.2-2 Done: Daniel Baumann We believe that the bug you reported is fixed in the latest version of mycli, 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 1083...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Daniel Baumann (supplier of updated mycli 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: Sat, 09 Nov 2024 12:20:20 +0100 Source: mycli Architecture: source Version: 1.27.2-2 Distribution: sid Urgency: medium Maintainer: Daniel Baumann Changed-By: Daniel Baumann Closes: 1083497 Changes: mycli (1.27.2-2) sid; urgency=medium . * Uploading to sid. * Removing manual python3-pkg-resources depends (Closes: #1083497). Checksums-Sha1: 82ab3a918db373108d9ea07c38b6ce7fb8fa75e1 1964 mycli_1.27.2-2.dsc 781c23ed483da8961df5edc663995c7ae56e3a1e 4280 mycli_1.27.2-2.debian.tar.xz 2f8bd0faecb6e28630ea6758979d381818aac671 6733 mycli_1.27.2-2_amd64.buildinfo Checksums-Sha256: 60481128f3683b4d7a1b0fa25fd8656849b02f5cd7b9166150340d368d0b6a46 1964 mycli_1.27.2-2.dsc 3e73585d2a93a4975af3e687b58025c2684b9878c24fe9a5e1ac7aaa7db3bc24 4280 mycli_1.27.2-2.debian.tar.xz c084edb07fc57e99083098d8bdff1fc0752449759c045df682a494e97f6e9a6e 6733 mycli_1.27.2-2_amd64.buildinfo Files: f537176bd5c86dbb80de6cd9343ba21a 1964 database optional mycli_1.27.2-2.dsc afdbbca8ee4a835b8b278500cdc8bd5d 4280 database optional mycli_1.27.2-2.debian.tar.xz bdde1fbfb43a3d3ccaf8497d55ab5c81 6733 database optional mycli_1.27.2-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEgTbtJcfWfpLHSkKSVc8b+YaruccFAmcvRZ8ACgkQVc8b+Yar ucfYcw//ex0MmolslH6PWBzFPMaH8rvCZrppLsBjCD6smdLtc9TcjpfLwcsamXaO XHFzqxwnOfv86TXDNjpqdGD/CsGpkwVyq2RtKFqVrZdppvOiveYoqjeSrqtnAxZ5 y3SvYVGmpd34broPfYYSmVx0L2C1ADlEm+mHWDijgWlzQLxuxT+sQ4J9q3Kl6P3W IjLLEi0KijIixMq1uyUNW5Mxm0brku4Xw7wBkT9KMLmSlzp5xoPgxAoaoJsvoTXh NsUw7VWpwxD6Sl1rjkksE5ticgKueMuSqmQFG25uQPUKDxUmEm9cyTvSm4j7LCQe d/seKK02QjLOCp5/v+aVGpfW4RsFf7ULHXcGgBQfvq3Dc+DDIz8Jn06KRC9shyqF 8AqRQ+ZEv13cJ5Ch6WdHza/PX5z+2XY8zXqRb4q6MuNQSJFN/QYAxGjz4z6GDm1A WV5c0NDmCY97EihXtUKpUM9EczfHgCnCrcgYucu7+9fnIxnhjR1HiwYBi/9Ivsiq LAVhywD0YLGimxEohMY/G1pbaUtRwiZzf5eXsF7vos/MO9wAVR8DQ9OXVhVLs3Ad klspt6SKGJqT1g2XdZuMsMBJzvmsuifD9GHTlsuG4xdFjxIzJAps9QJahJyddqG/ 88DsbY2LLiq+2i8v3UrmX0o39OdjYFq+oNZ1bzIVad0KwFcVAR0= =vls2 -END PGP SIGNATURE- pgpo6cPohIlN2.pgp Description: PGP signature --- End Message ---
Bug#1083539: marked as done (pgcli: (build-)depends on deprecated module python3-pkg-resources)
Your message dated Sat, 09 Nov 2024 11:35:53 + with message-id and subject line Bug#1083539: fixed in pgcli 4.1.0-3 has caused the Debian Bug report #1083539, regarding pgcli: (build-)depends on deprecated module python3-pkg-resources 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.) -- 1083539: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1083539 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:pgcli Version: 4.1.0-2 Severity: normal Tags: sid trixie User: debian-pyt...@lists.debian.org Usertags: pkg-resources-deprecation [This bug is targeted to the upcoming trixie release] The package build-depends or depends on python3-pkg-resources, which is deprecated upstream. Details can be found at https://setuptools.pypa.io/en/latest/pkg_resources.html Use of pkg_resources is deprecated in favor of importlib.resources, importlib.metadata and their backports (importlib_resources, importlib_metadata). Some useful APIs are also provided by packaging (e.g. requirements and version parsing). Users should refrain from new usage of pkg_resources and should work to port to importlib-based solutions. Python 3.12 in unstable provides both importlib_resources and importlib_metadata, so no additional dependencies on those packages are needed. --- End Message --- --- Begin Message --- Source: pgcli Source-Version: 4.1.0-3 Done: Daniel Baumann We believe that the bug you reported is fixed in the latest version of pgcli, 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 1083...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Daniel Baumann (supplier of updated pgcli 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: Sat, 09 Nov 2024 12:18:56 +0100 Source: pgcli Architecture: source Version: 4.1.0-3 Distribution: sid Urgency: medium Maintainer: Daniel Baumann Changed-By: Daniel Baumann Closes: 1083539 Changes: pgcli (4.1.0-3) sid; urgency=medium . * Uploading to sid. * Removing manual python3-pkg-resources depends (Closes: #1083539). Checksums-Sha1: 36675f6d5bfd971c6d14975264a381304fe4ae52 2015 pgcli_4.1.0-3.dsc ec99ef4df8ed89d979e65b673e8a2acfadd84773 4448 pgcli_4.1.0-3.debian.tar.xz 80ca8d0ebca9c777fbd80bc80c600d22f00cdabd 7099 pgcli_4.1.0-3_amd64.buildinfo Checksums-Sha256: 8e8f4e63b5d303a5ee67dd46fb6e99cf74f5dfa817168d94d078bbd3cdf097c9 2015 pgcli_4.1.0-3.dsc 9993e5212aac580567deb7671b44391c9627c9d8316ee69a8f5a4f6e873388bb 4448 pgcli_4.1.0-3.debian.tar.xz 499eba4b13591f7a38dd0becd93947944c2b2a2a9952bb91412f8c1275931cc9 7099 pgcli_4.1.0-3_amd64.buildinfo Files: dc0212fe94db2691ab7a160a188da5bb 2015 database optional pgcli_4.1.0-3.dsc 7a3872f29ae20388ba5a56660853b8c9 4448 database optional pgcli_4.1.0-3.debian.tar.xz 24d552b5f331b204ed98308cadd9ea3c 7099 database optional pgcli_4.1.0-3_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEgTbtJcfWfpLHSkKSVc8b+YaruccFAmcvRVcACgkQVc8b+Yar ucd2ERAAiDTydnRsSDeL9MM098i87AeMQlblcPy4BXV3huAf9SoNbzS/QCvdXZtt BlWByh3oKw3xvgDi8a/1rlfXXeMwG2S9211ytUMb3tjtTWFzY3l6MIH2C/i+A1yt aio87HJRzMeJy4xmJ4UD2nvxq7bZ5TQfHSoM7zKoHKUqCabKJfYXbBtv434hC8GD POoWKWaJbwkg3wCkeS0RdkP8UyAY0vIQiRjZsmyTGM77sNRs53EOerC3lvGzdigA bldyunBZ0glkjX8GKRr6JAMSOMkAcZyvr/1zGxqkI89f94m62USOcWFc4NWA9XLK PmExPQxvrNgC9MeGpkvNdjKXgnA42cPqon7yy1JB3SkmgGwotgUe4Rbmk8AFSRCs oACPYYBvIBKeudfMaCaPDWu1JpY74pD60v8G0zLbZ6d1XsRjrty5obWBkdDEMsPx hi5wjT3zSoEnzwKnpkM6fOfU0KB7dth9AXCW/Oqf+79fzuZpb+xqtOQwpSUxC1Ky SDS/qtj9iF6ak4guMxOEyLHf/RRg7/VsicGcnhyBKs/ymWFcyh6gbCeRBMqN/wAC 3oqKSinhojQvlAK6nm8XvDBycIlo/7P2N1xRMFBVX1arMuUb9ehobq2buM4oLpDz yLjRoKKTYwblss47w/+ybetrzDDRXV7pzKYogzIo35HG6NXRQzc= =pupU -END PGP SIGNATURE- pgpH5UdFbJQdr.pgp Description: PGP signature --- End Message ---
Bug#1080741: marked as done (Missing Build-Depends on python3-setuptools)
Your message dated Sat, 09 Nov 2024 11:10:46 + with message-id and subject line Bug#1080741: fixed in python-gnuplot 1.8-9 has caused the Debian Bug report #1080741, regarding Missing Build-Depends on python3-setuptools 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.) -- 1080741: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1080741 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python-gnuplot Version: 1.8-8 Severity: important User: debian-pyt...@lists.debian.org Usertags: dh-python-no-setuptools Tags: sid, trixie This package failed build from source when test-built against a version of dh-python without a python3-setuptools dependency. distutils is no longer part of the Python standard library, since 3.12. But a minimal version of it becomes available when the python3-setuptools package is installed. Please add a Build-Depends on python3-setuptools to your package, or migrate the package's build system away from setuptools/distutils. If you run into any difficulties, please raise them on debian-pyt...@lists.debian.org. This bug has been filed at "important" severity, as the change hasn't been made in dh-python yet, but this may be raised to RC before the trixie release. Thanks, Stefano --- End Message --- --- Begin Message --- Source: python-gnuplot Source-Version: 1.8-9 Done: Alexandre Detiste We believe that the bug you reported is fixed in the latest version of python-gnuplot, 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 1080...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Alexandre Detiste (supplier of updated python-gnuplot 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: Sat, 09 Nov 2024 11:20:43 +0100 Source: python-gnuplot Architecture: source Version: 1.8-9 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers Changed-By: Alexandre Detiste Closes: 1080741 Changes: python-gnuplot (1.8-9) unstable; urgency=medium . * Team Upload * Add dependency on python3-setuptools for Distutils compatibility (Closes: #1080741) * Set Rules-Requires-Root: no Checksums-Sha1: 535e21ff599eee1a9d239c434ae4138e798e1c84 2158 python-gnuplot_1.8-9.dsc d850d793a89439015ff9897cffdb8fcdaf7e60ed 13428 python-gnuplot_1.8-9.debian.tar.xz 254bdaa60e96a766c9d9c07762a167915cf34e75 7887 python-gnuplot_1.8-9_source.buildinfo Checksums-Sha256: af731f9c979ad6c17b9ebb4638fa70dc12fe531b3890d22c5c87539aac5d60e1 2158 python-gnuplot_1.8-9.dsc 0b166539162fc4635e3f6490564d87c7a719940e3fd9ef45c37ad587bd01e68e 13428 python-gnuplot_1.8-9.debian.tar.xz ed401ef41a3dd866c6c2bfc09f516afbcd89393abf35a4336715458bbd1b70df 7887 python-gnuplot_1.8-9_source.buildinfo Files: dc2deb15318b2addf6df5d479320f2d2 2158 python optional python-gnuplot_1.8-9.dsc 9e610b21cf481c85ef43671fe01b7b9d 13428 python optional python-gnuplot_1.8-9.debian.tar.xz f2a0a842eb5e7f1cb20dd713d5ff0cfc 7887 python optional python-gnuplot_1.8-9_source.buildinfo -BEGIN PGP SIGNATURE- iQJFBAEBCgAvFiEEj23hBDd/OxHnQXSHMfMURUShdBoFAmcvPjMRHHRjaGV0QGRl Ymlhbi5vcmcACgkQMfMURUShdBp20RAAgG2Y2lvwnvNKgag1Sj+EnF0/guPKB9sh jvHHqzTOQHPp8gSq0IlELk5t61py6D/r7WRkxBLkEialkmsoGxB8w/hZJXZeG087 328Ap5i0JNCLup7Qq4qfgI4F5JYAHAa7v4x88VqFIv1Jy7gkIChSSLP5xO4HEfpd 6JTOeyYQZaAzRnceVpNB9KkxEwczFv4WmkN1yaCJPuD9FVkATPi9Q+LFT710t++r OBF+1p3MdAG9RDXYRIezQZRJjVWaHBuCu2O3h2tiGuo+i6/txSG6Bzw0wo38SnX4 qy5vUvQ7Njnj+fP221O/VIjz4ovxV1PC9JHwWv9w0tifkNDI1Ji1TS8KR/dw9M03 A8yofUrdINj2GFjIeg6AGoijUh31009sK1roBY3IaPuANm10vse6IQlyQovnkdRB shz8zM74BMnZG+p6kpn7/vs/oB0lmdZVwCDpN+jV6yz3JI7C3zwvruXCGIU+/l1q vOmzq38gozv42V9Mp6z9h0Nf+af73/RhDBwkajw4G6b2o+IBH9TICuKLl5SkayCq 5b6g5pHtJG1au81lIDUo2D24Qn92QKWGddv2mijdLZdOpueb7LWkND+nRbqjZtP0 mxqjooxyUjNvEfWaew2PABBIjF4y+hjfS+XabEW/01K8viDclwe3396AwsLhsezb 0/13I5kl72o= =o2vG -END PGP SIGNATURE- pgp9eGCkqLKt0.pgp Description: PGP signature --- End Message ---
Bug#1086910: marked as done (ffindex: depends on openmpi on 32-bit architectures)
Your message dated Sat, 09 Nov 2024 11:06:23 + with message-id and subject line Bug#1086910: fixed in ffindex 0.9.9.9-7 has caused the Debian Bug report #1086910, regarding ffindex: depends on openmpi on 32-bit architectures 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.) -- 1086910: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1086910 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ffindex Severity: serious Hi, ffindex depends on openmpi on 32-bit architectures, which has been removed in openmpi 5. Thus this package needs to stop depending on it on those architectures. There are a couple of options: - build-dep on mpi-default-dev instead of openmpi-dev, so that the MPICH implementation can be used on those architectures. - remove the package from 32-bit architectures (armel, armhf and i386) by filing an RM bug against ftp.debian.org See [1] for the transition bug and [2] for the tracker. Cheers, Emilio [1] https://bugs.debian.org/1064810 [2] https://release.debian.org/transitions/html/openmpi-rm32.html --- End Message --- --- Begin Message --- Source: ffindex Source-Version: 0.9.9.9-7 Done: Étienne Mollier We believe that the bug you reported is fixed in the latest version of ffindex, 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 1086...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Étienne Mollier (supplier of updated ffindex 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: Sat, 09 Nov 2024 11:33:18 +0100 Source: ffindex Architecture: source Version: 0.9.9.9-7 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team Changed-By: Étienne Mollier Closes: 1084923 1086910 Changes: ffindex (0.9.9.9-7) unstable; urgency=medium . * d/control: migrate to mpi-default-*. (Closes: #1086910, #1084923) * d/control: migrate to pkgconf. * d/control: declare compliance to standards version 4.7.0. * d/control: add myself to uploaders. * d/*lintian-overrides: adjust mismatched override. * d/watch: remove unneeded template lines. * d/patches/*: declare reviewers separately. This change fixes invalid dep3 metadata. Checksums-Sha1: c67cfe131be7faeb90da19aa9c4da1a4961c3591 2367 ffindex_0.9.9.9-7.dsc cc226a958bf632d180d334bcdca5f336b0325f70 15564 ffindex_0.9.9.9-7.debian.tar.xz Checksums-Sha256: 410787a963d5e67c367baf87bb14b1373058203d54c6ec1b7162aa85bcf84fbc 2367 ffindex_0.9.9.9-7.dsc decd0ed750872e5bc425a7b85accb258a90c491be546c447461d467b638dd55b 15564 ffindex_0.9.9.9-7.debian.tar.xz Files: 66e36ee9ee0a592452d5f48f9927d712 2367 science optional ffindex_0.9.9.9-7.dsc c720410381090d45c005a3cf35a1dffa 15564 science optional ffindex_0.9.9.9-7.debian.tar.xz -BEGIN PGP SIGNATURE- iQJIBAEBCgAyFiEEj5GyJ8fW8rGUjII2eTz2fo8NEdoFAmcvPa0UHGVtb2xsaWVy QGRlYmlhbi5vcmcACgkQeTz2fo8NEdqoKhAAkSPSRKphz2TPky0I4+w60eXVihwp G+1Fx1NVhatByhQ5d9jYvMhJl0Z0/QYosbfL8v+Sszn4QDTrjpCE/YvNndiioCJK fug5v73r5wWc1AzXURAB72l99Ua4aryuYITNvGRjEeCzUSPrjl9TY1ouamtn6ZIX A4hwHuk7I3V/h8+pUzIskmr6uM6WUShdm8F1HZS8qQHJtkWHIW4BUgR/VpxXdk0d fry05fP+NBynmojgJxWz/+3S8044QdvzKA6HzLzuPYQ+37Tp5MCUbFg59emJSkX8 2nEn7YCjhkSmmQBSxMLW6NF4Qq9kzJwXVIuadP6Tfo7Mib9G0jY3tSxHsLYw9zOO KbjeGzD4ZDyu83EXtGok/Q5pED9KcR8BMnBkxLGBS5mGnOvLV6mGzyDhmaBiKhe7 9jsempXzMpileH/ZL8CuySSD6eINq5O4Hvq9mnFqzfziJZHfGlCrPdZkZ7PL9DAS BMEyfcvATBCCVkHYk6pEFHPSbrJtyehR5zOLRq3dzoZOwlK5rrw5sZ6V4B8Ddp8Z 4jkR09NqewY+Ur/Pe47ol4LzeToZQ2wmn6K6UiB0SZelCqV69pWHiMRb4aByn4Wu 9XkDFvUWU2QiQ2Ja/pztquruLq3wxhXEeK1QQKZ33LfI+D6JM1NVKIZfuTNb2l6r WSqZQsibvKO/xSQ= =zk2R -END PGP SIGNATURE- pgp8Dfxs5g1yc.pgp Description: PGP signature --- End Message ---
Bug#1084923: marked as done (ffindex: Drop openmpi for 32-bit systems)
Your message dated Sat, 09 Nov 2024 11:06:23 + with message-id and subject line Bug#1084923: fixed in ffindex 0.9.9.9-7 has caused the Debian Bug report #1084923, regarding ffindex: Drop openmpi for 32-bit systems 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.) -- 1084923: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1084923 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ffindex Version: 0.9.9.9-6.1 Severity: normal This package is part of the openmpi-rm32 transition. In the upcoming release openmpi-5 , 32bit support is being dropped. Please move to using mpi-default as this enables mpich on 32-bit systems. -- System Information: Debian Release: 12.7 APT prefers stable-security APT policy: (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-25-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_IE.UTF-8), LANGUAGE=en_IE:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled --- End Message --- --- Begin Message --- Source: ffindex Source-Version: 0.9.9.9-7 Done: Étienne Mollier We believe that the bug you reported is fixed in the latest version of ffindex, 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 1084...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Étienne Mollier (supplier of updated ffindex 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: Sat, 09 Nov 2024 11:33:18 +0100 Source: ffindex Architecture: source Version: 0.9.9.9-7 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team Changed-By: Étienne Mollier Closes: 1084923 1086910 Changes: ffindex (0.9.9.9-7) unstable; urgency=medium . * d/control: migrate to mpi-default-*. (Closes: #1086910, #1084923) * d/control: migrate to pkgconf. * d/control: declare compliance to standards version 4.7.0. * d/control: add myself to uploaders. * d/*lintian-overrides: adjust mismatched override. * d/watch: remove unneeded template lines. * d/patches/*: declare reviewers separately. This change fixes invalid dep3 metadata. Checksums-Sha1: c67cfe131be7faeb90da19aa9c4da1a4961c3591 2367 ffindex_0.9.9.9-7.dsc cc226a958bf632d180d334bcdca5f336b0325f70 15564 ffindex_0.9.9.9-7.debian.tar.xz Checksums-Sha256: 410787a963d5e67c367baf87bb14b1373058203d54c6ec1b7162aa85bcf84fbc 2367 ffindex_0.9.9.9-7.dsc decd0ed750872e5bc425a7b85accb258a90c491be546c447461d467b638dd55b 15564 ffindex_0.9.9.9-7.debian.tar.xz Files: 66e36ee9ee0a592452d5f48f9927d712 2367 science optional ffindex_0.9.9.9-7.dsc c720410381090d45c005a3cf35a1dffa 15564 science optional ffindex_0.9.9.9-7.debian.tar.xz -BEGIN PGP SIGNATURE- iQJIBAEBCgAyFiEEj5GyJ8fW8rGUjII2eTz2fo8NEdoFAmcvPa0UHGVtb2xsaWVy QGRlYmlhbi5vcmcACgkQeTz2fo8NEdqoKhAAkSPSRKphz2TPky0I4+w60eXVihwp G+1Fx1NVhatByhQ5d9jYvMhJl0Z0/QYosbfL8v+Sszn4QDTrjpCE/YvNndiioCJK fug5v73r5wWc1AzXURAB72l99Ua4aryuYITNvGRjEeCzUSPrjl9TY1ouamtn6ZIX A4hwHuk7I3V/h8+pUzIskmr6uM6WUShdm8F1HZS8qQHJtkWHIW4BUgR/VpxXdk0d fry05fP+NBynmojgJxWz/+3S8044QdvzKA6HzLzuPYQ+37Tp5MCUbFg59emJSkX8 2nEn7YCjhkSmmQBSxMLW6NF4Qq9kzJwXVIuadP6Tfo7Mib9G0jY3tSxHsLYw9zOO KbjeGzD4ZDyu83EXtGok/Q5pED9KcR8BMnBkxLGBS5mGnOvLV6mGzyDhmaBiKhe7 9jsempXzMpileH/ZL8CuySSD6eINq5O4Hvq9mnFqzfziJZHfGlCrPdZkZ7PL9DAS BMEyfcvATBCCVkHYk6pEFHPSbrJtyehR5zOLRq3dzoZOwlK5rrw5sZ6V4B8Ddp8Z 4jkR09NqewY+Ur/Pe47ol4LzeToZQ2wmn6K6UiB0SZelCqV69pWHiMRb4aByn4Wu 9XkDFvUWU2QiQ2Ja/pztquruLq3wxhXEeK1QQKZ33LfI+D6JM1NVKIZfuTNb2l6r WSqZQsibvKO/xSQ= =zk2R -END PGP SIGNATURE- pgp9heePWd0cl.pgp Description: PGP signature --- End Message ---
Bug#1085227: marked as done (bookworm-pu: package python-cryptography/38.0.4-3+deb12u1)
Your message dated Sat, 09 Nov 2024 10:51:02 + with message-id and subject line Closing bugs released with 12.8 has caused the Debian Bug report #1085227, regarding bookworm-pu: package python-cryptography/38.0.4-3+deb12u1 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.) -- 1085227: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1085227 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: release.debian.org Severity: normal Tags: bookworm User: release.debian@packages.debian.org Usertags: pu X-Debbugs-Cc: Debian Python Team , secur...@debian.org * CVE-2023-49083: NULL dereference when loading PKCS7 certificates (Closes: #1057108) * CVE-2024-26130: NULL dereference when PKCS#12 key and cert don't match (Closes: #1064778) diffstat for python-cryptography-38.0.4 python-cryptography-38.0.4 changelog | 10 + patches/0001-Fixed-crash-when-loading-a-PKCS-7-bundle-with-no-cer.patch | 48 +++ patches/0002-Fixes-10422-don-t-crash-when-a-PKCS-12-key-and-cert-.patch | 63 ++ patches/series |2 4 files changed, 123 insertions(+) diff -Nru python-cryptography-38.0.4/debian/changelog python-cryptography-38.0.4/debian/changelog --- python-cryptography-38.0.4/debian/changelog 2023-02-28 07:36:13.0 +0200 +++ python-cryptography-38.0.4/debian/changelog 2024-10-16 19:53:04.0 +0300 @@ -1,3 +1,13 @@ +python-cryptography (38.0.4-3+deb12u1) bookworm; urgency=medium + + * Non-maintainer upload. + * CVE-2023-49083: NULL dereference when loading PKCS7 certificates +(Closes: #1057108) + * CVE-2024-26130: NULL dereference when PKCS#12 key and cert don't match +(Closes: #1064778) + + -- Adrian Bunk Wed, 16 Oct 2024 19:53:04 +0300 + python-cryptography (38.0.4-3) unstable; urgency=medium [ Salvatore Bonaccorso ] diff -Nru python-cryptography-38.0.4/debian/patches/0001-Fixed-crash-when-loading-a-PKCS-7-bundle-with-no-cer.patch python-cryptography-38.0.4/debian/patches/0001-Fixed-crash-when-loading-a-PKCS-7-bundle-with-no-cer.patch --- python-cryptography-38.0.4/debian/patches/0001-Fixed-crash-when-loading-a-PKCS-7-bundle-with-no-cer.patch 1970-01-01 02:00:00.0 +0200 +++ python-cryptography-38.0.4/debian/patches/0001-Fixed-crash-when-loading-a-PKCS-7-bundle-with-no-cer.patch 2024-10-16 19:53:04.0 +0300 @@ -0,0 +1,48 @@ +From 8378c1ff784a9601966b88f1c5587d50120038c3 Mon Sep 17 00:00:00 2001 +From: Alex Gaynor +Date: Mon, 27 Nov 2023 14:35:35 -0500 +Subject: Fixed crash when loading a PKCS#7 bundle with no certificates (#9926) + +--- + src/cryptography/hazmat/backends/openssl/backend.py | 5 - + tests/hazmat/primitives/test_pkcs7.py | 6 ++ + 2 files changed, 10 insertions(+), 1 deletion(-) + +diff --git a/src/cryptography/hazmat/backends/openssl/backend.py b/src/cryptography/hazmat/backends/openssl/backend.py +index f8776b732..45a644cf6 100644 +--- a/src/cryptography/hazmat/backends/openssl/backend.py b/src/cryptography/hazmat/backends/openssl/backend.py +@@ -2454,9 +2454,12 @@ class Backend: + _Reasons.UNSUPPORTED_SERIALIZATION, + ) + ++certs: list[x509.Certificate] = [] ++if p7.d.sign == self._ffi.NULL: ++return certs ++ + sk_x509 = p7.d.sign.cert + num = self._lib.sk_X509_num(sk_x509) +-certs = [] + for i in range(num): + x509 = self._lib.sk_X509_value(sk_x509, i) + self.openssl_assert(x509 != self._ffi.NULL) +diff --git a/tests/hazmat/primitives/test_pkcs7.py b/tests/hazmat/primitives/test_pkcs7.py +index 138bc0f3b..559e1f274 100644 +--- a/tests/hazmat/primitives/test_pkcs7.py b/tests/hazmat/primitives/test_pkcs7.py +@@ -89,6 +89,12 @@ class TestPKCS7Loading: + mode="rb", + ) + ++def test_load_pkcs7_empty_certificates(self, backend): ++der = b"\x30\x0B\x06\x09\x2A\x86\x48\x86\xF7\x0D\x01\x07\x02" ++ ++certificates = pkcs7.load_der_pkcs7_certificates(der) ++assert certificates == [] ++ + + # We have no public verification API and won't be adding one until we get + # some requirements from users so this function exists to give us basic +-- +2.30.2 + diff -Nru python-cryptography-38.0.4/debian/patches/0002-Fixes-10422-don-t-crash-when-a-PKCS-12-key-and-cert-.patch python-cryptography-38.0.4/debian/patches/0002-Fixes-10422-don-t-crash
Bug#1082024: marked as done (bookworm-pu: package timeshift/22.11.2-1+deb12u1)
Your message dated Sat, 09 Nov 2024 10:51:02 +
with message-id
and subject line Closing bugs released with 12.8
has caused the Debian Bug report #1082024,
regarding bookworm-pu: package timeshift/22.11.2-1+deb12u1
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.)
--
1082024: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1082024
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Control: affects -1 + src:timeshift
X-Debbugs-Cc: timesh...@packages.debian.org
User: release.debian@packages.debian.org
Usertags: pu
Tags: bookworm
X-Debbugs-Cc: by...@debian.org
Severity: normal
Debian Debian Stable Release Managers,
I am looking for a stable-pu for Debian 12 on package timeshift
to fix https://bugs.debian.org/1069676 .
[ Reason ]
Package timeshift in Debian 12 currently misses an explicit
runtime dependency pkexec. A new stable-pu upload is needed
to add the missing runtime dependency back.
This bug is reported as https://bugs.debian.org/1069676 and
has been fixed in Debian Testing/Unstable.
[ Impact ]
The user will not be able to open timeshift tools if pkexec
is not installed on the system.
[ Tests ]
Manually tested.
[ Risks ]
Minimal risk. Only an addition of runtime dependency is added.
[ Checklist ]
[X] *all* changes are documented in the d/changelog
[X] I reviewed all changes and I approve them
[X] attach debdiff against the package in (old)stable
[X] the issue is verified as fixed in unstable
[ Changes ]
diff -Nru timeshift-22.11.2/debian/changelog timeshift-22.11.2/debian/changelog
--- timeshift-22.11.2/debian/changelog 2023-01-11 20:43:46.0 -0500
+++ timeshift-22.11.2/debian/changelog 2024-09-17 12:52:34.0 -0400
@@ -1,3 +1,10 @@
+timeshift (22.11.2-1+deb12u1) bookworm; urgency=medium
+
+ * Team upload.
+ * debian/control: Add missing dependency on pkexec. (Closes: #1069676)
+
+ -- Boyuan Yang Tue, 17 Sep 2024 12:52:34 -0400
+
timeshift (22.11.2-1) unstable; urgency=medium
* Team upload.
diff -Nru timeshift-22.11.2/debian/control timeshift-22.11.2/debian/control
--- timeshift-22.11.2/debian/control2022-07-20 14:42:19.0 -0400
+++ timeshift-22.11.2/debian/control2024-09-17 12:51:59.0 -0400
@@ -22,6 +22,7 @@
Architecture: any
Depends:
cron-daemon | cron,
+ pkexec,
psmisc,
rsync,
${misc:Depends},
[ Other info ]
Please let me know if you have any questions.
Thanks,
Boyuan Yang
signature.asc
Description: This is a digitally signed message part
--- End Message ---
--- Begin Message ---
Source: release.debian.org
Version: 12.8
Hi,
Each of the updates tracked by these bugs was included in today's 12.8
bookworm point release.
Regards,
Adam--- End Message ---
Bug#1086154: marked as done (bookworm-pu: package tgt/1:1.0.85-1+deb12u1)
Your message dated Sat, 09 Nov 2024 10:51:02 + with message-id and subject line Closing bugs released with 12.8 has caused the Debian Bug report #1086154, regarding bookworm-pu: package tgt/1:1.0.85-1+deb12u1 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.) -- 1086154: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1086154 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: release.debian.org Severity: normal Tags: bookworm X-Debbugs-Cc: t...@packages.debian.org, David Gstir , Richard Weinberger , car...@debian.org Control: affects -1 + src:tgt User: release.debian@packages.debian.org Usertags: pu Hi SRM, tgt is affected in stable by CVE-2024-45751, but it is no-dsa. I did a while back a NMU for unstable, preparing for this bookworm-pu update as well. Given there are no issues reported with it in unstable, now proposing as well the bookworm update. Description is at https://security-tracker.debian.org/tracker/CVE-2024-45751 https://www.openwall.com/lists/oss-security/2024/09/07/2 |The user-space iSCSI target daemon of the Linux target framework (tgt) |uses an insecure random number generator to generate CHAP |authentication callenges. This results in predictable challenges which |an attacker capable of recording network traffic between iSCSI target |and initiator can abuse to bypass CHAP authentication by replaying |previous responses. The patch switches to a proper entropy source. Regards, Salvatore --- End Message --- --- Begin Message --- Source: release.debian.org Version: 12.8 Hi, Each of the updates tracked by these bugs was included in today's 12.8 bookworm point release. Regards, Adam--- End Message ---
Bug#1074088: marked as done (bookworm-pu: package cjson/1.7.15-1+deb12u2)
Your message dated Sat, 09 Nov 2024 10:51:02 +
with message-id
and subject line Closing bugs released with 12.8
has caused the Debian Bug report #1074088,
regarding bookworm-pu: package cjson/1.7.15-1+deb12u2
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.)
--
1074088: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074088
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Control: affects -1 + src:cjson
X-Debbugs-Cc: cj...@packages.debian.org
User: release.debian@packages.debian.org
Usertags: pu
Tags: bookworm
Severity: normal
[ Reason ]
CVE-2024-31755
[ Impact ]
Segmentation violation via the cJSON_SetValuestring function.
If the valuestring passed to cJSON_SetValuestring is NULL, a null
pointer dereference will happen, which can potentially cause denial of
service (DOS).
[ Tests ]
Upstream's tests continue to pass, no new tests were added since this is
a trivial change.
[ Risks ]
Minimal risk as the patch is trivial and only changes 1 line to fix this
security issue.
[ Checklist ]
[x] *all* changes are documented in the d/changelog
[x] I reviewed all changes and I approve them
[x] attach debdiff against the package in (old)stable
[x] the issue is verified as fixed in unstable
[ Changes ]
* Backport patch to add NULL check to cJSON_SetValuestring (CVE-2024-31755)
(Closes: #1071742)
[ Other info ]
Security team have marked it no-dsa.
--
Maytham Alsudany
Debian Maintainer
maytham @ OFTC
maytha8 @ Libera
diff -Nru cjson-1.7.15/debian/changelog cjson-1.7.15/debian/changelog
--- cjson-1.7.15/debian/changelog 2024-04-09 09:30:29.0 +0800
+++ cjson-1.7.15/debian/changelog 2024-06-23 14:27:41.0 +0800
@@ -1,3 +1,11 @@
+cjson (1.7.15-1+deb12u2) bookworm; urgency=medium
+
+ * Non-maintainer upload.
+ * Backport patch to add NULL check to cJSON_SetValuestring (CVE-2024-31755)
+(Closes: #1071742)
+
+ -- Maytham Alsudany Sun, 23 Jun 2024 14:27:41 +0800
+
cjson (1.7.15-1+deb12u1) bookworm; urgency=medium
* Non-maintainer upload.
diff -Nru cjson-1.7.15/debian/patches/0002-add-null-check-to-cjson-setvaluestring.patch cjson-1.7.15/debian/patches/0002-add-null-check-to-cjson-setvaluestring.patch
--- cjson-1.7.15/debian/patches/0002-add-null-check-to-cjson-setvaluestring.patch 1970-01-01 08:00:00.0 +0800
+++ cjson-1.7.15/debian/patches/0002-add-null-check-to-cjson-setvaluestring.patch 2024-06-23 14:27:41.0 +0800
@@ -0,0 +1,23 @@
+Origin: backport, https://github.com/DaveGamble/cJSON/commit/7e4d5dabe7a9b754c601f214e65b544e67ba9f59
+From: Up-wind
+Bug: https://github.com/DaveGamble/cJSON/issues/839
+Bug-Debian: https://bugs.debian.org/1071742
+Acked-by: Maytham Alsudany
+Subject: [PATCH] Add NULL check to cJSON_SetValuestring()
+ If the valuestring passed to cJSON_SetValuestring is NULL, a null pointer
+ dereference will happen. This patch adds the NULL check of valuestring before
+ it is dereferenced.
+ .
+ Fix for CVE-2024-31755.
+
+--- a/cJSON.c
b/cJSON.c
+@@ -406,7 +406,7 @@ CJSON_PUBLIC(char*) cJSON_SetValuestring(cJSON *object, const char *valuestring)
+ return NULL;
+ }
+ /* return NULL if the object is corrupted */
+-if (object->valuestring == NULL)
++if (object->valuestring == NULL || valuestring == NULL)
+ {
+ return NULL;
+ }
diff -Nru cjson-1.7.15/debian/patches/series cjson-1.7.15/debian/patches/series
--- cjson-1.7.15/debian/patches/series 2024-04-09 09:29:47.0 +0800
+++ cjson-1.7.15/debian/patches/series 2024-06-23 14:27:41.0 +0800
@@ -1 +1,2 @@
0001-add-null-checkings.patch
+0002-add-null-check-to-cjson-setvaluestring.patch
signature.asc
Description: This is a digitally signed message part
--- End Message ---
--- Begin Message ---
Source: release.debian.org
Version: 12.8
Hi,
Each of the updates tracked by these bugs was included in today's 12.8
bookworm point release.
Regards,
Adam--- End Message ---
Bug#1086632: marked as done (bookworm-pu: package apr/1.7.2-3+deb12u1)
Your message dated Sat, 09 Nov 2024 10:51:02 +
with message-id
and subject line Closing bugs released with 12.8
has caused the Debian Bug report #1086632,
regarding bookworm-pu: package apr/1.7.2-3+deb12u1
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.)
--
1086632: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1086632
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
Tags: bookworm
X-Debbugs-Cc: a...@packages.debian.org, Stefan Fritsch ,
Debian Apache Maintainers , j...@debian.org,
car...@debian.org
Control: affects -1 + src:apr
User: release.debian@packages.debian.org
Usertags: pu
[ Reason ]
apr in bookworm is affected by CVE-2023-49582, #1080375 where
permissions of shared mem files are too wide, making them word
readable.
The apr upstream version 1.7.5 changes those to 0600 permissions.
The issue does not warrant a DSA, so we would like to include it in
the point release.
[ Impact ]
Users of libapr1 create still shared mem files with too lax
permissions.
[ Tests ]
Manual testing the update with apache2 ScoreBoardFile file, previously
created with 0644 permissions, and now with the more restrictive 0600.
[ Risks ]
The patch is taken to upstream merge into 1.7.x version and there were
no followups since then. The version is unstable is present since
beginning of september, TTBOMK without reports.
[ Checklist ]
[x] *all* changes are documented in the d/changelog
[x] I reviewed all changes and I approve them
[x] attach debdiff against the package in (old)stable
[x] the issue is verified as fixed in unstable
[ Changes ]
Change to use 0600 permissions for named shared memoy.
[ Other info ]
Nothing specifically.
Regards,
Salvatore
diff -Nru apr-1.7.2/debian/changelog apr-1.7.2/debian/changelog
--- apr-1.7.2/debian/changelog 2023-02-26 21:51:24.0 +0100
+++ apr-1.7.2/debian/changelog 2024-10-31 21:08:12.0 +0100
@@ -1,3 +1,11 @@
+apr (1.7.2-3+deb12u1) bookworm; urgency=medium
+
+ * Non-maintainer upload.
+ * Use 0600 perms for named shared mem consistently (CVE-2023-49582)
+(Closes: #1080375)
+
+ -- Salvatore Bonaccorso Thu, 31 Oct 2024 21:08:12 +0100
+
apr (1.7.2-3) unstable; urgency=medium
* Add more fixes for atomics from upstream, in particular for
diff -Nru apr-1.7.2/debian/patches/CVE-2023-49582.patch
apr-1.7.2/debian/patches/CVE-2023-49582.patch
--- apr-1.7.2/debian/patches/CVE-2023-49582.patch 1970-01-01
01:00:00.0 +0100
+++ apr-1.7.2/debian/patches/CVE-2023-49582.patch 2024-10-31
21:07:08.0 +0100
@@ -0,0 +1,71 @@
+From: Eric Covener
+Date: Tue, 20 Aug 2024 21:50:42 +
+Subject: Merge r1920082 from 1.8.x:
+Origin:
https://github.com/apache/apr/commit/36ea6d5a2bfc480dd8032cc8651e6793552bc2aa
+Bug-Debian: https://bugs.debian.org/1080375
+Bug-Debian-Security: https://security-tracker.debian.org/tracker/CVE-2023-49582
+
+use 0600 perms for named shared mem consistently
+
+
+
+
+git-svn-id: https://svn.apache.org/repos/asf/apr/apr/branches/1.7.x@1920083
13f79535-47bb-0310-9956-ffa450edef68
+---
+ shmem/unix/shm.c | 18 +++---
+ 1 file changed, 7 insertions(+), 11 deletions(-)
+
+diff --git a/shmem/unix/shm.c b/shmem/unix/shm.c
+index 096884d99d50..ea9b94277b01 100644
+--- a/shmem/unix/shm.c
b/shmem/unix/shm.c
+@@ -287,10 +287,9 @@ APR_DECLARE(apr_status_t) apr_shm_create(apr_shm_t **m,
+ status = APR_SUCCESS;
+
+ #if APR_USE_SHMEM_MMAP_TMP
+-/* FIXME: Is APR_OS_DEFAULT sufficient? */
+-status = apr_file_open(&file, filename,
+- APR_READ | APR_WRITE | APR_CREATE | APR_EXCL,
+- APR_OS_DEFAULT, pool);
++status = apr_file_open(&file, filename,
++ APR_FOPEN_READ | APR_FOPEN_WRITE |
APR_FOPEN_CREATE | APR_FOPEN_EXCL,
++ APR_FPROT_UREAD | APR_FPROT_UWRITE, pool);
+ if (status != APR_SUCCESS) {
+ return status;
+ }
+@@ -319,8 +318,7 @@ APR_DECLARE(apr_status_t) apr_shm_create(apr_shm_t **m,
+ }
+ #endif /* APR_USE_SHMEM_MMAP_TMP */
+ #if APR_USE_SHMEM_MMAP_SHM
+-/* FIXME: SysV uses 0600... should we? */
+-tmpfd = shm_open(shm_name, O_RDWR | O_CREAT | O_EXCL, 0644);
++tmpfd = shm_open(shm_name, O_RDWR | O_CREAT | O_EXCL, 0600);
+ if (tmpfd == -1) {
+ return errno;
+ }
+@@ -361,10 +359,9 @@ APR_DECLARE(apr_status_t) apr_shm_create(apr_shm_t **m,
+ #elif APR_USE_SHMEM_SHMGET
+ new_m-&
Bug#1086613: marked as done (bookworm-pu: package ipmitool/1.8.19-4+deb12u2)
Your message dated Sat, 09 Nov 2024 10:51:02 +
with message-id
and subject line Closing bugs released with 12.8
has caused the Debian Bug report #1086613,
regarding bookworm-pu: package ipmitool/1.8.19-4+deb12u2
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.)
--
1086613: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1086613
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
Tags: bookworm
User: release.debian@packages.debian.org
Usertags: pu
X-Debbugs-Cc: ipmit...@packages.debian.org, z...@debian.org, a...@debian.org,
shankerwangm...@gmail.com
Control: affects -1 + src:ipmitool
[ Reason ]
There are some upstream bugs. Please see Changes section for details.
[ Impact ]
Users would still suffer from upstream bugs. #1061770 and #1082101 would
render some important functionality of this package unusable.
[ Tests ]
I tested the patched version manually and confirm problems have been fixed.
[ Risks ]
All changes are simple and self-explanatory. Risks are minimal.
[ Checklist ]
[x] *all* changes are documented in the d/changelog
[x] I reviewed all changes and I approve them
[x] attach debdiff against the package in (old)stable
[x] the issue is verified as fixed in unstable
[ Changes ]
Mainly patches backported from upstream (and applied in sid):
* 0800-fix-buffer-overrun.patch: a slight stack buffer overflow,
but this function is widely used. Very tiny fix.
* 0801-fix-lan-print-fails-on-unsupported-parameters.patch:
this is an important issue that affects the package usability (#1061770)
* 0802-fix-temp-read-parameters.patch: fix temperature reading,
this also confuses users. Although no BTS bug, I heard user complaints.
* 0803-fix-sdr-hex-value.patch: fixes an important bug report (#1082101)
And drop lsb-base in Depends, to make lintian happy.
--
Thanks,
Shengqi Chen
diff -Nru ipmitool-1.8.19/debian/changelog ipmitool-1.8.19/debian/changelog
--- ipmitool-1.8.19/debian/changelog2024-05-17 20:26:20.0 +0800
+++ ipmitool-1.8.19/debian/changelog2024-11-02 14:52:14.0 +0800
@@ -1,3 +1,15 @@
+ipmitool (1.8.19-4+deb12u2) bookworm; urgency=medium
+
+ * Non-maintainer upload.
+ * d/control: Remove obsolete lsb-base from Depends
+ * d/patches: backport several important fixes from upstream
++ fix a buffer overrun in `open` interface
++ fix lan print fails on unsupported parameters (see: #1061770)
++ fix parameter passed to read temperature sensors
++ fix using hex values when sending raw data (see: #1082101)
+
+ -- Shengqi Chen Sat, 02 Nov 2024 14:52:14 +0800
+
ipmitool (1.8.19-4+deb12u1) bookworm; urgency=medium
* Non-maintainer upload.
diff -Nru ipmitool-1.8.19/debian/control ipmitool-1.8.19/debian/control
--- ipmitool-1.8.19/debian/control 2024-05-17 20:26:20.0 +0800
+++ ipmitool-1.8.19/debian/control 2024-11-02 14:52:07.0 +0800
@@ -19,8 +19,7 @@
Architecture: any
Depends:
${misc:Depends},
- ${shlibs:Depends},
- lsb-base (>= 3.0-6)
+ ${shlibs:Depends}
Pre-Depends:
${misc:Pre-Depends}
Recommends: openipmi
diff -Nru ipmitool-1.8.19/debian/patches/0800-fix-buffer-overrun.patch
ipmitool-1.8.19/debian/patches/0800-fix-buffer-overrun.patch
--- ipmitool-1.8.19/debian/patches/0800-fix-buffer-overrun.patch
1970-01-01 08:00:00.0 +0800
+++ ipmitool-1.8.19/debian/patches/0800-fix-buffer-overrun.patch
2024-11-02 14:40:23.0 +0800
@@ -0,0 +1,35 @@
+From b4bc5c335159b1c272e06dba98e2916e3ecc0462 Mon Sep 17 00:00:00 2001
+From: Howitzer105mm
+Date: Tue, 26 Mar 2024 11:28:16 +
+Subject: [PATCH] open: Eliminate buffer overrun (#24)
+
+clangd reports a buffer overrun issue in `open` interface.
+
+The sprintf() used to fill ipmi_devfs2 requires 17 bytes to store the
+null terminated string. The character buffer is only 16 bytes in
+length.
+
+Signed-off-by: Johnathan Mantey
+Reviewed-on: https://codeberg.org/IPMITool/ipmitool/pulls/24
+Reviewed-by: Alexander Amelkin
+Co-authored-by: Howitzer105mm
+Co-committed-by: Howitzer105mm
+Forwarded: not-needed
+Applied-Upstream:
https://codeberg.org/IPMITool/ipmitool/commit/b4bc5c335159b1c272e06dba98e2916e3ecc0462
+---
+ src/plugins/open/open.c | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+diff --git a/src/plugins/open/open.c b/src/plugins/open/open.c
+index 39c8ea2..88cb6c3 100644
+--- a/src/plugins/open/open.c
b/src/plugins/open/open.c
+@@ -94,7 +94,7 @@ ipmi_openipmi_open(struct ipmi_intf *intf)
+ {
+ char ipmi_dev[16];
+ char ipmi_devfs
Bug#1086164: marked as done (bookworm-pu: package glibc/2.36-9+deb12u9)
Your message dated Sat, 09 Nov 2024 10:51:02 + with message-id and subject line Closing bugs released with 12.8 has caused the Debian Bug report #1086164, regarding bookworm-pu: package glibc/2.36-9+deb12u9 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.) -- 1086164: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1086164 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: release.debian.org Severity: normal Tags: bookworm X-Debbugs-Cc: gl...@packages.debian.org Control: affects -1 + src:glibc User: release.debian@packages.debian.org Usertags: pu [ Reason ] The upstream stable branch got a few fixes in the last months, and this update pulls them into the debian package. [ Impact ] In case the update isn't approved, systems will be left with a few issues, and the differences with upstream will increase. [ Tests ] The upstream fixes come with additional tests, which represent the major part of the debdiff as some test support code had to be backported to support the new tests. [ Risks ] The changes to do not affect critical part of the library, and come with additional tests. The upstream changes have been in sid for about a month and in testing for about 2 weeks. [ Checklist ] [x] *all* changes are documented in the d/changelog [x] I reviewed all changes and I approve them [x] attach debdiff against the package in (old)stable [x] the issue is verified as fixed in unstable [ Changes ] Most of the changes come from the upstream stable branch, and are summarized in the Debian changelog. Please find below some additional explanations. * debian/testsuite-xfail-debian.mk: mark tst-support_descriptors as XFAIL, due to sbuild bug #1070003. => The tst-support_descriptors test fail when running in share mode, due to a limitation of sbuild. This patch allows this test to fail, as some of the build daemons were building stable in unshare mode. This is not the case anymore, but might be re-enabled at some point, so better be safe. * debian/patches/localedata/git-locale-hr_HR-euro.diff: change Croatian locale to use Euro as currency. => This a backport of an upstream patch, as requested by a user, to change the Croatian currency to Euro: https://lists.debian.org/debian-glibc/2024/10/msg00026.html * debian/patches/git-updates.diff: update from upstream stable branch: - resolv: do not ignore short error responses (as generated by e.g. Unbound) to avoid timeouts. => This avoids a timeout when resolving IP using an Unbound nameserver is configured to refuse queries. See the corresponding upstream bug report: https://sourceware.org/bugzilla/show_bug.cgi?id=31890 - resolv: fix timeouts when single-request mode is enabled in resolv.conf. - resolv: fix reloading resolv.conf when a nameserver has been automatically switched to single-request mode. => The single-request mode is used to perform the IPv4 and IPv6 requests sequentially instead of in parallel. This could be due to a config option in resolv.conf or when it is detected that a name server do not support queries in parallel. See the corresponding upstream bug reports: https://sourceware.org/bugzilla/show_bug.cgi?id=30081 https://sourceware.org/bugzilla/show_bug.cgi?id=31476 - mremap(): fix support for the MREMAP_DONTUNMAP option. => The MREMAP_DONTUNMAP option has been added in Linux 5.7, and the way it is implemented on the glibc side might or might not be correct depending on how variadic arguments are defined in the architecture ABI. This fixes support for this new option so that it works on all architectures. See the corresponding upstream bug: https://sourceware.org/bugzilla/show_bug.cgi?id=31968 - fortification: fix name space violation in fortify wrappers. => The way the fortify wrappers are defined can cause some clash with some code, it happens at least with the libsdtc++ testsuite with -D_FORTIFY_SOURCE=2. See the corresponding upstream bug; https://sourceware.org/bugzilla/show_bug.cgi?id=32052 - vfscanf(): fix matches longer than INT_MAX. => This fixes a corner case in the vscanf() function, please see the corresponding upstream bug; https://sourceware.org/bugzilla/show_bug.cgi?id=27650 - ungetc(): fix uninitialized read when putting into unused streams. - ungetc(): fix backup buffer leak on program exit. => This fixes a non-compliance of the ungetc() function with regards to the C11 definition. The second change is actually a fixup of the first one. Please see t
Bug#1086207: marked as done (bookworm-pu: package glib2.0/2.74.6-2+deb12u4)
Your message dated Sat, 09 Nov 2024 10:51:02 +
with message-id
and subject line Closing bugs released with 12.8
has caused the Debian Bug report #1086207,
regarding bookworm-pu: package glib2.0/2.74.6-2+deb12u4
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.)
--
1086207: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1086207
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
Tags: bookworm
X-Debbugs-Cc: glib...@packages.debian.org, debian-cr...@lists.debian.org
Control: affects -1 + src:glib2.0
User: release.debian@packages.debian.org
Usertags: pu
[ Reason ]
Requested by Helmut Grohne on behalf of the cross team.
[ Impact ]
If not approved, backports of packages that participate in bootstrapping
and have had their build-dependency on libglib2.0-dev{,-bin} relaxed to
a build-dependency on the new smaller packages libgio-2.0-dev{,-bin} will
need to revert that change.
[ Tests ]
diffoscope reports that there are no changes to the actual binaries, other
than the new Provides, the version number and some timestamps.
I successfully built
https://salsa.debian.org/debian/libverto/-/tree/wip/smcv/sample-bokworm-backport?ref_type=heads
(which is based on #1082732 and uses libgio-2.0-dev) in a bookworm
environment, and it pulls in libglib2.0-dev instead, as desired.
I also successfully built
https://salsa.debian.org/debian/libportal/-/tree/wip/smcv/nogir
(which uses libgio-2.0-dev and libgio-2.0-dev-bin) in a bookworm
environment without further source changes by using the nogir build-profile,
and it pulls in libglib2.0-dev{,-bin} instead, as desired.
An upgraded bookworm GNOME desktop system runs successfully.
[ Risks ]
Low risk, the changes are trivial.
[ Checklist ]
[x] *all* changes are documented in the d/changelog
[x] I reviewed all changes and I approve them
[x] attach debdiff against the package in (old)stable
[x] the issue is verified as fixed in unstable
[ Changes ]
The only change that is not directly part of what Helmut requested is that
I changed the Uploaders field in `debian/control.in` to be identical to
the one in `debian/control`, so that rebuilds with a different version of
gnome-pkg-tools will not alter it. We have stopped using a `debian/control.in`
for this package (and most other GNOME packages) in trixie.
diffstat for glib2.0-2.74.6 glib2.0-2.74.6
changelog | 21 +
control|2 ++
control.in |4 +++-
3 files changed, 26 insertions(+), 1 deletion(-)
diff -Nru glib2.0-2.74.6/debian/changelog glib2.0-2.74.6/debian/changelog
--- glib2.0-2.74.6/debian/changelog 2024-05-14 11:11:32.0 +0100
+++ glib2.0-2.74.6/debian/changelog 2024-10-28 08:41:03.0 +
@@ -1,3 +1,24 @@
+glib2.0 (2.74.6-2+deb12u4) bookworm; urgency=medium
+
+ [ Helmut Grohne ]
+ * Provide libgio-2.0-dev from libglib2.0-dev in bookworm.
+In unstable, libgio-2.0-dev has been split off from
+libglib2.0-dev. Some of the build dependencies on libglib2.0-dev
+will be switched over to libgio-2.0-dev. This causes them to
+be unsatisfiable in bookworm-backports, unless a bookworm update
+provides forward compatibility by providing libgio-2.0-dev (which
+has never been mentioned in bookworm).
+
+ [ Simon McVittie ]
+ * d/control.in: libglib2.0-dev-bin Provides libgio-2.0-dev-bin.
+Packages backported from trixie/sid might build-depend on
+libgio-2.0-dev-bin if they participate in bootstrapping and need to
+run utilities like glib-mkenums or gdbus-codegen during their build.
+ * d/control.in: Freeze Uploaders at the value it previously had in bookworm.
+This allows `debian/rules clean` to be run without altering d/control.
+
+ -- Simon McVittie Mon, 28 Oct 2024 08:41:03 +
+
glib2.0 (2.74.6-2+deb12u3) bookworm; urgency=medium
* d/p/gdbusmessage-Clean-the-cached-arg0-when-setting-the-messa.patch:
diff -Nru glib2.0-2.74.6/debian/control glib2.0-2.74.6/debian/control
--- glib2.0-2.74.6/debian/control 2024-05-14 11:11:32.0 +0100
+++ glib2.0-2.74.6/debian/control 2024-10-28 08:41:03.0 +
@@ -142,6 +142,7 @@
Replaces: libglib2.0-0-dbg (<< 2.51.4-1~)
Suggests: libgirepository1.0-dev (>= 1.62),
libglib2.0-doc
+Provides: libgio-2.0-dev (= ${binary:Version})
Description: Development files for the GLib library
GLib is a library containing many useful C routines for things such
as trees, hashes, lists, and strings. It is a useful general-purpose
@@ -163,6 +164,7 @@
${shlibs:Depends}
Suggests: libgdk-pixb
Bug#1086611: marked as done (bookworm-pu: package node-dompurify/2.4.1+dfsg+~2.4.0-2+deb12u1)
Your message dated Sat, 09 Nov 2024 10:51:02 +
with message-id
and subject line Closing bugs released with 12.8
has caused the Debian Bug report #1086611,
regarding bookworm-pu: package node-dompurify/2.4.1+dfsg+~2.4.0-2+deb12u1
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.)
--
1086611: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1086611
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
Tags: bookworm
X-Debbugs-Cc: node-dompur...@packages.debian.org, y...@debian.org
Control: affects -1 + src:node-dompurify
User: release.debian@packages.debian.org
Usertags: pu
[ Reason ]
node-dompurify is vulnerable to prototype pollutions.
Note that CVE-2024-45801 cae with previous security fix pushed to
Bookworm via security update (regression).
[ Impact ]
Low security issue
[ Tests ]
No tests in Bookworm for this package
[ Risks ]
Low risk, patch is trivial
[ Checklist ]
[X] *all* changes are documented in the d/changelog
[X] I reviewed all changes and I approve them
[X] attach debdiff against the package in (old)stable
[X] the issue is verified as fixed in unstable
[ Changes ]
Just some additional checks
Best regards,
Yadd
diff --git a/debian/changelog b/debian/changelog
index 02c7a01..e9a5528 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,9 @@
+node-dompurify (2.4.1+dfsg+~2.4.0-2+deb12u1) bookworm; urgency=medium
+
+ * Fix prototype pollutions (Closes: CVE-2024-45801, CVE-2024-48910)
+
+ -- Yadd Sat, 02 Nov 2024 07:15:24 +0100
+
node-dompurify (2.4.1+dfsg+~2.4.0-2) bookworm-security; urgency=medium
* Team upload
diff --git a/debian/patches/CVE-2024-45801.patch
b/debian/patches/CVE-2024-45801.patch
new file mode 100644
index 000..3aa90c4
--- /dev/null
+++ b/debian/patches/CVE-2024-45801.patch
@@ -0,0 +1,74 @@
+Description: fix prototype pollution
+ Regression introduced into 2.4.1+dfsg+~2.4.0-2
+Author: Mario Heiderich
+Origin: upstream, https://github.com/cure53/DOMPurify/commit/26e1d69c
+Bug:
https://github.com/cure53/DOMPurify/security/advisories/GHSA-mmhx-hmjr-r674
+Forwarded: not-needed
+Applied-Upstream: 2.5.1, https://github.com/cure53/DOMPurify/commit/26e1d69c
+Reviewed-By: Yadd
+Last-Update: 2024-10-30
+
+--- a/src/purify.js
b/src/purify.js
+@@ -14,6 +14,7 @@
+ stringToString,
+ stringIndexOf,
+ stringTrim,
++ numberIsNaN,
+ regExpTest,
+ typeErrorCreate,
+ lookupGetter,
+@@ -1484,8 +1485,14 @@
+ }
+ }
+
+-/* Remove first element node (ours) if FORCE_BODY is set */
+-if (body && FORCE_BODY) {
++/*
++ * Remove an element if nested too deeply to avoid mXSS
++ * or if the __depth might have been tampered with
++ */
++if (
++ shadowNode.__depth >= MAX_NESTING_DEPTH ||
++ numberIsNaN(shadowNode.__depth)
++) {
+ _forceRemove(body.firstChild);
+ }
+
+@@ -1520,8 +1527,14 @@
+ }
+ }
+
+- /* Remove an element if nested too deeply to avoid mXSS */
+- if (currentNode.__depth >= MAX_NESTING_DEPTH) {
++ /*
++ * Remove an element if nested too deeply to avoid mXSS
++ * or if the __depth might have been tampered with
++ */
++ if (
++currentNode.__depth >= MAX_NESTING_DEPTH ||
++numberIsNaN(currentNode.__depth)
++ ) {
+ _forceRemove(currentNode);
+ }
+
+--- a/src/utils.js
b/src/utils.js
+@@ -50,6 +50,8 @@
+
+ const typeErrorCreate = unconstruct(TypeError);
+
++const numberIsNaN = unapply(Number.isNaN);
++
+ export function unapply(func) {
+ return (thisArg, ...args) => apply(func, thisArg, args);
+ }
+@@ -155,6 +157,8 @@
+ stringToLowerCase,
+ stringToString,
+ stringTrim,
++ // Number
++ numberIsNaN,
+ // Errors
+ typeErrorCreate,
+ // Other
diff --git a/debian/patches/CVE-2024-48910.patch
b/debian/patches/CVE-2024-48910.patch
new file mode 100644
index 000..41ccf65
--- /dev/null
+++ b/debian/patches/CVE-2024-48910.patch
@@ -0,0 +1,20 @@
+Description: fix prototype pollution
+Author: Mario Heiderich
+Origin: upstream, https://github.com/cure53/DOMPurify/commit/d1dd0374
+Bug:
https://github.com/cure53/DOMPurify/security/advisories/GHSA-p3vf-v8qc-cwcr
+Forwarded: not-needed
+Applied-Upstream: 2.4.2
+Reviewed-By: Yadd
+Last-Update: 2024-11-02
+
+--- a/src/utils.js
b/src/utils.js
+@@ -97,7 +97,7 @@
+
+ let property;
+ for (property in object) {
+-if (apply(hasOwnProperty, object, [property])) {
++if (apply(hasOwnProperty, object, [property]) === true) {
+
Bug#1086601: marked as done (bookworm-pu: package intel-microcode/3.20240910.1~deb12u1)
Your message dated Sat, 09 Nov 2024 10:51:02 + with message-id and subject line Closing bugs released with 12.8 has caused the Debian Bug report #1086601, regarding bookworm-pu: package intel-microcode/3.20240910.1~deb12u1 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.) -- 1086601: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1086601 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: release.debian.org Severity: normal Tags: bookworm User: release.debian@packages.debian.org Usertags: pu [ Reason ] As requested by the security team, I would like to bring the microcode update level for Intel processors in Bullseye and Bookworm to match what we have in Sid and Trixie. This is the bug report for Bookworm, a separate one will be filled for Bullseye. This fixes: * Two CVEs in many Intel processors - Mitigations for INTEL-SA-01103 (CVE-2024-23984) - Mitigations for INTEL-SA-01097 (CVE-2024-24968) * Other unspecified functional issues on several processors There are no releavant issues reported on this microcode update, considering the version of intel-microcode already available as security updates for bookworm and bullseye. [ Impact ] If this update is not approved, owners of most recent "client" Intel processors and a few server processors will depend on UEFI updates to be protected from the issues listed above. [ Tests ] There were no bug reports from users of Debian sid or Trixie, these packages have been tested there since 2024-09-21 (sid), 2024-09-27 (trixie). [ Risks ] Unknown, but not believed to be any different from other Intel microcode updates. [ Checklist ] [x] *all* changes are documented in the d/changelog [x] I reviewed all changes and I approve them [x] attach debdiff against the package in (old)stable [x] the issue is verified as fixed in unstable [ Changes ] As per the debdiff, only documentation changes, package documentation changes, and the binary blob change from upstream. changelog| 52 ++-- debian/changelog | 73 --- intel-ucode/06-97-02 |binary intel-ucode/06-97-05 |binary intel-ucode/06-9a-03 |binary intel-ucode/06-9a-04 |binary intel-ucode/06-aa-04 |binary intel-ucode/06-b7-01 |binary intel-ucode/06-ba-02 |binary intel-ucode/06-ba-03 |binary intel-ucode/06-ba-08 |binary intel-ucode/06-be-00 |binary intel-ucode/06-bf-02 |binary intel-ucode/06-bf-05 |binary releasenote.md | 35 15 files changed, 155 insertions(+), 5 deletions(-) [ Other info ] The package version with "~" is needed to guarantee smooth updates to the next debian release. -- Henrique Holschuh diff --git a/changelog b/changelog index d5e45bc..e6eb97c 100644 --- a/changelog +++ b/changelog @@ -1,3 +1,33 @@ +2024-09-10: + * New upstream microcode datafile 20240910 +- Mitigations for INTEL-SA-01103 (CVE-2024-23984) + A potential security vulnerability in the Running Average Power Limit + (RAPL) interface for some Intel Processors may allow information + disclosure. +- Mitigations for INTEL-SA-01097 (CVE-2024-24968) + A potential security vulnerability in some Intel Processors may allow + denial of service. +- Fixes for unspecified functional issues on several processor models +- The processor voltage limit issue on Core 13rd/14th gen REQUIRES A + FIRMWARE UPDATE. It is present in this release for sig 0xb0671, but + THE VOLTAGE ISSUE FIX ONLY WORKS WHEN THE MICROCODE UPDATE IS LOADED + THROUGH THE FIT TABLE IN FIRMWARE. Contact your system vendor for a + firmware update that includes the appropriate microcode update for + your processor. + * Updated Microcodes: +sig 0x00090672, pf_mask 0x07, 2024-02-22, rev 0x0036, size 224256 +sig 0x00090675, pf_mask 0x07, 2024-02-22, rev 0x0036 +sig 0x000b06f2, pf_mask 0x07, 2024-02-22, rev 0x0036 +sig 0x000b06f5, pf_mask 0x07, 2024-02-22, rev 0x0036 +sig 0x000906a3, pf_mask 0x80, 2024-02-22, rev 0x0434, size 08 +sig 0x000906a4, pf_mask 0x80, 2024-02-22, rev 0x0434 +sig 0x000a06a4, pf_mask 0xe6, 2024-06-17, rev 0x001f, size 137216 +sig 0x000b0671, pf_mask 0x32, 2024-07-18, rev 0x0129, size 215040 +sig 0x000b06a2, pf_mask 0xe0, 2024-02-22, rev 0x4122, size 220160 +sig 0x000b06a3, pf_mask 0xe0, 2024-02-22, rev 0x4122 +sig 0x000b06a8, pf_mask 0xe0, 2024-02-22, rev 0x4122 +sig 0x000b06e0, pf_mask 0x19, 2024-03-25, rev 0x001a, size 138240 +
Bug#1086163: marked as done (bookworm-pu: package curl/7.88.1-10+deb12u8)
Your message dated Sat, 09 Nov 2024 10:51:02 +
with message-id
and subject line Closing bugs released with 12.8
has caused the Debian Bug report #1086163,
regarding bookworm-pu: package curl/7.88.1-10+deb12u8
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.)
--
1086163: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1086163
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Control: affects -1 + src:curl
X-Debbugs-Cc: c...@packages.debian.org, aquilamac...@riseup.net,
samuel...@debian.org
User: release.debian@packages.debian.org
Usertags: pu
Tags: bookworm
Severity: normal
[ Reason ]
The reason is to fix CVE-2024-8096 [1], which involves improper handling
of OCSP stapling in curl when using GnuTLS as the TLS backend. If the
OCSP status returns an error other than "revoked" (e.g.,
"unauthorized"), curl fails to mark the certificate as invalid.
[ Impact ]
The vulnerabilities in the curl code of bookworm can be exploited by
attackers, potentially compromising secure connections.
[ Tests ]
Autopkgtest passed without issues [3].
[ Risks ]
The patch simplifies OCSP response handling by improving error checks.
It is low-risk, as it refines existing functionality without major
changes to the code structure. The patch from upstream was not altered,
meaning that any potential regressions would only stem from upstream
changes, not from modifications on our side. Any potential minor risk
would only impact the GnuTLS backend, leaving other TLS backends
unaffected. samueloph also reviewed and approved my changes.
[ Checklist ]
[x] *all* changes are documented in the d/changelog
[x] I reviewed all changes and I approve them
[x] attach debdiff against the package in (old)stable
[x] the issue is verified as fixed in unstable
[ Changes ]
1. Imported the upstream patch that fixes CVE-2024-8096.
[1] https://security-tracker.debian.org/tracker/CVE-2024-8096
[2] https://hackerone.com/reports/2669852
[3] https://salsa.debian.org/aquilamacedo/curl/-/jobs/6297570)diff -Nru curl-7.88.1/debian/changelog curl-7.88.1/debian/changelog
--- curl-7.88.1/debian/changelog 2024-08-17 14:06:29.0 -0300
+++ curl-7.88.1/debian/changelog 2024-09-17 16:29:24.0 -0300
@@ -1,3 +1,14 @@
+curl (7.88.1-10+deb12u8) bookworm; urgency=medium
+
+ * Team upload.
+ * Import patch for CVE-2024-8096
+- CVE-2024-8096: When the TLS backend is GnuTLS, curl may incorrectly
+ handle OCSP stapling. If the OCSP status reports an error other than
+ "revoked" (e.g., "unauthorized"), it is not treated as a bad certificate,
+ potentially allowing invalid certificates to be considered valid.
+
+ -- Aquila Macedo Costa Tue, 17 Sep 2024 16:29:24 -0300
+
curl (7.88.1-10+deb12u7) bookworm; urgency=medium
* Team upload.
diff -Nru curl-7.88.1/debian/patches/CVE-2024-8096.patch curl-7.88.1/debian/patches/CVE-2024-8096.patch
--- curl-7.88.1/debian/patches/CVE-2024-8096.patch 1969-12-31 21:00:00.0 -0300
+++ curl-7.88.1/debian/patches/CVE-2024-8096.patch 2024-09-17 16:29:07.0 -0300
@@ -0,0 +1,200 @@
+From aeb1a281cab13c7ba791cb104e556b20e713941f Mon Sep 17 00:00:00 2001
+From: Daniel Stenberg
+Date: Tue, 20 Aug 2024 16:14:39 +0200
+Subject: [PATCH] gtls: fix OCSP stapling management
+
+Reported-by: Hiroki Kurosawa
+Closes #14642
+---
+ lib/vtls/gtls.c | 146
+ 1 file changed, 73 insertions(+), 73 deletions(-)
+
+diff --git a/lib/vtls/gtls.c b/lib/vtls/gtls.c
+index 03d6fcc038aac3..c7589d9d39bc81 100644
+--- a/lib/vtls/gtls.c
b/lib/vtls/gtls.c
+@@ -850,6 +850,13 @@ static CURLcode gtls_client_init(struct Curl_cfilter *cf,
+ init_flags |= GNUTLS_NO_TICKETS;
+ #endif
+
++#if defined(GNUTLS_NO_STATUS_REQUEST)
++ if(!config->verifystatus)
++/* Disable the "status_request" TLS extension, enabled by default since
++ GnuTLS 3.8.0. */
++init_flags |= GNUTLS_NO_STATUS_REQUEST;
++#endif
++
+ rc = gnutls_init(>ls->session, init_flags);
+ if(rc != GNUTLS_E_SUCCESS) {
+ failf(data, "gnutls_init() failed: %d", rc);
+@@ -1321,104 +1328,97 @@ Curl_gtls_verifyserver(struct Curl_easy *data,
+ infof(data, " server certificate verification SKIPPED");
+
+ if(config->verifystatus) {
+-if(gnutls_ocsp_status_request_is_checked(session, 0) == 0) {
+- gnutls_datum_t status_request;
+- gnutls_ocsp_resp_t ocsp_resp;
++gnutls_datum_t status_request;
++gnutls_ocsp_resp_t ocsp_r
Bug#1086193: marked as done (bookworm-pu: package sumo/1.15.0+dfsg-1+deb12u1)
Your message dated Sat, 09 Nov 2024 10:51:02 +
with message-id
and subject line Closing bugs released with 12.8
has caused the Debian Bug report #1086193,
regarding bookworm-pu: package sumo/1.15.0+dfsg-1+deb12u1
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.)
--
1086193: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1086193
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
Tags: bookworm
User: release.debian@packages.debian.org
Usertags: pu
X-Debbugs-Cc: s...@packages.debian.org, sanv...@debian.org
Control: affects -1 + src:sumo
[ Reason ]
This upload fixes FTBFS Bug #1082135, a case of "unintended parallelism".
A bashism &> made doxygen to work in the background from dh_auto_build.
By the time dh_installdocs works, doxygen was still writing things
in the directory on which dh_installdocs was supposed to act.
[ Impact ]
Anybody trying to build the package from source may potentially
get the build failure. In some systems it has been observed
a failure rate of 100%.
[ Tests ]
I've tested that the package builds ok in a machine where the
build used to fail.
[ Risks ]
Very low. The fix is a one-liner.
[ Checklist ]
[X] *all* changes are documented in the d/changelog
[X] I reviewed all changes and I approve them
[X] attach debdiff against the package in (old)stable
[X] the issue is verified as fixed in unstable
[ Changes ]
Fix bashism in CMakeLists.txt.
[ Other info ]
The debdiff is attached. I'm uploading the package now, but I will
wait for confirmation before pushing to salsa.diff -Nru sumo-1.15.0+dfsg/debian/changelog sumo-1.15.0+dfsg/debian/changelog
--- sumo-1.15.0+dfsg/debian/changelog 2022-12-17 09:20:08.0 +0100
+++ sumo-1.15.0+dfsg/debian/changelog 2024-10-28 16:44:00.0 +0100
@@ -1,3 +1,10 @@
+sumo (1.15.0+dfsg-1+deb12u1) bookworm; urgency=medium
+
+ * Team upload.
+ * Remove bashism from CMakeLists.txt. Closes: #1082135.
+
+ -- Santiago Vila Mon, 28 Oct 2024 16:44:00 +0100
+
sumo (1.15.0+dfsg-1) unstable; urgency=medium
* Team upload.
diff -Nru sumo-1.15.0+dfsg/debian/patches/remove-bashism-from-cmakelists.patch
sumo-1.15.0+dfsg/debian/patches/remove-bashism-from-cmakelists.patch
--- sumo-1.15.0+dfsg/debian/patches/remove-bashism-from-cmakelists.patch
1970-01-01 01:00:00.0 +0100
+++ sumo-1.15.0+dfsg/debian/patches/remove-bashism-from-cmakelists.patch
2024-10-28 16:42:21.0 +0100
@@ -0,0 +1,16 @@
+Description: Redirect stdout and stderr in a POSIX-compatible way
+Author: Santiago Vila
+Bug-Debian: https://bugs.debian.org/1082135
+Last-Update: 2024-10-28
+
+--- a/CMakeLists.txt
b/CMakeLists.txt
+@@ -566,7 +566,7 @@
+ add_custom_target(doxygen
+ COMMAND rm -rf docs/doxygen
+ COMMAND mkdir docs/doxygen
+-COMMAND doxygen sumo.doxyconf &> doxygen.log
++COMMAND doxygen sumo.doxyconf > doxygen.log 2>&1
+ WORKING_DIRECTORY ${CMAKE_SOURCE_DIR})
+ set_property(TARGET doxygen PROPERTY EXCLUDE_FROM_DEFAULT_BUILD TRUE)
+ set_property(TARGET doxygen PROPERTY FOLDER "doc")
diff -Nru sumo-1.15.0+dfsg/debian/patches/series
sumo-1.15.0+dfsg/debian/patches/series
--- sumo-1.15.0+dfsg/debian/patches/series 2022-12-15 08:51:00.0
+0100
+++ sumo-1.15.0+dfsg/debian/patches/series 2024-10-28 16:42:21.0
+0100
@@ -1,3 +1,4 @@
60_fix_tests.patch
setuptools.patch
python3.patch
+remove-bashism-from-cmakelists.patch
--- End Message ---
--- Begin Message ---
Source: release.debian.org
Version: 12.8
Hi,
Each of the updates tracked by these bugs was included in today's 12.8
bookworm point release.
Regards,
Adam--- End Message ---
Bug#1086151: marked as done (bookworm-pu: package util-linux/2.38.1-5+deb12u2)
Your message dated Sat, 09 Nov 2024 10:51:02 +
with message-id
and subject line Closing bugs released with 12.8
has caused the Debian Bug report #1086151,
regarding bookworm-pu: package util-linux/2.38.1-5+deb12u2
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.)
--
1086151: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1086151
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
Tags: bookworm
User: release.debian@packages.debian.org
Usertags: pu
X-Debbugs-Cc: util-li...@packages.debian.org, e...@debian.org
Control: affects -1 + src:util-linux
[ Reason ]
ema@ asked in #1085682 to improve reporting of ARM CPU core names in
lscpu for bookworm.
Just as background: on x86, /proc/cpuinfo provides CPU names etc, but on
ARM it doesn't; instead lscpu has lists in its source code.
[ Impact ]
This is improved hardware support. Without the change, running bookworm
on newer ARM(64) hosts will not show their CPU core name in lscpu
output.
[ Tests ]
ema@ picked the commits from upstream and tested it.
[ Risks ]
The commits are from upstream, have been in unstable for a while, and
they only add entries in lookup tables. IMO there is only a very small
risk for regressions.
[ Checklist ]
[x] *all* changes are documented in the d/changelog
[x] I reviewed all changes and I approve them
[x] attach debdiff against the package in (old)stable
[x] the issue is verified as fixed in unstable
[ Changes ]
Three patches from upstream. Each adds more CPU core names for ARM(64)
platforms.
[ Other info ]
Nothing I'm aware of.
Thanks for considering,
Chris
diff -Nru util-linux-2.38.1/debian/changelog util-linux-2.38.1/debian/changelog
--- util-linux-2.38.1/debian/changelog 2024-03-28 10:52:12.0 +0100
+++ util-linux-2.38.1/debian/changelog 2024-10-18 14:56:02.0 +0200
@@ -1,3 +1,12 @@
+util-linux (2.38.1-5+deb12u2) bookworm; urgency=medium
+
+ * Add the following upstream patches to identify new Arm cores:
+- 0027-lscpu-Add-Neoverse-V2-Cortex-R82.patch
+- 0028-lscpu-Add-2023-Cortex.patch
+- 0029-lscpu-Add-Neoverse-V3-N3.patch
+
+ -- Emanuele Rocca Fri, 18 Oct 2024 12:56:02 +
+
util-linux (2.38.1-5+deb12u1) bookworm-security; urgency=medium
* Add upstream patches to fix CVE-2024-28085 (Closes: #1067849)
diff -Nru util-linux-2.38.1/debian/patches/series
util-linux-2.38.1/debian/patches/series
--- util-linux-2.38.1/debian/patches/series 2024-03-28 10:52:12.0
+0100
+++ util-linux-2.38.1/debian/patches/series 2024-10-18 14:56:02.0
+0200
@@ -30,6 +30,9 @@
upstream/0024-fsck-Processes-may-kill-other-processes.patch
upstream/0025-libblkid-ntfs-avoid-UB-in-signed-shift.patch
upstream/0026-libblkid-iso9660-allocate-enough-space-for-UTF16-dec.patch
+upstream/0027-lscpu-Add-Neoverse-V2-Cortex-R82.patch
+upstream/0028-lscpu-Add-2023-Cortex.patch
+upstream/0029-lscpu-Add-Neoverse-V3-N3.patch
upstream/PATCH-rfkill-man-List-options-for-supported-device-types.patch
upstream/PATCH-1-2-lib-pty-Put-master-PTY-into-non-blocking-mode-a.patch
upstream/PATCH-2-2-lib-pty-minor-cleanups.patch
diff -Nru
util-linux-2.38.1/debian/patches/upstream/0027-lscpu-Add-Neoverse-V2-Cortex-R82.patch
util-linux-2.38.1/debian/patches/upstream/0027-lscpu-Add-Neoverse-V2-Cortex-R82.patch
---
util-linux-2.38.1/debian/patches/upstream/0027-lscpu-Add-Neoverse-V2-Cortex-R82.patch
1970-01-01 01:00:00.0 +0100
+++
util-linux-2.38.1/debian/patches/upstream/0027-lscpu-Add-Neoverse-V2-Cortex-R82.patch
2024-10-18 14:56:02.0 +0200
@@ -0,0 +1,29 @@
+From 6857cccbb4157d5da34ca98f77a0ac9d68e1e740 Mon Sep 17 00:00:00 2001
+From: ThomasKaiser
+Date: Sun, 22 Jan 2023 12:37:33 +0100
+Subject: [PATCH] Add missing ARM-cores
+
+https://github.com/ThomasKaiser/sbc-bench/commit/37332238c0a8b7c1555dca9d18a7c98362564416#diff-fdfd2a032c64d6e9ba92a3197cad6b26573c7094433d74efa4ae80f44f65aa99
+---
+ sys-utils/lscpu-arm.c | 2 ++
+ 1 file changed, 2 insertions(+)
+
+diff --git a/sys-utils/lscpu-arm.c b/sys-utils/lscpu-arm.c
+index 8357253c66c..f65b25ed66d 100644
+--- a/sys-utils/lscpu-arm.c
b/sys-utils/lscpu-arm.c
+@@ -78,6 +78,7 @@ static const struct id_part arm_part[] = {
+ { 0xd0d, "Cortex-A77" },
+ { 0xd0e, "Cortex-A76AE" },
+ { 0xd13, "Cortex-R52" },
++{ 0xd15, "Cortex-R82" },
+ { 0xd20, "Cortex-M23" },
+ { 0xd21, "Cortex-M33" },
+ { 0xd40, "Neoverse-V1" },
+@@ -94,6 +95,7 @@ static
Bug#1085708: marked as done (bookworm-pu: package ninja-build/1.11.1-2~deb12u1)
Your message dated Sat, 09 Nov 2024 10:51:02 +
with message-id
and subject line Closing bugs released with 12.8
has caused the Debian Bug report #1085708,
regarding bookworm-pu: package ninja-build/1.11.1-2~deb12u1
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.)
--
1085708: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1085708
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
Tags: bookworm
User: release.debian@packages.debian.org
Usertags: pu
X-Debbugs-Cc: ninja-bu...@packages.debian.org
Control: affects -1 + src:ninja-build
[ Reason ]
ninja fails on 32 bit architectures with files that have a >32bit inode.
[ Impact ]
This mostly affects automated builds / CI systems since such
large inode numbers typically appear when using overlayfs.
[ Tests ]
* Builds fine on amd64 and i386 (including unit tests)
* autopkgtest runs fine on amd64
* Rebuilt a couple of reverse build-deps on i386 and amd64, no failures
* Simon has verified the fix is effective on bookworm
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041897#34
[ Risks ]
The change is pretty limited only touching stat() calls.
[ Checklist ]
[x] *all* changes are documented in the d/changelog
[x] I reviewed all changes and I approve them
[x] attach debdiff against the package in (old)stable
[x] the issue is verified as fixed in unstable
[ Changes ]
Cherry-pick upstream fix that essentially replaces stat() with stat64()
when largefile is enabled.
[ Other info ]
The change was already part of testing before it was replaced with a new
upstream version.
Thus I'm proposing a rebuild of that package.diff -Nru ninja-build-1.11.1/debian/changelog
ninja-build-1.11.1/debian/changelog
--- ninja-build-1.11.1/debian/changelog 2022-09-02 12:31:31.0 +0200
+++ ninja-build-1.11.1/debian/changelog 2024-10-19 18:02:37.0 +0200
@@ -1,3 +1,16 @@
+ninja-build (1.11.1-2~deb12u1) bookworm; urgency=medium
+
+ * Rebuild for bookworm.
+
+ -- Felix Geyer Sat, 19 Oct 2024 18:02:37 +0200
+
+ninja-build (1.11.1-2) unstable; urgency=medium
+
+ * Support large inode numbers on 32-bit systems. (Closes: #1041897)
+- Cherry-pick upstream commit as support_32bit_system_like_i386.patch
+
+ -- Felix Geyer Sun, 03 Sep 2023 16:34:04 +0200
+
ninja-build (1.11.1-1) unstable; urgency=medium
* New upstream release.
diff -Nru ninja-build-1.11.1/debian/patches/series
ninja-build-1.11.1/debian/patches/series
--- ninja-build-1.11.1/debian/patches/series1970-01-01 01:00:00.0
+0100
+++ ninja-build-1.11.1/debian/patches/series2024-10-19 18:02:30.0
+0200
@@ -0,0 +1 @@
+support_32bit_system_like_i386.patch
diff -Nru
ninja-build-1.11.1/debian/patches/support_32bit_system_like_i386.patch
ninja-build-1.11.1/debian/patches/support_32bit_system_like_i386.patch
--- ninja-build-1.11.1/debian/patches/support_32bit_system_like_i386.patch
1970-01-01 01:00:00.0 +0100
+++ ninja-build-1.11.1/debian/patches/support_32bit_system_like_i386.patch
2024-10-19 18:02:30.0 +0200
@@ -0,0 +1,187 @@
+From 7bba11ae704efc84cac5fde5e9be53f653f237d1 Mon Sep 17 00:00:00 2001
+From: Ma Aiguo
+Date: Sun, 9 Oct 2022 17:50:29 +0800
+Subject: [PATCH] support 32bit system like i386 (#829)
+
+---
+ src/build_log_test.cc | 6 +-
+ src/deps_log_test.cc | 43 ---
+ src/disk_interface.cc | 5 +
+ src/util.cc | 5 +
+ 4 files changed, 55 insertions(+), 4 deletions(-)
+
+diff --git a/src/build_log_test.cc b/src/build_log_test.cc
+index 37182994d2..f03100d809 100644
+--- a/src/build_log_test.cc
b/src/build_log_test.cc
+@@ -133,9 +133,13 @@ TEST_F(BuildLogTest, Truncate) {
+ log1.RecordCommand(state_.edges_[1], 20, 25);
+ log1.Close();
+ }
+-
++#ifdef __USE_LARGEFILE64
++ struct stat64 statbuf;
++ ASSERT_EQ(0, stat64(kTestFilename, &statbuf));
++#else
+ struct stat statbuf;
+ ASSERT_EQ(0, stat(kTestFilename, &statbuf));
++#endif
+ ASSERT_GT(statbuf.st_size, 0);
+
+ // For all possible truncations of the input file, assert that we don't
+diff --git a/src/deps_log_test.cc b/src/deps_log_test.cc
+index 13fcc788b6..cb1c925532 100644
+--- a/src/deps_log_test.cc
b/src/deps_log_test.cc
+@@ -138,9 +138,13 @@ TEST_F(DepsLogTest, DoubleEntry) {
+ deps.push_back(state.GetNode("bar.h", 0));
+ log.RecordDeps(state.GetNode("out.o", 0), 1, deps);
+ log.Close();
+-
++#ifdef __USE_LARGEFILE64
++struct stat64 st;
++ASSERT_E
Bug#1085711: marked as done (bookworm-pu: package libvirt/9.0.0-4+deb12u2)
Your message dated Sat, 09 Nov 2024 10:51:02 + with message-id and subject line Closing bugs released with 12.8 has caused the Debian Bug report #1085711, regarding bookworm-pu: package libvirt/9.0.0-4+deb12u2 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.) -- 1085711: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1085711 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: release.debian.org Severity: normal Tags: bookworm User: release.debian@packages.debian.org Usertags: pu X-Debbugs-Cc: libv...@packages.debian.org Control: affects -1 + src:libvirt [ Reason ] The update addresses two issues: the first one is * https://bugs.debian.org/1030926 while the other one isn't tracked on the BTS but has been reported to the upstream user list as * https://lists.libvirt.org/archives/list/us...@lists.libvirt.org/thread/QZ43KUTWO5UY2FLC5BMKKHA7CCCKJ3HI/ In both cases, the solution is a clean cherry-pick of a fix that has already been committed upstream. [ Impact ] If the update is not approved, i386 VMs will continue not working on Debian 12 unless AppArmor is disabled, and certain (admittedly uncommon) configurations will result in unbootable or even disappearing guests, particularly when upgrading from Debian 11. [ Tests ] The update was manually tested. I have also inspected the changes and confirmed that they make sense. For one of the backported patches, I am the original author. [ Risks ] The fixes are small and targeted, and have already been validated upstream. libvirt has an extremely high bar for breaking backwards compatibility, so the risk of that being an issue is very low. [ Checklist ] [x] *all* changes are documented in the d/changelog [x] I reviewed all changes and I approve them [x] attach debdiff against the package in stable [ ] the issue is verified as fixed in unstable About the last point. One of the issues (i386 VMs not working with AppArmor) doesn't actually reproduce in unstable, because the triggering factor is /usr/bin/qemu-system-i386 being a wrapper script, and that was only the case in Debian 12. The backported change is not in unstable right now, but will be once 10.9.0-1 is uploaded. This will happen in early November, right after the upstream release is published. It doesn't seem worthwhile to upload to unstable only to add a backport that is effectively a no-op for that version, or to delay the update until 12.9. Hopefully the Release Team agrees with this rationale. Cheers. -- Andrea Bolognani Resistance is futile, you will be garbage collected. diff -Nru libvirt-9.0.0/debian/changelog libvirt-9.0.0/debian/changelog --- libvirt-9.0.0/debian/changelog 2024-08-24 16:05:45.0 +0200 +++ libvirt-9.0.0/debian/changelog 2024-10-21 13:51:48.0 +0200 @@ -1,3 +1,14 @@ +libvirt (9.0.0-4+deb12u2) bookworm; urgency=medium + + * [275099d] patches: Add backports +- backport/apparmor-Allow-running-i686-VMs-on-Debian-12.patch + - Closes: #1030926 +- backport/qemu_process-Skip-over-non-virtio-non-TAP-NIC-[...] + - Prevents certain guests from becoming unbootable or +disappearing during upgrade + + -- Andrea Bolognani Mon, 21 Oct 2024 13:51:48 +0200 + libvirt (9.0.0-4+deb12u1) bookworm; urgency=medium [ Cyril Brulebois ] diff -Nru libvirt-9.0.0/debian/patches/backport/apparmor-Allow-running-i686-VMs-on-Debian-12.patch libvirt-9.0.0/debian/patches/backport/apparmor-Allow-running-i686-VMs-on-Debian-12.patch --- libvirt-9.0.0/debian/patches/backport/apparmor-Allow-running-i686-VMs-on-Debian-12.patch 1970-01-01 01:00:00.0 +0100 +++ libvirt-9.0.0/debian/patches/backport/apparmor-Allow-running-i686-VMs-on-Debian-12.patch 2024-10-21 13:51:48.0 +0200 @@ -0,0 +1,37 @@ +From: Andrea Bolognani +Date: Tue, 15 Oct 2024 11:50:36 +0200 +Subject: apparmor: Allow running i686 VMs on Debian 12 + +In Debian 12, the qemu-system-i386 binary in /usr/bin is a wrapper +script, with the actual executable living in /usr/libexec instead. +This makes it impossible to run i686 VMs when AppArmor is enabled. + +Allow running the actual binary. + +https://bugs.debian.org/1030926 + +Signed-off-by: Andrea Bolognani +Reviewed-by: Jim Fehlig +(cherry picked from commit 81493d8eb6ec5d3f063b0b5770df33ed656d6766) + +Forwarded: not-needed +Origin: https://gitlab.com/libvirt/libvirt/-/commit/81493d8eb6ec5d3f063b0b5770df33ed656d6766 +Bugs-Debian: https://bugs.debian.org/1030926 +--- + src/security/apparmor/libvirt-qemu | 3 +++ + 1 file changed, 3 insertions(+
Bug#1086149: marked as done (bookworm-pu: package ntfs-3g/2022.10.3-1+deb12u2)
Your message dated Sat, 09 Nov 2024 10:51:02 +
with message-id
and subject line Closing bugs released with 12.8
has caused the Debian Bug report #1086149,
regarding bookworm-pu: package ntfs-3g/2022.10.3-1+deb12u2
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.)
--
1086149: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1086149
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
Tags: bookworm
User: release.debian@packages.debian.org
Usertags: pu
X-Debbugs-Cc: ntfs...@packages.debian.org
Control: affects -1 + src:ntfs-3g
[ Reason ]
I overlooked a mistake back during the development of Bookworm. I have
fixed bug #983359 [1] which notes that pre-dependency on fuse3 is not
the correct way to have it for the working of ntfs-3g. But then, there
was already a newer version of it in Experimental due to a soname
change. I've uploaded that when I got a go for the transition - forgot
to merge the previous change.
Thus it was missing from Sid as well, but lately I have fixed this
there as well.
[ Impact ]
The package fuse3 might be removed (in case no other package depends
on it), thus breaking the use of ntfs-3g.
[ Tests ]
Builds fine on amd64.
[ Risks ]
Basically nothing.
[ Checklist ]
[x] *all* changes are documented in the d/changelog
[x] I reviewed all changes and I approve them
[x] attach debdiff against the package in stable
[x] the issue is verified as fixed in unstable
[ Changes ]
Move the fuse3 pre-dependency to dependency, only d/control changed
(expect d/changelog of course).
Thanks for considering,
Laszlo/GCS
[1] https://bugs.debian.org/983359
diff -Nru ntfs-3g-2022.10.3/debian/changelog ntfs-3g-2022.10.3/debian/changelog
--- ntfs-3g-2022.10.3/debian/changelog 2024-06-23 14:34:22.0 +0200
+++ ntfs-3g-2022.10.3/debian/changelog 2024-10-27 15:16:10.0 +0100
@@ -1,3 +1,9 @@
+ntfs-3g (1:2022.10.3-1+deb12u2) bookworm; urgency=medium
+
+ * Move fuse to simple dependency (closes: #983359).
+
+ -- Laszlo Boszormenyi (GCS) Sun, 27 Oct 2024 15:16:10 +0100
+
ntfs-3g (1:2022.10.3-1+deb12u1) bookworm; urgency=medium
* Fix use-after-free in 'ntfs_uppercase_mbs' (CVE-2023-52890)
diff -Nru ntfs-3g-2022.10.3/debian/control ntfs-3g-2022.10.3/debian/control
--- ntfs-3g-2022.10.3/debian/control 2022-10-31 15:14:06.0 +0100
+++ ntfs-3g-2022.10.3/debian/control 2024-10-27 15:16:10.0 +0100
@@ -15,14 +15,12 @@
Package: ntfs-3g
Section: otherosfs
Architecture: linux-any kfreebsd-any
-Pre-Depends:
- ${misc:Pre-Depends},
- fuse3 [linux-any],
- fuse4bsd [kfreebsd-any],
Depends:
${misc:Depends},
${shlibs:Depends},
- libntfs-3g89 (= ${binary:Version})
+ libntfs-3g89 (= ${binary:Version}),
+ fuse3 [linux-any],
+ fuse4bsd [kfreebsd-any]
#Provides: ${ntfs-3g:Provides}
Description: read/write NTFS driver for FUSE
NTFS-3G uses FUSE (Filesystem in Userspace) to provide support for the NTFS
--- End Message ---
--- Begin Message ---
Source: release.debian.org
Version: 12.8
Hi,
Each of the updates tracked by these bugs was included in today's 12.8
bookworm point release.
Regards,
Adam--- End Message ---
Bug#1086116: marked as done (bookworm-pu: package gtk+3.0/3.24.38-2~deb12u3)
Your message dated Sat, 09 Nov 2024 10:51:02 + with message-id and subject line Closing bugs released with 12.8 has caused the Debian Bug report #1086116, regarding bookworm-pu: package gtk+3.0/3.24.38-2~deb12u3 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.) -- 1086116: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1086116 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: release.debian.org Severity: normal Tags: bookworm X-Debbugs-Cc: gtk+...@packages.debian.org Control: affects -1 + src:gtk+3.0 User: release.debian@packages.debian.org Usertags: pu Hello, I have uploaded gtk+3.0/3.24.38-2~deb12u3 which I'd like to see go into bookworm. [ Reason ] As detailed in bug Bug#1084489, the version of gtk3 in bookworm is still using a focus event that was deprecated a long time ago. Newer versions of the Orca screen reader for blind people recently migrated to dropping the support for these old events. This means that when users try to use more recent Orca versions (to improve screen reading for various applications), they get strong regressions. So it's not a regression in stable itself, but it is preventing users from using a more recent version of Orca (to improve the mere usage of their computer), such as from bookworm-backports or directly from upstream Orca. [ Impact ] With a newer version of Orca, some actions of the user do not get audible feedback to the user, thus leaving the user quite lost in what is happening, notably in combo-boxes, gnome-terminal tabs, and others. [ Tests ] This fix was tested by an end user. [ Risks ] The code is very trivial [ Checklist ] [X] *all* changes are documented in the d/changelog [X] I reviewed all changes and I approve them [X] attach debdiff against the package in (old)stable [X] the issue is verified as fixed in unstable [ Changes ] It replaces calling the deprecated atk_focus_tracker_notify (atk_obj); with calling atk_object_notify_state_change (atk_obj, ATK_STATE_FOCUSED, TRUE); as it should since like a decade. diff -Nru gtk+3.0-3.24.38/debian/changelog gtk+3.0-3.24.38/debian/changelog --- gtk+3.0-3.24.38/debian/changelog2024-07-19 12:57:06.0 +0200 +++ gtk+3.0-3.24.38/debian/changelog2024-10-25 20:17:45.0 +0200 @@ -1,3 +1,11 @@ +gtk+3.0 (3.24.38-2~deb12u3) bookworm; urgency=medium + + * Non-maintainer upload. + * d/p/atk_focus_tracker_notify.deprecated.patch: Fix letting Orca announce +initial focus (Closes: #1084489) + + -- Samuel Thibault Fri, 25 Oct 2024 20:17:45 +0200 + gtk+3.0 (3.24.38-2~deb12u2) bookworm; urgency=medium * d/p/Stop-looking-for-modules-in-cwd.patch: diff -Nru gtk+3.0-3.24.38/debian/patches/atk_focus_tracker_notify.deprecated.patch gtk+3.0-3.24.38/debian/patches/atk_focus_tracker_notify.deprecated.patch --- gtk+3.0-3.24.38/debian/patches/atk_focus_tracker_notify.deprecated.patch 1970-01-01 01:00:00.0 +0100 +++ gtk+3.0-3.24.38/debian/patches/atk_focus_tracker_notify.deprecated.patch 2024-10-25 20:15:00.0 +0200 @@ -0,0 +1,61 @@ +From 5147e95d1d6a02212b1f51c2cc0a61653425850a Mon Sep 17 00:00:00 2001 +From: Michael Weghorn +Date: Wed, 8 May 2024 11:32:27 +0200 +Subject: [PATCH] a11y: Port from deprecated atk_focus_tracker_notify + +Port `gail_focus_notify` from using the deprecated +`atk_focus_tracker_notify` to notify about the new +focus object. Notify of a state of the focused state +instead, as suggested in the +`atk_focus_tracker_notify` doc [1]. + +Using the deprecated function e.g. resulted in +the Orca screen reader no longer announcing +initial focus on editable comboboxes in +LibreOffice Writer's toolbars after Orca dropped +support for the deprecated "focus" AT-SPI event +in this commit [2]: + +commit 9e2902dd46c7e583a097e235dfd7e3c50b016383 +Author: Joanmarie Diggs +Date: Wed May 1 12:14:07 2024 +0200 + +Remove the on_focus handler for the LibreOffice script + +The "focus:" event was deprecated many years ago. If the expected +"object:state-changed:focused" event is absent, that bug should +be fixed. + +This commit makes the announcement work again. + +It also fixes the scenario described in [3]. + +[1] https://docs.gtk.org/atk/func.focus_tracker_notify.html +[2] https://gitlab.gnome.org/GNOME/orca/-/commit/9e2902dd46c7e583a097e235dfd7e3c50b016383 +[3] https://gitlab.gnome.org/GNOME/gtk/-/issues/454#note_2099344 + +Fixes: #454 +--- + gtk/a11y/gtkaccessibility.c | 4 +--- + 1 file changed, 1 insertion(+), 3 deletions(-)
Bug#1085965: marked as done (bookworm-pu: package distro-info-data/0.58+deb12u3)
Your message dated Sat, 09 Nov 2024 10:51:02 + with message-id and subject line Closing bugs released with 12.8 has caused the Debian Bug report #1085965, regarding bookworm-pu: package distro-info-data/0.58+deb12u3 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.) -- 1085965: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1085965 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: release.debian.org Severity: normal Tags: bookworm X-Debbugs-Cc: distro-info-d...@packages.debian.org Control: affects -1 + src:distro-info-data User: release.debian@packages.debian.org Usertags: pu [ Reason ] Run of the mill distro-info-data update, adding an Ubuntu release. [ Impact ] Ubuntu release data will be out of date. [ Tests ] Automated syntax checks and some smoketests for historical data. Manually verified that the Ubuntu release is known. [ Risks ] Minimal risk data update. [ Checklist ] [X] *all* changes are documented in the d/changelog [X] I reviewed all changes and I approve them [X] attach debdiff against the package in (old)stable [X] the issue is verified as fixed in unstable [ Changes ] Add Ubuntu 25.04 "Plucky Puffin" diff -Nru distro-info-data-0.58+deb12u2/debian/changelog distro-info-data-0.58+deb12u3/debian/changelog --- distro-info-data-0.58+deb12u2/debian/changelog 2024-04-30 17:41:56.0 -0700 +++ distro-info-data-0.58+deb12u3/debian/changelog 2024-10-23 18:58:20.0 -0700 @@ -1,3 +1,10 @@ +distro-info-data (0.58+deb12u3) bookworm; urgency=medium + + * Update data to 0.63: +- Add Ubuntu 25.04 "Plucky Puffin" (LP: #2084572) + + -- Stefano Rivera Wed, 23 Oct 2024 18:58:20 -0700 + distro-info-data (0.58+deb12u2) bookworm; urgency=medium * Update data to 0.61: diff -Nru distro-info-data-0.58+deb12u2/ubuntu.csv distro-info-data-0.58+deb12u3/ubuntu.csv --- distro-info-data-0.58+deb12u2/ubuntu.csv2024-04-30 17:41:56.0 -0700 +++ distro-info-data-0.58+deb12u3/ubuntu.csv2024-10-23 18:58:20.0 -0700 @@ -40,3 +40,4 @@ 23.10,Mantic Minotaur,mantic,2023-04-20,2023-10-12,2024-07-11 24.04 LTS,Noble Numbat,noble,2023-10-12,2024-04-25,2029-05-31,2029-05-31,2034-04-25 24.10,Oracular Oriole,oracular,2024-04-25,2024-10-10,2025-07-10 +25.04,Plucky Puffin,plucky,2024-10-10,2025-04-17,2026-01-15 --- End Message --- --- Begin Message --- Source: release.debian.org Version: 12.8 Hi, Each of the updates tracked by these bugs was included in today's 12.8 bookworm point release. Regards, Adam--- End Message ---
Bug#1085591: marked as done (bookworm-pu: package lgogdownloader/3.9-2)
Your message dated Sat, 09 Nov 2024 10:51:02 +
with message-id
and subject line Closing bugs released with 12.8
has caused the Debian Bug report #1085591,
regarding bookworm-pu: package lgogdownloader/3.9-2
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1085591: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1085591
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
Tags: bookworm
User: release.debian@packages.debian.org
Usertags: pu
Dear release team,
[ Reason ]
The version of lgogdownloader in stable crashes with current URLs used
in GOG; see #1085527 for an example. This renders the package
unusable.
[ Impact ]
Users can no longer download artifacts using lgogdownloader, which is
the package’s sole purpose.
[ Tests ]
The proposed fix is the fix implemented upstream; see
https://github.com/Sude-/lgogdownloader/issues/279 for details. The
patches apply as-is to the version in Bookworm; see
https://github.com/Sude-/lgogdownloader/commit/52b8bdc8fa0028bcb875c6a723c6e04deeecbcb8
and
https://github.com/Sude-/lgogdownloader/commit/6556dc6a82b4e3d64ef1a7940736be3a7b2ac956
The fix is already available in unstable (it’s included in version
3.15) and works there. 3.9 with these patches builds and works fine; I
can reproduce the bug and verify that the suggested patch fixes it.
[ Risks ]
The fix seems straightforward enough to me. In any case the package is
already broken, making it worse won’t make the situation worse for
users.
[ Checklist ]
[x] *all* changes are documented in the d/changelog
[x] I reviewed all changes and I approve them
[x] attach debdiff against the package in (old)stable
[x] the issue is verified as fixed in unstable
[ Changes ]
The changes add a number of checks to the
galaxyAPI::getPathFromDownloadUrl function to handle new components
found in URLs.
[ Other info ]
Nothing I can think of!
Regards,
Stephen
diff --git a/debian/changelog b/debian/changelog
index a798d46..1cb1f94 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,9 @@
+lgogdownloader (3.9-2+deb12u1) bookworm; urgency=medium
+
+ * Apply upstream fixes for parsing Galaxy URLs. Closes: #1085527.
+
+ -- Stephen Kitt Sun, 20 Oct 2024 21:39:20 +0200
+
lgogdownloader (3.9-2) unstable; urgency=medium
* qtwebengine5-dev is now available on mips64el, use it there. Thanks
diff --git a/debian/patches/galaxy-urls-1.patch
b/debian/patches/galaxy-urls-1.patch
new file mode 100644
index 000..bcc5a24
--- /dev/null
+++ b/debian/patches/galaxy-urls-1.patch
@@ -0,0 +1,24 @@
+commit 52b8bdc8fa0028bcb875c6a723c6e04deeecbcb8
+Author: Sude
+Date: Thu Aug 22 18:13:44 2024 +0300
+
+Fix galaxyAPI::getPathFromDownlinkUrl with Fastly CDN urls
+
+Fastly CDN urls don't contain query strings
+
+diff --git a/src/galaxyapi.cpp b/src/galaxyapi.cpp
+index 56d5745..7699d69 100644
+--- a/src/galaxyapi.cpp
b/src/galaxyapi.cpp
+@@ -567,6 +567,11 @@ std::string galaxyAPI::getPathFromDownlinkUrl(const
std::string& downlink_url, c
+ else
+ filename_end_pos = downlink_url_unescaped.find_first_of("?");
+
++// Downlink doesn't contain "?path=" or "?"
++// Set end pos to length
++if (filename_end_pos == std::string::npos)
++filename_end_pos = downlink_url_unescaped.length();
++
+ if (downlink_url_unescaped.find("/" + gamename + "/") !=
std::string::npos)
+ {
+
path.assign(downlink_url_unescaped.begin()+downlink_url_unescaped.find("/" +
gamename + "/"), downlink_url_unescaped.begin()+filename_end_pos);
diff --git a/debian/patches/galaxy-urls-2.patch
b/debian/patches/galaxy-urls-2.patch
new file mode 100644
index 000..8d32f26
--- /dev/null
+++ b/debian/patches/galaxy-urls-2.patch
@@ -0,0 +1,88 @@
+commit 6556dc6a82b4e3d64ef1a7940736be3a7b2ac956
+Author: Sude
+Date: Thu Aug 22 21:50:23 2024 +0300
+
+Add more checks to galaxyAPI::getPathFromDownlinkUrl
+
+diff --git a/src/galaxyapi.cpp b/src/galaxyapi.cpp
+index 7699d69..716ebdd 100644
+--- a/src/galaxyapi.cpp
b/src/galaxyapi.cpp
+@@ -547,40 +547,51 @@ std::string galaxyAPI::getPathFromDownlinkUrl(const
std::string& downlink_url, c
+ {
+ std::string path;
+ std::string downlink_url_unescaped =
(std::string)curl_easy_unescape(curlhandle, downlink_url.c_str(),
downlink_url.size(), NULL);
++size_t filename_start_pos = 0;
+
+-// GOG has changed the url formatting few times between 2 different
formats.
+-
Bug#1084171: marked as done (bookworm-pu: package 7zip/22.01+dfsg-8+deb12u1)
Your message dated Sat, 09 Nov 2024 10:51:02 +
with message-id
and subject line Closing bugs released with 12.8
has caused the Debian Bug report #1084171,
regarding bookworm-pu: package 7zip/22.01+dfsg-8+deb12u1
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.)
--
1084171: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1084171
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
Tags: bookworm security
X-Debbugs-Cc: 7...@packages.debian.org, t...@security.debian.org,
yokota.h...@gmail.com
Control: affects -1 + src:7zip
User: release.debian@packages.debian.org
Usertags: pu
[ Reason ]
Fix CVE-2023-52168 (buffer overflow) and CVE-2023-52169 (buffer over-read)
[ Impact ]
Some vulnerabilities are unfixed.
[ Tests ]
Very trivial NTFS disk image file test was passed.
* list files
* extract files
[ Risks ]
Upstream dose not provide fix patch.
So I extract fix patch from CVE reporter's blog entry.
> https://dfir.ru/2024/06/19/vulnerabilities-in-7-zip-and-ntfs3/
I think the fix patch will works, but not confirmed by upstream
because upstream dose not provides fix patch files.
[ Checklist ]
[x] *all* changes are documented in the d/changelog
[x] I reviewed all changes and I approve them
[x] attach debdiff against the package in (old)stable
[x] the issue is verified as fixed in unstable
[ Changes ]
Add fix-ups to NTFS extractor.
[ Other info ]
CVE Reporter's blog entry:
> https://dfir.ru/2024/06/19/vulnerabilities-in-7-zip-and-ntfs3/
Debdiff can be examine from online:
> https://salsa.debian.org/debian/7zip/-/tree/bookworm-update
>
https://salsa.debian.org/debian/7zip/-/commits/33950db8e8c9130ac6718fde10515c74f9c6cecc
Roger Shimizu provides bookworm-backports package
7zip:24.08+dfsg-1~bpo12+1.
7zip 24.08 already fixed the vulnerabilities by upstream since 24.05.
--
YOKOTA Hiroshi
diff -Nru 7zip-22.01+dfsg/debian/changelog 7zip-22.01+dfsg/debian/changelog
--- 7zip-22.01+dfsg/debian/changelog2022-12-18 21:09:42.0 +0900
+++ 7zip-22.01+dfsg/debian/changelog2024-10-06 11:40:03.0 +0900
@@ -1,3 +1,9 @@
+7zip (22.01+dfsg-8+deb12u1) bookworm; urgency=medium
+
+ * Fix CVE-2023-52168 and CVE-2023-52169
+
+ -- YOKOTA Hiroshi Sun, 06 Oct 2024 11:40:03 +0900
+
7zip (22.01+dfsg-8) unstable; urgency=medium
* Upgrade Debian standards
diff -Nru
7zip-22.01+dfsg/debian/patches/0009-Fix-CVE-2023-52168-and-CVE-2023-52169.patch
7zip-22.01+dfsg/debian/patches/0009-Fix-CVE-2023-52168-and-CVE-2023-52169.patch
---
7zip-22.01+dfsg/debian/patches/0009-Fix-CVE-2023-52168-and-CVE-2023-52169.patch
1970-01-01 09:00:00.0 +0900
+++
7zip-22.01+dfsg/debian/patches/0009-Fix-CVE-2023-52168-and-CVE-2023-52169.patch
2024-10-06 11:40:03.0 +0900
@@ -0,0 +1,146 @@
+From: YOKOTA Hiroshi
+Date: Wed, 2 Oct 2024 12:09:49 +0900
+Subject: Fix CVE-2023-52168 and CVE-2023-52169
+
+Bug-Debian: https://security-tracker.debian.org/tracker/CVE-2023-52168
+Bug-Debian: https://security-tracker.debian.org/tracker/CVE-2023-52169
+Forwarded: not-needed
+
+This patch was extracted from reporter's blog and
+upstream/23.01..upstream/24.05 diff.
+> https://dfir.ru/2024/06/19/vulnerabilities-in-7-zip-and-ntfs3/
+---
+ CPP/7zip/Archive/NtfsHandler.cpp | 89 +---
+ 1 file changed, 57 insertions(+), 32 deletions(-)
+
+diff --git a/CPP/7zip/Archive/NtfsHandler.cpp
b/CPP/7zip/Archive/NtfsHandler.cpp
+index 0b9ee29..39a1299 100755
+--- a/CPP/7zip/Archive/NtfsHandler.cpp
b/CPP/7zip/Archive/NtfsHandler.cpp
+@@ -71,6 +71,7 @@ struct CHeader
+ {
+ unsigned SectorSizeLog;
+ unsigned ClusterSizeLog;
++ unsigned MftRecordSizeLog;
+ // Byte MediaType;
+ UInt32 NumHiddenSectors;
+ UInt64 NumSectors;
+@@ -156,14 +157,47 @@ bool CHeader::Parse(const Byte *p)
+
+ NumClusters = NumSectors >> sectorsPerClusterLog;
+
+- G64(p + 0x30, MftCluster);
++ G64(p + 0x30, MftCluster); // $MFT.
+ // G64(p + 0x38, Mft2Cluster);
+- G64(p + 0x48, SerialNumber);
+- UInt32 numClustersInMftRec;
+- UInt32 numClustersInIndexBlock;
+- G32(p + 0x40, numClustersInMftRec); // -10 means 2 ^10 = 1024 bytes.
+- G32(p + 0x44, numClustersInIndexBlock);
+- return (numClustersInMftRec < 256 && numClustersInIndexBlock < 256);
++ G64(p + 0x48, SerialNumber); // $MFTMirr
++
++ /*
++numClusters_per_MftRecord:
++numClusters_per_IndexBlock:
++only low byte from 4 bytes is used. Another 3 high bytes are zeros.
++ If the number is positive (number <
Bug#1085430: marked as done (bookworm-pu: package xfpt/0.11-1+deb12u1)
Your message dated Sat, 09 Nov 2024 10:51:02 +
with message-id
and subject line Closing bugs released with 12.8
has caused the Debian Bug report #1085430,
regarding bookworm-pu: package xfpt/0.11-1+deb12u1
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.)
--
1085430: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1085430
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
Tags: bookworm
X-Debbugs-Cc: x...@packages.debian.org
Control: affects -1 + src:xfpt
User: release.debian@packages.debian.org
Usertags: pu
Hello,
I would like to fix a minor security issue (#1080219 CVE-2024-43700) in
stable, no DSA is planned.
[ Checklist ]
[x] *all* changes are documented in the d/changelog
[x] I reviewed all changes and I approve them
[x] attach debdiff against the package in (old)stable
[x] the issue is verified as fixed in unstable
This is pretty straightforward cherry-pick of the upstream change, just
dropping some noise (copyright year and version bump.)
cu Andreas
--
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'
diff -Nru xfpt-0.11/debian/changelog xfpt-0.11/debian/changelog
--- xfpt-0.11/debian/changelog 2020-09-18 11:13:36.0 +0200
+++ xfpt-0.11/debian/changelog 2024-10-19 13:32:57.0 +0200
@@ -1,3 +1,11 @@
+xfpt (0.11-1+deb12u1) bookworm; urgency=medium
+
+ * Cherry-pick 30-Diagnose-error-if-macro-expansion-makes-a-line-too-l.patch
+from upstream GIT master to fix buffer overflow CVE-2024-43700.
+Closes: #1080219
+
+ -- Andreas Metzler Sat, 19 Oct 2024 13:32:57 +0200
+
xfpt (0.11-1) unstable; urgency=low
* Fix watchfile (report functionality).
diff -Nru xfpt-0.11/debian/patches/30-Diagnose-error-if-macro-expansion-makes-a-line-too-l.patch xfpt-0.11/debian/patches/30-Diagnose-error-if-macro-expansion-makes-a-line-too-l.patch
--- xfpt-0.11/debian/patches/30-Diagnose-error-if-macro-expansion-makes-a-line-too-l.patch 1970-01-01 01:00:00.0 +0100
+++ xfpt-0.11/debian/patches/30-Diagnose-error-if-macro-expansion-makes-a-line-too-l.patch 2024-10-19 13:32:57.0 +0200
@@ -0,0 +1,280 @@
+From a690304bbd3fd19e9dfdad50dcc87ad829f744e4 Mon Sep 17 00:00:00 2001
+From: Philip Hazel
+Date: Sun, 11 Aug 2024 17:43:41 +0100
+Subject: [PATCH] Diagnose error if macro expansion makes a line too long for
+ its buffer
+
+---
+ ChangeLog| 7 +++
+ src/dot.c| 9 +++--
+ src/error.c | 7 ---
+ src/functions.h | 4 ++--
+ src/globals.c| 4 ++--
+ src/para.c | 5 +++--
+ src/read.c | 27 +--
+ src/structs.h| 3 ++-
+ testing/infiles/07 | 5 +
+ testing/outfiles/07 | 1 +
+ testing/outfiles/07.err | 4
+ testing/outfiles/cmd.err | 2 +-
+ 12 files changed, 59 insertions(+), 19 deletions(-)
+ create mode 100644 testing/infiles/07
+ create mode 100644 testing/outfiles/07
+ create mode 100644 testing/outfiles/07.err
+
+--- a/src/dot.c
b/src/dot.c
+@@ -467,10 +467,11 @@ while (*p != 0)
+ argstr *as = misc_malloc(sizeof(argstr));
+ as->next = NULL;
+ *pp = as;
+ pp = &(as->next);
+ as->string = misc_readitem(p, NULL, &length, NULL, 0);
++ as->length = length;
+ p += length;
+ }
+
+ pp = &(md->lines);
+ for (;;)
+@@ -488,21 +489,24 @@ for (;;)
+
+ as = misc_malloc(sizeof(argstr));
+ as->next = NULL;
+ *pp = as;
+ pp = &(as->next);
+- as->string = misc_copystring(line, Ustrlen(line));
++ length = Ustrlen(line);
++ as->string = misc_copystring(line, length);
++ as->length = length;
+ }
+
+ /* If there aren't any replacement lines, fake up a comment so that there's
+ always something for a macro to generate. */
+
+ if (md->lines == NULL)
+ {
+ md->lines = misc_malloc(sizeof(argstr));
+ md->lines->next = NULL;
+ md->lines->string = misc_copystring(US". Dummy line\n", 13);
++ md->lines->length = 13;
+ }
+ }
+
+
+
+@@ -900,10 +904,11 @@ while (*p != 0)
+ argstr *as = misc_malloc(sizeof(argstr));
+ as->next = NULL;
+ *pp = as;
+ pp = &(as->next);
+ as->string = misc_readitem(p, NULL, &length, NULL, 0);
++ as->length = length;
+ p += length;
+ }
+ }
+
+ /* End of dot.c */
+--- a/src/error.c
b/src/error.c
+@@ -78,11 +78,12 @@ static error_struct error_data[] = {
+ { ec_seri
Bug#1085176: marked as done (bookworm-pu: package lemonldap-ng/2.16.1+ds-deb12u3)
Your message dated Sat, 09 Nov 2024 10:51:02 +
with message-id
and subject line Closing bugs released with 12.8
has caused the Debian Bug report #1085176,
regarding bookworm-pu: package lemonldap-ng/2.16.1+ds-deb12u3
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.)
--
1085176: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1085176
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
Tags: bookworm
X-Debbugs-Cc: lemonldap...@packages.debian.org, y...@debian.org
Control: affects -1 + src:lemonldap-ng
User: release.debian@packages.debian.org
Usertags: pu
[ Reason ]
Lemonldap-ng <2.20.0 is vulnerable to a XSS injection (#1084979,
CVE-2024-48933)
[ Impact ]
Low security issue unless admin change default regex for logins
[ Tests ]
Passed
[ Risks ]
Low risk, patch is trivial
[ Checklist ]
[X] *all* changes are documented in the d/changelog
[X] I reviewed all changes and I approve them
[X] attach debdiff against the package in (old)stable
[X] the issue is verified as fixed in unstable
[ Changes ]
Add HTML escapes and change autofocus
Cheers,
Xavier
diff --git a/debian/NEWS b/debian/NEWS
index 0bb3cc914..0b5732a86 100644
--- a/debian/NEWS
+++ b/debian/NEWS
@@ -1,3 +1,16 @@
+lemonldap-ng (2.16.1+ds-deb12u3) UNRELEASED; urgency=medium
+
+ Custom templates maybe vulnerable to XSS injection when default allowed
+ characters have been changed. To fix this, replace every
+
+
+
+ by
+
+
+
+ -- Yadd Tue, 15 Oct 2024 19:27:47 +0200
+
lemonldap-ng (2.16.1+ds-deb12u2) bookworm; urgency=medium
A feature of OIDC allows the OpenID Provider to fetch the Authorization
diff --git a/debian/changelog b/debian/changelog
index 148164a94..c0bc25b80 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,9 @@
+lemonldap-ng (2.16.1+ds-deb12u3) bookworm; urgency=medium
+
+ * Fix XSS issue (Closes: #1084979, CVE-2024-48933)
+
+ -- Yadd Tue, 15 Oct 2024 20:59:06 +0200
+
lemonldap-ng (2.16.1+ds-deb12u2) bookworm; urgency=medium
* Fix open redirection when OIDC RP has no redirect uris
diff --git a/debian/patches/CVE-2024-48933.patch
b/debian/patches/CVE-2024-48933.patch
new file mode 100644
index 0..eb666a0dd
--- /dev/null
+++ b/debian/patches/CVE-2024-48933.patch
@@ -0,0 +1,117 @@
+Description: Fix XSS vulnerability
+ A cross-site scripting (XSS) vulnerability in LemonLDAP::NG before 2.19.3
+ allows remote attackers to inject arbitrary web script or HTML into the
+ login page via a username if userControl has been set to a non-default
+ value that allows special HTML characters.
+Author: Maxime Besson
+Bug: https://gitlab.ow2.org/lemonldap-ng/lemonldap-ng/-/issues/3232
+Bug-Debian: https://bugs.debian.org/1084979
+Forwarded: not-needed
+Applied-Upstream: 2.20.0,
https://gitlab.ow2.org/lemonldap-ng/lemonldap-ng/-/merge_requests/606
+Reviewed-By: Yadd
+Last-Update: 2024-10-15
+
+--- a/lemonldap-ng-portal/site/coffee/portal.coffee
b/lemonldap-ng-portal/site/coffee/portal.coffee
+@@ -295,12 +295,9 @@
+ if datas['choicetab']
+ authMenuTabs.tabs "option", "active", $('#authMenu a[href="#' +
datas['choicetab'] + '"]').parent().index()
+
+- if datas['login']
+- $("input[type=password]:first").focus()
+- else
+- # If there are no auto-focused fields, focus on first visible
input
+- if $("input[autofocus]").length == 0
+- $("input[type!=hidden]:first").focus();
++ # If there are no auto-focused fields, focus on first visible input
++ if $("input[autofocus]").length == 0
++ $("input[type!=hidden]:first").focus()
+
+ # Open links in new windows if required
+ if datas['newwindow']
+--- a/lemonldap-ng-portal/site/templates/bootstrap/checkuser.tpl
b/lemonldap-ng-portal/site/templates/bootstrap/checkuser.tpl
+@@ -11,7 +11,7 @@
+
+
+
+-" trplaceholder="user" aria-required="true"/>
++" trplaceholder="user"
aria-required="true"/>
+
+
+
+--- a/lemonldap-ng-portal/site/templates/bootstrap/globallogout.tpl
b/lemonldap-ng-portal/site/templates/bootstrap/globallogout.tpl
+@@ -6,7 +6,7 @@
+
+
+
+- ACTIVE SSO SESSIONS:
++ ACTIVE SSO SESSIONS:
+
+
+
+--- a/lemonldap-ng-portal/
Bug#1085026: marked as done (bookworm-pu: package docker.io/20.10.24+dfsg1+deb12u1)
Your message dated Sat, 09 Nov 2024 10:51:02 + with message-id and subject line Closing bugs released with 12.8 has caused the Debian Bug report #1085026, regarding bookworm-pu: package docker.io/20.10.24+dfsg1+deb12u1 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.) -- 1085026: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1085026 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: release.debian.org Severity: normal Tags: bookworm X-Debbugs-Cc: docker...@packages.debian.org, secur...@debian.org Control: affects -1 + src:docker.io User: release.debian@packages.debian.org Usertags: pu Control: tags -1 + security [ Reason ] CVE-2024-41110 [ Impact ] Authentification bypass [ Tests ] Yes added to test suite [ Risks ] Low code is tested. Patch is official [ Checklist ] [X] *all* changes are documented in the d/changelog [X] I reviewed all changes and I approve them [X] attach debdiff against the package in (old)stable [X] the issue is verified as fixed in unstable [ Changes ] - Fix CVE-2024-41110 - Fix of salsaCI to bookworm [ Other info ] May be worth a DSA due to popcon diff -Nru docker.io-20.10.24+dfsg1/debian/changelog docker.io-20.10.24+dfsg1/debian/changelog --- docker.io-20.10.24+dfsg1/debian/changelog 2023-04-05 15:19:59.0 + +++ docker.io-20.10.24+dfsg1/debian/changelog 2024-10-12 15:19:49.0 + @@ -1,3 +1,15 @@ +docker.io (20.10.24+dfsg1-1+deb12u1) bookworm-security; urgency=high + + * Team upload + * Fix CVE-2024-41110: Authz zero length regression +A security vulnerability has been detected in Docker Engine, +which could allow an attacker +to bypass authorization plugins (AuthZ) under specific +circumstances. The base likelihood of this being exploited is low. +(Closes: #1084993) + + -- Bastien Roucari??s Sat, 12 Oct 2024 15:19:49 + + docker.io (20.10.24+dfsg1-1) unstable; urgency=medium * Team upload. diff -Nru docker.io-20.10.24+dfsg1/debian/gbp.conf docker.io-20.10.24+dfsg1/debian/gbp.conf --- docker.io-20.10.24+dfsg1/debian/gbp.conf 2023-01-14 08:55:59.0 + +++ docker.io-20.10.24+dfsg1/debian/gbp.conf 2024-10-12 15:19:49.0 + @@ -1,2 +1,2 @@ [DEFAULT] -debian-branch = master +debian-branch = debian/bookworm diff -Nru docker.io-20.10.24+dfsg1/debian/.gitlab-ci.yml docker.io-20.10.24+dfsg1/debian/.gitlab-ci.yml --- docker.io-20.10.24+dfsg1/debian/.gitlab-ci.yml 2023-01-14 08:55:59.0 + +++ docker.io-20.10.24+dfsg1/debian/.gitlab-ci.yml 1970-01-01 00:00:00.0 + @@ -1,29 +0,0 @@ -# https://docs.gitlab.com/ce/ci/yaml/#include -include: - - remote: https://salsa.debian.org/onlyjob/ci/raw/master/onlyjob-ci.yml - -## "amd64-unstable" always runs by default followed by lintian. - -## Only for arch:all packages: -binary-indep: - extends: .build-indep - -## Job to check Build-Depends versioning: -amd64-testing_unstable: - extends: .build - variables: -arch: amd64 -dist: testing_unstable - -i386-unstable: - extends: .build - variables: -arch: i386 -dist: unstable - -amd64-experimental: - extends: .build - variables: -arch: amd64 -dist: experimental diff -Nru docker.io-20.10.24+dfsg1/debian/gitlab-ci.yml docker.io-20.10.24+dfsg1/debian/gitlab-ci.yml --- docker.io-20.10.24+dfsg1/debian/gitlab-ci.yml 2023-01-14 08:55:59.0 + +++ docker.io-20.10.24+dfsg1/debian/gitlab-ci.yml 2024-10-12 15:19:49.0 + @@ -4,3 +4,5 @@ --- include: - https://salsa.debian.org/go-team/infra/pkg-go-tools/-/raw/master/pipeline/test-archive.yml +variables: + RELEASE: 'bookworm' diff -Nru docker.io-20.10.24+dfsg1/debian/patches/CVE-2024-41110.patch docker.io-20.10.24+dfsg1/debian/patches/CVE-2024-41110.patch --- docker.io-20.10.24+dfsg1/debian/patches/CVE-2024-41110.patch 1970-01-01 00:00:00.0 + +++ docker.io-20.10.24+dfsg1/debian/patches/CVE-2024-41110.patch 2024-10-12 15:19:49.0 + @@ -0,0 +1,180 @@ +From 88c4b7690840044ce15489699294ec7c5dadf5dd Mon Sep 17 00:00:00 2001 +From: Jameson Hyde +Date: Mon, 26 Nov 2018 14:15:22 -0500 +Subject: CVE-2024-41110 [PATCH] Authz plugin security fixes for 0-length content and path + validation Signed-off-by: Jameson Hyde +MIME-Version: 1.0 +Content-Type: text/plain; charset=UTF-8 +Content-Transfer-Encoding: 8bit + +fix comments + +[debian description] +A security vulnerability has been detected in certain versions of Docker Engine, +which could allow an attacker to bypass authorization plugins (AuthZ) +under specific circumstances. The bas
Bug#1085281: marked as done (bookworm-pu: package btrfs-progs/6.2-1.1+deb12u1)
Your message dated Sat, 09 Nov 2024 10:51:02 + with message-id and subject line Closing bugs released with 12.8 has caused the Debian Bug report #1085281, regarding bookworm-pu: package btrfs-progs/6.2-1.1+deb12u1 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.) -- 1085281: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1085281 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: release.debian.org Severity: normal Tags: bookworm User: release.debian@packages.debian.org Usertags: pu X-Debbugs-Cc: btrfs-pr...@packages.debian.org, h...@bupt.moe Control: affects -1 + src:btrfs-progs Control: block 1085207 by -1 [ Reason ] btrfs-convert <= 6.3.1 has a long existing bug that produces bad chksum when converting from ext4 [1][2][3]. Although data is not corrupted, the checksum errors are not easy to fix. And users would get lots of complaints from btrfs module when using the corrupted fs. [ Impact ] They will still get the wrong behavior and obtain btrfs structure with lots of wrong checksums. [ Tests ] Tested by users and me. After applying, the problem described in [1] does not reproduce any more. [ Risks ] Code is simple. Detailed explanation and reproducer is in patch header and in [1]. [ Checklist ] [x] *all* changes are documented in the d/changelog [x] I reviewed all changes and I approve them [x] attach debdiff against the package in (old)stable [x] the issue is verified as fixed in unstable [ Changes ] I cherry-picked a patch from a fixed upstream version. [ Other info ] I'm not sure about the versioning, since this is both a NMU and stable- pu. Maybe .1 is not needed or in the wrong position. [1]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1085207 [2]: https://lore.kernel.org/all/cover.1683592875.git@suse.com/ [3]: https://github.com/kdave/btrfs-progs/commit/416507904c65c5436c2e0bd356669a816365eaf4 Thanks, Shengqi Chen --- End Message --- --- Begin Message --- Source: release.debian.org Version: 12.8 Hi, Each of the updates tracked by these bugs was included in today's 12.8 bookworm point release. Regards, Adam--- End Message ---
Bug#1084907: marked as done (bookworm-pu: package systemd/252.31-1~deb12u1)
Your message dated Sat, 09 Nov 2024 10:51:02 +
with message-id
and subject line Closing bugs released with 12.8
has caused the Debian Bug report #1084907,
regarding bookworm-pu: package systemd/252.31-1~deb12u1
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.)
--
1084907: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1084907
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
Tags: bookworm
User: release.debian@packages.debian.org
Usertags: pu
X-Debbugs-Cc: pkg-systemd-maintain...@lists.alioth.debian.org
Dear Release Team,
We would like to upload the latest stable point release of systemd 252
to bookworm-p-u. Stable release branches are maintained upstream with
the intention of providing bug fixes only and no compatibility
breakages, and with automated non-trivial CI jobs that also cover
Debian and Ubuntu. I have already uploaded to p-u.
Debdiff attached. The only packaging change is to drop a patch merged
upstream and refresh another to remove fuzz.
diff -Nru systemd-252.30/debian/changelog systemd-252.31/debian/changelog
--- systemd-252.30/debian/changelog 2024-08-25 18:35:39.0 +0100
+++ systemd-252.31/debian/changelog 2024-10-10 18:40:53.0 +0100
@@ -1,3 +1,11 @@
+systemd (252.31-1~deb12u1) bookworm; urgency=medium
+
+ * New upstream version 252.31
+ * Drop journald.conf patch merged upstream
+ * Refresh patches to remove fuzz from update
+
+ -- Luca Boccassi Thu, 10 Oct 2024 18:40:53 +0100
+
systemd (252.30-1~deb12u2) bookworm; urgency=medium
* Backport patch to revert new comment in /etc/systemd/journald.conf.
diff -Nru systemd-252.30/debian/patches/debian/Re-enable-journal-forwarding-to-syslog.patch systemd-252.31/debian/patches/debian/Re-enable-journal-forwarding-to-syslog.patch
--- systemd-252.30/debian/patches/debian/Re-enable-journal-forwarding-to-syslog.patch 2024-08-25 18:33:30.0 +0100
+++ systemd-252.31/debian/patches/debian/Re-enable-journal-forwarding-to-syslog.patch 2024-10-10 18:40:53.0 +0100
@@ -16,8 +16,6 @@
src/journal/journald.conf | 2 +-
3 files changed, 3 insertions(+), 2 deletions(-)
-diff --git a/man/journald.conf.xml b/man/journald.conf.xml
-index 2db6a0f..160544a 100644
--- a/man/journald.conf.xml
+++ b/man/journald.conf.xml
@@ -356,7 +356,7 @@
@@ -29,11 +27,9 @@
command line options systemd.journald.forward_to_syslog,
systemd.journald.forward_to_kmsg,
systemd.journald.forward_to_console, and
-diff --git a/src/journal/journald-server.c b/src/journal/journald-server.c
-index 31358cd..863575c 100644
--- a/src/journal/journald-server.c
+++ b/src/journal/journald-server.c
-@@ -2289,6 +2289,7 @@ int server_init(Server *s, const char *namespace) {
+@@ -2289,6 +2289,7 @@
.ratelimit_interval = DEFAULT_RATE_LIMIT_INTERVAL,
.ratelimit_burst = DEFAULT_RATE_LIMIT_BURST,
@@ -41,13 +37,11 @@
.forward_to_wall = true,
.max_file_usec = DEFAULT_MAX_FILE_USEC,
-diff --git a/src/journal/journald.conf b/src/journal/journald.conf
-index 5a60a9d..64f4d4b 100644
--- a/src/journal/journald.conf
+++ b/src/journal/journald.conf
@@ -32,7 +32,7 @@
#RuntimeMaxFiles=100
- #MaxRetentionSec=0
+ #MaxRetentionSec=
#MaxFileSec=1month
-#ForwardToSyslog=no
+#ForwardToSyslog=yes
diff -Nru systemd-252.30/debian/patches/Revert-journal-comment-the-default-value-in-journald.conf.patch systemd-252.31/debian/patches/Revert-journal-comment-the-default-value-in-journald.conf.patch
--- systemd-252.30/debian/patches/Revert-journal-comment-the-default-value-in-journald.conf.patch 2024-08-25 18:34:31.0 +0100
+++ systemd-252.31/debian/patches/Revert-journal-comment-the-default-value-in-journald.conf.patch 1970-01-01 01:00:00.0 +0100
@@ -1,17 +0,0 @@
-Author: Luca Boccassi
-Bug-Debian: http://bugs.debian.org/1079086
-Description: Revert "journal: comment the default value in journald.conf"
- Because of how dpkg handles config files, this will cause a prompt to
- users on upgrade, which is undesirable for stable updates, so revert it
- in v252-stable.
a/src/journal/journald.conf
-+++ b/src/journal/journald.conf
-@@ -30,7 +30,7 @@
- #RuntimeKeepFree=
- #RuntimeMaxFileSize=
- #RuntimeMaxFiles=100
--#MaxRetentionSec=0
-+#MaxRetentionSec=
- #MaxFileSec=1month
- #ForwardToSyslog=yes
- #ForwardToKMsg=no
diff -Nru systemd-252.30/debian/patches/series systemd-252.31/debian/patches/series
--- systemd-252.30/debian/patches/series 2024-08-25 18:32:58.0 +0100
+
Bug#1083162: marked as done (bookworm-pu: package sqlite3/3.40.1-2+deb12u1)
Your message dated Sat, 09 Nov 2024 10:51:02 + with message-id and subject line Closing bugs released with 12.8 has caused the Debian Bug report #1083162, regarding bookworm-pu: package sqlite3/3.40.1-2+deb12u1 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.) -- 1083162: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1083162 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: release.debian.org Severity: normal Tags: bookworm User: release.debian@packages.debian.org Usertags: pu X-Debbugs-Cc: secur...@debian.org, Laszlo Boszormenyi (GCS) * CVE-2023-7104: Session extension buffer overread --- End Message --- --- Begin Message --- Source: release.debian.org Version: 12.8 Hi, Each of the updates tracked by these bugs was included in today's 12.8 bookworm point release. Regards, Adam--- End Message ---
Bug#1082902: marked as done (bookworm-pu: package nghttp2/1.52.0-1+deb12u2)
Your message dated Sat, 09 Nov 2024 10:51:02 +
with message-id
and subject line Closing bugs released with 12.8
has caused the Debian Bug report #1082902,
regarding bookworm-pu: package nghttp2/1.52.0-1+deb12u2
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.)
--
1082902: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1082902
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
Tags: bookworm
User: release.debian@packages.debian.org
Usertags: pu
X-Debbugs-Cc: secur...@debian.org, Tomasz Buchert
* CVE-2024-28182: unbounded number of HTTP/2 CONTINUATION frames DoS
(Closes: #1068415)
* nghttp2_option_set_stream_reset_rate_limit was added in
1.52.0-1+deb12u1, add to debian/libnghttp2-14.symbols
Tagged moreinfo, as question to the security team whether they want
this in -pu or as DSA.
diffstat for nghttp2-1.52.0 nghttp2-1.52.0
changelog | 10
libnghttp2-14.symbols |2
patches/0001-Limit-CONTINUATION-frames-following-an-incoming-HEAD.patch | 106
++
patches/0002-Add-nghttp2_option_set_max_continuations.patch | 101
+
patches/series |2
5 files changed, 221 insertions(+)
diff -Nru nghttp2-1.52.0/debian/changelog nghttp2-1.52.0/debian/changelog
--- nghttp2-1.52.0/debian/changelog 2023-11-24 16:57:26.0 +0200
+++ nghttp2-1.52.0/debian/changelog 2024-09-27 16:25:38.0 +0300
@@ -1,3 +1,13 @@
+nghttp2 (1.52.0-1+deb12u2) bookworm; urgency=medium
+
+ * Non-maintainer upload.
+ * CVE-2024-28182: unbounded number of HTTP/2 CONTINUATION frames DoS
+(Closes: #1068415)
+ * nghttp2_option_set_stream_reset_rate_limit was added in
+1.52.0-1+deb12u1, add to debian/libnghttp2-14.symbols
+
+ -- Adrian Bunk Fri, 27 Sep 2024 16:25:38 +0300
+
nghttp2 (1.52.0-1+deb12u1) bookworm-security; urgency=medium
* CVE-2023-44487 (Closes: #1053769)
diff -Nru nghttp2-1.52.0/debian/libnghttp2-14.symbols
nghttp2-1.52.0/debian/libnghttp2-14.symbols
--- nghttp2-1.52.0/debian/libnghttp2-14.symbols 2022-09-25 17:26:28.0
+0300
+++ nghttp2-1.52.0/debian/libnghttp2-14.symbols 2024-09-27 16:25:38.0
+0300
@@ -33,6 +33,7 @@
nghttp2_option_del@Base 1.3.0
nghttp2_option_new@Base 1.3.0
nghttp2_option_set_builtin_recv_extension_type@Base 1.10.0
+ nghttp2_option_set_max_continuations@Base 1.52.0-1+deb12u2~
nghttp2_option_set_max_deflate_dynamic_table_size@Base 1.15.0
nghttp2_option_set_max_outbound_ack@Base 1.39.2
nghttp2_option_set_max_reserved_remote_streams@Base 1.3.0
@@ -46,6 +47,7 @@
nghttp2_option_set_no_rfc9113_leading_and_trailing_ws_validation@Base 1.50.0
nghttp2_option_set_peer_max_concurrent_streams@Base 1.3.0
nghttp2_option_set_server_fallback_rfc7540_priorities@Base 1.48.0
+ nghttp2_option_set_stream_reset_rate_limit@Base 1.52.0-1+deb12u1~
nghttp2_option_set_user_recv_extension_type@Base 1.8.0
nghttp2_pack_settings_payload@Base 1.3.0
nghttp2_priority_spec_check_default@Base 1.3.0
diff -Nru
nghttp2-1.52.0/debian/patches/0001-Limit-CONTINUATION-frames-following-an-incoming-HEAD.patch
nghttp2-1.52.0/debian/patches/0001-Limit-CONTINUATION-frames-following-an-incoming-HEAD.patch
---
nghttp2-1.52.0/debian/patches/0001-Limit-CONTINUATION-frames-following-an-incoming-HEAD.patch
1970-01-01 02:00:00.0 +0200
+++
nghttp2-1.52.0/debian/patches/0001-Limit-CONTINUATION-frames-following-an-incoming-HEAD.patch
2024-09-27 16:21:17.0 +0300
@@ -0,0 +1,106 @@
+From 73d22aa3debd47d8b87a256f3262f84d08ece9ca Mon Sep 17 00:00:00 2001
+From: Tatsuhiro Tsujikawa
+Date: Sat, 9 Mar 2024 16:26:42 +0900
+Subject: Limit CONTINUATION frames following an incoming HEADER frame
+
+---
+ lib/includes/nghttp2/nghttp2.h | 7 ++-
+ lib/nghttp2_helper.c | 2 ++
+ lib/nghttp2_session.c | 7 +++
+ lib/nghttp2_session.h | 10 ++
+ 4 files changed, 25 insertions(+), 1 deletion(-)
+
+diff --git a/lib/includes/nghttp2/nghttp2.h b/lib/includes/nghttp2/nghttp2.h
+index fa22081c..b394bde9 100644
+--- a/lib/includes/nghttp2/nghttp2.h
b/lib/includes/nghttp2/nghttp2.h
+@@ -440,7 +440,12 @@ typedef enum {
+* exhaustion on server side to send these frames forever and does
+* not read network.
+*/
+- NGHTTP2_ERR_FLOODED = -904
++ NGHTTP2_ERR_FLOODED = -904,
++ /**
++ * When a local endpoint receives too many CONTINUATION
