Hi Laurent,
thank you for the answer.
On 2026-03-30 00:22, Laurent Bercot wrote:
> What exact problems are you experiencing during package creation?
The actual problem is, that after the package is successfully built, the
Debian Lintian system throws a custom-library-search-path error.
https://lintian.debian.org/tags/custom-library-search-path.html
Basically the debian policy discourages the use of rpath except in
certain situations, which do not apply here.
> Some skaware packages already exist for Debian, they do not turn off rpath,
> and they're working, as far as I can tell.
I have checked skalibs, execline and s6: rpath was introduced in spring
2025 to their Makefiles. Since the current skaware Debian packages were
built in 2024, that topic didn't come up yet.
This means, that this Lintian policy will also affect the other skaware
Debian packages, when they get updated.
> [...]
> I am reluctant to provide an option to disable rpath because in my
> experience, disabling it can cause linking failure annoyances at every
> step, whereas keeping it enable only causes problems when something is
> already wrong either in a build or in versioning management of a package.
> If Debian can do without that option, and so far it looks like it has
> been able to, I'd rather keep it that way.
Thanks for the explanation. I will investigate alternatives like
patching the Makefile or using chrpath. Such a config option seemed to
me like the cleanest and most future proof way to solve this.
>> 2. API breaking changes
>>
>> During 2.14.4.0 and 2.14.5.0, the removal of `skalibs_sigtable` caused
>> an API breaking change in
>
> That one, however, is on me: I failed to flag this commit as requiring
> a major update. Sorry about that; it normally does not happen.
It is good to know, that such changes usually cause a major version update.
> What is the simplest way for me to fix it? Should I cut a 2.15.0.0
> release of skalibs ASAP, that you can then link all your new binaries
> against, and usable versions will jump from 2.14.4.0 directly to 2.15.0.0?
Thank you for the offer, that would be perfect. But if you intended to
release 2.15 anyway in the next days, then this can wait.
Best wishes
Markus
Received on Mon Mar 30 2026 - 18:46:58 CEST