[02:35] <sheap> how would I file a bug against one of the servers/services/mirrors that ubuntu provides?
[02:37] <sarnold> sheap: iirc ddebs is pitti's area of expertise but I haven't seen him around  lately; maybe a mail to ubuntu-devel?
[02:37] <sheap> sarnold: ah okay, thanks for your help :)
[02:37] <micahg> are you sure it's an ubuntu mirror?
[02:38] <micahg> hrm, I meant one operated by Canonical
[02:39] <sarnold> micahg: it's an oddity with ddebs.ubuntu.com Releases file
[02:39] <micahg> ah
[02:59] <infinity> hallyn: I do like "reassuring flow".
[03:00] <infinity> hallyn: Also, congrats on being the last pre-freeze upload.
[03:07] <hallyn> infinity: \o/  do i get a prize?
[03:07] <hallyn> i'm not happy about it :(
[03:09] <infinity> hallyn: Your prize is a sense of emptiness and loss.
[03:10] <hallyn> it makes no sense.  one uptodate laptop, one uptodate vm.  unpriv vivid containers on one get services in custom cgroups;  on the other ,not.
[03:11] <hallyn> infinity: np, i water that down iwth some johnny walker black
[08:17] <elfy> just installed with the beta2 for us - works great if you've got US keyboard - no keyboard layout page, not had time to look at anyone else's images - bug 1435714
[08:26] <dholbach> good morning
[08:52] <ogra_> didrocks, you broke ubuntustudio it seems, is there a -meta change missing ?
[08:52] <ogra_> (imae builds that is)
[08:52] <ogra_> *image
[08:53] <didrocks> ogra_: oh, can be, are they still using upstart?
[08:53] <ogra_> might be, it fails with an upstart dep problem
[08:53] <didrocks> ogra_: do you have a link? I'm going to give a look
[08:53] <ogra_> The following packages have unmet dependencies:
[08:53] <ogra_>  upstart-bin : Depends: upstart but it is not going to be installed
[08:53] <ogra_> E: Unable to correct problems, you have held broken packages.
[08:54] <ogra_> https://launchpad.net/~ubuntu-cdimage/+livefs/ubuntu/vivid/ubuntustudio
[08:54] <ogra_> oh, meh
[08:54] <didrocks> ogra_: btw, I was wondering, those links are reachable by anything? I always have to look at my legs
[08:54] <didrocks> logs*
[08:54] <ogra_> ignore me, seems it built
[08:54] <didrocks> ogra_: :p
[08:54] <ogra_> dont look at your legs :)
[08:54] <ogra_> thats bad for your neck
[08:54] <didrocks> ogra_: yeah, I try to preserve them :)
[08:55] <ogra_> ah, wait
[08:55] <ogra_> amd64 built, i386 still fails
[08:55] <didrocks> yeah, they are using systemd-sysv though, so the change should be a noop
[08:55]  * didrocks looks
[08:55] <ogra_> different error
[08:55] <ogra_> ignore it
[08:55] <ogra_> upstart wise all seems fine there
[08:56] <didrocks> ogra_: right, seems only archive not reachable
[08:56] <ogra_> infinity, seems all flavours fail in "P: Deconfiguring file /etc/apt/sources.list"
[08:56] <didrocks> so, I didn't broke them :)
[08:56] <ogra_> didrocks, you did ... but only the builds before :)
[08:56] <didrocks> ogra_: just on my question about the links, do you know anywhere in the launchpad interface to reach them?
[08:56] <ogra_> you mean the build logs ?
[08:57] <didrocks> ogra_: well, it built during the transition, so yeah :p
[08:57] <didrocks> ogra_: yep
[08:57] <didrocks> ogra_: was to expect for anything which built before systemd migrates to the release pocket
[08:57] <ogra_> https://launchpad.net/~ubuntu-cdimage/+livefs/<dist>/<suite>/<flavour>
[08:57] <didrocks> ogra_: yeah, so just knowing the pattern… that was my guess, thanks!
[08:58] <ogra_> not sure if you can access older ones than the handfull that is shown there (i doubt we throw them away, but have no idea how to access them)
[08:59] <didrocks> ogra_: that was my wondering, I think I'll do some pattern storage in my browser, thanks!
[08:59] <ogra_> well, i'm sure cjwatson coulld tell you if/where they are kept
[09:00] <ogra_> (they might probably even be accessible via lp-lib, who knows :) )
[09:02] <didrocks> can be ;)
[09:02] <cjwatson> ogra_: no UI for them but you can indeed use the fairly obvious interfaces in launchpadlib
[09:02] <ogra_> :)
[09:02] <cjwatson> start from https://launchpad.net/+apidoc/devel.html#livefses
[09:03] <cjwatson> ogra_,didrocks: alternatively, a quick non-LP way is to navigate through the image build logs in http://people.canonical.com/~ubuntu-archive/cd-build-logs/
[09:04] <ogra_> oh, we still keep that ?
[09:04] <cjwatson> every one of those that dispatched a livefs build includes a link to the LiveFSBuild object in LP at the top of the log
[09:04] <cjwatson> of course
[09:06] <didrocks> cjwatson: yeah, I was using that previously, but it's really not as handy as the launchpad logs
[09:06] <didrocks> didn't notice the link though, thanks for the tip cjwatson :)
[09:11] <cjwatson> didrocks: yeah, at some point I might add proper batch navigation with next/previous etc. in there.  feel free to file a bug against Launchpad itself as a reminder
[09:14] <ogra_> didrocks, was your goal to remove upstart from the images ? that definitely failed on touch ... http://people.canonical.com/~ogra/touch-image-stats/146.changes
[09:14] <ogra_> it only added upstart-sysv
[09:15] <ogra_> (your seed change kind of indicates you wanted to remove it)
[09:16] <cjwatson> ogra_: upstart-sysv Pre-Depends: upstart
[09:16] <ogra_> oh, fine then
[09:20] <didrocks> ogra_: upstart is now "upstart + upstart-bin - upstart-sysv"
[09:20] <didrocks> (and now upstart-bin is empty)
[09:24] <didrocks> cjwatson: bug #1435742 FYI
[09:24] <cjwatson> ta
[09:25] <didrocks> thank you :)
[09:39] <flexiondotorg> Now that the repo is frozen, do I need to do anything differently regarding Debian syncs that fix bugs?
[09:39] <flexiondotorg> Normally, I just subscribe the ubuntu-sponsors, but should I be subscribing ubuntu-release now as well?
[09:40] <Riddell> Noskcaj: how did you get on with git-glib?
[09:45] <cjwatson> flexiondotorg: No, ubuntu-release are notified in other ways
[09:45] <cjwatson> (after the sync happens)
[09:45] <flexiondotorg> cjwatson, Thanks.
[09:45] <cjwatson> flexiondotorg: You only need to subscribe ubuntu-release if you feel you need to get an up-front exception, e.g. for a feature change
[09:46] <flexiondotorg> cjwatson, Understood.
[09:56] <flexiondotorg> cjwatson, I would appear Ubuntu MATE does not have image builds queued for Beta 2 :(
[09:56] <flexiondotorg> cjwatson, How can I get Ubuntu MATE added to Beta 2?
[09:57] <ogra_> flexiondotorg, there was a mail on the release ML
[09:57] <flexiondotorg> ogra_, Still new to this. Not on that ML. Subscribing now.
[09:57] <ogra_> oh, heh ... seems that was a typoed Beta1 call :P
[09:58] <flexiondotorg> ogra_, Is there anything that can be done to include Ubuntu MATE in Beta2?
[09:58] <cjwatson> flexiondotorg: => infinity
[09:58] <flexiondotorg> cjwatson, Thanks.
[09:59] <ogra_> i'm not sure how the process is, usually someone sends a call for participation to the ML
[09:59] <flexiondotorg> ogra_, OK. Last time I was invited via IRC>
[09:59] <ogra_> and the flavoour release managers answer if they want to take part ... doesnt seem to be the case this time
[09:59] <ogra_> so yeah, infinity is your best bet
[10:00] <flexiondotorg> ogra_, What time zone is infinity in?
[10:00] <cjwatson> oh, your last batch of image builds failed
[10:00] <cjwatson> that would be why
[10:00] <cjwatson> looks like a transient network issue
[10:00] <flexiondotorg> cjwatson, Oh.
[10:00] <ogra_> cjwatson, yeah, with a weird connection error when deconfiguring sources.list
[10:00] <ogra_> i pinged infinity above already
[10:00] <ogra_> flexiondotorg, he is in canada
[10:00] <ogra_> but in his case that means nothing
[10:01] <flexiondotorg> ogra_, ;)
[10:01] <ogra_> infinity is in an infinite TZ :)
[10:01] <cjwatson> I've just kicked a rebuild
[10:01] <flexiondotorg> cjwatson, Thanks.
[10:25] <flexiondotorg> cjwatson, Will the rebuild be sufficient to enter Ubuntu MATE into Beta 2 or will I still need to follow up with infinity?
[10:26] <cjwatson> flexiondotorg: I don't recall.  You'll find out from iso.qa.ubuntu.com in a bit.
[10:27]  * flexiondotorg nods
[11:27] <flexiondotorg> cjwatson, Ubuntu MATE 20150324.1 has landed in Beta 2 :)
[11:27] <cjwatson> cool
[11:27] <flexiondotorg> cjwatson, Can you tell me if the PowerPC image is on its way?
[11:27] <cjwatson> you could look yourself in the build logs
[11:27] <cjwatson> http://people.canonical.com/~ubuntu-archive/cd-build-logs/ubuntu-mate/vivid/
[11:28] <cjwatson> looks like it built fine, so presumably beta 2 isn't configured to include it but it's there as a daily build
[11:28] <cjwatson> any changes to that would be an infinity question
[11:30] <flexiondotorg> cjwatson, Thanks.
[11:31] <asac> cjwatson: who would be good to get https://code.launchpad.net/~snappy-dev/livecd-rootfs/core_update/+merge/250245 reviewed?
[11:32] <cjwatson> asac: slangasek should be able to assign somebody
[11:32] <asac> cjwatson: he is out the whole week
[11:33] <asac> who has enough know how to do first round?
[11:33] <cjwatson> asac: ah, well he delegated mvo for foundations matters
[11:33] <cjwatson> asac: so try him
[11:33] <asac> mvo: ^^ can you find someone ?
[11:40] <LocutusOfBorg1> hi developers!
[12:06] <mvo> asac: sure
[12:40] <melodie> hello
[12:42] <melodie> I have been browsing the web and asking on help chans, no one knows about the information I'm seeking, so I thought some devs should know? Can someone tell me how the installer manages to install grub-efi on a machine using efi/uefi on gpt, whereas only grub-pci is in the iso? I checked here: http://cdimage.ubuntu.com/ubuntu/releases/14.04.2/release/ubuntu-14.04.2-desktop-amd64+mac.manifest
[12:42] <melodie> and of course it's the same in the community derivatives
[12:43] <cjwatson> melodie: It's in the pool, not in the squashfs; manifest only lists the latter.  See .list
[12:44] <melodie> hi cjwatson
[12:44] <cjwatson> The pool has various packages as .debs that don't make sense in the squashfs but need to be available for optional or opportunistic installation.
[12:44] <cjwatson> Arguably grub-pc shouldn't be in the squashfs either, but there's probably some reason it's tedious to avoid.
[12:44] <melodie> is that why the command "apt-cache policy grub-efi" doesn't show it as installed?
[12:44] <cjwatson> It won't show it as installed if you're looking in a live session, no.
[12:44] <melodie> I mean in the live
[12:44] <melodie> ok
[12:44] <cjwatson> That's expected and normal.
[12:45] <cjwatson> Though I also wouldn't expect literally "grub-efi" to be installed, since that's a transitional package.
[12:45] <melodie> where in the iso is the pool? Is it even there?
[12:45] <cjwatson> It's carefully hidden in the top-level directory named "pool"
[12:45] <melodie> that would be grub-efi-amd64 or so perhaps?
[12:45] <cjwatson> Just to make it hard for you to find
[12:45] <cjwatson> It would be grub-efi-amd64, yes
[12:45] <melodie> ok
[12:46] <melodie> one more that none knew, if you don't mind. Do Windows updates risk to damage the Grub installed bootloader later, making the access to Ubuntu impossible? (my user isn't a tech person)
[12:47] <cjwatson> I'm very much not a Windows expert.  My understanding is that that is not normally a problem, though.
[12:47] <melodie> ok :)
[12:48] <cjwatson> Some Windows applications fiddle about with the boot area in nasty ways, but GRUB takes countermeasures to protect itself from that.
[12:48] <melodie> oh? !
[12:49] <cjwatson> It has built-in error correction code so that it can survive a small number of its own sectors being overwritten.
[12:49] <melodie> are there official docs about the actual state of dual-boot with Windows 8/8.1?
[12:49] <cjwatson> Of course not if another full-blown boot loader is installed over the top.
[12:49] <cjwatson> No idea.
[12:49] <melodie> alright, thank you.
[13:02] <melodie> cjwatson is there a way to make a custom version having the same properties as an official one? ie: creating a meta package including custom theme and configuration files, then installing that meta package on a minimal ubuntu version? (mini iso or else?)
[13:02] <cjwatson> melodie: Sorry, I don't know
[13:02] <melodie> ok
[13:21] <doko> Riddell, you updated libgit2 without caring about libgit2-glib: https://launchpad.net/ubuntu/+source/libgit2-glib/0.0.22-1build2
[13:23] <Riddell> mm yes, on my todo list
[13:23] <Riddell> Noskcaj: did you get anywhere with that?
[13:25] <cjwatson> 13:17 -queuebot:#ubuntu-release- Unapproved: libgit2-glib (vivid-proposed/universe) [0.0.22-1build1 => 0.0.22-1build2] (no packageset)
[13:25] <cjwatson> 13:17 -queuebot:#ubuntu-release- Unapproved: accepted libgit2-glib [source] (vivid-proposed) [0.0.22-1build2]
[13:26] <cjwatson> Ah, that was doko's attempted and failed rebuild
[13:26] <doko> yeah, didn't check before upload
[13:50] <infinity> ogra_: When you said "all flavours failed", you were exaggerating, I guess?
[13:50] <infinity> ogra_: I certainly see a lot of images on the ISO tracker.
[13:50] <infinity> Though, certainly not as many as should be there. :/
[13:50] <ogra_> infinity, nope, i wasnt... i had one mail per flavour in my inbox
[13:51] <ogra_> except for touch ... which uses ports.u.c
[13:51] <infinity> Tempted to just respin the world instead of sorting out what failed and what didn't.
[13:51] <ogra_> i think colin did that already
[13:52] <infinity> ogra_: Most of the images there are from my run, not his.
[13:52] <ogra_> ah, k
[13:52] <ogra_> yeah, he probably only meant MATE
[13:52] <infinity> Hence my exaggeration comment.
[13:56] <flexiondotorg> infinity, I think Xubuntu are missing i386.
[14:02] <doko> seb128, please could desktop have a look at http://people.canonical.com/~ubuntu-archive/component-mismatches.txt and maybe seed things where needed?
[14:02] <doko> Mirv, tjaalton, mlankhorst: ^^^ same please
[14:03] <seb128> doko, sorry, busy with other things today but I can try tomorrow, but if somebody else has slots to work on that please do
[14:20] <didrocks> doko: 5 entries are due to indicator-applet/gnome-panel wanted to be pulled in main, but it's a false positive. seb128 pointed me at http://irclogs.ubuntu.com/2014/10/07/%23ubuntu-devel.html#t16:18 (seems you already discussed this case)
[14:21] <seb128> https://bugs.launchpad.net/ubuntu/+source/germinate/+bug/1367719
[14:21] <seb128> that was the bug mentioned when we had the discussion previous cycle
[14:24] <cjwatson> infinity: I only did anything about MATE FWIW
[14:24] <cjwatson> seb128: Oh, that turned out to be something altogether different and more confusing
[14:24] <cjwatson> seb128: And guess who didn't write it down in the bug
[14:25] <infinity> cjwatson: Yeah, the dates implied as much.
[14:25] <seb128> cjwatson, I see, time to do that then? ;-)
[14:25]  * cjwatson finds the remaining bit of IRC log
[14:26] <seb128> cjwatson, the issue didn't get fixed though? because it seems it's being discussed again/still problematic on component-mismatch
[14:26] <cjwatson> It didn't get fixed, no.  I've updated the bug
[14:27] <seb128> thanks
[14:38] <infinity> didrocks: *poke*
[14:42] <didrocks> infinity: hey
[14:43] <melodie> cjwatson after finishing the install, grub-efi does not seem installed, it still boots directly to Windows without any choice. (just for your information, don't know yet if I'll put a bug report)
[14:43] <infinity> didrocks: Check out that email I bounced you from pitti.
[14:43] <cjwatson> melodie: OK, well I'm sorry about that, but I'm not working on this stuff at the moment
[14:44] <infinity> didrocks: Can you evaluate if that commit he's alluding to is a dire enough bugfix that we want it in the beta?
[14:44] <cjwatson> melodie: so I guess file a bug if you think something is broken
[14:44] <didrocks> infinity: sure looking and back to you in few minutes
[14:45] <melodie> cjwatson I have to check if it is a bug or if some tweaks are known to have to be done manually (such as copying some files, removing other files…) who would be an expert in the matter?
[14:48] <cjwatson> melodie: Try giving details in #ubuntu-installer once you're reasonably sure it's not your bug
[14:49] <melodie> thanks cjwatson I am going there right away (yes I'm sure I didn't produce the bug)
[14:50] <tjaalton> doko: mesa/xserver changes look fine there
[14:50] <doko> tjaalton, so demote the rest?
[14:52] <tjaalton> doko: the rest? libegl1-mesa-drivers is a dummy package so that's fine, xserver-xephyr was in main due to remmina which I don't care about. the other binaries from these source pkgs of course need to stay in main :)
[14:54] <didrocks> infinity: the patches (there are 2: one from Lennart and a fix later from Martin) are quite instrusive, but I think it worthes a try, backporting them
[15:00] <mlankhorst> doko: not sure if anything needs xephyr..
[15:02] <didrocks> infinity: do you have a bug reference handy?
[15:03] <infinity> didrocks: Nope, it was just something pitti mentioned in passing.
[15:03] <didrocks> ok
[15:03] <infinity> didrocks: You already know more about it than I do. ;)
[15:03] <didrocks> (I feel I should add "sadly" :p)
[15:03] <infinity> Heh.
[15:06] <didrocks> infinity: ok, currently building (a good 20 minutes), will then install, do a couple of reboots and traditional tests. Keeping you posted
[15:06] <infinity> didrocks: Kay.  Would be nice if we could reproduce the thing it's meant to be fixing and test that it's fixed.
[15:06] <infinity> didrocks: But if not, whatever.  WCPGW, right?
[15:06] <didrocks> infinity: yeah, it's a race unfortunately where the mount point is available before the device node…
[15:07] <didrocks> infinity: it's only the init system, minor :p
[15:42] <bdmurray> xnox: Is there a way to stop an upstart user job temporarily?
[15:47] <lamont> dear thermald, must you log every 4 seconds?
[15:57] <Cimi> Ursinha, hi, would be possible to trigger the build of https://code.launchpad.net/~nick-dedekind/ubuntu-settings-components/1390136.laggy-backends/+merge/252754 ?
[16:02] <Ursinha> Cimi: I just triggered a rebuild, not sure why that was there waiting for 23 hours? I'd have to have a look
[16:03] <Ursinha> Cimi: it's also more effective if you ping cihelp on #ubuntu-ci-eng with such requests :)
[16:03] <Cimi> Ursinha, ok, thanks :)
[16:09] <doko> roaksoax, jamespage: please could you subscribe to the python-bcrypt bug reports? b-d of python-django (https://bugs.launchpad.net/ubuntu/+source/python-bcrypt/+bug/1427861)
[16:09] <jamespage> doko, ack
[16:09] <jamespage> done
[16:09] <didrocks> infinity: ok, seems that at least I didn't trigger new bugs with this systemd version: various vms tested under qemu, and my own system
[16:10] <didrocks> infinity: my partitions (even those with ecryptfs) are still mounted, I can play with an usb key and get it automounted/shut down…
[16:10] <doko> thansk
[16:10] <didrocks> and tmpfs on /tmp is ok as well
[16:11] <didrocks> I wonder if that would fix a known bug I saw, one sec
[16:11] <tyhicks> thanks jamespage :)
[16:14] <didrocks> well, no, at least, it didn't regress it
[16:15] <didrocks> infinity: 219-4ubuntu10 uploaded
[16:16] <infinity> didrocks: Kay.  If/when we get a serious keyboard bug sorted out that affects $world, I'll let it into the next build.
[16:16] <didrocks> infinity: sure, poke me if you notice/heard of anything
[16:29] <seb128> infinity, hey, ogra_ claims that the new glibc requires other things to rebuild to stop crashing, is that true? that sounds wrong, for sure if that's the case it means there is some abi change and we should fix that rather than paper over with rebuilds?
[16:29] <seb128> ogra_, ^ moving discussion here
[16:30] <infinity> seb128: That seems entirely untrue, what is this claim based on?
 ogra, did anyone mention that to infinity?
 i think rsalveti|lunch is still investigating
 we know that pulse broke the same time libc landed ...
 buut we dont have actual evidence it is libc's fault yet
[16:30] <ogra_> just for the context :)
 charles, yeah, likely needs a rebuild for latest libc ...
[16:30] <infinity> ogra_: On armhf, or all arches?  Define "broke".  Is there any interesting debugging info?
[16:30] <seb128> to give some more context
[16:31] <ogra_> infinity, as i said, jhodapp and rsalveti are investigating
[16:32] <seb128> infinity, http://pastebin.ubuntu.com/10670042/ was mentioned in the discussion
[16:32] <ogra_> infinity, i dont think we have any way to test audio on non armhf (the x86 emulator doesnt provide any audio)
[16:34] <infinity> Not seeing a ton of evidence there that glibc is at fault, but happy to be involved when people have more info.
[16:34] <seb128> rsalveti, ^
[16:34] <ogra_> right, it just started happening the same time libc landed
[16:34] <infinity> ogra_: Was that an image upgraded in-place from 2.19 to 2.21, or a fresh build with 2.21?
[16:35] <ogra_> infinity, how do you mean "fresh build" ? every image is a fresh build, we dont support dist-upgrade
[16:35] <ogra_> (or apt)
[16:37] <ogra_> sadly it started happening while the importer was disabled ... usually you only have like ten packages changing between two images ... the libc landing came in with a rather big chunk due to that http://people.canonical.com/~ogra/touch-image-stats/144.changes
[16:39] <ogra_> infinity, honestly it could be everything on that above list ... which is why nobody pinged you yet ... but i think davmor2 reported something with media playback in his testing too
[16:39] <infinity> ogra_: Well, that's what I meant.  Was it a clean image, or an image with an upgraded libc for testing purposes.
[16:39] <ogra_> ah, no, we all see it on the recent images since 144 came out
[16:39] <ogra_> 143 works fine
[16:40] <davmor2> infinity: both, On friday it was latest vivid plus libc from vivid-proposed, Monday it was already in the image and displayed the same breakage
[16:41] <ogra_> bug 1435867
[16:41] <ogra_> this is the related bug btw
[16:45] <infinity> davmor2: Oh, that was the media-hub thing I was told about in testing?
[16:45] <davmor2> infinity: Yeap
[16:45] <infinity> Right, and the backtrace I got at the time was unreadably useless. :/
[16:45] <davmor2> infinity: about right :(
[16:53] <flexiondotorg> cjwatson, Remember that grub-pc issue? - https://bugs.launchpad.net/ubuntu-mate/+bug/1426436
[16:53] <flexiondotorg> cjwatson, It is still affecting some installs. Trying to gather some feedback about affected systems.
[16:53] <flexiondotorg> cjwatson, Do you have an insight/ideas you can share with me?
[16:53] <rsalveti> infinity: ogra_: davmor2: I'm investigating this issue now
[16:54] <davmor2> rsalveti: you rock \m/
[16:55] <rsalveti> a lot of things changed in 144, so hard to know for now
[16:55] <ogra_> right
[16:56] <rsalveti> ogra_: infinity: yeah, updated just libc, rebooted, and was able to reproduce the problem
[16:59] <doko> happyaron, is it ok to demote these fcitx packages? fcitx-libs fcitx-libs-gclient fcitx-libs-qt fcitx-module-quickphrase-editor fcitx-qw fcitx-table-all fcitx-table-bingchan fcitx-table-cangjie fcitx-table-dianbaoma fcitx-table-erbi fcitx-table-wanfeng fcitx-table-wbpy fcitx-table-wubi fcitx-table-ziranma fcitx-tools
[17:01] <infinity> flexiondotorg: Looks like your ship-live seed isn't quite working as expected.
[17:02] <flexiondotorg> infinity, Any ideas as to what I can change?
[17:05] <infinity> flexiondotorg: Not sure, poking at it in a sec.
[17:08] <cjwatson> flexiondotorg: Sorry, I'm unlikely to be able to help
[17:08] <infinity> flexiondotorg: Also, why did you remove oem-config-slideshow entirely?
[17:08] <flexiondotorg> cjwatson, OK.
[17:08] <flexiondotorg> infinity, Because OEM config does work with no slideshow present.
[17:09] <infinity> flexiondotorg: Ahh, and no data's better than the generic data?  Fair enough.
[17:09] <Quintasan> mvo: Is it possible to backport fix for debian #778375 to trusty?
[17:09] <flexiondotorg> infinity, There is an OEM going to be using this and they prefer just the progress bars rather than Ubuntu slides in Ubuntu MATE.
[17:10] <flexiondotorg> infinity, So looking at this - http://people.canonical.com/~ubuntu-archive/germinate-output/ubuntu-mate.vivid/ship-live
[17:10] <flexiondotorg> infinity, No grub stuff mentioned at all.
[17:10] <infinity> flexiondotorg: Yeah, I know.  I'm trying to wrap my head around it.
[17:10] <flexiondotorg> infinity, Thank you!
[17:11] <mvo> Quintasan: yes, will you help with the SRU paperwork :) ? is there a bug for this already in ubuntu?
[17:11] <Quintasan> My SRU skills are a little bit rusty but yeah.
[17:11] <mvo> Quintasan: I head out for dinner now, but happy to do that
[17:12] <mvo> Quintasan: lets talk later/tomorrow, I'm european timezone
[17:12] <Quintasan> utc+1 here
[17:16] <flexiondotorg> infinity, All the flavours seems to have sip-live that doesn't include grub - http://people.canonical.com/~ubuntu-archive/germinate-output/ubuntu.vivid/ship-live
[17:16] <infinity> flexiondotorg: No one else seeds it explicitly in ship-live, they inherit it from boot.
[17:16] <flexiondotorg> infinity, Ah, OK.
[17:17] <infinity> Although, I don't see grub-pc in /pool/ for a lot of people.
[17:17] <infinity> Very confusing.
[17:18] <infinity> This has been true going back to trusty, though, so maybe we always expected to get it over the network.
[17:18] <infinity> Or this has been buggy forever, and no one noticed.
[17:19] <infinity> Oh, or grub-pc is in the livefs for others...
[17:20] <cjwatson> Pretty sure it's there due to kernel dependencies or something
[17:21] <cjwatson> Yeah, via boot
[17:21] <infinity> Yeah, so it's in the livefs for everyone but mate.
[17:21] <flexiondotorg> infinity, Feedback I've had from the Ubuntu mATE community is this has been an issue for sometime.
[17:21] <infinity> Curious.
[17:21] <flexiondotorg> Is the order in STRUCTURE important? For example - ship: boot desktop installer d-i-requirements
[17:22] <infinity> ship isn't relevant.
[17:23] <flexiondotorg> I'm just using ship as an example.
[17:25] <infinity> Oh.
[17:25] <cjwatson> The top-to-bottom order in STRUCTURE is important.  In some corner cases, the left-to-right order within a single line can matter if things are non-deterministic anyway and so germinate ends up picking a different random package to satisfy a Provides or similar, but it normally doesn't matter.
[17:25] <infinity> I bet it's because you do the --no-install-recommends thing.
[17:25] <infinity> Yup.
[17:25] <flexiondotorg> infinity, Yeah, I did wonder. Sadly, I have to.
[17:25] <infinity> linux-image Recommends grub.
[17:25] <cjwatson> flexiondotorg: uh, didn't I explain this to you weeks ago?
[17:26] <cjwatson> I distinctly remember the conversation, and I have grub-pc added to ubuntu-mate.vivid/ship-live in my local checkout
[17:26] <infinity> Which means lubuntu probably has this bug too, or they've worked around it elsewhere.
[17:26] <flexiondotorg> cjwatson, Yes. And I started submitting patching to the packages that I could avoid this.
[17:26] <cjwatson> which I was only likely to do if pastebinning it to you
[17:27] <cjwatson> but the kernel clearly can't change its Recommends
[17:27] <flexiondotorg> cjwatson, I did add grub-pc to ship-live as you suggested.
[17:27] <Quintasan> mvo: bug #1435984
[17:27] <infinity> cjwatson: So, the ship-live addition seems to fail curiously, as in it's not there on the images.
[17:27] <cjwatson> oh, I see
[17:27] <infinity> cjwatson: But really, it should just be in the livefs, like it is for everyone who gets it for free via recommends.
[17:27] <cjwatson> probably because it inherits from something else and so germinate thinks it already has it
[17:27] <infinity> cjwatson: Yes, likely that.
[17:27] <cjwatson> indeed, ship-live inherits from boot
[17:28]  * infinity nods.
[17:28] <cjwatson> which is aaaaaaaaarguably incorrect but maybe not worth rocking the boat on
[17:28] <cjwatson> so yeah, add grub-pc to live
[17:28] <flexiondotorg> cjwatson, Wilco.
[17:28] <cjwatson> preferably with a comment explaining that this is due to --no-install-recommends
[17:28] <flexiondotorg> cjwatson, infinity Just grub-pc?
[17:29] <flexiondotorg> cjwatson, Understood.
[17:29] <cjwatson> grub-pc is the only one in this particular maze of twisty passages
[17:29] <cjwatson> but we'll see
[17:29] <cjwatson> sorry I didn't understand properly earlier
[17:29] <infinity> Huh.  lubuntu has grub-pc in their livefs.  I wonder how.
[17:30] <infinity> Dumb luck, I guess.
[17:30] <flexiondotorg> cjwatson, infinity Many thanks for helping me with this.
[17:30] <flexiondotorg> I'll push updated seeds in a sec.
[17:30] <flexiondotorg> And rebuild.
[17:30] <cjwatson> Lubuntu doesn't have Feature: no-follow-recommends in its live seed
[17:31] <cjwatson> So it gets the Recommends of ubiquity
[17:31] <infinity> cjwatson: Ahh, it's only in some other bits, I guess.  And in livecd-rootfs.
[17:31] <cjwatson> I'd recommend that ubuntu-mate do the same if it doesn't break things
[17:31] <cjwatson> But there may be some reason it isn't practical right now
[17:31] <flexiondotorg> cjwatson, Sadly, I need no-follow-recommends in the live seed.
[17:31] <cjwatson> So in that case, it may in fact be worth checking through the Recommends of ubiquity
[17:32] <cjwatson> Recommends: grub-pc | grub | grub-efi, dmraid, btrfs-tools, ubuntu-drivers-common, lvm2
[17:32] <infinity> Changing anything two days before a milestone is probably not practical, but it really should be cleaned up.
[17:32] <flexiondotorg> cjwatson, Without it the indicator-* stuff pull in pretty much all of Unity.
[17:32] <cjwatson> You're adding grub-pc, you already have dmraid, so perhaps you should add btrfs-tools, ubuntu-drivers-common, lvm2
[17:32] <infinity> flexiondotorg: There are ways to fix that, but yeah, not today.
[17:33] <flexiondotorg> infinity, I have been submitting patch to indicator-* to add MATE support so I don't have to no-follow.
[17:33] <flexiondotorg> infinity, But for some that patching is not trivial.
[17:33] <flexiondotorg> cjwatson, Thanks for the tips on other packages.
[17:33] <flexiondotorg> I'll check those now.
[17:43] <flexiondotorg> cjwatson, How does this look to you? http://bazaar.launchpad.net/~ubuntu-mate-dev/ubuntu-seeds/ubuntu-mate.vivid/view/head:/live
[17:57] <cjwatson> flexiondotorg: seems fine
[17:57] <cjwatson> (though you don't need "#" to introduce a comment in seeds; it just has to not begin with " * ")
[17:57] <flexiondotorg> cjwatson, Thanks for looking and think for helping.
[17:57] <flexiondotorg> cjwatson, I know I don't need # for comments, but old habits... ;)
[17:58] <flexiondotorg> *thanks for helping
[18:16] <Jeremy26> Hi.  Which #irc chan is the right place to deal with GRUB2+UEFI installer failures for PRE-release Vivid?  Afaict, there's breakage -- and I'm trying to help get this addressed befor the release.
[18:27] <dz0ny> hi
[21:50] <doko> infinity, would you accept gccgo-5 during the freeze? changes to libgo only
[21:51] <infinity> doko: I'd have to respin for libgcc1, so ideally not.
[21:52] <infinity> doko: But go ahead and upload, I can block in proposed and let it through if there's a reason for another respin.
[21:52] <doko> ok
[22:15] <doko> infinity, uploaded, and gmp is waiting too, correcting a recommends to keep gcc-4.8 quiet in universe
[22:16] <infinity> doko: Ta.  I assume gccgo-5 needs sagari to build happily?
[22:17] <doko> yes, testsuite is on
[22:17] <infinity> doko: Alright, I'll let it in when that kernel build is done, then.
[22:18] <infinity> I guess I could give armhf a head start and cancel the ppc build.
[22:18]  * infinity does that.
[22:50] <rsalveti> infinity: so the media-hub issue is actually an issue between gstreamer and pulse
[22:50] <rsalveti> infinity: it fails to seek/pause, causing either a crash (fails to lock a mutex) or a cond_wait that stays forever
[22:51] <rsalveti> which, for whatever reason, only happens with the new libc
[22:51] <infinity> rsalveti: Possibly due to (ironically) bugfixes in threading on ARM? :P
[22:52] <rsalveti> infinity: that would be my guess as well
[22:52] <rsalveti> works fine with x86
[22:52] <infinity> rsalveti: Trawling git commits between 2.19 and 2.21 show a fair number of fixes from Will Newton along those lines, but nothing looks obviously wrong to me.
[22:53] <infinity> rsalveti: If one could construct a small test case that would let us pass blame one direction or the other, that would be nice.
[22:53] <rsalveti> yup, that's what I'm trying to do