From metatracker at psf.upfronthosting.co.za  Fri Feb  6 21:35:11 2009
From: metatracker at psf.upfronthosting.co.za (Jean-Paul Calderone)
Date: Fri, 06 Feb 2009 20:35:11 +0000
Subject: [Tracker-discuss] [issue234] python-dev tracker summary emails
	contain incorrect "median duration of open issues" information
In-Reply-To: <1233952511.91.0.674582983418.issue234@psf.upfronthosting.co.za>
Message-ID: <1233952511.91.0.674582983418.issue234@psf.upfronthosting.co.za>


New submission from Jean-Paul Calderone <exarkun at twistedmatrix.com>:

The weekly tracker summary emails sent to python-dev contain incorrect
information.  The value for the "median duration of open issues" it
reports has recently wrapped around to 0 and started growing from there.
 Looking at older reports, it's clear that there's a bug in the
calculation of this value, since it jumps from a median of several years
to a median of one day in the span of one week.

----------
messages: 1138
nosy: exarkun
priority: bug
status: unread
title: python-dev tracker summary emails contain incorrect "median duration of open issues" information

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

From metatracker at psf.upfronthosting.co.za  Sun Feb  8 01:14:59 2009
From: metatracker at psf.upfronthosting.co.za (Daniel Diniz)
Date: Sun, 08 Feb 2009 00:14:59 +0000
Subject: [Tracker-discuss] [issue234] python-dev tracker summary emails
	contain incorrect "median duration of open issues" information
In-Reply-To: <1233952511.91.0.674582983418.issue234@psf.upfronthosting.co.za>
Message-ID: <1234052099.89.0.369894211117.issue234@psf.upfronthosting.co.za>


Daniel Diniz <ajaksu at gmail.com> added the comment:

It seems that the problem isn't an overflow.

To find the median Roundup sorts on issue id and picks the middle, but
bugs.python.org has lots of sf.net ids. Since these ids are higher and
older, the sort is broken.

Ordering by ID, one can see where the median is now: http://tinyurl.com/d4oowj

Click "next" a few times and you'll get to where it was a month ago (i.e, in
some ancient sf.net bug). So it's a long-standing bug.

I believe the attached patch (against
tracker/instances/python-dev/scripts/roundup-summary ) should fix it.

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

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue234>
_______________________________________________________
-------------- next part --------------
A non-text attachment was scrubbed...
Name: summary.diff
Type: text/x-diff
Size: 396 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/tracker-discuss/attachments/20090208/c509b707/attachment.diff>

From metatracker at psf.upfronthosting.co.za  Sun Feb  8 10:43:35 2009
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v._L=C3=B6wis?=)
Date: Sun, 08 Feb 2009 09:43:35 +0000
Subject: [Tracker-discuss] [issue234] python-dev tracker summary emails
	contain incorrect "median duration of open issues" information
In-Reply-To: <1233952511.91.0.674582983418.issue234@psf.upfronthosting.co.za>
Message-ID: <1234086215.84.0.820705473201.issue234@psf.upfronthosting.co.za>


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

Thanks for the patch, committed as r69430. The median duration is now computed
as 435 days

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

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

From metatracker at psf.upfronthosting.co.za  Wed Feb 18 06:11:47 2009
From: metatracker at psf.upfronthosting.co.za (Gregory P Smith)
Date: Wed, 18 Feb 2009 05:11:47 +0000
Subject: [Tracker-discuss] [issue235] incorrent To: headers in mail sent
	from tracker upon error processing email
In-Reply-To: <1234933907.44.0.734315958943.issue235@psf.upfronthosting.co.za>
Message-ID: <1234933907.44.0.734315958943.issue235@psf.upfronthosting.co.za>


New submission from Gregory P Smith <greg at krypto.org>:

I tried to reply to an issue via email to add a note.  That failed.  But more
interesting is that:

A) the To: header in the email from the tracker is messed up (see the headers
below).
B) I received the failure email from the tracker at all (it apparently used my
actual email address to perform the delivery, despite messing up the To: header).

It looks like something expecting a sequence got a string.  Possibly a mimetools
usage issue as headers can often have multiple values thus it expects sequences
rather than individual strings somewhere?


Delivered-To: greg at krypto.org
Received: by 10.103.118.18 with SMTP id v18cs239649mum;
        Tue, 17 Feb 2009 19:32:16 -0800 (PST)
Received: by 10.181.61.7 with SMTP id o7mr2623482bkk.51.1234927936727;
        Tue, 17 Feb 2009 19:32:16 -0800 (PST)
Return-Path: <roundup-admin at psf.upfronthosting.co.za>
Received: from psf.upfronthosting.co.za (bugs.python.org [88.198.142.26])
        by mx.google.com with ESMTP id 19si6367756bwz.83.2009.02.17.19.32.15;
        Tue, 17 Feb 2009 19:32:16 -0800 (PST)
Received-SPF: neutral (google.com: 88.198.142.26 is neither permitted nor denied
by best guess record for domain of roundup-admin at psf.upfronthosting.co.za)
client-ip=88.198.142.26;
Authentication-Results: mx.google.com; spf=neutral (google.com: 88.198.142.26 is
neither permitted nor denied by best guess record for domain of
roundup-admin at psf.upfronthosting.co.za)
smtp.mail=roundup-admin at psf.upfronthosting.co.za
Received: from psf.upfronthosting.co.za (localhost [10.0.0.1])
	by psf.upfronthosting.co.za (Postfix) with ESMTP id 44F387863C
	for <greg at krypto.org>; Wed, 18 Feb 2009 04:32:15 +0100 (CET)
Content-Type: multipart/mixed;
    boundary="88.198.142.26.1006.25012.1234927935.280.1"
Subject: Failed issue tracker submission
To: g at psf.upfronthosting.co.za, r at psf.upfronthosting.co.za,
	e at psf.upfronthosting.co.za, g at psf.upfronthosting.co.za, "",
	k at psf.upfronthosting.co.za, r at psf.upfronthosting.co.za,
	y at psf.upfronthosting.co.za, p at psf.upfronthosting.co.za,
	t at psf.upfronthosting.co.za, o at psf.upfronthosting.co.za,
	"."@psf.upfronthosting.co.za, o at psf.upfronthosting.co.za,
	r at psf.upfronthosting.co.za, g at psf.upfronthosting.co.za
From: Python tracker <roundup-admin at psf.upfronthosting.co.za>
Date: Wed, 18 Feb 2009 03:32:15 +0000
X-Roundup-Name: Python tracker
X-Roundup-Loop: hello
X-Roundup-Version: 1.4.2
MIME-Version: 1.0
Message-Id: <20090218033215.44F387863C at psf.upfronthosting.co.za>


--88.198.142.26.1006.25012.1234927935.280.1
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


An unexpected error occurred during the processing
of your message. The tracker administrator is being
notified.

....

----------
messages: 1141
nosy: gregory.p.smith
priority: bug
status: unread
title: incorrent To: headers in mail sent from tracker upon error processing email

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

From asmodai at in-nomine.org  Wed Feb 18 07:14:19 2009
From: asmodai at in-nomine.org (Jeroen Ruigrok van der Werven)
Date: Wed, 18 Feb 2009 07:14:19 +0100
Subject: [Tracker-discuss] Updating to Roundup 1.4.6
Message-ID: <20090218061419.GK91939@nexus.in-nomine.org>

I was talking in private with Daniel about the tracker and getting the
desired features and such implemented. I noticed we are currently on 1.4.2
of the official Roundup tree with additional custom changes. Since I've done
quite a bit of merging in newer releases from a vendor in my FreeBSD time, I
proposed to dig into upgrading our 1.4.2 codebase to 1.4.6.

Before I start duplicating work: is anyone else already working on this?

-- 
Jeroen Ruigrok van der Werven <asmodai(-at-)in-nomine.org> / asmodai
????? ?????? ??? ?? ??????
http://www.in-nomine.org/ | http://www.rangaku.org/ | GPG: 2EAC625B
Earth to earth, ashes to ashes, dust to dust...

From martin at v.loewis.de  Wed Feb 18 07:33:32 2009
From: martin at v.loewis.de (=?ISO-8859-1?Q?=22Martin_v=2E_L=F6wis=22?=)
Date: Wed, 18 Feb 2009 07:33:32 +0100
Subject: [Tracker-discuss] [issue235] incorrent To: headers in mail sent
 from tracker upon error processing email
In-Reply-To: <1234933907.44.0.734315958943.issue235@psf.upfronthosting.co.za>
References: <1234933907.44.0.734315958943.issue235@psf.upfronthosting.co.za>
Message-ID: <499BABBC.5040507@v.loewis.de>

> I tried to reply to an issue via email to add a note.  That failed.  But more
> interesting is that:

Do you still have the message that caused the failure? The reply said
that I should have received an error message, but I can't find that.

From metatracker at psf.upfronthosting.co.za  Wed Feb 18 07:33:39 2009
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v._L=C3=B6wis?=)
Date: Wed, 18 Feb 2009 06:33:39 +0000
Subject: [Tracker-discuss] [issue235] incorrent To: headers in mail sent
	from tracker upon error processing email
In-Reply-To: <1234933907.44.0.734315958943.issue235@psf.upfronthosting.co.za>
Message-ID: <499BABBC.5040507@v.loewis.de>


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

> I tried to reply to an issue via email to add a note.  That failed.  But more
> interesting is that:

Do you still have the message that caused the failure? The reply said
that I should have received an error message, but I can't find that.

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

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

From brett at python.org  Wed Feb 18 07:52:59 2009
From: brett at python.org (Brett Cannon)
Date: Tue, 17 Feb 2009 22:52:59 -0800
Subject: [Tracker-discuss] Updating to Roundup 1.4.6
In-Reply-To: <20090218061419.GK91939@nexus.in-nomine.org>
References: <20090218061419.GK91939@nexus.in-nomine.org>
Message-ID: <bbaeab100902172252p1c1603c9x7409d468d1114f60@mail.gmail.com>

On Tue, Feb 17, 2009 at 22:14, Jeroen Ruigrok van der Werven <
asmodai at in-nomine.org> wrote:

> I was talking in private with Daniel about the tracker and getting the
> desired features and such implemented. I noticed we are currently on 1.4.2
> of the official Roundup tree with additional custom changes. Since I've
> done
> quite a bit of merging in newer releases from a vendor in my FreeBSD time,
> I
> proposed to dig into upgrading our 1.4.2 codebase to 1.4.6.
>
> Before I start duplicating work: is anyone else already working on this?
>

Not that has told this list unless Martin has been planning this quietly.

-Brett
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/tracker-discuss/attachments/20090217/27963c3f/attachment.htm>

From martin at v.loewis.de  Wed Feb 18 07:58:06 2009
From: martin at v.loewis.de (=?UTF-8?B?Ik1hcnRpbiB2LiBMw7Z3aXMi?=)
Date: Wed, 18 Feb 2009 07:58:06 +0100
Subject: [Tracker-discuss] Updating to Roundup 1.4.6
In-Reply-To: <bbaeab100902172252p1c1603c9x7409d468d1114f60@mail.gmail.com>
References: <20090218061419.GK91939@nexus.in-nomine.org>
	<bbaeab100902172252p1c1603c9x7409d468d1114f60@mail.gmail.com>
Message-ID: <499BB17E.9030803@v.loewis.de>

> Not that has told this list unless Martin has been planning this
> quietly.

Not at all.

Martin

From metatracker at psf.upfronthosting.co.za  Wed Feb 18 08:20:16 2009
From: metatracker at psf.upfronthosting.co.za (Gregory P Smith)
Date: Wed, 18 Feb 2009 07:20:16 +0000
Subject: [Tracker-discuss] [issue235] incorrent To: headers in mail sent
	from tracker upon error processing email
In-Reply-To: <1234933907.44.0.734315958943.issue235@psf.upfronthosting.co.za>
Message-ID: <1234941616.78.0.531652671754.issue235@psf.upfronthosting.co.za>


Gregory P Smith <greg at krypto.org> added the comment:

heres the message in its entirety (i've since cut and pasted my response into
the issue via the web interface).

                                                                               
                                                                               
                                                                               
               
Delivered-To: greg at krypto.org
Received: by 10.103.118.18 with SMTP id v18cs239649mum;
        Tue, 17 Feb 2009 19:32:16 -0800 (PST)
Received: by 10.181.61.7 with SMTP id o7mr2623482bkk.51.1234927936727;
        Tue, 17 Feb 2009 19:32:16 -0800 (PST)
Return-Path: <roundup-admin at psf.upfronthosting.co.za>
Received: from psf.upfronthosting.co.za (bugs.python.org [88.198.142.26])
        by mx.google.com with ESMTP id 19si6367756bwz.83.2009.02.17.19.32.15;
        Tue, 17 Feb 2009 19:32:16 -0800 (PST)
Received-SPF: neutral (google.com: 88.198.142.26 is neither permitted nor denied
by best guess record for domain of roundup-admin at psf.upfronthosting.co.za)
client-ip=88.198.142.26;
Authentication-Results: mx.google.com; spf=neutral (google.com: 88.198.142.26 is
neither permitted nor denied by best guess record for domain of
roundup-admin at psf.upfronthosting.co.za)
smtp.mail=roundup-admin at psf.upfronthosting.co.za
Received: from psf.upfronthosting.co.za (localhost [10.0.0.1])
	by psf.upfronthosting.co.za (Postfix) with ESMTP id 44F387863C
	for <greg at krypto.org>; Wed, 18 Feb 2009 04:32:15 +0100 (CET)
Content-Type: multipart/mixed;
    boundary="88.198.142.26.1006.25012.1234927935.280.1"
Subject: Failed issue tracker submission
To: g at psf.upfronthosting.co.za, r at psf.upfronthosting.co.za,
	e at psf.upfronthosting.co.za, g at psf.upfronthosting.co.za, "",
	k at psf.upfronthosting.co.za, r at psf.upfronthosting.co.za,
	y at psf.upfronthosting.co.za, p at psf.upfronthosting.co.za,
	t at psf.upfronthosting.co.za, o at psf.upfronthosting.co.za,
	"."@psf.upfronthosting.co.za, o at psf.upfronthosting.co.za,
	r at psf.upfronthosting.co.za, g at psf.upfronthosting.co.za
From: Python tracker <roundup-admin at psf.upfronthosting.co.za>
Date: Wed, 18 Feb 2009 03:32:15 +0000
X-Roundup-Name: Python tracker
X-Roundup-Loop: hello
X-Roundup-Version: 1.4.2
MIME-Version: 1.0
Message-Id: <20090218033215.44F387863C at psf.upfronthosting.co.za>


--88.198.142.26.1006.25012.1234927935.280.1
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


An unexpected error occurred during the processing
of your message. The tracker administrator is being
notified.

--88.198.142.26.1006.25012.1234927935.280.1
Content-Type: text/plain
Content-Disposition: attachment
Content-Description: Message you sent

Return-Path: <greg at krypto.org>
X-Original-To: report at bugs.python.org
Delivered-To: roundup+tracker at psf.upfronthosting.co.za
Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.158])
	by psf.upfronthosting.co.za (Postfix) with ESMTP id 2324078590
	for <report at bugs.python.org>; Wed, 18 Feb 2009 04:32:10 +0100 (CET)
Received: by fg-out-1718.google.com with SMTP id 13so580429fge.20
        for <report at bugs.python.org>; Tue, 17 Feb 2009 19:32:10 -0800 (PST)
MIME-Version: 1.0
Received: by 10.103.5.14 with SMTP id h14mr4199439mui.108.1234927929576; Tue, 
	17 Feb 2009 19:32:09 -0800 (PST)
In-Reply-To: <1234911749.63.0.657212726256.issue4258 at psf.upfronthosting.co.za>
References: <1225795512.12.0.546973896448.issue4258 at psf.upfronthosting.co.za>
	 <1234911749.63.0.657212726256.issue4258 at psf.upfronthosting.co.za>
Date: Tue, 17 Feb 2009 19:32:09 -0800
Message-ID: <52dc1c820902171932p4441cbdfqc6a15a380b8a2d37 at mail.gmail.com>
Subject: Re: [issue4258] Use 30-bit digits instead of 15-bit digits for Python 
	integers.
From: "Gregory P. Smith" <greg at krypto.org>
To: Python tracker <report at bugs.python.org>
Content-Type: multipart/alternative; boundary=0016e649d9a290ce81046329101e

--0016e649d9a290ce81046329101e
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

> => I would suggest to use 2^30 base only if sizeof(long)>=8 (64 bits
CPU).
Thats not the correct test.  Test for an actual 64-bit build target.
 sizeof(long) and sizeof(long long) are not usefully related to that in any
sort of cross platform manner.  On windows, we'd define the flag for 15 vs
30 bit longs in the build configs for the various build targets.  On every
thing else (autoconf), we can use a configure test to check the same things
that platform.architecture() checks to return '32bit' vs '64bit'.

--0016e649d9a290ce81046329101e
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

&gt;&nbsp;<span class=3D"Apple-style-span" style=3D"border-collapse: collap=
se; ">=3D&gt; I would suggest to use 2^30 base only if sizeof(long)&gt;=3D8=
 (64 bits<br>CPU).</span><div><span class=3D"Apple-style-span" style=3D"bor=
der-collapse: collapse;"><br>
</span></div><div><span class=3D"Apple-style-span" style=3D"border-collapse=
: collapse;">Thats not the correct test. &nbsp;Test for an actual 64-bit bu=
ild target. &nbsp;sizeof(long) and sizeof(long long) are not usefully relat=
ed to that in any sort of cross platform manner. &nbsp;On windows, we&#39;d=
 define the flag for 15 vs 30 bit longs in the build configs for the variou=
s build targets. &nbsp;On every thing else (autoconf), we can use a configu=
re test to check the same things that platform.architecture() checks to ret=
urn &#39;32bit&#39; vs &#39;64bit&#39;.</span></div>
<div><br></div>

--0016e649d9a290ce81046329101e--

--88.198.142.26.1006.25012.1234927935.280.1--

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

From ajaksu at gmail.com  Wed Feb 18 23:34:14 2009
From: ajaksu at gmail.com (Daniel (ajax) Diniz)
Date: Wed, 18 Feb 2009 19:34:14 -0300
Subject: [Tracker-discuss] [Python-Dev] Tracker cleanup roadmap
In-Reply-To: <a3b05e8b0902180040w255cafe9l7ff9f9ca342553e1@mail.gmail.com>
References: <2d75d7660902161920g61c83d5btdcaf831ee6b04fa@mail.gmail.com>
	<499A721E.4060007@v.loewis.de>
	<a3b05e8b0902180040w255cafe9l7ff9f9ca342553e1@mail.gmail.com>
Message-ID: <2d75d7660902181434u6dba8378tc3f693678b9ca6ff@mail.gmail.com>

Hi Venkatraman,

Venkatraman S wrote:
>
> On Tue, Feb 17, 2009 at 1:45 PM, "Martin v. L?wis" <martin at v.loewis.de> wrote:
>>
>> Don't expect too much
>> help from other people - I have been waiting for volunteers to show up
>> helping with the tracker for more than a year now.
>
> I have been mostly a silent spectator around and would like to chip in.

Great! Thanks for joining us :)
What would you like to help with? Anyway, let's move this thread to
tracker-discuss :)

> Need some initial throttle(help) for the full-fledged attack :)

Well, I'm currently updating the TrackerDevelopment[1] article and
trying to make the initial setup easier. These should help a bit, but
I'd be glad to (try to) answer any questions you have. Please let me
know (or mail tracker-discuss[2]) if something on the guide isn't
clear (you can, of course, edit it directly).

"Martin v. L?wis" wrote:
> Please take a look at the meta tracker. It has various open issues, many
> open for many months now. Please tackle one that can be fixed through
> patches to the tracker instance preferably; changes to roundup are also
> acceptable in principle.

Agreed, if you want to get to know the code and at the same time work
on something useful, taking a look at the meta tracker[3] is a great
first step.

Welcome aboard!

Daniel

[1] http://wiki.python.org/moin/TrackerDevelopment
[2] http://mail.python.org/mailman/listinfo/tracker-discuss
[3] http://psf.upfronthosting.co.za/roundup/meta/ :)

From seefeld at sympatico.ca  Wed Feb 18 23:57:25 2009
From: seefeld at sympatico.ca (Stefan Seefeld)
Date: Wed, 18 Feb 2009 17:57:25 -0500
Subject: [Tracker-discuss] [Python-Dev] Tracker cleanup roadmap
In-Reply-To: <2d75d7660902181434u6dba8378tc3f693678b9ca6ff@mail.gmail.com>
References: <2d75d7660902161920g61c83d5btdcaf831ee6b04fa@mail.gmail.com>	<499A721E.4060007@v.loewis.de>	<a3b05e8b0902180040w255cafe9l7ff9f9ca342553e1@mail.gmail.com>
	<2d75d7660902181434u6dba8378tc3f693678b9ca6ff@mail.gmail.com>
Message-ID: <499C9255.3030309@sympatico.ca>

Hi there,

this is just a little note / reminder to try to submit Roundup patches 
and enhancements that you may have accumulated while working on the 
bugs.python.org tracker.
A couple of weeks ago I moved the Roundup project's own tracker close to 
where bugs.python.org is hosted, and am now actively developing Roundup 
again (at least for a while). So this is a good time to get in touch to 
merge things upstream. :-)

(See http://www.roundup-tracker.org.)

Thanks,
       Stefan

-- 

      ...ich hab' noch einen Koffer in Berlin...


From ajaksu at gmail.com  Thu Feb 19 00:46:48 2009
From: ajaksu at gmail.com (Daniel (ajax) Diniz)
Date: Wed, 18 Feb 2009 20:46:48 -0300
Subject: [Tracker-discuss] [Python-Dev] Tracker cleanup roadmap
In-Reply-To: <499C9255.3030309@sympatico.ca>
References: <2d75d7660902161920g61c83d5btdcaf831ee6b04fa@mail.gmail.com>
	<499A721E.4060007@v.loewis.de>
	<a3b05e8b0902180040w255cafe9l7ff9f9ca342553e1@mail.gmail.com>
	<2d75d7660902181434u6dba8378tc3f693678b9ca6ff@mail.gmail.com>
	<499C9255.3030309@sympatico.ca>
Message-ID: <2d75d7660902181546n52e440bfn4b8f238f2ee0e3c0@mail.gmail.com>

Hi  Stefan,

Stefan Seefeld wrote:
> Hi there,
>
> this is just a little note / reminder to try to submit Roundup patches and enhancements that you may have accumulated while working on the bugs.python.org tracker.
> A couple of weeks ago I moved the Roundup project's own tracker close to where bugs.python.org is hosted, and am now actively developing Roundup again (at least for a while). So this is a good time to get in touch to merge things upstream. :-)

Cool, I saw your recent checkins :)

I won't be touching Roundup code for a while. I have yet to take a
look at where/how we diverge and Jeroen is working on updating the
python-dev instance.

I have spotted some issues in your tracker I'd like to fix a bit later
on, like scope of AND searches (per message x per issue). Some planned
features also have to be implemented in Roundup land, like boolean
relations for query terms ('find' in indexer_[xapian|rdbms].py IIRC).

FWIW, I've linked to Roundup docs and issue tracker from our
TrackerDevelopment article.

Cheers,
Daniel

From ajaksu at gmail.com  Thu Feb 19 13:02:29 2009
From: ajaksu at gmail.com (Daniel (ajax) Diniz)
Date: Thu, 19 Feb 2009 09:02:29 -0300
Subject: [Tracker-discuss] Making the local instance easier to install
Message-ID: <2d75d7660902190402w59f50e0di453ad021ec972945@mail.gmail.com>

Hi,

I'm working on a couple of issues/patches that focus on getting a
local instance up and running.

The TrackerDevelopment article was a bit stale, so I've updated it to
include some caveats and tips, that boil down to (* marks a patch to
be submitted to the meta tracker):

[from a message to Jeroen]
1 - postgresql 8.3 won't work unless patched (looks like it's working,
only to break e.g. adding new issues), 8.2 works fine. A simple patch
makes 8.3 work: http://issues.roundup-tracker.org/issue2030479 (won't
submit this as it's present in Roundup 1.4.6).

2 - Installing psycopg2 from my package manager didn't work, from source
works nicely.

3 - SpamBayes can be another problem if you already use it (or doesn't
want to), this one I have yet to sort out. A local copy runs fine.

[new]
4* - The CIA.vc detector will embarrassingly post your test issues to
http://cia.vc/stats/project/python

5* - There are new values for a couple of fields, like Priority and Stages.

6* - SpamBayes dummy config should allow empty string/missing spambayes_uri.

7 - detectors/audit2to3.py isn't present anymore, but the general suggestion
about disabling detectors is still useful.

8 - Added links for Roundup docs and issue tracker.

I think we should discuss a workflow, will post a message on this
(with a couple of suggested features/bugs/RFCs ) soon :)

Cheers,
Daniel

From metatracker at psf.upfronthosting.co.za  Thu Feb 19 13:03:27 2009
From: metatracker at psf.upfronthosting.co.za (Daniel Diniz)
Date: Thu, 19 Feb 2009 12:03:27 +0000
Subject: [Tracker-discuss] [issue236] Disable CIA.vc detector by default
In-Reply-To: <1235045007.64.0.745186267851.issue236@psf.upfronthosting.co.za>
Message-ID: <1235045007.64.0.745186267851.issue236@psf.upfronthosting.co.za>


New submission from Daniel Diniz <ajaksu at gmail.com>:

The CIA.vc detector in local instances will send mail to Python's page there,
which gets embarrassing quickly: http://cia.vc/stats/author/ajaksu :D

----------
files: cia.diff
messages: 1144
nosy: ajaksu2
priority: bug
status: unread
title: Disable CIA.vc detector by default

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue236>
_______________________________________________________
-------------- next part --------------
A non-text attachment was scrubbed...
Name: cia.diff
Type: text/x-diff
Size: 302 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/tracker-discuss/attachments/20090219/2aa10219/attachment.diff>

From metatracker at psf.upfronthosting.co.za  Thu Feb 19 13:03:41 2009
From: metatracker at psf.upfronthosting.co.za (Daniel Diniz)
Date: Thu, 19 Feb 2009 12:03:41 +0000
Subject: [Tracker-discuss] [issue237] Make SpamBayes' dummy config more
	tolerant
In-Reply-To: <1235045021.33.0.00810434635886.issue237@psf.upfronthosting.co.za>
Message-ID: <1235045021.33.0.00810434635886.issue237@psf.upfronthosting.co.za>


New submission from Daniel Diniz <ajaksu at gmail.com>:

This patch, from a post by Skip Montanaro[1], allows not declaring or setting
spambayes_uri value to an empty string, adding two try:except for handling these.

[1] http://mail.python.org/pipermail/tracker-discuss/2008-February/001549.html

----------
files: spambayes_uri.diff
messages: 1145
nosy: ajaksu2
priority: wish
status: unread
title: Make SpamBayes' dummy config more tolerant

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue237>
_______________________________________________________
-------------- next part --------------
A non-text attachment was scrubbed...
Name: spambayes_uri.diff
Type: text/x-diff
Size: 823 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/tracker-discuss/attachments/20090219/a696c0d1/attachment.diff>

From metatracker at psf.upfronthosting.co.za  Thu Feb 19 13:04:23 2009
From: metatracker at psf.upfronthosting.co.za (Daniel Diniz)
Date: Thu, 19 Feb 2009 12:04:23 +0000
Subject: [Tracker-discuss] [issue238] Update 'initial_data.py' to match
	current values
In-Reply-To: <1235045063.45.0.472608826025.issue238@psf.upfronthosting.co.za>
Message-ID: <1235045063.45.0.472608826025.issue238@psf.upfronthosting.co.za>


New submission from Daniel Diniz <ajaksu at gmail.com>:

This patch makes a local instance values for fields match those of
bugs.python.org. Maybe making the IDs match would be good, if so I'd need to see
the retired values in the official tracker. 

I could also work on a script to update initial_data.py on demand (or
automatically on Class edit?).

----------
files: initial_data.diff
messages: 1146
nosy: ajaksu2
priority: wish
status: unread
title: Update 'initial_data.py' to match current values

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue238>
_______________________________________________________
-------------- next part --------------
A non-text attachment was scrubbed...
Name: initial_data.diff
Type: text/x-diff
Size: 6160 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/tracker-discuss/attachments/20090219/0c6ca2ad/attachment.diff>

From metatracker at psf.upfronthosting.co.za  Thu Feb 19 13:04:36 2009
From: metatracker at psf.upfronthosting.co.za (Daniel Diniz)
Date: Thu, 19 Feb 2009 12:04:36 +0000
Subject: [Tracker-discuss] [issue180] Add creator/assignee to search view
In-Reply-To: <1200938043.26.0.777887020922.issue180@psf.upfronthosting.co.za>
Message-ID: <1235045076.68.0.386052488443.issue180@psf.upfronthosting.co.za>


Daniel Diniz <ajaksu at gmail.com> added the comment:

The results of a quick search now include both creator and assignee. I'll add
'type' to it and to the default view.

----------
assignedto:  -> ajaksu2
nosy: +ajaksu2
status: unread -> chatting

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

From metatracker at psf.upfronthosting.co.za  Thu Feb 19 13:19:24 2009
From: metatracker at psf.upfronthosting.co.za (Daniel Diniz)
Date: Thu, 19 Feb 2009 12:19:24 +0000
Subject: [Tracker-discuss] [issue180] Add creator/assignee to search view
In-Reply-To: <1200938043.26.0.777887020922.issue180@psf.upfronthosting.co.za>
Message-ID: <1235045964.86.0.492398120281.issue180@psf.upfronthosting.co.za>


Daniel Diniz <ajaksu at gmail.com> added the comment:

Here's the patch.

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue180>
_______________________________________________________
-------------- next part --------------
A non-text attachment was scrubbed...
Name: display_type.diff
Type: text/x-diff
Size: 999 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/tracker-discuss/attachments/20090219/c29b5cc7/attachment.diff>

From ajaksu at gmail.com  Thu Feb 19 14:27:19 2009
From: ajaksu at gmail.com (Daniel (ajax) Diniz)
Date: Thu, 19 Feb 2009 10:27:19 -0300
Subject: [Tracker-discuss] Tracker hacking workflow
Message-ID: <2d75d7660902190527m6d2d1b57v149cb5c89f4d77b3@mail.gmail.com>

Hi,
I'd like to chat about the tracker hacking effort a little, so we can
work together more efficiently. Knowing how/what people want to
contribute allows us to think about what can be done to make it
easier. I'll throw a few ideas to get things started, but feel free to
discuss anything else :)

Right now, I'm working just like I work on Python issues: small
patches (that may be incompatible with each other) sent to the (meta)
tracker. Maybe using a public DVCS repository (e.g. at Bitbucket)
would make sharing our modifications (before SVN commits) easier. What
do you think?

The same 'public repository' approach can be useful for discussing
goals, using the Python wiki or something similar. When fleshed out
enough, goals/task should become tickets in the meta tracker, IMO.
Does this work for everybody?

I'm planning to create a public python-dev instance for testing: that
way, we could get useful feedback from people that don't have a local
instance running (or are too busy to patch and test). Maybe a buildbot
could be set just for restarting the server after commits. Would that
be interesting? Martin, would you prefer another setup?

Cheers,
Daniel

From metatracker at psf.upfronthosting.co.za  Thu Feb 19 14:45:10 2009
From: metatracker at psf.upfronthosting.co.za (Daniel Diniz)
Date: Thu, 19 Feb 2009 13:45:10 +0000
Subject: [Tracker-discuss] [issue239] Add 'Stage' to search page
In-Reply-To: <1235051110.26.0.105167036009.issue239@psf.upfronthosting.co.za>
Message-ID: <1235051110.26.0.105167036009.issue239@psf.upfronthosting.co.za>


New submission from Daniel Diniz <ajaksu at gmail.com>:

This patch makes searching for, sorting or grouping by Stage possible.

----------
files: stage_search.diff
messages: 1149
nosy: ajaksu2
priority: feature
status: unread
title: Add 'Stage' to search page

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue239>
_______________________________________________________
-------------- next part --------------
A non-text attachment was scrubbed...
Name: stage_search.diff
Type: text/x-diff
Size: 879 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/tracker-discuss/attachments/20090219/8889cee1/attachment.diff>

From metatracker at psf.upfronthosting.co.za  Thu Feb 19 15:04:36 2009
From: metatracker at psf.upfronthosting.co.za (Daniel Diniz)
Date: Thu, 19 Feb 2009 14:04:36 +0000
Subject: [Tracker-discuss] [issue240] Fix 'not closed' search
In-Reply-To: <1235052276.47.0.658195032076.issue240@psf.upfronthosting.co.za>
Message-ID: <1235052276.47.0.658195032076.issue240@psf.upfronthosting.co.za>


New submission from Daniel Diniz <ajaksu at gmail.com>:

The search by status for 'not closed' currently searches for 'closed' + 'not
set' + 'open' instead of pending' + 'not set' + 'open'. Fix attached.

----------
files: notclosed_search.diff
messages: 1150
nosy: ajaksu2
priority: bug
status: unread
title: Fix 'not closed' search

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue240>
_______________________________________________________
-------------- next part --------------
A non-text attachment was scrubbed...
Name: notclosed_search.diff
Type: text/x-diff
Size: 756 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/tracker-discuss/attachments/20090219/2c48affc/attachment.diff>

From metatracker at psf.upfronthosting.co.za  Thu Feb 19 15:14:47 2009
From: metatracker at psf.upfronthosting.co.za (Daniel Diniz)
Date: Thu, 19 Feb 2009 14:14:47 +0000
Subject: [Tracker-discuss] [issue125] typing (just) a tracker ID in the
	search box should go to that issue
In-Reply-To: <1235052887.09.0.640250052467.issue125@psf.upfronthosting.co.za>
Message-ID: <1235052887.09.0.640250052467.issue125@psf.upfronthosting.co.za>


New submission from Daniel Diniz <ajaksu at gmail.com>:

Closing as issue 123 has advanced more.

----------
nosy: +ajaksu2
status: unread -> resolved

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

From metatracker at psf.upfronthosting.co.za  Thu Feb 19 15:20:56 2009
From: metatracker at psf.upfronthosting.co.za (Daniel Diniz)
Date: Thu, 19 Feb 2009 14:20:56 +0000
Subject: [Tracker-discuss] [issue219] Please add link to security tracker
	from main tracker page
In-Reply-To: <1221661962.49.0.99429423588.issue219@psf.upfronthosting.co.za>
Message-ID: <1235053256.4.0.797608188603.issue219@psf.upfronthosting.co.za>


Daniel Diniz <ajaksu at gmail.com> added the comment:

Is this a won't fix or should I work on a patch?

----------
nosy: +ajaksu2

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

From metatracker at psf.upfronthosting.co.za  Thu Feb 19 16:18:45 2009
From: metatracker at psf.upfronthosting.co.za (Daniel Diniz)
Date: Thu, 19 Feb 2009 15:18:45 +0000
Subject: [Tracker-discuss] [issue207] Denote which dependencies issues have
	been closed
In-Reply-To: <1211141168.1.0.612084028465.issue207@psf.upfronthosting.co.za>
Message-ID: <1235056725.61.0.297318356205.issue207@psf.upfronthosting.co.za>


Daniel Diniz <ajaksu at gmail.com> added the comment:

Here's a patch, the template part is OK-ish but the CSS could use some tweaking.

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

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue207>
_______________________________________________________
-------------- next part --------------
A non-text attachment was scrubbed...
Name: closed_dependency.diff
Type: text/x-diff
Size: 1334 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/tracker-discuss/attachments/20090219/ebc7ec11/attachment-0001.diff>

From metatracker at psf.upfronthosting.co.za  Thu Feb 19 16:49:52 2009
From: metatracker at psf.upfronthosting.co.za (Daniel Diniz)
Date: Thu, 19 Feb 2009 15:49:52 +0000
Subject: [Tracker-discuss] [issue189] Tracker Weekly Summary: 'Closed by'
	sometimes incorrect
In-Reply-To: <1203177616.06.0.45592637075.issue189@psf.upfronthosting.co.za>
Message-ID: <1235058592.48.0.25590481497.issue189@psf.upfronthosting.co.za>


Daniel Diniz <ajaksu at gmail.com> added the comment:

This one could be fixed by using db.history/db.getjournal and retrieving the
last entry containing change to 'closed'. Or _issue could grow a _closedby column. 

IMHO, either would be too much trouble for a pretty unimportant issue.

----------
assignedto: dubois -> 
nosy: +ajaksu2 -dubois
status: unread -> chatting

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

From metatracker at psf.upfronthosting.co.za  Thu Feb 19 17:12:12 2009
From: metatracker at psf.upfronthosting.co.za (Daniel Diniz)
Date: Thu, 19 Feb 2009 16:12:12 +0000
Subject: [Tracker-discuss] [issue172] Traceback exposed in misformed URL
In-Reply-To: <1196951026.1.0.157520960574.issue172@psf.upfronthosting.co.za>
Message-ID: <1235059932.34.0.316180084708.issue172@psf.upfronthosting.co.za>


Daniel Diniz <ajaksu at gmail.com> added the comment:

Oh, well, I didn't want to patch roundup-src just yet but I don't like this one.
Patch catches KeyError, returns None and handles that downstream.

----------
nosy: +ajaksu2

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue172>
_______________________________________________________
-------------- next part --------------
A non-text attachment was scrubbed...
Name: misformed_traceback.diff
Type: text/x-diff
Size: 1002 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/tracker-discuss/attachments/20090219/dcf44c67/attachment.diff>

From metatracker at psf.upfronthosting.co.za  Thu Feb 19 17:34:22 2009
From: metatracker at psf.upfronthosting.co.za (Daniel Diniz)
Date: Thu, 19 Feb 2009 16:34:22 +0000
Subject: [Tracker-discuss] [issue224] "Search in All Issues" button
In-Reply-To: <1223897016.78.0.0580124380517.issue224@psf.upfronthosting.co.za>
Message-ID: <1235061262.44.0.834275778053.issue224@psf.upfronthosting.co.za>


Daniel Diniz <ajaksu at gmail.com> added the comment:

I really would like to have a "Search in All Issues" button. Having it as a tiny
search box under the "Show issue:" one would be enough. 

I like the idea of having the second search form in the attached file show for
user logged in, while anonymous users would see the first one.

----------
nosy: +ajaksu2

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue224>
_______________________________________________________
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/tracker-discuss/attachments/20090219/0ce844ab/attachment.html>

From metatracker at psf.upfronthosting.co.za  Thu Feb 19 18:09:38 2009
From: metatracker at psf.upfronthosting.co.za (Daniel Diniz)
Date: Thu, 19 Feb 2009 17:09:38 +0000
Subject: [Tracker-discuss] [issue202] Edit Queries screen should include a
	link to the search page
In-Reply-To: <1207668185.49.0.108699616732.issue202@psf.upfronthosting.co.za>
Message-ID: <1235063378.23.0.0733433997825.issue202@psf.upfronthosting.co.za>


Daniel Diniz <ajaksu at gmail.com> added the comment:

Instead of a link, the patch adds a text input and 'Add' button.

When a user supplies a name, the search page will open with the selected name in
"Query name" and a helpful message telling her to click "Search" to save a new
query.

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

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue202>
_______________________________________________________
-------------- next part --------------
A non-text attachment was scrubbed...
Name: edit_query_add_new.diff
Type: text/x-diff
Size: 636 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/tracker-discuss/attachments/20090219/a85035dc/attachment.diff>

From metatracker at psf.upfronthosting.co.za  Thu Feb 19 18:58:23 2009
From: metatracker at psf.upfronthosting.co.za (Daniel Diniz)
Date: Thu, 19 Feb 2009 17:58:23 +0000
Subject: [Tracker-discuss] [issue165] Preventing 'Broken Pipe' and similar
	exceptions
In-Reply-To: <1193056360.43.0.794459675532.issue165@psf.upfronthosting.co.za>
Message-ID: <1235066303.15.0.944103769513.issue165@psf.upfronthosting.co.za>


Daniel Diniz <ajaksu at gmail.com> added the comment:

Is this still an issue?

----------
nosy: +ajaksu2

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

From metatracker at psf.upfronthosting.co.za  Thu Feb 19 19:10:00 2009
From: metatracker at psf.upfronthosting.co.za (Daniel Diniz)
Date: Thu, 19 Feb 2009 18:10:00 +0000
Subject: [Tracker-discuss] [issue167] Added resolution keyword "confirmed"
In-Reply-To: <1194626858.37.0.770894714995.issue167@psf.upfronthosting.co.za>
Message-ID: <1235067000.8.0.620933095711.issue167@psf.upfronthosting.co.za>


Daniel Diniz <ajaksu at gmail.com> added the comment:

Now we have Stages, "confirmation needed" might be an easier way to flag any
unconfirmed bugs (and suggest people try reproducing the issue).

That would allow two paths to 'test needed':
good bug report -> 'test needed'
poor bug report -> 'confirmation needed' -> 'test needed'

That would avoid the (immediate) need to change the default view.

----------
nosy: +ajaksu2

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

From metatracker at psf.upfronthosting.co.za  Thu Feb 19 19:28:30 2009
From: metatracker at psf.upfronthosting.co.za (Daniel Diniz)
Date: Thu, 19 Feb 2009 18:28:30 +0000
Subject: [Tracker-discuss] [issue87] add # of comments to default issue list
In-Reply-To: <1173534188.93.0.690515473058.issue87@psf.upfronthosting.co.za>
Message-ID: <1235068110.55.0.386499538174.issue87@psf.upfronthosting.co.za>


Daniel Diniz <ajaksu at gmail.com> added the comment:

I think the '''"number of comments" or "number of distinct commenters" fields,
which you then can also add into the index''' idea is the way to go. 

New comments or deletions can increase/decrease those fields, which should be
pre-populated by a run-once script that counts current messages/commenters.

Is this still a wanted feature?

----------
nosy: +ajaksu2

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

From martin at v.loewis.de  Thu Feb 19 19:47:03 2009
From: martin at v.loewis.de (=?ISO-8859-1?Q?=22Martin_v=2E_L=F6wis=22?=)
Date: Thu, 19 Feb 2009 19:47:03 +0100
Subject: [Tracker-discuss] Making the local instance easier to install
In-Reply-To: <2d75d7660902190402w59f50e0di453ad021ec972945@mail.gmail.com>
References: <2d75d7660902190402w59f50e0di453ad021ec972945@mail.gmail.com>
Message-ID: <499DA927.3030509@v.loewis.de>

> 3 - SpamBayes can be another problem if you already use it (or doesn't
> want to), this one I have yet to sort out. A local copy runs fine.

It should be possible to disable it, in detectors/config.ini

> [new]
> 4* - The CIA.vc detector will embarrassingly post your test issues to
> http://cia.vc/stats/project/python

We should add code to that detector so that it reads some config.ini
as well, so you can disable cia if you want to. It probably should be
off by default.

Regards,
Martin

From metatracker at psf.upfronthosting.co.za  Thu Feb 19 19:48:58 2009
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v._L=C3=B6wis?=)
Date: Thu, 19 Feb 2009 18:48:58 +0000
Subject: [Tracker-discuss] [issue236] Disable CIA.vc detector by default
In-Reply-To: <1235045007.64.0.745186267851.issue236@psf.upfronthosting.co.za>
Message-ID: <1235069338.09.0.0507982293158.issue236@psf.upfronthosting.co.za>


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

The proposed patch is no solution. The live site must not have any local changes
to the code that is in subversion. Reading some configuration value from
config.ini would be fine.

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

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

From metatracker at psf.upfronthosting.co.za  Thu Feb 19 19:49:21 2009
From: metatracker at psf.upfronthosting.co.za (Georg Brandl)
Date: Thu, 19 Feb 2009 18:49:21 +0000
Subject: [Tracker-discuss] [issue87] add # of comments to default issue list
In-Reply-To: <1173534188.93.0.690515473058.issue87@psf.upfronthosting.co.za>
Message-ID: <1235069361.94.0.911990160208.issue87@psf.upfronthosting.co.za>


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

Yes!

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

From metatracker at psf.upfronthosting.co.za  Thu Feb 19 19:57:16 2009
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v._L=C3=B6wis?=)
Date: Thu, 19 Feb 2009 18:57:16 +0000
Subject: [Tracker-discuss] [issue238] Update 'initial_data.py' to match
	current values
In-Reply-To: <1235045063.45.0.472608826025.issue238@psf.upfronthosting.co.za>
Message-ID: <1235069836.43.0.860882556642.issue238@psf.upfronthosting.co.za>


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

It's easy to find out the missing ids; then go to the respective URLs, e.g.

http://bugs.python.org/stage1

to find out what the original issue was. Some psql results:

  1 | Python 2.6
  2 | Python 2.5
  3 | Python 2.4
  4 | Python 2.3
  5 | Python 2.2.3
  6 | Python 2.2.2
  7 | Python 2.2.1
  8 | Python 2.2
  9 | Python 2.1.2
 10 | Python 2.1.1
 11 | 3rd party
 12 | Python 3.0
 13 | Python 3.1
 14 | Python 2.7
 15 | Python 2.5.3

  1 | Build
  2 | Demos and Tools
  3 | Distutils
  4 | Documentation
  5 | Extension Modules
  6 | IDLE
  7 | Installation
  8 | Interpreter Core
  9 | Library (Lib)
 10 | Macintosh
 11 | Regular Expressions
 12 | Tests
 13 | Tkinter
 14 | Unicode
 15 | Windows
 16 | XML
 17 | None
 18 | Documentation tools (Sphinx)
 19 | 2to3 (2.x to 3.0 conversion tool)
 20 | 2to3 (2.x to 3.0 conversion tool)
 22 | ctypes

  1 | py3k
  2 | patch
  3 | r-eyyy-mond
  4 | rfe
  5 | 64bit
  6 | easy
  7 | 26backport
  8 | needs review

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

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

From martin at v.loewis.de  Thu Feb 19 20:04:19 2009
From: martin at v.loewis.de (=?ISO-8859-1?Q?=22Martin_v=2E_L=F6wis=22?=)
Date: Thu, 19 Feb 2009 20:04:19 +0100
Subject: [Tracker-discuss] Tracker hacking workflow
In-Reply-To: <2d75d7660902190527m6d2d1b57v149cb5c89f4d77b3@mail.gmail.com>
References: <2d75d7660902190527m6d2d1b57v149cb5c89f4d77b3@mail.gmail.com>
Message-ID: <499DAD33.2050305@v.loewis.de>

> Right now, I'm working just like I work on Python issues: small
> patches (that may be incompatible with each other) sent to the (meta)
> tracker. Maybe using a public DVCS repository (e.g. at Bitbucket)
> would make sharing our modifications (before SVN commits) easier. What
> do you think?

I'm not able to use DVCS software. Feel free to set something up, but
please continue to submit patches. The way your progress looks like,
I'm willing to grant svn write access shortly (assuming you want it).

> I'm planning to create a public python-dev instance for testing: that
> way, we could get useful feedback from people that don't have a local
> instance running (or are too busy to patch and test). Maybe a buildbot
> could be set just for restarting the server after commits. Would that
> be interesting? Martin, would you prefer another setup?

I think you are overestimating the amount of volunteers that you can
attract (although I would be happy to be proven wrong). For the moment,
I'm just assuming that is just us two.

Regards,
Martin

From asmodai at in-nomine.org  Thu Feb 19 20:07:19 2009
From: asmodai at in-nomine.org (Jeroen Ruigrok van der Werven)
Date: Thu, 19 Feb 2009 20:07:19 +0100
Subject: [Tracker-discuss] Tracker hacking workflow
In-Reply-To: <2d75d7660902190527m6d2d1b57v149cb5c89f4d77b3@mail.gmail.com>
References: <2d75d7660902190527m6d2d1b57v149cb5c89f4d77b3@mail.gmail.com>
Message-ID: <20090219190719.GO91939@nexus.in-nomine.org>

-On [20090219 14:27], Daniel (ajax) Diniz (ajaksu at gmail.com) wrote:
>Right now, I'm working just like I work on Python issues: small
>patches (that may be incompatible with each other) sent to the (meta)
>tracker. Maybe using a public DVCS repository (e.g. at Bitbucket)
>would make sharing our modifications (before SVN commits) easier. What
>do you think?

Right now patches might sound better until we really need to get cracking at
some major changes or so.

Right now I'm just focusing on getting local changes resolved with the 1.4.6
release.

-- 
Jeroen Ruigrok van der Werven <asmodai(-at-)in-nomine.org> / asmodai
????? ?????? ??? ?? ??????
http://www.in-nomine.org/ | http://www.rangaku.org/ | GPG: 2EAC625B
Earth to earth, ashes to ashes, dust to dust...

From metatracker at psf.upfronthosting.co.za  Thu Feb 19 20:10:19 2009
From: metatracker at psf.upfronthosting.co.za (Daniel Diniz)
Date: Thu, 19 Feb 2009 19:10:19 +0000
Subject: [Tracker-discuss] [issue236] Disable CIA.vc detector by default
In-Reply-To: <1235045007.64.0.745186267851.issue236@psf.upfronthosting.co.za>
Message-ID: <1235070619.51.0.226287098343.issue236@psf.upfronthosting.co.za>


Daniel Diniz <ajaksu at gmail.com> added the comment:

That makes sense :)

I think having 'TEMPLATE' and 'parameters' either in config.ini or separated
files would be neater. But not much real value would be added, so I'm not doing
it yet.

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue236>
_______________________________________________________
-------------- next part --------------
A non-text attachment was scrubbed...
Name: cia_config.diff
Type: text/x-diff
Size: 1427 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/tracker-discuss/attachments/20090219/82df8f32/attachment-0001.diff>

From metatracker at psf.upfronthosting.co.za  Thu Feb 19 20:12:10 2009
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v._L=C3=B6wis?=)
Date: Thu, 19 Feb 2009 19:12:10 +0000
Subject: [Tracker-discuss] [issue219] Please add link to security tracker
	from main tracker page
In-Reply-To: <1221661962.49.0.99429423588.issue219@psf.upfronthosting.co.za>
Message-ID: <1235070730.13.0.993806382638.issue219@psf.upfronthosting.co.za>


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

If Barry still wants it, we should do it.

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

From metatracker at psf.upfronthosting.co.za  Thu Feb 19 20:28:34 2009
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v._L=C3=B6wis?=)
Date: Thu, 19 Feb 2009 19:28:34 +0000
Subject: [Tracker-discuss] [issue165] Preventing 'Broken Pipe' and similar
	exceptions
In-Reply-To: <1193056360.43.0.794459675532.issue165@psf.upfronthosting.co.za>
Message-ID: <1235071714.52.0.971812445931.issue165@psf.upfronthosting.co.za>


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

No, I haven't seen any such messages in a long time (although I'm unsure whether
I'm getting roundup error messages at all).

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

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

From metatracker at psf.upfronthosting.co.za  Thu Feb 19 20:30:39 2009
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v._L=C3=B6wis?=)
Date: Thu, 19 Feb 2009 19:30:39 +0000
Subject: [Tracker-discuss] [issue167] Added resolution keyword "confirmed"
In-Reply-To: <1194626858.37.0.770894714995.issue167@psf.upfronthosting.co.za>
Message-ID: <1235071839.08.0.311259627219.issue167@psf.upfronthosting.co.za>


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

Brett, any opinion?

----------
assignedto:  -> brett.cannon
nosy: +brett.cannon, loewis

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

From metatracker at psf.upfronthosting.co.za  Thu Feb 19 20:31:34 2009
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v._L=C3=B6wis?=)
Date: Thu, 19 Feb 2009 19:31:34 +0000
Subject: [Tracker-discuss] [issue87] add # of comments to default issue list
In-Reply-To: <1235068110.55.0.386499538174.issue87@psf.upfronthosting.co.za>
Message-ID: <499DB394.4070203@v.loewis.de>


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

> Is this still a wanted feature?

I think so, yes.

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

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

From martin at v.loewis.de  Thu Feb 19 20:31:32 2009
From: martin at v.loewis.de (=?ISO-8859-1?Q?=22Martin_v=2E_L=F6wis=22?=)
Date: Thu, 19 Feb 2009 20:31:32 +0100
Subject: [Tracker-discuss] [issue87] add # of comments to default issue
 list
In-Reply-To: <1235068110.55.0.386499538174.issue87@psf.upfronthosting.co.za>
References: <1235068110.55.0.386499538174.issue87@psf.upfronthosting.co.za>
Message-ID: <499DB394.4070203@v.loewis.de>

> Is this still a wanted feature?

I think so, yes.

From metatracker at psf.upfronthosting.co.za  Thu Feb 19 20:39:25 2009
From: metatracker at psf.upfronthosting.co.za (Brett C.)
Date: Thu, 19 Feb 2009 19:39:25 +0000
Subject: [Tracker-discuss] [issue167] Added resolution keyword "confirmed"
In-Reply-To: <1194626858.37.0.770894714995.issue167@psf.upfronthosting.co.za>
Message-ID: <1235072365.97.0.177039406405.issue167@psf.upfronthosting.co.za>


Brett C. <brett at python.org> added the comment:

A stage before *test needed* makes sense. That way an unset Stage means that a
triage is needed and we now have a way for people to say "this is triaged in
terms of being categorized and such, but I don't know if the bug is valid".

Question is what to name it. Should it be "confirmation needed", "confirm",
"verify"? I would like a non-native English speaker to make the final call to
make sure it makes sense.

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

From metatracker at psf.upfronthosting.co.za  Thu Feb 19 20:41:52 2009
From: metatracker at psf.upfronthosting.co.za (Brett C.)
Date: Thu, 19 Feb 2009 19:41:52 +0000
Subject: [Tracker-discuss] [issue241] Rename *test needed* Stage to *unit
	test needed*
In-Reply-To: <1235072512.23.0.847427107108.issue241@psf.upfronthosting.co.za>
Message-ID: <1235072512.23.0.847427107108.issue241@psf.upfronthosting.co.za>


New submission from Brett C. <brett at python.org>:

Daniel pointed out that *test needed* is a little misleading. It would be better
to rename it to *unit test needed* to make it very clear what that stage represents.

I would make the change myself but I don't remember the magical URL to do it.

----------
messages: 1170
nosy: brett.cannon
priority: feature
status: unread
title: Rename *test needed* Stage to *unit test needed*

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

From ajaksu at gmail.com  Thu Feb 19 20:48:27 2009
From: ajaksu at gmail.com (Daniel (ajax) Diniz)
Date: Thu, 19 Feb 2009 16:48:27 -0300
Subject: [Tracker-discuss] Tracker hacking workflow
In-Reply-To: <499DAD33.2050305@v.loewis.de>
References: <2d75d7660902190527m6d2d1b57v149cb5c89f4d77b3@mail.gmail.com>
	<499DAD33.2050305@v.loewis.de>
Message-ID: <2d75d7660902191148g7817e2c1gf9e18133ab24a50@mail.gmail.com>

"Martin v. L?wis" wrote:
> I'm not able to use DVCS software. Feel free to set something up, but
> please continue to submit patches.

That would be the idea, but we're settling on patches for now.

> The way your progress looks like,
> I'm willing to grant svn write access shortly (assuming you want it).

I'd feel (current_fear_of_doing_something_stupid)**1000, so I'd rather
wait as long as necessary for someone to take a look at and/or commit
my patches, if that's not too inconvenient.

>> I'm planning to create a public python-dev instance for testing: that
>> way, we could get useful feedback from people that don't have a local
>> instance running (or are too busy to patch and test). Maybe a buildbot
>> could be set just for restarting the server after commits. Would that
>> be interesting? Martin, would you prefer another setup?
>
> I think you are overestimating the amount of volunteers that you can
> attract (although I would be happy to be proven wrong). For the moment,
> I'm just assuming that is just us two.

I think the 'coding and testing' team will always be small. I'm
counting three of us with Jeroen (who can help with commits). I'm
hopeful that Venkatraman will be able to help too. But that would not
be the testing instance's goal.

I can offer a patch to solve an issue in the meta tracker, but I don't
expect most ticket submitters to set a local instance just to see if I
got things right. I don't want bugs.python.org to be the testbed
either :)

So, short of working with screenshots (see attachment :D), I think the
easiest way to get feedback from the submitter is to offer a ride on a
patched instance. I have at least two patches I'd like feedback on
looks (CSS), one for marking closed dependencies and the screenshot
attached :)

When I go breaking database stuff to add new features on the Roundup
side of our tracker, I'd also like to have people
complaining/bikeshedding/outraged at a test instance before they start
doing so on the real tracker.

But this will take a little while to set up :)

Daniel
-------------- next part --------------
A non-text attachment was scrubbed...
Name: edit_queries_new.png
Type: image/png
Size: 9789 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/tracker-discuss/attachments/20090219/b35d8f20/attachment-0001.png>

From metatracker at psf.upfronthosting.co.za  Thu Feb 19 20:48:54 2009
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v._L=C3=B6wis?=)
Date: Thu, 19 Feb 2009 19:48:54 +0000
Subject: [Tracker-discuss] [issue167] Added resolution keyword "confirmed"
In-Reply-To: <1235072365.97.0.177039406405.issue167@psf.upfronthosting.co.za>
Message-ID: <499DB7A4.6030004@v.loewis.de>


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

> Question is what to name it. Should it be "confirmation needed", "confirm",
> "verify"? I would like a non-native English speaker to make the final call to
> make sure it makes sense.

How about "not yet verified"?

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

From martin at v.loewis.de  Thu Feb 19 20:48:52 2009
From: martin at v.loewis.de (=?ISO-8859-1?Q?=22Martin_v=2E_L=F6wis=22?=)
Date: Thu, 19 Feb 2009 20:48:52 +0100
Subject: [Tracker-discuss] [issue167] Added resolution keyword
	"confirmed"
In-Reply-To: <1235072365.97.0.177039406405.issue167@psf.upfronthosting.co.za>
References: <1235072365.97.0.177039406405.issue167@psf.upfronthosting.co.za>
Message-ID: <499DB7A4.6030004@v.loewis.de>

> Question is what to name it. Should it be "confirmation needed", "confirm",
> "verify"? I would like a non-native English speaker to make the final call to
> make sure it makes sense.

How about "not yet verified"?

From metatracker at psf.upfronthosting.co.za  Thu Feb 19 20:51:56 2009
From: metatracker at psf.upfronthosting.co.za (Brett C.)
Date: Thu, 19 Feb 2009 19:51:56 +0000
Subject: [Tracker-discuss] [issue167] Added resolution keyword "confirmed"
In-Reply-To: <499DB7A4.6030004@v.loewis.de>
Message-ID: <bbaeab100902191151u5292d56dq1fc12e2d4e2339db@mail.gmail.com>


Brett C. <brett at python.org> added the comment:

On Thu, Feb 19, 2009 at 11:48, Martin v. L?wis <
metatracker at psf.upfronthosting.co.za> wrote:

>
> Martin v. L?wis <martin at v.loewis.de> added the comment:
>
> > Question is what to name it. Should it be "confirmation needed",
> "confirm",
> > "verify"? I would like a non-native English speaker to make the final
> call to
> > make sure it makes sense.
>
> How about "not yet verified"?

Works for me!

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue167>
_______________________________________________________
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/tracker-discuss/attachments/20090219/26c002a2/attachment.htm>

From martin at v.loewis.de  Thu Feb 19 20:54:20 2009
From: martin at v.loewis.de (=?UTF-8?B?Ik1hcnRpbiB2LiBMw7Z3aXMi?=)
Date: Thu, 19 Feb 2009 20:54:20 +0100
Subject: [Tracker-discuss] Tracker hacking workflow
In-Reply-To: <2d75d7660902191148g7817e2c1gf9e18133ab24a50@mail.gmail.com>
References: <2d75d7660902190527m6d2d1b57v149cb5c89f4d77b3@mail.gmail.com>	
	<499DAD33.2050305@v.loewis.de>
	<2d75d7660902191148g7817e2c1gf9e18133ab24a50@mail.gmail.com>
Message-ID: <499DB8EC.8030003@v.loewis.de>

> I can offer a patch to solve an issue in the meta tracker, but I don't
> expect most ticket submitters to set a local instance just to see if I
> got things right. I don't want bugs.python.org to be the testbed
> either :)

It has been so far, and it worked quite well. So I don't worry too much
about breaking it - people will notice us fast enough.

> So, short of working with screenshots (see attachment :D), I think the
> easiest way to get feedback from the submitter is to offer a ride on a
> patched instance. I have at least two patches I'd like feedback on
> looks (CSS), one for marking closed dependencies and the screenshot
> attached :)

Don't get me wrong: if you want to set up a public test installation,
go ahead! All I'm saying is that I feel it's not necessary (I will
continue to test on my local installation, if I test at all).

We can also arrange to host a test installation on the upfronthosting
machine - although we'll have to restrict access to that machine to
very few people.

Martin

From metatracker at psf.upfronthosting.co.za  Thu Feb 19 20:59:32 2009
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v._L=C3=B6wis?=)
Date: Thu, 19 Feb 2009 19:59:32 +0000
Subject: [Tracker-discuss] [issue237] Make SpamBayes' dummy config more
	tolerant
In-Reply-To: <1235045021.33.0.00810434635886.issue237@psf.upfronthosting.co.za>
Message-ID: <1235073572.22.0.884699795743.issue237@psf.upfronthosting.co.za>


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

Thanks, committed as r69778

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

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

From metatracker at psf.upfronthosting.co.za  Thu Feb 19 21:02:20 2009
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v._L=C3=B6wis?=)
Date: Thu, 19 Feb 2009 20:02:20 +0000
Subject: [Tracker-discuss] [issue180] Add creator/assignee to search view
In-Reply-To: <1200938043.26.0.777887020922.issue180@psf.upfronthosting.co.za>
Message-ID: <1235073740.35.0.342587444058.issue180@psf.upfronthosting.co.za>


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

Thanks, committed as r69779

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

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

From metatracker at psf.upfronthosting.co.za  Thu Feb 19 21:04:06 2009
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v._L=C3=B6wis?=)
Date: Thu, 19 Feb 2009 20:04:06 +0000
Subject: [Tracker-discuss] [issue239] Add 'Stage' to search page
In-Reply-To: <1235051110.26.0.105167036009.issue239@psf.upfronthosting.co.za>
Message-ID: <1235073846.83.0.522069594383.issue239@psf.upfronthosting.co.za>


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

Thanks, committed as r69780

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

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

From metatracker at psf.upfronthosting.co.za  Thu Feb 19 21:06:16 2009
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v._L=C3=B6wis?=)
Date: Thu, 19 Feb 2009 20:06:16 +0000
Subject: [Tracker-discuss] [issue240] Fix 'not closed' search
In-Reply-To: <1235052276.47.0.658195032076.issue240@psf.upfronthosting.co.za>
Message-ID: <1235073976.3.0.308183304399.issue240@psf.upfronthosting.co.za>


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

Thanks, committed as r69781

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

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

From metatracker at psf.upfronthosting.co.za  Thu Feb 19 21:11:40 2009
From: metatracker at psf.upfronthosting.co.za (Daniel Diniz)
Date: Thu, 19 Feb 2009 20:11:40 +0000
Subject: [Tracker-discuss] [issue167] Added resolution keyword "confirmed"
In-Reply-To: <1194626858.37.0.770894714995.issue167@psf.upfronthosting.co.za>
Message-ID: <1235074300.63.0.240286245738.issue167@psf.upfronthosting.co.za>


Daniel Diniz <ajaksu at gmail.com> added the comment:

I think the more synthetic 'unconfirmed' or 'unverified' would be easier to
understand than 'not yet verified' for us Portuguese speakers. OTOH,'not yet'
helps delivering a 'just waiting for your help' message.

So, in short, I'm not even sure why I posted this :D

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

From metatracker at psf.upfronthosting.co.za  Thu Feb 19 21:12:26 2009
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v._L=C3=B6wis?=)
Date: Thu, 19 Feb 2009 20:12:26 +0000
Subject: [Tracker-discuss] [issue207] Denote which dependencies issues have
	been closed
In-Reply-To: <1211141168.1.0.612084028465.issue207@psf.upfronthosting.co.za>
Message-ID: <1235074346.94.0.298278682223.issue207@psf.upfronthosting.co.za>


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

Thanks, committed as r69782. To see this in action, look at

http://bugs.python.org/issue2775

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

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

From ajaksu at gmail.com  Thu Feb 19 21:21:21 2009
From: ajaksu at gmail.com (Daniel (ajax) Diniz)
Date: Thu, 19 Feb 2009 17:21:21 -0300
Subject: [Tracker-discuss] Tracker hacking workflow
In-Reply-To: <499DB8EC.8030003@v.loewis.de>
References: <2d75d7660902190527m6d2d1b57v149cb5c89f4d77b3@mail.gmail.com>
	<499DAD33.2050305@v.loewis.de>
	<2d75d7660902191148g7817e2c1gf9e18133ab24a50@mail.gmail.com>
	<499DB8EC.8030003@v.loewis.de>
Message-ID: <2d75d7660902191221v718e827cg8d819156ae6a9cd4@mail.gmail.com>

"Martin v. L?wis"  wrote:
>> I can offer a patch to solve an issue in the meta tracker, but I don't
>> expect most ticket submitters to set a local instance just to see if I
>> got things right. I don't want bugs.python.org to be the testbed
>> either :)
>
> It has been so far, and it worked quite well. So I don't worry too much
> about breaking it - people will notice us fast enough.
>
>> So, short of working with screenshots (see attachment :D), I think the
>> easiest way to get feedback from the submitter is to offer a ride on a
>> patched instance. I have at least two patches I'd like feedback on
>> looks (CSS), one for marking closed dependencies and the screenshot
>> attached :)
>
> Don't get me wrong: if you want to set up a public test installation,
> go ahead! All I'm saying is that I feel it's not necessary (I will
> continue to test on my local installation, if I test at all).

OK, I might even become a little more courageous along the way and not
set it up. Right now, the idea of a public sandbox sounds great :)

> We can also arrange to host a test installation on the upfronthosting
> machine - although we'll have to restrict access to that machine to
> very few people.

I don't think it'd be necessary, but I'd like to know more about the
setup of the Python tracker. Things like which server/module is used,
which fulltext indexer, how heavily loaded it is, etc. I'll come back
asking the right questions when I find them out :)

Daniel

From metatracker at psf.upfronthosting.co.za  Thu Feb 19 21:21:46 2009
From: metatracker at psf.upfronthosting.co.za (Brett C.)
Date: Thu, 19 Feb 2009 20:21:46 +0000
Subject: [Tracker-discuss] [issue207] Denote which dependencies issues have
	been closed
In-Reply-To: <1235074346.94.0.298278682223.issue207@psf.upfronthosting.co.za>
Message-ID: <bbaeab100902191221y6a5f2c25o90d92b6b0a23275a@mail.gmail.com>


Brett C. <brett at python.org> added the comment:

On Thu, Feb 19, 2009 at 12:12, Martin v. L?wis <
metatracker at psf.upfronthosting.co.za> wrote:

>
> Martin v. L?wis <martin at v.loewis.de> added the comment:
>
> Thanks, committed as r69782. To see this in action, look at
>
> http://bugs.python.org/issue2775

Very cool!

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

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue207>
_______________________________________________________
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/tracker-discuss/attachments/20090219/6cfe10bc/attachment.htm>

From metatracker at psf.upfronthosting.co.za  Thu Feb 19 21:24:12 2009
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v._L=C3=B6wis?=)
Date: Thu, 19 Feb 2009 20:24:12 +0000
Subject: [Tracker-discuss] [issue202] Edit Queries screen should include a
	link to the search page
In-Reply-To: <1207668185.49.0.108699616732.issue202@psf.upfronthosting.co.za>
Message-ID: <1235075052.22.0.363846423999.issue202@psf.upfronthosting.co.za>


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

Thanks, committed as r69783. The usage of ok_message is very clever, and
reconfirms how powerful roundup is; please consider contributing that to the
standard template of roundup.

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

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

From metatracker at psf.upfronthosting.co.za  Thu Feb 19 21:30:24 2009
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v._L=C3=B6wis?=)
Date: Thu, 19 Feb 2009 20:30:24 +0000
Subject: [Tracker-discuss] [issue236] Disable CIA.vc detector by default
In-Reply-To: <1235045007.64.0.745186267851.issue236@psf.upfronthosting.co.za>
Message-ID: <1235075424.44.0.71246089386.issue236@psf.upfronthosting.co.za>


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

Thanks for the patch, committed as r69784

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

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

From metatracker at psf.upfronthosting.co.za  Thu Feb 19 21:34:02 2009
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v._L=C3=B6wis?=)
Date: Thu, 19 Feb 2009 20:34:02 +0000
Subject: [Tracker-discuss] [issue167] Added resolution keyword "confirmed"
In-Reply-To: <1235074300.63.0.240286245738.issue167@psf.upfronthosting.co.za>
Message-ID: <499DC238.60000@v.loewis.de>


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

> I think the more synthetic 'unconfirmed' or 'unverified' would be easier to
> understand than 'not yet verified' for us Portuguese speakers. OTOH,'not yet'
> helps delivering a 'just waiting for your help' message.

I thought of "unconfirmed" as well, but that could be misinterpreted as
"someone tried confirming it, and it wasn't reproducible".

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

From martin at v.loewis.de  Thu Feb 19 21:44:01 2009
From: martin at v.loewis.de (=?UTF-8?B?Ik1hcnRpbiB2LiBMw7Z3aXMi?=)
Date: Thu, 19 Feb 2009 21:44:01 +0100
Subject: [Tracker-discuss] Tracker hacking workflow
In-Reply-To: <2d75d7660902191221v718e827cg8d819156ae6a9cd4@mail.gmail.com>
References: <2d75d7660902190527m6d2d1b57v149cb5c89f4d77b3@mail.gmail.com>	
	<499DAD33.2050305@v.loewis.de>	
	<2d75d7660902191148g7817e2c1gf9e18133ab24a50@mail.gmail.com>	
	<499DB8EC.8030003@v.loewis.de>
	<2d75d7660902191221v718e827cg8d819156ae6a9cd4@mail.gmail.com>
Message-ID: <499DC491.7010309@v.loewis.de>

> I don't think it'd be necessary, but I'd like to know more about the
> setup of the Python tracker. Things like which server/module is used,
> which fulltext indexer, how heavily loaded it is, etc. I'll come back
> asking the right questions when I find them out :)

Some are easy to answer:
- Linux 2.6.17 vserver, Apache 2.2.3, roundup-server,
  request-forwarding through mod_rewrite (with a bypass for @@file)
- fulltext indexer: no idea, how do I tell?
- right now: load average ca. 0.3. From Feb 8 to Feb 15, number
  of accesses to bugs.python.org: 272589

HTH,
Martin

From ajaksu at gmail.com  Thu Feb 19 22:17:18 2009
From: ajaksu at gmail.com (Daniel (ajax) Diniz)
Date: Thu, 19 Feb 2009 18:17:18 -0300
Subject: [Tracker-discuss] Tracker hacking workflow
In-Reply-To: <499DC491.7010309@v.loewis.de>
References: <2d75d7660902190527m6d2d1b57v149cb5c89f4d77b3@mail.gmail.com>
	<499DAD33.2050305@v.loewis.de>
	<2d75d7660902191148g7817e2c1gf9e18133ab24a50@mail.gmail.com>
	<499DB8EC.8030003@v.loewis.de>
	<2d75d7660902191221v718e827cg8d819156ae6a9cd4@mail.gmail.com>
	<499DC491.7010309@v.loewis.de>
Message-ID: <2d75d7660902191317n737accb3p83ddc05f2f360947@mail.gmail.com>

"Martin v. L?wis" wrote:
>> I don't think it'd be necessary, but I'd like to know more about the
>> setup of the Python tracker. Things like which server/module is used,
>> which fulltext indexer, how heavily loaded it is, etc. I'll come back
>> asking the right questions when I find them out :)
>
> Some are easy to answer:
> - Linux 2.6.17 vserver, Apache 2.2.3, roundup-server,
>  request-forwarding through mod_rewrite (with a bypass for @@file)

Thanks, @@file was fooling me indeed.

> - fulltext indexer: no idea, how do I tell?

That's a little fuzzy on docs, I think it'll be Xapian if available,
the DB otherwise. That'll only make a difference for trying to have
those flexible searches, so it's nothing we should worry about now.

> - right now: load average ca. 0.3. From Feb 8 to Feb 15, number
>  of accesses to bugs.python.org: 272589

Nice, I won't even think of stress testing a local instance then, it
seems the server is at ease :)

Thanks for the info!

Daniel

From ajaksu at gmail.com  Thu Feb 19 23:10:41 2009
From: ajaksu at gmail.com (Daniel (ajax) Diniz)
Date: Thu, 19 Feb 2009 19:10:41 -0300
Subject: [Tracker-discuss] Tracker hacking workflow
In-Reply-To: <20090219190719.GO91939@nexus.in-nomine.org>
References: <2d75d7660902190527m6d2d1b57v149cb5c89f4d77b3@mail.gmail.com>
	<20090219190719.GO91939@nexus.in-nomine.org>
Message-ID: <2d75d7660902191410l1b4a9ea4x3a0410c974303cb3@mail.gmail.com>

Jeroen Ruigrok van der Werven wrote:
> Right now patches might sound better until we really need to get cracking at
> some major changes or so.

OK :)

> Right now I'm just focusing on getting local changes resolved with the 1.4.6
> release.

Cool, thanks a lot for looking into this.

Daniel

From metatracker at psf.upfronthosting.co.za  Fri Feb 20 00:16:18 2009
From: metatracker at psf.upfronthosting.co.za (Daniel Diniz)
Date: Thu, 19 Feb 2009 23:16:18 +0000
Subject: [Tracker-discuss] [issue225] Ordering of messages is incorrect for
	some jython issues.
In-Reply-To: <1225134556.68.0.873773412263.issue225@psf.upfronthosting.co.za>
Message-ID: <1235085378.52.0.70652453927.issue225@psf.upfronthosting.co.za>


Daniel Diniz <ajaksu at gmail.com> added the comment:

Quoting http://www.roundup-tracker.org/docs/FAQ.html#id15:
'''
How is sorting performed, and why does it seem to fail sometimes?

When we sort items in the hyperdb, we use one of a number of methods, depending
on the properties being sorted on:
[...]
Note that if an ?order? property is defined on a Class that is used for sorting,
all items of that Class must have a value against the ?order? property, or
sorting will result in random ordering.
'''

Taking a look at the linked issue, it seems to have two oddities compared to 
other issues I opened inn the Jython tracker: messages with a SpamBayes score of
0 (as opposed to a very small number > 0) and one message with the "In-reply-to"
header set.

Could you take a look at other problematic issues (didn't find any) and check
these, please?

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

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

From metatracker at psf.upfronthosting.co.za  Fri Feb 20 00:50:42 2009
From: metatracker at psf.upfronthosting.co.za (Daniel Diniz)
Date: Thu, 19 Feb 2009 23:50:42 +0000
Subject: [Tracker-discuss] [issue218] Inline Patch options for python-bugs
	list and roundup email
In-Reply-To: <1220585553.16.0.432911761102.issue218@psf.upfronthosting.co.za>
Message-ID: <1235087442.76.0.129833395994.issue218@psf.upfronthosting.co.za>


Daniel Diniz <ajaksu at gmail.com> added the comment:

I don't think the potential benefits of inlining would be worth the overhead and
maintenance burden. It doesn't seem too hard to inline clean ASCII patches, even
to check for a maximum size before inlining. But I wouldn't like to have to fix
broken inlining of files with invalid chars, mixed line-endings, whatever.

If more people ask for attachments (below a maximum size), I'll try to implement it.

----------
nosy: +ajaksu2

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

From metatracker at psf.upfronthosting.co.za  Fri Feb 20 00:57:48 2009
From: metatracker at psf.upfronthosting.co.za (Brett C.)
Date: Thu, 19 Feb 2009 23:57:48 +0000
Subject: [Tracker-discuss] [issue218] Inline Patch options for python-bugs
	list and roundup email
In-Reply-To: <1220585553.16.0.432911761102.issue218@psf.upfronthosting.co.za>
Message-ID: <1235087868.86.0.690759382979.issue218@psf.upfronthosting.co.za>


Brett C. <brett at python.org> added the comment:

I say we don't worry about this. Use case is not worth the headache of
supporting it.

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

From metatracker at psf.upfronthosting.co.za  Sun Feb 22 23:27:04 2009
From: metatracker at psf.upfronthosting.co.za (Daniel Diniz)
Date: Sun, 22 Feb 2009 22:27:04 +0000
Subject: [Tracker-discuss] [issue172] Traceback exposed in misformed URL
In-Reply-To: <1196951026.1.0.157520960574.issue172@psf.upfronthosting.co.za>
Message-ID: <1235341624.08.0.495696479251.issue172@psf.upfronthosting.co.za>


Daniel Diniz <ajaksu at gmail.com> added the comment:

Ho, it turns out that passing invalid values for fields also hits something
similar to this.

This new patch handles DB errors for values like 'type':'123123123123' and also
catches '@sort0=FRUTA'.

It's not finished. I'm creating new issues with a command-line client (will
start editing them soon) and more cases will probably be uncovered :)

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue172>
_______________________________________________________
-------------- next part --------------
A non-text attachment was scrubbed...
Name: invalid_input.diff
Type: text/x-diff
Size: 4074 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/tracker-discuss/attachments/20090222/d4ca754e/attachment.diff>

From metatracker at psf.upfronthosting.co.za  Tue Feb 24 18:00:05 2009
From: metatracker at psf.upfronthosting.co.za (Daniel Diniz)
Date: Tue, 24 Feb 2009 17:00:05 +0000
Subject: [Tracker-discuss] [issue242] Add 'Stage' to results page
In-Reply-To: <1235494805.03.0.629781097036.issue242@psf.upfronthosting.co.za>
Message-ID: <1235494805.03.0.629781097036.issue242@psf.upfronthosting.co.za>


New submission from Daniel Diniz <ajaksu at gmail.com>:

This patch adds 'Stage' as a column to the search results when 'Display' is
selected (it already worked for '[Group|Sort] on'). Also removes a spurious
'<td>&nbsp<td>' from 'Stage' row in the search page.

----------
files: stages_search_display.diff
messages: 1187
nosy: ajaksu2
priority: feature
status: unread
title: Add 'Stage' to results page

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue242>
_______________________________________________________
-------------- next part --------------
A non-text attachment was scrubbed...
Name: stages_search_display.diff
Type: text/x-diff
Size: 1626 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/tracker-discuss/attachments/20090224/820a2792/attachment.diff>

From metatracker at psf.upfronthosting.co.za  Tue Feb 24 18:04:06 2009
From: metatracker at psf.upfronthosting.co.za (Daniel Diniz)
Date: Tue, 24 Feb 2009 17:04:06 +0000
Subject: [Tracker-discuss] [issue238] Update 'initial_data.py' to match
	current values
In-Reply-To: <1235045063.45.0.472608826025.issue238@psf.upfronthosting.co.za>
Message-ID: <1235495046.69.0.209407019198.issue238@psf.upfronthosting.co.za>


Daniel Diniz <ajaksu at gmail.com> added the comment:

Thanks, Martin! It's been a real time saver for my search tests.

Here's an updated diff that should allow local instances to have matching IDs
for all field values.

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue238>
_______________________________________________________
-------------- next part --------------
A non-text attachment was scrubbed...
Name: initial_data_updated.diff
Type: text/x-diff
Size: 7682 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/tracker-discuss/attachments/20090224/20052cfa/attachment.diff>

From metatracker at psf.upfronthosting.co.za  Tue Feb 24 19:26:34 2009
From: metatracker at psf.upfronthosting.co.za (Daniel Diniz)
Date: Tue, 24 Feb 2009 18:26:34 +0000
Subject: [Tracker-discuss] [issue243] Add multiselects for searches
In-Reply-To: <1235496930.77.0.173448579527.issue243@psf.upfronthosting.co.za>
Message-ID: <1235499994.28.0.905674483616.issue243@psf.upfronthosting.co.za>


Daniel Diniz <ajaksu at gmail.com> added the comment:

It seems Multilinks (like Keywords, Components and Versions) won't support
searches for "ID in [X, 'not selected']" as effortlessly as they support "ID in
[X, Y]". Links work fine already.

Another item in another ToDo list :)

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

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

From metatracker at psf.upfronthosting.co.za  Tue Feb 24 18:35:30 2009
From: metatracker at psf.upfronthosting.co.za (Daniel Diniz)
Date: Tue, 24 Feb 2009 17:35:30 +0000
Subject: [Tracker-discuss] [issue243] Add multiselects for searches
In-Reply-To: <1235496930.77.0.173448579527.issue243@psf.upfronthosting.co.za>
Message-ID: <1235496930.77.0.173448579527.issue243@psf.upfronthosting.co.za>


New submission from Daniel Diniz <ajaksu at gmail.com>:

Currently, the search interface doesn't implement an interesting Roundup
feature: multi select fields can be queried in an OR fashion.

This allows one to search, e.g., for issues with "Version in ['2.5', '2.6',
'2.7']" or "Stage in ['patch review', 'not selected']". Right now Version in
['not selected', 'x.y'] ignores the 'not selected' part.

However, displaying all these fields as multi selects makes the search page too
complicated. I've worked on a couple (unobtrusive) JavaScript and CSS hacks to
expose the feature, any feedback would be of great help.

The attached page should work OK with JS enabled and degrade gracefully
otherwise. It's more of a request for comments, so only I tried to present
alternatives (as opposed to optimizing ease-of-use / looks).

Here's example SQL currently generated for Stage, I'll look into the Versions
issue later.

Stage:
    Allows multiple stages as OR query (comma-separated)
    * select _issue.id from _issue where ((_issue._stage in (E'3')))
    'not selected' query is weird:
    * select id from _stage where _name=E'-1'
      select _issue.id from _issue   where (_issue._stage is NULL)

----------
files: issue_search.html
messages: 1189
nosy: ajaksu2
priority: wish
status: unread
title: Add multiselects for searches

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue243>
_______________________________________________________
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/tracker-discuss/attachments/20090224/8f424966/attachment-0001.html>

From metatracker at psf.upfronthosting.co.za  Wed Feb 25 23:00:59 2009
From: metatracker at psf.upfronthosting.co.za (Daniel Diniz)
Date: Wed, 25 Feb 2009 22:00:59 +0000
Subject: [Tracker-discuss] [issue244] Any User can hijack other Users'
	Queries
In-Reply-To: <1235599259.83.0.0315928724687.issue244@psf.upfronthosting.co.za>
Message-ID: <1235599259.83.0.0315928724687.issue244@psf.upfronthosting.co.za>


New submission from Daniel Diniz <ajaksu at gmail.com>:

Any User has the ability to edit or create Queries, which equates to Admin's
ability to edit Classes, as far as Queries are concerned. This ignores Query
ownership in the CSV interface, allowing one to edit, steal or delete someone
else's Queries.

Attached patch blocks this path.

----------
files: actions_query.diff
messages: 1191
nosy: ajaksu2
priority: urgent
status: unread
title: Any User can hijack other Users' Queries

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue244>
_______________________________________________________
-------------- next part --------------
A non-text attachment was scrubbed...
Name: actions_query.diff
Type: text/x-diff
Size: 776 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/tracker-discuss/attachments/20090225/fa3f4b03/attachment.diff>

From metatracker at psf.upfronthosting.co.za  Wed Feb 25 23:10:47 2009
From: metatracker at psf.upfronthosting.co.za (Daniel Diniz)
Date: Wed, 25 Feb 2009 22:10:47 +0000
Subject: [Tracker-discuss] [issue244] Any User can hijack other Users'
	Queries
In-Reply-To: <1235599259.83.0.0315928724687.issue244@psf.upfronthosting.co.za>
Message-ID: <1235599847.61.0.875621183596.issue244@psf.upfronthosting.co.za>


Daniel Diniz <ajaksu at gmail.com> added the comment:

And this one removes the UI :)

I think 'keyword' (implying 'Developer') might not be strict enough...

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

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue244>
_______________________________________________________
-------------- next part --------------
A non-text attachment was scrubbed...
Name: _generic_index_query.diff
Type: text/x-diff
Size: 613 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/tracker-discuss/attachments/20090225/cd1a471f/attachment.diff>