commit d0adc7bd299a5b56eb42adc4ab8b3109bedcb4bb
Author: Simon McVittie <smcv@debian.org>
Date: Sun Aug 16 18:03:17 2026 +0100
d/control: Enable gir sequence
This generates appropriate dependencies for the included GIR XML.
For this to work, we need to install the typelib somewhere -
normally this would be a gir1.2-phosh-0 package, but to avoid a trip
through NEW, install it into gir1.2-phosh-0-dev for now.
commit 797761b05d8ce31e8db4256813ab78b66d4c7837
Author: Simon McVittie <smcv@debian.org>
Date: Sun Aug 16 17:59:54 2026 +0100
d/salsa-ci.yml: Exercise the nocheck and nodoc build-profiles
If they regress with future changes, this is a good way to find out.
commit 9f5c30fdfe94bc6951dd4153db5f5e75d9634442
Author: Simon McVittie <smcv@debian.org>
Date: Sun Aug 16 17:27:03 2026 +0100
d/control: Replace libgirepository1.0-dev build-dependency
We need gobject-introspection for the command-line tools, and
gir1.2-*-dev for each GIR XML module whose name/version is passed to
the includes parameter of gnome.generate_gir. In practice the GIR XML
is currently provided by the various lib*-dev packages, but that won't
necessarily always be true if they were built with the nogir
build-profile, so explicit is better than implicit.
Closes: #1118904
commit e120750495c748aa529762215a158f7d7300c508
Author: Simon McVittie <smcv@debian.org>
Date: Sun Aug 16 17:22:40 2026 +0100
d/control, d/rules: Only require gi-docgen if phosh-doc will be built
If we're doing an architecture-only build (debuild -B) like the
official Debian buildds do, then we don't need to waste time on this.
commit 547a0144576ea744b639d1f502b6a5c884270829
Author: Simon McVittie <smcv@debian.org>
Date: Sun Aug 16 17:18:51 2026 +0100
d/control: Always require GObject-Introspection, even under nodoc
As well as being needed by gi-docgen, the introspection toolchain is
needed by -Dbindings-lib=true, which is unconditionally enabled.
Closes: #1144560
Among the 1 debian patch available in version 0.57.0-1 of the package, we noticed the following issues:
Automatic checks made by the Debian l10n team found some issues with the translations contained in this package. You should check the l10n status report for more information.
Issues can be things such as missing translations, problematic translated strings, outdated PO files, unknown languages, etc.