From metatracker at psf.upfronthosting.co.za Sun Mar 2 17:28:16 2008 From: metatracker at psf.upfronthosting.co.za (Philipp Gortan) Date: Sun, 02 Mar 2008 16:28:16 -0000 Subject: [Tracker-discuss] [issue148] 'Make a Copy' failed In-Reply-To: <1188873360.02.0.256456370115.issue148@psf.upfronthosting.co.za> Message-ID: <1204475296.54.0.755321553403.issue148@psf.upfronthosting.co.za> Philipp Gortan added the comment: Brett, since I don't have svn commit rights, I pass this issue on to you, for testing and merging. Patch is attached, a unittest too. For a detailed analysis, see msg 1006. Thanks! ---------- assignedto: mephinet -> brett.cannon nosy: +brett.cannon status: in-progress -> testing _______________________________________________________ Meta Tracker _______________________________________________________ -------------- next part -------------- A non-text attachment was scrubbed... Name: make_a_copy.patch Type: application/octet-stream Size: 2166 bytes Desc: not available Url : http://mail.python.org/pipermail/tracker-discuss/attachments/20080302/0fff65e6/attachment.obj From metatracker at psf.upfronthosting.co.za Sun Mar 2 18:02:54 2008 From: metatracker at psf.upfronthosting.co.za (Philipp Gortan) Date: Sun, 02 Mar 2008 17:02:54 -0000 Subject: [Tracker-discuss] [issue153] trigger traceback when doing issue search on non-existent username In-Reply-To: <1189488338.51.0.328974488764.issue153@psf.upfronthosting.co.za> Message-ID: <1204477374.35.0.20122592097.issue153@psf.upfronthosting.co.za> Philipp Gortan added the comment: I *don't* get a traceback if I specify a non-existing username in the search form for "creator", "last actor" or "assigned to". However, I *do* get a traceback in the "nosy list member" field, so the first guess would be that link properties have meanwhile been fixed, but multilink properties have not. ---------- assignedto: -> mephinet nosy: +mephinet _______________________________________________________ Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Sun Mar 2 18:52:35 2008 From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v._L=C3=B6wis?=) Date: Sun, 02 Mar 2008 17:52:35 -0000 Subject: [Tracker-discuss] [issue153] trigger traceback when doing issue search on non-existent username In-Reply-To: <1189488338.51.0.328974488764.issue153@psf.upfronthosting.co.za> Message-ID: <1204480355.9.0.635981059933.issue153@psf.upfronthosting.co.za> Martin v. L?wis added the comment: Indeed, the issue with searching for invalid user names was fixed as issue179. Perhaps that can give a clue where to look for the problem. ---------- nosy: +loewis _______________________________________________________ Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Sun Mar 2 20:56:45 2008 From: metatracker at psf.upfronthosting.co.za (Brett C.) Date: Sun, 02 Mar 2008 19:56:45 -0000 Subject: [Tracker-discuss] [issue148] 'Make a Copy' failed In-Reply-To: <1188873360.02.0.256456370115.issue148@psf.upfronthosting.co.za> Message-ID: <1204487805.84.0.990718943648.issue148@psf.upfronthosting.co.za> Brett C. added the comment: Thanks for the patch, mephinet! I am not in a place right now to look this over, so I am unassigning myself. But I will email tracker-discuss to make sure someone catches the fact that there is now a patch. ---------- assignedto: brett.cannon -> _______________________________________________________ Meta Tracker _______________________________________________________ From brett at python.org Sun Mar 2 20:58:02 2008 From: brett at python.org (Brett Cannon) Date: Sun, 2 Mar 2008 11:58:02 -0800 Subject: [Tracker-discuss] Issue 148 has a patch; can someone review it? Message-ID: Philipp (who hopefully is subscribed to this lists =) came up with a patch for issue 148, but I can't review it right now. Just pinging the list directly so someone can do a review and this doesn't languish. -Brett From metatracker at psf.upfronthosting.co.za Mon Mar 3 09:02:29 2008 From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v._L=C3=B6wis?=) Date: Mon, 03 Mar 2008 08:02:29 -0000 Subject: [Tracker-discuss] [issue148] 'Make a Copy' failed In-Reply-To: <1188873360.02.0.256456370115.issue148@psf.upfronthosting.co.za> Message-ID: <1204531349.37.0.290941714139.issue148@psf.upfronthosting.co.za> Martin v. L?wis added the comment: Thanks again for the patch. I have now committed and deployed the templating.py part (as r61201), but not the test suite change, to minimize our deviation from the upstream code base. Please consider submitting the entire patch again upstream (i.e. sf.net/projects/roundup). I'll mark the issue in-progress, until this happened, or until you've indicated that you don't want to contribute it to roundup itself. ---------- nosy: +loewis status: testing -> in-progress _______________________________________________________ Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Mon Mar 3 11:17:52 2008 From: metatracker at psf.upfronthosting.co.za (Philipp Gortan) Date: Mon, 03 Mar 2008 10:17:52 -0000 Subject: [Tracker-discuss] [issue148] 'Make a Copy' failed In-Reply-To: <1188873360.02.0.256456370115.issue148@psf.upfronthosting.co.za> Message-ID: <1204539472.09.0.969244382148.issue148@psf.upfronthosting.co.za> Philipp Gortan added the comment: Thank you for committing! I created an issue upstream, sf bug #1906147, so I close this issue. ---------- status: in-progress -> resolved _______________________________________________________ Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Mon Mar 3 22:25:06 2008 From: metatracker at psf.upfronthosting.co.za (Georg Brandl) Date: Mon, 03 Mar 2008 21:25:06 -0000 Subject: [Tracker-discuss] [issue194] Rename "change note" field to "comment" In-Reply-To: <1204579506.2.0.538780610578.issue194@psf.upfronthosting.co.za> Message-ID: <1204579506.2.0.538780610578.issue194@psf.upfronthosting.co.za> New submission from Georg Brandl: The field name "Change Note" confuses many users, especially when creating a new issue. ---------- messages: 1013 nosy: gbrandl priority: wish status: unread title: Rename "change note" field to "comment" _______________________________________________________ Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Tue Mar 4 00:09:07 2008 From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v._L=C3=B6wis?=) Date: Mon, 03 Mar 2008 23:09:07 -0000 Subject: [Tracker-discuss] [issue194] Rename "change note" field to "comment" In-Reply-To: <1204579506.2.0.538780610578.issue194@psf.upfronthosting.co.za> Message-ID: <1204585747.12.0.793485126945.issue194@psf.upfronthosting.co.za> Martin v. L?wis added the comment: Assuming you still meant it to be upper-cased, this is now fixed in r61216. ---------- nosy: +loewis status: unread -> resolved _______________________________________________________ Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Thu Mar 6 20:05:38 2008 From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v._L=C3=B6wis?=) Date: Thu, 06 Mar 2008 19:05:38 -0000 Subject: [Tracker-discuss] [issue177] Set content type of .diff, .patch and .py to text/plain In-Reply-To: <1199987051.75.0.768683673246.issue177@psf.upfronthosting.co.za> Message-ID: <1204830338.62.0.946370732952.issue177@psf.upfronthosting.co.za> Martin v. L?wis added the comment: I have now changed the content-type for all existing patches. ---------- status: in-progress -> resolved _______________________________________________________ Meta Tracker _______________________________________________________ From martin at v.loewis.de Thu Mar 6 21:19:20 2008 From: martin at v.loewis.de (=?ISO-8859-1?Q?=22Martin_v=2E_L=F6wis=22?=) Date: Thu, 06 Mar 2008 21:19:20 +0100 Subject: [Tracker-discuss] Auto-Assignment Message-ID: <47D051C8.1060402@v.loewis.de> I just implemented auto-assignment for the tracker, i.e. a component can be linked to a developer so that issues mentioning the component get assigned to that developer (unless an explicit assignment is made). I have assigned 2to3 to Collin Winter (this was already implemented as a special case), and Documentation and Sphinx to Georg Brandl. Regards, Martin From metatracker at psf.upfronthosting.co.za Thu Mar 6 22:08:53 2008 From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v._L=C3=B6wis?=) Date: Thu, 06 Mar 2008 21:08:53 -0000 Subject: [Tracker-discuss] [issue195] Support report+username@bugs.python.org In-Reply-To: <1204837733.95.0.668625835363.issue195@psf.upfronthosting.co.za> Message-ID: <1204837733.95.0.668625835363.issue195@psf.upfronthosting.co.za> New submission from Martin v. L?wis: Currently, when mail gets sent to report+gvanrossum at bugs.python.org (say), it ends up in /var/spool/mail/roundup. Would it be possible to change the postfix configuration so that all mail to report+ gets processed the same as report, i.e. redirected to roundup+tracker? ---------- assignedto: izak messages: 1016 nosy: izak, loewis priority: bug status: unread title: Support report+username at bugs.python.org _______________________________________________________ Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Thu Mar 6 23:12:25 2008 From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v._L=C3=B6wis?=) Date: Thu, 06 Mar 2008 22:12:25 -0000 Subject: [Tracker-discuss] [issue35] Automatic nosy-list addition based on user preferences In-Reply-To: <87y7qhsl57.fsf@uterus.efod.se> Message-ID: <1204841545.32.0.357808170976.issue35@psf.upfronthosting.co.za> Martin v. L?wis added the comment: I would like to resolve this issue as "won't fix". I don't think users would regularly use it; instead, they can already subscribe to new-bugs-announce, and filter for keywords by email headers in any way they like (and their MUA supports). ---------- nosy: +loewis status: deferred -> resolved ______________________________________________________ Meta Tracker ______________________________________________________ From collinw at gmail.com Thu Mar 6 23:49:26 2008 From: collinw at gmail.com (Collin Winter) Date: Thu, 6 Mar 2008 14:49:26 -0800 Subject: [Tracker-discuss] [Python-Dev] Auto-Assignment In-Reply-To: <47D051C8.1060402@v.loewis.de> References: <47D051C8.1060402@v.loewis.de> Message-ID: <43aa6ff70803061449v74533819n5a4e12fe3c4f9132@mail.gmail.com> On Thu, Mar 6, 2008 at 12:19 PM, "Martin v. L?wis" wrote: > I just implemented auto-assignment for the tracker, i.e. a component > can be linked to a developer so that issues mentioning the component > get assigned to that developer (unless an explicit assignment is > made). > > I have assigned 2to3 to Collin Winter (this was already implemented > as a special case), and Documentation and Sphinx to Georg Brandl. Thanks! From metatracker at psf.upfronthosting.co.za Fri Mar 7 08:05:26 2008 From: metatracker at psf.upfronthosting.co.za (Izak Burger) Date: Fri, 07 Mar 2008 07:05:26 -0000 Subject: [Tracker-discuss] [issue195] Support report+username@bugs.python.org In-Reply-To: <1204837733.95.0.668625835363.issue195@psf.upfronthosting.co.za> Message-ID: <47D0E92A.50405@upfrontsystems.co.za> Izak Burger added the comment: Martin v. L?wis wrote: > Currently, when mail gets sent to report+gvanrossum at bugs.python.org (say), it > ends up in /var/spool/mail/roundup. Would it be possible to change the postfix > configuration so that all mail to report+ gets processed the same as > report, i.e. redirected to roundup+tracker? Good question. Postfix has this feature where mail addressed to user+suffix is delivered to user, but if that user has a .forward+suffix file in his home directory, it follows the instructions contained therein. We're already making use of this feature, mail sent to report at bugs.python.org gets aliased to roundup+tracker, which delivers it to the roundup user and follows the instructions contained in .forward+tracker. I'm not sure what postfix does in the case where there was already a suffix on the original address. I'm much more of an exim guy and I know this would be very easy in exim, but I suspect something might be possible using transports or something similar. This will require some research. ---------- status: unread -> chatting _______________________________________________________ Meta Tracker _______________________________________________________ From izak at upfrontsystems.co.za Fri Mar 7 08:05:14 2008 From: izak at upfrontsystems.co.za (Izak Burger) Date: Fri, 07 Mar 2008 09:05:14 +0200 Subject: [Tracker-discuss] [issue195] Support report+username@bugs.python.org In-Reply-To: <1204837733.95.0.668625835363.issue195@psf.upfronthosting.co.za> References: <1204837733.95.0.668625835363.issue195@psf.upfronthosting.co.za> Message-ID: <47D0E92A.50405@upfrontsystems.co.za> Martin v. L?wis wrote: > Currently, when mail gets sent to report+gvanrossum at bugs.python.org (say), it > ends up in /var/spool/mail/roundup. Would it be possible to change the postfix > configuration so that all mail to report+ gets processed the same as > report, i.e. redirected to roundup+tracker? Good question. Postfix has this feature where mail addressed to user+suffix is delivered to user, but if that user has a .forward+suffix file in his home directory, it follows the instructions contained therein. We're already making use of this feature, mail sent to report at bugs.python.org gets aliased to roundup+tracker, which delivers it to the roundup user and follows the instructions contained in .forward+tracker. I'm not sure what postfix does in the case where there was already a suffix on the original address. I'm much more of an exim guy and I know this would be very easy in exim, but I suspect something might be possible using transports or something similar. This will require some research. From metatracker at psf.upfronthosting.co.za Fri Mar 7 20:12:41 2008 From: metatracker at psf.upfronthosting.co.za (Raghuram Devarakonda) Date: Fri, 07 Mar 2008 19:12:41 -0000 Subject: [Tracker-discuss] [issue196] RE for matchig revision id's needs tweaking In-Reply-To: <1204917161.88.0.0844926023843.issue196@psf.upfronthosting.co.za> Message-ID: <1204917161.88.0.0844926023843.issue196@psf.upfronthosting.co.za> New submission from Raghuram Devarakonda: Please check http://bugs.python.org/msg63340. The revision id is not auto-linked because it is not preceded by whitespace. Replacing '(?P\s+)' with '(?P^|\s+)' would do the trick but that would still leave some other cases unmatched. I think something like "(^|[^a-zA-Z0-9])(revision|rev|r)(\s*)(\d+)($|[^a-zA-Z0-9])" would be good. Note that this regex combines the current separate regexes for revision ids. I will have to take a closer look before proposing this as patch, though. ---------- messages: 1019 nosy: draghuram priority: bug status: unread title: RE for matchig revision id's needs tweaking _______________________________________________________ Meta Tracker _______________________________________________________ From collinw at gmail.com Thu Mar 6 23:49:26 2008 From: collinw at gmail.com (Collin Winter) Date: Thu, 6 Mar 2008 14:49:26 -0800 Subject: [Tracker-discuss] [Python-Dev] Auto-Assignment In-Reply-To: <47D051C8.1060402@v.loewis.de> References: <47D051C8.1060402@v.loewis.de> Message-ID: <43aa6ff70803061449v74533819n5a4e12fe3c4f9132@mail.gmail.com> On Thu, Mar 6, 2008 at 12:19 PM, "Martin v. L?wis" wrote: > I just implemented auto-assignment for the tracker, i.e. a component > can be linked to a developer so that issues mentioning the component > get assigned to that developer (unless an explicit assignment is > made). > > I have assigned 2to3 to Collin Winter (this was already implemented > as a special case), and Documentation and Sphinx to Georg Brandl. Thanks! _______________________________________________ Python-Dev mailing list Python-Dev at python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/jgarber%40ionzoft.com From metatracker at psf.upfronthosting.co.za Fri Mar 7 21:46:21 2008 From: metatracker at psf.upfronthosting.co.za (Raghuram Devarakonda) Date: Fri, 07 Mar 2008 20:46:21 -0000 Subject: [Tracker-discuss] [issue196] RE for matchig revision id's needs tweaking In-Reply-To: <1204917161.88.0.0844926023843.issue196@psf.upfronthosting.co.za> Message-ID: <1204922781.91.0.857619246028.issue196@psf.upfronthosting.co.za> Raghuram Devarakonda added the comment: Please see rev_regex.diff that contains some changes to the regex. The modifications include: 1) Consolidate three RE's to one. 2) Now revision id's can be preceded by any non-ascii and non-digit character. 3) Check that revision id's are followed by non-ascii and non-digit character. 4) The resultant link name is always "revision " even if the original string is "r" or "rev". This simplifies the RE and I don't think we loose anything. 5) Improve the "test" code. ---------- status: unread -> chatting _______________________________________________________ Meta Tracker _______________________________________________________ -------------- next part -------------- A non-text attachment was scrubbed... Name: rev_regex.diff Type: text/x-patch Size: 3373 bytes Desc: not available Url : http://mail.python.org/pipermail/tracker-discuss/attachments/20080307/391d4bbf/attachment.bin From metatracker at psf.upfronthosting.co.za Sat Mar 8 21:13:15 2008 From: metatracker at psf.upfronthosting.co.za (Philipp Gortan) Date: Sat, 08 Mar 2008 20:13:15 -0000 Subject: [Tracker-discuss] [issue153] trigger traceback when doing issue search on non-existent username In-Reply-To: <1189488338.51.0.328974488764.issue153@psf.upfronthosting.co.za> Message-ID: <1205007195.14.0.102386633888.issue153@psf.upfronthosting.co.za> Philipp Gortan added the comment: The fundamental problem we're facing here is that the module that's observing the error, the `lookupIds` function in cgi.templating, does not have any possibility to report the error to the user. It cannot raise an exception that results in the user being returned to the search with the `error_message` containing an appropriate message, like "User 'foo' doesn't exist", which would be the right thing, I guess. So I handle the wrong user input the same way as it's handled for link properties, by dropping the unknown value from the filterspec. Can someone with checkin privileges please review and merge the patch? Thank you! ---------- assignedto: mephinet -> status: chatting -> testing _______________________________________________________ Meta Tracker _______________________________________________________ -------------- next part -------------- A non-text attachment was scrubbed... Name: cgi-handle-non-existing-key.patch Type: application/octet-stream Size: 783 bytes Desc: not available Url : http://mail.python.org/pipermail/tracker-discuss/attachments/20080308/c66541d1/attachment.obj From metatracker at psf.upfronthosting.co.za Sat Mar 8 21:58:45 2008 From: metatracker at psf.upfronthosting.co.za (Paul Dubois) Date: Sat, 08 Mar 2008 20:58:45 -0000 Subject: [Tracker-discuss] [issue153] trigger traceback when doing issue search on non-existent username In-Reply-To: <1205007195.14.0.102386633888.issue153@psf.upfronthosting.co.za> Message-ID: Paul Dubois added the comment: One idea is, add an artificial 'user' with no privleges named 'Unknown User', and instead of deleting the value from the filterspec, change it to this name. I don't know what would happen but it would be interesting....(:-> On Sat, Mar 8, 2008 at 12:13 PM, Philipp Gortan < metatracker at psf.upfronthosting.co.za> wrote: > > Philipp Gortan added the comment: > > The fundamental problem we're facing here is that the module that's > observing > the error, the `lookupIds` function in cgi.templating, does not have any > possibility to report the error to the user. It cannot raise an exception > that > results in the user being returned to the search with the `error_message` > containing an appropriate message, like "User 'foo' doesn't exist", which > would > be the right thing, I guess. > So I handle the wrong user input the same way as it's handled for link > properties, by dropping the unknown value from the filterspec. > Can someone with checkin privileges please review and merge the patch? > Thank you! > > ---------- > assignedto: mephinet -> > status: chatting -> testing > > _______________________________________________________ > Meta Tracker > > _______________________________________________________ > _______________________________________________ > Tracker-discuss mailing list > Tracker-discuss at python.org > http://mail.python.org/mailman/listinfo/tracker-discuss > > ---------- nosy: +dubois _______________________________________________________ Meta Tracker _______________________________________________________ -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mail.python.org/pipermail/tracker-discuss/attachments/20080308/4f2538aa/attachment.htm From gortan at gmail.com Sun Mar 9 00:25:07 2008 From: gortan at gmail.com (Philipp Gortan) Date: Sun, 9 Mar 2008 00:25:07 +0100 Subject: [Tracker-discuss] Updating bugs.python.org to Roundup release 1.4.2 [was: Python Fork and our SF Tracker] Message-ID: Hi Martin, hello list, On Fri, Mar 7, 2008 at 6:45 PM, "Martin v. L?wis" wrote: > I also don't know of anybody else > who has the time to merge a recent roundup release into bugs.python.org. > If somebody would step forward: that would certainly be a useful thing. Well, I'll give it a try (and take this topic to the tracker-discuss mailing list, as it's becoming python.org-centric now, I guess). I created a patch that covers the changes between the CVS tags release-1-3-2 and release-1-4-2, and applied it (in my sandbox) against the current python.org SVN head. The merge resulted in conflicts in six files, with the only larger problems being in roundup/mailgw.py, as Ulrik Mikaelsson has already pointed out. I followed his advise and gave preference to the sf.net version. The resulting patch against the SVN head comprises: 79 files changed, 10260 insertions(+), 5640 deletions(-) with all 556 unittests passing, including those using the postgresql backend. Besides running the unittests and clicking through the web interface a bit, there isn't exactly a lot I can do when it comes to extensive testing, so are there any proposals on how to proceed with the update? Thanks for input, cu, Philipp -- Philipp Gortan Obviously I was either onto something, or on something. -- Larry Wall on the creation of Perl -------------- next part -------------- A non-text attachment was scrubbed... Name: roundup-1.3.2-to-1.4.2.patch.gz Type: application/x-gzip Size: 221235 bytes Desc: not available Url : http://mail.python.org/pipermail/tracker-discuss/attachments/20080309/bcab7f45/attachment-0001.bin From martin at v.loewis.de Sun Mar 9 09:50:54 2008 From: martin at v.loewis.de (=?ISO-8859-1?Q?=22Martin_v=2E_L=F6wis=22?=) Date: Sun, 09 Mar 2008 09:50:54 +0100 Subject: [Tracker-discuss] Updating bugs.python.org to Roundup release 1.4.2 In-Reply-To: References: Message-ID: <47D3A4EE.9050208@v.loewis.de> > Besides running the unittests and clicking through the web interface a bit, > there isn't exactly a lot I can do when it comes to extensive testing, > so are there any proposals on how to proceed with the update? I just installed it, and it seems to work fine (despite myself not running roundup-admin migrate first, but immediately restarting roundup-server). So thanks for the patch. I'm sure people will report problems when they find any. Regards, Martin From martin at v.loewis.de Sun Mar 9 10:13:40 2008 From: martin at v.loewis.de (=?ISO-8859-1?Q?=22Martin_v=2E_L=F6wis=22?=) Date: Sun, 09 Mar 2008 10:13:40 +0100 Subject: [Tracker-discuss] Updating bugs.python.org to Roundup release 1.4.2 [was: Python Fork and our SF Tracker] In-Reply-To: References: Message-ID: <47D3AA44.5040902@v.loewis.de> > I created a patch that covers the changes between the CVS tags > release-1-3-2 and release-1-4-2, and applied it (in my sandbox) against the > current python.org SVN head. Unfortunately, I just found that the patch also contained your change for issue 153. This is bad, since the subversion history now claims that the change is part of roundup 1.4.2 (which, AFAICT, it is not). Can you please double check whether any other changes that are not part of 1.4.2 made it into that patch? Regards, Martin From metatracker at psf.upfronthosting.co.za Sun Mar 9 10:23:24 2008 From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v._L=C3=B6wis?=) Date: Sun, 09 Mar 2008 09:23:24 +0000 Subject: [Tracker-discuss] [issue153] trigger traceback when doing issue search on non-existent username In-Reply-To: <1189488338.51.0.328974488764.issue153@psf.upfronthosting.co.za> Message-ID: <1205054604.21.0.34735741364.issue153@psf.upfronthosting.co.za> Martin v. L?wis added the comment: This patch was committed as part of r61320. It works insofar as there isn't any traceback anymore. However, it gives somewhat surprising results: rather than finding no issues, it finds all issues; if you then check you see that none of the issues found actually feature that user as creator or in the nosy list. Paul's proposal should work fine, I think, in the specific case: if you use "nobody" as the user, it will not find anything. More generally, if you use -1 as the id, it will produce valid SQL, searching for ID -1, which won't be found. Of course, it would be even better if there was an error message instead of an empty result list, but, as you say, that may be difficult to do. _______________________________________________________ Meta Tracker _______________________________________________________ From gortan at gmail.com Sun Mar 9 11:43:38 2008 From: gortan at gmail.com (Philipp Gortan) Date: Sun, 9 Mar 2008 11:43:38 +0100 Subject: [Tracker-discuss] Updating bugs.python.org to Roundup release 1.4.2 [was: Python Fork and our SF Tracker] In-Reply-To: <47D3AA44.5040902@v.loewis.de> References: <47D3AA44.5040902@v.loewis.de> Message-ID: On Sun, Mar 9, 2008 at 10:13 AM, "Martin v. L?wis" wrote: > > I created a patch that covers the changes between the CVS tags > > release-1-3-2 and release-1-4-2, and applied it (in my sandbox) against the > > current python.org SVN head. > > Unfortunately, I just found that the patch also contained your change > for issue 153. This is bad, since the subversion history now claims that > the change is part of roundup 1.4.2 (which, AFAICT, it is not). Oh, sorry 'bout that, I seem to have got confused by the amount of lines changed X-) If I make a diff between the roundup release 1.4.2 tag and the bugs.python.org svn trunk these are the changes: * roundup/cgi/client.py: `clean_sessions` has two modifications: r54913 | erik.forsberg | 2007-04-21 18:42:55 +0200 (Sat, 21 Apr 2007) | 4 lines Try to cope with http://sourceforge.net/tracker/index.php?func=detail&aid=1703116&group_id=31577&atid=402788 which is causing large amounts of mail from the tracker. r61200 | martin.v.loewis | 2008-03-03 08:19:52 +0100 (Mon, 03 Mar 2008) | 2 lines Protect all session cleaning against concurrent access. * roundup/cgi/templating.py has three changes: r56964 | erik.forsberg | 2007-08-12 21:01:45 +0200 (Sun, 12 Aug 2007) | 3 lines Modify URL regexp to demand URLs to end with letter, digit, underscore or slash. Fixes http://psf.upfronthosting.co.za/roundup/meta/issue127. r61201 | martin.v.loewis | 2008-03-03 08:56:30 +0100 (Mon, 03 Mar 2008) | 3 lines Strip values of a multilink parameter after splitting at commas. Fixes #148. and the change you mentioned, which is the fix for meta issue 153, but not yet submitted on sf.net * in roundup/roundupdb.py: r59861 | martin.v.loewis | 2008-01-08 20:54:24 +0100 (Tue, 08 Jan 2008) | 2 lines Generate additional headers. * whitespace or cosmetic changes in backends/rdbms_common.py, backends/back_postgresql.py, roundup/mailgw.py, test/test_mailgw.py cu, Philipp -- Philipp Gortan Obviously I was either onto something, or on something. -- Larry Wall on the creation of Perl From martin at v.loewis.de Sun Mar 9 21:44:40 2008 From: martin at v.loewis.de (=?ISO-8859-1?Q?=22Martin_v=2E_L=F6wis=22?=) Date: Sun, 09 Mar 2008 21:44:40 +0100 Subject: [Tracker-discuss] Updating bugs.python.org to Roundup release 1.4.2 [was: Python Fork and our SF Tracker] In-Reply-To: References: <47D3AA44.5040902@v.loewis.de> Message-ID: <47D44C38.1050105@v.loewis.de> > Oh, sorry 'bout that, I seem to have got confused by the amount of > lines changed X-) > > If I make a diff between the roundup release 1.4.2 tag and the > bugs.python.org svn trunk > these are the changes: Ok, IIUC, there was only this one additional change. Thanks for the confirmation. > and the change you mentioned, which is the fix for meta issue 153, but > not yet submitted on sf.net So what do you think about the alternative approach, of arranging that it finds nothing, instead of everything? Regards, Martin From eric at trueblade.com Sun Mar 9 21:49:24 2008 From: eric at trueblade.com (Eric Smith) Date: Sun, 09 Mar 2008 16:49:24 -0400 Subject: [Tracker-discuss] How do I get permission to close an issue? Message-ID: <47D44D54.50104@trueblade.com> A few weeks ago, I checked in a change that fixes issue 1600. I'd like to close this issue, but it looks like I don't have permission. The wiki says that sending mail to tracker-discuss is the way to ask for permission, so I'm asking! Thanks. Eric. From brett at python.org Sun Mar 9 23:10:56 2008 From: brett at python.org (Brett Cannon) Date: Sun, 9 Mar 2008 15:10:56 -0700 Subject: [Tracker-discuss] How do I get permission to close an issue? In-Reply-To: <47D44D54.50104@trueblade.com> References: <47D44D54.50104@trueblade.com> Message-ID: On Sun, Mar 9, 2008 at 1:49 PM, Eric Smith wrote: > A few weeks ago, I checked in a change that fixes issue 1600. I'd like > to close this issue, but it looks like I don't have permission. The > wiki says that sending mail to tracker-discuss is the way to ask for > permission, so I'm asking! I found Eric's username as eric.smith (right, Eric?). But what role should he have. Coordinator? Developer? Which one are we using for people who can triage issues? -Brett From martin at v.loewis.de Sun Mar 9 23:23:40 2008 From: martin at v.loewis.de (=?ISO-8859-1?Q?=22Martin_v=2E_L=F6wis=22?=) Date: Sun, 09 Mar 2008 23:23:40 +0100 Subject: [Tracker-discuss] How do I get permission to close an issue? In-Reply-To: References: <47D44D54.50104@trueblade.com> Message-ID: <47D4636C.7090701@v.loewis.de> > I found Eric's username as eric.smith (right, Eric?). But what role > should he have. Coordinator? Developer? Which one are we using for > people who can triage issues? Developer. In principle, all committers should have the Developer role. Coordinator is the role of people managing the tracker. Regards, Martin From eric at trueblade.com Sun Mar 9 23:24:41 2008 From: eric at trueblade.com (Eric Smith) Date: Sun, 09 Mar 2008 18:24:41 -0400 Subject: [Tracker-discuss] How do I get permission to close an issue? In-Reply-To: References: <47D44D54.50104@trueblade.com> Message-ID: <47D463A9.5000500@trueblade.com> Brett Cannon wrote: > On Sun, Mar 9, 2008 at 1:49 PM, Eric Smith wrote: >> A few weeks ago, I checked in a change that fixes issue 1600. I'd like >> to close this issue, but it looks like I don't have permission. The >> wiki says that sending mail to tracker-discuss is the way to ask for >> permission, so I'm asking! > > I found Eric's username as eric.smith (right, Eric?). But what role > should he have. Coordinator? Developer? Which one are we using for > people who can triage issues? Right. eric.smith. Sorry about that. I'm also going to open some issues for PEP's 3101 and 3127, then I'll close those as I implement fixes. Eric. From brett at python.org Mon Mar 10 01:08:34 2008 From: brett at python.org (Brett Cannon) Date: Sun, 9 Mar 2008 17:08:34 -0700 Subject: [Tracker-discuss] How do I get permission to close an issue? In-Reply-To: <47D463A9.5000500@trueblade.com> References: <47D44D54.50104@trueblade.com> <47D463A9.5000500@trueblade.com> Message-ID: On Sun, Mar 9, 2008 at 3:24 PM, Eric Smith wrote: > > Brett Cannon wrote: > > On Sun, Mar 9, 2008 at 1:49 PM, Eric Smith wrote: > >> A few weeks ago, I checked in a change that fixes issue 1600. I'd like > >> to close this issue, but it looks like I don't have permission. The > >> wiki says that sending mail to tracker-discuss is the way to ask for > >> permission, so I'm asking! > > > > I found Eric's username as eric.smith (right, Eric?). But what role > > should he have. Coordinator? Developer? Which one are we using for > > people who can triage issues? > > Right. eric.smith. Sorry about that. > > I'm also going to open some issues for PEP's 3101 and 3127, then I'll > close those as I implement fixes. OK, you now have a Developer role. -Brett From gortan at gmail.com Mon Mar 10 10:54:41 2008 From: gortan at gmail.com (Philipp Gortan) Date: Mon, 10 Mar 2008 10:54:41 +0100 Subject: [Tracker-discuss] Updating bugs.python.org to Roundup release 1.4.2 [was: Python Fork and our SF Tracker] In-Reply-To: <47D44C38.1050105@v.loewis.de> References: <47D3AA44.5040902@v.loewis.de> <47D44C38.1050105@v.loewis.de> Message-ID: On Sun, Mar 9, 2008 at 9:44 PM, "Martin v. L?wis" wrote: > So what do you think about the alternative approach, of arranging > that it finds nothing, instead of everything? This definitely sounds like a reasonable approach, but please keep in mind, that we should then also change the behaviour for the link class. My current implementation is com-bug-atible with the link search, where you also find all issues if you specify an invalid username, like in: cu, Philipp -- Philipp Gortan Obviously I was either onto something, or on something. -- Larry Wall on the creation of Perl From martin at v.loewis.de Mon Mar 10 17:05:24 2008 From: martin at v.loewis.de (=?ISO-8859-1?Q?=22Martin_v=2E_L=F6wis=22?=) Date: Mon, 10 Mar 2008 17:05:24 +0100 Subject: [Tracker-discuss] Updating bugs.python.org to Roundup release 1.4.2 [was: Python Fork and our SF Tracker] In-Reply-To: References: <47D3AA44.5040902@v.loewis.de> <47D44C38.1050105@v.loewis.de> Message-ID: <47D55C44.9000406@v.loewis.de> > This definitely sounds like a reasonable approach, but please keep in > mind, that > we should then also change the behaviour for the link class. My current > implementation is com-bug-atible with the link search, where you also find > all issues if you specify an invalid username, like in: > > I see. I guess the current patch is fine, then. Thanks again for your efforts, Martin From metatracker at psf.upfronthosting.co.za Mon Mar 10 17:06:45 2008 From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v._L=C3=B6wis?=) Date: Mon, 10 Mar 2008 16:06:45 +0000 Subject: [Tracker-discuss] [issue153] trigger traceback when doing issue search on non-existent username In-Reply-To: <1189488338.51.0.328974488764.issue153@psf.upfronthosting.co.za> Message-ID: <1205165205.73.0.362654398336.issue153@psf.upfronthosting.co.za> Martin v. L?wis added the comment: After some discussion on tracker-discuss, we agreed to go with the current patch. As it actually fixes the issue at hand, I'll mark it as resolved. ---------- status: testing -> resolved _______________________________________________________ Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Sun Mar 16 21:49:09 2008 From: metatracker at psf.upfronthosting.co.za (Georg Brandl) Date: Sun, 16 Mar 2008 20:49:09 +0000 Subject: [Tracker-discuss] [issue197] Add "performance" type In-Reply-To: <1205700549.33.0.412186257138.issue197@psf.upfronthosting.co.za> Message-ID: <1205700549.33.0.412186257138.issue197@psf.upfronthosting.co.za> New submission from Georg Brandl : Title says it all. ---------- messages: 1025 nosy: gbrandl priority: wish status: unread title: Add "performance" type _______________________________________________________ Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Sun Mar 16 21:57:34 2008 From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v._L=C3=B6wis?=) Date: Sun, 16 Mar 2008 20:57:34 +0000 Subject: [Tracker-discuss] [issue197] Add "performance" type In-Reply-To: <1205700549.33.0.412186257138.issue197@psf.upfronthosting.co.za> Message-ID: <1205701054.1.0.219710726372.issue197@psf.upfronthosting.co.za> Martin v. L?wis added the comment: You can add this yourself; go to http://bugs.python.org/issue_type ---------- assignedto: -> gbrandl nosy: +loewis status: unread -> chatting _______________________________________________________ Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Sun Mar 16 22:04:48 2008 From: metatracker at psf.upfronthosting.co.za (Georg Brandl) Date: Sun, 16 Mar 2008 21:04:48 +0000 Subject: [Tracker-discuss] [issue197] Add "performance" type In-Reply-To: <1205700549.33.0.412186257138.issue197@psf.upfronthosting.co.za> Message-ID: <1205701488.32.0.321454266066.issue197@psf.upfronthosting.co.za> Georg Brandl added the comment: Ah, I tried http://bugs.python.org/type in vain... thanks! ---------- status: chatting -> resolved _______________________________________________________ Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Sun Mar 16 22:10:13 2008 From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v._L=C3=B6wis?=) Date: Sun, 16 Mar 2008 21:10:13 +0000 Subject: [Tracker-discuss] [issue197] Add "performance" type In-Reply-To: <1205700549.33.0.412186257138.issue197@psf.upfronthosting.co.za> Message-ID: <1205701813.16.0.771659613692.issue197@psf.upfronthosting.co.za> Martin v. L?wis added the comment: For the schema, see http://svn.python.org/projects/tracker/instances/python-dev/schema.py In this case, I quickly located the class name through http://svn.python.org/projects/tracker/instances/python-dev/initial_data.py I believe it's issue_type because type alone could conflict with the builtin function too easily. ---------- status: resolved -> chatting _______________________________________________________ Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Mon Mar 17 18:30:53 2008 From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v._L=C3=B6wis?=) Date: Mon, 17 Mar 2008 17:30:53 +0000 Subject: [Tracker-discuss] [issue198] Set attributes in the body In-Reply-To: <1205775053.19.0.471134513632.issue198@psf.upfronthosting.co.za> Message-ID: <1205775053.19.0.471134513632.issue198@psf.upfronthosting.co.za> New submission from Martin v. L?wis : Setting attributes in the subject, like [nosy=+foo], messes with threading in gmail. It would be nice if one could also set fields in the (top of the) body, e.g. title = foo nosy = +foo ---------- messages: 1029 nosy: loewis priority: wish status: unread title: Set attributes in the body _______________________________________________________ Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Tue Mar 18 16:11:35 2008 From: metatracker at psf.upfronthosting.co.za (Sean Reifschneider) Date: Tue, 18 Mar 2008 15:11:35 +0000 Subject: [Tracker-discuss] [issue199] Tasks with no comments generate confusing error when updating status. In-Reply-To: <1205853095.57.0.890437161873.issue199@psf.upfronthosting.co.za> Message-ID: <1205853095.57.0.890437161873.issue199@psf.upfronthosting.co.za> New submission from Sean Reifschneider : I have been triaging unassigned bugs with no priority set. Some of these have no comments associated with them. When I try to set the status and assigned fields, it gives me an error like "Invalid list ID". So I've been adding comments like "Assigned" to these items when I muck with them. ---------- messages: 1030 nosy: jafo priority: bug status: unread title: Tasks with no comments generate confusing error when updating status. _______________________________________________________ Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Tue Mar 18 17:04:35 2008 From: metatracker at psf.upfronthosting.co.za (Sean Reifschneider) Date: Tue, 18 Mar 2008 16:04:35 +0000 Subject: [Tracker-discuss] [issue199] Tasks with no comments generate confusing error when updating status. In-Reply-To: <1205853095.57.0.890437161873.issue199@psf.upfronthosting.co.za> Message-ID: <1205856275.04.0.403305181556.issue199@psf.upfronthosting.co.za> Sean Reifschneider added the comment: I'm not sure about how these issues got created. Yesterday I did about 20 or 30 bugs and 2 or 3 of them were without any messages. However, I looked at around 40 this morning and they all had messages. I tried to create an issue without a message, and it also generates the "Edit Error: list index out of range" error. Ditto if I create an issue with a message and then try the "remove" button. Could these message-less issues have been imported from the SF tracker? I have issue 2392 which I'm currently playing with on this. You can reproduce by either: Load issue 2392 Click on "Remove" on the first message Or: Create a new issue with the message area empty. At the least, in the last case the error is confusing. For the existing rare case where an issue has no message, I guess we can just live with it. ---------- assignedto: -> loewis nosy: +loewis status: unread -> chatting _______________________________________________________ Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Tue Mar 18 20:27:00 2008 From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v._L=C3=B6wis?=) Date: Tue, 18 Mar 2008 19:27:00 +0000 Subject: [Tracker-discuss] [issue199] Tasks with no comments generate confusing error when updating status. In-Reply-To: <1205853095.57.0.890437161873.issue199@psf.upfronthosting.co.za> Message-ID: <1205868420.89.0.450106767091.issue199@psf.upfronthosting.co.za> Martin v. L?wis added the comment: This is now fixed in r61545. ---------- status: chatting -> resolved _______________________________________________________ Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Wed Mar 19 18:13:39 2008 From: metatracker at psf.upfronthosting.co.za (Brett C.) Date: Wed, 19 Mar 2008 17:13:39 +0000 Subject: [Tracker-discuss] [issue200] Entering a non-existent issue # in "show issue" In-Reply-To: <1205946819.54.0.990394406592.issue200@psf.upfronthosting.co.za> Message-ID: <1205946819.54.0.990394406592.issue200@psf.upfronthosting.co.za> New submission from Brett C. : If you use a non-existent bug number (e.g., 3000) in "show issue" you get a page with a single line: "Wed Mar 19 17:10:40 2008: An error occurred. Please check the server log for more infomation.". That should get changed since that message suggests there was an error rather than just an invalid issue number. ---------- messages: 1033 nosy: brett.cannon priority: bug status: unread title: Entering a non-existent issue # in "show issue" _______________________________________________________ Meta Tracker _______________________________________________________ From stephen at xemacs.org Sat Mar 22 19:51:33 2008 From: stephen at xemacs.org (Stephen J. Turnbull) Date: Sun, 23 Mar 2008 03:51:33 +0900 Subject: [Tracker-discuss] Editing "public" queries in tracker [was: ... project management] In-Reply-To: <96720E99-D5A3-46B8-BBAA-88C021F24653@python.org> References: <2C2D7EC7-51F2-4F4E-8127-87ACCC6F8413@python.org> <5E86F9D7-4421-4C57-8294-B0EC6A4EE03C@python.org> <47DDF318.4080303@v.loewis.de> <96720E99-D5A3-46B8-BBAA-88C021F24653@python.org> Message-ID: <87abkqfv7u.fsf@uwakimon.sk.tsukuba.ac.jp> I think this howto is of general interest to the community, but I'm crossposting to Tracker-Discuss and redirecting discussion there. Reply-To set. Barry Warsaw writes: > Thanks Martin, I think this will work for now. Is there any way you > can allow me to edit this query too? While as Martin says only the author can edit a query, you can (in Roundup 1.4.2, which bugs.python.org may not have yet?) edit a copy of that query. (Since a query is an object, you can keep the same name for multiple queries. **But:** This is a doubleplusungood idea unless you coordinate with the first author to remove one of the versions, because there is no way to distinguish multiple queries by the same name except whether they are editable or not.) What I see in the edit interface at first is Query Include ... Edit Private ... YourQuery_ [not yours to edit] (where trailing _ indicates a link and <> a GUI widget). After setting YourQuery "leave in: yes", I see Query Include ... Edit Private ... YourQuery_ edit_ [delete] YourQuery_ [not yours to edit] ie, it looks like Roundup automatically makes a copy for you to edit. Urk ... once I've edited it, I now see Query Include ... Edit Private ... YourQuery_ edit_ [delete] YourQuery_ edit_ [delete] YourQuery_ [not yours to edit] where one of the editables is my version, and the other a copy of the original query You wrote. So even the editor is likely to find it confusing unless he renames his new version. Also, in 1.4.2 there seems to be a bug, such that my ordinary User was unable retire or remove the query. For now, you may not want to do this a lot as your sidebar will get cluttered. I wonder if it might be a good idea to have a convention to distinguish public queries that may be used as templates? From metatracker at psf.upfronthosting.co.za Wed Mar 26 15:40:12 2008 From: metatracker at psf.upfronthosting.co.za (Alan Kennedy) Date: Wed, 26 Mar 2008 14:40:12 +0000 Subject: [Tracker-discuss] [issue201] Message misclassified as spam. In-Reply-To: <1206542412.46.0.385759958849.issue201@psf.upfronthosting.co.za> Message-ID: <1206542412.46.0.385759958849.issue201@psf.upfronthosting.co.za> New submission from Alan Kennedy : The following message has been misclassified as spam. http://bugs.python.org/msg64525 The roundup interface tells me "please login and report the message as being misclassified." But after logging in, I cannot see a way to do that in the RoundUp interface. So I'm reporting it here. ---------- messages: 1034 nosy: amak priority: bug status: unread title: Message misclassified as spam. _______________________________________________________ Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Wed Mar 26 22:33:47 2008 From: metatracker at psf.upfronthosting.co.za (Brett C.) Date: Wed, 26 Mar 2008 21:33:47 +0000 Subject: [Tracker-discuss] [issue201] Message misclassified as spam. In-Reply-To: <1206542412.46.0.385759958849.issue201@psf.upfronthosting.co.za> Message-ID: <1206567227.23.0.93473536854.issue201@psf.upfronthosting.co.za> Brett C. added the comment: I marked it as ham. ---------- nosy: +brett.cannon status: unread -> resolved _______________________________________________________ Meta Tracker _______________________________________________________