On Jul 6, 2009, at 7:59 AM, Kristofer Henriksson wrote:
I noticed the same thing happen to me in the past, where I would get a python backtrace upon logging in, though the logout link still would work for me. If I was logged out, I had no problems accessing pages. I just checked this again and I don't seem to be having these problems, but I wanted to confirm that more than one person has seen it and that it doesn't seem to have been caused by any recent change. On Mon, Jul 6, 2009 at 9:55 AM, Mark Evenson<even...@panix.com> wrote:Mark Evenson wrote:Joshua Root wrote:On 2009-7-6 22:51, Mark Evenson wrote:The [Macports Trac instance][1] seems to have been down for severaldays.[…]I haven't noticed any downtime. What happens when you try to use it?[…]The following python trace: Traceback (most recent call last):File "/opt/local/lib/python2.5/site-packages/trac/web/api.py", line 367,in send_error 'text/html')File "/opt/local/lib/python2.5/site-packages/trac/web/chrome.py", line728, in render_template if not req.session or not int(req.session.get('accesskeys', 0)): File "/opt/local/lib/python2.5/site-packages/trac/web/api.py", line[…]Apparently something screwy with my login ID, as coming in with a clean browser shows everything normal (I'm loathe to clear my main browser'scookies but I guess I should, and then iterate over the login ID). Thanks to those who responded.
Its a bug in Trac. You should be able to clear your cookies for macosforge.org and macports.org and login again to workaround the problem.
-Bill
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ macports-dev mailing list macports-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev