From metatracker at psf.upfronthosting.co.za Mon Dec 3 20:50:26 2007 From: metatracker at psf.upfronthosting.co.za (Guido van Rossum) Date: Mon, 03 Dec 2007 19:50:26 -0000 Subject: [Tracker-discuss] [issue170] Pagination sticks around when switching queries Message-ID: <1196711426.82.0.368929437802.issue170@psf.upfronthosting.co.za> Guido van Rossum added the comment: I lied with my answer for (2). It is actually the same as (3): http://bugs.python.org/issue?status=-1,1,3&@sort=-activity&@search_text=&@dispname=Your%20Issues&@filter=status,assignee&@group=priority&@columns=id,activity,title,creator,status&assignee=5&@pagesize=50&@startwith=50&versions=12 So the issue is that somehow the startwith from the current query leaks into the link for Your Issues. That should be easier to debug for you. Sorry for the false lead! _______________________________________________________ Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Mon Dec 3 21:08:23 2007 From: metatracker at psf.upfronthosting.co.za (Erik Forsberg) Date: Mon, 03 Dec 2007 20:08:23 -0000 Subject: [Tracker-discuss] [issue170] Pagination sticks around when switching queries In-Reply-To: <1196711426.82.0.368929437802.issue170@psf.upfronthosting.co.za> Message-ID: <20071203210747.387640c3@uterus> Erik Forsberg added the comment: ... > That should be easier to debug for you. Ha! That's today's understatement! :-) Turns out a helper function used to construct the URL took the startwith from the request. This has now been fixed. I'll see if it exists in the standard templates shipped with roundup and fix it there as well. > Sorry for the false lead! No problem. I classified the bug as one of those issues that required some time to be understood, and see, it almost solved itself :-). Cheers, \EF -- Erik Forsberg http://efod.se GPG/PGP Key: 1024D/0BAC89D9 ---------- status: chatting -> resolved _______________________________________________________ Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Tue Dec 4 09:29:49 2007 From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v._L=C3=B6wis?=) Date: Tue, 04 Dec 2007 08:29:49 -0000 Subject: [Tracker-discuss] [issue171] Order file uploads by date Message-ID: <1196756988.98.0.8226257455.issue171@psf.upfronthosting.co.za> New submission from Martin v. L?wis: When looking at attached patches, it is often necessary to find out what the most recent patch is. Therefore, it would be good if the attachments were ordered by upload date, not by name. See http://bugs.python.org/issue1490190 for an example. ---------- messages: 867 nosy: loewis priority: feature status: unread title: Order file uploads by date _______________________________________________________ Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Thu Dec 6 15:23:46 2007 From: metatracker at psf.upfronthosting.co.za (Facundo Batista) Date: Thu, 06 Dec 2007 14:23:46 -0000 Subject: [Tracker-discuss] [issue172] Traceback exposed in misformed URL Message-ID: <1196951026.1.0.157520960574.issue172@psf.upfronthosting.co.za> New submission from Facundo Batista: If you create a bad URL, a lot of internal information is exposed: Try with this one... http://bugs.python.org/issue?@sort0=FRUTA ...and you'll see something like what I've attached. (I put it as "critical" because it's a security issue) Regards, . Facundo ---------- files: issue.htm messages: 868 nosy: facundobatista priority: critical status: unread title: Traceback exposed in misformed URL _______________________________________________________ Meta Tracker _______________________________________________________ -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mail.python.org/pipermail/tracker-discuss/attachments/20071206/f04e522b/attachment.htm From martin at v.loewis.de Thu Dec 6 19:46:12 2007 From: martin at v.loewis.de (=?UTF-8?B?Ik1hcnRpbiB2LiBMw7Z3aXMi?=) Date: Thu, 06 Dec 2007 19:46:12 +0100 Subject: [Tracker-discuss] [issue172] Traceback exposed in misformed URL In-Reply-To: <1196951026.1.0.157520960574.issue172@psf.upfronthosting.co.za> References: <1196951026.1.0.157520960574.issue172@psf.upfronthosting.co.za> Message-ID: <47584374.1010903@v.loewis.de> > If you create a bad URL, a lot of internal information is exposed: What specific, security-relevant internal information are you referring to? I can't see any in the traceback you provided. Regards, Martin From metatracker at psf.upfronthosting.co.za Thu Dec 6 19:46:15 2007 From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v._L=C3=B6wis?=) Date: Thu, 06 Dec 2007 18:46:15 -0000 Subject: [Tracker-discuss] [issue172] Traceback exposed in misformed URL In-Reply-To: <1196951026.1.0.157520960574.issue172@psf.upfronthosting.co.za> Message-ID: <47584374.1010903@v.loewis.de> Martin v. L?wis added the comment: > If you create a bad URL, a lot of internal information is exposed: What specific, security-relevant internal information are you referring to? I can't see any in the traceback you provided. Regards, Martin ---------- status: unread -> chatting _______________________________________________________ Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Mon Dec 10 13:34:59 2007 From: metatracker at psf.upfronthosting.co.za (Facundo Batista) Date: Mon, 10 Dec 2007 12:34:59 -0000 Subject: [Tracker-discuss] [issue172] Traceback exposed in misformed URL Message-ID: <1197290099.49.0.6237969518.issue172@psf.upfronthosting.co.za> Facundo Batista added the comment: I think that showing the internal variables and their values on one side, and the full traceback with directory names and everything on the other, could be used by bad people to attack the system (I don't know how, but I'm not a cracker). Even if the information exposed is not so important, what's the harm of not showing it? Returning a 505, or a "Query bad formed" message should be enough. Maybe disabling the "debug mode" in the server will do it and minimize the effort. Anyway, I just wanted to point the issue to you, because maybe it was not a desired effect. If you consciously want to leave it like this, it's ok to me (feel free to close the bug). Thank you!! _______________________________________________________ Meta Tracker _______________________________________________________ From amk at amk.ca Mon Dec 10 15:37:34 2007 From: amk at amk.ca (A.M. Kuchling) Date: Mon, 10 Dec 2007 09:37:34 -0500 Subject: [Tracker-discuss] GHOP project idea: Roundup for job offers Message-ID: <20071210143734.GB9173@amk-desktop.matrixgroup.net> python.org has a job board at . Right now jobs are sent to an e-mail list and the page is simply edited by hand. It would be nice to automate this process. On the pydotorg list, Martin von Loewis suggested that Roundup could be used for this task. I took his post and turned it into a project description for the Google Highly Open Participation contest: http://wiki.python.org/moin/AndrewKuchling/JobBoardDraft What does the tracker-discuss group think of this idea? (Please edit the draft as you wish; Martin knows Roundup well, but I don't, and may have misworded something.) Does anyone want to mentor the student who takes on this project? --amk From metatracker at psf.upfronthosting.co.za Mon Dec 10 22:54:22 2007 From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v._L=C3=B6wis?=) Date: Mon, 10 Dec 2007 21:54:22 -0000 Subject: [Tracker-discuss] [issue172] Traceback exposed in misformed URL Message-ID: <1197323662.52.0.312939687784.issue172@psf.upfronthosting.co.za> Martin v. L?wis added the comment: Setting the priority to "bug" then. The complete source code, including the complete configuration data, is available for inspection by anybody in subversion; it's open source. Whether or not it's desirable to display this information, I don't know. If there is a real bug somewhere, it is sure helpful if the report can include the corresponding traceback. ---------- priority: critical -> bug _______________________________________________________ Meta Tracker _______________________________________________________ From skip at pobox.com Thu Dec 13 13:35:07 2007 From: skip at pobox.com (skip at pobox.com) Date: Thu, 13 Dec 2007 06:35:07 -0600 Subject: [Tracker-discuss] [Python-3000] Is it possible that some issues reported in the tracker can loose or be deleted? (fwd) Message-ID: <18273.9979.233195.140188@montanaro.dyndns.org> Passing this note along from the python-3000 mailing list. FYI. Skip -------------- next part -------------- An embedded message was scrubbed... From: Vizcayno Subject: [Python-3000] Is it possible that some issues reported in the tracker can loose or be deleted? Date: Tue, 11 Dec 2007 14:18:18 -0800 (PST) Size: 5994 Url: http://mail.python.org/pipermail/tracker-discuss/attachments/20071213/e5ec119f/attachment.eml From draghuram at gmail.com Fri Dec 14 04:12:57 2007 From: draghuram at gmail.com (Raghuram Devarakonda) Date: Thu, 13 Dec 2007 22:12:57 -0500 Subject: [Tracker-discuss] missing issue in search Message-ID: <2c51ecee0712131912s38f802f8r639979d6a0ef7cd8@mail.gmail.com> Hi, >From time to time, I search for all open issues where I commented. I just populate "actor" field with my user name. Here is the link: http://bugs.python.org/issue?%40search_text=&title=&%40columns=title&id=&%40columns=id&creation=&creator=&activity=&%40columns=activity&%40sort=activity&actor=draghuram&type=&components=&versions=&severity=&dependencies=&assignee=&keywords=&priority=&%40group=priority&status=1&%40columns=status&resolution=&%40pagesize=50&%40startwith=0&%40queryname=&%40old-queryname=&%40action=search The list does now show issue 1256. Am I doing something wrong or is there some problem in the search? Can some one please check? Thanks, Raghu From metatracker at psf.upfronthosting.co.za Fri Dec 14 07:04:40 2007 From: metatracker at psf.upfronthosting.co.za (Brett C.) Date: Fri, 14 Dec 2007 06:04:40 -0000 Subject: [Tracker-discuss] [issue137] No option for Python 3 Message-ID: <1197612280.7.0.499827285651.issue137@psf.upfronthosting.co.za> Brett C. added the comment: There is a 'Python 3.0' version listing now, so closing as resolved. ---------- status: done-cbb -> resolved _______________________________________________________ Meta Tracker _______________________________________________________ From brett at python.org Fri Dec 14 07:17:32 2007 From: brett at python.org (Brett Cannon) Date: Thu, 13 Dec 2007 22:17:32 -0800 Subject: [Tracker-discuss] can people help clean up the issues on the meta tracker? Message-ID: I just looked at the issue tracker and noticed a bunch of bugs that have not been touched in three months. While I understand not worrying about features and wishes at the moment, the fact that we have lingering bugs worries me somewhat. The issue tracker is pretty important. Now I know we are all volunteers here and I appreciate all the work people have put in. But if we need more help to address issues please let me know! That way I can kick off the new year looking for help from people (maybe take advantage of potential New Years resolutions set up by people to help out Python =). But if people think we are okay with our current staff levels, can we at least go through and clean out the issues? This will become more critical if I manage to get around to trying to get people to discuss possible ways to change our issue workflow to work better for Python in 2008. -Brett From martin at v.loewis.de Fri Dec 14 08:14:37 2007 From: martin at v.loewis.de (=?ISO-8859-1?Q?=22Martin_v=2E_L=F6wis=22?=) Date: Fri, 14 Dec 2007 08:14:37 +0100 Subject: [Tracker-discuss] can people help clean up the issues on the meta tracker? In-Reply-To: References: Message-ID: <47622D5D.60304@v.loewis.de> > The issue tracker is pretty important. Now I know we are all > volunteers here and I appreciate all the work people have put in. But > if we need more help to address issues please let me know! Yes, we definitely need more help. > But if people think we are okay with our current staff levels, can we > at least go through and clean out the issues? No; there is not enough time to do that. Regards, Martin From metatracker at psf.upfronthosting.co.za Fri Dec 14 13:24:45 2007 From: metatracker at psf.upfronthosting.co.za (Hernan Foffani) Date: Fri, 14 Dec 2007 12:24:45 -0000 Subject: [Tracker-discuss] [issue173] Search by "Actor" really means "Last Actor" Message-ID: <1197635085.36.0.382880791687.issue173@psf.upfronthosting.co.za> New submission from Hernan Foffani: AFAICT a search by Actor X reports the issues where X was the last user who made some comment (activity?) to the issue. The standard Roundup tracker labeled the search field as "Last Actor" and that is the correct standard behavior. I don't know if this was changed for python-dev and a regression bug appears. ---------- messages: 873 nosy: hfoffani priority: bug status: unread title: Search by "Actor" really means "Last Actor" _______________________________________________________ Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Fri Dec 14 17:59:35 2007 From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v._L=C3=B6wis?=) Date: Fri, 14 Dec 2007 16:59:35 -0000 Subject: [Tracker-discuss] [issue173] Search by "Actor" really means "Last Actor" Message-ID: <1197651575.79.0.141192198073.issue173@psf.upfronthosting.co.za> Martin v. L?wis added the comment: Is searching for "actor" also supported in roundup? ---------- status: unread -> chatting _______________________________________________________ Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Fri Dec 14 18:51:03 2007 From: metatracker at psf.upfronthosting.co.za (Hernan Foffani) Date: Fri, 14 Dec 2007 17:51:03 -0000 Subject: [Tracker-discuss] [issue173] Search by "Actor" really means "Last Actor" Message-ID: <1197654663.73.0.531640595611.issue173@psf.upfronthosting.co.za> Hernan Foffani added the comment: Same thing in standard Roundup: searching for Actor means "Last Actor". Don't know if that is the desired behavior. I'll ask in the list... _______________________________________________________ Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Fri Dec 14 19:18:08 2007 From: metatracker at psf.upfronthosting.co.za (Hernan Foffani) Date: Fri, 14 Dec 2007 18:18:08 -0000 Subject: [Tracker-discuss] [issue173] Search by "Actor" really means "Last Actor" Message-ID: <1197656288.57.0.756232332022.issue173@psf.upfronthosting.co.za> Hernan Foffani added the comment: No need to ask after all. "actor" is an artificial property that is automatically set with the last user that actuate on the issue. Same thing happens with "Activity". My recommendation is to change the label of the field to avoid further confusions. We can also add a feature request. _______________________________________________________ Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Fri Dec 14 20:38:07 2007 From: metatracker at psf.upfronthosting.co.za (Paul Dubois) Date: Fri, 14 Dec 2007 19:38:07 -0000 Subject: [Tracker-discuss] [issue163] new traceback, cause unknown Message-ID: <1197661086.98.0.39766836842.issue163@psf.upfronthosting.co.za> Paul Dubois added the comment: Resolving as transient. ---------- status: chatting -> resolved _______________________________________________________ Meta Tracker _______________________________________________________ From pfdubois at gmail.com Fri Dec 14 20:44:52 2007 From: pfdubois at gmail.com (Paul Dubois) Date: Fri, 14 Dec 2007 11:44:52 -0800 Subject: [Tracker-discuss] can people help clean up the issues on the meta tracker? In-Reply-To: References: Message-ID: I closed a couple which were still open but resolved. This is a good time for me to bring up that I need to be replaced here. It turns out I have a lot of other interests now that I am retired and both my skill and interest levels in technical stuff have fallen rapidly. On Dec 13, 2007 10:17 PM, Brett Cannon wrote: > I just looked at the issue tracker and noticed a bunch of bugs that > have not been touched in three months. While I understand not worrying > about features and wishes at the moment, the fact that we have > lingering bugs worries me somewhat. > > The issue tracker is pretty important. Now I know we are all > volunteers here and I appreciate all the work people have put in. But > if we need more help to address issues please let me know! That way I > can kick off the new year looking for help from people (maybe take > advantage of potential New Years resolutions set up by people to help > out Python =). > > But if people think we are okay with our current staff levels, can we > at least go through and clean out the issues? This will become more > critical if I manage to get around to trying to get people to discuss > possible ways to change our issue workflow to work better for Python > in 2008. > > -Brett > _______________________________________________ > Tracker-discuss mailing list > Tracker-discuss at python.org > http://mail.python.org/mailman/listinfo/tracker-discuss > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mail.python.org/pipermail/tracker-discuss/attachments/20071214/37c03ac7/attachment.htm From brett at python.org Fri Dec 14 21:24:25 2007 From: brett at python.org (Brett Cannon) Date: Fri, 14 Dec 2007 12:24:25 -0800 Subject: [Tracker-discuss] can people help clean up the issues on the meta tracker? In-Reply-To: References: Message-ID: On Dec 14, 2007 11:44 AM, Paul Dubois wrote: > I closed a couple which were still open but resolved. > > This is a good time for me to bring up that I need to be replaced here. It > turns out I have a lot of other interests now that I am retired and both my > skill and interest levels in technical stuff have fallen rapidly. > Well, that settles that then. Come the new year I will put the call out for new volunteers and threaten that if we don't get enough we will be switching to a closed-source solution (e.g., JIRA or Launchpad since both groups said they would be happy to have us if the current situation didn't work out). I assume you can at least hold on until we get more help, Paul? And thanks for what you have been able to contribute so far. -Brett > > > > On Dec 13, 2007 10:17 PM, Brett Cannon wrote: > > > > > > > > I just looked at the issue tracker and noticed a bunch of bugs that > > have not been touched in three months. While I understand not worrying > > about features and wishes at the moment, the fact that we have > > lingering bugs worries me somewhat. > > > > The issue tracker is pretty important. Now I know we are all > > volunteers here and I appreciate all the work people have put in. But > > if we need more help to address issues please let me know! That way I > > can kick off the new year looking for help from people (maybe take > > advantage of potential New Years resolutions set up by people to help > > out Python =). > > > > But if people think we are okay with our current staff levels, can we > > at least go through and clean out the issues? This will become more > > critical if I manage to get around to trying to get people to discuss > > possible ways to change our issue workflow to work better for Python > > in 2008. > > > > -Brett > > _______________________________________________ > > Tracker-discuss mailing list > > Tracker-discuss at python.org > > http://mail.python.org/mailman/listinfo/tracker-discuss > > > > From skip at pobox.com Wed Dec 19 16:14:39 2007 From: skip at pobox.com (skip at pobox.com) Date: Wed, 19 Dec 2007 09:14:39 -0600 Subject: [Tracker-discuss] Submitting bugs by mail seems not to be working Message-ID: <18281.13663.551290.893636@montanaro.dyndns.org> I've tried three times today to submit a bug report and patch via email. As far as I can tell all three simply dropped off the face of the earth. #1 - To: bugs at python.org From: skip at pobox.com Subject: Tests needing network flag? #2 - To: report at bugs.python.org From: skip at pobox.com Subject: Tests needing network flag? #3 - To: report at bugs.python.org From: skip.montanaro at python.org Subject: Tests needing network flag? Looking at my tracker details it looks like my valid emails are skip at pobox.com and skip.montanaro at gmail.com. I added skip.montanaro at python.org, but not before submitting the third report. Am I missing something or is submitting by email either not supported or broken? Skip From georg at python.org Wed Dec 19 16:37:33 2007 From: georg at python.org (Georg Brandl) Date: Wed, 19 Dec 2007 16:37:33 +0100 Subject: [Tracker-discuss] Submitting bugs by mail seems not to be working In-Reply-To: <18281.13663.551290.893636@montanaro.dyndns.org> References: <18281.13663.551290.893636@montanaro.dyndns.org> Message-ID: <47693ABD.60606@python.org> skip at pobox.com schrieb: > I've tried three times today to submit a bug report and patch via email. As > far as I can tell all three simply dropped off the face of the earth. > > #1 - To: bugs at python.org > From: skip at pobox.com > Subject: Tests needing network flag? > > #2 - To: report at bugs.python.org > From: skip at pobox.com > Subject: Tests needing network flag? > > #3 - To: report at bugs.python.org > From: skip.montanaro at python.org > Subject: Tests needing network flag? > > Looking at my tracker details it looks like my valid emails are > skip at pobox.com and skip.montanaro at gmail.com. I added > skip.montanaro at python.org, but not before submitting the third report. > > Am I missing something or is submitting by email either not supported or > broken? I can see two new reports on the announce list - #1659 and #1660. Georg From skip at pobox.com Wed Dec 19 18:07:25 2007 From: skip at pobox.com (skip at pobox.com) Date: Wed, 19 Dec 2007 11:07:25 -0600 Subject: [Tracker-discuss] Submitting bugs by mail seems not to be working In-Reply-To: <47693ABD.60606@python.org> References: <18281.13663.551290.893636@montanaro.dyndns.org> <47693ABD.60606@python.org> Message-ID: <18281.20429.339668.238142@montanaro.dyndns.org> >> I've tried three times today to submit a bug report and patch via >> email. As far as I can tell all three simply dropped off the face of >> the earth. >> ... >> >> Looking at my tracker details it looks like my valid emails are >> skip at pobox.com and skip.montanaro at gmail.com. I added >> skip.montanaro at python.org, but not before submitting the third >> report. >> >> Am I missing something or is submitting by email either not supported >> or broken? Georg> I can see two new reports on the announce list - #1659 and #1660. I see them now as well. I closed #1660. #1659 says I created it at 09:17:30. I sent the mail for that at 09:02:34. Maybe I was just expecting too immediate of a response. Final question... It's clear that mail sent to bugs at python.org does not forward to report at bugs.python.org. At the same time it doesn't bounce. Where does that email alias go? Can we get it to redirect to report at bugs.python.org? It's a very logical name for the email bug reporting address. Skip From martin at v.loewis.de Wed Dec 19 20:35:13 2007 From: martin at v.loewis.de (=?ISO-8859-1?Q?=22Martin_v=2E_L=F6wis=22?=) Date: Wed, 19 Dec 2007 20:35:13 +0100 Subject: [Tracker-discuss] Submitting bugs by mail seems not to be working In-Reply-To: <18281.20429.339668.238142@montanaro.dyndns.org> References: <18281.13663.551290.893636@montanaro.dyndns.org> <47693ABD.60606@python.org> <18281.20429.339668.238142@montanaro.dyndns.org> Message-ID: <47697271.8080509@v.loewis.de> > Final question... It's clear that mail sent to bugs at python.org does not > forward to report at bugs.python.org. At the same time it doesn't bounce. > Where does that email alias go? Can we get it to redirect to > report at bugs.python.org? It's a very logical name for the email bug > reporting address. You should ask postmaster at python.org about that. "we" cannot get it to redirect (i.e. neither you nor me can, as neither of us has access to mail.python.org). Regards, Martin From skip at pobox.com Wed Dec 19 20:46:50 2007 From: skip at pobox.com (skip at pobox.com) Date: Wed, 19 Dec 2007 13:46:50 -0600 Subject: [Tracker-discuss] Submitting bugs by mail seems not to be working In-Reply-To: <47697271.8080509@v.loewis.de> References: <18281.13663.551290.893636@montanaro.dyndns.org> <47693ABD.60606@python.org> <18281.20429.339668.238142@montanaro.dyndns.org> <47697271.8080509@v.loewis.de> Message-ID: <18281.29994.751990.227031@montanaro.dyndns.org> Martin> You should ask postmaster at python.org about that. Thanks. Done. Skip From metatracker at psf.upfronthosting.co.za Mon Dec 31 13:35:58 2007 From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v._L=C3=B6wis?=) Date: Mon, 31 Dec 2007 12:35:58 -0000 Subject: [Tracker-discuss] [issue133] show real name of comment authors Message-ID: <1199104558.28.0.25995980379.issue133@psf.upfronthosting.co.za> Martin v. L?wis added the comment: This is now fixed in r59615, and life. ---------- status: chatting -> resolved _______________________________________________________ Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Mon Dec 31 13:37:02 2007 From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v._L=C3=B6wis?=) Date: Mon, 31 Dec 2007 12:37:02 -0000 Subject: [Tracker-discuss] [issue166] document user roles Message-ID: <1199104622.84.0.49654432245.issue166@psf.upfronthosting.co.za> Martin v. L?wis added the comment: I consider this resolved. If somebody thinks further action is necessary, please state what that action should be. ---------- status: chatting -> resolved _______________________________________________________ Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Mon Dec 31 13:42:40 2007 From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v._L=C3=B6wis?=) Date: Mon, 31 Dec 2007 12:42:40 -0000 Subject: [Tracker-discuss] [issue173] Search by "Actor" really means "Last Actor" Message-ID: <1199104960.21.0.58306132996.issue173@psf.upfronthosting.co.za> Martin v. L?wis added the comment: Thanks for the report. This is now fixed in r59616. ---------- status: chatting -> resolved _______________________________________________________ Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Mon Dec 31 13:52:44 2007 From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v._L=C3=B6wis?=) Date: Mon, 31 Dec 2007 12:52:44 -0000 Subject: [Tracker-discuss] [issue135] Not obvious that the main search is limited to 'open' bugs Message-ID: <1199105564.12.0.146704997258.issue135@psf.upfronthosting.co.za> Martin v. L?wis added the comment: This is now fixed in r59618, by changing the label of the search button. Is that solution acceptable? ---------- status: unread -> testing _______________________________________________________ Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Mon Dec 31 14:27:59 2007 From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v._L=C3=B6wis?=) Date: Mon, 31 Dec 2007 13:27:59 -0000 Subject: [Tracker-discuss] [issue171] Order file uploads by date Message-ID: <1199107679.8.0.663478790602.issue171@psf.upfronthosting.co.za> Martin v. L?wis added the comment: This is now fixed in r59619. ---------- status: unread -> resolved _______________________________________________________ Meta Tracker _______________________________________________________