/srv/irclogs.ubuntu.com/2007/05/30/#ubuntu-x.txt

brycehmm, I'm getting odd errors attempting to reach archive.ubuntu.com:12:44
bryceErr http://archive.ubuntu.com gutsy/main dpatch 2.0.2212:44
bryce  404 Not Found [IP: 91.189.89.8 80] 12:44
brycenevermind, figured it out02:40
ubotuNew bug: #117638 in xorg (main) "Graphics problem when users have different screen resolutions" [Undecided,Unconfirmed]  https://launchpad.net/bugs/11763803:19
=== cjwatson_ [n=cjwatson@82-69-40-219.dsl.in-addr.zen.co.uk] has joined #ubuntu-x
tepsipakkievery epoch has been committed to git.d.o07:50
keescooktepsipakki: very cool!08:10
tepsipakkithere are 24 packages with different orig.tar.gz, 45 packages with changes committed and waiting for upload, and 16 that otherwise can be synced after an upload08:14
tepsipakkimaybe I should put all of this in the wiki..08:14
tepsipakkiits just easier to edit a text file which is always open on my screen session :)08:14
=== cjwatson [n=cjwatson@82-69-40-219.dsl.in-addr.zen.co.uk] has joined #ubuntu-x
=== seb128 [n=seb128@ubuntu/member/seb128] has joined #ubuntu-x
=== seb128 [n=seb128@ubuntu/member/seb128] has joined #ubuntu-x
keescookbryce: okidoky.  evil evil beforelight05:31
bryceyup05:31
keescookI think we're very close -- I suspect there are just some patch thingies missing from the rules05:31
bryceI'd checked dpkg -c on the deb before I sent it in, and didn't see the recursive paths05:31
keescookwhich other package uses the x patch stuff?05:31
bryceappres, xorg-docs, bitmap, xorg-server, etc. etc.05:32
brycebasically all the ones I've touched have used this system05:32
keescookbryce: weird.  I wonder why we're seeing different results.  does your build log show it as having applied the patch?05:32
bryceI seem to recall it did, yes05:32
keescookappres and bitmap don't seem to have it05:33
keescookdo you still have the log?  Something must be wrong with my build environment05:33
keescookah, yeah, xorg-docs has it05:34
keescookokay, so, comparing the build and clean rules between xorg-docs and beforelight.  xorg-docs has:05:35
keescookbuild: patch build-stamp05:35
keescookbuild-stamp:05:35
keescookwhere as beforelight is just:05:35
keescookbuild: build-stamp05:35
keescookbuild-stamp:05:35
bryceno, don't have the log05:36
keescookgo ahead and build it again (it's quick).  I'd like to track down the source of the problem.05:36
bryceok building05:37
brycehmm, there's nothing indicating the patch applied05:42
keescookcan you paste-bin the results of dpkg -c ?05:44
brycehttp://pastebin.ca/52285005:48
=== pitti [n=pitti@ubuntu/member/pitti] has joined #ubuntu-x
=== pitti [n=pitti@ubuntu/member/pitti] has left #ubuntu-x ["Bye"]
ubotuNew bug: #117222 in xorg (main) "Dell Latitude X1 Screen Resolution" [Undecided,Needs info]  https://launchpad.net/bugs/11722205:54
keescookbryce: drwxr-xr-x root/root         0 2007-05-30 08:37 ./tmp/buildd/beforelight-1.0.2/debian/beforelight/05:55
keescookso there are bad paths in your .deb too.  Okay, I'm not going crazy.  :)05:56
ubotuNew bug: #117782 in linux-restricted-modules-2.6.20 (restricted) "Upgrade of linux-restricted-modules-2.6.20-16-generic failed" [Undecided,Unconfirmed]  https://launchpad.net/bugs/11778205:56
keescookbryce: alright, so, to hook up xsf fully.05:56
keescookdo you still have the xorg-docs source tree to look at?05:56
bryceyeah05:57
keescookin xorg-docs's debian/rules, take a look at the "build" rule.05:57
keescookbefore it can run the "build" rule, it has to do the pre-reqs, so it performs "patch" and then "build-stamp".05:57
keescook"build-stamp" is immediately below the "build:" rule, and "patch" is defined in the xsf included makefile05:58
keescookif you look at beforelight's debian/rules, you'll see that "patch" is missing.  go ahead and add it (order is important: it needs to do "patch" before "build-stamp" -- gotta build the patched source)05:59
bryceah, I thought "patch" was leftover from dpatch, so removed it06:03
keescookit tends to be a general rule for invoking whatever patch system has been included in the packaging.06:04
keescookno matter what the patch system, it always has to happen before the build and after the clean, etc.  :)06:04
keescookbryce: any luck with rebuilding beforelight with the fixed rules file?06:13
brycenope, it complained I didn't have quilt06:13
bryce(installing)06:13
bryceer wait, it's already installed06:14
keescook??06:14
brycehrm06:14
keescookthat's a build-dep06:14
keescookso you'll need to update your control file too (adding the xsf stuff, I guess, requires quilt)06:14
brycehowever quilt is already listed in the Build-Depends 06:15
brycewait06:15
bryceclearly I need stronger coffee06:15
keescookheh.  :)06:15
bryceman what a pita for such a irrelevant bit of x ;-)06:16
bryceah well, you learn the most on things that *don't* go smoothly, eh?06:16
keescook:) but it's all for the learning.  right.  :)06:16
brycehrm06:22
bryceNo patches in series06:22
bryceNo patches to apply06:22
bryceoh!06:22
brycemv 00list series06:22
brycedpkg-gencontrol: warning: unknown substitution variable ${misc:Depends}06:27
bryceis that normal?06:27
keescookI think that's normal, but I honestly don't know what it means.06:27
bryceahh06:27
bryce100_appdefaultdir_prefix.patch06:27
bryceApplying patches...successful.06:27
keescookyay!06:27
keescookhave you used quilt before?  I hadn't before doing debian packaging.  I find it... weird.06:28
keescookif you use quilt directly, don't forget to set  QUILT_PATCH=debian/patches  otherwise it'll write them to just "patches"  :)06:28
brycethere was a brief period when I started on nfsv4 where they were using quilt, before they switched to git06:29
bryceso I used it like once or twice, but I found I just needed to deal with their patches in aggregate anyway, so didn't really learn it06:30
bryceyup, got it in my .bashrc06:30
keescookcool.06:30
brycehttp://pastebin.ca/52295706:31
keescookoh! sorry, it's QUILT_PATCHES  (I missed the "ES" before)06:31
keescookwhat do you think of the dpkg -c output?06:31
brycehmm, well it looks the same to me as the last one06:34
keescookI would agree.  :(06:35
bryceso I'm not sure that the patch works correctly06:35
keescookwhat you see there is what would be installed from the deb, and nothing should ever go in /tmp or /home, etc06:35
keescookso, here's another thing, your patch only changes Makefile.am; this file is not used by the build.  (Makefile.in is used)06:36
keescookso you'll like need to add Makefile.in's changes too.06:37
bryceah, that could be it06:37
keescook(and send the Makefile.am patch upstream, since that seems to be a legit bug)06:37
bryce100_appdefaultdir_prefix.patch06:53
bryceApplying patches...successful.06:53
keescook:)06:53
brycelooks clean http://pastebin.4programmers.net/231906:56
keescookeeexcellent!06:56
brycethat xorg-docs patch got accepted and applied upstream :-)06:56
keescooknice.  :)06:56
keescookokay, go ahead and upload beforelight, and I'll sponsor it in.06:57
jcristauis that patch the same as http://git.debian.org/?p=pkg-xorg/app/xbase-clients.git;a=blob;f=debian/patches/16_beforelight_install_app-defaults.diff;hb=HEAD ?06:57
brycethe xorg-docs patch was Debian's 023_specs_doc_fixes.diff06:57
jcristauyes, i saw that, thanks for forwarding it!06:58
keescookjcristau: yeah, that looks like the same beforelight patch06:58
bryceah yes, the beforelight patch is that one06:58
jcristauok06:58
bryceok, posted upstream07:01
jcristau\o/07:02
jcristaui should have done that when i added the patch in the first place...07:02
bryceno prob; made for a good learning opportunity for me07:03
brycejcristau: which brings up a question...  why does debian-x use this xsfbs system for handling patches, rather than dpatch?07:04
jcristauthe primary reason would be that dpatch sucks :)07:04
jcristaubut the xsfbs stuff was basically imported from the monolith, and most of it is unused now...07:05
jcristauwe should work on integrating the rest in quilt proper07:05
brycewell I do have to admit I could never get dpatch working, whereas xsfbs was reasonably straightforward (all the problems I ran into were my own doing)07:05
jcristau(the fact that dpatches aren't proper patches isn't exactly helpful, e.g.)07:06
bryceyeah07:06
brycejcristau: btw, I don't remember if I showed this to you already - http://people.ubuntu.com/~bryce/Xorg/versions_current.html07:07
brycejust for my own sanity to check what still needs merged/updated07:07
jcristaunice07:08
brycemost of what's left is just epoch number variances, or stuff that will come from the apps split out07:09
jcristauok07:12
=== johanbr [n=j@JBrannlund.MathStat.Dal.Ca] has joined #ubuntu-x
johanbrHi. Has it been decided which version of Mesa will land in Gutsy? The reason I ask is that 3D support for my card was added very recently, and it'd be nice to able to ditch the fglrx driver.07:17
bryce6.5.3 is in gutsy now07:18
brycebut the plan is for 7.0.007:18
brycewe're just waiting for the 7.0.0 release, which I understand should be any day now (tm)07:18
johanbrI see, thank you. Will Mesa 7.0.0 include current git, or is that a different branch?07:19
jcristauit's mesa_7_0_branch07:20
brycejohanbr: any testing you could do of that branch for the mesa guys could be a big help07:20
keescookbryce: the resulting patch in debian/patches looks a little funny -- I've dropped the duplication of itself, and will upload this once it finishes building07:33
keescookthe final results look fine, though.  \o/07:33
bryceah ok07:33
bryceoh, I see, I had an extra/different copy of the patch hanging around that got tucked in.  hrm07:35
keescookyeah, before each upload, I review any patches I've touched, and then the debdiff itself between the current and older package.07:36
keescook(and I look at the diff.gz to make sure there weren't any out-of-debian/ changes07:36
bryceI think I was just being impatient, I usually check that07:36
keescookokay, uploaded!  :)07:37
brycekewl!  thanks!07:37
keescooknp :)07:39
brycekeescook: I figured out debian's naming scheme for X *proto packages.  Filled in a ton of blanks:  http://people.ubuntu.com/~bryce/Xorg/versions_current.html07:58
brycestill haven't figured out where the font-* packages go though07:58
keescookcheck the debian/copyright files, they should mention where they were downloaded from07:59
keescookoh, you mean the reverse, sorry07:59
bryceno, the issue... yeah07:59
jcristauxfonts-base has font-arabic-misc font-cursor-misc font-daewoo-misc font-dec-misc font-isas-misc font-jis-misc font-micro-misc font-misc-misc font-mutt-misc font-schumacher-misc font-sony-misc font-sun-misc07:59
keescookcheck xfonts-base, ah jcristau is too fast for me.  :)08:00
bryceahh08:00
brycejcristau: any plans on ever breaking those out, or will that package stay as is for a while?08:00
jcristauthat'll stay as is08:01
brycecool08:01
jcristauxfonts-100dpi: font-adobe-100dpi font-bh-100dpi font-bh-lucidatypewriter-100dpi font-bitstream-100dpi08:01
jcristauxfonts-75dpi: font-adobe-75dpi font-bh-75dpi font-bh-lucidatypewriter-75dpi font-bitstream-75dpi08:02
brycewhat's the command to list what is contained in them?08:02
johanbrbryce: I tried building Mesa git a week ago, but the compile failed, apparently because it found the (old) system libdrm and I wasn't able to get it to work right. I'll see if I have time one of these days...08:02
brycejohanbr: cool, let us know if you get it working08:03
jcristaubryce: i'm using "ls" in the source tree :)08:03
bryceahh heh08:03
jcristauxfonts-cyrillic has font-*-cyrillic08:03
johanbrbryce: Sure, will do. The Mesa 7.0.0 branch does appear to contain the support for my chipset (rs480), so it looks like I'll be able to use free drivers in Gutsy.08:04
jcristauand it looks like xfonts-scalable is actually font-bitstream-type108:05
bryceok /me hacks in some translation tables08:06
jcristauxfonts-encodings is called "encodings" upstream08:07
jcristaubryce: "xproto" upstream is "x11proto-core" in debian08:36
ubotuNew bug: #117828 in xorg (main) "switch user" [Undecided,Needs info]  https://launchpad.net/bugs/11782811:07

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