From metatracker at psf.upfronthosting.co.za  Wed Jun  1 19:46:02 2011
From: metatracker at psf.upfronthosting.co.za (Ezio Melotti)
Date: Wed, 01 Jun 2011 17:46:02 +0000
Subject: [Tracker-discuss] [issue401] Fold history in the issue pages
In-Reply-To: <1306464983.45.0.41831171245.issue401@psf.upfronthosting.co.za>
Message-ID: <1306950362.44.0.757837405186.issue401@psf.upfronthosting.co.za>


Ezio Melotti <ezio.melotti at gmail.com> added the comment:

I reverted the history folding and applied the 'end' key tweak in r88847.

As usual I'll leave this open for a while to see if there is some feedback.

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue401>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Thu Jun  2 22:25:18 2011
From: metatracker at psf.upfronthosting.co.za (Tshepang Lekhonkhobe)
Date: Thu, 02 Jun 2011 20:25:18 +0000
Subject: [Tracker-discuss] [issue403] please allow post editing
In-Reply-To: <1307046318.48.0.544701036876.issue403@psf.upfronthosting.co.za>
Message-ID: <1307046318.48.0.544701036876.issue403@psf.upfronthosting.co.za>


New submission from Tshepang Lekhonkhobe <tshepang at gmail.com>:

Please allow users to edit their messages/posts to the Python bug tracker.

----------
messages: 2070
nosy: tshepang
priority: feature
status: unread
title: please allow post editing

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue403>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Fri Jun  3 00:03:38 2011
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v=2E_L=C3=B6wis?=)
Date: Thu, 02 Jun 2011 22:03:38 +0000
Subject: [Tracker-discuss] [issue403] please allow post editing
In-Reply-To: <1307046318.48.0.544701036876.issue403@psf.upfronthosting.co.za>
Message-ID: <1307052218.18.0.188342800609.issue403@psf.upfronthosting.co.za>


Martin v. L?wis <martin at v.loewis.de> added the comment:

Why is that necessary? Notice that the post was also sent by email, and you can't edit the email copies, either.

----------
nosy: +loewis
status: unread -> chatting

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue403>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Fri Jun  3 02:38:30 2011
From: metatracker at psf.upfronthosting.co.za (Tshepang Lekhonkhobe)
Date: Fri, 03 Jun 2011 00:38:30 +0000
Subject: [Tracker-discuss] [issue403] please allow post editing
In-Reply-To: <1307046318.48.0.544701036876.issue403@psf.upfronthosting.co.za>
Message-ID: <1307061510.39.0.136927543441.issue403@psf.upfronthosting.co.za>


Tshepang Lekhonkhobe <tshepang at gmail.com> added the comment:

To fix typos for example.

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue403>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Fri Jun  3 07:25:01 2011
From: metatracker at psf.upfronthosting.co.za (Georg Brandl)
Date: Fri, 03 Jun 2011 05:25:01 +0000
Subject: [Tracker-discuss] [issue403] please allow post editing
In-Reply-To: <1307046318.48.0.544701036876.issue403@psf.upfronthosting.co.za>
Message-ID: <1307078701.73.0.533052064821.issue403@psf.upfronthosting.co.za>


Georg Brandl <g.brandl at gmx.net> added the comment:

If you feel the need to correct a typo, you can do it with a follow-up post.  The problem is that while you may only use this rationally, other users will use it in harmful ways.

Following a tracker issue history can be confusing enough without having to assume that a reply doesn't refer to the current text of a message, but a previous revision.

And as Martin says, if the email notifications differ from the post you see when opening the issue in the web interface, that's just as annoying and confusing.

----------
nosy: +gbrandl
status: chatting -> resolved

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue403>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Fri Jun  3 10:12:26 2011
From: metatracker at psf.upfronthosting.co.za (Tshepang Lekhonkhobe)
Date: Fri, 03 Jun 2011 08:12:26 +0000
Subject: [Tracker-discuss] [issue403] please allow post editing
In-Reply-To: <1307046318.48.0.544701036876.issue403@psf.upfronthosting.co.za>
Message-ID: <1307088746.16.0.344489438088.issue403@psf.upfronthosting.co.za>


Tshepang Lekhonkhobe <tshepang at gmail.com> added the comment:

Makes sense. Thanks.

----------
status: resolved -> chatting

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue403>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Fri Jun  3 22:41:05 2011
From: metatracker at psf.upfronthosting.co.za (anatoly techtonik)
Date: Fri, 03 Jun 2011 20:41:05 +0000
Subject: [Tracker-discuss] [issue404] Personal comment rating
In-Reply-To: <1307133665.5.0.190293604429.issue404@psf.upfronthosting.co.za>
Message-ID: <1307133665.5.0.190293604429.issue404@psf.upfronthosting.co.za>


New submission from anatoly techtonik <techtonik at gmail.com>:

I badly need comment rating +1/-1 to hide messages I am not interested in specific thread. This feature can later be leveraged to count community rating on some posts to provide feedback for people how can they make their comments more useful. It is also a time saver on revisiting some very long threads.

IMO this kind of feedback fun is essential for community, and there is more than just fun in it (even though for fun for me is already a worthy argument to implement).

----------
messages: 2075
nosy: techtonik
priority: wish
status: unread
title: Personal comment rating

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue404>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Sun Jun  5 23:01:22 2011
From: metatracker at psf.upfronthosting.co.za (Ned Deily)
Date: Sun, 05 Jun 2011 21:01:22 +0000
Subject: [Tracker-discuss] [issue401] Fold history in the issue pages
In-Reply-To: <1306464983.45.0.41831171245.issue401@psf.upfronthosting.co.za>
Message-ID: <1307307682.17.0.280004773308.issue401@psf.upfronthosting.co.za>


Ned Deily <nad at acm.org> added the comment:

The "end" key tweak is a much better solution, IMO.  Thanks!

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue401>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Tue Jun  7 13:00:12 2011
From: metatracker at psf.upfronthosting.co.za (Ezio Melotti)
Date: Tue, 07 Jun 2011 11:00:12 +0000
Subject: [Tracker-discuss] [issue401] Fold history in the issue pages
In-Reply-To: <1306464983.45.0.41831171245.issue401@psf.upfronthosting.co.za>
Message-ID: <1307444412.85.0.936334710443.issue401@psf.upfronthosting.co.za>


Ezio Melotti <ezio.melotti at gmail.com> added the comment:

Since the 'end' key tweak seems OK, I'll close this.

----------
status: testing -> resolved

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue401>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Tue Jun  7 13:03:18 2011
From: metatracker at psf.upfronthosting.co.za (Ezio Melotti)
Date: Tue, 07 Jun 2011 11:03:18 +0000
Subject: [Tracker-discuss] [issue312] Add a 'go to the last message' link
In-Reply-To: <1263565390.97.0.608174776201.issue312@psf.upfronthosting.co.za>
Message-ID: <1307444598.76.0.427852675494.issue312@psf.upfronthosting.co.za>


Ezio Melotti <ezio.melotti at gmail.com> added the comment:

The fix applied in #401 should address this as well, therefore I'm closing this issue.

----------
status: in-progress -> resolved
superseder: +Fold history in the issue pages

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue312>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Tue Jun  7 13:29:16 2011
From: metatracker at psf.upfronthosting.co.za (Ezio Melotti)
Date: Tue, 07 Jun 2011 11:29:16 +0000
Subject: [Tracker-discuss] [issue119] Tracker Documentation
In-Reply-To: <1185340066.06.0.0886892361436.issue119@psf.upfronthosting.co.za>
Message-ID: <1307446156.38.0.13895218124.issue119@psf.upfronthosting.co.za>


Ezio Melotti <ezio.melotti at gmail.com> added the comment:

Now there are still 4 documents:
 * http://docs.python.org/dev/py3k/bugs.html
 * http://wiki.python.org/moin/SubmittingBugs
 * http://docs.python.org/devguide/triaging.html
 * http://wiki.python.org/moin/TrackerDocs/

The first two pages explain how to submit a bug and are basically the same.
The 3rd and 4th page explain the fields of the bug tracker and what links are generated.
I think both the wiki pages should redirect to the docs pages.  The content can either be removed or left it there.

The dev/workflow/ page no longer exist.

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue119>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Tue Jun  7 13:41:47 2011
From: metatracker at psf.upfronthosting.co.za (Ezio Melotti)
Date: Tue, 07 Jun 2011 11:41:47 +0000
Subject: [Tracker-discuss] [issue295] title is changed by email updates when
	only whitespace had	changed
In-Reply-To: <1248179761.3.0.0135867721483.issue295@psf.upfronthosting.co.za>
Message-ID: <1307446907.04.0.164368659518.issue295@psf.upfronthosting.co.za>


Ezio Melotti <ezio.melotti at gmail.com> added the comment:

This can be fixed in roundup-src/roundup/mailgw.py:1026 [0].
The split/join approach should be OK.  IIUC the title might still be changed if someone inserts for example a double space or a tab, and then the split/join removes it when someone replies via mail, but after the first normalization there shouldn't be other changes given by tabs inserted by the mail client.

[0]: http://svn.python.org/view/tracker/roundup-src/roundup/mailgw.py?view=markup

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue295>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Wed Jun  8 03:50:59 2011
From: metatracker at psf.upfronthosting.co.za (R David Murray)
Date: Wed, 08 Jun 2011 01:50:59 +0000
Subject: [Tracker-discuss] [issue295] title is changed by email updates when
	only whitespace had	changed
In-Reply-To: <1248179761.3.0.0135867721483.issue295@psf.upfronthosting.co.za>
Message-ID: <1307497859.55.0.371507985299.issue295@psf.upfronthosting.co.za>


R David Murray <rdmurray at bitdance.com> added the comment:

There is actually another problem here that this doesn't address.  What happens periodically is that someone changes the issue title, then someone else replies to a previous message on the issue, and the title gets changed back to the old title.  What would be ideal would be if we can detect that the change is sourced in an email submission and disallow changing the issue title from the email.  I think this would be acceptable since if I recall correctly we already disallow changing properties via the special syntax in the email title.

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue295>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Wed Jun  8 03:52:06 2011
From: metatracker at psf.upfronthosting.co.za (R David Murray)
Date: Wed, 08 Jun 2011 01:52:06 +0000
Subject: [Tracker-discuss] [issue295] title is changed by email updates when
	only whitespace had	changed
In-Reply-To: <1248179761.3.0.0135867721483.issue295@psf.upfronthosting.co.za>
Message-ID: <1307497926.66.0.980199341897.issue295@psf.upfronthosting.co.za>


R David Murray <rdmurray at bitdance.com> added the comment:

An advantage of doing the fix the way I just suggested is that it would be done in a reactor and not require a patch to the roundup source.

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue295>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Thu Jun  9 19:18:13 2011
From: metatracker at psf.upfronthosting.co.za (Ezio Melotti)
Date: Thu, 09 Jun 2011 17:18:13 +0000
Subject: [Tracker-discuss] [issue295] title is changed by email updates when
	only whitespace had	changed
In-Reply-To: <1248179761.3.0.0135867721483.issue295@psf.upfronthosting.co.za>
Message-ID: <1307639893.94.0.827160144877.issue295@psf.upfronthosting.co.za>


Ezio Melotti <ezio.melotti at gmail.com> added the comment:

Apparently there's no way for a detector to know if a message comes from an email or from the web interface, so using a detector to prevent title changes from emails is not possible.
The whitespace normalization can still be done with a detector though.  Another option is to do it in the mailgw, adding a config option to enable/disable it and submit the patch upstream to Roundup.
For the record the problem of the title changed while replying to an older message has been reported in #395.

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue295>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Thu Jun  9 22:44:07 2011
From: metatracker at psf.upfronthosting.co.za (Ezio Melotti)
Date: Thu, 09 Jun 2011 20:44:07 +0000
Subject: [Tracker-discuss] [issue396] Grant jython-dev user dev access on
	bugs.jython.org
In-Reply-To: <1303506250.16.0.899227765775.issue396@psf.upfronthosting.co.za>
Message-ID: <1307652247.67.0.573143473871.issue396@psf.upfronthosting.co.za>


Ezio Melotti <ezio.melotti at gmail.com> added the comment:

This should be fixed now.

----------
assignedto:  -> ezio.melotti
nosy: +ezio.melotti
status: unread -> resolved

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue396>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Thu Jun  9 22:57:30 2011
From: metatracker at psf.upfronthosting.co.za (Ezio Melotti)
Date: Thu, 09 Jun 2011 20:57:30 +0000
Subject: [Tracker-discuss] [issue374] Please remove email from post
In-Reply-To: <1296599531.18.0.468409864589.issue374@psf.upfronthosting.co.za>
Message-ID: <1307653050.38.0.15463076636.issue374@psf.upfronthosting.co.za>


Ezio Melotti <ezio.melotti at gmail.com> added the comment:

There's no way to edit messages (except maybe raw SQL or something similar), and since the message has been there for a few years now, I don't think removing it now will make a big difference.

----------
nosy: +ezio.melotti
status: chatting -> resolved

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue374>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Sat Jun 11 17:36:40 2011
From: metatracker at psf.upfronthosting.co.za (Vinay Sajip)
Date: Sat, 11 Jun 2011 15:36:40 +0000
Subject: [Tracker-discuss] [issue405] Mercurial integration - "Create Patch"
	fails with "No such	file or directory"
In-Reply-To: <1307806600.08.0.0276214976327.issue405@psf.upfronthosting.co.za>
Message-ID: <1307806600.08.0.0276214976327.issue405@psf.upfronthosting.co.za>


New submission from Vinay Sajip <vinay_sajip at yahoo.co.uk>:

I'm working on Issue 12291 in the Python tracker:

http://bugs.python.org/issue12291

I just pushed my changes to a public sandbox on hg.python.org, into a new branch that I created: fix12291:

http://hg.python.org/sandbox/vsajip#fix12291

I added the above repo URL to the "remote hg repo" field and it shows up, but when I clicked on "Create Patch" it failed with this error:

[Errno 2] No such file or directory: '/home/roundup/trackers/tracker/cpython/Doc/Makefile'

I clicked "Create Patch" again and it failed with the same error.

----------
messages: 2086
nosy: loewis, vinay.sajip
priority: bug
status: unread
title: Mercurial integration - "Create Patch" fails with "No such file or directory"

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue405>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Thu Jun 16 16:20:07 2011
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?=C3=89ric_Araujo?=)
Date: Thu, 16 Jun 2011 14:20:07 +0000
Subject: [Tracker-discuss] [issue405] Mercurial integration - "Create Patch"
	fails with "No such	file or directory"
In-Reply-To: <1307806600.08.0.0276214976327.issue405@psf.upfronthosting.co.za>
Message-ID: <1308234007.06.0.946387358169.issue405@psf.upfronthosting.co.za>


?ric Araujo <merwok at netwok.org> added the comment:

Same error on http://bugs.python.org/issue12344

----------
nosy: +eric.araujo
status: unread -> chatting

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue405>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Thu Jun 16 16:23:38 2011
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?=C3=89ric_Araujo?=)
Date: Thu, 16 Jun 2011 14:23:38 +0000
Subject: [Tracker-discuss] [issue382] Bad CC on review
In-Reply-To: <1301154873.73.0.955420098799.issue382@psf.upfronthosting.co.za>
Message-ID: <1308234218.31.0.10076579528.issue382@psf.upfronthosting.co.za>


?ric Araujo <merwok at netwok.org> added the comment:

I?ve sent a number of reviews to unexpanded names, thinking that Roundup would replace them with the email addresses :/

----------
nosy: +eric.araujo
status: unread -> chatting

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue382>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Thu Jun 16 16:26:32 2011
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?=C3=89ric_Araujo?=)
Date: Thu, 16 Jun 2011 14:26:32 +0000
Subject: [Tracker-discuss] [issue394] Better integration with Rietveld code
	review tool
In-Reply-To: <1303156350.85.0.792534425783.issue394@psf.upfronthosting.co.za>
Message-ID: <1308234392.7.0.38763629031.issue394@psf.upfronthosting.co.za>


?ric Araujo <merwok at netwok.org> added the comment:

+1 to a message.

----------
nosy: +eric.araujo
status: unread -> chatting

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue394>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Thu Jun 16 16:32:15 2011
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?=C3=89ric_Araujo?=)
Date: Thu, 16 Jun 2011 14:32:15 +0000
Subject: [Tracker-discuss] [issue397] Document that Python prompt is treated
	special
In-Reply-To: <1304364204.59.0.815639718869.issue397@psf.upfronthosting.co.za>
Message-ID: <1308234735.2.0.182924831508.issue397@psf.upfronthosting.co.za>


?ric Araujo <merwok at netwok.org> added the comment:

This looks more like the too aggressive removal of email quotes than special handing of the Python prompt.

----------
nosy: +eric.araujo
status: unread -> chatting

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue397>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Thu Jun 16 19:38:45 2011
From: metatracker at psf.upfronthosting.co.za (Ezio Melotti)
Date: Thu, 16 Jun 2011 17:38:45 +0000
Subject: [Tracker-discuss] [issue397] Document that Python prompt is treated
	special
In-Reply-To: <1304364204.59.0.815639718869.issue397@psf.upfronthosting.co.za>
Message-ID: <1308245925.52.0.334416595735.issue397@psf.upfronthosting.co.za>


Ezio Melotti <ezio.melotti at gmail.com> added the comment:

Isn't this the same problem described in http://psf.upfronthosting.co.za/roundup/meta/issue264 ?

----------
nosy: +ezio.melotti

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue397>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Fri Jun 17 11:45:57 2011
From: metatracker at psf.upfronthosting.co.za (Steffen Daode Nurpmeso)
Date: Fri, 17 Jun 2011 09:45:57 +0000
Subject: [Tracker-discuss] [issue397] Document that Python prompt is treated
	special
In-Reply-To: <1304364204.59.0.815639718869.issue397@psf.upfronthosting.co.za>
Message-ID: <1308303957.07.0.290832977578.issue397@psf.upfronthosting.co.za>


Steffen Daode Nurpmeso <sdaoden at gmail.com> added the comment:

@Ezio: Seems to really match issue 264 in respect to symptoms.
@?ric: Aggressive removal of email quotes - i don't know.
       (Good stuff seems to agree in not touching quotes at all. :)

Background:
At that time i've posted a lot of messages which did
   NL NL example-code NL NL
and it must have been just around the day that i've created
this issue here that something in the Python bug tracker was
changed to squeeze these NL NL pairs into single newlines.
So it seems that i thought first that the prompt stuff was
just a part of this "message cleanup" change.
But i still haven't looked into roundup sources, so i can
only be wrong.

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue397>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Fri Jun 17 17:38:22 2011
From: metatracker at psf.upfronthosting.co.za (Steffen Daode Nurpmeso)
Date: Fri, 17 Jun 2011 15:38:22 +0000
Subject: [Tracker-discuss] [issue397] Document that Python prompt is treated
	special
In-Reply-To: <1304364204.59.0.815639718869.issue397@psf.upfronthosting.co.za>
Message-ID: <1308325102.12.0.714626136892.issue397@psf.upfronthosting.co.za>


Steffen Daode Nurpmeso <sdaoden at gmail.com> added the comment:

(I close it?!  Oops, what to use?  Using "resolved"..)

----------
status: chatting -> resolved

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue397>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Sat Jun 18 11:36:28 2011
From: metatracker at psf.upfronthosting.co.za (anatoly techtonik)
Date: Sat, 18 Jun 2011 09:36:28 +0000
Subject: [Tracker-discuss] [issue407] bug in revision linking code
In-Reply-To: <1308389788.13.0.048506676138.issue407@psf.upfronthosting.co.za>
Message-ID: <1308389788.13.0.048506676138.issue407@psf.upfronthosting.co.za>


New submission from anatoly techtonik <techtonik at gmail.com>:

http://bugs.python.org/msg137584

are there any test written for those? What about Roundup itself?

----------
messages: 2095
nosy: techtonik
priority: bug
status: unread
title: bug in revision linking code

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue407>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Sat Jun 18 12:36:55 2011
From: metatracker at psf.upfronthosting.co.za (Ezio Melotti)
Date: Sat, 18 Jun 2011 10:36:55 +0000
Subject: [Tracker-discuss] [issue407] bug in revision linking code
In-Reply-To: <1308389788.13.0.048506676138.issue407@psf.upfronthosting.co.za>
Message-ID: <1308393415.08.0.902696047938.issue407@psf.upfronthosting.co.za>


Ezio Melotti <ezio.melotti at gmail.com> added the comment:

Yes, but it's difficult to get them right, since URLs and revision numbers are converted to links in two different places and both are always applied (i.e. you can't prevent links for URLs to be created if a link for revisions has been created already), so in some cases they might overlap.
I think this specific case can be solved by tweaking the regex, but there are and there will be other cases where it will fail.

----------
nosy: +ezio.melotti
status: unread -> chatting

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue407>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Sat Jun 18 13:12:41 2011
From: metatracker at psf.upfronthosting.co.za (anatoly techtonik)
Date: Sat, 18 Jun 2011 11:12:41 +0000
Subject: [Tracker-discuss] [issue407] bug in revision linking code
In-Reply-To: <1308389788.13.0.048506676138.issue407@psf.upfronthosting.co.za>
Message-ID: <1308395561.34.0.180138683685.issue407@psf.upfronthosting.co.za>


anatoly techtonik <techtonik at gmail.com> added the comment:

That's why I'd prefer to have this regex covered by test cases. Preferably in Roundup codebase itself, so that pydotorg won't have to deal with burden of maintaining this pile of hacks.

Can you be more specific about the problem? It is too abstract to see the exact cause.

Where are they converted?
When URLs are converted to links?
When revision numbers are converted?
Which rule is taken priority and where it is decided?

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue407>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Sun Jun 19 12:34:51 2011
From: metatracker at psf.upfronthosting.co.za (anatoly techtonik)
Date: Sun, 19 Jun 2011 10:34:51 +0000
Subject: [Tracker-discuss] [issue264] Mail gateway borks quotes and console
	sessions
In-Reply-To: <1239122891.37.0.849970456048.issue264@psf.upfronthosting.co.za>
Message-ID: <1308479691.23.0.835451416696.issue264@psf.upfronthosting.co.za>


anatoly techtonik <techtonik at gmail.com> added the comment:

It seems that Roundup need a standards based reST or Markdown editor

----------
nosy: +techtonik

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue264>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Sun Jun 19 15:15:14 2011
From: metatracker at psf.upfronthosting.co.za (Ezio Melotti)
Date: Sun, 19 Jun 2011 13:15:14 +0000
Subject: [Tracker-discuss] [issue407] bug in revision linking code
In-Reply-To: <1308389788.13.0.048506676138.issue407@psf.upfronthosting.co.za>
Message-ID: <1308489314.14.0.362652007845.issue407@psf.upfronthosting.co.za>


Ezio Melotti <ezio.melotti at gmail.com> added the comment:

URLs and issue numbers are converted by Roundup directly[0], all the other Python-specific linkifications are done in an extension[1].  The tests for the extension are in [3].  URLs are always converted to links, so the regexes in the extensions should figure out when a string is part of an URL and don't convert it to link.

[0]: http://svn.python.org/view/tracker/roundup-src/roundup/cgi/templating.py?view=markup (in StringHTMLProperty)
[1]: http://svn.python.org/view/tracker/instances/python-dev/extensions/local_replace.py?view=markup
[2]: http://svn.python.org/view/tracker/instances/python-dev/extensions/test/

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue407>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Sun Jun 19 16:53:36 2011
From: metatracker at psf.upfronthosting.co.za (R David Murray)
Date: Sun, 19 Jun 2011 14:53:36 +0000
Subject: [Tracker-discuss] [issue264] Mail gateway borks quotes and console
	sessions
In-Reply-To: <1239122891.37.0.849970456048.issue264@psf.upfronthosting.co.za>
Message-ID: <1308495216.72.0.451529227009.issue264@psf.upfronthosting.co.za>


R David Murray <rdmurray at bitdance.com> added the comment:

Even if it did, that would have zero effect on this issue.

Personally, I'd rather deal with the occasional lost text when someone is doing an email reply than to deal with the reams of quoted text resulting from top post replies.  I deal with the latter frequently with a work related (non-roundup) tracker, and it is a PITA to figure out what is actually going on in the tickets when I review them.

That said, we ought to be able to develop a heuristic that detects and preserves interactive session blocks.  Somebody has to do it, though :)

----------
nosy: +r.david.murray

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue264>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Sun Jun 19 17:05:51 2011
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?=C3=89ric_Araujo?=)
Date: Sun, 19 Jun 2011 15:05:51 +0000
Subject: [Tracker-discuss] [issue405] Mercurial integration - "Create Patch"
	fails with "No such	file or directory"
In-Reply-To: <1307806600.08.0.0276214976327.issue405@psf.upfronthosting.co.za>
Message-ID: <1308495951.73.0.824555628142.issue405@psf.upfronthosting.co.za>


?ric Araujo <merwok at netwok.org> added the comment:

My GSoC student found the reason of the problem: When we put a full Mercurial URI like http://blah#branch, the patch generation fails, we have to go to the edit repo form (on another page) and fill in separately the base URI and the branch.

It would be easier if both fields (repo and branch) were on the same page (i.e. the issue page), and/or the repo field parsed URIs like blah#branch.

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue405>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Sun Jun 19 17:24:24 2011
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v=2E_L=C3=B6wis?=)
Date: Sun, 19 Jun 2011 15:24:24 +0000
Subject: [Tracker-discuss] [issue405] Mercurial integration - "Create Patch"
	fails with "No such	file or directory"
In-Reply-To: <1307806600.08.0.0276214976327.issue405@psf.upfronthosting.co.za>
Message-ID: <1308497064.84.0.7191997674.issue405@psf.upfronthosting.co.za>


Martin v. L?wis <martin at v.loewis.de> added the comment:

I was hesitant to add another field into the UI, which is already overloaded, and it would make people assume that they have to fill out the branch field.
I assumed that using named branches would be uncommon enough to let people who use them go through a separate UI.

Not sure whether the syntax repo#branch is actually an established convention, or whether there is a different syntax that Mercurial folks use. Before supporting the syntax, this should be verified.

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue405>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Sun Jun 19 17:33:48 2011
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?=C3=89ric_Araujo?=)
Date: Sun, 19 Jun 2011 15:33:48 +0000
Subject: [Tracker-discuss] [issue405] Mercurial integration - "Create Patch"
	fails with "No such	file or directory"
In-Reply-To: <1307806600.08.0.0276214976327.issue405@psf.upfronthosting.co.za>
Message-ID: <1308497628.5.0.292565059583.issue405@psf.upfronthosting.co.za>


?ric Araujo <merwok at netwok.org> added the comment:

repo#branch is a supported format, not a convention for notation.  For example, I always recommend using ?hg clone http://hg.python.org/cpython#default? to avoid pulling 2.x branches.

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue405>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Sun Jun 19 17:57:54 2011
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v=2E_L=C3=B6wis?=)
Date: Sun, 19 Jun 2011 15:57:54 +0000
Subject: [Tracker-discuss] [issue405] Mercurial integration - "Create Patch"
	fails with "No such	file or directory"
In-Reply-To: <1307806600.08.0.0276214976327.issue405@psf.upfronthosting.co.za>
Message-ID: <1308499074.5.0.545350007814.issue405@psf.upfronthosting.co.za>


Martin v. L?wis <martin at v.loewis.de> added the comment:

Ah, ok. I recall trying the format in a browser, and it (probably not surprisingly) failed. I guess it's then ok to support the format when adding repositories; I wouldn't change the schema, though (i.e. keep repo and branch separated).

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue405>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Sun Jun 19 18:00:10 2011
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?=C3=89ric_Araujo?=)
Date: Sun, 19 Jun 2011 16:00:10 +0000
Subject: [Tracker-discuss] [issue405] Mercurial integration - "Create Patch"
	fails with "No such	file or directory"
In-Reply-To: <1307806600.08.0.0276214976327.issue405@psf.upfronthosting.co.za>
Message-ID: <1308499210.89.0.342327917214.issue405@psf.upfronthosting.co.za>


?ric Araujo <merwok at netwok.org> added the comment:

How did it fail in a browser?  It does not link to a fragment of the page, but the URI prior to the # sign still references a clonable Mercurial repo.

About the schema: sure, no need to change it.

Thanks for supporting repo#branch.

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue405>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Sun Jun 19 22:16:14 2011
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v=2E_L=C3=B6wis?=)
Date: Sun, 19 Jun 2011 20:16:14 +0000
Subject: [Tracker-discuss] [issue405] Mercurial integration - "Create Patch"
	fails with "No such	file or directory"
In-Reply-To: <1307806600.08.0.0276214976327.issue405@psf.upfronthosting.co.za>
Message-ID: <1308514574.76.0.427998716511.issue405@psf.upfronthosting.co.za>


Martin v. L?wis <martin at v.loewis.de> added the comment:

This is now fixed in r88855

----------
status: chatting -> resolved

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue405>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Sun Jun 19 22:17:52 2011
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?=C3=89ric_Araujo?=)
Date: Sun, 19 Jun 2011 20:17:52 +0000
Subject: [Tracker-discuss] [issue405] Mercurial integration - "Create Patch"
	fails with "No such	file or directory"
In-Reply-To: <1307806600.08.0.0276214976327.issue405@psf.upfronthosting.co.za>
Message-ID: <1308514672.45.0.520481402547.issue405@psf.upfronthosting.co.za>


?ric Araujo <merwok at netwok.org> added the comment:

Great, thanks!

----------
status: resolved -> chatting

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue405>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Sun Jun 19 22:51:43 2011
From: metatracker at psf.upfronthosting.co.za (Vinay Sajip)
Date: Sun, 19 Jun 2011 20:51:43 +0000
Subject: [Tracker-discuss] [issue405] Mercurial integration - "Create Patch"
	fails with "No such	file or directory"
In-Reply-To: <1308495951.73.0.824555628142.issue405@psf.upfronthosting.co.za>
Message-ID: <98061.14258.qm@web25808.mail.ukl.yahoo.com>


Vinay Sajip <vinay_sajip at yahoo.co.uk> added the comment:

> ?ric Araujo <merwok at netwok.org> added the  comment:
> 
> My GSoC student found the reason of the problem: When we put a  full Mercurial 
>URI like http://blah#branch, the patch generation fails, we have to go to the 
>edit  repo form (on another page) and fill in separately the base URI and the  
>branch.
> 
> It would be easier if both fields (repo and branch) were on the  same page 
>(i.e. the issue page), and/or the repo field parsed URIs like  blah#branch.

I had the impression from reading some posts about Mercurial integration (I 
think by MvL, but I may be misremembering that) that the system was already 
parsing branches from the blah#branch form - since then, that's how I've been 
adding repo URLs to the tracker.

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue405>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Sun Jun 19 23:26:35 2011
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?=C3=89ric_Araujo?=)
Date: Sun, 19 Jun 2011 21:26:35 +0000
Subject: [Tracker-discuss] [issue405] Mercurial integration - "Create Patch"
	fails with "No such	file or directory"
In-Reply-To: <1307806600.08.0.0276214976327.issue405@psf.upfronthosting.co.za>
Message-ID: <1308518795.05.0.998204174199.issue405@psf.upfronthosting.co.za>


?ric Araujo <merwok at netwok.org> added the comment:

Yep, see subthread starting at http://mail.python.org/pipermail/python-dev/2011-March/109819.html

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue405>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Sat Jun 25 02:19:22 2011
From: metatracker at psf.upfronthosting.co.za (Nick Coghlan)
Date: Sat, 25 Jun 2011 00:19:22 +0000
Subject: [Tracker-discuss] [issue394] Better integration with Rietveld code
	review tool
In-Reply-To: <1303156350.85.0.792534425783.issue394@psf.upfronthosting.co.za>
Message-ID: <1308961162.07.0.986994203934.issue394@psf.upfronthosting.co.za>


Nick Coghlan <ncoghlan at gmail.com> added the comment:

Yep, came here after reviewing an issue and posting a "Reviewed" comment to suggest much the same thing. Perhaps the tracker could be included on the cc list for the post-review notification?

----------
nosy: +ncoghlan

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue394>
_______________________________________________________

From jeanw2007 at gmail.com  Thu Jun 30 03:04:44 2011
From: jeanw2007 at gmail.com (Jing)
Date: Wed, 29 Jun 2011 21:04:44 -0400
Subject: [Tracker-discuss] Database of Issue Tracker
Message-ID: <BANLkTi=UUgxM20X3fHh6xzR+9xJg8XsTuA@mail.gmail.com>

Hi,

I want to get a copy of the database of issues in the issue tracker,
including histories of each issue. The current export function provided by
the issue tracker web interface only supports CSV format, which doesn't
record histories/logs.

Is there a way that I can access the full database, or something with
similar structure, such as exporting an XML file?

Thanks!
Jing
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/tracker-discuss/attachments/20110629/10cde59e/attachment.html>

From martin at v.loewis.de  Thu Jun 30 07:46:34 2011
From: martin at v.loewis.de (=?ISO-8859-1?Q?=22Martin_v=2E_L=F6wis=22?=)
Date: Thu, 30 Jun 2011 07:46:34 +0200
Subject: [Tracker-discuss] Database of Issue Tracker
In-Reply-To: <BANLkTi=UUgxM20X3fHh6xzR+9xJg8XsTuA@mail.gmail.com>
References: <BANLkTi=UUgxM20X3fHh6xzR+9xJg8XsTuA@mail.gmail.com>
Message-ID: <4E0C0DBA.6040005@v.loewis.de>

> I want to get a copy of the database of issues in the issue tracker,
> including histories of each issue. The current export function provided
> by the issue tracker web interface only supports CSV format, which
> doesn't record histories/logs.
> 
> Is there a way that I can access the full database, or something with
> similar structure, such as exporting an XML file?

There is a certain amount of private data in the database (such as email
addresses and encrypted passwords) which I don't want to make available.
Please let me know in private what exactly it is that you need and what
you need it for, and I'll see what I can do.

Regards,
Martin