Craig White wrote:
On Sat, 2009-10-03 at 13:07 -0400, Bill Davidsen wrote:
I'm just not buying Bill's concept of breaking and never digging
out.
That's your choice, I think Tait Clarridge hit the method to downgrade
first,
then rerun the upgrade. In another forum (chat room) someone said that
the yum
'clean' had been used, then upgrade succeeded in fixing the system.
Both of those suggestions indicate that "using only the 'upgrade'
command" isn't
the way to get things sane again. If it worked for you, fine, but I
still put
Tait's suggestion in my tricks folder, seems a robust thing to do,
rather than
repeating the unsuccessful upgrade.
----
it's about the assumption...
if a yum clean metadata fixes the issue, then it is not an issue that is
problematic for everyone but only those whose metadata contains a
package list of updates that won't work...it's a local problem.
The fact that multiple people had the problem, and several people had it on
multiple machines, seems to make it a 'common problem,' and since it was caused
by a dependency error in the repositories which certainly was not local.
I can assure you that neither I nor most have had to 'downgrade' in
order to upgrade.
Well that clears it up, if you don't have the problem it doesn't matter how many
other people have it, it's unimportant. The rest of us don't count, and
shouldn't clutter the list with solutions to any problem you don't personally
have, and if we don't load the same metadata you do that's our fault.
--
Bill Davidsen <davidsen@xxxxxxx>
"We have more to fear from the bungling of the incompetent than from
the machinations of the wicked." - from Slashdot
--
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
