Your message dated Fri, 25 Aug 2023 13:39:40 +0200
with message-id <1f02aa0d0d984cf3f56f39dcbaa55a2516a61d74.ca...@collabora.com>
and subject line Re: Bug#1050500: Acknowledgement (meson: Add direct dependency
on dpkg-dev)
has caused the Debian Bug report #1050500,
regarding meson: Add direct dependency on dpkg-dev
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 ow...@bugs.debian.org
immediately.)
--
1050500: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050500
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: meson
Version: 1.0.1-5
Severity: normal
Dear Maintainer,
The meson package should depend on `dpkg-dev` as it is actually using
`dpkg-architecture` directly
(see
https://github.com/mesonbuild/meson/blob/1bb29b1b329ec056c61a54070024b6b003cf5ca4/mesonbuild/utils/universal.py#L1025
) to compute the correct libdir.
I discovered this by compiling my project with the debian:stable-slim
docker container which doesn't include `dpkg-architecture` by default.
I wondered why my library was being installed to /usr/lib64.
--- End Message ---
--- Begin Message ---
Oops, it's in recommends and I'm using `--no-install-recommends` so it
seems good to me.
--- End Message ---
