On Tue, Feb 23, 2021 at 08:44:34PM +1030, Simon Lees wrote:
On 2/23/21 8:20 PM, Michal Suchánek wrote:
On Mon, Feb 22, 2021 at 10:20:09AM +1030, Simon Lees wrote:
On 2/22/21 7:13 AM, L A Walsh wrote:
On 2021/02/19 14:14, Axel Braun wrote:
One can always build locally against OBS repos.
--- Yeah, your build target also has to be installable on your local machine. That's a primary reason for building on my local machine. The resulting rpm will use the libs on my machine at build time, and can be installed and work after they are built.
At this point it sounds more like you are trying to build a derivative distribution "Based on openSUSE" just for one machine.
Using a foreign or virtual environment won't let you build, necessarily, for installation on your local machine.
One feature of open build service that people building derivative distros use is that packages will use other packages in the same project / repo for builds. So if all the custom packages you are using on your machine are in the same project then it will use them for builds. This gives you other advantages as well in that if you update one of the libraries it will automatically rebuild all the packages that depend on it.
There is no such project. The packages are some obsolete TW snapshot. And building on Leap may or may not work - I think the new rpm spec file uses features of the new rpm so it is not buildable with old rpm. I suppose that at some point in the history of the rpm package it contained the new sources and was buildable with old rpm but you need to find that, rebuild with old rpm, and then you can install the current one. Not exactly nice experience. And it's quite possible that such sources were only present in some bootstrap project and locating them in OBS is pretty much impossible.
My reply here was to
Using a foreign or virtual environment won't let you build, necessarily, for installation on your local machine.
It is clear that at this point the only real solution is upgrading rpm to the latest version using one of our provided packages (possibly via first installing an intermediate rpm version) then optionally using that package to rebuild itself and going from there. But at this point i'm really not sure why we are still discussing it on this list as what is being done here is far from any form of supported openSUSE system.
Also from your analysis in your other mail it is clear that the rpm package is not months old but much older. According to the report the user did not upgrade for a few months but ended up with rpm 4.11 which is very old - 4.12 was introduced in 2014. So this is clearly some problem with the system - using package lock, having old software installed that prevents the rpm upgrade, or whatever. If you break it you get to keep the pieces. Can't do much about that. Thanks Michal