You are not logged in.
Hi,
I have a couple of questions regarding the AUR/lensfun-git.
https://aur-dev.archlinux.org/packages/lensfun-git/ shows as version 0.3.2.r751.geced8c7-1, when i install the package it shows up as lensfun-git 0.3.2.r1683.g95de75d8-1. I assume that this is fine and the version of the AUR-package is only updated when the package itself is updated, not with every new release in the git. Is this correct?
When trying to view raw images I noticed that some of the programs didn't work as liblensfun.so.1 is missing:
"error while loading shared libraries: liblensfun.so.1: cannot open shared object file: No such file or directory"
pacman -Qo /usr/lib/liblensfun.so.1 -> error: No package owns /usr/lib/liblensfun.so.1
pacman -Qo /usr/lib/liblensfun.so.2 -> /usr/lib/liblensfun.so.2 is owned by lensfun-git 0.3.2.r1683.g95de75d8-1
How/where do I report this? Is this an issue with lensfun, with the AUR-package, or should the digikam/darktable, ... -packages be updated to require versions of lensfun that include the liblensfun.so.1?
Offline
Why are you using AUR-dev? That's an ancient snapshot of what the AUR looked like before a major update -- packages on it are likely to be outdated at the very least. But you are correct about -git package versioning, that is why they (as well as other VCS packages) have a pkgver function.
As for your soname problem, use lddtree (from community/pax-utils) to identify what has been built against that library, and if it is owned by an AUR package, rebuild it. If it's owned by a repo package, and you are sure your system is up-to-date, then you may have cause to open a bug report against that package. EDIT: My mistake, see below.
Last edited by WorMzy (2019-06-09 12:12:45)
Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD
Making lemonade from lemons since 2015.
Offline
If it's owned by a repo package, and you are sure your system is up-to-date, then you may have cause to open a bug report against that package.
No, the repo package provides liblensfun.so.1, so other repo packages are built against that. Not being built against a newer -dev version that the user opts to install from the AUR would not be a bug.
"UNIX is simple and coherent..." - Dennis Ritchie, "GNU's Not UNIX" - Richard Stallman
Offline
Ah, right you are. For some reason I read it as though the repo package provided liblensfun.so.2. OP, you will need to rebuild the repo packages against the new library (see ABS), or create a compat package to provide the old library in a way that doesn't conflict with the -git package.
Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD
Making lemonade from lemons since 2015.
Offline
Hi, thank you for your answers.
I successfully rebuild darktable via ABS, but I don't really want to build all the packages from source with every update (that's why I switched over from gentoo). Is building a compatibility-package easy to learn or should I just wait for the repo packages to be updated?
WorMzy, to answer your question about AUR-dev: It was the first link duckduckgo provided, I didn't even notice the unusual subdomain.
Offline
should I just wait for the repo packages to be updated?
https://lensfun.github.io/news/
That suggests you may have to wait a long time.
Changing lensfun-git to coexist with lensfun seems best solution . Since lensfun-git uses a different so-name, that may be easier then in most cases.
If you remove
provides=('lensfun=0.3.0')
conflicts=('lensfun')
then build and try to install, what errors do you get from pacman ?
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
(A works at time B) && (time C > time B ) ≠ (A works at time C)
Offline
I hadn't noticed the versioned 'provides'. While it's not the cause of this problem, you definitely should not use a versioned 'provides' when the package you are building definitely doesn't provide that version!
"UNIX is simple and coherent..." - Dennis Ritchie, "GNU's Not UNIX" - Richard Stallman
Offline