[Rock-dev] autoproj_bootstrap

[Sylvain Joyeux]

Nope. Definitely an autoproj v2 bug.

I'm going to fix it properly... in the meantime, I'm guessing that
your autoproj/overrides.yml has an empty (nil) overrides: entry like
this:

```
overrides:
```

just commenting that one out should do the trick.

Sylvain

On Mon, May 22, 2017 at 9:45 AM, Moritz Schilling
<moritz.schilling at dfki.de> wrote:
> Hi Sylvain,
>
> it is a bootstrap with an old buildconf.git, so i guess the configuration has changed ?
> After using it with "--debug" I got:
> "no implicit conversion of nil into Array
> /home/assert/.autoproj/gems/ruby/2.1.0/gems/autoproj-2.0.3/lib/autoproj/local_package_set.rb:62:in `+': no implicit conversion of nil into Array (TypeError)
>         from /home/assert/.autoproj/gems/ruby/2.1.0/gems/autoproj-2.0.3/lib/autoproj/local_package_set.rb:62:in `load_overrides'
>         from /home/assert/.autoproj/gems/ruby/2.1.0/gems/autoproj-2.0.3/lib/autoproj/package_set.rb:467:in `parse_source_definition'
>         from /home/assert/.autoproj/gems/ruby/2.1.0/gems/autoproj-2.0.3/lib/autoproj/local_package_set.rb:44:in `load_description_file'
>         from /home/assert/.autoproj/gems/ruby/2.1.0/gems/autoproj-2.0.3/lib/autoproj/ops/configuration.rb:437:in `update_configuration'
>         from /home/assert/.autoproj/gems/ruby/2.1.0/gems/autoproj-2.0.3/lib/autoproj/ops/configuration.rb:381:in `load_package_sets'
>         from /home/assert/.autoproj/gems/ruby/2.1.0/gems/autoproj-2.0.3/lib/autoproj/workspace.rb:467:in `load_package_sets'
>         from /home/assert/.autoproj/gems/ruby/2.1.0/gems/autoproj-2.0.3/lib/autoproj/cli/update.rb:75:in `run'
>         from /home/assert/.autoproj/gems/ruby/2.1.0/gems/autoproj-2.0.3/lib/autoproj/cli/main.rb:42:in `block in run_autoproj_cli'
>         from /home/assert/.autoproj/gems/ruby/2.1.0/gems/autoproj-2.0.3/lib/autoproj/reporter.rb:64:in `block in report'
>         from /home/assert/.autoproj/gems/ruby/2.1.0/gems/autobuild-1.10.1/lib/autobuild/reporting.rb:284:in `report'
>         from /home/assert/.autoproj/gems/ruby/2.1.0/gems/autoproj-2.0.3/lib/autoproj/reporter.rb:63:in `report'
>         from /home/assert/.autoproj/gems/ruby/2.1.0/gems/autoproj-2.0.3/lib/autoproj/cli/main.rb:33:in `run_autoproj_cli'
>         from /home/assert/.autoproj/gems/ruby/2.1.0/gems/autoproj-2.0.3/lib/autoproj/cli/main.rb:130:in `update'
>         from /home/assert/.autoproj/gems/ruby/2.1.0/gems/thor-0.19.4/lib/thor/command.rb:27:in `run'
>         from /home/assert/.autoproj/gems/ruby/2.1.0/gems/thor-0.19.4/lib/thor/invocation.rb:126:in `invoke_command'
>         from /home/assert/.autoproj/gems/ruby/2.1.0/gems/thor-0.19.4/lib/thor.rb:369:in `dispatch'
>         from /home/assert/.autoproj/gems/ruby/2.1.0/gems/thor-0.19.4/lib/thor/base.rb:444:in `start'
>         from /home/assert/.autoproj/gems/ruby/2.1.0/gems/autoproj-2.0.3/bin/aup:5:in `<top (required)>'
>         from /home/assert/work/test/.autoproj/bin/aup:15:in `load'
>         from /home/assert/work/test/.autoproj/bin/aup:15:in `<main>'"
> Are there any guidelines to transition to autoproj v2?
>
> BR,
>
> Moritz
>
>> Sylvain Joyeux <bir.sylvain at gmail.com> hat am 22. Mai 2017 um 13:53 geschrieben:
>>
>>
>> It doesn't seem to happen in a clean VM + clean bootstrap (I'm at the
>> initial osdep install stage)
>>
>> Is this a clean bootstrap, or an upgraded v1 bootstrap ?
>>
>> Could you re-run with --debug ? It will output a full backtrace.
>>
>> Sylvain
>>
>> On Mon, May 22, 2017 at 8:42 AM, Moritz Schilling
>> <moritz.schilling at dfki.de> wrote:
>> > Hello Sylvain,
>> >
>> > i have tried ruby2.1.5 as well as ruby2.3.0.
>> > But both produced the same error.
>> >
>> > BR,
>> >
>> > Moritz
>> >
>> >> Sylvain Joyeux <bir.sylvain at gmail.com> hat am 22. Mai 2017 um 13:21 geschrieben:
>> >>
>> >>
>> >> On Mon, May 22, 2017 at 5:42 AM, Moritz Schilling
>> >> <moritz.schilling at dfki.de> wrote:
>> >> > Hello there,
>> >> >
>> >> > it seems, that the autoproj_bootstrap script - even the stable one - has changed to autoproj v2, correct? Unfortunately, I am not able to bootstrap with this (debian, jessie).
>> >> Correct.
>> >>
>> >> > When "autoproj update" or any other command is invoked it fails in the end with something like this (here: autoproj update)
>> >> I'm checking that out ... Just to be sure, what's your ruby version ?
>> >>
>> >> Sylvain