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

diddledankyrofa: I like the "potentially bonkers" comment :-D00:28
diddledanI'm sat here giggling to myself over that :-p00:29
mupBug #1745528 opened: snap icon available <Snappy:New> <https://launchpad.net/bugs/1745528>02:10
bashfulrobotAnyone around for a few (hopefully) quick questions?02:58
bashfulrobotIf not, I'll pop back in the AM (PST).02:59
bashfulrobotTY02:59
ikeymornin05:17
mborzeckimorning05:56
zyga-ubuntugood morning06:56
zyga-ubuntuFYI, I need to take today off,06:56
zyga-ubuntulast day of winter holidays for kids and I need to spend some time with them06:56
mupPR snapd#4532 closed: store: use the "publisher" when populating the "publisher" field  <Created by mvo5> <Merged by zyga> <https://github.com/snapcore/snapd/pull/4532>06:58
mborzeckizyga-ubuntu: hey, morning06:58
zyga-ubuntuhey!06:59
zyga-ubuntuI slept for hoooours06:59
zyga-ubuntuI woke up later at night and just briefly wandered here06:59
mborzeckiyeah, today is monday you know? :)06:59
zyga-ubuntuman, I missed that sleep06:59
zyga-ubuntuhaha!06:59
zyga-ubuntugood one :) I tried to fool our daughter a moment ago06:59
mborzeckihaha06:59
mborzeckimy kids are starting the break on monday ;)07:00
zyga-ubuntuoh, right :)07:01
mborzeckizyga-ubuntu: btw. sent you a small PR for snapd aur package: https://github.com/bboozzoo/aur-snapd/pull/1, nothing fancy07:01
mupPR bboozzoo/aur-snapd#1: snapd: fix generation of systemd unit files, use /etc/default/snapd as environment file <Created by bboozzoo> <https://github.com/bboozzoo/aur-snapd/pull/1>07:01
zyga-ubuntulooking07:03
zyga-ubuntudone07:03
mborzeckizyga-ubuntu: can you belive that indent is no longer package in arch?07:04
mborzeckii played with arch CI yday and i was like 'wtf?' when it failed on installing indent07:04
zyga-ubuntumborzecki: indent is a weird tool, I'd like to migrate away from it07:08
zyga-ubuntuand use clang-format07:08
zyga-ubuntunot only more widely available but much better output07:08
mborzeckizyga-ubuntu: briefly thought about dumping autotools in favor of cmake or meson, though the latter is not availble in 14.04 :/07:08
mborzecki`yaml.reader.ReaderError: unacceptable character #xdce2: special characters are not allowed` on arch tests/main/snap-info07:11
zyga-ubuntumborzecki: I cannot stand cmake syntax, I think ultimately what we have is bad but the alternatives are not widely available or are not fantastically better07:21
zyga-ubuntumborzecki: that's a curious one07:21
zyga-ubuntuI ran into it 100s of times07:21
zyga-ubuntubut it's a race somewhere07:21
zyga-ubuntumemory is corrupted07:21
zyga-ubuntuI dumped the yaml text when this happened07:21
zyga-ubuntuand I got random stuff all the time07:22
zyga-ubuntuit only ever surfaced on arch07:22
zyga-ubuntuperhaps due to a combination of compiler settings not used by other distributions07:22
zyga-ubuntuI didn't get to the bottom of it07:22
zyga-ubuntutry printing the buffer, I'm curious what you will get07:28
mborzeckizyga-ubuntu: found a related debian bug reported by Chipaca https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=80682607:28
mborzeckianyways, reading the patch explains why pretending we're using a utf8 locale fixes the problem07:29
mborzecki`LC_ALL=en_US.utf8 python3 check.py < out` works just fine07:29
zyga-ubuntumborzecki: how does python come into the picture?07:46
zyga-ubuntumborzecki: I thought this was from golang07:46
zyga-ubuntumvo: hey07:46
zyga-ubuntumvo: I'm off today07:46
zyga-ubuntuneed to leave in a few minutes anyway07:46
mborzeckizyga-ubuntu: no it's python3, there's a check.py script in tests/main/snap-info, we basically dump `snap info` output and then verify it with the script, and it chokes on the unicode up arrows07:47
mvozyga-ubuntu: hey, enjoy your day off07:49
mborzeckii still think that we should not produce any unicode output if locale does not support unicode07:49
mvomborzecki: not knowing much context I agree07:50
mvomborzecki: but that seems to be a broader issue, iirc our progress is also quite liberal with non ascii chars07:50
mborzeckimvo: the tests are using LANG=C.UTF-8 which is in a patched glibc, this does not work on arch, so the default ends up being C, `snap info` uses unicode characters in the output, the script checking `snap info`'s output is python3 which does magic behind the scenes depending on your locale, part of it i have already fixed, the other part makes pyyaml throw an exception when reading yaml input (ie.. snap info07:52
mborzeckioutput dump)07:52
zyga-ubuntumborzecki: not the same bug then07:54
* zyga-ubuntu -> afk07:56
mborzeckizyga-ubuntu: not exactly, the patch does more than is written in the bug report :P07:56
mvomborzecki: right, yeah, python is unhappy if the encoding does not match, I'm not surprised. a shames that C.utf-8 is not standarized08:00
mborzeckipstolowski: morning08:05
pstolowskihey!08:05
kalikianao/08:20
kalikianamorning, mborzecki08:20
mborzeckikalikiana: hey08:21
Chipacamo'in08:53
ikeyrawr08:53
Chipacaif you say so08:54
mvohrm, hrm, looks like master is broken right now09:02
mvosearch test failing09:02
Chipacamvo: D:09:06
mvoChipaca: unless you are looking into this already I will do so now09:06
Chipacamvo: I was not09:06
mborzeckistore related tests are randomly failing?09:22
mupPR snapd#4549 opened: tests: update "searching" test to match store changes <Created by mvo5> <https://github.com/snapcore/snapd/pull/4549>09:27
mvomborzecki: hopefully not randomly but yes, everything is broken right now09:29
mvomborzecki: see PR above09:29
mborzeckimvo: i've restarted #4487 5-6 times already, not counting the searching thing, there's failures in fetching snaps (either in prepare, or some refresh tests)09:30
mupPR #4487: cmd/snap: snap refresh --time with new and legacy schedules <Created by bboozzoo> <https://github.com/snapcore/snapd/pull/4487>09:30
mvomborzecki: oh, more? sucks09:30
mvomborzecki: sounds like a reason to talk to the good people from the store team :)09:31
* mvo looks at the results09:31
mborzeckimvo: regarding 4549, database is no longer listed in sections :/ any clue why?09:34
mvomborzecki: yeah, I just talked to the store team - it just got removed, there is a set of new sections09:35
mborzeckihm can they confirm that all the sections are listed in `snap find --section`?09:36
mvomborzecki: I think that is the case09:39
mvomborzecki: in your current run it is just "searching" what failed so far09:41
mvomborzecki: so fingers crossed :)09:41
mborzeckimvo: btw: maciek@corsair:github.com/snapcore/snapd (git)-[master] ./test-snap find --section=foobar09:41
mborzeckiNo matching snaps for ""09:41
mvoyeah, we should tweak the error09:41
mvoto include that the search was in a section09:41
mborzeckimvo: i can look into it09:41
mvoand/or show that there is no such section09:42
mvonot sure what metadata we get from the store09:42
mvothanks mborzecki09:42
Deknosaloha, is there a bugtracker for snaps anywhere?09:44
Deknosi tried minikube and kubectl snaps on ubuntu 17.10 and debian, but it did not work. manual installation works, though. any idea how to write a issue/bug for snap?09:45
mvoDeknos: is this a issue with the snaps themself? or an issue with the snapd, i.e. can you not use any snaps on your system? if the former, there is a "contact" field in the "snap info" output that you can use to get in touch with the snap provider09:51
mvoDeknos: there is also forum.snapcraft.io where a lot of the snap developers hang around09:51
Deknoswell it seems to have to do sth with the installation since manual installation works, but via snaps setup of the vms crash10:03
Deknosthanks, i'll try the forum.10:03
mupBug #1669012 changed: Can't reinstall a snap already installed switching confinement mode <amd64> <apport-bug> <xenial> <snapd:Triaged> <snapd (Ubuntu):Triaged> <https://launchpad.net/bugs/1669012>10:04
mvoDeknos: good luck!10:09
mborzeckimvo: do you think a separate error message if no matches in section were found makes sense? https://paste.ubuntu.com/26463360/10:22
mvomborzecki: this looks good to me10:23
mborzeckimvo: well i'm counting on sections being cached (which they seem to be) as this does an additional cli.Sections() call :)10:24
mupPR snapd#4549 closed: tests: update "searching" test to match store changes <Created by mvo5> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/4549>10:48
niemeyerMornings11:04
* ikey plays "Walking on sunshine" in response to "morning"11:04
niemeyerikey: I don't think I had ever seen that11:10
ikeyhttps://www.youtube.com/watch?v=iPUmE-tne5U11:11
ikey^^11:11
ogra_♬ ♪♩♬11:12
mupPR snapd#4550 opened: cmd/snap: improve output when snaps were found in a section or the section is invalid <Created by bboozzoo> <https://github.com/snapcore/snapd/pull/4550>11:13
niemeyerikey: Yeah, I just watched it.. not sure what to take from it.. my life will probably never be the same again11:17
ikeymost welcome lol11:17
ikeyso i tried jdstrand's recommendations this morning with snapd/apparmor11:19
ikeyapparmor was most unhappy11:19
ikeygonna have to bite the bullet and just suck it up with the whole 4.8 requirement11:19
ogra_niemeyer, would you mind adding a "yes this is right/no, nonsense" answer to https://forum.snapcraft.io/t/what-happens-if-an-architectures-all-snap-becomes-arch-specific/3675 ?11:37
niemeyerogra_: Will have a look11:38
ogra_thanks11:38
niemeyermborzecki: About your question on arch yesterday,11:38
niemeyermborzecki: we never had our own arch image, I believe11:38
niemeyermborzecki: What likely happened was that you were using an arch image provided by Linode, which was obsoleted11:38
mborzeckiniemeyer: yes, that was the case, fortunately spread -vv contains all the info about machine templates i need ;)11:38
niemeyermborzecki: I find a bit surprising to be honest11:39
niemeyermborzecki: I mean, anyway using that image is now broken11:39
niemeyeranyone11:39
niemeyerLooking at https://www.linode.com/distributions, the current one seems to be 2018.01.0211:39
mborzeckiniemeyer: switched to that version already11:40
cachio_mvo, https://paste.ubuntu.com/26461903/ https://paste.ubuntu.com/26461941/11:54
cachio_mvo I see those errors on rpi2 and 3 when I refresh from stable to beta11:54
mvocachio_: thanks, looking11:56
mvocachio_: *hrm* smells like an issue with writable-path, let me dig11:58
mvocachio_: out of curiosity, this did not happen on an x86 core device?12:00
cachio_mvo, no12:00
cachio_mvo, just on the pi12:01
mvointeressting12:01
mvocachio_: and you said you refreshed from the previous stable, correct? a fresh image from stable and then refresh to beta?12:01
cachio_mvo, I used the stable from http://cdimage.ubuntu.com/ubuntu-core/16/stable/current/12:02
cachio_mvo, the factory one12:02
mvocachio_: thank you, I give it a go12:02
ChipacaI'm not going to be here for the standup; I'm off to a school meeting (that'll probably extend into the afternoon) (I'll retroactively file for pto if it does)12:05
mvoChipaca: thanks and see you12:07
Chipacamvo: still here for another little while though :-)12:08
Chipacameeting is 13:30, google says 30 minutes of driving (but midday rush is a thing)12:08
mupIssue snapcraft#1886 opened: Support for yarn --extra-args <bug> <Created by sergiusens> <https://github.com/snapcore/snapcraft/issue/1886>12:11
mvocachio_: confusing, I just did install of the stable image, refreshed mnaully to beta rebooted and systemctl list-timers hows me the timer12:21
mvocachio_: can you ssh into the board and run "systemctl list-timers --all" and paste that please?12:21
cachio_sure12:21
mupPR snapd#4551 opened: interfaces: do not auto-connect manually disconnected interfaces <Created by stolowski> <https://github.com/snapcore/snapd/pull/4551>12:21
cachio_mvo, https://paste.ubuntu.com/26463820/12:22
* kalikiana going to go for an earlier lunch in a few12:25
mupPR snapd#4552 opened: testutil: do not use echo for printing potentially conflicting arguments <Created by bboozzoo> <https://github.com/snapcore/snapd/pull/4552>12:33
mvocachio_: hm, how strange. in a meeting now, lets talk in a bit12:33
cachio_mvo, np12:36
mupPR snapd#4547 closed: snap: fix race in `snap run --strace` <Created by mvo5> <Merged by zyga> <https://github.com/snapcore/snapd/pull/4547>12:40
ikeywill we have a jdstrand around today? primarily so i know in order to get my best begging face on12:47
* ikey readies a spray bottle for the fake tears12:47
diddledanikey: https://youtu.be/elmwnUOtxu8?t=7613:21
ikeyhah perfect13:22
mvocachio_: what is the output of "systemctl status snapd.snap-repair.timer" on the pi2?14:00
mvocachio_: (or pi3)14:00
pstolowskicachio_, do you have any gsettings branch I can look at? or can describe the test case you want to achieve?14:01
cachio_https://paste.ubuntu.com/26464226/14:01
cachio_pstolowski, yes, on sec14:01
cachio_pstolowski, https://github.com/sergiocazzolato/snapd/tree/tests-interface-gsettings14:02
cachio_there is a snap already uploded to the store14:02
cachio_mvo,  https://paste.ubuntu.com/26464226/14:03
pstolowskicachio_, thanks, i'll have a lunch now and will take a look afterwards14:10
* pstolowski lunch14:10
cachio_pstolowski, sure, just ping me14:13
mvocachio_: thanks, I'm on it14:18
mvocachio_: I think I found the issue and pushed a fix to the core build, will be part of ~rc214:22
mupPR core#79 opened: 26-fixup-core.chroot: fix snapd.snap-repair.timer enable symlink <Created by mvo5> <https://github.com/snapcore/core/pull/79>14:22
cachio_mvo, great14:23
cachio_mvo, which is the problem that you found?14:23
mvocachio_: its a problem with the writable-path stuff: https://github.com/snapcore/core/pull/79/commits14:24
mupPR core#79: 26-fixup-core.chroot: fix snapd.snap-repair.timer enable symlink <Created by mvo5> <https://github.com/snapcore/core/pull/79>14:24
cachio_mvo, ohh, tx14:25
kalikianakyrofa: Hey15:19
kalikianakyrofa: Can I pick your brain on the checker callable used in the grammar? I was looking into "to" for strings, ie. the source property, and it adds ":armhf" and such because ToStatement doesn't know about packages or other properties15:20
kyrofakalikiana, hahaha15:26
kyrofaYeah we probably don't want that eh?15:26
kyrofakalikiana, do you want to HO?15:27
kalikianakyrofa: Yeah, we can have a quick chat now if you have time15:28
kyrofakalikiana, I do15:30
kalikianakyrofa: Shall we use the weekly?15:30
kyrofaweekly?15:30
kyrofaYep15:30
kyrofaOh wait, no15:30
kyrofakalikiana, any chance you have skype?15:30
kyrofaI'm so stinking sick of chrome15:30
kalikianakyrofa: I'm seeing a trend here :-D15:30
kyrofaLet's use that. Or talky15:30
kyrofaIs talky better?15:31
kyrofaI really don't care. Just something that doesn't require me to open chroem15:31
kalikianakyrofa: Either one works for me15:31
kalikianalol15:31
kyrofaLet's try talky. Hold on15:31
pstolowskicachio_, test-snapd-gsettings is the snap you meant?15:38
cachio_yes15:38
cachio_pstolowski,15:38
pstolowskicachio_, oh wow, that snap is huge15:41
cachio_pstolowski, yes :s15:42
pstolowskicachio_, I see more plugs than just gsettings in its snap.yaml; is this intended to be used for many tests?15:46
cachio_it is pluggin also desktop15:47
cachio_pstolowski, it is because it needs to access to destop files15:47
bloodearnesthey folks, is there any way to call setuid() at all from a strictly confined snap? E.G. to switch to the 'daemon' or 'nobody' user, which is in the core snap, I don't need to create a user (just can't run as root)15:51
mupIssue snapcraft#1887 opened: Update to ROS2 Ardent <Created by kyrofa> <https://github.com/snapcore/snapcraft/issue/1887>15:51
bloodearnestI thought there was some seccomp/apparmor provision for this, but I can't find any documentation on it15:52
kyrofabloodearnest, no, it's in the design phases as I understand it, jdstrand will know more/all15:55
pstolowskicachio_, I think you could get rid of python-gi dependency (which already pulls a lot of stuff). glib comes with a gsettings cli that can query and set settings db16:03
pstolowskikyrofa, hey, where can I lookup the definition of desktop-gtk3 part? I knew it but forgot..16:05
kyrofapstolowski, snapcraft define16:06
kyrofapstolowski, or do you want to update it?16:06
pstolowskikyrofa, no, just check it out16:06
kyrofaYeah, that should work16:06
pstolowskikyrofa, thanks!16:06
jdstrandbloodearnest: not yet. it is on the roadmap. I suggest you keep an eye on https://forum.snapcraft.io/t/multiple-users-and-groups-in-snaps/146116:09
bloodearnestkyrofa: jdstrand: ok, thanks16:10
bloodearnestfwiw, this make squid and postgres very difficult to run, as they both refuse to run as uid 016:10
jdstrandbloodearnest: note this is something I'd really like to see done, but it isn't prioritized high atm. the design is there and approved (which is good), but it is slow going16:10
jdstrandbloodearnest: but we'll get to it16:11
jdstrandbloodearnest: I think someone posted in the forum what to do with postgresql16:11
jdstrandbloodearnest: there is also the snapcraft preload plugin which LD_PRELOADs to make them no-ops16:11
jdstrandbut like you say, the correct thing is to have this support. we'll get there16:12
cachio_<cachio_> pstolowski, ok, I'll try that16:13
cachio_<cachio_> pstolowski, apart of that, any idea about hot make it work on linode?16:13
cachio_<cachio_> it was failing trying to create many directories16:13
cachio_<cachio_> but then can't access to the gsettings user keys16:13
cachio_<cachio_> it is just reading the values that come inside the snap16:13
cachio_<cachio_> but when I try to update and see the change, the values have not been changed16:13
pstolowskicachio_, and you depend on desktop-gtk3 path to have the entire environment and schemas set, correct?16:14
bloodearnestjdstrand: ok, I'll check the forums for that. I don't think the preload plugin helps here - postgres has a hard coded if (geteuid() == 0), it doesn't try to drop privs itself, but forces you to do it16:14
cachio_pstolowski, I got disconnected, sorry16:14
cachio_pstolowski, yes16:14
jdstrandbloodearnest: someone specifically patched postgresql for the postgresql snap16:14
cachio_I copied that from the gnome-calculator app16:14
jdstrandbloodearnest: so yes, you might have to patch. for now. but we'll get there16:14
pstolowskicachio_, so I think you should try to remove it as it pulls half of the desktop stuff obviously, and take a look at https://github.com/Ubuntu/snapcraft-desktop-helpers/blob/master/common/desktop-exports16:15
pstolowskicachio_, this is part of the desktop-launch script afaict16:15
pstolowskicachio_, look at the gsettings stuff there16:15
pstolowskicachio_, you can basically replicate it16:15
cachio_pstolowski, ok, but the problem is that all the desktop part is not in the linode images16:16
cachio_pstolowski, so, the mappings in this script don't work16:17
pstolowskicachio_, yeah but we don't need it afaict16:17
blackboxswpedronis: hi any suggestions on https://forum.snapcraft.io/t/seed-yaml-documentation/3050/4     maybe --classic snaps can't be seeded ?16:18
pstolowskiblackboxsw, he is off, back next week16:18
blackboxswahh excellent pstolowski thanks for the heads up16:19
cachio_pstolowski, ok, I'll try to clean this but first I need to figure out how to fix the current issue16:20
cachio_pstolowski, for example16:20
pstolowskicachio_, afaiu the snap should have glib as the base dependency. all the schema stuff is build in $SNAP_USER_DATA/.local/share (we should replicate this part of the script)16:20
pstolowskicachio_, and the test could use gsettings binary from the snap, no custom python to query gsettings data16:21
pstolowskicachio_, we should be able to test gsettings with just cli tools, no need for gtk and all the desktop stuff16:22
cachio_pstolowski, ok, I'll try this16:22
pstolowskicachio_, i'm not sure about the dconf part of the interface, it has a dbus snippet16:23
pstolowskicachio_, there is a dconf binary that can also query settings. but i don't know if it touches dbus16:23
cachio_pstolowski, no idea16:24
ikeyso jdstrand to clarify, how am i going to move forward with the steam thing?16:24
pstolowskicachio_, if not, then we can use dbus-send cli or something else (not to pull python)16:24
ikeycuz that much i failed as yet to discern16:25
ikeybut gathered "pending voodoo" being the trend16:25
pstolowskicachio_, well, just the bare python itself is not too bad, problems start when we pull too much stuff16:26
cachio_pstolowski, yes, agree16:27
cachio_pstolowski, I tried to simulate what the desktop team do but it is so complex for our tests16:27
jdstrandikey: I'd like to get some feedback on cx vs px. I also want to come up with the rules to give you, then tell you the course forward16:30
jdstrandikey: I have some work to do to give you all that16:30
* jdstrand is in meetings today, but hopes to pick this up this afternoon16:30
pstolowskicachio_, $SNAP/usr/bin/gsettings cli is a good enough test as it uses the same glib API that gui apps would use16:31
pstolowskicachio_, but as I say I don't know about the dbus part of the policy for dconf and what would be a good test for it (other than sending a dbus message manually with dbus-send or some such), perhaps someone from desktop team can explain16:34
ikeyjdstrand, ok16:37
ikeyi think ill have to pull my snaps out of the store16:37
ikeyas i cant update them16:37
jdstrandikey: ? why?16:38
cachio_pstolowski, ok, I'll start researching on this16:38
ikeybecause to develop them any further i need working strict confinement, and they're bugged out in their current state16:38
ikeyand nobody else will have the interface they need to run them properly16:38
ikeyetc16:38
jdstrandikey: you could set 'grade: devel' and not push them to stable16:38
ikeyive not pushed to stable16:39
ikeybecause of my permanent chicken / egg cycle with this snap :P16:39
jdstrandI don't know if that is helpful or not, but an option16:39
ikeybasically because i cant update them i cant testify to their security status16:41
ikeyand would be more comfortable with withdrawing them entirely16:41
ikeyas it reflects poorly on solus16:41
cachio_pstolowski, another question16:41
cachio_pstolowski, https://paste.ubuntu.com/26465150/16:42
cachio_hidraw should be just for gadgets?16:42
jdstrandwell, regardless, I'll be working on this to give you what you need16:42
cachio_pstolowski, or it should be visible in any core?16:42
cachio_pstolowski, based on that declaration16:43
mupPR core#79 closed: 26-fixup-core.chroot: fix snapd.snap-repair.timer enable symlink <Created by mvo5> <Merged by mvo5> <https://github.com/snapcore/core/pull/79>16:43
ikeyjdstrand, how would i go about unpublishing snaps..?16:43
ikeyif such a concept exists16:43
ikeyalternatively ill refresh the snaps without any of the new interfaces.. but ofc they remain broken16:45
ikeythis is too much thinking for a friday -_-16:45
jdstrandikey: I'm not sure tbh. perhaps roadmr or sergiusens can comment?16:45
ikeywhat would need to be done on your side out of interest?16:47
ikeyre: enabling the globbing stuffs16:47
pstolowskicachio_, this declaration says the slot can be on gadget or core, but i've no idea whether this is correct or not16:48
roadmrikey: the best way IIRC is to push a new snap and release that to the channel where the snap-you-want-unpublished is16:51
roadmrikey: effectively superseding it really. Once it's not published on any channels, it'll be uninstallable for anyone, not even by specifying --revision16:52
ikeyi mean like all revisions16:52
roadmrikey: oh like just removing them from existence entirely? I don't think that can be done :( sorry16:53
ikeyah ok16:53
roadmrikey: another way is to close all channels. snapcraft close stable16:53
ikeyso ill need to push a gimped build then16:53
ikeyroadmr, unfortunately i dont have a stable channel16:53
roadmrsame for beta, edge, candidate.16:53
roadmrikey: if the snap is on e.g. edge, you can close that too16:54
ikeyok ty16:54
mupPR snapd#4553 opened: many: add io.snapcraft.Settings to `snap userd` <Blocked> <Created by mvo5> <https://github.com/snapcore/snapd/pull/4553>16:58
* kalikiana going to wrap up for the week shortly16:59
pstolowskieow, o/17:04
mupPR snapd#4554 opened: test build - ignore <Blocked> <Created by mvo5> <https://github.com/snapcore/snapd/pull/4554>17:06
cachio_ogra_, hey17:08
cachio_could you please confirm if the hidraw interface is available on any core device17:08
cachio_ogra_, this is the declaration https://paste.ubuntu.com/26465150/17:09
mupPR snapd#4553 closed: many: add io.snapcraft.Settings to `snap userd` <Blocked> <Created by mvo5> <Closed by mvo5> <https://github.com/snapcore/snapd/pull/4553>17:09
mupPR snapd#4554 closed: test build - ignore <Blocked> <Created by mvo5> <Closed by mvo5> <https://github.com/snapcore/snapd/pull/4554>17:09
mvocachio_: I get dinner now, but the failure in 4073 is strange still :/17:10
cachio_mvo, checking17:11
mupPR snapd#4538 closed: interfaces/builtin: Add new steam-support interface <Created by ikeydoherty> <Closed by ikeydoherty> <https://github.com/snapcore/snapd/pull/4538>17:12
ogra_cachio_, nops, uhid is there but not hidraw17:22
ogra_cachio_, so core does not have it declared atm17:23
ogra_(the core snap that is)17:23
cachio_ogra_, ok17:26
cachio_ogra_, tx17:26
ogra_s/declared/exposed/17:26
ogra_np17:26
cachio_ogra_, not sure why not17:29
cachio_ogra_, it should17:29
ogra_ogra@localhost:~$ snap interfaces|grep hid17:29
ogra_:uhid17:29
ogra_well, thats what i get17:29
ogra_(on all core devices running here)17:30
niemeyerThis is looking smooth... https://travis-ci.org/snapcore/snapd/jobs/33381637717:30
kyrofajdstrand, got a question for you. I have a user who's snap needs to be disabled/enabled _every boot_, otherwise every daemon prints this: "cannot change profile for the next exec call: No such file or directory"17:50
kyrofajdstrand, can you think of a reason for this?17:50
kyrofazyga-ubuntu, that ^ may interest you as well17:50
zyga-ubuntukyrofa: ack17:51
zyga-ubuntukyrofa: daemon should not do that17:51
zyga-ubuntukyrofa: on restart we reload profiles17:51
zyga-ubuntukyrofa: this smells like a container with apparmor disabled17:51
zyga-ubuntukyrofa: fighting over apparmor from the parent host17:51
zyga-ubuntukyrofa: if I'm right I'll get a t-shirt with some silly container stacking apparmor text17:52
kyrofazyga-ubuntu, all I know so far is that it's hosted on aruba.it17:52
zyga-ubuntuyeah17:52
kyrofazyga-ubuntu, if you're up for jumping into the discussion, it's here: https://github.com/nextcloud/nextcloud-snap/issues/42517:52
zyga-ubuntulooks like it17:52
mupPR snapd#4553 opened: many: add io.snapcraft.Settings to `snap userd` <Blocked> <Created by mvo5> <https://github.com/snapcore/snapd/pull/4553>17:52
mupPR snapd#4554 opened: test build - ignore <Blocked> <Created by mvo5> <https://github.com/snapcore/snapd/pull/4554>17:52
kyrofa(including logs)17:52
mupPR snapd#4554 closed: test build - ignore <Blocked> <Created by mvo5> <Closed by mvo5> <https://github.com/snapcore/snapd/pull/4554>17:53
kyrofaThanks zyga-ubuntu :)17:55
zyga-ubuntumy pleasure :)17:55
zyga-ubuntuI'm off today but back at my PC doing stuff so I can look for activity on that thread17:56
mupPR snapd#4553 closed: many: add io.snapcraft.Settings to `snap userd` <Blocked> <Created by mvo5> <Closed by mvo5> <https://github.com/snapcore/snapd/pull/4553>18:13
mupPR snapd#4546 closed: snap: tidy up top-level help output <Created by cjwatson> <Merged by zyga> <https://github.com/snapcore/snapd/pull/4546>18:17
mupPR snapd#4555 opened: test -ignore <Blocked> <Created by mvo5> <https://github.com/snapcore/snapd/pull/4555>18:18
zyga-ubuntumvo: what are you testing?18:18
mupPR snapd#4552 closed: testutil: do not use echo for printing potentially conflicting arguments <Created by bboozzoo> <Merged by zyga> <https://github.com/snapcore/snapd/pull/4552>18:19
mvozyga-ubuntu: I don't get why 4073 is failing18:20
cachio_mvo, debugging it18:23
cachio_mvo, it'll take a while18:23
cachio_mvo, everithing is slowwww18:23
cachio_mvo, https://paste.ubuntu.com/26465771/18:25
cachio_it is like we create the ubuntu core, something happens to the user18:26
cachio_I stopped the test just after we reboot the machine18:26
cachio_and I get that18:27
cachio_and before it works18:27
mvocachio_: oh, interessting18:27
mvocachio_: I wonder what in this PR broke it, it does not touch any of this18:28
cachio_mvo, the test user is not in cat /var/lib/extrausers/passwd | grep test18:31
cachio_not sure why18:31
mvozyga-ubuntu: just fyi - I updated http://people.canonical.com/~mvo/tmp/snap-boot.svg this time with snaps, it shows that snap.mount runs before the two snaps (core, hello) are mount. the mountinfo file is https://paste.ubuntu.com/26465825/18:36
jdstrandkyrofa: I've not seen that, but it sounds like snap-confine is running and trying to change profile to the snap's profile, but that profile is not loaded18:37
mvocachio_: its super strange, I had issue with my local spread (gustavo helped me fixing it) and now I will try to get to the bottom of it18:37
zyga-ubuntumvo: oh, great, let me see18:38
jdstrandkyrofa: if it is happening on boot, that could be that the snap is starting before snapd starts and the apparmor init/unit isn't loading /var/cache/apparmor18:38
cachio_mvo, I am waiting to get a debug session18:38
mvocachio_: thank you, keep me updated please, curious if you hvae any ideas18:38
zyga-ubuntujdstrand: can we detect apparmor is not stacked inside a container?18:38
jdstrandkyrofa: restarting snapd should cause snapd to load all the profiles18:38
cachio_it is like for some reason the test user is not being added as a user in the files group gshadow passwd shadow18:38
mvozyga-ubuntu: still two mounts though18:38
zyga-ubuntuinspecting18:38
jdstrandzyga-ubuntu: can you rephrase?18:38
zyga-ubuntujdstrand: sure, sorry, let's say I use a privileged lxd container that doesn't use apparmor stacking, can I detect that somehow from inside the container?18:39
jdstrandkyrofa, zyga-ubuntu: *if* the snap is running in a container, it certainly seems plausible that the detection logic is not working right18:39
zyga-ubuntumvo: question about the graph, what determines the width of a row?18:40
zyga-ubuntuthey all seem to have the same width18:40
zyga-ubuntuis it "starting" or "finished"18:40
zyga-ubuntuis it possible that our tweaks on post-start run in parallel with snap mounts?18:40
jdstrandzyga-ubuntu: aiui, not as well as we should be able to. /lib/apparmor/functions has is_container_with_internal_policy() which is a hacky way of determining this18:41
mvozyga-ubuntu: thats an interessting idea18:41
zyga-ubuntujdstrand: thank you, let me read it18:41
mvozyga-ubuntu: the man page claims that the ordering will be correct if one mount unit is below/above the mount hirarchy18:43
mupPR snapd#4555 closed: test -ignore <Blocked> <Created by mvo5> <Closed by mvo5> <https://github.com/snapcore/snapd/pull/4555>18:45
jdstrandkyrofa, zyga-ubuntu: this seems similar to https://irclogs.ubuntu.com/2018/01/09/%23ubuntu-devel.html#t03:3418:47
jdstrandI think jjohansen developed a patch for that for artful18:47
jdstrandkyrofa: what kernel was that on?18:47
kyrofajdstrand, uncertain, I'll ask for a `snap version` run18:48
zyga-ubuntumvo: yes but what about the extra scripts that run after that are defined in one mount unit18:52
mvozyga-ubuntu: there is currently no extra script, its just shared,bind in the options18:55
zyga-ubuntumvo: ahh18:57
zyga-ubuntuhmm hmm hmm18:58
zyga-ubuntuthis makes litlte sense18:58
zyga-ubuntuwould it bother you to drop the "shared" flag and rerun?18:58
zyga-ubuntuand see what we get in mountinfo please?18:58
zyga-ubuntuI'm suprprised you saw shared, in my testing shared was not working18:58
zyga-ubuntucan you tell me how to reproduce your setup?18:58
mvozyga-ubuntu: sure, one sec19:01
mvozyga-ubuntu: here the same without shared https://paste.ubuntu.com/26465983/19:02
mvozyga-ubuntu: this is all on 16.04 classic19:02
zyga-ubuntuhmmm19:06
zyga-ubuntuodd19:06
zyga-ubuntu137 89 7:0 / /snap/core/3887 ro,nodev,relatime shared:117 - squashfs /dev/loop0 ro19:06
zyga-ubuntu138 23 7:0 / /snap/core/3887 ro,nodev,relatime shared:117 - squashfs /dev/loop0 ro19:06
zyga-ubuntu143 89 7:1 / /snap/hello/20 ro,nodev,relatime shared:122 - squashfs /dev/loop1 ro19:06
zyga-ubuntu144 23 7:1 / /snap/hello/20 ro,nodev,relatime shared:122 - squashfs /dev/loop1 ro19:06
zyga-ubuntuhow come you get this?19:06
zyga-ubuntuthoey are all shared19:06
zyga-ubuntuis this running in a container on top of your 16.04?19:06
zyga-ubuntumvo: ^ ?19:17
mvozyga-ubuntu: this is a regular vm19:20
mvozyga-ubuntu: sorry for the delay19:20
zyga-ubuntumvo: no worries, I'm mostly wondering how this is possible19:21
zyga-ubuntumvo: is there any part of test prep code that makes /snap or / rshared?19:21
zyga-ubuntumaybe this is an artefact19:21
zyga-ubuntuwas this done via spread19:21
zyga-ubuntuI was doing it in a boxes VM (so just plain KVM) on 16.04 with lxd and it was not getting the sharing19:22
mvozyga-ubuntu: this is all done manual, I used a stock 16.04 vm and added the mount unit manually19:22
zyga-ubuntuI see19:22
mvozyga-ubuntu: but no lxd here19:23
zyga-ubuntuhmm hm :)19:23
zyga-ubuntucurious19:23
zyga-ubuntuoh/19:23
mvozyga-ubuntu: this is the pure vm19:23
zyga-ubuntuwait19:23
zyga-ubuntubut pure 16.04 vm doesn't have this problem19:23
zyga-ubuntuit's shared by default already19:23
mvozyga-ubuntu: I know, but if the fix produces double mounts thats a problem, no? or do we not care?19:23
zyga-ubuntu(the duplication is a curious issue but it's not the main problem in containers)19:23
zyga-ubuntuyeah, we may care19:23
zyga-ubuntuI wonder what is really going on19:23
zyga-ubuntuok, this made me curous19:23
zyga-ubuntu*curious19:23
zyga-ubuntuI will explore19:24
mvozyga-ubuntu: ok, I will do the mount unit generated via postinst script step next19:24
mvocachio_: I know what breaks it - I added a zenity recommends that seems to cause the failure, I will dig into the details monday, peace of mind in the end :)19:59
cachio_mvo, heehhe20:00
cachio_mvo, ok20:00
cachio_mvo, btw, I have doctor app on monday, not sure if I'll be at home for the standup20:01
mvocachio_: no worries20:01
mvocachio_: thanks for letting me know20:01
cachio_tx20:01
Chipacasergiusens: question: is snapcraft validating snap version strings?20:15
mupPR snapd#4544 closed: spread: remove more EOLed releases <Created by zyga> <Merged by zyga> <https://github.com/snapcore/snapd/pull/4544>20:16
kyrofaChipaca, yeah, to ^[a-zA-Z0-9.+~-]+$ and max length of 3220:23
Chipacakyrofa: k thx20:23
kyrofaChipaca, is that okay? Has it changed?20:24
Chipacakyrofa: snapd doesn't care :-) but i'm writing code in snapd that cares a little bit20:24
kyrofaGotcha20:24
Chipacai mean, if the version is valid, i'll use it in a filename20:25
Chipacaif it's not, ¯\_(ツ)_/¯20:25
Chipacalooking at that regexp, me, I wouldn't let versions end in ~, but again ¯\_(ツ)_/¯20:26
Chipacai mean, a version of 4.~1~ would be somewhat confusing20:26
Chipacaat least to those of us used to VERSION_CONTROL=numbered20:27
kyrofaHeck, same goes for the rest probably20:27
ChipacaI could see people ending it in +20:29
Chipacastill, very minor friday-what-am-i-doing-at-the-keyboard nitpick20:29
* Chipaca ponders beer20:29
cachio_ Chipaca, any idea why the hidsraw interface is not visible?20:40
Chipacacachio_: no. visible where?20:43
Chipacacachio_: I don't have a hidsraw in my tree (but i haven't synced today)20:44
cachio_Chipaca, hidraw20:48
Chipacacachio_: do you have /dev/hidraw*?20:49
cachio_yes20:50
Chipacacachio_: dunno, then :-)20:51
cachio_Chipaca, hehe, np20:52
cachio_do you have the interface?20:52
diddledanso one crazy SOB just got wine running21:11
diddledanjust rebuilding my snap to be sure I wasn't dreaming21:12
* Chipaca EODs21:22
* Chipaca EOWs21:22
* Chipaca EOLs21:22
mupPR snapcraft#1888 opened: elf: make patchelf a dependency <Created by sergiusens> <https://github.com/snapcore/snapcraft/pull/1888>21:49
=== doko is now known as doko__
=== doko__ is now known as doko
Son_Gokuneed testing for snapd 2.30 update for Fedora 26: https://bodhi.fedoraproject.org/updates/FEDORA-2018-798e0f02ff22:27
=== doko is now known as doko__

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