Bug#1070833: evolution: Failed to load module: /usr/lib/evolution/modules/module-rss.so
Source: evolution Version: 3.52.1-1 Severity: serious Hello, When starting evolution, I see the following messages in the terminal: (process:20505): e-data-server-WARNING **: 09:48:19.447: module_load: libevolution-rss-common.so: cannot open shared object file: No such file or directory Failed to load module: /usr/lib/evolution/modules/module-rss.so (evolution:20505): camel-CRITICAL **: 09:48:19.525: camel_provider_list: Could not load /usr/lib/evolution-data-server/camel-providers/libcamelrss.so: libevolution-rss-common.so: cannot open shared object file: No such file or directory It seems that libcamelrss.so is loading libevolution-rss-common.so but the file is installed in evolution-dev instead of libevolution. Please move that file Kind regards, Laurent Bigonville -- System Information: Debian Release: trixie/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.7.12-amd64 (SMP w/12 CPU threads; PREEMPT) Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), LANGUAGE=fr_BE:fr Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#1061731: fwupd: Failed to load daemon: failed to load engine: Failed to load config: Key file does not have group “redfish”
On Mon, 29 Jan 2024 10:47:50 +0100 Laurent Bigonville wrote: > > Hello, > > It seems that fwupd is not starting anymore on my machine. > > In the logs I can see: > > jan 29 10:40:28 eriador systemd[1]: Starting fwupd.service - Firmware > update daemon... > jan 29 10:40:28 eriador fwupd[13042]: Failed to load daemon: failed to > load engine: Failed to load config: Key file does not have group “redfish” > jan 29 10:40:28 eriador systemd[1]: fwupd.service: Main process exited, > code=exited, status=1/FAILURE > jan 29 10:40:28 eriador systemd[1]: fwupd.service: Failed with result > 'exit-code'. > jan 29 10:40:28 eriador systemd[1]: Failed to start fwupd.service - > Firmware update daemon. > I've no idea what happened, but the configuration file was changed (I didn't do these changes): $ sudo diff -u fwupd/fwupd.conf /etc/fwupd/fwupd.conf --- fwupd/fwupd.conf 2024-01-24 10:15:36.0 +0100 +++ /etc/fwupd/fwupd.conf 2023-07-13 11:36:11.244229063 +0200 @@ -1,5 +1,20 @@ -# use `man 5 fwupd.conf` for documentation [fwupd] DisabledPlugins=test;test_ble OnlyTrusted=true AllowEmulation=false +DisabledPlugins=test;test_ble +IgnorePower=false +OnlyTrusted=true +AllowEmulation=false + +[msr] +MinimumSmeKernelVersion=5.18.0 + +[redfish] + +[thunderbolt] +MinimumKernelVersion=4.13.0 +DelayedActivation=false +RetimerOfflineMode=false + +[uefi_capsule]
Bug#1061776: fail2ban: Wrong journalmatch for sshd jail
Package: fail2ban Version: 1.0.2-2 Severity: serious Tags: sid trixie bookworm Hello, The default journalmatch for ssh the following: filter.d/sshd.conf: journalmatch = _SYSTEMD_UNIT=sshd.service + _COMM=sshd But the .service file for ssh in debian is called ssh.service, not sshd.service If I run journalctl _SYSTEMD_UNIT=sshd.service _COMM=sshd, I get no entries. If I run journalctl _SYSTEMD_UNIT=ssh.service _COMM=sshd , I get the logs I think there are still something broken with the switch to journald The configuration should be changed to: "_SYSTEMD_UNIT=ssh.service _COMM=sshd" IMVHO Kind regards, Laurent Bigonville
Bug#1061731: fwupd: Failed to load daemon: failed to load engine: Failed to load config: Key file does not have group “redfish”
Package: fwupd Version: 1.9.12-1 Severity: serious Hello, It seems that fwupd is not starting anymore on my machine. In the logs I can see: jan 29 10:40:28 eriador systemd[1]: Starting fwupd.service - Firmware update daemon... jan 29 10:40:28 eriador fwupd[13042]: Failed to load daemon: failed to load engine: Failed to load config: Key file does not have group “redfish” jan 29 10:40:28 eriador systemd[1]: fwupd.service: Main process exited, code=exited, status=1/FAILURE jan 29 10:40:28 eriador systemd[1]: fwupd.service: Failed with result 'exit-code'. jan 29 10:40:28 eriador systemd[1]: Failed to start fwupd.service - Firmware update daemon. Kind regards, Laurent Bigonville
Bug#1059922: nut-server: upsd fails to start since version 2.8.1
severity 1059922 important thanks > Dear Laurent Bigonville, Hello Jörg, > with version 2.8.0-7 an EATON UPS connected to a debian computer via > USB was working in standalone mode as expected. The only change in the > config files was in /etc/nut/ups.conf where I added the following lines: > > [Eaton] > driver = usbhid-ups > port = auto > vendorid = 0463 > pollfreq = 30 > > After the upgrade to version 2.8.1-1 the upsd daemon would fail to > start. The output in /var/log/syslog is > > upsd[12132]: not listening on ::1 port 3493 > upsd[12132]: listening on 127.0.0.1 port 3493 > upsd[12132]: no listening interface available > > instead of > > upsd[12553]: listening on 127.0.0.1 port 3493 > upsd[12553]: not listening on ::1 port 3493 > upsd[12553]: Connected to UPS [Eaton]: usbhid-ups-Eaton > upsd[12555]: Startup successful > > for the working version 2.8.0. > Any ideas? Could you please attach the other configuration files here (please check for clear-text passwords)? Do you have the loopback (127.0.0.1/::1) interface properly working? I cannot reproduce this at home where I have also an EATON UPS Kind regards, Laurent Bigonville
Bug#1037478: ca-certificates-java: Loop in the execution of the trigger
Package: ca-certificates-java Version: 20230103 Severity: serious Hello, While updating today, I got the following error: dpkg: boucle détectée durant le traitement des actions différées : listes des paquets qui en sont responsables (normalement) : ca-certificates-java -> ca-certificates-java paquets bloqués par le traitement impossible d'actions différées requises : ca-certificates-java: update-ca-certificates-java: /usr/lib/jvm libc-bin: ldconfig dictionaries-common: aspell-autobuildhash There seems to be a loop in the trigger execution Kind regards Laurent Bigonville -- System Information: Debian Release: trixie/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-9-amd64 (SMP w/8 CPU threads; PREEMPT) Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), LANGUAGE=fr_BE:fr Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: SELinux: enabled - Mode: Permissive - Policy name: refpolicy Versions of packages ca-certificates-java depends on: ii ca-certificates 20230311 ii openjdk-11-jre-headless [java8-runtime-headless] 11.0.19+7-1 ca-certificates-java recommends no packages. ca-certificates-java suggests no packages. -- Configuration Files: /etc/default/cacerts [Errno 13] Permission non accordée: '/etc/default/cacerts' -- no debconf information
Bug#1031152: system-config-printer: unlock button in system-config-printer provides no elevated permissions dialog
On Sun, 12 Feb 2023 09:06:02 -0500 Alexis wrote: [...] > > > * What was the outcome of this action? > > The following error was thrown: > > Gtk-WARNING **: 08:47:30.475: Error acquiring permission: Failed to acquire permission for action-id org.opensuse.cupspkhelper.mechanism.all-edit Do you have the cups-pk-helper package installed? system-config-printer-common already recommends that package. The definition of Recommends is: "This declares a strong, but not absolute, dependency. The Recommends field should list packages that would be found together with this one in all but unusual installations.", so you should probably also install recommended packages. Kind regards, Laurent Bigonville
Bug#1034223: powerman: dh_installsystemd doesn't handle files in /usr/lib/systemd/system
severity 1034223 important thanks On Tue, 11 Apr 2023 16:42:32 +0200 Andreas Henriksson wrote: > Hello Laurent Bigonville, > > On Tue, Apr 11, 2023 at 09:37:27AM +0200, bi...@debian.org wrote: > > Package: powerman > > Version: 2.3.27-2 > > Severity: serious > > Tags: sid bookworm > > User: debhel...@packages.debian.org > > Usertags: systemd-files-in-usr-bookworm > > > > Dear Maintainer, > > > > It seems that your package powerman 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. > [...] > > Note that debian/rules has: > > ``` > override_dh_installinit: > dh_installinit --no-start --no-enable > > override_dh_installsystemd: > dh_installsystemd --no-start --no-enable > ``` > > So do you agree that the severity of this bug report should be downgraded > (maybe even closed)? I think severity can be downgraded (to "important"?), this is still a problem as systemctl daemon-reload is not called, but at least there will be surprise after a reboot.
Bug#1034055: fwknop-apparmor-profile: AppArmor profile installed in systemd system service path
Le 7/04/23 à 20:19, Francois Marier a écrit : On 2023-04-07 at 07:23:07, Laurent Bigonville (bi...@debian.org) wrote: It seems that you install the apparmor profile in the path for systemd system service The following change should be reverted: https://salsa.debian.org/debian/fwknop/-/commit/d3a5aaef39fedc1bb94e26921afbf63f79b31af7 Hm, that does look like a mistake. I don't remember what might have caused me to make that change. I guess the apparmor profile hasn't been in use for a while then. It seems like it's too late in the release process to re-add it in bookworm. Here's what I'm thinking of doing: - move it to /usr/share/apparmor/extra-profiles/ (so it's not turned on by default) for bookworm - move it back to /etc/apparmor.d/ after bookworm Alternatively, I could also not change anything for bookworm since it's not enabled as an AppArmor profile and it will be ignored as a systemd unit file. What do you think? Sorry for the late answer. I see that you moved the file to /usr/share/apparmor/extra-profiles/, for now it's OK I guess, might be indeed be too late to enable the profile so late in the development cycle An other option for bookworm+1 is to move the file back to /etc/apparmor.d/ AND merge the profile back in the main package so it's installed along side the daemon and kill fwknop-apparmor-profile (that package only ships one file AFAICS) Apparmor profile can be put in complain/non-enforcing mode if the user really wants to.
Bug#1034234: libpam-modules-bin: dh_installsystemd doesn't handle files in /usr/lib/systemd/system
Le 11/04/23 à 19:53, Sam Hartman a écrit : control: tags -1 wontfix "bigon" == bigon writes: bigon> It seems that your package libpam-modules-bin is shipping bigon> files (.service, .socket or .timer) in bigon> /usr/lib/systemd/system. I think we're talking about pam_namespace.service. I don't think dh_installsystemd has anything to do for that file because it has no Install section. What harm is caused by pam_namespace.service being in /usr/lib/systemd? dh_installsystemd also takes care of calling systemctl daemon-reload when a new .service file is installed/removed, it also takes care that the service is stopped before removing the package (in this case it's a short living/oneshot service, but still) bigon> debhelper? As soon as debhelper is supporting (not until bigon> bookworm+1 aka Trixie) you will be able to move them back to bigon> the newer location. Um, no doing that before dpkg is fixed to deal with aliasing could potentially be a really bad idea. I'm not sure I understand, if all the files are at package level moved to /usr instead of / then aliasing in dpkg is not needed, isn't it? Again, what harm is caused by pam_namespace.service being in /usr/lib/systemd/system? How is this a bug?
Bug#1034055: fwknop-apparmor-profile: AppArmor profile installed in systemd system service path
Package: fwknop-apparmor-profile Version: 2.6.10-13 Severity: serious Hello It seems that you install the apparmor profile in the path for systemd system service The following change should be reverted: https://salsa.debian.org/debian/fwknop/-/commit/d3a5aaef39fedc1bb94e26921afbf63f79b31af7 Kind regards, Laurent Bigonville -- System Information: Debian Release: 12.0 APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-7-amd64 (SMP w/12 CPU threads; PREEMPT) Kernel taint flags: TAINT_WARN Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), LANGUAGE=fr_BE:fr Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages fwknop-apparmor-profile depends on: pn fwknop-server fwknop-apparmor-profile recommends no packages. fwknop-apparmor-profile suggests no packages.
Bug#1033045: librest-dev: Missing dependencies
Package: librest-dev Version: 0.9.1-4 Severity: serious Hello, It seems that librest-dev and librest-extras-dev are missing dependencies that are declared in the .pc files, like libjson-gib-dev and others. That should probably be fixed Kind regards, Laurent Bigonville -- System Information: Debian Release: 12.0 APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-6-amd64 (SMP w/8 CPU threads; PREEMPT) Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), LANGUAGE=fr_BE:fr Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: SELinux: enabled - Mode: Permissive - Policy name: refpolicy Versions of packages librest-dev depends on: ii gir1.2-rest-1.0 0.9.1-4 ii librest-1.0-00.9.1-4 pn libsoup-3.0-dev ii libxml2-dev 2.9.14+dfsg-1.1+b3 librest-dev recommends no packages. librest-dev suggests no packages.
Bug#1032183: libgusb-dev: missing dependency on libjson-glib-1.0-dev
On Wed, 1 Mar 2023 11:06:21 + Simon McVittie wrote: > Control: tags -1 + patch > > On Wed, 01 Mar 2023 at 10:52:44 +, Simon McVittie wrote: > > I'll send the obvious patch when I have a bug number. > > Attached, or available from > https://salsa.debian.org/efi-team/libgusb/-/merge_requests/6 Hello, Independently of whether the package should migrate to testing/bookworm now, could this bug be fixed? I think the necessary patches are in git, is it possible to upload? Kind regards, Laurent Bigonville
Bug#1032510: packagekit: pkcon what-provides application/x-keepass2 makes PK crash
Package: packagekit Version: 1.2.6-3 Severity: serious Hello, pkcon what-provides application/x-keepass2 makes PK crash: $ pkcon what-provides application/x-keepass2 Getting provides[=] Loading cache [=] Querying[=] e daemon crashed mid-transaction! Finished[ ] (0%) Stack trace of thread 10447: #0 0x7faf3ef75ccc __pthread_kill_implementation (libc.so.6 + 0x8accc) #1 0x7faf3ef26ef2 __GI_raise (libc.so.6 + 0x3bef2) #2 0x7faf3ef11472 __GI_abort (libc.so.6 + 0x26472) #3 0x7faf3c89d919 _ZN9__gnu_cxx27__verbose_terminate_handlerEv (libstdc++.so.6 + 0x9d919) #4 0x7faf3c8a8e1a _ZN10__cxxabiv111__terminateEPFvvE (libstdc++.so.6 + 0xa8e1a) #5 0x7faf3c8a8e85 _ZSt9terminatev (libstdc++.so.6 + 0xa8e85) #6 0x7faf3c8a90d8 __cxa_throw (libstdc++.so.6 + 0xa90d8) #7 0x7faf3c8a00e4 _ZSt19__throw_logic_errorPKc (libstdc++.so.6 + 0xa00e4) #8 0x7faf3e96cb3a _ZNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEC4IS3_EEPKcRKS3_ (libpk_backend_apt.so + 0x2cb3a) #9 0x7faf3e95d122 backend_what_provides_thread (libpk_backend_apt.so + 0x1d122) #10 0x5644cb0c7aca pk_backend_job_thread_setup (packagekitd + 0x23aca) #11 0x7faf3f5dbcfd g_thread_proxy (libglib-2.0.so.0 + 0x7ecfd) #12 0x7faf3ef73fd4 start_thread (libc.so.6 + 0x88fd4) #13 0x7faf3eff466c __clone3 (libc.so.6 + 0x10966c) This breaks GNOME ability to suggest which application to install when opening files. Feel free to downgrade the severity if you want. Kind regards, Laurent Bigonville -- System Information: Debian Release: 12.0 APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-6-amd64 (SMP w/12 CPU threads; PREEMPT) Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), LANGUAGE=fr_BE:fr Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages packagekit depends on: ii init-system-helpers 1.65.2 ii libappstream4 0.16.1-1 ii libapt-pkg6.0 2.6.0 ii libc6 2.36-8 ii libgcc-s1 12.2.0-14 ii libglib2.0-02.74.6-1 ii libglib2.0-bin 2.74.6-1 ii libgstreamer1.0-0 1.22.0-2 ii libpackagekit-glib2-18 1.2.6-3 ii libpolkit-gobject-1-0 122-3 ii libsqlite3-03.40.1-1 ii libstdc++6 12.2.0-14 ii libsystemd0 252.6-1 ii polkitd 122-3 Versions of packages packagekit recommends: ii packagekit-tools 1.2.6-3 ii systemd 252.6-1 Versions of packages packagekit suggests: ii appstream 0.16.1-1 -- no debconf information
Bug#1028301: grub: grub-probe doesn't detect that file is on cryptfs on new installation
Package: grub-common Version: 2.06-7 Severity: serious File: /usr/sbin/grub-probe Hello, On a newly installed laptop, it seems that grub-probe is not able to detect that files are on an encrypted FS. New laptop: $ sudo grub-probe -t abstraction /usr/share/images/desktop-base/desktop-grub.png lvm $ sudo lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS nvme0n1 259:00 476,9G 0 disk ├─nvme0n1p1 259:10 512M 0 part /boot/efi ├─nvme0n1p2 259:20 488M 0 part /boot └─nvme0n1p3 259:30 476G 0 part └─nvme0n1p3_crypt 254:00 475,9G 0 crypt ├─new_laptop--vg-root254:10 27,9G 0 lvm / ├─new_laptop--vg-swap_1 254:20 976M 0 lvm [SWAP] ├─new_laptop--vg-home254:3040G 0 lvm /home └─new_laptop--vg-libvirt 254:4060G 0 lvm /var/lib/libvirt Old laptop: $ sudo grub-probe -t abstraction /usr/share/images/desktop-base/desktop-grub.png cryptodisk luks gcry_rijndael gcry_rijndael gcry_sha256 lvm $ sudo lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS sda8:01 0B 0 disk nvme0n1 259:00 476,9G 0 disk ├─nvme0n1p1 259:10 512M 0 part /boot/efi ├─nvme0n1p2 259:20 244M 0 part /boot └─nvme0n1p3 259:30 476,2G 0 part └─nvme0n1p3_crypt 254:00 476,2G 0 crypt ├─old_laptop--vg-root254:10 27,9G 0 lvm / ├─old_laptop--vg-swap_1 254:20 31,7G 0 lvm [SWAP] ├─old_laptop--vg-home254:30 120G 0 lvm /home ├─old_laptop--vg-sid_amd64_sbuild254:40 5G 0 lvm ├─old_laptop--vg-flatpak 254:5050G 0 lvm /var/lib/flatpak ├─old_laptop--vg-libvirt 254:6075G 0 lvm /var/lib/libvirt ├─old_laptop--vg-docker 254:7010G 0 lvm /var/lib/docker ├─old_laptop--vg-acng254:8010G 0 lvm /var/cache/apt-cacher-ng └─old_laptop--vg-buster_amd64_sbuild 254:90 5G 0 lvm Setting this as serious as this seems to be a regression, this at least breaks grub ability to display the theme wallpaper. Kind regards, Laurent Bigonville
Bug#968997: fwupdmgr: "Successfully" updates BIOS firmware, no effect on reboot
On Mon, 3 Oct 2022 21:48:42 +0100 Steve McIntyre wrote: > On Mon, Oct 03, 2022 at 09:22:02PM +0200, Vincent Bernat wrote: > > > >shim-unsigned has been updated to 15.6 which has the right patches in. But > >for some reason, shim-signed is still at 15.4. > > We've had problems in submitting shim 15.6 to Microsoft for > signing. We're working on a solution, but it's going to take a little > longer yet. Hello Steven, Sorry to insist (again), but do you have any news about this? We are slowly approaching the freeze for bookworm and having a fix for this looks quite important to me. Kind regards, Laurent Bigonville
Bug#1023530: nut: flaky autopkgtest: varying failures
On Sun, 6 Nov 2022 07:30:38 +0100 Paul Gevers wrote: > Dear maintainer(s), Hello Paul > I looked at the results of the autopkgtest of your package. I noticed > that it regularly fails (after the fix for bug #1019221). > > Because the unstable-to-testing migration software now blocks on > regressions in testing, flaky tests, i.e. tests that flip between > passing and failing without changes to the list of installed packages, > are causing people unrelated to your package to spend time on these > tests. > > Don't hesitate to reach out if you need help and some more information > from our infrastructure. It's impossible for me to reproduce this locally, can you still see that in the CI runs? For me this looks like a race condition, the test code already waits for 2 sec after the start of the nut daemon an drivers to be certain that everything is properly started. I can increase that sleep, but that's probably not the best solution. An other solution is to have a loop checking that the (dummy) driver is really connected, but I need to investigate how and I've no time ATM. Last solution could be to ask the release team to tag this bug as "bookworm-ignore" so it can be part of the upcoming release and try to fix this for the next one. WDYT? Kind regards, Laurent Bigonville
Bug#1011726: switcheroo-control: FTBFS: AssertionError: 0 != 1
severity 1011726 important thanks On Thu, 26 May 2022 08:13:24 +0200 Lucas Nussbaum wrote: > > Hi, > > During a rebuild of all packages in sid, your package failed to build > on amd64. Hello, I cannot reproduce this on my laptop, not sure what happened I'll reduce the severity to important so the package is not removed from unstable for now Kind regards, Laurent Bigonville
Bug#976686: marked as pending in glom
Control: tag -1 pending Hello, Bug #976686 in glom 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/gnome-team/glom/-/commit/b17344b757762493cd8cf22e99a1383f54afefd7 debian/rules: Enforce that that boost_python library uses default python version Closes: #976686, #956709 (this message was generated automatically) -- Greetings https://bugs.debian.org/976686
Bug#1009175: python3-samba package trying to replace file owned by samba one (dckeytab)
Package: python3-samba Version: 2:4.16.0+dfsg-2 Severity: serious Hello, When updating my system this morning, I got the following error: Préparation du dépaquetage de .../03-python3-samba_2%3a4.16.0+dfsg-2_amd64.deb ... Dépaquetage de python3-samba (2:4.16.0+dfsg-2) sur (2:4.13.14+dfsg-1+b3) ... dpkg: erreur de traitement de l'archive /tmp/apt-dpkg-install-pB0IcL/03-python3-samba_2%3a4.16.0+dfsg-2_amd64.deb (--unpack) : tentative de remplacement de « /usr/lib/python3/dist-packages/samba/dckeytab.cpython-310-x86_64-linux-gnu.so », qui appartient aussi au paquet samba 2:4.13.14+dfsg-1+b3 dpkg-deb: erreur: coller subprocess was killed by signal (Relais brisé (pipe)) Apparently the dckeytab.cpython-310-x86_64-linux-gnu.so file moved from the samba package to the python3-samba without the proper Breaks/Replaces -- System Information: Debian Release: bookworm/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.16.0-6-amd64 (SMP w/8 CPU threads; PREEMPT) Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), LANGUAGE=fr_BE:fr Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: SELinux: enabled - Mode: Permissive - Policy name: refpolicy Versions of packages python3-samba depends on: ii libbsd0 0.11.6-1 ii libc6 2.33-7 ii libgnutls30 3.7.3-4+b1 ii libldb2 2:2.5.0+smb-2+samba4.16.0+dfsg ii libpython3.10 3.10.4-3 ii libtalloc2 2.3.3-3+b1 ii libtevent0 0.11.0-1 ii libwbclient02:4.16.0+dfsg-2 ii python3 3.10.4-1 ii python3-ldb 2:2.5.0+smb-2+samba4.16.0+dfsg ii python3-talloc 2.3.3-3+b1 ii python3-tdb 1.4.6-2+b1 ii samba-libs 2:4.16.0+dfsg-2 Versions of packages python3-samba recommends: ii python3-gpg 1.16.0-1.2 python3-samba suggests no packages. -- no debconf information
Bug#1006127: wireless-regdb stable policy
FTR, this seems to be fixed in the last release (2022-02-18) of wireless-regdb: https://git.kernel.org/pub/scm/linux/kernel/git/sforshee/wireless-regdb.git/commit/?id=e427ff2a592e26fc1e8336769b9a1ad223f6f697
Bug#1005594: rygel: FTBFS: ../meson.build:99:0: ERROR: Could not generate cargs for gst-editing-services-1.0:
reassign 1005594 libges-1.0-dev 1.20.0-1 affects 1005594 src:rygel thanks On Sun, 13 Feb 2022 08:31:17 +0100 Lucas Nussbaum wrote: > Hi, > > During a rebuild of all packages in sid, your package failed to build > on amd64. > [...] > > Package 'python-3.9-embed', required by 'gst-editing-services-1.0', not found This is an issue with gstreamer-editing-services1.0 libges-1.0-dev package should depends against libpython3-dev (or libpython3.X-dev) as the .pc file requires it I'm not sure how to automatically calculate that we need libpython3.9-dev vs libpython3.10-dev for example
Bug#1005113: fwupd: Please tighten the version of libfwupd2
Package: fwupd Version: 1.5.7-5 Severity: serious Hello, fwupd package should tighten the version of the libfwupd2 dependency (and probably libfwupdplugin as well) Mixing fwupd version 1.5.7-5 and libfwupd2 version 1.7.4-1 makes fwupd crash Kind regards, Laurent Bigonville -- System Information: Debian Release: bookworm/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.15.0-3-amd64 (SMP w/8 CPU threads) Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), LANGUAGE=fr_BE:fr Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: SELinux: enabled - Mode: Permissive - Policy name: refpolicy Versions of packages fwupd depends on: ii libc6 2.33-5 ii libcurl3-gnutls7.81.0-1 ii libefiboot137-6 ii libelf10.186-1 ii libflashrom1 1.2-5 ii libfwupd2 1.5.7-5 ii libfwupdplugin11.5.7-5 ii libglib2.0-0 2.70.3-1 ii libgnutls303.7.3-4+b1 ii libgudev-1.0-0 237-2 ii libgusb2 0.3.8-1 ii libjcat1 0.1.9-1 ii libjson-glib-1.0-0 1.6.6-1 ii libpolkit-gobject-1-0 0.105-31.1+b1 ii libsmbios-c2 2.4.3-1 ii libsqlite3-0 3.37.2-2 ii libsystemd0250.3-2 ii libtss2-esys-3.0.2-0 3.1.0-3 ii libxmlb2 0.3.6-2 ii shared-mime-info 2.1-2 Versions of packages fwupd recommends: ii bolt 0.9.1-2 ii dbus 1.12.20-3 ii fwupd-amd64-signed [fwupd-signed] 1.5.7+5 ii python33.9.8-1 pn secureboot-db ii udisks22.9.4-1 Versions of packages fwupd suggests: pn gir1.2-fwupd-2.0 -- Configuration Files: /etc/dbus-1/system.d/org.freedesktop.fwupd.conf [Errno 2] Aucun fichier ou dossier de ce type: '/etc/dbus-1/system.d/org.freedesktop.fwupd.conf' /etc/fwupd/remotes.d/fwupd.conf [Errno 2] Aucun fichier ou dossier de ce type: '/etc/fwupd/remotes.d/fwupd.conf' -- no debconf information
Bug#1002065: scipy build-depenencies unsatisfiable in testing/unstable
On 9/01/22 00:43, Drew Parsons wrote: On 2022-01-08 19:44, Laurent Bigonville wrote: On Tue, 21 Dec 2021 11:09:02 + Peter Michael Green wrote: scipy build-depends on python3-pybind11 (<< 2.8) but testing and unstable have version 2.8.1-3 FTR, the package builds fine with python3-pybind11 2.9 Could you drop that restriction or is it really broken with higher versions? They're conservative with their official releases. From scipy/pyproject.toml: "This to prevent that a future backwards-incompatible release will break the source build of a SciPy release.". It's more relevant for local user pip builds in a virtualenv, keeping the virtualenv constrained to known-good package versions. It's not so crucial for Debian since we maintain our own package self-consistency. In fact the upper bound is only applied upstream to the release versions. The development version has no upper bound (still set at "pybind11>=2.4.3") So it should be safe to remove the upper bound for us. It's a pity apt-rdepends doesn't support reverse build-dependencies yet, it would make it simpler to keep track of these things when testing new releases. Thanks for your answer. Do you want me to upload the change? Or would you have time to do it? Kind regards, Laurent Bigonville
Bug#1002065: scipy build-depenencies unsatisfiable in testing/unstable
On Tue, 21 Dec 2021 11:09:02 + Peter Michael Green wrote: > scipy build-depends on python3-pybind11 (<< 2.8) but testing and unstable > have version 2.8.1-3 FTR, the package builds fine with python3-pybind11 2.9 Could you drop that restriction or is it really broken with higher versions? Kind regards, Laurent Bigonville
Bug#1002986: libguestfs-tools: Depends on guestfs-tools that is not in the archive
Package: libguestfs-tools Version: 1:1.46.2-1 Severity: serious Hello, It looks like libguestfs-tools version 1:1.46.2-1 in depending on guestfs-tools that is not in the archive making the package uninstalable guestfs-tools is currently stuck in the new queue Kind regards, Laurent Bigonville -- System Information: Debian Release: bookworm/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.15.0-2-amd64 (SMP w/4 CPU threads) Kernel taint flags: TAINT_FIRMWARE_WORKAROUND Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: SELinux: enabled - Mode: Permissive - Policy name: refpolicy
Bug#997253: closing 997253
close 997253 thanks I cannot reproduce the FTBFS with that exact error 15.0+dfsg1-3 that I just uploaded also builds fine on the buildd I'm closing this bug
Bug#996335: marked as pending in pulseaudio
Control: tag -1 pending Hello, Bug #996335 in pulseaudio 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/pulseaudio-team/pulseaudio/-/commit/b1706f98d107aabc3f5ce372fe316f826e75a72f debian/rules: Explicitly disable building doxygen documentation Closes: #996335 (this message was generated automatically) -- Greetings https://bugs.debian.org/996335
Bug#998592: marked as pending in glade
Control: tag -1 pending Hello, Bug #998592 in glade 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/gnome-team/glade/-/commit/ad41ae30dc04d5de170775ff7ecd6294defcb6fe debian/libgladeui-2-13.symbols: Remove symbols previously exported by the plugins Also symplify the debian/rules file. Not too sure why they are not exported anymore though Closes: #998592 Gbp-Dch: Full (this message was generated automatically) -- Greetings https://bugs.debian.org/998592
Bug#999904: Uncoordinated split of debugedit package out of src:rpm
Source: debugedit,rpm Severity: serious Tags: sid bookworm Hello, debugedit has been split out of the src:rpm package, but src:rpm is still building the package as well. In addition to that, rpm package has a strong versioned dependency against debugedit (debugedit (= 4.16.1.2+dfsg1-3)) which means that rpm cannot be installed anymore. We need to keep this package out of testing until this is resolved Kind regards, Laurent Bigonville -- System Information: Debian Release: bookworm/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.14.0-4-amd64 (SMP w/8 CPU threads) Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), LANGUAGE=fr_BE:fr Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: SELinux: enabled - Mode: Permissive - Policy name: refpolicy
Bug#998091: libclc: Keep out of bookworm
Source: libclc Version: 0.2.0+git20190827-8 Severity: serious Hello, libclc should be kept out of bookworm as packages built from llvm now offer the same files The package should more than probably be removed from the archive, but I let you open a RM bug (or reassign this one) Kind regards, Laurent Bigonville -- System Information: Debian Release: bookworm/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.14.0-3-amd64 (SMP w/8 CPU threads) Kernel taint flags: TAINT_FIRMWARE_WORKAROUND Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: SELinux: enabled - Mode: Permissive - Policy name: refpolicy
Bug#993011: pulseaudio-module-bluetooth: no longer detects bluetooth headphones
Hello, On Thu, 26 Aug 2021 12:08:03 +0200 Vincent Lefevre wrote: > > After the upgrade to 15.0+dfsg1-2, pulseaudio no longer detects > my bluetooth headphones when I switch them on. As apparently there is a workaround and/or the problem is coming from bluez, do you think we should keep this bug RC and prevent the migration to unstable? Kind regards, Laurent Bigonville
Bug#996113: libmodulemd: Please move Modulemd.py GObject introspection override to gir1.2-modulemd-2.0
Source: libmodulemd Version: 2.12.0-1 Severity: serious Hello, Without knowing all in and odds of libmodulemd, GObject introspection override files are runtime files, not development files. That means that the file must be moved to the gir1.2-modulemd-2.0 package (and the python3 dependency removed from the -dev package). GObject introspection can be used in multiple language, not only python, meaning that I'm not sure having an explicit dependency on python is actually a good idea here. But the little problem is that the override file uses the "six" module, and I'm not sure we can make the gir1.2-modulemd-2.0 package depends on that either. That means that the responsability of depending on python3 and python3-six should originate from the package using the binding (and ofcourse python) I'm making this RC as I think that without the override file, the binding is not working properly Kind regards, Laurent Bigonville -- System Information: Debian Release: bookworm/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.14.0-1-amd64 (SMP w/8 CPU threads) Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), LANGUAGE=fr_BE:fr Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: SELinux: enabled - Mode: Permissive - Policy name: refpolicy
Bug#994595: libuser1-dev: Missing dependencies against libglib2.0-dev
Package: libuser1-dev Version: 1:0.62~dfsg-0.4 Severity: serious Tags: bullseye bookworm sid Hello, Looking at the libuser.pc file, it seems that the libuser1-dev is missing a dependency against libglib2.0-dev Could you please add it? Kind regards, Laurent Bigonville -- System Information: Debian Release: bookworm/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-8-amd64 (SMP w/8 CPU threads) Kernel taint flags: TAINT_WARN Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), LANGUAGE=fr_BE:fr Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: SELinux: enabled - Mode: Permissive - Policy name: refpolicy
Bug#993491: grilo-plugins: Please switch to tracker 3
Source: grilo-plugins Version: 0.3.13-2 Severity: serious Tags: patch Hello, The transition to tracker 3 has begun, and grilo-plugins requires changes to the build-dependencies to use that new version There is already a MR proposed here: https://salsa.debian.org/berto/grilo-plugins/-/merge_requests/2 Could you please apply that change? Kind regards, Laurent Bigonville -- System Information: Debian Release: bookworm/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-8-amd64 (SMP w/8 CPU threads) Kernel taint flags: TAINT_WARN Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), LANGUAGE=fr_BE:fr Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: SELinux: enabled - Mode: Permissive - Policy name: refpolicy
Bug#989875: closing 989875
close 989875 14.99.1+dfsg1-3 thanks Fixed in 14.99.1+dfsg1-3 https://salsa.debian.org/pulseaudio-team/pulseaudio/-/commit/1dc98e0d034a85f2f959c6c061c0ab5e2ac4e5c4
Bug#988440: Keep out of bookwork
Source: golang-github-seccomp-containers-golang Version: 0.3.2-1 Severity: serious Tags: bookworm sid Hello, golang-github-seccomp-containers-golang is now deprecated upstream and has been replaced by containers-common This package should be removed of the archive when the rdeps updated to not depends against this package. Better to keep this outside of bookworm in any cases Kind regards, Laurent Bigonville -- System Information: Debian Release: 11.0 APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-6-amd64 (SMP w/4 CPU threads) Kernel taint flags: TAINT_FIRMWARE_WORKAROUND Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: SELinux: enabled - Mode: Permissive - Policy name: refpolicy
Bug#987207: podman not running out-of-the-box as root
Hello,
So the problem here is, again, linked to the fact that I'm using a test
SELinux policy that doesn't contain all the needed contexts, so yeah
it's a mix of configuration issue and the fact that podman is not
ignoring these errors if SELinux is in permissive. I'll ping upstream again.
So the remaining problem here is iptables command not being installed
(and the seccomp.json file missing to a lower extend)
Le 21/04/21 à 10:21, Laurent Bigonville a écrit :
Hello,
I just did a minimal test VM and... it indeed works...
I'll investigate why on my machine it's not working.
But, on the test VM, podman still fails because "iptables" is not
installed, only "nft" is intalled by default now. So there is still a
problem here.
Le 21/04/21 à 05:02, Reinhard Tartler a écrit :
Control: tag -1 moreinfo
Hi Laurent,
I've downloaded the Bullseye Alpha 3 debian installer and installed
using kvm to have a super clean new system. Unfortunately, I was
unable to reproduce the issue that you described below. (I did find
some issues with rootless podman outside of a gnome-session, but
that's a different story).
The symptoms sound a lot like described in this upstream bug:
https://github.com/containers/podman/issues/5721
<https://github.com/containers/podman/issues/5721>
Can you please compare your notes with that upstream bug? Can you
confirm that the 'overlay' kernel module is loaded? (in my test, it
was loaded automatically). If you still think this is an issue in the
Debian package, please let me know. I may require your assistance
with reproducing this issue.
-rt
On Mon, Apr 19, 2021 at 11:54 AM Laurent Bigonville <mailto:bi...@debian.org>> wrote:
Package: podman
Version: 3.0.1+dfsg1-1
Severity: serious
Hello,
After installing podman, I cannot run it as root out of the box as it
fails with:
ERRO[] [graphdriver] prior storage driver overlay failed:
kernel does not support overlay fs: 'overlay' is not supported
over extfs at "/var/lib/containers/storage/overlay": backing file
system is unsupported for this graph driver
Error: kernel does not support overlay fs: 'overlay' is not
supported over extfs at "/var/lib/containers/storage/overlay":
backing file system is unsupported for this graph driver
Looking at fedora it seems that they have a containers-common package
that ships a default storage.conf file:
https://src.fedoraproject.org/rpms/containers-common/blob/rawhide/f/storage.conf
<https://src.fedoraproject.org/rpms/containers-common/blob/rawhide/f/storage.conf>
I see that the debian package is shipping a file in
/usr/share/containers/storage.conf (in the containers-storage
package),
but that file is apparently not read (strace only shows that the
file in
/etc/containers is read) and anyway unlike in fedora:
1) the driver is not set to overlay
2) the file is installed only if the containers-storage package is
installed, which is not done by default.
3) that file is not read anyway, strace only shows that
/etc/containers/storage.conf is read and not
/usr/share/containers/storage.conf, so the file is apparently useless
Shouldn't debian do the same thing than fedora so everything
works OOTB?
As a side note, I can see they are shipping also other files as well,
like the seccomp.json file, using strace, it seems that podman
tries to
read them:
[pid 14835] newfstatat(AT_FDCWD, "/etc/containers/seccomp.json",
0xcee6b8, 0) = -1 ENOENT (Aucun fichier ou dossier de ce type)
[pid 14835] newfstatat(AT_FDCWD,
"/usr/share/containers/seccomp.json", 0xcee788, 0) = -1
ENOENT (Aucun fichier ou dossier de ce type)
Shouldn't that file be shipped by default too?
Kind regards,
Laurent Bigonville
-- System Information:
Debian Release: 11.0
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1,
'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 5.10.0-6-amd64 (SMP w/8 CPU threads)
Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8),
LANGUAGE=fr_BE:fr
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: SELinux: enabled - Mode: Permissive - Policy name: refpolicy
Versions of packages podman depends on:
ii conmon 2.0.25+ds1-1
ii containernetworking-plugins 0.9.0-1+b3
ii golang-github-containers-common 0.35.4+ds1-1
ii init-system-helpers 1.60
ii libc6 2.31-11
ii libdevmapper1.02.1 2:1.02.175-2.1
ii libgpgme11 1.14.0-1+b2
ii libseccomp2 2.5.1-1
ii runc 1.0.0~rc93+ds1-3
Bug#987207: podman not running out-of-the-box as root
Hello,
I just did a minimal test VM and... it indeed works...
I'll investigate why on my machine it's not working.
But, on the test VM, podman still fails because "iptables" is not
installed, only "nft" is intalled by default now. So there is still a
problem here.
Le 21/04/21 à 05:02, Reinhard Tartler a écrit :
Control: tag -1 moreinfo
Hi Laurent,
I've downloaded the Bullseye Alpha 3 debian installer and installed
using kvm to have a super clean new system. Unfortunately, I was
unable to reproduce the issue that you described below. (I did find
some issues with rootless podman outside of a gnome-session, but
that's a different story).
The symptoms sound a lot like described in this upstream bug:
https://github.com/containers/podman/issues/5721
<https://github.com/containers/podman/issues/5721>
Can you please compare your notes with that upstream bug? Can you
confirm that the 'overlay' kernel module is loaded? (in my test, it
was loaded automatically). If you still think this is an issue in the
Debian package, please let me know. I may require your assistance with
reproducing this issue.
-rt
On Mon, Apr 19, 2021 at 11:54 AM Laurent Bigonville <mailto:bi...@debian.org>> wrote:
Package: podman
Version: 3.0.1+dfsg1-1
Severity: serious
Hello,
After installing podman, I cannot run it as root out of the box as it
fails with:
ERRO[] [graphdriver] prior storage driver overlay failed:
kernel does not support overlay fs: 'overlay' is not supported
over extfs at "/var/lib/containers/storage/overlay": backing file
system is unsupported for this graph driver
Error: kernel does not support overlay fs: 'overlay' is not
supported over extfs at "/var/lib/containers/storage/overlay":
backing file system is unsupported for this graph driver
Looking at fedora it seems that they have a containers-common package
that ships a default storage.conf file:
https://src.fedoraproject.org/rpms/containers-common/blob/rawhide/f/storage.conf
<https://src.fedoraproject.org/rpms/containers-common/blob/rawhide/f/storage.conf>
I see that the debian package is shipping a file in
/usr/share/containers/storage.conf (in the containers-storage
package),
but that file is apparently not read (strace only shows that the
file in
/etc/containers is read) and anyway unlike in fedora:
1) the driver is not set to overlay
2) the file is installed only if the containers-storage package is
installed, which is not done by default.
3) that file is not read anyway, strace only shows that
/etc/containers/storage.conf is read and not
/usr/share/containers/storage.conf, so the file is apparently useless
Shouldn't debian do the same thing than fedora so everything works
OOTB?
As a side note, I can see they are shipping also other files as well,
like the seccomp.json file, using strace, it seems that podman
tries to
read them:
[pid 14835] newfstatat(AT_FDCWD, "/etc/containers/seccomp.json",
0xcee6b8, 0) = -1 ENOENT (Aucun fichier ou dossier de ce type)
[pid 14835] newfstatat(AT_FDCWD,
"/usr/share/containers/seccomp.json", 0xcee788, 0) = -1 ENOENT
(Aucun fichier ou dossier de ce type)
Shouldn't that file be shipped by default too?
Kind regards,
Laurent Bigonville
-- System Information:
Debian Release: 11.0
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1,
'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 5.10.0-6-amd64 (SMP w/8 CPU threads)
Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8),
LANGUAGE=fr_BE:fr
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: SELinux: enabled - Mode: Permissive - Policy name: refpolicy
Versions of packages podman depends on:
ii conmon 2.0.25+ds1-1
ii containernetworking-plugins 0.9.0-1+b3
ii golang-github-containers-common 0.35.4+ds1-1
ii init-system-helpers
1.60
ii libc6
2.31-11
ii libdevmapper1.02.1
2:1.02.175-2.1
ii libgpgme11
1.14.0-1+b2
ii libseccomp2
2.5.1-1
ii runc
1.0.0~rc93+ds1-3
Versions of packages podman recommends:
ii buildah 1.20.0+ds1-1
ii fuse-overlayfs 1.4.0-1
ii golang-github-containernetworking-plugin-dnsname 1.1.1+ds1-4+b4
ii slirp4netns 1.0.1-2
ii tini 0.19.0-1
ii uidmap 1:4.8.1-1
Versions of packages podman suggests:
ii containers-storage 1.24.8+dfsg1-1+b1
ii docker-compose 1.25.0-1
-- no debconf information
--
regards,
Reinhard
Bug#987207: podman not running out-of-the-box as root
On Mon, 19 Apr 2021 17:50:52 +0200 Laurent Bigonville wrote: > > Looking at fedora it seems that they have a containers-common package > that ships a default storage.conf file: > > https://src.fedoraproject.org/rpms/containers-common/blob/rawhide/f/storage.conf Note that that file is not setting the "mount_program" by default as fedora/RH defaults to xfs. Debian is still using extfs by default, so that parameter is probably needed here
Bug#987207: podman not running out-of-the-box as root
Package: podman Version: 3.0.1+dfsg1-1 Severity: serious Hello, After installing podman, I cannot run it as root out of the box as it fails with: ERRO[] [graphdriver] prior storage driver overlay failed: kernel does not support overlay fs: 'overlay' is not supported over extfs at "/var/lib/containers/storage/overlay": backing file system is unsupported for this graph driver Error: kernel does not support overlay fs: 'overlay' is not supported over extfs at "/var/lib/containers/storage/overlay": backing file system is unsupported for this graph driver Looking at fedora it seems that they have a containers-common package that ships a default storage.conf file: https://src.fedoraproject.org/rpms/containers-common/blob/rawhide/f/storage.conf I see that the debian package is shipping a file in /usr/share/containers/storage.conf (in the containers-storage package), but that file is apparently not read (strace only shows that the file in /etc/containers is read) and anyway unlike in fedora: 1) the driver is not set to overlay 2) the file is installed only if the containers-storage package is installed, which is not done by default. 3) that file is not read anyway, strace only shows that /etc/containers/storage.conf is read and not /usr/share/containers/storage.conf, so the file is apparently useless Shouldn't debian do the same thing than fedora so everything works OOTB? As a side note, I can see they are shipping also other files as well, like the seccomp.json file, using strace, it seems that podman tries to read them: [pid 14835] newfstatat(AT_FDCWD, "/etc/containers/seccomp.json", 0xcee6b8, 0) = -1 ENOENT (Aucun fichier ou dossier de ce type) [pid 14835] newfstatat(AT_FDCWD, "/usr/share/containers/seccomp.json", 0xcee788, 0) = -1 ENOENT (Aucun fichier ou dossier de ce type) Shouldn't that file be shipped by default too? Kind regards, Laurent Bigonville -- System Information: Debian Release: 11.0 APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-6-amd64 (SMP w/8 CPU threads) Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), LANGUAGE=fr_BE:fr Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: SELinux: enabled - Mode: Permissive - Policy name: refpolicy Versions of packages podman depends on: ii conmon 2.0.25+ds1-1 ii containernetworking-plugins 0.9.0-1+b3 ii golang-github-containers-common 0.35.4+ds1-1 ii init-system-helpers 1.60 ii libc62.31-11 ii libdevmapper1.02.1 2:1.02.175-2.1 ii libgpgme11 1.14.0-1+b2 ii libseccomp2 2.5.1-1 ii runc 1.0.0~rc93+ds1-3 Versions of packages podman recommends: ii buildah 1.20.0+ds1-1 ii fuse-overlayfs1.4.0-1 ii golang-github-containernetworking-plugin-dnsname 1.1.1+ds1-4+b4 ii slirp4netns 1.0.1-2 ii tini 0.19.0-1 ii uidmap1:4.8.1-1 Versions of packages podman suggests: ii containers-storage 1.24.8+dfsg1-1+b1 ii docker-compose 1.25.0-1 -- no debconf information
Bug#986665: $HOME not writable when using schroot
Le 9/04/21 à 11:09, Simon McVittie a écrit :
On Fri, 09 Apr 2021 at 10:37:59 +0200, Laurent Bigonville wrote:
The dep8 specification says:
Tests can expect that the ``$HOME`` environment variable to be set
to a directory that exists and is writeable by the user running the test.
But when using schroot (not tried anythong else), $HOME is set to the
HOME of the user running the autopkgtest and does not exists in the
schroot. So either the spec is wrong or the implementation.
What schroot configuration are you using? Relevant information:
* your user's home directory
* the file in /etc/schroot/chroot.d defining the chroot you're using
* /etc/schroot/${profile}/fstab, where ${profile} is taken from the
chroot's configuration
If you are using profile=default (which is the default if left unspecified),
/etc/schroot/default/fstab usually bind-mounts the real /home.
If you are using profile=sbuild, /etc/schroot/sbuild/fstab usually does
not, making it unsuitable for autopkgtest-virt-schroot.
Using a chroot that contains a pre-created home directory for the user
running autopkgtest is also an option, but this is not currently something
that can be set up automatically.
I'm indeed using the "sbuild" profile, but I don't think that anybody
would want to have their real home bind mounted in the chroot and mixed
with the one from the tests
Shouldn't HOME be pointing a temporary directory like for AUTOPKGTEST_TMP ?
I would recommend using autopkgtest-virt-lxc or autopkgtest-virt-qemu:
those are considerably better-tested in practice than -schroot.
I should maybe look at that, but my schroot setup is usually enough for me
Bug#986665: $HOME not writable when using schroot
Package: autopkgtest Version: 5.16 Severity: serious Hello, The dep8 specification says: Tests can expect that the ``$HOME`` environment variable to be set to a directory that exists and is writeable by the user running the test. But when using schroot (not tried anythong else), $HOME is set to the HOME of the user running the autopkgtest and does not exists in the schroot. So either the spec is wrong or the implementation. Kind regards, Laurent Bigonville -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-5-amd64 (SMP w/8 CPU threads) Kernel taint flags: TAINT_WARN Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), LANGUAGE=fr_BE:fr Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: SELinux: enabled - Mode: Permissive - Policy name: refpolicy Versions of packages autopkgtest depends on: ii apt-utils 2.2.2 ii libdpkg-perl1.20.7.1 ii procps 2:3.3.17-5 ii python3 3.9.2-3 ii python3-debian 0.1.39 Versions of packages autopkgtest recommends: ii autodep8 0.24 Versions of packages autopkgtest suggests: pn lxc pn lxd ii ovmf 2020.11-4 pn qemu-efi-aarch64 pn qemu-efi-arm pn qemu-system ii qemu-utils1:5.2+dfsg-9 ii schroot 1.6.10-12 pn vmdb2 -- no debconf information
Bug#985317: marked as pending in gimp
Control: tag -1 pending Hello, Bug #985317 in gimp 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/gnome-team/gimp/-/commit/5e2599acefbaa7d7463a62476efcf0e92f79fe1e debian/control.in: Add graphviz to the dependencies Some optional functionality of libgegl used in gimp now requires the dot executable shipped in the graphviz package Closes: #985317 Gbp-Dch: Full (this message was generated automatically) -- Greetings https://bugs.debian.org/985317
Bug#985561: Please re-add nftables.service dependency in fail2ban.service
Package: fail2ban Version: 0.11.2-1 Severity: serious Hello, Making this RC as this could cause ordering issue during boot and firewalling rules not being properly applied, feel free to donwgrade It seem that the deb_no_iptables_service patch removes nftables.service from PartOf=, but recent nftables is shipping this service and the bullseye defaults to nft as well Shouldn't nftables.service be readded? Kind regards, Laurent Bigonville -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-4-amd64 (SMP w/8 CPU threads) Kernel taint flags: TAINT_WARN, TAINT_FIRMWARE_WORKAROUND Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: SELinux: enabled - Mode: Permissive - Policy name: refpolicy Versions of packages fail2ban depends on: ii lsb-base 11.1.0 ii python3 3.9.2-2 Versions of packages fail2ban recommends: ii iptables 1.8.7-1 ii nftables 0.9.8-3 pn python3-pyinotify pn python3-systemd ii whois 5.5.8 Versions of packages fail2ban suggests: ii bsd-mailx [mailx]8.1.2-0.20180807cvs-2 pn monit ii rsyslog [system-log-daemon] 8.2102.0-2 ii sqlite3 3.34.1-3
Bug#984879: podman: Error: failed to mount shm tmpfs
Package: podman Version: 3.0.1+dfsg1-1 Severity: serious Hello, I'm trying to run a container using podman (podman run -ti debian /bin/bash) as root and as non-root and I get the same error in both cases: Error: failed to mount shm tmpfs "/var/lib/containers/storage/overlay-containers/aeb3feb433b8cc40e61afb534c04b5ace9afbc519a4b0030407e08c405989ec4/userdata/shm": invalid argument or Error: failed to mount shm tmpfs "/home/bigon/.local/share/containers/storage/overlay-containers/b96996612a424cddcb1d38f20071c974eb185d678a882d952b338cfa18e59abb/userdata/shm": invalid argument Not sure what's happening, I don't remember changing anything to the default configuration. An idea? Kind regards, Laurent Bigonville -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-4-amd64 (SMP w/8 CPU threads) Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), LANGUAGE=fr_BE:fr Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: SELinux: enabled - Mode: Permissive - Policy name: refpolicy Versions of packages podman depends on: ii conmon 2.0.25+ds1-1 ii containernetworking-plugins 0.9.0-1+b1 ii crun 0.17+dfsg-1 ii golang-github-containers-common 0.33.4+ds1-1 ii init-system-helpers 1.60 ii libc62.31-9 ii libdevmapper1.02.1 2:1.02.175-2.1 ii libgpgme11 1.14.0-1+b2 ii libseccomp2 2.5.1-1 ii runc 1.0.0~rc93+ds1-2 Versions of packages podman recommends: ii buildah 1.19.6+dfsg1-1 ii fuse-overlayfs1.4.0-1 ii golang-github-containernetworking-plugin-dnsname 1.1.1+ds1-4+b2 ii slirp4netns 1.0.1-1 ii tini 0.19.0-1 ii uidmap1:4.8.1-1 Versions of packages podman suggests: pn containers-storage ii docker-compose 1.25.0-1 -- no debconf information
Bug#982355: manpages-l10n: File conflict with procps and manpages-*
On Tue, 09 Feb 2021 21:49:29 +1100 Craig Small wrote: > Source: manpages-l10n > Severity: important I raised the severity here as the procps package now Breaks packages built from src:manpages-l10n But looking at the build logs, procps 2:3.3.17-1 is not adding any French and is only adding one German manpages, are these breaks even worthy? Note that the w.procps.1 also look problematic and should probably be removed from the translations packages as well. procps install a w.1 -> w.procps.1 alternative symlink in English but there is nothing in the other languages
Bug#892275: redshift: Unable to connect to GeoClue
Hello, The problem here is that refshift is started before the geoclue agent is started. gnome-shell implements its own agent so that always work for people using GNOME. For people not using GNOME (or no DE at all) you need to have the geoclue agent running before doing any location query. The problem is that the geoclue agent is started via a xdg autostart file and redshift is started via a systemd user file meaning that the ordering between these two is uncertain. Moreover, using systemd to start redshift (as it requires an X display) is also feels wrong to as system will try to start it even when the user is logged in on a terminal/without X IMVHO, you should remove the redshift systemd file and let redshift start via de xdg autostart mechanism. The geoclue agent should then be started before redshift as I think it start the process using the alphabetical order. Kind regards, Laurent Bigonville
Bug#979970: libselinux1: dependency to newer libc6 ignored by/missing for aptitude
Le 26/01/21 à 13:44, Julian Andres Klode a écrit :
On Tue, Jan 26, 2021 at 12:52:52PM +0100, Aurelien Jarno wrote:
reassign 979970 src:glibc,src:libselinux,src:apt,src:openssh
thanks
On 2021-01-25 11:59, Laurent Bigonville wrote:
reassign 979970 src:glibc 2.30-1
affects 979970 + libselinux1
thanks
On Tue, 12 Jan 2021 13:31:19 +0100 Charlemagne Lasse
wrote:
Right now, an update from buster to bullseye on amd64 completely
bricks the system because libselinux1 is requiring a libc6 which is
not yet installed on the system:
Preparing to unpack .../0-libselinux1_3.1-2+b2_amd64.deb ...
De-configuring libselinux1:i386 (2.8-1+b1) ...
Unpacking libselinux1:amd64 (3.1-2+b2) over (2.8-1+b1) ...
tar: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.30' not
found (required by /lib/x86_64-linux-gnu/libselinux.so.1)
dpkg-deb: error: tar subprocess returned error exit status 1
It is then not possible anymore to recover the system because dpkg
(mv, ...) is no longer working.
There is most likely some kind dependency missing to let aptitude
known that it must first update libc6 before it can update
libselinux1. At least on this system, the installed version of libc6
for amd64 and i386 was still 2.28-10 when this happened
After some discussion on IRC it looks like the problem is apparently coming
from the breaks added to the libc6 package.
The break hasn't been added randomly, but in response to upstream
release notes and bug #965932. In short the openssh seccomp filters in
buster are too narrow, and do not allow the new 64-bit syscalls needed
for 64-bit time_t compatibility to be used.
So we definitely can't drop this break. For me this is not a libc6 bug.
Or if it is, it is as much the fault of libc6 (for using new syscalls)
than libselinux1 (for starting using symbol versioning).
This is not a question of finding the right solution, but more of the
least worst one.
The reason that libselinux needs glibc >= 2.30 is because it now uses
gettid(), it cas be replaced by syscall(__NR_gettid), right?
With the following patch, the dependency is back to "Depends: libc6 (>=
2.14), libpcre2-8-0 (>= 10.22)" at least on amd64
--- a/src/procattr.c
+++ b/src/procattr.c
@@ -94,7 +94,7 @@ static int openattr(pid_t pid, const cha
if (fd >= 0 || errno != ENOENT)
goto out;
free(path);
- tid = gettid();
+ tid = syscall(__NR_gettid);
rc = asprintf(, "/proc/self/task/%d/attr/%s", tid, attr);
} else {
errno = EINVAL;
Bug#979970: libselinux1: dependency to newer libc6 ignored by/missing for aptitude
reassign 979970 src:glibc 2.30-1 affects 979970 + libselinux1 thanks On Tue, 12 Jan 2021 13:31:19 +0100 Charlemagne Lasse wrote: > Right now, an update from buster to bullseye on amd64 completely > bricks the system because libselinux1 is requiring a libc6 which is > not yet installed on the system: > > Preparing to unpack .../0-libselinux1_3.1-2+b2_amd64.deb ... > De-configuring libselinux1:i386 (2.8-1+b1) ... > Unpacking libselinux1:amd64 (3.1-2+b2) over (2.8-1+b1) ... > tar: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.30' not > found (required by /lib/x86_64-linux-gnu/libselinux.so.1) > dpkg-deb: error: tar subprocess returned error exit status 1 > > It is then not possible anymore to recover the system because dpkg > (mv, ...) is no longer working. > > There is most likely some kind dependency missing to let aptitude > known that it must first update libc6 before it can update > libselinux1. At least on this system, the installed version of libc6 > for amd64 and i386 was still 2.28-10 when this happened After some discussion on IRC it looks like the problem is apparently coming from the breaks added to the libc6 package. I personally cannot reproduce this in chroot
Bug#979970: libselinux1: dependency to newer libc6 ignored by/missing for aptitude
On Tue, 12 Jan 2021 13:31:19 +0100 Charlemagne Lasse wrote: Hello > Right now, an update from buster to bullseye on amd64 completely > bricks the system because libselinux1 is requiring a libc6 which is > not yet installed on the system: > > Preparing to unpack .../0-libselinux1_3.1-2+b2_amd64.deb ... > De-configuring libselinux1:i386 (2.8-1+b1) ... > Unpacking libselinux1:amd64 (3.1-2+b2) over (2.8-1+b1) ... > tar: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.30' not > found (required by /lib/x86_64-linux-gnu/libselinux.so.1) > dpkg-deb: error: tar subprocess returned error exit status 1 > > It is then not possible anymore to recover the system because dpkg > (mv, ...) is no longer working. > > There is most likely some kind dependency missing to let aptitude > known that it must first update libc6 before it can update > libselinux1. At least on this system, the installed version of libc6 > for amd64 and i386 was still 2.28-10 when this happened Ouch Do you still have access to that machine? Would it be possible to attach here the /var/log/apt/eipp.log.xz (or some other log files?) created during the failed update? Kind regards, Laurent Bigonville
Bug#978172: evolution-data-server: FTBFS: CheckFunctionExists.c:17: undefined reference to `res_query'
severity 978172 normal retitle 978172 Decide whether libphonenumber or its users should B-D against libboost dev packages thanks EDS builds fine again, now that libphonenumber has reintroduced the B-D against libboost dev packages libphonenumber maintainer wants use to depend on boost dev package, let's discuss that after bullseye release
Bug#980423: 3.12.4 makes several packages FTBFS
Source: protobuf Version: 3.12.4-1 Severity: serious Hello, Several packages FTBFS since 3.12.4 The autopkgtest catched ignition-msgs and ignition-transport, see https://packages.qa.debian.org/p/protobuf.html I can see that evolution-data-server also FTBFS All seems to FTBFS for more or less the same reasons: /usr/include/ignition/msgs5/ignition/msgs/version.pb.h:59:51: error: ‘AuxiliaryParseTableField’ in namespace ‘google::protobuf::internal’ does not name a type; did you mean ‘AuxillaryParseTableField’? 59 | static const ::PROTOBUF_NAMESPACE_ID::internal::AuxiliaryParseTableField aux[] | ^~~~ | AuxillaryParseTableField This is a bit unfortunate that it's happening so late in the developpement cycle. Kind regards, Laurent Bigonville -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.9.0-5-amd64 (SMP w/8 CPU threads) Kernel taint flags: TAINT_WARN Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), LANGUAGE=fr_BE:fr Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: SELinux: enabled - Mode: Permissive - Policy name: refpolicy
Bug#948105: marked as pending in libgdata
Control: tag -1 pending Hello, Bug #948105 in libgdata 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/gnome-team/libgdata/-/commit/20fc00727a98286c30a885e74eeb865a891c8c18 debian/control.in: Rename libuhttpmock-dev to libuhttpmock-0.0-dev Closes: #948105 (this message was generated automatically) -- Greetings https://bugs.debian.org/948105
Bug#979879: arpack: FTBFS on kfreebsd, m68k and sh4 due to tests failure
Source: arpack Version: 3.8.0-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) Hello, Currently arpack FTBFS on kfreebsd, m68k and sh4 due to tests failures The difference with the other architectures is that the latest version of openmpi is not built on these. I would make the tests non-fatal on these architectures for now until openmpi builds properly. Kind regards, Laurent Bigonville -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.9.0-5-amd64 (SMP w/8 CPU threads) Kernel taint flags: TAINT_WARN Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), LANGUAGE=fr_BE:fr Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: SELinux: enabled - Mode: Permissive - Policy name: refpolicy
Bug#978437: geoclue-2.0: regression in 2.5.7-1, no geolocation returned
forwarded 978437 https://gitlab.freedesktop.org/geoclue/geoclue/-/issues/142 thanks Le 30/12/20 à 16:43, gregor herrmann a écrit : Thanks for the testing! The following line is actually the real problem, I did all my tests on laptop with wifi cards, I just tried on my desktop and I get the same error (and timeout as you) (geoclue:10479): Geoclue-WARNING **: 16:26:35.098: Failed to create query: No WiFi devices available It looks like geoclue is not doing any request to the Mozilla Location Service is there is no wifi cards (or wifi network around) anymore
Bug#978427: ppp: Updates create a copy of /lib/systemd/system/pppd-dns.service and dangling symlink
Package: ppp Version: 2.4.8-1+1~exp1 Severity: serious Hello, On upgrade, I see dpkg telling me the following: Obsolete conffile /lib/systemd/system/pppd-dns.service has been modified by you. Saving as /lib/systemd/system/pppd-dns.service.dpkg-bak ... Two problems here: 1) I never modified this file 2) This is not a conffile and the file should be removed by the package In any case, if a user would need to modify a systemd .service file, they would never modify the file in the (/usr)/lib hierarchy, but in /etc. Please drop the following line in ppp.maintscript (AFAIK, that should never be called on files that are not conffiles): rm_conffile /lib/systemd/system/pppd-dns.service 2.4.8-1+1~exp1~ Moreover, the package leave dangling symlink (/etc/systemd/system/multi-user.target.wants/pppd-dns.service) as the service was enabled before... There are also leftover in /var/lib/systemd/deb-systemd-helper-enabled. On update you should call the following commands to make sure all these files are removed: if dpkg --compare-versions "$2" le-nl "2.4.8-1+2~"; then rm -f /lib/systemd/system/pppd-dns.service.dpkg-bak deb-systemd-helper purge pppd-dns.service >/dev/null deb-systemd-helper unmask pppd-dns.service >/dev/null fi Kind regards, Laurent Bigonville -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.9.0-5-amd64 (SMP w/8 CPU threads) Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), LANGUAGE=fr_BE:fr Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: SELinux: enabled - Mode: Permissive - Policy name: refpolicy Versions of packages ppp depends on: ii libc6 2.31-6 ii libcrypt1 1:4.4.17-1 ii libpam-modules 1.3.1-5 ii libpam-runtime 1.3.1-5 ii libpam0g1.3.1-5 ii libpcap0.8 1.9.1-4 ii libssl1.1 1.1.1i-1 ii libsystemd0 247.2-3 ii procps 2:3.3.16-5 ppp recommends no packages. ppp suggests no packages. -- Configuration Files: /etc/chatscripts/gprs [Errno 13] Permission non accordée: '/etc/chatscripts/gprs' /etc/chatscripts/pap [Errno 13] Permission non accordée: '/etc/chatscripts/pap' -- no debconf information
Bug#978167: colorhug-self-test test fails
Source: colord Version: 1.4.5-2 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) Hello, Looks like the colorhug-self-test test fails on multiple architectures, including s390x: 3/4 colorhug-self-test FAIL 0.00s (killed by signal 6 SIGABRT) --- command --- 21:13:18 /<>/obj-s390x-linux-gnu/lib/colorhug/ch-self-test --- stdout --- # random seed: R02S7261ca96b49d1017624b4d4add6928d0 1..11 # Start of ColorHug tests ok 1 /ColorHug/hash ok 2 /ColorHug/device-queue Bail out! ERROR:../lib/colorhug/ch-self-test.c:227:ch_test_math_convert_func: assertion failed (pf.offset == 3): (9279 == 3) --- stderr --- ** ERROR:../lib/colorhug/ch-self-test.c:227:ch_test_math_convert_func: assertion failed (pf.offset == 3): (9279 == 3) Kind regards, Laurent Bigonville -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.9.0-5-amd64 (SMP w/4 CPU threads) Kernel taint flags: TAINT_FIRMWARE_WORKAROUND Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: SELinux: enabled - Mode: Permissive - Policy name: refpolicy
Bug#977876: packagekit-offline-update.service not enabled, not offline updates applied
Package: packagekit Version: 1.2.1-1 Severity: serious Hello, It seems that packagekit-offline-update.service is not enabled meaning that the offline update functionality is broken. This is annoying as GNOME is using this functionality meaning that it's possible the the system of our users are not updated. The contrib/PackageKit.spec.in file explicitly creates a symlink to system-update.target.wants: mkdir -p $RPM_BUILD_ROOT/usr/lib/systemd/system/system-update.target.wants ln -sf /usr/lib/systemd/system/packagekit-offline-update.service \ $RPM_BUILD_ROOT/usr/lib/systemd/system/system-update.target.wants/packagekit-offline-update.service That symlink should also be created IMVHO (fwupd is also doing that) Could you please make sure that this is done? Kind regards, Laurent Bigonville -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.9.0-5-amd64 (SMP w/8 CPU threads) Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), LANGUAGE=fr_BE:fr Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: SELinux: enabled - Mode: Permissive - Policy name: refpolicy
Bug#970933: marked as pending in geary
Control: tag -1 pending Hello, Bug #970933 in geary 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/gnome-team/geary/-/commit/3e29004d68de382f22e4a5f1c8a90326ed063a9f New upstream release (Closes: #972520, #970933) (this message was generated automatically) -- Greetings https://bugs.debian.org/970933
Bug#973648: marked as pending in glade
Control: tag -1 pending Hello, Bug #973648 in glade 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/gnome-team/glade/-/commit/06857d4b765437a7102155214bb6f48a168a8f5e debian/control.in: Add Breaks/Replaces against libgladeui-2-6 (Closes: #973648) (this message was generated automatically) -- Greetings https://bugs.debian.org/973648
Bug#971166: marked as pending in libgovirt
Control: tag -1 pending Hello, Bug #971166 in libgovirt 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/gnome-team/libgovirt/-/commit/315441d2bd8d482ae258e80599686e5ade8b773b debian/control.in: Add ca-certificates to the BD, this is needed for the tests (Closes: #971166) (this message was generated automatically) -- Greetings https://bugs.debian.org/971166
Bug#956355: pam: Please stop using deprecated and headers
Hello, The package currently FTBFS in debian due to this. FTR, Andreas packaged the (then) new 1.4.0 upstream release that fixes this problem: https://salsa.debian.org/ah/pam/-/commits/master-1.4.0 IMVHO, we should really update to at least that version (and maybe to 1.5.1 that it's now out as well). Steve, do you think you would have time to update PAM? Kind regards, Laurent Bigonville
Bug#963311: telepathy-glib: FTBFS: E: Build killed with signal TERM after 150 minutes of inactivity
severity 963311 important thanks The package builds fine on all release architectures, I don't think that bug is RC anymore
Bug#968816: tilix: Library load failed (librsvg-2.so.2): ... Illegal instruction
libgtkd-3-dev should also probably pull librsvg2-dev and maybe other -dev package as well (like gtk, glib, atk, cairo, ...): cat /usr/lib/x86_64-linux-gnu/pkgconfig/gtkd-3.pc Name: GtkD Description: A D binding and OO wrapper for GTK+. Version: 3.9.0 Libs: -L-L/usr/lib/x86_64-linux-gnu/ -L-lgtkd-3 -L-ldl Cflags: -I/usr/include/d/gtkd-3/ Requires: gtk+-3.0, gdk-3.0, atk, pango, cairo, cairo-gobject, pangocairo, librsvg-2.0, gio-2.0, glib-2.0, gobject-2.0
Bug#968816: tilix: Library load failed (librsvg-2.so.2): ... Illegal instruction
reassign 968816 libgtkd-3-0 3.9.0-3 affects 968816 +tilix Thanks On Fri, 21 Aug 2020 18:38:28 +0200 Jakub Wilk wrote: > > When librsvg2-2 is not installed, tilix crashes with SIGILL: > > $ tilix > object.Exception@generated/gtkd/gtkd/Loader.d(125): Library load failed (librsvg-2.so.2): librsvg-2.so.2: cannot open shared object file: No such file or directory > Illegal instruction > This looks like a gtkd issue to me. They had the same issue in Red Hat and it was fixed in that package: https://bugzilla.redhat.com/show_bug.cgi?id=1694324 Reassigning to gtkd then
Bug#871564: closing 871564
close 871564 thanks This is probably fixed by the switch to a new upstream
Bug#971728: closing 971728
close 971728 0.9.0-2 thanks Hello, This is fixed in 0.9.0-2 Kind regards, Laurent Bigonville
Bug#970589: marked as pending in tracker-miners
Control: tag -1 pending Hello, Bug #970589 in tracker-miners 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/gnome-team/tracker-miners/-/commit/74decc3598e02481ef2588cbeea8c0dce973b128 New upstream release - Remove generic gstreamer-based image extraction codepath - Allow statx in seccomp filter, used by newer GLib - Set a deadline of 30 seconds for extraction tasks - Several fixes to libav-based extractor Closes: #970589 (this message was generated automatically) -- Greetings https://bugs.debian.org/970589
Bug#968035: Cannot migrate to testing due to Breaks: mercurial-crecord (<= 0.20151121-2)
Source: mercurial Version: 5.4.1-2 Severity: serious Hello, mercurial cannot migrate to testing due to the Breaks against mercurial-crecord (<= 0.20151121-2) It is discussed here[0] that mercurial-crecord 0.20151121-2 is now a transitional package that is displaying a NEWS message during the update to tell the users how they can enable the built-in feature. So either, the mercurial-crecord should completely be removed or the Breaks should be changed to mercurial-crecord (<< 0.20151121-2~) Kind regards, Laurent Bigonville [0] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=804267#25 -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.7.0-2-amd64 (SMP w/8 CPU threads) Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), LANGUAGE=fr_BE:fr Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: SELinux: enabled - Mode: Permissive - Policy name: refpolicy
Bug#956354: libuser: Please stop using deprecated and headers
severity 956354 important thanks Well actually, selinux support is not enabled in libuser, so this is not RC ATM
Bug#956691: fixed in psi 1.3-6
On Wed, 01 Jul 2020 21:52:11 + Debian FTP Masters wrote: Hello, > * Use libhunspell instead of libenchant (Closes: Bug#956691) Just for my understanding, why did you switch to libhunspell instead of libenchant-2? As said it seems to have support for enchant-2 in the code (there are references to HAVE_ENCHANT2) Kind regards, Laurent Bigonville
Bug#956710: fixed in abiword 3.0.2-11
Hello, On Fri, 05 Jun 2020 22:03:34 + Debian FTP Masters wrote: > * add patch to use enchat2 instead of enchant; The fix is not complete, the libabiword-dev package still depends on libenchant-dev Could you also fix that please? Kind regards, Laurent Bigonville
Bug#961279: Experimental version needs to be ported to mozjs68
Package: policykit-1 Version: 0.116-2 Severity: serious Tags: experimental Hello, policykit-1 0.116 from experimental needs to be ported to mozjs68 now that mozjs60 is gone from the archive. Kind regards, Laurent Bigonville -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.6.0-1-amd64 (SMP w/8 CPU cores) Kernel taint flags: TAINT_FIRMWARE_WORKAROUND Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), LANGUAGE=fr_BE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: SELinux: enabled - Mode: Permissive - Policy name: refpolicy Versions of packages policykit-1 depends on: ii adduser 3.118 ii dbus 1.13.14-1 ii libc62.30-8 ii libexpat12.2.9-1 ii libgcc-s1 [libgcc1] 10.1.0-2 ii libglib2.0-0 2.64.2-1 ii libmozjs-60-060.8.0-2 ii libpam-systemd [logind] 245.5-3 ii libpam0g 1.3.1-5 ii libpolkit-agent-1-0 0.116-2 ii libpolkit-gobject-1-00.116-2 ii libstdc++6 10.1.0-2 ii libsystemd0 245.5-3 policykit-1 recommends no packages. policykit-1 suggests no packages. Versions of packages policykit-1 is related to: pn elogind pn libpam-elogind ii libpam-systemd 245.5-3 ii systemd 245.5-3 -- Configuration Files: /etc/polkit-1/rules.d/40-debian-sudo.rules [Errno 13] Permission non accordée: '/etc/polkit-1/rules.d/40-debian-sudo.rules' /etc/polkit-1/rules.d/50-default.rules [Errno 13] Permission non accordée: '/etc/polkit-1/rules.d/50-default.rules' -- no debconf information
Bug#954690: closing 954690
close 954690 2.8.4-2 thanks Hey, This has been fixed in the last upload: [ Philip Withnall ] * Backport patch from upstream to fix encoding issue with GLib 2.63
Bug#960653: /usr/lib/python3.7/tkinter/__pycache__/ not deleted
Package: python3-tk Version: 3.8.3-1 Severity: serious Hello, When updating today, dpkg complained about the /usr/lib/python3.7 directory not being empty: Dépaquetage de python3-distutils (3.8.3-1) sur (3.8.2-2) ... dpkg: avertissement: impossible de supprimer l'ancien répertoire « /usr/lib/python3.7 » : Le dossier n'est pas vide Looking at the context of /usr/lib/python3.7 I found that there was still /usr/lib/python3.7/tkinter/__pycache__/ containing .pyc files in it. The .pyc and the pycache directory should be deleted when python3-tk was moved from 3.7 to 3.8. Kind regards, Laurent Bigonville -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.6.0-1-amd64 (SMP w/8 CPU cores) Kernel taint flags: TAINT_WARN Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), LANGUAGE=fr_BE:fr (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: SELinux: enabled - Mode: Permissive - Policy name: refpolicy Versions of packages python3-tk depends on: ii blt 2.5.3+dfsg-4+b1 ii libc6 2.30-8 ii libtcl8.6 8.6.10+dfsg-1 ii libtk8.6 8.6.10-1 ii python3 3.8.2-3 ii tk8.6-blt2.5 2.5.3+dfsg-4+b1 python3-tk recommends no packages. Versions of packages python3-tk suggests: pn python3-tk-dbg ii tix 8.4.3-10+b1 -- no debconf information
Bug#959962: Missing dependencies?
Package: virt-p2v Version: 1.42.0-1 Severity: serious Hello, virt-p2v has no dependencies defined, but quickly looking which external tools it's using it should IMVHO at least requires the following dependencies: xz-utils for xzcat binutils for strip libguestfs-tools for virt-builder It's also using bash and gzip but these are essentials and should probably not be added to the dependencies. Kind regards, Laurent Bigonville -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.5.0-2-amd64 (SMP w/8 CPU cores) Kernel taint flags: TAINT_FIRMWARE_WORKAROUND Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), LANGUAGE=fr_BE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: SELinux: enabled - Mode: Permissive - Policy name: refpolicy
Bug#959961: Prefix not properly set?
Package: virt-p2v Version: 1.42.0-1 Severity: grave Hi, When running virt-p2v-make-disk or virt-p2v-make-kiwi, I get the folowing errors: # virt-p2v-make-disk -o plop virt-p2v-make-disk: cannot find /lib/x86_64-linux-gnu/virt-p2v/virt-p2v.xz # virt-p2v-make-kiwi /usr/bin/virt-p2v-make-kiwi: cannot find dependencies file (/share/virt-p2v/dependencies.suse) The files are installed under /usr/lib/x86_64-linux-gnu/virt-p2v/virt-p2v.xz and /usr/share/virt-p2v/dependencies.suse. Looks like the prefix is not properly set Kind regards, Laurent Bigonville -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.5.0-2-amd64 (SMP w/8 CPU cores) Kernel taint flags: TAINT_FIRMWARE_WORKAROUND Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), LANGUAGE=fr_BE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: SELinux: enabled - Mode: Permissive - Policy name: refpolicy
Bug#948780: closing 948780
close 948780 3.36.0-1 thanks Hello, Not sure what happened but 3.36.0-1 is building fine on the buildd Closing this bugreport
Bug#956881: enchant: Keep out of bullseye
Source: enchant Version: 1.6.0-11.3 Severity: serious Tags: sid bullseye Hello, I don't think we want to ship both enchant (v1) and enchant-2 in bullseye. The transition[0] is in progress and bugs (most with patch) have been opened against the rdeps. So let's make it clear that enchant will not be present in bullseye. Kind regards, Laurent Bigonville [0] https://release.debian.org/transitions/html/enchant-2.html -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.5.0-1-amd64 (SMP w/8 CPU cores) Kernel taint flags: TAINT_WARN Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), LANGUAGE=fr_BE:fr (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: SELinux: enabled - Mode: Permissive - Policy name: refpolicy
Bug#955668: libgaminggear: FTBFS: pango-coverage.h:28:10: fatal error: hb.h: No such file or directory
reassign 955668 src:libgaminggear 0.15.1-9
tag 955668 + ftbfs patch
thanks
On Sat, 11 Apr 2020 18:30:19 +0200 Pierre-Elliott =?utf-8?B?QsOpY3Vl?=
wrote:
> Le vendredi 03 avril 2020 à 21:37:34+0200, Lucas Nussbaum a écrit :
> > [snip]
>
> libpango1.0-dev should depend on libharfbuzz-dev, but it doesn't. This
> bug seems to be in src:pango1.0, and therefore I reassign it.
>
> Dear pango1.0 maintainers, please fix the dependencies of
> libpango1.0-dev.
>
Well actually no, libpango1.0-dev already depends on libharfbuzz-dev
The problem seems to be that libgaminggear build-system does not rely on
the information coming from pkg-config (it doesn't use the variables
starting with PKG_) and instead guessing the path for the include
directory itself.
My knowledge of CMake is really low, but the attached patch seems to fix
the FTBFS
Kind regards,
Laurent Bigonville
--- a/CMakeLists.txt
+++ b/CMakeLists.txt
@@ -76,6 +76,7 @@ INCLUDE_DIRECTORIES(
${GTK_INCLUDE_DIRS}
${M_INCLUDE_DIR}
${NOTIFY_INCLUDE_DIRS}
+ ${PKG_PANGO_INCLUDE_DIRS}
)
ADD_SUBDIRECTORY(configuration)
Bug#952582: marked as pending in gnome-builder
Control: tag -1 pending Hello, Bug #952582 in gnome-builder 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/gnome-team/gnome-builder/-/commit/a32b7e6e2c30af1f821a39f65f31a49fc2bd9953 d/p/meson-Add-generated-lsp-enum-header-to-lsp-sources.patch: Fix FTBFS Avoid race condition by adding generated lsp enum header to lsp sources Gbp-Dch: full Closes: #952582 (this message was generated automatically) -- Greetings https://bugs.debian.org/952582
Bug#956527: FTBFS: debian/rules still uses python(2) without havind an explicit dependency
Source: numpy Version: 1:1.17.4-5 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) Hello, numpy FTBFS with the following error: python debian/versions3.helper >> debian/python3-numpy.substvars /bin/sh: 1: python: not found It apparently still uses python2 without havind an explicit dependency Kind regards, Laurent Bigonville -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.5.0-1-amd64 (SMP w/8 CPU cores) Kernel taint flags: TAINT_WARN Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), LANGUAGE=fr_BE:fr (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: SELinux: enabled - Mode: Permissive - Policy name: refpolicy
Bug#955659: closing 955659
close 955659 6.1.09-1 thanks Hi, The tests seem to succeed now Closing this bugreport Kind regards, Laurent Bigonville
Bug#955264: marked as pending in librsvg
Control: tag -1 pending Hello, Bug #955264 in librsvg 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/gnome-team/librsvg/-/commit/3ecbcc462abca0cc4d0cc5cd3f6b1dd171945153 Fix FTBFS in the tests due to missing link against libharfbuzz Closes: #955264 (this message was generated automatically) -- Greetings https://bugs.debian.org/955264
Bug#955399: FTBFS when building arch:all packages only
Source: xorg-server Version: 2:1.20.7-4 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) Hello, It seems that xorg-server FTBFS when building arch:all packages only, https://buildd.debian.org/status/fetch.php?pkg=xorg-server=all=2%3A1.20.8-1=1585574275=0 dh_missing --fail-missing dh_missing: warning: udeb/usr/bin/Xorg exists in debian/tmp but is not installed to anywhere dh_missing: warning: udeb/usr/lib/xorg/protocol.txt exists in debian/tmp but is not installed to anywhere dh_missing: warning: udeb/usr/lib/xorg/modules/libshadowfb.so exists in debian/tmp but is not installed to anywhere dh_missing: warning: udeb/usr/lib/xorg/modules/libfbdevhw.so exists in debian/tmp but is not installed to anywhere dh_missing: warning: udeb/usr/lib/xorg/modules/libshadow.so exists in debian/tmp but is not installed to anywhere dh_missing: warning: udeb/usr/lib/xorg/modules/libfb.so exists in debian/tmp but is not installed to anywhere dh_missing: warning: udeb/usr/lib/xorg/modules/libvbe.so exists in debian/tmp but is not installed to anywhere dh_missing: warning: udeb/usr/lib/xorg/modules/libvgahw.so exists in debian/tmp but is not installed to anywhere dh_missing: warning: udeb/usr/lib/xorg/modules/libint10.so exists in debian/tmp but is not installed to anywhere dh_missing: warning: udeb/usr/lib/xorg/modules/drivers/modesetting_drv.so exists in debian/tmp but is not installed to anywhere dh_missing: warning: udeb/usr/share/X11/xorg.conf.d/10-quirks.conf exists in debian/tmp but is not installed to anywhere dh_missing: error: missing files, aborting The following debhelper tools have reported what they installed (with files per package) * dh_install: xdmx (2), xdmx-tools (14), xnest (2), xorg-server-source (1), xserver-common (3), xserver-xephyr (2), xserver-xorg-core (13), xserver-xorg-core-udeb (4), xserver-xorg-dev (5), xserver-xorg-legacy (3), xvfb (4), xwayland (1) * dh_installdocs: xdmx (0), xdmx-tools (0), xnest (0), xorg-server-source (0), xserver-common (0), xserver-xephyr (1), xserver-xorg-core (0), xserver-xorg-dev (0), xserver-xorg-legacy (0), xvfb (0), xwayland (0) * dh_installman: xdmx (0), xdmx-tools (0), xnest (0), xorg-server-source (0), xserver-common (0), xserver-xephyr (0), xserver-xorg-core (0), xserver-xorg-dev (0), xserver-xorg-legacy (0), xvfb (0), xwayland (0) If the missing files are installed by another tool, please file a bug against it. When filing the report, if the tool is not part of debhelper itself, please reference the "Logging helpers and dh_missing" section from the "PROGRAMMING" guide for debhelper (10.6.3+). (in the debhelper package: /usr/share/doc/debhelper/PROGRAMMING.gz) Be sure to test with dpkg-buildpackage -A/-B as the results may vary when only a subset is built For a short-term work-around: Add the files to debian/not-installed -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.4.0-4-amd64 (SMP w/8 CPU cores) Kernel taint flags: TAINT_WARN Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), LANGUAGE=fr_BE:fr (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: SELinux: enabled - Mode: Permissive - Policy name: refpolicy
Bug#954912: Please switch to gupnp/gssdp 1.2
Source: librm Version: 2.1.2-2 Severity: serious Tags: patch Hello, Could you please switch the build-dependencies to gupnp/gssdp 1.2 instead of 1.0? We are currently trying to get rid of the version 1.0 librm has reintroduced a reverse-dependencies against that old version. Kind regards Laurent Bigonville -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.4.0-4-amd64 (SMP w/8 CPU cores) Kernel taint flags: TAINT_WARN Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), LANGUAGE=fr_BE:fr (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: SELinux: enabled - Mode: Permissive - Policy name: refpolicy diff -Nru librm-2.1.2/debian/control librm-2.1.2/debian/control --- librm-2.1.2/debian/control 2020-02-04 22:47:40.0 +0100 +++ librm-2.1.2/debian/control 2020-03-25 08:54:31.0 +0100 @@ -13,8 +13,8 @@ libspandsp-dev, libjson-glib-dev, libsndfile1-dev, - libgupnp-1.0-dev, - libgssdp-1.0-dev, + libgupnp-1.2-dev, + libgssdp-1.2-dev, libcapi20-dev, libgstreamer1.0-dev, libgstreamer-plugins-base1.0-dev,
Bug#954553: marked as pending in nautilus
Control: tag -1 pending Hello, Bug #954553 in nautilus 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/gnome-team/nautilus/-/commit/efed905f6af8056d216a0bbf47f84bdfcb558e4e debian/control.in: Lower pango BD to 1.42, there is now a version check in the code for the functionalities that require 1.44 Closes: #954553 (this message was generated automatically) -- Greetings https://bugs.debian.org/954553
Bug#954195: marked as pending in gnome-music
Control: tag -1 pending Hello, Bug #954195 in gnome-music 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/gnome-team/gnome-music/-/commit/d2268bebe7ab555f76426256db533f57e94fbb34 d/p/gnome-music.in-Do-not-change-the-module-search-path-on-in.patch, d/p/gnome-music.in-Do-not-use-pyexecdir-variable.patch: Do not change the python search path, from upstream Closes: #954195 (this message was generated automatically) -- Greetings https://bugs.debian.org/954195
Bug#954284: puppet broken with ruby 2.7
severity 954284 serious Thanks On Thu, 19 Mar 2020 17:51:32 +0100 Laurent Bigonville wrote: > Hello, > > With ruby 2.7 upload, when running the puppet cli, I get the following > warning/error: > > /usr/lib/ruby/vendor_ruby/puppet/util.rb:461: warning: URI.escape is obsolete > cannot load such file -- sync > > puppet returns a non-zero exit code > OK the puppet package "only" lacks of a dependency on ruby-sync gem
Bug#954284: puppet broken with ruby 2.7
Package: puppet Version: 5.5.10-4 Severity: grave Hello, With ruby 2.7 upload, when running the puppet cli, I get the following warning/error: /usr/lib/ruby/vendor_ruby/puppet/util.rb:461: warning: URI.escape is obsolete cannot load such file -- sync puppet returns a non-zero exit code Kind regards, Laurent Bigonville -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.4.0-4-amd64 (SMP w/8 CPU cores) Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), LANGUAGE=fr_BE:fr (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: SELinux: enabled - Mode: Permissive - Policy name: refpolicy Versions of packages puppet depends on: ii adduser 3.118 ii facter 3.11.0-3+b1 ii hiera3.2.0-2 ii init-system-helpers 1.57 ii lsb-base 11.1.0 ii ruby 1:2.7 ii ruby-augeas 1:0.5.0-3+b7 ii ruby-deep-merge 1.1.1-1 ii ruby-shadow 2.5.0-1+b2 Versions of packages puppet recommends: ii debconf-utils 1.5.73 ii lsb-release11.1.0 pn ruby-selinux Versions of packages puppet suggests: pn ruby-hocon pn ruby-rrd -- no debconf information
Bug#954257: python3-audit: SWIG-related type errors render module unusable
Package: python3-audit Version: 1:2.8.5-2 Severity: grave Control: forward -1 https://github.com/linux-audit/audit-userspace/issues/120 Looks like #927946 is back/was not properly fixed This only affects unstable (and probably bullseye) -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.4.0-4-amd64 (SMP w/8 CPU cores) Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), LANGUAGE=fr_BE:fr (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: SELinux: enabled - Mode: Permissive - Policy name: refpolicy Versions of packages python3-audit depends on: ii libaudit11:2.8.5-2+b1 ii libauparse0 1:2.8.5-2+b1 ii libc62.30-2 ii python3 3.8.2-1 python3-audit recommends no packages. python3-audit suggests no packages. -- no debconf information
Bug#952097: fixed in spice-gtk 0.37-2
On Tue, 17 Mar 2020 22:06:04 + Debian FTP Masters wrote: > * debian/control: Add libdrm-dev to the build-dependencies (Closes: #952097) FTR, upstream has removed the include, so libdrm-dev can be removed with the next upstream release
Bug#952597: Two gdcm bugs fixed in Git
On Wed, 11 Mar 2020 00:25:25 + peter green wrote: > > ... > > The following packages have unmet dependencies: > > python3-vtk7 : Depends: python3 (< 3.8) but 3.8.2-1 is to be installed > > Unable to resolve dependencies! Giving up... > > ... > This was a result of the python 3.8 transition, vtk7 has now been rebuilt on most architectures (mips is still building) and so it is now possible to satisfy the build-dependencies of gdcm. > > I just did a test build, but unfortunately it failed. There is a new (3.0.5) upstream release, maybe that will help? > > cd /gdcm/obj-x86_64-linux-gnu/Utilities/VTK && /usr/bin/cmake -E make_directory /gdcm/obj-x86_64-linux-gnu/Utilities/VTK /gdcm/obj-x86_64-linux-gnu/Utilities/VTK/CMakeFiles/vtkgdcmsharpglue.dir && /usr/bin/cmake -E env SWIG_LIB=/usr/share/swig4.0 /usr/bin/swig4.0 -csharp -namespace vtkgdcm -dllimport vtkgdcmsharpglue -outdir /gdcm/obj-x86_64-linux-gnu/Utilities/VTK -c++ -I/usr/include -I/usr/include/vtk-7.1 -I/usr/include/freetype2 -I/usr/include/x86_64-linux-gnu -I/usr/lib/x86_64-linux-gnu/openmpi/include/openmpi -I/usr/lib/x86_64-linux-gnu/openmpi/include -I/usr/include/python3.8 -I/usr/include/hdf5/openmpi -I/usr/include/jsoncpp -I/usr/include/libxml2 -I/usr/include/tcl -I/gdcm/obj-x86_64-linux-gnu/Source/Common -I/gdcm/Source/Common -I/gdcm/Source/DataStructureAndEncodingDefinition -I/gdcm/Source/MediaStorageAndFileFormat -I/gdcm/Source/DataDictionary -I/gdcm/Utilities/VTK -o /gdcm/obj-x86_64-linux-gnu/Utilities/VTK/CMakeFiles/vtkgdcmsharpglue.dir/vtkgdcmCSHARP_wrap.cxx > > /gdcm/Utilities/VTK/vtkgdcm.i > > /usr/include/vtk-7.1/vtkStringArray.h:36: Warning 402: Base class 'vtkAbstractArray' is incomplete. > > /usr/include/vtk-7.1/vtkAlgorithm.h:38: Warning 402: Only forward declaration 'vtkAbstractArray' was found. > > /gdcm/Utilities/VTK/vtkgdcm.i:354: Error: A deprecated csdestruct_derived typemap was found for vtkGDCMTesting, please remove it and replace all csdestruct, csdestruct_derived and csfinalize typemaps by the csdispose, csdispose_derived, csdisposing and csdisposing_derived typemaps. > > /gdcm/Utilities/VTK/vtkgdcm.i:365: Error: A deprecated csdestruct_derived typemap was found for vtkGDCMImageReader, please remove it and replace all csdestruct, csdestruct_derived and csfinalize typemaps by the csdispose, csdispose_derived, csdisposing and csdisposing_derived typemaps. > > /gdcm/Utilities/VTK/vtkgdcm.i:376: Error: A deprecated csdestruct_derived typemap was found for vtkGDCMImageWriter, please remove it and replace all csdestruct, csdestruct_derived and csfinalize typemaps by the csdispose, csdispose_derived, csdisposing and csdisposing_derived typemaps. > > ninja: build stopped: subcommand failed. > > dh_auto_build: error: cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 ninja -j1 -v returned exit code 1 > > make[1]: *** [debian/rules:110: override_dh_auto_build-arch] Error 25 > > make[1]: Leaving directory '/gdcm' > > make: *** [debian/rules:54: build] Error 2 > >
Bug#953398: marked as pending in gnome-builder
Control: tag -1 pending Hello, Bug #953398 in gnome-builder 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/gnome-team/gnome-builder/-/commit/e159936a5ff37e3bde1ebceaf1406090bbc02b79 debian/control.in: Fix the version of gir1.2-glib-2.0 to make it installable again, oups (Closes: #953398) (this message was generated automatically) -- Greetings https://bugs.debian.org/953398
Bug#952416: marked as pending in glom
Control: tag -1 pending Hello, Bug #952416 in glom 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/gnome-team/glom/-/commit/d4f05832f2cfd8f89685d559378272a872b06a9b debian/rules: Fix FTBFS with python3.8 (Closes: #952416) (this message was generated automatically) -- Greetings https://bugs.debian.org/952416
Bug#952211: marked as pending in yarl
Control: tag -1 pending Hello, Bug #952211 in yarl 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/modules/yarl/-/commit/afcf96d3325e3deaa914703b29f4deabc917067b Fix test related FTBFS with python 3.8.2 (Closes: #952211) * Team upload. * Update d/p/0005-Fix-tests-in-new-Pythons.patch to fix tests with python 3.8.2, upstream has reverted a fix to avoid unexpected behaviour change in a point release (Closes: #952211) (this message was generated automatically) -- Greetings https://bugs.debian.org/952211
Bug#952211: marked as pending in yarl
Control: tag -1 pending Hello, Bug #952211 in yarl 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/modules/yarl/-/commit/afcf96d3325e3deaa914703b29f4deabc917067b Fix test related FTBFS with python 3.8.2 (Closes: #952211) * Team upload. * Update d/p/0005-Fix-tests-in-new-Pythons.patch to fix tests with python 3.8.2, upstream has reverted a fix to avoid unexpected behaviour change in a point release (Closes: #952211) (this message was generated automatically) -- Greetings https://bugs.debian.org/952211
Bug#953222: Bug#953223 closed by Debian FTP Masters (reply to Laszlo Boszormenyi (GCS) ) (Bug#953223: fixed in fuse3 3.9.0-2)
Hey, I'm wondering is this shouldn't be fixed in debian stable (fuse and fuse3) as well Kind regards, Laurent Bigonville Le 7/03/20 à 12:54, Debian Bug Tracking System a écrit : This is an automatic notification regarding your Bug report which was filed against the fuse3 package: #953223: Stop explicitly removing /etc/fuse.conf on purge It has been closed by Debian FTP Masters (reply to Laszlo Boszormenyi (GCS) ). 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 Laszlo Boszormenyi (GCS) ) by replying to this email.
Bug#953223: Stop explicitly removing /etc/fuse.conf on purge
Package: fuse3 Version: 3.9.0-1 Severity: serious Hi, I discovered today that for some reasons the /etc/fuse.conf (conffile) was missing on my machine while I didn't remember deleting it myself. After some investigations I discovered that both the fuse and fuse3 are providing /etc/fuse.conf and are explicitly removing that file in their postrm scripts on purge. IMHO this is not OK (and even a policy violation) Please stop removing /etc/fuse.conf and let dpkg handle that Kind regards, Laurent Bigonville -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.4.0-4-amd64 (SMP w/8 CPU cores) Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), LANGUAGE=fr_BE:fr (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: SELinux: enabled - Mode: Permissive - Policy name: refpolicy Versions of packages fuse3 depends on: ii adduser 3.118 ii libc6 2.29-10 ii libfuse3-3 3.9.0-1 ii lsb-base11.1.0 ii mount 2.34-0.1 ii sed 4.7-1 fuse3 recommends no packages. fuse3 suggests no packages. -- no debconf information
