=== sergiusens_ is now known as sergiusens
[03:54] <zyga> Good morning!
[03:55] <zyga> I’m heading to Flock
[03:55] <zyga> Have a great day everyone, I will be partially offline until I arrive at the conference
[03:55] <zyga> Pharaoh_Atem: I solved the hang in “info”
[03:56] <zyga> You have to install “filesystem”first, then subsequent installation of info and anything else works fine
[04:57]  * zyga straps in his seat
[04:57] <zyga> See you in Frankfurt :-)
[05:08] <mborzecki> morning
[06:43] <zyga> Good day from Frankfurt
[06:44] <zyga> Hey mborzecki, mvo asked to say he will be back at around 10:30,
[06:44] <mborzecki> zyga: hey, safe travels :P
[06:44] <mborzecki> zyga: sure, do you know if cachio has updated arch images yday?
[06:46] <zyga> I don’t know about that, sorry
[06:47] <mborzecki> zyga: how was your flight to fra?
[06:48] <zyga> Short :-)
[06:48] <zyga> About an hour and a half
[06:48] <mborzecki> hehe
[06:48] <zyga> Now some time for breakfast and then onwards to Dresden
[06:48] <mborzecki> zyga: is there no train you could take from waw?
[06:50] <zyga> Yeah, 9 hrs
[06:50] <zyga> I wanted to for a moment
[06:50] <zyga> But then again 9 hours and much mi
[06:51] <zyga> Much more expensive
[07:00] <mborzecki> zyga: heh ;) trains, anyways hope you have a great time there and lots of interesting f2f talks
=== pstolowski|afk is now known as pstolowski
[07:17] <pstolowski> mornings
[07:18] <mborzecki> wow, binutils on arch is borked atm, making valgrind failing with most peculiar way https://paste.fedoraproject.org/paste/p4z3kuDHXR5nZ~cMg99XRg/raw
[07:18] <mborzecki> pstolowski: heya
[07:25] <zyga> Hey Paweł:-)
[07:29] <pstolowski> zyga: train more expensive? surprised
[07:39] <ondra> zyga hey
[07:41] <ondra> zyga dunno if you had time, but I hit yesterday with two machines "snap-update-ns failed with code 1" error
[07:41] <ondra> zyga seems to be related to layout
[07:44] <zyga> No, ondra I didn’t have any time yet. I’m making demo snaps and flocking this week
[07:45] <zyga> Maybe ask Maciej and Paweł for help
[07:45] <ondra> zyga yeah, though to give you head up as you are layout master :)
[07:48] <zyga> Call me “master yoga”
[07:51] <mborzecki> zyga: you plannoning to go on exile? :)
[07:54] <mborzecki> if anyone feels like doing some reviews, https://github.com/snapcore/snapd/pull/5605 snap-device-helper unit tests
[07:56] <zyga> I am heading to Dagobah to balance the force of deb and rpm ;-)
=== tomwardill_ is now known as tomwardill
[08:09] <mborzecki> zyga: feels more like tatooine in this weather :)
[08:11] <Chipaca> buongiorno, principesse
[08:12] <mborzecki> Chipaca: hey
[08:13] <Chipaca> mborzecki: <badly dubbed>jak się masz dzisiaj?
[08:13] <Chipaca> mborzecki: <mouth finishes moving five seconds later>
[08:13] <mborzecki> Chipaca: can practice that in bru
[08:14] <Chipaca> mborzecki: if i get my passport back in time
[08:14] <Chipaca> (hey for all i know it's waiting for me when i get back home) (hah yeah right)
[08:23] <zyga> Chipaca: extra credits for e-ogonek :-)
[08:25] <Chipaca> zyga: ǫǫǫǫǫh̨h̨
=== f4 is now known as Guest43960
[08:55]  * Chipaca liked having an mvo around
[08:57] <Chipaca> :-D
[08:58] <Chipaca> mvo: morning!
[09:00] <pstolowski> mvo: hey, i've addressed your comments to https://github.com/snapcore/snapd/pull/4940 ; it seemed you verbally approved, can you take another look / approve?
[09:00] <pstolowski> mvo: and good morning btw!
[09:01] <zyga> Good morning again mvo
[09:03] <mvo> Chipaca: good morning! and good morning to pstolowski  and zyga
[09:03] <mvo> pstolowski: I have a look in a wee bit
[09:03] <mvo> sorry for being a bit late this morning
[09:03] <pstolowski> mvo: thanks!
[09:04] <Chipaca> mvo: everything a'ight?
[09:05] <mvo> Chipaca: yeah, school started again thats all
[09:05] <mvo> Chipaca: I guess that counts as "no" ;)
[09:05] <Chipaca> mvo: ah! gotcha
[09:05] <Chipaca> mvo: do you guys have more school days, or are your holidays different?
[09:05] <Chipaca> the boys still have another month, here
[09:06] <mvo> Chipaca: I'm not sure, we have 6 weeks in summer
[09:06] <zyga> mvo: how can school start in August?
[09:06] <Chipaca> mvo: and that ended today?
[09:06] <zyga> We still have a month left
[09:06] <mvo> Chipaca: correct
[09:06] <zyga> Ouch :-)
[09:06] <mvo> zyga: it started super early this year, no idea why
[09:06] <Chipaca> zyga: learning in 35C builds character
[09:07] <mvo> zyga: each german "state" has a different schedule so that the autobahn is not congesteted all the same time
[09:07] <zyga> Chipaca: testing in 35C also builds character ;-)
[09:07] <mvo> Chipaca: ha! correct
[09:07] <zyga> S/testing/resting/
[09:07] <Chipaca> zyga: in particular, character U+2668
[09:07] <zyga> Hahahhahaha
[09:07] <mvo> zyga: yeah, this year is very unfortunate timing
[09:07] <mvo> lol
[09:08] <mvo> zyga, Chipaca: how long is summer vac for you guys?
[09:09] <Chipaca> mvo: it varies slightly from place to place, but last week of july to first week of september, ish
[09:09] <Chipaca> mvo: ~6 weeks also I guess
[09:09]  * mvo nods
[09:11] <zyga> Mvo: about 9 weeks
[09:11] <zyga> All of July and August
[09:11] <zyga> And also small parts of June an September
[09:12] <Chipaca> mvo: I don't know if you saw, but systemd-detect-virt uses fscaps in xenial, and we strip xattrs on core, meaning core's systemd-detect-virt might not work properly for users
[09:12] <mvo> zyga: nice
[09:12] <mvo> Chipaca: aha, was that in the forum? or here on irc?
[09:12] <mborzecki> and if you're at universty and don't slack off too much you get 12+ weeks of vacation
[09:12] <Chipaca> mvo: email
[09:13] <zyga> mborzecki: indeed :-)
[09:13] <Chipaca> mvo: (on the 'fscaps for erryone' thread)
[09:13] <mvo> Chipaca: what can we do about it? whitelist systemd-detect-virt from the stipping?
[09:13] <zyga> Transition between high school and uni is very shocking in this regard
[09:13] <Chipaca> mvo: for xenial, figure out if it's a problem first :-)
[09:14] <Chipaca> mvo: I'm only poking you about it because osutil/squashfs/fstype.go has your name all over it
[09:14] <Chipaca> mvo: if that's only used from snapd (i.e. from root), then we don't need to worry at all
[09:14] <mborzecki> zyga: could you https://github.com/snapcore/snapd/pull/5605 ? :)
[09:14] <mvo> aha, good
[09:14] <Chipaca> mvo: oh and errtracker
[09:15] <Chipaca> mvo: for core20, we need to chat with jdstrand at some point, and then plan on how to support this, but there's probably plenty of time :-)
[09:15] <mvo> Chipaca: heh, just like with core18 ;)
[09:15] <mvo> Chipaca: but yeah, sounds like a plan!
[09:15] <Chipaca> (this is assuming it gets the go-ahead, which seems likely)
[09:16] <zyga> mborzecki: can I voice it here? I don’t have network on my laptop
[09:16] <Chipaca> mvo: i forwarded you an email i sent to the list that hasn't made it through, where i outline the things i could think of that needed doing (not in enough detail for us, but for 3rd parties)
[09:16] <mborzecki> zyga: yeah
[09:16] <mvo> Chipaca: cool, thanks for this!
[09:17] <Chipaca> mvo: sometimes i forget to forget to manage
[09:17] <Chipaca> :-)
[09:17] <mvo> Chipaca: heh :)
[09:17] <mvo> Chipaca: we know about your secret identity
[09:18]  * Chipaca hides in shame
[09:18]  * mvo hugs Chipaca 
[09:18]  * Chipaca hugs back
[09:20] <zyga> mborzecki: looks good to me
[09:21] <zyga> Sorry for not doing it there, 2FA + airport
[09:21] <mborzecki> zyga: np
[09:21] <mborzecki> zyga: thanks for reviewing it while at the airport :P
[09:22] <mvo> pstolowski: approved, can I merge it?
[09:26] <pstolowski> mvo: yes, thx!
[09:29] <mvo> pstolowski: congrats, that was in the works for a while, nice to see it landing!
[09:30] <pstolowski> mvo: well, yeah, but it's still just the foundation. anyway, glad to see it landing!
[09:31] <pstolowski> mvo: if you're in the mood of udev-related reviews, this is relatively simple and needs 2nd review - https://github.com/snapcore/snapd/pull/5505
[09:32] <mvo> pstolowski: sounds good, I put it on my list
[09:33] <pstolowski> ty
[09:44] <ogra> ppisati, hmm
[09:44] <ogra> ogra@localhost:~$ ls /snap/pc-kernel/current/
[09:44] <ogra> System.map-4.4.140+  bzImage-4.4.140+  firmware  initrd-4.4.140+.img  initrd.img  kernel.img  meta  modules
[09:45] <ogra> ppisati, when did we stop shipping the config ?
[09:45] <ogra> ppisati, (the pc kernel snaps do not have /proc/config.gz enabled by default either)
[09:49] <mborzecki> pstolowski: thanks for the review of 5605, updates pushed
[10:18] <pstolowski> mborzecki: +1
[10:26] <ppisati> ogra: uhm, i'm not sure
[10:31] <ogra> ppisati, we should have at least one method to get info about the running config ... iirc the arm kernels simply enable IKCONFIG ... we should do that too for the source built ones
[10:31] <ogra> (just by setting it in snapcraft.yaml i think)
[10:35] <ppisati> ogra: kconfigflavour: snapdragon
[10:35] <ppisati> ogra: we use the same config as the packaged kernel
[10:35] <ppisati> ogra: i think the snapcraft kernel plugin doesn't simply copy that file
[10:41] <ogra> yeah
[10:43]  * zyga evacuates
[10:43] <pstolowski> mborzecki: i'm looking at https://github.com/snapcore/snapd/pull/5594 ; i'm probably missing something, but why do we need to create instance-specific env vars and have snap-confine re-create them under old names?
[10:47] <ogra> mvo, hmm, did we regress xdg-open/user-open in core ? i get errors all of a sudden for apps that call xdg-open
[10:47] <ogra> i think this worked yesterday
[10:48] <mvo> ogra: there was a update for core yesterday (if you run stable). can you please try "snap revert core" and see if that fixes it?
[10:48] <ogra> doing ...
[10:48] <mvo> ogra: what core rev are you currently running?
[10:49] <ogra> installed:   16-2.34.3                (5145) 91MB core
[10:49] <ogra> updated yesterday apparently
[10:49] <mborzecki> pstolowski: because we want to make snp instances transparent to applications and pretend it's running as <snap> instead of <snap>_foo, SNAP_NAME, SNAP, SNAP_COMMON and so on environment variables are the same as it was a <snap> (atm those are <snap>_foo)
[10:50] <ogra> hmm
[10:50] <ogra> Uncaught Exception:
[10:50] <ogra> Error: Command failed: xdg-open undefined
[10:50] <ogra> user-open error: no such file or directory
[10:50] <ogra> even after rollback
[10:50] <mborzecki> pstolowski: iow SNAP_INSTANCE_* will reflect <snap>_foo, while the regular SNAP_* will prented as if it's <snap>
[10:50] <ogra> thats weird
[10:50] <mborzecki> pstolowski: and s-c will does some magic to make it happen so :P
[10:52] <pstolowski> mborzecki: aaah ok, i get it now, had to look at the code agin, thanks
[10:54] <ogra> mvo, so checking core, xdg-open is available everywhere ... and has the same content ... looks more like there is an issue with "snapctl user-open" somewhere
[10:56] <ogra> could the desktop side of it be the issue ?
[10:57] <ogra> ogra@acheron:~$ snapctl user-open foo
[10:57] <ogra> user-open error: no such file or directory
[10:57] <ogra> (not sure if you can even call it that way, but the error is the same if i do)
[10:59]  * zyga is still evacuating, veeeery slowly
[11:01] <mborzecki> https://github.com/snapcore/snapd/pull/5607 actual s-d-h with parallel installs
[11:07] <pstolowski> mborzecki: is the revision and version common for all instances of same snap?
[11:08] <mborzecki> pstolowski: no, each instance is separate
[11:17] <pstolowski> mborzecki: right, i misread the code, thanks again
[11:25] <mvo> ogra: hm, hm, I am not familiar with the canpctl user-open side, only xdg-open
=== snowolf is now known as Guest85587
[11:41] <zyga> I’m waiting to rebook my flight
[11:45] <ogra> mborzecki, was it you who worked on the amdgpu support in the opengl interface ?
[11:45] <mborzecki> ogra: nope, i worked on fixing nvidia
[11:45] <ogra> (i had assumed amdgpu is in the standard paths nd wouldnt need special casing like nvidia does)
[11:45] <ogra> ah, ok
[11:45] <ogra> did we have anyone working on amdpu at all ?
[11:46] <ogra> *amdgpu
[11:46] <mborzecki> ogra: looking forward to working on it once the prices drop to a resonable level for those 2 yrs old gpus
[11:47] <mvo> zyga: what happend?
[11:47] <ogra> heh
[11:51] <mborzecki> pstolowski: updated the spread test in https://github.com/snapcore/snapd/pull/5594
[11:52] <pstolowski> ty
[11:52] <mborzecki> pstolowski: if you feel like doing some more reviews, could you take a look at https://github.com/snapcore/snapd/pull/5561 ?
[11:52] <pstolowski> mborzecki: yes, will do
[11:53] <mborzecki> pstolowski: thanks
[11:55] <mborzecki> hmm trying snapcraft on arch, so far the biggest hurdle is lxd setup
[11:59] <mborzecki> lxd has a custom fork of sqlite3 now?
[11:59] <mvo> mborzecki: yes
[11:59] <mvo> mborzecki: with distrubition iirc
[12:01] <mborzecki> mvo: i'm rebuilding it from aur now, used snaps first but lxd init --auto failed setting up bridge iface
[12:03] <mborzecki> cachio: did you manage to sort it out with arch image yesterday?
[12:04] <cachio> mborzecki, hey, yes
[12:04] <cachio> mborzecki, did you see the error again?
[12:05] <mborzecki> cachio: did you update the image or switched to an older one?
[12:05] <mborzecki> cachio: no, no errors today :0
[12:05] <cachio> mborzecki, initially switched to an old one
[12:05] <cachio> then I created a new one
[12:06] <cachio> mborzecki, but basically there was 2 problems
[12:07] <cachio> when I switched to the old image, we had another error as well
[12:08] <mborzecki> cachio: yeah, i think glibc & python was updated yesteday and brought in a bunch of rebuilds
=== pstolowski is now known as pstolowski|lunch
[12:09] <cachio> mborzecki, also the shadow service was failing
=== sergiusens_ is now known as sergiusens
[12:10] <cachio> this was producing the state = degraded
[12:10] <cachio> apart of this, the google compute engine package needed a rebuild
[12:10] <cachio> and also an uninstaller
[12:21] <mvo> cachio: we can blacklist the test on arch too if needed (cc mborzecki) - I mean, if its too hard for arch to boot correctly ;)
[12:21] <cachio> mvo, hehee
[12:21] <mvo> cachio, mborzecki but seriously, I think its fine to backlits until its fixed on the image
[12:21] <cachio> mvo, the image is already fixed
[12:22] <cachio> mvo, I did it yesterday
[12:22] <cachio> mvo, did you see the error today?
[12:23] <mvo> cachio: oh, okay, sorry I think I misread the previous sentences. I (incorrectly) read that its still an issue. if all is fixed just ignore me
[12:23] <cachio> :)
[12:29] <mborzecki> mvo: https://paste.ubuntu.com/p/WzXRzbKDWJ/ the log is empty
[12:29] <Chipaca> mvo: i can confirm the warnings pipeline pr is green because arch is no longer failing that test
[12:29] <Chipaca> fwiw
[12:29] <mvo> mborzecki: hrm, not a lot of log :(
[12:30] <mborzecki> mvo: yeah, whole 2 lines
[12:30] <mvo> Chipaca: cool, thanks for confirming
[12:30] <mvo> mborzecki: :(
=== andyrock_ is now known as andyrock
[12:40] <mborzecki> any clue why tests/main/security-devpts is connecting physical-memory-observe iface?
[12:40] <sergiusens> mvo: added some comments to your PR, I can help out with the mocking if you want
[12:41]  * sergiusens 👋
[12:46] <zyga> Hey, guess what
[12:46] <zyga> A am taking the train after all
[12:46] <zyga> Mvo: trains in Germany are pretty €€€&
[12:46] <mvo> sergiusens: in a meeting right now I check it out after the next meeting
[12:46] <mvo> zyga: yes
[12:46] <mvo> zyga: also late
[12:46] <mvo> zyga: and sometimes very hot
[12:46] <mvo> zyga: but €€€€ as well
[12:47] <zyga> 105€ for Frankfurt nah Dresden
[12:47] <mvo> zyga: woah, yeah - how many hours?
[12:47] <zyga> Nach?
[12:47] <mvo> zyga: from fra -> dresden - how long will you travel
[12:47] <zyga> No idea yet
[12:47] <mvo> zyga: should be 4:15 direct
[12:47] <zyga> ICE 1653
[12:48] <mvo> zyga: which is quite nice
[12:48] <Chipaca> zyga: also they announce them wrong so you get into the one going the wrong way
[12:48] <mvo> zyga: and its on time
[12:48] <mvo> zyga: it should be a very nice train
[12:48] <zyga> Perfect
[12:48] <zyga> Just no luggage :-(
[12:48] <mvo> zyga: uh, what happend at the airport?
[12:49] <mvo> zyga: you should also have wifi on this train
[12:49] <mvo> zyga: fwiw, *if* you know in advance and book the train a couple of days ahead of time you get a discount usually. but I guess this was not planed :/
[12:52] <zyga> T1 was evacuated
[12:52] <zyga> Airport is shut down
[12:52] <zyga> No planes, no luggage
=== pstolowski|lunch is now known as pstolowski
[12:54] <Chipaca> zyga: who farted?
[12:54]  * Chipaca ever the professional
[12:55] <zyga> Well
[12:55] <zyga> Rolls eyes
[13:32] <ogra> Chipaca, am i reading that right, you are establishing professional farting ?
[13:33] <ogra> zyga, enjoy frankfurt then :/
[13:50] <mborzecki> jdstrand: should we enforce that appname as passed to snap-device-helper has a snap_ prefix?
[13:51] <jdstrand> mborzecki: yes, definitely
[13:51] <mborzecki> jdstrand: ack
[13:51] <jdstrand> mborzecki: well, put another way. we should not remove snap_. it would be nice to have a little check in there to enforce it
[13:52] <jdstrand> we don't enforce it now, but we should
[13:53] <mborzecki> jdstrand: btw. any clue why snap-device-helper exits with 0 if maj:min is not passed?
[13:59] <jdstrand> mborzecki: that was in the original implementation. I think with the way the tagging works, udev might call out to it for specific operations which aren't an error condition, but we'd like to ignore
[13:59] <zyga> mvo: od the Core 18 meeting IP?
[13:59] <zyga> Up
[13:59] <zyga> As in are we doing it
[13:59] <jdstrand> mborzecki: I don't remember the details otoh. mvo *may* (it was included in his first commit, but we're talking 3+ years ago)
[13:59] <mborzecki> jdstrand: fair enough, i've accounted for that in the test
[14:10] <cachio> mvo, error: cannot download snap "pc-kernel=18": snap not found
[14:11] <cachio> any idea what happened with the kernel snap?
[14:51] <mvo> cachio: please make sure your core snap is coming from the "edge" channel
[14:52] <cachio> mvo, sorry, I refreshed from stable yesterday :)
[14:52] <cachio> to test the new core in stable
[14:52] <mvo> zyga: the Core18 meeting did not happen, the most relevant people are on vac
[14:53] <mvo> cachio: no worries
[14:53] <mvo> cachio: we need to make sure this code lands in beta and candidate etc soon :)
[14:53] <mvo> cachio: its a useful reminder
[14:54] <cachio> mvo, yes, thanks for that, building image now
[14:56] <mvo> cachio: good luck
[14:58] <kenvandine> In doing a dist-upgrade on 18.04, the update hung and i see this in the journal
[14:58] <kenvandine> https://paste.ubuntu.com/p/7CqFfDts7P/
=== jamespage is now known as JamesPage
[14:58] <kenvandine> parse error in a yaml
[14:58] <kenvandine> maybe the seed.yaml got messed up during the dist-upgrade and is blocking restarting snapd?
[14:59] <kyrofa> Hey mvo, adding fuse to our debian/tests/control allowed us to get further, but it really just changed the error: https://pastebin.ubuntu.com/p/pVtNGPnfpq/ . Any thoughts?
=== stevoo is now known as Guest49739
[15:00] <mvo> kenvandine: could you pastebin the seed.yaml and also the timestamp of the seed file?
[15:00] <kenvandine> https://paste.ubuntu.com/p/zZKCmSGFyT/
[15:00] <mvo> kenvandine: did you dist-upgrade form 16.04 -> 18.04 or was that a 18.04->18.04 upgrade?
[15:00] <kenvandine> that's the last couple lines of stdout during the dist-upgrade
[15:00] <kenvandine> 18.04->18.04
[15:01] <mvo> kenvandine: what do you see with snap changes?
[15:01] <kenvandine> error: no changes found
[15:01] <sergiusens> kenvandine: looks like broken yaml
[15:01] <mvo> kyrofa: hm, this tricky, this is running the snapd tests inside an lxd container?
[15:02] <kyrofa> mvo, just installing a snap is all
[15:02] <mvo> kyrofa: what security is selected for this container, I remember an issue about it, let me see if I can find details
[15:02] <kyrofa> mvo, I'm not sure, autopkgtest is a bit of a black box to me
[15:02] <mvo> kyrofa: yeah, depending on the configuration of the container this might not work because of apparmor
[15:03] <mvo> kyrofa: also, what version of ubuntu is the host running?
=== JamesPage is now known as jamespage
[15:03] <kenvandine> mvo, http://paste.ubuntu.com/p/ssxXhh5R5R/
[15:03] <kyrofa> mvo, also no idea, I'm afraid. We can hope back to ubuntu-devel to discuss
[15:03] <sergiusens> mvo: echo -e of kenvandine's output http://paste.ubuntu.com/p/MPXRpW3Xb2/
[15:03] <mvo> kyrofa: let me try to find the relevant forum topic
[15:03] <mvo> sergiusens: heh, thank you
[15:05] <mvo> kenvandine: it looks like there is a single "gnome-3-26-1604_64.snap" in the middle of the yaml
[15:05] <mvo> kenvandine: at line 51 of the pastebin
[15:05] <mvo> kenvandine: aha, multiple ones - at line 30 as well
[15:06] <mvo> kenvandine: I'm not aware of snapd writing to this file except when it is used with "snap prepare-image". is that something one of the distro tools are doing? also seeding should only happen if there is no /var/lib/snapd/state.json
[15:09] <sergiusens> kyrofa: finally happy with the snap injection thing
[15:09] <kenvandine> mvo, no idea :)
[15:10] <mvo> kenvandine: what is the mtime of this file?
[15:10] <sergiusens> going to send out a link your way for overview before I chore down on the endless list of unit tests this might require
[15:10] <kenvandine> looks like it's appending
[15:10] <mvo> kenvandine: can you grep for "seed.yaml" in /var/lib/dpkg/info/*.{post,pre}inst ?
[15:11] <kenvandine> mvo, nothing
[15:11] <kenvandine> so maybe this was there before
[15:11] <kyrofa> sergiusens, awesome
[15:13] <mvo> kenvandine: what do you see in "snap changes"?
[15:14] <kenvandine> error: no changes found
[15:14] <kenvandine> mvo, but.. i just re-crafted the seed.yaml file
[15:14] <kenvandine> and restarted snapd
[15:15] <mvo> kenvandine: ok, with that it should be seeding now
[15:15] <mvo> kenvandine: would love to know where the corrupted file came from
[15:15] <kenvandine> and now snap changes says lists a couple initializing
[15:15] <kenvandine> mvo, well.. could be my fault :)
[15:15] <kenvandine> this was a test image from the desktop-preinstalled work we did with microsoft :)
[15:15] <kenvandine> the hyper-v image
[15:18] <mvo> kyrofa: I talked to zyga and I think the issue is that when lxd is run as a privileged container and it is restricted further with apparmor the snapd assumptions about what it can do do not work. I don't think there is anything on our side we can do unfortunately
[15:18] <mvo> kenvandine: ok
[15:19] <mvo> kenvandine: good luck in any case
[15:19] <kyrofa> mvo, so you think this is a privileged container?
[15:19] <mvo> kyrofa: its my best guess so far
[15:20] <kyrofa> That would surprise me, but I'll ask
[15:21] <mvo> kyrofa: the error looks a bit like this: Permission denied; attempted to load a profile while confined?
[15:21] <mvo> )
[15:21] <kyrofa> (just given how locked down these things tend to be)
[15:21] <mvo> kyrofa: this looks like there is a restricting profile around the container already
[15:22] <mvo> kyrofa: fwiw, we do not run our autopkgtests tests inside containers. we do test basic lxd support by installing snaps in the default lxd container though
[15:22] <kyrofa> mvo, yeah, we have a test suite to make sure we can build snaps and they run as expected, and they work everywhere except armhf! Haha
[15:23] <kyrofa> mvo, interesting observation, let's see what steve says. I wish this wasn't all so opaque
[15:26] <mvo> kyrofa: yeah, sorry
[15:26] <mvo> kyrofa: quick question about snapcraft - I have a testfialure "would reformat /root/snapcraft/snapcraft/plugins/go.py" what re-format tool do you use ?
[15:27] <mvo> kyrofa: i.e. what should I run?
[15:27] <mvo> kyrofa: to fix it
[15:39] <sergiusens> kyrofa: https://github.com/snapcore/snapcraft/commit/68506c11c81fdcffc783ddfdf10b5692651d6d8c
[15:40] <sergiusens> mvo snap install black --edge --devmode; black .
[15:40] <mvo> sergiusens: ta
[15:41] <sergiusens> mvo: we took the gofmt route for python, a nice addition to end useless discussions
[15:41] <mvo> sergiusens: thanks, updated the PR based on your latest suggestion, but no new mocks
[15:41] <mvo> sergiusens: yeah, I'm a huge fan (now) of auto code format
[15:42] <mvo> sergiusens: I just was not sure what tool I have to use
[15:42] <sergiusens> I can add the mocks
[15:42] <mvo> sergiusens: that would be lovely if you don't mind
[15:42] <sergiusens> indeed, I don't agree with the formatting a 100%, but it is just a matter of getting used to
[15:43] <mvo> sergiusens: yeah, the diff looks a bit unusual (just did the reformat) but then its fine, consistency++
[15:45] <sergiusens> the site explains how it reformats to minimize future diffs (or make them more obvious)
[16:11] <mvo> pstolowski: I have some feedback in 5505 - looks good some ideas in the PR, I will likely play around with it some more after dinner
[16:12] <pstolowski> mvo: ty!
=== pstolowski is now known as pstolowski|afk
[16:45] <mvo> pstolowski|afk: sorry, I got a bit carried away. here is my ideas around the parsing, we can leverage the go scanner to make the scanning more tailored to us: http://paste.ubuntu.com/p/5BPDSjTSK9/ (the diff http://paste.ubuntu.com/p/pPB5sfJxHP/)
[17:11] <cachio> mvo, core18 getting stuck https://paste.ubuntu.com/p/Yv7ZpKzQHT/
[17:12] <cachio> mvo, both 1md64 nd i386
[17:12] <cachio> it is starting
[17:13] <cachio> mvo, this is the full outputhttps://paste.ubuntu.com/p/v8qB25DXGg/
[17:13] <cachio> https://paste.ubuntu.com/p/v8qB25DXGg/
[17:14] <mvo> cachio: looks like entropy
[17:15] <mvo> cachio: is that spread?
[17:15] <cachio> mvo, no, I just started kvm with the core18 image
[17:15] <cachio> this is the output
[17:17] <mvo> cachio: try to enter some keys
[17:17] <mvo> cachio: in the console
[17:17] <mvo> just type random stuff
[17:18] <cachio> nothing happensw
[17:18] <mvo> cachio: do you see the keys echoed in the terminal?
[17:18] <mvo> cachio: this is probably https://launchpad.net/ubuntu/+source/util-linux/2.31.1-0.4ubuntu3.2
[17:19] <mvo> cachio: it usually works when pressing keys a bunch of times, then at some point "crng initialized" is printed
[17:19] <cachio> mvo, I'll try it
[17:20] <cachio> I already have it installed
[17:21] <cachio> mvo, same command line to create the vm?
[17:28] <mvo> cachio: getting the fix is non-trivial unfortunately, the initrd in the kernel snaps needs an update
[17:29] <mvo> cachio: so you need to mount the image, then unpack the squashfs, then unpack the initrd, then cp the fixed libuuid.so.... into the initrd, repack that, repack the snap, run the image
[17:30] <cachio> mvo, do we have the libuuid.so already fixed?
[17:30] <mvo> cachio: yes, its in the package of util-linux in bionic-prposed
[17:31] <cachio> mvo, ah, ok
[17:36] <mvo> cachio: you can extract it from the deb via e.g. dpkg-deb -x
[17:37] <cachio> mvo, ok
[17:39] <mvo> cachio: good luck! if you are successful please add it to the bug that this got validated on core18
[17:44] <cachio> mvo, sure, thanks for the support
[17:45] <mvo> cachio: yw, sorry that its so bumpy still
=== jkridner|pd is now known as jkridner
[19:17] <zyga> Hey
[19:17] <zyga> I just arrived
[19:17] <zyga> 7:10->21:17
[19:18] <zyga> ENOLUGGAGE