prefrontalare the KDE 4.4 beta packages available from the kubuntu ppa the same version of kde available in lucid alpha 2?00:36
Lex79RC2 for karmic is available here: https://launchpad.net/~kubuntu-ppa/+archive/beta/+packages00:40
prefrontalok i have that. thanks00:41
ScottKIs the kdepim-runtime build-dep on libakonadi-dev wrong or is someone packaging 1.3?01:03
Lex79ScottK: I did 1.30, not uploaded yet?01:06
ScottKLex79: It's not.  Where is it?01:07
ScottKOK.  Thanks.01:07
Lex79ScottK: eigen2 needs upload too01:08
ScottKLex79: Also in ninja?01:08
prefrontalpart 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/ToolsNotRedrawing01:10
prefrontalour app also links against Qt 4.601:10
prefrontaland works perfect in Jaunty w/ 4.601:10
ScottKLex79: Done.01:13
ScottKeigen2 is failing due to some latex stuff.01:18
Lex79I saw01:19
ScottKprefrontal: What kind of graphics?01:19
prefrontalScottK, sorry?01:19
prefrontalAdditionally, 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/KDEGroupingCrash01:20
prefrontalScottK, they are buttons with text01:20
ScottKprefrontal: 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:20
ScottKprefrontal: Sorry, I mean like video card.  It looks X related perhaps.01:21
prefrontal01:00.0 VGA compatible controller: nVidia Corporation G92 [GeForce 8800 GT] (rev a2)01:21
prefrontali'm using packaged nvidia drivers. i'm not sure what version I have. I am fully up to date karmic01:22
ScottKAll my stuff in Intel, so I know almost nothing about how that stuff works.  Sorry.01:22
prefrontali just wonder what good filing a bug with kde will do. they won't be able to replicate the bug unless they install our software01:23
ScottKDid you try Karmic as released (Qt 4.5.2 and KDE 4.3.2/4)?01:23
prefrontalworks fine with that01:23
ScottKprefrontal: If there's a good backtrace and it points at kwin, the backtrace is often enough.01:23
ScottKOK, well that would tend to exhonorate the video drivers.01:24
prefrontalyes i'm sure its new kde feats01:24
prefrontalif they aren't fixed by RC3 i will file bug reports01:24
ScottKI think now is the time to file reports.01:25
ScottKIf you can create a reduced test case to show the redraw problems that would probably really help.01:25
dhillon-v10ScottK: what do I need to be familiar with if I want to work on code-reviews: c++ and kde api right01:28
dhillon-v10*need to know01:28
ScottKdhillon-v10: I don't do that so I don't know.01:29
dhillon-v10ScottK: okay :)01:29
dhillon-v10ScottK: oh and I am following your advice, all my work is only in kde now :) thanks for that01:29
Lex79dhillon-v10: ask in #kde-devel maybe01:30
dhillon-v10Lex79: alright I was about to :)01:30
ScottKLex79: luatex being in Universe is the reason01:31
Lex79why? I've not touched the buil-deps of eigen, luatex was in Main?01:33
Lex79and now it's in Universe? or is it only "marked new"?01:34
prefrontalI 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.001:35
ScottKLex79: It looks like a new texlive-base dependency01:36
prefrontalis 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:38
Lex79prefrontal: you can change "karmic" to "lucid" in the entries of /etc/apt/sources.list and do apt-get update && apt-get dist-upgrade01:40
prefrontalthats it? ok, wish me luck01:40
ScottKprefrontal: That's one way.  The best way is sudo do-release-upgrade -d01:40
prefrontallucid is a bit buggy in my virtual machine but i'm hoping that one or two bugs actually disappear01:41
ScottKThat way the upgrade manager is involved and it is often programmed to handle special cases.01:41
prefrontalok i'll use that01:41
Lex79ScottK: do we need another MIR maybe, I don't think eigen will build without that dependency01:41
ScottKLex79: I'm looking at textlive-base right now.01:41
ScottKLooks like it needs a MIR.01:46
prefrontalcan we start a betting pool as to whether my computer will reboot after upgrading to lucid? :)01:47
verbalshadowprefrontal: how will we know if you can't boot :)02:03
prefrontali have a jaunty setup 1.5 seconds of chair rolling away ;) the install looks to be almost done02:04
prefrontalafter 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 exist02:47
prefrontalno interesting info in dmesg, kdm.log or xorg.0.log02:48
ScottKDo you have networking?02:51
ScottKMy netbook has broadcom wireless and I lost the drivers on upgrade.02:51
prefrontaloh, good point. i do not have networking02:51
prefrontalwhereas i'm plugged into ethernet and my nis login continues to work..02:52
ScottKYou might have more luck with kdm if you remove usplash.02:52
prefrontali nuked .kde and now it's looking good02:58
prefrontalstill no networking02:58
prefrontalwhich is bizarre since my nfs mount is working02:58
prefrontali do have an ip address.. any idea?03:00
ScottKNot really.03:01
prefrontali'm not the first :( https://bugs.launchpad.net/ubuntu/+bug/51147803:05
ubottuUbuntu bug 511478 in ubuntu "My Network Connections are disable and not recognize by the OS after a upgrade to Lucid Lynx" [Undecided,New]03:05
ScottKprefrontal: Can you ping stuff from a konsole session?03:09
prefrontalit looks like this issue has been around since early december based on some forum threads03:10
prefrontali've tried ifup/ifdown, and invoke-rc.d networking restart03:10
prefrontalalso dhclient, and ifconfig eth0 up/down03:11
prefrontali can't even get knetworkmanager to start, just bails with errors03:11
ScottKIf you've got your networking configured via network-manager, ifup/down and restarting networking are no-ops03:11
prefrontali don't actually, just tried it in desperation ;)03:11
ScottKI'd suggest asking on #ubuntu+1 since it doesn't sound Kubuntu specific.03:12
prefrontalk thakns03:12
ScottKAll 16 buildds that can build fro Lucid are busy.  14 of the 16 are building Kubuntu stuff.03:14
prefrontalin networking under system settings there is a wired tab, and there is no wired connection listed there03:20
ScottKThat's normal03:22
* ScottK is on wireless right now.03:22
prefrontalthe 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
prefrontalcya ScottK03:25
ScottKCya.  Good luck03:25
=== shtylman is now known as kubuntu-devel
=== kubuntu-devel is now known as shtylman
verbalshadowprefrontal: 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 ) connection05:10
nixternalwow, 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 along07:06
nixternalrocked out the first part in the "Filing a bug" documentation too....whicked insane, which pictures too :)07:06
nixternalneversfelde: thanks for the updated choqok dude, that seems to have fixed a bunch of issues \o/07:20
* nixternal beds07:20
hunger_tis strigi suppossed to work in lucid at this time?07:26
=== hunger_t is now known as hunger
markeyneversfelde: got your new Choqok package, but, issues remain (seems even worse now)08:23
markeyI'll do the downgrade dance08:23
markeyok, back on choqok_0.6.608:45
markeyyour instructions worked, nice08:45
markeyyep, that one works08:48
Nightrosehey folks :)  I want to install mediawiki and extension by hand but would like to have all deps installed by apt if possible11:59
Nightroseis there a command that does that handily?12:00
Tm_Tno idea12:17
ScottKRiddell: 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:03
ScottKGetting that out of New is all that stands between us and RC2 being done on i386 and amd64.14:10
apacheloggerwhy do we use a dated soprano version?14:30
=== binarylooks is now known as binarylooks_
RiddellScottK: ok14:35
Riddellapachelogger: where's that?  lucid has 2.3.70 and http://soprano.sourceforge.net/ says that's the latest14:35
apacheloggerRiddell: I was talking karmic :)14:35
=== binarylooks_ is now known as binarylooks
Riddellapachelogger: I'm pretty sure karmic shipped with what was available at the time14:56
apacheloggerRiddell: in the ppa ;)14:56
Riddellalso has 2.3.70 https://launchpad.net/~kubuntu-ppa/+archive/beta/+index?start=75&batch=7515:06
apacheloggerno clue where I got the old one from then Oo15:07
apacheloggerRiddell: please sync krename 4.0.3-1 from debian, last upload to ubuntu was a fakesync15:27
ScottK-laptopRiddell: Looks like luatex on armel missed promotion to Main and is causing eigen2 to fail.  Would you please promote it?15:27
persiaDidn't lool say if FTBFS?15:28
ScottK-laptopRetry worked15:29
ScottK-laptopapachelogger: It's synced,but FTBFS.15:39
shadeslayerhi can i ask a launchpad PPA question about packaging here?15:54
=== yofel_ is now known as yofel
apacheloggerScottK-laptop: meh16:10
shadeslayerapachelogger: btw good to have you back :)16:10
apacheloggeroh I should have staied away, debian's patch policy causes headache already16:11
shadeslayerhehe :)16:11
shadeslayerapachelogger: will you revive project neon in the near future?16:12
shadeslayerthats sad,just loved it :(16:13
* jussi01 sighs at cdimage being so slw today... I juat want a daily that works! :(16:54
jussi01or even an alpha 2... has anyone got one of those in a fast location?16:55
ScottKAccepting worked on edge, so after the next publisher run, RC2 is done.17:01
shadeslayerhi 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
ScottKWhat package?17:05
shadeslayerScottK: kopete-facebook17:05
shadeslayerScottK: they released 0.1.5 whereas we have 0.1.417:06
ScottKOK.  This is a good place for that.17:06
shadeslayerScottK: well i talked to persia about this in motu17:06
ScottKI'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:06
shadeslayerand i wanted to help with packaging and thought its a small package which can do with some love17:07
ScottKThat sounds good.17:07
ScottKJust be patient.17:07
shadeslayersure :)17:08
shadeslayeri have all night :17:08
=== shadeslayer is now known as shadeslayer_
=== shadeslayer_ is now known as shadeslayer
shadeslayerhi any ninjas around to teach me about packaging?18:10
apacheloggerwhat do you need to know?18:17
shadeslayerapachelogger: well for starters theres a package kopete-facebook which needs updating,how do i update it in the repos?18:21
apacheloggeryou do not18:21
apacheloggeryou need special privledges to upload anything to the official repos ;)18:21
shadeslayerapachelogger: um why? the current one does not work with 4.418:21
shadeslayerapachelogger: of course but what about the kubuntu backports PPA?18:22
apacheloggersame thing, just less formal18:22
shadeslayercant i give it to you guys and you upload it18:22
ScottKNope, doesn't know that one18:23
apacheloggershadeslayer: https://wiki.ubuntu.com/PackagingGuide/Complete#Updating an Ubuntu Package18:23
shadeslayeroh 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
shadeslayerapachelogger: i was reading that but persia said i needed to contact you guys to update a package already in the repo18:24
persiaI thought it would be easier to work with the ninjas than just an arbitrary update.18:25
ScottKshadeslayer: plasma-scriptengine-python probably needs the new kdebindings which doesn't work yet.18:25
ScottKSo that's not suprising.18:25
persiaIt's not so much a need, as that I thought it was the right set of people to whom to offer help.18:25
shadeslayerScottK: ah..18:25
apacheloggershadeslayer: "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:25
ScottKGotta run.  Back later.18:26
shadeslayerapachelogger: i meant the proposed repo18:26
apacheloggerstill not precise enough ;)18:27
apacheloggershadeslayer: lets start with the kubuntu version ... for what version of kubuntu do you want to prepare an updated package?18:27
shadeslayerapachelogger: 9.10 Karmic Koala18:28
apacheloggerok, that already shrinks the amount of possible repos a lot :)18:28
shadeslayerapachelogger: hehe i already meant the current release,although i wasnt explicit enough :)18:29
hungerIs nepomuk/strigi supposed to work on lucid at this time?18:29
apacheloggershadeslayer: current can also be the one currently in development ;)18:29
apacheloggershadeslayer: so next question is ... is there a new version of kopete-facebook available from upstream?18:30
shadeslayerapachelogger: yeah :)18:30
shadeslayerapachelogger: yep 0.1.518:30
shadeslayerwe currently have : 0.1.4-0ubuntu1.118:30
apacheloggerhunger: nope, from what I have seen earlier we do not build soprano with virtuoso backend yet18:30
Lex79yes we build, but still not works :)18:31
apacheloggeroh, ok18:31
* apachelogger is wondering where the pkg is18:32
apacheloggershadeslayer: perfect, so you want to provide 0.1.5 to karmic users18:32
shadeslayerapachelogger: yes!18:32
apacheloggernow I also know what you meant with "proposed repo" ;)18:32
apacheloggerhowever, it's not that simple18:32
shadeslayerapachelogger: ok lets go slowly then18:33
apacheloggershadeslayer: karmic-proposed is the testing part of karmic-updates, those are technically two different repos, proposed is not active by default, updates however is18:33
shadeslayerapachelogger: 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-facebook18:34
apacheloggerwell, yes, I'll get there...18:34
shadeslayer(0.1.4 doesnt work with 4.4 apparently)18:34
shadeslayerapachelogger: ok18:34
apacheloggerfirst 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 user18:35
apacheloggerso to get anything in there you would have to do a stable release update (short: SRU)18:36
ubottuStable Release Update information is at http://wiki.ubuntu.com/StableReleaseUpdates18:36
apacheloggerlong story short, the jump from 0.1.4 to .5 does not qualify for such a SRU ;)18:36
shadeslayerapachelogger: you mean like point release?18:36
shadeslayerlike from 0.1.4 to 0.1.518:36
apacheloggershadeslayer: even more restricted!18:36
apacheloggerultimately one update to proposed/updates holds exactly one change to resolve one very particular issue18:36
apacheloggerthe more changes, the higher the risk of regression, the lower the likelyhood it gets accepted for upload to proposed to begin with18:37
hungerapachelogger: I do have virtuoso backends installed with kdebase-runtime or so.18:37
shadeslayerapachelogger: ah i get it.. like it says, even one line changes can cause regressions18:37
apacheloggerhunger: yeah, Lex79 says it is just not working, for whatever reason :)18:38
apacheloggerhunger: shouldn't be too long now I suppose18:38
hungerapachelogger: Actually it seems to kind of work after installing all virtuoso packages, even though the nepomuk config thingy says it does not.18:38
apacheloggershadeslayer: 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
hungerapachelogger: I do see search results that must have come from the indexer... and the index grew quite a lot:-)18:39
apacheloggershadeslayer: instead, when providing such updates as from 0.1.4 to 0.1.5, we utilize another repo, karmic-backports18:39
shadeslayerapachelogger: ok18:39
hungerapachelogger: 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:40
apacheloggershadeslayer: 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 least18:41
shadeslayerapachelogger: ah..18:41
apacheloggerkarmic-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.418:42
shadeslayerapachelogger: i was just typing that question... you read my mind :o18:43
apacheloggerso, that is your motivation18:43
apacheloggerBUT ;)18:43
shadeslayertheres always one isnt there18:43
apachelogger0.1.5 might be interesting to lucid users and might also be interesting to karmic users that do not use KDE 4.418:43
apacheloggerso 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.418:44
shadeslayerapachelogger: yeah,but kopete-facebook works *only* with 4.3.2 and not the later bug fix releases18:44
shadeslayerapachelogger: shouldnt the lucid package already be prepared?18:46
apacheloggerthat is the question we have to answer first18:46
shadeslayerapachelogger: should i check ?18:47
apacheloggershadeslayer: you could for example enter upkg:kopete-facebook into krunner18:47
apacheloggerthat should take you to packages.ubuntu.com18:48
apacheloggeror ask ubottu18:48
apachelogger!info kopete-facebook lucid18:48
shadeslayerthats new :)18:48
apacheloggeror look it up on launchpad18:48
ubottukopete-facebook (source: kopete-facebook): Facebook chat plugin for Kopete. In component universe, is optional. Version 0.1.4+git20091226-0ubuntu1 (lucid), package size 63 kB, installed size 304 kB18:48
shadeslayerapparently yes18:48
shadeslayeri guess the +git is the git patches applied?18:48
apachelogger+git means that it is a snapshot from git18:49
apacheloggerthere is also +svn and +bzr etc.18:49
shadeslayerand they mean the same thing18:49
apacheloggerright, they just indiciate which kind of version control system the snapshot comes from18:49
shadeslayeryeah i just learned to use bazaar a few days ago :P18:50
shadeslayer(the ubuntu-manual thing)18:50
apacheloggerusually 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 snapshots18:50
apacheloggercool :)18:50
shadeslayerapachelogger: so this means that alot of patches were applied from that git snapshot?18:51
apacheloggerin this case it means no patches were applied at all18:51
shadeslayerapachelogger: eh? then why the +git?18:52
apacheloggersomeone took the complete code from the git repository on 2009-12-2618:52
apacheloggerand turned it into a source package18:52
shadeslayerapachelogger: so its kinda like 0.1.4.x18:52
apacheloggernot exactly18:53
shadeslayerapachelogger: why?18:53
apacheloggerit is something between 0.1.4 and 0.1.518:53
shadeslayerthats what i said :P18:53
apachelogger0.1.4.x would be a minimal update to 0.1.418:53
shadeslayerhmm well i actually meant what you said... difference of perception :)18:54
shadeslayerbut yeah i get what you mean18:54
apacheloggeryeah, though I would not say 0.1.4.x but 0.1.4+git20091226 ;)18:54
shadeslayerhehe :)18:54
apacheloggerwhich is really what it is, it is 0.1.4 at the time of 2009-12-26 from git18:55
apachelogger(technically it was not 0.1.5 by then)18:55
apacheloggerso indeed we need to update the lucid package as well18:55
shadeslayerapachelogger: and for that ill need special permissions18:55
apacheloggerno, for the _upload_ you need18:56
shadeslayerwhich cant be given to anybody18:56
apacheloggernot for the update18:56
shadeslayeryeah thats what i meant,for the upload18:56
shadeslayerof course i can just make the package and give it to you guys18:56
shadeslayerwhich is much easier..18:57
apacheloggershadeslayer: https://wiki.ubuntu.com/SponsorshipProcess deocumentes the whole sponsorship process18:57
apacheloggerafter all that theory I suppose you want to get started on updating the lucid package? ;)18:58
shadeslayerive already downloaded the 0.1.5 source :P18:58
apacheloggerthough 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.418:58
shadeslayerok,so we work top down18:59
apacheloggershadeslayer: do you have some how to guide on updating a package?19:00
shadeslayerapachelogger: me?19:01
apacheloggerwell, something you can follow, or do you need me to hold your hand? ;)19:01
shadeslayerapachelogger: well i was reading https://wiki.ubuntu.com/PackagingGuide/Complete#Packaging from Scratch and got till dh_make19:01
apacheloggerwell, that is not helping much here ;)19:02
shadeslayerand then editing the changelog19:02
apacheloggershadeslayer: got the URL of the 0.1.5 source?19:02
shadeslayeryeah one sec19:02
shadeslayerapachelogger: http://github.com/dmacvicar/kopete-facebook/downloads19:02
apacheloggershadeslayer: first things first: getting the current lucid package19:05
apacheloggeropen a terminal and go to some nice directory where you want to do you work19:05
shadeslayerapachelogger: /home/shadeslayer/packaging << done19:06
apacheloggerI recommend that you create a subdirectory in there ;)19:06
apacheloggerotherwise it gets messy after some time19:06
apacheloggermkdir kopete-facebook; cd kopete-facebook19:06
shadeslayerhehe... ok19:06
apacheloggerfor example19:06
shadeslayerapachelogger: done and untarred19:07
apacheloggerthen you pull the current source package from launchpad19:07
apacheloggerpull-lp-source kopete-facebook lucid19:07
shadeslayerapachelogger: where?19:08
shadeslayerin the kopete-facebook dir?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 ubuntu19:08
shadeslayerok one sec19:08
apacheloggeronce pull-lp-source is done it should have extracted the package already. my dir now looks like this: http://paste.ubuntu.com/362122/19:09
shadeslayerapparently kubuntu-dev-tools doesnt cut it :P19:10
apacheloggershadeslayer: it ships with ubuntu-dev-tools19:10
shadeslayerE: 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
apacheloggershadeslayer: manage-credentials create -c ubuntu-dev-tools -l 219:11
ScottKThe version in Lucid doesn't require that if you don't specify the release (it defaults to Lucid_19:12
apacheloggerthat should fire up your browser with launchpad asking you to grant privledges to ubuntu-dev-tools19:12
apachelogger"read all public data" should be fine I suppose19:12
shadeslayerum no such option :P19:13
apacheloggerwell, something that sounds like that :P19:13
shadeslayerread non private data?19:13
shadeslayerdone and pressed enter19:14
apacheloggershadeslayer: does pull-lp-source work now?19:14
shadeslayerwell my internet connection is working like crazy right now19:14
shadeslayerit didnt finish19:14
apacheloggeryou need to close the browser and press enter I think19:15
shadeslayerok pulling now19:15
shadeslayeryeah did that :)19:15
shadeslayerapachelogger: its downloading tarballs19:16
apacheloggerScottK: will revu ever get cleaned up again?19:16
shadeslayerapachelogger: http://pastebin.com/f1796f83c19:17
apacheloggershadeslayer: perfect, kopete-facebook-0.1.4+git20091226 will now contain the old debian directory19:17
shadeslayerok i should untar it first right19:18
apacheloggershadeslayer: so  just copy that over to the new source directory19:18
apacheloggershadeslayer: already untared ;)19:18
apacheloggerpull-lp-source took care of that19:18
apacheloggerotherwise you would extract the source with ... dpkg-source -x kopete-facebook_0.1.4+git20091226-0ubuntu1.dsc19:18
apacheloggerdpkg-source will do some additional magic over "regular" untaring19:19
shadeslayerapachelogger: done19:20
shadeslayercopied the debian directory19:20
apacheloggershadeslayer: ok, now you need to rename the new tarball19:21
apacheloggerusually tarballs need to be named NAME_VERSION.orig.tar.gz19:21
apachelogger(there are cases where that is not the case, but for now just consider that the law ;))19:21
shadeslayerdone :)19:22
apacheloggerso dmacvicar-kopete-facebook-3376a46.tar.gz needs to be kopete-facebook_0.1.5.tar.gz19:22
shadeslayerapachelogger: yeah did that :)19:22
apacheloggernow you can enter the new source directory19:22
shadeslayerapachelogger: i just renamed the directory as orig.tar.gz accidently :P19:23
apacheloggerthe first thing you want to do in the new source is add a changelog entry19:24
shadeslayerin it..19:24
shadeslayerapachelogger: in the debian folder...19:24
apacheloggerfor that you can use the tool dch (short for debchange)19:24
apacheloggerthat needs to be invoked from the top source folder (the dir containing the debian one)19:25
shadeslayerapachelogger: like : dch -e rohan16garg@gmail.com ?19:25
apacheloggerand no19:25
apacheloggerthat is quite unhandy19:25
apacheloggerkate ~/.bashrc19:25
apacheloggerat the very bottom you add19:26
apacheloggerexport DEBFULLNAME='Harald Sitter'19:26
apacheloggerexport DEBEMAIL='apachelogger@ubuntu.com'19:26
apacheloggerwell, with your data obviously ;)19:26
shadeslayernow dch?19:27
apacheloggersource ~/.bashrc19:27
shadeslayerreload the settings :) done already19:28
apacheloggerthat applies what you just did to the terminal (from now it will be applied to all new terminals right away though ;))19:28
apacheloggerah, ok :D19:28
apacheloggerdch -v 0.1.5-0ubuntu1 -D lucid19:28
shadeslayergives me a warning.... lucid not recognized19:29
shadeslayerand i press enter19:29
apacheloggerthat 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 DEBFULLNAME19:29
apacheloggershadeslayer: 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:29
shadeslayerapachelogger: hmm i have karmic-backport afail19:30
apacheloggerScottK: ^19:30
shadeslayerapachelogger: http://pastebin.com/f38e64f3c19:30
apachelogger!info ubuntu-dev-tools karmic-backports19:31
ubottuPackage ubuntu-dev-tools does not exist in karmic-backports19:31
apacheloggershadeslayer: apparently it does not want to do that ;)19:31
apacheloggershadeslayer: the standard entry for all new releases is "New upstream release"19:32
shadeslayerjust after * ?19:32
apacheloggerlike in the screenshot I posted19:32
apacheloggerthen just save the change19:33
shadeslayerdone :)19:34
apacheloggershadeslayer: now open debian/control in your preffered editor19:35
shadeslayerapachelogger: ^^19:36
apacheloggerwith every update you usually want to check whether all files in debian/ are updated19:37
shadeslayerthe build deps and stuff?19:37
apacheloggeryes, though at this point we would have to guess whether they need additions or something19:38
apacheloggerbut, for example homepage and standards-version can be checked right away19:38
apacheloggerI suppose the current homepage entry is not that up-to-date19:38
apacheloggermaybe you can find a better one19:38
apacheloggerand standards-version is the version of the debian policy this package is compatible with19:39
apacheloggermost recent one is 3.8.3, so we should probably go with that http://www.debian.org/doc/debian-policy/19:39
shadeslayerone sec19:39
shadeslayerapachelogger: theres no blog entry for 0.1.5 but theres one for 0.1.519:42
shadeslayerum 0.1.419:42
apacheloggerusually homepage should be something static19:43
shadeslayeror should i just add the the whole home page19:43
apacheloggerI would add http://github.com/dmacvicar/kopete-facebook19:43
apacheloggerit is the closest to a homepage there is IMHO19:44
shadeslayerand standards version to http://github.com/dmacvicar/kopete-facebook19:44
shadeslayerctrl+shift+C fails me :P19:45
shadeslayerok next?19:45
apacheloggeronce you are done with that you need to add those 2 changes to the changelog19:45
apacheloggeryou can either do that manually by opening the changelog in your editor19:46
apacheloggeror by using dch -a19:46
apachelogger-a == append ;)19:46
shadeslayerdch again in root source dir19:46
apacheloggerso you would add something like  * Changed homepage from blog to github  * Bumped Standards-Version from 3.8.1 to 3.8.319:46
ScottKapachelogger: No idea about review.19:46
apacheloggershadeslayer: yes, dch only works from root source I think19:47
ScottKapachelogger: 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
apacheloggershadeslayer: though -a really just adds such a bullet point *, which you can do just as well yourself in an editor ;)19:47
shadeslayerapachelogger: done19:47
shadeslayerapachelogger: hehe :)19:48
apacheloggerScottK: oh, I was wrong anyway, dch is part of devtools ^^19:48
* apachelogger is incredibly silly today19:48
ScottKYeah, devscripts19:48
shadeslayerapachelogger: ok done19:49
apacheloggershadeslayer: 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
apacheloggershadeslayer: now we get to a tricky part19:49
ScottKThe 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
shadeslayerapachelogger: ah ok19:49
dhillon-v10hi 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 no19:50
apacheloggershadeslayer: this package uses patches and a rather confusing approach to applying those patches19:50
ScottKdhillon-v10: If it's a difference between the Ubuntu package and the Debian package, yes.19:50
shadeslayerapachelogger: btw i must tell you that im experiencing power outages19:50
apacheloggershadeslayer: usually packaging patches are stored in debian/patches19:50
_Groo_ppl whats wrong with dput uploads, im having timeouts and i cant send anything, the speed is below 2k uploads...!!!19:51
dhillon-v10ScottK: alright thanks :)19:51
shadeslayerapachelogger: so if you dont get a reply for more than 2 mins that means there was power/Internet outage :P19:51
apacheloggershadeslayer: ok, I'll not be worried should you get lost ;)19:51
dhillon-v10_Groo_: same happened to me yesterday19:51
shadeslayerapachelogger: ok so patches...19:51
apacheloggershadeslayer: so, now you can open all patches in there19:51
_Groo_i cant upload koffice, newer kde multimedia with PA, nothing :(19:52
shadeslayerapachelogger: um why do we need patches?19:52
apacheloggershadeslayer: to fix bugs ;)19:52
apacheloggershadeslayer: as stated on the SRU page, the smaller the change the lower the risk of regression19:52
_Groo_can i use http instead of ftp? or launchpad only accepts ftp?19:53
shadeslayerapachelogger: hehe.. but arent these patches applied upstream rather than at our end?19:53
apacheloggershadeslayer: yes, ultimately they are applied upstream, but sometimes upstream does not release the fixed version early enough for us to use it19:53
apacheloggerfor example19:53
apachelogger0.1.4 does not build against KDE 4.419:54
apacheloggerbut upstream did not yet release 0.1.519:54
apacheloggerand we are releasing a kubuntu version in like 2 weeks19:54
dhillon-v10ScottK: 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 updated19:54
shadeslayerapachelogger: ok19:54
apacheloggershadeslayer: 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 builds19:55
ScottKdhillon-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
shadeslayerah so thats a 0.1.4 which was made to build with kubuntu19:55
* shadeslayer starts to get the hang of things19:56
apacheloggershadeslayer: we call that cherry picking http://en.wikipedia.org/wiki/Cherry_picking#Software_configuration_management19:56
dhillon-v10ScottK: 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 changes19:56
shadeslayerhehe :)19:56
apacheloggerif you understood bazaar's branch concept already it might help to think of packages as branches of the same software19:57
ScottKThe creation dates are almost certainly noise.  You need to look for any real changes and not drop blindly.19:57
dhillon-v10ScottK: alright19:57
apacheloggershadeslayer: 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
shadeslayerapachelogger: yeah i already know basic stuff about git and bzr19:58
shadeslayerbranches of a tree19:58
shadeslayerand then you apply patches to merge the branch with the trunk :P19:59
shadeslayerapachelogger: btw ill be packaging choqok too later :P19:59
apacheloggeroh dear :D19:59
apacheloggerwell, lets move on19:59
shadeslayeron my own though :P19:59
apacheloggersince I do not want to go into the patch system details just now...20:00
apacheloggerwhat we need to do is drop all patches20:00
shadeslayerapachelogger: drop as in apply or drop as in not apply20:00
apacheloggerthey both originated from upstream (which, if it were properly documented, you could easily see in the debian/changelog)20:00
apacheloggershadeslayer: remove20:00
apacheloggerrm -rf debian/patches20:00
apacheloggerhowever, in this particular case we need to do a bit more20:01
apacheloggerin debian rules remove line 520:01
apacheloggerinclude /usr/share/cdbs/1/rules/simple-patchsys.mk20:01
shadeslayerchangelog  compat  control  copyright  rules20:01
dhillon-v10ScottK: here: # translation of ssl-cert_1.0.22_nl.po to Dutch20:01
dhillon-v10#    Translators, if you are not familiar with the PO format, gettext20:01
dhillon-v10#    documentation is worth reading, especially sections dedicated to20:01
dhillon-v10#    this format, e.g. by running:20:01
dhillon-v10#         info -n '(gettext)PO Files'20:01
dhillon-v10#         info -n '(gettext)Header Entry'20:02
apacheloggerin debian/control line 7 remove the build-dep "quilt, "20:02
dhillon-v10#    Some information specific to po-debconf are available at20:02
shadeslayerapachelogger: why did we do that?20:02
dhillon-v10#            /usr/share/doc/po-debconf/README-trans20:02
dhillon-v10#         or http://www.debian.org/intl/l10n/po-debconf/README-trans20:02
dhillon-v10#    Developers do not need to manually edit POT or PO files.20:02
shadeslayerdhillon-v10: 0_o20:02
dhillon-v10# Paul Gevers <paul@climbing.nl>, 2008.20:02
dhillon-v10msgid ""20:02
dhillon-v10msgstr ""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
apacheloggerI wonder if the whole po is coming through now :D20:02
dhillon-v10"PO-Revision-Date: 2008-09-23 21:38-0500\n"20:02
ScottK!pastebin | dhillon-v1020:02
dhillon-v10"Last-Translator: Paul Gevers <paul@climbing.nl>\n"20:02
ubottudhillon-v10: For posting multi-line texts into the channel, please use http://ubuntu.pastebin.com | To post !screenshots use http://tinyurl.com/imagebin | !pastebinit to paste directly from  command line | Make sure you give us the URL for your paste - see also the channel topic20:02
Tm_Tapachelogger: you don't see him flooding anymore, right?20:03
apacheloggershadeslayer: 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 process20:03
apacheloggershadeslayer: the quilt build-dep in debian/control is a very sophisticated patch system20:04
shadeslayerso basically we need to remove the parts which were supposed to apply those patches20:04
apacheloggertechnically we could leave this stuff around, but it is better to keep the package as clean as possible20:05
apacheloggerwhich includes not referencing patch systems when there are no patches :)20:05
Tm_Tshould have done this rightaway, his client couldn't stop it, it seems20:05
shadeslayerapachelogger: of course20:05
apacheloggerTm_T: ;)20:05
shadeslayerapachelogger: something you said about line 7 , got lost in the flood there :)20:06
apacheloggershadeslayer: now, dont forget to document this in the changelog20:06
* shadeslayer like irssi... asks for confirmation20:06
apachelogger* Removed all patches and patch system (all applied upstream)20:06
apacheloggerfor example20:06
shadeslayerapachelogger: ah of course the change log20:06
apacheloggershadeslayer: ultimately you would mention the patches' names ;)20:07
apachelogger* Removed all patches kubuntu_01_offline_detection.diff and kubuntu_02_protocol_changes.diff (all20:07
shadeslayerdone :)20:08
shadeslayerapachelogger: ah even the ones removed?20:08
apachelogger* Removed all patches (all applied upstream)20:08
apachelogger  - kubuntu_01_offline_detection.diff20:08
apachelogger  - kubuntu_02_protocol_changes.diff20:08
shadeslayeroh like that20:08
shadeslayerbut i already deleted the patches directory20:08
apacheloggeryeah, I should have told you before ;)20:09
apacheloggerwell, next time you know, plus it is bonus anyway20:09
shadeslayerok ill go through the old one20:09
apacheloggershadeslayer: this stuff can help people who try to reproduce what happened via the changelog and by mentioning the names it is easier to search20:09
apacheloggerso 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 upstream20:10
shadeslayerok i understand20:10
apachelogger...and maybe you were wrong in removing the patch, and I could go poke you in the eye :P...20:11
Tm_Tdhillon-v10: welcome back and sorry again for forgetting ban on20:11
shadeslayersure :)20:11
dhillon-v10Tm_T: np, I should be the one apologizing :D20:11
shadeslayerapachelogger: ill wear shades next time im around you20:11
shadeslayerapachelogger: what next?20:13
apacheloggerI think you are ready to testbuild the package20:13
apacheloggerdebuild -S -sa20:13
* shadeslayer jumps up and down with joy20:13
apacheloggerwill create a source package20:13
shadeslayerapachelogger: in the source dir?20:14
shadeslayeror the one above it?20:14
shadeslayerapachelogger: http://pastebin.com/f4cd2c97b20:15
shadeslayerand the last two lines : debuild: fatal error at line 1255:20:16
shadeslayerrunning debsign failed20:16
shadeslayeri think line 1255 means 1255 of LINE:   -kubuntu_02_protocol_changes.diff20:16
apacheloggershadeslayer: please paste your debian/changelog20:16
apacheloggershadeslayer: do you have a GPG key?20:16
shadeslayerapachelogger: i have a ssh-rsa key if thats what you mean20:17
apacheloggerSSH != GPG :)20:17
shadeslayerhow do i get one?20:17
apacheloggershadeslayer: https://help.ubuntu.com/community/GnuPrivacyGuardHowto20:17
shadeslayerapachelogger: http://pastebin.com/f6b9e1e4c20:17
apacheloggerthe lines before the patch file names have tabulators20:19
shadeslayerapachelogger: ah thats why?20:19
shadeslayerdid i have to use space?20:19
apacheloggerusually you should stick to spaces, only debian/rules should contain tabulators20:19
apacheloggershadeslayer: most editors can be configured to add a certain amount of white spaces when the tabulator key is used20:20
shadeslayerapachelogger: i used nano...20:20
shadeslayerapachelogger: do i generate a key before building the package?20:21
apacheloggeryou need to sign the source with your key20:21
shadeslayerok one sec20:21
shadeslayerfirst i need to generate one right20:21
shadeslayerRSA algorithm?20:22
apacheloggershadeslayer: yes20:23
apacheloggerjust sticking with the defaults is a good idea :)20:23
shadeslayerum where is the key stored?20:26
prefrontaljust 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 example20:26
apacheloggershadeslayer: ~/.gnupg20:26
prefrontalthis 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/176435020:27
shadeslayerapachelogger: private keys?20:27
apacheloggershadeslayer: you probably should read on about gpg on wikipedia ;)20:27
apacheloggeryou have a private and a public key20:27
apacheloggerthe private key is used to sign and encrypt stuff20:28
shadeslayerah ok20:28
apacheloggerthe public key is used to proof the signature20:28
shadeslayerah ok20:29
shadeslayerso its my sign that its actually by me20:29
shadeslayerand thats why its called a signature :P20:29
apacheloggerright ;)20:31
shadeslayerok now what?20:32
apacheloggershadeslayer: that is what your changelog should look like http://paste.ubuntu.com/362169/20:33
apacheloggershadeslayer: then you can run debuild -S -sa again20:33
apacheloggerand hopefully it works now :D20:33
* shadeslayer crosses fingers20:33
shadeslayerdebsign: gpg error occurred!  Aborting....20:35
shadeslayeralso : debuild: fatal error at line 1255:20:35
apacheloggermore output please20:36
shadeslayerone sec20:37
shadeslayeri modified the changelog according to your pastebin20:37
shadeslayerapachelogger: http://paste.ubuntu.com/362178/20:38
apacheloggershadeslayer: what does ...  gpg -k "Rohan Garg" ... spit out20:38
shadeslayerapachelogger: http://pastebin.com/f620eb78320:39
shadeslayeri made 2 keys.. :P20:40
shadeslayerapachelogger: should i delete one20:41
apacheloggershadeslayer: the comment is of the disturbing kind ;)20:41
neversfeldeany known problems with kdm, I cannot login, kdm crashes.20:42
shadeslayerapachelogger: which one?20:42
apacheloggershadeslayer: you need to add that to your DEBFULLNAME and the debian/changelog20:42
apachelogger(shadeslayer's key)20:42
shadeslayerapachelogger: ah should i remove it?20:42
apacheloggernot sure if you can20:42
apacheloggerthough I suppose you can20:42
shadeslayerapachelogger: too vauge :P20:43
apacheloggerwell, I dont know ;P20:44
shadeslayerapachelogger: what do i do once again>20:45
shadeslayerapachelogger: i add what to DEBFULLNAME ?20:45
apacheloggerthe comment of the key you want to use20:46
apacheloggergotta run20:46
apacheloggersee you later20:46
shadeslayerapachelogger: ok so like export DEBFULLNAME='Rohan Garg'20:46
shadeslayerRohan (shadeslayer's key)20:46
shadeslayeranyone else around here to help?20:46
shadeslayerapachelogger: thanks for the help though :)20:47
shadeslayerScottK: any ideas?20:54
shadeslayerim like at the end of this thing :P20:54
ScottKIt needs to match exactly.20:55
shadeslayerScottK: ok but what do i put in the change log?20:55
shadeslayerah found it20:56
ScottKshadeslayer: Sorry, I'm only barely here and don't have time to read all the backscroll.20:56
shadeslayerScottK: it saysSuccessfully signed dsc and changes files20:56
shadeslayerScottK: and i had run debuild -S -sa20:56
ScottKGotta run myself.20:57
shadeslayerScottK: ok bye20:57
shadeslayeranyone else?20:57
shadeslayeri think im asking for too much :P20:58
RiddellI have no idea how to reply to this http://paste.ubuntu.com/362190/21:05
shadeslayerRiddell: um.. no one knows the reply to that21:06
shadeslayernot even linus himself :P21:07
neversfeldewhere did we disable the groups in category internet in kickoff the last time?21:07
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 the21:14
Trouble-two problems may be linked.21:14
shadeslayerTrouble-: that happened to me too... i made a pre-kde bash script21:15
Trouble-That's good to know! After searching Google I assumed I was the only person with the problem :)21:16
shadeslayerTrouble-: although the problem disappeared in RC 221:18
Trouble-My problem got worse with RC2 hehe21:19
Trouble-Now I have to 'startx' from a terminal :)21:20
shadeslayerTrouble-: that wont give you shut down and reboot options :P21:20
Trouble-AND then run plasma-netbook manually ;-)21:20
shadeslayerTrouble-: do sudo kdm..21:20
shadeslayerTrouble-: kdm doesnt start up automatically?21:20
Trouble-Yea, I gotta logout, then shutdown from the terminal too :)21:20
shadeslayerTrouble-: put this in rc.local : kdm21:21
Trouble-kdm starts fine. When I login, KDE starts to start, but then I get dropped back to kdm :-s21:21
Trouble-Need to work out what it's doing, or rather not doing21:21
shadeslayerTrouble-: check the logs21:21
ScottKTrouble-: Does it work on the 2nd try?  If so, I believe this is known.21:32
prefrontalafter reboot in lucid i have to run ifdown eth0 && ifup eth0 && start kdm21:34
shadeslayeranyone know how to build a .deb?21:35
mass-destructionshadeslayer: pbuilder :)21:35
shadeslayermass-destruction: well the last command apachelogger gave me was : debuild -S -sa21:36
mass-destructionshadeslayer: that too :)21:36
shadeslayermass-destruction: but i dont see any .deb ?21:36
mass-destructionshadeslayer: move a directory up, it should be there21:37
shadeslayeri want my binary files :P21:37
shadeslayermass-destruction: theres a .build fine21:37
shadeslayermass-destruction: http://pastebin.com/f42d80cdc21:38
mass-destructionshadeslayer: just give me a sec.21:39
shadeslayermass-destruction: take 221:39
shadeslayerbut please do reply :P,its 3 AM here :D21:39
mass-destructionshadeslayer: alright go into you debian directory and then do this: dpkg-deb --build, let's see if that works21:40
Trouble-ScottK: 'fraid not. It's permanent :-s21:40
Trouble-shadeslayer: Just looking at kdm.log now.21:40
Trouble-I wonder if it's something to do with "[config/dbus] couldn't register object path"21:41
shadeslayermass-destruction: dpkg-deb: --build needs a <directory> argument21:42
mass-destructionshadeslayer: 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 shadeslayer21:43
shadeslayermass-destruction: ok no problem ill come back tommorow then :)21:44
=== mass-destruction is now known as dhillon-v10
Zoraelkdm 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:34
JontheEchidnadunno, best file a report against xserver-xorg-video-intel22:37
JontheEchidnafwiw I updated yesterday and my lappy boots just fine22:37
JontheEchidna(it has an intel)22:38
shadeslayerapachelogger: my first build thanks to you :D : https://launchpad.net/~rohangarg/+archive/kde-extra/+packages22:47
nixternalthe list for KOffice MIRs keep on growing23:17
Riddellnixternal: what's new?23:21
nixternalplotutils needs to be MIRd for pstoedit23:22
crimsunRiddell: / maco: is the usb symptom described on ubuntu-devel@ with or without karmic-updates enabled?23:22
nixternaljust one there, so that is good23:22
Riddellcrimsun: I think markey only had it after he updated with karmic-updates23:22
nixternalgoing through all of the bug reports and security stuff for the packages now, creating an annoyingly massive checklist23:22
crimsunRiddell: there's definitely a linux component to the uevent screwage23:23
crimsuncf. udevadm monitor --property23:24

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!