=== kitterma is now known as ScottK [06:16] good morning [08:35] clivejo: what is the muon FFe status ? === Blizzzek is now known as Blizzz [10:21] : In need of a sponsor [12:22] Hi folks [13:15] regarding libqapt3-runtime, should this not pull in libqapt3 which is the actual library? [13:16] : Muon - I built it yesterday, it Crashes when checking for updates [13:16] : Might be a Lib problem, but need to debug [13:16] : Ovidiu is assiting me on this [13:16] : But... [13:17] Sick_Rimmit it needs libqapt [13:17] : I have no authority with KDE, and am still trying to work out how to assign myself as maintainer [13:17] Ive built it too and its in my PPA [13:17] Did you see my email on devel list? [13:17] : Ah ha alrighty, so I could test with that, perhaps this evening [13:17] : No at work at moment [13:18] I was in touch with Carlos [13:18] : I am not MOTU, and have no commit rights, so I too will need a Mentor / Sponsor to work with me [13:18] Carlos has commit access [13:18] : But am happy to dash around breaking the code 😃 [13:19] its him that fixed the close and cache bugs [13:19] : Ah ha, alright I will send him an email this evening [13:19] https://lists.ubuntu.com/archives/kubuntu-devel/2016-March/010299.html [13:20] but that cache bug fix requires an updated libqapt [13:20] to correctly handle the signals [13:21] : OK, well happy to work on this, this evening if you're around [13:21] https://lists.ubuntu.com/archives/kubuntu-devel/2016-March/010340.html [13:22] there been a few people testing the latest git version, including myself and it works great [13:23] I opened a FFE to try and get it into Xenial [13:23] but need a sponsor (Bug 1562406) [13:23] bug 1562406 in muon (Ubuntu) "[FFe] Update to latest upstream version" [Undecided,Confirmed] https://launchpad.net/bugs/1562406 [14:28] Yay, all the Kubuntu PPA keys seem to have fixed now! apt is no longer complaining about weak keys on any of them [16:45] : ;) [19:35] clivejo: Hi there [19:36] ovidiu-florin: You about good buddy ? [19:39] yup [19:39] Hi [19:39] Hi [19:39] hows you? [19:39] Good, been a busy day, but back home now [19:39] hiho [19:40] Wanted to try out MPM with you libqapt on 16.04 [19:40] Im trying to get back control of my system [19:40] Was hopinf ovidiu-florin was about as he was doing some debugging yesterday [19:40] left KCI open in firefox and its using 5Gb of memory and maxing out a CPU core [19:40] I'm just getting a 16.04 VM ready now, which will take me about 30 mins [19:41] Restart Firefox, and it'll stop doing that [19:41] I think FF could do with a little optimisation work [19:42] so to bring you up to speed on NPM [19:42] MPM even [19:42] yes please do [19:42] acheron88 reported that he had built from git [19:42] and it was working up until the start of March [19:43] so we debugged it [19:44] http://paste.ubuntu.com/15490905/ [19:45] I built it from the Master branch which I pulled about 4 days ago. builds and runs, but crashes when checking updatres [19:45] yup [19:45] same as that bug report [19:45] crashes on QObject::connect: No such signal QApt::Backend::cacheReloadStarted() [19:46] Carlos fixed two bugs on the 3rd March [19:47] one was to do with closing the main window [19:47] the other was that updating caused a blank package list [19:47] Ah yes I saw those in the commit logs [19:47] so he added code that allows qapt to signal [19:47] https://quickgit.kde.org/?p=libqapt.git [19:48] so basically you need the two packages updated to make it work [19:48] we found that if we reverted the last commit to muon, it worked [19:49] but Carlos explained to me what he was doing and I realised it was better to include that fix [19:49] Ah alright [19:49] so packaged libqapt and muon [19:49] build I did that worked straight off was on 2nd March [19:49] hi acheron88 :) [19:49] hi :) [19:49] OK, and you have a ppa with the latest lib in it yes ? [19:50] yes, both libqapt and muon [19:50] Oh both right cool, do they work ? [19:50] I added a dep on the latest version of qapt too [19:50] seems to [19:50] about 6 people have been testing it [19:50] Ah ha, right that excellent [19:50] so I opened a FFE [19:50] not tested exhaustively, but not managed to crash it yet [19:51] to try and get the fixes into Xenial [19:51] and the status is ? [19:51] but if you could get in touch with Carlos I think hes interested in keeping Muon updated [19:51] I need a sponsor [19:52] Yep, I will do that [19:52] like yofel or someone with MOTU [19:52] Carlos I mean [19:52] hes talking about giving it a face lift [19:52] new QML/declarative UI [19:53] be nice if we could have some input in that and maybe help him out [19:53] coding is not one of my strong points [19:53] Well, I know ovidiu-florin and I will assist [19:53] havent coded since uni [19:54] nor here. can build it, but not code it that much [19:54] I can usually follow what its doing [19:54] mine neither, but am happy to try pussling with it [19:54] pzzuling [19:54] oh you know what I mean [19:54] but sitting down and actually writting code is beyond me [19:55] well it seems that discover and updater have been stripped out of Muon and are now in the plasma-discover package [19:56] so Muon is now the stand alone package manager [19:56] good. that means you can apt purge them and not affect anything else :) [19:57] acheron88: do you know how to find build deps? [20:00] Emailed Carlo [20:02] clivejo: build-deps on source without packing/debian folder? [20:02] seems a nice guy :) [20:03] or something already packaged? [20:03] yeah, I hacked the packaging from old muon packaging [20:03] there is probably some build deps in the packaging that arent needed any more [20:03] Ive messed up my pbuild [20:05] I think there is some script/command or something that does a build or dummy build and logs what depends are actually needed by the compilation? [20:05] can't recall what is is or where to find it though [20:05] http://anonscm.debian.org/cgit/pkg-kde/plasma/muon.git/tree/debian/control?h=kubuntu_xenial_archive [20:06] thats the old control file, listing the build dep's LP installs in order to build it [20:06] apt-cache showsrc | grep Build-Depends ? [20:06] acheron88: do you know how to package? [20:07] I know how to make some adjustments to what other people have packaged, and then rebuild [20:07] but not really from the ground up or in detail [20:11] which of your PPA's has Muon and LibQapt [20:12] https://launchpad.net/~clivejo/+archive/ubuntu/xenial [20:13] Ah perfect, I'll install that on my test VM now [20:13] uninstall the local build first, if you have it [20:13] acheron88: are you using the one from my PPA? [20:17] at present, yes [20:17] sorry, his name is Carlo Vanini [20:17] no s [20:17] :/ my bad [20:18] Any use? https://www.debian.org/doc/manuals/maint-guide/dreq.en.html [20:21] http://paste.ubuntu.com/15562746/ [20:21] * sick_rimmit dives off to look at debian link [20:21] acheron88: I think thats runtime deps [20:21] then -dev packages for those [20:22] its libQApt.so.3 that was causing us the problem [20:23] Ah brilliant [20:23] "and for each library listed, e.g., libfoo.so.6, and for each library listed, e.g., libfoo.so.6, execute dpkg -S libfoo.so.6" [20:23] Is debian where you guys go for your documentation about how to package etc.. etc.. [20:23] "Then just take the -dev version of every package as a Build-Depends entry." [20:23] what Im looking for is a list of packages we would need to install on a clean system in order to build the source code into binary [20:23] sick_rimmit: yes, debian is our upstream [20:24] most of our packaging is on debian git too [20:24] I've been trying to use the Ubuntu docs, and failing or getting lost [20:24] That is what the debian link to gets to in the end, the build deps [20:24] sick_rimmit: yeah, they need updated [20:25] supposedly [20:25] acheron88: but you will also need things like extra-cmake-modules and other package building tools [20:26] yes, but that's easily worked out from trying to build yourself from git [20:26] sick_rimmit: this is the current packaging for muon on debian git - http://anonscm.debian.org/cgit/pkg-kde/plasma/muon.git/ [20:27] cmake/configure moans about what it needs but doesn't have [20:27] acheron88: do you have a clean system in order to do that? [20:27] like a pbuild or something [20:28] sick_rimmit: kubuntu_xenial_archive is our branch [20:28] mostly I'm just building for myself, and have plenty of HD space, so just install what I need on that machine itself [20:29] but that packaging is for the old muon (updater, discover and muon PM) all in one [20:29] acheron88: no problem, Im just looking for a short cut! [20:30] chroot of a basic system to try builds in? [20:30] yeah [20:30] rather than pbuilder [20:30] thats what pbuild is really, just a chroot of a nice clean system [20:31] So the muon packaging, is that basically the contents of the /debian directory / [20:31] ? [20:31] sick_rimmit: yup [20:31] Ah ha, now I think I see what your doing [20:31] so you not doing dh_make and all that [20:32] the packaging actually does that too [20:32] you're merging KDE packages with Debian packaging and doing a Debuild [20:32] the last standalone packaging for muon was v5.4.3 presumably? [20:32] see the debian/rules file [20:33] we take the source code and mash it together with the packaging and if all goes well we get .deb files at the end [20:33] the packaging is like the recipe of how and where everything goes [20:34] So are you using git subpackages ? [20:34] I take a git snapshot [20:34] basically git clone the kde archive [20:34] should really learn how to package properly [20:35] then create a tarball of that, I called it muon_5.5.0+git20160326.orig.tar.gz [20:35] acheron88: Are you comfortable with packaging to .deb from scratch ? [20:35] sick_rimmit: not a chance [20:36] OK [20:36] acheron88: feel free to ask :) Also, come to the packaging party! [20:36] may well do [20:36] Yes, to be fair I think we are all at different stages of trying to figure packaging out [20:37] I'm following you clivejo [20:37] debain devs do seem to have gone that extra mile out of their way to make it complicated [20:37] sick_rimmit: true, but we can help each other. There are always things one person picks up and understands better [20:38] Yes that's right [20:38] acheron88: it does look that way, and I feel your pain. But I think they designed in a way to make you think about what you are doing and therefore flag mistakes easier [20:39] keep meaning to start here and go through the guides: http://packaging.ubuntu.com/ [20:39] We'll be doing that at the party [20:39] acheron88: I wouldnt!! I read those things for ages [20:39] Going through getting everything setup [20:39] only way to learn is to get your hands dirty and actually do it [20:39] clivejo: fair enough [20:40] At the party on the 15th, you can follow along ask questions etc.. [20:41] sounds a plan [20:42] OK. gotta go [20:42] hope you get muon in xenial :) [20:42] OK, c u later [20:42] thanks for your help acheron88 [20:45] * clivejo re-creates pbuild environment [20:47] * sick_rimmit setting my bzr and DEBFULLNAME crudentials [20:50] there we go, I'm all setup [20:53] I'll be going through those steps again on yofel server at the party so folks can have a crack at it themselves [20:54] sick_rimmit: do you know how to get the packaging from LP? [20:55] No.. the way I did it when Riddell showed me was to copy the /debian folder from the current package, [20:56] something like that it was quite some time ago [20:56] I have a sense that dh_make is the right way to go as it will make all that for you [20:56] but of course that for new [20:57] I it's an update then the old stuff needs to be kept too [20:57] Ah I get mixed up anyways [20:57] there is jusy too many ways to do too many things [20:57] ok, well lets grab my muon packaging [20:58] so go to the packages page on my PPA - https://launchpad.net/~clivejo/+archive/ubuntu/xenial/+packages [20:58] click the arrow beside muon [20:58] k [20:58] and you can see the package files? [20:59] yes see em [20:59] so you can either download the packaging by downloading muon_5.5.0+git20160326-0ubuntu1~ubuntu16.04~ppa2.debian.tar.xz [20:59] or you can use dget which will grab the packaging and source code [21:00] Ah yes dget I remember [21:00] so dget https://launchpad.net/~clivejo/+archive/ubuntu/xenial/+files/muon_5.5.0+git20160326-0ubuntu1~ubuntu16.04~ppa2.dsc [21:00] dget needs a dsc file to work with [21:01] that will grab both the source code and the packaging [21:01] got it [21:02] so if you do an ls, you should have 3 files [21:02] *.orig.tar.gz is your source code [21:03] and *.debian.tar.xz is the packaging [21:03] yep I see that [21:04] so unpack the packaging - tar -xvf muon_5.5.0+git20160326-0ubuntu1~ubuntu16.04~ppa2.debian.tar.xz [21:05] you will get a debian folder [21:05] ah yes [21:05] now unpack the source code - tar -xvf muon_5.5.0+git20160326.orig.tar.gz [21:06] you will get a muon folder [21:06] libmuon [21:06] ? [21:07] i.e /debian/libmuon [21:07] yeah, there are still issues we need to clean up with the packaging [21:07] was going to go through it with you [21:08] the first "problem" is the way I grabbed the git snapshot [21:08] do you notice in the sourcecode there are .git folders? [21:09] cd muon [21:09] ls -al [21:10] hmm [21:10] there is a folder called .git [21:10] I have /muon folde missing [21:10] did you unpack the source code? [21:10] do I need to upack muon..orig.tar.gz too [21:10] tar -xvf muon_5.5.0+git20160326.orig.tar.gz [21:10] no [21:10] yes [21:11] 2 secs, now its making more sense [21:11] Ok got /debian /muon/.git [21:11] we're there [21:12] orig.tar.gz is the source code I grabbed from KDE git here - https://quickgit.kde.org/?p=muon.git [21:12] ok cd into muon [21:12] k [21:12] so basically .git and .reviewboardrc shouldnt be there [21:13] * clivejo was hacking and didnt do it properly [21:14] Hmm [21:14] that is a hidden folder git uses to track changes and history [21:14] so we probably want to do a git checkout rather than a snapshot [21:14] you reckon > [21:14] ? [21:15] yes, thats what I should have done [21:15] but I cloned it [21:15] taking up space for no reason [21:16] I'm starting to figure what KCI might be doing now [21:16] Pulling KDE source from GIT, Debian packaging from Debian. running Debuild [21:16] maybe ? [21:17] exactly [21:17] ah ha brilliant [21:18] Ideally we would want to develop Jenkins jobs for each new package we want in Kubuntu then right ? [21:18] Launchpad doesnt like sourcecode with the same name [21:18] so I cant just delete these files and upload again [21:18] Ah right [21:19] so my plan is to rename the new sourcecode (minus the git faff) and use a current date stamp [21:19] Yes that sounds like a good solution [21:19] so my new source will be muon_5.5.0+git20160330.orig.tar.gz [21:19] repack and dput ? [21:20] perfect [21:20] yes, but there are few more problems! [21:20] oh [21:21] so go back up and cd into debian folder [21:21] yep [21:22] oh actually, we'll grab the source and prepare the orig file first [21:22] k [21:22] so back to your working folder [21:22] k [21:22] the one with debian and muon in it [21:22] yep [21:22] so we will delete the muon folder [21:23] and muon_5.5.0+git20160326.orig.tar.gz [21:23] done [21:29] * clivejo scratches head [21:30] Im not sure how to grab a snapshot without those files! [21:34] I usually just delete them manually [21:35] hang on I have a git book link one sec I find it [21:37] ok I used git clone kde:muon [21:37] v [21:37] then git archive --prefix=muon/ -o ../muon_5.5.0+git20160330.orig.tar.gz HEAD [21:37] https://www.git-scm.com/book/en/v2 [21:38] that seems to do what we need [21:38] thats something I need to ask yofel or sgclark [21:39] hmmm I deleted muon folder, and so now have not git config for kde:muon [21:39] Doh! [21:41] do you have the settings for your .gitconfig file? [21:42] Nope. so git doesn't know what kde is [21:42] well kde: [21:43] is [21:43] https://sysadmin.kde.org/services/code-repositories/ [21:44] git clone git://anongit.kde.org/muon.git [21:44] works [21:45] you can use that [21:45] Bingo [21:45] nice git archive command foo clive [21:46] just learned something myself [21:46] isnt this fun! [21:46] Yes, it's good crack when working together [21:47] so you got a clone? [21:48] yes, I archived from it to [21:48] was just going to see if that removed the .git folde [21:48] r [21:48] so you cd into the muon folder [21:49] and run git archive --prefix=muon/ -o ../muon_5.5.0+git20160330.orig.tar.gz HEAD [21:49] Yes, [21:49] you can then delete the muon folder [21:50] I unpacked it and there is no .git folder, so Woo Hoo that's one bit [21:50] phewww [21:50] now for .reviewboardrc [21:50] * clivejo wipes sweat off brow [21:50] that can stay [21:50] it is part of the KDE archive [21:51] * sick_rimmit copies git archive command to packaging Basket [21:51] usually I just delete the .git and .reviewboardrc manually [21:51] Im not sure what is best practice, we need to ask [21:53] Interesting [21:53] https://git-scm.com/docs/git-archive [21:53] usually with KDE software we download the tarball from http://download.kde.org/ [21:53] Take a look at --remote [21:54] It might be possible to pull an archive from the remote all in one command [21:55] possible, this is all new to me [21:56] most sofware is pre-tarballed ready for use [21:56] like this [21:56] git archive --remote=git://anongit.kde.org/muon.git --prefix=muon/ -o ../muon_5.5.0+git-tester.orig.tar.gz HEAD [21:56] That will work with any KDE remote [21:57] Now that's groovy [21:57] wow yes it is [21:58] you dont need the ../ then [21:58] Ah yeah ! that's right [21:58] * clivejo adds command to his packaging bible [22:00] I wonder is that a proper tar.gz file format though? [22:01] Ah no, I don't think it is [22:02] --format= [22:02] Format of the resulting archive: tar or zip. If this option is not given, and the output file is specified, the format is inferred from the filename if possible (e.g. writing to "foo.zip" makes the output to be in the zip format). Otherwise the output format is tar. [22:02] So its just a plan tar [22:02] or you can specify zip with the --format switch [22:03] But that's OK as a .tar file for the purpose of packaging [22:03] just need to change the -o filname.tar [22:05] I guess we could just untar it [22:05] and then use tar -cvzf to create a tar.gz [22:05] Yes just tar -xvf [22:06] or just gzip it [22:06] hmmm I wonder [22:08] I would just grab a snapshot from quickgit [22:09] Here is some more Bash sauce [22:10] git archive --remote=git://anongit.kde.org/muon.git --prefix=muon/ -o ./muon_5.5.0+git-tester.orig.tar HEAD; gzip muon_5.5.0+git-tester.orig.tar [22:10] That'll pull it, tar it, and gzip it [22:11] you end up with *.orig.tar.gz [22:11] http://i.imgur.com/RDsRRRb.png [22:11] but good to know how to do it from git all the same [22:12] Ah yes, but with the CLI above it removes the .git folder from the source [22:12] so we don't have go rm'ing it [22:12] so does the snapshot link it the git web gui [22:12] More than one way to skin a cat! [22:13] not .git folder in each snapshot [22:13] Oh [22:13] lol [22:14] no. your way is good, as you may not always have a handy way to do that via the web [22:14] Maybe just needs to be a bit more fancy... [22:16] well Ive learned something tonight! [22:16] #!/bin/bash; git archive --remote=$REMOTE --prefix=$PROJECT -o $PATH+FILE+DATE HEAD; gzip $PATH+FILE+DATE [22:17] That's pseudo code, but we could rap that into a shell script, and have do some magic across a set of proejcts [22:18] anyways.. maybe I muck about with that another time [22:18] sick_rimmit: its worth noting this is more advanced packaging :P [22:19] I'll have a crack at shell scripting something, not right now though [22:19] another day [22:19] just dont make the same mistake I did and forget about the .git folder [22:20] but to go in the archive we need to fix these rooky mistakes [22:21] alright where we up to with the packaging [22:21] Im gonna have to go soon, but Ill give you an idea of what needs fixed [22:22] so in the debian folder [22:22] k [22:23] we need to change the version to muon 5.5.0+git20160330 [22:23] we need to check the build deps in the control file [22:24] remove the libmoun stuff [22:25]