Your message dated Fri, 03 Oct 2025 17:21:04 +0000
with message-id <[email protected]>
and subject line Bug#1061107: fixed in vala 0.56.18-5
has caused the Debian Bug report #1061107,
regarding vapigen: Make it possible to cross-compile libraries with Vala
bindings
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1061107: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061107
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: valac
Version: 0.56.14-1
Severity: wishlist
X-Debbugs-Cc: [email protected]
Now that we can cross-compile GObject-Introspection data, many GNOME
packages that could not not previously be cross-compiled become available
for cross-compiling. However, some of the libraries we would like to be
able to cross-compile (for example ibus and libportal) have Vala bindings,
generated from the library's own GIR XML via the vapigen tool.
At the moment, during a cross-build, vapigen will generally be a
host-architecture binary which cannot always be run on the build
architecture, causing builds to fail.
Ideally, during a cross-build, we would like to run a build-architecture
vapigen binary, but configure it (perhaps via command-line options or
environment variables) so that it will find host-architecture GIR XML
in /usr/lib/${DEB_HOST_MULTIARCH}/gir-1.0. The search paths need to
be architecture-specific in order to find GLib-2.0.gir without having
libgirepository1.0-dev installed, because libgirepository1.0-dev
is not cross-compile-friendly. I don't think there are any other
architecture-dependent paths involved, but the Vala maintainers would
know what this tool does better than I do.
As a proof-of-concept, I was able to work around this in libportal by
generating some local wrappers and overrides; but ideally this would
be something that could be done centrally, with most of the work in the
vala package.
I'll follow up with more concrete suggestions, but I wanted to open the
bug with a relatively solution-neutral problem statement rather than
jumping directly to a solution.
This is related to #1060904, but perhaps more of a downstream issue;
some solutions to it would benefit from #1060904, but that isn't a
mandatory dependency.
Thanks,
smcv
--- End Message ---
--- Begin Message ---
Source: vala
Source-Version: 0.56.18-5
Done: Simon McVittie <[email protected]>
We believe that the bug you reported is fixed in the latest version of
vala, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Simon McVittie <[email protected]> (supplier of updated vala package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Fri, 03 Oct 2025 17:55:37 +0100
Source: vala
Architecture: source
Version: 0.56.18-5
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers
<[email protected]>
Changed-By: Simon McVittie <[email protected]>
Closes: 1061107 1116553
Changes:
vala (0.56.18-5) unstable; urgency=medium
.
* Team upload
* Retry previous upload (no changes)
.
vala (0.56.18-4) unstable; urgency=medium
.
* Team upload
* d/patches, d/control: Make valac Multi-Arch co-installable.
By making the deprecated vala-gen-introspect script pick up
architecture-specific details from $PKG_CONFIG, we can make it
textually identical across all architectures. (Closes: #1116553)
* d/control: valac Recommends gcc | gcc-for-host, not just gcc.
The architecture-prefixed `${DEB_HOST_GNU_TYPE}-valac` wrappers tell
valac to use `${DEB_HOST_GNU_TYPE}-gcc`, so if those wrappers are
used, the gcc package is not strictly necessary.
* d/changelog: Point to #1116552 in previous changelog entry
* Release to unstable
.
vala (0.56.18-3) experimental; urgency=medium
.
* Team upload
* d/rules: Parameterize the vala major/minor version number
* d/rules: Generate cross valac wrapper from a template
* d/*.links: Create cross valac symlinks declaratively
* Use absolute path to run valac in the cross wrapper.
If the cross wrapper for valac has been found in /usr/bin, it
seems less surprising if it runs the corresponding system copy of
valac, bypassing any possible locally-installed valac that might
conceivably be the same major version number.
* Move vapigen, vapigen-0.56 to valac-bin, add required Breaks/Replaces
* d/rules: Generate a ${DEB_HOST_GNU_TYPE}-vapigen which searches
appropriate directories.
For example, this means we find GLib-2.0.gir in
/usr/lib/${DEB_HOST_MULTIARCH}/gir-1.0. (Closes: #1061107)
* Generate a ${DEB_HOST_GNU_TYPE}-vala.ini to use valac, vapigen wrappers.
This allows packages with a Meson build system to opt-in to using
the host architecture valac and vapigen during cross-builds. Ideally
this would be done more centrally, in `meson env2mfile` (#1116552)
or debhelper, but we should make the infrastructure available first.
* d/control, d/rules: Use build-architecture valac if cross-compiling.
This allows vala itself to be cross-compiled, as long as the
pkg.vala.nographviz build-profile is used (or #983886 is fixed)
and a native build for the build architecture has been done first.
* d/copyright: Don't quote the FSF's former postal address here
* Standards-Version: 4.7.2 (no changes required)
* Initially upload to experimental, since the cross-related changes
are somewhat intrusive
Checksums-Sha1:
a19c6e663f94b44967322b123eac0041267e7aaa 3424 vala_0.56.18-5.dsc
a0b3f4ce1a2e5af2c03910b24c5ed231d06612d7 36944 vala_0.56.18-5.debian.tar.xz
65950efd120e91cfbafc08df3a7ed638836691ca 12752880 vala_0.56.18-5.git.tar.xz
4198e1cf572356e46d57622b61b4878302fec0cf 18214 vala_0.56.18-5_source.buildinfo
Checksums-Sha256:
a99b945f770c440be9c5c8a1d0f1d630852eb48122fdcdc5b3fefe7ec95d736f 3424
vala_0.56.18-5.dsc
bd538055568355df01eab1b8cca5a05a4e6c798f9ff631fd82ea8f040a500d42 36944
vala_0.56.18-5.debian.tar.xz
dea2108818a0ef22581a474de9df06d45618544c76e43c13383ca05beece8145 12752880
vala_0.56.18-5.git.tar.xz
7c8683eab4a30a16088b58e42d28b081ae8599594605e77d8ec94e4f221b26fa 18214
vala_0.56.18-5_source.buildinfo
Files:
abd7df448ed85da81966e49676faa35d 3424 devel optional vala_0.56.18-5.dsc
f727151d95b48071004323fca5a0ce81 36944 devel optional
vala_0.56.18-5.debian.tar.xz
22d2b61c1bb062a0dd1393fa73103aeb 12752880 devel optional
vala_0.56.18-5.git.tar.xz
84c8177086c4cb5e79af7363ce1d5ba5 18214 devel optional
vala_0.56.18-5_source.buildinfo
Git-Tag-Info: tag=8c72d955b62a251c9c985db8da3cc71c9b9cc99b
fp=7a073ad1ae694fa25bff62e5235c099d3eb33076
Git-Tag-Tagger: Simon McVittie <[email protected]>
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEN02M5NuW6cvUwJcqYG0ITkaDwHkFAmjgAIIACgkQYG0ITkaD
wHmethAAl26Kr1VJTkbgcsD5AbX5l+RgBeDIMesqFYa6t0TIze/9uUbzceWke+7q
w4ghKgYmUEFO8yCA/OG8h7T7xPp57NzV7DeKqiqp7M2qCIsbBKjYam038bl1y8nv
g0jj/LD001iW6cWMGL2keNS28NUgHE1DXtkNQ+ux46kj2isoTNryYsuxrgY7a0R0
SGwes8v2LyVJVamgDtdSxUltZvuOZKZM2YhP9KsiR5WFqZvR1G3WMtHlYq2otFzR
ACjbkbCJhyFERh0uDsk6ayBp0+FEdgnHKNS2jW0SIQNtzH9Say7euM8ZR0HWH4Xi
kLf195WQjHIzFShpbmE/xjHfoSXJyNav61CDdxd8ug38nKr72wHpojNN8v3+yKAz
yD1qsfGYYzIg5d41gLwiBS2KVhy4gEvWcAcYrxrCgJdobL2fdQTtqWyV1cxbI7lW
nUSTAcjxYh53rD+Wh5kmQZzD1FjDaP7hAof5TMhC89m4wfMYpONMgzeBuFHmdR4F
QBdQqr4UubYRQgdoaDWdYA+LgzFdgdb6CzvkwGhCcJ2Wury2VWdcM84lcsO6f7Ob
x8zbZCfRU2UDaIrF0tA09WLo8RrxnEXVU0KX5RLkvrast0hT42PpojyrUEw33kGm
qXd1DnGeWT7CnjobI+3sxl22SQbBqA7hUomhVfK0Eg1ppFucRYI=
=5Wrs
-----END PGP SIGNATURE-----
pgpbYN1nTGSYF.pgp
Description: PGP signature
--- End Message ---
