[00:00] kees: http://jdong.mit.edu/~jdong/usnramble.txt (WARNING: HUGE FILE) [00:01] jdong: *rofl* so I guess it doesn't do highest-rated output? heheh [00:01] I think you need slightly longer chains. [00:01] wgrant: that's what she said. [00:01] I mean... working on it. [00:03] Some of it looks quite real. [00:04] jdong: you were bored, I take it [00:04] ajmitch: isn't that when I'm the most dangerous? :) [00:05] Chuck McAuley reported that the [00:05] security context of the function XULDocument.persist() did not sufficiently [00:05] check the length of netbios packets [00:05] that's when we start running for cover [00:35] Ok, my packages are built! [00:36] http://ubuntuforums.org/showthread.php?p=6163764#post6163764 [00:36] now I am a bit tired [00:37] goodnight everyone and thanks for all the help! === Guest51470 is now known as jrib === jrib is now known as Guest25082 === Guest25082 is now known as jrib [00:59] i need some packaging help. i ran debuild -S -sa and it failed saying secret key not available even though my private key is visible in Seahorse [00:59] maco: With an identical UID to that mentioned in your changelog? [01:00] wgrant: um, do you mean the email address listed? [01:01] yes, the email address used in debian/changelog is on my private key [01:02] maco: The full name, the comment and the e-mail address all need to match [01:02] the name and the email address do, though i dont believe the comment goes anywhere in debian/changelog [01:02] maco: Compare the uid lines from gpg --list-secret-keys to the Changed-By field in the .changes [01:03] They need to match exactly [01:03] If not, add -k to debuild [01:04] .changes? [01:04] maco: Yeah, such as krecipes_0.9.1-4_source.changes [01:05] maco: I'm not sure if debuild actually generates one, sorry. [01:05] the Changed-By field matches my uid [01:05] maco: If you're not sure, comparing what's in debian/changelog versus gpg --list-secret-keys should be fine [01:05] well, except for the comment [01:06] are you supposed to include the comment somewhere? [01:06] yes. [01:06] and yeah, now that you mention -k, i do recall having to specify my key id whenever the last time i made a package was [01:06] The strings must match precisely. [01:06] oh. where's the comment supposed to go? in changelog? [01:06] Because your key has a comment and your entry in debian/changelog doesn't. [01:07] maco: Your Name (Comment) [01:07] The same place it goes in your secret key. [01:07] i just meant, is it supposed to go directly in changelog or is it supposed to be in some config file [01:07] but ok, sounds like you mean in the changelog [01:10] thanks guys [01:10] * StevenK kicks nm-applet for hiding [01:11] StevenK: Probably means that NM isn't running. [01:11] root 5603 0.0 0.0 54652 1324 ? Ss Nov03 0:00 /usr/sbin/NetworkManager [01:11] I ignore NM on this machine, so I suspect I told the applet to go away and stop bothering me, but now I want it back [01:12] What does nm-applet say if you run it in a terminal? The service is already taken? [01:12] Ah. [01:12] wgrant: Yup, the service is already taken [01:13] Is nm-applet already running, or is this a case of NM being crap like it is on one of my upgraded boxes? [01:13] It's running [01:13] Kill NM dead. /etc/init.d/NetworkManager stop might not kill it hard enough. [01:13] NM 0.7 can be very strnage.... [01:13] My feeling is there might be a gconf key [01:15] Seems I'm wrong [01:15] * StevenK gets out the Big Hammer [01:15] Which big hammer? [01:16] Killing NM dead [01:16] Ah. [01:19] StevenK: yeah get rid of the mofo [01:42] How do I go about finding whether a given package has different versions in backports and proposed repos? [01:42] If this version of uvcvideo has an update in proposed, I may just want to enable those, and if it doesn't, I'll probably end up compiling the driver [01:43] ...but then, that's probably in some big package with all the other kernel drivers... [02:35] question... isn't SIGHUP supposed to be sent to the processes attached to a pty whenever the master side is closed? no matter how it is closed? [02:37] for some reason it looks like SIGHUP is not sent to background processes when you exit from the shell, but IS if you close the terminal.. I could swear it should be sent no matter what causes the controlling process to exit [03:03] are there plans to update the version of Eclipse in the repos anytime soon? the repo is two releases behind [03:05] sjdurfey: 3.2.2-6.1 is in Debian unstable. We should probably have that in the repositories in the next few weeks. We just need someone to merge/sync it [03:06] why another 3.2? eclipse is on release 3.4 [03:06] sjdurfey: I doubt that Debian will upgrade to 3.4 until after Lenny is released. [03:07] is there any particular reason for that? [03:07] Eclipse isn't known for being trivial to package, nor overly stable, I suspect. [03:08] And it's not likely to get a release freeze exception. [03:09] that makes sense [03:12] sjdurfey: If someone wanted to package 3.4 for Ubuntu, it's probably get in. So far no one has. [03:13] I don't think we've got anybody strange enough to package Eclipse... [03:13] i dont have the slighest idea on how to package [03:14] * ajmitch will refrain from putting his hand up for it [03:15] Right, well that's been the general consensus. [03:15] its so hard to package eclipse that no one will volunteer to do it? [03:18] Does eclipse still build the swt-gtk libraries that other java apps use? [03:18] It's not so much hard as unique and very resource intensive. Last time I looked at it it wouldn't even compile on a box with less than (IIRC) 2GB of RAM. [03:18] RAOF: One way to find out ... [03:19] wow, thats a whole lot of ram [03:19] As I said, painful. It might have been 1, not 2. I don't remember for sure. [03:20] * ScottK did some work on it about a year ago and learned his lesson. [03:20] haha [03:24] how is packaging done? [03:32] sjdurfey: https://wiki.ubuntu.com/PackagingGuide [03:33] thanks [03:35] wow, there is quite a bit to read there [03:43] * ajmitch wonders why gcc just doesn't want to work in pbuilder on the laptop [03:44] probably some package missing, but build-essential is there at leasy [03:49] hmmm, i found out what motu stands for, and im thinking learning how to package and helping where i can would be a great learning experience for me [03:55] sjdurfey: https://wiki.ubuntu.com/MOTU/Contributing [03:56] thanks [03:57] No problem :-) There is also https://wiki.ubuntu.com/MOTU/GettingStarted [03:58] does a motu just deal with packages, or is there also coding going on as well? [03:58] Fixing bugs => coding [03:59] If you are a pure coder, there is Ubuntu Core Developer, the other tech role in Ubuntu... [04:00] yeah, im def. not to the point where i can contribute patches and what not. hopefully i will be, i just need to find the time [04:01] Fixing documentation and packaging bugs is very much needed ... do what you can! [04:02] ill read the guides and what not to see what i can do to contribute, i very much want to be part of the open source community [04:03] It's big enough that there's room for everyone, if you're willing to make the effort to actually contribute. Writers, graphic artists, translators, ... lots of roles other than the traditional coder/developer/network admin stuff [04:05] i would like to stick with the coding, bug fixing, patching, etc. im a CS major and would def. love to learn more about coding for linux [04:06] In that case... jump in :-) [04:06] i will, i guess school work will have to be pushed to the side a bit :P its keeping me from more important things [04:07] * jmarsden graduated with a B.sc in Computing and Information Systems... back in 1983 :-) [04:08] mines going to be a B.A. i was originally a psych major so i had tons of arts & humanities built up when i switched to CS, so a B.A. would have been quicker to complete rather than a B.S. [04:08] Ohhh. Someone even older than me .... [04:08] Watch it :) [04:08] that cannot be possible! [04:08] Bah. You youngsters. [04:08] ScottK: don't worry, I saw a DD in the street yesterday, I think he's about 70+ [04:08] DD? [04:09] debian developer [04:09] ahhh ok [04:10] sjdurfey: If you decide the MOTU path is the one you want to take there is a mentoring program you can use if you want... https://wiki.ubuntu.com/MOTU/Mentoring [04:11] ill look into that, thanks a lot. i think a mentoring program is a great idea for beginners! there is so much information out there it can be duanting [04:11] bddebian: I'm sure you remember the name philip charles [04:11] sjdurfey: Plus there are generally people here to answer questions. The formal mentoring program is not at all required. [04:12] Feel free to roll up your sleeves, dive in and ask questions as they occur. [04:12] persia: thanks ! [04:12] thats awesome. i love how nice the people in the ubuntu chans are. i certainly cannot say the same for the programming channels however.... [04:13] i listened to Jono Bacon give a speech about that very thing a couple months ago at the Ohio Linux Fest [04:13] ajmitch: Absolutely, I was just going to ask if that was who you were talking about :) [06:49] good morning [06:50] Morning Daniel. [06:50] hi Iulian [07:11] <\sh> moins [07:11] 'ey === doko_ is now known as doko [07:44] Does anyone have any ideas why I get this lintian error: dpkg-awk: shell-script-fails-syntax-check ./usr/lib/awk/dpkg-awk.lib ? [07:44] Running sh -n dpkg-awk.lib gives me dpkg-awk.lib: 34: Syntax error: word unexpected (expecting ")") [07:44] But it doesn't seem right. [07:45] dpkg-awk.lib file contains http://paste.ubuntu.com/71254/plain/ [07:53] iulian: Does running it with sh -nv help at all to see where the error is? [07:54] morning ! [07:59] jmarsden: Not really, this is what I got http://paste.ubuntu.com/71263/ [08:00] iulian: Me too, but that's not the 34th line according to http://paste.ubuntu.com/71254/ line numbering... [08:00] iulian: I'm editing t down to try and find exactly what it complains about... [08:00] jmarsden: Awesome, thanks a lot. [08:10] iulian: The problem is the line: option_parse(opt_list, opt_link, help, ARGC, ARGV) [08:10] I think because option_parse has not been defined yet so the shell does not treat it as a function? [08:11] * iulian is looking [08:13] Yes, this line is being treated by sh as a function definition for option_parse but that would have syntax option_parse () stuff [08:13] SO it complains about the missing closing ) [08:17] jmarsden: And how can I do that? My sh coding skills are awful. [08:18] Mine are a bit rusty... I'm not sure what this is really trying to do... are we defining option_parse here, or calling it? [08:22] Hmm, no idea. [08:23] iulian: I think the scrpit may not really be an sh script... should the first line be #!/bin/awk ?? [08:23] There is code here that does not look like sh code to me. [08:24] Let me try that. [08:24] The more I look at it the more I think this is awk code or something very like it. But I've never programmed in awk :-) [08:25] Some parts look like awk, but some parts look like shell, which makes it extra confusing. [08:27] Agreed. === lionel_ is now known as lionel [08:30] jmarsden, persia: It's indeed AWK code. [08:30] Thanks a lot! [08:30] So who or what put !#/bin/sh at the top of it? :-) Anyway, no problem, glad we figured it out. [08:31] I've no idea ;) [08:32] * jmarsden needs to get some sleep... goodnight all [08:32] Sleep well, jmarsden. [08:55] wgrant: axiom is still racy with new gcl, pushing it won't harm too much, but it won't solve problems for every package, but at least it should for maxima. [08:56] DktrKranz: I haven't been able to test maxima too much today, but my first impression is that it's slightly broken in wxmaxima. [08:56] Oh. [08:56] And it doens't event start on the CLI. [08:57] my impression was right, then [08:57] It might well not be due to your gcl change, of course. [08:58] it took too fast to build [08:58] It seems to give the right results. [09:37] now, with a bit of luck, i won't get moderated... [09:38] ooh, i don't :) [09:39] ScottK: added a bit to that u-d-d madness thread. [09:41] Hobbsee: oh dear [09:42] ajmitch: it's not that bad [09:42] yes, yes it is! [09:44] * ajmitch stabs flash, again [09:44] having it crash firefox repeatedly is annoying [09:47] heh [09:47] hey Hobbsee [09:49] hey NCommander [09:49] how goes it? [09:49] going OK [09:55] Hi, I am trying to rebuild openoffice.org3 for hardy [09:55] I believe "debuild -S" overflows /tmp [09:55] http://rafb.net/p/8qQk5i67.html [09:56] Laibsch: yeah, you'd probably need a huge system to do that... [09:56] line 19 [09:56] Hobbsee: I am using the PPA [09:56] Laibsch: not on that pastebin... [09:56] Laibsch: even building the source, i believe you need a pretty huge system. calc would know more. [09:57] But just debuild -S seems to run out of space, I think probably on /tmp, although I can never catch it [09:57] * Hobbsee wonders if your / ran out of space, too [09:57] Hobbsee: I just want to package the unchanged source for uploading to my PPA [09:58] Hobbsee: I have /usr/, /usr/src, /var and a bunch of other things on separate partitions [09:58] * Hobbsee notes that's probably against the TOS? [09:58] Building OOo on the PPA? [09:58] I don't think so [09:58] Hobbsee: Why would uploading an unchanged source be against the TOS? [09:58] We will not accept uploads of packages that are unmodified from their original source in Ubuntu or Debian, only packages that include your own changes. We ask that people include useful changelogs for each package so that users and other developers can understand what new features they are exploring in their work. Read the PPA Terms of Use for more information. [09:58] My quote was specifically enlarged so I can do this [09:58] FAQ on https://help.launchpad.net/Packaging/PPA?action=show&redirect=PPA#Frequently%20asked%20questions [09:59] Aha. [09:59] Hobbsee: Well, I do rebuild debian experimental packages for hardy [09:59] So, at least the changelog changes ;-) [09:59] Laibsch, isn't there already an OOo PPA for Hardy ? [09:59] I haven't heard anybody complain, yet [09:59] Not that I am aware of [09:59] There is one for intrepid [09:59] We are talking about OOo3, not OOo2 [10:00] Laibsch: either way, i'd expect you ran out of space on whatever partition has /tmp, so it died. You'll need a machine with more space, most likely, to even rebuild the source. [10:00] Laibsch, https://launchpad.net/~openoffice-pkgs/+archive [10:00] ops, ignore me, intrepid only :P [10:00] OK [10:01] I was aware of that group PPA [10:01] Last I looked it had only Intrepid [10:01] Seems to be still the case [10:01] Hobbsee: Hmm, I have sometimes thought about using my PPA as a test build device before uploading to "the real thing"... [10:01] talked to the people in the group about it? [10:01] Hobbsee: I was wondering if there is no way to somehow get around that problem [10:01] I have tmpfs and thus RAM/2 [10:01] Usually that is sufficient [10:02] mok0: I think that's reasonable. [10:02] mok0: I do that. Of course, at that point, they're not unmodified from their ubuntu counterparts, because teh new ubuntu counterparts haven't been uploaded yet. [10:02] Laibsch: OOo is not in any way usual. [10:02] ajmitch: Were you talking to me? [10:02] wgrant: ++ [10:02] Laibsch: yes [10:02] Hobbsee: Heh, yeah [10:03] What would that help? I can build the source fine myself (and then possibly share my work with them) [10:03] * Hobbsee thought you couldn't build the source by yourself, and this was the original problem... [10:03] except for space constraints of course ;-) [10:03] right [10:03] I prefer to be independent, here [10:03] Well, I must have been able to pull it off once [10:03] some coordination is useful, especially when you're about to DoS the PPA buildds [10:03] I have rc2 source in my PPA [10:04] ajmitch: That is not the case [10:04] And as I said, the admins are aware of my activities [10:04] * Hobbsee agrees with slangasek. Open Office needs to be downsized to Open Cubicle. [10:04] My quota was enlarged specifically for OOo builds [10:05] Hobbsee: I hope that will eventually happen [10:05] right, but the point still stands about some coordination of work being a Good thing [10:05] Until then, lots of test builds by people like me will be needed [10:05] ajmitch: I never questioned that [10:05] And I am doing that [10:05] Take a look at my profile: r0lf [10:05] I'm not a loner [10:05] But I'm impatient [10:05] right, you had just said you wanted to be independent [10:06] impatient -> wish for independency [10:06] fix things myself, then feed them back [10:06] better? [10:06] coming back to my original question [10:07] Is there no way to divert the tmpdir for a single command? I think, earlier I "mount -o bind" /tmp to someplace else before "debuild -S" [10:07] Works, but not really pretty [10:08] haven't seen anything to do it [10:08] man page doens't show anything of that nature. [10:24] james_w: I presume you're going to deal with rrdtool? [10:24] rrdtool? [10:24] I was just looking at https://bugs.launchpad.net/ubuntu/+source/mailgraph/+bug/221010 [10:24] Launchpad bug 221010 in mailgraph "homepage for mailgraph has moved" [Undecided,New] [10:25] Should to be easy to backport the fixes to releases pre-hardy [10:25] I was just about to try and prepare a debdiff for sponsorship [10:34] When I fix that package, should I also fix small errors along the way, like updating the standards version to 3.8.0? [10:34] Or should I rather prepare a minimally invasive debdiff? [10:36] Minimal, unless it's a package only in Ubuntu. [10:57] anyone from SRU awake? [11:24] dholbach: Finally! [11:24] wgrant: yeah [11:24] Although it would be nice to have component subscriptions directly in LP, this is nice. [11:25] it was partly my fault that this was stalled for so long - I wrestled with mailman a bit, gave up, tried again months later, gave up, then Barry told me that we need a handler installed, then it took him some time to work it out, then I was busy with other stuff, then I prodded the IS team and they were quite quick to sort it out [11:26] * wgrant is a bit confused at 'IS' and 'quick' near each other. [11:26] But anyway, it's sorted out now. Good work. [11:26] that's what I want to avoid, that's why I said it [11:28] but yeah, I'm happy too that it's working now :) === not_rly is now known as orly_owl [12:11] Laibsch: your debdiff says distribution intrepid, shouldn't it read dapper-proposed? Also check version number. [12:11] Laibsch: and you don't want the fix for feisty, it is not supported anymore. [12:13] slytherin: Thanks for taking a look [12:13] The intrepid thing is certainly just a glitch [12:13] !sru | Laibsch [12:13] Laibsch: Stable Release Update information is at http://wiki.ubuntu.com/StableReleaseUpdates [12:13] feisty not supported anyomre? [12:14] Laibsch: no. it had only 18 months of support. [12:14] 7.04 + 18 is 8.10 :-) [12:14] Well, I still see it on ubuntu.com [12:14] Sylphid, 7.04 + 18 is 25.04 [12:14] OK, must be a grace period, then [12:14] er, slytherin [12:15] alright, feisty still supported, then [12:15] Laibsch, it's not [12:15] Laibsch, all SRU bugs for Feisty were declined [12:15] It just hasn't been archived yet [12:15] NCommander: I was talking about Ubuntu math. :-P [12:15] oh [12:15] lol [12:27] hi. How does a revu-day work? [12:27] Do the users have to request a review or will all packages will be reviewed? [12:28] handschuh: Hey. Asking here for a review helps [12:29] RainCT: ok, thanks. I will ask tomorrow then. [12:30] handschuh: (you can also ask when it isn't REVU Day, btw) [12:30] RainCT: so whats different on REVU Day? [12:31] handschuh, On REVU day, more MOTU allocate time to do REVUs. [12:32] persia: ah, thanks [12:33] so as RanCT suggested: I would kindly ask to review two of my small libraries (http://revu.ubuntuwire.com/details.py?package=libauvitoapiaxis-java, http://revu.ubuntuwire.com/details.py?package=libballoontip-java) that are needed for a larger project of mine (http://revu.ubuntuwire.com/details.py?package=jaolt) [12:33] * RainCT notices that it's Friday already [12:34] I wish :) [12:38] It's been Friday for almost 4 hours (at least in select parts of Kiribati) [12:39] 20 minutes [12:39] tick [12:39] tock [12:39] tick [12:39] tock [12:40] persia: I see.. UTC+14, nice [12:40] o.O there's UTC+12:45, UTC-3:30.. XDDD [12:40] RainCT, It mostly exists so that you can't get to tomorrow without leaving the country. [12:42] persia: Uhm.. How long is REVU Day then? 50 (24+12+14)? [12:43] When I was REVU Coordinator, I didn't know about UTC+14, and only ran it for 49 hours. I'd suggest 50. [12:55] * slytherin notices word java in the links pasted by handschuh 8-) [12:56] :-) [13:01] slytherin: What is the problem with the version number? [13:01] Should it have dapper in the version number? [13:01] like 1.12-1~dapper1 [13:02] instead of 1.12-1ubuntu1 ? [13:02] Laibsch: No. I guess the version should be ubuntu0.1. Please confirm from someone in SRU team. [13:03] ubuntu0.1 until it is officially uploaded? [13:03] ping SRU team [13:03] Laibsch: are you preparing a SRU? [13:03] Well, not sure if it actually is a real SRU [13:03] But it is a patch for a package in dapper [13:03] and others [13:04] mailgraph [13:04] The homepage has changed [13:04] so, a rather simply and straight-forward change without regression potential [13:05] geser: are you a member of the SRU team? [13:05] if you plan to get it to dapper-updates: the version should be 1.12-1ubuntu0.1 and the target in the changelog: dapper-proposed [13:05] Laibsch: no [13:05] Alright [13:05] Can you explain the reason for ubuntu0.1? [13:05] Laibsch: SRU is stable release update, no matter how small or bug the change is. Whether it will go in or not will be evaluated by SRU team. And since the package is in universe, it will be motu-sru. [13:06] OK [13:07] Laibsch: the version should be larger than the current one and smaller than the one in $release+1 (which might have an "ubuntu1"), so usually "ubuntu0.1" is added [13:10] hm, that leads to endless recursion, doesn't it? [13:10] Let's say I did an SRU to hardy with ubuntu0.1 [13:10] no, the next one would be ubuntu0.2 (which is still < ubuntu1) [13:11] Then somebody else would do an SRU (unrelated) to gutsy again with ubuntu0.1 [13:11] Problem not solved [13:11] Laibsch: there are rules for this on the wiki [13:11] So, I kind of fail to see the need for introducing 0. [13:11] Laibsch, No, they'd just have to pick a version string between the two. [13:12] Laibsch, It's a convention we follow, rather than a hard rule. It makes the versions predictable, so we can use standard techniques to determine how to handle exceptions. [13:12] persia: OK, so why is that not possible without introducing 0.1? Right now there is no ubuntu1 package [13:12] (and the vast majority of packages won't have the same base version for both gutsy and hardy anyway) [13:13] Laibsch: using Xubuntu0.7.10.1,Xubuntu0.8.04.1, etc. for different releases is an option [13:13] Laibsch, It's not that it's not possible, it's that we have a convention we use. [13:13] The convention is to use .X to indicate SRU uploads. When there isn't a base ubuntu variation, that becomes ubuntu0.X [13:13] (because we need to have the string "ubuntu" for a variety of reasons) [13:14] I understand the reason for 0.1, but while that is mostly for cornercases, I don't think it catches them all, sort of invalidating the whole idea of it. You get my point? [13:14] Laibsch, Yes, but that the system isn't complete doesn't mean it's not useful. [13:14] persia: IOW, all packages ubuntuX where uploaded before the release was made public? [13:14] It's a very rare case that we SRU packages that have the same version in two different releases, especially for different issues. [13:14] Laibsch, huh? [13:15] Laibsch: if you do a SRU for a version 1.0-1 using 1.0-1.1 then this would be confusing as we would think that it's a NMU from Debian. So, naming it 1.0-1ubuntu0.1 makes it clear that it's a SRU or security upload [13:15] No, that indicates it was modified by someone for Ubuntu. [13:15] But once the release is made, the thing becomes an SRU, right [13:15] The version string doesn't change between -proposed and -updates [13:15] And then you are not allowed to use ubuntuX anymore, but use ubuntu0.X instead [13:15] AFter release data [13:16] date [13:16] Yes, after release date we use the .X notation to indicate a version change. [13:16] Oh, wait a minute [13:16] Does this 0.X thing also apply to gutsy? [13:16] Every change should be updated in the development repo first, so the changes in the .X versions don't contribute towards trunk. [13:16] or would that be ubuntu1? [13:17] It applies to all types of SRU. [13:17] On the other hand, in the rare case that the version in gutsy is the same as the version in hardy, you need to work around it by picking different version numbers so gutsy < hardy < intrepid < jaunty continues to apply. [13:18] OK, then in the general case it is $nothing, ubuntu1, ubuntu2, ... before release and ubuntu$i.1, ubuntu$i.2, ubuntu$i.3, ... for SRU uploaded after the release, right? [13:18] public release [13:18] (in which case constructions like 0.1.7.04, 01..7.10, 01..8.04 can be useful. [13:19] Laibsch, Loosely, yes. [13:19] alright [13:19] (although remember to upload to the new development release *before* the SRU) [13:19] Intrepid is already fixed [13:19] That counts :) [13:20] Closes: LP#221010 [13:20] correct format? [13:20] Don't use "closes:", that's for Debian. [13:20] Format is "LP: #nnnnnn" [13:20] (LP:#221010) [13:20] alright [13:20] Many people use parentheses after describing the specific thing changed. [13:21] too complicated ;-) [13:21] so many conventions [13:21] Most of them grew from problems we had in the past. [13:21] understood === azeem_ is now known as azeem [13:37] bug 221010 looks OK now? [13:37] Launchpad bug 221010 in mailgraph "homepage for mailgraph has moved" [Low,In progress] https://launchpad.net/bugs/221010 [13:40] Laibsch, Looks good. I think I need to wait for someone from MOTU SRU to ACK before I can upload though. [13:47] revu day huh? === LucidFox_ is now known as LucidFox [13:51] RainCT: any idea why isn't .diff on revu opened inline in firefox? [13:53] slytherin: how big is it? [13:53] RainCT: 5KB [13:54] handschuh: ping [13:55] slytherin: I think that is a FF "issue" [13:55] slytherin: pong ( did I miss something) [13:56] I have worked around such things by installing an extension [13:56] http://www.spasche.net/mozilla/ [13:56] handschuh: not yet, I was reviewing libballoontip-java. [13:58] slytherin: not sure, perhaps there's something missing in Apache's config [13:58] slytherin: thank you (did you commet it already) [13:58] handschuh: not yet. [13:59] RainCT: may be you could return type as text/plain [14:01] slytherin: if this works, won't it break normal downloads (eg, with dget)? [14:02] RainCT: I am talking about just .diff, not .diff.gz. [14:02] slytherin: ah. what's a .diff? [14:02] :P [14:03] RainCT: I see both .diff and .diff.gz here - http://revu.ubuntuwire.com/details.py?package=libballoontip-java Is that something you haven't done. .diff contains extracted .diff.gz. [14:05]