On 2021/03/09 18:23, Neal Gompa wrote:
First: You should be updating your Tumbleweed system continuously.
If a disk controller hadn't wreaked havoc on the main and backup arrays, this issue wouldn't have been near the problem that it became. Nevertheless, I wasn't aware of how fragile or vulnerable a tumbleweed system would be nor that it would be a fulltime job to keep such a system running, especially given the number of breakages in functionality and compatibility associated with suse's bleeding edge. Just to upgrade from release to release took months as I reviewed new changes as I applied them in upgrading my server.
Second: If you're really struggling to update your system because of the compression change, then you can bootstrap an upgrade by downloading a container rootfs[1][2], extracting it, bind mounting your main rootfs into a directory in it, and using the container's RPM + Zypper/DNF to do it.
DNF? The main problem there is a matter of assessing the effects of something like: 1302 packages to upgrade, 2324 to downgrade, 1025 new, 299 to remove, 243 to change vendor, 19 to change arch. on a working system and how well one might trust all package upgrades to be done seamlessly such that system downtime would be negligible.
Third: Your quoting style is weird and breaks my client. How are you doing this and why?
How am I doing this? I use the mystical powers of Thunderbird replying in text mode, um...I really don't know what you are talking about. You aren't trying to use google's web client are you? I had all sorts of grief when I had to rely on it for a few months while my server was down. Google tends to play loose with Internet (and mail) RFC's/standards...