[01:04] <darrenwu> store is not working right now. Web https://myapps.developer.ubuntu.com, "snap install" and  "ubuntu-image" cannot work.
[02:26] <darrenwu> it's back now.
[07:50] <foxmask> bonjello
[07:59] <mup> PR snapcraft#902 opened: Snap revision prune <Created by seawaywen> <https://github.com/snapcore/snapcraft/pull/902>
[08:01] <dholbach> good morning
[08:27] <zyga> good morning
[09:20] <crazyoldworld> what is a desktop app for snappy
[09:20] <crazyoldworld> snapplets?
[09:20] <crazyoldworld> snapple
[09:20] <crazyoldworld> ok thanks
[09:29] <mup> Bug #1641150 changed: snap hooks are not run with environment similar to apps: PATH, LD_LIBRARY_PATH <Snapcraft:New> <Snappy:Invalid by zyga> <https://launchpad.net/bugs/1641150>
[09:38] <zyga> crazyoldworld: what do you mean?
[09:44] <seb128> zyga, if I had to guess I would say he's asking how to call an application distributed as a .snap
[09:44] <seb128> which is a "snap"  I guess
[11:34] <mup> PR snapd#2271 opened: snap: add support for classic confinement <Created by zyga> <https://github.com/snapcore/snapd/pull/2271>
[12:21] <davmor2> mwhudson: :(  still looping here on todays build
[12:27] <MikeB_> I'm having trouble installing and running a system service in Classic mode on a Ubuntu Core.  I've changed /usr/sbin/policy-rc.d to allow the service to start by returning 104.  But invoke-rc.d complains the service file doesn't exist.  I checked, and it does exist in /lib/systemd/system.  Any idea why I'm having problems?
[12:36] <mup> Bug #1641590 opened: snap --help outline text <Snappy:New> <https://launchpad.net/bugs/1641590>
[13:11] <mup> PR snapcraft#896 closed: indicators: work with Content-Encoding set <Created by sergiusens> <Merged by sergiusens> <https://github.com/snapcore/snapcraft/pull/896>
[13:23] <mup> PR snapcraft#903 opened: store: download without login <Created by sergiusens> <https://github.com/snapcore/snapcraft/pull/903>
[13:35] <zyga> dholbach: hey, do you remember that project that helped desktop snaps to run?
[13:35] <zyga> dholbach: stuff like setting up gdk and themes?
[13:38] <ssweeny> zyga: you mean https://github.com/ubuntu/snapcraft-desktop-helpers ?
[13:38] <sergiusens> didrocks davidcalle is there anything to do with LP: #1618021
[13:38] <sergiusens> ?
[13:38] <mup> Bug #1618021: tour: cannot re-install hello-world-service without devmode <tour> <Snapcraft:Triaged by davidc3> <https://launchpad.net/bugs/1618021>
[13:39] <zyga> ssweeny: yes, thank you!
[13:39] <ssweeny> np
[13:39] <dholbach> zyga, yes, that's the one :)
[13:40] <didrocks> sergiusens: I guess davidcalle needs to reupdate the text to include --dangerous now
[13:40] <davidcalle> didrocks: sergiusens: looking, but sounds likely, yes
[14:50] <jamespage> ok so I really must be missing something obvious about organize/filesets
[14:51] <jamespage> context is that there are a number of files in the release tarball that I'm snapping that are not installed by the python plugin
[14:51] <jamespage> https://github.com/openstack-snaps/snap-glance
[14:52] <jamespage> I basically need to push etc/*.conf|ini|json etc/glance/
[15:05] <sergiusens> jamespage until I get the scriptlets for parts in place you will need to grab the source twice and use `dump` in one of them
[15:05] <sergiusens> `organize` and `filesets` apply to the installed assets not the sources.
[15:05] <jamespage> sergiusens, ok glad I had not missed something
[15:06] <sergiusens> ogranize is like a dpkg-divert but both assets being valid
[15:06] <sergiusens> err, I mean, the diverted asset being valid
[15:07] <sergiusens> jamespage we have this same problem here https://github.com/snapcore/snapcraft/blob/master/demos/gopaste/snapcraft.yaml
[15:07] <Exquisitus> hello everyone!
[15:09] <Exquisitus> I have a question: my snapcraft maven plugin runs "mvn package" and pick up for the snap always the target/${app-name}.jar. Instead I want to wrap in the final snap a different jar executable
[15:10] <Exquisitus> that is created in the root directory
[15:13] <didrocks> sergiusens: any clue on the maven plugin? ^ (I never looked at it, only know about some hardcoded target paths). IIRC, you wanted some real world user experience
[15:19] <mup> Bug #1641631 opened: Raspberry Pi images do not support boot from USB <Snappy:New> <https://launchpad.net/bugs/1641631>
[15:25] <jamespage> sergiusens, ok I see got that working now
[15:25] <jamespage> https://github.com/openstack-snaps/snap-glance/blob/master/snapcraft.yaml
[15:26] <jamespage> sergiusens, one more question if I may - is there a nice easy way to extract something from the upstream release tarball/source to set as the version number?
[15:26] <jamespage> pbr is quite good at generating versions based on tags
[15:26] <jamespage> and I think that gets baked into the release and snapshot tarballs
[15:31] <jdstrand> roadmr (cc, nessita): fyi, https://myapps.developer.ubuntu.com/dev/click-apps/5779/rev/373/ gives a 504 when clicking 'approve'. going back to the page seems to indicate it worked (ie, it is approved)
[15:31] <jdstrand> roadmr (cc nessita): all of those should be approved, but there are only 4 left so I don't want to remove any more test cases
[15:32] <nessita> jdstrand, checking
[15:32] <jdstrand> roadmr: (for some wider context, see the plugs/slots thread I responded to today)
[15:32]  * roadmr bumps into nessita while checking :D
[15:32] <nessita> roadmr, I leave it to you, this sounds related to the approved interfaces/
[15:32] <nessita> ?
[15:32] <roadmr> jdstrand: btw, I see it has a nice payload; I'll deploy the stuff to auto-approve based on that this week
[15:33] <roadmr> nessita: does it? do we have an oops?
[15:33] <jdstrand> roadmr: ah great! :)
[15:33] <nessita> roadmr, well, the package that is failing is the one with specific interfaces efined
[15:33] <nessita> (is the first one I see)
[15:33] <roadmr> nessita: the payload passing shouldn't cause a timeout, I'd suspect it's more related to number of published packages. But let's see
[15:34] <nessita> roadmr, there are oopses for the soft timeout
[15:34] <jdstrand> nessita: my reference to plugs/slots was not meant to indicate a problem there (/me has no insight on that) only that things are going to manual review cause plugs/slots being given to review tools hasn't landed yet
[15:38] <roadmr> nessita: check the query count, https://oops.canonical.com/oops/?oopsid=OOPS-4c9cb191528bbc05f12c48a2abcaa764 we're running some queries over 300 times, this number matches the # of uploaded lxc snaps, so I suspect just some n+1 issue. Doesn't look related to the approved interfaces payload as IIRC we never iterate over all uploads for that
[15:39] <nessita> yeah
[15:41] <sergiusens> jamespage you can do it the other way around, $SNAPCRAFT_PROJECT_VERSION can be used in your `source` entry
[15:42] <jamespage> sergiusens, oh neat
[15:42] <jamespage> sergiusens, are there any conventions around use of numbers/codenames etc?
[15:44] <sergiusens> for versions? not really, mostly up to you
[15:44] <jamespage> great
[15:46] <nessita> roadmr, any verdict?
[15:47] <roadmr> nessita: there are 3 queries we run once for each upload of the snap, I need to track down where those come from and see if I can optimize them...
[15:48] <nessita> roadmr, reindexing that package does not work either
[15:49] <nessita> roadmr, so something broke regarding prefetching tables
[15:49] <roadmr> nessita: oh was that already using prefetching?
[15:49] <nessita> roadmr, yes, "a lot" :-)
[17:39] <SuperJonotron> installing snap with --force-dangerous on a new system but complaining that --force-dangerous is an unknown flag now
[17:40] <cwayne> try --dangerous
[17:40] <SuperJonotron> cwayne, tried that too, same result
[17:42] <SuperJonotron> i tired without either and no errors like I had before without that flat, maybe an update has relaxed something in the security  model for use of that flag?
[17:45] <ogra_> --dangerous is set by default if your snap also uses --devmode IIRC
[17:48] <SuperJonotron> yup, it does use devmode
[17:48] <SuperJonotron> i guess the added --dangerous was in an update since i had to use both before
[17:48] <SuperJonotron> not sure why it doesn't recognize the flag at all anymore though
[17:49] <ogra_> yeah, that was a bit of a mess, but fixed for the image release two weeks ago
[17:50] <roadmr> jdstrand: hello, the --plugs/--slots thing is now enabled in production in the store. Let me know if you have any questions about how it works or you find any bugs or problems
[17:50] <roadmr> jdstrand: (it's controlled via a waffle flag so it's easy to disable if it gives trouble)
[17:50] <jdstrand> roadmr: oh, that was quick. thanks! :)
[17:51] <roadmr> jdstrand: haha yes :) we were just pending a deployment, I tested everything late last week
[18:22] <mup> PR snapd#2246 closed: debian: add version 2.17 to changelog <Created by mvo5> <Merged by niemeyer> <https://github.com/snapcore/snapd/pull/2246>
[18:34] <jdstrand> roadmr: will you handle the lxd approvals or shall I (I don't want to remove the 504 test cases)
[18:40] <mup> PR snapd#2272 opened: debian: add 2.17.1 to changelog <Created by niemeyer> <https://github.com/snapcore/snapd/pull/2272>
[19:06] <mup> PR snapcraft#866 closed: Login with option to agree to terms of service and human friendly errors <Created by psivaa> <Merged by sergiusens> <https://github.com/snapcore/snapcraft/pull/866>
[19:13] <mwhudson> davmor2: :(
[19:13] <davmor2> mwhudson: see the email I sent out seems to only be on configured networks
[19:14] <mwhudson> davmor2: ugh looks like i didn't upload the fix to the ppa :)
[19:14] <mwhudson> s/:)/:(/
[19:15] <davmor2> mwhudson: that's not gonna help then ;) So look again tomorrow then right?
[19:16] <mwhudson> davmor2: yea
[19:16] <mwhudson> davmor2: well, assuming my fix is right :)
[19:38] <sea-gull_> hey #snappies! Do I understand correctly that anybody can now upload snappy packages without any kind of approval?
[19:40] <mcphail> sea-gull_: anyone can upload a snap, but not all snaps can be uploaded by anyone
[19:44] <Francesco_> Hi all
[19:45] <roadmr> jdstrand: I think the reason for the 504s is clear, I guess it's ok if you handle those approvals
[19:45] <Francesco_> sorry I am a noob can somebody please tell me what I have to enter to login to the ubuntu snappy store and install webdm
[19:46] <jdstrand> roadmr: ok, thanks
[19:49] <sea-gull_> mcphail: so who or how it's determined what can the given man upload?
[19:49] <Francesco_> exit
[19:49] <sea-gull_> for instance, I use latest git, and I would like to have it as a snap
[19:49] <sea-gull_> what should I do to get or make it?
[19:58] <sergiusens> sea-gull_ I wrote this on using snapcraft to get stuff onto the store if you want to check out http://blog.sergiusens.org/posts/Making-your-snaps-available-to-the-store-using-snapcraft/
[20:01] <sea-gull_> sergiusens: thanks, looks useful
[20:04] <sergiusens> sea-gull_ for more polished documentation, snapcraft.io is your go-to site ;-)
[20:08] <sea-gull_> yep, I've skimmed through it already
[20:31] <ahoneybun> bladernr`: heyo
[20:31] <bladernr`> ahoneybun, howdy
[20:31] <ahoneybun> let me open up the email on the desktop here and take a look
[20:32] <bladernr`> Oh sure... no rush, by the way, it's a pet project.
[20:33] <ahoneybun> it was for me as well
[20:34] <ahoneybun> bladernr`: this is my current yaml file for it: http://pastebin.ubuntu.com/23477247/
[20:34] <ahoneybun> I've recently restarted my effort to make it
[20:36] <ahoneybun> so desktop/gtk3 or anything is deprecated
[20:36] <ahoneybun> how do I write it?
[20:36] <ahoneybun> without the " / ?
[20:36] <mup> PR snapd#2267 closed: debian: add 2.17.1 to changelog <Created by mvo5> <Merged by niemeyer> <https://github.com/snapcore/snapd/pull/2267>
[20:36] <mup> PR snapd#2272 closed: debian: add 2.17.1 to changelog <Created by niemeyer> <Merged by niemeyer> <https://github.com/snapcore/snapd/pull/2272>
[20:38] <ahoneybun> I just changed the desktop/qt5 to desktop/gtk3
[21:16] <mhall119> Son_Goku: ping
[21:17] <mhall119> zyga: Son_Goku: If we get snapd and snap-confine in to the CentOS repo you were planning on, what versions of CentOS would that be available on?
[21:17] <Son_Goku> CentOS 7 only
[21:17] <mhall119> ok, is there any possibility of getting it in 6.6?
[21:45] <bladernr`> ahoneybun, so I've tried both by just staging the package from Ubuntu and your way, by pulling/compiling from source and both times I end up now with this
[21:45] <bladernr`> http://pastebin.ubuntu.com/23477531/
[21:46] <bladernr`> problem seems to be that the launcher (pithos) is still looking in /share, not $SNAP/share
[21:47] <bladernr`> the configure.in file in the source has config options to specify the datadir and rootdatadir, so I wonder if there's a way to pass config options to snapcraft to force it to look in /snap/pithos/current/
[21:47] <bladernr`> I don't understand how snapcraft prepends $SNAP in the environment though...
[21:48] <bladernr`> but I don't have time to work on it anymore today, maybe later tonight or tomorrow or later this week.
[21:51] <Son_Goku> mhall119, if it didn't require systemd, sure
[21:53] <mhall119> what does CentOS 6 use, sysv or upstart?
[21:59] <popey> mhall119: upstart surely?
[22:07] <SuperJonotron> was working through a --force-dangerous or --dangerous issue earlier today, I removed it and the snap can install...the first time only
[22:07] <SuperJonotron> every time after that the flag is required but rejected on the first install of a snap
[22:07] <SuperJonotron> is there better syntax than that to install a newer version?
[22:08] <mup> PR snapd#2273 opened: interfaces: add avahi-observe (LP: #1639967) <Created by jdstrand> <https://github.com/snapcore/snapd/pull/2273>
[22:10] <popey> SuperJonotron: can you paste the entire terminal output of you doing the install?
[22:11] <popey> SuperJonotron: also, what version of snapd package do you have, and what distro are you on?
[22:11] <zyga> mhall119: I doubt that but let's get it into fedora first
[22:11] <SuperJonotron> popey,  2.14.2~16.04+ppa215-1
[22:12] <zyga> mhall119: checking one thing
[22:13] <zyga> mhall119: I cannot say now, in any case it's a thing beyond the horizon today
[22:14] <popey> SuperJonotron: what version of ubuntu you on?
[22:14] <SuperJonotron> popeye, command "sudo snap install snap*.snap --devmode", error: error: cannot find signatures with metadata for snap "snapname.snap", adding the flag --force-dangerous works
[22:14] <SuperJonotron> but will fail if it's the first installation of the snap
[22:14] <SuperJonotron> popey, 16.04
[22:15] <popey> right, I'd expect you to have to add --dangerous (or --force-dangerous in older versions of snapd)
[22:15] <popey> 2.16 is the current version of snapd, so you probably need to "sudo apt dist-upgrade" your machine
[22:25] <SuperJonotron> popey, thanks, i might just right into an installer script to try both to handle older versions
[22:46] <mup> Bug #1641752 opened: request for snap interface that expose userspace device APIs <Snappy:New> <https://launchpad.net/bugs/1641752>
[23:40] <Trevinho> jdstrand: hey, thanks for the fix for libappindicator...
[23:43] <Trevinho> jdstrand: as for the setprocess policy, I've there's the process-control plug, but it has to be manually enabled... I guess UI will be there for handling such cases in the future... However, I was wondering wether it would be the case to make setpriorty to be allowed for snaps that want to control the child process with higher nice values...
[23:44] <Trevinho> for example there are some tools for doing video rendering that reduce the priority of the child process (typically mencoder or ffmpeg)... That is a policy that I don't think would need any particular privilege.
[23:52] <mup> Bug #1641758 opened: Allow to call setpriority on child processes when priority is lower than default <snapd-interface> <Snappy:New> <https://launchpad.net/bugs/1641758>
[23:58] <jdstrand> Trevinho: yes, that will be coming soon (setpriority with nice values of greater than 0)
[23:59] <jdstrand> Trevinho: hmm, but only on the current process. if for children, you are going to need process-control I think
[23:59] <Trevinho> jdstrand: cool, I've opened a bug... I didn't find anything about that, so...
[23:59] <Trevinho> jdstrand: mhmh, I see, but.. Why isn't that safe?
[23:59] <Trevinho> if it's all inside snap...
[23:59] <jdstrand> it would be safe