Upgrading to 19 by fedup: bad and good news

[poma]

On 30.06.2013 14:19, Ed Greshko wrote:
> On 06/30/13 19:28, poma wrote:
>> On 30.06.2013 03:38, Ed Greshko wrote:
>> …
>>> 1.  X not starting...  But this was a simple matter since this is a VBox VM.  Just needed to boot to level 3 and reinstall the VBox addons
>> x86_64?
>> i686 -> https://bugzilla.redhat.com/attachment.cgi?id=758301
>> rhbz#972095
> 
> x86_64.   No big deal.  This isn't the first time this has happened with VBox VM's

True, it isn't the first time the guest additions needs patch&compile,
although this one towards xorg-x11-server per se.

>>> 2.  No F19 kernel.  This was easy to fix by "yum distro-sync".  (Had to erase firefox first....)
>> 'fedup-cli --network' - no problems whatsoever
> 
> It has been pointed out to me that I hit a known issue.   "It's simply that since F19 has been frozen for so long, F18 has a newer kernel in stable. The latest F19 kernels are still only in updates-testing. When the 0-day updates push happens, this will be resolved"

Kernel downgrade mechanism during upgrade should cover this, although
it sounds contradictory. :)

>>> 3.  Still some minor issues with grub....  But no show stoppers.
>> 'extlinux' - no problems whatsoever
>>
> 
> I hit https://bugzilla.redhat.com/show_bug.cgi?id=975800 .   But that was easy to overcome.

Grub2 unnecessarily complicates the whole thing, and not the only one.

> FWIW, no need to place me on the Cc: list to mails to the list.  It actually makes things a bit more cumbersome as with TBird I have to hit "Reply All" to get Fedora in addresses and go back and delete you from the To.

Just for your perfectionism sake. :)


poma