Bug#1071861: plakativ: prepare for next python3-fitz version
Quoting Bastian Germann (2024-06-26 19:36:05) > Control: retitle -1 plakativ: autopkgtest fails with python3-fitz 1.24.x > Control: severity -1 serious > > Now the pymupdf version has been updated. Thank you! Unfortunately, with the changes and the new version I now get a segmentation fault in the tests: https://ci.debian.net/packages/p/plakativ/testing/amd64/48338176/ I didn't look into this yet. signature.asc Description: signature
Bug#1074399: marked as done (libcgi-application-plugin-authentication-perl: autopkgtest regression: libcgi-application-plugin-authentication-perl vs libcgi-pm-perl)
Your message dated Fri, 28 Jun 2024 22:21:43 + with message-id and subject line Bug#1074399: fixed in libcgi-application-plugin-authentication-perl 0.24+~cs0.5-2 has caused the Debian Bug report #1074399, regarding libcgi-application-plugin-authentication-perl: autopkgtest regression: libcgi-application-plugin-authentication-perl vs libcgi-pm-perl to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1074399: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074399 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libcgi-application-plugin-authentication-perl Version: 0.24+~cs0.5-1 Severity: serious Tags: patch ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: chris.peter...@canonical.com User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu oracular ubuntu-patch libcgi-application-plugin-authentication-perl's build time tests fail due to a change in behavior in libcgi-pm-perl with trailing slashes in URLs. In particular, a test was failing which compared generated output with a reference output that was generated with an older version of libcgi-pm-perl. I applied the attached patch to fix the issue Ubuntu and also forwarded it upstream. Thanks for considering the patch. - cpete diff -Nru libcgi-application-plugin-authentication-perl-0.24+~cs0.5/debian/patches/login-box-basic.patch libcgi-application-plugin-authentication-perl-0.24+~cs0.5/debian/patches/login-box-basic.patch --- libcgi-application-plugin-authentication-perl-0.24+~cs0.5/debian/patches/login-box-basic.patch 1969-12-31 16:00:00.0 -0800 +++ libcgi-application-plugin-authentication-perl-0.24+~cs0.5/debian/patches/login-box-basic.patch 2024-06-27 16:02:21.0 -0700 @@ -0,0 +1,23 @@ +Description: Update test for CGI.pm >=4.66 + CGI.pm made changes to "restore the trailing slash in ->url" in 4.66[1], + which causes a test failure in one of the tests comparing output with + a reference generated by a previous version of CGI.pm. This patch + updates the reference file for compatibility with CGI.pm >= 4.66. + + [1] https://github.com/leejo/CGI.pm/commit/a5485b5f3b2b1cc85761b6781ff6660b4f377498 +Author: Chris Peterson +Forwarded: https://github.com/MicroTechnology-Services/cgi-application-plugin-authentication/pull/2 +Bug-Ubuntu: https://bugs.launchpad.net/ubuntu/+source/libcgi-application-plugin-authentication-perl/+bug/2071369 +Last-Update: 2024-06-27 +--- +This patch header follows DEP-3: http://dep.debian.net/deps/dep3/ +--- a/t/out/basic_login_box b/t/out/basic_login_box +@@ -28,6 +28,6 @@ + + + +- http://localhost; /> ++ http://localhost/; /> + + diff -Nru libcgi-application-plugin-authentication-perl-0.24+~cs0.5/debian/patches/series libcgi-application-plugin-authentication-perl-0.24+~cs0.5/debian/patches/series --- libcgi-application-plugin-authentication-perl-0.24+~cs0.5/debian/patches/series 1969-12-31 16:00:00.0 -0800 +++ libcgi-application-plugin-authentication-perl-0.24+~cs0.5/debian/patches/series 2024-06-27 11:32:51.0 -0700 @@ -0,0 +1 @@ +login-box-basic.patch --- End Message --- --- Begin Message --- Source: libcgi-application-plugin-authentication-perl Source-Version: 0.24+~cs0.5-2 Done: gregor herrmann We believe that the bug you reported is fixed in the latest version of libcgi-application-plugin-authentication-perl, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1074...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. gregor herrmann (supplier of updated libcgi-application-plugin-authentication-perl package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 29 Jun 2024 00:05:49 +0200 Source: libcgi-application-plugin-authentication-perl Architecture: source Version: 0.24+~cs0.5-2 Distribution: unstable Urgency: medium Maintainer: Debian Perl Group Changed-By: gregor herrmann Closes: 1074399 Changes: libcgi-application-plugin-authentication-perl (0.24+~cs0.5-2) unstable; urgency=medium . * Add patch for CGI.pm >= 4.66 compatibility. Taken from
Bug#1074271: closing 1074271
close 1074271 thanks Rebuilt and re-uploaded for amd64 in version 1.4.3-6
Bug#1074399: marked as pending in libcgi-application-plugin-authentication-perl
Control: tag -1 pending Hello, Bug #1074399 in libcgi-application-plugin-authentication-perl reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/perl-team/modules/packages/libcgi-application-plugin-authentication-perl/-/commit/5d7045429a90a25f3613ce0a566f7a57139e79c0 Add patch for CGI.pm >= 4.66 compatibility. Taken from upstream Git commit. Thanks: Chris Peterson for the bug report. Closes: #1074399 LP: #2071369 (this message was generated automatically) -- Greetings https://bugs.debian.org/1074399
Processed: Bug#1074399 marked as pending in libcgi-application-plugin-authentication-perl
Processing control commands: > tag -1 pending Bug #1074399 [libcgi-application-plugin-authentication-perl] libcgi-application-plugin-authentication-perl: autopkgtest regression: libcgi-application-plugin-authentication-perl vs libcgi-pm-perl Added tag(s) pending. -- 1074399: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074399 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: closing 1074271
Processing commands for cont...@bugs.debian.org: > close 1074271 Bug #1074271 [src:amgcl] amgcl: needs rebuild for Python 3.12 as default Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 1074271: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074271 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: bug 1074399 is forwarded to https://github.com/MicroTechnology-Services/cgi-application-plugin-authentication/pull/2
Processing commands for cont...@bugs.debian.org: > forwarded 1074399 > https://github.com/MicroTechnology-Services/cgi-application-plugin-authentication/pull/2 Bug #1074399 [libcgi-application-plugin-authentication-perl] libcgi-application-plugin-authentication-perl: autopkgtest regression: libcgi-application-plugin-authentication-perl vs libcgi-pm-perl Set Bug forwarded-to-address to 'https://github.com/MicroTechnology-Services/cgi-application-plugin-authentication/pull/2'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1074399: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074399 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1066938: Fwd: Bug#1066938: libfiu: FTBFS on arm{el,hf}: /tmp/cc54dEva.s:726: Error: symbol `open64' is already defined
On Sun, Apr 28, 2024 at 06:50:30PM +0100, Alberto Bertogli wrote: I'm still trying to find a reasonable workaround. I found a workaround to fix the compilation issue, by detecting and not building the 64-bit variants when there is asm aliasing for the relevant functions. However, it is now failing some of the tests, because of some weird API/ABI issue with the size of off_t. The calls to the wrapped function are okay, but then the underlying call to glibc's functions have the wrong argument sizes :( So I'm still trying to figure out to make this work. Alberto
Bug#1074451: librecoll39-dev has an undeclared file conflict on /usr/lib/x86_64-linux-gnu/librecoll.so
Package: librecoll39-dev Version: 1.39.0-1 Severity: serious User: debian...@lists.debian.org Usertags: fileconflict Control: affects -1 + recollcmd librecoll39-dev has an undeclared file conflict. This may result in an unpack error from dpkg. The file /usr/lib/x86_64-linux-gnu/librecoll.so is contained in the packages * librecoll39-dev/1.39.0-1 as present in unstable * recollcmd/1.36.1-1+b2 as present in trixie These packages can be unpacked concurrently, because there is no relevant Replaces or Conflicts relation. Attempting to unpack these packages concurrently results in an unpack error from dpkg, because none of the packages installs a diversion for the affected file. Kind regards The Debian Usr Merge Analysis Tool This bug report has been automatically filed with no human intervention. The source code is available at https://salsa.debian.org/helmutg/dumat. If the filing is unclear or in error, don't hesitate to contact hel...@subdivi.de for assistance.
Processed: librecoll39-dev has an undeclared file conflict on /usr/lib/x86_64-linux-gnu/librecoll.so
Processing control commands: > affects -1 + recollcmd Bug #1074451 [librecoll39-dev] librecoll39-dev has an undeclared file conflict on /usr/lib/x86_64-linux-gnu/librecoll.so Added indication that 1074451 affects recollcmd -- 1074451: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074451 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1074379: marked as done (wireplumber: Bluetooth profile switch crashes wireplumber)
Your message dated Fri, 28 Jun 2024 19:57:55 + with message-id and subject line Bug#1074379: fixed in wireplumber 0.5.5-1 has caused the Debian Bug report #1074379, regarding wireplumber: Bluetooth profile switch crashes wireplumber to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1074379: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074379 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: wireplumber Version: 0.5.4-1 Severity: important Dear Maintainer, today I updated my system, affecting also wireplumber:amd64 (0.5.3-1, 0.5.4-1) and libwireplumber-0.5-0:amd64 (0.5.3-1, 0.5.4-1), leading to not being able to hear or speak to other people in video conferences (google meet on firefox, chromium). I'm running a lenovo ThinkPad T480s normally using a jabra evolve2 65 headset connected via the internel bluetooth device. Poking around I found that without the BT device connected I could use the internal sound device as well as another USB soundbar. In syslog I found the following entries: wireplumber[3124]: spa.bluez5.native: RFCOMM receive command but modem not available: AT+BTRH?#015 wireplumber[3124]: wplua: [string "linking-utils.lua"]:118: bad argument #4 to 'format' (number expected, got nil)#012stack traceback:#012#011[C]: in function 'string.format'#012#011[string "linking-utils.lua"]:118: in global 'setPriorityMediaRoleLink'#012#011[string "linking-utils.lua"]:98: in function 'linking-utils.updatePriorityMed iaRoleLink'#012#011[string "link-target.lua"]:157: in function <[string "link-target.lua"]:25>#012#011[C]: in ? bluetoothd[1004]: profiles/audio/avdtp.c:cancel_request() Discover: Connection timed out (110) kernel: input: Jabra Evolve2 65 (AVRCP) as /devices/virtual/input/input24 gsd-media-keys[3677]: Unable to get default source gsd-media-keys[3677]: Unable to get default source kernel: wireplumber[3124]: segfault at 7f23a60f0128 ip 7f23a86dd681 sp 7fffa0053730 error 4 in libpipewire-module-protocol-native.so[7f23a8 6d2000+27000] kernel: Code: 38 31 ed 48 89 50 08 48 8b 0a 48 89 08 48 89 02 48 8b 10 48 89 42 08 48 39 c3 74 59 0f 1f 44 00 00 48 8b 50 10 48 85 d2 74 16 <48> 8b 52 28 48 85 d2 74 0d 48 8b 78 18 8b 74 24 0c 83 c5 01 ff d2 Thus I downloaded libwireplumber-0.5-0_0.5.3-1_amd64.deb and wireplumber_0.5.3-1_amd64.deb testing and after a reboot also the bluetooth device worked again. If you need any more information, I'll appily try to provide them (might need some help on that ;-)) The USB devices connected are: lsusb Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 0424:2744 Microchip Technology, Inc. (formerly SMSC) Hub Bus 001 Device 003: ID 058f:9540 Alcor Micro Corp. AU9540 Smartcard Reader Bus 001 Device 004: ID 2cb7:0210 Fibocom L830-EB-00 LTE WWAN Modem Bus 001 Device 005: ID 413c:a503 Dell Computer Corp. AC511 Sound Bar Bus 001 Device 006: ID 8087:0a2b Intel Corp. Bluetooth wireless interface Bus 001 Device 008: ID 5986:2113 Bison Electronics Inc. SunplusIT Integrated Camera Bus 001 Device 009: ID 06cb:009a Synaptics, Inc. Metallica MIS Touch Fingerprint Reader Bus 001 Device 011: ID 05ac:1006 Apple, Inc. Hub in Aluminum Keyboard Bus 001 Device 012: ID 05ac:0250 Apple, Inc. Aluminium Keyboard (ISO) Bus 001 Device 013: ID 03f0:674a HP, Inc HP 100 USB Optical Mouse Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 002: ID 0424:5744 Microchip Technology, Inc. (formerly SMSC) Hub Bus 002 Device 003: ID 0bda:0316 Realtek Semiconductor Corp. Card Reader Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub With best wishes Wolfi -- System Information: Debian Release: trixie/sid APT prefers stable-security APT policy: (500, 'stable-security'), (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.0.0-6-amd64 (SMP w/8 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 Versions of packages wireplumber depends on: ii dbus-user-session [default-dbus-session-bus] 1.14.10-4+b1 ii dbus-x11 [dbus-session-bus] 1.14.10-4+b1 ii init-system-helpers 1.66 ii libc6 2.38-13 ii libglib2.0-0t64 2.80.3-1 ii libpipewire-0.3-0t64 1.0.7-1 ii libwireplumber-0.5-0
Bug#1073432: marked as done (unyt: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13)
Your message dated Fri, 28 Jun 2024 19:57:43 +
with message-id
and subject line Bug#1073432: fixed in unyt 3.0.2-2
has caused the Debian Bug report #1073432,
regarding unyt: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i
python{version} -p "3.12 3.11" returned exit code 13
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1073432: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1073432
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: unyt
Version: 3.0.2-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240615 ftbfs-trixie
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules binary
> dh binary --with python3 --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild plugin_pyproject:129: Building wheel for python3.12 with "build"
> module
> I: pybuild base:311: python3.12 -m build --skip-dependency-check
> --no-isolation --wheel --outdir /<>/.pybuild/cpython3_3.12_unyt
> * Building wheel...
> running bdist_wheel
> running build
> running build_py
> creating build
> creating build/lib
> creating build/lib/unyt
> copying unyt/__init__.py -> build/lib/unyt
> copying unyt/unit_registry.py -> build/lib/unyt
> copying unyt/_array_functions.py -> build/lib/unyt
> copying unyt/unit_object.py -> build/lib/unyt
> copying unyt/exceptions.py -> build/lib/unyt
> copying unyt/mpl_interface.py -> build/lib/unyt
> copying unyt/_version.py -> build/lib/unyt
> copying unyt/equivalencies.py -> build/lib/unyt
> copying unyt/testing.py -> build/lib/unyt
> copying unyt/unit_systems.py -> build/lib/unyt
> copying unyt/_parsing.py -> build/lib/unyt
> copying unyt/_unit_lookup_table.py -> build/lib/unyt
> copying unyt/dimensions.py -> build/lib/unyt
> copying unyt/_physical_ratios.py -> build/lib/unyt
> copying unyt/_on_demand_imports.py -> build/lib/unyt
> copying unyt/_deprecation.py -> build/lib/unyt
> copying unyt/unit_symbols.py -> build/lib/unyt
> copying unyt/physical_constants.py -> build/lib/unyt
> copying unyt/dask_array.py -> build/lib/unyt
> copying unyt/array.py -> build/lib/unyt
> copying unyt/_pint_conversions.py -> build/lib/unyt
> creating build/lib/unyt/tests
> copying unyt/tests/test_dask_arrays.py -> build/lib/unyt/tests
> copying unyt/tests/__init__.py -> build/lib/unyt/tests
> copying unyt/tests/test_unyt_testing.py -> build/lib/unyt/tests
> copying unyt/tests/test_unit_systems.py -> build/lib/unyt/tests
> copying unyt/tests/test_array_functions.py -> build/lib/unyt/tests
> copying unyt/tests/test_units.py -> build/lib/unyt/tests
> copying unyt/tests/test_unyt_array.py -> build/lib/unyt/tests
> copying unyt/tests/test_define_unit.py -> build/lib/unyt/tests
> copying unyt/tests/test_no_duplicates.py -> build/lib/unyt/tests
> copying unyt/tests/test_unit_registry.py -> build/lib/unyt/tests
> copying unyt/tests/test_mpl_interface.py -> build/lib/unyt/tests
> creating build/lib/unyt/_mpl_array_converter
> copying unyt/_mpl_array_converter/__init__.py ->
> build/lib/unyt/_mpl_array_converter
> creating build/lib/unyt/tests/data
> copying unyt/tests/data/__init__.py -> build/lib/unyt/tests/data
> running egg_info
> creating unyt.egg-info
> writing unyt.egg-info/PKG-INFO
> writing dependency_links to unyt.egg-info/dependency_links.txt
> writing requirements to unyt.egg-info/requires.txt
> writing top-level names to unyt.egg-info/top_level.txt
> writing manifest file 'unyt.egg-info/SOURCES.txt'
> reading manifest file 'unyt.egg-info/SOURCES.txt'
> reading manifest template 'MANIFEST.in'
> warning: no previously-included files matching '__pycache__' found under
> directory '*'
> warning: no previously-included files matching '*.py[co]' found under
> directory '*'
> warning: no files found matching '*.jpg' under directory 'docs'
> warning: no files found matching '*.gif' under directory 'docs'
> adding license file 'LICENSE'
> writing manifest file 'unyt.egg-info/SOURCES.txt'
> copying unyt/tests/data/old_json_registry.txt -> build/lib/unyt/tests/data
> copying unyt/tests/data/unyt_array_sympy1.8.pickle ->
> build/lib/unyt/tests/data
> installing to build/bdist.linux-x86_64/wheel
> running install
> running install_lib
> creating build/bdist.linux-x86_64
> creating build/bdist.linux-x86_64/wheel
> creating build/bdist.linux-x86_64/wheel/unyt
> copying
Processed: tagging 1074431, tagging 1074430, tagging 1074429, tagging 1074426 ..., tagging 1074425 ...
Processing commands for cont...@bugs.debian.org: > tags 1074431 + upstream Bug #1074431 [src:arm-trusted-firmware] arm-trusted-firmware: CVE-2024-6287 CVE-2024-6285 Added tag(s) upstream. > tags 1074430 + upstream Bug #1074430 [src:adminer] adminer: CVE-2023-45196 CVE-2023-45195 Added tag(s) upstream. > tags 1074429 + upstream Bug #1074429 [src:xml-security-c] xml-security-c: CVE-2024-34580 Added tag(s) upstream. > tags 1074426 + upstream Bug #1074426 [src:golang-golang-x-image] golang-golang-x-image: CVE-2024-24792 Ignoring request to alter tags of bug #1074426 to the same tags previously set > forwarded 1074426 https://github.com/golang/go/issues/67624 Bug #1074426 [src:golang-golang-x-image] golang-golang-x-image: CVE-2024-24792 Ignoring request to change the forwarded-to-address of bug#1074426 to the same value > tags 1074425 + upstream Bug #1074425 [src:openvpn-auth-ldap] openvpn-auth-ldap: CVE-2024-28820 Ignoring request to alter tags of bug #1074425 to the same tags previously set > forwarded 1074425 https://github.com/threerings/openvpn-auth-ldap/pull/92 Bug #1074425 [src:openvpn-auth-ldap] openvpn-auth-ldap: CVE-2024-28820 Ignoring request to change the forwarded-to-address of bug#1074425 to the same value > tags 1074414 + upstream Bug #1074414 [src:gpac] gpac: CVE-2024-6061 CVE-2024-6062 CVE-2024-6063 CVE-2024-6064 Added tag(s) upstream. > tags 1074415 + upstream Bug #1074415 [src:slic3r-prusa] slic3r-prusa: CVE-2020-28594 CVE-2020-28595 CVE-2020-28596 CVE-2020-28598 Added tag(s) upstream. > tags 1074416 + upstream Bug #1074416 [src:libde265] libde265: CVE-2024-38949 CVE-2024-38950 Added tag(s) upstream. > forwarded 1074416 https://github.com/strukturag/libde265/issues/460 Bug #1074416 [src:libde265] libde265: CVE-2024-38949 CVE-2024-38950 Set Bug forwarded-to-address to 'https://github.com/strukturag/libde265/issues/460'. > tags 1074417 + upstream Bug #1074417 [src:zziplib] zziplib: CVE-2024-39133 Ignoring request to alter tags of bug #1074417 to the same tags previously set > forwarded 1074417 https://github.com/gdraheim/zziplib/issues/164 Bug #1074417 [src:zziplib] zziplib: CVE-2024-39133 Ignoring request to change the forwarded-to-address of bug#1074417 to the same value > tags 1074418 + upstream Bug #1074418 [src:libmodbus] libmodbus: CVE-2023-26793 Added tag(s) upstream. > forwarded 1074418 https://github.com/stephane/libmodbus/issues/683 Bug #1074418 [src:libmodbus] libmodbus: CVE-2023-26793 Set Bug forwarded-to-address to 'https://github.com/stephane/libmodbus/issues/683'. > tags 1074419 + upstream Bug #1074419 [src:bluez] bluez: CVE-2023-51596 Added tag(s) upstream. > tags 1074421 + upstream Bug #1074421 [src:grpc] grpc: CVE-2023-44487 Added tag(s) upstream. > tags 1074422 + upstream Bug #1074422 [src:libmodbus] libmodbus: CVE-2024-36843 CVE-2024-36844 CVE-2024-36845 Added tag(s) upstream. > tags 1074423 + upstream Bug #1074423 [src:nltk] nltk: CVE-2024-39705 Ignoring request to alter tags of bug #1074423 to the same tags previously set > tags 1074424 + upstream Bug #1074424 [src:zziplib] zziplib: CVE-2024-39134 Ignoring request to alter tags of bug #1074424 to the same tags previously set > forwarded 1074424 https://github.com/gdraheim/zziplib/issues/165 Bug #1074424 [src:zziplib] zziplib: CVE-2024-39134 Ignoring request to change the forwarded-to-address of bug#1074424 to the same value > thanks Stopping processing here. Please contact me if you need assistance. -- 1074414: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074414 1074415: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074415 1074416: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074416 1074417: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074417 1074418: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074418 1074419: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074419 1074421: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074421 1074422: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074422 1074423: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074423 1074424: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074424 1074425: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074425 1074426: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074426 1074429: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074429 1074430: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074430 1074431: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074431 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#1073432 marked as pending in unyt
Processing control commands:
> tag -1 pending
Bug #1073432 [src:unyt] unyt: FTBFS: dh_auto_test: error: pybuild --test
--test-pytest -i python{version} -p "3.12 3.11" returned exit code 13
Added tag(s) pending.
--
1073432: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1073432
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1073432: marked as pending in unyt
Control: tag -1 pending Hello, Bug #1073432 in unyt reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/python-team/packages/unyt/-/commit/18123880f1fd8098ace0d72104528fba17439d8e Mark test as failing in later Sympy versions Closes: #1073432 (this message was generated automatically) -- Greetings https://bugs.debian.org/1073432
Bug#1073128: marked as done (clamav: unaligned access on armhf architecture)
Your message dated Fri, 28 Jun 2024 18:50:10 + with message-id and subject line Bug#1073128: fixed in clamav 1.3.1+dfsg-4 has caused the Debian Bug report #1073128, regarding clamav: unaligned access on armhf architecture to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1073128: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1073128 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: clamav Version: 1.3.1+dfsg-3 Severity: serious tags: patch Hello, in Ubuntu, where the kernel is configured to forbid unaligned accesses on armhf, the package FTBFS (this should be reproducible also on some Debian buildd machines, this is why I'm reporting as serious severity) example of failure: https://launchpadlibrarian.net/734963041/buildlog_ubuntu-oracular-armhf.clamav_1.3.1+dfsg-3ubuntu1_BUILDING.txt.gz 3: clamscan/fp_check_test.py::TC::test_fp_for_normalized PASSED [ 52%] 5: freshclam_test.py::TC::test_freshclam_08_cdiff_update_twice PASSED [100%] 5: 5: === warnings summary === 5: freshclam_test.py:20 5: /<>/unit_tests/freshclam_test.py:20: DeprecationWarning: 'cgi' is deprecated and slated for removal in Python 3.13 5: import cgi 5: 5: -- Docs: https://docs.pytest.org/en/stable/how-to/capture-warnings.html 5: == 10 passed, 1 skipped, 1 warning in 49.40s === 3: clamscan/fp_check_test.py::TC::test_fp_for_normalized_wild PASSED[ 54%] 4: clamd_test.py::TC::test_clamd_08_VirusEvent PASSED [ 69%] 3: clamscan/fp_check_test.py::TC::test_fp_for_zipped_file PASSED[ 56%] 3: clamscan/fp_check_test.py::TC::test_fp_for_zipped_file_wild PASSED [ 58%] 2/6 Test #5: freshclam Passed 51.50 sec test 6 Start 6: sigtool 6: Test command: /usr/bin/pytest "-v" "sigtool_test.py" 6: Working Directory: /<>/unit_tests 6: Environment variables: 6: PYTHONTRACEMALLOC=1 6: VERSION=1.3.1 6: SOURCE=/<> 6: BUILD=/<>/obj-arm-linux-gnueabihf 6: TMP=/<>/obj-arm-linux-gnueabihf/unit_tests 6: CK_FORK=no 6: CK_DEFAULT_TIMEOUT=300 6: LD_LIBRARY_PATH=/<>/obj-arm-linux-gnueabihf/libfreshclam:/<>/obj-arm-linux-gnueabihf/libclamav:/usr/lib/arm-linux-gnueabihf: 6: DYLD_LIBRARY_PATH=/<>/obj-arm-linux-gnueabihf/libfreshclam:/<>/obj-arm-linux-gnueabihf/libclamav:/usr/lib/arm-linux-gnueabihf: 6: PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games 6: LIBSSL=/usr/lib/arm-linux-gnueabihf/libssl.so 6: LIBCRYPTO=/usr/lib/arm-linux-gnueabihf/libcrypto.so 6: LIBZ=/usr/lib/arm-linux-gnueabihf/libz.so 6: LIBBZ2=/usr/lib/arm-linux-gnueabihf/libbz2.so 6: LIBPCRE2=/usr/lib/arm-linux-gnueabihf/libpcre2-8.so 6: LIBXML2=/usr/lib/arm-linux-gnueabihf/libxml2.so 6: LIBCURL=/usr/lib/arm-linux-gnueabihf/libcurl.so 6: LIBJSONC=/usr/lib/arm-linux-gnueabihf/libjson-c.so 6: LIBICONV= 6: LLVM_LIBS= 6: LLVM_DIRS= 6: LIBPTHREADW32= 6: LIBWIN32COMPAT= 6: LIBCLAMAV=/<>/obj-arm-linux-gnueabihf/libclamav/libclamav.so.12.0.2 6: LIBCLAMMSPACK=/usr/lib/arm-linux-gnueabihf/libmspack.so 6: LIBCLAMUNRARIFACE= 6: LIBCLAMUNRAR= 6: CHECK_CLAMAV=/<>/obj-arm-linux-gnueabihf/unit_tests/check_clamav 6: CHECK_CLAMD=/<>/obj-arm-linux-gnueabihf/unit_tests/check_clamd 6: CHECK_FPU_ENDIAN=/<>/obj-arm-linux-gnueabihf/unit_tests/check_fpu_endian 6: CLAMBC=/<>/obj-arm-linux-gnueabihf/clambc/clambc 6: CLAMD=/<>/obj-arm-linux-gnueabihf/clamd/clamd 6: CLAMDSCAN=/<>/obj-arm-linux-gnueabihf/clamdscan/clamdscan 6: CLAMDTOP=/<>/obj-arm-linux-gnueabihf/clamdtop/clamdtop 6: CLAMSCAN=/<>/obj-arm-linux-gnueabihf/clamscan/clamscan 6: CLAMSUBMIT=/<>/obj-arm-linux-gnueabihf/clamsubmit/clamsubmit 6: CLAMCONF=/<>/obj-arm-linux-gnueabihf/clamconf/clamconf 6: FRESHCLAM=/<>/obj-arm-linux-gnueabihf/freshclam/freshclam 6: SIGTOOL=/<>/obj-arm-linux-gnueabihf/sigtool/sigtool 6: CLAMAV_MILTER=/<>/obj-arm-linux-gnueabihf/clamav-milter/clamav-milter 6: CLAMONACC=/<>/obj-arm-linux-gnueabihf/clamonacc/clamonacc 6: Test timeout computed to be: 1500 3: clamscan/fuzzy_img_hash_test.py::TC::test_sigs_bad_algorithm PASSED [ 60%] 3: clamscan/fuzzy_img_hash_test.py::TC::test_sigs_bad_hamming PASSED[ 62%] 3: clamscan/fuzzy_img_hash_test.py::TC::test_sigs_bad_hash PASSED [ 64%] 3: clamscan/fuzzy_img_hash_test.py::TC::test_sigs_good_allmatch PASSED [ 66%] 4: clamd_test.py::TC::test_clamd_09_clamdscan_ExcludePath PASSED[ 76%] 6: = test session starts
Bug#1074351: rust-curve25519-dalek: RUSTSEC-2024-0344
Hi Jonas, On Thu, Jun 27, 2024 at 10:52:47PM +0200, Jonas Smedegaard wrote: > Quoting Salvatore Bonaccorso (2024-06-27 08:03:39) > > There is RUSTSEC-2024-0344 provided for rust-curve25519-dalek, can you > > have a look for unstable? > > > > https://rustsec.org/advisories/RUSTSEC-2024-0344.html > > https://github.com/dalek-cryptography/curve25519-dalek/pull/659 > > Certainly - it is on its way now... Thanks for dealing with it! Regards, Salvatore
Bug#1074448: corrosion: fails to build with rustc >= 1.79
Source: corrosion
Version: 0.4.7-1
Severity: serious
Tags: ftbfs upstream patch
Justification: fails to build from source (but built successfully in the past)
hi!
rustc in version 1.79 and later doesn't allow dashes in lib names
anymore. corrosion's test cases executed as part of the build and later,
during autopkgtest, use such a now forbidden library name. the build and
autopkgtest run thus fail, which currently prevents rustc 1.79 from migrating
to testing (which is fine, and good that the test caught it :)).
upstream fixed this as part of 0.5:
https://github.com/corrosion-rs/corrosion/issues/501
with:
https://github.com/corrosion-rs/corrosion/commit/f85b2422d39fb2f7daca33aa6c2ee7647e9f9348
the linked commit applies cleanly to 0.4.7-1, so either cherry-picking
it or updating to 0.5 would be appreciated (ideally before end of July,
when I'll likely upload 1.80).
there seems to be one other issue related to cbindgen (and probably
related commits upstream):
> 4/69 Test #22: cbindgen_rust2cpp_build
> ..***Failed2.42 sec
> CMake Warning:
> Ignoring empty string ("") provided on the command line.
>
>
> CMake Warning:
> Ignoring empty string ("") provided on the command line.
>
>
> CMake Warning:
> Ignoring empty string ("") provided on the command line.
>
>
> CMake Warning:
> Ignoring empty string ("") provided on the command line.
>
>
> CMake Warning:
> Ignoring empty string ("") provided on the command line.
>
>
> -- TEST_BINARY_DIRECTORY:
> /<>/obj-x86_64-linux-gnu/test/cbindgen/build-cbindgen_rust2cpp
> '/usr/bin/cmake' '-GUnix Makefiles' '-DRust_TOOLCHAIN=' '--log-level' 'Debug'
> '-DRust_CARGO_TARGET=x86_64-unknown-linux-gnu'
> '-DCMAKE_C_COMPILER=/usr/bin/cc' '-S'
> '/<>/test/cbindgen/rust2cpp' '-B'
> '/<>/obj-x86_64-linux-gnu/test/cbindgen/build-cbindgen_rust2cpp'
> -- The C compiler identification is GNU 13.3.0
> -- The CXX compiler identification is GNU 13.3.0
> -- Detecting C compiler ABI info
> -- Detecting C compiler ABI info - done
> -- Check for working C compiler: /usr/bin/cc - skipped
> -- Detecting C compile features
> -- Detecting C compile features - done
> -- Detecting CXX compiler ABI info
> -- Detecting CXX compiler ABI info - done
> -- Check for working CXX compiler: /usr/bin/c++ - skipped
> -- Detecting CXX compile features
> -- Detecting CXX compile features - done
> -- Using Corrosion 0.4.7 with CMake 3.29.6 and the `Unix Makefiles` Generator
> CMake Warning at /<>/cmake/FindRust.cmake:197 (message):
> CMake variable `Rust_TOOLCHAIN` specified, but `rustup` was not found.
> Ignoring toolchain and looking for a Rust toolchain not managed by rustup.
> Call Stack (most recent call first):
> /<>/cmake/Corrosion.cmake:63 (find_package)
> /<>/CMakeLists.txt:73 (include)
>
>
> -- Parsed Target triple: arch: x86_64, vendor: unknown, OS: linux, env: gnu
> -- Parsed Target triple: arch: x86_64, vendor: unknown, OS: linux, env: gnu
> -- Determining required link libraries for target x86_64-unknown-linux-gnu
> -- Required static libs for target x86_64-unknown-linux-gnu:
> gcc_s;util;rt;pthread;m;dl;c
> -- Found Rust: /usr/bin/rustc (found version "1.79.0")
> -- Using Corrosion as a subdirectory
> -- Found 1 targets in package rust-lib
> -- TARGET rust_lib produces byproducts librust_lib.a;;
> -- Corrosion created the following CMake targets: rust_lib
> -- rust target is rust_lib
> -- Output directory property (target rust_lib): ARCHIVE_OUTPUT_DIRECTORY dir:
> output_directory-NOTFOUND
> -- Setting IMPORTED_LOCATION for target rust_lib-static to
> `/<>/obj-x86_64-linux-gnu/test/cbindgen/build-cbindgen_rust2cpp/librust_lib.a`.
> -- Adding command to copy byproducts `librust_lib.a` to
> /<>/obj-x86_64-linux-gnu/test/cbindgen/build-cbindgen_rust2cpp/librust_lib.a
> -- Configuring done (0.8s)
> -- Generating done (0.0s)
> -- Build files have been written to:
> /<>/obj-x86_64-linux-gnu/test/cbindgen/build-cbindgen_rust2cpp
> '/usr/bin/cmake' '--build'
> '/<>/obj-x86_64-linux-gnu/test/cbindgen/build-cbindgen_rust2cpp'
> gmake[2]: Entering directory
> '/<>/obj-x86_64-linux-gnu/test/cbindgen/build-cbindgen_rust2cpp'
> gmake[2]: warning: jobserver unavailable: using -j1. Add '+' to parent make
> rule.
> gmake[3]: Entering directory
> '/<>/obj-x86_64-linux-gnu/test/cbindgen/build-cbindgen_rust2cpp'
> gmake[4]: Entering directory
> '/<>/obj-x86_64-linux-gnu/test/cbindgen/build-cbindgen_rust2cpp'
> gmake[4]: Leaving directory
> '/<>/obj-x86_64-linux-gnu/test/cbindgen/build-cbindgen_rust2cpp'
> [ 0%] Built target cargo-prebuild_rust_lib
> gmake[4]: Entering directory
> '/<>/obj-x86_64-linux-gnu/test/cbindgen/build-cbindgen_rust2cpp'
> gmake[4]: Leaving directory
> '/<>/obj-x86_64-linux-gnu/test/cbindgen/build-cbindgen_rust2cpp'
> gmake[4]: Entering directory
> '/<>/obj-x86_64-linux-gnu/test/cbindgen/build-cbindgen_rust2cpp'
>Compiling rust-lib v0.1.0 (/<>/test/cbindgen/rust2cpp/rust)
> Finished `dev`
Bug#1071338: marked as done (python-numpysane: FTBFS: test/testlib_pywrap_GENERATED.c:24:10: fatal error: numpy/arrayobject.h: No such file or directory)
Your message dated Fri, 28 Jun 2024 18:37:02 + with message-id and subject line Bug#1071338: fixed in python-numpysane 0.41-5 has caused the Debian Bug report #1071338, regarding python-numpysane: FTBFS: test/testlib_pywrap_GENERATED.c:24:10: fatal error: numpy/arrayobject.h: No such file or directory to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1071338: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071338 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:python-numpysane Version: 0.40-3 Severity: serious Tags: ftbfs Dear maintainer: During a rebuild of all packages in unstable, your package failed to build: [...] debian/rules build dh build --with python3 --buildsystem=pybuild dh_update_autotools_config -O--buildsystem=pybuild dh_autoreconf -O--buildsystem=pybuild dh_auto_configure -O--buildsystem=pybuild I: pybuild base:311: python3.12 setup.py config WARNING: '.' not a valid package name; please use only .-separated package names in setup.py running config I: pybuild base:311: python3.11 setup.py config WARNING: '.' not a valid package name; please use only .-separated package names in setup.py running config debian/rules override_dh_auto_build make[1]: Entering directory '/<>' make README README-pywrap make[2]: Entering directory '/<>' python3 extract_README.py numpysane README.org README README.footer.org python3 extract_README.py numpysane_pywrap README-pywrap.org README-pywrap README.footer.org make[2]: Leaving directory '/<>' dh_auto_build I: pybuild base:311: /usr/bin/python3.12 setup.py build WARNING: '.' not a valid package name; please use only .-separated package names in setup.py running build running build_py copying numpysane.py -> /<>/.pybuild/cpython3_3.12_numpysane/build copying numpysane_pywrap.py -> /<>/.pybuild/cpython3_3.12_numpysane/build copying extract_README.py -> /<>/.pybuild/cpython3_3.12_numpysane/build creating /<>/.pybuild/cpython3_3.12_numpysane/build/pywrap-templates copying pywrap-templates/pywrap_module_footer_generic.c -> /<>/.pybuild/cpython3_3.12_numpysane/build/pywrap-templates copying pywrap-templates/pywrap_function_generic.c -> /<>/.pybuild/cpython3_3.12_numpysane/build/pywrap-templates copying pywrap-templates/pywrap_module_header.c -> /<>/.pybuild/cpython3_3.12_numpysane/build/pywrap-templates I: pybuild base:311: /usr/bin/python3 setup.py build WARNING: '.' not a valid package name; please use only .-separated package names in setup.py running build running build_py copying numpysane.py -> /<>/.pybuild/cpython3_3.11_numpysane/build copying numpysane_pywrap.py -> /<>/.pybuild/cpython3_3.11_numpysane/build copying extract_README.py -> /<>/.pybuild/cpython3_3.11_numpysane/build creating /<>/.pybuild/cpython3_3.11_numpysane/build/pywrap-templates copying pywrap-templates/pywrap_module_footer_generic.c -> /<>/.pybuild/cpython3_3.11_numpysane/build/pywrap-templates copying pywrap-templates/pywrap_function_generic.c -> /<>/.pybuild/cpython3_3.11_numpysane/build/pywrap-templates copying pywrap-templates/pywrap_module_header.c -> /<>/.pybuild/cpython3_3.11_numpysane/build/pywrap-templates make[1]: Leaving directory '/<>' debian/rules override_dh_auto_test make[1]: Entering directory '/<>' make test3 make[2]: Entering directory '/<>' ./test/genpywrap.py > test/testlib_pywrap_GENERATED.c cc -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -g -Wno-missing-field-initializers -Wsign-compare -DNDEBUG -g -fwrapv -Wall -g -Werror=implicit-function-declaration -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -fPIC -I/usr/include/python3.11 -Wno-cast-function-type -Wdate-time -D_FORTIFY_SOURCE=2 -c -o test/testlib_pywrap_GENERATED.o test/testlib_pywrap_GENERATED.c test/testlib_pywrap_GENERATED.c:24:10: fatal error: numpy/arrayobject.h: No such file or directory 24 | #include | ^ compilation terminated. make[2]: *** [: test/testlib_pywrap_GENERATED.o] Error 1 make[2]: Leaving directory '/<>' make[1]: *** [debian/rules:22: override_dh_auto_test] Error 2 make[1]: Leaving directory '/<>' make: *** [debian/rules:6: build] Error 2 dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2 The above is just how
Bug#1064495: marked as done (sitecopy FTBFS: incompatible neon version)
Your message dated Fri, 28 Jun 2024 18:37:51 + with message-id and subject line Bug#1064495: fixed in sitecopy 1:0.16.6-13 has caused the Debian Bug report #1064495, regarding sitecopy FTBFS: incompatible neon version to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1064495: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064495 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: sitecopy Version: 1:0.16.6-11 Severity: serious Tags: ftbfs sitecopy fails to build from source in unstable. I think the relevant part of the build log is: | checking for neon-config... /usr/bin/neon-config | checking linking against neon... yes | configure: incompatible neon library version 0.33.0: wanted 0.24 25 26 27 28 31 32 | configure: error: could not use external neon library | tail -v -n \+0 config.log Apparently, sitecopy is incompatible with neon >= 0.33. This quite definitely needs a sourceful upload of sitecopy. Helmut --- End Message --- --- Begin Message --- Source: sitecopy Source-Version: 1:0.16.6-13 Done: Petter Reinholdtsen We believe that the bug you reported is fixed in the latest version of sitecopy, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1064...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Petter Reinholdtsen (supplier of updated sitecopy package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 28 Jun 2024 20:12:44 +0200 Source: sitecopy Architecture: source Version: 1:0.16.6-13 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Petter Reinholdtsen Closes: 1064495 Changes: sitecopy (1:0.16.6-13) unstable; urgency=medium . * QA upload. . * Updated 31_Fix-various-issues.diff to work with neon >= 0.33 (Closes: #1064495). Checksums-Sha1: 6fe175471f77a7f58f33233f3ea1674b3e8ee42a 1906 sitecopy_0.16.6-13.dsc 8870a8eb2953cf7b67c8ff5dbf7a0928471b394e 36788 sitecopy_0.16.6-13.debian.tar.xz b7e8e19881de87477905ad01ec28d40bba26fb2d 7488 sitecopy_0.16.6-13_source.buildinfo Checksums-Sha256: 16aa7f7dd2b90d7340879e5a3f4872ed37d9dbc788baf05a90d4b04dfd228f13 1906 sitecopy_0.16.6-13.dsc ad7e0264980624cf43c8bde55f91166aff3aa2ad07f907eea86760208104dba4 36788 sitecopy_0.16.6-13.debian.tar.xz 6b5d616c1bfede5254c6545e26455fc67cba6ff402d5320702ac74a32ecdbbfc 7488 sitecopy_0.16.6-13_source.buildinfo Files: 48288d534db5ddfc5e5f74c6a64cd4cd 1906 web optional sitecopy_0.16.6-13.dsc 207b5b115faa73c7400bfaa2eebbb705 36788 web optional sitecopy_0.16.6-13.debian.tar.xz eaa4df697891ec694653c40485352001 7488 web optional sitecopy_0.16.6-13_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEERqLf4owIeylOb9kkgSgKoIe6+w4FAmZ+/acACgkQgSgKoIe6 +w46ERAAvQ2CAoI+1D8NLvT/VFActbfM84OgsXtKwi8WhQFc0ozLT0fjb5riiy8z NSWUF9OeYl92ugEJuha2rG2R10Z3S0qwHQ5P5qXtv1iYw5y5ZlU4/6UWmYpaUuPT 2SW6TyxELRfuRx0vSlYW8agbDQSL1VasdawyvOs/TlfsHAspdNV/6azloHkf3sFj dkjzDf+POKbYn/NJwuJkGQAU/AnTCrFZFpJQMdIXAZKXMH7vE8p90pzOhRDGY4tI kfQoVy4TejFZznD8J4FyUDHjHhOAiF3ZJD71rcp226IY2xVHjxjFx0/2iHc9/MZX zxiF1FzsSdLhOWNvg6vme+S1QUZbjRnGwNQJVKYJg06RHJusMM1mIpdMveQmlk4E fUenxfighpfFildAqMrYk+RSkzbAdfQz9cJU1js2b8/lZ0eaEgQO70qQ3j6eVn4G na+2/WwkWkM7/Hd4F9HQ+a7oPsiUxgFe/owXDmKjSdQ2XYUC4hx2SLcFsqhtnuGt igMMRwRGeiKHMUhNbswihzYs/Zr9WFD8OaZP0+2S9shHUp7hZs12otU/ntiLA/Ux NTMWq30QZUunKF7HTxd/fuTUnL55AQdE8F9wZyzQZLJZsxbo3KhV2Aisb/iSdhCy IDku8PCFVJXdZUJqDJDC08lP+d+PWH9F/QdIhyYb1QcIZGA0Wx8= =UpC/ -END PGP SIGNATURE- pgpnn3EFA2tkp.pgp Description: PGP signature --- End Message ---
Processed: Re: sitecopy FTBFS: incompatible neon version
Processing control commands: > tags -1 + patch Bug #1064495 [src:sitecopy] sitecopy FTBFS: incompatible neon version Added tag(s) patch. -- 1064495: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064495 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1064495: sitecopy FTBFS: incompatible neon version
Control: tags -1 + patch [Helmut Grohne] > Apparently, sitecopy is incompatible with neon >= 0.33. This quite > definitely needs a sourceful upload of sitecopy. This seem to be the fix, already applied several times for new versions already: diff --git a/debian/patches/31_Fix-various-issues.diff b/debian/patches/31_Fix-various-issues.diff index 30cddf9..55932a2 100644 --- a/debian/patches/31_Fix-various-issues.diff +++ b/debian/patches/31_Fix-various-issues.diff @@ -849,8 +849,8 @@ -# Support neon 0.24 through 0.30 -NE_REQUIRE_VERSIONS([0], [24 25 26 27 28 29 30]) -+# Support neon 0.24 through 0.31 -+NE_REQUIRE_VERSIONS([0], [24 25 26 27 28 31 32]) ++# Support neon 0.24 through 0.33 ++NE_REQUIRE_VERSIONS([0], [24 25 26 27 28 31 32 33]) dnl But we don't use zlib or ACL support NEON_WITHOUT_ZLIB -- Happy hacking Petter Reinholdtsen
Bug#1069403: marked as done (halide: FTBFS on arm64: E: Build killed with signal TERM after 150 minutes of inactivity)
Your message dated Fri, 28 Jun 2024 18:00:11 + with message-id and subject line Bug#1069403: fixed in halide 17.0.2-1 has caused the Debian Bug report #1069403, regarding halide: FTBFS on arm64: E: Build killed with signal TERM after 150 minutes of inactivity to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1069403: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069403 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: halide Version: 17.0.1-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-arm64 Hi, During a rebuild of all packages in sid, your package failed to build on arm64. Relevant part (hopefully): > Start 405: correctness_parallel_reductions > 46/84 Test #405: correctness_parallel_reductions .. > Passed0.67 sec > Start 406: correctness_parallel_rvar > 47/84 Test #406: correctness_parallel_rvar > Passed0.64 sec > Start 407: correctness_parallel_scatter > 48/84 Test #407: correctness_parallel_scatter . > Passed0.69 sec > Start 408: correctness_random > 49/84 Test #408: correctness_random ... > Passed1.42 sec > Start 409: correctness_reorder_rvars > 50/84 Test #409: correctness_reorder_rvars > Passed0.69 sec > Start 410: correctness_rfactor > 51/84 Test #410: correctness_rfactor .. > Passed5.56 sec > Start 411: correctness_stream_compaction > 52/84 Test #411: correctness_stream_compaction > Passed0.61 sec > Start 412: correctness_thread_safety > E: Build killed with signal TERM after 150 minutes of inactivity The full build log is available from: http://qa-logs.debian.net/2024/04/20/halide_17.0.1-1_unstable-arm64.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240420;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240420=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Source: halide Source-Version: 17.0.2-1 Done: Roman Lebedev We believe that the bug you reported is fixed in the latest version of halide, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1069...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Roman Lebedev (supplier of updated halide package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 26 Jun 2024 04:33:35 +0300 Source: halide Binary: halide17-api-doc libhalide17-2 libhalide17-2-dbgsym libhalide17-dev libhalide17-dev-dbgsym libhalide17-doc libhalideaot17-2 python3-halide python3-halide-doc Architecture: source all amd64 Version: 17.0.2-1 Distribution: unstable Urgency: medium Maintainer: Roman Lebedev Changed-By: Roman Lebedev Description: halide17-api-doc - fast, portable computation on images and tensors (Doxygen documen libhalide17-2 - fast, portable computation on images and tensors libhalide17-dev - fast, portable computation on images and tensors -- Development f libhalide17-doc - fast, portable computation on images and tensors (C++ documentati libhalideaot17-2 - fast, portable computation on images and tensors (virtual library python3-halide - fast, portable computation on images and tensors -- Python3 bindi python3-halide-doc - fast, portable computation on images and tensors (Python3 documen Closes: 1066057 1068138 1069403 Changes: halide (17.0.2-1) unstable; urgency=medium .
Bug#1068138: marked as done (halide: FTBFS on amd64: 676 - python_correctness_atomics (Failed))
Your message dated Fri, 28 Jun 2024 18:00:11 + with message-id and subject line Bug#1068138: fixed in halide 17.0.2-1 has caused the Debian Bug report #1068138, regarding halide: FTBFS on amd64: 676 - python_correctness_atomics (Failed) to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1068138: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068138 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: halide Version: 17.0.1-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org https://buildd.debian.org/status/fetch.php?pkg=halide=amd64=17.0.1-1%2Bb2=1711572233=0 The following tests FAILED: 676 - python_correctness_atomics (Failed) 677 - python_correctness_autodiff (Failed) Errors while running CTest make[2]: *** [debian/rules:118: perform_stage_build] Error 8 Cheers -- Sebastian Ramacher --- End Message --- --- Begin Message --- Source: halide Source-Version: 17.0.2-1 Done: Roman Lebedev We believe that the bug you reported is fixed in the latest version of halide, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1068...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Roman Lebedev (supplier of updated halide package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 26 Jun 2024 04:33:35 +0300 Source: halide Binary: halide17-api-doc libhalide17-2 libhalide17-2-dbgsym libhalide17-dev libhalide17-dev-dbgsym libhalide17-doc libhalideaot17-2 python3-halide python3-halide-doc Architecture: source all amd64 Version: 17.0.2-1 Distribution: unstable Urgency: medium Maintainer: Roman Lebedev Changed-By: Roman Lebedev Description: halide17-api-doc - fast, portable computation on images and tensors (Doxygen documen libhalide17-2 - fast, portable computation on images and tensors libhalide17-dev - fast, portable computation on images and tensors -- Development f libhalide17-doc - fast, portable computation on images and tensors (C++ documentati libhalideaot17-2 - fast, portable computation on images and tensors (virtual library python3-halide - fast, portable computation on images and tensors -- Python3 bindi python3-halide-doc - fast, portable computation on images and tensors (Python3 documen Closes: 1066057 1068138 1069403 Changes: halide (17.0.2-1) unstable; urgency=medium . * Update to newest upstream point release * Go back to building against LLVM17, resulting in a soversion bump, see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067005 * Drop soversion from -dev package name, only one can be installed at the same time, add necessary breaks+replaces (Closes: #1066057) * Add explicit timeout for tests, allow them to be rerun at least once, to avoid spurious build failures due to flaky CI infra (Closes: #1069403) * Allow all tests to be rerun at least once, to avoid spurious build failures due to flaky CI infra (Closes: #1068138) * 64-bit `time_t` transition rebuild Checksums-Sha1: 81e38bfaa966ca5b2a0ebd778bd660e06fd10069 2905 halide_17.0.2-1.dsc c44ab8697195197e7b492c5da5a04a7a3c821018 33078928 halide_17.0.2.orig.tar.gz 93c348de3bcb85d839ad580ac47129074e9a55c5 295780 halide_17.0.2-1.debian.tar.xz fca3b49e7ae5666ea2392d172227f3dee677623e 5513024 halide17-api-doc_17.0.2-1_all.deb 78ef50e1fb04f59cff2a48bac9a1aae7d4184ada 14108 halide_17.0.2-1_amd64.buildinfo 4d68e85df580a4f0109db6ef86e334f4584ca339 32743076 libhalide17-2-dbgsym_17.0.2-1_amd64.deb 79d70aa19117aceb6d860881b7c49364f5d3f6f9 10120236 libhalide17-2_17.0.2-1_amd64.deb a76fd13887112e22df7f93b8ac000fb79d679ac0 5272544 libhalide17-dev-dbgsym_17.0.2-1_amd64.deb 7084f28922be07bc72ce8339a34c6b3823149ff4 2309636 libhalide17-dev_17.0.2-1_amd64.deb 0efdc1fa47f570b4e758c928c1d9f872d2c84f8f 4555952 libhalide17-doc_17.0.2-1_all.deb ec3263f63e79e3919f6c30d7b5e9c2539fb54993 5620 libhalideaot17-2_17.0.2-1_all.deb a99eb32f1764217affe17d802ed6023f21dc673a 45976 python3-halide-doc_17.0.2-1_all.deb c2f0cecaad709f2d965757946f18f1ce81ee3e8f 649556
Bug#1066057: marked as done (libhalide17-1-dev has an undeclared file conflict)
Your message dated Fri, 28 Jun 2024 18:00:11 + with message-id and subject line Bug#1066057: fixed in halide 17.0.2-1 has caused the Debian Bug report #1066057, regarding libhalide17-1-dev has an undeclared file conflict to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1066057: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066057 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libhalide17-1-dev Version: 17.0.1-1 Severity: serious User: debian...@lists.debian.org Usertags: fileconflict Control: affects -1 + libhalide17-0-dev libhalide17-1-dev has an undeclared file conflict. This may result in an unpack error from dpkg. The files * /usr/lib/x86_64-linux-gnu/cmake/Halide17/Halide-shared-deps.cmake * /usr/lib/x86_64-linux-gnu/cmake/Halide17/Halide-shared-targets-release.cmake * /usr/lib/x86_64-linux-gnu/cmake/Halide17/Halide-shared-targets.cmake * /usr/lib/x86_64-linux-gnu/cmake/Halide17/HalideConfig.cmake * /usr/lib/x86_64-linux-gnu/cmake/Halide17/HalideConfigVersion.cmake * /usr/lib/x86_64-linux-gnu/cmake/HalideHelpers17/FindHalide_WebGPU.cmake * /usr/lib/x86_64-linux-gnu/cmake/HalideHelpers17/Halide-Interfaces-release.cmake * /usr/lib/x86_64-linux-gnu/cmake/HalideHelpers17/Halide-Interfaces.cmake * /usr/lib/x86_64-linux-gnu/cmake/HalideHelpers17/HalideGeneratorHelpers.cmake * /usr/lib/x86_64-linux-gnu/cmake/HalideHelpers17/HalideHelpersConfig.cmake * /usr/lib/x86_64-linux-gnu/cmake/HalideHelpers17/HalideHelpersConfigVersion.cmake * /usr/lib/x86_64-linux-gnu/cmake/HalideHelpers17/HalideTargetHelpers.cmake * /usr/lib/x86_64-linux-gnu/cmake/HalideHelpers17/TargetExportScript.cmake * /usr/lib/x86_64-linux-gnu/halide17/adams2019_retrain_cost_model * /usr/lib/x86_64-linux-gnu/halide17/adams2019_weightsdir_to_weightsfile * /usr/lib/x86_64-linux-gnu/halide17/anderson2021_retrain_cost_model * /usr/lib/x86_64-linux-gnu/halide17/anderson2021_weightsdir_to_weightsfile * /usr/lib/x86_64-linux-gnu/halide17/featurization_to_sample * /usr/lib/x86_64-linux-gnu/halide17/get_host_target * /usr/lib/x86_64-linux-gnu/halide17/libautoschedule_adams2019.so * /usr/lib/x86_64-linux-gnu/halide17/libautoschedule_anderson2021.so * /usr/lib/x86_64-linux-gnu/halide17/libautoschedule_li2018.so * /usr/lib/x86_64-linux-gnu/halide17/libautoschedule_mullapudi2016.so * /usr/lib/x86_64-linux-gnu/libHalide17.so * /usr/lib/x86_64-linux-gnu/libHalidePyStubs17.a are contained in the packages * libhalide17-0-dev/17.0.0-2 as present in trixie * libhalide17-1-dev/17.0.1-1 as present in unstable These packages can be unpacked concurrently, because there is no relevant Replaces or Conflicts relation. Attempting to unpack these packages concurrently results in an unpack error from dpkg, because none of the packages installs a diversion for the affected files. Kind regards The Debian Usr Merge Analysis Tool This bug report has been automatically filed with no human intervention. The source code is available at https://salsa.debian.org/helmutg/dumat. If the filing is unclear or in error, don't hesitate to contact hel...@subdivi.de for assistance. --- End Message --- --- Begin Message --- Source: halide Source-Version: 17.0.2-1 Done: Roman Lebedev We believe that the bug you reported is fixed in the latest version of halide, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1066...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Roman Lebedev (supplier of updated halide package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 26 Jun 2024 04:33:35 +0300 Source: halide Binary: halide17-api-doc libhalide17-2 libhalide17-2-dbgsym libhalide17-dev libhalide17-dev-dbgsym libhalide17-doc libhalideaot17-2 python3-halide python3-halide-doc Architecture: source all amd64 Version: 17.0.2-1 Distribution: unstable Urgency: medium Maintainer: Roman Lebedev Changed-By: Roman Lebedev Description: halide17-api-doc - fast, portable computation on images and tensors (Doxygen documen libhalide17-2 - fast, portable computation on images and tensors libhalide17-dev - fast, portable computation on images and
Bug#1069495: wacomtablet: FTBFS on armhf: dh_auto_test: error: cd obj-arm-linux-gnueabihf && make -j4 test ARGS\+=--verbose ARGS\+=-j4 returned exit code 2
Hi, this bug seems not to have been seen in the reproducible-builds [1] or in the buildd [2] projects. The FTBFS is related to a failing test 9: qt.qpa.xcb: could not connect to display :99 9: qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found. 9: This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem. 9: 9: Available platform plugins are: eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, xcb. 9: 9/22 Test #9: Test.Common.PropertySet ..Subprocess aborted***Exception: 0.02 sec qt.qpa.xcb: could not connect to display :99 qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found. This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem. Available platform plugins are: eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, xcb. that looks more an issue with Qt (and xorg?). Is this still failing to build for you or shall we close this? Thank you Marco [1]https://tests.reproducible-builds.org/debian/history/armhf/wacomtablet.html [2]https://buildd.debian.org/status/fetch.php?pkg=wacomtablet=armhf=3.2.0-5%2Bb1=1711193918=0
Bug#1074442: freecad: FTBFS with Python 3.12 as default
Source: freecad
Version: 0.21.2+dfsg1-4
Severity: serious
Tags: ftbfs
User: debian-pyt...@lists.debian.org
Usertags: python3.12
freecad FTBFS with Python 3.12 as the default version [1]. I've
copied what I hope is the relevant part of the log below.
Regards
Graham
[1] https://tests.reproducible-builds.org/debian/rb-pkg/freecad.html
/build/reproducible-path/freecad-0.21.2+dfsg1/src/CXX/IndirectPythonInterface.cxx:
In function 'int& Py::_Py_DebugFlag()':
/build/reproducible-path/freecad-0.21.2+dfsg1/src/CXX/IndirectPythonInterface.cxx:521:63:
warning: 'Py_DebugFlag' is deprecated [-Wdeprecated-declarations]
521 | PYCXX_EXPORT int &_Py_DebugFlag(){ return
Py_DebugFlag; }
|
^~~~
In file included from /usr/include/python3.12/Python.h:48,
from
/build/reproducible-path/freecad-0.21.2+dfsg1/src/CXX/WrapPython.h:58,
from
/build/reproducible-path/freecad-0.21.2+dfsg1/src/CXX/IndirectPythonInterface.hxx:1,
from
/build/reproducible-path/freecad-0.21.2+dfsg1/src/CXX/IndirectPythonInterface.cxx:38:
/usr/include/python3.12/cpython/pydebug.h:8:37: note: declared here
8 | Py_DEPRECATED(3.12) PyAPI_DATA(int) Py_DebugFlag;
| ^~~~
/build/reproducible-path/freecad-0.21.2+dfsg1/src/CXX/IndirectPythonInterface.cxx:
In function 'int& Py::_Py_InteractiveFlag()':
/build/reproducible-path/freecad-0.21.2+dfsg1/src/CXX/IndirectPythonInterface.cxx:522:63:
warning: 'Py_InteractiveFlag' is deprecated
[-Wdeprecated-declarations]
522 | PYCXX_EXPORT int &_Py_InteractiveFlag() { return
Py_InteractiveFlag; }
|
^~
/usr/include/python3.12/cpython/pydebug.h:11:37: note: declared here
11 | Py_DEPRECATED(3.12) PyAPI_DATA(int) Py_InteractiveFlag;
| ^~
/build/reproducible-path/freecad-0.21.2+dfsg1/src/CXX/IndirectPythonInterface.cxx:
In function 'int& Py::_Py_OptimizeFlag()':
/build/reproducible-path/freecad-0.21.2+dfsg1/src/CXX/IndirectPythonInterface.cxx:523:63:
warning: 'Py_OptimizeFlag' is deprecated [-Wdeprecated-declarations]
523 | PYCXX_EXPORT int &_Py_OptimizeFlag() { return
Py_OptimizeFlag; }
|
^~~
/usr/include/python3.12/cpython/pydebug.h:13:37: note: declared here
13 | Py_DEPRECATED(3.12) PyAPI_DATA(int) Py_OptimizeFlag;
| ^~~
/build/reproducible-path/freecad-0.21.2+dfsg1/src/CXX/IndirectPythonInterface.cxx:
In function 'int& Py::_Py_NoSiteFlag()':
/build/reproducible-path/freecad-0.21.2+dfsg1/src/CXX/IndirectPythonInterface.cxx:524:63:
warning: 'Py_NoSiteFlag' is deprecated [-Wdeprecated-declarations]
524 | PYCXX_EXPORT int &_Py_NoSiteFlag() { return
Py_NoSiteFlag; }
|
^
/usr/include/python3.12/cpython/pydebug.h:14:37: note: declared here
14 | Py_DEPRECATED(3.12) PyAPI_DATA(int) Py_NoSiteFlag;
| ^
/build/reproducible-path/freecad-0.21.2+dfsg1/src/CXX/IndirectPythonInterface.cxx:
In function 'int& Py::_Py_VerboseFlag()':
/build/reproducible-path/freecad-0.21.2+dfsg1/src/CXX/IndirectPythonInterface.cxx:525:63:
warning: 'Py_VerboseFlag' is deprecated [-Wdeprecated-declarations]
525 | PYCXX_EXPORT int &_Py_VerboseFlag() { return
Py_VerboseFlag; }
|
^~
/usr/include/python3.12/cpython/pydebug.h:9:37: note: declared here
9 | Py_DEPRECATED(3.12) PyAPI_DATA(int) Py_VerboseFlag;
| ^~
/build/reproducible-path/freecad-0.21.2+dfsg1/src/CXX/IndirectPythonInterface.cxx:
In function 'const char* Py::__Py_PackageContext()':
/build/reproducible-path/freecad-0.21.2+dfsg1/src/CXX/IndirectPythonInterface.cxx:527:63:
error: '_Py_PackageContext' was not declared in this scope; did you
mean '__Py_PackageContext'?
527 | PYCXX_EXPORT const char *__Py_PackageContext() { return
_Py_PackageContext; }
|
^~
|
__Py_PackageContext
Processed: forcibly merging 1069433 1069512
Processing commands for cont...@bugs.debian.org:
> forcemerge 1069433 1069512
Bug #1069433 {Done: Samuel Thibault } [src:openmpi]
gtg-trace: FTBFS on armhf: tests fail
Bug #1069512 {Done: Samuel Thibault } [src:openmpi]
python-escript: FTBFS on armhf: tests fail
Removed indication that 1069512 affects src:gtg-trace
Added indication that 1069512 affects src:python-escript,src:gtg-trace
Bug #1069433 {Done: Samuel Thibault } [src:openmpi]
gtg-trace: FTBFS on armhf: tests fail
Marked as fixed in versions openmpi/4.1.6-13; no longer marked as fixed in
versions 4.1.6-13.
Merged 1069433 1069512
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1069433: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069433
1069512: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069512
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1042221: marked as done (xraylib: FTBFS: dh_install: error: missing files, aborting)
Your message dated Fri, 28 Jun 2024 20:14:14 +0300 with message-id and subject line Fixed in unstable has caused the Debian Bug report #1042221, regarding xraylib: FTBFS: dh_install: error: missing files, aborting to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1042221: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042221 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: xraylib Version: 4.0.0+dfsg1-3 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230726 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > dh_auto_install > cd obj-x86_64-linux-gnu && > DESTDIR=/<>/xraylib-4.0.0\+dfsg1/debian/tmp LC_ALL=C.UTF-8 ninja > install > [0/1] Installing files. > Compiling > '/<>/debian/tmp/usr/local/lib/python3.11/dist-packages/xraylib.py'... > Installing src/libxrl.so.11.1.0 to > /<>/debian/tmp/usr/lib/x86_64-linux-gnu > Installing python/xraylib.py to > /<>/debian/tmp/usr/local/lib/python3.11/dist-packages > Installing python/_xraylib.cpython-311-x86_64-linux-gnu.so to > /<>/debian/tmp/usr/local/lib/python3.11/dist-packages > Installing python/xraylib_np.cpython-311-x86_64-linux-gnu.so to > /<>/debian/tmp/usr/local/lib/python3.11/dist-packages > Installing /<>/include/xraylib.h to > /<>/debian/tmp/usr/include/xraylib/ > Installing /<>/include/xraylib-lines.h to > /<>/debian/tmp/usr/include/xraylib/ > Installing /<>/include/xraylib-shells.h to > /<>/debian/tmp/usr/include/xraylib/ > Installing /<>/include/xraylib-parser.h to > /<>/debian/tmp/usr/include/xraylib/ > Installing /<>/include/xraylib-auger.h to > /<>/debian/tmp/usr/include/xraylib/ > Installing /<>/include/xraylib-defs.h to > /<>/debian/tmp/usr/include/xraylib/ > Installing /<>/include/xraylib-crystal-diffraction.h to > /<>/debian/tmp/usr/include/xraylib/ > Installing /<>/include/xraylib-nist-compounds.h to > /<>/debian/tmp/usr/include/xraylib/ > Installing /<>/include/xraylib-radionuclides.h to > /<>/debian/tmp/usr/include/xraylib/ > Installing /<>/include/xraylib-error.h to > /<>/debian/tmp/usr/include/xraylib/ > Installing /<>/include/xraylib-deprecated.h to > /<>/debian/tmp/usr/include/xraylib/ > Installing /<>/include/xraylib-aux.h to > /<>/debian/tmp/usr/include/xraylib/ > Installing /<>/cplusplus/xraylib++.h to > /<>/debian/tmp/usr/include/xraylib/ > Installing /<>/obj-x86_64-linux-gnu/meson-private/libxrl.pc to > /<>/debian/tmp/usr/lib/x86_64-linux-gnu/pkgconfig > Installing symlink pointing to libxrl.so.11.1.0 to > /<>/debian/tmp/usr/lib/x86_64-linux-gnu/libxrl.so.11 > Installing symlink pointing to libxrl.so.11 to > /<>/debian/tmp/usr/lib/x86_64-linux-gnu/libxrl.so > Running custom install script '/usr/bin/python3 > /<>/obj-x86_64-linux-gnu/meson-private/pycompile.py > python-3.11-installed.json 0' > find debian/tmp/ -name xraydoc.txt -delete || true > find debian/tmp -name libxrl.la -delete || true > make[1]: Leaving directory '/<>' >dh_install -O-Smeson > dh_install: warning: Cannot find (any matches for) > "usr/lib/python3*/*-packages/_xraylib*.so" (tried in ., debian/tmp) > > dh_install: warning: python3-xraylib missing files: > usr/lib/python3*/*-packages/_xraylib*.so > dh_install: warning: Cannot find (any matches for) > "usr/lib/python3*/*-packages/xraylib*" (tried in ., debian/tmp) > > dh_install: warning: python3-xraylib missing files: > usr/lib/python3*/*-packages/xraylib* > dh_install: error: missing files, aborting > make: *** [debian/rules:15: binary] Error 25 The full build log is available from: http://qa-logs.debian.net/2023/07/26/xraylib_4.0.0+dfsg1-3_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230726;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20230726=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Whatever caused this seems to have been fixed last August in unstable:
Processed: llvm/llvmlite/numba
Processing commands for cont...@bugs.debian.org: > block 1068961 by 1050069 Bug #1068961 [src:llvm-toolchain-18] llvm-toolchain-18: block migration to testing: to many llvm-toolchain versions in testing 1068961 was not blocked by any bugs. 1068961 was not blocking any bugs. Added blocking bug(s) of 1068961: 1050069 > End of message, stopping processing here. Please contact me if you need assistance. -- 1068961: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068961 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1073828: libuim-data update fails due to undefined symbol
Control: tags -1 patch On 2024-06-19 "Gustavo R. Montesino" wrote: > Package: libuim-data > Version: 1:1.8.8-9.4 > Severity: serious > Justification: Policy 8.6 > Hello, > Can't upate libuim-data due to undefined symbol in uim-module-manager: > Configurando libuim-data (1:1.8.8-9.4) ... > uim-module-manager: symbol lookup error: uim-module-manager: undefined > symbol: uim_internal_strlcpy Hello, The latest iteration of https://salsa.debian.org/debian/uim/-/merge_requests/15#note_501667 is intended to fix this. cu Andreas
Processed: Re: Bug#1073828: libuim-data update fails due to undefined symbol
Processing control commands: > tags -1 patch Bug #1073828 [libuim-data] libuim-data update fails due to undefined symbol Added tag(s) patch. -- 1073828: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1073828 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed (with 1 error): Merge duplicates
Processing commands for cont...@bugs.debian.org:
> reassign 1069512 src:openmpi
Bug #1069512 [src:python-escript] python-escript: FTBFS on armhf: tests fail
Bug reassigned from package 'src:python-escript' to 'src:openmpi'.
No longer marked as found in versions python-escript/5.6-7.
Ignoring request to alter fixed versions of bug #1069512 to the same values
previously set
> forcemerge 1069433 1069512
Bug #1069433 {Done: Samuel Thibault } [src:openmpi]
gtg-trace: FTBFS on armhf: tests fail
Bug #1069512 [src:openmpi] python-escript: FTBFS on armhf: tests fail
Marked Bug as done
Added indication that 1069512 affects src:gtg-trace
Marked as fixed in versions openmpi/4.1.6-13.
Marked as found in versions openmpi/4.1.6-12 and openmpi/4.1.6-3.
Bug #1069433 {Done: Samuel Thibault } [src:openmpi]
gtg-trace: FTBFS on armhf: tests fail
Added tag(s) trixie and sid.
Bug #1069512 {Done: Samuel Thibault } [src:openmpi]
python-escript: FTBFS on armhf: tests fail
Ignoring request to alter fixed versions of bug #1069512 to the same values
previously set
Unable to complete merge on previous attempt; trying again (retry: 2)
Bug #1069512 {Done: Samuel Thibault } [src:openmpi]
python-escript: FTBFS on armhf: tests fail
Ignoring request to alter fixed versions of bug #1069512 to the same values
previously set
Unable to complete merge on previous attempt; trying again (retry: 3)
Bug #1069512 {Done: Samuel Thibault } [src:openmpi]
python-escript: FTBFS on armhf: tests fail
Ignoring request to alter fixed versions of bug #1069512 to the same values
previously set
After four attempts, the following changes were unable to be made:
fixed_versions of #1069512 is 'openmpi/4.1.6-13' not '4.1.6-13'
Failed to forcibly merge 1069433: Unable to modify bugs so they could be merged.
> affects 1069433 src:python-escript
Bug #1069433 {Done: Samuel Thibault } [src:openmpi]
gtg-trace: FTBFS on armhf: tests fail
Added indication that 1069433 affects src:python-escript
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1069433: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069433
1069512: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069512
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: Fixed in experimental, and no longer RC since old binaries were removed
Processing commands for cont...@bugs.debian.org:
> close 1068684 22~git20240513132534.e278a05+ds3-1
Bug #1068684 [src:bornagain] bornagain: FTBFS on many architectures
Marked as fixed in versions bornagain/22~git20240513132534.e278a05+ds3-1.
Bug #1068684 [src:bornagain] bornagain: FTBFS on many architectures
Marked Bug as done
> severity 1068684 important
Bug #1068684 {Done: Adrian Bunk } [src:bornagain] bornagain:
FTBFS on many architectures
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1068684: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068684
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: bump severity of python 3.12 ftbfs bugs
Processing commands for cont...@bugs.debian.org: > severity 1067507 serious Bug #1067507 [src:lomiri-ui-toolkit] lomiri-ui-toolkit ftbfs with Python 3.12 Severity set to 'serious' from 'important' > severity 1067598 serious Bug #1067598 [src:wfuzz] wfuzz: FTBFS with Python 3.12 as default Severity set to 'serious' from 'important' > severity 1070437 serious Bug #1070437 [src:skimage] skimage: FTBFS with Python 3.12 as default Severity set to 'serious' from 'important' > severity 1069221 serious Bug #1069221 [src:termbox] termbox ftbfs with Python 3.12 Severity set to 'serious' from 'important' > severity 1064307 serious Bug #1064307 [src:awscli] awscli ftbfs with Python 3.12 as the default Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 1064307: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064307 1067507: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067507 1067598: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067598 1069221: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069221 1070437: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070437 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1074435: yade: FTBFS with Python 3.12 as default
Source: yade Version: 2024.02a-1 Severity: serious Tags: ftbfs User: debian-pyt...@lists.debian.org Usertags: python3.12 yade FTBFS with Python 3.12 as the default version [1]. I've copied what I hope is the relevant part of the log below. Regards Graham [1] https://buildd.debian.org/status/fetch.php?pkg=yade=amd64=2024.02a-1%2Bb4=1719565244=0 CMake Warning (dev) at cMake/GetVersion.cmake:7 (exec_program): Policy CMP0153 is not set: The exec_program command should not be called. Run "cmake --help-policy CMP0153" for policy details. Use the cmake_policy command to set the policy and suppress this warning. Use execute_process() instead. Call Stack (most recent call first): CMakeLists.txt:139 (INCLUDE) This warning is for project developers. Use -Wno-dev to suppress it. -- Version is set to 2024.02a -- GCC Version >= 4.8. Adding -ftrack-macro-expansion=0 -- GCC Version >= 4.8. Adding -save-temps -- Found Eigen3: /usr/include/eigen3 (Required is at least version "2.91.0") -- [36mLog filtering: enabled [0m -- Enabling boost::log library and DEBUG=OFF. Logging will work nicely, backtraces will not have debug info, files will be small. -- Architecture: amd64 -- Found GLUT: /usr/lib/x86_64-linux-gnu/libglut.so -- Found freeglut: /usr/include/GL -- md5sum of freegult /usr/include/GL/freeglut_std.h is: 5d350938fc0be29757a26e466fff6414 -- freegult version is 3.0.0 Loop on the following python versions and check available dependencies:3.11;3.10;3.9;3.8;3.7;3.6;3.5;3.4;3.3;3.2;3.1;3.0 CMake Warning (dev) at CMakeLists.txt:328 (FIND_PACKAGE): Policy CMP0148 is not set: The FindPythonInterp and FindPythonLibs modules are removed. Run "cmake --help-policy CMP0148" for policy details. Use the cmake_policy command to set the policy and suppress this warning. This warning is for project developers. Use -Wno-dev to suppress it. -- Found PythonInterp: /usr/bin/python3 (found version "3.12.4") Trying python version: 3.11 parsed as 3 11 CMake Warning (dev) at CMakeLists.txt:328 (FIND_PACKAGE): Policy CMP0148 is not set: The FindPythonInterp and FindPythonLibs modules are removed. Run "cmake --help-policy CMP0148" for policy details. Use the cmake_policy command to set the policy and suppress this warning. This warning is for project developers. Use -Wno-dev to suppress it.
Bug#1058165: marked as done (itango: FTBFS: ModuleNotFoundError: No module named 'tango._tango')
Your message dated Fri, 28 Jun 2024 13:19:16 +
with message-id
and subject line Bug#1058165: fixed in itango 0.1.9+ds-1
has caused the Debian Bug report #1058165,
regarding itango: FTBFS: ModuleNotFoundError: No module named 'tango._tango'
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1058165: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058165
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: itango
Version: 0.1.7-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20231212 ftbfs-trixie
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_auto_build
> I: pybuild base:310: /usr/bin/python3.12 setup.py build
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.12_itango/build/itango
> copying itango/__init__.py ->
> /<>/.pybuild/cpython3_3.12_itango/build/itango
> copying itango/eventlogger.py ->
> /<>/.pybuild/cpython3_3.12_itango/build/itango
> copying itango/itango.py ->
> /<>/.pybuild/cpython3_3.12_itango/build/itango
> copying itango/common.py ->
> /<>/.pybuild/cpython3_3.12_itango/build/itango
> copying itango/__main__.py ->
> /<>/.pybuild/cpython3_3.12_itango/build/itango
> copying itango/install.py ->
> /<>/.pybuild/cpython3_3.12_itango/build/itango
> creating /<>/.pybuild/cpython3_3.12_itango/build/itango/resource
> copying itango/resource/starter.png ->
> /<>/.pybuild/cpython3_3.12_itango/build/itango/resource
> copying itango/resource/motor.png ->
> /<>/.pybuild/cpython3_3.12_itango/build/itango/resource
> copying itango/resource/database.png ->
> /<>/.pybuild/cpython3_3.12_itango/build/itango/resource
> copying itango/resource/serial.png ->
> /<>/.pybuild/cpython3_3.12_itango/build/itango/resource
> copying itango/resource/device.png ->
> /<>/.pybuild/cpython3_3.12_itango/build/itango/resource
> copying itango/resource/ITangoConsole.svg ->
> /<>/.pybuild/cpython3_3.12_itango/build/itango/resource
> I: pybuild base:310: /usr/bin/python3 setup.py build
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.11_itango/build/itango
> copying itango/__init__.py ->
> /<>/.pybuild/cpython3_3.11_itango/build/itango
> copying itango/eventlogger.py ->
> /<>/.pybuild/cpython3_3.11_itango/build/itango
> copying itango/itango.py ->
> /<>/.pybuild/cpython3_3.11_itango/build/itango
> copying itango/common.py ->
> /<>/.pybuild/cpython3_3.11_itango/build/itango
> copying itango/__main__.py ->
> /<>/.pybuild/cpython3_3.11_itango/build/itango
> copying itango/install.py ->
> /<>/.pybuild/cpython3_3.11_itango/build/itango
> creating /<>/.pybuild/cpython3_3.11_itango/build/itango/resource
> copying itango/resource/starter.png ->
> /<>/.pybuild/cpython3_3.11_itango/build/itango/resource
> copying itango/resource/motor.png ->
> /<>/.pybuild/cpython3_3.11_itango/build/itango/resource
> copying itango/resource/database.png ->
> /<>/.pybuild/cpython3_3.11_itango/build/itango/resource
> copying itango/resource/serial.png ->
> /<>/.pybuild/cpython3_3.11_itango/build/itango/resource
> copying itango/resource/device.png ->
> /<>/.pybuild/cpython3_3.11_itango/build/itango/resource
> copying itango/resource/ITangoConsole.svg ->
> /<>/.pybuild/cpython3_3.11_itango/build/itango/resource
> PYTHONPATH=. http_proxy='127.0.0.1:9' sphinx-build -N -bman doc/ build/man
> Running Sphinx v7.2.6
> making output directory... done
> building [mo]: targets for 0 po files that are out of date
> writing output...
> building [man]: all manpages
> updating environment: [new config] 1 added, 0 changed, 0 removed
> [2Kreading sources... [100%] itango
>
> looking for now-outdated files... none found
> pickling environment... done
> checking consistency... done
> writing... itango.1 { } done
> build succeeded.
>
> The manual pages are in build/man.
> cp build/man/itango.1 build/man/itango3.1
> PYTHONPATH=. http_proxy='127.0.0.1:9' sphinx-build -N -bhtml doc/
> build/sphinx/html
> Running Sphinx v7.2.6
> making output directory... done
> building [mo]: targets for 0 po files that are out of date
> writing output...
> building [html]: targets for 1 source files that are out of date
> updating environment: [new config] 1 added, 0 changed, 0 removed
> [2Kreading sources... [100%] itango
>
> looking for now-outdated files... none found
> pickling environment... done
> checking consistency... done
> preparing documents... done
> copying assets... copying static files... done
> copying extra files...
Processed: Re: Bug#1071894: closing 1071894
Processing commands for cont...@bugs.debian.org:
> # adding for completeness, as this was actually fixed yesterday
> fixed 1071894 0.7.4-5
Bug #1071894 {Done: Roland Mas } [src:stackview] stackview:
FTBFS: unsatisfiable build-dependencies
Marked as fixed in versions stackview/0.7.4-5.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1071894: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071894
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1071894: closing 1071894
close 1071894 0.7.10-1 thanks
Processed: closing 1071894
Processing commands for cont...@bugs.debian.org: > close 1071894 0.7.10-1 Bug #1071894 [src:stackview] stackview: FTBFS: unsatisfiable build-dependencies The source 'stackview' and version '0.7.10-1' do not appear to match any binary packages Marked as fixed in versions stackview/0.7.10-1. Bug #1071894 [src:stackview] stackview: FTBFS: unsatisfiable build-dependencies Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 1071894: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071894 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1074430: adminer: CVE-2023-45196 CVE-2023-45195
Source: adminer X-Debbugs-CC: t...@security.debian.org Severity: grave Tags: security Hi, The following vulnerabilities were published for adminer. CVE-2023-45196[0]: | Adminer and AdminerEvo allow an unauthenticated remote attacker to | cause a denial of service by connecting to an attacker-controlled | service that responds with HTTP redirects. The denial of service is | subject to PHP configuration limits. Adminer is no longer supported, | but this issue was fixed in AdminerEvo version 4.8.4. https://github.com/adminerevo/adminerevo/pull/102/commits/23e7cdc0a32b3739e13d19ae504be0fe215142b6 CVE-2023-45195[1]: | Adminer and AdminerEvo are vulnerable to SSRF via database | connection fields. This could allow an unauthenticated remote | attacker to enumerate or access systems the attacker would not | otherwise have access to. Adminer is no longer supported, but this | issue was fixed in AdminerEvo version 4.8.4. https://github.com/adminerevo/adminerevo/pull/102/commits/18f3167bbcbec3bc746f62db72e016aa99144efc It seems adminer is dead upstream and adminerevo picked up development, so most likely Debian should follow the new upstream? If you fix the vulnerabilities please also make sure to include the CVE (Common Vulnerabilities & Exposures) ids in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2023-45196 https://www.cve.org/CVERecord?id=CVE-2023-45196 [1] https://security-tracker.debian.org/tracker/CVE-2023-45195 https://www.cve.org/CVERecord?id=CVE-2023-45195 Please adjust the affected versions in the BTS as needed.
Bug#1066629: marked as done (ucspi-tcp: FTBFS: tcpserver.c:143:29: error: implicit declaration of function ‘getpid’ [-Werror=implicit-function-declaration])
Your message dated Fri, 28 Jun 2024 11:29:48 +
with message-id
and subject line Bug#1066629: fixed in ucspi-tcp 1:0.88-9
has caused the Debian Bug report #1066629,
regarding ucspi-tcp: FTBFS: tcpserver.c:143:29: error: implicit declaration of
function ‘getpid’ [-Werror=implicit-function-declaration]
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1066629: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066629
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ucspi-tcp
Version: 1:0.88-8
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240313 ftbfs-trixie ftbfs-impfuncdef
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
This is most likely caused by a change in dpkg 1.22.6, that enabled
-Werror=implicit-function-declaration. For more information, see
https://wiki.debian.org/qa.debian.org/FTBFS#A2024-03-13_-Werror.3Dimplicit-function-declaration
Relevant part (hopefully):
> x86_64-linux-gnu-gcc -g -O2 -Werror=implicit-function-declaration
> -ffile-prefix-map=/<>=. -fstack-protector-strong
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection
> -Wdate-time -D_FORTIFY_SOURCE=2 -c tcpserver.c
> tcpserver.c: In function ‘doit’:
> tcpserver.c:143:29: error: implicit declaration of function ‘getpid’
> [-Werror=implicit-function-declaration]
> 143 | strnum[fmt_ulong(strnum,getpid())] = 0;
> | ^~
> tcpserver.c:148:5: error: implicit declaration of function
> ‘socket_ipoptionskill’ [-Werror=implicit-function-declaration]
> 148 | socket_ipoptionskill(t);
> | ^~~~
> tcpserver.c:150:5: error: implicit declaration of function
> ‘socket_tcpnodelay’ [-Werror=implicit-function-declaration]
> 150 | socket_tcpnodelay(t);
> | ^
> tcpserver.c:210:7: error: implicit declaration of function ‘close’
> [-Werror=implicit-function-declaration]
> 210 | close(fdrules);
> | ^
> tcpserver.c: At top level:
> tcpserver.c:292:1: warning: return type defaults to ‘int’ [-Wimplicit-int]
> 292 | main(int argc,char **argv)
> | ^~~~
> tcpserver.c: In function ‘main’:
> tcpserver.c:408:12: error: implicit declaration of function ‘fork’
> [-Werror=implicit-function-declaration]
> 408 | switch(fork()) {
> |^~~~
> cc1: some warnings being treated as errors
> make[2]: *** [Makefile:759: tcpserver.o] Error 1
The full build log is available from:
http://qa-logs.debian.net/2024/03/13/ucspi-tcp_0.88-8_unstable.log
All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240313;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240313=lu...@debian.org=1=1=1=1#results
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects
If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: ucspi-tcp
Source-Version: 1:0.88-9
Done: Peter Pentchev
We believe that the bug you reported is fixed in the latest version of
ucspi-tcp, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 1066...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Peter Pentchev (supplier of updated ucspi-tcp package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Fri, 28 Jun 2024 13:59:27 +0300
Source: ucspi-tcp
Architecture: source
Version: 1:0.88-9
Distribution: unstable
Urgency: medium
Maintainer: Peter Pentchev
Changed-By: Peter Pentchev
Closes: 1066629
Changes:
ucspi-tcp (1:0.88-9) unstable; urgency=medium
.
* Import the 0006-implicit-declarations Ubuntu patch to fix
the FTBFS in Debian unstable due to the
Processed: tag 1074265 as pending
Processing commands for cont...@bugs.debian.org: > tag 1074265 pending Bug #1074265 [libcgal-qt6-dev] libcgal-qt6-dev: missing Breaks+Replaces: libcgal-qt5-dev (<< 6) Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 1074265: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074265 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: closing 1063190
Processing control commands:
> found -1 5.2.1.13040+dfsg-2
Bug #1063190 {Done: Pierre-Elliott Bécue }
[src:owncloud-client] owncloud-client: NMU diff for 64-bit time_t transition
Marked as found in versions owncloud-client/5.2.1.13040+dfsg-2 and reopened.
--
1063190: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063190
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1063190: closing 1063190
Control: found -1 5.2.1.13040+dfsg-2 On Tue, 25 Jun 2024 15:36:40 +0200 Agustin Martin wrote: On Mon, Jun 10, 2024 at 11:46:20PM +0200, Pierre-Elliott Bécue wrote: > close 1063190 > thanks Hi, Pierre-Elliott owncloud-client seems still not in testing because of #1063190. Missing version in bug closing? The 5.x uploads have reverted the t64 renaming of libowncloudsync0 to libowncloudsync0t64 without any explanation why the transition would not be needed for this package. The t64 nmu needs to be reinstated before this package can migrate to testing. Andreas
Bug#1073991: marked as done (ezurio-qcacld-2.0-dkms: module fails to build for Linux 6.9: wlan_hdd_hostapd.c:1574:9: error: too many arguments to function 'cfg80211_ch_switch_notify')
Your message dated Fri, 28 Jun 2024 10:24:25 + with message-id and subject line Bug#1073991: fixed in ezurio-qcacld-2.0-dkms 0.0~git20230623.2cd31b6-3 has caused the Debian Bug report #1073991, regarding ezurio-qcacld-2.0-dkms: module fails to build for Linux 6.9: wlan_hdd_hostapd.c:1574:9: error: too many arguments to function 'cfg80211_ch_switch_notify' to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1073991: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1073991 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: ezurio-qcacld-2.0-dkms Version: 0.0~git20230623.2cd31b6-2 Severity: important Hi, your package fails to build a module for Linux 6.9 in experimental: /var/lib/dkms/ezurio-qcacld-2.0/0.0~git20230623.2cd31b6/build/CORE/HDD/src/wlan_hdd_hostapd.c: In function 'hdd_chan_change_notify': /var/lib/dkms/ezurio-qcacld-2.0/0.0~git20230623.2cd31b6/build/CORE/HDD/src/wlan_hdd_hostapd.c:1574:9: error: too many arguments to function 'cfg80211_ch_switch_notify' 1574 | cfg80211_ch_switch_notify(dev, , 0, 0); | ^ Please see the attached make.log for lots of warnings that could be related. Andreas make.log.xz Description: application/xz --- End Message --- --- Begin Message --- Source: ezurio-qcacld-2.0-dkms Source-Version: 0.0~git20230623.2cd31b6-3 Done: Johannes Schauer Marin Rodrigues We believe that the bug you reported is fixed in the latest version of ezurio-qcacld-2.0-dkms, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1073...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Johannes Schauer Marin Rodrigues (supplier of updated ezurio-qcacld-2.0-dkms package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 28 Jun 2024 12:03:34 +0200 Source: ezurio-qcacld-2.0-dkms Architecture: source Version: 0.0~git20230623.2cd31b6-3 Distribution: unstable Urgency: medium Maintainer: Lukas F. Hartmann Changed-By: Johannes Schauer Marin Rodrigues Closes: 1073991 Changes: ezurio-qcacld-2.0-dkms (0.0~git20230623.2cd31b6-3) unstable; urgency=medium . * debian/patches/fixup.patch: fix compilation for linux 6.9 (closes: #1073991) Checksums-Sha1: cc2cf0eede9ded935f2600ad995488cbe5310cd8 2325 ezurio-qcacld-2.0-dkms_0.0~git20230623.2cd31b6-3.dsc 430311c52ca871b75500c230bbf3c59c2347d9d6 16496 ezurio-qcacld-2.0-dkms_0.0~git20230623.2cd31b6-3.debian.tar.xz Checksums-Sha256: d10ecd1a9095f7c892235529918aaddead6bbb5adc8d45854b3710189b85b763 2325 ezurio-qcacld-2.0-dkms_0.0~git20230623.2cd31b6-3.dsc c347dfa0339b6d4090062669d642b7fe3fb979b3e0843362723a2263223a3293 16496 ezurio-qcacld-2.0-dkms_0.0~git20230623.2cd31b6-3.debian.tar.xz Files: 4e1edf767876ed83d566766e7af52f5e 2325 kernel optional ezurio-qcacld-2.0-dkms_0.0~git20230623.2cd31b6-3.dsc 8dbb424ec5f34214963fe464d1b5f6d0 16496 kernel optional ezurio-qcacld-2.0-dkms_0.0~git20230623.2cd31b6-3.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEElFhU6KL81LF4wVq58sulx4+9g+EFAmZ+irIACgkQ8sulx4+9 g+EPqA/+IZMUDELaGP/Qq4CDJgGb8iWDagA0xgp6loP4wwR4YrYEqd1Z1qkMIt+P 9yzYLXDOsmjOQ1hCdgxzsDyx16hQ+SML85sZr27AmkFR6ugLNAZDZiyBtbagkXR5 HNlh/b6d0a6RLjswEJJCWOroVwAWnLHXiJ8vAV+69/qJRZMfhKsJVi/LzOQtHZPo C4HVoccXxDqv5A4Tgt5EVfZ51EzFeqxR3TyZRRTYyhG99yukplaUq2MYD876LKIB Pdoh+A3pdBMw3gHHWkRQKMw0u0wCUUYB1lIhFq0Q5zTPVJ2iYQ6RFRMHnpCK0Jbt /5GOqBrkX+muwtmTEw2dm6grQ0MXpDqlZ6VG+MybBtuO8QQJKKFl6eqBdnCHxiJ/ twuj6noW4lpzgj+tu6wYtTYyViC32yN4dg8Cu+v7cJSqCKy66rx0TqLJx20mvOjY TD9ySMKvlZ9zSLSiJQilzeiMFRf7B+Pn9L+qMfNQNEOwes3pjEET2cxEyYC/qSXa vP1psMRjZgkK/7c3SqrgA+kNjLU+XAI27bxr53gPppgp0pj2MtDYpaPLSM5lLPip DLtNNCsgLN74WZ3aVHmbgL773g6AaCZ0mhxP8EZEnNz7wPz0yS85ePzbzJ9t5Oip MCp0VylLC3k4Y9P9Gg2ZP9TR2AT6+trQmtEemhv7QL0xbm82W2U= =yJE9 -END PGP SIGNATURE- pgpF2FQq4vbQy.pgp Description: PGP signature --- End Message ---
Bug#1074412: rust-apr:FTBFS:build failure（arguments to this function are incorrect）
Source: rust-apr
Version: 0.1.9-1
Severity: serious
Tags: FTBFS, patch
User: debian-ri...@lists.debian.org
Usertags: riscv64
X-Debbugs-Cc: debian-ri...@lists.debian.org
Dear rust-apr Maintainer,
The package rust-apr build failed on arch riscv64,arm64,ppc64el and s490x
caused by incorrect arguments.The crucial buildd log below:
```
Running `CARGO=/usr/bin/cargo CARGO_CRATE_NAME=apr
CARGO_MANIFEST_DIR=/<> CARGO_PKG_AUTHORS='Jelmer Vernooij
' CARGO_PKG_DESCRIPTION='Rust bindings for Apache
Portable Runtime'
CARGO_PKG_HOMEPAGE='https://github.com/jelmer/apr-rs'
CARGO_PKG_LICENSE=Apache-2.0 CARGO_PKG_LICENSE_FILE=''
CARGO_PKG_NAME=apr
CARGO_PKG_REPOSITORY='https://github.com/jelmer/apr-rs.git'
CARGO_PKG_RUST_VERSION='' CARGO_PKG_VERSION=0.1.9
CARGO_PKG_VERSION_MAJOR=0 CARGO_PKG_VERSION_MINOR=1
CARGO_PKG_VERSION_PATCH=9 CARGO_PKG_VERSION_PRE=''
CARGO_PRIMARY_PACKAGE=1
LD_LIBRARY_PATH='/<>/target/debug/deps:/usr/lib'
OUT_DIR=/<>/target/riscv64gc-unknown-linux-gnu/debug/build/apr-b417133e16d63cef/out
rustc --crate-name apr --edition=2021 src/lib.rs --error-format=json
--json=diagnostic-rendered-ansi,artifacts,future-incompat
--emit=dep-info,link -C embed-bitcode=no -C debuginfo=2 --test -C
metadata=5bed62fa808055ec -C extra-filename=-5bed62fa808055ec
--out-dir /<>/target/riscv64gc-unknown-linux-gnu/debug/deps
--target riscv64gc-unknown-linux-gnu -C
incremental=/<>/target/riscv64gc-unknown-linux-gnu/debug/incremental
-L dependency=/<>/target/riscv64gc-unknown-linux-gnu/debug/deps
-L dependency=/<>/target/debug/deps --extern
ctor=/<>/target/debug/deps/libctor-bd244608a47cb8e3.so -C
debuginfo=2 --cap-lints warn -C linker=riscv64-linux-gnu-gcc -C
link-arg=-Wl,-z,relro --remap-path-prefix
/<>=/usr/share/cargo/registry/apr-0.1.9
--remap-path-prefix
/<>/debian/cargo_registry=/usr/share/cargo/registry -L
native=/usr/lib/riscv64-linux-gnu -l apr-1 -l aprutil-1 -l ldap -l
lber -l apr-1 --cfg system_deps_have_apr_1 --cfg
system_deps_have_apr_util_1`
error[E0308]: arguments to this function are incorrect
--> src/date.rs:5:14
|
5 | unsafe { apr_date_checkmask(data.as_ptr() as *const i8,
mask.as_ptr() as *const i8) != 0 }
| ^^
|
note: expected `*const u8`, found `*const i8`
--> src/date.rs:5:33
|
5 | unsafe { apr_date_checkmask(data.as_ptr() as *const i8,
mask.as_ptr() as *const i8) != 0 }
| ^^
= note: expected raw pointer `*const u8`
found raw pointer `*const i8`
note: expected `*const u8`, found `*const i8`
--> src/date.rs:5:61
|
5 | unsafe { apr_date_checkmask(data.as_ptr() as *const i8,
mask.as_ptr() as *const i8) != 0 }
|
^^
= note: expected raw pointer `*const u8`
found raw pointer `*const i8`
note: function defined here
-->
/usr/share/cargo/registry/apr-0.1.9/target/riscv64gc-unknown-linux-gnu/debug/build/apr-b417133e16d63cef/out/generated.rs:3:152799
|
3 | ...r\n @return 1 if the string matches, 0 otherwise"] pub fn
apr_date_checkmask (data : * const :: std :: os :: raw :: c_char ,
mask : * ...
|
^^
error[E0308]: mismatched types
--> src/date.rs:9:61
|
9 | let rv = unsafe {
crate::generated::apr_date_parse_http(data.as_ptr() as *const i8) };
| -
^^ expected `*const u8`, found `*const i8`
| |
| arguments to this function are incorrect
|
= note: expected raw pointer `*const u8`
found raw pointer `*const i8`
note: function defined here
-->
/usr/share/cargo/registry/apr-0.1.9/target/riscv64gc-unknown-linux-gnu/debug/build/apr-b417133e16d63cef/out/generated.rs:3:153452
|
3 | ...ould be out of range or if the date is invalid."] pub fn
apr_date_parse_http (date : * const :: std :: os :: raw :: c_char) ->
apr_tim...
|
^^^
error[E0308]: mismatched types
--> src/date.rs:18:60
|
18 | let rv = unsafe {
crate::generated::apr_date_parse_rfc(data.as_ptr() as *const i8) };
|
^^ expected `*const u8`, found `*const i8`
| |
| arguments to this function are incorrect
|
= note: expected raw pointer `*const u8`
found raw pointer `*const i8`
note: function defined here
-->
/usr/share/cargo/registry/apr-0.1.9/target/riscv64gc-unknown-linux-gnu/debug/build/apr-b417133e16d63cef/out/generated.rs:3:154709
|
3 | ...would be out of range or if the date is invalid."] pub fn
apr_date_parse_rfc (date : * const :: std :: os :: raw :: c_char) ->
apr_tim...
|
^^
error[E0308]: arguments to this function are incorrect
--> src/getopt.rs:186:13
|
186 | crate::generated::apr_getopt(
|
|
note: expected `*const u8`, found `*const i8`
Bug#1074321: marked as done (createrepo-c FTBFS: error: implicit declaration of function ‘xmlCheckUTF8’)
Your message dated Fri, 28 Jun 2024 09:49:29 + with message-id and subject line Bug#1074321: fixed in createrepo-c 0.17.3-5 has caused the Debian Bug report #1074321, regarding createrepo-c FTBFS: error: implicit declaration of function ‘xmlCheckUTF8’ to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1074321: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074321 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: createrepo-c Version: 0.17.3-4 Severity: serious Tags: ftbfs patch Forwarded: https://github.com/rpm-software-management/createrepo_c/pull/402 https://buildd.debian.org/status/logs.php?pkg=createrepo-c=0.17.3-4%2Bb2 ... /<>/src/sqlite.c: In function ‘cr_sqlite3_bind_text’: /<>/src/sqlite.c:76:16: error: implicit declaration of function ‘xmlCheckUTF8’ [-Werror=implicit-function-declaration] 76 | } else if (xmlCheckUTF8((const unsigned char *) orig_content) |^~~~ ... --- End Message --- --- Begin Message --- Source: createrepo-c Source-Version: 0.17.3-5 Done: Peter Pentchev We believe that the bug you reported is fixed in the latest version of createrepo-c, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1074...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Peter Pentchev (supplier of updated createrepo-c package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 28 Jun 2024 12:28:10 +0300 Source: createrepo-c Architecture: source Version: 0.17.3-5 Distribution: unstable Urgency: medium Maintainer: RPM packaging team Changed-By: Peter Pentchev Closes: 1074321 Changes: createrepo-c (0.17.3-5) unstable; urgency=medium . * Add the const-libxml2 upstream patch to fix FTBFS with a recent version of libxml2 which now returns a pointer to a const structure. * Add the sqlite-libxml2 upstream patch to fix another GCC 13 const warning/error. Closes: #1074321 * Add the year 2024 to my debian/* copyright notice. * Use X-DH-Compat instead of debian/compat. * Let debhelper add some default dependencies automatically. * Use dpkg's default.mk in the rules file. * Reflow a rules file line for clarity. * Declare dpkg-build-api v1, drop the implied Rules-Requires-Root: no. * Use dh-package-notes to record ELF package metadata. * Refresh the Python code style of the autopkgtest runner. Checksums-Sha1: a5c4c5e680c17e2860540074f2f49fbd33ed4381 2812 createrepo-c_0.17.3-5.dsc 1f07c8ca61654c1c526a0e8c138efb4755b01d1d 11668 createrepo-c_0.17.3-5.debian.tar.xz Checksums-Sha256: 55599eb457636b785cf3fae913d2d3800bdeb2b9b884587a671ab35d29338ed4 2812 createrepo-c_0.17.3-5.dsc 0dad2790a8cc8c6e65fcbc0e53c08268cf849551c3d72994e677dd0bc8ce2c0a 11668 createrepo-c_0.17.3-5.debian.tar.xz Files: dae9e1315b526d2c144925748100e76d 2812 utils optional createrepo-c_0.17.3-5.dsc 88251e161be6e9dd7383551055bb606d 11668 utils optional createrepo-c_0.17.3-5.debian.tar.xz -BEGIN PGP SIGNATURE- iQJEBAEBCgAuFiEELuenpRf8EkzxFcNUZR7vsCUn3xMFAmZ+hMQQHHJvYW1AZGVi aWFuLm9yZwAKCRBlHu+wJSffE8y1EACzHDkNkkNy8rK2jDbyZC5C8F2l5hy+PcVr 0OaYZ9RFieODQq8TF1+bOf+CyvWUNmS6CJNu4OSQmYa8W0hwPDcZrW8pRNwVlvCg uDIhO4F4/nF4ooBG702yTj8tuHv2uGyqjjSBrwLUr7GTLBnnK/+/uc1loDLB6qSR 6P1AGaXMaEQKCVb6L5YfLB3P9ZuFF7/lLwqWoRFU6Hjj6bGyERugaJSYXpKlBFyJ 8GPifnGl19mAjSC/+f+1EmGecOwNjn0OAWZ8FQ+eoVXdpTfb58TS5ILpE/ME898v zzJOeu5rbSSiuFmv7+X7AfmyT2AKeuUpNh5izI6r5EnNs0ZfTsHnhSlReENsXsBL 4nlywVthqdQ+Fn33gKXRI+DbkAlJMLT7NH85K6vSEcZ+/BSvMqjNoaeWY+bMx5H0 HMQ6GK7XodieTB2yQGshCD/+qgDZZYqudDdZzRPh4CO7QC+M8TiUKyC8uokc+pgj i+Nvyrhwr0xNGCDMaHOZhh8DSKOT7VZkDjA0SBOOE9T9oeHbAAtEFjwktB9JMunA Z8Xi8cxC4Yt+w9ugcOwNBTHdOC3+lz+M7W43OekOrCvmXPlwrNQCbuhKH6Cdr6+I eW9ZCf1Ov5dzNKtg8IqvUMURTKne8nFFR3p3djbPgsBXSRskw+obtnKypLARR2Ei zNQD+TkYTA== =KJdu -END PGP SIGNATURE- pgp8sSYSwdZly.pgp Description: PGP signature --- End Message ---
Bug#1069488: parsinsert: FTBFS on armhf: make[1]: *** [debian/rules:30: override_dh_auto_test] Error 1
Some further results on parsinsert: after rebuilding on all release architectures, it turned out the other affected platform was armel, in addition to armhf. This suggests possibly a regression introduced by time_t migration to 64-bit size. Or this could be something else I have no clue of yet. The other architectures: amd64, arm64, i386, mips64el, ppc64el, s390x, and risv64, built all fine and would not require removal. Hope this helps, -- .''`. Étienne Mollier : :' : pgp: 8f91 b227 c7d6 f2b1 948c 8236 793c f67e 8f0d 11da `. `' sent from /dev/pts/1, please excuse my verbosity `- signature.asc Description: PGP signature
Bug#1069378: marked as done (picom: FTBFS: Package xcb-dri3 was not found in the pkg-config search path)
Your message dated Fri, 28 Jun 2024 10:30:06 +0200 with message-id <42fc6f57-2ce7-a0da-3832-39f3ea64a...@debian.org> and subject line Re: Bug#1069378: picom: FTBFS on arm64: cc: error: unrecognized command-line option '-Wunknown-warning-option' has caused the Debian Bug report #1069378, regarding picom: FTBFS: Package xcb-dri3 was not found in the pkg-config search path to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1069378: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069378 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: picom Version: 10.2-3 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-arm64 Hi, During a rebuild of all packages in sid, your package failed to build on arm64. Relevant part (hopefully): > cc (Debian 13.2.0-23) 13.2.0 > Copyright (C) 2023 Free Software Foundation, Inc. > This is free software; see the source for copying conditions. There is NO > warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. > --- > Running command: /usr/bin/cc -E -dM - > - > --- > Detecting linker via: `/usr/bin/cc -Wl,--version -Wl,-z,relro -Wl,-z,now -g > -O2 -Werror=implicit-function-declaration > -ffile-prefix-map=/<>=. -fstack-protector-strong > -fstack-clash-protection -Wformat -Werror=format-security > -mbranch-protection=standard -Wdate-time -D_FORTIFY_SOURCE=2` -> 0 > stdout: > GNU ld (GNU Binutils for Debian) 2.42 > Copyright (C) 2024 Free Software Foundation, Inc. > This program is free software; you may redistribute it under the terms of > the GNU General Public License version 3 or (at your option) a later version. > This program has absolutely no warranty. > --- > stderr: > collect2 version 13.2.0 > /usr/bin/ld -plugin /usr/libexec/gcc/aarch64-linux-gnu/13/liblto_plugin.so > -plugin-opt=/usr/libexec/gcc/aarch64-linux-gnu/13/lto-wrapper > -plugin-opt=-fresolution=/tmp/cclZVU05.res -plugin-opt=-pass-through=-lgcc > -plugin-opt=-pass-through=-lgcc_s -plugin-opt=-pass-through=-lc > -plugin-opt=-pass-through=-lgcc -plugin-opt=-pass-through=-lgcc_s --build-id > --eh-frame-hdr --hash-style=gnu --as-needed -dynamic-linker > /lib/ld-linux-aarch64.so.1 -X -EL -maarch64linux --fix-cortex-a53-843419 -pie > /usr/lib/gcc/aarch64-linux-gnu/13/../../../aarch64-linux-gnu/Scrt1.o > /usr/lib/gcc/aarch64-linux-gnu/13/../../../aarch64-linux-gnu/crti.o > /usr/lib/gcc/aarch64-linux-gnu/13/crtbeginS.o > -L/usr/lib/gcc/aarch64-linux-gnu/13 > -L/usr/lib/gcc/aarch64-linux-gnu/13/../../../aarch64-linux-gnu > -L/usr/lib/gcc/aarch64-linux-gnu/13/../../../../lib -L/lib/aarch64-linux-gnu > -L/lib/../lib -L/usr/lib/aarch64-linux-gnu -L/usr/lib/../lib > -L/usr/lib/gcc/aarch64-linux-gnu/13/../../.. --version -z relro -z now -lgcc > --push-state --as-needed -lgcc_s --pop-state -lc -lgcc --push-state > --as-needed -lgcc_s --pop-state /usr/lib/gcc/aarch64-linux-gnu/13/crtendS.o > /usr/lib/gcc/aarch64-linux-gnu/13/../../../aarch64-linux-gnu/crtn.o > --- > Sanity testing C compiler: /usr/bin/cc > Is cross compiler: False. > Sanity check compiler command line: /usr/bin/cc sanitycheckc.c -o > sanitycheckc.exe -g -O2 -Werror=implicit-function-declaration > -ffile-prefix-map=/<>=. -fstack-protector-strong > -fstack-clash-protection -Wformat -Werror=format-security > -mbranch-protection=standard -Wdate-time -D_FORTIFY_SOURCE=2 > -D_FILE_OFFSET_BITS=64 -Wl,-z,relro -Wl,-z,now > Sanity check compile stdout: > > - > Sanity check compile stderr: > > - > Running test binary command: > /<>/obj-aarch64-linux-gnu/meson-private/sanitycheckc.exe > C compiler for the build machine: /usr/bin/cc (gcc 13.2.0 "cc (Debian > 13.2.0-23) 13.2.0") > C linker for the build machine: /usr/bin/cc ld.bfd 2.42 > --- > Detecting archiver via: `gcc-ar --version` -> 0 > stdout: > GNU ar (GNU Binutils for Debian) 2.42 > Copyright (C) 2024 Free Software Foundation, Inc. > This program is free software; you may redistribute it under the terms of > the GNU General Public License version 3 or (at your option) any later > version. > This program has absolutely no warranty. > --- > Build machine cpu family: aarch64 > Build machine cpu: aarch64 > Host machine cpu family: aarch64 > Host machine cpu: aarch64 > Target machine cpu family: aarch64 > Target machine cpu: aarch64 > Program git found: NO > Running compile: > Working directory: > /<>/obj-aarch64-linux-gnu/meson-private/tmpibvj0tr_ > Code: > > #ifdef __has_include >
Bug#1072971: mesa: fails to initialize OpenGL on s390x: Unexpected format PIPE_FORMAT_X8B8G8R8_SRGB in st_new_renderbuffer_fb
Control: tag -1 -patch
On Friday, 28 June 2024 09:55:24 CEST Michel Dänzer wrote:
> > This is fixed in upstream commit 5ca85d75c05de9df7c3170122dfdb04bc795b43a
> > ("dri: Fix BGR format exclusion"), which I attached for your convenience.
>
> Beware that this commit caused a regression on little endian platfors:
>
> https://gitlab.freedesktop.org/mesa/mesa/-/issues/11398
Thanks for that. Let's remove the patch tag then.
The discussion has been reopened in the forwarded MR:
https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/29837#note_2470033
signature.asc
Description: This is a digitally signed message part.
Processed: Re: Bug#1072971: mesa: fails to initialize OpenGL on s390x: Unexpected format PIPE_FORMAT_X8B8G8R8_SRGB in st_new_renderbuffer_fb
Processing control commands: > tag -1 -patch Bug #1072971 [mesa] mesa: fails to initialize OpenGL on s390x: Unexpected format PIPE_FORMAT_X8B8G8R8_SRGB in st_new_renderbuffer_fb Removed tag(s) patch. -- 1072971: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072971 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#1073480: zstdTargets.cmake: missing targets zstd::libzstd_shared, zstd::libzstd_static, zstd::libzstd
Processing control commands: > reassign -1 src:qt6-base Bug #1073480 [libzstd-dev] zstdTargets.cmake: missing targets zstd::libzstd_shared, zstd::libzstd_static, zstd::libzstd Bug reassigned from package 'libzstd-dev' to 'src:qt6-base'. No longer marked as found in versions libzstd/1.5.6+dfsg-1. Ignoring request to alter fixed versions of bug #1073480 to the same values previously set -- 1073480: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1073480 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#1073480: zstdTargets.cmake: missing targets zstd::libzstd_shared, zstd::libzstd_static, zstd::libzstd
Processing control commands: > reassign -1 src:qt6-base Bug #1073480 [src:qt6-base] zstdTargets.cmake: missing targets zstd::libzstd_shared, zstd::libzstd_static, zstd::libzstd Ignoring request to reassign bug #1073480 to the same package -- 1073480: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1073480 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1073480: zstdTargets.cmake: missing targets zstd::libzstd_shared, zstd::libzstd_static, zstd::libzstd
control: reassign -1 src:qt6-base On Thu, Jun 27, 2024 at 11:01:44AM +0900, yokota wrote: > Hello, > > I think this bug is not a libzstd's bug but qt6-base's bug. > > Please check this QTBUG. > > [#QTBUG-119469] Targets not yet defined: zstd::libzstd_static > > https://bugreports.qt.io/browse/QTBUG-119469 > > The QTBUG said this bug was fixed in Qt 6.7.2, so update Qt to 6.7.2 > will fixes the problem. > > Or, back port QTBUG-119469 fix from git commits. > https://code.qt.io/cgit/qt/qtbase.git/log/?qt=grep=QTBUG-119469 Thanks for tracking this down! It does indeed seem to be a problem in the way QT6 internally wraps zstd's CMake targets. G'luck, Peter -- Peter Pentchev r...@ringlet.net r...@debian.org pe...@morpheusly.com PGP key:https://www.ringlet.net/roam/roam.key.asc Key fingerprint 2EE7 A7A5 17FC 124C F115 C354 651E EFB0 2527 DF13 signature.asc Description: PGP signature
Bug#1072971: mesa: fails to initialize OpenGL on s390x: Unexpected format PIPE_FORMAT_X8B8G8R8_SRGB in st_new_renderbuffer_fb
On 2024-06-28 00:28, Diederik de Haas wrote:
> Control: tag -1 upstream, fixed-upstream patch
> Control: forwarded -1 https://gitlab.freedesktop.org/mesa/mesa/-/issues/11360
> https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/29837
>
> On 14 Jun 2024 13:36:54 +0200 Emilio Pozuelo Monfort wrote:
>> Control: reassign -1 mesa 24.1.1-2
>> Control: affects -1 kuserfeedback
>> Control: retitle -1 mesa: fails to initialize OpenGL on s390x: Unexpected
>> format PIPE_FORMAT_X8B8G8R8_SRGB in st_new_renderbuffer_fb
>>
>> Actually this looks like a regression in mesa in 24.1. A few rdeps are
>> failing their autopkgtests with the same PIPE_FORMAT_X8B8G8R8_SRGB error,
>> e.g.:
>>
>> https://ci.debian.net/packages/k/kodi/testing/s390x/47675600/
>> https://ci.debian.net/packages/o/openscad/testing/s390x/47689316/
>
> This is fixed in upstream commit 5ca85d75c05de9df7c3170122dfdb04bc795b43a
> ("dri: Fix BGR format exclusion"), which I attached for your convenience.
Beware that this commit caused a regression on little endian platfors:
https://gitlab.freedesktop.org/mesa/mesa/-/issues/11398
--
Earthling Michel Dänzer| https://redhat.com
Libre software enthusiast | Mesa and Xwayland developer
Bug#1073170: marked as done (src:libabigail: fails to migrate to testing for too long: uploader built arch:all binaries)
Your message dated Fri, 28 Jun 2024 06:38:04 + with message-id and subject line Bug#1073170: fixed in libabigail 2.5-1.1 has caused the Debian Bug report #1073170, regarding src:libabigail: fails to migrate to testing for too long: uploader built arch:all binaries to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1073170: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1073170 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libabigail Version: 2.4-3 Severity: serious Control: close -1 2.5-1 Tags: sid trixie pending User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 30 days as having a Release Critical bug in testing [1]. Your package src:libabigail has been trying to migrate for 41 days [2]. Hence, I am filing this bug. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and trixie, so it doesn't affect (old-)stable. Your package is only blocked because the arch:all binary package(s) aren't built on a buildd. Unfortunately the Debian infrastructure doesn't allow arch:all packages to be properly binNMU'ed. Hence, I will shortly do a no-changes source-only upload to DELAYED/15, closing this bug. Please let me know if I should delay or cancel that upload. Paul [1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html [2] https://qa.debian.org/excuses.php?package=libabigail OpenPGP_signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: libabigail Source-Version: 2.5-1.1 Done: Paul Gevers We believe that the bug you reported is fixed in the latest version of libabigail, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1073...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Paul Gevers (supplier of updated libabigail package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 14 Jun 2024 07:20:16 +0200 Source: libabigail Architecture: source Version: 2.5-1.1 Distribution: unstable Urgency: medium Maintainer: Debian GCC Maintainers Changed-By: Paul Gevers Closes: 1073170 Changes: libabigail (2.5-1.1) unstable; urgency=medium . * Non-maintainer upload. * source only upload to enable migration (Closes: #1073170) Checksums-Sha1: 891d0e4a76d1e7c1eff04761d8a3910bead50c36 2091 libabigail_2.5-1.1.dsc 9358e0dfd0f0c2b95d892263beb902035fa78c68 4440 libabigail_2.5-1.1.debian.tar.xz Checksums-Sha256: e16fd6546d2ac1f24fa7e8b9e48bed48e6a95f98e263881296a8428a115393b5 2091 libabigail_2.5-1.1.dsc 61fe6f7178cb71275216f5ac84c3f2d47348b09fe41832c1667fc1778e0b4aa5 4440 libabigail_2.5-1.1.debian.tar.xz Files: 7a946e460bb9391c5c9dbd404bb5c0c0 2091 libs optional libabigail_2.5-1.1.dsc 55d049b19abc89a8589661d7f82be588 4440 libs optional libabigail_2.5-1.1.debian.tar.xz -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAmZr1lAACgkQnFyZ6wW9 dQooeAf+JrKnEziI8ppuJPrkyh5OyX7d13LrOgEf0LOKBg/eKPC8PBzhEU1b96OL b8iSF83CUkQTGvNtr7PSlSFOnO3gHqzJ6XhD4gp4yDgZwISFHb/FTVM+Sly8vFaV 6Pcp+vbM6CH3m0KJGuHAzOkA8u2xLJ97GTwi49l285Iqn2pwh3NoFNG00Pc6lVaF IGyT8H4jjduGRG54X+RlTKW13oC+55PdZkAJ2hcih/WBiMEuQXa4opkqoPRQhFtW fCRsmpZ3HrPMOEExYxW/PfxuiKQWptzkV5hnY9G/qpPzaPguvBMKxF8Ip/I3j5wI yXpU34288r2d9O/E5/SZMftmxg/oKg== =7FK/
Processed: Re: Bug#1074370: ffmpeg: Fails to build on armel & armhf
Processing control commands: > forwarded -1 https://trac.ffmpeg.org/ticket/11074 Bug #1074370 [src:ffmpeg] ffmpeg: Fails to build on armel & armhf Set Bug forwarded-to-address to 'https://trac.ffmpeg.org/ticket/11074'. > tags -1 upstream Bug #1074370 [src:ffmpeg] ffmpeg: Fails to build on armel & armhf Added tag(s) upstream. -- 1074370: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074370 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1074370: ffmpeg: Fails to build on armel & armhf
Control: forwarded -1 https://trac.ffmpeg.org/ticket/11074 Control: tags -1 upstream On 2024-06-28 01:40:25 +0100, Peter Green wrote: > On 27/06/2024 12:33, Jeremy Bícha wrote: > > Source: ffmpeg > > Version: 7:6.1.1-4 > > Severity: serious > > Tags: ftbfs > > User: debian-...@lists.debian.org > > Usertags: armel armhf > > X-Debbugs-CC: debian-...@lists.debian.org > > > > ffmpeg is failing to build on armel & armhf (but not arm64). This was > > noticed while rebuilding ffmpeg for the ongoing jpeg-xl 0.9 > > transition. I don't believe the build failure is related to the new > > version of jpeg-xl. The last successful official build before this was > > on June 9. > > I belive binutils has recently got stricter about assembler syntax > (see for example https://gitlab.com/postmarketOS/pmaports/-/issues/2401 ) > but given that this particular assembler involves macros, I don't feel > confident trying to fix this myself. This is also affects the 7.0.x branch. Issue reported upstream. Cheers -- Sebastian Ramacher
Processed: found 1074370 in 7:6.1.1-3
Processing commands for cont...@bugs.debian.org: > found 1074370 7:6.1.1-3 Bug #1074370 [src:ffmpeg] ffmpeg: Fails to build on armel & armhf Marked as found in versions ffmpeg/7:6.1.1-3. > thanks Stopping processing here. Please contact me if you need assistance. -- 1074370: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074370 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
