[00:02] stgraber: If you haven't already, can you work the tracker magic to give me a milestone? [00:02] jtaylor: Lemme look. [00:03] infinity: sure [00:03] jtaylor: The pytables that was promoted to -release 7 hours ago? [00:03] infinity: I'm assuming all flavours are participating this time around? [00:04] stgraber: They pretty much have to, following our old rules of "no beta, no release". [00:05] infinity: ok, done, any build done from that point on will show up in the Beta 2 milestone [00:06] stgraber: Kay. We should probably add and drop some products too... [00:07] stgraber: core, netboot, and server ppc64el probably need to exist. And unless I go and fix it in a real hurry, server omap* are both a lost cause. [00:08] * infinity goes to disable both of those right now so we stop trying and failing to build them. If I find the time to fix them (and if anyone cares), we can put them back later. [00:10] Oh, Laney did that on the 17th. :) [00:10] infinity: the current manifest is http://iso.qa.ubuntu.com/admin/config/services/qatracker/series/42/manifest [00:11] let me know what we're missing and I'll check if we have it in stock already and it just needs adding or if I need to create a new product entry [00:12] stgraber: As above. Need ppc64el netboot, server, core. [00:12] stgraber: And need to drop server armhf+omap and server armhf+omap4 [00:14] ok, dropped the two omaps, ppc64el will need some more work as I need to create product entries for those [00:15] Alright, omap server images purged from the mirrors and crontab on manual. [00:15] Erm, cron slightly too manual... [00:16] * infinity reenables self-rebuilds. [00:16] stgraber: Do we still want system-image imports running? [00:17] * infinity guesses so. [00:17] yeah, don't touch system-image [00:26] Wait... [00:26] Is the trusty NEW queue really empty because we caught up, or did stgraber's bot go crazy and accept everything? [00:27] what's wrong with accepting everything once in a while during a full freeze and a LTS release? [00:27] Heh. [00:27] And, no, we must have actually caught up, the bot's not even running yet. [00:27] Sweet. [00:28] * infinity turns on the bot. [00:28] don't worry, we'll provide you something to work on shortly ;) [00:28] Err... [00:28] * infinity turns on the bot AFTER changing the default series. [00:29] s/hardy/trusty/ [00:29] infinity: core, netboot and server ppc64el added to the tracker and manifest [00:29] stgraber: Lovely, thanks. [00:29] infinity: so if nobody messed up the cdimage code, they should magically auto-publish [00:29] stgraber: That auto-accept bot would be a lot less dangerous, if it acted on the current devel series instead of having SERIES hardcoded. ;) [00:29] * knome bows for all the hard work the release team does [00:30] and for a bit more :) [00:30] well, netboot is triggered from a cron on my server which I'll manually trigger now [00:30] * infinity was --><-- this close to auto-accepting the saucy queue. [00:30] infinity: isn't it limited to the release pocket? [00:30] stgraber: No, proposed... [00:30] oh yeah, that could be dangerous :) [00:30] stgraber: So, it would happily accept all the pending SRUs for a series. ;) [00:31] knome: Meh, this time of year, the hard work is all up to people like you. [00:31] huhu, don't tell me [00:31] knome: I just have to write emails and herd cats (neither of which I enjoy), but you have to test, test, test. [00:31] i still have to squeeze out the last drips of non-commercial creativity juice to the xubuntu wallpaper [00:31] and the paperwork related to that ;) [00:32] infinity: I think I remember why I had to do that... [00:32] >>> list(lp.distributions['ubuntu'].getDevelopmentSeries()) [00:32] [] [00:32] Oh look, and there's the bot earning its keep already. \o/ [00:32] Yay for it not bitrotting. [00:32] something to do with a frozen series not being considered as development or something [00:32] stgraber: I believe there's a different call that works for frozen too. [00:33] # We care about the development series by defaults. [00:33] if hasattr(options, 'suite'): [00:33] ubuntu = options.launchpad.distributions['ubuntu'] [00:33] options.suite = ubuntu.current_series.name + '-proposed' [00:33] ^-- From some other random script... [00:35] >>> print lp.distributions['ubuntu'].current_series.name [00:35] trusty [00:35] stgraber: ^ [00:35] ah, that's good. Feel free to just commit the fix then :) [02:34] Hello, i send a debdiff for this bug https://bugs.launchpad.net/bugs/1251849 may apply for a SRU? [02:34] Launchpad bug 1251849 in xserver-xorg-video-openchrome (Ubuntu) "[VX820] Regression: driver does not work on Samsung NC20" [High,Confirmed] === Ursinha is now known as Ursinha-afk === Ursinha-afk is now known as Ursinha [04:02] No more than a few hours after I freeze the archive, I upload d-i, wait an hour, and wonder why it's not been built. [04:02] I'm SMRT today. [04:03] ah I guess you want that one for beta 2? [04:03] stgraber: Yeah, the latest kernel had d-i specific changes to it, I'd like it in the builds. [04:04] Figured I'd let lightdm in for free, since it'll happen in parallel. [04:06] yeah, that's fine, nobody tried to spin candidate images anyway yet [04:07] No, I had planned to spin them after d-i built. :P [04:07] So, if I can get Qscintalla2 for Qt5 building, would it be reasonable to let it in for trusty assuming I'm careful to make sure the existing Qt4 stuff isn't affected? [04:07] infinity: ah, you're actually doing an initial mass build for everyone? last time around I just told them "we're ready, press the button when you are" and didn't do anything myself :) [04:08] infinity is full service. [04:08] ScottK: Like, a new library/soname for qt5, but still also build the qt4 libs? [04:09] Yes. [04:09] ScottK: That would seem entirely reasonable. It's not really a new "feature", per se, if the existing stuff is untouched. [04:09] (Much like new source packages aren't a new feature, until someone wants to depend on them or seed them) [04:10] The tricky part here is upstream used the same name for the Qt4 and Qt5 libs, but did leave at least some plumbing in place for renaming and didn't suggest I not do it when I asked. [04:10] stgraber: In retrospect, that would have been smarter, but my email did claim I'd do the first spin for everyone. I should probably stick by that. [04:10] So I don't know if it'll be done or not. [04:11] ScottK: So, it would be nice if you schooled upstream about them needing to be a new SONAME if built against a different Qt. [04:11] ScottK: Unless they mask that very, very well in their ABI and the Qt4 and Qt5 builds really are compatible... [04:11] We discussed it. [04:11] No, they aren't and they know it. [04:11] (If that's the case, then I'd go for a temp SONAME for now for playtime, and then if you move wholesale later, do some clever renames and replaces) [04:12] Ahh, kay. Yeah, if they're incompatible, get them to fix their shit. :P [04:12] But for now, you could just tack a modifier on the end or something. [04:12] When they sort out how to do it right, you can always rename and rebuild rdeps if there are any. [04:13] There is allegedly some qmake magic I can do that will make it all wonderful. [04:13] As I say, this may not make it. [04:13] Heh. [04:13] Well, if you get around to it, you have my approval to make it happen. [04:14] And regardless, upstream needs to get their SONAME story sorted before more people try building against Qt5 and have a sad. [04:14] Yeah. Not holding my breath. [04:20] stgraber: So, hrm. Instead of me driving this at nusakan's commandline, or clicking in a web UI, do you have a way to just blat our "rebuild 'em all" to the tracker DB? [04:20] s/our/out/ [04:27] infinity: annoyingly, nothing terribly easy... I just checked and I don't export the rebuild method over the API, so I can easily query the manifest and get all the products but I can't actually queue the rebuild over the API (I should probably fix that next cycle). [04:27] so your best bet is to get the manifest, then head to the daily milestone, tick all the things that are on the manifest and click rebuild [04:29] I think that's the most efficient way of doing it. The alternative is to just run all the things in cron but that'd waste quite a bit of livefs buildd time for stuff that don't matter for beta2 (though not as much as selecting everything on the daily page, which apparently has more things than the crontab...). [04:29] stgraber: Except that they're not all on the daily. [04:31] Meh, I'll just respin the way I usually do when I get home from my late night outing. === doko__ is now known as doko [08:02] hey, did anyone diable touch builds in the crontab by accident (seems there was no 3am build) [08:03] yeah ... re-enabling [09:08] ogra_: I had it in my build pipeline so it would happen eventually. [09:08] ogra_: I guess you'll get two now. :P [09:09] infinity, heh, k [09:09] there was just a manual build that finished 20min ago [09:09] stgraber: Hrm, I don't see server/ppc64el up there. [09:17] python3-apparmor is now in main. Could you build a set of Ubuntu Desktop images? [09:20] jibel: There are a bunch of builds in the pipe still. [09:20] jibel: Either way, indicator-sound pull all of that stuff in needs to be fixed. [09:20] s/pull/pulling/ [10:13] didrocks: I'll reject that one then [10:13] Laney: oh, you can? [10:13] oh right [10:14] I'm stupid, nice :) [10:14] Laney: so… let me redo with the real version name [10:14] The queue is saving your ass here :P [10:14] (there is a new one coming with 24.is.20 [10:14] which we can reject as well [10:14] right [10:15] rejecting that one then ^ [10:15] done [10:15] Laney: I was wondering why I didn't see it :p [10:16] the other one should be there soon (uploaded) [10:17] I've lost track. Is 12.10.2+14.04.20140324.is.12.10.2+14.04.20140320-0ubuntu1 the one I want? :P [10:18] infinity: yeah :) [10:18] Should be [10:18] diff it against that version to double check [10:18] Too late. I'm trusting the Frenchman. [10:19] infinity: hehe, once I type the correct version and don't s/24/20/, all is fine :) [10:19] http://launchpadlibrarian.net/170656407/indicator-sound_12.10.2%2B14.04.20140324-0ubuntu2_12.10.2%2B14.04.20140324.is.12.10.2%2B14.04.20140320-0ubuntu1.diff.gz FYI [10:20] cjwatson, thanks for letting that dbus# ABI revert bullshit through. banshee upstream are very... agitated... about that particular issue [10:21] agitated is an understatement [10:21] * hyperair very nearly put him on /ignore [10:21] directhex: which dbus# thing? [10:21] no memory of this [10:22] Subject: [ubuntu/trusty] dbus-sharp-legacy 0.7.0-5ubuntu1 (Accepted) [10:22] Date: Sun, 23 Mar 2014 18:53:51 -0000 [10:22] glad you're happy but wasn't me :) [10:22] I guess somebody was cleaning the NEW queue over the weekend [10:23] Yeah, no idea who the NEW hero was, but it was empty when I got to work on Monday, which made me both happy and suspicious. [10:23] well, perhaps you could gain some credit anyway: can someone bump it into main, for banshee to be able to build against it? review really shouldn't be needed, it's an old version of an already-in-main package [10:24] (also the matching dbus-sharp-glib-legacy) [10:24] directhex: Yeah, can do. Does banshee already build-dep on it? [10:24] not yet [10:24] Right, so fix that. [10:24] oh so i upload a new banshee first? [10:24] And then component-mismatches will prompt us to DTRT. [10:25] aha [10:25] okay, that's interesting [10:25] i thought it'd just ftbfs [10:25] ok. thanks guys. [10:25] hyperair, it'll ftbfs, but with a *reason*! [10:25] ... [10:27] hyperair: It will FTBFS, yes. Which is fine. Then we get told by our tools exactly which bits need promoting, and we do our monkey work, and subsequent build retries will work. [10:28] cool [10:37] hyperair: Do I have a new banshee yet? *poke, poke* [10:37] infinity: hang on, test building... [10:37] dpkg -O -i'ing... [10:37] i have my own suspicions that this won't work because libnotify has been ported to new dbus.. [10:38] hyperair: Oh, not working would be less than ideal. [10:38] infinity: that's the point when i give the finger to upstream [10:38] * hyperair sighs [10:39] oh amazing, it works! [10:39] hyperair: I hope upstream likes free fingers. [10:39] let's upload [10:39] i dunno, maybe upstream eats ladies' fingers [10:40] okay uploaded [10:40] imma go disappear from office now [10:51] directhex: Err, wait, why did you think we'd need to promote anything? [10:51] directhex: banshee is in universe. [10:51] it is? [10:51] Sure is. [10:52] Has been more or less forever, except that one cycle where it was the default player, whenever that was. [10:52] oneiric? [10:52] publishing history says natty, oneiric, precise [10:53] Well, natty oneiric, then. [10:53] precise it dropped back to universe before release. [10:55] utlemming: Despite promises, you never did seed joyent-mdata-client. Please find a home for it, or it's going to universe. :P [10:55] utlemming: (server-supported, something cloudy, whatever) [11:25] * infinity heads off to have a nap. === hggdh_ is now known as hggdh === Ursinha is now known as Ursinha-afk === Ursinha-afk is now known as Ursinha [14:16] infinity: looking into ppc64el images now [14:17] No iso.qa.ubuntu.com product found for ubuntu-server/daily/trusty-server-ppc64el; skipping. [14:17] looks like the cdimage branch needs some fixing [14:18] infinity: next time you had new builds on nusakan, don't forget etc/qa-products :) [14:18] updating now [14:20] * stgraber does a respin of core and server ppc64el to confirm they now publish fine [15:07] infinity: took two tries to get ubuntu-core ppc64el building but that's done now. [15:54] could somebody review the ffe on https://bugs.launchpad.net/indicator-power/+bug/880881 ? [15:54] Launchpad bug 880881 in indicator-power (Ubuntu) "[ffe] Power indicator does not combine multiple battery status" [Medium,In progress] [15:59] stgraber: want to review activity-log-manager to slip it into the beta as we're respinning anyway? [16:00] Laney: accepted (diffs of diffs are always so readable...) [16:00] :-) [16:01] that project is bad [16:01] it's sort of owned by us but not really managed well [16:01] like the upstream bzr branch has debian/patches in it that don't apply [16:01] anyway, cheers [16:03] Riddell: there's a kubuntu thingy in the unapproved queue [16:18] is there a reason we don't have ubuntu images as part of the final beta milestone [16:21] that was a quick review [16:23] Laney, it likely got autoaccepted by the bot since it's on none of the images [16:25] it is on a few of them, but maybe someone started reviewing before the bot noticed it ... [17:05] when are expected ubuntu desktop images? [17:10] jibel: infinity said he would spin some when he emerges [17:16] Laney: there are a few exceptions in the bot, maybe that's one of them [17:17] I see [17:17] PACKAGE_WHITELIST = ["upstart-app-launch", "click", "click-apparmor", [17:17] "apparmor-easyprof-ubuntu", "ubuntuone-credentials"] [17:18] those are from last cycle, they may need adapting if no longer relevant [17:33] if have a seed change I'd like to get into the server-ship seed for beta-2 - would one of the release team be able to ack my change please? [17:37] hi, I have a CI train merge for HUD with some crash bugfixes [17:38] I misunderstood the wiki and thought the final freeze was on Thursday [17:38] what should I do to get them landed? / is it simply too late now? [17:40] jamespage: Which change? [17:40] infinity, https://code.launchpad.net/~james-page/ubuntu-seeds/ubuntu.trusty-hv-kvp/+merge/212686 [17:41] pete-woods: It's not too late for final, might be too late for the beta. [17:41] infinity, bug 1294856 [17:41] Launchpad bug 1294856 in hv-kvp-daemon-init (Ubuntu Trusty) "Add hv-kvp-daemon-init to the server seed" [High,Triaged] https://launchpad.net/bugs/1294856 [17:42] jamespage: Guessing you haven't kept in touch with apw, who is pulling that init script into linux-cloud-tools, and we're dropping hv-kvp-daemon-init except as a transitional package) [17:42] infinity, evidently not [17:42] * jamespage sighs [17:42] Though, for now, this seed change it probably correct anyway. [17:43] utlemming, ^^ you need to be aware of that [17:43] And if people use the server CD pool for upgrades, it would still be correct for 12.04->14.04 upgrades. [17:43] So, sure, let's commit this. [17:43] infinity, ack - I'll push now [17:43] jamespage: Ta. [17:43] I'm literally minutes away from a mass respin, so... [17:43] Timing++ [17:43] infinity: okay, does that mean I need to ask to be added to the general phone FFE? (https://bugs.launchpad.net/ubuntu/+bug/1282590) [17:43] Launchpad bug 1282590 in Ubuntu "[FFe] standing freeze exception in trusty for Ubuntu Touch-specific packages" [Undecided,Confirmed] [17:43] infinity, exclude touch this time :P [17:44] infinity,done - thanks! [17:44] pete-woods: no, and bug fixes don't need FFe [17:44] balloons: There were some build/seed issues, respinning nowish. [17:44] ogra_: Yes dear. [17:44] :) [17:45] Laney: okay, thanks, is it just a matter of waiting on the archive being un-frozen then? [17:45] i.e. for final release [17:45] pete-woods: It's not going to be unfrozen, upload at will. We'll accept what we accept. [17:45] You can upload and they will get stuck in the queue for release team review [17:47] I don't have rights to upload or anything like that, I just have a message in the CI train that I'm in the UNAPPROVED queue [17:47] if that means it's already uploaded, and waiting for you guys' approval, then great [17:47] that might it got uploaded/published already I think [17:47] pete-woods, https://launchpad.net/ubuntu/trusty/+queue?queue_state=1&queue_text= [17:47] yeah, it's in there [17:48] seb128: cool, thanks for the magic URL :) [17:48] yup [17:48] oh, I forgot about syncs-in-queue. grr [17:48] Okay, world respin in progress now. [17:48] Won't touch flavours after this one. [17:48] you might want to click the merge&clean button with ignore_not_in_dist [17:48] the freeze is not going to play nice with the limited number of silos/ppas otherwise [17:49] seb128: okay, thanks, will get my manager to do that [17:49] e.g if the silos get locked down until things reach trusty release pocket [17:49] thanks [17:50] * pete-woods has no rights of his own [17:55] Erk. Wait. Is seeded-in-ubuntu just behind the times, or is click *still* being pulled in on xubuntu and kylin desktops? :/ [17:56] click is listed in http://cdimage.ubuntu.com/ubuntukylin/daily-live/20140325/trusty-desktop-i386.manifest [17:56] It parses the manifests AFAIK, so it'll show it as long as it's in the latest image [17:56] and in http://cdimage.ubuntu.com/xubuntu/daily-live/20140325/trusty-desktop-amd64.manifest [17:57] Oh. I assumed it worked on germinate output. [17:57] Parsing manifests is stale data. [17:57] Kay. [17:57] so click sure was on both images last time we built them anyway [17:57] stgraber: Yeah, I know why it *was*, and we fixed that, so I was annoyed that it still was, according to the tool that likes to use old data. :P [17:58] The name is misleading. :P [17:58] the tool really ought to be called on-ubuntu-image or something like that [17:58] Should be "was-in-an-ubuntu-iso-recently" [17:58] :) [17:59] I'd much prefer if it actually did what the name implies, told you what would be on an image based on germinate output. [17:59] But oh well. [17:59] SMOP :P [18:05] Laney: Send me obfuscated patches? [18:05] oresome === pete-woods is now known as pete-woods-afk [18:17] seb128: I think you mentioned the silos earlier. One thing to be careful about is that until a sync is accepted, the files only reside in the PPA. [18:17] seb128: so if you clear a silo before we accept it into proposed, the copy will fail when we finally do [18:17] stgraber, urg, I overlooked that [18:18] * ogra_ guesses thats something the whole landing team needs teaching about [18:18] can anyone accept the hud upload before it gets deleted? ;-) [18:19] plzkthx [18:19] stgraber, ogra_: can you communicate that to #ubuntu-ci-eng, I see that being a frequent gotcha this week, we can't keep the silos locked down until after beta or we are going to run out of silos [18:19] seb128, i'll try to remember to bring it up in tomorrows meeting [18:20] thanks [18:20] why do we need the freeze at all? [18:20] can't we just britney block things in proposed nowadays? [18:20] the release team usually wants to review all changes to main from that point on, to make sure people don't sneak in features and to make sure nothing terrible happens to the archive [18:21] unseeded packages get auto-accepted and so do those that are only in touch images, so a fair amount of the CI-Train stuff should go through fine [18:21] not so "fair amount" [18:21] we have a stack of desktop stuff going through that [18:22] including all indicators, compiz, unity, hud, unity-control-center, unity-settings-daemon [18:23] we are struggling with the silos being all allocated daily atm, and that was before the beta freeze [18:23] so we could add a massive britney block on top of the freeze so we can let those into -proposed without letting them into the release pocket [18:23] that would be nice [18:23] though I think it'd be easier for the CI folks to just not assign silos to those projects until post-beta [18:23] since things won't be landing anyway [18:23] shrug [18:23] I'm getting really annoyed at how people want to block others to work nowadays [18:24] having silos makes my job much easier [18:35] jibel / balloons: According to queuebot, you haz images. Sorry for the delay. [18:35] :-) [18:46] anyone around to move an SRU candidate to the right pocket? walinuxagent was put in precise-proposed/universe when it should have gone in precise-proposed. [18:52] utlemming: Can fix. [18:52] infinity: thank you kindly [18:53] We really need to fix that bug. [18:53] utlemming: Fixed. [18:53] (The override, not the bug) [18:53] infinity: awesomes, thansk [18:54] utlemming: Did you see my joyent ping? [18:54] infinity: er, where? [18:54] Here, last night. [18:54] 04:55 < infinity> utlemming: Despite promises, you never did seed joyent-mdata-client. Please find a home for it, or it's going to universe. :P [18:54] infinity: OH! [18:55] infintiy: I thought I didn't find it a home :/ [18:55] s/didn't/did/? [18:55] yes [18:56] infinity: I thought I did, but apparently I didn't [18:56] utlemming: Anyhow, when I NEWed it to main in November, you promised you'd seed it. You're a bit late. ;) [18:56] infintiy: indeed...I deserve the scolding [18:57] utlemming: I'm assuming server-ship or supported, but didn't really want to make the call for you. [18:58] infinity: supported is the right place [18:58] infintity: that is where hv-kvp-daemon-init lived for so long [18:58] utlemming: Want me to JFDI that for you, then? [18:59] infintiy: yeah, that would be really, really appreciated [19:00] utlemming: iz done. [19:00] stgraber: Speaking of component-mismatches, I guess you stopped using zram-config? [19:01] (at least, I think it was you pulling it into main before...) [19:01] Yeah, ltsp-client used to pull it in. [19:03] infinity: ah yeah, the recommends was dropped from Debian in the last merge. (yeah, I know it doesn't exist in Debian but we have a rather weird shared packaging :)) [19:04] stgraber: Well, my master plan to pull zram-config magic into initramfs-tools is obviously not happening this cycle, so if you still want it, you might want to bring back the dep. [19:04] (Otherwise, happy to demote... *shrug*) [19:04] infinity: apparently some of the biggest ltsp user think nbd-swap is better for ltsp's usecase, so I'm fine having it demoted to universe [19:05] (I still run it on all my machines but I don't really care whether it's in main or universe :)) [19:05] Swapping over a network? WCPGW? [19:05] I could see an argument for both in tandem. [19:05] well, when your X session and your rootfs already come from the network, you're already dead without network... [19:05] zram to get you the most use of your local RAM, and nbd-swap for when things go to hell. [19:06] stgraber: I wasn't thinking of "if the network goes away", just the speed of swapping pages over ethernet. [19:07] Though, I suppose, on an uncongested GigE network backed by a very fast server disk array, that may well be faster than swapping to local disk. [19:07] (That's a fair few ifs, though) [19:07] yeah, I agree that both would be ideal, with proper priorities set, though I didn't manage to convince someone in ltsp upstream to get that stuff done. === Ursinha is now known as Ursinha-afk === Ursinha-afk is now known as Ursinha [19:46] Any chance of getting a couple of things uploaded? I need to ask for a rebuild afterwards. Two packages - lp:ubuntustudio-live and lp:ubuntustudio-meta. ubuntustudio-meta has a fix for a critical bug 1297219 .. [19:46] Launchpad bug 1297219 in ubuntustudio-live (Ubuntu) "package selection plugin crashes when deselecting a transtional meta package" [Critical,Fix committed] https://launchpad.net/bugs/1297219 [19:47] zequence: I can have a look in a bit if no one beats me to it. [19:47] and, also, ubuntustudio-live has a plugin that allows us to select packages from our metas individuall, but the metas aren't yet updated [19:47] zequence: If you're doing the ISO testing, I don't much care if you cause yourself respins. ;) [19:47] infinity: That would be great :) [20:26] zequence: So, I'm around now. [20:27] zequence: Checking out your two branches. But what did you mean by "but the metas aren't yet updated"? [20:27] infinity, thanks, syncing now... [20:27] jibel: Sorry about the mess. Between the "hey, look, click on all the desktop CDs" thing and pitti's noticing that all the langpacks were broken, it's been a rocky start. :P [20:28] * jibel was wondering what to do tonight, now he knows :) [20:28] balloons: I haven't been paying attention to community testing so far. Do you have any indication that all our flavours are on the ball? [20:30] this flavour is :) [20:30] this one being xubuntu [20:31] infinity, yes, lubuntu and xubuntu are out and about [20:31] elfy: \o/ [20:31] infinity: you can probably tell that given I was hassling you for the url ;) [20:31] no idea on kubuntu or ubuntu gnome.. although I saw ubuntu gnome announce [20:31] balloons: Right, but literally everyone should be participating this time. myth, studio, kylin, gnome, X, K, and L. I think that's everyone... [20:31] balloons: If you have the right contacts for everyone, can you send a gentle prod out? :P [20:31] myth and studio, yea.. not heard anything from them [20:32] Well, studio is zequence above, we know he's doing things. :) [20:32] ahh indeed [20:32] balloons: we've still got that nasty keyboard issue - no-one really has any idea what to about it [20:32] myth's primary contact is... Mario? Maybe? [20:33] infinity, yea [20:33] superm1, [20:33] yeah we're in a little bit of a mess right now still [20:34] infinity: everyone keeps forgetting Edubuntu ;) but yeah, we'll have a beta2 [20:34] superm1: Well, validating to the point of "it doesn't blow up computers" is better than nothing. Something more thorough would be nice by final release, of course. :) [20:34] i'll ping the kylin guys [20:34] well it installs, but only if you install in "install only" mode [20:34] stgraber: I don't count you, since you're an Ubuntu desktop, and you basically just roll with the punches and get your testing done quietly. :P [20:34] which i guess means not blowing stuff up [20:34] tgm and I going to try to sort out a few things that are broke, but $life has been in the way lately [20:57] infinity: I've made some changes in seeds that haven't been updated in ubuntustudio-meta [20:58] the source is updated [20:58] zequence: Right, kay. So, if I review and sponsor these two, want me to refresh meta at the same time and jam it all in? [20:58] but not the uploaded package [20:58] infinity: If you refresh the meta, without uploading the source, if you like, remove two files.. [20:59] I mean, without uploading from lp:ubuntustudio-meta directly [20:59] zequence: Oh, I see, you've refreshed it in bzr. [20:59] * infinity has never seen a meta in bzr, that's a bit meta in itself. [21:00] zequence: That's a whole lot of new audio-recommends... Are those installed by default? [21:01] infinity: Yes, but with our new plugin, you can deselect stuff [21:01] infinity: Besides refreshing, I've removed two files, rtprio.py [21:01] and ubuntustudio-audio-rtprio.conf [21:02] Kay. Your call, your flavour. Just want to make sure you're fully aware of the crazy of blowing out the base install size. ;) [21:02] in the root folder [21:02] infinity: It's a DVD :) [21:02] most of it is pretty small [21:02] zequence: Sure, "it's a DVD" is an argument to ship more packages in pool/, but not necessarily to install them. :) [21:02] Also, ARGH. [21:03] git diff ; svn diff ; bzr diff. [21:03] This. This is my workflow. [21:03] Stupid fingers. [21:03] infinity: maybe http://www.greenend.org.uk/rjk/vcs/ is your kind of thing [21:03] cjwatson: Does that magically make everything one command? [21:04] I believe that's roughly the idea. Though I expect if you're doing anything non-trivial with git then it doesn't wrap that [21:04] I suspect that would just be more confusing. [21:04] At least when I screw up an innocent "diff" or "log", I then end up in the right mindset for future scary things. [21:05] Maybe you need an sl equivalent. [21:05] Like the fantastic semantic difference between "git add" and "anything-else add". [21:05] Type svn and a mallet unfolds from the back of your monitor to whack you. [21:06] I'm not sure I want to hear what cvs and rcs would do then :) [21:06] Water pistols, directed so they hit both you and your keyboard. [21:07] cjwatson: oh wow, that's awesome [21:07] p4 produces a comedy gun with a flower sticking out the end. [21:08] elmo: It doesn't really fit my brain, but I can definitely imagine it being helpful for some [21:08]