Bug#1065553: marked as done (fonts-jetbrains-mono: Jetbrains-Mono 2.304 broken in Gnome Terminal)
> Tried again, and the problem goes away if I close all open gnome-terminals, > so this bug can be closed. > I guess it's a problem in gnome-terminal that doesn't detect the font file > changed, and tries accessing glyphs in wrong locations in the font file > (based on the older file). There is a longstanding bug where apps need to be restarted to make use of updated fonts. A particularly serious report of this is https://bugs.debian.org/788791 which is mitigated because the Cantarell font (the default UI font for Debian's GNOME Shell) is only updated rarely. Thank you, Jeremy Bícha
Bug#1071546: rust-curve25519-dalek: failing autopkgtests
Source: rust-curve25519-dalek Version: 4+20240207+dfsg-3 Severity: serious rust-curve25519-dalek's autopkgtests are failing in 3 places. The failing autopkgtests are preventing migration to Testing. https://qa.debian.org/excuses.php?package=rust-curve25519-dalek error: none of the selected packages contains these features: fiat_backend error: none of the selected packages contains these features: bench error[E0412]: cannot find type `StaticSecret` in this scope Thank you, Jeremy Bícha
Bug#1071528: ITP: hardinfo2 -- Hardinfo2 offers System Information and Benchmark for Linux Systems
On Mon, May 20, 2024 at 11:09 AM Lucas Castro wrote: > Package: wnpp > Severity: wishlist > Owner: Lucas Castro > X-Debbugs-Cc: debian-de...@lists.debian.org > > * Package name: hardinfo2 > Version : 2.1.2 > Upstream Contact: Name > * URL : https://hardinfo2.org/ > * License : GPL-2 > Programming Lang: C > Description : Hardinfo2 offers System Information and Benchmark for > Linux Systems > > Hardinfo2 is based on hardinfo, which have not been released >10 years. > Hardinfo2 is the reboot that was needed. > > Hardinfo2 offers System Information and Benchmark for Linux Systems. It is > able to > obtain information from both hardware and basic software. It can benchmark > your system and compare > to other machines online. > > Features include: > - Report generation (in either HTML or plain text) > - Online Benchmarking - compare your machine against other machines > > Status > -- > - Capabilities: Hardinfo2 currently detects most software and hardware > detected by the OS. > - Features: Online database for exchanging benchmark results. > - Development: Currently done by contributors, hwspeedy maintains > > Hardinfo2 is based on hardinfo, which have not been released >10 years. > Hardinfo2 is the reboot that was needed. Please see https://bugs.debian.org/1071373 (ITS: hardinfo) and coordinate with Boyuan Yang on updating hardinfo. Thank you, Jeremy Bícha
Bug#1071537: rust-snow: autopkgtest failures
Source: rust-snow Version: 0.9.6-4 Severity: serious rust-snow's autopkgtest is still failing which prevents migration to Testing. https://qa.debian.org/excuses.php?package=rust-snow Excerpt -- error[E0599]: no function or associated item named `new` found for struct `snow::Builder` in the current scope --> tests/vectors.rs:151:37 | 151 | let mut init_builder = Builder::new(params.clone()); | ^^^ function or associated item not found in `Builder<'_>` Thank you, Jeremy Bícha
Bug#1071517: hardinfo: Unnecessary Build-Depends libsoup2.4
Package: hardinfo Version: 0.5.1+git20180227-2.1 Severity: important Tags: trixie sid User: pkg-gnome-maintain...@lists.alioth.debian.org Usertags: libsoup2 X-Debbugs-CC: by...@debian.org hardinfo has Build-Depends: libsoup2.4-dev but doesn't use libsoup at all. I checked with rgrep -i soup Thank you, Jeremy Bícha
Bug#1071514: RM: qpdfview [i386] -- RoM; NBS; no reverse dependencies
Package: ftp.debian.org User: ftp.debian@packages.debian.org Usertags: remove X-Debbugs-Cc: qpdfv...@packages.debian.org Control: affects -1 src:qpdfview poppler's qt6 bindings are no longer built on i386. This means that qpdfview is no longer buildable on i386; therefore, please remove qpdfview from i386. qpdfview has no reverse dependencies, but both lqxt and xfe have Recommends: qpdfview. Please let me know if we need to update those packages to drop the Recommends on i386. I got approval from Debian's qpdfview maintainer Louis-Philippe Véronneau before filing this bug. Thank you, Jeremy Bícha
Bug#1071513: RM: photoqt [i386] -- RoQA; NBS; no reverse dependencies
Package: ftp.debian.org User: ftp.debian@packages.debian.org Usertags: remove X-Debbugs-Cc: phot...@packages.debian.org Control: affects -1 src:photoqt poppler's qt6 bindings are no longer built on i386. This means that photoqt is no longer buildable on i386; therefore, please remove photoqt from i386. photoqt has no reverse dependencies. Thank you, Jeremy Bícha
Bug#1071253: rust-snow: autopkgtest failures
Control: retitle -1 rust-snow: autopkgtest failures rust-snow builds now but its autopkgtests fail which blocks migration to Testing. I saw this in a brief look at the autopkgtest log but there may be other errors: error: no matching package named `aes-gcm` found https://qa.debian.org/excuses.php?package=rust-snow Thank you, Jeremy Bícha
Bug#1071259: foxtrotgps: Unnecessary Build-Depends libsoup2.4
Patch attached Thank you, Jeremy Bícha From: Jeremy Bicha Date: Fri, 17 May 2024 12:15:28 +0200 Subject: Drop obsolete Build-Depends: libsoup2.4-dev Closes: #1071259 --- debian/control | 1 - 1 file changed, 1 deletion(-) diff --git a/debian/control b/debian/control index 6281f17..6759913 100644 --- a/debian/control +++ b/debian/control @@ -13,7 +13,6 @@ Build-Depends: libglade2-dev, libgps-dev, libgtk2.0-dev, - libsoup2.4-dev, libsqlite3-dev, libxml2-dev, texinfo,
Bug#1071259: foxtrotgps: Unnecessary Build-Depends libsoup2.4
Package: foxtrotgps Version: 1.2.2+bzr332-1 Severity: important Tags: trixie sid patch User: pkg-gnome-maintain...@lists.alioth.debian.org Usertags: libsoup2 foxtrotgps has Build-Depends: libsoup2.4-dev but doesn't use libsoup at all. I checked with rgrep -i soup foxtrotgps uses Beautiful Soup (python3-bs4) which is different than libsoup. In my follow-up email, I am attaching a patch to fix this issue Thank you, Jeremy Bícha
Bug#1071252: rust-libp2p-identity: fails to build
Source: rust-libp2p-identity
Version: 0.2.8+ds-4
Severity: serious
Tags: ftbfs
rust-libsp2p-identity fails to build from source in Unstable because
of a build test error:
https://buildd.debian.org/status/package.php?p=rust-libp2p-identity
Running
`/<>/target/x86_64-unknown-linux-gnu/release/deps/keypair_api-0ab69a7110130a15`
running 1 test
test calling_keypair_api ... FAILED
failures:
calling_keypair_api stdout
thread 'calling_keypair_api' panicked at 'internal error: entered
unreachable code', identity/src/keypair.rs:329:9
stack backtrace:
0: rust_begin_unwind
at /usr/src/rustc-1.70.0/library/std/src/panicking.rs:578:5
1: core::panicking::panic_fmt
at /usr/src/rustc-1.70.0/library/core/src/panicking.rs:67:14
2: core::panicking::panic
at /usr/src/rustc-1.70.0/library/core/src/panicking.rs:117:5
3: libp2p_identity::keypair::Keypair::from_protobuf_encoding
at ./src/keypair.rs:329:9
4: keypair_api::calling_keypair_api
at ./tests/keypair_api.rs:5:13
5: keypair_api::calling_keypair_api::{{closure}}
at ./tests/keypair_api.rs:4:26
6: core::ops::function::FnOnce::call_once
at /usr/src/rustc-1.70.0/library/core/src/ops/function.rs:250:5
7: core::ops::function::FnOnce::call_once
at /usr/src/rustc-1.70.0/library/core/src/ops/function.rs:250:5
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a
verbose backtrace.
Thank you,
Jeremy Bícha
Bug#1071253: rust-snow: Fails to build, missing crate x25519_dalek
Source: rust-snow Version: 0.9.6-2 Tags: ftbfs rust-snow fails to build in Unstable. This is an excerpt from the build log: https://buildd.debian.org/status/package.php?p=rust-snow error[E0432]: unresolved import `x25519_dalek` --> tests/general.rs:13:5 | 13 | use x25519_dalek as x25519; | ^^ no external crate `x25519_dalek` Thank you, Jeremy Bícha
Bug#1071250: rust-imap-codec: Fails to build: error: no matching package named `libfuzzer-sys` found
Source: rust-imap-codec Version: 1.0.0-2 Severity: serious Tags: ftbfs rust-imap-codec fails to build from source in Unstable. This line shows in its build log: error: no matching package named `libfuzzer-sys` found https://buildd.debian.org/status/package.php?p=rust-imap-codec Thank you, Jeremy Bícha
Bug#1061179: Bug#1060019: transition: poppler 24.02
libpoppler134 has migrated to Testing and I don't see libpoppler126 there any more so I'm closing the poppler transition bug. Thank you, Jeremy Bícha
Bug#1071141: gnome-remote-desktop: `/usr/lib/tmpfiles.d/gnome-remote-desktop-tmpfiles.conf:2: Failed to resolve user 'gnome-remote-desktop': No such process`
On Wed, May 15, 2024 at 7:51 AM Paul Menzel wrote: > gnome-remote-desktop (46.1-3) wird eingerichtet ... > /usr/lib/tmpfiles.d/gnome-remote-desktop-tmpfiles.conf:2: Failed to > resolve user 'gnome-remote-desktop': No such process > /usr/lib/tmpfiles.d/gnome-remote-desktop-tmpfiles.conf:3: Failed to > resolve user 'gnome-remote-desktop': No such process > Creating group 'gnome-remote-desktop' with GID 987. > > The failure lines were printed in red. Yes, I am tracking this in https://bugs.debian.org/1070119 and https://bugs.debian.org/1070473 Thank you, Jeremy Bícha
Bug#1070119: gnome-remote-desktop: missing gnome-remote-desktop user setup in salsa upcoming 46 version
Control: reopen -1 Control: retitle -1 gnome-remote-desktop: long delay when first installing version 46 Control: block 1050237 by -1 I'm not happy with the performance of what I've implemented because it still has the 90 second delay even though gnome-remote-desktop is otherwise working now. See also https://bugs.debian.org/1070473 Thank you, Jeremy Bícha
Bug#1070862: poppler: possibly unintended revert of t64 renames for non-main library in 24.x
Control: severity -1 serious On Fri, May 10, 2024 at 1:48 PM Simon McVittie wrote: > Please bump this up to RC if analysis shows that it is a genuine problem, > or close it if analysis shows that I'm being overly cautious. I think it is appropriate to bump this to RC. I will try to get this upload done by tomorrow; I'm in the midst of a busy travel week. Thank you, Jeremy Bícha
Bug#1070836: rust-apple-nvram: Switch from rust-nix 0.26 to 0.27
Source: rust-apple-nvram Version: 0.2.0-1 Severity: serious Tags: ftbfs upstream sid X-Debbugs-CC: andr...@fatal.se rust-apple-nvram Depends and Build-Depends: rust-nix 0.26 but Unstable has rust-nix 0.27 instead. I tried doing a simple version bump from 0.26 to 0.27 in the package but dh_auto_test failed. Thank you, Jeremy Bícha
Bug#1070405: darktable: Please drop unused Build-Depends: libsoup2.4-dev
On Mon, May 6, 2024 at 2:46 PM David Bremner wrote: > > Jeremy Bícha writes: > > > Source: darktable > > Version: 4.6.1-2 > > > > Please drop Build-Depends: libsoup2.4-dev . It isn't used at all and > > we would eventually like to remove libsoup2.4 from Debian. > > > > Thank you, > > Jeremy Bícha > > How can I verify that it is not used? rgrep -i soup Also: https://github.com/darktable-org/darktable/commit/228fcf0041773 Thank you, Jeremy Bícha
Bug#1070644: gnome-remote-desktop: System .service file enabled but not the user one?
Control: forwarded -1 https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/merge_requests/260 It looks like upstream is proposing to split gnome-remote-desktop's new systemd systemd service into two system services to fix this issue. It's unclear whether they will land this in 46.x Thank you, Jeremy Bícha
Bug#1070644: gnome-remote-desktop: System .service file enabled but not the user one?
Control: severity -1 serious On Mon, May 6, 2024 at 11:03 AM Laurent Bigonville wrote: > > Package: gnome-remote-desktop > Version: 46.1-3 > Severity: normal > > Hello, > > It seems that the system systemd .service is enabled at boot, while the > user one is not. > > Any reason why the former is enabled and the later is not? > > Not sure I see the rational here That could be a critical bug so I'm bumping the severity. I think the service ought not run unless it is enabled and it shouldn't be enabled by default. (There is GUI in gnome-control-center to enable it but that GUI is patched out for Unstable.) Thank you, Jeremy Bícha
Bug#1070473: debhelper: Run dh_installsysusers after dh_installtmpfiles
On Mon, May 6, 2024 at 7:33 AM Luca Boccassi wrote: > Am I reading this correctly, that the package is using tmpfiles to > create a home directory? I'm not sure that was foreseen as a use case > to be honest, I'd bring it upstream Yes. Should I bring the issue upstream to systemd or upstream to gnome-remote-desktop? Thank you, Jeremy Bícha
Bug#1070473: debhelper: Run dh_installsysusers after dh_installtmpfiles
On Mon, May 6, 2024 at 2:06 AM Niels Thykier wrote: > > 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? There is a circular dependency here. $ cat /usr/lib/tmpfiles.d/gnome-remote-desktop-tmpfiles.conf # tmpfiles.d file to ensure the existence of the home directory for gnome-remote-desktop user d /var/lib/gnome-remote-desktop 0700 gnome-remote-desktop gnome-remote-desktop d /etc/gnome-remote-desktop 0755 gnome-remote-desktop gnome-remote-desktop $ cat /usr/lib/sysusers.d/gnome-remote-desktop-sysusers.conf # sysusers.d file to ensure the existence of the gnome-remote-desktop user u gnome-remote-desktop - "GNOME Remote Desktop" /var/lib/gnome-remote-desktop The 90 second hang if systemd-sysusers is run before /var/lib/gnome-remote-desktop exists is annoying, but systemd-tmpfiles errors if the gnome-remote-desktop user doesn't exist yet. Running tmpfiles, then sysusers, then tmpfiles again works except for that 90 second hang. I had to remove the gnome-remote-desktop package, then remove the gnome-remote-desktop user and the directories and then reboot to test changes properly. Thank you, Jeremy Bícha
Bug#1070463: gnome-remote-desktop: 46 has failing build tests
Control: severity -1 important Control: unblock 1050237 by -1 On Sun, May 5, 2024 at 1:15 PM Jeremy Bícha wrote: > The build tests were passing with version 45. It is not clear to me > why the tests are failing in Debian Experimental but passing in Ubuntu > 24.04 LTS. I have ignored gnome-remote-desktop's test failures for now in Debian since it is a higher priority to land GNOME Shell 46 in Testing. Maybe there is a missing dependency and getting more things in Unstable would help. Thank you, Jeremy Bícha
Bug#1070473: debhelper: Run dh_installsysusers after dh_installtmpfiles
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
Bug#1053866: transition: jpeg-xl
Control: block -1 by 1061627 I was able to build all the reverse dependencies in Ubuntu 24.04 LTS against jpeg-xl from experimental. But jpeg-xl won't be able to migrate to Testing until its autopkgtests are fixed. https://release.debian.org/britney/pseudo-excuses-experimental.html#jpeg-xl See the blocking bug. Thank you, Jeremy Bícha
Bug#1060019: transition: poppler 24.02
Control: retitle -1 transition: poppler 24.02 Control: affects -1 src:poppler Since originally requesting this transition, I have updated the version to 24.02. I believe all reverse dependencies can be binNMU'd for this. Thank you, Jeremy Bícha
Bug#1070119: gnome-remote-desktop: missing gnome-remote-desktop user setup in salsa upcoming 46 version
On Sun, May 5, 2024 at 2:51 PM Jeremy Bícha wrote: > Where did you get gnome-remote-desktop 46.1-1_amd64.deb from? It has > not been successfully built on Debian's buildds yet. Oh, I guess it was mentioned in your bug title: you built it from Salsa. Thank you, Jeremy Bícha
Bug#1070119: gnome-remote-desktop: missing gnome-remote-desktop user setup in salsa upcoming 46 version
Where did you get gnome-remote-desktop 46.1-1_amd64.deb from? It has not been successfully built on Debian's buildds yet. Thank you, Jeremy Bícha
Bug#1070463: gnome-remote-desktop: 46 has failing build tests
Source: gnome-remote-desktop Version: 46.1-1 Severity: serious Tags: ftbfs experimental Control: block 1050237 by -1 X-Debbugs-CC: ma...@ubuntu.com gnome-remote-desktop's build tests are failing. This is blocking the GNOME Shell 46 transition since GNOME Shell & GNOME Remote Desktop should have the same major version, at least while the projects are under heavy development. The build tests were passing with version 45. It is not clear to me why the tests are failing in Debian Experimental but passing in Ubuntu 24.04 LTS. Thank you, Jeremy Bícha
Bug#1070462: transition: evolution-data-server 3.52
Package: release.debian.org User: release.debian@packages.debian.org Usertags: transition X-Debbugs-Cc: evolution-data-ser...@packages.debain.org One of the evolution-data-server libraries had a soname bump. I believe everything should be binNMUable without issue. This tracker is good: https://release.debian.org/transitions/html/auto-evolution-data-server.html On behalf of the Debian GNOME team, Jeremy Bicha
Bug#1070348: pipewire: pipewire-pulse: warningin syslog every second for snap_get_audio_permissions
On Sat, May 4, 2024 at 4:00 AM Dylan Aïssi wrote: > > Hello Sergio and Jeremy, > > Le sam. 4 mai 2024 à 05:48, Michael Welsh Duggan a écrit : > > > > After updating my linux kernel to 6.7.12-1, I keep getting the following > > message in my syslog, once a second: > > > > pipewire-pulse[]: default: snap_get_audio_permissions: kernel lacks > > 'fine grained unix mediation'; snap audio permissions won't be honored. > > > > It seems that snap support in pipewire requires a kernel feature > (fine grained unix mediation) that is not yet enabled in Debian. > > I'm thinking of disabling for now the snap support in Debian since > there is no point in keeping it enabled if it's unusable. But, I will > keep it enabled for Ubuntu. What do you think? That makes sense to me. Thank you, Jeremy Bícha
Bug#1063026: helvum: Upcoming gtk update
Control: severity -1 serious Control: tags -1 + ftbfs Jonas, the Rust GTK crates were uploaded to Unstable today. Could you upload your helvum package from Experimental to Unstable? Thank you, Jeremy Bícha
Bug#1070405: darktable: Please drop unused Build-Depends: libsoup2.4-dev
Source: darktable Version: 4.6.1-2 Please drop Build-Depends: libsoup2.4-dev . It isn't used at all and we would eventually like to remove libsoup2.4 from Debian. Thank you, Jeremy Bícha
Bug#1070404: srain: Please update to 1.7.0
Source: srain Version: 1.7.0 Severity: wishlist Please update srain to 1.7.0. One detail I am interested in is that it switches from libsoup2.4 to libsoup3. https://github.com/SrainApp/srain/releases Thank you, Jeremy Bícha
Bug#1070399: RM: pmix [armel armhf i386] -- RoQA; NBS; no arch-specific reverse dependencies
Package: ftp.debian.org User: ftp.debian@packages.debian.org Usertags: remove X-Debbugs-Cc: p...@packages.debian.org Control: affects -1 src:pmix Please remove pmix on 32-bit architectures. It is no longer built there and its only reverse dependency, openmpi has already been updated to only use pmix on 64-bit architectures. This will allow several packages to migrate from Unstable to Testing (it is one of the blockers for gst-plugins-bad1.0). Thank you, Jeremy Bícha
Bug#1034878: #1034878 meld gives python traceback if run as root
Control: forwarded -1 https://gitlab.gnome.org/GNOME/meld/-/issues/846 Control: severity -1 minor On Sat, May 4, 2024 at 8:42 AM wrote: > Bug #1034878 - meld gives python traceback if run as root is caused by the > call to Gtk.Settings.get_default() in settings.py at about line 56. In general, GNOME developers and the Debian GNOME team don't want you running apps as root/sudo. We do expect some things to be broken if you try it anyway. However, you can try raising this issue directly with the upstream meld developers who may be willing to apply a fix for the issue. I notice that someone already reported a similar issue today but maybe you can add a comment with your additional research. https://gitlab.gnome.org/GNOME/meld/-/issues/846 Thank you, Jeremy Bícha
Bug#1067169: gnome-control-center: Disable location services?
On Thu, Apr 18, 2024 at 10:33 AM Arnaud Ferraris wrote: > TBH I would prefer it if those services were kept enabled in Debian, as > those are useful to mobile users. Moreover, it seems an alternative to > MLS is being worked on, although I don't know what its current status > is, nor whether it'll be live before MLS goes down. But if it's ready > soon enough (that's a big "if", granted), then g-c-c will likely need a > small patch to switch to it, without user-visible disruption. Thank you for your reply. After further consideration, both Ubuntu 24.04 LTS and Fedora 40 have re-enabled location service settings in gnome-control-center for now. Therefore, I have kept location services enabled in Debian Unstable too. https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/3032 Jeremy Bícha
Bug#1070323: RM: gnome-shell-extension-bluetooth-quick-connect -- RoM; unmaintained, obsolete with gnome-shell 45
The new upstream project is https://github.com/Extensions-Valhalla/gnome-bluetooth-quick-connect Thank you, Jeremy Bícha
Bug#1052090: gnome-shell-extension-bluetooth-quick-connect: needs update for GNOME Shell 45
On Sun, Sep 17, 2023 at 9:33 AM Simon McVittie wrote: > I don't intend to put time into this change myself, because I no longer > use this extension (see #1043008), so I'm marking this as serious already > (justification: "in the package maintainer's opinion, makes the package > unsuitable for release"). If anyone else in the GNOME team wants to see > this extension stay available in Debian, now is your chance to take over > the package, at which point the severity of this bug becomes your choice. > > If nobody steps up to maintain it, I will ask for this extension to be > removed when we are ready for the GNOME Shell 45 transition. Simon, I filed the removal bug. I haven't really seen complaints during the 6 months that the extension was removed from Testing. The upstream project was archived. However I noted in the removal bug, that there is a fork: https://github.com/Extensions-Valhalla/gnome-bluetooth-quick-connect But the fork switched to TypeScript which might make it difficult to package for Debian main. Thank you, Jeremy Bícha
Bug#1070323: RM: gnome-shell-extension-bluetooth-quick-connect -- RoM; unmaintained, obsolete with gnome-shell 45
Package: ftp.debian.org User: ftp.debian@packages.debian.org Usertags: remove X-Debbugs-Cc:gnome-shell-extension-bluetooth-quick-conn...@packages.debian.org Control: affects -1 src:gnome-shell-extension-bluetooth-quick-connect Please remove gnome-shell-extension-bluetooth-quick-connect from Debian. It is no longer maintained upstream: https://github.com/bjarosze/gnome-bluetooth-quick-connect Its functionality has basically been incorporated into GNOME Shell 45 which we intend to land in Unstable soon after the t64 transition completes. There does happen to be a forked version but it uses TypeScript. I've not looked closely at that version but in my experience, GNOME Typescript packages are difficult to package for Debian main. On behalf of the Debian GNOME Maintainers, Jeremy Bícha
Bug#1068123: Breaks phosh << 0.37.0-2
Control: severity -1 important On Sun, Mar 31, 2024 at 6:03 AM Guido Günther wrote: > gnome-session 46 dropped `--builtin` and `--systemd`. This breaks phosh < > 0.37.0-2. Would be great to have a proper `Breaks: ` relationship > to ease upgrades. I'm lowering the severity since phosh 0.38 landed in Testing today and it would be good for gnome-session to migrate also. But I can do another gnome-session upload soon. What exact gnome-session binary-package do you think we need to add the Breaks: to? I know that Budgie was also affected by the change; that's why budgie-session exists now. Thank you, Jeremy Bícha
Bug#1070269: bluez: Please update to 5.75
Source: bluez Version: 5.73-1 Severity: wishlist bluez 5.75 is available. Please update to it. Perhaps it helps https://bugs.debian.org/1069012 ? Also I submitted several merge requests for the Debian package at https://salsa.debian.org/bluetooth-team/bluez/-/merge_requests Thank you, Jeremy Bícha
Bug#1070250: telepathy-glib: Fails to build with glib 2.80
Source: telepathy-glib Severity: serious Version: 0.24.2-0.3 Tags: ftbfs upstream X-Debbugs-CC: bi...@debian.org Please cherry-pick the glib commit from https://gitlab.freedesktop.org/telepathy/telepathy-glib/-/commits/master to fix the build with glib 2.80 (currently in experimental but will be uploaded to Unstable as soon as the t64 transitions clear out). There is also a commit there to port examples from Python 2 to 3. Thank you, Jeremy Bícha
Bug#1070247: telepathy-glib: Fails to build with glib 2.80
Source: telepathy-glib Severity: serious Version: 0.24.2-0.3 Tags: ftbfs upstream X-Debbugs-CC: bi...@debian.org Please cherry-pick the glib commit from https://gitlab.freedesktop.org/telepathy/telepathy-glib/-/commits/master to fix the build with glib 2.80 (currently in experimental but will be uploaded to Unstable as soon as the t64 transitions clear out). There is also a commit there to port examples from Python 2 to 3. Thank you, Jeremy Bícha
Bug#1019042: [Pkg-rust-maintainers] Bug#1019042: rust-qwertone: FTBFS - dep issue
Control: severity -1 serious This issue is now RC since it's not possible to build qwertone on Unstable now. But I expect qwertone will get an upload to fix this issue within a few days. See https://salsa.debian.org/debian/qwertone/-/merge_requests/1 Thank you, Jeremy Bícha
Bug#1058652: RM: python-boto -- ROM; orphaned upstream, replaced by python-boto3
Control: tags -1 -moreinfo The reverse dependencies have been taken care of now. Thank you, Jeremy Bícha
Bug#1070186: python3-datalad: Don't recommend python3-boto
Package: python3-datalad Version: 0.19.6-2 Severity: serious Debian Policy § 2.2 says that packages in main (like python3-datalad) are not allowed to have Recommends on packages that are not in main (unless it is only a non-default alternative for a package in main). python3-datalad Recommends: python3-boto but python3-boto has been removed from Testing and will likely be removed from Unstable soon. See https://bugs.debian.org/1058652 The replacement is python3-boto3 but the package will likely need changes to upstream code to work with the new version. Thank you, Jeremy Bícha
Bug#1070119: gnome-remote-desktop: missing gnome-remote-desktop user setup in salsa upcoming 46 version
On Tue, Apr 30, 2024 at 11:29 AM Alban Browaeys wrote: > So I did not mean mixinf gnome-shell/gnome-remote-desktop version. My > interest was into connection via RDP to a not unlocked or already > opened remote Gnome Shell. > > As of now I us the "Allow Locked Remote Desktop" extension and gdm3 > autologin on the remote gnome shell user session. > I would like to get rid of these hacks (especially since I have to set > an empty password on my gnome keyring for such a setup). Well you'll also need gnome-control-center built without the "revert the remote desktop changes" patch. Our priority is to get the t64 transitions migrated to Testing, then upload GNOME Shell 46 to Unstable (with Release Team permission). The Debian GNOME team may not have time or interest in maintaining two versions of gnome-control-center for people trying to use Remote Login right now. Thank you, Jeremy Bícha
Bug#1070119: gnome-remote-desktop: missing gnome-remote-desktop user setup in salsa upcoming 46 version
Control: severity -1 important On Tue, Apr 30, 2024 at 9:57 AM Alban Browaeys wrote: > The issue seems to be that the user gnome-remote-desktop is not existing > thus the system wide systemd gnome-remote-desktop.service fails to > start: The gnome-remote-desktop user is new for gnome-remote-desktop 46. The user ought to be created by the package and it seems to work for Ubuntu 24.04 LTS (which uses the same packaging). > I found no issue tracker on the salsa project for gnome-remote-desktop > so opened the issue here. I wouldn't open an upstream bug for this issue yet since we should assume this is a Debian packaging issue until confirmed otherwise. > I believe the bug is import as it prevents opening a new desktop session > (but it still works when connection to an existing session). Yes, I've bumped the severity but what do you mean about connecting to an existing session? It's not intended to run, for instance, gnome-remote-desktop 45 with gnome-shell 46 or with gnome-shell 44 but I guess the package dependencies aren't set quite that strict. Thank you, Jeremy Bícha
Bug#1070094: RM: rust-gtk3-macros -- RoM; unmaintained library
Package: ftp.debian.org User: ftp.debian@packages.debian.org Usertags: remove X-Debbugs-Cc: rust-gtk3-mac...@packages.debian.org Control: affects -1 src:rust-gtk3-macros Please remove rust-gtk3-macros from Debian. It is part of the Rust GTK3 stack that is no longer maintained and is incompatible with the Rust GNOME 46 packages. https://bugs.debian.org/1064375 On behalf of the Debian Rust Maintainers, Jeremy Bícha
Bug#1070093: RM: rust-gdk-sys -- RoM; unmaintained library
Package: ftp.debian.org User: ftp.debian@packages.debian.org Usertags: remove X-Debbugs-Cc: rust-gdk-...@packages.debian.org Control: affects -1 src:rust-gdk-sys Please remove rust-gdk-sy from Debian. It is part of the Rust GTK3 stack that is no longer maintained and is incompatible with the Rust GNOME 46 packages. https://bugs.debian.org/1064375 On behalf of the Debian Rust Maintainers, Jeremy Bícha
Bug#1070091: RM: rust-gdk -- RoM; unmaintained library
Package: ftp.debian.org User: ftp.debian@packages.debian.org Usertags: remove X-Debbugs-Cc: rust-...@packages.debian.org Control: affects -1 src:rust-gdk Please remove rust-gdk from Debian. It is part of the Rust GTK3 stack that is no longer maintained and is incompatible with the Rust GNOME 46 packages. https://bugs.debian.org/1064375 On behalf of the Debian Rust Maintainers, Jeremy Bícha
Bug#1070092: RM: rust-gtk -- RoM; unmaintained library
Package: ftp.debian.org User: ftp.debian@packages.debian.org Usertags: remove X-Debbugs-Cc: rust-...@packages.debian.org Control: affects -1 src:rust-gtk Please remove rust-gtk from Debian. Rust GTK3 is no longer maintained and is incompatible with the Rust GNOME 46 packages. https://bugs.debian.org/1064375 On behalf of the Debian Rust Maintainers, Jeremy Bícha
Bug#1070090: RM: rust-gdkx11- RoM; unmaintained library
Package: ftp.debian.org User: ftp.debian@packages.debian.org Usertags: remove X-Debbugs-Cc: rust-gdk...@packages.debian.org Control: affects -1 src:rust-gdkx11 Please remove rust-gdkx11 from Debian. It is part of the Rust GTK3 stack that is no longer maintained and is incompatible with the Rust GNOME 46 packages. https://bugs.debian.org/1064375 On behalf of the Debian Rust Maintainers, Jeremy Bícha
Bug#1070086: RM: rust-gtk-sys -- RoM; unmaintained library
Package: ftp.debian.org User: ftp.debian@packages.debian.org Usertags: remove Tags: moreinfo X-Debbugs-Cc: rust-gtk-...@packages.debian.org Control: affects -1 src:rust-gtk-sys Control: block -1 by 1064373 Please remove rust-gtk-sys from Debian. It is part of the Rust GTK3 stack that is no longer maintained and is incompatible with the Rust GNOME 46 packages. https://bugs.debian.org/1064375 On behalf of the Debian Rust Maintainers, Jeremy Bícha
Bug#1070089: RM: rust-gdkx11-sys-- RoM; unmaintained library
Package: ftp.debian.org User: ftp.debian@packages.debian.org Usertags: remove X-Debbugs-Cc: rust-gdkx11-...@packages.debian.org Control: affects -1 src:rust-gdkx11-sys Please remove rust-gdkx11-sys from Debian. It is part of the Rust GTK3 stack that is no longer maintained and is incompatible with the Rust GNOME 46 packages. https://bugs.debian.org/1064375 On behalf of the Debian Rust Maintainers, Jeremy Bícha
Bug#1070088: RM: rust-atk-sys -- RoM; unmaintained library
Package: ftp.debian.org User: ftp.debian@packages.debian.org Usertags: remove X-Debbugs-Cc: rust-atk-...@packages.debian.org Control: affects -1 src:rust-atk-sys Please remove rust-atk-sys from Debian. It is part of the Rust GTK3 stack that is no longer maintained and is incompatible with the Rust GNOME 46 packages. https://bugs.debian.org/1064375 On behalf of the Debian Rust Maintainers, Jeremy Bícha
Bug#1070087: RM: rust-atk -- RoM; unmaintained library
Package: ftp.debian.org User: ftp.debian@packages.debian.org Usertags: remove X-Debbugs-Cc: rust-...@packages.debian.org Control: affects -1 src:rust-atk Please remove rust-atk from Debian. It is part of the Rust GTK3 stack that is no longer maintained and is incompatible with the Rust GNOME 46 packages. https://bugs.debian.org/1064375 On behalf of the Debian Rust Maintainers, Jeremy Bícha
Bug#1070080: remmina: check old releases for compatibility with freerdp2 security updates
Source: remmina Version: 1.3.3+dfsg-2 Severity: important Tags: security I noticed that the Ubuntu Security Team updated remmina in Ubuntu 20.04 LTS to make it compatible with the freerdp2 security update they pushed a few days ago. Perhaps similar coordinated uploads need to happen for old Debian releases. https://launchpad.net/ubuntu/+source/remmina/1.4.25+dfsg-0ubuntu0.20.04.1 https://ubuntu.com/security/notices/USN-6752-1 Thank you, Jeremy Bícha
Bug#1070078: remmina: please build with freerdp3
Source: remmina Version: 1.4.35+dfsg-1 Severity: wishlist Please build remmina with freerdp3 now that it's available in Unstable. If you do that, you'll need to also cherrypick the fix from https://gitlab.com/Remmina/Remmina/-/merge_requests/2579 which is being tracked in Ubuntu 24.04 LTS as https://launchpad.net/bugs/2062177 (since Ubuntu switched to freerdp3 early). Thank you, Jeremy Bícha
Bug#1070057: mutter: Severe keyboard input lag/pauses
On Mon, Apr 29, 2024 at 8:42 AM Florian Cramer wrote: > Package: mutter > Version: 46.0-1 > Severity: important > X-Debbugs-Cc: flrnc...@gmail.com > > Dear Maintainer, > > In all programs that rely on mutter and/or Gnome/GTK libraries for keyboard > input, I am experiencing severe keyboard input lag/pauses, sometimes for > several seconds. This might be a problem that only occurs in xorg with the > Nvidia driver, and is identical to what has been described here: > https://gitlab.gnome.org/GNOME/mutter/-/issues/3384 I believe this is fixed in mutter 46.1 which I have just uploaded to Experimental. Could you update to that version when it's available and see if the problem goes away after you restart your computer? Thank you, Jeremy Bícha
Bug#1066797: gstreamer1.0: FTBFS: tests/check/libs/gstharness.c: Received signal 11 (Segmentation fault)
Control: severity -1 important This build failure does not appear to be reproducible on the official buildds and this RC bug is blocking big parts of the t64 transitions so I'm lowering the severity. Thank you, Jeremy Bícha
Bug#1069952: upgrade from 2.78.4-1 to 2.78.4-7 breaks over 200 packages in testing distribution
On Sat, Apr 27, 2024 at 9:33 AM js wrote: >Wanted to see the effect of upgrading libglib2.0-dev by a minor >version number, 2.78.4-1 to 2.78.4-7 and that would have caused over >200 packages to break in the **testing** distribution. Try sudo apt dist-upgrade It is not a "minor" update. It is part of the t64 transition which is a huge change. Thank you, Jeremy Bícha
Bug#1069415: libsoup2.4: FTBFS on arm64: dh_auto_test: error: cd obj-aarch64-linux-gnu && DEB_PYTHON_INSTALL_LAYOUT=deb LC_ALL=C.UTF-8 MESON_TESTTHREADS=4 meson test returned exit code 29
On Wed, Apr 24, 2024 at 5:04 PM Santiago Vila wrote: > > Jeremy Bícha wrote: > > It was also marked as severity important instead of RC because it does not > > affect official buildds. > > Not true: > > https://buildd.debian.org/status/logs.php?pkg=libsoup2.4=all > > See also: > > https://buildd.debian.org/status/logs.php?pkg=gcr=all > > and also: > > https://buildd.debian.org/status/logs.php?pkg=gcr4=amd64 > > And regardless of the severity of the day, you were *explicitly* asked > by Sebastian Ramacher to disable *or* fix the flaky tests: > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057562#17 > > Note that it's "or", nobody is asking you to act heroically and spend a time > that you don't have. We just want to build the packages without random > failures, > and for that it's enough to disable the tests that we know to be broken. > It can't be so much difficult. I believe you are thinking about https://bugs.debian.org/1057562 The issue I am talking about now is https://bugs.debian.org/1064744 which is different and one I that I don't recall you or Sebastian interacting with me on. Also, whatever affects libsoup2.4/all on those builds is different as its test failures are different that what was reported here or at 1064744. There isn't currently a Debian bug for that issue. Thank you, Jeremy Bícha
Bug#1057562: closed by Debian FTP Masters (reply to Jeremy Bícha ) (Bug#1057562: fixed in gcr4 4.2.0-2)
On Tue, Apr 23, 2024 at 11:00 AM Colin Watson wrote: > I've been attempting to debug this on an AWS instance provided by > Santiago. So far I'm afraid I can only report some partial progress, > but I might as well write down what I've got so far. Colin, thanks for looking into this issue. It also affects source gcr (which is just the older version of gcr4). If you have time, feel free to forward this issue to https://gitlab.gnome.org/GNOME/gcr/-/issues/ Jeremy Bícha
Bug#1069631: loki-ecmwf: Unsatisfiable dependency: python3-loki etc
Source: loki-ecmwf Version: 0.2.0-1 Severity: serious After https://salsa.debian.org/science-team/loki-ecmwf/-/commit/fd228e81dcb, python3-loki-ecmwf-lint-rules has Depends: python3-loki but that package is not available in Debian. https://qa.debian.org/excuses.php?package=loki-ecmwf complains about other uninstallable packages but I did not check them. Thank you, Jeremy Bícha
Bug#1069624: rapidfuzz: Fails to build on arch: all
Source: rapidfuzz Version: 3.6.2+ds-2 Severity: serious Tags: ftbfs The arch: all build for rapidfuzz is failing: https://buildd.debian.org/status/package.php?p=rapidfuzz If you use sbuild, I believe you can test this with sbuild -arch-all --no-arch-any Thank you, Jeremy Bícha
Bug#1069621: rust-event-listener: no-default-features autopkgtest fails
Simple patch attached. Thank you, Jeremy Bícha From: Jeremy Bicha Date: Sun, 21 Apr 2024 13:37:18 -0400 Subject: [PATCH] Mark no-default-features autopkgtest as flaky Closes: #1069621 --- debian/tests/control | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/debian/tests/control b/debian/tests/control index e97cdaa..e5008bc 100644 --- a/debian/tests/control +++ b/debian/tests/control @@ -18,7 +18,7 @@ Depends: librust-futures-lite-1+default-dev, librust-try-lock-0.2+default-dev, librust-waker-fn-1+default-dev, -Restrictions: allow-stderr +Restrictions: allow-stderr, flaky Test-Command: /usr/share/cargo/bin/cargo-auto-test event-listener 5.3.0 --all-targets
Bug#1069621: rust-event-listener: no-default-features autopkgtest fails
Source: rust-event-listener Version: 5.3.0-2 Severity: serious Tags: experimental patch X-Debbugs-CC: werdah...@riseup.net rust-event-listener's --no-default-features autopkgtest is failing: https://ci.debian.net/packages/r/rust-event-listener/unstable/amd64/ This issue will block the rust-event-listener transition. I suggest marking the autopkgtest as flaky and reporting the issue upstream. Thank you, Jeremy Bícha
Bug#1069618: rust-process-viewer: Fails to build with rust-gtk4 0.8
Source: rust-process-viewer Version: 0.5.8-4 Severity: important Forwarded: https://github.com/GuillaumeGomez/process-viewer/pull/206 Tags: ftbfs The Debian Rust team will update rust-gtk4 from 0.7 to 0.8 soon. rust-process-viewer is not yet compatible with rust-gtk4 0.8. I started on the porting but I don't expect to work on this more. Thank you, Jeremy Bícha
Bug#1061421: Fails to start after an upgrade
On Sun, Apr 21, 2024 at 2:36 AM Arto Jantunen wrote: > > Jeremy Bícha writes: > > Please verify whether wlgreet is working for you now. > > Was something changed somewhere? What, where? > > On trixie the issue reproduces exactly the same (even with sway upgraded > to the binNMU'd version from sid). There have been a huge amount of changes, but most of those changes were in Unstable and haven't reached Testing yet. Marc, there is a fix for sway 1.9 in wlgreet 0.5. Do you want to try if that improves anything here? Thank you, Jeremy Bícha
Bug#1069577: squeekboard: Please package 1.38.0
Source: squeekboard Version: 1.24.0-1 Severity: wishlist Control: affects -1 phosh-core Please package squeekboard 1.38.0. The phosh-core metapackage version 38 (in experimental) has Depends: squeekboard (>= 1.38.0) | phosh-osk-stub (>= 0.38.0) https://gitlab.gnome.org/World/Phosh/squeekboard/-/releases/v1.38.0 Thank you, Jeremy Bícha
Bug#1063026: helvum: Upcoming gtk update
On Sat, Apr 20, 2024 at 9:22 AM Jonas Smedegaard wrote: > Quoting Jeremy Bícha (2024-04-20 13:20:23) > > I am attaching patches to update helvum and would like to upload to > > Experimental. > > > > Jonas, the Salsa repo is a little jumbled. Could you push your > > pristine-tar branch? And update debian/latest to include your latest > > upload? > > Git repo are now unentangled. I did so by force-pushing and thereby > overriding most of your previous uncoordinated changes, Jeremy. > > Thanks for your contributing, but please coordinate ahead, especially > when introducing new upstream code is involved, since that is > particulary tricky to unentangle. Thank you. Would you like to upload these patches to Experimental now? Or do you want me to? Jeremy Bícha
Bug#1063026: helvum: Upcoming gtk update
I am attaching patches to update helvum and would like to upload to
Experimental.
Jonas, the Salsa repo is a little jumbled. Could you push your
pristine-tar branch? And update debian/latest to include your latest
upload?
Thank you,
Jeremy Bícha
From fd91245564f7b71a9f6e88106b425af56c15b0c1 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Jeremy=20B=C3=ADcha?=
Date: Sat, 20 Apr 2024 07:14:35 -0400
Subject: [PATCH 3/3] Update Build-Depends
---
debian/control | 11 ++-
1 file changed, 6 insertions(+), 5 deletions(-)
diff --git a/debian/control b/debian/control
index 5450b7e..0d0f4c2 100644
--- a/debian/control
+++ b/debian/control
@@ -7,13 +7,14 @@ Build-Depends:
debhelper-compat (= 13),
desktop-file-utils,
dh-cargo,
- librust-glib-0.18+default-dev,
- librust-glib-0.18+log-dev,
- librust-libadwaita-0.5+default-dev,
- librust-libadwaita-0.5+v1-3-dev,
+ librust-async-channel+default-dev,
+ librust-glib-0.19+default-dev,
+ librust-glib-0.19+log-dev,
+ librust-libadwaita-0.6+default-dev,
+ librust-libadwaita-0.6+v1-3-dev,
librust-log-0.4+default-dev,
librust-once-cell-1+default-dev,
- librust-pipewire-0.7+default-dev,
+ librust-pipewire-0.8+default-dev,
libstring-shellquote-perl,
meson,
Standards-Version: 4.6.2
--
2.43.0
From 189c8a94ab4dba723ae063c1ac43dafdc507f54c Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Jeremy=20B=C3=ADcha?=
Date: Fri, 19 Apr 2024 20:03:14 -0400
Subject: [PATCH 1/3] Cherry-pick several patches to switch to latest GNOME
Rust crates
Closes: #1063026
---
.../Update-to-latest-gtk-rs-crates.patch | 401 ++
debian/patches/Use-responsive-design.patch| 158 +++
...t-media.category-property-to-manager.patch | 28 ++
debian/patches/series | 6 +
...isplay-node-media-name-in-graph-view.patch | 304 +
...um-to-track-the-latest-pipewire0.8.0.patch | 300 +
debian/patches/use-AdwToolbarView.patch | 87
7 files changed, 1284 insertions(+)
create mode 100644 debian/patches/Update-to-latest-gtk-rs-crates.patch
create mode 100644 debian/patches/Use-responsive-design.patch
create mode 100644 debian/patches/pw-Set-media.category-property-to-manager.patch
create mode 100644 debian/patches/series
create mode 100644 debian/patches/ui-Display-node-media-name-in-graph-view.patch
create mode 100644 debian/patches/update-Helvum-to-track-the-latest-pipewire0.8.0.patch
create mode 100644 debian/patches/use-AdwToolbarView.patch
diff --git a/debian/patches/Update-to-latest-gtk-rs-crates.patch b/debian/patches/Update-to-latest-gtk-rs-crates.patch
new file mode 100644
index 000..1be6793
--- /dev/null
+++ b/debian/patches/Update-to-latest-gtk-rs-crates.patch
@@ -0,0 +1,401 @@
+From: Tom Wagner
+Date: Sat, 23 Mar 2024 11:51:04 +0100
+Subject: Update to latest gtk-rs crates
+
+(cherry picked from commit f32559511d5e950bf5fde965de47c9caec6eabba)
+---
+ Cargo.toml | 7 ++--
+ src/application.rs | 7 ++--
+ src/graph_manager.rs | 94 ++
+ src/main.rs| 2 +-
+ src/pipewire_connection/mod.rs | 38 -
+ src/ui/graph/port.rs | 4 +-
+ 6 files changed, 89 insertions(+), 63 deletions(-)
+
+diff --git a/Cargo.toml b/Cargo.toml
+index a9a220c..f839bfc 100644
+--- a/Cargo.toml
b/Cargo.toml
+@@ -15,11 +15,12 @@ categories = ["gui", "multimedia"]
+
+ [dependencies]
+ pipewire = "0.8.0"
+-adw = { version = "0.5", package = "libadwaita", features = ["v1_4"] }
+-glib = { version = "0.18", features = ["log"] }
++adw = { version = "0.6", package = "libadwaita", features = ["v1_4"] }
++glib = { version = "0.19", features = ["log"] }
++async-channel = "2.2"
+
+ log = "0.4.11"
+
+-once_cell = "1.7.2"
++once_cell = "1.19"
+
+ libc = "0.2"
+diff --git a/src/application.rs b/src/application.rs
+index 97aa21b..a40ac30 100644
+--- a/src/application.rs
b/src/application.rs
+@@ -16,7 +16,7 @@
+
+ use adw::{
+ gio,
+-glib::{self, clone, Receiver},
++glib::{self, clone},
+ gtk,
+ prelude::*,
+ subclass::prelude::*,
+@@ -33,8 +33,9 @@ static AUTHORS: = env!("CARGO_PKG_AUTHORS");
+ mod imp {
+ use super::*;
+
++use std::cell::OnceCell;
++
+ use adw::subclass::prelude::AdwApplicationImpl;
+-use once_cell::unsync::OnceCell;
+
+ #[derive(Default)]
+ pub struct Application {
+@@ -140,7 +141,7 @@ impl Application {
+ /// Create the view.
+ /// This will set up the entire user interface and prepare it for being run.
+ pub(super) fn new(
+-gtk_receiver: Receiver,
++gtk_receiver: async_channel::Receiver,
+ pw_sender: Sender,
+ ) -> Self {
+ let app: Application = glib::Object::builder()
+diff --git a/s
Bug#1068929: async-lock: Please update for event-listener 5.x
Control: block -1 by 1068930 You'll also need to bump the dependency on rust-async-channel to build against the version that was built for event-listener 5. Thank you, Jeremy Bícha
Bug#1067169: gnome-control-center: Disable location services?
On Tue, Mar 19, 2024 at 12:59 PM Jeremy Bícha wrote: > Mozilla has announced that it will be disabling third party access to > the Mozilla Location Service June 12. This is used via geoclue-2.0 to > provide a variety of services across Debian desktops, in particular in > gnome-control-center. > > GNOME has recently proposed a build option [1] to hide the > location-related settings in gnome-control-center. I'm told that > geoclue can also work with GPS so the settings might be useful for > people using Debian on mobile devices. However, I think we need to do > what's best for the vast majority of our users. I'm filing this issue > for awareness in case anyone wants to contribute alternate ways of > handling this situation upstream to GNOME. gnome-control-center 46.1 will be released in a few days with location services disabled by default. Although Debian is not on an urgent timeline (the next Debian Stable release is not until 2025), I intend to keep location services disabled when I upload the new version to Debian. That provides for more notice for people to adapt to the change before Mozilla's deadline. Please let me know if it would be better to keep location services enabled a bit longer. I provided a few more details at https://launchpad.net/bugs/2062178 Thank you, Jeremy Bícha
Bug#1069215: ***SPAM*** Bug#1069215: cherrytree: Please update to 1.1.2
On Thu, Apr 18, 2024 at 5:03 AM Patrick Winnertz wrote: > I've already prepared a update to 1.1.2 within the git and I'll upload within > the next week. So an update is coming. > > (REason for waiting: I've switched my gpg-setup from SC main key to C main > key + S subkey, but this needs to be picked up by the debian keyring before > uploading (and this will likely happen on ~24.4.). May I do the upload for you? I'd like to try to get the new version into Ubuntu 24.04 LTS but there isn't much time left. Thank you, Jeremy Bícha
Bug#1069216: rust-futures-rustls: Fails to build from source
Source: rust-futures-rustls Version: 0.24.0-3 Severity: serious Tags: ftbfs rust-futures-rustls fails to build: https://buildd.debian.org/status/package.php?p=rust-futures-rustls Thank you, Jeremy Bícha
Bug#1069215: cherrytree: Please update to 1.1.2
Source: cherrytree Version: 1.1.0+dfsg-1 Severity: wishlist Please update to 1.1.2 since it fixes several bugs: https://github.com/giuspen/cherrytree/releases Thank you, Jeremy Bícha
Bug#1061421: Fails to start after an upgrade
Control: tags +moreinfo Please verify whether wlgreet is working for you now. Thank you, Jeremy Bícha
Bug#1069033: pipewire: Update to 1.0.5
Source: pipewire Version: 1.0.5-1 Severity: wishlist Please update pipewire to 1.0.5. Could you also mark the new release as fixing LP: #2061381 ? https://launchpad.net/bugs/2061381 The new pipewire release improves how well the gnome-snapshot webcam app works for me. (Still buggy, but it's an improvement!) Let me know if you need help with this update. Thank you, Jeremy Bícha
Bug#1068823: (No Subject)
Control: reassign -1 src:apt Control: severity -1 wishlist On Sat, Apr 13, 2024 at 1:00 PM mYnDstrEAm wrote: > Thanks guys, these are very useful methods and I'll mention these as > alternatives to disk cleanups recommended at > https://unix.stackexchange.com/q/774199/233262 (this would probably very > useful to have at places about upgrades failing due to disk space issues even > though people only look these up once the problems already occurred). > > However, the problem of the upgrade requiring more disk space than displayed > at first remains and the command by Zeimetz can't be used with a built-in > rememberable well-known command like sudo apt-get upgrade --stepwise Personally, I don't think a machine that has that limited storage ought to be upgraded using apt from one Debian stable release to another. I suggest upgrading the storage first. If that's not possible, I recommend replacing the OS with a new image of Debian rather than trying to use apt to upgrade a few packages at a time. As has already been mentioned, it is not supported to arbitrarily break apt updates up like that to upgrade from say Debian 12 to the not-yet-released Debian 13. Thank you, Jeremy Bícha
Bug#1068923: heat-cfntools: Remove from Debian?
Source: heat-cfntools Version: 1.4.2-4 Severity: serious Control: blocks 1058652 by -1 According to https://launchpad.net/bugs/2052437 "heat-cfntools has officially been retired in the upstream OpenStack project so we should just RM it from the archive" heat-cfntools was already removed from Testing because of https://bugs.debian.org/1058242 Can we file a removal bug for heat-cfntools to allow for the removal of python-boto? Thank you, Jeremy Bícha
Bug#1068763: [Pkg-utopia-maintainers] Bug#1068763: upower: Please update to 1.90.4
Control: tags -1 -moreinfo On Wed, Apr 10, 2024 at 9:57 AM Michael Biebl wrote: > > Control: tags -1 + moreinfo > > Am 10.04.2024 um 15:38 schrieb Jeremy Bícha: > > Source: upower > > Version: 1.90.3-1 > > Severity: wishlist > > X-Debbugs-CC: bi...@debian.org > > > > Please update upower to 1.90.4. It was released yesterday with a fix > > for a significant disk write/ CPU use issue. > > > > https://gitlab.freedesktop.org/upower/upower/-/releases/v1.90.4 > > I might be mistaken, but 1.90.4 is just 1.90.3 with NEWS updated? > https://gitlab.freedesktop.org/upower/upower/-/compare/v1.90.3...v1.90.4?from_project_id=139=false Yeah that looks correct. Thank you for checking. Jeremy Bícha
Bug#1068763: upower: Please update to 1.90.4
Source: upower Version: 1.90.3-1 Severity: wishlist X-Debbugs-CC: bi...@debian.org Please update upower to 1.90.4. It was released yesterday with a fix for a significant disk write/ CPU use issue. https://gitlab.freedesktop.org/upower/upower/-/releases/v1.90.4 Thank you, Jeremy Bícha
Bug#1068484: juce-modules-source: Depends: libwebkit2gtk-4.0-dev but it is no longer built
Source: juce Version: 7.0.5+ds-1 Severity: serious Tags: trixie sid User: pkg-webkit-maintain...@lists.alioth.debian.org Usertags: webkit-4.0 Debian's webkit2gtk no longer builds the 4.0 API. The 4.1 API is the same as the 4.0 API except that it uses libsoup3 instead of libsoup2.4. Since juce does not use libsoup directly, it should be possible to change all references to webkit2gtk-4.0 to webkit2gtk-4.1 in both the upstream code (with a patch) and in debian/control to fix this issue. Please let me know if you intend to fix this bug soon or I will likely NMU this next week. Thank you, Jeremy Bícha
Bug#1068468: tracker: failing autopkgtest
Source: tracker Version: 3.7.1-1 Severity: serious Forwarded: https://gitlab.gnome.org/GNOME/tracker/-/issues/434 tracker's autopkgtest began failing after the update from 3.7.0 to 3.7.1. This is preventing tracker from being eligible for migration to Testing. I have reported the issue upstream. Thank you, Jeremy Bícha
Bug#1065778: libcdio: FTBFS on arm{el,hf}: _cdio_stdio.c:53:20: error: implicit declaration of function ‘fseeko64’; did you mean ‘fseeko’? [-Werror=implicit-function-declaration]
Control: tags -1 +patch There was an Ubuntu upload to fix this issue: https://launchpadlibrarian.net/723206207/libcdio_2.1.0-4.1build1_2.1.0-4.1ubuntu1.diff.gz https://launchpad.net/ubuntu/+source/libcdio/2.1.0-4.1ubuntu1 Thank you, Jeremy Bícha
Bug#1067675: library package (arch any) depending on a "common" package with too strict version constraint
Control: tags -1 -patch I misunderstood what you were proposing in part because the "patch" you proposed here was not for mutter and the version you pushed into Ubuntu had a hardcoded version instead. And I didn't read carefully enough. To move your idea forward, I proposed https://salsa.debian.org/gnome-team/libshumate/-/merge_requests/4 which also is not mutter but I think is a simpler test case which we can then apply to other packages including mutter if it is accepted. Thank you, Jeremy Bícha
Bug#1063957: python-pytest-lazy-fixture: autopkgtest regression with pytest 8
I noticed one package affected by this issue, prettytable, has switched to a fork, pytest-lazy-fixtures (note the s at the end of the name). Would someone like to package this for Debian to fix several packages failing to build? https://github.com/dev-petrov/pytest-lazy-fixtures Thank you, Jeremy Bícha
Bug#1066757: prettytable: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13
This is actually https://bugs.debian.org/1063957 prettytable has worked around this for the 3.10.0 release by switching to a fork, python-pytest-lazy-fixtures, which is not yet packaged in Debian. Thank you, Jeremy Bícha
Bug#1067675: library package (arch any) depending on a "common" package with too strict version constraint
Cloning a bug in the way you did is not very helpful. mutter's
situation is different than folks.
The mutter binary package has Depends: mutter-common (>= ${source:Version})
That allows mutter to be binNMU'd.
An alternative is to do something like evolution which has this override:
dh_makeshlibs -V'libevolution (>= $(DEB_VERSION_UPSTREAM)),
libevolution (<< $(DEB_GNOME_NEXTVERSION))'
which translates to this when built on Unstable (3.50.3-1+b1) :
dh_makeshlibs -V'libevolution (>= 3.50.3), libevolution (<< 3.51)'
We do actually need the upstream version of the -common package to
match the other binary packages. I am not convinced there is even
value in switching to the evolution style since it seems rare for
there to be an upload after the first upload for an upstream version
(-2 or higher basically) where the fact that sometimes arch: all
builds slower than other architectures is enough of a problem in these
packages to make the packaging more complicated.
I would prefer to revert your Ubuntu diff for mutter so that if this
bug is fixed, it is fixed in Debian first.
Thank you,
Jeremy Bícha
Bug#1068230: automatic suspend regression with gnome-settings-daemon 46
On Tue, Apr 2, 2024 at 8:03 AM Jeremy Bícha wrote: > > On Tue, Apr 2, 2024 at 5:31 AM Pirate Praveen > wrote: > > Recently automatic suspend stopped working. I think this was after gnome > > settings daemon 46 was available. Some background > > https://salsa.debian.org/Mobian-team/devices/librem5-support/-/issues/7 > > > > Not sure if phosh needs some adjustments with recent changes in gnome > > settings daemon. For now assigned to both. > > Do you have phosh 0.37 or higher installed yet? Correction: Do you have phosh 0.37.0-2 or 3.7.1-1 installed? Thank you, Jeremy Bícha
Bug#1068230: automatic suspend regression with gnome-settings-daemon 46
On Tue, Apr 2, 2024 at 5:31 AM Pirate Praveen wrote: > Recently automatic suspend stopped working. I think this was after gnome > settings daemon 46 was available. Some background > https://salsa.debian.org/Mobian-team/devices/librem5-support/-/issues/7 > > Not sure if phosh needs some adjustments with recent changes in gnome > settings daemon. For now assigned to both. Do you have phosh 0.37 or higher installed yet? Thank you, Jeremy Bícha
Bug#1067432: gnome-shell-pomodoro: needs update for GNOME Shell 46
Control: forwarded -1 https://github.com/gnome-pomodoro/gnome-pomodoro/issues/693 Please package version 0.25.1 to fix this issue. The new version drops support for GNOME Shell 45 but that's ok because Debian Experimental has version GNOME Shell 46. Thank you, Jeremy Bícha
Bug#1063096: python3-webview: proxy_tools dependency not found
On Sun, Mar 17, 2024 at 3:42 AM Jochen Sprickerhof wrote: > you uploaded python3-webview recently which seem to be broken (see > below). As I currently don't use the package, are you interested in > taking over maintainership? Sorry, the package has no reverse dependencies in Debian so I don't have a need for the package either. Thank you, Jeremy Bícha
Bug#1068130: xdg-desktop-portal-gnome cause slow start up time in some application
On Sun, Mar 31, 2024 at 10:31 AM Gaston Gonzalez wrote: > On Sun, Mar 31, 2024 at 10:11:37AM -0400, Jeremy Bícha wrote: > > Which desktop are you using? > > Budgie desktop (10.8.2-3) If you don't use GNOME, you don't need xdg-desktop-portal-gnome installed. xdg-desktop-portal-gtk is probably fine until the Budgie developers create their own portal backend. Thank you, Jeremy Bícha
Bug#1068130: xdg-desktop-portal-gnome cause slow start up time in some application
On Sun, Mar 31, 2024 at 9:57 AM Gaston Gonzalez wrote: > After some digging, it seems that the issue is related to the > applications using xdg-desktop-portal-gnome. After uninstalling it, the > problem is solved. Which desktop are you using? xdg-desktop-portal-gnome is the preferred portal backend for GNOME and you need a portal backend installed. There are important improvements we need in xdg-desktop-portal-gnome 46 but this is blocked on getting GNOME Shell 46 into Unstable (and Testing) which we expect to happen soon after the 32-bit time_t transition is resolved. Thank you, Jeremy Bícha
Bug#1068103: Cannot disable touchpad acceleration after upgrading to GNOME 46
On Sat, Mar 30, 2024 at 2:06 PM Josh Triplett wrote: > After upgrading GNOME to 46, the touchpad seems to have some sort of > acceleration enabled: it feels like it has a painfully large amount of > inertia. > > I've tried > gsettings set org.gnome.desktop.peripherals.touchpad accel-profile flat > and that doesn't seem to change anything. Please note that 'flat' should be in single quotes. You could also try using the GNOME Tweaks app to disable Touchpad Acceleration which should do the same thing as the gsettings command but without needing to know the correct syntax. Thank you, Jeremy Bícha
