On 2018-06-14 10:42, Ancor Gonzalez Sosa wrote:
On 06/13/2018 07:56 PM, Carlos E. R. wrote:
On 2018-06-12 13:53, Stephan Kulow wrote:
On 06/12/2018 11:42 AM, martin(a)pluskal.org
That being said I would like to express my hope
that people interested
in manually testing Leap before release realize that last week before
release is a bit late (if you expect to have some impact on what is
released as iso).
I actually doubt seriously that any of the linked bugs slipped
Yes, some did.
Well, that's at least questionable for the examples you have provided. :-)
I tested a few betas as fresh installs in my laptop, and there was a
missing feature I needed: importing the existing partition layout (from
reading fstab). This lack made installing on existing computers more
cumbersome, as partitions have to be entered one by one manually. So I
used zypper dup instead.
"Needed" is a too strong word here. It's true that without the
Mount Point" button you have to manually select all the partitions you
want to reuse. Something like 10 extra clicks. So that button was a
convenience to save clicks, but its absence is far from being a stopper
for testing the installer (that's why it was not implemented at the
Ten extra clicks per partition.
In this system there are 55.
Ok, I may not need all of them at start, I can edit them back when the
system runs importing some fstab from backup copy myself. So say I enter
5 partitions manually: that's 50 clicks, and several strings to type
(label perhaps and mount point). Say quarter an hour extra.
Enough to decide for zypper dup instead.
was added late in the process, I didn't notice when, with
the result that I did not test it.
We can agree then, this is again about late testing and not about the
bugs being introduced late.
No. A bug that was not discovered because the feature was introduced too
late for being noticed, and possibly in a hurry.
In fact, I failed to do late testing of the final ISO betas, or I would
have discovered those two bugs
Well, two serious bugs crept in late and I failed
to discover them :-(
a) YaST crashes if there are encrypted partitions listed in fstab
If I'm not mistaken, this bug didn't slip in the last moment. It was
probably there since the very beginning (by the way, it may be that your
description makes it sound more severe than it was).
Well, my testing in the same computer did not detect it previously. In
fact, mounting existing encrypted partitions failed before because yast
did not write crypttab. Possibly when this bug was corrected the other
b) YaST can
select ALL existing partitions for formatting, including
/home and other data partitions, with the result of data destruction.
b2) sometimes it formats none, which is also catastrophic.
I don't think (b2) is true. The partitioner in Leap 15.0 always formats
ALL reused mount points.
It happened to me in a virtual machine where I tested for this bug.
In previous versions there was an extra checkbox
labeled "Format System
Volumes" to control all that. The exact behavior depending on the
concrete partition and the value of that checkbox turned out to be
I say it is a dangerous bug.
If it is a conscious decision, put a warning in red.
Till someone at IBM gets his home deleted and complains, as happened
once years ago. Then you people changed the code fast :-(
Cheers / Saludos,
Carlos E. R.
(from openSUSE, Leap 15.0 x86_64 (ssd-test))
To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org
To contact the owner, email: opensuse-project+owner(a)opensuse.org