[01:52] <ogra_> dasjoe, the tarballs are fragments used to build the actual snappy setup, no you cant just unpack and use them ... what you can do is use the snap packages from there together with the ubuntu-devce-flash from http://people.canonical.com/~mvo/all-snaps/ to create an image
[03:14] <techraf> hello, on my playground Ubuntu Core machine I had Transmission running in docker container with its interface bound to port 9091
[03:14] <techraf> I forgot about it and installed `snappy install transmission.matiasb` Transmission
[03:15] <techraf> it created its directory in /writable, I deactivated it made changes to settings, activated it again
[03:16] <techraf> by default it also runs on port 9091
[03:17] <techraf> later when I was trying to locate downloads it turned out that I actually used already running dockerized Transmission
[03:17] <techraf> why Transmission snap did not visually report any error that the port 9091 was already used?
[03:18] <techraf> if it reported somewhere, where shall I look?
[03:19] <techraf> (and is it "overall" snappy issue, or was it responsibility of that particular snap?)
[03:31] <techraf> (running 15.04)
=== tbr_ is now known as tbr
[10:43] <netphreak> Hi, guys!
[10:45] <netphreak> Anyone know how are os updates to Snappy Ubuntu handled? - automatically installed, or do these require manual user intervention?
[16:49] <kyrofa_> netphreak, you still around?
=== JanC_ is now known as JanC
[17:55] <dasjoe> ogra_: sorry if this wasn't clear, I do not intend to use snappy but just the "old" Ubuntu Core
[19:36] <netphreak> Hi, guys!
[19:36] <netphreak> Anyone know how are os updates to Snappy Ubuntu handled? - automatically installed, or do these require manual user intervention?
[19:58] <ogra_> dasjoe, then you dont ever want to use the -preinstalled bits ... they are all "snappified"
[20:58] <dasjoe> ogra_: right, thanks :)