/srv/irclogs.ubuntu.com/2007/11/28/#ubuntu-x.txt

ubotuNew bug: #172456 in xorg (main) "intel driver does not honor CW command" [Undecided,New] https://launchpad.net/bugs/17245600:00
ubotuNew bug: #172435 in xorg (main) "[hardy] login hangs after upgrade to xorg 1.4" [Undecided,Confirmed] https://launchpad.net/bugs/17243500:21
ubotuNew bug: #82925 in xorg (main) "AutoRepeat doesn't work on Thinkpad Back/Forward keys." [Undecided,New] https://launchpad.net/bugs/8292509:45
ubotuNew bug: #172591 in xorg (main) "intel driver does not honor clone screen output" [Undecided,New] https://launchpad.net/bugs/17259115:35
ubotuNew bug: #172601 in xserver-xorg-driver-ati (main) "Dual-head fails with ati driver, appears related to 'crtc'" [Undecided,New] https://launchpad.net/bugs/17260116:45
ubotuNew bug: #172610 in xserver-xorg-video-intel (main) "gnome-panel position is above the standard one" [Undecided,New] https://launchpad.net/bugs/17261017:41
brycemy cat this morning:  http://bryceharrington.org/Photos/Cats/18:09
tjaaltonmm, that looks comfy ;)18:12
ubotuNew bug: #172638 in mesa (main) "Segmentation fault in Mesa dri / SDL _ConvertX86p32_8RGB332" [Undecided,New] https://launchpad.net/bugs/17263820:21
brycehuh, all the X tasks for alpha-1 are done.  https://launchpad.net/ubuntu/+milestone/hardy-alpha-1  We're awesome20:32
bryceoh whoops, there's a couple blueprints for driver issues.  hmm20:34
tjaaltonusers can propose those at will..20:46
tjaaltontoo bad that specs can't be marked invalid by devs20:49
brycedo you think those are invalid?  I think at best they're bug reports...20:59
tjaaltoninvalid as specs. there are almost 1800 specs listed, and majority of those should just be bug reports21:46
brycetrue21:50
tjaaltonooh, they got removed :)22:00
bryceyup22:00
bryceI got friends ;-)22:01
brycethe specs are still there, just not listed for hardy22:01
tjaaltonyeah22:02
tjaaltonsomeone should have the guts to clean up the specs22:03
bryceagreed22:03
bryceI've been accumulating a list of obsolete/invalid X specs on wiki (X/Blueprints), in hopes one day to find someone who can/will go through and close them22:03
tjaaltonI guess the reason why it has come to this is that the guidelines used to mention that "feature requests should be specs"22:04
bryceI asked mdz a while ago, but he didn't want to do it22:04
* bryce nods22:04
tjaaltonit needs special powers..22:05
bryceto be honest I think by not regularly weeding blueprints, it makes the whole system less useful22:10
bryceI wish it were categorized more, like bugs are, so there'd be an X-blueprints area that we could maintain22:11
tjaaltonright22:13
tjaaltonit's hopeless trying to find something useful, although the search works somewhat22:14
tjaaltonsigh, why did I start going through nv bugs in upstream22:28
bryceheh22:29
bryceeh, so much for offering to help with the xorg website22:30
tormodhi22:31
bryceheya tormod :-)22:32
tormodbryce: xorg website?22:32
brycedaniels asked for help on wiki.x.org22:32
tormodon the xorg ML?22:32
bryceyeah22:32
tormodI asked them for permissions to remove spam some time ago , heard nothing22:33
bryceweird, because it seems the complaint was that the spam load was too high22:33
tormodkind of sucks to file bugs for every change you want to do on the front page also22:33
bryceyep22:33
tormodthe xorg problem is that they don't want to receive help :)22:34
bryceseems that way22:34
bryceupstreams are weird22:34
tormodtheir issues with their server hardware is another farce22:35
tormodthey've got money, servers, people who would like to help...22:35
bryceI like how they completely shut everything down for days when they have security issues22:36
tormodbut things are just blocked on... nothing?22:36
* bryce shrugs22:37
bryceI figure it's just that daniels takes on too many tasks himself, and isn't comfortable sharing responsibiltiies or something22:38
brycelike you say, step 1 is you have to want to receive help22:38
bryce(step 2 is actually letting people help you) ;-)22:39
tormodI read the thread - yeah it ended up in "which wiki engine is better" discussion. They don't seem to get that "community" thing...22:41
brycetormod, tjaalton, do either of you have code/processes for packaging x.org snapshots?22:45
tormodbryce: funny you ask, was working on it all night :)22:45
brycekewl22:45
tjaaltonbryce: nope22:45
tormodI've been trying to automate xorg git + debian git -> source deb22:46
brycesome of the ume guys are wanting snapshot packages of xserver git head so they can use the new xephyr stuff22:46
brycecool, can I assist?22:46
tormodworks nice for radonhd, but for some reason not for ati22:46
tormodI wanted to make builds for ati+atombios...22:46
bryceyeah this sounds like it could be quite useful for bleeding edge folks without packaging expertise22:47
brycehow could I help?22:47
tormodTake a look at the script attached to XorgOnTheEdge22:48
bryceok22:48
tormodIt potentially work with xorg-server as well.22:48
tormodbut I am not fluent enough in git to get much further ATM.22:49
tormodSince they are removing xsfbs I have to incorporate make-orig-tar also.22:49
brycehmm, I'm not spotting the link...?22:50
tormodwiki Attachments22:50
bryceoh whoa, I didn't know there was such a thing.  cool thanks22:51
tormodbryce, the radeonhd packages on XorgOnTheEdge are built with the script, the extra manual steps (mostly adjustments for Gutsy) are documented in debian/README.ubuntu-dev23:03

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!