Arch Linux

Andrei Korshikov

Member

Registered: 2024-02-10

Posts: 10

Website

[SOLVED] namcap: Soname … is not specified as provides by … yet

For example:

cvs-feature-bin I: Soname 'libbsd.so=0-64' is not specified as provides by libbsd yet (needed in files ['usr/bin/cvs'])

Should I do something—e.g. should I use

depends=(libbsd.so=0-64)

instead of just

depends=(libbsd)

?

Or should I just skip this message?

I guess it will disappear when autodeps will be applied everywhere.

Last edited by Andrei Korshikov (2026-03-26 20:26:16)

Lone_Wolf

Administrator

From: Netherlands, Europe

Registered: 2005-10-04

Posts: 14,912

Re: [SOLVED] namcap: Soname … is not specified as provides by … yet

Does cvs-feature-bin come from the AUR cvs-feature pacakge or is it from a different package ?

If the latter please post the PKGBUILD you have.

Kep in mind that autodeps currently does nothing for aur packages (as far as I know)

---

Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.

clean chroot building not flexible enough ?
Try clean chroot manager by graysky

Andrei Korshikov

Member

Registered: 2024-02-10

Posts: 10

Website

Re: [SOLVED] namcap: Soname … is not specified as provides by … yet

My question was stupid (had obvious answer). In principle, namcap's libdepends-missing-provides message is quite self-explanatory: the dependency provides array does not contain the soname. If the dependency is out of my control (i.e. I can not or do not want to rebuild it)—I can do nothing.

---

namcap: Soname dependency … provided by … detected and not included was closed as duplicate of this thread. Well, libdepends-detected-not-included is distinct message and I have an explanation—see I: Soname dependency … provided by … detected and not included (needed in files …).

---

Does cvs-feature-bin come from the AUR cvs-feature pacakge or is it from a different package?

I was playing with a local package, now it is cvs-feature-bin. But my questions were generic: what to do with libdepends-missing-provides and libdepends-detected-not-included? Anyway, I've added my current understanding to the wiki: https://wiki.archlinux.org/title/Namcap#Troubleshooting

---

autodeps currently does nothing for aur packages (as far as I know)

Yep, I agree. Libraries must be built with autodeps (i.e. have "depend = lib:…" in their .PKGINFOs), which is not the case for official packages, to my understanding.

Last edited by Andrei Korshikov (2026-03-26 20:29:18)