From metatracker at psf.upfronthosting.co.za  Sat Jan  2 20:10:59 2010
From: metatracker at psf.upfronthosting.co.za (Ezio Melotti)
Date: Sat, 02 Jan 2010 19:10:59 +0000
Subject: [Tracker-discuss] [issue309] Problems with wrap="hard" and konqueror
In-Reply-To: <1262459459.14.0.698323309061.issue309@psf.upfronthosting.co.za>
Message-ID: <1262459459.14.0.698323309061.issue309@psf.upfronthosting.co.za>


New submission from Ezio Melotti <ezio.melotti at gmail.com>:

The 'Comment' textarea in the issue page uses wrap="hard". Konqueror has a bug
that truncates the text if the line is longer of the 72-columns limit of the
textarea (https://bugs.kde.org/show_bug.cgi?id=220005). This caused problems
like http://bugs.python.org/issue7617#msg97115 .
The 'wrap' attribute is not even valid HTML
(http://www.w3.org/TR/html401/interact/forms.html#edef-TEXTAREA).
I suggest to remove it and implement the line-breaking server-side. Also note
that it's easy to avoid the 72 chars limit if the message is sent via mail (see
http://bugs.python.org/issue7621#msg97144).
(Thanks to Georg Brandl that investigated the issue.)

----------
messages: 1492
nosy: ezio.melotti, loewis
priority: wish
status: unread
title: Problems with wrap="hard" and konqueror

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

From metatracker at psf.upfronthosting.co.za  Sat Jan  2 20:49:23 2010
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v=2E_L=C3=B6wis?=)
Date: Sat, 02 Jan 2010 19:49:23 +0000
Subject: [Tracker-discuss] [issue309] Problems with wrap="hard" and konqueror
In-Reply-To: <1262459459.14.0.698323309061.issue309@psf.upfronthosting.co.za>
Message-ID: <1262461763.8.0.77378666039.issue309@psf.upfronthosting.co.za>


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

This is now fixed in issue 309. The wrapping should already happend through CSS.

----------
status: unread -> resolved

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

From metatracker at psf.upfronthosting.co.za  Sat Jan  2 20:50:01 2010
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v=2E_L=C3=B6wis?=)
Date: Sat, 02 Jan 2010 19:50:01 +0000
Subject: [Tracker-discuss] [issue309] Problems with wrap="hard" and konqueror
In-Reply-To: <1262459459.14.0.698323309061.issue309@psf.upfronthosting.co.za>
Message-ID: <1262461801.38.0.126049157688.issue309@psf.upfronthosting.co.za>


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

s/issue 309/revision 77239/

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

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

From metatracker at psf.upfronthosting.co.za  Sun Jan  3 13:41:01 2010
From: metatracker at psf.upfronthosting.co.za (Antoine Pitrou)
Date: Sun, 03 Jan 2010 12:41:01 +0000
Subject: [Tracker-discuss] [issue310] Email gateway broken
In-Reply-To: <1262522461.88.0.655997318312.issue310@psf.upfronthosting.co.za>
Message-ID: <1262522461.88.0.655997318312.issue310@psf.upfronthosting.co.za>


New submission from Antoine Pitrou <pitrou at free.fr>:

I got the following failure when trying to reply to an issue via an e-mail:

?There were problems handling your subject line argument list:
- not of form [arg=value,value,...;arg=value,value,...]

Subject was: "Re: [issue1755841] Patch for [ 735515 ] urllib2 should cache 301 redir"?


This is the first time I get this message. Replying by e-mail used to work fine.

----------
messages: 1495
nosy: pitrou
priority: urgent
status: unread
title: Email gateway broken

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

From metatracker at psf.upfronthosting.co.za  Sun Jan  3 13:58:28 2010
From: metatracker at psf.upfronthosting.co.za (Antoine Pitrou)
Date: Sun, 03 Jan 2010 12:58:28 +0000
Subject: [Tracker-discuss] [issue310] Email gateway broken
In-Reply-To: <1262522461.88.0.655997318312.issue310@psf.upfronthosting.co.za>
Message-ID: <1262523508.69.0.865164512095.issue310@psf.upfronthosting.co.za>


Antoine Pitrou <pitrou at free.fr> added the comment:

It worked in another instance. Perhaps it is because of the "[ 735515 ]" in the subject line.

----------
priority: urgent -> bug
status: unread -> chatting

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

From metatracker at psf.upfronthosting.co.za  Sun Jan  3 15:37:56 2010
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v=2E_L=C3=B6wis?=)
Date: Sun, 03 Jan 2010 14:37:56 +0000
Subject: [Tracker-discuss] [issue310] Email gateway broken
In-Reply-To: <1262522461.88.0.655997318312.issue310@psf.upfronthosting.co.za>
Message-ID: <1262529476.51.0.657600630204.issue310@psf.upfronthosting.co.za>


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

It's not a bug; square brackets in the subject are reserved for attribute setting. Just remove them.

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

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

From metatracker at psf.upfronthosting.co.za  Tue Jan  5 08:49:46 2010
From: metatracker at psf.upfronthosting.co.za (Ezio Melotti)
Date: Tue, 05 Jan 2010 07:49:46 +0000
Subject: [Tracker-discuss] [issue309] Problems with wrap="hard" and konqueror
In-Reply-To: <1262459459.14.0.698323309061.issue309@psf.upfronthosting.co.za>
Message-ID: <1262677786.51.0.458575625033.issue309@psf.upfronthosting.co.za>


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

The wrapping doesn't seem to work, now the messages are not limited to 72 chars anymore.

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

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

From metatracker at psf.upfronthosting.co.za  Tue Jan  5 21:41:18 2010
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v=2E_L=C3=B6wis?=)
Date: Tue, 05 Jan 2010 20:41:18 +0000
Subject: [Tracker-discuss] [issue309] Problems with wrap="hard" and konqueror
In-Reply-To: <1262459459.14.0.698323309061.issue309@psf.upfronthosting.co.za>
Message-ID: <1262724078.55.0.560103993835.issue309@psf.upfronthosting.co.za>


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

Can you give an example?

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

From metatracker at psf.upfronthosting.co.za  Wed Jan  6 18:04:22 2010
From: metatracker at psf.upfronthosting.co.za (Ezio Melotti)
Date: Wed, 06 Jan 2010 17:04:22 +0000
Subject: [Tracker-discuss] [issue309] Problems with wrap="hard" and konqueror
In-Reply-To: <1262459459.14.0.698323309061.issue309@psf.upfronthosting.co.za>
Message-ID: <1262797462.49.0.581591660668.issue309@psf.upfronthosting.co.za>


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

For example http://bugs.python.org/issue1755841#msg96899 .
All the messages from there till msg96959 (2009-12-28) are limited to 72 chars per line. Starting from msg97155 (2010-01-03, so after the fix) they just take all the available space, using the whole width of the page.

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

From metatracker at psf.upfronthosting.co.za  Wed Jan  6 19:04:46 2010
From: metatracker at psf.upfronthosting.co.za (Georg Brandl)
Date: Wed, 06 Jan 2010 18:04:46 +0000
Subject: [Tracker-discuss] [issue309] Problems with wrap="hard" and konqueror
In-Reply-To: <1262459459.14.0.698323309061.issue309@psf.upfronthosting.co.za>
Message-ID: <1262801086.93.0.615170915024.issue309@psf.upfronthosting.co.za>


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

That is to be expected when wrap="hard" is removed

I don't think the new behavior is wrong; hard-wrapping at 72 chars also wraps
pasted output which makes it quite ugly to read.

----------
nosy: +gbrandl

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

From metatracker at psf.upfronthosting.co.za  Fri Jan  8 02:36:14 2010
From: metatracker at psf.upfronthosting.co.za (R David Murray)
Date: Fri, 08 Jan 2010 01:36:14 +0000
Subject: [Tracker-discuss] [issue311] Change default search to make
	duplicate issues less likely
In-Reply-To: <1262914574.94.0.0439579037453.issue311@psf.upfronthosting.co.za>
Message-ID: <1262914574.94.0.0439579037453.issue311@psf.upfronthosting.co.za>


New submission from R David Murray <rdmurray at bitdance.com>:

I would like to see the default search (the one run by the search box) changed a bit to make it more likely that non-developer users will find existing but possibly closed bugs that match their problem.  I would recommend that the default be to search all bugs.  I would also like to see the search results ignore the issue priority, and be sorted in descending order (most recently updated bugs listed first).  Hopefully this would reduce the incidence of duplicated bug reports.

(I also note that even as a developer I often run this search, which I can't really set up as a canned search since I need to input the search string, so I would find it useful for myself for it to be the default search.)

----------
messages: 1502
nosy: r.david.murray
priority: feature
status: unread
title: Change default search to make duplicate issues less likely

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

From metatracker at psf.upfronthosting.co.za  Fri Jan 15 15:23:10 2010
From: metatracker at psf.upfronthosting.co.za (Ezio Melotti)
Date: Fri, 15 Jan 2010 14:23:10 +0000
Subject: [Tracker-discuss] [issue312] Add a 'go to the last message' link
In-Reply-To: <1263565390.97.0.608174776201.issue312@psf.upfronthosting.co.za>
Message-ID: <1263565390.97.0.608174776201.issue312@psf.upfronthosting.co.za>


New submission from Ezio Melotti <ezio.melotti at gmail.com>:

It would be useful to have a 'go to the last message' link that sends to http://bugs.python.org/issueXXXX#msgYYYYY somewhere at the beginning of the page (a good place might be just next to the "Messages (N)"). This is especially useful while reading issues from a cellphone (where is not so easy to scroll) and/or when the issue contains lots of message and the last one is somewhere at about 3/4 of the page (the last 1/4 is taken by the log).
Similarly a 'go to the top' link could be added after the last message.
These links will also be useful to go back and forth while answering (using the form at the top) to the last message (at the bottom).

----------
messages: 1503
nosy: ezio.melotti
priority: wish
status: unread
title: Add a 'go to the last message' link

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

From martin at v.loewis.de  Sat Jan 16 19:26:11 2010
From: martin at v.loewis.de (=?ISO-8859-1?Q?=22Martin_v=2E_L=F6wis=22?=)
Date: Sat, 16 Jan 2010 19:26:11 +0100
Subject: [Tracker-discuss] OpenID in python tracker
Message-ID: <4B5204C3.4050309@v.loewis.de>

I have now added OpenID-support to bugs.python.org.
If there are any problems, please report them to the
meta tracker.

Regards,
Martin

From brett at python.org  Sat Jan 16 20:47:18 2010
From: brett at python.org (Brett Cannon)
Date: Sat, 16 Jan 2010 11:47:18 -0800
Subject: [Tracker-discuss] OpenID in python tracker
In-Reply-To: <4B5204C3.4050309@v.loewis.de>
References: <4B5204C3.4050309@v.loewis.de>
Message-ID: <bbaeab101001161147w4c4026a3r453808da44b8f522@mail.gmail.com>

Fantastic! Thanks, Martin!

On Sat, Jan 16, 2010 at 10:26, "Martin v. L?wis" <martin at v.loewis.de> wrote:
> I have now added OpenID-support to bugs.python.org.
> If there are any problems, please report them to the
> meta tracker.
>
> Regards,
> Martin
> _______________________________________________
> Tracker-discuss mailing list
> Tracker-discuss at python.org
> http://mail.python.org/mailman/listinfo/tracker-discuss
>

From metatracker at psf.upfronthosting.co.za  Sat Jan 16 20:57:30 2010
From: metatracker at psf.upfronthosting.co.za (Georg Brandl)
Date: Sat, 16 Jan 2010 19:57:30 +0000
Subject: [Tracker-discuss] [issue313] OpenID in python tracker: better hint
	to registered users
In-Reply-To: <4B5204C3.4050309@v.loewis.de>
Message-ID: <4B521A06.8010105@python.org>


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

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Am 16.01.2010 19:26, schrieb "Martin v. L?wis":
> I have now added OpenID-support to bugs.python.org.
> If there are any problems, please report them to the
> meta tracker.

I first tried to associate my OpenID when logged out, by clicking on
the icons above the login box.  This presents a registration form,
but does not hint that existing users should go to "Your details" and
use the association field there.

The hint could probably replace the SourceForge hint that's still
displayed on that page.

(And there's a space missing in "Login(OpenID possible)".)

Georg
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.14 (GNU/Linux)

iEYEARECAAYFAktSGgYACgkQN9GcIYhpnLA0UwCglC5D1sVOoo9cShUR2pJQMF33
ztkAn3NMkKXzGurw4swllpPJm1qUGgnF
=1sj6
-----END PGP SIGNATURE-----

----------
messages: 1504
nosy: gbrandl, loewis
status: unread
title: OpenID in python tracker: better hint to registered users

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

From georg at python.org  Sat Jan 16 20:56:54 2010
From: georg at python.org (Georg Brandl)
Date: Sat, 16 Jan 2010 20:56:54 +0100
Subject: [Tracker-discuss] OpenID in python tracker: better hint to
	registered users
In-Reply-To: <4B5204C3.4050309@v.loewis.de>
References: <4B5204C3.4050309@v.loewis.de>
Message-ID: <4B521A06.8010105@python.org>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Am 16.01.2010 19:26, schrieb "Martin v. L?wis":
> I have now added OpenID-support to bugs.python.org.
> If there are any problems, please report them to the
> meta tracker.

I first tried to associate my OpenID when logged out, by clicking on
the icons above the login box.  This presents a registration form,
but does not hint that existing users should go to "Your details" and
use the association field there.

The hint could probably replace the SourceForge hint that's still
displayed on that page.

(And there's a space missing in "Login(OpenID possible)".)

Georg
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.14 (GNU/Linux)

iEYEARECAAYFAktSGgYACgkQN9GcIYhpnLA0UwCglC5D1sVOoo9cShUR2pJQMF33
ztkAn3NMkKXzGurw4swllpPJm1qUGgnF
=1sj6
-----END PGP SIGNATURE-----

From metatracker at psf.upfronthosting.co.za  Sat Jan 16 22:31:57 2010
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v=2E_L=C3=B6wis?=)
Date: Sat, 16 Jan 2010 21:31:57 +0000
Subject: [Tracker-discuss] [issue313] OpenID in python tracker: better hint
	to registered users
In-Reply-To: <4B521A06.8010105@python.org>
Message-ID: <4B52304B.4040102@v.loewis.de>


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

> I first tried to associate my OpenID when logged out, by clicking on
> the icons above the login box.  This presents a registration form,
> but does not hint that existing users should go to "Your details" and
> use the association field there.
> 
> The hint could probably replace the SourceForge hint that's still
> displayed on that page.
> 
> (And there's a space missing in "Login(OpenID possible)".)

Thanks; these are now fixed.

Regards,
Martin

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

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

From martin at v.loewis.de  Sat Jan 16 22:31:55 2010
From: martin at v.loewis.de (=?ISO-8859-1?Q?=22Martin_v=2E_L=F6wis=22?=)
Date: Sat, 16 Jan 2010 22:31:55 +0100
Subject: [Tracker-discuss] OpenID in python tracker: better hint to
	registered users
In-Reply-To: <4B521A06.8010105@python.org>
References: <4B5204C3.4050309@v.loewis.de> <4B521A06.8010105@python.org>
Message-ID: <4B52304B.4040102@v.loewis.de>

> I first tried to associate my OpenID when logged out, by clicking on
> the icons above the login box.  This presents a registration form,
> but does not hint that existing users should go to "Your details" and
> use the association field there.
> 
> The hint could probably replace the SourceForge hint that's still
> displayed on that page.
> 
> (And there's a space missing in "Login(OpenID possible)".)

Thanks; these are now fixed.

Regards,
Martin

From metatracker at psf.upfronthosting.co.za  Sat Jan 16 22:51:50 2010
From: metatracker at psf.upfronthosting.co.za (R David Murray)
Date: Sat, 16 Jan 2010 21:51:50 +0000
Subject: [Tracker-discuss] [issue314] OpenId Python tracker: associate gave
	opaque error message
In-Reply-To: <1263678710.47.0.199099744566.issue314@psf.upfronthosting.co.za>
Message-ID: <1263678710.47.0.199099744566.issue314@psf.upfronthosting.co.za>


New submission from R David Murray <rdmurray at bitdance.com>:

I went to details, typed my openid in the form box, clicked associate, and got a page telling me there was an error and the tracker administrators had been informed.

----------
messages: 1506
nosy: r.david.murray
priority: bug
status: unread
title: OpenId Python tracker: associate gave opaque error message

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

From metatracker at psf.upfronthosting.co.za  Sun Jan 17 00:15:55 2010
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v=2E_L=C3=B6wis?=)
Date: Sat, 16 Jan 2010 23:15:55 +0000
Subject: [Tracker-discuss] [issue314] OpenId Python tracker: associate gave
	opaque error message
In-Reply-To: <1263678710.47.0.199099744566.issue314@psf.upfronthosting.co.za>
Message-ID: <1263683755.52.0.095054834623.issue314@psf.upfronthosting.co.za>


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

Please try again; I have fixed a number of problems based on tracker reports.

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

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

From metatracker at psf.upfronthosting.co.za  Sun Jan 17 05:52:42 2010
From: metatracker at psf.upfronthosting.co.za (R David Murray)
Date: Sun, 17 Jan 2010 04:52:42 +0000
Subject: [Tracker-discuss] [issue314] OpenId Python tracker: associate gave
	opaque error message
In-Reply-To: <1263678710.47.0.199099744566.issue314@psf.upfronthosting.co.za>
Message-ID: <1263703962.59.0.485820898463.issue314@psf.upfronthosting.co.za>


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

Got the same error.

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

From metatracker at psf.upfronthosting.co.za  Sun Jan 17 06:47:30 2010
From: metatracker at psf.upfronthosting.co.za (Brett C.)
Date: Sun, 17 Jan 2010 05:47:30 +0000
Subject: [Tracker-discuss] [issue314] OpenId Python tracker: associate gave
	opaque error message
In-Reply-To: <1263678710.47.0.199099744566.issue314@psf.upfronthosting.co.za>
Message-ID: <1263707250.54.0.171569729003.issue314@psf.upfronthosting.co.za>


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

Is this restricted to only the three OpenID providers like PyPI, Martin? If so then I think David's issue is he is not clicking the provider icons to make the association (or at least that's how I got it to work).

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

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

From metatracker at psf.upfronthosting.co.za  Sun Jan 17 10:18:41 2010
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v=2E_L=C3=B6wis?=)
Date: Sun, 17 Jan 2010 09:18:41 +0000
Subject: [Tracker-discuss] [issue314] OpenId Python tracker: associate gave
	opaque error message
In-Reply-To: <1263678710.47.0.199099744566.issue314@psf.upfronthosting.co.za>
Message-ID: <1263719921.44.0.174283043262.issue314@psf.upfronthosting.co.za>


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

No, any provider is accepted. The error david sees is the notification that roundup had crashed with an exception and that the traceback had been sent to me.
Unfortunately, I couldn't find a report that was sent around the time David wrote msg1508...

David, if the problem persists: can you please report what ID you tried to use?

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

From metatracker at psf.upfronthosting.co.za  Tue Jan 19 02:26:24 2010
From: metatracker at psf.upfronthosting.co.za (R David Murray)
Date: Tue, 19 Jan 2010 01:26:24 +0000
Subject: [Tracker-discuss] [issue314] OpenId Python tracker: associate gave
	opaque error message
In-Reply-To: <1263678710.47.0.199099744566.issue314@psf.upfronthosting.co.za>
Message-ID: <1263864384.96.0.697897391309.issue314@psf.upfronthosting.co.za>


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

Yes, it is still failing. The id is 'david.bitdance.com', which works fine at bitbucket.org.

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

From metatracker at psf.upfronthosting.co.za  Tue Jan 19 04:05:22 2010
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v=2E_L=C3=B6wis?=)
Date: Tue, 19 Jan 2010 03:05:22 +0000
Subject: [Tracker-discuss] [issue314] OpenId Python tracker: associate gave
	opaque error message
In-Reply-To: <1263678710.47.0.199099744566.issue314@psf.upfronthosting.co.za>
Message-ID: <1263870322.78.0.847402314998.issue314@psf.upfronthosting.co.za>


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

Thanks. I have now fixed some more bugs, please try again.

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

From metatracker at psf.upfronthosting.co.za  Tue Jan 19 13:24:55 2010
From: metatracker at psf.upfronthosting.co.za (R David Murray)
Date: Tue, 19 Jan 2010 12:24:55 +0000
Subject: [Tracker-discuss] [issue314] OpenId Python tracker: associate gave
	opaque error message
In-Reply-To: <1263678710.47.0.199099744566.issue314@psf.upfronthosting.co.za>
Message-ID: <1263903895.22.0.978800944884.issue314@psf.upfronthosting.co.za>


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

This time I got sent to my login page.  When I validated there, I got sent back to bugs.python.org, but it said authorization failed at the top.

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

From metatracker at psf.upfronthosting.co.za  Tue Jan 19 14:43:15 2010
From: metatracker at psf.upfronthosting.co.za (R David Murray)
Date: Tue, 19 Jan 2010 13:43:15 +0000
Subject: [Tracker-discuss] [issue314] OpenId Python tracker: associate gave
	opaque error message
In-Reply-To: <1263678710.47.0.199099744566.issue314@psf.upfronthosting.co.za>
Message-ID: <1263908595.59.0.351626358223.issue314@psf.upfronthosting.co.za>


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

Woops, not quite right.  It actually says:

Authentication failed: 

in red at the top.

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

From metatracker at psf.upfronthosting.co.za  Fri Jan 22 09:37:24 2010
From: metatracker at psf.upfronthosting.co.za (Amaury Forgeot d'Arc)
Date: Fri, 22 Jan 2010 08:37:24 +0000
Subject: [Tracker-discuss] [issue298] realname search should be case
	insensitive
In-Reply-To: <1253148331.7.0.788282669865.issue298@psf.upfronthosting.co.za>
Message-ID: <1264149444.3.0.397557043891.issue298@psf.upfronthosting.co.za>


Amaury Forgeot d'Arc <amauryfa at gmail.com> added the comment:

I just got the same issue.

----------
nosy: +amaury.forgeotdarc
status: unread -> chatting

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

From metatracker at psf.upfronthosting.co.za  Mon Jan 25 08:02:48 2010
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v=2E_L=C3=B6wis?=)
Date: Mon, 25 Jan 2010 07:02:48 +0000
Subject: [Tracker-discuss] [issue303] Exception when sending a ticket reply
	via email
In-Reply-To: <1255688821.53.0.717488738607.issue303@psf.upfronthosting.co.za>
Message-ID: <1264402968.11.0.487739689943.issue303@psf.upfronthosting.co.za>


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

Is that still an issue? I have no clue what might have been causing it, but I can't reproduce it right now.

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

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

From metatracker at psf.upfronthosting.co.za  Mon Jan 25 08:08:02 2010
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v=2E_L=C3=B6wis?=)
Date: Mon, 25 Jan 2010 07:08:02 +0000
Subject: [Tracker-discuss] [issue296] XSS vulnerability in ok_message
In-Reply-To: <1248205874.61.0.225589760626.issue296@psf.upfronthosting.co.za>
Message-ID: <1264403282.43.0.652999649319.issue296@psf.upfronthosting.co.za>


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

Not sure what "those messages" are that you want to remove altogether, but please notice that "they" probably also include error_message, which is a way to indicating an error to the user. I disagree that these should be considered annoying; they are fairly important indeed.

As to why they are in the URL: I still don't have an answer to that question. Anybody interested should probably investigate the source code, or ask on the roundup tracker.

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

From metatracker at psf.upfronthosting.co.za  Mon Jan 25 08:11:41 2010
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v=2E_L=C3=B6wis?=)
Date: Mon, 25 Jan 2010 07:11:41 +0000
Subject: [Tracker-discuss] [issue298] realname search should be case
	insensitive
In-Reply-To: <1253148331.7.0.788282669865.issue298@psf.upfronthosting.co.za>
Message-ID: <1264403501.87.0.382952111092.issue298@psf.upfronthosting.co.za>


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

In what field can you search for realname? AFAICT, roundup only supports searching for username.

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

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

From metatracker at psf.upfronthosting.co.za  Mon Jan 25 08:28:52 2010
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v=2E_L=C3=B6wis?=)
Date: Mon, 25 Jan 2010 07:28:52 +0000
Subject: [Tracker-discuss] [issue314] OpenId Python tracker: associate gave
	opaque error message
In-Reply-To: <1263678710.47.0.199099744566.issue314@psf.upfronthosting.co.za>
Message-ID: <1264404532.22.0.740324358065.issue314@psf.upfronthosting.co.za>


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

Please try once more: this time, the error message should include a traceback.

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

From metatracker at psf.upfronthosting.co.za  Mon Jan 25 09:18:21 2010
From: metatracker at psf.upfronthosting.co.za (Amaury Forgeot d'Arc)
Date: Mon, 25 Jan 2010 08:18:21 +0000
Subject: [Tracker-discuss] [issue298] realname search should be case
	insensitive
In-Reply-To: <1253148331.7.0.788282669865.issue298@psf.upfronthosting.co.za>
Message-ID: <1264407501.33.0.916808901016.issue298@psf.upfronthosting.co.za>


Amaury Forgeot d'Arc <amauryfa at gmail.com> added the comment:

Sorry, it's here:
http://bugs.python.org/user?@sort=username

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

From metatracker at psf.upfronthosting.co.za  Mon Jan 25 11:47:34 2010
From: metatracker at psf.upfronthosting.co.za (Ezio Melotti)
Date: Mon, 25 Jan 2010 10:47:34 +0000
Subject: [Tracker-discuss] [issue296] XSS vulnerability in ok_message
In-Reply-To: <1248205874.61.0.225589760626.issue296@psf.upfronthosting.co.za>
Message-ID: <1264416454.5.0.270486659401.issue296@psf.upfronthosting.co.za>


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

I meant "removing them from the URL". The messages should be written in the HTML directly without changing the URL.

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

From metatracker at psf.upfronthosting.co.za  Mon Jan 25 15:10:28 2010
From: metatracker at psf.upfronthosting.co.za (R David Murray)
Date: Mon, 25 Jan 2010 14:10:28 +0000
Subject: [Tracker-discuss] [issue296] XSS vulnerability in ok_message
In-Reply-To: <1248205874.61.0.225589760626.issue296@psf.upfronthosting.co.za>
Message-ID: <1264428628.15.0.692166661754.issue296@psf.upfronthosting.co.za>


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

My guess would be that the programmer put them in the URL in order to avoid the problem of someone pressing 'refesh' on the error page generating a re-submission of the form.  Doing this via a redirect to a URL avoids the resubmission problem without needing to get involved in session management (ie: staying RESTful).  However, whatever is passed in the URL should be sanitized before being displayed.  I haven't looked at the source either, so I don't know how complicated it would be to fix this, but if what is normally passed is only text, just escaping it before displaying it should be an almost trivial change.

And yeah, it would be nice to fix 'clear this message' to completely clear the URL, too.

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

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

From metatracker at psf.upfronthosting.co.za  Mon Jan 25 15:13:50 2010
From: metatracker at psf.upfronthosting.co.za (R David Murray)
Date: Mon, 25 Jan 2010 14:13:50 +0000
Subject: [Tracker-discuss] [issue314] OpenId Python tracker: associate gave
	opaque error message
In-Reply-To: <1263678710.47.0.199099744566.issue314@psf.upfronthosting.co.za>
Message-ID: <1264428830.39.0.717932704134.issue314@psf.upfronthosting.co.za>


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

Authentication failed: Traceback (most recent call last): File "/home/roundup/trackers/tracker/extensions/openid_login.py", line 156, in handle signed = openid.authenticate(session, query) File "/home/roundup/trackers/tracker/lib/openid.py", line 423, in authenticate raise ValueError('incorrect session') ValueError: incorrect session

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

From metatracker at psf.upfronthosting.co.za  Tue Jan 26 00:44:50 2010
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v=2E_L=C3=B6wis?=)
Date: Mon, 25 Jan 2010 23:44:50 +0000
Subject: [Tracker-discuss] [issue314] OpenId Python tracker: associate gave
	opaque error message
In-Reply-To: <1263678710.47.0.199099744566.issue314@psf.upfronthosting.co.za>
Message-ID: <1264463090.48.0.80721041996.issue314@psf.upfronthosting.co.za>


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

I think I have identified the problem - please try again.

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

From metatracker at psf.upfronthosting.co.za  Tue Jan 26 04:00:24 2010
From: metatracker at psf.upfronthosting.co.za (R David Murray)
Date: Tue, 26 Jan 2010 03:00:24 +0000
Subject: [Tracker-discuss] [issue314] OpenId Python tracker: associate gave
	opaque error message
In-Reply-To: <1263678710.47.0.199099744566.issue314@psf.upfronthosting.co.za>
Message-ID: <1264474824.69.0.0345953933778.issue314@psf.upfronthosting.co.za>


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

Well, the error changed :)

Authentication failed: incorrect session

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

From metatracker at psf.upfronthosting.co.za  Tue Jan 26 21:47:08 2010
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v=2E_L=C3=B6wis?=)
Date: Tue, 26 Jan 2010 20:47:08 +0000
Subject: [Tracker-discuss] [issue314] OpenId Python tracker: associate gave
	opaque error message
In-Reply-To: <1263678710.47.0.199099744566.issue314@psf.upfronthosting.co.za>
Message-ID: <1264538828.94.0.128114895393.issue314@psf.upfronthosting.co.za>


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

Please try once more.

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

From metatracker at psf.upfronthosting.co.za  Tue Jan 26 22:13:30 2010
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v=2E_L=C3=B6wis?=)
Date: Tue, 26 Jan 2010 21:13:30 +0000
Subject: [Tracker-discuss] [issue315] Upgrade Debian installation
In-Reply-To: <1264540410.57.0.767216150288.issue315@psf.upfronthosting.co.za>
Message-ID: <1264540410.57.0.767216150288.issue315@psf.upfronthosting.co.za>


New submission from Martin v. L?wis <martin at v.loewis.de>:

Security Support for Debian GNU/Linux 4.0 will be terminated on February 15th, according to www.debian.org. It would be good if we could upgrade the psf machine to lenny before that.

Is that something that Upfronthosting will do, or shall we do that?

----------
assignedto: izak
messages: 1527
nosy: izak, loewis, roche
priority: urgent
status: unread
title: Upgrade Debian installation

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

From metatracker at psf.upfronthosting.co.za  Wed Jan 27 03:08:47 2010
From: metatracker at psf.upfronthosting.co.za (R David Murray)
Date: Wed, 27 Jan 2010 02:08:47 +0000
Subject: [Tracker-discuss] [issue314] OpenId Python tracker: associate gave
	opaque error message
In-Reply-To: <1263678710.47.0.199099744566.issue314@psf.upfronthosting.co.za>
Message-ID: <1264558127.75.0.576315468645.issue314@psf.upfronthosting.co.za>


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

Excellent.  Worked this time.

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

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

From metatracker at psf.upfronthosting.co.za  Wed Jan 27 08:44:38 2010
From: metatracker at psf.upfronthosting.co.za (Izak Burger)
Date: Wed, 27 Jan 2010 07:44:38 +0000
Subject: [Tracker-discuss] [issue315] Upgrade Debian installation
In-Reply-To: <1264540410.57.0.767216150288.issue315@psf.upfronthosting.co.za>
Message-ID: <4B5FEFE9.1030905@upfrontsystems.co.za>


Izak Burger <izak at upfrontsystems.co.za> added the comment:

Hi all,

> Is that something that Upfronthosting will do, or shall we do that?

Yes, this sudden dropping of etch also caught us unawares. Its supposed 
to be as easy as running "apt-get dist-upgrade", but because there is 
sometimes breakage involved when dist-upgrading we plan to do this as 
follows: First we (upfront) will make a copy of the virtual server, and 
dist-upgrade that, making notes of anything that needs adjustment. We 
(upfront and psf) can then test that to make sure everything works. 
Finally we can schedule some downtime and do the dist-upgrade for real.

Let me know what you think.

regards,
Izak

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

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

From metatracker at psf.upfronthosting.co.za  Wed Jan 27 20:06:23 2010
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v=2E_L=C3=B6wis?=)
Date: Wed, 27 Jan 2010 19:06:23 +0000
Subject: [Tracker-discuss] [issue315] Upgrade Debian installation
In-Reply-To: <4B5FEFE9.1030905@upfrontsystems.co.za>
Message-ID: <4B608EAD.20706@v.loewis.de>


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

> Let me know what you think.

If that's how you would prefer to do it, it's fine with me. I would be
skeptical that everything can be tested, though, e.g. testing the email
setup might be tricky.

OTOH, on systems that I have to manage, I just accepted to the downtime
and the potential aftermath that it caused, so skipping the test upgrade
would be fine with with me as well.

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