Testing needed: autoproj 1.6.2.rc9

First, changelog, then installation/upgrade instructions.

Changelog:

* overhauled osdeps fine-grained configuration. See
http://orocos.org/dfki-next/autoproj/osdeps.html
for more information
* fix too-aggressive caching of operating system characteristics,
which breaks on OS upgrades.
* on Debian-like systems, filter out packages that are already
installed
* on all systems, filter packages that have already been handled by
the osdeps
* add a -k option that continues operation even after errors. The sum
of all errors are properly presented at the end of the run.
* when boostrapping, check that the current directory is empty and
warn the user if it is not.
* the 'default' option can be used in osdeps to fall-back on version
and/or OS name. I.e.

ubuntu:
9.04: special_package
default: normal_package_for_all_other_versions_of_ubuntu

* a few more minor bugfixes

To install in an already bootstrapped installation:

gem install --prerelease autoproj

To bootstrap a new installation using 1.6.2.rc9

1. you MUST use the bootstrap script at
http://orocos.org/dfki-next/autoproj_bootstrap
2. run it with the "dev" option
autoproj_bootstrap dev git
git://gitorious.org/orocos-toolchain/autoproj.git branch=master

Testing needed: autoproj 1.6.2.rc9

On 11/02/2010 03:27 PM, Sylvain Joyeux wrote:
> First, changelog, then installation/upgrade instructions.
>
> Changelog:
>
> * overhauled osdeps fine-grained configuration. See
> http://orocos.org/dfki-next/autoproj/osdeps.html
> for more information
> * fix too-aggressive caching of operating system characteristics,
> which breaks on OS upgrades.
> * on Debian-like systems, filter out packages that are already
> installed
> * on all systems, filter packages that have already been handled by
> the osdeps
> * add a -k option that continues operation even after errors. The sum
> of all errors are properly presented at the end of the run.
> * when boostrapping, check that the current directory is empty and
> warn the user if it is not.
> * the 'default' option can be used in osdeps to fall-back on version
> and/or OS name. I.e.
>
> ubuntu:
> 9.04: special_package
> default: normal_package_for_all_other_versions_of_ubuntu
>
> * a few more minor bugfixes
>
> To install in an already bootstrapped installation:
>
> gem install --prerelease autoproj
>
> To bootstrap a new installation using 1.6.2.rc9
>
> 1. you MUST use the bootstrap script at
> http://orocos.org/dfki-next/autoproj_bootstrap
> 2. run it with the "dev" option
> autoproj_bootstrap dev git
> git://gitorious.org/orocos-toolchain/autoproj.git branch=master

Some more information (sorry Leopold ...)

- "dev" MUST be the first on the autoproj_bootstrap command line
- the repository I list above is wrong. The proper repository is
git://gitorious.org/orocos-toolchain/build.git

The test command line is therefore

autoproj_bootstrap dev git git://gitorious.org/orocos-toolchain/build.git

Testing needed: autoproj 1.6.2.rc9

A Dimarts 02 Novembre 2010, Sylvain Joyeux va escriure:
> First, changelog, then installation/upgrade instructions.
>
> Changelog:
>
> * overhauled osdeps fine-grained configuration. See
> http://orocos.org/dfki-next/autoproj/osdeps.html
> for more information
> * fix too-aggressive caching of operating system characteristics,
> which breaks on OS upgrades.
> * on Debian-like systems, filter out packages that are already
> installed
> * on all systems, filter packages that have already been handled by
> the osdeps
> * add a -k option that continues operation even after errors. The sum
> of all errors are properly presented at the end of the run.
> * when boostrapping, check that the current directory is empty and
> warn the user if it is not.
> * the 'default' option can be used in osdeps to fall-back on version
> and/or OS name. I.e.
>
> ubuntu:
> 9.04: special_package
> default: normal_package_for_all_other_versions_of_ubuntu
>
> * a few more minor bugfixes
>
> To install in an already bootstrapped installation:
>
> gem install --prerelease autoproj
>
> To bootstrap a new installation using 1.6.2.rc9
>
> 1. you MUST use the bootstrap script at
> http://orocos.org/dfki-next/autoproj_bootstrap
> 2. run it with the "dev" option
> autoproj_bootstrap dev git
> git://gitorious.org/orocos-toolchain/autoproj.git branch=master

I have run:

./autoproj_bootstrap --verbose dev git
git://gitorious.org/orocos-toolchain/autoproj.git branch=master

and I got

autodetecting the operating system
Which prepackaged software (a.k.a. 'osdeps') should autoproj install
automatically (all, ruby, os, none) ?
The software packages that autoproj will have to build may require other
prepackaged softwares (a.k.a. OS dependencies) to be installed (RubyGems
packages, packages from your operating system/distribution, ...). Autoproj
is able to install those automatically for you.

Advanced users may want to control this behaviour. Additionally, the
installation of some packages require administration rights, which you may
not have. This option is meant to allow you to control autoproj's
behaviour
while handling OS dependencies.

* if you say "all", it will install all packages automatically.
This requires root access thru 'sudo'
* if you say "ruby", only the Ruby packages will be installed.
Installing these packages does not require root access.
* if you say "os", only the OS-provided packages will be installed.
Installing these packages requires root access.
* if you say "none", autoproj will not do anything related to the
OS dependencies.

As any configuration value, the mode can be changed anytime by calling
an autoproj operation with the --reconfigure option (e.g. autoproj update
--reconfigure).

Finally, OS dependencies can be installed by calling "autoproj osdeps"
with the corresponding option (--all, --ruby, --os or --none). [all]
autoproj: installing a proper Ruby environment (this can take a long time)
autoproj: installing autoproj and its dependencies (this can take a long time)
installing/updating RubyGems dependencies: autobuild, rdoc
installing/updating RubyGems dependencies: autoproj

version control dev is unknown to autoproj

in /home/users/leopold.palomo/robotica/orocos/orocos-toolchain/autoproj/.gems/gems/autoproj-1.6.1/lib/autoproj/manifest.rb:89:in
`initialize'

in /home/users/leopold.palomo/robotica/orocos/orocos-toolchain/autoproj/.gems/gems/autoproj-1.6.1/lib/autoproj/manifest.rb:162:in
`new'

in /home/users/leopold.palomo/robotica/orocos/orocos-toolchain/autoproj/.gems/gems/autoproj-1.6.1/lib/autoproj/manifest.rb:162:in
`normalize_vcs_definition'

in /home/users/leopold.palomo/robotica/orocos/orocos-toolchain/autoproj/.gems/gems/autoproj-1.6.1/lib/autoproj/cmdline.rb:924:in
`do_switch_config'

in /home/users/leopold.palomo/robotica/orocos/orocos-toolchain/autoproj/.gems/gems/autoproj-1.6.1/lib/autoproj/cmdline.rb:1018:in
`bootstrap'

in /home/users/leopold.palomo/robotica/orocos/orocos-toolchain/autoproj/.gems/gems/autoproj-1.6.1/lib/autoproj/cmdline.rb:685:in
`handle_mode'

in /home/users/leopold.palomo/robotica/orocos/orocos-toolchain/autoproj/.gems/gems/autoproj-1.6.1/lib/autoproj/cmdline.rb:656:in
`parse_arguments'

in /home/users/leopold.palomo/robotica/orocos/orocos-toolchain/autoproj/.gems/gems/autoproj-1.6.1/lib/autoproj/cmdline.rb:655:in
`catch'

in /home/users/leopold.palomo/robotica/orocos/orocos-toolchain/autoproj/.gems/gems/autoproj-1.6.1/lib/autoproj/cmdline.rb:655:in
`parse_arguments'

in /home/users/leopold.palomo/robotica/orocos/orocos-toolchain/autoproj/.gems/gems/autoproj-1.6.1/bin/autoproj:53

in /home/users/leopold.palomo/robotica/orocos/orocos-toolchain/autoproj/.gems/gems/autoproj-1.6.1/bin/autoproj:23:in
`report'

in /home/users/leopold.palomo/robotica/orocos/orocos-toolchain/autoproj/.gems/gems/autobuild-1.5.22/lib/autobuild/reporting.rb:78:in
`report'

in /home/users/leopold.palomo/robotica/orocos/orocos-toolchain/autoproj/.gems/gems/autoproj-1.6.1/bin/autoproj:22:in
`report'

in /home/users/leopold.palomo/robotica/orocos/orocos-toolchain/autoproj/.gems/gems/autoproj-1.6.1/bin/autoproj:51

in /home/users/leopold.palomo/robotica/orocos/orocos-toolchain/autoproj/.gems/bin/autoproj:19:in
`load'

in /home/users/leopold.palomo/robotica/orocos/orocos-toolchain/autoproj/.gems/bin/autoproj:19
ERROR: failed to run autoproj bootstrap --verbose, dev, git,
git://gitorious.org/orocos-toolchain/autoproj.git, branch=master

Regards,

Leo

Testing needed: autoproj 1.6.2.rc9

On 11/03/2010 03:55 PM, Leopold Palomo-Avellaneda wrote:
> A Dimarts 02 Novembre 2010, Sylvain Joyeux va escriure:
>> First, changelog, then installation/upgrade instructions.
>>
>> Changelog:
>>
>> * overhauled osdeps fine-grained configuration. See
>> http://orocos.org/dfki-next/autoproj/osdeps.html
>> for more information
>> * fix too-aggressive caching of operating system characteristics,
>> which breaks on OS upgrades.
>> * on Debian-like systems, filter out packages that are already
>> installed
>> * on all systems, filter packages that have already been handled by
>> the osdeps
>> * add a -k option that continues operation even after errors. The sum
>> of all errors are properly presented at the end of the run.
>> * when boostrapping, check that the current directory is empty and
>> warn the user if it is not.
>> * the 'default' option can be used in osdeps to fall-back on version
>> and/or OS name. I.e.
>>
>> ubuntu:
>> 9.04: special_package
>> default: normal_package_for_all_other_versions_of_ubuntu
>>
>> * a few more minor bugfixes
>>
>> To install in an already bootstrapped installation:
>>
>> gem install --prerelease autoproj
>>
>> To bootstrap a new installation using 1.6.2.rc9
>>
>> 1. you MUST use the bootstrap script at
>> http://orocos.org/dfki-next/autoproj_bootstrap
>> 2. run it with the "dev" option
>> autoproj_bootstrap dev git
>> git://gitorious.org/orocos-toolchain/autoproj.git branch=master
> I have run:
>
> ./autoproj_bootstrap --verbose dev git
> git://gitorious.org/orocos-toolchain/autoproj.git branch=master
>
> and I got
>
> autodetecting the operating system
> Which prepackaged software (a.k.a. 'osdeps') should autoproj install
> automatically (all, ruby, os, none) ?
> The software packages that autoproj will have to build may require other
> prepackaged softwares (a.k.a. OS dependencies) to be installed (RubyGems
> packages, packages from your operating system/distribution, ...). Autoproj
> is able to install those automatically for you.
>
> Advanced users may want to control this behaviour. Additionally, the
> installation of some packages require administration rights, which you may
> not have. This option is meant to allow you to control autoproj's
> behaviour
> while handling OS dependencies.
>
> * if you say "all", it will install all packages automatically.
> This requires root access thru 'sudo'
> * if you say "ruby", only the Ruby packages will be installed.
> Installing these packages does not require root access.
> * if you say "os", only the OS-provided packages will be installed.
> Installing these packages requires root access.
> * if you say "none", autoproj will not do anything related to the
> OS dependencies.
>
> As any configuration value, the mode can be changed anytime by calling
> an autoproj operation with the --reconfigure option (e.g. autoproj update
> --reconfigure).
>
> Finally, OS dependencies can be installed by calling "autoproj osdeps"
> with the corresponding option (--all, --ruby, --os or --none). [all]
> autoproj: installing a proper Ruby environment (this can take a long time)
> autoproj: installing autoproj and its dependencies (this can take a long time)
> installing/updating RubyGems dependencies: autobuild, rdoc
> installing/updating RubyGems dependencies: autoproj
>
> version control dev is unknown to autoproj
>
> in /home/users/leopold.palomo/robotica/orocos/orocos-toolchain/autoproj/.gems/gems/autoproj-1.6.1/lib/autoproj/manifest.rb:89:in
> `initialize'
>
> in /home/users/leopold.palomo/robotica/orocos/orocos-toolchain/autoproj/.gems/gems/autoproj-1.6.1/lib/autoproj/manifest.rb:162:in
> `new'
>
> in /home/users/leopold.palomo/robotica/orocos/orocos-toolchain/autoproj/.gems/gems/autoproj-1.6.1/lib/autoproj/manifest.rb:162:in
> `normalize_vcs_definition'
>
> in /home/users/leopold.palomo/robotica/orocos/orocos-toolchain/autoproj/.gems/gems/autoproj-1.6.1/lib/autoproj/cmdline.rb:924:in
> `do_switch_config'
>
> in /home/users/leopold.palomo/robotica/orocos/orocos-toolchain/autoproj/.gems/gems/autoproj-1.6.1/lib/autoproj/cmdline.rb:1018:in
> `bootstrap'
>
> in /home/users/leopold.palomo/robotica/orocos/orocos-toolchain/autoproj/.gems/gems/autoproj-1.6.1/lib/autoproj/cmdline.rb:685:in
> `handle_mode'
>
> in /home/users/leopold.palomo/robotica/orocos/orocos-toolchain/autoproj/.gems/gems/autoproj-1.6.1/lib/autoproj/cmdline.rb:656:in
> `parse_arguments'
>
> in /home/users/leopold.palomo/robotica/orocos/orocos-toolchain/autoproj/.gems/gems/autoproj-1.6.1/lib/autoproj/cmdline.rb:655:in
> `catch'
>
> in /home/users/leopold.palomo/robotica/orocos/orocos-toolchain/autoproj/.gems/gems/autoproj-1.6.1/lib/autoproj/cmdline.rb:655:in
> `parse_arguments'
>
> in /home/users/leopold.palomo/robotica/orocos/orocos-toolchain/autoproj/.gems/gems/autoproj-1.6.1/bin/autoproj:53
>
> in /home/users/leopold.palomo/robotica/orocos/orocos-toolchain/autoproj/.gems/gems/autoproj-1.6.1/bin/autoproj:23:in
> `report'
>
> in /home/users/leopold.palomo/robotica/orocos/orocos-toolchain/autoproj/.gems/gems/autobuild-1.5.22/lib/autobuild/reporting.rb:78:in
> `report'
>
> in /home/users/leopold.palomo/robotica/orocos/orocos-toolchain/autoproj/.gems/gems/autoproj-1.6.1/bin/autoproj:22:in
> `report'
>
> in /home/users/leopold.palomo/robotica/orocos/orocos-toolchain/autoproj/.gems/gems/autoproj-1.6.1/bin/autoproj:51
>
> in /home/users/leopold.palomo/robotica/orocos/orocos-toolchain/autoproj/.gems/bin/autoproj:19:in
> `load'
>
> in /home/users/leopold.palomo/robotica/orocos/orocos-toolchain/autoproj/.gems/bin/autoproj:19
> ERROR: failed to run autoproj bootstrap --verbose, dev, git,
> git://gitorious.org/orocos-toolchain/autoproj.git, branch=master
"dev" MUST be the first argument

Thanks for testing.

Testing needed: autoproj 1.6.2.rc9

A Dimecres 03 Novembre 2010, Sylvain Joyeux va escriure:
> On 11/03/2010 03:55 PM, Leopold Palomo-Avellaneda wrote:
> > A Dimarts 02 Novembre 2010, Sylvain Joyeux va escriure:
> >> First, changelog, then installation/upgrade instructions.
......

> > git,
> > git://gitorious.org/orocos-toolchain/autoproj.git, branch=master
>
> "dev" MUST be the first argument

./autoproj_bootstrap dev --verbose git git://....

?

Testing needed: autoproj 1.6.2.rc9

On 11/03/2010 04:30 PM, Leopold Palomo-Avellaneda wrote:
> A Dimecres 03 Novembre 2010, Sylvain Joyeux va escriure:
>> On 11/03/2010 03:55 PM, Leopold Palomo-Avellaneda wrote:
>>> A Dimarts 02 Novembre 2010, Sylvain Joyeux va escriure:
>>>> First, changelog, then installation/upgrade instructions.
> ......
>
>>> git,
>>> git://gitorious.org/orocos-toolchain/autoproj.git, branch=master
>> "dev" MUST be the first argument
> ./autoproj_bootstrap dev --verbose git git://....
> ?
Yep. FYI, --verbose is not used for bootstrapping, only passed later on
to the "real" autoproj.

Sylvain

Testing needed: autoproj 1.6.2.rc9

A Dimecres 03 Novembre 2010, Sylvain Joyeux va escriure:
> On 11/03/2010 04:30 PM, Leopold Palomo-Avellaneda wrote:
> > A Dimecres 03 Novembre 2010, Sylvain Joyeux va escriure:
> >> On 11/03/2010 03:55 PM, Leopold Palomo-Avellaneda wrote:
> >>> A Dimarts 02 Novembre 2010, Sylvain Joyeux va escriure:
> >>>> First, changelog, then installation/upgrade instructions.
> >
> > ......
> >
> >>> git,
> >>> git://gitorious.org/orocos-toolchain/autoproj.git, branch=master
> >>
> >> "dev" MUST be the first argument
> >
> > ./autoproj_bootstrap dev --verbose git git://....
> > ?
>
> Yep. FYI, --verbose is not used for bootstrapping, only passed later on
> to the "real" autoproj.
>
> Sylvain

./autoproj_bootstrap dev --verbose git
git://gitorious.org/orocos-toolchain/autoproj.git branch=master
autodetecting the operating system
Which prepackaged software (a.k.a. 'osdeps') should autoproj install

[.....]

Finally, OS dependencies can be installed by calling "autoproj osdeps"
with the corresponding option (--all, --ruby, --os or --none). [all]
autoproj: installing a proper Ruby environment (this can take a long time)
autoproj: installing autoproj and its dependencies (this can take a long time)
looking for RubyGems updates
installing/updating RubyGems dependencies: autoproj
autodetecting the operating system
checking out autoproj main configuration
autoproj_config: running git clone -o autobuild
git://gitorious.org/orocos-toolchain/autoproj.git /home/users/leopold.palomo/robotica/orocos/orocos-toolchain/autoproj/autoproj
(output goes to install/log/autoproj_config-import.log)
autoproj_config: running git reset --hard autobuild/master
(output goes to install/log/autoproj_config-import.log)
Access method to gitorious (git, http or ssh)
Use 'ssh' only if you have a gitorious account and have commit rights
on the Orocos projects. Otherwise, we advise you to use 'git' [git]

expected an autoproj configuration
in /home/users/leopold.palomo/robotica/orocos/orocos-toolchain/autoproj/autoproj,
but /home/users/leopold.palomo/robotica/orocos/orocos-toolchain/autoproj/autoproj/manifest
does not exist
ERROR: failed to run autoproj bootstrap --verbose, git,
git://gitorious.org/orocos-toolchain/autoproj.git, branch=master