/srv/irclogs.ubuntu.com/2017/03/30/#snappy.txt

mupBug #1677417 opened: /etc/ld.so.conf.d/conjure-up.conf breaks apt on host system <Snappy:New> <conjure-up (Ubuntu):New for adam-stokes> <https://launchpad.net/bugs/1677417>00:35
=== chihchun_afk is now known as chihchun
=== hikiko_ is now known as hikiko
mwhudsonwho can help me with tracks in the store?07:17
zygamwhudson: maybe open a store side question on the forum?07:22
mwhudsonzyga: did the forum get mentioned on the mailing list yet?07:23
zygamwhudson: it's metioned in the topic here :)07:23
mwhudsonyes, that's the only place i've seen it mentioned07:23
zygamwhudson: I think it will replace the mailing list entirely07:23
* mwhudson gives an old man sign07:23
mwhudson*sigh07:23
mwhudsonhttps://forum.snapcraft.io/t/can-someone-set-up-guardrails-for-the-go-snaps-tracks/7207:29
mwhudsonalso autopublishing to tracks from launchpad would save me a lot of effort :)07:29
morphismwhudson: ping07:31
mwhudsonmorphis: hi07:32
morphismwhudson: hey! how are things? :-)07:32
mwhudsonmorphis: not bad!07:32
morphismwhudson: sounds good, I saw you're one of the maintainers of snapd in debian07:33
mwhudsonmorphis: yeah07:33
morphismwhudson: any concrete plans to update the package real soon?07:33
mwhudsonmorphis: no, debian is in freeze07:33
morphisdon't we have a package in unstable too?07:33
mwhudsonmorphis: i thought re-execing in the core snap mostly meant i didn't have to07:33
mwhudsonwell yeah but life is easier if stable and unstable don't diverge aiui07:34
zygamwhudson: I think we could file an RC bug because we need to ship something or the package is totally broken :/07:34
mwhudsoni could upload a newer one to experimental07:34
mwhudsonzyga: right, if we need to fix this core snap hanging thing with a new package, we need to do that07:34
morphismwhudson: we had a few serious issues recently which are now patched in snapd 2.23.6, though I didn't checked yet if debian is affected07:34
* zyga reboots to try new pulseaudio 07:35
morphismwhudson: let me try the current snapd package in testing07:36
mwhudsonmorphis: i've not dealt with the politics of getting a release exception in debian07:37
morphismwhudson: ok, so lets see if we an avoid this :-)07:37
mwhudsonmorphis: but it's at least possible that targeted fixes will be an easier sell than a wholesale upgrade07:37
mwhudsonor not, i don't know07:37
morphismwhudson: I think if there are single fixes needed to get snapd in debian re-exec into the one coming from the core snap we can do that07:38
morphiszyga: https://bugzilla.opensuse.org/show_bug.cgi?id=1031501#c307:43
zygamorphis: looking07:48
zygamorphis: so 1) this will only work if home interface is connected (it doesn't even have to be used)07:48
zygamorphis: why does every non-snap app work?07:48
zygamorphis: there must be a different auth mechanism that is being tried07:49
zygamorphis: it fails and xauthority is a workaround07:49
morphismaybe07:49
morphisthat is what I am currently looking into07:49
morphiszyga: it wouldn't even work with the home interface connected as it doesn't allow you to use .XAuthority07:49
morphisit only works in this case because we have no confinement at all07:50
zygamorphis: ah, right07:56
morphiszyga: ok, it gets interesting, XAUTHORITY is set to /tmp/xauth-1000-_0 in KDE on suse08:07
morphiszyga: are we doing any processing of the env vars when we spawn up the snap environment?08:07
morphisno, as it seems, it ends up the snap in the snap env08:08
zygamorphis: aha08:09
zygamorphis: see08:09
zygamorphis: it is /tmp related :)08:09
morphiszyga: flatpak is doing some extra stuff here08:09
morphissee https://sources.debian.net/src/flatpak/0.8.4-3/common/flatpak-run.c/?hl=1944#L192408:09
zygamorphis: yes, I think we need to extra stuff for x11 and pulseaudio08:09
zygamorphis: that feels like snap-confine's work08:10
zygamorphis: you could read the xauth config on startup08:10
zygamorphis: and after dropping privs write the file into the fresh /tmp08:10
zygamorphis: (remember that tmp is empty)08:11
morphiszyga: right08:11
morphissimilar to what flatpak does08:11
zygamorphis: yeah08:14
zygamorphis: right now I'd code it in C directly08:14
zygamorphis: but I sooomewhat worry about how many hacks like this we'll need08:14
zygamorphis: I suspect that a bound set so this is oK08:14
zygamorphis: if it starts to look like each new interface needs this we may have to think about snapd assisting via a backend08:14
morphiszyga: right08:14
morphiszyga: lets start with a hack into snap-confine08:15
morphisactually this is kind of a problem and wondering if the KDE guys didn't experienced this problem with their snaps08:15
morphiszyga: let me take this problem as part of my cross-distro work08:16
morphisSon_Goku: ping08:26
Son_Gokupong08:26
Son_Goku:/08:26
morphisSon_Goku: you saw the PR for the missing not upstream patch?08:30
Son_Gokuyes08:30
Son_GokuI already added the comment to my spec08:30
morphisgood08:30
Son_GokuI'm rebasing to 2.23.6, since you guys released that yesterday :/08:30
morphisSon_Goku: :-)08:30
Son_Gokuand I've already been bitten patchwise08:31
morphisin which way?08:31
Son_Gokuthe systemd unit template PR doesn't apply cleanly onto 2.23.608:31
Son_Gokuthe rules file hunks all fail08:31
Son_Gokuso I've been purging those manually from the patch08:31
morphisyeah those things are nasty08:32
morphisSon_Goku: so really time to get them all dropped :-)08:32
morphisSon_Goku: I am trying to get that solved with 2.2408:32
Son_Gokuis seccomp still broken for 2.23.6?08:35
Son_Gokumorphis ^08:36
morphisSon_Goku: we have fixed one bug but I fear there might be more08:38
Son_Gokuso still broken, yay :(08:38
morphisnot directly broken08:38
morphisbut as AppARmor is disabled we may run into situatuions where things would have been blocked already by AppArmor and not run into seccomp denials which lead to hanging processes like we had for snapctl08:39
morphisSon_Goku: once we're done with the basic packaging bits I will start working on getting proper CI up for fedora/debian/suse/..08:39
morphisthen we have a much safer way of handling and testing those things and can ensure they keep working08:40
Son_GokuI feel like banging my head into the ground with all this shit... :/08:40
Son_Gokualright, I'm turning back on seccomp and damn the consequences08:40
morphisSon_Goku: things will be much easier once we have all patches upstream08:41
morphisand confinement is on my list too08:42
Son_GokuI hate golang so much08:42
Son_Gokuit just adds so much complication to things08:42
morphis:-)08:42
Son_GokuI used to merely dislike golang, now I hate it08:43
seb128hey morphis, sorry I was not around when you pinged yesterday and it was a contentless ping so couldn't reply when I came back ... I guess it was about that KDE/opensuse issue you are discussing on the list and now here?08:45
morphisseb128: right, I thought you might be one who knows what is going on but I've figured the real problem already: https://bugs.launchpad.net/snapd/+bug/167751308:46
mupBug #1677513: snap-confine does not pass file referenced by XAUTHORITY env variable into the snap environment <snapd:Confirmed for morphis> <https://launchpad.net/bugs/1677513>08:46
morphisseb128: didn't checked KDE on Ubuntu yet but they might set XAUTHORITY to something in /run or /home too08:47
morphisseb128: but thanks for the late pong :-)08:47
seb128np, glad that you figured it out :-)08:47
Son_Gokuwell, here we go...08:52
Son_Gokumorphis: https://koji.fedoraproject.org/koji/taskinfo?taskID=1867855708:53
morphisSon_Goku: awesome!08:53
pedronismvo: #3109 is mergeable, no?08:54
morphisSon_Goku: will give this some testing once ready08:54
Son_Gokuoh crap08:55
Son_GokuI just realized something08:55
morphis?08:55
Son_GokuI need to pull in my snapctl patch08:57
Son_Gokufor selinux08:57
Son_Gokuthat was almost certainly not merged back in to 2.23.608:57
Son_Gokunot knocking on mvo, but this was not exactly something he cared about for merging back into releases before08:58
morphisSon_Goku: ah, is that one already in master?08:58
Son_Gokuyes08:58
morphisok, another one we can drop with 2.24 then..08:58
Son_Gokusince the debubuntu packages don't ship the selinux module as a subpackage yet, he has no way of knowing or caring about changes to it08:58
morphisright08:59
morphisSon_Goku: this will get better once we have CI also caring about fedora08:59
Son_GokuI doubt it08:59
Son_Gokuit'll be hard to spot selinux backport things because the domain is in permissive mode09:00
morphisI see09:01
morphissomething I need to dive into at a later point09:01
Son_Gokugenerally, selinux policy module changes should be assumed to be backported, I think09:02
Son_Gokuas they are generally reactive from when you guys change something, rather than proactive09:03
mvoSon_Goku: hey, sorry that some bits did not get backported, we want to do a 2.24 soon though. we did the 2.23.6 mostly to ensure we have some important bugfixes out before moving on. once 2.24 lands things should move more normal again, i.e. things in master also go into the release etc09:07
Son_Gokumvo: no worries09:08
Son_GokuI blame morphis anyway :P09:08
Son_Goku(not really!)09:08
morphisSon_Goku: :-D09:08
Son_Gokuanyway, I expect that this will get better, vis-a-vis the selinux module, once someone adds the packaging for it to debubu packaging09:09
Son_Gokuwhat I'm going to hate doing is packaging DNF debian-style for snapcraft09:10
Son_GokuI despise Debian-style packaging (I consider it way more complicated than it should be)09:10
Son_Gokuit's not that I don't know how to do it... I certainly do09:10
Son_Gokuafter all, I used to use Ubuntu for years and almost became a Debian/Ubuntu contributor many years ago09:11
Son_Gokufuck09:13
Son_Gokusnapd FTBFS on i68609:14
Son_Gokuand ppc6409:14
Son_Gokuwell, at least it built on ppc64le09:15
Son_Gokuhttps://koji.fedoraproject.org/koji/taskinfo?taskID=1867872309:15
morphisSon_Goku: ah, I have a fix for that one09:17
* Son_Goku groans09:18
morphisSon_Goku: https://github.com/snapcore/snapd/pull/309409:18
mupPR snapd#3094: cmd: rework header check for xfs/xqm.h <Created by morphis> <Merged by zyga> <https://github.com/snapcore/snapd/pull/3094>09:18
Son_Gokuyay09:18
Son_Gokumore patches09:18
morphisSon_Goku: with that everything should build fine, verified with https://copr.fedorainfracloud.org/coprs/mrmorph/snapcore/09:18
Son_Gokuyou don't have a fix for ppc64, though09:18
morphiswhich doesn't build for ppc but for i38609:19
morphisyeah looking into that one ..09:19
morphisSon_Goku: can I easily cross build with mock?09:20
Son_Gokuno09:20
Son_Gokumock does not support foreign arches like that yet09:20
Son_GokuBUT09:20
Son_GokuFedora offers contributors access to ppc64 VMs09:20
morphisah09:20
Son_Gokumorphis: I suggest hopping into #fedora-ppc and asking about it09:21
morphisSon_Goku: will do, need to care about a few other things first09:23
morphispedronis: what retry interval do we have in snapd currently to reach the serial-vault as configured from the prepare-device hook?09:27
pedronismorphis: 1 minutes for dynamic errors,  for things that look like the vault is not understanding a back off starting from 5 minutes and then doubling up to a max09:30
Son_Gokumorphis: and joy of joys09:31
Son_Gokuarmv7hl failed too09:31
morphispedronis: ok, but we don't block the further first-boot process when we can't the server, right?09:31
morphisSon_Goku: wonderful ..09:31
Son_Gokufull list of failures: https://koji.fedoraproject.org/koji/taskinfo?taskID=1867872309:31
pedronismorphis: first boot is completely independent, they are even two different changes09:31
pedronismorphis: what we block is the fist refresh for a bit09:31
pedroniswe try to refresh witha serial if possible09:32
pedronisbut after a while try anyway09:32
Son_Gokumorphis: it looks like arm failed because of same issue with i68609:32
morphispedronis: ok, just wanted a confirmation on this09:32
morphisSon_Goku: yeah, which is a "good" thing :-)09:32
Son_Gokumorphis: added patch, and trying again: https://koji.fedoraproject.org/koji/taskinfo?taskID=1867897709:38
morphisSon_Goku: great09:38
zygamvo: can you please have a 2nd look at https://github.com/snapcore/snapd/pull/310209:46
mupPR snapd#3102: interfaces/mount: add function for parsing mount entries <Created by zyga> <https://github.com/snapcore/snapd/pull/3102>09:46
Son_Gokumorphis: now i686 just fails to compile :(09:46
Son_Goku  /usr/include/xfs/xfs.h:51:12: error: size of array 'xfs_assert_largefile' is too large09:47
Son_Goku extern int xfs_assert_largefile[sizeof(off_t)-8];09:47
Son_Gokumorphis: you need to go back to the drawing board on this09:47
zygaI see you two are having fun :)09:48
* Son_Goku groans09:48
Son_GokuI wanted this to be released already09:48
Son_GokuI want the buildsys to stop telling me that snapd-glib is broken09:48
zygaI start to see light at the end of my tunnel09:48
zygawith the move to go the coding moves faster than before09:49
morphisSon_Goku: hm, this worked for me well in Yocto ..09:49
Son_GokuI see crushing sadness and dispair09:49
Son_Gokumorphis: Yocto is bullshit09:49
morphisSon_Goku: lets not get into this discussion, please :-)09:49
Son_GokuYocto can be whatever you want, so it doesn't really serve as a great means of comparison09:49
morphisSon_Goku: you have a link to the last build?09:50
zygaSon_Goku: I think the more interesting fact is that it built on 32bit debian09:50
Son_Gokuzyga: Debian has older compiler09:50
zygaSon_Goku: sid?09:50
zygaSon_Goku: very doubtful09:51
Son_Gokuhas debian moved onto GCC 7 yet?09:51
Son_Gokuas far as I knew, they were still on 6.3.x09:51
zygaSon_Goku: yes09:51
Son_Gokuare you using hardened build flags there?09:52
zygahttps://packages.debian.org/experimental/gcc-709:52
Son_Gokubecause Fedora does by default09:52
zygaSon_Goku: I don't know09:52
Son_GokuI know Debian does not09:52
zygabut dones't look like related to what the error above says09:52
zygait does look like the size of off_t is the relevant factor here09:52
zygabut TBH09:52
zygathis is all load of BS09:52
Son_Gokuzyga: anyway, gcc-defaults in sid is gcc609:52
zygabecause we should just check if that header file exists09:52
Son_Gokuhttps://packages.debian.org/sid/gcc09:52
zygaall we need are _constants_09:53
zygamorphis: feel free to hardcode those as those are kernel constants and kernel is not insane to change09:53
zygamorphis: and drop libxfsprogs-devel from dependencies09:53
Son_Gokumorphis, zyga: https://koji.fedoraproject.org/koji/taskinfo?taskID=1867897709:53
Son_Gokuthe green, orange, and red links are clickable :)09:53
zygathe ppc one is interesting, checking09:54
morphiszyga: you propose that as an upstream change? :-)09:54
Son_Gokuhere's a previous failed build, too, prior to adding snap-confine patch: https://koji.fedoraproject.org/koji/taskinfo?taskID=1867872309:54
zygamorphis: as a distro change and upstream change later09:54
zygamorphis: I see no reason to check linkability or work around this issue09:54
zygamorphis: if we care about a hanful of constants09:54
morphisSon_Goku: ok, this looks different now09:55
Son_Gokuthe failures are possibly caused by newer libxfs09:55
morphismaybe09:55
Son_GokuFedora has xfsprogs 4.10.009:56
Son_GokuDebian has xfsprogs 4.9.009:56
Son_Gokusince we update the kernel, we also update the tools too09:56
morphisSon_Goku: my guess is that we should get this building with add -D_FILE_OFFSET_BITS=64 to CFLAGS10:01
Son_Gokupatch?10:01
morphisSon_Goku: something like https://paste.ubuntu.com/24280132/ but didn't tested it yet10:03
Son_Gokueasy to test, I can just fire off a scratch build for it10:04
Son_Gokuokay, I'm getting super sick of this10:04
Son_Gokusomeone needs to turn off OpenID auth on raw pastes10:04
Son_Gokumorphis: if no one fixes that, please stop using paste.ubuntu.com10:04
morphis:-)10:05
zygaSon_Goku: I bet there's a reason for that10:06
Son_Gokuzyga: I don't care10:06
Son_Gokuit's stupid and aggravating and I can't curl anything10:06
Son_Gokumorphis: please use paste.fedoraproject.org, if you need an alternative10:06
Son_Gokuthere's also a handy fpaste utility for pasting from the CLI :)10:07
Son_Gokuhttps://pagure.io/fpaste10:07
* zyga wonders why not pastebinit + config10:07
Son_Gokuwell, I didn't know about pastebinit :)10:08
zygait supports many paste services10:08
zygasimple python script AFAIR10:09
Son_Gokuit has a fpaste config10:09
Son_Gokuthough I don't know if it works with the new pastebin software fedora deployed recently: https://fedoramagazine.org/hello-modern-paste/10:10
morphisSon_Goku: looks nice10:11
zygaSon_Goku: I honestly don't like the new paste, there was a looot of negative feedback after it was rolled out10:12
zygaSon_Goku: I need to try it again though, I think/hope some of that feedback was addressed10:12
Son_GokuI don't care for it's look and the superlong URLs10:12
zygaSon_Goku: the URLs were totally broken wrt basic usaility10:13
zyga*usability10:13
=== carlolo_ is now known as carlolo
Son_Gokumorphis: trying a scratch build with your diff: https://koji.fedoraproject.org/koji/taskinfo?taskID=1867935410:16
morphisok10:16
morphisah10:17
morphisit wont work10:17
morphisneeds to be = instead of +=10:17
morphisSon_Goku: sorry for that10:17
morphisSon_Goku: https://paste.fedoraproject.org/paste/-NaL-TKvNct9~lx1tvVDdl5M1UNdIGYhyRLivL9gydE=10:18
Son_Gokudoes that mean all the hardening flags are clobbered?10:18
morphisno10:20
morphisif we add AM_CFLAGS then they are there10:20
morphisSon_Goku: so something like https://paste.fedoraproject.org/paste/k6OU-DUhS5tSIQ5cglQP7F5M1UNdIGYhyRLivL9gydE= is more correct10:21
morphisSon_Goku: this fork functionality is quite nice10:21
Son_Gokuyes, it is10:21
zygaogra: how do you reply with a quote on discourse?10:22
ograzyga, just mark something in the text then a "quote" thing pops up10:22
ograyou also earn a new badge with it ;)10:22
zygaaah, nice!10:22
zygathanks!10:22
Son_Gokumorphis: take 2: https://koji.fedoraproject.org/koji/taskinfo?taskID=1867942710:25
morphisSon_Goku: lets hope this now works ..10:25
Son_Gokusince arm takes too long, I'm going to assume it works if i686 does10:25
Son_Gokuthen you can prepare a formal PR and I can have a formal patch and we can try again for all arches10:26
zygaogra: heh, my quote didn't really work :)10:26
Son_GokuI wish our discourse supported social sign on10:27
zygafixed now10:27
zygaogra: have a look at https://github.com/snapcore/core-build10:27
Son_Goku(not Ubuntu SSO, but normal SSO, like Google, Twitter, GitLab, GitHub, etc.)10:27
zygaogra: what else do we need there?10:27
zygaSon_Goku: I think it doesn't upstream and that's why we don't have it here10:28
Son_Gokuweird10:28
zygaSon_Goku: and as a plugin it is not supported from what I heard10:28
zygaSon_Goku: I think there's a thread about that actually10:28
Son_Gokuhm10:28
zygaSon_Goku: no, let's start one10:28
Son_Gokuthe Rust forum uses social sign-on, I think10:28
Son_Gokuyeah, Rust uses GitHub10:29
zygahttps://forum.snapcraft.io/t/support-for-sso-on-forum-snapcraft-io/7510:29
Son_Gokuone of the other ones I know of uses Google10:29
morphisSon_Goku: looks like the patch apply failed this time10:29
Son_Goku:/10:30
zygaogra: https://forum.snapcraft.io/t/gardening-in-github-com-snapcore-core-build/7610:34
Son_Gokumorphis: fixed the patch, but it didn't work10:36
morphisSon_Goku: you have the full patchset somewhere?10:36
morphislet me create the patch on top of that10:36
Son_Gokumorphis: the patch set is http://pkgs.fedoraproject.org/cgit/rpms/snapd.git/tree/ + https://da.gd/qUH4P10:38
morphisSon_Goku: https://paste.fedoraproject.org/paste/AFR94F40CNQwmk3eFcy4Rl5M1UNdIGYhyRLivL9gydE= should cleanly apply on top of the patchset10:43
Son_Gokuyes, but it still doesn't fix the problem10:44
Son_Gokuoh wait10:44
Son_Gokula10:44
ograzyga, if you mention me in the post you dont need to ping on IRC ;)10:44
ogra(was already writing an answer when you pinged)10:45
zygaogra: aha, you get destkop notifications on @-mentions?10:46
Son_Gokumorphis: take 4: https://koji.fedoraproject.org/koji/taskinfo?taskID=1867955210:47
ograzyga, yeah10:47
morphisSon_Goku: we're coming closer :-)10:49
morphisSon_Goku: ok, this didn't help10:50
morphisSon_Goku: need to scratch my head around this when I am done with my meetings10:51
mupPR snapd#3113 opened: overlord/snapstate: unlock/relock the state less, especially not across mutating the SnapState of a snap <Created by pedronis> <https://github.com/snapcore/snapd/pull/3113>11:17
pedronisChipaca: you might want to look at snapd#3113 when one have a moment, it's not big, it's the changes about locking discussed yesterday11:30
mupPR snapd#3113: overlord/snapstate: unlock/relock the state less, especially not across mutating the SnapState of a snap <Created by pedronis> <https://github.com/snapcore/snapd/pull/3113>11:30
Chipacapedronis— looking11:30
mvopedronis: yes, 3109 is mergable11:32
mvozyga: sure, I have a look at the fstab thing11:32
mupPR snapd#3109 closed: Merge 2.23.6 release back into master <Created by mvo5> <Merged by pedronis> <https://github.com/snapcore/snapd/pull/3109>11:34
pedronismvo: done11:35
ograzyga, https://github.com/snapcore/core-build/pull/111:35
mupPR core-build#1: adjust README file to proper reflect repo content <Created by ogra1> <https://github.com/snapcore/core-build/pull/1>11:35
mvopedronis: ta11:37
zygaogra: +111:38
Chipacapedronis— +1; lgtm and good start11:57
zygaChipaca: care to do a 2nd review of https://github.com/snapcore/snapd/pull/310211:58
mupPR snapd#3102: interfaces/mount: add function for parsing mount entries <Created by zyga> <https://github.com/snapcore/snapd/pull/3102>11:58
Chipacazyga— nah11:58
* Chipaca grins11:58
zygaChipaca: et tu Brutus?11:58
zyga;-)11:58
Chipacazyga— et ideam habent quam multa.11:59
jdstrandmorphis, Son_Goku: things will also get much better when we don't kill the process for a seccomp denial and instead return something like EPERM. this is in progress11:59
morphisjdstrand: yeah, that would help12:00
morphisjdstrand: however I still fear we will run into multiple bugs with just seccomp and no AppArmor12:00
morphisso having some extensive testing before we enable this would be good12:00
jdstrandmorphis: the sandbox is definitely designed for both to be enabled. enabling seccomp without apparmor isn't really gaining you much12:01
morphisjdstrand: right12:01
jdstrandmorphis: I mean, sure, you can't load a kernel module, but you can write a file to /etc/modules.d12:01
morphisjdstrand: so for other systems we need SELinux + Seccomp or nothing12:01
jdstrand/etc/modules-load.d12:02
Chipacazyga— +1 (with a comment)12:03
jdstrandmorphis: re selinux> yes, though selinux only has rudimentary dbus mediation compared to apparmor12:03
morphisjdstrand: yeah sadly, but this is something we need to talk in the near future12:03
morphisjdstrand: having this on my road map for cross-distro after I am through all the others things :-)12:03
jdstrandmorphis: this was actually discussed a good bit in the Hague12:04
zygajdstrand: FYI, overlayfs got good selinux support lately, is that because LSMs got improved or and so apparmor "groks" overlayfs automatically or is that selinux specific, do you know?12:04
morphisjdstrand: oh great, seems like I missed that session :-)12:04
morphisjdstrand: are there any notes available?12:04
jdstrandmorphis: I suspect that the list of interfaces available will need to be different for an apparmor enabled system vs an selinux system12:04
morphisjdstrand: yeah, maybe12:05
jdstrandmorphis: it was inconclusive. various problems were identified because of the capabilities of each system and how they both approach MAC differently12:05
zygaChipaca: thanks for the hint, applied!12:06
jdstrandmorphis: when you are starting to write selinux policy, you'll want to do a hangout with at least me, Tyler and jj12:06
morphisjdstrand: absolutely12:06
Chipacazyga— as i said the compiler is probably good enough nowadays to not make it necessary, but sometimes (like here) it's probably clearer anyways12:06
zygaChipaca: yeah, I really like it, feels pythonic in good way :)12:07
Chipaca:-)12:07
morphisjdstrand: this is currently somewhere on the horizon but I want to have proper CI for those systems in place first12:07
Chipacazyga— yeah12:07
zygamorphis: I think you could start by trying to run unit tests on snapd build on fedora12:07
zygamorphis: that will show looooots of red because of /snap shift12:07
morphiszyga: yeah :-)12:07
=== cachio_afk is now known as cachio
zygamorphis: niemeyer suggested that we add a mock call so that those tests assume /snap is still in place12:08
zygamorphis: for spread you will need a different tactics I fear, as those are integration tests12:08
jdstrandmorphis: it is possible to do things like: the process with this label can talk to the process with that label over dbus with selinux (eg, I can talk to all of network-manager or I can't talk to network-manager at all), but for carving out parts of the dbus api-- no12:08
zygamorphis: while not perfect, I had an idea with snapd-fhs package that puts a /snap -> /var/lib/snapd/snap symlink in place12:08
morphiszyga: yeah, mock call sounds good, will need to look into that once we're through the current phase of getting distros into shape12:08
zygamorphis: as a $0.01 solution12:08
morphiszyga: depends if we can that approved by the other distros12:08
jdstrandmorphis: but there are other issues that aren't at the top of my head12:09
jdstrand(even with dbus)12:09
zygajdstrand: are you sure? I saw some fine-grained mediation for dbus + selinux lately (but maybe I was confused)12:09
zygamorphis: for spread testing12:09
zygamorphis: not for anything else12:09
morphisjdstrand: I think we should come together at some point and just brainstorm to see what problems we have and to guess possible solutions12:09
jdstrandzyga: patches to dbus deamon?12:09
morphiszyga: flatpak uses a proxy for that, maybe they added selinux to that12:10
zygajdstrand: I think to selinux, I saw policy language that was referring to specific methods12:10
* zyga googles12:10
jdstrandif you're talking flatpak, they either write services where the whole api is safe or use a proxy12:10
morphisjdstrand: right12:11
zygajdstrand: no, not flatpak12:11
zygajdstrand: I know they use a proxy, it's a different approach altogether12:11
pedronisfgimenez: mvo: we are hitting /dev/ram0 issues now in the spread tests12:12
zygapedronis: https://forum.snapcraft.io/t/spread-tests-fail-on-lack-of-dev-ram0/7712:13
zygajdstrand: I cannot find it, all I can find now confirms what you said earlier (no per-method control)12:14
zygait would be nice if selinux supported that actually12:14
jdstrandzyga: indeed it would :)12:15
zygajdstrand: the proxy based approach has one advantage, it can be rolled out on any old kernel12:15
zygajdstrand: (and any old dbus)12:15
zygajdstrand: do you think we should write such proxy?12:15
jdstrandzyga: but the kdbus discussions showed that people weren't really interested in it12:15
zygajdstrand: in selinux over dbus?12:16
zygajdstrand: I saw that kdbus disposed the xml language too12:16
zygajdstrand: but I wasn't aware of any other details12:16
jdstrandzyga: I can't make that recommendation. putting a proxy in front of dbus-daemon would slow things down. it would have to be measured. it is certainly possible12:17
* Chipaca ~> lunch12:17
=== hikiko is now known as hikiko-ln
jdstrandzyga: the gist of the kdbus conversations was that "selinux doesn't do interface/path/member mediation, why should we allow apparmor to do that? either the service is safe or it isn't"12:18
zygajdstrand: hmm, who expressed this view? kernel developers or kdbus developers?12:19
jdstrandit's an interesting argument that has merit, but we fell on different sides. we felt it was useful to go to that depth, they (kdbus guys) did not12:20
jdstrandzyga: yes12:20
jdstrandif you recall, the kdbus discussions were lennart, kay and greg12:20
zygajdstrand: well, I think I agree with kdbus developers for _new_ services written by security aware developers but that's not a good coverage of the software people want to use12:21
jdstrandDan got into it a little bit, but not too much12:21
zygajdstrand: what was his view?12:21
zyga(and the flatpak dbus proxy is a perfect example of that)12:22
jdstrandyou should read the thread12:22
zygajdstrand: is that the kdbus thread? any hints on what to google?12:22
zygamvo: I applied your feedback on https://github.com/snapcore/snapd/pull/310212:25
mupPR snapd#3102: interfaces/mount: add function for parsing mount entries <Created by zyga> <https://github.com/snapcore/snapd/pull/3102>12:25
zygamvo: if we could merge that I have two more proposals to do on top12:25
jdstrandzyga: apparmor and kdbus12:25
zygaOK12:26
zygathanks!12:26
cachiojdstrand, hey, fyi https://bugs.launchpad.net/apparmor/+bug/167758712:30
mupBug #1677587: apparmor is denying access to executables shared through content interface <AppArmor:New> <https://launchpad.net/bugs/1677587>12:31
Son_Gokujdstrand: there's already a bit of a rudimentary selinux policy in data/selinux12:39
Son_Gokuit needs beefing up, but at least it's enough to get snapd working12:39
Son_Gokusnapd can't yet run properly confined :(12:39
mvozyga: looking now, sorry for the delay12:45
zygano worries12:47
* zyga is a sad panda12:47
zygacan't load package: package github.com/snapcore/snapd/cmd/snap-update-ns: use of cgo in test /home/zyga/go/src/github.com/snapcore/snapd/cmd/snap-update-ns/bootstrap_test.go not supported12:47
mupPR snapd#3102 closed: interfaces/mount: add function for parsing mount entries <Created by zyga> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/3102>12:49
Chipacamvo, niemeyer, I'll be missing the standup today12:50
mvoChipaca: no worries12:50
fgimenezogra: snap kernel on edge is ok again \o/ https://travis-ci.org/snapcore/spread-cron/builds/21673415812:52
mvofgimenez: what happend? how did it get fixed?12:53
zygamvo: it was reverted12:53
zygamvo: look at this thread: https://forum.snapcraft.io/t/spread-tests-fail-on-lack-of-dev-ram0/77/1612:53
zygamvo: specifically this https://forum.snapcraft.io/t/spread-tests-fail-on-lack-of-dev-ram0/77/1312:54
mvota12:55
jdstrandcachio: thanks, responded12:59
jdstrandSon_Goku: yeah, I was talking about the steps after that-- snap confinement and snap to snap communications13:00
fgimenezmvo: yep, it was finally fixed, i'll file a bug about the problem, ogra where should i report it?13:00
ografgimenez, against linux i guess13:00
fgimenezogra: ok thanks13:01
sergiusensstgraber: hey, `lxc image list ubuntu:` doesn't return any 16.04 image (and it seems the aliases are all wonky too)13:02
=== hikiko-ln is now known as hikiko
jdstrandroadmr: hi! can you pull r865? this isn't urgent and has code changes (tested of course :). I suggest not rolling out before weekend (ie, follow whatever staging procedures you'd normally use for code changes)13:04
niemeyerChipaca: Ack, thanks for the note13:04
niemeyerHello all13:05
roadmrjdstrand: sure! ok, let me check the commit log to see what the changes are about. But I'll have it in SCA trunk in a sec.13:05
jdstrandroadmr: code changes aren't extensive, it is just more than the last few pulls I've requested,13:09
mupPR snapd#3114 opened: interfaces/mount: add function for saving fstab-like file <Created by zyga> <https://github.com/snapcore/snapd/pull/3114>13:19
morphisSon_Goku: hm, when I try to build snapd with mock for rawhide, shouldn't it fetch the golang-* packages we already pushed there?13:26
morphisalways fails with saying it can't find those deps13:26
Son_Gokumirror sync is not complete, I suspect13:26
Son_Gokuyou can create custom mock targets to use13:27
Son_GokuI have a fedora-rawhide-x86_64-koji config that I use to access Koji's internal repos, since they are publicly accessible13:27
Son_GokuI'll paste it for you13:27
morphisthanks13:28
Son_Gokumorphis: https://da.gd/Oh2U13:28
Son_Gokusave it as "fedora-rawhide-x86_64-koji.cfg"13:29
Son_Gokuthen do "mock -r </path/to/fedora-rawhide-x86_64-koji.cfg> </path/to/package.src.rpm>"13:29
morphisok13:29
zygaChipaca: hey13:32
zygaChipaca: you around?13:32
Chipacazyga— with some latency yes13:32
zygaChipaca: can you please eyeyball https://github.com/snapcore/snapd/pull/3103/files13:33
mupPR snapd#3103: interfaces/mount: add function for parsing fstab-like file <Created by zyga> <https://github.com/snapcore/snapd/pull/3103>13:33
zygaChipaca: if not too inconvenient13:33
Chipacano probs13:33
fgimenezhey pstolowski during the 2.23.6 candidate validation vigo got this error on dragonboard http://paste.ubuntu.com/24281125/ afaik you have been working in this area, could you please take a look when you have a moment?13:38
=== jjohansen1 is now known as jj-cloaked
zyganiemeyer: do you think we should have a "casual" category for posts that would not be related to snaps in any way?13:41
ogra"gossip"13:44
ogra:)13:44
niemeyerHmm.. not sure.. problem is that they'd show in forum.snapcraft.io nevertheless..13:45
niemeyerLet me see if there's some sort of "only inside category" setting13:45
zyganiemeyer: https://forum.snapcraft.io/t/should-we-have-category-casual-for-daily-chatter/80/113:45
zyganiemeyer: I see longue13:45
zyganiemeyer: but not sure if that's one post13:45
zyganiemeyer: or a category13:45
Chipacazyga— +1'ed, with two ignorable notes13:47
=== jj-cloaked is now known as jjohansen
pedronisniemeyer: I added the comment blocked to snapd#3113 if you want to review13:49
mupPR snapd#3113: overlord/snapstate: unlock/relock the state less, especially not across mutating the SnapState of a snap <Critical> <Created by pedronis> <https://github.com/snapcore/snapd/pull/3113>13:49
pedronisniemeyer: I put the PR link also in the forum13:50
pedroniss/blocked/block/13:50
fgimenezogra: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/167762213:56
mupBug #1677622: missing ramdisks in latest amd64 kernel snap <linux (Ubuntu):New> <https://launchpad.net/bugs/1677622>13:56
ografgimenez, great, thx13:57
niemeyerpedronis: Ack, thanks14:11
pstolowskifgimenez, sorry, i was in another meeting and missed your message. will take a look14:18
fgimenezpstolowski: np thanks14:19
=== josepht` is now known as josepht
mupPR snapd#3115 opened: interfaces/unity7: support unity messaging menu <Created by jdstrand> <https://github.com/snapcore/snapd/pull/3115>14:31
King_InuYashazyga: morphis: make sure you guys give feedback on tomb updates: https://bodhi.fedoraproject.org/updates/?packages=golang-github-go-tomb-tomb14:34
King_InuYashamorphis: ahh, I see you did14:35
pstolowskifgimenez, this is super weird, I don't see a reason for it too fail on one arch and not others. any chance the tests were executed against an older revision of snapd for some reason?14:35
King_InuYashazyga: please do so, so that it'll sync out to stable14:35
pstolowskivigo, ^ ?14:36
fgimenezpstolowski: i don't think so, dragonboard is notably slower than other platforms, afaik is the only diference, vigo can give you more details14:36
pstolowskifgimenez, ah, interesting14:36
ograoh ? dragonboard is slower ?14:37
ogra(nobody told me yet)14:37
vigopstolowski, my mistake I though I switched to the new branch14:38
pstolowskivigo, ah, so all good?14:43
vigopstolowski, re-running spread tests14:43
roadmrhey folks, who can help me with the discourse.snapcraft.io forum? I tried signing up but it's not sending me the confirmation e-mail, so I can't really use it yet :(14:47
ograniemeyer, is the admin ^^^14:47
roadmrthanks!14:48
niemeyerroadmr: Heya14:53
niemeyerroadmr: Let me test the email sending14:53
roadmrthanks niemeyer!14:54
roadmrlet me know if you need me to do anything14:54
niemeyerroadmr: Problem is in the system.. I'm probably blowing some quota14:56
roadmroops :(14:56
stgrabersergiusens: that would be a CPC problem, the LXD team doesn't control the ubuntu: remote15:05
mupPR snapd#3116 opened: interfaces: allow executing ld.so (needed with new AppArmor base abstraction) <Created by jdstrand> <https://github.com/snapcore/snapd/pull/3116>15:08
mupPR snapd#2833 opened: many: allow core refresh.schedule setting <Created by mvo5> <https://github.com/snapcore/snapd/pull/2833>15:09
vigopstolowski, ping15:12
vigoI ran again against current branch in i386 and failed again15:12
vigohttps://pastebin.canonical.com/184322/15:13
niemeyerroadmr: Looks like it was actually my own provider that crashed.. they have a critical announcement saying they're working on it15:14
niemeyerroadmr: I've shifted it to Canonical's SMTP.. can you please give it a try now?15:14
roadmroh whoops :)15:14
roadmrniemeyer: sure thing, here I go15:15
niemeyerroadmr: You _migth_ have received the email already, actually15:15
roadmrniemeyer: none of the previous attempts have arrived, I just requested a new one, will wait a bit for it15:17
niemeyerroadmr: Thanks15:17
pstolowskivigo, hmm ok let me try it locally15:23
roadmrniemeyer: still nothing. ~10 mins feels slowish for an e-mail, right?15:25
ograniemeyer, is there a setting in discourse that would open links in additional tabs or new windows ? currently a link i click replaces the forum ....15:28
ograwould be nice to have that opening in external pages15:28
niemeyerroadmr: Yeah15:30
pstolowskivigo, I just run this specific test against master and it passed here; are you running it against current master or a tagged version?15:30
niemeyerroadmr: There's definitely something broken, and I'm having  a slightly harder time debugging because my own email is broken due to the provider15:31
niemeyerroadmr: Or there's just a big queue15:31
vigopstolowski, np I updated to a non existing branch and lacked tests15:31
vigoit is correctly set now15:31
roadmrmaybe queue + retries15:31
=== chihchun is now known as chihchun_afk
niemeyerkyrofa: Did you just get an email from the forum?15:32
pstolowskivigo, hmm ok I'm confused now :), so is it all good and passing now after all?15:32
kyrofaniemeyer, just now? No15:32
niemeyerpopey: What about you?15:33
niemeyerAccording to the logs the queue is slowly going out.. but I'm not sure about whether the SMTP host from Canonical has any constraints in terms of origin, etc15:34
popeyhmm?15:36
niemeyerYep, there we go..15:37
niemeyer[Sender] 550 relay not permitted15:37
roadmroops :)15:37
niemeyerWill need to do something else15:37
popeyyeah, I have no emails for a while15:37
popeyI'd recommend using a cloud email provider. flexiondotorg has done this at scale, and knows a good option15:37
ograniemeyer, google smtp ...15:37
flexiondotorgNo, don't use Google SMTP. Bad thing _will_ happen.15:38
ograoh ?15:38
flexiondotorgI use Sendgrid. It's brilliant.15:38
popeyyeah, you get blocked from google for using it too much15:38
ograwhat are these bad things ?15:38
popeythey have very strict limits15:38
niemeyerogra: What is the password there?15:38
ograoh15:38
flexiondotorgGoogle rejects lots of mail.15:39
flexiondotorgSo the mailing list features of Discourse become unreliable and notifications don't work properly.15:39
ograniemeyer, well, obviously gmail is a bad idea ...15:39
niemeyerflexiondotorg: Yeah, that was my idea too (sendgrid), except they deactivated my account for inactivity15:39
flexiondotorgSendgrid is the way to go.15:39
flexiondotorgI have tried them all with Discource.15:39
niemeyerand guess what, I need email to re-activate it.. #FML15:39
ogralol15:39
roadmrhehe :)15:41
morphisPharaoh_Atem, King_InuYasha: lets give https://paste.fedoraproject.org/paste/DMpW-ZW11QIB76FA9DBnEF5M1UNdIGYhyRLivL9gydE= a try15:41
loolcjwatson: Hey15:47
loolcjwatson: I hope you had a good leave (if you're not back ignore this)15:47
loolcjwatson: I had a "store upload failed" for one snap build out of 4, I pressed "Retry" button, upload worked, but snap wasn't published to the channels it was supposed to be published in15:48
loolcjwatson: really minor but thought I'd mention it; would you like me to report this somewhere?15:48
ogralool, are you sure it wasnt published ? note there is quite a delay15:49
* ogra fell for that multiple times in the past 15:49
loologra: it passed review, and then was ready to publish15:49
loolI just clicked in the web UI to do so15:49
ograright, and then between 10 and 20min later it publishes ...15:49
loolit had the "thumb up" icon15:49
ograyeah15:49
looland no channel selected15:50
ograi see that at times for the core snap daily build ... but as i said, afetr a while it publishes then15:50
cjwatsonlool: sure, report that as a Launchpad bug15:51
kyrofaogra, lool I've seen the same 10 minute delay or so15:51
loolcjwatson: ok, seems to be normal; perhaps I only saw it because of the retry15:51
roadmrjdstrand: hello! oops, "unexpected output" from tools r865...15:54
cjwatsonlool: so I mean there's the standard problem that we currently have to poll the store to find out when it's done with processing the actual upload, and we don't want to lock up a worker waiting for it, so we poll every so often15:54
morphisPharaoh_Atem, King_InuYasha: lets see how it goes: https://koji.fedoraproject.org/koji/taskinfo?taskID=1868400215:55
loolcjwatson: fine with me; I thought I had uncovered a weird case15:55
jdstrandroadmr: how did you invoke it?15:56
jdstrandroadmr: (I think I know the issue though)15:56
roadmrjdstrand: from latest trunk: $ PYTHONPATH=$PWD ./bin/click-review /tmp/hello-classic-tomechangosubanana-1_foo48_amd64.snap15:56
roadmrjdstrand: maybe you forgot to bzr add overrides?15:56
roadmrbecause "ImportError: No module named 'clickreviews.overrides'"15:57
Pharaoh_Atemmorphis: you've already started a scratch build?15:57
morphisPharaoh_Atem: yes15:57
roadmrjdstrand: (and I guess the trace is what the store is complaining about).15:57
morphisPharaoh_Atem: tried to a local vm for i386 up but failed .. somehow vbox doesn't want to boot the fedora i386 images15:58
jdstranddid I forget to bzr add the file?15:58
morphisPharaoh_Atem: and mock doesn't want to work on lxd15:58
Pharaoh_Atemmorphis: you could have just done a mock build for i386 on x86_^415:58
Pharaoh_Atem*x86_6415:58
jdstrandcrap I did15:58
roadmrjdstrand: maybe :( so it'd work locally...15:58
morphisPharaoh_Atem: tried this but failed :-)15:58
morphisPharaoh_Atem: need to play a little bit more and look at what I am doing than just doing it next to a meeting15:59
jdstrandroadmr: r866. sorry16:00
roadmrjdstrand: no problem, at least we caught it quickly :)16:00
=== JanC is now known as Guest23500
=== JanC_ is now known as JanC
morphisPharaoh_Atem: we're coming closer: https://koji.fedoraproject.org/koji/taskinfo?taskID=1868426816:15
morphisPharaoh_Atem: for the ppc64 build I don't have any idea yet16:18
Pharaoh_Atemmorphis: did you ask for a VM in #fedora-ppc yet?16:21
morphisPharaoh_Atem: not yet16:23
morphismvo, zyga: are we building snapd in ubuntu for ppc64?16:24
Pharaoh_Atemmorphis: you're not in Debian16:27
Pharaoh_Atembut in Ubuntu, you're building against powerpc and ppc64el16:27
morphisyeah, just saw that16:27
morphisjust want to get a baseline for things to look in16:27
Pharaoh_AtemI'm *guessing* that powerpc is the < POWER 7 big endian architectures16:28
Pharaoh_Atemaka, the 32-bit ones16:28
naccPharaoh_Atem: yes, BE power16:28
Pharaoh_Atemold BE POWER, but yes16:29
Pharaoh_Atemmorphis: so endianness shouldn't break it :/16:29
morphisPharaoh_Atem: it shouldn't16:30
morphisbut also we have go 1.6 vs. 1.816:30
Pharaoh_Atemright16:30
morphislatest we have in ubuntu is 1.7 in zesty16:30
morphisPharaoh_Atem: sad that the build log doesn't give any error16:31
morphisPharaoh_Atem: also interesting is that this (if the log can be trusted) fails when building golang.org/x/net/context/ctxhtt16:35
Pharaoh_Atemwell, time to test a theory, I guess16:42
morphisPharaoh_Atem: drop the guy (sharkcz) a mail to get VM access16:43
Pharaoh_Atemmorphis: you mean you sent him an email16:46
morphisyes16:46
morphiss/drop/dropped/16:46
zygamorphis: yes we do build snapd for ppc6416:56
morphiszyga: any idea why https://kojipkgs.fedoraproject.org//work/tasks/4273/18684273/build.log fails?16:57
morphiszyga: our last issue on the way to have snapd in rawhide :-)16:57
renatujdstrand, could you please :D? https://myapps.developer.ubuntu.com/dev/click-apps/6676/rev/2/16:57
zygamorphis: checking16:59
zygamorphis: sorry, where is the error there?16:59
zygathat's pretty uncomprehensible to me17:00
morphiszyga: that is the question :-)17:00
zygait looks like /usr/lib/golang/pkg/tool/linux_ppc64/compile -o $WORK/golang.org/x/net/context/ctxhttp.a -trimpath $WORK -p golang.org/x/net/context/ctxhttp -complete -buildid dd5b033021ca065fee8c7c29c22a9306c1500731 -D _/usr/share/gocode/src/golang.org/x/net/context/ctxhttp -I $WORK -I /usr/share/gocode/pkg/linux_ppc64 -pack ./ctxhttp.go fails to compile17:00
morphisyeah, trying to add a -v to that right now to get more details17:00
zygai'd add --quiet to see less noise17:01
zygaand see just "this is what failed"17:01
morphisPharaoh_Atem: did you saw this with your bundled builds too?17:01
jdstrandrenatu: done17:01
Pharaoh_Atemthe patches don't apply17:02
morphisPharaoh_Atem: ah17:02
zygawhy would that be only on one arch?17:02
Pharaoh_Atemit's the only big endian arch17:03
morphis"patch unexpectedly ends in middle of line"17:03
morphisbut if something wouldn't apply it would fail the build17:03
renatujdstrand, thanks17:03
zygaPharaoh_Atem: how does that matter for patches?17:03
renatujdstrand, did you add it to whitelist?17:03
zygaPharaoh_Atem: note that this builds on ubuntu, we don't know what really fails as that log is garbage-ish17:04
jdstrandrenatu: yes17:04
Pharaoh_Atemzyga: since the systemd unit patches fail to apply, the build stops17:04
zygaPharaoh_Atem: aha, do we have any arch-specific patches?17:05
renatujdstrand, thanks twice ;)17:05
Pharaoh_Atemnope17:05
Pharaoh_Atemthe patch that failed was the one that rewrites the systemd unit files to use templates17:05
Pharaoh_Atemapparently it couldn't find the location to apply the files17:05
zygaPharaoh_Atem: I still don't understand how that only fails on ppc6417:06
* Pharaoh_Atem shrugs17:06
zygaPharaoh_Atem: I bet I'm missing something :/17:06
morphisPharaoh_Atem: where do you see that in the logs?17:06
morphis+ /usr/bin/cat /builddir/build/SOURCES/PR3084-packaging-use-templates-for-systemd-units.patch17:06
morphisdoesn't give any error17:06
Pharaoh_Atemhttps://koji.fedoraproject.org/koji/taskinfo?taskID=1868511617:07
Pharaoh_Atemhttps://kojipkgs.fedoraproject.org//work/tasks/5116/18685116/build.log17:07
morphisah, that is a different build17:07
Pharaoh_Atemit fails because mvo strips .gitignore17:07
morphisah so you're talking about the vendorized build?17:08
Pharaoh_Atemyes17:08
morphisah :-)17:08
morphisthat confused zyga I guess17:08
Pharaoh_Atemyou asked about bundled/vendorized build17:08
morphisyeah I know17:08
morphishowever close to EOD, will look again into this tomorrow morning17:09
zygamorphis: you know, just kill ppc6417:09
zygaand revisit next time17:09
morphisPharaoh_Atem: ^^17:09
Pharaoh_Atemfine17:10
Pharaoh_AtemI'll do that for now17:10
morphiszyga: you know, I am pragmatic, I am all in for those things :-)17:10
zygawhile I'd like to see ppc64 flourish the arch is dead dead dead and will stay dead unless something happens17:10
morphis:-)17:12
Pharaoh_Atemzyga: we do not support s390x, I guess?17:13
Pharaoh_Atemor mips?17:13
zygaPharaoh_Atem: s390x is "supported"17:13
zygaPharaoh_Atem: I think at least17:13
zygaPharaoh_Atem: mips no because there's no mips build of ubuntu17:13
zygaPharaoh_Atem: mips would be cool but it seems to be dominated by 4MB flash crap devices17:14
Pharaoh_Atemzyga: Fedora is in the middle of a MIPS bootstrap, which is why I asked17:17
zygaPharaoh_Atem: do you know what kind of hardware is used?17:18
Pharaoh_Atemnot yet, no17:18
Pharaoh_AtemI've not talked to Michel about it17:18
zygaPharaoh_Atem: I have a ci20 but I must sadly say it's crap17:19
zygaPharaoh_Atem: the kernel crashes in minutes17:19
mupPR snapd#3116 closed: interfaces: allow executing ld.so (needed with new AppArmor base abstraction) <Created by jdstrand> <Merged by jdstrand> <https://github.com/snapcore/snapd/pull/3116>17:19
Pharaoh_Atemzyga: I need you to retire snap-confine for me17:25
zygaPharaoh_Atem: how do I do that?17:26
Pharaoh_Atemzyga: fedpkg co snap-confine && fedpkg switch-branch f24 && fedpkg retire "Merged into snapd" && fedpkg switch-branch f25 && fedpkg retire "Merged into snapd" && fedpkg switch-branch f26 && fedpkg retire "Merged into snapd" fedpkg switch-branch master && fedpkg retire "Merged into snapd"17:27
Pharaoh_Atemerr17:27
Pharaoh_Atemfedpkg co snap-confine && cd snap-confine && fedpkg switch-branch f24 && fedpkg retire "Merged into snapd" && fedpkg switch-branch f25 && fedpkg retire "Merged into snapd" && fedpkg switch-branch f26 && fedpkg retire "Merged into snapd" fedpkg switch-branch master && fedpkg retire "Merged into snapd"17:27
zygaPharaoh_Atem: thanks!17:27
zygaPharaoh_Atem: I'll do that shortly :)17:27
Pharaoh_Atemactually, need to change command slightly17:27
Pharaoh_Atemone second17:27
Pharaoh_AtemI'm going to merge the commit I already made to all branches17:29
morphisPharaoh_Atem: you're going to trigger new builds for snapd now or is that a thing for tomorrow?17:30
Pharaoh_AtemI'm doing it now, yes17:30
morphisPharaoh_Atem: great, then we can call out for testing in the community tomorrow17:32
Pharaoh_Atemzyga: pkgdb-cli orphan --retire snap-confine f24 && pkgdb-cli orphan --retire snap-confine f25 && pkgdb-cli orphan --retire snap-confine f2617:32
Pharaoh_Atemzyga: run this asap17:32
zygaPharaoh_Atem: ack17:39
Pharaoh_Atemzyga: I've already retired it from rawhide, and you're the only person who can run it for the older branches17:39
Pharaoh_Atembuilding F26 package now17:40
Pharaoh_Atemat least now the buildsystem will stop bitching about the snapd-glib broken dep17:40
zyga60 seconds17:40
zygaPharaoh_Atem: it said I must use fedpkg retire first17:42
Pharaoh_Atemthen do that17:42
zygaay17:43
zygaPharaoh_Atem: push got rejected17:43
zygahmmm17:43
zygaPharaoh_Atem: hook declined update17:44
Pharaoh_Atemdid you do it with a fresh checkout?17:44
zygaPharaoh_Atem: no, with one I had on disk17:44
Pharaoh_Atemit should already have "dead.package" files on every branch from f24 on up17:44
zygaPharaoh_Atem: shall I try with a fresh one?17:44
Pharaoh_Atemyes17:44
zygaok17:44
Pharaoh_Atemactually a fresh checkout may let you just use pkgdb CLI17:44
Pharaoh_Atembut try with fedpkg retire17:44
Pharaoh_Atemif fedpkg retire works, more power to us :)17:45
zygaPharaoh_Atem: said I'm not allowed to retire f2517:46
zygahmmm17:46
zygatrying pkgdb17:46
zyganope17:46
zygaany ideas?17:46
Pharaoh_Atemzyga: pop into #fedora-releng and ask about it17:47
zygaPharaoh_Atem: "dead.package found" but then says "no `dead.package' for snap-confine on f24"17:47
zygaOK17:47
jdstrandogra: can you kick off a build for linux-generic-bbb?17:50
Pharaoh_Atemmorphis, zyga: snapd FTBFS on F24 and F2517:54
Pharaoh_Atemoh wait, I know why17:54
Pharaoh_Atembecause I need buildroot overrides17:54
Pharaoh_Atemduh17:54
Pharaoh_Atemzyga: drop your watch commits and approvacls here: https://admin.fedoraproject.org/pkgdb/package/rpms/snap-confine/17:57
zygaPharaoh_Atem: trying17:57
=== TinoGuest_ is now known as TinoGuest
zygaPharaoh_Atem: I managed to orphan in f24/2518:00
zygaPharaoh_Atem: can you check18:01
zygaPharaoh_Atem: I'm not sure what to do18:01
Pharaoh_Atemchange your watchcommits to obsolete here: https://admin.fedoraproject.org/pkgdb/package/rpms/snap-confine/acl/watchcommits/18:01
zygathat's done18:02
Pharaoh_Atemthere, that's taken care of18:03
niemeyerroadmr: Should be all sorted out, btw18:04
niemeyerogra: core-build reporting here too18:04
Pharaoh_Atemzyga: could you give positive karma on https://bodhi.fedoraproject.org/updates/?packages=golang-github-go-tomb-tomb ?18:16
Pharaoh_Atemthat way it'll cycle out to stable quickly?18:16
zygasure18:17
Pharaoh_Atemall the ones with +2 need good karma18:17
Pharaoh_Atemthat way, they'll sync out with stable updates push in an hour or so18:18
Pharaoh_Atemat least, I think it's in an hour18:18
Pharaoh_Atemthen I don't have to do too many buildroot overrides18:18
zygaPharaoh_Atem: done18:21
zygaPharaoh_Atem: gee, I should manage something myself, this feels good18:21
zygaPharaoh_Atem: just golang packages are not very interesting "works for me" is hard to tes18:22
zygatest18:22
jdstrandkyrofa: to save you time: https://github.com/snapcore/snapd/pull/3112#discussion_r10900857618:57
mupPR snapd#3112: interfaces: add a joystick interface <Created by kyrofa> <https://github.com/snapcore/snapd/pull/3112>18:57
kyrofajdstrand, hahaha, right after I commented, I saw "AppArmor pcre syntax (currently not supported)" in the reference18:57
kyrofaFelt dumb18:57
kyrofajdstrand, the "Documentation of language syntax" above is what misled me18:58
jdstrandno worries. it looks like regex sometimes, but it isn't18:58
zygajdstrand: could you do a quick review for getmntent replacement?18:59
zygahttps://github.com/snapcore/snapd/pull/3103#discussion_r10892774218:59
mupPR snapd#3103: interfaces/mount: add function for parsing fstab-like file <Created by zyga> <https://github.com/snapcore/snapd/pull/3103>18:59
jdstrandzyga: I cannot, I'm time-shifting today and will be on the road in a few minutes. if you need it today, perhaps ask tyhicks to see if he can put someone on it, otherwise it will have to wait19:01
kyrofajdstrand, wait, I'm a little confused. The PR in its current state will allow /dev/input/js. Is your snippet different?19:01
zygajdstrand: OK19:01
zygajdstrand: it's okay, it's not urgent19:01
kyrofajdstrand, you say "if you want to support /dev/js"19:01
zygakyrofa: maybe you? it's super short and I have one review already19:02
jdstrandkyrofa: sorry I wrote the comment too fast. I meant to have input/ in all reference to /dev/js19:03
kyrofajdstrand, I know what you meant-- I'm really talking about js with no numbers following19:03
jdstrandkyrofa: do you want no numbers to be supported too?19:04
kyrofajdstrand, at least in my experimentation, it always has a number19:04
jdstrandkyrofa: then leave it as is. reading https://github.com/torvalds/linux/blob/master/Documentation/admin-guide/devices.txt it seems it always has a number19:05
kyrofajdstrand, good deal19:05
zygajdstrand: note that update-ns is not setuid root19:06
zygajdstrand: it's just a program19:06
Pharaoh_Atemzyga: I'm sure you have some other interesting software you'd like in Fedora :)19:06
zygajdstrand: if someone makes it crash, well, fine (though I think the current code is written in a way that won't easily crash)19:06
jdstrandkyrofa: actually in reading that I'm reminded that you also want: /run/udev/data/c13:{[0-9],[12][0-9],3[01]} r,19:06
kyrofazyga, sorry man, I have no context for that review, I couldn't do it justice19:06
zygaPharaoh_Atem: I'll think of something, maybe made in C, without many deps19:06
zygakyrofa: no worries, thanks19:07
kyrofajdstrand, whoa :P19:07
zygakyrofa: I think your brain just exploded19:07
jdstrandzyga: I know it isn't setuid root. but if an unprivileged user can make snapd call update-ns with arbitrarily controlled arguments, then the unpriv user can try to attack update-ns19:08
kyrofazyga, he says it so casually. "By the way, I should probably mention you need this insane glob in there"19:08
zygajdstrand: update-ns is only called when we connect/disconnect content19:08
zygajdstrand: and the argument is always just the snap name19:08
zygajdstrand: no input19:08
kyrofajdstrand, is that just where udev places the in-affect rules?19:10
jdstrandkyrofa: no, that is just some udev info on the device that some libraries like to read. go ahead and cat /run/udev/data/c13:0 if js0 is plugged in19:11
jdstrandzyga: can you add a comment to the PR that the arguments to update-ns are not user-controllable (like you just did here)19:11
kyrofajdstrand, huh, neat19:12
jdstrandok, heading out, 'see' you monday :)19:12
zygayes19:12
zygao/19:12
jdstrandthanks19:13
pedronisniemeyer: have you looked at snapd#3113 ?19:22
mupPR snapd#3113: overlord/snapstate: unlock/relock the state less, especially not across mutating the SnapState of a snap <Critical> <Created by pedronis> <https://github.com/snapcore/snapd/pull/3113>19:22
niemeyerpedronis: Not yet.. after solving a couple of details in the forum, I'm now running through the new threads and opening the PR review requests I found there in new tabs.. then will look through them all19:23
niemeyerpedronis: I can look at that one now if you can make good use of immediate feedback19:23
JamieBennettniemeyer: can we please enable other forms of auth on the forum for new users? Apparently its pretty easy to do.19:26
niemeyerJamieBennett: https://forum.snapcraft.io/t/support-for-sso-on-forum-snapcraft-io/75/519:26
JamieBennettRight but it would be good to enable that early no?19:27
pedronismvo: there's a bunch of autopkgtest failing with something like: 2017/03/30 18:00:26 Discarding autopkgtest:ubuntu-16.04-amd64, cannot connect: cannot connect to autopkgtest:ubuntu-16.04-amd64: ssh: must specify HostKeyCallback19:27
roadmrthanks niemeyer ! I just got the confirmation e-mail. Awesome :)19:43
niemeyerpedronis: Reviewed, if you're not watching the forum19:59
pedronisniemeyer: yes, answered you concerens in the review and the forum20:04
niemeyerpedronis: vvv20:04
niemeyerMan.. that never works well.. it's merged.20:04
mupPR snapd#3113 closed: overlord/snapstate: unlock/relock the state less, especially not across mutating the SnapState of a snap <Critical> <Created by pedronis> <Merged by niemeyer> <https://github.com/snapcore/snapd/pull/3113>20:04
niemeyermup: You're late!20:05
mupniemeyer: Roses are red, violets are blue, and I don't understand what you just said.20:05
pedronisniemeyer: thanks, was about to merge it20:07
pedronisniemeyer: about the aliases gdoc, I was a bit confused by your comments, are you planning to move to a wiki entry in the forum? or something I shoul do?20:13
niemeyerpedronis: I will.. I have it half-way done and ended up being distracted by other concerns yesterday20:13
niemeyerpedronis: Should be there by tomorrow20:13
pedronisok20:13
pedronisnp20:13
pedronisniemeyer: I updated snapd#3044 to follow current direction21:27
mupPR snapd#3044: snapstate: more helpers to work with alias states (aliases v2) <Critical> <Created by pedronis> <https://github.com/snapcore/snapd/pull/3044>21:27
* pedronis calls it a day21:27
niemeyerpedronis: Sweet, thanks!21:27
niemeyerI'm going to (try to) step out as well.. haven't had much sleep lately21:28
cachiojdstrand, do you know if there is a way to uninstall + install thte same snap without download it again?22:09
kyrofacachio, snap download it first22:15
kyrofacachio, that will obtain both the snap and its assertion. If you `snap ack` the assertion before installing it, you don't need --dangerous and it'll still update from the store22:16
cachiokyrofa, awesome, I'll try that, thanks22:16
kyrofacachio, I believe you'll only need to `snap ack` once, and install however many times, but don't quote me on that. Removing the snap could possibly remove the assertion22:17
cachiokyrofa, ok22:18
mwhudsoni don't think assertions are removed at all currently?22:23
mwhudsonnot sure either22:24
kyrofamwhudson, I suspect you're right, just unverified22:24
mwhudsonwhat's the easiest way to set up a daily build of a snap in launchpad?22:26
mwhudsonin the case where the branch containing the snapcraft.yaml does not change22:26
mwhudsonpresumably i could call the launchpad api from a cronjob but wondering if there is anything neater22:27
kyrofamwhudson, I use Travis daily jobs to make a new commit to change the version and force-push to a branch in LP which has a snap building/publishing on changes22:29
kyrofamwhudson, gnarly22:29
mwhudsonkyrofa: yeah, that doesn't sound much better than what i said22:29
kyrofamwhudson, in fact, I prefer your solution22:30

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