On 09/11/2020 18.15, L A Walsh wrote:
On 2020/11/09 04:04, Carlos E. R. wrote:
On 09/11/2020 13.00, Dominique Leuenberger / DimStar wrote:
...as the payload compression changed, we have always been aware that no matter how long we will make the payload change, there will be some user takign n+1 days until they will update.
Of course! Though am making progress -- am able to build a copy of zstd from the source rpm, but the source rpm gets errors which I haven't sorted out yet.
But at least I can install files via rpm2cpio. rpm2cpio worked before, but produced a zstd-compressed cpio archive. But now I can uncompress that with zstd -d and then work from the cpio archive.
She said the machine was current, then had hard disk trouble for two months. Then it failed to update.
---- Actually I said I was able to install rpm's from from the then current TW stream. However, looking at the rpm on my system shows an unreasonably old, non-tumbleweed version from 13.2. Not sure how that missed getting updated, but that's one cause.
RPM to support zstd payload, still is not lost: the TW instance cna be 'offline upgraded' (i.e. boot the NET install/DVD and pick 'upgrade' in the bootloader. This will use RPM on the DVD/NEt and allow to move to a current TW snapshot).
Well, yeah, basically like doing a reinstall over the old installation without formatting. I'm pretty sure that would result in a non-working (if even bootable) result.
No, this is a documented procedure. It is the same procedure as used to upgrade a machine from 13.1 to 13.2 before zypper dup was invented. And, it can be used as well for emergency recovery of broken systems. Try it out in a virtual machine.
I'm in the middle of moving several partitions, and haven't really dealt with the problem of moving boot+root from 'd' to 'c' in lilo after I remove the old sys-drives.
If you have lilo it is possible that the DVD upgrade could refuse to start.
This is one of the procedures I recommended. She has not commented back yet.
I'd rather not write over everything from my current install. I don't think it would correctly upgrade/update my config files
You would get them converted to .rpmold, or get .prmnew, as with any other update. AFAIK, the procedure never deletes your config files.
Anything else you're trying to do, is out of the supported scenarios, I've had to adapt to various support-scenarios since evaluating and adopting it for the basis of sgi's linux in ~98 or 99. Think I started with SuSE Linux 5.3 for my home machine.
-- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)