Shibboleth Developers

[Digant C Kasundra <>]

--On Thursday, November 09, 2006 10:14 PM -0500 Scott Cantor 
<> wrote:

> > I'm trying to keep up with the RPMs (we resign and keep them on our
> > local  Satellite server) but I'm having problems because release numbers
> > aren't  being properly incremented.
>
> Nothing (codewise) has changed, so I didn't increment anything. All I did
> was setup a new staging area and sign the files.
>
> > Looking in the current source RPMs directory
> > on the site, I see the xerces-c release 2 package with a timestamp of
> > Nov  8th, making it the 3rd release 2 xerces-c package I've seen.
>
> If the RPM release number isn't incremented, it hasn't changed. That much
> I will promise. I can't promise the timestamp will be the same forever. If
> that's a requirement for you, I'm sorry, but I'm not willing to guarantee
> that.
>
> -- Scott

The timestamp thing is fine.  We had some local tools compiled against 
xerces-c.  I had two rpms with the same version and release number.  The 
tool complained about one of the symbols being a different size in the 
shared object with the newer RPM with a build date of Oct 6, but executed 
fine with the older RPM against which I had originally compiled the tool 
(build date Jun 05).  This means the two packages are not equivalent and 
should have had a different release number in my opinion.


--
Digant C Kasundra 
<>
Technical Lead, ITS Unix Systems and Applications, Stanford University