/srv/irclogs.ubuntu.com/2018/08/13/#snappy.txt

mborzeckimorning05:05
mborzeckimvo: hi05:42
mvogood morning mborzecki05:43
mvomborzecki: how are you? anything important that I missed in the morning so far :) ?05:52
mborzeckimvo: no, not really, some forum posts but nothing super interesting either05:53
mvomborzecki: yeah, just looking over things, looks all pretty tame so far05:55
zygaGood morning. I woke up but please give me some time to come to senses and prepare for work.06:06
mvozyga: good morning06:08
mvozyga: no fires, take your time06:08
mborzeckizyga: hey06:23
zygaHad my coffee, did some basic unpacking of work stuff, just taking Bit for a short walk to buy bread.07:05
zygaI was home at around 11PM last night07:06
mborzeckizyga: take a day off07:07
zygaI plan to swap on Friday but I really want to write some reports before I forget07:07
zygaI also want to share what I know with everyone07:09
=== chihchun_afk is now known as chihchun
=== pstolowski|afk is now known as pstolowski
pstolowskiMorning!07:16
mborzeckipstolowski: hey07:27
zygaok07:44
zygaI think I'm "back"07:44
zyganow I have a huge pile of papers to go through07:44
zygafrom the last two events07:44
zygathen email reporting and email catch-up07:45
zygalastly some reviews I'd like to do07:45
zygamvo: hey, any news from gustavo?07:45
zygais the standup going to move to an earlier slot?07:45
=== chihchun is now known as chihchun_afk
mvozyga: I have not heard from him yet07:51
zygagood morning Chipaca08:14
Chipacazyga: greetings. You bring coffee?08:14
zygaChipaca: now I feel uncomfortable because yes I do bring coffee, but I have no way to share08:15
mvohey Chipaca ! good morning08:15
niemeyerGoooooood morning!08:15
zygaChipaca: I'll bring you some next time we meet in person08:15
zyganiemeyer: wooot :)08:15
mvohey niemeyer, welcome back!08:15
Chipacazyga: :-)08:15
zyganiemeyer: hey, welcome, how was the hop across the pond?08:15
Chipacaniemeyer: welcome back!08:15
niemeyerThanks! Very happy to be back08:15
Chipacaand now to get some coffee08:16
zyganiemeyer: do you plan to move the standup to an actual early morning stand up time? :-)08:16
niemeyerzyga: That'd be quite nice, but it also means we'd lose Sergio08:16
zygaindeed, that's not great :/08:17
mborzeckiwe can move sergio08:20
zygamborzecki: haha :D08:20
zygawe should ask him first though :)08:20
pedronismorning08:21
mborzeckipedronis: hey08:21
mborzeckipstolowski: left some comments in https://github.com/snapcore/snapd/pull/563208:22
pstolowskimborzecki: thanks, looking08:25
niemeyerpedronis: Morning!08:26
Chipacamvo, pedronis, mborzecki, good morning to you too08:26
* Chipaca now has coffee and all is well08:26
mborzeckiniemeyer: Chipaca: hey08:26
niemeyerYo08:27
pedronisniemeyer: welcome back08:27
ChipacaGiven how chipper niemeyer is I can only assume he hasn't looked at his email yet (or he looked, selected all, and deleted)08:27
zygahahaha08:27
zygaChipaca: I have the same feeling08:27
zygalooking at my inbox now08:28
zygahey pedronis, good morning :)08:28
pedronismvo: Chipaca: I see some PRs asking my review or that seems I should review, how urgent are they?08:28
Chipacapedronis: if  it's tagged 2.35, it's urgent08:28
Chipacapedronis: if it isn't, probably not08:29
pedronisChipaca: mvo: can they wait the afternoon though or not?08:29
* Chipaca defers to mvo on that08:29
pedronisthey are all marked 2.3508:30
pedronis;)08:30
Chipacapedronis: dangit08:31
pedronisChipaca: proxy reg is the large one08:32
Chipacadangit²08:32
mvopedronis: good morning, nice to have you back08:33
mvopedronis: its not super urgent we have a bit of time for 2.35 in beta08:33
mvopedronis: definitely can wait for the afternoon or tomorrow08:33
pedronisok, thank you, sounds reasonable08:33
Chipacamvo: these should all be squash-merges at this point, right?08:34
pedronisI see there's a bunch of PR for 2.3508:38
pedronisI mean, the ones waiting for me are not the only ones08:39
=== chihchun_afk is now known as chihchun
mvopedronis: yeah, some need some high level input from niemeyer like 5340 and 5569, i.e. if the names and high level operations are ok08:45
mvopedronis: the other ones are just work afaict08:45
niemeyerAck08:45
mvoniemeyer: also not super urgent (just slightly urgent), I'm assuming you have tons of backlog from all directions08:45
niemeyermvo: Yeah, it's been one of the most disconnected holidays I've had, so it's all a swamp now :)08:46
pstolowskiniemeyer: hey o/ :)08:47
pstolowskimborzecki: replied, let me know if it makes sense08:47
pstolowski(re review comment)08:47
niemeyerpstolowski: o/08:48
Chipacapedronis: #5617 really starts with #5613 fwiw (but the latter landed already)08:57
Chipacaniemeyer: I can move the morning thing fwiw (even to the afternoon)08:59
niemeyerChipaca: Which morning thing?08:59
Chipacaniemeyer: I saw you moving the standup around, and I've got an hour of my morning blocked off, but it's flexible09:00
pedronisChipaca: I see09:00
pedronisI'll skim that too09:01
niemeyerChipaca: Ah, thanks09:01
niemeyerChipaca: I'm actually just trying to put our standup back into the usual time.. and having a hard time at it :)09:01
pedronisChipaca: I saw in the log you mentioned the autocontext,  I suppose you find out that is not needed in the managers,  it's mostly a thin wrapper for store around other helpers09:01
Chipacaniemeyer: hehe. It's there now :-)09:01
Chipacapedronis: yeah, i chased it down until it disappeared :-)09:02
niemeyerI couldn't manage to get our old event to recur properly.. but I did manage to preserve our hangout by just copy & pasting the link into the location field09:02
ogragrrrr !!!09:18
ograso the current images auto-refresh core in the middle of running console-conf09:18
ograi thought we had a mechanism to prevent that09:19
ograalso ... snapd hangs on shutdown after an auto-refresh (1:30 timeout) is that known ?09:20
niemeyerogra: We still have a mechanism to prevent that.. the mechanism is time-based, though09:32
niemeyerIf it stays up for too long (2h?) it will attempt to refresh09:33
ograwell, it doesnt seem to use a very long timeout atm ... it happened a few mins after booting the VM09:33
ogra(initial boot that is)09:33
niemeyerogra: it certainly not in the few minutes range09:33
niemeyerSo something else is going on there09:33
ograright, thats what i thought ...09:33
ogra(this is an older edge image from the 7th, might be an edge-only thing)09:34
* ogra re-tries with the same image from scratch ... lets see if i can reproduce09:40
ograyep09:41
mvoogra: that is edge? stable?09:41
ograreboots after about 2min09:41
ogramvo, edge09:41
mvoogra: uc16/amd64? i.e.. I just need to create an image and wait to reproduce?09:42
ogramvo, see the other channel09:42
mvoogra: thank you. to test on an stock image, will uc16/amd64 be okay? just to see if its already failing in the base images09:43
mvo?09:43
* Chipaca hugs kyrofa 10:26
* niemeyer hugs Chipaca and kyrofa with no context and shares the love10:27
Chipacaniemeyer: I -1'ed a PR of his10:27
Chipacawith a WAT10:27
Chipacabut he's still awesome10:28
niemeyerDamn.. I've mistaken a potential fight for love10:28
ogralove is full of fights, aint it ?10:28
Chipacaniemeyer: my hug was to emphasize that my criticism was with his work, not with himself10:30
Chipacawhich is easy to forget10:30
pedronisChipaca: is command-chain supposed to support arguments at all ?10:31
niemeyerChipaca: Ah, I thought maybe you were hugging him as a matter of self-protection10:31
Chipacapedronis: well, in that implementation it does10:31
niemeyer;P10:31
Chipacaniemeyer: I'm not scared of him, for two reasons10:31
pedronisChipaca: brokenly, though?10:31
Chipacaniemeyer: one, he's on the other side of the world10:31
Chipacaniemeyer: two, I can run longer10:31
pedronisheh10:32
niemeyerpedronis, Chipaca: No, it shouldn't support arguments.. at least until we understand why10:33
Chipacapedronis: if it's meant to replace a wrapper shell command, then it needs to be able to have spaces and stuff in it10:33
pedronisniemeyer: that was my understanding as well10:33
pedronisseems there is confusion around that though10:33
niemeyerThe idea is to have the command able to be called as "foo bar baz actual-command -its -args"10:33
niemeyerIf there are arguments, then we'll start to worry about ordering issues and whatnot10:34
pedronismaybe is just a matter of missing validation10:34
pedronisChipaca I suppose knows more, he looked at the PR10:34
Chipacaheh10:34
Chipacawait, if that _is_ what's wanted maybe the pr is ok10:34
=== chihchun is now known as chihchun_afk
Chipacait does exec 'chain1 chain2 chain3 actualcmd arg arg arg' (except chainN can have args but let's ignore that bit for now)10:35
Chipacagiven the feature is presented as a way to avoid having a wrapper, I thought this was not what was intended10:35
ChipacaIOW I thought what was wanted was 'chain1; chain2; actualcmd arg arg arg'10:36
pedronisno, the former10:36
Chipacabecause, you can _already_ have chain1 chain2 chain3 in cmd10:36
pedronisbut no args10:36
pedronisChipaca: yes, but then no --shell10:36
pedronisetc10:36
Chipacacan you give me an example of what chains are, then?10:36
ChipacaI did read the forum post but it wasn't illuminating10:37
pedronisChipaca: first class (as in demarcated) wrappers10:37
pedronis?10:37
pedronisniemeyer can probably say more10:38
niemeyerChipaca: Sure, sorry for the lack of context10:39
niemeyerChipaca: The idea is enabling wrappers to be dropped as they exist today10:39
niemeyerChipaca: snapcraft today has to inject some logic via its plugins10:39
niemeyerChipaca: The result is we get the messy shell script where "command" is just a line at the end of it10:39
Chipacaniemeyer: so the wrappers would still exist, they'd just be modified to take args like sudo & etc?10:40
niemeyerChipaca: Instead, we want each plugin to generate its own content in its own script, and at the end call the rest of the chain10:40
niemeyerChipaca: This enables the script to generate its environment, and have the rest of the chain within it10:41
niemeyerChipaca: That also means it may be composed, seeing what's before and after it as a blackbox10:41
niemeyerChipaca: and means we can have /bin/bash as the command and get the shell inside the tip, or after any of the commands really (we haven't designed UI for that latter part)10:42
niemeyerChipaca: Right, they'd exist but be more isolated than they are today10:42
niemeyerChipaca: Adding a wrapper just means adding the command to the end of the chain10:43
niemeyerThis also makes templates work more easily10:44
Chipacaniemeyer: ok10:44
Chipacaniemeyer: I still fear tab completion might be too brittle to support this10:45
Chipacaniemeyer: but I'll leave it to implementers to figure out :-)10:45
niemeyerChipaca: Not sure why?10:46
niemeyerChipaca: I mean, the end result is effectively the same10:46
niemeyerChipaca: I mean, today wrapped commands are already called inside a shell script, in a chain10:47
Chipacaniemeyer: right, but the completer wasn't wrapped10:48
Chipacabah, as long as it all ends in an exec of what used to be exec'ed it'll be fine10:49
niemeyerChipaca: Right, that's what I imagined10:52
niemeyerChipaca: Or at least hoped.. :)10:52
Chipacaniemeyer: :-)10:52
Son_Gokuniemeyer, mvo, JamieBennett, popey: so I'm back home from Flock11:02
Son_GokuI can honestly say that the talk was a great success11:02
Son_Gokupeople were really interested (some difficult questions about store stuff aside)11:02
Son_Gokuand there's definitely interest in plugging in snap delivery into the Fedora pipeline11:03
mvopstolowski: can we cherry-pick https://github.com/pilebones/go-udev/pull/14 into our tree without making later merges harder ? I'm not super familar with git subtree11:07
popeySon_Goku: excellent, great to hear! Was it filmed?11:08
Son_Gokuyes, but probably poorly11:08
popeyhah11:08
Son_Gokuat least audio might be okay, but the hotel wanted to rip off the organizers on the A/V equipment, so last minute purchase of equipment happened11:09
Son_Gokuso you can guess it was kind of rickety11:09
Son_Goku:/11:09
pstolowskimvo: it should be fine, i did something similiar already (had local changes and later merged upstream, it just works out conflicts -if any- as you would expect from git, e.g. there'll be no conflicts unless you really touch same area)11:09
pstolowskimvo: can we just sync with upstream again whe your fix lands? there shouldn't be many changes, if any11:11
mvopstolowski: yeah, no changes afaict, so that should be fine. I will propsoe the same pr against master now11:13
pstolowskimvo: ok. either way is fine11:14
mvopstolowski: I did both now, pushed to upstream and also created one for us so we should be covered either way (ie. if upstream is slow)11:16
pstolowskimvo: great, ty! was it causing failures?11:16
mvopstolowski: yes, build failure on powrpc11:17
pstolowskimvo: hmm, curious why didn't it fail when it landed earlier?11:17
mvopstolowski: it probably did and it was lost in the noise11:18
pstolowskii see11:18
pstolowskiok, thanks for the fix!11:18
mvopstolowski: but maybe not, might be worth investigating11:18
mvopstolowski: do you remember when this landed? a while ago, right?11:18
pstolowskimvo: yes, at least 4-5 weeks ago11:19
mvopstolowski: yeah, it looks like its failing since Jul 17 wich matches (roughly) the merge of go-udev stuff11:21
pstolowskimvo: and it's autopackage tests right?11:25
mvopstolowski: yeah11:25
pstolowskimvo: right.. that's why it went under the radar11:26
mvopstolowski: yeah, no biggie11:26
mvopstolowski: but those small arches are always extra work11:26
ograSon_Goku, a clever person would just have set up a mobile phone in each room to record videos ;)11:30
Son_Gokuyou don't know how close you are to how the video was recorded11:30
ogra:D11:30
Chipacaogra: dashcams are really cheap right now11:33
* niemeyer steps out for lunch11:39
ograChipaca, +111:42
Chipacajdstrand: did you get a chance to look at the hostnamectl denials?11:46
mborzeckiyay, so after the updates to s-c and default apparmor profiles, the basic remapping/file-access tests is passing on ubuntu too11:55
pedronismvo:  I reviewed #561112:10
pedroniswe lost mup?12:12
mborzeckipedronis: yes, it's been silent for the last 2+ weeks12:13
popeyDid mup go on holiday with niemeyer :)12:23
mvopedronis: thank you! looking12:26
mborzeckipstolowski: pushed an update to https://github.com/snapcore/snapd/pull/561412:27
pstolowskimborzecki: thanks, will check in a moment12:28
pstolowski+112:43
mborzeckipstolowski: thanks12:45
niemeyerHe broke down last Tuesday, apparently..12:47
niemeyermup: You okay now?12:47
niemeyermup: no?12:48
niemeyermup: echo foo12:48
niemeyermup: How about now?12:55
zygaoh13:01
zygastandup!13:01
niemeyerHmm.. I can't login13:02
niemeyerIs it just me?13:03
Chipacaniemeyer: we're all here13:04
Chipacaniemeyer: we13:04
pedronisChipaca: I reviewed a bit #561713:10
Chipacapedronis: thanks13:12
Chipacasparkiegeek: could you reply to pedronis' first comment on https://github.com/snapcore/snapd/pull/5617 ? (I could, but it'd be more authoritative from you)13:13
niemeyermup: ping13:20
pedronisChipaca: I checked myself and it seems to be true but not sure it was ever tested13:26
Chipacapedronis: i think it has unit tests, but i'm not sure that's what you mean :-)13:29
pedronisChipaca: I mean the proxying of registration13:30
pedronisin the proxy13:30
Chipacapedronis: yes, that's what i mean13:32
Chipacapedronis: it didn't support custom serial vaults, but did support forwarding to the generic one13:33
Chipacapedronis: and i think there are unit tests to that effect13:33
mborzeckipedronis: when you're done with higih priority stuff, I could use your one last look at https://github.com/snapcore/snapd/pull/5561 Chipaca and pstolowski went through it but as we know those changes may be a bit tricky13:45
mborzeckibtw. 15th is a public holiday here (cc zyga pstolowski)13:48
pstolowskiright, forgot about that13:48
pstolowskicachio: hey, you did some work around journalctl cursor in the spread test right13:49
pstolowski?13:49
cachioyes13:49
cachiopstolowski, I implemented that in the tests13:49
cachiowhy?13:49
pstolowskicachio: good, so the problem i have is this - this is journalctl output I see when my test fails: https://paste.ubuntu.com/p/XH4ps65yQ3/13:50
pstolowskicachio: note the " New test starts here " message13:50
pstolowskicachio: this is when the test thinks cursor starts13:50
cachiopstolowski, yes13:51
pstolowskicachio: so get_journalctl_log doesn't return the early snapd start messages (and i need to match those)13:51
cachiopstolowski, is there any problem there?13:51
pstolowskicachio: i wonder if that is intended or not; we seem to be preparing snapd after journcal curstor initialization, so it's not clear why it's like this13:52
cachiopstolowski, yes, it is intended13:52
cachiopstolowski, if we move the cursor initialization back, then we get a lot of messages from the previous test13:53
cachiopstolowski, and it was causing other issues13:53
pstolowskihmm allright13:53
cachiopstolowski, could you restart snapd as part of the test?13:54
cachioand check this initialization?13:54
pstolowskicachio: yes, that's what i was considering13:54
pstolowskijust wanted to make sure it's intended13:54
cachiowe are already doing that in one test13:54
pstolowskicachio: thanks13:54
cachiopstolowski, yaw13:54
niemeyermup: You ok now?13:54
cachiopstolowski, check catalog-update teswt13:55
cachiopstolowski, I think this a similar test13:55
niemeyermup: echo ok14:01
mupniemeyer: ok14:01
niemeyerYep.. nickserv registration issues, related to the spam measures recently adopted14:01
niemeyerpopey: ^14:01
popey\o/14:01
pedronismborzecki: yes, will look at parallel installs after I have unblocked other things14:03
mborzeckipedronis: thanks14:03
=== Eleventh_Doctor is now known as Pharaoh_Atem
popeyniemeyer: what's the plan to prevent snap (your QA systems?) from flooding https://errors.ubuntu.com/ ?14:11
mborzeckipopey: afaik snapd QA is not reporting errors back to errors.ubuntu.com14:16
niemeyerpopey: On a call14:17
niemeyerpopey: Will ping a moment14:17
niemeyerin a14:17
cachiozyga, hey14:18
cachioI ran the fedora base test on core14:18
zygayes?14:18
cachioand it is failing14:18
cachiohttps://paste.ubuntu.com/p/cGs978ZWqy/14:18
zygayes, it's expected until master hits edge but let me look at the failure14:19
cachioit is trying to get the snap.yaml from an incorrect path14:19
zygayeah, that's exactly that14:19
zygawhich version of snapd was that?14:19
cachiobeta core14:19
cachioI am suing 2.3414:19
cachioI am suing 2.3514:19
zygaI will check if this is in master and in edge14:19
niemeyerpopey: To make sure we're on the same page, what's the exact issue there?  Do we have any open bugs or forum topics?14:19
cachiozyga, if it has been addresses it is ok14:20
zygacachio: fetching now, I'll let you know in a moment14:20
mupPR snapd#5638 opened: interfaces: basic spread test for udev monitor <Created by stolowski> <https://github.com/snapcore/snapd/pull/5638>14:20
zygacachio: but the same test I used passed when the branch was merged14:20
zygacachio: so I believe it is fixed now, just out of sync in that channel14:20
zygacachio: (we added a spread test for it)14:20
cachiozyga, well, this spread test is failing14:20
cachioError executing external:ubuntu-core-16-64:tests/main/fedora-base-smoke14:21
zygacachio: it _passed_ when it was merged into master so either the external target is older than master (which is IMO likely) or something broke since14:21
zygaone sec, almost done here14:21
popeyniemeyer: we discussed in one of the sprints months back. Basically errors.ubuntu.com seems to have a flood of crash reports from snap. They're coming from kvm based installs. I think m_vo and c_hipaca looked into it, and suggested it was from your build / testing systems14:22
popeyniemeyer: having the site flooded with snap crashes makes it less useful / usable.14:22
zygacachio: reproduced in edge, so I suspect edge is just out of date14:23
zygacachio: I will re-check with master14:23
niemeyerpopey: I recall a related conversation back then, and I recall we actually landed changes to reduce how much we logged14:23
niemeyerpopey: It'd be nice to have a proper forum topic so we can have more details about the problem and so people can follow through14:24
popeyniemeyer: I will start a new thread14:26
niemeyerpopey: Thank you14:26
kyrofaChipaca, I haven't looked at the review yet, but indeed, that chain args are intended (see the forum proposal as well as the enshrining spread test)14:36
cachiozyga, are yoiu planning to upload the fedora snapd for arm and other architectures?14:47
cachiozyga, it is failing on arm6414:48
cachiozyga, or should I push the PR to skip it?14:48
zygaskip it please14:48
zygait's hard to cross-build today14:49
zygait will auto build later when it's done inside the fedora infra14:49
cachiozyga, sure, tx14:49
zygathank you14:49
Chipacakyrofa: psh, don't come here with your "facts"14:49
kyrofaChipaca, heh. Find to get rid of them, but they're 1) easy to support, 2) requested by someone, and 3) have no clear downside14:51
kyrofaFine*14:51
kyrofaI suspect this is simply an "easier to add functionality than remove it" argument, which is of course reasonable14:53
Chipacakyrofa: you mean arguments in the chain?14:53
Chipacakyrofa: yeah14:53
kyrofaIndeed14:53
mupPR snapd#5639 opened: snapcraft: set version information for the snapd snap <Created by mvo5> <https://github.com/snapcore/snapd/pull/5639>14:55
Chipacakyrofa: I hope the review ended up making sense though14:56
kyrofaChipaca, indeed. Does the functionality make sense, now?14:57
mvokyrofa: silly question, when is the snapcraft version script run? after the build by any chance?14:57
kyrofaChipaca, there are so many snaps out there where `snap run --shell` doesn't represent anything close to the real environment because of all these wrappers14:58
pedronismvo: +1 for #5611 with a nitpick14:59
mupPR #5611: devicestate: only run device-hook when fully seeded <Created by mvo5> <https://github.com/snapcore/snapd/pull/5611>14:59
mvopedronis: thank you, checking14:59
kyrofamvo, during the prime step15:00
mvokyrofa: cool, thanks15:02
pedronisChipaca: added a question to #5617, I think the answer is no, but making sure15:02
mupPR #5617: overlord/devicestate: DTRT w/a snap proxy to reach a serial vault <Created by chipaca> <https://github.com/snapcore/snapd/pull/5617>15:02
mupPR snapd#5640 opened: tests: skip unsupported architectures for fedora-base-smoke test <Created by sergiocazzolato> <https://github.com/snapcore/snapd/pull/5640>15:03
pedronismvo: looked at #5631 as well, couple of comment/questions15:08
mupPR #5631: snapstate: ensure normal snaps wait for the "snapd" snap on refresh <Core18> <Created by mvo5> <https://github.com/snapcore/snapd/pull/5631>15:08
mupPR core18#63 opened: [RFC] snapcraft.yaml: add current date to core18 rev <Created by mvo5> <https://github.com/snapcore/core18/pull/63>15:18
mvopedronis: thanks for your comments on 5583 too!15:20
pstolowskimvo: since you reviewed some of my udev stuff last week, would you find a moment for https://github.com/snapcore/snapd/pull/5618 or https://github.com/snapcore/snapd/pull/5632 ?15:23
mupPR #5618: overlord: instantiate UDevMonitor <Created by stolowski> <https://github.com/snapcore/snapd/pull/5618>15:23
mupPR #5632: overlord: integrate device enumeration with udev monitor <Created by stolowski> <https://github.com/snapcore/snapd/pull/5632>15:23
cachio_Chipaca, https://paste.ubuntu.com/p/FJVhj5H2H7/ see those permissions16:07
cachio_I saw you changed install-sideload to check this16:07
cachio_but in core it is failing16:08
sergiusensmvo you should switch to snapcraftctl set-version $(whatever) (last section of https://snapdocs.labix.org/extracting-information-from-sources-in-snapcraft-parts/4642)16:49
Chipacacachio_: how are those files getting there?16:49
mupPR snapcraft#2209 closed: tests: add spread suite for tar-content plugin <Created by kyrofa> <Merged by sergiusens> <https://github.com/snapcore/snapcraft/pull/2209>16:51
cachio_Chipaca, which ones??16:59
cachio_all of them?16:59
cachio_I think those are downloaded during test executions16:59
ograsergiusens, but set-version only works from an override or am i wrong ?17:22
ogra(i use it all the time btw, it is awesome ... but if you dont have overrides it is kind of forcing adding one on you)17:23
sergiusensogra: so? snapcraftctl <step> makes what you would otherwise override actually run17:28
kyrofacachio_, spread from master can't seem to run with snapd's spread.yaml: preserve-size is an invalid size string?17:32
kyrofaKnow anything about that?17:32
cachio_kyrofa, you need to update spread17:33
kyrofacachio_, I did17:33
cachio_mmm17:33
cachio_did you download a spread again?17:33
kyrofaI ran `go get`17:34
cachio_curl -s -O https://niemeyer.s3.amazonaws.com/spread-amd64.tar.gz && tar xzvf spread-amd64.tar.gz17:34
cachio_try that17:34
niemeyerkyrofa: zyga mentioned that yesterday.. I need to update, sorry17:34
kyrofaIsn't that this? https://github.com/snapcore/spread/pull/6617:35
mupPR spread#66: Define storage at system level <Created by sergiocazzolato> <https://github.com/snapcore/spread/pull/66>17:35
kyrofaThe one in aws contains stuff that hasn't been merged?17:35
niemeyerkyrofa: Sorry, I thought you were talking about the snap17:44
niemeyerkyrofa: I have no local changes17:45
cachio_niemeyer, I pushed this last week https://github.com/snapcore/spread/pull/6617:45
mupPR spread#66: Define storage at system level <Created by sergiocazzolato> <https://github.com/snapcore/spread/pull/66>17:45
cachio_niemeyer, could you take a look when you have a time?17:45
niemeyerYeah, but that's not kyrofa's point I assume17:45
niemeyerIf it's not merged it can't be used by snapd's spread.yaml17:45
niemeyerand the tarball from S3 can't help either17:46
kyrofaChipaca, https://github.com/snapcore/snapd/pull/5569 has been updated17:46
mupPR #5569: snap,snap-exec: support command-chain for app <Created by kyrofa> <https://github.com/snapcore/snapd/pull/5569>17:46
kyrofaniemeyer, cachio_ false alarm, I just don't know how to use go apparently :)17:48
kyrofaniemeyer, yeah, I don't use the snap as I use lxc17:49
Chipacakyrofa: dude18:07
Chipacakyrofa: that's so much nicer, as a diff18:07
Chipacakyrofa: +1'ed with a long-winded comment :-)18:12
kyrofaChipaca, oh darn, good catch on the env, yes, we need that18:19
kyrofaWhich means I'm missing a test, too18:19
kyrofaWait, no, I'm being silly18:22
kyrofaI'll respond on the PR18:22
* cachio_ afk18:26
zygais Graham on IRC?18:28
sergiusenszyga: I can ask him18:34
zygasergiusens: I'm just curious, I never thought about his IRC handle18:34
pedroniszyga: he is on holiday this week and the next afaik18:34
zygaah, I see18:35
zygathanks18:35
sergiusenszyga: should be seen as degville18:35
=== grumble is now known as Guest76306
=== gurmble is now known as grumble
jdstrandChipaca: which hostnamectl issue are you referring to?19:08
jdstrandChipaca: and hi!19:08
zygajdstrand: hey :)19:23
jdstrandhey zyga :)19:23
=== benoitc_ is now known as benoitc
=== marosg_ is now known as marosg
=== sitter_ is now known as sitter
=== souther_ is now known as souther
=== TinoGuest_ is now known as TinoGuest
mupPR snapcraft#2191 closed: Improve pr template and tools ignored files <Created by touilleMan> <Merged by sergiusens> <https://github.com/snapcore/snapcraft/pull/2191>19:27
mupPR snapd#5641 opened: interfaces: miscellaneous policy updates <Created by jdstrand> <https://github.com/snapcore/snapd/pull/5641>19:46
mupPR snapd#5642 opened: interfaces: miscellaneous policy updates - 2.35 <Created by jdstrand> <https://github.com/snapcore/snapd/pull/5642>19:50
tomreynhi. i'm wondering how to tell apart snap packages (and developers) to trust and those not to trust. surely oyu can't decide this for me, but i notice a lot of packages are submitted by a developer named 'Snapcrafters', and wonder whether you can tell me more about this (generic sounding) developer.19:54
* kyrofa points tomreyn to popey19:55
* tomreyn throws spinach towards popey19:56
popeyI am afk19:58
popeyBut. Look on GitHub for snapcrafters19:58
popeyIt's a repo full of snaps, that are maintained by canonical and the wider community19:58
tomreynthanks20:15
=== tedg_ is now known as ted__
=== ted__ is now known as tedg__
=== tedg__ is now known as tedg
mupPR snapd#5569 closed: snap,snap-exec: support command-chain for app <Created by kyrofa> <Merged by kyrofa> <https://github.com/snapcore/snapd/pull/5569>22:04
mupPR snapd#5643 opened: interfaces/builtin: addtl network-manager resolved DBus fix <Created by tonyespy> <https://github.com/snapcore/snapd/pull/5643>22:10
Chipacajdstrand: hi!22:37
mupPR snapd#5644 opened: interfaces: add audio-playback/audio-record and make pulseaudio manually connect <Created by jdstrand> <https://github.com/snapcore/snapd/pull/5644>22:39
jdstrandeexit22:45
mupPR snapcraft#2211 closed: tests: add spread suite for ament plugin <Created by kyrofa> <Merged by kyrofa> <https://github.com/snapcore/snapcraft/pull/2211>23:37

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!