On Mon, Mar 27, 2017 at 9:13 PM, Dmitrii Shcherbakov <
dmitrii.shcherba...@canonical.com> wrote:
>
>
> TL;DR: Putting libvirt and QEMU into the same snap removes an ability
> to update them independently and only use new QEMU binaries after VM
> shutdown.
>
[...]
7 If a QEMU process is terminated
learly have a reduced subset of actions (e.g. no
interfaces) maybe one option would be to hide that reduced subset all
behind one subcommand like: "snap dbg [find|list|install|...]" ?
[1]: https://sourceware.org/gdb/onlinedocs/gdb/Separate-Debug-Files.html
--
Christian Ehrhardt
Softwa
missed the importance of this when it came around a
few days ago.
Since now there is also this insights post about it - it might be worth to
"ping" the thread once more.
See:
https://insights.ubuntu.com/2017/01/09/how-to-snap-introducing-classic-confinement/
--
Christian Ehrhardt
S
3
And just as in your case it is still in kind of a "Not urgent, but nice"
state.
If we realize that this is really a more common need, it might be worth to
chime in and bump priority for anybody affected.
--
Christian Ehrhardt
Software Engineer, Ubuntu Server
Canonical Ltd
--
Snapcraf
On Fri, Aug 12, 2016 at 1:35 PM, Mark Shuttleworth wrote:
> Interfaces should actually handle this case very well, as long as both
> sides of the file exchange are predictable. So I can imagine CUPS
> providing an interface to ingest PPDs and a PPD snap that consumes that
> interface making the P
as soon as squid_deb_proxy or others give you headache about upgrading
with format changes (your template now differs from the conf that the user
modified :-/) you can take a look at the discussion for
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1611638
--
Christian Ehrhardt
Software En
On Tue, Aug 9, 2016 at 7:37 PM, Kyle Fazzari
wrote:
>
>
> On 08/09/2016 12:18 AM, Christian Ehrhardt wrote:
>
>
> On Tue, Aug 9, 2016 at 7:38 AM, Simon Fels
> wrote:
>
> Thanks a lot Simon for the answers!
> A few clarifications requests inline below (mostly gettin
ppersB:
plugin: copy
files:
file.wrapper: B
--
Christian Ehrhardt
Software Engineer, Ubuntu Server
Canonical Ltd
--
Snapcraft mailing list
Snapcraft@lists.snapcraft.io
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/snapcraft
lue involved as on "snap building time"
the path of $SNAP_USER_DATA and such isn't fix IIRC (could change per setup
and in future).
Worth a feature request bug? I'll wait for the discussion first.
--
Christian Ehrhardt
Software Engineer, Ubuntu Server
Canonical Ltd
--
Snapcraft m
mplement in your snap and a user can
> call from the outside with a simple 'snap set
> snap.name.confkey=confvalue' or similar.
>
Thanks, as above I consider this WIP then - is there a bug I could
subscribe myself and link to from my code?
--
Christian Ehrhardt
Software Engineer,
ointers or - if not already defined
and documented - to kick off some discussion about it.
[1]: https://developer.ubuntu.com/en/snappy/guides/config/
--
Christian Ehrhardt
Software Engineer, Ubuntu Server
Canonical Ltd
--
Snapcraft mailing list
Snapcraft@lists.snapcraft.io
Modify settings o
[3]: http://snapcraft.io/docs/reference/interfaces
--
Christian Ehrhardt
Software Engineer, Ubuntu Server
Canonical Ltd
--
Snapcraft mailing list
Snapcraft@lists.snapcraft.io
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/snapcraft
12 matches
Mail list logo