On 2021/02/23 01:46, Simon Lees wrote:
the rpm-binary that could speak both
formats should have been statically linked so it could run on
both. and would be runnable in the future.
This has been discussed in the past, from an openSUSE perspective
we would be far more interested in a statically linked zypper
From a SuSE perspective upgrading from SuSE 6.x, rpm is far more
in the end because we provide working
upgrade paths for people on standard systems.
So anyone who does any customization or who has brought up a
SuSE system via upgrades from SuSE 6.x or 7.x, is SOL. My system got this
way because I upgraded from old suse and I didn't have the luxury
of doing a wipe+install w/each upgrade. Good thing opensuse takes
care of their longer term dupes, er customers...
I have 4.11.3 on my system and have tried
and then tried building it -- same for 4.15.1 -- though it's in
the new binary encoding, and won't be loaded by rpm's under 4.15
but have you tried using the 4.14.1 to install the 4.15 and then the
4.15 to install the now current 4.16. Then you can use 4.16 to build and
install whatever you'd like.
Unfortunately, tried installing 4.14.1 and then building = 4.14.1
wouldn't install, and building it didn't work either. Same for 4.15.1.
Simon Lees wrote:
From there you can update to the latest rpm
provided in Leap 15.2 and then onto rpm 4.16.0 which is now the version
This matter is complicated by RH and Suse having some binaries
in different locations, as well as moving the rpm-DB and changing
to a new DB format.
Shouldn't be, the openSUSE packages should provide all the migration
needed for this if you install them in the right order.
Ho Ho, Ha Ha...like I can come close to doing things in the 'right'
order -- so far, no order has worked, so I don't know how close I'll get to
the "one true" order. Sorry, but everytime someone talks about the
'right' way, its in hind-site relative to what worked. Plenty of times the
'standard system' was messed up and went one direction in 1 release and
in the next release. If I went with the standard system -- there wouldn't
have been zero chance of upgrading without a complete reinstall, multiple
So please understand -- standard system has required complete reinstalls
in the past. You are absolutely right in that I don't have a standard
Meanwhile, for key pieces of SW like a
they really should be statically built-to-last.
Well the supported way to update a system is `zypper dup` we will make
sure that works there should rarely be a need for an openSUSE user to
call rpm directly, especially when installing / removing / upgrading
Um, where are the .repo files I need to add to zypper for it
to read the current dist? I've been using the repo/repodata/repomd.xml
for my own local cache and building a repository with that locally,
but without downloading that first, zypper seems unhappy:
Error building the cache:
] Valid metadata
not found at specified URL
Warning: Skipping repository 'TW-OSS' because of the above error.
Tried repo/repodata (included --check in the zypper command and
it *claimed* it was successfully added:
sudo zypper ar --check http://download.opensuse.org/tumbleweed/repo/oss
Adding repository 'TW-OSS'
Repository 'TW-OSS' successfully added
Enabled : Yes
Autorefresh : No
GPG check : Yes
URI : http://download.opensuse.org/tumbleweed/repo/oss