I don’t know if I missed something important, but this morning after an overnight refresh of the ‘snapcraft’ snap environment the command argument for --destructive-mode is not working on my Ubuntu LTS 20.04 build machine.
`ubuntu@ubuntu:~/Development/debug/ufw$ snapcraft --destructive-mode
Error: no such option: --destructive-mode
`
Any suggestions?
-Casey
ubuntu@ubuntu:~/Development/debug/ufw$ snap tasks 465
Status Spawn Ready Summary
…
…
Done yesterday at 10:03 EST yesterday at 10:03 EST Ensure prerequisites for “snapcraft” are available
Done yesterday at 10:03 EST yesterday at 10:04 EST Download snap “snapcraft” (5793) from channel “latest/stable”
Done yesterday at 10:03 EST yesterday at 10:04 EST Fetch and check assertions for snap “snapcraft” (5793)
Done yesterday at 10:03 EST yesterday at 10:04 EST Mount snap “snapcraft” (5793)
Done yesterday at 10:03 EST yesterday at 10:04 EST Run pre-refresh hook of “snapcraft” snap if present
Done yesterday at 10:03 EST yesterday at 10:04 EST Stop snap “snapcraft” services
Done yesterday at 10:03 EST yesterday at 10:04 EST Remove aliases for snap “snapcraft”
Done yesterday at 10:03 EST yesterday at 10:04 EST Make current revision for snap “snapcraft” unavailable
Done yesterday at 10:03 EST yesterday at 10:04 EST Copy snap “snapcraft” data
Done yesterday at 10:03 EST yesterday at 10:04 EST Setup snap “snapcraft” (5793) security profiles
Done yesterday at 10:03 EST yesterday at 10:04 EST Make snap “snapcraft” (5793) available to the system
Done yesterday at 10:03 EST yesterday at 10:04 EST Automatically connect eligible plugs and slots of snap “snapcraft”
Done yesterday at 10:03 EST yesterday at 10:04 EST Set automatic aliases for snap “snapcraft”
Done yesterday at 10:03 EST yesterday at 10:04 EST Setup snap “snapcraft” aliases
Done yesterday at 10:03 EST yesterday at 10:04 EST Run post-refresh hook of “snapcraft” snap if present
Done yesterday at 10:03 EST yesterday at 10:04 EST Start snap “snapcraft” (5793) services
Done yesterday at 10:03 EST yesterday at 10:04 EST Remove data for snap “snapcraft” (5737)
Done yesterday at 10:03 EST yesterday at 10:04 EST Remove snap “snapcraft” (5737) from the system
Done yesterday at 10:03 EST yesterday at 10:04 EST Clean up “snapcraft” (5793) install
Done yesterday at 10:03 EST yesterday at 10:04 EST Run configure hook of “snapcraft” snap if present
Done yesterday at 10:03 EST yesterday at 10:04 EST Run health check of “snapcraft” snap
Done yesterday at 10:03 EST yesterday at 10:14 EST Consider re-refresh of “gimp”, “intellij-idea-ultimate”, “snapcraft”
…
Consider re-refresh of “gimp”, “intellij-idea-ultimate”, “snapcraft”
2020-12-01T10:14:53-05:00 INFO No re-refreshes found.
What version of snapcraft?
$ snapcraft version
snapcraft, version 4.4.3
The only way I can reproduce this is if the snap/snapcraft.yaml has no base specified, which is expected, and has been this way for months. Are you perhaps using the deb of snapcraft (very old) instead of the snap?
alan@robot:~/Temp/snapcraft_test/nobase$ snapcraft --destructive-mode
Error: no such option: --destructive-mode
alan@robot:~/Temp/snapcraft_test/nobase$ grep ^base snap/snapcraft.yaml
alan@robot:~/Temp/snapcraft_test/nobase$
alan@robot:~/Temp/snapcraft_test/core$ snapcraft --destructive-mode
Pulling my-part
Building my-part
Staging my-part
Priming my-part
Snapping |
Snapped my-snap-name_0.1_amd64.snap
alan@robot:~/Temp/snapcraft_test/core$ grep ^base snap/snapcraft.yaml
base: core # the base snap is the execution environment for this snap
alan@robot:~/Temp/snapcraft_test/core18$ snapcraft --destructive-mode
Pulling my-part
Building my-part
Staging my-part
Priming my-part
Snapping |
Snapped my-snap-name_0.1_amd64.snap
alan@robot:~/Temp/snapcraft_test/core18$ grep ^base snap/snapcraft.yaml
base: core18 # the base snap is the execution environment for this snap
alan@robot:~/Temp/snapcraft_test/core18$
alan@robot:~/Temp/snapcraft_test/core20$ snapcraft --destructive-mode
Pulling my-part
Building my-part
Staging my-part
Priming my-part
Snapping |
Snapped my-snap-name_0.1_amd64.snap
alan@robot:~/Temp/snapcraft_test/core20$ grep ^base snap/snapcraft.yaml
base: core20 # the base snap is the execution environment for this snap
ubuntu@ubuntu:~/Development/debug/ufw$ snap info snapd
name: snapd
summary: Background service that manages and maintains installed snaps
publisher: Canonical✓
store-url: https://snapcraft.io/snapd
license: GPL-3.0
description: |
…
…
type: snapd
snap-id: PMrrV4ml8uWuEUDBT8dSGnKUYbevVhc4
tracking: latest/stable
refresh-date: yesterday at 04:33 EST
channels:
latest/stable: 2.48 2020-12-02 (10238) 32MB -
latest/candidate: 2.48 2020-11-23 (10238) 32MB -
latest/beta: 2.48 2020-11-19 (10238) 32MB -
latest/edge: 2.48+git474.gba4f22d 2020-12-02 (10437) 32MB -
installed: 2.48 (10238) 32MB snapd
ubuntu@ubuntu:~/Development/debug/ufw$ snapcraft version
snapcraft, version 4.4.3
Ok: So I think I have the same problem … the ufw project snap files do not include a base: stanza in the yaml file. I was able to specify a base: stanza it started to build.
That is weird, but it was working prior to last night’s refresh.
-Casey
Previous Revision: 9721
$ ls /var/snap/snapd/
10238 9721 common current
Traced it back to a github glitch … The wrong branch was getting pulled for ufw source…
-Casey