[01:15] <Sarvatt> might just throw this all in maverick edgers depending on how much it screws up upgrading, will see after everything builds
[01:16] <RAOF> :)
[01:16] <Sarvatt> leaving lucid on 1.8.x for sure though
[01:19] <Sarvatt> got a refreshed bgnr patch that doesn't break the video abi finally so everything's fine, thats what was holding me back before because gdm was all kinds of screwed up without -nr support
[01:19] <RAOF> Sweet!
[01:23] <Sarvatt> felt like i've been in australia for the past week, had to tiptoe around a 5GB bandwidth cap on my cell phone until I got net here :D
[01:26] <RAOF> Heh.
[01:26] <RAOF> I've chewed through 70% of my cap already this month; rollover date is the 27th.
[01:26] <RAOF> That steam sale was a bit of a killer :)
[01:28] <bjsnider> luckily i'm uncapped
[01:28] <johanbr> RAOF, did you lose a bet?
[01:28] <Sarvatt> i dont think i'm capped either because i used about 20gb last week on the phone but i coulda swore it was 5gb
[01:29] <RAOF> johanbr: ?
[01:29] <johanbr> RAOF,  "I've chewed through 70% of my cap already"
[01:29] <Sarvatt> so warewolf, got some logs for me to dig through to see about your touchscreen? :)
[01:30] <johanbr> sounds like you promised to eat your hat if...
[01:30] <warewolf> Sarvatt: you're the third person I have involved in this now actually
[01:30] <warewolf> Sarvatt: and each of you seem to be chiming in when the rest are idle :)
[01:30] <Sarvatt> /var/log/Xorg.0.log, dmesg would help
[01:30] <warewolf> Sarvatt: in the mean time, enjoy my fireworks photos from yesterday: http://picasaweb.google.com/richard.harman/WashingtonDCFireworks20100704#
[01:31] <RAOF> johanbr: :P
[01:31] <warewolf> Sarvatt: actually I'm certain it isn't an X problem, it's a kernel problem.
[01:31] <warewolf> Sarvatt: the hid-mosart driver isn't "attaching" to the hardware, and making a /dev/input device.
[01:32] <warewolf> Sarvatt: want me to give you an account on the EeePC so you can mess with it directly or are you preoccupied
[01:32] <Sarvatt> that'd be perfect if you dont mind
[01:32] <RAOF> Woot!  One Q965 motherboard received.  Let's play “hunt that bug”!
[01:32] <warewolf> ok just a sec
[01:33] <warewolf> lemme find a crossover cable so I can stick this bad boy in a DMZ
[01:34] <Sarvatt> RAOF: Q965 is just a gma 950 derivative isn't it? you want a real 965!
[01:35] <Sarvatt> yeah its a GMA 3000, just a souped up gen 3
[01:35] <warewolf> GMA--
[01:35] <warewolf> poulsbo--
[01:36] <warewolf> crossover acquired
[01:36] <Sarvatt> \o/
[01:36] <RAOF> No, I want me a Q965.
[01:36] <Sarvatt> thanks richard, a lot faster if i can poke around on it :)
[01:37] <RAOF> So I can unbreak resolution changing.
[01:38] <warewolf> Sarvatt: I thought as much
[01:47] <warewolf> yaay
[04:40] <RAOF> Aww, man.  Everyone with Q965 should totally run checkbox and do the randr cycle test.
[04:41] <maco> do what now?
[04:41] <maco> is Q965 the same as i965?
[04:42] <RAOF> Nope.
[04:42] <RAOF> It's a GMA3000, not an X3000
[04:42] <RAOF> Important difference :)
[04:59] <Sarvatt> ugh what the heck, almost all drivers failed to build because of missing dependencies against xserver 1.8.99.904
[05:00] <Sarvatt> i guess xserver-xorg-dev needs to pull in libxext-dev now?
[05:03] <Sarvatt> well its a lot more widespread than that, acecad just needed libxext but everything else is failing at compile time - https://edge.launchpad.net/~sarvatt/+archive/xorg-testing/+packages?field.name_filter=&field.status_filter=published&field.series_filter=maverick
[05:03] <Sarvatt> thats a nasty looking list
[05:08] <Sarvatt> RAOF: want me to run it on 945 or do ya know its q965 specific?
[05:13] <Sarvatt> these packages all build fine locally, now i'm stumped..
[05:13] <RAOF> Sarvatt: You're welcome to try, but I'm pretty sure it's 965-specific.
[05:21] <RAOF> Looks like CFLAGS isn't getting set correctly?
[05:31] <Sarvatt> yeah none of the packages can find /usr/include/xorg
[05:32] <Sarvatt> xorg-server.pc is fine, doesn't happen locally with the same packages, hmm
[05:34] <Sarvatt> of course i dont have pbuilder set up or the space to set one up at the moment :(
[05:36] <warewolf> Sarvatt: I thought you were going to bed :P
[05:36] <Sarvatt> yeah then i saw like 50+ build failures i could upload and have ready when i wake up if i figure it out :)
[05:36]  * warewolf is having fun helping a friend figure out WTF happened and how his box got hacked into
[05:36] <warewolf> haha
[05:37] <warewolf> this is the life of a geek
[07:13] <Sarvatt> i'm stumped.. anyone have any idea why all of these packages aren't getting proper CFLAG's now when they build fine locally with the same packages? https://edge.launchpad.net/~sarvatt/+archive/xorg-testing/+packages?field.name_filter=&field.status_filter=published&field.series_filter=maverick
[07:20] <Sarvatt> everything builds fine against xserver 1.8.2, did that a few hours before trying against 1.8.99.904
[07:26] <Sarvatt> guess i should compare the build deps on the ones that actually built right and see if its one of those
[07:27] <RAOF> Mayhap.
[07:31] <RAOF> Hm.  Is it a change in xorg-macros that's breaking it?
[07:32] <Sarvatt> hmm
[07:32] <RAOF> x-x-v-intel, for example, doesn't ever explicitly AC_SUBST(XORG_CFLAGS) anywhere, but that's what it uses to pick up the include directories.
[07:32] <Sarvatt> i built the server against 1.10 then built all those drivers against 1.8.99.904, and for 1.8.2 i already had the server built and just built the libs and drivers
[07:33] <Sarvatt> so could be that
[07:33] <Sarvatt> lessee what changed between 1.8.0 and 1.10.0
[07:34] <Sarvatt> just doc stuff
[07:35] <Sarvatt> xorg-server.pc added this in 1.8.99.904 - Requires.private: xproto >= 7.0.17 randrproto >= 1.2.99.3 renderproto >= 0.11 xextproto >= 7.0.99.3 inputproto >= 1.9.99.902 kbproto >= 1.0.3 fontsproto videoproto dri2proto >= 2.3 xineramaproto
[07:36] <Sarvatt> its gotta be some build dep needing to be added because it builds fine locally just not on a ppa or pbuilder
[07:47] <Sarvatt> hmm
[07:47] <Sarvatt> everything that built right has sdkdir=`$PKG_CONFIG --variable=sdkdir xorg-server` in configure.ac
[07:48] <Sarvatt> darn nope, just hadn't finished grepping yet
[07:50] <RAOF> Sarvatt: xserver-xorg-dev is missing a depends on xineramaproto
[07:51] <RAOF> At least, as of my reading of the package and the xorg-server.pc file.
[07:52] <Sarvatt> ahhhhhhhh i ran into that problem a few weeks ago too, lets see if that fixes it
[07:52] <Sarvatt> thanks so much RAOF 
[07:53] <RAOF> No problem whatsoever.  I'd like to update to 1.8.99.904 in Maverick/experimental soon, so you're helping tremendously.
[07:56] <Sarvatt> bingo!
[07:58] <Sarvatt> that's all it was
[07:58] <Sarvatt> sheesh, can't thank you enough, i should have been asleep 4 hours ago :)
[07:59] <Sarvatt> now to hit rebuild 100 times after the new server builds
[08:02]  * Sarvatt ponders jumping to japan and just reuploading everything again instead
[08:42] <RAOF> Sarvatt: Would you like *me* to hit those rebuild buttons?
[08:45] <Sarvatt> could just copy it all to edgers :)
[08:47] <Sarvatt> cant hit rebuild until the server is closer to building, was 4 hours last i looked
[08:47] <Sarvatt> and its in a personal ppa so ya cant hit rebuild
[08:50] <Sarvatt> tormod didn't want a crackier ppa on edgers team than edgers and would rather me put the crack in there but i get 100+ emails when favicons go transparent because of cairo so i'm a little conservative in there and build big things in my ppa first... :D
[08:51] <Sarvatt> its good to go for edgers maverick though, just need a few drivers not in pkg-xorg like tslib
[09:38] <Sarvatt> sheesh, i386 queue time goes up every time i look.. amd64 is all rebuilding now though
[09:57] <seb128> Sarvatt, it's a queue of langpack builds but it seems to have lower priority than uploads so should not be an issue
[17:38] <Sarvatt> so wacom needs updating, and acecad/citron don't build against 1.8.99.904 but otherwise everything is good
[17:40] <Sarvatt> of course this is with everything from git, will probably run into problems using released versions of things
[18:19] <Sarvatt> ah hell, binary copied xserver and it hadn't been published yet when the drivers started building
[18:23] <bryceh> heya Sarvatt, welcome back!
[19:31] <Sarvatt> heyo bryceh! sorry had to run out for a bit
[20:13] <Sarvatt> darnit, can't copy nvidia-graphics-drivers from maverick to x-updates because maverick's is using a different orig.tar.gz
[20:14] <Sarvatt> deleted it from x-updates a day ago and its still saying the orig.tar.gz exists in the ppa even though it doesnt
[20:15] <Sarvatt> looks like the package makes its own orig.tar.gz now too so i cant just make a debian native without one to get around it, and changing the version to something like 256.35+xup1 makes it try to look for .run's with that name
[20:20] <Sarvatt> maybe it'll let me upload just not copy
[20:22] <bryceh> could be
[20:22] <bryceh> if it's totally stuck, put a request in via Answers for someone to take a loo
[20:23] <bryceh> +k
[20:44] <bjsnider> Sarvatt, just repackage it
[20:46] <Sarvatt> i've been trying
[20:46] <Sarvatt> its all screwed up now
[20:46] <Sarvatt> Rejected:
[20:46] <Sarvatt> File nvidia-graphics-drivers_256.35.orig.tar.gz already exists in Primary Archive for Ubuntu, but uploaded version has different contents
[20:46] <Sarvatt> primary archive for ubuntu?
[20:47] <bjsnider> for that series
[20:47] <Sarvatt> lucid
[20:47] <bjsnider> so install the source package, then do debuild -S -sd and upload
[20:48] <Sarvatt> it got rejected, i did that as well
[20:48] <Sarvatt> oh maybe i packaged that for maverick by mistake that time
[20:48] <Sarvatt> nope
[20:48] <Sarvatt> Version: 256.35-0ubuntu0sarvatt2~lucid
[20:48] <Sarvatt> Distribution: lucid
[20:50] <bjsnider> i didn't know hte 256 driver had been officially packaged for lucid
[20:51] <Sarvatt> i think its just screwed because I tried copying it and it failed
[20:51] <Sarvatt> checking changes
[20:51] <bjsnider> you tried copying it from maverick to lucid?
[20:51] <Sarvatt> yeah
[20:51] <Sarvatt> rebuild copying
[20:52] <bjsnider> from official maverick to ppa lucid?
[20:52] <Sarvatt> yeah i do it all the time
[20:52] <bjsnider> so why did it fail?
[20:52] <Sarvatt> https://edge.launchpad.net/ubuntu/+archive/primary/+copy-packages?field.name_filter=nvidia&field.status_filter=published&field.series_filter=maverick
[20:52] <Sarvatt> it says the orig.tar.gz is already exists in the PPA
[20:52] <bjsnider> it does
[20:52] <Sarvatt> but it doesn't, and its not on any of the sources lists
[20:52] <bjsnider> you put it there
[20:52] <Sarvatt> i deleted it 24 hours ago
[20:53] <Sarvatt> so i could copy the official one since its different
[20:53] <bjsnider> it takes a week for the deleted stuff to actually be deleted
[20:53] <Sarvatt> since when?
[20:53] <bjsnider> i dunno, ever i guess
[20:53] <Sarvatt> its not on the ppa or in any of the sources when i look at the lists directly
[20:53] <Sarvatt> it only took about 2 hours a few weeks ago
[20:53] <bigjools> Hi - you can't overwrite file versions with different contents - ever.
[20:53] <bjsnider> yeah, it's removed from the list
[20:54] <bjsnider> that's right too
[20:54] <bjsnider> there can only every be one source package with that unique name
[20:54] <bjsnider> you can never replace it
[20:54]  * bigjools is the lead dev for Soyuz
[20:55] <Sarvatt> it's worked in the past, but i've never done it while copying, but i am positive i have done it in the past many times with strictly uploaded sources
[20:55] <bjsnider> bigjools, so what does he do, upload the one he deleted again?
[20:55] <bigjools> it's impossible to overwrite a file with different contents, you've never done it I can assure you :)
[20:56] <bigjools> the easiest thing is to bump the version if you can and upload it again
[20:56] <bjsnider> he cannot bump the version and keep it accurate
[20:56] <bigjools> I've never tried uploading a deleted one again, it might work
[20:56] <bjsnider> he'd have to change the resulting package name by adding a dash somewhere after the .35
[20:56] <Sarvatt> thats what I mean I've done in the past before many times
[20:57] <Sarvatt> but yeah I can't alter the version on this package in a way that it'll accept, crap :(
[20:57] <bigjools> darn
[20:57] <bjsnider> Sarvatt, try uploading the source package you originally created for the ppa
[20:57] <bjsnider> not the maverick one
[20:57] <Sarvatt> i did :(
[20:57] <bjsnider> it rejected it?
[20:57] <Sarvatt> it's stuck saying it exists in primary archive for ubuntu
[20:58] <bjsnider> ok, when is nvidia releasing a new driver?
[20:58] <Sarvatt> and contents different
[20:58] <bjsnider> now would be a good time
[20:58] <Sarvatt> yeah tell me about it, won't be doing that again :)
[20:58] <bigjools> Sarvatt: that means you're uploading to Ubuntu, not a PPA
[20:59] <Sarvatt> bigjools: I copied it from primary archive for ubuntu and it's screwed up where it thinks the file is, i'm positive it's going to the PPA
[20:59] <Sarvatt> Uploading to x-updates (via ftp to ppa.launchpad.net):
[20:59] <bigjools> what upload path?
[21:00] <Sarvatt> fqdn = ppa.launchpad.net
[21:00] <Sarvatt> method = ftp
[21:00] <Sarvatt> incoming = ~ubuntu-x-swat/x-updates/ubuntu
[21:00] <bigjools> ok
[21:00] <bigjools> the error is misleading because the file was copied from  Ubuntu
[21:00] <bigjools> bleh
[21:00] <Sarvatt> yeah only it wasn't really copied because it had an error so it's kinda stuck in limbo
[21:00] <bigjools> so, how long ago did you delete the package?
[21:00] <bjsnider> but the point remains it's still complaining about the source package name
[21:00] <Sarvatt> 24 hours or so
[21:01] <Sarvatt> aha!
[21:01] <Sarvatt> [PPA ubuntu-x-swat-x-updates] [ubuntu/lucid] nvidia-graphics-drivers 256.35-0ubuntu2~xup (Accepted)
[21:01] <bigjools> ok you can resurrect it by copying it within the PPA I think
[21:01] <Sarvatt> woot
[21:01] <bigjools> FWIW you can refer to .orig files in Ubuntu from your PPA as well
[21:02] <Sarvatt> i tried that but the .orig isn't really available and it got rejected
[21:02] <Sarvatt> thanks for the help bigjools, got it worked out :)
[21:02] <bigjools> this is why the UI to copy files from Ubuntu is not linked anywhere :)
[21:03] <bigjools> it's got issues
[21:03] <Sarvatt> yeah definitely going to be more careful with it in the future :)
[21:03] <bigjools> anyway, you're welcome
[21:03] <bjsnider> it should have stopped him from trying to do this in the first place
[21:03] <bigjools> why should it have done that?
[21:03] <Sarvatt> i dont see how it could, this is a really fringe problem
[21:04] <bjsnider> he was trying to overwrite an already-existing source package with another of the same name but different contents
[21:04] <bigjools> hmmm
[21:04] <bjsnider> it shoul dhave looked at the ppa contents and said "you don't wanna do that, sparky"
[21:04] <bigjools> can you file a bug please?  I can take a look.
[21:05]  * Sarvatt tries to figure out how to explain the situation in a bug
[21:05] <bigjools> bugs.launchpad.net/soyuz
[21:05] <bigjools> just say what you did, exactly
[21:08] <bjsnider> there's something it stops you from doing, which is rebuilding a package in a new series but keeping the same package name. that is a good policy, to just say "no" when someone tries to do something that would violate the rules
[21:12] <Sarvatt> writing up the bug I'm not really sure it's a bug outside of it saying the orig.tar.gz existed in the primary archive for ubuntu, in the end it did accept a package with my original orig.tar.gz
[21:12] <Sarvatt> (saying it existed already in the rejected mail)
[21:14] <Sarvatt> man, I'm even more confused now, the orig.tar.gz it accepted was actually the one copied from the archive!
[21:15] <bjsnider> was there any difference between that one and your original orig fie in terms of contents?
[21:15] <Sarvatt> the one in the archive uses the nocompat32 .run
[21:16] <Sarvatt> for x64
[21:16] <bjsnider> what? why?
[21:16] <Sarvatt> it uses the 32 bit .run contents directly
[21:16] <bjsnider> i see
[21:18] <Sarvatt> it had to  have actually deleted my orig.tar.gz with the same name and copied the one from the archive over because this one it accepted really is the archive one
[21:19] <Sarvatt> dpkg-source: info: building nvidia-graphics-drivers using existing nvidia-graphics-drivers_256.35.orig.tar.gz
[21:19] <Sarvatt> i opened up that orig.tar.gz and it's got the nocompat32.run in it
[21:20] <bjsnider> then the original error doesn't make sense
[21:20] <Sarvatt> yeah for sure.. i'm totally lost
[21:21] <bjsnider> bigjools, it takes a week for files to actually disappear from a ppa once they are deleted, right?
[21:21] <Sarvatt>  871f54c6c8e0b30fcb5fec40fe3eed7b7081203c 49082614 nvidia-graphics-drivers_256.35.orig.tar.gz << the uploaded one it accepted  f8ec98f1d0deef487e60f8435ce8ccc7e3f30bd4 65596688 nvidia-graphics-drivers_256.35.orig.tar.gz << my original one i deleted
[21:21] <bigjools> from the repo. 15 minutes or so, from inside Launchpad it takes a week
[21:23] <bjsnider> bigjools, in other words, launchpad still thinks they're there for a week?
[21:23] <Sarvatt> http://ppa.launchpad.net/ubuntu-x-swat/x-updates/ubuntu/pool/main/n/nvidia-graphics-drivers/
[21:23] <bigjools> no, it just keeps a copy in the librarian in case you want to keep it
[21:23] <bigjools> for downloading later
[21:23] <Sarvatt> definitely the one from the maverick archive in there, i only uploaded the diff
[21:25] <bjsnider> that error message would happen if you had tried to copy a maverick package into the ppa into the maverick series. i don't see why it would happen if copying into the lucid series
[23:28] <warewolf> Sarvatt: hey, I figured out how to get dhcpd working on two interfaces, so it should be easier to into my EeePC now.