On 2/21/23 04:14, Per Jessen wrote:
Patrick Shanahan wrote:
* Carlos E. R. <robin.listas@telefonica.net> [02-20-23 04:54]:
Well, often when TW breaks because the developers have done some change that users don't know about, the only place to possibly ask is the factory list, as devs and packagers are the only people that may know what is going on. Users ask in the users or support list, and nobody knows for days, because devs don't read there.
please cite examples of "when TW breaks"
One of my TW systems broke only just three weeks ago. After a 'dup', the initrd was not re-built correctly, the system did not boot up. No need to solicit support, although I screwed up when trying to boot a rescue system - I picked 64bit instead of 32bit :-)
your continuing ranting about TW being unstable is FUD!
Maybe not quite - TW _does_ break, there are simply way too many things that are not being tested in openQA. Not a criticism, just a fact.
and factory is not the *only* place to seek help with TW difficulties, it is *not* the place.
True, most of the time it is the wrong place for a user-only to seek support. The thing with TW is - it is for users who have a penchant for tinkering and who don't mind spending the time.
In my limited opinion of course. I keep TW on two uncritical systems, if they happen not to work for a week or two, it doesn't matter.
In my experience occasionally tumbleweed breaks, but never bad enough that I haven't been able to just roll back to a previous snapshot and have it work again. -- Simon Lees (Simotek) http://simotek.net Emergency Update Team keybase.io/simotek SUSE Linux Adelaide Australia, UTC+10:30 GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B