/srv/irclogs.ubuntu.com/2018/11/20/#snappy.txt

mborzeckimorning06:04
mborzeckimvo: hey06:13
zygaHey06:25
mvohey mborzecki and zyga06:25
zygamvo: I sent a small tweak to the apt hook test06:25
mborzeckizyga: hey06:25
mborzeckiplenty of reviews, unfortunately all are blocked by the tests :/06:26
zygaYeah06:26
mvozyga: yeah, I approved it already06:27
mvozyga: nice one06:27
mvozyga: I think we still need a test that checks if we update the catalog on startup06:27
mvozyga: but this one is nice as it adds clarity (and clean messages)06:27
mvomborzecki: yeah, tests are very unhappy06:28
mvozyga, mborzecki did anyone talk to the store last evening about the 403?06:28
zygaYes06:28
zygaDaniel is on this06:28
mborzeckigreat06:28
zygaI was thinking that perhaps we should ask for a bug report to track06:28
mvogreat06:29
zygaEven if only the bug is public06:29
zygaI need to take Bit out06:29
zygaBrrr06:29
zygaSee you soon06:29
mwhudsonis running hello-world.evil as root supposed to hit the permission denied error?06:54
mvomwhudson: yes06:54
mwhudsonbecause i get the permission denied as a regular user on debian06:55
mwhudsonbut not as root06:55
mwhudson(debian testing)06:55
mvomwhudson: looking06:55
mwhudsonmvo: tbh i'm surprised i get it at all on debian :)06:55
mwhudsoni didn't think the kernel had all the apparmor snapd needed06:56
mvomwhudson: this is what I see on ubuntu https://paste.ubuntu.com/p/Xy8BKNYwkT/06:57
mvomwhudson: [509022.132463] audit: type=1400 audit(1542697004.011:11343): apparmor="DENIED" operation="mknod" profile="snap.hello-world.evil" name="/var/tmp/myevil.txt" pid=29003 comm="evil" requested_mask="c" denied_mask="c" fsuid=0 ouid=006:57
mborzeckimwhudson: can you post the output of `snap debug sandbox-features` somewhere?06:57
mwhudsonmborzecki: http://paste.debian.net/1052415/07:20
mvomwhudson: hm, those apparmor options looks good, and yet hello-world.evil is not giving you an error? anything interessting in dmesg (I guess not) when you run this?07:27
zygamwhudson: as a user, do you get a denial?07:29
zygaAFAIK we didn't enable the feature outside of arch and tumblweed07:29
mwhudsonno, nothing in dmesg07:34
mwhudsonfor either user or root07:34
zygaright07:34
zygamaybe the non-root case is just failing on regular permissions?07:34
zygamvo: are things still failing on the store?07:35
mwhudsonzyga: hah yes, it failed as a user because i'd run it as root first...07:35
zyga\o/07:35
zygamwhudson: having said that I  think we could enable apparmor on debian now07:35
mwhudsonzyga: i though the plan was to interrogate the kernel and decide on that, not based on distro07:36
mvozyga: we had one successful run07:36
mwhudsonzyga: but yes07:36
zygayes but it's not just the kernel07:36
zygawe check the kernel07:36
zygabut we also check the distribution07:36
zygabecause apparmor userspace also matters and that was a simpler check07:36
mborzeckizyga: hm another sysctl tweak needed for rhel, max_user_namespaces is 0 by default :/07:36
mwhudsonah07:36
* zyga wonders if 4.20 will have everything07:37
zygauser namespaces?07:37
zygacan you tell me more about that07:37
zygawe don't use that07:37
zygamwhudson, mborzecki: I'd love some eyes on https://github.com/snapcore/snapd/pull/611107:37
zygaI know it's probably most distant to being useful for debian at this stage07:37
zygabut that's the eventual goal, cut packaging cruft by using packaging/snapd.m07:38
zygasnapd.mk07:38
mwhudsonzyga: "Fortunately the makefile world is much saner" i feel sorry for you!07:38
zygahaha, because of RPM of because thinking Makefile is saner :) ?07:38
zygaI mainly cannot understand how RPM macros can be this crippled07:39
zygathey are an oozing mess IMO07:39
mborzeckizyga: we don't but there's a test to check whether snaps can do, see tests/regression/lp-161868307:39
* zyga looks07:39
mborzeckizyga: otoh, it's probably ok if users enable it themselves when needed07:39
zygahah07:40
zygathat's a very specific test :-)07:40
zygamborzecki: the test can also toggle that IMO07:40
zygamborzecki: it will also self-document07:40
mborzeckifair enough :)07:40
zygaI think this is a test where we used to break LXD07:40
=== pachulo_ is now known as pachulo
=== pstolowski|afk is now known as pstolowski
pstolowskimorning08:02
pstolowskizyga: i'm going to work on the yesterday's implicit hooks+interfaces issue, ok?08:19
zygapstolowski: sure, thank you08:19
zygaI can close that tab :)08:19
pedroniszyga: hi, I saw you are looking into catalogs, afaik  /names was not working in the store last night and fixed just this morning08:57
zygahey08:57
zygayep, I know, I talked to daniel about it08:57
zygaI improved the test to fail faster with a clear error message08:57
zyganow back to ongoing tasks, trying to land stuff that's pending08:57
pedroniszyga: ok, np, just making sure it was on the store side08:59
pedroniswasn't sure if people pinged08:59
zygayep08:59
mborzeckizyga: can you look at https://github.com/snapcore/snapd/pull/6168 later on?08:59
zygamborzecki: sure08:59
zygaoh08:59
zygaI did, I have pending review comments08:59
mborzeckiheh :) post'em08:59
mborzeckizyga: i reverted the snap-mgmt piece09:00
mborzeckibtw. i installed kde on my laptop yday, the theming is off too, i have it set up to use the breeze theme for gtk apps and it's clearly using a different theme as well as font size09:01
zygamborzecki: done09:05
zygapedronis: I'll land 6150 with --from-snap-confine and do a small PR on top to rename that to --inherit-lock so that we don't lose a test slot09:06
zygaI need a 2nde review on https://github.com/snapcore/snapd/pull/614809:19
zygamvo did one09:19
zyga+0, -7 branch09:19
zygamborzecki: could you look at https://github.com/snapcore/snapd/pull/611109:20
zygamborzecki: if not for centos, I'd love to have this for the next suse release09:20
mborzeckihttps://github.com/snapcore/snapd/pull/6168 - centos & spread is green :)09:26
mvomborzecki: nice!09:26
mborzeckimvo: and needs a 2nd review09:27
mvomborzecki: yeah, neck-deep in fontconfig again right now :(09:31
mborzeckimvo: np, i'll poke pstolowski09:31
mborzeckipstolowski: would you like to review 6168?09:32
pstolowskimborzecki: sure09:32
mborzeckipstolowski: ta09:32
zygabrb coffee09:32
zygaand re09:48
zygahey Chipaca, cachio09:49
zygaSIGILL during go build https://www.irccloud.com/pastebin/n7OW8M6x/09:50
zygamvo: ^09:50
zygafirst time I saw this09:50
zyga18.1009:50
cachiozyga, running a test?09:53
cachiohey09:53
zyganot even that, just building09:54
zyganot a test, building snap-seccomp09:54
Chipacamvo: tinyproxy is growing up 😍09:57
mvoChipaca: heh, yeah09:57
mvoChipaca: maybe we need to rename it to lesstinyproxy09:57
Chipacamediumproxy09:57
Chipacamidproxy?09:57
mvolol09:57
cachiozyga, I'll try to reproduce it09:58
zygaChipaca: dwarf proxy ;)09:58
Chipacazyga: yeah... no, not that09:59
zygaright? :)09:59
mvocachio: good morning! are things good for promotion of 2.36.1 to stable?09:59
mvodid we loose mup again?10:02
mvomup: hello10:02
zygaChipaca: https://github.com/minimaxir/big-list-of-naughty-strings :D10:02
cachiomvo, hi10:02
Chipacazyga: yeah :-)10:02
Chipacazyga: try setting that as the description of your snap10:02
cachiomvo, everything is ready10:02
cachiomvo, let me check with store team10:03
mvocachio: awesome, thank you10:04
cachiomvo, np10:05
zygamborzecki: remember this bug? https://github.com/snapcore/snapd/pull/6159 :D10:06
zygait's green10:06
mborzeckiheh, let me review that10:06
zygait's not that short as I made more changes to tests and merged two functions together for simplicity10:06
zygabut the spread test is nice and much better than before10:06
zygathanks!10:06
zygaone more to the done lane :)10:06
zygaChipaca: hey, can you look at https://github.com/snapcore/snapd/pull/6174 - I'm not sure if this is done right wrt layering in the daemon10:10
Chipacazyga: in 510:11
zygamainly about how to get to refresh catalogs from api.go10:11
zygasure, thanks!10:11
diddledanwho can I talk to about a missing repo in my build service dashboard?10:41
diddledanspecifically it's one that I've previously added that has disappeared10:41
zygadiddledan: not sure, anyone from the store I presume but not sure who's online now10:41
diddledanI need to trigger a build so I went looking for it, but can't find it10:42
diddledanthe snap is still in my store dashboard, so I figured the store is correct10:42
diddledanit's only the build service that's missing it10:43
diddledanI tried to re-add it and it just sits there doing nothing10:43
diddledanjust sits there with the spinner spinning: https://usercontent.irccloud-cdn.com/file/LDUEyS53/image.png10:44
mborzeckiopened a forum topic about theming under kde: https://forum.snapcraft.io/t/gtk-app-themes-under-kde/8597 (cc popey)10:45
popeydiddledan: I'd file a bug https://github.com/canonical-websites/build.snapcraft.io/issues10:46
diddledanpopey: interesting that you've filed a bug with a similar console log from the browser from when I try to re-add the repo to build: https://github.com/canonical-websites/build.snapcraft.io/issues/115510:48
popey:)10:48
popeyLukewh: ^10:48
Lukewh👀10:49
diddledanhere's my bug: https://github.com/canonical-websites/build.snapcraft.io/issues/117510:55
cachiomvo, 2.36.1 is stable10:56
mvocachio: \o/10:57
cachiomvo, wiki updated too :)10:58
Chipacamvo: do you remember the user request that caused us to look at `snap list --format=....`?11:01
Chipacamvo: found it11:03
mvoChipaca: ok11:08
* zyga considers lunch12:03
zygamvo: did you see https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/180418612:18
mvozyga: yes, I think this will be fixed with 615612:19
* zyga goes for lunch 12:19
zygayeah, I just wanted to have this on your radar12:19
zygaheh12:49
zygaI found some nice piece of garbage12:49
cachiomvo, hey, apt-hooks test failing because /var/cache/snapd/commands.db does not exist on ubuntu 18.0412:50
Chipacamvo: are the 2.36 and 2.37 lanes 'done' lanes, or 'doing' lanes?12:51
Chipacaand what's the relation between 19.04 done and 'done' done12:51
* Chipaca is lost in a maze of lanes, all alike12:51
cachiomvo, I see this error https://paste.ubuntu.com/p/SxD8Jr2XJb/12:51
Chipacacachio: store names endpoint 403'ed well into last night12:53
Chipacaor timed out, yes12:53
zygaChipaca: they are done lane12:53
cachioChipaca, this is happening now too12:53
zygabut scoped to release version12:53
cachioI just reproduced that12:53
Chipacacachio: really? seems to be working here :-(12:54
cachioChipaca, it is happening sporadically in master12:54
Chipacacachio: 'timeout reading body', or 403?12:54
cachioI just executed that on ubuntu-18.04-64 with -repeat 5012:55
cachioChipaca, the timeout12:55
Chipacacachio: locally, or google cloud?12:55
cachioChipaca, https://paste.ubuntu.com/p/2xsHgkgyNs/12:56
Chipacai'm seeing 8s, which is very close to the 10s timeout we have12:56
cachioon google cloud12:56
cachiorunning the test apt-hooks12:56
Chipacaok12:57
Chipacazyga: I've renamed them to say Done, then12:58
zygaChipaca: I see now, nice12:58
zygaclearer12:58
Chipacacachio: it's still a store issue though; not much we can do from our code12:58
zygabtw12:58
Chipacazyga: i'm not really sure the 2.36 and 2.37 were done vs doing12:58
zygathis 5K monitor really pays for itself when you use our trello board :-)12:58
Chipacazyga: but titling them will make it clearer if they weren't (somebody'll shout)12:59
zygaChipaca: those were done12:59
zygayep12:59
cachioChipaca, nice, thanks13:01
Chipacacachio: when exactly were those tests run?13:01
Chipacawgrant wants to know :-)13:02
cachioChipaca, I saw that error on travis13:02
Chipacacachio: that's not an answer :-)13:02
wgrantThere wree 403s until I woke up about four hours ago. There were two brief periods of timeouts about an hour ago as fallout from the core release.13:03
cachiowgrant, it failed few ours ago on travis13:03
cachioChipaca,13:03
wgrantIt's a criminal offense in most jurisdictions to report store problems without specific error messages and times.13:03
Chipaca'about an hour ago' matches that fallout window13:03
cachiowgrant, Chipaca then I rexecuted that failed test from my machine few minutes ago13:03
zygalol13:03
zygathis should go to quotes :)13:03
cachioand I could reproduce it13:03
Chipacacachio: what's your ping to api.snapcraft.io?13:04
cachioChipaca, wgrant I reproduced the error running from my machine the srpead test 30 minutes ago13:04
cachioChipaca, the test was executed on a gce instance btw13:04
Chipacaah13:04
Chipacacontrolled locally, but run on gce, got it13:05
cachioyes13:05
mborzeckioff to pick up the kids13:05
cachioChipaca, spread -debug -repeat 50 google:ubuntu-18.04-64:tests/main/apt-hooks13:07
cachioI reproduced that by running that test13:07
cachioon master13:07
cachiomborzecki, centos in13:24
mvoChipaca: 2.36,7 is done13:27
ahasenackhi, is snap supposed to honor the https_proxy env var?13:31
ahasenackI'm exporting it just before a snap install, but it's being ignored13:31
ahasenack(no sudo, I'm root already)13:31
mvosergiusens, kyrofa hey, can someone help me with "Failed to pull source: unable to determine source type of 'fc/'." ? context is https://github.com/snapcore/core/pull/99 - what is puzzling is that this works in https://code.launchpad.net/~mvo/+git/fontconfig-multi-cache13:32
ahasenackhttps://pastebin.ubuntu.com/p/j7pwP4brsS/13:32
mvoahasenack: its complicated - snapd will honor it but the snap command will not pick it up and transfer it to snapd (if that makes sense)13:33
mvoahasenack: so "http_proxy=... /usr/lib/snapd/snapd & ; sudo snap install foo" would work (in theory)13:34
ahasenackI see, it's the daemon13:34
mvoahasenack: we could make this work by simply reading http_proxy in snap (the cli) and when talking to the daemon setting it for these requests13:35
ahasenackinstalling lxd suddenly became harder13:35
mvoahasenack: this would require a bit of code and a design discussion. I think its what most users expect though13:35
ahasenacklooks like I can add it to /etc/environment13:35
ahasenackand restart snapd13:35
ahasenackEnvironmentFile=-/etc/environment <-- because of that in its service file13:36
mvoahasenack: yes, or "snap set core https.proxy=..."13:36
mborzeckicachio: pstolowski: thanks!13:47
Chipacamvo: and was I right in thinking that the bare "Done" was "Done on master"?13:49
mvoChipaca: done for things that cannot be associated with a release13:51
niemeyerHeya13:57
niemeyerI'm updating the blender snap during intervals here at the sprint13:58
niemeyerI just found what seems like another minor bug on the handling of installation flags:13:58
niemeyer% sudo snap install blender_2.79b_amd64.snap --dangerous13:58
niemeyererror: cannot perform the following tasks:13:58
niemeyer- Mount snap "blender" (unset) (snap "blender" requires classic confinement)13:58
niemeyerLooks like classic was ignored until too late13:58
niemeyerChipaca: ^13:58
Chipacaniemeyer: yes, i noticed that as well. it's just how we handle the error, fwiw14:01
ChipacainstallPath doesn't do the handholding install does14:01
Chipacaand the blurb is slightly off for installPath14:01
Chipacabut it needs to do something14:01
Chipacai'll get to it14:01
Chipacacurrently on the warnings-as-yaml thing14:01
niemeyerThanks!14:01
* Chipaca lags14:01
niemeyersergiusens: snapcraft is doing something curious with multi-line strings14:09
niemeyer  \ compositing and motion tracking, even video editing and game\ncreation.\n\nBlender\14:10
niemeyer  \ is a public project, made by hundreds of people from around the\nworld; by studios\14:10
niemeyersergiusens: That's ending up in meta/snap.yaml14:10
mvocachio: do you happen to know the status of the 2.35.5 SRU? is all the validation done from our side?14:45
cachiomvo, checking14:53
cachiomvo, last sru done is for 2.35.414:54
cachioI can make 2.35.5 today14:55
mvocachio: great, thanks14:55
mvocachio: lets try to get it out of the door, I pushed 2.36 into the sru queue but it can sit there14:55
cachiomvo, sure, I'll complete it todya14:56
mvocachio: thank you14:56
niemeyerjdstrand: Heya14:56
jdstrandniemeyer: hi :)14:56
niemeyerjdstrand: Apparently the store reviews are blocking  the title field:14:56
niemeyer"  - unknown entries in snap.yaml: 'title'"14:56
niemeyersergiusens: This is an issue as well for snapcraft ^14:57
niemeyerBoth license and title are being blocked14:57
jdstrandniemeyer: oh, huh. when was that added?14:57
niemeyerjdstrand: Curiously, it's been a while14:57
jdstrandthat is curious14:58
niemeyerjdstrand: I think we didn't really notice because most people are either setting it in the store UI directly, or don't care14:58
jdstrandniemeyer: is this something where snap.yaml doesn't know about it but snapcraft is passing it through cause it is in snapcraft.yaml? of is it legitimate for snap.yaml?14:59
jdstrands/of is/or is/14:59
niemeyerjdstrand: It's been legitimate in snap.yaml for long now14:59
jdstrandhuh14:59
* jdstrand shrugs14:59
jdstrandI'll fix it14:59
niemeyerjdstrand: Again, I think it's just that most people that care about the title has been editing the whole metadata directly in the web UI14:59
niemeyerjdstrand: So bypassing the review14:59
niemeyerjdstrand: It gets down to snapd on install15:00
* jdstrand nods15:00
jdstrandI see it in info_snap_yaml.go15:00
jdstrandI'll double check is anything else is missing while I'm at it15:00
jdstrandeverything else is there15:01
mborzeckimvo: https://paste.ubuntu.com/p/vbJPDwH5YF/15:06
cachiomvo, http://people.canonical.com/~ubuntu-archive/proposed-migration/bionic/update_excuses.html#snapd15:08
cachionot tests executed on bionic for 2.35.515:08
niemeyerjdstrand: Thanks! Can we get it through as well please15:09
niemeyerjdstrand: I also have 2.80 behind it15:09
cachiomvo, Not touching package due to block request by freeze (contact #ubuntu-release if update is needed)15:09
jdstrandniemeyer: yes, I'll review the queue15:09
niemeyerjdstrand: Danke!15:10
sergiusensniemeyer: thanks. I am off today but will work on title tomorrow (license should work without passthrough in 3.0). I will look at the code or ask Chipaca about rules for title since he has been doing the snap pack validation work15:26
sergiusensniemeyer the line breaks might be related to the use of | for description, we recently switched it to >. Thanks to sparkiegeek15:28
niemeyersergiusens: | is what we want in general I believe15:29
niemeyersergiusens: In either case, that looks like a longstanding issue.. I have pretty old snaps that have the description mangled like that15:29
jdstrandroadmr: hi! can you pull r1156 of the review tools?15:30
roadmrjdstrand: howdy! totally, will do15:30
jdstrandthanks15:30
sergiusensjdstrand: I was not aware title made it in. But do tell me when you start allowing it so we do not block new users when using it. Passthrough should work in the meantime.15:31
jdstrandniemeyer: both are approvied15:31
jdstrandsergiusens: my ping to roadmr is for that15:32
* sergiusens goes back to being off15:32
jdstrandsergiusens: so feel free to commit at your convenience. and enjoy your day off :)15:32
mborzeckizyga: can you try this in a vm? https://gist.github.com/bboozzoo/d4b142229b1915ef7cc0cf8593599ad9 i can reproduce the mount problem quite reliably (you need to have bc installed)15:34
mborzeckijust systemd and mount units15:34
kyrofamvo, I just pulled that core PR #99, and those parts pull fine for me15:34
kyrofaDid you sort it out?15:35
niemeyersergiusens: Let's please catch up when you are back. Using ">" is probably a bug too, but likely not it. I'll report a bug.15:36
mvokyrofa: it fails in LP15:38
mvokyrofa: it works locally15:38
mvokyrofa: I'm very confused, it also works in a very similar setup (https://code.launchpad.net/~mvo/+snap/fontconfig-multi-cache) where it works15:39
mvokyrofa: slightly desperate as it blocks some important work15:39
kyrofaYeah I think I know what work that is :)15:41
niemeyerhttps://bugs.launchpad.net/snapcraft/+bug/1804258 https://bugs.launchpad.net/snapcraft/+bug/180425615:42
niemeyermup: Are you okay?15:42
niemeyerHmm.. freenode seems to be still blocking15:43
kyrofamvo, can I see a LP log of the failure?15:43
niemeyermup: Now?15:43
niemeyermup: Now?15:43
mupniemeyer: I really wish I understood what you're trying to do.15:43
niemeyerYeah.. :/15:43
niemeyerNeed to improve mup to identify itself automatically to nickserv15:44
mvokyrofa: https://travis-ci.org/snapcore/core/builds/457417770?utm_source=github_status&utm_medium=notification15:44
mvokyrofa: and https://github.com/snapcore/core/blob/master/.travis.yml is the build script15:45
mvokyrofa: maybe some outdated version of snapcraft or something?15:46
kyrofamvo, https://github.com/snapcore/core/blob/master/.travis.yml#L2215:46
kyrofaDo you intend to copy the fc dir there?15:47
mvokyrofa: !!!15:47
mvokyrofa: it looks like this script needs some serious love15:47
mvokyrofa: thats exactly it, thank you so much15:47
kyrofaHaha, no problem15:47
kyrofamvo, that error is a bit misleading, please do log a bug when able15:48
* cachio lunch15:50
zygamborzecki: re15:56
zygamborzecki: trying15:56
zygamborzecki: does it brick the system? :)15:56
zygamborzecki: running on 16.0416:00
zygamborzecki: no luck yet16:01
zygaI can add more cores16:01
zyga(or less cores, need to check what's the key)16:01
zygacurrently running with 4 cores16:01
zygamborzecki: no luck, restored snapshot16:02
zygagoing to 1 core16:03
zygamborzecki: I got "3: disk-16 missing"16:06
cachiomvo, no 2.35.5 on proposed/bionic16:09
cachiomvo, is it agreed?16:10
zygamborzecki: running for a longer while I see more "disk missing" errors16:12
mborzeckizyga: try 18.10 or fedora or arch16:45
zygamborzecki: I'll jump into this tomorrow, I'm deep in something else now16:46
zygamborzecki: but it failed on 16.04 too16:46
zygawhen I went to one core it was failing faster16:46
mborzeckizyga: takes one run to reproduce on 18.10 :)16:49
zygamborzecki: good16:52
zygamborzecki: I think it's not systemd16:52
zygaI can show you where the lock is missing16:52
zygabut we can hack that tomorrow16:52
zygaI _suspect_ it's a security bug16:52
zygaso either fix quickly or be considerate16:52
mupPR snapd#6177 opened: interfaces: draft of LimeSDR hotplug interface <Hotplug 🔌> <⛔ Blocked> <Created by stolowski> <https://github.com/snapcore/snapd/pull/6177>17:05
roadmrhi jdstrand ! hey is it possible to make a plug in one snap automagically connect to another snap's slot? I know the IDs of both snaps.17:19
=== pstolowski is now known as pstolowski|afk
mupBug #1804281 opened: Cannot refresh snaps if home is in NFS with root_squash <Snappy:New> <https://launchpad.net/bugs/1804281>18:01
niemeyerjdstrand: Thanks for the approvals18:04
niemeyerjdstrand: Looking into it now.. I might have a new revision soon18:05
Chipacadpkg-shlibdeps: error: no dependency information found for /lib/x86_64-linux-gnu/libpthread.so.0 (used by debian/snapd/usr/lib/snapd/snap-failure)18:13
ChipacaWAT18:13
* cachio afk19:02
mvokyrofa: https://bugs.launchpad.net/snapcraft/+bug/1763394 is a bug about this, I will amend it19:17
mupBug #1763394: cleanbuild gets confused with directory source type <Snapcraft:Triaged by sergiusens> <https://launchpad.net/bugs/1763394>19:17
jdstrandpstolowski|afk: fyi, I saw and am still digesting your hotplug/autoconnect forum post19:50
mwhudsonis there a snapd api i can hit to answer the question "will snap refresh --channel=$foo $bar do anything"?20:37
mwhudsonthere's /v2/find?select=refresh but that won't be correct if the snap is not tracking $foo already20:38
mwhudsonanother question!20:38
mwhudsonif a snap revision is in two channels $foo and $bar and currently tracking $foo, will snap refresh --channel=$bar restart services from the snap?20:39
mwhudsoni guess not20:39
=== kali_ is now known as kaliy
Chipacamwhudson: o/22:19
Chipacamwhudson: no there isn't a "dry run"22:19
Chipacamwhudson: there is 'snap refresh --list' which is something almost completely but not entirely different22:20
Chipacawhy is there a --list and not a --dry-run?22:20
Chipacaprobably "we r dum"22:20
Chipacabut also probably hysterical reasons22:20
Chipacaanyhow, came here to close the window because dmesg is spamming me about nvidia dropping off the bus and every character takes 2 seconds to appear22:21
Chipacathat was fun to write22:21
Chipacabbiab reboot22:21

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