Source: libxfce4windowing
Version: 4.20.4-1build1
Severity: important
Tags: newcomer
X-Debbugs-Cc: [email protected]
Dear Maintainer,
* What led up to the situation?
I am the DM for budgie-desktop - I cannot compile the latest upstream
budgie-desktop that depends on libxfce4windowing 4.20.4
* What exactly did you do (or not do) that was effective (or
ineffective)?
Compiling budgie-desktop preview 2 depends on 4.20.4 capability where the dev
package ships the vapi for libxfce4windowing
* What was the outcome of this action?
The compilation fails
* What outcome did you expect instead?
The compilation should work - budgie-desktop no longer ships with its own vapi
- upstream budgie states its requirement
is for libxfce4windowing v4.20.4 with its own shipped vapi
I note - the current package is autotools based.
I've tested via a meson build - with the option -Dvala=yes and a B/D of valac
to allow vapigen to be installed
I'm not sure the current autotools files has the same vala based option - maybe
--enable-vala in d/rules ?
If you wish, I'm happy to attach a debdiff that switches the build of
libxfce4windowing to use meson?
-- System Information:
Debian Release: forky/sid
APT prefers resolute
APT policy: (500, 'resolute')
Architecture: amd64 (x86_64)
Kernel: Linux 6.17.0-6-generic (SMP w/16 CPU threads; PREEMPT)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
