/srv/irclogs.ubuntu.com/2015/04/02/#ubuntu-release.txt

=== sturmflut_ is now known as sturmflut
cyphermoxinfinity: hey, I just remember now. did you contact design about updating the slideshow?14:12
=== doko_ is now known as doko
infinitycyphermox: Nope.  That needs doing.14:53
cyphermoxinfinity: k. I will contact people.14:55
kickinz1o/15:00
rbasakinfinity: kickinz1 has done some testing and prepared a summary of our proposed docker 1.5 bump in bug 1430760 that I think answers your questions. Could you review please?15:00
rbasakdoko: ^^ any comments?15:00
ubot93bug 1430760 in docker.io (Ubuntu) "[FFE] Bump up docker.io version to 1.5 in Vivid" [High,Triaged] https://launchpad.net/bugs/143076015:00
elfycyphermox: you managed to get anywhere with the halt after removing install medium in vivid at all?15:02
cyphermoxelfy: not yet :(15:07
cyphermoxI did nail the oem-config though15:07
elfyokey doke15:07
cyphermoxI'm getting back to getting plymouth to catch input right after my meetings15:09
infinitycyphermox: Ta.15:10
infinityrbasak: I can look after this meeting.15:10
rbasakThank you!15:10
dokorbasak, are all build-deps in vivid?15:11
rbasakdoko, infinity: oh, good point, sorry. I forgot about that.15:12
rbasakWe had to sync two packages from Debian.15:12
rbasakThey'd be NEW in Vivid.15:12
rbasakI will update the bug.15:12
dokorbasak, gccgo-go [powerpc] drop this, not necessary anymore15:14
rbasakdoko: OK, no problem. I didn't know why that was needed - your changelog entry didn't say.15:15
rbasakkickinz1: ^^15:15
rbasakBug updated noting the two new build deps.15:15
kickinz1rbasak, OK, was updating bug also...15:16
dokorbasak, that was working around issue in gccgo-5 on powerpc, not needed anymore15:16
dokorbasak, any idea why arm64 fails to build?15:17
rbasakdoko: no, but I didn't pay much attention because I'm told it was broken previously, so there's no regression there.15:17
rbasakI'm treating arm64 as a separate effort that I haven't taken on right now.15:18
doko+ifeq ($(DEB_BUILD_ARCH),ppc64el)15:18
doko+    DOCKER_BUILD_TARGET = dyngccgo15:18
doko+else15:18
doko+    DOCKER_BUILD_TARGET = dynbinary15:18
doko+endif15:18
doko+15:18
dokothis looks wrong ...15:18
rbasakThe patches add a new build target, so we use it on ppc64el. Why is it wrong?15:19
dokoshould be ifneq (,$(filter $(DEB_HOST_ARCH), arm64 powerpc ppc64el))15:19
rbasakAnd armhf maybe? But it builds and works on armhf with golang-go it seems?15:20
dokoyes, unless you want to use gccgo on armhf15:20
kickinz1rbasak: yes, builds and seems to work on armhf15:20
rbasakOK. I have no objection to changing it to your conditional then.15:20
dokorbasak, do you have a build log for arm64?15:22
kickinz1doko, I'll get it15:23
rbasakdoko: OOI, why DEB_HOST_ARCH instead of DEB_BUILD_ARCH?15:24
rbasakShouldn't the choice of compiler be based on the target architecture?15:25
flexiondotorgcyphermox, That reference to "plymouth catching input" is that to to fix the issue with entering the full disk encryption passphrase?15:25
dokoBUILD is the arch you build on, HOST the arch you build for15:26
dokorbasak, ^^^15:27
cyphermoxflexiondotorg: no15:27
cyphermoxit's on shutdown15:27
infinityrbasak: HOST is the architecture that will be hosting the binaries, BUILD is the arch that's building them.  And yes, we all know it's confusing, and we're a couple decades too late to fix it. :P15:28
rbasakAh. Thanks. I should have read the docs more carefully instead of assuming.15:30
dokoand don't confuse HOST and TARGET ;-P15:30
infinitydoko: And then throw all the assumptions out the window when dealing with the kernel, where they renamed everything to make sense, but completely conflict with compiler tradition.15:35
kickinz1doko, sorry was in a meeting.16:08
slangasekinfinity: looks like update-manager is particularly unhappy with debconf passthrough failures from kernel postinsts16:26
infinityslangasek: Like, somehow more unhappy than it is with libc6? :P16:28
infinityslangasek: Or the same brand of unhappy?16:28
slangasekinfinity: I never had to run 'apt-get -f install' for libc616:28
slangasekand I'm now getting very bizarre backtraces from u-m16:28
infinityslangasek: Oh, but that's just pure luck because libc6 debconfs in preinst.16:28
slangasekactually no, because while I said postinst, looking closely I see that linux-image is also failing in preinst16:29
infinityBleh.  I guess I'll bump "figuring out HTF to debug that" further up the list.16:30
apwslangasek, is that our breakage, or just breakage and we're the victim16:33
infinityapw: The latter.16:33
* slangasek nods16:33
infinityI actually dreamt that I fixed the bug the other night, and woke up remembering just enough of the dream to realize that my subconscious is a very, very bad programmer.16:35
infinity"No, like, really, if you just insert a banana in this loop here, everything works."16:35
slangasekheh16:40
slangasek"bug in debconf passthrough; ate more fiber"16:40
kickinz1doko, rbasak: just updated bug logs with arm64 builds (both golang and gccgo).16:40
dokokickinz1, arm64 golang?16:41
infinityslangasek: Too far.16:42
* infinity drafts an HR complaint.16:42
kickinz1doko, I just tried, didn't check. there seems to be a golang package available for arm64 as it is all arch.16:44
ogra_infinity, but did you even try the banana thing ? probably your subconscious isnt actually that far off, you just belive it is16:46
infinityogra_: My new laptop doesn't have a banana port.16:46
ogra_ah, damn ... technical hurdles .. yeah, thats bad then16:46
dokokickinz1, this is an old build log, copied from the debian log archive ... please don't do that. rbasak, if you have a fixed package, please test-build it on vivid/arm6416:52
dokohave to run now16:52
kickinz1doko, no, I did it tueday, maybe I uploaded the bad one...16:54
slangasekinfinity: because it's an Apple?17:10
rbasakdoko: are you looking at the right file?17:13
rbasakdoko: I see the build log kickinz1 produced. Eg: I: Finished running '/home/ubuntu/docker_test/repo/add'.17:13
rbasak(hack for sbuild to pick up new build deps not in the archive yet)17:13
=== kickinz1 is now known as kickinz1|afk
infinitycyphermox: Hrm, did you really want "isolate" and not "start" in oem-config-firstboot?18:22
infinitycyphermox: The reading of isolate implies that it'll stop anything that graphical.target doesn't depend on.18:22
infinitycyphermox: Which would include, say, mysql, sshd, whatever other random things might have been running but not necessary to the target you asked for.18:23
cyphermoxinfinity: isolate in systemd means "change runlevel"18:23
infinitycyphermox: Also, how does this work for non-graphical systems (oem-config on a server)?18:23
cyphermoxwhich before oem-config sounds fine, tbh18:23
cyphermoxserver appears to be landing in graphical.target too18:24
infinityWeird...18:24
cyphermoxit's also not actually starting anything in oem-config unless you reboot into it18:25
infinityMmkay.18:25
cyphermoxfrom which point once it's done, it will go in graphical.target (could be any other target we want, really), to really do the rest of the startup18:25
cyphermoxthe point is to avoid starting getty@tty1, or display-manager, since they kind of break the oem-config18:26
infinityI love this brave new, and super-intuitive world.18:28
cyphermoxahaha18:28
cyphermoxI agree with "world"18:28
infinity"I world as well!"18:29
cyphermoxand new.18:29
cyphermoxmuch less about super-intuitive.18:29
bdmurrayslangasek: https://code.launchpad.net/~brian-murray/ubuntu-archive-tools/strike-thru-dupes/+merge/25513119:18
tedgSo I've got a package that is in proposed, but migration is blocked on a boottest error that seems to be a known bug.19:22
tedgHow do I move that along?19:23
slangasektedg: which package and what bug?19:23
tedgBug: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/142100919:23
ubot93Launchpad bug 1421009 in qtbase-opensource-src (Ubuntu) "unity8 sometimes hangs on boot" [Critical,In progress]19:23
infinitytedg: We just retry the test.19:23
tedgPackage: ubuntu-themes19:23
tedginfinity, Is that something I can do?19:24
infinitytedg: I believe so, but not sure exactly how the permissions there work.19:24
slangasektedg: people with the necessary jenkins access can; I also don't know what the acl is19:24
infinitytedg: I retried it, but you can see if http://d-jenkins.ubuntu-ci:8080/view/Vivid/view/BootTest/job/vivid-boottest-ubuntu-themes/ has a "Build Now" link on the left for you after you've logged in (top right).19:25
slangasekbut anyway, yeah, for a boottest failing due to an intermittent bug, we want to retry it and see it *not* fail to be sure the known bug isn't masking unknown bugs19:25
tedginfinity, I can see it, but I don't have Build Now19:25
infinitytedg: And you're logged in?19:26
tedgYup19:26
infinitytedg: In that case, the answer to the ACL question is "no". :P19:26
infinityIt should be improved to make sure people with upload rights can also twiddle tests, but I think this is one of the many warts that aren't likely to get fixed before a move away from Jenkins.19:26
slangasekaddendum: "ask the QA team"19:26
tedgWell I don't have upload rights19:27
infinityOh, in that case, nevermind.19:27
infinityEven if it was working the way I'd think it should, you wouldn't have access.19:27
tedgSo the set may be correct19:27
* tedg should really apply, but there are so many nice people to help19:28
boikohello, I have two packages marked with "Regression" labels in the update excuses page (telephony-service and telepathy-ofono)19:30
boikodo I need to do anything regarding those two packages?19:30
infinityboiko: They succeeded on a retry.19:48
boikoinfinity: ah nice, thanks20:05
=== alexabreu is now known as alex-abreu|off
bdmurrayslangase`: https://code.launchpad.net/~brian-murray/ubuntu-archive-tools/strike-thru-dupes/+merge/25513122:53
=== slangase` is now known as slangasek
slangasekbdmurray: ack, looking22:53
slangasekbdmurray: merged22:54
bdmurraythanks22:54
=== salem_ is now known as _salem

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