From metatracker at psf.upfronthosting.co.za  Sat Sep  1 19:23:36 2012
From: metatracker at psf.upfronthosting.co.za (Ezio Melotti)
Date: Sat, 01 Sep 2012 17:23:36 +0000
Subject: [Tracker-discuss] [issue414] Mercurial integration: verify repo
	when adding
In-Reply-To: <1312642333.95.0.845747072773.issue414@psf.upfronthosting.co.za>
Message-ID: <1346520216.14.0.473927472129.issue414@psf.upfronthosting.co.za>


Ezio Melotti added the comment:

> (FTR, the Bitbucket https URIs are not private, this may be yet another bug.)

This should be fixed with ebed4eccab36.

The error reported by the tracker was "('invalid token', 90)", and was caused by:

>>> old = 'max(ancestors(branch("%s")))-outgoing("%s"))' % (patchbranch, base)
>>> commands.diff(repo.ui, repo, rev=[old, patchbranch])
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/usr/lib/python2.7/dist-packages/mercurial/commands.py", line 2319, in diff
    node1, node2 = scmutil.revpair(repo, revs)
  File "/usr/lib/python2.7/dist-packages/mercurial/scmutil.py", line 497, in revpair
    l = revrange(repo, revs)
  File "/usr/lib/python2.7/dist-packages/mercurial/scmutil.py", line 549, in revrange
    m = revset.match(repo.ui, spec)
  File "/usr/lib/python2.7/dist-packages/mercurial/revset.py", line 1046, in match
    raise error.ParseError(_("invalid token"), pos)
mercurial.error.ParseError: ('invalid token', 90)

The problem was an extra ')', and http://mail.python.org/pipermail/python-dev/2011-November/114704.html told me which one had to be removed.  Bitbucket remote repos should now work.

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

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

From metatracker at psf.upfronthosting.co.za  Thu Sep  6 15:55:33 2012
From: metatracker at psf.upfronthosting.co.za (Barry Warsaw)
Date: Thu, 06 Sep 2012 13:55:33 +0000
Subject: [Tracker-discuss] [issue478] Cannot enter issue # in tracker
Message-ID: <1346939733.36.0.906385893452.issue478@psf.upfronthosting.co.za>


New submission from Barry Warsaw:

Go to bugs.python.org and enter 4194 (or any number) into the tracker's Show Issue field, then click on Show Issue.  You get an error page saying

broken form: multiple @action values submitted

Tested on Chromium 20.0.1132.47 Ubuntu 12.10 (144678)

----------
messages: 2581
nosy: barry
priority: urgent
status: unread
title: Cannot enter issue # in tracker

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

From metatracker at psf.upfronthosting.co.za  Thu Sep  6 16:26:26 2012
From: metatracker at psf.upfronthosting.co.za (R David Murray)
Date: Thu, 06 Sep 2012 14:26:26 +0000
Subject: [Tracker-discuss] [issue478] Cannot enter issue # in tracker
In-Reply-To: <1346939733.36.0.906385893452.issue478@psf.upfronthosting.co.za>
Message-ID: <1346941586.03.0.817269086688.issue478@psf.upfronthosting.co.za>


R David Murray added the comment:

This is probably a duplicate of issue 448.

----------
nosy: +r.david.murray
status: unread -> chatting

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

From metatracker at psf.upfronthosting.co.za  Thu Sep  6 17:24:13 2012
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v=2E_L=C3=B6wis?=)
Date: Thu, 06 Sep 2012 15:24:13 +0000
Subject: [Tracker-discuss] [issue478] Cannot enter issue # in tracker
In-Reply-To: <1346939733.36.0.906385893452.issue478@psf.upfronthosting.co.za>
Message-ID: <1346945053.23.0.658228462989.issue478@psf.upfronthosting.co.za>


Martin v. L?wis added the comment:

Indeed.

barry: can you please report the exact URL your browser was pointing to when you entered the number? Performing your instructions fails to reproduce the issue; entering 4194 after typing "bugs.python.org" in the URL bar in Chrome works just fine for me.

Most likely, you had search results displayed when entering the number.

----------
nosy: +loewis
priority: urgent -> bug

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

From barry at python.org  Thu Sep  6 17:40:13 2012
From: barry at python.org (Barry Warsaw)
Date: Thu, 6 Sep 2012 11:40:13 -0400
Subject: [Tracker-discuss] [issue478] Cannot enter issue # in tracker
In-Reply-To: <1346945053.23.0.658228462989.issue478@psf.upfronthosting.co.za>
References: <1346939733.36.0.906385893452.issue478@psf.upfronthosting.co.za>
	<1346945053.23.0.658228462989.issue478@psf.upfronthosting.co.za>
Message-ID: <20120906114013.744df93b@resist.wooz.org>

On Sep 06, 2012, at 03:24 PM, Martin v. L?wis wrote:

>barry: can you please report the exact URL your browser was pointing to when
>you entered the number? Performing your instructions fails to reproduce the
>issue; entering 4194 after typing "bugs.python.org" in the URL bar in Chrome
>works just fine for me.
>
>Most likely, you had search results displayed when entering the number.

You're exactly right Martin.  I searched in the top search bar for "subprocess
bufsize" and it was on the results page that I entered 4194 and got the
error.  If I just go to http://bugs.python.org and enter 4194, there's no
problem.

From metatracker at psf.upfronthosting.co.za  Thu Sep  6 17:40:17 2012
From: metatracker at psf.upfronthosting.co.za (Barry Warsaw)
Date: Thu, 06 Sep 2012 15:40:17 +0000
Subject: [Tracker-discuss] [issue478] Cannot enter issue # in tracker
In-Reply-To: <1346945053.23.0.658228462989.issue478@psf.upfronthosting.co.za>
Message-ID: <20120906114013.744df93b@resist.wooz.org>


Barry Warsaw added the comment:

On Sep 06, 2012, at 03:24 PM, Martin v. L?wis wrote:

>barry: can you please report the exact URL your browser was pointing to when
>you entered the number? Performing your instructions fails to reproduce the
>issue; entering 4194 after typing "bugs.python.org" in the URL bar in Chrome
>works just fine for me.
>
>Most likely, you had search results displayed when entering the number.

You're exactly right Martin.  I searched in the top search bar for "subprocess
bufsize" and it was on the results page that I entered 4194 and got the
error.  If I just go to http://bugs.python.org and enter 4194, there's no
problem.

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

From metatracker at psf.upfronthosting.co.za  Sat Sep  8 07:00:57 2012
From: metatracker at psf.upfronthosting.co.za (Chris Jerdonek)
Date: Sat, 08 Sep 2012 05:00:57 +0000
Subject: [Tracker-discuss] [issue479] Add "Committer List" link below "User
	List"
Message-ID: <1347080457.03.0.685725820762.issue479@psf.upfronthosting.co.za>


New submission from Chris Jerdonek:

This issue is to add a "Committer List" link below the "User List" link.

Nick suggested this idea on python-dev (in the context of a discussion to allow users to add an IRC handle):

http://mail.python.org/pipermail/python-dev/2012-August/121519.html

The URL might look something like this:

http://bugs.python.org/user?iscommitter=1&@action=search&@sort=username&@pagesize=300

(R. David Murray also suggested increasing the page size for this link so that all committers would display on a single page.)

----------
messages: 2585
nosy: chris.jerdonek
priority: feature
status: unread
title: Add "Committer List" link below "User List"

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

From metatracker at psf.upfronthosting.co.za  Sat Sep  8 12:53:30 2012
From: metatracker at psf.upfronthosting.co.za (Ezio Melotti)
Date: Sat, 08 Sep 2012 10:53:30 +0000
Subject: [Tracker-discuss] [issue479] Add "Committer List" link below "User
	List"
In-Reply-To: <1347080457.03.0.685725820762.issue479@psf.upfronthosting.co.za>
Message-ID: <1347101610.35.0.910653990667.issue479@psf.upfronthosting.co.za>


Ezio Melotti added the comment:

Done in 5db35bf7b557.

----------
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/issue479>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Sat Sep  8 12:55:29 2012
From: metatracker at psf.upfronthosting.co.za (Ezio Melotti)
Date: Sat, 08 Sep 2012 10:55:29 +0000
Subject: [Tracker-discuss] [issue478] Cannot enter issue # in tracker
In-Reply-To: <1346939733.36.0.906385893452.issue478@psf.upfronthosting.co.za>
Message-ID: <1347101729.04.0.231462288683.issue478@psf.upfronthosting.co.za>


Ezio Melotti added the comment:

Closing as duplicate of #448.

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

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

From metatracker at psf.upfronthosting.co.za  Sat Sep  8 13:05:42 2012
From: metatracker at psf.upfronthosting.co.za (Ezio Melotti)
Date: Sat, 08 Sep 2012 11:05:42 +0000
Subject: [Tracker-discuss] [issue473] Cannot edit (eg) component: No such
	action "editcsv"
In-Reply-To: <1344111678.46.0.378003951263.issue473@psf.upfronthosting.co.za>
Message-ID: <1347102342.66.0.367661277667.issue473@psf.upfronthosting.co.za>


Ezio Melotti added the comment:

editcsv was disabled by MvL in 7337c08edc4c.  I'm adding him to the nosy so he can comment.

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

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

From metatracker at psf.upfronthosting.co.za  Sat Sep  8 14:12:26 2012
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v=2E_L=C3=B6wis?=)
Date: Sat, 08 Sep 2012 12:12:26 +0000
Subject: [Tracker-discuss] [issue473] Cannot edit (eg) component: No such
	action "editcsv"
In-Reply-To: <1344111678.46.0.378003951263.issue473@psf.upfronthosting.co.za>
Message-ID: <1347106346.04.0.703324740875.issue473@psf.upfronthosting.co.za>


Martin v. L?wis added the comment:

It was temporarily disabled in r70258 (Mar 9 06:19:15 2009)

http://svn.python.org/view/tracker/roundup-src/roundup/cgi/client.py?r1=70258&r2=70388&pathrev=88900

but re-enabled in r70388 (Mar 15 21:43:30 2009)

http://svn.python.org/view/tracker/roundup-src/roundup/cgi/client.py?r1=70258&r2=70388&pathrev=88900

That this change survived is probably a glitch in the Mercurial migration.

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

From metatracker at psf.upfronthosting.co.za  Sat Sep  8 14:20:14 2012
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v=2E_L=C3=B6wis?=)
Date: Sat, 08 Sep 2012 12:20:14 +0000
Subject: [Tracker-discuss] [issue473] Typo
In-Reply-To: <1347102342.66.0.367661277667.issue473@psf.upfronthosting.co.za>
Message-ID: <20120908142012.Horde.WKwJTqGZi1VQSzf8OtpnT4A@webmail.df.eu>


Martin v. L?wis added the comment:

Commiter -> Committer

Regards,
Martin

----------
title: Cannot edit (eg) component: No such action "editcsv" -> Typo

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

From metatracker at psf.upfronthosting.co.za  Sat Sep  8 19:07:03 2012
From: metatracker at psf.upfronthosting.co.za (Chris Jerdonek)
Date: Sat, 08 Sep 2012 17:07:03 +0000
Subject: [Tracker-discuss] [issue480] Add "IRC Handle" to user details
Message-ID: <1347124023.25.0.886765458921.issue480@psf.upfronthosting.co.za>


New submission from Chris Jerdonek:

This issue is to add "IRC Handle" to the list of editable user details as was discussed on python-dev in a thread starting here:

http://mail.python.org/pipermail/python-dev/2012-August/121516.html

Nick suggested the specific idea to do this on Roundup.

Once this is done, I feel that IRC Handle should be added as a displayed column in both the "User List" and "Committer List" pages.  (By the nature of how IRC is used, the IRC handle field is much more useful if one could see the handles of a list of users at once.)

On a related note, would there be a way from the UI to display only those users with an IRC handle (e.g. by doing a certain type of search), so that one could see more easily the IRC handles of non-core developers?  Or would that need to be added?

----------
messages: 2591
nosy: chris.jerdonek
priority: feature
status: unread
title: Add "IRC Handle" to user details

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

From metatracker at psf.upfronthosting.co.za  Sat Sep  8 19:15:00 2012
From: metatracker at psf.upfronthosting.co.za (Chris Jerdonek)
Date: Sat, 08 Sep 2012 17:15:00 +0000
Subject: [Tracker-discuss] [issue481] Display committer icon in user search
	result lists
Message-ID: <1347124500.02.0.523594657274.issue481@psf.upfronthosting.co.za>


New submission from Chris Jerdonek:

On the core-mentorship list, R. David Murray observed that the committer icon does not display next to usernames in user search result lists, e.g. here:

http://bugs.python.org/user?iscommitter=1&@action=search&@sort=username&@pagesize=300

(though, for example, the * for the Contrib form does).

This issue is to add the committer icon when appropriate.

----------
messages: 2592
nosy: chris.jerdonek
priority: feature
status: unread
title: Display committer icon in user search result lists

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

From metatracker at psf.upfronthosting.co.za  Sat Sep  8 20:23:20 2012
From: metatracker at psf.upfronthosting.co.za (Ezio Melotti)
Date: Sat, 08 Sep 2012 18:23:20 +0000
Subject: [Tracker-discuss] [issue481] Display committer icon in user search
	result lists
In-Reply-To: <1347124500.02.0.523594657274.issue481@psf.upfronthosting.co.za>
Message-ID: <1347128600.16.0.552028892769.issue481@psf.upfronthosting.co.za>


Ezio Melotti added the comment:

Currently the committer icon is "hardcoded" in the issue.item.html template.
I guess it could be added to the user list too, either as a separate "is committer" column, or as an icon.
I don't think it should appear next to each occurrence of the name, for example in the "creator"/"assigned to" fields of the issue list page.

----------
nosy: +ezio.melotti, r.david.murray
status: unread -> chatting

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

From metatracker at psf.upfronthosting.co.za  Sat Sep  8 20:27:49 2012
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v=2E_L=C3=B6wis?=)
Date: Sat, 08 Sep 2012 18:27:49 +0000
Subject: [Tracker-discuss] [issue481] Display committer icon in user search
	result lists
In-Reply-To: <1347124500.02.0.523594657274.issue481@psf.upfronthosting.co.za>
Message-ID: <1347128869.21.0.155642408386.issue481@psf.upfronthosting.co.za>


Martin v. L?wis added the comment:

I agree that the icon shouldn't be displayed in every place the name occurs. I'm skeptical whether it has value in the user search list. If the complaint is only about consistency, I propose to make it consistent by also dropping the "contrib form received" symbol from user.list.

----------
nosy: +loewis

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

From metatracker at psf.upfronthosting.co.za  Sat Sep  8 20:48:36 2012
From: metatracker at psf.upfronthosting.co.za (Chris Jerdonek)
Date: Sat, 08 Sep 2012 18:48:36 +0000
Subject: [Tracker-discuss] [issue481] Display committer icon in user search
	result lists
In-Reply-To: <1347124500.02.0.523594657274.issue481@psf.upfronthosting.co.za>
Message-ID: <1347130116.19.0.931746378973.issue481@psf.upfronthosting.co.za>


Chris Jerdonek added the comment:

Personally, I think seeing the committer/contrib status is useful on the user list (though it is not important that the committer status be communicated via a graphical icon).  For tracker purposes, I think this may even be more useful than, say, seeing the user's "Organisation," and it takes up less space.  What if some other character were used?

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

From metatracker at psf.upfronthosting.co.za  Sat Sep  8 21:31:11 2012
From: metatracker at psf.upfronthosting.co.za (R David Murray)
Date: Sat, 08 Sep 2012 19:31:11 +0000
Subject: [Tracker-discuss] [issue481] Display committer icon in user search
	result lists
In-Reply-To: <1347124500.02.0.523594657274.issue481@psf.upfronthosting.co.za>
Message-ID: <1347132671.47.0.36880438528.issue481@psf.upfronthosting.co.za>


R David Murray added the comment:

If the contributor icon is not added, I think removing the contrib form received marker would be good.  As it is, one is fooled into expecting both icons should be there when appropriate, and might mistakenly think someone is not a committer because the commiter one is absent.  With no markers there would be no such implicit expectation.

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

From metatracker at psf.upfronthosting.co.za  Sat Sep  8 21:56:28 2012
From: metatracker at psf.upfronthosting.co.za (Chris Jerdonek)
Date: Sat, 08 Sep 2012 19:56:28 +0000
Subject: [Tracker-discuss] [issue482] display revision links in log page
Message-ID: <1347134188.64.0.383823664446.issue482@psf.upfronthosting.co.za>


New submission from Chris Jerdonek:

It seems like the entries on the "log" page don't always link to the corresponding revision:

http://hg.python.org/cpython/shortlog

This seems to happen when the revision description itself begins with text that results in a link to something else (e.g. an issue number).

In contrast, the "graph" page seems always to link to the revision:

http://hg.python.org/cpython/graph

Related to this, if the description field contains text that results in a link to something else, then the UI doesn't make a distinction between the portion of the description that links to the revision and the portion that links to the something else.

For example, with description text "Fix for fcc629208842", "Fix for" links to the revision, but "fcc629208842" links to the named revision.

It might be better if the revision link was separate from the description.  That would be one way to address both of the issues above.

----------
messages: 2597
nosy: chris.jerdonek
priority: feature
status: unread
title: display revision links in log page

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

From metatracker at psf.upfronthosting.co.za  Sat Sep  8 22:03:13 2012
From: metatracker at psf.upfronthosting.co.za (Chris Jerdonek)
Date: Sat, 08 Sep 2012 20:03:13 +0000
Subject: [Tracker-discuss] [issue482] log page entries don't always link to
	revision
In-Reply-To: <1347134188.64.0.383823664446.issue482@psf.upfronthosting.co.za>
Message-ID: <1347134593.89.0.513407982204.issue482@psf.upfronthosting.co.za>


Chris Jerdonek added the comment:

Also, let me know if I didn't file this in the right place.  This is "meta" to Python and so I didn't think appropriate for bugs.python.org.  On the other hand, it's not related to the Roundup instance which this issue list may be limited to.

----------
status: unread -> chatting

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

From metatracker at psf.upfronthosting.co.za  Sat Sep  8 22:28:25 2012
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v=2E_L=C3=B6wis?=)
Date: Sat, 08 Sep 2012 20:28:25 +0000
Subject: [Tracker-discuss] [issue482] log page entries don't always link to
	revision
In-Reply-To: <1347134188.64.0.383823664446.issue482@psf.upfronthosting.co.za>
Message-ID: <1347136105.37.0.27815965546.issue482@psf.upfronthosting.co.za>


Martin v. L?wis added the comment:

This is not an issue of the bug tracker (i.e. bugs.python.org).

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

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

From metatracker at psf.upfronthosting.co.za  Sat Sep  8 22:37:49 2012
From: metatracker at psf.upfronthosting.co.za (Chris Jerdonek)
Date: Sat, 08 Sep 2012 20:37:49 +0000
Subject: [Tracker-discuss] [issue482] log page entries don't always link to
	revision
In-Reply-To: <1347134188.64.0.383823664446.issue482@psf.upfronthosting.co.za>
Message-ID: <1347136669.89.0.578257631063.issue482@psf.upfronthosting.co.za>


Chris Jerdonek added the comment:

Understood, though where should this be filed?

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

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

From metatracker at psf.upfronthosting.co.za  Sat Sep  8 22:40:15 2012
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v=2E_L=C3=B6wis?=)
Date: Sat, 08 Sep 2012 20:40:15 +0000
Subject: [Tracker-discuss] [issue482] log page entries don't always link to
	revision
In-Reply-To: <1347134188.64.0.383823664446.issue482@psf.upfronthosting.co.za>
Message-ID: <1347136815.43.0.300763580147.issue482@psf.upfronthosting.co.za>


Martin v. L?wis added the comment:

I don't know; I don't think there is a tracker for it. You should probably ask the maintainers of the hg installation (i.e. Antoine and Georg).

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

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

From metatracker at psf.upfronthosting.co.za  Sat Sep  8 22:44:32 2012
From: metatracker at psf.upfronthosting.co.za (Chris Jerdonek)
Date: Sat, 08 Sep 2012 20:44:32 +0000
Subject: [Tracker-discuss] [issue482] log page entries don't always link to
	revision
In-Reply-To: <1347134188.64.0.383823664446.issue482@psf.upfronthosting.co.za>
Message-ID: <1347137072.33.0.0372165390006.issue482@psf.upfronthosting.co.za>


Chris Jerdonek added the comment:

Okay, I've asked on python-dev.  We'll see what they say.

http://mail.python.org/pipermail/python-dev/2012-September/121632.html

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

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

From metatracker at psf.upfronthosting.co.za  Sat Sep  8 22:45:19 2012
From: metatracker at psf.upfronthosting.co.za (Chris Jerdonek)
Date: Sat, 08 Sep 2012 20:45:19 +0000
Subject: [Tracker-discuss] [issue482] log page entries don't always link to
	revision
In-Reply-To: <1347134188.64.0.383823664446.issue482@psf.upfronthosting.co.za>
Message-ID: <1347137119.01.0.0796554671881.issue482@psf.upfronthosting.co.za>


Chris Jerdonek added the comment:

(It doesn't seem like there is a way to keep the status set to resolved when commenting on a resolved issue.)

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

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

From metatracker at psf.upfronthosting.co.za  Sun Sep  9 17:25:51 2012
From: metatracker at psf.upfronthosting.co.za (Ezio Melotti)
Date: Sun, 09 Sep 2012 15:25:51 +0000
Subject: [Tracker-discuss] [issue481] Display committer icon in user search
	result lists
In-Reply-To: <1347124500.02.0.523594657274.issue481@psf.upfronthosting.co.za>
Message-ID: <1347204351.21.0.774811384096.issue481@psf.upfronthosting.co.za>


Ezio Melotti added the comment:

Removing the "*" is fine with me.
A couple of alternatives I was considering are:
1) add the information in a tooltip, so that it shows something like "[committer] Name Surname" or "[contributor] Name Surname";
2) use smaller icons and have a black&white one for contributors and a colored one for committers;

If we make sure that all the committers have signed the contributor form, we could also use the "committer" tooltip/icon as a superset of "contributor", without having to use two separate icons.

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

From metatracker at psf.upfronthosting.co.za  Wed Sep 12 18:17:25 2012
From: metatracker at psf.upfronthosting.co.za (Ezio Melotti)
Date: Wed, 12 Sep 2012 16:17:25 +0000
Subject: [Tracker-discuss] [issue473] Cannot edit (eg) component: No such
	action "editcsv"
In-Reply-To: <1344111678.46.0.378003951263.issue473@psf.upfronthosting.co.za>
Message-ID: <1347466645.02.0.00537884346452.issue473@psf.upfronthosting.co.za>


Ezio Melotti added the comment:

This is fixed in f3f06a648171.
I also removed Colin's UID to test the fix.

----------
assignedto:  -> ezio.melotti
status: chatting -> resolved

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

From metatracker at psf.upfronthosting.co.za  Tue Sep 25 20:43:14 2012
From: metatracker at psf.upfronthosting.co.za (Ezio Melotti)
Date: Tue, 25 Sep 2012 18:43:14 +0000
Subject: [Tracker-discuss] [issue144] email with one out of three patches
	is	confusing
In-Reply-To: <1188515828.87.0.955745320995.issue144@psf.upfronthosting.co.za>
Message-ID: <1348598594.97.0.76104585416.issue144@psf.upfronthosting.co.za>


Ezio Melotti added the comment:

Currently a mail is sent even when a single file with no comment is added, and it's also possible to send several files at once via email (see e.g. http://bugs.python.org/msg171305), so I think this can be considered resolved.

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

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

From metatracker at psf.upfronthosting.co.za  Fri Sep 28 14:07:33 2012
From: metatracker at psf.upfronthosting.co.za (Ezio Melotti)
Date: Fri, 28 Sep 2012 12:07:33 +0000
Subject: [Tracker-discuss] [issue483] irker detector for roundup
Message-ID: <1348834053.04.0.0348292997231.issue483@psf.upfronthosting.co.za>


New submission from Ezio Melotti:

Now that CIA is dead I wrote a new Roundup detector that uses irker [0][1] instead of CIA.  I tested it locally and it seems to work fine.  It requires irclib [2] and the irker daemon running in background.
If that's OK, I'll push the detector, download/install irclib on b.p.o and start the irker daemon.  It's also necessary to add 
[irker]
channels = irc://chat.freenode.net/#python-dev
to detectors/config.ini to make it work.

[0]: http://www.catb.org/esr/irker/
[1]: http://esr.ibiblio.org/?p=4607
[2]: http://sourceforge.net/projects/python-irclib/files/irc-2.0.1.zip/download

----------
assignedto: ezio.melotti
messages: 2607
nosy: ezio.melotti, loewis
priority: urgent
status: unread
title: irker detector for roundup

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

From metatracker at psf.upfronthosting.co.za  Fri Sep 28 17:31:29 2012
From: metatracker at psf.upfronthosting.co.za (Ezio Melotti)
Date: Fri, 28 Sep 2012 15:31:29 +0000
Subject: [Tracker-discuss] [issue483] irker detector for roundup
In-Reply-To: <1348834053.04.0.0348292997231.issue483@psf.upfronthosting.co.za>
Message-ID: <1348846289.38.0.684197561367.issue483@psf.upfronthosting.co.za>


Ezio Melotti added the comment:

I installed irclib, irker, the attached detector and started the daemon.
Everything seems to work fine, I'll test it for a few days and then commit everything if there are no problems.

----------
priority: urgent -> feature
status: unread -> testing

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