The system neither starts to build my program, it dies before.:disapointed:ġ-when I should put pkgconfig( package) following BuildRequires: and when not, because if I try BuildRequires: pkgconfig(libliquid-devel) I updated my spec file following the one you linked - I could not plain copy it because it’s an old release (0.26 = May 2019)ĭespite that, nothing changes: the build continue to fail since the buildroot itself fails to install. That tarball will be published on Sourceforge then the spec will link it. My goal here is to check if building in obs still works or if I need to update something, like the spec or the other files need to build deb packagesīecause I want to put these up to date files in the final 0.50 tarball. Well, the 0.50 has not been published yet. So I can update the spec file version, then run the following to update the source Don’t use soapy, but do work with RTL SDRs (ADSB and high altitude balloons). Where is the link to 0.50, you should put the full url to the download (plus when wanting to update you can auto download the source, plus it’s a OBS check). So the problem could be solved by replacing 1.7.3 with 1.7.4++ in the buildroot but I can’t figure out how to do thatīTW I can build my RPMs without problems in my Tumbleweed box without OBS, since pkgconf-pkg-config is 1.8.0. do not own directories provided by filesystem.The buildroot was: /var/tmp/build-root/openSUSE_Tumbleweed-x86_64 Since then, I’m no more able to build it, due to an error arising while *osc build *sets up the buildroot:Ģ7s] cumulate rpm-build-4.17.0-2.1ģ0s] Preparing… #ģ0s] file /usr/lib64/pkgconfig conflicts between attempted installs of pkgconf-pkg-config-1.7.3-26.5.x86_64 and filesystem-84.87-3.1.x86_64ģ0s] file /usr/share/pkgconfig conflicts between attempted installs of pkgconf-pkg-config-1.7.3-26.5.x86_64 and filesystem-84.87-3.1.x86_64ģ0s] tweed failed “build pkgconf.spec” at Wed Dec 15 22:24. I have a project at my home I could build without problems until last September, both locally and online.
0 Comments
Leave a Reply. |