From metatracker at psf.upfronthosting.co.za  Sun Apr  1 03:39:03 2012
From: metatracker at psf.upfronthosting.co.za (R David Murray)
Date: Sun, 01 Apr 2012 01:39:03 +0000
Subject: [Tracker-discuss] [issue443] The quick search appears to be broken
In-Reply-To: <1332950156.73.0.95153285509.issue443@psf.upfronthosting.co.za>
Message-ID: <1333244343.28.0.0509483589049.issue443@psf.upfronthosting.co.za>


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

Sorry, I thought the title made the same bug appropriate, but you are right, since it is a different problem it should be a different bug.  I'll close this one and open a new one (I have a bit more info to add).

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

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

From metatracker at psf.upfronthosting.co.za  Sun Apr  1 03:51:07 2012
From: metatracker at psf.upfronthosting.co.za (R David Murray)
Date: Sun, 01 Apr 2012 01:51:07 +0000
Subject: [Tracker-discuss] [issue445] xapian index appears to be incomplete
Message-ID: <1333245067.12.0.362344366419.issue445@psf.upfronthosting.co.za>


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

With the OS upgrade, the bug tracker is now using Roundup's xapian support for full text searches.  However, this does not appear to be returning complete results.  One example: searching on 'strftime' returns issues 6641, 3091, 2782, and 1459103, but issue 3173 also mentions strftime (including in the title).

A little googling led me to this page: http://openhatch.org/bugs/issue585, which is another group having similar problems with the xapian index.

A search on the roundup bug tracker for xapian bugs yields no hits.

A search using google on the roundup issue tracker for xapian issues yields several open bugs (as well as some fixed ones).  Presumably the roundup tracker is using xapian, and not all the bugs are fixed...

----------
messages: 2418
nosy: loewis, r.david.murray
priority: bug
status: unread
title: xapian index appears to be incomplete

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

From metatracker at psf.upfronthosting.co.za  Sun Apr  1 05:06:26 2012
From: metatracker at psf.upfronthosting.co.za (R David Murray)
Date: Sun, 01 Apr 2012 03:06:26 +0000
Subject: [Tracker-discuss] [issue446] Break down 'open' into 'enhancements'
	vs 'bugs' in	roundup-summary
Message-ID: <1333249586.91.0.0132272669125.issue446@psf.upfronthosting.co.za>


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

I propose to alter the weekly roundup-summary email by breaking down the 'open' category in the header issue summary into the subcategories 'enhancements' and 'bugs'.  The idea is that you get what you measure, and if we see how many bugs we are fixing versus enhancements we are committing, we might get a few more bugs fixed.

The attached patch treats 'enhancment' and 'performance' as enhancements (yes, I know performance issues can be bugs, but ones that really are bugs tend to get fixed quickly), and everything else (including uncategorized) as bugs.

I'm sure we can make some progress on our bug count just by categorizing uncategorized issues, but that will give us a better idea of how many unfixed bugs we really have, which I think is useful info.

----------
files: bugs.patch
messages: 2419
nosy: ezio.melotti, r.david.murray
priority: feature
status: unread
title: Break down 'open' into 'enhancements' vs 'bugs' in roundup-summary

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue446>
_______________________________________________________
-------------- next part --------------
--- /home/roundup/bin/roundup-summary	2010-11-02 16:58:22.000000000 +0100
+++ roundup-summary	2012-04-01 04:50:09.000000000 +0200
@@ -24,6 +24,10 @@
     -r RESOLVED, --resolved=RESOLVED
                         Comma-delimited list of statuses that corresponds to
                         resolved (default: resolved,done,done-cbb,closed,faq).
+    -n ENHANCEMENT, --not-bug=ENHANCEMENT
+                        Comma-delimited list of types that correspond to
+                        issues that are enhancemnts, not bugs (default:
+                        enhancement)
     -o FILENAME, --output=FILENAME
                         File name for output; default is stdout.
     -e FILENAME, --errors=FILENAME
@@ -60,9 +64,11 @@
 Do NOT respond to this message.
 
 Issues counts and deltas:
-  open   %(open)5d (%(open_delta)+3d)
-  closed %(closed)5d (%(closed_delta)+3d)
-  total  %(total)5d (%(total_delta)+3d)
+  open            %(open)5d (%(open_delta)+3d)
+    enhancements  %(enhancements)5d (%(enhancements_delta)+3d)
+    bugs          %(bugs)5d (%(bugs_delta)+3d)
+  closed          %(closed)5d (%(closed_delta)+3d)
+  total           %(total)5d (%(total_delta)+3d)
 
 Open issues with patches: %(patches)-5d"""
 
@@ -79,6 +85,8 @@
 <p>Issues stats:</p>
 <table border="1">
   <tr><th>open</th><td>%(open)5d (%(open_new)+3d)</td></tr>
+  <tr><th>&nbsp;&nbsp;enhancements</th></td>%s(enhancements)5d (%s(enhancements_delta)+3d)</td></tr>
+  <tr><th>&nbsp&nbsp;;bugs</th></td>%s(bugs)5d (%s(bugs_delta)+3d)</td></tr>
   <tr><th>closed</th><td>%(closed)5d (%(closed_new)+3d)</td></tr>
   <tr><th>total</th><td>%(total)5d (%(total_new)+3d)</td></tr>
 </table>
@@ -93,6 +101,8 @@
     """
     # list of statuses to treat as closed -- these don't have to all exist.
     resolved_status_def = 'resolved,done,done-cbb,closed,faq'
+    # similar list of types to treat as enhancements, not bugs.
+    enhancement_type_def = 'enhancement,performance'
     # period of time for report. Uses roundup syntax for ranges.
     default_dates = '-1w;' # last week
     # email address of recipient of report, if any.
@@ -120,6 +130,10 @@
         help='Comma-delimited list of statuses that corresponds to resolved '
              '(default: %default).')
     advanced.add_option(
+        '-n', '--not-bug', dest='enhancements', default=enhancement_type_def,
+        help='Comma-delmited list of types that correspond to issues that '
+             'are enhancements, not bugs (default: %default).')
+    advanced.add_option(
         '-o', '--output', dest='output', metavar='FILENAME', default='',
         help='File name for output; default is stdout.')
     advanced.add_option(
@@ -144,6 +158,7 @@
                      'you must supply the path to a tracker home.')
     options.dates = get_dates(options.dates)
     options.resolved = [s.strip() for s in options.resolved.split(',')]
+    options.enhancements = [s.strip() for s in options.enhancements.split(',')]
     instance_home = args[0]
     return options, instance_home
 
@@ -208,9 +223,9 @@
         start_str = start_date.pretty(format='%F') # %F -> yyyy-mm-dd
         end_str = end_date.pretty(format='%F')
         # counters for current values
-        open_tot = closed_tot = all_tot = 0
+        open_tot = enhance_tot = closed_tot = all_tot = 0
         # counters for previous values
-        open_old = closed_old = all_old = 0
+        open_old = enhance_old = closed_old = all_old = 0
         with_patch = 0
         patch_id = DB.keyword.lookup('patch')
         for id, issue in self.issues.iteritems():
@@ -218,6 +233,8 @@
             if issue['creation'] > end_date:
                 continue
             all_tot += 1
+            was_enhance = issue['last_period_type'] in OPTIONS.enhancements
+            is_enhance = issue['type'] in OPTIONS.enhancements
             if issue['creation'] < start_date:
                 all_old += 1
                 # check if the issue was closed at the end of the previous
@@ -226,6 +243,9 @@
                     closed_old += 1
                 else:
                     open_old += 1
+                    if was_enhance:
+                        enhance_old += 1
+                
             # check if the issue is closed now
             if issue['closed']:
                 closed_tot += 1
@@ -233,10 +253,16 @@
                 open_tot += 1
                 if patch_id in issue['keyword_ids']:
                     with_patch += 1
+                if is_enhance:
+                    enhance_tot += 1
         all_delta = all_tot - all_old
         open_delta = open_tot - open_old
         closed_delta = closed_tot - closed_old
         assert all_delta == open_delta + closed_delta
+        enhance_delta = enhance_tot - enhance_old
+        bugs_tot = open_tot - enhance_tot
+        bugs_old = open_old - enhance_old
+        bugs_delta = bugs_tot - bugs_old
         # save the values in an attribute to avoid calculating it twice
         # when both the txt and the HTML header are needed (i.e. when sending
         # HTML mails)
@@ -246,6 +272,8 @@
             tracker_name=DB.config.TRACKER_NAME,
             open=open_tot, open_delta=open_delta,
             closed=closed_tot, closed_delta=closed_delta,
+            bugs=bugs_tot, bugs_delta=bugs_delta,
+            enhancements=enhance_tot, enhancements_delta=enhance_delta,
             total=all_tot, total_delta=all_delta,
             patches=with_patch,
         )
@@ -505,6 +533,9 @@
         status = None,
         real_status = sid2name(attrs['status']), # Avoid a bug in get_issue_attrs
         last_period_status = None, # the status of the issue before start_date
+        type = '',
+        real_type = tid2name(attrs['type']),
+        last_period_type = None, # the type of the issue before start_date
         actor = None,
         activity = None,
         keyword_ids = kwds,
@@ -524,6 +555,8 @@
         status1 = sid2name(attrs['status']),
         actor2 = attrs['actor'],
         activity2 = attrs['activity'],
+        type2 = tid2name(attrs['type']),
+        type1 = tid2name(attrs['type']),
         journal = journal
     )
     return issue, helper
@@ -545,13 +578,14 @@
         return dates.to_value > issue['creation'] <= dates.from_value
 
     def update(issue, helper):
-        for key in ('status', 'actor', 'activity'):
+        for key in ('status', 'actor', 'activity', 'type'):
             issue[key] = issue[key] or helper[key + '2']
     # I'm not sure all this stuff is necessary, but it seems to work...
     # this trick catches the first time we are in the interval of interest
     if helper['activity2'] < dates.to_value:
         update(issue, helper)
     status_changes = []
+    type_changes = []
     old_time = issue['creation']
     for _, time, userid, act, data in helper['journal']:
         in_period =  dates.to_value > time >= dates.from_value
@@ -585,7 +619,12 @@
                     issue['real_status'] in OPTIONS.resolved):
                     issue['closer'] = userid
                     issue['closed_date'] = time
+            if 'type' in data:
+                helper['type1'] = tid2name(data['type'])
+                type_changes.append((old_time, helper['type1']))
+                old_time = time
     status_changes.append((old_time, issue['real_status']))
+    type_changes.append((old_time, issue['real_type']))
     # if the status didn't change and this is still None set it to 'open',
     # leave it to None for new issues
     if issue['creation'] < dates.from_value:
@@ -594,6 +633,11 @@
                 issue['last_period_status'] = status
         if issue['last_period_status'] is None:
             issue['last_period_status'] = 'open'
+        for time, type in type_changes:
+            if time < dates.from_value:
+                issue['last_period_type'] = type
+        if issue['last_period_type'] is None:
+            issue['last_period_type'] = issue['type']
     # get these set if not done before
     update(issue, helper)
     last_opened = issue['reopened_date'] or issue['creation']
@@ -657,6 +701,13 @@
     cache[status_id] = name
     return name
 
+def tid2name(issue_type_id, cache={None:'none'}):
+    if issue_type_id in cache:
+        return cache[issue_type_id]
+    name = DB.issue_type.get(issue_type_id, 'name')
+    cache[issue_type_id] = name
+    return name
+
 def uid2name(user_id, cache={None:'none'}):
     if user_id in cache:
         return cache[user_id]

From metatracker at psf.upfronthosting.co.za  Sun Apr  1 10:55:52 2012
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v=2E_L=C3=B6wis?=)
Date: Sun, 01 Apr 2012 08:55:52 +0000
Subject: [Tracker-discuss] [issue445] xapian index appears to be incomplete
In-Reply-To: <1333245067.12.0.362344366419.issue445@psf.upfronthosting.co.za>
Message-ID: <1333270552.53.0.185014534089.issue445@psf.upfronthosting.co.za>


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

I suggest to check the specific index, using a custom Python script, to find out what exactly is in the index.

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

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

From metatracker at psf.upfronthosting.co.za  Mon Apr  2 17:04:18 2012
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v=2E_L=C3=B6wis?=)
Date: Mon, 02 Apr 2012 15:04:18 +0000
Subject: [Tracker-discuss] [issue415] Mercurial integration: regression in
	diff generation
In-Reply-To: <1312642512.39.0.425778233696.issue415@psf.upfronthosting.co.za>
Message-ID: <1333379058.1.0.988833176103.issue415@psf.upfronthosting.co.za>


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

Closing this report as invalid: the misgeneration of the patch has not been demonstrated.

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

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

From metatracker at psf.upfronthosting.co.za  Mon Apr  2 17:25:16 2012
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v=2E_L=C3=B6wis?=)
Date: Mon, 02 Apr 2012 15:25:16 +0000
Subject: [Tracker-discuss] [issue409] Spam on jython tracker.
In-Reply-To: <1310843975.4.0.271262889404.issue409@psf.upfronthosting.co.za>
Message-ID: <1333380316.89.0.169702317679.issue409@psf.upfronthosting.co.za>


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

Retiring the message had not the desired effect; it merely makes it unavailable for listing. I have now restored the Spam button, and marked the files and the message as spam.

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

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

From metatracker at psf.upfronthosting.co.za  Mon Apr  2 17:29:30 2012
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v=2E_L=C3=B6wis?=)
Date: Mon, 02 Apr 2012 15:29:30 +0000
Subject: [Tracker-discuss] [issue444] Mail delivery failed
In-Reply-To: <1333199768.96.0.175106528184.issue444@psf.upfronthosting.co.za>
Message-ID: <1333380570.1.0.059875037386.issue444@psf.upfronthosting.co.za>


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

I have forwarded this report to postmaster.

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

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

From metatracker at psf.upfronthosting.co.za  Mon Apr  2 17:34:35 2012
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v=2E_L=C3=B6wis?=)
Date: Mon, 02 Apr 2012 15:34:35 +0000
Subject: [Tracker-discuss] [issue440] unable to log in with
	openid.stackexchange.com
In-Reply-To: <1331759578.98.0.306317277648.issue440@psf.upfronthosting.co.za>
Message-ID: <1333380875.45.0.598200233775.issue440@psf.upfronthosting.co.za>


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

I can't reproduce this. It works fine for me.

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

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

From metatracker at psf.upfronthosting.co.za  Mon Apr  2 17:47:37 2012
From: metatracker at psf.upfronthosting.co.za (Tshepang Lekhonkhobe)
Date: Mon, 02 Apr 2012 15:47:37 +0000
Subject: [Tracker-discuss] [issue440] unable to log in with
	openid.stackexchange.com
In-Reply-To: <1331759578.98.0.306317277648.issue440@psf.upfronthosting.co.za>
Message-ID: <1333381657.74.0.428995855764.issue440@psf.upfronthosting.co.za>


Tshepang Lekhonkhobe <tshepang at gmail.com> added the comment:

yeah, it works today

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

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

From metatracker at psf.upfronthosting.co.za  Mon Apr  2 18:07:26 2012
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v=2E_L=C3=B6wis?=)
Date: Mon, 02 Apr 2012 16:07:26 +0000
Subject: [Tracker-discuss] [issue439] Email notifictations not received for
	rietveld review
In-Reply-To: <1331683700.81.0.418164698072.issue439@psf.upfronthosting.co.za>
Message-ID: <1333382846.28.0.655589980033.issue439@psf.upfronthosting.co.za>


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

That's not actually true: dmalcolm *is* in the CC list of http://bugs.python.org/review/13703/show (at PyCon, we checked the Reviewer's list, which is a separate list of users in Rietveld that (I think) are the ones who made reviews).

I created issue 14477 to further experiment.

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

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

From metatracker at psf.upfronthosting.co.za  Mon Apr  2 18:10:18 2012
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v=2E_L=C3=B6wis?=)
Date: Mon, 02 Apr 2012 16:10:18 +0000
Subject: [Tracker-discuss] [issue439] Email notifictations not received for
	rietveld review
In-Reply-To: <1331683700.81.0.418164698072.issue439@psf.upfronthosting.co.za>
Message-ID: <1333383018.0.0.364442892852.issue439@psf.upfronthosting.co.za>


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

dmalcolm: can you please report whether you received the email from Rietveld, titled "Rietveld test issue (issue14477)" and posted a minute ago?

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

From metatracker at psf.upfronthosting.co.za  Mon Apr  2 18:19:13 2012
From: metatracker at psf.upfronthosting.co.za (David Malcolm)
Date: Mon, 02 Apr 2012 16:19:13 +0000
Subject: [Tracker-discuss] [issue439] Email notifictations not received for
	rietveld review
In-Reply-To: <1333383018.0.0.364442892852.issue439@psf.upfronthosting.co.za>
Message-ID: <1333383507.2447.50.camel@surprise>


David Malcolm <dmalcolm at redhat.com> added the comment:

On Mon, 2012-04-02 at 16:10 +0000, Martin v. L?wis wrote:
> Martin v. L?wis <martin at v.loewis.de> added the comment:
> 
> dmalcolm: can you please report whether you received the email from Rietveld, titled "Rietveld test issue (issue14477)" and posted a minute ago?

No: I did receive two emails from the *bug tracker* [1], both with
subject
  "[issue14477] Rietveld test issue"
(the first signifying the issue was opened, the second with:
  "keywords: +patch
  Added file: http://bugs.python.org/file25098/readme.diff"

However, I don't seem to have received an email from Rietveld: not with
the title you describe above.

[1] both have
From: =?utf-8?q?Martin_v=2E_L=C3=B6wis?= <report at bugs.python.org>
but are Reply-To:Python tracker <report at bugs.python.org>

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

From metatracker at psf.upfronthosting.co.za  Tue Apr  3 20:25:50 2012
From: metatracker at psf.upfronthosting.co.za (Oleg)
Date: Tue, 03 Apr 2012 18:25:50 +0000
Subject: [Tracker-discuss] [issue447] Cannot remind password for python wiki
Message-ID: <1333477550.44.0.112787201433.issue447@psf.upfronthosting.co.za>


New submission from Oleg <phd at phdru.name>:

I have tried to login to http://wiki.python.org/moin/SqlObject and failed. I tried to send a password reminder to myself but moin failed with the following message on that page:

(553, 'rejected, message looks like spam.\n.\\c Contact your postmaster/admin for assistance. Please provide the following information in your problem report: time (Apr 03 20:19:42) and client (2001:888:2000:d::a4).')

----------
messages: 2429
nosy: phd
priority: bug
status: unread
title: Cannot remind password for python wiki

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

From metatracker at psf.upfronthosting.co.za  Wed Apr  4 08:24:57 2012
From: metatracker at psf.upfronthosting.co.za (Eric Snow)
Date: Wed, 04 Apr 2012 06:24:57 +0000
Subject: [Tracker-discuss] [issue402] Unable to log in to Rietveld code
	review interface
In-Reply-To: <1306534797.29.0.437152892578.issue402@psf.upfronthosting.co.za>
Message-ID: <1333520697.32.0.246078835769.issue402@psf.upfronthosting.co.za>


Eric Snow <ericsnowcurrently at gmail.com> added the comment:

any ideas on this one?  I'm willing to trouble-shoot it (but don't have access).

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

From metatracker at psf.upfronthosting.co.za  Thu Apr  5 17:35:35 2012
From: metatracker at psf.upfronthosting.co.za (Izak Burger)
Date: Thu, 05 Apr 2012 15:35:35 +0000
Subject: [Tracker-discuss] [issue442] Upgrade Debian
In-Reply-To: <1332991300.63.0.391057034289.issue442@psf.upfronthosting.co.za>
Message-ID: <CAGscxN30cmnRVQXCgee=bQ-fNYL2=X2cXBwFyVaMsmTNj=K54w@mail.gmail.com>


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

Hi again,

I discovered the Hetzner Wiki with the details on how to set up ipv6
properly. It appears to work now. The ipv6 address for bugs.python.org
is:

2a01:4f8:131:2480::3

regards,
Izak

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

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

From metatracker at psf.upfronthosting.co.za  Thu Apr  5 18:43:01 2012
From: metatracker at psf.upfronthosting.co.za (Terry Reedy)
Date: Thu, 05 Apr 2012 16:43:01 +0000
Subject: [Tracker-discuss] [issue448] Login not working (mostly)
Message-ID: <1333644181.93.0.427714955722.issue448@psf.upfronthosting.co.za>


New submission from Terry Reedy <tjreedy at udel.edu>:

If I go to bugs.python.org, get default page with recent activity, fill in name,pass, hit [login], I get, with red background
"broken form: multiple @action values submitted"

If I go to search page and do same, I do get logged in.
If I do a search and do same from results page, get same error.
This is new behavior.

Win7, 64 bit, FireFox 11

----------
messages: 2432
nosy: terry.reedy
priority: urgent
status: unread
title: Login not working (mostly)

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

From metatracker at psf.upfronthosting.co.za  Thu Apr  5 19:12:06 2012
From: metatracker at psf.upfronthosting.co.za (Nadeem Vawda)
Date: Thu, 05 Apr 2012 17:12:06 +0000
Subject: [Tracker-discuss] [issue402] Unable to log in to Rietveld code
	review interface
In-Reply-To: <1306534797.29.0.437152892578.issue402@psf.upfronthosting.co.za>
Message-ID: <1333645926.16.0.607061984587.issue402@psf.upfronthosting.co.za>


Nadeem Vawda <nadeem.vawda at gmail.com> added the comment:

AFAICT, the source lives at <http://svn.python.org/view/tracker/>, with the
Rietveld stuff under instances/python-dev/rietveld/.

You might be able to get useful info by trying to run your own instance locally,
and inspecting the DB state directly before and after reproducing the bug.

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

From metatracker at psf.upfronthosting.co.za  Fri Apr  6 01:51:59 2012
From: metatracker at psf.upfronthosting.co.za (Eric Snow)
Date: Thu, 05 Apr 2012 23:51:59 +0000
Subject: [Tracker-discuss] [issue402] Unable to log in to Rietveld code
	review interface
In-Reply-To: <1306534797.29.0.437152892578.issue402@psf.upfronthosting.co.za>
Message-ID: <1333669919.65.0.187649962073.issue402@psf.upfronthosting.co.za>


Eric Snow <ericsnowcurrently at gmail.com> added the comment:

Yeah, I'll give it a go tonight.  Hopefully I can turn something up.  (While I'm at it I'll probably update the wiki page on building a tracker instance.)

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

From metatracker at psf.upfronthosting.co.za  Fri Apr  6 07:05:52 2012
From: metatracker at psf.upfronthosting.co.za (Ramchandra Apte)
Date: Fri, 06 Apr 2012 05:05:52 +0000
Subject: [Tracker-discuss] [issue449] Sending email to bugs.python.org could
	create bug report	with wrong name.
Message-ID: <1333688752.74.0.278825254267.issue449@psf.upfronthosting.co.za>


New submission from Ramchandra Apte <maniandram01 at gmail.com>:

If you set your email name to something different from your bug tracker name and send an email to bugs.python.org, the bug report created will contain the email name. The bug report created is uncloseable and only the bug tracker admins can close it. The bug tracker should get the name by searching for the email address in the user database not by the email name.
For example, issue 13661 .

----------
messages: 2435
nosy: ramchandra.apte
priority: bug
status: unread
title: Sending email to bugs.python.org could create bug report with wrong name.

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

From metatracker at psf.upfronthosting.co.za  Fri Apr  6 07:07:47 2012
From: metatracker at psf.upfronthosting.co.za (Ramchandra Apte)
Date: Fri, 06 Apr 2012 05:07:47 +0000
Subject: [Tracker-discuss] [issue411] Roundup instance is outdated
In-Reply-To: <1311602492.71.0.972062932119.issue411@psf.upfronthosting.co.za>
Message-ID: <1333688867.81.0.965732863655.issue411@psf.upfronthosting.co.za>


Ramchandra Apte <maniandram01 at gmail.com> added the comment:

Status of this bug?

----------
nosy: +ramchandra.apte

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

From metatracker at psf.upfronthosting.co.za  Sat Apr  7 04:35:42 2012
From: metatracker at psf.upfronthosting.co.za (Paul Ackersviller)
Date: Sat, 07 Apr 2012 02:35:42 +0000
Subject: [Tracker-discuss] [issue450] ia64-hp-hpux11.31 won't compile
	Python-2.6.8rc2 without	-D_TERMIOS_INCLUDED
Message-ID: <1333766142.58.0.876252232668.issue450@psf.upfronthosting.co.za>


New submission from Paul Ackersviller <pda at freeshell.org>:

I can't help thinking that configure should be able to figure out the need for this -- Modules/termios.c won't compile without adding -D_TERMIOS_INCLUDED by hand. This is far from new, all 2.5+ versions I've tried to compile are like that on this platform.

----------
messages: 2437
nosy: pda
priority: wish
status: unread
title: ia64-hp-hpux11.31 won't compile Python-2.6.8rc2 without -D_TERMIOS_INCLUDED

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

From metatracker at psf.upfronthosting.co.za  Sat Apr  7 04:55:23 2012
From: metatracker at psf.upfronthosting.co.za (Paul Ackersviller)
Date: Sat, 07 Apr 2012 02:55:23 +0000
Subject: [Tracker-discuss] [issue451]
	Python-2.7.3rc2/Modules/_ctypes/libffi/src/dlmalloc.c	won't
	compile on ia64-hp-hpux11.31 due to 'struct mallinfo'
Message-ID: <1333767323.39.0.265147506534.issue451@psf.upfronthosting.co.za>


New submission from Paul Ackersviller <pda at freeshell.org>:

In file included from /usr/local/src/Python-2.7.3rc2/Modules/_ctypes/libffi/src/dlmalloc.c:1161:0:
/usr/local/free/lib/gcc/ia64-hp-hpux11.31/4.6.3/include-fixed/stdlib.h:591:10: error: redefinition of 'struct mallinfo'
/usr/local/src/Python-2.7.3rc2/Modules/_ctypes/libffi/src/dlmalloc.c:622:8: note: originally defined here
In file included from /usr/local/src/Python-2.7.3rc2/Modules/_ctypes/libffi/src/dlmalloc.c:1161:0:
/usr/local/free/lib/gcc/ia64-hp-hpux11.31/4.6.3/include-fixed/stdlib.h:773:29: error: conflicting types for 'mallinfo'
/usr/local/src/Python-2.7.3rc2/Modules/_ctypes/libffi/src/dlmalloc.c:811:17: note: previous declaration of 'mallinfo' was here
/usr/local/src/Python-2.7.3rc2/Modules/_ctypes/libffi/src/dlmalloc.c:4383:17: error: conflicting types for 'mallinfo'
/usr/local/src/Python-2.7.3rc2/Modules/_ctypes/libffi/src/dlmalloc.c:811:17: note: previous declaration of 'mallinfo' was here

----------
messages: 2438
nosy: pda
priority: critical
status: unread
title: Python-2.7.3rc2/Modules/_ctypes/libffi/src/dlmalloc.c won't compile on ia64-hp-hpux11.31 due to 'struct mallinfo'

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

From metatracker at psf.upfronthosting.co.za  Sat Apr  7 05:21:11 2012
From: metatracker at psf.upfronthosting.co.za (Paul Ackersviller)
Date: Sat, 07 Apr 2012 03:21:11 +0000
Subject: [Tracker-discuss] [issue452] Python-2.6.8rc2 test never finishes
	ia64-hp-hpux11.31
Message-ID: <1333768871.55.0.687800045934.issue452@psf.upfronthosting.co.za>


New submission from Paul Ackersviller <pda at freeshell.org>:

Perhaps I'm not interpreting something happening earlier, but `make test' here  only seems to run a short time but doesn't actually finish.  It appears not to be using any cpu, or waiting for input, so I'm not sure what's happening.
...
test_grammar
test_opcodes
test_dict
test_builtin
test_exceptions
test_types
test_unittest
test_doctest
test_doctest2
test_py3kwarn
test_py3kwarn skipped -- test.test_py3kwarn must be run with the -3 flag
test_MimeWriter
test_SimpleHTTPServer
test_StringIO
test___all__
test test___all__ failed -- Traceback (most recent call last):
  File "/usr/local/src/Python-2.6.8rc2/Lib/test/test___all__.py", line 103, in test_all
    self.check_all(modname)
  File "/usr/local/src/Python-2.6.8rc2/Lib/test/test___all__.py", line 39, in check_all
    modname, e.__class__.__name__, e))

AssertionError: __all__ failure in distutils.command: ImportError: No module named _sha256

test___future__
test__locale
test_abc
test_abstract_numbers
test_aepack
test_aepack skipped -- No module named aepack
test_aifc
test_al
test_al skipped -- No module named al
test_anydbm
test_applesingle
test_applesingle skipped -- No module named macostools
test_array
test_ast
test_asynchat
test test_asynchat failed -- multiple errors occurred; run in verbose mode for details
test_asyncore
test test_asyncore failed -- multiple errors occurred; run in verbose mode for details
test_atexit
test_audioop
test_augassign
test_base64
test_bastion
test_bigaddrspace
test_bigmem
test_binascii
test_binhex
test_binop
test_bisect
test_bool
test_bsddb
test_bsddb skipped -- No module named _bsddb
test_bsddb185
test_bsddb185 skipped -- No module named bsddb185
test_bsddb3
test_bsddb3 skipped -- No module named _bsddb
test_buffer
test_bufio
test_bytes
test_bz2
test_bz2 skipped -- No module named bz2
test_calendar
test_call
test_capi

----------
messages: 2439
nosy: pda
priority: bug
status: unread
title: Python-2.6.8rc2 test never finishes ia64-hp-hpux11.31

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

From metatracker at psf.upfronthosting.co.za  Sat Apr  7 05:32:09 2012
From: metatracker at psf.upfronthosting.co.za (Paul Ackersviller)
Date: Sat, 07 Apr 2012 03:32:09 +0000
Subject: [Tracker-discuss] [issue453] Can't build Python-2.7.3rc2 _ctypes
	module on	ia64-hp-hpux11.31 even using --with-system-ffi
Message-ID: <1333769529.15.0.271000298578.issue453@psf.upfronthosting.co.za>


New submission from Paul Ackersviller <pda at freeshell.org>:

I do have an external libffi package installed -- is there some trick in directing --with-system-ffi to the path where it's located.

----------
messages: 2440
nosy: pda
priority: urgent
status: unread
title: Can't build Python-2.7.3rc2 _ctypes module on ia64-hp-hpux11.31 even using --with-system-ffi

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

From metatracker at psf.upfronthosting.co.za  Sat Apr  7 10:10:20 2012
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v=2E_L=C3=B6wis?=)
Date: Sat, 07 Apr 2012 08:10:20 +0000
Subject: [Tracker-discuss] [issue450] ia64-hp-hpux11.31 won't compile
	Python-2.6.8rc2 without	-D_TERMIOS_INCLUDED
In-Reply-To: <1333766142.58.0.876252232668.issue450@psf.upfronthosting.co.za>
Message-ID: <1333786220.93.0.0439539699066.issue450@psf.upfronthosting.co.za>


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

This is not the bug tracker for Python, but the bug tracker for Python's bug tracker, which can be found at bugs.python.org.

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

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

From metatracker at psf.upfronthosting.co.za  Sat Apr  7 10:10:53 2012
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v=2E_L=C3=B6wis?=)
Date: Sat, 07 Apr 2012 08:10:53 +0000
Subject: [Tracker-discuss] [issue451]
	Python-2.7.3rc2/Modules/_ctypes/libffi/src/dlmalloc.c	won't
	compile on ia64-hp-hpux11.31 due to 'struct mallinfo'
In-Reply-To: <1333767323.39.0.265147506534.issue451@psf.upfronthosting.co.za>
Message-ID: <1333786253.14.0.333195584302.issue451@psf.upfronthosting.co.za>


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

This is not the bug tracker for Python, but the bug tracker for Python's bug tracker, which can be found at bugs.python.org.

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

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

From metatracker at psf.upfronthosting.co.za  Sat Apr  7 10:11:07 2012
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v=2E_L=C3=B6wis?=)
Date: Sat, 07 Apr 2012 08:11:07 +0000
Subject: [Tracker-discuss] [issue452] Python-2.6.8rc2 test never finishes
	ia64-hp-hpux11.31
In-Reply-To: <1333768871.55.0.687800045934.issue452@psf.upfronthosting.co.za>
Message-ID: <1333786267.56.0.670570557544.issue452@psf.upfronthosting.co.za>


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

This is not the bug tracker for Python, but the bug tracker for Python's bug tracker, which can be found at bugs.python.org.

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

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

From metatracker at psf.upfronthosting.co.za  Sat Apr  7 10:11:21 2012
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v=2E_L=C3=B6wis?=)
Date: Sat, 07 Apr 2012 08:11:21 +0000
Subject: [Tracker-discuss] [issue453] Can't build Python-2.7.3rc2 _ctypes
	module on	ia64-hp-hpux11.31 even using --with-system-ffi
In-Reply-To: <1333769529.15.0.271000298578.issue453@psf.upfronthosting.co.za>
Message-ID: <1333786281.06.0.575815550242.issue453@psf.upfronthosting.co.za>


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

This is not the bug tracker for Python, but the bug tracker for Python's bug tracker, which can be found at bugs.python.org.

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

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

From metatracker at psf.upfronthosting.co.za  Sat Apr  7 18:21:16 2012
From: metatracker at psf.upfronthosting.co.za (Thomas-Jon Corpuz)
Date: Sat, 07 Apr 2012 16:21:16 +0000
Subject: [Tracker-discuss] [issue454] IDLE issue
Message-ID: <1333815676.76.0.0816436150213.issue454@psf.upfronthosting.co.za>


New submission from Thomas-Jon Corpuz <arcangeltj at gmail.com>:

I am having an issue opening the Python IDLE. There is an error message saying 'IDLE's subprocess didn't make connection. Either IDLE can't start a subprocess or personal firewall is blocking the connection.' Can I have more information to what and why this is happening? And what can I do to fix this problem?

----------
messages: 2445
nosy: arcangeltj
priority: urgent
status: unread
title: IDLE issue

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

From metatracker at psf.upfronthosting.co.za  Sat Apr  7 20:04:46 2012
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v=2E_L=C3=B6wis?=)
Date: Sat, 07 Apr 2012 18:04:46 +0000
Subject: [Tracker-discuss] [issue454] IDLE issue
In-Reply-To: <1333815676.76.0.0816436150213.issue454@psf.upfronthosting.co.za>
Message-ID: <1333821886.92.0.963042940063.issue454@psf.upfronthosting.co.za>


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

This is the tracker for issues with the Python bug tracker. The Python bug tracker itself is at bugs.python.org.

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

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

From metatracker at psf.upfronthosting.co.za  Sun Apr  8 09:11:32 2012
From: metatracker at psf.upfronthosting.co.za (Serhiy Storchaka)
Date: Sun, 08 Apr 2012 07:11:32 +0000
Subject: [Tracker-discuss] [issue455] Patch review in some issues is not
	working
Message-ID: <1333869092.36.0.421927917118.issue455@psf.upfronthosting.co.za>


New submission from Serhiy Storchaka <storchaka at gmail.com>:

See http://bugs.python.org/issue6972. I get "No issue exists with that id (6972)" when trying to review a patch.

----------
messages: 2447
nosy: storchaka
priority: bug
status: unread
title: Patch review in some issues is not working

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

From metatracker at psf.upfronthosting.co.za  Sun Apr  8 09:12:58 2012
From: metatracker at psf.upfronthosting.co.za (Serhiy Storchaka)
Date: Sun, 08 Apr 2012 07:12:58 +0000
Subject: [Tracker-discuss] [issue455] Patch review in some issues is not
	working
In-Reply-To: <1333869092.36.0.421927917118.issue455@psf.upfronthosting.co.za>
Message-ID: <1333869178.17.0.325175841804.issue455@psf.upfronthosting.co.za>


Serhiy Storchaka <storchaka at gmail.com> added the comment:

http://bugs.python.org/issue6972

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

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

From metatracker at psf.upfronthosting.co.za  Sun Apr  8 21:35:24 2012
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v=2E_L=C3=B6wis?=)
Date: Sun, 08 Apr 2012 19:35:24 +0000
Subject: [Tracker-discuss] [issue455] Patch review in some issues is not
	working
In-Reply-To: <1333869092.36.0.421927917118.issue455@psf.upfronthosting.co.za>
Message-ID: <1333913724.58.0.988755072465.issue455@psf.upfronthosting.co.za>


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

I had to delete a lot of rietveld issues due to performance reasons after the initial setup. I have now also removed the dangling links.

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

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

From metatracker at psf.upfronthosting.co.za  Mon Apr  9 00:17:17 2012
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v=2E_L=C3=B6wis?=)
Date: Sun, 08 Apr 2012 22:17:17 +0000
Subject: [Tracker-discuss] [issue402] Unable to log in to Rietveld code
	review interface
In-Reply-To: <1306534797.29.0.437152892578.issue402@psf.upfronthosting.co.za>
Message-ID: <1333923437.46.0.576907001204.issue402@psf.upfronthosting.co.za>


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

This is now fixed in r88935, which updates auth_user when _user changes. In addition, I manually updated the 187 users which have changed their usernames since the rietveld setup was created.

Please confirm that it works.

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

From metatracker at psf.upfronthosting.co.za  Mon Apr  9 04:11:36 2012
From: metatracker at psf.upfronthosting.co.za (Eric Snow)
Date: Mon, 09 Apr 2012 02:11:36 +0000
Subject: [Tracker-discuss] [issue402] Unable to log in to Rietveld code
	review interface
In-Reply-To: <1306534797.29.0.437152892578.issue402@psf.upfronthosting.co.za>
Message-ID: <1333937496.93.0.473554700559.issue402@psf.upfronthosting.co.za>


Eric Snow <ericsnowcurrently at gmail.com> added the comment:

Works great.  Thanks, Martin!

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

From metatracker at psf.upfronthosting.co.za  Mon Apr  9 06:39:57 2012
From: metatracker at psf.upfronthosting.co.za (Nadeem Vawda)
Date: Mon, 09 Apr 2012 04:39:57 +0000
Subject: [Tracker-discuss] [issue402] Unable to log in to Rietveld code
	review interface
In-Reply-To: <1306534797.29.0.437152892578.issue402@psf.upfronthosting.co.za>
Message-ID: <1333946397.92.0.921645691373.issue402@psf.upfronthosting.co.za>


Nadeem Vawda <nadeem.vawda at gmail.com> added the comment:

Confirmed fixed. Thanks!

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

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

From metatracker at psf.upfronthosting.co.za  Tue Apr 10 06:50:40 2012
From: metatracker at psf.upfronthosting.co.za (anatoly techtonik)
Date: Tue, 10 Apr 2012 04:50:40 +0000
Subject: [Tracker-discuss] [issue411] Roundup instance is outdated (1.4.19
	is the latest version	as of 2012-03)
In-Reply-To: <1311602492.71.0.972062932119.issue411@psf.upfronthosting.co.za>
Message-ID: <1334033440.15.0.581133375602.issue411@psf.upfronthosting.co.za>


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

Looking at revision 88888 it's done. http://svn.python.org/view/tracker/instances/ Gratz Ezio for scoring magic revisions number. =)

----------
status: chatting -> resolved
title: Roundup instance is outdated -> Roundup instance is outdated (1.4.19 is the latest version as of 2012-03)

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

From metatracker at psf.upfronthosting.co.za  Wed Apr 11 15:30:20 2012
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Kristj=C3=A1n_Valur_J=C3=B3nsson?=)
Date: Wed, 11 Apr 2012 13:30:20 +0000
Subject: [Tracker-discuss] [issue456] Add user links to roundup users
Message-ID: <1334151020.0.0.534784635455.issue456@psf.upfronthosting.co.za>


New submission from Kristj?n Valur J?nsson <kristjan at ccpgames.com>:

It would be nice if users could add a URL link that could be associated with their account, for example, to get additional information on the specific users.  Their user names in the issues pages could then hyperlink to that URL.

----------
messages: 2454
nosy: kristjan.jonsson
priority: wish
status: unread
title: Add user links to roundup users

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

From metatracker at psf.upfronthosting.co.za  Wed Apr 11 16:45:13 2012
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v=2E_L=C3=B6wis?=)
Date: Wed, 11 Apr 2012 14:45:13 +0000
Subject: [Tracker-discuss] [issue456] Add user links to roundup users
In-Reply-To: <1334151020.0.0.534784635455.issue456@psf.upfronthosting.co.za>
Message-ID: <1334155513.38.0.393459000191.issue456@psf.upfronthosting.co.za>


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

Thanks for the report. This is now implemented in r88945

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

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

From metatracker at psf.upfronthosting.co.za  Wed Apr 11 16:50:19 2012
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Kristj=C3=A1n_Valur_J=C3=B3nsson?=)
Date: Wed, 11 Apr 2012 14:50:19 +0000
Subject: [Tracker-discuss] [issue456] Add user links to roundup users
In-Reply-To: <1334151020.0.0.534784635455.issue456@psf.upfronthosting.co.za>
Message-ID: <1334155819.5.0.3107475253.issue456@psf.upfronthosting.co.za>


Kristj?n Valur J?nsson <kristjan at ccpgames.com> added the comment:

That was fast!  I wish more of my suggestions were greeted with such enthusiasm :)

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

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

From metatracker at psf.upfronthosting.co.za  Wed Apr 11 21:38:42 2012
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Kristj=C3=A1n_Valur_J=C3=B3nsson?=)
Date: Wed, 11 Apr 2012 19:38:42 +0000
Subject: [Tracker-discuss] [issue456] Add user links to roundup users
In-Reply-To: <1334151020.0.0.534784635455.issue456@psf.upfronthosting.co.za>
Message-ID: <1334173122.47.0.63451617901.issue456@psf.upfronthosting.co.za>


Kristj?n Valur J?nsson <kristjan at ccpgames.com> added the comment:

Attempting to edit the new "homepage" field on bugs.python.org results in an error:  You do not have permission to edit user

----------
status: resolved -> in-progress

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

From metatracker at psf.upfronthosting.co.za  Sat Apr 14 02:00:03 2012
From: metatracker at psf.upfronthosting.co.za (R David Murray)
Date: Sat, 14 Apr 2012 00:00:03 +0000
Subject: [Tracker-discuss] [issue445] xapian index appears to be incomplete
In-Reply-To: <1333245067.12.0.362344366419.issue445@psf.upfronthosting.co.za>
Message-ID: <1334361603.19.0.49399922058.issue445@psf.upfronthosting.co.za>


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

Fixed in r88947.  The xapian find function was only returning the first 10 results, and many of *those* got filtered out because they were inside file objects, which we don't include in search results by default.

Interestingly, although we host the round up bug tracker (which I hadn't realized), this doesn't fix the search for 'xapian' there, which still returns no results.  It returns three hits if I search in 'title', but none in 'all text'.  I wonder if its index needs to be rebuilt.

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

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

From metatracker at psf.upfronthosting.co.za  Sun Apr 15 12:26:09 2012
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Kristj=C3=A1n_Valur_J=C3=B3nsson?=)
Date: Sun, 15 Apr 2012 10:26:09 +0000
Subject: [Tracker-discuss] [issue458] editing "homepage" field is not
	possible
Message-ID: <1334485569.34.0.217371137544.issue458@psf.upfronthosting.co.za>


New submission from Kristj?n Valur J?nsson <kristjan at ccpgames.com>:

Editing the new "Homepage" field for the user on bugs.python.org. is not possible, the user is greeted with the "You do not have permission to edit user" message.  All other fields are editable.

----------
assignedto: loewis
messages: 2459
nosy: kristjan.jonsson, loewis
priority: bug
status: unread
title: editing "homepage" field is not possible

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

From metatracker at psf.upfronthosting.co.za  Mon Apr 16 17:33:04 2012
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v=2E_L=C3=B6wis?=)
Date: Mon, 16 Apr 2012 15:33:04 +0000
Subject: [Tracker-discuss] [issue373] Add 'module' field to tracker
In-Reply-To: <87ei4ub9sk.fsf@uwakimon.sk.tsukuba.ac.jp>
Message-ID: <4F8C3BAE.1020209@v.loewis.de>


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

>  > Having a way for non-commiters to indicate to everyone
> 
> In XEmacs's Roundup we allow any user to assign themselves an
> "assignable" Role (which is misnamed "Developer").  All this does is
> add them to the list that pops up for "Assigned-To" (there is also an
> assign-to-me option there which allows anybody to assign an issue to
> themselves, whether they have the Developer Role or not).

In Python, we don't do assignments. What I could imagine is an
"ask for help" feature, where people indicate components that they
are willing to work on, along with an "ask for help" button available
to developers that sends anybody interested one of the relevant
components a help request. Triagers could then send a message to
these volunteers indicating what work needs to be done.

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

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

From metatracker at psf.upfronthosting.co.za  Mon Apr 16 23:10:25 2012
From: metatracker at psf.upfronthosting.co.za (anatoly techtonik)
Date: Mon, 16 Apr 2012 21:10:25 +0000
Subject: [Tracker-discuss] [issue373] Add 'module' field to tracker
In-Reply-To: <4F8C3BAE.1020209@v.loewis.de>
Message-ID: <CAPkN8xL+FRsqB34BMEeJ3JghHRVVkQWnBHa020pRYgCTp881Pw@mail.gmail.com>


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

On Mon, Apr 16, 2012 at 6:33 PM, Martin v. L?wis
<metatracker at psf.upfronthosting.co.za> wrote:
>> ?> Having a way for non-commiters to indicate to everyone
>>
>> In XEmacs's Roundup we allow any user to assign themselves an
>> "assignable" Role (which is misnamed "Developer"). ?All this does is
>> add them to the list that pops up for "Assigned-To" (there is also an
>> assign-to-me option there which allows anybody to assign an issue to
>> themselves, whether they have the Developer Role or not).
>
> In Python, we don't do assignments. What I could imagine is an
> "ask for help" feature, where people indicate components that they
> are willing to work on, along with an "ask for help" button available
> to developers that sends anybody interested one of the relevant
> components a help request. Triagers could then send a message to
> these volunteers indicating what work needs to be done.

I believe that was not an assignment in classical management style.
The primary purpose is to be able to assign a ticket to yourself to
become a ticket owner. You're basically "taking a task", but you can
also agree with somebody who triages tickets to assign interesting
stuff to you, so that it can popup in your personal Roadmap
automatically ('module' field which is a topic of this ticket can also
be used to add all interested subscribers) . You can then rearrange
items in your personal Roadmap list and the ordinary number of the
item in this list will then be displayed next to your name in ticket.
A separate feature(creep) is to enable tickets with several owners -
people, who are actually committed to do something about this ticket.
This gives people an ability to coordinate by looking into each
other's Roadmaps. This should also answer the question 'why my bug is
opened here for 5 years already?'.

The ticket owner know the stuff better and can can be coordinator
(mentor) for the task. Ticket owner with less number near to hos name
is more likely to work on it than other. Empty "owner" means that task
is not interesting, and somebody is free to take and a candy for
developers out of it.

I am not opposing "ask for help" feature proposal, but find it strange:
1. It implies that there is a separation between developers and non-developers
2. And that developers need help
3. That developers nudge volunteers to help them
I prefer the scenario where everybody is free to participate
regardless of the status. For example, you don't need to be a
developer to draw diagrams, write tests, PEPs, user stories, improve
tracker and python web site.

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

From metatracker at psf.upfronthosting.co.za  Tue Apr 17 01:37:24 2012
From: metatracker at psf.upfronthosting.co.za (Ezio Melotti)
Date: Mon, 16 Apr 2012 23:37:24 +0000
Subject: [Tracker-discuss] [issue373] Add 'module' field to tracker
In-Reply-To: <1296578034.58.0.494679196594.issue373@psf.upfronthosting.co.za>
Message-ID: <1334619444.33.0.0215673599496.issue373@psf.upfronthosting.co.za>


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

Something similar to the "module" field already exists: the nosy list autocomplete can search for module maintainers and developers can add themselves if they are interested to specific modules.

One possible option is to move this information from the devguide to the tracker, so that everyone (including non-developers) can list the modules they want to maintain.
If this happens, we could also move the "interest areas" to the tracker, and possibly merge them with and/or use them to replace the "components".  The result would be a few fixed set of tags (module names, interest areas) that can be used to find people interested to a specific issue and possibly to mark/tag the issue.
If we want to add another layer of complexity we might also let the user decide what kind of notification they want to have (auto-assign, auto-nosy, just some visual hint for potentially interesting issues).

Once people agree on one of these ideas, someone will have to turn it in a concrete proposal (that should include both the UI changes necessary and how the whole thing is supposed to work), and then someone will have to implement it.


>>>> * there are hundreds of modules;
>>> How many exactly? I doubt there is more than hundred.
>> More than two hundreds.
> How many exactly?

209 on the "experts" page, 265 in help('modules').  Note that help('modules') lists some C _modules (like several _codecs_*) that are not listed on the "experts" page but otoh it just lists the root of packages, without listing all the subpackages (e.g. only 'xml' instead of 'xml.dom', 'xml.sax', 'xml.etree').

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

From metatracker at psf.upfronthosting.co.za  Tue Apr 17 03:43:40 2012
From: metatracker at psf.upfronthosting.co.za (Ezio Melotti)
Date: Tue, 17 Apr 2012 01:43:40 +0000
Subject: [Tracker-discuss] [issue448] Login not working (mostly)
In-Reply-To: <1333644181.93.0.427714955722.issue448@psf.upfronthosting.co.za>
Message-ID: <1334627020.03.0.714350385282.issue448@psf.upfronthosting.co.za>


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

If you e.g. click on the logout link, you get redirected to http://bugs.python.org/?@action=logout.  IIUC you get an error because if e.g. you try to login again, the same url is used as target by the login form (<form method="post" action="#">) so the server receives an action via POST (<input type="hidden" name="@action" value="Login" />) plus the old one via GET (@action=logout in the URL).  I had this problem while switching between users, and the workaround was to go to homepage (e.g. bugs.python.org) after the logout in order to avoid having extra "action" in the URL when I was logging in again.
If we change the target to use only the name of the page, we should be able to solve the problem, but we will lose the ability to get back to the exact page we were visiting after a login (that shouldn't be a big problem though).
Note that the problem also affects the "show issue" form and possibly other forms.

----------
nosy: +ezio.melotti
priority: urgent -> bug
status: unread -> chatting

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

From metatracker at psf.upfronthosting.co.za  Tue Apr 17 06:25:54 2012
From: metatracker at psf.upfronthosting.co.za (Ezio Melotti)
Date: Tue, 17 Apr 2012 04:25:54 +0000
Subject: [Tracker-discuss] [issue457] Modules not shown in help
Message-ID: <1334636754.03.0.035155505251.issue457@psf.upfronthosting.co.za>


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

Could you elaborate a bit more?

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

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

From metatracker at psf.upfronthosting.co.za  Tue Apr 17 06:51:46 2012
From: metatracker at psf.upfronthosting.co.za (Ezio Melotti)
Date: Tue, 17 Apr 2012 04:51:46 +0000
Subject: [Tracker-discuss] [issue437] Ignore a dot in urls if it's the last
	character
In-Reply-To: <1330951468.67.0.643931051848.issue437@psf.upfronthosting.co.za>
Message-ID: <1334638306.29.0.831820841181.issue437@psf.upfronthosting.co.za>


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

I was pretty sure I fixed this already, but I tried on a local instance on my laptop and it's not working, so I'm probably just confusing this problem with <http://issues.roundup-tracker.org/issue2550657>.  The fact that I can't find any tests for it around seems to confirm this (or maybe I have local changes on my home pc since iirc it's working there).
Once I get home I'll double check this and then fix it.

----------
assignedto:  -> ezio.melotti

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

From metatracker at psf.upfronthosting.co.za  Tue Apr 17 15:17:21 2012
From: metatracker at psf.upfronthosting.co.za (R David Murray)
Date: Tue, 17 Apr 2012 13:17:21 +0000
Subject: [Tracker-discuss] [issue448] Login not working (mostly)
In-Reply-To: <1333644181.93.0.427714955722.issue448@psf.upfronthosting.co.za>
Message-ID: <1334668641.88.0.204746849594.issue448@psf.upfronthosting.co.za>


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

Oh, I hate web sites that don't take me back to exactly the page I was on after I log in.  -1 on that proposal.  We could strip @action's from the URL, though, that would make sense.

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

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

From metatracker at psf.upfronthosting.co.za  Tue Apr 17 16:23:38 2012
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v=2E_L=C3=B6wis?=)
Date: Tue, 17 Apr 2012 14:23:38 +0000
Subject: [Tracker-discuss] [issue448] Login not working (mostly)
In-Reply-To: <1333644181.93.0.427714955722.issue448@psf.upfronthosting.co.za>
Message-ID: <1334672618.03.0.294744113004.issue448@psf.upfronthosting.co.za>


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

Ezio: but you would have a green bar "You are logged out - clear this message", right? And if you follow the "clear this message" link, you get to a URL with no action, right? So I doubt this is what Terry did.

Terry: can you reproduce this (I can't)? If so, please give exact reproduction steps. How exactly did you go to bugs.python.org?

I can reproduce it for the search case. In that case, stripping the action is not a good idea.

I think the __came_from field should include query parameters.

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

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

From metatracker at psf.upfronthosting.co.za  Tue Apr 17 19:39:12 2012
From: metatracker at psf.upfronthosting.co.za (Ezio Melotti)
Date: Tue, 17 Apr 2012 17:39:12 +0000
Subject: [Tracker-discuss] [issue448] Login not working (mostly)
In-Reply-To: <1333644181.93.0.427714955722.issue448@psf.upfronthosting.co.za>
Message-ID: <1334684352.47.0.861055713491.issue448@psf.upfronthosting.co.za>


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

> Oh, I hate web sites that don't take me back to exactly the page I was on after I log in.

I said it wouldn't be a big problem because if I'm not logged in already, I usually do it to reply to a message, and in that case you would be sent back to the right issue page (issueXXXXX).  It wouldn't work for searches or one of the "summary" query though, because it would redirect to the "issue" page.

> Ezio: but you would have a green bar "You are logged out - clear this message", right?

Yes

> And if you follow the "clear this message" link, you get to a URL with no action, right?

Yes, but I usually just click on the logo on the top-left (note that logging out already redirects to the list of issues).

> So I doubt this is what Terry did.

I only encountered this problem while switching accounts on my test tracker (so logout+login), it never happened to me on the regular tracker (probably because I never had to combine login/logout/search there).

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

From metatracker at psf.upfronthosting.co.za  Wed Apr 18 00:08:19 2012
From: metatracker at psf.upfronthosting.co.za (Terry Reedy)
Date: Tue, 17 Apr 2012 22:08:19 +0000
Subject: [Tracker-discuss] [issue448] Login not working (mostly)
In-Reply-To: <1333644181.93.0.427714955722.issue448@psf.upfronthosting.co.za>
Message-ID: <1334700499.58.0.758944844249.issue448@psf.upfronthosting.co.za>


Terry Reedy <tjreedy at udel.edu> added the comment:

Ezio is correct that the problem is having an 'action=xxx' in the url while doing a login. Logout -- back to main page but with url such as
http://bugs.python.org/issue?@action=logout&@pagesize=50&@startwith=0
instead of simple
bugs.python.org
(how I usually start from history) is the obvious way to trigger it.
I am not sure how I triggered this. Perhaps I hit 'logout' instead of 'your details'.

Why is 'action=logout' in the url? It has already happened and is not to be repeated. The remainder is not needed as it is the default. In this case, http:bugs.python.org would be enough, except maybe for a page to return to. Or the action should be, if anything 'login', not logout.

The other way to trigger the problem is to go to site, do a search, and get to a url is something like the following, with most invisible
http://bugs.python.org/issue?%40search_text=module&ignore=file%3Acontent&title=&%40columns=title&id=&%40columns=id&stage=&creation=&creator=&activity=&%40columns=activity&%40sort=activity&actor=&nosy=&type=&components=&versions=&dependencies=&assignee=&keywords=&priority=&%40group=priority&status=1&%40columns=status&resolution=&nosy_count=&message_count=&%40pagesize=50&%40startwith=0&%40action=search
including the 'action=search' at the end. Now remember "Oh, I forgot to login" and hit login. Red message. This is a bug in my opinion.

Here, perhaps the url is needed to return to the page, but does the search need to be repeated? Even if so, why are multiple actions prohibited?

I usually don't bother or remember to login until I am on an issue page, whose url has no action, and decide I want to comment or change headers. Or I go directly to an issue page from the Friday report. So I am probably wrong about problem being new, except to me.

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

From metatracker at psf.upfronthosting.co.za  Wed Apr 18 01:59:29 2012
From: metatracker at psf.upfronthosting.co.za (Ezio Melotti)
Date: Tue, 17 Apr 2012 23:59:29 +0000
Subject: [Tracker-discuss] [issue448] Login not working (mostly)
In-Reply-To: <1333644181.93.0.427714955722.issue448@psf.upfronthosting.co.za>
Message-ID: <1334707169.45.0.844229758831.issue448@psf.upfronthosting.co.za>


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

> Why is 'action=logout' in the url? It has already happened and is not to be repeated.

IIUC this happens because Roundup uses GET for the logout, so in order to logout you have to go to a page that contains action=logout in the URL -- e.g. the page you go to by clicking the "Logout" link.

> Here, perhaps the url is needed to return to the page, but
> does the search need to be repeated?

Most likely, unless the login/logout is implemented via AJAX (but that's impractical since the content of the page usually changes when you log in/out).

> Even if so, why are multiple actions prohibited?

The problem here is that Roundup is mixing GET and POST, normally you would have only one action, and having more actions might result in a conflict (e.g. login+logout).  Instead of giving an error Roundup could ignore the GET action if there's already a POST one, or use POST for the logout too.

> I usually don't bother or remember to login until I am on an issue page,
> whose url has no action, and decide I want to comment or change headers.

This is what I usually do, that's why I said that usually it wouldn't be a problem removing all the GET args from the URL.

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

From metatracker at psf.upfronthosting.co.za  Wed Apr 18 07:50:17 2012
From: metatracker at psf.upfronthosting.co.za (py.user)
Date: Wed, 18 Apr 2012 05:50:17 +0000
Subject: [Tracker-discuss] [issue459] Add to the search of bugs.python.org
	ranges for creation	and activity
Message-ID: <1334728217.37.0.981108360736.issue459@psf.upfronthosting.co.za>


New submission from py.user <bugzilla-mail-box at yandex.ru>:

It would be able to find topics for last five days or last month or year

----------
messages: 2471
nosy: py.user
priority: wish
status: unread
title: Add to the search of bugs.python.org ranges for creation and activity

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

From metatracker at psf.upfronthosting.co.za  Wed Apr 18 08:02:15 2012
From: metatracker at psf.upfronthosting.co.za (Ezio Melotti)
Date: Wed, 18 Apr 2012 06:02:15 +0000
Subject: [Tracker-discuss] [issue459] Add to the search of bugs.python.org
	ranges for creation	and activity
In-Reply-To: <1334728217.37.0.981108360736.issue459@psf.upfronthosting.co.za>
Message-ID: <1334728935.8.0.13504513021.issue459@psf.upfronthosting.co.za>


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

That should be already possible if you click on the "Search" link in the left sidebar.

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

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

From techtonik at gmail.com  Wed Apr 18 08:24:40 2012
From: techtonik at gmail.com (anatoly techtonik)
Date: Wed, 18 Apr 2012 09:24:40 +0300
Subject: [Tracker-discuss] Kill vendor path
Message-ID: <CAPkN8xJUfDv-0VnU4Ue0YtizVE4f_DKEtJRA_T60qUdY1hC+_w@mail.gmail.com>

Hi,

http://svn.python.org/view/tracker/ contains vendor/ path, which is 5
years old. Developer docs say that this path is used to track
python.org modifications with upstream. It is not true, because
vendor/ contains 1.3.2 and instances use 1.4.19  Because nobody uses
vendor/ I propose to move it out of the way by deleting. Those who
need the historical version, will find it in SVN history together with
the code that actually uses this vendor path.
--
anatoly t.

From metatracker at psf.upfronthosting.co.za  Wed Apr 18 08:45:53 2012
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v=2E_L=C3=B6wis?=)
Date: Wed, 18 Apr 2012 06:45:53 +0000
Subject: [Tracker-discuss] [issue448] Login not working (mostly)
In-Reply-To: <1334700499.58.0.758944844249.issue448@psf.upfronthosting.co.za>
Message-ID: <20120418084551.Horde.83i4UNjz9kRPjmMfkdgybgA@webmail.df.eu>


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

> Why is 'action=logout' in the url? It has already happened

Wrong. The URL you are seeing is the very one that did the
logout. This is how web browsers work: they show you the URL
that corresponds to the page you are seeing. Likewise for
your other suggestions and questions.

----------
title: Login not working with 'get' action -> Login not working (mostly)

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

From metatracker at psf.upfronthosting.co.za  Wed Apr 18 10:21:59 2012
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v=2E_L=C3=B6wis?=)
Date: Wed, 18 Apr 2012 08:21:59 +0000
Subject: [Tracker-discuss] [issue459] Add to the search of bugs.python.org
	ranges for creation	and activity
In-Reply-To: <1334728217.37.0.981108360736.issue459@psf.upfronthosting.co.za>
Message-ID: <1334737319.3.0.487409754422.issue459@psf.upfronthosting.co.za>


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

The date specification should be better documented, though: either by reference, or by copying from

http://roundup.sourceforge.net/doc-1.0/user_guide.html#date-properties

Your examples are specified as "from -5d", "from -1m", and "from -1y"

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

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

From metatracker at psf.upfronthosting.co.za  Wed Apr 18 13:21:42 2012
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v=2E_L=C3=B6wis?=)
Date: Wed, 18 Apr 2012 11:21:42 +0000
Subject: [Tracker-discuss] [issue342] remove "phone" field for users
In-Reply-To: <1277934377.76.0.701119970252.issue342@psf.upfronthosting.co.za>
Message-ID: <1334748102.83.0.325255544959.issue342@psf.upfronthosting.co.za>


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

This is now fixed in r88948.

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

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

From metatracker at psf.upfronthosting.co.za  Wed Apr 18 13:31:12 2012
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v=2E_L=C3=B6wis?=)
Date: Wed, 18 Apr 2012 11:31:12 +0000
Subject: [Tracker-discuss] [issue445] xapian index appears to be incomplete
In-Reply-To: <1333245067.12.0.362344366419.issue445@psf.upfronthosting.co.za>
Message-ID: <1334748672.79.0.212290633471.issue445@psf.upfronthosting.co.za>


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

Unfortunately, the roundup tracker itself is unmaintained, ever since Stefan Seefeld left. I have now reindexed the setuptools tracker, and the search for "xapian" does bring up some issues.

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

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

From metatracker at psf.upfronthosting.co.za  Thu Apr 19 00:22:08 2012
From: metatracker at psf.upfronthosting.co.za (py.user)
Date: Wed, 18 Apr 2012 22:22:08 +0000
Subject: [Tracker-discuss] [issue459] Add to the search of bugs.python.org
	ranges for creation	and activity
In-Reply-To: <1334728217.37.0.981108360736.issue459@psf.upfronthosting.co.za>
Message-ID: <1334787728.04.0.224745003011.issue459@psf.upfronthosting.co.za>


py.user <bugzilla-mail-box at yandex.ru> added the comment:

start;end works (thanks to loewis)
there is no info in the search about capabilities
and "Tracker Documentation" doesn't describe them

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

From metatracker at psf.upfronthosting.co.za  Thu Apr 19 11:36:03 2012
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v=2E_L=C3=B6wis?=)
Date: Thu, 19 Apr 2012 09:36:03 +0000
Subject: [Tracker-discuss] [issue459] Add to the search of bugs.python.org
	ranges for creation	and activity
In-Reply-To: <1334728217.37.0.981108360736.issue459@psf.upfronthosting.co.za>
Message-ID: <1334828163.11.0.239097901091.issue459@psf.upfronthosting.co.za>


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

This is now fixed in r88949.

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

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

From metatracker at psf.upfronthosting.co.za  Thu Apr 19 13:35:47 2012
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v=2E_L=C3=B6wis?=)
Date: Thu, 19 Apr 2012 11:35:47 +0000
Subject: [Tracker-discuss] [issue323] email is not obfuscated in the msg
In-Reply-To: <1267435647.66.0.658210680138.issue323@psf.upfronthosting.co.za>
Message-ID: <1334835347.82.0.785716926521.issue323@psf.upfronthosting.co.za>


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

I'm declaring this resolved (no change), with the rationale given by Daniel (ajaksu2). If users really don't want their emails published, we should disable them altogether (option 1). However, users apparently are not strongly requesting this, plus Daniel's point on being able to reply directly is valid.

If users really need their email addresses covered, they can submit new issues here (or reopen this one), and we'll reconsider.

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

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

From metatracker at psf.upfronthosting.co.za  Fri Apr 20 17:45:12 2012
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v=2E_L=C3=B6wis?=)
Date: Fri, 20 Apr 2012 15:45:12 +0000
Subject: [Tracker-discuss] [issue442] Upgrade Debian
In-Reply-To: <1332688612.07.0.744642194464.issue442@psf.upfronthosting.co.za>
Message-ID: <1334936712.54.0.363485417633.issue442@psf.upfronthosting.co.za>


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

I have now edited /etc/apache2/ports.conf, /etc/ssh/sshd_config, and /etc/postfix/main.cf to enable IPv6.

For Postfix, I would appreciate a review of the changes; I added inet_protcols and edited inet_interfaces and mynetworks.

I also put the name into DNS.

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

From metatracker at psf.upfronthosting.co.za  Fri Apr 20 18:42:16 2012
From: metatracker at psf.upfronthosting.co.za (Izak Burger)
Date: Fri, 20 Apr 2012 16:42:16 +0000
Subject: [Tracker-discuss] [issue442] Upgrade Debian
In-Reply-To: <1334936712.54.0.363485417633.issue442@psf.upfronthosting.co.za>
Message-ID: <CAGscxN3it3YjUvd6FCw4B-Lfx_ybYyY_9d4+daYHzdbAjMk8QQ@mail.gmail.com>


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

On Fri, Apr 20, 2012 at 5:45 PM, Martin v. L?wis
<metatracker at psf.upfronthosting.co.za> wrote:
> For Postfix, I would appreciate a review of the changes; I added inet_protcols and edited inet_interfaces and mynetworks.

I'm not much of an ipv6 expert, but what I see looks like the
equivalent of $myipaddress/32 in ipv4 land, and is therefore in order.

One other note: On linux you unfortunately need to set up firewalling
for ipv4 and ipv6 seperately. We have a very nice ipv4 firewall in
place, but there is no ipv6 firewall. This is not really a big
problem, because nothing listens on ipv6 other than the services we
want open anyway, but it could affect future services, one should
always bind to localhost explicitly.

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

From metatracker at psf.upfronthosting.co.za  Sun Apr 22 07:00:38 2012
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v=2E_L=C3=B6wis?=)
Date: Sun, 22 Apr 2012 05:00:38 +0000
Subject: [Tracker-discuss] [issue372] Default search missed matching issue
	title for "capi"
In-Reply-To: <1296391426.25.0.112828803106.issue372@psf.upfronthosting.co.za>
Message-ID: <1335070838.72.0.240251662478.issue372@psf.upfronthosting.co.za>


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

rmtew: search is definitely case insensitive. I cannot reproduce your report; the search for "UDP" yields plenty results.

The issue here is that the search only looks for whole words indeed, with words being defined by r'(?u)\b\w{%d,%d}\b'. As the underscore counts as a word letter, search for "capi" doesn't find "test_capi".

I don't think that having a complete substring search is desirable. However, IMO, _ should not be considered as a letter; alternatively each word should be split around underscores, and these should be added to the words of a property as well.

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

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

From metatracker at psf.upfronthosting.co.za  Sun Apr 22 07:17:31 2012
From: metatracker at psf.upfronthosting.co.za (Nick Coghlan)
Date: Sun, 22 Apr 2012 05:17:31 +0000
Subject: [Tracker-discuss] [issue372] Default search missed matching issue
	title for "capi"
In-Reply-To: <1296391426.25.0.112828803106.issue372@psf.upfronthosting.co.za>
Message-ID: <1335071851.22.0.951840724799.issue372@psf.upfronthosting.co.za>


Nick Coghlan <ncoghlan at gmail.com> added the comment:

+1 for Martin's suggested fix - treating '_' as a word separator when building the word index.

Unfortunately, throwing Google at the problem doesn't return especially useful results, because it doesn't understand the logical structure of Roundup issues and returns direct links to individual comments instead of the issues that they relate to: "https://www.google.com/search?q=site%3Abugs.python.org%20capi#hl=en&sclient=psy-ab&q=site:bugs.python.org+capi+-ext%3Adiff+-ext%3Apatch&oq=site:bugs.python.org+capi+-ext%3Adiff+-ext%3Apatch"

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

From metatracker at psf.upfronthosting.co.za  Sun Apr 29 07:40:33 2012
From: metatracker at psf.upfronthosting.co.za (Ezio Melotti)
Date: Sun, 29 Apr 2012 05:40:33 +0000
Subject: [Tracker-discuss] [issue119] Tracker Documentation
In-Reply-To: <1185340066.06.0.0886892361436.issue119@psf.upfronthosting.co.za>
Message-ID: <1335678033.54.0.728576284436.issue119@psf.upfronthosting.co.za>


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

Fixed in http://hg.python.org/devguide/rev/252e2aabc87a

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

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