[08:58] <lordievader> Good morning
[12:16] <clivejo> anyone know more about this KActivities repository split?
[12:26] <BluesKaj> Howdy folks
[12:26] <clivejo> hi BluesKaj
[12:26] <BluesKaj> hi clivejo
[12:27] <clivejo> how are you today?
[12:27] <BluesKaj> good thanks, clivejo, and you?
[12:28] <clivejo> cold and confused
[12:36] <BluesKaj> clivejo, bummer :/ take a well deserved break perhaps?
[15:35] <snele> clivejo: about kactivities split i think you should ask ivan | home in #plasma
[15:36] <snele> i think he did it
[15:36] <snele> and they talked about that yesterday in #plasma
[15:36] <clivejo> snele: seems Neon has already done it
[19:21] <clivejo> yofel_: ping
[21:49] <clivejo> hi DarinMiller
[21:49] <DarinMiller> Hi clivejo
[21:50] <clivejo> how are you today?
[21:50] <DarinMiller> Very good. Gorgeous early spring day here.  And you?
[21:51] <clivejo> been a nice day here too, but temp is dropping below freezing at the moment
[22:00] <DarinMiller> clivejo how did you learned to package?  I am finding that the packaging rabbit hole is way deeper than anticipated.  
[22:01] <clivejo> DarinMiller: just by doing it
[22:02] <clivejo> Riddell spun up a VPS and walked me through it#
[22:03] <DarinMiller> I have enabled all accounts, read the debian packaging guildelines, read the ubuntu sponship guidleline and am currently reading through the bzr web help.  I still feel I am a long ways from being able to assemble the simplest package.
[22:04] <valorie> DarinMiller: if you decide to take the pill and jump into the hole
[22:04] <valorie> please fix our docs as you go!
[22:06] <clivejo> DarinMiller: where have you got to?
[22:06] <DarinMiller> I would be very happy to fix/update the docs once I understand.  But I am nearly useless with my current level of comprehension.
[22:07] <clivejo> do you understand how we combine the source code and the packaging to build a package?
[22:11] <DarinMiller> No.  I am not sure how bzr and pbuild interact. And when/where/how to apply the correct ppa to the pbuild enviro.  Not sure if bzr is PPA dependent.  I don't have clue how to create a source/build(?) file and if symbols are messed up, I have no idea where to even look.
[22:12] <clivejo> bzr is a VCS
[22:12] <DarinMiller> I feel so green that I hate bothering the people here until I can ask more intelligent questions, but I am floundering on my own trying to figure it out.
[22:12] <clivejo> DarinMiller: dont be silly!  We all started there!
[22:13] <clivejo> do you know how to get a package source?
[22:15] <DarinMiller> using apt-get source, yes.  (I finally enabled the source repositories just this weekend).   I tried using bzr to grab a dolphin branch (bzr branch ubuntu:dolphin) but that failed.
[22:16] <clivejo> if you look in the control file it will tell you where we keep the packaging
[22:17] <DarinMiller> where do I find this elusive control file? :)
[22:18] <clivejo> so run "sudo apt-get source dolphin"
[22:18] <clivejo> you should get a message like this
[22:18] <clivejo> NOTICE: 'dolphin' packaging is maintained in the 'Git' version control system at:
[22:18] <clivejo> git://anonscm.debian.org/pkg-kde/kde-applications/dolphin.git
[22:20] <clivejo> which is a git archive
[22:20] <clivejo> the web interface is here - http://anonscm.debian.org/cgit/pkg-kde/applications/dolphin.git/
[22:20] <DarinMiller> Yes, I have seen that, but did not know where/how to proceed.  I was under the impression, bzr performed similar functions and was the Canonical preferred method.
[22:21] <clivejo> yes and no
[22:21] <clivejo> most of the KDE software is on git
[22:22] <clivejo> we call that Debian git or Alioth
[22:22] <clivejo> if you visit that web interface you will see the repo in a visual format
[22:22] <clivejo> so there are 7 branches
[22:23] <clivejo> kubuntu_xenial_archive is tracking what is in the archive
[22:24] <DarinMiller> OK, following the links....
[22:24] <clivejo> kubuntu_unstable and stable are for KCI
[22:29] <clivejo> they track changes to the /debian folder which is used to create the package
[22:29] <DarinMiller> btw, back at the apt-get source dolphin, it proceeded to dl packages, but gave me this message at the end: Can't drop privileges for downloading as file 'dolphin_15.08.2-0ubuntu1.dsc' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied).  Am I missing an account setting somewhere?
[22:29] <clivejo> I get that message too
[22:29] <DarinMiller> oh, ok.
[22:30] <clivejo> I tend to use dget
[22:30] <clivejo> because the packages we are working on dont tend to be in the archive
[22:31] <DarinMiller> with dget, you pull the packages from here: http://anonscm.debian.org/cgit/pkg-kde/
[22:32] <DarinMiller> ?
[22:32] <clivejo> nope
[22:32] <clivejo> dget pulls the package by using a .dsc file
[22:32] <clivejo> for example, if you look on my PPA
[22:32] <clivejo> https://launchpad.net/~clivejo/+archive/ubuntu/xenial/+packages
[22:33] <clivejo> if you go down to purpose
[22:33] <clivejo> expand that package
[22:33] <clivejo> in the Package files you will see a purpose_1.0-0ubuntu1~ubuntu16.04~ppa1.dsc
[22:34] <clivejo> if you menu click and Copy link location you can copy the URL to the clipboard
[22:34] <clivejo> then run "dget https://launchpad.net/~clivejo/+archive/ubuntu/xenial/+files/purpose_1.0-0ubuntu1~ubuntu16.04~ppa1.dsc"
[22:34] <clivejo> that will grab the source from my PPA
[22:35] <DarinMiller> OK, I follow...
[22:35] <clivejo> so run that command
[22:36] <clivejo> you will get an error from gpg
[22:36] <clivejo> it basically because I signed the file and you cant check the signature
[22:36] <DarinMiller> Yes, public key not found, validation failed.
[22:37] <clivejo> now do an "ls"
[22:37] <clivejo> should be 3 files
[22:38] <DarinMiller> yes  2 .xz and a dsc file
[22:38] <clivejo> now run "dpkg-source -x  *dsc"
[22:39] <clivejo> you should now see a folder with the source code and in contains a /debian folder
[22:39] <clivejo> so "cd purpose-1.0/debian/"
[22:40] <clivejo> and list contents
[22:41] <clivejo> you should see all the packaging files
[22:41] <clivejo> control, rules, install files etc
[22:42] <DarinMiller> I had to kill my dophlin packages as they raised a conflict...
[22:42] <clivejo> sorry, should have said to mkdir a clean folder to work in
[22:42] <DarinMiller> Ok, yes.. opened control file in kate....
[22:43] <clivejo> Vcs-Browser: tells you where the packaging is kept
[22:43] <clivejo> Build-Depends: are a list of all the packages needed to actually build it
[22:44] <clivejo> then a list of the packages it will try to put the built files into
[22:44] <clivejo> ie Package: libkf5purpose-dev
[22:45] <clivejo> if you take a peek into libkf5purpose-dev.install
[22:46] <DarinMiller> hang on a sec, where/how do I use vcs-browser?  Is that a website, app or a file? 
[22:46] <clivejo> VCS is Version Control System
[22:47] <clivejo> vcs browser should be a web link
[22:47] <DarinMiller> nevermind, I see it now.....
[22:48] <clivejo> http://anonscm.debian.org/cgit/pkg-kde/frameworks/purpose.git
[22:49] <DarinMiller> OK, peeking at libkf5purpose-dev.install... (wasn't too impressed...)
[22:49] <DarinMiller> :)
[22:49] <clivejo> LOL
[22:49] <clivejo> its important file!
[22:50] <clivejo> if you dont "install" the files, it wont work!
[22:51] <clivejo> ok so in your terminal go back to the purpose-1.0 folder
[22:51] <DarinMiller> done
[22:52] <clivejo> how many CPU cores have you?
[22:52] <DarinMiller> 4 cores, 8 threads
[22:52] <clivejo> go run "debuild -j8"
[22:53] <DarinMiller> mising build dep, looks like I need to intall some stuff, just a sec..
[22:59] <clivejo> you will then see screens of info scrolling by!
[23:00] <clivejo> and get a sense of falling!
[23:00] <clivejo> what you are seeing is the build log
[23:01] <clivejo> something like this - https://launchpadlibrarian.net/243676443/buildlog_ubuntu-xenial-amd64.purpose_1.0+git20160228.1155+16.04-0_BUILDING.txt.gz
[23:01] <DarinMiller> still installing deps for debuild....
[23:01] <clivejo> this is why we use pbuild
[23:02] <clivejo> pbuild keeps all of this in a nice contained virtual environment
[23:02] <clivejo> but it helps to see this process at least once
[23:03] <DarinMiller> yes, i have seen you and scarlet post links to said files and yofel seems to be able to discover the issues therein almost instantly.
[23:03] <DarinMiller> Ok, building now...
[23:04] <DarinMiller> OK, build complete.... searching for the log...
[23:04] <clivejo> the "log" is all that output that scrolled by 
[23:05] <DarinMiller> oh ok, found it :)
[23:05] <clivejo> its shows all the prechecks for build deps, then the actual building and then the installing into the .debs
[23:06] <clivejo> ok so cd .. 
[23:06] <clivejo> and ls
[23:06] <clivejo> you should now see the actual .deb files
[23:06] <DarinMiller> yes!
[23:07] <clivejo> so you have actually built that package
[23:07] <clivejo> your computer used the source code to build all the binary files and then put them into .deb files for install on a debian based system
[23:08] <DarinMiller> way cool!
[23:08] <clivejo> isnt it!
[23:08] <clivejo> but the problem is that the source code changes and new features are added
[23:09] <clivejo> new files are created and old ones removed
[23:09] <clivejo> or the build requires new packages to actually be able to compile
[23:11] <DarinMiller> I am still confounded on how to unravel those mysteries.
[23:11] <clivejo> so a couple of days ago when KCI triggered a rebuild of this package, we got a notification in the channel that purpose build failed!
[23:12] <clivejo> the bot posts a link
[23:12] <clivejo> http://kci.pangea.pub/job/xenial_unstable_purpose/
[23:13] <clivejo> see down the left build #42
[23:14] <clivejo> click on the [amd64] and you will see the buildlog for that job
[23:14] <clivejo> do you see it?
[23:14] <DarinMiller> recipe for target 'pre_install_dh_install' failed
[23:15] <clivejo> yup!
[23:15] <DarinMiller> I see it, but I don't know what that means.
[23:15] <clivejo> the packaging was instructing it to install any files located in usr/share/kaccounts/services/
[23:15] <clivejo> but the installer couldnt find any files in that location
[23:16] <clivejo> but we do see a file being installed in a simular location
[23:16] <clivejo> - Installing: /«BUILDDIR»/purpose-1.0+git20160225.2316+16.04/debian/tmp/usr/share/accounts/services/twitter-microblog.service
[23:17] <clivejo> so for some reason upstream are now using usr/share/accounts instead of usr/share/kaccounts
[23:18] <clivejo> well actually they were using accounts then changed to kaccount and then moved back again!
[23:18] <clivejo> I have no idea why!
[23:19] <clivejo> if you look here
[23:19] <clivejo> http://anonscm.debian.org/cgit/pkg-kde/frameworks/purpose.git/log/?h=kubuntu_unstable
[23:19] <clivejo> 11 days ago Bhushan Shah changed the install path
[23:20] <clivejo> this is his commit
[23:20] <clivejo> http://anonscm.debian.org/cgit/pkg-kde/frameworks/purpose.git/commit/?h=kubuntu_unstable&id=ffacd521fbeb79b2d911719a433955edb3671d0b
[23:21] <clivejo> so he edited the file 	debian/libkf5purpose5.install and changed accounts to kaccounts
[23:21] <DarinMiller> This is a debian member?
[23:21] <clivejo> I think hes a Blue Systems employee, not sure
[23:21] <DarinMiller> We have to discover these changes randomly?
[23:22] <DarinMiller> How did you find this page?
[23:22] <clivejo> well all this is happening on the KCI
[23:23] <clivejo> [kubuntu-ci] Project wily_unstable_kfilemetadata build #148: FIXED in 24 min: http://kci.pangea.pub/job/wily_unstable_kfilemetadata/148/
[23:24] <clivejo> you will see messages like that popping up
[23:25] <clivejo> or the dreaded " STILL FAILING" or "FALTURE"
[23:25] <DarinMiller> Sounds like we need to use a variable list that is autoupdated when packages are built. Seem strange with all this automation that we have to manually discover such changes.  
[23:26] <clivejo> it cant really be automated
[23:26] <clivejo> needs knowledge
[23:26] <clivejo> or how the packages interact and so forth
[23:27] <clivejo> kubuntu works very closely with Debian#
[23:27] <clivejo> and we use their git repo
[23:28] <clivejo> and that is one of the problems we have
[23:28] <clivejo> there are only a few of use with debian git commit access
[23:29] <clivejo> but you can submit git diffs to fix problems :)
[23:30] <clivejo> and KCI is working with the git repo from upstream
[23:31] <clivejo> so frameworks, plasma, apps +1
[23:32] <clivejo> the idea is that if we can keep on top of the changes, new releases will be a lot easier to manage
[23:33] <DarinMiller> make sense
[23:34] <clivejo> but KCI does do its job by flagging up packages that need attention
[23:34] <clivejo> at the moment we have two major problems
[23:35] <clivejo> 1) kactivities is being split out into new packages
[23:35] <clivejo> 2) KDEPIM has major problems
[23:36] <DarinMiller> yes, I have been watching the PIM chaos from a distance and trying to figure out whats going on.
[23:37] <clivejo> http://kci.pangea.pub/job/xenial_unstable_kactivities/
[23:38] <clivejo> if you look at the downstream projects
[23:38] <clivejo> 15 projects are failing because of that one breakage
[23:40] <clivejo> oh, thats a missing file issue
[23:42] <clivejo> and symbols
[23:51] <clivejo> and the kubuntu-ci bot is broken again!
[23:52] <clivejo> was wondering why it was so quiet in here!