/srv/irclogs.ubuntu.com/2013/06/12/#kubuntu-devel.txt

ahoneybun__hello all00:59
ahoneybunhello01:33
ahoneybunhello all02:51
ahoneybunhey palasso03:17
palassohey ahoneybun ;)05:11
soeegod morning06:06
shadeslayerRiddell: ScottK is LGPL compatible with GPL v2?09:35
Riddellshadeslayer: which LGPL, there's three of them.  compatible to do what?09:43
Tm_TScottK is LGPL?09:43
shadeslayersaidinesh5: ^^09:43
shadeslayerhah09:44
* saidinesh5 checks09:44
shadeslayerRiddell: would it be possible for you to evaluate https://github.com/vovoid/vsxu for inclusion in the ubuntu archive?09:44
shadeslayerfrom a source/license PoV09:44
* Riddell clones09:45
RiddellVisualizations, project files and art provided with this release:10:00
Riddell    You may use them as you see fit, but we reserve the right to decide wether10:00
Riddell    or not you can remix them.10:01
Riddellshadeslayer: so the visualisation files can't be included10:01
Riddell  All design and graphic content/skins etc (c) Vovoid Media Technologies AB10:01
Riddell  are provided to you as-is, not for remixing.10:01
Riddellnor can they10:01
shadeslayersaidinesh5: ^^10:01
Riddell  Example assets:    Raya (c) Katie De Sousa.10:01
Riddellno licence on that10:01
saidinesh5Ah10:02
Riddellshadeslayer, 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
saidinesh5Oh10:10
saidinesh5and LGPL2.1 ?10:10
Riddellyes, that's the same as LGPL 2+10:10
saidinesh5no i mean is GPLv2 compatible with LGPL2.1 ?10:11
Riddellyes that's fine10:11
Riddellfor both linking and distributing together10:11
saidinesh5Ah10:11
saidinesh5Riddell: which bits are using LGPL3+ ?10:11
Riddell./tools/socket_library/trunk/src/10:12
Riddellsays   find . -name *cpp | xargs licensecheck | grep LGPL10:12
saidinesh5Ahh10:13
Riddellso maybe those bits don't get linked in, I'm not sure10:14
saidinesh5yep those arent linked afaik10:15
apolmaybe kdevelop should depend on kate-data? https://bugs.kde.org/show_bug.cgi?id=31818810:48
ubottuKDE bug 318188 in general "Adding snippet repository fails with clean install: missing file" [Normal,Resolved: downstream]10:48
Riddellapol: yeah I'll add that10:50
Riddellapol: 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 output10:51
apolok10:52
Riddellshadeslayer: a person has e-mailed me asking for plasma active 4 packages pointing at http://mail.kde.org/pipermail/active/2013-May/006136.html10:53
Riddellshadeslayer: 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 yet10:53
Riddellah it's on k-d as well10:55
QuintasanRiddell: I am to schedule a packaging sprint for PA so we can get the packages in shape10:56
QuintasanI'll do that after the damn exams10:57
Riddellvery cool10:57
QuintasanRiddell: as for KTp, I'm putting uploading onhold till I get it into Debian since I believe I just just became the maintainer of it10:58
QuintasanMight as well as attempt to get DM10:58
RiddellQuintasan: mm that sounds like something that could take time11:03
QuintasanRiddell: Getting it to Debian - no. Getting DM - more likely11:15
QuintasanRiddell: When I get it to Debian I'll just ask you to sync it, or ScottK, whoever has rights to perform this magic11:16
RiddellQuintasan: mm well be careful it doesn't end up taking weeks when people could be using it and testing it11:19
QuintasanRiddell: Should uploading that take more than 3 days from now on I'll just throw in the whole stack into our repos11:20
Riddellsounds a good plan11:22
Riddellhi tariq_ 11:29
Quintasanlol11:30
QuintasanIt's almost like apachelogger's reaction to python11:30
tariq_Hi RIddell!11:30
tariq_still getting to grips with this IRC!11:31
BluesKajHey all12:48
=== juancarlospaco_ is now known as juancarlospaco
murthyhello everyone15:12
ahoneybunmurthy: hello15:14
Riddellhi murthy 15:14
* Riddell blogs http://blogs.kde.org/2013/06/12/nice-e-mail15:16
murthywe here some in the #kubuntu channel15:17
murthy*hear15:17
ahoneybunRiddell: always getting great emails :)15:18
murthyI have some doubts about updating a changelog for a merge15:21
Riddellmurthy: what do you doubt?15:22
murthya 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/control15:30
murthy given by grab-merge and the merged one now  15:30
murthyRiddell: ^15:31
* Riddell waits for paste15:32
murthyhttp://paste.kde.org/771608/15:32
murthy^the file in conflict15:32
murthyhttp://paste.kde.org/771614/15:33
murthy^ the new one15:33
Riddellmurthy: please use   diff -u  and paste that again15:33
murthyRiddell: between the two?15:34
Riddellyes15:34
murthyok15:34
Riddellhttp://paste.kde.org/771608/ does not use diff -u15:34
murthyRiddell: I couldn't get you15:37
murthyRiddell: http://paste.kde.org/771608/ is generated by grab-merge script15:38
murthyRiddell: http://paste.kde.org/771626/15:38
murthythats the one with diff -u of both the control files15:38
Riddellhmm, I'm not sure it is :)15:40
Riddellanyway, build-deps looks like no changes needed so keep debian15:40
RiddellX-Python-Version need to work out if that's needed (by dh_python or something like that)15:40
RiddellBreaks: python-albatross-common   probably still needed, check changelog15:41
RiddellBreaks: python-albatross likewise15:41
Riddellchanges to Maintainer: are needed if there's any ubuntu changes15:41
Riddellvoila15:41
Riddellmurthy: how did you get on with kdiff3 ?15:41
murthyRiddell: why what?15:42
Riddellmurthy: what why what?15:43
murthyRiddell: What about kdiff3?15:44
murthyRiddell: have you noticed python in build-depends ?15:44
Riddellmurthy: did you merge it?15:45
murthyRiddell: you mean the file or the status of the merge request?15:46
Riddellmurthy: the package of kdiff3 needs merged https://merges.ubuntu.com/universe.html15:46
murthyoh :D15:46
murthyI thought you were talking about the kdiff app15:47
murthyI am doing albatross now15:47
murthy#118994215:47
murthyLP : #118994215:48
murthywhats the syntax?15:48
Riddellbug 118994215:48
ubottubug 1189942 in albatross (Ubuntu) "Please merge albatross 1.36-5.5 (universe) from Debian unstable (main)" [Undecided,Confirmed] https://launchpad.net/bugs/118994215:48
murthyRiddell:  this "python (>= 2.6.6-3~)" is added to the ubuntu's build-depends have you noticed? 15:50
murthyRiddell: so the resulting merge is a debian one?15:50
Riddellmurthy: it's not needed as far as I can see, python-all would being it in15:50
Riddellmurthy: it's not needed as far as I can see, python-all would bring it in15:50
murthyRiddell: ok, in case if it is need what should i put in the changelog?15:51
Riddellmurthy: merge from debian, remaining changes: add python build-dep (needed for reason foo)15:52
murthyRiddell: so the target is debian15:52
murthyoops15:53
Riddellmurthy: yes, we want to have as few changes from debian as possible15:53
Riddelldon't be afraid of adding them but also don't add them for no reason, it just adds more work15:53
Riddellok I'm out for the evening, good luck15:53
murthysee you later15:55
murthyyofel: are you there?15:57
yofelyes?15:57
murthyyofel: can you help me with a changlog for a merge15:57
murthyyofel: its a very simple one15:58
yofelsure15:58
murthythank you, i will paste the files15:58
murthyyofel: http://paste.kde.org/771608/15:58
murthy^ thats the debian/control file in conflict given by grab-merge15:59
yofelok16:00
murthyyofel: assume all the ubuntu stuff is correct, now update the  changelog which i will paste now16:00
murthyyofel: http://paste.kde.org/771662/16:01
murthythe last entry is mine16:01
murthycorrect that please16:01
yofelmurthy: well, Continuing the line, you add "Remaining changes:" and then list every change that you had to add to the debian package16:03
murthyyofel: can you do that and show me?16:04
yofelyou don't need to document the maintainer update though16:04
murthyyofel: just this one changelog16:05
yofelmurthy: 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 example16:08
murthyyofel: ok i will try16:09
shadeslayeryofel: can you send me a test mail at rohangarg AT kubuntu dot org ?16:16
yofelshadeslayer: done16:23
shadeslayerthat subject ...16:23
yofelI couldn't resist :P16:23
shadeslayer:D16:24
shadeslayerthe error mail usually has the same subject ;)16:24
murthyyofel: http://paste.kde.org/771692/16:27
murthythe updated changelog16:27
yofelmurthy: looking16:47
yofelmurthy: do we really still need that build-dep on python?16:48
yofelrest looks fine, except that I don't know enough about python packaging to decide what X-Python-Version should be set to16:48
murthyyofel: no it has to be checked, but for now, i am concerned about the changelog16:48
murthyyofel: so expect the python stuff everything ok(in case of the changelog wordings)?16:49
yofelmurthy: change "Update" to "Add" or "Set" as that's not really an update of anything but a new thing16:49
murthyok16:50
yofelother than that, the changelog is fine for the changes in the control file16:50
murthyok thank you, i will check for the phthon build-dep and update the changelog accordingly16:51
=== murthy is now known as murthy_
=== palasso_ is now known as palasso
vHandaRiddell: Could you please verify this package? https://sourceforge.net/projects/oscaf/files/shared-desktop-ontologies/0.11.0/18:49
vHandashadeslayer: ^18:49
yofelvHanda: what do you need verified?18:51
vHandajust that the package is fine18:51
vHandaand that I haven't done anything stupid18:51
vHandas/package/tarball18:51
yofelhm, looks fine on first glance18:53
vHandacool, thanks18:54
vHandaIt looked fine to me as well, but I wanted to be sure before I made the release announcement18:54
ahoneybunhello valorie19:07
valoriegreets21:07
ahoneybunvalorie: hello21:09
valoriehello, ahoneybun21:11
ahoneybunvalorie: littlegirl has been really working hard21:11
valorieI saw what you said the first time; I always read all the scrollback21:11
valorieI saw that21:11
ahoneybunoh21:11
valorieI sort of stepped back because it seemed she was doing her work off the wiki for some reason21:14
valorieso many pastebins!21:14
valorieonce she's slowed down, I'll look21:14
ahoneybunto see the work before saving21:14
valorieit would be nice to get all our pages with a common format21:14
valorieI was working on that as I could21:14
ahoneybunyea21:14
valorieRiddell: lovely blog!21:18
ahoneybunvalorie: did you see the rewrite of the managing repos21:19
ahoneybunhttps://wiki.kubuntu.org/Kubuntu/KubuntuDocs/Basic/ManagingRepositories21:20
valoriewth, why do we have the old way to add repositories, instead of the apt-add-repo way?21:22
valoriewhich is much superior21:22
ahoneybunoh21:22
valorienot a good idea at all, IMO21:22
valorieperhaps a link to the old way, for people running ancient versions21:22
valoriebut seriously, those have long been EOL21:23
ahoneybunlittlegirl is running 10.0421:23
ahoneybunhow would you remove them then?21:23
valorieoh, I dunno21:24
valoriesec21:24
valoriegrrr, I had a good explanation of that, now it's gone21:25
valorie:(21:25
valorieoh, well21:25
valorieshort answer: sudo ppa-purge ppa:<repository-name>/<subdirectory>21:27
ahoneybundoes that work without additional software?21:27
valoriewhat?21:27
valorieI'm not sure what you mean21:27
valorieppa-purge is something we should document anyway, for those who have added problematic PPAs21:28
valorieanyway, I see no reason to make that page enormous by documenting an outdated method of adding and removing repos21:29
valoriebut that's just my opinion21:29
ahoneybuntrue21:30
ahoneybunI'm ok with making it more uptodate21:30
ahoneybunup to date21:30
valorieI'm just wondering why good work was removed, and replaced with old stuff21:31
ahoneybunwell I thought we needed work done on how to deal with ppa;s21:32
valoriesure21:35
valorieI was wrong though, there is a ppa-purge package21:35
valoriehttp://www.webupd8.org/2009/12/remove-ppa-repositories-via-command.html21:35
* valorie goes to find official documentation of this21:35
valorieso otherwise it can be done thus: sudo add-apt-repository --remove ppa:someppa/ppa21:37
yofelthere's 2 definitions of "remove" mixed here21:37
valorieprobably a better idea to not introduce a package21:37
valorietrue21:37
yofeladd-apt-repository --remove -> disables the source entry but keeps the packages21:37
yofelppa-purge -> removes the PPA and downgrades what it can21:38
valorieand there are cases for doing both21:38
valorieor either21:38
ahoneybunvalorie: do what you think is best and I will work on it later21:39
ahoneybungtg21:39
valoriehttps://launchpad.net/ubuntu/precise/+package/ppa-purge21:39
valoriesee you later21:39
ahoneybunyea \21:39

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