We're not sure what happened.Google Code gave a 404 as can be seen in the linked console output.[oneiric]: invalid control file: /tmp/rosdeb-oneiric/fanuc-0.1.0.yaml Metadata is [<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>404 Not Found</title> </head><body> <h1>Not Found</h1> <p>The requested URL /svn/download/stacks/fanuc/fanuc-0.1.0/fanuc-0.1.0.yaml was not found on this server.</p> </body></html>] [precise]: invalid control file: /tmp/rosdeb-precise/fanuc-0.1.0.yaml Metadata is [<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>404 Not Found</title> </head><body> <h1>Not Found</h1> <p>The requested URL /svn/download/stacks/fanuc/fanuc-0.1.0/fanuc-0.1.0.yaml was not found on this server.</p> </body></html>] [quantal]: invalid control file: /tmp/rosdeb-quantal/fanuc-0.1.0.yaml Metadata is [<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>404 Not Found</title> </head><body> <h1>Not Found</h1> <p>The requested URL /svn/download/stacks/fanuc/fanuc-0.1.0/fanuc-0.1.0.yaml was not found on this server.</p> </body></html>]The job was run atBuild #26 (Sep 16, 2013 11:36:14 AM)
But the files were there before:------------------------------------------------------------------------r97 | shaun.edwards | 2013-09-16 11:35:57 -0700 (Mon, 16 Sep 2013) | 1 linenew release fanuc-0.1.0------------------------------------------------------------------------r96 | shaun.edwards | 2013-09-16 11:35:40 -0700 (Mon, 16 Sep 2013) | 1 linecreating new tarball directory------------------------------------------------------------------------Rerunning it this morning with the same parameters passed:We'll have to keep an eye on this as to whether there is a lag in propogating data from and svn add. If anyone else sees this problem please let us know.TullyOn Tue, Sep 17, 2013 at 10:11 AM, Tully Foote <tfoote@osrfoundation.org> wrote:
On Tue, Sep 17, 2013 at 9:43 AM, Shaun Edwards <shaun.edwards@gmail.com> wrote:
All,I'm having some trouble getting the fanuc stack to release. I ran the pre-release and it has failed in an odd spot during an apt-get update ( http://jenkins.ros.org/view/Prerelease/job/prerelease_groovy_fanuc_precise_amd64/8/console ):Executing command "sudo apt-get update"...Ign http://aptproxy.willoFATAL: Unable to delete script file /tmp/hudson3530644605247371707.shThis is a failure of the executor. I've taken it offline. We'll look into what failed on that machine.I went ahead and performed an official release, even thought the pre-release had issues. The ABB stack had similar problems with pre-release but not the official release. Unfortunately, I wasn't that lucky with the Fanuc release.
The release fails, but for a different reason than above:[build_debs]: Exception was Command '['setarch', 'i386', 'sudo', 'pbuilder', '--build', '--basetgz', '/var/cache/pbuilder/precise-i386-dry_7.tgz', '--configfile', '/home/rosbuild/hudson/workspace/ros-groovy-fanuc_binarydeb_precise_i386/monitored_vcs/rosdeb/pbuilder.conf', '--hookdir', '/home/rosbuild/hudson/workspace/ros-groovy-fanuc_binarydeb_precise_i386/staging_dir/hooks', '--buildresult', '/home/rosbuild/hudson/workspace/ros-groovy-fanuc_binarydeb_precise_i386/staging_dir/results', '--binary-arch', '--buildplace', '/home/rosbuild/hudson/workspace/ros-groovy-fanuc_binarydeb_precise_i386/staging_dir/pbuilder', '/home/rosbuild/hudson/workspace/ros-groovy-fanuc_binarydeb_precise_i386/staging_dir/ros-groovy-fanuc_0.1.0-0~precise.dsc']' returned non-zero exit status 1 [build_debs]: Build of [fanuc] failed, adding to broken listIt looks like the ".dsc" file is missing from the repo: https://ros-dry-releases.googlecode.com/svn/download/stacks/fanuc/fanuc-0.1.0I'm not sure if these two issues are related or separate.Has anybody encountered either of these issues?This looks like the sourcedeb job failed here: http://jenkins.ros.org/job/_dry_sourcedeb/26/console We will look into it. My first guess is that it has on old URL in the configuration.TullyShaun
_______________________________________________
ros-release mailing list
ros-release@lists.ros.org
http://lists.ros.org/mailman/listinfo/ros-release