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