| 2016-10-28 06:08:23 |
Marcus Tomlinson |
bug |
|
|
added bug |
| 2016-11-30 17:03:50 |
Marcus Tomlinson |
description |
Clients such as the snappy store scope / app, and libsnapd-glib/qt need a mechanism through which to receive snap state change signals from snapd.
During the Devices Sprint it was decided that it would be sufficient enough for ALL events to broadcasted to ALL subscribers. It'd then be left up to the receiving end to ignore those events it wasn't concerned with.
E.g. An event would simply say something along the lines of: “snap X changed from state A to state B” |
Clients such as the snappy store scope / app, and libsnapd-glib/qt need a mechanism through which to receive snap state change signals from snapd (such as install progress, snap installed / uninstalled, etc.).
During the Devices Sprint it was decided that it would be sufficient enough for ALL events to broadcasted to ALL subscribers. It'd then be left up to the receiving end to ignore those events it wasn't concerned with.
E.g. An event would simply say something along the lines of: “snap X changed from state A to state B” |
|
| 2016-11-30 17:04:49 |
Marcus Tomlinson |
summary |
Dig up events logic from commit history |
Need a mechanism through which to receive snap changes events |
|
| 2016-11-30 17:10:14 |
Marcus Tomlinson |
snapd (Ubuntu): importance |
Undecided |
High |
|
| 2016-11-30 17:35:32 |
Alexandre Abreu |
bug |
|
|
added subscriber Alexandre Abreu |
| 2016-11-30 19:23:46 |
Pat McGowan |
bug task added |
|
canonical-devices-system-image |
|
| 2016-11-30 19:24:03 |
Pat McGowan |
canonical-devices-system-image: importance |
Undecided |
High |
|
| 2016-11-30 19:24:03 |
Pat McGowan |
canonical-devices-system-image: status |
New |
Confirmed |
|
| 2016-11-30 19:24:03 |
Pat McGowan |
canonical-devices-system-image: milestone |
|
p2 |
|
| 2016-11-30 19:24:03 |
Pat McGowan |
canonical-devices-system-image: assignee |
|
Pat McGowan (pat-mcgowan) |
|
| 2016-12-01 04:14:11 |
Marcus Tomlinson |
description |
Clients such as the snappy store scope / app, and libsnapd-glib/qt need a mechanism through which to receive snap state change signals from snapd (such as install progress, snap installed / uninstalled, etc.).
During the Devices Sprint it was decided that it would be sufficient enough for ALL events to broadcasted to ALL subscribers. It'd then be left up to the receiving end to ignore those events it wasn't concerned with.
E.g. An event would simply say something along the lines of: “snap X changed from state A to state B” |
Clients such as the snappy store scope / app, and libsnapd-glib/qt need a mechanism through which to receive snap state change signals from snapd (such as install progress, snap installed / uninstalled, etc.).
During the Devices Sprint it was decided that it would be sufficient enough for ALL events to be broadcasted to ALL subscribers. It'd then be left up to the receiving end to ignore those events it wasn't concerned with.
E.g. An event would simply say something along the lines of: “snap X changed from state A to state B” |
|
| 2016-12-04 09:10:13 |
Launchpad Janitor |
snapd (Ubuntu): status |
New |
Confirmed |
|
| 2017-01-11 20:32:53 |
Pat McGowan |
canonical-devices-system-image: assignee |
Pat McGowan (pat-mcgowan) |
Alejandro J. Cura (alecu) |
|
| 2020-06-22 08:55:42 |
Samuele Pedroni |
snapd (Ubuntu): importance |
High |
Medium |
|
