[00:06] hi, whats the policy for handling "needs-packaging" requests for upstream projects that are basically dead? [00:07] chrisccoulson: That points towards the needs-packaging bug being "Invalid", but it's not absolute. [00:08] It depends a bit about the state of the project; an active upstream matters more for a complex project, or one with bugs. [00:08] If the request is for a package of something simple and mature, it might still be worth packaging. [00:09] yeah, i wasn't sure really. i'm looking at bug 249751. the reporter seems desparate for someone to package it, but there hasn't been any activity upstream since 2005, and their forums are just full of spam [00:09] Launchpad bug 249751 in ubuntu "[needs-packaging] LVE - Linux Video Editor" [Wishlist,Incomplete] https://launchpad.net/bugs/249751 [00:10] That doesn't sound (a) simple or (b) mature :) [00:10] it doesn't seem worth it really does it? [00:13] chrisccoulson: you sort of want an upstream who's alive to fix bugs that come up [00:13] unless you use & love the program enough to become the new defacto upstream [00:14] yeah, i thought that would be the case. is anyone volunteering to maintain it? ;) [00:15] * ajmitch runs away [00:18] what's the programming language? [00:19] hm. qt? nah, not my thing [00:19] qt2, no less! [00:19] whoa! qt2? [00:20] that's a bit of a throwback [00:20] we've got qt3 and qt4. I doubt we want qt2 as wlel! [00:21] you could always update the app to qt4 [00:21] * directhex spams the mailing list [00:21] i didn't even know there was a qt2 until just now [00:21] lol [00:21] i knew there was, as i've seen a book in the library about it [00:21] which looked very old. [00:21] never used glorious kde2? [00:22] are you sure it wasn't in a museum? [00:22] chrisccoulson: well, our library probably is that too [00:22] ;) [00:22] was it written in latin? [00:22] no, english [00:22] * ajmitch used to use kde back in those days [00:23] hm. how old is xfce4? i know i used xfce4 when it was brand new, at the same time kde2 was the default WM on undergrad systems, and someone had compiled kde3 on an nfs share [00:32] hello [00:33] i have a question, on how i need to join MOTU [00:33] what i need to do* [00:33] sorry [00:33] right now i am a ubuntero [00:34] what about the mentoring/sponsoring? [00:34] i need that, for starting, right? [00:34] HoppingWombat, what kind of contributions have you made? [00:35] i have answered questions ... i want to do bugs and package maintenance [00:35] and eventually help develop ubuntu itself -- but i dont expect that for several years [00:36] well, not to sound glib, but do it - pick a package that needs love (e.g. a package you use which needs an update), and give it love [00:36] you don't need to be a MOTU to help in the way you describe - and infact you'll find the experience gained is a necessary entry requirement [00:37] alright [00:37] thanks :-) [00:37] have you looked at https://wiki.ubuntu.com/MOTU/GettingStarted ? [00:37] i am looking at it now :-) [00:38] or i could do with people to work on the mono 2 transition ;) [00:38] directhex - what sort of work is left to do? [00:39] i might be able to volunteer some time ;) [00:39] chrisccoulson, sent an update to the mailing list, but i think it's waiting for moderation [00:39] no problem. i'll have a look at that in the morning, and see if there is anything i can offer:) [00:40] chrisccoulson, basically phase 1 is done - next is phase 2 (applications), where apps need to have their build-deps refreshed, and their build process told nicely to use a different compiler [00:40] that sounds *reasonably* simple [00:41] don't be sucked in! :-) [00:41] but seriously, it's well documented, and most cases will be simple [00:42] i have a nice friendly real-world example on the debian wiki [00:42] because pkg-mono has a fever [00:42] and the only cure is transitioned cowbell [00:42] thanks, i'll have a look at it in the morning. i've got to go now as it's getting quite late here [00:43] indeed. i need to make sammitches === sonicmctails is now known as NCommander [00:54] directhex: your mail doesn't mention 1.0 -> 2.0 Build-Dependencies, but the wiki does, why is that? [00:57] ahm... probably because i'm a pillock [01:25] directhex: how's http://paste.ubuntu.com/77583/ ? [01:28] james_w, looks like i'd expect it to - but it's half 1 in the morning and i'm about to go to bed, so can't do any more in-depth cross-checking right now [01:28] I'll work up the patch and send it to the list as requested [01:28] I just wasn't exactly sure what success looked like [01:29] there are some 1.0 dependencies, but there aren't 2.0 versions of the libraries to Build-Depend on apparently [02:08] How is this thing called, where you don't do a "make install" but another thing, that installs the software in a package format? [02:08] * in a debian package format [02:08] so, that the package manager is aware of the installed software [02:08] (and will remove it automatically if you want) [02:09] I was looking for checkinstall [02:16] Not here you weren't :)( [02:17] * Hobbsee hopes he's not a mobile guy [02:17] As in: Ubuntu mobile? Surely not. [02:18] i thought i recognised the nick [02:18] but not as a packager [02:21] I have an idea, since the package isn't in Ubuntu or Debian, why don't I just waste my time with checkinstall so only I can install it [02:21] must be a shitty app that nobody else wants [02:21] or uses [02:22] * ajmitch detects a subtle hint of sarcasm [02:22] nah, I am getting ready to dput all of my checkinstall builds now [02:22] awesome [02:22] nixternal++ [02:22] I am trying to get stupid pbuilder to build my damn sid setup using experimental in another mirror [02:22] hell, pbuilder won't even setup sid correctly yet [02:23] it won't? [02:23] nope [02:23] * ajmitch didn't have any problems with it recently [02:23] but that was a few weeks ago [02:23] I just went through my .pbuilderrc to find mistakes and didn't find any [02:23] and boom, it bombed out [02:24] your computer exploded? [02:24] * nixternal kicks sid in the pants [02:24] beating up on kids isn't nice [02:24] even if he does break all your toys [02:25] W: http://http.us.debian.org/debian/dists/sid/main/binary-i386/Packages.bz2 was corrupt [02:25] yay \o/ [02:26] Hello. I have this URL: http://revu.ubuntuwire.com/details.py?package=gemrb What files I need from there, in order to build a binary package? [02:28] amikrop: how about you just ask in one channel isntead of hopping aroudn the other dev channels asking the same question [02:28] [02:28] plus, I highly doubt if anyone will answer a checkinstall question due to its unique evilness [02:29] that too [02:29] well, you can't use checkinstall to build a package from a source like that, afaik. [02:30] nixternal: excuse me [02:30] did you burp? fart? [02:30] nixternal: cross-post [02:30] oh :) [02:31] ;) [02:31] nobody has ever said excuse me on irc before...thought there was a textual burp or wind breakage there [02:32] :P [02:33] seems my sid mirror I chose was boogered...we shall see how this goes [02:36] hey nixternal [02:36] wasabi [02:36] DAMNIT!@)!@*)!*@)!* [02:36] o_o; [02:37] W: Failure while configuring base packages. [02:37] WTF are you trying to do nixternal ? [02:37] build my sid pbuildd [02:37] I had no issues doing so [02:37] I can send you my basetgz [02:38] I think my connection might be choking or the mirror is choking....running it again to see where it dies this time [02:38] last time it couldn't download libc I think [02:38] nixternal, try ftp.us.debian.org [02:38] using that one now [02:38] http.us.debian.org was booged [02:39] busted Packages.bz2 [02:57] http://paste.ubuntu.com/77595/ [02:57] tell me, why would .pbuilderrc have references to "unstable" "testing" and "stable" when there aren't any debootstrap scripts for them under /usr/share/debootstrap/scripts/ [02:58] I remove the references to unstable, testing, and stable, and just have sid, lenny, and etch all works well [02:58] kind of...the sid pbuildd will not build [02:59] I comment out the case) and everything debian wise seems to work [02:59] nixternal: The example one at https://wiki.ubuntu.com/PbuilderHowto changes unstable/testing/stable into sid/lenny/etch for you... so that's just a convenience, I think? [03:00] jmarsden: well the one that "was" on the wiki is the same as you see there, or was the same and it is the one that breaks [03:01] OK. I hacked it up so it only knows about Ubuntu for my own purposes, have not yet needed/wanted/tried to set up a Debian pbuilder... I can try and see if it breaks for me too... [03:02] heh, my sid stuff seems to have worked [03:02] it must have been a mirror hiccup [03:03] OK... if you want to see if mine works for you, it's at http://paste.ubuntu.com/77596/ === santiago-pgsql is now known as Guest21988 === Guest21988 is now known as santiago-ve [04:35] superm1: Hello ? [04:35] anyone knows if superm1 is in vacation or so ? [04:38] AnAnt: I'd say he is. [05:55] today is REVU day? [05:57] yay \o/ [05:57] back to uploading packages to Debian...man it is so fun [06:27] When I'm fakesyncing a package from pkg-cli-apps svn in Debian, should I merge in the old Ubuntu changelogs? [06:37] Does anyone know any good bugzilla GUI? [06:51] slytherin: I use kbugbuster in KDE..it isn't to shabby, but it is far from great [06:53] RAOF: iirc in the past, the old Ubuntu changelogs were tossed [06:53] not 100% sure if that is still the case though [06:56] good morning [06:56] mornin' dholbach \o/ [06:56] hi nixternal [07:01] good morning === dholbach_ is now known as dholbach [08:23] slytherin: congratulations! [08:25] Congrats slytherin :-) [08:30] what's slytherin done? [08:32] directhex: become MOTU [08:32] oh. yay! === doko__ is now known as doko [08:55] slytherin: congrats! [09:05] slytherin: congrats [09:18] geser: dholbach: iulian: pochu: Thanks. I came to know from you all before I even read the mail. :-) [09:37] congratulations to slytherin, the Java packaging machine ! [09:37] Koon: Thanks. :-) [09:37] Koon: We have great work ahead. :-) [09:38] slytherin: with great power comes... more work :) [09:38] he he [09:40] slytherin: The project for tools helping in maven packaging is in https://launchpad.net/maven-packaging-support [09:40] slytherin: ludovicc, the author, applied for Java packaging [09:42] he intends to take on the missing library packaging, you might be able to help him on that ;) [09:42] Koon: Sure. Have you already talked to him to add this in team ppa? [09:42] (I mean he applied for the ubuntu-java LP team) [09:43] yes, that's why he applied to the team, not approved yet [09:43] slytherin: are you online around 2200-0000 UTC ? That's apparently when ludovicc works on that. [09:44] Koon: I will be in deep sleep, travelling in a bus towards my home. :-) [09:44] sweet dreams then :) [09:45] Then I'll try to sync with him by phone one of those nights. [09:46] Koon: I will try to put the work he has done in PPA till he gets approved. [09:46] Koon: And I will help him with packaging then. [09:47] slytherin: cool, maybe wait a little before pulling the branch, he is refactoring the scope of the tool to avoid some dependencies [09:47] Koon: sure, I will do this mostly on weekend. [09:47] basically separating what is needed at buid time and what is needed at packaging time [09:49] Koon: I will also go through the spec once more over weekend. [10:02] feel free to celebrate your happy reviewDay by reviewing my package at http://revu.ubuntuwire.com/details.py?package=sqliteman :D [10:15] eMerzh, minor: your description on 02_desktop_file.dpatch is wrong [10:17] directhex: oups....ok :) [10:18] eMerzh, and it's nice (though by no means required) to use the new machine-readable Copyright format. but these are nitpicks. it seems like a straightforward package to me, no glaring issues [10:21] directhex: did you have a link for doc about the new copyright format? [10:21] hang on [10:22] http://wiki.debian.org/Proposals/CopyrightFormat is gthe de-facto format [10:22] directhex: ok thanks [10:51] help review http://revu.ubuntuwire.com/details.py?package=iptux , thanks [10:55] lidaobing: just a quick question, why debhelper 7? [10:56] DktrKranz, no enough reason [10:56] DktrKranz, which version is suggested [10:58] lidaobing: 5 is compatible almost for every supported release [10:58] ok, I will try use debhelper 5 and rebuild [10:58] any other suggestion? [10:59] DktrKranz, any other suggestion? [10:59] lidaobing: I did a quick review, I'll make a more complex in some minutes [10:59] i think DktrKranz has a point - dh7 rules, but you're not obviously using anything not found in 5 (i.e. none of the new easy bits of dh7 are in evidence) [11:00] directhex, I got the idea, the dh_make suggests 7(maybe, I can't remember, :-) ), and I did not change it. [11:01] directhex, DktrKranz , I use dh_auto_configure, maybe this does not exist in 5 [11:05] lidaobing: indee [11:05] d [11:05] just use 'dh' ;) [11:07] directhex, what's the meaning of "just use 'dh' ;)"? [11:08] lidaobing, the big improvement with dh7 is that you don't need to call dh_foo and dh_bar and dh_boz individually. "dh $@" does it all [11:08] directhex, cool, I will try it [11:09] lidaobing, http://svn.debian.org/wsvn/pkg-mono/gluezilla/tags/2.0-1/debian/rules?op=file&rev=0&sc=0 is a DH7 rules file [11:09] lidaobing: if you replace dh_auto_configure with some ./configure magic, you're fine with older debhelper's [11:10] or you can move to dh7 for everything [11:10] DktrKranz, I will try to use debhelper 5, so I can backport this package. [11:22] congratulations slytherin [11:23] DktrKranz, I have upload a new version of iptux: http://revu.ubuntuwire.com/details.py?upid=4127, please help check [11:26] james_w: Thanks. I read your post about changelog and that is something even I was thinking for long time. :-) [11:26] I think a lot of people do. [11:26] lidaobing: checking [11:27] we work on other peoples stuff a lot in Ubuntu, so it's extra important [11:27] DktrKranz, thanks [11:29] james_w: also it is important when you can not figure out what changes in Debian version of a package while trying to do a merge. :-) [11:30] looks like tuxcrafter disagreed! [11:40] lidaobing: why did you include LDFLAGS="-Wl,-z,defs" ? [11:40] I copy it from dh_make [11:40] DktrKranz, I copy it from dh_make === ma101 is now known as ma10 [11:54] lidaobing: commented === asac_ is now known as asac [13:30] anyone familiar with sysprof and how to install whatever is needed to see function names? [13:41] any sysprof users? === LucidFox_ is now known as LucidFox === bddebian2 is now known as bddebian [15:04] blorp. i need to add a get-orig-source to a cdbs package [15:43] james_w: regarding bug 298273, the answer is no, it seems that superm1 is in vacation or so (note that his last couple of emails are sent from a mobile device) [15:43] Launchpad bug 298273 in sl-modem "Add DKMS support to sl-modem" [Undecided,New] https://launchpad.net/bugs/298273 [15:44] AnAnt: click on the overview tab at the top of the page [15:45] oh [15:45] even rmadison says that it's released [15:46] who did that ? [15:46] james_w: so the answer is yes then ! [15:47] why is the bug status NEW then ? [15:47] because you didn't reference the bug number in the changelog [15:47] silly me ! [15:47] ;) [15:47] I saw that go past on -changes, and was then surprised when the bug was still open [15:48] AnAnt: did you not get an "Accepted" mail? [15:48] that would have a Signed-By line that would tell you [15:48] james_w: nope, didn't get such thing [15:48] What does this error mean: dpkg-source: unrepresentable changes to source [15:48] dpkg-buildpackage: failure: dpkg-source -b pbxbuntu-asterisk-1.4.22 gave error exit status 1 [15:48] I'm trying to build a source package. [15:49] james_w: ok, I set the status to fix released [15:50] AnAnt: if you look on the jaunty-changes mailing list you will be able to see it [15:50] james_w: I see [15:51] ping dholbach - i just had a look at your comments on bug 302672. i can't seem to recreate the build failure that you're seeing [15:51] Launchpad bug 302672 in transmission "new transmission upstream version 1.40" [Wishlist,Triaged] https://launchpad.net/bugs/302672 [15:51] any idead how to debug why db_set is failing in postinst script? [15:52] chrisccoulson: hm, I had it in a jaunty amd64 pbuilder [15:52] i've just tried it in jaunty amd64 and i386, and i can't get it to fail in either [15:52] and i just tried uploading it my PPA, and it built there too :/ [15:53] strange! [15:53] http://launchpadlibrarian.net/20030188/buildlog_ubuntu-jaunty-i386.transmission_1.40-0ubuntu1~ppa1_FULLYBUILT.txt.gz [15:55] the most epic piece of anti-mono-in-ubuntu-context hate i've ever seen, taken from the #boycottnovell irc channel logs: "[01:31] schestowitz: lol, ya know what? Even Nelson Mandela himself should protest of Ubuntu coming with Mono pre-installed and well-incorporated." [15:56] chrisccoulson: libcurl-dev seems to be a virtual package, it shouldn't just Build-Depend on that. [15:56] Any advice on this error: dpkg-source: unrepresentable changes to source ???? [15:56] james_w - i did wonder whether that might be an issue [15:56] directhex: yes, clearly, they have their perspectives and priorities correct [15:57] chrisccoulson: if you want to build on a virtual package you should Build-Depend on "real-package-that-provides-virtual | virtual" [15:57] mgdm, they wonder why their cause is not treated with respect [15:57] chrisccoulson: I don't know why that would fail for one pbuilder and not another though [15:57] i can do that. in fact, both of the packages that provide the virtual package come from the same source package anyway [16:00] dholbach - i wasn't aware of the "uscan --download" trick for getting the new upstream source. thats a bit easier. thanks! [16:00] chrisccoulson, works great until you need to +dfsg a package [16:01] i haven't had to come across that yet though:) [16:04] I'm online for any comments on http://revu.ubuntuwire.com/details.py?package=metalink , this contains a new version with better licensing and I've moved to CDBS. [16:06] Does anyone know how to tell debuild that I'm building the orig file? [16:06] ls [16:07] have a native package version number? [16:07] ? [16:07] do you not just miss the bit after the "-" in the version number? [16:08] pbxbuntu-asterisk_1.4.22.orig.tar.gz [16:08] that's the orig file.. [16:08] pbxbuntu-asterisk-1.4.22 that's the directory I'm building it from... [16:08] pbxbuntu-asterisk_1.4.22-0ubuntu1.diff.gz [16:08] did I get something wrong? [16:09] dpkg-source: error: cannot represent change to pbxbuntu-asterisk-1.4.22/contrib/firmware/iax/iaxy.bin: binary file contents changed [16:09] dpkg-source: unrepresentable changes to source [16:09] dpkg-buildpackage: failure: dpkg-source -b pbxbuntu-asterisk-1.4.22 gave error exit status 1 [16:09] if you want to make a native package, your version number must be free from "-" [16:09] That's the error it's failing at.... [16:09] so what do I need to change? [16:10] pbxbuntu_asterisk_1.4.22? [16:10] that's not the version number. the version number is set in the changelog [16:11] pbxbuntu-asterisk (1.4.22-0ubuntu1) hardy; urgency=low [16:11] changed to:pbxbuntu-asterisk (1.4.22-0ubuntu1) hardy; urgency=low [16:11] oops. [16:11] pbxbuntu-asterisk (1.4.22_0ubuntu1) hardy; urgency=low ??? [16:11] i don't think you quite understand the original problem, which is why the solution isn't helping you [16:12] directhex: I think you're right. [16:12] if you want to rebuild orig, then that means you will no longer have a diff.gz file - only orig and dsc [16:12] I'm not sure if I need that... I'm trying to build the original file. It seems I have a .orig file. [16:13] the usual option is removing all "non-native" markers from the version number, i.e. just "1.4.22". alternatively, erase your orig, and it'll be forced to regenerate it assuming it's a native package [16:13] but making a new orig is the wrong thing to do in 99% of cases [16:13] i.e. unless you need to +dfsg a package, don't do it [16:13] I'm not sure what +dfsg a package means. [16:14] I'm trying to build a new package from source. I'm not trying to 'patch' any existing package. [16:14] And I think that's where I am confused. [16:14] help review http://revu.ubuntuwire.com/details.py?package=iptux, thanks, I upload a new version just now. [16:15] quentusrex - that's good, but if you're adding a debian/ folder in order to package it, then that is a diff from the original source [16:16] chrisccoulson: ok. Then it sounds like I don't need to change anything with the orig file. [16:16] if you don't want to maintain a diff, and you just want to package everything in to the orig.tar.gz, then the version number in your debian/changelog needs to be the same as the version of the upstream source (ie, no "-0ubuntu1" bit) [16:16] but that's a bad idea [16:17] But the problem I have is that when I try to build the source with 'debuild -S' it errors out with: dpkg-source: warning: executable mode 0755 of 'contrib/scripts/get_ilbc_source.sh' will not be represented in diff [16:17] dpkg-source: error: cannot represent change to pbxbuntu-asterisk-1.4.22/contrib/firmware/iax/iaxy.bin: binary file contents changed [16:18] the warning is nothing to worry about i don't think. the error is because you changed a binary file i assume (but i'm really not all that sure) [16:18] but that's what the: dh_clean [16:18] dpkg-source -b pbxbuntu-asterisk-1.4.22 [16:18] dpkg-source: warning: Version number suggests Ubuntu changes, but Maintainer: does not have Ubuntu address [16:18] That's what changes the binary file. [16:18] the dpkg-source -b changes it... [16:19] i'm not sure really :/ [16:19] And I think the source for the software gives a default file, then when built the software overwrites with a custom binary file. [16:19] please help review http://revu.ubuntuwire.com/details.py?package=iptux, thanks [16:21] lidaobing: I'll have another look when I come back home (in a couple of hours) [16:23] DktrKranz, OK, thanks in advance. but I have to go to sleep in 1 hour(here is UTC+8). so please paste your comment, thanks again. [16:35] chrisccoulson, directhex I found the problem. It seems I accidentally build the orig with no files in it. [16:38] good stuff;) [16:42] my fingers are crossed... This might just work... [16:43] My development machine is ubuntu 8.10, and I'm building this for 8.04... === thekorn_ is now known as thekorn [16:54] if someone want to review my package...i've just correct a tiny tiny error... http://revu.ubuntuwire.com/details.py?package=sqliteman [17:04] RainCT: mind if I merge serpentine? [17:05] ryanakca: it's all yours [17:08] RainCT: thanks [17:09] ryanakca: thank _you_ :) [17:19] Should I keep the translation from rosetta in a merge? It's the same upstream version, so I'm guessing that since they're still valid, I can leave them? [17:19] If I am building a package for ubuntu hardy, do I have to be running hardy on my system? or is there a way to build it? [17:20] quentusrex: you build in a chroot, look for pbuilder on the wiki... [17:20] I've got pbuilder... [17:21] just don't know how to use it to build outside of my system. [17:21] https://wiki.ubuntu.com/PbuilderHowto ... so, if you're building it for hardy, you need to create a hardy pbuilder. If you're building for jaunty, create a jaunty one, etc. [17:25] quentusrex: What do you have in your pbuilder chroot? If you're interested in having more than one, see https://wiki.ubuntu.com/PbuilderHowto#Multiple%20pbuilders [17:25] ryanakca: dh_clean: Sorry, but 6 is the highest compatibility level supported by this debhelper. [17:25] make: *** [clean] Error 1 [17:25] dpkg-buildpackage: failure: fakeroot debian/rules clean gave error exit status 2 [17:25] just one pbuilder: hardy. [17:26] but I did the debuild -S on a Ibex system. [17:28] ryanakca: you'll need intrepid for debian/compat level 7 [17:28] both pbuilder and debuild -S [17:28] hyperair: for keeping translations from rosetta? Or was that for quentusrex ? [17:28] then how do I debuild -S on my intrepid system in such a way that a hardy system can install it? [17:29] I created the source package with debuild -S on my intrepid system. But when I tried to install the package on my hardy system it gave me the debhelper error... [17:29] How do I run debuild -S on my intrepid system so that it uses a debhelper 6 compatible build? [17:30] ryanakca: what? [17:30] ryanakca: and whoops, i meant to ping quentusrex [17:30] :) [17:30] quentusrex: echo 6 > debian/compat [17:31] and drop the debhelper build requirement to >= 6 [17:32] ok [17:32] I was born in Petersburg, VA. [17:32] lol' [17:32] wrong window [17:33] since I changed the subject. where are you all from? [17:33] ...that's one hell of a change [17:33] i'm malaysian [17:33] New Brunswick, Canada [17:34] is New Brunswick east or west Canada? [17:36] quentusrex: eastern [17:36] I'm trying to get to know some of the other developers for Asterisk and telephony. [17:36] cool. [17:36] I moved from East Coast, USA to West. I'm in Seattle, WA now. [17:37] i'm uh.. still sitting around in malaysia [17:38] hyperair: I'm ready the wikipedia article about malaysia... I've never been there... [17:38] reading you mean? [17:38] yeah... [17:38] heheh [17:38] Today isn't my best day for irc... [17:39] yes, that's usually the response i get. "malaysia? where's that?" [17:39] The only thing I know about malaysia is where it is on a map, and that it got hit hard by that tsunami. [17:39] hmm [17:39] hard by the tsunami? [17:39] i'd say not [17:40] no? [17:40] we got shielded from it mostly [17:40] sumatra got it worst [17:40] and that's part of indonesia [17:40] the huge island that's parallel to peninsular malaysia [17:40] west of it [17:40] the tsunami came from west of sumatra [17:40] whacked out the northern regions [17:40] lucky for malaysia... [17:41] and some smaller waves came to northern malaysia [17:41] i hear penang got hit [17:41] but it was mild compared to acheh, sumatra [17:41] that one got whacked out completely i think ._. [17:41] Living here in Seattle we're worried about a tsunami [17:42] you near to a beach or somethign? [17:42] * ryanakca mumbles something about !ot [17:42] lol [17:42] ryanakca: how is this not related to MOTU? :P [17:42] RainCT: lol [17:43] hyperair: check out the wikipedia article about the Puget Sound and then Seattle. we're right on the water... [17:43] alright, back to MOTU. [17:43] RainCT: Maybe you could answer my question then (since you added them), Should I keep the translation from rosetta in a merge? It's the same upstream version, so I'm guessing that since they're still valid, I can leave them? [17:43] ryanakca: Yes. And please forward them to Debian if I didn't do that (although I think I did :)). [17:44] uhm.. or better directly to upstream [17:44] RainCT: *nod* [17:50] Alright, if my package requires another of my packages. [17:50] How do I do this? [17:51] So, I'm building the packages with debuild -S [17:51]