Talk:HackingHowto: Difference between revisions
Jump to navigation
Jump to search
(note need for python-sqlalchemy* on Debian) |
No edit summary |
||
| Line 1: | Line 1: | ||
With the SQL transition underway, on my Debian stable system, I had to install the <tt>python-sqlalchemy</tt> and <tt>python-sqlalchemy-ext</tt> packages to make MediaGoblin go. IRC advised me to get them from backports, which I did, and that's worked out, although there are packages in stable too -- not sure if they're new enough. Either way, should instructions about this be added to the documentation now? Or is a temporary transition thing? --[[User:Brett|Brett]] 09:18, 31 March 2012 (EDT) |
With the SQL transition underway, on my Debian stable system, I had to install the <tt>python-sqlalchemy</tt> and <tt>python-sqlalchemy-ext</tt> packages to make MediaGoblin go. IRC advised me to get them from backports, which I did, and that's worked out, although there are packages in stable too -- not sure if they're new enough. Either way, should instructions about this be added to the documentation now? Or is a temporary transition thing? --[[User:Brett|Brett]] 09:18, 31 March 2012 (EDT) |
||
: When using a virtualenv, these are downloaded for you in ./bin/python setup.py develop --upgrade |
|||
Revision as of 11:23, 26 January 2014
With the SQL transition underway, on my Debian stable system, I had to install the python-sqlalchemy and python-sqlalchemy-ext packages to make MediaGoblin go. IRC advised me to get them from backports, which I did, and that's worked out, although there are packages in stable too -- not sure if they're new enough. Either way, should instructions about this be added to the documentation now? Or is a temporary transition thing? --Brett 09:18, 31 March 2012 (EDT)
- When using a virtualenv, these are downloaded for you in ./bin/python setup.py develop --upgrade