F15 preupgrade: lots of uneraseable dupes

JD jd1008 at gmail.com
Mon Oct 10 19:40:38 UTC 2011

On 10/10/2011 11:54 AM, Rahul Sundaram wrote:
> On 10/11/2011 12:13 AM, JD wrote:
>> Preupgrade is not a single operation solution. The
>> user is expected to know several complex operations
>> and execute them in right order.
> Nonsense.  It is a point and click gui.
>> A yum upgrade script would be a single point solution
>> that a user could run. If problems, then user could report
>> the results, along with a log file that a script could leave
>> behind. That is a very desirable solution for all non-techies
>> and newbs.
> I still cannot see you explaining what exactly is the problem a script
> is supposed to solve.  Unless you have a good problem statement, you
> have zero scope of a solution.
> Rahul
I tried preupgrade.
I tried upgrade via DVD.
I tried upgrade via yum according to
All of them failed to upgrade the system to full F16.
Upgrading via all these methods left hundreds of
F14 packages in place, even though they were
installed via yum update from fedora updates
repository, for which F16 updates were indeed
identified by yum, but at the same time yum would
then say "Not found".
I had taken care to disable other repo files, such as
rpmfusion, adobe, google, skype, atrpms so as not
to get a whole bunch of errors unrelated to upgrading
from fedora repos.

So, if upgrading is such a complex and trouble
prone operation, what should an ambassador's
message to the world be regarding this issue?
That it can be done but it is fraught with problems
and dangers of rendering your system unreliable
at best, and (in my case) leaves you with a corrupted
rpm database and unable to login via the gnome login

I believe you and other fedora developers, and
protagonists can and should do better to produce
such a script/utility.

As a side note:
I also run several systems with various versions of
windows - all of them have many third party software
(kind of akin to fedora users installing form other rpm
repos like fedorafusion and atrpms) - I have never
run into such show stopper upgrade problems with
these systems. Almost every upgrade failure was due
to an undetected malware, or a disk having become marginal.
Pls. do not misconstrue this. I am not trying to pit us
against them. I am only saying that upgrading should
be a completely trouble free operation, and that Fedora
devs can indeed fix this problem via a script or even
as you say, a point and click solution, which in it's
current incarnation, does not work.



More information about the users mailing list