This is against an old rpm (4.0.2) but I think this behaviour hasn't changed
in a while.
If I have a directory with bash.rpm
and someone builds newbash.rpm with Obsoletes: bash.rpm
things works as expected:
rpm -U newbash.rpm
Now, unless something very wonoky happened, I think I think I saw
rpm -U bash.rpm succeeding (the files don't conflict).
Is that possible/normal?
In that case, I put both Conflicts: bash.rpm / Obsoletes: bash.rpm
But if I do that, rpm -U newbash.rpm should still work, however, if someone
tries rpm -U bash.rpm, should it just be a no-op that won't cause an error,
or would it try to install bash and then fail due to the conflict?
Yes, I can build dummy packages to try all this, but at the same time I want
to make sure I understand expected (not observed) behaviour as well as well
as what is recommended in case like this.
"A mouse is a device used to point at the xterm you want to type in" - A.S.R.
Microsoft is to operating systems & security ....
.... what McDonalds is to gourmet cooking
Home page: http://marc.merlins.org/
Received on Mon Nov 16 01:32:10 2009