trying to sign-build without keys leaves a -build file, empty
Bug #1629984 reported by
Leo Arias
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Snapcraft |
Fix Released
|
Medium
|
Celso Providelo | ||
Bug Description
I tried to sign-build, but I had not created the keys. This throws an error, but leaves behind a -build empty file. So after I created the keys I tried to sign again and it kept saying that "A signed build assertion for this snap already exists."
If the sign fails, no -build file should be created.
To reproduce:
$ rm *-build
$ rm -rf ~/.snap/gnupg
$ snapcraft sign-build *.snap
$ cat *-build
| Changed in snapcraft: | |
| status: | Triaged → In Progress |
| assignee: | nobody → Celso Providelo (cprov) |
Revision history for this message
| Sergio Schvezov (sergiusens) wrote | #1 |
| Changed in snapcraft: | |
| status: | In Progress → Fix Committed |
| milestone: | none → 2.20 |
| tags: | added: store |
| Changed in snapcraft: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
https:/