[00:15] ScottK: woot, going for DM [00:37] LaserJock: dungeon master? :) [00:37] heh, something like that === bmk789_ is now known as bmk789 === bmk789 is now known as ChuckNorris === ChuckNorris is now known as bmk789 [01:17] Chuck ? [01:18] shitty gary gygax has passwed away [02:12] effie_jayx: poke [02:15] Heya gang [02:20] bddebian: 'lo! [02:20] Heya crimsun_ [02:21] Heya crimsun_, bddebian. [02:22] Hi RAOF [02:23] hi bddebian, crimsun_ , RAOF [02:23] Heh, heya LaserJock [02:23] Hey folks. [02:23] (Easier to do. :p) [02:24] Hi TheMuso... :-) [02:24] 'lo RAOF, LaserJock, TheMuso === freeflyi1g is now known as freeflying === wolfger_ is now known as wolfger === Pici` is now known as Pici [02:57] Hobbsee, yep??? [03:13] TheMuso: I may need you to upload soonish (or post-Alpha 6 - up to you guys now) [03:13] err, sorry, alsa-driver being the source. [03:14] crimsun: Probably post alpha 6 is the best bet atm, but sure I can take care of it. [03:15] TheMuso: thanks. Given post-Alpha 6, then, I'll ping you. [03:15] crimsun: Sure. [04:00] is there a link on the ubuntu wiki that says how to make a .deb? i checked ubuntuforums and found a guide but its not like easy to follow...i dont like guides that always lead u to clicking other links, i like it all in 1 page [04:00] D-Unit: I suggest you search the wiki for the packaging guide, and go to http://wiki.ubuntu.com/MOTU to be linked to further information. [04:05] effie_jayx: can you fix libapache2-mod-python please? at least in gutsy, it appears to depend on 2 versions of python. [04:08] TheMuso, https://wiki.ubuntu.com/PackagingGuide ? [04:08] D-Unit: I'd say thats the one. [04:08] k, thx [04:57] oh man, it's awesome when Debian fixes things :-) [04:57] I thought my fitting program was gonna be toast [05:07] * cody-somerville is actually pretty impressed with his interactions with debian. [05:07] I had heard all this bad stuff [05:08] I think the deal is that "Debian" as a whole is not a valid unit of social interaction. [05:08] that' strue [05:08] some are nice, some aren't. [05:09] You can have excellent dealings with individual maintainers, but if you try to interact with "Debian" (by, for example, attempting to become NM), it's icky. [05:09] All DDs I've worked with have been great. [05:09] It seems Debian is so big that cliques form [05:17] * bddebian refrains from comment [06:01] cody-somerville: how dare you say that Debian is cliquish, I'm not sitting with you at lunch anymore [06:01] slangasek, hehe :D [06:01] * cody-somerville makes a note to sit by slangasek at the UDS. [06:04] it's amazing what Debian talks about on it's mailing lists [06:04] they really like to hash stuff around [06:04] (not that we don't at all) [06:05] reading debian-devel and debian-project can be really interesting [06:05] the mailing lists are important for staying on top of where things are going... but they're definitely not where the work happens. :) [06:06] btw, I sent in my application for DM yesterday :-) [06:06] and ScottK sent his in today [06:07] I noticed that, cheers to the both of you [06:07] hopefully I won't get booted out in the first week ;-) [06:11] :D [06:12] I hope DM will be a real good initiative for Debian [06:13] I know it's been a motivator for me [06:15] oi oi [06:15] LaserJock: dm? Is this the same as NM? [06:16] DM is not the same as NM [06:16] TheMuso: no, it's different [06:16] Right [06:17] Debian Maintainer is for people who don't want to be full Debian Developers yet [06:17] Ah. [06:17] they are limited to packages they are a Maintainer or Uploader for [06:17] http://wiki.debian.org/Maintainers === Fujitsu_ is now known as Fujitsu === Lutin_ is now known as Lutin === txwikinger2 is now known as txwikinger === doko_ is now known as doko === fabo_ is now known as fabo === ogra__ is now known as ogra [08:27] morning people === harrison1 is now known as harrisony === asac_ is now known as asac === soren_ is now known as soren === \sh_away is now known as \sh [09:52] <\sh> damn..why people assign randomly bugs, just because there is one who uploaded...grmpf [10:07] \sh: Because they don't understand the process. And want to make you look bad :) [10:08] <\sh> RAOF: I blame sbuild ,-) [10:08] \sh: Yeah, wierd bug. [10:08] <\sh> because wine works with pbuilder / manual build [10:11] Which bug are we talking about? [10:12] soren: The bug where wine segfaults on everything if built in sbuild/buildd, and doesn't when built in pbuilder. [10:12] Sounds like fun. Compared build logs? [10:13] You'd want to ask \sh that :) [10:13] <\sh> soren: wine crashing [10:14] <\sh> soren: I compared everything...there is no change...I also removed dh_strip to get rid of some problems with it... [10:15] <\sh> soren: funny though: using a snapshot chroot, which is also used for sbuild, and do a manual build...wine works...using sbuild directly -> package binaries -> crash [10:17] <\sh> soren: so I think something strange happens when building the package...and there is a difference between sbuild and pbuilder [10:19] A guy posted to the bug with his ./configure output. [10:19] <\sh> but I'm at the end with my knowledge, or as you say in german "ich bin am ende mit meinem latein" [10:19] It's different from the build logs from launchpad. [10:20] checking for -lXi... not found [10:20] <\sh> soren: yes...because he doesn't do the magic we did [10:20] checking for -lXinerama... not found [10:20] On Launchpad. [10:20] <\sh> soren: this is already resolved [10:20] <\sh> soren: a temp problem...(which is not the cause of the crash) [10:21] Did you compare the full build logs? === warp10 is now known as warp69 [10:22] <\sh> soren: yepp....I can reproduce this on any compile host I have...the build logs are the same and even the compile output of the manual build compared to the sbuild log (minus the package building process) [10:24] <\sh> and if someone has time and wants to help...it'll be appreciated :) I'm lost for now [10:25] Do you happen to have the build logs handy from pbuilder where it works? [10:26] <\sh> soren: my sbuild logs are still available..pbuilder i have to recreate one... [10:26] * \sh is just building another one...I have to md5sum check the binaries from the package with the ones I build manually [10:27] <\sh> soren: I'll publish them when I have the pbuilder logfile.. [10:28] \sh: in the bug report you wrote wine does *not* work when built in pbuilder, and it doesn't work for me either. I have a fix to make the pbuilder working again. [10:29] <\sh> albert23: somehow my last pbuilder try worked...sbuild didn't [10:29] <\sh> albert23: what did you change? [10:30] \sh: sbuild is not really interesting. Launchpad has those, and it's the case where it doesn't work. I want to compare to the case where it *does* work. [10:30] \sh: problem is the standard LDFLAGS to default value: -Wl,-Bsymbolic-functions set by dpkg-buildpackage [10:30] <\sh> soren: yepp..you'll get the pbuilder output :) [10:31] \sh: if I reset LDFLAGS and make sure not to strip, it works again [10:33] Wine is like a half hour build or thereabouts, no? [10:33] \sh: this is my debdiff: http://pastebin.ubuntu.com/5308/ [10:33] \sh: it makes dh_strip and dbgsym creation work again as well [10:34] It claims to also fix the segfault? Is that accurate? [10:34] soren: yes it is [10:34] \sh: see also http://www.winehq.org/pipermail/wine-bugs/2007-July/062505.html [10:37] <\sh> hmm...give me a shot... [10:38] Hobbsee, ping [10:38] \sh: note the Unexport FLAGS set by dpkg-buildpackage was not needed and is commented out in debian/rules [10:40] <\sh> albert23: yepp..could you push your change towards the bug report? (bug #191575) [10:40] Launchpad bug 191575 in wine "wine segfaults on winecfg" [High,Confirmed] https://launchpad.net/bugs/191575 [10:41] \sh: yes I will, after first cleaning up the unneeded change [10:41] <\sh> albert23: much better, if you could checkout the wine debian/dir from ubuntu-wine project [10:41] <\sh> s/project/team/ [10:41] <\sh> albert23: https://code.edge.launchpad.net/~ubuntu-wine/wine/ubuntu-debian-dir :) [10:43] \sh: sorry, I have not used bazaar before.... [10:52] <\sh> albert23: ok..I#ll do it then when it works :) [10:52] <\sh> but first lunch...bbl [11:19] effie_jayx: pong [11:19] \sh: [11:19] \sh: because they expect you to fix it if they assign it to you. duh. === bmk789_ is now known as bmk789 [11:31] If i change the /etc/pbuilderrc file distribution to hardy from gutsy, then run sudo pbuilder update --override-config, that will update my pbuilder to hardy successfully?' [11:32] Probably not. [11:32] AFAIR distributino is only really used at creation time. [11:32] soren: ok, whats the correct way to upgrade pbuilder then? [11:33] delete the base, change the distribution and run pbuilder create again? [11:33] You need to either create a new pbuilder from scratch (which I recommend) or change the source.list in your current pbuilder and then run the command you mentioned. [11:33] * soren needs food, so goes to lunch [11:33] ok [11:33] thanks [11:54] jdstrand, heya :) [11:54] hi emgent! === mrpouit is now known as mr_pouit [12:05] <\sh> albert23: you are the hero [12:06] \sh: :-) [12:07] <\sh> albert23: would you like to give me your realname? [12:07] \sh: it's in the debdiff [12:11] Is there anyone later today who can help me uploading Phatch & SPE? [12:12] jdstrand, i have some debdiff for your todolist :P [12:12] great! [12:23] sorry, wrong channel === cprov is now known as cprov-lunch [12:35] could someone remove the existing gnome-lirc-properties_0.2.2-0ubuntu1.dsc package, please? it is broken. [12:36] hmm... or should dcut do the job? [12:49] Does anyone know if LZMA is default compression for packages now? [12:49] hi, I'd like to know if I could upload a new package on revu even if it is "feature freeze" [12:53] slytherin: no and yes [12:53] jmehdi: you can. likely no one will look at it [12:53] slytherin: no for most, yes on some large packages [12:54] jdong: large packages like OOo? [12:54] slytherin: the compression and decompression costs of LZMA are usually several orders of magnitude away from that of gzip/bzip2 so it's not globally enabled [12:54] slytherin: and yes OOo is one of the LZMA'ed packages [12:54] cool [12:54] indeed [12:55] the other cool thing is that it brings "lzma" into main and installed by default [12:55] which for modern PC's is a great alternative to gzip [12:57] meh....dislike doing ffe [12:59] "Bug Fix." I swear. ;-) [13:01] sure...:) [13:05] bug #198731 [13:05] Launchpad bug 198731 in lighttpd "[CVE-2008-1111] Failure to Handle Exceptional Conditions " [Undecided,Confirmed] https://launchpad.net/bugs/198731 [13:14] Hello [13:15] I read in the policy that the distributions field in changelog can be a space separated list of distributions. Does that actually work with the build system? === cody-somerville is now known as somerville32 [13:20] mok0: that part is from the old Debian ages, I don't think Ubuntu is using it [13:21] azeem: ok. Seems smart though. Although I don [13:21] t think the distribution information belongs in changelog [13:21] "distribution" as in "hardy", "hardy-backports" etc. [13:21] azeem: yes [13:21] why wouldn't it belong into changelog? [13:22] azeem: because it's a silly to have to create a new changelog entry just because you are compiling a package under a new distribution [13:22] that doesn't follow [13:22] azeem: no? [13:23] you can override the distribution in the .changes file [13:23] azeem: how do you do that? [13:23] vi foo.changes [13:23] :-) [13:23] azeem: because it's a silly to have to create a new change file entries just because you are compiling a package under a new distribution :-) [13:23] well, it's what the Ubuntu autobuilders do with synced Debian packages I guess [13:24] azeem: I think the logical association is that a distribution is a set of packages. A package does not necessarily have anything to do with a distributgion [13:25] In fact, a package can be part of many distributions. [13:25] a source package mabye [13:25] maybe* [13:25] Therefore, it doesn't make sense to define the distribution in changelog [13:25] binary packages tend to get rebuilt for the respective distribution [13:25] azeem: the changelog documents the source package [13:26] azeem: exactly: from the same source [13:26] mok0: well, what's your use case? [13:26] upload the same source to hardy and dapper-backports? [13:26] azeem: I have a bunch of packages that need to be compiled unchanged for hardy [13:26] upload the same source to unstable and hardy? [13:26] mok0: unchanged fro what? [13:26] from* [13:26] azeem: unchanged from gutsy [13:27] azeem: I need to process them all manually to correct the distribution in debian/changelog [13:27] why would you upload package to gutsy at this point? [13:27] * slytherin wonders why the heck OOo fails to build on powerpc [13:27] azeem: we run gutsy on almost all machines [13:28] <\sh> WINE WORKS AGAIN YEEHAA [13:28] does it make sense for apache to have two pyton versions in the depens line? [13:29] mok0: and where are you uploading to? [13:29] azeem: a local repo [13:29] so autobuild the package for gutsy from there [13:30] azeem: autobuild? [13:30] buld the hardy source package for gutsy [13:31] I don't see why you would have to change debian/changelog in this case [13:31] azeem: you mean, just override the distribution? [13:31] yes [13:31] doesn't pbuilder (or whatever you're using) have an option for that? [13:31] sbuild has [13:32] azeem: I haven't seen one for pbuilder... I'm not (yet) using sbuild, although I plan to [13:33] azeem: In fact, I'd like to have a complete building environment, like that in the PPA [13:33] azeem: because I need to build for several distributions and 2 archs === lmr_ is now known as lmr[brb] [13:50] tbf: a bit late, but dcut doesn't work on REVU [13:51] RainCT: so some demigod has to cleanup it seems? [13:51] ah! revu's demigod did! :-D [13:54] Hmm. Major upset in openoffice in today's hardy upgrade [13:54] Yeah. Excellent excuse to yank the sucker out. I like it. [13:55] soren: Harsh words on an otherwise innocent Wednesday... [13:57] <\sh> what's wrong with our beloved office app? ,-) [14:01] apart from that it is blazing fast. :-P === lmr[brb] is now known as lmr [14:03] \sh: I'm assuming that's a rhetorical question.. :) [14:04] <\sh> soren: kind of ;) [14:05] Good. [14:05] :) === asac__ is now known as asac [14:13] Trying to figure out what cdbs' tarball.mk is good for. Anyone knows? [14:16] it's for orig.tar.gz's which contain other (possibly multiple) tarballs === ubotu is now known as ubotu` === ubotu` is now known as ubotu === txwikinger2 is now known as txwikinger === Ibalon is now known as zakame === tb1 is now known as tbf [14:48] \sh: congratulation :) [14:48] <\sh> hellboy195: no give your congrats to albert23 :) [14:49] \sh: true but you also put a lot of work and time into it ;) [14:57] <\sh> hellboy195: that's one of the duties...:) [14:58] heya [14:58] <\sh> hellboy195: the only rant i have, the bug was known to wine bugzilla..but was set to closed/invalid [14:59] \sh: I liked the explanation: Don't mess with linker flags unless you understand exactly what they do. Now what would the dpkg developer think of that? [15:00] \sh: grrr [15:01] <\sh> albert23: regarding the wine bugreport...it's wines fault...or better not wines fault, but it's an exception I would liked to know earlier...and it's not any other ones fault of a misbehaving wine...I think wine needs a status like mplayer, which is pushing their own LDFLAGS too [15:02] <\sh> s/their/its/ [15:10] <\sh> albert23: the fun part about this bug is, that the bugreport was set to closed/invalid, but actually it's not invalid neither should it be closed... === warp69 is now known as warp10 [15:11] \sh: yeah, at least they could have given a bit more explanation. [15:14] <\sh> albert23: so for the next time, I need to refine my searches to include invalids/closed bugs too ,-) [15:15] \sh: Maybe. Actually, first I found the fix. Only when I tried to validate the fix I found that bug report [15:16] <\sh> albert23: well, after 2 weeks trying to search what was the cause, you don't see the obvious... [15:16] <\sh> 4 weeks actually [15:17] \sh: it's just that I was caught by those standard flag settings before that made me try this [15:19] <\sh> albert23: which source was it? :) [15:20] \sh: that was gcal. First it build fine, suddenly it was FTBFS [15:20] Heya gang === _czessi is now known as Czessi [15:26] <\sh> albert23: but it was CFLAGS in gcals case ... but yes... === Zic_ is now known as Zic [15:39] jdstrand, another debdiff for your todolist :P [15:39] bug #198731 [15:39] Launchpad bug 198731 in lighttpd "[CVE-2008-1111] Failure to Handle Exceptional Conditions " [Medium,Fix released] https://launchpad.net/bugs/198731 [15:39] hardy fixed by \sh, gutsy, feisty, edgy, dapper ready and tested. [15:41] \sh: It this a good wine to backport and did you see the note I left for you about kdeguidance wineconfig? [15:42] emgent: ok. thanks! [15:42] <\sh> ScottK: you can try :) and no..I didn't get the note [15:43] \sh: Would you please look at the wine related debdiff in Bug #151982 and tell if you think we should do that? I'm preparing a kdeguidance upload over the next few days. [15:43] Launchpad bug 151982 in kde-guidance "Wineconfig doesn't detect Wine" [Medium,In progress] https://launchpad.net/bugs/151982 [15:47] <\sh> ScottK: regarding /usr/local/lib* I think it has to follow the very same rules as /usr/lib*...but I would even drop the /usr/local/lib* check complety [15:47] <\sh> ScottK: and yes, the patch is fine :) [15:48] \sh: Thanks. [15:48] The local bit's in there from upstream, so I'll probably leave it. [15:48] User install stuff in /usr/local it's their problem. [15:49] <\sh> ScottK: so go ahead :) [15:50] Main's frozen until the last alpha is released. Unless someone kvetches about the version I have in my PPA, I'll upload it after the freeze is off. [15:51] <\sh> ScottK: yepp... [15:53] <\sh> crimsun: are you working on a fix for libflashsupport? === santiago-php is now known as santiago-ve === asac_ is now known as asac [16:17] ScottK, did superm1 get you what you needed yesterday re: kde-guidance? [16:17] mdomsch: No, but it's a few days yet, so as long as I get it from one of you soonish. [16:20] mdomsch, sorry i got disconnected yesterday when you mentioned my name w/o a log. what was needed? [16:20] I had a bug at one point against kde-guidance, needing new MonitorsDB file from upstream [16:21] the copy in the kde-guidance upstream tarball is by definition out of date [16:21] you said that you have some of those guys using hwdatadb on the same page, i'm guessing kde-guidance isn't? [16:22] https://bugs.launchpad.net/ubuntu/+source/kde-guidance/+bug/157321 [16:22] Launchpad bug 157321 in kde-guidance "28 new Dell monitors for MonitorsDB file" [High,Fix released] [16:22] So the question would be are there more? [16:22] everything is marked fix released on that bug? [16:23] says 'fix released', but there are plenty more... [16:23] in fact, exactly 29 [16:23] 28 more [16:23] superm1: I'm uploading a new kde-guidance after the freeze is over, so I'd like to get that wrapped up into it. [16:24] ScottK, should just be a matter of grabbing the latest MonitorsDB on that git tree i'd expect [16:24] and dropping it in place [16:24] ScottK, http://git.fedorahosted.org/git/hwdata.git?p=hwdata.git;a=blob_plain;f=MonitorsDB;hb=HEAD [16:25] is the new upstream for that file [16:25] superm1, right [16:25] OK. I can do that. [16:26] mdomsch, ScottK realistically i think it'd be a better idea to stop shipping different MonitorsDB files in different packages, but rather symlink to a "single" MonitorsDB and keep that in sync (add it as a dependency to all the others) [16:26] it's probably too late to do that for this cycle, but its something we should look at doing for Intrepid [16:27] superm1: I agree. [16:27] Both with doing and it's to late for this cycle. [16:27] superm1, I agree too [16:27] the hwdata package in hardy is up-to-date right now with the hwdata git tree [16:27] ScottK, so if you want to have a small BoF at UDS this time around, all that can get organized there [16:28] that's where I would expect to see the file live, and kde-guidance get a dep on hwdata [16:28] i can write a spec for it [16:28] superm1: Please do. We need to totally revisist displayconfig for Kubuntu for Intrepid in any case. [16:28] alrighty :) [16:29] huh, hwdata shouldn't be quite up-to-date, let me rerun my script [16:30] mdomsch: It'll be a bit before I get to it. [16:31] hwdata is in main btw, as is kde-guidance, so no cross problems there [16:32] mdomsch: Could you also please add this monitor while you're adding so I don't have to maintain it as an Kubuntu unique difference: Bug #192899 [16:32] Launchpad bug 192899 in kde-guidance "New monitor Viewsonic VA702B in MonitorsDB" [Low,In progress] https://launchpad.net/bugs/192899 [16:32] ScottK, sure, one sec [16:36] ScottK, pushed upstream [16:36] Great. [16:38] ScottK, if you're going to have a bunch of those, we can get you commit rights on the upstream repo [16:38] mdomsch: I probably won't. I only hit that one because I'm preparing an kdeguidance upload and was trying to cherrypick through the other open bugs and get the easy ones. === cody-somerville is now known as somerville32 === _czessi is now known as Czessi === \sh is now known as \sh_away === ogra_cmpc is now known as ogra [18:06] DarkSun88: Around? === Ubulette_ is now known as Ubulette [19:05] ScottK: for libdb transition, which package should be used in the build-dep: libdb4.6-dev or libdb-dev ? [19:06] libdb4.6 [19:06] mathiaz: I'd use libdb4.6-dev so you aren't suprised [19:06] Are grepping for transactions in the source code is enough ? [19:06] mathiaz: im working on cyrus-imap its a bit more complicated [19:06] or is it transaction ? [19:07] zul: What I told them to do was grep for the word transaction in the package and leave it alone if they found it. [19:07] ScottK: ok - thanks. [19:07] ScottK: ah ok [19:08] Trying to get less experienced folks to knock out some of the easy ones. [19:08] ScottK: and by them you mean ? [19:08] mathiaz: You and others when we discussed it in the server team meetings === slangase` is now known as slangasek [19:08] ScottK: ok. [19:09] ScottK: if transactions are used, what are the issues ? migration ? API breaks ? [19:09] You have to migrate the data to a new structure. [19:09] mathiaz: Look at pitti's liddb4.6 transition patch in cyrus-sasl2 for an example. [19:10] ScottK: ok. So existing datas have to be migrated. However the source code doesn't need to be updated ? [19:11] As I understand it, yes. [19:11] ScottK: ok. Thanks :) [19:12] mathiaz: however some the api has changed as well like smtpguard [19:12] and cryus-imap as well [19:13] zul: when do you catch that error ? when building the package ? [19:13] correct === \sh_away is now known as \sh [19:23] <\sh> re [19:39] persia: FYI, the new gnuvd is in Hardy now :) [19:49] * \sh hates wireshark ,-)= [19:51] \sh: uhh updating wine right now. *Love ya* :D [19:52] <\sh> hellboy195: beer at linuxtag is appreciated ;) [19:52] \sh: I would do it if I'd be there :\ [19:53] <\sh> hellboy195: you need to come :) [19:53] \sh: no time, no money :( [19:53] * ScottK hands \sh https://wiki.ubuntu.com/UbuntuDevelopment#Removals [19:53] ;-) [19:54] <\sh> ScottK: lol yeah...it would be better if we could just inject new upstream versions for wireshark...that would stop my headaches ;) [19:54] <\sh> cherrypicking patches is boring ;) [19:54] <\sh> and bug # [19:55] <\sh> bug #172283 is really a long list...downto dapper;) [19:56] Personally I have a very strong policy of never running wireshark on a machine that's not well hidden behind an external firewall. I assume it's got security trouble. [19:56] If I have to do stuff on the internet I use tcpdump. [19:57] <\sh> ScottK: I wonder really who the guys are finding out all those issues...I think they don't have a real life(tm) [19:57] It's a popular package. They do say that with enough eyes all bugs are shallow. [19:58] <\sh> ScottK: yes, but presenting a malicious mp3 is really art [19:58] Yes, but the world if full of artists. [19:59] <\sh> -ERIGHT:) [19:59] Last night I went with my wife to see a seamstress about making a dress for her (my brother is getting married next month). While we were there she was trying to go to the web site of a dress pattern maker and apparently get a typo. === kuechengarten is now known as thekorn [20:00] She ended up with a pop-up recommending she download some 'security' software. [20:00] Fortunately she thought before clicking to accept the install and asked me (knowing I know a bit about computers) [20:00] Dunno what would have happened if I hadn't been there. [20:01] <\sh> ScottK: I hope she bought you a nice old bottle of [20:01] Well she and my wife are still haggling the price of making the dress. I'm hopin it factors in there. [20:02] <\sh> hehe [20:21] <\sh> bah....one CVE but already fixed with an old one...what the heck are they doing [21:06] good night people === neversfelde_ is now known as neversfelde [21:10] * Fujitsu incinerates scipy. [21:10] Yeah! [21:11] I think I've finally got it building on all archs. [21:11] It doesn't like it on any arch if LDFLAGS is set at all, but works with FFLAGS set everywhere except amd64. [21:27] ScottK, do native packages require a FFe if they ship only bugfixes? [21:27] No. [21:28] Thanks. [21:39] <\sh> oh damn... [21:40] \sh: So wine joy? [21:40] <\sh> RAOF: much better...my second package I'm buggin in, wireshark [21:49] \sh: Oooh, someone's fixed dh_strip for wine, too! [21:50] <\sh> RAOF: na..the fix is -X ;) [21:50] <\sh> RAOF: but that was already in my local debian/ dir [21:50] Oh. Well, it's still 1/3 the size of before :) [21:53] <\sh> RAOF: well, it should have the size of gutsy again (with some bytes more) === \sh is now known as \sh_away [23:14] zul: can you have a look at bug 182571 and include it in the samba merge ? [23:14] Launchpad bug 182571 in samba "smb.conf(5): Poor backspace escaping" [Wishlist,Confirmed] https://launchpad.net/bugs/182571 [23:17] yuck, what's it take to fix the tools being used to generate the manpages? [23:42] jdong: Ignoring the Main/Universe split for backports is definitely there again. Please complain. [23:47] ScottK: bug filed [23:47] Great. [23:47] now we... wait :D [23:48] Any tool/program to wrap a text file in 80-col format ? [23:49] kate? [23:54] par? [23:57] vim?