fedora 11 worst then ever release

Ralf Corsepius rc040203 at freenet.de
Mon Jul 27 06:12:57 UTC 2009


On 07/27/2009 07:33 AM, David Cantrell wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On Sun, 26 Jul 2009, Björn Persson wrote:
>
>> Ralf Corsepius wrote:
>>> On 07/26/2009 02:37 PM, Seth Vidal wrote:
>>>> On Sat, 25 Jul 2009, Alan Cox wrote:
>>>>> "all of my system has a wrong openssl version"
>>>>>
>>>>> all these symptoms sound like your upgrade went horribly wrong. I've
>>>>> seen preupgrade mash up a box by half upgrading like that. It's the
>>>>> main
>>>>> reason
>>>>> I don't think preupgrade is actually safe to use yet.
>>>>
>>>> Preupgrade's process is to depsolve - using the same method anaconda
>>>> does, download the pkgs it solves out. Put them in a cachedir. Download
>>>> a kernel and an initrd, Setup a ks.cfg. then reboot the machine and
>>>> allow anaconda to do the install.
>>>>
>>>> Specific issues we've had with preupgrade are related to not being able
>>>> to find a mirror and/or not being able to get pkgs.
>>>
>>> Mine were
>>> * preupgrade running out of diskspace on / when trying to fill
>>> /var/cache/yum (my "/"'s tend to be minimized/small)
>>
>> You're not blaming Preupgrade for the partition being too small, are
>> you? If
>> you want a small root partition you should put /var/cache/yum on another
>> partition.
>>
>> Do you mean Preupgrade didn't handle the lack of disk space well?
>>
>>> * anaconda failing during reboots due not being able to process fstab
>>> correctly (FC11's anaconda misparses fstab and is unable able to process
>>> bind-mounts nor nfs-mounts).
>
> Bind mounts are fixed, as far as I know:
> https://bugzilla.redhat.com/show_bug.cgi?id=496406
>
> For NFS mounts, I believe it's fixed in commit
> 40728ffcc1e32eb6b5ccc0cd3b3ddb23216cf199, which was on June 7th. That
> should
> carry over NFS mounts listed in /etc/fstab if you are doing an upgrade.
Well, to my knowledge these are "FIXED RAWHIDE", only.

>>> * anaconda's depsolving failed when upgrading an FC10 + FC10-updates
>>> system due to NEVR issues.
>
> If you have any details of the failure, it would help.
Unfortunately no. I had not been involved into upgrading the system this 
had happened to from the beginning.

I was called to troubleshoot this upgrade. The situation I found was a 
partially upgraded system, stuck on upgrading yum due to a rpm conflict 
on yum itself. No idea how the person trying to upgrade managed to get 
into this situation.

Ralf




More information about the fedora-devel-list mailing list