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

ci: llvm packages have unmet dependencies #4347

Closed
leongross opened this issue Jul 19, 2024 · 4 comments
Closed

ci: llvm packages have unmet dependencies #4347

leongross opened this issue Jul 19, 2024 · 4 comments

Comments

@leongross
Copy link
Contributor

leongross commented Jul 19, 2024

While the ci for my PR ran, I realized that the dependency setup for the size diff failed.

Reading package lists...
W: https://apt.llvm.org/jammy/dists/llvm-toolchain-jammy-18/InRelease: Key is stored in legacy trusted.gpg keyring (/etc/apt/trusted.gpg), see the DEPRECATION section in apt-key(8) for details.
Reading package lists...
Building dependency tree...
Reading state information...
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 libllvm18 : Breaks: llvm-18-dev (< 1:18.1.8-4) but 1:18.1.8~++20240717051017+3b5b5c1ec4a3-1~exp1~20240717171122.141 is to be installed
E: Unable to correct problems, you have held broken packages.
Error: Process completed with exit code 100.

I will have a look at that soon.

@leongross
Copy link
Contributor Author

leongross commented Jul 19, 2024

Update: There seems to be a general problem regarding the llvm packages provided via apt for ubuntu 22.04.

llvm/llvm-project#99453

@deadprogram deadprogram changed the title ci: packages have unmet dependecies ci: llvm packages have unmet dependencies Jul 19, 2024
@leongross leongross mentioned this issue Jul 19, 2024
@deadprogram
Copy link
Member

llvm/llvm-project#99502 despite being a duplicate actually has more info. Supposed to be fixed now, but rerunning the tinygo ci check still shows same error.

@leongross
Copy link
Contributor Author

Does the CI use the updated package index of llvm or is this maybe some caching issue?

dankegel added a commit to dankegel/tinygo that referenced this issue Jul 20, 2024
Attempt to sidestep packaging skew for the moment.

See tinygo-org#4347
and llvm/llvm-project#99502
dankegel added a commit to dankegel/tinygo that referenced this issue Jul 20, 2024
Attempt to sidestep packaging skew for the moment.

See tinygo-org#4347
and llvm/llvm-project#99502

This PR will probably be moot by the time it's reviewed :-)
deadprogram added a commit that referenced this issue Jul 20, 2024
deadprogram added a commit that referenced this issue Jul 20, 2024
@deadprogram
Copy link
Member

This has now been corrected by #4350 so now closing. Thank you for reporting @leongross

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

2 participants