[Tracker-discuss] [issue449] Sending email to bugs.python.org could create bug report with wrong name.

New submission from Ramchandra Apte : If you set your email name to something different from your bug tracker name and send an email to bugs.python.org, the bug report created will contain the email name. The bug report created is uncloseable and only the bug tracker admins can close it. The b

[Tracker-discuss] [issue411] Roundup instance is outdated

Ramchandra Apte added the comment: Status of this bug? -- nosy: +ramchandra.apte ___ PSF Meta Tracker ___ ___

[Tracker-discuss] [issue402] Unable to log in to Rietveld code review interface

Eric Snow added the comment: Yeah, I'll give it a go tonight. Hopefully I can turn something up. (While I'm at it I'll probably update the wiki page on building a tracker instance.) ___ PSF Meta Tracker

[Tracker-discuss] [issue402] Unable to log in to Rietveld code review interface

Nadeem Vawda added the comment: AFAICT, the source lives at , with the Rietveld stuff under instances/python-dev/rietveld/. You might be able to get useful info by trying to run your own instance locally, and inspecting the DB state directly before and after

[Tracker-discuss] [issue448] Login not working (mostly)

New submission from Terry Reedy : If I go to bugs.python.org, get default page with recent activity, fill in name,pass, hit [login], I get, with red background "broken form: multiple @action values submitted" If I go to search page and do same, I do get logged in. If I do a search and do same f

[Tracker-discuss] [issue442] Upgrade Debian

Izak Burger added the comment: Hi again, I discovered the Hetzner Wiki with the details on how to set up ipv6 properly. It appears to work now. The ipv6 address for bugs.python.org is: 2a01:4f8:131:2480::3 regards, Izak -- status: resolved -> chatting ___