From metatracker at psf.upfronthosting.co.za  Fri Dec  3 06:59:42 2010
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?=C3=89ric_Araujo?=)
Date: Fri, 03 Dec 2010 05:59:42 +0000
Subject: [Tracker-discuss] [issue362] Mass-edit distutils bugs fields
In-Reply-To: <1291355982.58.0.128388352603.issue362@psf.upfronthosting.co.za>
Message-ID: <1291355982.58.0.128388352603.issue362@psf.upfronthosting.co.za>


New submission from ?ric Araujo <merwok at netwok.org>:

I would like this query to be performed: for each open bug with the Distutils component, if Distutils2 component is not set, add it; if eric.araujo (user 7641) is not in nosy, add him.

The first part is to get all open bugs under one component, to have only one link to give to people.  The second part is to make sure I don?t miss messages.

Optional: if the type is feature request, remove Distutils, remove versions, add version ?3rd party?.

Optional: if the type is not feature request, set versions to 3.2, 3.1, 2.7, 3rd party.

Thanks in advance.

----------
messages: 1871
nosy: eric.araujo, loewis
priority: wish
status: unread
title: Mass-edit distutils bugs fields

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

From metatracker at psf.upfronthosting.co.za  Mon Dec  6 08:53:24 2010
From: metatracker at psf.upfronthosting.co.za (Georg Brandl)
Date: Mon, 06 Dec 2010 07:53:24 +0000
Subject: [Tracker-discuss] [issue363] auto-nosy release manager(s) on
	release blockers
In-Reply-To: <1291622004.94.0.383802311228.issue363@psf.upfronthosting.co.za>
Message-ID: <1291622004.94.0.383802311228.issue363@psf.upfronthosting.co.za>


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

What do others think?  Is this feasible?

(Rough patch attached; untested.)

----------
files: autonosy_rm.diff
messages: 1872
nosy: gbrandl
priority: wish
status: unread
title: auto-nosy release manager(s) on release blockers

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue363>
_______________________________________________________
-------------- next part --------------
Index: python-dev/detectors/autonosy.py
===================================================================
--- python-dev/detectors/autonosy.py	(Revision 87094)
+++ python-dev/detectors/autonosy.py	(Arbeitskopie)
@@ -4,14 +4,16 @@
 # Python 2.3 ... 2.6 compatibility:
 from roundup.anypy.sets_ import set
 
+RELEASE_MANAGERS = {
+    'Python 2.6': 'barry',
+    'Python 2.7': 'benjamin.peterson',
+    'Python 3.1': 'benjamin.peterson',
+    'Python 3.2': 'georg.brandl',
+}
+
 def autonosy(db, cl, nodeid, newvalues):
+    components = newvalues.get('components', [])
 
-    if 'components' not in newvalues:
-        # Without components, nobody needs to be added as nosy
-        return
-    else:
-        components = newvalues['components']
-
     nosy = set()
     if 'nosy' in newvalues:
         new_nosy = newvalues.get('nosy', [])
@@ -26,6 +28,13 @@
         users = db.component.get(component, 'add_as_nosy')
         nosy |= set(users)
 
+    if 'priority' in newvalues:
+        if db.priority.get(newvalues['priority'], 'name') == 'release blocker':
+            for version in newvalues.get('versions', []):
+                name = db.version.get(version, 'name')
+                if name in RELEASE_MANAGERS:
+                    nosy.add(RELEASE_MANAGERS[name])
+
     newvalues['nosy'] = list(nosy)
 
 

From metatracker at psf.upfronthosting.co.za  Mon Dec  6 09:37:15 2010
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v=2E_L=C3=B6wis?=)
Date: Mon, 06 Dec 2010 08:37:15 +0000
Subject: [Tracker-discuss] [issue363] auto-nosy release manager(s) on
	release blockers
In-Reply-To: <1291622004.94.0.383802311228.issue363@psf.upfronthosting.co.za>
Message-ID: <1291624635.7.0.963585661906.issue363@psf.upfronthosting.co.za>


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

I think the patch is wrong (it needs to lookup ids from strings for users, priorities and versions), but otherwise, it is feasible.

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

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

From metatracker at psf.upfronthosting.co.za  Fri Dec 10 18:54:20 2010
From: metatracker at psf.upfronthosting.co.za (milko.krachounov)
Date: Fri, 10 Dec 2010 17:54:20 +0000
Subject: [Tracker-discuss] [issue364] Python Website: Color scheme of the
	issues tracker's	textarea background
In-Reply-To: <1292003660.3.0.901269998435.issue364@psf.upfronthosting.co.za>
Message-ID: <1292003660.3.0.901269998435.issue364@psf.upfronthosting.co.za>


New submission from milko.krachounov <psf.meta at milko.3mhz.net>:

The CSS for the issues tracker (for example,
http://bugs.python.org/issue?@template=item and http://psf.upfronthosting.co.za/roundup/meta/issue?@template=item) specifies a background for the 
textarea on focus, but it doesn't specify 1) a background colour for the 
textarea without focus, 2) a foreground colour. The result is that on a white-
on-black colour scheme the textarea appears with white text on yellow 
background that is unreadable.

>From the CSS of the tracker on bugs.python.org:
textarea {
  font-family: monospace;
}

textarea:focus, select:focus {
  background-color: #ffffc0;
}

----------
messages: 1874
nosy: milko.krachounov
priority: bug
status: unread
title: Python Website: Color scheme of the issues tracker's textarea background

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

From techtonik at gmail.com  Fri Dec 10 20:11:40 2010
From: techtonik at gmail.com (anatoly techtonik)
Date: Fri, 10 Dec 2010 21:11:40 +0200
Subject: [Tracker-discuss] Fwd: [issue20] Add in SVN plugin?
In-Reply-To: <1292008202.45.0.0872149497881.issue20@psf.upfronthosting.co.za>
References: <1292008202.45.0.0872149497881.issue20@psf.upfronthosting.co.za>
Message-ID: <AANLkTin2FZmFOvd80oKm++ZHQw8X7+z6OOV4Vrm8x8Ne@mail.gmail.com>

This message is classified as spam. Do I need to file a report or it's ok?
--
anatoly t.




---------- Forwarded message ----------
From: anatoly techtonik <metatracker at psf.upfronthosting.co.za>
Date: Fri, Dec 10, 2010 at 9:10 PM
Subject: [issue20] Add in SVN plugin?
To: techtonik at gmail.com



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

More "outdated" ideas http://bugs.python.org/issue10659

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

From skip at pobox.com  Fri Dec 10 20:40:05 2010
From: skip at pobox.com (skip at pobox.com)
Date: Fri, 10 Dec 2010 13:40:05 -0600
Subject: [Tracker-discuss] Fwd: [issue20] Add in SVN plugin?
In-Reply-To: <AANLkTin2FZmFOvd80oKm++ZHQw8X7+z6OOV4Vrm8x8Ne@mail.gmail.com>
References: <1292008202.45.0.0872149497881.issue20@psf.upfronthosting.co.za>
	<AANLkTin2FZmFOvd80oKm++ZHQw8X7+z6OOV4Vrm8x8Ne@mail.gmail.com>
Message-ID: <19714.33301.248701.722329@montanaro.dyndns.org>


    anatoly> This message is classified as spam. Do I need to file a report or it's ok?

I don't know.  I doubt at this point we need any spam filtering on the
tracker.  Martin's last changes to compare subscribe time with first issue
creation time seem to have solved most/all spam problems.

Skip

From martin at v.loewis.de  Fri Dec 10 20:56:48 2010
From: martin at v.loewis.de (=?ISO-8859-1?Q?=22Martin_v=2E_L=F6wis=22?=)
Date: Fri, 10 Dec 2010 20:56:48 +0100
Subject: [Tracker-discuss] Fwd: [issue20] Add in SVN plugin?
In-Reply-To: <19714.33301.248701.722329@montanaro.dyndns.org>
References: <1292008202.45.0.0872149497881.issue20@psf.upfronthosting.co.za>	<AANLkTin2FZmFOvd80oKm++ZHQw8X7+z6OOV4Vrm8x8Ne@mail.gmail.com>
	<19714.33301.248701.722329@montanaro.dyndns.org>
Message-ID: <4D028600.6080702@v.loewis.de>

>     anatoly> This message is classified as spam. Do I need to file a report or it's ok?

No, I have unclassified it.

> I don't know.  I doubt at this point we need any spam filtering on the
> tracker.  Martin's last changes to compare subscribe time with first issue
> creation time seem to have solved most/all spam problems.

Sounds fine to me. I'll stop the automatic classification, but leave the
user interface so that users can still classify the messages manually.

Regards,
Martin

From metatracker at psf.upfronthosting.co.za  Wed Dec 15 04:00:58 2010
From: metatracker at psf.upfronthosting.co.za (Ezio Melotti)
Date: Wed, 15 Dec 2010 03:00:58 +0000
Subject: [Tracker-discuss] [issue363] auto-nosy release manager(s) on
	release blockers
In-Reply-To: <1291622004.94.0.383802311228.issue363@psf.upfronthosting.co.za>
Message-ID: <1292382058.24.0.371632408776.issue363@psf.upfronthosting.co.za>


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

I committed the patch with a couple of changes in r87253 using the user ids instead of the names.
I then further improved the patch in r87257 to also check the previous values when they are not changed, so, if the version is already set to e.g. 3.2 and the priority is changed to release blocker (and vice versa -- priority already set to release blocker and 3.2 added), the 3.2 release manager will be added anyway. Finally I fixed a bug in r87259 that gave an error message when the priority was not set.
Attached a diff of all these changes

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

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue363>
_______________________________________________________
-------------- next part --------------
Index: instances/python-dev/detectors/autonosy.py
===================================================================
--- instances/python-dev/detectors/autonosy.py	(revision 87250)
+++ instances/python-dev/detectors/autonosy.py	(revision 87259)
@@ -4,14 +4,16 @@
 # Python 2.3 ... 2.6 compatibility:
 from roundup.anypy.sets_ import set
 
+RELEASE_MANAGERS = {
+    'Python 2.6': '19',   # barry
+    'Python 2.7': '4455', # benjamin.peterson
+    'Python 3.1': '4455', # benjamin.peterson
+    'Python 3.2': '93',   # georg.brandl
+}
+
 def autonosy(db, cl, nodeid, newvalues):
+    components = newvalues.get('components', [])
 
-    if 'components' not in newvalues:
-        # Without components, nobody needs to be added as nosy
-        return
-    else:
-        components = newvalues['components']
-
     nosy = set()
     if 'nosy' in newvalues:
         new_nosy = newvalues.get('nosy', [])
@@ -26,6 +28,25 @@
         users = db.component.get(component, 'add_as_nosy')
         nosy |= set(users)
 
+    # get the new values if they changed or the already-set ones if they didn't
+    priority = 'None'
+    if 'priority' in newvalues:
+        priority_id = newvalues['priority']
+    else:
+        priority_id = db.issue.get(nodeid, 'priority')
+    if priority_id is not None:
+        priority = db.priority.get(priority_id, 'name')
+    if 'versions' in newvalues:
+        versions = newvalues.get('versions', [])
+    else:
+        versions = db.issue.get(nodeid, 'versions')
+
+    if priority == 'release blocker':
+        for version in versions:
+            name = db.version.get(version, 'name')
+            if name in RELEASE_MANAGERS:
+                nosy.add(RELEASE_MANAGERS[name])
+
     newvalues['nosy'] = list(nosy)
 
 

From metatracker at psf.upfronthosting.co.za  Wed Dec 15 04:05:46 2010
From: metatracker at psf.upfronthosting.co.za (Ezio Melotti)
Date: Wed, 15 Dec 2010 03:05:46 +0000
Subject: [Tracker-discuss] [issue364] Python Website: Color scheme of the
	issues tracker's	textarea background
In-Reply-To: <1292003660.3.0.901269998435.issue364@psf.upfronthosting.co.za>
Message-ID: <1292382346.34.0.225287136163.issue364@psf.upfronthosting.co.za>


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

Fixed in r87244 for the python-dev, meta and jython trackers.
I changed only the text color to black when the background is yellow and left it unchanged in the other cases. This means that, with your configuration, you should see white-on-black normally and black-on-yellow once you focus on the textarea.
Let me know if this is fine for you, and thanks for the report!

----------
assignedto:  -> ezio.melotti
nosy: +ezio.melotti
status: unread -> resolved

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue364>
_______________________________________________________
-------------- next part --------------
Index: instances/meta/html/style.css
===================================================================
--- instances/meta/html/style.css	(revision 83128)
+++ instances/meta/html/style.css	(working copy)
@@ -436,6 +436,7 @@
 input[type="radio"]:focus,
 input[type="password"]:focus,
 textarea:focus, select:focus {
+  color: #000000;
   background-color: #ffffc0;
 }
 
Index: instances/jython/html/style.css
===================================================================
--- instances/jython/html/style.css	(revision 83128)
+++ instances/jython/html/style.css	(working copy)
@@ -449,6 +449,7 @@
 input[type="radio"]:focus,
 input[type="password"]:focus,
 textarea:focus, select:focus {
+  color: #000000;
   background-color: #ffffc0;
 }
 
Index: instances/python-dev/html/style.css
===================================================================
--- instances/python-dev/html/style.css	(revision 83128)
+++ instances/python-dev/html/style.css	(working copy)
@@ -451,6 +451,7 @@
 input[type="radio"]:focus,
 input[type="password"]:focus,
 textarea:focus, select:focus {
+  color: #000000;
   background-color: #ffffc0;
 }
 

From metatracker at psf.upfronthosting.co.za  Wed Dec 15 22:10:18 2010
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?=C3=89ric_Araujo?=)
Date: Wed, 15 Dec 2010 21:10:18 +0000
Subject: [Tracker-discuss] [issue364] Python Website: Color scheme of the
	issues tracker's	textarea background
In-Reply-To: <1292003660.3.0.901269998435.issue364@psf.upfronthosting.co.za>
Message-ID: <1292447418.05.0.948171680938.issue364@psf.upfronthosting.co.za>


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

Thanks a bunch for fixing this, you made my day!

----------
nosy: +eric.araujo
status: resolved -> chatting

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

From metatracker at psf.upfronthosting.co.za  Wed Dec 15 22:11:24 2010
From: metatracker at psf.upfronthosting.co.za (milko.krachounov)
Date: Wed, 15 Dec 2010 21:11:24 +0000
Subject: [Tracker-discuss] [issue364] Python Website: Color scheme of the
	issues tracker's	textarea background
In-Reply-To: <1292003660.3.0.901269998435.issue364@psf.upfronthosting.co.za>
Message-ID: <1292447484.29.0.266165732453.issue364@psf.upfronthosting.co.za>


milko.krachounov <psf.meta at milko.3mhz.net> added the comment:

Works great now, thank you very much!

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

From metatracker at psf.upfronthosting.co.za  Fri Dec 24 15:22:56 2010
From: metatracker at psf.upfronthosting.co.za (ipatrol)
Date: Fri, 24 Dec 2010 14:22:56 +0000
Subject: [Tracker-discuss] [issue365] No issue exists with that id
In-Reply-To: <1293200576.2.0.44483259406.issue365@psf.upfronthosting.co.za>
Message-ID: <1293200576.2.0.44483259406.issue365@psf.upfronthosting.co.za>


New submission from ipatrol <ipatrol6010 at yahoo.com>:

I noticed this on issue 7511 specifically with http://bugs.python.org/review/7511/show (the "review" link for a patch). This doesn't appear normal, any ideas?

----------
messages: 1880
nosy: ipatrol
priority: bug
status: unread
title: No issue exists with that id

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

From metatracker at psf.upfronthosting.co.za  Mon Dec 27 00:42:57 2010
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v=2E_L=C3=B6wis?=)
Date: Sun, 26 Dec 2010 23:42:57 +0000
Subject: [Tracker-discuss] [issue365] No issue exists with that id
In-Reply-To: <1293200576.2.0.44483259406.issue365@psf.upfronthosting.co.za>
Message-ID: <1293406977.76.0.731729987761.issue365@psf.upfronthosting.co.za>


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

Does this cause a problem? There simply is no issue with that id.

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

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

From metatracker at psf.upfronthosting.co.za  Mon Dec 27 01:13:28 2010
From: metatracker at psf.upfronthosting.co.za (R David Murray)
Date: Mon, 27 Dec 2010 00:13:28 +0000
Subject: [Tracker-discuss] [issue365] No issue exists with that id
In-Reply-To: <1293200576.2.0.44483259406.issue365@psf.upfronthosting.co.za>
Message-ID: <1293408808.64.0.0617210681616.issue365@psf.upfronthosting.co.za>


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

Well, it means there's a link in the tracker (a 'review' link) that when you click on it gives an error message.  That is a bit confusing.

ipatrol: the review functionality isn't really working yet.

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

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

From metatracker at psf.upfronthosting.co.za  Mon Dec 27 01:17:39 2010
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v=2E_L=C3=B6wis?=)
Date: Mon, 27 Dec 2010 00:17:39 +0000
Subject: [Tracker-discuss] [issue365] No issue exists with that id
In-Reply-To: <1293200576.2.0.44483259406.issue365@psf.upfronthosting.co.za>
Message-ID: <1293409059.28.0.147533938605.issue365@psf.upfronthosting.co.za>


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

Sorry, I misunderstood that to mean that issue7511 simply doesn't exist.

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