mupPR snapcraft#2291 closed: meta: put environment into runner instead of app wrapper <Created by kyrofa> <Merged by sergiusens> <https://github.com/snapcore/snapcraft/pull/2291>00:02
=== gurmble is now known as grumble
=== cpaelzer_ is now known as cpaelzer
zygaI’m feeling somewhat better.05:50
zygaThe store is fully operational again, great!05:56
mborzeckizyga: hey06:01
mupPR snapd#5805 closed: cmd/snap-update-ns: enforce trespassing checks <Created by zyga> <Merged by zyga> <https://github.com/snapcore/snapd/pull/5805>06:21
* zyga is happy to land that06:21
mupPR snapd#5864 closed: make sure hostnamectl can be used on core too <Created by ogra1> <Merged by zyga> <https://github.com/snapcore/snapd/pull/5864>06:25
mupPR snapd#5857 closed: userd: extend the list of supported XDG Desktop properties when autostarting user applications <Created by bboozzoo> <Merged by bboozzoo> <https://github.com/snapcore/snapd/pull/5857>06:38
mupPR snapd#5840 closed: interfaces/apparmor, interfaces/builtin: tweaks for parallel snap installs <Parallel installs> <Created by bboozzoo> <Merged by bboozzoo> <https://github.com/snapcore/snapd/pull/5840>06:39
mvo5571 should be an easy win (just needs a second review)06:51
mborzeckimvo: 5571 appears to be merged, did you mean another pr?06:54
mborzecki5771 maybe?06:54
mvomborzecki: yes, sorry06:54
mvoclearly more tea is needed :)06:54
mupPR snapd#5771 closed: selftest: add test to ensure selftest.checks is up-to-date  <Created by mvo5> <Merged by zyga> <https://github.com/snapcore/snapd/pull/5771>07:06
zygamvo: trespassing fix is merged, shall I propose a PR to take layouts out of beta?07:06
zygamvo: full disclaimer, I'm investigating a bug that is related to propagation settings07:07
zygaso perhaps not yet but then again, it would help a lot of people with simple layouts already07:07
mvozyga: let do it07:08
mvozyga: and we can wait with the merge until you finished your investigation07:08
mvozyga: but this way spread can run etc07:08
mborzeckinice to see the diff in #5596 so short, nearly all i had in the integration branch is now in07:20
mupPR #5596: [WIP] Parallel installs integration <Blocked> <Parallel installs> <Created by bboozzoo> <https://github.com/snapcore/snapd/pull/5596>07:21
mvomborzecki: hm, this looks like the integration PR juts contains some more tests, so time to merge those too?07:22
mborzeckimvo: i'll push those separately along with couple enhancements to other tests07:23
mvomborzecki: cool07:24
mborzeckibut first coffee07:24
mupPR snapcraft#2300 opened: [WIP] plugins: remove implicit source <Created by kyrofa> <https://github.com/snapcore/snapcraft/pull/2300>07:35
mupPR snapd#5866 opened: tests: remove unneeded cleanup from layout tests <Simple> <Created by zyga> <https://github.com/snapcore/snapd/pull/5866>07:41
mupPR snapd#5867 opened: many: enable layouts by default <Created by zyga> <https://github.com/snapcore/snapd/pull/5867>07:43
zygamvo: ^ done07:46
mvozyga: ta07:51
mvozyga: hm, curious, why switching the default instead of juts removing the option entirely?08:02
mvozyga: I mean, whats the use-case, someone who feels uncomfortable with layout should still be able to disable them?08:02
luk3yxIf I make my snap private, will existing users continue getting updates?08:02
luk3yxAnd can people still install it by snap name?08:02
luk3yx(I want a semi-private snap so people download the "official" snap instead)08:03
kyrofazyga, mvo do you guys have any thoughts on this? https://forum.snapcraft.io/t/snaps-are-broken-in-bionic-lxd-container/733908:03
mupPR snapd#5868 opened: tests/main/snap-env: extend to cover parallel installations of snaps <Parallel installs> <Simple> <Created by bboozzoo> <https://github.com/snapcore/snapd/pull/5868>08:03
mvokyrofa: can you please try the switch core to "edge"?08:07
mvokyrofa: we fixed this recently but its not in beta yet, hopefully by EOD though08:08
kyrofamvo, will do, thanks08:09
zygakyrofa: replied08:14
ackkhi, I'm getting the following error running snapcraft: ImportError: /snap/snapcraft/2022/lib/python3.5/site-packages/nacl/_sodium.abi3.so: undefined symbol: crypto_pwhash_argon2id_opslimit_moderate08:15
zygakyrofa: or how your new neighbours might have said if they spoke broken Spanish like I do: yo ha añadido una respuesta08:16
kyrofaakk interesting, we've started getting that as well08:17
kyrofaBut it doesn't seem consistent-- you?08:17
zygaChipaca: heey08:17
Chipacazyga: (y)08:18
kyrofaUrgh... why can't I cancel spread...08:18
zygaChipaca: I'd like to add a tweak to yams loader for snap.yaml to indicate an error if "layouts" (plural) is used over the singular correct form08:18
zygaChipaca: I was thinking of a simple new entry to deserialise with the different name08:18
zygaChipaca: but if you have a better idea I'm all ears08:19
Chipacakyrofa: you can, it just takes a bit08:19
Chipacakyrofa: it delays because it shuts down the remotes, which can take a while to respond08:19
Chipacakyrofa: you can also ctrl-backslash, and then use the .spread* to clean up08:20
Chipacazyga: I wonder if there's a way to throw an error on anything unparsed08:21
zygaChipaca: mmm, that may be future-proof nasty08:21
zygaI'd rather not08:21
kyrofaChipaca, ah, ctrl-backslash will do it!08:21
Chipacakyrofa: usually you can then tell spread itself to clean up using e.g. spread -reuse-pid=<the appropriate number from inspecting .spread*> -discard08:23
Chipacakyrofa: spread itself will also tell you what the right argument for -reuse-pid is in its log, if it's still in your scrollback08:23
Chipacazyga: good point08:23
kyrofaChipaca, just --reuse --discard seems to work08:24
zygaChipaca: but we could _warn_ about it08:25
zyga(wink wink)08:25
Chipacazyga: if only we had something like that08:25
* Chipaca gets back to writing stuff on the forum08:25
zygaChipaca: https://github.com/snapcore/snapd/pull/586908:26
mupPR #5869: snap: detect layouts vs layout in snap.yaml <Created by zyga> <https://github.com/snapcore/snapd/pull/5869>08:26
mupPR snapd#5869 opened: snap: detect layouts vs layout in snap.yaml <Simple> <Created by zyga> <https://github.com/snapcore/snapd/pull/5869>08:27
Chipacazyga: what about: TypeLouts errorCatcher08:27
Chipacazyga: and then, type errorCatcher struct{}08:27
Chipacazyga: and then, func (errorCatcher) UnmarshalYAML(...)08:27
zygaand fail on deserialise?08:27
zygaI'll do that, great idea08:27
zygahow to tweak the error message then?08:28
zygano < > to specialise08:28
zygaI could use a generic type08:28
Chipacazyga: make it a layoutsErrorCatcher for now, we can worry about making it generic later08:28
zygaand subtype it08:29
zygaChipaca: actually, we can use the struct tags for that08:32
Chipacazyga: we can?08:32
Chipacazyga: i thought that'd be visible one step up08:32
zygaChipaca: TypoLayouts errorCatcher `yaml:"layouts,omitempty",hint:"yada yada"`08:33
zygasomething like that?08:33
Chipacazyga: does the errorCatcher deserialiser "see" that hint?08:33
zyganot sure yte08:33
zygalooking at this part now08:33
pedronis#5833 needs a 2nd review08:34
mupPR #5833: asserts,interfaces/policy: add support for on-store/on-brand/on-model plug/slot rule constraints <Created by pedronis> <https://github.com/snapcore/snapd/pull/5833>08:34
jameshIf errorCatcher is implementing yaml.Marshaler, I doubt it would have access to the tag08:41
zygayeah, that's what I see so far08:42
zygaI'm still looking for _a_ way08:42
jameshit'd have a pointer to the struct member passed as the receiver, but no way of knowing that it is a member of the struct08:42
jameshmaking the struct itself implement yaml.Marshaler on the other hand might do the trick08:42
zygabut then we're back to square one with explicit checking per-field like I do nwo08:43
zygait _feels_ like schema08:44
mupPR snapd#5813 closed: image: warn on missing default-providers <Created by mvo5> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/5813>08:44
zygaso maybe the simple fix I did now is OK before we have schema support08:44
Chipacaniemeyer: mvo: how much do we still care about old local revisions? I'm talking about local revisions from before we went negative for local08:44
Chipacathat is, revisions above 10000008:45
Chipacawe have tests for them, but I suspect we don't really support them any more outside of those tests08:45
mupPR snapd#5870 opened: tests/main/parallel-install-services: add spread test for snaps with services <Parallel installs> <Simple> <Created by bboozzoo> <https://github.com/snapcore/snapd/pull/5870>08:50
niemeyerChipaca: My only concern is people using these after installing an old image08:59
zygaChipaca: I abandon this idea now,08:59
Chipacaniemeyer: ack09:00
=== abeato_ is now known as abeato
* zyga -> coffee and snack09:19
Chipacamvo: what should I tag warnings as? 2.36?09:26
mvoChipaca: yes09:29
mvoChipaca: what is missing there?09:29
mvoChipaca: I kind of hope to do 2.36 later today09:29
Chipacamvo: https://forum.snapcraft.io/t/warnings/759909:30
Chipacamvo: that :-)09:30
Chipacadegville: https://forum.snapcraft.io/t/warnings/759909:30
Chipacadegville: let me know if you can't edit that and want to09:31
Chipaca(i know you want to :-p)09:31
zygaChipaca: how do you feel about adding a warning that warnings are added to everyone refreshing from old snapd? :)09:31
zyga(and then we remove it in the next release)09:31
Chipacazyga: before answering I need to know how many other bad ideas you've had today09:32
zygaChipaca: ... I need to re-think the idea to get up in the morning09:32
Chipacazyga: I liked at the sprint where you'd announce "this is bad idea #N++"09:32
* zyga is now being honest09:33
Chipacazyga: my main problem with your idea here is that it'd be the _only_ warning the user'd see09:33
zygain that case it'd be futile09:33
Chipacazyga: because warnings are there, but nothing uses them as yet09:33
Chipacathat's 2.37 material09:33
zygaany low hanging fruit?09:33
zygain that case I'd postpone the idea to 2.3709:34
Chipacazyga: egrep -ir '(todo|xxx).*warn'09:34
Chipacazyga: and, my secondary problem with your idea is that if we need to do that, then we failed to make them obvious and discoverable and subtle and non-intrusive09:34
zygawarning: your snapd has updated to x.yz, featuring new functionality and bug fixes09:35
zygabut that's not a warning09:35
Chipacazyga: and it'll train the user to ignore them09:36
zygammm, perhaps but that would be a nice touch09:36
Chipacaso, yeah, -109:36
zyga"snapd is getting better while you are to looking"09:36
pedronisplease rate snapd09:37
zygammm, those are way more annoying09:37
mupPR snapd#5871 opened: snapstate: only report errors if there is an actual error  <Created by mvo5> <https://github.com/snapcore/snapd/pull/5871>09:37
zygabecause they are like beggars asking for a coin, here it's more of a "what's new"09:37
pedronisanyway lots of our users will not see warnings unless gnome-software learns about them09:38
zygayeah, that's true09:38
zygait'd be more welcome if any app could do it09:38
zygawell, back to propagation09:38
pedronisthe app can do it inside themselves09:38
zygayeah but if all apps could do it in a standardised way through gnome-software it would be nice09:39
pedronismaybe, maybe not09:39
pedroniseverything already wants to speak to me09:39
Chipacapedronis: that's because you're famous09:40
mupPR snapd#5872 opened: tests/main/parallel-install-local: rename from *-sideload, extend to run snaps <Parallel installs> <Simple> <Created by bboozzoo> <https://github.com/snapcore/snapd/pull/5872>09:42
zygatoday Alice in wonderland would have to agree to a privacy policy, EULA and limited warranty before falling down the rabbit hole09:43
diddledanshe wouldn't read them thoroughly, though, or at all, and therefore be violated without her knowing09:50
mupPR snapd#5866 closed: tests: remove unneeded cleanup from layout tests <Simple> <Created by zyga> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/5866>09:52
mupPR snapd#5873 opened: tests/main/parallel-install-store: run installed snap <Parallel installs> <Simple> <Created by bboozzoo> <https://github.com/snapcore/snapd/pull/5873>10:09
jocis there any particular reason why core18 edge hasnt seen an update for about 3 weeks now?10:13
diddledanjoc: is there a problem with what's there now?10:14
jocwas hoping for at least a build with ping back as per https://forum.snapcraft.io/t/core18-included-binaries/7191/1410:14
zygajoc: yes10:17
zygajoc: it's because when it is stable we cannot break it10:18
zygaso that decision was postponed10:18
zygajoc: I _believe_ this is now the decision of the foundation team though10:18
zygamvo: ^10:18
joczyga: makes sense for stable channel but was looking at edge10:18
zygaoh, I missed that, sorry10:19
zygain that case I don't know10:19
jocmaybe the transfer to foundations is the reason for the hiatus10:19
mupBug #1771793 changed: Interface for hardware temperature monitoring <Snappy:Invalid> <https://launchpad.net/bugs/1771793>10:31
diddledanmup is slow, I changed that bug 4 minutes ago! :-p10:31
mupBug #4: Importing finished po doesn't change progressbar <iso-testing> <lp-translations> <Launchpad itself:Fix Released by carlos> <Ubuntu:Invalid> <https://launchpad.net/bugs/4>10:31
diddledansilly bot10:32
zygawhen the machines rebel mup will remember you said that ;)10:32
diddledanI, for one, welcome our shiny metal overlords10:33
Son_Gokuah bender and morpheus10:46
mborzeckicachio has set up centos images, 2018-09-27 12:47:06 Sending project content to google:centos-7-64 (sep271046-416264)...10:48
mvojoc: ping is back but the core18 snap is held up in manual review because of this, sil2100 is working on fixing this AIUI10:50
ackkhi, question about the nodejs plugin: shouldn't it run "yarn install" (with node-package-manager: yarn) automatically during the build phase?10:51
diddledanackk: I don't think yarn support works right now10:52
ackkdiddledan, looking at https://github.com/snapcore/snapcraft/blob/master/snapcraft/plugins/nodejs.py#L178 it seems it does10:53
ackkdiddledan, I mean by setting node-package-manager to yarn I do get yarn installed, but it doesn't really install stuff from the yarn.lock file automatically10:53
diddledanyes, that's what I'm referring to. it's broken.10:53
ackkah, I see10:54
ackkdiddledan, fwiw https://paste.ubuntu.com/p/tYJPk9bt6K/ worked for me10:54
kyrofadiddledan, akk can one of you please log a bug about that?10:57
ackkdiddledan, maybe you have a bit more context for the bug ^ ?10:58
diddledanI haven't really dug into it. I meant to, but then forgot :-)10:59
mupBug #1794727: node plugin doesn't run yarn install during build <Snapcraft:New> <https://launchpad.net/bugs/1794727>11:04
rbasaksnapcraft edge channel broken? beta works. edge failure: https://paste.ubuntu.com/p/GW4gWH4nrC/11:07
rbasakkyrofa, sergiusens: ^11:07
rbasakedge 2022; beta 187111:09
diddledanrbasak: kyrofa is working on it11:09
kyrofarbasak, thank you for letting us know, very nice to have folks testing edge :)11:10
kyrofaAll over it11:11
rbasakGreat, thanks :)11:11
mborzeckiChipaca: warnings aren't pushed by anything yet, are they?11:12
* zyga needs to take the dog for a walk11:17
diddledanzyga: going dogging, eh? ;-p11:19
diddledanI really should take myself for a walk occasionally ;-D11:20
diddledan<-- lazy11:20
Chipacamborzecki: correct; sudo http snapd:///v2/debug action=add-warning message="hello world"11:26
jdstrandmborzecki: hi! fyi, was looking at pt 5594 and noticed something. see https://github.com/snapcore/snapd/pull/5594/files#r22088665411:28
mupPR #5594: snap/snapenv: add snap instance specific variables <Parallel installs> <Created by bboozzoo> <Merged by bboozzoo> <https://github.com/snapcore/snapd/pull/5594>11:28
mborzeckijdstrand: looking11:28
jdstrand# bind mount *not* used here (see 'parallel installs', above)11:30
mborzeckijdstrand: this was fixed later on in https://github.com/snapcore/snapd/pull/5735 which came as a result of discussion in #5713 (parallel installs mount mappings)11:30
jdstrandowner @{HOME}/snap/@{SNAP_INSTANCE_NAME}/                  r,11:30
mupPR #5735: snap/snapenv: drop some instance specific variables, use instance-specific ones for user locations <Parallel installs> <Simple> <Created by bboozzoo> <Merged by bboozzoo> <https://github.com/snapcore/snapd/pull/5735>11:30
mupPR #5713: many: mount namespace mapping for parallel installs of snaps <Parallel installs> <Squash-merge> <Created by bboozzoo> <Merged by bboozzoo> <https://github.com/snapcore/snapd/pull/5713>11:30
jdstrandowner @{HOME}/snap/@{SNAP_INSTANCE_NAME}/**                mrkix,11:30
mborzeckijdstrand: so $HOME is instance specific path now, same as $SNAP_USER_DATA11:31
jdstrandok, I see that in that pr. thanks!11:32
mborzeckijdstrand: thank you for being so thorough11:33
jdstrandmborzecki: it sounds like there isn't anything left for me with this feature?11:33
mborzeckijdstrand: not at the moment, i'll ping you if i end up doing any tweaks to the interfaces11:34
jdstrandmborzecki: ok, thanks! I bet you're pretty happy to see this coming to a close :)11:34
mborzeckijdstrand: and thanks for the reviews again :)11:34
jdstrandnp :)11:34
mborzeckiChipaca: aargh, need http unix sockets extension11:35
Chipacamborzecki: snap install http dude11:35
mborzeckipublisher: John Lenton (chipaca), nice!11:36
Chipacamborzecki: that's why it understands snapd:/// at all :-)11:36
Chipacamborzecki: also how it's able to use snapd-control :D11:37
mborzeckiChipaca: yay, works now11:39
ograpedronis, is it normal that i dont get a snap id here ? https://paste.ubuntu.com/p/ZNcjS2P53M/11:39
mborzeckiChipaca: any plan on where do we start springking warnings first?11:39
Chipacamborzecki: also relevant, there's a unshow-all-warnings debug action11:39
ogra(i'm trying to pre-connect some interfaces from gadget.yaml but if the system doesnt see an id i can not really do that)11:40
Chipacamborzecki: egrep -ir '(todo|xxx).*warn'11:40
Chipacamvo: how're you feeling about dotfiles for 2.36?11:49
zygadiddledan: adopting a dog helped with my step count average :)11:50
ograProcess '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/sda1' failed with exit code 111:52
ograis there any chance to find out *why* it actually failed ?11:52
ograi can manually mount the device (and it properly carries an auto-import.assertion file)11:52
ograjournalctl sadly does only print that one line ... and snap changes doesnt mention it either11:53
ogra(it is a vfat formatted usb stick)11:54
Chipacaogra: dmesg might have more info11:55
Chipacaogra: that command is run via an udev rule11:55
ogramanually running the program helps a bit (tells me the user already exists, which is indeed true because i manually created it after the import failed)11:55
Chipacaogra: snapd-autoimport.rules (or 66-snapd-autoimport.rules)11:55
ograChright, might help to connect stderr to stdout here11:55
=== Chipaca is now known as Chright
ograChipaca, ^^11:56
* Chright ~> lunch-making11:57
mborzeckioff to pick up the kids11:58
=== Chright is now known as Chipaca
Chipacaniemeyer: do you want to review #5856, or should I merge it? (it has two +1s already)12:02
mupPR #5856: cmd/snap: tame the help zoo <Created by chipaca> <https://github.com/snapcore/snapd/pull/5856>12:02
* Chipaca ~> really lunch12:03
ograis there a valid way to find the name of the model from a hook without using snapd-control ?12:07
niemeyerChipaca: If it follows what we discussed, +112:09
mupPR snapd#5874 opened: Adding missing permission to create /run/wpa_supplicant directory <Created by kubiko> <https://github.com/snapcore/snapd/pull/5874>12:10
mupPR snapd#5875 opened: Avahi interface update <Created by kubiko> <https://github.com/snapcore/snapd/pull/5875>12:20
Chipacaniemeyer: there's a change, with a new Admin section that has version, warnings, okay, and get, set and wait (meaning the old Config section went away)12:24
niemeyerChipaca: Hmm12:25
niemeyerChipaca: Sounds a bit awkward at first sight12:25
niemeyerChipaca: The whole of "snap foo" is admin12:25
pedronisogra: looks like is locally installed12:25
niemeyerChipaca: and get/set/wait seem unrelated to the rest12:25
pedronisin which case I think that's the current behavior12:25
ograpedronis, indeed it is, i'm trying to develop as bunch of default connections for the interfaces12:26
ogra(trying to test them before uploading indeed)12:26
ograah, thats pretty unfortunate12:26
pedronisogra: we don't print a snap id for local snaps (even if there's a corresponding store one)12:26
ograi thought it would still pull the id from the store12:26
pedronisthat output is actually a bit confusing12:27
ograwell, it results in the connections to not happening12:27
pedronisyes, connections are only for store snaps12:27
pedronisgiven they are snap id based12:28
ograyeah, thats a bit bad for developing ...12:28
ograwould be nice if we could use some kind of fake id or some such ... i imaging other developers also would like to test their changes before pushing them to the store12:28
Chipacaniemeyer: thing is, what we discussed didn't include warnings, so those need adding somewhere; i tried to iterate on this at the sprint but we were never not busy with other stuff :-)12:29
Chipacaniemeyer: so I thought the second best thing would be to iterate in a PR12:29
niemeyerChipaca: Sure, and that's what we're doing here too I guess..12:30
pedronisogra: you can always push first as private snap12:30
Chipacaniemeyer: dunno, I'm having lunch, not iterating12:30
pedronisubuntu-image gets annoying but possible12:30
ograpedronis, sure, i can also push just to edge and leave it there but preferably i'd like to test locally first12:31
niemeyerChipaca: Well, you're iterating on lunch.. agile style? :)12:31
ograanyway, i'll get around ... but it would be great to improve in that area12:31
Chipacaniemeyer: not enough beer for this to be XP, so maybe it's scrum?12:32
mvoChipaca: dotfiles> I want it in but we can pull it into ~pre2 or ~rc1. it also need a proper name12:41
ChipacaI think dotfiles is fine12:44
mvoChipaca: even better, less churn :)12:46
diddledanhas anyone tried calling a classic snap command from a process that is itself also a classic snap? does it work?12:46
mvoChipaca: I think it needs an ack from jamie, I addressed a bunch of things but I'm not sure if its all to his satisfaction12:47
diddledanas in crossing the boundary between two classic snaps12:47
Chipacamvo: there's even a quora article about dotfiles12:47
Chipacamvo: I'm not sure if that's an argument for or against, but it's there12:47
pedronismvo: are you thinking of cutting 2.36 ?12:50
mvopedronis: I was thinking after the meeting - anything pending on your side that should be in that is not milestoned?12:52
pedronismvo: yes, 4 PRs,  they should get to reviewable today or early tomorrow12:53
mvopedronis: ok12:58
mvopedronis: is it about the brand store work?12:59
pedronismvo: yes12:59
* mvo nods12:59
* zyga tries to join the standup ...13:00
popeyThis is a fun error message...13:00
niemeyerI'll be a couple of minutes late13:01
popey(kodi isn't even installed)13:01
popeyMaybe it should say "snap "kodi" isn't installed" or something?13:01
popey(you can easily reproduce this with "snap connect foo:bar"13:03
zygapopey: I'll fix that, thanks!13:03
ogrageez, just install kodi13:04
popeykodi 18.0b2-Leia installed13:04
ograwe have a leia snap ?!?!?13:04
popey*I* do13:04
ografor armhf by chance ?13:04
diddledanok. the problem I'm encountering is specific to vscode then - it cannot launch the dotnet sdk cli which is in a separate classic snap - I've tried to do a reduced testcase but couldn't get that to fail, so something is screwey with the vscode snap13:04
popeyogra: not yet13:05
diddledansilly thing, though, is that using the inbuilt command line in vscode can launch the sdk cli13:05
ograpopey, well, once you do ... i'd be a happy tester13:05
popeybet you will13:05
ograUbuntuCoreElec !!!13:05
mupPR snapcraft#2295 closed: tests: use SNAPCRAFT_PACKAGE_TYPE everywhere <Created by sergiusens> <Merged by sergiusens> <https://github.com/snapcore/snapcraft/pull/2295>13:06
mupPR snapcraft#2296 closed: part grammar processor: lazily capture attributes from plugin <Created by kyrofa> <Merged by sergiusens> <https://github.com/snapcore/snapcraft/pull/2296>13:06
mupPR snapcraft#2297 closed: [legacy] part grammar processor: lazily capture attributes from plugin <Created by kyrofa> <Merged by sergiusens> <https://github.com/snapcore/snapcraft/pull/2297>13:06
mupPR snapd#5862 closed: cmd: fix C formatting <Simple> <Created by zyga> <Merged by zyga> <https://github.com/snapcore/snapd/pull/5862>13:06
mupPR snapcraft#2301 opened: tests: move most tests to spread and reorder travis.yaml <Created by sergiusens> <https://github.com/snapcore/snapcraft/pull/2301>13:21
Chipacadegville: I did the change in 'snap whoami' fwiw (as well as the new Other (miscelanea) category)13:50
degvilleChipaca: thanks! Sad I can no longer use my printer though.13:51
Chipacadegville: just pipe it to "lp" and it'll work13:51
Chipacadegville: I don't know if the unicode characters will work though, it might set it to banner mode and print you out of a home13:52
mvosil2100: who in foundations might know about translations ? I wonder who can approvehttps://translations.launchpad.net/snapd/trunk/+imports13:59
mvosil2100: https://translations.launchpad.net/snapd/trunk/+imports13:59
mvosil2100: someone with special powers needs to approve this one and I'm trying to find who that someone is :)13:59
Chipacadegville: AIUI Miscellanea was a countable miscellany. Ignoring the typo, did I get that wrong?14:01
Chipacathat is, they're synonyms, but miscellanea are countable and miscellany might not be14:01
Chipacabut, maybe it's archaic14:02
Chipaca:) you tell me14:02
diddledanmvo: https://upload.wikimedia.org/wikipedia/en/thumb/e/eb/SupermanRoss.png/250px-SupermanRoss.png14:02
mvodiddledan: I'm looking for that dude!14:02
diddledanall the powers14:02
mvodiddledan: in the old days it was dpm or danilo but I don't know about the present days :/14:02
sil2100mvo: this is the part of translations that I have no power over! I think Gunnar is responsible for this now14:03
mvoI will just pester random people until I find out more14:03
sil2100mvo: let me poke him through e-mail, he'll at least know14:03
mvosil2100: nevermind14:03
mvosil2100: I got some help now from colin and hopefully thats enough I will keep in mind that gunnar is the guy14:04
mvosil2100: thanks!14:04
mupPR snapd#5876 opened: selftest: rename selftest.Run() to sanity.Check() <Created by mvo5> <https://github.com/snapcore/snapd/pull/5876>14:08
Chipacamvo: do we do tarballs of releases on github?14:12
Chipacawaaait, is this something github does automagically14:13
* Chipaca prods it14:13
zygaChipaca: yes we do14:14
zygawe produce three dedicated tarballs14:14
Chipacayep, https://github.com/snapcore/snapd/releases14:14
Chipacalooking at that now14:14
Chipacazyga: i can haz darwin in lab?14:16
Chipacazyga: taw14:16
Chipacazyga: I can't even get to the lab, right now14:16
Chipacanot sure why14:16
zygaChipaca: I turned it off (fan noise)14:17
zygaChipaca: note, it's updated to Mojave and home-brew is out14:17
zygaso you need to re-do it14:17
zygawhen I looked at brew it suggested that I don't use sudo though14:17
zygaso maybe something new?14:17
Chipacazyga: not use sudo, and instead what?14:17
zygaI mean14:17
zygawhatever you need :)14:17
mvoChipaca: why do you ask?14:17
Chipacamvo: because our brew formula currently is only a head formula, and I'd like to make it do releases instead14:18
Chipacaso you can 'brew install snap' (as opposed to the current 'brew install --HEAD snap')14:18
Chipacas/as opposed/in addition/14:18
mvoChipaca: aha, nice14:19
diddledanis that a brew formula for linuxbrew or homebrew (macOS) or both? if it's targeting homebrew in some way, how's that work??!14:20
Chipacadiddledan: both14:21
Chipacaalthough the linuxbrew one is incidental, the objective is homebrew14:22
Chipacadiddledan: snap, the command, works on darwin14:22
Chipacadiddledan: snapd does not14:22
sergiusensdiddledan: the same way it works for snapcraft on mac14:22
sergiusensoh, ic, the how does that work is related to snapd14:22
diddledanI figured snap would be useless without a snapd to control14:22
sergiusensdiddledan: we want the snap command avail since it is what holds the license field validation logic14:23
Chipacadiddledan: the only thing stopping snapd from working via remote control is nasty humans14:28
Chipaca(i.e., auth)14:28
diddledanbah. filthy scum14:28
Chipacazyga: your network is slow today :-(14:29
zyganot me14:30
zygamaybe $family or weather14:30
Chipacazyga: taking *minutes* to download the go 1.11 bottle14:30
diddledantry changing the tyres14:30
zygabad mirror?14:32
zygawhere are you fetching from?14:32
zygaI see almost no traffic14:33
ograprobably there is a detour sign outside your viallge14:34
Chipacadang, 2.35.2 did not build on darwin yet.14:42
Chipacamvo: how is the .vendor. tarball built? i'd like to test it with master14:43
Chipacathat is, i need a tarball for a stable brew build, but the latest snapd_2.35.2.vendor.tar.xz doesn't cut it :-)14:44
mupPR snapcraft#2290 closed: pluginhandler: update build should overwrite organize <Created by kyrofa> <Merged by sergiusens> <https://github.com/snapcore/snapcraft/pull/2290>14:45
Chipacamvo: also: can we make those tarballs come pre-generated? ie without needing mkversion etc?14:50
kyrofasergiusens, yeah, pip is doing something weird here14:54
kyrofapip install pymacaroons==0.9.2 actually does the right thing14:55
kyrofaBut using the requirements.txt seems to be getting 0.9.014:55
kyrofaIt's interesting because pip freeze shows 0.9.2, then I actually look at it and its __init__ shows 0.9.014:55
pedronisfun, if I add an empty TearDownTest to one of the suites in snapstate some unrelated tests fail :/14:57
zygaChipaca: look at release-tools15:06
zygaChipaca: there's a script for it15:06
* Chipaca looks around for a Neal15:08
mupPR snapcraft#2280 closed: Use the better snapcraft.io/account URL <Created by evandandrea> <Merged by sergiusens> <https://github.com/snapcore/snapcraft/pull/2280>15:09
zygaPharaoh_Atem: ^15:25
* Pharaoh_Atem pops in15:26
zygaChipaca: ^15:26
* zyga runs15:26
ChipacaPharaoh_Atem: hola15:26
Pharaoh_AtemI'm confused, what's going on here?15:26
ChipacaPharaoh_Atem: is the tarball (as in https://github.com/snapcore/snapd/releases) used as part of the rpm build at any point?15:26
ChipacaPharaoh_Atem: do you need to hoop through jumps to get the version?15:27
Pharaoh_Atemnope, I set the version in the spec, and propagate it down to everything15:27
ChipacaPharaoh_Atem: I mean, the mkversion.sh script15:27
ChipacaPharaoh_Atem: you don't use it /  do things differently?15:27
Pharaoh_AtemI use it15:27
Pharaoh_Atem./mkversion.sh %version-%release15:28
Pharaoh_Atemthat's in the spec file for every snapd package derived from my packaging15:28
Chipacafair enough15:28
ChipacaPharaoh_Atem: ok15:28
ChipacaPharaoh_Atem: thanks15:28
Pharaoh_Atemno problem15:28
ChipacaI might just do that on darwin as well, then15:28
Chipacaif I can figure out the equivalent in brewish15:28
Pharaoh_Atembrew has a version variable15:29
ChipacaI was going to do a bunch of work to make mkversion itself figure it out but this is easier15:29
ChipacaPharaoh_Atem: and a revision! :-)15:29
Pharaoh_Atemhold on, I did this recently when I packaged rpm for homebrew15:29
ChipacaPharaoh_Atem: https://formulae.brew.sh/formula/rpm ?15:30
Pharaoh_AtemI rewrote that formula15:30
Pharaoh_AtemI think #{VERSION} is defined?15:30
Pharaoh_AtemI know it does some introspecting from the tarball name15:30
Chipacalowercase, at  least, works15:31
Chipacaie #{version}15:31
Pharaoh_Atemyeah, ruby is weird15:31
Pharaoh_Atemno problem ;)15:31
ograniemeyer, mvo, zyga https://forum.snapcraft.io/t/no-mdns-support-in-snaps-should-core-have-a-modified-nsswitch-conf/7603 any thoughts here would be appreciated15:32
Pharaoh_Atemmost things tend to behave like rpm spec files :D15:32
Pharaoh_Atemogra: shit15:32
Pharaoh_Atemthat explains the bugs I'm getting in Fedora15:32
Pharaoh_Atemour nsswitch.conf is getting blown away and breaking things15:32
zygaogra: hmm15:32
zygaogra: yeah, tough choice15:33
zygamaybe it should be writable?15:33
zygaand snap might manage that somehow15:33
Pharaoh_Atemzyga, ogra ^15:33
zygaPharaoh_Atem: we should not be mounting anything on the host15:34
zygaunless the code is broken15:34
zygabut then all hell would break lose15:34
Pharaoh_Atemmaybe it is, just not on Ubuntu :(15:34
zygawe test it on fedora dozens of times a day15:34
Pharaoh_Atemthis is not the only file that we're having problems with caused by snapd15:34
ograPharaoh_Atem, heh15:35
zygaPharaoh_Atem: can you see weird mounts on your snap running system?15:35
zygaif not then we are not doing that (or you are not using any snaps)15:35
Pharaoh_Atemzyga: I'll check in a bit, when I can get to my snap dev environment15:35
Pharaoh_AtemI've removed snapd and snaps from my main workstation because it kept breaking things15:35
zyga /o\15:35
Pharaoh_AtemI had no choice, I can't have a broken workstation at work15:36
Pharaoh_AtemI had snapd on here for a while to play around with base snaps and building fedora based layered snaps15:36
ograPharaoh_Atem, i'D appreciate a comment on the thread indeed :)15:37
Pharaoh_Atemogra: commented: https://forum.snapcraft.io/t/no-mdns-support-in-snaps-should-core-have-a-modified-nsswitch-conf/7603/215:42
Pharaoh_Atemzyga, ogra, the really challenging problem is that I have no idea what is causing this15:43
Pharaoh_Atemthe best I can guess is that something is doing a read+writeback and because we can't operate in strict confinement, it actually hits the filesystem and breaks things15:44
ograPharaoh_Atem, thanks !15:46
mvoChipaca: I will merge 5865 now but if my question inline is valid please do a followup (if not even better :)16:02
Chipacawhat was 5865?16:03
* Chipaca looks16:03
mvoChipaca: the translation comments16:03
Chipacamvo: aww16:03
Chipacamvo: 5856 was the one i wanted in :-)16:03
mupPR snapd#5865 closed: cmd/snap: add a bunch of TRANSLATORS notes (and a little more i18n) <Created by chipaca> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/5865>16:03
Chipacaso close16:03
Chipacamvo: :-) tahnks16:03
mvoChipaca: heh, the --help one has a +1 from me already16:04
Chipacamvo: grah, you're right about them not being the same16:04
Chipacadrat it16:04
mvoChipaca: but if degville gives a +1 too …16:04
mvoChipaca: no worries16:04
mvoChipaca: just do a followup and all is good16:04
mvoChipaca: ta!16:05
mvoChipaca: uh and 5856 has a conflict now :/16:05
Chipacamvo: tests for 5856 haven't started yet, otherwise it's gtg imo16:05
Chipacaof _course_ it does16:05
mvoChipaca: the help one only had a single +1 so far, no? /me double checks16:05
mvoChipaca: aha, silly me, two +1, one from degville  earlier. so yeah, ready once tests are happy :)16:06
Chipacaand conflcits16:06
Chipacamvo: how easy is it for you to build a fake tarball (like the ones in https://github.com/snapcore/snapd/releases)?16:07
mupPR snapd#5873 closed: tests/main/parallel-install-store: run installed snap <Parallel installs> <Simple> <Created by bboozzoo> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/5873>16:07
Chipacamvo: I tried doing it starting from dpkg-buildpackage of the git checkout and got into trouble :-)16:07
mvoChipaca: the release ones? trivial: "gbp buildpackage -S" and ./release-tools/repack-tarball ../build-area/*.tar.xz16:08
mvoChipaca: do you want one?16:08
Chipacamvo: of ~master, I could use one to test brew stable build, yes16:08
Chipacamvo: I can point it at any url (and then switch it back to github when that's done)16:08
Chipacamvo: OTOH, I can also wait for the actual tarball16:09
Chipacait's not going to land before that16:09
mvoChipaca: building one for you now16:10
mvoChipaca: try http://people.canonical.com/~mvo/.chipaca/16:12
Chipacamvo: <316:12
* zyga is starving16:14
Chipacawoooooo, that worked :-D16:15
Chipacamvo: thanks again16:15
mupPR snapcraft#2040 closed: lifecycle: always prime dependencies <Created by sergiusens> <Closed by sergiusens> <https://github.com/snapcore/snapcraft/pull/2040>16:39
mvoChipaca: \o/ great to hear that it works :)16:50
rbasakkyrofa: on the subject of testing edge, I'm looking to land a git-ubuntu regression fix and our CI is failing because our CI is using snapcraft from edge. I'm reluctant to switch it to use beta because then I wouldn't be testing edge, which is useful :)16:56
rbasakNot sure what I want exactly. I thought I'd mention the situation.16:56
kyrofarbasak, yeah, tough situation. I think we've figured out the fix, if it helps16:57
mupPR snapd#5856 closed: cmd/snap: tame the help zoo <Created by chipaca> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/5856>17:03
Chipacamvo: weee17:06
mvoChipaca: !!!17:06
* mvo hugs Chipaca 17:06
Chipacaand go-flags master is working again :-D17:06
mvozyga: 5870 looks like you almost gave a +117:07
Chipacasome of our tests broke because now it's better :-)17:07
mvoChipaca: haha17:07
Chipacaone of the fixes was that before it left space for all options, even if some of them were hidden17:07
mvoChipaca: the update will be a small burden on debian as they will also need to update the package17:07
Chipacayou can see that in 'snap help prefer' for ex17:07
mvoChipaca: cool, thanks for fixing this!17:08
Chipacathis assumes all the tests are ok, now, of course :-)17:08
mupPR snapd#5583 closed: cmd/snapd,daemon,overlord: without snaps, stop and wait for socket <Created by mvo5> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/5583>17:10
Chipacazyga: i'm done with the lab, thanks17:18
mupPR snapcraft#2302 opened: requirements.txt: stop using pymacaroons-pynacl <Created by kyrofa> <https://github.com/snapcore/snapcraft/pull/2302>17:22
mupPR snapcraft#2303 opened: requirements.txt: stop using pymacaroons-pynacl <Created by kyrofa> <https://github.com/snapcore/snapcraft/pull/2303>17:22
zygamvo: looking at 587017:51
Chipacaso, we were using a bug in go-flags :-(17:52
Chipacasad trombone17:52
zygaChipaca: oh?17:52
zygaChipaca: cool, what did you find?17:52
Chipacawe use PassAfterNonOption17:52
Chipacabut only really use it in 'snap run'17:52
zygaChipaca: is it the time when we roll our own?17:52
zygaor do we have a way to fix it17:53
Chipacabah, I think this is fixable17:53
Chipacain a few ways17:53
Chipacabut the basic thing is: PassAfterNonOption means "be strict POSIXly"17:53
Chipacathere was a bug in go-flags where it didn't actually do its job17:53
Chipacaso you could have "snap install foo --classic" mean the same as "snap install --classic foo"17:53
Chipacawhich is explicitly not what PassAfterNonOption should do: with PassAfterNonOption, the first --classic is no longer an option17:54
Chipacait's an argument, and is passed to the command's Execute as such17:54
Chipacabut of course we want "snap run http --help" to have that help reach http17:54
Chipacaeasy fix: require everybody using snap run directly to do "snap run -- http --help17:55
Chipacahacky fix: peek at os.Args, and rewrite it to add a -- for 'snap run'17:56
Chipacathe first one is trivial, only really affects tests on our end17:56
Chipacasnapped apps continue to work, because we'd add the -- ourselves17:56
Chipacaonly people we'd be breaking are those that use 'snap run' with arguments17:56
Chipacabut … that's probably some people17:56
Chipacaso, leaning towards the hacky don't-break-people one17:57
sergiusensChipaca: the joys of wanting to mix strict arg parsing with friendly arg parsing :-)18:07
zygaChipaca: still hear?18:23
zygaI have a branch with the Mk** helpers moved18:23
zygait's a bit big18:23
zygawanna see?18:24
zygaChipaca: https://github.com/snapcore/snapd/pull/5877 I opened for RFC18:34
mupPR #5877: cmd/snap-update-ns,osutil: move helpers to osutil <Created by zyga> <https://github.com/snapcore/snapd/pull/5877>18:34
mupPR snapd#5877 opened: cmd/snap-update-ns,osutil: move helpers to osutil <Created by zyga> <https://github.com/snapcore/snapd/pull/5877>18:34
Chipacazyga: hmmm18:34
Chipacazyga: are you all hyped up, or are you wrapping up your day?18:34
zygamore of a task switching18:34
zygathis was a distraction today18:34
zygaI'm working on something more involved18:34
zygaalso upset about MBP - still not fixed18:35
zygaand apparently service people broke the screen /o\18:35
zygaat this rate I'll get crumbs next week18:35
zygait was such a nice machine18:35
Chipacazyga: official service?18:36
zyganot real apple but authorised services18:36
zygaI'm sure they will fix it18:36
zyga(or just give me a brand new unit)18:36
zygabut ... what the hell happened18:36
zygamaybe I should just not think more about it18:37
zygaand just wait patiently18:37
zygaand not get more gray18:37
zyganext time I'll open it in the store18:37
zygaand just ask for a different unit18:37
zygaand let them turn gr{a,e}y18:38
zygawhich is it?18:38
Chipacazyga: depends on where you're standing when you say it18:39
Chipacaanyway, it's 19:40, I need to make dinner18:40
zygaChipaca: https://github.com/snapcore/snapd/pull/5877 landing would make me happy18:40
mupPR #5877: cmd/snap-update-ns,osutil: move helpers to osutil <Created by zyga> <https://github.com/snapcore/snapd/pull/5877>18:40
zygaand I can then go and rest18:40
zygayou're right, EOD time18:40
Chipacaand instead I'm knee deep in making our thing work with the new go-flags18:40
Chipacazyga: I'll look at that last one after dinner, k?18:40
zygano no wrong branch18:40
zygabut sure18:40
Chipacawell, leave the one you want me to look at18:40
Chipacaif it's too big, i'll punt18:41
zygameant https://github.com/snapcore/snapd/pull/586918:41
mupPR #5869: snap: detect layouts vs layout in snap.yaml <Simple> <Created by zyga> <https://github.com/snapcore/snapd/pull/5869>18:41
Chipacaotherwise i'll sleep at 3am again18:41
JohKhow do I get snap apps to work when my home is symlinked to a different drive?19:07
gQuigsis there something obvious I'm doing wrong here: https://pastebin.ubuntu.com/p/jgMBPYSYBz/   following workaround from forum - https://forum.snapcraft.io/t/importerror-no-module-named-six/1002/319:07
JohKI get similar errors to what users report when their home is on a nfs mount19:12
JohKi.e. for pycharm or spotify19:12
ograJohK, stop using a symlink and use a bind mount instead19:15
zygaJohK: hey, as ogra said you must use a bind mount instead19:15
zygaor just mount your home directory to /home/$LOGNAME19:16
JohKI use this setup for 15 years...19:18
JohKogra: Really? I use this setup for 15 years...19:18
JohKogra: why is not having a symlink a requirement for snap to work?19:20
JohKwell I guess Im not using snapd then, thx19:21
zygabecause symlinks and real directories are not the same, have fun with your setup for the next 15 years19:57
mupPR snapd#5878 opened: overlord/ifacestate: make sure to pass in the Model assertion when enforcing policies <Created by pedronis> <https://github.com/snapcore/snapd/pull/5878>20:00
Chipacazyga: chill20:05
Chipacazyga: you there?20:21
Chipacazyga: comment on your pr20:24
Chipacazyga: and a suggestion coming up in diff form20:24
zygaon 5877?20:24
Chipacazyga: https://pastebin.ubuntu.com/p/V2NbGY6GPp/20:24
zygadid you see what the error looks like if you try that?20:25
Chipacazyga: yes20:25
zygait's less sublime, talking about unmarshaling and such20:25
zygaAFAIR, it was less pretty than now20:25
Chipaca1 sec20:25
Chipaca$ snap pack . ..20:26
Chipacaerror: cannot pack ".": cannot parse snap.yaml: cannot use "layouts" (plural), please use singular "layout" instead20:26
zygawe _can_ parse snap.yaml20:26
zygawe just don't like what we found20:26
zygaand without the extra change?20:26
Chipacazyga: without which extra change?20:26
zygaI mean, without your suggestion20:26
Chipacazyga: it's in the comment: error: cannot pack ".": cannot use "layouts" (plural), please use singular "layout" instead20:27
Chipacaand this is with pack, where you know at least that you're building this20:27
zygaI was thinking about making a error type and returning it instead20:28
zygaand tweaking the error reception in the client20:28
Chipacaimagine getting «cannot install "foo": cannot use "layouts"»20:28
zygabut I think it's too late for that today, I was about to hit the bed20:28
zygabut I'll try both tomorrow20:28
Chipacazyga: ?20:28
zygaand see if the error looks nice in all cases (I was thinking of "snap try" mostly)20:28
Chipacazyga: there is no client/server for 'snap pack'20:28
zygayou can make a snap with older version and install it20:29
zygathat's what I meant, sorry for not being clear20:29
zygaI'll continue tomorrow :)20:30
Chipacazyga: g'night20:30
Chipacai'm off as well20:30
mupPR snapd#5879 opened: vendor, cmd/snap: refactor to accommodate the new less buggy go-flags <Created by chipaca> <https://github.com/snapcore/snapd/pull/5879>20:54
sergiusensstgraber: hey there, everytime my lxd snap updates (just did recently) my container(s) die(s); from what I recollect this should not be the case so wondering if there is a way to monitor what is going on21:27
stgrabersergiusens: what channel?21:28
stgrabersergiusens: journalctl -u snap.lxd.daemon -u 50021:28
sergiusensstgraber: latest/stable is where I saw it just now21:28
sergiusensstgraber: exit with 13721:31
sergiusensstgraber: for context https://pastebin.ubuntu.com/p/8qc6VHhNsW/21:31
stgrabersergiusens: "dmesg" output?21:33
sergiusensstgraber: maybe this https://pastebin.ubuntu.com/p/wH2WCMFjsD/ ?21:37
sergiusensstgraber: I can hand over the full output if you want too21:37
stgrabersergiusens: nah, unrelated, full output please21:38
stgrabersergiusens: also, the journalctl didn't show you anything more than what you pasted? that was way shorted than 500 lines21:38
sergiusensthere's more in the journal, I'll send over21:39
sergiusensstgraber: full journal https://pastebin.canonical.com/p/39DRDZBXtm/21:40
sergiusensto any other person, sorry for the private link, but I haven't checked if this leaks any sensitive data 🙂21:41
stgrabersergiusens: full dmesg?21:42
stgrabersergiusens: ah and "snap version" too please?21:42
sergiusensstgraber: https://pastebin.canonical.com/p/CMxrySp2cB/21:43
sergiusensstgraber: http://paste.ubuntu.com/p/Q3Y5mjjj54/21:44
stgrabersergiusens: "snap changes" output?21:44
sergiusensstgraber: I think you want this specific change http://paste.ubuntu.com/p/mRqcZrcPyv/21:46
sergiusensan autorefresh change that is21:46
sergiusenshmm, let me see if I can get those out in english client side21:46
sergiusensmeh, no21:47
sergiusens"""Detener los servicios del snap "lxd"""" translates to """Stopping services from the snap "lxd""""21:49
stgraberoh, that's actually very interesting21:50
stgraberwell, maybe not21:50
stgrabercan you show me cat /proc/$(pgrep daemon.start)/environ | tr '\0' '\n'?21:51
sergiusensright, it doesn't say exactly if it will ignore the stop or not after going in21:51
stgraberwell, no, it not being in english is the interesting part :)21:51
stgraberbecause we parse that in our stop code21:51
stgraberbut the environment of the stop code should be such that it's in english21:52
sergiusensstgraber: my locale at installation time is spanish https://pastebin.canonical.com/p/zsw3RDXCtP/21:53
stgrabercrap, I didn't expect systemd to respect it :)21:53
sergiusensthis is why we don't do translations for these things :-P21:53
stgrabersergiusens: LANG=C.UTF-8 snap changes21:53
sergiusensstgraber: tried that already :-)21:54
sergiusensstgraber: so it means the changes are generated by snapd, they are also ephemeral, so I suppose that restarting snapd will kill the changes21:54
stgrabersnapd stores them as a string in the user's language?21:55
sergiusensI am not sure about that, I hope not; but I do suppose that snapd returns output to the snap command already in the set lang21:55
stgraberoh, so the daemon is returning translated strings then, great...21:56
sergiusensyes, it seems so21:57
sergiusensit wouldn't be that bad if the client could tell it the language it wanted those strings in21:57
sergiusensbut alas, that does not seem to be the case21:58
stgraberdo you know if there's some new way for us to figure out if we're dealing with a unit restart due to refresh vs unit restart due to host shutdown?21:59
sergiusensstgraber: given the timestamps, this is certainly a refresh; change 19 which I pasted is from auto-refresh22:00
sergiusensI was actually doing something else when I saw the container go away22:01
stgrabersergiusens: yeah, I'm sure that's the problem, I'm just looking for ways to fix it which don't involve me hardcoding strings for every language we may get back from snapd :)22:01
stgrabersergiusens: curl --unix-socket /run/snapd.socket snapd/v2/snaps/lxd -s | jq .result.status22:04
stgrabersergiusens: is this in english?22:04
sergiusensfwiw https://forum.snapcraft.io/t/snap-snapd-language/760722:08
sergiusensstgraber: yes, that is in English22:09
sergiusensreturned "active"22:09
stgrabersergiusens: unfortunately that won't quite be enough as it won't tell me if the snap is being removed, poking at the /changes API instead now22:09
sergiusensok, I will have to commute back home right now, but I can get back to this in a bit, just leave me anything required to check22:10
stgrabersergiusens: curl --unix-socket /run/snapd.socket snapd/v2/changes?select=all\&for=lxd -s | jq -r ".result | .[] | .kind"22:13
stgraberI think that will be our way out of this problem, much more reliable than parsing snap changes22:14
=== slangasek is now known as vorlon
=== vorlon is now known as slangasek
=== slangasek is now known as vorlon
stgrabersergiusens: wrote a new query tool that pokes the API directly, building a new snap with that, will test tomorrow (in Europe now, so a bit late here)22:57

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