savannah-hackers
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Savannah-hackers] [Mail Delivery System] Mail delivery failed: returnin


From: Mathieu Roy
Subject: [Savannah-hackers] [Mail Delivery System] Mail delivery failed: returning message to sender
Date: Thu, 18 Dec 2003 20:03:37 +0100
User-agent: Gnus/5.1002 (Gnus v5.10.2) Emacs/21.3 (gnu/linux)

For a reason I ignore, the following mail has not been delivered
correctly.





--- Begin Message --- Subject: Mail delivery failed: returning message to sender Date: Thu, 18 Dec 2003 17:52:59 +0100
This message was created automatically by mail delivery software.

A message that you sent could not be delivered to one or more of its
recipients. This is a permanent error. The following address(es) failed:

  address@hidden
    SMTP error from remote mailer after end of data:
    host mx10.gnu.org [199.232.76.166]: 550 Invalid address in message header
  address@hidden
    SMTP error from remote mailer after end of data:
    host mx10.gnu.org [199.232.76.166]: 550 Invalid address in message header
  address@hidden
    SMTP error from remote mailer after end of data:
    host mx10.gnu.org [199.232.76.166]: 550 Invalid address in message header
  address@hidden
    SMTP error from remote mailer after end of data:
    host mx10.gnu.org [199.232.76.166]: 550 Invalid address in message header

------ This is a copy of the message, including all the headers. ------

Return-path: <address@hidden>
Received: from [192.168.1.7] (helo=dionysos.nibelungen.rez)
        by hephaistos.nibelungen.rez with esmtp (Exim 4.30)
        id 1AX1OQ-0004MM-BC; Thu, 18 Dec 2003 17:52:54 +0100
Received: from moa by dionysos.nibelungen.rez with local (Exim 3.36 #1 (Debian))
        id 1AX1OQ-00015h-00; Thu, 18 Dec 2003 17:52:54 +0100
To: Rudy Gevaert <address@hidden>
Cc: "Bradley M. Kuhn" <address@hidden>, savannah-dev <address@hidden>
          Savannah-hackers <address@hidden>,  address@hidden,
          address@hidden
Subject: Re: Savannah situation
X-GPG-Keyserver: http://pgp.mit.edu
X-GPG-Keynumber: 2DA199B9 2002-04-09
References: <address@hidden> <address@hidden>
        <address@hidden> <address@hidden>
        <address@hidden> <address@hidden>
        <address@hidden> <address@hidden>
From: Mathieu Roy <address@hidden>
Date: Thu, 18 Dec 2003 17:52:54 +0100
In-Reply-To: <address@hidden> (Rudy Gevaert's message of
 "Thu, 18 Dec 2003 11:21:40 -0500")
Message-ID: <address@hidden>
User-Agent: Gnus/5.1002 (Gnus v5.10.2) Emacs/21.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: Mathieu Roy <address@hidden>

Rudy Gevaert <address@hidden> said:

> On Thu, Dec 18, 2003 at 09:49:57AM -0500, Bradley M. Kuhn wrote:
>> Is there a way that we can add a flag to the database that will display
>> whether or not a project has been audited or not?  Perhaps it could
>> display a statement that says:
>> 
>>   "This software has not yet been audited since the November 2003 crack of
>>    Savannah."
>> 
>> How hard would it be to do that?
>
> I don't think that will be hard, the only thing that is left to be
> done is to update any select statements in the savannah code to check
> that new field in the datebase.
>

Please, do not ever do any commit before discussing it on
savannah-dev. 

Savannah is developed because there are entities interested in, like
the CERN. Having in the database crap related to our very own crap
(compromise) is not acceptable. No statement in the database should
ever be changed in  favor of a savannah.gnu.org specific issue (people
at CERN are not expecting to have the database inconsistent over
time, for instance). 

If you want to edit the description of a set of project, as Bradley
asked: 

   - create two groups called  GNU-unaudited and nonGNU-unaudited
     group type description, add "This software has not yet been
     audited since the November 2003 crack of Savannah."
   - move every project by a sql command from group GNU to
     GNU-unaudited and  nonGNU to nonGNU-unaudited.
   - when a project is know to be checked, with the web interface, it
     is enough for the admin to change the group type the group
     belongs too.

This way, you can set a specific description, but there are many
others advantages.

There is a way to go without editing the code in almost every
case. The Savannah project is no longer a savannah.gnu.org specific
tool and no change in this last spirit is not acceptable. I made
promise to contributors from the CERN and others similar places and I
intend to keep that promise. 



-- 
Mathieu Roy

  +---------------------------------------------------------------------+
  | General Homepage:           http://yeupou.coleumes.org/             |
  | Computing Homepage:         http://alberich.coleumes.org/           |
  | Not a native english speaker:                                       |
  |     http://stock.coleumes.org/doc.php?i=/misc-files/flawed-english  |
  +---------------------------------------------------------------------+

--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]