[Server-devel] recover from broken yum transaction

[Martin Langhoff]

On Fri, Sep 12, 2008 at 3:01 AM, Seth Vidal <skvidal at fedoraproject.org> wrote:
>>  - Is it safe to run at boot time via an init script?
> as long as the network is up, it should be.

That is not very useful for us. I don't worry so much about the
machine being killed in the 'download stuff' part, bit AFAIK that's
not part of the 'transaction'. When yum-complete-transaction is
called, I am expecting it to work with the RPMs it has, and ensure
anything it was trying to do gets done...

WRT networking, in places like Peru my rule of thumb is that 50% of
the servers will _not_ have internet. Package installations / upgrades
are very likely to happen by sending out USB keys with a bunch of
RPMs, and a GPG-signed script that triggers the yum process.

yum supports -C... can yum-complete-transaction support -C as well?

>>  - Is there an easy way to check for pending transactions?
>
> yum-complete-transaction checks for them itself

Yes, though it's useful to be able to check that for logging/reporting...

>>  - Does it have useful exit codes indicating whether it's done anything?
>
> If the results codes are not good enough we can fix that easily enough.

I am asking because checking the manpage and reading the source did
not give me any hints as to exit codes. Neither does 'man yum' talk
about exit codes except for the "check-update" command.

So I wonder what's the expected behaviour WRT exit codes for yum?

>> Is that different from `package-cleanup --problems` ?
>
> --problems reports a different set of things - package conflicts and
> unresolved deps. A dupe is not, implicitly, a problem. it CAN be, but it
> is not always.

Right - that's lower priority for my use cases. Thanks for the hint.

cheers,



m
-- 
 martin.langhoff at gmail.com
 martin at laptop.org -- School Server Architect
 - ask interesting questions
 - don't get distracted with shiny stuff - working code first
 - http://wiki.laptop.org/go/User:Martinlanghoff