On 1/14/25 14:38, Michael Biebl wrote:
Am 14.01.25 um 16:11 schrieb Diederik de Haas:
On Tue Jan 14, 2025 at 3:49 PM CET, Diederik de Haas via
Pkg-voip-maintainers wrote:
On Thu Jan 9, 2025 at 6:55 PM CET, Michael Biebl wrote:
No, all you are supposed to do in your .install files is to use the
correct paths
/usr/lib/systemd/system/foo.service
/usr/lib/sysusers.d/foo.conf
/usr/lib/tmpfile.d/foo.conf
The upstream build system is supposed to install the files directly
into
those paths as they are defined in /usr/share/pkgconfig/systemd.pc.
Those paths should be queried by the build system via pkgconfig and
not
be hard-coded.
If it doesn't do that, then there is a bug in the upstream build
system
and you should report it as such to upstream.
This is *not* a Debian packaging issue!
I tried it with the attached patch and got the same error as Chris
Knadle
pointed out, 'even' with 1.5.735 which has the referenced commit/PR.
Can you confirm whether the attached patch is the right thing to do on
the Debian side? If that's the case, then we know (?) that the problem
is indeed (still) in the upstream build system.
Or if the patch is incorrect, can you point out why/where and possibly
provide an (cmake based) example which I could use as inspiration?
Looks like I found confirmation that the upstream build system is NOT
doing the right thing ... in CMakeCache.txt:
Have you used -Duse-pkgconf-install-paths=ON ?
I looked at that setting in cmake_options.md and it states that it's
incompatible with CMAKE_INSTALL_PREFIX, so this looks to be an override
of what CMake would normally be doing. I'll consult upstream as to what
they think about this.
-- Chris
Chris Knadle
chris.kna...@coredump.us
