Robert Moskowitz wrote: Hi,
Miika Komu wrote:Robert Moskowitz wrote: Hi,Miika Komu wrote:Robert Moskowitz wrote: Hi Robert,I am finally at the point where I have a new set of rpms (newer patch level) to apply to a system.excellent!Problem is there is no change in the rpm name, so yum does not see anything to update (even if the file create date is more recent).The RPMs are like this: /usr/src/redhat/RPMS/i386/hipl-daemon-1.0.4-1.i386.rpmIs there a magic yum parameter to get the update applied?Feel free to experiment with the Release number: test/packaging/hipl.spec Version: 1.0.4 Release: 1> Don't want to do an erase then install. Would that not make all new HIs?The configuration files are not managed by yum/rpm. Hipd creates them by itself and removal of rpm does not remove the HIs.Or perhaps the patch number should be included in the rpm name? The SIP communicator project does this with their nightly rpms.I have named the current version as 1.0.4 in anticipation of the next release in the version control. I would recommend that you change your local copy to 1.0.3-2 so that you'd stay in sync with the version numbering.What I would do is change the Release to: Release: 1-patch-1982fine by me if it works for you.I contend this is a bug in the rpm build process. Without a different rpm name with each patch, as far as rpm and yum are concerned it is the same rpm and will not update. With rpm you CAN use the --replacepkg, but with yum your only recourse is to erase and install.The SIP Communicator project does something similar for their nightly builds.
I added an item to bugzilla: http://hipl.hiit.fi/bugzilla/show_bug.cgi?id=704