[opensuse-packaging] pkgconfig(libfprint-2) not found
Hi, I'm building a package for TW against libfprint-2: libfprint-devel-1.90.1-61.1.x86_64.rpm provides pkgconfig(libfprint-2) = 1.90.1 but this is not found (although it is in TW standard) Any idea why? Affected package: https://build-test-1.opensuse.org/package/show/ home:DocB:branches:home:DocB:branches:hardware/fingerprint-gui (removing pkgconfig(libfprint-2) in favour of libfprint-devel fixes the issue, but I would be interested why it is not found.....) Cheers Axel -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
On 5/11/20 5:44 PM, Axel Braun wrote:
Affected package: https://build-test-1.opensuse.org/package/show/ home:DocB:branches:home:DocB:branches:hardware/fingerprint-gui
(removing pkgconfig(libfprint-2) in favour of libfprint-devel fixes the issue, but I would be interested why it is not found.....)
Hi Axel, Because you have crap in your home project. It's a good idea to remove it. It reduces build pressure on OBS and also doesn't get everyone confused. Your repository comes from, (osc meta prj) <repository name="openSUSE_Tumbleweed"> <path project="home:DocB:branches:hardware" repository="openSUSE_Tumbleweed"/> <arch>i586</arch> <arch>x86_64</arch> </repository> But that project has a copy of the library, # osc ls home:DocB:branches:hardware fingerprint-gui libfprint # osc ls home:DocB:branches:hardware libfprint baselibs.conf libfprint-1.0.tar.xz libfprint.changes libfprint.spec And getting these binaries results in, # rpm -qp --provides libfprint-devel-1.0-2.1.x86_64.rpm warning: libfprint-devel-1.0-2.1.x86_64.rpm: Header V3 RSA/SHA256 Signature, key ID 748af481: NOKEY libfprint-devel = 1.0-2.1 libfprint-devel(x86-64) = 1.0-2.1 pkgconfig(libfprint) = 1.0 And this is why libfprint-2 is not available. Because it's not. The first libfprint-devel is too old. So if you change your BR, you are building also vs. wrong library anyway, unless that's your intention. Hope this clears up the situation :) - Adam -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
Hello Adam, Am Dienstag, 12. Mai 2020, 13:14:13 CEST schrieb Adam Majer:
On 5/11/20 5:44 PM, Axel Braun wrote:
Affected package: https://build-test-1.opensuse.org/package/show/ home:DocB:branches:home:DocB:branches:hardware/fingerprint-gui
(removing pkgconfig(libfprint-2) in favour of libfprint-devel fixes the issue, but I would be interested why it is not found.....)
Because you have crap in your home project. It's a good idea to remove it. It reduces build pressure on OBS and also doesn't get everyone confused.
I would not call it crap (see below)....
Your repository comes from, (osc meta prj)
<repository name="openSUSE_Tumbleweed"> <path project="home:DocB:branches:hardware" repository="openSUSE_Tumbleweed"/> <arch>i586</arch> <arch>x86_64</arch> </repository>
But that project has a copy of the library,
# osc ls home:DocB:branches:hardware fingerprint-gui libfprint
# osc ls home:DocB:branches:hardware libfprint baselibs.conf libfprint-1.0.tar.xz libfprint.changes libfprint.spec
And getting these binaries results in,
# rpm -qp --provides libfprint-devel-1.0-2.1.x86_64.rpm warning: libfprint-devel-1.0-2.1.x86_64.rpm: Header V3 RSA/SHA256 Signature, key ID 748af481: NOKEY libfprint-devel = 1.0-2.1 libfprint-devel(x86-64) = 1.0-2.1 pkgconfig(libfprint) = 1.0
OK, I was under the wrong assumption that it picks the newer library (from TW) as long as I dont pin it to a certain version.
And this is why libfprint-2 is not available. Because it's not. The first libfprint-devel is too old. So if you change your BR, you are building also vs. wrong library anyway, unless that's your intention.
Actually it was: Intention was to bring fingerprint-gui to qt5, and that worked as long as libfprint is version 1.0. Current fingerprint-gui for TW is broken anyway.... Next I wanted to build it against libfprint-2, thats the reason for the second branch. Unfortunately there seems to be an API change as well, so this need someone with qt programming skills (which is not me) So, if someone wth qt skills want to look into this....much welcome! Thanks for the clarification! Axel -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
On 5/12/20 3:44 PM, Axel Braun wrote:
Next I wanted to build it against libfprint-2, thats the reason for the second branch. Unfortunately there seems to be an API change as well, so this need someone with qt programming skills (which is not me)
You have to keep in mind, when you branch, the search path for the derived project is from your branched project. The chain continues. So if you want to build vs. Factory, you have to alter your project to either build vs. openSUSE:Factory/snapshot or at very least hardware/openSUSE_Tumbleweed AFAIK, OBS picks the first rpm in the chained path and these RPMs are picked without versions. The BR resolution appears to occur later. This process makes for a consistent resolution of the project path. - Adam -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
participants (2)
-
Adam Majer -
Axel Braun