Bug#1067660: wireplumber: Wireplumber 0.5.0 breaks asahi-audio 1.x
Hello Andreas, Le mar. 30 avr. 2024 à 17:26, Andreas Henriksson a écrit : > > We now have asahi-audio 2.x in experimental. Please poke us again when > we should upload to unstable (or feel free to NMU asahi-audio to > unstable when you upload wireplumber 0.5.x to unstable). > The release team agreed to go ahead with this transition, so I am going to upload wireplumber in unstable and I will do a nmu for asahi-audio at the same time. Best regards, Dylan
Bug#1064401: python-requests-kerberos: please package version 0.14
Hi, FYI, version 0.14 needs python-pyspnego that I'm going to package. Cheers, Thomas Goirand (zigo)
Bug#1070477: RM: freezer-api -- ROM; unmaintained upstream
Package: ftp.debian.org Severity: normal User: ftp.debian@packages.debian.org Usertags: remove X-Debbugs-Cc: freezer-...@packages.debian.org Control: affects -1 + src:freezer-api Hi, freezer was already removed from Debian, let's also remove freezer-api. Cheers, Thomas Goirand (zigo)
Bug#981754: Interest in taking over the dkopp Debian package
[Hill Ma] > I made a merge request for 7.7 here: > https://salsa.debian.org/debian/dkopp/-/merge_requests/3 This process seem to have completely stopped. I found some lingering changes in https://salsa.debian.org/debian/dkopp >, diverting from the current package in the archive. I am working to clean this up. If you want me to sponsor the upload, my sponsoring preferences are available from http://www.hungry.com/~pere/debian-sponsoring.html >. -- Happy hacking PEtter Reinholdtsen
Bug#1070292: Dep removed from python-influxdb-client
I've uploaded the fix to python-influxdb-client. Thomas
Bug#1070332: Wont fix
Hi Thomas, * Thomas Goirand [2024-05-06 08:21]: I already explained this: I am *NOT* interested in addressing this type of failure. Designate is "OpenStack DNS as a Service", therefore, it is expected that it's going to check/use /etc/resolv.conf. If you carefully look at what's going on, you'll see that it's not even doing DNS queries to the outside, it's simply testing itself. Removing the test would mean less Q/A, which is not desirable. "Fixing" the test would mean more work, which isn't needed in this case (the package works perfectly). Feel free to bug upstream and resolve it there if you think that's valuable, though I am of the opinion it's a loss of time. Also, note that the package builds perfectly fine in the current buildd environment (and on my laptop's sbuild setup). If that was going to change, of course, I'd review my opinion. In the mean time, I see no point in this bug. Fix your build env... Note that the buildds started switching to the unshare backend so the package will FTBFS soon. Cheers Jochen signature.asc Description: PGP signature
Bug#1070473: debhelper: Run dh_installsysusers after dh_installtmpfiles
Jeremy Bícha: Source: debhelper Version: 13.15.3 Control: affects -1 src:gnome-remote-desktop X-Debbugs: syst...@packages.debian.org gnome-remote-desktop 46 upstream has decided to implement both tmpfiles.d and sysusers.d to create a system user and its home directory. systemd-tmpfiles needs to run before systemd-sysusers. If not, on a new install, this command hangs for about 90 seconds: Creating user 'gnome-remote-desktop' (GNOME Remote Desktop) with UID *** and GID ***. Then this error: Could not execute systemctl: at /usr/bin/deb-systemd-invoke line 148. Then the installation completes successfully. Therefore, I recommend that debhelper automatically runs dh_installtmpfiles before running dh_installsysusers in case any other projects want to do what gnome-remote-desktop does. I was able to workaround this issue: https://salsa.debian.org/gnome-team/gnome-remote-desktop/-/commit/8490919 Thank you, Jeremy Bícha Hi Michael and Luca What is the correct order for tmpfiles vs. sysusers? I thought the order was sysusers (to create the user) and then tmpfiles (to create files/directories and set ownership accordingly). In this bug report, the request is to have the directories first before the user is created. Could you please assert what the correct order is for the default case? Best regards, Niels
Bug#1069600: Fwd: dm-writeboost: isolation-machine autopkgtest fails: sudo: not found
On 06/05/2024 07.38, Paul Gevers wrote: Hi, On 05-05-2024 8:04 p.m., Andreas Beckmann wrote: 167s autopkgtest [09:50:25]: test test-dm-writeboost.sh: [--- 168s II: Checking for 14G available disk space...SKIP How much disk space is used already by the time you get to this test? The test has done nothing, yet. The root of the testbed has 25 GB total (starting off with 990 MB used), so your test has 24 GB to use (including installing test dependencies). The biggest test dependency is (virtual) linux-headers-generic + deps, as (virtual) linux-image-generic should already be isntalled ... So there should be plenty of space available. The skip is probably coming from the non-verbose check for 8 CPUs where I applied the patch from Ubuntu... Will make that verbose and also report skip reasons better. Andreas
