User1: jamespage,  ping
User2: babyface_, morning
User1: jamespage, good morning!
User1: jamespage, I just found that the job http://91.69.162.6:8080/view/Quantal/view/ISO%20Testing/job/quantal-server-amd64_tomcat-server/70/testReport/junit/test/TomcatServerTest/testTomcatDaemon/  failed again.  but in this bug:  https://bugs.launchpad.net/ubuntu/+source/tomcat7/+bug/1025595   you said you already increased the time
User3: Ubuntu bug 1025595 in tomcat7 "tomcat7 not running on port 8005 after installation" [Undecided,Invalid]
User1: jamespage, could you have a look on it?
User2: babyface_, I have - but it is possible that on a really slow VM that it still does not complete in time.
User2: babyface_, I am considering an alternative fix to this - to make randomness a bit quicker in the test VM for this test
User1: jamespage,  yes, please.
User1: jamespage, we can not just let it be unstable, that looks ugly  ;)
User2: babyface_, yes - but it is a test failure rather than a bug... I will fix it but not right now...
User2: babyface_, if you want a green ball just run it again - in all likelyhood it will pass..
User4: User2 Assuming this is a /dev/random entropy issue, just make the VMs use urandom for random?
User2: infinity, yeah - that was my thinking
User1: jamespage, ack, I know, it's not a big deal, and not a real bug in code, so take you time and fix it when you are free
User2: i've just not got to it yet
User4: (That said, I could see it as a package bug too, if the package sometimes forks the daemon but then doesn't *actually* start for a minute, that's a bit unintuitive)
User4: User2 But it's certainly a bug/misfeature in the test framework to ever use a real /dev/random, unless the point of the test is actually to test quality of randomness (which would be a rather rare testcase, I suspect).
User2: infinity, certainly not in this case
User5: !package haveged
User3: Factoid 'package haveged' not found
User5: !deb haveged
User3: Factoid 'deb haveged' not found
User5: User2 User4 $ sudo apt-get install haveged
User5: this will give you more entropy without using urandom. I do this a lot on VMs.
User2: xnox, that of course is another alternative...
 * jamespage wonders what that package actuall does...
User5: Linux entropy source using the HAVEGE algorithm
User5: french wrote it, it must be good =)
User6: User9 I've confirmed that all those duplicate ArchivePermission rows are gone now.
User6: User9 (P.S. please use edit-acl rather than edit_acl.py - at some point I'll drop that compat symlink)
User7: erm...
User7: User8 you're not in backporters; why are you uploading and accepting backports?
User8: User7 it's not good enough to be a core-dev?
User7: no, just as it isn't for SRUs
User8: User7 sorry about that
User9: User6 yay, thanks for cleaning that up!
User10: ogra_, Daviey -  I'm seeing we're still building arm server armhf+omap - who's using it/testing it?  and can it be dropped?
User10: mvo,  we're starting to ramp into A3 now.   Could you please do the GnomeAppInstallDatabaseUpdate now?
User11: I just realized we're still showing 'quantal daily' and not alpha 3 as our milestone
User12: skaet, well, i switched armhf to alternate over the weekend and would greastly prefer to drop server preinstalled but i'm not sure if QA relies on preinstalled
User12: skaet, alternate is only built for omap4 atm
User10: balloons, we'll be switching it over today
User12: skaet, and server preinstalled is still broken
User10: ogra_,  why do we care about armhf+omap?
User10: for server
User12: skaet, because its the easiest way to install adev setup on a beagle
User12: *a dev
User12: using ubuntu-core is painful to set up, the alternative is the netboot images but these indeed require a network connection
User12: but i wouldnt cry if we lose them
User12: skaet, as for all omap3 images, we only build them because it has such a big community ... but we're lacking testers here
User10: ogra_,  if we're lacking testers,  not much point in building them while we're limited for capacity.
 * Riddell wonders if he has time to slip in one extra new package into the archive for alpha 3
User12: skaet, well, we get the kernel and bootloader for free (close to zero work) and we have a ton of spare beagleboards in the datacenter (former builders)
User12: we should just send them out to some people :)
User13: User8 mind if I rebuild calligra-l10n today for bug #1027215
User3: Launchpad bug 1027215 in calligra-l10n "calligra-l10n-xx should enhance, not recommend calligra" [High,Triaged] https://launchpad.net/bugs/1027215
 * micahg doesn't want to disrupt kubuntu alpha 3
User10: Riddell,  how many hours is it going to take to build?
User8: User13 yes please go ahead
User10: (and dependencies...?)
User8: User10 5 minutes says launchpad, but it's actually not on the images so it shouldn't be an issue for alpha I think
User10: Riddell,  if its not on the image no worries,  even if it is,  we're still fine for something that small.
 * skaet more worried about kernels, unity, firefox, launchpad, etc.
 * cjwatson is still hoping to get the server squashfs work in today
User6: just fixing tasksel at the moment
User6: almost everything else is done
User6: User10 what's the worry about launchpad?
User10: cjwatson,  no worry about launchpad,  just that "package" can be rather an ambiguous term in terms of build time.
User10: was just trying to figure if it was something smallish,  or not
User6: ok
User14: User4 What are the chances you get around to fixing the fact that soyuz makes packages with uninstallable build-deps FTBFS instead of putting them in dep wait anytime soon?
User14: In Kubuntu there's discussion of rewickering the packages to work around this, but it'll be work that could be avoided if that's going to happen soonish.
User10: Laney, slangasek https://wiki.ubuntu.com/QuantalQuetzal/TechnicalOverview/Alpha3  is ready for data to be added from the various teams now.
User7: great, perhaps link it from the freeze announcement
User10: Laney, yup,  just posting here to let you know that step is done.
User10: infinity,  until the new arm build infrastructure comes online,  can we drop arm server armhf+omap?   I don't think we have any testing lined up for, it,  and we're getting pretty close to capacitity with arm builds in the 24 period.
User4: User10 I'm happy dropping it forever and just having netboot.
User4: (Same goes for all armhf+omap images)
User4: We discussed this last Alpha, but I think failed to come to action.
User10: infinity,  ok.    for all the ones you're the signoff for,  consider removed from the manifest then.
User4: Riddell / User14 Any qualms about dropping armhf+omap from Kubutu (not omap4, just omap)
User4: User10 Which ones am I signed off for? :P
User10: infinity, https://wiki.ubuntu.com/QuantalQuetzal/ReleaseManifest
User10: ubuntu server pre-installed armhf+omap,  ubuntu preinstalled armhf+omap are the ones I'm spotting with your name beside
User4: Right.  And Kubuntu doesn't list it in the manifest anyway, so dropping that works too.
User8: User4 I'm fine with it but is there a way I can justify that to my community?
User14: User8 I don't think we have any testers.
User4: User8 You apparently don't list it as a release image anyway... Unless that was a mistake.
User4: User8 And you so don't have testers.  I ended up testing that image for precise.
User4: (And it sucked... Beagleboard + KDE = lolz)
User14: And the Canonical QA person who used to do it in his personal time doesn't work for Canonical anymore.
User14: So no testing.
User8: that'll do then, fine to drop it
User10: infinity,  ok,  dropped from the manifest.     nusakan need editing to reflect,  but I need to go to dentist now.   If you get to it before I return, post here please.
User4: Erk.
User4: User7 We dropped all precise arm images?
User7: User4 Apparently that was the decision.
User10: infinity Core should still be there.
User4: I missed that memo.
User4: Well, yes.  I don't count core when I talk about images.
User4: Cause it's not one.
User4: Not an installer, anyway. :P
User4: User7 What was the driver behind ARM not being cool enough for point releases?
User10: https://wiki.ubuntu.com/PrecisePangolin/ReleaseManifest/12.04.1
User10: infinity, ^ this is for daily builds prior to LTS release.
User4: User10 Kay, that doesn't give me rationale.
User10: and follow on from what was indicated as LTS vs. not in:  https://wiki.ubuntu.com/PrecisePangolin/ReleaseManifest
User10: all the arm ones were 18 month support
User4: Ahh, fair enough.
User4: User7 That probably didn't need default-arches mangling, mind you, since "not doing daily-preinstalled builds" would have a similar effect.
User4: Anyhow.  No big deal.  Just conflicted with my changes. :P
User10: infinity,  what changes????
User4: ...
User7: hahaha
User4: User10 The ones we discussed 6 minutes ago?
User10: heh,  ok.  :)
User10: sorry,  Laney's were done earlier and I was worried it was something else.
 * skaet --> dental appt.  biab
User11: I updated the notice board for the ETA on when the milestone builds will hit. Can we please make sure it stays up to date as we have respins, etc? Thanks!
User11: it's currently listed as 0600 on July 24th -- update if that day/time changes
User6: I'm switching the server images over to squashfs-base style now
User6: I guess there's some kind of fiddly pad thing I have to update?
User15: for the image build list, there's http://pad.ubuntu.com/ubuntu-release
User14: http://greenwellplumber.com/blog/wp-content/uploads/2011/12/Bathroom_humor_by_charfade1.jpg
User6: OK, server switched to squashfs-base, amended pad accordingly
User6: running an experimental build now, since all is quiet
User6: Oops, build failure with squashfs-base.  Fixing ...
User14: Is the highbank stuff going into Quantal as well?  Precise-proposed before Quantal doesn't fit the SRU policy.
User9: User16 ^
User16: User14 its already in Quantal, but flash-kernel had a rewrite so its a different patch
User14: OK.
User14: Thanks.
User16: I'm waiting for my PPA to finish building d-i to make sure I got everything sane then that gets uploaded and can be fully tested
User14: Good to hear it's (at least not in the short term) another poulsbo.
 * NCommander grumbles, armhf/powerpc seems tohave dropped off my PPA
User14: (which you could only ever run on one Ubuntu release)
User16: User14 its been a bit of a pain TBH. d-i itself requires a command line option to run while everything is in proposed. There is a chance everything might work, and the moment it gets pocket copied to updates it will break
User16: (I'm pretty sure it won't, but we've never built a new image on a point release before)
 * skaet back
User14: The good news is that whatever it does, it's not a regression ....
User10: slangasek, Laney - email sent for the freeze.
User4: User16 Eh?  d-i requires no such thing.
User16: User4 ?
User4: User16 We do d-i in proposed all the time, how is that broken for you?
User16: User4 no, I'm not expecting it to break. However, because highbank's enablement bits are in proposed, we need to set apt-setup/proposed=true on the command line for testing
User10: slangasek,  will you be doing the debian-installer upload for the new kernel?
User4: Oh, sure.  Kay, I thought you meant something sketchier for building.
User4: User10 I will.
User4: User10 Once they all roll in.
User16: I know d-i will pull udebs from updates, but a voice in the back of my head tells me to revalidate the instant highbank migrates to updates
User10: infinity,  what's still left to land?
User16: User4 when do you plan to upload d-i? I'm about to upload it to add highbank (I can depwaiton your patches)
User4: User10 Two ARMs and a PowerPC.
 * skaet should have known.
User4: User16 Talking about quantal here.
User16: oh
User4: User16 But I do need to commit a kernel ABI bump for precise-proposed too.  No reason those can't be in the same upload as your fiddling, however.
User16: User4 I committed my highbank d-i patches onto the proposed branch, and testbuilt on armhf/i386 and looks good, so if you just want to upload it tonight
User10: slangasek, infinity - I'm going to turn off the cron now, and point the next set of builds to start populating alpha 3 on the iso tracker.
 * skaet figures Laney's EODed by now...
User16: User4 if you plan on doing your ABI bump tonight, I'll leave it as is, else I rather upload ASAP as mahmoh and mreed need to testthis
User4: User16 I can do it tonight.  Gives me a chance to quickly review your bits too.
User16: User4 thanks
User10: cron for quantal disabled,   builds targetted to Quantal Alpha 3
User10: infinity, am looking at the changes made to the server rebuild, and its not synching up with what's in the crontab for server at the moment.  Do you know or cjwatson make the changes to the pad?
User10: (pad.ubuntu.com/ubuntu-release)
User4: User10 They seem to reconcile fine for me, what's the issue?
User6: User10 What infinity said.
User6: I made those changes.
User10: cjwatson,  seeing buildlive with for-project $p cron.daily  looked a bit odd
User6: It's correct, and it matches the crontab.
User6: It's not really a "live" build; we're using buildlive because it knows how to build squashfses, but it's just for the base system.
User6: The images still use d-i.
User10: thanks.  that makes a bit more sense.
User15: User10 cron> sounds good, thanks
ubuntu-release
Ubuntu IRC