Bug#1033805: marked as done (opendmarc: Segmentation fault with 3072-bit key signatures in ARC-Seal headers)
Your message dated Thu, 13 Apr 2023 07:05:43 +0200 with message-id and subject line opendmarc: Segmentation fault with 3072-bit key signatures in ARC-Seal headers has caused the Debian Bug report #1033805, regarding opendmarc: Segmentation fault with 3072-bit key signatures in ARC-Seal headers 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.) -- 1033805: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033805 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: opendmarc Version: 1.4.0~beta1+dfsg-6+deb11u1 Severity: serious Tags: upstream patch Justification: Maintainer designation Currently opendmarc in Stable, Testing, and Unstable will crash if they key used in an ARC header field is 3072 bit RSA or longer. This really needs to be fixed prior to release since, in normal usage, when a milter crashes it stops all mail flow on the system. Since the key size is an attribute decided by the sending domain, there's no work around on the receiver side to avoid the specific keys at issue. Longer RSA keys are becoming more common and this trend will continue through Bookworm's life, so the impact will only grow. Patch available in the upstream GitHub repository: https://github.com/trusteddomainproject/OpenDMARC/issues/183 Scott K --- End Message --- --- Begin Message --- We’ve seen no evidence of crashing in 1.4.2-1 or 1.4.2-2, closing.--- End Message ---
Bug#1034328: timeshift with btrfs on LUKS encrypted filesystem and sysvinit does not work
Subject: timeshift with btrfs on LUKS encrypted filesystem and/or sysvinit/runit does not work. Package: timeshift X-Debbugs-Cc: n...@ambag.es Version: 20.11.1-1 Severity: grave Justification: renders package unusable Dear Maintainer, timeshift is working with btrfs, when it is not encrypted with LUKS and sysvinit. But with an encrypted drive, timeshift does work not with my BTRFS-filesystem with sysvinit. There is only a warning, that the system-drive is not found. Here some Infos about the system: ~# cat /etc/fstab UUID=779a1789-d53f-4882-bdcc-36e142fc482a / btrfs rw,noatime,subvol=@ 0 1 UUID=cbc12706-9f45-452f-9d0d-4cfef99e8042 /boot ext4 defaults,noatime 0 2 UUID=779a1789-d53f-4882-bdcc-36e142fc482a /home btrfs rw,noatime,subvol=@home 0 2 UUID=779a1789-d53f-4882-bdcc-36e142fc482a /.snapshots btrfs rw,noatime,subvol=@snapshots 0 2 tmpfs /tmp tmpfs defaults,nosuid,nodev 0 0 ~# btrfs subvolume list / ID 256 gen 8874 top level 5 path @ ID 262 gen 8765 top level 5 path @home ID 263 gen 8752 top level 5 path @snapshots ~# mount sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime) proc on /proc type proc (rw,nosuid,nodev,noexec,relatime) udev on /dev type devtmpfs (rw,nosuid,relatime,size=1993068k,nr_inodes=498267,mode=755) devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=600,ptmxmode=000) tmpfs on /run type tmpfs (rw,nosuid,nodev,noexec,relatime,size=402388k,mode=755) /dev/mapper/sda2_crypt on / type btrfs (rw,noatime,space_cache,subvolid=256,subvol=/@) tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k) securityfs on /sys/kernel/security type securityfs (rw,relatime) pstore on /sys/fs/pstore type pstore (rw,relatime) tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev,noexec,relatime,size=804760k) /dev/sda1 on /boot type ext4 (rw,noatime) /dev/mapper/sda2_crypt on /home type btrfs (rw,noatime,space_cache,subvolid=262,subvol=/@home) /dev/mapper/sda2_crypt on /.snapshots type btrfs (rw,noatime,space_cache,subvolid=263,subvol=/@snapshots) tmpfs on /tmp type tmpfs (rw,nosuid,nodev,relatime) cgroup2 on /sys/fs/cgroup type cgroup2 (rw,nosuid,nodev,noexec,relatime,nsdelegate) tmpfs on /run/user/0 type tmpfs (rw,nosuid,nodev,relatime,size=402384k,nr_inodes=100596,mode=700) tmpfs on /run/user/1000 type tmpfs (rw,nosuid,nodev,relatime,size=402384k,nr_inodes=100596,mode=700,uid=1000,gid=1000) ~# timeshift --check E: System disk not found! ~# timeshift --debug D: Main() D: D: Running Timeshift v20.11.1 D: D: Session log file: /var/log/timeshift/2023-04-13_04-55-20_.log D: Distribution: debian "11" D: DIST_ID: debian D: Main: check_dependencies() D: Main: add_default_exclude_entries() D: Main: add_default_exclude_entries(): exit D: update_partitions() D: df -T -B1 D: Device: get_disk_space_using_df(): 1 D: Device: get_mounted_filesystems_using_mtab(): 1 D: Device: get_filesystems(): 5 D: partition list updated D: detect_system_devices() D: /boot is mapped to device: /dev/sda1, UUID=cbc12706-9f45-452f-9d0d-4cfef99e8042 D: Searching subvolume for system at path: / D: Found subvolume: @, on device: D: Found subvolume: @home, on device: D: Found subvolume: @snapshots, on device: D: Users: tom root D: Encrypted home users: D: Encrypted home dirs: D: Encrypted private dirs: D: Main: load_app_config() App config loaded: /etc/timeshift/timeshift.json D: IconManager: init() D: bin_path: /usr/bin/timeshift D: found images directory: /usr/share/timeshift/images D: Main(): ok D: AppConsole: parse_arguments() D: Main: initialize_repo() D: backup_uuid= D: backup_parent_uuid= D: Setting snapshot device from config file D: Main: initialize_repo(): exit D: AppConsole: start_application() D: exit_app() D: Main: save_app_config() D: SnapshotRepo: available() D: device is null D: is_available: false App config saved: /etc/timeshift/timeshift.json D: unmount_target_device() D: clean_logs() D: rm -rf '/tmp/8N47lEDL' -- System Information: Debian Release: 11.6 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-20-amd64 (SMP w/2 CPU threads) 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: sysvinit (via /sbin/init) LSM: AppArmor: enabled Versions of packages timeshift depends on: ii libc62.31-13+deb11u5 ii libcairo21.16.0-5 ii libgdk-pixbuf-2.0-0 2.42.2+dfsg-1+deb11u1 ii libgee-0.8-2 0.20.4-1 ii libglib2.0-0 2.66.8-1 ii libgtk-3-0 3.24.24-4+deb11u2 ii libjson-glib-1.0-0 1.6.2-1 ii libvte-2.91-00.62.3-1 ii psmisc 23.4-2 ii rsync3.2.3-4+deb11u1 timeshift recommends no packages. timeshift suggests no packages. -- no debconf information --
Bug#1034160: marked as done (libkscreenlocker5: Screen locker crashes asking for loginctl command)
Your message dated Thu, 13 Apr 2023 00:12:40 + with message-id and subject line Bug#1034160: fixed in qtbase-opensource-src 5.15.8+dfsg-7 has caused the Debian Bug report #1034160, regarding libkscreenlocker5: Screen locker crashes asking for loginctl command 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.) -- 1034160: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034160 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libkscreenlocker5 Version: 5.27.2-1 Severity: grave Justification: renders package unusable Dear Maintainer, After some libraries updates, I cannot lock my plasma session anymore. It shows a black screen with a message asking to go to a virtual terminal and run a 'loginctl unlock-session 2' or similar to unlock the screen. This is happening with my desktop and my notebook. Even with a reboot this problem presists. Debian Release: 12.0 APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.2.10 (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE Locale: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8), LANGUAGE=pt_BR:pt:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages libkscreenlocker5 depends on: ii kio5.103.0-1 ii kpackagetool5 5.103.0-1 ii libc6 2.36-8 ii libkf5configcore5 5.103.0-2 ii libkf5configgui5 5.103.0-2 ii libkf5configqml5 5.103.0-2 ii libkf5coreaddons5 5.103.0-1 ii libkf5crash5 5.103.0-1 ii libkf5declarative5 5.103.0-1 ii libkf5globalaccel-bin 5.103.0-1 ii libkf5globalaccel5 5.103.0-1 ii libkf5i18n55.103.0-1 ii libkf5idletime55.103.0-2 ii libkf5kiocore5 5.103.0-1 ii libkf5notifications5 5.103.0-1 ii libkf5package5 5.103.0-1 ii libkf5quickaddons5 5.103.0-1 ii libkf5screendpms8 4:5.27.2-1 ii libkf5waylandclient5 4:5.103.0-1 ii libkf5windowsystem55.103.0-1 ii libkf5xmlgui5 5.103.0-1 ii liblayershellqtinterface5 5.27.2-1 ii libpam0g 1.5.2-6 ii libqt5core5a 5.15.8+dfsg-4 ii libqt5dbus55.15.8+dfsg-4 ii libqt5gui5 5.15.8+dfsg-4 ii libqt5network5 5.15.8+dfsg-4 ii libqt5qml5 5.15.8+dfsg-3 ii libqt5quick5 5.15.8+dfsg-3 ii libqt5widgets5 5.15.8+dfsg-4 ii libqt5x11extras5 5.15.8-2 ii libstdc++6 12.2.0-14 ii libwayland-client0 1.21.0-1 ii libwayland-server0 1.21.0-1 ii libx11-6 2:1.8.4-2 ii libxcb-keysyms10.4.0-1+b2 ii libxcb11.15-1 ii libxi6 2:1.8-1+b1 ii psmisc 23.6-1 Versions of packages libkscreenlocker5 recommends: ii kde-config-screenlocker 5.27.2-1 libkscreenlocker5 suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: qtbase-opensource-src Source-Version: 5.15.8+dfsg-7 Done: Lisandro Damián Nicanor Pérez Meyer We believe that the bug you reported is fixed in the latest version of qtbase-opensource-src, 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 1034...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Lisandro Damián Nicanor Pérez Meyer (supplier of updated qtbase-opensource-src 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, 12 Apr 2023 20:24:34 -0300 Source: qtbase-opensource-src Architecture: source Version: 5.15.8+dfsg-7 Distribution: unstable Urgency: medium Maintainer: Debian Qt/KDE Maintainers Changed-By: Lisandro Damián Nicanor Pérez Meyer Closes: 1033995 1034160 1034271 Changes: qtbase-opensource-src (5.15.8+dfsg-7) unstable; urgency=medium . * Update a11y_root.diff. This time the code waits for Qt loop to process the check (Closes: #1033995, #1034160, #1034271). Checksums-Sha1:
Processed: Re: libvcflib breaks freebayes autopkgtest: Error: signal 11
Processing control commands:
> reopen -1
Bug #1032557 {Done: Andreas Tille } [src:freebayes] libvcflib
breaks freebayes autopkgtest: Error: signal 11
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions freebayes/1.3.7-1~exp.
--
1032557: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032557
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1032557: libvcflib breaks freebayes autopkgtest: Error: signal 11
Control: reopen -1 This bug was marked as fixed in a new-upstream upload of freebayes to experimental. But my testing on Ubuntu shows that a no-change rebuild of freebayes 1.3.6-2 against current libvcflib is sufficient to fix the segfault. This implies that libvcflib has actually broken ABI without changing its SONAME, and that this is what is causing the segfault. So I don't consider it correct to mark this bug as "fixed" in freebayes, as libvcflib1 needs a rename to block the new library being loaded by old binaries. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer https://www.debian.org/ slanga...@ubuntu.com vor...@debian.org signature.asc Description: PGP signature
Bug#1034211: marked as done (booth: dh_installsystemd doesn't handle files in /usr/lib/systemd/system)
Your message dated Wed, 12 Apr 2023 21:18:57 + with message-id and subject line Bug#1034211: fixed in booth 1.0-283-g9d4029a-2 has caused the Debian Bug report #1034211, regarding booth: dh_installsystemd doesn't handle files in /usr/lib/systemd/system 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.) -- 1034211: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034211 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: booth Version: 1.0-283-g9d4029a-1 Severity: serious Tags: sid bookworm User: debhel...@packages.debian.org Usertags: systemd-files-in-usr-bookworm Dear Maintainer, It seems that your package booth is shipping files (.service, .socket or .timer) in /usr/lib/systemd/system. This is not supported by the version of dh_installsystemd/debhelper currently in unstable and bookworm (See: #1031695). That means that currently your service might not be enabled at boot and/or started as expected. With the freeze currently in effect, debhelper will not be fixed for bookworm. As a result, could you please move these files to /lib/systemd/system instead so they are properly detected by debhelper? As soon as debhelper is supporting (not until bookworm+1 aka Trixie) you will be able to move them back to the newer location. Note that bookworm is currently in hard freeze, please limit the changes you are uploading to the ones fixing RC bugs. Also note that you might have to request a freeze exception to the release team. See: https://release.debian.org/testing/freeze_policy.html Feel free to contact me if you have any questions. Kind regards, Laurent Bigonville The list of packages has been generated with the following command: apt-file search -x '^/usr/lib/systemd/system/.*\.(service|timer|socket)$'|cut -d: -f1|sort -u --- End Message --- --- Begin Message --- Source: booth Source-Version: 1.0-283-g9d4029a-2 Done: Valentin Vidic We believe that the bug you reported is fixed in the latest version of booth, 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 1034...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Valentin Vidic (supplier of updated booth 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, 12 Apr 2023 22:58:53 +0200 Source: booth Architecture: source Version: 1.0-283-g9d4029a-2 Distribution: unstable Urgency: medium Maintainer: Debian HA Maintainers Changed-By: Valentin Vidic Closes: 1034211 Changes: booth (1.0-283-g9d4029a-2) unstable; urgency=medium . * d/install: place files in /lib/systemd/system (Closes: #1034211) Checksums-Sha1: 28ea8b1723487b2d8e8102d3f76235fabfd354c2 2415 booth_1.0-283-g9d4029a-2.dsc 70b941656739b6d02be0ecd1f76144998d9968cd 8192 booth_1.0-283-g9d4029a-2.debian.tar.xz f03301aed0206bca5fcaa5d4c6c2e95e96f7d065 7504 booth_1.0-283-g9d4029a-2_source.buildinfo Checksums-Sha256: 37117e33c1ba73cd2b87c1eb286cd6c93d94afb074e6a693b2ff799420ef762a 2415 booth_1.0-283-g9d4029a-2.dsc 934aa0b7b51516e3df1646633ce9e8b5d13a3b70a4ace501911bb80ab36d0a33 8192 booth_1.0-283-g9d4029a-2.debian.tar.xz f38f0a11251a9444ef1d5fbf061b4528627650ecaa4bdc6bff571c5757051e90 7504 booth_1.0-283-g9d4029a-2_source.buildinfo Files: 433ee0bb01e116676cb6faca74c29fb4 2415 admin optional booth_1.0-283-g9d4029a-2.dsc e36d261dde714f2a4148717b92f707e9 8192 admin optional booth_1.0-283-g9d4029a-2.debian.tar.xz 471d4363ef9ae1e678f0416cf003cce9 7504 admin optional booth_1.0-283-g9d4029a-2_source.buildinfo -BEGIN PGP SIGNATURE- iQJGBAEBCgAwFiEExaW53cM9k/u2PWfIMofYmpfNqHsFAmQ3Hu0SHHZ2aWRpY0Bk ZWJpYW4ub3JnAAoJEDKH2JqXzah7Zr8QAJWp7y6d0nzOu/puct6U8LBLqhSHVD7Y 6w1mjVp+mfqxAigIaXeXxSVTE7HQiXPneGqCeVPMyUVvtRtdnh9YGro3Fu8sOX9e SkcPamfgIm4zuYoOL3X3z/aZNgO2FHbeq2/aDocF18WSU2Ebd+vJrdU1VI0X56Fa O/270G8lRKMD24YQwhSGA1Erq0RnjkZQYxWzY9uViJWou9q3o5rdnsIuhwiHfo2y nd5iyMhc7kZhI5Cwly68R59+VHpiXDZgoK5VXODmrWlGdsdVCR62c/LcT2UJzEph wVd3vyQyVObdImbo9BgeL4B2Z0ssSJetXdJ5/pwljS+K0LyAbw2VeYdk0PmrIRkw 15I2B8yTYo+i5winQlapTP8rBoU5zAzSGABGkH26x2EwiMpB3sPzRrHGRSbydFyG kaOgSxxGawpOOSPCGMREyIKakwneekA90mexCjHGdBROdRWvYhGAsiPzm7/xzGGW
Bug#1034303: nvidia-cuda-toolkit breaks nvidia-cuda-samples autopkgtest on amd64: bad exit status: 2
Hi Andreas, Thanks. On 12-04-2023 21:32, Andreas Beckmann wrote: That needs dkms/3.0.10-8, already unblocked. So, shouldn't it be reassigned to dkms, closed and annotated as Affecting nvidia-cuda-toolkit and nvidia-cuda-samples? Paul OpenPGP_signature Description: OpenPGP digital signature
Bug#1034303: nvidia-cuda-toolkit breaks nvidia-cuda-samples autopkgtest on amd64: bad exit status: 2
On 12/04/2023 20.17, Paul Gevers wrote: With a recent upload of nvidia-cuda-toolkit the autopkgtest of nvidia-cuda-samples fails on amd64 in testing when that autopkgtest is pass fail nvidia-cuda-toolkit from testing 11.8.0-3 nvidia-cuda-samples from testing 11.8~dfsg-2 all others from testing from testing That needs dkms/3.0.10-8, already unblocked. Some background: src:nvidia-cuda-toolkit is too large to have autopkgtests on its own. So I've moved them to src:nvidia-cuda-samples. I recently fixed nvidia-fs-dkms (src:nvidia-cuda-toolkit) to work with the bookworm kernel (that's the important change in src:nvidia-cuda-toolkit missing in bookworm) (before it skipped that kernel), only to expose a bug in the dkms-autopkgtest script (src:dkms) since nvidia-fs-dkms is the first package in the archive making use of the BUILD_DEPENDS directive in dkms.conf. Andreas
Bug#1034310: digikam crashes after upgrade from bullseye to bookworm
Package: digikam Version: 4:7.9.0-1+b2 Severity: grave Dear Maintainer, after the upgrade from bullseye to bookworm, digikam does not start anymore, but crashes on startup. I put the severity to grave, since I cannot judge how many users would be affected after an upgrade. Feel free to downgrade the bug report if there is any evidence, that only few users are affected. I logged the output when starting digikam. First it stops itself, then it aborts: rd@h370:~$ digikam > digikam.log 2>&1 [1]+ Stopped digikam > digikam.log 2>&1 rd@h370:~$ fg digikam > digikam.log 2>&1 Aborted (core dumped) rd@h370:~$ The (uncompressed) digikam.log is huge, therefore I made it available here: https://bokomoko.de/~rd/Debian/digikam.log.xz It might be that it is a side effect of the upgrade, but at least for apt the system looks ok root@h370:~# apt full-upgrade Paketlisten werden gelesen… Fertig Abhängigkeitsbaum wird aufgebaut… Fertig Statusinformationen werden eingelesen… Fertig Paketaktualisierung (Upgrade) wird berechnet… Fertig 0 aktualisiert, 0 neu installiert, 0 zu entfernen und 0 nicht aktualisiert. root@h370:~# and after very initial testing I have not seen other issues in the system. If you need anything more, please let me know. Thanks Rainer -- System Information: Debian Release: 12.0 APT prefers testing-security APT policy: (500, 'testing-security'), (500, 'testing-debug'), (105, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.1.0-7-amd64 (SMP w/6 CPU threads; PREEMPT) Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=de:en_US Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages digikam depends on: ii digikam-data 4:7.9.0-1 ii digikam-private-libs 4:7.9.0-1+b2 ii libc6 2.36-8 ii libgcc-s1 12.2.0-14 ii libkf5configcore5 5.103.0-1 ii libkf5coreaddons5 5.103.0-1 ii libkf5i18n5 5.103.0-1 ii libmagick++-6.q16-8 8:6.9.11.60+dfsg-1.6 ii libqt5core5a 5.15.8+dfsg-3 ii libqt5gui55.15.8+dfsg-3 ii libqt5sql55.15.8+dfsg-3 ii libqt5sql5-mysql 5.15.8+dfsg-3 ii libqt5sql5-sqlite 5.15.8+dfsg-3 ii libqt5widgets55.15.8+dfsg-3 ii libstdc++612.2.0-14 ii perl 5.36.0-7 Versions of packages digikam recommends: ii chromium [www-browser] 112.0.5615.49-2 ii ffmpegthumbs 4:22.12.3-1 ii firefox-esr [www-browser] 102.9.0esr-2 ii konqueror [www-browser]4:22.12.3-1 ii lynx [www-browser] 2.9.0dev.12-1 Versions of packages digikam suggests: ii breeze-icon-theme 4:5.103.0-1 pn digikam-doc ii systemsettings 4:5.27.2-1 -- no debconf information
Bug#1034213: arno-iptables-firewall: dh_installsystemd doesn't handle files in /usr/lib/systemd/system
Hello Laurant, Hello Andreas, On Wed, 2023-04-12 at 13:43 +0200, Andreas Henriksson wrote: > On Tue, Apr 11, 2023 at 09:37:27AM +0200, bi...@debian.org wrote: > > Package: arno-iptables-firewall > > Version: 2.1.1-7 > > Severity: serious > > Tags: sid bookworm > > User: debhel...@packages.debian.org > > Usertags: systemd-files-in-usr-bookworm > > > > Dear Maintainer, > > > > It seems that your package arno-iptables-firewall is shipping files > > (.service, .socket or > > .timer) in /usr/lib/systemd/system. > [...] > > It seems the package has manually written maintainer scripts (instead > of > letting debhelper generating the proper code): > > ``` > arno-iptables-firewall-2.1.1> grep -R deb-systemd-helper debian/ > debian/postrm: # Remove deb-systemd-helper's state file > debian/postrm: deb-systemd-helper purge > arno-iptables-firewall.service > debian/postinst:deb-systemd-helper enable > arno-iptables-firewall.service > ``` > > So while I think manually written maintscript code should be frowned > upon (since it's a very common source of bugs), I guess this means > this bug is not RC severity?! > Laurent, as Andreas already pointed out arno-iptables-firewall (AIF) does not make use of dh_installsystemd but instead uses deb-systemd- helper with its maintainer scripts. A quick look into the source code of deb-systemd-helper [1] showed that this tools can deal with a service file stored in /usr/lib/systemd/system. This matches my observation that since arno-iptables-firewall 2.1.1-5 local debci runs using qemu as well as those at the Ubuntu site [2] were processed successfully. Debian's CI [3] unfortunately does not support the isolation-machine restriction, so there are no successful tests logged there. Therefore this bug against arno-iptables-firewall seems like a false negative to me, and I would like to ask you to check my arguments and close the bug eventually. Let me know if you still believe the service file should be moved back to /lib from /usr/lib. Andreas, I am not sure how it might be possible to have everything created automatically by debhelper, especially the part creating an initial configuration from user input might prevent this. If you have any suggestions how to simplify the maintainer scripts I am happy to adopt these. Best, Sven [1] https://sources.debian.org/src/init-system-helpers/1.65.2/script/deb-systemd-helper/#L153 [2] https://autopkgtest.ubuntu.com/packages/arno-iptables-firewall/jammy/amd64 [3] https://ci.debian.net/packages/a/arno-iptables-firewall/ -- GPG Fingerprint 3DF5 E8AA 43FC 9FDF D086 F195 ADF5 0EDA F8AD D585 signature.asc Description: This is a digitally signed message part
Bug#1034272: marked as done (corectrl: Crash: missing runtime dep qml-module-qtquick-window2)
Your message dated Wed, 12 Apr 2023 19:04:30 + with message-id and subject line Bug#1034272: fixed in corectrl 1.3.5+ds-1 has caused the Debian Bug report #1034272, regarding corectrl: Crash: missing runtime dep qml-module-qtquick-window2 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.) -- 1034272: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034272 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: corectrl Severity: grave Version: 1.3.3+ds-1 X-Debbugs-CC: t...@debian.org matthias.geiger1...@tutanota.de Hi, Forwarded from https://www.phoronix.com/news/CoreCtrl-In-Debian-Ubuntu-23.04 : % corectrl [11-04-23 21:40:40.595][W] glxinfo command failed QQmlApplicationEngine failed to load component qrc:/qml/main.qml:11:1: Type ApplicationWindow unavailable file:///usr/lib/x86_64-linux- gnu/qt5/qml/QtQuick/Controls.2/Material/ApplicationWindow.qml:38:1: module "QtQuick.Window" is not installed [11-04-23 21:40:43.014][W] QML engine failed to load main interface! [11-04-23 21:40:43.014][W] Initialization failed [11-04-23 21:40:43.014][W] Exiting... terminate called without an active exception [1]5228 IOT instruction corectrl This error will disappear once qml-module-qtquick-window2 is installed. Looks like corectrl is (at least) missing this runtime dependency. Best Regards, Boyuan Yang signature.asc Description: This is a digitally signed message part --- End Message --- --- Begin Message --- Source: corectrl Source-Version: 1.3.5+ds-1 Done: Matthias Geiger We believe that the bug you reported is fixed in the latest version of corectrl, 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 1034...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Matthias Geiger (supplier of updated corectrl package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 09 Apr 2023 09:27:45 +0200 Source: corectrl Architecture: source Version: 1.3.5+ds-1 Distribution: unstable Urgency: medium Maintainer: Gürkan Myczko Changed-By: Matthias Geiger Closes: 1034272 Changes: corectrl (1.3.5+ds-1) unstable; urgency=medium . * New upstream release * Added missing runtime deps in d/control (Closes: #1034272) * Updated extended description Checksums-Sha1: e3e52f8348c943ff2b175efc9912f81c4b928626 2244 corectrl_1.3.5+ds-1.dsc ea06dc850157874c36797c3345414050d4e36ab1 316370 corectrl_1.3.5+ds.orig.tar.gz 51f48e0135181c5fc38942bc003a50a8a4baa819 3116 corectrl_1.3.5+ds-1.debian.tar.xz c25896793a8379a814252317cbc614f57419d046 13184 corectrl_1.3.5+ds-1_amd64.buildinfo Checksums-Sha256: 66128b3b4d245a3b83ebb207f6e514357f451f106b87fd13f9780abced09aefc 2244 corectrl_1.3.5+ds-1.dsc 8a5f740d8d398f6730924ff80ba7f34ae8e7bb50bba666a8d0f5aa585d89dd77 316370 corectrl_1.3.5+ds.orig.tar.gz 12adc3f0c8348dbbb98d8c4375458c205569a129bd93b94e15a2e0957b441258 3116 corectrl_1.3.5+ds-1.debian.tar.xz 8b17d3421a6c90f911227423dda02e2cd8334346befe68d12b8dd5e62ad6b57b 13184 corectrl_1.3.5+ds-1_amd64.buildinfo Files: 1af9bc3bce3107e718336984e865b621 2244 utils optional corectrl_1.3.5+ds-1.dsc fdadee9fe176594fbd2c2bfb49027f34 316370 utils optional corectrl_1.3.5+ds.orig.tar.gz 9408f84022d494502156f0e7e2ab7561 3116 utils optional corectrl_1.3.5+ds-1.debian.tar.xz ca59c7c3ab3a56bf74ea4549a011ef8a 13184 utils optional corectrl_1.3.5+ds-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJUBAEBCgA+FiEEwuGmy/3s5RGopBdtGL0QaztsVHUFAmQ2+XYgHG1hdHRoaWFz LmdlaWdlcjEwMjRAdHV0YW5vdGEuZGUACgkQGL0QaztsVHUI5hAAuDn/19qtJ221 Bc22c87uI24fJld2CQ48hu5VEVlc9gtnF/TIkJV1Fw4pyADfbHa/TuTyTLX/kZtu 0z129HH4SPTBhqmkb0Kb4CvJAER+VftnqA18BNzsao6KOiVXVit8pyyijv4J8HOO YZtngB2itNlp4efJbOUXc/5dcHCauYt5qmn6q1VNxwZSsWAAn2dm5sY49EXE+b66 dE+1EeMBDRNoCYew2hthk1HJ94IqJjE3Wg3ATfozZaSJS80qMd4ULHgOcXJ1R13n XwJr5VukiSf+PTcUtvjofAlhEQuqP0CfLRFYYDlhgDE6jBkeSFctUKFbpyo4aAwD TJEtSYG8A6+ft3HUIPHW/ZxRQX6aAYtiVIiW32fZS121L6Purh1nSu++lr+addMG wyt0wK/y5StOzh5mx3ziTRS81fqM8mUtwGeEswYKA6HgK5xYHptjaX4Gbi4HVenF eRJKmykgdRhinOtqO5tcYRkFs1Hc26cqzCiOURYLnDI8djiEsc2IjdPNB5tKBA4D FTatJ4NxRnkqVxReNwiwkTBCL6OfOjqlfjVJ+jSOMAS35BnjoYMt8i3s2smKE8nn
Bug#1034304: geoalchemy2: autopkgtest regression on s390x: AssertionError
Source: geoalchemy2
Version: 0.13.1-2
Severity: serious
Tags: sid bookworm bookworm-ignore
User: debian...@lists.debian.org
Usertags: regression
Dear maintainer(s),
With a recent upload of geoalchemy2 the autopkgtest of geoalchemy2 fails
in testing on s390x when that autopkgtest is run with the binary
packages of geoalchemy2 from unstable. It passes when run with only
packages from testing. In tabular form:
passfail
geoalchemy2from testing0.13.1-2
all others from testingfrom testing
I copied some of the output at the bottom of this report.
Currently this regression is blocking the migration to testing [1]. Can
you please investigate the situation and fix it? Please be reminded that
s390x is our only big endian architecture.
[Release Team member hat on] Because we're currently in the hard freeze
for bookworm, I have marked this bug as bookworm-ignore. Targeted fixes
are still welcome.
More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
Paul
[1] https://qa.debian.org/excuses.php?package=geoalchemy2
https://ci.debian.net/data/autopkgtest/testing/s390x/g/geoalchemy2/32779104/log.gz
=== FAILURES
===
_ TestInsertionORM.test_WKTElement[postgresql]
_
self =
session =
Lake = .Lake'>, setup_tables
= None
def test_WKTElement(self, session, Lake, setup_tables):
lake = Lake(WKTElement("LINESTRING(0 0,1 1)", srid=4326))
session.add(lake)
session.flush()
session.expire(lake)
assert isinstance(lake.geom, WKBElement)
assert str(lake.geom) == (
"010220e61002000"
"000f03ff03f"
)
E AssertionError: assert '00200200...0' ==
'010220e6...0f03f'
E -
010220e6100200f03ff03f
E ? - ^
^ -- - --
E +
00200210e600023ff03ff0
E ?++ + ^
+++ ^
tests/test_functional.py:297: AssertionError
_ TestInsertionORM.test_WKBElement[postgresql]
_
self =
session =
Lake = .Lake'>, setup_tables
= None
def test_WKBElement(self, session, Lake, setup_tables):
shape = LineString([[0, 0], [1, 1]])
lake = Lake(from_shape(shape, srid=4326))
session.add(lake)
session.flush()
session.expire(lake)
assert isinstance(lake.geom, WKBElement)
assert str(lake.geom) == (
"010220e61002000"
"000f03ff03f"
)
E AssertionError: assert '00200200...0' ==
'010220e6...0f03f'
E -
010220e6100200f03ff03f
E ? - ^
^ -- - --
E +
00200210e600023ff03ff0
E ?++ + ^
+++ ^
tests/test_functional.py:313: AssertionError
TestUpdateORM.test_Raster[postgresql]
_
self = 0x3ff8900de90>
session =
Ocean = .Ocean'>
setup_tables = None
def test_Raster(self, session, Ocean, setup_tables):
skip_postgis1(session)
polygon = WKTElement("POLYGON((0 0,1 1,0 1,0 0))", srid=4326)
o = Ocean(polygon.ST_AsRaster(5, 5))
session.add(o)
session.flush()
session.expire(o)
assert isinstance(o.rast, RasterElement)
rast_data = (
"0101009A99C93F9A99C9BFF03"
"FE61005000500440001010101010101010100"
"01010101010001"
)
> assert o.rast.data == rast_data
E AssertionError: assert '013F...1' ==
'0101009A...1'
E Skipping 45 identical trailing characters in diff, use -v to show
E -
0101009A99C93F9A99C9BFF03FE61005000500440001010
E ? ^ - --- ^^
-- --- --
E +
013FCABFCA3FF010E600050005440001010
E ? ^^^ ^^^ +++ ^^^
++
tests/test_functional_postgresql.py:365: AssertionError
__
Bug#1034303: nvidia-cuda-toolkit breaks nvidia-cuda-samples autopkgtest on amd64: bad exit status: 2
Source: nvidia-cuda-toolkit, nvidia-cuda-samples Control: found -1 nvidia-cuda-toolkit/11.8.0-3 Control: found -1 nvidia-cuda-samples/11.8~dfsg-2 Severity: serious Tags: sid bookworm bookworm-ignore User: debian...@lists.debian.org Usertags: breaks needs-update Dear maintainer(s), With a recent upload of nvidia-cuda-toolkit the autopkgtest of nvidia-cuda-samples fails on amd64 in testing when that autopkgtest is run with the binary packages of nvidia-cuda-toolkit from unstable. It passes when run with only packages from testing. In tabular form: passfail nvidia-cuda-toolkitfrom testing11.8.0-3 nvidia-cuda-samplesfrom testing11.8~dfsg-2 all others from testingfrom testing I copied some of the output at the bottom of this report. Currently this regression is blocking the migration of nvidia-cuda-toolkit to testing [1]. Due to the nature of this issue, I filed this bug report against both packages. Can you please investigate the situation and reassign the bug to the right package? [Release Team member hat on] Because we're currently in the hard freeze for bookworm, I have marked this bug as bookworm-ignore. More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=nvidia-cuda-toolkit https://ci.debian.net/data/autopkgtest/testing/amd64/n/nvidia-cuda-samples/32796174/log.gz Building module: Cleaning build area... 'make' -j2 KVER=6.1.0-7-amd64 IGNORE_CC_MISMATCH='1'..(bad exit status: 2) Error! Bad return status for module build on kernel: 6.1.0-7-amd64 (x86_64) Consult /var/lib/dkms/nvidia-fs/2.13/build/make.log for more information. E: nvidia-fs/2.13 failed to build for 6.1.0-7-amd64 == /var/lib/dkms/nvidia-fs/2.13/build/make.log == DKMS make.log for nvidia-fs-2.13 for kernel 6.1.0-7-amd64 (x86_64) Tue Apr 11 23:11:31 UTC 2023 ./configure 6.1.0-7-amd64 Picking NVIDIA driver sources from NVIDIA_SRC_DIR=/usr/src/nvidia-current-525.89.02/nvidia. If that does not meet your expectation, you might have a stale driver still around and that might cause problems. chmod +x ./create_nv.symvers.sh ./create_nv.symvers.sh 6.1.0-7-amd64 -E- Cannot locate nvidia modules! CUDA driver must be installed before installing this package! make: *** [Makefile:103: nv_symbols] Error 1 make: *** Waiting for unfinished jobs checking if uaccess.h access_ok has 3 parameters... no checking if uaccess.h access_ok has 2 parameters... yes Checking if blkdev.h has blk_rq_payload_bytes... yes Checking if fs.h has call_read_iter and call_write_iter... yes Checking if fs.h has filemap_range_has_page... no Checking if kiocb structue has ki_complete field... yes Checking if KI_COMPLETE has 3 parameters ... no Checking if vm_fault_t exist in mm_types.h... yes Checking if IOCB_HIPRI flag exists in fs.h... yes Checking if enum PCIE_SPEED_32_0GT exists in pci.h... yes Checking if atomic64_t counter is of type long... no Checking if RQF_COPY_USER is present or not... no Checking if dma_drain_size and dma_drain_needed are present in struct request_queue... no Checking if struct proc_ops is present or not ... yes Checking if split is present in vm_operations_struct or not ... no Checking if mremap in vm_operations_struct has one parameter... yes Checking if mremap in vm_operations_struct has two parameters... no Checking if symbol module_mutex is present... no Checking if blk-integrity.h is present... yes I: Trying to build nvidia-fs/2.13 for 6.1.0-7-cloud-amd64 Sign command: /usr/lib/linux-kbuild-6.1/scripts/sign-file Signing key: /var/lib/dkms/mok.key Public certificate (MOK): /var/lib/dkms/mok.pub Building module: Cleaning build area... 'make' -j2 KVER=6.1.0-7-cloud-amd64 IGNORE_CC_MISMATCH='1'..(bad exit status: 2) Error! Bad return status for module build on kernel: 6.1.0-7-cloud-amd64 (x86_64) Consult /var/lib/dkms/nvidia-fs/2.13/build/make.log for more information. E: nvidia-fs/2.13 failed to build for 6.1.0-7-cloud-amd64 == /var/lib/dkms/nvidia-fs/2.13/build/make.log == DKMS make.log for nvidia-fs-2.13 for kernel 6.1.0-7-cloud-amd64 (x86_64) Tue Apr 11 23:11:53 UTC 2023 ./configure 6.1.0-7-cloud-amd64 Picking NVIDIA driver sources from NVIDIA_SRC_DIR=/usr/src/nvidia-current-525.89.02/nvidia. If that does not meet your expectation, you might have a stale driver still around and that might cause problems. chmod +x ./create_nv.symvers.sh ./create_nv.symvers.sh 6.1.0-7-cloud-amd64 -E- Cannot locate nvidia modules! CUDA driver must be installed before installing this package! make: *** [Makefile:103: nv_symbols] Error 1 make: *** Waiting for unfinished jobs checking if uaccess.h access_ok has 3 parameters... no checking if uaccess.h access_ok has 2 parameters... yes Checking if blkdev.h has blk_rq_payload_bytes... yes Checking if
Processed: nvidia-cuda-toolkit breaks nvidia-cuda-samples autopkgtest on amd64: bad exit status: 2
Processing control commands: > found -1 nvidia-cuda-toolkit/11.8.0-3 Bug #1034303 [src:nvidia-cuda-toolkit, src:nvidia-cuda-samples] nvidia-cuda-toolkit breaks nvidia-cuda-samples autopkgtest on amd64: bad exit status: 2 Marked as found in versions nvidia-cuda-toolkit/11.8.0-3. > found -1 nvidia-cuda-samples/11.8~dfsg-2 Bug #1034303 [src:nvidia-cuda-toolkit, src:nvidia-cuda-samples] nvidia-cuda-toolkit breaks nvidia-cuda-samples autopkgtest on amd64: bad exit status: 2 Marked as found in versions nvidia-cuda-samples/11.8~dfsg-2. -- 1034303: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034303 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1033714: at runtime, flanker tries to create files under /usr
On Wed, Apr 12, 2023 at 07:52:53AM -0700, Daniel Kauffman wrote:
>
> > > > > This file is updated automatically if you're using a
> > > > > different version of the library than the one with which the
> > > > > file was created originally.
> > > This seems to confirm that for each version of the package, these
> > > files should be generated from debian/rules at build time.
> > Only if you want to also regenerate them when a new python3-ply is
> > uploaded, as far as I understand it.
> The python3-flanker package **could** be tightly coupled with the
> python3-ply package, but that wouldn't be ideal.
What else do you mean by generating files at the build time then?
The same problem will exist after a new python3-ply is uploaded.
> > > In the case of python3-flanker, the package does not work until the
> > > file is generated.
> > It does for me.
> Have you used flanker.addresslib.address.parse('u...@example.com') ?
Sure. It returns "u...@example.com".
> Other commands might not generate the files.
No, only importing shows these warnings. The second line doesn't.
> Are you running as root?
No, otherwise I wouldn't see the warnings.
> Have you already generated these files?
No, otherwise it wouldn't attempt to regenerate them and wouldn't print
these warnings.
The only difference is that I'm using Python 3.11, not 3.9, as it doesn't
exist in testing.
Bug#1033714: at runtime, flanker tries to create files under /usr
This file is updated automatically if you're using a different
version of the library than the one with which the file was created
originally.
This seems to confirm that for each version of the package, these
files should be generated from debian/rules at build time.
Only if you want to also regenerate them when a new python3-ply is
uploaded, as far as I understand it.
The python3-flanker package **could** be tightly coupled with the
python3-ply package, but that wouldn't be ideal.
Also I think
https://github.com/mailgun/flanker/commit/96d774eb6d67b1c5fafe711394c3756df7bb14ad
(not released yet) is probably about this issue.
That would be great! If the files are not generated at either build time
or run time, then this particular issue would be solved without special
handling for Debian packaging, which is always preferred.
Looks like this commit should be in the next release after v0.9.15
(released March 3, 2023).
In the case of python3-flanker, the package does not work until the
file is generated.
It does for me.
Have you used flanker.addresslib.address.parse('u...@example.com') ?
Other commands might not generate the files.
Are you running as root? In this case, the files would be generated and
saved without permission errors.
Have you already generated these files? Possibly by previously running
as root or possibly by previously installing flanker in a user environment?
Bug#1032183: marked as done (libgusb-dev: missing dependency on libjson-glib-1.0-dev)
Your message dated Wed, 12 Apr 2023 14:39:38 +
with message-id
and subject line Bug#1032183: fixed in libgusb 0.4.5-1.1
has caused the Debian Bug report #1032183,
regarding libgusb-dev: missing dependency on libjson-glib-1.0-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.)
--
1032183: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032183
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libgusb-dev
Version: 0.4.5-1
Severity: serious
Justification: Policy 7.2
To reproduce:
* Have a minimal Debian chroot or container
* apt install libgusb-dev
* pkg-config --cflags --libs gusb
Expected result: success, compiler flags are shown
Actual result:
> + pkg-config --cflags --libs gusb gobject-2.0 glib-2.0
> Package json-glib-1.0 was not found in the pkg-config search path.
> Perhaps you should add the directory containing `json-glib-1.0.pc'
> to the PKG_CONFIG_PATH environment variable
> Package 'json-glib-1.0', required by 'gusb', not found
I'll send the obvious patch when I have a bug number.
It's easy to reproduce this class of issues with an autopkgtest like
the one added by the attached patch, and running autopkgtest before upload
can detect and prevent these missing dependencies before they reach Debian.
smcv
-- System Information:
Debian Release: bookworm/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'stable-security'), (500,
'oldstable-debug'), (500, 'oldoldstable'), (500, 'buildd-unstable'), (500,
'unstable'), (500, 'testing'), (500, 'stable'), (500, 'oldstable'), (1,
'experimental-debug'), (1, 'buildd-experimental'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 6.1.0-5-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (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 libgusb-dev depends on:
ii gir1.2-gusb-1.0 0.4.5-1
ii libc6 2.36-8
ii libglib2.0-02.74.5-1
ii libglib2.0-dev 2.74.5-1
ii libgusb20.4.5-1
ii libjson-glib-1.0-0 1.6.6-1
ii libusb-1.0-0-dev2:1.0.26-1
libgusb-dev recommends no packages.
libgusb-dev suggests no packages.
-- no debconf information
>From e5c5697632a33b004cba3c687357f7408a591904 Mon Sep 17 00:00:00 2001
From: Simon McVittie
Date: Wed, 1 Mar 2023 10:25:00 +
Subject: [PATCH 1/2] Add a superficial autopkgtest for libgusb-dev
This checks whether the -dev package has all the required dependencies
to link a simple program with libgusb.
Signed-off-by: Simon McVittie
---
debian/tests/control | 5 +
debian/tests/libgusb-dev | 46
2 files changed, 51 insertions(+)
create mode 100644 debian/tests/control
create mode 100755 debian/tests/libgusb-dev
diff --git a/debian/tests/control b/debian/tests/control
new file mode 100644
index 000..2a91858
--- /dev/null
+++ b/debian/tests/control
@@ -0,0 +1,5 @@
+Tests: libgusb-dev
+Restrictions: allow-stderr, superficial
+Depends:
+ build-essential,
+ libgusb-dev,
diff --git a/debian/tests/libgusb-dev b/debian/tests/libgusb-dev
new file mode 100755
index 000..22bec3f
--- /dev/null
+++ b/debian/tests/libgusb-dev
@@ -0,0 +1,46 @@
+#!/bin/sh
+# Copyright 2023 Simon McVittie
+# SPDX-License-Identifier: LGPL-2.1-or-later
+
+set -eux
+
+if [ -n "${AUTOPKGTEST_ARTIFACTS-}" ]; then
+WORKDIR="$AUTOPKGTEST_ARTIFACTS"
+else
+WORKDIR="$(mktemp -d)"
+trap 'cd /; rm -fr "$WORKDIR"' 0 INT QUIT ABRT PIPE TERM
+fi
+
+if [ -n "${DEB_HOST_GNU_TYPE:-}" ]; then
+CROSS_COMPILE="$DEB_HOST_GNU_TYPE-"
+else
+CROSS_COMPILE=
+fi
+
+cat >> "$WORKDIR"/trivial.c <
+
+#include
+#include
+
+int main (int argc, char *argv[])
+{
+ GError *error = NULL;
+ GUsbContext *context = NULL;
+
+ context = g_usb_context_new ();
+
+ if (context == NULL)
+g_error ("%s", error->message);
+
+ g_object_unref (context);
+ return 0;
+}
+EOF
+
+cd "$WORKDIR"
+
+# Deliberately word-splitting pkg-config's output:
+# shellcheck disable=SC2046
+"${CROSS_COMPILE}gcc" -otrivial trivial.c $("${CROSS_COMPILE}pkg-config" --cflags --libs gusb gobject-2.0 glib-2.0)
+./trivial
--
2.39.2
--- End Message ---
--- Begin Message ---
Source: libgusb
Source-Version: 0.4.5-1.1
Done: Jeremy Bicha
We believe that the bug you reported is fixed in the latest version of
libgusb, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
Bug#1033424: image-factory: FTBFS in testing: AssertionError: pylint found issues:
Hello,
I have attached a debdiff where I replace the broad exception types with
appropriate error types. This patch satisfies the pylint test and allows
the package to build without issues. I can upload this RC bug fix as a
NMU if you want. Thanks!
--
Josef Schneider
GPG Fingerprint 3267 0331 DB61 A817 7D25 4D05 5A44 BC12 F2A8 E58F
diff -Nru image-factory-1.0.2/debian/changelog
image-factory-1.0.2/debian/changelog
--- image-factory-1.0.2/debian/changelog2021-11-12 16:52:40.0
+0100
+++ image-factory-1.0.2/debian/changelog2023-04-12 15:50:18.0
+0200
@@ -1,3 +1,11 @@
+image-factory (1.0.2-1.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * debian/patches: Add 0001-replace-broad-exceptions.patch.
++ Pass pylint test and fix FTBFS (Closes: #1033424).
+
+ -- Josef Schneider Wed, 12 Apr 2023 15:50:18 +0200
+
image-factory (1.0.2-1) unstable; urgency=medium
* New upstream release
diff -Nru
image-factory-1.0.2/debian/patches/0001-replace-broad-exceptions.patch
image-factory-1.0.2/debian/patches/0001-replace-broad-exceptions.patch
--- image-factory-1.0.2/debian/patches/0001-replace-broad-exceptions.patch
1970-01-01 01:00:00.0 +0100
+++ image-factory-1.0.2/debian/patches/0001-replace-broad-exceptions.patch
2023-04-12 15:50:18.0 +0200
@@ -0,0 +1,43 @@
+From a32952d31c02d2ce2425032e1960c0c292a29855 Mon Sep 17 00:00:00 2001
+From: Josef Schneider
+Date: Wed, 12 Apr 2023 15:49:41 +0200
+Subject: [PATCH] replace broad exceptions
+
+---
+ image-factory | 6 +++---
+ 1 file changed, 3 insertions(+), 3 deletions(-)
+
+diff --git a/image-factory b/image-factory
+index f8dffe0..5130fd7 100755
+--- a/image-factory
b/image-factory
+@@ -61,7 +61,7 @@ def get_config():
+ if env_name in os.environ:
+ config_files = [os.environ[env_name]]
+ if not os.path.isfile(config_files[0]):
+-raise Exception(
++raise FileNotFoundError(
+ "'" + config_files[0] + "' (set in " + env_name + ") is not a
valid file."
+ )
+ else:
+@@ -135,7 +135,7 @@ def cache_file(cache_dir, source):
+ elif source.startswith("rsync:"):
+ call_command(["rsync", "--no-motd", source, destination])
+ else:
+-raise Exception(f"No download handler for file '{source}' found.")
++raise ValueError(f"No download handler for file '{source}' found.")
+ return relative_destination
+
+
+@@ -163,7 +163,7 @@ def download_and_publish(config, image, source, filename):
+ elif source.startswith("rsync:"):
+ call_command(["rsync", "--no-motd", source, destination])
+ else:
+-raise Exception(f"No download handler for file '{source}' found.")
++raise ValueError(f"No download handler for file '{source}' found.")
+ return destination
+
+
+--
+2.38.1
+
diff -Nru image-factory-1.0.2/debian/patches/series
image-factory-1.0.2/debian/patches/series
--- image-factory-1.0.2/debian/patches/series 1970-01-01 01:00:00.0
+0100
+++ image-factory-1.0.2/debian/patches/series 2023-04-12 15:50:18.0
+0200
@@ -0,0 +1 @@
+0001-replace-broad-exceptions.patch
OpenPGP_0x5A44BC12F2A8E58F.asc
Description: OpenPGP public key
OpenPGP_signature
Description: OpenPGP digital signature
Bug#1034042: marked as pending in openvswitch
Control: tag -1 pending Hello, Bug #1034042 in openvswitch 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/third-party/openvswitch/-/commit/345f17c6b265e9692640ad98b3b1571fc2a2c6db * CVE-2023-1668: Remote traffic denial of service via crafted packets with IP proto 0. Applied upstream patch: ofproto-dpif-xlate: Always mask ip proto field (Closes: #1034042). (this message was generated automatically) -- Greetings https://bugs.debian.org/1034042
Processed: Bug#1034042 marked as pending in openvswitch
Processing control commands: > tag -1 pending Bug #1034042 [src:openvswitch] openvswitch: CVE-2023-1668: Remote traffic denial of service via crafted packets with IP proto 0 Ignoring request to alter tags of bug #1034042 to the same tags previously set -- 1034042: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034042 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#1034042 marked as pending in openvswitch
Processing control commands: > tag -1 pending Bug #1034042 [src:openvswitch] openvswitch: CVE-2023-1668: Remote traffic denial of service via crafted packets with IP proto 0 Added tag(s) pending. -- 1034042: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034042 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1034042: marked as pending in openvswitch
Control: tag -1 pending Hello, Bug #1034042 in openvswitch 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/third-party/openvswitch/-/commit/6e7cc9dcb5c5303c171847398938155a50d06907 * CVE-2023-1668: Remote traffic denial of service via crafted packets with IP proto 0. Applied upstream patch: ofproto-dpif-xlate: Always mask ip proto field (Closes: #1034042). (this message was generated automatically) -- Greetings https://bugs.debian.org/1034042
Bug#1034289: inkscape: canvas stops updating completely when trying to edit a text box
Package: inkscape Version: 1.2.2-2+b1 Followup-For: Bug #1034289 Additional information: the issue I'm seeing seems to match upstream issue #3664 https://gitlab.com/inkscape/inkscape/-/issues/3664 and seems to be related to a GTK bug when GTK_IM_MODULE=xim Unsetting the variable or testing one of the values recommended in the comments to the bug solves the issue for me.
Bug#1034218: marked as done (cfengine3: dh_installsystemd doesn't handle files in /usr/lib/systemd/system)
Your message dated Wed, 12 Apr 2023 13:19:57 + with message-id and subject line Bug#1034218: fixed in cfengine3 3.21.0-2 has caused the Debian Bug report #1034218, regarding cfengine3: dh_installsystemd doesn't handle files in /usr/lib/systemd/system 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.) -- 1034218: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034218 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: cfengine3 Version: 3.21.0-1 Severity: serious Tags: sid bookworm User: debhel...@packages.debian.org Usertags: systemd-files-in-usr-bookworm Dear Maintainer, It seems that your package cfengine3 is shipping files (.service, .socket or .timer) in /usr/lib/systemd/system. This is not supported by the version of dh_installsystemd/debhelper currently in unstable and bookworm (See: #1031695). That means that currently your service might not be enabled at boot and/or started as expected. With the freeze currently in effect, debhelper will not be fixed for bookworm. As a result, could you please move these files to /lib/systemd/system instead so they are properly detected by debhelper? As soon as debhelper is supporting (not until bookworm+1 aka Trixie) you will be able to move them back to the newer location. Note that bookworm is currently in hard freeze, please limit the changes you are uploading to the ones fixing RC bugs. Also note that you might have to request a freeze exception to the release team. See: https://release.debian.org/testing/freeze_policy.html Feel free to contact me if you have any questions. Kind regards, Laurent Bigonville The list of packages has been generated with the following command: apt-file search -x '^/usr/lib/systemd/system/.*\.(service|timer|socket)$'|cut -d: -f1|sort -u --- End Message --- --- Begin Message --- Source: cfengine3 Source-Version: 3.21.0-2 Done: Christoph Martin We believe that the bug you reported is fixed in the latest version of cfengine3, 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 1034...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Christoph Martin (supplier of updated cfengine3 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, 12 Apr 2023 10:56:05 +0200 Source: cfengine3 Architecture: source Version: 3.21.0-2 Distribution: unstable Urgency: medium Maintainer: CFEngine Team Changed-By: Christoph Martin Closes: 1034218 Changes: cfengine3 (3.21.0-2) unstable; urgency=medium . * fix systemd path (closes: #1034218) Checksums-Sha1: 20b75bcad5654642269b0b6a1a3be56f4a4c8993 2404 cfengine3_3.21.0-2.dsc b8dd5963175886cbd50eec5d0248374eb107e4c2 521490 cfengine3_3.21.0.orig-masterfiles.tar.gz 0246a6dc2a292a7749526e79374d51695389696a 3339717 cfengine3_3.21.0.orig.tar.gz 3d1dd37e57526b3eddb600eb29460bbe2612cd5d 21092 cfengine3_3.21.0-2.debian.tar.xz 2e44aa482c1f55a96858c6812c9bdba59d95ec07 9563 cfengine3_3.21.0-2_amd64.buildinfo Checksums-Sha256: 3bb625e1f3c2948e465a452a1933dbe80c3679d91c5c3b095f9ed2bd55353b02 2404 cfengine3_3.21.0-2.dsc 013ebe68599915cedb4bf753b471713d91901a991623358b9a967d9a779bcc16 521490 cfengine3_3.21.0.orig-masterfiles.tar.gz 911778ddb0a4e03a3ddfc8fc0f033136e1551849ea2dcbdb3f0f14359dfe3126 3339717 cfengine3_3.21.0.orig.tar.gz 6440ba791ecc679ac6509224795faf8001f6f1d392723fc211a42e04899ce13f 21092 cfengine3_3.21.0-2.debian.tar.xz 871da1a08607b8109838d5b493f300679e5995310dede2b269202a7f3625f917 9563 cfengine3_3.21.0-2_amd64.buildinfo Files: c10566467906b1e4c64018b272d23c96 2404 admin optional cfengine3_3.21.0-2.dsc 8d87053a6e0a4166874199706f807bfa 521490 admin optional cfengine3_3.21.0.orig-masterfiles.tar.gz 5318e40702bc66a3ece44ec4ad77712b 3339717 admin optional cfengine3_3.21.0.orig.tar.gz 4f335a3cf21072b4ee13ccb7c6daf0b8 21092 admin optional cfengine3_3.21.0-2.debian.tar.xz 9e146a06717f3f6e1fde830ee48c2163 9563 admin optional cfengine3_3.21.0-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEt1cFkfJ3DVbrq4cu7mlEXgxb5BcFAmQ2qXIACgkQ7mlEXgxb 5BfQ8Q//R42aa8EYi/NRiE/40LTrjllWRAKVjWrJHa9rYaLZPMVA1xNpZRGe7GIq
Bug#1034213: arno-iptables-firewall: dh_installsystemd doesn't handle files in /usr/lib/systemd/system
On Tue, Apr 11, 2023 at 09:37:27AM +0200, bi...@debian.org wrote: > Package: arno-iptables-firewall > Version: 2.1.1-7 > Severity: serious > Tags: sid bookworm > User: debhel...@packages.debian.org > Usertags: systemd-files-in-usr-bookworm > > Dear Maintainer, > > It seems that your package arno-iptables-firewall is shipping files > (.service, .socket or > .timer) in /usr/lib/systemd/system. [...] It seems the package has manually written maintainer scripts (instead of letting debhelper generating the proper code): ``` arno-iptables-firewall-2.1.1> grep -R deb-systemd-helper debian/ debian/postrm: # Remove deb-systemd-helper's state file debian/postrm: deb-systemd-helper purge arno-iptables-firewall.service debian/postinst:deb-systemd-helper enable arno-iptables-firewall.service ``` So while I think manually written maintscript code should be frowned upon (since it's a very common source of bugs), I guess this means this bug is not RC severity?! Regards, Andreas Henriksson
Bug#1034214: tcmu-runner: dh_installsystemd doesn't handle files in /usr/lib/systemd/system
On Tue, Apr 11, 2023 at 09:37:27AM +0200, bi...@debian.org wrote: > Package: tcmu-runner > Version: 1.5.4-4 > Severity: serious > Tags: sid bookworm > User: debhel...@packages.debian.org > Usertags: systemd-files-in-usr-bookworm > > Dear Maintainer, > > It seems that your package tcmu-runner is shipping files (.service, .socket or > .timer) in /usr/lib/systemd/system. [...] tcmu-1.5.4> grep -R systemd.system . ./debian/tcmu-runner.install:debian/tmp/usr/lib/systemd/system/tcmu-runner.service ./README.md:1. If using systemd, copy `org.kernel.TCMUService1.service` to `/usr/share/dbus-1/system-services/` and `tcmu-runner.service` to `/lib/systemd/system`. ./CMakeLists.txt: install(FILES tcmu-runner.service DESTINATION /usr/lib/systemd/system/) These paths are wrong and the culprit of this bug report. You could change them to use the currently correct path, but then you would have to revert that again after bookworm is released when the paths will change again. A better solution would derive the path from systemd.pc, eg. pkg-config --variable=systemdsystemunitdir systemd (Note: this needs pkg-config and systemd in build-deps) Since the upstream build system is CMake, there are plenty of others to look at of how to implement using pkg-config and querying the variable in CMake. This should give you atleast a few hits that could be possible examples to follow: https://codesearch.debian.net/search?q=systemdsystemunitdir+path%3ACMake=0 https://codesearch.debian.net/search?q=systemdsystemunitdir+path%3AFindSystemd=0 Regards, Andreas Henriksson
Bug#1034215: drkonqi: dh_installsystemd doesn't handle files in /usr/lib/systemd/system
Hello again,
On Wed, Apr 12, 2023 at 01:19:52PM +0200, Andreas Henriksson wrote:
> On Tue, Apr 11, 2023 at 09:37:27AM +0200, bi...@debian.org wrote:
> > Package: drkonqi
> > Version: 5.27.2-1
> > Severity: serious
> > Tags: sid bookworm
> > User: debhel...@packages.debian.org
> > Usertags: systemd-files-in-usr-bookworm
> >
> > Dear Maintainer,
> >
> > It seems that your package drkonqi is shipping files (.service, .socket or
> > .timer) in /usr/lib/systemd/system.
> [...]
>
> ```
> $ apt-file show drkonqi | grep systemd/system
> drkonqi: /usr/lib/systemd/system/drkonqi-coredump-processor@.service
> ```
I forgot to mention that since this is a template unit (@.service)
maybe the severity should not be RC.
As far as I know debhelper will not enable any instance of a template
unit by default anyway, so the consequences that bigon warned about
probably doesn't apply here?
>
> From ./src/coredump/processor/CMakeLists.txt :
>
> ```
> configure_file(
> drkonqi-coredump-processor@.service.cmake
> ${CMAKE_CURRENT_BINARY_DIR}/drkonqi-coredump-processor@.service
> )
> install(
> FILES ${CMAKE_CURRENT_BINARY_DIR}/drkonqi-coredump-processor@.service
> DESTINATION ${KDE_INSTALL_SYSTEMDUNITDIR}/system
> )
> ```
>
> So apparently KDE_INSTALL_SYSTEMDUNITDIR is not set correctly.
>
> I'm not sure where this variable comes from. The above line is the
> only hit on
> https://codesearch.debian.net/search?q=KDE_INSTALL_SYSTEMDUNITDIR=1
>
> Maybe someone with better understanding of KDE and CMake can help figure this
> out.
>
> If not, I guess you can always add a hack that appends to dh_install to move
> the file into the correct directory as returned by
> `pkg-config --variable=systemdsystemunitdir systemd`.
> (Note: make sure to have systemd.pc available by build-dep on systemd)
Regards,
Andreas Henriksson
Bug#1034215: drkonqi: dh_installsystemd doesn't handle files in /usr/lib/systemd/system
On Tue, Apr 11, 2023 at 09:37:27AM +0200, bi...@debian.org wrote:
> Package: drkonqi
> Version: 5.27.2-1
> Severity: serious
> Tags: sid bookworm
> User: debhel...@packages.debian.org
> Usertags: systemd-files-in-usr-bookworm
>
> Dear Maintainer,
>
> It seems that your package drkonqi is shipping files (.service, .socket or
> .timer) in /usr/lib/systemd/system.
[...]
```
$ apt-file show drkonqi | grep systemd/system
drkonqi: /usr/lib/systemd/system/drkonqi-coredump-processor@.service
```
>From ./src/coredump/processor/CMakeLists.txt :
```
configure_file(
drkonqi-coredump-processor@.service.cmake
${CMAKE_CURRENT_BINARY_DIR}/drkonqi-coredump-processor@.service
)
install(
FILES ${CMAKE_CURRENT_BINARY_DIR}/drkonqi-coredump-processor@.service
DESTINATION ${KDE_INSTALL_SYSTEMDUNITDIR}/system
)
```
So apparently KDE_INSTALL_SYSTEMDUNITDIR is not set correctly.
I'm not sure where this variable comes from. The above line is the
only hit on
https://codesearch.debian.net/search?q=KDE_INSTALL_SYSTEMDUNITDIR=1
Maybe someone with better understanding of KDE and CMake can help figure this
out.
If not, I guess you can always add a hack that appends to dh_install to move
the file into the correct directory as returned by
`pkg-config --variable=systemdsystemunitdir systemd`.
(Note: make sure to have systemd.pc available by build-dep on systemd)
Regards,
Andreas Henriksson
Bug#1034289: inkscape: canvas stops updating completely when trying to edit a text box
Package: inkscape Version: 1.2.2-2+b1 Severity: serious Adding or editing a text box causes the canvas to stop updating altogether. Writing, selecting, etc still works, but the canvas does not refresh anymore until Inkscape is closed and reopened. This is also with the Preferences > Rendering > Update strategy set to "Full redraw". -- System Information: Debian Release: 12.0 APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'testing-security'), (500, 'testing-debug'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.1.0-7-amd64 (SMP w/12 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE 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 Versions of packages inkscape depends on: ii lib2geom1.2.0 1.2.2-3 ii libatkmm-1.6-1v5 2.28.3-1 ii libboost-filesystem1.74.0 1.74.0+ds1-20 ii libc6 2.36-9 ii libcairo-gobject2 1.16.0-7 ii libcairo2 1.16.0-7 ii libcairomm-1.0-1v5 1.14.4-2 ii libcdr-0.1-1 0.1.6-2+b2 ii libfontconfig1 2.14.1-4 ii libfreetype6 2.12.1+dfsg-4 ii libgc1 1:8.2.2-3 ii libgcc-s1 12.2.0-14 ii libgdk-pixbuf-2.0-02.42.10+dfsg-1+b1 ii libglib2.0-0 2.74.6-2 ii libglibmm-2.4-1v5 2.66.5-2 ii libgomp1 12.2.0-14 ii libgsl27 2.7.1+dfsg-3+b1 ii libgspell-1-2 1.12.0-1+b2 ii libgtk-3-0 3.24.37-2 ii libgtkmm-3.0-1v5 3.24.7-1 ii libharfbuzz0b 6.0.0+dfsg-3 ii libjpeg62-turbo1:2.1.5-2 ii liblcms2-2 2.14-2 ii libmagick++-6.q16-88:6.9.11.60+dfsg-1.6 ii libpango-1.0-0 1.50.12+ds-1 ii libpangocairo-1.0-01.50.12+ds-1 ii libpangoft2-1.0-0 1.50.12+ds-1 ii libpangomm-1.4-1v5 2.46.3-1 ii libpng16-161.6.39-2 ii libpoppler-glib8 22.12.0-2+b1 ii libpoppler126 22.12.0-2+b1 ii libpotrace01.16-2 ii libreadline8 8.2-1.3 ii librevenge-0.0-0 0.0.5-3 ii librsvg2-common2.54.5+dfsg-1 ii libsigc++-2.0-0v5 2.12.0-1 ii libsoup2.4-1 2.74.3-1 ii libstdc++6 12.2.0-14 ii libvisio-0.1-1 0.1.7-1+b3 ii libwpg-0.3-3 0.3.3-1 ii libx11-6 2:1.8.4-2 ii libxml22.9.14+dfsg-1.1+b3 ii libxslt1.1 1.1.35-1 ii python33.11.2-1+b1 ii zlib1g 1:1.2.13.dfsg-1 Versions of packages inkscape recommends: ii aspell 0.60.8-4+b1 ii fig2dev 1:3.2.8b-3 ii imagemagick 8:6.9.11.60+dfsg-1.6 ii imagemagick-6.q16 [imagemagick] 8:6.9.11.60+dfsg-1.6 ii imagemagick-7 [imagemagick] 8:7.1.1.6-dmo1 ii libimage-magick-perl 8:6.9.11.60+dfsg-1.6 ii libwmf-bin 0.2.12-5 ii python3-cssselect1.2.0-2 ii python3-lxml 4.9.2-1+b1 ii python3-numpy1:1.24.2-1 ii python3-scour0.38.2-2 Versions of packages inkscape suggests: ii dia 0.97.3+git20220525-5 pn inkscape-tutorials pn libsvg-perl ii pstoedit 3.78-2 ii python3-packaging 23.0-1 pn python3-uniconvertor ii ruby 1:3.1 -- no debconf information
Bug#1034216: boinc-client: dh_installsystemd doesn't handle files in /usr/lib/systemd/system
On Tue, Apr 11, 2023 at 09:37:27AM +0200, bi...@debian.org wrote: > Package: boinc-client > Version: 7.20.5+dfsg-1 > Severity: serious > Tags: sid bookworm > User: debhel...@packages.debian.org > Usertags: systemd-files-in-usr-bookworm > > Dear Maintainer, > > It seems that your package boinc-client is shipping files (.service, .socket > or > .timer) in /usr/lib/systemd/system. [...] So the package already contains this patch: ./debian/patches/systemd-directory.patch where the (currently) wrong path is used. Simply updating the patch would work, but then would have to be reverted again once it's changed in the future (after bookworm release). A better solution would be to use pkg-config and query systemd.pc for the correct path, eg. pkg-config --variable=systemdsystemunitdir systemd Note: that this needs systemd.pc to be available, thus you'll need to build-depend on the systemd package (as you already list pkg-config in build-deps). Regards, Andreas Henriksson
Bug#1034233: tlp: dh_installsystemd doesn't handle files in /usr/lib/systemd/system
Hi, @Laurent, thank you for highlighting this. @Andreas, the solution you suggested seems nice but ideally I'd rather keep build-dependencies to a minimal (currently there's only debhelper), so I prefer to revert usrmerge related changes introduced in 1.5, even if it means that I'll have to re-introduce them during Trixie's development cycle. Regards, -- Raphaël Halimi
Bug#1034217: qbittorrent-nox: dh_installsystemd doesn't handle files in /usr/lib/systemd/system
On Tue, Apr 11, 2023 at 09:37:27AM +0200, bi...@debian.org wrote:
> Package: qbittorrent-nox
> Version: 4.5.2-1
> Severity: serious
> Tags: sid bookworm
> User: debhel...@packages.debian.org
> Usertags: systemd-files-in-usr-bookworm
>
> Dear Maintainer,
>
> It seems that your package qbittorrent-nox is shipping files (.service,
> .socket or
> .timer) in /usr/lib/systemd/system.
[...]
This package seems to install a template unit (as well as a user unit).
Might be wrong, but as far as I know there's no debhelper code that
automatically enables an instance of a template unit, so maybe this
bug report does not qualify as RC severity.
The CMake build system seems to do things correctly by querying
systemd.pc for the systemdsystemunitdir variable already
(see ./cmake/Modules/FindSystemd.cmake and the use of it in
./dist/unix/CMakeLists.txt )
There's however this in unixconf.pri (which is wrong):
```
# Systemd Service file
nogui:systemd {
systemdService.files = $$DIST_PATH/systemd/qbittorrent-nox@.service
systemdService.path = $$PREFIX/lib/systemd/system
INSTALLS += systemdService
}
```
Regards,
Andreas Henriksson
Bug#1034218: cfengine3: dh_installsystemd doesn't handle files in /usr/lib/systemd/system
On Tue, Apr 11, 2023 at 09:37:27AM +0200, bi...@debian.org wrote: > Package: cfengine3 > Version: 3.21.0-1 > Severity: serious > Tags: sid bookworm > User: debhel...@packages.debian.org > Usertags: systemd-files-in-usr-bookworm > > Dear Maintainer, > > It seems that your package cfengine3 is shipping files (.service, .socket or > .timer) in /usr/lib/systemd/system. [...] So configure.ac contains this: ``` AC_ARG_WITH(systemd-service, AS_HELP_STRING([--with-systemd-service=PATH], [Install systemd service file in given path. The default is no, but if specified, the default path is /usr/lib/systemd/system.]), ``` So it hard-codes a default path, rather than check with systemd.pc. I think that could be fixed to actually use the path from systemd.pc instead. Alternatively you could ofcourse use the existing mechanism and extend the --with-systemd-service you're already passing in debian/rules to actually include the correct path as an argument. eg. ``` SYSTEMDSYSTEMUNITDIR=$(shell pkg-config --variable=systemdsystemunitdir systemd) [...] --with-systemd-service=$(SYSTEMDSYSTEMUNITDIR) \ [...] ``` Note: do not forget to add pkg-config and systemd (for systemd.pc) to build-deps. Regards, Andreas Henriksson
Bug#1034219: debomatic: dh_installsystemd doesn't handle files in /usr/lib/systemd/system
On Tue, Apr 11, 2023 at 09:37:27AM +0200, bi...@debian.org wrote: > Package: debomatic > Version: 0.26-1 > Severity: serious > Tags: sid bookworm > User: debhel...@packages.debian.org > Usertags: systemd-files-in-usr-bookworm > > Dear Maintainer, > > It seems that your package debomatic is shipping files (.service, .socket or > .timer) in /usr/lib/systemd/system. [...] debomatic is the second package using the pybuild build system that I look at which has subdirectories `usr/lib/systemd/system/` containing the service file and then no obvious code to install it so I guess all the magic to handle it is in pybuild or some upstream build system not included in the actual source package itself. I'm not sure exactly what the best option is to adress this for pybuild using packages, but my guess would be to have some debian/rules hack that moves the file (if it's not already located in the same path as returned by `pkg-config --variable=systemdsystemunitdir systemd`) after dh_install has run probably. Regards, Andreas Henriksson
Bug#1034220: shadowsocks-libev: dh_installsystemd doesn't handle files in /usr/lib/systemd/system
On Tue, Apr 11, 2023 at 09:37:27AM +0200, bi...@debian.org wrote: > Package: shadowsocks-libev > Version: 3.3.5+ds-9 > Severity: serious > Tags: sid bookworm > User: debhel...@packages.debian.org > Usertags: systemd-files-in-usr-bookworm > > Dear Maintainer, > > It seems that your package shadowsocks-libev is shipping files (.service, > .socket or > .timer) in /usr/lib/systemd/system. [...] The incorrect path is in: ./debian/shadowsocks-libev.install (also in ./debian/README.Debian ) Changing it to lib/systemd/system and then in trixie back to usr/lib/systemd/system again seems suboptimal. Rather than duplicating the path everywhere, the best thing would be to simply query systemd.pc for it, eg: pkg-config --variable=systemdsystemunitdir systemd This needs pkg-config and systemd to be in build-depends. To use this command in ./debian/shadowsocks-libev.install you would have to make the file executable and integrate dh-exec. I'll leave it up to you to decide if you think integrating dh-exec is worth it or not (Another option is to make the upstream build system install the file in the correct path.) Regards, Andreas Henriksson
Processed: fixed 1034160 in qtbase-opensource-src/5.15.8+dfsg-5 ...
Processing commands for cont...@bugs.debian.org: > fixed 1034160 qtbase-opensource-src/5.15.8+dfsg-5 Bug #1034160 [libqt5gui5] libkscreenlocker5: Screen locker crashes asking for loginctl command Marked as fixed in versions qtbase-opensource-src/5.15.8+dfsg-5. > found 1034160 qtbase-opensource-src/5.15.8+dfsg-6 Bug #1034160 [libqt5gui5] libkscreenlocker5: Screen locker crashes asking for loginctl command Marked as found in versions qtbase-opensource-src/5.15.8+dfsg-6. > thanks Stopping processing here. Please contact me if you need assistance. -- 1034160: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034160 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#981928: marked as done (gauche-gtk FTBFS: unknown define-cclass qualifier(s) (::base))
Your message dated Wed, 12 Apr 2023 06:04:17 + with message-id and subject line Bug#981928: fixed in gauche-gtk 0.6.1-1 has caused the Debian Bug report #981928, regarding gauche-gtk FTBFS: unknown define-cclass qualifier(s) (::base) 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.) -- 981928: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981928 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gauche-gtk Version: 0.6+git20160927-3 Severity: serious Tags: ftbfs bullseye sid https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/gauche-gtk.html ... unknown define-cclass qualifier(s) (::base) make[2]: *** [Makefile:10: gdkdisplay.c] Error 1 --- End Message --- --- Begin Message --- Source: gauche-gtk Source-Version: 0.6.1-1 Done: NIIBE Yutaka We believe that the bug you reported is fixed in the latest version of gauche-gtk, 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 981...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. NIIBE Yutaka (supplier of updated gauche-gtk package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 12 Apr 2023 14:16:04 +0900 Source: gauche-gtk Binary: gauche-gtk gauche-gtk-dbgsym Architecture: source amd64 Version: 0.6.1-1 Distribution: unstable Urgency: medium Maintainer: NIIBE Yutaka Changed-By: NIIBE Yutaka Description: gauche-gtk - Gauche bindings for GTK+ GUI Toolkit Closes: 981928 Changes: gauche-gtk (0.6.1-1) unstable; urgency=medium . * New upstream (Closes: #981928). * debian/patches/07-HUGE.patch: Remove. * debian/docs: Updated. Checksums-Sha1: 4b81041f3b764c066d32bc90cb6d1a9a49e5a5d4 1411 gauche-gtk_0.6.1-1.dsc 55ca015fbe86a45b33b5418b445d25e5aad17f03 204720 gauche-gtk_0.6.1.orig.tar.gz 5dbd8df4636c070f19f2325c2404161725603f0c 7348 gauche-gtk_0.6.1-1.debian.tar.xz c0f8f748ce5d769adf3b232feab08c10f0c025a8 2902424 gauche-gtk-dbgsym_0.6.1-1_amd64.deb d8fac9583a3b399f7fdc3a2cc2b0df346c6ca3a6 12314 gauche-gtk_0.6.1-1_amd64.buildinfo ccf48c047d7eef21d22781e9f37a7015114c3198 843572 gauche-gtk_0.6.1-1_amd64.deb Checksums-Sha256: a128fdf8549121346e97ff04f7281947cb2c85082ed09e88bf9ee595d7b1b74d 1411 gauche-gtk_0.6.1-1.dsc 7df4d5e35429acd6fee7f34ae936fca3e6c698692214ccd01f6bcd052aac5f83 204720 gauche-gtk_0.6.1.orig.tar.gz 32ef34a4730aa8bb6680c88fbb148498be5ce8c9abbd6cc0e925a3d3a3b2adc4 7348 gauche-gtk_0.6.1-1.debian.tar.xz fd51be42b07e6f3b159bb4c789d137bebfdf260f0f909d2b1d15cdd4b7baa938 2902424 gauche-gtk-dbgsym_0.6.1-1_amd64.deb 7bc66abd8ed85e7a01f535c57276de281ecef47305353f0f3b209e6e2039134b 12314 gauche-gtk_0.6.1-1_amd64.buildinfo d943dff3b43e6debd5820cd26a914ff08e6c4864304227ed0156c2e3a7d1b33c 843572 gauche-gtk_0.6.1-1_amd64.deb Files: f5e2dcb497405c411aa46298ffebd82f 1411 lisp optional gauche-gtk_0.6.1-1.dsc 94bff8f7e0e5bb9634a795bb9f5d2727 204720 lisp optional gauche-gtk_0.6.1.orig.tar.gz ead8f22b4f3ac74664cda5ace120a33a 7348 lisp optional gauche-gtk_0.6.1-1.debian.tar.xz 709114ecf83cd09a2e33bb9dd0aec88e 2902424 debug optional gauche-gtk-dbgsym_0.6.1-1_amd64.deb c4a0c6699c8d692d4ab4cd48400ee903 12314 lisp optional gauche-gtk_0.6.1-1_amd64.buildinfo 82bba005f4101d3d92df0f74e33694c2 843572 lisp optional gauche-gtk_0.6.1-1_amd64.deb -BEGIN PGP SIGNATURE- iHUEARYIAB0WIQS3MhxVeHDZjYHXYQFkARSvid5gVAUCZDZFoQAKCRBkARSvid5g VPWJAQC49nuNtJGN4GvbWRBfQmzCc5z5D1y66nD1Q9t0m8tqpQEAmvxxnK8Wxnn7 O9FKI7ZfdOZzFkXb0ICpkcYU9YaOaA4= =DmiO -END PGP SIGNATURE End Message ---
