[05:51] <mborzecki> morning
[07:48] <kalikiana> good morning o/
[07:53] <mborzecki> any idea why cassandra is no longer listed in `snap find --section=database` ?
[07:59] <mborzecki> pstolowski: hey
[07:59] <pstolowski> morning!
[08:01] <mborzecki> pstolowski: what do you know about cassandra snap?
[08:01] <pstolowski> mborzecki, zero
[08:01] <mborzecki> linode:debian-9-64:tests/main/searching is failing because cassandra is no longer listed in the output of `snap find --section=database`
[08:03] <mborzecki> judging by the comments, it's amd64 only, and the test, if running on amd64, will try to look it up in the store
[08:07] <mborzecki> pstolowski: any ideas why it might be gone now?
[08:09] <pstolowski> mborzecki, oh, i see. i guess it doesn't really matter, we should just change the test to search something else
[08:09] <pstolowski> mborzecki, mongo33 looks like a good candidate
[08:10] <mborzecki> pstolowski: is it also amd64 only?
[08:13] <pstolowski> mborzecki, yes
[08:51] <mup> PR snapd#4400 opened: tests/main/searching: handle changes in featured snaps list <Created by bboozzoo> <https://github.com/snapcore/snapd/pull/4400>
[08:53] <mborzecki> pstolowski: can you take a look ^^
[08:53] <pstolowski> looking
[09:20] <Chipaca> morning peeps. How's things today?
[09:23] <pstolowski> Chipaca, hey! mind taking a look at https://github.com/snapcore/snapd/pull/4400, tat should unblock tests
[09:23] <mup> PR #4400: tests/main/searching: handle changes in featured snaps list <Created by bboozzoo> <https://github.com/snapcore/snapd/pull/4400>
[09:32] <kalikiana> d'oh was looking a while for a "missing" property, only to notice later self wasn't the right object
[09:32]  * kalikiana coffee break
[09:48] <zyga-ubuntu> pstolowski: good morning
[09:48] <pstolowski> hey zyga-ubuntu !
[09:48] <pedronis> Chipaca: hi, master is also red with overall timeout atm
[09:48] <zyga-ubuntu> how are you doing?
[09:48]  * zyga-ubuntu looks at the snowstorm outside
[09:48] <zyga-ubuntu> I'm not doing my usual outdoor stuff today
[09:48] <zyga-ubuntu> decided to hop in to see how you are all doing
[09:49] <pstolowski> zyga-ubuntu, i'm good, thanks! how are your holidays?
[09:49] <pedronis> Chipaca: so reducing to two jobs didn't help (much),   start to suspect some network ops that are slow most of the times,  but not always?
[09:50] <zyga-ubuntu> pstolowski: good :-) I feel much more at ease than before
[09:50] <Chipaca> pedronis: should i bump it back up then?
[09:50] <zyga-ubuntu> and catching up on loads of things I put off at home :)
[09:50] <Chipaca> zyga-ubuntu: dude, if you pop in, we're just going to tell you about things that are broken :-)
[09:50] <zyga-ubuntu> Chipaca: haha
[09:50] <zyga-ubuntu> Chipaca: what's broken? :)
[09:51] <Chipaca> zyga-ubuntu: JamieBennett
[09:51] <zyga-ubuntu> Chipaca: believe me, usually I'm outside by now but it's snowing so badly I'm not doing that now
[09:51] <Chipaca> zyga-ubuntu: we broke the boss
[09:51] <zyga-ubuntu> ??
[09:51] <pedronis> Chipaca: I don't know
[09:51] <zyga-ubuntu> is jamie allright?
[09:51] <koza> zyga-ubuntu, hey, snowing. cmon nice sun here
[09:51] <pedronis> Chipaca: we need to understand what is slow
[09:51] <Chipaca> zyga-ubuntu: all his snaps are stateless
[09:51] <zyga-ubuntu> koza: WAT, where are you?
[09:51] <Chipaca> zyga-ubuntu: bah
[09:52] <Chipaca> zyga-ubuntu: it looks like all his snaps can't talk to dbus
[09:52] <zyga-ubuntu> Chipaca: rm -rf ~/snap ?
[09:52] <JamieBennett> zyga-ubuntu: I'm fine but yesterday was a day of finding a tonne of bugs it seems
[09:52] <mborzecki> zyga-ubuntu: hey, too bored vacationing? :)
[09:52] <zyga-ubuntu> Chipaca: apparmor denials?
[09:52] <Chipaca> zyga-ubuntu: no obvious unexpected denials
[09:52] <zyga-ubuntu> mborzecki: hehe, just stuck at home for the day
[09:52] <zyga-ubuntu> Chipaca: any missing dbus rules?
[09:52] <koza> zyga-ubuntu, LDZ
[09:52] <zyga-ubuntu> (not apparmor, dbus)
[09:52] <Chipaca> zyga-ubuntu: even things like opening a url didn't work i think
[09:52] <JamieBennett> zyga-ubuntu: everywhere from individual snaps to firmware issues with fwupdmgr, to USB C/Thunderbolt bugs
[09:52] <Chipaca> (and things worked here)
[09:52] <zyga-ubuntu> mmmmm
[09:52] <JamieBennett> Chipaca: that was a bug with unity -> Gnome Shell
[09:52] <Chipaca> JamieBennett: did you get a priest in
[09:53] <zyga-ubuntu> JamieBennett: what happens when you run snap run --shell in hello-world and then run xdg-open http://example.org
[09:53] <JamieBennett> Chipaca: on upgrade the .desktop file for Chrome when it is pinned to the dock does not contain %u so no urls were working when passed in
[09:54] <Chipaca> JamieBennett: chrome, not chromium?
[09:54] <JamieBennett> zyga-ubuntu: the url thing was a Chrome issue
[09:54] <JamieBennett> Chipaca: Chrome, yes
[09:54]  * JamieBennett should switch to Chromium
[09:54] <mborzecki> or firefox :)
[09:55]  * zyga-ubuntu has one more AP to update and install at home 
[09:55] <Chipaca> JamieBennett: that's a really old bug: https://askubuntu.com/a/729555/711
[09:55] <JamieBennett> mborzecki: I'd love to but HO's dont work for me and all my passwords are in Chrome so it would take some time to migrate
[09:55] <zyga-ubuntu> and then the backup disks for everything at home
[09:56] <JamieBennett> Chipaca: good find, I was barking up the wrong tree thinking it was a snap issue and debugging that
[09:56]  * zyga-ubuntu hugs everyone for using snaps and finding issues we will fix for everyone 
[09:56] <Chipaca> JamieBennett: not so much a find as a memory
[09:56] <Chipaca> JamieBennett: :-)
[09:57] <JamieBennett> Chipaca: I now have the pleasure of tracking down this bug - https://pastebin.canonical.com/205517/
[09:58]  * Chipaca steps slowly away from the JamieBennett 
[09:58] <JamieBennett> lol
[09:58] <zyga-ubuntu> on the other hand
[09:58] <zyga-ubuntu> star wars was fun
[09:58] <zyga-ubuntu> go and see it
[09:59] <JamieBennett> zyga-ubuntu: Booked for Christmas Eve, looking forward to it.
[09:59] <zyga-ubuntu> I'll look around for non-dubbed version, maybe without those distracting subtitles next
[09:59] <JamieBennett> I hear Yoda's back, some presenter on UK TV let it slip by accident
[09:59] <zyga-ubuntu> JamieBennett: I have no comment on the matter
[10:00] <JamieBennett> Well, its all over the UK news sites so hard to miss :(
[10:00]  * JamieBennett stops reading the news
[10:02] <zyga-ubuntu> JamieBennett: in my only comment I will say that the movie is better than I was expecting
[10:02] <zyga-ubuntu> JamieBennett: not sure if that says my expectations were low
[10:03] <JamieBennett> zyga-ubuntu: was it better than the last one?
[10:03] <zyga-ubuntu> JamieBennett: yes
[10:03] <JamieBennett> nice
[10:03] <zyga-ubuntu> JamieBennett: I think it ranks higher than some of IV-VI episodes
[10:05] <mborzeck1> last one as in 'rouge one' or 'the force awakens' ?
[10:05] <zyga-ubuntu> mborzeck1: FA, R1 is somewhat outside
[10:06] <zyga-ubuntu> at least for my comment above
[10:09] <mup> PR snapcraft#1755 closed: tests: collect the autopkgtest results and save them in git  <Created by elopio> <Merged by sergiusens> <https://github.com/snapcore/snapcraft/pull/1755>
[11:19] <gsilvapt> hello all
[11:19] <gsilvapt> I'm trying to run the static tests and I'm getting an error: ./runtests.sh: line 58: codespell: command not found
[11:19] <gsilvapt> Any suggestions?
[11:20] <kalikiana> gsilvapt: you'll want to `sudo apt install codespell`
[11:21] <gsilvapt> thank you, kalikiana. I may have forgotten to install the dependencies required. I'll try again now
[11:25] <daniellimws> I think it should be pip instead of apt
[11:25] <daniellimws> or both should work
[11:25] <gsilvapt> daniellimws, yes, both work. I thought it was strange to have only apt working
[11:28] <cachio> pedronis, hey, is there any url to get the version of the core snap in edge, or beta?
[11:28] <Chipaca> so... why on earth is tests/main/interfacs-many taking 5 inutes?
[11:28] <cachio> pedronis, whithout using any header
[11:29] <Chipaca> cachio: you need to set some headers
[11:29] <Chipaca> cachio: why?
[11:30] <Chipaca> cachio: you need to at least set X-Ubuntu-Series
[11:30] <cachio> Chipaca, it is because I need to setup the trigger in jenkins and it just allow to add a url
[11:31] <cachio> Chipaca, is it possible to pass the series as part of the url?
[11:31] <Chipaca> cachio: i don't think so, no
[11:31] <Chipaca> cachio: but, give me a bit
[11:31] <mup> PR snapd#4401 opened: [WIP] snapstate/ifacestate: autoconnect tasks <Created by stolowski> <https://github.com/snapcore/snapd/pull/4401>
[11:31] <pedronis> no, all apis we have rely on headers
[11:32]  * pedronis lunch
[11:33]  * jamesh wishes the travis-ci logs weren't quite so verbose
[11:35] <Chipaca> cachio: do you need it for both edge and beta?
[11:36] <cachio> Chipaca, yes, but most important is edge
[11:41] <Chipaca> cachio: https://people.canonical.com/~john/core_edge.json
[11:42] <cachio> Chipaca, I dont have permiossions to see that
[11:42] <Chipaca> cachio: try again
[11:42] <cachio> great
[11:43] <cachio> Chipaca, where are yo creating this?
[11:43] <Chipaca> cachio: people.c.c
[11:43] <Chipaca> cachio: crontab :-)
[11:43] <Chipaca> cachio: how often should it check?
[11:44] <cachio> Chipaca, every 10 minutes
[11:45] <cachio> Chipaca, thanks, I'll add this to the jenkins jobs
[11:45] <Chipaca> cachio: any otoher data you need in that json?
[11:46] <cachio> not sure yet, but I think with that info we are ok
[11:47] <cachio> is it for amd64, right?
[11:47] <cachio> because I need for arm64 and armhf
[11:51] <cachio> Chipaca, I'll be back for the standup
[11:53] <cachio> Chipaca, I need these triggrers to run the edge validation on cm3 and dragonboard
[11:53] <Chipaca> cachio: i can easily change it to be per arch as well
[11:54] <Chipaca> cachio: different urls though; i'll tell you where when it's done
[11:54] <cachio> Chipaca, :)
[11:54] <cachio> Chipaca, great, thansks
[11:55] <cachio> Chipaca, I'll be back for daily
[11:55] <Chipaca> cachio: i'll probably be late for the daily
[11:55]  * cachio afk
[11:59] <Chipaca> cachio: https://people.canonical.com/~john/core/
[12:01] <anddam> Chipaca: I was trying to figure about Snappy and Ubuntu Core, I wasn't sure if it was a single project, two Canonical's projects working togheter with Core relying on Snappy, or a third party project that's just being used by Core
[12:01] <anddam> I got curious about "containerized" apps in a desktop system, so Ubuntu Core came out
[12:04] <mup> PR snapd#4397 closed: tests/main/lxd: temporarily switch to manual <Blocked> <Created by bboozzoo> <Closed by bboozzoo> <https://github.com/snapcore/snapd/pull/4397>
[12:05] <Chipaca> anddam: ubuntu core is a thing from before snappy
[12:05] <Chipaca> anddam: snappy ubuntu core is ubuntu core based on snappy
[12:05] <Chipaca> anddam: in snappy there is a special snap that is called 'core', jsut to keep people on their toes
[12:06] <Chipaca> (in seriousness, the snap called 'core' is or was when we started a lot like what used to be ubuntu core)
[12:06] <Chipaca> anddam: but note snaps aren't containerised as i understand that terminology; they're confined
[12:08] <Chipaca> mborzeck1: you mentioned a mvo script that analysed spread output, do you have that somewhere?
[12:08] <mborzeck1> Chipaca: https://gist.github.com/mvo5/06a206e991b0ae5a53606821dded4bdf
[12:09] <anddam> Chipaca: ah thanks for the info. What's the difference between being containerised and confined there?
[12:09] <Chipaca> mborzeck1: i was about to dig into interfaces-many's suspicious 5 minute test runs, but thught i should check all of them first
[12:09] <Chipaca> and, i need to run to the school -- will bbl
[12:10] <anddam> also does snappy aim to be a full system package manager, like can it be seen replacing apt on an ubuntu system at some point in future/
[12:10] <Chipaca> anddam: snaps get a restricted view of the actual system (possibly with a different filesystem)
[12:10] <anddam> s,/$,?
[12:10]  * Chipaca -> afk
[12:10] <anddam> k
[12:15]  * pstolowski lunch
[12:34] <mup> Bug #1738197 opened: Daemons do not have an /run/user/* dir created <Snappy:New> <https://launchpad.net/bugs/1738197>
[12:43] <ackk> hi, I'm getting this error when trying to install a snap with "try": http://paste.ubuntu.com/26182870/ am I doing something wrong?
[13:02] <mborzeck1> pstolowski: standup
[13:02] <pstolowski> mborzeck1, coming
[13:02] <mborzeck1> cachio: standup
[13:03] <Chipaca> ackk: that's strange, let me test something locally
[13:03] <ackk> Chipaca, I think I found the issue, it seems I can't install the snap anymore in an LXD unless it's privileged
[13:04] <jdstrand> Chipaca: fyi, I helped him with opening urls, it was a local issue. it's sorted
[13:04] <ackk> (because of a systemd issue)
[13:04] <Chipaca> ackk: :-(
[13:05] <jdstrand> Chipaca: ah, I see you know that already :)
[13:06]  * jdstrand goes back to reading backscroll and commenting on things that no longer need discussion
[13:06]  * Chipaca hugs jdstrand 
[13:09] <jdstrand> Chipaca: the syscall denial in https://pastebin.canonical.com/205517/ is for listen. that is not in the dbus interface (interesting)
[13:09] <jdstrand> JamieBennett: hey, would you mind trying something?
[13:09]  * jdstrand hugs Chipaca 
[13:11] <jdstrand> oh, the new one better than force awakens? wow. /me tries to temper expectations
[13:12] <jdstrand> (I like force awakens a lot)
[13:12] <niemeyer> Hello!
[13:12] <jdstrand> hey niemeyer :)
[13:21]  * kalikiana going to lunch in ~10
[13:21] <kalikiana> niemeyer: o/ what's up
[13:24] <kalikiana> niemeyer: actually, would you have time for a quick chat? can be later today. there's something I wanted to ask you
[13:25] <kalikiana> (about architectures)
[13:26] <JamieBennett> hey jdstrand, sure
[13:26] <jdstrand> JamieBennett: hey. let me try to summarize the problem as I understand it
[13:27] <jdstrand> JamieBennett: the corebird snap isn't able to communicate on dbus and dies/stops working/doesn't work correctly
[13:27] <jdstrand> JamieBennett: is that accurate?
[13:28] <JamieBennett> jdstrand: Actually after more debugging I don't think it is a dbus issue
[13:28] <JamieBennett> I used dbus-monitor to see that the settings in Corebird were actually being set
[13:28] <jdstrand> JamieBennett: I saw a seccomp denial for 'listen'
[13:28] <niemeyer> kalikiana: Today and tomorrow will be somewhat tight as we're having a two-days meeting, but I will be around next week if we don't find a time slot
[13:28] <jdstrand> JamieBennett: so this would've caused some grief
[13:28] <JamieBennett> jdstrand: Corebird does not reflect the new settings in the UI
[13:29] <JamieBennett> jdstrand: happy to continue debugging though to see what the real issue is
[13:29] <jdstrand> JamieBennett: ok, the listen denial probably isn't the cause of that, but it is a bug in the dbus interface regardless
[13:29] <JamieBennett> ok
[13:30] <jdstrand> JamieBennett: but, if you wouldn't mind added this to /var/lib/snapd/seccomp/bpf/snap.corebird.corebird.src:
[13:30] <kalikiana> niemeyer: Alright. I'd say if there's time today that'd nice grand, but it's not an emergency so we can do it next week
[13:30] <jdstrand> listen
[13:30] <jdstrand> accept
[13:30] <jdstrand> accept4
[13:30] <jdstrand> JamieBennett: then running /snap/core/current/usr/lib/snapd/snap-seccomp compile /var/lib/snapd/seccomp/bpf/snap.corebird.corebird.src /var/lib/snapd/seccomp/bpf/snap.corebird.corebird.bin
[13:31] <jdstrand> JamieBennett: and then trying again, that would be great
[13:31] <JamieBennett> jdstrand: OK
[13:31] <mborzecki> i'm off to the 'christmas thing' at my son's kidergarten, bbl
[13:31] <jdstrand> I'm already preparing a PR for this regardless if it fixes your config issue
[13:32] <jdstrand> mborzecki: have fun!
[13:32]  * kalikiana going for lunch now
[13:37] <cachio> Chipaca, do you have the files for armhf and arm64?
[13:37] <Chipaca> cachio: https://people.canonical.com/~john/core/
[13:37] <niemeyer> cachio: I got the time wrong.. I need to head over to the meeting now, but will investigate this issue over the day and ping you when I have something
[13:38] <cachio> Chipaca, thanks a lot
[13:45] <cachio> niemeyer, sure, thanks
[13:46] <cachio> niemeyer, this is a good example https://travis-ci.org/snapcore/snapd/builds/316056668
[13:53] <Chipaca> so, interfaces-many legitimately takes 5 minuntes, because it does a 65 connects at an average of just over 4 seconds per connect
[13:53] <Chipaca> why does a connect take 4 seconds?
[13:57] <Chipaca> python3 -c $'import yaml;y=yaml.load(open("task.yaml"));\nfor i in ("execute","prepare","restore"):\n if i in y: open(i+".sh", "w").write(y[i])'
[13:57] <Chipaca> oops
[14:07] <sergiusens> elopio kalikiana can you enlighten me on why these cleanbuild/container builds fail https://travis-ci.org/snapcore/snapcraft/jobs/316397431
[14:37] <cachio> Chipaca, could you please dhance the version in the file https://people.canonical.com/~john/core/arm64_edge.json
[14:37] <cachio> I need to test if the trigger is workping properly
[14:39] <kalikiana> re
[14:42] <kalikiana> sergiusens: Looking
[14:43] <sergiusens> kalikiana if you find the reason, fix it up in a follow up PR to that one; I've skipped and logged a bug for that for now
[14:43] <sergiusens> running the actual tests is more important the having things green running against the wrong things
[14:51] <cachio> Chipaca, there?
[15:19] <mup> Issue snapcraft#1767 closed: stage-packages does not respect architectures <Created by sergiusens> <Closed by sergiusens> <https://github.com/snapcore/snapcraft/issue/1767>
[15:19] <mup> PR snapcraft#1788 closed: repo: error for packages with broken dependencies <Created by kalikiana> <Merged by sergiusens> <https://github.com/snapcore/snapcraft/pull/1788>
[15:22] <mup> PR snapcraft#1447 closed: add support for the "contact" field in snapcraft <Created by mvo5> <Closed by sergiusens> <https://github.com/snapcore/snapcraft/pull/1447>
[15:22] <mup> PR snapcraft#1579 closed: Make it possible to use the cmake ninja generator <Created by aleixpol> <Closed by sergiusens> <https://github.com/snapcore/snapcraft/pull/1579>
[15:25] <mup> PR snapcraft#1726 closed: schema: sources should not have defaults <Created by sergiusens> <Closed by sergiusens> <https://github.com/snapcore/snapcraft/pull/1726>
[15:36] <mup> Bug #1738222 opened: FAIL: main_test.go:769: snapSeccompSuite.TestCompatArchWorks <Snappy:New> <https://launchpad.net/bugs/1738222>
[15:47] <mup> PR snapd#4400 closed: tests/main/searching: handle changes in featured snaps list <Created by bboozzoo> <Merged by stolowski> <https://github.com/snapcore/snapd/pull/4400>
[15:52] <mborzecki> yay, at least one fire is put out
[15:53] <mborzecki> guys, if you have PRs open and they fail in tests/main/searching, then you pull the changes from master
[15:59] <mup> PR snapcraft#1807 opened: tests: run test_cleanbuild in LXD on Travis <Created by kalikiana> <https://github.com/snapcore/snapcraft/pull/1807>
[15:59] <Chipaca> cachio: sorry was afk. can i still help?
[15:59] <Chipaca> (was at physio)
[15:59] <cachio> Chipaca, it is ok, I already validated the triggers
[16:00] <Chipaca> cachio: ok
[16:00] <Chipaca> cachio: now, what was the thing about images?
[16:00] <Chipaca> cachio: I can put .png files on p.c.c, but I don't think that's what you meant :-p
[16:04] <cachio> Chipaca, seems to be working well
[16:04] <cachio> Chipaca, tomorrow I'll check it again to see if the whole thing is working
[16:04] <cachio> Chipaca, hehe, no it is ok
[16:04] <cachio> Chipaca, I need to build the image that I use for cm3 on beta validation
[16:04] <cachio> so, when there is a new core snap in beta (armhf) I need to generate a new image to test the cm3
[16:04] <cachio> Chipaca, but, first I prefer to make the edge validation work properly and then go to beta
[16:04] <Chipaca> cachio: ok, fair enough
[16:05] <Chipaca> cachio: I don't know if p.c.c has any sort of a SLA though; if this is going to block work if it goes down, we should look into moving it somwehre more solid (my main aim was to unblock you today)
[16:05] <cachio> Chipaca, ok, in that case I can setup a service on prodstack
[16:06] <cachio> Chipaca, it was the original idea
[16:06] <Chipaca> cachio: right, that's a better solution long term
[16:06] <cachio> Chipaca, agree
[16:07] <cachio> Chipaca, thanks for the json files :)
[16:07] <Chipaca> cachio: i can share the super high tech software that's behind them if you want :-p
[16:07] <cachio> Chipaca, hehehe, yes please
[16:08] <cachio> I am imaging the for
[16:08] <Chipaca> cachio: https://people.canonical.com/~john/core/get-core
[16:08] <kalikiana> kyrofa: would you have time for a chat in a bit? about garmmar stuff
[16:09] <cachio> Chipaca, awesome
[16:15] <kalikiana> kyrofa: elopio: sergiusens  Also heads-up I'll be off tomorrow and back on Monday
[16:20] <mup> PR snapcraft#1803 closed: ci: correctly run from snap <Created by sergiusens> <Merged by sergiusens> <https://github.com/snapcore/snapcraft/pull/1803>
[16:22] <kyrofa> kalikiana, sure, let me know
[16:32] <kalikiana> kyrofa: in say 5 minutes? just got out of another meeting and getting a coffee
[16:33] <hurricanehrndz> Who helps pack the fedora rpm, I'm trying to update suse and I'm just trying to understand the differences and fix some of the issues
[16:35] <kyrofa> hurricanehrndz, that's Son_Goku
[16:35] <kyrofa> kalikiana, sure
[16:35] <hurricanehrndz> oh yeah that's right
[16:35] <Son_Goku> hurricanehrndz: hi
[16:36] <Son_Goku> what's up?
[16:36] <hurricanehrndz> Son_Goku: I'm just trying to understand some of the linker flags used in the spec file for fedora
[16:37] <hurricanehrndz> Son_Goku: I have suse build working, but I'm not ending up with static binaries for snap-exec and snap-update-ns, which I understand is required for base snaps
[16:37] <Son_Goku> yeah
[16:37] <Son_Goku> it's a tricky mess
[16:37] <hurricanehrndz> Son_Goku: Yup, I gather that much
[16:37] <Son_Goku> I had been trying to do the suse one myself, but the golang toolchain is screwy :(
[16:38] <hurricanehrndz> Son_Goku: Well, I'm almost there https://build.opensuse.org/package/show/home:hurricanehernandez:branches:system:snappy/snapd
[16:38] <hurricanehrndz> Son_Goku: I'm just updating it.
[16:39] <hurricanehrndz> Son_Goku: the go macros are especially troublesome and I see how you handle it on fedora, but I'm confused about the linker flags you use in your gobuild macro
[16:42] <hurricanehrndz> Could you please walk me through them, specifically the '-B' flag, which I thought was for static and dynamic linking but the spec file uses a random hex or is the hex the builduuid
[16:42] <Son_Goku> sure,
[16:42] <kalikiana> kyrofa: I'm in the weekly now
[16:45] <Son_Goku> hurricanehrndz, also, `gpg2` is not correct
[16:46] <hurricanehrndz> Son_Goku: Thanks. I started with the spec that was on github within snapcore, go figure
[16:46] <hurricanehrndz> Son_Goku: ah.. I see you are going through my spec
[16:46] <Son_Goku> it has to be gpg1
[16:47] <Son_Goku> unfortunately, upstream snapd has not fixed their stuff to use gpg2 instead of gpg1
[16:48] <Son_Goku> I don't know why you're pulling in the 32-bit libs, though
[16:48] <Son_Goku> apparmor needs to be disabled on %suse_version < 1500
[16:49] <Son_Goku> hurricanehrndz: I guess you are going to only use vendored tarball?
[16:50] <kyrofa> kalikiana, sorry, hopping in now
[16:50] <Son_Goku> hurricanehrndz: also... bundling appears to still be outright banned in openSUSE: https://en.opensuse.org/openSUSE:Packaging_guidelines#Bundling_of_multiple_projects
[16:50] <hurricanehrndz> Son_Goku: Son_Goku: yes
[16:51] <kalikiana> No worries, I used the time to update some notes from today
[16:51] <kalikiana> Tedious but useful :-P
[16:53] <hurricanehrndz> Son_Goku: Hmm Yeah, I will see about unbundling later, I'm using zyga's work as a staring point
[16:56] <Son_Goku> hurricanehrndz: I'd suggest starting from my packaging and start from scratch
[16:56] <Son_Goku> I've made some effort to make the spec relatively portable
[16:57] <Son_Goku> the main thing that'll need to change is dropping the mandatory requires for snapd-selinux on snapd, since openSUSE supports either SELinux or AppArmor
[16:58] <hurricanehrndz> Son_Goku: Okay, I'm guess this is yours: https://github.com/snapcore/snapd/blob/master/packaging/fedora/snapd.spec
[16:58] <Son_Goku> https://src.fedoraproject.org/rpms/snapd/blob/master/f/snapd.spec
[16:58] <Son_Goku> but yes
[16:58] <Son_Goku> the canonical source tree is always in src.fedoraproject.org
[16:58] <Son_Goku> I don't release from snapcore/snapd
[16:59] <hurricanehrndz> Son_Goku:Okay I will start there
[16:59] <hurricanehrndz> Can you explain to me the ldflags on line 52
[17:00] <Son_Goku> sure
[17:00] <Son_Goku> in Fedora, we put a great deal of effort to make Go generate useful debug symbols
[17:00] <Son_Goku> the ldflags there enable that
[17:01] <Son_Goku> iirc, SUSE doesn't quite care as much about making useful debuginfo as Fedora does
[17:01] <hurricanehrndz> Cool, what's '-B' flag do?
[17:02] <hurricanehrndz> I tried reading the linker's man page but could find info on the hex following the flag
[17:03] <Son_Goku> it's a weird go thing
[17:04] <Son_Goku> it basically forces a build-id to be injected into the binaries
[17:04] <Son_Goku> because rpm uses that for debuginfo splitting and packaging
[17:05] <hurricanehrndz> Son_Goku: Thought so... had a feeling but couldn't find documentation
[17:05] <hurricanehrndz> should have looked up go linker
[17:05] <hurricanehrndz> ha ha
[17:05] <Son_Goku> https://fedoraproject.org/wiki/PackagingDrafts/Go#Debuginfo
[17:05] <jdstrand> Chipaca: fyi, I'm looking into the corebird issue from JamieBennett. we may hand off to the desktop team if I can't reproduce
[17:06] <hurricanehrndz> Son_Goku: Thank you, love find documentation...
[17:06] <jdstrand> Chipaca: it seems unrelated to snapd
[17:06] <hurricanehrndz> Son_Goku: Awesome, you've been a great help, thanks everything you have done so far
[17:06] <Son_Goku> np
[17:06] <jdstrand> Chipaca: not 100% sure yet since I can't reproduce, but it doesn't look like it
[17:07] <hurricanehrndz> Son_Goku: One more question, the vendor json specifies the exact versions of the supporting golibraries
[17:07] <Son_Goku> I ignore them
[17:07] <Son_Goku> aside from a few, they're mostly irrelevant
[17:08] <Son_Goku> the latest stuff that matches those library references work
[17:08] <hurricanehrndz> Son_Goku: Cool
[17:08] <Chipaca> jdstrand: ack
[17:08] <Chipaca> jdstrand: thank you!
[17:15] <kalikiana> sergiusens: FYI I couldn't find a way to reproduce the failing cleanbuild test locally, so I pushed snapcraft##1807  to expose the failure in Travis (which eats the errors by the looks of it) and will investigate this more on Monday - unless elopio beats me to figuring it out
[17:15] <mup> PR #1807: interfaces/builtin: allow /dev/vhci on bluetooth-control <Created by cwayne18> <Merged by niemeyer> <https://github.com/snapcore/snapd/pull/1807>
[17:16]  * kalikiana hugs mup very affectionately
[17:16] <kalikiana> ^^ snapcraft#1807
[17:16] <mup> PR snapcraft#1807: tests: run test_cleanbuild in LXD on Travis <Created by kalikiana> <https://github.com/snapcore/snapcraft/pull/1807>
[17:17]  * kalikiana wrapping up for today/ this week
[17:21] <elopio> snappy-m-o: let me introduce you to daniellimws.
[17:21] <snappy-m-o> Command ":" / ": let" not found.
[17:22] <elopio> no manners...
[17:22] <daniellimws> haha
[17:27]  * kalikiana hugs snappy-m-o 
[17:33] <flexiondotorg> kyrofa: Is SNAPCRAFT_SETUP_CORE still necessary for building classic snaps inside docker containers?
[17:33] <kyrofa> flexiondotorg, if snapd can't run, it's necessary
[17:33] <flexiondotorg> Thanks
[17:34] <kyrofa> flexiondotorg, without some jiggery, docker falls into that category
[17:34] <kyrofa> Sure thing!
[17:39] <kalikiana> flexiondotorg: kyrofa it's becoming automatic as of snapcraft#1801 which will be in the next release
[17:39] <mup> PR snapcraft#1801: lifecycle: detect docker to auto setup core <Created by sergiusens> <Merged by sergiusens> <https://github.com/snapcore/snapcraft/pull/1801>
[18:04]  * Chipaca EODish
[18:50] <brunosfer> Hi guys, does anyone know how can I replicate the GET requests to the snapcraft API ? e.g. sudo snap info <snap name>
[18:50] <brunosfer> Is there any public API documentation?
[18:52] <diddledan> flexiondotorg: can I pm a sec?
[19:02] <Pharaoh_Atem> hurricanehrndz: everything going well with suse packaging of snapd?
[19:03] <hurricanehrndz> Pharaoh_Atem: Well I just started tackling, I got all the info I need.. just time is required...
[19:03] <Pharaoh_Atem> cool
[19:05] <hurricanehrndz> Pharaoh_Atem: are you on suse?
[19:11] <Pharaoh_Atem> hurricanehrndz: I'm on Fedora, openSUSE, and Mageia :)
[19:13] <hurricanehrndz> Pharaoh_Atem: Cool, I'll send you a msg once it's ready for testing
[19:24] <diddledan> flexiondotorg: tis ok, I got ahold of popey
[19:32] <mborzecki> brunosfer: try running snapd with SNAPD_DEBUG=1
[19:33] <mborzecki> brunosfer: example curl based on what's in the logs: https://paste.ubuntu.com/26184762/
[19:42] <brunosfer> mborzecki: I stopped the service snapd, but now I can't find the path to the snapd binary file...
[22:47] <mup> Bug #1738295 opened: snap auto-refresh re-installs removed snaps <Snappy:New> <https://launchpad.net/bugs/1738295>