=== m4v_ is now known as m4v [00:01] ...and deliver what we promote [00:01] no silly usability bugs [00:01] amichair: I cannot tell you how right you are. [00:04] e.g. the software-properties (repo sources dialog) bugs I've been fixing for the past couple of days... they wouldn't pass a 30-minute qa session in any commercial company [00:05] and the whole app is just a gui, there's no real technical problem here... [00:05] amichair: You are my new best friend. [00:05] well I hope I can make things a tad better :-) [00:05] That is exactly the kind of thing that needs to get fixed. [00:06] just having these dialogs means Kubuntu is going to be better :) [00:06] you folks rock! [00:07] oooh what a horse race! literally [00:07] * claydoh is watching the breeders cup for some odd reason [00:08] So who else do we need to convince about this? (amichair and claydoh) [00:09] lol... I thought I wasn't getting some 'horse race' proverb from somewhere around the world ;-) [00:09] amichair: I had a moment of that, too. [00:10] I think it has to come up here (or in the lists) with the major kubuntu devs [00:10] amichair: And that's my question; I haven't been here long enough to know who those are. [00:11] probably no one to convince, I think all the 'players' are/would be on board thats why we have Timelord - to get more peeps involved and help form what we are going to become [00:11] me neither :-) === Snova_ is now known as Snova [00:12] claydoh: yes, I meant not as much 'convincing' as getting everyone's mind-share on this [00:13] claydoh: It seems like some people who are determined to stick as closely as possible to the KDE upstream aren't liable to be pleased about the idea of pushing customization. [00:13] apachelogger, Scott K, Rid dell, and a number of others [00:13] Or at least, the idea of including an-easier-to-find customization center. [00:13] so maybe we can get the KDE ppl to do it :-) [00:13] jwisser: customization can take many forms, but I think some small things are possible [00:14] claydoh: Nice thing about this channel is that I've already spoken to two of the three you mention by name. Good deal. :-) [00:14] claydoh: I'm not pushing for OOTB customization, just easier access to it for individual users. [00:15] amichair: Dur. I'm still in closed-source mindset from using my Mac. I forget you can go ask people nicely. [00:15] jwisser: that probably would be better for upstream as it would elp out KDE greatly [00:15] * jwisser goes to find the KDE dev channel. [00:16] re: the horse race, the favorite came from last place and ended up winning - and setting history as the first female horse to win the race [00:16] claydoh: we're making history here :-) [00:16] amichair: looks like it :) [00:17] Gotta say, I'm excited about the possibilities. :-) [00:18] * amichair wishes he could make a living of open source dev [00:18] For now, I'm just gonna start reading #kde-devel. I don't want to go ask for something until the Kubuntu community as a whole is behind it. [00:18] jwisser: go a head and mingle :-) [00:27] How bad would the reaction be to including a closed-source app on the Kubuntu desktop? Theoretically speaking? [00:27] jwisser: never by default, will never happen [00:28] it would go very badly i am sure [00:28] jwisser: which app? [00:28] Ubuntu policy wouldn't allow it even if everybody wanted it :P [00:29] JontheEchidna beat me to that point [00:29] Unfortunate. I was just thinking it would be extraordinarily badass if we could get the Doubletwist guys to port to Linux. "Just works" synching with craptons of media players and smartphones out of the box? Yes, please. [00:29] Hmmm. [00:30] I wonder if we could convince them to collaborate with Kubuntu devs on a FOSS version for Linux. [00:30] It occurred to me the other day that an app like that would to a long way toward distinguishing a given Linux distro. [00:31] Particularly because I'm pretty sure they're working on iPhone syncing… [00:31] Imagine being the first distro with full iPhone sync. [00:33] Better still if we could add support for the Pre, as well. [00:33] Talk about your killer app for a lot of users. [00:35] But, possibly I am crazy. [00:35] its gotta be FOSS tho, else we become linspire or worse :) [00:35] ::shivers:: Fair enough. None of that around here. [00:36] jwisser: well, we won't be the first - if they port, many distros will include it as well. Not that I think that's a bad thing :-) [00:36] one thing I've found is that it's very hard to be unique [00:36] Ehhh, we could be the first. Little creative release timing. ;-) [00:36] And a late announcement. [00:37] we are pretty much first among the regular 6-month distros [00:37] Not for long, sure, but we could be first to market and get a reputation for getting cool stuff done. [00:39] And if you want new devs, that should bring a few in. [00:49] is it possible in bzr to update the log message for a commited revision? [00:50] * JontheEchidna would like to know too [00:50] I usually just bzr uncommit when that happens [00:50] which is inconvenient, to say the least [00:55] JontheEchidna: r u a long time kubuntu dev? [00:56] I've been contributing since mid-2008, so not too terribly long-time compared to some here [00:56] jwisser: What's the only netbook oriented KDE distro in the world? [00:56] Being first is a good thing and we can do it if we pick some right things to be first at. [00:57] Marketing works in more than one direction. [00:57] ScottK: good point! but how would u translate that for someone that has no idea what kde is? [00:58] In 6 months if several distros are pestering the netbook devs for stuff, where will their first attention go? [00:58] Hopefully to us. [00:58] amichair: Part of the problem is that end users are really who you market to for netbooks. [00:59] The target market for netbooks is people making OEM decisions. [00:59] There is money in being pre-installed. [00:59] That drives a different kind of argument. [00:59] true [01:00] It is really hard to make existing GTK+ stuff scale down to netbooks. That's why Canonical has a huge mobile team. [01:00] Qt/KDE 4, it's dead easy. [01:00] if these ppl hear kde, is that enough to give us a few extra points? [01:00] Nokia didn't buy Trolltech for charity. [01:01] also, do scaling issues translate to oem problems, or ubuntu dev problems? [01:01] Qt is the future in small form factor computing compared to GTK. It's already known the Maemo 6 will be Qt. [01:01] amichair: Both. [01:01] cool (for us :-) ) [01:02] The future may be Android or something else, but between GTK and Qt, I think in the next couple of years, Qt is the clear winner. [01:02] amichair: Look at the size of the Canonical team working on Ubuntu Mobile desktop/launcher and look at us with 2 upstream devs and a few of us working part time. [01:03] The value position for an OEM in terms of cost risk is substantially lower with a Qt/KDE solution. [01:03] Hi, I need help. I just upgraded from jaunty to karmic and couldn't reboot. [01:03] KDE is shinier than Gnome too. [01:03] yes, shiny is why I'm here :-) [01:04] ::laughs:: Shiny is what kept me away for so long. [01:04] I heard someone at say that at install fests they just give Kubuntu CDs to people that ask for it or people that say Ubuntu is ugly. [01:04] (Sorry, forgot to set away while making dinner.) [01:04] The upgrade terminated between installing and clean up, but I got a reboot anouncement which I followed. [01:04] bjoern_: Did you try in #kubuntu? That's the help channel. [01:04] is promotion/marketing necessary in that case? or is it just about finding the right half-dozen oem decision makers and sending someone to talk to them? [01:05] amichair: That's promotion/marketing. [01:05] amichair: Still counts as promotion and marketing. ;-) [01:05] ok... u know what I mean :-) [01:05] One thing we need is a really shiny demo mode. [01:05] That's some of the hardest marketing to do, in fact, as a lot of those people have a small staff dedicated to keeping the riffraff away. [01:05] If we had that, a Kubuntu based netbook would fly off the shelves. [01:05] ScottK: Sorry, yes, but I didn't got an answer. [01:06] bjoern_: What happens when you try to boot? [01:06] ScottK: demo mode? isn't the regular user experience the aim of shininess? [01:06] amichair: It needs to look sexy on a store shelf. [01:06] This is about marketing still. [01:07] ScottK: that's my point... it needs to look that way all the time! if someone borrows my netbook to check their mail, they shold be jelous within 30 seconds... [01:07] ScottK: menu.lst had still the old kernel which didn't boot. And for the new kernel there is no initrd. [01:07] bjoern_: How about #ubuntu then. That's common between Kubuntu and Ubuntu. [01:07] amichair: That's so, but have you been in an Apple store? [01:07] * ScottK isn't so good with those kinds of problems. [01:08] amichair: That too. [01:08] ScottK: OK, thanks I will try there. [01:08] They have machines set up to cycle into sexy ad screensavers. [01:08] I think viral marketing is quite important for gizmos (which netbooks still are) [01:08] ScottK: KNE is going to ship with Ubuntu One enabled, right? [01:09] jwisser: Not decided for 10.04. We'd need someone to write a KDE client. [01:09] ScottK: Then we need someone to write a KDE client. No-hitch syncing for the average (l)user is something Linux traditionally sucks at. We have an opportunity to be awesome here. [01:10] So point one in the marketing plan is a section of kubuntu.org that this theoretical OEM VP of engineering would look at and go "Wow, I need to have someone look into this." [01:11] As long as point zero is actually having the features. ;-) [01:11] Part of the reason to focus marketing on the OEMs is OEM service contracts come with funding so Kubuntu has more paid devs and the abilty to do more stuff. [01:11] jwisser: Certainly. [01:11] jwisser: Much of the value propositon for Kubuntu Netbook exists today based on the technology and what we've already done. [01:12] So we can start to tell the story. [01:12] ::contemplates:: Working with OEMs could also give us an opportunity on flawless operation on certain hardware. [01:12] *to ensure [01:12] Yes. The existing Canonical OEM contracts are why Kubuntu Netbook works on as much hardware as it does. [01:13] ScottK: I'm just thinking it would be fantastic if our hypothetical OEM could sell a netbook/desktop combo by going "Holy crow, look at the syncing! Isn't that fantastic?" [01:13] Agreed. [01:13] Unfortunately Ubuntu One only sync's between Linux machines, so it's of no help for someone wanting to sync between a Windows desktop and a Linux netbook. [01:14] Could some enterprising Windows dev theoretically write a client? [01:14] (and I have mentioned this point to them and they are waiting for a community developed Windows client) [01:14] jwisser: Yes [01:15] Well, I wasn't even expecting a Windows client. [01:16] OK, I think for what you're looking for it's essential. [01:16] I was thinking that possibly we could get some OEMs to try to sell *ubuntu netbook/desktop combos on the distinction of Ubuntu One alone. [01:16] It's not worth our time to do marketing work that just cannabalizes the existing Linux netbook market. [01:16] I see. [01:16] ::nods:: Fair point. [01:17] For syncing, and OEM would be better off, at least today, making a deal to preinstall a dropbox client. [01:17] and/an [01:18] Right. We need something to convince them that's not so. :-) [01:18] Today it is so. [01:18] Why, specifically? [01:19] Dropbox is cross platform. [01:19] * jwisser waves aside cross-platformness. [01:19] Anything else? [01:19] "This will help you sell more netbooks to people that already use Linux on their desktops" is no help. [01:19] Dropbox is cheaper for more space. [01:20] 50GB for $10 is identical, no? [01:20] jwisser: I'd encourage you to do some research on why people think Nokia bought Trolltech. I suspect that will help you understand the engineering reasons OEMs want a Qt/KDE solution even if they don't know it. [01:21] OK, they've changed it then. Initially it was 10 [01:21] * jwisser goes to do some research on the subject. [01:25] who do I need to pay around here to review and merge some bugfixes? [01:26] JontheEchidna is Mr. Bugs. [01:26] amichair: What do you have? [01:27] I'm working on software-properties [01:28] OK. It's Python, right? [01:28] yep [01:29] OK. I can review that. [01:29] I'm new to that as well, so would love to get feedback [01:29] OK. I'm a medium grade Python hacker. We'll see. [01:30] * amichair is trying to figure out where is bzr branch lives... [01:32] oh wait, I need to push (sorry, svn user...) [01:33] is it just 'bzr push'? [01:33] tell it where if you havent before [01:34] like bzr push lp:~amichair/software-properties/doing-stuff [01:34] doing-stuff being your branch name [01:34] ~amichair being your launchpad account [01:35] assuming you were going to do it by pushing somewhere and doing a merge request. i dont think all the sponsors are clear on that process yet though, so debdiffs are still popular [01:36] how can I tell if it's already associated with a remote location? [01:37] In case anyone was wondering, this is what we need to *not* do with our marketing: http://phones.verizonwireless.com/motorola/droid/ [01:39] amichair: i'm looking... [01:40] amichair: bzr info [01:40] maco: ok, I suspected so and didn't see it, so I'll just try what u recommended above [01:42] amichair: You have to commit before you push. [01:43] you may want to look at other branches, too, that aren't listed in 'bzr info' [01:43] oh right...svn users arent used to that [01:43] ScottK: yes, I commited every fix in a separate revision - good habits from svn :-) [01:43] hehe [01:43] OK. [01:43] 'bzr info' can be misleading, since you're not confined to what's in .bzr/branch/branch.conf [01:43] maco: bad-habitted ppl aren't used to that :-) [01:44] why is it sending > 10M ? isn't it supposed to be sending only diffs? [01:44] amichair: i meant svn people arent used to a 2-step process. with svn you just commit and it goes remote always right? whereas here you commit locally and push to get it to the remote server [01:45] probably because the original doesnt exist at ~amichair/ yet [01:45] maco: yep, exactly. [01:45] and future pushes to the same spot will be just the diff [01:45] maco: oh, I figured since it's branched off an existing project, it would know that... [01:46] i think this is also the difference between branching and...um i think cloning? [01:46] one has the entire history. the other doesn [01:46] t [01:47] I started it off with 'bzr branch'... [01:47] well I don't mind, as long as I'm doing what's considered right for u guys :-) [01:47] ok, done [01:48] now where do I find it? what url do I give ScottK to review? [01:48] ah ok...so there's branch and checkout... [01:49] go to your launchpad page and hit the code button [01:49] and it should be listed as one of your branches [01:49] oh I see - it's 'Branches'. my very first branch! [01:50] yes and it seems to have all previous history too [01:51] hmm... no indication of where it actually branched off from the main project [01:51] yeah...i think "init" followed by "checkout" wouldnt have previous history [01:51] it won't unless you're using using stacking [01:51] dtchen: wont what? [01:52] it won't give any indication [01:52] ohok [01:52] that's more of a loggerhead issue, however [01:52] maco: I read that co just takes the main code and tries to push it back there, which I can't. branch lets me work in my own area. [01:53] so, does this look the way u'd like it to? https://code.launchpad.net/~amichai2/software-properties/fixes [01:54] (wish I could change that 2 to an r... really confusing) [01:54] almost [01:54] remember to use the correct changelog-closing syntax, which is LP: #foo [01:54] if you forget the colon or the hash, it's omitted. [01:54] ok, good to know [01:55] dtchen: any way to update the log message retroactively? [01:55] also, debcommit(1) is a good thing [01:55] amichair: the log message isn't that important; the changelog entries are more so [01:55] dtchen: what's that? [01:56] amichair: a highly recommended tool [01:56] if you have devscripts installed (and you should), check the man page for it [01:57] hi. Kubuntu install UI app is using the same strings (text) as Ubuntu Ubiquity ? [01:57] I don't, and I will :-) [01:57] or it is a different package ? [01:57] in a nutshell, you generate commit messages based on entries in debian/changelog. The correct bzr/LP syntax for --fixes is done automatically. [01:58] woah... quite a few dev scripts there :-p [01:59] adiroiban1: I'm pretty sure it's different. [01:59] shtylman: ^^^ ? [02:00] ScottK: can you please point me to the source package / project of the kubuntu-installer [02:00] thanks! [02:00] adiroiban1: It's in the same source package (ubiquity) [02:00] It's just a different front end [02:00] shtylman will know for sure. [02:01] ok. looking at the ubiquity source, it looks like 99% of the strings are reused [02:01] reused / shared [02:03] dtchen: so I manually edit changelog, then use debcommit [files] instead of bzr commit -m? [02:03] amichair: just debcommit -n [02:03] amichair: and if that's satisfactory, do the real commit without -n [02:04] amichair: debcommit takes care of bzr commit -m, as you'll note [02:04] dtchen: oki, and what's the standard for changelog entries? [02:04] amichair: I'm only referring to the changelog syntax for closing bugs [02:04] LP: #foo [02:05] there's some LP-fu on the backend that will link your bzr branch(es) to the bugs, too [02:05] dtchen: bug in general, I see there's urgency, indentation, etc... [02:05] ah, yes, follow the indentation [02:05] dtchen: or if I want to give a better explanation than the bug description, etc. [02:05] urgency doesn't really matter as much for Ubuntu source packages [02:05] dont change the urgency [02:05] as a general rule [02:06] most ubuntu devs dont, some dont even realize that it has an effect and just assume its a debian-only thing. it doesnt have a huge effect really anyway... [02:06] and email address, and datetime... is there a tool that generates all this as well? [02:06] yes [02:06] dch -i [02:06] it does affect build priority, but not in an obvious manner [and not for the typical source upload] [02:06] in .bashrc [02:06] export DEBEMAIL='maco.m@ubuntu.com' [02:06] export DEBFULLNAME='Mackenzie Morgan' [02:06] thats in mine [02:06] set to what yours should be [02:07] and then dch will know what data to fill in [02:08] wow looking at .bashrc may have just told me why i cant get ibus working. i left the s off... [02:09] no seele? aww [02:10] ok, now is there any way to change it retroactively in all them commits? or I'll just do better next time? [02:11] amichair: don't worry about the previous commit messages [02:11] dtchen: and the "LP: #num" is just in the dch freetext? [02:11] amichair: it's in debian/changelog [02:11] I think that's what you're calling "dch freetext" [02:12] dtchen: I mean the text argument to "dch -i" which scott just mentioned [02:13] amichair: yes [02:13] just want to clarify, from now on all I do when a rev is ready is "dch -i bla bla [(LP: #num)]" followed by "debcommit [files]"? and that's it? [02:14] well, I tend to edit stuff in $EDITOR [02:14] a typical workflow for me would be: dch -i -> $EDITOR -> debcommit -n -> debcommit [02:14] that's "dch -ie" instead? [02:15] amichair: Just dch -i will open debian/changelog formated for a new revision ready for you to edit. [02:15] should open in nano i think as the default [02:16] Shudder. [02:16] (i have EDITOR=/usr/bin/vim in my .bashrc though, so vim opens for me) [02:16] so "dch -i" -> edit (e.g. "bla bla [(LP: #num)]" or multiline with asterisks) -> debcommit on -> debcommit ? [02:17] oops, /on/-n/ [02:18] looks reasonable [02:18] (I just set vi as well...) [02:19] okily-dokily! [02:19] thanks guys, you've been very helpful :-) [02:19] ScottK: the branch is at https://code.launchpad.net/~amichai2/software-properties/fixes [02:19] OK [02:19] ScottK: I promise to do the changlog stuff better next time :-) [02:20] ScottK: and I would love any feedback at any level... whatever I can learn from :-) [02:20] Personally, I prefer a debdiff in a bug, but I'm old fashioned. Let me see if I can manage this. [02:21] but I gotta get going now, will check in tomorrow, it can wait till then [02:21] adiroiban1: the strings are the same as ubiquity [02:22] shtylman: thanks! I just wanted to be sure [02:22] thanks everyone! [02:22] the kubuntu frontend looks great :) [02:22] thanks :) [02:23] amichair: whoa, you rock [02:23] that's a lotta fixes [02:24] JontheEchidna: a lot? that's just one day! including learning python :-) [02:24] :o [02:24] JontheEchidna: there's actually a tough one I couldn't close, a crash that looks like a messed up stack frame or something, very strange. [02:25] shtylman: kudos for the great UI. I will come back with some i18n bugs :) [02:25] I could use some help there, maybe tomorrow :-) [02:25] cya! [02:25] wow [02:25] amichair: the one where clicking the checkbox crashes? Yeah, very strange [02:25] it's also been around forever :( [02:26] JontheEchidna: yep. happens also with keyboard. I got to one method call that if commented out crashes, if inlined doesn't crash, and if the first line in the nested call is changed to 'return', still crashes. hence it seems like a corrupt stack at the C level or something... really dunno [02:27] adiroiban1: sounds good [02:27] could be a PyQt issue [02:27] if regular Qt apps had such bugs we would seem them a lot more often, I'd think [02:27] but I really don't know enough about it, that's just a very wild guess :-) [02:28] JontheEchidna: well maybe I'll look deeper into it when I have the time. but I figured I'd start with quantity over quality :-p [02:29] hehe [02:30] anyway, it's past my bedtime. cya guys around! [02:38] hmm pyqt is implemented in C still right? not C++? [02:39] What makes you say that? [02:40] Hey ScottK, I'm sorta back. [02:41] DarkwingDuck: Welcome. [02:41] :) Push though a bit of pain but, I'm starting to try and get back into it. [02:41] JontheEchidna: are you merging with debian testing? [02:42] Lex79: yeah, for the LTS we're merging with squeeze (testing) [02:42] but really it's not that big of a difference for the KDE packages [02:42] since it just means that the latest n' greatest shows up 10 or so days later [02:43] Or 40 [02:43] Since KDE tends to get caught up with other stuff in transitions. [02:43] ok [03:00] could I get a sponsor for bug 477910? [03:00] Launchpad bug 477910 in akonadi "akonadi 1.2.1: new changes from Debian require merging" [Undecided,New] https://launchpad.net/bugs/477910 [03:04] * akonadi . [03:05] Lex79: libs-experimental is going away in 4.4, probably not worth it to merge [03:05] uhm :( [03:05] ok thank you [03:06] no prob. [03:30] JontheEchidna: Looking [03:32] JontheEchidna: Have a look at rmadison libboost1.40-dev and then tell me why I don't want to upload your diff? [03:33] universe, careless of me [03:33] 1.40 for Boost is probably what we want, but we didn't decide yet. [03:34] It's not a big deal. [03:35] should I update the diff or? [03:36] I don't think there's a rush. We'll decide at UDS week after next, so I'd just let it wait. [03:36] ok [03:38] So apparently Flash sucks no matter what OS you use: http://twitter.com/BritishRT/statuses/5488077051 [03:57] I'm wondering if fix_phonon_include patches could be removed for lucid... [03:57] someone knows? [04:24] Nightrose: Script: http://ajax.googleapis.com/ajax/libs/jquery/1.2.6/jquery.min.js:22 [04:24] Nightrose: buzz.kde.org still makes firefox not-happy for me [04:24] it says that script is either busy or not responding === akonadi is now known as nihui [07:12] haha [07:12] anyone know a certain "Herald Strait"? [07:13] the face rings a bell... [07:13] I could swear it's... straitlogger or something [07:15] http://boycottnovell.com/2009/11/07/ubuntu-9-10-works-well/ [08:17] Hi [08:42] what exactly does 'Triaged' mean as a bug status? [08:45] Triaged: the bug supervisor considers that the bug report contains all information a developer needs to start work on a fix. [08:45] from https://help.launchpad.net/Bugs/Statuses [08:46] 2. (Government, Politics & Diplomacy) the principle or practice of allocating limited resources, as of food or foreign aid, on a basis of expediency rather than according to moral principles or the needs of the recipients [10:13] Why are KDE, Kubuntu and you folks so awesome? [10:14] xD [10:14] thanks [10:14] Hi all [10:14] yw, but I demand an answer [10:15] i have not read i am doing support on kubuntu right now [10:15] so [10:15] xD [10:19] :) [10:56] MelisU: Because we have Ninjas [10:56] ~ninjas [10:56] oh, bot's dead [10:57] and apachelogger ain't here [10:58] maco, dtchen, ScottK: I followed your changlog advice of yesterday, but I see it increases the changlog version to 0.75.5ubuntu1 instead of 0.75.6... is this normal? [10:59] Riddell: have you reviewed my debdiff? Can I push changes to bzr or it needs more love? [10:59] maco: yea i know :( that's why i asked for coding help [11:00] is the correct next version 0.75.6 or 0.75.5ubuntu1? [11:02] Quintasan: apachelogger stormed out yesterday, said he needs a week to cool off :-( [11:02] amichair: what's the package? [11:03] Quintasan: software-properties [11:03] amichair: and what are you trying to do exacly? [11:04] hi! i updated my kubuntu to 9.10. now it takes over two minutes until the startup is finished. i created a bootchart: http://h.imagehost.org/view/0687/gerhard-nb-karmic-20091108-1 [11:04] can anybody tell me whats wrong? [11:04] Quintasan: I made a bunch of bugfixes, and the fellas taught me how to make proper changlogs with dch and debcommit, but I see the auto-version-increment is inconsistent... [11:04] sure it is [11:04] Quintasan: so I'm supposed to change it manually? or is this configured somewhere? [11:04] amichair: version format in ubuntu goes like this -> package.version--ubuntu [11:05] amichair: What's the previous version? [11:05] Quintasan: I'm looking down the changelog and see no 'ubuntu' in version numbers, just 0.75.1, 0.75.2,...,0.75.5 [11:06] hmm [11:06] looks like this is a ubuntu specific package [11:06] Quintasan: it's an ubuntu-only package I guess, so is the numbering different? [11:07] amichair: change it manually to 0.75.6 [11:07] Quintasan: am I supposed to fix it manually, or is there something to configure or a param to dch or something like that? [11:07] amichair: dunno about parameter, I usually fix it by hand when version's wrong [11:08] Quintasan: ooh, and I just noticed it says 'kramic' instead of 'unreleased' too [11:08] Quintasan: which I'm assuming from the previous entry is the way to go... [11:08] amichair: I guess they won't kill you for wrong version [11:08] Quintasan: :-) [11:08] amichair: I would replace karmic with lucid if it's an update [11:09] Quintasan: too bad the tools don't make this less error-prone, as is the point of having tools :-) [11:09] amichair: I haven't seen you around here, are you new here or you had a break? [11:09] amichair: oh [11:09] Quintasan: new here [11:09] amichair: dch automatically changes to lucid but I suppose we don't have updated it yet [11:10] didn't update* [11:10] Quintasan: it's my first kubuntu dev work, so I'm learning the basics (thanks!) [11:10] amichair: everyone has to start somewhere :P [11:11] * Quintasan is JontheEchidnas minion [11:11]