[01:15] hrmm, I just updated gmm++ to 4.0.0, and I got an email saying it is (New) and I have to wait...is this normal if you go from something like a 3.1 release to a 4.0 release? or did I fork something up? [01:17] ScottK: gmm++ 4.0.0, can you throw that one out for me? [01:17] I forked up of course [01:17] nixternal: Usually the library package name changes with a soname bump [01:17] grabbed gmm++ instead of getfem++ [01:17] I doubt it. [01:17] Ah [01:17] silly me [01:17] and I updated getfem++ over a week ago :p [01:18] brain->garbage(); [01:21] nixternal: libgmm++-dev | 4.0.0-3 | lucid/universe | all [01:21] So should I reject your upload? [01:22] yes please [01:22] huh? [01:22] shouldn't be -3 [01:23] 4.0.0-0ubuntu1 [01:23] GOne [01:23] thank you sir [01:23] It looks like the source package name changed in LUcid [01:23] * nixternal gets started with the MIRs now that everything is updated [01:27] getfem++ is where libgmm++-dev comes from now. [01:32] right [01:57] w00t, MIRs done for today [01:57] need to 2 MIRs to be processed before I can file 2 more MIRs for KOffice deps [01:58] so, hopefully everything will go through and we can have a good KOffice package [01:58] nixternal: just file them all [02:00] Riddell: yeah, I could do that, but rules are, don't file them if their other deps aren't in main yet [02:00] what rules? [02:00] though in the MIR, I could just put "this depends on bug so-and-so first" [02:00] if you have MIRs for the other deps that's fine [02:01] MIR procedures and check list [02:01] I will go ahead and do them now, since I have the text already done [02:02] nixternal: The format just asks the question are all the deps/build-deps in Main, it doesn't say the answer needs to be yes. [02:07] the new checklist does [02:07] ok, filed [02:08] ok, maybe there isn't a rule...I swore I just read it...I am sure I didn't make it up [03:54] nixternal: you are pretty good at validation stuff :) [04:00] dhillon-v10: seen it all :) [04:01] been doing docs for 15+ years now [04:05] nixternal: wow, didn't know that, been doing docs for about 7 months :) [04:06] yeah, I started with the Linux Documentation Project in 1993, Debian around 1995, KDE around 1997, and a bunch of other crappy projects that have since died :) [04:06] nixternal: It's kind of like when I was riding with the eldest daughter last year and getting somewhat frustrated with her driving and realized that I had a full year of driving experience for every hour she'd driven. [04:06] that's what happens when you fart dust you old man :p [04:07] w00t, inbox zarro [04:07] Yeah. [04:07] * ScottK had inbox zero the other day, but then I realized I'd screwed up my kmail rules. [04:07] lol [04:07] ScottK: when did you start with linux [04:07] ctrl+r in mutt ftw! [04:07] nixternal: so you have been around for a *while* now :) [04:08] dhillon-v10: Relatively recently. I started using it part time in 2003 and full time since 2005. [04:08] off and on, I got fed up with Linux around 2000 and ditched it totally for about a year [04:08] in that year I got addicted to Quake 3 and spent time traveling the USA trying to play professionally, but I wasn't that good :) [04:08] ScottK: nice, so that means I am the new one around here :) [04:09] nixternal: Quake 3 is awesome :) [04:09] Of course I also remember buying my Apple ][ and having the salesman tell me not to bother with buying the extra 32K RAM because 16K was enough. [04:09] I still have my Apple ][ [04:09] and my vic20 and comm64 [04:09] I think mine is in my dad's basement. [04:10] and i found out my atari 2600 is at my brother's house [04:10] I never owned those the Commodore's but did have a job where I sold them. [04:10] i went over there last week and his kids were playing pole position :) [04:10] nixternal: I got my laptop from a university as part of a research program so that was good :) === claydoh_ is now known as claydoh [09:16] good morning all === amik is now known as amichair [09:19] mornin Tm_T [09:26] connection via mobile broadband keep crash nm-kde [09:26] anyone has similar experience? [09:29] freeflying: you are actually able to connect? o.O [09:29] I'm old fashioned and use Kppp [09:30] jussi01: for wireless/wired, its fine [09:30] freeflying: yeah, I have no issues with that either, I use network-manager-gnome if i need the broadband/mobile stuff [09:31] heh [09:31] it has the very awesome mobilr broadband provider stuff for easy setup [09:34] jussi01: I find Kppp easy too, just, well, put the number and you're done [09:34] Tm_T: but who knows the number? /me doesnt... [09:35] jussi01: it's ~same everywhere, *99***1# [09:35] but yeah, provider database is great, makes it easier [09:43] * Sput uses knetworkmanager [10:41] the kde-devel meta-package doesn't exist anymore in Debian testing/Kubuntu, has it been replaced? [10:52] Mamarok: kde-devel is still there [10:57] hm, somebody told me Debian testing didn't have it anymore [11:07] shadeslayer: weeh, congrats [11:07] shadeslayer: already got a sponsor for it? [11:07] nixternal: ping [11:11] hm [11:12] Riddell: is help.kubuntu.org going to mirror help.ubuntu.com or will it be independent? [11:13] Riddell: about the USB problem, it could be a SLOID bug, dfaure just made a patch for: https://bugs.kde.org/168914 [11:13] SOLID* [11:14] JontheEchidna: so is someone going to port kfi? [11:15] apachelogger: can't say I've heard of it [11:15] Riddell: yeah, there seems to be lack of documentation from the documentation team ;) [11:16] there is a spec from jaunty suggesting help.kubuntu.org to mirror the ubuntu thingy, and on the lucid todo there is an entry that rich is in the process of wirting documentation for help.kubuntu.org [11:19] I suspect nixternal knows all about it then [11:24] shtylman: any progress on a kubuntu-installer-theme package? [11:38] apachelogger: yeah whee :D [11:38] apachelogger: no sponsor but i wanted to ask if the naming etc stuff was ok? [11:38] shadeslayer: what naming? [11:38] still have to talk to motu for sponsors :) [11:39] apachelogger: the package names which have ~karmic~ppa0 etc [11:39] apachelogger: for eg : https://launchpad.net/~rohangarg/+archive/kde-extra/+sourcepub/941646/+listing-archive-extra [11:39] Shouldn't it be in lucid first? [11:40] apachelogger: anyhow everything is fine right? [11:40] persia: i also did a lucid build [11:40] persia: https://launchpad.net/~rohangarg/+archive/kde-extra/+packages [11:40] yes, first we need to get it to lucid anyway ;) [11:40] :) [11:40] shadeslayer: ~karmic1~ppa0 [11:40] apachelogger: yes? [11:40] the karmic needs a number attached ;) [11:41] apachelogger: i should change it to that? ok [11:41] anyhow [11:41] shadeslayer: yes [11:41] ah ok :) [11:41] * apachelogger looks at lucid [11:41] ill do it asap :) [11:41] anything else? [11:42] nope [11:42] looking at lucid right now [11:43] ok [11:44] shadeslayer: quilt should be removed from the build-depends in debian/control [11:44] apachelogger: kopete-facebook? [11:45] yes [11:45] always watch the output of debuild [11:45] W: kopete-facebook source: quilt-build-dep-but-no-series-file [11:45] W: kopete-facebook source: patch-system-but-no-source-readme [11:45] W: kopete-facebook source: patch-system-but-direct-changes-in-diff .directory [11:46] the first 2 warnings are because of the quilt build-dependency and the last one because you accidently got one of dolphin's configs added [11:46] shadeslayer: also your debian/changelog entry is broken [11:47] which is why you should only use dch to do anything ;) [11:47] ah ok [11:48] parsechangelog/debian: warning: debian/changelog(l3): unrecognised line [11:48] LINE: * New Upstream release [11:48] parsechangelog/debian: warning: debian/changelog(l10): badly formatted trailer line [11:48] LINE: -- Rohan Garg Mon, 25 Jan 2010 01:39:31 +0530 [11:48] apachelogger: http://paste.ubuntu.com/362547/ [11:48] do apparently something is wrong with your first change line and the bottom line format is somehow messed up [11:49] apachelogger: yeah i saw that error,but i couldnt figure out what was wrong in that line [11:49] first things first [11:49] shadeslayer: please edit the lucid package and then re-backport that package to karmic [11:50] ok [11:50] otherwise you will almost certainly get lost in what you changed where [11:50] ok sure :) [11:50] so, first open debian/control [11:50] ill do the lucid build first [11:50] there remove "quilt, " from the build-depends [11:51] then remove the .directory file in the main source directory [11:51] apachelogger: already done [11:51] then open debian/changelog and take a look at what makes your first entry line different from the one from Scott's previous changelog entry [11:51] same with the bottom line [11:52] (tip: in both cases you have a whitespace issue) [11:52] ah [11:53] had a extra whitespace after every line apart from the first line [11:53] apachelogger: um are even the amount of whitespaces set? [11:54] yes [11:54] the format is very very strict [11:54] yeah i can see that :P [11:55] that is why ScottK mentioned that you should use dch to create the first entry and then only change the content, but not the stuff around it ;) [11:55] ok [11:56] apachelogger: ok after editing the changelog,i rebuild it right? [11:56] debuild -S -sa [11:56] yes [11:57] yeah still have a badly formatted trailer line >< [11:57] hold one [11:58] oh, btw, after you did one upload you can build with debuild -S -sd [11:58] that way you do not need to upload the tarball again, but just the changes, dsc and diff files [11:58] which is of course a lot faster most of the time ;) [11:59] oh thats good :) [12:02] shadeslayer: Hey dude, I sorted the logging in via kdm problem. Was some dodgy files in /tmp. I wish I'd moved them rather than deleting them, so I could have investigated more. Plasma-netbook still doesn't start automatically though - so that's next on my list ;-) [12:03] /var/log/kdm.log didn't tell me anything in the end :-s [12:04] apachelogger: http://pastebin.com/f37ca2478 [12:05] Trouble_: hmm well you could always put a pre kde script and forget about it :P [12:05] apachelogger: dunno. I started college last week so I have way less time now [12:05] shadeslayer: looks good [12:05] apachelogger: no changes to version> [12:05] like -0ubuntu0 ? [12:06] yay, 1404.37 < CIA-63> sebas * r1080019 /trunk/www/sites/www/ (5 files in 4 dirs): Release KDE 4.4 RC2 [12:06] JontheEchidna: groovy :) [12:06] Tm_T: :) [12:06] JontheEchidna: the being a college student, not the having less time ;) [12:06] JontheEchidna: i start mine in 3 days :P [12:06] shadeslayer: well, the thing is [12:07] shadeslayer: technically you should not upload -NubuntuN versions [12:07] shadeslayer: but always suffix them with ~ppaN or ~VERSIONN~ppaN ;) [12:07] oh ok [12:07] oha [12:07] the version in the changelog is wrong anyway [12:07] so i add this to my version right [12:07] shadeslayer: should be 0.1.5 [12:08] apachelogger: its 0.1.5 [12:08] a ubuntu version number always looks like this: UPSTREAM-DEBIANubuntuUBUNTU [12:08] 0.1.5-0ubuntu1 in this case [12:08] if the package was based of the first revision of a debian package of kopete-facebook 0.1.5 it would be 0.1.5-1ubuntu1 [12:08] yeah thats what i was asking about... and should i add ~lucid1~ppa1 : [12:08] apachelogger: oh, I did give k-n-h a distribution upgrade feature in case kpackagekit's turns out to be inadequate [12:09] JontheEchidna: kpk should work out fine [12:09] does kpk have support for the upgrade quirks that upgrade-manager uses? [12:09] JontheEchidna: but for karmic we need to deploy patches to pk and kpk [12:09] brb... [12:09] JontheEchidna: it is all handled via pk internals, kpk just tells the user that there is a upgrade to lucid [12:10] JontheEchidna: then it just invokes do-upgrade [12:10] which is where the problem lies right now, because it will try to launch the GTK interface [12:10] and that needs to be patched [12:10] ah, we could have it launch upgrade-manager-kde [12:10] though I have not heared back form glatzor on my patch for pk on that [12:10] JontheEchidna: that is what that do-upgrade thingy does [12:11] so we'd be using the same architecture, just launched by kpk [12:11] right [12:11] anyone want noodles ? :P [12:11] nice [12:11] JontheEchidna: technically not even kpk, kpk just launches a script that launches the update infrastracture ;) [12:11] nice @ noodles and @ kpk ;-) [12:11] though I've never had noodles for breakfast :x [12:12] * apachelogger still aint had no breakfast [12:12] its 6 pm here :P [12:12] 7 am here [12:12] * Riddell throws some porridge at apachelogger [12:12] and I need to be at campus in 45 minutes -.- [12:12] weeeh \o/ porridge :D [12:13] apachelogger: ok so the version is 0.1.5-0ubuntu0~karmic1~ppa1 [12:13] I have to leave in 15 minutes, which is when my ride to campus leaves [12:13] I think the campus blocks most ports except for port 80 on their wifi, because neither smtp nor irc work there :( [12:13] um ~lucid1~ppa1 [12:13] will have to talk to the IT dept. to see what's up [12:13] shadeslayer: that will not work [12:14] shadeslayer: foo1 > foo1~bar1 [12:14] JontheEchidna: my uni had even blocked launchpad.net [12:14] shadeslayer: foo1 < foo1+bar1 [12:14] apachelogger: oh.. [12:14] shadeslayer: luckily there's no web filter beyond blind port blockage [12:14] shadeslayer: so you need 0.1.5-0ubuntu1+lucid1~ppa1 now [12:14] shadeslayer: otherwise launchpad will reject the upload [12:15] apachelogger: one sec i need to log this :P [12:15] shadeslayer: though just to make that clear... the upload to ubuntu will still have -0ubuntu1 and just that ... the suffix is just for PPA uploads ;) [12:16] ok [12:16] apachelogger: whats the difference b/w ~ and + [12:18] eek [12:18] yeah can you gys hear me? go disconnected there :) [12:19] *git [12:19] shadeslayer: ~ makes the version smaller + makes it larger [12:19] say you have 0.1 [12:19] then 0.1~foo1 would be lower than 0.1 [12:19] oh.. [12:20] for example if you make a git snapshot before upstream does any release, then you want to use a version lower than 0.1 for sure [12:20] 4.3.0-0ubuntureally42 [12:20] :) [12:20] hehe [12:20] so you could use 0.1~git20100124 [12:20] no matter what is following, the ~ makes it smaller than the part before the ~ [12:20] * persia usually uses 0.0.0.1~ for pre-releases, just to be extra safe [12:21] hmm thats good foo :) [12:21] + does the same thing, just that it makes the version larger [12:21] so 0.1+git20100124 > 0.1 > 0.1~git20100124 [12:21] apachelogger: how do i remove all the .directory files? [12:21] apachelogger: ok :) [12:21] shadeslayer: just remove it and debuild ;) [12:22] apachelogger: by going into each dir? [12:22] well [12:22] you only have it in one dir [12:22] hmmm ok [12:23] unless you added more now ;) [12:23] in the version I downloaded you only have it in the main source dir ;) [12:24] shadeslayer: otherwise you could do find ./ -name ".directory" | xargs rm [12:24] persia: 0.0~ ;) [12:25] though I have been told some tool(s) insist that 0.0 is no valid version [12:25] apachelogger: Breaks the sync script in Soyuz, or yes, 0~ would be preferred. [12:25] * persia discovered this for a package that uses 0~ in Debian [12:26] I see [12:27] 0.0.0.1~ seems the least bad compromise, because most projects only have three sections in versions. [12:27] yeah [12:27] Sput: that is a rather short version :P [12:28] apachelogger: I can't remember the details :) but I found that amusing [12:28] apachelogger: http://paste.ubuntu.com/362565/ [12:29] hmm i guess i need to rename the .orig.tar.gz too [12:29] and the folder too [12:29] Sput: 4:4.1.1+really4.1.1-0ubuntu4 [12:29] Sput: though I have seen better than that too :D [12:30] apachelogger: yeah, something like that :) [12:31] apachelogger: also i just noticed that i have : .gitignore [12:31] i should remove that too right? [12:31] no [12:31] ok [12:31] that is from upstream [12:31] hmm [12:32] Sput: also on offer: 3:3.3.8really3.3.7-0ubuntu11.1 [12:32] you need to do that because you can't force downgrades, right? [12:32] if that was to be in a PPA it would be 3:3.3.8really3.3.7-0ubuntu11.1~ppa1, and backported something like 3:3.3.8really3.3.7-0ubuntu11.1~jaunty1~ppa1 ;) [12:32] Sput: right [12:34] now add to that a package with screwed upstream versioning... mplayer-1.0_rc4_p20091026 comes to mind, though there's worse [12:34] apachelogger: ok i think everything went without errors : http://paste.ubuntu.com/362569/ [12:35] apachelogger: should i dput? [12:36] shadeslayer: W: kopete-facebook source: diff-contains-svn-control-dir icons/.svn [12:36] W: kopete-facebook source: native-package-with-dash-version [12:36] apachelogger: yeah but as you said thats upstream right? [12:36] oh right, didnt see it earlier [12:37] but the second is a major issue [12:37] apachelogger: ok what does the error mean? [12:37] did debuild not warn you about anything? [12:37] nope [12:37] well [12:37] check your .orig.tar.gz [12:37] apachelogger: thats the complete output of debuild -S -sa [12:37] apparenlty debuild was unable to find it [12:38] apachelogger: kopete-facebook-0.1.5.orig.tar.gz [12:38] wrong name, see what I told you yesterday about the tarball name [12:38] with a _ ? [12:38] yes [12:38] that is important, anything but NAME_VERSION.orig.tar.gz will be ignored [12:38] ah.. [12:39] dpkg-source: info: building kopete-facebook in kopete-facebook_0.1.5-0ubuntu1+lucid1~ppa1.tar.gz [12:39] that is why debuild built its own tarball [12:39] which then made the package a native package (i.e. a package where Debian/Ubuntu is upstream themself, so there is no individual upstream tarball) [12:39] which is of course only legitimite for real native packages ;) [12:40] ah.. [12:40] for absolutely new packages [12:40] apachelogger: E: kopete-facebook_0.1.5-0ubuntu1+lucid1~ppa1_source.changes: bad-ubuntu-distribution-in-changes-file lucid [12:41] ignore it? [12:41] yes, ignore that [12:42] since it doesnt recognise lucid :P [12:42] okies [12:42] ready to upload.. should i delete the other lucid package? [12:42] shadeslayer: in the ppa? [12:42] apachelogger: yeah [12:43] no, it will be replaced by the new version automagically [12:43] ok [12:43] so now the upload.. [12:44] Successfully uploaded packages. [12:46] i love it when launchpad sends you the mail :P [12:48] ok i think i need to change all the package names :P [12:49] apachelogger: btw do i have to remove the patch folder everytime or is there some procedure for that? [12:49] <\sh> apachelogger: done -> jabber [12:49] \sh: thx :) [12:50] <\sh> apachelogger: welcome :) [12:50] shadeslayer: no, you just need to get the right package [12:51] shadeslayer: to get your most recent PPA version: go to the PPA page => look for the .dsc file => copy the url => dget URL => dpkg-source -x DSCFILE [12:51] dget https://edge.launchpad.net/~rohangarg/+archive/kde-extra/+files/kopete-facebook_0.1.5-0ubuntu1+lucid1~ppa1.dsc && dpkg-source -x kopete-facebook_0.1.5-0ubuntu1+lucid1~ppa1.dsc [12:52] for example [12:52] apachelogger: i meant that i have to change rekonq and choqok package names to fit the naming policy [12:52] the versioning policy! [12:52] not naming :P [12:53] and now, you do not need to [12:53] yeah the same :) [12:53] doesnt have much use now anyway [12:53] anyhow [12:53] hmm.. [12:53] gotta run [12:53] cya [12:53] apachelogger: one sec [12:53] where do i upload it to get sponsors? [12:54] meh hes gone :) [13:32] ScottK: 4.3.5 is all built and has had a couple of testers, think I can upload to karmic-backports? [14:00] Riddell: If you think it's ready, I'm OK. I'm slightly concerned that I read comments on the KDE lists that it had zero testing before release, but I'm good if you're good. [14:00] Riddell: Since backports build at a low priority, it might be best to do it on Friday? [14:02] bah, waiting [14:04] Uploading when the buildds aren't busy gives us fewer complaints due to archive skew. [14:29] * Riddell gets excited at kdebindings getting to 71% compiled and going [14:40] Riddell: awesome [14:50] Riddell: :o [14:50] failed at 98% ! [14:50] life is cruel [14:51] Riddell: error? [14:52] http://paste.ubuntu.com/362641/ [14:54] Hello, the link to the KDE SC 4.4 RC2 announcement is wrong here: http://www.kubuntu.org/news/kde-sc-4.4-rc-2 [14:54] It's point to the KDE SC 4.4 RC1 announcement [14:54] ulysses: um no [14:55] Riddell: free after 30 mins or so? [14:56] ulysses: fixed, thanks [14:56] shadeslayer: pardon? [14:57] Riddell: need to talk to you after 30-45 mins [14:57] I'm here all day [14:59] nixternal: amazing where he shows up http://mail.gnome.org/archives/marketing-list/2010-January/msg00120.html [15:04] Riddell: I uploaded this night kde-l10n for 4.3.5 in staging [15:06] Lex79: yeah saw that, we can probably copy those directly to backports [15:08] Riddell: just curiosity, what happens since changelog version says karmic instead karmic-backports? it will change automatically to karmic-backports after the copy? [15:08] no, that'll stay [15:08] ah [15:19] Lex79: did sandsmark get the phonon patch done? I saw he said he was testing it [15:20] re [15:21] Riddell: no he didn't for now [15:22] ho hum [15:22] let me know if you think I should try and poke him [15:22] Riddell: I poke him every day :( :) [15:23] I think we are friends at this point LoL [15:51] Riddell: where was the grouping in categories for kickoff disabled last time? I cannot find it. [15:51] neversfelde: it's in /etc/xdg/menus/kde4-applications.menu [15:51] ok, thanks [15:52] which is in kde4libs [15:52] without the prefix [15:58] oh oh oh [15:58] hold on [15:58] did jontheechnida not deactivate it upstream> [15:58] ? [15:58] apachelogger: deactivate the patch? [15:59] well the grouping in internet? [15:59] ah, dunno [15:59] neversfelde: best check kde svn first [15:59] I booted it from 4.3 because of its incosistency with the rest of the menu [15:59] ok [15:59] there was no progress for 4.4 so I asked jonny to boot it again in SVN [16:01] IIRC it was booted and then came back. [16:02] ScottK: I deliberately only booted it from the 4.3 branch but not trunk [16:02] giving the author a chance to work things out [16:02] which did not happen [16:02] neversfelde: not yet removed from 4.4 [16:02] doing that now [16:02] OK. Time to do it again then. [16:02] and trunk too this time [16:06] Uhm, it was reported, that bug 503070 wasn't fixed in kde-l10n-sk [16:06] Launchpad bug 503070 in kde-l10n-sk "kde-l10n-** 4:4.3.2-0ubuntu1 fails to install (tries to overwrite kimagemapeditor.mo from kde-i18n-**)" [Undecided,Confirmed] https://launchpad.net/bugs/503070 [16:07] kde rev 1080092 [16:07] http://websvn.kde.org/trunk/?rev=1080092&view=rev | svn://anonsvn.kde.org/home/kde/trunk -r 1080092 [16:07]