Dear Gumpmeisters,
            
The following 5 notifys should have been sent

*********************************************************** G U M P
[EMAIL PROTECTED]: Module tl-netty2 success, but with warnings.
[EMAIL PROTECTED]: Module apacheds success, but with warnings.
[EMAIL PROTECTED]: Module ldap-shared success, but with warnings.
[EMAIL PROTECTED]: Module commons-jelly success, but with warnings.
[EMAIL PROTECTED]: Project excalibur-xmlutil (in module excalibur) failed
*********************************************************** G U M P
[EMAIL PROTECTED]: Module tl-netty2 success, but with warnings.
Failed with to: [EMAIL PROTECTED] from: [tl-netty2 development <[EMAIL 
PROTECTED]>]
Failed to send notify e-mail: {'[EMAIL PROTECTED]': (550, 'relaying denied')}
To whom it may engage...
        
This is an automated request, but not an unsolicited one. For 
more information please visit http://gump.apache.org/nagged.html, 
and/or contact the folk at [EMAIL PROTECTED]

Module tl-netty2 contains errors.
The current state of this module is 'Success'.

Full details are available at:
    http://vmgump.apache.org/gump/public/tl-netty2/index.html

That said, some information snippets are provided here.

The following annotations (debug/informational/warning/error messages) were 
provided:
 -ERROR- *** Failed to update from source control. Stale contents ***



The following work was performed:
http://vmgump.apache.org/gump/public/tl-netty2/gump_work/update_tl-netty2.html
Work Name: update_tl-netty2 (Type: Update)
Work ended in a state of : Failed
Elapsed: 
Command Line: svn --quiet update --non-interactive tl-netty2 
[Working Directory: /usr/local/gump/public/workspace/cvs]
---------------------------------------------
svn: Working copy 'tl-netty2' locked
svn: run 'svn cleanup' to remove locks (type 'svn help cleanup' for details)
---------------------------------------------

To subscribe to this information via syndicated feeds:
- RSS: http://vmgump.apache.org/gump/public/tl-netty2/rss.xml
- Atom: http://vmgump.apache.org/gump/public/tl-netty2/atom.xml

============================== Gump Tracking Only ===
Produced by Gump version 2.2.
Gump Run 41321502062005, vmgump.apache.org:vmgump-public:41321502062005
Gump E-mail Identifier (unique within run) #2.

*********************************************************** G U M P
[EMAIL PROTECTED]: Module apacheds success, but with warnings.
Failed with to: [EMAIL PROTECTED] from: [apacheds development 
<[email protected]>]
Failed to send notify e-mail: {'[email protected]': (550, 'SPF forgery: 
Please see 
http://spf.pobox.com/why.html?sender=dev%40directory.apache.org&ip=209.237.227.203&receiver=hermes.apache.org')}
To whom it may engage...
        
This is an automated request, but not an unsolicited one. For 
more information please visit http://gump.apache.org/nagged.html, 
and/or contact the folk at [EMAIL PROTECTED]

Module apacheds contains errors.
The current state of this module is 'Success'.

Full details are available at:
    http://vmgump.apache.org/gump/public/apacheds/index.html

That said, some information snippets are provided here.

The following annotations (debug/informational/warning/error messages) were 
provided:
 -ERROR- *** Failed to update from source control. Stale contents ***



The following work was performed:
http://vmgump.apache.org/gump/public/apacheds/gump_work/update_apacheds.html
Work Name: update_apacheds (Type: Update)
Work ended in a state of : Failed
Elapsed: 
Command Line: svn --quiet update --non-interactive apacheds 
[Working Directory: /usr/local/gump/public/workspace/cvs]
---------------------------------------------
svn: Working copy 'apacheds' locked
svn: run 'svn cleanup' to remove locks (type 'svn help cleanup' for details)
---------------------------------------------

To subscribe to this information via syndicated feeds:
- RSS: http://vmgump.apache.org/gump/public/apacheds/rss.xml
- Atom: http://vmgump.apache.org/gump/public/apacheds/atom.xml

============================== Gump Tracking Only ===
Produced by Gump version 2.2.
Gump Run 41321502062005, vmgump.apache.org:vmgump-public:41321502062005
Gump E-mail Identifier (unique within run) #3.

*********************************************************** G U M P
[EMAIL PROTECTED]: Module ldap-shared success, but with warnings.
Failed with to: [EMAIL PROTECTED] from: [ldap-shared development 
<[email protected]>]
Failed to send notify e-mail: {'[email protected]': (550, 'SPF forgery: 
Please see 
http://spf.pobox.com/why.html?sender=dev%40directory.apache.org&ip=209.237.227.203&receiver=hermes.apache.org')}
To whom it may engage...
        
This is an automated request, but not an unsolicited one. For 
more information please visit http://gump.apache.org/nagged.html, 
and/or contact the folk at [EMAIL PROTECTED]

Module ldap-shared contains errors.
The current state of this module is 'Success'.

Full details are available at:
    http://vmgump.apache.org/gump/public/ldap-shared/index.html

That said, some information snippets are provided here.

The following annotations (debug/informational/warning/error messages) were 
provided:
 -ERROR- *** Failed to update from source control. Stale contents ***



The following work was performed:
http://vmgump.apache.org/gump/public/ldap-shared/gump_work/update_ldap-shared.html
Work Name: update_ldap-shared (Type: Update)
Work ended in a state of : Failed
Elapsed: 
Command Line: svn --quiet update --non-interactive ldap-shared 
[Working Directory: /usr/local/gump/public/workspace/cvs]
---------------------------------------------
svn: Working copy 'ldap-shared' locked
svn: run 'svn cleanup' to remove locks (type 'svn help cleanup' for details)
---------------------------------------------

To subscribe to this information via syndicated feeds:
- RSS: http://vmgump.apache.org/gump/public/ldap-shared/rss.xml
- Atom: http://vmgump.apache.org/gump/public/ldap-shared/atom.xml

============================== Gump Tracking Only ===
Produced by Gump version 2.2.
Gump Run 41321502062005, vmgump.apache.org:vmgump-public:41321502062005
Gump E-mail Identifier (unique within run) #4.

*********************************************************** G U M P
[EMAIL PROTECTED]: Module commons-jelly success, but with warnings.
Failed with to: [EMAIL PROTECTED] from: [commons-jelly development 
<[email protected]>]
Failed to send notify e-mail: {'[email protected]': (550, 'SPF 
forgery: Please see 
http://spf.pobox.com/why.html?sender=commons-dev%40jakarta.apache.org&ip=209.237.227.203&receiver=hermes.apache.org')}
To whom it may engage...
        
This is an automated request, but not an unsolicited one. For 
more information please visit http://gump.apache.org/nagged.html, 
and/or contact the folk at [EMAIL PROTECTED]

Module commons-jelly contains errors.
The current state of this module is 'Success'.

Full details are available at:
    http://vmgump.apache.org/gump/public/commons-jelly/index.html

That said, some information snippets are provided here.

The following annotations (debug/informational/warning/error messages) were 
provided:
 -ERROR- *** Failed to update from source control. Stale contents ***



The following work was performed:
http://vmgump.apache.org/gump/public/commons-jelly/gump_work/update_commons-jelly.html
Work Name: update_commons-jelly (Type: Update)
Work ended in a state of : Failed
Elapsed: 
Command Line: svn --quiet update --non-interactive commons-jelly 
[Working Directory: /usr/local/gump/public/workspace/cvs]
---------------------------------------------
svn: Working copy 'commons-jelly' locked
svn: run 'svn cleanup' to remove locks (type 'svn help cleanup' for details)
---------------------------------------------

To subscribe to this information via syndicated feeds:
- RSS: http://vmgump.apache.org/gump/public/commons-jelly/rss.xml
- Atom: http://vmgump.apache.org/gump/public/commons-jelly/atom.xml

============================== Gump Tracking Only ===
Produced by Gump version 2.2.
Gump Run 41321502062005, vmgump.apache.org:vmgump-public:41321502062005
Gump E-mail Identifier (unique within run) #5.

*********************************************************** G U M P
[EMAIL PROTECTED]: Project excalibur-xmlutil (in module excalibur) failed
Failed with to: [EMAIL PROTECTED] from: [Gump <[email protected]>]
Failed to send notify e-mail: {'[email protected]': (550, 'SPF forgery: 
Please see 
http://spf.pobox.com/why.html?sender=dev%40excalibur.apache.org&ip=209.237.227.203&receiver=hermes.apache.org')}
To whom it may engage...
        
This is an automated request, but not an unsolicited one. For 
more information please visit http://gump.apache.org/nagged.html, 
and/or contact the folk at [EMAIL PROTECTED]

Project excalibur-xmlutil has an issue affecting its community integration.
This issue affects 1 projects,
 and has been outstanding for 3 runs.
The current state of this project is 'Failed', with reason 'Configuration 
Failed'.
For reference only, the following projects are affected by this:
    - excalibur-xmlutil :  Repository of reusable components.


Full details are available at:
    http://vmgump.apache.org/gump/public/excalibur/excalibur-xmlutil/index.html

That said, some information snippets are provided here.

The following annotations (debug/informational/warning/error messages) were 
provided:
 -DEBUG- Sole output [excalibur-xmlutil-02062005.jar] identifier set to project 
name
 -INFO- Failed with reason configuration failed
 -ERROR- Bad Dependency. Project: saxpath unknown to *this* workspace
 -INFO- Optional dependency checkstyle prerequisite failed with reason build 
failed
 -INFO- Failed to extract fallback artifacts from Gump Repository

To subscribe to this information via syndicated feeds:
- RSS: http://vmgump.apache.org/gump/public/excalibur/excalibur-xmlutil/rss.xml
- Atom: 
http://vmgump.apache.org/gump/public/excalibur/excalibur-xmlutil/atom.xml

============================== Gump Tracking Only ===
Produced by Gump version 2.2.
Gump Run 41321502062005, vmgump.apache.org:vmgump-public:41321502062005
Gump E-mail Identifier (unique within run) #17.


--
Apache Gump
http://gump.apache.org/ [Instance: vmgump]

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to