configure hook missing reason it was invoked
Bug #1672747 reported by
Ondrej Kubik
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| snapd |
Triaged
|
Medium
|
Unassigned | ||
Bug Description
when configure hook is invoked, there are several reasons leading to it, just to mention:
- user calling snap set <key>=<value>
- installing snap first time
- updating snap
- rollback
Each of this situation requires potentially different way to be be handled. At the moment it's left down to snap configure implementation to determine this, based on some custom storing of version/revisions values and comparing them.
This is
a) fragile as changes in snapd break it (own experience)
b) tricky thanks to other snapd bugs (config entries not being wiped at snap remove)
c) each snap with configure hook needs to reimplement same workaround
Revision history for this message
| Zygmunt Krynicki (zyga) wrote | #1 |
Revision history for this message
| Oliver Grawert (ogra) wrote | #2 |
| affects: | snapd (Ubuntu) → snapd |
| Changed in snapd: | |
| importance: | Undecided → Medium |
| status: | New → Triaged |
Revision history for this message
| Paweł Stołowski (stolowski) wrote | #3 |
To post a comment you must log in.
This is a dupe of a bug reported by ogra.