[12:15] <Tm_T> any of you have idea about font packages?
[12:16] <crimsun> what sort?
[12:16] <Tm_T> hum, I might provide two or three font packages for ubuntu
[12:17] <crimsun> your own?
[12:18] <Tm_T> nope, xfonts-base-transcoded and 100dpi and 75dpi
[12:18] <Tm_T> both are not in breezy nor dapper atm
[12:19] <crimsun> you'll want to ask Daniel [Stone]  why they're not
[12:19] <Tm_T> ok
[12:19] <crimsun> I doubt he omitted them randomly
[12:19] <Tm_T> 22:08 #ubuntu-devel: < siretart> Tm_T: filing a bug is a good idea in any case
[12:19] <Tm_T> 23:19 #ubuntu-devel: < siretart> Tm_T: yes. or even better, provide a package ;)
[12:20] <Tm_T> I think they're dropped out because if your system is using utf-8 locales, you don't need them
[12:20] <Tm_T> and somebody is expecting we are do so
[12:20] <crimsun> that's essentially my thinking
[12:21] <Tm_T> but I (and tons of other people) does have ISO-8859-15 locales etc
[12:21] <Tm_T> but sure, I'll ask :)
[12:21] <Tm_T> but in the meantime, I (we) need packages
[12:22] <Tm_T> so, should I just take debian package and change location where fonts are installed to ubuntu way, or?
[12:22] <Tm_T> I just installed newest packages I found from debian mirrors and then copied files to right place
[12:24] <Tm_T> hum, maybe daniel can tell what I need to know ;(
[12:28] <crimsun> yep, at the very least you'll need to change the installation path
[12:30] <Tm_T> aye
[12:30] <Tm_T> I'll catch up daniel tomorrow then
[06:12] <LeeJunFan> Riddell: did something change in latest kde so that removing kubuntu-defaults and copying konqueror.rc no longer give back full functionality?
[09:17] <Hobbsee> hi everyone
[12:33] <mornfall> lalala
[12:33] <mornfall> i should mail mdz
[12:34] <Verwilst> hello!
[12:37] <Hobbsee> er...ok then!
[12:37] <Hobbsee> to reinstall breezy?
[12:56] <Verwilst> my currently-breezy desktop into dapper ;)
[12:57] <Verwilst> i'm running 5 production servers on dapper now, so i think it's fit for my desktop too ;)
[01:00] <Hobbsee> ah, right, so you're taking off breezy, and sticking dapper on there, yes, right, that makes sense now
[01:00] <Hobbsee> i was wondering how you planned to install breezy from a dapper cd!
[01:07] <Verwilst> hehe
[01:25] <Verwilst> mornfall: how's the kde update-notifier coming? ;)
[01:26] <mornfall> Verwilst: it's sitting in my systray
[01:26] <mornfall> Verwilst: it's in dapper for ages now .p
[01:26] <Verwilst> screeniiiiieeee
[01:26] <Verwilst> oh
[01:26] <Verwilst> what's it called? :)
[01:27] <mornfall> adept-notifier
[01:27] <Verwilst> but not installed by default i guess?
[01:27] <mornfall> it is, just nothing to run it automatically
[01:27] <mornfall> well, it is part of adept package
[01:27] <Verwilst> ah
[01:27] <mornfall> at least i hope so :)
[01:34] <Hobbsee> hey, cool!  it works!
[01:35] <Hobbsee> it's installed by default, yes
[01:35] <Verwilst> screeenshoooot
[01:35] <Verwilst> :p
[01:35] <Hobbsee> from me?
[01:35] <Verwilst> sure
[01:36] <Hobbsee> um
[01:36] <Hobbsee> well....seeing as it doesnt seem to *update* the apt-get list, then of course there's nothing to upgrade
[01:38] <JRe> mornfall: tough, I have errors with adept when I try to fetch updates
[01:38] <mornfall> JRe: current dapper?
[01:39] <JRe> mornfall: yep
[01:39] <mornfall> there should be a new version
[01:39] <Hobbsee> testing it out, after a manual sudo apt-get update...
[01:40] <JRe> mornfall: the one I have is 1.89ubuntu3
[01:42] <Verwilst> it's the last one according to packages.ubuntu.com
[01:42] <Hobbsee> Adept Updater: 1.88.1 Wibble (alpha 1.5) is my current one
[01:45] <Verwilst> well, here goes my install! see ya in a bit!
[02:28] <robotgeek_work> Hobbsee: ping
[02:28] <Hobbsee> robotgeek_work: pong
[02:29] <robotgeek_work> Hobbsee: i'm working on the Kubuntu Desktop guide, and i need to know if there are going to be Kubuntu Shipits
[02:29] <Hobbsee> Riddell: ping
[02:30] <Riddell> Hobbsee: pong
[02:30] <Riddell> robotgeek_work: assume yes
[02:30] <Hobbsee> robotgeek_work: I think they planned on it, but Riddell would be the one to answer that
[02:30] <Riddell> might have a better idea this time next week
[02:30] <Riddell> Hobbsee: yay!  we missed you
[02:30] <Hobbsee> :)
[02:31] <robotgeek_work> thanks Riddell , i'm currently just hacking the Ubuntu Desktop Guide, and that's good news. I just have to search replace this section :)
[02:31] <Hobbsee> and even that only a couple of times
[02:36] <robotgeek_work> hmm, i never know Kubuntu means "towards humanity" in Bemba. More changes, tsk tsk
[02:43] <robotgeek_work> one more for you Hobbsee . Kubuntu started with Hoary? or earlier/later?
[02:44] <Hobbsee> *thinks*
[02:44] <Hobbsee> robotgeek_work: ah, hoary
[02:44] <robotgeek_work> Hobbsee: thanks :)
[02:44] <Hobbsee> no problems
[02:51] <Riddell> yes, hoary
[02:52] <robotgeek_work> Riddell: i guess i'll have some nice work done by next week
[02:58] <Riddell> robotgeek_work: excellent
[02:59] <robotgeek_work> i'm editing the common sections right now, the main work will start from now on. 
[03:05] <robotgeek_work> i have kubuntu dapper running on my ibook, i hope by the time I get to system settings, the modules bug will be fixed :)
[03:06] <Verwilst> grmbl
[03:06] <Verwilst> kde is still ugly by default :(
[03:07] <Hobbsee> it is, rather
[03:07] <Verwilst> hopefully 4.0 will fix that :$
[03:18] <Verwilst> mornfall: would be cool if adept-notifier would disappear when no updates are needed
[03:20] <mornfall> Verwilst: why
[03:22] <Hobbsee> mornfall: when did 1.89 of adept-notifier go into the repos?  for some reason, I only have Adept Updater: 1.88.1 Wibble (alpha 1.5), and i just did an update&upgrade
[03:24] <Verwilst> mornfall: too many icons in the systray already :(
[03:24] <Verwilst> it'll be like windows after a while, a bigger systray than taskbar :p
[03:27] <mornfall> Hobbsee: 1.89 is a versioning mistake
[03:27] <Hobbsee> right
[03:28] <mornfall> there are 5 icons in my systray
[03:28] <mornfall> out of which at least 2 are useless
[03:31] <robotgeek_work> i'm hopfully not  8 secs away from breakage, lol
[03:33] <Verwilst> btw, by reinstalling i removed my sources.list :(
[03:33] <Verwilst> anybody has that w32codecs repo laying around?
[03:33] <Verwilst> it wasn't plf btw
[03:33] <robotgeek_work> Verwilst: marillat?
[03:34] <Verwilst> no
[03:38] <Hobbsee> Verwilst: ah, wasnt that in http://tinyurl.com/e4a5s
[03:38] <Hobbsee> or is that now out of date?
[03:40] <Verwilst> oh well, they'll do for now
[05:38] <Flosoft> hey
[05:38] <Flosoft> anyone already using PSI 0.10 with Jingle?
[05:56] <Flosoft> Riddell: Is there anyone here that could make a PSI Jingle release like those of Amarok?
[05:59] <Riddell> Flosoft: PSI?
[05:59] <Flosoft> a Jabber client
[05:59] <Flosoft> http://psi-im.org/wiki/Jingle_branch#Linux
[06:00] <Flosoft> the first with Jingle Implementation
[06:00] <Riddell> and you want what?
[06:00] <Flosoft> an .deb or an apt-source ... as mine fails to compile :S
[06:00] <Flosoft> PSI is already in the sources
[06:01] <Flosoft> but it is an old one
[06:01] <Riddell> how is that like amarok?
[06:01] <Flosoft> and the normal 0.10 (just released) does not contain Jingle
[06:01] <Flosoft> amarok is always up2date with additional sources ? ( kubuntu.org )
[06:02] <Riddell> ah, a backport
[06:02] <Riddell> i jingle support in dapper?
[06:02] <Flosoft> no
[06:02] <Riddell> so that's needed first
[06:03] <Riddell> ask in #ubuntu-motu
[06:03] <Flosoft> jingle isn't in PSIs official release
[06:03] <Riddell> hmm, psi is qt, that's our domain
[06:03] <Flosoft> :)
[06:04] <Riddell> raphink, \sh_away maybe?
[06:04] <raphink> Riddell: what?
[06:04] <raphink> Riddell: you want us to backport amarok to breezy?
[06:05] <Flosoft> no
[06:05] <Flosoft> make a PSI with Jingle backport
[06:05] <raphink> Riddell: why did you call me?
[06:05] <raphink> hmm ok
[06:05] <raphink> it's in dapper already I suppose?
[06:05] <Flosoft> note: PSI with Jingle isn't in PSIs official branch
[06:05] <Flosoft> http://psi-im.org/wiki/Jingle_branch
[06:06] <raphink> I cna't seem to find it in dapper
[06:06] <Flosoft> and it would be great to have it in Synaptic or as deb
[06:06] <Flosoft> in Breezy there is 0.93
[06:06] <Riddell> psi is in universe
[06:07] <raphink> Flosoft: can you package?
[06:07] <raphink> I can find psi Riddell 
[06:07] <raphink> but not jingle
[06:07] <Flosoft> raphink: no :S
[06:07] <raphink> apt-cache search jingle
[06:07] <raphink> I get nothing
[06:07] <raphink> in dapper
[06:07] <raphink> what's the name of the package for the jingle branch?
[06:07] <Flosoft> psi too
[06:07] <Flosoft> there is no package
[06:08] <raphink> so you would like a package, that's it?
[06:08] <raphink> you want a psi-jingle package?
[06:08] <Flosoft> yes
[06:08] <raphink> that seems easy
[06:08] <raphink> just package it ;)
[06:08] <raphink> hehe
[06:08] <raphink> Flosoft: how much do you know about Debian GNU/Linux ?
[06:09] <Flosoft> not soo much
[06:09] <Flosoft> a happy linux user
[06:09] <raphink> haha ok ;)
[06:09] <raphink> well I guess we could package it
[06:09] <raphink> but it would be nicer if you did it :)
[06:09] <raphink> so you would learn to package
[06:10] <raphink> and as this is a package you care about it's nice
[06:10] <raphink> :)
[06:10] <raphink> Flosoft: what do you think?
[06:10] <raphink> ;)
[06:10] <Flosoft> only problem: I didn't get to install psi manually :S
[06:11] <Flosoft> u know .. compile etc.
[06:11] <raphink> ah!
[06:11] <raphink> what failed?
[06:11] <Flosoft> make afaik
[06:11] <Flosoft> it was some time ago
[06:11] <raphink> ok
[06:11] <Flosoft> otherwise ... if u want to see I can open a screen here
[06:12] <raphink> no that's fine
[06:12] <raphink> I'd be happy if you could package it
[06:12] <Flosoft> ok ...
[06:12] <raphink> otherwise I can add it to my list of softs to package ;)
[06:12] <Flosoft> one sec ...
[06:13] <Flosoft> if u can guide me through I can try it again 
[06:13] <raphink> do you want some links to documents to learn how to package? ;)
[06:13] <Flosoft> sure
[06:13] <kkathman> raphink: I'd like those please
[06:13] <raphink> kkathman: <><
[06:13] <raphink> kkathman: you'd like what?
[06:13] <kkathman> the links to package...Im going to be helping robotgeek
[06:14] <raphink> https://wiki.ubuntu.com/PackagingTips
[06:14] <raphink> https://wiki.ubuntu.com/MOTUReviewingGuide once you know quite enough
[06:14] <raphink> the main link to learn to package is the Debian New Maintainer's GUide
[06:15] <raphink> http://www.debian.org/doc/manuals/maint-guide/index.en.html
[06:15] <raphink> that is THE reference to learn Debian packaging :)
[06:15] <raphink> and at least throwing an eye on Debian policy : http://www.debian.org/doc/debian-policy/
[06:15] <raphink> :)
[06:15] <kkathman> thanks
[06:16] <Flosoft> what about deb-install?
[06:16] <kkathman> do I need to be on dapper NOW to create debian packages, or can I still be on breezy?
[06:16] <raphink> Flosoft: no
[06:16] <raphink> Flosoft: packaging is an advanced feature
[06:16] <raphink> it's hand-made
[06:17] <raphink> you can use debinstall, checkinstall or whatever for your own packages if you want
[06:17] <raphink> but if you want your packages in Ubuntu
[06:17] <raphink> there won't be 10 seconds before any MOTU will refuse such a package
[06:17] <raphink> kkathman: you can still be on breezy and use a dapper pbuilder and chroot
[06:17] <raphink> to build and test the packages
[06:18] <raphink> Flosoft: using dh_make is fine to help building packages
[06:18] <raphink> but debinstall/checkinstall is not
[06:18] <raphink> you'll get much more work to do by using such things than by making the packages yourself
[06:19] <kkathman> I assume that the above documents will explain the install procedures
[06:19] <raphink> Flosoft: make me a Checkinstall GNU/Linux distro if you want to, I'm sure it won't even boot ;)
[06:19] <raphink> kkathman: yes
[06:20] <kkathman> raphink:  I still have room to install dapper if it would be best
[06:20] <raphink> for many apps, it is fine to use cdbs aswell (to some extent) which makes packaging easier
[06:20] <kkathman> I have breezy and SUSE on my box, but plenty of room for dapper if need be
[06:20] <raphink> get a chroot and pbuilder
[06:21] <kkathman> raphink: I'll read those docs and they should direct me in those right?
[06:21] <raphink> they won't teach you about chroots and pbuilders
[06:22] <raphink> but you'll need them only later
[06:22] <raphink> learn about packaging first ;)
[06:22] <raphink> and don't hesitate to ask questions :)
[06:22] <raphink> when I learned packaging, my mentor took 8 hours in a row to guide me through my first package 
[06:22] <kkathman> okies...Im sure robotgeek will guide me along
[06:22] <raphink> so don't bother to ask for some help 
[06:22] <raphink> :)
[06:22] <Flosoft> well ... u'll be flooded with questions and pastebins ... don't worry raphink ;)
[06:23] <kkathman> raphink: I was starting to work with Hobbsee but she left on vacation and there was no way we'd finish before she left, so we postponed
[06:23] <raphink> Flosoft: I prefer to be flooded with questions and pastebins and increase the number of Debian packagers with good skills
[06:23] <kkathman> but robotgeek basically said he needed my help and I agreed
[06:23] <raphink> than to make the packages myself and not be sure there'll be anyone to maintain them 
[06:23] <Flosoft> :)
[06:23] <Flosoft> at the same time i'll write a tutorial for noobs ;)
[06:23] <raphink> Flosoft: so if you feel like learning how to package, don't hesitate to ping me either ;)
[06:24] <raphink> Flosoft: there is a tutorial : NDMG ;)
[06:24] <raphink> and some guys are working on an Ubuntu packaging guide
[06:24] <Flosoft> tooo much pages ;)
[06:24] <kkathman> NDMG?
[06:24] <raphink> Laserjock 
[06:24] <raphink> New Debian Maintainer's Guide
[06:24] <raphink> the link I gave you before
[06:24] <Flosoft> http://www.debian.org/doc/manuals/maint-guide/ch-first.en.html ?
[06:24] <raphink> Flosoft: I doubt you can write a packaging guide for noobs soon 
[06:24] <raphink> yes Flosoft 
[06:25] <Flosoft> there is a problem ... PSI is in the repository :S
[06:25] <raphink> this is the current reference to learn how to package
[06:25] <Flosoft> so how do I call it PSI-Jingle?
[06:25] <raphink> Flosoft: what you want to package is psi-jingle
[06:25] <raphink> not psi
[06:25] <raphink> ;)
[06:25] <Flosoft> but it runs on the same programm :S
[06:25] <raphink> so what?
[06:26] <raphink>  ;)
[06:26] <Flosoft> ok ...
[06:26] <raphink> you might have to set the dependencies of the package
[06:26] <raphink> saying psi-jingle replaces psi
[06:27] <raphink> so the psi package is deinstalled when psi-jingle is installed
[06:27] <raphink> ;)
[06:27] <Flosoft> :S
[06:27] <Flosoft> i'll see
[06:27] <raphink> yes
[06:27] <raphink> :)
[06:27] <Flosoft> I am currently @ 2.2
[06:27] <raphink> I'll be happy to help you :)
[06:28] <raphink> check if psi-jingle is not in Debian first 
[06:28] <Flosoft> how?
[06:28] <raphink> it doesn't seem to be
[06:28] <Flosoft> ok
[06:28] <raphink> well right now it's not easy to check
[06:28] <raphink> usually you can check on packages.debian.org
[06:28] <kkathman> ok Im off to read...thanks raphink :)   I'll still be around, but probably reading.
[06:29] <raphink> but the website is currenty down
[06:29] <raphink> kkathman: ok :)
[06:29] <raphink> if you have questions just ask :)
[06:29] <Flosoft> dh_make -e your.maintainer@address -f ../gentoo-0.9.12.tar.gz .... is that from the directory the sources are unpacked?
[06:29] <Flosoft> same as there is configure etc.?
[06:30] <raphink> yep
[06:30] <raphink> that's to package gentoo of course ;)
[06:30] <Flosoft> ofcourse ;)
[06:32] <Flosoft> http://kubuntu.pastebin.com/527555 ... correct?
[06:32] <raphink> no
[06:32] <raphink> Flosoft: you have to link to the tarball
[06:32] <raphink> that is int he parent dir
[06:33] <Flosoft> well there is non :S
[06:33] <Flosoft> it is a darcs source :S
[06:33] <raphink> how did you get the source then?
[06:33] <Flosoft> darcs
[06:33] <raphink> what is that?
[06:33] <Flosoft> well like a FTP download of all files
[06:33] <Flosoft> http://psi-im.org/wiki/Darcs_Instructions
[06:34] <raphink> there is no tarball for this?
[06:34] <raphink> it's like a CVS/SVN ?
[06:34] <Flosoft> no
[06:34] <Flosoft> yes
[06:34] <raphink> ok then ignore the -f option 
[06:34] <raphink> just run dh_make -e youradress
[06:34] <Flosoft> ok
[06:34] <raphink> do you have a PGP/GnuPG key ?
[06:34] <Flosoft> and still ../psi-jingle
[06:34] <Flosoft> yes
[06:34] <Flosoft> afaik
[06:34] <raphink> no, not the ../
[06:35] <raphink> because this goes witht he -f option
[06:35] <raphink> to link to the source tarball
[06:35] <Flosoft> ok
[06:35] <raphink> since you have no source tarball
[06:35] <raphink> you shall not use it
[06:35] <raphink> you might call the directory 
[06:35] <raphink> psi-jingle-darcs
[06:35] <raphink> if you got the version today
[06:35] <raphink> call the directory
[06:36] <raphink> psi-jingle-darcs-20060128
[06:36] <raphink> and then run
[06:36] <raphink> dh_make -e youraddress
[06:36] <raphink> so the name of the package will be psi-jingle-darcs
[06:36] <Flosoft> ok
[06:36] <raphink> since it's not a tarball version, but a darcs one
[06:36] <raphink> and the version number will be 20060128, ie the date 
[06:37] <raphink> which fits for this kind of packaging
[06:37] <Flosoft> and again ... dh_make from inside psi-jingle-darcs-20060128#
[06:37] <raphink> yes
[06:37] <Flosoft> ok
[06:37] <raphink> and only with the -e youraddress@yourdomain 
[06:37] <Flosoft> sure
[06:37] <Flosoft> and what about my pgp key?
[06:37] <raphink> using an address that is in your PGP key
[06:37] <raphink> since it will be used to sign the package
[06:37] <raphink> is your key in the strongset?
[06:37] <Flosoft> ok
[06:37] <Flosoft> :S
[06:38] <raphink> what's your key ID?
[06:38] <Flosoft> I trust it unlimited
[06:38] <raphink> what's your key ID Flosoft ?
[06:38] <raphink> Flosoft: gpg --list-keys
[06:39] <Flosoft> 0xDE942B63
[06:39] <raphink> and give me your key id please :)
[06:39] <raphink> ok you never uploaded it
[06:39] <raphink> or got it signed by anyone?
[06:40] <Flosoft> i'll do it now then ...
[06:40] <raphink> no no that's fine Flosoft 
[06:40] <raphink> ;)
[06:40] <raphink> you don't need it signed now
[06:40] <Flosoft> ok
[06:40] <raphink> but you need it uploaded to the servers
[06:40] <raphink> like mit.edu
[06:40] <raphink> that can be useful ;)
[06:41] <raphink> anyway, your key will be used to sign the package
[06:41] <raphink> so you have to use an email address that is registered on the key
[06:41] <Flosoft> ok
[06:41] <Flosoft> single binary?
[06:41] <raphink> yep
[06:41] <raphink> I guess ;)
[06:42] <raphink> dh_make will create a debian/directory in the source
[06:42] <raphink> and create a lot of things in it
[06:42] <raphink> the doc explains what they are for :)
[06:42] <raphink> I'll let you read :)
[06:44] <raphink> ping me if you need Flosoft 
[06:47] <Flosoft> ok ... 3.1 .. where is the make file? raphink?
[06:47] <raphink> how do you mean?
[06:48] <Flosoft> well 3.1 they say I have to check if there are no static paths
[06:48] <raphink> oh yes
[06:48] <raphink> in the makefile
[06:48] <Flosoft> but in what file is that?
[06:48] <raphink> well you must have a makefile in the source
[06:48] <raphink> it's called makefile ;)
[06:48] <Flosoft> brb ... gotta eat
[06:49] <raphink> ok
[07:04] <Flosoft> back
[07:04] <Flosoft> well there is no makefile raphink ... wanna take a look?
[07:14] <Flosoft> raphink ... u still there?
[07:40] <Flosoft> raphink?
[08:31] <Flosoft> raphink .... u there?
[08:32] <raphink> Flosoft: sorry I was eating
[08:32] <raphink> we're watching a movie right now
[08:32] <Flosoft> ah ok ...
[08:32] <raphink> but if you have a question go on
[08:32] <Flosoft> well can u take a look @ the console I got open
[08:32] <Flosoft> there is no makefile
[08:32] <Flosoft> only for windows
[08:32] <raphink> I'll have a look
[08:32] <raphink> wait
[08:32] <Flosoft> u got the login etc in pm
[08:33] <raphink> I'm logged it
[08:33] <raphink> in
[08:33] <Flosoft> screen -x
[08:33] <raphink> where did you put it
[08:33] <raphink> ?
[08:33] <Flosoft> just run screen -x
[08:33] <Flosoft> and you'll get in the same session as I am
[09:27] <kkathman> raphink you still around?
[09:28] <raphink> yep 
[09:28] <raphink> we're packaging with Flosoft 
[09:34] <kkathman> raphink:  whats the best way to find out if a package is being worked on ... is it the same thats listed in Debian?
[09:34] <kkathman> or does Kubuntu have its list?
[09:34] <raphink> the NEW queue is very short on ubuntu
[09:34] <raphink> we don't use bugs for that as on Debian
[09:35] <raphink> if a package is being worked on in Ubuntu for quite a long time, you'll see it on REVU
[09:35] <raphink> http://revu.tauware.de
[09:35] <raphink> if it's not on REVU, not in Dapper yet
[09:35] <raphink> then it's probably not being worked on in Ubuntu
[09:35] <raphink> yet you have to check on Debian
[09:35] <raphink> and especially if an ITP has been filed for it
[09:36] <raphink> on bugs.debian.org, package wnpp
[09:36] <raphink> and if someone has made an unofficial package, on apt-get.org ;)
[09:41] <kkathman> Im just trying to figure out that if I "found" a package to work on..what I would check to make sure no one else has it or that its not being worked on
[09:41] <Tm_T> kkathman: :)
[09:42] <raphink> kkathman: I listed this on MOTUReviewingGuide
[09:42] <raphink> https://wiki.ubuntu.com/MOTUReviewingGuide#head-bac17647fdb6e11e32c96b3ad874e9074cc21610
[09:43] <kkathman> ahhh  I havent got to that one yet...been on the debian manuals thing
[09:43] <kkathman> hey Tm_T :)
[09:43] <raphink> ok
[09:43] <kkathman> sorry to bother
[09:43] <raphink> :)
[09:44] <kkathman> didnt mean to invoke your frustration :(
[09:45] <jahor> hi. is there any way to be lucky with making rcS compatible with "switching servicess off by chmod -x /etc/init.d/foo" ?
[09:46] <raphink> kkathman: my frustration ? lol
[09:46] <jahor> i have patched my rc script to not complain aboyt executable permission. and now i could simply turn off services simplier than with update-rc.d
[11:15] <raphink> kkathman: got the infos you wanted?
[11:21] <kkathman> yah still reading :)
[11:22] <kkathman> apologize for interrupting.
[11:22] <raphink> np
[11:51] <Flosoft> hey
[11:51] <Flosoft> I am looking for someone who is able to code a amarok plugin
[11:54] <Riddell> Flosoft: #amarok