Bug#1063492: openvswitch: CVE-2023-3966: Invalid memory access in Geneve with HW offload
Control: tags -1 fixed-upstream According to this announcment [1], CVE-2023-3966 and CVE-2023-5366 are fixed with versions Latest stable: https://www.openvswitch.org/releases/openvswitch-3.2.2.tar.gz Current LTS series: https://www.openvswitch.org/releases/openvswitch-2.17.9.tar.gz Other: https://www.openvswitch.org/releases/openvswitch-3.1.4.tar.gz https://www.openvswitch.org/releases/openvswitch-3.0.6.tar.gz [1] https://mail.openvswitch.org/pipermail/ovs-announce/2024-February/000338.html As sid has currently a git snapshot, it is not clear to me if that has been fixed there too. On Thu, 08 Feb 2024 22:35:46 +0100 Salvatore Bonaccorso wrote: > Source: openvswitch > Version: 3.3.0~git20240118.e802fe7-3 > Severity: important > Tags: security upstream > X-Debbugs-Cc: car...@debian.org, Debian Security Team > Control: found -1 3.1.0-2 > > Hi, > > The following vulnerability was published for openvswitch. > > CVE-2023-3966[0]: > | Invalid memory access in Geneve with HW offload > > > 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-2023-3966 > https://www.cve.org/CVERecord?id=CVE-2023-3966 > [1] https://www.openwall.com/lists/oss-security/2024/02/08/3 > [2] https://mail.openvswitch.org/pipermail/ovs-dev/2024-February/411702.html > > Please adjust the affected versions in the BTS as needed. > > Regards, > Salvatore > >
Bug#1062805: RFS: mini-httpd/1.30-8 -- Small HTTP server
Hi Alexandru, I can upload this package for you. --abhijith
Bug#1025080: I suggest to close this bug
I suggest to close this bug PC
Bug#1062596: libqt5qxlsx: NMU diff for 64-bit time_t transition
The latest stable version of QtXlxs is 1.4.6 and prepelease of 1.4.7 is published now. Probably updating to latest stable may be important. — WBW, Alex
Bug#1040375: /usr/lib/x86_64-linux-gnu/simplescreenrecorder/libssr-glinject.so: Segmentation fault when used with anything
I had a look upstream, and found two issues that seem to be about this crash bug: https://github.com/MaartenBaert/ssr/issues/992 and https://github.com/MaartenBaert/ssr/issues/1013 . The latter have some patch proposals. If the latest upstream git edition work, could the fix be the change descrived as "Switch to PLT hooks to make GLInject work with new dlopen/dlsym in libc" in https://github.com/MaartenBaert/ssr/commit/83b8f9f5d9c9ab06152657e57f85b6f71954a6b9 >? I do not use ssr much myself, and have not had time to test. -- Happy hacking Petter Reinholdtsen
Bug#1061496: valgrind: Segmentation fault on armhf checking programs built with -fstack-clash-protection or -fstack-check
Control: affects -1 + libvorbis-dev Control: block 1061501 by -1 This issue cause a failing autopkgtest with libvorbis. I would much prefer a fix in valgrind instead of disabling a autopkgtest check. -- Happy hacking Petter Reinholdtsen
Bug#1049982: bullseye-pu: package riemann-c-client/1.10.4-2+b2
Hi Jonathan, On Tue, Feb 06, 2024 at 05:59:10PM +, Jonathan Wiltshire wrote: > This request was approved but not uploaded in time for the previous point > releases (11.8 and 11.9). Should it be included in 11.10, or should this > request be abandoned and closed? I am not sure about the process, but AFAIK there is nothing more I can do and I have to wait for a Debian committer to push it so that the fixed version is available to all Debian users. As far as I am concerned, I am still very interested in seeing the fixed version shipped in Debian! In case I missed something and the ball is in my court, please point me to the next move because I obviously missed it! Thanks, Romain -- Romain Tartière http://romain.blogreen.org/ pgp: 8234 9A78 E7C0 B807 0B59 80FF BA4D 1D95 5112 336F (ID: 0x5112336F) (plain text =non-HTML= PGP/GPG encrypted/signed e-mail much appreciated) signature.asc Description: PGP signature
Bug#1049988: bookworm-pu: package riemann-c-client/1.10.4-2
Hi Jonathan, On Tue, Feb 06, 2024 at 06:12:47PM +, Jonathan Wiltshire wrote: > This request was approved but not uploaded in time for the previous point > release (12.5). Should it be included in 12.6, or should this request be > abandoned and closed? I am not sure about the process, but AFAIK there is nothing more I can do and I have to wait for a Debian committer to push it so that the fixed version is available to all Debian users. As far as I am concerned, I am still very interested in seeing the fixed version shipped in Debian! In case I missed something and the ball is in my court, please point me to the next move because I obviously missed it! Thanks, Romain -- Romain Tartière http://romain.blogreen.org/ pgp: 8234 9A78 E7C0 B807 0B59 80FF BA4D 1D95 5112 336F (ID: 0x5112336F) (plain text =non-HTML= PGP/GPG encrypted/signed e-mail much appreciated) signature.asc Description: PGP signature
Bug#1063634: minitube: Does not store preview image for subscriptions
Package: minitube Version: 3.9.3-2 Severity: normal X-Debbugs-Cc: fu...@debian.org Hi, when subscribing to a channel, minitube does not store a preview image with the subscription. That renders the channel invisible in the 'Subscriptions' tab. It's possible to "blindly" click on them, though. Kind regards, Bruno -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.6.13-amd64 (SMP w/8 CPU threads; PREEMPT) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) (ignored: LC_ALL set to de_DE.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 minitube depends on: ii dbus-user-session [default-dbus-session-bus] 1.14.10-4 ii dbus-x11 [dbus-session-bus] 1.14.10-4 ii libc6 2.37-15 ii libmpv2 0.37.0-1 ii libqt5core5a 5.15.10+dfsg-6 ii libqt5dbus5 5.15.10+dfsg-6 ii libqt5gui55.15.10+dfsg-6 ii libqt5network55.15.10+dfsg-6 ii libqt5qml55.15.10+dfsg-2 ii libqt5sql55.15.10+dfsg-6 ii libqt5sql5-sqlite 5.15.10+dfsg-6 ii libqt5widgets55.15.10+dfsg-6 ii libqt5x11extras5 5.15.10-2 ii libstdc++614-20240201-3 minitube recommends no packages. minitube suggests no packages. -- no debconf information
Bug#1063633: ITP: python-autodocsumm -- API that automatically extends sphinx
Package: wnpp Severity: wishlist Owner: "Marcos Rodrigues de Carvalho (aka oday)" X-Debbugs-Cc: debian-de...@lists.debian.org, marcosrcarvalh...@gmail.com * Package name: python-autodocsumm Version : 0.2.12 Upstream Contact: Philipp S. Sommer * URL : https://github.com/Chilipp/autodocsumm/ * License : apache-2.0 Programming Lang: Python Description : API that automatically extends sphinx The Python autodocsumm module is a tool that helps developers write documentation for their Python programs in an easier and faster way. It does this automatically, creating summaries or "shortcuts" to the important parts of the code, such as functions and methods. . The module is capable of: - automatically create summaries - produces explanatory comments - customize summaries with extra details - Allows Integration with Other Tools
Bug#1061744: ipyparallel: Patch to fix failing unit test
Package: ipyparallel
Followup-For: Bug #1061744
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu noble ubuntu-patch
X-Debbugs-Cc: chris.peter...@canonical.com
Control: tags -1 patch
Dear Maintainer,
In Ubuntu, the attached patch was applied to achieve the following:
* Fix tests for python3.12 (LP: #2052727)
Python3.12 added checks for mock methods prefixed with `called_` since
assert mock.called_once()
was a common mistake.
Thanks for considering the patch.
- Chris
diff -Nru
ipyparallel-7.1.0/debian/patches/python3-assert-called-once-with.patch
ipyparallel-7.1.0/debian/patches/python3-assert-called-once-with.patch
--- ipyparallel-7.1.0/debian/patches/python3-assert-called-once-with.patch
1969-12-31 16:00:00.0 -0800
+++ ipyparallel-7.1.0/debian/patches/python3-assert-called-once-with.patch
2024-02-08 10:44:16.0 -0800
@@ -0,0 +1,24 @@
+Description: Fix bad test assert for python3.12
+ Python3.12 includes a check for the common mistake of:
+assert mocked_object.called_once_with(params)
+ and now raises an attribute error instead of erroneously passing the test.
+ The correct assertion method is `assert_called_once_with`. See:
+ https://github.com/python/cpython/issues/100690
+ for more information.
+Author: Chris Peterson
+Bug-Ubuntu: https://bugs.launchpad.net/ubuntu/+source/ipyparallel/+bug/2052727
+Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061744
+Last-Update: 2024-02-08
+---
+This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
+--- a/ipyparallel/tests/test_util.py
b/ipyparallel/tests/test_util.py
+@@ -14,7 +14,7 @@
+ assert util.disambiguate_ip_address('0.0.0.0', socket.gethostname()) ==
localhost()
+ wontresolve = 'this.wontresolve.dns'
+ assert util.disambiguate_ip_address('0.0.0.0', wontresolve) == wontresolve
+-assert warn_mock.called_once_with(
++warn_mock.assert_called_once_with(
+ 'IPython could not determine IPs for {}: '
+ '[Errno -2] Name or service not known'.format(wontresolve),
+ RuntimeWarning,
diff -Nru ipyparallel-7.1.0/debian/patches/series
ipyparallel-7.1.0/debian/patches/series
--- ipyparallel-7.1.0/debian/patches/series 2023-02-10 00:19:19.0
-0800
+++ ipyparallel-7.1.0/debian/patches/series 2024-02-08 10:42:39.0
-0800
@@ -5,3 +5,4 @@
fix_docs
fix_setuptools_import.patch
0007-generate-code-reducer-from-CodeType-signature.patch
+python3-assert-called-once-with.patch
Bug#1063434: 389-ds-base: Build flags for 32bit architectures
Package: 389-ds-base Version: 2.4.4+dfsg1-1 Followup-For: Bug #1063434 User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu noble ubuntu-patch X-Debbugs-Cc: chris.peter...@canonical.com Control: tags -1 patch Dear Maintainer, I see this has been marked for autoremoval, but I have recently introduced a patch in Ubuntu which fixed builds for armhf. Please see the attached for a functionally similar patch that should enable builds on your 32bit architectures (armhf, armel, and i386). I can provide armhf autopkgtest results shortly. Thanks, Chris diff -Nru 389-ds-base-2.4.4+dfsg1/debian/rules 389-ds-base-2.4.4+dfsg1/debian/rules --- 389-ds-base-2.4.4+dfsg1/debian/rules2024-01-08 07:40:49.0 -0800 +++ 389-ds-base-2.4.4+dfsg1/debian/rules2024-02-08 16:26:51.0 -0800 @@ -7,6 +7,9 @@ ifneq (,$(filter $(DEB_HOST_ARCH), armel m68k mips mipsel powerpc powerpcspe sh4)) export DEB_LDFLAGS_MAINT_APPEND=-latomic endif +ifneq (,$(filter $(DEB_HOST_ARCH), armhf armel i386)) + export DEB_CFLAGS_MAINT_APPEND=-D_LARGEFILE64_SOURCE +endif REALFILE = \ bin/ds-logpipe.py \
Bug#1063632: spirv-llvm-translator-17 FTBFS: error: ‘CapabilityLongConstantCompositeINTEL’ was not declared in this scope
Source: spirv-llvm-translator-17 Version: 17.0.0-3 Severity: serious Tags: ftbfs Forwarded: https://github.com/KhronosGroup/SPIRV-LLVM-Translator/issues/2261 https://buildd.debian.org/status/logs.php?pkg=spirv-llvm-translator-17=17.0.0-3%2Bb1 ... In file included from /<>/lib/SPIRV/libSPIRV/SPIRVModule.h:44, from /<>/lib/SPIRV/LLVMToSPIRVDbgTran.h:42, from /<>/lib/SPIRV/LLVMToSPIRVDbgTran.cpp:38: /<>/lib/SPIRV/libSPIRV/SPIRVEntry.h: In member function ‘SPIRV::SPIRVCapVec SPIRV::SPIRVContinuedInstINTELBase::getRequiredCapability() const’: /<>/lib/SPIRV/libSPIRV/SPIRVEntry.h:911:19: error: ‘CapabilityLongConstantCompositeINTEL’ was not declared in this scope 911 | return getVec(CapabilityLongConstantCompositeINTEL); | ^~~~ ...
Bug#1036640: debian template's help lists archived releases that are not installable
Control: tags -1 + pending Hi Santiago, Thanks for the report. With the latest version of lxc-templates (pending upload with some related bug fixes) it is possible to create containers for jessie and stretch; wheezy and earlier simply no longer work: > lxc-create -t debian -n stretch -- -r stretch \ > --mirror=http://archive.debian.org/debian \ > --keyring=/usr/share/keyrings/debian-archive-removed-keys.gpg The jessie container starts up, but it doesn't automatically get an IP -- I didn't perform any further investigation. stretch works just fine. I have updated the list of supported releases in the template's help output to list only non-archived releases. Underlying support is still there, and a new section in the help output will describe how to create a container for an archived release. Mathias signature.asc Description: This is a digitally signed message part
Bug#1063631: hkl FTBFS with libcglm-dev 0.9.2-1
Source: hkl Version: 5.0.0.3381-1 Severity: serious Tags: ftbfs patch Forwarded: https://repo.or.cz/hkl.git/commit/c3badf0779a70f1666ccf8241d144ebb01897a0e https://buildd.debian.org/status/logs.php?pkg=hkl=5.0.0.3381-1%2Bb1 ... hkl-binoculars-geometry.c: In function ‘hkl_binoculars_parameter_transformation_get’: hkl-binoculars-geometry.c:45:45: error: incompatible type for argument 1 of ‘glms_rotate_atm’ 45 | r = glms_rotate_atm(m, pivot, angle, axis); | ^ | | | mat4s ...
Bug#1063630: ronn: Please package new upstream version
Package: ronn Version: 0.9.1-3 Severity: wishlist Dear Maintainer, after some years without releases upstream recently released a new version. I would appreciate it, if the new version would be packaged for debian. Best regards, Martin -- 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-17-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.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 ronn depends on: ii ruby 1:3.1 ii ruby-ronn 0.9.1-3 ronn recommends no packages. ronn suggests no packages. -- no debconf information signature.asc Description: PGP signature
Bug#1021370: please add aac support
please add aac support, even if it is via nonfree Many headphones or speakers devices have that codec to have good quality. Without them they are completely unusable. Any workaround to compile that codec separately or is it necessary to rebuild the entire pipewire? thanks! -- Fernando Toledo Dock Sud BBS http://bbs.docksud.com.ar telnet://bbs.docksud.com.ar
Bug#1063629: sysvinit-core.postinst: remove obsolete code path for /etc/inittab fixup on hurd in 2014
Source: sysvinit Version: 3.08-6 Severity: normal Tags: patch User: debian-d...@lists.debian.org Usertags: dpkg-root-support X-Debbugs-Cc: debian-h...@lists.debian.org Hi, In 2014, code was added to to the sysvinit-core.postinst to fix up /etc/inittab files on hurd which had /libexec/getty instead of /sbin/getty and which were missing the following line: c:23:respawn:/sbin/getty 38400 console Also since 2014 (commit 6af0110c) ./debian/share/inittab.gnu is installed on enduser systems which contains aforementioned fixes already. The fixup code in sysvinit-core.postinst is thus long obsolete as any systems that were affected should've long been upgraded and new systems were installed using inittab.gnu which is not broken. I prepared a merge request which removes the obsolete code path here: https://salsa.debian.org/debian/sysvinit/-/merge_requests/12 Removing this old codepath helps with DPKG_ROOT because when creating chrootless systems, uname -s output is potentially incorrect, for example when preparing a hurd chroot on linux. See bug #1063624 for a similar instance of maintainer scripts calling uname causing problems for creating chroots using the DPKG_ROOT mechanism. Thanks! cheers, josch
Bug#1063628: ITP: python-command-runner -- a platform-agnostic external command execution library for python with extra goodies
Package: wnpp Severity: wishlist Owner: Harlan Lieberman-Berg X-Debbugs-Cc: debian-de...@lists.debian.org, an...@beanfield.com, hlieber...@debian.org * Package name: python-command-runner Version : 1.6.0 Upstream Contact: Orsiris de Jong * URL : https://github.com/netinvent/command_runner * License : BSD-3-clause Programming Lang: Python 3 Description : a platform-agnostic external command execution library for python command_runner's purpose is to run external commands from python, just like subprocess on which it relies, while solving various problems a developer may face among: - Handling of all possible subprocess.popen / subprocess.check_output scenarios / python versions in one handy function without encoding / timeout hassle - Allow stdout/stderr stream output to be redirected to callback functions / output queues / files so you get to handle output in your application while commands are running - Callback to optional stop check so we can stop execution from outside command_runner - Callback with optional process information so we get to control the process from outside command_runner - Callback once we're finished to ease thread usage - Optional process priority and io_priority settings - System agnostic functionality, the developer shouldn't carry the burden of Windows & Linux differences - Optional Windows UAC elevation module compatible with CPython, PyInstaller & Nuitka - Optional Linux sudo elevation compatible with CPython, PyInstaller & Nuitka My plan is to maintain this package under the auspices of the Debian Python Team. I am packaging this module in part because it is a direct dependency of LibreNMS, though I don't currently have plans to package that. Sincerely, -- Harlan Lieberman-Berg ~hlieberman
Bug#1063627: zipper.app: transition from p7zip to 7zip
Source: zipper.app Version: 1.5-3 Severity: normal Dear Maintainer, your package Depends/Recommends/Suggests or has some other relation to the p7zip/p7zip-full/p7zip-rar packages, which have become transitional packages in debian trixie and will eventually be removed from debian. They have been replaced by 7zip and 7zip-rar packages. If necessary, please modify your package to use the executables from the 7zip package instead. If everything everything behaves as expected, then remove p7zip/p7zip-full/p7zip-rar from the control file and replace it with 7zip and/or 7zip-rar. This bug is currently filed with normal priority but the priority will be increased as the release date of debian trixie gets closer. Thank you for maintaining software in debian.
Bug#1063626: RFP: rust-adblock -- adblock-rust is the engine powering Brave's native adblocker, available as a library for anyone to use
Package: wnpp Severity: wishlist * Package name: rust-adblock Version : 0.8.6 Upstream Contact: Andrius Aucinas * URL : https://crates.io/crates/adblock * License : MPL-2.0 Programming Lang: Rust Description : adblock-rust is the engine powering Brave's native adblocker, available as a library for anyone to use adblock-rust is the engine powering Brave's native adblocker, available as a library for anyone to use. It features: . Network blocking Cosmetic filtering Resource replacements Hosts syntax uBlock Origin syntax extensions iOS content-blocking syntax conversion Compiling to native code or WASM Rust bindings (crates) JS bindings (npm) Community-maintained Python bindings (pypi) High performance! This is needed for angelfish, and also as a generally useful lib for adblocks.
Bug#1063625: xarchiver: transition from p7zip to 7zip
Source: xarchiver Version: 1:0.5.4.22-1 Severity: normal Dear Maintainer, your package Depends/Recommends/Suggests or has some other relation to the p7zip/p7zip-full/p7zip-rar packages, which have become transitional packages in debian trixie and will eventually be removed from debian. They have been replaced by 7zip and 7zip-rar packages. If necessary, please modify your package to use the executables from the 7zip package instead. If everything everything behaves as expected, then remove p7zip/p7zip-full/p7zip-rar from the control file and replace it with 7zip and/or 7zip-rar. This bug is currently filed with normal priority but the priority will be increased as the release date of debian trixie gets closer. Thank you for maintaining software in debian.
Bug#1063624: libc.preinst: please skip kernel check via uname when DPKG_ROOT is not empty for gnu hurd support
Source: glibc Version: 2.37-15 Severity: normal Tags: patch User: debian-h...@lists.debian.org Usertags: hurd X-Debbugs-Cc: debian-h...@lists.debian.org, debian-cr...@lists.debian.org Hi, one of the reasons for DPKG_ROOT support in packages close to the essential and build-essential set is to build chroots for architectures that do not have qemu-user support. Building chroots for hurd from linux is one such scenario where qemu-user emulation will never allow running hurd binaries from the chroot on the linux system creating that chroot and thus the only way to create it (short of running the whole thing inside a full virtual machine) is to use chrootless mode. In our last round of DPKG_ROOT related patches we built chroots for other linux architectures on linux. Now we try building chroots for foreign kernels. In this case: hurd on linux. In the process we discovered another problem class: maintainer scripts running uname. This is a problem because "uname -s" will print "Linux" and thus the linux-specific parts of the maintainer script get executed but we want to build a hurd chroot and need the hurd-specific bits instead. In case of libc.preinst, its use of "uname -s" and "uname -r" can be avoided by adding another condition on $DPKG_ROOT being empty, i.e to only check the kernel version for normal installations but not when glibc is installed with dpkg --force-script-chrootless as in that case, there exists no way for the script to know what kernel version will be running on the final system where the chroot will be deployed. So if "$DPKG_ROOT" is not empty, the kernel version checks just get skipped. I submitted a patch as a merge request here: https://salsa.debian.org/glibc-team/glibc/-/merge_requests/20 Please consider applying it to close this bug. What do you think? Thanks! cheers, josch
Bug#1063588: nibabel fails to run with Python 3.12 as the default
Control: tags -1 help Control: tags -1 upstream Control: forwarded -1 https://github.com/nipy/nibabel/issues/1294 -- http://fam-tille.de
Bug#1063623: winetricks: transition from p7zip to 7zip
Source: winetricks Version: 20240105-1 Severity: normal Dear Maintainer, your package Depends/Recommends/Suggests or has some other relation to the p7zip/p7zip-full/p7zip-rar packages, which have become transitional packages in debian trixie and will eventually be removed from debian. They have been replaced by 7zip and 7zip-rar packages. If necessary, please modify your package to use the executables from the 7zip package instead. If everything everything behaves as expected, then remove p7zip/p7zip-full/p7zip-rar from the control file and replace it with 7zip and/or 7zip-rar. This bug is currently filed with normal priority but the priority will be increased as the release date of debian trixie gets closer. Thank you for maintaining software in debian.
Bug#1063621: bookworm-pu: package clamav/clamav_1.0.5+dfsg-1~deb12u1
Package: release.debian.org
Control: affects -1 + src:clamav
X-Debbugs-Cc: cla...@packages.debian.org
User: release.debian@packages.debian.org
Usertags: pu
Tags: bookworm
Severity: normal
This is an update to the latest clamav release in the 1.0.x series. This
update closes two CVEs:
- CVE-2024-20290: Fixed a possible heap overflow read bug in the OLE2 file
parser that could cause a denial-of-service (DoS) condition.
- CVE-2024-20328: Fixed a possible command injection vulnerability in the
"VirusEvent" feature of ClamAV's ClamD service.
To fix this issue, we disabled the '%f' format string parameter. ClamD
administrators may continue to use the `CLAM_VIRUSEVENT_FILENAME` environment
variable, instead of '%f'. But you should do so only from within an
executable, such as a Python script, and not directly in the clamd.conf
"VirusEvent" command.
Announcement by upstream:
https://blog.clamav.net/2023/11/clamav-130-122-105-released.html
The previous 1.0.4 release was in unstable since 2024-01-20 and migrated
to testing on 2024-01-22. The 1.0.5 release is in unstable since
2024-02-08 and I have reports of issues so far.
The attached debdiff is against the current version in Bookworm and has
the libclamav_rust/.cargo/ folder omitted. Otherwise the diff grows to
over 100MiB.
Sebastian
diff --git a/.github/workflows/cmake.yml b/.github/workflows/cmake.yml
index 6208c93..422e291 100644
--- a/.github/workflows/cmake.yml
+++ b/.github/workflows/cmake.yml
@@ -24,6 +24,10 @@ name: CMake Build
runs-on: windows-2019
steps:
+ - name: Die, link!
+run: rm /usr/bin/link.exe
+shell: bash
+
- uses: actions/checkout@v1
- name: Install Build Tools
diff --git a/CMakeLists.txt b/CMakeLists.txt
index cfeeb49..b2c6533 100644
--- a/CMakeLists.txt
+++ b/CMakeLists.txt
@@ -22,7 +22,7 @@ string(TIMESTAMP TODAY "%Y%m%d")
set(VERSION_SUFFIX "")
project( ClamAV
- VERSION "1.0.3"
+ VERSION "1.0.5"
DESCRIPTION "ClamAV open source email, web, and end-point anti-virus toolkit." )
set(CMAKE_MODULE_PATH "${CMAKE_CURRENT_SOURCE_DIR}/cmake" ${CMAKE_MODULE_PATH})
@@ -676,13 +676,13 @@ check_type_size("ssize_t" SIZEOF_SSIZE_T)
if(SIZEOF_SSIZE_T STREQUAL "")
# ssize_t is a signed type in POSIX storing at least -1.
# Set it to "int" to match the behavior of AC_TYPE_SSIZE_T (autotools).
-set(ssize_t int)
+set(SSIZE_T_DEF "typedef int ssize_t;")
endif()
check_type_size("off_t" SIZEOF_OFF_T)
if(SIZEOF_OFF_T STREQUAL "")
# off_t is a signed type in POSIX no narrower than int.
# Set it to "long int" to match the behavior of AC_TYPE_OFF_T (autotools).
-set(off_t long int)
+set(OFF_T_DEF "typedef long int off_t;")
endif()
check_type_size("int" SIZEOF_INT)
diff --git a/Cargo.lock b/Cargo.lock
index e06ab2a..05e6643 100755
--- a/Cargo.lock
+++ b/Cargo.lock
@@ -8,26 +8,6 @@ version = "1.0.2"
source = "registry+https://github.com/rust-lang/crates.io-index;
checksum = "f26201604c87b1e01bd3d98f8d5d9a8fcbb815e8cedb41ffccbeb4bf593a35fe"
-[[package]]
-name = "ansi_term"
-version = "0.12.1"
-source = "registry+https://github.com/rust-lang/crates.io-index;
-checksum = "d52a9bb7ec0cf484c551830a7ce27bd20d67eac647e1befb56b0be4ee39a55d2"
-dependencies = [
- "winapi",
-]
-
-[[package]]
-name = "atty"
-version = "0.2.14"
-source = "registry+https://github.com/rust-lang/crates.io-index;
-checksum = "d9b39be18770d11421cdb1b9947a45dd3f37e93092cbf377614828a319d5fee8"
-dependencies = [
- "hermit-abi 0.1.19",
- "libc",
- "winapi",
-]
-
[[package]]
name = "autocfg"
version = "1.1.0"
@@ -102,7 +82,6 @@ version = "0.20.0"
source = "registry+https://github.com/rust-lang/crates.io-index;
checksum = "51e3973b165dc0f435831a9e426de67e894de532754ff7a3f307c03ee5dec7dc"
dependencies = [
- "clap",
"heck",
"indexmap",
"log",
@@ -115,6 +94,15 @@ dependencies = [
"toml",
]
+[[package]]
+name = "cc"
+version = "1.0.83"
+source = "registry+https://github.com/rust-lang/crates.io-index;
+checksum = "f1174fb0b6ec23863f8b971027804a42614e347eafb0a95bf0b12cdae21fc4d0"
+dependencies = [
+ "libc",
+]
+
[[package]]
name = "cexpr"
version = "0.6.0"
@@ -160,21 +148,6 @@ dependencies = [
"libloading",
]
-[[package]]
-name = "clap"
-version = "2.34.0"
-source = "registry+https://github.com/rust-lang/crates.io-index;
-checksum = "a0610544180c38b88101fecf2dd634b174a62eef6946f84dfc6a7127512b381c"
-dependencies = [
- "ansi_term",
- "atty",
- "bitflags",
- "strsim",
- "textwrap",
- "unicode-width",
- "vec_map",
-]
-
[[package]]
name = "color_quant"
version = "1.1.0"
@@ -201,9 +174,9 @@ dependencies = [
[[package]]
name = "crossbeam-channel"
-version = "0.5.6"
+version = "0.5.8"
source = "registry+https://github.com/rust-lang/crates.io-index;
-checksum = "c2dd04ddaf88237dc3b8d8f9a3c1004b506b54b3313403944054d23c0870c521"
+checksum = "a33c2bf77f2df06183c3aa30d1e96c0695a313d4f9c453cc3762a6db39f99200"
dependencies = [
Bug#1063622: otpw: install PAM module into /usr
Source: otpw Version: 1.5-2 Severity: normal Tags: patch User: helm...@debian.org Usertags: dep17m2 We want to finalize the /usr-merge via DEP17 by moving all files to /usr. otpw installs files into /lib these should be moved into the respective canonical locations in /usr/. Please find a patch attached. It has been build-tested. Note 1: this change includes moving the .so into a multiarch path which is recommended on Debian nowadays. Note 2: this should not be backported to bookworm. If you intend to backport, please use dh_movetousr instead. If your package will change for the t64 transition or otherwise rename/split/move its binaries (packages) during trixie, please then upload to experimental and get in touch with the UsrMerge driver, please see the wiki [1]. Michael [1] https://wiki.debian.org/UsrMerge diff -Nru otpw-1.5/debian/changelog otpw-1.5/debian/changelog --- otpw-1.5/debian/changelog 2019-01-05 18:22:19.0 +0100 +++ otpw-1.5/debian/changelog 2024-02-09 23:08:08.0 +0100 @@ -1,3 +1,11 @@ +otpw (1.5-2.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Install PAM module into /usr. (Closes: #-1) + * Use Multi-Arch paths. + + -- Michael Biebl Fri, 09 Feb 2024 23:08:08 +0100 + otpw (1.5-2) sid; urgency=medium * debian/control: use dh 11 diff -Nru otpw-1.5/debian/libpam-otpw.install otpw-1.5/debian/libpam-otpw.install --- otpw-1.5/debian/libpam-otpw.install 2017-06-04 13:54:48.0 +0200 +++ otpw-1.5/debian/libpam-otpw.install 2024-02-09 23:05:29.0 +0100 @@ -1 +1 @@ -/lib/security +usr/lib/*/security diff -Nru otpw-1.5/debian/rules otpw-1.5/debian/rules --- otpw-1.5/debian/rules 2018-12-14 19:43:21.0 +0100 +++ otpw-1.5/debian/rules 2024-02-09 23:07:29.0 +0100 @@ -6,6 +6,8 @@ # dh-make output file, you may use that output file without restriction. # This special exception was added by Craig Small in version 0.37 of dh-make. +include /usr/share/dpkg/architecture.mk + # Uncomment this to turn on verbose mode. #export DH_VERBOSE=1 @@ -52,8 +54,8 @@ mkdir -p debian/tmp install -d debian/tmp/usr/bin install otpw-gen debian/tmp/usr/bin - install -d debian/tmp/lib/security - install pam_otpw.so debian/tmp/lib/security + install -d debian/tmp/usr/lib/$(DEB_HOST_MULTIARCH)/security + install pam_otpw.so debian/tmp/usr/lib/$(DEB_HOST_MULTIARCH)/security install -d debian/tmp/usr/include install -m644 otpw.h debian/tmp/usr/include install -d debian/tmp/usr/lib
Bug#1063620: ukui-biometric-auth: install PAM module into /usr
Source: ukui-biometric-auth
Version: 1.2.2.1-2
Severity: normal
Tags: patch
User: helm...@debian.org
Usertags: dep17m2
We want to finalize the /usr-merge via DEP17 by moving all files to
/usr. ukui-biometric-auth installs files into /lib these should be moved
into the respective canonical locations in /usr/.
Please find a patch attached. It has been build-tested.
Note 1: this change includes moving the .so into a multiarch path which
is recommended on Debian nowadays.
Note 2: this should not be backported to bookworm. If you intend to
backport, please use dh_movetousr instead.
If your package will change for the t64 transition or otherwise
rename/split/move its binaries (packages) during trixie, please
then upload to experimental and get in touch with the UsrMerge
driver, please see the wiki [1].
Michael
[1] https://wiki.debian.org/UsrMerge
diff -Nru ukui-biometric-auth-1.2.2.1/debian/changelog
ukui-biometric-auth-1.2.2.1/debian/changelog
--- ukui-biometric-auth-1.2.2.1/debian/changelog2023-08-21
07:47:48.0 +0200
+++ ukui-biometric-auth-1.2.2.1/debian/changelog2024-02-09
21:58:37.0 +0100
@@ -1,3 +1,11 @@
+ukui-biometric-auth (1.2.2.1-2.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Install PAM module into /usr. (Closes: #-1)
+ * Bump debhelper-compat to 13 to get variable expansion in .install files.
+
+ -- Michael Biebl Fri, 09 Feb 2024 21:58:37 +0100
+
ukui-biometric-auth (1.2.2.1-2) unstable; urgency=medium
* d/control: drop policykit-1, add pkexec. (Closes: #1025633)
diff -Nru ukui-biometric-auth-1.2.2.1/debian/control
ukui-biometric-auth-1.2.2.1/debian/control
--- ukui-biometric-auth-1.2.2.1/debian/control 2023-08-21 07:47:48.0
+0200
+++ ukui-biometric-auth-1.2.2.1/debian/control 2024-02-09 21:58:37.0
+0100
@@ -3,7 +3,7 @@
Priority: optional
Maintainer: Kylin Team
Uploaders: handsome_feng
-Build-Depends: debhelper-compat (= 12),
+Build-Depends: debhelper-compat (= 13),
cmake (>= 2.6),
qtbase5-dev,
libpam-dev,
diff -Nru ukui-biometric-auth-1.2.2.1/debian/libpam-biometric.install
ukui-biometric-auth-1.2.2.1/debian/libpam-biometric.install
--- ukui-biometric-auth-1.2.2.1/debian/libpam-biometric.install 2021-06-22
11:24:29.0 +0200
+++ ukui-biometric-auth-1.2.2.1/debian/libpam-biometric.install 2024-02-09
21:58:37.0 +0100
@@ -1,5 +1,5 @@
/etc/biometric-auth/ukui-biometric.conf
-/lib/security/*
+/lib/security/* usr/lib/${DEB_HOST_MULTIARCH}/security/
/usr/bin/*
/usr/share/pam-configs/*
/usr/share/polkit-1/actions/*.policy
Bug#1063619: unp: transition from p7zip to 7zip
Source: unp Version: 2.0~pre10 Severity: normal Dear Maintainer, your package Depends/Recommends/Suggests or has some other relation to the p7zip/p7zip-full/p7zip-rar packages, which have become transitional packages in debian trixie and will eventually be removed from debian. They have been replaced by 7zip and 7zip-rar packages. If necessary, please modify your package to use the executables from the 7zip package instead. If everything everything behaves as expected, then remove p7zip/p7zip-full/p7zip-rar from the control file and replace it with 7zip and/or 7zip-rar. This bug is currently filed with normal priority but the priority will be increased as the release date of debian trixie gets closer. Thank you for maintaining software in debian.
Bug#1063618: sabnzbdplus: transition from p7zip to 7zip
Source: sabnzbdplus Version: 4.2.2+dfsg-1 Severity: normal Dear Maintainer, your package Depends/Recommends/Suggests or has some other relation to the p7zip/p7zip-full/p7zip-rar packages, which have become transitional packages in debian trixie and will eventually be removed from debian. They have been replaced by 7zip and 7zip-rar packages. If necessary, please modify your package to use the executables from the 7zip package instead. If everything everything behaves as expected, then remove p7zip/p7zip-full/p7zip-rar from the control file and replace it with 7zip and/or 7zip-rar. This bug is currently filed with normal priority but the priority will be increased as the release date of debian trixie gets closer. Thank you for maintaining software in debian.
Bug#1063554: closed by Helmut Grohne (Re: Bug#1063554: firmware-linux-free: move files to /usr (DEP17))
Helmut, you are awesome fast :) On Fri, Feb 09, 2024 at 09:51:05PM +, Debian Bug Tracking System wrote: > This is an automatic notification regarding your Bug report > which was filed against the firmware-linux-free package: > > #1063554: firmware-linux-free: move files to /usr (DEP17) > > It has been closed by Helmut Grohne . > > Their explanation is attached below along with your original report. > If this explanation is unsatisfactory and you have not received a > better one in a separate message then please contact Helmut Grohne > by > replying to this email. > > > -- > 1063554: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063554 > Debian Bug Tracking System > Contact ow...@bugs.debian.org with problems > From: Helmut Grohne > Date: Fri, 9 Feb 2024 22:48:44 +0100 > To: Salvatore Bonaccorso > Cc: 1063554-d...@bugs.debian.org > Subject: Re: Bug#1063554: firmware-linux-free: move files to /usr (DEP17) > Message-ID: <20240209214844.ga3105...@subdivi.de> > > Version: 20200122-3 > Control: tags -1 - moreinfo > > On Fri, Feb 09, 2024 at 10:43:42PM +0100, Salvatore Bonaccorso wrote: > > Before I do mess up: Ben did upload to experimental 20200122-3, which > > runs dh_movetousr if available. Cf. > > > > https://salsa.debian.org/kernel-team/firmware-free/-/commit/cdbadf48dd0250c88e60eba2e96ce45bbc42e59a > > > > Is this actually enough? > > Yes. I failed to check experimental. We're in the process of hunting > down the long tail of packages that don't just work. Ack! So if that version does not show any problems in your testing for the /usr-merge transition then I guess the next step is to move that to unstable to facilitate your goal. Regards, Salvatore
Bug#1063617: sogo FTBFS on little endian
Source: sogo Version: 5.9.0-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/logs.php?pkg=sogo=5.9.0-1 https://buildd.debian.org/status/logs.php?pkg=sogo=5.9.1-1 ... == FAIL: test_recurrenceRangesWithinCalendarDateRange_ (TestiCalRecurrenceCalculator.m:381) -- Invalid occurrence for recurrence rule FREQ=YEARLY;UNTIL=2131T09Z;BYMONTH=1;BYDAY=SU,MO,TU,WE,TH,FR,SA: Fri 1999-01-01 09:00 (expected date was Sat 1998-01-31 09:00) == FAIL: test_NGInternetSocketAddressFromString (TestNGNetUtlilities.m:86) -- isIpv4 mismatch. Expected: '1', result: '0'. Test url: 'localhost:1001' == FAIL: test_generateDataForHeaderFieldNamed_value_ (TestNGMimeAddressHeaderFieldGenerator.m:78) -- received 'wolfg...@test.com, wolfg...@test.com' instead of '"" ' for '"" ' -- Ran 38 tests FAILED (3 failures, 0 errors) hash = $argon2id$v=19$m=65536,t=2,p=1$H1BrOTIX9XOi2WuD7zx+pw$Vvik3l21HkuRr5LhnJz0RBq35hxI8woG51F/gEuUt78 make[3]: *** [GNUmakefile:63: check] Error 1 debian/rules ignores test failures on big endian
Bug#1063554: firmware-linux-free: move files to /usr (DEP17)
Control: tags -1 + moreinfo Hi Helmut, On Fri, Feb 09, 2024 at 04:02:42PM +0100, Helmut Grohne wrote: > Package: firmware-linux-free > Version: 20200122-2 > Tags: patch > User: helm...@debian.org > Usertags: dep17m2 > > Hi, > > we want to finalize the /usr-merge transition by moving all aliased > files from / to /usr via DEP17 to avoid any negative effects arising > from aliasing. firmware-linux-free is involved, because it installs > firmware files below /lib/firmware. Since it cannot be converted > automatically using dh-sequence-movetousr, I'm attaching a patch. This > patch should not be uploaded to bookworm-backports or earlier. Also note > that firmware-carl9170 is in the process of taking over firmware from > firmware-linux-free and doing so will cause a file loss (DEP17 P1). This > is tracked as #1050989. I do not expect that firmware-linux-free needs > to support firmware-carl9170 in mitigating this. Before I do mess up: Ben did upload to experimental 20200122-3, which runs dh_movetousr if available. Cf. https://salsa.debian.org/kernel-team/firmware-free/-/commit/cdbadf48dd0250c88e60eba2e96ce45bbc42e59a Is this actually enough? Regards, Salvatore
Bug#1063616: runescape: transition from p7zip to 7zip
Source: runescape Version: 0.8-2 Severity: normal Dear Maintainer, your package Depends/Recommends/Suggests or has some other relation to the p7zip/p7zip-full/p7zip-rar packages, which have become transitional packages in debian trixie and will eventually be removed from debian. They have been replaced by 7zip and 7zip-rar packages. If necessary, please modify your package to use the executables from the 7zip package instead. If everything everything behaves as expected, then remove p7zip/p7zip-full/p7zip-rar from the control file and replace it with 7zip and/or 7zip-rar. This bug is currently filed with normal priority but the priority will be increased as the release date of debian trixie gets closer. Thank you for maintaining software in debian.
Bug#1063615: rocksndiamonds: transition from p7zip to 7zip
Source: rocksndiamonds Version: 4.3.6.0+dfsg-1 Severity: normal Dear Maintainer, your package Depends/Recommends/Suggests or has some other relation to the p7zip/p7zip-full/p7zip-rar packages, which have become transitional packages in debian trixie and will eventually be removed from debian. They have been replaced by 7zip and 7zip-rar packages. If necessary, please modify your package to use the executables from the 7zip package instead. If everything everything behaves as expected, then remove p7zip/p7zip-full/p7zip-rar from the control file and replace it with 7zip and/or 7zip-rar. This bug is currently filed with normal priority but the priority will be increased as the release date of debian trixie gets closer. Thank you for maintaining software in debian.
Bug#1063614: qnapi: transition from p7zip to 7zip
Source: qnapi Version: 0.2.3-2 Severity: normal Dear Maintainer, your package Depends/Recommends/Suggests or has some other relation to the p7zip/p7zip-full/p7zip-rar packages, which have become transitional packages in debian trixie and will eventually be removed from debian. They have been replaced by 7zip and 7zip-rar packages. If necessary, please modify your package to use the executables from the 7zip package instead. If everything everything behaves as expected, then remove p7zip/p7zip-full/p7zip-rar from the control file and replace it with 7zip and/or 7zip-rar. This bug is currently filed with normal priority but the priority will be increased as the release date of debian trixie gets closer. Thank you for maintaining software in debian.
Bug#1060925: Accepted sogo 5.9.1-1 (source) into unstable
Source: sogo Source-Version: 5.9.1-1 Fixes CVE-2023-48104, #1060925, so closing it with this version. On Fri, Feb 09, 2024 at 07:59:18PM +, Debian FTP Masters wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA512 > > Format: 1.8 > Date: Wed, 07 Feb 2024 16:39:36 +0100 > Source: sogo > Architecture: source > Version: 5.9.1-1 > Distribution: unstable > Urgency: medium > Maintainer: Debian SOGo Maintainers > > Changed-By: Jordi Mallach > Changes: > sogo (5.9.1-1) unstable; urgency=medium > . >* New upstream release. >* Revert all unvendoring changes as they completely break SOGo. >* Rely on dh_installinit to install the systemd service file. >* Refresh Remove-build-date.patch. >* Update number of expected test failures to 1. >* Release to unstable. > Checksums-Sha1: > a0de7bcc140f48cbee4b3a1c65a4875e0fa1fd17 2264 sogo_5.9.1-1.dsc > 4674851c65672b7070023dbdae2eef9b8ddf0280 34831391 sogo_5.9.1.orig.tar.gz > 580e185dca322a62032869a1f3b8bce688d07112 18276 sogo_5.9.1-1.debian.tar.xz > 36366d5cec0c489b7d637764f4128fb441a7b4fa 11322 sogo_5.9.1-1_amd64.buildinfo > Checksums-Sha256: > c1372ed8ede354b7ef534ec94ad0b28097c937d6120406fd74c2cfbb707b4832 2264 > sogo_5.9.1-1.dsc > df6ac305a99196ee66d60fda395af81d8da044e7f5c1b1603a51dc4a8edf8ac4 34831391 > sogo_5.9.1.orig.tar.gz > 8f211e9ebbd87ee81f4869c940d96d4a749b0d21fa564174e3ca7148c7ce33e8 18276 > sogo_5.9.1-1.debian.tar.xz > bc7bd540fe6520504bc15af43607b45ec58dedb244c1976646fce982d3782f56 11322 > sogo_5.9.1-1_amd64.buildinfo > Files: > 10df580323cea3434bdca93dfcbe5c39 2264 mail optional sogo_5.9.1-1.dsc > a260fe92c447f0b185dbd6ebeb411907 34831391 mail optional > sogo_5.9.1.orig.tar.gz > 36387abcff529a9720a676365085dd5f 18276 mail optional > sogo_5.9.1-1.debian.tar.xz > f48324600482875ab6b6b90067035549 11322 mail optional > sogo_5.9.1-1_amd64.buildinfo > > -BEGIN PGP SIGNATURE- > > iQIzBAEBCgAdFiEE6BdUhsApKYN8KGoWJVAvb8vjywQFAmXGas4ACgkQJVAvb8vj > ywQuMxAAm6BBOyqtWJ2panPGkdREkfOW+uvM480CVL2uEkzb5lSkedmyHQ1WU2P5 > lDsXYj0cZbA9Qkjyf1jZqjOCRWW472FPBYkrG19oeS4Qnc3t8HN17Urv13lSrWm1 > A0rCqDBGaI+uPSRI33DfkEbuc2BvZnb9l6gbeSgEyONRKbQ1IsuseQyS6Kuc/plu > vqvCWC2/Bi3YTjvxSYfKwqDJggd/6LtNPok0rL2++Iu6gD9i9NHZY/nLe2hyqzqQ > sMcejzJB0Gc3ZtDeQVD7kr9IMZnLUQUra5wby8XrbQx6YSzw7fJ/fhemczqicJ67 > CfTCtRs0TzDQlzA5UxsXKGEcGVsIKDfD59Cbhfdv6EnEDCcnsAUf4wC+GStjtI8n > 8tN4rU6WOdS3suW2ZdxTco7ujpxyimcxHe/Z2ruO44XWuaOK6XN2EqweULfUc5cR > 3qkPpGftHbZUQh12at4enjL85EpMOXf832jMiamaNnwwgQE9rtisCfphOUOz8rLX > xWEjCqPkJ8JQPQeCTghJK0rWonZfLMgi6ooLOco9BOZWMtuEF/BmaVsfTOR0zafq > YoGMot69JzIQbVcbpbBhNHSwa6IXW1nzzm3V40cajM4p3lubb7YOesXLyGeZTPO3 > gdQ2w7CSsPLMUAZMJMG+/K3qy1epbdAANRnVPCWyR8fjR9KvPnQ= > =j//V > -END PGP SIGNATURE- >
Bug#1063605: debian-policy: mandate use of `dpkg-buildflags` for all software compilation on Debian
On Fri, Feb 09, 2024 at 09:16:00PM +0100, Ansgar wrote:
> Package: debian-policy
> Version: 4.6.2.0
> Severity: important
>
> Hi,
>
> with the upcoming time_t & friends 64-bit transition, dpkg-buildflags
> will be used to configure the ABI in use.
This decision comes from the wrong premise that the use of dpkg-buildflags
is universal, which is not the case. Hence it needs to be reconsidered.
There is not magic that will make all packages use dpkg-buildflags consistently
in the timeframe of this migration.
> Thus all compiler
> invocations *must* use the flags specified by dpkg-buildflags to avoid
> ABI inconsistencies like this one:
>
> struct T { time_t a; time_t b; };
>
> If this struct is accessed from both `libfoo1t64` (built respecting
> dpkg-buildflags and thus time_t is 64-bit) and `bar` (built by a user
> invoking gcc themselves), the result is probably not what one wants.
>
> Thus `dpkg-buildflags` *must* be used by all packages *and* all users,
> including users building their own software. There is one exception
> when libraries provide both 32-bit and 64-bit time_t ABIs like glibc
> itself (but I doubt there are many of those).
No, it is required that packages use correctly the right compiler flags.
Since packages need to be reuploaded anyway this is not a real issue.
dpkg-buildflags is not required for that, and does not necessarily achieve it
either, since upstream build system might not honor the environment variables
CFLAGS etc. consistently.
> Any compiler invocation missing these *should* be a serious bug.
> (This should probably be mentioned in user documentation as well.)
This a different issue than mandating dpkg-buildflags.
dpkg-buildflags leads to build flags which are significantly different from
upstream, that have not been tested by users building from source, and they
can change without notice. It is very reasonable not to trust them.
In general we discourage diverging from upstream for similar reasons.
I offered #724621 as an option which would let packages maintainers control
which buildflags are used while still providing the benefit of buildflags.
Cheers,
--
Bill.
Imagine a large red swirl here.
Bug#1063613: python-rarfile: transition from p7zip to 7zip
Source: python-rarfile Version: 4.1-2 Severity: normal Dear Maintainer, your package Depends/Recommends/Suggests or has some other relation to the p7zip/p7zip-full/p7zip-rar packages, which have become transitional packages in debian trixie and will eventually be removed from debian. They have been replaced by 7zip and 7zip-rar packages. If necessary, please modify your package to use the executables from the 7zip package instead. If everything everything behaves as expected, then remove p7zip/p7zip-full/p7zip-rar from the control file and replace it with 7zip and/or 7zip-rar. This bug is currently filed with normal priority but the priority will be increased as the release date of debian trixie gets closer. Thank you for maintaining software in debian.
Bug#1063612: ITP: corrosion -- Tool for integrating rust with an existing CMake project
Package: wnpp Severity: wishlist Owner: Nilesh Patra X-Debbugs-Cc: debian-de...@lists.debian.org, nil...@debian.org * Package name: corrosion Version : 0.4.7 Upstream Contact: Andrew Gaspar * URL : https://github.com/corrosion-rs/corrosion * License : MIT Programming Lang: C++ Description : Tool for integrating rust with an existing CMake project Corrosion, formerly known as cmake-cargo, is a tool for integrating Rust into an existing CMake project. . Corrosion can automatically import executables, static libraries, and dynamic libraries from a workspace or package manifest (Cargo.toml file). Needed for angelfish to manage it easily. This will be maintained in the debian namespace.
Bug#1063611: python3-datalad: transition from p7zip to 7zip
Package: python3-datalad Severity: normal Dear Maintainer, your package Depends/Recommends/Suggests or has some other relation to the p7zip/p7zip-full/p7zip-rar packages, which have become transitional packages in debian trixie and will eventually be removed from debian. They have been replaced by 7zip and 7zip-rar packages. If necessary, please modify your package to use the executables from the 7zip package instead. If everything everything behaves as expected, then remove p7zip/p7zip-full/p7zip-rar from the control file and replace it with 7zip and/or 7zip-rar. This bug is currently filed with normal priority but the priority will be increased as the release date of debian trixie gets closer. Thank you for maintaining software in debian.
Bug#1063542: python-parsl-doc: please make the build reproducible
Hi James, James Addison, on 2024-02-09: > When Sphinx builds documentation, by default it will emit a Python repr() of > the manager_config argument, causing the hostname of the build host to be > included. > > We can solve that by instructing the Sphinx autodoc extension to retain the > textual representation of argument lists as they are found in the source > code, instead of evaluated and repr'd equivalents. Thank you thank you thank you! This reproducibility issue has been nagging me from day zero. Despite trying to filter out the host name, it ended up in the search indexer, sliced by dashes when the name contained some, preventing sed passes to resolve the issue. I see to include your patch in the next python-parsl upload; this will also allow some cleanup in the d/rules. Have a nice day, :) -- .''`. Étienne Mollier : :' : pgp: 8f91 b227 c7d6 f2b1 948c 8236 793c f67e 8f0d 11da `. `' sent from /dev/pts/5, please excuse my verbosity `-on air: AndersonPonty Band - Time and a Word signature.asc Description: PGP signature
Bug#1063498: rust-glib-sys FTBFS with the nocheck build profile: cp: cannot stat '/usr/share/gir-1.0/GLib-2.0.gir': No such file or directory
On Thu, 8 Feb 2024 15:20:53 +0100 Helmut Grohne wrote: > Source: rust-glib-sys > Version: 0.18.1-2 > Severity: serious > Tags: ftbfs trixie sid > > rust-glib-sys fails to build from source in unstable when built with the > nocheck build profile. Since trixie, a nocheck failure is considered > release-critical. A build ends with: > > | debian/rules execute_before_dh_auto_build > | make[1]: Entering directory '/<>' > | cp /usr/share/gir-1.0/GLib-2.0.gir /<> > | cp: cannot stat '/usr/share/gir-1.0/GLib-2.0.gir': No such file or directory > | make[1]: *** [debian/rules:9: execute_before_dh_auto_build] Error 1 > | make[1]: Leaving directory '/<>' > | make: *** [debian/rules:4: binary] Error 2 > | dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2 > > Helmut Control: tags +1 patch Hi Helmut, the version in experimental already contains the fix for this. I hope to subsequently upload all of gtk-rs to experimental this weekend and then to unstable soon after. Actually some other gtk-rs packages are also affected; this will be remedied. best, -- Matthias Geiger Debian Maintainer "Freiheit ist immer Freiheit des anders Denkenden" -- Rosa Luxemburg OpenPGP_0x18BD106B3B6C5475.asc Description: OpenPGP public key OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1063610: python3-binwalk: transition from p7zip to 7zip
Package: python3-binwalk Severity: normal Dear Maintainer, your package Depends/Recommends/Suggests or has some other relation to the p7zip/p7zip-full/p7zip-rar packages, which have become transitional packages in debian trixie and will eventually be removed from debian. They have been replaced by 7zip and 7zip-rar packages. If necessary, please modify your package to use the executables from the 7zip package instead. If everything everything behaves as expected, then remove p7zip/p7zip-full/p7zip-rar from the control file and replace it with 7zip and/or 7zip-rar. This bug is currently filed with normal priority but the priority will be increased as the release date of debian trixie gets closer. Thank you for maintaining software in debian.
Bug#1063609: texstudio_4.7.2+ds-1_all-buildd.changes REJECTED
Source: texstudio Version: 4.7.2+ds-1 Severity: serious On 2024-02-07 17:06, Debian FTP Masters wrote: > > texstudio-doc_4.7.2+ds-1_all.deb: Built-Using refers to non-existing source > package python3-pygments (= 2.17.2+dfsg-1) > > > Mapping sid to unstable. > > === > > Please feel free to respond to this email if you don't understand why > your files were rejected, or if you upload new files which address our > concerns. > > >
Bug#1063508: ITP: node-long -- Class for representing 64-bit two's-complement integer value
Le ven. 9 févr. 2024 à 04:42, Marco Trevisan a écrit : > Package: wnpp > Severity: wishlist > Owner: Marco Trevisan (Treviño) > X-Debbugs-CC: debian-de...@lists.debian.org > > * Package name: node-long > Version : 5.2.3 > Upstream Author : Daniel Wirtz > * URL : https://github.com/dcodeIO/long.js#readme > * License : Apache-2.0 > Programming Lang: JavaScript > Description : Class for representing 64-bit two's-complement > integer value > > A Long class for representing a 64 bit two's-complement integer value > derived from the Closure Library for stand-alone use and extended with > unsigned support. > . > This is a class used by various modules that does not use newer bigint. > . > Node.js is an event-based server-side JavaScript engine. > > This is a tiny module that is needed for protobufjs (bug #977564), > although being widely used according to npm stats, I feel it's better to > package it as standalone and not as grouped package. > > Salsa repository is at: > https://salsa.debian.org/3v1n0-guest/node-esm2umd/-/tree/debian/latest > > Please mark the debian/latest as default branch since I can't change it > myself. > > The package had a dependency on a very tiny project (esm2umd) that was > just basically a tiny wrapper to babel. I've also prepared the packaging > for it [1], but given that such project has not a clear license (I > mailed the maintainer meanwhile), I preferred to avoid using it, also > because it's really just a script using babel and I have been able to > easily re-implement it, making the build process slightly bigger > > The package needs sponsor, since I'm only a maintainer, but I'll be > happy keeping the maintenance of it. > Hi will do but last i checked it has a long line of wasm wirhout source Bastien > > I've given access to the js salsa team. > > [1] https://salsa.debian.org/3v1n0-guest/node-esm2umd/ > >
Bug#1063608: playonlinux: transition from p7zip to 7zip
Source: playonlinux Version: 4.3.4-3 Severity: normal Dear Maintainer, your package Depends/Recommends/Suggests or has some other relation to the p7zip/p7zip-full/p7zip-rar packages, which have become transitional packages in debian trixie and will eventually be removed from debian. They have been replaced by 7zip and 7zip-rar packages. If necessary, please modify your package to use the executables from the 7zip package instead. If everything everything behaves as expected, then remove p7zip/p7zip-full/p7zip-rar from the control file and replace it with 7zip and/or 7zip-rar. This bug is currently filed with normal priority but the priority will be increased as the release date of debian trixie gets closer. Thank you for maintaining software in debian.
Bug#1063607: igraph: FTBFS on i386: test::igraph_hrg (Failed)
Source: igraph Version: 0.10.9+ds-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=igraph=i386=0.10.9%2Bds-1=1707132840=0 526: Test timeout computed to be: 1500 521/554 Test #508: test::igraph_hrg ...***Failed0.20 sec -- Test case output differs from the expected output -- See diff below: -- --- --- /<>/tests/unit/igraph_hrg.out 2024-02-04 21:40:29.0 + +++ /<>/_BUILD_STATIC/tests/test_igraph_hrg.out2024-02-05 11:14:47.195150846 + @@ -1,24 +1,24 @@ -Vertex # 25, left: # 29, right: # 43, prob: 0.0067 -Vertex # 26, left: # 13, right: # 46, prob: 1 -Vertex # 27, left: # 14, right: # 19, prob: 1 -Vertex # 28, left: # 15, right: # 16, prob: 0 -Vertex # 29, left: # 28, right: # 41, prob: 0.23 -Vertex # 30, left: # 33, right: # 37, prob: 0.13 -Vertex # 31, left: # 8, right: # 34, prob: 1 -Vertex # 32, left: # 23, right: # 24, prob: 0 -Vertex # 33, left: # 22, right: # 27, prob: 0 -Vertex # 34, left: # 7, right: # 44, prob: 1 -Vertex # 35, left: # 17, right: # 39, prob:0.1 -Vertex # 36, left: # 12, right: # 20, prob: 0 -Vertex # 37, left: # 26, right: # 36, prob: 0 -Vertex # 38, left: # 42, right: # 45, prob: 1 -Vertex # 39, left: # 21, right: # 48, prob: 0 -Vertex # 40, left: # 2, right: # 5, prob: 1 -Vertex # 41, left: # 32, right: # 35, prob: 0 -Vertex # 42, left: # 4, right: # 31, prob: 1 -Vertex # 43, left: # 0, right: # 47, prob: 1 -Vertex # 44, left: # 6, right: # 9, prob: 1 -Vertex # 45, left: # 1, right: # 40, prob: 1 -Vertex # 46, left: # 11, right: # 18, prob: 0 -Vertex # 47, left: # 3, right: # 38, prob: 1 -Vertex # 48, left: # 10, right: # 30, prob: 0.25 +Vertex # 25, left: # 33, right: # 36, prob: 0.029 +Vertex # 26, left: # 19, right: # 20, prob: 0 +Vertex # 27, left: # 14, right: # 26, prob: 1 +Vertex # 28, left: # 10, right: # 37, prob: 0.15 +Vertex # 29, left: # 21, right: # 30, prob: 0 +Vertex # 30, left: # 18, right: # 35, prob: 0 +Vertex # 31, left: # 1, right: # 42, prob: 1 +Vertex # 32, left: # 16, right: # 41, prob: 1 +Vertex # 33, left: # 32, right: # 39, prob: 0 +Vertex # 34, left: # 0, right: # 45, prob: 1 +Vertex # 35, left: # 11, right: # 17, prob: 0 +Vertex # 36, left: # 27, right: # 28, prob: 0 +Vertex # 37, left: # 43, right: # 48, prob: 0 +Vertex # 38, left: # 6, right: # 9, prob: 1 +Vertex # 39, left: # 13, right: # 29, prob: 0.75 +Vertex # 40, left: # 5, right: # 44, prob: 1 +Vertex # 41, left: # 23, right: # 24, prob: 0 +Vertex # 42, left: # 40, right: # 47, prob: 1 +Vertex # 43, left: # 3, right: # 31, prob: 1 +Vertex # 44, left: # 8, right: # 34, prob: 1 +Vertex # 45, left: # 2, right: # 4, prob: 1 +Vertex # 46, left: # 12, right: # 22, prob: 0 +Vertex # 47, left: # 7, right: # 38, prob: 1 +Vertex # 48, left: # 15, right: # 46, prob: 1 -- --- CMake Error at /<>/etc/cmake/run_legacy_test.cmake:67 (message): Exiting test. Cheers -- Sebastian Ramacher
Bug#1063606: pax: transition from p7zip to 7zip
Source: pax Version: 1:20201030-1 Severity: normal Dear Maintainer, your package Depends/Recommends/Suggests or has some other relation to the p7zip/p7zip-full/p7zip-rar packages, which have become transitional packages in debian trixie and will eventually be removed from debian. They have been replaced by 7zip and 7zip-rar packages. If necessary, please modify your package to use the executables from the 7zip package instead. If everything everything behaves as expected, then remove p7zip/p7zip-full/p7zip-rar from the control file and replace it with 7zip and/or 7zip-rar. This bug is currently filed with normal priority but the priority will be increased as the release date of debian trixie gets closer. Thank you for maintaining software in debian.
Bug#1063605: debian-policy: mandate use of `dpkg-buildflags` for all software compilation on Debian
Package: debian-policy
Version: 4.6.2.0
Severity: important
Hi,
with the upcoming time_t & friends 64-bit transition, dpkg-buildflags
will be used to configure the ABI in use. Thus all compiler
invocations *must* use the flags specified by dpkg-buildflags to avoid
ABI inconsistencies like this one:
struct T { time_t a; time_t b; };
If this struct is accessed from both `libfoo1t64` (built respecting
dpkg-buildflags and thus time_t is 64-bit) and `bar` (built by a user
invoking gcc themselves), the result is probably not what one wants.
Thus `dpkg-buildflags` *must* be used by all packages *and* all users,
including users building their own software. There is one exception
when libraries provide both 32-bit and 64-bit time_t ABIs like glibc
itself (but I doubt there are many of those).
Any compiler invocation missing these *should* be a serious bug.
(This should probably be mentioned in user documentation as well.)
Currently Debian Policy does not mention dpkg-buildflags at all.
Ansgar
Bug#1063604: nng: FTBFS on i396, ppc64el, s390x
Source: nng Version: 1.7.2-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=nng=i386=1.7.2-1=1707038234=0 The following tests FAILED: 14 - nng.sp.protocol.bus0.bus_test (Failed) 35 - nng.supplemental.tls_test (Failed) 50 - nng.compat.compat.nanomsg.compat_tcp_test (Timeout) 53 - nng.httpserver (Failed) 57 - nng.multistress (Subprocess aborted) 64 - nng.tls (Failed) 65 - nng.tcpsupp (Failed) 66 - nng.tcp (Failed) 69 - nng.ws (Failed) 72 - nng.reqstress (Subprocess aborted) 77 - nng.compat_msg (Subprocess aborted) 85 - nng.compat_reqttl (Subprocess aborted) 87 - nng.compat_surveyttl (Subprocess aborted) Errors while running CTest make[2]: *** [Makefile:94: test] Error 8 https://buildd.debian.org/status/fetch.php?pkg=nng=ppc64el=1.7.2-1=1707038154=0 The following tests FAILED: 14 - nng.sp.protocol.bus0.bus_test (Failed) 35 - nng.supplemental.tls_test (Failed) 50 - nng.compat.compat.nanomsg.compat_tcp_test (Timeout) 53 - nng.httpserver (Failed) 57 - nng.multistress (Subprocess aborted) 64 - nng.tls (Failed) 65 - nng.tcpsupp (Failed) 66 - nng.tcp (Failed) 69 - nng.ws (Failed) 72 - nng.reqstress (Subprocess aborted) 77 - nng.compat_msg (Subprocess aborted) 85 - nng.compat_reqttl (Subprocess aborted) 87 - nng.compat_surveyttl (Subprocess aborted) Errors while running CTest make[2]: *** [Makefile:94: test] Error 8 https://buildd.debian.org/status/fetch.php?pkg=nng=s390x=1.7.2-1=1707052223=0 The following tests FAILED: 67 - nng.tcp6 (Failed) Errors while running CTest make[2]: *** [Makefile:94: test] Error 8 Cheers -- Sebastian Ramacher
Bug#1063556: [INTL:sv] Swedish strings for firebuild debconf
Hi Martin, fixed two typos in this translation. (ellr -> eller ; kommernsiella -> kommersiella ) Regards, Anders# Translation of firebuild debconf template to Swedish # Copyright (C) 2024 Martin Bagge # This file is distributed under the same license as the firebuild package. # # Martin Bagge , 2024 msgid "" msgstr "" "Project-Id-Version: firebuild\n" "Report-Msgid-Bugs-To: firebu...@packages.debian.org\n" "POT-Creation-Date: 2022-11-14 17:54+0100\n" "PO-Revision-Date: 2024-02-09 16:06+0100\n" "Last-Translator: Martin Bagge \n" "Language-Team: Swedish \n" "Language: sv\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" #. Type: boolean #. Description #: ../templates:1001 msgid "Do you accept the terms of the Firebuild license?" msgstr "Accepterar du villkoren i licensen för Firebuild?" #. Type: boolean #. Description #: ../templates:1001 msgid "" "Firebuild users are required to acknowledge and accept the license. Please " "find it below. If you accept this license, the package installation will " "continue. If you refuse it, it will be interrupted." msgstr "" "Användare av Firebuild måste aktivt bekräfta licensvillkoren, se nedan. Om " "du accepterar dessa villkor kommer paketinstallationen att fortsätta. Om " "inte så kommer installationen att avbrytas." #. Type: boolean #. Description #: ../templates:1001 msgid "Firebuild is free for personal use or commercial trial." msgstr "" "Firebuild får användas fritt för privat bruk eller som utvärdering i " "kommersiella sammanhang." #. Type: boolean #. Description #: ../templates:1001 msgid "" "Non-trial commercial use requires licenses available from https://firebuild.; "com." msgstr "" "Övrig användning i kommersiella sammanhang är inte tillåtet utan en licens " "från https://firebuild.com.; #. Type: boolean #. Description #: ../templates:1001 msgid "" "Modification and redistribution are permitted, but commercial use of " "derivative works is subject to the same requirements of this license." msgstr "" "Ändringar och vidareförmedling är tillåtet men kommersiell användning lyder " "fortsatt under samma villkor." #. Type: boolean #. Description #: ../templates:1001 msgid "" "THE SOFTWARE IS PROVIDED \"AS IS\", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR " "IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, " "FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE " "AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER " "LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING " "FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS " "IN THE SOFTWARE." msgstr "" "THE SOFTWARE IS PROVIDED \"AS IS\", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR " "IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, " "FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE " "AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER " "LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING " "FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS " "IN THE SOFTWARE." #. Type: error #. Description #: ../templates:2001 msgid "The license has been refused" msgstr "Licensvillkoren har avvisats" #. Type: error #. Description #: ../templates:2001 msgid "" "Please remove the firebuild packages or reinstall the firebuild package (e." "g. via apt-get install --reinstall firebuild) to get prompted to accept the " "license again." msgstr "" "Vänligen ta bort firebuild-paketen eller installera om firebuild-paketet " "(med hjälp av apt-get install --reinstall firebuild) för att återigen visa " "licensfrågan."
Bug#1063602: seqan-needle: FTBFS on amd64: test/api/insert_delete_test (Failed)
Source: seqan-needle Version: 1.0.2+ds-2 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=seqan-needle=amd64=1.0.2%2Bds-2=1707394988=0 2: [ RUN ] insert.ibfmin 2: unknown file: Failure 2: C++ exception with description "std::bad_alloc" thrown in the test body. 2: 2: [ FAILED ] insert.ibfmin (0 ms) [...] 2: [ FAILED ] 1 test, listed below: 2: [ FAILED ] insert.ibfmin 2: 2: 1 FAILED TEST 2/13 Test #2: test/api/insert_delete_test ...***Failed0.03 sec Cheers -- Sebastian Ramacher
Bug#1063603: composer: CVE-2024-24821
Source: composer Version: 2.6.6-1 Severity: grave Tags: security upstream Justification: user security hole X-Debbugs-Cc: car...@debian.org, Debian Security Team Hi, The following vulnerability was published for composer. CVE-2024-24821[0]: | Composer is a dependency Manager for the PHP language. In affected | versions several files within the local working directory are | included during the invocation of Composer and in the context of the | executing user. As such, under certain conditions arbitrary code | execution may lead to local privilege escalation, provide lateral | user movement or malicious code execution when Composer is invoked | within a directory with tampered files. All Composer CLI commands | are affected, including composer.phar's self-update. The following | scenarios are of high risk: Composer being run with sudo, Pipelines | which may execute Composer on untrusted projects, Shared | environments with developers who run Composer individually on the | same project. This vulnerability has been addressed in versions | 2.7.0 and 2.2.23. It is advised that the patched versions are | applied at the earliest convenience. Where not possible, the | following should be addressed: Remove all sudo composer privileges | for all users to mitigate root privilege escalation, and avoid | running Composer within an untrusted directory, or if needed, verify | that the contents of `vendor/composer/InstalledVersions.php` and | `vendor/composer/installed.php` do not include untrusted code. A | reset can also be done on these files by the following:```sh rm | vendor/composer/installed.php vendor/composer/InstalledVersions.php | composer install --no-scripts --no-plugins ``` 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-24821 https://www.cve.org/CVERecord?id=CVE-2024-24821 [1] https://github.com/composer/composer/security/advisories/GHSA-7c6p-848j-wh5h [2] https://github.com/composer/composer/commit/64e4eb356b159a30c766cd1ea83450a38dc23bf5 Please adjust the affected versions in the BTS as needed. Regards, Salvatore
Bug#1063601: tailspin: FTBFS: error[E0407]: method `backtrace` is not a member of trait `Error`
Source: tailspin
Version: 3.0.0+dfsg-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=tailspin=amd64=3.0.0%2Bdfsg-1=1706195420=0
Running
`/<>/target/release/build/eyre-15058028a1ebd405/build-script-build`
[eyre 0.6.8] error[E0407]: method `backtrace` is not a member of trait `Error`
[eyre 0.6.8] -->
/<>/target/x86_64-unknown-linux-gnu/release/build/eyre-eb1eb971e427fb49/out/probe.rs:19:9
[eyre 0.6.8]|
[eyre 0.6.8] 19 | / fn backtrace() -> Option<> {
[eyre 0.6.8] 20 | | let backtrace = Backtrace::capture();
[eyre 0.6.8] 21 | | match backtrace.status() {
[eyre 0.6.8] 22 | | BacktraceStatus::Captured |
BacktraceStatus::Disabled | _ => {}
[eyre 0.6.8] 23 | | }
[eyre 0.6.8] 24 | | unimplemented!()
[eyre 0.6.8] 25 | | }
[eyre 0.6.8]| |_^ not a member of trait `Error`
[eyre 0.6.8]
[eyre 0.6.8] error[E0554]: `#![feature]` may not be used on the stable release
channel
[eyre 0.6.8] -->
/<>/target/x86_64-unknown-linux-gnu/release/build/eyre-eb1eb971e427fb49/out/probe.rs:2:16
[eyre 0.6.8] |
[eyre 0.6.8] 2 | #![feature(backtrace)]
[eyre 0.6.8] |^
[eyre 0.6.8]
[eyre 0.6.8] warning: the feature `backtrace` has been stable since 1.65.0 and
no longer requires an attribute to enable
[eyre 0.6.8] -->
/<>/target/x86_64-unknown-linux-gnu/release/build/eyre-eb1eb971e427fb49/out/probe.rs:2:16
[eyre 0.6.8] |
[eyre 0.6.8] 2 | #![feature(backtrace)]
[eyre 0.6.8] |^
[eyre 0.6.8] |
[eyre 0.6.8] = note: `#[warn(stable_features)]` on by default
[eyre 0.6.8]
[eyre 0.6.8] error: aborting due to 2 previous errors; 1 warning emitted
[eyre 0.6.8]
[eyre 0.6.8] Some errors have detailed explanations: E0407, E0554.
[eyre 0.6.8] For more information about an error, try `rustc --explain E0407`.
[eyre 0.6.8] cargo:rustc-cfg=track_caller
Cheers
--
Sebastian Ramacher
Bug#1063600: open3d: FTBFS: embree3/rtcore.h: No such file or directory
Source: open3d Version: 0.17.0+ds-9 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=open3d=amd64=0.17.0%2Bds-9%2Bb1=1705418499=0 [ 44%] Building CXX object cpp/open3d/t/geometry/CMakeFiles/tgeometry.dir/RaycastingScene.cpp.o cd /<>/obj-x86_64-linux-gnu/cpp/open3d/t/geometry && /usr/bin/c++ -DBUILD_GUI -DFMT_SHARED -DOPEN3D_CUDA_COMPILER_ID=\"\" -DOPEN3D_CUDA_COMPILER_VERSION=\"\" -DOPEN3D_CXX_COMPILER_ID=\"GNU\" -DOPEN3D_CXX_COMPILER_VERSION=\"13.2.0\" -DOPEN3D_CXX_STANDARD=\"17\" -DOPEN3D_ENABLE_DLL_EXPORTS -DUNIX -DUSE_BLAS -DZMQ_STATIC -D_FORTIFY_SOURCE=2 -D_GLIBCXX_USE_CXX11_ABI=1 -D__TBB_LIB_NAME=tbb_static -Dkiss_fft_scalar=double -I/<>/cpp -I/<> -isystem /<>/3rdparty/tomasakeninemoeller/include -isystem /<>/3rdparty/rply/rply -isystem /<>/3rdparty/tinyfiledialogs/include -isystem /usr/include/vtk-9.1 -isystem /usr/include/jsoncpp -isystem /usr/include/liblzf -isystem /usr/include/minizip -isystem /usr/include/imgui -isystem /usr/include/pgm-5.3 -isystem /usr/include/libxml2 -isystem /usr/include/mit-krb5 -isystem /usr/include/eigen3 -isystem /usr/include/filament-1.9 -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -faligned-new -Wno-psabi -Wdate-time -D_FORTIFY_SOURCE=2 -std=gnu++17 -fPIC -Wall -Wextra -Wno-unused-parameter -fstack-protector-strong -Wformat -Wformat-security -fopenmp -MD -MT cpp/open3d/t/geometry/CMakeFiles/tgeometry.dir/RaycastingScene.cpp.o -MF CMakeFiles/tgeometry.dir/RaycastingScene.cpp.o.d -o CMakeFiles/tgeometry.dir/RaycastingScene.cpp.o -c /<>/cpp/open3d/t/geometry/RaycastingScene.cpp /<>/cpp/open3d/t/geometry/RaycastingScene.cpp:15:10: fatal error: embree3/rtcore.h: No such file or directory 15 | #include | ^~ compilation terminated. make[3]: *** [cpp/open3d/t/geometry/CMakeFiles/tgeometry.dir/build.make:219: cpp/open3d/t/geometry/CMakeFiles/tgeometry.dir/RaycastingScene.cpp.o] Error 1 Cheers -- Sebastian Ramacher
Bug#1063599: mathgl: FTBFS on amd64: tests seg fault
Source: mathgl Version: 8.0.1-5 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=mathgl=amd64=8.0.1-5=1704780389=0 ape.png: ok tens.png: ok ternary.png: ok text.png: ok text2.png: ok textmark.png: ok ticks.png: ok tile.png: ok tiles.png: ok torus.png: ok traj.png: ok triangulation.png: ok triplot.png: ok tube.png: ok type0.png: ok type1.png: ok type2.png: ok vect.png: ok vect3.png: ok venn.png: ok Segmentation fault make[1]: *** [debian/rules:59: override_dh_auto_test] Error 139 make[1]: Leaving directory '/<>' Cheers -- Sebastian Ramacher
Bug#1063598: python-fastparquet: FTBFS: Python.h: No such file or directory
Source: python-fastparquet Version: 2023.10.1-2 Severity: serious Tags: ftbfs Justification: fails to build from source X-Debbugs-Cc: sramac...@debian.org https://buildd.debian.org/status/fetch.php?pkg=python-fastparquet=amd64=2023.10.1-2=1704222935=0 building 'fastparquet.speedups' extension creating build/temp.linux-x86_64-cpython-312 creating build/temp.linux-x86_64-cpython-312/fastparquet x86_64-linux-gnu-gcc -fno-strict-overflow -Wsign-compare -DNDEBUG -g -O2 -Wall -g -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -g -fwrapv -O2 -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -I/usr/include/python3.12 -I/usr/lib/python3/dist-packages/numpy/core/include -c fastparquet/speedups.c -o build/temp.linux-x86_64-cpython-312/fastparquet/speedups.o fastparquet/speedups.c:29:10: fatal error: Python.h: No such file or directory 29 | #include "Python.h" | ^~ compilation terminated. error: command '/usr/bin/x86_64-linux-gnu-gcc' failed with exit code 1 ERROR Backend subprocess exited when trying to invoke build_wheel Cheers -- Sebastian Ramacher
Bug#1063597: giac: FTBFS on amd64: tests seg fault
Source: giac Version: 1.9.0.69+dfsg2-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=giac=amd64=1.9.0.69%2Bdfsg2-1%2Bb1=1707503131=0 FAIL: chk_factor // Using locale /usr/share/locale/ // C.UTF-8 // /usr/share/locale/ // giac // UTF-8 // Maximum number of parallel threads 4 // Unable to find keyword file doc/en/keywords Added 0 synonyms // Time 0 // Time 0 // Time 0 // Time 0.01 // Time 0 // Time 0 // Time 0 // Time 0 // Time 0 // Time 0 // Time 0 // Time 0 // Time 0.01 // Time 0 // Time 0 // Time 0 // Time 0 // Time 0 // Time 0 // Time 0 // Time 0 // Time 0.01 // Time 0 // Time 0 // Time 0.01 // Time 0 // Time 0 // Time 0 Segmentation fault 28a29,32 > (5*x+11)*(8*x+1)*(12*x-13)*(15*x+8)*(30*x-31)*(120*x-209), > (x^20-x^15+x^10-x^5+1)*(x^20+x^15+x^10+x^5+1), > (x^2-x+1)*(x^2+x+1)*(x^8-x^7+x^5-x^4+x^3-x+1)*(x^8+x^7-x^5-x^4-x^3+x+1)*(x^40-x^35+x^25-x^20+x^15-x^5+1)*(x^40+x^35-x^25-x^20-x^15+x^5+1), > x^200-x^199+x^197-x^196+x^194-x^193+x^191-x^190+x^188-x^187+x^185-x^184+x^182-x^181+x^179-x^178+x^176-x^175+x^173-x^172+x^170-x^169+x^167-x^166+x^164-x^163+x^161-x^160+x^158-x^157+x^155-x^154+x^152-x^151+x^149-x^148+x^146-x^145+x^143-x^142+x^140-x^139+x^137-x^136+x^134-x^133+x^131-x^130+x^128-x^127+x^125-x^124+x^122-x^121+x^119-x^118+x^116-x^115+x^113-x^112+x^110-x^109+x^107-x^106+x^104-x^103+x^101-x^100+x^99-x^97+x^96-x^94+x^93-x^91+x^90-x^88+x^87-x^85+x^84-x^82+x^81-x^79+x^78-x^76+x^75-x^73+x^72-x^70+x^69-x^67+x^66-x^64+x^63-x^61+x^60-x^58+x^57-x^55+x^54-x^52+x^51-x^49+x^48-x^46+x^45-x^43+x^42-x^40+x^39-x^37+x^36-x^34+x^33-x^31+x^30-x^28+x^27-x^25+x^24-x^22+x^21-x^19+x^18-x^16+x^15-x^13+x^12-x^10+x^9-x^7+x^6-x^4+x^3-x+1 FAIL chk_factor (exit status: 1) Cheers -- Sebastian Ramacher
Bug#1057562: gcr4: FTBFS: failing tests
Control: tags -1 serious Hi On 2024-01-21 10:26:19 -0500, Jeremy Bícha wrote: > Control: severity -1 important > > I believe the gcr tests are just flaky. They are now also failing on the buildds: https://buildd.debian.org/status/fetch.php?pkg=gcr4=amd64=4.1.0-2%2Bb1=1707501299=0 If they are flaky, please disable them or - if possible - make them non-flaky. Cheers -- Sebastian Ramacher
Bug#1063596: flint: FTBFS on amd64: test segfault
Source: flint Version: 3.0.1-3 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=flint=amd64=3.0.1-3=1707499549=0 powmod_x_fmpz_preinv...PASS randtest_irreduciblePASS scalar_addmul_fq... PASS scalar_div_fq... PASS scalar_mul_fq... PASS scalar_submul_fq... PASS set_fmpz_poly... PASS set_nmod_poly... PASS set_trunc... PASS PASS sqr... shift_left/right... PASS sqr_KS... PASS sqr_classical... PASS sqrt... PASS sqrt_seriesPASS sub... PASS sub_series... PASS xgcdPASS xgcd_euclidean_fPASS ctx_init_modulusPASS ctx_init_modulus_nmodPASS PASS make[2]: *** [Makefile:663: build/fq_default/test/t-ctx_init_modulus_nmod_TEST_RUN] Segmentation fault make[2]: *** Waiting for unfinished jobs PASS ctx_modulusPASS Cheers -- Sebastian Ramacher
Bug#1063595: mimedefang: let dh_installsystemd install units for DEP17
Package: mimedefang Version: 3.3-1 Tags: patch User: helm...@debian.org Usertags: dep17m2 Hi, we want to move all aliased files from / to /usr to finalize the /usr-merge transition via DEP17. mimedefang is involved, because it manually install systemd units. I recommend using dh_installsystemd, because it automatically chooses the right location of units and am attaching a patch for this. In addition to applying the patch, you need to invoke two commands: ln -s ../systemd-units/mimedefang-multiplexor.service debian/mimedefang.mimedefang-multiplexor.service ln -s ../systemd-units/mimedefang.service debian/mimedefang.service These symlinks are not representable in a debdiff. Unlike moving the units manualy, using dh_installsystemd is safe in the face to backports. Helmut diff --minimal -Nru mimedefang-3.3/debian/changelog mimedefang-3.3/debian/changelog --- mimedefang-3.3/debian/changelog 2023-01-30 18:00:55.0 +0100 +++ mimedefang-3.3/debian/changelog 2024-02-09 17:40:37.0 +0100 @@ -1,3 +1,10 @@ +mimedefang (3.3-1.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Install systemd units using dh_installsystemd (closes: #-1) + + -- Helmut Grohne Fri, 09 Feb 2024 17:40:37 +0100 + mimedefang (3.3-1) unstable; urgency=medium * New upstream version 3.3 diff --minimal -Nru mimedefang-3.3/debian/mimedefang.dirs mimedefang-3.3/debian/mimedefang.dirs --- mimedefang-3.3/debian/mimedefang.dirs 2023-01-30 18:00:55.0 +0100 +++ mimedefang-3.3/debian/mimedefang.dirs 2024-02-09 17:38:07.0 +0100 @@ -2,4 +2,3 @@ usr/sbin etc/mail usr/share/mimedefang -lib/systemd/system diff --minimal -Nru mimedefang-3.3/debian/rules mimedefang-3.3/debian/rules --- mimedefang-3.3/debian/rules 2023-01-30 18:00:55.0 +0100 +++ mimedefang-3.3/debian/rules 2024-02-09 17:40:37.0 +0100 @@ -71,7 +71,6 @@ $(MAKE) install DESTDIR=$(CURDIR)/debian/mimedefang cp debian/mimedefang.conf debian/mimedefang/usr/share/mimedefang/ cp debian/mimedefang.pl.conf debian/mimedefang/etc/mail/mimedefang.pl.conf - cp -p systemd-units/*.service debian/mimedefang/lib/systemd/system/ rmdir debian/mimedefang/usr/sbin # rmdir debian/mimedefang/etc/spamassassin @@ -104,6 +103,8 @@ # dh_installmime cp -p examples/init-script debian/init.d dh_installinit + dh_installsystemd --no-enable --no-start + dh_installsystemd --name=mimedefang-multiplexor --no-enable --no-start dh_installcron dh_installman dh_installinfo
Bug#1063594: patool: transition from p7zip to 7zip
Source: patool Version: 2.0.0-2 Severity: normal Dear Maintainer, your package Depends/Recommends/Suggests or has some other relation to the p7zip/p7zip-full/p7zip-rar packages, which have become transitional packages in debian trixie and will eventually be removed from debian. They have been replaced by 7zip and 7zip-rar packages. If necessary, please modify your package to use the executables from the 7zip package instead. If everything everything behaves as expected, then remove p7zip/p7zip-full/p7zip-rar from the control file and replace it with 7zip and/or 7zip-rar. This bug is currently filed with normal priority but the priority will be increased as the release date of debian trixie gets closer. Thank you for maintaining software in debian.
Bug#1063593: megaglest: transition from p7zip to 7zip
Source: megaglest Version: 3.13.0-9 Severity: normal Dear Maintainer, your package Depends/Recommends/Suggests or has some other relation to the p7zip/p7zip-full/p7zip-rar packages, which have become transitional packages in debian trixie and will eventually be removed from debian. They have been replaced by 7zip and 7zip-rar packages. If necessary, please modify your package to use the executables from the 7zip package instead. If everything everything behaves as expected, then remove p7zip/p7zip-full/p7zip-rar from the control file and replace it with 7zip and/or 7zip-rar. This bug is currently filed with normal priority but the priority will be increased as the release date of debian trixie gets closer. Thank you for maintaining software in debian.
Bug#1063592: mcomix: transition from p7zip to 7zip
Source: mcomix Version: 3.0.0-1 Severity: normal Dear Maintainer, your package Depends/Recommends/Suggests or has some other relation to the p7zip/p7zip-full/p7zip-rar packages, which have become transitional packages in debian trixie and will eventually be removed from debian. They have been replaced by 7zip and 7zip-rar packages. If necessary, please modify your package to use the executables from the 7zip package instead. If everything everything behaves as expected, then remove p7zip/p7zip-full/p7zip-rar from the control file and replace it with 7zip and/or 7zip-rar. This bug is currently filed with normal priority but the priority will be increased as the release date of debian trixie gets closer. Thank you for maintaining software in debian.
Bug#1062016: Consider providing separate librsvg2 package
On Wed, 31 Jan 2024 00:14:50 +0100 Matthias Geiger wrote: > please consider providing a librust-librsvg2-dev package. This should > just install the rust source files under > /usr/share/cargo/registry/librsvg2-VERSION. This will be needed by > loupe/glycin to load svgs (other crates also started depend on > librsvg2). > > f_g: Is an install of those files compatible with our setup even if some > deps of librsvg2 are not in debian yet (it's built vendored) ? Hi (f_g here ;)), For librsvg to be usable as a Rust dependency in Debian, all its dependencies (which are currently vendored) also need to be packaged as Rust source code in a way that allows rdeps of librust-librsvg-dev to find them. There are two approaches for the vendored deps: 1) package each of them in the regular fashion (if missing, upgrading/.. otherwise), and build-depend on them in src:librsvg instead of vendoring them 2) ship them in some non-standard path (from the vendored copies), but make cargo pick them up via some hack (patch/source replacement, path deps, extra vendoring step in d/rules of all rdeps, ..) Building a librust-librsvg-dev containing the librsvg Rust source (and for variant 2 above, the vendored sources) should be fairly straight-forward. Obviously 1) is the cleaner approach, since it would also allow src:libsrvg to stop vendoring its Rust dependencies, reducing the number of duplicate copies in the archive. I am not sure what sort of exception/agreement there is in place w.r.t. librsvg's current vendoring, and whether that should be re-evaluated now that it is properly published on crates.io and no longer uses vendoring upstream (AFAICT). The main downside is that currently non-vendored statically linked Rust binaries/cdylibs only have "limited" security support. IMHO this is something we should try to solve during the Trixie release cycle, or at least start working on in earnest.
Bug#1063591: ITP: anew -- Tool for adding new lines to files, skipping duplicates (program)
Package: wnpp Severity: wishlist Owner: "Marcos Rodrigues de Carvalho (aka oday)" X-Debbugs-Cc: debian-de...@lists.debian.org, debian...@lists.debian.org , marcosrcarvalh...@gmail.com * Package name: anew Version : 0.1-1 Upstream Contact: Tom Hudson * URL : https://github.com/tomnomnom/anew * License : Expat Programming Lang: Go Description : Tool for adding new lines to files, skipping duplicates (program) This program provides a tool for adding new lines to files while ensuring that duplicate lines are skipped. It offers a convenient solution for managing text files by preventing redundant data. The tool is designed to streamline file editing processes and improve efficiency when working with large datasets or configuration files. It can be useful in various scenarios, such as log management, data processing, and configuration management tasks.
Bug#1062703: firmware-realtek: Direct firmware load for rtl_nic/rtl8125b-2.fw failed with error -2
Control: tag -1 moreinfo Hi, On Friday, 9 February 2024 19:35:01 CET Miguel A. Rojas wrote: > A few days ago, I went to > https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git > and update the missing loaded modules. > > Indeed, I noticed that I have another messages related to the iwlwifi > module: "kernel: iwlwifi :00:14.3: firmware: failed to load > iwlwifi-so-a0-hr-b0-83.ucode (-2)". The reason I asked for more dmesg lines is that it likely then tried (f.e.) -81, then -79 and then probably succeeded at some point. The Debian kernel (unfortunately imo) 'promoted' warning/info messages to errors, which make it appear more severe then they actually are. > I think the the root cause is that the current Debian packages firmware > packages are 6 months old and they need to be updated accordingly. New > Debian Linux kernel expects a specific version of the firmware or the > name of the firmware has changed. I do think that the old package versions are a problem, so I have been working on Merge Requests for updating them. Version 20230804 would make the -83 file available. But the device using and older version should still work. If it doesn't work with an older version, but it does work with a newer, that's important info. But I'm still a bit confused as this bug is about *realtek* firmware, not iwlwifi? Can you answer the question I asked previously? signature.asc Description: This is a digitally signed message part.
Bug#1063590: debian-reference-common: debian-reference and mkindexhtml are broken
Package: debian-reference-common Version: 2.113 Severity: important Dear Osamu Aoki, as far as I understand the scripts /usr/share/debian-reference-common/mkindexhtml and /usr/bin/debian-reference are broken since the move of the documents to /usr/share/doc/debian-reference-common/docs . The scripts still use /usr/share/doc/debian-reference as DR_DOC_ROOT which should now be /usr/share/doc/debian-reference-common . Therefore, during installation no index.html is generated and calling debian-reference fails silently. Regards, Jörg. -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (600, 'testing'), (500, 'unstable'), (5, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.7.3 (SMP w/16 CPU threads) Locale: LANG=C.utf8, LC_CTYPE=C.utf8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: sysvinit (via /sbin/init) Versions of packages debian-reference-common depends on: ii sensible-utils 0.0.22 Versions of packages debian-reference-common recommends: ii firefox [www-browser] 122.0.1-1 ii w3m [www-browser] 0.5.3+git20230121-2 Versions of packages debian-reference-common suggests: pn calibre pn debian-reference pn debian-reference-de ii debian-reference-en 2.113 pn debian-reference-es pn debian-reference-fr pn debian-reference-id pn debian-reference-it pn debian-reference-ja pn debian-reference-pt pn debian-reference-zh-cn pn debian-reference-zh-tw pn mc pn vim -- no debconf information
Bug#1063589: multiqc fails autopkg tests with Python 3.12
Package: src:multiqc
Version: 1.14+dfsg-1.1
Severity: important
Tags: sid trixie ftbfs
User: debian-pyt...@lists.debian.org
Usertags: python3.12
[...]
362s autopkgtest [09:34:55]: test run-unit-test: [---
370s Traceback (most recent call last):
370s File "/usr/bin/multiqc", line 33, in
370s sys.exit(load_entry_point('multiqc==1.14', 'console_scripts',
'multiqc')())
370s
^^^
370s File "/usr/bin/multiqc", line 25, in importlib_load_entry_point
370s return next(matches).load()
370s
370s File "/usr/lib/python3.12/importlib/metadata/__init__.py", line
205, in load
370s module = import_module(match.group('module'))
370s
370s File "/usr/lib/python3.12/importlib/__init__.py", line 90, in
import_module
370s return _bootstrap._gcd_import(name[level:], package, level)
370s
370s File "", line 1387, in _gcd_import
370s File "", line 1360, in _find_and_load
370s File "", line 1310, in
_find_and_load_unlocked
370s File "", line 488, in
_call_with_frames_removed
370s File "", line 1387, in _gcd_import
370s File "", line 1360, in _find_and_load
370s File "", line 1331, in
_find_and_load_unlocked
370s File "", line 935, in _load_unlocked
370s File "", line 994, in
exec_module
370s File "", line 488, in
_call_with_frames_removed
370s File "/usr/lib/python3/dist-packages/multiqc/__init__.py", line
16, in
370s from .multiqc import run
370s File "/usr/lib/python3/dist-packages/multiqc/multiqc.py", line
21, in
370s from distutils import version
370s ModuleNotFoundError: No module named 'distutils'
370s autopkgtest [09:35:03]: test run-unit-test: ---]
Bug#1063588: nibabel fails to run with Python 3.12 as the default
Package: src:nibabel Version: 5.2.0-2 Severity: important Tags: sid trixie ftbfs User: debian-pyt...@lists.debian.org Usertags: python3.12 [...] 359s autopkgtest [08:34:15]: test run-unit-test: [--- 362s = test session starts == 362s platform linux -- Python 3.12.2, pytest-7.4.4, pluggy-1.4.0 -- /usr/bin/python3.12 362s cachedir: .pytest_cache 362s rootdir: /tmp/autopkgtest.opYRhs/build.LA4/src 362s plugins: pytest_httpserver-1.0.8 373s collecting ... collected 5649 items / 1 error 373s 373s ERRORS 373s _ ERROR collecting nisext/tests/test_sexts.py __ 373s ImportError while importing test module '/tmp/autopkgtest.opYRhs/build.LA4/src/nisext/tests/test_sexts.py'. 373s Hint: make sure your test modules/packages have valid Python names. 373s Traceback: 373s /usr/lib/python3.12/importlib/__init__.py:90: in import_module 373s return _bootstrap._gcd_import(name[level:], package, level) 373s nisext/tests/test_sexts.py:9: in 373s from ..sexts import package_check 373s nisext/sexts.py:5: in 373s from distutils import log 373s E ModuleNotFoundError: No module named 'distutils' 373s === warnings summary === 373s nibabel/testing/__init__.py:29 373s /tmp/autopkgtest.opYRhs/build.LA4/src/nibabel/testing/__init__.py:29: DeprecationWarning: 'importlib.abc.Traversable' is deprecated and slated for removal in Python 3.14 373s from importlib.abc import Traversable 373s 373s nisext/__init__.py:10 373s /tmp/autopkgtest.opYRhs/build.LA4/src/nisext/__init__.py:10: UserWarning: The nisext package is deprecated as of NiBabel 5.0 and will be fully 373s removed in NiBabel 6.0 373s warnings.warn( 373s 373s -- Docs: https://docs.pytest.org/en/stable/how-to/capture-warnings.html 373s === short test summary info 373s ERROR nisext/tests/test_sexts.py 373s Interrupted: 1 error during collection 373s 2 warnings, 1 error in 11.27s =
Bug#980049: fwupd: Should fwupd specify dbus as a dependency?
I can't help but feel this needs to be rethought. If I install the current Debian 12 via netinst and choose not to install 'standard system utilities'... a choice many people take if they prefer to install their own set of utilities instead... and a choice which doesn't advertise any negative connotations for unchecking it... Then it means the debootstrap process that debian-installer did... won't install dbus (as it's only a recommends of systemd)... and dbus won't be installed from 'standard system utilities' either. From this point, there are two scenarios... If you've got recommends enabled on your system... Installing the fwupd package will automatically try to start the fwupmgr service and fail because the dbus package it just installed (because dbus is a recommends of fwupd) won't automatically start and stays inactive unless you active it or reboot. This gives you an ugly **red error message** in the apt-get output of... "dbus.service is not active, cannot reload." If you've got recommends disabled on your system... (a perfectly valid scenario, but there are haters of this!)... Installing the fwupd package will automatically try to start the fwupmgr service and fail because dbus isn't installed. This gives you an ugly **red error message** in the apt-get output of... "Failed to reload dbus.service: Unit dbus.service not found." I know that some people just install fwupd to use the fwuptool manually which works just fine without fwupdmgr... But unless this package is split into two (one for the fwupmgr service, one for fwupdtool), or unless it is reconfigured so it doesn't try to automatically start fwupmgr... then I can't see how dbus shouldn't be considered a depend for fwupd. It literally can't perform one of its main functions, a function that is automatically started, and shows an error!.. without it!
Bug#1062703: firmware-realtek: Direct firmware load for rtl_nic/rtl8125b-2.fw failed with error -2
Hi Diederik, A few days ago, I went to https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git and update the missing loaded modules. Indeed, I noticed that I have another messages related to the iwlwifi module: "kernel: iwlwifi :00:14.3: firmware: failed to load iwlwifi-so-a0-hr-b0-83.ucode (-2)". I think the the root cause is that the current Debian packages firmware packages are 6 months old and they need to be updated accordingly. New Debian Linux kernel expects a specific version of the firmware or the name of the firmware has changed. Regards O
Bug#1063584: python-skbio: tests fail with scipy 1.11
Evidently fixed upstream with https://github.com/scikit-bio/scikit-bio/pull/1887 see also https://github.com/scikit-bio/scikit-bio/pull/1930 (for python 3.12)
Bug#1063587: bpftrace: Fails to find individual uprobes with 'No probes to attach'
Package: bpftrace
Version: 0.20.1-1
Severity: important
Hi,
bpftrace in sid fails to find individual uprobes, but strangely manages
to find them if using a wildcard. The uprobe then seems to behave as
expected, it can print arguments and such.
root@testvm:~# bpftrace -e 'uprobe:/bin/ls:format_user_or_group {}'
No probes to attach
root@testvm:~# bpftrace -e 'uprobe:/bin/ls:format_user_or_grou* {}'
Attaching 1 probe...
Kprobes are not affected:
root@testvm:~# bpftrace -e 'kprobe:icmp_echo {}'
Attaching 1 probe...
This is with bpftrace 0.20.1-1, kernel 6.6.13-1, coreutils 9.4-3+b1 (and
related -dbgsym package) on a clean amd64 test VM.
Bug#1063586: lxqt-archiver: transition from p7zip to 7zip
Source: lxqt-archiver Version: 0.8.0-3 Severity: normal Dear Maintainer, your package Depends/Recommends/Suggests or has some other relation to the p7zip/p7zip-full/p7zip-rar packages, which have become transitional packages in debian trixie and will eventually be removed from debian. They have been replaced by 7zip and 7zip-rar packages. If necessary, please modify your package to use the executables from the 7zip package instead. If everything everything behaves as expected, then remove p7zip/p7zip-full/p7zip-rar from the control file and replace it with 7zip and/or 7zip-rar. This bug is currently filed with normal priority but the priority will be increased as the release date of debian trixie gets closer. Thank you for maintaining software in debian.
Bug#1058997: Patch is not sufficient (Was: flask-autoindex is incompatible with Py3.12)
Control: tags -1 - patch Hi Alexandre, I've applied your patch in Git but as you can see in Salsa CI[1] it is not sufficient to fix the build issue. Kind regards and thanks for your help anyway Andreas. [1] https://salsa.debian.org/python-team/packages/flask-autoindex/-/jobs/5272253 -- http://fam-tille.de
Bug#1029701: scikit-learn: tests fail with scipy 1.10
Source: scikit-learn Version: 1.2.1+dfsg-1 Followup-For: Bug #1029701 scikit-learn continues to fail with scipy 1.11 from experimental 648s FAILED ../../../../usr/lib/python3/dist-packages/sklearn/linear_model/tests/test_quantile.py::test_incompatible_solver_for_sparse_input[interior-point] 648s FAILED ../../../../usr/lib/python3/dist-packages/sklearn/linear_model/tests/test_quantile.py::test_linprog_failure 648s FAILED ../../../../usr/lib/python3/dist-packages/sklearn/linear_model/tests/test_quantile.py::test_warning_new_default 648s FAILED ../../../../usr/lib/python3/dist-packages/sklearn/metrics/tests/test_dist_metrics.py::test_cdist_bool_metric[X_bool0-Y_bool0-kulsinski] 648s FAILED ../../../../usr/lib/python3/dist-packages/sklearn/metrics/tests/test_dist_metrics.py::test_cdist_bool_metric[X_bool1-Y_bool1-kulsinski] 648s FAILED ../../../../usr/lib/python3/dist-packages/sklearn/metrics/tests/test_dist_metrics.py::test_pdist_bool_metrics[X_bool0-kulsinski] 648s FAILED ../../../../usr/lib/python3/dist-packages/sklearn/metrics/tests/test_dist_metrics.py::test_pdist_bool_metrics[X_bool1-kulsinski] 648s FAILED ../../../../usr/lib/python3/dist-packages/sklearn/metrics/tests/test_pairwise.py::test_pairwise_boolean_distance[kulsinski] 648s FAILED ../../../../usr/lib/python3/dist-packages/sklearn/neighbors/tests/test_neighbors.py::test_kneighbors_brute_backend[float64-kulsinski] 648s FAILED ../../../../usr/lib/python3/dist-packages/sklearn/neighbors/tests/test_neighbors.py::test_radius_neighbors_brute_backend[kulsinski] 648s FAILED ../../../../usr/lib/python3/dist-packages/sklearn/preprocessing/tests/test_data.py::test_power_transformer_yeojohnson_any_input[X3] 648s FAILED ../../../../usr/lib/python3/dist-packages/sklearn/tests/test_base.py::test_clone_sparse_matrices 648s FAILED ../../../../usr/lib/python3/dist-packages/sklearn/tests/test_common.py::test_estimators[PowerTransformer()-check_fit2d_1sample] 648s = 13 failed, 24496 passed, 2459 skipped, 2 deselected, 116 xfailed, 43 xpassed, 2600 warnings in 577.48s (0:09:37) = scipy 1.11 is currently in experimental but I'd like to upload soon to unstable to resolve Bug#1061605, which would make this bug serious. It's likely fixed in the newer upstream releases.
Bug#1063585: lutris: transition from p7zip to 7zip
Source: lutris Version: 0.5.14-2 Severity: normal Dear Maintainer, your package Depends/Recommends/Suggests or has some other relation to the p7zip/p7zip-full/p7zip-rar packages, which have become transitional packages in debian trixie and will eventually be removed from debian. They have been replaced by 7zip and 7zip-rar packages. If necessary, please modify your package to use the executables from the 7zip package instead. If everything everything behaves as expected, then remove p7zip/p7zip-full/p7zip-rar from the control file and replace it with 7zip and/or 7zip-rar. This bug is currently filed with normal priority but the priority will be increased as the release date of debian trixie gets closer. Thank you for maintaining software in debian.
Bug#1063584: python-skbio: tests fail with scipy 1.11
Source: python-skbio Version: 0.5.9-3 Severity: normal Control: block 1061605 by -1 python-skbio is failing various tests with scipy 1.11 from experimental 150s FAILED skbio/diversity/alpha/tests/test_base.py::BaseTests::test_fisher_alpha 150s FAILED skbio/diversity/tests/test_driver.py::BetaDiversityTests::test_available_metrics 150s FAILED skbio/diversity/tests/test_driver.py::BetaDiversityTests::test_qualitative_bug_issue_1549 150s FAILED skbio/stats/tests/test_composition.py::AncomTests::test_ancom_fail_multiple_groups scipy 1.11 is currently in experimental but I'd like to upload soon to unstable to resolve Bug#1061605, which would make this bug serious.
Bug#1063583: krusader: transition from p7zip to 7zip
Source: krusader Version: 2:2.8.0-1 Severity: normal Dear Maintainer, your package Depends/Recommends/Suggests or has some other relation to the p7zip/p7zip-full/p7zip-rar packages, which have become transitional packages in debian trixie and will eventually be removed from debian. They have been replaced by 7zip and 7zip-rar packages. If necessary, please modify your package to use the executables from the 7zip package instead. If everything everything behaves as expected, then remove p7zip/p7zip-full/p7zip-rar from the control file and replace it with 7zip and/or 7zip-rar. This bug is currently filed with normal priority but the priority will be increased as the release date of debian trixie gets closer. Thank you for maintaining software in debian.
Bug#1063582: kinect-audio-setup: transition from p7zip to 7zip
Source: kinect-audio-setup Version: 0.5-1 Severity: normal Dear Maintainer, your package Depends/Recommends/Suggests or has some other relation to the p7zip/p7zip-full/p7zip-rar packages, which have become transitional packages in debian trixie and will eventually be removed from debian. They have been replaced by 7zip and 7zip-rar packages. If necessary, please modify your package to use the executables from the 7zip package instead. If everything everything behaves as expected, then remove p7zip/p7zip-full/p7zip-rar from the control file and replace it with 7zip and/or 7zip-rar. This bug is currently filed with normal priority but the priority will be increased as the release date of debian trixie gets closer. Thank you for maintaining software in debian.
Bug#1063581: gnumed-client: transition from p7zip to 7zip
Source: gnumed-client Version: 1.8.18+dfsg-1 Severity: normal Dear Maintainer, your package Depends/Recommends/Suggests or has some other relation to the p7zip/p7zip-full/p7zip-rar packages, which have become transitional packages in debian trixie and will eventually be removed from debian. They have been replaced by 7zip and 7zip-rar packages. If necessary, please modify your package to use the executables from the 7zip package instead. If everything everything behaves as expected, then remove p7zip/p7zip-full/p7zip-rar from the control file and replace it with 7zip and/or 7zip-rar. This bug is currently filed with normal priority but the priority will be increased as the release date of debian trixie gets closer. Thank you for maintaining software in debian.
Bug#1063580: game-data-packager: transition from p7zip to 7zip
Package: game-data-packager Severity: normal Dear Maintainer, your package Depends/Recommends/Suggests or has some other relation to the p7zip/p7zip-full/p7zip-rar packages, which have become transitional packages in debian trixie and will eventually be removed from debian. They have been replaced by 7zip and 7zip-rar packages. If necessary, please modify your package to use the executables from the 7zip package instead. If everything everything behaves as expected, then remove p7zip/p7zip-full/p7zip-rar from the control file and replace it with 7zip and/or 7zip-rar. This bug is currently filed with normal priority but the priority will be increased as the release date of debian trixie gets closer. Thank you for maintaining software in debian.
Bug#1063579: ITP: hexwalk -- hex editor/viewer/analyzer
Package: wnpp Severity: wishlist * Package name : hexwalk Version : 1.6.0 Upstream Author : Carmix * URL : https://github.com/gcarmix/hexwalk * License : GPL Programming Lang: C++ Description : hex editor viewer analyzer HexWalk is an Hex editor, viewer, analyzer. Based on opensource projects like qhexedit2,binwalk and QT. It is cross platform and has plenty of features: * Advanced Find (can find patterns in binary files based on HEX,UTF8,UTF16 and regex) * Binwalk integration * Entropy Analysis * Hash Calculator * Bin/Dec/Hex Converter * Hex file editing * Diff file analysis * Byte Patterns to parse headers It is smart tool especially for reverse engineers
Bug#1059666: python-hug: autopkgtest failure with Python 3.12
Hi Federico, Am Thu, Feb 08, 2024 at 07:02:09PM +0100 schrieb Federico Ceratto: > Sure, go ahead, and thank you for taking care of the bug! Done.[1] Please note: I activated build-time testing and non-trivial autopkgtest. This involved some fixes for Python3.11, Python3.12 as well as numpy. I also marked tests accessing network skip. There were two remaining types of test failures I would like you to pay attention or point upstream to. This is documented in debian/README.source[2]. I have the feeling that also python-marshmallow would reside nicely in DPT but since there is no bug in this package I do not see any reason to act right now. Kind regards Andreas. [1] https://tracker.debian.org/news/1502390/accepted-python-hug-260-3-source-into-unstable/ [2] https://salsa.debian.org/python-team/packages/python-hug/-/blob/master/debian/README.source?ref_type=heads -- http://fam-tille.de
Bug#1063578: forensics-extra: transition from p7zip to 7zip
Source: forensics-extra Version: 2.49 Severity: normal Dear Maintainer, your package Depends/Recommends/Suggests or has some other relation to the p7zip/p7zip-full/p7zip-rar packages, which have become transitional packages in debian trixie and will eventually be removed from debian. They have been replaced by 7zip and 7zip-rar packages. If necessary, please modify your package to use the executables from the 7zip package instead. If everything everything behaves as expected, then remove p7zip/p7zip-full/p7zip-rar from the control file and replace it with 7zip and/or 7zip-rar. This bug is currently filed with normal priority but the priority will be increased as the release date of debian trixie gets closer. Thank you for maintaining software in debian.
Bug#1063577: firmware-carl9170: Should nonfree-firmware exclude 'carl9170fw' dir from linux-firmware?
Package: firmware-carl9170 Version: 1.9.9-399-gcd480b9-1 Severity: minor -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/ has a directory ``carl9170fw`` which is also the source name of this package. When I check this package Homepage I see the following: ``` Firmware binary The firmware can be obtained from firmware tree. ``` And 'firmware tree' is a link to firmware-nonfree's repo (via a redirect). Looking through this package git repo, I found this URL: https://github.com/chunkeey/carl9170fw/ And a casual comparison with the ``carl9170fw`` dir in linux-firmware repo shows a LOT of similarities. But it's not the same. It appears that this package's upstream is a fork of linux-firmware? In any case, I'm confused about the relation between the ``carl9170fw`` dir in linux-firmware and this package. Can you tell me if the ``carl9170fw`` dir should be excluded in firmware-nonfree, just like ``ath9k_htc`` is excluded as it's packaged in ``open-ath9k-htc-firmware``? - -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (101, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.6.13-amd64 (SMP w/16 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled -BEGIN PGP SIGNATURE- iHUEARYIAB0WIQT1sUPBYsyGmi4usy/XblvOeH7bbgUCZcZVTgAKCRDXblvOeH7b bkmaAP99nTma9WFJeFzfFEGpZfTyIf0KmTNxJBX2XkEq0QM7cAD9G9eRc+UG31Hg J9CXEtwGbWnEbEfvUug3waKiwrSpWw4= =1zzV -END PGP SIGNATURE-
Bug#1063576: O: virtualenv-clone -- script for cloning a non-relocatable virtualenv (Python3)
Package: wnpp Severity: normal X-Debbugs-Cc: virtualenv-cl...@packages.debian.org Control: affects -1 + src:virtualenv-clone I intend to orphan the virtualenv-clone package. I packaged virtualenv-clone because it was a dependency of virtualenvwrapper which I no longer use. The package description is: Virtualenv provides a way to make virtualenv's relocatable which could then be copied as wanted. However making a virtualenv relocatable this way breaks the no-site-packages isolation of the virtualenv as well as other aspects that come with relative paths and '/usr/bin/env' shebangs that may be undesirable. . Also, the .pth and .egg-link rewriting doesn't seem to work as intended. This attempts to overcome these issues and provide a way to easily clone an existing virtualenv. . This is the Python3 package.
Bug#1063575: O: virtualenvwrapper -- extension to virtualenv for managing multiple environments
Package: wnpp Severity: normal X-Debbugs-Cc: virtualenvwrap...@packages.debian.org Control: affects -1 + src:virtualenvwrapper I intend to orphan the virtualenvwrapper package. I no longer use virtualenvwrapper, pipenv and poetry are better alternatives for all of my use cases. The package description is: virtualenvwrapper is a set of extensions to Ian Bicking's virtualenv tool. The extensions include wrappers for creating and deleting virtual environments and otherwise managing your development workflow, making it easier to work on more than one project at a time without introducing conflicts in their dependencies.
Bug#1063574: O: sysconftool -- development tool to install and update configuration files
Package: wnpp Severity: normal X-Debbugs-Cc: sysconft...@packages.debian.org Control: affects -1 + src:sysconftool I intend to orphan the sysconftool package. I have no use for the package and it had no uploads for ages. The package description is: sysconftool is a development utility that helps to install application configuration files. sysconftool allows an existing application to be upgraded without losing the older version's configuration settings, but that's the advantage over plain dpkg upgrading, will add new configuration settings (and remove unneeded).
Bug#1063573: flatpak-builder: transition from p7zip to 7zip
Source: flatpak-builder Version: 1.4.0-1 Severity: normal Dear Maintainer, your package Depends/Recommends/Suggests or has some other relation to the p7zip/p7zip-full/p7zip-rar packages, which have become transitional packages in debian trixie and will eventually be removed from debian. They have been replaced by 7zip and 7zip-rar packages. If necessary, please modify your package to use the executables from the 7zip package instead. If everything everything behaves as expected, then remove p7zip/p7zip-full/p7zip-rar from the control file and replace it with 7zip and/or 7zip-rar. This bug is currently filed with normal priority but the priority will be increased as the release date of debian trixie gets closer. Thank you for maintaining software in debian.
Bug#1063338: [regression 6.1.76] dlm: cannot start dlm midcomms -97 after backport of e9cdebbe23f1 ("dlm: use kernel_connect() and kernel_bind()")
I sent this patch out to sta...@vger.kernel.org. Everyone should be CCd. Thanks for your help in confirming the fix works. -Jordan
Bug#1063572: jfsutils: move files to /usr (DEP17)
Package: jfsutils Version: 1.1.15-5 Tags: patch User: helm...@debian.org Usertags: dep17 Hi, we want to finalize the /usr-merge transition by moving all aliased files from / to /usr via DEP17 to avoid any negative effects arising from aliasing. jfsutils is involved because it installs utiles to /sbin. Since it cannot be automatically converted using dh-sequence-movetousr, I'm sending a patch to perform the conversion. This patch should not be uploaded to bookworm-backports or earlier as it would violate the file move moratorium there. Helmut diff --minimal -Nru jfsutils-1.1.15/debian/changelog jfsutils-1.1.15/debian/changelog --- jfsutils-1.1.15/debian/changelog2020-06-23 22:31:15.0 +0200 +++ jfsutils-1.1.15/debian/changelog2024-02-09 17:06:29.0 +0100 @@ -1,3 +1,10 @@ +jfsutils (1.1.15-5.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Move files to /usr for DEP17 (closes: #-1). + + -- Helmut Grohne Fri, 09 Feb 2024 17:06:29 +0100 + jfsutils (1.1.15-5) unstable; urgency=medium * Update Standards-Version to 4.5.0 . diff --minimal -Nru jfsutils-1.1.15/debian/jfsutils-udeb.install jfsutils-1.1.15/debian/jfsutils-udeb.install --- jfsutils-1.1.15/debian/jfsutils-udeb.install2016-11-07 18:39:06.0 +0100 +++ jfsutils-1.1.15/debian/jfsutils-udeb.install2024-02-09 17:06:29.0 +0100 @@ -1 +1 @@ -debian/tmp/sbin \ No newline at end of file +debian/tmp/usr/sbin diff --minimal -Nru jfsutils-1.1.15/debian/jfsutils.install jfsutils-1.1.15/debian/jfsutils.install --- jfsutils-1.1.15/debian/jfsutils.install 2016-11-07 18:39:06.0 +0100 +++ jfsutils-1.1.15/debian/jfsutils.install 2024-02-09 17:06:29.0 +0100 @@ -1 +1 @@ -debian/tmp/sbin +debian/tmp/usr/sbin diff --minimal -Nru jfsutils-1.1.15/debian/rules jfsutils-1.1.15/debian/rules --- jfsutils-1.1.15/debian/rules2016-11-07 18:39:29.0 +0100 +++ jfsutils-1.1.15/debian/rules2024-02-09 17:06:26.0 +0100 @@ -25,5 +25,4 @@ LDFLAGS += -Wl,--no-relax endif -DEB_CONFIGURE_USER_FLAGS := --sbindir=/sbin DEB_MAKE_INSTALL_TARGET := install DESTDIR=$(CURDIR)/debian/tmp
Bug#1063571: libpcre3: move libraries to /usr (DEP17)
Package: libpcre3 Version: 2:8.39-15 Tags: patch User: helm...@debian.org Usertags: dep17m2 Hi, we want to finalize the /usr-merge transition by moving all aliased files from / to /usr via DEP17 to avoid any negative effects arising from aliasing. libpcre3 is involved, because installs a shared library below /lib. I'm sending a patch, because it cannot be automatically converted using dh-sequence-movetousr. Note that this patch must not be uploaded to bookworm-backports or earlier as it would violate the earlier file move moratorium there. Helmut diff --minimal -Nru pcre3-8.39/debian/changelog pcre3-8.39/debian/changelog --- pcre3-8.39/debian/changelog 2022-12-22 17:45:21.0 +0100 +++ pcre3-8.39/debian/changelog 2024-02-09 16:13:23.0 +0100 @@ -1,3 +1,10 @@ +pcre3 (2:8.39-15.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Move library to /usr. (Closes: #-1) + + -- Helmut Grohne Fri, 09 Feb 2024 16:13:23 +0100 + pcre3 (2:8.39-15) unstable; urgency=medium * Make currently-important packages optional as pcre3 is obsolete diff --minimal -Nru pcre3-8.39/debian/dirs pcre3-8.39/debian/dirs --- pcre3-8.39/debian/dirs 2022-12-22 17:45:21.0 +0100 +++ pcre3-8.39/debian/dirs 1970-01-01 01:00:00.0 +0100 @@ -1,2 +0,0 @@ -usr/bin -usr/sbin diff --minimal -Nru pcre3-8.39/debian/rules pcre3-8.39/debian/rules --- pcre3-8.39/debian/rules 2022-12-22 17:45:21.0 +0100 +++ pcre3-8.39/debian/rules 2024-02-09 16:12:49.0 +0100 @@ -93,10 +93,6 @@ dh_install -a # This man page is in the main package, don't want it in -dev rm debian/libpcre3-dev/usr/share/man/man3/pcrepattern.3 - # Move actual library to /lib - mkdir -p debian/libpcre3/lib/$(DEB_HOST_MULTIARCH) - mv debian/libpcre3/usr/lib/$(DEB_HOST_MULTIARCH)/libpcre.so.* debian/libpcre3/lib/$(DEB_HOST_MULTIARCH) - ln -sf /lib/$(DEB_HOST_MULTIARCH)/libpcre.so.3 debian/libpcre3-dev/usr/lib/$(DEB_HOST_MULTIARCH)/libpcre.so # we never need to reference the library path in pcre-config on # Debian, so clip it out so that the script will be multiarch-safe. sed -i -e"s,/$(DEB_HOST_MULTIARCH),,g" debian/libpcre3-dev/usr/bin/pcre-config
Bug#1063570: mbr: move install-mbr to /usr/sbin (DEP17)
Package: mbr Version: 1.2.1 Tags: patch trixie sid User: helm...@debian.org Usertags: dep17m2 Hi, we want to finalize the /usr-merge transition by moving all aliased files from / to /usr via DEP17 to avoid any negative effects arising from aliasing. mbr is involved, because it installs /sbin/install-mbr. I am sending a patch, because it cannot be automatically converted using dh-sequence-movetousr. Note that this patch should not be uploaded to bookworm-backports or earlier, because it would violate the file move moratorium there. Helmut diff --minimal -Nru mbr-1.2.1/debian/changelog mbr-1.2.1+nmu1/debian/changelog --- mbr-1.2.1/debian/changelog 2018-09-25 21:15:56.0 +0200 +++ mbr-1.2.1+nmu1/debian/changelog 2024-02-09 16:51:48.0 +0100 @@ -1,3 +1,10 @@ +mbr (1.2.1+nmu1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Move install-mbr to /usr. (Closes: #-1) + + -- Helmut Grohne Fri, 09 Feb 2024 16:51:48 +0100 + mbr (1.2.1) unstable; urgency=medium * Remove report bug message and version number. Closes: #909563. diff --minimal -Nru mbr-1.2.1/debian/rules mbr-1.2.1+nmu1/debian/rules --- mbr-1.2.1/debian/rules 2018-09-20 10:05:36.0 +0200 +++ mbr-1.2.1+nmu1/debian/rules 2024-02-09 16:51:38.0 +0100 @@ -21,7 +21,7 @@ build-indep: build-stamp build-stamp: - ./configure --exec-prefix=`pwd`/debian/mbr/ --prefix=`pwd`/debian/mbr/usr --build=$(DEB_BUILD_GNU_TYPE) --host=$(DEB_HOST_GNU_TYPE) + ./configure --prefix=`pwd`/debian/mbr/usr --build=$(DEB_BUILD_GNU_TYPE) --host=$(DEB_HOST_GNU_TYPE) $(MAKE) CC="$(CC)" LD="$(LD)" CFLAGS="$(CFLAGS)" touch build @@ -36,12 +36,12 @@ dh_testdir dh_testroot dh_prep - dh_installdirs -p mbr-udeb sbin + dh_installdirs -p mbr-udeb usr/sbin dh_installdocs -p mbr debian/README-1st.Debian NEWS README AUTHORS dh_installchangelogs $(MAKE) install INSTALL_PROGRAM="$(INSTALL_PROGRAM)" ifneq ($(filter mbr-udeb,$(binaries)),) - cp `pwd`/debian/mbr/sbin/install-mbr `pwd`/debian/mbr-udeb/sbin/ + cp `pwd`/debian/mbr/usr/sbin/install-mbr `pwd`/debian/mbr-udeb/usr/sbin/ endif binary-indep: build
Bug#1063569: fsprotect: move files to /usr (DEP17)
Source: fsprotect Version: 1.0.7+nmu1 Tags: patch trixie sid User: helm...@debian.org Usertags: dep17 Hi, we want to finalize the /usr-merge transition by moving all aliased files from / to /usr via DEP17 to avoid any negative effects arising from aliasing. fsprotect is involved for multiple files. I'm sending a patch, because it cannot be converted automatically using dh-sequence-movetousr. Note that this patch should not be uploaded to bookworm-backports or earlier as it would violate the file move moratorium there. Helmut diff --minimal -Nru fsprotect-1.0.7+nmu1/debian/changelog fsprotect-1.0.7+nmu2/debian/changelog --- fsprotect-1.0.7+nmu1/debian/changelog 2022-10-15 12:06:05.0 +0200 +++ fsprotect-1.0.7+nmu2/debian/changelog 2024-02-09 17:13:30.0 +0100 @@ -1,3 +1,10 @@ +fsprotect (1.0.7+nmu2) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Move files to /usr for DEP17. (Closes: #-1) + + -- Helmut Grohne Fri, 09 Feb 2024 17:13:30 +0100 + fsprotect (1.0.7+nmu1) unstable; urgency=medium * Non-maintainer upload. diff --minimal -Nru fsprotect-1.0.7+nmu1/debian/dirs fsprotect-1.0.7+nmu2/debian/dirs --- fsprotect-1.0.7+nmu1/debian/dirs2016-01-10 16:11:37.0 +0100 +++ fsprotect-1.0.7+nmu2/debian/dirs2024-02-09 17:13:07.0 +0100 @@ -1 +1 @@ -/lib/fsprotect +/usr/lib/fsprotect diff --minimal -Nru fsprotect-1.0.7+nmu1/debian/fsprotect.install fsprotect-1.0.7+nmu2/debian/fsprotect.install --- fsprotect-1.0.7+nmu1/debian/fsprotect.install 2016-01-10 16:11:37.0 +0100 +++ fsprotect-1.0.7+nmu2/debian/fsprotect.install 2024-02-09 17:12:50.0 +0100 @@ -1,5 +1,5 @@ initramfs-tools/hooks/fsprotect /usr/share/initramfs-tools/hooks initramfs-tools/scripts/local-bottom/fsprotect /usr/share/initramfs-tools/scripts/local-bottom initramfs-tools/scripts/local-bottom/fsprotect /usr/share/initramfs-tools/scripts/nfs-bottom -bin/is_aufs /bin -lib/fsprotect-protect /lib/fsprotect/ +bin/is_aufs /usr/bin +lib/fsprotect-protect /usr/lib/fsprotect/ diff --minimal -Nru fsprotect-1.0.7+nmu1/debian/rules fsprotect-1.0.7+nmu2/debian/rules --- fsprotect-1.0.7+nmu1/debian/rules 2017-01-01 23:11:45.0 +0100 +++ fsprotect-1.0.7+nmu2/debian/rules 2024-02-09 17:12:30.0 +0100 @@ -10,5 +10,5 @@ dh_installman debian/is_aufs.1 binary-install/fsprotect:: - chmod 755 $(DEB_DESTDIR)/lib/fsprotect/fsprotect-protect + chmod 755 $(DEB_DESTDIR)/usr/lib/fsprotect/fsprotect-protect
Bug#1063321: libwxgtk3.2-1t64 has an undeclared file conflict
On Fri, 9 Feb 2024, Scott Talbert wrote: On Tue, 6 Feb 2024, Helmut Grohne wrote: Package: libwxgtk3.2-1t64 Version: 3.2.4+dfsg-3.1~exp1 Severity: serious User: debian...@lists.debian.org Usertags: fileconflict Control: affects -1 + libwxgtk-gl3.2-1 libwxgtk-gl3.2-1t64 libwxgtk-media3.2-1 libwxgtk-media3.2-1t64 libwxgtk-webview3.2-1 libwxgtk-webview3.2-1t64 X-Debbugs-Cc: vor...@debian.org libwxgtk3.2-1t64 has an undeclared file conflict. This may result in an unpack error from dpkg. Hello Steve, Are you planning on fixing this, or would you like me to? If the latter, how would you like the fix submitted before this is uploaded to unstable? Sending to your vor...@dodds.net as your mail server rejected the mail sent through debian.org with some sort of SPF error. Probably something the debian server is doing? Scott
Bug#1042447: file-roller: transition from p7zip to 7zip
Source: file-roller Version: 43.1-1 Followup-For: Bug #1042447 Dear Maintainer, your package Depends/Recommends/Suggests or has some other relation to the p7zip/p7zip-full/p7zip-rar packages, which have become transitional packages in debian trixie and will eventually be removed from debian. They have been replaced by 7zip and 7zip-rar packages. If necessary, please modify your package to use the executables from the 7zip package instead. If everything everything behaves as expected, then remove p7zip/p7zip-full/p7zip-rar from the control file and replace it with 7zip and/or 7zip-rar. This bug is currently filed with normal priority but the priority will be increased as the release date of debian trixie gets closer. Thank you for maintaining software in debian.
Bug#1063568: puppetserver: Hangs on systems using at least some non-C/English locale with certain 'file' resources
Package: puppetserver Version: 7.9.5-2 Severity: normal Tags: l10n upstream Dear Maintainer(s), after upgrading from puppet-master to puppetserver, we noticed that Puppet runs on certain agents did not terminate anymore and left a Java process on the Puppet server which was using ~100% of one CPU core. After some debugging and a few detours, I noticed that this seems to be ultimately caused by a bug(?) in JRuby (I've reported this to the JRuby upstream at [1] already) which is triggered by Puppet Server when the system locale is set to one of at least some locales other than C/English (via /etc/default/locale) - which is de_CH.UTF-8 in our case. I'm also attaching a small archive with a Puppet module which can be used to trigger this issue - in short, a 'file' resource which recursively copies a structure containing a directory and a symbolic link to this directory results in an open() on the directory followed by a read() in the Puppet Server code which never returns, but apparently loops endlessly somewhere (Puppet Server seems to expect it to throw an exception in this case if I'm interpreting its logic correctly). My solution for this problem was the addition of a 'LANG="C"' line to /etc/default/puppetserver and restarting it to ensure that Puppet Server always runs with a defined locale that doesn't make it trigger the problematic JRuby behavior. Afterwards, the Puppet agent runs terminated again and were successful. I'm not sure if this is the right place to report or fix this issue, but until this gets fixed in JRuby (if it even is fixable with a reasonable amount of effort), applying a workaround in the Debian package's debian/puppetserver.default or debian/puppetserver.service might prevent others from running into the same issue when using the packages from Debian. Cheers, Manfred [1] https://github.com/jruby/jruby/issues/8096 -- System Information: Debian Release: 12.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-17-amd64 (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=de_CH.utf8, LC_CTYPE=de_CH.utf8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: unable to detect Versions of packages puppetserver depends on: ii default-jre-headless 2:1.17-74 ii facter 4.3.0-2 ii hiera3.10.0-1 ii jruby9.3.9.0+ds-8 ii libclj-time-clojure 0.15.2-2 ii libclj-yaml-clojure 0.7.2-1 ii libclojure-java 1.11.1-2 ii libcomidi-clojure0.3.2-2 ii libcommons-exec-java 1.3-2 ii libcommons-io-java 2.11.0-2 ii libcommons-lang-java 2.6-10 ii libdropwizard-metrics-java 3.2.6-1 ii libdujour-version-check-clojure 0.2.3-1 ii libjruby-utils-clojure 4.0.3-4 ii libkitchensink-clojure 3.2.1-1 ii libliberator-clojure 0.15.3-1 ii libprismatic-schema-clojure 1.2.0-4 ii libpuppetlabs-http-client-clojure2.1.1-1 ii libpuppetlabs-i18n-clojure 0.9.2-2 ii libpuppetlabs-ring-middleware-clojure1.3.1-3 ii libraynes-fs-clojure 1.5.2-1 ii libsemver-clojure0.3.0-2 ii libshell-utils-clojure 1.0.2-3 ii libslingshot-clojure 0.12.2-3 ii libssl-utils-clojure 3.5.0-2 ii libtrapperkeeper-authorization-clojure 1.0.0-4 ii libtrapperkeeper-clojure 3.2.0-4 ii libtrapperkeeper-comidi-metrics-clojure 0.1.2-2 ii libtrapperkeeper-filesystem-watcher-clojure 1.2.2-3 ii libtrapperkeeper-metrics-clojure 1.5.0-5 ii libtrapperkeeper-scheduler-clojure 1.1.3-7 ii libtrapperkeeper-status-clojure 1.1.1-4 ii libtrapperkeeper-webserver-jetty9-clojure4.4.1-5 ii libyaml-snake-java 1.33-2 ii puppet-agent 7.23.0-1 ii ruby 1:3.1 ii ruby-deep-merge 1.1.1-2 ii ruby-fast-gettext2.0.3-2 ii ruby-gettext 3.3.3-2 ii ruby-hocon 1.3.1-2 ii ruby-locale 2.1.3-1 ii ruby-puppet-resource-api 1.8.16-2 ii ruby-puppetserver-ca-cli 2.4.0-4 ii ruby-semantic-puppet 1.0.4-1 ii ruby-text1.3.1-1 Versions of packages puppetserver
