Public bug reported:
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
** Affects: snapd (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1672747
Title:
configure hook missing reason it was invoked
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1672747/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
