Bug#1069687: librust-bitflags-1-dev: fails to co-install
Hi Matthias, On Mon, Apr 22, 2024 at 10:34:11PM +0200, Matthias Geiger wrote: > This is the same situation as in #1040477. This is an issue wrt how we > generate the semvers. I image rust-proc-macro-crate-1 would pose the same > problem. Quoting you from 1040477: Right! > Is the only workaround dropping Ma:same here ? I see very little alternatives. We must choose: * Do not combine M-A:same + Provides: foo + Breaks: foo. * Fix dose/apt/dpkg to agree on what this means. If we were to adapt dose and apt, they's simply arrive at the conclusion that M-A:same would not work here so that really is not what you'd want here. This amounts to fixing dpkg to allow this very combination in the same way that apt and dose allow it. So yeah, changing dpkg could be an option. Ccing dpkg-devel about it. The first alternative means that we must not combine them at the same time. As we very much want M-A:same, we must not have this combination of Provides and Brekas. Keep in mind that they serve slightly different purposes. We have Breaks + Replaces and you can only replace a real package but Provides introduce a virtual package. In effect we're dealing with a package that sometimes is virtual and other times is real. We can choose different names for these uses. The real package could be renamed and also provide the virtual facility. All of them would now provide the virtual one as virtual only and none of them would have the virtual name. The Breaks and Replaces would be updated to match the real name. This may not work for the in-archive situations right now as Breaks and Replaces may still be necessary for upgrades, but it is something that may work in future situations of the same kind. In the mean time, consider that M-A:same presently is a lie. Removing it is better than continuing to lie. It's not like we must have everything in perfect multiarch. Even for cross compilation, we often can get away without M-A:same by only requiring a package for the host architecture. M-A:same is not the goal. It's a tool and way may consider using other tools. Helmut
Bug#1052197: marked as done (xrdp: after bullseye-security upgrade, empty turquoise screen after logging in)
Your message dated Tue, 23 Apr 2024 07:34:02 +0200 with message-id <1699e174995000925cc3c24e6c945...@phys.ethz.ch> and subject line xrdp: after bullseye-security upgrade, empty turquoise screen after logging in has caused the Debian Bug report #1052197, regarding xrdp: after bullseye-security upgrade, empty turquoise screen after logging in 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.) -- 1052197: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052197 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: xrdp Version: 0.9.21.1-1~deb11u1 Severity: serious Justification: does not work X-Debbugs-Cc: t...@mirbsd.de, t...@security.debian.org I’ve just upgraded the xrdp package. I had made sure to terminate the old service before the new version is started. Then, to test it, I logged in, but all I get is a window with a turquoise background, nothing on it. I *can* however see in ps(1) that my session (IceWM, kwalletcli) is started; it’s just not transmitted to rdesktop. -- System Information: Debian Release: 11.7 APT prefers oldstable-updates APT policy: (500, 'oldstable-updates'), (500, 'oldstable-security'), (500, 'oldstable-proposed-updates'), (500, 'oldoldstable-updates'), (500, 'oldoldstable-proposed-updates'), (500, 'oldoldstable'), (500, 'oldstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-25-amd64 (SMP w/4 CPU threads) Kernel taint flags: TAINT_FIRMWARE_WORKAROUND Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/lksh Init: sysvinit (via /sbin/init) Versions of packages xrdp depends on: ii adduser 3.118+deb11u1 ii init-system-helpers 1.60 ii libc62.31-13+deb11u6 ii libfuse2 2.9.9-5 ii libjpeg62-turbo 1:2.0.6-4 ii libopus0 1.3.1-0.1 ii libpam0g 1.4.0-9+deb11u1 ii libssl1.11.1.1w-0~deb11u1 ii libx11-6 2:1.7.2-1+deb11u1 ii libxfixes3 1:5.0.3-2 ii libxrandr2 2:1.5.1-1 ii lsb-base 11.1.0 ii ssl-cert 1.1.0+nmu1 Versions of packages xrdp recommends: ii fuse 2.9.9-5 ii xorgxrdp 1:0.2.15-1 Versions of packages xrdp suggests: pn guacamole Versions of packages xorgxrdp depends on: ii libc6 2.31-13+deb11u6 ii libepoxy0 1.5.5-1 pn xorg-input-abi-24 ii xserver-xorg-core [xorg-video-abi-24] 2:1.20.11-1+deb11u6 Versions of packages xorgxrdp recommends: pn xorg Versions of packages xrdp is related to: ii tightvncserver [vnc-server] 1:1.3.10-3 ii xserver-xorg-legacy 2:1.20.11-1+deb11u6 -- no debconf information --- End Message --- --- Begin Message --- yes, the bug can be closed. closing. Alex--- End Message ---
Bug#1053334: galera-4: FTBFS because of expired certificates
> What about bullseye, which is also a supported distribution? > > I have not reached the point where I want to do NMUs for these kind > of bugs, but if this were my package, I would certainly do an upload > for bullseye as well. If I can be of any help, please say so. This bug report was about Bookworm, but sure, we can do Bullseye as well. WIP at https://salsa.debian.org/otto/galera/-/commits/debian/bullseye If you want to help, you can file a MR on Salsa at any time or review existing open MRs. No need to do NMUs - the actual upload is not the work, but doing the commits and filing the stable-update bug reports to release manager.
Bug#1059245: gdm3: GDM3 fails to start on Wayland, maybe due to org.freedesktop.systemd1 failing to activate
Package: gdm3 Version: 45.0.1-3 Followup-For: Bug #1059245 Dear Maintainer, I have just had the same bug happen on a different machine after an upgrade. See attached apt history for the differences in packages before/after the issue appeared. *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? apt-get dist-upgrade * What exactly did you do (or not do) that was effective (or ineffective)? Forced Xorg, rather than Wayland (with WaylandEnable=true), but neither work, same as for the original issue. * What was the outcome of this action? GDM failed to start. * What outcome did you expect instead? GDM starts. *** End of the template - remove these template lines *** -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (990, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.6.15-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), LANGUAGE=en_AU:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages gdm3 depends on: ii accountsservice 23.13.9-6 ii adduser 3.137 ii dbus [default-dbus-system-bus]1.14.10-4 ii dbus-bin 1.14.10-4 ii dbus-daemon 1.14.10-4 ii dconf-cli 0.40.0-4+b1 ii dconf-gsettings-backend 0.40.0-4+b1 ii debconf [debconf-2.0] 1.5.86 ii gir1.2-gdm-1.045.0.1-3 ii gnome-session [x-session-manager] 45.0-2 ii gnome-session-bin 45.0-2 ii gnome-session-common 45.0-2 ii gnome-settings-daemon 46~beta-2 ii gnome-shell 44.9-1 ii gnome-terminal [x-terminal-emulator] 3.51.90-1 ii gsettings-desktop-schemas 46.0-1 ii libaccountsservice0 23.13.9-6 ii libaudit1 1:3.1.2-2 ii libc6 2.37-15 ii libcanberra-gtk3-00.30-11 ii libcanberra0 0.30-11 ii libgdk-pixbuf-2.0-0 2.42.10+dfsg-3+b1 ii libgdm1 45.0.1-3 ii libglib2.0-0 2.78.4-1 ii libglib2.0-bin2.78.4-1 ii libgtk-3-03.24.41-1 ii libgudev-1.0-0238-3 ii libkeyutils1 1.6.3-3 ii libpam-modules1.5.2-9.1+b1 ii libpam-runtime1.5.2-9.1 ii libpam-systemd [logind] 255.4-1 ii libpam0g 1.5.2-9.1+b1 ii librsvg2-common 2.54.7+dfsg-2 ii libselinux1 3.5-2 ii libsystemd0 255.4-1 ii libx11-6 2:1.8.7-1 ii libxau6 1:1.0.9-1 ii libxcb1 1.15-1 ii libxdmcp6 1:1.1.2-3 ii mutter [x-window-manager] 44.8-3 ii polkitd 124-1 ii procps2:4.0.4-4 ii systemd-sysv 255.4-1 ii ucf 3.0043+nmu1 ii x11-common1:7.7+23 ii x11-xserver-utils 7.7+10 Versions of packages gdm3 recommends: ii at-spi2-core 2.50.0-1+b1 ii desktop-base 12.0.6+nmu1 ii gnome-session [x-session-manager] 45.0-2 ii x11-xkb-utils 7.7+8 ii xserver-xephyr 2:21.1.12-1 ii xserver-xorg 1:7.7+23 ii zenity 4.0.1-1 Versions of packages gdm3 suggests: pn libpam-fprintd ii libpam-gnome-keyring 42.1-1+b2 pn libpam-pkcs11 pn libpam-sss ii orca 46.1-1 -- Configuration Files: /etc/gdm3/daemon.conf changed: [daemon] WaylandEnable=false [security] [xdmcp] [chooser] [debug] Enable=true -- debconf information: * shared/default-x-display-manager: gdm3 gdm3/daemon_name: /usr/sbin/gdm3 *** /home/shtrom/apt_history_gdm_issue.log Start-Date: 2024-04-20 20:59:25 Commandline: apt-get -y upgrade Requested-By: shtrom (1000) Upgrade: dpkg:amd64 (1.22.2, 1.22.4), fontconfig:amd64 (2.14.2-6, 2.15.0-1.1), libvulkan1:amd64 (1.3.268.0-1, 1.3.275.0-1), libvulkan1:i386 (1.3.268.0-1, 1.3.275.0-1), reportbug:amd64 (12.0.0, 13.0.1), libsvtav1enc1d1:amd64 (1.7.0+dfsg-2, 1.7.0+dfsg-2+b1), libsvtav1enc1d1:i386 (1.7.0+dfsg-2, 1.7.0+dfsg-2+b1), libbox2d2:amd64 (2.4.1-3, 2.4.1-3+b2), libgucharmap-2-90-7:amd64 (1:15.1.2-1, 1:15.1.2-1+b1), libsphinxbase3:amd64 (0.8+5prealpha+1-16+b1, 0.8+5prealpha+1-16+b2),
Bug#1069642: linux-image-6.1.0-20-amd64: kernel panic after 2024-04-20
Seeing this same issue. In my case, it ended up being caused by Crowdstrike Falcon Sensor combined with this specific kernel. Reverting the kernel or upgrading Falcon (via Falcon upgrade policy) works around this issue, for now. I think I see that 6.1.87 has attempted to fix some BHI implementation issues that were originally introduced in 6.1.85. Perhaps certain kernel modules aren't ready for this syscall hardening?
Processed: severity 1066556
Processing commands for cont...@bugs.debian.org:
> severity 1066556 normal
Bug #1066556 {Done: Andrey Rakhmatullin } [src:libdrpm]
libdrpm: FTBFS: drpm_write.c:94:20: error: implicit declaration of function
‘strlen’ [-Werror=implicit-function-declaration]
Severity set to 'normal' from 'serious'
>
End of message, stopping processing here.
Please contact me if you need assistance.
--
1066556: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066556
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1069678: marked as done (openjdk-8: CVE-2024-21011 CVE-2024-21068 CVE-2024-21085 CVE-2024-21094)
Your message dated Mon, 22 Apr 2024 23:34:17 + with message-id and subject line Bug#1069678: fixed in openjdk-8 8u412-ga-1 has caused the Debian Bug report #1069678, regarding openjdk-8: CVE-2024-21011 CVE-2024-21068 CVE-2024-21085 CVE-2024-21094 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.) -- 1069678: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069678 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: openjdk-8 X-Debbugs-CC: t...@security.debian.org Severity: grave Tags: security Hi, The following vulnerabilities were published for openjdk-8. CVE-2024-21011[0]: | Vulnerability in the Oracle Java SE, Oracle GraalVM for JDK, Oracle | GraalVM Enterprise Edition product of Oracle Java SE (component: | Hotspot). Supported versions that are affected are Oracle Java SE: | 8u401, 8u401-perf, 11.0.22, 17.0.10, 21.0.2, 22; Oracle GraalVM for | JDK: 17.0.10, 21.0.2, 22; Oracle GraalVM Enterprise Edition: | 20.3.13 and 21.3.9. Difficult to exploit vulnerability allows | unauthenticated attacker with network access via multiple protocols | to compromise Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM | Enterprise Edition. Successful attacks of this vulnerability can | result in unauthorized ability to cause a partial denial of service | (partial DOS) of Oracle Java SE, Oracle GraalVM for JDK, Oracle | GraalVM Enterprise Edition. Note: This vulnerability can be | exploited by using APIs in the specified Component, e.g., through a | web service which supplies data to the APIs. This vulnerability also | applies to Java deployments, typically in clients running sandboxed | Java Web Start applications or sandboxed Java applets, that load and | run untrusted code (e.g., code that comes from the internet) and | rely on the Java sandbox for security. CVSS 3.1 Base Score 3.7 | (Availability impacts). CVSS Vector: | (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L). CVE-2024-21068[1]: | Vulnerability in the Oracle Java SE, Oracle GraalVM for JDK, Oracle | GraalVM Enterprise Edition product of Oracle Java SE (component: | Hotspot). Supported versions that are affected are Oracle Java SE: | 8u401-perf, 11.0.22, 17.0.10, 21.0.2, 22; Oracle GraalVM for JDK: | 17.0.10, 21.0.2 and 22; Oracle GraalVM Enterprise Edition: 21.3.9. | Difficult to exploit vulnerability allows unauthenticated attacker | with network access via multiple protocols to compromise Oracle Java | SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition. | Successful attacks of this vulnerability can result in unauthorized | update, insert or delete access to some of Oracle Java SE, Oracle | GraalVM for JDK, Oracle GraalVM Enterprise Edition accessible data. | Note: This vulnerability can be exploited by using APIs in the | specified Component, e.g., through a web service which supplies data | to the APIs. This vulnerability also applies to Java deployments, | typically in clients running sandboxed Java Web Start applications | or sandboxed Java applets, that load and run untrusted code (e.g., | code that comes from the internet) and rely on the Java sandbox for | security. CVSS 3.1 Base Score 3.7 (Integrity impacts). CVSS Vector: | (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N). CVE-2024-21085[2]: | Vulnerability in the Oracle Java SE, Oracle GraalVM Enterprise | Edition product of Oracle Java SE (component: Concurrency). | Supported versions that are affected are Oracle Java SE: 8u401, | 8u401-perf, 11.0.22; Oracle GraalVM Enterprise Edition: 20.3.13 and | 21.3.9. Difficult to exploit vulnerability allows unauthenticated | attacker with network access via multiple protocols to compromise | Oracle Java SE, Oracle GraalVM Enterprise Edition. Successful | attacks of this vulnerability can result in unauthorized ability to | cause a partial denial of service (partial DOS) of Oracle Java SE, | Oracle GraalVM Enterprise Edition. Note: This vulnerability can be | exploited by using APIs in the specified Component, e.g., through a | web service which supplies data to the APIs. This vulnerability also | applies to Java deployments, typically in clients running sandboxed | Java Web Start applications or sandboxed Java applets, that load and | run untrusted code (e.g., code that comes from the internet) and | rely on the Java sandbox for security. CVSS 3.1 Base Score 3.7 | (Availability impacts). CVSS Vector: | (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L). CVE-2024-21094[3]: | Vulnerability in the Oracle Java SE, Oracle GraalVM for JDK, Oracle | GraalVM Enterprise Edition product of Oracle Java SE
Bug#1068255: marked as done (dh-python: dh_python3 loses cpython module name when renaming shared object)
Your message dated Mon, 22 Apr 2024 23:20:00 + with message-id and subject line Bug#1068255: fixed in dh-python 6.20240422 has caused the Debian Bug report #1068255, regarding dh-python: dh_python3 loses cpython module name when renaming shared object 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.) -- 1068255: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068255 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: dnf Version: 4.14.0-4.1 Severity: grave Justification: renders package unusable Dear Maintainer, I have just tried to start up dnf and it aborts with a following error: Traceback (most recent call last): File "/usr/bin/dnf", line 61, in from dnf.cli import main File "/usr/lib/python3/dist-packages/dnf/__init__.py", line 30, in import dnf.base File "/usr/lib/python3/dist-packages/dnf/base.py", line 29, in import libdnf.transaction File "/usr/lib/python3/dist-packages/libdnf/__init__.py", line 13, in from . import module File "/usr/lib/python3/dist-packages/libdnf/module.py", line 10, in from . import _module ImportError: cannot import name '_module' from partially initialized module 'libdnf' (most likely due to a circular import) (/usr/lib/python3/dist- packages/libdnf/__init__.py) Python version is 3.11.8 (python package version is 3.11.8-3+b2) -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.7.9-amd64 (SMP w/20 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages dnf depends on: ii dnf-data 4.14.0-4.1 ii libmodulemd2 2.14.0-3+b1 ii python3 3.11.8-1 ii python3-dbus 1.3.2-5+b2 ii python3-dnf 4.14.0-4.1 ii sqlite3 3.45.2-1 dnf recommends no packages. dnf suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: dh-python Source-Version: 6.20240422 Done: Stefano Rivera We believe that the bug you reported is fixed in the latest version of dh-python, 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. Stefano Rivera (supplier of updated dh-python package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 22 Apr 2024 18:40:47 -0400 Source: dh-python Architecture: source Version: 6.20240422 Distribution: unstable Urgency: medium Maintainer: Piotr Ożarowski Changed-By: Stefano Rivera Closes: 1068255 Changes: dh-python (6.20240422) unstable; urgency=medium . * Add support for Python 3.11 and 3.12 in test_interpreter. * Add generic test for the current default Python 3 interpreter in test_interpreter. * dh_python3: Don't rename _module to module. (Closes: #1068255) Checksums-Sha1: 89692657cba807639be554ff2885e32c7b350272 1688 dh-python_6.20240422.dsc 4454ca6196c0fcd2df543159f43cdcad288facf4 123072 dh-python_6.20240422.tar.xz 460673a0b438ab68ce9ac2ee346c71a2b0c72928 7466 dh-python_6.20240422_source.buildinfo Checksums-Sha256: 14e1878dcb0b617d91156b32f2a95e1e9d428feb5623c42cf6a55eb896237465 1688 dh-python_6.20240422.dsc ea14b356093827966882535d8f11155f75fbb0b51add1b366aee3d2714563e42 123072 dh-python_6.20240422.tar.xz af773c66f72a42bfc65419705395a56e60b0ee3e980568862b3269c0099103db 7466 dh-python_6.20240422_source.buildinfo Files: eedcaf3b2be0ec39491474b6d5a1d65d 1688 python optional dh-python_6.20240422.dsc 495716a0022da6923514dbfa8c2f1695 123072 python optional dh-python_6.20240422.tar.xz b5b3fa058facf2cf52eabe9f8c4c516e 7466 python optional dh-python_6.20240422_source.buildinfo -BEGIN PGP SIGNATURE- iIoEARYKADIWIQTumtb5BSD6EfafSCRHew2wJjpU2AUCZibqlRQcc3RlZmFub3JA ZGViaWFuLm9yZwAKCRBHew2wJjpU2PDAAPwOwS8Y7lQiiIIzgJmFts7ek3LsG9G2 /Xv+pNtqgHmx4AEA0B1V0KviQ0lvuZUi9cCK/mjNd7WBLouy1yDr7dr18gE= =/CnJ -END PGP SIGNATURE- pgpLdsw4V_2kq.pgp
Bug#1068255: marked as pending in dh-python
Control: tag -1 pending Hello, Bug #1068255 in dh-python 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/tools/dh-python/-/commit/5406e503c4428ae3b019f2078146a1ea2dfc2fa5 dh_python3: Don't rename _module to module. (Closes: #1068255) (this message was generated automatically) -- Greetings https://bugs.debian.org/1068255
Processed: Bug#1068255 marked as pending in dh-python
Processing control commands: > tag -1 pending Bug #1068255 [dh-python] dh-python: dh_python3 loses cpython module name when renaming shared object Added tag(s) pending. -- 1068255: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068255 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1064409: marked as done (cpdb-backend-cups build depends on cruft libcpdb-libs-backend-dev)
Your message dated Mon, 22 Apr 2024 22:49:21 + with message-id and subject line Bug#1064409: fixed in cpdb-backend-cups 2.0b5-1 has caused the Debian Bug report #1064409, regarding cpdb-backend-cups build depends on cruft libcpdb-libs-backend-dev 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.) -- 1064409: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064409 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: cpdb-backend-cups Version: 1.1.1-1 Severity: serious Tags: ftbfs trixie sid libcpdb-libs-backend-dev is no longer built by src:cpdb-libs --- End Message --- --- Begin Message --- Source: cpdb-backend-cups Source-Version: 2.0b5-1 Done: Thorsten Alteholz We believe that the bug you reported is fixed in the latest version of cpdb-backend-cups, 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. Thorsten Alteholz (supplier of updated cpdb-backend-cups 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, 20 Apr 2024 18:03:02 +0200 Source: cpdb-backend-cups Architecture: source Version: 2.0b5-1 Distribution: unstable Urgency: medium Maintainer: Thorsten Alteholz Changed-By: Thorsten Alteholz Closes: 1064409 Changes: cpdb-backend-cups (2.0b5-1) unstable; urgency=medium . * New upstream release. * debian/watch: tags are not named consistently, they might have a leading v or not * debian/control: bump standard to 4.7.0 (no changes) * debian/control: package now depends on libcpdb-backend-dev (Closes: #1064409) Checksums-Sha1: 35659a923e1c29bc118a649512f577d98f7ef22e 2273 cpdb-backend-cups_2.0b5-1.dsc 8ea71791ee2c537fa381d28728be5818bd5c05a2 33562 cpdb-backend-cups_2.0b5.orig.tar.gz 4ea81fb2e207a2141c891f20be8022aebb5d56ad 2896 cpdb-backend-cups_2.0b5-1.debian.tar.xz 963fbc352d10c678e1fd4360014fe2b4766ab1fa 9902 cpdb-backend-cups_2.0b5-1_amd64.buildinfo Checksums-Sha256: 49b3ae2fbec82ea04184e9bcc720346aa444fba183801b6533b9e546f0615f8b 2273 cpdb-backend-cups_2.0b5-1.dsc fd708620c05233c2ea21924acefe385c46fefaca3fefc1eee7b3e2b544b624bb 33562 cpdb-backend-cups_2.0b5.orig.tar.gz 31e43c294be9ae6764d6e141794028d4641f7db655ce67413f5a3b6040b63403 2896 cpdb-backend-cups_2.0b5-1.debian.tar.xz 8a652ddeb14c442d8dbaa55b82584d24e90375fc39007e4862b3b8cdab502087 9902 cpdb-backend-cups_2.0b5-1_amd64.buildinfo Files: e59afdfe308264998f255d16fa837194 2273 net optional cpdb-backend-cups_2.0b5-1.dsc a793de801849b1328d0a9678a9f3d8ab 33562 net optional cpdb-backend-cups_2.0b5.orig.tar.gz 9b34e5a7267bef055e40d7e69c23d3aa 2896 net optional cpdb-backend-cups_2.0b5-1.debian.tar.xz 8fd0ca6768b1239488a2745ca027e357 9902 net optional cpdb-backend-cups_2.0b5-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQKnBAEBCgCRFiEEYgH7/9u94Hgi6ruWlvysDTh7WEcFAmYm1mBfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDYy MDFGQkZGREJCREUwNzgyMkVBQkI5Njk2RkNBQzBEMzg3QjU4NDcTHGRlYmlhbkBh bHRlaG9sei5kZQAKCRCW/KwNOHtYR0D4D/4/lKiBtpRhzpzDXSmnahmFb6qYlxB7 eZ/MEpbeE4FleIZQcLZ7fU6tzKag1KtxRjeBioF7BPlvMU8wUVQs9DcNDidzCjSx MTqtUuKmBCZ0qVeviKXkUcXUQjoi92/uLbTNr3hePis9F9jgOtEGUXo+oHgEE8g7 uZqRHPIV6M3ZEE9LyqpWyJOZYvxXNr6sWiub5h34IpwsZl0YRBjWaivgIYPBiPgS 24FqHRD4a7lmFPI/j+SjsImJlGNxNPpu7fR20O1+t+RZ1YdAF0Y7b9Fm4OMFZ6On UMlLgtAioj/HgUyrfEwiIx0R3+kNcmQkyiLZfN0t7OALWZVdWPO/tJlh9j4bzMYC oogPf9m9A6r6TWU5shjV2VcpA21GTK3cBn7latAOmq/4S7qPjiFVnDX+1b+A4N9D LUpqrBhxoVinJh+WGgy1CyGn+++DYtyMqoBAvJvMQptYOQKsYgedYKz3cDx8FEAs uSmPlZEhCDzZIOPqWBprAILFyi5aSmnIYUptXfdyyRuaIldoyX+8Sb5uT29SBIVu kxNoXCnfgCJbbWrXBfLYE/fl5tQqmyNk0JULyk0lhyUXsz5IfMCXuN0U3Kd9QSj0 /YdCyApEpDvtCyEw3iz1pP1NTEWUhEqHQW91kBe/ARO0O9hoH22S/BAPT7tXasOr ll5n/3ky8cNPvw== =uRP1 -END PGP SIGNATURE- pgpFmDSKe7bad.pgp Description: PGP signature --- End Message ---
Bug#1069678: openjdk-8: CVE-2024-21011 CVE-2024-21068 CVE-2024-21085 CVE-2024-21094
tags 1069678 + pending thanks I’m working on it. Upload should come RSN. AIUI the security team can feel free to ignore openjdk-8 as it’s in sid for bootstrapping and preparing ELTS upgrades and downstreams purposes, and not “as is” security-supported in Debian, so if it helps lowering the workload…
Processed: Re: Bug#1069678: openjdk-8: CVE-2024-21011 CVE-2024-21068 CVE-2024-21085 CVE-2024-21094
Processing commands for cont...@bugs.debian.org: > tags 1069678 + pending Bug #1069678 [src:openjdk-8] openjdk-8: CVE-2024-21011 CVE-2024-21068 CVE-2024-21085 CVE-2024-21094 Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 1069678: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069678 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1058047: marked as done (gammapy: FTBFS with Python 3.12)
Your message dated Mon, 22 Apr 2024 22:24:15 +
with message-id
and subject line Bug#1058047: fixed in gammapy 1.1-4
has caused the Debian Bug report #1058047,
regarding gammapy: FTBFS with Python 3.12
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1058047: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058047
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gammapy
Version: 1.1-3
Severity: serious
Tags: ftbfs
User: debian-pyt...@lists.debian.org
Usertags: python3.12
Hi Maintainer
gammapy FTBFS [1] with Python 3.12 as a supported version. I've
copied what I hope is the relevant part of the log below.
Regards
Graham
[1] https://buildd.debian.org/status/package.php?p=gammapy
=== FAILURES ===
_ test_parameter_name __
def test_parameter_name():
with pytest.raises(RuntimeError):
> class MyTestModel:
gammapy/modeling/models/tests/test_core.py:256:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
self = Parameter(name='wrong-name', value=3.0, factor=3.0, scale=1.0,
unit=Unit(dimensionless), min=nan, max=nan, frozen=False,
id=0x8e307aa0)
owner = .MyTestModel'>
name = 'par'
def __set_name__(self, owner, name):
if not self._name == name:
> raise ValueError(f"Expected parameter name '{name}', got
> {self._name}")
E ValueError: Expected parameter name 'par', got wrong-name
E Error calling __set_name__ on 'Parameter' instance 'par'
in 'MyTestModel'
gammapy/modeling/parameter.py:165: ValueError
--- End Message ---
--- Begin Message ---
Source: gammapy
Source-Version: 1.1-4
Done: Ole Streicher
We believe that the bug you reported is fixed in the latest version of
gammapy, 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 1058...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Ole Streicher (supplier of updated gammapy package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Mon, 22 Apr 2024 12:06:01 +0200
Source: gammapy
Architecture: source
Version: 1.1-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Astro Team
Changed-By: Ole Streicher
Closes: 1058047
Changes:
gammapy (1.1-4) unstable; urgency=medium
.
* Python 3.12 tests and configs (Closes: #1058047)
Checksums-Sha1:
9d0fd68c009c1ea374252649a459e053fd837e1b 2445 gammapy_1.1-4.dsc
4cfe7023951f8d953a6ae7bceafd293bccdca892 9520 gammapy_1.1-4.debian.tar.xz
Checksums-Sha256:
5e6d1f1e24a6e4df529e75c0f403dfcf4f4f77f3ff99a2e5bd6a221ba2369de0 2445
gammapy_1.1-4.dsc
d362ebcdae95934f5626d556903541313ed05388e27b5dd0f4ed6967d8a3b8b6 9520
gammapy_1.1-4.debian.tar.xz
Files:
2e796151f4f6b779421c65420db5ff97 2445 python optional gammapy_1.1-4.dsc
514bac02d7c6aced8cb9f3e7c309a432 9520 python optional
gammapy_1.1-4.debian.tar.xz
-BEGIN PGP SIGNATURE-
iQIzBAEBCgAdFiEE7/BpV0Ra2/h0L3qtmk9WvbkOGL0FAmYmyjAACgkQmk9WvbkO
GL0mgw//arKdzXHjQCKTpVXTiOl0A6m5OSfTtqNJyMZg1mWN1oYs+zqid7eZByPG
LxyODLX1WbNHx21srrYKWytQVAR9mx3fWHIaviztmLVjlaciIwkpXk8gBNjN091R
9yXI5PPArChpQlUA3ikL/Y+/yffdhnkN4AefqcAs/5qMzw0/YkrQyEKVZof8rPAK
Eiwtcfns5S4/r2o5XMoUoaqdf2O/9gLdNwPzHJu8b4YfYL2+5mJiNLOCeO4yH+ji
pIgWJic21vCXd2gwPgV9DwlNaCxRix9UNPKOB0hat2PWYAyB0sm/a0rZpHYp3thM
LolZ/CuEutfMx30z532oLQmLnF1UAHozJgC2GyoDDawdD3mpE7FSAMkqeSDL8HDS
mmsqWf5+3hF9HAOq2LVv48Jmpqk76t2TOKhpM+dTQ+6XHew8eSdJu73ennT3pdx1
5rz1JXODRB8u3nCPuFxZwTgpoX2zkEM3mEQ/eM6Drd+9BUnhfl9EZp/2PRz+N/GO
YZY+H1zwsaUcpT8LV9//GRE7SLgA7jd70fBoRFJ1vdPrQStT4stvdfA/xwCNef8l
brCOOFcrqpEH7MPINoyYZ0JtJVDiijYdNfHJzd+iP/Ju8e4dGiE/t/wuNVOZC4k3
1m4aIe4Uo05eMmSDjY4UnrMZtqOcr/azNG8JFCmbmW2dWb+hUQA=
=QUTw
-END PGP SIGNATURE-
pgp_P6MyBJcmC.pgp
Description: PGP signature
--- End Message ---
Bug#1069371: marked as done (hugo: FTBFS on arm64: make[1]: *** [debian/rules:89: override_dh_auto_build] Error 25)
Your message dated Mon, 22 Apr 2024 22:04:38 + with message-id and subject line Re: hugo: FTBFS on arm64: make[1]: *** [debian/rules:89: override_dh_auto_build] Error 25 has caused the Debian Bug report #1069371, regarding hugo: FTBFS on arm64: make[1]: *** [debian/rules:89: override_dh_auto_build] Error 25 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1069371: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069371 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: hugo Version: 0.124.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): > make[1]: Entering directory '/<>' > go is /usr/bin/go > go version go1.22.2 linux/arm64 > dh_auto_build -- -ldflags '-X > "github.com/gohugoio/hugo/common/hugo.buildDate=2024-03-25T03:00:41Z" -X > "github.com/gohugoio/hugo/common/hugo.vendorInfo=debian:0.124.1-1"' -tags > 'dev extended' > cd _build && go install -trimpath -v -p 4 -ldflags "-X > \"github.com/gohugoio/hugo/common/hugo.buildDate=2024-03-25T03:00:41Z\" -X > \"github.com/gohugoio/hugo/common/hugo.vendorInfo=debian:0.124.1-1\"" -tags > "dev extended" github.com/gohugoio/hugo github.com/gohugoio/hugo/bufferpool > github.com/gohugoio/hugo/cache github.com/gohugoio/hugo/cache/dynacache > github.com/gohugoio/hugo/cache/filecache github.com/gohugoio/hugo/codegen > github.com/gohugoio/hugo/commands github.com/gohugoio/hugo/common > github.com/gohugoio/hugo/common/collections > github.com/gohugoio/hugo/common/constants > github.com/gohugoio/hugo/common/hcontext > github.com/gohugoio/hugo/common/herrors github.com/gohugoio/hugo/common/hexec > github.com/gohugoio/hugo/common/hreflect > github.com/gohugoio/hugo/common/hstrings > github.com/gohugoio/hugo/common/htime github.com/gohugoio/hugo/common/hugio > github.com/gohugoio/hugo/common/hugo github.com/gohugoio/hugo/common/loggers > github.com/gohugoio/hugo/common/maps github.com/gohugoio/hugo/common/math > github.com/gohugoio/hugo/common/para github.com/gohugoio/hugo/common/paths > github.com/gohugoio/hugo/common/predicate > github.com/gohugoio/hugo/common/rungroup > github.com/gohugoio/hugo/common/terminal github.com/gohugoio/hugo/common/text > github.com/gohugoio/hugo/common/types > github.com/gohugoio/hugo/common/types/css > github.com/gohugoio/hugo/common/types/hstring > github.com/gohugoio/hugo/common/urls github.com/gohugoio/hugo/compare > github.com/gohugoio/hugo/config github.com/gohugoio/hugo/config/allconfig > github.com/gohugoio/hugo/config/privacy > github.com/gohugoio/hugo/config/security > github.com/gohugoio/hugo/config/services > github.com/gohugoio/hugo/config/testconfig github.com/gohugoio/hugo/create > github.com/gohugoio/hugo/create/skeletons github.com/gohugoio/hugo/deploy > github.com/gohugoio/hugo/deploy/deployconfig github.com/gohugoio/hugo/deps > github.com/gohugoio/hugo/docshelper github.com/gohugoio/hugo/helpers > github.com/gohugoio/hugo/htesting github.com/gohugoio/hugo/htesting/hqt > github.com/gohugoio/hugo/hugofs github.com/gohugoio/hugo/hugofs/files > github.com/gohugoio/hugo/hugofs/glob github.com/gohugoio/hugo/hugolib > github.com/gohugoio/hugo/hugolib/doctree > github.com/gohugoio/hugo/hugolib/filesystems > github.com/gohugoio/hugo/hugolib/paths > github.com/gohugoio/hugo/hugolib/segments github.com/gohugoio/hugo/identity > github.com/gohugoio/hugo/identity/identitytesting > github.com/gohugoio/hugo/langs github.com/gohugoio/hugo/langs/i18n > github.com/gohugoio/hugo/lazy github.com/gohugoio/hugo/livereload > github.com/gohugoio/hugo/markup github.com/gohugoio/hugo/markup/asciidocext > github.com/gohugoio/hugo/markup/asciidocext/asciidocext_config > github.com/gohugoio/hugo/markup/asciidocext/internal > github.com/gohugoio/hugo/markup/blackfriday > github.com/gohugoio/hugo/markup/converter > github.com/gohugoio/hugo/markup/converter/hooks > github.com/gohugoio/hugo/markup/goldmark > github.com/gohugoio/hugo/markup/goldmark/codeblocks > github.com/gohugoio/hugo/markup/goldmark/goldmark_config > github.com/gohugoio/hugo/markup/goldmark/images > github.com/gohugoio/hugo/markup/goldmark/internal/extensions/attributes > github.com/gohugoio/hugo/markup/goldmark/internal/render > github.com/gohugoio/hugo/markup/highlight > github.com/gohugoio/hugo/markup/highlight/chromalexers > github.com/gohugoio/hugo/markup/internal >
Bug#1064613: vtun: Segmentation fault with default config
On Sat, 24 Feb 2024 23:55:18 + =?utf-8?q?Lucas_L=C3=B3pez?=
wrote:
I copied the example server file /usr/share/doc/vtun/examples/vtund-server.conf
into
/etc/vtund.conf and enabled server mode in /etc/default/vtun. When I start the
service
with systemctl I get the following error on the dmesg log:
[343358.769324] vtund[3002]: segfault at 0 ip 5572cac05e34 sp
7ffc9a47f610 error 4 in vtund[5572cabff000+b000] likely on CPU 0 (core 0,
socket 0)
[343358.769342] Code: 24 10 e8 2f 96 ff ff 85 c0 0f 88 0d 01 00 00 48 8b 44 24 10 48
89 44 24 08 48 85 c0 0f 84 f0 00 00 00 48 89 c3 90 48 8b 6b 18 <66> 44 39 7d 00
0f 85 d1 00 00 00 48 8b 73 08 4c 89 ef e8 55 97 ff
I checked the config and the manual but I haven't been able to use the package
due to the segfault.
BTW, the autogenerated systemd unit has the attributes RemainAfterExit=yes,
SuccessExitStatus=5 6,
so even on failure the unit appears as "active (exited)". Hence it needs a
"systemctl restart",
"systemctl start" won't do anything which is a bit counterintuitive.
Hello,
I am not the maintainer of vtun, just tried to find some more informations
about the crash.
I was not able to reproduce it inside a minimal VM, but I think
from the dmesg lines it happened in netlib.c line 156.
This looks like ifa->ifa_addr is no valid pointer but gets dereferenced.
I guess it might be related to the network configuration of this specific host,
maybe containing an interface without having an address assigned.
Kind regards,
Bernhard
148 int getifaddr(struct sockaddr_storage *addr, char * ifname, sa_family_t
af)
...
154
155 for (ifa = ifas; ifa; ifa = ifa->ifa_next) {
156 if( ifa->ifa_addr->sa_family != af ||
157strcmp(ifname, ifa->ifa_name) )
https://sources.debian.org/src/vtun/3.0.4-2/netlib.c/#L156
https://man7.org/linux/man-pages/man3/getifaddrs.3.html
# 2024-04-22 Trixie/testing amd64 qemu VM
apt update
apt install systemd-coredump mc htop gdb
# with unstable
apt install vtun vtun-dbgsym devscripts
apt build-dep vtun
mkdir /home/benutzer/source/vtun/orig -p
cd/home/benutzer/source/vtun/orig
dget
https://snapshot.debian.org/archive/debian-debug/20191112T220504Z/pool/main/v/vtun/vtun_3.0.4-2.dsc
dpkg-source -x vtun_3.0.4-2.dsc
cp -a /usr/share/doc/vtun/examples/vtund-server.conf /etc/vtund.conf
cp -a /etc/default/vtun /etc/default/vtun.orig
sed -i 's/# RUN_SERVER=no/RUN_SERVER=yes/g' /etc/default/vtun
wget
https://snapshot.debian.org/archive/debian/20220514T093947Z/pool/main/v/vtun/vtun_3.0.4-2%2Bb1_amd64.deb
wget
https://snapshot.debian.org/archive/debian-debug/20220514T091215Z/pool/main/v/vtun/vtun-dbgsym_3.0.4-2%2Bb1_amd64.deb
dpkg -i *.deb
systemctl start vtun.service
-> Could not reproduce the crash
[343358.769324] vtund[3002]: segfault at 0 ip 5572cac05e34 sp
7ffc9a47f610 error 4 in vtund[5572cabff000+b000] likely on CPU 0 (core 0,
socket 0)
[343358.769342] Code: 24 10 e8 2f 96 ff ff 85 c0 0f 88 0d 01 00 00 48 8b 44 24
10 48 89 44 24 08 48 85 c0 0f 84 f0 00 00 00 48 89 c3 90 48 8b 6b 18 <66> 44 39
7d 00 0f 85 d1 00 00 00 48 8b 73 08 4c 89 ef e8 55 97 ff
# https://wiki.debian.org/InterpretingKernelOutputAtProcessCrash
error 4
0b0100
* bit 0 ==0: no page found
* bit 1 ==0: read access
* bit 2 ==1: user-mode access
echo -n "find /b ..., ..., 0x" && \
echo "24 10 e8 2f 96 ff ff 85 c0 0f 88 0d 01 00 00 48 8b 44 24 10 48 89 44 24
08 48 85 c0 0f 84 f0 00 00 00 48 89 c3 90 48 8b 6b 18 <66> 44 39 7d 00 0f 85 d1
00 00 00 48 8b 73 08 4c 89 ef e8 55 97 ff" \
| sed 's/[<>]//g' | sed 's/ /, 0x/g'
gdb -q --pid $(pgrep vtund)
(gdb) pipe info target | grep -E ".text$"
0x55c1fbd0f7f0 - 0x55c1fbd19ba1 is .text
(gdb) find /b 0x55c1fbd0f7f0, 0x55c1fbd19ba1, 0x24, 0x10, 0xe8, 0x2f,
0x96, 0xff, 0xff, 0x85, 0xc0, 0x0f, 0x88, 0x0d, 0x01, 0x00, 0x00, 0x48, 0x8b,
0x44, 0x24, 0x10, 0x48, 0x89, 0x44, 0x24, 0x08, 0x48, 0x85, 0xc0, 0x0f, 0x84,
0xf0, 0x00, 0x00, 0x00, 0x48, 0x89, 0xc3, 0x90, 0x48, 0x8b, 0x6b, 0x18, 0x66,
0x44, 0x39, 0x7d, 0x00, 0x0f, 0x85, 0xd1, 0x00, 0x00, 0x00, 0x48, 0x8b, 0x73,
0x08, 0x4c, 0x89, 0xef, 0xe8, 0x55, 0x97, 0xff
0x55c1fbd15e0a
1 pattern found.
(gdb) b * (0x55c1fbd15e0a + 42)
Breakpoint 1 at 0x55c1fbd15e34: file ./netlib.c, line 156.
(gdb) info b
Num Type Disp Enb AddressWhat
1 breakpoint keep y 0x55c1fbd15e34 in getifaddr at
./netlib.c:156
(gdb) disassemble /r 0x55c1fbd15e0a, 0x55c1fbd15e0a + 62
Dump of assembler code from 0x55c1fbd15e0a to 0x55c1fbd15e48:
0x55c1fbd15e0a : 24 10 and$0x10,%al
0x55c1fbd15e0c : e8 2f 96 ff ff call
0x55c1fbd0f440
0x55c1fbd15e11 : 85 c0 test %eax,%eax
0x55c1fbd15e13 : 0f 88 0d 01 00 00 js
0x55c1fbd15f26
0x55c1fbd15e19 : 48 8b 44 24 10 mov
0x10(%rsp),%rax
0x55c1fbd15e1e : 48 89 44 24 08
Bug#1066113: marked as done (guix: CVE-2024-27297)
Your message dated Mon, 22 Apr 2024 21:02:37 + with message-id and subject line Bug#1066113: fixed in guix 1.2.0-4+deb11u2 has caused the Debian Bug report #1066113, regarding guix: CVE-2024-27297 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.) -- 1066113: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066113 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: guix Version: 1.4.0-5 Severity: important Tags: security upstream X-Debbugs-Cc: car...@debian.org, Debian Security Team Control: found -1 1.2.0-4+deb11u1 Hi, Vagrant, knowing that you are awaere already, but filling for having a Debian bug tracking reference. The following vulnerability was published for guix. CVE-2024-27297[0]: | Nix is a package manager for Linux and other Unix systems. A fixed- | output derivations on Linux can send file descriptors to files in | the Nix store to another program running on the host (or another | fixed-output derivation) via Unix domain sockets in the abstract | namespace. This allows to modify the output of the derivation, after | Nix has registered the path as "valid" and immutable in the Nix | database. In particular, this allows the output of fixed-output | derivations to be modified from their expected content. This issue | has been addressed in versions 2.3.18 2.18.2 2.19.4 and 2.20.5. | Users are advised to upgrade. There are no known workarounds for | this vulnerability. If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2024-27297 https://www.cve.org/CVERecord?id=CVE-2024-27297 [1] https://git.savannah.gnu.org/cgit/guix.git/commit/?id=8f4ffb3fae133bb21d7991e97c2f19a7108b1143 Please adjust the affected versions in the BTS as needed. Regards, Salvatore --- End Message --- --- Begin Message --- Source: guix Source-Version: 1.2.0-4+deb11u2 Done: Vagrant Cascadian We believe that the bug you reported is fixed in the latest version of guix, 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. Vagrant Cascadian (supplier of updated guix 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: Wed, 17 Apr 2024 15:39:38 -0700 Source: guix Architecture: source Version: 1.2.0-4+deb11u2 Distribution: bullseye-security Urgency: medium Maintainer: Vagrant Cascadian Changed-By: Vagrant Cascadian Closes: 1066113 Changes: guix (1.2.0-4+deb11u2) bullseye-security; urgency=medium . * debian/patches: guix-daemon: Protect against file descriptor escape when building fixed-output derivations (CVE-2024-27297). (Closes: #1066113) Checksums-Sha1: 28b4569f128da111e30db1dd880c7553a157522a 1810 guix_1.2.0-4+deb11u2.dsc 9245bd579c15a089fecb4fde0d9e2fc43af4e0fa 30564986 guix_1.2.0.orig.tar.gz e34806e9aef744309a6901ee70299b96a25f455c 833 guix_1.2.0.orig.tar.gz.asc 881577cdea7ff9de3e8107faf37e8753e2fac35f 40996 guix_1.2.0-4+deb11u2.debian.tar.xz 057d4000fdbf4bf010fc1d60c39ba1a90caca163 10498 guix_1.2.0-4+deb11u2_amd64.buildinfo Checksums-Sha256: 365f2076c2f421edc202522f146b79df4b3a3797a5eb25790ef9222c6f00458e 1810 guix_1.2.0-4+deb11u2.dsc 5ecdf7ced25b1fb0ca7c57e794b7b60c8a7adcb15261dec2af37925c838c6d74 30564986 guix_1.2.0.orig.tar.gz e278e3aba3fe9acd35aa6586933d940f0c847ccfb6d1370cb5c4f754732d2fb6 833 guix_1.2.0.orig.tar.gz.asc 05e9b181607c3e07a65f43223a2c600651ec8b32fbe6faf0db895d339576e158 40996 guix_1.2.0-4+deb11u2.debian.tar.xz 14ecbba7b1bf646546d99ec53e727e3664c10c21d43d34f3ad068d1647bcedb1 10498 guix_1.2.0-4+deb11u2_amd64.buildinfo Files: e685bc2cbdcb0a9172008a20ef634536 1810 admin optional guix_1.2.0-4+deb11u2.dsc f11073e551eaf9ae7119cd90671c0d90 30564986 admin optional guix_1.2.0.orig.tar.gz bbed756aaf1d8303a14cc9b5fdc05066 833 admin optional guix_1.2.0.orig.tar.gz.asc d09141d2b754aff550b959148df45994 40996 admin optional guix_1.2.0-4+deb11u2.debian.tar.xz fbe95bfe922c77ccbace88ff1eb1b089 10498 admin optional
Bug#1069603: [Pkg-openssl-devel] Bug#1069603: Bug#1069603: openssl breaks libcrypt-smime-perl autopkgtest: Crypt::SMIME#setPublicKeyStore: failed to store the public cert
On 2024-04-21 19:30:21 [+0200], Paul Gevers wrote: > Hi Hi, > > Could britney be hinted to migrate both at the same time? This should > > solve the issue you pointed out. > > There is no "please test together" knob if that's what you mean (is that > what you mean?). Yes, it is/ was. > I have triggered the test manually, so for now the lights > are green. Because those expire, I have added a hint to ignore the failure > of the old version in testing. Okay, thank you. In general I would poke the release team once I would expect it to migrate but didn't. But give the current events, I just waited until something happens. > Paul Sebastian
Bug#1069689: marked as done (mandos lost mandos.service systemd unit)
Your message dated Mon, 22 Apr 2024 20:41:16 + with message-id and subject line Bug#1069689: fixed in mandos 1.8.16-1.2 has caused the Debian Bug report #1069689, regarding mandos lost mandos.service systemd unit 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.) -- 1069689: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069689 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: mandos Version: 1.8.16-1.1 Severity: serious Tags: patch Justification: prevent testing migration after unintentional deletion of systemd unit X-Debbugs-Cc: Bastian Germann User: helm...@debian.org Usertags: dep17p6 The last mandos upload is the first after systemd.pc having moved systemdsystemunitdir from /lib to /usr/lib. mandos' upstream Makefile uses this to see where to install units to, but it also only does that if the relevant directory exists. Now since the new location wasn't created, it ceased installing the unit. We need to create the new location to reinstate the unit. Patch attached. I think the loss of the unit is unintantional and for that reason file this as rc bug. Please adjust if you disagree. This change makes mandos backports-unsafe. I don't expect mandos to be backported. Helmut diff --minimal -Nru mandos-1.8.16/debian/changelog mandos-1.8.16/debian/changelog --- mandos-1.8.16/debian/changelog 2024-04-19 13:08:30.0 +0200 +++ mandos-1.8.16/debian/changelog 2024-04-22 21:13:43.0 +0200 @@ -1,3 +1,10 @@ +mandos (1.8.16-1.2) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Install mandos.service again. (Closes: #-1) + + -- Helmut Grohne Mon, 22 Apr 2024 21:13:43 +0200 + mandos (1.8.16-1.1) unstable; urgency=medium * Non-maintainer upload. diff --minimal -Nru mandos-1.8.16/debian/mandos.dirs mandos-1.8.16/debian/mandos.dirs --- mandos-1.8.16/debian/mandos.dirs2019-08-18 21:51:02.0 +0200 +++ mandos-1.8.16/debian/mandos.dirs2024-04-22 21:13:43.0 +0200 @@ -5,6 +5,6 @@ etc/dbus-1/system.d usr/sbin var/lib/mandos -lib/systemd/system usr/lib/tmpfiles.d usr/lib/sysusers.d +usr/lib/systemd/system --- End Message --- --- Begin Message --- Source: mandos Source-Version: 1.8.16-1.2 Done: Helmut Grohne We believe that the bug you reported is fixed in the latest version of mandos, 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. Helmut Grohne (supplier of updated mandos package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 22 Apr 2024 21:13:43 +0200 Source: mandos Architecture: source Version: 1.8.16-1.2 Distribution: unstable Urgency: medium Maintainer: Mandos Maintainers Changed-By: Helmut Grohne Closes: 1069689 Changes: mandos (1.8.16-1.2) unstable; urgency=medium . * Non-maintainer upload. * Install mandos.service again. (Closes: #1069689) Checksums-Sha1: 11bf2e6eca9e8b4b00dd291e8ec1c9f61b843a7e 2109 mandos_1.8.16-1.2.dsc 6c307b5de6e076342698778e0204baf994619bf1 27396 mandos_1.8.16-1.2.debian.tar.xz 1fc879f36397562756ed95ea9e285b529a3f8a94 8182 mandos_1.8.16-1.2_source.buildinfo Checksums-Sha256: 419b91693f9462c00b16c922030a15457512727adf2b3801b2a5a61dbfae325b 2109 mandos_1.8.16-1.2.dsc 29e61d0d74e5483b4928e24fff694efe5d563926f23666192c0e91380b87847a 27396 mandos_1.8.16-1.2.debian.tar.xz 5d75fb83bcfe8b9a4c6e5eb6b646d8453310d3930baf8df50d0319f6ea3b03f6 8182 mandos_1.8.16-1.2_source.buildinfo Files: 38c1b5db1b7f5cca4984fee280ab7311 2109 admin optional mandos_1.8.16-1.2.dsc f29ddd3f5ac291d9722f65800048d4fd 27396 admin optional mandos_1.8.16-1.2.debian.tar.xz 8e5a11b1c3800307fd29c304184d8aae 8182 admin optional mandos_1.8.16-1.2_source.buildinfo -BEGIN PGP SIGNATURE- iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmYmwm4QHGJhZ2VAZGVi aWFuLm9yZwAKCRAfXHqLRVZDFES6DAD2YTKRldJKagpAT4u5qlfhvWuxnZNuD1SA LcbTbmDDo7PqpVxMj+xG27hja5P0078e/zB8qCNpOQrDbAnCQXHiC92l3GTqlOLE 2Bg4rcx3rhvSc+vwTzrtUAdtKub79slEvYDzCQTaUDG8crotIWn1lrMCuFbwSBPE yIqy+I7g/XYTgTKibFn8jtXeDtZM4KK4I94gRiUcnS8opHgE68wEuInWHTe3gvJy
Bug#1066113: marked as done (guix: CVE-2024-27297)
Your message dated Mon, 22 Apr 2024 20:34:14 + with message-id and subject line Bug#1066113: fixed in guix 1.4.0-3+deb12u1 has caused the Debian Bug report #1066113, regarding guix: CVE-2024-27297 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.) -- 1066113: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066113 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: guix Version: 1.4.0-5 Severity: important Tags: security upstream X-Debbugs-Cc: car...@debian.org, Debian Security Team Control: found -1 1.2.0-4+deb11u1 Hi, Vagrant, knowing that you are awaere already, but filling for having a Debian bug tracking reference. The following vulnerability was published for guix. CVE-2024-27297[0]: | Nix is a package manager for Linux and other Unix systems. A fixed- | output derivations on Linux can send file descriptors to files in | the Nix store to another program running on the host (or another | fixed-output derivation) via Unix domain sockets in the abstract | namespace. This allows to modify the output of the derivation, after | Nix has registered the path as "valid" and immutable in the Nix | database. In particular, this allows the output of fixed-output | derivations to be modified from their expected content. This issue | has been addressed in versions 2.3.18 2.18.2 2.19.4 and 2.20.5. | Users are advised to upgrade. There are no known workarounds for | this vulnerability. If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2024-27297 https://www.cve.org/CVERecord?id=CVE-2024-27297 [1] https://git.savannah.gnu.org/cgit/guix.git/commit/?id=8f4ffb3fae133bb21d7991e97c2f19a7108b1143 Please adjust the affected versions in the BTS as needed. Regards, Salvatore --- End Message --- --- Begin Message --- Source: guix Source-Version: 1.4.0-3+deb12u1 Done: Vagrant Cascadian We believe that the bug you reported is fixed in the latest version of guix, 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. Vagrant Cascadian (supplier of updated guix 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: Wed, 17 Apr 2024 14:23:27 -0700 Source: guix Architecture: source Version: 1.4.0-3+deb12u1 Distribution: bookworm-security Urgency: medium Maintainer: Vagrant Cascadian Changed-By: Vagrant Cascadian Closes: 1066113 Changes: guix (1.4.0-3+deb12u1) bookworm-security; urgency=medium . * debian/patches: guix-daemon: Protect against file descriptor escape when building fixed-output derivations (CVE-2024-27297). (Closes: #1066113) Checksums-Sha1: 1575901846c9f03abed91fff6281294f998f07a7 1893 guix_1.4.0-3+deb12u1.dsc 0d36f7907db883b775b2e4bf5a527ba59ee6778a 40563275 guix_1.4.0.orig.tar.gz 8e6b53fee0cc17a0c302432a89386017850bbbdf 833 guix_1.4.0.orig.tar.gz.asc 7c538b9dc13c6b54a2e795e02c84fe44872b0a2c 59800 guix_1.4.0-3+deb12u1.debian.tar.xz 24efc6808dc59cea517e45fae50713837fe2b044 11054 guix_1.4.0-3+deb12u1_amd64.buildinfo Checksums-Sha256: a4419520bb5829aa2ce25ee4e809e154d84ed98456b6b7c5d97f8a44b6499156 1893 guix_1.4.0-3+deb12u1.dsc 43c769cbf632ef05449ac1fa48c1ba152c33494c6abc7e47137bba7b2149f8a4 40563275 guix_1.4.0.orig.tar.gz b30c7e63048c3fe4e72d6146f107e55e27d1ea1eb5bc7fd8818f20a1a32c8e10 833 guix_1.4.0.orig.tar.gz.asc e716f6f46e3185404a247f125e3add8b44252d337df87063f95f08eb95032bee 59800 guix_1.4.0-3+deb12u1.debian.tar.xz 43e5f9fe33c0142c2fa8a084258192224c2ef7d9262988e0d95a03f1c5b87bd6 11054 guix_1.4.0-3+deb12u1_amd64.buildinfo Files: 2f2cfa48595274d40bfb4d3739b1c69f 1893 admin optional guix_1.4.0-3+deb12u1.dsc 740b0afa9a9eac622ea5fecc06737429 40563275 admin optional guix_1.4.0.orig.tar.gz 8c6f80b9dfbb77bb656b3e0f5187baa7 833 admin optional guix_1.4.0.orig.tar.gz.asc 846aab762bf3898373cabf643096089d 59800 admin optional guix_1.4.0-3+deb12u1.debian.tar.xz f9f74f69d2f560722f74348a028873c5 11054 admin optional
Bug#1069687: librust-bitflags-1-dev: fails to co-install
On Mon, 22 Apr 2024 21:01:22 +0200 Helmut Grohne wrote: > Package: librust-bitflags-1-dev > Version: 1.3.2-5+b1 > Severity: serious > Justification: causes an installation failure > > Hi, > > Attempting to install librust-bitflags-1-dev for multiple architectures > fails, because apt and dpkg disagree about how breaks and provides work. > apt thinks that self-breaks can be ignored, but dpkg thinks that since > librust-bitflags-1-dev breaks+provides librust-bitflags-1.3.2-dev it > cannot be coinstalled and gives up. You cannot combine such > breaks+provides with m-a:same. The simplest workaround here is dropping > m-a:same as it cannot be exercised anyway. > > Helmut This is the same situation as in #1040477. This is an issue wrt how we generate the semvers. I image rust-proc-macro-crate-1 would pose the same problem. Quoting you from 1040477: A very simple workaround from my pov would be temporarily removing Multi-Arch: same. Of course that would make the package unavailable to cross compilation, but on the flip side, it already is. After dropping Multi-Arch: same, dose would no longer consider solutions involving coinstallations of it and archive testing could continue. Failing that, the only way I see is blacklisting the package in crossqa, but then I'd probably forget about it and it would also be surprising in the diagnostics as crossqa would always tell that this package does not exist. I prefer having you work around the issue. A simple upload dropping M-A:same removes the worst of pain and gives us time to work on a generic solution. Do you agree? Is the only workaround dropping Ma:same here ? Unfortunately we need the semvers (but try to keep them to a minimum). CC'd Fabian since he is a bit more knowledgable than me here. best, -- Matthias Geiger Debian Maintainer
Processed: Re: Re: loqui: FTBFS: loqui-core-gtk.gob:256:25: error: implicit declaration of function ‘account_list_dialog_open_for_connect’ [-Werror=implicit-function-declaration]
Processing control commands: > tags -1 + pending Bug #1066379 [src:loqui] loqui: FTBFS: loqui-core-gtk.gob:256:25: error: implicit declaration of function ‘account_list_dialog_open_for_connect’ [-Werror=implicit-function-declaration] Added tag(s) pending. -- 1066379: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066379 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1066379: Re: loqui: FTBFS: loqui-core-gtk.gob:256:25: error: implicit declaration of function ‘account_list_dialog_open_for_connect’ [-Werror=implicit-function-declaration]
Control: tags -1 + pending On Wed, 10 Apr 2024 12:19:54 -0400 Nick Rosbrook wrote: > This FTBFS is due to a missing include of account_list_dialog.h. In > Ubuntu we applied this patch to fix it. > > * debian/patches: fix implicit declaration of > account_list_dialog_open_for_connect > > > Thanks for considering the patch. Thanks for the patch! I intend to NMU this shortly with Nick's patch, debdiff attached. Please let me know asap if you want me to hold it. /Andreas gus...@debian.org nmu_fixing_1066379.debdiff Description: Binary data
Bug#1069686: libsequoia-octopus-librnp: postinst script Syntax error: "fi" unexpected
On Mon, Apr 22, 2024 at 02:41:44PM -0400, Daniel Kahn Gillmor wrote: > /var/lib/dpkg/tmp.ci/preinst: 12: Syntax error: "fi" unexpected (expecting > "then") > dpkg: error processing archive > /tmp/apt-dpkg-install-aFNmwO/1-libsequoia-octopus-librnp_1.8.1-3_amd64.deb > (--unpack): > new libsequoia-octopus-librnp package pre-installation script subprocess > returned error exit status 2 fixed in git. > Please try at least installing and uninstalling the package before > pushing it into unstable! the change seems innocent enough... (I just wasnt expected the different formatting styles...) > This also makes me wonder whether we should be doing anything in an > autopkgtest kind of way for this package. It'd be great to get some > more automated confirmation that the things are working as expected > before we inflict them on the rest of the debian ecosystem :P the irony is: the autopkg tests for the package had failed which I blamed on unstables unstableness these days, so I reviewed the diff once more, (again) didnt notice the introduced bug and did a source only upload, because the change were tiny... :/ to me this is more an argument for unstable-untested, or testing maybe. -- cheers, Holger ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ holger@(debian|reproducible-builds|layer-acht).org ⢿⡄⠘⠷⠚⠋⠀ OpenPGP: B8BF54137B09D35CF026FE9D 091AB856069AAA1C ⠈⠳⣄ 20230709: Today was the warmest day on earth in 125,000 years. Today was also the day with the most planes in the air at one time ever in history. By the time you read this both of these records have probably been broken. signature.asc Description: PGP signature
Bug#1069689: mandos lost mandos.service systemd unit
I am uploading Helmut's changes as NMU. The debdiff is attached. mandos_1.8.16-1.2.debdiff Description: Binary data
Bug#1068750: marked as done (moment-timezone.js: FTBFS everywhere)
Your message dated Mon, 22 Apr 2024 19:49:59 + with message-id and subject line Bug#1068750: fixed in moment-timezone.js 0.5.45+dfsg-1+2024a has caused the Debian Bug report #1068750, regarding moment-timezone.js: FTBFS everywhere 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.) -- 1068750: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068750 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:moment-timezone.js Version: 0.5.32+dfsg1-2+2021a Severity: serious Tags: bullseye bookworm trixie sid ftbfs Dear maintainer: This package currently fails to build from source in all supported distributions. make[1]: Leaving directory '/<>' dh_clean debian/rules binary dh binary dh_update_autotools_config dh_autoreconf debian/rules execute_before_dh_auto_configure make[1]: Entering directory '/<>' # Fail the build if the tzdata package does not match TZVER. grep -q '^# version 2023d$' /usr/share/zoneinfo/tzdata.zi make[1]: *** [debian/rules:28: execute_before_dh_auto_configure] Error 1 make[1]: Leaving directory '/<>' make: *** [debian/rules:24: binary] Error 2 dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2 See also: https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/moment-timezone.js.html I'm curious: Does this package embed the information from tzdata into javascript code, in such a way that a change in tzdata requires a rebuild? I think it would be highly desirable to find a way for this package to do what it's supposed to do without having to fix it in oldstable and stable every year. (In fact, I asked Paul Gevers about this, he says that a package which we know for sure that it will fail to build during the support time of the release is RC). Thanks. --- End Message --- --- Begin Message --- Source: moment-timezone.js Source-Version: 0.5.45+dfsg-1+2024a Done: Martina Ferrari We believe that the bug you reported is fixed in the latest version of moment-timezone.js, 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. Martina Ferrari (supplier of updated moment-timezone.js package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 22 Apr 2024 19:16:15 + Source: moment-timezone.js Architecture: source Version: 0.5.45+dfsg-1+2024a Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Martina Ferrari Closes: 1068750 Changes: moment-timezone.js (0.5.45+dfsg-1+2024a) unstable; urgency=medium . * New upstream version 0.5.45+dfsg. * debian/copyright: Update years. * Support tzdata 2024a. Closes: #1068750. Checksums-Sha1: f9663e5bcc9b707788d9415eff453f917706c2f9 2356 moment-timezone.js_0.5.45+dfsg-1+2024a.dsc 9e582ede7a292da78a80ef33661e443ec2d82b36 1991404 moment-timezone.js_0.5.45+dfsg.orig.tar.xz ebf98a19a9ed0a7e4d6b5fe6c38b31b6de0d690c 6364 moment-timezone.js_0.5.45+dfsg-1+2024a.debian.tar.xz e79690da0b1e3aa8897293034688090fd684c10c 20437 moment-timezone.js_0.5.45+dfsg-1+2024a_amd64.buildinfo Checksums-Sha256: 8ea4fb10516e980fdf541b50ff5b4bd79376ab9d1cf13b41c4a96f58bfc2de69 2356 moment-timezone.js_0.5.45+dfsg-1+2024a.dsc 605638ef0f6235292fbf571510b2d1751899afd50af4cfed63f024c679b979ee 1991404 moment-timezone.js_0.5.45+dfsg.orig.tar.xz f25dae861ebedc15dd0fd0398ea3aeb374fbddc5625f4f9753b08281d8656136 6364 moment-timezone.js_0.5.45+dfsg-1+2024a.debian.tar.xz 9202e1ed43c137b4b980c9a3382c3644546297185e0ca7d6758be1c0b6a65f33 20437 moment-timezone.js_0.5.45+dfsg-1+2024a_amd64.buildinfo Files: 1ef00920ba182620d1634f268e839198 2356 javascript optional moment-timezone.js_0.5.45+dfsg-1+2024a.dsc 48a03ce04ec6e1e05da7b8aca6734726 1991404 javascript optional moment-timezone.js_0.5.45+dfsg.orig.tar.xz 1d9aeb8a59f30675dc0c65b5c9909181 6364 javascript optional moment-timezone.js_0.5.45+dfsg-1+2024a.debian.tar.xz 67b43d90b9c168ba14bcff56c549ab35 20437 javascript optional moment-timezone.js_0.5.45+dfsg-1+2024a_amd64.buildinfo -BEGIN PGP SIGNATURE-
Bug#1069692: nfs-ganesha: FTBFS on arm{el,hf}: /usr/include/features-time64.h:26:5: error: #error "_TIME_BITS=64 is allowed only with _FILE_OFFSET_BITS=64"
Source: nfs-ganesha Version: 4.3-9 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org https://buildd.debian.org/status/fetch.php?pkg=nfs-ganesha=armel=4.3-9=1713793450=0 [ 93%] Building C object FSAL/FSAL_GPFS/CMakeFiles/fsalgpfs.dir/file.c.o cd /<>/src/obj-arm-linux-gnueabi/FSAL/FSAL_GPFS && /usr/bin/cc -DHAS_DOFF -D_GNU_SOURCE=1 -Dfsalgpfs_EXPORTS -I/<>/src/obj-arm-linux-gnueabi/include -I/<>/src/include -I/<>/src/include/os/linux -I/include -I/usr/include/ntirpc -I/usr/include/dbus-1.0 -I/usr/lib/arm-linux-gnueabi/dbus-1.0/include -I/<>/src/FSAL/FSAL_GPFS -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -fno-strict-aliasing -O2 -g -DNDEBUG -fPIC -MD -MT FSAL/FSAL_GPFS/CMakeFiles/fsalgpfs.dir/file.c.o -MF CMakeFiles/fsalgpfs.dir/file.c.o.d -o CMakeFiles/fsalgpfs.dir/file.c.o -c /<>/src/FSAL/FSAL_GPFS/file.c In file included from /usr/include/features.h:393, from /usr/include/assert.h:35, from /<>/src/FSAL/FSAL_GPFS/file.c:38: /usr/include/features-time64.h:26:5: error: #error "_TIME_BITS=64 is allowed only with _FILE_OFFSET_BITS=64" 26 | # error "_TIME_BITS=64 is allowed only with _FILE_OFFSET_BITS=64" | ^ Cheers -- Sebastian Ramacher
Processed: Bug#1068750 marked as pending in moment-timezone.js
Processing control commands: > tag -1 pending Bug #1068750 [src:moment-timezone.js] moment-timezone.js: FTBFS everywhere Added tag(s) pending. -- 1068750: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068750 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1069691: libmaus2: FTBFS on arm64: what(): AutoArray failed to allocate 1398102 elements (11184816 bytes)
Source: libmaus2 Version: 2.0.813+ds-2 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org https://buildd.debian.org/status/fetch.php?pkg=libmaus2=arm64=2.0.813%2Bds-2=1713374325=0 libmaus2 2.0.813: test/test-suite.log === # TOTAL: 13 # PASS: 11 # SKIP: 0 # XFAIL: 0 # FAIL: 2 # XPASS: 0 # ERROR: 0 .. contents:: :depth: 2 FAIL: testRank.sh = /<>/test /<>/test /<>/test [V] testing FastRank...done. [V] testing RunLengthBitVector...done. [V] testing E2Append: [V]rank class libmaus2::rank::ERank222BAppend writer type libmaus2::bitio::BitWriterTemplate data type unsigned long [V] loop 1 [V] libmaus2::rank::ERank222BAppendDynamic loop 1 [V] loop 2 [V] libmaus2::rank::ERank222BAppendDynamic loop 2 [V] loop 3 [V] libmaus2::rank::ERank222BAppendDynamic loop 3 [V] loop 4 [V] libmaus2::rank::ERank222BAppendDynamic loop 4 [V] loop 5 [V] libmaus2::rank::ERank222BAppendDynamic loop 5 [V] testing WaveletTree rank/select random (size 128)...done. [V] testing WaveletTree smaller/larger...done. [V] testing CacheLineRank: terminate called after throwing an instance of 'libmaus2::exception::LibMausException' what(): AutoArray failed to allocate 1398102 elements (11184816 bytes) current total allocation 11521707 /<>/src/.libs/libmaus2_stacktrace.so.2(libmaus2::stacktrace::StackTrace::StackTrace()+0x74)[0xb4644b88] /<>/src/.libs/libmaus2_exception.so.2(libmaus2::exception::LibMausException::LibMausException()+0x40)[0xb4e42b40] /<>/src/.libs/testRank(libmaus2::autoarray::AutoArrayAllocate::allocate(unsigned long)+0xc4)[0xe833c2c4] /<>/src/.libs/testRank(testCacheLineRank()+0x88)[0xe831d318] /<>/src/.libs/testRank(main+0x134)[0xe830b834] /lib/aarch64-linux-gnu/libc.so.6(+0x26dc4)[0xb4886dc4] /lib/aarch64-linux-gnu/libc.so.6(__libc_start_main+0x98)[0xb4886e98] /<>/src/.libs/testRank(_start+0x30)[0xe830c5f0] ./testRank.sh: line 7: 355775 Aborted ../src/testRank Exiting with return code 134 FAIL testRank.sh (exit status: 134) FAIL: testdnarank.sh /<>/test /<>/test /<>/test [V] running short tests... AutoArray failed to allocate 16 elements (128 bytes) current total allocation 341115 /<>/src/.libs/libmaus2_stacktrace.so.2(libmaus2::stacktrace::StackTrace::StackTrace()+0x74)[0xa4e64b88] /<>/src/.libs/libmaus2_exception.so.2(libmaus2::exception::LibMausException::LibMausException()+0x40)[0xa55b2b40] /<>/src/.libs/testdnarank(libmaus2::autoarray::AutoArrayAllocate::allocate(unsigned long)+0xc4)[0xc76d0e24] /<>/src/.libs/testdnarank(libmaus2::rank::DNARankTemplate<64u>::loadFromRunLength(std::vector, std::allocator >, std::allocator, std::allocator > > > const&, unsigned long)+0x108)[0xc76dcfd8] /<>/src/.libs/testdnarank(void testShort >(unsigned long)+0x27c)[0xc77008bc] /<>/src/.libs/testdnarank(main+0x15c)[0xc76b16cc] /lib/aarch64-linux-gnu/libc.so.6(+0x26dc4)[0xa50a6dc4] /lib/aarch64-linux-gnu/libc.so.6(__libc_start_main+0x98)[0xa50a6e98] /<>/src/.libs/testdnarank(_start+0x30)[0xc76b1970] Exiting with return code 1 FAIL testdnarank.sh (exit status: 1) Cheers -- Sebastian Ramacher
Bug#1068750: marked as pending in moment-timezone.js
Control: tag -1 pending Hello, Bug #1068750 in moment-timezone.js 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/js-team/moment-timezone.js/-/commit/a1ccd03c583206a83c580a1c90d52486f6254416 Support tzdata 2024a. Closes: #1068750 (this message was generated automatically) -- Greetings https://bugs.debian.org/1068750
Processed: libsequoia-octopus-librnp has an undeclared file conflict on /usr/lib/thunderbird/librnp.so
Processing control commands: > affects -1 + thunderbird Bug #1069688 [libsequoia-octopus-librnp] libsequoia-octopus-librnp has an undeclared file conflict on /usr/lib/thunderbird/librnp.so Added indication that 1069688 affects thunderbird -- 1069688: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069688 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1069689: mandos lost mandos.service systemd unit
Source: mandos Version: 1.8.16-1.1 Severity: serious Tags: patch Justification: prevent testing migration after unintentional deletion of systemd unit X-Debbugs-Cc: Bastian Germann User: helm...@debian.org Usertags: dep17p6 The last mandos upload is the first after systemd.pc having moved systemdsystemunitdir from /lib to /usr/lib. mandos' upstream Makefile uses this to see where to install units to, but it also only does that if the relevant directory exists. Now since the new location wasn't created, it ceased installing the unit. We need to create the new location to reinstate the unit. Patch attached. I think the loss of the unit is unintantional and for that reason file this as rc bug. Please adjust if you disagree. This change makes mandos backports-unsafe. I don't expect mandos to be backported. Helmut diff --minimal -Nru mandos-1.8.16/debian/changelog mandos-1.8.16/debian/changelog --- mandos-1.8.16/debian/changelog 2024-04-19 13:08:30.0 +0200 +++ mandos-1.8.16/debian/changelog 2024-04-22 21:13:43.0 +0200 @@ -1,3 +1,10 @@ +mandos (1.8.16-1.2) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Install mandos.service again. (Closes: #-1) + + -- Helmut Grohne Mon, 22 Apr 2024 21:13:43 +0200 + mandos (1.8.16-1.1) unstable; urgency=medium * Non-maintainer upload. diff --minimal -Nru mandos-1.8.16/debian/mandos.dirs mandos-1.8.16/debian/mandos.dirs --- mandos-1.8.16/debian/mandos.dirs2019-08-18 21:51:02.0 +0200 +++ mandos-1.8.16/debian/mandos.dirs2024-04-22 21:13:43.0 +0200 @@ -5,6 +5,6 @@ etc/dbus-1/system.d usr/sbin var/lib/mandos -lib/systemd/system usr/lib/tmpfiles.d usr/lib/sysusers.d +usr/lib/systemd/system
Bug#1069688: libsequoia-octopus-librnp has an undeclared file conflict on /usr/lib/thunderbird/librnp.so
Package: libsequoia-octopus-librnp Version: 1.8.1-3 Severity: serious User: debian...@lists.debian.org Usertags: fileconflict Control: affects -1 + thunderbird libsequoia-octopus-librnp has an undeclared file conflict. This may result in an unpack error from dpkg. The file /usr/lib/thunderbird/librnp.so is contained in the packages * libsequoia-octopus-librnp/1.8.1-3 as present in unstable * thunderbird/1:122.0~b2-1 as present in experimental 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: Re: chmlib: FTBFS: chm_http.c:167:32: error: implicit declaration of function ‘inet_addr’ [-Werror=implicit-function-declaration]
Processing control commands: > tags -1 patch Bug #1066327 [src:chmlib] chmlib: FTBFS: chm_http.c:167:32: error: implicit declaration of function ‘inet_addr’ [-Werror=implicit-function-declaration] Added tag(s) patch. -- 1066327: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066327 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1066327: chmlib: FTBFS: chm_http.c:167:32: error: implicit declaration of function ‘inet_addr’ [-Werror=implicit-function-declaration]
Package: chmlib Followup-For: Bug #1066327 User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu noble ubuntu-patch Control: tags -1 patch Dear Maintainer, In Ubuntu, the attached patch was applied to achieve the following: * debian/patches/implicit-declarations.patch: Add missing includes and fix large file support. (LP: #2062947). Thanks for considering the patch. -- System Information: Debian Release: bookworm/sid APT prefers jammy-updates APT policy: (500, 'jammy-updates'), (500, 'jammy-security'), (500, 'jammy'), (100, 'jammy-backports') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.5.0-28-generic (SMP w/10 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), LANGUAGE=en_CA:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled diff -Nru chmlib-0.40a/debian/patches/implicit-declarations.patch chmlib-0.40a/debian/patches/implicit-declarations.patch --- chmlib-0.40a/debian/patches/implicit-declarations.patch 1969-12-31 17:00:00.0 -0700 +++ chmlib-0.40a/debian/patches/implicit-declarations.patch 2024-04-19 20:28:30.0 -0600 @@ -0,0 +1,38 @@ +Description: Add missing includes and fix large file support +Author: Zixing Liu +Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066327 +Bug-Ubuntu: https://bugs.launchpad.net/bugs/2062947 +Forwarded: no +Last-Update: 2024-04-19 +--- +--- chmlib-0.40a.orig/src/chm_http.c chmlib-0.40a/src/chm_http.c +@@ -34,6 +34,7 @@ + #include + #include + #include ++#include + #if __sun || __sgi + #include + #define strrchr rindex +@@ -43,6 +44,7 @@ + #include + #include + #include ++#include + + /* threading includes */ + #include +--- chmlib-0.40a.orig/src/chm_lib.c chmlib-0.40a/src/chm_lib.c +@@ -86,7 +86,9 @@ + #include + /* #include */ + #endif +- ++#ifdef _LARGEFILE_SOURCE ++#define pread64 pread ++#endif + /* includes/defines for threading, if using them */ + #ifdef CHM_MT + #ifdef WIN32 diff -Nru chmlib-0.40a/debian/patches/series chmlib-0.40a/debian/patches/series --- chmlib-0.40a/debian/patches/series 1969-12-31 17:00:00.0 -0700 +++ chmlib-0.40a/debian/patches/series 2024-04-19 20:25:29.0 -0600 @@ -0,0 +1 @@ +implicit-declarations.patch
Bug#1068750: moment-timezone.js: FTBFS everywhere
Hi Santiago, On Wed, 10 Apr 2024 12:39:54 +0200 Santiago Vila wrote: Dear maintainer: This package currently fails to build from source in all supported distributions. # Fail the build if the tzdata package does not match TZVER. grep -q '^# version 2023d$' /usr/share/zoneinfo/tzdata.zi Yes, this is expected after each update to tzdata. I'm curious: Does this package embed the information from tzdata into javascript code, in such a way that a change in tzdata requires a rebuild? Yes. It is the only way I found to keep the package aligned with tzdata while ensuring it is fully built from source: upstream ships the pre-compiled tzdata information, so I regenerate those files using the tzdata package. I think it would be highly desirable to find a way for this package to do what it's supposed to do without having to fix it in oldstable and stable every year. Without a new upload, I cannot imagine how.. :-/ (In fact, I asked Paul Gevers about this, he says that a package which we know for sure that it will fail to build during the support time of the release is RC). It fails to build if tzdata is updated, but it never stops working. It just needs to be updated as often as tzdata is. But if you have a suggestion to make this more automatic, I would love to hear it.. I have been doing this very repetitive maintenance for years! -- Martina Ferrari
Bug#1069687: librust-bitflags-1-dev: fails to co-install
Package: librust-bitflags-1-dev Version: 1.3.2-5+b1 Severity: serious Justification: causes an installation failure Hi, Attempting to install librust-bitflags-1-dev for multiple architectures fails, because apt and dpkg disagree about how breaks and provides work. apt thinks that self-breaks can be ignored, but dpkg thinks that since librust-bitflags-1-dev breaks+provides librust-bitflags-1.3.2-dev it cannot be coinstalled and gives up. You cannot combine such breaks+provides with m-a:same. The simplest workaround here is dropping m-a:same as it cannot be exercised anyway. Helmut
Bug#1069686: libsequoia-octopus-librnp: postinst script Syntax error: "fi" unexpected
Package: libsequoia-octopus-librnp Version: 1.8.1-3 Severity: grave X-Debbugs-Cc: Daniel Kahn Gillmor Trying to install libsequoia-octopus-librnp: /var/lib/dpkg/tmp.ci/preinst: 12: Syntax error: "fi" unexpected (expecting "then") dpkg: error processing archive /tmp/apt-dpkg-install-aFNmwO/1-libsequoia-octopus-librnp_1.8.1-3_amd64.deb (--unpack): new libsequoia-octopus-librnp package pre-installation script subprocess returned error exit status 2 Please try at least installing and uninstalling the package before pushing it into unstable! This also makes me wonder whether we should be doing anything in an autopkgtest kind of way for this package. It'd be great to get some more automated confirmation that the things are working as expected before we inflict them on the rest of the debian ecosystem :P --dkg -- System Information: Debian Release: trixie/sid APT prefers testing-debug APT policy: (500, 'testing-debug'), (500, 'testing'), (500, 'stable'), (500, 'oldstable'), (200, 'unstable-debug'), (200, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.6.15-amd64 (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_FIRMWARE_WORKAROUND Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages libsequoia-octopus-librnp depends on: ii libbz2-1.0 1.0.8-5.1 ii libc6 2.37-15 ii libgcc-s1 14-20240201-3 ii libgmp102:6.3.0+dfsg-2+b1 ii libhogweed6t64 3.9.1-2.2 ii libnettle8t64 3.9.1-2.2 ii libsqlite3-03.45.1-1 ii libssl3t64 3.2.1-3 Versions of packages libsequoia-octopus-librnp recommends: ii zenity 4.0.1-1 Versions of packages libsequoia-octopus-librnp suggests: ii thunderbird 1:115.10.1-1 -- no debconf information signature.asc Description: PGP signature
Processed: tagging 1032177
Processing commands for cont...@bugs.debian.org:
> tags 1032177 - ftbfs
Bug #1032177 [faketime] faketime doesn't fake time (on i386)
Bug #1067016 [faketime] osslsigncode: FTBFS on arm{el,hf}: test failures
Removed tag(s) ftbfs.
Removed tag(s) ftbfs.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1032177: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032177
1067016: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067016
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: reassign 1067016 to faketime, affects 1067016, forcibly merging 1032177 1067016
Processing commands for cont...@bugs.debian.org:
> reassign 1067016 faketime
Bug #1067016 [src:osslsigncode] osslsigncode: FTBFS on arm{el,hf}: test failures
Bug reassigned from package 'src:osslsigncode' to 'faketime'.
No longer marked as found in versions osslsigncode/2.8-1.
Ignoring request to alter fixed versions of bug #1067016 to the same values
previously set
> affects 1067016 src:osslsigncode
Bug #1067016 [faketime] osslsigncode: FTBFS on arm{el,hf}: test failures
Added indication that 1067016 affects src:osslsigncode
> forcemerge 1032177 1067016
Bug #1032177 [faketime] faketime doesn't fake time (on i386)
Bug #1067016 [faketime] osslsigncode: FTBFS on arm{el,hf}: test failures
Set Bug forwarded-to-address to
'https://github.com/wolfcw/libfaketime/issues/418'.
Severity set to 'grave' from 'serious'
Removed indication that 1067016 affects src:osslsigncode
Marked as found in versions faketime/0.9.10-2.1.
Bug #1032177 [faketime] faketime doesn't fake time (on i386)
Added tag(s) ftbfs.
Merged 1032177 1067016
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1032177: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032177
1067016: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067016
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1064920: FTBFS on 32-bit architectures
I created a pull request to fix the build issue. Please review
https://salsa.debian.org/bluefield-team/rshim-user-space/-/merge_requests/11
-tai
On Tue, Feb 27, 2024 at 7:27 PM dann frazier wrote:
>
> Source: rshim-user-space
> Version: 2.0.12+debian-1
> Severity: serious
> Tags: ftbfs
> Justification: fails to build from source (but built successfully in the past)
>
> The switch to fuse3 appears to have introduced a build issue for 32-bit
> architectures such as armhf:
>
> From
> https://buildd.debian.org/status/fetch.php?pkg=rshim-user-space=armhf=2.0.20%2Bdebian-1=1709056732=0
> :
>
> gcc -DHAVE_CONFIG_H -I. -I.. -Wall -DHAVE_RSHIM_NET
> -I/usr/include/libusb-1.0 -DHAVE_RSHIM_USB
> -I/usr/include/arm-linux-gnueabihf -DHAVE_RSHIM_PCIE -I/usr/include/fuse3
> -DHAVE_RSHIM_FUSE -Wdate-time -D_FORTIFY_SOURCE=2 -DFUSE_USE_VERSION=30
> -DDEFAULT_RSHIM_CONFIG_FILE='"/etc/rshim.conf"' -g -O2
> -ffile-prefix-map=/<>=. -fstack-protector-strong
> -fstack-clash-protection -Wformat -Werror=format-security -c -o
> rshim-rshim_fuse.o `test -f 'rshim_fuse.c' || echo './'`rshim_fuse.c
> In file included from /usr/include/fuse3/fuse_lowlevel.h:25,
> from /usr/include/fuse3/cuse_lowlevel.h:19,
> from rshim_fuse.c:23:
> /usr/include/fuse3/fuse_common.h:928:1: error: static assertion failed:
> "fuse: off_t must be 64bit"
> 928 | _Static_assert(sizeof(off_t) == 8, "fuse: off_t must be 64bit");
> | ^~
> rshim_pcie.c: In function ‘rshim_pcie_mmap_vfio’:
> rshim_pcie.c:52:37: warning: overflow in conversion from ‘long long unsigned
> int’ to ‘__off_t’ {aka ‘long int’} changes value from ‘7696581394436’ to ‘4’
> [-Woverflow]
>52 | #define VFIO_GET_REGION_ADDR(x) ((uint64_t) x << 40ULL)
> | ^
> rshim_pcie.c:634:18: note: in expansion of macro ‘VFIO_GET_REGION_ADDR’
> 634 | VFIO_GET_REGION_ADDR(VFIO_PCI_CONFIG_REGION_INDEX) +
> | ^~~~
> rshim_pcie.c:52:37: warning: overflow in conversion from ‘long long unsigned
> int’ to ‘__off_t’ {aka ‘long int’} changes value from ‘7696581394436’ to ‘4’
> [-Woverflow]
>52 | #define VFIO_GET_REGION_ADDR(x) ((uint64_t) x << 40ULL)
> | ^
> rshim_pcie.c:643:19: note: in expansion of macro ‘VFIO_GET_REGION_ADDR’
> 643 | VFIO_GET_REGION_ADDR(VFIO_PCI_CONFIG_REGION_INDEX) +
> | ^~~~
> rshim_fuse.c: In function ‘rshim_fuse_misc_read’:
> rshim_fuse.c:713:36: warning: format ‘%ld’ expects argument of type ‘long
> int’, but argument 5 has type ‘uint64_t’ {aka ‘long long unsigned int’}
> [-Wformat=]
> 713 | n = snprintf(p, len, "%-16s%ld(s)\n", "UP_TIME",
> value/BF3_REF_CLK_IN_HZ);
> | ~~^
> ||
> |long int
> | %lld
> rshim_fuse.c: In function ‘rshim_fuse_misc_write’:
> rshim_fuse.c:954:25: warning: format ‘%lx’ expects argument of type ‘long
> unsigned int *’, but argument 3 has type ‘uint64_t *’ {aka ‘long long
> unsigned int *’} [-Wformat=]
> 954 | if (sscanf(p, " 0x%lx", ) != 1)
> | ~~^ ~~
> | | |
> | | uint64_t * {aka long long unsigned int *}
> | long unsigned int *
> | %llx
> make[3]: *** [Makefile:524: rshim-rshim_fuse.o] Error 1
>
>
> -- System Information:
> Debian Release: trixie/sid
> APT prefers unstable-debug
> APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'stable'),
> (1, 'experimental-debug'), (1, 'experimental')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
>
> Kernel: Linux 6.6.15-amd64 (SMP w/4 CPU threads; PREEMPT)
> Kernel taint flags: TAINT_FIRMWARE_WORKAROUND
> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not
> set
> Shell: /bin/sh linked to /usr/bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled
Bug#1069247: libconfig-model-dpkg-perl: test failures
On Mon, Apr 22, 2024 at 07:41:42PM +0200, Dominique Dumont wrote: > On Sunday, 21 April 2024 18:07:00 CEST Julian Andres Klode wrote: > > This should be fixed in apt git already, just needs an upload, > > which is waiting-ish for some more merges > > Given [1], I need to ask... > > Is this a definitive fix or will this feature come back with apt 3.0 ? The feature remains available in output version 3.0 which is what apt(8) is defaulting to right now. apt-get remains at output version 0 at least until 4.0. This should be fixed in apt side on 2.9.2 I just uploaded, but either way it's a weird thing to break because we change progress messages for interactive output, maybe run with -q instead or don't pretend to be a tty. -- debian developer - deb.li/jak | jak-linux.org - free software dev ubuntu core developer i speak de, en
Bug#1069247: libconfig-model-dpkg-perl: test failures
On Sunday, 21 April 2024 18:07:00 CEST Julian Andres Klode wrote: > This should be fixed in apt git already, just needs an upload, > which is waiting-ish for some more merges Given [1], I need to ask... Is this a definitive fix or will this feature come back with apt 3.0 ? All the best [1] https://salsa.debian.org/apt-team/apt/-/commit/fc35b4d7d95b2848db482021df4f4500ac142080
Bug#1069685: haskell-language-c-quote: Missing build dependency on alex
Source: haskell-language-c-quote Version: 0.13.0.1-1 Severity: serious Tags: ftbfs X-Debbugs-Cc: Debian Haskell Group , Kari Pahula https://buildd.debian.org/status/logs.php?pkg=haskell-language-c-quote=0.13.0.1-1 ... Error: hlibrary.setup: The program 'alex' version >=3 is required but it could not be found. ...
Bug#1067615: ping bug #1067615
Sorry, but this is just a ping to keep the package from being autoremoved
Processed: severity of 1065435 is important
Processing commands for cont...@bugs.debian.org:
> # downgrading as already tagged downgrade but forgot to change severity
> severity 1065435 important
Bug #1065435 {Done: Julian Andres Klode } [src:aptitude]
aptitude: FTBFS on armhf and armel: deduced conflicting types for parameter
‘const T’ (‘long int’ and ‘__suseconds64_t’ {aka ‘long long int’})
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1065435: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065435
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#1069546: ktorrent: FTBFS on armel: dh_install: error: missing files, aborting
Processing control commands: > severity -1 wishlist Bug #1069546 [src:ktorrent] ktorrent: FTBFS on arches without QtWebEngine Severity set to 'wishlist' from 'serious' -- 1069546: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069546 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1069546: ktorrent: FTBFS on armel: dh_install: error: missing files, aborting
Control: severity -1 wishlist
Processed: Re: Bug#1069614: erfs: isolation-machine autopkgtest fails: sshfs failed
Processing control commands: > severity -1 serious Bug #1069614 [src:erfs] erfs: isolation-machine autopkgtest fails: sshfs failed Severity set to 'serious' from 'important' > retitle -1 erfs: no longer functional, should be removed Bug #1069614 [src:erfs] erfs: isolation-machine autopkgtest fails: sshfs failed Changed Bug title to 'erfs: no longer functional, should be removed' from 'erfs: isolation-machine autopkgtest fails: sshfs failed'. -- 1069614: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069614 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed (with 1 error): Re: Bug#1069546: ktorrent: FTBFS on armel: dh_install: error: missing files, aborting
Processing control commands: > retitle -1 ktorrent: FTBFS on arches without QtWebEngine Bug #1069546 [src:ktorrent] ktorrent: FTBFS on armel: dh_install: error: missing files, aborting Changed Bug title to 'ktorrent: FTBFS on arches without QtWebEngine' from 'ktorrent: FTBFS on armel: dh_install: error: missing files, aborting'. > severity -1 whishlist Severity level `whishlist' is not known. Recognized are: critical, grave, serious, important, normal, minor, wishlist, fixed. > tags -1 + wontfix Bug #1069546 [src:ktorrent] ktorrent: FTBFS on arches without QtWebEngine Added tag(s) wontfix. -- 1069546: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069546 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1069546: ktorrent: FTBFS on armel: dh_install: error: missing files, aborting
Control: retitle -1 ktorrent: FTBFS on arches without QtWebEngine Control: severity -1 whishlist Control: tags -1 + wontfix Le 20 avril 2024 15:23:30 GMT+02:00, Lucas Nussbaum a écrit : >Source: ktorrent >Version: 22.12.3-2 >Severity: serious >Justification: FTBFS >Tags: trixie sid ftbfs >User: lu...@debian.org >Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-armel > >Hi, Dear Lucas, >During a rebuild of all packages in sid, your package failed to build >on armel. what happens is that on arches that don't have QtWebEngine, the ktorrent build succeeds but doesn't produce some of the files expected by dh_install for the arch:all ktorrent-data package. The issue doesn't happen on buildds where arch:all packages are built on amd64 and other arches run dh_install -a. There is no easy way to split the generation of the arch:all files for ktorrent in a separate build-indep target so I'm marking this bug as whishlist+wontfix. Happy hacking, -- Aurélien
Bug#1068045: marked as done (libssl3,yapet: YAPET cannot decrypt YAPET1.0-format DB)
Your message dated Mon, 22 Apr 2024 17:02:12 + with message-id and subject line Bug#1064724: fixed in yapet 2.6-2~deb12u1 has caused the Debian Bug report #1064724, regarding libssl3,yapet: YAPET cannot decrypt YAPET1.0-format DB 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.) -- 1064724: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064724 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libssl3 Version: 3.0.13-1~deb12u1 Severity: grave Justification: renders package unusable X-Debbugs-Cc: t...@security.debian.org Control: affects -1 + yapet Dear maintainer, This version of libssl3 from bookworm-proposed-updates breaks YAPET. When I try to open my passwords database, it claims the master password I type is incorrect. But downgrading libssl3 fixes the problem. -- System Information: Debian Release: 12.5 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.1.0-18-amd64 (SMP w/8 CPU threads; PREEMPT) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB.UTF-8 Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libssl3 depends on: ii libc6 2.36-9+deb12u5 libssl3 recommends no packages. libssl3 suggests no packages. -- no debconf information -- Sean Whitton signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: yapet Source-Version: 2.6-2~deb12u1 Done: Salvatore Bonaccorso We believe that the bug you reported is fixed in the latest version of yapet, 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. Salvatore Bonaccorso (supplier of updated yapet package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 11 Apr 2024 20:40:18 +0200 Source: yapet Architecture: source Version: 2.6-2~deb12u1 Distribution: bookworm Urgency: medium Maintainer: Salvatore Bonaccorso Changed-By: Salvatore Bonaccorso Closes: 1064724 Changes: yapet (2.6-2~deb12u1) bookworm; urgency=medium . * Rebuild for bookworm . yapet (2.6-2) unstable; urgency=medium . * crypt/blowfish: Remove EVP_CIPHER_CTX_set_key_length() (Closes: #1064724) * crypt/aes: Remove EVP_CIPHER_CTX_set_key_length() Checksums-Sha1: 0a691e8916fd5949d49c4c357a7dcb78452fda72 2064 yapet_2.6-2~deb12u1.dsc 335a90e8fefc66c9841426829d31880c84fd428a 8028 yapet_2.6-2~deb12u1.debian.tar.xz Checksums-Sha256: 62195a270b1c7939db5b7008a656d05eec3c13bbc93db78f8cb7b41fd5dd2009 2064 yapet_2.6-2~deb12u1.dsc 805b03cc33acb8789e6c48d486edee19e5ff0771cf3a66ad732650f089f79a5a 8028 yapet_2.6-2~deb12u1.debian.tar.xz Files: 210afad98d9b43635abe82a24dd5454d 2064 utils optional yapet_2.6-2~deb12u1.dsc c7ec34ece7531676f120836b63ba1419 8028 utils optional yapet_2.6-2~deb12u1.debian.tar.xz -BEGIN PGP SIGNATURE- iQKmBAEBCgCQFiEERkRAmAjBceBVMd3uBUy48xNDz0QFAmYYMFxfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDQ2 NDQ0MDk4MDhDMTcxRTA1NTMxRERFRTA1NENCOEYzMTM0M0NGNDQSHGNhcm5pbEBk ZWJpYW4ub3JnAAoJEAVMuPMTQ89ElwUP/2M+gLpGqVZvTXiS9fWr2BYilBs+6CDs QnkXQF7qXIF7hVJlBrURefgLyZOnEuiTeyM043cMPjptqDS9EmaS8aetCWdvq23F EjtXAkGXNnxhugOu0AIeXuVI3C+e+sYxlO6f/g7McbywQPRK4XY0bqTzwn7+A20F IAeeOQzGH7NBsj3d6zq9aui+lsH+EHWgmAKFnEaGuyKf6ZoYt6eAR3ao0Q7gafuN 99MTJ71wmfZd/hT9LmD9EMTxbrl74oAW2uZlKGR2iQcbscE8E4cEKNJ8VIVZI1gH 0xHZjQl2eZOWM7OwmBl3Sb8IMjQqDXiyYjAXdG8NuO1RwOyveVpa46KGlhvsvrd/ 1fbn7y9GlQ+eNeBcYJ/9mzpBqg35ljliwbuFrEirnIx6MbBAbvp7Lzy8Xnmz7pr4 BGbiNoPyFDzKW6vPOpXb14XXS802IZa1LsnVfOow4oopk5YbGJFCbsjBmmixNs6q uIdZjkg0AQtt9Jplu3EJQgSejcWYxDVAKX8jEHpvwVUA4oWeoffcAsYFbfrFR3P/ YPn2ZrGSZzL0Cz/1NBorb7o8ju7L/Ba/jKle9nuLTdkJ/DwnhxM/yYusZzDfT5kC 44Kq4oSQsjL/Yf8Euw98lRnw7j0974c1GWsFT55pM0G7y6dyMfXmT0asVW2FpQc4 uiGbY6yZDek6 =H6a+ -END PGP SIGNATURE- pgp4cttjQyk6k.pgp Description: PGP signature --- End Message ---
Bug#1064724: marked as done (yapet: FTBFS: dh_auto_test: error: make -j8 check "TESTSUITEFLAGS=-j8 --verbose" VERBOSE=1 returned exit code 2)
Your message dated Mon, 22 Apr 2024 17:02:12 + with message-id and subject line Bug#1064724: fixed in yapet 2.6-2~deb12u1 has caused the Debian Bug report #1064724, regarding yapet: FTBFS: dh_auto_test: error: make -j8 check "TESTSUITEFLAGS=-j8 --verbose" VERBOSE=1 returned exit code 2 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1064724: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064724 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: yapet Version: 2.6-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240224 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[5]: Entering directory '/<>/tests/crypt' > FAIL: blowfish > PASS: key448 > PASS: blowfishfactory > FAIL: file_blowfish > FAIL: foreign > PASS: cryptofactoryhelper > PASS: aes256 > PASS: key256 > PASS: aes256factory > PASS: file_aes256 > === >YAPET 2.6: tests/crypt/test-suite.log > === > > # TOTAL: 10 > # PASS: 7 > # SKIP: 0 > # XFAIL: 0 > # FAIL: 3 > # XPASS: 0 > # ERROR: 0 > > .. contents:: :depth: 2 > > FAIL: blowfish > == > > .E.E.E. > > > !!!FAILURES!!! > Test Results: > Run: 4 Failures: 0 Errors: 3 > > > 1) test: should encrypt and decrypt (E) > uncaught exception of type std::exception (or derived). > - Error encrypting data > > > 2) test: should throw on decrypting corrupted data (E) > uncaught exception of type std::exception (or derived). > - Error encrypting data > > > 3) test: should throw on decrypting with wrong password (E) > uncaught exception of type std::exception (or derived). > - Error encrypting data > > > FAIL blowfish (exit status: 1) > > FAIL: file_blowfish > === > > .E.E.E.E.E.E.E.E.E.E > > > !!!FAILURES!!! > Test Results: > Run: 10 Failures: 0 Errors: 10 > > > 1) test: should correctly read empty file (E) > uncaught exception of type std::exception (or derived). > - Error encrypting data > > > 2) test: should correctly read empty file (E) > uncaught exception of type std::exception (or derived). > - Error encrypting data > > > 3) test: should throw expected exception on invalid password (E) > uncaught exception of type std::exception (or derived). > - Error encrypting data > > > 4) test: should write passwords (E) > uncaught exception of type std::exception (or derived). > - Error encrypting data > > > 5) test: should detect file modification on password save (E) > uncaught exception of type std::exception (or derived). > - Error encrypting data > > > 6) test: should force password save on modified file (E) > uncaught exception of type std::exception (or derived). > - Error encrypting data > > > 7) test: should get the correct time when the master password was set (E) > uncaught exception of type std::exception (or derived). > - Error encrypting data > > > 8) test: should properly set new password (E) > uncaught exception of type std::exception (or derived). > - Error encrypting data > > > 9) test: should allow saving passwords after password change (E) > uncaught exception of type std::exception (or derived). > - Error encrypting data > > > 10) test: should throw exception on reading corrupt file (E) > uncaught exception of type std::exception (or derived). > - Invalid password > > > FAIL file_blowfish (exit status: 1) > > FAIL: foreign > = > > .E.E.E.E.E.E.E.E > > > !!!FAILURES!!! > Test Results: > Run: 8 Failures: 0 Errors: 8 > > > 1) test: 32bit little endian pre 0.6 (E) > uncaught exception of type std::exception (or derived). > - Invalid password > > > 2) test: 32bit big endian pre 0.6 (E) > uncaught exception of type std::exception (or derived). > - Invalid password > > > 3) test: 64bit little endian pre 0.6 (E) > uncaught exception of type std::exception (or derived). > - Invalid password > > > 4) test: 64bit big endian pre 0.6 (E) > uncaught exception of type std::exception (or derived). > - Invalid password > > > 5) test: 32bit little endian 0.6 (E) > uncaught exception of type std::exception (or derived). > - Invalid password > > > 6) test: 32bit big endian 0.6 (E) > uncaught exception of type std::exception (or derived). > - Invalid password > > > 7) test: 64bit little endian 0.6 (E) > uncaught exception of type std::exception (or derived). > - Invalid password > > > 8) test: 64bit big endian 0.6 (E) > uncaught
Bug#1060768: marked as done (pdudaemon: Missing dependency on python3-aiohttp)
Your message dated Mon, 22 Apr 2024 17:02:11 +
with message-id
and subject line Bug#1060768: fixed in pdudaemon 0.0.8.58.g597052b-1+deb12u1
has caused the Debian Bug report #1060768,
regarding pdudaemon: Missing dependency on python3-aiohttp
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.)
--
1060768: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060768
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: pdudaemon
Version: 0.0.8.58.g597052b-1
Severity: serious
Attempting to use pdudaemon without python3-aiohttp installed results in
a traceback:
# pdudaemon
Traceback (most recent call last):
File "/usr/sbin/pdudaemon", line 33, in
sys.exit(load_entry_point('pdudaemon==0.1', 'console_scripts',
'pdudaemon')())
^^
File "/usr/sbin/pdudaemon", line 25, in importlib_load_entry_point
return next(matches).load()
File "/usr/lib/python3.11/importlib/metadata/__init__.py", line 202, in load
module = import_module(match.group('module'))
File "/usr/lib/python3.11/importlib/__init__.py", line 126, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
File "", line 1206, in _gcd_import
File "", line 1178, in _find_and_load
File "", line 1149, in _find_and_load_unlocked
File "", line 690, in _load_unlocked
File "", line 940, in exec_module
File "", line 241, in _call_with_frames_removed
File "/usr/lib/python3/dist-packages/pdudaemon/__init__.py", line 32, in
from pdudaemon.httplistener import HTTPListener
File "/usr/lib/python3/dist-packages/pdudaemon/httplistener.py", line 24, in
from aiohttp import web
ModuleNotFoundError: No module named 'aiohttp'
but there is no dependency declared in the package. Installing the
python3-aiohttp resolves this issue.
-- System Information:
Debian Release: 12.1
APT prefers stable-security
APT policy: (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: arm64
Kernel: Linux 6.1.0-10-amd64 (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8),
LANGUAGE=en_GB:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages pdudaemon depends on:
ii python3 3.11.2-1+b1
pn python3-hid
pn python3-paramiko
ii python3-pexpect 4.8.0-4
ii python3-pyasn10.4.8-3
ii python3-pysnmp4 4.4.12-2
ii python3-requests 2.28.1+dfsg-1
ii python3-serial3.5-1.1
pn python3-systemd
pn python3-usb
Versions of packages pdudaemon recommends:
ii inetutils-telnet [telnet] 2:2.4-2
ii openssh-client 1:9.2p1-2
pdudaemon suggests no packages.
--- End Message ---
--- Begin Message ---
Source: pdudaemon
Source-Version: 0.0.8.58.g597052b-1+deb12u1
Done: Andreas Beckmann
We believe that the bug you reported is fixed in the latest version of
pdudaemon, 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 1060...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Andreas Beckmann (supplier of updated pdudaemon 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, 19 Apr 2024 09:40:49 +0200
Source: pdudaemon
Architecture: source
Version: 0.0.8.58.g597052b-1+deb12u1
Distribution: bookworm
Urgency: medium
Maintainer: Matt Hart
Changed-By: Andreas Beckmann
Closes: 1060768
Changes:
pdudaemon (0.0.8.58.g597052b-1+deb12u1) bookworm; urgency=medium
.
* Non-maintainer upload.
* Add dependency on python3-aiohttp. (Closes: #1060768)
Checksums-Sha1:
3b26f7e79a620f96e5ee523cbb5b4d22f450cb57 2370
pdudaemon_0.0.8.58.g597052b-1+deb12u1.dsc
da20c4e0cb23034a8471996b80cf46d70e9bb690 6220
pdudaemon_0.0.8.58.g597052b-1+deb12u1.debian.tar.xz
3b1426ad9dc75af6779ea3cf63eea2f1c814e0bb 7970
pdudaemon_0.0.8.58.g597052b-1+deb12u1_source.buildinfo
Checksums-Sha256:
Bug#1039612: marked as done (libtool: Incorrect check for += operator causes func_append to fail)
Your message dated Mon, 22 Apr 2024 17:02:11 +
with message-id
and subject line Bug#1039612: fixed in libtool 2.4.7-7~deb12u1
has caused the Debian Bug report #1039612,
regarding libtool: Incorrect check for += operator causes func_append to fail
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.)
--
1039612: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1039612
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libtool
Version: 2.4.6-15
Severity: grave
Tags: patch
Justification: renders package unusable
X-Debbugs-Cc: erjoa...@gmail.com
Dear Maintainer,
While building isc-dhcpd-server, I tried using autoreconf as per instructions
to generate the ./configure file.
But running `autoreconf -i` on this project failed with this error:
/usr/bin/libtoolize: 1: eval: hookable_fns+=: not found
/usr/bin/libtoolize: 1: eval: hookable_fns+=: not found
/usr/bin/libtoolize: 1: eval: hookable_fns+=: not found
/usr/bin/libtoolize: 1: eval: hookable_fns+=: not found
libtoolize: error: 'func_options_prep' does not accept hook functions.
autoreconf: libtoolize failed with exit status: 1
Some others have reported this error, but the solution mentioned in that thread
was to run as root, which I shouldn't have to do to build in a local directory:
https://github.com/libsndfile/libsndfile/issues/132#issue-153391414
Looking at the source, I noticed the problem is not that
`func_options_prep does not accept hook functions`,
but that the script assumes the append operator `+=` works when it doesn't.
This assumption is based on the value of BASH_VERSION, but unfortunately this
is not reliable:
if test set = "${BASH_VERSION+set}${ZSH_VERSION+set}"; then
: ${_G_HAVE_ARITH_OP="yes"}
: ${_G_HAVE_XSI_OPS="yes"}
# The += operator was introduced in bash 3.1
case $BASH_VERSION in
[12].* | 3.0 | 3.0*) ;;
*)
: ${_G_HAVE_PLUSEQ_OP="yes"} # not really!
;;
esac
fi
It's not reliable because on my system, plain debian 11, /bin/sh is linked to
/usr/bin/dash, but the BASH_VERSION environment variable appears to have been
inherited from the bash process on my terminal and it is not
modified or deleted by dash. And += doesn't work in dash:
█[debian-x1-7th][isc-dhcp-4.4.1][0]$ ls -l /usr/bin/sh
lrwxrwxrwx 1 root root 4 Apr 27 17:06 /usr/bin/sh -> dash
█[debian-x1-7th][isc-dhcp-4.4.1][130]$ dash
\[\]█\[\][\h][\W][0]$ \[\]echo $BASH_VERSION
5.1.4(1)-release
\[\]█\[\][\h][\W][0]$ \[\]a=1
\[\]█\[\][\h][\W][0]$ \[\]a+=2
dash: 3: a+=2: not found
\[\]█\[\][\h][\W][127]$ \[\]
There's some advice online about how to find the true name of the shell:
https://stackoverflow.com/questions/23011370/ but I think it is too
complicated and error prone, and I think
the simplest way to correct this is to actually test for the feature directly
as is already being done in the script:
(eval 'x=a; x+=" b"; test "a b" = "$x"') && _G_HAVE_PLUSEQ_OP=yes
There is a comment expressing concern about speed of the test above and about
minimizing forks:
# We should try to minimise forks, especially on Windows where they are
# unreasonably slow, so skip the feature probes when bash or zsh are
# being used:
But I don't see any reason for needing a fork here:
if test -z "$_G_HAVE_PLUSEQ_OP" && \
__PLUSEQ_TEST="a" && \
__PLUSEQ_TEST+=" b" 2>/dev/null && \
test "a b" = "$__PLUSEQ_TEST"; then
_G_HAVE_PLUSEQ_OP=yes
fi
Even if a fork were needed, I don't think the possible speedup of avoiding the
a one-line feature probe is worth the risk of breaking users who
invoke this script from a parent bash terminal.
I'm including my suggested patch inline below:
527,547c527,535
< # We should try to minimise forks, especially on Windows where they are
< # unreasonably slow, so skip the feature probes when bash or zsh are
< # being used:
< if test set = "${BASH_VERSION+set}${ZSH_VERSION+set}"; then
< : ${_G_HAVE_ARITH_OP="yes"}
< : ${_G_HAVE_XSI_OPS="yes"}
< # The += operator was introduced in bash 3.1
< case $BASH_VERSION in
< [12].* | 3.0 | 3.0*) ;;
< *)
< : ${_G_HAVE_PLUSEQ_OP="yes"}
< ;;
< esac
< fi
<
< # _G_HAVE_PLUSEQ_OP
< # Can be empty, in which case the shell is probed, "yes" if += is
< # useable or anything else if it does not work.
< test -z "$_G_HAVE_PLUSEQ_OP" \
< && (eval 'x=a; x+=" b"; test "a b" = "$x"') 2>/dev/null \
< &&
Bug#1038776: marked as done (dcmtk: fails to purge: rm: cannot remove '/var/lib/dcmtk/db/STORESCP': Is a directory)
Your message dated Mon, 22 Apr 2024 17:02:08 + with message-id and subject line Bug#1038776: fixed in dcmtk 3.6.7-9~deb12u1 has caused the Debian Bug report #1038776, regarding dcmtk: fails to purge: rm: cannot remove '/var/lib/dcmtk/db/STORESCP': Is a 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.) -- 1038776: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1038776 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: dcmtk Version: 3.6.7-8 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to purge if the installation originated in jessie or before: >From the attached log (scroll to the bottom...): (Reading database ... 10105 files and directories currently installed.) Purging configuration files for dcmtk (3.6.7-8+b1) ... rm: cannot remove '/var/lib/dcmtk/db/STORESCP': Is a directory dpkg: error processing package dcmtk (--purge): installed dcmtk package post-removal script subprocess returned error exit status 1 Errors were encountered while processing: dcmtk The postrm contains if [ -d /var/lib/dcmtk/db/STORESCP ]; then rm -f /var/lib/dcmtk/db/STORESCP fi This directory only exists on upgrades from the jessie version or earlier. cheers, Andreas dcmtk_3.6.7-8+b1.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: dcmtk Source-Version: 3.6.7-9~deb12u1 Done: Andreas Beckmann We believe that the bug you reported is fixed in the latest version of dcmtk, 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 1038...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Beckmann (supplier of updated dcmtk 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, 19 Apr 2024 13:38:32 +0200 Source: dcmtk Architecture: source Version: 3.6.7-9~deb12u1 Distribution: bookworm Urgency: medium Maintainer: Debian Med Packaging Team Changed-By: Andreas Beckmann Closes: 1038776 Changes: dcmtk (3.6.7-9~deb12u1) bookworm; urgency=medium . * Team upload. * Rebuild for bookworm. . dcmtk (3.6.7-9) unstable; urgency=medium . * Team upload. * Fix postrm Closes: #1038776 Checksums-Sha1: 2b250ec7cf930ed1267cc98123a16e03aa406645 2349 dcmtk_3.6.7-9~deb12u1.dsc 8cf2df9d490e0ce0e7d8944e084471b3d2292d36 40828 dcmtk_3.6.7-9~deb12u1.debian.tar.xz 91396b238f61ce74d54dfdc85dae6aa083022b42 7802 dcmtk_3.6.7-9~deb12u1_source.buildinfo Checksums-Sha256: cd9c012c5a332d41c826eeb1567e486fcaa72c31ee4cde72db04cc45cd61a808 2349 dcmtk_3.6.7-9~deb12u1.dsc be1c74ac0c18c4d8cef3eff770b415479112bd25133189bee2f03043c194d652 40828 dcmtk_3.6.7-9~deb12u1.debian.tar.xz 03264ff59aad4f19511e585c996ee1f21c3bc431832ed2b832a9b79216a6cf61 7802 dcmtk_3.6.7-9~deb12u1_source.buildinfo Files: fb28e30524dee82ec2a0a95a22f80746 2349 science optional dcmtk_3.6.7-9~deb12u1.dsc a66d8bd4254fabecd699d6fcf0e4f81f 40828 science optional dcmtk_3.6.7-9~deb12u1.debian.tar.xz 22d5dee9a35f038f9e8a64ae2052ccc2 7802 science optional dcmtk_3.6.7-9~deb12u1_source.buildinfo -BEGIN PGP SIGNATURE- iQJEBAEBCAAuFiEE6/MKMKjZxjvaRMaUX7M/k1np7QgFAmYiWEwQHGFuYmVAZGVi aWFuLm9yZwAKCRBfsz+TWentCP0sEACAvysdi7KkKQne/du020vrakIwVSzltutg VRL1JHzGOC/5c7hsyo6t/rANO1AM1kwCfZvDkjbsg2NAfNVGvUZZfjljFoak2M0l LPAxzPqLolfHoxrRnJ0XnznWQu9PyA/jXlfCpVgVLK06h8CsAAc3sv6zPSBOAI1W ZuEgXxGmLdciQ+en2x1m2Jz7A4LpVRLYelCmlMk6auUvZnpNudbwV4v3H9wIrfAa QqtNvSoBv7knRk8EHiFUHbXTa8s8NS2jQgWFRIFciCeKvZsGwiF8PeAPxv9HO5SO oR5oerr12IVRVOXVXTwrKMFWiWhOjG/kKPJcvUTjZStTReNkmnKtEmIZ+SbnV2BG custmDTehbTucZCLD3GDcXIuQCrxaOYXLbFpTF9JxYbJU9HUIx9OEWlnCWIk9RuJ rGOiUWaJbZuTNzltXZlmgMQM60JblS43mvBydiZ3lLinSnNipsPkV0R5+MIJHvti ++HFG01IbOcOyfDPd11yN5n1hp/r0Dkf31li7mx+IOLDWoyDGnePyv/hnkElvlGA DrSpSktcV0gWMHPbOZQri+iyMGeMsJlSA4irENios6XX9Z19eoEaJA+K25mtola+ An/YgHS1e0yYrRgboY3pSsfMRa7k4LaPBH4CQwsSbjJGub1rSpMVVthgUOZKK2M9 yo1Grn+MIA== =cRIT -END PGP SIGNATURE- pgpXlHS8xaz1O.pgp Description: PGP signature --- End Message ---
Processed: unarchive
Processing commands for cont...@bugs.debian.org:
> unarchive 1031439
Bug #1031439 {Done: John Scott } [src:gcc-sh-elf]
gcc-sh-elf: FTBFS: make[6]: *** No rule to make target
'../libsframe/libsframe.la', needed by 'libbfd.la'. Stop.
Unarchived Bug 1031439
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1031439: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031439
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1067251: librust-isahc-dev: impossible to install
On Wed, 20 Mar 2024 21:29:24 +0100 Matthias Geiger
wrote:
> Package: librust-isahc-dev
> Severity: grave
> Justification: not installable
> X-Debbugs-Cc: werdah...@riseup.net
>
Unfortunately polling 2.x to 3.x had breaking changes. This is my
attempt at a
(non-working) patch bumping polling (see attachment). Maybe you can
figure out the missing bits; this is too difficult for me.
best,
werdahias
diff --git a/Cargo.toml b/Cargo.toml
index d797d20..62ca8cd 100644
--- a/Cargo.toml
+++ b/Cargo.toml
@@ -43,7 +43,7 @@ futures-io = "0.3.24" # futures-io ecosystem compatibility
http = "0.2.1" # http ecosystem compatibility, part of API
log = "0.4" # log ecosystem compatibility
once_cell = "1" # used for a few singletons
-polling = "2" # async I/O driver
+polling = "3" # async I/O driver
sluice = "0.5.4" # byte buffers between curl and Isahc
url = "2.1" # URL parsing
waker-fn = "1" # async primitive
diff --git a/src/agent/selector.rs b/src/agent/selector.rs
index 813e708..836dd39 100644
--- a/src/agent/selector.rs
+++ b/src/agent/selector.rs
@@ -1,5 +1,5 @@
use curl::multi::Socket;
-use polling::{Event, Poller};
+use polling::{Event, Poller, Events};
use std::{
collections::{HashMap, HashSet},
io,
@@ -30,7 +30,7 @@ pub(crate) struct Selector {
/// Socket events that have occurred. We re-use this vec every call for
/// efficiency.
-events: Vec,
+events: Events,
/// Incrementing counter used to deduplicate registration operations.
tick: usize,
@@ -50,7 +50,7 @@ impl Selector {
poller: Arc::new(Poller::new()?),
sockets: HashMap::with_hasher(Default::default()),
bad_sockets: HashSet::with_hasher(Default::default()),
-events: Vec::new(),
+events: Events::new(),
tick: 0,
})
}
@@ -144,7 +144,7 @@ impl Selector {
// We don't do this immediately after polling because the caller may
// choose to de-register a socket before the next call. That's why we
// wait until the last minute.
-for event in self.events.drain(..) {
+for event in self.events.iter() {
let socket = event.key as Socket;
if let Some(registration) = self.sockets.get_mut() {
// If the socket was already re-registered this tick, then we
@@ -211,21 +211,17 @@ fn poller_add(poller: , socket: Socket, readable: bool, writable: bool) -
// operation as a modification is sufficient to handle this.
//
// This is especially common with the epoll backend.
-if let Err(e) = poller.add(socket, Event {
-key: socket as usize,
-readable,
-writable,
-}) {
+if let Err(e) = poller.add(socket,
+Event::readable(socket.try_into().unwrap()),
+) {
tracing::debug!(
"failed to add interest for socket {}, retrying as a modify: {}",
socket,
e
);
-poller.modify(socket, Event {
-key: socket as usize,
-readable,
-writable,
-})?;
+poller.modify(socket,
+Event::readable(socket.try_into().unwrap()),
+)?;
}
Ok(())
@@ -239,21 +235,17 @@ fn poller_modify(
) -> io::Result<()> {
// If this errors, we retry the operation as an add instead. This is done
// because epoll is weird.
-if let Err(e) = poller.modify(socket, Event {
-key: socket as usize,
-readable,
-writable,
-}) {
+if let Err(e) = poller.modify(socket,
+Event::readable(socket.try_into().unwrap()),
+) {
tracing::debug!(
"failed to modify interest for socket {}, retrying as an add: {}",
socket,
e
);
-poller.add(socket, Event {
-key: socket as usize,
-readable,
-writable,
-})?;
+poller.add(socket,
+Event::readable(socket.try_into().unwrap()),
+)?;
}
Ok(())
Bug#1069642: Same error
Today raised same error on my colleague's two laptops and on one server with this kernel. It was not possible to boot, only with older kernel.
Bug#1069679: ofono: CVE-2023-2794
Source: ofono X-Debbugs-CC: t...@security.debian.org Severity: grave Tags: security Hi, The following vulnerability was published for ofono. CVE-2023-2794[0]: | A flaw was found in ofono, an Open Source Telephony on Linux. A | stack overflow bug is triggered within the decode_deliver() function | during the SMS decoding. It is assumed that the attack scenario is | accessible from a compromised modem, a malicious base station, or | just SMS. There is a bound check for this memcpy length in | decode_submit(), but it was forgotten in decode_deliver(). https://bugzilla.redhat.com/show_bug.cgi?id=2255387 https://git.kernel.org/pub/scm/network/ofono/ofono.git/commit/?id=a90421d8e45d63b304dc010baba24633e7869682 https://git.kernel.org/pub/scm/network/ofono/ofono.git/commit/?id=7f2adfa22fbae824f8e2c3ae86a3f51da31ee400 https://git.kernel.org/pub/scm/network/ofono/ofono.git/commit/?id=07f48b23e3877ef7d15a7b0b8b79d32ad0a3607e https://git.kernel.org/pub/scm/network/ofono/ofono.git/commit/?id=8fa1fdfcb54e1edb588c6a5e260b065a39c9 If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2023-2794 https://www.cve.org/CVERecord?id=CVE-2023-2794 Please adjust the affected versions in the BTS as needed.
Bug#1069677: rust-rustls: CVE-2024-32650
Source: rust-rustls X-Debbugs-CC: t...@security.debian.org Severity: grave Tags: security Hi, The following vulnerability was published for rust-rustls. CVE-2024-32650[0]: | Rustls is a modern TLS library written in Rust. | `rustls::ConnectionCommon::complete_io` could fall into an infinite | loop based on network input. When using a blocking rustls server, if | a client send a `close_notify` message immediately after | `client_hello`, the server's `complete_io` will get in an infinite | loop. This vulnerability is fixed in 0.23.5, 0.22.4, and 0.21.11. https://github.com/rustls/rustls/security/advisories/GHSA-6g7w-8wpp-frhj https://github.com/rustls/rustls/commit/2123576840aa31043a31b0770e6572136fbe0c2d (v/0.23.5) https://github.com/rustls/rustls/commit/6e938bcfe82a9da7a2e1cbf10b928c7eca26426e (v/0.23.5) https://rustsec.org/advisories/RUSTSEC-2024-0336.html If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2024-32650 https://www.cve.org/CVERecord?id=CVE-2024-32650 Please adjust the affected versions in the BTS as needed.
Bug#1069678: openjdk-8: CVE-2024-21011 CVE-2024-21068 CVE-2024-21085 CVE-2024-21094
Source: openjdk-8 X-Debbugs-CC: t...@security.debian.org Severity: grave Tags: security Hi, The following vulnerabilities were published for openjdk-8. CVE-2024-21011[0]: | Vulnerability in the Oracle Java SE, Oracle GraalVM for JDK, Oracle | GraalVM Enterprise Edition product of Oracle Java SE (component: | Hotspot). Supported versions that are affected are Oracle Java SE: | 8u401, 8u401-perf, 11.0.22, 17.0.10, 21.0.2, 22; Oracle GraalVM for | JDK: 17.0.10, 21.0.2, 22; Oracle GraalVM Enterprise Edition: | 20.3.13 and 21.3.9. Difficult to exploit vulnerability allows | unauthenticated attacker with network access via multiple protocols | to compromise Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM | Enterprise Edition. Successful attacks of this vulnerability can | result in unauthorized ability to cause a partial denial of service | (partial DOS) of Oracle Java SE, Oracle GraalVM for JDK, Oracle | GraalVM Enterprise Edition. Note: This vulnerability can be | exploited by using APIs in the specified Component, e.g., through a | web service which supplies data to the APIs. This vulnerability also | applies to Java deployments, typically in clients running sandboxed | Java Web Start applications or sandboxed Java applets, that load and | run untrusted code (e.g., code that comes from the internet) and | rely on the Java sandbox for security. CVSS 3.1 Base Score 3.7 | (Availability impacts). CVSS Vector: | (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L). CVE-2024-21068[1]: | Vulnerability in the Oracle Java SE, Oracle GraalVM for JDK, Oracle | GraalVM Enterprise Edition product of Oracle Java SE (component: | Hotspot). Supported versions that are affected are Oracle Java SE: | 8u401-perf, 11.0.22, 17.0.10, 21.0.2, 22; Oracle GraalVM for JDK: | 17.0.10, 21.0.2 and 22; Oracle GraalVM Enterprise Edition: 21.3.9. | Difficult to exploit vulnerability allows unauthenticated attacker | with network access via multiple protocols to compromise Oracle Java | SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition. | Successful attacks of this vulnerability can result in unauthorized | update, insert or delete access to some of Oracle Java SE, Oracle | GraalVM for JDK, Oracle GraalVM Enterprise Edition accessible data. | Note: This vulnerability can be exploited by using APIs in the | specified Component, e.g., through a web service which supplies data | to the APIs. This vulnerability also applies to Java deployments, | typically in clients running sandboxed Java Web Start applications | or sandboxed Java applets, that load and run untrusted code (e.g., | code that comes from the internet) and rely on the Java sandbox for | security. CVSS 3.1 Base Score 3.7 (Integrity impacts). CVSS Vector: | (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N). CVE-2024-21085[2]: | Vulnerability in the Oracle Java SE, Oracle GraalVM Enterprise | Edition product of Oracle Java SE (component: Concurrency). | Supported versions that are affected are Oracle Java SE: 8u401, | 8u401-perf, 11.0.22; Oracle GraalVM Enterprise Edition: 20.3.13 and | 21.3.9. Difficult to exploit vulnerability allows unauthenticated | attacker with network access via multiple protocols to compromise | Oracle Java SE, Oracle GraalVM Enterprise Edition. Successful | attacks of this vulnerability can result in unauthorized ability to | cause a partial denial of service (partial DOS) of Oracle Java SE, | Oracle GraalVM Enterprise Edition. Note: This vulnerability can be | exploited by using APIs in the specified Component, e.g., through a | web service which supplies data to the APIs. This vulnerability also | applies to Java deployments, typically in clients running sandboxed | Java Web Start applications or sandboxed Java applets, that load and | run untrusted code (e.g., code that comes from the internet) and | rely on the Java sandbox for security. CVSS 3.1 Base Score 3.7 | (Availability impacts). CVSS Vector: | (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L). CVE-2024-21094[3]: | Vulnerability in the Oracle Java SE, Oracle GraalVM for JDK, Oracle | GraalVM Enterprise Edition product of Oracle Java SE (component: | Hotspot). Supported versions that are affected are Oracle Java SE: | 8u401, 8u401-perf, 11.0.22, 17.0.10, 21.0.2, 22; Oracle GraalVM for | JDK: 17.0.10, 21.0.2, 22; Oracle GraalVM Enterprise Edition: 20.3.13 | and 21.3.9. Difficult to exploit vulnerability allows | unauthenticated attacker with network access via multiple protocols | to compromise Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM | Enterprise Edition. Successful attacks of this vulnerability can | result in unauthorized update, insert or delete access to some of | Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise | Edition accessible data. Note: This vulnerability can be exploited | by using APIs in the specified Component, e.g., through a web | service which supplies data to the APIs. This vulnerability also | applies to Java
Processed: Re: pylint: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13
Processing commands for cont...@bugs.debian.org:
> # Given the diff between sid vs testing is literally just a maintainer
> # chance, it is safe to assume the bug is also in testing
> found 1066755 3.0.3-1
Bug #1066755 [src:pylint] pylint: FTBFS: dh_auto_test: error: pybuild --test
--test-pytest -i python{version} -p "3.12 3.11" returned exit code 13
Marked as found in versions pylint/3.0.3-1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1066755: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066755
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1069471: marked as done (nfs-ganesha: FTBFS on 32-bit: build-dependency not installable: libcephfs-dev)
Your message dated Mon, 22 Apr 2024 13:34:33 + with message-id and subject line Bug#1069471: fixed in nfs-ganesha 4.3-9 has caused the Debian Bug report #1069471, regarding nfs-ganesha: FTBFS on 32-bit: build-dependency not installable: libcephfs-dev 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.) -- 1069471: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069471 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: nfs-ganesha Version: 4.3-8 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-armhf Hi, During a rebuild of all packages in sid, your package failed to build on armhf. Relevant part (hopefully): > +--+ > | Install package build dependencies > | > +--+ > > > Setup apt archive > - > > Merged Build-Depends: bison, cmake, debhelper (>= 10), dh-python, flex, > libacl1-dev, libattr1-dev, libblkid-dev, libcap-dev, libcephfs-dev, > libdbus-1-dev, libkrb5-dev, liblttng-ctl-dev, liblttng-ust-dev, > libnfsidmap-dev, libntirpc-dev (>= 4.3), libpython3-all-dev, liburcu-dev, > libwbclient-dev, lttng-tools, pkgconf, pyqt5-dev-tools, python3-all-dev, > python3-pyqt5, python3-setuptools, python3-sphinx, uuid-dev, xfslibs-dev, > build-essential, fakeroot > Filtered Build-Depends: bison, cmake, debhelper (>= 10), dh-python, flex, > libacl1-dev, libattr1-dev, libblkid-dev, libcap-dev, libcephfs-dev, > libdbus-1-dev, libkrb5-dev, liblttng-ctl-dev, liblttng-ust-dev, > libnfsidmap-dev, libntirpc-dev (>= 4.3), libpython3-all-dev, liburcu-dev, > libwbclient-dev, lttng-tools, pkgconf, pyqt5-dev-tools, python3-all-dev, > python3-pyqt5, python3-setuptools, python3-sphinx, uuid-dev, xfslibs-dev, > build-essential, fakeroot > dpkg-deb: building package 'sbuild-build-depends-main-dummy' in > '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'. > Ign:1 copy:/<>/apt_archive ./ InRelease > Get:2 copy:/<>/apt_archive ./ Release [615 B] > Ign:3 copy:/<>/apt_archive ./ Release.gpg > Get:4 copy:/<>/apt_archive ./ Sources [1202 B] > Get:5 copy:/<>/apt_archive ./ Packages [1028 B] > Fetched 2845 B in 0s (0 B/s) > Reading package lists... > Reading package lists... > > Install main build dependencies (apt-based resolver) > > > Installing build dependencies > Reading package lists... > Building dependency tree... > Reading state information... > Some packages could not be installed. This may mean that you have > requested an impossible situation or if you are using the unstable > distribution that some required packages have not yet been created > or been moved out of Incoming. > The following information may help to resolve the situation: > > The following packages have unmet dependencies: > sbuild-build-depends-main-dummy : Depends: libcephfs-dev but it is not > installable > E: Unable to correct problems, you have held broken packages. > apt-get failed. The full build log is available from: http://qa-logs.debian.net/2024/04/20/nfs-ganesha_4.3-8_unstable-armhf.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: nfs-ganesha Source-Version: 4.3-9 Done: Christoph Martin We believe that the bug you reported is fixed in the latest version of nfs-ganesha, 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. Christoph Martin
Bug#1069646: marked as done (python-glance-store - Build-depends on deprecated package: python3-boto)
Your message dated Mon, 22 Apr 2024 12:34:36 + with message-id and subject line Bug#1069646: fixed in python-glance-store 4.7.0-4 has caused the Debian Bug report #1069646, regarding python-glance-store - Build-depends on deprecated package: python3-boto 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.) -- 1069646: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069646 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python-glance-store Version: 4.7.0-2 Severity: serious python-glance-store build-depends on deprecated package python3-boto. See #1058652 Also it seems to not build at all: | dpkg-buildpackage: info: source package python-glance-store | dpkg-buildpackage: info: source version 4.7.0-2 | dpkg-buildpackage: info: source distribution unstable | dpkg-buildpackage: info: source changed by Thomas Goirand | dpkg-source --before-build . | dpkg-source: info: using options from source/debian/source/options: --extend-diff-ignore=^[^/]*[.]egg-info/ | /bin/true debian/rules clean | debian/rules build-indep | make: pyversions: No such file or directory | py3versions: no X-Python3-Version in control file, using supported versions | dh build-indep --buildsystem=python_distutils --with python3,sphinxdoc | dh_auto_configure: warning: Please use the third-party "pybuild" build system instead of python-distutils | dh_auto_configure: warning: This feature will be removed in compat 12. | make[1]: pyversions: No such file or directory | py3versions: no X-Python3-Version in control file, using supported versions | echo "Do nothing..." | Do nothing... | make[1]: pyversions: No such file or directory | py3versions: no X-Python3-Version in control file, using supported versions | echo "Do nothing..." | Do nothing... |create-stamp debian/debhelper-build-stamp | /bin/true debian/rules binary-indep | dpkg-genbuildinfo --build=all -O../python-glance-store_4.7.0-2_all.buildinfo | dpkg-genbuildinfo: error: binary build with no binary artifacts found; .buildinfo is meaningless | dpkg-buildpackage: error: dpkg-genbuildinfo --build=all -O../python-glance-store_4.7.0-2_all.buildinfo subprocess returned exit status 255 Bastian -- ... bacteriological warfare ... hard to believe we were once foolish enough to play around with that. -- McCoy, "The Omega Glory", stardate unknown --- End Message --- --- Begin Message --- Source: python-glance-store Source-Version: 4.7.0-4 Done: Thomas Goirand We believe that the bug you reported is fixed in the latest version of python-glance-store, 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. Thomas Goirand (supplier of updated python-glance-store package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 22 Apr 2024 14:12:33 +0200 Source: python-glance-store Architecture: source Version: 4.7.0-4 Distribution: unstable Urgency: medium Maintainer: Debian OpenStack Changed-By: Thomas Goirand Closes: 1069646 Changes: python-glance-store (4.7.0-4) unstable; urgency=medium . * Remove build-depends on python3-boto (Closes: #1069646). Checksums-Sha1: 2899e9d09776973ef6d2172d5febd173cb9dc46d 3167 python-glance-store_4.7.0-4.dsc a4e4c33c7136d0abf5ae6387bc3dba893504d9b5 6552 python-glance-store_4.7.0-4.debian.tar.xz 8532a3978f7897d04a4ccfc7c32050ed3b20001c 14402 python-glance-store_4.7.0-4_amd64.buildinfo Checksums-Sha256: 560132b7e58a47710fef77d5d364b0c101e48eb9405df1f1e48f11d52fac265e 3167 python-glance-store_4.7.0-4.dsc 159ffa1fe1229e8e2fc53de57796bb073a18f285831306d294b650325768d045 6552 python-glance-store_4.7.0-4.debian.tar.xz 66dca5e6750d20b947b97ce9da1307daed64b46cf5e67b87b749db04f2fb48c5 14402 python-glance-store_4.7.0-4_amd64.buildinfo Files: a3d8c44b9410d81b92162e62bb6abc39 3167 python optional python-glance-store_4.7.0-4.dsc fc9c09c3071ea10324ac3e0df9fcee64 6552 python optional python-glance-store_4.7.0-4.debian.tar.xz 4c05975dfb4e9d3624ce9f62bfd5a9e0 14402 python optional python-glance-store_4.7.0-4_amd64.buildinfo -BEGIN PGP SIGNATURE-
Bug#1069646: marked as pending in python-glance-store
Control: tag -1 pending Hello, Bug #1069646 in python-glance-store 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/openstack-team/libs/python-glance-store/-/commit/a07d7150bbbc8141cb975847ddd1377e23a4d297 Remove build-depends on python3-boto (Closes: #1069646). (this message was generated automatically) -- Greetings https://bugs.debian.org/1069646
Processed: Bug#1069646 marked as pending in python-glance-store
Processing control commands: > tag -1 pending Bug #1069646 [python-glance-store] python-glance-store - Build-depends on deprecated package: python3-boto Added tag(s) pending. -- 1069646: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069646 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1069336: marked as done (Not installable due to hardcoded pre-t64 library deps)
Your message dated Mon, 22 Apr 2024 12:05:44 + with message-id and subject line Bug#1069336: fixed in seafile-client 9.0.5+ds1-1 has caused the Debian Bug report #1069336, regarding Not installable due to hardcoded pre-t64 library deps 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.) -- 1069336: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069336 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: seafile-gui Version: 9.0.4+ds1-1+b4 Severity: grave seafile-gui explicitly Depends: libsearpc1, libseafile0. They should be changed to the t64 names if they are really needed. -- System Information: Debian Release: trixie/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'unstable'), (500, 'testing'), (101, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.7.9-amd64 (SMP w/16 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages seafile-gui depends on: ii libc6 2.37-18 ii libgcc-s1 14-20240330-1 ii libglib2.0-0t64 [libglib2.0-0] 2.78.4-6 ii libjansson4 2.14-2+b2 ii libqt5core5t64 [libqt5core5a] 5.15.10+dfsg-7.2+b1 ii libqt5dbus5t64 [libqt5dbus5]5.15.10+dfsg-7.2+b1 ii libqt5gui5t64 [libqt5gui5] 5.15.10+dfsg-7.2+b1 ii libqt5network5t64 [libqt5network5] 5.15.10+dfsg-7.2+b1 ii libqt5webkit5 5.212.0~alpha4-33+b3 ii libqt5widgets5t64 [libqt5widgets5] 5.15.10+dfsg-7.2+b1 pn libquazip5-1 pn libquazip5-1t64 pn libseafile0 pn libseafile0t64 pn libsearpc1 pn libsearpc1t64 ii libsqlite3-03.45.3-1 ii libstdc++6 14-20240330-1 pn seafile-daemon seafile-gui recommends no packages. Versions of packages seafile-gui suggests: pn seafile-cli --- End Message --- --- Begin Message --- Source: seafile-client Source-Version: 9.0.5+ds1-1 Done: Moritz Schlarb We believe that the bug you reported is fixed in the latest version of seafile-client, 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. Moritz Schlarb (supplier of updated seafile-client package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 22 Apr 2024 13:42:46 +0200 Source: seafile-client Architecture: source Version: 9.0.5+ds1-1 Distribution: unstable Urgency: medium Maintainer: Debian Seafile Team Changed-By: Moritz Schlarb Closes: 1069336 Changes: seafile-client (9.0.5+ds1-1) unstable; urgency=medium . * New upstream version 9.0.5+ds1 * Refresh patches * Update CI config * Fix Dependencies (Closes: #1069336) Checksums-Sha1: 39f5250d004f139d1ca3df4ece1e35c50c6721bb 2359 seafile-client_9.0.5+ds1-1.dsc 340a10a8bd715070ea899613f50b4f1cc537ece5 1693216 seafile-client_9.0.5+ds1.orig.tar.xz a4d9620d11f5df08d6904b84359096810a1f2bb1 9684 seafile-client_9.0.5+ds1-1.debian.tar.xz 6f4c717829e627289a17985dc8d714e238acbc4b 15340 seafile-client_9.0.5+ds1-1_amd64.buildinfo Checksums-Sha256: b12eb008f299a0cc379d9a40662cfbc3861c3d411e659e2cf2dbfbdceb17b22d 2359 seafile-client_9.0.5+ds1-1.dsc f22d2f20b3ed04c9f8a995560c8c60b0e75b034dc346bc0b31d0fa727de77630 1693216 seafile-client_9.0.5+ds1.orig.tar.xz 517b52cd859608b0c1372e4d25a946539b540207e17e85c682b78608c932dcf2 9684 seafile-client_9.0.5+ds1-1.debian.tar.xz 65b21504ff327104f6a92da77038e7b3429477ee1c4b04171633154240c9c86d 15340 seafile-client_9.0.5+ds1-1_amd64.buildinfo Files: f901e43b185537d5ce615ad16f7e3276 2359 net optional seafile-client_9.0.5+ds1-1.dsc a69d989181f89a9973cdcc58effeb5e6 1693216 net
Bug#1069336: marked as pending in seafile-client
Control: tag -1 pending Hello, Bug #1069336 in seafile-client 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/debian/seafile-client/-/commit/758facd2f3c3ec44da432885c5e0cdc629d8bab8 Fix Dependencies (Closes: #1069336) (this message was generated automatically) -- Greetings https://bugs.debian.org/1069336
Processed: Bug#1069336 marked as pending in seafile-client
Processing control commands: > tag -1 pending Bug #1069336 [seafile-gui] Not installable due to hardcoded pre-t64 library deps Added tag(s) pending. -- 1069336: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069336 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: severity 1068657
Processing commands for cont...@bugs.debian.org:
> severity 1068657 normal
Bug #1068657 {Done: Luca Boccassi } [src:pkcs11-provider]
pkcs11-provider FTBFS with openssl 3.2.1-3
Severity set to 'normal' from 'serious'
>
End of message, stopping processing here.
Please contact me if you need assistance.
--
1068657: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068657
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1068959: marked as done (py-ubjson: FTBFS: testsuite failure: FAILED (failures=2))
Your message dated Mon, 22 Apr 2024 10:35:41 + with message-id and subject line Bug#1068959: fixed in py-ubjson 0.16.1-4 has caused the Debian Bug report #1068959, regarding py-ubjson: FTBFS: testsuite failure: FAILED (failures=2) to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1068959: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068959 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: py-ubjson Version: 0.16.1-3 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) Dear maintainer, py-ubjson fails to build from source due to errors in the testsuite. >From my build log on amd64: | == | FAIL: test_recursion (test.TestEncodeDecodeFpExt.test_recursion) | -- | Traceback (most recent call last): | File "/<>/.pybuild/cpython3_3.12_ubjson/build/test/test.py", line 476, in test_recursion | with self.assert_raises_regex(RuntimeError, 'recursion'): | AssertionError: RuntimeError not raised | | == | FAIL: test_recursion (test.TestEncodeDecodePlainExt.test_recursion) | -- | Traceback (most recent call last): | File "/<>/.pybuild/cpython3_3.12_ubjson/build/test/test.py", line 476, in test_recursion | with self.assert_raises_regex(RuntimeError, 'recursion'): | AssertionError: RuntimeError not raised | | -- | Ran 116 tests in 2.212s | | FAILED (failures=2) | E: pybuild pybuild:389: test: plugin distutils failed with: exit code=1: cd /<>/.pybuild/cpython3_3.12_ubjson/build; python3.12 -m unittest discover -v test/ A full build log on riscv64 is available here: https://buildd.debian.org/status/fetch.php?pkg=py-ubjson=riscv64=0.16.1-3%2Bb1=1713019530=0 Full build logs on amd64 and arm64 are also available on reproducible builds: https://tests.reproducible-builds.org/debian/rbuild/unstable/amd64/py-ubjson_0.16.1-3.rbuild.log.gz https://tests.reproducible-builds.org/debian/rbuild/unstable/arm64/py-ubjson_0.16.1-3.rbuild.log.gz Regards Aurelien --- End Message --- --- Begin Message --- Source: py-ubjson Source-Version: 0.16.1-4 Done: Jérémy Lal We believe that the bug you reported is fixed in the latest version of py-ubjson, 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. Jérémy Lal (supplier of updated py-ubjson package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 22 Apr 2024 12:13:27 +0200 Source: py-ubjson Architecture: source Version: 0.16.1-4 Distribution: unstable Urgency: medium Maintainer: Debian Python Team Changed-By: Jérémy Lal Closes: 1068959 Changes: py-ubjson (0.16.1-4) unstable; urgency=medium . * Team upload * Update patch for python 3.12 compatibility. Closes: #1068959. Checksums-Sha1: f6ace0039966356bab2d6ab868f87a8a01849730 2432 py-ubjson_0.16.1-4.dsc 5ad2662db8cb460922c03bcd78141ea1ad5ff733 6856 py-ubjson_0.16.1-4.debian.tar.xz 08ffdb0ab33c7e288096b3657e3c7462b2c5bba4 8447 py-ubjson_0.16.1-4_source.buildinfo Checksums-Sha256: fd9a53aa8b1798239b0852abedeb86364a47fca3b1145f5f00fafe61736ab8c3 2432 py-ubjson_0.16.1-4.dsc ea74c93adba45abc9c75a80b3eed9e7eb7ad7c8589fd900dce03866b075e242d 6856 py-ubjson_0.16.1-4.debian.tar.xz 0abecf3a0c80971be7be413adedd1505ffce606d8c5d6db2e66abc07c9b1bcee 8447 py-ubjson_0.16.1-4_source.buildinfo Files: 7b57fe1b9387034c77eb87097615de07 2432 python optional py-ubjson_0.16.1-4.dsc 9675dd411e6e10b782a92239db20e8c4 6856 python optional py-ubjson_0.16.1-4.debian.tar.xz 0c4ac3c783314a2c7c55d350a9f08c85 8447 python optional py-ubjson_0.16.1-4_source.buildinfo -BEGIN PGP SIGNATURE- iQJGBAEBCAAwFiEEA8Tnq7iA9SQwbkgVZhHAXt0583QFAmYmOTUSHGthcG91ZXJA bWVsaXgub3JnAAoJEGYRwF7dOfN0DqkP/R2sNLw259ZT8sxFGmUSDMsh7N4slM0K
Bug#1066491: libt3window: FTBFS: .config.c:8:13: error: implicit declaration of function ‘setupterm’; did you mean ‘set_term’? [-Werror=implicit-function-declaration]
Hi,
On Wed, Mar 13, 2024 at 12:52:51PM +0100, Lucas Nussbaum wrote:
https://wiki.debian.org/qa.debian.org/FTBFS#A2024-03-13_-Werror.3Dimplicit-function-declaration
Relevant part (hopefully):
gcc -g -O2 -Werror=implicit-function-declaration
-ffile-prefix-map=/<>=. -fstack-protector-strong
-fstack-clash-protection -Wformat -Werror=format-security -fcf-protection `pkg-config
--cflags tinfo` -c -o .config.o .config.c
.config.c: In function ‘main’:
.config.c:8:13: error: implicit declaration of function ‘setupterm’; did you
mean ‘set_term’? [-Werror=implicit-function-declaration]
8 | if (setupterm(NULL, fd, ) == OK) {
| ^
| set_term
.config.c:12:17: error: implicit declaration of function ‘tputs’; did you mean
‘puts’? [-Werror=implicit-function-declaration]
12 | tputs("\033[0m", 1, putchar);
| ^
| puts
cc1: some warnings being treated as errors
make[2]: *** [.Makefile:19: .config.o] Error 1
I have sent one RFS[0] to fix the issue.
[0]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069662
Regards,
--
Bo YU
signature.asc
Description: PGP signature
Bug#1065435: closed by Debian FTP Masters (reply to Julian Andres Klode ) (Bug#1065435: fixed in aptitude 0.8.13-6)
On Sat, Mar 23, 2024 at 11:21:07AM +, Debian Bug Tracking System wrote:
> This is an automatic notification regarding your Bug report
> which was filed against the src:aptitude package:
>
> #1065435: aptitude: FTBFS on armhf and armel: deduced conflicting types for
> parameter ‘const T’ (‘long int’ and ‘__suseconds64_t’ {aka ‘long long int’})
>
> It has been closed by Debian FTP Masters
> (reply to Julian Andres Klode ).
>
> Their explanation is attached below along with your original report.
> If this explanation is unsatisfactory and you have not received a
> better one in a separate message then please contact Debian FTP Masters
> (reply to Julian Andres Klode
> ) by
> replying to this email.
I was told to ping the bug to prevent autoremoval, so doing this
--
debian developer - deb.li/jak | jak-linux.org - free software dev
ubuntu core developer i speak de, en
signature.asc
Description: PGP signature
Bug#1053334: galera-4: FTBFS because of expired certificates
El 22/4/24 a las 8:47, Otto Kekäläinen escribió: I was able to reproduce this for Bookworm both locally and in CI at https://salsa.debian.org/mariadb-team/galera-4/-/jobs/5620032 After importing latest upstream build/test passes: https://salsa.debian.org/otto/galera/-/jobs/5624466 Stable upload request filed at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069639 Thanks a lot! What about bullseye, which is also a supported distribution? I have not reached the point where I want to do NMUs for these kind of bugs, but if this were my package, I would certainly do an upload for bullseye as well. If I can be of any help, please say so. Thanks.
Processed: tagging 1007026
Processing commands for cont...@bugs.debian.org: > tags 1007026 + ftbfs Bug #1007026 [rust-weedle] rust-weedle - needs nom 5 Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 1007026: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1007026 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1069631: marked as done (loki-ecmwf: Unsatisfiable dependency: python3-loki etc)
Your message dated Mon, 22 Apr 2024 09:19:29 + with message-id and subject line Bug#1069631: fixed in loki-ecmwf 0.2.1-2 has caused the Debian Bug report #1069631, regarding loki-ecmwf: Unsatisfiable dependency: python3-loki etc 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.) -- 1069631: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069631 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: loki-ecmwf Version: 0.2.0-1 Severity: serious After https://salsa.debian.org/science-team/loki-ecmwf/-/commit/fd228e81dcb, python3-loki-ecmwf-lint-rules has Depends: python3-loki but that package is not available in Debian. https://qa.debian.org/excuses.php?package=loki-ecmwf complains about other uninstallable packages but I did not check them. Thank you, Jeremy Bícha --- End Message --- --- Begin Message --- Source: loki-ecmwf Source-Version: 0.2.1-2 Done: Alastair McKinstry We believe that the bug you reported is fixed in the latest version of loki-ecmwf, 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. Alastair McKinstry (supplier of updated loki-ecmwf package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 22 Apr 2024 09:43:41 +0100 Source: loki-ecmwf Architecture: source Version: 0.2.1-2 Distribution: unstable Urgency: medium Maintainer: Alastair McKinstry Changed-By: Alastair McKinstry Closes: 1069631 Changes: loki-ecmwf (0.2.1-2) unstable; urgency=medium . * Fix py3dist-overrides for incorrect dep on python3-loki. Closes: #1069631 Checksums-Sha1: 1f8e848c08501a0169e144095218de43c3d2fcf9 2697 loki-ecmwf_0.2.1-2.dsc bfc82d742425b8c1c9064f27b4a7ed83504ef414 3792 loki-ecmwf_0.2.1-2.debian.tar.xz Checksums-Sha256: 83abb3d6f9165a10cbd4cfda54aabdf82af028beb8cdceb4ebdf6cc4a15086ab 2697 loki-ecmwf_0.2.1-2.dsc ec8a144a269369a7f77c0ce9a2ff0a463c66b7ca1c308bb634c41fcc93e8f4a5 3792 loki-ecmwf_0.2.1-2.debian.tar.xz Files: f49cbb9124a54ded091e5105db6e284c 2697 python optional loki-ecmwf_0.2.1-2.dsc 3a4206228aee70282e43fc3d638f1887 3792 python optional loki-ecmwf_0.2.1-2.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEgjg86RZbNHx4cIGiy+a7Tl2a06UFAmYmJD4ACgkQy+a7Tl2a 06U9iw//cWssGf7V6M/3YPX5G57Un4VoLLGq/s7AuG/cWhfvwdyvHHT1xuv72/rE jJIwuh9Ay8sQUSW9rXgxs2qcYD2hznMASuu4lMxYmYcP2tLhgq3ohEPa7y1ojNYY ACC7dsOqKp+lJ59KNXIrGxRDwc65dUuqTNR6tTndL4p69sEQIx8FJwV7EuIZ3YGq pV5ZARP7uim7TAa0r84jIKFncnkIVOuCnf7oF9MjVqaiqlMGjvOC+pnpb3uPr5iW oxVfkiytnHAq1pA9gX6Y4GzgfDsRkBjlWdNDiE+Zx0RoQ9aSqLpL9r0z/ijcT/Oo 6DL8kZ3d4k8yUPi55XfoOkZmMJZGYWG4RZ2RY8jqk/JCLGAFFL60KHdADFCs0Raj 9VRD6OdhKgFB9jNgSPC3h3LKO5l8i228/kBiwYXY6XISZZRhYzBQ2X9Kfi1v6T4j UXcNiU+20g8kh4uR+p4VEpOHe/yl06idd7JfeK3KaWPB9HxOlAzw5WAA536X4z50 9YCYBx4Cc8DxlfsEaGE3As8dDBisX2u8FnaLU5qBrQP+i0GqRsNYMJrnk6pGGaFJ qkyQAt7HQ9xTXzwpZCY4o/Niyiu4FbI3vxjEXy96GhcvR7/8zNHvMl3yUQYYwqEU T1Q0dg6TE4AbAcwdbdwRwxdxK85MFYLzKXKjvd0MQ3wrRvU6+KQ= =YWX9 -END PGP SIGNATURE- pgpHCISdSuILG.pgp Description: PGP signature --- End Message ---
Bug#1069465: marked as done (libeatmydata: FTBFS on armhf: features-time64.h:26:5: error: #error "_TIME_BITS=64 is allowed only with _FILE_OFFSET_BITS=64")
Your message dated Mon, 22 Apr 2024 09:19:20 + with message-id and subject line Bug#1069465: fixed in libeatmydata 131-2 has caused the Debian Bug report #1069465, regarding libeatmydata: FTBFS on armhf: features-time64.h:26:5: error: #error "_TIME_BITS=64 is allowed only with _FILE_OFFSET_BITS=64" 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.) -- 1069465: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069465 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libeatmydata Version: 131-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-armhf Hi, During a rebuild of all packages in sid, your package failed to build on armhf. Relevant part (hopefully): > /bin/bash ./libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. > -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time > -D_FORTIFY_SOURCE=2 -DBUILDING_LIBEATMYDATA -g -O2 > -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. > -fstack-protector-strong -fstack-clash-protection -Wformat > -Werror=format-security -c -o libeatmydata/la-libeatmydata.lo `test -f > 'libeatmydata/libeatmydata.c' || echo './'`libeatmydata/libeatmydata.c > libtool: compile: gcc -DHAVE_CONFIG_H -I. -D_LARGEFILE_SOURCE > -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 > -DBUILDING_LIBEATMYDATA -g -O2 -Werror=implicit-function-declaration > -ffile-prefix-map=/<>=. -fstack-protector-strong > -fstack-clash-protection -Wformat -Werror=format-security -c > libeatmydata/libeatmydata.c -fPIC -DPIC -o > libeatmydata/.libs/la-libeatmydata.o > In file included from /usr/include/features.h:393, > from /usr/include/arm-linux-gnueabihf/sys/types.h:25, > from libeatmydata/libeatmydata.c:22: > /usr/include/features-time64.h:26:5: error: #error "_TIME_BITS=64 is allowed > only with _FILE_OFFSET_BITS=64" >26 | # error "_TIME_BITS=64 is allowed only with _FILE_OFFSET_BITS=64" > | ^ > make[2]: *** [Makefile:1046: libeatmydata/la-libeatmydata.lo] Error 1 The full build log is available from: http://qa-logs.debian.net/2024/04/20/libeatmydata_131-1_unstable-armhf.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: libeatmydata Source-Version: 131-2 Done: Mattia Rizzolo We believe that the bug you reported is fixed in the latest version of libeatmydata, 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. Mattia Rizzolo (supplier of updated libeatmydata package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 22 Apr 2024 10:29:08 +0200 Source: libeatmydata Architecture: source Version: 131-2 Distribution: unstable Urgency: medium Maintainer: Mattia Rizzolo Changed-By: Mattia Rizzolo Closes: 1069465 Changes: libeatmydata (131-2) unstable; urgency=medium . * Bump Standards-Version, no changes needed. * Add patch to fix FTBFS on 32 bits with a t64 env. Closes: #1069465 Checksums-Sha1: 0059cd6ef31d493053eb411251613e5770d603b3 2512 libeatmydata_131-2.dsc 69e350b8d1bac5b2fa636d24e705e914b1c4bfb1 16292 libeatmydata_131-2.debian.tar.xz 58416273fac16a3b85a65e6ca48835ceb890cbdc 6844 libeatmydata_131-2_amd64.buildinfo Checksums-Sha256: 9aaa429091a5e5cdc877dc041cb8745b5b06cd26c81a7743eeed29fe790f40ce 2512
Bug#1069372: efibootguard: FTBFS on arm64: kernel-stub/fdt.c:169:49: error: passing argument 2 of ‘CopyMem’ discards ‘const’ qualifier from pointer target type [-Werror=discarded-qualifiers]
This is a upstream bug. Thanks for reporting, Quirin forwarded 1069372 efibootguard-...@googlegroups.com On 4/20/24 2:01 PM, Lucas Nussbaum wrote: Source: efibootguard Version: 0.16-2 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): make[2]: Entering directory '/<>' make --no-print-directory all-recursive Making all in . set -e; echo ' CHK version.h'; mkdir -p ./; ./gen_version_h ./ < Makefile.in > version.h.tmp; if [ -r version.h ] && cmp -s version.h version.h.tmp; then rm -f version.h.tmp; else echo ' UPD version.h'; mv -f version.h.tmp version.h; fi CHK version.h /usr/bin/mkdir -p completion/bash; PYTHONPATH=./completion/shtab:./completion /usr/bin/python3 -m shtab -u --shell=bash bg_setenv.cli.bg_setenv >completion/bash/bg_setenv.bash UPD version.h /usr/bin/mkdir -p completion/bash; PYTHONPATH=./completion/shtab:./completion /usr/bin/python3 -m shtab -u --shell=bash bg_printenv.cli.bg_printenv >completion/bash/bg_printenv.bash /usr/bin/mkdir -p drivers/watchdog/; gcc -I. -include config.h -I./include -I/usr/include -I/usr/include/efi -I/usr/include/efi/aarch64 -I/usr/include/aarch64-linux-gnu -Wall -Wextra -std=gnu99 -ggdb -O0 -fpic -fshort-wchar -ffreestanding -fno-strict-aliasing -Wsign-compare -DGNU_EFI_USE_MS_ABI -Werror -mgeneral-regs-only -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -mbranch-protection=standard -fno-stack-protector -c drivers/watchdog/init_array_start.S -o drivers/watchdog/init_array_start.o /usr/bin/mkdir -p drivers/watchdog/; gcc -I. -include config.h -I./include -I/usr/include -I/usr/include/efi -I/usr/include/efi/aarch64 -I/usr/include/aarch64-linux-gnu -Wall -Wextra -std=gnu99 -ggdb -O0 -fpic -fshort-wchar -ffreestanding -fno-strict-aliasing -Wsign-compare -DGNU_EFI_USE_MS_ABI -Werror -mgeneral-regs-only -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -mbranch-protection=standard -fno-stack-protector -c drivers/watchdog/init_array_end.S -o drivers/watchdog/init_array_end.o /usr/bin/mkdir -p env/; gcc -I. -include config.h -I./include -I/usr/include -I/usr/include/efi -I/usr/include/efi/aarch64 -I/usr/include/aarch64-linux-gnu -Wall -Wextra -std=gnu99 -ggdb -O0 -fpic -fshort-wchar -ffreestanding -fno-strict-aliasing -Wsign-compare -DGNU_EFI_USE_MS_ABI -Werror -mgeneral-regs-only -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -mbranch-protection=standard -fno-stack-protector -c env/syspart.c -o env/syspart.o /usr/bin/mkdir -p env/; gcc -I. -include config.h -I./include -I/usr/include -I/usr/include/efi -I/usr/include/efi/aarch64 -I/usr/include/aarch64-linux-gnu -Wall -Wextra -std=gnu99 -ggdb -O0 -fpic -fshort-wchar -ffreestanding -fno-strict-aliasing -Wsign-compare -DGNU_EFI_USE_MS_ABI -Werror -mgeneral-regs-only -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -mbranch-protection=standard -fno-stack-protector -c env/fatvars.c -o env/fatvars.o /usr/bin/mkdir -p ./; gcc -I. -include config.h -I./include -I/usr/include -I/usr/include/efi -I/usr/include/efi/aarch64 -I/usr/include/aarch64-linux-gnu -Wall -Wextra -std=gnu99 -ggdb -O0 -fpic -fshort-wchar -ffreestanding -fno-strict-aliasing -Wsign-compare -DGNU_EFI_USE_MS_ABI -Werror -mgeneral-regs-only -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -mbranch-protection=standard -fno-stack-protector -c utils.c -o utils.o /usr/bin/mkdir -p ./; gcc -I. -include config.h -I./include -I/usr/include -I/usr/include/efi -I/usr/include/efi/aarch64 -I/usr/include/aarch64-linux-gnu -Wall -Wextra -std=gnu99 -ggdb -O0 -fpic -fshort-wchar -ffreestanding -fno-strict-aliasing -Wsign-compare -DGNU_EFI_USE_MS_ABI -Werror -mgeneral-regs-only -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -mbranch-protection=standard -fno-stack-protector -c loader_interface.c -o loader_interface.o /usr/bin/mkdir -p ./; gcc -I. -include config.h -I./include -I/usr/include -I/usr/include/efi -I/usr/include/efi/aarch64 -I/usr/include/aarch64-linux-gnu -Wall -Wextra -std=gnu99 -ggdb -O0 -fpic -fshort-wchar -ffreestanding -fno-strict-aliasing -Wsign-compare -DGNU_EFI_USE_MS_ABI -Werror -mgeneral-regs-only -g -O2 -Werror=implicit-function-declaration
Bug#1069088: marked as done (libvdeplug-slirp - dependencies unsatisfiable on 32-bit non-i386 architectures.)
Your message dated Mon, 22 Apr 2024 08:47:00 + with message-id and subject line Bug#1069088: fixed in vdeplug-slirp 0.1.0-3 has caused the Debian Bug report #1069088, regarding libvdeplug-slirp - dependencies unsatisfiable on 32-bit non-i386 architectures. to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1069088: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069088 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libvdeplug-slirp Version: 0.1.0-2 Tags: trixie, sid Severity: grave User: debian-...@lists.debian.org Usertag: time-t After being rebuilt for the time64 transition, libvdeplug-slirp still depends on the pre-time64 libraries libvdeplug2 and libvdeslirp0. It also depends on libvdeplug2t64. As a result it is uninstallable on architectures that are undergoing the time64 transition (armel, armhf and some debian-ports architectures). Ubuntu has already fixed this issue by removing the hardcoded dependencies and adding code to debian/rules to calculate a correct libvdeplug dependency. http://launchpadlibrarian.net/721384619/vdeplug-slirp_0.1.0-2build1_0.1.0-2ubuntu1.diff.gz --- End Message --- --- Begin Message --- Source: vdeplug-slirp Source-Version: 0.1.0-3 Done: Mattia Rizzolo We believe that the bug you reported is fixed in the latest version of vdeplug-slirp, 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. Mattia Rizzolo (supplier of updated vdeplug-slirp package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 22 Apr 2024 10:08:00 +0200 Source: vdeplug-slirp Architecture: source Version: 0.1.0-3 Distribution: unstable Urgency: medium Maintainer: Debian VirtualSquare Team Changed-By: Mattia Rizzolo Closes: 1069088 Changes: vdeplug-slirp (0.1.0-3) unstable; urgency=medium . * Team upload. . [ Debian Janitor ] * Apply multi-arch hints. + libvdeplug-slirp: Add Multi-Arch: same. Changes-By: apply-multiarch-hints . [ Mattia Rizzolo ] * remove some boilerplate from d/rules. * Don't hardcode dependencies on shared libraries. (Closes: #1069088) Checksums-Sha1: 984225614bffa578f73fd298c13569edb2cd6e67 2118 vdeplug-slirp_0.1.0-3.dsc c34dfb8856b6263285ff16689c1389ecf0d91d1f 2168 vdeplug-slirp_0.1.0-3.debian.tar.xz d0a9947edcb3dc3d10c271c63966458fccd07bdd 7474 vdeplug-slirp_0.1.0-3_amd64.buildinfo Checksums-Sha256: b604d79d3a141cf95af1653483e239e83e249f17a6ec59e92a28faa77c08bca3 2118 vdeplug-slirp_0.1.0-3.dsc ebb787ce1a9f3710016f3aad08a779f24a874e7ffe27711839c9ed0553376895 2168 vdeplug-slirp_0.1.0-3.debian.tar.xz 2162788d9a1fab73facecaa9bfa362074998907b1b4e573fb172ae4e89d2d666 7474 vdeplug-slirp_0.1.0-3_amd64.buildinfo Files: 4bfb44202cbe9d562de522c07e363154 2118 libs optional vdeplug-slirp_0.1.0-3.dsc 6829a4bcb921a1ae1460f52a400568e0 2168 libs optional vdeplug-slirp_0.1.0-3.debian.tar.xz fe895f84c70c62c4f42885205d4f309e 7474 libs optional vdeplug-slirp_0.1.0-3_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEi3hoeGwz5cZMTQpICBa54Yx2K60FAmYmG9oACgkQCBa54Yx2 K63lMxAAkT/3Kvm0H4w76r1jmTn7QHGTUrSQ0DhzP/pJ0qBwOUlsehIV3UDcZyzH WRpYPVbBIXPGBYmTP4ydTuWp89Ijk4DcrODojPpIc9uu6VGDdyO484RwVKoDCZlc xPkSv+nZkc7pKoMtxMytwx0flCxgGCNrGHSggzdFQSDN7qD0Vcm0pEtnJkB6wy2g VKm89g9O8/4z72a0n4XTGbR8wWGt0yU79vOCDKtQPzLeOOq6Z4L+3nY/2XqF60ar 73fozX51/spjEVfe4Epakkg1Kgqj2SS7yNUFgF6Cgj+tZTo9ncjztf8RbyOyJt8y zLDP5ZWbnsDyxYXiSU8ns5N8gUFSPNg30Ot9EHn3/93jkDnlyYWsFXoWQUu9ZQmI F72lhas4F3gccKiFfxVRRhPZ5Bo88ZcnZxRoV/UMvqXVXWoZLSmLRFnIIPByLWeY +Sy5YoX3CiH4JRA5MViw4E/7sgLKToR9fCgvwNpk4SeaBejIPWczc4rsycDpciEf pvZ8FULWEMUEY/DWnQg2x+a9BbceJDPUc+R8vVBWG0pdUaQRRB6FTYGH47SphyHu teOh38hpn7h5+64WtxUUbEQPrAm/Q+ECKxUTGfzauUzgw+eu8YgBQSOgB3vNejwV CVWJTQPOeaMKiyjrGtKO79NkQdREWPoZK9KG9bVa1+QX9DRlOB0= =wnzD -END PGP SIGNATURE- pgpcNJAn1IxEd.pgp Description: PGP signature --- End Message ---
Bug#1069339: marked as done (Not installable due to hardcoded pre-t64 library deps)
Your message dated Mon, 22 Apr 2024 08:46:51 + with message-id and subject line Bug#1069339: fixed in vdeplug-pcap 0.1.0-3 has caused the Debian Bug report #1069339, regarding Not installable due to hardcoded pre-t64 library deps 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.) -- 1069339: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069339 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libvdeplug-pcap Version: 0.1.0-2+b3 Severity: grave libvdeplug-pcap explicitly Depends: libvdeplug2, libpcap0.8. They should be changed to the t64 names if they are really needed. -- System Information: Debian Release: trixie/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'unstable'), (500, 'testing'), (101, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.7.9-amd64 (SMP w/16 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libvdeplug-pcap depends on: ii libc6 2.37-18 ii libpcap0.8t64 [libpcap0.8]1.10.4-4.1 ii libvdeplug2t64 [libvdeplug2] 4.0.1-5.1 libvdeplug-pcap recommends no packages. libvdeplug-pcap suggests no packages. --- End Message --- --- Begin Message --- Source: vdeplug-pcap Source-Version: 0.1.0-3 Done: Mattia Rizzolo We believe that the bug you reported is fixed in the latest version of vdeplug-pcap, 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. Mattia Rizzolo (supplier of updated vdeplug-pcap package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 22 Apr 2024 10:02:20 +0200 Source: vdeplug-pcap Architecture: source Version: 0.1.0-3 Distribution: unstable Urgency: medium Maintainer: Debian VirtualSquare Team Changed-By: Mattia Rizzolo Closes: 1069339 Changes: vdeplug-pcap (0.1.0-3) unstable; urgency=medium . [ Mattia Rizzolo ] * Team upload. * Don't hardcode libary names. Thanks to Matthias Klose for the patch (Closes: #1069339) * drop some boilerplate from d/rules . [ Debian Janitor ] * Apply multi-arch hints. + libvdeplug-pcap: Add Multi-Arch: same. Changes-By: apply-multiarch-hints Checksums-Sha1: 3962252396ccce3baefb20f9654f209cd24a3800 2095 vdeplug-pcap_0.1.0-3.dsc 5bde3a5a3f40bb994dcc4905b4d62c9bd3934e10 2544 vdeplug-pcap_0.1.0-3.debian.tar.xz 767300d78d09d9d99cd36b7874a6c507ebf9faba 7564 vdeplug-pcap_0.1.0-3_amd64.buildinfo Checksums-Sha256: 15f40f0b80d6d0c4d6adf7086a9a7bbfd8512ec782d6ca35e8539b797710a1cd 2095 vdeplug-pcap_0.1.0-3.dsc 1b823fd33e3e83706c3bfb20a86302db2bad076a3ec1f42a5b65ebf59097bd6c 2544 vdeplug-pcap_0.1.0-3.debian.tar.xz 309218a6dd2514b4cd993a76f81b08f14279c290c1e2463d4c22c16fafb5cb93 7564 vdeplug-pcap_0.1.0-3_amd64.buildinfo Files: 5dd8e64010e72d84759a2f6f85eb198d 2095 libs optional vdeplug-pcap_0.1.0-3.dsc 26b9f0be42fc5790003176a966138729 2544 libs optional vdeplug-pcap_0.1.0-3.debian.tar.xz a5cec38f54c430aa2901c77b1b5034d9 7564 libs optional vdeplug-pcap_0.1.0-3_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEi3hoeGwz5cZMTQpICBa54Yx2K60FAmYmGisACgkQCBa54Yx2 K60DzQ//ZPo5thEk6OVTscqJGU0Eba/J5OJLHKdF/cj4xuRPsk8qlLJlmiR0vzu9 X+gQLNS8doB0r2Q7yE1DT0x1jS4t6J1+9LUv6gXYJBMtg9VmRA3QfSNJh8GGOBLs OSCRFooxQe78SUssj439dIjGeWKAN+T3HZKNT168YhqlspKJEKv+lLTMfWME39Ik zQJ+1SdiiM4PLjjzdQAPSTt5aOct6nAs/mWKk7VckURsiSLKtH+a0tGnsmuyxfxn iHhdX3VM6wInJFVNnJ8Mgq7tm5IiR9wrG4ej7Ed9d+p8h8gQxOLV+4J/i/7x2Ws7 dIASvCuAqTla91FjqMy4v1UNCu5QJc8EKBkdFDMVz7uyph6Iqd0vt08qiWhJQefz lGcModI68esmDua3pSmB4o9DQdDD+2TKBfjvSDgdJOkvL2GUFPhoEXsz80UE9HDl 75IYIZ1h4ecvFBKiG58fxhoP3QB28TdkmflEeKO/3N6iSRdzUwG7DKOUg/uXcKfm XVLommdshTf/Xqmbol2Vk0/TTH4KMss3ZXzNHmqzh1jp5/Tey4nMqILcZf9oU0zG QVHj7zQSDTRLJqpRTlCHDRVFQowU2HG3XLsumZcLRav3AzEdvT9WKEh0LXaSMfpU
Processed: Bug#1069465 marked as pending in libeatmydata
Processing control commands: > tag -1 pending Bug #1069465 [src:libeatmydata] libeatmydata: FTBFS on armhf: features-time64.h:26:5: error: #error "_TIME_BITS=64 is allowed only with _FILE_OFFSET_BITS=64" Added tag(s) pending. -- 1069465: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069465 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1069465: marked as pending in libeatmydata
Control: tag -1 pending Hello, Bug #1069465 in libeatmydata 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/debian/libeatmydata/-/commit/8e4f521eeb66bcd581b519a8673327f6d07431f1 Add patch to fix FTBFS on 32 bits with a t64 env Closes: #1069465 Signed-off-by: Mattia Rizzolo (this message was generated automatically) -- Greetings https://bugs.debian.org/1069465
Bug#1037903: xrt: ftbfs with GCC-13
On Sat, 16 Sep 2023 20:13:12 +0200 Jonathan Bergh
wrote:
Control: tags -1 + patch
Fixes 1037903 due to upgrade to gcc-13
Hello, I had to add another one for arm64 build failure
---
xrt-202210.2.13.466+dfsg.orig/src/runtime_src/core/edge/user/aie/common_layer/adf_api_config.h
+++
xrt-202210.2.13.466+dfsg/src/runtime_src/core/edge/user/aie/common_layer/adf_api_config.h
@@ -16,6 +16,7 @@
#pragma once
+#include
#include
#include
Index: xrt-202210.2.13.466+dfsg/src/runtime_src/core/edge/user/zynq_dev.h
===
--- xrt-202210.2.13.466+dfsg.orig/src/runtime_src/core/edge/user/zynq_dev.h
+++ xrt-202210.2.13.466+dfsg/src/runtime_src/core/edge/user/zynq_dev.h
@@ -19,6 +19,7 @@
#include
#include
#include
+#include
class zynq_device {
public:
OpenPGP_signature.asc
Description: OpenPGP digital signature
Bug#1069642: linux-image-6.1.0-20-amd64: kernel panic after 2024-04-20
Same problem here, but with a different call trace. The RIP logline had one of `security_file_permission` and `security_netlink_send`, I don't remember which one.
Bug#1069655: libkf6userfeedback-data: missing Breaks+Replaces: libkuserfeedbackcoreqt6-1 (<< 6)
Package: libkf6userfeedback-data Version: 6.0.0-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts fileconflict Hi, during a test with piuparts I noticed your package fails to upgrade from 'sid' to 'experimental'. It installed fine in 'sid', then the upgrade to 'experimental' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. This error may also be triggered by having a predecessor package from 'sid' installed while installing the package from 'experimental'. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces >From the attached log (scroll to the bottom...): Preparing to unpack .../libkf6userfeedback-data_6.0.0-1_all.deb ... Unpacking libkf6userfeedback-data (6.0.0-1) ... dpkg: error processing archive /var/cache/apt/archives/libkf6userfeedback-data_6.0.0-1_all.deb (--unpack): trying to overwrite '/usr/share/qlogging-categories6/org_kde_UserFeedback.categories', which is also in package libkuserfeedbackcoreqt6-1:amd64 1.3.0-3+b2 Errors were encountered while processing: /var/cache/apt/archives/libkf6userfeedback-data_6.0.0-1_all.deb cheers, Andreas libkuserfeedbackcoreqt6-1=1.3.0-3+b2_libkf6userfeedback-data=6.0.0-1.log.gz Description: application/gzip
Processed: found 966249 in 0.9.1-1, tagging 1069608, found 966288 in 2.12.5+dfsg-1 ..., tagging 1069027 ...
Processing commands for cont...@bugs.debian.org:
> found 966249 0.9.1-1
Bug #966249 [src:appstream-generator] appstream-generator FTBFS with gdc:
error: undefined identifier ‘JSONType’
Marked as found in versions appstream-generator/0.9.1-1.
> tags 1069608 + sid trixie
Bug #1069608 [src:topplot] topplot: missing test-depends on python3-all
Added tag(s) sid and trixie.
> found 966288 2.12.5+dfsg-1
Bug #966288 [src:mcollective] mcollective - RM for bullseye?
Marked as found in versions mcollective/2.12.5+dfsg-1.
> reassign 1069027 jupyter-notebook 6.4.12-2.2
Bug #1069027 [python3-notebook] python3-notebook: Jupyter Notebook fails to
start - wrong call to traitlets.warn
Bug reassigned from package 'python3-notebook' to 'jupyter-notebook'.
No longer marked as found in versions jupyter-notebook/6.4.12-2.2.
Ignoring request to alter fixed versions of bug #1069027 to the same values
previously set
Bug #1069027 [jupyter-notebook] python3-notebook: Jupyter Notebook fails to
start - wrong call to traitlets.warn
Marked as found in versions jupyter-notebook/6.4.12-2.2.
> tags 1069027 + sid trixie
Bug #1069027 [jupyter-notebook] python3-notebook: Jupyter Notebook fails to
start - wrong call to traitlets.warn
Added tag(s) trixie and sid.
> tags 1061229 + sid trixie
Bug #1061229 {Done: Graham Inggs } [src:numpydoc] numpydoc:
Failing autopkgtest
Added tag(s) sid and trixie.
> tags 1068713 + sid trixie bookworm
Bug #1068713 {Done: Vincent Danjean } [oar-common]
oar-common: Submitting jobs does not work on a fresh installation of OAR
Added tag(s) bookworm, sid, and trixie.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1061229: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061229
1068713: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068713
1069027: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069027
1069608: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069608
966249: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966249
966288: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966288
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1064293: less: CVE-2022-48624
Hi, On Sat, Apr 20, 2024 at 07:54:13AM -0400, P. J. McDermott wrote: > On 2024-04-19 at 15:55, Salvatore Bonaccorso wrote: > > Hi, > > > > FWIW, I'm actually preparing a security update for the two CVEs and > > for bookworm I was first planning to do a 590-2.1 reaching unstable, > > and so then 590-2.1~deb12u1 for bookworm. > > > > But if you want to override it with a NMU and proposing to salvage the > > package this is equally fine. > > Your DELAYED/2 NMU is probably the fastest and best way to get these > CVEs fixed in unstable and bookworm, so that's fine, thanks. Any plans > for 551-2 in bullseye? The two patches in your NMU apply cleanly there. Yes, both bookworm-security and bullseye-security updates are already prepared and uploaded to security-master. I will wait for some exposure of less in unstable with the two fixes before releasing the DSA. I have not pushed the changes yet to the repository (will be done after the DSA release). I cannot comment on the salvaging of the package directly, as Milan has responded to the bug and even acked the NMU. So I assume he is active and you need to discuss with him on co-maintainership for less. But as I read the discussion is already happening. So stopping here to comment. Regards, Salvatore
Bug#1069646: python-glance-store - Build-depends on deprecated package: python3-boto
Package: python-glance-store Version: 4.7.0-2 Severity: serious python-glance-store build-depends on deprecated package python3-boto. See #1058652 Also it seems to not build at all: | dpkg-buildpackage: info: source package python-glance-store | dpkg-buildpackage: info: source version 4.7.0-2 | dpkg-buildpackage: info: source distribution unstable | dpkg-buildpackage: info: source changed by Thomas Goirand | dpkg-source --before-build . | dpkg-source: info: using options from source/debian/source/options: --extend-diff-ignore=^[^/]*[.]egg-info/ | /bin/true debian/rules clean | debian/rules build-indep | make: pyversions: No such file or directory | py3versions: no X-Python3-Version in control file, using supported versions | dh build-indep --buildsystem=python_distutils --with python3,sphinxdoc | dh_auto_configure: warning: Please use the third-party "pybuild" build system instead of python-distutils | dh_auto_configure: warning: This feature will be removed in compat 12. | make[1]: pyversions: No such file or directory | py3versions: no X-Python3-Version in control file, using supported versions | echo "Do nothing..." | Do nothing... | make[1]: pyversions: No such file or directory | py3versions: no X-Python3-Version in control file, using supported versions | echo "Do nothing..." | Do nothing... |create-stamp debian/debhelper-build-stamp | /bin/true debian/rules binary-indep | dpkg-genbuildinfo --build=all -O../python-glance-store_4.7.0-2_all.buildinfo | dpkg-genbuildinfo: error: binary build with no binary artifacts found; .buildinfo is meaningless | dpkg-buildpackage: error: dpkg-genbuildinfo --build=all -O../python-glance-store_4.7.0-2_all.buildinfo subprocess returned exit status 255 Bastian -- ... bacteriological warfare ... hard to believe we were once foolish enough to play around with that. -- McCoy, "The Omega Glory", stardate unknown
Bug#1068818: sngrep: CVE-2024-3119 CVE-2024-3120
Hi, On 21/4/24 21:58, Moritz Muehlenhoff wrote: > Hi Victor, > diff looks fine, but I don't believe this really needs a DSA; it's rather > obscure attack vector. > I think addressing this via the next Bookworm point release is perfectly > fine, what do you think? Fine for me. No objections from my side. > Procedure is outlined at > https://www.debian.org/doc/manuals/developers-reference/pkgs.en.html#special-case-uploads-to-the-stable-and-oldstable-distributions Ack.Thanks -- - | ,''`. Victor Seva | | : :' : linuxman...@torreviejawireless.org | | `. `' PGP: 8F19 CADC D42A 42D4 5563 730C 51A0 9B18 CF5A 5068 | |`- Debian Developer | - OpenPGP_signature.asc Description: PGP signature OpenPGP_0x7D7B65C42A0EC8B2.asc Description: application/pgp-keys
Bug#1069191: glibc: GLIBC-SA-2024-0004/CVE-2024-2961: ISO-2022-CN-EXT: fix out-of-bound writes when writing escape sequence
Hi, Can this be backported to older Debian versions via the security repo? This bug can be used to execute code when using the PHP engine: * https://www.offensivecon.org/speakers/2024/charles-fol.html * https://www.openwall.com/lists/oss-security/2024/04/18/4
Bug#1069499: closing 1069499
close 1069499 1.6.1-1 thanks This was fixed by upstream commit 972276a49bd6f6f44b5819b737e8e74c20a18da6, which is included in the 1.6.1-1 upload. -- Robert Edmonds edmo...@debian.org
Processed: closing 1069499
Processing commands for cont...@bugs.debian.org: > close 1069499 1.6.1-1 Bug #1069499 [src:mtbl] mtbl: FTBFS on armhf: dh_auto_test: error: make -j4 check "TESTSUITEFLAGS=-j4 --verbose" VERBOSE=1 returned exit code 2 Marked as fixed in versions mtbl/1.6.1-1. Bug #1069499 [src:mtbl] mtbl: FTBFS on armhf: dh_auto_test: error: make -j4 check "TESTSUITEFLAGS=-j4 --verbose" VERBOSE=1 returned exit code 2 Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 1069499: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069499 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1069499: mtbl: FTBFS on armhf: dh_auto_test: error: make -j4 check "TESTSUITEFLAGS=-j4 --verbose" VERBOSE=1 returned exit code 2
Lucas Nussbaum wrote: > Source: mtbl > Version: 1.3.0-1 > Severity: serious > Justification: FTBFS > Tags: trixie sid ftbfs > User: lu...@debian.org > Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-armhf > > Hi, > > During a rebuild of all packages in sid, your package failed to build > on armhf. > > > Relevant part (hopefully): > > test-sorted-merge: t/test-sorted-merge.c:96: quiet_tmpnam: Assertion > > `not_found == 1' failed. Hi, Lucas: I see the function that failed here has been entirely rewritten since this release, so I've uploaded the latest upstream version 1.6.1 and that built successfully on all architectures. So I'll mark this bug fixed in 1.6.1-1. Thanks! -- Robert Edmonds edmo...@debian.org
Bug#1041130: marked as done (google-compute-engine-oslogin FTBFS with googletest 1.13.0)
Your message dated Mon, 22 Apr 2024 07:19:17 + with message-id and subject line Bug#1041130: fixed in google-compute-engine-oslogin 20240415.00-1 has caused the Debian Bug report #1041130, regarding google-compute-engine-oslogin FTBFS with googletest 1.13.0 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.) -- 1041130: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041130 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: google-compute-engine-oslogin Version: 20210907.00-1 Severity: serious Tags: ftbfs trixie sid https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/google-compute-engine-oslogin.html ... In file included from /usr/src/googletest/googletest/include/gtest/gtest-message.h:57, from /usr/src/googletest/googletest/include/gtest/gtest-assertion-result.h:46, from /usr/src/googletest/googletest/include/gtest/gtest.h:64, from oslogin_utils_test.cc:17: /usr/src/googletest/googletest/include/gtest/internal/gtest-port.h:270:2: error: #error C++ versions less than C++14 are not supported. 270 | #error C++ versions less than C++14 are not supported. | ^ ... This can be fixed by changing -std=c++11 to -std=c++14 in test/Makefile --- End Message --- --- Begin Message --- Source: google-compute-engine-oslogin Source-Version: 20240415.00-1 Done: Bastian Blank We believe that the bug you reported is fixed in the latest version of google-compute-engine-oslogin, 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 1041...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Bastian Blank (supplier of updated google-compute-engine-oslogin package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 22 Apr 2024 09:01:53 +0200 Source: google-compute-engine-oslogin Architecture: source Version: 20240415.00-1 Distribution: unstable Urgency: medium Maintainer: Debian Cloud Team Changed-By: Bastian Blank Closes: 1041130 Changes: google-compute-engine-oslogin (20240415.00-1) unstable; urgency=medium . * New upstream release. (closes: #1041130) * Move all remaining files to /usr. Checksums-Sha1: 02588ed20764e050fc9caceca33a7e9464b54218 1620 google-compute-engine-oslogin_20240415.00-1.dsc fe05b2e11dd586d56d16ef942d467c947d7fe985 50376 google-compute-engine-oslogin_20240415.00.orig.tar.xz 14ab1b79a67d0f0467bd7289ee0b0f78e0d4f194 2792 google-compute-engine-oslogin_20240415.00-1.debian.tar.xz 64501c2cd030cb21977b64c90d9fe798882d35cf 6191 google-compute-engine-oslogin_20240415.00-1_source.buildinfo Checksums-Sha256: 7e9a3386175158305b9201c058842db41fc277fc66d141525085d5cc96a6f4b5 1620 google-compute-engine-oslogin_20240415.00-1.dsc 5bcb6c4bfd08e0f6aef24e9e861d765124f319ee330466e4a70e8cde618e131d 50376 google-compute-engine-oslogin_20240415.00.orig.tar.xz d03db4e0ee0375436335ace1749b53f0bcbd6bffa8048399cb8d416a1798ce32 2792 google-compute-engine-oslogin_20240415.00-1.debian.tar.xz 38a2c48b37cc7a48e1b1c23df30f95fe31247dcea2705a6f1af611f3b17f2160 6191 google-compute-engine-oslogin_20240415.00-1_source.buildinfo Files: 05d275c8292a106fb85e3cc530b7d57e 1620 admin optional google-compute-engine-oslogin_20240415.00-1.dsc d5bedb39432e34590b0528931254da79 50376 admin optional google-compute-engine-oslogin_20240415.00.orig.tar.xz 9f71b75ec95a7110a253151fc0bd6be2 2792 admin optional google-compute-engine-oslogin_20240415.00-1.debian.tar.xz e5a139287447e5f9c4f34d996e3a8a40 6191 admin optional google-compute-engine-oslogin_20240415.00-1_source.buildinfo -BEGIN PGP SIGNATURE- iHUEARYIAB0WIQQ8pEKDNIgQDAQDOBFji0aBW7swjwUCZiYMnQAKCRBji0aBW7sw j7h9AQCxEO7HgGbM3FefjyC+GVII9wiK64Oy0ZlibyUDqJGX0QEAytCDHJHRduxf jwIEqjFAe+2U0wqKwT6Q4for3Pf4mgA= =l5VW -END PGP SIGNATURE- pgpWJHia6wohA.pgp Description: PGP signature --- End Message ---
Bug#1053334: galera-4: FTBFS because of expired certificates
I was able to reproduce this for Bookworm both locally and in CI at https://salsa.debian.org/mariadb-team/galera-4/-/jobs/5620032 After importing latest upstream build/test passes: https://salsa.debian.org/otto/galera/-/jobs/5624466 Stable upload request filed at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069639
