[Rock-dev] [rock] #236: tarball package directory deletion not followed by checkout
rock
noreply at opendfki.de
Fri Jan 4 10:20:22 CET 2013
#236: tarball package directory deletion not followed by checkout
-----------------------+-----------------------------------
Reporter: alco01 | Owner: rock-dev-mailing-list
Type: defect | Status: new
Priority: normal | Milestone:
Component: toolchain | Keywords: autoproj tarball
-----------------------+-----------------------------------
Hi,
during autoproj update I was prompted for the deletion of external/yaml-
cpp and answered 'yes' in order to get the new version. I would expect
autoproj to check out said package immediately. Sadly nothing happened,
which I did not notice at first.
{{{
aconquest at laborratte-ad:~/dev/rock.master.1.9/gui/vizkit$ autoproj update
Access method to import data from gitorious.org (git, http or ssh): git
Which prepackaged software (a.k.a. 'osdeps') should autoproj install
automatically (all, ruby, os, none) ? all
autodetecting the operating system
looking for RubyGems updates
updating autoproj main configuration
autoproj: updating remote definitions of package sets
updating rock.toolchain
updating rock
updating rock.tutorials
rock.toolchain: auto-importing orocos.toolchain
updating orocos.toolchain
rock.toolchain: auto-importing rock.base
updating rock.base
WARN: osdeps definition for qtruby, previously defined in
autoproj/remotes/rock.toolchain/rock.osdeps-ruby19 overridden by
autoproj/remotes/rock/rock.osdeps-ruby19
autoproj: loading ...
run 'autoproj reconfigure' to change configuration options
and use 'autoproj switch-config' to change the remote source for
autoproj's main build configuration
Which flavor of Rock do you want to use ? master
Do you need compatibility with OCL ? (yes or no): false
the target operating system for Orocos/RTT (gnulinux or xenomai):
gnulinux
which CORBA implementation should the RTT use ? omniorb
should we delete /home/aconquest/dev/rock.master.1.9/external/yaml-cpp
to update external/yaml-cpp to 0.3.0 ?
a new tarball for external/yaml-cpp is now selected, and I therefore
need to delete the
current directory to update. If you say no, the build will continue
but I will ask
you again next time. [no] yes
deleted /home/aconquest/dev/rock.master.1.9/external/yaml-cpp: a new
archive version is available
autoproj: importing and loading selected packages
updating base/numeric
updating base/orogen/interfaces
...
}}}
I opened a new shell and started builing gui/vizkit manually. Then it
started checking out external/yaml-cpp.
{{{
aconquest at laborratte-ad:~/dev/rock.master.1.9/gui/vizkit/ruby/test$
autoproj build gui/vizkit
Access method to import data from gitorious.org (git, http or ssh): git
Which prepackaged software (a.k.a. 'osdeps') should autoproj install
automatically (all, ruby, os, none) ? all
WARN: osdeps definition for qtruby, previously defined in
autoproj/remotes/rock.toolchain/rock.osdeps-ruby19 overridden by
autoproj/remotes/rock/rock.osdeps-ruby19
autoproj: loading ...
run 'autoproj reconfigure' to change configuration options
and use 'autoproj switch-config' to change the remote source for
autoproj's main build configuration
Which flavor of Rock do you want to use ? master
Do you need compatibility with OCL ? (yes or no): false
the target operating system for Orocos/RTT (gnulinux or xenomai):
gnulinux
which CORBA implementation should the RTT use ? omniorb
autoproj: importing and loading selected packages
checking out external/yaml-cpp
autoproj: building and installing packages
configuring CMake build system for external/yaml-cpp | configuring CMake
build system for image_processing/jpeg_conversion
configuring CMake build system for image_processing/jpeg_conversion |
configuring CMake build system for drivers/aggregator
}}}
I have a hunch that this is not supposed to happen.
Regards
Allan
--
Ticket URL: <https://rock.opendfki.de/ticket/236>
rock <https://rock.opendfki.de>
rock: the robot construction kit
More information about the Rock-dev
mailing list