[02:35] <sergiusens> jdstrand: I think he won it when we had the term husks in the snapd code base ;-)
[02:42] <mup> PR snapcraft#1272 closed: tests: initial setup for the snapcraft snap tests with spread <Created by elopio> <Merged by sergiusens> <https://github.com/snapcore/snapcraft/pull/1272>
[02:45] <mup> PR snapcraft#1279 closed: misc: rename the snap dir variable to prime dir <Created by elopio> <Merged by sergiusens> <https://github.com/snapcore/snapcraft/pull/1279>
[04:19] <Trevinho> jdstrand: you can now go back to use normal snapcraft-preload as fix for you issue has been merged upstream
[05:30] <mup> PR snapcraft#1238 closed: beta <Created by snappy-m-o> <Merged by elopio> <https://github.com/snapcore/snapcraft/pull/1238>
[07:03] <pedronis> mvo: hi, I got a +1 from Gustavo for snapd#3220, maybe you can finish the review you were doing? some points I addressed in snapd#3245
[07:03] <mup> PR snapd#3220: many: implement snap prefer <snap>  (aliases v2) <Created by pedronis> <https://github.com/snapcore/snapd/pull/3220>
[07:03] <mup> PR snapd#3245: many: aliases v2 cleanups <Created by pedronis> <https://github.com/snapcore/snapd/pull/3245>
[07:11] <mvo> pedronis: thanks, will do
[07:24] <pedronis> mvo: any reason not to merge #3244, I don't see anything controversial in there
[07:27] <mvo> pedronis: I tihnk its fine to merge, gustavo asked for those changes so he might want to review but afaict its all addressed in this pr
[07:38] <pedronis> mvo: no, now that I look at those commetns, there's a couple of things missing
[07:42] <beruic> Hi there. Has anyone experimented with making a build server for snaps?
[07:45] <zyga> beruic: yes
[07:45] <zyga> beruic: build.snapcraft.io
[07:45] <zyga> beruic: :-)
[07:45] <zyga> beruic: using snapcraft itself it is not that hard
[07:48] <beruic> @zyga Awesome. I'm considering trying to distribute my companys Django project on Core using snaps.
[07:48] <nothal> beruic: No such command!
[07:49] <beruic> zyga Awesome. I'm considering trying to distribute my companys Django project on Core using snaps.
[07:49] <beruic> Sorry for double posting
[07:50] <beruic> Does anyone know of a Freenode client for Ubuntu? Preferably one that comes as a snap package ;)
[07:50] <pedronis> mvo: there's just a couple minor things there now that I looked more carefully
[07:51] <zyga> beruic: I don't know of any, I'd love to see polari IRC from gnome but that may require some more work on gnome/gui side; irssi should be easy to snap
[07:54] <pedronis> zyga: I think there's a script to update the board, but gustavo needs to run it
[07:54] <pedronis> it's semi-automated, not fully afaiu
[07:56] <zyga> pedronis: aha, good to know
[07:59] <pedronis> mvo: seems there's a few things for 2.25 that we didn't get to do (https://forum.snapcraft.io/t/next-snapd-2-25/197), right? I suppose we didn't consider there was Easter
[08:02] <beruic> I'm having trouble figuring out the following about build.snapcraft.io: 1. I'm pretty sure it only connects to GitHub (we use Bitbucket :( ) 2. Is it possible to publish snaps that are only internally available, or does build.snapcraft.io always publish for public access?
[08:07] <zyga> beruic: I think it's meant for public snaps, you can build stuff yourself with snapcraft (from bitbucket) and as long as you don't push it to any channel you should be OK
[08:07] <zyga> beruic: you can get more answers by asking on forum.snapcraft.io
[08:08] <beruic> zyga: Thank you :)
[08:25] <zyga> mvo: I see more sleep tweaks on https://github.com/snapcore/snapd/pull/3242
[08:25] <mup> PR snapd#3242: tests: tweak time for econnreset test a bit more <Created by mvo5> <https://github.com/snapcore/snapd/pull/3242>
[08:25] <zyga> mvo: is there a way to make that test reliable without that?
[08:26] <pedronis> tests and sleep, almost always tears
[08:35] <pedronis> mvo: I made a suggestion on #3220 let me know what you think there?
[08:37] <pedronis> mvo: what's the plan for 2.25?
[08:39] <Chipaca> error: cannot get data for "complexion": [0xc82016e300 0xc82016e480 0xc82016e600]
[08:39] <Chipaca> ^^^ WTF
[08:39] <mvo> zyga: maybe, I think it will need a muchbigger snap
[08:40] <zyga> Chipaca: hmm
[08:40] <mvo> zyga: the problem is that there is a bit of a race, when the print happens it has not connected yet, I could make another debug print when its connected. we want to only retry on rst
[08:40] <mvo> zyga: when rst happens in the middle not at the start
[08:40] <zyga> Chipaca: that's the snap you added in your tests, right?
[08:40] <Chipaca> zyga— it's a snap, yes
[08:40] <zyga> mvo: could we do something, anything, via a helper proxy that we control, to make the test easier to write
[08:41] <Chipaca> zyga— i did 'snap try complexion'
[08:41] <Chipaca> it printed that
[08:41] <zyga> Chipaca: what are those [] numbers?
[08:41] <Chipaca> but that was apparently a success message? because the snap was installed after that
[08:41] <Chipaca> zyga— I have absolutely no idea
[08:41] <Chipaca> zyga— that was the output of 'snap try'
[08:41] <mvo> pedronis: checking your suggestion now. the plan for 2.25 is to push it out once the aliases are ready. it looks like in the standup we can discuss what (if anything) else is a must for 2.25
[08:41] <mvo> pedronis: definitly want to release today
[08:41] <zyga> Chipaca: ./cmd/snap/cmd_snap_op.go
[08:42] <Chipaca> $ sudo snap try complexion/
[08:42] <Chipaca> error: cannot get data for "complexion": [0xc82016e300 0xc82016e480 0xc82016e600]
[08:42] <pedronis> mvo: ok, aliases should be definitely in soon, mostly waiting on your feedback there ;) ?
[08:42] <zyga> Chipaca: the list is %v of `snaps` which came out of cli.List()
[08:42] <zyga> Chipaca: looks like wonky String method
[08:42] <zyga> that doesn't take pointer receiver
[08:42] <mvo> zyga: sending RST is tricky, the best way I found was via the iptables, however something like trickle might help to ensure the download is not too quickly over. or just a huge snpa, maybe I just go with that
[08:43] <Chipaca> looks like snap.List returned three items despite being given a snap name
[08:43] <zyga> Chipaca: yep
[08:43] <Chipaca> wonky indeed D:
[08:43] <Chipaca> why
[08:43] <zyga> Chipaca: let's patch the string methodfirst
[08:43] <Chipaca> all i wanted to do was manual testing of complexion
[08:43] <mvo> pedronis: ha!  on it :)
[08:44] <zyga> http://paste.ubuntu.com/24465628/
[08:44] <zyga> Chipaca: try with this
[08:44] <Chipaca> so this is something that's broken on master
[08:44] <mup> PR snapd#3220 closed: many: implement snap prefer <snap>  (aliases v2) <Created by pedronis> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/3220>
[08:46] <Chipaca> zyga— it's a %v, I don't think String is called on it
[08:47] <pedronis> Chipaca: mmh
[08:47] <zyga> Chipaca: aha, that's also possible
[08:49] <Chipaca> ah, look at that, it would be called
[08:50] <zyga> ogra_: how can I watch your webinar?
[08:58] <fgimenez_> hi mvo, this is the test i mentioned for the new local assertions capabilities of prepare-image https://github.com/mvo5/snappy/pull/16 it passes locally on your branch, let me know if i should change anything about it
[08:58] <mup> PR mvo5/snappy#16: tests: add spread test for assertions in prepare-image's extra-snaps <Created by fgimenez> <https://github.com/mvo5/snappy/pull/16>
[08:58] <morphis> mvo: updated https://github.com/snapcore/snapd/pull/3244 for pedronis comments
[08:58] <mup> PR snapd#3244: many: fix review comments from PR #3177 <Created by morphis> <https://github.com/snapcore/snapd/pull/3244>
[09:02] <mvo> fgimenez_: nice work, thats some  magic in there :) I have a look
[09:02] <mvo> morphis: thanks, also special thanks to pedronis for double checking that one
[09:04] <pedronis> mvo: snapd#3245 is ready for review, it contains some of the follow ups I promised in previous reviews
[09:04] <mup> PR snapd#3245: many: aliases v2 cleanups <Created by pedronis> <https://github.com/snapcore/snapd/pull/3245>
[09:04] <pedronis> plus other cleanups
[09:06] <pedronis> Chipaca: maybe you could give it a look as well? ^ (it's smallish, repetitive)
[09:10] <morphis> Son_Goku: ping
[09:14] <zyga> gah, I was debugging something that kept failing because I forgot to merge mater
[09:14] <zyga> master
[09:15] <mvo> fgimenez_: could you please merge master and push again in the prepare-image-assert-test branch? there is some unrelated diff and I updated my branch but it looks GH is not updating the diff until you push something too
[09:16] <fgimenez_> mvo: sure on it
[09:16] <mvo> ta
[09:19] <mvo> morphis: static checks are failing in your x11 pr, should be a trivial fix .)
[09:19] <morphis> mvo: ok
[09:20] <morphis> mvo: fixed
[09:21] <mvo> zyga: I will pull in 3243, jamie was asking for a test, maybe we can get one in a followup?
[09:21] <zyga> mvo: yes, I'll do one in a follow-up
[09:21] <zyga> mvo: I was looking at that already but it will need some extra mocking
[09:21] <zyga> mvo: and this will make CE happy
[09:21] <mvo> 3238 needs a second review
[09:22] <mvo> Chipaca: maybe you -^ ? branch is very small
[09:22] <mup> PR snapd#3243 closed: cmd/snap-confine: don't use apparmor if it is disabled on boot <Created by zyga> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/3243>
[09:22] <pedronis> zyga: wasn't there a test we disabled about that?
[09:23] <zyga> pedronis: yes but the test depends on an unreleased kernel, CE has a kernel that they can use this on already
[09:23] <pedronis> ah, I see
[09:31] <fgimenez_> mvo: fixed, now it shows only the test files https://github.com/mvo5/snappy/pull/16
[09:31] <mup> PR mvo5/snappy#16: tests: add spread test for assertions in prepare-image's extra-snaps <Created by fgimenez> <https://github.com/mvo5/snappy/pull/16>
[09:38] <Son_Goku> morphis: pong
[09:38] <morphis> Son_Goku: you saw my patch recently for the rpm to enable unit tests for the vendorized build
[09:38] <Son_Goku> yes
[09:38] <Son_Goku> I wanted to ask you something
[09:39] <morphis> shoot :-)
[09:39] <Son_Goku> does the unit tests require internet access?
[09:39] <mvo> fgimenez_: thanks, reading now
[09:39] <Son_Goku> because if they do, then I'm not merging this
[09:39] <morphis> Son_Goku: they shouldn't as far as I know
[09:39] <zyga> Son_Goku: no, they don't
[09:39] <zyga> Son_Goku: regular unit tests
[09:39] <zyga> Son_Goku: spread requires internet access but that's not tested at package build time
[09:39] <Son_Goku> okay, then
[09:40] <Son_Goku> morphis, could you link me the patch again? I seem to have downloaded it on a computer that's not this one
[09:40] <morphis> Son_Goku: sure
[09:40] <ogra_> zyga, you got to ask thibautr__
[09:42] <mup> PR snapcraft#1219 closed: kernel plugin: learn how to assemble the ubuntu config using kconfigflavour <Created by piso77> <Closed by piso77> <https://github.com/snapcore/snapcraft/pull/1219>
[09:53] <Son_Goku> morphis, nvm, I found it
[09:54] <morphis> Son_Goku: ok, was finishing something else but would have pasted it afterwards
[09:54] <morphis> zyga: what do you think about https://github.com/morphis/snapd/commit/75888e9198aedda1a862b7db496733e308b38a49 ?
[09:55] <zyga> morphis: that won't work
[09:56] <zyga> morphis: /etc/ssl is a symlink
[09:56] <zyga> no way to bind mount over one
[09:56] <zyga> (sorry)
[09:56] <morphis> sure but we have the target in /usr/share too
[09:56] <morphis> zyga: you mean /etc/ssl is a symlink on suse?
[09:56] <zyga> yes
[09:56] <zyga> no cheap way out other than to stop sharing /etc
[09:57] <morphis> ok that makes thing more complicate
[09:57] <morphis> zyga: " What we will then see is a symlink from /etc/ssl./certs to /var/lib/ca-certificates/pem that is just broken (the symlink)."
[09:57] <morphis> if I read that correct /etc/ssl/certs is the symlink
[09:57] <morphis> not /etc/ssl
[09:58] <zyga> morphis: aha, hmm
[09:58] <zyga> morphis: maybe that will work then
[09:58] <morphis> zyga: let me verify that
[09:58] <zyga> morphis: I still don't like it but it looks like a smaller change
[09:58] <zyga> morphis: please do
[09:58] <morphis> zyga: it's a cheap fix for the meantime
[09:59] <morphis> instead of taking quite some time to rework the rest
[09:59] <Son_Goku> morphis, I don't have the patch you added to the spec, though
[09:59] <morphis> Son_Goku: ah
[10:02] <Son_Goku> morphis, which sort of makes this pointless :)
[10:03] <Chipaca> mvo— you're cutting the release, yes?
[10:04] <pedronis> mvo: landed #3245
[10:04] <mup> PR snapd#3245 closed: many: aliases v2 cleanups <Created by pedronis> <Merged by pedronis> <https://github.com/snapcore/snapd/pull/3245>
[10:07] <morphis> Son_Goku: you mean 0001-many-fix-test-cases-to-work-with-different-DistroLib.patch ?
[10:07] <Son_Goku> yes
[10:07] <morphis> that one is merged into 2.25
[10:07] <Son_Goku> I didn't even see that PR
[10:07] <morphis> sorry, is up for merge
[10:07] <morphis> Son_Goku: https://github.com/snapcore/snapd/pull/3222
[10:07] <mup> PR snapd#3222: many: fix test cases to work with different DistroLibExecDir <Created by morphis> <https://github.com/snapcore/snapd/pull/3222>
[10:08] <thibautr__> zyga here you go for the webinar...
[10:08] <thibautr__> https://www.brighttalk.com/webcast/6793/248379
[10:08] <morphis> Son_Goku: 2.26 is more likely
[10:09] <zyga> thibautr__: thanks!
[10:11] <morphis> zyga: ok, /etc/ssl isn't a symlink on suse
[10:11] <zyga> morphis: ha
[10:11] <zyga> morphis: ok, let's do this, add this to suse build
[10:11] <zyga> morphis: as a distro patch
[10:11] <zyga> morphis: I'd love to see it work
[10:12] <morphis> zyga: :-)
[10:12] <Son_Goku> this patch makes no sense
[10:13] <zyga> Son_Goku: why not?
[10:14] <Son_Goku> not the suse one, the PR
[10:14] <Son_Goku> I don't even know what you're changing in the suse one :)
[10:14] <zyga> ah, sorry
[10:15] <morphis> Son_Goku: ?
[10:15] <Son_Goku> morphis: I left a comment in the PR, but I'm confused because it looks like you're testing the wrong thing now
[10:15] <morphis> Son_Goku: no you don't
[10:16] <Son_Goku> so why is everything changing from distrolibexec to corelibexec?
[10:16] <morphis> Son_Goku: there are many reexec cases which were properly handleed
[10:16] <morphis> but those are never used on fedora/suse
[10:16] <morphis> so they were wrong for quite some time
[10:16] <morphis> and rexec never would have worked
[10:18] <Son_Goku> ah
[10:19] <morphis> zyga: didn't you say you merged https://build.opensuse.org/request/show/490989 ?
[10:20] <zyga> morphis: I thought I did
[10:20] <Son_Goku> wtf is rcsnapd?
[10:20] <morphis> Son_Goku: https://en.opensuse.org/openSUSE:Packaging_checks#suse-missing-rclink
[10:20] <morphis> it's not really of any use anymore but rpmlint complains about it ..
[10:21] <Son_Goku> that's a bug, actually
[10:21] <zyga> morphis: aha, did that again
[10:21] <morphis> Son_Goku: maybe
[10:21] <Son_Goku> because they just decided to get rid of that stuff a couple of weeks ago
[10:21] <morphis> Son_Goku: then we can drop this in the near future again
[10:21] <Son_Goku> (yes, I'm involved in openSUSE, too :) )
[10:21] <Son_Goku> the only distribution family I'm not all that involved in is Debian :)
[10:22] <Son_Goku> I even have a somewhat tenuous link to Yocto
[10:22] <morphis> Son_Goku: :-)
[10:23] <Son_Goku> the reasons for not getting involved in Debian/Ubuntu are sadly long and terrible
[10:23] <Son_Goku> I told mvo once, quite a while ago
[10:24] <Son_Goku> oh, and ximion knows too :P
[10:24] <Son_Goku> I guess if I get the time, I'll help Debian complete the transition to dracut
[10:24] <Son_Goku> I already told ximion I'd help him on it, at least :)
[10:28] <morphis> Son_Goku: any progress on the postrm script?
[10:29] <Son_Goku> it needs reworking, but I think I'm nearly there :)
[10:29] <morphis> great!
[10:35] <mvo> Chipaca: release> yes, very soon. was thinking right after the standup so that we can discuss as a group if there is anything missing that must go in but I think we are good
[10:37] <mup> PR snapd#3238 closed: cmd/snap-confine: re-enable re-assciate fix for CE <Created by zyga> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/3238>
[10:42] <mup> PR snapcraft#1285 opened: kernel plugin: learn how to assemble the ubuntu config using kconfigflavour <Created by piso77> <https://github.com/snapcore/snapcraft/pull/1285>
[10:45] <pstolowski> mvo, my branch failed on econnreset test yesterday - https://s3.amazonaws.com/archive.travis-ci.org/jobs/225939208/log.txt?X-Amz-Expires=29&X-Amz-Date=20170427T104419Z&X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAJRYRXRSVGNKPKO5A/20170427/us-east-1/s3/aws4_request&X-Amz-SignedHeaders=host&X-Amz-Signature=014a53a5f0d9f89ee092ab7db9df6258e5f7cc3fa15bd68841c80719c2148446 - did you land any fixes since? shall I just retry?
[10:48] <mvo> pstolowski: yeah, I'm working on making them more reliable
[10:48] <mvo> pstolowski: sorry for that, just retry for now
[10:48] <mvo> zyga: do you think you could look at 3232?
[10:49] <mvo> zyga: a (nice) suggestion from samuele in there
[10:49] <mvo> zyga: I think this can go in then
[10:49] <mvo> (assuming it gets a second review)
[10:50] <zyga> mvo: looking
[10:51] <zyga> mvo: the "applied"?
[10:51] <zyga> mvo: I'd rather not change that in this branch alone, it's much cleaner to change it in one patch across the whole tree (there are other places)
[10:52] <mvo> zyga: ok, do you want to do a followup? works for me
[10:52] <pstolowski> mvo, sure, np. thanks!
[10:52] <zyga> mvo: yes, when other things land
[10:52] <zyga> mvo: this is in 3 or 4 places (the wording)
[10:52] <Son_Goku> morphis: alright, so I'm trying this now... https://koji.fedoraproject.org/koji/taskinfo?taskID=19231693
[10:53] <morphis> Son_Goku: it's a vendorized build?
[10:53] <Son_Goku> nope
[10:53] <morphis> then it wont work
[10:54] <morphis> Son_Goku: I still need to file bugs for updates to a few golang-* packages and we need https://bugzilla.redhat.com/show_bug.cgi?id=1444819
[10:54] <morphis> so only the vendorized build works for now
[10:55] <Son_Goku> then I'll test that locally
[10:57] <morphis> Son_Goku: I will update https://bugzilla.redhat.com/show_bug.cgi?id=1444819 later today
[10:57] <Son_Goku> okay
[11:20] <pedronis> mvo: this fell through the cracks for 2.25 https://forum.snapcraft.io/t/gadget-snap-config-defaults-dont-work/409 I created the topic now, and marked upcoming (2.26)
[11:20] <pedronis> mvo: don't know what else we missed in 2.25
[11:24] <zyga> mvo: is 2.25 tagged now?
[11:26] <Son_Goku> zyga: it's not tagged yet
[11:26] <pedronis> zyga: he said after the standup
[11:26] <zyga> aha
[11:27] <zyga> I missed that , sorry
[11:36] <mup> PR snapcraft#1280 closed: Added support for 'branches' in Store responses (release, close, and status) <Created by facundobatista> <Merged by sergiusens> <https://github.com/snapcore/snapcraft/pull/1280>
[11:37] <facubatista> yay
[11:45] <Chipaca> raah rahh
[11:45] <ogra_> moo?
[11:45] <Chipaca> ogra_— bash is a bundle of sticks made entirely of poo
[11:45] <jdstrand> Trevinho: sorry I didn't get a chance to test that sooner
[11:45] <jdstrand> Trevinho: and thanks you for the fix! :)
[11:46] <Trevinho> jdstrand: no worries..
[11:46] <Chipaca> ooh, a jdstrand!
[11:46] <ogra_> Chipaca, fully agreed :)
[11:46] <jdstrand> hey Chipaca :)
[11:46] <Chipaca> jdstrand— in etelpmoc, change the ()s around the definition of comopt to {}s
[11:46] <Chipaca> compopt*
[11:46] <jdstrand> Chipaca: I couldn't stop thinking about bash completion after you left (sorry)
[11:48] <Chipaca> jdstrand— still debugging why it doesn't get it quite right, but that'll get the slashes and such
[11:48] <jdstrand> Chipaca: does that give the 'ls' behavior
[11:48] <jdstrand> ?
[11:48] <Chipaca> jdstrand— closer. it depends. yes? sorta.
[11:48] <jdstrand> heh
[11:48] <Chipaca> jdstrand— it trips up and returns nothing as soon as it's quoted or there is a space in there
[11:49] <Chipaca> jdstrand— and i'm tracing that and very puzzled by it
[11:49] <Chipaca> but, yeah, it wasn't setting compopt -o filenames, meaning you didn't get ls-like behaviour ever
[11:49] <Chipaca> because, subshell /o\
[11:49] <Chipaca> my bad there
[11:51] <jdstrand> interesting
[11:51] <zyga> Chipaca: does that mean the tab-completion feature is out of 2.25??
[11:52] <Chipaca> I'm torn
[11:52] <Chipaca> I think we should land it, and then iterate
[11:52] <Chipaca> but I'm open to other people saying otherwise
[11:52] <jdstrand> Chipaca: if we land it, please add '&' to the grep
[11:52] <Chipaca> jdstrand— will do
[11:53] <jdstrand> however, if we land it as is, I'm quite sure someone will file a bug
[11:53] <jdstrand> that's ok. we could pre-file it :)
[11:53] <jdstrand> and even reference it in the code
[11:54]  * zyga breaks for lunch :/
[12:01] <niemeyer> Mornings
[12:08] <jdstrand> niemeyer: good morning :)
[12:11] <jdstrand> stgraber: hey, I just noticed that my lxd snap is not upgrading. I'm at 2.5 (r241). have you seen this?
[12:18] <jdstrand> stgraber: fyi, https://forum.snapcraft.io/t/lxd-snap-not-refreshing-says-it-is-local-but-it-isnt/411
[12:19] <jdstrand> mvo: sorry to bother you. this seems like something potentially bad ^
[12:19] <mvo> pstolowski: 3242 is ready for a second review, should fix the econnreset tstuff
[12:19] <mvo> jdstrand: looking
[12:20] <pstolowski> mvo, thanks, approved
[12:20] <mvo> jdstrand: that looks alarming indeed - last refresh was month and month ago
[12:21] <mvo> jdstrand: I assume you installed this a long time ago? I suspect there is somehting missing in the state, would you mail the state file to me (privately) ? it may contain the macaroon so either edit it out or I can write something that just extracts the lxd information
[12:22] <jdstrand> mvo: I was one of the first users of the lxd snap, so, 'yes'
[12:22] <jdstrand> mvo: /var/lib/snapd/state.json ?
[12:23] <jdstrand> mvo: should I stop snapd first or anything?
[12:23] <mvo> jdstrand: yes, this one. should be fine
[12:24] <pedronis> mvo: jdstrand: that error can happen only if the state has no snapid for that snap
[12:25] <pedronis> we had some bugs around preserving side info on some ops, might be because of one of those
[12:25] <mvo> pedronis: yeah, I hope the state give some more clues
[12:26] <Chipaca> zyga— do i have to do anything to have ./run-checks --static not complain about things in configure?
[12:26] <zyga> Chipaca: try distclean in cmd but other than that, no :/
[12:26] <zyga> Chipaca: I'm working on a way to switch away from automake
[12:26] <zyga> Chipaca: sorry about that
[12:29] <jdstrand> mvo: sent
[12:31] <jdstrand> Chipaca: you might have to remove some stuff that distclean doesn't I don't know if that got cleaned up, but I have in my notes: cd cmd ; make clean ; make distclean ; rm -f aclocal.m4 config.sub config.guess depcomp configure snap-confine/snap-confine.apparmor snap-confine/Makefile snap-confine/Makefile.in snap-confine/tests/Makefile snap-confine/tests/Makefile.in ; rm -rf autom4te.cache
[12:32] <mvo> jdstrand, pedronis: look like side-info is totally busted for this particular revision :/ http://paste.ubuntu.com/24466403/
[12:32] <mvo> jdstrand: as a workaround you can snap rmeove lxd/snap install --candidate lxd
[12:32] <mvo> jdstrand: the interessting question of course is what happend
[12:33] <Chipaca> jdstrand— I was a lazy bag of lazy stuff and moved ahead by putting my static check before the spellcheck
[12:33] <Chipaca> jdstrand— pushed a branch full of comments, and a &
[12:33] <pedronis> mvo: yea, that seems the effect of disable/enable at some point I think
[12:33] <pedronis> for example
[12:33] <mvo> pedronis: aha, indeed - most likely that bug
[12:34] <jdstrand> mvo: I'm kinda worried to remove it cause I don't want to lose my container. it has my whole build environment
[12:35] <jdstrand> it is plausible I did enable/disable. I've done that before, but I don't know if I ever did on this snap. what if I disable/enable now?
[12:35] <pedronis> jdstrand: it won't fix it
[12:35] <pedronis> it lost the information
[12:36] <pedronis> jdstrand: what you can do is stop snapd, edit that bit of state to put back the snapid, restart snapd and run refresh
[12:38] <jdstrand> I'd much rather do that than remove/install
[12:38] <mvo> jdstrand: yeah, was about to suggest the same, copy the snap-id from the pastebin
[12:38] <mvo> jdstrand: with that you are hopefully back
[12:39] <mup> PR snapd#3242 closed: tests: tweak time for econnreset test a bit more <Created by mvo5> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/3242>
[12:41] <jdstrand> mvo: I'm looking at a wall of text and I have the paste in front of me. you are saying replace '{"name":"lxd","snap-id":"","revision":"241"}' with '{"name":"lxd","snap-id":"id from paste","revision":"241"}'?
[12:42] <mvo> jdstrand: correct
[12:42] <mvo> jdstrand: and make a backup of the state file first :)
[12:42] <mvo> jdstrand: (I guess you did by mailing it to me)
[12:49] <jdstrand> mvo: ok, that worked. thanks! I updated the forum for some of this, but you guys might want to add more detail
[12:49] <jdstrand> pedronis: thank you too :) ^
[12:49] <mvo> jdstrand: thank you and sorry for the trouble
[12:50] <mvo> jdstrand: I think we know which bug it caused, the issue is long fixed since but of course there is fallout :/
[12:51] <jdstrand> mvo: do you have a json linter/checker? it seems like this could be detected programmatically. I'm not sure how many state.json issues there are that could benefit from a linter/checker, but it's an idea
[12:52] <mvo> jdstrand: the issue here is that no snap-id is a legal state, it happens if you sideload without any assertions
[12:52] <mvo> jdstrand: this makes it hard to cleanup
[12:53] <jdstrand> mvo: yes, but the revision didn't start with an 'x'
[12:53] <mvo> jdstrand: but I think we could be smarter actually - if it has a normal revision but no snap-id and there is a snapid available in the previous sequence its probably that bug
[12:53] <mvo> jdstrand: yeah, was just thinking this too :)
[12:53] <jdstrand> exactly
[12:59] <Chipaca> hah! tests failed because i can't type
[13:00] <ogra_> standup ?
[13:24] <mup> PR snapcraft#1263 closed: lxd: pass through commands into the container <Created by kalikiana> <Merged by sergiusens> <https://github.com/snapcore/snapcraft/pull/1263>
[13:29] <mup> PR snapd#3233 closed: packaging: remove current mount profiles when purging <Created by zyga> <Closed by zyga> <https://github.com/snapcore/snapd/pull/3233>
[13:30] <mup> PR snapcraft#1278 closed: recording: save the snapcraft.yaml in the resulting snap <Created by elopio> <Merged by sergiusens> <https://github.com/snapcore/snapcraft/pull/1278>
[13:46] <morphis> zyga: where is /var/lib/snapd/mount coming from?
[13:47] <zyga> morphis: snapd writes it
[13:48] <zyga> morphis: it's where mount profiles are stored
[13:48] <morphis> zyga: getting: cannot perform operation: mount --bind /snap/core/current//var/lib/snapd mount /tmp/snap.rootfs_5lYRhE/var/lib/snapd/mount: No such file or directory
[13:48] <morphis> none of the core snaps (stable, candidate or edge) has that directory
[13:49] <zyga> morphis: it should be created by snapd
[13:49] <bdx_>  /join #mailman
[13:49] <morphis> zyga: how if the core snap is read-only?
[13:50] <zyga> morphis: well, /var/lib/snapd is not
[13:50] <zyga> morphis: is that the actual error message you see?
[13:50] <morphis> zyga: yes
[13:50] <zyga> that message looks wrong
[13:50] <zyga> (I mean, the space)
[13:50] <zyga> morphis: how did you get there?
[13:50] <morphis> yeah, I typed it as somehow copying from my VM didn't worked
[13:50] <zyga> ahh
[13:50] <zyga> ok
[13:50] <zyga> that's much better then
[13:50] <morphis> that is on suse with the latest stable snap
[13:51] <zyga> hmm hmm
[13:51]  * zyga looks
[13:51] <zyga> morphis: how did you make that happen?
[13:51] <morphis> wondering if I just did things wrong with my build setup .. let me try again with the package in the repository
[13:52] <morphis> zyga: hm, must be my build
[13:52] <morphis> the package from the repository works fien
[13:53] <zyga> morphis: aha, which distro is that?
[13:53] <morphis> suse
[13:54] <morphis> zyga: btw. https://blog.online.net/2017/04/27/scaleway-disruptive-armv8-cloud-servers/
[13:55] <morphis> zyga: must have been a local change from me, will figure that out later
[13:57] <zyga> morphis: oh nice
[13:57] <zyga> morphis: btw, I got a v7 server but it was running some local kernel without any chance of changing that
[13:59] <zyga> intereqesting forum post https://forum.snapcraft.io/t/local-snap-store/412
[14:00] <mup> PR snapd#3244 closed: many: fix review comments from PR #3177 <Created by morphis> <Merged by niemeyer> <https://github.com/snapcore/snapd/pull/3244>
[14:11] <mup> PR snapd#3156 closed: many: support debian in our CI <Created by morphis> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/3156>
[14:11] <mvo> morphis: thank you very much for this branch
[14:27] <mup> PR snapd#3231 closed: cmd/snap-discard-ns: remove current profile when cleaning up <Created by zyga> <Merged by niemeyer> <https://github.com/snapcore/snapd/pull/3231>
[14:27] <mup> PR snapcraft#1286 opened: lxd: Setup image and target arch for cross-compilation <Created by kalikiana> <https://github.com/snapcore/snapcraft/pull/1286>
[14:50] <zyga> mvo: can you announce here when you are about to tag 2.25
[14:51] <jdstrand> kyrofa: hey, I'm having some trouble with snapcraft cleanbuild. do you have a moment to help?
[14:52] <mup> PR snapd#3232 closed: cmd/snap-confine: write current mount profile <Created by zyga> <Merged by niemeyer> <https://github.com/snapcore/snapd/pull/3232>
[14:52] <niemeyer> zyga: Some notes on this one for a follow up ^^^
[14:53] <niemeyer> mvo: Bash completion feels a bit optimistic if we want to cut 2.25 soon
[14:54] <zyga> niemeyer: I saw, thanks!
[15:03] <mvo> zyga: sure, can do.
[15:03] <kyrofa> Sorry jdstrand, I got a late start this morning. I must have turned my alarm off in my sleep
[15:03] <kyrofa> jdstrand, how can I help?
[15:03] <mvo> zyga: anything particular you are waiting?
[15:07] <jdstrand> kyrofa: no worries, I only asked a moment ago
[15:07] <niemeyer> pedronis: Quick proposal on the aliases topic
[15:07] <zyga> mvo: not really, just want to know when it's out :)
[15:07]  * niemeyer lunches
[15:07] <jdstrand> kyrofa: so, trying to use cleanbuild. I have a working lxd and containers, blah blah. cleanbuild creates a new container each time
[15:08] <zyga> jdstrand: I think this is the design
[15:08] <jdstrand> kyrofa: but it doesn't have networking. the snapcraft help tells me to go to https://linuxcontainers.org/lxd/getting-started-cli/
[15:08] <zyga> jdstrand: aha, that's not designed :)
[15:08] <pedronis> niemeyer: it's probably easy, but needs a quick branch, mvo?
[15:08] <jdstrand> kyrofa: which I did. but that doesn't help. I either need to tell snapcraft how to invoke the creation or I need to tell it to use an existing conatiner
[15:09] <pedronis> mvo: https://forum.snapcraft.io/t/improving-the-aliases-implementation/18
[15:09] <pedronis> mvo: https://forum.snapcraft.io/t/improving-the-aliases-implementation/18/26
[15:09] <jdstrand> kyrofa: but I don't see how to do either
[15:10] <mvo> pedronis: works for me, does not look like a big change
[15:11] <mup> PR snapd#3246 opened: cmd/snap-confine: remove obsolete debug message <Created by zyga> <https://github.com/snapcore/snapd/pull/3246>
[15:11] <kyrofa> jdstrand, when you create new containers, can they hit the network?
[15:11] <kyrofa> jdstrand, by hand, I mean
[15:12] <jdstrand> kyrofa: no. I have to create them use --profile=with-network
[15:12] <jdstrand> using*
[15:12] <kyrofa> jdstrand, ah, that's the problem them
[15:12] <pedronis> mvo: niemeyer: let me try to make a quick branch
[15:12] <jdstrand> yes
[15:12] <kyrofa> jdstrand, snapcraft just runs `snapcraft launch <whatever> -e`
[15:12] <kyrofa> Err.... lxc
[15:12] <kyrofa> Not awake yet
[15:12] <jdstrand> kyrofa: is it possible to add options to the launch? I really need --storage=default --profile=with-network
[15:13] <jdstrand> even if it was just in a config file, that would work for me
[15:13] <kyrofa> jdstrand, I don't think so, not right now anyway, but that seems like a perfectly valid use-case and worth a bug
[15:14] <jdstrand> ok, I'll file a bug. I guess I can just cowboy a patch into /usr to see if it works
[15:14] <kyrofa> jdstrand, snapcraft just shells out... you can just patch snapcraft for now too
[15:15] <kyrofa> I can show you where if you like
[15:15] <jdstrand> that would be great :)
[15:15] <kyrofa> (it's easy to run from source)
[15:15] <kyrofa> Okay, one second, coffee is ready
[15:15] <mup> PR snapcraft#1287 opened: tests: minor cleanups on the spread tests <Created by elopio> <https://github.com/snapcore/snapcraft/pull/1287>
[15:17] <kyrofa> jdstrand, alright, do you want to run from source then?
[15:18] <kyrofa> (or edit the installed snapcraft)
[15:19] <jdstrand> kyrofa: I see it is snapcraft/internal/lxd.py
[15:19] <kyrofa> jdstrand, yep, that's it
[15:19] <jdstrand> kyrofa: I'll just modify deb files
[15:20] <kyrofa> jdstrand, good deal. Just for reference, if you want to run from source, I recommend removing the snapcraft deb install first (leaving its deps in place), but then all you need to do is clone snapcraft and add its bin/ dir to the PATH
[15:22] <jdstrand> kyrofa: yeah, otherwise files in /usr might be used. would have to play with PYTHONPATH iirc (see this with riview tools, et al)
[15:22] <jdstrand> kyrofa: ok, thanks! cleanbuild is working now
[15:22] <kyrofa> jdstrand, awesome! You can see from that code though how easy it would be to add the feature you request
[15:23] <kyrofa> Please do log a bug
[15:23] <kyrofa> The only problem to solve is how to best expose that functionality to the user from snapcraft
[15:31] <jdstrand> kyrofa: https://bugs.launchpad.net/snapcraft/+bug/1686766
[15:31] <mup> Bug #1686766: cleanbuild should allow specifying options to 'lxc launch' <Snapcraft:New> <https://launchpad.net/bugs/1686766>
[15:33] <mup> PR snapd#3247 opened: many: use "SNAP.APP as ALIAS" instead of => when listing added/removed aliases <Created by pedronis> <https://github.com/snapcore/snapd/pull/3247>
[15:33] <kyrofa> Thanks jdstrand
[15:33] <mvo> sergiusens: do you install snaps as part of the snapcraft testsuite? I see some error reports in errors.ubuntu.com that indicate someone tries to install spongeshaker on s390x. if that is the snapcraft tests, please set "SNAPPY_TESTING=1" in the environment, this will ensure no error reports are generated
[15:33] <jdstrand> kyrofa: np. thanks for talking me through it
[15:33] <pedronis> mvo:  niemeyer: snapd#3247
[15:33] <mup> PR snapd#3247: many: use "SNAP.APP as ALIAS" instead of => when listing added/removed aliases <Created by pedronis> <https://github.com/snapcore/snapd/pull/3247>
[15:34] <kyrofa> Any time :)
[15:34] <sergiusens> mvo: yes we install snaps as part of the suite, maybe that SNAPPY_TESTING needs to be mentioned on the forums :-)
[15:35] <mvo> sergiusens: yes, I can do that
[15:35] <jhobbs> is there a way to install different channels/revisions of the same snap at the same time on the same system, by giving them different names perhaps?
[15:35] <jhobbs> so if i wanted juju edge i could run juju-edge.juju and i wanted juju-beta i could run juju-beta.juju or something
[15:38] <mup> PR snapd#3248 opened: Fail early in the spread suite if trying to run it inside a container <Created by mvo5> <https://github.com/snapcore/snapd/pull/3248>
[15:41] <kyrofa> jhobbs, I'm afraid not-- only one revision of a given snap can be active at once
[15:41] <kyrofa> jhobbs, the only way to do something like that would be to have multiple juju snaps
[15:41] <kyrofa> (named differently)
[15:42] <jhobbs> ok kyrofa that's what i figured, thanks
[15:42] <zyga> jdstrand: I let a small comment on https://github.com/snapcore/snapd/pull/2749
[15:42] <mup> PR snapd#2749: interfaces/default: allow mknod for regular files, pipes and sockets (LP: #1636540) <Created by jdstrand> <https://github.com/snapcore/snapd/pull/2749>
[15:42] <zyga> jdstrand: if you want I can take care of it
[15:45] <jdstrand> Trevinho: ok, I finally tested your preload changes. it no longer segfaults. it is interesting that now there is different stderr output: http://paste.ubuntu.com/24467212/
[15:49] <jdstrand> zyga: let me do it, thanks. I've been wanting to get this to pass the tests and this might be the key
[15:50]  * jdstrand hasn't been able to get to his PRs due to other snappy reviews (sorry)
[15:50] <zyga> no worries, we're all in the same boat :)
[15:52] <zyga> jdstrand: I'll look at the netlink one now
[15:52] <pedronis> mvo: that branch is waiting for its travis run , will take a while I suppose
[15:53]  * zyga will break in 40 minutes to visit friends
[15:56] <mvo> pedronis: yeah, I have dinner in the meantime
[16:06] <zyga> jdstrand: one small fixme
[16:08] <Trevinho> jdstrand: are you sure you're using the proper script to launch it? It should be snapcraft-preload. As it seems it doesn't use it right now... Mhmh
[16:12] <jdstrand> Trevinho: I did rename it:
[16:12] <jdstrand> apps:
[16:12] <jdstrand>   snap-review:
[16:12] <jdstrand>     command: snapcraft-preload click-review
[16:12] <Trevinho> Hmm
[16:12] <Trevinho> I got that error when the lib wasn't preloaded...
[16:13] <jdstrand> Trevinho: http://paste.ubuntu.com/24467447/
[16:14] <jdstrand> and I see in command-snap-review.wrapper: exec "snapcraft-preload" click-review "$@"
[16:14] <Trevinho> jdstrand: anyway... It seems that the tool doesn't cleanup temp on ctrl+c... When testing i had quickly filled it with gb of stuff... ;-)
[16:14] <jdstrand> that might be part of the rename. ok, noted
[16:14] <Trevinho> jdstrand: can you lsof -p it to check?
[16:14]  * jdstrand has a number of other things to fix there
[16:16] <Trevinho> jdstrand: don't redefine the part... Just add after: snapcraft-preload
[16:16] <Trevinho> Plus the command
[16:17] <jdstrand> Trevinho: python3 31889 jamie  mem    REG    7,3    28072      39 /snap/review-tools/x1/lib/libsnapcraft-preload.so
[16:18] <Trevinho> Hm... So it indeed is there...
[16:18] <Trevinho> Weird
[16:18] <Trevinho> I wasn't getting that... But I'll try it tomorrow... It's past midnight here... ;-)
[16:18] <jdstrand> Trevinho: I need to redefine it for the amd64 vs not-amd64 stuff (build-backages) I thought
[16:19] <Trevinho> jdstrand: upstream version should work now
[16:19] <jdstrand> honestly, I've not mastered snapcraft parts by any stretch
[16:19] <Trevinho> jdstrand: it works in both amd64 and i386 here.
[16:20] <Trevinho> jdstrand: but in case you can override remote parts things
[16:20] <zyga> Trevinho: I may use your preload helper for classic confinement
[16:20] <jdstrand> Trevinho: ok, thanks!
[16:22] <Trevinho> zyga: Yeah... It's something I need to test too, but it should just work. As it prefers snap stuff over inaccessible elements
[16:23] <Trevinho> Or not existent. But an access issue in apparmor gives a still some false positives
[16:23] <jdstrand> Trevinho: ok, it seemed to build using 'after:\n- snapcraft-preload'
[16:24] <jdstrand> Trevinho: I mean the build. still have the error output I pasted earlier
[16:26] <zyga> mvo: are we missing the actual meat in that branch https://github.com/snapcore/snapd/pull/3241
[16:26] <mup> PR snapd#3241: snap: make `snap prepare-image` read .assert files for local snaps <Created by mvo5> <https://github.com/snapcore/snapd/pull/3241>
[16:26] <zyga> mvo: I only see the tests
[16:27] <zyga> ah, odd, I see it after reloading
[16:28] <jdstrand> Trevinho: speaking of apparmor-- I see denials for /etc/magic
[16:28] <jdstrand> Trevinho: fyi for tomorrow
[16:28] <zyga> mvo: dropped a comment on that branch
[16:28] <zyga> Trevinho: I have a different goal, I'll let you know later when I start working on this
[16:29] <ogra_> zyga, or mvo ... a second signoff on https://github.com/snapcore/core-build/pull/8 would be appreciated :)
[16:29] <mup> PR core-build#8: add shellcheck test, fix code for shellcheck <Created by ogra1> <https://github.com/snapcore/core-build/pull/8>
[16:29]  * zyga breaks
[16:29]  * ogra_ looks for glue to fix zyga 
[16:29] <kyrofa> nessita, is there a way to set up collaboration in the store only after having registered a name (prior to uploading anything)?
[16:29] <zyga> ogra_: I'll check it out later, I need to run
[16:29] <zyga> ogra_: sorry :/
[16:30] <ogra_> zyga, no worries
[16:30] <pedronis> niemeyer: it would be good I think to run the sync script again for the review sprint
[16:33] <morphis> zyga: please see my last comment on https://github.com/snapcore/snapd/pull/3222
[16:33] <mup> PR snapd#3222: many: fix test cases to work with different DistroLibExecDir <Created by morphis> <https://github.com/snapcore/snapd/pull/3222>
[16:33] <morphis> zyga: looks like you were looking at a older revision
[16:35] <morphis> mvo: thanks for merging the debian CI one :-)
[16:50] <morphis> niemeyer: btw. did you do a snap for discourse?
[16:50] <niemeyer> morphis: Of course! :)
[16:50] <kyrofa> niemeyer, would be curious to see that
[16:51] <niemeyer> Yeah, it's definitely an interesting one.. I'm actually using it as a testing bed for some ideas that we've been discussing
[16:52] <niemeyer> The update experience is already much better than the upstream process
[16:52] <morphis> niemeyer: nice, is it in the store?
[16:52] <niemeyer> morphis: I've been working its way there
[16:52] <morphis> niemeyer: and we're running forum.snapcraft.io with it?
[16:52] <niemeyer> We won't be able to get it out of devmode for a while, but I've been fixing a few issues with jdstrand in multiple iterations
[16:52] <niemeyer> morphis: Yeah
[16:53] <morphis> niemeyer: nice, was wondering how mature it is and wanted to try it for a personal project
[16:55] <niemeyer> morphis: It is pretty solid.. there's at least one more issue I need to solve for integrating the database migration on startup, but after that I'd be happy to have you as another tester for sure
[16:56] <morphis> niemeyer: sounds great!
[16:56] <ogra_> morphis, quietening the anbox telegram channel a bit by moving bits to a forum ?
[16:56]  * ogra_ would appreciate that ... :)
[16:56] <morphis> ogra_: was one thing I was thinking about ..
[16:57] <ogra_> 1
[16:57] <ogra_> err
[16:57] <ogra_> +1
[16:57] <morphis> but actually not sure if I want to spend time on administrating that
[16:57] <ogra_> yeah
[16:57] <ogra_> it is surely some extra work
[16:57] <morphis> yeah, both in administration and social maintenance
[17:02] <morphis> niemeyer: can you see why a certain linode instance failed to boot?
[17:02] <niemeyer> morphis: I can try to..
[17:02] <morphis> niemeyer: tried to spin up a fedora-25 instance on Spread-25
[17:02] <niemeyer> morphis: Checking
[17:02] <morphis> but connection timesout after a bit when the instance was already reported as booted
[17:04] <niemeyer> morphis: It's powered off.. probably missed the -reuse flag?
[17:04] <niemeyer> morphis: One detail that we probably need to address both on Fedora and the Debian images:
[17:04] <niemeyer> morphis: By default Linode boots with a custom Linode kernel
[17:04] <morphis> niemeyer: https://paste.ubuntu.com/24467648/ is what I used
[17:04] <niemeyer> morphis: We can fix that by installing the kernel in the image itself, and booting with GRUB 2 as a "kernel" instead (that's how Linode sets it up)
[17:05] <niemeyer> morphis: See details here for the several distros: https://www.linode.com/docs/tools-reference/custom-kernels-distros/run-a-distribution-supplied-kernel-with-kvm
[17:05] <morphis> niemeyer: tought I've set "GRUB 2" for debian
[17:05] <niemeyer> morphis: Could be.. I haven't checked really.. just reminded of the problem now
[17:05] <morphis> niemeyer: https://github.com/snapcore/snapd/blob/master/spread.yaml#L59
[17:05] <niemeyer> morphis: \o/
[17:06] <morphis> niemeyer: did the same for fedora but maybe that is the issue here, let me try without "GRUB 2" for fedora
[17:07] <niemeyer> morphis: Ah, yes, you most probably need to boot without it the first time
[17:07] <niemeyer> morphis: I'll tweak the notes in the forum later to mention this detail
[17:07] <morphis> niemeyer: worked for debian thought with "GRUB 2", however not sure if Fedora uses grub or not
[17:07] <morphis> niemeyer: thanks!
[17:08] <niemeyer> morphis: Problem is that the image needs to have the kernel inside it in the first place and grub be ready to take the boot there, otherwise it won't work
[17:08] <morphis> niemeyer: ok, without "GRUB 2" it worked
[17:08] <niemeyer> morphis:  Ubuntu won't work either, IIRC
[17:08] <morphis> ok
[17:08] <niemeyer> morphis: Ours work because I tuned
[17:08] <niemeyer> Our images, that is
[17:09] <morphis> ok
[17:09]  * ogra_ imagines spoilers and chrome exhaust pipes on gustavos images ...
[17:10] <niemeyer> ogra_: That's sooooo unlike me! ;)
[17:10] <ogra_> heh
[17:11] <niemeyer> I could see myself doing the opposite, taking a 69's beetle and bringing it to its original form :)
[17:11] <niemeyer> But first I need to prepare for the sprint..
[17:11] <niemeyer> Will step out and run some external life errands here.. back later
[17:20] <morphis> niemeyer: can you snapshot Spread-26 as a fedora-25-64 image?
[17:25] <mvo> ogra_: the shellcheck pr will probably be done tomorrow, still working on 2.25
[17:25] <mvo> ogra_: final test is still not done
[17:42] <niemeyer> morphis: Image is a bit large at 1800MB.. can we get it down a bit somehow?
[17:43] <niemeyer> morphis: Note that the restore logic in spread.yaml drops data such as packaging information and packages themselves which were downloaded.. that needs tweaking for fedora and other rpm based distros
[17:43] <niemeyer> This may be part of the bloat there
[17:47] <niemeyer> Will being these point back into the forum so we can discuss async
[17:48] <mup> PR snapcraft#1287 closed: tests: minor cleanups on the spread tests <Created by elopio> <Merged by sergiusens> <https://github.com/snapcore/snapcraft/pull/1287>
[17:59] <jdstrand> Chipaca: ok, re-reviewed https://github.com/snapcore/snapd/pull/3150. I think it is quite close (depending on your opinion of how to handle _filedir, but I'm not blocking on that)
[17:59] <mup> PR snapd#3150: In-snap bash tab completion <Created by chipaca> <https://github.com/snapcore/snapd/pull/3150>
[18:07] <pedronis> mvo: snapd#3247 was running and passing but exceeded time limit :/
[18:07] <mup> PR snapd#3247: many: use "SNAP.APP as ALIAS" instead of => when listing added/removed aliases <Created by pedronis> <https://github.com/snapcore/snapd/pull/3247>
[18:15] <pedronis> mvo: I think we need to rethink something here, a CI process  that can take 3h+ to land something is not very C
[18:18] <pedronis> mvo: you are also the one that suffers most, needing to wait through this for releases, and usually it gets worse exactly around releases
[18:33] <kyrofa> Chipaca, was `snap install --revision=` only recently locked down to collaborators on that snap?
[18:33] <kyrofa> (like, v2.24?)
[18:40] <pedronis> kyrofa: it was always planned to work like that
[18:41] <pedronis> it's the store that does that, in any case, is not a snapd change
[18:41] <kyrofa> pedronis, I'm aware, but it wasn't like that until recently
[18:41] <kyrofa> Huh, okay
[18:42] <kyrofa> Would be nice to get a heads up when stuff like that happens, maybe a forum post
[18:45] <pedronis> kyrofa: I'm really not aware that changed and was different before
[18:46] <kyrofa> pedronis, I've never once had to run `snap login` before today, but have run `snap install --revision=` many times
[18:49] <mup> PR snapd#3247 closed: many: use "SNAP.APP as ALIAS" instead of => when listing added/removed aliases <Created by pedronis> <Merged by pedronis> <https://github.com/snapcore/snapd/pull/3247>
[18:56] <pedronis> mvo: ^ merged
[19:09] <noise][> kyrofa: are you able to install the revision when you are logged in (as a collaborator on the snap) ?
[19:09] <kyrofa> noise][, yes, the only issue is that the behavior seems to have changed without warning
[19:09] <pedronis> niemeyer: I updated the docs to use  "command as alias" format as well
[19:09] <pedronis> kyrofa: is this revision published in some channel? or was it published at some point?
[19:10] <kyrofa> pedronis, it's the previously-stable revision
[19:11] <noise][> kyrofa: understood, trying to find when that change happened
[19:11] <noise][> and is on my agenda to start having store release notes on the forum
[19:13] <Chipaca> kyrofa— snap install --revision= never worked unless you were a collaborator or the revision was tip
[19:16] <facubatista> kyrofa, you say that, after login, you can install a revision that is NOT currently published?
[19:16] <kyrofa> Chipaca, then I must be insane, because I've done it many times to troubleshoot migration issues
[19:17] <kyrofa> facubatista, if "not currently published" = "superceded by another revision in the same channel," yes
[19:18] <Chipaca> kyrofa— well, you could also specify --revision if you _had_ the revision
[19:18] <kyrofa> Chipaca, what do you mean?
[19:18] <Chipaca> kyrofa— if you had it installed
[19:18] <Chipaca> e.g. if you were on 2, refreshed to 3 (but still have 2), you can use --revision to move to 2
[19:18] <noise][> i.e. in the last N (n=3?) that you had installed/updated-to?
[19:18] <Chipaca> yep
[19:18] <kyrofa> Ahhhhhh
[19:19] <kyrofa> Yeah I bet that was it
[19:19] <noise][> bingo!
[19:19] <noise][> ok, glad we all are not crazy :)
[19:19] <Chipaca> noise][— speak for yourself :-p
[19:19]  * Chipaca is probably certifiable at this point
[19:19]  * noise][ clarifies to only apply to this issue
[19:19] <Chipaca> :-)
[19:23] <cachio> niemeyer, hi, I was working on that https://forum.snapcraft.io/t/testing-console-conf/413/8
[19:23] <cachio> niemeyer, I have a solution for that problem
[19:24] <cachio> niemeyer, are you familiar with this topic?
[19:25] <mvo> pedronis: yay, thanks
[19:26]  * Chipaca sadfaces and moves tab completion to 2.26
[19:33] <pedronis> Chipaca: hug
[20:16] <mvo> pedronis: I'm too tired to release tonight, will happen first thing in my morning
[21:20] <zyga> jdstrand_: it's in
[21:21] <mup> PR snapd#2749 closed: interfaces/default: allow mknod for regular files, pipes and sockets (LP: #1636540) <Created by jdstrand> <Merged by zyga> <https://github.com/snapcore/snapd/pull/2749>
[21:23] <jdstrand_> zyga: \o/
[21:23] <jdstrand_> zyga: thank you :)
[21:24] <zyga> jdstrand: I'll go through the netlink one but it has some more content
[21:25] <zyga> jdstrand: and this may also be in the release :-)
[21:25] <zaganator> hi got an issue
[21:26] <zaganator> i'm trying 4 the first time to install snapApp un my system but where is a list of the installable snap?
[21:28] <zaganator> guys no one can answer me
[21:28] <zaganator> ???
[21:28] <kyrofa> zaganator, you can use the software center, or use `snap find` to find snaps
[21:29] <zaganator> i've did it but the few sofware i found are unuseful for me...
[21:30] <zaganator> does some beta version are around to be tested
[21:31] <kyrofa> zaganator, I guess it depends on what you're looking for
[21:32] <jdstrand> zyga: thanks! :)
[21:33] <zaganator> right... but i've found exactly 7 app (only)
[21:34] <kyrofa> zaganator, this might be along the lines of what you're looking for: https://uappexplorer.com/apps?type=snappy
[21:34] <kyrofa> That is an unofficial third-party site, but it indexes our store
[21:35] <zaganator> woooooooooooooow
[21:35] <zaganator> thanks
[21:36] <zaganator> this is better just to try something "done" in snap
[21:38] <kyrofa> niemeyer, do you know if LP: #1636934 was ever contained in a release?
[21:38] <mup> Bug #1636934: snapctl seem to cache values even if snap is removed and then installed again <snapd:Fix Committed by stolowski> <https://launchpad.net/bugs/1636934>
[21:41] <zaganator> leaving Grazie!!
[21:41] <kyrofa> No problem zaganator, have a good one
[21:49] <kyrofa> Ah, v2.24 it seems
[22:52] <mup> Bug #1686852 opened: Can only run hello snap as root <Snappy:New> <https://launchpad.net/bugs/1686852>