In 3.8 we ran a script something like “update-siteconfig-rt3.8”. Is there something like this in RT 4.0.2? I have a fresh install (manual of course) on Ubuntu Server Natty (11.04) and am unable, at this point to serve pages from RT. A big change in the apache configuration as well from the jump to RT4 from RT3.8.
There were no huge changes in how RT 4.0 process config files unlike
it was in RT 3.8. Also, as far as I can see that script is debian
specific thing.On Thu, Sep 15, 2011 at 5:52 PM, Izz Abdullah Izz.Abdullah@hibbett.com wrote:
In 3.8 we ran a script something like “update-siteconfig-rt3.8”. Is there
something like this in RT 4.0.2? I have a fresh install (manual of course)
on Ubuntu Server Natty (11.04) and am unable, at this point to serve pages
from RT. A big change in the apache configuration as well from the jump to
RT4 from RT3.8.
Even if it is debian specific, I was running on an Ubuntu server previously with RT3.8. So what actually updates RT_Config.pm from the RT_SiteConfig.pm settings? Surely not simply restarting the apache service.From: ruslan.zakirov@gmail.com [mailto:ruslan.zakirov@gmail.com] On Behalf Of Ruslan Zakirov
Sent: Thursday, September 15, 2011 9:25 AM
To: Izz Abdullah
Cc: rt-users@lists.bestpractical.com
Subject: Re: [rt-users] Updating RT_SiteConfig in RT4.0.2
Hi,
There were no huge changes in how RT 4.0 process config files unlike
it was in RT 3.8. Also, as far as I can see that script is debian
specific thing.
Even if it is debian specific, I was running on an Ubuntu server previously with RT3.8. So what actually updates RT_Config.pm from the RT_SiteConfig.pm settings? Surely not simply restarting the apache service.
update-rt-siteconfig takes the files in
/etc/request-tracker3.8/RT_SiteConfig.d and uses them to construct
/etc/request-tracker3.8/RT_SiteConfig.pm. It does not alter RT_Config.pm
(which is installed under /usr in Debian).
If you are installing RT 4 manually, you will just be updating
RT_SiteConfig.pm directly.
If you prefer to work with Debian packages, you might find that it’s
possible to backport 4.0 to Natty without too much work.
(Incidentally, it looks like 11.10 will release with RT 4.0.1; if any
Ubuntu users would prefer 4.0.2 in 11.10, now would be a good time to
find an Ubuntu developer to sync this for you).
Dominic Hargreaves, Systems Development and Support Team
Computing Services, University of Oxford
Even if it is debian specific, I was running on an Ubuntu server previously with RT3.8. So what actually updates
I can believe that was running some script. Ubuntu is a debian based
distro and plenty of things migrate from Debian into Ubuntu.
RT_Config.pm from the RT_SiteConfig.pm settings? Surely not simply restarting the apache service.
In vanilla RT nothing updates RT_Config.pm from RT_SiteConfig.pm. Both
are loaded, as well as configs from plugins. Settings in SiteConfig
just have the highest priority.
There were no huge changes in how RT 4.0 process config files unlike
it was in RT 3.8. Also, as far as I can see that script is debian
specific thing.
In 3.8 we ran a script something like “update-siteconfig-rt3.8”. Is there
something like this in RT 4.0.2? I have a fresh install (manual of course)
on Ubuntu Server Natty (11.04) and am unable, at this point to serve pages
from RT. A big change in the apache configuration as well from the jump to
RT4 from RT3.8.
I am aware Ubuntu is a debian clone. Anyway, I admit I was mistaken about RT_Config being updated by RT_SiteConfig by that script. Either way, the script is no longer in 4.0.2, or maybe it is the newer server version I am using. I thought I had to run that script each time I updated the siteconfig file in order to see the changes in RT, but you know something, I also always restarted apache as well, so maybe that was the trick all along.
Even if it is debian specific, I was running on an Ubuntu server previously with RT3.8. So what actually updates
I can believe that was running some script. Ubuntu is a debian based
distro and plenty of things migrate from Debian into Ubuntu.
RT_Config.pm from the RT_SiteConfig.pm settings? Surely not simply restarting the apache service.
In vanilla RT nothing updates RT_Config.pm from RT_SiteConfig.pm. Both
are loaded, as well as configs from plugins. Settings in SiteConfig
just have the highest priority.
There were no huge changes in how RT 4.0 process config files unlike
it was in RT 3.8. Also, as far as I can see that script is debian
specific thing.
In 3.8 we ran a script something like “update-siteconfig-rt3.8”. Is there
something like this in RT 4.0.2? I have a fresh install (manual of course)
on Ubuntu Server Natty (11.04) and am unable, at this point to serve pages
from RT. A big change in the apache configuration as well from the jump to
RT4 from RT3.8.
if any Ubuntu users would prefer 4.0.2 in 11.10, now would be a good time to find an Ubuntu developer to sync this for you
I certainly would prefer that RT4.0.2 come with Ubuntu 11.10. What
does “find an Ubuntu developer” mean? Does it mean vote and make noise
in some issue tracking system? Or hire someone to fix the 4.0.1
packages?
if any Ubuntu users would prefer 4.0.2 in 11.10, now would be a good time to find an Ubuntu developer to sync this for you
I certainly would prefer that RT4.0.2 come with Ubuntu 11.10. What
does “find an Ubuntu developer” mean? Does it mean vote and make noise
in some issue tracking system? Or hire someone to fix the 4.0.1
packages?
Probably filing a bug against request-tracker4 in launchpad would be a
good way to start. It’s just a simple action for someone with the right
access, I believe; the 4.0.1 packages are unmodified from my Debian
ones so there’s no remerging to do.
Dominic Hargreaves, Systems Development and Support Team
Computing Services, University of Oxford