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

Ubuntu 2204 #2

Merged
merged 2 commits into from
Oct 21, 2022
Merged

Ubuntu 2204 #2

merged 2 commits into from
Oct 21, 2022

Conversation

aravindavk
Copy link
Member

No description provided.

Signed-off-by: Aravinda Vishwanathapura <[email protected]>
# TODO: Review the below list of dependencies
- name: Install the Build dependencies
run: |
sudo apt update -y

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If you add the line: "sudo apt install -y libunwind-dev"
between "sudo apt update -y" and "sudo apt install -y --no-install-recommends...." all would work.
Example and test run are here.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the help.

Copy link

@pieter3d pieter3d Dec 10, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I ran into this same issue, and this solved it for me as well (the libunwind-14 and libunwind-dev conflict). But I don't really understand why? Is that some issue with something that is depending on libunwind? And why would updating them in two different steps solve the problem? What prevents this from happening again? It's kind of awkward to have this explicit update in my CI without any real explanation.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @pieter3d!
Here is the explanation. It is just a related to dependencies bug. Nobody can prevent it.

Signed-off-by: Aravinda Vishwanathapura <[email protected]>
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

Successfully merging this pull request may close these issues.

3 participants