[03:21] <Bluefoxicy> wait, what
[03:21] <Bluefoxicy> there are no text terminals
[03:21] <Bluefoxicy> ctrl+alt+F1-F6 just shows the line "Scanning for Btrfs filesystems"
[05:51] <pitti> Good morning
[05:52] <tsimonq2> o/ pitti, how are you? :)
[05:55] <pitti> hey tsimonq2! a bit tired, but ok, how about you?
[05:59] <tsimonq2> great pitti :)
[06:00] <tsimonq2> pitti: quick question, are you a Core Dev?
[06:00] <pitti> yes
[06:01] <tsimonq2> pitti: you on the release team?
[06:01] <pitti> https://launchpad.net/~pitti/+participation :)
[06:02] <tsimonq2> oh sorry
[06:03] <tsimonq2> yeah nevermind
[06:45] <pitti> didrocks: bonjour !
[06:46] <pitti> didrocks: do you know about the ubuntu-make test regressions? (http://autopkgtest.ubuntu.com/packages/u/ubuntu-make/yakkety/amd64/) -- it seems to complain about "debian/tests/collect-coverage: line 8: cd: /tmp/global-coverage: No such file or directory"
[06:46] <pitti> oh, and "Couldn't find static file 'jquery.ba-throttle-debounce.min.js'" in the "small" test
[06:47] <pitti> the one above might just be a consequence of that
[06:48] <didrocks> hey pitti! this error happen when no tests have been running.
[06:48] <didrocks> maybe one build-dep breaking the coverage report?
[06:48] <pitti> didrocks: right, so I guess the missing jquery.ba-throttle-debounce.min.js causes the failure?
[06:49] <didrocks> probably yeah (same, this is on the coverage report side)
[06:50] <cpaelzer> late but good morning everybody
[08:48] <pitti> juliank: hm, didn't we use to have something like $APTROOT?
[08:49] <pitti> juliank: i. e. if I have my little sandbox with foo/etc/apt/sources.list and foo/var/lib/apt/lists etc.
[08:49] <pitti> juliank: (working on the archive auth -- I'd rather install the GPG key properly than [trusted=yes]
[08:50] <pitti> the apport code uses apt.Cache(rootdir=), but that still barfs on the signature error even though trusted.gpg.d/ddebs.ubuntu.com.gpg is in place
[08:52] <pitti> oh, I think apt -o RootDir="$(pwd)" update
[09:20] <pitti> juliank: meh, I can't get this to work :( <myroot>/etc/apt/trusted.gpg.d seems to get entirely ignored, it always takes the one in the root dir
[09:28] <pitti> juliank: so at least test_install_package_from_a_ppa() is a regression in apt, the key for the PPA is definitively there; the test_install_old_packages() failure is my fault, I'll push the fix (but that's not sufficient for the same reason)
[09:35] <Saviq> pitti, morning, can you please rerun https://requests.ci-train.ubuntu.com/static/britney/ticket-1604/landing-019-yakkety/excuses.html with proposed enabled, it's fallout from the Qt 5.6.1 release
[09:35] <Saviq> (the in progress ones will fail, too)
[09:41] <pitti> juliank: filed as bug 1607283 with a standalone simple reproducer
[09:44] <juliank> pitti: Reproduced.
[09:45] <pitti> juliank: it could of course be a red herring and reading trusted.gpg.d from the sandbox may have never worked -- but apt previously didn't complain about it?
[09:45] <juliank> pitti: I'm going to bisect this
[09:45] <pitti> juliank: cheers!
[09:45] <pitti> Saviq: retried the failures and running ones
[09:46] <Saviq> pitti, thanks!
[09:56] <juliank> pitti: Can even reproduce it with 1.2.10 :/ - so it seems that's not a regression
[10:03] <pitti> juliank: hm, it works on my laptop with current yakkety
[10:03] <pitti> and apport with 1.3~exp1 doesn't fail on that
[10:07] <juliank> pitti: Well, failing is a strong word... 1.3~exp1 shouldn't find the keys, but only warns about the missing keys, and does not produce an error
[10:08] <juliank> pitti: https://paste.debian.net/785744/
[10:10] <juliank> pitti: Probably because apt-key can only look at config files, and not config values set in the parent process.
[10:12] <juliank> So, you'd have to specify dir in a apt.conf file and then set APT_CONFIG env var to that path
[10:13] <juliank> Not sure how to fix that yet
[10:14] <juliank>  We should probably dump the config to a file, set APT_CONFIG=temp-file and only then start apt-key
[10:15] <juliank> s/We/apt/
[10:27] <pitti> juliank: so apt.Cache(rootdir=foo) sets "Dir=foo" more or less?
[10:28] <juliank> It sets Dir in the current process, but that's not forwarded to the apt-key process
[10:28] <pitti> juliank: oh, you mean apt-get update calls apt-key for verifying the sig, that's not done in-process?
[10:28] <juliank> Yes
[10:29] <juliank> apt calls apt-key which calls gpgv
[10:29] <pitti> juliank: so how did that work in earlier versions, did it just silently ignore the missing key?
[10:29] <juliank> It should not ignore it silently
[10:29] <pitti> on my laptop I don't have ddebs in "apt-key list" and yet that python3 command line works fine
[10:29] <pitti> (and the apport tests)
[10:43] <Mirv> pitti: Saviq: https://requests.ci-train.ubuntu.com/static/britney/ticket-1604/landing-019-yakkety/excuses.html just updated but I don't find any running or completed results that would have been run with yakkety-proposed. I do find results that were started eg 30mins ago
[10:44] <Saviq> Mirv, pitti, yeah I was looking there too, I saw them initially with all-proposed in running queue, not sure if all the tests were restarted or just unity8... not sure where to look for recently-completed runs for PPAs
[10:45] <pitti> no, I restarted all the regressions and all teh runing ones with --all-proposed
[10:45] <pitti> seems that didn't help indeed
[10:46] <Saviq> pitti, e.g. https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-yakkety-ci-train-ppa-service-landing-019/yakkety/amd64/u/unity8/20160728_094920@/log.gz still doesn't seem to have proposed enabled so maybe we're looking at the tests that were running already?
[10:47] <Saviq> those http://autopkgtest.ubuntu.com/running.shtml#pkg-unity8 however don't have "All-proposed: True"
[10:47] <Saviq> for ppa 019
[10:47] <Mirv> Saviq: that started after your discussion, and there are similar ones 15-20mins later that also don't have proposed enabled
[10:48] <pitti> Saviq: landing-060 != landing-019
[10:48] <Saviq> pitti, there's some landing-019 further down
[10:48] <pitti> well, I did queue them with all-proposed, apparently that didn't make it to the testbed for some reason
[10:48] <juliank> pitti: RFC: https://github.com/Debian/apt/compare/master...julian-klode:bugfix/apt-key-config
[10:49] <juliank> Or rather just https://github.com/Debian/apt/commit/1bdb1e50e2b36bd5ffd14b8dbec8be1052eb1987
[10:50] <pitti> juliank: OOI, what does that new "conf" temp file do? I thought this  was just about setting $APT_CONFIG?
[10:50] <juliank> pitti: We dump the current in-process config to a temporary file, and then pass that as APT_CONFIG to apt-key
[10:51] <juliank> It's ugly, but I don't really see what else we could do
[10:51] <pitti> ah
[10:52] <pitti> Saviq, Mirv: I retried unity8/i386 again with --all-proposed (can do the others if that works)
[10:52] <pitti> oh crap, I know
[10:52] <pitti> I did -s yakkety
[10:52] <juliank> I'm not sure if it is safe
[10:52] <pitti> we want xenial I guess
[10:52] <juliank> We mkstemp() the file, but then basically ignore the fd, and re-open by name for the C++ ostream
[10:53] <pitti> no, actually, you do want y
[10:54] <juliank> I could use __gnu_cxx::stdio_filebuf() to directly use the fd
[10:54] <pitti> it's running now, I'll check in a bit
[10:54] <juliank> on the other hand, I also pass it by name to apt-key...
[10:55] <juliank> we also pass the temporary split gpg signature + data to apt-key by-name, though...
[10:55] <pitti> $ APT_CONFIG=/tmp/sandbox python3 -c 'import apt; c=apt.Cache(rootdir="/tmp/sandbox"); c.update()'
[10:55] <pitti> juliank: ^ that also doesn't work though, should it?
[10:55] <juliank> pitti: No
[10:55] <pitti> I guess that's the part of "need to actually write the config file"
[10:55] <juliank> pitti: APT_CONFIG is a config file, not a dir
[10:55] <juliank> s/is/needs/
[10:56] <juliank> I guess I also do not set cloexec on the ofstream currently :/
[10:56] <pitti> ok, so APT_CONFIG=/tmp/sandbox/etc/apt/apt.conf also doesn't work as I suppose that doesn't look for the other files relative to that
[10:57] <juliank> pitti: You'd need to have Dir "my-chroot-path" in your APT_CONFIG file
[10:57] <pitti> Laney: yay freeze lift
[10:58] <pitti> juliank: indeed, that does the trick; so that's what your branch does automatically now
[10:58] <juliank> Yes
[10:58] <pitti> juliank: nice, thanks muchly for fixing that!
[10:58] <pitti> juliank: I guess I'll upload apport then so that the next apt upload catches a fixed one (for the missing ddebs.u.c. key import)
[10:59] <juliank> pitti: Yes, I'll upload a new apt soon too to see if that works :)
[11:00] <juliank> I'll also upload a python-apt that tells apt-key to shut up, so we do not get stderr failures for python-apt
[11:01] <juliank> Once everything works here, I'll upload it to Debian with possibly some more fixes from DonKult and sync it
[11:01] <juliank> here = in Ubuntu
[11:01] <juliank> not on my machine :D
[11:04] <pitti> juliank: new p-apt just landed, FYI
[11:04] <juliank> Great
[11:16] <doko> Mirv, did you have a chance to look at the powerpc related GCC6 qt*-opensource-src FTBFS?
[11:17] <doko> tvoss, sil2100: please could you fix the GCC6 related ftbfs for dbus-cpp and ubuntu-ui-tookit? http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/test-rebuild-20160705-gcc6-yakkety.html
[11:31] <juliank> pitti: uploaded python-apt (to fix the stderr output during test) and apt (with the apt-key config fix from my branch).
[11:31]  * juliank still has to write a test case and probably refactor it a bit for upstream
[11:32] <juliank> For now, the main point is to get the autopkgtests working again, though.
[11:33] <Mirv> doko: not much, but note that yakkety-proposed now has Qt 5.6.1. looking at the previous rebuilds, all of them say "/usr/bin/ld.gold: --secure-plt: unknown option"
[11:33] <Mirv> so maybe it's the powerpc version of ld.gold
[11:38] <Mirv> https://llvm.org/bugs/show_bug.cgi?id=20572
[11:38] <Mirv> that's LLVM though..
[11:39] <doko> Mirv, but you don't use clang explicitly, do you?
[11:41] <Mirv> doko: no, just educating myself of the switch via google
[11:47] <jgrimm> dannf, would you be able to verify https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1574904
[11:51] <Mirv> pitti: Saviq: no proposed in unity8/i386 https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-yakkety-ci-train-ppa-service-landing-019/yakkety/i386/u/unity8/20160728_105414@/log.gz
[11:55] <doko> tedg, could you have a look at https://launchpad.net/ubuntu/+archive/test-rebuild-20160705-gcc6/+build/10416146 (GCC 6 FTBFS)?
[12:02] <doko> Mirv, looks like qtbase-opensource-src has configure options/values -use-gold-linker/-no-use-gold-linker/USE_GOLD_LINKER/CFG_USE_GOLD_LINKER. please disable then on powerpc. gold on powerpc doesn't have this option
[12:03] <doko> but wondering why you only see this with GCC 6 ...
[12:32] <pitti> xnox: do you think the new mdadm is ready for merging now?
[12:39] <xnox> pitti, yes. still need to retest on ubuntu. ideally i would like to just port the remaining ubuntu-only bits to debian (e.g. apport integration) such that we could have it in-sync.
[12:40] <xnox> pitti, are you volunteering to merge mdadm? =)
[12:40] <pitti> xnox: I'm asking because systemd 231-1 needs the new version; I could also temporarily drop that Breaks:, I don't think we actually have an rcS init.d script in Ubuntu; I asked because if you were going to merge/sync anyway that wouldn't be needed
[12:40] <pitti> xnox: I can do the merge (apport bits etc.), but I would suck at testing it
[12:41] <pitti> xnox: AFAIR our main delta was udev vs. init.d script
[12:41] <xnox> oh that. ok. I see.
[12:42] <pitti> not sure if that's still relevant with your rework, as that now seems to be dynamic in the Debian version too?
[12:42] <xnox> I'm hoping to do openssl, boost1.61 and mdadm this week =) today and tomorrow. I guess i could bump mdadm above boost1.61 =)
[12:43] <pitti> I'm just done with ebtables, now going to nfs-utils (that's a big one), and scsitools/ifscheme (these shuold be small)
[12:43] <pitti> then the only remaining one is mdadm
[12:43] <pitti> and then we finally got rid of rcS.d init scripts :)
[12:43] <xnox> pitti, it's now much better in debian than ubuntu, cause it now integrates with block-local loop for proper mount handling.
[12:43] <pitti> sounds yummy :)
[12:43] <pitti> nice work!
[12:43] <xnox> pitti, may i ask you something about postgresql? =)
[12:44] <pitti> xnox: sure, you can always ask (I've been out of the loop for a fair while, so not sure I can answer)
[12:44] <xnox> why the slice is not named as "postgresql-slice" =)
[12:44] <xnox> why the slice is not named as "postgresql-system.slice"
[12:44] <xnox> because at the moment: systemctl status postgresql* -> will show "master" unit & all instances, but not the slice which has e.g. current memory usage stats =(
[12:45] <xnox> imho it should be renamed "system-postgresql.slice" -> "postgresql-system.slice"
[12:45]  * xnox off to get coffee
[12:45] <pitti> slices don't work that way, you can't arbitrarily name them; their name reflects the cgroup hierarchy
[12:46] <pitti> i. e. all system services are in, or in a child of system.slice
[12:47] <pitti> postgresql.slice would be completely independent, thus global resource limits would then not apply to it any more
[12:47] <pitti> xnox: status '*postgresql*' should work?
[12:52] <Saviq> Mirv, yeah I just saw, not sure what's going on... pitti any idea why your "all-proposed" reruns end up running without proposed again https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-yakkety-ci-train-ppa-service-landing-019/yakkety/i386/u/unity8/20160728_105414@/log.gz ?¿
[12:55] <pitti> Saviq: oh, I know: Mirv requested it! bug 1541334
[12:55] <pitti> this was changed in https://git.launchpad.net/~ubuntu-release/+git/autopkgtest-cloud/commit/?id=b029faacbe
[12:55]  * Saviq shakes fist
[12:55] <pitti> i. e. we don't run silos against -proposed because that broke train landings in other ways
[12:55] <pitti> can't have it both ways :/
[12:55] <pitti> so I guess Qt needs to land first?
[12:56] <pitti> how can the new Qt break that silo if it is only in -proposed? or does the new silo depend on the new qt already?
[12:56] <Saviq> pitti, it builds against proposed
[12:56] <Saviq> pitti, so it links against the new qt
[12:56] <pitti> a silo cannot land if any of its dependencies are stuck in -proposed anyway?
[12:56] <pitti> hmm
[12:57] <Saviq> I think it can
[12:57] <pitti> so I could temporarily revert that, but it will again break the cases from teh bug above
[12:57] <Saviq> but here the problem is not dependencies but broken test runs
[12:58] <Saviq> pitti, couldn't --all-proposed override that? i.e. when you explicitly ask for it, shouldn't it go for all proposed anyway?
[12:58] <pitti> I guess so, yes
[12:58] <Saviq> that would be best IMO
[13:02] <Mirv> Saviq: pitti: yes, having proposed enabled brings usually more trouble than it helps, that's why it's generally disabled. but in case of transition like that, it could be useful to have an option to run with all proposed (even risking the other trouble it brings)
[13:03] <pitti> code updated/deployed, retried unity8/i386
[13:04] <pitti> if that works, I'll retry the others
[13:04] <Saviq> great, thanks
[13:04] <Mirv> awesome
[13:15] <xnox> pitti, ahhhh i did not realise that it is `systemd-escape`d path =)
[13:15] <xnox> so it's like .device/.mount units
[13:15] <pitti> xnox: right
[14:33] <Saviq> pitti, looking at http://autopkgtest.ubuntu.com/running.shtml#pkg-unity8 it's much better, so if you could restart all regressions in https://requests.ci-train.ubuntu.com/static/britney/ticket-1604/landing-019-yakkety/excuses.html with allproposed - thanks!
[14:41] <LocutusOfBorg> anybody knows why mdadm is not installable on yakkety? it tries to remove init
[14:41] <LocutusOfBorg> pitti, ^^ seems somewhere systemd/init related
[14:42] <mterry> Laney, any luck on unity-greeter (I'm guessing no)
[14:42] <mterry> ?
[14:45] <Laney> mterry: hey there, nope - haven't tried any more this week really
[14:46] <mterry> ugh.  I don't want to be the one holding up gtk3.20
[14:46] <Laney> mterry: I would probably not actually hold it up on this bug
[14:46] <mterry> Laney, heh
[14:46] <Laney> :)
[14:46] <mterry> Well I don't want to be the one breaking user logins when they make a typo
[14:46] <Laney> haha
[14:47] <pitti> Saviq: indeed, done
[14:47] <Laney> mterry: I noticed that if you go down to the guest session entry and then back then it appears again
[14:47] <pitti> LocutusOfBorg: that only affects -proposed, that's known; see discussion with xnox two hours ago
[14:47] <mterry> Laney, yeah there's an easy way to get it back
[14:47] <mterry> Laney, but you have to try that.  And have more than one entry
[14:47] <pitti> LocutusOfBorg: i. e. systemd will stay in -proposed until mdadm gets merged, or I do a temporary ubuntu delta to drop the breaks
[14:48] <Laney> mterry: damn, I aws hoping that would be a clue to you
[14:48] <mterry> Laney, no.  I don't get it at all
[14:48] <Laney> I think that robert_ancell is back now
[14:48] <Laney> at least he emailed the team aboutu some work stuff...
[14:48] <mterry> Laney, we do set css class names somewhere in there...  but I didn't think we did fancy stuff with it
[14:48] <Saviq> pitti, awesome, thanks - Mirv it's running well now
[14:49] <xnox> pitti, i have a merge ready, and will upload it soon, once i test that it is sort of correct =)
[14:49] <xnox> (it will be a sync)
[14:49] <pitti> awesome!
[14:50] <LocutusOfBorg> I see now
[14:50] <LocutusOfBorg> thanks
[14:50] <LocutusOfBorg> I'll wait then, a bunch of packages are FTBFS because of this issue
[14:50] <LocutusOfBorg> e.g. diffoscope
[14:50] <pitti> urgh, b-dep on systemd and mdadm??
[14:50] <LocutusOfBorg>  sbuild-build-depends-diffoscope-dummy : Depends: python3-guestfs but it is not going to be installed
[14:50] <Laney> mterry: I think all of that should work with the rejigged CSS that I did
[14:51] <LocutusOfBorg> pitti, not directly but meh
[14:52] <LocutusOfBorg> libguestfs should be the one needing them both?
[14:52] <pitti> right, that's the one that is uninstallable right now
[14:52] <xnox> LocutusOfBorg, why do you have proposed enabled on a development machine?
[14:52] <pitti> LocutusOfBorg: sorry about that -- should be fixed soon
[14:52] <LocutusOfBorg> xnox, I don't have
[14:53] <xnox> LocutusOfBorg, one must not run with -proposed enabled on a development series.
[14:53] <xnox> OK
[14:53] <LocutusOfBorg> I don't even run yakkety
[14:53] <pitti> xnox: it's an FTBFS (which runs against -proposed)
[14:53] <LocutusOfBorg> http://people.canonical.com/~ubuntu-archive/proposed-migration/yakkety/update_excuses.html
[14:53] <LocutusOfBorg> yes exactly
[14:53] <LocutusOfBorg> I was looking at gammaray, and I saw diffoscope FTBFS
[14:59] <mterry> Yup commenting out all css use in unity-greeter doesn't fix anything
[15:01] <Laney> probably punt to Robert for now
[15:01] <Laney> he should know lightdm signals the greeter to re-display the box
[15:01] <Laney> that's where I would start poking, but it is pretty complicated to me atm
[15:04] <seb128> didrocks, pitti, could you comment on bug #1584575 maybe? I think it makes sense but you are more familiar with the work done there I think
[15:04] <seb128> like should it have a
[15:04] <seb128>     [Install]
[15:04] <seb128>     WantedBy=multi-user.target
[15:05] <seb128>     Alias=display-manager.service
[15:05] <seb128> ?
[15:05] <didrocks> I don't remember the latest on this, as this got discussed over and over again, but I thought we decided on the Alias
[15:06] <didrocks> let's wait on pitti for now, he may have a better memory that I do on this
[15:06] <pitti> it's blurry as well, but indeed this is controlled by display-manager.service
[15:07] <mterry> Laney, hrm.  Found another bug.  If you click on the session-chooser icon, nothing is drawn and you can't go back
[15:07] <pitti> IIRC all *dm's postinsts need to set /etc/systemd/system/display-manager.service to whatever was chosen in debconf
[15:07] <pitti> seb128: ^
[15:08] <pitti> setting Alias= sounds correct, but not WantedBy=
[15:08] <pitti> we don't want *all* DMs to start
[15:08] <seb128> good point
[15:08] <pitti> the whole mechanics for that is still horribly complicated and redundant -- you can use update-rc.d, debconf, /etc/X11/default-display-manager etc.
[15:09] <pitti> I think /etc/X11/default-display-manager is still meant to be the canonical way to configure this, that's why we skipped the [Install] sections so that you don't introduce contradictions with systemctl enable/disable
[15:12] <seb128> pitti, ok, so looks like a non-trivial one, might just be better to not change anything for now then
[15:12] <seb128> thanks!
[15:15] <Laney> mterry: meh
[15:15] <Laney> it works if you go into the inspector and some rule
[15:15] <Laney> like * { border: 1px solid red; }
[15:15] <Laney> then even if you pause it, it works
[15:17] <mterry> Laney, wait how do you use the inspector again?  you said ctrl+alt+i, which doesn't do anything for me.  I assume I need to be running some inspector tool first?
[15:19] <Laney> mterry: apt install libgtk-3-dev; gsettings set org.gtk.Settings.Debug enable-inspector-keybinding true
[15:19] <Laney> should have said, sorry :(
[15:24] <mterry> still doesn't do anything for me  :(
[15:25] <mterry> Well both the prompt box and the session list use a PromptBox class to do drawing.  And it certainly has some weird drawing logic...  But per my tests, everything seems to be right
[15:27] <pitti> Mirv, Saviq: ah, first green on https://requests.ci-train.ubuntu.com/static/britney/ticket-1604/landing-019-yakkety/excuses.html :)
[15:33] <juliank> pitti: So, the python-apt upload is basically done with testing. No new regressions, as expected, but it will need some manual work due to the click issue (ubuntu-make failure is ignored, click failure is not ) - that fixes the regression with the new APT. I also noticed that the apport test had a communication issue with LP on amd64 and retried that
[15:34] <juliank> So, I think apt should land tomorrow :)
[15:34] <pitti> juliank: indeed, python-apt is all good except click, I'll hint that
[15:37] <pitti> juliank: thanks for retrying apport; once that lands this ought to help with the new apt
[15:37] <juliank> yep
[15:39] <pitti> juliank: just weird that apport in http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#apt still failed the "PPA" tests that should work with the apt fix
[15:40] <juliank> pitti: Hmm, not sure
[15:42] <juliank> But if there's still something to fix, we can do so
[16:11] <xnox> pitti, mdadm 3.4-4 uploaded -> i will try to sync it when it becomes available for syncage. Or if you spot it first, feel free to sync it over. with force.
[17:56] <pitti> "Use the force, Luke^WLaunchpad!" :)
[17:57] <Mirv> pitti: somehow armhf failures show still not using yakkety-proposed https://requests.ci-train.ubuntu.com/static/britney/ticket-1604/landing-019-yakkety/excuses.html - I've pinged Savi_q regarding the unity8 qmluitests failures
[17:57] <Mirv> (on x86)
[17:57] <pitti> Mirv: oh, they ran there -- forgot to update these boxes
[17:58] <Mirv> ok :)
[17:58] <pitti> Mirv: updated the lxd boxes, retried everything again
[17:59]  * pitti waves good evening
[17:59] <Mirv> pitti: thank you, good evening!
[20:49] <Guest55167> does this channel cover 16.10?
[20:52] <Guest55167> anyone here?
[22:37] <xnox> Is this Richard Brandson (Virgin Group) putting on Ubuntu cap? https://res.cloudinary.com/www-virgin-com/f_auto,q_80/virgin-com-prod/sites/virgin.com/files/lewis_hat_2.jpg
[22:41] <infinity> xnox: http://ubuntuismclothing.com/
[22:41] <xnox> OMG there is a whole clothing line.
[22:42]  * xnox throws all my clothes in suitcase and takes it to the dumpster