On Tue, May 15, 2007, Caleb Epstein wrote:
> 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/
But if the "Release" header has not changed in a OpenPKH CURRENT
package, this means the package is the same and its resulting binary
package content is the same and this in turn means there should be no
problem. The only possibility I see is the 24h window in CURRENT: as
CURRENT uses Release headers of YYYYMMDD it _CAN_ be that an identically
named CURRENT package is still different (two commits to the same
package on the same day). This usually occurs only during package
development, because even on the sometimes happening upstream updates
twice per day the "Version" header is already different. So, I'm still
puzzled what caused the problem for you...
Ralf S. Engelschall
[EMAIL PROTECTED]
www.engelschall.com
______________________________________________________________________
OpenPKG http://openpkg.org
User Communication List openpkg-users@openpkg.org
