-
Notifications
You must be signed in to change notification settings - Fork 49
snap: Use core22 #293
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
base: main
Are you sure you want to change the base?
snap: Use core22 #293
Conversation
Now that the issue was worked around in the previous commit, commit 577ccb0 can be reverted.
wget is deprecated in favor of wget2 development. However, using that as a drop-in replacement for wget1 is a breaking change. So just switch to curl, which is more stable and more than sufficient in this context here.
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.
ACK 9182a28, built and installed locally on Ubuntu 24.04:
$ snapcraft
Pulling bitcoin-core :: Downloading package: libxcb-util1/snap/snapcraft/15369/lib/python3.12/site-packages/apt/package.py:810: Warning: W:Download is performed unsandboxed as root as file '/root/.cache/snapcraft/download/libxcb-util1_0.4.0-1build2_amd64.deb' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied)
acq.run()
Generated snap metadata
Created snap package bitcoin-core_29.0_amd64.snap
$ sudo snap install bitcoin-core_29.0_amd64.snap --dangerous
bitcoin-core 29.0 installed
The resulting binaries are runnable.
Just for reference, the warning is unrelated to the changes here and happens with core20 as well: https://cirrus-ci.com/task/5992906776903680?logs=snapcraft_build#L974:
|
While
core20
is still technically supported, it requires workarounds such as #284 to work around bugs like canonical/snapcraft#5316.Also, the kde-neon extension is only offered in an older version. kde-neon-6 isn't offered at all. Ref: #292
So just use
core22
.My understanding is that even
core24
can be used, without any visible or breaking change to end-users, but this is left for a follow-up for now.(Edit: The curl change isn't needed here, but should make future core updates easier)