[Debian-mobcom-maintainers] Bug#1010578: osmo-mgw: FTBFS if systemd is in build environment

[Gianfranco Costamagna]

control: severity -1 serious

Hello, I think not being able to build a package in a "normal" environment is considered RC

G.
On Wed, 4 May 2022 13:44:15 -0600 Dan Bungert <daniel.bungert at canonical.com> wrote:
> Package: osmo-mgw
> Version: 1.9.0+dfsg1-3
> Severity: normal
> User: ubuntu-devel at lists.ubuntu.com
> Usertags: origin-ubuntu kinetic
> 
> Dear Maintainer,
> 
> If systemd is present in the build environment, the following output will be
> observed during build:
> 
> dh_missing: warning: lib/systemd/system/osmo-mgw.service exists in debian/tmp
> but is not installed to anywhere
> dh_missing: error: missing files, aborting
> 
> This appears to be due to an unexpected upstream systemd service file, that is
> then not covered by the existing debhelper commands.
> 
> There are several options to avoid this, including
> * add the entry to not-installed
> * configure with argument --with-systemdsystemunitdir=no, which cause the
>   install step to not provide the upstream systemd service file
> * adjust the package to use the upstream systemd service file
> 
> I propose using the --with-systemdsystemunitdir=no configuration.  See below.
> 
> -Dan
> 
> diff -Nru osmo-mgw-1.9.0+dfsg1/debian/rules osmo-mgw-1.9.0+dfsg1/debian/rules
> --- osmo-mgw-1.9.0+dfsg1/debian/rules   2022-03-16 14:59:47.000000000 -0600
> +++ osmo-mgw-1.9.0+dfsg1/debian/rules   2022-05-04 13:34:46.000000000 -0600
> @@ -15,6 +15,10 @@
>  %:
>         dh $@ --with autoreconf
> 
> +override_dh_auto_configure:
> +       # Use the packaging-provided systemd unit file
> +       dh_auto_configure -- --with-systemdsystemunitdir=no
> +
>  override_dh_auto_test:
>         dh_auto_test || (find . -name testsuite.log -exec cat {} \; ; false)
> 
>