Bug#1103904: ITP: pwvucontrol -- pipewire volume control
Matthias Geiger <[email protected]> Sun, 26 Jul 2026 14:40:24 +0200
| Newsgroups | gmane.linux.debian.devel.wnpp |
|---|---|
| Message-ID | <tis9dy.54vnfiech9v9__48075.7050959923$1785070884$gmane$org@riseup.net> |
On Sun, 26 Jul 2026 10:07, Christopher Obbard <[email protected]> wrote: >Hey, > > >I am happy to help with packaging this. Feel free to put me in Uploaders. > > >Just a couple of quick thoughts: > > >The package isn't published on crates.io. How do we solve that in debcargo-config? I guess since it'll be vendored you'll most likely create its own repo and not use debcargo-conf? > > Yes, that will be vendored to debian/missing-sources. >I looked at cargo debstatus for this package; here's a short summary: >``` >cargo debstatus --all-features --no-dev-dependencies > pwvucontrol v0.5.3 (in workspace, /home/obbardc/projects/git/pwvucontrol) > 🔴 ├── wireplumber v0.2.0 (git+https://github.com/saivert/wireplumber.rs.git?branch=wp-0.5-glib-0.21-pipewire-0.9#04fbbc6ea157cdd7061f6a5f2a6b22e102fccbcc) > ├── anyhow v1.0.103 (in debian) > ├── formatx v0.2.4 (in debian) > ├── futures v0.3.32 (in debian) > ├── gettext-rs v0.7.7 (in debian) > 🔽 ├── glib v0.21.5 (newer, 0.22.7 in debian) > 🔽 ├── gtk4 v0.10.3 (newer, 0.11.3 in debian) > 🔴 ├── imbl v3.0.0 > 🔽 ├── libadwaita v0.8.1 (newer, 0.9.1 in debian) > ├── log v0.4.33 (0.4.32 in debian) > └── pipewire v0.9.2 (in debian) >``` > >I tried patching out the gnome deps to latest in Debian; but it failed to build with ~88 errors. I didn't go any further. > Yeah that does seem not easily fixable. > >For the crate to build, I needed these B-d: >blueprint-compiler >libgdk-pixbuf-2.0-dev >libgtk-4-dev >libadwaita-1-dev >libpipewire-0.3-dev >libwireplumber-0.5-dev > > >Since upstream uses meson, I had to go the long way around to generate the resources etc: > >meson setup builddir >meson compile -C builddir dev-schema >meson compile -C builddir blueprints >meson compile -C builddir resources_gresource > >GSETTINGS_SCHEMA_DIR="$PWD/builddir/data" \ >GSETTINGS_BACKEND=memory \ >PWVUCONTROL_RESOURCEDIR="$PWD/builddir/data/resources" \ >cargo run > That should happen automatically with meson build. Given upstream is still on gtk-rs 0.10 I am considering to keep this shelved for now. I filed https://github.com/saivert/pwvucontrol/issues/117. The FFI bindings are not that trivial to update, and I do not want to vendor all of gtk-rs; just the wireplumber crate. best,