Re: Question regarding jpp6 and jpp5

On Sun, Mar 21, 2010 at 10:41 AM, Jason Corley <[email protected]> wrote:
> Not to belabor the point but if you don't think the rpm query was
> sufficient to show you the problem was resolved, you don't understand
> what the problem was. The basic issue is that rpm.org has released
> multiple incompatible versions of rpm that have been used in various
> fedora versions. Due to the nature of RHEL release cycles none of
> these rpm versions have been in a RHEL released product (as of this
> writing and RHEL 5.4). The point at which things started to become
> problematic depending on usage was the rpm.org 4.6 release iirc, and
> 4.7 and 4.8 have introduced various new incompatibilities. You can
> view their release notes for the gory details. At any rate, a
> 4.4.x(.y.z) built rpm should rebuild fine on at least any version of
> rhel 4.x and up, and I believe it will even work on 2.x and up (though
> I have no virtual machines of those to test).
>
> So for quick reference: no current RHEL release has a rpm version
> greater 4.4, and no recent fedora version has a version less than 4.6.

Thank you, I misunderstood that you were using "RPMVERSION" and not
"VERSION". I'd actually use the more standard lowercase syntax, and
write it like this:

     rpm -qp --nosignature  --qf 'rpmversion
%{rpmversion}\t%{name}-%{version}-%{release}.%{arch}.rpm\n'

Unfortunately for me lately, I'm also dealing with a raft of software
that mislabels their RPM's and for with the name of the RPM file has
nothing to do with the actual package name and so have become a
bit.... touchy about these queries. This includes Sun's JDK RPM's of
course, but also includes VMWare and Centrify packages. I've written
to all of them about it, it's confusing.

> The reason we had problems before is because our buildroots for JPP
> 5.0 are centos based, and when we started 6.0 we had a fedora
> buildroot. We've since reverted to the centos root, and that resolved
> the problem for all new builds. However we may have missed some
> packages in the mass rebuild (always a possibility) so if you see
> packages that either a) don't rebuild, or b) show a RPMVERSION query
> tag of something 4.6 or greater, please let us know so we can rebuild
> it.
>
> Jason

Well, that's easy: I have a local rsync mirror of
rsync.mirrors.dotsrc.org, which I assume is reasonably up to date, and
simply issue this:

prompt> cd /var/www/mirrors/jpackage/6.0/
prompt> find . -name \*.rpm -exec rpm -qp --qf
'%rpmversion:%{rpmversion}\t}' \; -print > /tmp/report
prompt> sort -o /tmp/report /tmp/report

The result isn't pretty. There are hundreds of packages whose RPM
version is much more recent than 4.4. Transforming them to compile
cleanly under a CentOS 5 OS is pretty painful, a lot of Java
components and dependencies have changed over the last 3 years.

Simply building the SRPM's for RHEL 5 compatibility would be helpful.
As long as we all avoid using .spec files that exclude source or
patches if you're on different OS's or architectures, and merely don't
bother to *use* them if you're on the wrong type of system, we should
be OK.