Comment # 9 on bug 953769 from
Hello there, okay maybe I misunderstand all the involved wording and terms
here, but only stuff I care for about is actually is:

if it is still true that opensuse is supposed to be supported by directly going
from N release to N+1, then this bug is a clear and absolute valid bugrepot as
a system utterly fails when coming from the direct predecessor 13.2 going to
the direct successor 42.1

I have demonstrated this behavior and I have reported as extensively as I could
possibly do.

I am really annoyed pretty much about these constant mess situations that
opensuse is getting me into, even such basic things are suddenly messed such as
a simple networking interface.

Does anyone actually *DO* test a clean N release of opensuse and moving it
forward to the N+1 release *BEFORE* release or is it always *ME* who is finding
these basic but completely unnerving bugs that completely kill the usability of
a linux machine running opensuse?

Also: suse enterprise or whatever, will we have this or a similar inverted bug
the next suse/enterprise/open release when all of a sudden everybody is then
bending over backwards and goint back to enpXsY networking names again? maybe
in the next release of opensuse or the following one? Is this a likely scenario
or outcome of the future development of opensuse?

also why the heck did we ever go to enpXsY if it never was necessary to begin
with?

i can really not recommend opensuse to anyone not because of the failing
rocketscience and brainsurgery technology that is being used but because of the
most simple basic things that are failing.

this cant be right. please do tell me if it still makes sense to stick with
opensuse.

thanks.


You are receiving this mail because: