-
Notifications
You must be signed in to change notification settings - Fork 22
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 versions fails if remote has no master branch #321
Comments
Hi @planthaber, This PR should have solved these problems.... I will check this weekend to see what I missed. Just to understand what happened:
Is this right? I am trying to understand so I can reproduce the error |
Yes exactly, it happend for planning/ompl (rock-core/rock-package_set): Steps to reproduce on a fresh rock-core bootstrap:
|
Hi @planthaber , I reproduced your error with the rock environment, I think that the key "*" to get all the packages in the planning namespace here is setting it to master due to here, and when you override it here you do not override the branch, so it stays on master, causing the problem to try finding the Just to confirm, can you send the output of yours Thanks! |
|
But then I don't get why the normal checkout works, even worked before rock-core/autobuild#96. The issue only comes with using Nevertheless, deleting the branch setting in the override solves this issue: |
I agree that this is strange, but they maybe moved to the main branch recently, I've just saw that they moved the badge to main recently. Also, when I did the checkout here it already rose an error.
I think that when you don't set to local, it checks if the commit you want exists on remote before it snapshots, see here and here.
Nice! |
@planthaber, Can we close this issue? |
I have the feeling that fixing this in the importer is better than the workaround from rock-core/rock-package_set#23. Just removing What do you think? |
I agree, It makes sense |
|
Yep, what I meant was: We do in |
Hi,
I tired to use autoproj versions to generate a list of compatible package versions after a successful compile, but in case of ompl this leads to an error (full message below).
Is this possibly related to rock-core/autobuild#96?
Ompl doesn't have a master branch, it is using "main" instead
The text was updated successfully, but these errors were encountered: