[15:03] <Jonopoly> does lubuntu 19.04 have hwe kernal?
 No
 Jonopoly but you can install the package.
 sorry, apparently 19.04 doesn't have hwe
[15:16] <Jonopoly> thanks lubot
[17:21] <The_LoudSpeaker> lubot bhaiya is so helpful. How so helpful bhaiya? Teach us also bhaiya! lubot bhaiya is so pro! _/\_
[17:22] <The_LoudSpeaker> XD


[00:00] <UndiFineD> LjL, I always forget these silly little things
[00:00] <topyli> welcome to the funny farm
[00:00] <LjL> UndiFineD: now you'll be pointed and laughed at in most channels you join! \o/
[00:00] <topyli> hehe
[00:00] <rww> and are able to kickban LjL from here
[00:01] <rww> I mean... congratulations!
[00:01] <UndiFineD> hah
[00:03] <UndiFineD> I am not wearing steel pointed shoes
[00:03] <UndiFineD> high heels are for my GF
[00:10] <topyli> UndiFineD: your cloak has a typo, i requested a fix :)
[00:11] <rww> lol.
[00:11] <topyli> your own fault for having a creative nick!
[00:12] <rww> that is longer than 3 characters
[00:12] <UndiFineD> hah
[00:13] <topyli> yeah. doubles are allowded (6), but unconvenional spelling is just weird
[00:13] <UndiFineD> indeed it is intentional
[00:14] <UndiFineD> in the past I could simply find all pages with my nick, but typo's overruled that
[00:14] <topyli> i'm sure. staff just read it wrong. worry not, they'll fix it once they get around to it
[00:15] <UndiFineD> now if only they'd let me in on linkedin, for which I had requested access 5 times already
[00:15] <topyli> huh? can't everybody join?
[00:15] <topyli> oh you mean the ubuntu members group there
[00:15] <UndiFineD> yeah
[00:16] <rww> isn't MTeck the one in charge of that?
[00:16] <topyli> maybe it's unmaintainded. who's supposed to.... oh
[00:16] <rww> yes, he is
[00:16] <topyli> UndiFineD: so poke him
[00:17] <UndiFineD> no it is maintained, but they do not read messages well
[00:17] <rww> he isn't online. memoserv! (mtecknology)
[00:17] <rww> although hrm, apparently he's online under a different nick somewhere
[00:17] <rww> aha! EvilMTeck
[00:18] <topyli> boo
[00:18] <topyli> that's staff tradition
[00:18] <rww> UndiFineD: it's now fixed
[00:18] <topyli> yay
[00:19] <UndiFineD> cool
[00:43] <EvilMTeck> EvilMTeck: hm?
[00:44] <MTecknology> topyli: I like it though
[00:44] <rww> wannabee staffer ;P
[00:44] <rww> anyways UndiFineD wanted to join your LinkedIn Ubuntu thingadoodle
[00:45] <MTecknology> is he one of the people that never listened to the email I sent to them?
[00:45]  * MTecknology looks
[00:45] <rww> dunno
[00:46] <UndiFineD> I doubt that
[00:46] <rww> MTecknology: I'm not planning on using LinkedIn ever, but I'm vaguely curious: what's in the email?
[00:48] <MTecknology> rww: I actually don't remember... every time i click decline there's an auto message sent out - let me go grab it
[00:49] <UndiFineD> MTecknology, would you decline the same person 3 times on the same day ?
[00:49] <UndiFineD> without looking at the message they send
[00:50] <MTecknology> rww: http://dpaste.com/545157/
[00:50] <MTecknology> that message lies though... linkedin doesn't let me use email verification - which made things easy
[00:51] <MTecknology> UndiFineD: name?
[00:52] <UndiFineD> k.dejong
[00:52] <UndiFineD> Keimpe de Jong
[00:53] <MTecknology> I don't see your request listed
[00:54] <UndiFineD> no it has been a while
[00:54] <MTecknology> https://launchpad.net/people/?name=de+Jong%2C+Keimpe&searchfor=all
[00:54] <UndiFineD> MTecknology, send my request just now
[00:55] <UndiFineD> https://launchpad.net/~k.dejong
[00:55] <MTecknology> approved - next time read the message you're sent
[00:56] <rww> ironically, that silly LP search page doesn't find MTecknology either.
[00:56] <UndiFineD> well, if I reply it is not read
[00:56] <rww> oh, I lie, I can't spell
[00:57] <MTecknology> 29 requests to join this week..
[00:59] <UndiFineD> well people are at least interested :)
[01:01] <rww> MTecknology: 90% of which aren't valid requests, I'd guess?
[01:01] <MTecknology> rww: pretty much
[01:01] <rww> yeah, concept of an "Ubuntu Member" isn't immediately obvious to a lot of people
[01:03]  * Cheri703 might be trying to become an ubuntu member soon
[01:07] <MTecknology> rww: well.... 4 potentially legit....
[01:08] <MTecknology> better than normal odds
[20:44] <MichealH> Is the Lubuntu Channels Official?
[20:44] <MichealH> As Lubuntu is now Official
[20:46] <persia> MichealH: How do you mean "Official"?  Do you mean "have all the i's been dotted and t's crossed" or do you mean "These are considered important channels and part of the Ubuntu channel set"?
[20:47] <MichealH> I mean is the #lubuntu channel Core?
[20:47] <MichealH> BRB
[20:47] <MichealH> Switching PC's
[20:50] <persia> I think "Core" and "Official" are very different, and should be kept that way.  There's lots of "Official" channels that aren't "Core".
[20:50] <rww> MichealH: Unless something changed recently and I haven't heard about it and the documentation hasn't been updated, it's not managed by the IRC team, so it's not a core channel.
[20:50] <rww> https://wiki.ubuntu.com/IRC/IrcTeam/Scope lists the ones that are.
[20:51] <rww> Lubuntu's council and the IRC council would presumably have to discuss it if they wanted #lubuntu to be managed by the IRC team.
[20:53] <persia> Well, no, as Lubuntu doesn't have a "council".
[20:54] <rww> Fun. Well whoever's responsible for important decisions there I guess ;P
[20:54] <MichealH> The founder of #lubuntu? :P
[20:54] <persia> Anyway, that's just details: for folk not part of Lubuntu and not on the IRCC, it's best to consider the Lubuntu channels the same as any other flavour at this point.
[20:55] <persia> (and I recommend not poking this too much if you don't fit into those categories unless there is some issue happening that needs it poked, which IRCC can probably help sort)
[20:55] <rww> persia: I was replying to MichealH asking whether the channels are core channels. The word "official" is thrown around enough that I don't bother trying to define it :P
[20:56] <persia> rww, "Core" has been messy and contentious in it's time as well :)
[20:56] <rww> persia: and now we have a nice shiny list and it hasn't been an issue in a while, afaik ;P
[20:57] <rww> and from the IRC op perspective, it's an important distinction, as core channel implies the ops there have bantracker access for the whole namespace, idle in -ops, etc., etc.
[20:57] <LjL> i don't recommend recommending against the public not commenting over matters ;(
[20:57] <persia> rww, Yeah, we said that last time we had a list :)  Note that I'm happy the issue is quiet, and I hope it's a long while before we discuss it again: I just believe that any fixed lists are inherently unscalable, so therefore need continued discussion as the project changes.
[20:58] <MichealH> As a op of #lubuntu, I may find the bantracker and all of ubottu's features to be useful to the channel
[20:58] <persia> LjL, Comments are fine.  Given the scrambling to sort Lubuntu stuff lately, I suspect the folks that need to do things are busy enough that more folk asking them to do more things won't help much yet.
[20:58] <rww> MichealH: considering that #lubuntu has 1 ban set, I doubt this.
[20:59] <rww> but anyway, it's not my decision, so *shrug*
[20:59] <MichealH> rww: But as it grows, we may need it
[21:00] <MichealH> persia: I did not ask them to do it, I just asked if it was core or not
[21:01] <persia> Oh, I know :)
[21:01] <MichealH> Although I think it would benifit us later on :)
[21:02] <rww> incidentally, the ban's set against a dynamic hostname that's no longer valid anyway, so is removable ;)
[21:05] <MichealH> heh
[21:05] <LjL> rww is annoying don't mind him
[21:06] <LjL> he wants banlists to be clean because a clean banlist is a happier banlist or something
[21:06] <MichealH> Reminds me of my school - "A tidy tie is a happy tie"
[21:06] <MichealH> lulz
[21:07] <rww> LjL: well, you know, it's one less banlist slot to hunt down when #lubuntu grows and the list gets full.
[21:10] <LjL> *censors himself*
[21:18] <MichealH> rww: BTW, How did you know that was dynamic?
[21:18] <rww> MichealH: because I recognize the user from #ubuntu, and they've switched hostnames since that one.
[22:01] <clandestino> ciao a tutti, sono di nuovo qui....non è cambiato nulla
[22:02] <clandestino> mi è venuta però un'idea...tempo fa avevo provato ad installare kde come alternativa a gnome, quindi credo di avere un ibrido....
[22:04] <LjL> clandestino: mi sa che stai cercando #ubuntu-it, questo è #ubuntu-irc


[01:52] <sirix> good evening
[01:52] <CherryPuffs> Hey sirix
[01:53] <sirix> CherryPuffs: hey what's up
[01:54] <CherryPuffs> Just chilling :)
[01:54] <sirix> ok
[20:31] <studio-user559> UbuntuStudio 1604. Cant config 1st monitor left of 2nd ! How it make ?
[23:47] <Nvidia-1050> I was wondering if Studio Ubuntu has good suport for the Nvidia 1050 ti GTX
[23:47] <Nvidia-1050> ?


[00:08] <LaserJock> bdoin: subscribed, thanks
[00:09] <bdoin> LaserJock: for the translations issue, you thing something can be done for gutsy ?
[00:13] <bazz> Silly qusetion...where would I look for ldm to play with settings? Are there any flat files for it?
[00:16] <johnny_> it's lts.conf
[00:16] <johnny_> those are the settings for it
[00:17] <bazz> darn....
[00:17] <johnny_> to get what you want, you'll prolly have to write some code
[00:17] <johnny_> or get somebody else to write it for you
[00:18] <bazz> I wish I could write code.....
[00:18] <bazz> think there would be anyone out there interested inn doing it
[00:18] <johnny_> nobody i know
[00:18] <johnny_> except for pay obviously
[00:19] <bazz> yeah...
[00:19] <johnny_> you should write out a description of exactly what you need, your post needs to be elaborated on
[00:19] <bazz> then post to the group?
[00:20] <johnny_> yes
[00:21] <bazz> cool...I will give that a go
[00:22] <bazz> I have a few things I'm gonna try first...see what happens
[00:29] <LaserJock> bdoin: I really don't know, we have a fairly high barrier on what can go into the -updates repositories
[00:30] <LaserJock> bdoin: we can't have hundreds and hundreds of new packages going in
[00:30] <bdoin> but gcompris translations are in a separate common translation package no ?
[00:31] <LaserJock> bdoin: on the other hand, if I can get a new translation put into the lang packs, which are updated something like monthly
[00:31] <LaserJock> without messing around with the gcompris package itself
[00:31] <LaserJock> I think we'd have a shot
[00:31] <LaserJock> I just don't have enough experience with translations to know exactly how difficult it'd be
[00:31] <LaserJock> but I can look into it and ask around
[00:32] <LaserJock> I'm still not 100% positive on what the problem is
[00:32] <LaserJock> are we just carrying old translations? or are they incomplete translations of the new versions
[00:32] <bdoin> well we already have very good translations that we ship with each release. we are very formal on string freeze and it's sad it ends up so messy on Ubuntu
[00:34] <bdoin> in many languages, GCompris is just not usable in schools
[00:40] <LaserJock> bdoin: because of Ubuntu messing up the translations?
[00:41] <bdoin> yes
[00:43] <LaserJock> well that's not cool
[00:43] <LaserJock> we certianly shouldn't be making things worse
[00:43] <bdoin> teachers in primary education does rarely speak english, at least in france. currently, when you launch GCompris in french, you have to dig around the menus to find something translated.
[00:46] <bdoin> it's just annoying when translation are broken on some application but for the GCompris target and shool audience of Edubuntu, it's a show stopper
[00:47]  * bdoin have to sleep, bye
[00:48] <LaserJock> bdoin: well, I'm very sorry and I'll do my best to get this all cleaned up
[00:49] <bdoin> thanks a lot, be assured that it's really important for non english speaker and it's a must for the credibility of edubuntu in the educational market
[00:50] <LaserJock> I agree
[00:50] <bdoin> bye
[01:11] <johnny_> anybody have a problem with firefox not completely closing on exit with ltsp?
[03:49] <johny> hi there
[03:49] <johny> I need help mounting an ntfs drive please
[03:51] <scrapbunny> is anyone having issues with 7.10 running slow on thin clients
[03:52] <johny> I'm having issues mounting an ntfs drive
[03:53] <scrapbunny> are you running edubuntu stand alone or as thin client?
[03:54] <johny> I think it's the stand alone
[03:54] <johny> I have tried a few faq's and websites but it still doesn't work
[03:54] <johny> other than that I'm having good success with it and and happy
[03:55] <johny> als I'm still a newbie
[03:55] <johny> alas even
[03:55] <scrapbunny> is this with 7.10? I'm a newbie too but will try to help :)
[03:55] <johnny_> you have to use ntfs-3g
[03:55] <johnny_> if you want read/write that is
[03:56] <johny> it says that that driver is installed
[03:56] <johny> yes it is 7.10
[03:57] <johny> I get an error msg
[03:57] <scrapbunny> what is the message?
[03:57] <johny> something about it wasn't dismounted properly
[03:57] <johny> I treid what it said
[03:57] <johny> and it didn't work
[03:59] <scrapbunny> so have you ever been able to mount the drive?
[03:59] <johny> no I havn't
[03:59] <johny> not since the instal
[04:00] <scrapbunny> do you have more than one user set up on this computer?
[04:01] <johny> just me
[04:01] <johny> when I try to acces it it says that I don't have permission tough
[04:01] <johny> though even
[04:02] <johny> used to say that
[04:02] <johny> now it says unclean shut down
[04:02] <johny> failed to mount
[04:02] <johny> cannont mount volume
[04:02] <johny> whem I click details it says
[04:03] <johny> unclean shut down
[04:04] <scrapbunny> when you click on system, Administration, then users and groups what does it show?
[04:04] <scrapbunny> should be root and then your account
[04:04] <johny> yes it does show that
[04:05] <scrapbunny> can you click on your account and then Properties?
[04:06] <johny> yes that works
[04:07] <scrapbunny> then click the user priviledges and make sure administer system is checked
[04:07] <johny> I checked it now
[04:07] <scrapbunny> it wasn't checked?
[04:08] <johny> no it wasn't
[04:09] <johny> should I restart
[04:09] <scrapbunny> now that is is checked i would do a restart and see if you can now mount the drive. from some of the other messages it sound like the computer was not turned off correctly at some point
[04:10] <johny> so how do I fix that
[04:10] <scrapbunny> how are you turning off the computer?
[04:10] <johny> oh maybe i can try what it says again
[04:11] <johny> I generally use the shutdown icon
[04:11] <johny> unless something is frozen completely and I can't
[04:12] <johny> I'll try a resart now though and come back it may have helped alot
[04:12] <scrapbunny> i know that there are issues with the shutdown and especially hibernate and sleep mode so make sure you have run an update so you have any fixes
[04:16] <johny> I'm back
[04:16] <johny> I still get the same error message about unclean shutdown
[04:17] <johny> mount is denied because ntfs is marked to be in use
[04:19] <scrapbunny> have you opened terminal and typed sudo reboot ?
[04:19] <johny> nope i havn't
[04:20] <johny> I just got it to mount though just now
[04:20] <johny> I can access my files yay
[04:21] <scrapbunny> that is what is suggested on the forums. if you get the unclean shutdown again I would try that
[04:21] <scrapbunny> :-D
[04:24] <johny> I had to force a mount from console
[04:24] <johny> that was of course after your help alowing my user administative privlages
[04:24] <johny> that fised the first problem
[04:24] <johny> fixed
[04:24] <johny> then I had to use sudo to force a mount on the drive
[04:24] <johny> now I have my files
[04:24] <johny> thank you
[04:24] <johny> your help is greatly appreciated
[04:24] <johny> I have more questions for another day
[04:24] <johny> but that will keep me happy till tomorrow
[04:24] <johny> :)
[04:25] <johny> I wish I could help you on your question
[04:25] <johny> but I'm more of a newb than you
[04:25] <johny> lol
[04:27] <scrapbunny> no prob, i am trying to get 32 computers in my school lab going as thin clients. i have 14 set up and they are running a lot slower then they should
[06:26] <Artemko> Tell please, whether it is possible to make, what OpenOffice it would be started as local_apps? And how it to make? I wish to lower loading on a server. And as in ltsp 5 to specify the coding, and that cyrillics on local device is displayed incorrectly
[06:28] <Artemko> And still there is an appendix which everyone start in Wine, whether there is a sense to make administrative installation that all used one structure, whether will lower it loading?
[14:45] <sbalneav> Morning all
[14:51] <RichEd> hi sbalneav
[14:51] <sbalneav> Morning RichEd
[14:52] <ogra> heya scottie
[14:53] <Petaris_Aki> Morning sbalneav
[14:54] <sbalneav> Morning ogra
[14:54] <sbalneav> see my rantings in #ltsp?
[14:54] <ogra> nope
[14:54] <ogra> i'm not in there today
[14:55] <sbalneav> looks like we might have a nice alternative to getltscfg, eliminating the last binary
[14:55] <sbalneav> from the ltsp core package.
[14:55] <ogra> Q-Funk got a bit rude at me so i decided toi not do #ltsp for today
[14:55] <ogra> yay
[14:55] <ogra> thats awesome !!
[14:55] <sbalneav> Hopefully you still love ME though, right?
[14:56] <sbalneav> :)
[14:56] <ogra> indeed i do
[14:56] <ogra> just wanted to stop the argument with matin
[14:56]  * sbalneav hugs ogra
[14:57] <ogra> blaming  me of spreading "nonsense" about amd
[14:57]  * ogra hugs sbalneav
[14:57] <sbalneav> What nonsense?
[14:58] <ogra> he says i would have gone around telling people a backport is the only possible solution ... (which is nonsense indeed)
[14:58] <sbalneav> I don't remember you saying anything like that.
[14:58] <ogra> all i asked was if someone had tried to backport the older working version ... whiout saying anything about idf it fixes stuiff or not
[14:59] <ogra> anyway, he was pretty wound up today, so i decided to stay out of the line of fire :) since my day was good so far and i didnt want to get wound up as well
[15:00] <ogra> :)
[15:01] <sbalneav> heh
[15:01]  * ogra has a new SDSL line sitting in the basement ... but still waiting to be able to use it ... and i'm so eager top see the upload rates ...
[15:01] <sbalneav> A tactical retreat is a perfectly valid strategy
[15:01] <ogra> but indeed they f*cked up my login data ...
[15:01] <sbalneav> ooh
[15:01] <ogra> so i'm waiting for them to fix it which apparently wont happen before apm today
[15:02] <ogra> *8pm
[15:02] <ogra> (twiddling thumbs for 4h more )
[15:02] <sbalneav> yeah, we have a bunch of lawyers here who got blackberrys, so I've been dealing with a boatload of silly problems the last couple of days.
[15:04] <ogra> RichEd, btw http://lwn.net/Articles/198333/
[15:04] <ogra> now getting the kernel team to accept it :)
[15:05] <RichEd> cool is it a working patch ?
[15:05] <RichEd> just needs approval ?
[15:05] <ogra> no idea
[15:05] <ogra> i just found it ...
[15:06] <ogra> but greg KH (one of the upstream kernel devs) didnt objetc it
[15:06] <ogra> so it seems to be fine from a general POV ...
[15:06] <ogra> but it was written for 2.6.18, we're at 2.6.24 with hardy
[15:06] <ogra> so might need modifications
[15:07] <ogra> but it means that we dont have to write it on our own, there is code that just needs to be made running on our current version
[15:08] <ogra> i'm waiting for BenC to get up to corner him and amitk and get some more info from the kernel team side
[15:08] <sbalneav> ogra: great news!
[15:09] <sbalneav> "utterly impossible" => "50 lines of code" => someone's already done the work
[15:09] <sbalneav> nice
[15:09] <sbalneav> \o/
[15:20] <RichEd> yo mr sladen ... fancy seeing you in here :)
[15:52] <o00w> can someone help with installing a Novell client to my 7.04 install...I get an error "install: missing destination file operand after "
[16:11] <sbalneav> o00w: Novell client what?
[16:12] <o00w> sbalneav: Suse Novell Client 2.0
[16:12] <sbalneav> I have no idea what that is :)
[16:13] <o00w> used for authenticating to network servers and handles script to automatically map drives for particular user accounts
[16:13] <o00w> also known as NetWare
[16:17] <o00w> anyway do you know what this error means...install: missing destination file operand after
[16:17] <o00w> this was the command I gave from terminal: sudo install ./ncl_install
[16:17] <sbalneav> Yeah, the install isn't finding something it needs.
[16:18] <sbalneav> is this client certified to work on Ubuntu, or only SuSE linux?
[16:18]  * ogra would guess thats a script on its own
[16:18] <ogra> i.e. did you try sudo ./ncl_install
[16:18] <o00w> ./ncl_install is not a bash command
[16:19] <ogra> ok, then its probably not a script
[16:19] <o00w> install: missing destination file operand after `./ncl_install'
[16:19] <o00w> there are two scripts though
[16:20] <o00w> autorun.sh and ...ok nm just one script
[16:20] <o00w> nm ncl_install is a script
[16:21] <o00w> but it doesn't have a sh file extension
[16:21] <sbalneav> Doesn't have to
[16:22] <sbalneav> perfectly acceptable to have a script without a .sh extention.
[16:22] <o00w> so the header #! /bin/bash is what defines it as a script?
[16:23] <sbalneav> Yup, that's called a shebang
[16:24] <o00w> wow and I thought you were joking
[16:37] <sbalneav> o00w: Know why "!" is called a "bang" in computer circles?
[16:38] <sbalneav> Because on the old IBM card punches, the "!" would punch out a whole row on the card.
[16:38] <sbalneav> This made the maximum number of the little fingers that made the punches move, making the loudest noise.
[16:39] <sbalneav> Therefore, "!" became known as a "bang"
[16:39] <sbalneav> It's also called a "dammit"
[16:39] <sbalneav> from the VI command :q!
[16:39] <o00w> interesting that wasn't in the wikipedia article or atleast I missed it
[16:39] <sbalneav> To quit without saving, usually after you've mucked up your edit.
[16:40] <sbalneav> read: "Quit, dammit!"
[16:40] <sbalneav> :)
[16:41] <sbalneav> http://www.ss64.com/bashsyntax/pronounce.html
[16:42] <bddebian> Heya
[17:41] <Petaris_Aki> Anyone care to help me debug a botched LDAP *client configuration on my LTSP server?
[17:41] <Petaris_Aki> I followed a how-to
[17:41] <Petaris_Aki> so I know exactly what I did
[17:42] <Petaris_Aki> I followed this:  http://ubuntuforums.org/showthread.php?p=3723403
[19:15] <moquist_> Aaaarg! I my boss' boss just installed Edubuntu Gutsy and our boot times went UP. 8-o
[19:15] <moquist_> (according to him)
[19:15] <moquist_> I told him about LDM_DIRECTX so hopefully that will make those TCs sing once they're booted, anyway.
[19:16] <ogra1> unlikely ... LDM_DIRECTX doesnt help with booting
[19:18] <TelnetManta> ogra1: Could you test a site for me real quick?
[19:19] <TelnetManta> just need to make sure its responding from outside of my firewall
[19:21] <TelnetManta> nevermind
[19:24] <ogra1> just post the url
[19:24] <ogra1> there are 45 ppl in this channel, even if i wouldnt respond someone might be bored and take a look ;)
[19:27] <stgraber> ogra1: About iTalc, I'll just do a small shell script starting "ica" in a while loop, it's still possible for users to kill it but not that easy (as it won't show up with the iTalc icon in the gnome process list)
[19:27] <ogra1> yeah, sounds ok for a start
[19:28] <stgraber> ogra1: solutions like using sudo would introduce way to much changes (we can't really change the sudoers) and I don't like running it as root (that'd be a bad point for its main inclusion too :))
[19:28] <ogra1> yeah
[19:35] <TelnetManta> http://support.anderson5.net
[19:36] <TelnetManta> can anyone get to that url? Or even ping it?
[19:38] <stgraber> TelnetManta: I can
[19:39] <TelnetManta> thank you
[19:58] <gamed|ph> hi
[19:59] <gamed|ph> anybody knows how to change the ip of the ltsp-server the ltsp-client will connect to? My dhcp/tftpd runs on a different maschine then my ltsp
[20:05] <ogra__> you can use SERVER in lts.conf
[20:13] <gamed|ph> ogra__ i've already tried that
[20:13] <gamed|ph> but doesn't work :-(
[20:14] <ogra__> where does it break exactly ?
[20:15] <gamed|ph> i've to create a lts.conf in the same directory my kernels are located
[20:15] <gamed|ph> in tftproot
[20:16] <gamed|ph> and write something like [default] \n SERVER = <IP_ADDRESS>
[20:18] <gamed|ph> I get initramfs shell of busybox
[20:18] <gamed|ph> and on Alt + F1 the mounts fail because "invalid argument"
[20:20] <moquist> ogra__: I know. But it may be enough to speed up the TCs after booting...that may tide him over.
[20:21] <moquist> gamed|ph: are you past setting next-server in dhcpd.conf?
[20:21] <ogra__> gamed|ph, aha ... thats gutsy then, right ?
[20:21] <gamed|ph> next-server is the ip of my tftpd, i want to change the ip for my ltsp because its not equal to the tftp/dhcp-ip
[20:22] <ogra__> if you are in busybox that means kernel and initramfs were loaded fine, so up to tftp everything is fine
[20:22]  * moquist nods
[20:22] <gamed|ph> ogra__: yes, of course
[20:22] <ogra__> it likely doesnt know where to get the rootfs from
[20:22] <gamed|ph> yeah, i don't know how to set the nfs-ip
[20:23] <ogra__> set nbdroot="<server ip>:<image serving port from inetd.conf>"
[20:23] <ogra__> in your pxelinux.cfg/default file
[20:23] <gamed|ph> at apped?
[20:23] <gamed|ph> *append
[20:23] <ogra__> right
[20:23] <ogra__> just after quiet and splash
[20:27] <moquist> ogra__: I did tell him (boss' boss) that I haven't even tested Gutsy with any of our TCs yet, and that we don't have it in production, etc. *shakes head*
[20:28] <ogra__> oh man
[20:33] <gamed|ph> ok it works - thanks! But now the authentification seems to be a problem :-/
[20:33] <gamed|ph> verifying password takes a very long time
[20:35] <ogra__> thats a bit tricky, you need the sshkey in your image
[20:36] <gamed|ph> ahh, in the /opt/ltsp/images/i386.img?
[20:36] <ogra__> ltsp-update-sshkeys does that
[20:37] <gamed|ph> "this workstation isn't authorized..." mh,ok
[20:37] <ogra__> but it will only work if the image server is the login server as well
[20:37] <ogra__> is that the case ?
[20:39] <gamed|ph> yes
[20:41] <gamed|ph> mh, this workstatio isn't authorized to cv
[20:41] <gamed|ph> onnect to the server
[20:41] <ogra__> run: sudo ltsp-update-sshkeys ; sudo ltsp-update-image .... get a coffee ... rebot the client if its done with the image
[20:42] <ogra__> that will fix the message
[20:42] <ogra__> i assume you changed the IP of the machine after you ran ltsp-build-client
[20:42] <ogra__> (its usually run on install in edubuntu fwiw) :)
[20:47] <gamed|ph> cool it works!
[20:47] <gamed|ph> thanks :-)
[20:48] <ogra__> gern geschehn :)
[20:48] <gamed|ph> ah du kannst auch deutsch
[20:48] <ogra__> jup
[20:48] <gamed|ph> da würg ich mir hier einen auf englisch ab ;-)
[20:49] <ogra__> bildet doch ;)
[20:49] <gamed|ph> haste zufällig ne gute idee wie ich das system nun noch an ne aktice directory anbinde?
[20:49] <ogra__> EDUbuntu :)
[20:50] <gamed|ph> ;-)
[20:50] <gamed|ph> *active
[20:51] <ogra__> http://ubuntuforums.org/showthread.php?t=280702 ?
[20:51] <ogra__> is fuer dapper ...
[20:54] <gamed|ph> kriegt man das nicht einfacher hin?
[20:54] <ogra__> nope
[20:55] <gamed|ph> k, thx
[21:35] <ace_suares> hi all, hi ogra__ !
[21:36] <ace_suares> for some reason, i installed from ubuntu gutsy alternate cd, not from edubuntu gutsy cd
[21:36] <ace_suares> what's the quick way to apt-get all the edubuntu stuff after the install si done.
[21:36] <ace_suares> It's not in the faq... can I put it in the faq after someone explained it to me ?
[21:43] <scrapbunny> edubuntu-desktop will get you most everything. i think you still need to add the games though
[21:47] <LaserJock> ace_suares: are you wanting LTSP or just educational apps?
[21:48] <ace_suares> Hi LaserJock!
[21:49] <ace_suares> LTSP, especially.
[21:49] <ace_suares> with edubuntu-desktop, is does it do ltsp-build-client and things ? And configure dhcp and all that ?
[21:51] <LaserJock> no
[21:51] <LaserJock> I don't think we have anything that does everything that the Edubuntu disk does
[21:51] <LaserJock> but you can do most of it at least
[21:51] <LaserJock> ogra__ would know specifically
[21:51] <ace_suares> see, it would be nice if there was some way to get the exact result from an ubuntu-cd + some apt-get magic, as an install form an edubuntu-cd
[21:52] <ace_suares> like a button on the desktop 'add kubuntu' or 'add edubuntu'
[21:52] <LaserJock> you want to install ltsp-server-standalone
[21:52] <ace_suares> or lacking that, a faq...
[21:52] <ace_suares> Is there a walktrough somewhere ?
[21:52] <LaserJock> ace_suares: I believe it's on a wiki page
[21:53] <ace_suares> yeah i looked troughthe edubuintu wiki but didn't quickly find what I needed...
[21:53] <ace_suares> I mean, i've done this before (apt-get ltsp-server-standalone and such) but I always was missing somethin
[21:53] <ace_suares> here or there...
[21:53] <ace_suares> or am i being dimwitted ?
[21:53] <LaserJock> this might work https://help.ubuntu.com/community/UbuntuLTSP/LTSPQuickInstall
[21:55] <ace_suares> that page looks good... thanx !
[22:21] <ace_suares> ping ogra__
[22:22] <ace_suares> What's a good way to use alternative sources.list for ltsp-build-client ?
[22:22] <ace_suares> I have a local repository which saves me tons of time on every install and update of ubuntu, but ltsp-build-client uses
[22:22] <ace_suares> remote repos.
[22:23] <ace_suares> I think the name of the repos are in deifferent places, the security repo is in another place then the main ??
[22:24] <ace_suares> oh... you build ins ome options in 010-manage-mirrors ? let me see ...
[22:25] <ace_suares> --copy-sourceslist ? that would be cool !
[22:28] <ace_suares> nah... it still goes to security.ubuntu.com !
[22:38] <ace_suares> tried --early-mirror and --security-mirror, but it's awfully slow, so I think it's still going to the internet to retrieve packages
[22:39] <johnny> sbalneav, i tried the suggestion you had, still no dice, ssh -X user@ltspserver  from sh on the thinclients works fine
[22:40] <johnny> or rather.. i guess there was dice
[22:40] <johnny> i'm just at a loss of what to try next
[22:49] <ace_suares> I have a local mirror like this : http://tupac/archive.ubuntu.com/ubuntu and I have dapper, feisty and gutsy there
[22:50] <ace_suares> the first part of the update goes fine, then suddenly it gives errors like 'http://tupac Releases.gz: ignored, can't find ...
[22:50] <ace_suares> In this case, it shouldn't strip the archive.ubuntu.com part...
[22:51] <ace_suares> i ran with ltsp-build-client --mirror http://tupac/archive.ubuntu.com/ubuntu
[22:51] <ace_suares> I don't get it....!
[23:05] <ace_suares> ah... tupac is not in the chrooted /etc/hosts !
[23:14] <ace_suares> this finally worked, in a couple of minutes ltsp-build-client completed !
[23:15] <ace_suares> ltsp-build-client --mirror http://<IP_ADDRESS>/archive.ubuntu.com/ubuntu --security-mirror http://<IP_ADDRESS>/archive.ubuntu.com/
[23:15] <ace_suares> note that if you put /ubuntu after the security mirror, it doesn't work!


[00:35] <zmoylan-pi> oh no, not again! https://twitter.com/angryearthling/status/975157299999379457/photo/1
[00:38] <daftykins> :D
[00:46] <zmoylan-pi> At least no petunias were harmed in this snow...
[09:15] <brobostigon> morning boys and girls.
[09:28] <zmoylan-pi> o/
[09:30] <zmoylan-pi> snow on the ground... that changes usual plans for a nice long sunday walk...
[09:31] <brobostigon> o/
[09:31] <brobostigon> same as here too, :(
[09:32] <SuperEngineer> sudo build snow_man
[09:33] <SuperEngineer> sudo cmake snow_angel
[09:34] <zleap> :)
[09:50] <brobostigon> :)
[11:50] <TidalFlow> Virgin angryies https://www.youtube.com/watch?v=Byz94fkwf6U
[13:10] <SuperEngineer> Quiet today. I'm guessing they're all out sunbathing.
[13:13] <penguin42> oh yes, lovely weather for sunbathing
[13:15] <SuperEngineer> :)
[13:16]  * SuperEngineer looks on bright side: if it's snowing, it isn't raining!
[13:17] <penguin42> actually it's not snowing here now, we've just got a layer of it and it's still 1c
[13:21] <SuperEngineer> typical... not quite cold enough to make your own ice, not quite warm enough to put the mankini on.


[00:02] <Riddell> phoenix_firebrd: what's from sourceforge?
[00:02] <Riddell> phoenix_firebrd: I'm about to go to bed but can verify things in the morning
[00:02] <phoenix_firebrd> Riddell: sure, good night
[00:05] <yofel> phoenix_firebrd: kolab is at http://git.kolab.org/libkolab - but as both kolab and kolabxml have watch files you can just use uscan/uupdate to fetch the new versions
[00:06] <phoenix_firebrd> yofel: so is this page outdated http://qa.ubuntuwire.com/uehs/no_updated.html
[00:07] <phoenix_firebrd> yofel: whats the time now? here it us 5 37 am
[00:10] <yofel_> bah, great time for a connection reset
[00:10] <yofel> phoenix_firebrd: kolab is at http://git.kolab.org/libkolab - but as both kolab and kolabxml have watch files you can just use uscan/uupdate to fetch the new versions
[00:10] <yofel> (in case you didn't get it)
[00:11] <phoenix_firebrd> yofel: i am going through it right now
[00:11] <phoenix_firebrd> yofel: Do you have some time to guide me now
[00:11] <yofel> a few minutes, then I'm off to bed too
[00:13] <phoenix_firebrd> yofel: I am trying to compile freeimage from here freeimage
[00:13] <phoenix_firebrd> oops
[00:13] <phoenix_firebrd> yofel: http://qa.ubuntuwire.com/uehs/no_updated.html
[00:14] <yofel> hm, we usually just sync that from debian
[00:14] <phoenix_firebrd> yofel: can you walkthrough for compiling a single package for the first time?
[00:15] <phoenix_firebrd> yofel: if its too late, i can wait till tomorrow
[00:17] <yofel> will have to wait then. But maybe someone else can answer a question or two
[00:18] <allee> phoenix_firebrd: I cd to the package source and do debuild -us -uc
[00:18] <phoenix_firebrd> allee: we dont need bazaar?
[00:18] <yofel> phoenix_firebrd: do you need freeimage for something? Otherwise kolab would be more helpful currently (library packages are a bit tricky in general for beginners though)
[00:18] <allee> phoenix_firebrd: ah, one step back ;-)
[00:19] <phoenix_firebrd> yofel: ok, i will start with kolab
[00:19] <allee> phoenix_firebrd: rename the tar file so it ends  <name>_<ver>.orig.tar.gz
[00:19] <allee> or .bz
[00:19] <phoenix_firebrd> allee: wait i will clone first
[00:20] <yofel> that, or let uscan and uudate do the initial updating
[00:20] <yofel> *uupdate
[00:20] <phoenix_firebrd> yofel: ok
[00:21] <yofel> hm, do we even have  branches for kolab...
[00:21] <allee> I doubt
[00:21] <yofel> nope
[00:22] <allee> KDAP dudes did pkging for debian.  So there should be something already ...
[00:22] <phoenix_firebrd> whats the syntax for uupdate
[00:22] <yofel> we have kolab 0.2.1, can be updated to 0.4.1
[00:23] <yofel> but I don't see anything in debian so far
[00:23] <yofel> phoenix_firebrd: sec
[00:24] <yofel> phoenix_firebrd: if you've unpackaged the old package and ran uscan, then "uupdate ../libkolab_0.4.1.orig.tar.gz"
[00:25] <phoenix_firebrd> yofel: so initially i have to git clone right?
[00:25] <yofel> no, you don't need git at all
[00:26] <yofel> we package tarballs if available, not git snapshots. (even if for kolab the tarball is a snapshot of the git tag)
[00:26] <phoenix_firebrd> yofel: so now i have to download this libkolab-0.4.1.tar.gz  ?
[00:26] <yofel> phoenix_firebrd: uscan does that for you
[00:26] <yofel> using the watch file in the package
[00:27] <yofel> phoenix_firebrd: but first things first: start with 'pull-lp-source libkolab raring'
[00:27] <yofel> go into the source and run uscan there
[00:27] <allee> yofel,phoenix_firebrd: here's the mailing list aktivity of the debian kolag pkging: http://lists.alioth.debian.org/pipermail/pkg-kolab-devel/
[00:28] <phoenix_firebrd> yofel: sudo apt-get install ubuntu-dev-tools
[00:28] <phoenix_firebrd> yofel: installing
[00:28] <yofel> phoenix_firebrd: yep, you'll need those frequently
[00:29] <phoenix_firebrd> allee: i will join the mailing list
[00:29] <yofel> phoenix_firebrd: add https://code.launchpad.net/~bulldog98/+archive/kubuntu-dev-tools to the mix, you won't need them immediatly, but they'll be handy
[00:30] <phoenix_firebrd> yofel: mix?
[00:30] <yofel> just add the ppa to your sources
[00:30] <phoenix_firebrd> yofel: oh :D
[00:32] <phoenix_firebrd> yofel: source pulled
[00:33] <yofel> go into the unpacked source and run uscan
[00:33] <phoenix_firebrd> yofel: ran uscan
[00:33] <allee> kolab debian pkg summary: http://wiki.debian.org/Teams/pkg-kolab
[00:33] <yofel> good, now run uupdate on the tarball
[00:36] <phoenix_firebrd> yofel: i have 2 new items one an new version traball and  a sym link
[00:36] <yofel> use the tar with orig in its name
[00:38] <phoenix_firebrd> yofel: http://imagebin.org/243876
[00:39] <yofel> phoenix_firebrd: yeah, now run uupdate
[00:41] <phoenix_firebrd> yofel: "uupdate libkolab_0.2.1.orig.tar.gz"
[00:41] <yofel> no, not 0.2.1, 0.4.1
[00:41] <phoenix_firebrd> yofel: "uupdate: cannot find debian/changelog.Are you in the top directory of the source tree?
[00:41] <phoenix_firebrd> "
[00:41] <yofel> you need to be inside libkolab-0.2.1
[00:41] <phoenix_firebrd> yofel: ok
[00:41] <yofel> there run
[00:41] <yofel> uupdate ../libkolab_0.4.1.orig.tar.gz
[00:42] <phoenix_firebrd> yofel: done
[00:43] <phoenix_firebrd> yofel: i have the new source
[00:44] <phoenix_firebrd> yofel: the rest is the packaging procedure
[00:44] <yofel> yeah, now it's the standard way of building and fixing
[00:44] <phoenix_firebrd> yofel: For maintainer's name and email , should i put your's?
[00:45] <yofel> no, those are supposed to be set to what it's set now
[00:45] <yofel> for now just try to build the package
[00:45] <yofel> i.e. debuild -S and throw it into pbuilder
[00:45] <phoenix_firebrd> yofel: ok
[00:46] <yofel> from a quick build here: a few tests fail, a few new files, and new symbols
[00:47] <phoenix_firebrd> yofel: ok
[00:49] <phoenix_firebrd> yofel: Are you waiting for me?
[00:49] <yofel> phoenix_firebrd: not really, where are you at?
[00:50] <phoenix_firebrd> yofel: creating gpg key
[00:51] <phoenix_firebrd> yofel: gpg: skipped "Prasad Murthy <phoenix@matrix>": secret key not available
[00:51] <phoenix_firebrd> yofel: the email is wrong
[00:51] <yofel> is $DEBEMAIL set?
[00:51] <phoenix_firebrd> yofel: no
[00:52] <yofel> best put that in your .bashrc:
[00:52] <yofel> export DEBFULLNAME='Philip Muškovac'
[00:52] <yofel> export<EMAIL_ADDRESS>[00:52] <yofel> with your data
[00:53] <phoenix_firebrd> yofel: if i put that there wont be a problem in using key
[00:54] <yofel> dch will use that to fill in the name in the changelog, which debsign then uses to search for the ky
[00:54] <yofel> *key
[00:55] <phoenix_firebrd> yofel: ok
[00:57] <phoenix_firebrd> yofel: so after setting that i have to download the source again?
[00:58] <yofel> ok, I need to be off to bed, a few hints:
[00:58] <yofel> if you don't have a pbuilder chroot yet, look at pbuilder-dist which should be easy to understand
[00:58] <yofel> if you can't fix the tests (I'm too tried to make sense of the errors right now) disabel them by putting 'override_dh_auto_test:' a the end of debian/rules
[00:58] <yofel> if you don't know what a symbol diff (which you'll see after fixing the install file), look at http://pkg-kde.alioth.debian.org/symbolfiles.html (and no, you don't need to immediately understand that)
[00:58] <yofel> phoenix_firebrd: no, just fix your name in debian/changelog
[00:59] <phoenix_firebrd> yofel: ok good night, see you later
[00:59] <yofel> feel free to throw questions at the channel anyway, someone might answer while you stick around
[01:00] <yofel> good night
[02:25] <EagleScreen> why apturl-kde depends on software-properties-kde? does it really need it?
[03:10] <claydoh> SteveRiley_: ping ping ping!
[06:39] <shadeslayer> wow
[06:39] <shadeslayer> php closely resembles C++
[06:40] <Tm_T> shadeslayer: pardon?
[06:40] <shadeslayer> Tm_T: my ISP uses a web based login page, and I found this : https://github.com/vercingetorix/Reliance-Broadband/blob/master/index.php
[06:40] <shadeslayer> which is a php script to login from the command line
[06:40] <shadeslayer> looks alot like C++
[06:41] <shadeslayer> it's very OOP oriented
[06:42] <tsimpson> it's more like C with classes
[06:42] <shadeslayer> heh :)
[10:16] <BluesKaj> Hey all
[10:17] <shadeslayer> hi BluesKaj
[10:17] <BluesKaj> hi shadeslayer
[10:27] <jdrab> hi guys, it looks like this bug is present in kubuntu 13.04 https://bugreports.qt-project.org/browse/QTBUG-28843 should i report it? or will it be resolved automatically ?
[10:33] <shadeslayer> jdrab: it'll be fixed when Qt releases the next bug fix revision and we package it
[10:34] <jdrab> shadeslayer: ty
[10:34] <shadeslayer> I think  it's in
[10:34] <shadeslayer> ( in the next bug fix release )
[10:34] <jdrab> do you think it will be fixed in neon sooner than 13.04?
[10:35] <shadeslayer> yes
[10:35] <shadeslayer> yofel_: care to upload a new snapshot of Qt ^ ?
[10:35] <shadeslayer> jdrab: this is assuming the fix was committed to Qt itself
[10:36] <shadeslayer> like I said, I *think* it was committed but I don't see a commit url to confirm on jira
[10:36] <shadeslayer> https://codereview.qt-project.org/#change,42266
[10:38] <jdrab> i always wanted to try neon :P now it's the time
[10:38] <yofel_> shadeslayer: qtjob is still running, so it should be in when it's committed
[10:38] <shadeslayer> ah you have a cron job running?
[10:38] <shadeslayer> awesome
[10:38] <yofel_> cronjob? what for?
[10:39] <yofel_> https://code.launchpad.net/~neon/+recipe/project-neon-qt
[10:41] <shadeslayer> err
[10:42] <shadeslayer> nvm
[10:42] <shadeslayer> I thought qt had issues being imported
[10:42] <yofel_> those were fixed ages ago ^^
[10:42] <shadeslayer> I see
[10:43] <shadeslayer> I thought we still had cronjob running and what not
[10:43] <shadeslayer> yofel_: btw http://www.golem.de/news/linux-distribution-ubuntu-erwaegt-umstieg-auf-rolling-releases-1301-97086.html
[10:43] <shadeslayer> yofel_: have you heard of this?
[10:43] <yofel_> hum, not yet
[10:44] <yofel_> I wouldn't really be against it. You would essentially have a 2-year stable platform and a bit more flexibility in between that
[10:44] <shadeslayer> yeah
[10:44] <yofel_> although that's what debian is
[10:44] <shadeslayer> heh
[10:45] <shadeslayer> I'd use sid if only their KDE version wasn't so outdated
[10:45] <shadeslayer> and I don't want to roll my own
[10:46] <yofel_> well, I prefer ubuntu as it's generally more up-to-date
[10:47] <yofel> I'm just worrying how "release packages when they're done" would work
[10:47] <yofel> we would essentially have <release> as rolling and <release-proposed> as dev?
[10:47] <yofel> not that we're not already going in that direction
[10:47] <shadeslayer> I'm not sure how the convinced sabdfl because iirc he was against rolling releases
[10:47] <yofel> ack
[10:48] <xnox> ;-))))))))
[10:48] <yofel> well, he'll keep the LTS releases, and it simplyfies support in general
[10:48] <yofel> as you would essentially drop needs for SRU's the 3 in-between releases
[10:49] <shadeslayer> xnox: oh oh I was installing Netrunner and wanted to ask you something
[10:49] <shadeslayer> xnox: so in the timzone selector I have to select Kolkata
[10:49] <xnox> yofel: security updates as well.
[10:49] <yofel> right
[10:49] <shadeslayer> xnox: which is like this tiny point on the map
[10:49] <shadeslayer> and defines the timezone for the whole of India
[10:50] <shadeslayer> would it be possible to just click India and make it automatically select 'Kolkata'
[10:50]  * yofel notes that this would make our job easier too - as we wouldn't have to worry about providing updates and backports for X releases in parallel but only 2 mostly
[10:50]  * xnox vaguely remembers some bugs about Kolkata as it's not the first time I'm looking it's location up =/
[10:50] <shadeslayer> *nod*
[10:51] <shadeslayer> xnox: so, plz2fix? :D
[10:51] <shadeslayer> I've done about 3-4 installs for friends over the last month and all of them complained about this
[10:52] <shadeslayer> ( I just watched as they did the install so I could see what issues they usually hit )
[10:58] <yofel> shouldn't the time-zone usually be auto recognised?
[10:59] <shadeslayer> yes, but for some reason it failed on 12.10 when I was installing it
[10:59] <shadeslayer> didn't debug why
[11:00] <yofel> hm
[11:00] <yofel> anyway
[11:00] <yofel> -> lunch, bbl
[11:04] <shadeslayer> cya
[12:35] <yofel> can someone else please try to reproduce bug 1103135? I can't
[12:35] <yofel> this is precise
[12:39] <phoenix_firebrd> yofel: i can test, rc3 for which version?
[12:42] <yofel> phoenix_firebrd: precise + 4.9.98 from beta ppa
[12:42] <yofel> I just asked the reporter if he really did restart his session after the upgrade
[12:42] <yofel> as that symbol error looks fishy
[12:43] <phoenix_firebrd> yofel: Its working in 12.10
[12:43] <yofel> phoenix_firebrd: how far did you get with kolab yesterday?
[12:43] <phoenix_firebrd> yofel: i dont have 12.04
[12:43] <yofel> no problem
[12:43] <phoenix_firebrd> yofel: its in launchpad 4 min to build for i386
[12:44] <yofel> I tried to reproduce it in a VM, but either it's not broken or I'm missing something
[12:44] <phoenix_firebrd> yofel: build successful with pbuilder, some tests fail
[12:45] <phoenix_firebrd> yofel: for the kate thing, there was some problem with qt that make many qt apps crah
[12:45] <phoenix_firebrd> *crash
[12:46] <yofel> hm, that doesn't look like a qt error though
[12:48] <phoenix_firebrd> yofel: in pbuilder kdeinit needs klauncher, so do i have to install the minimum kde packages?
[12:48] <phoenix_firebrd> yofel: thats for testing
[12:50] <yofel> phoenix_firebrd: for testing what?
[12:50] <phoenix_firebrd> yofel: the tests fail because kdeinit cant find klauncher binary
[12:50] <yofel> oh, good catch
[12:51] <yofel> I guess adding a build-dep for kdelibs5-plugins for the tests is acceptable
[12:53] <phoenix_firebrd> yofel: so after the tests should i have to remove the build-dep?
[12:53] <yofel> no, just add it to the Build-Depends in the control file
[12:54] <yofel> phoenix_firebrd: what's your launchpad id again?
[12:54] <phoenix_firebrd> yofel: https://launchpad.net/~murthy
[12:54] <phoenix_firebrd> yofel: dep wait https://launchpad.net/~murthy
[12:55] <phoenix_firebrd> oops
[12:55] <phoenix_firebrd> yofel: https://launchpadlibrarian.net/129196232/buildlog_ubuntu-raring-i386.libkolab_0.4.1-0ubuntu1_MANUALDEPWAIT.txt.gz
[12:55] <yofel> thanks
[12:56] <yofel> phoenix_firebrd: what's libkcalccore4 ?
[12:56] <phoenix_firebrd> yofel: its in universe , it is needed
[12:56] <yofel> no, wait, we need to clear something up here
[12:56] <phoenix_firebrd> yofel: how can i add universe to the ppa?
[12:57] <yofel> that you can do from the main ppa page -> Edit Dependencies
[12:57] <yofel> phoenix_firebrd: now back to the lib: it's needed by what?
[12:58] <yofel> phoenix_firebrd: and it's libkcalcore4 not libkcalccore4
[12:58] <phoenix_firebrd> yofel: during build it failed at a point and i went it to the source and found it needs this
[12:59] <yofel> let me try this again
[12:59] <phoenix_firebrd> yofel: checking
[13:00] <phoenix_firebrd> yofel: yes its a typo
[13:00] <yofel> phoenix_firebrd: and another thing: when you upload a package to a ppa, at least append ~ppa1 to the version, as you now won't be able to properly put an updated package into the PPA that can later be  updated to the archive package
[13:01] <yofel> note that ~ lowers the version
[13:01] <phoenix_firebrd> yofel: ya, i usually put -
[13:01] <yofel> - is higher, so that won't help either
[13:02]  * yofel tries to build without libkcalcore4 and libkabc
[13:02] <phoenix_firebrd> ok
[13:04] <yofel> phoenix_firebrd: see http://www.debian.org/doc/debian-policy/ch-controlfields.html#s-f-Version on how the package version is calculated
[13:05] <phoenix_firebrd> this is heaven
[13:10] <yofel> builds without those libs, but tests still fail
[13:11] <phoenix_firebrd> yofel: for raring right?
[13:11]  * yofel wonders if this is the problem:
[13:11] <yofel> (13:10:19) commonconversion.cpp(43):    ktimezoned is not available and required for timezone interpretation
[13:11] <yofel> raring, yes
[13:12] <phoenix_firebrd> yofel: ktimezoned fails because of dbus not available
[13:12] <yofel> oh, right, now I saw that error too
[13:12] <phoenix_firebrd> yofel: need dbus and dbus-x11
[13:12] <phoenix_firebrd> yofel: what error?
[13:12] <yofel> already installed
[13:12] <phoenix_firebrd> yofel: in that case kdelibs-plugin?
[13:13] <yofel> klauncher(21427) kdemain: No DBUS session-bus found. Check if you have started the DBUS server.
[13:13] <phoenix_firebrd> thats it
[13:14] <phoenix_firebrd> yofel: does pbuilder store every build log and if so where?
[13:14] <yofel> did you use pbuilder-dist? I think that stores a .build file somewhere near the source or the build result
[13:14] <yofel> only the last build though
[13:17] <phoenix_firebrd> yofel: i used pbuilder
[13:17] <phoenix_firebrd> yofel: i am confused
[13:18] <yofel> not sure where that puts it, I have this in my .pbuilderrc:
[13:18] <yofel> PKGNAME_LOGFILE_EXTENTION="_$(dpkg --print-architecture).build"
[13:18] <yofel> PKGNAME_LOGFILE=yes
[13:18] <yofel> which puts a logfile in the result folder
[13:20] <phoenix_firebrd> yofel: can using pbuilder-dist be different from pbuilder in building process? I am wondering how it failed for me
[13:21] <yofel> phoenix_firebrd: do you have universe enabled in pbuilder?
[13:21] <phoenix_firebrd> yofel: ya, i put that in the pbuilderrc file
[13:21] <yofel> hum, can't say it then without a buildlog
[13:23] <phoenix_firebrd> yofel: what is the universe repository string
[13:23] <yofel> my sources list has:
[13:23] <yofel> deb http://archive.ubuntu.com/ubuntu/ raring main restricted universe multiverse
[13:27] <phoenix_firebrd> yofel: no the string which i should be adding in the launchpad
[13:27] <yofel> why launchpad?
[13:27] <phoenix_firebrd> yofel: testing
[13:28] <yofel> we're not at a point where the package will even build
[13:28] <phoenix_firebrd> yofel: no i wont build
[13:28] <phoenix_firebrd> yofel: just to know
[13:28] <shadeslayer> cyphermox: mathieu-tl AT ubuntu ?
[13:28] <yofel> the ppa already has universe enabled
[13:29] <yofel> you see that in the buildlog
[13:29] <yofel> Get:11 http://ftpmaster.internal raring/universe i386 Packages [5407 kB]
[13:29] <shadeslayer> apparently yes
[13:29] <yofel> shadeslayer: do you know how to use dbus in package tests?
[13:30] <shadeslayer> yofel: I need more info, the kind that KDE ships with ?
[13:30] <shadeslayer> the ones you can start with make check/test
[13:30] <shadeslayer> or autopkg tests and what not
[13:30] <yofel> the ones that dh_auto_test will run
[13:31] <shadeslayer> right, make test/check
[13:31] <yofel> right
[13:32] <shadeslayer> ideally those tests should use dbus-launch?
[13:32] <shadeslayer> or you could override dh_auto_test and manually start a session if the test doesn't do it already?
[13:34] <yofel> that's what I tried, let me try again to get a clean log
[13:39] <yofel> shadeslayer: http://paste.kde.org/654422/
[13:40] <shadeslayer> and are you sure that dbus was launched?
[13:40] <shadeslayer> maybe dbus needs other stuff setup first or sth
[13:40] <yofel> well, I probably did it the wrong way
[13:40] <yofel> now I did 'dbus-launch dh_auto_test' and it hung up
[13:40] <shadeslayer> heh
[13:41] <yofel> oh fun
[13:41] <yofel> QSYSTEM: FormatTest::testIncidence(v2eventSimple) startkdeinitlock(8895)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned initialize() D-Bus call failed:  "The name org.
[13:41] <yofel> kde.kded was not provided by any .service files"
[13:41] <yofel> this won't work...
[13:41] <shadeslayer> first start dbus, then launch org.kde.kded?
[13:42] <shadeslayer> or kded even
[13:43] <phoenix_firebrd> builds without those deps
[13:43] <phoenix_firebrd> yofel: ^
[13:43] <yofel> shadeslayer: how does one do that?
[13:43] <shadeslayer> doesn't matter, just pull it in?
[13:44] <yofel> kde-runtime-data: /usr/share/kde4/services/kded/ktimezoned.desktop
[13:44] <yofel> is installed
[13:46] <shadeslayer> just run kded4
[13:47] <shadeslayer> but dbus should be running I think
[13:47] <shadeslayer> never tried running kded4 without dbus :P
[13:50] <yofel> shadeslayer: running dbus-launch is fine, but I fail at getting DBUS_SESSION_BUS_ADDRESS and DBUS_SESSION_BUS_PID into the environment after that
[13:51] <shadeslayer> oh, how do you do dbus-launch? just dbus-launch?
[13:51] <shadeslayer> can you try eval `dbus-launch`
[13:51] <yofel>         eval `dbus-launch`
[13:51] <yofel>         export DBUS_SESSION_BUS_ADDRESS DBUS_SESSION_BUS_PID
[13:51] <yofel>         kded4
[13:51] <yofel>         dh_auto_test
[13:52] <yofel> fails at kded4
[13:53] <shadeslayer> can you do a echo $DBUS_SESSION_BUS_ADDRESS $DBUS_SESSION_BUS_ADDRESS ?
[13:57] <yofel> shadeslayer: hm, DBUS_SESSION_BUS_PID is unset
[13:58] <yofel> shadeslayer: http://paste.kde.org/654446
[13:58] <shadeslayer> whaaaa
[13:59] <shadeslayer> hmm how odd
[14:01] <shadeslayer> yofel: try kdeini4 kded4
[14:01] <yofel> great, putting the stuff into a subscript worked... but now:
[14:01] <yofel> kded4: cannot connect to X server :0
[14:01]  * yofel resigns
[14:01] <shadeslayer> xD
[14:01] <shadeslayer> xvfb :P
[14:02] <yofel> why do people assume that kde is running during a build...
[14:03] <agateau> hey, dummy question: are kde packages built with -DQT_NO_DEBUG ?
[14:05] <yofel> agateau: I think yes
[14:06] <agateau> yofel: ok, thanks. Do you know if other distros do the same?
[14:09] <yofel> That I fear I don't know
[14:09] <shadeslayer> cyphermox: sent
[14:10] <yofel> shadeslayer: that hangs even earlier, I think we'll skip this for now
[14:10] <yofel> phoenix_firebrd: still there?
[14:10] <phoenix_firebrd> yofel: ya
[14:10] <shadeslayer> yofel: give it to me :P
[14:10] <phoenix_firebrd> yofel: watching
[14:10]  * shadeslayer can work on it a bit
[14:10] <yofel> shadeslayer: how about you fix this up once I'm done explaining the rest to phoenix_firebrd?
[14:10] <shadeslayer> ah sure
[14:10] <shadeslayer> whatcha guys packaging?
[14:11] <yofel> libkolab
[14:12] <yofel> phoenix_firebrd: put this in your debian/rules: http://paste.kde.org/654464/ - that will make the test not hold everything up
[14:12] <shadeslayer> I see
[14:12]  * shadeslayer would have gone for a .PHONY target there
[14:13] <yofel> why?
[14:14] <shadeslayer> just to be safer?
[14:14] <shadeslayer> though that's fine as well :)
[14:14] <yofel> well, I just wanted to get the error out of the way, not the tests themselves
[14:14] <shadeslayer> ah
[14:15] <phoenix_firebrd> yofel: next?
[14:16] <yofel> phoenix_firebrd: try to build it again, it'll end at missing files this time
[14:16]  * shadeslayer notes that we should put up a wiki page explaining what can be shipped and what's blacklisted
[14:17] <yofel> blacklisted as in?
[14:17] <shadeslayer> well
[14:17] <shadeslayer> blacklisted from the seeds
[14:17] <shadeslayer> libav for eg
[14:17] <yofel> ah, look at the seeds?
[14:17] <shadeslayer> sure, but no user looks at the seeds
[14:17] <yofel> hum, true
[14:18] <shadeslayer> they're like "The thing thats used to grow plants?"
[14:18] <EagleScreen> why apturl-kde depends on software-properties-kde, doues it really need it? is to enable repositories on the fly?
[14:18] <shadeslayer> hmm
[14:19] <shadeslayer> probably uses some python function?
[14:21] <yofel> doEnableSection() runs software-properties-kde so that's ok
[14:21] <yofel> EagleScreen: that's the case it seems
[14:21] <EagleScreen> I see, thanks
[14:23] <phoenix_firebrd> yofel: you and shadeslayer were discussing about running processes before in testing process, how to do that?
[14:24] <shadeslayer> phoenix_firebrd: things like dbus-launch and kded4?
[14:24] <EagleScreen> and that kind of functions shouldn't be go to software-properties-common?
[14:24] <shadeslayer> just add them to the required target
[14:24] <phoenix_firebrd> shadeslayer: ya
[14:24] <phoenix_firebrd> shadeslayer: for example dolphin
[14:24] <Riddell> shadeslayer: ship: * !libavcodec*
[14:24] <Riddell> ship: * !phonon-backend-null
[14:25] <Riddell> ! means blacklist
[14:25] <shadeslayer> Riddell: that too
[14:25] <yofel> EagleScreen: not as long as it does this: http://paste.kde.org/654482
[14:27] <EagleScreen> wow
[14:29] <yofel> phoenix_firebrd: rules is a Makefile, there you can define a target which you can then add a list of command to. So in dh7 packaging we would add an override target and just run the commands we want to add before the overridden command
[14:30] <phoenix_firebrd> yofel: ok. installing fails. http://paste.kde.org/654488/
[14:31] <yofel> phoenix_firebrd: right, as those are header files, you'll have to add them to libkolab-dev.install
[14:32] <phoenix_firebrd> yofel: what is this file  libkolab-dev.install ?
[14:32] <shadeslayer> afiestas: does webaccounts have a release?
[14:32] <yofel> a .install files tells debhelper what files will end up in a package
[14:32] <afiestas> shadeslayer: ?
[14:32] <shadeslayer> afiestas: a versioned release
[14:32] <yofel> development .so links and header files go into a -dev package by convention
[14:33] <afiestas> don't think so
[14:33] <shadeslayer> like 0.1 or sth
[14:33] <yofel> phoenix_firebrd: so libkolab-dev.install is the list of files that will be put into libkolab-dev
[14:33] <phoenix_firebrd> yofel: what about be the location of the  libkolab-dev.install?
[14:33] <yofel> inside the debian/ folder as always
[14:33] <yofel> it's already there, you just need to add the 3 files to it
[14:34] <phoenix_firebrd> yofel: so the output of debuild would be two packages?
[14:34] <yofel> yes, debian/control has 2 Package: definitions, i.e. you'll get 2 packages
[14:35] <yofel> you can add an install file for every package. (Actually once you have more than one package you need install files)
[14:36] <phoenix_firebrd> yofel: ok i have added the 3 lines to the install files,should i build ?
[14:36] <yofel> phoenix_firebrd: yep, but for the next step make sure that pbuilder saves the buildlog somewhere
[14:39] <phoenix_firebrd> yofel: sorry i started the build process without routing to a file, i will do it the next time
[14:39] <yofel> just let pbuilder do that for you...
[14:40] <yofel> phoenix_firebrd: do you have any .build files in /var/cache/pbuilder/result/ ?
[14:40] <phoenix_firebrd> yofel: on call
[14:40] <yofel> or wherever the build result gets put for you
[14:42] <Riddell> my toolbars keep disappearing :(
[14:43] <phoenix_firebrd> yofel: that location doesn't contain any logs
[14:44] <yofel> phoenix_firebrd: add this to your .pbuilderrc if you don't have it:
[14:44] <yofel> PKGNAME_LOGFILE_EXTENTION="_$(dpkg --print-architecture).build"
[14:44] <yofel> PKGNAME_LOGFILE=yes
[14:45] <yofel> it'll then put a logfile named after the package into $BUILDRESULT
[14:45] <EagleScreen> software-properties-kde seems to be outdated respect software-properties-gtk, do you plan update it ? do you plan use jockey forever to enable restricted drivers?
[14:46] <phoenix_firebrd> yofel: this is my pbuilderrc http://paste.kde.org/654506/
[14:47] <phoenix_firebrd> yofel: is content in rc file correct?
[14:47] <yofel> yes, just add the 2 lines I posted
[14:47] <phoenix_firebrd> yofel: adding
[14:47] <phoenix_firebrd> done
[14:48] <shadeslayer> EagleScreen: re jockey, I might look into that next month
[14:48] <shadeslayer> since no one has bothered looking into it
[14:49] <yofel> phoenix_firebrd: while we're at it, let's add one more thing that all of us use
[14:49] <yofel> first run 'bzr co lp:~kubuntu-packagers/pbuilder/pbuilder-hooks ~/.pbuilder-hooks'
[14:50] <phoenix_firebrd> yofel: i think build succeed. http://paste.kde.org/654518/
[14:50] <yofel> and then add this to your pbuilderrc:
[14:50] <yofel> HOOKDIR="$HOME/.pbuilder-hooks"
[14:50] <yofel> phoenix_firebrd: yep, and now we get to something that's specific to library packaging: symbol files
[14:51] <yofel> phoenix_firebrd: do you know what library symbols are?
[14:51] <phoenix_firebrd> yofel: i was once , when cracking windows exes and dlls
[14:52] <yofel> ah ok, linux ofc has them too, and we track the ABI of a library by keeping a list of all provided symbols in the package
[14:53] <yofel> that's what the libkolab0.symbols file in the package is for
[14:53] <yofel> now you'll see that dpkg-gensymbols posted a diff in the buildlog
[14:53] <phoenix_firebrd> yofel: checking
[14:53] <yofel> so the new version adds a lot of symbols (and removes 2 optional ones - marked as #MISSING#)
[14:54] <phoenix_firebrd> yofel: i can see that in the log
[14:55] <yofel> good, as c++ is a bit weird with symbols, we have a helper called pkgkde-symbolshelper that helps to manage the symbols
[14:55] <yofel> you can read more on that on http://pkg-kde.alioth.debian.org/symbolfiles.html
[14:55] <yofel> for now I'll explain on how to update the file
[14:56] <yofel> for that you'll need to be inside the package, i.e. in libkolab-0.4.1
[14:56] <yofel> next you'll need a file with the symbol diff, the buildlog works fine for that
[14:56] <yofel> now you need to update the symbols for the new version, which you can do with:
[14:57] <yofel> pkgkde-symbolshelper batchpatch -v 0.4.1 path_to_buildlog
[14:57] <yofel> just put the actual buildlog a the end instead
[14:58] <yofel> phoenix_firebrd: this should look like this in the end: http://paste.kde.org/654524
[14:58] <phoenix_firebrd> yofel: the buildlog should be full or partial is satisfied?
[14:58] <yofel> phoenix_firebrd: partial is fine as long as you have the complete symbol diff
[14:59] <yofel> as the script will look for the output of dpkg-gensymbols
[14:59] <phoenix_firebrd> yofel: shall i try with this http://paste.kde.org/654518/?
[14:59] <yofel> yeah, should work
[15:02] <phoenix_firebrd> yofel: http://paste.kde.org/654530/
[15:03] <yofel> yeah, looks right
[15:04] <phoenix_firebrd> yofel: what about the missing ones
[15:04] <yofel> now just to clean it up: open the symbols file in an editor, look for the MISSING ones and remove the commented lines
[15:04] <yofel> they're optional so don't worry about them
[15:07] <phoenix_firebrd> yofel: this is the symbol file after removing the commented lines http://paste.kde.org/654536/
[15:07] <phoenix_firebrd> yofel: ok?
[15:08] <phoenix_firebrd> yofel: i have done the launchpad pbuilder hook
[15:08] <yofel> the symbolsfile looks ok from what I see. Try building again, this time there should be no diff
[15:09] <yofel> good, those are some pbuilder enhancements that we use to make life easier
[15:09] <phoenix_firebrd> yofel: what does that do?
[15:10] <yofel> phoenix_firebrd: it's just a set of scripts, feel free to read them. The pbuilder manpage explains when what is called
[15:10] <yofel> (most important ones are auto-installing-updates and running list-missing at the end)
[15:11] <phoenix_firebrd> yofel: ok
[15:11] <phoenix_firebrd> yofel: going to build again
[15:13] <phoenix_firebrd> yofel: what about the tests? is it mandate for them to succeed to build a package?
[15:14] <yofel> it's mostly a mandate in main, so I think we could live without them. But they should work really. Problem now is that it seems you need to set up a working kde session during the build for them to work :/
[15:15] <phoenix_firebrd> yofel: i installed dbus and dbus-x11 after login and with save after login option
[15:15] <yofel> that won't help for the archive
[15:16] <phoenix_firebrd> yofel: ya
[15:16] <yofel> there you have to set everything up during the build
[15:17] <phoenix_firebrd> yofel: why didn't apt-cache search klaunch return kdelibs5-plugin , instead return some xfce package?
[15:17] <phoenix_firebrd> *klauncher
[15:17] <yofel> klauncher has no own package, use dpkg -S or apt-file search
[15:19] <phoenix_firebrd> yofel: right
[15:21] <yofel> geh, running make test on a local libkolab build opens kompare several times
[15:21] <yofel> that's not doable during a package build
[15:21] <yofel> phoenix_firebrd, shadeslayer: forget the tests -.-
[15:21] <shadeslayer> oh?
[15:22] <shadeslayer> why not?
[15:22] <phoenix_firebrd> ?
[15:22] <yofel> see 2 lines above
[15:22] <shadeslayer> xvfb?
[15:22] <yofel> and how do you close kompare in xvfb?
[15:22] <shadeslayer> or whatever it's called
[15:22] <shadeslayer> don't?
[15:22] <yofel> the tests don't continue while it's open?
[15:22] <shadeslayer> ah
[15:22]  * shadeslayer thinks
[15:23] <shadeslayer> yofel: if possible, can you check if there's a dbus interface that we can call as soon as kompare is seen on the screen?
[15:23] <shadeslayer> so you could tell it to quit
[15:23] <shadeslayer> over dbus
[15:23] <phoenix_firebrd> why is it opening
[15:25] <shadeslayer> phoenix_firebrd: because it's a test :)
[15:25] <shadeslayer> yofel: and complaint loudly to kolab people :P
[15:25] <yofel> qdbus org.kde.kompare-24620 /kompare/FirstKompareShell org.qtproject.Qt.QWidget.close
[15:25] <yofel> works, but as you see it has the PID in the interface URL
[15:25] <shadeslayer> simple
[15:26] <shadeslayer> qdbus `qdbus|grep kompare 0 /kompare/FirstKompareShell org.qtproject.Qt.QWidget.close`
[15:26] <shadeslayer> erm
[15:26] <yofel> ok, I'll leave it to you to figure it out :P
[15:26] <shadeslayer> qdbus `qdbus|grep kompare` /kompare/FirstKompareShell org.qtproject.Qt.QWidget.close`
[15:26] <shadeslayer> haha :P
[15:26] <shadeslayer> just give me the packaging :P
[15:26] <shadeslayer> when you're done
[15:26] <yofel> phoenix_firebrd: how did the build go?
[15:26] <shadeslayer> cyphermox: fun, upstream will refuse qapt/packagekit patches
[15:27] <phoenix_firebrd> yofel: its running
[15:27] <shadeslayer> Riddell: I just talked to Lamarque and he said that he will not allow packages that add a feature that installs VPN packages on the fly when clicking "Setup VPN" or sth
[15:28] <cyphermox> shadeslayer: they won't, it can just be a compile-time switch, and show a proper error message when there is no way to invoke qapt or whatever, this is implementation detail that shouldn't be considered too much
[15:28] <cyphermox> instead, I'd just write a patch and propose it
[15:28] <shadeslayer> cyphermox: I mentioned that
[15:28] <shadeslayer> see the latest switch, you can try and convince him if you want :P
[15:28] <shadeslayer> erm
[15:28] <shadeslayer> s/switch/email/
[15:28] <kubotu> shadeslayer: You did something wrong... Try s/you/me/ or tell me "help sed"
[15:28] <Riddell> shadeslayer: why not?
[15:28] <shadeslayer> Riddell: "You can patch Plasma NM when building packages for (K)Ubuntu. I am just saying that I will not patch Plasma NN to do half work, if it does not work for everybody then this change should stay in (K)Ubuntu only."
[15:29] <shadeslayer> from email archives
[15:29] <shadeslayer> cyphermox: and by upstream I meant KDE upstream
[15:29] <Riddell> ok so we can add the feature but he won't take it upstream
[15:29] <shadeslayer> yes
[15:30] <Riddell> shadeslayer: remind me again why we need this?
[15:30] <shadeslayer> Riddell: plasma-widget-nm statically compiles a list of VPN stuff in the UI
[15:30] <shadeslayer> and that stuff won't actually work until that nm plugin is installed
[15:31] <cyphermox> shadeslayer: I think the approach by email was wrong, I'll respond
[15:31] <phoenix_firebrd> yofel: full log http://paste.kde.org/654566/
[15:31] <shadeslayer> cyphermox: I see
[15:31] <shadeslayer> cyphermox: feel free to
[15:32] <shadeslayer> Riddell: go to the VPN tab in network manager plasmoid
[15:33] <shadeslayer> so if you add PPTP for eg, it won't work till you have network-manager-pptp install
[15:33] <shadeslayer> *installed
[15:33] <Riddell> shadeslayer: but why can't we just have them all installed by default?
[15:33] <shadeslayer> useless for most users?
[15:35] <Riddell> hmm   blacklist:network-manager-vpnc
[15:35] <Riddell> I wonder why that is
[15:35] <Riddell> I'm not sure that seed actually does anything now
[15:36] <phoenix_firebrd> yofel: I am getting an error "pkgkde-symbolshelper: error: no valid patches found"
[15:39] <yofel> phoenix_firebrd: there is no patch - which means everything's ok now
[15:39] <phoenix_firebrd> yofel: thought so, nice
[15:40] <yofel> I just noticed that cmake complains about SWIG, but I have that installed here and it still complains
[15:40] <Riddell> yofel: has libkolab changed a lot?
[15:40] <phoenix_firebrd> yofel: where did you see, in my log?
[15:40] <yofel> Riddell: a few new headers, new symbols, and a few new annoying tests
[15:41] <yofel> the tests are what we're talking about all day
[15:41] <yofel> oh, I had swig2.0, kolab wants swig
[15:41]  * yofel has no idea what swig is
[15:41] <yofel> Description-en: Generate scripting interfaces to C/C++ code
[15:44] <shadeslayer> wtf
[15:44] <shadeslayer> I can't resize a skype window
[15:44] <phoenix_firebrd> yofel: should we add swig2.0 to build-deps ?
[15:45] <shadeslayer> the chat window specifically
[15:46] <yofel> phoenix_firebrd: it's 'swig' that it wants - but I don't see any difference when adding it...
[15:47] <phoenix_firebrd> yofel: loss of functionality witout that?
[15:47] <yofel> not sure, I guess it won't hurt to add it
[15:47] <phoenix_firebrd> yofel: ok
[15:47] <yofel> So add it and put the package somewhere where shadeslayer can fetch it
[15:48] <yofel> as I think we're done otherwise
[15:48] <shadeslayer> put it in a PPA?
[15:48] <phoenix_firebrd> yofel:  ok :)
[15:48] <yofel> ok, ppa...
[15:48] <phoenix_firebrd> mine?
[15:49] <yofel> phoenix_firebrd: if you want to put it in the same ppa again, 2 things:
[15:49] <yofel> a) manually delete the package in there first
[15:49] <phoenix_firebrd> ~ppa1?
[15:49] <yofel> b) change the version to 0.4.1-0ubuntu1~ubuntu13.04~ppa1
[15:49] <yofel> that's the convention for raring
[15:50] <phoenix_firebrd> yofel: ok
[15:50] <Riddell> apachelogger: bug 1102165 known to you?
[15:50] <yofel> phoenix_firebrd: and update the changelog a bit
[15:50] <yofel> phoenix_firebrd: so it tells others what you did
[15:50] <yofel> phoenix_firebrd: meaning at least updating the install and symbol files
[15:51] <yofel> :q
[15:51] <yofel> fail -.-
[15:53] <shadeslayer> :P
[15:53] <shadeslayer> Who want's to reply to "Change the default settings of Kubuntu to improve the first time user experience "
[15:53] <yofel> read it half, ask me again on saturday
[15:54] <shadeslayer> haha
[15:54] <EagleScreen> shadeslayer: and what will you reply to him?
[15:54] <phoenix_firebrd> yofel: i can't understand what you are asking me to put in the changelog
[15:54]  * Riddell is doing e-mails now
[15:54] <shadeslayer> awesome
[15:55] <shadeslayer> EagleScreen: just that some stuff can't be done while other stuff should be done in upstream KDE
[15:55] <shadeslayer> Kubuntu aims to provide a pristine KDE experience.
[15:55] <yofel> Riddell++
[15:55] <shadeslayer> now if that experience is bad, fix it in KDE
[15:56] <EagleScreen> who decided that Kubuntu has to provide a pristine KDE experience?
[15:56] <shadeslayer> Riddell :P
[15:56] <EagleScreen> I think the guy who wrote that message has a lot of reason
[15:56] <shadeslayer> and I think almost everyone agrees
[15:57] <yofel> phoenix_firebrd: something like http://paste.kde.org/654620 - just so people know that you did change something
[15:57] <EagleScreen> a few custimation over the default KDE would improve the first user experiencie
[15:57] <phoenix_firebrd> yofel: really?
[15:58] <shadeslayer> EagleScreen: any reason why they should not be upstreamed?
[15:58] <phoenix_firebrd> yofel: when the user sees this what will they understand ?
[15:58] <shadeslayer> i.e. made default in KDE
[15:58] <yofel> a few things like yakuake are nonsense, vlc isn't doable I think. We already talked about rekonq. Do people use the keep above others button? I do, but do others?
[15:58] <shadeslayer> EagleScreen: note that we're talking about KDE configs in particular
[15:58] <yofel> phoenix_firebrd: that's not for users, but for fellow package maintainers
[15:58] <yofel> phoenix_firebrd: and people that review what you did
[15:59] <phoenix_firebrd> yofel: oh
[15:59] <phoenix_firebrd> yofel: now it makes sense
[15:59] <yofel> it's the same as a VCS commit message really
[15:59] <EagleScreen> shadeslayer: yes, it is much harder and it will take much time to have it done by upstream than by Kubuntu, many distributions customize its desktops to improve the user experience, upstream hasn't the reason always
[16:00] <shadeslayer> not harder
[16:00] <shadeslayer> if it's sane and everyone agrees that it's a sane default, it won't be harder
[16:00]  * yofel wonders if his reply to kde bug 310486 was a bit too harsh
[16:01] <yofel> not even sure that's something *they* want to even be concerned about
[16:03] <EagleScreen> i have suffered off that bug
[16:03] <Riddell> yofel: grumpy! :)
[16:03] <EagleScreen> i'd only worry about it if it happens also in minor kde upgrades (4.9.4 -> 4.9.5)
[16:03] <Riddell> yofel: but that is a longstanding problem
[16:04] <yofel> Riddell: yeah, but usually it works - just this time they change the implementation and BOOM
[16:05] <yofel> EagleScreen: yeah, it's not really *that* great of an issue. But it looks REALLY unprofessional if a software update causes you do hard-cycle your system
[16:05] <yofel> which is what my dad would do in such a situation
[16:06] <EagleScreen> my dad and all my friend would do it too
[16:07] <phoenix_firebrd> shadeslayer: this is my ppa "murthy/test"
[16:07] <shadeslayer> cool
[16:07] <shadeslayer> oh
[16:07] <phoenix_firebrd> yofel: i have uploaded the package waiting for the confirmation mail
[16:08] <shadeslayer> phoenix_firebrd: you're from India? :D
[16:08]  * shadeslayer is guessing from the name
[16:08] <phoenix_firebrd> shadeslayer: ya
[16:08] <shadeslayer> your package is FTBFS in the PPA xD
[16:08] <shadeslayer> phoenix_firebrd: I'm in Gurgaon :)
[16:08] <phoenix_firebrd> shadeslayer: i am from Tamilnadu
[16:08]  * shadeslayer rages at bzr for being so slow to checkout
[16:09] <phoenix_firebrd> shadeslayer: nice
[16:10] <phoenix_firebrd> shadeslayer: you are a software engineer?
[16:10] <shadeslayer> phoenix_firebrd: yeah :)
[16:10] <shadeslayer> by profession only however
[16:10] <phoenix_firebrd> shadeslayer: cool
[16:11] <shadeslayer> I'm electronics and comm. engineer by education :P
[16:11] <phoenix_firebrd> shadeslayer: me too
[16:11] <shadeslayer> :)
[16:12] <Riddell> shadeslayer: really?  so this kubuntu stuff is just a side hobby for you?
[16:12] <shadeslayer> it's the other way around, the Electronics/GSM stuff was a hobby
[16:12] <yofel> phoenix_firebrd: if you want, libkolabxml would be the next thing to update - it's less work too (I just checked ;P)
[16:13] <phoenix_firebrd> yofel: sure, can i do it tomorrow?
[16:13] <yofel> 1 patch to be dropped, a few new build-deps, and that's it
[16:13] <yofel> sure, just say if you need help or a review
[16:14] <phoenix_firebrd> yofel: sure, its bed time and i have to finish my dinner
[16:14] <yofel> hm, it seems some people can go to bed before sunrise... unlike shadeslayer :P
[16:14] <shadeslayer> hehe
[16:14] <phoenix_firebrd> yofel: i have uploaded the files and its in the ppa, how can i delete the old one, there is no option to delete it
[16:15] <shadeslayer> I pulled off about 30 hours on Monday-Tuesday
[16:15] <phoenix_firebrd> yofel: usually i do that
[16:15] <yofel> phoenix_firebrd: https://launchpad.net/~murthy/+archive/test/+packages should have a delete button on the right side of the page
[16:15] <shadeslayer> at the end of 30 hours I wanted to just sleep
[16:15] <yofel> if you haven't deleted the package yet it'll probably get rejected
[16:16] <shadeslayer> but won't it get rejected even then?
[16:16] <shadeslayer> i.e. even after deleting them
[16:16] <yofel> as long as the tarball isn't different it should accept it I think
[16:16] <phoenix_firebrd> yofel: done
[16:17] <phoenix_firebrd> yofel: its getting built for amd64
[16:17] <yofel> ah, the version is totally wrong, but I guess we can fix that
[16:18] <shadeslayer> phoenix_firebrd: pro tip, I know how much internet connections in India suck, so I'd advise asking Riddell for an EC2 instance since usually that's alot faster to work on
[16:19] <phoenix_firebrd> yofel: omg, very sorry , i just noticed that
[16:19] <shadeslayer> or buying a dedicated server if you have the moniez
[16:19] <phoenix_firebrd> shadeslayer: ya
[16:20] <Riddell> ec2 available on request indeed
[16:22] <yofel> phoenix_firebrd: nevermind, it would only be a problem for someone that uses the ppa
[16:23] <shadeslayer> Riddell: can you upload PA3 today?
[16:23] <shadeslayer> I cannot find the time to upload it :|
[16:23] <shadeslayer> note that the rules could use with a bit of fixing ( needs branch switching )
[16:25] <phoenix_firebrd> shadeslayer: what troubles me more is not the internet speed, it the 2 hrs scheduled power cut.
[16:25] <shadeslayer> haha
[16:25] <Riddell> shadeslayer: it's ready?
[16:25] <shadeslayer> My router + modem combo is on backup power
[16:25] <shadeslayer> Riddell: yes
[16:25] <shadeslayer> I tested it, works perfectly
[16:25] <Riddell> sweet
[16:26] <Riddell> shadeslayer: from ~kubuntu-active PPA?
[16:26] <phoenix_firebrd> shadeslayer:  here no backup
[16:26] <shadeslayer> yep
[16:26] <shadeslayer> It also changed my configs to be more tablet friendly
[16:26] <shadeslayer> so when I logged into plasma-desktop, all my buttons were *huge*
[16:27] <shadeslayer> yofel: apachelogger suggest we should setup a PPA with packages that replace standard kde packages but everything be built from git
[16:27] <shadeslayer> want to start on that? :D
[16:28] <Riddell> shadeslayer: mm isn't that neon?
[16:29] <shadeslayer> Riddell: no, neon installs to /opt/project-neon
[16:29] <shadeslayer> We're talking about dailies that replace your stable desktop
[16:29] <Riddell> shadeslayer: the maintinance of that sounds impossible
[16:29] <shadeslayer> for people living on the extreme edge
[16:29] <shadeslayer> Riddell: that's what I said as well
[16:29] <Riddell> there's a reason neon uses simplified packaging
[16:29] <shadeslayer> *nod*
[16:30] <shadeslayer> Riddell: possibly apachelogger was drunk or sth
[16:30] <yofel> well, it's not IMPOSSIBLE with more patterns in install files etc. but it would need some dedicated maintainer (not me)
[16:31] <yofel> and the launchpad folks would probably want to kill us for building kde daily twice
[16:31] <shadeslayer> haha
[16:34] <Alex_Zion> HI guys , i'm pretty sure a lot of user here are on kubuntu devel mailing list, where I post my first post yesterday, it was a well written post !?! , I mean is the first time I write and I never read you mailing list, so I don't know, it was too long, too short, is better put more o less detail or they are just enough !?! and stuff like that , just to teach me even how to write a good and usefull posts on mailing list .. :)
[16:36] <phoenix_firebrd> shadeslayer: you will take care of the rest for libkolab ?
[16:37] <Riddell> Alex_Zion: a good e-mail, I'm writing a reply now, most of the issues we've considered before however
[16:37] <shadeslayer> phoenix_firebrd: yeah :)
[16:37] <Alex_Zion> well , good to know Riddell ;)
[16:37] <phoenix_firebrd> shadeslayer: thank you
[16:37] <shadeslayer> I'll try and do enable tests in a bit
[16:37] <phoenix_firebrd> yofel: anything else?
[16:38] <BluesKaj> ok , bbl..stuff to do
[16:38] <yofel> phoenix_firebrd: for libkolab? not from my side
[16:39] <phoenix_firebrd> yofel: in that case good night to you, shadeslayer Riddell. I have learned something today.
[16:39] <shadeslayer> night :)
[16:39] <yofel> gn
[16:39] <Riddell> night phoenix_firebrd
[17:09] <cyphermox> shadeslayer: there, if we send a patch it will be accepted.
[17:09] <shadeslayer> *nod*
[17:28] <shadeslayer> yofel: odd : kded(14371): KUniqueApplication: Cannot find the D-Bus session server:  "Unable to autolaunch a dbus-daemon without a $DISPLAY for X11"
[17:28] <shadeslayer> even though X was started
[17:29] <yofel> hm, is DISPLAY set?
[17:30] <shadeslayer> yep
[17:30] <shadeslayer> that's the first thing I do
[17:30] <yofel> :/
[17:32] <shadeslayer> sec
[17:51] <apachelogger> shadeslayer, Riddell: gentoo has a smaller team and they manage to do it...
[17:52] <yofel> apachelogger: using how simple packaging? (I didn't look at the portage scripts)
[17:53] <apachelogger> the point is it is no more work than what we do now
[17:53] <apachelogger> except it is incremental
[17:53] <yofel> hm
[17:53] <apachelogger> so half the team does not become unavailable when a kde release is out
[17:53] <yofel> well
[17:54] <yofel> I guess I could wrap something up experimentally for the core packages
[17:54] <shadeslayer> yofel: any ideas how I can get xvfb-run to run multiple commands in one go?
[17:54] <yofel> no
[17:54] <apachelogger> I am not saying we should do this for every package, but at least the core monolithic ones
[17:54] <shadeslayer> :S
[17:54] <apachelogger> i.e. libs,pimlibs,workspace,baseapps,runtime
[17:55] <yofel> then you might as well do it for the others as there's not much to maintain there - except running a script to update the version as needed
[17:55] <apachelogger> or ones where we have an interest in tighlty following development
[17:55] <apachelogger> yofel: in the long run, yes
[17:56] <apachelogger> however since there is so little change in the other sources the gain is also smaller
[17:56] <yofel> well, I get your point about the main packages
[17:56] <shadeslayer> yay my krunner hanged
[17:56] <shadeslayer> managed to get some backtrace : http://paste.kde.org/654812/
[17:57] <yofel> do you want to follow master? As the RC's are branched off and I'm not sure if it makes sense to constantly import all the stable branches
[17:58] <apachelogger> I'd simply follow master
[17:58] <apachelogger> from rc to final there is also no significant change that would benefit from incremental updates
[17:58] <apachelogger> (or at least there should not be ';))
[18:00] <yofel> apachelogger: how would you handle the branches then? As we'll have to branch our packaging if we do that - or stop using bzr with RC which I don't really want to use
[18:00] <apachelogger> branch
[18:00] <yofel> or we simply start using branches in general for every kde release (which'll be a lot)
[18:00] <apachelogger> we should branch more anyway
[18:00] <apachelogger> yofel: yeah, a lot, but that is entirely bazaars fault :S
[18:01] <yofel> ack
[18:01] <apachelogger> iff launchpad and bazaar supported that workflow better I'd also simply daily build everything we have and branch for each release
[18:02] <apachelogger> but as it stand we'd then have 5k branches after 1 year ^^
[18:02] <yofel> who cares? ^^
[18:04] <apachelogger> makes stuff hard to use for newcomers etc.
[18:04] <yofel> well, most of us already use kbzr to check stuff out, we can just extend that
[18:05] <apachelogger> yeah, of *us*
[18:05] <apachelogger> ^^
[18:05] <yofel> others are supposed to read the Vcs links in the packages...
[18:05] <apachelogger> so we need to change those all the time
[18:05] <apachelogger> also merging between bazaar branches does not give me joy... so much easier with git :P
[18:05] <yofel> script it
[18:05] <yofel> true
[18:08] <yofel> apachelogger: did you have a plan for managing the failure notifications? Other than adding yet another team and using it's ML to handle that
[18:09] <yofel> also remind me to look at the notifications for ~kubuntu-packagers. Even if CIA is dead I would still like to know when people change something...
[18:19] <shadeslayer> there's this alternate site for CIA
[18:20] <yofel> kudos to kevin for analyzing kde bug 310486
[18:24] <kubotu> ::workspace-bugs:: [1103591] package libkworkspace4abi1 4:4.8.5-0ubuntu0.2 failed to install/upgrade: ErrorMessage: sub... @ https://bugs.launchpad.net/bugs/1103591 (by Stefano P.)
[18:31] <shadeslayer> ooohhh
[18:31] <shadeslayer> yofel: almost there
[18:31] <shadeslayer> http://paste.kde.org/654836/
[18:32] <shadeslayer> though for some reason it just stops after kded4
[19:01] <shadeslayer> ...
[19:03] <soee> good evening
[19:43] <shadeslayer> apachelogger: halp http://paste.kde.org/654890/
[19:43] <shadeslayer> yofel: ^
[19:43] <shadeslayer> it just hangs at line 15
[19:43] <shadeslayer> nothing happens after that
[19:58] <shadeslayer> infact it says kded already loaded
[20:00] <shadeslayer> http://paste.kde.org/654920/
[20:01] <shadeslayer> I'll let it run longer and see what happens
[20:08] <jessie|work> What version of kio-mtp is in the beta repos? Is it up to date with the git repo?
[20:09] <shadeslayer> errr which repo?
[20:10]  * jessie|work shrugs
[20:10] <jessie|work> The official one? That has active development?
[20:10] <shadeslayer> raring?
[20:10] <shadeslayer> !info kio-mtp raring
[20:10] <jessie|work> http://anongit.kde.org/kio-mtp <- That one
[20:11] <shadeslayer> jessie|work: what version of Kubuntu are *you* running?
[20:11] <jessie|work> I'm on 12.10 with 4.9.97.
[20:11] <shadeslayer> I see
[20:12] <shadeslayer> we have https://launchpad.net/~kubuntu-ppa/+archive/experimental
[20:13] <shadeslayer> with a git snapshot from 4th of this month
[20:13] <shadeslayer> yofel: lololo http://paste.kde.org/654926/
[20:13] <shadeslayer> though it's still on the 7th test
[20:14] <yofel> shadeslayer++
[20:14] <shadeslayer> yofel: it's hilarious btw
[20:14] <shadeslayer> you just need to override it to run with xvfb-run
[20:14] <shadeslayer> and it starts kded4 et all
[20:14] <yofel> *headdesk*
[20:14] <shadeslayer> :P
[20:16] <shadeslayer> yofel: which test started kompare?
[20:16] <yofel> first
[20:16] <shadeslayer> odd then
[20:17] <shadeslayer> maybe the last test just takes a shit ton of time
[20:17] <yofel> not really, that's the one that's not finished
[20:17] <shadeslayer> oh
[20:18] <shadeslayer> maybe ask kolab guys how we can run it
[20:19] <jessie|work> Let's try that again.
[20:19] <jessie|work> !info libmtp raring
[20:19] <jessie|work> !info libmtp9 raring
[20:19] <yofel> !info libmtp9 raring
[20:19] <shadeslayer> heh
[20:20] <jussi> man I love how the menus are embedded in the decorations now :D
[20:20] <shadeslayer> hehe
[20:22] <shadeslayer> 7/8 Test #1: formattest .......................***Failed    3.19 sec
[20:22] <shadeslayer> :S
[20:22] <jussi> shadeslayer: btw, that issue I had? removed empathy and all is good :D
[20:22] <shadeslayer> lol
[20:22] <shadeslayer> don't install empathy with ktp
[20:22] <shadeslayer> it's causes mashups
[20:23] <yofel> please fix that on a packaging level...
[20:23] <yofel> well, "fix" it
[20:23] <jussi> yeah, Ive both kde and unity desktops here
[20:23] <jessie|work> I don't have empathy installed.
[20:23] <jussi> yeah, its a bit shit that it happens like that to be honest.
[20:24] <shadeslayer> yofel: it can't be
[20:24] <jessie|work> Nevermind, I was lost in the sauce for a moment there.
[20:24] <shadeslayer> well
[20:24] <yofel> yeah, nvm
[20:24] <shadeslayer> because it's perfectly fine to have both of them installed
[20:24] <shadeslayer> but runtime can cause issues
[20:24] <jessie|work> I was talking about kio-mtp and misread that as ktp or what not.
[20:24] <jussi> shadeslayer: cant you just put a nice "confilcts" in there?
[20:24] <shadeslayer> jussi: why? it's just the runtime that's problematic
[20:24] <jussi> oh
[20:25] <jussi> well whatever, its evil and removing it made it work :D
[20:26] <jussi> shadeslayer: I assume your password protected code hasnt made it into there yet?
[20:27] <shadeslayer> where? it
[20:27] <shadeslayer> it made it into master
[20:27] <shadeslayer> it'll be released with 0.6
[20:27] <jussi> shadeslayer: doesnt seem to work on the daily ppa thing installed here
[20:28] <shadeslayer> 0.o
[20:28]  * jussi updates and checks again
[20:28] <shadeslayer> make sure you logout && login
[20:40] <shadeslayer> yofel: I got it to work, but it requires introduction of magic numbers
[20:40] <shadeslayer> will show you once I do another rebuild
[20:40] <yofel> ... what?
[20:40] <shadeslayer> yeah
[20:42] <cyphermox> ScottK: hi
[20:42] <yofel> shadeslayer: anyway, you said that wrapping dh_auto_test in xvfb-run makes the tests build in general, right?
[20:43] <yofel> should we do that in neon?
[20:43] <shadeslayer> yes it does
[20:43] <shadeslayer> maybe?
[20:43] <yofel> I'll give it some tries later
[20:43] <shadeslayer> it'll need kde-runtime and kdelibs-bin installed
[20:43] <shadeslayer> oh and kdelibs plugins
[20:44] <yofel> ok, kdelibs is a non-issue, kde-runtime we'll have to see
[20:46] <shadeslayer> yofel: http://paste.kde.org/654968/
[20:46] <shadeslayer> though I'm thinking of making a while loop
[20:46] <shadeslayer> to check the pidof kompare
[20:46] <shadeslayer> that's just a hack I threw together :P
[20:47] <yofel> shadeslayer: that immediately reminded me of http://thedailywtf.com/Articles/Too-Much-Sleep.aspx
[20:47] <yofel> though not as bad ^^
[20:48] <shadeslayer> hehe
[20:56] <shadeslayer> bah
[20:56] <shadeslayer> I don't know enough make :P
[21:00] <vassie> hello everyone, i'm interested in packaging an app that isn't in the repos for kubuntu
[21:00] <vassie> jonathan emailed me and said to stop by
[21:01] <vassie> https://bugs.launchpad.net/ubuntu/+bug/1103383
[21:01] <shadeslayer> yofel: any ideas how to make it check for a null pid again and again?
[21:02] <yofel> vassie: that would be Riddell probably :)
[21:02] <vassie> yofel: yes, didn't know if he was online
[21:03] <yofel> shadeslayer: null pid? as in whether pidof returns nothing?
[21:03] <shadeslayer> yep
[21:03] <shadeslayer> as in, keep polling till you get a pid
[21:04] <yofel> uh, assign the output to a variable and check if that's -z?
[21:05] <shadeslayer> sure, but how do I loop over that
[21:06] <yofel> the tricky part would be knowing when to stop...
[21:07] <shadeslayer> when it's not zero? :P
[21:07] <yofel> and how many kompare's do you need to kill?
[21:07] <shadeslayer> just the one
[21:08] <yofel> hm, I got more than one here, but if it's just one..
[21:10] <shadeslayer> oh
[21:11] <shadeslayer> I think I figured it out
[21:11] <Riddell> evening
[21:11] <Riddell> hi vassie, welcome along
[21:11] <yofel> usually it's
[21:11] <yofel> var=
[21:11] <yofel> while zero
[21:11] <yofel> set it
[21:11] <yofel> done
[21:11] <vassie> Riddell: hello
[21:13] <vassie> Riddell: i've been playing around with cantata and it compiles fine on 12.10, but i'm using checkinstall to build a deb, which i assume isn't very clean?
[21:18] <vassie> Riddell: i'm more than happy to help officially package it, or create my own ppa
[21:19] <shadeslayer> bah
[21:19] <shadeslayer> yofel: the build fails when doing pidof kompare
[21:19] <shadeslayer> because there's no compare
[21:20] <shadeslayer> I'll have to add -
[21:20] <yofel> was just about to ask how you run it, but if that works do it
[21:23] <shadeslayer> yofel: http://paste.kde.org/655016/
[21:26] <Riddell> vassie: awooga
[21:26] <Riddell> vassie: want me to take you through it now? will probably take about an hour
[21:27] <yofel> shadeslayer: line 15 should use the var, no?
[21:27] <shadeslayer> yes
[21:27] <shadeslayer> :P
[21:27] <yofel> bad shadeslayer testing whether I'm awake :P
[21:27] <shadeslayer> hehe
[21:27] <vassie> Riddell: that would be awesome, but i'm going to have to go offline soon, is it ok if i mail you?
[21:28] <shadeslayer> I think I should sleep now
[21:28] <Riddell> vassie: yeah we can find another time if that works better
[21:28] <shadeslayer> last rebuild
[21:28] <shadeslayer> yofel: I still think the loop is wrong btw
[21:28] <vassie> Riddell: thank you, i appreciate the help
[21:29] <yofel> s/$(komparePid)/$$komparePid/ maybe
[21:29] <kubotu> yofel: You did something wrong... Try s/you/me/ or tell me "help sed"
[21:29] <yofel> be quiet kubotu
[21:36] <shadeslayer> yofel: http://paste.kde.org/655028/
[21:37] <yofel> shadeslayer: oh, the loop needs to be on one line, so use \
[21:37] <shadeslayer> ahh
[21:37] <yofel> and move the - before the while I guess
[21:37] <shadeslayer> hmm
[21:39] <shadeslayer> wat
[21:39] <shadeslayer> kquitapp(26170): "Application kompare-6356 could not be found using service org.kde.kompare-6356 and path /MainApplication."
[21:39] <yofel> o.O
[22:03] <shadeslayer> yofel: odd
[22:04] <shadeslayer> very odd
[22:04] <shadeslayer> I have : root     11676  1.4  0.3<PHONE_NUMBER>2 pts/4    Sl   22:04   0:00 kompare -c /tmp/buildd/libkolab-0.4.1/obj-x86_64-linux-gnu/tests/expectedFile.h11607 /tmp/buildd/libkolab-0.4.1/obj-x86_64-linux-gnu/tests/convertedFile.L11607
[22:05] <shadeslayer> but let's say I do qdbus
[22:05] <yofel> qdbus on the right dbus session?
[22:05] <shadeslayer> dunn
[22:05] <shadeslayer> I get : Could not connect to D-Bus server: org.freedesktop.DBus.Error.Spawn.ExecFailed: //bin/dbus-launch terminated abnormally with the following error: No protocol specified
[22:05] <shadeslayer> Autolaunch error: X11 initialization failed.
[22:06] <yofel> o.O
[22:11] <shadeslayer> meh, I'm sleeping
[22:11] <shadeslayer> too tired for this
[22:12] <yofel> do so, good job getting so far :)
[22:12] <shadeslayer> yeah, maybe I can figure out the solution in my sleep xD
[22:12] <shadeslayer> though interesting how it worked once