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.sh


This 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 list


It looks like the ".dsc" file is missing from the repo: https://ros-dry-releases.googlecode.com/svn/download/stacks/fanuc/fanuc-0.1.0

I'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. 

Tully
 

Shaun

_______________________________________________
ros-release mailing list
ros-release@lists.ros.org
http://lists.ros.org/mailman/listinfo/ros-release