SRPM URL: http://www.stahnkage.com/tmp/epel-release-4-2.src.rpm
Description: EPEL repository configuration and setup
Was wondering if it would be easier to have one generic package to cover
both EL4 and EL5?
Jens, it was planned to use the same package for both. The only differences in
RHEL 5 should be the yum repo file, and a bump of epel-release.
Up2date isn't involved in RHEL 5, so that's a plus. I just submitted this to
get the ball rolling on the epel-release package. I thought it would have to
approved only on EL 4 and then I would bump for EL 5 and build.
I followed the model used by Fedora-release.
You're right: the version only appears in two places... :)
Humm. I can't seem to get to the srpm url... just hangs on me.
Eventually I get:
504 Gateway Time-out
17:18:35 ERROR 504: Gateway Time-out.
Also, is there a spec url?
Nevermind. Now it's working. ;)
Will review this in a bit here...
OK - Package meets naming and packaging guidelines
OK - Spec file matches base package name.
OK - Spec has consistant macro usage.
OK - Meets Packaging Guidelines.
OK - License (GPL)
OK - License field in spec matches
OK - License file included in package
OK - Spec in American English
OK - Spec is legible.
See below - Sources match upstream md5sum:
OK - BuildRequires correct
OK - Package has %defattr and permissions on files is good.
OK - Package has a correct %clean section.
OK - Package has correct buildroot
OK - Package is code or permissible content.
OK - Packages %doc files don't affect runtime.
OK - Package has rm -rf RPM_BUILD_ROOT at top of %install
OK - Package compiles and builds on at least one arch.
OK - Package has no duplicate files in %files.
OK - Package doesn't own any directories other packages own.
See below - Package owns all the directories it creates.
See below - No rpmlint output.
See below - final provides and requires are sane.
OK - Should build in mock.
1. Since redhat/fedora is upstream for this package, can you add
a note as suggested in:
2. The up2date files present a problem. Should up2date be required
by this package (so that the post commands work right)? If so, that would
be anoying to places where up2date was not installed. Perhaps it should
be in a subpackage, only installed by those that have up2date?
Should this package require 'yum' ?
3. Where does the version come from? 4 for epel4?
Is the epel5 version of this going to be version 5?
If so, perhaps there is no need for the dist tag?
4. rpmlint says:
W: epel-release non-conffile-in-etc /etc/epel-release
W: epel-release non-conffile-in-etc /etc/pki/rpm-gpg/RPM-GPG-KEY-EPEL
I think those can be ignored.
W: epel-release dangerous-command-in-%postun cp
Do we need to make a rpmsave there?
5. The description could be a bit more verbose.
Perhaps you could expand EPEL in case there are people who
don't know what it means?
RHEL4 does not have yum it only has up2date CentOS4 has yum so by not
requiring either it will work on both with what comes with the distro.
I really dont think EPEL should have yum for EL-4
Yeah, looking at centos-release and redhat-release, they provide the needed
directories, so there shouldn't be a need for yum or up2date Requires, so cross
Although, it looks like centos-release also provides an apt-rpm source list.
Might be nice for this package to also provide one.
Why do we need a epel-release file in etc? That seems unneeded to me.
This cp in %postun looks dangerous to me, too. Can that be avoided somehow?
My ISP has been having issues, so if you can't get these files downloaded, try
again in 20 minutes or so.
* Sun Mar 25 2007 Michael Stahnke <email@example.com> - 4-3
- Removed cp in postun
- Removed the file epel-release - provides no value
- Removed dist tag as per review bug #233236
- Changed description
That looks good.
The summary seems fine now, but the description is still using epel...
perhaps change it from:
"This package contains the epel repository GPG key as well as configuration
for yum and up2date."
"This package contains the Extra Packages for Enterprise Linux (EPEL) repository
GPG key as well as configuration for yum and up2date."
Other than that nitpick, I don't see any blockers, so this package is APPROVED.
Don't forget to close this once it's been imported and built.
I'll change the description after CVS branch. Thanks!
New Package CVS Request
Package Name: epel-release
Short Description: EPEL repository configuration and setup
Branches: EL-4, EL-5
This package appears to be in now... can we close this review request?