[12:11] thank you so much LaserJock and sistpoty [12:11] cbx33: thank's for your contribution ;) [12:12] np === nictuku [n=yves@ubuntu/member/nictuku] has joined #ubuntu-motu === mukund [n=mukund@62.3.217.116] has joined #ubuntu-motu === Gazer [n=gazer@mail.aktiv-assekuranz.com] has joined #ubuntu-motu === Fujitsu [n=fujitsu@203.23.49.35] has joined #ubuntu-motu [12:49] Toadstool: did you really mean to send that to all those lists? [12:50] LaserJock: yep [12:51] k :-) [12:51] I've just followed what dholbach wrote in https://wiki.ubuntu.com/UbuntuBugDay/Draft [12:51] LaserJock: you pimp the school but you don't hang out there ;) [12:51] mass bug day annoucement spam :p [12:51] +n [12:51] Toadstool: but the subject sounds more like a discussion topic than an announcment :-) [12:52] sweet Toadstool, i can't wait!!! [12:52] back to dinner ;) [12:52] nixternal: yeah yeah, I get to many channels open [12:52] LaserJock: well, I'm not good at choosing mail subjects :) [12:53] so are we going to have a Hug Day every Wednesday? [12:53] hmm I need to find a way to perform "apt-get -s upgrade" as an unprivileged user. [12:54] avoiding the lock would be great [12:54] hmm [12:54] interesting thought [12:54] LaserJock: hmm... that's what was planned at the end of Dapper's development, every Wednesday -> hug day IIRC [12:54] aptitude :-) [12:54] Toadstool: k [12:55] We need them :) [12:55] indeed :) [12:55] well, we need Hug Days, REVU Days, Merge Days, School Days, Meeting Days [12:55] that's 5 [12:55] looks like our week is packed ;-) [12:55] heh [12:56] Heheheh === Fujitsu merges. [12:56] Fujitsu: I'm not sure you are allowed to on non-Merge Days ;-) [12:57] Or not. [12:57] hehe [12:57] I think all my syncs/merges worked properly... === Fujitsu checks Launchpad. [12:57] that's cool [12:58] make sure to document those on your wiki page [12:58] btw.: does UVF apply for universe as well? [12:58] there is one Universe Freeze [12:58] not until feature freeze [12:58] in September some time [12:58] at the same time as Beta Freeze I believe [12:59] it is UVF and FF combined for Universe [12:59] LaserJock, I did :) [12:59] great :) [01:00] yeah, cause I was freaking out at the thought of how many merges needed to be done by July 13th :-) [01:00] sistpoty: UniverseFreeze -> September 28th according to the wiki [01:00] hmm, that sounds like a factoid [01:01] Toadstool: ah, thx... wasn't there when I last looked at it [01:01] :) [01:01] LaserJock, I was about to die when I checked a week ago... I thought you were going to be stuffed. [01:02] hmm? [01:02] !freeze [01:02] September 28th is the Universe Freeze. No new packages or upstream versions after this point without an exception. See http://wiki.ubuntu.com/EdgyReleaseSchedule [01:02] Haha. Very good. [01:02] oops, 1am and I'm supposed to wake up at 6am... time to go to bed [01:02] I think it might be advisable to rename UVF. [01:02] g'night everybody [01:03] Bye, Toadstool! [01:03] cya ToadZzZztool [01:03] gn8 ToadZzZztool === zul [n=chuck@ubuntu/member/zul] has joined #ubuntu-motu [01:10] hey [01:10] hi [01:10] how is it going tseng? [01:11] Hi zul. [01:11] hey [01:11] fine thanks [01:13] LaserJock: Micah Cowan raises a good point RE: MOTU Mentors [01:13] crimsun: yeah, I'm replying [01:13] well, the spec should have defined that, shouldnt it ? [01:13] Mentors, or lack thereof? [01:14] LaserJock: and I'm not really sure how approximating a number of mentored people each of us would "accept" really changes things === Tachikoma [n=nexu@a80-126-56-145.adsl.xs4all.nl] has joined #ubuntu-motu [01:14] crimsun: well, the problem was that everybody said "busy" [01:14] which is a real turnoff [01:14] Yeah, I noticed that when I looked at the page. It was quite a turn off. [01:14] LaserJock: I think it might be easier for us to go the "office hours" route [01:14] so I put "generally available" and I got 2 right off the bat [01:15] well, for those of us who are "very busy", it really means "very busy". [01:15] crimsun: perhaps, although dholbach didn't liek the idea === nexu [n=nexu@a80-126-56-145.adsl.xs4all.nl] has joined #ubuntu-motu [01:15] crimsun: right, but it still mean all the people are going to go for the least busy person [01:15] then why don't we get rid of availability altogether? [01:15] yeah, perhaps that's the best solution [01:16] although I do like the idea of giving some indication of availability [01:16] Probably. [01:16] there's really no point in having it at all since we know there's going to be a strong tendency toward those who have a higher threshold or increased hours [01:16] how bout the mentor is in...ie something in the topic [01:16] Because I thought you were the only really available one, LaserJock. It's not a good idea having that field. [01:17] the problem is, in general, the people who are very active in MOTU are usually the least likely to have time for MOTU Hopeful development [01:18] Yeah, that's unfortunate. === micahcowan [n=micah@69.36.252.2] has joined #ubuntu-motu [01:18] and yet those are specifically the people who would benefit most from having people to mentor. [01:18] hi micahcowan, we were just talking about you :-) [01:18] Oh? :-) [01:19] Sorry I missed a good chunk of the conversation... [01:19] the further one progresses from being an initial "mentored" person, the more easily one loses sight of what areas to emphasise. [01:20] how about instead of using "availability" we have extend the IDs to Name, e-mail, irc nick, and preferred method of communication? [01:20] s/have// [01:21] hmm, what would the preferred method of communication be? [01:21] I think the idea is to use email [01:21] either irc or e-mail for starters [01:21] that way those of us who can't access either readily can choose what's most appropriate [01:22] I was thinking Name, email, irc nick, and area of intrest would maybe be good [01:22] Yeah, that sounds good. [01:22] "active MOTU areas" is probably a more delicate way of phrasing that [01:22] yeah [01:23] ok, so let's go with that idea then [01:23] drop availability and add active areas [01:23] micahcowan: so was the Mentors wiki page any better than my email? [01:23] or did both suck? [01:24] "original Make have been modified: you should use a patch instead" http://revu.tauware.de/details.py?upid=2439 I still have the original make, what do I do... if you feel so inclined, you can refer me to a webpage explaining how to patch for packaging :) [01:24] I think it said more or less the same thing as the email. [01:24] hmmm [01:25] micahcowan: so it was mostly just that you didn't really see what the point of it? === Fujitsu wonders if he can fill somebody's mentoring slot. [01:26] LaserJock: or that the point of it wasn't altogether clear to me, yeah... [01:26] I think it's also important to consider having multiple mentors [01:26] ryanakca: you could use s.th. like dpatch or cdbs' simple-patch-sys... [01:26] crimsun: well the point was to turn them over to MOTU as a whole once they could stand on 2 legs, so to speak [01:27] ryanakca: but imo directly patching the sources is ok as well, though raphink doesn't like it :P [01:27] Unless the point of it was just to get familiar with the mailing list, IRC, etc., get your feet damp... [01:27] lol... he's the one who said to patch it... so :) [01:27] micahcowan: more or less yeah [01:27] during my tenure at big blue, we had peer mentors and external mentors, the difference being that the external ones had been there for decades while our peers perhaps a few years more then us [01:27] than us ^ [01:27] ryanakca: but there is a different problem with typespeed: it's already in universe (but a different version)... [01:28] ... [01:28] ryanakca: so maybe it would be a good idea to reuse debian's packaging as far as possible (to keep the diversion small) [01:28] crimsun: we could have something like a MOTU Hopeful buddy system :-) [01:28] LaserJock: well, in that case, I think it was clear enough. I just wasn't sure if there was more to it than that. [01:28] LaserJock: yeah, we should encourage that [01:28] micahcowan: it could be, we don't have a lot of experience [01:29] crimsun: well, I proposed something like that back in probably Oct. or Nov. of last year ;-) [01:29] ryanakca: otherwise you might end up having it to maintain for ubuntu w.o. the possibility to go in sync ever again [01:29] LaserJack: basically, what I wanted to know is, given that I'm already on email, launchpad, etc, is there much value to my being Mentored? [01:29] ryanakca: which would be some kind of waste of resources imo [01:29] sistpoty: lost me :) [01:29] sistpoty: go in sync? [01:30] ryanakca: if the debian maintainer brings in 5.1, we can just sync that... [01:30] micahcowan: perhaps [01:30] ryanakca: or you could file a wishlist bug into debian bts with your updates to typespeed [01:31] ryanakca: which means less work for you and the debian maintainer [01:31] micahcowan: I think the initial idea was to just get people to the point where they could start asking good questions [01:31] ah [01:31] micahcowan: ok. What's a good question? :) [01:31] Did I just address myself? [01:31] heh [01:32] micahcowan: when will MOTU School sessions be offered and what is the next topic? [01:32] sistpoty: hmmm... "good idea to reuse debian's packaging"... does that mean copying the old control/changelog/copyright/rules? [01:32] micahcowan: I'm having problems understanding debhelper [01:32] ryanakca: basically yes... it means to change only things that absolutely need to be changed ;) [01:33] LaserJock: (doesn't that fall under packaging basics?) [01:33] micahcowan: who do I talk to about getting a sync done [01:33] micahcowan: that might be after they have had an initial read over of the Packaging Guide, for intsance [01:33] ok, here's my use case and plan for mentoring: [01:34] A forums person who has a decent knowledge of Linux and Ubuntu wants to contribute back to the distro [01:34] but they've never used IRC or mailing lists === mukund [n=mukund@62.3.217.116] has joined #ubuntu-motu [01:34] and they've only vaguely heard of MOTU [01:34] perhaps on a forum thread [01:34] that's the use case [01:35] now what I'd do is" [01:35] : [01:35] get them on the mailing lists [01:35] get them IRC if at all possible [01:35] sistpoty: kk [01:35] have them read over the Ubuntu Packaging Guide [01:35] (better yet, have them discuss the UPG with you) [01:36] ask them about their interests to see what areas to plug into (bug fixing, one of the MOTU teams, etc.) [01:36] talk about the general release process and what MOTUs do and how a package goes from a source tarball to a .deb on somebody's box (in generall terms) [01:37] I'd try to introduce them to people in the channel with like interests, etc. [01:37] and once I feel like they aren't floundering about trying to figure out what to do and can ask good questsions, they're off [01:38] LaserJock: sounds useful. It sounds like much of that won't apply to me at this point, but it sounds like a great idea. [01:38] I expect I'll always be in contact with them, but I'm *not* going to teach them everything about packaging (because we already have a mechanism for that) and I'm *not* going to turn them into my personal cronie/workhorse [01:39] we should have a clear subject line for e-mails, please [01:39] except for making them do all the MOTU Science merges/syncs, of course ;-) [01:39] I get upwards of a thousand daily, and even with filtering it's a chore [01:39] crimsun: which email? [01:40] LaserJock: I think you might add the bit about trying to plug them into specific teams (when applicable); introducing them to the group to the page. [01:40] -motu? [01:40] whenever that initial contact with prospective mentor is [01:40] oh, for Mentors? [01:40] that's why I can see multiple intro vectors [01:41] some people may feel more efficient hopping on irc and pinging you [01:41] some might send you an e-mail [01:42] micahcowan: something that is a bit tough with that page is that I'm guessing a potential mentee won't really know a lot of what they need, the just want to help out [01:43] whats the point of /debian/install? [01:43] but don't know where to start [01:43] ryanakca: installing files, man dh_install [01:43] LaserJock: /debian/rules? Makefile? it runs fine without it... hmmm... [01:44] debian/rules === ryanakca debates with himself wether or not to include it [01:44] :) debian/rules === Fujitsu_ [n=Fujitsu@203.23.49.35] has joined #ubuntu-motu [01:47] LaserJock et al.: ok, I've made the adjustment to Mentors, so you'll probably want to add your active areas [01:47] k, I'm on it === yves [n=yves@ubuntu/member/nictuku] has joined #ubuntu-motu [01:48] crimsun: how would "MOTU Mentor:" be for a subject line tag? [01:48] that would be great as a suggestion [01:48] I'm probably a corner case, but it would really help [01:48] well, I doubt it hurts [01:53] Are you going to add waking hours there? [01:53] I doubt it, I think for most people they fluctuate too much to be useful [01:53] maybe not though [01:53] we could just put 24x7 for crimsun and be done with it ;-) [01:54] I've worked on a project where I had to work with somebody who was in France. His waking hours were the opposite of mine, and it was incredibly difficult to collaborate. [01:54] sistpoty: ok, fixed it so that I recycle debian's packaging, and I still don't get the patching part :( [01:54] ryanakca: give me a sec... [01:55] sistpoty: kk, ty [01:55] Fujitsu_: most of my collaborators are, like Ubuntu devs, scattered across the globe. It makes for interesting sanity-scheduling. === FunnyLookinHat [n=funnyloo@71.57.11.218] has joined #ubuntu-motu [01:56] True, crimsun. === pschulz01 [n=paul@eth6067.sa.adsl.internode.on.net] has joined #ubuntu-motu [01:56] yeah, that is something you have to get used to [01:56] I guess, I guess. [01:56] ryanakca: it's simple for typespeed: don't use a patch system, just modify the files directly in the sourcepackage, since the debian maintainer does that as well. [01:57] ah, so I can ignore raphink's comment on patching :) [01:57] Urgh. That's not a good idea... Doesn't that break packaging guidelines? [01:57] ryanakca: yes [01:57] Fujitsu_: its a legitimate thing though [01:57] to both your comments ;-) [01:57] it's actually aligned with our packaging guidelines. [01:57] Heheh. I was wondering that... [01:57] Is it? [01:57] yes [01:57] if Debian doesn't use a patch system then you don't add one [01:58] precisely. [01:58] Yeah, but Debian should really use a patch system... [01:58] and if upstream (Debian) doesn't use that patch system, then debdiff is mighty straight-forward for us. [01:59] Fujitsu_: there isn't any Policy that I'm aware of that says you *have* to use a patch system [01:59] ryanakca: however it's a good idea to also make patches from what you changed and store them in debian/ubuntu-patches, since that's quite convenient... but that's up to you [01:59] LaserJock: I thought it was nearly absolute in the packaging-from-scratch guidelines I read... [01:59] Though I have noticed a couple exceptions "in the wild", I think. [01:59] sistpoty: hmmm... dunno how... sounds complicated... I messed around with some things a lot... I'll pass :) [02:00] sistpoty: probably cause me trouble down the road though :(... [02:00] hmmm... do I run sudo pbuilder update --distribution edgy --override-config now? [02:00] micahcowan: I would consider it "best practices" to make modifications as a patch that is stored in debian [02:01] micahcowan: if you're packaging from scratch, yes, it's highly recommended you use a patch system [02:01] ryanakca: do you have an edgy pbuilder? [02:01] but you could just apply the patch in debian/rules if you wanted to === nixternal_ [n=nixterna@unaffiliated/nixternal] has joined #ubuntu-motu [02:01] sistpoty: no... I'm running dapper... and dapper on pbuilder [02:02] ryanakca: then you'll also need to modify cat /etc/pbuilder/apt.config/sources.list iirc (and then run update --distribution edgy --override-config) [02:02] s/cat// [02:03] LaserJock: but not a requirement (for new packages)? [02:03] kk... so no more packaging for dapper or ??? (I'm getting really confused :) ) [02:03] micahcowan: I'm gonna say no, but highly recommended [02:03] ryanakca: no, dapper is closed, all new stuff goes to edgy [02:03] kk [02:04] hm... I personally dislike any patch systems, since a VCS can do much better... [02:04] ...so, in this context, it's not a new package, and already not based on patch system? [02:04] Just modify the source. [02:04] sistpoty: bash: cd: /etc/pbuilder/apt.config/: No such file or directory [02:05] right, we follow Debian's practice. [02:05] the changes will end up in diff.gz anyhow. [02:05] however the problem is that usually only a small group of people has access to that VCS, and a sourcepackage doesn't contain the info from the VCS [02:05] micahcowan: the Golden Rule of Ubuntu Packaging is : Minimize the delta between Debian and Ubuntu, you will appreciate it later :-) [02:05] ryanakca: hm..., then just try the pbuilder update --distribution edgy (...) === DarkMageZ [n=DarkMage@59.167.27.251] has joined #ubuntu-motu [02:06] I will complain bitterly that I hate that window between which dinstall runs and the mirrors haven't yet published the new source packages. [02:06] Maybe I've been misunderstanding. I was thinking "patch system" referred to diff.gz... and that the discussion was that versus a single tarball with changes included... [02:06] (for Debian, that is) [02:06] micahcowan, no. [02:07] Is it a reference to several, separate patches, one for each new set of changes? [02:07] micahcowan: no, patch system refers to patch helpers like dpatch, quilt, CDBS [02:07] oh... okay. [02:07] micahcowan: diff.gz is always present for such practices. The issue is whether one uses a system to manage patches that you'd place in debian/patches/ or whether you'd apply them directly without keeping them in that directory. [02:08] keeping things in debian/ is nice [02:09] LaserJock, it makes things neat not having a delta outside debian/... So yes. [02:09] what's the reasoning behind that: the security of knowing that if you're not looking in debian/ it's highly probably that the code you're looking at is original from upstream? [02:10] not so much debian/ but inside the diff.gz. [02:10] no... the reason is that you can annotate patches and differentiate on what change does what if you have a patch system [02:10] also it makes it easier to version control the packaging [02:10] crimsun: but you'll have a diff.gz, regardless of whether you use patching system or not (hopefully), yes? [02:10] you can just make a bzr branch out of the debian/ [02:11] micahcowan: yes. It's for maintenance. [02:11] Ah! Instead of branching the whole damn thing. Gotcha. [02:11] It makes it a lot lot easier to do merges if the patches are logically seperated. [02:11] Like I discovered yesterday with a couple of packages. [02:12] sistpoty: do I need to create a Desktop file for typespeed? my guess is no... but I'm not very good at guessing :) [02:12] bzr is darned nice, too. [02:13] ryanakca: it's nice to have one, but not essential [02:13] It's good to have one, ryanakca. A lot of Ubuntu deltas are exclusively .desktops. [02:13] yeah, but that's not good either :( [02:13] Does bzr have a relation to ubuntu? [02:13] (above CVS/SVN/etc?) [02:13] kk [02:14] micahcowan, uh, yeah. Both sponsored/developed by sabdfl. [02:14] many Ubuntu devs favore bzr as well [02:14] And rightly so. [02:14] It's great :D [02:15] and Launchpad has some support for bzr [02:15] Some? I'd say a lot. [02:15] maybe I'M still thinking to erm centralized for bzr *g* [02:15] Hehehe. [02:15] well, it's not for everything, IMO [02:16] It's for a lot of things. [02:16] I prefer SVN for my own stuff in most cases. [02:16] grr.. [02:16] I prefer bzr for local stuff and svn for remote [02:16] Is there much reason for me to /not/ continue to use SVN for my own packaging, assuming I get to that point at some time? [02:16] I prefer the other way. [02:17] I take it a desktop file is debian/Desktop ? [02:17] bzr is just waaay to slow for me remotely, plus it's got some nastiness with DNS lookups [02:17] No. [02:17] micahcowan: my mantra is use whatever fits. [02:17] debian/whatever.desktop [02:17] crimsun: sounds reasonable. :) [02:17] that means I have cvs, svn, hg, git, and bzr installed [02:18] I just installed cvs today :-) [02:18] what a PITA when the syntax starts contorting [02:18] Urgh. CVS. [02:18] crimsun: hm. I hope I never find myself in that situation... [02:18] gnome is converting to SVN but they had a problem so they went back to CVS until the get the bugs worked out [02:19] but launchpad converts everythin to bzr anyway ;-) [02:19] but it takes forever to branch so I just use CVS [02:19] l [02:19] err [02:23] git is interesting [02:24] hmm, this can't be good. "Permission denied (publickey)" when using bzr checkout [02:24] Hmm. From where? [02:25] whoa, this is all krunk. [02:25] well, that was from: bzr checkout sftp://~crimsun@bazaar.launchpad.net/~ubuntu-core-dev/alsa-utils/debian/ [02:26] lol can't even get from your own branch huh [02:26] what's "Name[xx] =Kfoo" in *.desktop... theres allready "Name=Kfoo"... [02:26] but ``bzr checkout http://bazaar.launchpad.net/~ubuntu-core-dev/alsa-utils/debian/'' fails, too, with "bzr: ERROR: Cannot lock: transport is read only" [02:26] also... "GenericName"... [02:27] try bzr get [02:27] ryanakca: see http://standards.freedesktop.org/desktop-entry-spec/latest/ for details [02:28] ryanakca: it really has xx? [02:29] http://doc.ubuntu.com/ubuntu/packagingguide/C/ubuntu-kubuntu.html yep [02:29] hmm, maybe I should have read that ;-) [02:29] lol [02:29] ryanakca: xx is a language identifier like de for germany and so on [02:30] ah, ty === ryanakca deletes that line [02:33] micahcowan: can you read over https://wiki.ubuntu.com/MOTU/Mentors real quick and see if it's better? === _jaldhar [n=jaldhar@c-68-38-202-139.hsd1.nj.comcast.net] has joined #ubuntu-motu [02:36] LaserJock: will do. [02:39] LaserJock: this seems significantly more informative. [02:39] yay for PEBKAC [02:40] LaserJock: But the "slots" system went away? [02:40] (for note, don't use ~crimsun when crimsun is correct.) [02:40] yay for wikipedia ;-) [02:41] micahcowan: yeah, we decided against it [02:42] ok, well I've got to get home and I see I've got some mentoring to do in my inbox :-) === Hobbsee [n=Hobbsee@ubuntu/member/hobbsee] has joined #ubuntu-motu [02:43] hey Hobbsee [02:43] hi zul === Fujitsu wonders if he can steal mentoring time from somebody. [02:47] <_jaldhar> Fujitsu: best to just ask your questions [02:47] _jaldhar, probably. [02:47] But I've got to go to class now. :( === _jaldhar is now known as jaldhar [02:48] Hobbsee: going for ubuntu-dev tomorrow? [02:48] zul: yep :) [02:48] assuming i'm awake [02:49] Hobbsee: heh...good [02:49] hmmm... I'm getting errors from pbuilder when building a package... errors, Makefile, debian/rules, debian/install at: http://pastebin.ca/90767 I'm looking for a shove in the direction... (not the answer) :) [02:49] zul: i'm kinda stuck if i *dont* get the upload rigts - i do lots of little fixes, and it's annoying to have to keep distracting people to get them to upload [02:49] good plan [02:49] Hobbsee: I highly doubt you won't be approved. [02:50] yeah same here [02:50] and I mean /highly/ [02:50] heck, you could probably go for -core-dev and be approved. [02:50] crimsun: hehe, i'm tempted. the stuff i'm playing with at the moment is in main. [02:53] ryanakca: the directory debian/typespeed//usr/games isn't created yet... is it in debian/dirs? [02:54] sistpoty: umm... nope... add "usr/games" to debian/dirs? [02:55] ryanakca: yep, that should solve it... dh_installdirs will create all dirs in debian/dirs. [02:55] h sistpoty [02:55] hi Hobbsee [03:01] if I'm using debuild, do I need to add "mkdir -p po" and "XGETTEXT=/usr/bin/kde-xgettext sh admin/cvs.sh extract-messages" to the end of the install rule ? [03:02] nevermind... stupid question... I looked in debian/control :) [03:03] I'me getting these errors http://pastebin.ca/90781 with those two lines of code at the end of the install rule [03:04] # [03:04] XGETTEXT=/usr/bin/kde-xgettext sh admin/cvs.sh extract-messages [03:04] # [03:04] sh: admin/cvs.sh: No such file or directory [03:04] ryanakca: i'd imagine that admin/cvs.sh never was there to start with, or got removed in clean. [03:05] ryanakca: typespeed is no kde package, no need to update the translation (and also no means to do that) [03:06] btw.: I only got a score of 440 right now... I guess I'm getting tired *g* [03:09] Hobbsee: no... never was there... === sharms [n=mindwarp@cpe-24-208-242-169.twmi.res.rr.com] has joined #ubuntu-motu [03:10] ryanakca: that's why then :P [03:10] :) === Hobbsee is really AFK now. [03:11] oh good, i'm downloading the package i modified a few days ago :) [03:11] hrrrm... I thought you were "really" AFK now :P [03:13] sistpoty: update... hasn't been translated yet :( [03:14] sistpoty: https://launchpad.net/distros/ubuntu/dapper/+source/typespeed/+translations [03:16] sistpoty: anything I can do about it? [03:18] ryanakca: not sure about rosetta... [03:19] you aren't talking about manual translation... are you? [03:19] or is there some other tool available? [03:19] ryanakca: yes, I am. [03:20] ryanakca: but you should leave the XGETTEXT="..." from debian/rules, since otherwise you'd have to write some means to import from rosetta to typespeed yourself [03:20] ryanakca: that command is pretty specific for kde package iirc [03:21] hmmm... kk... [03:24] well... its a shell command... not kde... hmmm... now that I think of it... XGETTEXT=/usr/bin/kde-xgettext kde-xgettext is useless... I'll look at the source of some command line scripts === sistpoty is now off to bed [03:32] gn8 everybody [03:32] night sistpoty [03:34] night === pschulz01 [n=paul@eth6067.sa.adsl.internode.on.net] has joined #ubuntu-motu === _jaldhar [n=jaldhar@c-68-38-202-139.hsd1.nj.comcast.net] has joined #ubuntu-motu === Arrogance [n=aks@ottawa-hs-64-26-167-180.d-ip.magma.ca] has joined #ubuntu-motu === Hobbsee [n=Hobbsee@ubuntu/member/hobbsee] has joined #ubuntu-motu [04:04] er, what was that? === Hobbsee [n=Hobbsee@ubuntu/member/hobbsee] has joined #ubuntu-motu === Hobbsee_ [n=Hobbsee@CPE-144-136-118-234.nsw.bigpond.net.au] has joined #ubuntu-motu [04:24] hi Hobbsee! I'll try to be around for the TB meeting tomorrow to cheerlead === zul [n=chuck@CPE0006258ec6c1-CM000a73655d0e.cpe.net.cable.rogers.com] has joined #ubuntu-motu === Hobbsee_ [n=Hobbsee@ubuntu/member/hobbsee] has joined #ubuntu-motu === Hobbsee_ [n=Hobbsee@ubuntu/member/hobbsee] has joined #ubuntu-motu === Hobbsee_ [n=Hobbsee@ubuntu/member/hobbsee] has joined #ubuntu-motu === _jaldhar is now known as jaldhar === Kyral [n=kyral@ubuntu/member/kyral] has joined #ubuntu-motu === Kyral [n=kyral@ubuntu/member/kyral] has joined #ubuntu-motu [04:58] hi Kyral [04:58] That [04:58] was [04:58] fscked up [04:58] Kyral: you maintaining easychem in Debian still? [04:58] Technically [04:58] hasn't been much to maintain lol [04:58] only bug reported was a typo [04:59] there's an ubuntu patch I believe [04:59] mkay...? [04:59] Hehe I haven't used a PBuilder in months [04:59] Kyral: hah. havent you seen my disconnects this morning? [04:59] Hobbsee: no the disconnects were MY doing [04:59] as in reboots [04:59] ah [05:00] I was getting my soundcard to come back suddenly [05:00]