[06:37] <cjwatson> mwhudson: https://paste.ubuntu.com/p/p5pb5RMbNZ/
[06:37] <cjwatson> missing .st_mode in some places I imagine
[07:52] <mwhudson> cjwatson: yes
[07:53] <mwhudson> waiting until i get out of meetings :)
[09:22] <cyphermox> @pilot in
[09:37] <seb128> bdmurray, do you have any idea why opening a bug from e.u.c  (https://errors.ubuntu.com/problem/b7bbe8793010d7f757f3de7861f6c9584a1fe623) is giving a "qastaging.launchpad.net" url?
[09:40] <mwhudson> cjwatson, slangasek: https://code.launchpad.net/~mwhudson/merge-o-matic/oops/+merge/355485
[09:43] <cjwatson> mwhudson: +1
[09:43]  * mwhudson belatedly notices that i can actually push to trunk
[09:44] <mwhudson> bdmurray: can you update the mom branch on shedu pls?
[09:45] <mwhudson> cjwatson: unless you can do that too
[09:52] <cjwatson> mwhudson: will do
[09:53] <cjwatson> mwhudson: done
[09:54] <mwhudson> cjwatson: after making my change i found the code in mom that was trying to handle permission bits already, so i have no idea (a) why that wasn't working already (b) if my change will help
[09:54] <mwhudson> but well we'll see
[09:54] <cjwatson> indeed
[09:58] <mwhudson> oh
[09:59] <mwhudson> i don't think merge_attr was run in the conflict case
[09:59] <mwhudson> so that would be one thing
[10:13] <xnox> mwhudson, https://launchpadlibrarian.net/389094029/buildlog_ubuntu-cosmic-amd64.gocryptfs_1.4.3-6_BUILDING.txt.gz
[10:14] <xnox> mwhudson, is this the error?!
[10:14] <xnox> # github.com/jacobsa/crypto/cmac
[10:14] <xnox> src/github.com/jacobsa/crypto/cmac/hash.go:97:3: undefined: xorBlock
[10:40] <Unit193> https://packages.qa.debian.org/g/gocryptfs/news/20180915T001910Z.html might otherwise help.
[10:50] <Unit193> https://salsa.debian.org/blade/apt-cacher-ng/commit/e9f49ca951599c09f23973fc0d294b0c0e78d59a miiight be handy for Bionic users of apt-cacher-ng, though it only blocks the release upgrader, not actual updates.
[10:52] <Unit193> (Or https://salsa.debian.org/blade/apt-cacher-ng/commit/72b9fa4fb51860dc48e827572941b47b49d0ffb4 really..)
[11:04] <Kremator>  hello folks, i com here with a design question: i know canonical devs wanted to move away from sysV init system because it was serialized, that means each process could only be launched after the previous one fully started so my question is: if upstart (old ubuntu's init system) was already asynchronous why did you wanted to move to another init system?
[11:04] <Kremator> was it the fact that systemd was actively developed and maintained by redhat so it would save you workload or similar? o were the features?
[11:10] <Unit193> I'd say a big part of it was that when Debian finally moved away from sysvinit, they went with systemd.  As I'm sure you're aware, there's a lot shared with Ubuntu and Debain, so this would likely be an area that would keep diverging, adding more and more delta.
[11:12] <Kremator> Unit193, well yeah, just rechecked with other people about the dates and yeah
[11:13] <Kremator> debian jssie and ubuntu 15.04 coincide in release dates, so canonical could launch a sysd LTS a year later after testing it
[11:13] <Kremator> Unit193, btw sir, is this your webpage? https://unit193.net/xubuntu/core/
[11:13] <Unit193> Sort of, yeah.
[11:14] <Kremator> what do you mean "sort of"?
[11:15] <Kremator> btw thansk for your builds, i used to use the 17.04 of your site a lot and  upgraded it to 17.10 till had to rollback to 16.04 lts
[11:15] <Unit193> Well, I guess nothing really.  It's my site/domain.
[11:16] <Kremator> just try to keep it up online
[11:17] <Unit193> Heh, I tend to get rid of ISOs once the next release happens, though there's always torrents.
[11:17] <Kremator> not about that, but back when i used to use your builds, i remember your site going offline everyonce in a while :P
[11:39] <bdmurray> seb128: I've seen that too and its not clear to me what is going on but I'll look into it.
[11:39] <seb128> bdmurray, thx
[11:39] <bdmurray> seb128: the bugs do get opened on launchpad.net though
[11:39] <seb128> right, I ended up at the right place, it's just confusing
[11:48] <seb128> bdmurray, it seems to do it for any new bug until you refresh the page then it's fine
[11:49] <bdmurray> seb128: Its not terrible but still curious
[11:49] <seb128> right
[12:16] <bdmurray> seb128: Have you seen bug 1743216?
[12:17] <seb128> bdmurray, yes, it's a weird one, I had a look but it's nothing obvious
[12:17] <seb128> Laney, you wouldn't have a clue about this one would you?
[12:18] <bdmurray> It looked like something in xdg-screensaver to me
[12:19] <Laney> nope
[12:19] <Laney> dunno what that is
[12:19] <Laney> rls tagging would be the right route to get it considered to be looked at by our team imho (rather than assigning it)
[12:20] <bdmurray> Laney: okay, noted
[12:20] <sarnold> https://codesearch.debian.net/search?q=named_window_id
[12:20] <Laney> thanks
[12:20] <Laney> (sarnold should feel free to fix it :-))
[12:21] <sarnold> :D
[12:29] <doko> coreycb, mwhudson: http://people.canonical.com/~ubuntu-archive/transitions/html/python3.7-only.html
[12:32] <mwhudson> coreycb: http://people.canonical.com/~ubuntu-archive/transitions/html/python3.7-add.html
[12:32] <mwhudson> coreycb: https://docs.google.com/document/d/1sdXd-IklDzdta6KvIhoqiOJP6OdILjPE7b_mrGqKwHQ/edit#