Custom Query (1173 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (97 - 99 of 1173)

Ticket Resolution Summary Owner Reporter
#129 FIXED organize admin/development scripts Will Kahn-Greene
Description
There are a few scripts that are in the repository now and probably
more to come. We should reorganize them so they get "installed"
when using builtout and setup.py install. Also, they should follow
a similar structure and have header information.

Maybe it's interesting to create a gmg command that has a series of
sub commands like PyBlosxom and git both have.

Regardless, the following things should be done:


1. administration/management scripts should be collected and put in
   a centralized place
2. they should be tweaked so they follow the same conventions
   (which means we should create a set of conventions for scripts)
3. we should fix the install process to "install" these scripts as
   well

It's probably worth doing this for 0.0.4, but it's something
someone can think about towards the end of the 0.0.4 cycle.



#806 fixed on setup, kombu 3.0 conflicts with celery 3.0.24 criticalcat
Description

Given fresh install on Trisquel 6.0 by following setup instructions here:

http://mediagoblin.readthedocs.org/en/v0.5.1/siteadmin/deploying.html

When running this command:

(sudo -u mediagoblin virtualenv --system-site-packages .
virtualenv .) && sudo -u mediagoblin ./bin/python setup.py develop

Then this error occurs:

error: Installed distribution kombu 3.0.0 conflicts with requirement kombu>=2.5.15,<3.0

Full error log: http://pastie.org/8417541 setup.py: http://pastie.org/8417552

It appears that celery is the one with the <3.0 dependency:

./lib/python2.7/site-packages/celery-3.0.24-py2.7.egg/EGG-INFO/requires.txt:kombu>=2.5.15,<3.0

When I add a <3.0 to the setup.py kombu dependency on a fresh version before running the same command

modified setup.py: http://pastie.org/8417570

Then the command succeeds

result: http://pastie.org/8417569

#1016 fixed oauth sends invalid timestamp format for postgresql db ayleph
Description

When using a client such as pypump to post content to GMG via the API, postgresql complains about an invalid timestamp syntax. Postgresql seems to expect a datetime string instead of Unix epoch integer.

DataError: (DataError) invalid input syntax for type timestamp: "1414412402"
Batch Modify
Note: See TracBatchModify for help on using batch modify.
Note: See TracQuery for help on using queries.