On 2021/03/13 01:31, Jan Engelhardt wrote:
Have a good start:
--- FWIW, I saved this aside for reference. I'm having too much fun "playing" with my pkg-dl-script alternating with attempts to build later versions of rpm from leap (15.0 to start with). That seems to be mostly installed, though only lightly tested w/rpm @ v4.14.1, "mostly"...had to give up on beecrypt for now. Even if the leap versions don't have the new compression scheme (dunno if they do or not), they will have a later rpm version that can handle newer build constructs. I do have the compression lib d/l and installed as a separate util. I can use that with 'rpm2cpio' to uncompress and install a new-fmt cpio archive, so I'm also making progress though almost certainly via a more circuitous route (I get distracted easily) like going via leap and a repo-mirroring script that mostly works for TW+leap. I _had_ a shell script to download release-based repos, but with a different set of versions for many rpms, I needed to move to downloading by a dated-list (in primary.xml) of rpms rather than downloading a directory (like oss/x86_64) so I could have a matched set of downloads as existed on a specific day. Backporting that to work with a version-based release was my next stop toward possibly side-grading back to leap, since TW is more unstable than I think I can deal with. In regards to stability, I'm mostly talking about upgrades breaking something: since TW upgrades stuff daily and leap every 'N' months, There's at least 20+ TW releases/month which multiplies chances of breakage considerably. Nevertheless, steps to upgrade an old TW with some repo -- maybe Bernhard's certainly is likely to be more direct than my unprioritized meanderings.
Once done, both rpm and glibc are new and it's back to standard business.
Standard? Thanks for the reference...