-
Notifications
You must be signed in to change notification settings - Fork 416
xorg: switch to git-checkout #76621
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
xorg: switch to git-checkout #76621
Conversation
Taffer
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks like there are a couple of updates required too (probably just rebasing will pick those up).
Dunno if you want to clean up those duplicates now or in a separate PR.
Signed-off-by: Colin Watson <colin.watson@chainguard.dev>
b22b1eb to
f4b40e5
Compare
Those packages are apparently duplicates, but `libxkbfile-dev` is more appropriately named. See wolfi-dev#76621 (comment). Signed-off-by: Colin Watson <colin.watson@chainguard.dev>
🌐 Build Failed: Environment
Build Details
Root Cause Analysis 🔍The build system failed to establish SSH connectivity to the QEMU virtual machine used for package building. The VM started successfully and SSH server was running, but SSH handshake failed with EOF error, preventing the build environment from being accessible for the actual package compilation process. Was this comment helpful? Please use 👍 or 👎 reactions on this comment. |
Signed-off-by: Colin Watson <colin.watson@chainguard.dev>
44d148c to
155ffb7
Compare
|
re: package-version-check and staging-package-version-check And what's with these cloud platforms having low limits? Like "Sorry, we had to truncate this directory to 1,000 files. 3069 entries were omitted from the list." uh, GitHub, did you guys not learn how to stream results? Or maybe just dump them all, we're adults, we can handle our web page taking another 100ms to load. 🙄 |
Related: https://github.com/chainguard-dev/internal-dev/issues/24668