[00:12] If I were to start trying to help with packaging, where on KCI would be the best place to look? senile? [00:57] hello [00:57] is anyone working on plasma 5.5.1 packages for kubuntu or aware of a ppa that has them? [08:52] Good morning. [10:06] frecel: no, we're not working on them yet. Yes, we are working in their direction (currently on frameworks), but we're very shorthanded currently [10:39] yofel: Suggestion: Since it seems that either you or sgclark seem to have to reply almost daily, perhaps load it into the channel topic? [10:40] might as well add that back, we did have that in the past === yofel changed the topic of #kubuntu-devel to: Kubuntu - Friendly computing | Plasma 5.5.1: TODO Apps 15.08.3: W/WIP X/TODO FW 5.17 W/TODO X/WIP | https://trello.com/kubuntu | http://qa.kubuntu.co.uk/ | milestoned bugs: http://goo.gl/AOx7bx === yofel changed the topic of #kubuntu-devel to: Kubuntu - Friendly computing | Plasma 5.5.1: TODO Apps 15.08.3: W/WIP X/TODO FW 5.17: W/TODO X/WIP | https://trello.com/kubuntu | http://qa.kubuntu.co.uk/ | milestoned bugs: http://goo.gl/AOx7bx [10:42] a bit cryptic, but those people that actually bother to read the topic should understand taht [10:43] actually === yofel changed the topic of #kubuntu-devel to: Kubuntu - Friendly computing | Plasma 5.5.1: TODO Apps 15.08.3: W/WIP X/TODO FW 5.17: W/TODO X/WIP | https://trello.com/kubuntu | http://qa.kubuntu.co.uk/ | milestoned bugs: http://goo.gl/AOx7bx | No, plasma 5.5 isn't packaged yet [10:43] peace [10:45] TY. Mind if I try to add the last bit to the support channel? [10:46] Sorry, I guess I do not have the permissions anyway. [11:00] I would rather not have that over there, even if it means answering a couple more questions. Additional info in the already long topic there is really just for emergencies [11:17] ok, so finally took a look at those app "backports" and the PPA had a dep on the INDI ppa which it shouldn't have. People really need to stop adding random PPA deps [11:21] uh... staging-frameworks didn't depend on -proposed [11:40] Hiyas all [18:07] yofel: hi since I have been absent for a while: where do you need help (besides parallelinzing git-clone-all)? [18:08] * parallelizing [18:18] I was looking at the merging failures and it looks like it would just take someone with git access to address a merge conflict: http://kci.pangea.pub/job/merger_breeze-icons/ [18:18] I was looking into how to help, but I don't know the git information to look into fixing the merge conflicts. [18:47] vertago1: git access is restricted and requires membership on the qt-kde team on alioth (debian). In the beginning we recommend sending patches for actual packaging issues (or pointing us to a fixed git branch somewhere) or doing coop packaging with someone or tackling small package updates [18:48] let me think a bit about how a good way to start helping with packaging would be... [18:49] santa_: hard to say, didn't you want to implement your workflow? I'm currently trying to meet that coming from the other direction by reworking and splitting the current scripts a bit so we can get work done. [18:52] santa_: I pretty much gave up using your workflow after making git-clone-all work for me took too long. I work in temporary directories, so I added -t to the script, but then it started doing nothing at all because you are relying on a fixed path in getFtpVersionMap(), which will fail depending on when the function is called [18:52] after I saw that I didn't feel like digging more into it [18:53] yofel: what was that -t suposed to do? [18:53] same thing as -t does for staging-upload [18:53] make a tmpdir and do all the work in there [18:53] so it can later be easily deleted [18:54] well the idea of automation-ng is using clones which you are suposed to keep [18:55] if your intention is to clone all the repositories each time a new upstream release arrives that is going to take a long time [18:55] doesn't work for me. I know myself, and if I have repo clones lying around, I *will* use them for random stuff. And I need a clean environment for the automation stuff [18:56] sure, that's why -t is supposed to be optional [18:56] there's nothing wrong with the script supporting both persistent and volatile workflows [18:57] well, I fail to see whats the problem [18:57] if you don't trust your previous clones you can clone them again [18:58] or if you screwed up and you want to start fresh or whatever [18:58] well, for starters, the git-clone-all I tried, cloned all repos inside of the kubuntu-automation checkout, without subfolder. Sorry, but that's a no-go for me [18:59] ok, I can go and make a symlink, and copy all the config stuff it needs to the temporary location, but the script should do that really. [19:00] And why would a *library* function rely on a specific execution location? If it needs the path, that's supposed to be a function parameter, not an in-function call [19:00] wat [19:01] def getFtpVersionMap(releaseType): [19:01] [snip] [19:01] cwd = os.path.dirname(os.path.realpath(__file__)) [19:01] yofel: any tips on sorting out the packing issues from the kci / git repo issues? [19:01] well, guess what, cwd depends on where you run it... [19:01] or where you are when that function is called [19:06] yofel: that cwd depends on where lib/utils.py is located [19:06] not if you os.chdir() before you run the function [19:06] which is what -t does [19:07] I mean, you can rework it to work even with that cwd call, but why would you rely on that in the first place? [19:08] hmm before anything, could you clarify exactly what are you trying to do and the expected behaviour? [19:09] I mean [19:09] $ git-clone-all -r frameworks -t [19:09] ↑ this? [19:09] something else? [19:10] ./git-clone-all -r frameworks -t ./foobar/ [19:10] after that all repos should be inside ./foobar/ [19:10] which means that git has to be run in foobar/, which means that cwd is in foobar [19:11] oh, ok, I don't think that is difficult to achieve [19:12] probably not, but I hit so many env assumtions in the script that it felt like I'm wasting me time [19:12] give me some minutes to code and think about what you have said so we can reach an "agreement" here [19:13] I don't think there isn't so many env assumptions but let me have a look [19:13] I'm actually happy that you're putting code into lib functions, but I want to eventually have those testable, and the current implementation is rather bad for that [19:16] vertago1: not where it's just a merge conflict. It's better if you look for build failures, missing files, lintian warnings etc. For those you can easily send me a patch that I can apply [19:17] git diff would be idea ofc. The repositories are on http://anonscm.debian.org/cgit/pkg-kde/ and the CI builds from the kubuntu_unstable / kubuntu_stable branches [19:17] yofel: ok. I have seen you have implemented the -t option, it works as expected here [19:18] I think it actually worked for frameworks or so, but did nothing for applications. Something weird like that [19:18] been a while since I tried it [19:18] has anyone thought about having KCI guess what the problem is to apply tags to build failures? [19:19] yofel: also I'm inclined to think you are wrong about this: [19:19] [20:06] yofel: that cwd depends on where lib/utils.py is located [19:19] [20:06] not if you os.chdir() before you run the function [19:19] vertago1: what's up with breeze-icons? I was packaging that today [19:19] possibly, I remember there being something wrong and thought that was it [19:19] I think it works regardless of what you do with os.chdir [19:21] yofel: ok, so would you give the thing another chance, so we can figure out the actual issues? [19:21] let me try [19:21] Riddell: I am fairly new to you all's packing workflow, but the merger script for breeze icons is complaining of a merge conflict [19:21] we could try it for plasma 5.5.1 or so [19:21] vertago1: url? [19:21] Riddell: http://kci.pangea.pub/job/merger_breeze-icons/ [19:22] is there any easy way to scrape the console outputs of the packages so I could look into writing a script to tag them? [19:23] you'll want to talk to sitter about that [19:23] actually I should wait on that. I am still trying to figure out which branch would be best to look for problems in. Senile? [19:23] vertago1: thanks, fixed [19:24] Riddell: thanks [19:24] vertago1: at some point a manual fix it needed, I'm not sure automating a tag on problems to label them would be worth any time it saved since manual look would still be needed [19:25] Riddel: yeah, I think it would be only useful if people were good at fixing particular kinds of problems and it was easier for them to find those problems by looking for a tag. [19:27] I am seeing this error a lot "Upload was likely rejected, we have been waiting for well over 30 minutes!" [19:28] It doesn't appear to be accurate because the timestamps don't reflect a 30minute wait [19:29] yofel: is it possible that you got something like this: https://paste.kde.org/pnkresnlw ? [19:29] that too, I forgot the mkdir call [19:30] but the script does seem to work now [19:30] yeah, was about to say that [19:33] does anyone else find that when they click on the taskbar to switch to another prgramme, that the cursor picks up a shortcut instead? [19:33] yes [19:33] its really getting on my nerves now [19:33] and sometimes it crashes plasma [19:33] or at least it used to [19:33] I havent crashed plasma in months [19:33] yeah I think that part might be fixed [19:33] I don't understand why it is picking up an icon though [19:34] but cant understand why is keeps picking up the shortcut [19:34] and it keeps following me until I click on the desktop and create the icon [19:34] I have to keep a section of desktop clear as an icon dump! [19:35] clivejo do you think an event might be getting lost so it thinks it is a click and drag instead of a single click? [19:35] well I thought that it was my wireless mouse [19:35] but I have a USB wired mouse and its doing the same [19:35] I have a logitech g9x and have the issue [19:35] my wireless mouse is logitech [19:36] but this wired one is a M$ one [19:36] a Basic Optical Mouse version 1.0 [19:36] 1.0A [19:37] I've seen that, but I can usually get rid by dropping the icon onto the app it came from [19:37] that is what I have done [19:37] vertago1: re tags , you mean like http://kci.pangea.pub/job/wily_unstable_purpose/74/parsed_console/ [19:37] yofel: its just a bloody pain having to dump the icon somewhere [19:37] agreed [19:38] when you're busy trying to do something [19:38] has anyone reported it? [19:39] shadeslayer: that is several steps toward what I would want to do. The next steps would involve filtering by errors or warnings. That would let you exclude all the build errors do to git [19:39] I dont know if its my workflow, but the majority of the icons are firefox and dolphin [19:39] Hm, might be possible [19:39] firefox the vast majority [19:39] clivejo: I wonder if I could use wireshark's USB monitoring to troubleshoot it [19:39] Iirc Jenkins allows Job tagging [19:40] vertago1: if you know how, please do! Id love to see it resolved [19:40] clivejo I need to be able to trigger it though [19:40] if 3 of us are experiencing it, must be an issue somewhere [19:40] clivejo: it seems to be sporadic [19:41] <---- Xenial up-to-date as of yesterday morning [19:41] happens in wily for me [19:41] the quicker, or more of a hurry Im in the worse it is [19:42] clivejo, it may be a click and drag threshold that needs to be adjusted [19:43] wonder should I mention it in plasma [19:43] the drag start distance default seems to be 4pixels [19:43] is it a kubuntu issue or all KDE distros [19:44] clivejo, I would try upping the drag start distance to 8 pixels or more and see if it makes it not as bad [19:44] how do I do that? [19:44] if you search mouse on the application launcher it is under the advanced tab [19:44] called "drag start distance" [19:45] ah yes [19:45] I use a high resolution: 1920x1200 so 4 pixels is fairly small [19:45] upped to 8 [19:45] will try that for a while [19:45] you may need it even higher [19:50] what happened 5-6days ago to throw senial packages off? [19:50] yofel, ok I found what I think it was wrong when you tried it [19:50] back to over 300 broken [19:51] clivejo: branch switching for stable did that I guess [19:52] yofel: maybe something like this https://paste.kde.org/pm7zbweh6 ? [19:52] don't think so, I think it literally did nothing (package list update from ftp failed?) [19:53] yofel: any update on how to fix networkmanager-qt ? [19:53] update? that still is waiting for scarlett to update n-m [19:53] Applications 15.12 released :) === yofel changed the topic of #kubuntu-devel to: Kubuntu - Friendly computing | Plasma 5.5.1: TODO Apps 15.08.3: W/WIP X/TODO FW 5.17: W/TODO X/WIP | https://trello.com/kubuntu | http://qa.kubuntu.co.uk/ | No, plasma 5.5 isn't packaged yet [19:54] diff: - milestone link. That's better linked from qa [19:54] soee_: when will you have the packaged and ready for testing :P [19:55] :D [19:55] yofel: in any case I think I have a couple of small changes for git-clone-all [19:55] here i relay on the devs :_-) === yofel changed the topic of #kubuntu-devel to: Kubuntu - Friendly computing | Plasma 5.5.1: TODO Apps 15.08.3: W/WIP 15.12.0: TODO FW 5.17: W/TODO X/WIP | https://trello.com/kubuntu | http://qa.kubuntu.co.uk/ | No, plasma 5.5 isn't packaged yet [19:56] 15.12 added [19:56] topic says that: TODO Apps 15.08.3, should 15.12 be done not the old one ? [19:56] btw this line [19:56] workdir = args.workdir if args.workdir else cwd [19:56] now it does ;) [19:56] soee_: you do know we are subscribed to the release mailing list and know this already :) [19:57] disappeared misteriously after the merge [19:57] clivejo: i;m like a smart bot that remainds it anyway :D [19:57] o.O [19:57] like a facebook poke [19:58] now someone has to write a depression bot that constantly reminds us of all the things we have to do [19:59] you can put writing that bot on the list of things the bot should remind you to do [19:59] :} [19:59] ahahaha [19:59] oh kolab will be at FOSDEM [20:02] * yofel goes back to making ppa-build-status write out json [20:02] * clivejo wishes he knew what was broken and how to fix it [20:03] the script is currently both a) a data processor, b) a print-out-html-string-because-that's-the-cool-way thingy because that was easy to do and because nobody cares and because AAAAARGh [20:05] like parley, why does the AMD64 build ok, but 386 wont install the deps?!? [20:05] where? [20:05] clivejo, that sounds like there may be a naming difference between amd64 and i386 [20:06] vertago1: https://launchpadlibrarian.net/230041926/buildlog_ubuntu-xenial-i386.parley_4%3A15.08.2%2Bgit20151215.0457%2B16.04-0_BUILDING.txt.gz [20:06] probably more like other packages not building on i386 as well [20:06] hmm [20:06] kio-dev but it is not going to be installed [20:07] * clivejo kicks KCI [20:07] why can't it fetch teh gpg key? [20:07] yeah, you can't debug that without aptitude, apt with debug output, or dose output [20:07] good question, but this is launchpad internal, so it doesn't really need to [20:08] yofel: pushed the simple fixes to https://github.com/jmsantamaria/kubuntu-automation-work [20:08] this way it will work better [20:08] btw I shouldn't have called that variable cwd, since it's confusing [20:09] santa_ scriptdir would probably make sense [20:09] or installdir or something like that [20:11] merged. Into master btw. as we should really start using them (And I kind of messed up while juggling branches) [20:12] ok, I will try to be here as much as possible to assist with issues [20:12] #packages we know use a different version than the rest of the release [20:12] differentVersion = ["baloo-kf5", "kfilemetadata-kf5", "kdepimlibs", "kdepim", "kdepim-runtime", "kde4libs"] [20:13] wow, even ppa-build-status has hardcoded configs /o\ [20:24] clifejo: so that is the kubuntu_xenail_archive branch here http://anonscm.debian.org/cgit/pkg-kde/applications/parley.git/refs/heads? [20:25] the KCI is using the unstable and stable branches [20:25] ok [20:25] is that parley the stable branch? [20:27] both stable and unstable are failing [20:27] due to the 386 build [20:27] I attempted to fix it and got the AMD64 to build locally and then on KCI [20:28] but the 386 keeps FTBFS [20:28] I have no idea why [20:28] clivejo are all the dependencies available? [20:28] I am looking at the list [20:28] cmake, [20:28] debhelper (>= 9), [20:28] extra-cmake-modules, [20:28] imagemagick, [20:28] kdoctools-dev, [20:28] kio-dev, [20:28] as far as I can see [20:28] kross-dev, [20:28] libkeduvocdocument-dev, [20:28] libkf5config-dev, [20:28] libkf5coreaddons-dev, [20:28] libkf5crash-dev, [20:29] libkf5i18n-dev, [20:29] libkf5kcmutils-dev, [20:29] libkf5khtml-dev, [20:29] libkf5newstuff-dev, [20:29] libkf5sonnet-dev, [20:29] libqt5svg5-dev, [20:29] libxml2-dev, [20:29] libxslt-dev, [20:29] pkg-config, [20:29] pkg-kde-tools (>= 0.12), [20:29] qtmultimedia5-dev, [20:29] qtscript5-dev [20:29] vertago1: we prefer to use a paste bin :) [20:29] yeah I didn't realize it was going to do that [20:29] https://paste.kde.org/ [20:29] or the likes [20:30] quassel keeps sending me to file : ///home..../kioexec/krun/ when I click URLs [20:30] I did attempt to setup a 386 pbuild but I ran into problems [20:30] how do you sent one up? [20:31] I can setup a i386 container [20:31] https://wiki.ubuntu.com/PbuilderHowto [20:31] * clivejo doesnt like 386 [20:32] have you use lxc at all? [20:32] they arn't that bad. I set one up because of a regression in samba [20:32] clivejo: what problem did you run into regarding i386 pbuilder? [20:33] * clivejo has a slow internet connection and had to upload and downland calligra source on numurious occassions [20:33] yofel: getting the packages [20:33] o.O that should work the same as always when in an i386 chroot [20:35] The following packages couldn't be cloned: [20:35] spectacle [20:35] ↑ what's that? [20:37] pbuilder create --architecture i386? [20:37] seems to be some new app in 15.12 [20:37] looks like it wants sudo [20:37] I am going to see if I can run it in userland [20:38] * yofel has a very custom pbuilder setup (not userland) [20:38] so can't really help with the defaults [20:38] * clivejo wonders how yofel has pbuilder set up [20:38] it doesn't work in userland because of debbootstrap [20:39] I got it to start fetching stuff [20:39] mine fetched lots of stuff, but then stopped [20:39] that ppa seems to corrupt things [20:39] enjoy my pbuilderrc paste.ubuntu.com/14056289/ - lots of stuff you don't need, but maybe you'll find something interesting [20:39] the problem is I am on wiley so I don't know if it will be a good test [20:40] hm, I need to update the debian codenames ^^ [20:40] vertago1: you can create pbuilder instances for xenial too [20:41] BTW senial is sitters codename for xenial [20:41] sorry senile [20:42] is that how it is pronounced anyway? [20:42] he has me typing senial by mistake [20:42] zenial [20:42] only if you have a certain accent ;) [20:42] hahaha [20:42] BlueKaj that is what I thought [20:44] grrrr stupid symbols [20:46] what is purpose anyway? [20:46] Ive packaged it and have no idea what its for! [20:47] Description: library for abstractions to get the developer's purposes fulfilled [20:47] uhuuuuh... [20:47] sounds very meta [20:47] * clivejo feels enlightened [20:48] yofel: its part of framesworks now? [20:48] looks like it [20:48] maybe it has a purpose there [20:48] why doesnt it have a frameworks version number? [20:49] hmm [20:49] it looks like my system config is incompatible with pbuilder as is [20:50] oh, it's not in 5.17 [20:50] #libnamingconfusion [20:50] I am going to have to get it to download the packages to the same physical device I am making the base configs on [20:51] if you're getting ln errors, you can disable the aptcache and use bindmounts or so [20:51] it is trying to hardlink across two hard drives [20:52] strange, its under frameworks in debian git - http://anonscm.debian.org/cgit/pkg-kde/frameworks/purpose.git/ [20:52] right, I get that too when building in tmpfs, so I'm using this when I do: [20:52] BINDMOUNTS="/var/cache/apt/archives/ /run/" [20:52] APTCACHE="" [20:52] I have a ssd for / and a platter drive for /home [20:53] I am just going to let it use /var for the base [20:53] I may need to move it later though [20:59] https://github.com/jmsantamaria/kubuntu-automation-work/commits/master [20:59] ↑ yofel stuff needed to bump the build depends for the last versions [21:02] I really don't see the point of that list you know [21:02] but thanks for the update [21:02] the json with all the -dev packages? [21:03] yep [21:03] or well, the package list has a potential use, but the versions? [21:03] they have the epoch or not [21:04] so no need to hardcode which packages are epoch'ed [21:04] clivejo so after getting a i386 pbuilder setup where do I get the .dsc to do the build? [21:05] note that the list is generated automatically with dev-package-names-list [21:05] also note that this script could be glued with the bump-* script in the future [21:05] aaaaah, that script actually does look up the real epoch [21:05] ok [21:06] yeah, parses the changelogs [21:08] vertago1: debuild -S [21:08] clivejo, in what context? [21:09] to get the .dsc to build in pbuilder [21:10] I need the tar files [21:12] should I enter the pbuild environment and then use apt-source? [21:12] I mean apt-get source [21:14] well I grab the debian git branch and then use uscan to grab the source [21:14] it is complaining that I don't have a sources.list [21:14] that's an option. Other one is to look up the URL on the web ui, or to use pull-ppa-source from lp:kubuntu-dev-tools, or to just rebuild from git as clive said [21:15] but KCI is grabbing the source directly from git [21:15] I already have the source from git and I checkout out the xenail-unstable branch [21:15] so in those cases I download the source from KCI PPA's [21:16] then you need to debuild -S to build the source [21:16] and instead of uploading to your PPA, you build it in pbuilder [21:17] for example use pbuilder-dist xenial build ../*dsc [21:17] that builds it in a nice clean xenial install [21:17] on my machine [21:19] yofel: do you know what top level package creates libkf5kcmutils-dev ? [21:19] it is complaing about no .orig.tar.xz even though it is there [21:19] clivejo: apt-cache showsrc libkf5kcmutils-dev [21:19] it looks like the version number is wrong [21:20] kscreenlocker (exit status = 1) [21:20] discover (exit status = 1) [21:20] breeze-gtk (exit status = 1) [21:21] check debian/changelog and make sure the versions are the same [21:21] ↑ this packages from plasma doesn't have a kubuntu_xenial_archive branch [21:21] how do you keep uscan from downloading newer versions? [21:21] they're new [21:22] could you create the branches then so I can continue to test the thing? [21:22] (no hurry) [21:25] I must have the wrong download url for uscan it says no matching hrefs for 15.08.2 [21:26] no, that's uscan not properly fetching all versions it could find. [21:26] I believe there's an uscan bug report for that [21:27] looks like I will have to do it manually [21:30] ls [21:33] hmm my build failed but for a different reason [21:34] actually when I looked at it more closely it is the same error, but my base probably has less installed by default [21:36] http://paste.ubuntu.com/14056655/ [21:36] yofel: https://launchpadlibrarian.net/230149652/buildlog_ubuntu-xenial-i386.kdeclarative_5.17.0%2Bgit20151216.0354%2B16.04-0_BUILDING.txt.gz says libkf5declarative-dev_5.17.0+git20151216.0354+16.04-0_i386.deb is being built ok [21:36] okaaaay..? [21:37] yet sbuild-build-depends-kcmutils-dummy : Depends: libkf5declarative-dev (>= 5.16.0~) but it is not going to be installed [21:37] why? [21:37] apt saying that doesn't mean that package is the problem [21:37] it is the package that apt fails on, due to dep issues with other packages [21:38] as I said, you need the output from aptitude, or apt with -o debug::pkgproblemresolver=true, or some kind of dose output to debug this [21:38] the apt output in the buildlog is next to useless [21:39] it only seems to be an issue in 386 [21:39] yofel is there a way to get apt to include that option inside pbuilder? [21:39] you can put it into the chroot's apt.conf I gues [21:39] s [21:40] how do you change the base and save updates? [21:40] nvm [21:40] I will just manually edit the .tgz [21:40] pbuilder login --save-after-login [21:40] that is easier [21:41] just make sure your last command exist with 0 [21:41] otherwise it won't save [21:42] python 2's datetime class has no easy way to generate a unix timestamp, seriously? [21:42] first time that I see something useful in 3 [21:44] yofel are you talking about an epoch timestamp? I am pretty sure you can get that in python 2 [21:45] I'm properly bllind, but I see nothing on https://docs.python.org/2/library/datetime.html [21:45] I'll just port the script to py3. Needs to be done anyway [21:47] yofel there is no obvious function, but it looks like most people just use .strftime("%s") [21:47] which is ugly because you have to parse a format string [21:47] yofel: I used sudo DIST=xenial ARCH=i386 pbuilder create does this overwrite my AMD64 environment? [21:48] clivejo I used pbuilder create --basetgz xenial_i386_base.tgz --architecture i386 --distribution xenial [21:48] not with my config if that's what you're trying... [21:48] my config is empty [21:49] minus the parallel build lines I copied from yofel's config [21:49] Im reviewing my 386 setup, trying to find out why its not working [21:51] but I only have one xenial-base.tgz [21:51] I think Ive overwritten my amd64 environment [21:51] clivejo I explicity name my base.tgz to keep from doing that [21:52] my setup will e.g. create a /var/cache/pbuilder/xenial-amd64.tgz [21:52] vertago1: thanks, I must do that in future [21:52] mine seems to put it in ~/pbuilder [21:52] right, depends on your config [21:53] which is what I want my /home is on a HDD and keeps writes off my SSD [21:54] this is the new error I get after adding pkgproblemresolver to the config: http://paste.ubuntu.com/14056915/ [21:54] it looks like my source urls are wrong [21:54] kdoctools-dev which is a virtual package and is not provided by any available package. [21:55] did you add the KCI PPA? [21:55] no [21:56] I will do that now [21:57] * clivejo waits on new pbuilder base to download [21:57] sucks being on a slow connection [21:59] vertago1: what are you trying to build? [21:59] parley on i386 [21:59] since it was broken [22:00] I am having trouble finding the exact ppa I should add [22:01]