[02:44] <ahoneybun> valorie: my bad I fell asleep
[02:45] <valorie> np
[02:45] <valorie> can you check and publish?
[02:45] <ahoneybun> why are we linking to 14.04?
[02:46] <valorie> ?
[02:46] <valorie> on the download page?
[02:46] <valorie> because it's LTS
[02:46] <valorie> for those who need the old plasma
[02:47] <ahoneybun> no the post you drafted
[02:47] <ahoneybun> it says 14.04.1 but it was linked to 16.04.1
[02:47] <valorie> typo I guess
[02:48] <valorie> I copied an old post and updated it
[02:48] <valorie> that's why a review is always good!
[02:48] <ahoneybun> want to link it to the text or just make it a link?
[02:48] <valorie> the sentence should be a link
[02:48] <valorie> same with the announce email
[02:49] <valorie> dunno who to make wordpress do that
[02:49] <ahoneybun> I can do it, also updated the alt download page from 16.04 to 16.04.1 
[02:49] <ahoneybun> and 14.04 to 14.04.4
[02:49] <valorie> super
[02:50] <valorie> thank you
[02:50] <ahoneybun> np
[02:51] <ahoneybun> let me make one change to the download page and I'll get out and let you check
[02:53] <ahoneybun> valorie: aright I'm out
[02:54] <ahoneybun> well logged out, still here if things need to be fixed
[02:55] <valorie> ahoneybun: I don't see it
[02:55] <valorie> did you publish?
 it's a draft still
[02:56] <ahoneybun> if that is how you meant it to look
[02:56] <valorie> it's out; let's publish
[02:56] <ahoneybun> alright
[02:56] <ahoneybun> added the release notes of .1 on the getkubuntu page as well
[02:57] <valorie> I pushed the publish button
[02:57] <valorie> thanks ahoneybun
[02:57] <ahoneybun> cool np :)
[02:58] <valorie> uh
[02:58] <valorie> why is 15.10 there?
[02:58] <valorie> that isn't supported anymore, is it?
[02:58] <valorie> !releases
[02:59] <ahoneybun> yea it lost it this month
[02:59] <ahoneybun> I can remove it
[02:59] <valorie> yes please
[02:59] <ahoneybun> let's see if ovidiuflorin gets mad lol
[03:00] <valorie> I think it actually officially loses support tomorrow, but whatever
[03:00] <valorie> since it was released on the 22nd
[03:01] <ahoneybun> done
[03:01] <valorie> \o/
[03:02] <ahoneybun> at least we're ahead there then
[05:14] <tsimonq2> clivejo, acheronuk: you see my upload?
 /me is mad
 about?
 :-P
 You asked me to get mad,  now I'm mad.
 😜
[05:42] <ahoneybun> XD
[05:43] <ahoneybun> I did not break anything so
[05:44] <acheronuk> tsimonq2: yes, see the comments after 13:48 https://irclogs.ubuntu.com/2016/07/21/%23kubuntu-devel.html
[05:45] <tsimonq2> oh okay
[05:47] <acheronuk> tsimonq2: the original versioning on that package is confusing
[05:47] <tsimonq2> acheronuk: well it wouldn't let me rebuild with ubuntu1
[05:47] <tsimonq2> wait a minute
[05:48] <tsimonq2> acheronuk: has it already been handled?
[05:48] <tsimonq2> if not, I'll just replace the debian revision with 3build1
[05:48] <acheronuk> should be something like 1.8.18+git20160320-3d8622c-3build1
[05:48] <tsimonq2> yeah
[05:49] <tsimonq2> acheronuk: so my question was, has it already been handled or can I do that again?
[05:49] <acheronuk> just checking the ppas...
[05:50] <acheronuk> nope. nothing there I can see
[05:50] <tsimonq2> alright
[05:50] <tsimonq2> acheronuk: do you have access to upload my fix?
[05:51] <acheronuk> as you have a -4 in your ppa, it might reject you uploading -3build1 to ppa
[05:52] <tsimonq2> deleted the PPA
[05:52] <tsimonq2> it's a throwaway PPA
[05:52] <acheronuk> I can copy to the kubuntu ppas anything that is fixed, yes
[05:53] <tsimonq2> alright :)
[05:53] <tsimonq2> acheronuk: why is the package being rebuilt?
[05:53] <acheronuk> it may have worked by deleting the package and waiting the 20-30 mins for launchpad to delete the sources from disk
[05:53] <tsimonq2> (for the changelog entry)
[05:54] <acheronuk> but a new ppa also works
[05:55] <acheronuk> the package needs rebuilding as the one in the archive was built against old dependency versions
[05:55] <acheronuk> Qt 5.5 etc
[05:56] <acheronuk> and the newer versions in the staging-plasma ppa cause the package to be removed or become uninstallable as a result
[05:57] <tsimonq2> acheronuk: https://launchpad.net/~tsimonq2/+archive/ubuntu/testing-1
[05:57] <tsimonq2> acheronuk: just uploaded
[05:57] <acheronuk> so it needs a no change rebuild against those newer packages to work with thsoe
[05:57] <tsimonq2> yeah
[05:58] <tsimonq2> acheronuk: https://launchpad.net/~tsimonq2/+archive/ubuntu/testing-1/+packages
[05:58] <tsimonq2> :)
[06:00] <acheronuk> :D
[06:03] <acheronuk> that can get copied across making sure that the option "Rebuild the copied sources" is selected, which would then rebuild again in our ppa against the versions there
[06:08] <acheronuk> as per yofel's comment @21:19 UTC, and backport to xenial would have to be versioned differently. i.e  3build1~ubuntu16.04~ppa1
[06:14] <acheronuk> tsimonq2: https://launchpad.net/~kubuntu-ppa/+archive/ubuntu/staging-plasma/+packages?field.name_filter=qtcurve&field.status_filter=published&field.series_filter=
[06:30] <tsimonq2> yeah acheronuk 
[06:31] <tsimonq2> acheronuk: so I need to upload the Xenial fix?
[06:31] <acheronuk> yes
[06:32] <tsimonq2> alright
[06:33] <tsimonq2> thanks acheronuk for uploading that then :D
[06:33] <tsimonq2> s/then//
[06:33] <acheronuk> no probs :)
[06:34] <tsimonq2> acheronuk: version in Xenial is 1.8.18+git20160112-0cd6aae-1 , so I have to make it 1.8.18+git20160112-0cd6aae-1build1
[06:35] <acheronuk> tsimonq2: no, you can backport the yakkety one you have done
[06:36] <tsimonq2> oh alright
[06:37] <acheronuk> as something like 1.8.18+git20160320-3d8622c-3build1~ubuntu16.04~ppa1
[06:38] <tsimonq2> acheronuk: I have a version in mind
[06:40] <acheronuk> kubuntu keeps to a versioning scheme for ppas and backports, so it's clear they are a backport, a ppa version, and upgrade ok if someone upgrades to the next ubuntu version
[06:41] <tsimonq2> alright so I have to change it from what I uploaded? https://launchpad.net/~tsimonq2/+archive/ubuntu/testing-1/+packages
[06:41] <tsimonq2> acheronuk: or is it fine as-is?
[06:41] <acheronuk> it needs to have the ~ after the version you did for yakkety
[06:43] <acheronuk> that makes apt/dpkg see it as an earlier version than the YY one you did, so if someone then upgrades to YY the XX one gets replaced
[06:43] <acheronuk> as said, yesterday yofel suggested 1.8.18+git20160320-3d8622c-3build1~ubuntu16.04~ppa1
[07:10] <tsimonq2> alright acheronuk 
[07:10] <tsimonq2> acheronuk: I'll do that
[07:13] <tsimonq2> acheronuk: argh... dpkg-source: error: Version number suggests Ubuntu changes, but Maintainer: does not have Ubuntu address
[07:13] <acheronuk> hmmm.... not sure
 Why would someone rm -rf /var/lib/apt/lists/* after installing some packages in a Docker image?
 I've checked /var/lib/apt/lists after installing somehting and it's empty
 I don't get it
[07:25] <acheronuk> tsimonq2: ummm..... I get that as just a warning, but not an error http://paste.ubuntu.com/20422182/
[07:29] <acheronuk> grrr. or even if I could follow my own suggestion properly, then http://paste.ubuntu.com/20422518/
[07:35] <tsimonq2> acheronuk: what OS are you running? what command did you run?
[07:37] <acheronuk> I am running Xenial, and I ran 'debuild -S -sa' 
[07:37] <tsimonq2> I'm running Yakkety
[07:37] <tsimonq2> *gets Xenial schroot*
[07:38] <acheronuk> tsimonq2: should make no difference as far as I know
[07:39] <acheronuk> clivej does everything while running yakkety
[07:40] <tsimonq2> weird
[07:41] <acheronuk> I've only been doing this a few months, so others may see something obvious I can't right this second
[07:50] <yofel> ovidiuflorin: that directory contains the apt package list cache (i.e. the files that apt update downloads). You could argue that's data you don't need in a docker image
 yeah... that's what the doker folks told me
 I hoped for a more detailed explanation
[07:53] <tsimonq2> yofel: would you happen to know why I can't build this?
[07:55] <yofel> ovidiuflorin: well, that folder is 510M on my system, and those are files that you can always download again if you need to install something, so it's really not something you want inside a docker *image*, only in a running container if you need them
[07:55] <yofel> as you generally want to keep the image size as small as possible
[07:56] <yofel> and if you keep updating the images, those files would also bloat the diff between versions
 I get how for docker that would be a bad thing, but what's in there more precicely?
[07:58] <yofel> the package lists, which are the files that tell apt what packages it can download from which repositories. e.g. /var/lib/apt/lists/de.archive.ubuntu.com_ubuntu_dists_trusty_main_binary-amd64_Packages
[08:00] <yofel> plus the package description translations, DEP-11 metadata for icons and components, etc.
[08:03] <tsimonq2> acheronuk: would it be okay if I named it 1.8.18+git20160320-3d8622c-3build1~16.04~ppa1 ?
[08:03] <yofel> yeah, that'll be fine
[08:04] <acheronuk> tsimonq2: does that work for you then?
[08:04] <tsimonq2> yup
[08:04] <tsimonq2> perfect
[08:05] <acheronuk> yofel tsimonq2: maybe the yakkety version of devscripts etc has stricter checks now then?
[08:05] <tsimonq2> maybe
[08:05] <yofel> hm, that's dpkg, not devscripts
[08:05] <yofel> but yeah, probably
[08:06] <tsimonq2> yofel, acheronuk: uploaded, building now: https://launchpad.net/~tsimonq2/+archive/ubuntu/testing-1/+packages
[08:07]  * acheronuk goes to look at dpkg changelog
[08:13] <tsimonq2> acheronuk: done building, do you wait until it's published to copy or can you do it now?
[08:14] <yofel>                if (length $ENV{DEBEMAIL} and $ENV{DEBEMAIL} =~ /\@ubuntu\.com/) {
[08:14] <yofel>                    error(g_('Version number suggests Ubuntu changes, but Maintainer: does not have Ubuntu address'));
[08:14] <yofel>                } else {
[08:14] <yofel>                    warning(g_('Version number suggests Ubuntu changes, but Maintainer: does not have Ubuntu address'));
[08:14] <yofel>  interesting....
[08:14] <tsimonq2> weird
[08:14] <acheronuk> tsimonq2: copied https://launchpad.net/~kubuntu-ppa/+archive/ubuntu/staging-plasma/+packages?field.name_filter=qtcurve&field.status_filter=published&field.series_filter=
[08:15] <tsimonq2> \o/
[08:16] <tsimonq2> acheronuk: so what happens after that PPA?
[08:16] <tsimonq2> acheronuk: and is there anything else packaging-related I can do?
[08:18] <acheronuk> tsimonq2: will end up going into Xenial backports ppa in the end hopefully, and the YY packages into YY if someone with main archive permissions deems them ok
[08:18] <tsimonq2> alright :)
[08:18] <tsimonq2> acheronuk: I see a bunch of `Newer version available` warnings, is that expected?
[08:19] <tsimonq2> for example: qtconnectivity-opensource-src - 5.6.1-2~yakkety+build1 (Newer version available)
[08:20] <acheronuk> tsimonq2: normally you'd worry on that, but with those packages it's ok
[08:20] <yofel> it's because 5.6.1 of that package is in the archive already
[08:20] <yofel> with a higher version than in the PPA
[08:20] <acheronuk> reason being that ubuntu Qt maintainers uploaded their versions, but the builds failed. but launchpad still sees the newer sources are there
[08:22] <acheronuk> when building in the ppa LP takes the ppa version, as the archive version has no actual built .debs
[08:26] <acheronuk> tsimonq2: clivejo probably has a better handle on what is currently needed re packaging tasks
[08:32] <tsimonq2> alright
[08:32] <tsimonq2> clivejo: could I get something else to do? :)
[08:34] <acheronuk> yofel: so if I had an ubuntu.com email address like simon, it would give me an error?
[08:34] <yofel> probably. I use my kubuntu.org one, so that explains why I never get that
[08:36] <acheronuk> I can see the logic. sorta. ubuntu uploader and 'ubuntu' in version, but not ubuntu maintainer = wtf (error)
[08:41] <yofel> yeah, we just hit a corner case where that's nonsense
[08:57] <acheronuk> tsimonq2: I can now use that ppa without it removing my qtcurve themes for kde :)
[08:57] <acheronuk> which makes me happy, as I'm not keen on breeze or the qt5 oxgen :D
 Has log in time slowed down again in 5.7.2?
[09:49] <soee> i have this feeling 
[09:55] <tsimonq2> acheronuk: yay! :D
[09:56] <tsimonq2> acheronuk, yofel: maybe it would be worth it to file a bug
[09:57] <yofel> tsimonq2: what was the context again?
[09:57] <clivejo> soee: feeling it has slowed down?
[09:57] <mamarley> clivejo: It seems about the same for me, unless the missing-folderview-desktop bug is triggered.
[09:58] <tsimonq2> yofel: can't have Ubuntu revisions because it
[09:58] <mamarley> That bug is sort of similar to what we were seeing early with 5.6.x when the folderview on the desktop would disappear and it would take a very long time on the splash screen.
[09:58] <clivejo> I feel like its delayed by about 15seconds compared to previous versions of plasma
[09:58] <tsimonq2> *the maintainer doesn't have an Ubuntu address
[09:58] <tsimonq2> clivejo: ^
[09:58] <tsimonq2> wait didn't mean to ping you but hello :)
[09:58]  * clivejo waves
[09:58] <soee> clivejo: yes
[09:59] <clivejo> sorry, just logged on, trying to catch up!
[09:59] <clivejo> so many different threads of conversation
[09:59] <yofel> tsimonq2: feel free to, IMO that's not worth an error, even if the original intentions were good
[09:59] <tsimonq2> yofel: where did you find the code for that?
[10:00] <yofel> scripts/Dpkg/Vendor/Ubuntu.pm
[10:00] <tsimonq2> clivejo: I'm looking for something else to do now :)
[10:00] <tsimonq2> yofel: in what package?
[10:00] <yofel> dpkg
[10:00] <tsimonq2> alright thanks
[10:00] <mamarley> clivejo: In my case, the problem was that the ~/.config/plasma-org.kde.plasma.desktop-appletsrc had lastScreen=-1 for the folderviews.  Obviously, you can't have negative monitors, so once I replaced those values with 0 and 1, it worked fine.
[10:02] <yofel> oh, the trello integration for my nick is fixed. yay
[10:02] <tsimonq2> clivejo: got anything? :)
[10:02] <jimarvan> hey clive
[10:06] <soee> mamarley: i had one lastSeenScreen=-1 in that file
[10:06] <soee> changing it doesn't speed up loading
[10:06] <soee> hmm but i still have it set to -1
[10:07] <mamarley> soee: You may have to shut down Plasma before changing it, or you may not be suffering from the same problem as me.
[10:07] <clivejo> tsimonq2: well Im working on testing Plasma 5.7.2 on YY
[10:07] <clivejo> trying to resolve the installation issues with it
[10:08] <clivejo> there is some issue with plasma-dsicover I havent managed to figure out yet
[10:08] <clivejo> discover
[10:09] <clivejo> anyone else see this on YY?
[10:11] <tsimonq2> clivejo: that same PPA?
[10:11] <clivejo> staging-plasma
[10:12] <clivejo> you could also look for packaging issues you can fix on KCI
[10:12] <clivejo> send us a merge request
[10:13] <tsimonq2> alright
[10:13] <tsimonq2> what's KCI?
[10:13] <clivejo> Kubuntu Continious Intregration
[10:13] <clivejo> http://kci.pangea.pub
[10:13] <tsimonq2> alright
[10:14] <clivejo> it grabs the latest source code from KDE and combines it with our packaging ( https://code.launchpad.net/~kubuntu-packagers/+git )
[10:14] <tsimonq2> aww why does it have to remove LXQt?
[10:15] <tsimonq2> now I have to use it in a VM
[10:15] <tsimonq2> :P
[10:15] <tsimonq2> clivejo: I would highly suggest removing any conflicts with LXQt
[10:15] <clivejo> those messages from kubuntu-ci are being generated by KCI
[10:16] <clivejo> tsimonq2: I dont know enough about LXQt to comment on that
[10:16] <tsimonq2> alright
[10:17] <acheronuk> LXQt are going to have to cope with the Qt 5.6 transtion in YY eventually, if that is the cause
[10:17] <BluesKaj> Hiyas all
[10:18] <acheronuk> clivejo: I can maybe have a look at that discover conflict later if no-one else does
[10:19] <tsimonq2> acheronuk: yeah LXQt uses Qt 5.5.1
[10:19] <acheronuk> clivejo: just now I'm about to go for a pub-lunch, so will be some time
[10:20] <acheronuk> tsimonq2: Well Qt 5.6 will go in the main archive for YY, so they'll have to cope with it as we are doing
[10:20] <clivejo> tsimonq2: do you know any of the LXQt people?
[10:21] <tsimonq2> clivejo: great friends with them :)
[10:21] <tsimonq2> well not really
[10:21] <tsimonq2> but I know them
[10:22] <tsimonq2> clivejo: I'll do some test builds locally
[10:22] <clivejo> maybe you could get in touch and see if they need help transitioning to Qt 5.6.1
[10:23] <tsimonq2> alright, but like I said, maybe it already works
[10:23] <clivejo> I dont personally use it so dont see the conflicts
[10:23] <tsimonq2> *shrug*
[10:23] <BluesKaj> sddm doesn't accept jpegs for background on the login page 
[10:24] <BluesKaj> on Yakkety
[10:24] <acheronuk> maxyz has done a build of  lxqt-qtplugin - 0.10.0-3build1~2 in his ppa today
[10:24] <acheronuk> https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-024/+packages
[10:25] <acheronuk> so he at least is looking at it
[10:25] <acheronuk> ok. bbl
[10:25] <tsimonq2> ooh let's see
[10:28] <tsimonq2> clivejo: let's say foo depends on bar. bar 0.2 is in the PPA but bar 0.1 is in Ubuntu. I upload foo 0.1-1. Does foo use bar 0.1 or 0.2 when building?
[10:28] <tsimonq2> (this is in a PPA)
[10:29] <clivejo> packagekit : Depends: libpackagekit-glib2-16 (= 0.8.17-4ubuntu6~gcc5.4ubuntu2) but 0.9.5-0ubuntu1 is to be installed
[10:30] <clivejo> 0.1-1 is debian version
[10:31] <tsimonq2> clivejo: but just for example
[10:31] <clivejo> but 0.2 is higher so if its in the same PPA, it will build using that
[10:31] <tsimonq2> alright
[10:31] <tsimonq2> great
[10:31] <clivejo> do you know about epochs?
[10:32] <tsimonq2> in what context?
[10:32] <clivejo> packages
[10:32] <tsimonq2> sort of
[10:33] <clivejo> !info ark
[10:33] <clivejo> 4:15.12.3-0ubuntu1 The 4: is an epoch
[10:33] <tsimonq2> oh then I don't know
[10:34] <clivejo> the -0 is the debian version
[10:35] <clivejo> and ubuntu1 is our archive version
[10:35] <clivejo> with the 15.12.3 being the upstream KDE version of the package
[10:36] <tsimonq2> oh okay
[10:36] <clivejo> git pull
[10:37] <clivejo> oupps
[10:37] <tsimonq2> I knew what the rest standed for, I just don't know what the 4: means
[10:37] <clivejo> usually to fix a boo boo someone makes with the version
[10:38] <clivejo> ie if they made a typo and released 51.12.3
[10:39] <clivejo> that version will not be upgradeable again until upstream get to a version higher than it
[10:40] <clivejo> so the epoch overrides it and allows us to fix the versioning so it is upgradable again
[10:40] <tsimonq2> oh okay
[10:40] <clivejo> can be confusing
[10:41] <clivejo> but essential to understanding you need the epoch for build deps as well
[10:45] <tsimonq2> so wait, the 4 means that 51.12.3 can't be upgraded to 51.12.4 and over?
[10:45] <tsimonq2> or am I not understanding this correctly?
[10:45] <clivejo> 51 is just an example
[10:46] <clivejo> a typo where someone might have put 51 instead of 15
[10:46] <tsimonq2> ohhhh
[10:46] <tsimonq2> so I understand the purpose now
[10:46] <clivejo> but the next natural version from KDE is 16.04
[10:46] <tsimonq2> but why 4?
[10:46] <clivejo> but because 51 is greater, it wouldnt allow the upgrade
[10:47] <tsimonq2> why not 15 then?
[10:48] <clivejo> once its gone to the archive and install on many systems we cant just change it back
[10:49] <clivejo> its rare, but in Kubuntu we have a few :/
[10:49] <clivejo> I think an automation script may have messed up in the past, but I dont know the reason
[10:49] <tsimonq2> so give me an example of a correct epoch then
[10:51] <clivejo> well ark is an example
[10:51] <clivejo> it has an epoch of 4:
[10:52] <tsimonq2> oh
[10:52] <clivejo> http://anonscm.debian.org/cgit/pkg-kde/applications/ark.git/tree/debian/changelog
[10:52] <tsimonq2> I guess what is the barrier with 4?
[10:52] <tsimonq2> why does it have to be 4?
[10:53] <tsimonq2> I'm not understanding that
[10:53] <clivejo> well in this case I cant answer that!
[10:54] <clivejo> Initial packaging on line 635 of changelog seems to indicate it started off life with an epoch
[10:54] <tsimonq2> does it have to universally be 4 and if not, why?
[10:54] <clivejo> I think, someone decided to use 4
[10:54] <clivejo> maybe KDE4 at the time
[10:55] <tsimonq2> sorry for not understanding this, but what about in a different package?
[10:55] <clivejo> and because we use automation it might been easier to just give all the applications suite a 4: epoch
[10:56] <clivejo> most of KDE Applications have an epoch of 4:
[10:56] <tsimonq2> I would like to understand what it's preventing. Is it if the version is over 4?
[10:56] <tsimonq2> If so, then that isn't right
[10:56] <clivejo> http://qa.kubuntu.co.uk/ppa-status/applications/build_status_16.04.3_yakkety.html
[10:56] <tsimonq2> I mean, what does it prevent?
[10:57] <clivejo> it allows the package to be upgradeable again after a mistake in the versioning
[10:58] <clivejo> say for example I release 16.07 of my latest app
[10:59] <clivejo> but I made a type and instead released version 61.07
[10:59] <clivejo> I then release 17.01 of the app in January
[10:59] <clivejo> but the archive has version 61.07 which is higher
[11:00] <clivejo> my new app will never be upgradeable until the version is greater than 61.07
[11:00] <clivejo> so to override that my new version would need an epoch
[11:01] <clivejo> ie 1:17.01
[11:02] <clivejo> this now means my new version will be installed, upgrading version 61.07, the freak package of doom
[11:02] <tsimonq2> oh okay
[11:02] <tsimonq2> clivejo: then for the next release do you remove the epoch?
[11:03] <clivejo> no
[11:03] <clivejo> it cant be removed
[11:03] <tsimonq2> so then what happens if you do it again?
[11:03] <clivejo> if I did another mistake, ie 1:71.05
[11:03] <clivejo> then I have to bump the epoch again
[11:03] <clivejo> to 2:17.06
[11:04] <clivejo> and so forth
[11:04] <tsimonq2> oh okay
[11:04] <tsimonq2> that makes sense
[11:04] <tsimonq2> I get it now :)
[11:04] <tsimonq2> clivejo: so why do I need to know this for rebuilds?
[11:04] <clivejo> LOL you dont
[11:04] <clivejo> you asked about versions
[11:05] <clivejo> and epochs are very important
[11:05] <clivejo> but also confusing!
[11:07] <clivejo> LOL
[11:07] <clivejo> git fetch santa
[11:08] <tsimonq2> 05:40:51 AM < clivejo> can be confusing
[11:08] <tsimonq2> 05:41:20 AM < clivejo> but essential to understanding you need the epoch for build deps as well
[11:08] <tsimonq2> I took that as I needed it for rebuilds XD
[11:08] <tsimonq2> but hey, nice to know :)
[11:08] <clivejo> no, just packaging in general
[11:09] <clivejo> its an area that took me a while to get my head around
[11:09] <clivejo> Im very bad with numbers
[11:09] <clivejo> Im Dyslexic
[11:13] <tsimonq2> clivejo: I think this is failing due to the lack of memory... http://kci.pangea.pub/job/yakkety_unstable_kdepim-addons/
[11:14] <clivejo> yeah, KCI has "issues"
[11:14] <clivejo> but PIM is a beast, noone likes tackling it!
[11:29] <clivejo> santa_: was there an issue with kde4libs?
[11:33] <maxyz> acheronuk: Mmh, no, that was not me
[11:47] <tsimonq2> clivejo: what Qt, non-KDE packages are in the staging-plasma PPA?
[11:47] <tsimonq2> clivejo: just all the qt* packages?
[11:48] <santa_> clivejo: it was ftbfsing from git/kubuntu_yakkety_archive because of symbols, build logs:
[11:49] <santa_> https://launchpadlibrarian.net/271959760/buildlog_ubuntu-yakkety-amd64.kde4libs_4:4.14.22-0ubuntu1~ubuntu16.10~ppa1_BUILDING.txt.gz
[11:50] <santa_> http://gpul.grupos.udc.es/logs/kde4libs_4.14.22-0ubuntu1+santa30_amd64.build
[11:51] <santa_> clivejo: ffmpeg thimbs was failing too bacause of a less trivial issue, I have a merge request fixing that one
[11:51] <santa_> * ffmpegthumbs
[11:52] <santa_> tsimonq2: what was your doubt about versioning, you don't understand the "4:" prefix of some packages?
[11:53] <tsimonq2> santa_: he cleared things up for me
[11:53] <santa_> k
[11:55] <santa_> [13:07] <clivejo> git fetch santa
[11:55] <santa_> lol
[11:58] <santa_> ah I see you already merged my stuff, thanks!
[11:59] <yofel> don't we have a bug for the ffmpegthumbs issue?
[12:02] <santa_> if we have it I don't know
[12:02] <yofel> bug 1574037 - anyone fancy doing an SRU for that?
[12:02] <santa_> ah, that's other issue
[12:02] <yofel> santa_: that was fixed in the diff you proposed to merge though
[12:03] <santa_> yes, because it uses the new pkg-kde-tools stuff
[12:03] <santa_> making the path right
[12:03] <yofel> exactly
[12:04] <santa_> I was planning to prepare a couple of merge requests for things in xenial
[12:04] <santa_> (targeted to updates)
[12:05] <yofel> santa_: everyone of that would need an SRU bug associated with it
[12:06] <yofel> but it would be great to have a list of stuff that we should be fixing
[12:08]  * yofel wonders what happened to apps 16.10
[12:09] <santa_> 16.10?
[12:09] <yofel> er, 16.08
[12:10] <santa_> ah
[12:11] <santa_> yofel: any document about how the ubuntesque "bureaucracy" works for sru's?
[12:11] <yofel> !sru
[12:11] <yofel> see #Procedure
[12:17] <yofel> clivejo: FYI: I released ffmpegthumbs to yakkety so ^ bug is fixed
[12:19] <jimarvan> hmm
[12:19] <jimarvan> I should download yakkety to virtualbox and start testing
[12:19] <jimarvan> for things you need confirmation
[12:33] <acheronuk> maxyz: I meant Mirv, sorry!
[12:38] <acheronuk> clivejo: I'm not dyslexic, & did my degree/PhD in physics/maths, and debian versioning still confuses me at times!
[12:38] <Mirv> tsimonq2: acheronuk: clivejo: yeah it looks like all LXQt bits compile just fine at least, testing welcome from silo 24
[12:39] <tsimonq2> Mirv: ooh! are you working with that now?
[12:39] <Mirv> also KDE bits should be ready, testing welcome too although I'll test myself probably on Monday :)
[12:40] <Mirv> tsimonq2: well for the Qt 5.6 upgrade I need to rebuild everything using Qt private headers so yes I'm rebuilding all the packages. now finally it starts to seem pretty good, with s390x/powerpc issues solved during my leave and other fixes I've been doing this week.
[12:40] <Mirv> AFAIK https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-024 is ready for Unity 8, Plasma 5 and LxQt, but it's all very fresh and not much tested at all yet
[12:42] <acheronuk> Mirv: we've been test compiling with our own backported Qt5.6.1 builds. Once you think yours are done then we should sync up so that we are both using whatever candidate builds that will go into Yakkety 
[12:42] <tsimonq2> Mirv: I'll use that PPA and try to rebuild some LXQt packages
[12:42] <tsimonq2> Mirv: I'm running LXQt right now so I'll test :)
[12:43] <Mirv> acheronuk: sans testing, some missing -gles Qt twin packages, a Qt Creator 4 transition (which I plan to do first), the PPA should be complete for sanity testing now. I will probably next week switch the "Approved" switch in that silo, not to land to archives yet but to get the autopkgtests results which might reveal lots of fixes needed elsewhere.
[12:44] <Mirv> so yes it should be near final now, even though it might be 1-2 weeks from actual landing, depending on how many surprises are found
[12:44] <Mirv> Qt always manages to surprise :)
[12:44] <acheronuk> indeed it does!
[12:47] <acheronuk> Mirv: thanks for that info :)
[12:53] <tsimonq2> Mirv: I'll be test rebuilding and uploading to https://launchpad.net/~tsimonq2/+archive/ubuntu/lxqt-qt-5.6.1 , then if it builds correctly, I'm installing it on my system
[12:56] <Mirv> ok, thanks acheronuk and tsimonq2
[13:04] <acheronuk> tsimonq2: that would be good. I've played a bit with that when razor-qt was a thing, but not much on lxqt recently
[13:05] <tsimonq2> acheronuk: well I'm running it right now
[13:05] <tsimonq2> acheronuk: and I want to enable the Kubuntu Staging PPA without things breaking, because I have 2 desktops on this install, KDE Plasma and LXQt
[13:07] <acheronuk> tsimonq2: currently I have xubuntu/xfce4 as a fallback DE on most machines. switching that to lxqt might be nice
[13:08] <tsimonq2> acheronuk: Lubuntu (team I'm a part of) switches to LXQt within a year or two
[13:08] <tsimonq2> acheronuk: I can get you instructions for that, depending on your release and distro :)
[13:09] <acheronuk> yeah, that was the 'gap' I fell down. razor-qt going nowhere, and lxqt not seeming ready. or at least it appeared so, even if that was not the case
[13:50] <clivejo> anyone testing apps 16.04.3 on YY?
[13:51] <ahoneybun> how close are we
[13:51] <ahoneybun> for XX
[13:51] <ahoneybun> well you are
[13:51] <clivejo> well looks like ffmpegthumbs are fixed
[13:52] <clivejo> I was going to do a backport if got the all clear?
[13:52] <ahoneybun> oh only on YY atm?
[13:53] <clivejo> yes, YY is dev and we do that first
[13:53] <ahoneybun> alright
[13:53] <ahoneybun> I only have XX on all machines
[13:53] <ahoneybun> plus don't have my laptop power cable
[13:55] <clivejo> wow Im just on fire these days
[13:55] <clivejo> I, Liliane Donated ( 2,000,000 USD )Two million dollars to you
[13:56] <clivejo> luck that, Ive almost spend the last money
[14:03] <clivejo> yofel: you uploaded ffmpegthumbs to the archive?
[14:03] <yofel> yes
[14:03] <clivejo> the fresh one built today with santa's patch?
[14:03] <yofel> yes
[14:03] <clivejo> oh cool
[14:04] <clivejo> I preparing to backport 16.04.3 to XX, that ok?
[14:04] <yofel> yeah, please do. Then we can use yakkety for 16.08 once the tars are up
[14:05] <clivejo> just doing a git pull 
[14:05] <clivejo> I should have all the tarballs locally, so shouldnt take long
[14:07] <tsimonq2> Mirv: builds fine, updating now
[14:14] <jimarvan> see ya later peeps
[14:15] <clivejo> jimarvan: you coming to party?
[14:15] <acheronuk> did someone sort something for qtwebengine for apps 16.08?
[14:20] <jimarvan> clive
[14:20] <jimarvan> i cannot :(
[14:20] <jimarvan> 22:30 I will be back home. I have kickboxing now every Monday and Friday 20:30-22:00
[14:22] <jimarvan> see ya later on
[14:37] <tsimonq2> this is weird
[14:37] <tsimonq2> clivejo: so I have LXQt mostly rebuilt for Qt 5.6.1
[14:38] <tsimonq2> and so I added the Kubuntu Staging Plasma PPA back
[14:38] <tsimonq2> like I originally wanted it
[14:38] <tsimonq2> it removes lxqt-config because apparently lxqt-config depends on libkf5screen6
[14:39] <tsimonq2> it's not a direct dependency, and I don't know what still might be
[14:40] <yofel> it should be a direct dependency
[14:41] <yofel> $ apt-cache depends lxqt-config
[14:41] <yofel>   Depends: libkf5screen6
[14:41] <yofel> Needs to be rebuilt against libkf5screen7
[14:42] <tsimonq2> yofel: so do I need to enable the Kubuntu Staging PPA when I rebuild then?
[14:42] <yofel> yes
[14:42] <tsimonq2> alright
[15:02] <tsimonq2> yofel: yay! it works! thanks a lot! :)
[15:05] <soee> \o/
[15:11] <tsimonq2> so hello from LXQt with Qt 5.6.1!
[15:11] <soee> is this some king to spaceship ? :D
[15:11] <soee> *kind
[15:11] <soee> *of
[15:12] <tsimonq2> huh? :D
[15:12] <soee> LXQt
[15:12] <clivejo> any major changes?
[15:12] <tsimonq2> nope
[15:12] <tsimonq2> it's pretty much the same
[15:12] <tsimonq2> went into my Plasma session, laggy
[15:13] <tsimonq2> it had a bit of slowness to it
[15:13] <tsimonq2> and I have 16 GB of RAM and a 6 core processor
[15:14] <tsimonq2> clivejo: is that to be expected?
[15:14] <clivejo> what version of plasma?
[15:22] <tsimonq2> clivejo: 5.7.2
[15:23] <clivejo> wonder were that is coming from
[15:23] <tsimonq2> Kinfocenter
[15:24] <tsimonq2> :P
[15:24] <clivejo> I meant the lag :P
[15:25] <tsimonq2> oh lol
[15:26] <clivejo> so many emails!
[15:31] <clivejo> ok, I have a few lastScreen=-1
[15:31] <clivejo> and replaced with 0
[15:35] <clivejo> wish this upload would hurry up so I can reboot
[16:04] <clivejo> oh sugar lumps
[16:05] <clivejo> need FW5.21 or better for Apps on Xenial
[16:08] <acheronuk> clivejo: one prob is plasma-discover 5.7.2 depends packagekit >= 1.0
[16:09] <acheronuk> and some obsolete plasma-discover 5.6.5 packages maybe
[16:11] <acheronuk> http://paste.ubuntu.com/20467363/
[16:12] <acheronuk> and http://paste.ubuntu.com/20468770/
[16:17] <tsimonq2> clivejo: I know you said that I could fix build errors, but is there anything *specific* you would like me to look at?
[16:21] <acheronuk> tsimonq2: http://kci.pangea.pub/ xenial or yakkety fix tabs?
[16:23] <acheronuk> I've been gradually trying to fix things to make plasma desktop etc build on there, but any failure is not good
[16:24] <tsimonq2> acheronuk: we have a common error
[16:24] <tsimonq2> acheronuk: usr/share/appdata/org.kde.ark.PACKAGE.xml is missing
[16:25] <acheronuk> christ! "Build Queue (327)" zzzzz
[16:26] <acheronuk> tsimonq2: yes, missing appstream data a common one
[16:26] <tsimonq2> acheronuk: ooh, how do I fix that? :D
[16:28] <acheronuk> tsimonq2: if you look at the buildlog in the install section, you can see where it's been moved to
[16:28] <tsimonq2> alright
[16:28] <acheronuk> in this case it's now /usr/share/metainfo/org.kde.ark.appdata.xml
[16:28] <tsimonq2> oh then that's easy
[16:28]  * tsimonq2 fxes
[16:28] <tsimonq2> *fixes
[16:29] <acheronuk> yes, the .install file would need updating
[16:29] <tsimonq2> acheronuk: do I take the package from the CI PPA?
[16:31] <acheronuk> kubuntu packaging is here: https://code.launchpad.net/~kubuntu-packagers/+git
[16:31] <tsimonq2> ok
[16:32] <tsimonq2> acheronuk: how do I submit patches then?
[16:32] <tsimonq2> acheronuk: and what branch goes into CI?
[16:33] <acheronuk> the workflow yofel had me doing until I had commit access was:
[16:33] <acheronuk> * clone the package git repo
[16:34] <acheronuk> * checkout the branch (i.e. kubuntu_unstable for CI)
[16:34] <acheronuk> * make the fix
[16:34] <acheronuk> * do a commit
[16:35] <acheronuk> * push that branch to your own personal git repo on launchpad
[16:36] <acheronuk> * then use launchpad web interface to propose a merge with the kubuntu packaging branck
[16:36] <acheronuk> instructions here for setting up git/ssh for kununtu https://notes.kde.org/p/kubuntu-packaging
[16:38] <tsimonq2> acheronuk: I can't access that page
[16:38] <tsimonq2> it requires a login
[16:39] <acheronuk> tsimonq2: you need an account from: https://identity.kde.org/
[16:44] <tsimonq2> acheronuk: where on that page?
[16:45] <acheronuk> Register - top right
[16:45] <tsimonq2> acheronuk: no I'm already there
[16:46] <tsimonq2> acheronuk: where on the pad are the instructions?
[16:46] <acheronuk> https://notes.kde.org/p/kubuntu-packaging
[16:46] <acheronuk> sorry, you didn't mean that!
[16:46] <tsimonq2> correct
[16:47] <acheronuk> "For easy cloning of LP git repositories, put this in your ~/.gitconfig (where USER is your launchpad username):"
[16:47] <acheronuk> ^^^ that section
[16:48] <tsimonq2> oh okay
[16:48] <acheronuk> that way to clone a packages repo, you just do 'git clone kubuntu:packagename'
[16:49] <acheronuk> so simple as 'git clone kubuntu:ark'
[16:50] <tsimonq2> oh that's convenient
[16:50] <acheronuk> yep, that's the point :)
[16:51] <tsimonq2> acheronuk: do I have to make a debian/changelog entry as well or do you guys do that?
[16:51] <acheronuk> yes, you would
[16:52] <acheronuk> 'dch' will append an entry
[16:52] <tsimonq2> alright
[16:53] <acheronuk> don't need a whole new entry, as this is UNRELEASED
[16:53] <tsimonq2> alright
[16:55] <acheronuk> eventually you git diff would look something like this which I did for plasma last night https://git.launchpad.net/~kubuntu-packagers/kubuntu-packaging/+git/plasma-desktop/commit/?id=67acd6880767fe7bdc3f1e1164c7d7646b52883a
[16:57] <acheronuk> for no trivial changes you should/could test the building of the package with pbuilder, but that is a slight faff to set up
[16:57] <acheronuk> *non trivial
[16:58] <tsimonq2> so wait would I just replace the path for that file or copy the whole usr/share/metainfo dir like you did?
[16:58] <tsimonq2> s/copy/add an entry for/
[17:00] <acheronuk> just the directory should work, as it catches anything in there
[17:01] <acheronuk> it will only be appstream data in there, so you'd want it whatever the name is
[17:01] <tsimonq2> alright
[17:02] <acheronuk> git diff | pastbininit will give you a pastebin link for your changes before you do anything else with them
[17:02] <tsimonq2> acheronuk: so committed and pushed, what now?
[17:03] <tsimonq2> oh no lol
[17:03]  * tsimonq2 iks fast
[17:03] <tsimonq2> *is
[17:03] <acheronuk> no prob, you are ahead of me :)
[17:03] <tsimonq2> so what now?
[17:03] <acheronuk> have you a link to the repo you pushed to?
[17:04] <tsimonq2> https://git.launchpad.net/~tsimonq2/+git/kubuntu-ark?h=kubuntu_unstable
[17:06] <tsimonq2> acheronuk: so are you going to grab my commit and push it to the ark repo?
[17:06] <tsimonq2> acheronuk: or do you have comments?
[17:06] <acheronuk> really you should keep the .install file entries sorted alphabetically, but should not matter here
[17:07] <tsimonq2> acheronuk: so should I move it?
[17:07] <acheronuk> ok. yes, you may as well
[17:08] <tsimonq2> hm?
[17:09] <tsimonq2> acheronuk: done
[17:09] <acheronuk> http://manpages.ubuntu.com/manpages/xenial/man1/wrap-and-sort.1.html
[17:09] <tsimonq2> take a look again?
[17:09] <acheronuk> see above ^^ wrap and sort tool is handy :)
[17:10] <acheronuk> but it may change other files if they also are a bit unsorted
[17:10] <tsimonq2> did nothing
[17:11] <tsimonq2> acheronuk: but I pushed the change
[17:11] <acheronuk> if everything is right, it won't
[17:11] <tsimonq2> acheronuk: and everything is right
[17:12] <tsimonq2> acheronuk: so https://git.launchpad.net/~tsimonq2/+git/kubuntu-ark/commit/?h=kubuntu_unstable&id=59cbe839a6355536309a0beb10315835052eccca
[17:12] <acheronuk> yep
[17:12] <tsimonq2> what now?
[17:12] <acheronuk> 2 secs - next bit needs to be done from LP web interface
[17:12] <tsimonq2> k
[17:13] <acheronuk> ok here: https://code.launchpad.net/~tsimonq2/+git/kubuntu-ark
[17:13] <acheronuk> you click through to the branch
[17:14] <acheronuk> so to https://code.launchpad.net/~tsimonq2/+git/kubuntu-ark/+ref/kubuntu_unstable
[17:14]  * tsimonq2 nods
[17:14] <tsimonq2> now?
[17:15] <acheronuk> you should see some links on that page to propose a merge?
[17:15] <acheronuk> I can't, as it's not MY repo
[17:16] <tsimonq2> uhh no
[17:16] <tsimonq2> acheronuk: do you have access to the Kubuntu Ark Git repo?
[17:17] <acheronuk> yes
[17:18] <tsimonq2> acheronuk: do the merge locally then push
[17:18] <acheronuk> no
[17:18] <tsimonq2> well I can't submit a merge proposal...
[17:18] <acheronuk> there should be a link: Propose for merging
[17:19] <tsimonq2> well there isn't one
[17:20] <acheronuk> no? http://i.imgur.com/5URPGBw.png
[17:21] <tsimonq2> ohh I know what the problem is
[17:21] <yofel> ~tsimonq2/+git/kubuntu-ark is missing the project. It has to be ~tsimonq2/kubuntu-packaging/+git/kubuntu-ark
[17:21] <tsimonq2> I pushed to junk
[17:21] <tsimonq2> yeah yofel got it
[17:22] <acheronuk> ah. oops. missed that
[17:23] <yofel> hm, discover needing packagkit is a prolem :S
[17:24] <yofel> oh
[17:24] <yofel>  packagekit | 1.1.1-1ubuntu1                  | yakkety-proposed | source, amd64, arm64, armhf, i386, powerpc, ppc64el, s390x
[17:24] <tsimonq2> acheronuk: Target reference path? huh?
[17:24] <yofel> so I guess we're getting another attempt at that
[17:24] <ahoneybun> ximion: found a laptop with Tanglu 3 on it lol
[17:24] <acheronuk> tsimonq2: http://i.imgur.com/z71Prlo.png
[17:25] <ximion> ahoneybun: \o/
[17:25] <tsimonq2> ok okay
[17:25] <tsimonq2> ahoneybun: hello :)
[17:25] <ximion> not too surprising, our userbase isn't small
[17:25] <ahoneybun> getting Ubuntu back for someone
[17:25] <ximion> it's only small in comparison with Debian, Fedora, Ubuntu, ...
[17:25] <acheronuk> tartget ref path is tha branch you want to merge with
[17:25] <ahoneybun> hey tsimonq2
[17:26] <tsimonq2> acheronuk: https://code.launchpad.net/~tsimonq2/kubuntu-packaging/+git/kubuntu-ark/+merge/300929
[17:26] <tsimonq2> \o/
[17:27] <acheronuk> the people on the kubuntu packagers team list should now get an email asking them to review your merge to approve it
[17:28] <ahoneybun> cool
[17:28] <tsimonq2> acheronuk: aren't you on that team? :)
[17:28] <acheronuk> it's a bit of a faff at 1st, but it's the best option LP has with it's git repos at the moment
[17:29] <tsimonq2> alright
[17:29] <yofel> only direct team members get a mail - which he isn't. He could do the merge though
[17:29] <acheronuk> tsimonq2: I am since a couple of weeks ago
[17:30] <acheronuk> yofel: I got an email
[17:30] <tsimonq2> alright
[17:30] <yofel> oh, interesting
[17:30]  * yofel wonders why that didn't work for him then..
[17:31] <acheronuk> I can't remember how to do the merge though!
[17:31]  * acheronuk goes to look in irc logs
[17:32] <acheronuk> tsimonq2: that means you can propose as many as you like, and don't have to catch us in here or email us for each one
[17:33] <tsimonq2> alright :)
[17:34] <acheronuk> yofel: I did deliberately subscribe to the LP mailing list for any extra team memberships I got?
[17:35] <yofel> packagers doesn't have a ML though, but it might've been a setting that I missed
[17:40] <tsimonq2> argh these merge proposals just don't look right
[17:41] <tsimonq2> (the second one I'm working on)
[17:41] <tsimonq2> oh I'm dumb... :P
[17:44] <acheronuk> yofel: once approved, would that be 'git clone kubuntu:ark; cd ark; git checkout kubuntu_unstable; git remote add tsimonq2 lp:~tsimonq2/kubuntu-packaging/+git/kubuntu-ark/; git fetch tsimonq2; git merge tsimonq2/kubuntu_unstable; git push'
[17:45] <tsimonq2> it would be the same as doing that I think
[17:45] <tsimonq2> acheronuk: I think you can do it in Launchpad?
[17:45] <tsimonq2> but otherwise that looks correct if my Git skills are good
[17:46] <acheronuk> tsimonq2: nope. we found we couldn't. LP haven't implemented that part yet :(
[17:46] <tsimonq2> oh :(
[17:46] <ahoneybun> tsimonq2: Rick is having packaging classes
[17:47] <ahoneybun> you want to know the packaging "tiers"?
[17:47] <tsimonq2> ahoneybun: so how do you up a tier? what even is that system?
[17:48] <clivejo> I have three merge requests for the same package
[17:48] <tsimonq2> acheronuk: don't merge yet!
[17:48] <tsimonq2> wait
[17:48] <tsimonq2> don't merge artikulate
[17:48] <acheronuk> tsimonq2: https://community.kde.org/Kubuntu/Policies#Kubuntu_Teams_.28.28NEW.29.29
[17:49] <acheronuk> I got fully Ninja'd up a week or 2 ago
[17:49] <acheronuk> but I'm still learning!
[17:50] <acheronuk> tsimonq2: I'm not merging anything until I'm sure I can do it right. Not tried on one of these requests before
[17:51] <tsimonq2> acheronuk: that long thing was correct
[17:51]  * tsimonq2 tries locally to make sure
[17:53] <tsimonq2> yup
[17:53] <tsimonq2> I just left out git push
[17:53] <ahoneybun> tsimonq2: well yellow belts are the first step, then you become a full ninja
[17:53] <ahoneybun> then kubuntu developer
[17:53] <clivejo> hummm what on earth is going on in artikulate
[17:54] <ahoneybun> from that link that acheronuk gave
[17:54] <tsimonq2> clivejo: that's me I thinl :)
[17:54] <tsimonq2> *think
[17:54] <tsimonq2> clivejo: you talking about my couple of MPs I opened and closed? :P
[17:54] <clivejo> oh request has been removed
[17:54] <clivejo> tsimonq2: yes
[17:54] <tsimonq2> clivejo: all good, I was dumb for a minute there :P
[17:55] <acheronuk> tsimonq2: https://git.launchpad.net/~kubuntu-packagers/kubuntu-packaging/+git/ark/commit/?id=59cbe839a6355536309a0beb10315835052eccca
[17:55]  * tsimonq2 gets emails :D
[17:56] <yofel> acheronuk: yeah, that's the correct procedure
[17:56] <acheronuk> yofel: it's what  you said to be back in the irc logs. just had to find it
[17:57] <acheronuk> *to me
[17:57] <acheronuk> tsimonq2: that commit should also trigger a build job in the KCI
[17:57] <tsimonq2> ahoneybun: I have a few uploads in the Ubuntu archive, I know the packaging process well, and I want to start "training". Approve me? :)
[17:57] <tsimonq2> \o/ ahoneybun 
[17:57] <tsimonq2> whoops, \o/ acheronuk 
[17:58] <tsimonq2> ahoneybun: (for yellow belt)
[17:58] <ahoneybun> I believe it would be a council choice
[17:58] <ahoneybun> not mine alone
[17:59] <tsimonq2> ahoneybun: how do I submit an application then?
[17:59] <yofel> yellow belt isn't council matters, as it doesn't actually give you much permissions
[17:59] <yofel> just go and add him
[18:00] <ahoneybun> done
[18:00] <acheronuk> :D
[18:00] <tsimonq2> \o/
[18:01] <ahoneybun> welcome on board tsimonq2
[18:02] <tsimonq2> yay
[18:04] <clivejo> tsimonq2: if you setup a kubuntu git shortname you can clone easier
[18:04]  * tsimonq2 did
[18:04] <clivejo> for example I use git clone kubuntu:ark
[18:04] <clivejo> lots easier :)
[18:05] <clivejo> and also if you can push to your own git minus the kubuntu- that would make my life easier too :)
[18:05] <tsimonq2> yeah
[18:06] <tsimonq2> so what's the process once merged?
[18:06] <tsimonq2> I see #158 on http://kci.pangea.pub/job/xenial_unstable_ark/ is waiting for "Upstream"
[18:07] <tsimonq2> is that just waiting for ark to build in the PPA?
[18:07] <clivejo> it should be queue in KCI
[18:07] <acheronuk> KCI will do a merge job and make a build job for the ppa
[18:08] <acheronuk> KCI has a big job queue at the moment though
[18:08] <tsimonq2> any chance I can see where that queue is? :)
[18:09] <clivejo> all going well, you will see a KCI telling us that ark is FIXED
[18:09] <acheronuk> http://kci.pangea.pub/
[18:09] <tsimonq2> oh
[18:10] <clivejo> #kubuntu-ci is a channel for announcements too
[18:10] <ahoneybun> 244 oh boy
[18:10] <clivejo> can be handy to search there without human chat getting in the way 
[18:11] <yofel> 244 isn't much, the nightly job triggers >400 or so
[18:11] <yofel> although, it's quite a lot for this time of day
[18:11] <acheronuk> it would go down a lot quicker if LP was faster and more reliable
[18:12] <clivejo> yofel: you mind if I clear the queue and let it build the packages they working on?
[18:13] <yofel> not particulary
[18:14] <acheronuk> tsimonq2: welcome to yellow belts by the way :)
[18:15] <tsimonq2> thanks :)
[18:16] <acheronuk> tsimonq2: I have a feeling that very soon you will be showing me how to do stuff. lol
[18:16] <tsimonq2> hahaha
[18:22] <acheronuk> clivejo: reminds me, I was going to do some howto slides for that merge proposal thing
[18:22] <tsimonq2> moar merge proposals! \o/ https://code.launchpad.net/~tsimonq2/kubuntu-packaging/+git/kubuntu-blinken/+merge/300937
[18:24] <clivejo> I didnt get a request for that one
[18:25] <acheronuk> I just did
[18:30] <acheronuk> next dojo is?
[18:31] <acheronuk> Thur 28th?
[18:31] <clivejo> dont think I got an event card for it
[18:32] <tsimonq2> I think you guys get that I'll have another PR :P
[18:33] <acheronuk> tsimonq2: http://kci.pangea.pub/view/yakkety%20FIX/job/yakkety_unstable_ark/60/
[18:33] <acheronuk> PR?
[18:33] <tsimonq2> oh sorry MP
[18:33] <tsimonq2> I'm used to saying PR
[18:33] <yofel> PR is the offical git term
[18:33] <tsimonq2> ^
[18:34] <yofel> LP people are just stuck with MP
[18:34] <tsimonq2> acheronuk: and I know, I'm watching it :P http://kci.pangea.pub/job/xenial_unstable_ark/158/console
[18:34] <acheronuk> tsimonq2: and https://launchpad.net/~kubuntu-ci/+archive/ubuntu/unstable/+packages?field.name_filter=ark&field.status_filter=published&field.series_filter=
[18:35] <tsimonq2> \o/
[18:36] <acheronuk> it's very satisfying making a git change and watching all the gears spin up to build the changes you just made :)
[18:36] <acheronuk> if LP doesn't crap out, that is
[18:37] <tsimonq2> I know :)
[18:40] <tsimonq2> dolphin MP? :)
[18:41] <tsimonq2> thanks
[18:41] <tsimonq2> man this is so awesome watching this all
 /me watches his email get hit up with merges lol
[18:42] <tsimonq2> XD
[18:43] <acheronuk> tsimonq2: you know where debian and Neon keep their git repos for packaging kde?
[18:43] <tsimonq2> where?
[18:43] <acheronuk> http://packaging.neon.kde.org/cgit/
[18:44] <acheronuk> https://anonscm.debian.org/cgit/pkg-kde/
[18:44] <tsimonq2> wxl: hey
[18:44] <wxl> tsimonq2: didn't have to join ;)
[18:44] <tsimonq2> I see :)
[18:44] <acheronuk> tsimonq2: quite often, there will already be git fixes for issues there
[18:44] <tsimonq2> wxl wants to get a yellow belt, right? :D
[18:44] <tsimonq2> yeah acheronuk 
[18:44] <tsimonq2> acheronuk: I checked
[18:45] <wxl> yes please! i need packaging training and would love to help out with kubuntu
[18:45] <tsimonq2> wxl: I'll walk you through what I've been doing for the last few hours :)
[18:45] <wxl> tsimonq2: for now just point me in the right direction. i'll do the application process or whatever later on
[18:46] <wxl> s/\(application\)/\1\/training/
[18:46] <tsimonq2> wxl: look at the process for getting a Yellow belt :)
[18:46] <tsimonq2> Kubuntu Ninjas Yellow Belts is anyone who is training up to become a Kubuntu Ninja
[18:46] <tsimonq2> Get some training in packaging or show you know how to make a package in Ubuntu
[18:46] <tsimonq2> Apply to join the team
[18:46] <tsimonq2> ~kubuntu-council can add you
[18:46] <acheronuk> tsimonq2: ok. just though I would mention is case :)
[18:46] <tsimonq2> (tjhe last 4 lines are bullet points)
[18:46] <tsimonq2> membership lasts for a year
[18:47] <acheronuk> *thought
[18:47] <tsimonq2> acheronuk: yep, thanks :)
[18:47] <wxl> oh ok so i need training first
[18:47] <tsimonq2> yeah
[18:47] <wxl> ok how do i get that? XD
[18:47] <tsimonq2> I/we teach you :)
[18:47] <acheronuk> for starters: http://kubuntu.org/news/kubuntu-dojo-ninja-developer-training/
[18:47] <wxl> oh goodie
[18:47] <acheronuk> and in here :)
[18:48] <wxl> acheronuk: so first, i go back in time? XD
[18:48] <tsimonq2> isn't there another dojo coming up acheronuk ?
[18:48] <acheronuk> I think #3 is next thurs?
[18:48]  * wxl clicks all the links in desperation
[18:49] <tsimonq2> XD
[18:49] <wxl> need an invitation for the G+ stream
[18:49] <tsimonq2> wxl: it's not on G+
[18:49] <wxl> so yeah, not seeing anything
[18:49] <tsimonq2> it's on BigBlueButton
[18:49] <wxl> but i'll be there if i can figure out when it is XD
[18:49] <acheronuk> wxl: not got too far with #1 or #2 to be honest, so you can catch up easily
[18:50] <tsimonq2> wxl: so first, do you know how to download and build a source package?
[18:50] <acheronuk> Rick Timmis was doing slides for the next one the other day, but he seems off IRC today
[18:50] <wxl> tsimonq2: yep
[18:51] <tsimonq2> wxl: you have read the packaging guide? 
[18:51] <wxl> tsimonq2: yep
[18:51] <wxl> and i did the hello package
[18:51] <acheronuk> wxl: well, with some technical hitches on #1, that is about as far as #2 got
[18:51] <tsimonq2> acheronuk: let's just teach him here ;)
[18:52] <tsimonq2> (or get him started)
[18:52] <acheronuk> tsimonq2: that as well, certainly
[18:52] <wxl> my problem is applying what the guide taught me to more complicated situations, i think
[18:52] <tsimonq2> acheronuk: what else does he need to know to be good to go for "Get some training in packaging or show you know how to make a package in Ubuntu" ?
[18:52] <tsimonq2> yeah I see what you mean wxl 
[18:53] <tsimonq2> D:
[18:53] <tsimonq2> :(
[18:53] <wxl> i had an idea of packaging my friend's node-based arduino ide and i just got stymied
[18:53] <tsimonq2> yeah
[18:54] <acheronuk> get set up on launchpad with gpg and ssh keys?
[18:54] <wxl> yep
[18:54] <tsimonq2> acheronuk: can you rebuild xenial_unstable_dolphin ? it's an error unrelated to the package
[18:55] <tsimonq2> wxl: have you read the Debian Policy manual?
[18:55] <wxl> i also have lofty dreams of understanding how to get a package submitted for the very first time to debian and taking it all the way downstream
[18:55] <wxl> no
[18:55] <tsimonq2> oooh it's a good read :)
[18:55] <tsimonq2> https://www.debian.org/doc/debian-policy/
[18:55] <acheronuk> kde identity account?
[18:55] <wxl> ummmmmmm
[18:55] <wxl> acheronuk: is that what i'd use for making bug reports?
[18:56] <tsimonq2> clivejo: can you rebuild xenial_unstable_dolphin ? it's an error unrelated to the package
[18:56] <clivejo> tsimonq2: done
[18:56] <acheronuk> wxl: not quite the same, no.
[18:56] <wxl> acheronuk: link me to account creation page then?
[18:56] <tsimonq2> wxl: you don't have freedom of username on that site :(
[18:57] <wxl> WOOOOOOOOOOOT?
[18:57] <acheronuk> https://identity.kde.org/index.php?r=registration/index
[18:57] <tsimonq2> lol
[18:57] <tsimonq2> wxl: you'll see what I mean
[18:57] <acheronuk> if you have a bugs.kde.org account, you should use the same email you used for that
[18:58] <acheronuk> as I think they can link the 2 up later if required, and that makes it easier
[18:58] <wxl> oh
[18:58] <wxl> actually the one i have for bugs is my work, so nevermind
[18:59] <acheronuk> they can sort it out is not I think
[18:59] <acheronuk> *if not
[18:59]  * tsimonq2 is afk for a few mins
[18:59] <wxl> oh i guess that's not terrible
[19:00] <acheronuk> with the identity account you should be able to read the kubuntu packagers notepad https://notes.kde.org/p/kubuntu-packaging
[19:02] <wxl> aw man
[19:02] <wxl> profile picture can't handle transparency booo
[19:03] <wxl> nice
[19:03] <wxl> i got some reading to do
[19:03] <wxl> once i have my lunch break acheronuk :)
[19:03] <acheronuk> wxl: no probs. I could do with dinner!
[19:04] <sick_rimmit> Hi Folks
[19:04] <wxl> acheronuk: then brexit stage left? sorry, couldn't resist ;)
[19:04] <sick_rimmit> Kubuntu Party is happening
[19:04] <acheronuk> the docs aren't as up to date or complete as they could be
[19:04] <tsimonq2> sick_rimmit: now?
[19:04] <sick_rimmit> Yes
[19:05] <sick_rimmit> http://kubuntu.blindsidenetworks.net/kubuntu/
[19:05] <sick_rimmit> Room 1
[19:05] <tsimonq2> oh!
[19:05] <tsimonq2> okay
[19:05] <wxl> wait
[19:05] <wxl> is this the dojo thingy?
[19:05] <tsimonq2> sick_rimmit: eating some food but I'll be there in a bit
[19:05] <sick_rimmit> Password: welcome
[19:05] <wxl> Congratulations and welcome to the Bike Friday community. It was nice talking with you about your upcoming Bike Friday and thanks for the order.
[19:05] <wxl> I have your completed bike design & invoice information for you in the attachments; please review to be sure all parts, sizing, and accessories are listed as you expect them. Everything looks good on this end. 
[19:05] <wxl> Your bike should ship within a plus or minus five business day window of DATE. Note Ground shipping is usually 5-7 additional business days. You will get a tracking number from us automatically when it's on the way. If we run into a situation where we are unable to make your promise date, we'll contact you. Otherwise, assume your bike order is proceeding like normal.
[19:05] <acheronuk> sick_rimmit: ahhhh... I'll on there shortly. food needed as well.....
[19:05] <wxl> An important consideration about timing:  once your bicycle begins the production process, any changes made closer than 3 weeks from your ship date may not be possible. The things we can change for you we will but it may result in a service charge if it requires someone's time away from other tasks to expedite it through. If you need to make any changes or add anything, please let me know as soon as 
[19:05] <wxl> possible.
[19:05] <wxl> argh
[19:05] <wxl> wrong window
[19:05] <wxl> so sorry :(
[19:05] <tsimonq2> wxl: no this is an informal party but sick_rimmit is the same guy who does the dojo
[19:06] <wxl> oh cool
[19:06] <wxl> sick_rimmit: when's the next dojo?
[19:06] <wxl> (also for the curious, yes, i work for a bicycle manufacturer)
[19:10] <acheronuk> dojo is next Thurs
[19:11] <wxl> acheronuk: same time?
[19:12] <acheronuk> just checking
[19:23] <acheronuk> wxl: we'll get the time to you when have it
 (Sticker, 512x512) https://irc-attachments.kde.org/biMNEftf/file_281.webp
[19:29] <tsimonq2> YAY!
[19:31] <ahoneybun> fixes everywhere
[19:33] <tsimonq2> \o/
[19:33] <acheronuk> :D
[19:39] <tsimonq2> clivejo: the failure on xenial_unstable_gpgmepp is a one time error, rebuild please?
[19:40] <clivejo> done
[19:40] <tsimonq2> thanks clivejo 
[19:44] <tsimonq2> hey clivejo, what PPAs are enabled in building https://launchpad.net/~kubuntu-ci/+archive/ubuntu/unstable ? or are there none?
[19:44] <tsimonq2> (or anyone else who can answer, sorry for pinging clive specifically)
[19:44] <clivejo> should tell you in the console output
[19:45] <tsimonq2> hm okay
[19:45] <clivejo> http://kci.pangea.pub/job/xenial_unstable_gpgmepp/121/console
[19:46] <clivejo> usually just the archive and the unstable PPA
[19:46] <tsimonq2> alright :)
[19:49] <clivejo> acheronuk: mind taking a look at apps 16.04.3 ?
[19:54] <tsimonq2> clivejo: for the fix for gwenview, it wants a package that has 16.04~ , the correct action would be to update that to 16.04.3~ correct?
[19:57] <clivejo> the .3 are bugfix releases
[19:57] <clivejo> so no major changes
[19:57] <clivejo> so mightnt matter that much to be honest
[19:59] <tsimonq2> clivejo: well it's trying to depend on a package with the version: 4:16.04.3+p16.10+git20160722.0723-0
[19:59] <clivejo> yeah thats our KCI versioning
[20:00] <tsimonq2> clivejo: so that needs to be adjusted in the gewnview deps
[20:00] <tsimonq2> *gwenview
[20:03] <acheronuk> Missing build dependencies: libkf5kipi-dev (>= 16.04~) ?
[20:03] <tsimonq2> yes
[20:03] <tsimonq2> but the thing I'm stumped on is it isn't a direct dep
[20:04] <tsimonq2> well I mean it is, but not in the control file
[20:05] <yofel> yes, but we have several dependency layers, so it's just stuck on something intermediate package
[20:05] <acheronuk> the version in XX KCI and the archive is 15.12.2
[20:05] <yofel> and apt is very non-descriptive for dependeny chain issues
[20:05] <acheronuk> because the build of newer ones in kci has been failing for a long time
[20:06] <acheronuk> https://launchpad.net/~kubuntu-ci/+archive/ubuntu/unstable/+packages?field.name_filter=kipi&field.status_filter=published&field.series_filter=
[20:06] <acheronuk> fix libkf5kipi in XX KCI, and you will then get the dep to build gwenview
[20:07] <tsimonq2> acheronuk: oh I'm dumb
[20:07] <tsimonq2> I'm looking at a Xenial log...
[20:07] <tsimonq2> thanks for pointing that out
[20:10] <tsimonq2> acheronuk: how do I fix it? why is it in the CI PPA if it isn't on CI?
[20:11] <tsimonq2> I mean, if it's failing, shouldn't it be on CI?
[20:11] <acheronuk> http://kci.pangea.pub/job/xenial_unstable_libkipi/
[20:11] <tsimonq2> thanks
[20:12] <acheronuk> http://kci.pangea.pub/job/xenial_unstable_libkipi/35/console
[20:12] <acheronuk> "CI::VersionEnforcer::UnauthorizedChangeError"
[20:12] <acheronuk> WTF?
[20:13] <tsimonq2> ikr
[20:13] <acheronuk> That I have not seen before
[20:14] <tsimonq2> weird
[20:15] <tsimonq2> clivejo: rebuild xenial_unstable_marble please?
[20:15] <acheronuk> Has been failing for a long time, hence the last successful build is that old 15.12 version
[20:15] <tsimonq2> I know, but it's failing with the Launchpad error
[20:15] <tsimonq2> well
[20:15] <tsimonq2> nvm
[20:18] <tsimonq2> acheronuk: marbles is also caught up with that error
[20:19] <acheronuk> will have to check with people who know more on CI failures
[20:19] <tsimonq2> uhh qtcurve hasn't been built since July 4
[20:20]  * tsimonq2 builds locally to test
[20:21] <acheronuk> qtcurve only rarely has changes in git
[20:23] <acheronuk> https://quickgit.kde.org/?p=qtcurve.git
[20:23] <tsimonq2> acheronuk: yes but why not build it?
[20:23] <yofel> hm,     
[20:23] <yofel> def validate_epochs(old_epoch, new_epoch)
[20:23] <yofel>       return if old_epoch == new_epoch
[20:24] <yofel> let me clone libkipi
[20:25] <yofel> ok, so something is very wrong in our automation tooling
[20:25] <yofel>  libkf5kipi | 15.12.3-0ubuntu1 | yakkety/universe | source
[20:25] <yofel> libkf5kipi (4:16.04.3-0ubuntu1) UNRELEASED; urgency=medium
[20:26] <acheronuk> tsimonq2: looks a different named package: https://launchpad.net/~kubuntu-ci/+archive/ubuntu/unstable/+packages?field.name_filter=qtcurve&field.status_filter=published&field.series_filter=
[20:26] <acheronuk> one we were doing is just called qtcurve
[20:28] <clivejo> yofel: should I move qtcurve to LP?
[20:33] <acheronuk> one good thing is, getting someone new to look at stuff highlights these things others might have passed over
[20:34] <clivejo> yofel: https://git.launchpad.net/~kubuntu-packagers/kubuntu-packaging/+git/libkipi/tree/debian/changelog?h=kubuntu_unstable
[20:34] <yofel> I'm fixing packaging-exceptions.json
[20:34] <yofel> that's broken
[20:35] <clivejo> https://git.launchpad.net/~kubuntu-packagers/kubuntu-packaging/+git/libkipi/commit/?h=kubuntu_unstable&id=f3ec24d2f22a220b1b827c29b6c29a5af414da79
[20:35] <yofel> I still believe the tooling is what broke it
[20:36] <acheronuk> only Xenial it fails on https://launchpad.net/~kubuntu-ci/+archive/ubuntu/unstable/+packages?field.name_filter=kipi&field.status_filter=published&field.series_filter= 
[20:36] <acheronuk> and has for a long time
[20:37] <clivejo> Ill remove the epoch packages in KCI Unstable
[20:38] <yofel> you will also have to delete them from staging-*
[20:39] <yofel> and I'll send a mail to the ML so that everyone that's using staging knows that they need to force-downgrade a couple packages on their systems
[20:40] <yofel> clivejo: so, what I found broken were: baloo-widgets5 libkf5kface libkf5sane libkgeomap
[20:41] <yofel> at least that's all apps, so our backports aren't broken yet
[20:45] <tsimonq2> new MP! \o/
[20:46] <yofel> hm, why is libkgeomap not in the ppa...
[20:46]  * tsimonq2 shoots a wild https://code.launchpad.net/~tsimonq2/kubuntu-packaging/+git/kubuntu-plasma-sdk/+merge/300950 in clivejo's direction
[20:47] <yofel> o.O
[20:47] <yofel> libkgeomap-16.04.3.tar.xz is a thing, but package-name-list doesn't see it...
[20:48] <yofel> AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAARGH
[20:48] <yofel> why does that stupid thing have yet another hardcoded blacklist in it *****-.-
[20:51] <acheronuk> tsimonq2: It needed to be fix, so good in the long run!
[20:51] <tsimonq2> \o/
[20:54] <acheronuk> I have no Ruby :(
[20:55] <clivejo> who did that?  Line 20:   "libkgeomap": None,
[20:56] <yofel> clivejo: git blame
[20:57] <tsimonq2> can we rebuild xenial_unstable_kcron ?
[20:57] <tsimonq2> Launchpad error
[20:57] <yofel> tsimonq2: done
[20:58] <tsimonq2> ruh roh, the kind of fixes I've been doing need to be reversed here: https://launchpadlibrarian.net/274465810/buildlog_ubuntu-xenial-amd64.kdenlive_4%3A16.04.3+p16.04+git20160722.1124-0_BUILDING.txt.gz
[20:58] <tsimonq2> right?
[20:58] <yofel> ok, libkgeomap in the list now, lets package it for 16.08
[20:59] <yofel> tsimonq2: hm, no, that's another case of appstream -> metainfo rename
[21:00] <tsimonq2> yofel: but then what's wrong?
[21:00] <yofel> dh_install: kdenlive-data missing files: usr/share/appdata
[21:00] <yofel> dh_install: usr/share/metainfo/kdenlive.appdata.xml exists in debian/tmp but is not installed to anywhere
[21:00] <yofel> isn't that the thing you've been fixing?
[21:00] <tsimonq2> marble?
[21:00] <tsimonq2> I don't think so
[21:00] <tsimonq2> *checks again*
[21:00] <yofel> tsimonq2: you linked kdenlive
[21:01] <tsimonq2> oh sorry
[21:01] <tsimonq2> nope
[21:01] <clivejo> yofel: https://git.launchpad.net/~kubuntu-packagers/+git/kubuntu-automation/commit/?id=19d1c0e9fff53985dfdf5d4cbebfd690464b0950
[21:01] <clivejo> Jon killed it
[21:01] <clivejo> but why?
[21:01] <tsimonq2> yofel: I haven't worked on kdenlive (yet)
[21:01] <yofel> clivejo: dunno
[21:02] <yofel> hm, no, my ruby script now fails with other errors. So I at least got the authentication right
[21:02] <yofel> I'll just do this by hand and continue another time
[21:04] <tsimonq2> yofel: re kdenlive, it's failing because of the conversion
[21:04] <tsimonq2> dh_install: kdenlive-data missing files: usr/share/appdata
[21:04] <tsimonq2> dh_install: usr/share/metainfo/kdenlive.appdata.xml exists in debian/tmp but is not installed to anywhere
[21:05] <yofel> yes, so just fix the install file to install metainfo?
[21:05] <clivejo> could you send list of them here please, didnt quite catch it
[21:05] <tsimonq2> oh that's right, geez
[21:06] <tsimonq2> yofel: yakkety_unstable_baloo-widgets is failing because it ran out of memory... :/
[21:06] <yofel> SIGH
[21:07] <yofel> clivejo: baloo-widgets5 libkf5kface libkf5sane libkgeomap libkf5kipi
[21:07] <acheronuk> tsimonq2: do you know pyqt?
[21:07] <yofel> libkgeomap isn't up, so that's good
[21:07] <tsimonq2> acheronuk: no
[21:07] <tsimonq2> what is it?
[21:07] <clivejo> from unstable and staging?
[21:08] <acheronuk> tsimonq2: what the kubuntu installer kde front is done with
[21:08] <acheronuk> tsimonq2: I thought you wouldn't, but asked on the off chance
[21:09] <acheronuk> tsimonq2: it needs porting from pyqt4 to pyqt5
[21:10] <yofel> tsimonq2: would lubuntu be interested in using the Qt frontend eventually?
[21:10] <clivejo> yofel: I uploaded kipi without the epoch to YY and XX staging-apps
[21:10] <yofel> thanks
[21:10] <tsimonq2> yofel: we are switching to LXQt so yes
[21:11] <yofel> ok, something to keep in mind then
[21:11] <tsimonq2> yofel: and I'm really not the one who makes decisions about this, Julien does, gilir@ubuntu.com :)
[21:11] <tsimonq2> he's our development team lead
[21:12] <acheronuk> tsimonq2: at the moment unless ported, we will lose the pretty slideshow you watch while the iso installs
[21:12] <tsimonq2> :(
[21:13] <tsimonq2> acheronuk: dropping Qt or GTK?
[21:14] <acheronuk> pyqt4 has dropped it's QtWebkit support, which the slides need in the QT/kde frontend
[21:15] <acheronuk> tsimonq2: at the moment so the YY installer doesn't crash, we've had to disable the slideshow :(
[21:15] <yofel> ok, kci.yaml updated
[21:15] <acheronuk> tsimonq2: pyqt5 has the support
[21:15] <yofel> now how do I run the update again..
[21:17] <yofel> FYI: I'm running a projects update on jenkins. So it might interrupt something
[21:18] <tsimonq2> acheronuk: so they are dropping GTK?
[21:18] <tsimonq2> acheronuk: or Qt?
[21:18] <tsimonq2> acheronuk: and :(
[21:18] <acheronuk> tsimonq2: GTK is unaffected
[21:19] <acheronuk> tsimonq2: it's the QT4 frontend only with the problem
[21:19] <acheronuk> tsimonq2: so ubuntu/xubuntu etc are fine
[21:20] <tsimonq2> acheronuk: oh that sucks
[21:20] <tsimonq2> acheronuk: what does Lubuntu and Kubuntu use?
[21:20] <tsimonq2> (or does Lubuntu use GTK and Kubuntu uses Qt?)
[21:20] <yofel> what you just said I believe
[21:20] <acheronuk> tsimonq2: kubuntu = QT4/pyqt4
[21:20] <acheronuk> tsimonq2: I have no idea on lubuntu
[21:21] <tsimonq2> acheronuk: so what's the issue then?
[21:21] <acheronuk> it is an eon since I installed that
[21:22] <tsimonq2> yofel: kdenlive incoming
[21:22] <acheronuk> tsimonq2: pyqt4 has dropped the QtWebit support the slides need, so a frontend using that can't have them work
[21:23] <acheronuk> tsimonq2: pyqt5 is staying with support, so we need to port our installer frontend to that
[21:23] <tsimonq2> acheronuk: so now what?
[21:23] <tsimonq2> oh okay
[21:23] <tsimonq2> and you need help? :)
[21:23] <acheronuk> tsimonq2: I don't know pyqt4/5 hardly at all
[21:23] <tsimonq2> acheronuk: I don't know it
[21:23] <tsimonq2> acheronuk: I know Python though
[21:23] <acheronuk> tsimonq2: and people who did/do have left
[21:24] <tsimonq2> acheronuk: what's the package name?
[21:24] <tsimonq2> I'll take a look :)
[21:24] <tsimonq2> (but no promises)
[21:24] <acheronuk> tsimonq2: ubiquity-frontend-kde I think?
[21:25] <acheronuk> also see: http://pyqt.sourceforge.net/Docs/PyQt5/pyqt4_differences.html
[21:25] <tsimonq2> alright
[21:28] <tsimonq2> acheronuk: I'll look this weekend
[21:28] <acheronuk> tsimonq2: if lubuntu/lxqt want a QT frontend eventually, they will have to figure it out at some point if we don't
[21:29] <acheronuk> or so I guess anyway
[21:29] <acheronuk> tsimonq2: anything is appreciated :)
[21:29] <tsimonq2> alright :)
[21:29] <tsimonq2> \o/ yay
[21:29] <tsimonq2> my fix is in! \o/
[21:30]  * clivejo high 5's tsimonq2
[21:31] <tsimonq2> and kcron too!
[21:31]  * yofel synced the repo for libkgeomap to LP
[21:32] <tsimonq2> yofel: so I don't know if this is still supposed to show 5.2.0... https://launchpadlibrarian.net/274505232/buildlog_ubuntu-yakkety-amd64.kdepim-addons_16.04.3+p16.10+git20160722.1625-0_BUILDING.txt.gz
[21:32]  * tsimonq2 tries to fix
[21:33] <yofel> tsimonq2: don't mind that
[21:33] <clivejo> thats a sync from debian
[21:33] <yofel> oh?
[21:33] <yofel> ok then
[21:33] <tsimonq2> yofel: so I *shouldn't* try to fix it?
[21:33] <yofel> I thought that was thanks to the bug in our build-dep bumper
[21:34] <yofel> tsimonq2: the *version* isn't the issue here
[21:34] <yofel> so not worth fixing
[21:34] <clivejo> I think its a new package
[21:34] <yofel> it's a new package missing from the CI
[21:34] <yofel> hm... according to this script that i'm running a lot of stuff is missing from the CI
[21:34] <yofel> although that's mostly intentional
[21:35] <clivejo> PIM had major changes recently
[21:35] <yofel> the script is now modifying jenkins
[21:36] <yofel> lets see what happens...
[21:38] <yofel> acheronuk, tsimonq2: Btw. if you want to commit something *without* the CI triggering a build, put NOCI into the commit message
[21:38] <acheronuk> yofel: handy to know
[21:40] <yofel> hm, now that added less CI jobs than I hoped
[21:40] <yofel> well, at least breeze-gtk and discover have CI jobs now
[21:41]  * yofel wonders what an easy way is to figure out what jobs we need right now and are missing
[21:42] <tsimonq2> alright yofel 
[21:42] <tsimonq2> yeah nice to know
[21:42] <tsimonq2> yofel: like anywhere or at the beginning?
[21:43] <yofel> beginning I think
[21:43] <yofel> the pattern is (?s).*NOCI.*
[21:44] <yofel> well, anywhere actually
[21:45] <yofel> so, all the stuff with an error below it is missing a CI job: http://sprunge.us/jEDf
[21:47] <yofel> I'll fix the obvious missing PIM parts
[21:48] <clivejo> I want to learn how to do this
[21:48] <blaze> sometimes lp does not trigger dependency-wait builds :\
[21:48] <yofel> so, in short: you clone pangea tooling, install the ruby libs locally with bundler, update the kci.yaml in the ci-tooling, then bundler exec ./update-projects.rb
[21:49] <clivejo> it hasnt been doing that at all recently
[21:49] <tsimonq2> klettres PR incoming
[21:49] <yofel> it should, but might take like 2 or 3 hours
[21:50] <yofel> clivejo: additionally to that, you need an actual user under your name that's a member of the admin role in jenkins, so you can use your auth token for jenkins in the scripts
[21:50] <jimarvan> o/ :)
[21:51] <yofel> hey
[21:51] <yofel> clivejo: regarding fixing what's missing. All that's needed is to manually create the _unstable and _stable branches in the repositories and re-run the script
[21:51] <yofel> that's what I'm doing now
[21:52] <clivejo> have you a script for that?
[21:52] <yofel> no
[21:53] <yofel> I don't want to add everything, so I'm just doing the couple by hand
[21:53]  * acheronuk only gets about 50% of that, but is watching for info
[21:55] <yofel> clivejo: ok, so I made this after all: alias branchcreate='git checkout kubuntu_yakkety_archive; git checkout -b kubuntu_unstable; git push origin kubuntu_unstable; git checkout -b kubuntu_stable; git push origin kubuntu_stable'
[21:55]  * tsimonq2 throws a wild https://code.launchpad.net/~tsimonq2/kubuntu-packaging/+git/kubuntu-klettres/+merge/300957 at acheronuk 
[21:56] <tsimonq2> \o/
[21:56] <tsimonq2> yay
[21:56] <tsimonq2> \o/
[22:03] <tsimonq2> that needs a rebuild, Launchpad error ^
[22:03] <tsimonq2> :(
[22:04] <tsimonq2> same, Launchpad error ^
[22:04] <tsimonq2> clivejo: ^
[22:05] <yofel> building
[22:05] <tsimonq2> thank you yofel 
[22:06] <tsimonq2> yofel: xenial_unstable_akonadi-calendar has been hit by Launchpad failures as well
[22:07] <ahoneybun> mhall119: any word about sponsorship for Akademy/QtCon?
[22:11] <tsimonq2> yofel: that one is an epic fail ^
[22:11] <yofel> yeah... I obviously missed something
[22:12] <yofel> but why did others build...
[22:13] <yofel> I'll just retry it, the yakkety job is running fine
[22:13] <tsimonq2> if I want to fix an application that doesn't have an existing changelog, do I create one?
[22:13] <tsimonq2> I mean entry that I can add in
[22:14] <yofel> hm... which one?
[22:14] <tsimonq2> kalgebra
[22:14] <tsimonq2> yofel: it's a Debian import so it needs an ubuntu1
[22:15] <yofel> tsimonq2: it does have an ubuntu1 in git
[22:15] <yofel> are you on master by chance?
[22:15]  * tsimonq2 forgot to switch branches :(
[22:15] <yofel> heh
[22:15] <tsimonq2> thanks
[22:19] <tsimonq2> kalgebra PR incoming
[22:20] <yofel> oh, discover actually compiled, I'm impressed
[22:20] <acheronuk> tsimonq2: I admire the enthusiasm you have :)
[22:20] <yofel> now what's wrong with akonadimime
[22:20] <tsimonq2> acheronuk: :)
[22:20] <yofel> oh right, that's pimlibs, brrr
[22:20] <clivejo> its part of akonadi!
[22:20] <clivejo> its expected
[22:21] <yofel> lol, that looks like it never ever built in the CI
[22:21] <yofel> OH
[22:21] <yofel>     Qt5WebEngineConfig.cmake
[22:21] <yofel> uhm
[22:21] <yofel> ok, ignore that
[22:21] <tsimonq2> acheronuk: \o/
[22:22] <acheronuk> yep, I wonder when we'll get QtWebEngine :(
[22:25] <jimarvan> Qt5WebEngine?
[22:26] <yofel> the replacement for qtwebkit, essentially chromium with a Qt5 api around it
[22:26] <tsimonq2> kiriki PR incoming
[22:26] <jimarvan> oooooh
[22:26] <jimarvan> sounds sweet :D
[22:27] <yofel> yeah, but not something anyone wants to actually maintain
[22:27] <jimarvan> o.O
[22:27] <jimarvan> I see...
[22:27] <acheronuk> jimarvan: https://anonscm.debian.org/cgit/pkg-kde/qt/qtwebengine.git/
[22:28] <jimarvan> going
[22:29] <blaze> Author Scarlett Clark, lol
[22:29] <jimarvan> :D
[22:30] <jimarvan> very interesting indeed
[22:30] <blaze> it's better to waste your time somewhere else
[22:31] <jimarvan> hmm
[22:31] <clivejo> git fetch simon --by-the-toes
[22:32] <tsimonq2> khangman PR incoming
[22:32] <tsimonq2> clivejo: why? lol
[22:32] <tsimonq2> clivejo: you getting annoyed by all the emails of my many MPs? :D
[22:32] <clivejo> nope
[22:33] <jimarvan> :_)
[22:33] <jimarvan> gn guys
[22:33] <tsimonq2> clivejo: then why? lol
[22:33] <jimarvan> see ya tomorrow
[22:33] <tsimonq2> o/ jimarvan 
[22:33] <jimarvan> if i survive my shoulder pain
[22:33] <jimarvan> o/
[22:33] <clivejo> I call your remote simon
[22:33] <clivejo> so have to git fetch simon
[22:34] <tsimonq2> O__o
[22:34] <acheronuk> clivejo: huh?
[22:34] <clivejo> Rik much have beaten me to the last one !
[22:34] <clivejo> must
[22:35] <acheronuk> ummm https://code.launchpad.net/~tsimonq2/kubuntu-packaging/+git/kubuntu-khangman/+merge/300962
[22:35] <mhall119> ahoneybun: I have a task to review our current fund level, since many of you applied
[22:35] <tsimonq2> oh noes acheronuk 
[22:35] <tsimonq2> nice catch
[22:35] <tsimonq2> hold on
[22:36] <acheronuk> clivejo: you can have them in a bit. I'm sleepy now
[22:36] <clivejo> me too
[22:37] <tsimonq2> D: I'm only getting started XD
[22:37] <clivejo> pace yourself!
[22:37] <tsimonq2> :P
[22:37] <acheronuk> I was going to carry on with plasma in kci today, but it never happened. tomorow maybe
[22:38] <acheronuk> clivejo tsimonq2: enthusiasm of youth!
[22:38] <clivejo> indeed
[22:38] <clivejo> also helps to be in another timezone!
[22:38] <acheronuk> true
[22:39] <tsimonq2> acheronuk: I'm hoping to reduce Rick's price :P
[22:39] <tsimonq2> to 0
[22:39] <tsimonq2> XD
[22:39] <yofel> mhall119: any idea until when you'll have an update on that?
[22:40] <acheronuk> I'm wondering what date I can say my 6 months probation will be up
[22:40] <acheronuk> assuming I get that far!
[22:40] <yofel> well, don't burn yourself out along the way ;)
[22:40] <ahoneybun> you will acheronuk
[22:40] <yofel> other than that, you're like...halfway... I think?
[22:41] <clivejo> there are good days and there are bad days
[22:41] <acheronuk> I've been on and off here since January I think?
[22:41] <acheronuk> but sustained and significant is another measure
[22:41] <yofel> ah, I judged by 'visible contributions'
[22:42] <yofel> but I didn't take that close a look to the logs
[22:42] <ahoneybun> the council can judge on how significant they are
[22:42] <yofel> so feel free to convince me otherwise
[22:42] <ahoneybun> and I think they work is great
[22:42] <ahoneybun> *your work
[22:42] <acheronuk> yofel: I'll work it out sometime. I'm not in a desperate hurry
[22:42] <yofel> hm, I really need to figure out how to set up an external builder for jenkins
[22:43] <yofel> bummer that I can't get docker to work on linode lxd
[22:43] <yofel> probably because they use a custom kernel
[22:43]  * acheronuk can feel the youths catching up, that is all
[22:43] <ahoneybun> I'm tempted to try Unity on this laptop again
[22:43] <yofel> maybe running a VM would work
[22:44] <yofel> like, running docker in a VM in lxd on a cloud node. hurray for abstraction
[22:44] <clivejo> did you do a merge on hangman?
[22:45] <acheronuk> clivejo: no, I left it, as was fubar
[22:45] <clivejo> looks like its been merged with debian
[22:46] <mhall119> yofel: I'll try and have it ready by our wednesday call when we review the requests
[22:46] <yofel> mhall119: ok, thanks!
[22:46] <mhall119> np
[22:46] <ahoneybun> thanks mhall119
[22:46] <ahoneybun> so for sure I can't go
[22:47] <acheronuk> clivejo: I did nothing with that MP
[22:47] <clivejo> I just wonder why that happened
[22:48] <acheronuk> forgot to change branch?
[22:48] <clivejo> ah yes
[22:49] <acheronuk> I've done that once but caught it before it went anywhere
[22:51] <acheronuk> do I set up a personal wiki page on kubuntu or ubuntu wiki?
[22:51] <tsimonq2> acheronuk: fixed https://code.launchpad.net/~tsimonq2/kubuntu-packaging/+git/kubuntu-khangman/+merge/300965
[22:51] <ahoneybun> either, they are the same
[22:51] <ahoneybun> acheronuk: ^
[22:52] <acheronuk> ahoneybun: oh, they share the db then? they look different, but that makes sense
[22:53] <ahoneybun> yea it's just a theme over it
[22:53] <acheronuk> ahoneybun: gotcha
[22:54] <acheronuk> ahoneybun: if I'm going to try to start writing down what I've done, it may as well be there at least in part
[22:54] <tsimonq2> kiten PR incoming
[22:54] <ahoneybun> yea and I'll add a testminal
[22:57] <acheronuk> ahoneybun: thx :)
[22:57] <ahoneybun> np of course
[23:00] <tsimonq2> kdenlive! \o/
[23:02] <tsimonq2> acheronuk: how do I know where files have moved?
[23:02] <tsimonq2> if they are gone, how do I find out where they went?
[23:03] <acheronuk> if they are gone, they may not be built any more. the install section shows all that was built
[23:04] <acheronuk> or/and you can look on KDE source git for a package/project to see if there are any changes on there that account for files no longer being built
 (Photo, 1920x1080) https://irc-attachments.kde.org/0gJEfxBN/file_283.jpg
[23:08] <tsimonq2> alright
[23:08] <acheronuk> tsimonq2: file naming may just have changed also etc etc
[23:09] <clivejo> acheronuk: are you merging kiten?
[23:09] <acheronuk> can be a be obvious. can be a bit of detective work
[23:09] <acheronuk> clivejo: for some reason I got no email on that one?
[23:10] <clivejo> ok Ill do it
[23:11] <tsimonq2> clivejo: https://code.launchpad.net/~tsimonq2/kubuntu-packaging/+git/kubuntu-kiten/+merge/300966
[23:12] <clivejo> yeah got an email about it 
[23:14] <acheronuk> hmmm. it shows in gmail website, but not in email client. must have fallen foul of some filter
[23:14] <tsimonq2> \o/ merged
[23:16] <acheronuk> ok people. I'm calling it a night. :)
[23:16] <tsimonq2> o/ acheronuk 
 @marcinsagol Life is Strange works well so far
[23:29] <valorie> tsimonq2: you're on fire!
[23:29] <valorie> lovely to see you join the team
[23:29] <tsimonq2> :)
[23:30] <tsimonq2> valorie: how are you? :)
[23:30] <valorie> good!
[23:31] <valorie> missing my husband -- he's been on a week-long work trip, and returns tomorrow
[23:31] <tsimonq2> valorie: do you have access to rebuild yakkety_unstable_kcalc please?
[23:31] <tsimonq2> oh okay :)
[23:31] <valorie> are you having a good summer?
[23:31] <tsimonq2> yeah! :D
[23:31] <valorie> sorry, I'm not a packager and don't want to muck stuff up
[23:31] <tsimonq2> alright :)
[23:31] <valorie> ahoneybun: do you have that access?
[23:31] <yofel> kcalc building
[23:32] <valorie> ^^^
[23:32] <tsimonq2> thank you yofel 
[23:32] <valorie> ah, yofel still up
[23:32] <valorie> bit late there isn't it?
 Access for ?
 @Valoriez
[23:32] <valorie> yofel did it
[23:33] <tsimonq2> yofel: this is the same critical error that was in another package, did you find a solution? http://kci.pangea.pub/job/yakkety_unstable_breeze-plymouth/lastFailedBuild/consoleFull
[23:33] <tsimonq2> yakkety_unstable_kpackage - ran out of memory
[23:34] <tsimonq2> yakkety_unstable_kpty - also ran out of memory
[23:34] <yofel> hm, no, I just retried that
[23:34] <tsimonq2> alright
[23:34] <tsimonq2> yakkety_unstable_ktp-contact-runner - needs a rerun, Launchpad error
[23:34] <valorie> gosh, somebody kick LP some new memory!
[23:34] <yofel> that's not LP, that's the CI
[23:35] <tsimonq2> yakkety_unstable_milou - also needs a rebuild because of Launchpad
[23:37] <valorie> oh right
[23:38] <tsimonq2> weird, yakkety_unstable_plasma-desktop is still failing although the appstream data move correction has already been done
[23:39] <tsimonq2> yofel: maybe needs a rebuild? do you know what's going on? ^
[23:39] <tsimonq2> dh_install: Cannot find (any matches for) "usr/share/appdata/org.kde.plasmashell.metainfo.xml" (tried in "." and "debian/tmp")
[23:39] <tsimonq2> dh_install: plasma-desktop-data missing files: usr/share/appdata/org.kde.plasmashell.metainfo.xml
[23:39] <tsimonq2> dh_install: missing files, aborting
[23:39] <valorie> !info plasma-discover-updater
[23:40] <yofel> did someone merge that? because that never built
[23:40] <tsimonq2> yakkety_unstable_systemsettings - needs a rebuild to make sure that there aren't any critical issues, last two builds were inconclusive
[23:40] <tsimonq2> xenial_unstable_khangman, yofel?
[23:40] <ahoneybun> fixes all around
[23:40] <tsimonq2> \o/
[23:41] <yofel> plasma-desktop
[23:41] <tsimonq2> kalgebra, kiriki, khangman, \o/
[23:41] <tsimonq2> \o/
[23:42] <leumas> more \o/!!
[23:42] <yofel> hm...
[23:42] <valorie> plasma-desktop is rather important!
[23:43] <yofel> oh. plasma-desktop is depwait
[23:43] <yofel> uh, but the log says otherwise
[23:43] <yofel> wth
[23:43] <yofel> I'll rebuild it
[23:45] <yofel> plasma-discover deleted
[23:46] <tsimonq2> picmi PR incoming
[23:47] <tsimonq2> yakkety_unstable_ffmpegthumbs - exited with not enough memory
[23:49] <tsimonq2> same with yakkety_unstable_attica
[23:50] <tsimonq2> yakkety_unstable_bomber - Launchpad error, needs rebuilding
[23:51] <tsimonq2> yakkety_unstable_granatier - too little memory
[23:57] <yofel> meh, where are the memory errors coming from. It's not like the server runs OOM
[23:57] <tsimonq2> gwenview PR incoming
[23:58] <valorie> wonderful to see all this work happening
[23:58]  * valorie goes off to eat dinner