[00:21] <mup> PR snapd#7427 opened: tests/overlord/snapstate: refactor for cleaner test failures <Simple 😃> <Created by anonymouse64> <https://github.com/snapcore/snapd/pull/7427>
[00:28] <mup> PR snapd#7428 opened: systemd, wrappers/services: add helpers for disabling multiple services in a snap <Created by anonymouse64> <https://github.com/snapcore/snapd/pull/7428>
[00:29] <mup> PR snapd#7429 opened: wrappers/services: add CurrentSnapServiceStates + unit tests <Created by anonymouse64> <https://github.com/snapcore/snapd/pull/7429>
[00:43] <mup> PR snapd#7430 opened: [RFC] overlord/snapstate: set snap-setup-task for first task in change <Created by anonymouse64> <https://github.com/snapcore/snapd/pull/7430>
[00:53] <mup> PR snapd#7431 opened: overlord/snapstate: don't re-enable and start disabled services on refresh, etc <Created by anonymouse64> <https://github.com/snapcore/snapd/pull/7431>
[05:18] <mborzecki> morning
[06:18] <mborzecki> mvo: morning
[06:40] <mup> PR snapd#7427 closed: tests/overlord/snapstate: refactor for cleaner test failures <Simple 😃> <Created by anonymouse64> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/7427>
[07:00] <pstolowski> morning
[07:07] <mvo> hey pstolowski
[07:12] <mborzecki> pstolowski: hey
[07:16] <mborzecki> nice, thunderstorm at 9am :/
[07:20] <pstolowski> mhm. quiet here but very cloudy and raining
[07:21] <mborzecki> pstolowski: it's finished now
[07:21] <mborzecki> pstolowski: < 10 minutes total, heh
[07:28] <zyga> hey
[07:28] <zyga> oh boy
[07:28] <zyga> I was in #snapcraft
[07:28] <zyga> complaining that there is nobody there
[07:29] <zyga> and it's a quiet day :D
[07:29] <zyga> how are you guys?
[07:29] <zyga> mborzecki, pstolowski: really? it's sunny and almost 20 here
[07:29] <mvo> zyga: hey, good morning. good, good, but it sounds like you need a cup of coffee :)
[07:29] <zyga> mvo: haha :)
[07:29] <zyga> I guess so
[07:29] <zyga> I'm reviewing channels PR
[07:29] <zyga> mvo: I was on a bike ride already, should be more awake
[07:32] <mborzecki> zyga: the front is moving NW, so enjoy your weather
[07:32] <mborzecki> zyga: about that, this is what poland looked like on 03.09 https://www.wykop.pl/cdn/c3201142/comment_I9dTRiDkK6k1pkTXd1VyOL7XMeNwQ8PD.jpg
[07:33] <zyga> mborzecki: looks like cake
[07:34] <mborzecki> zyga: mhm, the bottom screen capture is from Lodz afaik
[07:35] <zyga> mborzecki: polska A i polska B ;-)
[07:39] <zyga> I should make that coffee
[07:40] <zyga> it was surprising because mvo didn't join #snapcraft
[07:40] <zyga> but was doing reviews
[07:40] <zyga> so I was thinking there's an IRC split
[07:53] <mborzecki> zyga: conflicts in https://github.com/snapcore/snapd/pull/7421
[07:53] <mup> PR #7421: cmd/snap-confine: unmount /writable from snap view <Created by zyga> <https://github.com/snapcore/snapd/pull/7421>
[07:59] <ackk> zyga, hi, do you know why doing something https://github.com/maas/maas/blob/master/Makefile#L770-L784 would break a try'd snap?
[08:00] <ackk> zyga,  I ran that and now I get
[08:00] <ackk> $ maas
[08:00] <ackk> execv failed: No such file or directory
[08:20] <Chipaca> ackk: are you running the maas binary you think you are running?
[08:25] <mvo> Chipaca: do you think you could have a look at https://github.com/snapcore/spread/pull/69 ? should be easy but I want it to be as good as possible before giving it to Gustavo
[08:25] <mup> PR spread#69: Manage pagination retrieving images from google backend <Created by sergiocazzolato> <https://github.com/snapcore/spread/pull/69>
[08:25] <Chipaca> mvo: I do think I could
[08:25] <mvo> Chipaca: thank you!
[08:26] <mvo> Chipaca: (I hope this means you will actually do it and not just think about it ;) I guess I phrased my question a bit too vague)
[08:26] <Chipaca> :-p
[08:26] <Chipaca> maybe it was just the right amount of vague
[08:27] <mvo> heh
[08:33] <zyga> Trevinho: hello
[08:33] <zyga> Trevinho: I got a note that you experienced an interesting failure on your system last week
[08:44] <zyga> mborzecki: hey
[08:44] <zyga> I noticed yo talked to Trevinho last week
[08:44] <mborzecki> zyga: hm?
[08:44] <zyga> quick question:
[08:44] <zyga> the "mount core" task failed
[08:44] <zyga> the log has
[08:44] <zyga> Mount snap "core" (7396)
[08:44] <zyga> 2019-09-05T20:09:11+02:00 ERROR remove /snap/core/7396: device or resource busy
[08:44] <zyga> does this seem to imply to you that succeeded on the DO path
[08:44] <zyga> something later failed
[08:44] <zyga> and then we went to UNDO
[08:45] <zyga> and this is when this failed?
[08:45] <mborzecki> zyga: i think Trevinho posted snap change for that refresh, and indeed it was undoing something
[08:45] <mborzecki> zyga: let me check my history
[08:46] <zyga> Hold    today at 17:13 CEST  today at 20:08 CEST  Remove snap "core" (7169) from the system
[08:46] <zyga> this is what seems to have failed
[08:46] <zyga> and then we got the other error
[08:46] <zyga> because the new core was already used by something else
[08:46] <zyga> or by some scanning utility that held open file descriptors to core
[08:47] <zyga> so the question is: do you think that it was the undo path that failed?
[08:50] <mborzecki> zyga: this is the snap change output https://pastebin.ubuntu.com/p/Yhy3hxGG8b/
[08:55] <zyga> mborzecki: yes, I have that
[08:57] <mborzecki> zyga: hard to tell from the log, but i think the problem was 2019-09-05T19:38:54+02:00 ERROR cannot remove snap file "core", will retry in 3 mins: remove /snap/core/7169: device or resource busy
[08:57] <mborzecki> zyga:  then it went with undo
[08:57] <mborzecki> zyga:  and then errored out in undo of setup-snap, which got logged with default case handler in taskrunner
[08:57] <zyga> mmm
[08:57] <zyga> mhm
[09:22] <zyga> mborzecki: I've made a patch for that
[09:25] <ackk> Chipaca, wdym? I get the same error by running /snap/bin/maas, if that's what you mean
[09:25] <Chipaca> ackk: ah, good. Ok. What happens if you 'snap run --trace maas'?
[09:25] <Chipaca> strace*
[09:26] <ackk> $ snap run --strace maas
[09:26] <ackk> error: exit status 1
[09:26] <ackk> Chipaca, ^
[09:26] <mup> PR snapd#7432 opened: boot,dirs,image: introduce boot.MakeBootable, use it in image instead of ad hoc code <Created by pedronis> <https://github.com/snapcore/snapd/pull/7432>
[09:32] <ackk> Chipaca, fwiw the same happens with the maas service, it fails to start with "file not found"
[09:33] <zyga> mborzecki, mvo: https://github.com/snapcore/snapd/pull/7433
[09:33] <mup> PR #7433: systemd: detach rather than unmount .mount units <Bug> <Created by zyga> <https://github.com/snapcore/snapd/pull/7433>
[09:33] <mup> PR snapd#7433 opened: systemd: detach rather than unmount .mount units <Bug> <Created by zyga> <https://github.com/snapcore/snapd/pull/7433>
[09:33] <Chipaca> ackk: what does snap pack --check-skeleton of the prime directory say, if anything?
[09:33] <Chipaca> i think 'snap try' already does that but just in case
[09:38] <ackk> Chipaca, nothing
[09:38] <Chipaca> ackk: if that check passes, that means the binary itself that the app points to exists. As that's probably a shell wrapper, look at it and see what it calls
[09:38] <Chipaca> ackk: or
[09:38] <Chipaca> ackk: tell you what, if it is a wrapper, add "set -x" to the top of it :-)
[09:39] <Chipaca> ackk: and see which command it is that fails
[09:39] <ackk> Chipaca, execv failed: No such file or directory
[09:39] <pedronis> Chipaca: hi, could you review #7425, #7411 and #7197 (they are already marked for you, there's a couple more but they either need more work or are descendant from those)
[09:39] <ackk> Chipaca, I put a -x on the snapcraft wrapper
[09:39] <mup> PR #7425: channel: introduce Resolve and ResolveLocked <Created by pedronis> <https://github.com/snapcore/snapd/pull/7425>
[09:39] <mup> PR #7411: cmd/model: output tweaks, add'l tests <Created by anonymouse64> <https://github.com/snapcore/snapd/pull/7411>
[09:39] <mup> PR #7197: usersession: track connections to session agent for exit on idle and peer credential checks <Created by jhenstridge> <https://github.com/snapcore/snapd/pull/7197>
[09:39] <ackk> but it's not even run
[09:40] <Chipaca> pedronis: will do
[09:40] <Chipaca> pedronis: thanks
[09:40] <Chipaca> ackk: how can i reproduce this?
[09:47] <ackk> Chipaca, I guess by fetching the maas code, building the snap and using snap try
[09:47] <Chipaca> ackk: if you pack the snap, does it still break in this way?
[09:47] <ackk> Chipaca, I've run into this a lot of times in the past, recently thought it got fixed since I wasn't seeing it anymore
[09:47] <ackk> Chipaca, well if I remove and reinstall it even with try it gets fixed
[09:48] <ackk> Chipaca, it's not a snap filesystem issue for sure
[09:48] <ackk> Chipaca, if it matters I'm running it in a container, with bind-mounted home
[09:48] <ackk> Chipaca, so I can't really try a packed snap, because of the snapfuse issue...
[09:48] <Chipaca> ackk: what happens if you disable and then enable the maas snap?
[09:51] <ackk> Chipaca, starts working again it seems
[09:51] <Chipaca> ackk: does maas use layouts or content?
[09:51] <ackk> Chipaca, no
[09:51] <Chipaca> content interface*
[09:52] <Chipaca> ackk: it looks like the rsync somehow breaks the mount but not sure how
[09:52] <Chipaca> ackk: unless …
[09:53] <Chipaca> ackk: as well as doing that series of rsyncs you linked to, do you also somehow re-create the 'prime' directory?
[09:53] <ackk> Chipaca, no, just that rsync
[09:53] <Chipaca> hm
[09:53] <ackk> I run 'make sync-dev-snap' and that's it
[09:53] <ackk> (and snap restart maas)
[09:55] <Chipaca> ackk: would be interesting to look at 'findmnt' (maybe 'findmnt -D') for when it works vs when it doesn't
[09:56] <ackk> Chipaca, ok, lemme see if it happens again
[09:56] <ackk> I have the one when it works
[09:59] <ackk> Chipaca, of course now I ran sync like 30 times and it doesn't happen ;/
[09:59] <Chipaca> :-)
[10:03]  * Chipaca takes a break
[10:03] <pstolowski> ogra: hey, any thoughts on https://bugs.launchpad.net/snapd/+bug/1843077 ? not sure it belongs to snapd, probably somewhere else (core?)
[10:03] <mup> Bug #1843077: Data corruption when UC is not powered down cleanly  <snapd:New> <https://launchpad.net/bugs/1843077>
[10:15] <mvo> zyga: oh, nice one!
[10:24] <mborzecki> zyga: updated #7419
[10:24] <mup> PR #7419: cmd/snap-confine: add unit tests for sc_invocation, cleanup memory leaks in tests <Created by bboozzoo> <https://github.com/snapcore/snapd/pull/7419>
[10:24] <mborzecki> pstolowski:  can you take a look at that PR too? ^^
[10:28] <ogra> pstolowski, the bug is way to vague ... "doesnt boot" ... :P ... (what did cause it exactly ... whats the actual error they see then etc etc) ... you can indeed tune some settings like having dirty pages flushed more often to disk and such but thats typically coming at a cost for other (generic) use-cases ... and it also only minimizes the risk. i'm not sure there is much that can be done about the journal
[10:28] <ogra> oh ... and on a sidenote ... i'm officially on vacation (til 23rd) ;)
[10:29] <ogra> (and "other filesystems" is a foundations question ;) )
[10:31] <ogra> i only do run two flash based boards over here ... (the others from SD) ... neither of them has ever shown such a behaviour
[10:31] <ogra> (hmm ... both on core 16 though ... thats perhaps a datapoint)
[10:35] <pstolowski> mborzecki: i'll
[10:36] <mborzecki> pstolowski: thx!
[10:36] <pstolowski> ogra: i see, thanks, and sorry for disturbing! enjoy your vacation!
[10:38] <zyga> mborzecki: looking
[10:39] <ogra> pstolowski, i wouldnt need to answer, all fine you didnt disturb  ;)
[10:44] <mvo> a second review for 7432 would be great, should be super straightforward
[10:48]  * pstolowski lucnh
[10:48]  * pstolowski lunch
[11:16]  * zyga debugs something
[11:16] <zyga> mvo: sorry for not doing more reviews :/
[11:18] <mvo> zyga: no worries
[11:31] <mup> PR snapd#7426 closed: cmd/snap-update-ns: clarify sharing comment <Simple 😃> <Created by zyga> <Merged by zyga> <https://github.com/snapcore/snapd/pull/7426>
[11:32] <mup> PR snapd#7434 opened: seed/seedwriter:  implement WriteMeta and tree16 corresponding code <Created by pedronis> <https://github.com/snapcore/snapd/pull/7434>
[11:40] <Chipaca> pedronis: in #7425, why 'locked' instead of 'pinned'? seems confusing
[11:40] <mup> PR #7425: channel: introduce Resolve and ResolveLocked <Created by pedronis> <https://github.com/snapcore/snapd/pull/7425>
[11:41] <pedronis> Chipaca: because in Toronto we discussed we don't want to use pinned, I'm exploring other options
[11:41] <pedronis> we'll have some clarity hopefully in Paris
[11:41] <Chipaca> I thought it was going to be like progress.NewTaskProgressAdapterLocked
[11:42] <Chipaca> it's the toronto water, it clogs the brain
[11:59] <cmatsuoka> mborzecki: I patched snap-image to work with recovery, but there was an inconsistency in the way the utility was handling file copying so I had to change it a little bit
[12:00] <mborzecki> cmatsuoka: cool, are the changes in your branch?
[12:00] <cmatsuoka> mborzecki: not yet, still working on that
[12:01] <mborzecki> cmatsuoka: ok, ping me when you push it, i'll take a look, perpahs somethins that could be fix in the RFC PR
[12:01] <cmatsuoka> mborzecki: the main problem was related to how file organization is always used (source/target with different paths)
[12:02] <cmatsuoka> mborzecki: I couldn't use the standard Write() methods to get files from the gadget to the prepared area, and then from prepared to the final image, because it would want to organize files twice
[12:03] <cmatsuoka> mborzecki: and I also can't copy from gadget to image and prepared area to image in two different passes, because the writer was designed to do it in a single pass
[12:04] <cmatsuoka> mborzecki: so I added an extra parameter to Write() to tell if file organization is to be used or not
[12:05] <mborzecki> cmatsuoka: so you used Write() to some staging location and then Write() again from the staging to actual destination?
[12:05] <pstolowski> re
[12:06] <cmatsuoka> mborzecki: I tried numerous approaches and that seemed to be the one that didn't require major rewrites, but if you have any better idea I'll gladly accept it
[12:08] <cmatsuoka> mborzecki: my first attempt was to copy from gadget to image in addition to the regular copy, but the writer wants to create the image from staging in a single pass
[12:13] <pedronis> cmatsuoka: what is the prepared area, why do you need two places/copies?
[12:13] <pedronis> is actually not super clear
[12:31] <cmatsuoka> pedronis: the "prepared area" is the directory written by snap prepare-image. snap image get bits from there, and bits directly from the gadget
[12:32] <cmatsuoka> pedronis: however, ubuntu-seed needs data from both at the same time (recovery from prepare-image, bootloader from gadget)
[12:32] <cmatsuoka> pedronis: because prepare-image doesn't add content files
[12:33] <mborzecki> cachio: https://paste.ubuntu.com/p/3pJzxxVT45/ so far we assumed it's only on arch?
[12:34] <cachio> mborzecki, yes
[12:34] <pedronis> cmatsuoka:  but we are not going to call prepare-image at runtime
[12:34] <cmatsuoka> pedronis: yes, but that's for the initial image generation
[12:34] <cachio> mborzecki, all the failures which I saw were on arch
[12:35] <pedronis> cmatsuoka: there is no strict reason btw not to move things from prepare-image to just snap-image if it makes sense
[12:36] <pedronis> cmatsuoka: also I just encapsulated the relevant code I think, the one that does gadget bits in prepare-image
[12:36] <pedronis> cmatsuoka: you should probably read https://github.com/snapcore/snapd/pull/7432
[12:36] <mup> PR #7432: boot,dirs,image: introduce boot.MakeBootable, use it in image instead of ad hoc code <Created by pedronis> <https://github.com/snapcore/snapd/pull/7432>
[12:36] <cmatsuoka> pedronis: I'll check that, thanks
[12:37] <pedronis> cmatsuoka: to be clear, we haven't yet exactly decided what prepare-image/ubuntu-image do for core 20 images
[12:38] <pedronis> if doing less or doing more is more convenient we ca tweak/decide
[12:41] <cmatsuoka> pedronis: yes, the snap-image investigation made me understand the issues there to see what kind of tweaks could be useful
[12:42] <mup> PR snapd#7435 opened: tests: explicitly restore after using LXD <Test Robustness> <Created by zyga> <https://github.com/snapcore/snapd/pull/7435>
[12:42] <ijohnson> good morning y'all
[12:43] <zyga> hey ijohnson :)
[12:43] <ijohnson> hey zyga o/
[12:47] <zyga> WAT? https://www.irccloud.com/pastebin/rRkpecF0/
[12:49] <ijohnson> pedronis: so from your comment, is #7428 unnecessary then? should I close that PR or might it still be useful to have those methods for a different use case
[12:50] <mup> PR #7428: systemd, wrappers/services: add helpers for disabling multiple services in a snap <Created by anonymouse64> <https://github.com/snapcore/snapd/pull/7428>
[12:52] <pedronis> ijohnson: we tend not to add unused helpers, it code base is big/sometimes confusing enough :)
[12:52] <pedronis> s/it code/the code/
[12:52] <ijohnson> ack, I'll close the PR then
[12:55] <mup> PR snapd#7428 closed: systemd, wrappers/services: add helpers for disabling multiple services in a snap <Created by anonymouse64> <Closed by anonymouse64> <https://github.com/snapcore/snapd/pull/7428>
[13:01] <zyga> ah, my bad
[13:01] <zyga> local bug
[13:19] <mup> PR snapd#7436 opened: many: make per-snap mount namespace MS_SHARED <Created by zyga> <https://github.com/snapcore/snapd/pull/7436>
[13:37] <mup> PR snapcraft#2702 closed: Release changelog for 3.8 <Created by sergiusens> <Merged by sergiusens> <https://github.com/snapcore/snapcraft/pull/2702>
[13:45]  * zyga wants to go for lunch, ttyl
[14:11] <mborzecki> pstolowski: noticed a little bug with unset, it's possible to unset an option that is not supported by core/system and otherwise would raise an error when tried with snap set
[14:12] <pstolowski> mborzecki: uh, nice catch, thank you! will fix
[14:15] <mup> PR snapd#7395 closed: cmd/snap-confine: apply global mount namespace initialization for confined and classic snaps <Created by bboozzoo> <Closed by bboozzoo> <https://github.com/snapcore/snapd/pull/7395>
[14:23] <mborzecki> wow, some heavy rain here
[14:30] <mup> PR snapd#7432 closed: boot,dirs,image: introduce boot.MakeBootable, use it in image instead of ad hoc code <Created by pedronis> <Merged by pedronis> <https://github.com/snapcore/snapd/pull/7432>
[14:31] <mup> PR snapd#7419 closed: cmd/snap-confine: add unit tests for sc_invocation, cleanup memory leaks in tests <Created by bboozzoo> <Merged by bboozzoo> <https://github.com/snapcore/snapd/pull/7419>
[14:35] <ijohnson> grr regex... am I missing something obvious here? https://pastebin.ubuntu.com/p/rFh2SzQG4z/
[14:36] <ijohnson> I have a feeling this has something to do with gocheck automatically adding the end of the line marker to the regex in ErrorMatches
[14:37] <mvo> ijohnson: does it help if you prefix the regexp with ".* "?
[14:38] <pstolowski> ijohnson: yep, this, and possibly .* at the end. you also have ] there, needs escaping
[14:38] <ijohnson> ah actually it does if I add .* to the start and then \n.* at the end too
[14:38] <ijohnson> went with
[14:38] <ijohnson> 	c.Assert(err, ErrorMatches, ".*is-enabled snap.hello-snap.svc1.service] failed with exit status 1: whoops\n.*")
[14:39] <ijohnson> pstolowski: I thought I would have to escape ] but it didn't seem to be necessary for some reason
[14:40] <mvo> second look at https://github.com/snapcore/spread/pull/69 would be great, hopefully good now
[14:40] <mup> PR spread#69: Manage pagination retrieving images from google backend <Created by sergiocazzolato> <https://github.com/snapcore/spread/pull/69>
[14:47] <pstolowski> ijohnson: interesting, maybe it's smart enough if opening [ is missing; some regex implementations would probably freak out
[14:47] <ijohnson> yeah true, do you think I should escape it anyways in case go ever changes behavior? seems unlikely I guess
[14:48] <pstolowski> ijohnson: i'd escape it just to avoid confusion / make it clear
[14:48] <ijohnson> ack
[14:48] <Trevinho> zyga: hey, hello... I saw mborzecki said wrote a patch, is that enough or do you need some more debugging data?
[14:49] <Trevinho> fyi I'm still affected, so... I can test new versions and/or provide more debugging
[14:49] <Trevinho> I suppose I still won't reboot for a while... Too much precious stuff in my /tmp xD
[15:11] <zyga> Trevinho: hey, I think one thing might be useful
[15:11] <zyga> Trevinho: please install lsof and run lsof on the paths that failed
[15:11] <zyga> Trevinho: like /snap/core/1234 (fix the number)
[15:11] <zyga> Trevinho: lastly, please report a bug,  this will aid in our tracking and allow us to store such logs easily
[15:11] <zyga> Trevinho: if you don't want to just say so and I'll report it
[15:13] <Trevinho> zyga: ok, as per lsof, there's nothing coming for the new version of the core
[15:13] <zyga> and the old one?
[15:14] <Trevinho> zyga: https://pastebin.ubuntu.com/p/jdbv6dRS79/
[15:14] <zyga> Trevinho: is core rev 7270 the one that failed to be removed?
[15:14] <Trevinho> yep
[15:15] <Trevinho> my current one
[15:27] <zyga> Trevinho: understood, thank you
[15:36] <zyga> Trevinho: let me know about that bug number if you have one
[15:41] <Trevinho> zyga: I also now tried to close all the app using current snap and it still failed, but without hanging at least...
[15:41] <Trevinho> https://pastebin.ubuntu.com/p/9H3w9bSgMZ/
[15:41] <Trevinho> so I suppose that in such case core should not block if removal of an old version failed
[15:42] <Trevinho> I mean, is that a fatal error? :o
[15:42] <zyga> Trevinho: what does lsof say now>?
[15:42] <Trevinho> nothing
[15:42] <zyga> lsof isn't perfect though, we'll see
[15:42] <Trevinho> as it wasn't saying anything of the failed-to-remove version before
[15:42] <Trevinho> yeah, that's the problem
[15:42] <mup> PR snapd#7437 opened:  wrappers/services.go: add disabled svc list arg to AddSnapServices <Created by anonymouse64> <https://github.com/snapcore/snapd/pull/7437>
[15:43] <Trevinho> zyga: I forgot, what's the command to get debug info from a change?
[15:43] <zyga> snap changes
[15:43] <zyga> snap change NNN or snap tasks NNN
[15:44]  * cachio lunch
[15:51] <mup> Bug #1843286 opened: Snap failing to remove old core doesn't update and keeps spinnig the CPU <Snappy:New> <https://launchpad.net/bugs/1843286>
[15:51] <Trevinho> zyga: https://bugs.launchpad.net/snappy/+bug/1843286
[15:51] <mup> Bug #1843286: Snap failing to remove old core doesn't update and keeps spinnig the CPU <Snappy:New> <https://launchpad.net/bugs/1843286>
[15:51] <zyga> Trevinho: thank you very much
[15:54] <zyga> I have the most of lack of luck recently
[15:58] <mup> PR snapcraft#2707 opened: manifest: sort package and snap lists for consistency <Created by cjp256> <https://github.com/snapcore/snapcraft/pull/2707>
[16:34] <mup> PR snapd#7433 closed: systemd: detach rather than unmount .mount units <Bug> <Created by zyga> <Merged by zyga> <https://github.com/snapcore/snapd/pull/7433>
[17:05]  * zyga EODs
[17:29] <rogpeppe> zyga: do you know how i might find out why my ubuntu-core-running raspberry pi is crashing? i'm now running on a not-much-used pi 3 and it's crashing regularly about twice a day (hard crash - it doesn't auto-reboot)
[17:30] <zyga> rogpeppe: enable persistent journal and look at the logs there; look at the serial output for hints
[17:30] <zyga> no other ideas from the top of my head
[18:35] <rogpeppe> zyga: thanks. looks like i can enable persistent journal with `mkdir /var/log/journal`. does that seem right to you?
[18:36] <zyga> yes
[18:36] <rogpeppe> zyga: sadly i can't look at serial output. i'm 500 miles away from the actual device now...
[18:37] <rogpeppe> zyga: i've now enabled persistant journal; hopefully i might see something after the next crash.
[18:37] <rogpeppe> zyga: BTW the other odd thing is that it only boots up about 50% of the time.
[18:39] <rogpeppe> zyga: BTW thanks a lot for your interaction on this issue. it's really nice to have some feedback.
[18:40] <zyga> I'm really happy to help
[18:40] <zyga> it's hard to help everyone that comes around
[18:40] <zyga> but it's also genuinely interesting to see what is the cause of this problem
[19:20]  * ijohnson relocates
[20:22] <ec0> hi there, observing something interesting with the organize keyword, and wanted to run it by someone. When using this keyword on a part using the 'python' plugin it doesn't seem to do anything? Is this expected behaviour?
[20:34] <mup> PR snapd#7407 closed: tests: run failing tests on ubuntu eoan due to is now set as unstable <Created by sergiocazzolato> <Merged by sergiocazzolato> <https://github.com/snapcore/snapd/pull/7407>
[20:48] <rogpeppe> zyga: FWIW i was ssh'd into the system when i saw this broadcast message:
[20:48] <rogpeppe> reboot scheduled to update the system
[20:48] <rogpeppe> The system is going down for reboot at Mon 2019-09-09 19:36:00 UTC!
[20:49] <rogpeppe> zyga: so perhaps it's not crashing after all, but just automatically rebooting and shutting down and not restarting
[20:49] <rogpeppe> zyga: why would it be rebooting automatically to update the system?
[20:50] <rogpeppe> zyga: that certainly might explain why the system is going down so regularly!
[23:23] <mup> PR snapcraft#2708 opened: tools: make environment-setup container name and image configurable <Created by cjp256> <https://github.com/snapcore/snapcraft/pull/2708>


[13:02] <abraCadaver> mind if I make a suggestion?
[13:03] <abraCadaver> just going to come out with it... :) new to the community, not really sure what the feel is here yet, but I've noticed something
[13:03] <abraCadaver> recently started using ubuntu and I started trying to get my friends to use it and nobody wants to, didn't want to myself until I thought it would make a great os for my old laptop / desktop, etc
[13:04] <abraCadaver> when I mentioned "linux loves old hardware", suddenly everybody got interested
[13:04] <abraCadaver> from 0 people to four people in one comment
[13:05] <abraCadaver> Every dev has an old laptop or desktop laying in a corner somewhere collecting dust that they don't want to throw out even though they don't use it
[13:05] <abraCadaver> I'm wondering if this idea might be a good thing to bring front and center?