On 5/15/07, Ralf S. Engelschall <[EMAIL PROTECTED]> wrote:
That's exactly the exceptional case I've talked about: if you do a forced upgrade from an old RPM package to a new RPM package BUT BOTH HAVE THE SAME VERSION/RELEASE NUMBER, RPM 4.2 usually doesn't correctly remove files of the old RPM which are no longer in the new RPM. I'm faced with this situation often during package development. But usually it should never happen when you work with the official OpenPKG RPM packages as they have a steadily increasing RELEASE number...
This is less exceptional than you might think, esp. when running CURRENT and doing regular updates. Packages are often rebuilt due to some dependency or build-dependency having changed, but the dependant package RELEASE hasn't changed. I think thats what I'm running into/ -- Caleb Epstein ______________________________________________________________________ OpenPKG http://openpkg.org User Communication List openpkg-users@openpkg.org
