[00:22] <amjjawad> hi infinity when I go to: http://cdimage.ubuntu.com/ubuntu-gnome/trusty/daily-live/20160217.1/trusty-desktop-i386.iso .. I get an error message "Not Found"
[00:22] <amjjawad> infinity, "The requested URL /ubuntu-gnome/trusty/daily-live/20160217.1/trusty-desktop-i386.iso was not found on this server."
[00:23] <amjjawad> same for "Ubuntu GNOME Desktop amd64"
[00:25] <jderose> yeah, i've been noticing weird things too... in the trusty/daily/ folder, 20160217.1 keeps appearing and disappearing but only have the i386 oversize warning file there
[00:26] <infinity> amjjawad: It's probably rsyncing.
[00:26] <infinity> jderose: ^
[00:27] <wxl> except that it doesn't show rebuilding on the tracker
[00:27] <wxl> which is what i'm accustomed to
[00:27] <wxl> like Lubuntu's still building
[00:27] <infinity> It's syncing from the primary build machine to the mirror frontends.
[00:27] <infinity> It marks it as done when it's done on the primary.
[00:27] <amjjawad> infinity, thanks for your reply. Any idea how long that would take? I'm on +11GMT and it's a huge hassle for me to keep up with those who are in your time zone for example ..
[00:27] <infinity> So, just be patient.
[00:28] <amjjawad> Ok, guess no other option but to be patient :)
[00:29] <infinity> It's trying hard to push the bits around. :)
[01:08] <infinity> wxl / amjjawad: Those images should be all happy now.
[01:11] <amjjawad> infinity, seems so, many thanks :)
[07:02]  * highvoltage checks in for testing time
[07:11] <highvoltage> 
[10:36] <davmor2> infinity: \o/ wifi on a mac \o/ \o/ \o/ and now back to testing
[10:51] <Adri2000> I just got filezilla 3.15 and libfilezilla (NEW) uploaded into xenial, the latter being needed by the former. a bit feature freeze rush :)
[13:09] <flocculant> infinity: marked xubuntu ready - grabbing the kubuntu images now - if no-one's touched them when I get back I'll at least make sure the images load in vbox and install
[15:58] <tgm4883> Wild question and possibly not the right place to ask, but is there any way for a flavor to have a PPA enabled (either via asking the user, or automatically) in the ISO?
[16:05] <cjwatson> All a flavour's packages have to be in the primary archive - that's part of the definition of being a flavour
[16:05] <cjwatson> https://wiki.ubuntu.com/RecognizedFlavors
[16:09] <lamont> does poilicy say that main should not Recommend: universe?
[16:09] <lamont> cjwatson: remind me of update-excuses url?
[16:09] <lamont> looking at why maas is still sitting in proposed (1.10 -> xenial)
[16:10] <cjwatson> lamont: recommend> yes
[16:10] <cjwatson> lamont: http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html
[16:10] <cjwatson> but you need http://people.canonical.com/~ubuntu-archive/proposed-migration/update_output.txt here
[16:10] <cjwatson>     * amd64: maas-test
[16:10] <lamont> cjwatson: as in recommend: never recommend universe? or it's ok to?
[16:10] <cjwatson> lamont: as in main is meant to be closed under recommends
[16:11] <lamont> ack
[16:12] <lamont> cjwatson: what's the proces forgetting maas-test dropped from the archive?\
[16:12] <cjwatson> lamont: file bug, subscribe ubuntu-archive
[16:13] <cjwatson> lamont: I can't quite see what the actual problem here is - oh, is it that python-maas-client is dropped?
[16:13] <lamont> yeah - and maas-test is deprecated and dead to us with python3
[16:15] <tgm4883> cjwatson: I know. I was trying to find a way to get more users mythtv fixes builds
[16:16] <tgm4883> currently, my plan is to bombard them with "you really should be using blah"
[16:21] <spleak> Quick Q: Wondering about release date of 14.04.4. Wiki says today, that still holds?
[16:34] <infinity> flocculant: Thanks in advance for the help with kubuntu.
[16:35] <infinity> lamont: main is closed WRT recommends because we install them by default, and it would lead to different behaviour if you have universe enabled or not.
[16:36] <infinity> (Hence why we don't make it a closed set for suggests, since those require purposeful action)
[16:37] <lamont> right
[16:50] <stokachu> what time today will the archive close?
[16:50] <infinity> stokachu: If by "archive close" you mean feature freeze, somewhere vaguely around 2100 UTC.
[16:51] <stokachu> yea feature freeze
[16:51] <stokachu> ok cool thanks
[16:51] <infinity> stokachu: Noted at the top of every ReleaseSchedule page: "Freezes normally happen around 2100 UTC time of the given date"
[16:51] <stokachu> ah i see that now :)
[16:52] <cyphermox> infinity: finishing the Changes report now...
[16:52] <infinity> cyphermox: \o/
[16:52] <infinity> cyphermox: Is the wiki r/w this morning?
[16:52] <cyphermox> looks that way
[16:52] <infinity> Shiny.
[16:53] <cyphermox> can you confirm the last USN included was USN-2902-1 ?
[16:53] <infinity> cyphermox: I have a call with Leann and $customer in 8 minutes, but after that I'll fix up the release notes, backup 14.04.3, create 14.04.4, and point to your summary page.
[16:53] <infinity> cyphermox: 2903-1 (NSS)
[16:53] <cyphermox> ah, cool
[16:54] <cyphermox> I wasn't sure, so I went conservative
[16:54] <cyphermox> the page will be at TrustyTahr/ReleaseNotes/ChangeSummary/14.04.4
[16:57] <cyphermox> yah, it's saved now. I have a local copy of the whole file, if anything breaks.
[16:58] <yofel> flocculant: we had one person testing kubuntu 14.04 yesterday or so. I just asked him again whether he had actually updated the iso tracker (I think he didn't)
[16:58] <yofel> flocculant: thanks for the help!
[17:03] <flocculant> yofel: welcome ofc - I did entire disk + livesession (just to make sure it worked) for both 64 and 32 bit
[17:05] <flocculant> yofel: did you see ^^ - results on tracker anyway
[17:07] <yofel> flocculant: didn't, thanks!
[17:14] <flocculant> infinity: which one of you good guys is helping out next week for B1 ?
[17:14] <infinity> flocculant: Not sure right now, but if no one's signed up, it might end up being me.  We'll see.
[17:15] <flocculant> ok
[17:15] <flocculant> I'll leave you in peace with trusty now :)
[17:45] <smb> infinity, I am a bit despairing now. Since yesterday at some point (cannot pinpoint it exactly) sbuild of Xen in Xenial fails at a stage that has not changed (in fact the version currently in the archive now fails at the same stage). Manually entering the chroot and running the same command succeeds. And when building in my PPA succeeded as well I hoped the archive would succeed there as well. But sadly not.
[17:45] <smb> https://launchpadlibrarian.net/240376638/buildlog_ubuntu-xenial-amd64.xen_4.6.0-1ubuntu3_BUILDING.txt.gz
[17:46] <smb> I am at the end of my wits about what is going on there...
[18:04] <wxl> what's the word, birds?
[18:05] <infinity> smb: Colin's new sbuild upload should fix it.
[18:06] <infinity> smb: Err, oh.  I didn't read your log. :P
[18:06] <infinity> smb: I have no idea what's broken your build...
[18:10] <infinity> jibel: We seem to be lacking any testing for server.
[18:10] <infinity> davmor2: ^
[18:11] <infinity> I'll do ppc/ppc64el.
[18:11] <davmor2> infinity: don't the server team handle that normally
[18:12] <infinity> davmor2: I like the theory, I'm unsure it's working in practice today.
[18:14] <davmor2> infinity: well we'll just blame them when it doesn't work properly, I'll just tickle the last of these desktops that are running and then I'll have an install but it will be rough and ready as I say we don't normally touch server
[18:14] <infinity> davmor2: Yeah, it doesn't need to be thorough, just a run-through with defaults and a reboot to make sure it boots/installs/reboots, and has the right kernel installed.
[18:14] <infinity> davmor2: That's all I'm doing on ppc*
[18:15] <infinity> davmor2: AFAIK, they're meant to have automated testing that is much more thorough, and they fill in the results, but I see no results filled in...
[18:15] <infinity> smoser: Que pasa with 14.04.4 testing from your team?
[18:16] <cyphermox> infinity: I can start some server install tests
[18:17] <infinity> cyphermox: Sure.  I've got the powerpcs covered.
[18:19] <cyphermox> ok
[18:20] <cyphermox> 0218 is the right one?
[18:23] <infinity> cyphermox: 217.1  There is no 28...
[18:23] <infinity> Err, no 218
[18:24] <infinity> cyphermox: http://cdimage.ubuntu.com/ubuntu-server/trusty/daily/20160217.1/
[18:24] <cyphermox> I'm an idiot, I was looking at xenial
[18:25] <davmor2> infinity: aren't server team the ones with access to s390x
[18:26] <infinity> davmor2: A few of us do, not that that relates to trusty...
[18:34] <davmor2> right tea is called so I will pick up when I get back
[18:36] <Beret> I'd love to live where tea is called
[18:39] <wxl> infinity: precise had 5 point releases. will trusty? or will 4 be it as with lucid?
[18:40] <wxl> oh yikes looks like someone needs to update https://wiki.ubuntu.com/ReleaseSchedule/LTStoLTS too
[18:44] <infinity> wxl: It'll have 5, with .5 including the lts-xenia kernel and X stacks.
[18:44] <infinity> s/xenia/xenial/
[18:45] <wxl> infinity: is that to be the *expected* trend from here on out?
[18:45] <infinity> wxl: Yeah.
[18:45] <wxl> infinity: thank you as always. :)
[18:47] <infinity> Alright, core all tested.
[18:52] <wxl> ok lubuntu's ready to go with release notes and everything
[18:52] <wxl> well, i just got to uncommon the drafty bits
[18:52] <wxl> ugh
[18:52] <wxl> s/on/ent/
[18:56] <smb> infinity, Somehow the only explanation for the error seen would be that the invocation of gcc only gets a partial file. But why is that always happening under sbuild control but not when using the exact same command (grep'ed from ps) when re-entering the exact same chroot environment that sbuild was using. I even threw away the whole build directory and re-created it with dpkg-source and still this would not break on
[18:56] <smb>  the manual run.
[18:58] <infinity> smb: Point me at the source package?
[18:58] <smb> infinity, well as it is now, just do a pull-lp-source xen xenial
[18:58] <infinity> smb: Oh, it's just the distro package?  Kay.
[18:59] <smb> infinity, yeah. and since that now fails but did build in the past its at least some little proof that the "it was not me" has some reason
[19:04] <davmor2> infinity: right last i386 test completed server images downloading now
[19:08] <davmor2> infinity: right I have i386, amd64 and mac on the go now
[19:08] <infinity> davmor2: Ta.
[19:30] <davmor2> infinity: running check disk on amd64+mac, amd64 and i386 I'm just testing the installed selections are installed
[20:07] <davmor2> infinity: done
[20:11] <cyphermox> I have a preseed test running for server, the mandatory and run-one are already done for amd64.
[20:11] <cyphermox> ah, well :D
[20:14] <davmor2> cyphermox: yeah I got all excited and hit them with a hammer
[20:14] <cyphermox> davmor2: good
[20:15] <davmor2> infinity: so are we good?
[20:24] <infinity> davmor2: Image-wise, yes.  Doing a bunch of pre-publishing and mirror bits and such now.
[20:25] <infinity> And contemplating a quick lunch.
[20:26] <davmor2> apparently the one guy is really desperate for us to know that intel 4500 gma gfx have an odd effect for him, but the intel part of my lenovo had no issues so no idea unfortunately
[20:30] <infinity> Okay, mirrors syncing, lunch while that settles out, then announcements and web site updates.
[20:53] <coreycb> infinity, can I get access to an s390 instance to test a dep8 failure?
[21:03] <wxl> we there yet? :)
[21:07] <infinity> coreycb: Possibly, but not by asking me.
[21:08] <coreycb> infinity, ok doko maybe?
[21:09] <doko> coreycb, that would be xnox
[21:09] <spleak_> 14.04.4 out of the oven soon, I presume? :)
[21:09] <coreycb> doko, ok thanks
[21:17] <wxl> spleak_: that's the plan, but we';re waiting on the official go ahead.
[21:32] <coreycb> xnox, I found an s390 machine
[21:40] <wxl> infinity: thanks for the heads up about us going live!
[21:42] <infinity> wxl: We're basically live.  I'm sending the announce now.
[21:42] <wxl> infinity: you mean you just sent it :)
[21:42] <infinity> Oh, was it moderated?
[21:42] <infinity> Kay.
[21:43] <wxl> luckily i'm on #ubuntu-news as they noticed it first :)
[21:44]  * pleia2 on top of things
[21:45] <pleia2> (it's on the fridge now)