Re: What should go in JPP6, and what as update to JPP5? When is support for RHEL versions dropped?

Nico Kadel-Garcia wrote:
> In the short term, I've published some hooks for this on this mailing
> list. The summary of the RHEL 5 compatibility issues of JPP5 is below:
>   
After a bit of experimentation, I'm part way though downgrading the 
buildroot for jpp6 to use centos5, but as discussed this requires all 
packages built prior to this change to be rebuilt.
I wrote something to rebuild all the jpp5 packages in mock when we 
swapped to using a mock buildroot, so I should be able to do something 
similar for this jpp6 rebuild
> * JPackage often uses ".noarch" packages rather than .i386/x86_64.
> This causes serious confusion when there is an old .i386 version in
> RHEL 5, a new noarch one from JPackagae, and yum tries to grab and
> install the .i386 version as well as the .noarch from JPackage. The
> easy solution is to put entries like these ' in your yum.conf.
>
>        exclude=ant.i386
>        exclude=tomcat5.i386
>
> Hmm. This list would be good to publish.
>   
I personally have not had any issue since I installed the 
jpackage-release package that provides a yum config with the right 
priority stuff in there. Let me know if you are still having issues with 
packages.
> * RHEL 5 obsoleted the 'ecj' package with 'eclipse-ecj'. This causes
> nuttiness, unless you provide an eclipse-ecj of a higher version
> number to displace the RHEL 5 one and eliminate the 'Obsoletes': that
> will allow the installation of JPackage ecj, and satisfy eclipse-ecj
> dependencies. I'm happy to send you a copy of my placeholder .spec
> file for this
>   
Send me the src.rpm and I'll import into CVS and make you the package 
maintainer. Have you been given a CVS account yet ?
> * The java-1.6.0-sun and java-1.6.0-sun-compat packages are seriously
> out of date. Again, I'm happy to send you the copies of my .spec
> files.
>
> In fact, I'd be willing to maintain those now.
>   
Once you have a CVS account, we can let you keep that upto date. 
Publishing the nosrc.rpm packages are a bit of a pain as they aren't 
real packages so need to be dealt with differently and are not part of 
our automated upload system currently

-- 
Will Tatam