[hipl-users] Re: rpm naming
- From: Robert Moskowitz <rgm@xxxxxxxxxxxxxxx>
- To: hipl-users@xxxxxxxxxxxxx
- Date: Mon, 8 Dec 2008 12:53:36 -0500
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.rpm
Is 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-1982
Or whatever the last patch of the day is. Thing is the only ways I have
figure out how to find the last patch of the day is to see it scroll by
when running 'tla replay' or running 'tla logs -D' and waiting for the
end of that long list...
I have intentionally delayed the release (again) so that we can work
out some known issues with the dnsproxy (689, 698, 701, 702 and 703).
I want the release to be as stable as possible.
Btw, there are some notes doc/HACKING on running your own repo
(RETRIEVING HIPL PACKAGES FROM A REPOSITORY) but I am sure that you
are already familiar with such things.
I have my own local repo maintained with createrepo.
I will have to read your docs and compare. Perhaps I have some tips! Nah...
Other related posts:
