[07:23] ari-tczew pinged me privately in oftc, but is no longer connected there, who should I reply to? === soee_ is now known as soee === tazz_ is now known as tazz [07:54] maxyz: he doesn't coordinate with us AFAIK so, best send an email I suppose [08:00] Good morning. [08:01] It was about some gcc5 changes needed for kf5. Well, nevermind, please let me know if you need to bump a lib to v5. [08:32] sitter: I need your help [08:33] I've talked with apol and he said that we need KDevelop in the Kubuntu CI [08:33] how can I get it in there? [08:38] kdevelop needs a kf5 port that has a release planned for <= 6months in the future. then kdevelop and its dependencies on http://anonscm.debian.org/cgit/?q=pkg-kde need to have a kubuntu_unstable branch added. those branches then also need porting to kf5. then kdevelop and its deps need to be added to http://anonscm.debian.org/cgit/pkg-kde/ci-tooling.git/tree/data/projects.json for integration. then someone needs to tell me to sync the CI jobs [08:39] assuming their repository name on debian is not what their repository name on kde is someone also first needs to write manual mapping mapping rules in http://anonscm.debian.org/cgit/pkg-kde/ci-tooling.git/tree/data/upstream-scm.yml before I can sync [08:39] or rather, I could sync but the builds will fail since they can't find their upstream source ^^ [08:42] so we can't get a CI with master? [08:43] ovidiu-florin: where did I say that? :P [08:44] so we can? [08:44] assuming a release is planned in due time sure [08:44] guys 14.04.3 is labeled as "beta" in startup disk creator: http://www.dodaj.rs/?a/XA/3wsiwEEC/snapshot21.png [08:44] I'm working on the Plasma Mobile SDK. I'm not sure I understud the whole process, but my current task is to get KDevelop Maste into the CI so we can make a docker image based on that [08:45] ovidiu-florin: same process applies minuse the 6months rule [08:45] has a different file for the projects list though http://anonscm.debian.org/cgit/pkg-kde/ci-tooling.git/tree/data/projects_mci.json [08:47] snele: I wonder where startup disk creator gets it's labeling from... [08:47] Perhaps some mirror is slightly behind? [08:49] lordievader: it is latest 5th August http://cdimage.ubuntu.com/kubuntu/releases/14.04.3/release/ [08:50] Hmm, since there were no respins that should be the released image. [08:55] Riddell: are we throwing kwallet-pam backport at backports ppa? [08:55] going to add the pam automatic magic, after that we probably could do a quick backport [09:00] sitter: I'll package it for wily and then maybe a useful person like sgclark will backport it [09:04] Riddell: needs the pams first though :P [09:04] yep [09:05] * sitter crosses fingers for CI QA to pass [09:05] btw [09:05] since shadeslayer mentioned it [09:05] the binary naming standard apparently is libpam-foo [09:05] not pam-foo [09:05] just a FYI [09:06] and on another note. I am now wondering why we didn't move the pam into kwallet source itself :P [09:06] seems odd to have it in plasma only [09:20] Riddell: I attempted kamoso last night, its in my PPA [09:20] the naming convections are still causing me grief [10:39] mparillo, lordievader: all good on the 14.04.3 announce? [10:39] The 64bit was fine IMO. [10:41] lovely [10:44] Do you know why it needed more than 1g memory? [10:44] Was it the live session in the background eating too much ram? [10:44] that I've no idea alas [10:44] maybe we need to disable something [10:45] Must say I haven't checked if it works when you go straight to installation. [10:50] Riddell: Too late now, but I did test 32 bit live session, full install, and full encrypted install with no obvious breakage. Only the usual that after clicking the restart button at the end of installation I had to force powerdown my VM [10:51] I think I had to do that too. [10:53] mm, most annoying that [10:55] morning sitter. have you seen my mail about symbols files in kubuntu_wily_archive? [10:56] santa_: haven't gotten to it yet, sorry [10:57] k [11:21] what's the name of that audio software that we used for meeting? [11:22] mumble [11:22] thank you [11:24] Riddell: are you preping 5.4 uploads or are you on other stuff? [11:24] sitter: I plan to get on plasma 5.4 shortly [11:24] ping if you get to it before me please [11:25] needs branches sorted out [11:34] sitter: just needs kubutu_stable merged in no? [11:34] no [11:34] unstable -> stable first [11:35] and then the stable -> archive merge [11:36] sitter: before that, could we switch the kci to gcc 5? otherwise this is going to be a mess, I'm afraid... [11:36] santa_: isn't it? [11:36] gcc5 still stuck in proposed? [11:37] hmm, I cecked the last kconfig build yesterday and is using gcc 4 [11:37] that would at least explain the symbol divergence [11:37] which means I broke stuff xD [11:37] sitter: ok shall I merge those now? [11:37] I suppose that's the mail about? [11:37] Riddell: go ahead [11:37] Riddell: just make sure... these are two merge runs [11:38] https://launchpad.net/ubuntu/+source/gcc-5 [11:38] ↑ yep, still in proposed [11:38] sitter: do I need to turn off kci? [11:38] blergh [11:38] Riddell: disabled it is already [11:39] sitter: yeah, my mail is about that, I was guessing that you needed to dist-upgrade the chroot used to build the packages in the kci [11:39] santa_: this makes the situation somewhat unfortunate. depending on proposed means all users would need to enable proposed as well [11:40] we can figure it out without depending on proposed [11:41] * sitter hits nexts in ubiquity and reads mail [11:43] sitter: this is not in the mail: I can do the following: keep sending patches for symbols files like I have been doing (these symbols files will be compatible with gcc 4 AND gcc 5 .i.e. we don't depend on proposed), once the kci is switched on with gcc 5 there shoudln't be any problem, but if there is, I will be glad to help [11:44] Riddell, hope you can install most of kde again. how's the update going? [11:44] does it make sense to you? [11:44] santa_: KCI takes offense with MISSING but passing symbols [11:45] sitter: "MISSING but passing" ~ "optional symbols gone" ? [11:45] yes [11:45] oh, damn [11:46] there are only three options I can think of 1. we disable symbol tracking for now (which could be simply ignoring MISSING symbols in passing builds) meaning we won't track ABI until gcc5 lands 2. we make KCI use proposed (which from an integration POV is the best option) but that needs users to enable proposed AND since we use wily for plasma 5.4 testing now that can impact testing results there 3. we pull up a second CI chain that ignores symbols [11:46] and delivers for plasma testing (likely requires some engineering effort first) [11:47] I think I would vote for 1 [11:47] yeah, it's probably the least annoying of the options [11:48] I will be very glad to help with this option, also note that I have some partial work for kde apps / gcc 5 [11:49] yeah, I essentialy reverted part of that :P [11:49] * sitter was under the impression that gcc had landed already for some reason [11:51] sitter: another issue: think about this post-"gcc 5 landed in wily" situation: we get a new symbol in gcc 5, it's noise/optional and won't show up in gcc 4, however it's added as a non-optional symbol by the kci [11:52] sitter: I'll move kgamma to kgamma5 in debian git [11:52] santa_: do we still need to support gcc4 though? [11:52] sitter: ... and if it's marked as optional confuses the kci -> how do we deal with backports? [11:53] oh, KCI only tracks symbols on latest_series [11:53] I suggested the backport scripts should do the same [11:53] ok [11:53] there's not much value derived from it given the effort involved to make the symbol tables work for backport versions [11:54] so, no need to support gcc 4 in any futher symbols patching? [11:55] * so, no need to support gcc 4 in any futher symbols patching targeted to kubuntu_wily_archive? [11:57] *nod* [11:58] http://anonscm.debian.org/cgit/pkg-kde/ci-tooling.git/commit/?id=86e9ba69eb46fd57f00510adf8a05cab93689f26 [11:59] Riddell: I still don't get why you can't use an epoch [11:59] sitter: on kgamma? [11:59] sitter: it's an upstream issue, upstream versions have no epoch [12:00] ah [12:00] I see [12:01] personally I don't see this as an upstream issue TBH [12:01] for a lib it would be an upstream issue. but random tarball versions mean nothing *shrug* [12:12] sitter: hmm, sorry about the brain fart, but now that I think about it: we need to support gcc 4 if we don't want to depend on proposed [12:14] ah yeah, otherwise pkg-kde explodes xD [12:14] clivejo: could you update your purpose package too? http://download.kde.org/unstable/purpose/ then I'll get those into the ubuntu archive [12:14] santa_: I can actually bypass that as well [12:15] ahoneybun: there's no frameworks port of kget so there's no need to package that manually, it's just stuff with frameworks ports that need updates https://community.kde.org/Applications/15.04_Release_Notes [12:16] sitter: bypass what exactly? [12:16] santa_: simply drop the symbols files altogether [12:16] if there are no symbols files the build cannot fail on them [12:16] which is in fact what we do for vivid CI anyway [12:17] http://anonscm.debian.org/cgit/pkg-kde/ci-tooling.git/commit/?id=ad287d3e20d62c6a52e373b3b6f702015cc0e19b [12:17] Riddell: are you about these evening [12:17] clivejo: probably not [12:19] sitter: while I'm not very familiar with the kci stuff, I think I get the idea [12:21] Riddell, sitter: so now that the symbols handling is sorted out, what's the plan about the new upcoming versions? [12:22] (of frameworks, applications, plasma) [12:22] should I finish my 15.04.3/kubuntu_wily_archive apps patches for gcc 5? [12:24] no clue what Riddell's plan there was. I understand KF5 was partially uploaded to proposed though [12:24] Riddell: did you run the merging yet? === rdieter_work is now known as rdieter [12:30] Riddell: what version is akonadi,IRC channel says "Stable: 1.13, master is KF5", download KDE.org says "15.07.90" and the archive has 1.13.0-2ubuntu4 !? [12:31] also is kamoso version correct? [12:31] 3.0.0+rc1? [12:32] LP kept rejecting it on me [12:41] Howdy folks [12:42] sitter: not yet merged no [12:44] clivejo: akonadi is 15.07.90 http://download.kde.org/unstable/applications/15.07.90/src/ [12:45] clivejo: kamoso should be 3.0.0~rc1, else 3.0.0 will be smaller than current [12:56] * Riddell merges plasma [13:01] Riddell: please leave me and clivejo some list of packages that are ported to kf5 [13:06] Riddell: baloo needs stable branch removed [13:06] and kfilemetadata [13:07] ahoneybun: https://community.kde.org/Applications/15.04_Release_Notes [13:07] ahoneybun: https://community.kde.org/Applications/15.08_Release_Notes [13:07] which list is it? [13:07] all tagged [new] [13:07] yes, what sitter said [13:07] also see kubuntu-devel mail from like 1 month ago or so pertaining to apps packaging [13:07] there is a shortlist of what needs doing to port to kf5 [13:08] sitter: that mail made very little sense [13:08] entirely possible :P [13:08] so everything with [new] needs packaging? [13:08] I tend to work in spheres puny humans have problems comprehending :P [13:08] ahoneybun: except for dragon [13:09] ahoneybun: in general a good rule of thumb is to check if the repo has a kubuntu_unstable branch === ahoneybun changed the topic of #kubuntu-devel to: Ninjas! https://community.kde.org/Applications/15.08_Release_Notes | https://trello.com/kubuntu | http://qa.kubuntu.co.uk/ | Plasma Mobile images: http://kubuntu.plasma-mobile.org/ | congratulations to sgclark on Akademy Award [13:09] if not then it needs porting, if it has one then it likely doesn't as that means it is in CI [13:10] sitter: ark: http://anonscm.debian.org/cgit/pkg-kde/applications/ark.git/ [13:10] ? [13:11] ahoneybun: what's your question? [13:11] does that need packaging> [13:11] I see no kubuntu_unstable [13:11] yes, it needs porting [13:11] sitter: those kubuntu_stable branches seem to be already gone [13:11] Riddell: my clone just disagreed [13:12] ahoneybun: yes, it has no kubuntu_unstable because it is new, so it needs porting from scratch [13:12] so you'd start with kubuntu_wily_archive [13:12] branch it into kubuntu_unstable and then start porting away [13:12] how do I do that? [13:12] sitter: tell clone sitter to get a grip https://paste.kde.org/pear8vydf [13:12] commands [13:12] I could tell you how I do it usually but I fear that might confuse you :/ [13:13] git co kubuntu_wily_archive [13:13] git co -b kubuntu_unstable [13:13] then clone upstream repo [13:13] then ln -s ark/debian into the upstream repo [13:13] then dpkg-buildpackage -us -uc -jauto -b until green :P [13:13] also I read CMakeLists.txt to get the build dependencies [13:13] ahoneybun: really, Riddell might be more help with this [13:14] ln -s? [13:14] sitter: I'll package frameworks first because plasma presumably wants the new baloo [13:14] ahoneybun: symbolic link [13:14] ahoneybun: it's essentially cheating my way to a source package that is no source package [13:14] as I said, more confusing than helpful [13:14] perhaps [13:16] Riddell: and baloo? [13:16] ah [13:16] Riddell: in plasma [13:16] sitter: is now part of frameworks [13:16] not frameworks [13:17] sitter: ? [13:17] nevermind, I'll do it myself [13:18] the merger tool actually has a beauty flaw [13:18] it'd create stable branches in repos we don't use anymore [13:19] * sitter scratches head [13:19] Riddell: kdelibs5-dev is old right? [13:20] ahoneybun: yep, remove that if it's for a frameworks port [13:20] that's kdelibs4 despite the number in it [13:20] I'm working on ark [13:20] in the ec2 still [13:23] ahoneybun: :) [13:24] I''m guessinig your in there too? [13:24] not currently [13:25] oh ok [13:25] thought you were watching me lol [13:25] I'm not, but you never know when I am! [13:26] true.... [13:26] lol [13:27] is this really needed libkonq5-dev ? [13:27] Konqueror libraries [13:29] ahoneybun: that's kdelibs4 stuff too [13:29] thought so [13:29] probably needed for some preview in the old version but drop it for the port [13:29] drop it [13:30] ? [13:30] yep [13:30] k [13:32] yay patchs [13:32] *patches [13:43] Riddell: have you pushed the merge yet? [13:44] ScottK: I am in VA next week Wed-Sun if you are around. [13:45] Interesting. Quite possibly. [13:45] Need to survive this week/weekend before I have mental bandwidth to think about it though. [13:45] We are renting a car, so getting to you won't be an issue [13:45] no worries [13:50] sitter: yes [13:50] sitter: I'm now packaging frameworks [13:54] mh [13:54] Riddell: can you paste me your merge command [13:54] there is something very fishy going on [13:55] sitter: um git checkout kubuntu_stable; git merge kubuntu_unstable; git checkout kubuntu_wily_archive; git merge kubuntu_stable [13:56] Oo [13:56] Riddell: repo-merge? [14:01] sitter: what's the difference? [14:02] repo-merge is easier [14:02] it's also workign on clean clones [14:02] but if we consider tools pointless I can also just stop writing them [14:02] please don't O.o [14:34] hmm, lots of missing https://launchpadlibrarian.net/213854859/buildlog_ubuntu-wily-amd64.attica-kf5_5.13.0-0ubuntu1~ubuntu15.10~ppa1_BUILDING.txt.gz [14:39] santa_: know anything about this failure? https://launchpadlibrarian.net/213854859/buildlog_ubuntu-wily-amd64.attica-kf5_5.13.0-0ubuntu1~ubuntu15.10~ppa1_BUILDING.txt.gz [14:40] Riddell: baloo merge broken [14:40] sitter: kubuntu-ci is silent on the subject, what's up? [14:40] Riddell: yeah, I forget to include the patch in the patchset for 5.12/gcc 5, see kubuntu-devel [14:40] doesn't know who broke it [14:41] Riddell: http://gpul.grupos.udc.es/kubuntu_patches/frameworks-5.12/attica-kf5/0001-Update-symbols.patch [14:41] this should do part of the job [14:42] sitter: merge pushed [14:46] santa_: applied thanks :) [14:47] doko: thank you for the openbabel update, I have just found out that libkface (from kde apps) is still ftbfs'ing this time because of opencv (which will need a transition in debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=791226) [14:47] Debian bug 791226 in src:opencv "opencv: library transition is needed when GCC 5 is the default" [Important,Open] [14:49] part of the build log: https://paste.kde.org/pmpewa1p3 [15:20] Riddell: for kdesu would be nice to either merge from kubuntu_unstable or cherry-pick my patch to make the debian/rules working fine on any distro [15:21] Riddell: I mean this commit http://git.debian.org/?p=pkg-kde/frameworks/kdesu.git;a=commitdiff;h=bd63db8 [15:21] I have checked kubuntu_wily_archive and still doesn't have the patch [15:22] Will kdesu replace kdesudo? [15:27] santa_, Riddell: surely that kdesu commit is merged in wily_archive? [15:27] oh wait, we are uploading 5.12 [15:27] santa_: probably can just wait for 5.13 [15:27] seeing as we are one month behind by the time 5.12 is in 5.13 will be out :P [15:30] 5.13 is building now https://launchpad.net/~kubuntu-ppa/+archive/ubuntu/staging-frameworks [15:31] Riddell: you merged frameworks, right? [15:32] hi. is anyone working on getting the kubuntu packages in wily updated for the gcc5 transition? [15:32] santa_: cherry-picked thanks [15:32] sitter: hmm it should have happened in the staging script let me check [15:32] if you had to cherry pick it wasn't [15:32] dobey: yes we are, slowed down by lots of stuff also being ported to frameworks [15:32] that commit is like 3 weeks ago [15:33] sitter: fooey :( [15:33] s/ago/old [15:33] Riddell: don't forget to resume CI before you leave [15:33] * sitter heads out [15:33] gotcha [15:33] Riddell: ah ok. [15:33] dobey: what's the issue? [15:34] Riddell: well i'm just seeing that the majority of remaining failures are kde things, some of which just need simple no-change rebuilds. i don't have upload permissions, so i can't fix any myself directly, so i'm just poking to see if i can get someone to fix them [15:35] I'm currently doing frameworks and expect to do plasma and applications after [15:35] the packages that have libs though, need lib renames for the changed abi from gcc5 [15:35] dobey: got an example to see if it's in that lot of not? [15:36] Riddell: well, the "step" package just needs a simple no-change rebuild [15:37] "cantor" also seems to just need a no-change rebuild [15:41] dobey: aye they're all in applications, I'll get to them toot sweet next week [15:48] Riddell: plasma 5? [15:48] 5,4 [15:49] BluesKaj: is next on my list to package [15:49] good to hear Riddell :-) === Riddell changed the topic of #kubuntu-devel to: Ninjas! https://community.kde.org/Applications/15.08_Release_Notes | https://trello.com/kubuntu | http://qa.kubuntu.co.uk/ | Plasma Mobile images: http://kubuntu.plasma-mobile.org/ | congratulations to sgclark on Akademy Award | http://qa.kubuntu.co.uk/ppa-status/frameworks/build_status_5.13.0_wily.html [16:03] add http://qa.kubuntu.co.uk/ppa-status/frameworks/build_status_5.13.0_wily.html kf5 5.13 [16:05] Riddell: ready for testing yet? [16:06] clivejo: frameworks? goodness no lots to build still [16:06] * clivejo shakes head [16:10] Riddell: is the name I used for Kamoso in my PPA ok? 3.0.0+rc1-1ubuntu1 ? [16:10] clivejo: should be 3.0.0~rc1-0ubuntu1 [16:11] ~ means less so the final 3.0.0 will be a larger number, and -0 because it's not in debian yet [16:18] ok so purpose has jumped from 0.1 to 1.0 ? [16:27] Riddell: I have detected a general problem in frameworks 5.13, e-c-m build depend was not bumped to 5.13 [16:28] Riddell: if you don't have a quick way to fix it, I have an script to fix this quickly for all frameworks packages [16:29] Riddell: If you have few minutes would you help me with these Lintan messaqes https://paste.kde.org/p8sb8k8vt [16:29] mm yes it's missing from dev-package-name-lists/frameworks-wily, I'll just add it in thanks [16:30] clivejo: you shouldn't need to build-dep on qt5-default so just remove that [16:30] clivejo: libkf5purpose5 probably needs multi-arch: same [16:31] clivejo: and symbols files need updated which is faffy and is described at http://pkg-kde.alioth.debian.org/symbolfiles.html "pkgkde-symbolshelper batchpatch -v 1.8 buildlog" probably easiest [16:35] oh good lord [16:45] wont build at all now - dpkg-source: error: aborting due to unexpected upstream changes, see /tmp/purpose_1.0~rc1-0ubuntu1~ubuntu15.10~ppa2.diff.WC8miU [16:49] gives up [16:53] clivejo: look in that file and see what it's moaning about [16:54] maybe you downloaded a log file into the source and it wants it removed [16:56] Riddell: hmm, so are you going to push to git anything to bump to e-c-m to 5.13? [16:57] s/to e-c-m/e-c-m/ [16:59] pushing... [17:01] santa_: pushed [17:05] Riddell: thanks, re-scheduling build for my ppa simulation... === Riddell changed the topic of #kubuntu-devel to: Ninjas! https://community.kde.org/Applications/15.08_Release_Notes | https://trello.com/kubuntu | http://qa.kubuntu.co.uk/ | Plasma Mobile images: http://kubuntu.plasma-mobile.org/ | congratulations to sgclark on Akademy Award | http://qa.kubuntu.co.uk/ppa-status/frameworks/build_status_5.13.0_wily.html | http://qa.kubuntu.co.uk/ppa-status/plasma/build_status_5.3.95_wily.html [17:09] plasma up http://qa.kubuntu.co.uk/ppa-status/plasma/build_status_5.3.95_wily.html [17:34] Riddell: may I send you my w-i-p set of patches for apps before it's too late? it doesn't cover the full set of apps ftbfs'es with gcc 5 but would be a nice thing to have in kubuntu_wily_archive before we start with apps 15.08 [17:51] santa_: Perhaps you could take a look at this one: [17:51] qt-gstreamer is on the list of packages with symbols changes for g++5, and is hit by the qt4+boost issue. package has non-trivial reverse-dependencies (both qt4 and qt5 binaries are seeded). any kubuntuers able to take a look at this? Riddell, ScottK? [17:51] fwiw if I disable the qt4 build it still ftbfs by failing to find /usr/lib/x86_64-linux-gnu/gstreamer-1.0/include/gst/gstconfig.h, so there's some failure to properly pkgconfig here as well [17:52] Or anyone else? [17:57] ScottK: what's the problem exactly? qt4 is ftbfsing in ubuntu because of gstreamer? [17:58] if so I might have an idea about the problem [17:58] santa_: If you can work on it, have a chat with slangasek for details. [17:58] All I know is what I pasted. [18:10] ScottK: ack [18:10] Thanks. === rdieter is now known as rdieter_work [21:04] anyone about to help me with symbols file? [21:05] Im trying to update libkf5purpose library from 1.0beta to 1.0rc1 [21:05] lintan is complaining about the symbols file [21:07] I have what I believe is the diff file - https://paste.kde.org/px3t5ktw9 [21:07] but cant figure out how to actually apply it [21:10] yofel Riddell anyone? [21:11] first, see http://pkg-kde.alioth.debian.org/symbolfiles.html [21:12] my connection is bad so I'll have to explain that later [21:14] but the diff is weird, the symbols aren't that different.. [21:17] Ive rm *.symbols :/ [21:17] bad idea [21:17] we need those files to make sure that the version doesn't stay the same if a symbol gets removed [21:18] so you need to be able to see what gets removed [21:18] cant even build it [21:18] well, it'll probably fail on missing symbols, right [21:18] gonna have to start again, this is a proper mess [21:19] oh its completed [21:19] in that case, we have a problem, but I can talk more about that when I'm home (~30min) [21:19] * yofel hits is connection [21:20] https://paste.kde.org/pyu0zedj5 [21:20] should I start from scatch [21:41] this makes NO sense! [21:52] watch some netflix or some silly youtube video [21:53] LOL ahoneybun dont get me started on netflix [21:53] there is a movie called "Rubber" [21:54] I dont live in the correct country! [21:54] oh [21:54] right [21:54] well the W's are about symbols [21:54] what does lesspipe tell you? [21:55] there are symbols there, but they must be from the beta build [21:55] and have changed now in the rc1 buid [21:55] but I cant figure out how to update them [21:55] small name changes maybe [21:55] oh [21:55] not in debian/rules? [21:56] or something [21:56] jonathan pointed me to http://pkg-kde.alioth.debian.org/symbolfiles.html [21:57] but dpkg-buildpackage -j4 | tee buildlog fails with dpkg-source: error: aborting due to unexpected upstream changes, see /tmp/purpose_1.0~rc1-0ubuntu1~ubuntu15.10~ppa1.diff.yXAmw_ [21:58] I don't even know dpkg-buildpackage yet so [21:58] I just use debuild [21:59] its complaining about the file buildlog not being in the original source [21:59] but its a new file! [21:59] I usually just chill till someone gets here [21:59] oh that gave me an idea [22:00] what if I put ../buildlog [22:02] ok that worked [22:03] yay [22:03] step one complete [22:04] *beep* *beep* of a *beep*'ing *beep* [22:05] I hate versions!! [22:05] pkgkde-symbolshelper: error: input symbol file template version (5.9.0+git20150516.0223) is higher than the specified one (1.0) [22:06] how did it get to 5.9.0?!? [22:19] so awesome to see you two helping one another out [22:20] clivejo: are you a Kubuntu Member? [22:20] nope [22:20] please apply! [22:20] !membership [22:20] Ubuntu Membership means recognition of a significant and sustained contribution to Ubuntu and the Ubuntu community. For more info see https://wiki.ubuntu.com/Membership/NewMember [22:20] not sure I want to [22:20] you qualify so Just Do It [22:21] can you tell me why?] [22:21] pm is ok [22:21] if you prefer [22:21] recent events [22:22] that I understand, and it's been very upsetting for many of us [22:23] however IMO we are the captain of our own ship, if we want to be [22:24] IMO ubuntu will always be steered by MS/Canonical [22:25] I moved from Ubuntu to Kubuntu because of Unity and MIR, plus the sending of search info to Amazon [22:26] Riddell, not sure about santa's last question. opencv is already transitioned, and it can't be in unstable because of missing transitions in the b-d's. not sure what to do about it [22:26] anyway, afk again [22:27] JR asked questions a lot of us want to know, and look at the way he was treated [22:27] so Im not sure I want to be a member of that "community" [22:31] plus when I was trying to help beta testing in Ubuntu and asked questions I felt like something unpleasure found on ones shoe! [22:31] unpleasant [22:32] sorry, I might have missed something [22:32] my computer ran out of battery without warning me [22:32] very rude of it [22:32] yes, we'll always be steered by Canonical, that is a basic fact of life [22:33] clivejo: very sorry to hear that you were treated badly while beta-testing [22:33] here? [22:33] no, here have been great! [22:33] or in #ubuntu+1 [22:33]