Age | Commit message (Collapse) | Author |
|
svn path=/branches/tk705/; revision=6000
|
|
svn path=/trunk/; revision=5999
|
|
svn path=/branches/tk705/; revision=5998
|
|
Old method of passing the Conf object to ROARequestForm was brittle due to overriding a private method in BaseFormSet.
New method is to use a closure to embed the Conf object within a class generated on the fly.
See #709
svn path=/trunk/; revision=5997
|
|
svn path=/trunk/; revision=5996
|
|
configuration on Precise was a false positive caused by an orphaned
symlink. Rewrite again to separate Debian and Ubuntu so we can do
version number checks in a halfway sane fashion.
Most likely the real underlying issue is Debian-family packaging for
Apache 2.2 vs Apache 2.4, so there may be possible to simplify this
again at some point, but in theory this will do for now.
Need to re-test on Trusty and Wheezy to make sure the fix for Precise
didn't break them. See #720.
svn path=/trunk/; revision=5995
|
|
svn path=/trunk/; revision=5994
|
|
svn path=/trunk/; revision=5993
|
|
See #720.
svn path=/trunk/; revision=5992
|
|
svn path=/trunk/; revision=5991
|
|
svn path=/branches/tk705/; revision=5990
|
|
svn path=/branches/tk705/; revision=5989
|
|
svn path=/branches/tk705/; revision=5988
|
|
legacy rpki and pubd databases.
svn path=/branches/tk705/; revision=5987
|
|
MIDDLEWARE_CLASSES. Fixes #717.
svn path=/trunk/; revision=5986
|
|
svn path=/trunk/; revision=5985
|
|
svn path=/branches/tk705/; revision=5984
|
|
svn path=/branches/tk705/; revision=5983
|
|
svn path=/branches/tk705/; revision=5982
|
|
svn path=/branches/tk705/; revision=5981
|
|
packages when nothing had changed.
svn path=/trunk/; revision=5980
|
|
svn path=/branches/tk705/; revision=5979
|
|
svn path=/trunk/; revision=5978
|
|
supported platforms.
svn path=/trunk/; revision=5977
|
|
svn path=/branches/tk705/; revision=5976
|
|
staying current.
svn path=/trunk/; revision=5975
|
|
svn path=/branches/tk705/; revision=5974
|
|
suffix on the site configuration filename. Need to check whether this
breaks older distributions, if so will need to something version
dependent.
svn path=/trunk/; revision=5973
|
|
svn path=/trunk/; revision=5972
|
|
Builds for Ubuntu Precise Pangolin (12.04) disabled, either for good
or until we figure out how to convince reprepo to accept the same
package compiled for two different releases (sigh). See #712.
svn path=/trunk/; revision=5971
|
|
svn path=/branches/tk705/; revision=5970
|
|
SAX.
svn path=/branches/tk705/; revision=5969
|
|
svn path=/branches/tk705/; revision=5968
|
|
svn path=/branches/tk705/; revision=5967
|
|
svn path=/branches/tk705/; revision=5966
|
|
svn path=/branches/tk705/; revision=5965
|
|
svn path=/branches/tk705/; revision=5964
|
|
svn path=/branches/tk705/; revision=5963
|
|
svn path=/branches/tk705/; revision=5962
|
|
smoketest temporarily broken as it doesn't know anything about Django.
svn path=/branches/tk705/; revision=5961
|
|
svn path=/branches/tk705/; revision=5960
|
|
daemons was pointless, so back that out before removing branches/tk713.
svn path=/branches/tk705/; revision=5958
|
|
with all its tedious setup actions.
svn path=/branches/tk705/; revision=5957
|
|
svn path=/branches/tk705/; revision=5956
|
|
might be due to some kind of CSRF problem, might be worth figuring out
how to disable that for debugging but not terribly urgent.
svn path=/branches/tk713/; revision=5955
|
|
Result sometimes hangs with browser waiting for response, not sure
why, might be ancient abandoned bug #116.
Logging control is a bit screwy, everything uses Python's logging
library but we have multiple ways of configuring it.
svn path=/branches/tk713/; revision=5954
|
|
startup procedure. This may be temporary, as processing --help
without a configuration file may require deferring all Django imports
until late enough that --config would work too. Defer for now.
svn path=/branches/tk713/; revision=5953
|
|
svn path=/branches/tk713/; revision=5952
|
|
svn path=/branches/tk713/; revision=5951
|
|
indeed masking the new migration stuff. yamltest now runs migrations
as part of setting up test CAs; still need to decide whether running
migrations in production is something that should be handled
explicitly via rpki-manage or should be bundled into rpki-sql-setup.
Old settings.configure() code still present as a trail of breadcrumbs
to follow when backing out the rest of the tortuous startup sequence
required by the old way of doing things.
svn path=/branches/tk713/; revision=5950
|