On Mon, May 14, 2007, Caleb Epstein wrote:
> On 5/14/07, Ralf S. Engelschall <[EMAIL PROTECTED]> wrote:
>
> > Sorry, I've no clue what caused this problem for you.
>
> Weird. I generally just do
>
> % openpkg build -UakK | sh
>
> Might this have any/something to do with it? I tried removing the
> package, and the .dmp file was indeed removed. Perhaps its something
> in the way the upgrades are done?
>
> I notice that if I do:
>
> % openpkg rpm -e xemacs
> % openpkg rpm -Uvh <old xemacs rpm>
> % openpkg rpm -Uvh <newer xemacs rpm-but-same-release-number>
>
> The second upgrade fails unless I specify --force, in which case I am
> left with a single xemacs package installed, but the .dmp files for
> both versions.
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...
Ralf S. Engelschall
[EMAIL PROTECTED]
www.engelschall.com
______________________________________________________________________
OpenPKG http://openpkg.org
User Communication List openpkg-users@openpkg.org
