=== yofel_ is now known as yofel
[22:19] <Sarvatt> bjsnider: planning on doing a requestsync -d experimental i965-va-driver and requestsync -d experimental libva before feature freeze or does it need ubuntu changes?
[22:20] <bjsnider> unless somebody has taken the i965 package and finished it, it's not ready
[22:20] <Sarvatt> its all released in experimental
[22:20] <bjsnider> it is?
[22:20] <Sarvatt> wont get synced automatically
[22:20] <bjsnider> news to me
[22:20] <Sarvatt> yea
[22:20] <bjsnider> i'll take a look at it at some point
[22:22] <bjsnider> what's the version number?
[22:22] <Sarvatt> http://packages.debian.org/changelogs/pool/main/i/intel-vaapi-driver/intel-vaapi-driver_1.0.15-1/changelog
[22:22] <bjsnider> ok, that work was done without my knowledge, so it's probably syncable. it's not the barebones thing i sent them anymore
[22:23] <bjsnider> looks like it's relatively mature
[22:23] <bjsnider> i just gave it to siretart and he asked if anyone wanted to work on it and that's the last i heard of it
[22:23] <Sarvatt> do ya want to do the sync so your name is tied to it for later upload rights purposes or anything?
[22:24] <Sarvatt> thats why i was asking
[22:24] <Sarvatt> just has to go in before the 16th
[22:29] <Sarvatt> requestsync -d experimental i965-va-driver && requestsync -d experimental libva, attach test build logs from pbuilder to the bugs it files, its super easy
[22:30] <bjsnider> test builds in precise?
[22:32] <Sarvatt> yeah not using precise? sudo pbuilder create --distribution precise then sudo pbuilder --build foo.dsc
[22:34] <bjsnider> precise isn't very precise at this point
[22:36] <Sarvatt> of course all the effort so it shows up under https://launchpad.net/~brandonsnider/+related-software might be for naught now since its not archive admins doing the processing, most people forget to leave your attribution when they sponsor it now :P
[22:36] <RAOF> Sarvatt: Thanks for looking at that - I was thinking of pulling that across.
[22:38] <bjsnider> Sarvatt, i've got one more i was looking at, how can i check if it's part of the plan or not already?
[22:38] <Sarvatt> sec, pizzas here
[22:39] <bjsnider> there should be a "planned features" wiki like fedora's
[22:39] <bjsnider> but not on the ubuntu wiki site because that's constantly borked
[22:40] <RAOF> By and large the blueprints targeted to a release *should* be the “planned features”
[22:41] <Sarvatt> bjsnider: one more what? lots of things are planned like that but the decisions done in the teams, like we picked X versions back in november
[22:43] <bjsnider> another package i would like to have updated, but i don't know if it's already planned
[22:46] <RAOF> What package?
[22:47] <Sarvatt> yeah totally depends on the package so need to know that :)
[22:48] <RAOF> bjsnider: I think generally you should assume that if there's not already a bug about it, and it's not super-core (mesa, xorg-server), then there's probably no-one doing anything with it right now :)
[22:50] <bjsnider> you mean nobody cares about my little package?
[22:50] <RAOF> bjsnider: I don't know - what little package are you talking about? :)
[22:52] <RAOF> Also, “caring” ≠ “about to update it” ☺
[22:53] <bjsnider> gnome-mplayer/gmtk/gecko-mediaplayer
[22:55] <Sarvatt> thats fully up to date
[22:55] <Sarvatt> 1.0.5-1 in debian unstable, 1.0.5-1 in precise
[22:56] <bjsnider> coolio