[05:00] <zyga> Good morning
[05:08] <mborzecki> morning
[05:45] <zyga> Hi
[05:46] <mborzecki> zyga: hey
[05:46] <mvo> zyga: hey ! how if flock?
[05:46] <mvo> hey mborzecki
[05:47] <mborzecki> mvo: mornings
[05:47] <mborzecki> zyga: yeah, how's flock? you're gonna miss the morning yoga class
[05:50] <zyga> So far things are very hot because not much a/c
[05:50] <zyga> I was drying my clothing ;-)
[05:51] <zyga> How are things
[05:51] <zyga> When is the next release?
[05:55] <mvo> zyga: beta this week I think
[06:56] <mborzecki> hmm running into some problems with snapd under lxd on arch (quite a combo)
[06:56] <mborzecki> snapd actually works again after i made the container privileged, but i see an odd issue with reloading udev rules
[07:01] <mborzecki> https://paste.ubuntu.com/p/xpK7vgfsMG/
[07:02] <zyga> Hey mvo
[07:02] <zyga> Flock is just starting
[07:02] <zyga> Looking forward to the release
[07:02] <mborzecki> zyga: good luck :)
[07:03] <pstolowski> morning
[07:03] <mvo> zyga: cool, yeah, looking over the open PRs right now
[07:03] <mvo> pstolowski: hey, good morning
[07:10] <mborzecki> so udevadm control --reload-rules fails with status 2, but no output
[07:24] <mvo> pstolowski: not sure if you got my message from yesterday, I got a bit carried away when reviewing the udevadm output parser. hope its ok
[07:24] <pstolowski> mvo: yes! thanks for the review and for playing with it! i'm on it
[07:34] <mvo> pstolowski: I really like the go scanner customization possiblities, its pretty simpel but quite powerful at the same time
[07:35] <mvo> pstolowski: anyway, happy that you find it interessting
[07:38] <mborzecki> and installing any snap that triggers udev rule reload fails too
[08:04] <mborzecki> mvo: could you take a look at https://forum.snapcraft.io/t/error-cannot-assert-container-build-on-arch-linux-fails/6655/7 ? who would know more about udev & lxc?
[08:07] <mvo> mborzecki: sure, looking
[08:20] <pstolowski> mvo: addressed your feedback to #5505
[08:37] <mvo> pstolowski: thank you! this looks great, I went over it in full again and added some more small ideas but feel free to ignore
[08:43] <mborzecki> something wrong with travis job queue? builds seem to be stuck
[08:54] <pstolowski> mvo: thanks again; updated
[09:03] <mvo> pstolowski: very nice! thank you. lets merge it once its green
[09:05] <pstolowski> yay
[09:20] <mvo> pstolowski: nice job, lots is landing right now
[09:23] <mborzecki> there's also a bunch of snapcraft jobs queued up so there's that :)
[09:29]  * Son_Goku waves
[10:10] <mthaddon> popey: who would be right person to ask for a review of https://github.com/snapcrafters/sentry/pull/8/files ?
[10:14] <Chipaca> mvo: https://errors.ubuntu.com/?release=Ubuntu%2016.04&period=day <-fun
[10:20] <zyga> mborzecki: hey, is instance work something that is ready to be demonstrated?
[10:22] <mborzecki> zyga: maybe, you can grab it here https://github.com/snapcore/snapd/pull/5596 , some caveats though, you can install only one snap from the store using _<foo> name, but you can snap install --dangerous --name snap_foo as many as you like
[10:22] <zyga> That is ok
[10:22] <mborzecki> zyga: things may be rough aroudn the edges, but installing, removing, running should work
[10:22] <zyga> I plan to do locally built demos
[10:22] <zyga> Thanks
[10:22] <mborzecki> zyga: ping me when you need help
[10:27] <zyga> Thank you
[10:32] <mvo> Chipaca: uh, all  ERROR [daemon-reload] failed with exit status 1: Failed to execute operation: Connection timed out ?
[10:32] <mvo> Chipaca: i.e. have you looked at the details yet?
[10:32] <mvo> Chipaca: thats the stable core refresh interacting badly with the amazon linux agent?
[10:32] <Chipaca> mvo: the ones I looked at, the syslog seemed bad
[10:32] <ppisati> sergiusens: i'm not a python expert, but i can't install black on my xenial box
[10:33] <ppisati> https://pastebin.ubuntu.com/p/wnvmdp8HRq/
[10:33] <ppisati> if i pip search, i can see it, but i'm unable to install it
[10:33] <Chipaca> mvo: but, yes, all amazon-ssm-agent
[10:33] <ppisati> is it beacuse it requires python 3.6.0+?
[10:33] <mvo> Chipaca: any hints what goes on that triggers the bug?
[10:34] <ppisati> sergiusens: but then we are implicitly requiring python 3.6.0+ for the entire snapcraft project then
[10:35] <Chipaca> mvo: no
[10:35] <mvo> Chipaca: hm, the random one I just looked at has "Aug 08 10:23:53 ip-10-0-136-110 kernel: INFO: task setfont:701 blocked for more than 120 seconds."
[10:35] <mvo> Chipaca: within a kernel oops
[10:35] <Chipaca> mvo: same in all the ones i saw
[10:36] <ppisati> yep, my feeling is that we moved the requirement to 3.6.x:
[10:36] <ppisati>  python3-dev | 3.5.1-3          | xenial          | amd64, arm64, armhf, i386, powerpc, ppc64el, s390x
[10:36] <ppisati>  python3-dev | 3.6.5-3          | bionic          | amd64, arm64, armhf, i386, ppc64el, s390x
[10:37] <mvo> Chipaca: very strange, I wonder what is going on there
[11:09] <popey> mthaddon: sorry, missed the ping. me, now.
[11:11] <cachio> mvo, hey, yesterday I tried to mount initrd but I couldn't
[11:11] <zyga> Hey hey
[11:12] <zyga> Still alive and kicking
[11:12] <zyga> Some interesting observations coming from Flock
[11:12] <zyga> Some plenaries left, them more individual sessions
[11:12] <cachio> mvo, https://paste.ubuntu.com/p/tpqnJW5VVD/
[11:17] <mthaddon> popey: fantastic, thanks
[11:42] <Chipaca> cachio: i thought you couldn't mount initrd
[11:42] <cachio> Chipaca, yes, I couldn't
[11:42] <cachio> Chipaca, any idea how to do it?
[11:43] <Chipaca> cachio: what does ‘file /home/sergio/test/lab/kernel/initrd.img’ say?
[11:44] <cachio> -rw-r--r-- 1 root root 9684891 jul 31 08:45 initrd.img
[11:44] <cachio> Chipaca, which info do you want?
[11:45] <Chipaca> cachio: the output of ‘file /home/sergio/test/lab/kernel/initrd.img’ :-)
[11:45] <Chipaca> cachio: ‘file’ is a command
[11:45] <cachio> Chipaca, hehe, sorry, /home/sergio/test/lab/kernel/initrd.img: ASCII cpio archive (SVR4 with no CRC
[11:46] <cachio> yes, I read fast and did not understand it
[11:46] <om26er> popey: ping https://github.com/snapcrafters/android-studio/pull/32
[11:47] <popey> om26er: merged :)
[11:47] <Chipaca> cachio: so, ‘cpio -t < /home/sergio/test/lab/kernel/initrd.img’ to list it, ‘cpio -x < /home/sergio/test/lab/kernel/initrd.img’ to extract it, etc
[11:47] <Chipaca> cachio: (man cpio)
[11:47] <cachio> Chipaca, tx
[11:47] <cachio> I'll try it
[11:47] <om26er> popey: thanks, need your eyes on https://github.com/snapcrafters/android-studio/pull/28 as well, that automates releases of android studio
[11:48] <Chipaca> cachio: mvo: if there's a way to _mount_ initrd, I don't know it
[11:48] <Chipaca> cachio: if you have 'mc' installed, you can rename it to foo.cpio and navigate it with that
[11:48] <Chipaca> cachio: or with gvfs (e.g. nautilus)
[11:49] <Chipaca> ah
[11:49] <Chipaca> cachio: you can mount it with gvfs, of course
[11:49] <cachio> Chipaca,  I am trying to extract it , replace a file and pack it again
[11:56] <Chipaca> cachio: mounting it with gvfs won't help because  it doesn't support writing  to it
[11:57] <cachio> Chipaca, I am trying to replace libuuid.so but I can't find it
[11:57] <cachio> it is not indice the initrd.img
[11:59] <Chipaca> cachio: not the .so on its own, just the .so.1 and .so.1.3.0
[11:59] <Chipaca> (at least in the one i have here)
[12:00] <cachio> libuuid.so.1
[12:00] <Chipaca> cachio: that'll be a symlink to the .1.3.0
[12:01] <cachio> Chipaca, but I dont have any
[12:01] <Chipaca> cachio: where is this initrd from?
[12:02] <cachio> Chipaca, it is from the core-18 image for amd64
[12:02] <Chipaca> cachio: the one on people.canonical.com?
[12:03]  * Chipaca downloads that
[12:03] <cachio> Chipaca, no, I built it by using ubuntu-image
[12:03] <Chipaca> cachio: ok, i'll look at the one on p.c.c first
[12:03] <Chipaca> :-)
[12:03] <cachio> Chipaca, I think I'll need to use it as well
[12:10] <mborzecki> pstolowski|lunch: Chipaca: updated https://github.com/snapcore/snapd/pull/5561
[12:10] <mborzecki> that's one annoying PR there :)
[12:15] <sergiusens> ppisati: snap install black --edge --devmode
[12:16] <sergiusens> ppisati: btw, mind taking a look https://github.com/snapcore/snapcraft/pull/2202 ?
[12:43] <pstolowski> hmm what's ogoing on with travis.. still struggling?
[12:46] <sergiusens> ppisati: and no,we still require xenial, it is just a tool we depend on that requires a newer python, so it has been snapped, the hacking docs have been updated to reflect that too
[12:48] <ppisati> sergiusens: the github page for black said it required 3.6.0+, hence my assumption
[12:49] <ppisati> sergiusens: another question - after i git clone the snapcraft repo, nothing happens if i invoke bin/snapcraft
[12:49] <ppisati> sergiusens: sergiusens i mean, i don't get any output
[12:52] <ogra> it probably prints black on black, change the terminal bgcolor :P
[12:53] <ppisati> ogra: :(
[13:00] <Chipaca> ppisati: did you read HACKING.md, about using venv?
[13:01] <ppisati> Chipaca: yep
[13:01] <ppisati> Chipaca: i'm in venv
[13:08] <Chipaca> ppisati: no output at all, but it just returns? or does it hang?
[13:09] <ppisati> Chipaca: https://pastebin.ubuntu.com/p/tZbytBjtG7/
[13:36] <mvo> cachio: let me look at this initrd now in core18
[13:36] <Chipaca> sergiusens: hola
[13:36] <Chipaca> sergiusens: https://pastebin.ubuntu.com/p/tZbytBjtG7/ <- ppisati hates you
[13:37]  * Chipaca throws everybody under the bus
[13:37] <sergiusens> ppisati: pip install -e .
[13:37] <cachio> mvo, sure
[13:38] <cachio> mvo, I checked in the initrd inside the kernel
[13:38] <sergiusens> Chipaca: yeah, we changed this back then when we decided to support snapcraftctl IIRC. I do not know why we have that bin file still
[13:38] <cachio> mvo, which is inside the core 18 image
[13:38] <sergiusens> kyrofa: do you recall?
[13:39] <mthaddon> popey: thanks for the review. What would be the schedule for publishing an updated snap for that?
[13:40] <ppisati> sergiusens: oh ok, it took the working snapcraft directory, made a pip package and installed it
[13:41] <sergiusens> ppisati: yeah, you can easily work in editing mode by doing "pip install -e ."
[13:42] <ppisati> sergiusens: so if i modify the src code, and i invoke snapcraft, it'll invoke my modified src code - i guess that's the meaning of editing mode
[13:42] <sergiusens> ppisati: exactly
[13:45] <ppisati> sergiusens: ok, i have all i need now, thanls
[13:45] <ppisati> *thanks
 cachio, Chipaca aha, I remember now what the issue is/was with your initramfs - the kernel now concats multiple ones after each other but cpio will only "see" the first one in this mode. this is why it looked so tiny probably
 cachio: this makes working with it even more of a PITA of course
[13:58] <mvo> (sorry got disconnected)
[14:00] <cachio> mvo, ahhh
[14:01] <cachio> mvo, are you going to fix that?
[14:01] <cachio> mvo, or how should I make to extract the correct initramtd
[14:02] <cachio> initrd
[14:02] <Chipaca> mvo: what can I milestone #5613 to?
[14:03] <mvo> cachio: I'm on it right now
[14:03] <mvo> cachio: half way there (hopefully)
[14:04] <mvo> Chipaca: yes please
[14:04] <cachio> mvo, great, thanks
[14:05] <Chipaca> mvo: wat
[14:06] <mvo> Chipaca: you mean wat about the multiple initrds?
[14:06] <mvo> Chipaca: or a different "wat"?
[14:07] <Chipaca> mvo: no i mean: "what can I milestone #5613 to?" "yes"
[14:07] <mvo> Chipaca: I set the milestone to 2.35 now, hope thats ok
[14:07] <Chipaca> mvo: yes :-)
[14:07] <mvo> Chipaca: I hope we won't need another 2.34
[14:08] <mvo> *fingers crossed*
[14:08] <Chipaca> mvo: I just wanted to know what to target it to :-) sorry for the confusion
[14:08] <mvo> Chipaca: no worries, its still very hot :)
[14:09] <mvo> Chipaca: also multiple initrds inside squashfs inside an image make my head spin a little
[14:09] <mvo> Chipaca: but I think I got it under control now
[14:09] <Chipaca> mvo: https://en.wikipedia.org/wiki/Yo-yo_de-spin
[14:10] <popey> mthaddon: actually the build failed.. https://build.snapcraft.io/user/snapcrafters/sentry / https://launchpad.net/~build.snapcraft.io/+snap/17fc91e19f932bd8a75175923b533019-xenial/+build/296424
[14:10] <mvo> Chipaca: woah
[14:11] <Chipaca> mvo: next time you need to look at multiple initrds inside suqashfs inside an image, grab two yo-yos
[14:11] <Chipaca> :-)
[14:12] <popey> I learn so much useful stuff via this channel :)
[14:14] <ogra> mvo, just use multiple initramfs lines in grub.cfg
[14:15] <ogra> ... now i scared him
[14:15] <popey> om26er: will add the android studio pr to the to-do list, thanks
[14:16] <Chipaca> mvo: when does 2.35 close?
[14:18] <mvo> Chipaca: the first pre-image today but there is no reaoson not to cherry-pick selected PRs
[14:18] <mvo> Chipaca: especially since it looks like travis is rather busy currently
[14:18] <Chipaca> heh
[14:18] <mvo> cachio: http://people.canonical.com/~mvo/tmp/core18-amd64-18-alpha20180803-with-lp1783810.img.xz
[14:18] <mvo> cachio: that seems to be working for me
[14:19] <mvo> cachio: I replaced the initramfs there
[14:19] <cachio> mvo, excelent, thanks
[14:27] <mvo> meh, network is a bit unreliable today
 cachio: if it works for you, please mark 1783810 as verified
[14:27] <mvo> cachio: did you write anything after this?
[14:27] <ogra> that didnt even get through
[14:28] <mvo> ogra: heh, thanks
[14:29] <cachio> mvo, it is working now
[14:29] <cachio> it gets stuck like 2 seconds and then it continues
[14:29] <mvo> cachio: with the updated image?
[14:29] <cachio> mvo, yes
[14:30] <mvo> cachio: great
[14:31] <cachio> mvo, but it is taking so long to contact the store
[14:31] <mvo> cachio: I think we can mark the bug as sru-validated then
[14:31] <cachio> it is trying to create the user
[14:31] <mvo> cachio: meh, this delay is probably real entropy :/
[14:31] <mvo> cachio: I mean, for the store we need real entropy afaik
[14:32] <mvo> cachio: we may need to investigate solutions like polinate
[14:32] <cachio> mvo, it restarted and I ran console conf again
[14:32] <cachio> and it created the user
[14:32] <mvo> ok
[14:37] <cachio> mvo, still https://paste.ubuntu.com/p/vfCr3yw836/
[14:39] <mvo> cachio: did you refresh core18 and the other bits from edge?
[14:39] <mvo> cachio: i.e. please run "sudo snap refresh --edge core18"
[14:45] <cachio> mvo, in progress
[14:46] <mvo> cachio: ta
[14:53]  * Chipaca takes a break
[15:03] <kyrofa> sergio doesn't seem to be around, but Chipaca, ppisati that file is only for Windows packaging. bin/snapcraftctl is what was needed for snapcraftctl
[15:03] <kyrofa> If you want to run snapcraft from source, install it into a venv
[15:04] <cachio> mvo, after refresh core18
[15:04] <cachio> the system reboots
[15:04] <cachio> but in the console I don't see the reboot
[15:04] <mvo> cachio: no reboot message there? hm, hm
[15:04] <cachio> and I can't connect to the vm anymore
[15:05] <mvo> cachio: anything in the terminal?
[15:05]  * mvo tries to reproduce
[15:05] <cachio> well, It did it
[15:05] <cachio> but took much more than usual
[15:07] <cachio> mvo, currently running the tests using external
[15:07] <cachio> mvo, let's see how it goes
[15:07] <zyga> kyrofa: hey
[15:08] <zyga> kyrofa: how do I upload a snap snans snapcraft?
[15:08] <cachio> mvo, it is so weird how it did the reboot
[15:08] <zyga> or how do I tell snapcraft to upload a snap it did not build
[15:08] <mvo> cachio: hm, the image may be problematic
[15:08] <mvo> cachio: because the kernel snap is modified the seeding may not work
[15:08] <kyrofa> zyga, you can't anymore, store removed that capability
[15:08] <cachio> mvo, in parallel i'll continue doing manual test for this image
[15:08] <kyrofa> ... I think
[15:09] <kyrofa> Yeah, looks like it
[15:09] <zyga> kyrofa: what do I need to do to upload a snap that snapcraft did not build
[15:09] <zyga> kyrofa: I can share the makefile I use
[15:09] <kyrofa> zyga, you can still use snapcraft to push it
[15:09] <zyga> nope, I tried
[15:09] <zyga> it crashes
[15:09] <kyrofa> How so?
[15:09] <zyga> boom https://www.irccloud.com/pastebin/Kbk2VkV1/
[15:10] <zyga> not sure why it wants to remove anything
[15:10] <zyga> or why it cares
[15:10] <zyga> I gave it a snap.yaml
[15:10] <zyga> er
[15:10] <zyga> a *.snap file
[15:10] <kyrofa> zyga, it needs to know the snap name, so it unpacks the meta/snap.yaml
[15:10] <zyga> there is no snapcraft.yaml in the tree
[15:10] <zyga> ok
[15:10] <kyrofa> But permissions seem odd. How did you create this snap?
[15:11] <zyga> cat Makefile https://www.irccloud.com/pastebin/hdHBMAuP/
[15:11] <zyga> tip: this requires fedora to run
[15:11] <zyga> or dnf that you don't have on ubuntu to be precise
[15:11] <zyga> note that I even use a "prime" directory
[15:11] <zyga> [zyga@faroe fedora29]$ ls -ld prime/meta/snap.yaml
[15:11] <zyga> -rw-r--r--. 1 root root 1297 Aug  8 17:08 prime/meta/snap.yaml
[15:12] <zyga> the snap.yaml is
[15:12] <zyga> cat snap.yaml https://www.irccloud.com/pastebin/6IJSmdR6/
[15:13] <kyrofa> zyga, huh, can you share that snap with me?
[15:13] <zyga> sure
[15:14] <zyga> any ideas how
[15:14] <zyga> there was that thing for sharing files
[15:14] <popey> wormhole
[15:14] <kyrofa> zyga, people.canonical, or magic wormhole
[15:14] <zyga> I forgot to sync my ssh key so I don't have access to my personal stuff
[15:14] <kyrofa> Haha, hi popey
[15:14] <zyga> I'll use wormhole
[15:14] <popey> wormhole ftw
[15:14] <zyga> thank you popey :)
[15:14] <popey> np
[15:15] <zyga> kyrofa: I sent you wormhole command to run
[15:16] <kyrofa> zyga, receiving now
[15:16] <kyrofa> Done. That really is magical
[15:17] <zyga> woah
[15:17] <zyga> indeed :)
[15:17] <zyga> I'm using snapcraft as a snap
[15:17] <zyga> in case that matters
[15:18] <mvo> cachio: ok, yeah, the reboot is strange
[15:20] <cachio> mvo, is it related to the entropy?
[15:25] <ogra> sil2100, is there any ETA when the new features (gadget connections) will land in the ubuntu-image snap so we can actually make use of them ?
[15:25] <ogra> (i see the code landed since a while)
[15:25] <mvo> cachio: slowness may well be related, did you update the kernel as well or kept that? please try to keep the kernel as it has the fixed initrd
[15:26] <zyga> kyrofa: any ideas?
[15:26] <zyga> kyrofa: I'd like to upload that snap
[15:26] <zyga> to edge
[15:27] <kyrofa> zyga... I can't explain this. Run `unsquashfs -d /tmp/foo/ fedora29.snap -e meta/snap.yaml`
[15:27] <zyga> k
[15:27] <kyrofa> zyga, you'll see you own /tmp/foo/meta and everything
[15:27] <kyrofa> But you can't delete it without sudo
[15:27] <zyga> kyrofa: that worked
[15:27] <kyrofa> I thought maybe it was an ACL thing, but it doesn't seem so
[15:27] <zyga> that's correct!
[15:27] <zyga> I cannot remove it
[15:28] <ogra> mvo, hmm, looking at #5612 there needs to be some more AI in it ... i.e. on devices where pivot-agent is installed you want that snap to be set up first (to not waste time before a model pivot happens (which includes a factory reset) ) but i.e. on systems where pivot-agent and NM are seeded you want NM to be seeded before pivot-agent ... etc etc
[15:28] <kyrofa> zyga, what DEMONS did you put on my machine
[15:28] <zyga> one sec
[15:28] <zyga> I think I know
[15:29] <ogra> mvo, you'D want that to happen somewhere between your 2 and 3 in that enumeration
[15:30] <zyga> kyrofa: actually
[15:30] <zyga> not yet :)
[15:30] <zyga> it is _very_ interesting
[15:31] <kyrofa> zyga, right?!
[15:31] <zyga> it's on tmpfs here
[15:31] <zyga> so not even xattrs
[15:31] <sil2100> ogra: hey! I planned to release u-i 1.4 this week, I guess that's still more-or-less possible
[15:31] <ogra> sil2100, awesome, i just wanted to make sure the snap isnt forgotten (i dont use any deb for u-image anymore ... and i guess most of my collegaues dont either)
[15:32] <kyrofa> zyga, anyway, if you can manage to get to the bottom of that, snapcraft should happily upload this for you
[15:32] <zyga> kyrofa: I think I know
[15:32] <zyga> can you ls -ld meta
[15:33] <zyga> followed by ls -ldZ meta
[15:34] <zyga> doh
[15:34] <sil2100> ogra: it won't be forgotten! I'll actually promote 1.4 to stable finally this time, since usually that wasn't part of the process
[15:34] <zyga> kyrofa: it's not what I put
[15:34] <zyga> the /tmp/foo directory is not writable!
[15:34] <zyga> kyrofa: it's snapcraft :D
[15:34] <zyga> kyrofa: chmod +w /tmp/foo
[15:34] <zyga> "daemons" :D
[15:36] <kyrofa> zyga, what the heck. unsquashfs makes that dir, but this works for other snaps
[15:37] <zyga> kyrofa: so ... why is it read-only?
[15:37] <kyrofa> zyga, if I run that same unsquashfs command on, say, the snapcraft snap, it's writable
[15:37] <zyga> oh
[15:37] <zyga> a possible hint
[15:37] <zyga> dr-xr-xr-x. 19 root root     4096 Aug  8 15:59 prime
[15:37] <zyga> I'll tweak that
[15:38] <kyrofa> Oh interesting
[15:38] <kyrofa> That must be saved somewhere in the image
[15:39] <zyga> yeah
[15:39] <zyga> since prime is the rootfs
[15:39] <zyga> it is not writable for some reason
[15:39] <zyga> (not sure wh)
[15:39] <kyrofa> Indeed
[15:39] <zyga> trying now
[15:40] <zyga> man, that's an obscure one :)
[15:40] <kyrofa> That error message was NOT helpful
[15:40]  * zyga hugs kyrofa 
[15:40]  * kyrofa hugs zyga back
[15:41] <zyga> apparently that's how / is set up on fedora
[15:41] <zyga> it's not root writable
[15:41] <kyrofa> That's interesting
[15:43] <zyga> is / writable by root on ubuntu?
[15:43] <ogra> mvo, i actually commented on #5612
[15:43] <mvo> ogra: thanks, thats useful information. note that it won't change any snap ordering if the snaps are not bases or content providers so you can control the order via required snaps. it will just enforce certain things for special types like bases
[15:43] <ogra> zyga, classic ? sure
[15:43] <zyga> kyrofa: pushed :)
[15:43] <zyga> processing
[15:44] <zyga> mvo: now I need your super-powers :)
[15:44] <mvo> zyga: what for?
[15:44] <kyrofa> zyga, nice!
[15:44] <zyga> mvo: for fedora29 snap, let me see if it actually gets blocked
[15:44] <zyga> still in processing
[15:45] <ogra> mvo, yeah, i'm just wondering if we should perhaps have a "seed priority" value you can give to snaps or some such ... beyond the order in required-snaps so the handling of bases could take that into account ... the prob appreas to be very complex now that bases are a thing :)
[15:45] <ogra> *appears
[15:45] <mvo> ogra: yeah, its definitely complex
[15:46] <ogra> i tried to explain it in the comment ...
[15:46] <zyga> it's still processing
[15:46] <zyga> roadmr: hey
[15:47] <zyga> roadmr: is there a way to check if a snap processing task on the store is stuck / crashed for whatever reason
[15:47] <zyga> roadmr: I just submitted one for "fedora29"
[15:47] <roadmr> hi zyga !
[15:47] <roadmr> zyga: is that the snap name?
[15:47] <roadmr> zyga: we *are* checking a situation with snaps getting stuck :(
[15:47] <zyga> roadmr: yes
[15:48] <zyga> it's a 29M snap that is processing for a few minutes now
[15:48] <sil2100> mvo: btw. I tried latest subiquity from git and sadly it doesn't work, so for now I cherry-picked the branding fixes and pushed that into a PPA
[15:48] <zyga> it's been made on fedora manually so maybe dragons apply
[15:48] <zyga> it's a base snap
[15:48] <mvo> sil2100: ta
[15:48] <roadmr> zyga: let me have a look
[15:48] <zyga> thank you
[15:48] <sil2100> mvo: Michael mentioned console-conf from subiquity master isn't really usable right now
[15:49] <mvo> sil2100: did you figure anything about about the interface issue on the pis? I would love to build pi images soon(ish) but this is a blocker right now
[15:49] <mvo> sil2100: (not the only one though)
[15:49] <roadmr> zyga: I see *no* uploads for fedora29 snap :( that may mean it got rejected even before hitting the database
[15:49] <zyga> roadmr: whoah?
[15:49] <zyga> how is that possible
[15:49] <mvo> zyga: what message did you get from the store?
[15:49] <zyga> I see fedora29.snap 100% uploaded and a spinning processing marker
[15:50] <roadmr> zyga: what are you using? snapcraft?
[15:50] <zyga> it's hard to copy paste from the console but it is processing
[15:50] <zyga> yes
[15:53] <zyga> no change still
[15:53] <zyga> I can abort and retry
[15:53] <zyga> but ... no idea
[15:53] <roadmr> zyga: no, please hold on a second
[15:53] <zyga> oh
[15:53] <zyga> I just did :<
[15:53] <roadmr> :P
[15:53] <zyga> https://www.irccloud.com/pastebin/z7UDGHnq/
[15:53] <mvo> zyga: do you happen to know if there is a way to ask apparmor for current capabilities? I want to find out if I have mac_admin
[15:53] <zyga> although it's not done yet, the process is alive still
[15:53] <popey> zyga: https://forum.snapcraft.io/t/degraded-performance-snaps-stuck-in-automated-review/6736
[15:53] <zyga> mvo: I don't know if there is a way
[15:53] <popey> you are probably being hit by this, but roadmr is the best one to help :)
[15:54] <zyga> thank you
[15:54] <mvo> zyga: aha, I htink I found code in lxd for this
[15:54] <mvo> zyga: heh, that looks promising
[15:54] <roadmr> zyga: fedora29 is crashing the scan / reviewer tools appparently
[15:54] <zyga> roadmr: how?
[15:54] <roadmr> zyga: getting yo more details
[15:55] <zyga> jdstrand: ^
[15:55] <roadmr> aha interesting, zyga jdstrand this should be reproable locally
[15:55] <roadmr> Permission denied: '/tmp/tmp14k8ex/unpacked/usr/lib/snapd
[15:55] <roadmr> apparently the snap has some funny perms which the tools can't properly clean up
[15:55] <zyga> looking
[15:56] <kyrofa> zyga, hahaha, you're breaking EVERYTHING
[15:56] <zyga> it's just 755
[15:57] <zyga> roadmr: do you have a traceback that would help jdstrand?
[15:57] <roadmr> sure, just a sec
[15:59] <roadmr> zyga, jdstrand : https://pastebin.canonical.com/p/wrmWdbh7yk/
[16:00] <zyga> thank you
[16:00] <zyga> jdstrand: can you please look at that, maybe I can tweak the snap somehow
[16:01] <roadmr> zyga: do you have a local copy of the reviewer tools? maybe you can run it and check?
[16:01] <zyga> no, I don't
[16:01] <roadmr> zyga: hehe :) https://launchpad.net/click-reviewers-tools/trunk, conversely if you let me have a copy of the snap I can run that
[16:02] <zyga> roadmr: I can wormhole the snap to you
[16:03] <sil2100> mvo: apologies it's taking so long, still digging into it and I'll know more tomorrow for sure
[16:04] <mvo> sil2100: thank you, no worries, sorry for nagging so much
[16:19] <zyga> roadmr: can you please telegram me once you have something?
[16:19] <roadmr> let me see if I can
[16:19] <mvo> kyrofa: could you please run the following https://play.golang.org/p/ttDizCrhv6q
[16:19] <mvo>  inside your pi lxd env?
[16:20] <roadmr> zyga: can you tg me so you appear in my list of contacts?
[16:21] <roadmr> zyga: oh sorry, that traceback has *nothing* to do with the reviewer tools :(
[16:21] <zyga> sure
[16:22] <zyga> oh?
[16:23] <roadmr> nono, it's all the *store* code trying to clean up and failing because some of the unpacked files have funny permissions it seems
[16:23] <roadmr> let me try
[16:25] <kyrofa> mvo, doing now
[16:27] <roadmr> zyga: indeed the permissions look fine :( I'll check again in a bit, need to afk
[16:32] <kyrofa> mvo, both with and without the raw.lxc I get `1 0 errno 0`
[16:43] <Chipaca> kyrofa: does snapcraft support bases?
[16:43] <Chipaca> as in, doing the right thing wrt building against the appropriate glibc?
[16:44] <Chipaca> asking as the last time I checked it didn't (you had to use passthrough), but  users are asking :-)
[16:47] <kyrofa> Chipaca, not quite yet. We're using build VMs to support different bases, and that work isn't completely finished yet
[16:47] <kyrofa> Chipaca, sergiusens might have a branch for you to experiment with though, if you're interested
[16:47] <Chipaca> kyrofa: nah, it's answering a user's complaint: "The base key of snapcraft.yaml and it’s possible values are not documented"
[16:48] <Chipaca> kyrofa: i'm finding a polite way of replying "duh"
[16:48] <kyrofa> Hahaha
[16:48] <kyrofa> Yeah that's our biggest roadmap item this cycle, it'll be a bit yet
[16:50] <Chipaca> kyrofa: BUT WHY ISN'T IT DOCUMENTED YET
[16:51] <Chipaca> kyrofa: :-D
[16:56] <Chipaca> jdstrand: remember yesterday we were talking about core18 on 14.04? (I think it was yesterday, in the context of the socket multiplex thing)
[16:56] <Chipaca> jdstrand: https://forum.snapcraft.io/t/cannot-perform-readlinkat-on-the-mount-namespace-file-descriptor-of-the-init-process-permission-denied/6743 might be relevant to that
[16:59] <sergiusens> Chipaca: you did not read my post http://blog.sergiusens.org/posts/snapcraft-build-environments/ ?
[16:59] <Chipaca> sergiusens: "read my blog"?
[17:00] <Chipaca> sergiusens: I wonder why my rss reader didn't pick it up
[17:00] <sergiusens> Chipaca: it is about the progress, it is also a forum post ;-)
[17:01] <sergiusens> Chipaca: but what is this about? I just didn't read it all in here, too much traffic :-)
[17:01] <Chipaca> sergiusens: a user complaining about the lack of documentation for a feature that isn't done
[17:01] <Chipaca> sergiusens: in their defence, everybody is excited about bases
[17:02] <sergiusens> Chipaca: I know, the availability of bases is however being gated as the introduction of build environment
[17:02] <Chipaca> sergiusens: no complaints from me :-)
[17:03] <Chipaca> most people are only going to come to the feature excited for the first time once
[17:07] <Shibe> is gnome-builder available as a snap?
[17:08] <ogra> https://snapcraft.io/store
[17:09] <ogra> specifically: https://snapcraft.io/search?category=&q=gnome-builder
[17:09] <popey> Shibe: not that I'm aware of
[17:09] <ogra> (i guess thats a "no")
[17:09] <popey> It's certainly been suggested, but nobody has done it
[17:09] <popey> ^ kenvandine :)
[17:10] <Shibe> how hard it is to make snap?
[17:10] <Shibe> if i compile gnome-builder in gentoo how much effort would it take to make a snap of it i can use on ubuntu?
[17:15] <Chipaca> Shibe: very tricky, because the libs will probably be all wrong
[17:31] <kyrofa> mvo, just wanted to verify that you got my output
[17:41] <kenvandine> popey, it would be easiest as a classic snap
[17:44] <mvo> kyrofa: thanks for the test run, that looks like I need to take another appraoch, oh well
[18:15] <jdstrand> Chipaca: I actually do not remember that. I remember I submitted a pr that made it so that socketcall would be there unconditionally on 14.04
[18:15] <jdstrand> Chipaca: and conditionally in other situations
[18:17] <jdstrand> Chipaca: I responded to that forum topic
[18:17] <Chipaca> jdstrand: rock on
[18:18] <jdstrand> Chipaca: it is probably a variation of https://forum.snapcraft.io/t/custom-kernel-error-on-readlinkat-in-mount-namespace/6097/21, which has a fix in trunk and 2.34, but not 2.34.3
[18:19]  * Chipaca sees a "I've asked John to ..." and gets nervous
[18:36] <jdstrand> roadmr: I see the update on status; does that mean resquashs is reenabled?
[19:01] <roadmr> jdstrand: I haven't reenabled it, let me just triple-check the incident report to ensure it's safe to do so
[19:03] <jdstrand> roadmr: yeah, I read that too and it wasn'
[19:03] <jdstrand> t clear to me
[19:06]  * cachio afk
[19:07] <roadmr> jdstrand: resquashfs enforcement enabled!
[19:18]  * jdstrand hugs roadmr :)