[amo] Make a system package for jinja 2.3.1

RESOLVED FIXED

Status

Infrastructure & Operations
WebOps: Other
--
minor
RESOLVED FIXED
8 years ago
5 years ago

People

(Reporter: jbalogh, Assigned: oremj)

Tracking

Details

(Reporter)

Description

8 years ago
Jinja has optional C speedups that make template auto-escaping move faster.  We need to compile that, so we need a system package.

Right now we're on 2.3.1, but 2.4 just came out so we'll move to that soon (though not immediately).

Updated

8 years ago
Assignee: server-ops → shyam

Updated

8 years ago
Assignee: shyam → jeremy.orem+bugs
(Reporter)

Updated

8 years ago
Depends on: 560444
(Assignee)

Comment 1

8 years ago
Done and installed on khan and preview. Let me know when you want these installed to the production machines.
(Assignee)

Updated

8 years ago
Status: NEW → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → FIXED
(Reporter)

Comment 2

8 years ago
(In reply to comment #1)
> Done and installed on khan and preview. Let me know when you want these
> installed to the production machines.

Please add it to the cron job machine (mradm02?) as well.

Reopening because fox2mike installed python 2.6.5 and it looks like this needs to be rebuilt.

ImportError: /usr/lib/python2.6/site-packages/_pylibmc.so: undefined symbol: memcached_server_list

Here's a test to make sure we're good: 
python26 -c 'import pylibmc; print pylibmc.__version__'
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
(Reporter)

Comment 3

8 years ago
(In reply to comment #2)
> Here's a test to make sure we're good: 
> python26 -c 'import pylibmc; print pylibmc.__version__'

That should be:
python -c 'import jinja2; print jinja2.__version__'
(Assignee)

Comment 4

8 years ago
Are we sticking with the 2.6.5 rpm or reverting to 2.6.2?
(In reply to comment #4)
> Are we sticking with the 2.6.5 rpm or reverting to 2.6.2?

I think the 2.6.5 rpm needs to be redone so it doesn't crash.  2.6.2 still has our crashes in it
(Reporter)

Comment 6

8 years ago
It turns out that Jinja doesn't build the C speedups by default.  We need to pass --with-speedups to get it going:

python setup.py --with-speedups build

In a shining note for Python option parsing, --with-speedups cannot come after build/install/whatever command you're calling.
(Assignee)

Comment 7

8 years ago
This package has been installed across all the AMO machines.
Status: REOPENED → RESOLVED
Last Resolved: 8 years ago8 years ago
Resolution: --- → FIXED
Component: Server Operations: Web Operations → WebOps: Other
Product: mozilla.org → Infrastructure & Operations
You need to log in before you can comment on or make changes to this bug.