[00:03] <Quintasan> Riddell or ScottK: mind reviewing if you have a second? http://dl.dropbox.com/u/69524/q4wine_0.114-r1-0ubuntu1.debian.tar.gz
[00:05] <ScottK> Quintasan: What is that?
[00:06] <Quintasan> ScottK: https://bugs.launchpad.net/ubuntu/+bug/360942
[00:07] <Quintasan> oh great, I'm missing description
[00:07] <ScottK> Quintasan: Since it's for wine, please ask Yokozar to look at it.
[00:08] <Quintasan> ScottK: okay
[00:15] <Riddell> ooh, it's Quintasan http://fridge.ubuntu.com/node/1958
[00:16] <Quintasan> Riddell: :D
[00:20] <Quintasan> Well, I'm going to bed. Good Night
[00:21] <Mamarok> nini Quintasan :)
[00:21]  * Mamarok should do that, too
[00:38] <ScottK> Riddell: live CD build worked on i386, so I think we're actually in good shape.
[03:36] <ScottK> There is good news and there is bad news:
[03:37] <ScottK> 1.  Good news: Software installation is easy enough that my totally non-technical step daughter got Skype installed with no help.
[03:37] <ScottK> 2.  Bad news: I know because her mike didn't work out of the box and I had to show her about kmix and mixer settings to get it working.
[04:03] <crimsun> that *could* be a bug (WRT #2)
[04:03] <crimsun> OTOH, we've fixed a crackton of those sorts in current ALSA
[04:04] <crimsun> meaning, we now autoselect the appropriate mic based on jack presence, so if you have an external mic plugged in, the internal mic is muted
[04:04] <ScottK> IIRC I had to tell it to use analog input instead of digital.
[04:04] <crimsun> on karmic, that would be apt-get install linux-backports-modules-alsa-karmic-generic (and a reboot)
[04:09] <ScottK> I'm actually thinking I need to take a break from Ubuntu.
[04:09] <crimsun> it's healthy
[04:10] <crimsun> I'm looking forward to the day when I can actually use it without having to drag myself away from fixing stuff
[04:10] <ScottK> I'm disproportionately upset about the whole MoM discussion.
[04:10] <crimsun> yeah, that was a bit nasty
[04:11] <ScottK> It really brings into question Canonical's reliabilty as a partner to the community IMO.
[04:11] <ScottK> "Sorry, it's broken, but we've pitched it over the fence to fix.  Good luck."
[04:11] <crimsun> well, there certainly are commercial forces driving the company's motives
[04:11] <ScottK> Certainly.
[04:11] <ScottK> I can understand that.
[04:12] <ScottK> But ditching standard tools the people have used for years because one person is too busy and recommending unreliable, incomplete replacements is not a confidence builder.
[04:12] <crimsun> I've largely avoided this particular tidbit by having merged manually from the onset, but I understand how, if led to rely on its continued presence, its recent downtime would be annoying.
[04:13] <crimsun> unfortunately, I believe the core plumbers are utterly overworked
[04:13] <ScottK> I understand the downtime (even if I'm not happy about it).  It's the "and we're not going to fix it, but we didn't tell anyone" part I dislike
[04:13] <ScottK> No doubt, but MoM doesn't take a core plumber.
[04:14] <ScottK> So the fact that it was the sole responsibility of such a person is a management failure.
[04:15] <crimsun> I don't even profess to understand how it was developed; my inclination is that Scott hacked away in a cave and emerged "victorious" after a while
[04:15] <ScottK> I took a brief look at the code and it's not that horrible.
[04:16] <maco> ScottK: didnt other-scott say he's been trying to find someone to take it over for years?
[04:16] <ScottK> maco: Certainly.  That's why it's a management failure at Canonical.
[04:17] <crimsun> While I don't doubt there's a bit of ego involved all around, I agree that it could have been announced more widely.
[04:18] <crimsun> (Then again, all around we seem to have this announce problem. None of us is immune.)
[04:25] <seele> what is MoM an acronym for?
[04:25] <crimsun> merge-o-matic
[04:25] <seele> aah, sounds technical
[04:25] <ScottK> It was.
[04:27] <maco> hi seele
[04:27] <seele> maco: yo
[04:58] <shtylman> so whats the whole MoM battle?
[04:58] <shtylman> I only really get a gist of it from the mailing lists
[04:58] <shtylman> but don't know the backstory
[05:00] <ScottK> Intially it was a closed source tool provided by Canonical.
[05:00] <ScottK> Probably written by Keybuk in his spare time.
[05:01] <ScottK> Then it stopped getting updated during one release cycle, a few people in the community got fed up and made DaD.
[05:01] <ScottK> DaD was a FOSS version of MoM.
[05:01] <ScottK> It's merging algorithm was never quite as good, but it had comments and was updated more frequently.
[05:02] <ScottK> So for a while, MOTU used DaD and Canonical people used MoM.
[05:02] <ScottK> (non-Canonical core-dev were rather less common then)
[05:02] <ScottK> Then two years ago, Canonical agreed to open source MoM and the DaD devs agreed to merge their improvements.
[05:03] <ScottK> It took some time, but it finally got done.
[05:03] <ScottK> So DaD went away.
[05:03] <ScottK> All is ~ well for a while.
[05:03] <shtylman> k
[05:03] <ScottK> There are a few community contributions, but it's not a lot of work for Keybuk to keep up.
[05:03] <ScottK> Which is good, since he has no time.
[05:04] <ScottK> Then Debian package source format V3 shows up and everytime MoM hits one, it falls over dead.
[05:05] <ScottK> Today, Keybuk got pressed to fix it and washed his hands of it.
[05:05] <maco> i thoguht he'd been blacklisting problematic packages for a months...longer than v3's been around
[05:05] <ScottK> maco: That was in the archive.
[05:05] <ScottK> As long as that was done it hit MoM irregularly.
[05:05] <ScottK> Now that v3 can go in the archive, it hits every run.
[05:06] <ScottK> The consensus from the Canonical people in the conversation was that it was unreasonable for the community to expect Canonical to continue to provide this service and we should use bzr merges instead.
[05:06] <ScottK> Which might be OK except:
[05:07] <ScottK> 1.  All through the distributed development disucssions whenever it's been brought up, there have been repeated assurances that no one would be forced to switch.
[05:07] <ScottK> 2.  There's a very long list of packages that won't import yet and so can't be done this way.
[05:08] <ScottK> 3.  It's complex and not completely documented.  Between Laserjock and I we tried 5 merges tonight and managed only one upload.
[05:08] <maco> #2: there is?
[05:08] <maco> i thought james said all the packages were in bzr now
[05:08] <ScottK> ?
[05:09] <ScottK> He may have said that, but the instructions on merging using bzr say to consult a list of packages that won't import and that list is still there and not short.
[05:09] <shtylman> hmm
[05:09] <ScottK> The one upload I managed, I only managed becuase I asked how to get stuff done.
[05:09] <maco> hm ok then... <100?
[05:09] <shtylman> I was always under the impression that merging will all happen in bzr now..
[05:09] <ScottK> I dodn't count.
[05:09] <ScottK> dod/did
[05:09] <shtylman> and that the deb sources would also be in bzr
[05:09] <shtylman> so that it wouldn't be a problem
[05:10] <ScottK> shtylman: It will because there is nothing other than a completely manual merge as an option.
[05:10] <ScottK> shtylman: That's an interesting theory.
[05:10] <ScottK> 4.  Even once you know the workflow, it has more steps, more things to go wrong, and is pretty generally inferior to the old way of doing things.
[05:11] <ScottK> The added granularity of history that using a VCS would normally give you isn't relevant for merges.
[05:12] <shtylman> I see
[05:12] <shtylman> what type of merges are we talking about here?
[05:12] <shtylman> I honestly have no idea
[05:12] <shtylman> as I have never done package management
[05:13] <ScottK> It's for when we have local changes from Debian and they update their package.
[05:13] <shtylman> I see
[05:14] <ScottK> So the Debian changes and the Ubuntu changes get merged from a common ancestor.  Then you have to figure out how much of the Ubuntu difference is still relvant and needs to be preserved
[05:14] <shtylman> makes sense
[05:14] <shtylman> seems kinda like a rebase
[05:14] <shtylman> I guess it kinda is
[05:14] <ScottK> In a sense it is.
[05:15] <ScottK> shtylman: What VCS do you use the most?
[05:15] <shtylman> mostly git
[05:16] <shtylman> obviously bzr for ubuntu stuff
[05:16] <maco> git...i should learn more git
[05:17] <shtylman> I like bzr
[05:17] <ScottK> shtylman: Right, so say you'd only used git, had used it for years, and someone took it away and gave you an alpha release of bzr that you had to use instead (or you could just not use a VCS) and they did it with no warning.
[05:17] <shtylman> I just really like some git features more
[05:17] <ScottK> I'm not opposed to bzr.  I generally like it.  I've promoted it's use on $work projects.
[05:17] <shtylman> ... yea... not good
[05:18] <ScottK> This particular use case is just not yet fully baked.
[05:18] <shtylman> I can see where that would be a problem
[05:18] <JontheEchidna> didn't they try to do that once already?
[05:18] <shtylman> I guess the migration is just hard
[05:18] <JontheEchidna> back when bzr sucked?
[05:18] <ScottK> So that's kinda the current situation from my perspective.
[05:18] <shtylman> I see
[05:18] <maco> hey i have a merging question. how should my debian/changelog look at the end?
[05:19] <ScottK> JontheEchidna: We tried it during Gutsy in Kubuntu like we are now (for the Debian dirs), but that was a team choice to try it, it wasn't required.
[05:19] <maco> combine all the changelog entries that are ubuntu-specific into one new changelog that comes after the last debian one?
[05:19] <JontheEchidna> I combine all changelog entries, sticking the new debian entries in chronological order
[05:19] <ScottK> maco: All the previous Ubuntu entries should stil be there in order.
[05:19] <ScottK> One can argue chronological or version order.
[05:20] <maco> chronological or version order?
[05:20] <maco> version order, right?
[05:20] <maco> oh
[05:20] <maco> heh
[05:20] <maco> didnt read scott's second line ;)
[05:20]  * ScottK uses vesion order generally.
[05:21] <ScottK> There are times when it doesn't quite make sense.
[05:21] <ScottK> Then the new entry at the top should document all the remaining changes.
[05:31] <maco> would you be willing to sponsor a mergey upload for me?
[05:33] <crimsun> just to point, none of the packages I oversee are imported.
[05:33] <maco> crimsun: arent they all git anyway?
[05:33] <maco> crimsun: hey wanna upload hunspell? http://people.ubuntu.com/~maco.m/needs_sponsorship/
[05:33] <crimsun> pkg-alsa is entirely SVN
[05:34] <crimsun> maco: maybe in 25 minutes; I need to walk home
[05:34] <maco> ok
[05:34] <maco> crimsun: hey did you read email from me?
[05:34] <crimsun> no
[05:34] <maco> crimsun: pm real quick?
[05:34] <crimsun> I'm really stretched thin ATM
[06:49] <crimsun> maco: your changelog is pretty curt. Which changes did you retain/drop?
[06:49] <maco> crimsun: kept all. it was a clean merge, just the changelog had a conflict
[06:50] <crimsun> can you respin with a more verbose changelog entry for the next merger?
[06:50] <maco> the ubuntu changes are just a list of extra words to add to the dictionary
[06:50] <maco> yeah
[06:50] <crimsun> no need to list them all; you can use "refer to version X for extra words"
[06:52] <maco> * Merge with Debian, keeping all Ubuntu changes (extrawords.txt and its support in debian/rules)
[06:52] <maco> that work?
[06:52] <crimsun> yep
[07:03] <maco> um, by the way...i cant test this build in pbuilder...that whole "aptitude is fubar" thing
[07:03] <maco> aptitude just spits a stacktrace at me while trying to install the build-deps
[07:04] <maco> but since it built in debian and given what the ubuntu changes are..it should theoretically build fine on the buildd
[07:04] <ScottK> maco: There's more than one way to do it.
[07:04] <maco> ScottK: im listening
[07:04] <ScottK> Look in the pbuilder config file in /ect.
[07:05] <ScottK> IIRC there's a dependency resolver option that doesn't use aptitude.
[07:06] <maco> ah i see
[07:07] <maco>  PBUILDERSATISFYDEPENDSCMD=  should i use gdebi? manpage says thats faster than classic
[07:14] <maco> ScottK: thanks! the build is running now
[07:23] <maco> crimsun: ok, reupload with more verbose changelog and with having successfully built in pbuilder
[07:23] <maco> oh my its 230am?
[07:29] <ScottK> Now it is.
[07:30] <maco> *snort*
[07:30]  * crimsun points maco toward -v20070829-2ubuntu4
[07:30] <maco> whatd i do?
[07:30] <crimsun> you forgot to include the new Debian changelog entry
[07:31] <crimsun> I rerolled the source package for you this time; just keep it in mind for next time, please.
[07:31] <maco> whatd i forget what?
[07:31] <maco> -3ubuntu1 is the new entry
[07:32] <maco> -2ubuntu4 was the previous version in ubuntu
[07:32] <maco> -3 is in debian
[07:32] <maco> so -3ubuntu1 is the new merged one
[07:33] <maco> crimsun: what>
[07:33] <maco> *?
[07:33] <crimsun> passing -v20070829-2ubuntu4 to debuild -S means "include all changelog entries *since* this version in the _source.changes"
[07:34] <crimsun> without it, you only include the most recent, which omits -3
[07:34] <maco> ooooooo i see
[07:34] <maco> im sorry. thank you
[07:34] <crimsun> np. Z.
[07:35] <ScottK> Unless of course you're doing it the new fashioned way and using bzr builddeb where -v means be verbose.
[07:49] <maco> um actually, yes i was using bzr builddeb
[07:50] <maco> i assume thisd be: bzr builddeb --old=lp:debian/blahblah  then?
[07:51] <maco> oh, probably -rREVNO
[07:52] <maco> hmm nope. not -rREVNO
[07:53] <maco> helps if i read all of --help's output...
[07:57] <ScottK> To pass -v like in dpkg-buildpackage it's -- -v.
[07:57] <ScottK> Because -S -- -v is so intuitive
[08:06] <nixternal> ScottK: bzr merging not your friend?
[08:16] <Mamarok> Riddell: for the record, cjwatson talked to doko about a glibc backport. It's in doko's hands now
[08:17] <Mamarok> the number of duplicates of https://bugs.kde.org/show_bug.cgi?id=196207 is piling up every day...
[08:19] <Mamarok> gah, the bug description is not really accurate, extends to Qt applications, too
[09:16] <jussi01> agateau: ping
[09:19] <agateau> jussi01: pong
[09:20] <jussi01> agateau: I understand you are notifications goto man?
[09:20] <agateau> jussi01: sort of :)
[09:20] <jussi01> :D
[09:24] <jussi01> agateau: Im using 4.4 beta, notifications seem well screwed. they seem to stick around forever, unless you click on the cross. ie. we get a huge accumulation of little numbers that never go down...
[09:24] <agateau> oh that, I am sort of the "alternative notifications goto man", then
[09:25] <agateau> I created Colibri just because I didn't like the Plasma notifications
[09:25] <jussi01> agateau: ahh :D
[09:25] <agateau> Not sure I can help you here, you want to discuss this with notmart on #plasma
[09:25] <jussi01> what, pray tell, is colibri?
[09:26] <agateau> http://kde-apps.org/content/show.php/Colibri?content=117147
[09:26] <agateau> jussi01: you may find this post interesting as well: http://agateau.wordpress.com/2009/12/16/introducing-colibri-an-alternative-to-plasma-notifications/
[09:28]  * jussi01 reads
[09:36] <ghostcube> agateau: hmmm i will try this passive thingy
[09:36] <ghostcube> cause i dont like this monumental plasma notifies :)
[09:37] <agateau> :)
[09:37] <ghostcube> as jussi01 sayed a lot of them if you dont cancel them
[09:37] <ghostcube> o.o
[09:37] <ghostcube> hmm is there already a package or can i ask on getdeb for packaging it o.o
[09:38] <agateau> ghostcube: I haven't packaged it, but it was (I think) nixternal who commented on the post that someone was packaging it
[09:38] <ghostcube> ah ok
[09:38] <ghostcube> nixternal: winke winke
[09:42] <Riddell> office party time!
[09:42] <ghostcube> wth this looks so borked even if its wanted
[09:43] <ghostcube> https://code.launchpad.net/projects
[09:43]  * Riddell hangs tinsel up around the place
[09:43] <ghostcube> Riddell: ??
[09:43] <ghostcube> xmas party?
[09:44] <agateau> Riddell: is this an Edimburgh-only office party? the Chapelle-Rablais office is hard at work!
[09:44] <ghostcube> seems hes busy doing nothing :D
[09:44] <Riddell> oh the Edinburgh office is hard at work, just with Slade playing in the background
[09:45] <agateau> oh ok :)
[10:01] <Quintasan> good morning
[10:02] <ghostcube> morning
[10:14] <ulysses__> 11 am is not morning:)
[10:55] <ghostcube> :P
[11:01] <Quintasan> ulysses__: depends on when you got up :P
[11:01] <ulysses__> at 7:30 :/
[11:02] <Quintasan> what a shame, I went to sleep at about 5 o clock in the morning and got up at 10
[11:02] <Quintasan> :D
[11:02] <ulysses__> can't sleep at night?:P
[11:02] <Quintasan> yeah, pretty much
[11:02] <Quintasan> during the day too :P
[11:04] <Mamarok> what did I miss about virtuoso?
[11:04] <Quintasan> Mamarok: nothing, 6.0.1 is still not working or debian guy is crazy
[11:05] <Quintasan> Mamarok: the problem is probably with virtuoso or nepomuk itself
[11:05] <Quintasan> I've tried to poke in #nepomuk-kde but there was noone answering
[11:29] <Mamarok> Quintasan|Szel: write a mail directly to Sebastian Trueg, or poke him in @nepomuk-kde
[11:46] <Mamarok> here comes a packaging problem:
[11:47] <Mamarok> gah, /me hates bash when it doesn't allow Ctrl+C *grrr*
[11:48] <Mamarok> dpkg: error processing /var/cache/apt/archives/kde-window-manager_4%3a4.3.85-0ubuntu1~karmic1~ppa3_amd64.deb (--unpack):
[11:48] <Mamarok>  trying to overwrite '/usr/share/kde4/config/aurorae.knsrc', which is also in package kwin-style-aurorae 0:0.2.1-0ubuntu1
[11:48] <Mamarok> here you go ^^
[11:50] <Mamarok> and btw, there is a typo in the website announcement:
[11:50] <Mamarok> udo apt-get dist-uprade
[11:51]  * Mamarok is not good at copy-paste today
[11:51] <Mamarok> it reads dist-uprade, missing the g
[13:57] <Quintasan> Hello
[14:08] <ghostcube> ehlo
[14:12] <Riddell> pleasingly I have no merges with my name next to it
[14:14] <Riddell> oh actually it helps if I search by my launchpad id
[14:15] <Quintasan> :D
[14:16]  * Quintasan is off to help his dad, then back to backtracing crashes
[14:17]  * jussi01 hugs Riddell
[14:21] <freeflying> ScottK: arounds?
[14:21] <ScottK> freeflying: Yes.
[15:31] <ScottK> Riddell: We're really close to having things about as built as we are going to.  How would you feel about doing your qt4-x11 upload to fix powerpc today?
[15:33] <Riddell> hmm, I havn't started looking at it, I don't know the right syntax for arch specific patches
[15:33] <Riddell> or it may need to be done in the rules file specially
[15:33] <Riddell> let me look into it
[15:34] <ScottK> Whatver you did for armel last cycle (IIRC nepomuk stuff) worked out OK.
[15:55] <ScottK> Sparc is fully built now.
[16:34] <seele_> ScottK: you have a sparc station?
[16:34] <ScottK> seele: No.  Just tracking it in Launchpad.
[16:35] <seele> ah
[16:35] <ScottK> IA64 is done now too (don't have that either)
[16:53] <Lex79> JontheEchidna: when you got a second can you ack colibri on revu? thanks
[18:07] <ghostcube> hi
[18:07] <ghostcube> updated to beta 2 worked fine :)
[18:08] <ghostcube> anyone knows who is doing the ppa for nvidia vdpau drivers ?
[18:10] <ghostcube> ah got it njsnider
[18:10] <ghostcube> bjsnider
[18:10] <ghostcube> o.o
[18:48] <ghostcube> ok Qt 4.6 and kde 4.4 beta 2 in combination with new nvidia driver definetly rox
[18:48] <ghostcube> teh fast
[18:51] <Blizzz> well, Qt 4.6 sux for me, lot of bug reports refering to it
[19:29] <zegenie> anyone have any idea about why kded4 eats 100% cpu in 4.4 beta2?
[19:34] <Riddell> no, try unloading modules or using gdb
[20:21]  * Daskreech waves
[20:23] <Daskreech> Quintasan|Szel: ping
[21:05] <Mamarok> just installed that Beta 2 stuff on Karmic, I have all my desktop settings gone (activities, etc.), 2 panels (which luckily at least kept the settings, but twice, one smaller and hard to get rid of) and plasma crashes galore. I guess this is to be expected?
[21:05] <Mamarok> Oh and Akonadi doesn't run anymore
[21:07] <Mamarok> +: it's fast, desktop effects work like double speed now
[21:07] <Daskreech> back up ~/.kde before upgrades
[21:48] <dhillon-v10> nixternal, hi :D I looked at the lucid todo for kubuntu and are there any developmental tasks I can take part in
[22:28] <ScottK> Mamarok: https://launchpad.net/ubuntu/+source/eglibc/2.10.2-2ubuntu4
[22:29] <ScottK> Riddell: kdepim finally finished on armel, so that's fully built too.
[22:30] <txwikinger> http://www.techradar.com/news/software/operating-systems/8-of-the-best-kde-distributions-657523?artc_pg=3
[22:30]  * ScottK now waits for Riddell brilliant debian/rules hack for powerpc only patches
[22:33] <ScottK> txwikinger: You have been busy.  We all chatted about that ages ago.
[22:40] <dhillon-v10> ScottK, hi :D how are you
[22:40] <ScottK> dhillon-v10: Busy
[22:41] <dhillon-v10> ScottK, do you have any idea when merge-o-matic is going to be back, I heard its down right now
[22:42] <ScottK> Never unless someone fixes it.
[22:42] <dhillon-v10> ScottK, alright that's good enough for an answer :D I just continue my work as it then
[22:43] <ScottK> dhillon-v10: The answer wasn't a joke.  It's completely maintainerless right now, so unless someone volunteers to work on it, it won't get fixed.
[22:43] <Mamarok> ScottK: what about the backport to Karmic?
[22:44] <ScottK> Mamarok: Rules say it has to be fixed in the development release first, so this would be step one.
[22:44] <dhillon-v10> ScottK, I am really good at web designing, much better than packaging, can I get working on it, please
[22:44] <ScottK> All I know is I say it building.
[22:44] <Mamarok> OK, nice to know :)
[22:44] <ScottK> dhillon-v10: Source is in the merge-o-matic project on Launchpad.
[22:45] <dhillon-v10> ScottK, alright so what's the main problem behind it, is it not updating the packages
[22:45] <ScottK> dhillon-v10: It needs to deal with v3 format source packages.
[22:46] <dhillon-v10> ScottK, what's v3 format package
[22:46] <ScottK> dhillon-v10: Remember the start of the conversation where I said I was busy?  Google can help you with that one.
[22:47] <dhillon-v10> ScottK, I am sorry I didn't mean to bother you, I'll google that
[23:21] <Zorael> Is the Akonadi kcm module being transitioned out in 4.4? I see it's still in kdepim-runtime but it doesn't have a .desktop service entry.
[23:22] <ScottK> Zorael: It's in a separate binary now.
[23:22] <ScottK> (I think)
[23:33] <JontheEchidna> Zorael: upstream decided to remove the module, since basically the only thing you could do with it is break Akonadi (unless you really knew what you were doing)
[23:34] <Zorael> JontheEchidna: Ah, okay, makes sense.
[23:39]  * Riddell puts up some mistletoe here too and stand underneith it
[23:49]  * claydoh dcc's smooches to Riddell :)
[23:49] <Riddell> yay!
[23:51]  * claydoh is enjoying his beta2 presents , many thanks to all!
[23:52] <Riddell> ScottK: what do you think of this? http://bazaar.launchpad.net/%7Ekubuntu-members/qt/ubuntu/revision/50
[23:52] <Riddell> I've really no idea if that's the right syntax in rules
[23:52] <ScottK> Looking
[23:54] <nixternal> unix:!mac:*-g++*:QMAKE_LFLAGS += -Wl,--gc-sections   <- is this common for removing this line?
[23:54] <nixternal> back in the day, I would add that line when building on my old mac
[23:55] <crimsun> the linker explodes on ppc with --gc-sections
[23:55] <crimsun> meaning 10.04's current linker explodes on ppc
[23:57] <ScottK> Riddell: Looks right.  Looks similar to what you did in http://bazaar.launchpad.net/~kubuntu-members/kdebase-runtime/ubuntu/revision/69
[23:59] <ScottK> Of course I left the #ENDIF of of my IA64 build fix on the first try, so don't go by me.