From metatracker at psf.upfronthosting.co.za  Thu Apr  1 09:15:56 2010
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v=2E_L=C3=B6wis?=)
Date: Thu, 01 Apr 2010 07:15:56 +0000
Subject: [Tracker-discuss] [issue326] Postgres error: invalid page header ...
In-Reply-To: <1269420100.81.0.0570912412301.issue326@psf.upfronthosting.co.za>
Message-ID: <1270106156.04.0.504227415734.issue326@psf.upfronthosting.co.za>


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

I have now run a script that selects each _file record individually; this failed for 113 and 152. Some of them returned a NULL id (even though I selected them by id), namely 107, 116, 119, 126, 127, 10337. I have deleted all these records from the database; afterwards, pg_dump would create a dump of the table (I actually had to delete 119 from the dump instead). I dropped the table, and reloaded the dump.

Now I can create dumps of the entire postgres cluster.

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

From techtonik at gmail.com  Thu Apr  1 16:52:43 2010
From: techtonik at gmail.com (anatoly techtonik)
Date: Thu, 1 Apr 2010 17:52:43 +0300
Subject: [Tracker-discuss] http://bugs.python.org/issue2775
Message-ID: <g2wd34314101004010752gd9aed205n2f49e6136a602f54@mail.gmail.com>

Subj is offline. Page shows:
"An error has occurred

A problem was encountered processing your request. The tracker
maintainers have been notified of the problem."

Who was notified about the problem?
Is it still the problem with corrupted DB?
-- 
anatoly t.

From metatracker at psf.upfronthosting.co.za  Fri Apr  2 01:10:23 2010
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v=2E_L=C3=B6wis?=)
Date: Thu, 01 Apr 2010 23:10:23 +0000
Subject: [Tracker-discuss] [issue326] Postgres error: invalid page header ...
In-Reply-To: <1269420100.81.0.0570912412301.issue326@psf.upfronthosting.co.za>
Message-ID: <1270163423.14.0.913868633488.issue326@psf.upfronthosting.co.za>


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

Upfront has provided a backup from Feb 15. I have checked that none of the issues backed up at that point had been modified after after Feb 15. I have restored all missing _file entries to that point.

Attached is a list (file:ids1) of _file records that have been restored.

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue326>
_______________________________________________________
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ids
Type: application/octet-stream
Size: 593 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/tracker-discuss/attachments/20100401/04b72dae/attachment.obj>

From metatracker at psf.upfronthosting.co.za  Fri Apr  2 01:12:58 2010
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v=2E_L=C3=B6wis?=)
Date: Thu, 01 Apr 2010 23:12:58 +0000
Subject: [Tracker-discuss] [issue326] Postgres error: invalid page header ...
In-Reply-To: <1269420100.81.0.0570912412301.issue326@psf.upfronthosting.co.za>
Message-ID: <1270163578.04.0.845836186236.issue326@psf.upfronthosting.co.za>


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

Here is a list of file ids which are missing from range(16731): [0, 9109, 9110, 9184, 9278, 9347, 9375, 9376, 9377, 9378, 10156, 10157, 10158, 10159, 10160, 10161, 10162, 10163, 10164, 10165, 10166, 10167, 10168, 10169, 10295, 11287, 11294, 11825, 13128, 13340, 13341, 13342, 13343, 13344, 13345, 14084, 14209, 14898, 15500, 16149]

It would probably be useful to find out which of these are referenced from issues. I'll do that when I have time.

----------
assignedto: izak -> 

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

From metatracker at psf.upfronthosting.co.za  Fri Apr  2 01:13:30 2010
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v=2E_L=C3=B6wis?=)
Date: Thu, 01 Apr 2010 23:13:30 +0000
Subject: [Tracker-discuss] [issue327] Please provide backups
In-Reply-To: <1270015017.64.0.286941434615.issue327@psf.upfronthosting.co.za>
Message-ID: <1270163610.82.0.106077669595.issue327@psf.upfronthosting.co.za>


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

Gareth has now provided such backups.

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

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

From martin at v.loewis.de  Fri Apr  2 01:19:19 2010
From: martin at v.loewis.de (=?ISO-8859-1?Q?=22Martin_v=2E_L=F6wis=22?=)
Date: Fri, 02 Apr 2010 01:19:19 +0200
Subject: [Tracker-discuss] Problem with issue 1251
In-Reply-To: <l2pe04bdf311003301612l74fe252epa9d534cb68720c33@mail.gmail.com>
References: <l2pe04bdf311003301612l74fe252epa9d534cb68720c33@mail.gmail.com>
Message-ID: <4BB529F7.6010505@v.loewis.de>

Facundo Batista wrote:
> If you go to...
> 
>     http://bugs.python.org/issue1251
> 
> ...you get...
> 
> """
> An error has occurred
> 
> A problem was encountered processing your request. The tracker
> maintainers have been notified of the problem.
> """

Thanks for the report. This is now fixed.

Regards,
Martin


From martin at v.loewis.de  Fri Apr  2 01:17:33 2010
From: martin at v.loewis.de (=?ISO-8859-1?Q?=22Martin_v=2E_L=F6wis=22?=)
Date: Fri, 02 Apr 2010 01:17:33 +0200
Subject: [Tracker-discuss] http://bugs.python.org/issue2775
In-Reply-To: <g2wd34314101004010752gd9aed205n2f49e6136a602f54@mail.gmail.com>
References: <g2wd34314101004010752gd9aed205n2f49e6136a602f54@mail.gmail.com>
Message-ID: <4BB5298D.8070909@v.loewis.de>

> Who was notified about the problem?

Me.

> Is it still the problem with corrupted DB?

Yes. It is now fixed.

Regards,
Martin


From metatracker at psf.upfronthosting.co.za  Fri Apr  2 04:25:45 2010
From: metatracker at psf.upfronthosting.co.za (R David Murray)
Date: Fri, 02 Apr 2010 02:25:45 +0000
Subject: [Tracker-discuss] [issue274] Change Activity Summary dates to
	year-month-day format
In-Reply-To: <1240595270.96.0.454812708553.issue274@psf.upfronthosting.co.za>
Message-ID: <1270175145.99.0.015609940239.issue274@psf.upfronthosting.co.za>


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

This should be fixed for real now, I think.  (The patch had been committed but not installed).

----------
nosy: +r.david.murray
status:  -> resolved

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

From metatracker at psf.upfronthosting.co.za  Sat Apr  3 17:32:08 2010
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v=2E_L=C3=B6wis?=)
Date: Sat, 03 Apr 2010 15:32:08 +0000
Subject: [Tracker-discuss] [issue326] Postgres error: invalid page header ...
In-Reply-To: <1269420100.81.0.0570912412301.issue326@psf.upfronthosting.co.za>
Message-ID: <1270308728.63.0.332408778606.issue326@psf.upfronthosting.co.za>


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

None of these fileids are linked to issues, so it appears these ids really don't exist. Closing this as resolved.

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

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

From metatracker at psf.upfronthosting.co.za  Sun Apr  4 04:09:51 2010
From: metatracker at psf.upfronthosting.co.za (R David Murray)
Date: Sun, 04 Apr 2010 02:09:51 +0000
Subject: [Tracker-discuss] [issue326] Postgres error: invalid page header ...
In-Reply-To: <1269420100.81.0.0570912412301.issue326@psf.upfronthosting.co.za>
Message-ID: <1270346991.81.0.460986403548.issue326@psf.upfronthosting.co.za>


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

Interesting.  We just got a traceback email for one of them (13128), from an access by anonymous directly to the 'unnamed' file.  Looks related to some of the spam we get.

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

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

From metatracker at psf.upfronthosting.co.za  Sun Apr  4 09:26:25 2010
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v=2E_L=C3=B6wis?=)
Date: Sun, 04 Apr 2010 07:26:25 +0000
Subject: [Tracker-discuss] [issue326] Postgres error: invalid page header ...
In-Reply-To: <1269420100.81.0.0570912412301.issue326@psf.upfronthosting.co.za>
Message-ID: <1270365985.54.0.412516024926.issue326@psf.upfronthosting.co.za>


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

I think that's actually a roundup bug. If somebody accesses fileXXX/path, it shouldn't choke, but report http 404.

I checked the apache logs; the access to file13128/unnamed comes from Googlebot. Unfortunately, they don't provide a referer. I guess Googlebot will continue trying until they eventually get a proper result.

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

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

From metatracker at psf.upfronthosting.co.za  Sun Apr  4 20:13:45 2010
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v=2E_L=C3=B6wis?=)
Date: Sun, 04 Apr 2010 18:13:45 +0000
Subject: [Tracker-discuss] [issue326] Postgres error: invalid page header ...
In-Reply-To: <1269420100.81.0.0570912412301.issue326@psf.upfronthosting.co.za>
Message-ID: <1270404825.01.0.0536549795648.issue326@psf.upfronthosting.co.za>


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

I have now fixed the roundup bug with r79748 and r79749.

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

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

From techtonik at gmail.com  Tue Apr  6 11:21:42 2010
From: techtonik at gmail.com (anatoly techtonik)
Date: Tue, 6 Apr 2010 12:21:42 +0300
Subject: [Tracker-discuss] 'regression' type
Message-ID: <i2gd34314101004060221k5c622b23y6db333e53590a4b1@mail.gmail.com>

Are there any objections against introducing 'regression' type issues?
I need this for issue 6090
-- 
anatoly t.

From benjamin at python.org  Tue Apr  6 22:54:44 2010
From: benjamin at python.org (Benjamin Peterson)
Date: Tue, 6 Apr 2010 15:54:44 -0500
Subject: [Tracker-discuss] 'regression' type
In-Reply-To: <i2gd34314101004060221k5c622b23y6db333e53590a4b1@mail.gmail.com>
References: <i2gd34314101004060221k5c622b23y6db333e53590a4b1@mail.gmail.com>
Message-ID: <y2y1afaf6161004061354td1071e50pe15412243d72743a@mail.gmail.com>

2010/4/6 anatoly techtonik <techtonik at gmail.com>:
> Are there any objections against introducing 'regression' type issues?
> I need this for issue 6090

How do you think it would help?



-- 
Regards,
Benjamin

From techtonik at gmail.com  Tue Apr  6 22:59:33 2010
From: techtonik at gmail.com (anatoly techtonik)
Date: Tue, 6 Apr 2010 23:59:33 +0300
Subject: [Tracker-discuss] 'regression' type
In-Reply-To: <y2y1afaf6161004061354td1071e50pe15412243d72743a@mail.gmail.com>
References: <i2gd34314101004060221k5c622b23y6db333e53590a4b1@mail.gmail.com>
	<y2y1afaf6161004061354td1071e50pe15412243d72743a@mail.gmail.com>
Message-ID: <z2sd34314101004061359jbb5fa794s2af39c1b9dbbe85f@mail.gmail.com>

It will bring attention to delay 2.7 release.
-- 
anatoly t.



On Tue, Apr 6, 2010 at 11:54 PM, Benjamin Peterson <benjamin at python.org> wrote:
> 2010/4/6 anatoly techtonik <techtonik at gmail.com>:
>> Are there any objections against introducing 'regression' type issues?
>> I need this for issue 6090
>
> How do you think it would help?
>
>
>
> --
> Regards,
> Benjamin
>

From benjamin at python.org  Tue Apr  6 23:01:59 2010
From: benjamin at python.org (Benjamin Peterson)
Date: Tue, 6 Apr 2010 16:01:59 -0500
Subject: [Tracker-discuss] 'regression' type
In-Reply-To: <z2sd34314101004061359jbb5fa794s2af39c1b9dbbe85f@mail.gmail.com>
References: <i2gd34314101004060221k5c622b23y6db333e53590a4b1@mail.gmail.com>
	<y2y1afaf6161004061354td1071e50pe15412243d72743a@mail.gmail.com>
	<z2sd34314101004061359jbb5fa794s2af39c1b9dbbe85f@mail.gmail.com>
Message-ID: <s2m1afaf6161004061401xb51341b9xc676c63fea49b6c9@mail.gmail.com>

2010/4/6 anatoly techtonik <techtonik at gmail.com>:
> It will bring attention to delay 2.7 release.

We already have a priority for that.



-- 
Regards,
Benjamin

From techtonik at gmail.com  Tue Apr  6 23:19:12 2010
From: techtonik at gmail.com (anatoly techtonik)
Date: Wed, 7 Apr 2010 00:19:12 +0300
Subject: [Tracker-discuss] 'regression' type
In-Reply-To: <s2m1afaf6161004061401xb51341b9xc676c63fea49b6c9@mail.gmail.com>
References: <i2gd34314101004060221k5c622b23y6db333e53590a4b1@mail.gmail.com>
	<y2y1afaf6161004061354td1071e50pe15412243d72743a@mail.gmail.com>
	<z2sd34314101004061359jbb5fa794s2af39c1b9dbbe85f@mail.gmail.com>
	<s2m1afaf6161004061401xb51341b9xc676c63fea49b6c9@mail.gmail.com>
Message-ID: <r2jd34314101004061419sd0ee1e0aj433c9ef7f481ba6@mail.gmail.com>

On Wed, Apr 7, 2010 at 12:01 AM, Benjamin Peterson <benjamin at python.org> wrote:
>
>> It will bring attention to delay 2.7 release.
>
> We already have a priority for that.

Yes. But it can not be modified by users.
-- 
anatoly t.

From techtonik at gmail.com  Tue Apr  6 23:20:05 2010
From: techtonik at gmail.com (anatoly techtonik)
Date: Wed, 7 Apr 2010 00:20:05 +0300
Subject: [Tracker-discuss] 'regression' type
In-Reply-To: <s2m1afaf6161004061401xb51341b9xc676c63fea49b6c9@mail.gmail.com>
References: <i2gd34314101004060221k5c622b23y6db333e53590a4b1@mail.gmail.com>
	<y2y1afaf6161004061354td1071e50pe15412243d72743a@mail.gmail.com>
	<z2sd34314101004061359jbb5fa794s2af39c1b9dbbe85f@mail.gmail.com>
	<s2m1afaf6161004061401xb51341b9xc676c63fea49b6c9@mail.gmail.com>
Message-ID: <m2xd34314101004061420x98d03cfu8422880427811ff1@mail.gmail.com>

On Wed, Apr 7, 2010 at 12:01 AM, Benjamin Peterson <benjamin at python.org> wrote:
>
>> It will bring attention to delay 2.7 release.
>
> We already have a priority for that.

Yes. But it can not be specified/edited by reporters.
-- 
anatoly t.

From brett at python.org  Wed Apr  7 22:06:07 2010
From: brett at python.org (Brett Cannon)
Date: Wed, 7 Apr 2010 13:06:07 -0700
Subject: [Tracker-discuss] 'regression' type
In-Reply-To: <m2xd34314101004061420x98d03cfu8422880427811ff1@mail.gmail.com>
References: <i2gd34314101004060221k5c622b23y6db333e53590a4b1@mail.gmail.com> 
	<y2y1afaf6161004061354td1071e50pe15412243d72743a@mail.gmail.com> 
	<z2sd34314101004061359jbb5fa794s2af39c1b9dbbe85f@mail.gmail.com> 
	<s2m1afaf6161004061401xb51341b9xc676c63fea49b6c9@mail.gmail.com> 
	<m2xd34314101004061420x98d03cfu8422880427811ff1@mail.gmail.com>
Message-ID: <j2qbbaeab101004071306ved1013c9g986bf8b71ca344e2@mail.gmail.com>

On Tue, Apr 6, 2010 at 14:20, anatoly techtonik <techtonik at gmail.com> wrote:

> On Wed, Apr 7, 2010 at 12:01 AM, Benjamin Peterson <benjamin at python.org>
> wrote:
> >
> >> It will bring attention to delay 2.7 release.
> >
> > We already have a priority for that.
>
> Yes. But it can not be specified/edited by reporters.
>

That's on purpose. We have had issues in the past of reporters disagreeing
with how important an issue is and flipping the state to something else
*after* a core developer already changed the priority.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/tracker-discuss/attachments/20100407/e8b6987c/attachment.html>

From techtonik at gmail.com  Thu Apr  8 09:25:21 2010
From: techtonik at gmail.com (anatoly techtonik)
Date: Thu, 8 Apr 2010 10:25:21 +0300
Subject: [Tracker-discuss] 'regression' type
In-Reply-To: <j2qbbaeab101004071306ved1013c9g986bf8b71ca344e2@mail.gmail.com>
References: <i2gd34314101004060221k5c622b23y6db333e53590a4b1@mail.gmail.com>
	<y2y1afaf6161004061354td1071e50pe15412243d72743a@mail.gmail.com>
	<z2sd34314101004061359jbb5fa794s2af39c1b9dbbe85f@mail.gmail.com>
	<s2m1afaf6161004061401xb51341b9xc676c63fea49b6c9@mail.gmail.com>
	<m2xd34314101004061420x98d03cfu8422880427811ff1@mail.gmail.com>
	<j2qbbaeab101004071306ved1013c9g986bf8b71ca344e2@mail.gmail.com>
Message-ID: <w2gd34314101004080025jae3745b7h42c4bd3ad510e8d3@mail.gmail.com>

On Wed, Apr 7, 2010 at 11:06 PM, Brett Cannon <brett at python.org> wrote:
>> >
>> >> It will bring attention to delay 2.7 release.
>> >
>> > We already have a priority for that.
>>
>> Yes. But it can not be specified/edited by reporters.
>
> That's on purpose. We have had issues in the past of reporters disagreeing
> with how important an issue is and flipping the state to something else
> *after* a core developer already changed the priority.

I think it is a normal workflow. How else could people state that
issue is important for them? In Google there are stars, in Bugzilla -
votes. In other projects such as Trac there are 'priority' and
'severity'. The developers may schedule issue with priority, and user
editable severity may stay the same. If a person thinks that the issue
is 'critical' or a 'blocker' - that means this person is very
interested (or even very-very interested) in fixing the issue. All you
need is to show this person that his help is required and assist in
making a proper contribution.

This means:
1. help him to localize the problem, i.e.
http://wiki.winehq.org/RegressionTesting
2. explain him which code does he need to dig the problem
3. show where is this code located
4. explain how to setup dev environment
5. explain how to get test suite running easily
6. show an entrypoint to debug/fix cycle
7. show how to create a patch for review
8. show how to submit the patch
9. show how to refresh the patch easily for review

After a few 1-9 cycles you will be able to create a Python
Contribution Manual, similar or even better than
http://subversion.apache.org/docs/community-guide/   After some more
experience some steps could be automated or streamlined.


I am adding Richard to CC. He was eager to about means of improving
community outreach. So, here are entrypoints into development from bug
tracker. Not a single entrypoint, but several for appropriate user
level.
-- 
anatoly t.

From martin at v.loewis.de  Thu Apr  8 09:52:51 2010
From: martin at v.loewis.de (=?ISO-8859-1?Q?=22Martin_v=2E_L=F6wis=22?=)
Date: Thu, 08 Apr 2010 09:52:51 +0200
Subject: [Tracker-discuss] 'regression' type
In-Reply-To: <w2gd34314101004080025jae3745b7h42c4bd3ad510e8d3@mail.gmail.com>
References: <i2gd34314101004060221k5c622b23y6db333e53590a4b1@mail.gmail.com>	<y2y1afaf6161004061354td1071e50pe15412243d72743a@mail.gmail.com>	<z2sd34314101004061359jbb5fa794s2af39c1b9dbbe85f@mail.gmail.com>	<s2m1afaf6161004061401xb51341b9xc676c63fea49b6c9@mail.gmail.com>	<m2xd34314101004061420x98d03cfu8422880427811ff1@mail.gmail.com>	<j2qbbaeab101004071306ved1013c9g986bf8b71ca344e2@mail.gmail.com>
	<w2gd34314101004080025jae3745b7h42c4bd3ad510e8d3@mail.gmail.com>
Message-ID: <4BBD8B53.6020001@v.loewis.de>

> I think it is a normal workflow. How else could people state that
> issue is important for them? 

They can't, and that's a good thing, IMO. If they could state that
issues are important to them, they would have the expectation that these
things also get higher priority with the developers - however, the
developers have priorities that are completely unrelated to a specific
users needs. Then people get upset because the issues they reported as
urgent didn't get proper attention.

It is important that submitters understand that they submit bug reports
not to help them, but to help the Python community. A patch is a better
help than a bug report (typically), and a detailed bug report is a
better help than a fuzzy one.

If people need help themselves, they shouldn't post to the bug tracker.
Instead, they can post in mailing lists; if all else fails, they can
hire somebody to do the work for them.

> If a person thinks that the issue
> is 'critical' or a 'blocker' - that means this person is very
> interested (or even very-very interested) in fixing the issue.

Why is it important for the Python community to know that the bug is
urgent for the submitter? Typically, everybody sees their own bug report
as urgent.

> All you
> need is to show this person that his help is required and assist in
> making a proper contribution.

I typically post a message "do you want to provide a patch?" to indicate
to the submitter that this would be the best way to advance the issue.

> After a few 1-9 cycles you will be able to create a Python
> Contribution Manual, similar or even better than
> http://subversion.apache.org/docs/community-guide/

We have that already:

http://www.python.org/dev/
http://www.python.org/dev/intro/
http://www.python.org/dev/setup/
http://www.python.org/dev/workflow/
http://www.python.org/dev/contributing/

Regards,
Martin

From techtonik at gmail.com  Fri Apr  9 01:18:14 2010
From: techtonik at gmail.com (anatoly techtonik)
Date: Fri, 9 Apr 2010 02:18:14 +0300
Subject: [Tracker-discuss] improve version regexp
Message-ID: <i2hd34314101004081618zfb13033bwae24c45d92377209@mail.gmail.com>

http://bugs.python.org/msg102600

Version regexp or substitution could be improved.
-- 
anatoly t.

From martin at v.loewis.de  Fri Apr  9 01:21:58 2010
From: martin at v.loewis.de (=?ISO-8859-1?Q?=22Martin_v=2E_L=F6wis=22?=)
Date: Fri, 09 Apr 2010 01:21:58 +0200
Subject: [Tracker-discuss] improve version regexp
In-Reply-To: <i2hd34314101004081618zfb13033bwae24c45d92377209@mail.gmail.com>
References: <i2hd34314101004081618zfb13033bwae24c45d92377209@mail.gmail.com>
Message-ID: <4BBE6516.7060002@v.loewis.de>

anatoly techtonik wrote:
> http://bugs.python.org/msg102600
> 
> Version regexp or substitution could be improved.

I don't see this as an important bug, and fixing it would be difficult
(if you disagree, please provide a patch).

Regards,
Martin


From techtonik at gmail.com  Fri Apr  9 01:26:13 2010
From: techtonik at gmail.com (anatoly techtonik)
Date: Fri, 9 Apr 2010 02:26:13 +0300
Subject: [Tracker-discuss] improve version regexp
In-Reply-To: <4BBE6516.7060002@v.loewis.de>
References: <i2hd34314101004081618zfb13033bwae24c45d92377209@mail.gmail.com>
	<4BBE6516.7060002@v.loewis.de>
Message-ID: <s2vd34314101004081626r805c99e7mc8e08091068cf126@mail.gmail.com>

On Fri, Apr 9, 2010 at 2:21 AM, "Martin v. L?wis" <martin at v.loewis.de> wrote:
> anatoly techtonik wrote:
>> http://bugs.python.org/msg102600
>>
>> Version regexp or substitution could be improved.
>
> I don't see this as an important bug, and fixing it would be difficult
> (if you disagree, please provide a patch).

Where should I start?
-- 
anatoly t.

From martin at v.loewis.de  Fri Apr  9 01:35:17 2010
From: martin at v.loewis.de (=?UTF-8?B?Ik1hcnRpbiB2LiBMw7Z3aXMi?=)
Date: Fri, 09 Apr 2010 01:35:17 +0200
Subject: [Tracker-discuss] improve version regexp
In-Reply-To: <s2vd34314101004081626r805c99e7mc8e08091068cf126@mail.gmail.com>
References: <i2hd34314101004081618zfb13033bwae24c45d92377209@mail.gmail.com>	
	<4BBE6516.7060002@v.loewis.de>
	<s2vd34314101004081626r805c99e7mc8e08091068cf126@mail.gmail.com>
Message-ID: <4BBE6835.60706@v.loewis.de>

anatoly techtonik wrote:
> On Fri, Apr 9, 2010 at 2:21 AM, "Martin v. L?wis" <martin at v.loewis.de> wrote:
>> anatoly techtonik wrote:
>>> http://bugs.python.org/msg102600
>>>
>>> Version regexp or substitution could be improved.
>> I don't see this as an important bug, and fixing it would be difficult
>> (if you disagree, please provide a patch).
> 
> Where should I start?

My recommendation: drop this issue, and move to something more
important. If you absolutely want to work on this, start here:

https://svn.python.org/projects/tracker/

Regards,
Martin

From ajaksu at gmail.com  Fri Apr  9 01:47:47 2010
From: ajaksu at gmail.com (Daniel Diniz)
Date: Thu, 8 Apr 2010 20:47:47 -0300
Subject: [Tracker-discuss] improve version regexp
In-Reply-To: <s2vd34314101004081626r805c99e7mc8e08091068cf126@mail.gmail.com>
References: <i2hd34314101004081618zfb13033bwae24c45d92377209@mail.gmail.com> 
	<4BBE6516.7060002@v.loewis.de>
	<s2vd34314101004081626r805c99e7mc8e08091068cf126@mail.gmail.com>
Message-ID: <g2p2d75d7661004081647zd4900277o5d9d85b76a31b2f6@mail.gmail.com>

anatoly techtonik wrote:
> Where should I start?

IIUC, this is because http://bugs.python.org/version2 is valid, so the
code matches "class + id" first (and would do a lookup by name if it
were invalid). I believe the output code is in
roundup/cgi/templating.py->HTMLClass.getItem (around line 568).

But I agree with Martin, this seems very low priority.

How about we start a generic high-priority stuff thread? I think
learning and focusing on what the tracker maintainers, core devs and
release managers consider high priority has a better ROI than picking
small annoyances randomly.

Cheers,
Daniel

From martin at v.loewis.de  Fri Apr  9 01:52:02 2010
From: martin at v.loewis.de (=?UTF-8?B?Ik1hcnRpbiB2LiBMw7Z3aXMi?=)
Date: Fri, 09 Apr 2010 01:52:02 +0200
Subject: [Tracker-discuss] improve version regexp
In-Reply-To: <g2p2d75d7661004081647zd4900277o5d9d85b76a31b2f6@mail.gmail.com>
References: <i2hd34314101004081618zfb13033bwae24c45d92377209@mail.gmail.com>
	<4BBE6516.7060002@v.loewis.de>
	<s2vd34314101004081626r805c99e7mc8e08091068cf126@mail.gmail.com>
	<g2p2d75d7661004081647zd4900277o5d9d85b76a31b2f6@mail.gmail.com>
Message-ID: <4BBE6C22.3010502@v.loewis.de>

> How about we start a generic high-priority stuff thread? I think
> learning and focusing on what the tracker maintainers, core devs and
> release managers consider high priority has a better ROI than picking
> small annoyances randomly.

+1000

Martin

From techtonik at gmail.com  Fri Apr  9 12:20:14 2010
From: techtonik at gmail.com (anatoly techtonik)
Date: Fri, 9 Apr 2010 13:20:14 +0300
Subject: [Tracker-discuss] improve version regexp
In-Reply-To: <4BBE6C22.3010502@v.loewis.de>
References: <i2hd34314101004081618zfb13033bwae24c45d92377209@mail.gmail.com>
	<4BBE6516.7060002@v.loewis.de>
	<s2vd34314101004081626r805c99e7mc8e08091068cf126@mail.gmail.com>
	<g2p2d75d7661004081647zd4900277o5d9d85b76a31b2f6@mail.gmail.com>
	<4BBE6C22.3010502@v.loewis.de>
Message-ID: <g2ud34314101004090320vfe3d876dk6a70812e6b07a8c7@mail.gmail.com>

On Fri, Apr 9, 2010 at 2:52 AM, "Martin v. L?wis" <martin at v.loewis.de> wrote:
>> How about we start a generic high-priority stuff thread? I think
>> learning and focusing on what the tracker maintainers, core devs and
>> release managers consider high priority has a better ROI than picking
>> small annoyances randomly.
>
> +1000

Complexity of development business process incur wastes that increase
TCO to a degree that there is no ROI at all.

I prefer do things that reduce time waste. Right now my focus in on
enhancing pydotorg community outreach. While I'm waiting for decision
to join redundant lists and for acknowledgement of "pydotorg" brand,
it is impossible for me to take anything more major than small
annoyances.

-- 
anatoly t.

From georg at python.org  Sat Apr 10 20:17:17 2010
From: georg at python.org (Georg Brandl)
Date: Sat, 10 Apr 2010 20:17:17 +0200
Subject: [Tracker-discuss] 'regression' type
In-Reply-To: <w2gd34314101004080025jae3745b7h42c4bd3ad510e8d3@mail.gmail.com>
References: <i2gd34314101004060221k5c622b23y6db333e53590a4b1@mail.gmail.com>	<y2y1afaf6161004061354td1071e50pe15412243d72743a@mail.gmail.com>	<z2sd34314101004061359jbb5fa794s2af39c1b9dbbe85f@mail.gmail.com>	<s2m1afaf6161004061401xb51341b9xc676c63fea49b6c9@mail.gmail.com>	<m2xd34314101004061420x98d03cfu8422880427811ff1@mail.gmail.com>	<j2qbbaeab101004071306ved1013c9g986bf8b71ca344e2@mail.gmail.com>
	<w2gd34314101004080025jae3745b7h42c4bd3ad510e8d3@mail.gmail.com>
Message-ID: <4BC0C0AD.5070708@python.org>

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

Am 08.04.2010 09:25, schrieb anatoly techtonik:

>> That's on purpose. We have had issues in the past of reporters disagreeing
>> with how important an issue is and flipping the state to something else
>> *after* a core developer already changed the priority.
> 
> I think it is a normal workflow. How else could people state that
> issue is important for them? In Google there are stars, in Bugzilla -
> votes. In other projects such as Trac there are 'priority' and
> 'severity'.

Sorry, but I think you're mixing up concepts here.  I agree with Martin
(and Brett) that it needs to be reserved to developers (which is not the
same set as committers; it includes all those with sufficient tracker
privileges) to determine and set the priority of an issue.  It is
sometimes annoying enough that users can reopen an issue (but most of the
time, it makes sense that they can.)

Voting for bugs (or starring, or the "affects me too" in Launchpad) is
different.  Sure, the number of affected people can be an indication of
a bug's priority, but an often-run-into annoyance remains an annoyance.
I would not be opposed to introducing voting for bugs, but I don't think
it is necessary; interested users can leave a comment, which is often
better since they can add useful information.

> The developers may schedule issue with priority, and user
> editable severity may stay the same. If a person thinks that the issue
> is 'critical' or a 'blocker' - that means this person is very
> interested (or even very-very interested) in fixing the issue. All you
> need is to show this person that his help is required and assist in
> making a proper contribution.

That still doesn't make it a release blocker.  Quite the opposite -- for
example if the bug reported completely prevents using Python on an obscure,
maybe unsupported platform, it is certainly a blocker for the reporter,
but we certainly wouldn't consider holding up a release because of it.
he same holds for the very particular feature request that a user needs
desperately to write his application.

> This means:
> 1. help him to localize the problem, i.e.
> http://wiki.winehq.org/RegressionTesting
> 2. explain him which code does he need to dig the problem
> 3. show where is this code located
> 4. explain how to setup dev environment
> 5. explain how to get test suite running easily
> 6. show an entrypoint to debug/fix cycle
> 7. show how to create a patch for review
> 8. show how to submit the patch
> 9. show how to refresh the patch easily for review
> 
> After a few 1-9 cycles you will be able to create a Python
> Contribution Manual, similar or even better than
> http://subversion.apache.org/docs/community-guide/   After some more
> experience some steps could be automated or streamlined.

As pointed out, we have these guides.  It should be a simple step to add
the pertinent links to tracker pages.

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

iEYEARECAAYFAkvAwKwACgkQN9GcIYhpnLD0PQCfQtarzeIrxeuY1PCViOppD7Zd
rhsAnArTpkOJFNnRz698E4cp98zsBNUY
=yExD
-----END PGP SIGNATURE-----

From metatracker at psf.upfronthosting.co.za  Sun Apr 11 04:07:37 2010
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?=C3=89ric_Araujo?=)
Date: Sun, 11 Apr 2010 02:07:37 +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: <1270951657.07.0.0487138824186.issue241@psf.upfronthosting.co.za>


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

Hello

Magic! http://bugs.python.org/stage2

Regards

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

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

From metatracker at psf.upfronthosting.co.za  Sun Apr 11 07:42:06 2010
From: metatracker at psf.upfronthosting.co.za (techtonik)
Date: Sun, 11 Apr 2010 05:42:06 +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: <1270964526.31.0.980772961611.issue241@psf.upfronthosting.co.za>


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

What if really a 'test case' with a proof of concept and not `unit test` is needed?

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

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

From metatracker at psf.upfronthosting.co.za  Sun Apr 11 09:28:20 2010
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v=2E_L=C3=B6wis?=)
Date: Sun, 11 Apr 2010 07:28:20 +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: <1270970900.66.0.0633212085882.issue241@psf.upfronthosting.co.za>


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

I have now renamed the stage.

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

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

From chris.jerdonek at gmail.com  Tue Apr 13 22:19:18 2010
From: chris.jerdonek at gmail.com (Chris Jerdonek)
Date: Tue, 13 Apr 2010 13:19:18 -0700
Subject: [Tracker-discuss] request for developer privileges
Message-ID: <w2ndacc8d1a1004131319k1fb6b925g1236c3ca638cd5a6@mail.gmail.com>

Hi, I'm writing to request developer privileges in Tracker.  Recently,
I've been working on these two issues:

http://bugs.python.org/issue7559
http://bugs.python.org/issue8370

I would like to move them to "patch review".

Thanks,
--Chris

From ajaksu at gmail.com  Tue Apr 13 23:27:23 2010
From: ajaksu at gmail.com (Daniel Diniz)
Date: Tue, 13 Apr 2010 18:27:23 -0300
Subject: [Tracker-discuss] request for developer privileges
In-Reply-To: <w2ndacc8d1a1004131319k1fb6b925g1236c3ca638cd5a6@mail.gmail.com>
References: <w2ndacc8d1a1004131319k1fb6b925g1236c3ca638cd5a6@mail.gmail.com>
Message-ID: <k2s2d75d7661004131427i38d8dedbl362cdf469e2ac155@mail.gmail.com>

Hi Chris,

I've updated the issues for now. I assume you're interested in being
able to update and triage issues so you can help move tickets forward
in general, if so I'm +1 on you getting developer access. Until you
get it, let us know if you want given issues to be updated for you.

Cheers,
Daniel

From chris.jerdonek at gmail.com  Wed Apr 14 00:40:10 2010
From: chris.jerdonek at gmail.com (Chris Jerdonek)
Date: Tue, 13 Apr 2010 15:40:10 -0700
Subject: [Tracker-discuss] request for developer privileges
In-Reply-To: <k2s2d75d7661004131427i38d8dedbl362cdf469e2ac155@mail.gmail.com>
References: <w2ndacc8d1a1004131319k1fb6b925g1236c3ca638cd5a6@mail.gmail.com>
	<k2s2d75d7661004131427i38d8dedbl362cdf469e2ac155@mail.gmail.com>
Message-ID: <o2tdacc8d1a1004131540od9c9287cldd4b007900c099f4@mail.gmail.com>

On Tue, Apr 13, 2010 at 2:27 PM, Daniel Diniz <ajaksu at gmail.com> wrote:
> I've updated the issues for now. I assume you're interested in being
> able to update and triage issues so you can help move tickets forward
> in general, if so I'm +1 on you getting developer access.

Thanks a lot, Daniel.  I see you even updated a third issue I was
involved in that I didn't mention in my e-mail to tracker-discuss.
And yes, you are correct in that I'm interested in helping in general
for triage purposes, etc.

--Chris

From martin at v.loewis.de  Wed Apr 14 01:01:40 2010
From: martin at v.loewis.de (=?ISO-8859-1?Q?=22Martin_v=2E_L=F6wis=22?=)
Date: Wed, 14 Apr 2010 01:01:40 +0200
Subject: [Tracker-discuss] request for developer privileges
In-Reply-To: <w2ndacc8d1a1004131319k1fb6b925g1236c3ca638cd5a6@mail.gmail.com>
References: <w2ndacc8d1a1004131319k1fb6b925g1236c3ca638cd5a6@mail.gmail.com>
Message-ID: <4BC4F7D4.2030708@v.loewis.de>

> Hi, I'm writing to request developer privileges in Tracker.

I have given you the Developer role now. Please understand that setting
the state of an issue to "review" may *not* be the best way to trigger a
review - it may be more effective to post to python-dev if you truly
believe that the patch can be committed as-is.

Regards,
Martin

From chris.jerdonek at gmail.com  Wed Apr 14 01:15:10 2010
From: chris.jerdonek at gmail.com (Chris Jerdonek)
Date: Tue, 13 Apr 2010 16:15:10 -0700
Subject: [Tracker-discuss] request for developer privileges
In-Reply-To: <4BC4F7D4.2030708@v.loewis.de>
References: <w2ndacc8d1a1004131319k1fb6b925g1236c3ca638cd5a6@mail.gmail.com>
	<4BC4F7D4.2030708@v.loewis.de>
Message-ID: <p2wdacc8d1a1004131615z54a54932m7fa1ac455205b631@mail.gmail.com>

On Tue, Apr 13, 2010 at 4:01 PM, "Martin v. L?wis" <martin at v.loewis.de> wrote:
> I have given you the Developer role now. Please understand that setting
> the state of an issue to "review" may *not* be the best way to trigger a
> review - it may be more effective to post to python-dev if you truly
> believe that the patch can be committed as-is.

Thanks, Martin.  I had thought python-dev was to be used more for
higher-level discussions, but I will take your suggestion into account
going forward.

One question regarding this:

Are you suggesting that in some cases it may be better to post to
python-dev instead of setting an issue to review, or in addition to
setting it to review?

--Chris

From martin at v.loewis.de  Wed Apr 14 01:27:58 2010
From: martin at v.loewis.de (=?ISO-8859-1?Q?=22Martin_v=2E_L=F6wis=22?=)
Date: Wed, 14 Apr 2010 01:27:58 +0200
Subject: [Tracker-discuss] request for developer privileges
In-Reply-To: <p2wdacc8d1a1004131615z54a54932m7fa1ac455205b631@mail.gmail.com>
References: <w2ndacc8d1a1004131319k1fb6b925g1236c3ca638cd5a6@mail.gmail.com>	
	<4BC4F7D4.2030708@v.loewis.de>
	<p2wdacc8d1a1004131615z54a54932m7fa1ac455205b631@mail.gmail.com>
Message-ID: <4BC4FDFE.3030504@v.loewis.de>

> Are you suggesting that in some cases it may be better to post to
> python-dev instead of setting an issue to review, or in addition to
> setting it to review?

If you can (as you do now), both is certainly fine. Contributors who
can't edit the status should definitely post.

All kinds of things are discussed on python-dev. Posting about open
issues, proposed patches etc. is certainly on-topic.

The only thing that people dislike is a "pushy" attitude that
contributors sometimes show wrt. their patches ("I have this patch
posted already four days agos, and you bozos still haven't committed it").

Regards,
Martin

From metatracker at psf.upfronthosting.co.za  Wed Apr 14 07:45:28 2010
From: metatracker at psf.upfronthosting.co.za (sypper-pit)
Date: Wed, 14 Apr 2010 05:45:28 +0000
Subject: [Tracker-discuss] [issue331] python-ad
In-Reply-To: <1271223928.82.0.935759628608.issue331@psf.upfronthosting.co.za>
Message-ID: <1271223928.82.0.935759628608.issue331@psf.upfronthosting.co.za>


New submission from sypper-pit <sypper.pit at gmail.com>:

###########hi, if i'm start easy_install
############___________
#easy_install -U python_ad
Searching for python-ad
Reading http://pypi.python.org/simple/python_ad/
Reading http://www.boskant.nl/trac/python-ad
Download error: [Errno 8] hostname nor servname provided, or not known -- Some packages may not be found!
Reading http://code.google.com/p/python-ad
Best match: python-ad 0.9
Processing python_ad-0.9-py2.6-freebsd-7.3-RELEASE-i386.egg
python-ad 0.9 is already the active version in easy-install.pth
____________

########system not work for update:
########____________

# This file is part of Python-AD. Python-AD is free software that is made
# available under the MIT license. Consult the file "LICENSE" that is
# distributed together with this file for the exact licensing terms.
#
# Python-AD is copyright (c) 2007 by the Python-AD authors. See the file
# "AUTHORS" for a complete overview.

from setuptools import setup, Extension

setup(
    name = 'python-ad',
    version = '0.9',
    description = 'An AD client library for Python',
    author = 'Geert Jansen',
    author_email = 'geert at boskant.nl',
    url = 'http://code.google.com/p/python-ad',
    license = 'MIT',
    classifiers = ['Development Status :: 4 - Beta',
        'Intended Audience :: Developers',
        'License :: OSI Approved :: MIT License',
        'Programming Language :: Python'],
    package_dir = {'': 'lib'},
    packages = ['ad', 'ad.core', 'ad.protocol', 'ad.util'],
    ext_modules = [Extension('ad.protocol.krb5', ['lib/ad/protocol/krb5.c'],
                             libraries=['krb5'])],
    test_suite = 'nose.collector'
)

----------
messages: 1643
nosy: pit
priority: urgent
status: deferred
title: python-ad

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

From metatracker at psf.upfronthosting.co.za  Wed Apr 14 08:35:00 2010
From: metatracker at psf.upfronthosting.co.za (sypper-pit)
Date: Wed, 14 Apr 2010 06:35:00 +0000
Subject: [Tracker-discuss] [issue332] python_ad
In-Reply-To: <1271226900.58.0.634485005841.issue332@psf.upfronthosting.co.za>
Message-ID: <1271226900.58.0.634485005841.issue332@psf.upfronthosting.co.za>


New submission from sypper-pit <sypper.pit at gmail.com>:

test# python setup.py test
running test
running egg_info
writing lib/python_ad.egg-info/PKG-INFO
writing top-level names to lib/python_ad.egg-info/top_level.txt
writing dependency_links to lib/python_ad.egg-info/dependency_links.txt
reading manifest file 'lib/python_ad.egg-info/SOURCES.txt'
reading manifest template 'MANIFEST.in'
writing manifest file 'lib/python_ad.egg-info/SOURCES.txt'
running build_ext
copying build/lib.freebsd-7.3-RELEASE-i386-2.6/ad/protocol/krb5.so -> lib/ad/protocol
Failure: ImportError (/usr/home/pit/python-ad-0.9/lib/ad/protocol/krb5.so: Undefined symbol "krb5_cc_copy_creds") ... ERROR

======================================================================
ERROR: Failure: ImportError (/usr/home/pit/python-ad-0.9/lib/ad/protocol/krb5.so: Undefined symbol "krb5_cc_copy_creds")
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/usr/local/lib/python2.6/site-packages/nose-0.11.3-py2.6.egg/nose/loader.py", line 382, in loadTestsFromName
    addr.filename, addr.module)
  File "/usr/local/lib/python2.6/site-packages/nose-0.11.3-py2.6.egg/nose/importer.py", line 39, in importFromPath
    return self.importFromDir(dir_path, fqname)
  File "/usr/local/lib/python2.6/site-packages/nose-0.11.3-py2.6.egg/nose/importer.py", line 86, in importFromDir
    mod = load_module(part_fqname, fh, filename, desc)
  File "/usr/home/pit/python-ad-0.9/lib/ad/__init__.py", line 12, in <module>
    from ad.core.client import Client
  File "/usr/home/pit/python-ad-0.9/lib/ad/core/client.py", line 20, in <module>
    from ad.core.creds import Creds
  File "/usr/home/pit/python-ad-0.9/lib/ad/core/creds.py", line 17, in <module>
    from ad.protocol import krb5
ImportError: /usr/home/pit/python-ad-0.9/lib/ad/protocol/krb5.so: Undefined symbol "krb5_cc_copy_creds"

----------------------------------------------------------------------
Ran 1 test in 0.047s

FAILED (errors=1)
test# python
Python 2.6.4 (r264:75706, Apr  6 2010, 19:23:58) 
[GCC 4.2.1 20070719  [FreeBSD]] on freebsd7
Type "help", "copyright", "credits" or "license" for more information.
>>> import ad
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "build/bdist.freebsd-7.3-RELEASE-i386/egg/ad/__init__.py", line 12, in <module>
  File "build/bdist.freebsd-7.3-RELEASE-i386/egg/ad/core/client.py", line 20, in <module>
  File "build/bdist.freebsd-7.3-RELEASE-i386/egg/ad/core/creds.py", line 17, in <module>
  File "build/bdist.freebsd-7.3-RELEASE-i386/egg/ad/protocol/krb5.py", line 7, in <module>
  File "build/bdist.freebsd-7.3-RELEASE-i386/egg/ad/protocol/krb5.py", line 6, in __bootstrap__
ImportError: /root/.python-eggs/python_ad-0.9-py2.6-freebsd-7.3-RELEASE-i386.egg-tmp/ad/protocol/krb5.so: Undefined symbol "krb5_cc_copy_creds"

----------
messages: 1644
nosy: pit
priority: critical
status: unread
title: python_ad

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

From metatracker at psf.upfronthosting.co.za  Wed Apr 14 10:41:21 2010
From: metatracker at psf.upfronthosting.co.za (Georg Brandl)
Date: Wed, 14 Apr 2010 08:41:21 +0000
Subject: [Tracker-discuss] [issue331] python-ad
In-Reply-To: <1271223928.82.0.935759628608.issue331@psf.upfronthosting.co.za>
Message-ID: <1271234481.29.0.651868901808.issue331@psf.upfronthosting.co.za>


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

This is not a tracker to deal with setuptools problems.

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

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

From metatracker at psf.upfronthosting.co.za  Wed Apr 14 10:41:42 2010
From: metatracker at psf.upfronthosting.co.za (Georg Brandl)
Date: Wed, 14 Apr 2010 08:41:42 +0000
Subject: [Tracker-discuss] [issue332] python_ad
In-Reply-To: <1271226900.58.0.634485005841.issue332@psf.upfronthosting.co.za>
Message-ID: <1271234502.98.0.570826469374.issue332@psf.upfronthosting.co.za>


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

This is not a tracker to deal with setuptools/distutils problems.

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

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

From metatracker at psf.upfronthosting.co.za  Wed Apr 14 14:14:01 2010
From: metatracker at psf.upfronthosting.co.za (techtonik)
Date: Wed, 14 Apr 2010 12:14:01 +0000
Subject: [Tracker-discuss] [issue333] preserve search form value
In-Reply-To: <1271247241.53.0.197724027841.issue333@psf.upfronthosting.co.za>
Message-ID: <1271247241.53.0.197724027841.issue333@psf.upfronthosting.co.za>


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

Search string entered in top right search form is not preserved. It should be preserved to allow fast switching between search of open vs closed issues.

----------
messages: 1647
nosy: techtonik
priority: bug
status: unread
title: preserve search form value

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

From metatracker at psf.upfronthosting.co.za  Wed Apr 14 15:41:15 2010
From: metatracker at psf.upfronthosting.co.za (Ezio Melotti)
Date: Wed, 14 Apr 2010 13:41:15 +0000
Subject: [Tracker-discuss] [issue333] preserve search form value
In-Reply-To: <1271247241.53.0.197724027841.issue333@psf.upfronthosting.co.za>
Message-ID: <1271252475.57.0.506547159789.issue333@psf.upfronthosting.co.za>


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

Sounds like a good idea to me.

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

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

From metatracker at psf.upfronthosting.co.za  Wed Apr 14 16:39:35 2010
From: metatracker at psf.upfronthosting.co.za (sypper-pit)
Date: Wed, 14 Apr 2010 14:39:35 +0000
Subject: [Tracker-discuss] [issue332] python_ad
In-Reply-To: <1271234502.98.0.570826469374.issue332@psf.upfronthosting.co.za>
Message-ID: <j2sd782fd311004140739mb72a4d85m7fc7057393391ae5@mail.gmail.com>


sypper-pit <sypper.pit at gmail.com> added the comment:

ok, now i know. god lack

2010/4/14 Georg Brandl <metatracker at psf.upfronthosting.co.za>

>
> Georg Brandl <g.brandl at gmx.net> added the comment:
>
> This is not a tracker to deal with setuptools/distutils problems.
>
> ----------
> nosy: +gbrandl
> status: unread -> resolved
>
> _______________________________________________________
> PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
> <http://psf.upfronthosting.co.za/roundup/meta/issue332>
> _______________________________________________________
>

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

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

From metatracker at psf.upfronthosting.co.za  Wed Apr 14 21:45:18 2010
From: metatracker at psf.upfronthosting.co.za (techtonik)
Date: Wed, 14 Apr 2010 19:45:18 +0000
Subject: [Tracker-discuss] [issue334] remote bug watchers
In-Reply-To: <1271274318.29.0.317511707543.issue334@psf.upfronthosting.co.za>
Message-ID: <1271274318.29.0.317511707543.issue334@psf.upfronthosting.co.za>


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

It would be nice if bugs.python.org can monitor bugs in other trackers that are affected by Python issues. Like in Launchpad - https://bugs.edge.launchpad.net/dulwich/+bug/557585 - see the right column with link to Twisted Trac sucked in automatically.

----------
messages: 1650
nosy: techtonik
priority: feature
status: unread
title: remote bug watchers

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

From techtonik at gmail.com  Sat Apr 17 21:52:00 2010
From: techtonik at gmail.com (anatoly techtonik)
Date: Sat, 17 Apr 2010 22:52:00 +0300
Subject: [Tracker-discuss] Roundup 1.4.13 security upgrade
Message-ID: <r2ud34314101004171252j8db01609ub6c533c2be4cb350@mail.gmail.com>

Hello,

I see that the current Roundup version on `pydotorg` is 1.4.10, but
the latest available is 1.4.13

http://pypi.python.org/pypi/roundup/1.4.11 contains a number of fixes.
Among them a security issue about user permission escalation.
http://pypi.python.org/pypi/roundup/1.4.12 has even more changes.
http://pypi.python.org/pypi/roundup/1.4.13 is a regression bugfix release.

-- 
anatoly t.

From metatracker at psf.upfronthosting.co.za  Sat Apr 24 14:15:42 2010
From: metatracker at psf.upfronthosting.co.za (techtonik)
Date: Sat, 24 Apr 2010 12:15:42 +0000
Subject: [Tracker-discuss] [issue335] "out of date" resolution on open issue
In-Reply-To: <1272111342.82.0.249947227102.issue335@psf.upfronthosting.co.za>
Message-ID: <1272111342.82.0.249947227102.issue335@psf.upfronthosting.co.za>


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

There is an "out of date" resolution on opened issue that was not removed when an issue was reopened. Can anybody fix that? 
http://bugs.python.org/issue3341

And also fix tracker.

----------
messages: 1651
nosy: techtonik
priority: bug
status: unread
title: "out of date" resolution on open issue

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

From techtonik at gmail.com  Sat Apr 24 18:01:38 2010
From: techtonik at gmail.com (anatoly techtonik)
Date: Sat, 24 Apr 2010 19:01:38 +0300
Subject: [Tracker-discuss] Are docs@python.org subscribed to tracker
	notifications
Message-ID: <k2pd34314101004240901q5550dad8l6ffc33c1672f556b@mail.gmail.com>

Hi,

Are docs at python.org subscribed to tracker notifications?
The mailing list is closed to check.

Please, CC.
-- 
anatoly t.

From georg at python.org  Sat Apr 24 18:16:42 2010
From: georg at python.org (Georg Brandl)
Date: Sat, 24 Apr 2010 18:16:42 +0200
Subject: [Tracker-discuss] Are docs@python.org subscribed to
	tracker	notifications
In-Reply-To: <k2pd34314101004240901q5550dad8l6ffc33c1672f556b@mail.gmail.com>
References: <k2pd34314101004240901q5550dad8l6ffc33c1672f556b@mail.gmail.com>
Message-ID: <4BD3196A.4060408@python.org>

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

Am 24.04.2010 18:01, schrieb anatoly techtonik:
> Hi,
> 
> Are docs at python.org subscribed to tracker notifications?
> The mailing list is closed to check.

Why should the docs list be subscribed to tracker notifications?
We have the bugs list for that.

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

iEYEARECAAYFAkvTGWkACgkQN9GcIYhpnLDoqwCfS7ok6naw4bLy704dFHaquE/U
RkgAn3j4vh5+UeBfLlzaFHrwIZBu4G9j
=ZA/6
-----END PGP SIGNATURE-----

From techtonik at gmail.com  Sat Apr 24 18:51:36 2010
From: techtonik at gmail.com (anatoly techtonik)
Date: Sat, 24 Apr 2010 19:51:36 +0300
Subject: [Tracker-discuss] Are docs@python.org subscribed to tracker
	notifications
In-Reply-To: <4BD3196A.4060408@python.org>
References: <k2pd34314101004240901q5550dad8l6ffc33c1672f556b@mail.gmail.com>
	<4BD3196A.4060408@python.org>
Message-ID: <r2ld34314101004240951x52d71d41k70391b009d4765a5@mail.gmail.com>

On Sat, Apr 24, 2010 at 7:16 PM, Georg Brandl <georg at python.org> wrote:
>> Hi,
>>
>> Are docs at python.org subscribed to tracker notifications?
>> The mailing list is closed to check.
>
> Why should the docs list be subscribed to tracker notifications?
> We have the bugs list for that.

Pardon me. Rephrasing the question..

Are docs at python.org subscribed to tracker notifications for
Documentation component?

-- 
anatoly t.

From benjamin at python.org  Sat Apr 24 18:53:22 2010
From: benjamin at python.org (Benjamin Peterson)
Date: Sat, 24 Apr 2010 11:53:22 -0500
Subject: [Tracker-discuss] Are docs@python.org subscribed to tracker
	notifications
In-Reply-To: <r2ld34314101004240951x52d71d41k70391b009d4765a5@mail.gmail.com>
References: <k2pd34314101004240901q5550dad8l6ffc33c1672f556b@mail.gmail.com>
	<4BD3196A.4060408@python.org>
	<r2ld34314101004240951x52d71d41k70391b009d4765a5@mail.gmail.com>
Message-ID: <p2k1afaf6161004240953td480a58co26bff96d2cee9392@mail.gmail.com>

2010/4/24 anatoly techtonik <techtonik at gmail.com>:
> On Sat, Apr 24, 2010 at 7:16 PM, Georg Brandl <georg at python.org> wrote:
>>> Hi,
>>>
>>> Are docs at python.org subscribed to tracker notifications?
>>> The mailing list is closed to check.
>>
>> Why should the docs list be subscribed to tracker notifications?
>> We have the bugs list for that.
>
> Pardon me. Rephrasing the question..
>
> Are docs at python.org subscribed to tracker notifications for
> Documentation component?

No, why should they?



-- 
Regards,
Benjamin

From techtonik at gmail.com  Sat Apr 24 18:56:25 2010
From: techtonik at gmail.com (anatoly techtonik)
Date: Sat, 24 Apr 2010 19:56:25 +0300
Subject: [Tracker-discuss] Are docs@python.org subscribed to tracker
	notifications
In-Reply-To: <p2k1afaf6161004240953td480a58co26bff96d2cee9392@mail.gmail.com>
References: <k2pd34314101004240901q5550dad8l6ffc33c1672f556b@mail.gmail.com>
	<4BD3196A.4060408@python.org>
	<r2ld34314101004240951x52d71d41k70391b009d4765a5@mail.gmail.com>
	<p2k1afaf6161004240953td480a58co26bff96d2cee9392@mail.gmail.com>
Message-ID: <l2yd34314101004240956y763e8c0cs1e60953b8e8cef02@mail.gmail.com>

On Sat, Apr 24, 2010 at 7:53 PM, Benjamin Peterson <benjamin at python.org> wrote:
>>>>
>>>> Are docs at python.org subscribed to tracker notifications?
>>>> The mailing list is closed to check.
>>>
>>> Why should the docs list be subscribed to tracker notifications?
>>> We have the bugs list for that.
>>
>> Pardon me. Rephrasing the question..
>>
>> Are docs at python.org subscribed to tracker notifications for
>> Documentation component?
>
> No, why should they?

Then volunteers may subscribe to receive notification about
Documentation issues. They do not have any other means otherwise.

-- 
anatoly t.

From georg at python.org  Sat Apr 24 19:11:13 2010
From: georg at python.org (Georg Brandl)
Date: Sat, 24 Apr 2010 19:11:13 +0200
Subject: [Tracker-discuss] Are docs@python.org subscribed to tracker
 notifications
In-Reply-To: <l2yd34314101004240956y763e8c0cs1e60953b8e8cef02@mail.gmail.com>
References: <k2pd34314101004240901q5550dad8l6ffc33c1672f556b@mail.gmail.com>	
	<4BD3196A.4060408@python.org>	
	<r2ld34314101004240951x52d71d41k70391b009d4765a5@mail.gmail.com>	
	<p2k1afaf6161004240953td480a58co26bff96d2cee9392@mail.gmail.com>
	<l2yd34314101004240956y763e8c0cs1e60953b8e8cef02@mail.gmail.com>
Message-ID: <4BD32631.1020205@python.org>

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

Am 24.04.2010 18:56, schrieb anatoly techtonik:
> On Sat, Apr 24, 2010 at 7:53 PM, Benjamin Peterson <benjamin at python.org> wrote:
>>>>>
>>>>> Are docs at python.org subscribed to tracker notifications?
>>>>> The mailing list is closed to check.
>>>>
>>>> Why should the docs list be subscribed to tracker notifications?
>>>> We have the bugs list for that.
>>>
>>> Pardon me. Rephrasing the question..
>>>
>>> Are docs at python.org subscribed to tracker notifications for
>>> Documentation component?
>>
>> No, why should they?
> 
> Then volunteers may subscribe to receive notification about
> Documentation issues. They do not have any other means otherwise.

Actually that's a good idea.  I've added a "docs at python" user and
added it to the "auto-nosy" list for Documentation category issues.

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

iEYEARECAAYFAkvTJjEACgkQN9GcIYhpnLC4fACgpxSJrH9t1DN2aZeW6Rrv1oiQ
FqoAoJYA/gqiyWzoki1uRzmwA4vPRbE+
=KUK6
-----END PGP SIGNATURE-----

From martin at v.loewis.de  Sat Apr 24 19:22:04 2010
From: martin at v.loewis.de (=?ISO-8859-1?Q?=22Martin_v=2E_L=F6wis=22?=)
Date: Sat, 24 Apr 2010 19:22:04 +0200
Subject: [Tracker-discuss] Are docs@python.org subscribed to
	tracker	notifications
In-Reply-To: <l2yd34314101004240956y763e8c0cs1e60953b8e8cef02@mail.gmail.com>
References: <k2pd34314101004240901q5550dad8l6ffc33c1672f556b@mail.gmail.com>	<4BD3196A.4060408@python.org>	<r2ld34314101004240951x52d71d41k70391b009d4765a5@mail.gmail.com>	<p2k1afaf6161004240953td480a58co26bff96d2cee9392@mail.gmail.com>
	<l2yd34314101004240956y763e8c0cs1e60953b8e8cef02@mail.gmail.com>
Message-ID: <4BD328BC.8060705@v.loewis.de>

> Then volunteers may subscribe to receive notification about
> Documentation issues. They do not have any other means otherwise.

Sure they do.

Martin


From techtonik at gmail.com  Sat Apr 24 20:10:59 2010
From: techtonik at gmail.com (anatoly techtonik)
Date: Sat, 24 Apr 2010 21:10:59 +0300
Subject: [Tracker-discuss] Are docs@python.org subscribed to tracker
	notifications
In-Reply-To: <4BD328BC.8060705@v.loewis.de>
References: <k2pd34314101004240901q5550dad8l6ffc33c1672f556b@mail.gmail.com>
	<4BD3196A.4060408@python.org>
	<r2ld34314101004240951x52d71d41k70391b009d4765a5@mail.gmail.com>
	<p2k1afaf6161004240953td480a58co26bff96d2cee9392@mail.gmail.com>
	<l2yd34314101004240956y763e8c0cs1e60953b8e8cef02@mail.gmail.com>
	<4BD328BC.8060705@v.loewis.de>
Message-ID: <y2nd34314101004241110n359eef0eo671a0e4f7c394550@mail.gmail.com>

On Sat, Apr 24, 2010 at 8:22 PM, "Martin v. L?wis" <martin at v.loewis.de> wrote:
>> Then volunteers may subscribe to receive notification about
>> Documentation issues. They do not have any other means otherwise.
>
> Sure they do.

Like that?
-- 
anatoly t.

From izak at upfrontsystems.co.za  Mon Apr 26 09:35:08 2010
From: izak at upfrontsystems.co.za (Izak Burger)
Date: Mon, 26 Apr 2010 09:35:08 +0200
Subject: [Tracker-discuss] Backups and our other sysadmin
Message-ID: <4BD5422C.8040100@upfrontsystems.co.za>

Hi all,

Our other sysadmin has asked to be added to the meta-tracker so he will 
also receive tracker related issues. His email address is 
gareth at upfrontsystems.co.za.

He's asked me to inquire about backing up the postgresql database. We'd 
prefer to back it up using pg_dump, but another option would be to allow 
you guys to dump the database to a directory which we can back up. Which 
would you prefer?

regards,
Izak

From brett at python.org  Mon Apr 26 22:34:34 2010
From: brett at python.org (Brett Cannon)
Date: Mon, 26 Apr 2010 13:34:34 -0700
Subject: [Tracker-discuss] Backups and our other sysadmin
In-Reply-To: <4BD5422C.8040100@upfrontsystems.co.za>
References: <4BD5422C.8040100@upfrontsystems.co.za>
Message-ID: <o2pbbaeab101004261334o2579006exf9e9f1e7e194375c@mail.gmail.com>

On Mon, Apr 26, 2010 at 00:35, Izak Burger <izak at upfrontsystems.co.za>wrote:

> Hi all,
>
> Our other sysadmin has asked to be added to the meta-tracker so he will
> also receive tracker related issues. His email address is
> gareth at upfrontsystems.co.za.
>

You mean the tracker-discuss mailing list since anyone can create an account
on the meta tracker?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/tracker-discuss/attachments/20100426/4b355a92/attachment.html>

From martin at v.loewis.de  Mon Apr 26 23:10:23 2010
From: martin at v.loewis.de (=?ISO-8859-1?Q?=22Martin_v=2E_L=F6wis=22?=)
Date: Mon, 26 Apr 2010 23:10:23 +0200
Subject: [Tracker-discuss] Backups and our other sysadmin
In-Reply-To: <4BD5422C.8040100@upfrontsystems.co.za>
References: <4BD5422C.8040100@upfrontsystems.co.za>
Message-ID: <4BD6013F.5030503@v.loewis.de>

> Our other sysadmin has asked to be added to the meta-tracker so he will
> also receive tracker related issues. His email address is
> gareth at upfrontsystems.co.za.

If he creates an account on the meta tracker, we can try to remember to
assign any issues that affect upfront to him. Or else, as Brett
suggests, he can subscribe to tracker-discss, which gets all messages
(plus then some discussion, which he could filter out).

> He's asked me to inquire about backing up the postgresql database. We'd
> prefer to back it up using pg_dump, but another option would be to allow
> you guys to dump the database to a directory which we can back up. Which
> would you prefer?

There is already a cron job which creates daily dumps of the roundup
data - so if you do file-based backup, you already have them.

OTOH, I think I would also prefer pg_dumpall (sic). If it's unacceptable
to have them both, we can kill the cronjobs which create the files once
a day (they are in roundup's crontab).

In any case, we *do* want to have file backup also, because the files
and messages aren't actually stored in the database.

Regards,
Martin

From metatracker at psf.upfronthosting.co.za  Thu Apr 29 14:00:46 2010
From: metatracker at psf.upfronthosting.co.za (Mark Dickinson)
Date: Thu, 29 Apr 2010 12:00:46 +0000
Subject: [Tracker-discuss] [issue336] 'problem encountered' message when
	giving invalid nosy	entry
In-Reply-To: <1272542446.94.0.703576196344.issue336@psf.upfronthosting.co.za>
Message-ID: <1272542446.94.0.703576196344.issue336@psf.upfronthosting.co.za>


New submission from Mark Dickinson <dickinsm at gmail.com>:

Steps to reproduce:
(1) Create a new bug.
(2) Fill in title and nosy entries, leaving all other fields alone.  I used multiple (three) nosy entries, with the last nosy entry (accidentally) misspelled:  "facundo.batista" instead of "facundobatista".
(3) Hit the "Submit new entry" button.

Result: a new browser page, with the message: "A problem was encountered processing your request. The tracker maintainers have been notified of the problem."

After fixing the nosy entry and pressing "Submit new entry" again, I get a "Your request is being processed.  Please be patient." message;  after a few seconds, the submission then goes through.


See http://bugs.python.org/issue8568 for an example that produced this behavior.

----------
messages: 1652
nosy: mark.dickinson
priority: bug
status: unread
title: 'problem encountered' message when giving invalid nosy entry

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