On 2021/02/21 13:41, Axel Braun wrote:
Am Sonntag, 21. Februar 2021, 21:43:20 CET schrieb L A
One can always have a risc-chip virtual
machine that builds
your repos on your local machine, but that doesn't mean the resulting
binary is installable on your local machine.
As OBS sets up a clean build environment you can compile against targets that
do not match your setup
But that misses the point. The starting point in all of this
was to be able to install current rpm's on my system as I've been
able to do for the past 15 years.
If a package builds+installs on OBS for the iphone, it won't do me
any good as I don't have an iphone.
If the package I would build on OBS, would install, there wouldn't
be a problem, but the rpm's coming out of OBS for TW are encoded in
a new encoding that my existing TW machine+rpm cannot understand/read.
I feel here's the gap: Depending on how 'individual' your system is your
installs on your machine, but on no other.
Having a clean and reproduceable build environment is a *big* advantage in
Not if the binaries built on OBS are encrypted with a key I don't
have. OBS builds rpms compatible with rpm-4.15 or greater. I still have
a pre-4.15 rpm and am trying to upgrade it.
I have also tried building the newer rpm from the sources.
That's not working either. Dominique made a joke about how
she needed to install 'rpm-build' in order to build rpm. But
rpm-build is part of the rpm package. So to build rpm >=4.15, you
need an rpm-build that is >=4.15, but rpm-build is built when you
Doing a build on an OBS system will yield rpm's that are not
readable by rpm<4.15.
If someone has a pre-4.15 rpm, then they can't upgrade to suse's
current packages. They also cannot build or install an rpm>=4.15,
so they can't get to the point of being able to use packages
built on OBS.
The gap isn't about me building rpm's on my machine for someone else's
machine, but is about me building rpm's for my machine. The problem
is that I can't build+install the current rpm to install on my system.