On 01/03/2013 04:01 PM, "Jóhann B. Guðmundsson" wrote:
I assume you are not using encrypted partition

I do.

Given that we are already that far behind the schedule few more months
hardly matter or at least delay the release up to the point this issues
are fixed.

Yes it does. Many already upgraded to F18, and would like to see normal operation of F18 updates repositories.

What is not right here while the distribution has significantly
increased in size the release cycle has not been extended to accommodate
for that ( amongst other growth pain we suffer from )

Numbers? Has critpath really increased that much?

On 01/03/2013 03:50 PM, drago01 wrote:
> After the release does not help people that upgraded on release day
> and found themselves unable to unlock there harddrive or log in.

Oh come on, fedup doesn't delete the old kernel, you can still boot with the F17 kernel and fix up the keyboard mess.

I've upgraded quite a few machines already, all with non-US locales/keymaps, and while slightly annoying, it was easy enough to fix up afterwards.

Just document what to do eg. on the fedup wiki page (you need to read this page anyway, I doubt anyone will be able to use fedup without consulting the instructions there, and there are already instructions on how to fix up grub after the upgrade).

I have _never_ been able to upgrade a single fedora release without some minor manual fixing afterwards, and I do that since fc1. I find that acceptable. Though I value hints on prominent places, such as FAQ wiki pages, etc. My impression is though that it's gotten a lot better in the recent couple of releases.

There are other annoying problems, like broken upgrade path for kdelibs, which should be solved magically by finally releasing fc18.

So +1 (or more) from me for
- releasing fc18 soon
- document workarounds for keyboard issues
- continue working on long-term solutions for keyboard layout setting, like the one Lennart outlined.

Tom

--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

Reply via email to