[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: fedora 11 worst then ever release



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Mon, 27 Jul 2009, Ralf Corsepius wrote:

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.


That's true.  anaconda is unique in that the only way a new one can be
released to fix installation issues for users is to generate new media.  If
the problem is confined to the second stage of the installer, we can put the
fix in to an updates.img.  We do this for common bugs when a release comes
out, but we cannot spend all of our time constantly releasing updates.img
files:

    https://fedoraproject.org/wiki/Common_F11_bugs

We continue to fix problems reported against Fedora 11's anaconda in rawhide,
but for users needing the fix in the latest stable release, consider Fedora
Unity.  Fedora Unity generates new spins of the latest stable release
including backports of anaconda fixes:

    http://www.fedoraunity.org/

No guarantees of what Fedora Unity contains, but I know they follow the
rawhide anaconda and pick out fixes that work for the latest stable release
and generate new installation media.  You also get the benefit of having all
current stable updates for F-11 rolled up in to the installation media.

- -- David Cantrell <dcantrell redhat com>
Red Hat / Honolulu, HI

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAkptcuEACgkQ5hsjjIy1VklUDwCg3VaxUZcccm4X2io9BffrPWBP
NagAnRS0EuOe/RFaynGENwrN/8RD9kI4
=6ACn
-----END PGP SIGNATURE-----

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]