|Main Archive Page > Month Archives > fedora-users archives|
On 10/10/2011 12:28 PM, Rahul Sundaram wrote:
> On 10/10/2011 09:48 PM, JD wrote:
>> On 10/10/2011 08:49 AM, linux guy wrote:
>>> I had the same problem, for some reason, on one of my machines.
>>> On that machine I upgraded from the full install DVD instead of doing
>>> a yum preupgrade. Actually, I did the later, but it failed.
>>> Anyhow, I believe I ran a yum check all> list.txt and then edited the
>>> file and then used it as input to yum itself.
>>> It was a terrible, terrible process.
>> I wonder if this thread plays well into the idea
>> that upgrading using yum should be scripted by
>> an expert so that us mortals do not have to slog
>> through this mud :)
> It might be that Preupgrade has bugs. Reporting them and getting it
> fixed would be the first choice rather than replace it with a script
> which will likely have bugs as well. It is not realistic to believe
> that you can write a script to handle upgrades and not have bugs.
> Upgrading a distribution is a fairly complex process to say the least.
In addition to this problem the kernel installation only partially
worked. No modules installed, no initramfs. Solved by getting the kernel
rpm and reinstalling.
But reporting bugs on preupdate is tough. This is a remote machine. I
have no clue what caused this (these) problem(s).
-- users mailing list email@example.com To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines