snapcraft.io documents persistent state incorrectly

Bug #1617399 reported by Roger Peppe
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Snapcraft
Invalid
Undecided
Unassigned
snapd
Confirmed
Undecided
Unassigned

Bug Description

[17:57:34] <rogpeppe> in snapcraft.io, it says:
[17:57:34] <rogpeppe> ~/snap/<name>/current/ ← $SNAP_USER_DATA that can be rolled back
[17:57:34] <rogpeppe> ~/snap/<name>/common/ ← $SNAP_USER_COMMON unversioned user-specific data
[17:57:38] <rogpeppe> is that still true?
[17:57:57] <rogpeppe> i don't see any "current" or "common" directories inside ~/snap/<name>
[17:58:08] <rogpeppe> just x[0-9] directories
[17:59:50] <elopio> rogpeppe: they are in /var/snap
[18:00:31] <elopio> rogpeppe: please file a bug about that.

Revision history for this message
Leo Arias (elopio) wrote :

I'm not sure if we just need to update the document in snapcraft.io, or the files from var should also be linked to home. Can somebody please triage this?

Changed in snapcraft:
status: New → Invalid
Changed in snappy:
status: New → Confirmed
Michael Vogt (mvo)
affects: snappy → snapd
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.