Closed Bug 642978 Opened 9 years ago Closed 9 years ago

update and build scripts to work with new version of Template Toolkit


( Graveyard :: Server Operations, task, minor)

Not set


(Not tracked)



(Reporter: justdave, Assigned: justdave)



(2 files)

Currently we have Template Toolkit version-locked on mradm02 because a change to Template Toolkit broke the site build scripts for and

The attached patch will update the config for the scripts to allow them to work with the new version of Template Toolkit.  However, it makes use of a feature which was later added to Template Toolkit at our request to make up for the lost functionality when the intermediate version broke it.  Thus, applying this patch without upgrading Template Toolkit at the same time will break both of those websites.

tl;dr version: IT needs to commit this patch and upgrade Template Toolkit at the same time on mradm02 to avoid breaking the websites.

Both sites are in

cvs -d {username} co bugzilla-org
cvs -d {username} co seamonkeyproject-org

The patches should apply cleanly from the root directory of each checkout.

After committing, edit the yum configuration on mradm02 to remove the excludes line for perl-Template-Toolkit, and yum update perl-Template-Toolkit.
The build roots will automatically update via the cron job prior to the next pass of the site build, so a manual run or cvs update won't be necessary.  Just need to make sure Template Toolkit gets upgraded as soon as possible after the patches are committed.
Assignee: server-ops → justdave
Checking in etc/ttree.cfg;
/www/bugzilla-org/etc/ttree.cfg,v  <--  ttree.cfg
new revision: 1.9; previous revision: 1.8

Checking in etc/ttree.cfg;
/www/seamonkeyproject-org/etc/ttree.cfg,v  <--  ttree.cfg
new revision: 1.11; previous revision: 1.10

   perl-Template-Toolkit.x86_64 0:2.22-1.el5.rf
Closed: 9 years ago
Resolution: --- → FIXED
Justin, Jens, just FYI that this has been done.
Thanks! It's been the first time that I could actually run bin/build successfully now, even though, contrary to what README said, I had to create dist/ manually (otherwise it failed as early as trying to copy src/.htaccess).
Product: → Graveyard
You need to log in before you can comment on or make changes to this bug.