Currently I am getting on https://trac.sagemath.org/ (or on any ticket I
tried)
Traceback (most recent call last):
File "/usr/local/lib/python2.7/dist-packages/trac/web/api.py", line 602, in
send_error
data, 'text/html')
File "/usr/local/lib/python2.7/dist-packages/trac/web/chrome.py", line 1111,
in render_template
if self.stream_filters:
File "/usr/local/lib/python2.7/dist-packages/trac/core.py", line 82, in
extensions
components = [component.compmgr[cls] for cls in classes]
File "/usr/local/lib/python2.7/dist-packages/trac/core.py", line 208, in
__getitem__
component = cls(self)
File "/usr/local/lib/python2.7/dist-packages/trac/core.py", line 144, in
__call__
self.__init__()
File "/usr/local/lib/python2.7/dist-packages/sage_trac/ticket_branch.py",
line 37, in __init__
git_merger.GitMerger.__init__(self, *args, **kwargs)
File "/usr/local/lib/python2.7/dist-packages/sage_trac/git_merger.py", line
28, in __init__
GitBase.__init__(self, *args, **kwargs)
File "/usr/local/lib/python2.7/dist-packages/sage_trac/common.py", line 66,
in __init__
raise TracError('one of cgit_url or cgit_hot must be set in '
TracError: one of cgit_url or cgit_hot must be set in trac.ini
On Monday, June 20, 2016 at 4:18:47 PM UTC+1, Erik Bray wrote:
>
> Hi all,
>
> As decided toward the end of another recent thread [1] I willl be
> taking down the server at UW which hosts both trac.sagemath.org and
> git.sagemath.org, starting around 8:00 A.M. CEST. There are at least
> three reasons for this:
>
> 1. Mitigate issues related to reliance upon university IT
> infrastructure over which we have little control [2][3] or influence
> 2. Move to tier 1 cloud-based hosting for greater ease of deployment
> and (hopefully) better reliability
> 3. Address current and ongoing preformance / access issues with the
> Trac site, which are possibly related to 1
>
> An additional change to be aware of is that access to
> trac.sagemath.org, as well as the git web interface at
> git.sagemath.org will be switched to HTTPS *only*. HTTP redirects
> will be set up, but please update any URLs nonetheless.
>
> Other than that, with a little luck you should notice few or any
> differences. Please keep in mind though that the current Sage Trac
> infrastructure has a layer of grime and mold over it, and it's
> entirely possible I've missed a few spots while shining it up. So if
> anything isn't working after the migration please be patient and
> cooperate by sending notice either to
> sagemat...@googlegroups.com <javascript:>, or to me personally*.
>
> Best,
> Erik
>
> * The offer to e-mail me personally about such issues expires some
> indeterminate amount of time after the migration is completed. I want
> to be on-call for migration-related issues, but in general support
> issues should be sent to one of the mailing lists where they can be
> handled by the best personal available at the moment.
>
> [1] https://groups.google.com/d/msg/sage-devel/EKhgXsdKMhY/52fKpHDBAQAJ
> [2] https://groups.google.com/d/msg/sage-devel/Xw6CNq1lyiI/aeyT5TluDQAJ
> [3] https://groups.google.com/d/msg/sage-devel/Xw6CNq1lyiI/APzgctSUDQAJ
>
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.
