[00:01] ah sgclark decremented to libkf5screen6, but the symbols file is refering tp libkf5screen7 [00:06] clivejo: sitter and I went through all the old kubuntu pages on the ubuntu wiki, and copied what was good [00:06] if you see something we missed, please flag it somehow so we can pick it up [00:07] we didn't remove much, since that is 8 or so years of kubuntu history [00:16] * clivejo is off to bed [00:16] night all [00:17] niters clivejo [00:18] sweet dreams [00:21] bye [07:15] yofel: does this mean that this had a warning? 01:03:26 W, [2015-12-30T01:03:26.684863 #1] WARN -- : APT run (apt-get, ["-y", "-o", "APT::Get::force-yes=true", "-o", "Debug::pkgProblemResolver=true", "update"]) [07:50] Yeee, I fixed one [07:50] kind of... [08:00] cool! [08:03] I don't understand why this one fails [08:51] Good morning. [09:00] morning lordievader [09:01] Hey ovidiu-florin, how are you doing? [09:02] I'm looking into http://kci.pangea.pub/job/xenial_stable_akonadi-calendar to see why it fails [09:03] so, akonadi-calendar v15.12 should build just fine [09:04] Im' looking into kcalcore [09:04] Lots of 'cannot access'... [09:06] Is it supposed to be :? [09:10] I don't know [09:11] I can imagine that cannot be found if it is given like that to cd ;) [09:42] ^ faild because of KWallet failing [09:42] dh_install: libpam-kwallet5 missing files (lib/*/security/pam_kwallet5.so), aborting [09:42] debian/rules:27: recipe for target 'override_dh_install' failed [09:43] I'd like to test this localy [09:43] how can I do that? [09:43] yofel? clivejo? [09:44] I've started another build to see if the build logs are still validhttp://kci.pangea.pub/job/xenial_stable_kwallet-pam [09:44] valid* http://kci.pangea.pub/job/xenial_stable_kwallet-pam [09:49] ovidiu-florin: I suppose you can do that in a pbuilder environment using the sources. [09:49] lordievader: I don't know how to do that, or how to set one up [09:50] Setting it up ain't to difficult [1], but it could be that the Kubuntu team has better ways ;) [1] https://wiki.ubuntu.com/PbuilderHowto [09:50] ovidiu-florin: got a buildlog for kwallet? [09:50] kwallet-pam [09:51] clivejo: ^ [09:51] clivejo: https://launchpadlibrarian.net/232295000/buildlog_ubuntu-xenial-amd64.kwallet-pam_4%3A5.5.1%2Bgit20151230.0942%2B16.04-0_BUILDING.txt.gz [09:52] the dh_install fails [09:52] what's that? [09:53] where is this from? [09:54] kci? [09:54] yes [09:55] might be better to fix it in xenial archive [09:55] http://qa.kubuntu.co.uk/ppa-status/plasma/build_status_5.5.2_xenial.html [09:56] ovidiu-florin: have you a xenial installation? [09:57] or a pbuilder? [09:57] same error [09:57] clivejo: no [09:57] how do I set one up? [09:57] ok, you need one really [09:58] first install the necessary packages [09:58] sudo apt-get install pbuilder debootstrap devscripts [09:59] ovidiu-florin: maybe start a notepad so we can add this to the docs [10:00] clivejo: The Ubuntu/Debian docs on pbuilder are quite nice. [10:00] clivejo: add it in the setup section [10:00] what we need is any different? [10:01] lordievader: yeah, but bit flakey on setting up different arch and distributions [10:01] Is it? [10:02] ok, ovidiu-florin is new to this, we'll use him a guinea pig! [10:03] ovidiu-florin: your task is to setup a xenial pbuild environment :) [10:03] yeeey [10:03] can I do this in a wily systme? [10:03] * clivejo has to go walk the pup [10:04] clivejo: how much do you walk it? [10:04] ovidiu-florin: yup, the whole idea of this is to create a building environment separate to your host [10:04] I have to do the same [10:04] clivejo: I was thinking of building a docker image for this [10:05] never done that [10:05] I believe LP uses pbuild [10:05] No problem [10:05] so we can create a nice clean LP like environment [10:05] clivejo: when do you go, and how ong do you walk your dog? [10:06] ovidiu-florin: hard to say, depends on weather and what else hes been doing [10:07] I asked because I thought we should go at the same time [10:07] if hes been "helping" me on the farm I dont tend to walk him on the lead as much [10:07] Storm Fred has left me with a few issues to clean up [10:08] Thanks Fred! [10:08] I better go before he eats my wellies [10:58] clivejo yofel https://hub.docker.com/r/ovidiub13/kubuntu-packaging-devel/ [10:59] you can check the github repo for more info [10:59] and you can see the Dockerfile to see what it does [10:59] so far I've done only what clivejo told me [12:11] ovidiu-florin: thanks, I'll look at it in ~3h or so [12:12] do you know a good docker guide? I'm not very familiar with it yet. Even if I'll probably manage to get the image running at least [12:27] yofel: to get the image you have the command on the image page [12:28] just like github shows you the git clone command [12:28] yofel: to run the image, depends on the image and what it does [12:29] the image is the output from the Dockerfile or did you modify it later? (if that's possible) [12:30] good start at least, but we'll need a way to configure it, or add a simple setup script (for stuff like DEBEMAIL etc.) [12:30] yofel: of course [12:31] I have that in plan, but I don't know yet what to add [12:31] yes, it's the output of the Dockerfile [12:32] it's an automated build from the Github repo [12:32] Hiyas all [12:40] hi BluesKaj [12:40] yofel: the best docker tutorial is the official Docker documentation [12:41] hm ok. Last time I read it I didn't get very far. But I didn't really have something to work on either back then. [12:42] hi ovidiu-florin, yp [12:43] yofel [12:43] hey [12:46] bbl [13:13] yofel: should I add build-essential and cmake to the image? [13:15] clivejo: are you back? [14:51] yofel: are you back? [14:54] hiho [14:55] tomorrow Alpha 1 of Xenial :) [15:07] ovidiu-florin: RE [15:07] so that's a yes? [15:07] ovidiu-florin: offhand I would add: ubuntu-dev-tools, pkg-kde-tools, dpkg-dev [15:08] added [15:08] for KA we'll need some python and ruby stuff, but python-launchpadlib, python3-launchpadlib are the only ones I know offhand [15:08] anything else? [15:10] let me look through things a bit [15:10] awesome [15:10] git, git-buildpackage [15:10] bzr-builddeb [15:11] python-debian, python3-debian [15:15] python-distro-info python3-distro-info [15:16] python-apt, python3-apt [15:17] ruby [15:18] python-future [15:23] those are the deps for KA that I can see right now [15:23] we should probably also build and install kubuntu-dev-tools [15:23] (bzr repo at lp:kubuntu-dev-tools) [15:24] mostly obsolete, but I'm still using at least 2 scripts from there [15:24] so we also need bazaar [15:24] bzr-builddeb should pull that in [15:25] yup [15:27] we'll also need a small pbuilder guide. Question is whether we should just recommend pbuilder-dist (which is simple to use but has limited flexibility) or use a custom pbuilderrc which would allow flexible usage like explained on https://wiki.kubuntu.org/Kubuntu/Ninjas/BuildEnvironment?action=recall&rev=14 [15:28] I haven't read the ubuntu pbuilder guide in a long time [15:29] the pbuilder-hooks are a requirement really, you want to use those [15:31] * yofel off to make dinner, bbiab [15:35] image is built with the dependencies [15:35] working on adding a workspace now [16:28] what's apt-utils? [16:31] nothing I particulary use [16:31] oh, also add apt-transport-https to the dep list [16:34] ovidiu-florin: did you get yourself a pbuild environment [16:35] clivejo: I'm builting a Docker image for that [16:36] oh [16:36] can you make a pbuild one too [16:37] if we get you up and running in pbuild, then look into docker [16:37] the point would be to have pbuilder running inside docker [16:37] someone is working on 5.5.2 ? :) [16:38] http://qa.kubuntu.co.uk/ppa-status/plasma/build_status_5.5.2_xenial.html [16:39] I wanted to show ovidiu-florin how to add in missing files for kwallet-pam [16:41] can I do something while the Docker image is beiing built? [16:46] http://linuxfonts.narod.ru/why.linux.is.not.ready.for.the.desktop.current.html [16:55] ovidiu-florin: I dont know anything about docker, so cant help you with that [16:56] you missunderstood my question [16:56] I did? [16:58] yes [16:58] I asked what can I do, regardles of what's happening with docker [16:58] oh create a pbuild [16:59] for xenial [16:59] and add the staging ppa's [17:01] and install the kubuntu pbuilder hooks [17:02] https://code.launchpad.net/~kubuntu-packagers/pbuilder/pbuilder-hooks [17:04] how do I create a pbuild? [17:04] yofel: could that be moved to git too? [17:05] ovidiu-florin: your challenge this morning was to see if you could create one using the ubuntu howto page [17:05] and if you had problems to rewrite the docs [17:05] I hit a few problems following those instructions [17:05] could be, I didn't bother with that so far [17:05] [12:01:05] lordievader: yeah, but bit flakey on setting up different arch and distributions [17:06] until there's some concrete advantage, I don't move stuff [17:06] I took from here that it's different what we need from the Ubuntu docs [17:06] that's a clone-once-and-forget thing anyway usually [17:06] * clivejo dislikes bzr [17:06] yofel: advantage is git > bzr [17:07] ovidiu-florin: the guide yofel pointed out is better IMO [17:07] and the downside is that all current users need to remember to switch their checkouts and that people need to know that the location changed [17:08] shame its in CategoryKubuntuRubbish [17:08] does anyone know who maintains the wiki.kubuntu.org server? [17:09] canonical [17:09] oh [17:09] wiki.kubuntu.org is an alias for wiki.ubuntu.com [17:09] with a different default theme [17:09] is the theme on git or somewhere? [17:10] in bzr somewhere I believe, but I don't remember where [17:10] Riddell: do you remember? ^ [17:12] yofel: https://code.launchpad.net/~kubuntu-website/kubuntu-website/kubuntu-wikitheme [17:12] ? [17:12] that looks right actually [17:12] no updates in a while [17:13] we once tried to update the theme a bit, but nobody ever actually implemented the design that sheytan came up with [17:14] its moinmoin? [17:14] yep [17:15] * clivejo cowers [17:16] yofel: the https://wiki.kubuntu.org/Kubuntu/Ninjas/BuildEnvironment?action=recall&rev=14 guide gives a .pbuilderrc that only covers up to trusty [17:17] ovidiu-florin: well, it was never updated since the page ended up in the trash bin [17:17] the debian suites are also old [17:18] although we could just remove the safety check for the suites [17:18] so.... [17:18] less maintenance [17:18] I shouldn't add that rc anywhay? [17:19] just use the default one? [17:19] what default one? [17:19] aaah, the suites are used for the mirror detection to keep ubuntu and debian apart [17:19] default == empty [17:20] one in /usr/share/pbuilder/pbuilderrc [17:21] I believed that's always used [17:21] your own one just overrides the default values [17:21] in the end, those rc files are just shell scripts [17:22] ovidiu-florin: add it anyway, I'll send you a patch which removes the suite handling later [17:22] I'll add it when I'll get the patch, till then I'll use the default [17:23] ack, that's enough to build plain xenial chroots anyway [17:23] I think Jon or yofel pastebin mine [17:23] ? [17:23] Im trying to remember when I setup mine [17:23] That rc file in the wiki is derived from mine, yes. And mine is derived from the one harald wrote years ago [17:25] mind sharing it yofel? [17:26] it's on the wiki page? https://wiki.kubuntu.org/Kubuntu/Ninjas/BuildEnvironment?action=AttachFile&do=view&target=ninjas-pbuilderrc.txt [17:26] that's the "clean" version of mine [17:26] I mean your current one [17:26] that's a mess :P [17:26] LOL [17:26] it must work though! [17:26] lots of commented stuff, to make that useful for other people I would need to clean things up and document it [17:27] well, it does, but it supports chroots for ubuntu, debian and tanglu at the same time and stuff [17:28] there are useful things in there like eatmydata, pigz and parallel support [17:28] but lots of stuff newcomers will definitely not need [17:28] is there any problem if I run pbuilder as root? [17:28] on a VM? [17:29] in a VM not, in docker, no idea [17:29] yofel: is it possible to make a rc file to create pbuilder environments with PPAs auto enabled? [17:29] yes, by listing them in OTHERMIRROR [17:30] do you have to edit that for each session? [17:30] you need to be careful though as LP doesn't initialize the package lists for a release until you upload something [17:30] I made one wily-kci and wily-staging [17:30] so until that happens, apt will fail on that PPA [17:30] but I forget how I did it [17:32] the -suffix is added with pro=kci with my rc [17:32] can we have 5.5.2 finished today ? [17:32] no [17:32] LOL [17:32] meh, now that I'm talking about it, let me write a clean rc [17:33] well, no == very very unlikely, until someone does a fixing marathon starting now [17:33] soee_: forward your patches to me and Ill push them and upload to LP [17:34] clivejo: i'm waiting for docs to get started with packaging :) [17:34] LOL [17:34] well ovidiu-florin has started those [17:35] follow along now if you are interested [17:35] I: Extracting zlib1g... [17:35] W: Failure trying to run: chroot /var/cache/pbuilder/build/21/. mount -t proc proc /proc [17:35] W: See /var/cache/pbuilder/build/21/./debootstrap/debootstrap.log for details [17:35] E: debootstrap failed [17:35] W: Aborting with an error [17:35] I: cleaning the build env [17:35] I: removing directory /var/cache/pbuilder/build//21 and its subdirectories [17:35] setup a pbuilder environment is first step in building and testing packages yourself [17:35] I ran this: dist=trusty ARCH=i386 pbuilder create [17:36] why trusty? [17:36] sounds like sudo is missing? [17:36] how am I supposed to check those logs? [17:36] and why i386 [17:36] because https://wiki.kubuntu.org/Kubuntu/Ninjas/BuildEnvironment?action=recall&rev=14 says so [17:36] LOL [17:36] dont take it so literally! [17:36] well, that's supposed to work [17:37] I executed that as root [17:37] in docker (same as a VM, stop being scared of docker) [17:37] try sudo dist=xenial pbuilder create [17:37] I am ROOT! I don't neet sudo [17:38] just do it in a regular konsole? [17:38] I'm doing it in Konsole [17:38] I dont undertstand why you want a container inside a container, inside a container [17:38] but I don't think the TERM wrapper has anything to do woth this [17:38] hm, then the mount might be failing [17:39] hmmm.... [17:39] anyways, diner time and I could eat a horse! [17:39] chat later [17:40] * tsimonq2 hands clivejo a horse [17:40] :D [17:42] :)) [17:42] LOL [17:42] yofel: it seems the chroot fails again [17:42] or mount [17:42] dang [17:42] try a plain debootstrap run, that should leave the log [17:42] pbuilder deletes the tmpdir on failure [17:43] yofel: can you give me a command please? [17:44] debootstrap xenial /tmp/chroot [17:46] https://www.youtube.com/watch?v=G9m8O-7J5NM [18:07] yofel: mount: proc is write-protected, mounting read-only [18:07] mount: cannot mount proc read-only [18:07] this is what I get in Docker [18:07] anyhow [18:08] yeah, well, that won't work [18:08] in the host, directly on my system it finished ok [18:08] what now [18:08] ? [18:08] pbuilder hooks [18:09] no idea, I'm not familiar with docker, in LXC I know that I have to run unconfined containers. Maybe I can look into that later [18:09] here's the pbuilderrc btw: http://paste.ubuntu.com/14286057/ [18:09] forget docker [18:10] tell me what needs to be done regularly [18:10] and I'll figure out the docker part [18:11] for the hooks see the rc I pasted. You need to check out the hooks, then point HOOKDIR to the location [18:11] pbuilder will execute any hooks that are +x [18:14] now run pbuilder create again? [18:16] yes [18:16] ERROR: ld.so: object '/usr/lib/x86_64-linux-gnu/libeatmydata.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored. [18:16] add eatmydata and pigz to the deps though [18:16] as the rc says in line 1 [18:17] are those packages that need installing? [18:18] yes [18:22] interesting names [18:23] well, eatmydata makes sync() and fsync() noops, hence eatmydata if your system crashes. pigz is a parallel version of gzip [18:36] ERROR: ld.so: object '/usr/lib/x86_64-linux-gnu/libeatmydata.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored. [18:36] I still get this [18:37] but only when "I: Obtaining the cached apt archive contents" [18:37] it will stop once eatmydata gets installed in the chroot, which happens close to the end [18:37] ... [18:37] I'm open for suggestions how to improve that [18:38] we can ofc. disable eatmydata [18:38] hm... maybe one could create symlinks for the relevant commands instead of using LD_PRELOAD [18:39] no, that'll fail completely until eatmydata is installed :/ [18:41] I don't know what pbuilder does exactly yet [18:42] it's a script set that creates temporary chroots, installs the build-deps of a package, then builds it [18:42] it's for building packages in clean environments [18:43] similiar how the buildds on Launchpad do the package builds [18:43] ok [18:43] that way you can test whether your package will build on LP, or not [18:43] it's finished [18:43] what now? [18:43] clivejo: ? [18:55] yofel: ? [19:33] where have you got to? [19:42] clivejo: $ sudo -E dist=xenial pbuilder create finished [19:43] ok [19:43] use "pbuilder-dist xenial login --save-after-login" to test it [19:44] it will extract the file and setup a nice clean xenial environment [19:45] do an apt-get update while you are in there [19:45] control and D exits it and saves the changes back to the tarball [19:46] you don't usually want to pass --save-after-login unless you intentionally want to edit something in the chroot [19:46] and s/pbuilder-dist/pbuilder/ [19:47] yeah, this is just a one off to test it and check its package list is updated [19:47] oups [19:48] yofel would you do a apt-get upgrade too? [19:49] no, pbuilder update does that [19:49] would it speed it up a bit? [19:49] that does update + dist-upgrade + clean + autoremove I believe [19:49] from having to update every time? [19:50] well, we have a pbuilder hook for updating every time [19:50] but that doesn't persist the update, so pbuilder update is something you want to run every now and then [19:51] how does pbuilder update work? [19:51] can that be done from outside? [19:51] as I just said, I believe it runs apt-get update + dist-upgrade + clean + autoremove. But I didn't actually check that [19:51] that has to be done from the outside [19:51] update is just another command like build or login [19:52] do you pass the environment name too? [19:52] pbuilder update xenial-amd64? [19:53] and it saves it all back to the tarball? [19:53] well, if you're on xenial amd64 then just "pbuilder update" will do the job with my rc file, otherwise it would be "dist=xenial ARCH=i386 pbuilder update" [19:53] and yes, it saves the changes after a successful upgrade [19:53] read the manual ^^ [19:53] I been doing it manually :P [19:54] the archive is in /var/cache/pbuilder/xenial-amd64.tgz [19:54] so pbuilder-dist xenial login --save-after-login failed [19:54] just run: pbuilder login [19:54] I had a mistake [19:54] its just pbuilder [19:55] $ sudo dist=xenial pbuilder login [19:56] ok, I'm in now [19:56] do I exit and do $ sudo dist=xenial pbuilder update ? [19:57] yes [19:57] well its brand new, it shouldnt need updating [19:57] but its good info to know [19:58] * clivejo is learning new stuff too [19:58] then, if you want to try it out, you can fetch some source package and pass the path to the .dsc file to pbuilder build. Just apt-get source pkg-kde-tools or so, that's small [19:59] where does apt-get source download? [20:00] yofel: I prefer to use nano and installed it manually in the environment, how would you do that? [20:00] current directory [20:00] tried it and saw [20:00] thanks [20:00] clivejo: set EDITOR to nano in the rc and add nano to the EXTRAPACKAGES [20:01] those are the 2 places that the rc has "vim" set [20:01] it only installs it when a hook is triggered? [20:01] no, by default [20:01] although you can add it to the shell hook instead if you want [20:02] I prefer to have it usable when I login too though [20:02] and depending on the actions different hooks get executed [20:02] I had it installed into the tarball in wily [20:02] again, see hook section in the manual [20:02] wasnt sure if that was a good or bad thing [20:03] as long as you're aware of the change, it's ok. Just don't install anything that has heavy deps [20:03] where does it build it? [20:03] as otherwise that'll defy the point of a "clean" environment [20:03] ovidiu-florin: /var/cache/pbuilder/build// [20:05] /var/cache/pbuilder/build/15184 is the only folder and it's empty [20:05] what did pbuilder do? [20:05] yofel: also can pbuilder be configured to use local apt cache? [20:05] it will wipe the directory once the build finishes [20:06] the build artifacts should be in /var/cache/pbuilder/xenial-amd64/result/ [20:06] install dependencies, run lintian and some hooks [20:06] clivejo: that's what my rc does [20:06] there's lots of settings, see pbuilderrc manpage [20:07] Im running xenial locally, but it always downloads new copies for pbuilder [20:07] yup [20:07] they are there [20:07]