[00:16] <clivejo> Im afraid that’s me done for the night!
 Night clivejo
[00:17] <clivejo> should be a few more fixes in the pipeline, but the KCI queue is full and god knows when it will get around to building them
[00:19] <clivejo> only 24 failing packages in yakkety :)
 Nicr
 *nice
[00:22] <clivejo> 00:21:09 make: *** Cannot allocate memory.  Stop.
[00:22] <clivejo> grrr
[00:22] <clivejo> makes me angry
[00:22] <clivejo> good night
[07:06] <soee> hiho
[07:25] <Mirv> I've filed some bugs to please release team a bit more (they didn't ask, but I thought they might) https://bugs.launchpad.net/bugs/+bugs?field.tag=kf524
[07:25] <Mirv> I left out marble and okteta that I probably fixed now with symbol updates (marble also accepted to get built now), and akonadi-search that I'm still retrying to see if it's only flaky test as it failed only on one arch
[07:26] <Mirv> no response from release team however even though infinity said to be looking at the override plea "later" (14h ago)
[07:26] <Mirv> so, waiting continues today
[07:41] <yofel> Mirv: thanks! Having a track list of the tests is useful
 o/
[09:25] <soee> someone is using Enpass ?
[09:30] <soee> uhm desktop app is GTK but at least the icon works and fits pretty nice systray
[09:44] <Mirv> we got the autopkgtest forces!
[09:45] <Mirv> I'm still waiting for unity8 QA however to fix its tests. after that it's about pondering with release team "why nothing happens", which is usually the case and update_output.txt is needed in addition to the excuses page.
[09:51] <Mirv> oh ok missed a single plasma-framework s390x issue. I will ask that once we know whether u8 landing makes that green or not (if not, I'll ask if it could be overridden too and investigated later)
[10:01] <BluesKaj> Howdy folks
[10:09] <tsimonq2> o/ BluesKaj 
[10:10] <BluesKaj> hey ts
[10:10] <tsimonq2> lol
[10:11] <BluesKaj> tsimonq2,^, it's early, still on my first coffee :-)
[10:12] <tsimonq2> BluesKaj: well are you in #ubuntu-community-team ? I thought it was from the joke I literally just started there :P
[10:12] <BluesKaj> no 
[10:13] <tsimonq2> HAHAHAHAHA
[10:14] <BluesKaj> guess I missed the humour 
[10:14] <tsimonq2> BluesKaj: I PMed you what was said so I don't spam the channel
[10:36] <soee> green <3
[10:37] <soee> https://www.youtube.com/watch?v=OzgY_S7rEoo
[10:49] <tsimonq2> that was a nice minute of my life... :P
 LOL
 Gonna have that stuck on replay in my head all day now
 Thanks soee
[11:25] <soee> :d
 Only 17 broken packages sitting on the wall
[11:26] <soee> how do they become brokne exactyly ?
 The current ones have been broken for a while
 Most are PIM related
 Upstream changes mostly
 Clifford meanwhile I'll have this garbage stuck in my head all day :P https://www.youtube.com/watch?v=mVHJ6OwTYWc
[11:31] <acheronuk> libkf5calendarsupport http://paste.ubuntu.com/22018296/
[11:49] <yofel> acheronuk: wrap those tests in xvfb-run
[11:51] <acheronuk> so.....?
[11:51] <acheronuk> override_dh_auto_test:
[11:51] <acheronuk>         xvfb-run dh_auto_test
[11:53] <acheronuk> yofel: and add xvfb to the build depends?
[11:53] <yofel> acheronuk: yes, and yes
[11:53] <acheronuk> great. thanks :)
[11:56] <soee> can someone confirm this ugly clear button for filter field: http://i.imgur.com/xn3gWXs.png ?
[11:57] <mamarley> soee: Nope, sorry, looks fine here.
[11:58] <soee> :<
[11:58] <ahoneybun> filter?
[11:58] <soee> search field
[11:58] <ahoneybun> can't read your language
[11:59] <soee> it is not about lang, just the darkest button on the image :D
[12:00] <ahoneybun> I see a pixel black button
[12:00] <soee> yup
[12:25] <soee> wee..  warranty was goof
[12:26] <soee> *good
[12:26] <soee> i will have my monitor chnaged ot new one :)
[12:49] <soee> www.youtube.com/watch?list=PL0pdzjvYW9RFM_RjJhUhOO0OH8uVoRn3J&v=EshNTl23liY
[13:08] <acheronuk> yofel: those tests still fail http://paste.ubuntu.com/22025809/
[13:09] <yofel> huh, why does that need glx...
[13:10] <acheronuk> seems an odd thing to want for that, yes
[13:12] <yofel> libkf5calendarsupport_16.04.3+p16.10+git20160803.1257.orig.tar.xz: 
[13:12] <yofel> huh? why isn't that called calendarsupport?
[13:14] <acheronuk> bbl
[13:29] <tsimonq2> bbl o/
[13:49] <acheronuk> ummm. so disable that test?
[13:50] <yofel> I fixed it, you need to set the screen by hand for GL (took that from an autopkgtest config)
[13:51] <acheronuk> ah. thanks
[13:56] <davmor2> Hey guys there will be a respin shortly for 14.04.5 will someone be available to help out testing it?
[14:01] <yofel> davmor2: maybe, what's the rough equivalent of 'shortly' in hours?
[14:02]  * yofel agrees with infinity that our job is breaking things most of the time :D
[14:02] <davmor2> yofel: About an hour I've been told but infinity can give a more accurate time
[14:02] <yofel> k, thanks
[14:07] <yofel> the yakkey fix page fits on one screen \o/
[14:13] <yofel> hm...........
[14:15] <yofel> let me merge the current state in kubuntu_stable. Those symbols are 16.12 material
[14:19] <acheronuk> that was my next question if I got it built. I tried in pbuilder with the tests disabled, and got all those missing!
[14:21]  * yofel is a bit lost about the symbols
[14:21] <yofel> having the build jobs stay broken is bad, but then we loose symbol tracking for the archive updates which we need :/
[14:22] <yofel> patching debhelper in the ci PPA would be an idea...
[14:22] <acheronuk> patching to do what exactly?
[14:22] <yofel> not fail the build on missing symbols
[14:23] <yofel> but the build fails because that really does require an so version change :(
[14:24] <yofel> debianabimanaging all failures would be the perfect solution. But that's an overkill amount of overhead :/
[14:25] <yofel> or we keep leaving the MISSING comments in there and just update the symbols
[14:25] <yofel> but then we need to extend our archive QA to actually detect that
[14:25] <yofel> which probably would mean adding more patches to pkg-kde-tools
[14:38] <yofel> huh, what did *that* build o.O
[14:38] <yofel> *why
[14:39] <acheronuk> marble
[14:39] <acheronuk> set(GENERIC_LIB_VERSION "0.24.80")
[14:39] <acheronuk> set(GENERIC_LIB_SOVERSION "25")
[14:39] <acheronuk> set for 16.08 branch
[14:40] <yofel> I would postpone marble and okteta until after we've done the release branching for 16.08
[14:40] <acheronuk> and those latest big changes were in the 16.08 branch as well as master, so are the ok to fix?
[14:42] <acheronuk> ok. won't touch them
[14:42] <yofel> without a stable job it's hard to say
[14:42] <yofel> really all changes? The diff between 16.08 and master is huge for marble
[14:43] <acheronuk> let me check again
[14:45] <acheronuk> ok, this one was in both: https://quickgit.kde.org/?p=marble.git&a=commit&h=6c5a0b395dd34457d107780b398fb1df5beb9950
[14:45] <acheronuk> which was the big one I got the other night, and then said stop!
[14:46] <yofel> acheronuk: I guess lets risk it for both, and remember to re-check once we upload 16.08
[14:47] <acheronuk> I'll have another look through both before I even think about making changes, and if I'm not sure I'll query
[14:49] <yofel> hm, we never did finish 16.04.3
[15:10] <soee> ALSA 1.1.2 Released
[15:12] <mamarley> Something trout something
[15:29] <acheronuk> yofel: if calendarsupport unstable is now merged to stable, are those symbols OK to fix now? or are you still pondering things and would prefer it left?
[15:30] <yofel> acheronuk: just fix it
[15:31] <acheronuk> okay
[15:31] <yofel> we'll probably have to cherry pick stuff from kubuntu_unstable anyway, so lets worry about that in a week
[15:34] <yofel> santa_: so agreed, pkg-kde-tools is probably the appropriate place for that. Now I wonder how I would detect that we're building for the CI..
[15:34] <yofel> having a patched pkg-kde-tools in the ci ppa all the time would be somewhat annoying :/
[15:34] <santa_> I have a source of inspiration for that
[15:34] <santa_> let me check...
[15:43] <ahoneybun> mm there goes tryin got build the telepathy morse plugin
[15:46] <santa_> yofel: I think I would go for a shell evironment variable. so the CI would build with this variable
[15:47] <yofel> hm, then I need to figure out how to pass that into docker... not sure how the env looks like right now
[15:48] <yofel> but I did consider that too
[15:48] <yofel> (as it would be the most straight-forward solution build-system wise)
[15:49] <santa_> shouldn't be adjusting the templates for the build slaves enough?
[15:50] <yofel> santa_: the actual binary builds happing on launchpad, not in jenkins
[15:51] <yofel> hm.....
[15:51] <santa_> oh
[15:51] <yofel> or the ci-tooling injects a file into the source before uploading it
[15:52] <santa_> what builds in launchpad you are talking about? the ppa builds or something else in the kubuntu's workflow I am not aware yet?
[15:53] <yofel> santa_: the CI builds. Jenkins generates the sources, uploads that to the kubuntu-ci/ PPAs, then continues its work once the builds are done
[15:54] <santa_> ah, ok
[15:56] <santa_> yofel: in case you go for "or the ci-tooling injects a file into the source before uploading itor the ci-tooling injects a file into the source before uploading it"(TM) I had an script to alter one packages debian/rules and pass -c0 to dpkg-gensymbols
[15:57] <santa_> it supported both packages with and without dhmk
[15:58] <yofel> santa_: hm, true, that then actually doesn't need any pkg-kde-tools modification at all. As long as people don't accidentally copy that change into git
[15:58] <santa_> but altering the source like that is a bit ugly
[15:58] <yofel> although, that can be detected and the CI build made to fail on that
[15:59] <yofel> right, but the only other way I can currently think of is checking whether sources.list contains 'kubuntu-ci', which is ugly :(
[15:59] <yofel> does sbuild export something useful..
[16:00] <santa_> well, looking at the bright side of altering the source this would allow you to select which packages you want to build with -c0 and which ones you don't, right?
[16:00] <yofel> it would at least allow the possibility of doing that
[16:03] <yofel> on second though, with that we can only disable the check for /unstable, as /stable really should throw errors
[16:04] <yofel> and the tooling already messes with the changelog, so adding this won't really hurt
[16:05] <yofel> oh fun, I found the reason why the post-publishing checks aren't running
[16:06] <yofel>     unless File.exist?('logs/i386.log')
[16:06] <yofel>       puts 'found no logs'
[16:06] <yofel>       exit 0
[16:06] <yofel> we don't build i386 anymore ^^
[16:07] <santa_> hmm, what happens with i386 finally?
[16:08] <yofel> santa_: the logs? That's used for the lintian and symbol-addition checks
[16:09] <yofel> it also has a rather hacky qml dependency checker. Need to see if harald improved that in neon
[16:10] <santa_> yofel: no I mean I remember I read something about dropping i386 suport or something like that
[16:10] <santa_> but I don't remember where
[16:10] <yofel> santa_: oh that, I don't think we'll do that for the archive until 18.10, but we did remove it from the ci build list
[16:10] <yofel> it was on ubuntu-devel
[16:10] <yofel> ML
[16:11] <yofel> hm, why is i386 hardcoded there when there's proper archindep handling below that code....
[16:11] <acheronuk> yofel: another one that produced significant symbols changes - messagelib (kf5-messagelib) https://launchpadlibrarian.net/276544991/buildlog_ubuntu-yakkety-amd64.kf5-messagelib_4%3A16.04.3+p16.10+git20160803.1248-0_BUILDING.txt.gz
[16:11] <santa_> ah, there's a thread in kubuntu-devel too
[16:12] <yofel> yeah, that was partially CCd
[16:12] <yofel> acheronuk: maybe ignore that for today. I'll try to get the symbol ignoring added to the CI today after the meeting
[16:13] <acheronuk> yofel: no problem at all. will do
[16:17] <yofel> oh, the host key validation for launchpad is also only done once. I thought that happened for every dput attempt
[16:36] <clivejo> yofel: when I build libkolab it puts the lib in usr/lib/libkolab.so.1 but the install file is looking for usr/lib/*/libkolabxml.so.1* do I adjust the install file to match or try and make it put it into /usr/lib/<arch>
[16:37] <yofel> clivejo: first of all, that xml part sounds really wrong. But I would see why it doesn't put it into <arch> first
[17:05] <clivejo> Ive got a number of failed build emails from LP
[17:05] <ahoneybun> it's updating trusty still?
[17:05] <clivejo> huh?
[17:05] <ahoneybun> [Notice] -queuebot to #kubuntu-devel- Builds: Kubuntu Desktop amd64 [Trusty 14.04.5] has been updated (20160803)
[17:22] <acheronuk> libkf5eventview is looking for KGanttConfig.cmake
[17:23] <acheronuk> but libkf5kdgantt2 in KCI produces KF5KDGantt2Config.cmake
[17:23] <acheronuk> so FAIL!
[17:25] <santa_> https://gitlab.com/siduction-tools/pkg-kde-automation/blob/master/pass-c0-gensymbols
[17:26] <santa_> yofel ↑ the script I was usingto automate the addition of -c0
[17:27] <santa_> I can schedule a rebuild in my ppa simulation of frameworks/plasma/apps to check that it's still in shape
[17:38] <acheronuk> hmmm. they decided to use kdiagram https://quickgit.kde.org/?p=eventviews.git&a=blobdiff&h=4ae046296e4863b8a2af003c3da5d05e3014473d&hp=6ec8aeb705da8876bac5a796735dc18b009ff472&hb=b8ba0ff8aecd28e97d603bf659cf1c8a0191e291&f=CMakeLists.txt
[17:39] <acheronuk> which I can't see that we have
[17:45] <yofel> acheronuk: right, those images need testing
[17:46] <yofel> erm, ahoneybun^
[17:46] <acheronuk> lol
 who wants to see me dance with a chicken? https://hangouts.google.com/hangouts/_/event/c7qcgbtvn089cm84i6jumg2kplo?hl=en
 awww gosh darnit
 I missed it...
 missed?
 it's still on BBB atm
 !!!
[19:11] <yofel> santa_: thanks, with that I at least don't need to figure that out, just rewrite it in ruby
[19:19] <yofel> yay, I fixed the publication checks, building stuff is failing again \o/
[19:19] <jimarvan> :D
[19:25] <acheronuk> lol "It would very much appear that symbols have been retracted"
[19:29] <yofel> funny enough, akonadi is one of the packages that has -c0 set by default
[19:29] <yofel> which really shouldn't be the case
[19:30] <yofel> but yeah, i'll have to disable that check later on ^^
[19:31] <acheronuk> others will work though? I did wonder where they went, but thought it must have been by design
[19:31] <yofel> or hm
[19:32] <yofel> acheronuk: no, there was a weird requirement for an i386 buildlog, so that's why they stopped working
[19:32] <acheronuk> yeah, I saw where you worked that out earlier.
[19:33] <yofel> 19:17:10 KCI-E :: E: libkf5akonadiwidgets5: symbols-file-contains-current-version-with-debian-revision on symbol _ZN7Akonadi19ManageAccountWidget23setDescriptionLabelTextERK7QString@Base
[19:33] <yofel> I can't really disable that though...
[19:43] <jimarvan> clivejo: please record Rick the next time he says it
[19:43] <jimarvan> i want it as a ring tone
[19:43]  * tsimonq2 does it
[19:43] <jimarvan> ty ;)
[19:43] <clivejo> :P
[19:44] <tsimonq2> I have it up in Audacity
[19:44] <tsimonq2> RECORDED
[19:46] <jimarvan> OMG you are awesome
[19:46] <jimarvan> can you send it on irc? xD
[19:48] <yofel> hm, figuring if something is for 'stable' or 'unstable' is again complicated by the existence of frameworks :/
[19:49] <yofel> as those are - by design - only built in unstable
[19:49] <yofel> but are in fact only-stable
[19:50] <jimarvan> :/
[19:51] <tsimonq2> jimarvan: soon one sec
[19:56] <tsimonq2> jimarvan: http://picosong.com/Dk8m/
[19:57] <yofel> lol
[19:58] <acheronuk> :D
[19:59] <tsimonq2> lol, look at the song metadata
[19:59] <yofel> XD
[20:04] <yofel> guess I'll ditch the QA checks for frameworks for now
[20:04] <yofel> I might bring that back once the metadata for stable is back
[20:20] <tsimonq2> http://picosong.com/DkNh/
[20:20] <tsimonq2> again, see the song metadata :P
[20:22] <acheronuk> pmsl
[20:38] <jimarvan> gn peeps :)
[20:39] <acheronuk> night Jim
[21:04] <tsimonq2> yofel: so I'm seeing if I can fix that ^
[21:04] <tsimonq2> yofel: but I'm wondering why it's doing thast
[21:04] <tsimonq2> *that
[21:05] <yofel> tsimonq2: 21:03:41 dpkg-source: info: the patch has fuzz which is not allowed, or is malformed
[21:05] <tsimonq2> I see that, but I'm having trouble actually seeing what the error is
[21:05] <tsimonq2> I'll try some more locally but I don't know... :/
[21:06] <yofel> fuzz means that parts of the context lines around the patch block have changed
[21:06] <tsimonq2> oh that's helpfuk
[21:06] <tsimonq2> *helpful
[21:06] <yofel> so a simple quilt refresh of the patch should be enough to fix this
[21:06] <tsimonq2> there's a couple of them that I would like to fix
[21:06] <yofel> as long as it still applies with fuzz
[21:07] <yofel> the fuzz check is only applied at build time, not while unpackging and patching the source package
[21:07] <yofel> then it's just a warning
[21:08] <tsimonq2> well I learned something new today, thanks yofel :)
[21:09]  * yofel deploys experimental code to linode
[21:10] <yofel> if akonadi wasn't building..
[21:12] <tsimonq2> yofel: what's mgmt?
[21:12] <yofel> tsimonq2: "management" - CI maintenance jobs
[21:12] <tsimonq2> oh okay
[21:15] <acheronuk> I taking a look now at the YY FIX page with only 17 items, because if those tests work again that is going to fill right back up I think
[21:17] <tsimonq2> ahhhhhhhhhrgh
[21:20] <yofel> whee, I wrote ruby code that actually works \o/
[21:22]  * clivejo cheers
[21:23] <tsimonq2> could someone let me know what the *correct* procedure is for fixing fuzz errors? I'm trying but failing miserably...
[21:24] <tsimonq2> or rather, how are patches created (correctly) in the first place?
[22:54] <clivejo> anyone about?
[22:54] <clivejo> acheronuk: ping
[22:55] <tsimonq2> clivejo: yes, waiting for someone to respond to my question :P
[22:55] <tsimonq2> what's up?
[22:55] <clivejo> what was your question
[22:55] <tsimonq2> 04:23:09 PM < tsimonq2> could someone let me know what the *correct* procedure is for fixing fuzz errors? I'm trying but failing miserably...
[22:55] <tsimonq2> 04:24:53 PM < tsimonq2> or rather, how are patches created (correctly) in the first place?
[22:56] <clivejo> I dunno what the correct procedure is, but I tend to read the patch and if the lines are out, fix them
[22:57] <tsimonq2> alright
[22:57] <clivejo> or create a new patch by manually doing the edits
[22:57] <tsimonq2> good idea
[22:57] <clivejo> if its a bit more complicated
[22:59] <clivejo> so I would do quilt new Simons_new_ubber_fix.patch
[22:59] <tsimonq2> LOL
[22:59] <clivejo> quilt add <the file you are editing>
[22:59] <tsimonq2> yeah I have a guide somewhere, thanks ;)
[22:59] <clivejo> then make the changes
[22:59] <clivejo> and so fore
[22:59] <clivejo> forth
[23:00] <santa_> tsimonq2: what are you trying to fix in what branch?
[23:00] <clivejo> try and keep the original descriptions and headers
[23:00] <clivejo> santa_: are .h files usually installed into -dev packages?
[23:01] <santa_> clivejo: usually yes, why?
[23:01] <clivejo> got a ton of header files not sure what to do with them
[23:02] <santa_> what package?
[23:02] <clivejo> it seems to be a new one
[23:02] <santa_> from pim
[23:02] <clivejo> Im building a test package
[23:02] <clivejo> yes
[23:02] <santa_> which one?
[23:02] <clivejo> its called kdiagram
[23:03] <santa_> is the packaging already on git?
[23:03] <clivejo> https://launchpadlibrarian.net/276588091/buildlog_ubuntu-yakkety-amd64.libkf5eventviews_4%3A16.04.3+p16.10+git20160803.1733-0_BUILDING.txt.gz
[23:03] <clivejo> cant find it
[23:03] <clivejo> libkf5eventviews wants KGanttConfig.cmake
[23:03] <acheronuk> not in debian either
[23:03] <clivejo> this package seems to provide that
[23:04] <clivejo> Im just making skeleton packaging to see if it works
[23:04] <santa_> and d you have kgantt packaged?
[23:04] <santa_> * do you
[23:05] <santa_> nvm
[23:05] <santa_> you say it's suposed to be provided by kdiagram, right?
[23:09] <acheronuk> the eventview devs switched to building with kdiagram for some reason https://quickgit.kde.org/?p=eventviews.git&a=blobdiff&h=4ae046296e4863b8a2af003c3da5d05e3014473d&hp=6ec8aeb705da8876bac5a796735dc18b009ff472&hb=b8ba0ff8aecd28e97d603bf659cf1c8a0191e291&f=CMakeLists.txt
[23:11] <clivejo> santa_: yes, its building two libs
[23:11] <clivejo> kchart and kgantt
[23:12] <acheronuk> the 16.08 branch of eventviews still uses the old KF5KDGantt2. so far
[23:12] <acheronuk> so that shoudl be fine I hope
[23:14] <tsimonq2> santa_: kde-baseapps
[23:15] <tsimonq2> santa_: kubuntu_unstable
[23:15] <tsimonq2> santa_: so don't touch until I'm done please :P
[23:15] <santa_> tsimonq2: I don't have git perms yet, just want to know what are you doing
[23:16] <tsimonq2> oh k :)
[23:17] <santa_> tsimonq2: so it's the enable_debianabimanager.diff what is failing right?
[23:18] <tsimonq2> yeah
[23:19] <tsimonq2> ahhhhhhhh *pulls hair out*
[23:19] <tsimonq2> clivejo: can you please lend me a hand?
[23:20] <tsimonq2> http://kci.pangea.pub/job/yakkety_unstable_kde-baseapps/23/console
[23:21] <clivejo> thats the Debian ABI Manager
[23:22] <clivejo> basically it added a line or two to the CMakeLists.txt file
[23:23] <clivejo> download the source and see whats changed
[23:23] <clivejo> its probably just line numbers
[23:24] <tsimonq2> I tried...
[23:24] <tsimonq2> I'll try again...
[23:25] <acheronuk> that's not the only patch in the series that will fail ;)
[23:25] <tsimonq2> aaaaaaaa
[23:26] <tsimonq2> acheronuk: we'll get there when we get there... :P
[23:27] <acheronuk>  dpkg-source -i --before-build kde-baseapps
[23:27] <acheronuk> dpkg-source: info: applying enable_debianabimanager.diff
[23:27] <acheronuk> dpkg-source: info: applying enable_dlrestrictions.diff
[23:27] <acheronuk> dpkg-source: info: applying kubuntu_folderview_livecd_directory.diff
[23:27] <acheronuk> dpkg-source: error: LC_ALL=C patch -t -F 0 -N -p1 -u -V never -E -b -B .pc/kubuntu_folderview_livecd_directory.diff/ --reject-file=- < kde-baseapps/debian/patches/kubuntu_folderview_livecd_directory.diff gave error exit status 1
[23:27] <acheronuk> can't find file to patch at input line 10
[23:28] <santa_> tsimonq2, acheronuk: how can I download the source package?
[23:28] <santa_> or just the orig.tar.xz
[23:30] <acheronuk> there are snapshot links for .bz2 etc on kde quickgit, or you can do a shallow clone from git and tar it yourself
[23:31] <acheronuk> or..............
[23:32] <clivejo> santa_: from unstable PPA
[23:33] <clivejo> santa_: https://launchpad.net/~kubuntu-ci/+archive/ubuntu/unstable/+packages?field.name_filter=kde-baseapps&field.status_filter=published&field.series_filter=
[23:34] <clivejo> ie https://launchpad.net/~kubuntu-ci/+archive/ubuntu/unstable/+files/kde-baseapps_16.04.3+p16.10+git20160802.0908.orig.tar.xz
[23:34] <acheronuk> clivejo: that would be the last source it managed to patch OK though?
[23:34] <acheronuk> not the newer source snapshot that is failing to patch
[23:35] <clivejo> ah yes
[23:35] <santa_> yeah, I got the last one which was built
[23:35] <santa_> (which works)
[23:36] <santa_> gona clone from kde git then if nobody has a better suggestion
[23:36] <santa_> how are you guys doing it?
[23:36] <acheronuk> the workspace build directory on KCI also contains that last snapshotted source I think? 
[23:37] <acheronuk> http://kci.pangea.pub/job/yakkety_unstable_kde-baseapps/ws/build/
[23:37] <acheronuk> but you need to log in to get to that?
[23:37] <clivejo> this is true
[23:38] <tsimonq2> aaaargh I need help
[23:38] <santa_> I don't have access to that
[23:39] <acheronuk> santa_: that was more for tsimonq2 
[23:40] <acheronuk> tsimonq2: what is the trouble
[23:40] <tsimonq2> acheronuk: I can't get this stupid thing to build
[23:40] <tsimonq2> acheronuk: everything I try doesn't work
[23:40] <tsimonq2> acheronuk: I tried to recreate the patch
[23:41] <tsimonq2> acheronuk: I tried to do it locally, works fine
[23:41] <tsimonq2> acheronuk: I'm struggling
[23:42] <acheronuk> tsimonq2: so that patch applies locally with quilt, but doesn't when you try to built the source package?
[23:42] <acheronuk> *build
[23:43] <tsimonq2> acheronuk: I can build the source package fine locally
[23:45] <acheronuk> against what source? as it should fail on other patches in the series, even if you fix the first one
[23:53] <tsimonq2> acheronuk: I'll try grabbing that git repo then
[23:53] <tsimonq2> *shrug*
[23:55] <santa_> tsimonq2: in your local stuff, can you paste the output of "quilt pop -a && quilt push -a"?
[23:59] <tsimonq2> FINALLY I can locally reproduce it
[23:59] <santa_> tsimonq2: passing an option to fail on fuzz I presume