BATCH: All dressed up, with nowhere to go...
Dear Gumpmeisters, The following 2 notifys should have been sent *** G U M P [g...@vmgump]: Project apache-mailet-base (in module apache-mailet) failed [g...@vmgump]: Project asn1-codec (in module directory-shared) failed *** G U M P [g...@vmgump]: Project apache-mailet-base (in module apache-mailet) failed 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 gene...@gump.apache.org. Project apache-mailet-base has an issue affecting its community integration. This issue affects 1 projects. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - apache-mailet-base : Apache Mailet API Full details are available at: http://vmgump.apache.org/gump/public/apache-mailet/apache-mailet-base/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- (Gump generated) Maven2 Settings in: /srv/gump/public/workspace/apache-mailet/base/trunk/gump_mvn_settings.xml -INFO- Failed with reason build failed -DEBUG- Maven POM in: /srv/gump/public/workspace/apache-mailet/base/trunk/pom.xml -INFO- Failed to extract fallback artifacts from Gump Repository The following work was performed: http://vmgump.apache.org/gump/public/apache-mailet/apache-mailet-base/gump_work/build_apache-mailet_apache-mailet-base.html Work Name: build_apache-mailet_apache-mailet-base (Type: Build) Work ended in a state of : Failed Elapsed: 12 secs Command Line: mvn --batch-mode --settings /srv/gump/public/workspace/apache-mailet/base/trunk/gump_mvn_settings.xml package [Working Directory: /srv/gump/public/workspace/apache-mailet/base/trunk] CLASSPATH: /usr/lib/jvm/java-6-sun/lib/tools.jar:/srv/gump/public/workspace/apache-mailet/api/trunk/target/apache-mailet-2.5-SNAPSHOT.jar - [INFO] Downloading: http://localhost:8192/maven2/javax/mail/mail/1.4.3/mail-1.4.3.pom [INFO] Unable to find resource 'javax.mail:mail:pom:1.4.3' in repository central (http://repo1.maven.org/maven2) Downloading: http://localhost:8192/maven2/javax/activation/activation/1.1.1/activation-1.1.1.pom [INFO] snapshot org.apache.james:apache-mailet:2.5-SNAPSHOT: checking for updates from apache.snapshots [WARNING] repository metadata for: 'snapshot org.apache.james:apache-mailet:2.5-SNAPSHOT' could not be retrieved from repository: apache.snapshots due to an error: Authorization failed: Access denied to: http://localhost:8192/repo/m2-snapshot-repository/org/apache/james/apache-mailet/2.5-SNAPSHOT/maven-metadata.xml [INFO] Repository 'apache.snapshots' will be blacklisted Downloading: http://localhost:8192/maven2/javax/activation/activation/1.1.1/activation-1.1.1.jar 54K downloaded (activation-1.1.1.jar) [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Failed to resolve artifact. Missing: -- 1) org.apache.james:apache-mailet:jar:2.5-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.james -DartifactId=apache-mailet -Dversion=2.5-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.apache.james -DartifactId=apache-mailet -Dversion=2.5-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.james:apache-mailet-base:jar:1.1-SNAPSHOT 2) org.apache.james:apache-mailet:jar:2.5-SNAPSHOT -- 1 required artifact is missing. for artifact: org.apache.james:apache-mailet-base:jar:1.1-SNAPSHOT from the specified remote repositories: gump-central (http://localhost:8192/maven2), gump-apache.snapshots (http://localhost:8192/repo/m2-snapshot-repository) [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total time: 6 seconds [INFO] Finished at: Thu Apr 15 09:57:04 PST 2010 [INFO] Final Memory: 13M/23M [INFO] - To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/apache-mailet/apache-mailet-base/rss.xml -
sshd config change on vmgump
Folks, Following the recent havoc on ASF servers, new rules have been imposed on sshd keys and the use of passwords. I have implemented the first part of this today by changing the sshd configuration. Right now, the only ones that have sshd access are myself and Infra's Joe Schaefer and Mark Thomas. I am seeing the following accounts on the VM: leosimons bodewig brett billbarker dims mvdb sebb Who (still) needs sshd access? I can migrate keys accordingly. Next up, implementation of OPIE which has to happen by May 1 Or Else. Thanks, S. -- san...@temme.net http://www.temme.net/sander/ PGP FP: 51B4 8727 466A 0BC3 69F4 B7B8 B2BE BC40 1529 24AF - To unsubscribe, e-mail: general-unsubscr...@gump.apache.org For additional commands, e-mail: general-h...@gump.apache.org
Re: sshd config change on vmgump
I haven't done anything on gump in a few years. On 16/04/2010, at 11:40 AM, Sander Temme wrote: Folks, Following the recent havoc on ASF servers, new rules have been imposed on sshd keys and the use of passwords. I have implemented the first part of this today by changing the sshd configuration. Right now, the only ones that have sshd access are myself and Infra's Joe Schaefer and Mark Thomas. I am seeing the following accounts on the VM: leosimons bodewig brett billbarker dims mvdb sebb Who (still) needs sshd access? I can migrate keys accordingly. Next up, implementation of OPIE which has to happen by May 1 Or Else. Thanks, S. -- san...@temme.net http://www.temme.net/sander/ PGP FP: 51B4 8727 466A 0BC3 69F4 B7B8 B2BE BC40 1529 24AF -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ - To unsubscribe, e-mail: general-unsubscr...@gump.apache.org For additional commands, e-mail: general-h...@gump.apache.org
Re: sshd config change on vmgump
On 2010-04-16, Sander Temme san...@temme.net wrote: Following the recent havoc on ASF servers, new rules have been imposed on sshd keys and the use of passwords. I have implemented the first part of this today by changing the sshd configuration. Right now, the only ones that have sshd access are myself and Infra's Joe Schaefer and Mark Thomas. Who (still) needs sshd access? I can migrate keys accordingly. I do (as well as on the Solaris zone once that gets migrated). Next up, implementation of OPIE which has to happen by May 1 Or Else. Guess I have some reading to do 8-) Thanks for taking care of it Stefan - To unsubscribe, e-mail: general-unsubscr...@gump.apache.org For additional commands, e-mail: general-h...@gump.apache.org
Re: sshd config change on vmgump
Stefan, On Apr 15, 2010, at 9:15 PM, Stefan Bodewig wrote: On 2010-04-16, Sander Temme san...@temme.net wrote: Following the recent havoc on ASF servers, new rules have been imposed on sshd keys and the use of passwords. I have implemented the first part of this today by changing the sshd configuration. Right now, the only ones that have sshd access are myself and Infra's Joe Schaefer and Mark Thomas. Who (still) needs sshd access? I can migrate keys accordingly. I do (as well as on the Solaris zone once that gets migrated). I have added you to the centralized keystore and the appropriate group. The keys are the same keys that were in your ~/.ssh/authorized_keys* You should be able to log back in now. S. Next up, implementation of OPIE which has to happen by May 1 Or Else. Guess I have some reading to do 8-) Thanks for taking care of it Stefan - To unsubscribe, e-mail: general-unsubscr...@gump.apache.org For additional commands, e-mail: general-h...@gump.apache.org -- Sander Temme scte...@apache.org PGP FP: 51B4 8727 466A 0BC3 69F4 B7B8 B2BE BC40 1529 24AF - To unsubscribe, e-mail: general-unsubscr...@gump.apache.org For additional commands, e-mail: general-h...@gump.apache.org
