How do I get RPM from branched package on my Build Service?
All/Devs, I branched keepassxc and made the changes needed to install it with KDE3 without deleting the original keepassx. The build succeeds on build service, but I can't find the rpm. The Download link goes to my repository, but clicking the link says the repo isn't available: https://software.opensuse.org//download.html?project=home%3Adrankinatty%3Abranches%3Asecurity%3Akeepassxc&package=keepassxc Checking the direct repository: http://download.opensuse.org/repositories/home:/drankinatty:/branches:/ It's not there yet either? In the past within a minute or two after building the package would be in my repo, but there seems to be a hiccup. This is why I usually just build locally with rpmbuild -- at least then I can find the darn rpm when the build is done. Currently the build is finished for the 2nd time after cleaning up a RPM Lint complaint about the changelog, but still I can't seem to find the rpm. The only reason I used buildservice this time is the 15.4 Backport update .srpm will not build locally due to: error: Failed build dependencies: pkgconfig(libpcsclite) is needed by keepassxc-2.7.1-bp154.3.3.1.x86_64 There is no libpcsclite package available that provide the .pc file. No -devel, no nothing, just the libs -- which is why I tried build-service which succeeds, but hides how it did it behind the magic curtain. (do I have to hack a .pc file on my own for 15.4?) Anyway -- where do I find the rpm I just build on build service? It succeeded, it's just not in my repo or anywhere else I can find it. What's the trick? -- David C. Rankin, J.D.,P.E.
On 10/13/22 22:18, David C. Rankin wrote:
All/Devs,
I branched keepassxc and made the changes needed to install it with KDE3 without deleting the original keepassx. The build succeeds on build service, but I can't find the rpm. The Download link goes to my repository, but clicking the link says the repo isn't available:
Checking the direct repository:
http://download.opensuse.org/repositories/home:/drankinatty:/branches:/
It's not there yet either? In the past within a minute or two after building the package would be in my repo, but there seems to be a hiccup.
Never mind, It's just a LOT slower than it used to be. It's there now. -- David C. Rankin, J.D.,P.E.
participants (1)
-
David C. Rankin