[00:06] good night [00:16] Heya gang [00:25] hey Hobbsee [00:25] hey zul! [00:26] no one here but us goats [00:27] * Hobbsee is no goat [00:31] Hobbsee: can you prove that? :-) [00:31] Nafallo: yeah - people hav eseen me [00:32] Nafallo: Everyone knows she's a green alien. Duh. [00:32] * Hobbsee says "nyah. try harder" at the cars outside. [00:32] :-P [00:33] * Nafallo ponders if "people" are trustworthy enough though ;-) [00:33] well, they upload software that you're currently using, so... [00:34] Fujitsu: i though we established the fact that Hobbsee is a zombie [00:34] zul: Oops, so we did. [00:40] a zombie alien ? [00:41] btw hiya * [00:42] heya! [00:42] imbrandon: a *green* zombie alien! [00:42] hehe [00:53] hi [00:53] It's an ajmitch! Run! [00:53] * ajmitch runs [00:53] oh noes! [00:54] :( [00:54] * Hobbsee attacks ajmitch with the Long Pointy Stick of DOOM!!!!!!!!!!!!!!! ™ [00:54] * Hobbsee coattacks Burgundavia with it, too. [00:54] * ajmitch scurries off back into his corner [00:55] i love packages that seem intresting but have no help or man or documentation whatsoever, even on the project website [00:55] i think there is a manpage for ls [00:55] lol [00:55] mach is what i was speaking of [00:56] its supose to create rpm chroots, like debootstrap, replaces rpmstrap [00:56] * Fujitsu is glad that its secrets shall remain locked away forever. [01:03] Hobbsee: apparently women hate me today. My gf was beating me up as well ;( [01:04] Burgundavia: awww [01:05] * Hobbsee hugs Burgundavia [01:07] * slangasek beats up Burgundavia too, so he doesn't feel cheered that it's not a gender thing [01:07] Hah [01:07] hmm, s/doesn't/can/ [01:08] I hate you all [01:08] I am going to run Gentoo now [01:08] excellent [01:08] heh [01:08] our work here is done then [01:08] Well, our job is done. [01:08] * StevenK grins, and high fives ajmitch [01:08] hmm, I wonder why you need to agree to the Debian Machine Usage Policies to be a Debian Maintainer === neversfelde_ is now known as neversfelde [01:08] * Hobbsee attacks slangasek and bddebian with the Long Pointy Stick of DOOM!!!!!!!!!!!!!!! ™ to make it appear random [01:08] is that just because of the buildds? [01:10] Hobbsee: it may appear random to some, but the pattern is perfectly clear to me! [01:10] slangasek: oh yes? [01:10] hrmph [01:10] absolutely [01:10] * Hobbsee wonders if you're better at patterns than those she was playing with mao are [01:11] s/with mao/mao with/ [01:11] you're clearly poking people who IRC! [01:11] man, I suck at mao [01:11] although I played it at like 2 or 3am in a foreign country [01:11] and I was sick [01:11] so we'll blame it on that [01:12] soren can attest to how bad it was [01:12] LaserJock: I think those are considered standard operating conditions for Mao, sorry :) [01:12] heh [01:12] hehe [01:12] * Fujitsu wonders what this Mao thing is. [01:12] Fujitsu: come to a UDS and find out [01:13] Hah, like that's going to happen. [01:13] Then come to Sydney and find out [01:14] Maybe one day if I can convince my parents. Which isn't likely. [01:15] ... maybe one day you'll be allowed to travel without parental approval? [01:15] aside from the green alien zombies among us, people are known to age [01:15] slangasek: That's a while off yet. [01:16] Some of us faster than others :-( [01:16] I did say age, not grow up [01:17] Well. I've just satisified my government election duties... [01:17] satisfied [01:17] TheMuso: Did you have to? [01:17] StevenK: Of course. [01:17] Voting just encourages them [01:17] TheMuso: Was the form in Brallie? [01:17] With any luck our beloved Mr. Howard will be gone soon... [01:17] StevenK: I think not. [01:18] slangasek: Aye, and I'm already old. I'll never grow up :-) [01:18] StevenK: I would use electronic voting, but I heard that it wasn't open source, so wasn't interested. [01:18] Fujitsu: It's just a question if he gets replaced by Peter Costello or Kevin Rudd? [01:18] StevenK: That's true. [01:18] * bddebian liked Howard [01:19] * StevenK prefers the latter, Peter Costello seeming like a jerk [01:19] * slangasek draws a correlation between bddebian's last two statements [01:19] !packaging | LaserJock [01:19] LaserJock: packaging is The packaging guide is at http://wiki.ubuntu.com/PackagingGuide - See https://wiki.ubuntu.com/UbuntuDevelopment NewPackages for information on getting a package integrated into Ubuntu - Other developer resources are at https://wiki.ubuntu.com/UbuntuDevelopment - See also !backports [01:19] slangasek: Haha. [01:19] StevenK: I don't particularly like either, but would prefer the latter. But I don't have to vote until next time. [01:20] LaserJock, did you mean to remove the / before NewPackages on that second link? [01:22] StevenK: Do you mind if I take care of openmovieeditor? [01:22] TheMuso: Not overly [01:26] slangasek: Right, I'm old and experienced enough to know that I don't want the government running my life.. [01:26] * bddebian hides [01:27] Did you see the "Kirribilli house for sale" joke? Rudd did say that he was going to come and live with me, in Canberra. [01:27] you mean that you don't want the /Australian/ government running your life, right, you'd rather have the American government running your life? [01:28] Well he'll be in The Lodge and I'll still be slumming it. [01:29] Maybe I'll catch him at the local pub, or strip joint ... *** frenchy laughs at his own joke. [01:33] slangasek: I am an American. And I don't want to live in a nanny state, no. :-) [01:35] oh, so you like Howard because he's Somebody Else's Problem [01:35] slangasek: Would you mind checking why my gutenprint upload got rejected? [01:35] StevenK: you forgot to sacrifice a goat to soyuz. [01:35] lol [01:36] oh, is that why Hobbsee's insistent that she isn't a goat [01:36] Hah [01:36] haha [01:36] * Fujitsu normally uses goats for SCSI, but they might be useful for Soyuz too. [01:36] StevenK: do I have a clue where to look for rejects? [01:37] slangasek: There's a log on drescher [01:37] called? [01:37] That I have no clue about [01:38] The directories with the upload bits should be in /srv/launchpad.net/ubuntu-queue/rejected, I think. Rejections should be logged to the lp_archive mailbox. [01:39] slangasek: er, is there a new kernel upload planned before the alpha? [01:39] Fujitsu: And how do you know that? :-) [01:40] lamont: Sent. Thanks [01:40] Hobbsee: I haven't heard. [01:40] StevenK: I don't quite recall. [01:40] Hobbsee: It's still important to have a Rationale for syncs after DIF to explain why we're importing after the freeze (Freeze Exception Process) [01:40] hmm, the lp_archive mailbox is rather Large [01:41] Anyone using `debuild -k`: please only do this if you are a sponsor: it's far better to get your changelog identity entity to match your GPG keyring identity. [01:41] slangasek: I'm not surprised. How many gigabytes? [01:42] StevenK: wrong .orig.tar.gz referenced [01:42] Fujitsu: 1.9 \o/ [01:42] There was no .orig.tar.gz in the .changes file [01:42] StevenK: no, but there would have to be one in the .dsc [01:42] and the checksum doesn't match the existing one [01:42] slangasek: Nice. [01:42] Ah, duh. [01:42] I forgot about that [01:43] slangasek: Danke, I'll sort that out soonish [01:43] StevenK: Did you not get an upload rejection email? [01:44] that's just what I was going to ask, the mail I was peeking at is rather uploader-oriented [01:44] actually, it looks pretty much identical to a dak reject :) [01:44] I did, I just couldn't make sense of why it was talking about things in the archive. [01:44] Oh wel [01:44] well, even [01:54] LaserJock! [01:55] Is it just me, or is requestsync getting the version number incorrect in the email subjects it produces, yet it gets the correct changelog? [01:56] TheMuso: I don't think it's just you: I've seen a bunch of things in the sponsors queue with that issue. [01:58] persia: Ok, thats good to know. [02:27] !packaging [02:27] packaging is The packaging guide is at http://wiki.ubuntu.com/PackagingGuide - See https://wiki.ubuntu.com/UbuntuDevelopment/NewPackages for information on getting a package integrated into Ubuntu - Other developer resources are at https://wiki.ubuntu.com/UbuntuDevelopment - See also !backports [02:28] hmm, looks like he fixed it [02:30] LaserJock: ponies! [02:31] trying to find a screw I lost in my grandfather's laptop [02:46] LaserJock: get it all sorted i see [02:56] goodness sakes [02:56] I was gonna say something and my laptop just turned off [02:56] apparently somebody unplugged me [02:56] heh [02:56] on reboot I had a ton of fsck problems [02:56] nice [02:57] had run fsck manually and there was a lot of stuff [02:57] hopefully I didn't lose too much data [02:57] probably only what you had open [02:58] well, that's fine then [03:05] wow someone actualy sugested use qemubuilder to build a i386 package on a x86_64 instead of a i386 chroot/pbuilder [03:05] yes, let us bow our heads in shame [03:06] heh [03:13] c [03:13] d [03:13] ugh wront tab [03:13] TheMuso: c is right in any tab? [03:13] * persia suspects /c is useful to avoid gibber === Hobbsee_ is now known as Hobbsee [03:55] hi [03:55] I am new [03:55] DoYouKnow: Hi. [04:04] Now that I've started doing packaging on my server (dunno why I didn't do this earlier), I can get a lot more done quicker [04:04] AMD Athlon(tm) 64 X2 Dual Core Processor 3800+ VS. Pentium II (Deschutes) [04:06] i should set up ccache and maybe distcc [04:06] is distcc the only way to get pbuilder to hit multicores? [04:07] pwnguin: You don't want to do that: it means that your build won't match the buildd build, and may not work. [04:08] is there a problem with not matching the buildd build? [04:08] pwnguin: yes. [04:09] I'm thinking that question deserves a two part answer [04:10] pwnguin: Essentially, the main reason we bother to build things locally is to make sure that they will build on the buildds when they get uploaded. [04:11] If you are just playing for private use, you'd do better to do a local build with `debuild`. [04:11] If you want to build something as a candidate for the repositories, you'd do best to run a full Soyuz implementation, but that's annoying, and pbuilder does most of it. [04:12] wait [04:12] Hmm [04:12] are there cases where things would build in parallel but not in pbuilder? [04:12] The reason debuild is better for local use is that it takes advantage of the installed system, and so ./configure will often pull in libraries that may normally be excluded (depending on the build system). [04:12] interdiff doesn't work that great [04:13] pwnguin: Yes. If there is accidental timestamp skew, make -j can become very confused. [04:13] somerville32: How doesn't it work? [04:13] persia: then it would fail in parallel [04:13] persia, I get hunking errors all the time [04:14] pwnguin: Not necessarily: maybe it works in parallel because it can catch up, but breaks in serial due to the skew. [04:14] somerville32: What's your command line? [04:14] interdiff -z -p1 diff1 diff2 [04:15] somerville32: You get "hunking errors" from running interdiff, or trying to use that interdiff? [04:15] I get hunking errors while running it [04:16] Sometimes, I can't get any meaningful ouput at all [04:16] somerville32: Could you put your diffs somewhere? I've never seen that. [04:16] I have two examples that I'll post in a second [04:19] pwnguin: distcc isnt very nice with pbuilder as it needs source/package changes ( -j X ) but ccache works well if setup right [04:19] with pbuilder [04:19] ah [04:19] i thought maybe pbuilder was smart about that stuff [04:19] heh no [04:19] but still, im thinking if it works in parallel [04:20] it works in series [04:20] plus there are programs that just fail peroid with distcc [04:20] pbuilder or not [04:20] right [04:21] i know distcc has limitations [04:21] AND icecream is better imho :) [04:21] well, i did ask if distcc was the only way [04:22] kde* is notorious for useing icecream vs distcc, never heard of it being used with pbuilder though [04:22] [15:09] I'm thinking that question deserves a two part answer <-- persia already answered the latter half. [04:25] * persia wonders if somerville32 encountered a grue [04:26] he encounted a GoldenPony, i expect [04:26] Don't GoldenPonies shiine in the dark, lighting the way to a happier place? [04:27] * somerville32 coughs something about Debian. [04:27] bah nuff $work for one night [04:27] time for a new theme [04:28] What is this a sign of? [04:28] Installing: /usr/share/locale/ar/LC_MESSAGES/notecase.mo [04:28] /bin/sh: /tmp/buildd/notecase-1.6.9/debian/notecase: Permission denied [04:28] I'm using CDBS [04:28] (It says that for everything it tries to install) [04:28] that, cdbs = magic ? [04:28] Not using fakeroot? [04:29] filesystem full? [04:29] I'm using pbuilder [04:29] * persia suspects /tmp is tmpfs and only 1/2 RAM, and can't build big things [04:30] * Hobbsee wonders if it's somethinga bout executability [04:30] like, debian/rules not being executable [04:31] debian/rules is executed [04:31] I do see this: DEB_MAKE_CHECK_TARGET unset, not running checks [04:32] Hobbsee: That's cause an error much earlier in the process. [04:32] persia: ahhh [04:32] persia: it's been so long since i've done it :) [04:32] somerville32: the lack of running make check isn't a real error [04:34] Err. by "isn't a real error", I mean "is safe to ignore" [04:35] It built on my other computer IIRC [04:35] Does your other computer have more RAM? [04:35] I don't see dh_checkperms or w/e it is called being run. Is there a CDBS setting for that? [04:38] somerville32: Likely: there's a CDBS setting for everything. On the other hand, your problem is not dh_fixperms: you're either running out of space or trying to write to a directory that doesn't exist (maybe you need a notecase.dirs file?) [04:38] Most likely [04:38] Well, I gotta jet. bbl [04:39] somerville32: Please post your interdiff example when you can: that really sounds like a combinediff error, and I'd like to make sure it doesn't happen often. [04:40] Sure thing [06:19] Hi all! === LaserJock is now known as LaserRock [06:31] LaserRock! [06:47] pwnguin: btw if you havent seen it here is the info on http://en.opensuse.org/Icecream , its pretty KDE centric, but iirc it can be used for anything , its kinda a distcc-ng by suse [06:55] it can be used by whatever you want, the only thing kde centric with I think is the client status window [06:56] well, distcc will probably be enough [06:56] i guess you can't really hack in parallel builds to a package after the fact though [06:56] err [06:56] not distcc, [06:56] ccache [06:58] from a time standpoint, perhaps i should just figure out debuild [07:02] debuild is essentialy the same as pbuilder only not preformed in a chroot, i.e. apt-get build-dep ; debuild ; ( from the main package directory ) [07:02] Er. No. debuild doesn't pull build-deps. [07:02] common options are -S -sa for a source only ( REVU ) upload , just plain debuild if you were the last to make a change and -us -uc if you were not [07:03] persia: yea i added the apt-get build-dep bit :) [07:03] imbrandon: to debuild? Why? [07:03] debuild is essentialy the same as pbuilder only not preformed in a chroot, i.e. apt-get build-dep ; debuild ; ( from the main package directory ) [07:04] 00:58 < pwnguin> from a time standpoint, perhaps i should just figure out debuild [07:04] imbrandon: Further how are you parsing the build-deps? Will it pull the build-deps from the apt-cache or from debian/control? [07:04] * persia attempts to calculate timezones and reviews backscroll [07:04] they way i did it it will get them from the debian/control of the last one in the archive :) [07:05] imbrandon: Please don't do that: that completely breaks NBS processing. [07:05] persia: we're not talking about for something to be uplaoded [07:05] he is talking about using it for a personal build [07:05] imbrandon: Ah. OK. No worries then :) [07:06] * persia still likes dpkg-checkbuilddep [07:06] s [07:06] i do a lot of writing of new patches [07:07] pbuilder / debuild are helpful in that they already know the build process [07:10] oh wow , spam is getting worse, not just web 2.0 but "gibLink is a web 2.5 ..." [07:10] * imbrandon rolls eys [07:10] eyes even [07:10] gmail let through a spam that claimed to be from myself [07:10] heh [07:10] i complain about spam but gmail catches 90% of it [07:10] still a ton though [07:11] that makes it to my inbox [07:11] gmail's gotten better about catching russian spam [07:11] it used to not flag russian and japanese spam [07:11] i get maybe one a week [07:11] i just hate when you get 100000 returned emails for your domain becouse someone forged spam from your domain [07:12] but then i dont host a domain or place my email on my website [07:12] :) [07:12] gmail still handles my domain email but still [07:13] there's a backport of compiz? [07:13] yea, few days ago [07:13] oh, screensaver security type patches in it [07:16] Hi lionel. You are the last uploader for sword. May I request the sync for it? [07:18] warp10: which version is currently in ubuntu, and which version is in debian? [07:18] Hobbsee: 1.5.9-6ubuntu1 and 1.5.9-7 [07:19] warp10: have you seen the changelog entry for the ubuntu version? [07:19] Hobbsee: yep! [07:20] what does it say? [07:20] Hobbsee: just the sync request and Maintainer: change [07:21] the changelog has a sync request? was it a fakesync ? [07:21] imbrandon: yeah, it's a fakesync. [07:21] imbrandon: fakesync indeed. [07:21] * Hobbsee remembers it [07:21] warp10: that means that you cant sync it, as the debian and ubuntu tarballs are different. [07:21] Why was it fakesynced? [07:21] Ah. [07:22] Hobbsee: mmm... but shouldn't it be anyway synced after a version change? [07:23] warp10: the tarballs don't get synced across, if the tarball name is the same. [07:23] you have to apply the debian changes to the ubuntu package [07:25] Hobbsee: well, ok. I never met a fakesync before. Thanks for your hints! [07:25] no problem [07:26] hte next sync can happen at 1.5.10/1.6 ( when a new tarbal is released upstream ) [07:26] assuming there are still no ubuntu specific changes [07:27] that cant be dropped === nixternal is now known as _nixternal [08:27] StevenK: can I ask you about your changes to pdftk? I was looking at it and my changes are included in the Debian changes but I'm not sure if some of your changes are still needed. [08:27] Hum, wha? I made changes to pdftk? :-P [08:27] geser: Do you mind waiting until I sort out abiword? [08:28] sure [08:31] geser: Okay, let me have a look while it builds. [08:34] Debian builds now also with gcj-4.2 and g++-4.2 and it builds in a hardy pbuilder. So I don't know if those changes to the Makefile are still needed. [08:34] Otherwise the package can be synced. [08:38] geser: My only change for pdftk was a rebuild [08:38] I only added a changelog entry [08:40] StevenK: http://patches.ubuntu.com/p/pdftk/pdftk_1.40-2ubuntu3.patch lists you also for -2ubuntu1 [08:41] and the second patch has also ## general-fixes.dpatch by Steve Kowalik [08:43] Oh, ubuntu3 [08:44] Hrm. If I recall this a was a hard fix [08:46] geser: Right, I'm not certain that the Makefile patches are required anymore - if the compiler can find the paths itself, then drop it [08:47] geser: If I recall, doko asked it was built against 4.2 [08:47] ok, thanks. I'll request a sync then. [08:48] geser: Basically, the patch was to fix a build failure since it wasn't finding other class files referenced [08:49] Debian changes in their build-gcc-4.2 patch the classpath for the GCJH calls. I guess for the same purpose [08:49] Fair enough, sync it [09:33] RAOF: ping [09:41] welp i'm gonna call it an early night and see if i can get some sleep [09:41] gnight all [09:41] thanks slangasek [10:16] imbrandon: pong!~ [10:18] * persia encourages the use of Post-It™ notes when playing simulated table tennis [10:19] Gah, missed lordkow. [10:35] jpatrick: About styleclock: I was just adding a watch file, and noticed the rpath and shlibs issues. Do you remember why this package sets a private library? [10:36] persia: nop [10:36] I think upstream's dead anyway [10:37] jpatrick: Should we drop the package? I'm just trying to clean up missing watch files for Ubuntu-only packages. [10:37] with KDE4 it should be ok to drop [10:38] jpatrick: OK. I'll file a removal request. Thanks. [10:48] it this not a valid .install file: http://paste.ubuntu-nl.org/45682/ ? [10:49] jpatrick: Below ----- only? [10:49] yep [10:49] above is the error I keep getting [10:50] OK. Is there a $(CURDIR)/usr/ ? [10:50] usr/ should be debian/tmp/usr [10:51] hmm, I could leave out the usr/ since there is no other package made [10:51] jpatrick: Should be, but I'm not sure you can mix the "move bits from debian/tmp into subpackages" with raw installs (then again, I could be wrong). [10:52] Ah, if you've only one package, then dh_install isn't in multipackage mode, and that won't work at all. That's it. [10:52] next, is there really a $(CURDIR)/tmp/buildd/tork-023... ? [10:52] That just looks wrong to me. [10:53] lintian reports file-in-unusual-dir and dir-or-file-in-tmp for those files [10:53] I'm getting to get them into the right place [10:54] I suspect there's something funny with your build system. That's just not a good rule, as it will break for local builds, and will break for a version upgrade. [10:54] I have mailed upstream about it and he's very confused about what's happening [10:55] can someone review my package please. http://revu.tauware.de/details.py?package=libserial [10:55] jpatrick: The part that confuses me is why debian/tork/usr/share/man/man1/... is the wrong place. [10:56] persia: that's the thing :> [10:56] jpatrick: Could you pastebin `dpkg --contents` for the binary if you don't have those funny lines (and get the lintian error)? [10:58] persia: http://paste.ubuntu-nl.org/45683/ [11:01] jpatrick: Thanks. That's clearly wrong :) How about a buildlog? [11:02] http://paste.ubuntu-nl.org/45685/ [11:03] Also, this should really be three packages: tork-tsocks, libtorksocks1, and libtorksocks-dev [11:07] Hrm. With this many icons, I'd check the size: it might even deserve a tork-common as well... [11:08] jpatrick: OK. I think I have it. Could you paste upstream Makefile (after patching)? [11:10] persia: upstream will be estatic if you do :) being trying to get this to package for two months now: http://paste.ubuntu-nl.org/45686/ [11:12] jpatrick: That looks like Makefile.in : is that really the Makefile? [11:12] it's a Makefile.am [11:12] Ah. Could you run a build that doesn't delete afterwards, and also paste Makefile.in and Makefile? [11:14] how do you pbuild so it doesn't delete? [11:15] * persia doesn't use pbuilder and seeks support from others [11:16] you can login into pbuilder and then build it, but you will have to manually copy the files into /var/cache/pbuilder/buildd.../home/ [11:16] pochu: Thanks [11:17] I copied the src somewhere else ran "debian/rules build" from there [11:20] jpatrick: Is this CDBS, or hand-built rules? [11:21] nevermind. I just checked the build-deps (headsmack) [11:35] Should merging of packages in main be left to -core-dev? [11:36] slangasek: Regarding Alpha 1: how does that affect universe? Should we be targeting wiping the NBS list, or is it not as critical? As universe doesn't really affect the CD, would you prefer a universe freeze, or is it not essential? [11:36] persia: soyuz will force it all to freeze, if it's like usual, universe gets a manual shove [11:36] james_w: It depends. If you know the package well, and have worked with it before, you can go ahead. [11:36] erm. which i still can't do. bugger. [11:36] Hobbsee: Not based on the recent mail to u-d@ [11:37] persia: no I don't/haven't. [11:37] james_w: If you're not a previous contributor to the package, it's best to leave the merge, unless you're working with a previous contributor. [11:37] persia: that makes sense. However I didn't notice until I'd actually done the work. [11:37] james_w: In that case, best to leave it. Sponsoring into main can take a while, and the packages are all assigned to specific developers. [11:38] persia: oh, ignore me. i havent actually read teh mail yet. [11:38] Hobbsee: I try, but somehow I find it difficult :) [11:38] hi [11:38] hey RainCT [11:38] james_w: or ask the last uploader to review it if he can [11:38] persia: :P [11:39] Hmm. I have a main merge. Oops! [11:39] I'm merging classpath and it has the following Ubuntu specific changes: * Add /usr/include/xulrunner to CLASSPATH_INCLUDES in configure * And MOZILLA_CFLAGS are those required for something or might just be needed for it to build? [11:40] RainCT: Those are required to get the mozilla classes in the classpath. I'd check in #ubuntu-mozillateam to get a better understanding about them [11:40] thanks persia [11:41] slangasek: where can i find the information on what was discussed w.r.t the release team, at UDS? [11:41] james_w: No problem. Thanks for asking. [11:43] Is KDE4 targeted for hardy, or will it still be KDE3.x? [11:43] persia: ok, thx [11:43] persia: it'll be there, but not by deafult [11:43] Right then. I shan't remove styleclock, just fix it. [11:46] persia: aha, I got the Makefile http://paste.ubuntu-nl.org/45690/ [11:47] even tho it says Makefile.in... [11:48] jpatrick: Makefile.in isn't Makefile, but it's closer :) [11:48] that was the Makefile in /tmp/build/obj-linux-thingy/src/tsocks [11:49] jpatrick: Now I'm confused. This is Makefile or Makefile.in? [11:49] Makefil [11:49] -e* [11:50] * persia hopes '*' doesn't indicate shell expansion :) [11:50] nop, correction :) [11:56] jpatrick: Found it: line 66 sets the install directory to $(DESTDIR)$(torksocksmanpagedir), and line 412 sets torksocksmanpagedir to $(DESTDIR/$(mandir)/man1, which is a clear duplicate. [11:56] The next step is to look at Makefile.in, to try to figure out why that happens, and the final step is to adjust Makefile.am to make it not happen. [11:57] persia: ok, will do [11:58] jpatrick: Good luck, and thanks for tracking this down rather than trying to work around it with dh_install. [11:58] DaveMorris: still about? [12:00] Hobbsee> Out of curiosity, will KDE4 be in universe or main? [12:01]