When updated from 0.99.15 to 0.99.17: I had to change owner and group of /var/log/cherokee.* from root:root to cherokee:cherokee to make cherokee to start. And cherokee.conf was modified by env-update deleting php support. Reproducible: Always
Thanks for reporting these issues. Could you provide a little more explanation on your second point? env-update is only supposed to modify /etc/profile.env and /etc/ld.so.conf; how can you tell that it modified cherokee.conf?
This commit contains fixes for the logging/permissions issue: http://github.com/funtoo/portage/commit/df9a4a1f7e7ce4e8d6b468a60a6e0261b1cc2fe0 Committed to the Funtoo Portage tree.
(In reply to comment #1) > Thanks for reporting these issues. Could you provide a little more explanation > on your second point? env-update is only supposed to modify /etc/profile.env > and /etc/ld.so.conf; how can you tell that it modified cherokee.conf? > I meant etc-update.
Created attachment 196083 [details] Differences between cherokee.conf 0.99.15 and 0.99.19-r1 As you can see this new installation makes cherokee.conf to delete php support. And at least with 0.99.17 I tried to regenerate cherokee.conf using cherokee-admin but it didn't work, I'll try again with 0.99.19-r1. Anyway, this .conf changing should be fixed.
Thanks, that makes more sense. I see that Daniel's permissions fix has already been commited, so the only issue left is php being taken out of the default cherokee config file. I think it was an upstream decision since ebuild doesn't appear to modify the config, but you can see what the maintainers have to say about this topic.
etc-update doesn't really have anything to do with the issue here. it just merges what the package itself installs.
(In reply to comment #5) > Thanks, that makes more sense. I see that Daniel's permissions fix has > already been commited, so the only issue left is php being taken out of the > default cherokee config file. I think it was an upstream decision since > ebuild doesn't appear to modify the config, but you can see what the > maintainers have to say about this topic. Regarding this remaining issue, we are not changing it at ebuild level and, then, this is an upstream decision that you need to report directly to them
