Bug 740200

Hello. I have an testing version ready in my git tree. I can push it to EPEL, just don't have time to test it now. Can you test it?

There are some problems with upgrades from p4n 0.4 to 0.6, so this can be done for EL6 and Fedora 17 (maybe 16) only.

Hi Jan,

what are the upgrade issues?

Thanks.

Read p4n upgrade notes:
http://docs.pnp4nagios.org/pnp-0.6/upgrade

At least you need to update nagios acttion_url paths.

If you can help me to make automatic scripts, which will fix this for all users
or make some compatibility redirects, we can consider pushing to older distros too.

But for EL-6 question is different. Can you test this new package on EL-6 or fedora-devel?

I may give a look at the action_url path retro compatibility.

How will you package kohana? With another package or in the same package?

Kohana is in same package yet, but I can move it to separate subpackage, if you wish.

I was wondering if there were epel restrictions about bundling packages inside others.

Is kohana installing in /usr/lib? If yes, if someone will decide to build kohana rpm they would be in conflict.

There are various solutions which could translate the old urls to the new one, tell me if one of the solutions I found are fine with epel requirements.

pnp4nagios 0.6 needs some rewrite rules in httpd.
unfortunately pnp4nagios relies on nagios.conf for httpd configuration which comes from nagios package.
pnp4nagios could do the rewrite rules through .htaccess file but unfortunately it is blocked with AllowOverride None in the nagios.conf.

which means the options would be:
- patch nagios.conf during pnp4nagios installation to add the rewrite rules, the standard ones plus one which provide retroco-mpatibility, I can provide it, I have it. (or index.php patch needed to redirect old urls)
- patch nagios.conf during pnp4nagios installation to allow .htaccess files and deploy custom .htaccess file in pnp4nagios directory
- build a new nagios to allow .htaccess files and build pnp4nagios with rewrite rules in a .htaccess file

Is any of these options allowed?

(In reply to comment #7)
> There are various solutions which could translate the old urls to the new one,
> tell me if one of the solutions I found are fine with epel requirements.
> 
> pnp4nagios 0.6 needs some rewrite rules in httpd.
> unfortunately pnp4nagios relies on nagios.conf for httpd configuration which
> comes from nagios package.
> pnp4nagios could do the rewrite rules through .htaccess file but unfortunately
> it is blocked with AllowOverride None in the nagios.conf.
> 
> which means the options would be:
> - patch nagios.conf during pnp4nagios installation to add the rewrite rules,
> the standard ones plus one which provide retroco-mpatibility, I can provide it,
> I have it. (or index.php patch needed to redirect old urls)

Are you sure, you can fix all locations of natios config files? Can you write this "patch" to fix all occurences and do not modify anythin else?
If you can provide a script or patch, I can look at it, but I think it's very hard to do it and do not harm any user.

> - patch nagios.conf during pnp4nagios installation to allow .htaccess files and

Again, it's not very safe. Every user can have it's own config files in their own locations.

> deploy custom .htaccess file in pnp4nagios directory


> - build a new nagios to allow .htaccess files and build pnp4nagios with rewrite
> rules in a .htaccess file

I think you need to make a fork of nagios to allow this. Or at least build a different version, which is not required. It's a bad idea.

If you can't give me a patch, which will fix this globally, I will close this bug.

Let's close it for now.