* Carlos E. R. <robin.listas@telefonica.net> [02-20-23 13:46]:
On 2023-02-20 18:44, Per Jessen wrote:
Patrick Shanahan wrote:
* Carlos E. R. <> [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 :-)
xrdp broke recently.
I don't use it.
smb broke last November.
not for me.
Pipewire also broke in November.
not for me.
xrdp possibly also broke last October.
mlocate broke in February, but it also affected Leap.
not for me
digikam broke on August 2021
I didn't experience that but seldom utilize digikam.
systemd also broke that month
no
Just a quick search for the word "break" in TW posts. It is not criticism nor FUD. It is a feature, a expected thing to happen in development of anything.
when <users> say "break", it doesn't mean TW broke but that <user> experienced problems, but quite frequently, maybe most of the time, problems of their own doing. you cannot equate "break" to a user's system problem unless the break was caused by packages issued by openSUSE. statistics only reveal what is desired by the person stating the statistics. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet oftc