Somebody who can edit the wishlist page - please add rsyslog to the list:
It looks like Fedora is moving towards rsyslog, it's already in the development tree, it would be nice to have it in EPEL.
Thanks,
Florin Andrei wrote:
Somebody who can edit the wishlist page - please add rsyslog to the list:
It looks like Fedora is moving towards rsyslog, it's already in the development tree, it would be nice to have it in EPEL.
Done.
Rahul
On Thu, Sep 27, 2007 at 09:56:25PM +0530, Rahul Sundaram wrote:
It looks like Fedora is moving towards rsyslog, it's already in the development tree, it would be nice to have it in EPEL.
Done.
I already use it (1.18.0-1) on a RHEL5 system, seems to work ok.
The package has to be adapted on a few places to allow it to be installed along with sysklogd (I guess that should be the goal?). What I did:
- Provides and Obsoletes lines have to be disabled. - Chang "2345" to "-" in the init script (not started by default) - Comment out all line in the logrotate file (conflicts with sysklogd). - Don't execute the migration stuff (mv's) in %post.
Then it can be installed together with sysklogd and when someone wants to enable it, one has to do:
- chkconfig syslog off - chkconfig rsyslog on - comment out lines in syslog logrotate file - uncomment lines in rsyslog logrotate file
Jos Vos wrote:
On Thu, Sep 27, 2007 at 09:56:25PM +0530, Rahul Sundaram wrote:
It looks like Fedora is moving towards rsyslog, it's already in the development tree, it would be nice to have it in EPEL.
Done.
I already use it (1.18.0-1) on a RHEL5 system, seems to work ok.
We're testing the 1.19.2-1.el4.rf from http://dries.ulyssis.org/rpm/ on RHEL4 32 bit. So far so good.
The package has to be adapted on a few places to allow it to be installed along with sysklogd (I guess that should be the goal?). What I did:
Today I grabbed the latest rsyslog-1.19.6-2.fc8.src.rpm from Fedora Development and rebuilt it on RHEL4 32bit. Seems to work fine after very summary testing. Perhaps that should be the reference used for EPEL? Anyway, mainstream just released 1.19.8 today.
I did notice it does not chkconfig off the syslog service after it's installed.
On Thu, Sep 27, 2007 at 03:55:59PM -0700, Florin Andrei wrote:
Today I grabbed the latest rsyslog-1.19.6-2.fc8.src.rpm from Fedora Development and rebuilt it on RHEL4 32bit. Seems to work fine after very summary testing. Perhaps that should be the reference used for EPEL? Anyway, mainstream just released 1.19.8 today.
Does EPEL have rules about what packages EPEL packages can be based on? I mean: should EPEL packages be based only on non-test Fedora src.rpm's? This would mean that EPEL package for rsyslog can be released after F8 is released.
I did notice it does not chkconfig off the syslog service after it's installed.
Question is what to do when adding a package (rsyslog) that in fact obsoletes a regular RHEL5 package (sysklogd). Personally, I would opt for what I did: make sure installing the (rsyslog) package does not affect anything related to regular RHEL5 packages (sysklogd) and let the sysadmin do the config work afterwards (in this case doing two chkconfig commands and editting two logrotate files).
P.S. Sorry if I raise issues that are already decided in EPEL guidelines. Feel free to point me at the relevant docs :-).
On 28.09.2007 01:07, Jos Vos wrote:
On Thu, Sep 27, 2007 at 03:55:59PM -0700, Florin Andrei wrote:
Today I grabbed the latest rsyslog-1.19.6-2.fc8.src.rpm from Fedora Development and rebuilt it on RHEL4 32bit. Seems to work fine after very summary testing. Perhaps that should be the reference used for EPEL? Anyway, mainstream just released 1.19.8 today.
Does EPEL have rules about what packages EPEL packages can be based on? I mean: should EPEL packages be based only on non-test Fedora src.rpm's? [...]
Fedora IMHO for EPEL is kind of "testing ground" (just like it is for RHEL). Having similar Specs used in EPEL and Fedora also makes exchanging bugfixes a whole lot easier.
Thus it IMHO would be best for all if the EPEL spec file is based on the Fedora one. But that's not a hard requirement.
I did notice it does not chkconfig off the syslog service after it's installed.
Question is what to do when adding a package (rsyslog) that in fact obsoletes a regular RHEL5 package (sysklogd).
One of the (in parts unwritten IIRC) rules is: don't disturb the distribution we build for (e.g. RHEL in this case). So obsoleting is a no go.
Personally, I would opt for what I did: make sure installing the (rsyslog) package does not affect anything related to regular RHEL5 packages (sysklogd) and let the sysadmin do the config work afterwards (in this case doing two chkconfig commands and editting two logrotate files).
That should be fine.
CU knurd
Jos Vos wrote:
On Thu, Sep 27, 2007 at 09:56:25PM +0530, Rahul Sundaram wrote:
It looks like Fedora is moving towards rsyslog, it's already in the development tree, it would be nice to have it in EPEL.
Done.
I already use it (1.18.0-1) on a RHEL5 system, seems to work ok.
The package has to be adapted on a few places to allow it to be installed along with sysklogd (I guess that should be the goal?)
Would you be interested in being a EPEL contributor?
Rahul
On Fri, Sep 28, 2007 at 04:28:32AM +0530, Rahul Sundaram wrote:
Would you be interested in being a EPEL contributor?
Maybe... :-)
epel-devel@lists.fedoraproject.org
-
Florin Andrei -
Jos Vos -
Rahul Sundaram -
Thorsten Leemhuis