Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Autoproj.manifest.main_package_set is available later than expected #360

Closed
moooeeeep opened this issue Dec 15, 2021 · 3 comments
Closed

Comments

@moooeeeep
Copy link
Contributor

We've stumbled accross another inconsistency between the behavior of the current release version (2.15) and current master.

Consider this buildconf: https://github.com/moooeeeep/buildconf_3

With the current release bootstrap Autoproj.manifest.main_package_set is available while the init.rb of the package set is run. With the dev bootstrap nil is returned in the package set. It is later available in the overrides.rb of the buildconf though.


The interesting part of the output:

Release version:

p1/init.rb: is good
buildconf/overrides: is good

Dev version:

p1/init.rb: is nil
buildconf/overrides: is good

Not sure if this is some internal API which is subject to change without notice. But one of our package sets appears to use it, which is now broken with the dev version.

@g-arjones
Copy link
Contributor

Duplicate of #354

@g-arjones g-arjones marked this as a duplicate of #354 Dec 15, 2021
@moooeeeep
Copy link
Contributor Author

Thanks for pointing me to that! I think we refer to the same problem.

@doudou
Copy link
Member

doudou commented Feb 24, 2022

On top of being a duplicate, is has been fixed by #369

@doudou doudou closed this as completed Feb 24, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants