💾 Archived View for feldspaten.org › pages › tumbleweed.gmi captured on 2023-11-04 at 11:05:31. Gemini links have been rewritten to link to archived content

View Raw

More Information

⬅️ Previous capture (2023-09-08)

➡️ Next capture (2023-11-14)

🚧 View Differences

-=-=-=-=-=-=-

History of Tumbleweed Upgrades

Hi, here I keep a list of successful and failing Tumbleweed updates. The aim is to have a history log about how stable TW is. I will count the number of successful updates and the number of regressions. An update counts as successful, if the system boots and no major havoc is detected. Regressions are minor glitches, if individual (non-critical) parts of the system broke. The difference between the two, is that a failed update forces me to do a rollback, while regressions allow me still to do my daily work.

Snapshots are not released every day, and neither is my laptop on every single day. This is the reason, why there will be date holes. So, full disclosure: This page serves more of a personal log to allow me track how well Tumbleweed performs and not as a complete testing report about the stability of Tumbleweed updates a a whole.

Updates are grouped in blocks of 10 items.

Regressions are listed with their reference to the corresponding ticket on bugzilla.opensuse.org. For instance, boo#1234567 refers to https://bugzilla.opensuse.org/show_bug.cgi?id=1234567

Reported to Reddit and Blog (201 success, 5 skipped, 6 reg)

Note: Happy to have the recent snapshots skipped and thus avoided bsc#1209618

Note for `20230802 to 20230812`:

This update consists of updating ~6500 packages. Apart from boo#1213973, the system still shows some glitches but rolling back would be even more annoying.

I keep going forward from here onwards, but this snapshot was not unproblematic on my laptop. I asked for help for some of the issues and have not filed any bugs there yet. Counting it as regression, as there are some annoyances, but I'm still working on them. Not happy atm.