Mailinglist Archive: yast-devel (35 mails)

< Previous Next >
Re: [yast-devel] broken GUI installer
On 2014-04-30 11:57 (GMT+0200) Lukas Ocilka composed:

Josef Reidinger wrote:

thanks for reporting. I investigate code where it happen and something
is strange with mount points.

Bugzilla seems to be better place for bugs. And it's already there,
isn't it?

The first problem with Bugzilla is people don't always make summaries that are readily related to the problem observed, often putting some cryptic string in place of real description. I didn't find anything either about hover, or about loader + unfixed matching my observation/experience.

The second problem is Factory isn't entirely about latest, and one must either remember or guess whether and what isn't current in it in order to decide whether the observed problem isn't stemming from something several versions old and thus most likely known about already, or known to be a build or other transitory problem that might be gone in a matter of hours or a day. So, reporting/asking here e.g. is a way to find out whether it may be recognized as something new, particularly with this Ruby rebuilding of YaST and its dedicated mailing list.

FWIW, notwithstanding bugs, I liked the pre-Ruby installation YaST very much, far and away more than any other OS installer ever used, and am not particularly pleased with the installation simplification changes observed so far.

Also, I'm particularly unhappy that 13 month old https://bugzilla.novell.com/show_bug.cgi?id=663749 has not been implemented, which wouldn't even be needed if there was a checkbox to say new bootloader is or is not to be the master bootloader (aka stanzas for any but new OS desired or necessary).
--
"The wise are known for their understanding, and pleasant
words are persuasive." Proverbs 16:21 (New Living Translation)

Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata *** http://fm.no-ip.com/
--
To unsubscribe, e-mail: yast-devel+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: yast-devel+owner@xxxxxxxxxxxx

< Previous Next >
Follow Ups