-
Notifications
You must be signed in to change notification settings - Fork 444
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
Regression: snapcraft started failing with craft_archives.repo.errors.AptGPGKeyInstallError #4224
Comments
Dropping the subkey (thereby diverging from gpg's default) works around the issue. This is how I'm now generating the key:
git-ubuntu MP: https://code.launchpad.net/~racb/git-ubuntu/+git/usd-importer/+merge/445060 |
I was able to work around this issue by reverting to snapcraft 9201 and deleting the base lxc container (base-instance-snapcraft-buildd-base-v00--a12c0d0071c13c372948 for me) |
We are also getting this as we add puppet bolt via the snapcraft version is 7.4.3, Rev 9362 |
from snapcraft.yaml:
.asc file contents:
|
Thanks. Does it work if you remove the local keyfile from the |
That does seem to work, yes. Certainly suggests the issue is around parsing the keyfile. I am slightly surprised it built because I did need to have the keyfile locally originally (~8 months ago), but maybe something has changed on the repository side... |
The root cause is understood - I explained it in canonical/craft-archives#83 |
My snaps currently deploy packages from an internal company server from snapcraft.yaml
from snap/keys/0264B26D.asc
|
Maybe the key only got uploaded to keyserver.ubuntu.com recently? Regardless, as @basak says the cause of the error is known and I was just trying to see if we can get workarounds for individual cases. We'll do a 7.4.4 hotfix to address this. |
The new version supports asset files that contain more than one key (for whatever reason). This is more in line with the behavior done by the previous implementation (via apt-key). Closes canonical#4224
The new version supports asset files that contain more than one key (for whatever reason). This is more in line with the behavior done by the previous implementation (via apt-key). Closes #4224
Hi everyone. I put up a fix that should address this specific issue (
@basak this only addresses the multiple-keys issue, and not the "needs sudo" issue. |
I get a new error now:
Full trace: https://paste.ubuntu.com/p/KWzBHvvNSn/ Full steps to reproduce:
I also verified that I got the previous failure as expected if I just use the default stable channel. |
It appears to work for me:
|
The new version supports asset files that contain more than one key (for whatever reason). This is more in line with the behavior done by the previous implementation (via apt-key). Closes #4224
It's failing for me when I try to build this snap: https://raw.githubusercontent.com/snapcore/snapd/cca5d8f1db88131d6de8e469fc0b6a10d1f9b3a1/tests/lib/snaps/store/test-snapd-layout-change-with-daemon/snapcraft_old.yaml It is a cut version of the steam snap, which also fails with the same error:
I tried also with edge version (7.4.3.post49+gitdbe76f21) but still fails. |
Tried to compile directly from "master", but also fails. |
Any news on when this fix will make it into a released snapcraft? |
Bug Description
On Friday git-ubuntu CI regressed. It uses the stable snapcraft snap.
It seems that something was switched that caused it to start failing with an error from inside craft-archives. See canonical/craft-archives#83 for details.
To Reproduce
In a Focal lxd container, running as the ubuntu user (eg.
lxc launch ubuntu:focal test-container && lxc shell test-container
and thenlogin -f ubuntu
):Environment
Snapcraft is in destructive mode inside a lxd container.
snapcraft.yaml
See https://git.launchpad.net/git-ubuntu/tree/snap/snapcraft.yaml although note that snap.sh modifies it slightly to work around LP: #1918968. See that script for details.
Relevant log output
Additional context
No response
The text was updated successfully, but these errors were encountered: