On 2020-11-06 20:10:54 -0800, L A Walsh wrote:
TLDR: rpm(s) >= 4.15, can't be read, built or installed by rpm < 4.15 (specifically, 4.11).
Hmm this really depends on what "reading" exactly means (querying the rpm metadata or extracting the (compressed) payload (for instance, via rpm2cpio) should work).
On 2020/10/29 03:55, Simon Lees wrote:
I asked:
I don't suppose anyone thought about how users who missed a few months of internet connectivity might resync or make use of the new format rpms if they can't even install + build source-rpms.
I'm not sure how much we claim to support building openSUSE rpm's as source rpm's on there own. openSUSE rpm spec files often depend on variables that are defined in project config files in open build service, as such just using rpmbuild may result in packages not building or building with different configurations.
But is *installing* "rpms" from tumbleweed, with "rpm" on a tumbleweed install, supported?
The reason I was trying to build _rpm_ from source is to get an rpm with the "PayloadIsZstd" feature, since my local rpm doesn't have that feature. It really wouldn't help to build rpm on OBS if it would just give me an 'rpm' that I can't install on my machine due to prereqs.
Just rebuild it and disable/choose a different payload compression. For instance, adding something like this to the spec file disables payload compression for the binary rpms: %define _binary_payload w.ufdio Marcus -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org