Opened 16 years ago
Closed 15 years ago
#11109 closed (fixed)
Changeset 8224 broken in Trac
Reported by: | Fraser Nevett | Owned by: | Jacob |
---|---|---|---|
Component: | *.djangoproject.com | Version: | 1.0 |
Severity: | Keywords: | ||
Cc: | Triage Stage: | Ready for checkin | |
Has patch: | no | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Description
When trying to access http://code.djangoproject.com/changeset/8224, I get: "500 Internal Server Error (No changeset 8224 in the repository)".
It looks like the Subversion repository is intact, so I suspect the Trac database may need to be resync'd...
$ svn log -r 8224 http://code.djangoproject.com/svn/ ------------------------------------------------------------------------ r8224 | jbronn | 2008-08-06 22:40:00 +0100 (Wed, 06 Aug 2008) | 2 lines gis: The `verbose_name` positional keyword now works for `GeometryField`, thanks springmeyer; removed DOS line endings from Oracle & MySQL spatial backends, thanks cramm. ------------------------------------------------------------------------
$ svn diff -r 8223:8224 http://code.djangoproject.com/svn/ | grep Index: Index: django/trunk/django/contrib/gis/db/models/fields/__init__.py Index: django/trunk/django/contrib/gis/db/backend/mysql/query.py Index: django/trunk/django/contrib/gis/db/backend/oracle/query.py
Change History (5)
comment:1 by , 15 years ago
Triage Stage: | Unreviewed → Ready for checkin |
---|
comment:2 by , 15 years ago
I have no idea what causes this, but it just happened again with [11745]. The repository appears to be fine - it's just a Trac display problem.
comment:3 by , 15 years ago
Owner: | changed from | to
---|---|
Status: | new → assigned |
comment:4 by , 15 years ago
comment:5 by , 15 years ago
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
Done. For future reference, this is what I did on the djangoproject.com server:
$ cd /home/trac $ export PYTHONPATH=/home/djangoproject.com:/home/trac $ python trac-admin /home/trac/django.tracenv/ resync
Note that it appeared that each commit was erased from Trac for a few minutes, which scared me, but I guess that's normal. Even after the script is done running, there's some process that takes a few minutes to complete in the background, or something.
Verified. Nothing anyone outside of the core team can do to fix it, so I'll promote straight to checkin