=== chiluk` is now known as chiluk === jamesh__ is now known as jamesh === _salem is now known as salem_ === salem_ is now known as _salem [04:50] Good morning === timrc is now known as timrc-afk [06:59] good morning === tvoss is now known as tvoss|test === tvoss|test is now known as tvoss === Zic is now known as Guest68979 === Guest68979 is now known as Zic [08:53] I wonder if others are getting the graphical apt icon from time to time claiming KeyError "The cache has no package named 'ubuntu-emulator-runtime'" and if there's something that would need fixing. I think the package was this i386 only package? [08:53] sometimes I don't have it, but I remember having it already a month ago or so [08:54] right, from the 'android' source === Chipaca is now known as Chipakeitor === Chipakeitor is now known as __chip__ === __chip__ is now known as Chipaca [10:57] mvo_: have you seen bug 1341320? There's also http://askubuntu.com/questions/496199/hwe-support-status-does-not-tell-me-how-to-upgrade-to-12-04-5 which I think is the same thing. [10:57] bug 1341320 in update-manager (Ubuntu) "empty apt-get install command suggested by hwe-support-status" [Undecided,Confirmed] https://launchpad.net/bugs/1341320 [11:00] rbasak: no, haven't see it, thanks for the notificiation === MacSlow is now known as MacSlow|lunch === _salem is now known as salem_ === psivaa_ is now known as psivaa === MacSlow|lunch is now known as MacSlow === kentb-out is now known as kentb [14:27] hallyn: I rebuilt qemu with the debdiff for the mknod kvm stuff -- it didn't build qemu-keymap -- so my upgrade of packages is failing ... what am I missing? [14:27] rharper: i'm probably pushing to archive soon. but, qemu-keymap is obsoleted [14:27] it'll get removed when you upgrade [14:28] hrm, ok, maybe I'll just uninstall it [14:28] just trying to confirm that the upstart job does create the node file inside a container [14:28] the packaging should mamke it uninstall [14:28] it didn't [14:28] pkg is built at ppa:serge-hallyn/virt [14:28] you can jsut add that and dist-upgrade [14:28] ok, lemme give that a try then [14:29] ok then i'll wait for your report before pushing to utopic [14:32] hallyn: is that utopic only or should trusty versions be in there? I added and updated, but I don't see a qemu 2.1 via showpkg for qemu-system-x86 [14:33] rharper: utopic only [14:33] i don't think we can sru that to trusty [14:33] it's tiny, but stlil a feature [14:33] urg [14:33] that's fair [14:33] hallyn: lemme try on utopic then [14:34] hi! I was wondering if there's an up to date ubuntu-recommender repo? === wedgwood1 is now known as wedgwood [15:31] doko: fwiw I'm giving back freetype for ppc64el, this doesn't look like a freetype bug there's no error output from the compiler [15:34] doko: webob retry succeeded [15:35] barry, good, can you look at the other python-* ftbfs too? [15:36] doko: yep, it's one of my background tasks [15:37] * barry likes test suites that take 20m to run === Ursinha is now known as Ursinha-afk === dbarth_ is now known as dbarth [15:58] slangasek, freetype, looks like an issue with -fPIC only ... libtool sends this output happily to /dev/null [15:58] afk === timrc-afk is now known as timrc [16:00] doko: what an absurd thing for libtool to do! === victorp_ is now known as victorp [16:10] compiz would like to have core-dev ack for the dependency changes https://ci-train.ubuntu.com/job/ubuntu-landing-016-2-publish/8/artifact/packaging_changes_compiz_1%3A0.9.12+14.10.20140918-0ubuntu1.diff [16:19] slangasek, Me again. We been testing full disk encryption using Ubuntu 14.10 daily with mixed results. [16:20] pitti, ping! Will you be releasing a new version of umockdev? We (in the mir team) are looking forward to the O_TMPFILE fix... [16:20] slangasek, I can reliably reproduce installing a fresh 14.10 daily with full disk encryption enabled and then on first boot Plymouth will display just a black screen. [16:20] If I switch to vt1 and back to vt7 I see the Plymough graphical theme and pass phrase entry but Plymouth will not accept my pass phrase. [16:21] This is using hardware with open source radeon driver. [16:21] However, doing the same on hardware with Intel integrated chipset, everything works fine. [16:29] flexiondotorg: ok, useful info; I'm not sure if I have a radeon system here to test on but I'll try to figure that out [16:30] What we have also discovered is if we disable vt_handoff. Everything appears to work correctly. [16:30] slangasek, Have tested that theory extensively but so far a busted system can be made to work. [16:31] s/Have/Have not/ [16:56] slangasek, freetype is an include issue ... /home/doko/tmp/freetype-2.5.2/freetype-2.5.2/include/freetype.h:33:28: fatal error: ftconfig.h: No such file or directory [16:56] #include FT_CONFIG_CONFIG_H [16:56] ^ [16:57] -I ./builds/unix is on the command line, but it should be -I ../builds/unix === kentb is now known as kentb-afk === kentb-afk is now known as kentb === roadmr is now known as roadmr_afk [18:42] in 14.04.1 a package has MultiArch: foreign, and i can depend on it on an i386 package and install it on amd64 and everything works [18:42] in 14.10 it has no MultiArch, and I can't [18:42] is that a bug? [18:45] which package? [19:06] slangasek, Back from my run if you have any questions regarding Plymouth. [19:06] Or rather the testing we've been doing. [19:10] cjwatson, do yo uhave aminute ? [19:11] i'm trying to figure out what d-i does in install on ppc64el that i'm not doing [19:17] i'm prety sure its doing something to get /boot/grub/grub or /boot/grub/powerpc-ieee1275/core.elf onto /dev/sdb1 (the EFI system partition) [19:17] but it is moderately different [19:18] heres what the installed d-i system looks like : http://paste.ubuntu.com/8374462/ [19:21] flexiondotorg: mostly it's down to me laying hands on a radeon machine, I think [19:22] I'd send you one of mine but as I unerstand we are separated by some many thousands of miles 😞 [19:23] barry: ping https://bugs.launchpad.net/ubuntu/+source/python3.4/+bug/1367907 is there we can do anything about this? [19:23] Launchpad bug 1367907 in python3.4 (Ubuntu) "Segfault in gc with cyclic trash" [Undecided,New] [19:23] slangasek, Just used todays image and no need to vt switch but I still can't get Plymouth to accept the pass phrase. [19:25] flexiondotorg: I'm reasonably certain that there are radeon machines closer to hand, yes [19:27] slangasek, I've asked a couple of the other guys to join us here to explain what they have doscovered using virtualisation platforms such as Vbox and QEMU. [19:27] Not sure if they will take the bait and join though. [19:30] flexiondotorg: results in virtualized environments don't tell us why it's not working on radeon; VMs have different video drivers, and have been mostly-broken for a while with most of the VM video options [19:31] slangasek, Fair enough. But in some virtualised environment it works and others it doesn't. I thought it might be an easier way to gather some test data? [19:31] flexiondotorg: well, that would be useful data to have, but it still wouldn't help us for radeon [19:32] slangasek, Agreed. But I don't think this problem is specific to radeon. [19:35] The following bug reports maybe relevant. [19:35] https://bugs.freedesktop.org/show_bug.cgi?id=80553 [19:35] https://bugs.gentoo.org/show_bug.cgi?id=517572 [19:35] Freedesktop bug 80553 in general "plymouthd exists prematurely so boot splash doesn't work with 0.9.0" [Normal,Assigned] [19:35] bugs.gentoo.org bug 517572 in Core system "sys-boot/plymouth-0.9.0 does not shows splash screen" [Normal,Unconfirmed] [19:37] flexiondotorg, not sure how much you told so let me know what you need me to elaborate on [19:41] sigh [19:41] i need someone to sit me down and explain to me what the modules/abi checking in the kernel build process is all about [19:41] in terms that i won't forget again === roadmr_afk is now known as roadmr [19:46] infirit, Basically can you tell slangasek what virtualised environment can be used to demonstrate the problem and those that work fine. [19:47] infirit, I explained the on real hardware radeon open source driver do not allow Plymouth the accept the decryption pass phrase where as Intel drivers do. [19:47] virtualbox 4.3.14 does it for me [19:48] Sadly, I don't have an Nvidia system I can test on. [19:48] infirit, Virtualbox does what, work or not work? [19:48] I know, I know the answer but slangasek doesn't 😃 [19:48] But also qemu 2.1.1 in virt-manager/libvirt [19:49] flexiondotorg, slangasek none of those work for me once installed. [19:49] I have not tried vmware [19:50] Only when removing the handover it works in these 2 [19:50] But hat may just be working around another problem [20:06] slangasek: can you retry python-concurrent.futures: https://launchpad.net/ubuntu/+archive/test-rebuild-20140914/+build/6375254 [20:07] barry: retried [20:08] thanks [20:16] jtaylor: realpath [20:17] ? [20:18] 20:45:50> which package? [20:22] oh thats the one that got absorbed into coreutils right? [20:22] might be a bug due to the change [20:23] oh its one big package, thats probably why [20:31] jtaylor: what does that mean? [20:32] oh, in U it's in coreutils? [20:32] so it's a bug in the dummy transitional package i guess [20:32] though coreutils is M-A: foreign so it should work [20:32] maybe, the transitional is not m-a [20:32] exactly, and that breaks it [20:33] hm, can i depend on coreutils >x.y.z | realpath ? [20:33] I think so [20:37] worked in U, let's see on T [20:37] filing a bug should not harm either [20:38] yup [20:38] assuming m-a works for transitionals [20:38] * Chipaca files [20:39] https://bugs.launchpad.net/ubuntu/+source/realpath/+bug/1371303 [20:39] Launchpad bug 1371303 in realpath (Ubuntu) "missing MultiArch breaks multiarch packages that depend on realpath" [Undecided,New] [20:40] hm it should be filed against coreutils that contains the transitional [20:40] now to see if it'll work in 12.04 too :) [20:45] jtaylor: thanks for reassigning it === tdc_ is now known as tdc [21:02] Could someone please look at bug 1371309 [21:02] bug 1371309 in ubuntu-gnome-meta (Ubuntu) "Add numix-gtk-theme to ubuntu-gnome seed" [Undecided,New] https://launchpad.net/bugs/1371309 [21:24] cjwatson, You did the most recent change to the seed, is bug bug 1371309 alright? [21:24] bug 1371309 in ubuntu-gnome-meta (Ubuntu) "Add numix-gtk-theme to ubuntu-gnome seed" [Undecided,New] https://launchpad.net/bugs/1371309 === salem_ is now known as _salem [21:37] rbasak, jamespage: why is mysql built sequentially? [22:32] well, cjwatson if you come around. this is d-i install: http://paste.ubuntu.com/8375494/ . and this is curtin install: http://paste.ubuntu.com/8375494/ [22:43] bah. d-i : http://paste.ubuntu.com/8374462/ [23:13] doko: so for the record, it's not libtool that's suppressing the output, freetype is invoking libtool with >/dev/null 2>&1 and I can't figure out where in the build system this is happening === timrc is now known as timrc-afk [23:14] doko: also, I am skeptical of this "include issue"; why would freetype have regressed in its ability to find its own headers, and why would it have regressed only on ppc64el? [23:14] it is libtool [23:14] or the generated Makefile, once building with, and then without -fPIC [23:16] doko: freetype's build system is crazy and I can find no generated Makefile like you describe - which file are you seeing this in? === timrc-afk is now known as timrc [23:25] slangasek, no, it is libtool itself calling the compiler twice, once without -fPIC, and then with it [23:26] doko: ah; so it's libtool redirecting gcc's output? [23:26] do you know how to override that? [23:30] smoser: At a glance, I'm not actually seeing a problem with the difference between those two pastes. I assume that the curtin one doesn't boot, however? [23:31] # Allow error messages only from the first compilation. [23:31] if test "$suppress_opt" = yes; then [23:31] suppress_output=' >/dev/null 2>&1' [23:31] fi [23:31] hmm, -no-suppress apparently [23:31] doko: yeah, just got there, thanks [23:31] this is of course not documented in libtool --help [23:31] slangasek, libtool -no-suppress [23:32] apparently not [23:32] needs to go after the --mode argument [23:35] doko: ok; this is what I get for output now, doesn't say anything about an include problem? http://paste.ubuntu.com/8375838/ [23:36] hmm [23:36] slangasek: That's an -O3 problem. [23:36] does this go away with -O2? [23:36] probably ;) [23:37] slangasek: Or, rather, a sketchy code being optimised to oblivion with -O3. [23:37] I just wanted to confirm that this wasn't the include problem you were seeing [23:37] I'll chase it down from here