Re: [Python-Dev] Failed issue tracker submission
On Fri, 16 Nov 2012 22:35:38 -0800 Chris Jerdonek chris.jerdo...@gmail.com wrote: I'm pretty sure it's because python-dev is the 'from' address used when the messages are sent...and the configuration of that user is what allows them to be accepted. I suggest changing the from address and the account configuration to tracker-disc...@python.org instead. Above and on the meta tracker issue I filed, it sounds like Martin is saying that the e-mails should never be going to python-dev (or tracker-discuss) in the first place -- due to a roundup bug and because the e-mail is already being sent to the submitter and the roundup admins. Thus, changing the from address would only mitigate the problem and not be fixing the root cause. So, for the record, the From address has been changed to tracker-disc...@python.org, so python-dev shouldn't be spammed anymore. Cheers Antoine. ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Failed issue tracker submission
I filed an issue in the meta tracker about e-mails like the below that are sent to python-dev. The issue link is here: http://psf.upfronthosting.co.za/roundup/meta/issue492 --Chris On Thu, Nov 15, 2012 at 6:39 PM, Python tracker roundup-ad...@psf.upfronthosting.co.za wrote: An unexpected error occurred during the processing of your message. The tracker administrator is being notified. Return-Path: python-dev@python.org X-Original-To: rep...@bugs.python.org Delivered-To: roundup+trac...@psf.upfronthosting.co.za Received: from mail.python.org (mail.python.org [IPv6:2001:888:2000:d::a6]) by psf.upfronthosting.co.za (Postfix) with ESMTPS id DFD211C98E for rep...@bugs.python.org; Fri, 16 Nov 2012 03:39:49 +0100 (CET) Received: from albatross.python.org (localhost [127.0.0.1]) by mail.python.org (Postfix) with ESMTP id 3Y2kDj4Tk8zRb6 for rep...@bugs.python.org; Fri, 16 Nov 2012 03:39:49 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=python.org; s=200901; t=1353033589; bh=H41Haza/UPvj9B16qvXQtqjlb22jRmazur238MqAPOE=; h=MIME-Version:Content-Type:Content-Transfer-Encoding:From:To: Subject:Message-Id:Date; b=yz1YIEtIYuM3H9V1Ok0YJ/SDvU8xtO+cFOApgDH8jPRdxRS6z/CSdZ96bSY1cNFM7 4xxKY3LiUXipe439DPwEjxZr0HcsfX+2JdR4Pzf3OZmdopV6PEl8/twaIFoTHQMy8u dTwpZ7G4OJKCc2IeCq4e5Bl/TEvQvVT9NO8eoa3k= Received: from localhost (HELO mail.python.org) (127.0.0.1) by albatross.python.org with SMTP; 16 Nov 2012 03:39:49 +0100 Received: from virt-7yvsjn.psf.osuosl.org (virt-7yvsjn.psf.osuosl.org [140.211.10.72]) by mail.python.org (Postfix) with ESMTP for rep...@bugs.python.org; Fri, 16 Nov 2012 03:39:49 +0100 (CET) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: base64 From: python-dev@python.org To: rep...@bugs.python.org Subject: [issue15894] Message-Id: 3y2kdj4tk8z...@mail.python.org Date: Fri, 16 Nov 2012 03:39:49 +0100 (CET) TmV3IGNoYW5nZXNldCBiZDg1MzMxMWZmZTAgYnkgQnJldHQgQ2Fubm9uIGluIGJyYW5jaCAnZGVm YXVsdCc6Cklzc3VlICMxNTg5NDogRG9jdW1lbnQgd2h5IHdlIGRvbid0IHdvcnJ5IGFib3V0IHJl LWFjcXVpcmluZyB0aGUKaHR0cDovL2hnLnB5dGhvbi5vcmcvY3B5dGhvbi9yZXYvYmQ4NTMzMTFm ZmUwCg== ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/chris.jerdonek%40gmail.com ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Failed issue tracker submission
On Fri, 16 Nov 2012 12:47:52 -0800 Chris Jerdonek chris.jerdo...@gmail.com wrote: I filed an issue in the meta tracker about e-mails like the below that are sent to python-dev. The issue link is here: http://psf.upfronthosting.co.za/roundup/meta/issue492 These e-mails are just because someone mentioned the wrong issue number in a commit message, I think. Regards Antoine. ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Failed issue tracker submission
But python-dev seems a poor place to spam with those errors. On Fri, Nov 16, 2012 at 2:41 PM, Antoine Pitrou solip...@pitrou.net wrote: On Fri, 16 Nov 2012 12:47:52 -0800 Chris Jerdonek chris.jerdo...@gmail.com wrote: I filed an issue in the meta tracker about e-mails like the below that are sent to python-dev. The issue link is here: http://psf.upfronthosting.co.za/roundup/meta/issue492 These e-mails are just because someone mentioned the wrong issue number in a commit message, I think. Regards Antoine. ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/guido%40python.org -- --Guido van Rossum (python.org/~guido) ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Failed issue tracker submission
Zitat von Guido van Rossum gu...@python.org: But python-dev seems a poor place to spam with those errors. It's certainly not deliberate that they are sent. However, there are too few people interested in working on fixing that so that it remains unfixed. Even finding out why they are sent to python-dev is tricky. Regards, Martin ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Failed issue tracker submission
On Sat, 17 Nov 2012 00:47:33 +0100 mar...@v.loewis.de wrote: Zitat von Guido van Rossum gu...@python.org: But python-dev seems a poor place to spam with those errors. It's certainly not deliberate that they are sent. However, there are too few people interested in working on fixing that so that it remains unfixed. Even finding out why they are sent to python-dev is tricky. I think it's because I configured the dummy python-dev user that way: http://bugs.python.org/user13902 Regards Antoine. ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Failed issue tracker submission
On Sat, 17 Nov 2012 01:01:52 +0100, Antoine Pitrou solip...@pitrou.net wrote: On Sat, 17 Nov 2012 00:47:33 +0100 mar...@v.loewis.de wrote: Zitat von Guido van Rossum gu...@python.org: But python-dev seems a poor place to spam with those errors. It's certainly not deliberate that they are sent. However, there are too few people interested in working on fixing that so that it remains unfixed. Even finding out why they are sent to python-dev is tricky. I think it's because I configured the dummy python-dev user that way: http://bugs.python.org/user13902 I'm pretty sure it's because python-dev is the 'from' address used when the messages are sent...and the configuration of that user is what allows them to be accepted. I suggest changing the from address and the account configuration to tracker-disc...@python.org instead. --David ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Failed issue tracker submission
On Fri, Nov 16, 2012 at 10:06 PM, R. David Murray rdmur...@bitdance.com wrote: On Sat, 17 Nov 2012 01:01:52 +0100, Antoine Pitrou solip...@pitrou.net wrote: On Sat, 17 Nov 2012 00:47:33 +0100 mar...@v.loewis.de wrote: Zitat von Guido van Rossum gu...@python.org: But python-dev seems a poor place to spam with those errors. It's certainly not deliberate that they are sent. However, there are too few people interested in working on fixing that so that it remains unfixed. Even finding out why they are sent to python-dev is tricky. I think it's because I configured the dummy python-dev user that way: http://bugs.python.org/user13902 I'm pretty sure it's because python-dev is the 'from' address used when the messages are sent...and the configuration of that user is what allows them to be accepted. I suggest changing the from address and the account configuration to tracker-disc...@python.org instead. Above and on the meta tracker issue I filed, it sounds like Martin is saying that the e-mails should never be going to python-dev (or tracker-discuss) in the first place -- due to a roundup bug and because the e-mail is already being sent to the submitter and the roundup admins. Thus, changing the from address would only mitigate the problem and not be fixing the root cause. --Chris ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Failed issue tracker submission
Python tracker wrote: The node specified by the designator in the subject of your message (715365) does not exist. Subject was: [issue715365] Is this related to the Coverity ID being mentioned in http://bugs.python.org/issue15868 ? ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Failed issue tracker submission
Petri Lehtinen pe...@digip.org wrote: (715365) does not exist. Is this related to the Coverity ID being mentioned in http://bugs.python.org/issue15868 ? Must be. I used the pattern #number twice in the commit message: http://hg.python.org/cpython/rev/df663603e67a So let's avoid that in the future. Stefan Krah ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Failed issue tracker submission
On Sat, Sep 8, 2012 at 9:17 PM, Stefan Krah ste...@bytereef.org wrote: Petri Lehtinen pe...@digip.org wrote: (715365) does not exist. Is this related to the Coverity ID being mentioned in http://bugs.python.org/issue15868 ? Must be. I used the pattern #number twice in the commit message: http://hg.python.org/cpython/rev/df663603e67a No, using the pattern number twice is OK now - it's using it for an issue that *doesn't exist* that broke. Better to just not use that notation for the Coverity ID's by writing CID 715365 or something similar so we don't get any false hits on the tracker integration. Cheers, Nick. -- Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Failed issue tracker submission
Cheers On Apr 21, 2012 10:25 AM, R. David Murray rdmur...@bitdance.com wrote: On Sat, 21 Apr 2012 08:54:56 +0800, Matt Joiner anacro...@gmail.com wrote: I'm getting one of these every couple of days. What's the deal? On Apr 21, 2012 1:03 AM, Python tracker roundup-ad...@psf.upfronthosting.co.za wrote: There is a bug in the interface between roundup and hg that is new since roundup was switched to using xapian for indexing. When an hg commit mentions more than one issue number, the second (or subsequent, presumably) issue number triggers a write conflict and results in the email doing the second issue update being rejected. Since the email address associated with the hg update email is python-dev, the bounce gets sent here. There are currently only three people who do maintenance work on the tracker (it used to be just one), and none of us have found time to try to figure out a fix yet. --David ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Failed issue tracker submission
I'm getting one of these every couple of days. What's the deal? On Apr 21, 2012 1:03 AM, Python tracker roundup-ad...@psf.upfronthosting.co.za wrote: An unexpected error occurred during the processing of your message. The tracker administrator is being notified. Return-Path: python-dev@python.org X-Original-To: rep...@bugs.python.org Delivered-To: roundup+trac...@psf.upfronthosting.co.za Received: from mail.python.org (mail.python.org [82.94.164.166]) by psf.upfronthosting.co.za (Postfix) with ESMTPS id 833861CBB0 for rep...@bugs.python.org; Fri, 20 Apr 2012 19:00:09 +0200 (CEST) Received: from albatross.python.org (localhost [127.0.0.1]) by mail.python.org (Postfix) with ESMTP id 3VZ3GK10QGzN51 for rep...@bugs.python.org; Fri, 20 Apr 2012 19:00:09 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=python.org; s=200901; t=1334941209; bh=PuPHOLI7fb95kba5/ecLxSLCC9UpM27v8bYaw31epzE=; h=Date:Message-Id:Content-Type:MIME-Version: Content-Transfer-Encoding:From:To:Subject; b=ZfbTowau33LvKWnJHYtZ8Fy/cAslebBopL912urudimFDYNg5n7CHpPwxlMLlLTv5 tR2OZmCp3w90e6h937L7R6g7mew3xHaxeRbzP06cEK0JTyOQaekSKHBxivVMuU2hjL AE1J6MRlKrxJoqE8dQMyzP7+wM5o39unn76WD6bE= Received: from localhost (HELO mail.python.org) (127.0.0.1) by albatross.python.org with SMTP; 20 Apr 2012 19:00:09 +0200 Received: from dinsdale.python.org (svn.python.org[IPv6:2001:888:2000:d::a4]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by mail.python.org (Postfix) with ESMTPS for rep...@bugs.python.org; Fri, 20 Apr 2012 19:00:09 +0200 (CEST) Received: from localhost ([127.0.0.1] helo=dinsdale.python.org ident=hg) by dinsdale.python.org with esmtp (Exim 4.72) (envelope-from python-dev@python.org) id 1SLHBo-00063N-NT for rep...@bugs.python.org; Fri, 20 Apr 2012 19:00:08 +0200 Date: Fri, 20 Apr 2012 19:00:08 +0200 Message-Id: e1slhbo-00063n...@dinsdale.python.org Content-Type: text/plain; charset=utf8 MIME-Version: 1.0 Content-Transfer-Encoding: base64 From: python-dev@python.org To: rep...@bugs.python.org Subject: [issue14633] TmV3IGNoYW5nZXNldCBhMjgxYTY2MjI3MTQgYnkgQnJldHQgQ2Fubm9uIGluIGJyYW5jaCAnZGVm YXVsdCc6Cklzc3VlICMxNDYzMzogU2ltcGxpZnkgaW1wLmZpbmRfbW9kdWUoKSB0ZXN0IGFmdGVy IGZpeGVzIGZyb20gaXNzdWUKaHR0cDovL2hnLnB5dGhvbi5vcmcvY3B5dGhvbi9yZXYvYTI4MWE2 NjIyNzE0Cg== ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/anacrolix%40gmail.com ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Failed issue tracker submission
On Sat, 21 Apr 2012 08:54:56 +0800, Matt Joiner anacro...@gmail.com wrote: I'm getting one of these every couple of days. What's the deal? On Apr 21, 2012 1:03 AM, Python tracker roundup-ad...@psf.upfronthosting.co.za wrote: There is a bug in the interface between roundup and hg that is new since roundup was switched to using xapian for indexing. When an hg commit mentions more than one issue number, the second (or subsequent, presumably) issue number triggers a write conflict and results in the email doing the second issue update being rejected. Since the email address associated with the hg update email is python-dev, the bounce gets sent here. There are currently only three people who do maintenance work on the tracker (it used to be just one), and none of us have found time to try to figure out a fix yet. --David ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Failed issue tracker submission
On Thu, 05 Apr 2012 01:29:47 -, Python tracker roundup-ad...@psf.upfronthosting.co.za wrote: An unexpected error occurred during the processing of your message. The tracker administrator is being notified. Since the bounce message went here, I'm posting this here for those who are curious what caused it. It was triggered by my committing a patch with two issue numbers in the commit message. This triggered a DB lock problem on the roundup end, from the xapian indexer: Traceback (most recent call last): File /home/roundup/lib/python2.5/site-packages/roundup/mailgw.py, line 1395, in handle_Message return self.handle_message(message) File /home/roundup/lib/python2.5/site-packages/roundup/mailgw.py, line 1451, in handle_message return self._handle_message(message) File /home/roundup/lib/python2.5/site-packages/roundup/mailgw.py, line 1529, in _handle_message parsed_message.create_msg() File /home/roundup/lib/python2.5/site-packages/roundup/mailgw.py, line 1105, in create_msg messageid=messageid, inreplyto=inreplyto, **self.msg_props) File /home/roundup/lib/python2.5/site- packages/roundup/backends/rdbms_common.py, line 2958, in create content, mime_type) File /home/roundup/lib/python2.5/site- packages/roundup/backends/indexer_xapian.py, line 59, in add_text database = self._get_database() File /home/roundup/lib/python2.5/site- packages/roundup/backends/indexer_xapian.py, line 21, in _get_database return xapian.WritableDatabase(index, xapian.DB_CREATE_OR_OPEN) File /usr/lib/python2.6/dist-packages/xapian/__init__.py, line 4059, in __init__ _xapian.WritableDatabase_swiginit(self,_xapian.new_WritableDatabase(*args)) DatabaseLockError: Unable to get write lock on /home/roundup/trackers/tracker/db /text-index: already locked The Xapian index is new since the server upgrade, so it is possible this will always happen when more than one issue number is mentioned. Or it could be a random timing thing. Presumably it could also occur during normal web submissions if they happen to happen at the same time, which is a little bit worrisome. If anyone has any Xapien experience and would be willing to help out with debugging this and/or some indexing issues, please let me know :) --David ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Failed issue tracker submission
2011/3/29 Python tracker roundup-ad...@psf.upfronthosting.co.za: The node specified by the designator in the subject of your message (22663) does not exist. Subject was: [issue22663] Aha. This email was probably generated by a commit hook because this changeset http://hg.python.org/cpython/rev/dd852a0f92d6 has a typo in the issue number, it should have been 11662. Mail Gateway Help = Incoming messages are examined for multiple parts: . In a multipart/mixed message or part, each subpart is extracted and examined. The text/plain subparts are assembled to form the textual body of the message, to be stored in the file associated with a msg class node. Any parts of other types are each stored in separate files and given file class nodes that are linked to the msg node. . In a multipart/alternative message or part, we look for a text/plain subpart and ignore the other parts. Summary --- The summary property on message nodes is taken from the first non-quoting section in the message body. The message body is divided into sections by blank lines. Sections where the second and all subsequent lines begin with a or | character are considered quoting sections. The first line of the first non-quoting section becomes the summary of the message. Addresses - All of the addresses in the To: and Cc: headers of the incoming message are looked up among the user nodes, and the corresponding users are placed in the recipients property on the new msg node. The address in the From: header similarly determines the author property of the new msg node. The default handling for addresses that don't have corresponding users is to create new users with no passwords and a username equal to the address. (The web interface does not permit logins for users with no passwords.) If we prefer to reject mail from outside sources, we can simply register an auditor on the user class that prevents the creation of user nodes with no passwords. Actions --- The subject line of the incoming message is examined to determine whether the message is an attempt to create a new item or to discuss an existing item. A designator enclosed in square brackets is sought as the first thing on the subject line (after skipping any Fwd: or Re: prefixes). If an item designator (class name and id number) is found there, the newly created msg node is added to the messages property for that item, and any new file nodes are added to the files property for the item. If just an item class name is found there, we attempt to create a new item of that class with its messages property initialized to contain the new msg node and its files property initialized to contain any new file nodes. Triggers Both cases may trigger detectors (in the first case we are calling the set() method to add the message to the item's spool; in the second case we are calling the create() method to create a new node). If an auditor raises an exception, the original message is bounced back to the sender with the explanatory message given in the exception. $Id: mailgw.py,v 1.196 2008-07-23 03:04:44 richard Exp $ Return-Path: python-dev@python.org X-Original-To: rep...@bugs.python.org Delivered-To: roundup+trac...@psf.upfronthosting.co.za Received: from mail.python.org (mail.python.org [82.94.164.166]) by psf.upfronthosting.co.za (Postfix) with ESMTPS id 7DCEE1DEB0 for rep...@bugs.python.org; Tue, 29 Mar 2011 22:10:55 +0200 (CEST) Received: from albatross.python.org (localhost [127.0.0.1]) by mail.python.org (Postfix) with ESMTP id 3PzjsW1q1lz7Lmy for rep...@bugs.python.org; Tue, 29 Mar 2011 22:10:55 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=python.org; s=200901; t=1301429455; bh=WYL3NF6gQtbDZ+R9KxXHGS2PSlCAxyY+EQEgb/Yw5jI=; h=Date:Message-Id:Content-Type:MIME-Version: Content-Transfer-Encoding:From:To:Subject; b=RiMAivS4Shae7bPg7E7SocheqYB9pzk/Svimv+qumX5arnUaaC8h9iIJo8MFDcDdi +Wk0XzTjTjKsbobrKgZnfZf9a8j6Fv4Ym1nTyTcPcyjCMritjq9xNUluVQvHv/Vn2e RhpV2FUWOdCtBx83eUopMPGEEEwABnbG5ZwgsDzM= Received: from localhost (HELO mail.python.org) (127.0.0.1) by albatross.python.org with SMTP; 29 Mar 2011 22:10:55 +0200 Received: from dinsdale.python.org (svn.python.org [IPv6:2001:888:2000:d::a4]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by mail.python.org (Postfix) with ESMTPS for rep...@bugs.python.org; Tue, 29 Mar 2011 22:10:55 +0200 (CEST) Received: from localhost ([127.0.0.1] helo=dinsdale.python.org ident=hg) by dinsdale.python.org with esmtp (Exim 4.72) (envelope-from python-dev@python.org) id 1Q4fFf-00023G-4C for rep...@bugs.python.org; Tue, 29 Mar 2011 22:10:55 +0200 Date: Tue, 29 Mar 2011 22:10:55 +0200 Message-Id: e1q4fff-00023g...@dinsdale.python.org
Re: [Python-Dev] Failed issue tracker submission
Ouch. I fear this message may be repeated several times :/ Sorry for the spam, if that happens... Regards Antoine. On Tue, 08 Mar 2011 19:32:20 + Python tracker roundup-ad...@psf.upfronthosting.co.za wrote: You are not a registered user. Unknown address: python-dev@python.org ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Failed issue tracker submission
You are not a registered user. Unknown address: python-dev@python.org I should point out that I approved this message, mostly so whoever has thinks set up to send messages to the meta tracker as python-dev can fix the problem. Skip ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Failed issue tracker submission
Antoine Ouch. I fear this message may be repeated several times :/ Antoine Sorry for the spam, if that happens... Do you want me to reject or discard future messages to python-dev from roundup-admin? Skip ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Failed issue tracker submission
Le mardi 08 mars 2011 à 14:51 -0600, s...@pobox.com a écrit : Antoine Ouch. I fear this message may be repeated several times :/ Antoine Sorry for the spam, if that happens... Do you want me to reject or discard future messages to python-dev from roundup-admin? Hopefully there won't be any more (I've fixed the issue by creating an appropriate Roundup user). I think it's better not to discard them, in case it starts failing again. Regards Antoine. ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
