[00:11] <directhex> does it need to be modified? can't it go into the upstream kblog?
[04:00] <superm1> dtchen, ping.  are you around momentarily to talk to a mythtv dev about pulseaudio?
[04:03] <jdong> superm1: he told me 90 minutes 30 minutes before your ping.
[04:03] <jdong> (unrelated audio trap)
[04:04] <superm1> ah thanks
[04:12] <superm1> dtchen, well when you get back to your keyboard, i may not be here, but if you can drop in #mythtv, danielk22 is one of the main mythtv devs and is seeing loads of issues latency wise with pulse. if you can pop in there and speak to him about them and/or fire him an email at danielk@cuymedia.net, we'd appreciate it
[05:26] <dtchen> superm1: sure, i'll e-mail, thanks for the heads-up
[05:33] <superm1> thank dtchen
[07:41] <mrooney> is there any reason that "chown .users dir; chmod g+w dir" doesn't allow everyone to write to "dir/" ?
[07:42] <mrooney> I am going crazy trying to share this packaging stuff between two users on my machine
[07:43] <lifeless> its not sticky
[07:43] <mrooney> lifeless: what does that mean?
[07:44] <lifeless> just that
[07:44] <RAOF_> That files created in there will not have the directory's permissions, but will have the creating user's umask.
[07:44] <lifeless> it allows the group to write to dir, but doesn't affect the permissions of things created withint it
[07:44] <lifeless> neither their group, nor their mode
[07:46] <mrooney> lifeless: ah so if I do +t on the dir, then user a can create a directory and user b can remove it?
[07:47] <jdong> mrooney: delete permissions are handled by write permissions on the directory
[07:47] <mrooney> jdong: right, so the answer is..? :)
[07:47] <jdong> mrooney: marking a directory sticky causes everything created inside it to inherit the directory's permissions
[07:47] <jdong> which is clearly helpful in a shared dir setup
[07:48] <mrooney> ah excellent, that sounds like just what I want!
[07:54] <mrooney> jdong: any idea why with the directory "drwxrwxr-t  4 michael users 4096 2009-04-03 19:18 test" I can't mkdir test/something, I get perms denied
[07:58] <jdong> mrooney: you're sure you're in users?
[08:03] <mrooney> jdong: oh, I guess not! I assumed that "users" was all users due to the name and also seeing all users listed in "Users and Groups"
[08:03] <jdong> hehe :)
[08:03] <mrooney> thanks for the help :)
[08:04] <jdong> of course :) don't forget to logout/login to apply group changes.
[08:04] <mrooney> maybe in the future I should use cdrom or something everyone will reasonably be
[08:04] <mrooney> I wonder why 'users' exists if it isn't all users
[08:08] <Toadstool> g'morning
[10:48] <AnAnt> Hello, I am making a package that needs to have /var/run/dicod and  /var/lib/dicod, those will be empty during install, but would be populated during runtime, so should I create those dirs in postinst or should I install those empty dirs in the deb file itself ?
[10:50] <mok0> AnAnt: yes.
[10:50] <AnAnt> ?
[10:50] <mok0> AnAnt: use a .dirs file
[10:50] <AnAnt> ok
[10:50] <AnAnt> thanks
[10:50] <AnAnt> won't lintian complain about empty dirs in deb file ?
[10:50] <mok0> AnAnt: no
[10:50] <AnAnt> ok, thanks
[10:51] <mok0> AnAnt: only if you ship /usr/bin or something like that
[10:51] <AnAnt> ok
[10:53] <AnAnt> mok0: and chown them in postinst ?
[10:53] <mok0> AnAnt: who needs to own the dirs?
[10:53] <AnAnt> user created by postinst
[10:54] <wgrant> Watch out - /var/run is a tmpfs
[10:54] <soren> AnAnt: Note that /vaR/run/dicod should be created in an init script, since /var/run is a tmpfs.
[10:54] <mok0> AnAnt: well, then chown the dirs after the user has been created
[10:54] <soren> Or from within the application or whatever.
[10:55] <mok0> ah
[10:55] <mok0> of course
[10:55] <AnAnt> soren: thanks !
[10:56] <mok0> AnAnt: you need a postrm script to remove the stuff you create as well
[10:58] <AnAnt> mok0: you mean /var/lib/dicod/ ?
[11:06] <mok0> AnAnt: as said above, you need to create /var/run/dicod in the postinstall script. You can create /var/lib/dicod in a <package>.dirs file
[11:08] <mok0> AnAnt: then /var/lib/dicod will be deleted when the package is removed, but not the user
[11:08] <mok0> AnAnt: /var/run/dicod will be on a tmpfs, so it will be removed automatically as well
[12:51] <soc1> hi
[12:53] <soc1> i uploaded a package to my ppa, but i just got an email: "Rejected: Signer has no upload rights at all to this distribution. [...]"
[12:54] <soren> How did you upload it?
[12:54] <directhex> soc1, you may have accidentially uploaded to the main archive instead of your ppa
[12:56] <soc1> uh ...mom
[12:56] <soc1> how could i have done that?
[12:57] <soren> How did you upload your package?
[12:57] <soc1> dput merkaartor_0.13.1-0ubuntu1_source.changes
[12:57] <soren> Yup, that's how you upload to Ubuntu, not your ppa.
[12:58] <directhex> you forgot a target repo
[12:58] <directhex> dput reponamefromdputdotcf foo.changes
[12:58] <soc1> ok thanks
[12:58] <soren> Or just:
[12:58] <soren> dput ppa:your_launchpad_id something.changes
[12:58] <soc1> i thought dput .changes would be enough ---
[12:58] <soc1> because my own repo is the only one in .dput.cf
[12:58] <soren> There's also /etc/dput.cf
[12:59] <soc1> ah ok
[12:59] <soc1> thanks
[13:00] <soc1> btw, what do i have to do with packages which i updated, but the maintainer has his packaging in his svn?
[13:00] <directhex> try to team up with the maintainer
[13:00] <directhex> or at least send hima  debdiff
[13:22] <soc1> hi
[13:22] <soc1> could someone test merkaartor from my ppa?
[13:22] <soc1> https://launchpad.net/~soc-krg-nw/+archive/ppa
[13:24] <soc1> it's an app to create maps with a gps and openstreetmap
[13:24] <soc1> i would just be intersted, if you are having performance problems with it
[13:24] <soc1> because on my pc it made my pc totally unresponsive ... i think it's a problem with my nvidia gpu, but i would need someone to verify that ...
[14:10] <wintellect> apt-cache search for nucurse (the lib) returns lubncurses4 and libncurses5 - is there no generic one to include? Or is it a necessity to specify a version in the depends version of the control file?
[14:10] <wintellect> s/ncurse/ncurses/
[14:12] <geser> wintellect: you don't specify the version of libraries in (runtime) depends at all but use dh_shlibdeps during build for it
[14:13] <geser> it will fill the needed packages the binaries need
[14:13] <wintellect> geser: ok - where can I readup on dh_shlibdeps ?
[14:13] <Jimbo> Hey guys.  Over the weekend I put together my first package.  Is there a place that I could submit it for review?  Currently it is up on launchpad
[14:14] <geser> wintellect: it's part of debhelper; man dh_shlibdeps
[14:36] <wintellect> geser: ok, that worked its magic... "shlibs:Depends=libncurses5 (>= 5.6+20071006-3), libc6 (>= 2.4)"   would still love to know how it worked that out. Seems like magic at the mo
[14:37] <hyperair> wintellect: ldd any binary and you'll see
[14:37] <hyperair> wintellect: ldd /path/to/ELF_binary_or_so
[14:37] <hyperair> well that and a shlibs file which is shipped with lib packages
[14:39] <wintellect> so it takes the ldd of the final binary to calculate it?
[14:42] <hyperair> wintellect: probably something to that effect, yes
[14:42] <wintellect> hmmm... ok, it fails with pbuilder
[14:43] <hyperair> that's because you don't have the required library
[14:43] <hyperair> probably
[14:43] <wintellect> saying it can't find ncurses.h
[14:43] <wintellect> yeah
[14:43] <hyperair> libncurses-dev
[14:43] <wintellect> so where do I add that entry - the control file?
[14:43] <hyperair> or something
[14:43] <hyperair> add that to build-dep
[14:43] <hyperair> in control
[14:43] <wintellect> Ahhh, k
[14:43] <wintellect> makes sense
[14:43] <hyperair> =)
[14:43]  * wintellect slaps self with a wet fish
[14:52] <wintellect> YAY - it built. But installed in the wrong place. Need to look at the Makefile me thinks
[14:55] <soc1> could someone test merkaartor from my ppa? it's an app to create maps with a gps and openstreetmap. i would just be intersted, if you are having performance problems with it, because on my pc it made my pc totally unresponsive ... i think it's a problem with my nvidia gpu, but i would need someone to verify that ... https://launchpad.net/~soc-krg-nw/+archive/ppa
[15:00] <AnAnt> Hello, is there a tool like requestsync to request a merge ?
[15:02] <wintellect> If an app comes with a hardcoded Makefile - is it ok to manually fix it to make the package work?
[15:04] <bddebian> Heya gang
[15:06] <AnAnt> wintellect: yup, patch it
[15:07] <AnAnt> bddebian: how are you ?
[15:07] <AnAnt> do you know if  there is a tool like requestsync to request a merge ?
[15:07] <bddebian> Hi AnAnt
[15:20] <wintellect> AnAnt: am about to watch the youtube video on patching with Daniel Holbach :D
[15:21] <AnAnt> wintellect: huh ?
[15:22] <wintellect> http://www.youtube.com/watch?v=SAxFpKBG-bU
[15:24]  * directhex wants a video on how to use git without committing suicide
[15:25] <cody-somerville> git is eww
[15:25] <cody-somerville> bzr is yay!
[15:25] <directhex> cody-somerville, when all's said & done i just want a way to collaborate on packaging. but whilst i can wrangle the svn-based bits fine, git is boo
[15:27] <soc1> cody-somerville: there aren't many differences between git an bzr, are they?
[15:27] <cody-somerville> bzr just works
[15:27] <soc1> git is a bit faster and has github and bzr is a bit slower and has launchpad ...
[15:27] <soc1> cody-somerville: under which conditions doesn't git work
[15:27] <cody-somerville> git works
[15:28] <cody-somerville> bzr just works
[15:28] <soc1> ah ok :-)
[15:28] <cody-somerville> as in Just Works (TM)
[15:28] <cody-somerville> git's error messages can be confusing
[15:28] <soc1> i never do mistakes :-P
[15:28] <cody-somerville> and having to re-add files to resolve a conflict seems weird to me
[15:28] <cody-somerville> and then the whole fast forwarding thing is weird
[15:29] <cody-somerville> git says you can fast forward but you can't really fast word - it isn't an action
[15:29] <soc1> ah ok
[15:29] <cody-somerville> I do like how git tells me where I am in relationship to the parent though
[15:29] <cody-somerville> and I hate how bzr's revision history isn't immutable
[15:30] <soc1> mhh, but cvs and svn isn't dying fast enough ...
[15:30] <soc1> although most open-source projects have gone to dvcs ...
[15:31] <soc1> mhh could you look at my merkaartor package?
[15:31]  * cody-somerville nods.
[15:31] <cody-somerville> me?
[15:31] <soc1> yes
[15:31] <cody-somerville> lol
[15:32] <soc1> i would just need to know if it makes your pc unresponsive or not ...
[15:32] <cody-somerville> I'm the Xubuntu Project Lead
[15:32] <cody-somerville> I run an old computer
[15:32] <soc1> ah ok
[15:32] <cody-somerville> Of course it'll make my pc unresponsive - almost everything does :P
[15:32] <soc1> so no qt packages on the harddisk :-)
[15:32] <cody-somerville> that too
[15:32] <soc1> yes, but on my pc it almost killed it
[15:33] <cody-somerville> doh
[15:33] <soc1> 20 seconds where nothing responds then a half second where you could click on something then 20 seconds of total freeze agian ... and so on ... for 5 minutes until i could kill it
[15:34] <soc1> i only saw that xorg used 50% of the cpu ...
[15:34] <soc1> i fear it has soemthing to do with the nvidia gpu
[15:34] <soc1> because on my laptop with a ati radeon everything works absolutley smooth
[15:36] <soc1> oops, closed the window ...
[15:46] <Jimbo> Hey everybody.  I created my first package over the weekend.  Currently it's on launchpad, what's the next step for submitting it to ubuntu?
[15:47] <directhex> Jimbo, google "revu"
[15:48] <Jimbo> thanks directhex
[15:50] <hyperair> Jimbo: http://www.lmgtfy.com/?q=revu
[15:50] <Laney> unnecessary ;(
[15:51] <iulian> Hah
[15:51] <Jimbo> hyperair, Is this not the right channel for a question like that?
[15:51] <Laney> Yes, it is
[15:53] <RainCT> Is the fallback in /usr/bin/compiz needed nowadays?
[15:53] <hyperair> =p
[15:53] <hyperair> sorry, i was uh debugging my lmgtfy script =p
[15:54] <RainCT> (I ask because it breaks gnome-shell if you start it when Compiz is running)
[15:54] <hyperair> RainCT: it's hard to start a window manager if you don't have one running already.
[15:54] <hyperair> yo e-jat
[15:58] <e-jat> yo hyperair
[15:59] <hyperair> =)
[16:03] <wintellect> I'm slightly confused. I made changes to the Makefile so the app installs correctly - how do I ensure those changes are added?
[16:18] <wintellect> nm, ignore me
[16:18] <ScottK> Done
[16:24] <imbrandon> morning all
[16:26] <imbrandon> skype + ipod touch ( 2nd Gen ) + iphone headphones & mic == love
[16:55] <wintellect> ScottK: thanks :P
[18:39] <balachmar> Hi, I want to try and fix bug #337926 For I have also found this problem to exist when using x2x. Does anybody else know if anyone is working on this, or how to find out?
[18:40] <hyperair> balachmar: notice that it says [Medium,New]
[18:40] <hyperair> balachmar: Medium is priority. New is status. if someone was working on it, it'll be In Progress.
[18:41] <hyperair> well should be.
[18:41] <balachmar> hyperair: OK new is the status :) (should have known that...) Well one of the last posts says there is a fix. So I shall try and but some of the bug fixing lessons into action.
[18:42] <hyperair> =)
[18:42] <hyperair> good luc
[18:42] <hyperair> k
[18:42] <mok0> balachmar: assign the bug to yourself, and set status to "In progress"
[18:44] <helbuns> hello everyone, i'm running through the packing guide tutorial on hello, i had a question on the change log. my change log has this "hello (2.1.1-1-0ubuntu1) jaunty; urgency=low", but the deb one has "hello-debhelper (2.2-3) unstable; urgency=low". so do i rewrite the debs to  look like "hello-debhelper (2.2-3-0ubuntu1) jaunty; urgency=low" ??
[18:45] <binarymutant> helbuns, ya
[18:46] <helbuns> sweeeeeeet, thanks man
[18:46] <binarymutant> helbuns, actually it might be 1ubuntu1
[18:46] <helbuns> oh okay, in the future how do i know what number that is? or what does it reference
[18:47] <mok0> helbuns: -0ubuntu1 means the package is not in Debian
[18:47] <binarymutant> helbuns, if debian has it, it's 1ubuntu1, if debian doesn't have it it's 0ubuntu1. It goes: (debian-version)ubuntu(ubuntu-version)
[18:48] <binarymutant> if that makes any sense :/
[18:49] <helbuns> ohhhhhhhhh i see.... if they have it... meaning it's no an ubuntu specific package, which of course i can check first... then i put their number, otherwise its a 0
[18:49] <helbuns> and of course. you put the ubuntu number last
[18:49] <binarymutant> ya
[18:50] <dlynch> binarymutant: so this is correct, right? 0.0.8~b7-0~ppa1 (here the deb exists only as a PPA)
[18:50] <binarymutant> helbuns, in your example I would say it's 3ubuntu1 ?
[18:50] <GuyFromHell> If I'm to be making a patch to a file, do i patch against the fully patched version? or the upstream version? i can't tell from https://wiki.ubuntu.com/MOTU/Contributing but my gut says patched
[18:50] <helbuns> this is sweet... wait now i gotta ask, hello (2.1.1-1-0ubuntu1), that package says 2, so shoudl i make it ubuntu2
[18:50] <helbuns> biinarymutant, thanks i see what
[18:51] <helbuns> 's goin on now i think
[18:51] <binarymutant> dlynch, it's only relative to whats in the debian and ubuntu repos, not in PPAs
[18:52] <dlynch> binarymutant: since my package doesn't exist in either the debian or ubuntu repos, in that case should I name it something like apid-photo-downloader - 0.0.8~b7~ppa1 ?
[18:53] <dlynch> whoops, I mean rapid-photo-downloader-0.0.8~b7~ppa1
[18:53] <hyperair> you need a debian revision all the same. how about -0ubuntu1~ppa1?
[18:53] <hyperair> the stuff after "-"
[18:53] <binarymutant> dlynch, if it's going into ubuntu I would name it 0ubuntu1, if it's just staying in you ppa I doubt there's any policy on the naming scheme
[18:53] <hyperair> i personally use upstreamversion-0+ppa1.
[18:54] <dlynch> one day I would like it in ubuntu, but it's a bit rough around the edges for now...
[18:54] <binarymutant> dlynch, I would name it 0ubuntu1 then but I guess its all personal preference when it comes to PPAs
[18:55] <dlynch> binarymutant: thank you
[18:55] <binarymutant> np
[19:00] <binarymutant> GuyFromHell, you patch against the deb, if that answers the question
[19:01] <GuyFromHell> binarymutant, yes i believe it does. thank you
[19:06] <pochu_> so who is attending UDS?
[19:10] <binarymutant> will there be video again from UDS? I really liked the interviews that were put up on youtube
[19:11] <GuyFromHell> Can i get someone to message me (checking a patch im' making for xchat)
[19:12] <a|wen> GuyFromHell: works?
[19:12] <GuyFromHell> a|wen, yep, thanks to binarymutant
[19:13] <a|wen> :)
[19:13] <a|wen> GuyFromHell: you needed a private message as well, or this wa okay?
[19:14] <GuyFromHell> a|wen, i just needed something that will popup messages in quick succession. either way would have worked ^_^
[19:15] <a|wen> he
[19:27] <GuyFromHell> Okay so, if there's a patch, lets call it 71_im.dpatch, that changes a string to 'im' when it should be 'IM', should i be making 72_IM.dpatch or edit 71_im.dpatch and diff against that?
[19:30] <mok0> GuyFromHell: Add a new patch
[19:30] <pochu> stgraber: are you attending UDS this year?
[19:30] <mok0> GuyFromHell: easier to maintian
[19:31] <GuyFromHell> mok0, alrighty, will do that then
[19:52] <Laney> mok0: huh? If a patch is wrong then it should be fixed
[19:53] <james_w> I'd say that mok0's rule might be reasonable if the original patch was from Debian, but if it is an Ubuntu patch then fix it up directly
[19:54] <Laney> I'd rather fix the patch and send it back
[19:55] <Laney> patching the same line twice for the same problem seems crackful to me
[19:55] <james_w> true
[19:55] <james_w> if it's something that Debian have rejected then I would find a separate patch more maintainable, but some may disagree
[19:56] <quadrispro> hi guys
[19:56] <Laney> howdy
[21:57] <wintellect> Evenin all
[21:58] <jpds> Evening wintellect.
[21:59] <wintellect> jpds: I've built a new package (that wasn't listed as needs-packaging in launchpad). What's the next step to get it approved/reviewed, whatever?
[21:59] <Laney> !revu
[22:00] <Laney> wintellect: ^
[22:00] <jpds> wintellect: Upload it to revu^
[22:00] <wintellect> Ahhh, key
[22:00] <wintellect> erm... "kay"
[22:00]  * Laney is dying due to a stupidly hot curry
[22:00] <Laney> thanks dad :(
[22:01] <jpds> Laney: I know the feeling...
[22:01] <Laney> he likes to bring me food when he comes up, then asks me how it was with a knowing grin when I next see him
[22:01] <Laney> child abuse, that is
[22:01] <Laney> even though I'm 23
[22:02] <wintellect> oh dear (cue excitement) : "Feature Freeze is currently in effect and new packages are no longer accepted into Ubuntu Jaunty"
[22:02] <wintellect> from REVU site
[22:02] <Laney> that's right
[22:03] <Laney> karmic is your friend now
[22:04] <jbailey> Laney, Curry isn't good unless you can feel your intestines bleed.
[22:05] <Laney> jbailey: I'll tell you how good it was tomorrow then...
[22:07] <wintellect> Does it matter if my gpg signature takes the form:   foo bar (nick) <email address>   ?
[22:07] <wintellect> I notice the examples don't have the "(nick)" bit
[22:07] <wintellect> is that an issue?
[22:08] <jpds> That can't be your name.
[22:08] <jpds> wintellect: No, I don't think it will be, just try it and see.
[22:09] <wintellect> The signing bit works - just wanted to make sure it doesn't break any MOTU rule or something
[22:10] <Laney> not one that I'm aware of
[22:12] <hyperair> if you were that paranoid, just alias it or something
[22:17] <dtchen> siretart_: do you plan to backport the xine-lib fixes from 1.1.16.3 for bug 355825?
[22:17] <dtchen> siretart_: i've committed the PulseAudio fixes (they will be in the next Jaunty upload)
[22:26] <sladen> http://launchpad.net/bugs/356615  FFe data-package-only request if anyone's awake
[22:28]  * nhandler goes to look
[22:32] <nhandler> sladen: The FFe itself looks pretty reasonable, but the packages are not ready to enter the repositories. For instance, look at the warnings displayed for http://revu.ubuntuwire.com/p/bve-route-cross-city-south
[22:33] <siretart_> dtchen: feel free to upload, I'll import your upload in the hg branch then, ok?
[22:34] <sladen> nhandler: warning (1) is the Maintainer:   (2) is "unreleased", which I'm going to set in Git until I do a release
[22:34] <siretart_> dtchen: if you have your work already in hg, feel free to submit your patches via mail
[22:35] <sladen> nhandler: (there ar eno other warnings)
[22:35] <dtchen> siretart_: err, i can only attach debdiffs (i don't have upload privileges...)
[22:35] <Laney> dtchen: Don't suppose you know anything about bug 346204?
[22:36] <dtchen> Laney: it's queued, but i may not get to it this evening
[22:36] <Laney> no worries
[22:36] <Laney> thought I'd ask incase it slipped the radar
[22:36] <dtchen> well, with a few hundreds bugs on my radar ...
[22:36] <nhandler> sladen: (1) You are technically required to use an @ubuntu.com email address for the maintainer. (2) You are meant to change this prior to uploading to REVU. But I get I can ACK the FFe. Someone else will need to Advocate the packaging
[22:36] <Laney> indeed
[22:37] <siretart_> dtchen: debdiff is fine. I need to check with darren, I think he is working on a new upload to sid, which I'd prefer to merge. there is a sec. issue pending...
[22:38] <dtchen> siretart_: ok, if you're going to merge in time for jaunty, then i'll refrain
[22:43] <sladen> nhandler: groovy, I'll add the (LP: #bug number) and prepare it
[22:44] <nhandler> sladen: Just give me a little bit to finish up what I am working on
[22:50] <siretart_> dtchen: feel free to push me in case I forget, but I'll try to do it
[22:51] <dtchen> siretart_: thanks
[22:55] <Ampelbein> hi! could some MOTU have a look at bug 352653?
[23:02] <sladen> siretart_: can I safely push a same-version-number to REVU without having to do a full .orig upload
[23:03] <sladen> siretart_: (tried this by using -sd  and managed to upset it)
[23:03] <jpds> sladen: No, REVU doesn't behave like a proper debian archive.
[23:03] <mok0> sladen: yes, no problem
[23:03]  * sladen smiles
[23:04] <dtchen> IOW, yes you no
[23:04] <jpds> You  could try, but I think it'll complain that it can't find the .orig in the uploads directory.
[23:04] <mok0> sladen: REVU creates directories for sources based on date/time
[23:05] <sladen> anyway, so I /did/ try this (forcing -sd) and got a "cannot unpack directory"
[23:05] <mok0> sladen: use debuild -S -sa
[23:06] <sladen> mok0: I'm trying to /avoid/ uplaoding 30MB.  Not force it
[23:08] <jpds> sladen: Upload the .dsc and .diff.gz and .changes somewhere and I'll copy the .tar.gz from the pervious upload across.
[23:08] <jpds> Might want to /msg me the URL for the .changes
[23:09] <sladen> jpds: ta!
[23:14] <xnox> Hi everyone! If I remember correctly there was at one point somewhere a script mentioned which creates / uploads source packages for multiple ubuntu series ready to be uploaded to launchpad straight from the bzr-builddeb managed package. Can someone please point me to it?
[23:31] <xnox> nevermind found it! it's called autoppa
[23:31] <xnox> and it was featured in launchpad blog
[23:32] <xnox> cheers anyways and happy hacking everyone ;-)
[23:54] <kb9vqf> I was referred here about possibly getting my Intrepid + Jaunty KDE3.5 packages into the official repositories...any advice? ;-)
[23:55] <cody-somerville> You probably want to talk to the folks in #kubuntu-devel
[23:56] <kb9vqf> I just came from there...
[23:57] <kb9vqf> daskreech suggested that I start here