From amk at amk.ca  Sat May  3 01:11:32 2008
From: amk at amk.ca (A.M. Kuchling)
Date: Fri, 2 May 2008 19:11:32 -0400
Subject: [Tracker-discuss] [peke@iki.fi: [Jython-dev] Bug in 2.2.1: "%s" %
	u"\xA7" -> UnicodeError]
Message-ID: <20080502231132.GA22290@amk.local>

This jython-dev e-mail says that password resets aren't sending mail
successfully for the Jython tracker.  Can someone please confirm/fix?
Thanks!

--amk

-------------- next part --------------
An embedded message was scrubbed...
From: "Pekka Laukkanen" <peke at iki.fi>
Subject: [Jython-dev] Bug in 2.2.1: "%s" % u"\xA7" -> UnicodeError
Date: Fri, 2 May 2008 18:22:45 +0300
Size: 6014
URL: <http://mail.python.org/pipermail/tracker-discuss/attachments/20080502/7ed74880/attachment.eml>

From martin at v.loewis.de  Sat May  3 08:48:48 2008
From: martin at v.loewis.de (=?ISO-8859-1?Q?=22Martin_v=2E_L=F6wis=22?=)
Date: Sat, 03 May 2008 08:48:48 +0200
Subject: [Tracker-discuss] [peke@iki.fi: [Jython-dev] Bug in 2.2.1: "%s"
 %	u"\xA7" -> UnicodeError]
In-Reply-To: <20080502231132.GA22290@amk.local>
References: <20080502231132.GA22290@amk.local>
Message-ID: <481C0AD0.5010904@v.loewis.de>

> This jython-dev e-mail says that password resets aren't sending mail
> successfully for the Jython tracker.  Can someone please confirm/fix?

I just tried, and it works fine.

Regards,
Martin

From metatracker at psf.upfronthosting.co.za  Tue May  6 19:17:02 2008
From: metatracker at psf.upfronthosting.co.za (Georg Brandl)
Date: Tue, 06 May 2008 17:17:02 +0000
Subject: [Tracker-discuss] [issue204] Make reading the list of issues easier
In-Reply-To: <1210094220.54.0.585393177491.issue204@psf.upfronthosting.co.za>
Message-ID: <1210094220.54.0.585393177491.issue204@psf.upfronthosting.co.za>


New submission from Georg Brandl <g.brandl at gmx.net>:

A very low-priority feature request: distinguish table rows visually in issue
listings, making it easier to recognize which values belong together in
different columns.

----------
messages: 1040
nosy: gbrandl
priority: wish
status: unread
title: Make reading the list of issues easier

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

From metatracker at psf.upfronthosting.co.za  Wed May  7 07:24:33 2008
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v._L=C3=B6wis?=)
Date: Wed, 07 May 2008 05:24:33 +0000
Subject: [Tracker-discuss] [issue204] Make reading the list of issues easier
In-Reply-To: <1210094220.54.0.585393177491.issue204@psf.upfronthosting.co.za>
Message-ID: <1210137873.54.0.0265292529733.issue204@psf.upfronthosting.co.za>


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

This is now fixed in r62813. If you were interested in specific lists other than
the item list, please indicate which lists. If you dislike the colors, please
propose a patch to the style sheet.

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

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

From izak at upfrontsystems.co.za  Thu May 15 21:17:16 2008
From: izak at upfrontsystems.co.za (Izak Burger)
Date: Thu, 15 May 2008 21:17:16 +0200
Subject: [Tracker-discuss] Regenerated ssh keys on PSF
Message-ID: <482C8C3C.505@upfrontsystems.co.za>

Hi all,

Due to a recent vulnerability discovered in openssl, which also affects 
openssh and any keys generated by it, I had to regenerate the host key 
on the psf virtual host.

The fingerprint for the new key is: 
c4:ad:63:92:1b:c0:4a:35:c8:c5:3e:96:51:c0:88:67

You may want to do the same with any key pairs you use.

regards,
Izak

From doug.napoleone at gmail.com  Thu May 15 22:27:36 2008
From: doug.napoleone at gmail.com (Douglas Napoleone)
Date: Thu, 15 May 2008 16:27:36 -0400
Subject: [Tracker-discuss] Regenerated ssh keys on PSF
In-Reply-To: <482C8C3C.505@upfrontsystems.co.za>
References: <482C8C3C.505@upfrontsystems.co.za>
Message-ID: <f08f4fbb0805151327g12c7669fv7f1eb0d698e18c18@mail.gmail.com>

NOTE: only keys generated post May 2006 are 'weak' due to the code
change which was introduced at the time. If you generated your key
pairs with openssl before that date, you should be fine.

Full writeup here:
http://blog.isotoma.com/2008/05/debians_openssl_disaster.html

    -Doug


On Thu, May 15, 2008 at 3:17 PM, Izak Burger <izak at upfrontsystems.co.za> wrote:
> Hi all,
>
> Due to a recent vulnerability discovered in openssl, which also affects
> openssh and any keys generated by it, I had to regenerate the host key on
> the psf virtual host.
>
> The fingerprint for the new key is:
> c4:ad:63:92:1b:c0:4a:35:c8:c5:3e:96:51:c0:88:67
>
> You may want to do the same with any key pairs you use.
>
> regards,
> Izak
> _______________________________________________
> Tracker-discuss mailing list
> Tracker-discuss at python.org
> http://mail.python.org/mailman/listinfo/tracker-discuss
>

From metatracker at psf.upfronthosting.co.za  Sun May 18 21:47:23 2008
From: metatracker at psf.upfronthosting.co.za (Georg Brandl)
Date: Sun, 18 May 2008 19:47:23 +0000
Subject: [Tracker-discuss] [issue205] No feedback for invalid user name in
	search
In-Reply-To: <1211140043.34.0.175492627112.issue205@psf.upfronthosting.co.za>
Message-ID: <1211140043.34.0.175492627112.issue205@psf.upfronthosting.co.za>


New submission from Georg Brandl <g.brandl at gmx.net>:

When entering a wrong name in the "Creator" field (and probably other user
fields) in the search form, no hint is given that the user doesn't exist,
instead all issues are shown.

Is that intentional, or can it be fixed?

----------
messages: 1042
nosy: gbrandl
priority: bug
status: unread
title: No feedback for invalid user name in search

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

From metatracker at psf.upfronthosting.co.za  Sun May 18 22:04:16 2008
From: metatracker at psf.upfronthosting.co.za (Brett C.)
Date: Sun, 18 May 2008 20:04:16 +0000
Subject: [Tracker-discuss] [issue206] Sorting the dependencies list
In-Reply-To: <1211141056.56.0.826960816435.issue206@psf.upfronthosting.co.za>
Message-ID: <1211141056.56.0.826960816435.issue206@psf.upfronthosting.co.za>


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

It would be nice to sort the dependencies list in ascending order to make it 
easier to see if an issue is listed and to remove it from the list.

----------
messages: 1043
nosy: brett.cannon
priority: wish
status: unread
title: Sorting the dependencies list

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

From metatracker at psf.upfronthosting.co.za  Sun May 18 22:06:08 2008
From: metatracker at psf.upfronthosting.co.za (Brett C.)
Date: Sun, 18 May 2008 20:06:08 +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: <1211141168.1.0.612084028465.issue207@psf.upfronthosting.co.za>


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

When looking at an issue's dependencies list, there is no way to know which 
dependencies have been closed (and thus are no longer holding the issue under 
question up) or which are still open (and thus blocking closing the issue). It 
would be nice to somehow denote this in the dependencies list. Otherwise one has 
to manually go through and remove closed issues to get a better idea of what is 
left to do for an issue, which is needlessly destructive to useful information 
about an issue.

----------
messages: 1044
nosy: brett.cannon
priority: wish
status: unread
title: Denote which dependencies issues have been closed

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

From metatracker at psf.upfronthosting.co.za  Sun May 18 22:09:12 2008
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v._L=C3=B6wis?=)
Date: Sun, 18 May 2008 20:09:12 +0000
Subject: [Tracker-discuss] [issue205] No feedback for invalid user name in
	search
In-Reply-To: <1211140043.34.0.175492627112.issue205@psf.upfronthosting.co.za>
Message-ID: <1211141352.69.0.355009479796.issue205@psf.upfronthosting.co.za>


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

See issue153. It may be possible to fix this, but nobody knows how to.

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

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

From metatracker at psf.upfronthosting.co.za  Sun May 18 22:10:23 2008
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v._L=C3=B6wis?=)
Date: Sun, 18 May 2008 20:10:23 +0000
Subject: [Tracker-discuss] [issue206] Sorting the dependencies list
In-Reply-To: <1211141056.56.0.826960816435.issue206@psf.upfronthosting.co.za>
Message-ID: <1211141423.25.0.81655439034.issue206@psf.upfronthosting.co.za>


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

Can you give an example of an issue with a non-empty dependencies list?

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

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

From metatracker at psf.upfronthosting.co.za  Sun May 18 23:02:13 2008
From: metatracker at psf.upfronthosting.co.za (Georg Brandl)
Date: Sun, 18 May 2008 21:02:13 +0000
Subject: [Tracker-discuss] [issue205] No feedback for invalid user name in
	search
In-Reply-To: <1211140043.34.0.175492627112.issue205@psf.upfronthosting.co.za>
Message-ID: <1211144533.33.0.0375059580272.issue205@psf.upfronthosting.co.za>


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

Ah. I had thought I remembered something like this. Well, probably best to close
this then.

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

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

From metatracker at psf.upfronthosting.co.za  Mon May 19 10:06:01 2008
From: metatracker at psf.upfronthosting.co.za (Quentin Gallet-Gilles)
Date: Mon, 19 May 2008 08:06:01 +0000
Subject: [Tracker-discuss] [issue206] Sorting the dependencies list
In-Reply-To: <1211141056.56.0.826960816435.issue206@psf.upfronthosting.co.za>
Message-ID: <1211184356.31.0.752936008615.issue206@psf.upfronthosting.co.za>


Quentin Gallet-Gilles <qgallet at gmail.com> added the comment:

I believe Brett is talking about the issue used to track the PEP 3138 progress :
http://bugs.python.org/issue2775

----------
nosy: +quentin.gallet-gilles

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

From metatracker at psf.upfronthosting.co.za  Mon May 19 20:56:29 2008
From: metatracker at psf.upfronthosting.co.za (Brett C.)
Date: Mon, 19 May 2008 18:56:29 +0000
Subject: [Tracker-discuss] [issue206] Sorting the dependencies list
In-Reply-To: <1211141056.56.0.826960816435.issue206@psf.upfronthosting.co.za>
Message-ID: <1211223389.57.0.00356434619184.issue206@psf.upfronthosting.co.za>


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

I am talking about issue 2775 for PEP 3108 which has a rather long dependencies 
list.

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

From metatracker at psf.upfronthosting.co.za  Mon May 19 22:39:24 2008
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v._L=C3=B6wis?=)
Date: Mon, 19 May 2008 20:39:24 +0000
Subject: [Tracker-discuss] [issue206] Sorting the dependencies list
In-Reply-To: <1211141056.56.0.826960816435.issue206@psf.upfronthosting.co.za>
Message-ID: <1211229564.65.0.69799808388.issue206@psf.upfronthosting.co.za>


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

Thanks for the report. This is now fixed in r63472 (sorting issues by creation)

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

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

From metatracker at psf.upfronthosting.co.za  Mon May 19 22:48:47 2008
From: metatracker at psf.upfronthosting.co.za (Brett C.)
Date: Mon, 19 May 2008 20:48:47 +0000
Subject: [Tracker-discuss] [issue206] Sorting the dependencies list
In-Reply-To: <1211229564.65.0.69799808388.issue206@psf.upfronthosting.co.za>
Message-ID: <bbaeab100805191348n4f527c9lb69e62e4ceab5ad9@mail.gmail.com>


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

On Mon, May 19, 2008 at 1:39 PM, Martin v. L?wis
<metatracker at psf.upfronthosting.co.za> wrote:
>
> Martin v. L?wis <martin at v.loewis.de> added the comment:
>
> Thanks for the report. This is now fixed in r63472 (sorting issues by creation)
>

Thanks, Martin!

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

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

From metatracker at psf.upfronthosting.co.za  Wed May 21 15:02:25 2008
From: metatracker at psf.upfronthosting.co.za (Vinay Sajip)
Date: Wed, 21 May 2008 13:02:25 +0000
Subject: [Tracker-discuss] [issue208] Spurious results in search
In-Reply-To: <1211374945.26.0.731871548674.issue208@psf.upfronthosting.co.za>
Message-ID: <1211374945.26.0.731871548674.issue208@psf.upfronthosting.co.za>


New submission from Vinay Sajip <vinay_sajip at red-dove.com>:

bugs.python.org appears to include spurious results in search. For example, a
search for "logging" returns (amongst others) Issue 2663,

http://bugs.python.org/issue2663

which does not appear to be about logging, or even contain the text "log" in the
issue or any of the comments.

----------
messages: 1052
nosy: vsajip
priority: bug
status: unread
title: Spurious results in search

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

From metatracker at psf.upfronthosting.co.za  Sat May 24 02:39:56 2008
From: metatracker at psf.upfronthosting.co.za (Brett C.)
Date: Sat, 24 May 2008 00:39:56 +0000
Subject: [Tracker-discuss] [issue196] RE for matchig revision id's needs
	tweaking
In-Reply-To: <1204917161.88.0.0844926023843.issue196@psf.upfronthosting.co.za>
Message-ID: <1211589595.77.0.822822901252.issue196@psf.upfronthosting.co.za>


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

Another message that exposes a problem with the regex is http://bugs.python.org/msg67278 .

----------
nosy: +brett.cannon

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

From metatracker at psf.upfronthosting.co.za  Tue May 27 15:49:05 2008
From: metatracker at psf.upfronthosting.co.za (Philipp Gortan)
Date: Tue, 27 May 2008 13:49:05 +0000
Subject: [Tracker-discuss] [issue208] Spurious results in search
In-Reply-To: <1211374945.26.0.731871548674.issue208@psf.upfronthosting.co.za>
Message-ID: <1211896145.72.0.233701872172.issue208@psf.upfronthosting.co.za>


Philipp Gortan <mephinet at gmx.net> added the comment:

Well, the word "logging" turns out to be contained in the file which is attached
to that issue, "copytree.patch". It looks like this file is indexed, too - at
least when I search for some variable names that are used in this patch, e.g.
"ignored_names" or "ignore_patterns", I also get this issue as a result. This
might explain your "spurious" behavior - which I'd then call "feature" ;-)

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

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

From metatracker at psf.upfronthosting.co.za  Tue May 27 17:22:10 2008
From: metatracker at psf.upfronthosting.co.za (Vinay Sajip)
Date: Tue, 27 May 2008 15:22:10 +0000
Subject: [Tracker-discuss] [issue208] Spurious results in search
In-Reply-To: <1211374945.26.0.731871548674.issue208@psf.upfronthosting.co.za>
Message-ID: <1211901730.39.0.644997427212.issue208@psf.upfronthosting.co.za>


Vinay Sajip <vinay_sajip at red-dove.com> added the comment:

Yes, I agree. Sorry I missed checking the attachments! In hindsight, I should
have done this before posting here...So I am marking it as resolved. Sorry for
the noise!

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

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