[00:36] <prefrontal> are the KDE 4.4 beta packages available from the kubuntu ppa the same version of kde available in lucid alpha 2?
[00:40] <Lex79> RC2 for karmic is available here: https://launchpad.net/~kubuntu-ppa/+archive/beta/+packages
[00:41] <prefrontal> ok i have that. thanks
[01:03] <ScottK> Is the kdepim-runtime build-dep on libakonadi-dev wrong or is someone packaging 1.3?
[01:06] <Lex79> ScottK: I did 1.30, not uploaded yet?
[01:07] <ScottK> Lex79: It's not.  Where is it?
[01:07] <Lex79> ninja
[01:07] <ScottK> OK.  Thanks.
[01:08] <Lex79> ScottK: eigen2 needs upload too
[01:08] <ScottK> Lex79: Also in ninja?
[01:08] <Lex79> yes
[01:10] <prefrontal> part of our application is not redrawing in Karmic with KDE SC 4.4 RC2. it's been this way since RC1 as well. video: http://grey.colorado.edu/emergent/index.php/ToolsNotRedrawing
[01:10] <prefrontal> our app also links against Qt 4.6
[01:10] <prefrontal> and works perfect in Jaunty w/ 4.6
[01:13] <ScottK> Lex79: Done.
[01:13] <Lex79> good
[01:18] <ScottK> eigen2 is failing due to some latex stuff.
[01:19] <Lex79> I saw
[01:19] <Lex79> :(
[01:19] <ScottK> prefrontal: What kind of graphics?
[01:19] <prefrontal> ScottK, sorry?
[01:20] <prefrontal> Additionally, Kwin crashes when using the grouping feature with our application. I created a video of this in action with the backtrace as well: http://grey.colorado.edu/emergent/index.php/KDEGroupingCrash
[01:20] <prefrontal> ScottK, they are buttons with text
[01:20] <ScottK> prefrontal: If you got a good backtrace, I would recommend filing a bug at bugs.kde.org.  We don't do much to kwin, so it should almost certainly something that needs to be reported upstream.
[01:21] <ScottK> prefrontal: Sorry, I mean like video card.  It looks X related perhaps.
[01:21] <prefrontal> 01:00.0 VGA compatible controller: nVidia Corporation G92 [GeForce 8800 GT] (rev a2)
[01:22] <prefrontal> i'm using packaged nvidia drivers. i'm not sure what version I have. I am fully up to date karmic
[01:22] <ScottK> All my stuff in Intel, so I know almost nothing about how that stuff works.  Sorry.
[01:23] <prefrontal> i just wonder what good filing a bug with kde will do. they won't be able to replicate the bug unless they install our software
[01:23] <ScottK> Did you try Karmic as released (Qt 4.5.2 and KDE 4.3.2/4)?
[01:23] <prefrontal> works fine with that
[01:23] <ScottK> prefrontal: If there's a good backtrace and it points at kwin, the backtrace is often enough.
[01:24] <ScottK> OK, well that would tend to exhonorate the video drivers.
[01:24] <prefrontal> yes i'm sure its new kde feats
[01:24] <prefrontal> if they aren't fixed by RC3 i will file bug reports
[01:24] <prefrontal> thanks
[01:25] <ScottK> I think now is the time to file reports.
[01:25] <ScottK> If you can create a reduced test case to show the redraw problems that would probably really help.
[01:28] <dhillon-v10> ScottK: what do I need to be familiar with if I want to work on code-reviews: c++ and kde api right
[01:28] <dhillon-v10> *need to know
[01:29] <ScottK> dhillon-v10: I don't do that so I don't know.
[01:29] <dhillon-v10> ScottK: okay :)
[01:29] <dhillon-v10> ScottK: oh and I am following your advice, all my work is only in kde now :) thanks for that
[01:30] <Lex79> dhillon-v10: ask in #kde-devel maybe
[01:30] <dhillon-v10> Lex79: alright I was about to :)
[01:31] <Lex79> ;)
[01:31] <ScottK> Lex79: luatex being in Universe is the reason
[01:33] <Lex79> why? I've not touched the buil-deps of eigen, luatex was in Main?
[01:34] <Lex79> and now it's in Universe? or is it only "marked new"?
[01:35] <prefrontal> I hope to network upgrade to lucid, however, I get this python error when I run update-notifier-kde -u: RuntimeError: the sip module implements API v7.0 but the PyKDE4.kdecore module requires API v6.0
[01:36] <ScottK> Lex79: It looks like a new texlive-base dependency
[01:38] <prefrontal> is there another method of upgrading? what if I just sed -i 's/karmic/lucid/g' /etc/apt/sources.list /etc/lsb-release ?
[01:38] <prefrontal> (network upgrading..)
[01:40] <Lex79> prefrontal: you can change "karmic" to "lucid" in the entries of /etc/apt/sources.list and do apt-get update && apt-get dist-upgrade
[01:40] <prefrontal> thats it? ok, wish me luck
[01:40] <ScottK> prefrontal: That's one way.  The best way is sudo do-release-upgrade -d
[01:41] <prefrontal> lucid is a bit buggy in my virtual machine but i'm hoping that one or two bugs actually disappear
[01:41] <ScottK> That way the upgrade manager is involved and it is often programmed to handle special cases.
[01:41] <prefrontal> ok i'll use that
[01:41] <Lex79> ScottK: do we need another MIR maybe, I don't think eigen will build without that dependency
[01:41] <ScottK> Lex79: I'm looking at textlive-base right now.
[01:42] <Lex79> ok
[01:46] <ScottK> Looks like it needs a MIR.
[01:47] <prefrontal> can we start a betting pool as to whether my computer will reboot after upgrading to lucid? :)
[02:03] <verbalshadow> prefrontal: how will we know if you can't boot :)
[02:04] <prefrontal> i have a jaunty setup 1.5 seconds of chair rolling away ;) the install looks to be almost done
[02:47] <prefrontal> after rebooting into lucid kdm doesn't start. after starting it there is no panel and none of the repos pointed to in my sources.list exist
[02:48] <prefrontal> no interesting info in dmesg, kdm.log or xorg.0.log
[02:51] <ScottK> Do you have networking?
[02:51] <ScottK> My netbook has broadcom wireless and I lost the drivers on upgrade.
[02:51] <prefrontal> oh, good point. i do not have networking
[02:51] <prefrontal> hmm
[02:52] <prefrontal> whereas i'm plugged into ethernet and my nis login continues to work..
[02:52] <ScottK> You might have more luck with kdm if you remove usplash.
[02:58] <prefrontal> i nuked .kde and now it's looking good
[02:58] <prefrontal> still no networking
[02:58] <prefrontal> which is bizarre since my nfs mount is working
[02:58] <prefrontal> hmm...
[03:00] <prefrontal> i do have an ip address.. any idea?
[03:01] <ScottK> Not really.
[03:05] <prefrontal> i'm not the first :( https://bugs.launchpad.net/ubuntu/+bug/511478
[03:09] <ScottK> prefrontal: Can you ping stuff from a konsole session?
[03:10] <prefrontal> nope
[03:10] <prefrontal> it looks like this issue has been around since early december based on some forum threads
[03:10] <prefrontal> i've tried ifup/ifdown, and invoke-rc.d networking restart
[03:10] <ScottK> Odd.
[03:11] <prefrontal> also dhclient, and ifconfig eth0 up/down
[03:11] <prefrontal> i can't even get knetworkmanager to start, just bails with errors
[03:11] <ScottK> If you've got your networking configured via network-manager, ifup/down and restarting networking are no-ops
[03:11] <prefrontal> i don't actually, just tried it in desperation ;)
[03:12] <ScottK> I'd suggest asking on #ubuntu+1 since it doesn't sound Kubuntu specific.
[03:12] <prefrontal> k thakns
[03:14] <ScottK> All 16 buildds that can build fro Lucid are busy.  14 of the 16 are building Kubuntu stuff.
[03:14] <ScottK> ;-)
[03:20] <prefrontal> in networking under system settings there is a wired tab, and there is no wired connection listed there
[03:22] <ScottK> That's normal
[03:22] <ScottK> (IIRC)
[03:22]  * ScottK is on wireless right now.
[03:25] <prefrontal> the box has an ip address, nfs mounts work and I can ssh to it, yet it's "not connected" to the internet. color me confused.. i think that's enough for one evening :)
[03:25] <prefrontal> cya ScottK
[03:25] <ScottK> Cya.  Good luck
[05:10] <verbalshadow> prefrontal: it is normal to not have a listed connection in wired tab, you only need to have stuff there if you have a non-dhcp ( i.e. static ip or something similiar ) connection
[07:06] <nixternal> wow, just banged out a ton of doc stuff....I am so lucky, we have this guy Carl who is doing amazing editorial work for us and fixing all of the typos and info as we go along
[07:06] <nixternal> rocked out the first part in the "Filing a bug" documentation too....whicked insane, which pictures too :)
[07:20] <nixternal> neversfelde: thanks for the updated choqok dude, that seems to have fixed a bunch of issues \o/
[07:20]  * nixternal beds
[07:26] <hunger_t> is strigi suppossed to work in lucid at this time?
[08:23] <markey> neversfelde: got your new Choqok package, but, issues remain (seems even worse now)
[08:23] <markey> I'll do the downgrade dance
[08:45] <markey> ok, back on choqok_0.6.6
[08:45] <markey> your instructions worked, nice
[08:48] <markey> yep, that one works
[11:59] <Nightrose> hey folks :)  I want to install mediawiki and extension by hand but would like to have all deps installed by apt if possible
[12:00] <Nightrose> is there a command that does that handily?
[12:17] <Tm_T> no idea
[14:03] <ScottK> Riddell: I just tried to accept kdeplasma-addons from binary New and LP is timing out on me, so over to you to accept it ...
[14:10] <ScottK> Getting that out of New is all that stands between us and RC2 being done on i386 and amd64.
[14:30] <apachelogger> hm
[14:30] <apachelogger> why do we use a dated soprano version?
[14:35] <Riddell> ScottK: ok
[14:35] <Riddell> apachelogger: where's that?  lucid has 2.3.70 and http://soprano.sourceforge.net/ says that's the latest
[14:35] <apachelogger> oh
[14:35] <apachelogger> Riddell: I was talking karmic :)
[14:56] <Riddell> apachelogger: I'm pretty sure karmic shipped with what was available at the time
[14:56] <apachelogger> Riddell: in the ppa ;)
[15:06] <Riddell> also has 2.3.70 https://launchpad.net/~kubuntu-ppa/+archive/beta/+index?start=75&batch=75
[15:07] <apachelogger> ohm
[15:07] <apachelogger> no clue where I got the old one from then Oo
[15:27] <apachelogger> Riddell: please sync krename 4.0.3-1 from debian, last upload to ubuntu was a fakesync
[15:27] <ScottK-laptop> Riddell: Looks like luatex on armel missed promotion to Main and is causing eigen2 to fail.  Would you please promote it?
[15:28] <persia> Didn't lool say if FTBFS?
[15:29] <ScottK-laptop> Retry worked
[15:29] <persia> Ah.
[15:39] <ScottK-laptop> apachelogger: It's synced,but FTBFS.
[15:54] <shadeslayer> hi can i ask a launchpad PPA question about packaging here?
[16:10] <apachelogger> ScottK-laptop: meh
[16:10] <shadeslayer> apachelogger: btw good to have you back :)
[16:11] <apachelogger> oh I should have staied away, debian's patch policy causes headache already
[16:11] <shadeslayer> hehe :)
[16:12] <shadeslayer> apachelogger: will you revive project neon in the near future?
[16:13] <apachelogger> nope
[16:13] <shadeslayer> thats sad,just loved it :(
[16:54]  * jussi01 sighs at cdimage being so slw today... I juat want a daily that works! :(
[16:55] <jussi01> or even an alpha 2... has anyone got one of those in a fast location?
[17:01] <ScottK> Accepting worked on edge, so after the next publisher run, RC2 is done.
[17:05] <shadeslayer> hi i want to update a package in the repos but is out of date and does not work,can some one teach me how to do this?
[17:05] <ScottK> What package?
[17:05] <shadeslayer> ScottK: kopete-facebook
[17:06] <shadeslayer> ScottK: they released 0.1.5 whereas we have 0.1.4
[17:06] <ScottK> OK.  This is a good place for that.
[17:06] <shadeslayer> ScottK: well i talked to persia about this in motu
[17:06] <ScottK> I'm about to head out for a while, so I'm not available to help you now, but there are a number of people who might be able to help you here.
[17:07] <shadeslayer> and i wanted to help with packaging and thought its a small package which can do with some love
[17:07] <ScottK> That sounds good.
[17:07] <ScottK> Just be patient.
[17:08] <shadeslayer> sure :)
[17:08] <shadeslayer> i have all night :
[18:10] <shadeslayer> hi any ninjas around to teach me about packaging?
[18:17] <apachelogger> what do you need to know?
[18:21] <shadeslayer> apachelogger: well for starters theres a package kopete-facebook which needs updating,how do i update it in the repos?
[18:21] <apachelogger> you do not
[18:21] <apachelogger> you need special privledges to upload anything to the official repos ;)
[18:21] <shadeslayer> apachelogger: um why? the current one does not work with 4.4
[18:22] <shadeslayer> apachelogger: of course but what about the kubuntu backports PPA?
[18:22] <apachelogger> same thing, just less formal
[18:22] <shadeslayer> cant i give it to you guys and you upload it
[18:22] <ScottK> !sponsorship
[18:23] <ScottK> Nope, doesn't know that one
[18:23] <apachelogger> shadeslayer: https://wiki.ubuntu.com/PackagingGuide/Complete#Updating an Ubuntu Package
[18:24] <shadeslayer> oh and btw just so that you guys know plasma-scriptengine-python doesnt seem to work ( 4.3.95 ) and also the facebook widget :)
[18:24] <shadeslayer> apachelogger: i was reading that but persia said i needed to contact you guys to update a package already in the repo
[18:25] <persia> I thought it would be easier to work with the ninjas than just an arbitrary update.
[18:25] <ScottK> shadeslayer: plasma-scriptengine-python probably needs the new kdebindings which doesn't work yet.
[18:25] <ScottK> So that's not suprising.
[18:25] <persia> It's not so much a need, as that I thought it was the right set of people to whom to offer help.
[18:25] <shadeslayer> ScottK: ah..
[18:25] <apachelogger> shadeslayer: "in the repo" does not say a whole lot in the context of package uploads since the repo can be one of like 10 different ones ;)
[18:26] <ScottK> Gotta run.  Back later.
[18:26] <shadeslayer> apachelogger: i meant the proposed repo
[18:27] <apachelogger> still not precise enough ;)
[18:27] <apachelogger> shadeslayer: lets start with the kubuntu version ... for what version of kubuntu do you want to prepare an updated package?
[18:28] <shadeslayer> apachelogger: 9.10 Karmic Koala
[18:28] <apachelogger> ok, that already shrinks the amount of possible repos a lot :)
[18:29] <shadeslayer> apachelogger: hehe i already meant the current release,although i wasnt explicit enough :)
[18:29] <hunger> Is nepomuk/strigi supposed to work on lucid at this time?
[18:29] <apachelogger> shadeslayer: current can also be the one currently in development ;)
[18:30] <apachelogger> shadeslayer: so next question is ... is there a new version of kopete-facebook available from upstream?
[18:30] <shadeslayer> apachelogger: yeah :)
[18:30] <shadeslayer> apachelogger: yep 0.1.5
[18:30] <shadeslayer> we currently have : 0.1.4-0ubuntu1.1
[18:30] <apachelogger> hunger: nope, from what I have seen earlier we do not build soprano with virtuoso backend yet
[18:31] <Lex79> yes we build, but still not works :)
[18:31] <apachelogger> oh, ok
[18:32]  * apachelogger is wondering where the pkg is
[18:32] <apachelogger> shadeslayer: perfect, so you want to provide 0.1.5 to karmic users
[18:32] <shadeslayer> apachelogger: yes!
[18:32] <apachelogger> now I also know what you meant with "proposed repo" ;)
[18:32] <apachelogger> however, it's not that simple
[18:33] <shadeslayer> apachelogger: ok lets go slowly then
[18:33] <apachelogger> shadeslayer: karmic-proposed is the testing part of karmic-updates, those are technically two different repos, proposed is not active by default, updates however is
[18:34] <shadeslayer> apachelogger: yes,but i want provide this as a update along with the KDE 4.4 as a beta backport.so whoever updates to 4.4 gets a working kopete-facebook
[18:34] <apachelogger> well, yes, I'll get there...
[18:34] <shadeslayer> (0.1.4 doesnt work with 4.4 apparently)
[18:34] <shadeslayer> apachelogger: ok
[18:35] <apachelogger> first let me say one thing about proposed and updates though, to get anything in there it needs to meet a very precise set of requirements to ensure minimum risk of regression and breakage for the average user
[18:36] <apachelogger> so to get anything in there you would have to do a stable release update (short: SRU)
[18:36] <apachelogger> !sru
[18:36] <apachelogger> long story short, the jump from 0.1.4 to .5 does not qualify for such a SRU ;)
[18:36] <shadeslayer> apachelogger: you mean like point release?
[18:36] <shadeslayer> like from 0.1.4 to 0.1.5
[18:36] <apachelogger> shadeslayer: even more restricted!
[18:36] <apachelogger> ultimately one update to proposed/updates holds exactly one change to resolve one very particular issue
[18:37] <apachelogger> the more changes, the higher the risk of regression, the lower the likelyhood it gets accepted for upload to proposed to begin with
[18:37] <hunger> apachelogger: I do have virtuoso backends installed with kdebase-runtime or so.
[18:37] <shadeslayer> apachelogger: ah i get it.. like it says, even one line changes can cause regressions
[18:38] <apachelogger> hunger: yeah, Lex79 says it is just not working, for whatever reason :)
[18:38] <apachelogger> hunger: shouldn't be too long now I suppose
[18:38] <hunger> apachelogger: Actually it seems to kind of work after installing all virtuoso packages, even though the nepomuk config thingy says it does not.
[18:39] <apachelogger> shadeslayer: exactly, so we can not squeeze 0.1.5 into proposed/updates, because there probably were far too many changes to assure that there are no regressions or new bugs etc.
[18:39] <hunger> apachelogger: I do see search results that must have come from the indexer... and the index grew quite a lot:-)
[18:39] <apachelogger> shadeslayer: instead, when providing such updates as from 0.1.4 to 0.1.5, we utilize another repo, karmic-backports
[18:39] <shadeslayer> apachelogger: ok
[18:40] <hunger> apachelogger: The nepomuk systray thingy does not see it and claims the indexer is idle, on the command line I do get messages indicating that it does index though.
[18:41] <apachelogger> shadeslayer: basically anything that is in lucid qualifies for karmic-backports (as long as it is some super important library that should not be changed or something), so when I say everything I really mean most user applications, and even then it is practise to ensure that there is little to no regression at the very least
[18:41] <shadeslayer> apachelogger: ah..
[18:42] <apachelogger> karmic-backports does not contain KDE 4.4 though, so what you really want is to ship the update via the PPA that contains KDE 4.4
[18:43] <shadeslayer> apachelogger: i was just typing that question... you read my mind :o
[18:43] <apachelogger> so, that is your motivation
[18:43] <apachelogger> BUT ;)
[18:43] <shadeslayer> theres always one isnt there
[18:43] <apachelogger> 0.1.5 might be interesting to lucid users and might also be interesting to karmic users that do not use KDE 4.4
[18:44] <apachelogger> so in theory what you would want to do is prepare 3 package updates, one going to lucid, one going to karmic-proposed and one going to the PPA with KDE 4.4
[18:44] <shadeslayer> apachelogger: yeah,but kopete-facebook works *only* with 4.3.2 and not the later bug fix releases
[18:46] <shadeslayer> apachelogger: shouldnt the lucid package already be prepared?
[18:46] <apachelogger> that is the question we have to answer first
[18:47] <shadeslayer> apachelogger: should i check ?
[18:47] <apachelogger> shadeslayer: you could for example enter upkg:kopete-facebook into krunner
[18:48] <apachelogger> that should take you to packages.ubuntu.com
[18:48] <apachelogger> or ask ubottu
[18:48] <apachelogger> !info kopete-facebook lucid
[18:48] <shadeslayer> thats new :)
[18:48] <apachelogger> or look it up on launchpad
[18:48] <shadeslayer> apparently yes
[18:48] <shadeslayer> i guess the +git is the git patches applied?
[18:49] <apachelogger> almost
[18:49] <apachelogger> +git means that it is a snapshot from git
[18:49] <apachelogger> there is also +svn and +bzr etc.
[18:49] <shadeslayer> and they mean the same thing
[18:49] <apachelogger> right, they just indiciate which kind of version control system the snapshot comes from
[18:49] <shadeslayer> right?
[18:50] <shadeslayer> yeah i just learned to use bazaar a few days ago :P
[18:50] <shadeslayer> (the ubuntu-manual thing)
[18:50] <apachelogger> usually when just one or a couple of patches where applied this is not reflected in the package version itself, so you find those git and svn and bzr stuff almost exclusively with snapshots
[18:50] <apachelogger> cool :)
[18:51] <shadeslayer> apachelogger: so this means that alot of patches were applied from that git snapshot?
[18:51] <apachelogger> in this case it means no patches were applied at all
[18:52] <shadeslayer> apachelogger: eh? then why the +git?
[18:52] <apachelogger> someone took the complete code from the git repository on 2009-12-26
[18:52] <apachelogger> and turned it into a source package
[18:52] <shadeslayer> ah...
[18:52] <shadeslayer> apachelogger: so its kinda like 0.1.4.x
[18:53] <apachelogger> not exactly
[18:53] <shadeslayer> apachelogger: why?
[18:53] <apachelogger> it is something between 0.1.4 and 0.1.5
[18:53] <shadeslayer> thats what i said :P
[18:53] <apachelogger> no
[18:53] <apachelogger> 0.1.4.x would be a minimal update to 0.1.4
[18:54] <shadeslayer> hmm well i actually meant what you said... difference of perception :)
[18:54] <shadeslayer> but yeah i get what you mean
[18:54] <apachelogger> yeah, though I would not say 0.1.4.x but 0.1.4+git20091226 ;)
[18:54] <shadeslayer> hehe :)
[18:55] <apachelogger> which is really what it is, it is 0.1.4 at the time of 2009-12-26 from git
[18:55] <apachelogger> (technically it was not 0.1.5 by then)
[18:55] <apachelogger> anyhow
[18:55] <shadeslayer> yeah
[18:55] <apachelogger> so indeed we need to update the lucid package as well
[18:55] <shadeslayer> yep
[18:55] <shadeslayer> apachelogger: and for that ill need special permissions
[18:56] <apachelogger> no, for the _upload_ you need
[18:56] <shadeslayer> which cant be given to anybody
[18:56] <apachelogger> not for the update
[18:56] <shadeslayer> yeah thats what i meant,for the upload
[18:56] <shadeslayer> of course i can just make the package and give it to you guys
[18:56] <apachelogger> exactly
[18:57] <shadeslayer> which is much easier..
[18:57] <apachelogger> shadeslayer: https://wiki.ubuntu.com/SponsorshipProcess deocumentes the whole sponsorship process
[18:58] <apachelogger> after all that theory I suppose you want to get started on updating the lucid package? ;)
[18:58] <shadeslayer> yeah!
[18:58] <shadeslayer> ive already downloaded the 0.1.5 source :P
[18:58] <apachelogger> though I'd like to outline the plan: update the lucid package -> backport that package to karmic-backports -> upload a PPA version of the backport to the PPA with KDE 4.4
[18:59] <shadeslayer> ok,so we work top down
[19:00] <apachelogger> shadeslayer: do you have some how to guide on updating a package?
[19:01] <shadeslayer> apachelogger: me?
[19:01] <apachelogger> well, something you can follow, or do you need me to hold your hand? ;)
[19:01] <shadeslayer> apachelogger: well i was reading https://wiki.ubuntu.com/PackagingGuide/Complete#Packaging from Scratch and got till dh_make
[19:02] <apachelogger> well, that is not helping much here ;)
[19:02] <shadeslayer> and then editing the changelog
[19:02] <apachelogger> shadeslayer: got the URL of the 0.1.5 source?
[19:02] <shadeslayer> yeah one sec
[19:02] <shadeslayer> apachelogger: http://github.com/dmacvicar/kopete-facebook/downloads
[19:05] <apachelogger> thx
[19:05] <apachelogger> so
[19:05] <apachelogger> shadeslayer: first things first: getting the current lucid package
[19:05] <apachelogger> open a terminal and go to some nice directory where you want to do you work
[19:06] <shadeslayer> apachelogger: /home/shadeslayer/packaging << done
[19:06] <apachelogger> I recommend that you create a subdirectory in there ;)
[19:06] <apachelogger> otherwise it gets messy after some time
[19:06] <apachelogger> mkdir kopete-facebook; cd kopete-facebook
[19:06] <shadeslayer> hehe... ok
[19:06] <apachelogger> for example
[19:07] <shadeslayer> apachelogger: done and untarred
[19:07] <apachelogger> then you pull the current source package from launchpad
[19:07] <apachelogger> pull-lp-source kopete-facebook lucid
[19:08] <shadeslayer> apachelogger: where?
[19:08] <shadeslayer> in the kopete-facebook dir?
[19:08] <apachelogger> yes
[19:08] <apachelogger> ...some guides suggest to use apt-get source, that however does not always do what you might expect it to do, so pull-lp-source is the tool of choice for ubuntu
[19:08] <shadeslayer> ok one sec
[19:09] <apachelogger> once pull-lp-source is done it should have extracted the package already. my dir now looks like this: http://paste.ubuntu.com/362122/
[19:10] <shadeslayer> apparently kubuntu-dev-tools doesnt cut it :P
[19:10] <apachelogger> shadeslayer: it ships with ubuntu-dev-tools
[19:11] <shadeslayer> E: No credentials found for 'ubuntu-dev-tools', please see the manage-credentials manpage for help on how to create one for this consumer.
[19:11] <apachelogger> ewww
[19:11] <apachelogger> shadeslayer: manage-credentials create -c ubuntu-dev-tools -l 2
[19:12] <ScottK> The version in Lucid doesn't require that if you don't specify the release (it defaults to Lucid_
[19:12] <ScottK> _/)
[19:12] <apachelogger> that should fire up your browser with launchpad asking you to grant privledges to ubuntu-dev-tools
[19:12] <shadeslayer> yep
[19:12] <apachelogger> "read all public data" should be fine I suppose
[19:13] <shadeslayer> um no such option :P
[19:13] <apachelogger> well, something that sounds like that :P
[19:13] <shadeslayer> read non private data?
[19:13] <apachelogger> yes
[19:14] <shadeslayer> done and pressed enter
[19:14] <apachelogger> shadeslayer: does pull-lp-source work now?
[19:14] <shadeslayer> well my internet connection is working like crazy right now
[19:14] <shadeslayer> it didnt finish
[19:15] <apachelogger> "it"?
[19:15] <shadeslayer> manage-credentials
[19:15] <apachelogger> oh
[19:15] <apachelogger> you need to close the browser and press enter I think
[19:15] <shadeslayer> ok pulling now
[19:15] <shadeslayer> yeah did that :)
[19:16] <shadeslayer> apachelogger: its downloading tarballs
[19:16] <shadeslayer> done
[19:16] <apachelogger> ScottK: will revu ever get cleaned up again?
[19:17] <shadeslayer> apachelogger: http://pastebin.com/f1796f83c
[19:17] <apachelogger> shadeslayer: perfect, kopete-facebook-0.1.4+git20091226 will now contain the old debian directory
[19:17] <apachelogger> "old"
[19:18] <shadeslayer> ok i should untar it first right
[19:18] <apachelogger> shadeslayer: so  just copy that over to the new source directory
[19:18] <apachelogger> shadeslayer: already untared ;)
[19:18] <apachelogger> pull-lp-source took care of that
[19:18] <apachelogger> otherwise you would extract the source with ... dpkg-source -x kopete-facebook_0.1.4+git20091226-0ubuntu1.dsc
[19:19] <apachelogger> dpkg-source will do some additional magic over "regular" untaring
[19:19] <shadeslayer> ah,,
[19:20] <shadeslayer> apachelogger: done
[19:20] <shadeslayer> copied the debian directory
[19:21] <apachelogger> shadeslayer: ok, now you need to rename the new tarball
[19:21] <apachelogger> usually tarballs need to be named NAME_VERSION.orig.tar.gz
[19:21] <shadeslayer> ok
[19:21] <apachelogger> (there are cases where that is not the case, but for now just consider that the law ;))
[19:21] <shadeslayer> :D
[19:22] <shadeslayer> done :)
[19:22] <apachelogger> so dmacvicar-kopete-facebook-3376a46.tar.gz needs to be kopete-facebook_0.1.5.tar.gz
[19:22] <shadeslayer> apachelogger: yeah did that :)
[19:22] <apachelogger> okies
[19:22] <apachelogger> now you can enter the new source directory
[19:23] <shadeslayer> apachelogger: i just renamed the directory as orig.tar.gz accidently :P
[19:23] <shadeslayer> fixed
[19:24] <apachelogger> :)
[19:24] <apachelogger> the first thing you want to do in the new source is add a changelog entry
[19:24] <shadeslayer> in it..
[19:24] <shadeslayer> apachelogger: in the debian folder...
[19:24] <apachelogger> for that you can use the tool dch (short for debchange)
[19:25] <apachelogger> that needs to be invoked from the top source folder (the dir containing the debian one)
[19:25] <shadeslayer> apachelogger: like : dch -e rohan16garg@gmail.com ?
[19:25] <apachelogger> well
[19:25] <apachelogger> yes
[19:25] <apachelogger> and no
[19:25] <shadeslayer> eh?
[19:25] <apachelogger> that is quite unhandy
[19:25] <apachelogger> kate ~/.bashrc
[19:26] <shadeslayer> ok
[19:26] <apachelogger> at the very bottom you add
[19:26] <apachelogger> export DEBFULLNAME='Harald Sitter'
[19:26] <apachelogger> export DEBEMAIL='apachelogger@ubuntu.com'
[19:26] <apachelogger> well, with your data obviously ;)
[19:27] <shadeslayer> done
[19:27] <apachelogger> now
[19:27] <shadeslayer> now dch?
[19:27] <apachelogger> no
[19:27] <shadeslayer> ok
[19:27] <apachelogger> source ~/.bashrc
[19:28] <shadeslayer> reload the settings :) done already
[19:28] <apachelogger> that applies what you just did to the terminal (from now it will be applied to all new terminals right away though ;))
[19:28] <apachelogger> ah, ok :D
[19:28] <apachelogger> now
[19:28] <apachelogger> dch -v 0.1.5-0ubuntu1 -D lucid
[19:29] <shadeslayer> gives me a warning.... lucid not recognized
[19:29] <shadeslayer> and i press enter
[19:29] <apachelogger> that should fire up your preferred editor with a ready to go template entry for our new version targeting lucid with the contact data provided by DEBEMAIL AND DEBFULLNAME
[19:29] <apachelogger> shadeslayer: if you update your ubuntu-dev-tools with the version from karmic-backports the warning should disappear and you can drop the -D lucid ;)
[19:30] <shadeslayer> apachelogger: hmm i have karmic-backport afail
[19:30] <shadeslayer> *afaik
[19:30] <apachelogger> weird
[19:30] <apachelogger> ScottK: ^
[19:30] <shadeslayer> apachelogger: http://pastebin.com/f38e64f3c
[19:30] <apachelogger> http://aplg.kollide.net/images/osiris/snapshot064.png
[19:31] <apachelogger> !info ubuntu-dev-tools karmic-backports
[19:31] <apachelogger> oh
[19:31] <apachelogger> shadeslayer: apparently it does not want to do that ;)
[19:31] <apachelogger> anyway
[19:32] <apachelogger> shadeslayer: the standard entry for all new releases is "New upstream release"
[19:32] <shadeslayer> just after * ?
[19:32] <apachelogger> yep
[19:32] <apachelogger> like in the screenshot I posted
[19:32] <shadeslayer> ok
[19:33] <shadeslayer> done
[19:33] <apachelogger> then just save the change
[19:34] <shadeslayer> done :)
[19:35] <apachelogger> shadeslayer: now open debian/control in your preffered editor
[19:36] <shadeslayer> ok
[19:36] <shadeslayer> apachelogger: ^^
[19:37] <apachelogger> with every update you usually want to check whether all files in debian/ are updated
[19:37] <apachelogger> s/updated/up-to-date
[19:37] <shadeslayer> the build deps and stuff?
[19:38] <apachelogger> yes, though at this point we would have to guess whether they need additions or something
[19:38] <apachelogger> but, for example homepage and standards-version can be checked right away
[19:38] <apachelogger> I suppose the current homepage entry is not that up-to-date
[19:38] <apachelogger> maybe you can find a better one
[19:39] <apachelogger> and standards-version is the version of the debian policy this package is compatible with
[19:39] <apachelogger> most recent one is 3.8.3, so we should probably go with that http://www.debian.org/doc/debian-policy/
[19:39] <shadeslayer> ok
[19:39] <shadeslayer> one sec
[19:42] <shadeslayer> apachelogger: theres no blog entry for 0.1.5 but theres one for 0.1.5
[19:42] <shadeslayer> um 0.1.4
[19:43] <apachelogger> usually homepage should be something static
[19:43] <shadeslayer> or should i just add the the whole home page
[19:43] <apachelogger> I would add http://github.com/dmacvicar/kopete-facebook
[19:44] <apachelogger> it is the closest to a homepage there is IMHO
[19:44] <shadeslayer> ok
[19:44] <shadeslayer> and standards version to http://github.com/dmacvicar/kopete-facebook
[19:44] <shadeslayer> um
[19:44] <shadeslayer> 3.8.3
[19:45] <shadeslayer> ctrl+shift+C fails me :P
[19:45] <apachelogger> yes
[19:45] <shadeslayer> ok next?
[19:45] <apachelogger> once you are done with that you need to add those 2 changes to the changelog
[19:46] <apachelogger> you can either do that manually by opening the changelog in your editor
[19:46] <apachelogger> or by using dch -a
[19:46] <apachelogger> -a == append ;)
[19:46] <shadeslayer> dch again in root source dir
[19:46] <apachelogger> so you would add something like  * Changed homepage from blog to github  * Bumped Standards-Version from 3.8.1 to 3.8.3
[19:46] <ScottK> apachelogger: No idea about review.
[19:47] <apachelogger> shadeslayer: yes, dch only works from root source I think
[19:47] <ScottK> apachelogger: About a UDT backport, now that lp API support anonymous access to read services, I think pull-lp-source ought to be updated for that first.
[19:47] <apachelogger> shadeslayer: though -a really just adds such a bullet point *, which you can do just as well yourself in an editor ;)
[19:47] <shadeslayer> apachelogger: done
[19:48] <shadeslayer> apachelogger: hehe :)
[19:48] <apachelogger> ScottK: oh, I was wrong anyway, dch is part of devtools ^^
[19:48]  * apachelogger is incredibly silly today
[19:48] <ScottK> Yeah, devscripts
[19:48] <apachelogger> right
[19:49] <shadeslayer> apachelogger: ok done
[19:49] <apachelogger> shadeslayer: always carefully document what you do, it might save someone else's life in case you broke something and they are trying to repair it :)
[19:49] <apachelogger> shadeslayer: now we get to a tricky part
[19:49] <ScottK> The main time to be sure to use dch is when initially creating the entry.  There's a bunch of format that has to be just so and it handles it for you.
[19:49] <shadeslayer> apachelogger: ah ok
[19:50] <dhillon-v10> hi all, there's a file in the debian folder called ssl-cert.lintian-overrides when I am merging from Debian testing do I need to mention that file in the changelog or no
[19:50] <apachelogger> shadeslayer: this package uses patches and a rather confusing approach to applying those patches
[19:50] <ScottK> dhillon-v10: If it's a difference between the Ubuntu package and the Debian package, yes.
[19:50] <shadeslayer> apachelogger: btw i must tell you that im experiencing power outages
[19:50] <apachelogger> shadeslayer: usually packaging patches are stored in debian/patches
[19:51] <_Groo_> ppl whats wrong with dput uploads, im having timeouts and i cant send anything, the speed is below 2k uploads...!!!
[19:51] <dhillon-v10> ScottK: alright thanks :)
[19:51] <shadeslayer> apachelogger: so if you dont get a reply for more than 2 mins that means there was power/Internet outage :P
[19:51] <apachelogger> shadeslayer: ok, I'll not be worried should you get lost ;)
[19:51] <shadeslayer> :)
[19:51] <dhillon-v10> _Groo_: same happened to me yesterday
[19:51] <shadeslayer> apachelogger: ok so patches...
[19:51] <apachelogger> shadeslayer: so, now you can open all patches in there
[19:52] <_Groo_> i cant upload koffice, newer kde multimedia with PA, nothing :(
[19:52] <shadeslayer> apachelogger: um why do we need patches?
[19:52] <apachelogger> shadeslayer: to fix bugs ;)
[19:52] <apachelogger> shadeslayer: as stated on the SRU page, the smaller the change the lower the risk of regression
[19:53] <_Groo_> can i use http instead of ftp? or launchpad only accepts ftp?
[19:53] <shadeslayer> apachelogger: hehe.. but arent these patches applied upstream rather than at our end?
[19:53] <apachelogger> shadeslayer: yes, ultimately they are applied upstream, but sometimes upstream does not release the fixed version early enough for us to use it
[19:53] <shadeslayer> hmm
[19:53] <apachelogger> for example
[19:54] <apachelogger> 0.1.4 does not build against KDE 4.4
[19:54] <apachelogger> but upstream did not yet release 0.1.5
[19:54] <shadeslayer> ah..
[19:54] <apachelogger> and we are releasing a kubuntu version in like 2 weeks
[19:54] <dhillon-v10> ScottK: one more question: what about the translations, there's a po folder in there, and some of the templates have been modified, do I have to document each one of those templates, or can i just say translations updated
[19:54] <shadeslayer> apachelogger: ok
[19:55] <apachelogger> shadeslayer: at this point we most likely do not want to create a whole git snapshot, but rather isolate all changes necessary to make it build with KDE 4.4 and patch 0.1.4 with those changes, so that 0.1.4 builds
[19:55] <ScottK> dhillon-v10: We don't update translations in po files.  The odds are that the diff is all noise and can be dropped, but you need to check.
[19:55] <shadeslayer> ah so thats a 0.1.4 which was made to build with kubuntu
[19:55] <apachelogger> right
[19:56]  * shadeslayer starts to get the hang of things
[19:56] <apachelogger> shadeslayer: we call that cherry picking http://en.wikipedia.org/wiki/Cherry_picking#Software_configuration_management
[19:56] <dhillon-v10> ScottK: I had a similar feeling but when I opened the files there was different content like having different creating date, so can I just go ahead and drop the ubuntu changes
[19:56] <shadeslayer> hehe :)
[19:57] <apachelogger> if you understood bazaar's branch concept already it might help to think of packages as branches of the same software
[19:57] <ScottK> The creation dates are almost certainly noise.  You need to look for any real changes and not drop blindly.
[19:57] <dhillon-v10> ScottK: alright
[19:58] <apachelogger> shadeslayer: kopete-facebook in karmic is a different branch from the one in lucid, and the one in the PPA is also a different one, interchanging fixes between them is done via patches ... or sometimes a whole branch gets copied to replace another one (this usually helps for stuff that goes to karmic-backports)
[19:58] <shadeslayer> apachelogger: yeah i already know basic stuff about git and bzr
[19:58] <shadeslayer> branches of a tree
[19:59] <shadeslayer> and then you apply patches to merge the branch with the trunk :P
[19:59] <apachelogger> hm
[19:59] <shadeslayer> apachelogger: btw ill be packaging choqok too later :P
[19:59] <apachelogger> oh dear :D
[19:59] <apachelogger> well, lets move on
[19:59] <shadeslayer> on my own though :P
[20:00] <apachelogger> since I do not want to go into the patch system details just now...
[20:00] <apachelogger> what we need to do is drop all patches
[20:00] <shadeslayer> apachelogger: drop as in apply or drop as in not apply
[20:00] <apachelogger> they both originated from upstream (which, if it were properly documented, you could easily see in the debian/changelog)
[20:00] <apachelogger> shadeslayer: remove
[20:00] <apachelogger> rm -rf debian/patches
[20:01] <apachelogger> however, in this particular case we need to do a bit more
[20:01] <apachelogger> in debian rules remove line 5
[20:01] <apachelogger> include /usr/share/cdbs/1/rules/simple-patchsys.mk
[20:01] <shadeslayer> changelog  compat  control  copyright  rules
[20:01] <dhillon-v10> ScottK: here: # translation of ssl-cert_1.0.22_nl.po to Dutch
[20:01] <dhillon-v10> #
[20:01] <dhillon-v10> #    Translators, if you are not familiar with the PO format, gettext
[20:01] <dhillon-v10> #    documentation is worth reading, especially sections dedicated to
[20:01] <dhillon-v10> #    this format, e.g. by running:
[20:01] <dhillon-v10> #         info -n '(gettext)PO Files'
[20:02] <dhillon-v10> #         info -n '(gettext)Header Entry'
[20:02] <apachelogger> in debian/control line 7 remove the build-dep "quilt, "
[20:02] <dhillon-v10> #
[20:02] <dhillon-v10> #    Some information specific to po-debconf are available at
[20:02] <shadeslayer> apachelogger: why did we do that?
[20:02] <dhillon-v10> #            /usr/share/doc/po-debconf/README-trans
[20:02] <dhillon-v10> #         or http://www.debian.org/intl/l10n/po-debconf/README-trans
[20:02] <dhillon-v10> #
[20:02] <dhillon-v10> #    Developers do not need to manually edit POT or PO files.
[20:02] <shadeslayer> dhillon-v10: 0_o
[20:02] <dhillon-v10> #
[20:02] <dhillon-v10> # Paul Gevers <paul@climbing.nl>, 2008.
[20:02] <dhillon-v10> msgid ""
[20:02] <dhillon-v10> msgstr ""
[20:02] <dhillon-v10> "Project-Id-Version: ssl-cert_1.0.22_nl\n"
[20:02] <dhillon-v10> "Report-Msgid-Bugs-To: ssl-cert@packages.debian.org\n"
[20:02] <dhillon-v10> "POT-Creation-Date: 2009-01-16 00:59+0000\n"
[20:02] <apachelogger> I wonder if the whole po is coming through now :D
[20:02] <dhillon-v10> "PO-Revision-Date: 2008-09-23 21:38-0500\n"
[20:02] <ScottK> !pastebin | dhillon-v10
[20:02] <dhillon-v10> "Last-Translator: Paul Gevers <paul@climbing.nl>\n"
[20:03] <Tm_T> apachelogger: you don't see him flooding anymore, right?
[20:03] <apachelogger> shadeslayer: I recommend you read up on debian/rules and makefiles, it is a bit of a complicated topic, bascially that include line pulled in a macro that took care of applying and deapplying the patches in the build process
[20:04] <shadeslayer> ah
[20:04] <apachelogger> shadeslayer: the quilt build-dep in debian/control is a very sophisticated patch system
[20:04] <shadeslayer> ok
[20:04] <shadeslayer> so basically we need to remove the parts which were supposed to apply those patches
[20:04] <apachelogger> right
[20:05] <apachelogger> technically we could leave this stuff around, but it is better to keep the package as clean as possible
[20:05] <apachelogger> which includes not referencing patch systems when there are no patches :)
[20:05] <Tm_T> should have done this rightaway, his client couldn't stop it, it seems
[20:05] <shadeslayer> apachelogger: of course
[20:05] <apachelogger> Tm_T: ;)
[20:06] <shadeslayer> apachelogger: something you said about line 7 , got lost in the flood there :)
[20:06] <apachelogger> shadeslayer: now, dont forget to document this in the changelog
[20:06]  * shadeslayer like irssi... asks for confirmation
[20:06] <apachelogger> * Removed all patches and patch system (all applied upstream)
[20:06] <apachelogger> for example
[20:06] <shadeslayer> apachelogger: ah of course the change log
[20:07] <apachelogger> shadeslayer: ultimately you would mention the patches' names ;)
[20:07] <apachelogger> * Removed all patches kubuntu_01_offline_detection.diff and kubuntu_02_protocol_changes.diff (all
[20:07] <apachelogger> eh
[20:08] <shadeslayer> done :)
[20:08] <shadeslayer> apachelogger: ah even the ones removed?
[20:08] <apachelogger> * Removed all patches (all applied upstream)
[20:08] <apachelogger>   - kubuntu_01_offline_detection.diff
[20:08] <apachelogger>   - kubuntu_02_protocol_changes.diff
[20:08] <shadeslayer> oh like that
[20:08] <shadeslayer> but i already deleted the patches directory
[20:09] <apachelogger> yeah, I should have told you before ;)
[20:09] <shadeslayer> :P
[20:09] <apachelogger> well, next time you know, plus it is bonus anyway
[20:09] <shadeslayer> ok ill go through the old one
[20:09] <apachelogger> shadeslayer: this stuff can help people who try to reproduce what happened via the changelog and by mentioning the names it is easier to search
[20:10] <apachelogger> so I search for all appearaneces of that kubuntu_02 patch and find out that Bruno Bigras added it and that you removed it again because it was applied upstream
[20:10] <shadeslayer> ok i understand
[20:10] <shadeslayer> ah
[20:11] <apachelogger> ...and maybe you were wrong in removing the patch, and I could go poke you in the eye :P...
[20:11] <Tm_T> dhillon-v10: welcome back and sorry again for forgetting ban on
[20:11] <shadeslayer> sure :)
[20:11] <dhillon-v10> Tm_T: np, I should be the one apologizing :D
[20:11] <shadeslayer> apachelogger: ill wear shades next time im around you
[20:13] <shadeslayer> apachelogger: what next?
[20:13] <apachelogger> I think you are ready to testbuild the package
[20:13] <shadeslayer> :o
[20:13] <apachelogger> debuild -S -sa
[20:13]  * shadeslayer jumps up and down with joy
[20:13] <apachelogger> will create a source package
[20:14] <apachelogger> (hopefully)
[20:14] <shadeslayer> apachelogger: in the source dir?
[20:14] <apachelogger> yes
[20:14] <shadeslayer> or the one above it?
[20:15] <shadeslayer> apachelogger: http://pastebin.com/f4cd2c97b
[20:16] <shadeslayer> and the last two lines : debuild: fatal error at line 1255:
[20:16] <shadeslayer> running debsign failed
[20:16] <shadeslayer> i think line 1255 means 1255 of LINE:   -kubuntu_02_protocol_changes.diff
[20:16] <apachelogger> shadeslayer: please paste your debian/changelog
[20:16] <apachelogger> shadeslayer: do you have a GPG key?
[20:17] <shadeslayer> apachelogger: i have a ssh-rsa key if thats what you mean
[20:17] <apachelogger> no
[20:17] <apachelogger> SSH != GPG :)
[20:17] <shadeslayer> :)
[20:17] <shadeslayer> how do i get one?
[20:17] <apachelogger> shadeslayer: https://help.ubuntu.com/community/GnuPrivacyGuardHowto
[20:17] <shadeslayer> apachelogger: http://pastebin.com/f6b9e1e4c
[20:18] <shadeslayer> downloading
[20:19] <apachelogger> the lines before the patch file names have tabulators
[20:19] <shadeslayer> apachelogger: ah thats why?
[20:19] <shadeslayer> did i have to use space?
[20:19] <apachelogger> yes
[20:19] <shadeslayer> ><
[20:19] <apachelogger> usually you should stick to spaces, only debian/rules should contain tabulators
[20:20] <apachelogger> shadeslayer: most editors can be configured to add a certain amount of white spaces when the tabulator key is used
[20:20] <shadeslayer> apachelogger: i used nano...
[20:21] <shadeslayer> apachelogger: do i generate a key before building the package?
[20:21] <apachelogger> yes
[20:21] <apachelogger> you need to sign the source with your key
[20:21] <shadeslayer> ok one sec
[20:21] <shadeslayer> first i need to generate one right
[20:22] <shadeslayer> RSA algorithm?
[20:23] <apachelogger> shadeslayer: yes
[20:23] <apachelogger> just sticking with the defaults is a good idea :)
[20:24] <shadeslayer> :)
[20:24] <shadeslayer> generating
[20:26] <shadeslayer> um where is the key stored?
[20:26] <prefrontal> just upgraded to lucid. i have an ip address, my nfs mount is working and I can ssh to this machine, but it is not connected to the internet. ping doesn't work for example
[20:26] <apachelogger> shadeslayer: ~/.gnupg
[20:27] <prefrontal> this is the output of `route' http://pastebin.ca/raw/1764349  and this is the output of route on the jaunty machine next to it which is working: http://pastebin.ca/raw/1764350
[20:27] <shadeslayer> apachelogger: private keys?
[20:27] <apachelogger> shadeslayer: you probably should read on about gpg on wikipedia ;)
[20:27] <apachelogger> you have a private and a public key
[20:28] <apachelogger> the private key is used to sign and encrypt stuff
[20:28] <shadeslayer> ah ok
[20:28] <apachelogger> the public key is used to proof the signature
[20:29] <shadeslayer> ah ok
[20:29] <shadeslayer> so its my sign that its actually by me
[20:29] <shadeslayer> and thats why its called a signature :P
[20:31] <apachelogger> right ;)
[20:32] <shadeslayer> ok now what?
[20:33] <apachelogger> shadeslayer: that is what your changelog should look like http://paste.ubuntu.com/362169/
[20:33] <apachelogger> shadeslayer: then you can run debuild -S -sa again
[20:33] <apachelogger> and hopefully it works now :D
[20:33]  * shadeslayer crosses fingers
[20:35] <shadeslayer> nope
[20:35] <shadeslayer> debsign: gpg error occurred!  Aborting....
[20:35] <shadeslayer> also : debuild: fatal error at line 1255:
[20:36] <apachelogger> more output please
[20:37] <shadeslayer> one sec
[20:37] <shadeslayer> i modified the changelog according to your pastebin
[20:38] <shadeslayer> apachelogger: http://paste.ubuntu.com/362178/
[20:38] <apachelogger> shadeslayer: what does ...  gpg -k "Rohan Garg" ... spit out
[20:39] <shadeslayer> apachelogger: http://pastebin.com/f620eb783
[20:40] <shadeslayer> i made 2 keys.. :P
[20:41] <shadeslayer> apachelogger: should i delete one
[20:41] <apachelogger> oha
[20:41] <apachelogger> shadeslayer: the comment is of the disturbing kind ;)
[20:42] <neversfelde> any known problems with kdm, I cannot login, kdm crashes.
[20:42] <shadeslayer> apachelogger: which one?
[20:42] <apachelogger> shadeslayer: you need to add that to your DEBFULLNAME and the debian/changelog
[20:42] <apachelogger> (shadeslayer)
[20:42] <apachelogger> (shadeslayer's key)
[20:42] <shadeslayer> apachelogger: ah should i remove it?
[20:42] <apachelogger> not sure if you can
[20:42] <apachelogger> though I suppose you can
[20:43] <shadeslayer> apachelogger: too vauge :P
[20:44] <apachelogger> well, I dont know ;P
[20:45] <shadeslayer> apachelogger: what do i do once again>
[20:45] <shadeslayer> apachelogger: i add what to DEBFULLNAME ?
[20:46] <apachelogger> the comment of the key you want to use
[20:46] <apachelogger> oha
[20:46] <apachelogger> gotta run
[20:46] <apachelogger> see you later
[20:46] <shadeslayer> apachelogger: ok so like export DEBFULLNAME='Rohan Garg'
[20:46] <shadeslayer> Rohan (shadeslayer's key)
[20:46] <shadeslayer> anyone else around here to help?
[20:47] <shadeslayer> apachelogger: thanks for the help though :)
[20:54] <shadeslayer> ScottK: any ideas?
[20:54] <shadeslayer> im like at the end of this thing :P
[20:55] <ScottK> It needs to match exactly.
[20:55] <shadeslayer> ScottK: ok but what do i put in the change log?
[20:56] <shadeslayer> ah found it
[20:56] <ScottK> shadeslayer: Sorry, I'm only barely here and don't have time to read all the backscroll.
[20:56] <ScottK> Good
[20:56] <shadeslayer> yesss
[20:56] <shadeslayer> ScottK: it saysSuccessfully signed dsc and changes files
[20:56] <shadeslayer> ScottK: and i had run debuild -S -sa
[20:57] <ScottK> Good.
[20:57] <ScottK> Gotta run myself.
[20:57] <shadeslayer> ScottK: ok bye
[20:57] <shadeslayer> anyone else?
[20:58] <shadeslayer> i think im asking for too much :P
[21:05] <Riddell> I have no idea how to reply to this http://paste.ubuntu.com/362190/
[21:06] <shadeslayer> Riddell: um.. no one knows the reply to that
[21:07] <shadeslayer> not even linus himself :P
[21:07] <neversfelde> where did we disable the groups in category internet in kickoff the last time?
[21:14] <Trouble-> Does anyone know the (new?) method used to start either plasma-netbook or plasma-desktop? I have absolutely nothing in ~/.config/autostart. With KDE 4.4 RC1 and RC2 plasma-netbook does not start automatically. I don't have plasma-desktop installed, and I was using plasma-netbook previous to 4.4 RC1. New with RC2 I can no longer login - I'm just dropped back to kdm. I was about to look at this, but wondered if the
[21:14] <Trouble-> two problems may be linked.
[21:15] <shadeslayer> Trouble-: that happened to me too... i made a pre-kde bash script
[21:16] <Trouble-> That's good to know! After searching Google I assumed I was the only person with the problem :)
[21:18] <shadeslayer> Trouble-: although the problem disappeared in RC 2
[21:19] <Trouble-> Haha
[21:19] <Trouble-> Oh
[21:19] <Trouble-> My problem got worse with RC2 hehe
[21:20] <Trouble-> Now I have to 'startx' from a terminal :)
[21:20] <shadeslayer> Trouble-: that wont give you shut down and reboot options :P
[21:20] <Trouble-> AND then run plasma-netbook manually ;-)
[21:20] <shadeslayer> Trouble-: do sudo kdm..
[21:20] <shadeslayer> Trouble-: kdm doesnt start up automatically?
[21:20] <Trouble-> Yea, I gotta logout, then shutdown from the terminal too :)
[21:21] <shadeslayer> Trouble-: put this in rc.local : kdm
[21:21] <Trouble-> kdm starts fine. When I login, KDE starts to start, but then I get dropped back to kdm :-s
[21:21] <Trouble-> Need to work out what it's doing, or rather not doing
[21:21] <shadeslayer> hehe
[21:21] <shadeslayer> Trouble-: check the logs
[21:32] <ScottK> Trouble-: Does it work on the 2nd try?  If so, I believe this is known.
[21:34] <prefrontal> after reboot in lucid i have to run ifdown eth0 && ifup eth0 && start kdm
[21:35] <shadeslayer> anyone know how to build a .deb?
[21:35] <mass-destruction> shadeslayer: pbuilder :)
[21:36] <shadeslayer> mass-destruction: well the last command apachelogger gave me was : debuild -S -sa
[21:36] <mass-destruction> shadeslayer: that too :)
[21:36] <shadeslayer> mass-destruction: but i dont see any .deb ?
[21:37] <mass-destruction> shadeslayer: move a directory up, it should be there
[21:37] <shadeslayer> i want my binary files :P
[21:37] <shadeslayer> mass-destruction: theres a .build fine
[21:37] <shadeslayer> *file
[21:38] <shadeslayer> mass-destruction: http://pastebin.com/f42d80cdc
[21:39] <mass-destruction> shadeslayer: just give me a sec.
[21:39] <shadeslayer> mass-destruction: take 2
[21:39] <shadeslayer> :)
[21:39] <shadeslayer> but please do reply :P,its 3 AM here :D
[21:40] <mass-destruction> shadeslayer: alright go into you debian directory and then do this: dpkg-deb --build, let's see if that works
[21:40] <Trouble-> ScottK: 'fraid not. It's permanent :-s
[21:40] <Trouble-> shadeslayer: Just looking at kdm.log now.
[21:41] <Trouble-> I wonder if it's something to do with "[config/dbus] couldn't register object path"
[21:42] <shadeslayer> mass-destruction: dpkg-deb: --build needs a <directory> argument
[21:43] <mass-destruction> shadeslayer: I am sorry man, I build my files using pbuilder so I am not the best one to answer this question. Anyone else please help shadeslayer
[21:44] <shadeslayer> mass-destruction: ok no problem ill come back tommorow then :)
[22:34] <Zorael> kdm crashing at boot with a daily live image of Lucid. Known issue? kdm.log blames i915_dri and libglx. (http://pastebin.ubuntu.com/362222)
[22:37] <JontheEchidna> dunno, best file a report against xserver-xorg-video-intel
[22:37] <JontheEchidna> fwiw I updated yesterday and my lappy boots just fine
[22:38] <JontheEchidna> (it has an intel)
[22:47] <shadeslayer> apachelogger: my first build thanks to you :D : https://launchpad.net/~rohangarg/+archive/kde-extra/+packages
[23:17] <nixternal> the list for KOffice MIRs keep on growing
[23:21] <Riddell> nixternal: what's new?
[23:22] <nixternal> plotutils needs to be MIRd for pstoedit
[23:22] <crimsun> Riddell: / maco: is the usb symptom described on ubuntu-devel@ with or without karmic-updates enabled?
[23:22] <nixternal> just one there, so that is good
[23:22] <Riddell> crimsun: I think markey only had it after he updated with karmic-updates
[23:22] <nixternal> going through all of the bug reports and security stuff for the packages now, creating an annoyingly massive checklist
[23:23] <crimsun> Riddell: there's definitely a linux component to the uevent screwage
[23:24] <crimsun> cf. udevadm monitor --property