/srv/irclogs.ubuntu.com/2019/07/01/#snappy.txt

mborzeckimorning05:17
zygaGood morning05:44
=== morphis9464 is now known as morphis
mborzeckizyga: hey05:47
zygamborzecki: how are you today?05:53
zygamborzecki: we are moving again but this time relatively very little05:56
mborzeckizyga: changing places?05:58
mborzeckizyga: it's damn hot today again05:58
zygamborzecki: yeah, we didn't rent a single place for the whole duration of our stay06:00
zyga(which is uncertain anyway)06:00
zygamborzecki: here we have finally some clouds06:00
zygamborzecki: it is just 23C and very very pleasant06:01
zygaI'll check my PRs, some are close to landing06:01
zygamborzecki: do you think this will pass?06:04
zygahttps://www.irccloud.com/pastebin/bVNC8zuG/06:04
mborzeckizyga: mhm, looks good to me06:05
zygaI've replicated the case for generic ubuntu that matches apparmor, starting spread06:06
zygalet's see06:06
zygaI just noticed the grass is still wet, wow it is really cold and cloudy today06:06
mborzeckizyga: isn't that /usr/bin/sh vs /bin/sh ?06:07
zygamborzecki: yeah, I am pretty sure that is is06:07
mborzeckizyga: at laest on fedora/centos/amzn06:07
zygamborzecki: we have a magic thing in our spec that disables the rewrite that normally happens06:07
zygamborzecki: which makes me think that:06:07
mborzeckizyga: oh, right06:07
zyga1) it was always broken for hotplug06:07
zyga2) device cgroup was not tested on those systems effectively06:07
zyga3) after fixing this we will kill two birds with one stone06:08
zygamborzecki: I'll check that shortly06:08
zygabut it sounds plausible to me06:08
mborzeckimvo: morning, not taking a day off?06:20
zygamvo: hello06:22
mvohey zyga and mborzecki !06:24
zygahow are you doing?06:25
zygagood to be home?06:25
mvomborzecki, zyga I will be here today, want to be part of the standup, talk about the sprint and also welcome ian today06:25
mborzeckimvo: yay, ijohnson is starting today?06:25
mvozyga: yes, very good to be home, we had a network outage over the weekend, no phone or internet, so even a forced holiday from all digital things :)06:25
mvomborzecki: yes06:25
mvomborzecki: I think so at least, will double check for any last minute changes :)06:26
mborzeckimvo: great to have the team grow in size :)06:26
mvomborzecki: yeah, I'm excited too06:26
mvomborzecki, zyga how are you ? what did I miss? sorry for not joining the standup once, it was very busy06:27
zygamvo: relatively quiet week; some excessive iteration on the lxd fix06:27
zygamvo: but it now has two approvals and just a few comments to tweak06:27
mvozyga: \o/ thanks for jumping on this one06:28
mvozyga: and you made the trip and are "settled" now?06:28
zygamvo: haha06:28
zygamvo: we are moving today06:28
zygabut not far06:28
zygaso ...06:28
mborzeckimvo: landed some gadget updates bits, more on reviews still, but we're closing in06:28
zygait's not the most stable work environment ;)06:28
mvomborzecki: yay, thanks for this06:29
zygamvo: I have some feedback from manjaro, one small fix to a shell script to send06:30
mvozyga: cool!06:33
zygamborzecki: I know why that trivial udev change didn't work, fixed, let's see if it passes now06:40
mborzeckigot an errand to run, bbiab06:47
ackkhi, I'm having an issue building a python C extension in a snap (actually a dependency of what I'm snapping). I have a reproducer with a minimal snap that just builds the library: http://paste.ubuntu.com/p/qmxp7rBh6Z/. the error is http://paste.ubuntu.com/p/kgwcB673qf/ am I missing something in the build configuration?06:56
zygamborzecki: it passed, pushed now06:58
zygaackk: looks like lack of header06:59
ackkzyga, those headers are in the library itself07:00
ackkzyga, -Iast27/Include07:01
ackkzyga, needless to say that if I create a virtualenv and pip install typed-ast --no-binary=typed-ast it works07:02
zygaackk: but is that path OK when in snapcraft?07:05
zygait is a relative path, not sure if that is good here07:05
ackkmhm07:05
ackkzyga right but I think it's assumed to build from the base of the package07:06
zygaI don't know, just guessing based on what the errors said07:06
ackknot sure if snapcraft does something different, but it should just call pip ?07:06
zygamvo: https://github.com/snapcore/snapd/pull/7048 needs a 2nd review and is super simple07:10
zygamborzecki: final remark on https://github.com/snapcore/snapd/pull/7026 -- I would like not to enforce \n on the final line. I think it is too pedantic and doesn't win us anything while actively closing the utility of the parser down the line.07:14
zygamborzecki: I pushed remaining tweaks and intend to merge when green07:14
zygamborzecki: if you feel strongly about the newline please indicate so07:14
zygamborzecki: since you are on an errand now I'll wait until you return07:14
mvozyga: thanks, checking now07:15
=== pstolowski|afk is now known as pstolowski
pstolowskimornings!07:16
pstolowskiwelcome back mvo!07:16
mvopstolowski: good morning! and thank you :)07:16
mvopstolowski: feels good to be back :)07:16
zygamvo: thank you :)07:20
zygahello Pawel!07:20
ackkzyga, I wonder if it has to do with the fact that snapcraft calls "pip wheel" not "pip install", or because of environ07:29
zygaI really don't know, it would be good to see if you can reproduce the failure without snapcraft involved07:29
* zyga jumps at https://github.com/snapcore/snapd/pull/6891 again07:32
zygamvo: 1-2-1 in 15 minutes, right?07:42
mvozyga: yes07:47
diddledanackk: seemingly works when you remove `--no-binary=typed-ast` <-- I've never seen parameters passed this way and have no idea if that is even likely to work07:47
ackkdiddledan, yes, because on amd64/i386 that library is available as binary. on other arches it fails because it tries to build it. to test it I'm passing --no-binary to reproduce the issue on amd6407:48
ackkdiddledan, the original issue is that if you have no binary package for that library, it fails to build. I've seen similar issues with other libraries07:48
mborzeckire08:27
mborzeckizyga: for the sake of landing this fast and since we agreed on it on friday, let's maybe stick to \n for now08:33
mborzeckizyga: interestingly the PR with udev helper still fails on opensuse https://github.com/snapcore/snapd/pull/7049#issuecomment-50717376308:44
zygaI didn't change opensuse yet08:44
mborzeckizyga: take a look at the log, it's like a lib is missing08:46
pedronismborzecki: hi, after the fact comment,  gadget.Partition probably merits a doc comment08:52
mborzeckipedronis: ok, will add08:52
pedronisthx08:54
zygahello pedronis09:00
zygawelcome back!09:00
pstolowskioh well, snap config stuff is fun09:06
Chipacapstolowski: orly09:07
diddledanackk: it looks like the failure is induced by setting `CFLAGS="-I/usr/include/python3.6"`09:09
ackkdiddledan, which is set by snapcraft?09:10
diddledanyes09:11
mborzeckimicrok8s uses a vm to start the node?09:21
diddledanno, it runs directly09:22
* zyga could use a coffee09:30
pedronismvo: hi, we still need to publish 2.39.3 to snapd, right?09:30
mvopedronis: checking09:34
pedronismvo: is not even in beta afaict09:34
mvopedronis: it only affects devices so I think we don't need to SRU it, we should make it available on GH but no need for packaging updates either09:34
mvopedronis: let me check that09:34
mvopedronis: oh, the snapd snap - yes, need to check with sergio but yes, that needs to go out09:36
* mvo prepares beta09:36
pedronisyes, the snapd snap09:36
pedronissorry09:36
* Chipaca takes a break09:43
zygamborzecki: https://github.com/snapcore/snapd/pull/704909:56
mborzeckizyga: heh, so AA blocked that09:58
zygayeah, I'm so happy we have that distro09:58
zygabrb, taking out the garbage10:00
abeatopedronis, hey, did you see latest comment from Jamie in https://github.com/snapcore/snapd/pull/5915 ? is that a thumbs up for implementing 'snapctl netplan-apply'?10:15
zygare10:21
Chipacamvo, pedronis, re some of the less serious things we talked about last week I finally heard back from my archiver :-p   http://dionecanali.hd.free.fr/~mdione/nikola-gallery/galleries/GrULiC/presentacion/10:30
Chipacacheck out those super high resolution photos taken with an actual digital camera omgz10:30
Chipacahmmmm10:34
Chipacapstolowski: for automatic snapshots I suspect having 'expires=YYYY-mm-dd' instead of 'auto' might be more useful10:34
Chipacapedronis: WDYT?10:34
mvoChipaca: woah, when were these pics taken?10:36
pstolowskiChipaca: oh wow, who is this guy on 3rd photo? :)10:36
Chipacamvo: '00 iirc10:36
mvoChipaca: amazing :)10:36
Chipacamvo: we were very proud of our server at the time: http://dionecanali.hd.free.fr/~mdione/nikola-gallery/galleries/GrULiC/machines/pv-1/10:37
Chipacaproud mostly in that we were able to afford it, and it actually booted and ran fine as long as you held down a certain capacitor on the main hdd during boot10:37
Chipaca:-)10:37
Chipaca(also that rickety shelf was actually a controlled atmosphere because it was in the atmo lab at the uni)10:40
* Chipaca still puzzled about 'snap install --verbose'10:42
ograyou should make it read the output through speakers very loudly when --verbose is set ;)10:43
pedronisChipaca: what's the question?10:43
Chipacahttps://forum.snapcraft.io/t/how-to-run-a-snap-install-verbose-in-terminal/12100?u=chipaca10:43
Chipacaogra: xsublim, but for pulseaudio10:44
pedronisabeato: we discussed that a bit more last week, I think there is some idea to do that but let "netplan apply" call it if inside a snap10:45
ograChipaca, lol10:46
abeatopedronis, you mean change netplan to call the snapd API to re-start daemons if it detects it is being run inside a snap?10:47
pedronisabeato: no, to call an api that does the full apply10:47
pedronisnot just restart daemons10:47
pedroniswell really call snapctl, not an api10:47
pedronisas low-tech as possible, basically10:47
abeatopedronis, ah, I thought that was what 'snapctl netpla-apply' was going to do10:48
abeatoso no changes there10:48
pedronisabeato: yes, but saying the snap will just call netplan10:48
abeatopedronis, so the snap will call netplan and netplan will run snapctl netplan-apply?10:49
pstolowskiChipaca: expiration instead of auto sounds fine, it would reduce the need to read expiration time again on execution of the task. a side-effect of such change is obviously the effective expiration (calculated when the task is created vs when it's executed)10:52
ograthe snap will call snapctl and netplan itself will work aotomonously is what i understand from jamies comments10:52
ogra*autonomously10:52
pstolowskiChipaca: i'm not sure if it's an issue or not, probably is fine10:52
pedronisabeato: yes, something like that10:54
abeatook, I guess that can work too10:55
abeatoogra, the wording is slightly confusing tbh, I think he wants to make all this transparent to the netplan caller10:56
ograyeah, true10:57
* pstolowski lunch10:57
Chipacadebian 9 is buster, yes?10:58
Chipacahm, 9 is stretch11:00
zygaChipaca: stretch11:00
Chipacadebian has re-exec?11:00
zygahttps://en.wikipedia.org/wiki/Debian#Code_names11:00
zygaChipaca: yes it does11:00
mvopedronis: snapd 2.39.3 is now in beta, now sergio and cert need to jump on it :)11:00
ograstreched re-exec11:00
pedronismvo: ok11:03
Chipacazyga, degville: fwiw https://forum.snapcraft.io/t/cannot-install-snap-store-on-debian-9/12077?u=chipaca11:05
degvilleChipaca: thanks for the heads-up, looking now.11:07
mvopedronis: also did some investigation about a higher errors.u.c failure rate with the 2.39.3 release for sil2100  but it looks mostly under control (one unknown)11:07
zygaChipaca: aha11:12
Chipacazyga: oho11:12
Chipacazyga: a … gruffalo?11:12
zygawhaat? :)11:13
zygamborzecki: pushed to https://github.com/snapcore/snapd/pull/702611:13
zygaI think it's 100% what all the reviewers wanted now11:14
Chipacazyga: "Aha! Oho! A trail on the snow! // Whose is this trail and where does it go?"11:14
Chipacanote you need to pronounce 'snow' to rhyme with 'oho!' or you failed11:14
Chipaca(also with 'go!' :) )11:14
Chipacazyga: https://en.calameo.com/read/000612803e258cbf5d44711:15
sil2100mvo: phew, thanks for the investigation!11:19
zygamvo: replied on that shell script question11:22
Chipacaman the snapd package in debian 9 is old and bad and nasty :-(11:29
mvozyga: thx11:29
Chipacadoesn't debian have SRUs?11:29
=== ricab is now known as ricab|lunch
cjwatsonit's certainly possible to update packages in stable releases.  I have no idea whether it would be possible to convince the stable RMs to take a wholesale update here11:30
cjwatsonlike Ubuntu, somebody would have to make the case for it.  unlike Ubuntu, you wouldn't have management leverage to apply :P11:31
zygacjwatson: FYI, flatpack updates go to backports regularly11:31
zygaI think we could consider the same path11:31
cjwatsonno harm in trying though11:32
zygathough our dependency chain may be problematic11:32
mvobackports is pretty open in general for updates (iirc)11:33
Chipacaalmost had a heart attack because debian's snapd doesn't include the fix for the ucrednet vuln11:34
Chipaca… then realised it's so old, it doesn't even have the vulnerability11:34
cjwatsonfor backports it generally just needs to be in testing11:35
cjwatsonand obviously be buildable etc.11:35
Chipacaaw man, we have management leverage to apply? somebody should've told us11:41
Chipacamaybe we were missing management fulcrum11:42
mvocachio: hey, good morning. snapd 2.39.3 snap is in beta now, please give it a go :)11:42
mvoChipaca: did you see the comment in 7025? should be an easy win and then this one can go in11:55
* Chipaca looks11:59
Chipacamvo: that i should add a spread test?11:59
* zyga is hungry, brb12:05
mvoChipaca: yeah, we can do it in a followup as well12:05
mvoChipaca: its actually so simple its probably quicker if I do it instead of writing it here :/ but oh well :)12:05
Chipacamvo: doing it now12:06
mvoChipaca: \o/12:06
Chipacahoping to get feedback from sergio also12:06
* Chipaca has poked12:06
Chipacazyga: how's your things-i-need-to-review plate? #6695 has a half review and i was wondering if you'd be able to finish it or if i should do it12:25
zygaChipaca: go for it!12:26
zygaI'm debugging mount propagation12:26
zygaand feeling hungry while the folks go for lunch12:26
* Chipaca is having lunch12:28
zygamborzecki: https://github.com/snapcore/snapd/pull/7049 is green!12:30
zygamvo: ^ this will allow to have bash snaps that don't ship /bin/sh anymore12:30
zygabase snaps, not bash snaps12:30
zygamvo: consider it for 2.40 if you want to12:31
* Chipaca implements type:bash snaps12:34
ograChipaca, nooo ... make it type:POSIX !!!12:37
Chipacaogra: name:posix, type:msdos12:37
ogralol12:37
* zyga waits for amiga people to chime in12:37
zygaand for spread to spawn12:38
Chipacaships two apps12:38
Chipacavms12:38
Chipacaand pcm12:38
Chipacaas in pc/m, not as in /dev/pcm12:38
Chipacapedronis: 'cp'?12:41
Chipaca> cp, ln use --target-directory in full12:42
Chipacaah12:42
Chipacad'oh12:42
Chipacapedronis: until I pasted it here I thought that said In, not ln12:42
pedronisChipaca: I'm asking whether cutting it down to just dir is good style or not12:42
Chipacapedronis: probably not12:42
pedronisnot sure myself12:42
Chipacatarget-directory all over coreutils12:42
pedronisto be fair, they let you use just '-t'12:43
pedronisotoh this thing will probably be used mostly by scripts/snapcraft12:43
Chipacayeap12:43
pedronisso not sure it needs to be short vs clean12:44
Chipacabah12:44
Chipaca--basename, for sure12:44
Chipaca--target-dir[ectory] was just free :-)12:44
Chipaca(and neatly avoids the awkwardness of having something called 'basename' including a directory)12:45
pedronisChipaca: otoh ubuntu-image has -w DIRECTORY, --workdir DIRECTORY12:46
cachiomvo, hey, just arrived12:46
cachioI'll start with it12:46
pedronisand -O DIRECTORY, --output-dir DIRECTORY12:46
sergiusenspedronis: Chipaca I would argue that the descriptive long option is better in scripts/code as much as using descriptive non one letter variable names :-)12:47
Chipaca--directory-dir=ectory12:47
Chipacasergiusens: agreed12:47
Chipacasergiusens: I don't think you're arguing against the thing :-)12:48
Chipaca--target-directory is happening12:48
sergiusenscoming in late, I guess the discussion is about the best long-option to use?12:48
Chipacasergiusens: yeah, target-dir vs target-directory mostly12:50
sergiusensChipaca: if it helps, the positional argument you have for `pack` is `[<target-dir>]`, so if you are looking for consistency, there is your answer12:52
Chipacadammit :-)12:52
pedronisChipaca: our helps tend to do <*-dir>12:52
* Chipaca defenestrates a rabbit12:52
pedronisthose are not option names, they are placeholders really12:53
pedronisthough12:53
Chipacapedronis: I think --target-directory is the right call12:55
Chipacapedronis: it does jump out in the options though, it's very long, but that might be ok12:56
pedronisChipaca: we do have --ignore-validation12:56
Chipacapedronis: <target-dir> is probably fine as a placeholder but I wouldn't mind if we went full ectory there as well12:56
pedronisas far as I can tell the only option that abbreviates (not counting --devmode which is called like that everywhere) is --abs-time12:57
Chipacapsh, the longest options are --unicode=[auto|never|always] :)12:57
Chipacadownload doesn't have that one yet though12:58
Chipaca(but i expect to make --unicode and --color global at _some_ point)12:58
* Chipaca stands up13:00
=== ricab|lunch is now known as ricab
Chipacapedronis: i'm about to merge the 'snap download' pr, shout if i should hold off14:07
* cachio lunch15:03
Chipacathis chipaca will spontaneously EOD in T-19 minutes15:41
ackkis it ok to start services in a post-refresh hook?16:28
=== pstolowski is now known as pstolowski|afk
zygare17:28
* zyga resumes PRs17:28
Chipacaackk: yes18:02
ardagucluhello, what is the usage purpose of snapctl?. It is an executable and as I understand some other executable starts it. Am I right?, or I miss something.18:15
ackkChipaca, great, thanks. it did seem to work fine, but wanted to be sure it's really intended to be used18:28
ackkardaguclu, snapctl is used inside snap hooks to interact with the snap system (like, get configs, manage services, ...) for the snap itself18:29
ardagucluthanks.18:32

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