On 07/11/2020 05.10, L A Walsh wrote:
TLDR: rpm(s) >= 4.15, can't be read, built or installed by rpm < 4.15 (specifically, 4.11).
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.
...
I.e. I can't install the binary rpm, because it has 8 pre-reqs on other rpm packages that expand to some 30+ packages all that cannot be installed due to the fact that they require the "PayloadIsZstd" rpm feature.
There is another way. Install from a TW rescue system that has your installation as target. One way is to download a current TW DVD, boot it, and try to do an "offline upgrade" on your installation. As it uses its own rpm, it will work. If you allow it to connect to internet, it will use remote packages to install if they are not in the DVD. I'm assuming that the TW DVD doesn't have the upgrade functionality disabled. The other alternative would be to boot the TW XFCE Rescue Stick: <http://download.opensuse.org/tumbleweed/iso/openSUSE-Tumbleweed-Rescue-CD-i686-Current.iso> (burned to an USB stick) Boot it, mount your system under /mnt, and then use zypper or rpm operating on /mnt. This I have not done in a long time, but it should be possible as it is the mechanism used by the installation DVD to do installs/upgrades. rpm: --root DIRECTORY Use the file system tree rooted at DIRECTORY for all operations. Note that this means the database within DIRECTORY will be used for dependency checks and any scriptlet(s) (e.g. %post if installing, or %prep if building, a package) will be run after a chroot(2) to DIRECTORY. zypper: Target Options: -R, --root dir Operates on a different root directory. This option influences the location of the repos.d directory and the metadata cache directory and also causes rpm to be run with the --root option to do the actual installation or removal of packages. See also the FILES section. --installroot dir Behaves like --root but shares the repositories with the host system. HTH -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)