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

=== Eleventh_Doctor is now known as Pharaoh_Atem
mborzeckimorning05:55
=== [asc] is now known as [-asc-]
mupPR snapcraft#1852 opened: Added a missing step in Hacking.md <Created by Tanesh1701> <https://github.com/snapcore/snapcraft/pull/1852>06:56
zyga-ubuntuo/07:40
mvohey zyga-ubuntu, good monring07:41
zyga-ubuntuhey :)07:41
mupPR core#68 closed: hooks: fix shellcheck complains <Created by mvo5> <Merged by mvo5> <https://github.com/snapcore/core/pull/68>07:44
mborzeckizyga-ubuntu: mvo: morning guys07:47
zyga-ubuntugood morning07:50
kalikianamorning, zyga-ubuntu07:51
zyga-ubuntuhey :)07:51
* zyga-ubuntu had a fsck-initramfs-based-morning 07:51
zyga-ubuntubut all is good now, I hope07:52
kalikiananot how you wanna start your day... :-(07:52
mupPR snapd#4449 opened: cmd/libsnap-confine-private, cmd/snap-confine: fix logging of failed [u]mount when run with SNAP_CONFINE_DEBUG=1 <Created by bboozzoo> <https://github.com/snapcore/snapd/pull/4449>07:53
mvohey mborzecki - good morning and good morning kalikiana07:53
mborzeckikalikiana: morning07:53
kalikianamborzecki: mvo o/07:53
zyga-ubuntugconstpointer ?07:54
zyga-ubuntuwhy do we need that over, apparently, bool?07:54
zyga-ubuntuah, could be the limitation of the test protocol07:55
mborzeckizyga-ubuntu: just following gtest declarations and didn't want the compiler to scream at me07:55
zyga-ubuntuI think I would have preferred a debug library but this change is smaller, +107:56
mborzeckizyga-ubuntu: thanks07:58
mborzeckizyga-ubuntu: have you seen this? https://forum.snapcraft.io/t/on-arch-snaps-show-broken-after-switch-from-snapd-to-snapd-git/3427/408:09
mborzeckipstolowski: morning08:09
zyga-ubuntumborzecki: no, I just had a look now - my bet is it's a mount from some directory that dones't exist on arch in default install, maybe /usr/src or something like08:10
zyga-ubuntu...that08:10
zyga-ubuntuif you can strace it you will get the answer08:11
zyga-ubuntumborzecki: btw, does it work for you?08:12
mborzeckizyga-ubuntu: hm but what fails is: mount --rbind /dev /tmp/snap.rootfs_gwR9tX//dev: No such file or directory08:12
zyga-ubuntumborzecki: or also no?08:12
mborzeckiyes, it does08:12
zyga-ubuntuthat's odd, is the source/target present?08:12
mborzeckiit would be off for /dev not to exist08:12
mborzeckilookign at snap-confine source code, we create the destination directory08:13
mborzeckiaah, w8, we create the destination only it's it's bidirectional08:14
mupPR snapcraft#1853 opened: extractors: support appstream icon and desktop <Created by elopio> <https://github.com/snapcore/snapcraft/pull/1853>08:17
zyga-ubuntuhmm08:18
zyga-ubuntuthat feels like a bug08:19
zyga-ubuntubut08:19
zyga-ubuntu.. /dev should be in the core snap08:19
mvozyga-ubuntu: it is08:19
haisheng-from-chHi, I met a question about snapd. I make a pc.img which use ubuntu-img command. But when i log into the system. the snap can't mount, ant the syslog print:'Jan  5 08:10:49 localhost snapd[889]: 2018/01/05 08:10:49.391477 stateengine.go:101: state ensure error: devicemgr: cannot mark boot successful: cannot determine bootloader' many times. what should i do. Thanks.08:21
zyga-ubuntuhaisheng-from-ch: hey, which gadget/kernel/model did you use?08:24
haisheng-from-chalso when start the system . the screen print 'Mounting Mount unit for core.Mounted Mount unit for core. Unmounted Mount unit for core. ' many times.08:25
mborzeckii'll try to spin a manjaro vm locally and check what's happenning there08:25
ackkkmvo, hi! wrt that changes to base-18 you made on Fri, are they available in the latest build yet?08:26
=== ackkk is now known as ackk
mvoackk: I checked https://code.launchpad.net/~mvo/+snap/base-18 this morning - and it still has not build :( so we probably need to ask in #launchpad what is going on08:27
ackkI guess the few builders availble are hammered08:27
zyga-ubuntuackk: what's wrong with the build farm?08:29
haisheng-from-chkernel is 1604. gadget is the sample which provided in website.the model is customized by myself.08:30
haisheng-from-chthe model is '{08:31
haisheng-from-ch  "type": "model",08:31
haisheng-from-ch  "authority-id": "9go0hDakgpo17fYGy06ZguLT8Ly0Ma9F",08:31
haisheng-from-ch  "brand-id": "9go0hDakgpo17fYGy06ZguLT8Ly0Ma9F",08:31
haisheng-from-ch  "series": "16",08:31
haisheng-from-ch  "model": "kylin-test",08:31
haisheng-from-ch  "architecture": "amd64",08:31
haisheng-from-ch  "gadget": "kylin-gadget",08:31
haisheng-from-ch  "kernel": "pc-kernel",08:31
haisheng-from-ch  "timestamp": "2018-01-08T06:23:22+00:00"08:31
haisheng-from-ch}08:31
haisheng-from-ch'08:31
ackkzyga-ubuntu, it was shutdown because of meltdown/spectre, only whitelisted projects are built08:32
ackkzyga-ubuntu, so no PPA and snap builds08:32
zyga-ubuntuaaah08:33
zyga-ubuntumakes sense08:33
mvoackk: maybe we are not in that whitelist08:37
* zyga-ubuntu uses his GPU to heat up the room08:42
ackkmvo, yeah you should ask about it, I know other teams did08:42
zyga-ubuntudarn it's a cold day today08:42
haisheng-from-chhi, zyga-ubuntu, any info can be provieded for me about this error?08:44
zyga-ubuntuhaisheng-from-ch: not immediately, I work on core snapd but how it combines with reference gadgets and ubuntu image is complex; perhaps ask ogra_ as he's closer to that layer08:44
zyga-ubuntuit's best to open a forum topic08:45
zyga-ubuntuinclude all the details: which ubuntu-image you've used, how did you boot it, etc08:45
haisheng-from-chok thanks.08:45
mupPR snapd#4450 opened: snap: support `command-not-found` symlink for `snap advise-command` <Created by mvo5> <https://github.com/snapcore/snapd/pull/4450>09:03
ackkmvo, so with your latest changes you were able to get a working maas snap installed, right?09:05
mvoackk: yeah, it was not getting past "intializing" though09:09
mvoackk: fwiw, I ask on #launchpad about the build but I guess tricky TZ wise currently09:10
mvoackk: to get answers09:10
ackkmvo, cool. could you pass me the snap for the base so i can try locally (see if I can actually get maas to work)09:11
mvoackk: sure, let me try a cleanbuild for you09:14
ackkmvo, you might want to try #launchpad-ops09:17
zyga-ubuntuhey Chipaca09:23
Chipacazyga-ubuntu: o/09:23
Chipacazyga-ubuntu: over the weekend i might've gone all "here's a nickel, kid" on somebody's distro09:27
zyga-ubuntuChipaca: sorry, the analogy eludes me09:27
Chipacazyga-ubuntu: http://assets.amuniversal.com/6b08abb09fbb012f2fe600163e41dd5b09:27
zyga-ubuntuChipaca: are you saying you tried a bunch of distros?09:27
zyga-ubuntuhaha09:27
Chipacazyga-ubuntu: in particular, https://forum.snapcraft.io/t/cannot-comunicate-with-server-mx-linux-17/3455/209:28
kalikianaelopio: you're awake?09:31
mupPR core#70 opened: hooks: use symlink to run `snap advise-command` <Created by mvo5> <https://github.com/snapcore/core/pull/70>09:31
Chipacakalikiana: it's 3am in .cr09:31
kalikianaChipaca: Well, it didn't seem to stop him from pushing code to GitHub, that's why I'm asking09:32
Chipacaah09:32
Chipacakalikiana: i read it as a "are you awake", not as "wtf you awake"09:32
Chipaca:)09:32
kalikiana:-D09:33
kalikianaEnglish is so ambiguous when you don't use properly foul language09:34
Chipacawell i could've also been unambiguouss without being lazy, but i'm lazy09:35
* zyga-ubuntu crosses fingers09:46
mborzeckiTIL manjaro has a user friendly installer09:46
zyga-ubuntuis it just me or has the lower temperature brought much higher pressure09:50
zyga-ubuntuI don't feel sleepy like I did all last week09:50
Chipacamvo: you around?09:56
mvoChipaca: yes, good morning!09:57
Chipacamvo: good morning! what are my chances of you finishing your review of #4394?09:58
mupPR #4394: snap: give the snap.Container interface a Walk method <Created by chipaca> <https://github.com/snapcore/snapd/pull/4394>09:58
mvoChipaca: *cough* I let you wait long enough - I do that now as in right now10:01
Chipaca:-D10:01
* kalikiana coffee break10:01
Chipacanote fedora tests are disabled again10:03
mborzeckibtw. i actuallt hit the same problem as the spread tests did when updating my wife's fedora on friday10:04
Chipacamborzecki: which problem?10:05
Chipacamborzecki: or rather, which of the problems? :-)10:06
mborzeckiChipaca: failure to downlaod from updates repo10:07
Chipacaah10:07
Chipacamborzecki: i've also seen (in the tests) fedora not having 'snap' in the path, and fedora's systemd not knowing about snapd.service10:08
Chipacathat's the point i disabled the test again10:08
Chipaca(after re-running them ~6 times because of the repo thing)10:08
mborzeckithat's interesting, was it reproducible?10:08
Chipacasomething's very broken, needs fixing, but beyond me atm10:08
Chipacamborzecki: afaik it was just the once, but it was just the breaking point10:08
mborzeckihaha ok :)10:09
Chipacathat is, i had about 6 runs of it breaking because of the repo thing10:09
Chipacathen it didn't break because of the repo and instead didn't know about snapd10:09
Chipacaor the service10:09
Chipaca(different instances of fedora in the same run)10:09
mborzeckiwell f26 was to be switched to manual anyway, hoping we could get the f27 PR merged soon10:09
Chipacaso, (╯°□°)╯︵ ┻━┻10:09
=== tinwood_ is now known as tinwood
Chipacaok, off to physio for me10:18
* Chipaca bbi1h10:18
mborzeckihmm installed snapd-git on clean manjaro .. and it's broken, seems like snap mount dir is /var/lib/snapd/snap, but there's only /snap in the system, /var/lib/snapd/snap does not exist10:38
mborzeckizyga-ubuntu: any idea who i can talk to about this?10:38
zyga-ubuntumborzecki: so which of the two layouts would manjro prefer?10:39
mborzeckiidk, seems like they're undecided10:41
* kalikiana moving to coffee shop, brb10:42
mborzeckiso i managed to get:11:09
mborzeckiName         Version  Rev   Developer  Notes11:09
mborzeckicore                  3748  canonical  broken11:09
mborzeckihello-world           27    canonical  broken11:09
mborzeckion manjaro11:09
zyga-ubuntumborzecki: what's the configuration there/11:09
zyga-ubuntumborzecki: did it reexec11:09
zyga-ubuntumborzecki: is it using /snap or /var/lib/snapd/snap?11:09
mborzeckiyeah, it's using /var/lib/snapd/snap11:10
mborzeckilooks like the manjaro `community` repo pacakaes do not do a proper cleanup when removing11:10
zyga-ubuntuahh11:10
zyga-ubuntuthat's not catastrophic11:10
mborzeckithere's bits and pieces left behind, one of those is mounted snaps11:10
mborzeckiand for some reason i ended up having `hello-world` in /var/lib/snapd/snap but there's no core11:11
mborzeckiuhh, taje that back, there's 'hello-world' in /snap but no 'core'11:12
zyga-ubuntumborzecki: what if you start from scratch on a clean manjaro system11:12
zyga-ubuntuis it still broken then?11:12
mborzeckii had a clean system, then installed snapd-git, but apaprently they have snapd-git in community repo (?) and it was broken like i described earlier11:13
zyga-ubuntuaha, I see11:13
zyga-ubuntumborzecki: they accept PRs there so I guess we need to update it11:13
mborzeckithen i removed that package and tried to install snapd-git from aur, ran into multiple issues with files left behind by their community package and finally got into the 'broken' state :)11:14
ackkmvo, any luck on the build?11:17
* kalikiana having lunch earlier today11:18
* zyga-ubuntu burns spread cycles on iteration with apparmor11:20
mvoackk: not yet, I can give you a manually build one, for some reason "snapcraft cleanbuild" fails for me in artful, maybe deboostrap is doing things that are not supported, I get https://paste.ubuntu.com/26346220/ ( kalikiana may know more). I can give you a hand-hacked one instead11:21
ackkmvo, that would be helpful, thanks11:23
mupPR snapd#4451 opened: cmd/snap-update-ns: improve mocking for tests <Created by zyga> <https://github.com/snapcore/snapd/pull/4451>11:26
niemeyerGood morning!11:26
zyga-ubuntuniemeyer: hello11:27
zyga-ubuntulong time no see!11:27
niemeyerIndeed!11:28
mvoackk: please try http://people.canonical.com/~mvo/tmp/base-18_very-unstable_amd64.snap11:28
niemeyerJust learning how to type again..11:28
ackkmvo, thanks11:28
mvohey niemeyer - welcome back! we missed you11:28
niemeyermvo: Heya, thanks!11:28
niemeyerMissed you all too.. was a bit hard to put myself away from all action :)11:29
mborzeckiniemeyer: hey, how was your vacation?11:29
niemeyerIt was great being so offline for a few days11:30
ackkmvo, still getting https://paste.ubuntu.com/26346261/ when trying my snap11:30
kalikianamvo: you get that error with cleanbuild? I've never seen that. Would you mind filing a bug?11:32
pstolowskiniemeyer, hi! welcome back!11:34
* kalikiana getting food now, biab11:43
mupPR snapd#4452 opened: cmd/snap-update-ns: enable writable mimic, allow content sharing to $SNAP <Created by zyga> <https://github.com/snapcore/snapd/pull/4452>11:50
zyga-ubuntuwow, the bot is instant11:50
zyga-ubuntuwhen I opened this PR the latency was << 1s11:51
* zyga-ubuntu food break11:54
Chipacazyga-ubuntu: i think you just happened to open the PR at :59 :-)12:00
mvokalikiana: sure12:00
mvoackk: could you please try in clean vm? I can't reproduce this error12:00
zyga-ubuntuChipaca: hehe, maybe :)12:02
mvoChipaca: you have a first bit of review, I will continue in a little bit, its fine don't get me wrong, just tiny ideas/nitpicks12:02
zyga-ubuntumvo: I'll do two more PRs on hole-poking and layouts and then look at LXD mount issue12:02
Chipacamvo: ah then i'll wait (i already added your suggestion, was about to push)12:02
Chipacamvo: if you consider them nitpick-level, i can address them in the followup instead of here12:03
Chipacamvo: let me know :-)12:03
mborzeckithe AUR snapd package does not build :(12:03
mvoChipaca: interessting idea, we could merge and then do a follwup indeed12:06
Chipacamvo: i mean, i have a followup -- but it's not small12:06
Chipacaso maybe it's a _bad_ idea :-)12:06
Chipacabut it's certainly an idea12:07
mvoChipaca: the dirstack is used instead of recursion because you want to keep the open file handles low?12:07
mvoChipaca: heh :)12:07
Chipacamvo: and the call stack12:07
mvoChipaca: *nod*12:07
Chipacamvo: better to have a stack of string than a stack of stacks12:08
mvo+112:08
Chipacaat least that's what i was taught in uni, back when i paid attention12:08
mvoChipaca: was just wondering as the recursive version is easier to read but its fine, your reasoning is sound12:08
mvoChipaca: when you apply the "readOneDir" idea, maybe "readOneDirN()" and we add the "100" to the readOneDirN() call?12:10
Chipacamvo: what for?12:10
mvoChipaca: mostly clarity, readOneDir() is really read100ItemsFromOneDir :)12:11
mvo(as it is today/in that pastebin)12:11
Chipacamvo: maybe i should rename it babySteps()12:12
Chipacaas in Walk() -> babySteps()12:12
Chipaca:-)12:12
mvoChipaca: heh, yeah, something like this, seriously, just to avoid our future selfs using it assuming it would read *all* of that dir12:12
mvo(or my future self that has a limited memory span)12:12
ChipacaI'll rename it something super obvious, like twiddle()12:14
ChipacadoThing()12:14
Chipacaoh, i know! doProcessThing()12:14
zyga-ubuntujust go all the way and call it all twinky, twonky, twooty, twoo, calling each other with one global variable as help12:14
Chipacazyga-ubuntu: and the global variable should be literally 'help'12:16
pstolowskiChipaca, hey, there are rumours you have a lot on your plate and might want some help? for example with warnings, or free disk check?12:16
zyga-ubuntuChipaca: bonus point if it's a function pointer initialized to a XKCD strip12:16
Chipacapstolowski: warnings comes before free disk check warnings, but free disk computation coud come before that12:16
* zyga-ubuntu prepares oatmeal, the O(1) complexity food for software developers12:17
zyga-ubuntuwater, flakes, heat, eat12:17
Chipacazyga-ubuntu: this is go, you can't do `var help func() = "http://..."`12:17
zyga-ubuntuChipaca: function printing that or sensible-browser opening that would do12:17
zyga-ubuntuhttps://xkcd.com/1513/ is fine12:18
Chipacazyga-ubuntu: is it bad that somewhere on my other computer is a javascript page that edits itself until it compiles12:18
Chipacapstolowski: i've got a branch with part of warnings, i think? but not sure if it'd still work as it's from two sprints ago12:19
pstolowskiChipaca, perhaps I could take free disk computation?12:20
Chipacapstolowski: disk usage shares some of the issues with snapshots for which i wanted to fix user iteration, but i wasn't able to get to the bottom of those failures12:20
Chipacapstolowski: actually perhaps that's a good place to poke: want to see if you can figure out the failures?12:21
Chipacapstolowski: if you take #4299 and then12:22
mupPR #4299: osutil/user: replace our uses of os/user and filepath.Glob("/home/*") <Created by chipaca> <https://github.com/snapcore/snapd/pull/4299>12:22
Chipacapstolowski: spread  -seed=1512088627 -shell linode:ubuntu-14.04-64:tests/main/{interfaces-browser-support,abort}12:22
Chipacapstolowski: but with -debug instead of -shell12:22
Chipacapstolowski: you'll see the failures i mean (or you should)12:22
pstolowskiChipaca, ack, will see if I can find something12:22
Chipacapstolowski: the failure is the whole thing dying (spread says something about EOF)12:23
Chipacapstolowski: good luck12:23
pstolowskiChipaca, ahh, that failure12:23
mupPR snapd#4453 opened: Update README.md <Created by popey> <https://github.com/snapcore/snapd/pull/4453>12:23
Chipacapstolowski: indeedly12:24
mupPR snapcraft#1854 opened: Update README.md <Created by popey> <https://github.com/snapcore/snapcraft/pull/1854>12:24
greybackhey, any easy way to re-run CI on this? https://github.com/snapcore/snapd/pull/436512:25
mupPR #4365: interfaces/mir: allow Wayland socket and non-root sockets <Created by gerboland> <https://github.com/snapcore/snapd/pull/4365>12:25
zyga-ubuntugreyback: as in restart?12:26
Chipacagreyback: by CI you mean travis?12:26
zyga-ubuntu just did12:26
greybackzyga-ubuntu: Chipaca yes and yes12:27
Chipacagreyback: merge master first12:27
zyga-ubuntuaww12:27
Chipacazyga-ubuntu: fedora will fail :-/12:27
zyga-ubuntusorry for wasting cycles12:27
zyga-ubuntucancelled12:27
greybackah, the fedora thing still not fixed12:27
greybackok12:27
Chipacagreyback: well, if you merge master, they're disabled12:27
greybackChipaca: aha, ok12:27
greybackwill do12:27
Chipacaso no, but yes12:27
greyback:)12:27
Chipacagreyback: note if people have looked at it already we ask you merge instead of rebasing12:29
greybackChipaca: good to know, thank you12:29
mvoChipaca: ok, finished the rest, I get some lunch now12:30
ackkmvo, I'm testing in a container, not a vm12:30
ackkI can try a clean one, though12:30
mvoackk: if its not too much hassle that would be great.12:30
ackksure12:30
mvoackk: I couldn't reproduce the issue, but I was testing using a vm :/12:30
* mvo lunch12:30
ackkmvo, https://paste.ubuntu.com/26346467/ in a clean LXD12:34
mvoackk: thanks, puzzling12:35
ackkthe first error I 've seen randomly happen, but usually it's just the first time12:35
kalikianare12:42
pstolowskiChipaca, interfaces-browser-support from your branch passed here. i'm running 16.04, could this be a factor?12:59
Chipacapstolowski: i'm running 16.04 as well12:59
Chipacapstolowski: note it only fails together with another test12:59
pstolowskiChipaca, aha!12:59
Chipacapstolowski: that's why the command was as i typed13:00
pstolowskiI should treat your command literally.. yes13:00
Chipacaniemeyer: standup?13:01
kalikianapopey: Hey! Can you provide an example that triggers this bug? https://bugs.launchpad.net/snapcraft/+bug/174175213:12
mupBug #1741752: yaml.constructor.ConstructorError: could not determine a constructor for the tag '!ExtractedMetadata' <Snapcraft:Incomplete> <https://launchpad.net/bugs/1741752>13:12
popeykalikiana: done13:14
kalikianapopey: Thanks! Will try to reproduce here13:25
pstolowskiChipaca, and it passed https://pastebin.ubuntu.com/26346695/13:30
pstolowskiChipaca, you said it was failing every time for you?13:30
mborzeckiChipaca: i can look into fedora issues later today/tomorrow13:34
popeykalikiana: are we going to get stacktrace spam turned off sometime soon?13:37
kalikianapopey: There were some fixes for that already. Have you tested with the --beta snap?13:39
popeykalikiana: I'm on edge13:39
kalikianapopey: If that isn't a Freudin slip :-P Can you paste any recent example? We might not have caught all of them13:40
popeykalikiana: how about the bug you just asked me to put an example on? :)13:40
kalikianapopey:  Ah, right. So in this case you see the trace because it's not a known failure case. It's a genuine bug so this will need a proper exception code path.13:44
kalikianaWe don't generally try to hide those13:45
popeyI don't ever want to see them13:45
diddledanme too13:45
popeyunless I pass some kind of -show_me_the_python_nonsense_I_dont_care_about13:45
diddledanonly devs need to see those13:45
diddledanjust say "we dun goof'd" on unknown errors and leave it there13:46
popeySNAPCRAFT_VERBOSE=1 would do13:47
popeyi would set that on build.snapcraft.io or travis, but never on my laptop13:47
kalikianaWe could make them `--debug` only and something like `Please re-run with --debug to get a full trace`.  The most important aspect to my mind is that there's a clear path to knowing how to get the error and report it if desired.13:48
popeythat'd work13:48
diddledaneven better: --file-bug; that runs through until the failure and then gets all the useful debug info and posts it to launchpad similar to ubuntu-bug does13:49
diddledanor maybe call it "--create-bug"13:50
diddledansomething like that anywho13:50
diddledanthen we don't need to even work out which bits we need to copy13:50
kalikianaThat might need some discussion on what that info is... although that's a nice idea13:52
diddledanor rather than being explicit when it hits a failure it just prompts "do you want to create a bug? (Y/n)" which you can disable with a `--quiet` flag13:53
diddledanbonus points for finding duplicates13:54
kalikianaThat would've been awesome for codein...13:54
* kalikiana won't have time to look into the anytime soon13:54
diddledanpop it on the backlog :-)13:55
kalikianadiddledan: Mind filing a bug for it?13:55
diddledanroger that13:56
popeythere is one13:56
popeyi filed it iirc13:56
kalikianaFor "file a bug"?13:56
popeyno, for stfu13:56
popeyhttps://bugs.launchpad.net/snapcraft/+bug/174026513:56
mupBug #1740265: Stack trace makes it hard to discern real errors <Snapcraft:New> <https://launchpad.net/bugs/1740265>13:56
popeyPlease don't push that back until after we have bug reporting built in though :(13:57
kalikianapopey: Aye, this one is pretty straightforward. I'll bring it up later in our weekly meeting13:57
popeythanks13:57
diddledanbug #174190014:03
mupBug #1741900: Add file-a-bug functionality on errors <Snapcraft:New> <https://launchpad.net/bugs/1741900>14:03
kalikianadiddledan: Thanks!14:05
* pstolowski lunch14:10
* zyga-ubuntu quick break to catch up with kids14:10
* mborzecki is off to pick up the kids14:19
ogra_cyphermox, i have the next wlan module that doesnt support unbind ... given how big that block in netplan already is i wonder, cant we get away without unbinding the dirvers at all ?14:29
ogra_cyphermox, ath6kl_sdio this time ...14:30
cyphermoxnot afaik14:31
* ogra_ will file a bug and patch as usual ... but all these SRUs get tiring 14:31
Chipacapstolowski: indeed. Can you run the whole suite?14:32
Chipacapstolowski: also, what's your PROMPT_COMMAND? :-)14:33
ogra_cyphermox, https://code.launchpad.net/~ogra/netplan/+git/netplan/+merge/335824 .. do you need a separate MP for the xenial branch or will you just backport it ?14:41
mupPR snapd#4454 opened: snap: fix gadget.yaml parsing for multi volume gadgets <Created by mvo5> <https://github.com/snapcore/snapd/pull/4454>14:42
mupPR snapd#4455 opened: store, daemon/api: Rename MyAppsServer, point to dashboard.snapcraft.io instead <Created by sparkiegeek> <https://github.com/snapcore/snapd/pull/4455>14:42
zyga-ubuntuback to work14:48
ogra_cyphermox, https://bugs.launchpad.net/ubuntu/+source/nplan/+bug/174191014:52
mupBug #1741910: ath6kl_sdio does not support unbinding <netplan:New> <nplan (Ubuntu):New> <nplan (Ubuntu Xenial):New> <https://launchpad.net/bugs/1741910>14:52
cyphermoxogra_: it's fine as-is,thanks!15:00
ogra_awesome !15:00
elopiohello!15:00
elopiokalikiana: I am awake now :)15:00
kalikianaelopio: :-D15:15
kalikianaelopio: Actually there's something I'd like your input on. Can you have another look at snapcraft#1847 and tell me your thoughts on conditional `sudo` in `_container_run`? kyrofa wasn't very happy with it, so I changed it twice now. I figure a third opinion would help figure out the best path15:19
mupPR snapcraft#1847: lxd: Use user in container when mounting remote via sshfs <Created by kalikiana> <https://github.com/snapcore/snapcraft/pull/1847>15:19
kalikianaelopio: Also in case you haven't seen it, I made some comments on snapcraft#185315:21
mupPR snapcraft#1853: extractors: support appstream icon and desktop <Created by elopio> <https://github.com/snapcore/snapcraft/pull/1853>15:21
elopioyup, thanks for the review.15:21
elopiokalikiana: I find that clear, if user != 'root': prepend sudo.15:25
kalikianaelopio: first I had heuristics, then I had user=False... if you like this version I'm hoping kyrofa will also like it, but otherwise I'm out of ideas :-P15:26
kyrofakalikiana, haha, I'm sorry to be causing pain. user=False was way better15:27
kalikianakyrofa: :-|15:27
elopiothat's easy to fix, ask kyrofa for what will make him happy, instead of guessing :D15:27
kyrofakalikiana, I mean way better than the heuristics15:27
elopiolol15:27
kyrofakalikiana, haven't looked at the new way yet15:27
kalikianakyrofa: Oh, hah, okay15:27
kalikianaI'm actually liking the latest one a lot more myself now than what I did before15:28
kyrofaAlright I'll take a look soon. I have oodles of codein reviews15:28
kalikianaThe good kind of spam ;-)15:29
kalikianakyrofa: We can also have a quick chat about it in/after the weekly, might be easier at this point15:30
kyrofakalikiana, we can do that if I haven't been able to review by then, I know you go *poof* shortly after15:30
kalikianaYeah. I'm weird like that. As if the sun somehow goes down earlier where I'm at :-P15:32
mupPR snapcraft#1854 closed: Update README.md <Created by popey> <Merged by kyrofa> <https://github.com/snapcore/snapcraft/pull/1854>15:43
kyrofakalikiana, yeah, let's chat about this in a few15:51
=== __chip__ is now known as Chipaca
* zyga-ubuntu runs new tests and goes to update the forum on the progress towards layouts16:08
Chipacapstolowski: sorry if i missed your reply, were you able to run the full suite?16:24
pstolowskiChipaca, no, I got a bunch of EOFs, but not on the tests in questions16:25
pstolowski*in question16:25
Chipacapstolowski: that's fine16:26
Chipacapstolowski: those test were not the problem, the EOFs were16:26
pstolowskiah, ok16:26
Chipacajust that with those two i was always able to reproduce, but it's weird enough that i'm not surprised it's moved16:26
pstolowskiChipaca, re my command prompt, I use zsh and oh-my-zsh dot files ;)16:26
Chipacabooh :-) ok16:26
pstolowskiwho uses bash anyway? ;)16:27
Chipacao/16:28
ogra_hey !16:29
* Chipaca hides before ogra_ goes nukular16:30
ogra_lol16:30
mupPR snapcraft#1855 opened: storeapi: add docstrings for _snap_index_client.py <Created by konrad11901> <https://github.com/snapcore/snapcraft/pull/1855>16:34
brunosferHi guys, does anyone knows how can I install the exact version of a snap on ubuntu core?16:39
zyga-ubuntubrunosfer: what do you mean by exact version of a snap?16:45
pstolowskiChipaca, so it appears I need to run multiple spread tests to trigger EOF, that matches your observations right?16:53
Chipacapstolowski: yuup16:53
=== [-asc-] is now known as [asc]
brunosferzyga-ubuntu: e.g. snap discord has older versions. the current version is 0.0.3, however it has an older version 0.0.2, if I remove this snap from my OS, can I make something like sudo snap install discord --version=0.0.2 ?17:03
brunosferNot exactly a rollback to the previous version, but rather a version in particular, however in this case such thing does not apply.17:04
zyga-ubuntubrunosfer: not quite like that, versions are meaningless, you can install appropriate revision (see snap install --help)17:06
ogra_you can do that if you own the snap17:06
ogra_but only then17:06
zyga-ubuntubrunosfer: you can list the revisions you have on your machine17:06
zyga-ubuntubrunosfer: you can switch between any revisions that are published (by switching channels)17:06
zyga-ubuntubrunosfer: and between any revisions on your machine that you already had (by using -r)17:06
ogra_... and between random revisions from the store if you are the owner (developer)17:07
ogra_(unless that got disabled since i used it last)17:08
zyga-ubuntuogra_: no, it's a desired feature17:08
ogra_right17:08
kyrofakalikiana, test failures on snapcraft#184717:09
mupPR snapcraft#1847: lxd: Use user in container when mounting remote via sshfs <Created by kalikiana> <https://github.com/snapcore/snapcraft/pull/1847>17:09
kalikianakyrofa: Eh. Lemme check those quickly before I leave. Those all passed locally...17:10
kalikianaThanks17:10
* Chipaca hugs mvo 17:12
Chipacamvo: thank you for asking me for more tests17:13
kalikianaMeh, I was missing a mock geteuid there17:17
sparkiegeekis there a way of telling 'snap set' to not show progress (because I'm running it from a script)?17:32
zyga-ubuntuChipaca: ^17:34
Chipacasparkiegeek: </dev/null17:34
* zyga-ubuntu goes to fix a quick oversight in the new mimic code17:35
Chipacasparkiegeek: although it should already do that if stdin is not a tty17:35
zyga-ubuntuwell, not in minic but around it17:35
sparkiegeekChipaca: thanks17:35
Chipacasparkiegeek: just checked, and in 2.30 at least, if stdin is not a tty, you should get the nonverbose noninteractive "progress bar"17:35
Chipacait'll just print success17:36
Chipacaand that sort of thing17:36
sparkiegeekChipaca: confirmed with 2.30, stdin=open('/dev/null') does what I want17:36
sparkiegeekI was trying to find a --quiet/--non-interactive option17:36
sparkiegeekthis is fine though, cheers17:36
zyga-ubuntusparkiegeek: if this is python, use subprocess.DEVNULL17:37
mupPR snapcraft#1856 opened: remote_parts: Use hashed folder based on parts URI <Created by kalikiana> <https://github.com/snapcore/snapcraft/pull/1856>17:37
kalikianaAlrighty, pushed the remote parts fix out, now I'll call it a day17:39
* zyga-ubuntu will work for a little while longer to get all of the mimic branches merge-worthy and fully functional17:40
zyga-ubuntuand tomorrow, layouts17:40
sparkiegeekzyga-ubuntu: good shout17:41
kyrofaHey ogra_, do you know anything about the kernel on the nvidia Jetson boards? Can they run snaps?17:41
ogra_no idea17:41
ogra_but i doubt that17:42
kyrofaMe too17:42
sparkiegeekis there a way of getting snapd version information in a parseable format (e.g. JSON/YAML/..)?17:43
sparkiegeekor should I just do "^(.*)\s+(.*)$" style parsing?17:44
zyga-ubuntusparkiegeek: talk to the socket17:44
zyga-ubuntuthere's a whole API there17:44
zyga-ubuntu(talking json)17:44
brunosferzyga-ubuntu: sudo snap discord -r 0.0.2 ? Would be something like this?17:56
* Chipaca wraps up his day, at least for now17:58
zyga-ubuntubrunosfer: no, revisions are always integers18:02
zyga-ubuntubrunosfer: this looks like a version18:02
zyga-ubuntubrunosfer: try snap list --all18:02
zyga-ubuntubrunosfer: you will see various revisions of each snap on your system18:03
zyga-ubuntubrunosfer: again, unless you had a revision you want to go to, you cannot do that18:03
zyga-ubuntubrunosfer: only the owner of that snap can18:03
zyga-ubuntubrunosfer: snaps should have sensibly defined channels and not rely on their users pinning a specific revision18:03
brunosferzyga-ubuntu: Thanks, for clarifying. I want to go to the revision 32, how can I switch to an older revision? Because I have tried the -r flag and it didn't work.18:10
zyga-ubuntubrunosfer: do you have that revision on your system (snap list --all)18:10
brunosferzyga-ubuntu: Yes18:11
brunosferzyga-ubuntu: discord          0.0.3        41    snapcrafters  -18:11
brunosferdiscord          0.0.2        32    snapcrafters  disabled18:11
brunosferdiscord          0.0.3        38    snapcrafters  disabled18:11
brunosferzyga-ubuntu: I want to switch to the revision 3218:11
zyga-ubuntusnap refresh discord -r 32 OR snap revert discord18:11
zyga-ubunturefresh will go there but will keep updating18:11
zyga-ubuntuand revert will skip 3818:11
zyga-ubuntuAFAIK18:11
brunosferzyga-ubuntu: Thanks, I was using the switch for that. Now that you explained it makes indeed more sense to use the refresh to a specific revision. Thank ;)18:13
brunosferzyga-ubuntu: It's giving me the error: unknown flag 'r'18:14
brunosferzyga-ubuntu: It's working... no '-' was needed... just the 'r' as a flag.18:15
ogra_that sounds a bit buggy18:17
zyga-ubuntumaybe try --revision18:17
ogra_short options should use a -18:17
brunosferzyga-ubuntu: sudo snap refresh discord --revision=5018:18
brunosferzyga-ubuntu: it works like this... With the short option doesn't work.18:19
ogra_ah, the --help also doesnt list any short options at all18:19
zyga-ubuntusorry it must have been my rusty memory then18:28
* zyga-ubuntu still debugs one issue18:28
=== mwhudson_ is now known as mwhudson
kyrofaelopio, if you feel like taking circle ci for a spin: https://github.com/canonical-websites/tutorials.ubuntu.com/pull/61821:32
kyrofaHey niemeyer, are you around today? Or are you still out on vacation?21:33
kyrofaOh, back today, it seems. Okay, I'll catch you tomorrow then :)21:35
kyrofaHey there cratliff, good to see you around21:42
cratliffHey, yeah, the holidays can keep you busy sometimes.21:44
mupPR snapcraft#1847 closed: lxd: Use user in container when mounting remote via sshfs <Created by kalikiana> <Merged by kyrofa> <https://github.com/snapcore/snapcraft/pull/1847>21:56
kyrofaBoy no kidding22:16
niemeyerkyrofa: I'm fully back already23:06

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