[00:59] hello all [01:33] hello [02:51] hello all [03:17] hey palasso [05:11] hey ahoneybun ;) [06:06] god morning [09:35] Riddell: ScottK is LGPL compatible with GPL v2? [09:43] shadeslayer: which LGPL, there's three of them. compatible to do what? [09:43] ScottK is LGPL? [09:43] saidinesh5: ^^ [09:44] hah [09:44] * saidinesh5 checks [09:44] Riddell: would it be possible for you to evaluate https://github.com/vovoid/vsxu for inclusion in the ubuntu archive? [09:44] from a source/license PoV [09:45] * Riddell clones [10:00] Visualizations, project files and art provided with this release: [10:00] You may use them as you see fit, but we reserve the right to decide wether [10:01] or not you can remix them. [10:01] shadeslayer: so the visualisation files can't be included [10:01] All design and graphic content/skins etc (c) Vovoid Media Technologies AB [10:01] are provided to you as-is, not for remixing. [10:01] nor can they [10:01] saidinesh5: ^^ [10:01] Example assets: Raya (c) Katie De Sousa. [10:01] no licence on that [10:02] Ah [10:10] shadeslayer, saidinesh5: the cpp code is a mix of GPL 2, GPL 2+, LGPL 2+ and LGPL 3+. GPL 2 isn't compatible with LGPL 3+ [10:10] Oh [10:10] and LGPL2.1 ? [10:10] yes, that's the same as LGPL 2+ [10:11] no i mean is GPLv2 compatible with LGPL2.1 ? [10:11] yes that's fine [10:11] for both linking and distributing together [10:11] Ah [10:11] Riddell: which bits are using LGPL3+ ? [10:12] ./tools/socket_library/trunk/src/ [10:12] says find . -name *cpp | xargs licensecheck | grep LGPL [10:13] Ahh [10:14] so maybe those bits don't get linked in, I'm not sure [10:15] yep those arent linked afaik [10:48] maybe kdevelop should depend on kate-data? https://bugs.kde.org/show_bug.cgi?id=318188 [10:48] KDE bug 318188 in general "Adding snippet repository fails with clean install: missing file" [Normal,Resolved: downstream] [10:50] apol: yeah I'll add that [10:51] apol: probably also worth that being noted in the sources, in a README (it points at http://www.kdevelop.org/index.html?filename=HEAD/requirements.html but that doesn't exist) or better yet in cmake config output [10:52] ok [10:53] shadeslayer: a person has e-mailed me asking for plasma active 4 packages pointing at http://mail.kde.org/pipermail/active/2013-May/006136.html [10:53] shadeslayer: I'm not sure what martin's e-mail there is saying though, I don't think there's such a thing as PA 4 yet [10:55] ah it's on k-d as well [10:56] Riddell: I am to schedule a packaging sprint for PA so we can get the packages in shape [10:57] I'll do that after the damn exams [10:57] very cool [10:58] Riddell: as for KTp, I'm putting uploading onhold till I get it into Debian since I believe I just just became the maintainer of it [10:58] Might as well as attempt to get DM [11:03] Quintasan: mm that sounds like something that could take time [11:15] Riddell: Getting it to Debian - no. Getting DM - more likely [11:16] Riddell: When I get it to Debian I'll just ask you to sync it, or ScottK, whoever has rights to perform this magic [11:19] Quintasan: mm well be careful it doesn't end up taking weeks when people could be using it and testing it [11:20] Riddell: Should uploading that take more than 3 days from now on I'll just throw in the whole stack into our repos [11:22] sounds a good plan [11:29] hi tariq_ [11:30] lol [11:30] It's almost like apachelogger's reaction to python [11:30] Hi RIddell! [11:31] still getting to grips with this IRC! [12:48] Hey all === juancarlospaco_ is now known as juancarlospaco [15:12] hello everyone [15:14] murthy: hello [15:14] hi murthy [15:16] * Riddell blogs http://blogs.kde.org/2013/06/12/nice-e-mail [15:17] we here some in the #kubuntu channel [15:17] *hear [15:18] Riddell: always getting great emails :) [15:21] I have some doubts about updating a changelog for a merge [15:22] murthy: what do you doubt? [15:30] a package has only 1 conflicting file which is debian/control, grab-merge script generates the source from A(debian), B(ubuntu) and produces C which contains the conflicting file with the two difference with markings. Now the debian/control segments that are in conflict in A(debian) is not right and is totally ignored by choosing all the details from B(ubuntu). What will be my changelog entry and is C ubuntu or debian. I will paste the debian/control [15:30] given by grab-merge and the merged one now [15:31] Riddell: ^ [15:32] * Riddell waits for paste [15:32] http://paste.kde.org/771608/ [15:32] ^the file in conflict [15:33] http://paste.kde.org/771614/ [15:33] ^ the new one [15:33] murthy: please use diff -u and paste that again [15:34] Riddell: between the two? [15:34] yes [15:34] ok [15:34] http://paste.kde.org/771608/ does not use diff -u [15:37] Riddell: I couldn't get you [15:38] Riddell: http://paste.kde.org/771608/ is generated by grab-merge script [15:38] Riddell: http://paste.kde.org/771626/ [15:38] thats the one with diff -u of both the control files [15:40] hmm, I'm not sure it is :) [15:40] anyway, build-deps looks like no changes needed so keep debian [15:40] X-Python-Version need to work out if that's needed (by dh_python or something like that) [15:41] Breaks: python-albatross-common probably still needed, check changelog [15:41] Breaks: python-albatross likewise [15:41] changes to Maintainer: are needed if there's any ubuntu changes [15:41] voila [15:41] murthy: how did you get on with kdiff3 ? [15:42] Riddell: why what? [15:43] murthy: what why what? [15:44] Riddell: What about kdiff3? [15:44] Riddell: have you noticed python in build-depends ? [15:45] murthy: did you merge it? [15:46] Riddell: you mean the file or the status of the merge request? [15:46] murthy: the package of kdiff3 needs merged https://merges.ubuntu.com/universe.html [15:46] oh :D [15:47] I thought you were talking about the kdiff app [15:47] I am doing albatross now [15:47] #1189942 [15:48] LP : #1189942 [15:48] whats the syntax? [15:48] bug 1189942 [15:48] bug 1189942 in albatross (Ubuntu) "Please merge albatross 1.36-5.5 (universe) from Debian unstable (main)" [Undecided,Confirmed] https://launchpad.net/bugs/1189942 [15:50] Riddell: this "python (>= 2.6.6-3~)" is added to the ubuntu's build-depends have you noticed? [15:50] Riddell: so the resulting merge is a debian one? [15:50] murthy: it's not needed as far as I can see, python-all would being it in [15:50] murthy: it's not needed as far as I can see, python-all would bring it in [15:51] Riddell: ok, in case if it is need what should i put in the changelog? [15:52] murthy: merge from debian, remaining changes: add python build-dep (needed for reason foo) [15:52] Riddell: so the target is debian [15:53] oops [15:53] murthy: yes, we want to have as few changes from debian as possible [15:53] don't be afraid of adding them but also don't add them for no reason, it just adds more work [15:53] ok I'm out for the evening, good luck [15:55] see you later [15:57] yofel: are you there? [15:57] yes? [15:57] yofel: can you help me with a changlog for a merge [15:58] yofel: its a very simple one [15:58] sure [15:58] thank you, i will paste the files [15:58] yofel: http://paste.kde.org/771608/ [15:59] ^ thats the debian/control file in conflict given by grab-merge [16:00] ok [16:00] yofel: assume all the ubuntu stuff is correct, now update the changelog which i will paste now [16:01] yofel: http://paste.kde.org/771662/ [16:01] the last entry is mine [16:01] correct that please [16:03] murthy: well, Continuing the line, you add "Remaining changes:" and then list every change that you had to add to the debian package [16:04] yofel: can you do that and show me? [16:04] you don't need to document the maintainer update though [16:05] yofel: just this one changelog [16:08] murthy: try it yourself and I'll tell you what's wrong ;) take http://bazaar.launchpad.net/~kubuntu-packagers/kubuntu-packaging/digikam/view/head:/debian/changelog as example [16:09] yofel: ok i will try [16:16] yofel: can you send me a test mail at rohangarg AT kubuntu dot org ? [16:23] shadeslayer: done [16:23] that subject ... [16:23] I couldn't resist :P [16:24] :D [16:24] the error mail usually has the same subject ;) [16:27] yofel: http://paste.kde.org/771692/ [16:27] the updated changelog [16:47] murthy: looking [16:48] murthy: do we really still need that build-dep on python? [16:48] rest looks fine, except that I don't know enough about python packaging to decide what X-Python-Version should be set to [16:48] yofel: no it has to be checked, but for now, i am concerned about the changelog [16:49] yofel: so expect the python stuff everything ok(in case of the changelog wordings)? [16:49] murthy: change "Update" to "Add" or "Set" as that's not really an update of anything but a new thing [16:50] ok [16:50] other than that, the changelog is fine for the changes in the control file [16:51] ok thank you, i will check for the phthon build-dep and update the changelog accordingly === murthy is now known as murthy_ === palasso_ is now known as palasso [18:49] Riddell: Could you please verify this package? https://sourceforge.net/projects/oscaf/files/shared-desktop-ontologies/0.11.0/ [18:49] shadeslayer: ^ [18:51] vHanda: what do you need verified? [18:51] just that the package is fine [18:51] and that I haven't done anything stupid [18:51] s/package/tarball [18:53] hm, looks fine on first glance [18:54] cool, thanks [18:54] It looked fine to me as well, but I wanted to be sure before I made the release announcement [19:07] hello valorie [21:07] greets [21:09] valorie: hello [21:11] hello, ahoneybun [21:11] valorie: littlegirl has been really working hard [21:11] I saw what you said the first time; I always read all the scrollback [21:11] I saw that [21:11] oh [21:14] I sort of stepped back because it seemed she was doing her work off the wiki for some reason [21:14] so many pastebins! [21:14] once she's slowed down, I'll look [21:14] to see the work before saving [21:14] it would be nice to get all our pages with a common format [21:14] I was working on that as I could [21:14] yea [21:18] Riddell: lovely blog! [21:19] valorie: did you see the rewrite of the managing repos [21:20] https://wiki.kubuntu.org/Kubuntu/KubuntuDocs/Basic/ManagingRepositories [21:22] wth, why do we have the old way to add repositories, instead of the apt-add-repo way? [21:22] which is much superior [21:22] oh [21:22] not a good idea at all, IMO [21:22] perhaps a link to the old way, for people running ancient versions [21:23] but seriously, those have long been EOL [21:23] littlegirl is running 10.04 [21:23] how would you remove them then? [21:24] oh, I dunno [21:24] sec [21:25] grrr, I had a good explanation of that, now it's gone [21:25] :( [21:25] oh, well [21:27] short answer: sudo ppa-purge ppa:/ [21:27] does that work without additional software? [21:27] what? [21:27] I'm not sure what you mean [21:28] ppa-purge is something we should document anyway, for those who have added problematic PPAs [21:29] anyway, I see no reason to make that page enormous by documenting an outdated method of adding and removing repos [21:29] but that's just my opinion [21:30] true [21:30] I'm ok with making it more uptodate [21:30] up to date [21:31] I'm just wondering why good work was removed, and replaced with old stuff [21:32] well I thought we needed work done on how to deal with ppa;s [21:35] sure [21:35] I was wrong though, there is a ppa-purge package [21:35] http://www.webupd8.org/2009/12/remove-ppa-repositories-via-command.html [21:35] * valorie goes to find official documentation of this [21:37] so otherwise it can be done thus: sudo add-apt-repository --remove ppa:someppa/ppa [21:37] there's 2 definitions of "remove" mixed here [21:37] probably a better idea to not introduce a package [21:37] true [21:37] add-apt-repository --remove -> disables the source entry but keeps the packages [21:38] ppa-purge -> removes the PPA and downgrades what it can [21:38] and there are cases for doing both [21:38] or either [21:39] valorie: do what you think is best and I will work on it later [21:39] gtg [21:39] https://launchpad.net/ubuntu/precise/+package/ppa-purge [21:39] see you later [21:39] yea \