[00:01]  * phillw just what we need in a testing cycle.... sarcasm
[00:13] <infinity> micahg: Did your ubuntustudio-default-settings forget a Pre-Dep on a dpkg that supports maintscript-helper, or was it already there?
[00:15] <infinity> micahg: Ahh, nevermind, it was already there.
[00:26] <pgraner> skaet, ETA on images dropping?
[00:27] <skaet> pgraner,  they've started posting now.   alternates and server are all up
[00:27]  * pgraner needs to plan his drinking accordingly
[00:28] <infinity> pgraner: That's some solid prioritizing.
[00:28] <skaet> :)
[00:28] <pgraner> infinity, dude two nights of late drops... you're lucky I can type
[00:28] <infinity> pgraner: Timezone shift, man.  Drink in the morning, work at night.
[00:28] <infinity> pgraner: As a former manager of mine used to remind me, "it's always happy hour somewhere."
[00:29] <skaet> ubuntu alternate,  ubuntu dekstop, ubuntu server, ubuntu server arm should all be up.   ubuntu preinstalled arm are building now.
[00:29] <skaet> ubuntu dvd will be a while.
[00:29] <pgraner> infinity, I look at the whole day/night drinking times as limitations, I don't like being limited
[00:29] <skaet> LOL
[00:30] <pgraner> skaet, yep they are rolling in, I'm doing ARM first, then alternate, and desktop last
[00:30] <skaet> pgraner, sounds good.   flag here if any ugglies.
[00:31]  * skaet crossing fingers no ugglies.
[00:34] <cjwatson> slangasek: oho, aptitude 0.6.6-1
[00:34] <slangasek> hmm!
[00:35] <slangasek> cjwatson: are you going to merge it?
[00:35] <cjwatson> can do though not tonight
[00:35] <slangasek> ok, cool
[00:35]  * slangasek assigns you the bug then ;)
[00:36] <cjwatson> <- sucker
[00:38] <infinity> Oo.
[00:38] <infinity> It has the magical m-word.
[00:42] <skaet> stgraber,  only selected images being published are being reported in the channel.  Anything special needs to be done?
[00:46]  * infinity wonders idly where he can find 13MB to drop off the Ubuntu/PPC image.
[00:50] <stgraber> skaet: the bot was disconnected after flooding freenode earlier
[00:50] <skaet> stgraber,  gotcha.  thanks.
[01:25] <stgraber> added an hack to delay messages a bit to avoid being kicked out
[01:27] <cjwatson> that maas-enlist change is kind of important to avoid a rather obvious error
[01:27] <cjwatson> I've reviewed and accepted it
[01:28] <cjwatson> if pad.ubuntu.com will talk to me ...
[01:30] <cjwatson> hm, server was already built in this round
[01:30] <cjwatson> so I guess it's up to the server leads to ask for a respin if they want one
[01:31] <infinity> It was only *just* rebuilt, spinning it again wouldn't be world-ending, I bet.
[01:31] <infinity> And that bug seems annoying.
[01:32] <cjwatson> As well as the bug described, the particular manifestation of it will include the maas-enlist-udeb installer step failing with a red screen, I think.
[01:32] <hggdh> cjwatson: does d-i output 'question will be asked' even if a response is in the preseed?
[01:33]  * hggdh sees an error on server raid, seemingly because of that
[01:35] <cjwatson> hggdh: Not normally.  Point me to details?
[01:36] <hggdh> cjwatson: we run, under Jenkins, the ISO tests for server. For the new ISO, I got a failure on the RAID test. Looking at the current (failed) syslog, I see a 'question will be asked'. Since I look for it, I cancelled the run automatically
[01:36] <cjwatson> Do you have a URL for me?
[01:37] <hggdh> cjwatson: but looking at the *previous*, successful, run, I also see a 'question will be asked'
[01:37] <hggdh> yes
[01:37] <hggdh> cjwatson: https://jenkins.qa.ubuntu.com/view/Precise%20ISO%20Testing%20Dashboard/view/Daily/job/precise-server-amd64_raid1/126/console
[01:38] <hggdh> the full syslog is in here: https://jenkins.qa.ubuntu.com/view/Precise%20ISO%20Testing%20Dashboard/view/Daily/job/precise-server-amd64_raid1/126/artifact/126/test-results/
[01:43] <cjwatson> hggdh: Well, firstly, grub-pc/install_devices isn't preseeded (perhaps you're thinking of grub-installer/bootdev).  But it shouldn't be preseeded anyway.
[01:46] <cjwatson> hggdh: Secondly, this question is INPUTted in a kind of weird environment, and (although I can't see precisely why right now) it's quite possible it might say "question will be asked" when it in fact won't be.  If I were you I would disregard that one unless it's actually causing an automatic install to hang for itself.
[01:47] <hggdh> cjwatson: thanks. I will correct the code so that it will only fail the test if we are stuck on a
[01:47] <cjwatson> It is a bit weird, but debconf debugging was designed for human consumption rather than machine :-)
[01:47] <hggdh> 'question will be asked' right now. Later on I will look at the first point you made
[01:47] <cjwatson> Well, the first point doesn't contain any action for you
[01:48] <cjwatson> Your preseed looks fine from this point of view
[01:48] <hggdh> even better :-)
[01:48] <hggdh> this is a timing error on my code, then (and the first time since jaunty (when we added this test) that it happened
[01:48] <cjwatson> If it actually hangs, obviously, I'd like to know about it
[01:49] <hggdh> ack
[01:50] <cjwatson> looking at the successful log, this is something to do with passthrough weirdness, indeed
[01:50] <cjwatson> https://jenkins.qa.ubuntu.com/view/Precise%20ISO%20Testing%20Dashboard/view/Daily/job/precise-server-amd64_raid1/125/artifact/125/test-results/d-i-syslog.log.gz
[01:51] <cjwatson> after the first "INPUT high grub-pc/install_devices", there's some fiddling around with DATA (which transfers template information from one debconf frontend to another) and SUBST, and then it reissues the INPUT
[01:51] <cjwatson> the second time, it gets "question skipped"
[01:53] <hggdh> k
[01:53] <cjwatson> Oh, of course, this is a consequence of debconf-apt-progress
[01:54] <cjwatson> Sorry, for extremely limited values of "of course" probably confined to the person who wrote the code
[01:54] <hggdh> :-)
[01:54] <cjwatson> I'll explain in case anyone cares
[01:54] <phillw> Just so as this little borg drone knows before he goes for regeneration cycle, how are the respins going?
[01:54] <cjwatson> debconf-apt-progress deals with bridging apt download and install progress bars into debconf progress bars so that they can be displayed nicely, particularly in the installer
[01:55] <cjwatson> This involves two instances of debconf, one for the progress bar and one passing through questions from the package(s) being installed
[01:56] <cjwatson> (Not to mention cdebconf, which runs in the installer environment and is what actually displays everything - they're all chained together in a way that took me weeks to get working to start with but now I just ignore it most of the time)
[01:57] <cjwatson> Now, it's painful to run two instances of debconf normally, because they both want to lock their config database when they start up
[01:58] <cjwatson> So what you do is you take the one that passes through questions from the package being installed, and give it a database which amounts to /dev/null; it just shunts everything over to the instance that's running the progress bar
[01:58] <cjwatson> This means that the debconf instance that *first* sees the INPUT command here has no idea that the question has been preseeded
[01:59] <cjwatson> It isn't until it forwards it to the second one, which actually has a database worth talking about, that it knows about the preseeding so you get "question skipped"
[01:59] <hggdh> ah
[02:00] <cjwatson> This certainly makes machine parsing challenging, but that was never in the plan for that debug output :-)
[02:00] <cjwatson> So I don't feel too bad about it
[02:01] <hggdh> heh. It will be easy to fix my code, anyway -- just compare previous 'question will be asked' line with the current -- if they are the same, then we are stuck
[02:01]  * cjwatson idly notes that debconf-apt-progress is one of the few debconf programs nobody has got round to reimplementing for cdebconf yet ...
[02:01] <phillw> cjwatson: I do not suppose that any time soon you could explain that for us mere mortals? But, if you have got the handle on it & we will have isos, I trust in you guys just as I trust in MOTU's.
[02:01] <cjwatson> phillw: I think that was the best I could do without a whiteboard
[02:03] <cjwatson> As for respins, the desktop/DVD sequence seems to be working on Lubuntu at the moment
[02:03] <stgraber> now with tested anti-flood protection, hopefully it won't get kicked out any time soon
[02:03] <cjwatson> or rather the desktop sequence, looks like DVDs are being done in parallel with that
[02:04] <cjwatson> skaet: any particular reason bug 959224 is listed as a target of opportunity?  I don't plan to look at that this week.
[02:04] <ubot2> Launchpad bug 959224 in choose-mirror "Corrupt value for /etc/apt/apt.conf accepted during installation" [Medium,New] https://launchpad.net/bugs/959224
[02:05] <cjwatson> It's only a validation bug; certainly a bug but there are more important things and it doesn't block installation
[02:05] <phillw> cjwatson: I am guilty, it just seems a really silly bug
[02:05] <cjwatson> Sure, but it shouldn't be tracked here
[02:06] <phillw> cjwatson: it does not, but it blocks updates
[02:06] <cjwatson> Only if you entered it wrongly during installation.  It doesn't block otherwise.
[02:06] <cjwatson> What I mean is it isn't a blocker for everyone, or even most people.
[02:06] <skaet> cjwatson,  noted it there from earlier discussion, wasn't sure.   remove it if you're not looking at it,  no worries.
[02:07] <phillw> cjwatson: it was only a suggestion, as it may have tied in with the wriong mirrors being suggested.
[02:07] <cjwatson> Wrong mirrors being suggested?
[02:07] <cjwatson> (Bug#?)
[02:08] <phillw> cjwatson: sorry, seems to be same bug
[02:08] <cjwatson> phillw: OK, well, that bug only affects the proxy setting
[02:09] <cjwatson> I'm happy to try to fix it for final if I have time
[02:09] <cjwatson> Though it's very unlikely to be new; I suspect it goes back a long way.
[02:12] <phillw> cjwatson: both lubuntu and another flavour reported it.
[02:13] <phillw> cjwatson: remove that, the bug 966450
[02:13] <ubot2> Launchpad bug 966450 in debian-installer "Kubuntu doesn't prompt for a password on encrypted LVM boot (dup-of: 966403)" [Undecided,New] https://launchpad.net/bugs/966450
[02:13] <ubot2> Launchpad bug 966403 in debian-installer "Lubuntu Install (entire disk with encryption) doesn't prompt for disk password." [Undecided,New] https://launchpad.net/bugs/966403
[02:14] <phillw> which is an install bug
[02:15] <cjwatson> FWIW I did such an installation earlier today (or was it yesterday?) and it was fine
[02:15] <cjwatson> It's actually probably not an installer bug
[02:16] <cjwatson> That's first boot, so it's more likely to be cryptsetup or plymouth or something
[02:16]  * cjwatson sends it over to cryptsetup as a first pass
[02:18] <cjwatson> (which for the avoidance of doubt means somebody else will probably need to figure it out ...)
[02:18] <phillw> cjwatson: do you have the time to set the bugs as such and see if it comes back? I've seen reports of encryption bugs earlier & would like to clear the ground on them. Thanks.
[02:18] <cjwatson> "set the bugs as such"?  don't understand, sorry
[02:21] <phillw> cjwatson: well, either fix released, or needs more information? The two bug reports have a lot of data, but if there has been a release that retrospectively makes them invalid, then a simple "please check with latest release" will suffice?
[02:21] <cjwatson> I don't think that would be appropriate; he only just reported it
[02:22] <cjwatson> and I don't know what information is needed, not being a cryptsetup expert and being fairly rusty on plymouth
[02:22] <cjwatson> so it's best if somebody else looks
[02:23] <cjwatson> "fix released" would certainly be wrong since (a) chances are it's just that it happens on his system and not mine for some reason or other (b) even if it had been fixed I can't point to the fix
[02:24]  * slangasek reassigns to plymouth
[02:24] <phillw> cjwatson: has there been any testing of encrytpted in ubuntu
[02:24] <cjwatson> slangasek: right :)
[02:24] <slangasek> phillw: I test it every time I reboot
[02:24] <cjwatson> phillw: it's on the routine test cases so it's tested at every milestone
[02:26] <cjwatson> but it's important to be aware that this kind of thing can easily be hardware-specific
[02:26] <phillw> cjwatson: slangasek in which case, how do these bugs arrive? Please do understand that I am really new & trying to learn
[02:27] <cjwatson> even successful testing doesn't immunise you from hardware-specific problems
[02:27] <cjwatson> or the category of problem described by http://en.wikipedia.org/wiki/Race_condition
[02:28] <stgraber> which sadly makes for the majority of these annoying bugs...
[02:29] <cjwatson> plymouth (the software that handles input/output multiplexing at boot, and also displays a splash screen) takes some quite different code paths dependent on the graphics card, for instance, and is also more prone than most to delicate race conditions that take ages to track down
[02:29] <phillw> cjwatson: I saw that as bug earlier, I'm gradually getting used to this weird and wonderful language you speak in :)
[02:32] <phillw> I'm pretty much barred from speaking about the installing of 'strict' GTK3 rules. But I am getting better to understand that #shit happens#
[02:33] <phillw> how you guys do this? WOW
[02:35] <cjwatson> http://people.canonical.com/~ubuntu-archive/pending-sru.html <- "The following packages have an equal or higher version in the release pocket and should be removed from -proposed:"
[02:35] <cjwatson> whee
[02:35] <cjwatson> (hand-checked and processed)
[02:36] <cjwatson> I do wish lp-remove-package.py would tell you about the pocket it's removing from in its output.  Always gives me heartattacks.
[02:38]  * skaet just goes to look at the link.  :)
[02:39] <skaet> looking good cjwatson.  :)
[02:40]  * skaet --> evening dog walk,  biab
[02:50] <cjwatson> Is anyone with cocoplum access still using any of the old crap in ~lp_archive/python/?
[02:51] <cjwatson> I'm not seeing anything likely elsewhere in ~lp_archive/, and I strongly suspect it's all been superseded by launchpadlib-based stuff in ubuntu-archive-tools.
[02:51] <slangasek> not me
[02:52] <cjwatson> I'll nuke it tomorrow morning unless somebody shouts that they care.  Speak now or forever hold your peace.
[03:04] <infinity> cjwatson: Not I.
[03:06] <infinity> cjwatson: Also, regarding lp-remove-package.py heart attacks, I could have sworn someone filed a bug about better verbosity, like, 6 years ago.  But I can't find it.
[03:57] <skaet> pitti, infinity,  only images left to come off the builder are wubi, and ubuntu mx5/ac100 kubuntu omap4.   pad has been updated.
[03:57] <skaet> good night.
[03:57]  * skaet --> zzz
[04:17] <infinity> stgraber: queubot's seeing double.
[04:17] <phillw> infinity: please tell me that is a joke.....
[04:17] <infinity> stgraber: (See all the double entries for mosh)
[04:18] <infinity> stgraber: Or, triple...
[05:10] <pitti> Good morning
[05:30] <pgraner> morning pitti
[06:04]  * pitti accepts the -proposed uploads
[06:10] <pgraner> ogra_, is the TI icon supposed to be in the launcher on omap4 desk top?
[06:11] <pitti> everything else in unapproved is seeded somewhere
[06:43] <didrocks> pitti: if I use mass-sync.py to sponsor some bug fixes sync from debian (and for universe), that won't bypass the freeze, isn't it?
[06:43] <pitti> didrocks: I don't know about mass-sync; why not just use syncpackage?
[06:43] <pitti> didrocks: in the past, syncs from cocoplum went straight through, without being held in unapproved
[06:44] <didrocks> pitti: can use syncpackages with -n -e options
[06:44] <didrocks> pitti: I guess it's not very important for 2 packages in universe, right?
[06:44] <pitti> didrocks: -s for sponsoring, please
[06:45] <didrocks> ah ok, yeah, seeing -s :)
[06:45] <pitti> -n/-e are for --no-lp syncs
[06:45] <didrocks> ok ;)
[06:50] <didrocks> so, it's in unapproved :)
[08:02] <ogra_> pgraner, theoretically yes, practically i dont think anyone but tobin has teswted desktop in a while and technically we planned to switch to jockey for the driver and just add a wiki page for the codecs from the PPA
[08:02] <ogra_> (in which case we dont need the icon anymore)
[08:04] <ogra_> the latest pvr drivers are sitting in NEW so they wont make beta2, the old ones in the PPA are broken, so the icon is moot anyway atm
[08:04] <ogra_> (broken for precise)
[08:42] <cjwatson> infinity,stgraber: not so much seeing double, as misrepresenting binary as source.
[08:42] <cjwatson> didrocks: mass-sync.py is decommissioned for everything except backports.  (I forget whether I actually made it not work for syncs.)
[08:45] <didrocks> cjwatson: ah, thanks for the hint, I'll have a look at the wiki page later and probably make a note if not there already
[08:48] <cjwatson> aha, I actually made mass-sync.py call syncpackage if you try.
[08:49] <cjwatson> But mass-sync's interface is kind of awkward so you might as well call syncpackage directly (preferably without --no-lp).
[08:49] <didrocks> ah, it was a trap then! :)
[08:49] <didrocks> (btw, I still have syncpakcage running and not closing the sync bug until the universe sync is approved)
[08:50]  * cjwatson will be starting work properly in a few minutes and will look then
[08:54] <ogra_> pgraner, what is the bug you tracked as bug 966858 on the tracker, LP gets me to an error page for it
[08:58] <ogra_> (and given it seems to block the panda images it would actually be good to know what it is)
[08:59] <cjwatson> didrocks: ^-
[08:59] <didrocks> cjwatson: thanks :)
[09:24]  * ogra_ wonders why oem-config always takes so long to come up ... the ac100 usually gets you to lightdm in less than 15sec from powering on ... the installer takes about 2min to start ubiquity-dm
[09:26] <cjwatson> mvo: doesn't skype-bin need to be Multi-Arch: foreign?
[09:37] <mvo> cjwatson: ups, yes you are right, let me fix this
[10:33] <infinity> cjwatson: Ahh, were those binary NEW with translations, by any chance?  stgraber was having issues making those DTRT.
[10:33] <cjwatson> infinity: Not sure at this point.
[10:34] <infinity> cjwatson: Hrm, no they're not.
[10:34] <infinity> cjwatson: So, a regression while he was trying to fix the other case, I guess. :P
[11:08] <mvo> cjwatson: I will upload a new skype in a bit with the missing multi-arch: foreign and also with a conflicts/replaces for skype-bin on older skype versions. anything else you can think of that I may have missed? is the general direction sensible for the lucid->precise skype upgrade or do you have a alternative idea that might work, the -bin package is a little bit ugly
[11:11] <cjwatson> mvo: that was all I noticed.  Also Breaks/Replaces rather than C/R I think
[11:12] <mvo> thanks!
[11:42] <pgraner> ogra_, https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/966858
[11:42] <ubot2> Launchpad bug 966858 in gnome-settings-daemon "[power]: gnome-settings-daemon crashed with SIGSEGV in gnome_rr_screen_get_dpms_mode()" [Undecided,New]
[11:43] <ogra_> pgraner, oh, i filed the same yesterday, funny that apport didnt point you to it
[11:43] <ogra_> but given it respawns fine, why did you mark the image failed ?
[11:44] <ogra_> its surely a wart (like the missing icon) and should be noted in the release notes ... but the image generally works
[11:46] <ogra_> i.e. "good ehough for a beta"
[11:46] <ogra_> *enough
[12:39] <Riddell> no images listed for testing http://iso.qa.ubuntu.com/qatracker/milestones/210/builds/14369/downloads
[12:40] <pitti> Riddell: for which milestone should that be?
[12:40] <pitti> err, image
[12:40] <pitti> http://iso.qa.ubuntu.com/qatracker/milestones/210/builds has quite a lot
[12:41] <Riddell> pitti: for ubuntu desktop beta 2 armhf+omap4
[12:42] <cjwatson> Mm, I think it just doesn't know the URLs.
[12:42] <Riddell> I think so too
[12:43] <cjwatson> should be http://cdimage.ubuntu.com/daily-preinstalled/20120328/precise-preinstalled-desktop-armhf+omap4.img.gz
[12:43]  * Riddell eyes up pitti as a member of the ubuntu desktop team who has powers to add them
[12:44] <cjwatson> He does?  It needs DB access.
[12:44] <cjwatson> I think.
[12:44] <Riddell> no it's all improved
[12:44] <Riddell> just needs admin access to that site
[12:44] <cjwatson> oh maybe so, I was logged out
[12:45] <cjwatson> I can do it then
[12:45] <pitti> looking
[12:46] <cjwatson> pitti: I'm on it, unless you want to
[12:46] <pitti> cjwatson: ah, thanks
[12:46] <pitti> I just found where to set that
[12:46] <pitti> so, please go ahead
[12:51] <cjwatson> OK, it's pretty cumbersome and manual, but done for armhf+{omap4,omap}
[13:01] <Riddell> is a release sprint happening this release?  how do I get invited along?
[13:03] <cjwatson> https://wiki.canonical.com/UbuntuEngineering/Sprints/PreciseReleaseSprint
[13:08] <Riddell> cjwatson: lovely, and I get invited along by just putting my name on there and magically a hotel room will be allocated to me?
[13:10] <pgraner> ogra_, yea I agree
[13:11] <cjwatson> Riddell: I don't know, you should probably ask Kate
[13:12] <Riddell> skaet: hello
[13:27]  * phillw sulks ... not allowed to even view https://wiki.canonical.com/UbuntuEngineering/Sprints/PreciseReleaseSprint
[13:28] <phillw> btw, was last night / this morning the final respin for beta 2 RC?
[13:28] <Laney> that's because it contains next week's lottery numbers
[13:30] <phillw> Laney: I recall a 0 day horror that had the devs attending the release party all locked up and respinning whilst the forum went into melt down with people screaming "Why is not released yet!".... I'll give it a miss :P
[13:53] <Daviey> cjwatson: What was the upload from a few days ago for inclusion ?
[13:54] <Daviey> from roaksox ?
[13:59] <skaet> Riddell,  release sprint participation in london is being limited explicitly,  we're looking into setting up a G+ hangout for those not able to be there in person.
[14:00] <cjwatson> Daviey: powernapd
[14:02] <Daviey> ah
[14:02] <Daviey> I didn't think it was critical for beta-2 TBH.. but ok.
[14:03] <cjwatson> That's fine, then just bump the bug milestone
[14:03] <Riddell> phillw: it held next door to MI5 and opposite MI6 so it's pretty tightly controlled
[14:04] <Riddell> phillw: there have been respins, we won't know if they're final or not until they are all tested to work correctly
[14:17] <apw> skaet, we have a further (single) report of issues with aspm on the latest kernel.  after long discussions we think it is better to leave things as they are and make sure its documented in the notes.  this is based on the belief this may well be a bios issue, and that there should be work arounds we can document.  therefore we would much prefer to leave the code in to find out if there any other
[14:17] <apw> affected machines with a note in the release notes; all this for B2, using the results of that to make an informed decision for release
[14:19] <skaet> apw,  please add the release note to the TechnicalOverview, along with bug number.   if there are workarounds available, release note should be ok.   We're getting to late to do another respin unless its a kitten killer.
[14:20] <apw> skaet, yeah that was my feeling
[14:22] <skaet> apw,  if things change as the testing emerges,  flag me please.
[14:22] <apw> skaet, ack
[14:26] <phillw> Riddell: thanks, we're just waiting on powerppc for lubuntu to be tested and we are good to go :)
[14:28] <skaet> jibel,  any concerns on your list from the testing so far,  other than the kernel bug ^ referenced?
[14:30] <skaet> pitti,  cjwatson - pad is looking quiet,  any concern areas showing up on your radars?
[14:30] <pitti> not from here
[14:31]  * skaet hopes the trend continues.... :)
[14:31] <skaet> thanks
[14:32] <cjwatson> all quiet on the western front so far
[14:32] <skaet> phillw,  lubuntu test team rocks!   just saw that almost all the images have been tested now. sweet.  :)
[14:32] <jibel> skaet, nothing from me.
[14:32] <jibel> testing mac now
[14:33] <skaet> thanks jibel.  :)
[14:36] <highvoltage> hi, shouldn't https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/913731 be a release critical bug?
[14:36] <ubot2> Launchpad bug 913731 in plymouth "non-X installs still have vt.handoff=7" [High,Confirmed]
[14:36] <highvoltage> I just had a colleague tell me that ubuntu server installations have been broken for the last few weeks because he doesn't get a login prompt, and it's reasonable to expect that many, many ubuntu users will think the same when installing it
[14:51] <skaet> Daviey,  ^ thoughts?
[14:55] <ogra_> Riddell, did you get to test the panda image ?
[14:55] <Daviey> looking
[14:57] <Daviey> skaet: It's something i'm happy to release note for b2.. I don't think it's a blocker.  I'd surprised I hadn't seen it myself TBH. :)
[14:57] <Riddell> ogra_: yep
[14:57] <ogra_> Riddell, aaaaand ?
[14:57] <skaet> Daviey,  thanks.  Release note it is.
[14:57] <Daviey> cjwatson: I see bug 913731 is assigned to foundations, is it on your hit list for release?
[14:57] <ubot2> Launchpad bug 913731 in plymouth "non-X installs still have vt.handoff=7" [High,Confirmed] https://launchpad.net/bugs/913731
[14:57] <Riddell> ogra_: same bug in the graphics driver bug 961133
[14:57] <ubot2> Launchpad bug 961133 in linux "No video output from Ubuntu Desktop ARM Images on my Pandaboard to my DVI monitor" [Medium,Confirmed] https://launchpad.net/bugs/961133
[14:58] <Riddell> found a new monitor where it works using the other port at 640x480
[14:58] <doko> infinity, test rebuild started
[14:58] <ogra_> Riddell, ohh, intresting, can you note that on the bug and also talk to robclark in #ubuntu-arm ot #pandaboard ?
[14:59] <Riddell> ogra_: bug is updated, I can try pinging rob
[15:00] <skaet> highvoltage,  could you take a pass at updating the https://wiki.ubuntu.com/PrecisePangolin/TechnicalOverview for Edubuntu?
[15:01] <cjwatson> Daviey: hmm, not right now, slangasek, what do you think?
[15:01] <cjwatson> slangasek: (913731)
[15:02] <highvoltage> skaet: will do
[15:02] <Daviey> It's not critical but a nicety IMO.
[15:02] <skaet> thanks!  :)
[15:03] <stgraber> highvoltage: I'm currently in a meeting but I can have a look at the TechnicalOverview in an hour or so if you don't have time to look at it now
[15:04] <highvoltage> stgraber: thanks, I'll try to take a stab at it in the meantime. is it confirmed that we should include all the changes since the beginning of the cycle?
[15:05] <stgraber> highvoltage: for Edubuntu, I'd prefer we do that yes, maybe hilight changes from beta1 but IIRC the only change is translation update and bugfix releases of epoptes and ltsp
[15:07] <pabelanger> Morning, I just created a FFe (bug 967195) to help resolve bug 965484.  If a bug manager would be kind enough to help triage it, thanks
[15:07] <ubot2> Launchpad bug 967195 in ruby-rack "FFe: Sync ruby-rack 1.4.0-1 (universe) from Debian wheezy (main)" [Undecided,New] https://launchpad.net/bugs/967195
[15:07] <ubot2> Launchpad bug 965484 in redmine "redmine : Depends: ruby-rack (>= 1.4.0) but 1.3.5-1 is to be installed " [High,Triaged] https://launchpad.net/bugs/965484
[15:12] <Riddell> pabelanger: bug triagers I think are in #ubuntu-qt and universe packages are maintained by MOTU who I think are in #ubuntu-motu
[15:13] <ogra_> Riddell, yeah, that would help for sure, rob maintains the graphics drivers for the panda (sorry in meetings atm)
[15:13] <pabelanger> Riddell: right, but I though I needed somebody from ubuntu-release to first triage the FFe, before having somebody in MOTU sponsor the sync process
[15:15] <Riddell> pabelanger: ah for the FFe yes that needs approval from ubuntu-release, but it'll be much easier if a MOTU has already commented on the bug "yes this is good we want it"
[15:16] <pabelanger> Riddell: okay, let me get that for you
[15:50] <infinity> stgraber: Did you look into queubot's confusion about binary NEW from last night?
[15:51] <infinity> stgraber: The queue entries that confused it (mosh, on a few arches) are still in oneiric-backports/new.
[15:51] <stgraber> infinity: nope, I saw it in the backlog but haven't tried fixing it yet. I'm currently looking into an LTSP bug, then have the edubuntu techoverview to look at and the perf review stuff to get done (now that HR fixed my account). So I'll look at the bot this afternoon/evening
[15:52] <infinity> stgraber: Oh, yeah, not a priority by any means, was just curious if you caught the backscroll.
[15:59] <Daviey> skaet: Would like to do a server rebuild in ~2 hours.  If you are happy, I'll make sure all testcases are satisfied on the new build.
[16:01] <pitti> skaet: I'm off for TKD/dinner, etc.; will check back in after it to check for any new fires, but it seems rather quiet ATM
[16:02] <hggdh> Daviey: We, the sufferers, will also test it ;-)
[16:05] <Daviey> hggdh: What would we do without you?
[16:05] <ogra_> suffer yourself indeed :)
[16:05] <skaet> thanks pitti.
[16:06] <skaet> Daviey,  ok for the respin if it helps.
[16:31] <phillw> guys, a bit of bad news :( bug 967257
[16:31] <ubot2> Launchpad bug 967257 in lubuntu-meta "PPC Install CD from 28 Mar does not boot" [Undecided,New] https://launchpad.net/bugs/967257
[16:32] <phillw> Lars is a good tester for mac stuff. If he says it's broken, it's broken.
[16:32] <cjwatson> Has he tested any other powerpc images successfully?
[16:33] <cjwatson> I'd like to know whether this is Lubuntu-specific for some reason.
[16:33] <cjwatson> Or any images from earlier?
[16:33] <cjwatson> I can have a look in qemu, but the download will take the best part of an hour and I suspect I'll have finished for the day by then.
[16:34] <cjwatson> So any narrowing down of where/when things broke would be helpful.
[16:36] <phillw> I've asked him. We did have working isos from ppc before.
[16:36] <infinity> I've asked for a bit more verbosity on "doesn't boot".
[16:37] <phillw> http://iso.qa.ubuntu.com/qatracker/milestones/210/builds/14310/testcases
[16:37] <slangasek> cjwatson: bug #913731> so I actually sat down at the global jam and worked through this question; we have a tentative fix for plymouth, but I'm concerned that it could be racy
[16:37] <infinity> cjwatson: Possible that the default yaboot config might be aiming at powerpc instead of powerpc-smp?  Though, I'm pretty sure I got every such case I saw.
[16:37] <ubot2> Launchpad bug 913731 in plymouth "non-X installs still have vt.handoff=7" [High,Confirmed] https://launchpad.net/bugs/913731
[16:37] <phillw> my guess would be that the iso does not get recognised as a boot CD
[16:37] <cjwatson> infinity: It's a good possibility
[16:38] <slangasek> cjwatson: i.e., that having plymouth chvt carries a non-zero risk that installs *with* a GUI will get dropped to vt1
[16:39] <cjwatson> I couldn't think of any other sensible approach, unfortunately :-/
[16:39] <slangasek> cjwatson: what about probing for a DM when deciding whether to put vt.handoff on the commandline?
[16:40] <slangasek> (though this could go pear-shaped in a number of ways and I'm not keen to make this change late in cycle either)
[16:41] <cjwatson> Possible, but I have similar reservations; in particular it's quite possible for a DM to be installed after the last call to update-grub
[16:41] <slangasek> yep
[16:41] <slangasek> or removed
[16:41] <cjwatson> I'll grant you that that approach is better than hardcoding it at install time, though
[16:42] <infinity> dpkg triggers to the rescue?
[16:42] <slangasek> possibly
[16:42] <cjwatson> Starts getting hairy
[16:42] <infinity> Combined with DMs shipping the vt.handoff bit as a config snippet, rather than grub doing it heuristically.
[16:42] <cjwatson> I don't want to introduce new triggers at this point
[16:42] <slangasek> so the race I'm seeing is as follows:
[16:43] <slangasek> - rc is nearly empty, so finishes first
[16:43] <infinity> Well, no triggers, then, just ship vt.handoff as a config snippet, and update-grub in DM postinsts.
[16:43] <slangasek> - plymouth-stop is called with JOB=rc
[16:43] <slangasek> - 'plymouth quit' runs and shuts down the splash screen
[16:43] <slangasek> - DM starts up, sees no splash running, chvt and starts X
[16:43] <slangasek> - plymouth-stop calls chvt
[16:44] <slangasek> *maybe* 'plymouth stop' could do the vt switch itself, but that also makes me nervous
[16:45] <slangasek> 'plymouth quit' I mean
[16:46] <cjwatson> Can we atomically say "chvt but only if we're on our own VT"?
[16:46] <slangasek> I don't know
[16:47] <cjwatson> And also, yes, I thought 'plymouth quit' already chvted
[16:47] <slangasek> probably not
[16:47] <cjwatson> and --retain-splash stayed on the same vt
[16:47] <slangasek> yeah, let me dig into the code then and see
[16:48] <cjwatson> Doing the chvt outside of plymouth itself does seem doomed to raciness
[17:08] <slangasek>   if (terminal->initial_vt_number == terminal->vt_number)
[17:08] <slangasek>     {
[17:08] <slangasek>       ply_trace ("can't deactivate initial VT");
[17:08] <slangasek>       return false;
[17:08] <slangasek>     }
[17:08] <slangasek> that'll be it
[17:10] <slangasek> so plymouth only handles a chvt on quit if it started on a different vt than the one it used for splash
[17:11] <slangasek> seems fixable, but definitely needs some double-checking to make sure there are no races w/ the DM
[17:16] <infinity> phillw: Grabbing the lubuntu/ppc ISOs, I'll see if I can reproduce and/or debug after an early lunch.
[17:17] <phillw> infinity: thanks, Mars is grabbing the ubuntuppc - again about an hour.
[17:20] <stgraber> can I get someone from -release to review bug 967320 before I forward to the MIR team? thanks!
[17:20] <ubot2> Launchpad bug 967320 in xcompmgr "[MIR] Please promote xcompmgr to main for LTSP" [Undecided,New] https://launchpad.net/bugs/967320
[17:20] <stgraber> ^ is actually a FFe + MIR
[17:20] <stgraber> (just updated the title now)
[17:24] <cjwatson> Huh, the Lubuntu powerpc image claims to be "3.2.0-18-powerpc"
[17:24] <cjwatson> Oh, sorry, false alarm, that's an out of date Ubuntu one
[17:25] <cjwatson> Current Lubuntu claims to be "3.2.0-20-powerpc-smp", which is correct
[17:29] <cjwatson> It's sitting at a black screen in qemu.  Hard to tell if that's just slow or hung.
[17:29]  * cjwatson tries with --verbose
[17:30] <cjwatson> But at any rate, from the bug, this isn't the same thing.
[17:41] <phillw> cjwatson: Julien did say it takes a while with qemu.
[18:06]  * skaet --> lunch,  biab
[18:29] <stgraber> skaet: I'm also out for lunch, be back in 30min, will take a look at Edubuntu's tech overview then (sorry, trying to get LTSP's bandwidth usage down and performance up took a bit longer than anticipated)
[19:06] <phillw> bug 967257 --- YAY!!!!!
[19:06] <ubot2> Launchpad bug 967257 in lubuntu-meta "PPC Install CD from 28 Mar does not boot" [Undecided,Invalid] https://launchpad.net/bugs/967257
[19:07] <phillw> As to why he had issues? ... pass. He's a darn good mac tester.
[19:14] <joshuahoover> can i get someone on the release team to give us the go/no-go on these two freeze requests: #956077 and #851810
[19:14] <joshuahoover> bug #851810 and bug #956077
[19:14] <ubot2> Launchpad bug 851810 in ubuntuone-client "[FFe] Notify clients when volumes info from server is ready" [Medium,In progress] https://launchpad.net/bugs/851810
[19:14] <ubot2> Launchpad bug 956077 in ubuntuone-control-panel/stable-3-0 "[UIFe] Colour changes for the QT control panel" [High,Fix committed] https://launchpad.net/bugs/956077
[19:18] <stgraber> highvoltage: I think I'm done drafting the Edubuntu techoverview, can you have a look and maybe improve a bit?
[19:19] <skaet> :)
[19:20] <joshuahoover> skaet: can you help with getting someone to give us the go/no-go decision on those two freeze exceptions i listed? :)
[19:22] <skaet> joshuahoover,  they won't make it for Beta2 at this point.
[19:22]  * skaet going to look at them now,  and see who else needs to review.
[19:24] <joshuahoover> skaet: right, but we'd like to have them for final if possible, especially the color change
[19:27] <skaet> joshuahoover,  problem is that the UIFe didn't land last week,  and screen shots have started being taken.
[19:27] <stgraber> skaet: if you're into FFe reviews, can you look at bug 967320? ideally I'd like xcompmgr to be pulled by the next LTSP upload (scheduled for Friday)
[19:27] <ubot2> Launchpad bug 967320 in xcompmgr "[FFe][MIR] Please promote xcompmgr to main for LTSP" [Undecided,New] https://launchpad.net/bugs/967320
[19:28] <skaet> jbicha, ^  how far along are we with the screenshots for the docs?
[19:28] <joshuahoover> skaet: i'll personally update screenshots if that would help :)
[19:28] <skaet> joshuahoover, jbicha may take you up on it ;)
[19:28] <skaet> (and yes it might well help)
[19:29] <skaet> documentation freeze is tomorrow.
[19:36] <skaet> joshuahoover, 851810 is approved as long as we can get it landed early next week.
[19:39] <skaet> joshuahoover, could you take a review pass at https://wiki.ubuntu.com/PrecisePangolin/TechnicalOverview, and make sure its got all the key changes that have happened in Ubuntu One captured?
[19:40] <joshuahoover> skaet: yep, was doing that just a bit ago...then got distracted ;)
[19:52] <skaet>  stgraber,  challenge will be getting MIR resources to look at it in time.    details in bug.
[19:54]  * micahg wonders if changing the i386 default to PAE is worth release noting (or has this been hashed already)
[19:54] <micahg> *default kernel
[19:54] <slangasek> I would think so
[19:54] <slangasek> changes in the hardware we support installing on are generally a big question; better to document that up front
[19:55]  * skaet nods
[19:57] <micahg> do you want a release notes task on a bug?
[20:03] <jbicha> joshuahoover: we don't have any screenshots of ubuntuone in the system docs
[20:04] <joshuahoover> jbicha: perfect :)
[20:04] <joshuahoover> skaet: so, bug 956077 should be ok to do since we don't do screenshots of u1 in the sys docs - sound good?
[20:04] <ubot2> Launchpad bug 956077 in ubuntuone-control-panel/stable-3-0 "[UIFe] Colour changes for the QT control panel" [High,Fix committed] https://launchpad.net/bugs/956077
[20:05] <skaet> joshuahoover, sounds good,  thanks jbicha
[20:06] <skaet> micahg,  just go into TechnicalOverview wiki page and add in some text for now.   Most of that will be transfered to formal Release Notes, next week.
[20:07] <micahg> skaet: sorry, I don't think I'm the right person to do this
[20:07]  * skaet still needs to scrub out old release notes from that project, so we have something we can work with next month.
[20:08] <jbicha> skaet: joshuahoover: yes, updating ubuntu-one isn't a problem for Precise docs
[20:12] <skaet> micahg,  ack,  I'll add a sentence after its free to edit, and we'll get apw or ogasawara to review.
[20:12] <micahg> skaet: thanks
[20:14] <Daviey> Riddell: are you editing the tech overview?
[20:15] <stgraber> Daviey: it's the other Jonathan ;) (highvoltage)
[20:15] <stgraber> Daviey: and yeah, he's still editing (we're discussing discussing some changes now in #edubuntu)
[20:15] <Daviey> ok, groovy
[20:19] <skaet> joshuahoover, yes.  have updated bug.
[20:19] <joshuahoover> thanks
[20:28] <highvoltage> stgraber: oops, yes, 10s...
[20:28] <highvoltage> (I mean Daviey)
[20:29] <highvoltage> Daviey: ok I'm out of it
[20:36] <Daviey> ta
[20:39] <skaet> Daviey,   when you're done,  let me know,  have some edits queued up.
[20:41] <Daviey> skaet: Can you go first?
[20:41] <skaet> Daviey,  ok.  going in now.
[21:10] <skaet> Daviey, am out now.   All yours.
[21:10] <Daviey> Thanks!
[21:11] <stgraber> am I the only one who gets LP oopsing every time I try to report a bug?
[21:11] <skaet> Thanks highvoltage, stgraber,  Edubuntu part looks good.
[21:12] <stgraber> I reported it in #launchpad for now but didn't get a reply yet, tried around 10 times, get an oops every time and no bug registered (otherwise it wouldn't be too bad)
[21:12] <stgraber> that's fairly annoying when doing ISO testing
[21:27] <stgraber> FYI
[21:27] <stgraber> 21:26 < spm> stgraber: we appear to have a partially broken rollout; fixing atm.
[21:27] <stgraber> always nice to have at the middle of milestone testing...
[21:28] <knome> err, does that mean rebuilding images?
[21:28] <slangasek> no
[21:28] <knome> good
[21:28] <slangasek> that only refers to launchpad having trouble accepting bug reports
[21:28]  * knome was about to get worried ;)
[21:32] <knome> btw, what's with the upgrades in the iso tracker?
[21:33] <knome> i mean, the upgrade tests
[21:34] <stgraber> knome: what about them?
[21:35] <knome> stgraber, they keep on saying "rebuilding"
[21:36] <stgraber> oh right ... not sure who did that...
[21:36] <knome> :)=
[21:37] <stgraber> jibel: why did you disable the upgrade tests?
[21:37] <stgraber> (yay for audit trail!)
[21:37] <stgraber> oh no, actually the audit trail may be wrong
[21:37]  * stgraber checks
[21:38] <stgraber> right, not even history to find these
[21:38] <stgraber> skaet: any reason to have the upgrade tests disabled?
[21:39] <skaet> stgraber,  was rebuilding the images last night,  all hadn't finished before I went zzz,  oversight.
[21:39] <skaet> should reflect for today's images.
[21:40] <stgraber> skaet: so do we reset them all or just turn back on?
[21:40] <skaet> stgraber,  reset them is best.  we do have the history.
[21:40] <stgraber> I have automated test results that finished 5 minutes ago and didn't publish because they were turned off :(
[21:40]  * skaet is sorry.  
[21:40] <stgraber> skaet: done
[21:40] <skaet> should have checked this morning on it.
[21:41] <skaet> thanks for flagging knome
[21:41] <knome> no problem
[21:42] <stgraber> skaet: oh, just noticed that we didn't have wubi upgrades, should I remove the one I just added?
[21:42] <skaet> stgraer, did the RFC go through?
[21:43] <skaet> stgraber, ^
[21:43] <stgraber> skaet: AFAIK we still have it on the media and it's still under discussion
[21:43] <stgraber> skaet: though either way, doing upgrade testing of wubi system still seems relevant even if the installer isn't on a media
[21:44] <skaet> stgraber,  probably better leave it then.
[21:44] <slangasek> the upgrade doesn't refer to the CD though, does it?
[21:44] <slangasek> right, what stgraber said
[21:51] <Daviey> stgraber: Most of the server test cases have automated testing coverage, currently someone copies passes back to the tracker by hand.  Can you provide some guidance on how to automate this?
[21:51] <Daviey> Are there apidoc's?
[21:53] <stgraber> Daviey: there isn't one yet but I can give you some examples of what's currently used for the upgrade testing (and maybe some of GrueMaster's tests, not sure if he's using the API yet)
[21:53] <jibel> stgraber, uh ? I didn't, I enabled them yesterday, they were marked for rebuild
[21:54] <GrueMaster> stgraber: I was using it for core images, and was gearing up to use it for netboot & server arm testing.  Unfortunately, my workload has changed in recent weeks so won't be implementing it.
[21:58] <stgraber> jibel: yeah, I know, I thought I had a better audit trail for these but I just had the uid of the one adding them :)
[21:58] <Daviey> stgraber / GrueMaster: Just some code snippets well probably be enough :)
[21:58] <stgraber> Daviey: http://paste.ubuntu.com/904637/
[21:58] <stgraber> that's based on GrueMaster's code with some added comments
[22:00] <GrueMaster> Yep.  Only changes I made were for product info and SSO_LOGIN stuff.
[22:00] <Daviey> stgraber: the api doesn't support trying but not save()'ing?
[22:01] <stgraber> Daviey: right but I could probably update the stagging server for that if you want
[22:02] <Daviey> stgraber: happen to know if Desktop do it by hand still?
[22:02] <Daviey> stgraber: if you have a throwaway staging server to hand, i wouldn't object :)
[22:03] <stgraber> Daviey: I think they do, though jibel asked for the exact same API example a week or two ago, so maybe that changed :)
[22:03] <stgraber> oh, apparently my staging canonistack instance was killed :(
[22:03] <infinity> Welcome to the cloud.
[22:04] <stgraber> yeah, I'll just copy my development lxc container to one of my server (you know some good old hardware in a rack ;))
[22:04] <infinity> Server-hugger. :)
[22:05] <infinity> (I *love* that that's being used as a "derogatory" term for IT people who are cloud-resistant... So silly)
[22:05] <stgraber> ;)
[22:05] <Daviey> The irony of reliance on the cloud.. Yesterday, Openstack upstream trunk was closed, because the gating process relied on cloud instances to test, their cloud provder was broke.. meaning no code could land.
[22:05] <Daviey> could*
[22:06] <infinity> Can't fix the cloud without the cloud?
[22:06] <Daviey> yup.
[22:06] <infinity> Sort of like people who can't find their glasses without their glasses, I guess.
[22:06] <Daviey> Gut generally, if you are damaged by an instance going AWOL, your design is wrong IMO.
[22:07] <Daviey> Plannign for a rack of real hardware going away, is identical to trusting the cloud.
[22:07] <infinity> Sure, you don't "get" cloud computing if losing an instance hurts.
[22:07] <infinity> On the other hand, if you only have one instance, because you're cheap, the rules change. ;)
[22:07] <Daviey> Sadly, i would fall deeply in that category
[22:08] <stgraber> Daviey: container is crossing the atlantic now, ETA 10 minutes for the transfer + 5 minute or so to route it an IP
[22:08] <infinity> stgraber: Did you name it Titanic, to tempt fate?
[22:09] <Daviey> stgraber: I thought it was faster to copy data to an ssd, and use surface mail, than Canadian interwebs.
[22:09] <infinity> Daviey: Where did you get that strange notion?  We're not Australia.
[22:09] <knome> stgraber, http://www.youtube.com/watch?v=saalGKY7ifU <3
[22:09] <infinity> Daviey: We have the best speed/cost ratio for home users in the world, according to recent surveys.
[22:10] <Daviey> infinity: Ah, cheaper, not faster.. http://tinyurl.com/bms8jjv
[22:10] <stgraber> Daviey: I'd have agreed with you in the past but I now have a new and shiny 25/7 connection :)
[22:11] <GrueMaster> stgraber: Is there a way to unsubscribe en mass from the iso tracker?  unsubscribing from each individual image is a bit tedious.
[22:11] <infinity> Daviey: As a personal data point, I recently *downgraded* my service to 100/10, because 250/15 wasn't worth it.
[22:11] <Daviey> O_o
[22:12]  * micahg would love 10Mbit up
[22:12] <infinity> Daviey: Also, that particular jpeg was a protest against usage based billing that didn't happen.
[22:13]  * micahg has 25/2 ATM
[22:13] <infinity> We may not be as awesome as South Korea's fiber-to-every-bedroom (though they do pay for the priviledge), but, like I said, we're not Australia. :P
[22:13] <stgraber> Daviey: I also recently got native IPv6 giving me a nice 10 hops route to my server in Germany (native-v6 to native-v6!)
[22:14] <infinity> Now, if only we could get rid of our pesky government...
[22:15] <stgraber> infinity: lucky you, 25/7 is the maximum I can get here (with a decent upload) and not have quotas, without having fiber installed and pay thousand of dollars in setup fees
[22:15] <stgraber> though I run most of my stuff on a server with gigabit connectivity so it's not too bad
[22:15] <infinity> stgraber: Québec's always been a backward place. ;)
[22:16] <infinity> stgraber: And yeah, I run all my critical stuff on a server in San Jose with GigE.
[22:16] <stgraber> infinity: I won't comment ;) I know mdeslaur and some others may be watching
[22:16] <infinity> (Which seems silly, with this much bandwidth at home, but old habits die hard, and it's nice to have off-site backups)
[22:16] <infinity> And by "critical stuff", I mean screen sessions with irssi in them.  Obviously.
[22:17] <stgraber> infinity: to be honest, I probably would be able to get much faster internet, close to what you have if I was living in Montreal, or at least a bit closer to Montreal
[22:18] <infinity> stgraber: Yeah, I'd assume Videotron offers something along these lines.
[22:18] <infinity> stgraber: If not, they need to pull their socks up.
[22:20] <stgraber> infinity: AFAIK the best you can get with videotron is 120/20 but with a total cap of 500GB, so completely useless for me
[22:20] <stgraber> infinity: as any extra GB costs $1.5
[22:20]  * knome fortunately doesn't need >500GB upload bandwidth :)
[22:21] <ajmitch> stgraber: gee, poor you :P
[22:21] <stgraber> I don't use "that" much, between highvoltage and I, we're just using around 800GB/month
[22:22] <tumbleweed> has highvoltage explained ZA pricing to you? :)
[22:22]  * ajmitch has a 20GB cap
[22:22] <stgraber> tumbleweed: yeah ;)
[22:22] <ajmitch> tumbleweed: I'm guessing it's even worse than NZ?
[22:22] <stgraber> tumbleweed: ZA-internet being his measurement unit for internet speed and price ;)
[22:23] <highvoltage> hehe
[22:23] <highvoltage> we were just talking about that a few minutes ago
[22:23] <knome> how come nerds are talking about upload speeds and prices
[22:23]  * knome doesn't understand all this fuzz ;)
[22:24] <infinity> Because we're nerds.
[22:24] <highvoltage> knome: if you don't understand it, then you probably have good upload speeds and no quotas
[22:24] <tumbleweed> ajmitch: probably fairly similar. 250ms to US, ~60 EUR pm for 20GB cap at 10Mbps
[22:24] <stgraber> the problem I have with the 500GB cap on a 120Mb/s connection is that you can go through your quota in less than 10 hours!
[22:24] <infinity> And because Daviey made disparaging comments about Canada.
[22:24] <knome> highvoltage, or no need for any better for my taste :)
[22:24] <ajmitch> tumbleweed: sounds about what I have
[22:25] <GrueMaster> stgraber: Is there a way to unsubscribe en mass from the iso tracker? unsubscribing from each individual image is a bit tedious. (repeated)
[22:26] <stgraber> GrueMaster: not yet, that page is still work-in-progress, I can remove all subscriptions for a given uid if you want though
[22:27] <GrueMaster> Yep, remove mine.  Only thing I currently care for now is netboot armhf+armadaxp (and that may change soon).
[22:28] <infinity> stgraber: Shaw has done something clever with caps (or, rather, is about to).  Instead of billing per GB (ew), or throttling (EW!), they're... Upgrading.
[22:28] <infinity> stgraber: If you go over, they just bump you to the next highest plan for the month (including the speed).
[22:28] <infinity> stgraber: First time's free.  If you do it two months in a row, you pay.
[22:28] <stgraber> qatracker=> DELETE FROM qatracker_user_subscription WHERE userid=26110;
[22:28] <stgraber> DELETE 40
[22:28] <GrueMaster> infinity: That's just sick.  How non-capitalist of them.
[22:28] <stgraber> GrueMaster: ^
[22:29] <GrueMaster> stgraber: Thanks.
[22:29] <infinity> stgraber: I guess I'll see how that plays out.  But it's curious to do service improvement instead of degradation (I lived in Australia for far too long with bandwidth-throttling on caps)
[22:29] <stgraber> infinity: that actually sounds nice, though videotron/bell are way too evil to do that, it's a lot more fun making you pay every single GB over your cap :)
[22:31] <infinity> stgraber: Yeah.  And worst case scenario here would be hitting their top plan (250/15/unlimited), which is only 130/mo, so probably way less than people are hitthing with usage-based-billing.
[22:31] <infinity> stgraber: But the cooler thing (I think) is that people who don't really care about speed THAT much can just get the cheapest plan and have it autoupgrade if they miscalculated.
[22:32] <stgraber> infinity: yeah, my guestimate was that I'd get a $950 bill from videotron with their move from unlimited to 500GB quota for business connections
[22:32] <stgraber> infinity: (instead of $80 that's)
[22:33] <stgraber> instead I moved to teksavvy a few weeks ago, for now it works fine and they are actually faster, have native v6 and offer no-cap plans
[22:35] <stgraber> Daviey: http://iso.qa.dev.stgraber.org/
[22:36] <stgraber> Daviey: sorry for the delay, forgot that now that stgraber.org is signed by DNSSEC it takes me a bit longer to update ;)
[22:38] <Daviey> stgraber: not yet working here.. i'll check in at a decent time.. thanks!
[22:38] <infinity> WFM.
[23:04] <utlemming> straber: can you add http://cloud-images.ubuntu.com/precise/20120328/ to the ISO tracker?
[23:05] <phillw> stgraber: are you in USA?
[23:06] <stgraber> phillw: canada
[23:08] <phillw> stgraber: I can ask a friend of mine who works for one of the major providers over in USA/CA to see if he can get a deal for you? He does the installs, so gets 25% off for friends.
[23:14] <phillw> utlemming: you really need to work on a wiki page for http://cloud-images.ubuntu.com/precise/20120328/ I know cloud exists, but.....
[23:22] <utlemming> phillw: you mean http://cloud.ubuntu.com/docs/ ?
[23:22] <utlemming> cloud.ubuntu.com is a great place to start
[23:26]  * phillw :-X
[23:53]  * skaet wonders if who's cleaning out the unapproved proposed queue, and thanks them. 
[23:53] <phillw> how many respins do we expect? http://pad.ubuntu.com/ubuntu-release says none. Can I announce that the RC for beta 2 on lubuntu is a "GO"?
[23:53] <phillw> skaet: ^^
[23:53] <skaet> phillw, not expecting to do another respin at this point.    Still gathering data from the testing though.
[23:54] <skaet> So far,  all we've seen we can release note (or not release the image).
[23:54] <slangasek> skaet: the only removal from unapproved I see is my own reject of a verification-failed SRU that I've just reuploaded... :)
[23:55] <phillw> skaet: when is the cut off time? I do not want to to a release note before you are all happy.
[23:55] <phillw> unlike some other 'news' sites.
[23:56] <skaet> phillw,  thank you.  :)   release decision time will be happening tomorrow at some point,  release is official when the announce goes out, so coordinate to that.
[23:56] <skaet> We'll be getting the QA reports in,  and talking to the various teams about which images they have reservations about, what looks solid.   Then figure out what's safe to ship.
[23:57] <skaet> If we don't end up respinning,  likely around end of day for Europe.
[23:58] <skaet> phillw,   please make sure all the bugs you don't want folks to stumble into are documented under Lubuntu in the known issues section.    I'll be doing a pass as well.
[23:58] <skaet> but more contributing to it,  better its going to get.
[23:58] <phillw> skaet: but dooooo, pleeaaseee let me know if lubuntu has passed for beta 2? The lads are really chewing at my neack!
[23:58] <phillw> s/neack/neck
[23:59] <skaet> phillw,  I'll ping you as soon as soon as I know its all looking good.   Its fairly likely that the images you have right now will be the ones to go out with.
[23:59] <skaet> :)