/srv/irclogs.ubuntu.com/2008/06/18/#ubuntu-x.txt

bryceyep, mesa is mucha fun00:41
tjaaltonok, xserver 1.5 should be looking better. many patches deleted, some need forwarding upstream and some need to be forward ported01:01
tjaaltonumm, getting late. I'll push this tomorrow01:02
tjaaltonnight ->01:02
brycegreat01:07
brycemesa seems to not be building on amd64 (some pbuilder issue) but looks like it's ok on i386 so far.  I'll push it once it's finished building.01:07
brycemesa's pushed.03:05
brycetjaalton: I've also gone through a preliminary merge for xorg; I'd appreciate a review if you wouldn't mind:  http://people.ubuntu.com/~bryce/Testing/xorg/03:10
tjaaltonbryce: sure06:25
tjaaltonbryce: fwiw, I think xfonts-utils could've been synced, since the changes were meant for dapper->hardy upgrades06:40
tjaaltonsame goes to -vmware, a proper fix has been applied upstream :)06:45
tjaaltonbryce: xorg; I think the x11r6_bin_not_empty_move change can be deleted from templates and preinst06:53
tjaaltonbryce: is this targeted for 1.5?06:56
brycetjaalton: ah, that wasn't clear to me from the xfonts-utils changelog.  I did notice -vmware is syncable and will do that later08:55
tjaaltonbryce: sure, great08:58
tjaaltonxorg; radeonhd should already be in included in video-all09:00
tjaaltonand x11-common/xserver-xorg change actually reverts the change done in debian09:17
tjaaltonwhich is to move stuff from xserver-xorg to x11-common09:17
bryceboth of those are things I'm curious and not sure about09:18
tjaaltonhmm let me check that09:18
tjaaltonradeonhd is listed already though09:18
bryceok09:19
tjaaltonrules; it should be x11-common instead of xserver-xorg09:20
bryceso what should I change?09:21
tjaaltonleave them as they are in debian?-)09:22
bryceuh, but in this latest set of changes debian is moving them back from x11-common to xserver-xorg09:23
tjaaltonhmm, I don't understand.. I'm looking at the current debian version and the initscript and stuff are in x11-common09:26
tjaaltonmy mistake that I thought there was an actual change in debian. seems that not much has moved09:28
tjaaltondebconf has, but not the initscript or Xsession etc09:28
tjaaltonuh, dexconf09:28
bryce'X' as well09:31
tjaaltonright09:31
brycewhat I'm unsure of is what this implies for some of the ubuntu-specific changes relating to x11-common09:32
tjaaltonlike the apport script and failsafe?09:33
bryceright, and "Add a dependency to xserver-xorg for each binary built to save disk/livecd space."09:34
tjaaltonthat's because we only ship one set of docs09:34
tjaaltonand the rest is symlinked09:35
bryceright, and I changed the paths from .../x11-common/... to .../xorg-server/... - but is that correct?09:35
tjaaltonxserver-xorg-driver-all could be dropped09:35
tjaaltonwhy should those be moved?09:37
bryceexactly my question09:38
tjaaltonhehe09:38
tjaaltonso, if x11-common is not installed by default then yes, they should be moved09:40
tjaaltonbut it seems that x11-common is installed if you need _any_ of the X libs, so it should be safe to keep them there09:44
tjaaltonie. it has many reverse-dependencies, so keeping the changelog etc in x11-common is a safer bet09:48
bryceok09:48
tjaaltonxserver-xorg is only installed if you have X installed09:48
tjaaltonbtw, there's -12 which has openchrome09:53
tjaaltonand didn't q-funk want to drop amd from the deps?09:53
bryceah, didn't see -12 yet09:53
tjaaltonit was released last night :)09:53
bryceyeah, I need to doublecheck the amd stuff09:54
tjaaltonyou'll keep the BPX stuff for the time being?09:54
* bryce nods09:55
bryceprobably not much longer though.09:56
brycemaybe I should chat with Colin about it when we get together in London first.09:57
tjaaltonok, so if you plan on moving it, xserver-xorg should C/R x11-common09:57
tjaaltonbut if it gets dropped, maybe keep in x11-common until you come up with a plan09:58
tjaaltoncolin hasn't replied to the hal-script post.. maybe you'll manage to hack it so it actually works :)09:59
bryceyou might re-email him on that; he recently had a death in the family and was gone for a week and probably fell far behind in email10:00
tjaaltonoh right.. :/10:00
tjaaltonwhen is the sprint scheduled?10:01
bryceJul 14-1810:01
tjaaltonok10:02
tjaaltonI might re-email after I get back on Jun 29th10:03
tjaaltonafter tomorrow I'll be mostly offline, but will check email & irc almost daily10:03
tjaaltonyay for 3G10:03
bryce:-)10:04
tjaalton(well, GPRS on rural areas..)10:04
brycethink xserver 1.5 can be put in by then?10:04
tjaaltonit might get released next week, so when I get back things should be in good shape10:04
tjaaltonregarding mesa & drm too10:05
bryceis there more I could do to prep the way for it?10:05
bryceOtherwise, I guess now that packaging is pretty much caught up, I'll go back to focusing on -ati bugs a while.10:06
tjaaltonhmm, I think that the components are still in state of flux, so concentrating on bugwork for a week or two might pay off10:09
tjaaltonbtw, there's a new ati that probably should be merged/synced10:10
tjaalton"should be" meaning that it apparently fixes a ton of bugs10:12
bryceok, I'll look at getting that merged in10:13
bryceI also really need to get my auto-git builder for -intel (and -ati) up and running10:13
brycemaybe I can finally get that going :-)10:13
tjaaltonheh10:13
tjaaltonhum, should be enough to sync -ati from experimental. we have no changes10:14
tjaaltonQ-FUNK: 146_X86EMU-added-blacklist-for-I-O-port-in-0-0xFF-range.patch is not applied upstream and does not even apply on 1.5, so what should we do about it?10:31
tjaalton(xorg-server)10:31
Q-FUNKtjaalton: they eventually reverted the change and applied a more complex one to match GX2 and LX hardware specifically.10:32
Q-FUNKoh... wait.  blacklist10:33
Q-FUNKyes, they rejected blacklist.10:33
Q-FUNKhttp://www.x.org/wiki/AMDGeodeDriver10:33
Q-FUNKthey accepted only 2 out of 3 patches10:33
tjaaltonok, so it can be dropped?10:36
Q-FUNKyes10:37
tjaaltoncool10:38
cody-somervilleHey11:21
cody-somervilleCan someone please help me with bug #232122 ?11:22
ubottuLaunchpad bug 232122 in xfce4 "xfce4 hangs when tried to login again. (dup-of: 232364)" [Undecided,Confirmed] https://launchpad.net/bugs/23212211:22
ubottuLaunchpad bug 232364 in dbus "dbus-launch freezes for unknown reason at session start" [High,Confirmed] https://launchpad.net/bugs/23236411:22
cody-somervilleOr more specifically, bug #23236411:22
cody-somervillelibxcb hangs waiting on the bilateral socket with X11:25
cody-somervilleIt only occurs intermittently though11:25
tjaaltoncody-somerville: sounds hairy.. maybe ask the xcb devs?11:31
cody-somerville: (11:40
tjaaltonjoy, nvidia dropped support for GF5 from 177.xx12:34
tseliottjaalton: Kano told me that there are *only* these flavours:12:52
tseliotVER_LEGACY_1=71.86.0412:52
tseliot# DX7 cards since gf2mx and all DX8 cards12:52
tseliotVER_LEGACY_2=96.43.0512:52
tseliot# GeForce 5 series12:52
tseliotVER_LEGACY_3=173.14.0912:52
tseliotand latest is 177.13 which supports the gtx 260/28012:52
tseliottjaalton; I would like to package all the remaining flavours today. I will use our new package as a base rather than waiting for Debian to adopt the latest flavour too13:10
tseliottjaalton; objections?13:11
tjaaltontseliot: no, go ahead14:36
tseliottjaalton: ok, the new flavour will be nvidia-graphics-drivers-legacy-173xx14:38
tseliot(we can change this later)14:38

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