[00:15] <bryceh> RAOF, SRU bug #1037483 looks ripe for pushing out for nvidia-current-updates
[08:08] <mlankhorst> morning
[08:16] <Sarvatt> mlankhorst: "morning" man :)
[08:37] <mlankhorst> bryceh/RAOF: Any objections if I nuke a bunch of renamed mesa/xorg packages from the stack and let those fall back to the old unrenamed packages?
[08:38] <mlankhorst> libosmesa6, xnest, xdmx, xephyr
[08:38] <mlankhorst> xfbdev
[08:39] <mlankhorst> libglu1 (now a separate package, so I didn't see a reason not to keep the old one from mesa 8 instead)
[08:39] <Sarvatt> if you say xvfb next yeah
[08:39] <mlankhorst> yeah
[08:40] <Sarvatt> libglu1 should be easy?
[08:40] <mlankhorst> mesa 9 no longer packages it
[08:42] <tjaalton> installed precise on my laptop next to quantal.. time to fix the intel pageflip issue there
[08:43] <Sarvatt> damn 101_copy-fb.patch not being the same as upstream, thats the only thing stopping it from being easy :)
[08:43] <mlankhorst> and osmesa6 might get a soname bump in r to osmesa8, so we could keep it unrenamed
[08:44] <tjaalton> yeah likely so
[08:44] <Sarvatt> hell you could probably keep it as osmesa.so.6, not 100% sure though
[08:44] <tjaalton> that's what we do now
[08:44] <mlankhorst> Sarvatt: either way it's something that's going to give more pain to rename than to keep the old version
[08:45] <Hanmac> my ubuntu was installed as lynx and then upgraded until i reach quantal ... (i think someday i should make an clean install again ..)
[08:45] <Sarvatt> its only bumped to 8 because fedora/suse bumped to 8 and rebuilt everything against that afaik
[08:46] <Sarvatt> but hey its whiskey o'clock here
[08:47] <mlankhorst> yeah but unless there is a reason to upgrade osmesa i feel like we should just keep the current binary
[08:47] <Sarvatt> havent heard anyone complain we kept it 6 all throughout 7.xx
[08:48] <Sarvatt> and 8.0.x
[08:48] <tjaalton> it hasn't changed
[08:48] <jcristau> the only thing you should need to upgrade from mesa is the dri drivers, really
[08:48] <mlankhorst> and egl in the future :/
[08:48] <mlankhorst> but I'm hoping at that point that nvidia dev has his proposal for a stable libGL in
[08:54] <mlankhorst> is libgl1-mesa-dri-experimental still used? seems to be empty
[08:55] <tjaalton> it is
[08:55] <tjaalton> someone wanted to have i915g there
[08:55] <mlankhorst> ~/nfs/xorg/mesa/debian$ find libgl1-mesa-dri-experimental |grep i915
[08:55] <mlankhorst> ~/nfs/xorg/mesa/debian$ 
[08:55] <tjaalton> it's not there _now_ :)
[08:56] <mlankhorst> ok can just kill it off for the renamed stack, then
[08:57] <tjaalton> yep
[09:31] <mlankhorst> are the udeb files used anywhere in ubuntu?
[09:31] <tjaalton> installer
[09:32] <tjaalton> so you need them for .2
[09:32] <mlankhorst> ok
[09:33] <Sarvatt> i dont think any x related udebs are used no
[09:33] <tjaalton> oh right
[09:33] <tjaalton> heh
[09:33] <tjaalton> forgot
[09:34] <mlankhorst> :p
[09:39] <RAOF> Yeah, we don't use X11 in debian-installer. You're good :)
[09:39] <mlankhorst> shrug I'll leave it for now, it would be more work to remove udeb  generation
[09:42] <Sarvatt> changing one line in debian/rules is easy, but why do it if its not breaking anything :P
[09:42] <mlankhorst> Sarvatt: it's the testing that's hard
[10:07] <mlankhorst> hm tempted to append originalname-lts and xorg-renamed-package, so simply having a package conflict on xorg-renamed-package would be enough to kill all renamed packages, and i wouldn't need to repeatedly sru the original xorg-server every time a new version is released
[10:07] <mlankhorst> to each provides*
[10:08] <mlankhorst> and in case of conflicts/replaces, add originalname-lts to conflicts/replaces too
[10:08] <mlankhorst> hm that part is not needed i think
[10:20] <tjaalton> give an example with real package names :)
[10:21] <mlankhorst> provides: xxv-intel, xxv-intel-lts, xorg-renamed-package, xorg-renamed-package-lts-quantal
[10:22] <tjaalton> oh, virtual packages you mean?
[10:22] <mlankhorst> yeah
[10:24] <mlankhorst> it's just because xnest and such have a versioned depends on xserver-common, which could be replaced with xserver-common >= currentversion | xserver-common-lts
[10:24] <jcristau> eww
[10:25] <mlankhorst> jcristau: well it was never going to be nice, anyway
[10:25] <mlankhorst> and if it helps upstream is going to stay untouched :)
[10:26] <jcristau> would it be possible to build xserver-common from the xorg-server-lts-foo without renaming it?
[10:27] <tjaalton> hmm probably
[10:27] <mlankhorst> then people who don't use lts-quantal would upgrade xserver-common automatically to it..
[10:27] <mlankhorst> or 'package withheld'
[10:28] <tjaalton> yeah that's the problem, and that the manpage for Xserver(1) might change :)
[10:30] <mlankhorst> well if people want to keep that package unrenamed it shouldn't be hard to keep it like that..
[10:30]  * mlankhorst doesn't care either way
[10:30] <jcristau> mlankhorst: considering the contents of that package, upgrading it shouldn't be a big deal, hopefully
[10:31] <mlankhorst> ok leaving it unrenamed it is, then
[10:31]  * mlankhorst hopes launchpad won't bork on that
[10:31] <jcristau> just an idea anyway...
[10:32] <tjaalton> should be easy to change back
[10:32] <tjaalton> if needed
[10:32]  * mlankhorst adds a rename entry for xserver-common to xserver-common :P
[10:32] <tjaalton> the only "risk" is if it's confusing to see options for Xserver that the current installed version doesn't have
[10:33] <mlankhorst> is protocol.txt backward compatible?
[10:34] <mlankhorst> seems that is being parsed at least..
[10:34] <jcristau> iirc it's read by the selinux stuff
[10:34] <jcristau> or xace anyway
[10:34] <tjaalton> dri2 was the last thing added to it in 2009
[10:34] <tjaalton> *latest
[10:35] <jcristau> yeah eamon kind of vanished
[10:35] <mlankhorst> tjaalton: dri2.5 coming up though..
[10:35] <jcristau> and then this didn't get updated
[10:35] <mlankhorst> but ok if it won't break I don't care
[10:44] <mlankhorst> now how do I get this building again
[11:28] <mlankhorst> dh_install: dri/usr/include/GL/osmesa.h exists in debian/tmp but is not installed to anywhere
[11:28] <ricotz> bjsnider, i am curious did you look into updating libva while there are some newer releases
[11:28] <mlankhorst> argh why would that get installed with --disable-osmesa
[11:28] <mlankhorst> >:(
[11:29] <tjaalton> building current mesa from quantal?
[11:34] <mlankhorst> yeah renamed
[11:34] <mlankhorst> killing off osmesa is.. fun
[11:36] <mlankhorst> hopefully fixed now
[11:36] <tjaalton> oh right
[11:38] <akheron> mlankhorst: remember me? :)
[11:38] <akheron> I changed from xubuntu to default ubuntu a while ago, and my X hasn't crashed ever since
[11:39] <Hanmac> and now you are back because your x is crashing again?
[11:39] <akheron> well, actually it has hanged a few times, but nothing similar to the old behavior of crashing twice a day
[11:39] <akheron> Hanmac: no, just to report that things are not so bad :)
[11:41]  * Hanmac knows what is bad ... currently i need to reboot more than five times each day because something breaks my output
[11:47] <mlankhorst> ok mesa builds
[11:59] <mlankhorst> # Make sure Xvfb at least starts up
[11:59] <mlankhorst> PATH=debian/tmp/main/usr/bin/:/bin:/usr/bin \
[11:59] <mlankhorst>           debian/tmp/main/usr/bin/xvfb-run -s "-screen 0 1280x1024x24 -nolisten tcp -noreset" true
[12:00] <mlankhorst> xvfb-run: error: Xvfb failed to start
[12:00] <mlankhorst> haha
[13:36] <tjaalton> hum, would it be too bold to replace -intel's 101_copy-fb.patch with the commit from upstream, for precise
[13:36] <tjaalton> would help in backporting the pageflip fixes
[13:38] <bjsnider> ricotz, in x-updates? i thought about it
[13:51] <ricotz> bjsnider, i thought more about debian, if i have seen this right, you were involved there
[13:52] <ricotz> and the git repo seems messed up and abandoned :\
[13:52] <bjsnider> oh, i didn't know that
[13:52] <bjsnider> i will check into it
[13:52] <ricotz> alright
[13:59] <Hanmac> ricotz you are looking like an expert can you look at my bug, maybe you can find the culpit? #1060987 
[14:03] <mlankhorst> Hanmac: I've told you enough that upstream needs to respond, we don't know what's wrong and can't help you :/
[14:03] <mlankhorst> asking someone else will just give you the same answer twice
[14:04] <bjsnider> ricotz, btw you can put the latest clutter-gst and totem in the ppa. i built them here and installed them and they work fine
[14:25] <ricotz> bjsnider, at least clutter-gst-2.0 is suppose to land in quantal, yeah totem should be updated there
[14:26] <ricotz> assuming you meant the gnome3 ppa ;)
[14:26] <bjsnider> of course
[14:28] <mlankhorst> oops, wonder if that's why xserver broke, probably best not to have xserver-common conflict with itself
[14:28] <ricotz> Hanmac, i mentioned it already i don't have an amd gpu here so can't test it -- and yes, most part of the driver is located in the kernel which makes it a possible source of the problem
[14:29] <Hanmac> so i am forced to sit on this vulcano until i buy newer hardware ? :'(
[14:29] <ricotz> mlankhorst, regarding nvidia hopefully this gets fixed, not that i care about unity, but maybe if 310 is out 304 gets an update too
[14:32] <ricotz> Hanmac, you can go for testing kernel 3.7 and hope it makes a difference -- http://kernel.ubuntu.com/~kernel-ppa/mainline/daily/current/
[14:34] <ricotz> and of course #radeon
[14:35]  * mlankhorst notes that a package conflicting with itself has interesting effects on apt
[14:35] <bjsnider> "not that i care about unity" hahaha rock n roll
[14:38] <Hanmac> the 3.7 (3.6 daily) did not help yet, but i may have differnt errors (currently i load the newest daily)
[14:41] <bryceh> mlankhorst, no objections here.  I was wondering if those were sufficiently client-ish that they could be omitted, so good.
[14:42] <mlankhorst> bryceh: yeah i seemed to have broken something though, even with hints it no longer did the upgrade correctly. I'm testing if it was because I made xserver-common conflict with itself.
[14:47] <mlankhorst> or at least i was taught that if you could prove 1=0 then you cna do all kinds of fun things that defy logics :)
[14:52] <bryceh> mlankhorst, I think I derived that answer on more than a couple final exams in college...
[14:53] <mlankhorst> hehe :P
[15:51] <mlankhorst> Provides: xorg-input-abi-, xorg-renamed-package, xorg-renamed-package-lts-quantal, xorg-video-abi-, xserver-xorg-core
[15:51] <mlankhorst> figures..
[15:54] <tjaalton> so how does the intel backport work on precise? I've tried the old version with the upstream copy-fb patch but it fails to start
[15:55] <tjaalton> assuming it conflicts with plymouth, or maybe needs something else backported?
[16:02] <mlankhorst> I didn't look at it yet
[16:05] <tjaalton> hmm
[16:06] <tjaalton> actually failsafe does start, lightdm doesnt'
[16:06] <mlankhorst> for some reason I have no abi any more
[16:07] <tjaalton> oh heh, of course
[16:07] <tjaalton> failsafe uses vesa
[16:07] <tjaalton> duh
[16:08] <tjaalton> and looks like it just needs the compat commit
[16:08] <tjaalton> excellent
[16:08] <mlankhorst> accidentally killed all calls
[16:15] <tjaalton> oh yes, just needed to change pScreen to match the old api
[16:15] <tjaalton> so now I should have all the pageflip backports for precise
[16:15] <mlankhorst> oh that
[16:16] <tjaalton> plus the do-copy-fb commit
[16:16] <tjaalton> backported
[16:18] <mlankhorst> well xorg-server backport fixed again, was a bit overzealous with sed
[16:47] <mlankhorst> multilib is fun and breaking things in a new way I fear :/
[16:51] <tjaalton> flip_test passes
[16:53] <tjaalton> hum, or maybe not
[16:53] <tjaalton> both versions fail the same way
[16:59] <tjaalton> or maybe it's testing plain kms
[17:39] <mlankhorst> hm this thing hates me.. :/
[17:39]  * mlankhorst wonders if it's easier to rename libglapi
[17:42] <mlankhorst> or maybe I'm just hitting a bug in apt..
[17:46] <mlankhorst> seems like it.. 32-bits libglapi-mesa-lts-quantal is unpacked, then it tells dpkg to extract 32-bits and 64-bits libgl1-mesa-glx-lts-quantal, it misses 64-bits libglapi-mesa-lts-quantal and things go boom
[17:57] <mlankhorst> blegh eod even if i started late :P
[18:32] <bryceh> hey guys, I've posted status summary of where we are with bugs across all the X packages.  I doubt I'll have time to look into those things (maybe some nvidia bugs), but wanted to highlight the problem areas in case you want to tend to some of them.  the xserver crashes in particular could use some attention.
[19:07] <bjsnider> tjaalton, you took a shot at packaging gstreamer-vaapi i see
[19:07] <tjaalton> bjsnider: some time ago
[19:07] <bjsnider> http://anonscm.debian.org/gitweb/?p=users/tjaalton-guest/gstreamer-vaapi.git;a=summary
[19:07] <tjaalton> haven't touched it since
[19:07] <bjsnider> does it build?
[19:07] <bjsnider> new release happened today i guess
[19:07] <tjaalton> someone touched it on quantal I think
[19:07] <tjaalton> so I guess it builds
[19:25] <tjaalton> sigh, where to upload -intel for precise.. all the ppa's have a newer version already :)
[19:25] <tjaalton> let's just use proposed then..
[19:29] <tjaalton> or maybe not, now the patch fails to apply.. wtf
[19:30] <tjaalton> heh, pebkac
[19:56] <tjaalton> ok pushed -intel to precise-proposed, with a detailed test case on the bug..
[19:56] <tjaalton> time for EOD
[20:03] <bryceh> heh, that email didn't take long to hit phoronix.  must be a slow news day
[20:20] <mlankhorst> bryceh: probably :P
[20:21] <mlankhorst> although i did gain some insight in the making of phoronix on xdc2012
[20:21] <bryceh> oh?
[20:21] <mlankhorst> seems tons of beer is involved in making news!
[20:24] <mlankhorst> and some of the articles are really jus ttrolling after all
[20:29] <bryceh> mlankhorst, did michael admit that?