> When are we going to solve the problem with the -F feature of rpm saying
> "package <whatever> is already installed", and refusing to "freshen" all
> the other new packages given as arguments?
Good question. I still wait for a reply on my e-mail from last
tuesday...
> This makes it very hard to update system every night, making the
> debugging of cooker much more cumbersome and problematic, not to say
> "manual" also ;-).
Yes, confirmed. "Freshening" a running system is now a pain!!!
> I think this has been there for like two weeks now ... it this out of
> your control?
Seems to be a problem with the original rpm tars:
CHANGES under section "3.0.4 -> 3.0.5"
- internalize --freshen (Gordon Messmer <[EMAIL PROTECTED]>).
E.g. in "depend.c" there is around line 631 the comment:
/* FIXME: handling upgrades like this is *almost* okay. It doesn't
check to make sure we're upgrading to a newer version, and it
makes it difficult to generate a return code based on the number
of
packages which failed. */
Anyone who will fix this???
So long,
Juergen
