[packagekit] yum: Refreshing cache error

[Robin Norwood]

On Fri, 11 Apr 2008 16:31:35 +0100
Richard Hughes <hughsient at gmail.com> wrote:

> This is a bug that annoys me greatly:
> https://bugzilla.redhat.com/show_bug.cgi?id=439735
> 
> I really want the cache to be refreshed in the backend (like it is
> now) and then for the original action (e.g. search-group) to be
> redone.
> 
> I think Robin did something like this for the yum2 backend, but it's
> too close to the F9 release date to switch backends.
> 
> Could a python legend have a look at this please?

I ain't no legend, but I'll take a look at it today.  I do need some
details, though:

At what point should we 'start over'?  Should I resend signals
like AllowCancel, NoPercentageUpdates (or restart
the percentage update counter at 0?), set the Status as I'm starting
the transaction over?

The trickiest bit is the percentage updates thing - if I restart at 0,
will the backend or UI get confused?

Does it make sense to have a 'Starting over' status signal to let the
engine know?  Or, even more extreme, a 'Try this transaction again'
signal, and just have the engine reschedule an identical transaction?
That would make the backend implementation trivial, but maybe makes
things hard on the engine.

-RN

-- 
Robin Norwood
Red Hat, Inc.

"The Sage does nothing, yet nothing remains undone."
-Lao Tzu, Te Tao Ching