[04:30] <testificate> is any launchpad support on duty atm?
[04:33] <lifeless> no, but you might get lucky ;) Just ask.
[04:35] <testificate> some personal information was posted in a launchpad bug report. and I'm trying to see if I can have it edited or pulled
[04:35] <StevenK> We can hide the comment.
[04:35] <StevenK> Which bug and comment number?
[04:36] <lifeless> whats the url to the comment? thats from the top right of the commen - the #123 thing, and you can privmsg me if you like
[04:36] <lifeless> StevenK: trade you, I handle this, you finish reviewing :P
[04:36] <StevenK> lifeless: I have
[04:37] <lifeless> \o/
[04:37] <StevenK> lifeless: The LPGL comment is the only one I have
[04:37] <lifeless> yeah, see the thread - trove are not freetext
[04:38] <lifeless> StevenK: I've fixed that extraneous line up
[04:38] <lifeless> turns out testificate
[04:38] <lifeless> turns out testificate's issue is with the initial bug description :(
[04:38] <StevenK> Drat
[04:38] <wgrant> Best to make the bug private, then.
[04:38] <StevenK> Or wave SQL :-P
[04:39] <wgrant> Fixing the description history is on the radar, but it's not clear how to do it.
[04:39] <StevenK> For exactly this reason, I bet
[04:40] <wgrant> Yes.
[04:44] <lifeless> have made private and recommended filing a bug on apport
[04:45] <wgrant> Have you unsubscribed everyone?
[04:45] <wgrant> What's the bug #?
[04:46] <george_e> All of the builds from my recipe are failing with an unusual error. Here's one of the buildlogs: https://launchpadlibrarian.net/85234067/buildlog.txt.gz
[04:47] <george_e> The error: "bzr: ERROR: No module named apt_pkg.
[04:47] <george_e> You may need to install this Python library separately."
[04:47] <lifeless> wgrant: bug 499821
[04:47] <lifeless> wgrant: just -security and -bugs left, which testificate was ok with
[04:47] <wgrant> george_e: Fix for that is currently being rolled out
[04:47] <lifeless> wgrant: neither being inclusive
[04:48] <wgrant> lifeless: -bugs is roughly $world
[04:48] <george_e> wgrant: Will I be able to retry the build afterward without worrying about uploading the same version?
[04:48] <lifeless> wgrant: eh, requires coc + mentoring
[04:48] <lifeless> but yeah, can delete it too I guess
[04:48] <wgrant> george_e: Yes
[04:48] <george_e> Thanks.
[04:55] <testificate> wgrant: is -bugs not private?
[04:57] <lifeless> testificate: its the folk that can do bug triage for Ubuntu; joining the team is open to folk that demonstrate trustworthiness, sign the coc, and learn the triage rules.
[04:58] <lifeless> you can't just-join, and you can be removed if you are a problem
[05:00] <testificate> well I suppose that's the best that can be done for now then
[06:53] <george_e> Is it possible to change the Git URL an automatic import pulls from for a branch?
[06:56] <wgrant> george_e: You can't, but you can ask us to change it.
[06:56] <wgrant> As long as it's the same repo, just moved.
[06:57] <george_e> Could you please change ~george-edison55/libwebp/trunk to pull from http://git.chromium.org/webm/libwebp.git
[06:57] <george_e> It's got the old Git URL there.
[06:59] <wgrant> Let's see if that works.
[06:59] <george_e> Thank you!
[07:00] <george_e> Hopefully that will get the builds rolling again.
[09:03] <mrevell> Hi!
[11:19] <mirrakor_> is there a statistic for PPA archives?
[12:14] <tumbleweed> any ideas why this bug can't be created via the API? http://paste.ubuntu.com/740135/
[12:21] <wgrant> tumbleweed: Looks like your title has a newline at the end.
[12:21] <wgrant> Well, that's helpful.
[12:24] <wgrant> 23:21:16 < wgrant> tumbleweed: Looks like your title has a newline at the end.
[12:26] <tumbleweed> didn't think of that, thanks
[12:26]  * tumbleweed tries to figure out where that came from
[14:36] <CarlFK> http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/oneiric/squid-deb-proxy/oneiric/view/head:/debian/squid-deb-proxy.templates
[14:36] <CarlFK> I like pink and all, but... um.. not there.
[14:43] <CarlFK> is that really spozed to look like that? (and does anyone else think it is pretty hard to read?
[16:31] <Pegasus_RPG> Hello. I'm trying to add an ssh public key that I generated from an S/MIME certificate using a procedure I found on the Web. But Launchpad complains that the key is invalid. If I add extra words to the end, it takes it fine but incorporates the first extra word into the key instead of putting it as a coment
[16:31] <Pegasus_RPG> Am I doing something wrong?
[18:04] <SpamapS> was this a temporary error for daily builds? bzr: ERROR: No module named apt_pkg
[18:04] <SpamapS> https://launchpadlibrarian.net/85239636/buildlog.txt.gz
[18:05] <SpamapS> I had a bunch fail this morning
[18:05] <lamont> SpamapS: there was a rollout today APAC-time... could you do a test build and tell me if it still fails?
[18:06] <SpamapS> lamont: ack, running now
[18:07] <SpamapS> lamont: https://code.launchpad.net/~juju/+archive/pkgs/+recipebuild/119811 , expected in 4 hours.. ;)
[18:08] <lamont> there. that's a bit better
[18:11] <dobey> SpamapS: yes, i saw a couple of those last night, and a rebuild worked fine
[18:14] <lamont> SpamapS: looks like a winner?
[18:49] <SpamapS> lamont: yes, sorry, had a phone call, thanks for the q jump. :)
[18:58] <thomi|work> Hi - is there any way to force a recipe to be built for a new distro series? I've just enabled packages for natty on an existing recipe, and I want to trigger a build without touching the bazaar branch. Any ideas?
[18:58] <jelmer> thomi|work: you can request a build on the web page
[18:59] <thomi|work> jelmer: It's currently set to build daily. if I set it to build on request the "request build" button doesn't appear.
[18:59] <thomi|work> oh nuts - sorry, it hides down the bottom of the page. My bad.
[19:00] <thomi|work> Thanskl
[19:00] <moo-> how can i find the list of bugs that affect most people?
[19:01] <jelmer> moo-: go the the bugs page, then select "Order by number of users affected"
[19:02] <moo-> oh
[19:02] <moo-> https://bugs.launchpad.net/ubuntu
[19:03] <moo-> i dont find that
[19:04] <jelmer> moo-: there is a select box with "by importance"
[19:04] <jelmer> change that to "by number of users affected"
[19:04] <jelmer> not sure if it works on the Ubuntu project though, it's got a lot of bugs
[19:04] <moo-> ah there
[19:04] <moo-> thanks!
[19:05] <moo-> nspluginwrapper is #1, you can fix this easily by putting flash 64-bit in repository so ppl can use that instead of nspluginwrapper
[19:07] <jelmer> moo-: it's probably better to comment on the bug itself, this channel is about Launchpad, not Ubuntu
[19:08] <moo-> ok
[19:09] <jelmer> (but please do read the other comments, I'm sure that if there was a simple solution it would've already been fixed)
[19:13] <moo-> there is a simple solution, put the 64-bit flash version in the repository
[21:12] <poolie> SpamapS, lamont, dobey, yes, it was a bug
[21:12] <poolie> it's now fixed and deployed thanks to haw and lamont
[21:36] <rillian> hi. I'm trying to set up a launchpad mirror of https://git.xiph.org/opus.git
[21:36] <rillian> but the imports seem to fail without actually pulling anything
[21:36] <mwhudson> rillian: got a link to an import?
[21:36] <rillian> https://code.launchpad.net/~xiph/opus/master
[21:38] <mwhudson> hm
[21:38] <mwhudson> is there a git:// protocol mirror?
[21:39] <rillian> yes, just s/https/git/
[21:39] <mwhudson> have you tried importing that?
[21:39] <mwhudson> that said
[21:39] <mwhudson> bzr branch https://git.xiph.org/opus.git/ works just fine here
[21:39] <rillian> no. I did try http in case it was the authentication
[21:40] <mwhudson> ah, anyway:
[21:40] <mwhudson> bzr: ERROR: The repository you are fetching from contains submodules. To continue, upgrade your Bazaar repository to a format that supports nested trees, such as 'development-subtree'.
[21:40] <mwhudson> hi jelmer :-)
[21:40] <rillian> mwhudson, well, that's more than I got
[21:40] <rillian> I didn't think the repo had submodules though
[21:42] <mwhudson> rillian: i changed the import to git and got http://launchpadlibrarian.net/85300633/xiph-opus-master.log
[21:42] <mwhudson> rillian: which reflects what happened to me locally
[21:43] <rillian> ok, so two problems
[21:43] <rillian> 'git submodule status' prints nothing
[21:44] <Resistance> is the bzr-builder ppa restricted to the recipe team?
[21:44] <Resistance> or is there another way i can add that into my system?
[21:44]  * Resistance wants to local-test a recipe first
[21:46] <rillian> mwhudson, apparently there are submodules somewhere in the history
[21:47] <rillian> does that mean we can't mirror now, o is the 'upgrade your Bazaar repository' message something you can act on?
[21:47] <tumbleweed> Resistance: it tells you how to install it, in the project description: https://launchpad.net/bzr-builder
[21:48] <Resistance> tumbleweed:  then the page on the wiki needs updating - because that page links to a 403'd page
[21:49] <Resistance> tumbleweed:  Getting bzr-builder... You can install the bzr-builder plugin from this PPA:  https://launchpad.net/~dailydebs-team/+archive/bzr-builder
[21:50] <Resistance> that 403s
[21:50] <Resistance> or at least, says "Forbidden"
[21:50] <Resistance> (from https://help.launchpad.net/Packaging/SourceBuilds/GettingStarted#Getting_bzr-builder )
[21:50] <poolie> Resistance, the source is all out there
[21:50] <poolie> can i ask why you want to run it?
[21:50] <poolie> oh i see
[21:50] <poolie> you already said, to locally test it
[21:50] <Resistance> mhm
[21:51] <Resistance> *before* troubling the builders :P
[21:51]  * tumbleweed finds local testing vital when working on daily builds
[21:51] <poolie> i think the link is wrong
[21:51] <Resistance> and also the advice on the page tumbleweed linked me is wrong
[21:51] <Resistance> the code there that says to install/run it..
[21:51] <Resistance> this happens:
[21:51] <poolie> yes that link
[21:52] <Resistance> [kahless /home/teward/testing]% bzr branch lp:bzr-builder ~/.bazaar/plugins/builder
[21:52] <Resistance> bzr: ERROR: Parent of "/home/teward/.bazaar/plugins/builder" does not exist.
[21:52] <poolie> oh well that's easy
[21:52] <poolie> mkdir -p ~/.bazaar/plugins
[21:54] <poolie> https://bugs.launchpad.net/launchpad/+bug/891373
[21:54] <poolie> will try to look into it later
[21:56] <Resistance> does the debian/changelog version name just have to be whatever the base version is minus the ~{revno} stuff for the recipe?
[21:57]  * Resistance is getting a crash if he includes {revno} in the changelog
[21:58] <tumbleweed> don't worry about the changelog, the recipe build adds a new entry, with the version number based on your recipe
[21:58] <Resistance> ah good
[21:59] <Resistance> wth is this upstream source thing... its a bloody test recipe!
[21:59] <Resistance> there is no upstream source :/
[22:01] <jelmer> Resistance: your package probably disagrees (does it have the source format set to "3.0 (quilt)" or a version string that suggests a non-native package?)
[22:01] <jelmer> Resistance: alternatively, you can specify --allow-fallback-to-native
[22:01] <Resistance> jelmer:  yeah it builds when i use --allow-fallback-to-native
[22:02] <Resistance> but this'll need to work in PPAs, no?
[22:02] <Resistance> can i even specify such a build string?
[22:02]  * Resistance assumes not
[22:02] <jelmer> Resistance: launchpad has --allow-fallback-to-native enabled by default
[22:02] <Resistance> yeah it has the source format set to 3.0 (quilt)
[22:02]  * Resistance slaps his templates
[22:02] <jelmer> Resistance: "3.0 (quilt)" does suggest it's a non-native package, with an upstream source
[22:02] <Resistance> i'll have to fix those :P
[22:03] <Resistance> jelmer:  what should i change that to, if anything, to remove that?
[22:03] <jelmer> Resistance: "3.0 (native)"
[22:03] <Resistance> ok
[22:04] <Resistance> jelmer:  where would the output be located?  http://pastebin.com/bkjS0gqq  <-- last thing there is a lintian E: line, followed by a W: line.
[22:04] <Resistance> :/
[22:04] <Resistance> other than that, there's no errors
[22:08] <jelmer> Resistance: I think the second argument is the target dir
[22:09] <Resistance> also the lintian line might not show up anymore (to allow my system to stop yelling at me, i added teward@kahless to my active PGP key)
[22:09] <Resistance> jelmer:  well it built the source package correctly...
[22:10] <Resistance> jelmer:  theoretically, i'd have to pbuilder the source to determine whether it'll not explode, right?


[05:41] <Kilos> o/
[16:32] <tyhicks> hello
[16:32] <jdstrand> hi!
[16:32] <tyhicks> #startmeeting
[16:32] <meetingology> Meeting started Mon Feb  1 16:32:51 2016 UTC.  The chair is tyhicks. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[16:32] <meetingology> Available commands: action commands idea info link nick
[16:33] <tyhicks> The meeting agenda can be found at:
[16:33] <tyhicks> [LINK] https://wiki.ubuntu.com/SecurityTeam/Meeting
[16:33] <tyhicks> [TOPIC] Announcements
[16:33] <tyhicks> Gianfranco Costamagna (LocutusOfBorg) provided debdiffs for trusty-wily for virtualbox (LP: #1538115)
[16:33] <tyhicks> Otto Kekäläinen provided debdiffs for mariadb-5.5 (trusty, LP: #1524704) and mariadb-10.0 (vivid, wily, LP: #1538315)
[16:33] <tyhicks> Thank you for your assistance in keeping Ubuntu users secure! :)
[16:33] <tyhicks> [TOPIC] Weekly stand-up report
[16:33] <tyhicks> jdstrand: you're up
[16:35] <jdstrand> hey
[16:36] <jdstrand> so, this week I am focusing on snappy. in particular the review tools
[16:36] <jdstrand> I will be working on cleanups, new snap.yaml format and squashfs verification
[16:36] <jdstrand> I think that is it for me
[16:36] <jdstrand> mdeslaur: you're up
[16:36] <mdeslaur> I'm on triage this week
[16:37] <mdeslaur> and I plan on working on qemu updates
[16:37] <jdstrand> oh, I'll also respond to the skills threads as needed
[16:37] <mdeslaur> I may have time to pick something else off the list
[16:37] <mdeslaur> that's about it, sbeattie
[16:37] <sbeattie> I'm in the happy place this week
[16:37] <sbeattie> I have openjdk updates that I'm finishing up
[16:38] <sbeattie> I need to finish writing up my gcc -pie email about the test rebuild
[16:38] <sbeattie> I also have some apparmor items to get through this week
[16:38] <sbeattie> That will probably consume most of my week, along with the usual kernel cve handling.
[16:38] <sbeattie> tyhicks: you're up.
[16:39] <tyhicks> I'm in the community role this week
[16:39] <tyhicks> I will again focus on AppArmor stacking
[16:39] <tyhicks> I'm working on adding the ability to handle stacking rules in apparmor_parser
[16:40] <tyhicks> I'll also be working on cleaning up a large patch set of AppArmor kernel fixes from jj to land in Xenial and SRU to stable releases
[16:41] <tyhicks> if I have time, there are a few code review requests that would be nice to tend to
[16:41] <tyhicks> that's it for me
[16:41] <tyhicks> jjohansen: you're up
[16:42] <tyhicks> I don't see him around atm
[16:42] <tyhicks> sarnold_: go ahead
[16:43] <sarnold> bah
[16:44] <sarnold> I'm on bug triage this week; I ought to finish the dpdk MIR today or tomorrow (depending upon how buggy the weekend was :) and then move on to the backlog of review requests; if there's more apparmor stacking discussion, maybe throw in my two cents occasionally
[16:44] <sarnold> that should do it for me, chrisccoulson?
[16:44] <chrisccoulson> I don't have any updates planned this week (yay), although I'm still expecting a thunderbird update at some point
[16:45] <chrisccoulson> So I'll be focusing on finishing bug 1459830 and investigating some issues with playcanvas
[16:46] <chrisccoulson> Oh, the "no updates planned" bit isn't technically true - I'll be updating Firefox this week to fix a regression in the current version
[16:46] <chrisccoulson> I think that's me done
[16:46] <tyhicks> bummer
[16:46] <tyhicks> would have been nice to make it through the week without an update :)
[16:46] <chrisccoulson> heh
[16:47] <tyhicks> [TOPIC] Highlighted packages
[16:47] <tyhicks> The Ubuntu Security team will highlight some community-supported packages that might be good candidates for updating and or triaging. If you would like to help Ubuntu and not sure where to start, this is a great way to do so.
[16:47] <tyhicks> See https://wiki.ubuntu.com/SecurityTeam/UpdateProcedures for details and if you have any questions, feel free to ask in #ubuntu-security. To find out other ways of helping out, please see https://wiki.ubuntu.com/SecurityTeam/GettingInvolved.
[16:47] <tyhicks> http://people.canonical.com/~ubuntu-security/cve/pkg/owncloud-client.html
[16:47] <tyhicks> http://people.canonical.com/~ubuntu-security/cve/pkg/node.html
[16:47] <tyhicks> http://people.canonical.com/~ubuntu-security/cve/pkg/tripleo-heat-templates.html
[16:47] <tyhicks> http://people.canonical.com/~ubuntu-security/cve/pkg/geary.html
[16:47] <tyhicks> [TOPIC] Miscellaneous and Questions
[16:47] <tyhicks> http://people.canonical.com/~ubuntu-security/cve/pkg/puppet-module-puppetlabs-stdlib.html
[16:47] <tyhicks> Does anyone have any other questions or items to discuss?
[16:49] <tyhicks> jdstrand, mdeslaur, sbeattie, jjohansen, sarnold, ChrisCoulson: Thanks!
[16:49] <tyhicks> #endmeeting
[16:49] <meetingology> Meeting ended Mon Feb  1 16:49:21 2016 UTC.
[16:49] <meetingology> Minutes:        http://ubottu.com/meetingology/logs/ubuntu-meeting/2016/ubuntu-meeting.2016-02-01-16.32.moin.txt
[16:49] <mdeslaur> thanks tyhicks
[16:49] <sbeattie> tyhicks: thanks!
[16:53] <sarnold> thanks tyhicks!


[14:45] <MTecknology> Is the new theme going to be opened up to the public?
[14:48] <cjohnston> eventually
[14:48] <cjohnston> they wont tell us when
[14:49] <MTecknology> oh
[14:50] <MTecknology> will this still be for Drupal 5 or are they moving up to Drupal 6 or 7?
[14:52] <MTecknology> I'm just curious because I know for me to keep the ubuntu-drupal project going whether I get teh source or not, I'll have to tear it apart so I can chunk it into little modules and everything. For Drupal 6; I think I'm pretty much done developing new stuff, I've been gearing up for the change to D7
[15:02] <cjohnston> I couldn't tell you.. I don't get any answers.. lol
[15:02] <cjohnston> newz2000: you around yet?
[15:03] <newz2000> cjohnston: kind of
[15:03] <cjohnston> Can you answer MTecknology's questions?
[15:04] <newz2000> hey MTecknology: You're going to get some kind of help but I don't think the plan is to have dozen's of ubuntu.com clone sites. This is still in discussion
[15:05] <newz2000> If nothing else we'll push to have a community theme building project here in the web-team
[15:06] <MTecknology> newz2000: My goal of it is for loco sites, I already do that for the current theme. http://ubuntu-il.com/site/
[15:07] <newz2000> Yeah, that would be an example of a "clone site" that I don't think we want to encourage. Instead,
[15:07] <newz2000> what is better is to have a theme that shows a relationship without being a duplicate
[15:07] <newz2000> So that the sites feel unified and connected w/out leading people to think they're still on the same site
[15:08] <MTecknology> oh, i didn't realized I made it mimic that closely :P
[15:09] <newz2000> I know it's exciting to see the chagnes - think about it but hold tight
[15:10] <MTecknology> I'm only thinking now, I've been getting a lot of questions about it already
[15:13] <newz2000> I've got about three emails drafted to the web team to help answer questions and provide guidance for upcoming projects
[15:13] <newz2000> but there's so much happening that every time I draft it gets out-dated
[15:13] <MTecknology> newz2000: so if we make a new theme that's kind of close to what you guys come up with but very noticably different, not just enough for legal distinction, that's ok?
[15:14] <MTecknology> or still not what you're thinking?
[15:14] <newz2000> I im talks with the project manager in antoher IRC channel to hopefully have some more details ironed out
[15:14] <newz2000> MTecknology: yeah, I think that's ideal
[15:16] <newz2000> alejandraobregon has put some great thought and effort into the current design so we should get a little more details about that public so that we can apply the best parts of her work (as they pertain to community sites) to the new themes
[15:17] <newz2000> She's really thinking deeply about navigation and I think this will be key to get right in the new theme
[15:17] <newz2000> (as you remember, it was a major shortcoming of the existing theme)
[15:18] <MTecknology> ok; When you guys roll out the new theme I'll have to rip it apart anyway I'm sure. I make sure it works for RTL languages and varying widths like 80% or 900px. I'll keep thinking about ways to offer a distinction.
[15:21] <newz2000> MTecknology: another good thing to think about is how the different kinds of information that are shown on community sites
[15:22] <newz2000> and how that differs from ubuntu.com.
[15:22] <newz2000> ubuntu.com, even though it's a free product, is really about selling Ubuntu
[15:22] <newz2000> and community sites kind of have a different purpose
[15:23] <MTecknology> good point; I'll try to talk to some people about how they would like to see content moved around
[15:26] <newz2000> that would be a very useful place to start
[15:26] <newz2000> Also, your rtl stuff will be helpful too. We don't have a lot of in-house rtl users
[16:25] <cjohnston> uh oh.. newz2000 is on skype.. i might have to figure out what he looks like :-P
[16:39] <MTecknology> cjohnston: I know what doctormo and pleia2 look like - that's it
[16:40] <MTecknology> oh - I think I saw sabdfl once upon a time too..
[16:41] <cjohnston> MTecknology: ill show you my picture
[16:41] <cjohnston> althought it may scare you
[16:42] <MTecknology> :P
[16:42] <MTecknology> ok
[17:01] <MTecknology> wow, that's a short hostmask
[17:01] <cjohnston> lol
[17:02] <cjohnston> MTecknology: you on facebook?
[17:02] <MTecknology> ya
[17:02] <MTecknology> @canonical/mpt vs. @kalliki/admin/pdpc.supporter.mtecknology
[17:02] <cjohnston> http://www.facebook.com/FFEMTcJ
[17:03] <MTecknology> where's the scary?
[17:03] <mpt> MTecknology, I used to be canonical/launchpad/mpt, then I left the Launchpad team, so I asked to be canonical/ubuntu/mpt, but apparently canonical/ubuntu doesn't exist, so...
[17:03] <MTecknology> oh
[17:57] <cjohnston> MTecknology: seeing my picture
[18:56] <MTecknology> cjohnston: 11:03 < MTecknology> where's the scary? <- I was referring to the pic
[18:57] <cjohnston> me
[20:28] <cjohnston> newz2000: you still around?
[20:28] <newz2000> Si!
[20:29] <cjohnston> You don't by chance have, or can get the svgs for the new logos can you?
[20:29] <cjohnston> Need it for a logo we are going to make
[21:12] <thorwil> cjohnston: rather unlikely, as the whole artwork community is waiting for those


[00:02] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[00:02] -kubuntu-ci:#kubuntu-devel- Project merger_kdesdk-thumbnailers build #103: FIXED in 1 min 37 sec: http://kci.pangea.pub/job/merger_kdesdk-thumbnailers/103/
[00:04] -kubuntu-ci:#kubuntu-devel- Project merger_kdiamond build #613: FAILURE in 3 min 29 sec: http://kci.pangea.pub/job/merger_kdiamond/613/
[00:07] -kubuntu-ci:#kubuntu-devel- Project mgmt_merger build #697: STILL UNSTABLE in 6 min 13 sec: http://kci.pangea.pub/job/mgmt_merger/697/
[00:07] -kubuntu-ci:#kubuntu-devel- Project mgmt_progenitor build #683: STILL UNSTABLE in 6 min 15 sec: http://kci.pangea.pub/job/mgmt_progenitor/683/
[00:12] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kgpg build #97: STILL FAILING in 4 min 1 sec: http://kci.pangea.pub/job/yakkety_unstable_kgpg/97/
[00:13] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kgpg build #97: STILL FAILING in 4 min 16 sec: http://kci.pangea.pub/job/xenial_unstable_kgpg/97/
[00:22] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kgpg build #98: STILL FAILING in 3 min 45 sec: http://kci.pangea.pub/job/xenial_unstable_kgpg/98/
[00:25] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kgpg build #98: STILL FAILING in 8 min 30 sec: http://kci.pangea.pub/job/yakkety_unstable_kgpg/98/
[00:27] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kppp build #89: STILL UNSTABLE in 19 min: http://kci.pangea.pub/job/yakkety_unstable_kppp/89/
[00:27] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdesdk-kioslaves build #47: STILL UNSTABLE in 19 min: http://kci.pangea.pub/job/yakkety_unstable_kdesdk-kioslaves/47/
[00:28] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdesdk-kioslaves build #86: STILL UNSTABLE in 20 min: http://kci.pangea.pub/job/xenial_unstable_kdesdk-kioslaves/86/
[00:43] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kde-runtime build #206: STILL FAILING in 34 min: http://kci.pangea.pub/job/xenial_unstable_kde-runtime/206/
[00:43] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kppp build #12: STILL UNSTABLE in 35 min: http://kci.pangea.pub/job/xenial_unstable_kppp/12/
[00:59] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kcoreaddons build #268: STILL UNSTABLE in 32 min: http://kci.pangea.pub/job/xenial_unstable_kcoreaddons/268/
[00:59] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[00:59] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_breeze-icons build #292: FIXED in 32 min: http://kci.pangea.pub/job/xenial_unstable_breeze-icons/292/
[00:59] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kopete build #89: STILL UNSTABLE in 51 min: http://kci.pangea.pub/job/xenial_unstable_kopete/89/
[01:00] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kde-runtime build #212: STILL FAILING in 51 min: http://kci.pangea.pub/job/yakkety_unstable_kde-runtime/212/
[01:12] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kde-runtime build #207: STILL FAILING in 23 min: http://kci.pangea.pub/job/xenial_unstable_kde-runtime/207/
[01:12] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kopete build #66: STILL UNSTABLE in 1 hr 4 min: http://kci.pangea.pub/job/yakkety_unstable_kopete/66/
[01:12] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kauth build #158: STILL UNSTABLE in 28 min: http://kci.pangea.pub/job/yakkety_unstable_kauth/158/
[01:12] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_okular build #100: STILL UNSTABLE in 27 min: http://kci.pangea.pub/job/yakkety_unstable_okular/100/
[01:12] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_okular build #22: STILL UNSTABLE in 29 min: http://kci.pangea.pub/job/xenial_unstable_okular/22/
[01:12] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[01:12] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_breeze-icons build #176: FIXED in 28 min: http://kci.pangea.pub/job/yakkety_unstable_breeze-icons/176/
[01:12] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdevelop-pg-qt build #23: STILL UNSTABLE in 28 min: http://kci.pangea.pub/job/yakkety_unstable_kdevelop-pg-qt/23/
[01:13] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kcrash build #279: STILL UNSTABLE in 13 min: http://kci.pangea.pub/job/xenial_unstable_kcrash/279/
[01:23] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kauth build #286: STILL UNSTABLE in 23 min: http://kci.pangea.pub/job/xenial_unstable_kauth/286/
[01:30] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kde-runtime build #213: STILL FAILING in 24 min: http://kci.pangea.pub/job/yakkety_unstable_kde-runtime/213/
[01:30] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kcrash build #155: STILL UNSTABLE in 18 min: http://kci.pangea.pub/job/yakkety_unstable_kcrash/155/
[02:15] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kwallet build #293: STILL UNSTABLE in 16 min: http://kci.pangea.pub/job/xenial_unstable_kwallet/293/
[02:24] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kwallet build #132: STILL UNSTABLE in 16 min: http://kci.pangea.pub/job/yakkety_unstable_kwallet/132/
[03:02] <ahoneybun> darn OBS has not updated the PPA for yakkety
[03:03] <DarinMiller> OBS?
[03:11] <ahoneybun> https://obsproject.com/
[03:37] <tsimonq2> Night o/
[03:39] <DarinMiller> night simon o/
[03:47] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_spectacle build #109: STILL UNSTABLE in 13 min: http://kci.pangea.pub/job/xenial_unstable_spectacle/109/
[03:47] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_spectacle build #88: STILL UNSTABLE in 13 min: http://kci.pangea.pub/job/yakkety_unstable_spectacle/88/
[03:55] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdenlive build #288: STILL FAILING in 24 min: http://kci.pangea.pub/job/xenial_unstable_kdenlive/288/
[03:55] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdenlive build #137: STILL FAILING in 24 min: http://kci.pangea.pub/job/yakkety_unstable_kdenlive/137/
[04:08] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_okteta build #117: STILL UNSTABLE in 21 min: http://kci.pangea.pub/job/xenial_unstable_okteta/117/
[04:08] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_umbrello build #95: STILL UNSTABLE in 21 min: http://kci.pangea.pub/job/xenial_unstable_umbrello/95/
[04:15] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kstars build #260: STILL UNSTABLE in 28 min: http://kci.pangea.pub/job/xenial_unstable_kstars/260/
[04:19] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdenlive build #289: STILL FAILING in 19 min: http://kci.pangea.pub/job/xenial_unstable_kdenlive/289/
[04:19] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdenlive build #138: STILL FAILING in 19 min: http://kci.pangea.pub/job/yakkety_unstable_kdenlive/138/
[04:22] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kstars build #128: STILL UNSTABLE in 26 min: http://kci.pangea.pub/job/yakkety_unstable_kstars/128/
[04:22] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_ktp-common-internals build #137: STILL UNSTABLE in 20 min: http://kci.pangea.pub/job/yakkety_unstable_ktp-common-internals/137/
[04:22] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_ktp-common-internals build #211: STILL UNSTABLE in 21 min: http://kci.pangea.pub/job/xenial_unstable_ktp-common-internals/211/
[04:23] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_umbrello build #80: STILL UNSTABLE in 26 min: http://kci.pangea.pub/job/yakkety_unstable_umbrello/80/
[04:23] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_plasma-framework build #152: STILL FAILING in 19 min: http://kci.pangea.pub/job/yakkety_unstable_plasma-framework/152/
[04:25] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kde-baseapps build #102: STILL FAILING in 10 min: http://kci.pangea.pub/job/yakkety_unstable_kde-baseapps/102/
[04:30] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_libkcompactdisc build #51: STILL UNSTABLE in 16 min: http://kci.pangea.pub/job/xenial_unstable_libkcompactdisc/51/
[04:36] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kde-baseapps build #97: STILL FAILING in 4 min 55 sec: http://kci.pangea.pub/job/xenial_unstable_kde-baseapps/97/
[04:36] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kde-baseapps build #103: STILL FAILING in 5 min 56 sec: http://kci.pangea.pub/job/yakkety_unstable_kde-baseapps/103/
[04:44] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kirigami build #37: STILL UNSTABLE in 20 min: http://kci.pangea.pub/job/xenial_unstable_kirigami/37/
[04:44] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_ktp-auth-handler build #185: STILL UNSTABLE in 21 min: http://kci.pangea.pub/job/xenial_unstable_ktp-auth-handler/185/
[04:44] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_ktp-auth-handler build #138: STILL UNSTABLE in 21 min: http://kci.pangea.pub/job/yakkety_unstable_ktp-auth-handler/138/
[04:44] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_plasma-mediacenter build #188: STILL UNSTABLE in 21 min: http://kci.pangea.pub/job/xenial_unstable_plasma-mediacenter/188/
[04:45] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kde-baseapps build #98: STILL FAILING in 3 min 46 sec: http://kci.pangea.pub/job/xenial_unstable_kde-baseapps/98/
[04:45] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kwin build #7: STILL FAILING in 50 sec: http://kci.pangea.pub/job/xenial_unstable_kwin/7/
[04:51] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kwin build #8: STILL FAILING in 43 sec: http://kci.pangea.pub/job/xenial_unstable_kwin/8/
[04:55] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_plasma-framework build #153: STILL FAILING in 26 min: http://kci.pangea.pub/job/yakkety_unstable_plasma-framework/153/
[05:02] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_plasma-integration build #6: STILL UNSTABLE in 16 min: http://kci.pangea.pub/job/xenial_unstable_plasma-integration/6/
[05:02] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_marble build #7: STILL FAILING in 17 min: http://kci.pangea.pub/job/xenial_unstable_marble/7/
[05:03] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_plasma-sdk build #230: STILL UNSTABLE in 18 min: http://kci.pangea.pub/job/xenial_unstable_plasma-sdk/230/
 anybody awake here?
 how do I add Yakety to this bug report? https://bugs.launchpad.net/network-manager-vpnc/+bug/1297849
[05:09] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_discover build #5: STILL FAILING in 7 min 0 sec: http://kci.pangea.pub/job/xenial_unstable_discover/5/
[05:11] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_akonadi-calendar build #6: STILL UNSTABLE in 16 min: http://kci.pangea.pub/job/yakkety_unstable_akonadi-calendar/6/
[05:12] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_akonadi-contacts build #42: STILL UNSTABLE in 17 min: http://kci.pangea.pub/job/xenial_unstable_akonadi-contacts/42/
[05:12] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kirigami build #41: STILL UNSTABLE in 16 min: http://kci.pangea.pub/job/yakkety_unstable_kirigami/41/
[05:12] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_plasma-mediacenter build #105: STILL UNSTABLE in 16 min: http://kci.pangea.pub/job/yakkety_unstable_plasma-mediacenter/105/
[05:13] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kwin build #7: STILL FAILING in 1 min 7 sec: http://kci.pangea.pub/job/yakkety_unstable_kwin/7/
[05:19] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kwin build #8: STILL FAILING in 50 sec: http://kci.pangea.pub/job/yakkety_unstable_kwin/8/
[05:19] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_discover build #6: STILL FAILING in 4 min 54 sec: http://kci.pangea.pub/job/xenial_unstable_discover/6/
[05:24] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_marble build #8: STILL FAILING in 17 min: http://kci.pangea.pub/job/xenial_unstable_marble/8/
[05:27] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_plasma-integration build #6: STILL UNSTABLE in 15 min: http://kci.pangea.pub/job/yakkety_unstable_plasma-integration/6/
[05:28] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_plasma-sdk build #124: STILL UNSTABLE in 15 min: http://kci.pangea.pub/job/yakkety_unstable_plasma-sdk/124/
[05:29] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_marble build #7: STILL FAILING in 17 min: http://kci.pangea.pub/job/yakkety_unstable_marble/7/
[05:40] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_discover build #6: STILL UNSTABLE in 12 min: http://kci.pangea.pub/job/yakkety_unstable_discover/6/
[05:40] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdeplasma-addons build #3: STILL FAILING in 13 min: http://kci.pangea.pub/job/xenial_unstable_kdeplasma-addons/3/
[05:51] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdepim-addons build #74: STILL FAILING in 39 sec: http://kci.pangea.pub/job/xenial_unstable_kdepim-addons/74/
[05:51] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdepim-addons build #7: STILL FAILING in 43 sec: http://kci.pangea.pub/job/yakkety_unstable_kdepim-addons/7/
[05:57] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdepim-addons build #75: STILL FAILING in 37 sec: http://kci.pangea.pub/job/xenial_unstable_kdepim-addons/75/
[05:57] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_marble build #8: STILL FAILING in 22 min: http://kci.pangea.pub/job/yakkety_unstable_marble/8/
[05:57] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdepim-addons build #8: STILL FAILING in 41 sec: http://kci.pangea.pub/job/yakkety_unstable_kdepim-addons/8/
[05:57] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdeplasma-addons build #4: STILL FAILING in 11 min: http://kci.pangea.pub/job/xenial_unstable_kdeplasma-addons/4/
[06:03] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdeplasma-addons build #5: STILL FAILING in 12 min: http://kci.pangea.pub/job/yakkety_unstable_kdeplasma-addons/5/
[06:21] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdeplasma-addons build #6: STILL FAILING in 13 min: http://kci.pangea.pub/job/yakkety_unstable_kdeplasma-addons/6/
[06:23] <yofel> tsimonq2: dunno, as I said, I don't have time for afternoon meetings before friday
[06:37] <yofel> ovidiuflorin: if you open the URL for the package task, i.e. https://bugs.launchpad.net/ubuntu/+source/network-manager-vpnc/+bug/1297849 then there's a "Nominate for series" link. There select yakkety for the task
[06:37] <yofel> do that for every package you think is relevant, then ask a dev to accept them
[06:38] <acheronuk> yofel: not here? do you need to be a member of one of the bug teams? either direct or through kubuntu-dev?
[06:39] <yofel> well, I can accept them, but I'm not really sure if that's because I'm in ubuntu-dev or ubuntu-bug-control. It's one of those IIRC
[06:39] <yofel> although ubuntu-dev also implies ubuntu-bug-control
[06:39] <yofel> which is why I said dev
[06:40] <acheronuk> "Only the bug supervisor for a project can nominate a bug or blueprint as affecting a particular series with the Nominate for release link. "
[06:41] <yofel> oh, when did they do that
[06:41] <acheronuk> https://help.launchpad.net/Projects/SeriesMilestonesReleases
[06:41] <yofel> ovidiuflorin: ok, so just tell me what you think is affected
[06:41] <acheronuk> dunno, but I looked the other day for the SRU upgrade bug and found I could not do it
[06:42] <yofel> probably from back when they decided to lock down some bug stats etc.
 yofel, I'm not sure what's affected
 I just get the same-ish log messages
 basically the effect is: I connect to the VPN but there is no DNS resolving
[07:53] <yofel> well, I know even less about the issue, but if you could comment that you're able to reproduce the issue in yakkety for e.g. vpnc, then I'm willing to add a yakkety bug task for vpnc
[07:53] <yofel> but adding random bug tasks without actually verifying that the bug actually happens
 resolv.conf gets updated then reverted....
[07:53] <yofel> ... is a no-go in general
 I've added the comment
 but not much detail in it
 I'm not sure what is relevan
 I'll looke more into this tomorrow
 if I work remotely
[07:56] <yofel> do you remember the connection type? vpnc/openconnect/..
 openvpn
[07:57] <yofel> ok, then I'll add a task for that at least
 what does a task mean?
[07:58] <yofel> oh great, that added them for all packages *-.-
 ... :(
[07:59] <KurousagiMK2> The workaround https://ubuntuforums.org/showthread.php?t=2340042&p=13558035#post13558035
[07:59]  * yofel removes the ones for the fixed packages
[07:59] <yofel> "task" is how we refer to... one line in the bug status block at the top
 KurousagiMK2 that's for vpnc
[09:25] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kwin build #9: STILL FAILING in 13 min: http://kci.pangea.pub/job/yakkety_unstable_kwin/9/
[09:26] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kwin build #9: STILL FAILING in 15 min: http://kci.pangea.pub/job/xenial_unstable_kwin/9/
[09:44] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kwin build #10: STILL FAILING in 14 min: http://kci.pangea.pub/job/yakkety_unstable_kwin/10/
[09:46] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kwin build #10: STILL FAILING in 15 min: http://kci.pangea.pub/job/xenial_unstable_kwin/10/
[10:57] <acheronuk> clivejo @Santa et al : do you think this fix from plasma 5.8.1 is potentially backportable to plasma 5.7.5?
[10:59] <acheronuk> this I mean https://phabricator.kde.org/D3006
[11:32] <santa_> good morning everyone
[11:32] <acheronuk> hi santa_ :)
[11:33] <santa_> acheronuk: I was thinking in rebuilding everything for xenial, move it to the ppa and work on framewworks and new plasma for zesty
[11:34] <santa_> s/in/about/
[11:35] <santa_> * move it to the ppa ~ move it to the backports ppa
[11:35] <santa_> (like simon asked us a few days ago)
[11:36] <acheronuk> yeah, or backports-landing anyway.
[11:40] <santa_> acheronuk: ok, so do you mind if I start with frameworks? my idea is merging kubuntu_yakkety_archive into kubuntu_xenial_backports and rebuild everything in the fw staging ppa
[11:40] <santa_> any objections?
[11:41] <acheronuk> clive said yesterday I think that he wanted to start staging stuff. not sure what though
[11:41] <santa_> clivejo: ↑
 +1
 No objections from me
[11:42] <acheronuk> not from me. I think that needs to be done. I think Simon enabled all the architectures on the staging ppa, which may be a unnecessary while staging xenial backports?
[11:43] <yofel> someone might want to look at lp 1634125
 I can handle that later if nobody else does.
[11:46] <santa_> yofel: oh, now that you mention it we also have a pending bug fix for a frameworks package
[11:47] <santa_> ktexteditor/kubuntu_yakkety_archive branch
[11:47] <santa_> so if someone can upload that one it would be nice
[11:48] <yofel> I don't see anything
[11:57] <jimarvan> hey peeps :)
[11:57] <santa_> hi jimarvan
[11:58] <santa_> yofel: sorry, just pushed the commit in question now. I tought I alredy did that
[11:59] <jimarvan> hey santa_ :)
[12:00] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_ktexteditor build #95: FAILURE in 1 min 27 sec: http://kci.pangea.pub/job/yakkety_unstable_ktexteditor/95/
[12:00] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_ktexteditor build #233: FAILURE in 1 min 37 sec: http://kci.pangea.pub/job/xenial_unstable_ktexteditor/233/
[12:01] <yofel> I updated the bug, but upload will have to wait until evening, if clive isn't faster
[12:04] <santa_> np
[12:06] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_ktexteditor build #234: STILL FAILING in 1 min 3 sec: http://kci.pangea.pub/job/xenial_unstable_ktexteditor/234/
[12:06] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_ktexteditor build #96: STILL FAILING in 1 min 31 sec: http://kci.pangea.pub/job/yakkety_unstable_ktexteditor/96/
[12:51] <soee> ahoneybun: http://www.feralinteractive.com/en/games/madmax/?page=setting
[12:51] <soee> out now on mac and linux :)
[12:53] <BluesKaj> Hey folks
[12:54] <soee> hiho BluesKaj
[12:54] <BluesKaj> Hi soee
[13:18] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kwin build #11: STILL FAILING in 4 min 59 sec: http://kci.pangea.pub/job/yakkety_unstable_kwin/11/
[13:19] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kwin build #11: ABORTED in 5 min 39 sec: http://kci.pangea.pub/job/xenial_unstable_kwin/11/
[13:29] <clivejo> LP 1632848
[13:36] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kwin build #12: STILL FAILING in 18 min: http://kci.pangea.pub/job/yakkety_unstable_kwin/12/
[13:38] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kwin build #12: STILL FAILING in 18 min: http://kci.pangea.pub/job/xenial_unstable_kwin/12/
[13:40]  * mamarley upgraded to Zesty. O.o
[13:46]  * acheronuk makes the mouse jump
[13:50] <clivejo> !testers | Please test the patched package for LP 1632848
[13:50] <clivejo> grrr that needs changed!
[13:51] <clivejo> could do with a package testers and +1 testers
[14:00] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kwin build #13: STILL FAILING in 18 min: http://kci.pangea.pub/job/yakkety_unstable_kwin/13/
[14:01] <clivejo> tsdgeos: ping
[14:01] <tsdgeos> clivejo: hi
[14:02] <clivejo> howdy, regarding LP 1632848, would you mind testing that package in my PPA?
[14:02] <clivejo> I know the version number is wrong, but the patch should work
[14:03] <clivejo> for SRU needs to be ktexteditor (5.26.0-0ubuntu1.1
[14:03] <acheronuk> lol. I was just about to point that out.
[14:04] <clivejo> :P
[14:04] <tsdgeos> clivejo: link to the deb file?
[14:05] <clivejo> do you know which binary package it changes?
[14:05] <clivejo> I just added my PPA
[14:05] <clivejo> and done an upgrade
[14:06] <clivejo> it pulled in ktexteditor-data ktexteditor-katepart libkf5texteditor5 libkf5texteditor5-libjs-underscore
[14:06] <acheronuk> the debs? https://launchpad.net/~clivejo/+archive/ubuntu/yakkety/+build/11047602
[14:06] <tsdgeos> ok
[14:07] <clivejo> remember to remove and ppa purge my PPA after the test
[14:07] <clivejo> I upload a lot of testing stuff there
[14:07] <clivejo> and you dont want it!
[14:09] <tsdgeos> i like how stupid dpkg has a force-all switch
[14:09] <tsdgeos> that doesn't forces shit
[14:10] <tsdgeos> clivejo: yes, fixes it
[14:10] <clivejo> acheronuk: did you test it?
[14:10] <Quintasan> shadeslayer: Happy birthday!
[14:10] <shadeslayer> thank you :)
[14:11] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kwin build #13: STILL FAILING in 28 min: http://kci.pangea.pub/job/xenial_unstable_kwin/13/
[14:11] <clivejo> tsdgeos: can you add a comment as the orginal bug reporter that this package fixes it please?
[14:16] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_ktexteditor build #235: STILL FAILING in 48 sec: http://kci.pangea.pub/job/xenial_unstable_ktexteditor/235/
[14:16] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_ktexteditor build #97: STILL FAILING in 51 sec: http://kci.pangea.pub/job/yakkety_unstable_ktexteditor/97/
[14:16] <tsdgeos> clivejo: done, when do we get those packages in yakkety updates?
[14:16] <clivejo> Im trying to get them uploaded
 Happy birthday shadeslayer
[14:17] <clivejo> Im not very comfortable with doing SRU at the moment and it takes me a long time
[14:18] <clivejo> the problem is that the update needs to go to zesty first we havent proprly got our infrastructure configured just yet
[14:19] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kwin build #14: STILL FAILING in 16 min: http://kci.pangea.pub/job/yakkety_unstable_kwin/14/
[14:19] <BluesKaj> BBL
[14:21] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_ktexteditor build #236: STILL FAILING in 45 sec: http://kci.pangea.pub/job/xenial_unstable_ktexteditor/236/
[14:21] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_ktexteditor build #98: STILL FAILING in 48 sec: http://kci.pangea.pub/job/yakkety_unstable_ktexteditor/98/
[14:31] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kwin build #14: STILL FAILING in 20 min: http://kci.pangea.pub/job/xenial_unstable_kwin/14/
 the problem is that the update needs to go to zesty first we havent proprly got our infrastructure configured just yet
[14:40] <santa_> I don't think so
[14:40] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kwin build #15: STILL FAILING in 21 min: http://kci.pangea.pub/job/yakkety_unstable_kwin/15/
[14:40] <santa_> clivejo: what is the problem exactly?
[14:41] <clivejo> not a problem, just not great situation to be in when Im learning the ropes
[14:41] <clivejo> yakkety is an SRU so the version should be 1.1?
[14:42] <acheronuk> yes
[14:42] <clivejo> and I would like to have zesty_archive branches
[14:46] -kubuntu-ci:#kubuntu-devel- Project merger_ktexteditor build #763: FAILURE in 11 sec: http://kci.pangea.pub/job/merger_ktexteditor/763/
[14:51]  * acheronuk yawns
[14:51] <santa_> clivejo: if the version should be 1.1 would you mind to wait a bit so I can provide you a gbp-sru ?
[14:52] <santa_> nvm
[14:52] <santa_> I think the current gbp-archive should be enough
[14:52] <santa_> with "-d yakkety"
[14:54] <acheronuk> clivejo have you been using gpg-archive? or some other?
[14:54] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kwin build #15: STILL FAILING in 17 min: http://kci.pangea.pub/job/xenial_unstable_kwin/15/
[14:54] <santa_> gbp
[14:54] <acheronuk> lol. yes
[14:56] <acheronuk> someone on kubuntu forums spent pages trying to work out why kpgp wouldn't install saying the package didn't exist. when it should be kgpg!
[14:57] <acheronuk> so easy to mistype with similar acronyms
[15:09] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kwin build #16: STILL FAILING in 23 min: http://kci.pangea.pub/job/yakkety_unstable_kwin/16/
[15:30] <santa_> clivejo, acheronuk: just fyi I pushed some stuff to KA this week; a few changes to prepare for zesty and I also added a feature to gbp-ppa so you don't have to type "-s <number>", the number is calculated from launchpad, yet you can override the number providing "-s <number>" (that's useful if, for instance, you are not uploadng to your own ppas, not our staging ones)
[15:31] <acheronuk> santa_: I was just looking at those changes a few mins ago :)
[15:32] <santa_> ok. let me know if I broke something so we can fix it
[15:36] <jimarvan> :D
[16:48] <clivejo> tsimonq2: can you SHOW us how to get a full list of packages from LP git repo
[16:51] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kwin build #16: NOW UNSTABLE in 27 min: http://kci.pangea.pub/job/xenial_unstable_kwin/16/
[17:00] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kwin build #17: NOW UNSTABLE in 36 min: http://kci.pangea.pub/job/yakkety_unstable_kwin/17/
[17:02] <acheronuk> clivejo: wget -q -O - https://code.launchpad.net/~kubuntu-packagers/+git | grep kubuntu-packaging | awk -v FS="(+git/|</a>)" '{print $3}'
[17:02] <acheronuk> and repeat for each page on the repo?
[17:18] <clivejo> cool
[17:18] <clivejo> so can you find out of that entire list, how many of those packages have yakkety_archive branches?
[17:24] <santa_> why do you want to do that?
[17:25] <clivejo> because I think there are some that dont, and want to look at them
 Hai
 I see Rik answered?
[17:26] <clivejo> tsimonq2: is that how you did it?
[17:26] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kwin build #17: STILL UNSTABLE in 34 min: http://kci.pangea.pub/job/xenial_unstable_kwin/17/
 Nope
[17:27] <santa_> clivejo: from which package set? frameworks, plasma, applications or others?
 ./gitcloneall
 (with some arguments l
[17:27] <clivejo> others
[17:27] <santa_> ah, ok
[17:27] <clivejo> git clone all is only fw, plasma and apps
[17:27] <clivejo> I want all of them
[17:27] <santa_> yes
[17:28] <clivejo> gimme all your packages!
 sudo apt install santa
 XD
[17:28] <santa_> but what's the problem you want to solve exactly?
[17:29] <clivejo> just asking questions!
[17:30] <santa_> at some point we could extend git-clone-all so we could make git-clone-all -r other
[17:30] <clivejo> dunno if that would help, its only for rare occasions like we have now
[17:30] <santa_> however automatin the extra packages is a tough thing to do since it's a very heterogenours world
[17:31] <santa_> so, again, what are you trying to do? (if you are tryng to do something)
 So for sure we'll get QtWebEngine stuffs in the archive sometime around December and January. It'll be included with the 5.7.1 upload apparently.
[17:32] <clivejo> I want to create zesty_archive branches
[17:33] <clivejo> but I want to also see out of our entire package set, which ones are missing a yakkety one
[17:33] <clivejo> if any
[17:33] <clivejo> as the zesty branches will be from yakkety_archive
[17:34] <santa_> well, I would handle plasma frameworks and apps with git-clone-all/do-all
[17:34] <santa_> and the rest manually
 What's do-all?
[17:34] <santa_> because the work done in the other packages is manual anyway
 Example syntax?
[17:36] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kwin build #18: STILL UNSTABLE in 35 min: http://kci.pangea.pub/job/yakkety_unstable_kwin/18/
[17:38] <acheronuk> clivejo: git ls-remote -h kubuntu:kwin
[17:38] <clivejo> why is kwin going round in circles?
[17:38] <acheronuk> huh?
[17:39] <clivejo> KCI seems to be building kwin a lot
[17:40] <acheronuk> clivejo: doing soname bump on that in stages. so several commits and wait for result
[17:40] <clivejo> ah
 Oh you are?
 Cool!
 I want to see how you did it when you're done. :l
 *:)
[17:41] <acheronuk> and correcting some stupid typo where I forgot to put NOCI
 :P
[17:42] <acheronuk> then KCI does retries as well...
 This weekend I think I might get a local KCI setup good to go
 So I can rewrite in Python ;)
 But doing that might also require me to set up a mock Launchpad install
 But either way, whatever I do to get it building, I hope to do a lot of work
 Including *possibly* getting Stable builds working again
[17:54] <yofel> I seriously doubt you'll need a launchpad install? you might need a mock lplib though, just for the few calls that are being done
[17:54] <clivejo> you'll have that all ready for Monday morning I trust?
[17:55] <yofel> acheronuk: btw. manage-repo-webhooks has code that loops through *all* repositories, so you could just hack that with a print to get all relevant repo names
[17:55] <yofel> that script is in kubuntu-dev-tools
[17:56] <acheronuk> ^^ aha. thought there was bound to be a cleverer way :)
[17:57] <clivejo> I though that was Simon was told to use last time he batch edited the VCS?
[17:58] <yofel> althoug the changes itself I would do with do-all
 yofel: Yeah, that was my concern, although my thought is that I can mess with getting my own archive set up and tweaking everything for that. Or creating a PPA and asking for space to be allocated then tweaking the API calls.
 clivejo: Hopefully. ;)
[18:02] <yofel> well, for dev purposes a normal PPA will probably suffice, I wouldn't develop on production scale ^^
[18:03] <yofel> or you want to *also* look into our own build system setup? ^^
[18:04] <clivejo> yofel: how much rubish do you think is in unstable PPA?
[18:04] <yofel> not much I think, maybe some qt packages you don't need and a couple things that aren't CId anymore
[18:05] <yofel> you can definitely remove anything that LP marks as having a higher version
 yofel: I want to fully replicate our existing CI with the exception of different builders and different PPAs.
 That's it.
 I want all the same jobs and everything.
 I even want to try to run a nightly. 😂
[18:07] <yofel> uhm, I'm not quite sure why you would want to do that, but feel free to. We can give you a backup of the CI folder on master - except for the keys
[18:07] <yofel> which reminds me of backups...
 OK fair enough
 YES PLEASE 😜
[18:08] <yofel> maybe a combination of rsync to linode & rdiff-backup
 Yeah the nightly is painful enough, have it run at the same time as that. :P
 OK I'm off o/
 are we having an informal planning meeting tommorow evening or over the weekend?
[19:36] <valorie> acheronuk: I saw this yesterday in #ubuntu-release and wondered what it means - [22:21] <slangasek> acheronuk: there are now a number of Kubuntu packages listed on https://merges.ubuntu.com/universe.html that I'm TIL on; is there a better plan for getting these up-to-date wrt Debian unstable than for me to merge them via MoM?
[19:37] <mparillo> And on the topic of other channels, in Neon,  <tittiatcoke> Calibre comes from Ubuntu 16.04 and it was compiled against a lower Qt5 version.
[19:37] <mparillo> If calibre is important software, then I hope we have somebody who knows how to test it if we upgrade Qt for 16.04 via Kubuntu-Backports.
[19:38] <valorie> we don't package calibre, but that's a good point
[19:38] <valorie> I usually get that from the calibre website, sadly
[19:39] <valorie> someone who wants to become a MotU could package it though......
[19:42] <clivejo> good luck someone
[19:42] <clivejo> you'll need it
[20:12] <clivejo> what are the resource available on KCI master?
[20:14] <yofel> as in?
[20:15] <clivejo> RAM, Disk, CPU
[20:15] <yofel> run top? ^^
[20:15] <clivejo> sorry resources
[20:15] <yofel> or look at zabbix
[20:15] <clivejo> do you know off hand?
[20:16] <yofel> just checked, 4G RAM, 10G SWAP, 2 CPU, 493GB 87% used
[20:17] <yofel> where the hell is that disk usage from o.O
[20:17] <clivejo> indeed, I just gulped
[20:18] <yofel> well, 66G free, so not too worrying, still weird
[20:19] <yofel> looking at zabbix, the restore on the 6th/7th caused most of that
[20:19] <yofel> before that the usage was more like 45%
[20:19] <clivejo> can I have a link?
[20:20] <valorie> archive is about to be unfrozen btw
[20:20] <clivejo> that box is a VM isnt it?
[20:21] <yofel> I think it's an EC2 instance
[20:21] <yofel> hm, or no, the IP looks proxied, so something else
[20:24] <clivejo> acheronuk: can you test the version in proposed please and comment - LP 1632848
[20:24] <yofel> clivejo: PM for link
[20:24] <clivejo> I dont see Albert in the channel list
[20:25] <yofel> he's not always on, and if then as tsdgeos or so
[20:25] <valorie> tsgeos usually quits when he goes to bed
[20:27] <valorie> tsdgeos I mean
[20:29] <santa_> FYI I have just fixed a bug with the KA automatic calculation of ~ppaX numbers feature I have just implemented today
[21:12] <clivejo> valorie: was tsdgeos at QtCon?
[21:14] <valorie> yes, I'm sure you met Albert?
[21:15] <valorie> I think he left Wed. from Akademy, but yes, he is the e.V. board member whose term just ended
[21:21] <clivejo> I did?
[21:24] <valorie> well, I did
[21:24] <valorie> unsure if I introduced you
[21:24] <clivejo> probably not, you so rude!
[22:11] <valorie> gosh someone upgraded from 16.04 to 16.10 and now has a non-working lightdm
[22:12] <valorie> he wrote to me personally, kub-devel and kub-users
[22:12] <valorie> someone who knows more than me should give him some advice!
 well SDDM is what he/she should be using
 sudo dpkg-reconfigure sddm
 I believe
[22:25] <valorie> oh gosh, what is the best way to get the correct nvidia driver?
[22:25] <valorie> sudo driver manager something....
 well the driver manager app does not work without another command
[22:28] <valorie> hmmm, there is nvidia-settings - Tool for configuring the NVIDIA graphics driver
[22:29] <valorie> I'll leave that for others I guess
[22:29] <valorie> I don't mess with mine


[06:31] <mitya57> I just committed yet another Debian merge for qt4-x11. If someone wants it for Utopic, feel free to upload.
[06:31] <mitya57> http://bazaar.launchpad.net/~kubuntu-packagers/kubuntu-packaging/qt/revision/395#debian/changelog
[07:26] <lordievader> Good morning.
[07:30] <soee> hiho lordievader
[07:31] <lordievader> Hey soee, how are you doing?
[07:32] <soee> lordievader: doing good :) its friday, nice weather here in Poland :) you ?
[07:33] <lordievader> Doing good too, seems to become nice weather here too :)
[10:37] <BluesKaj> 'Morning folks
[11:11] <ScottK> mitya57: Did you fix/merge xmlpatterns for Qt5 as well?
[11:32] <Riddell> nazdar from Akademy
[16:44] <mitya57> ScottK: what's wrong with xmlpatterns?
[16:45] <ScottK> mitya57: There was a discussion about it on #debian-qt-kde yesterday (and an upload in Debian, IIR).  I had (wrongly I gather) assumed that's what prompted you to do the qt4-x11 merge.
[16:45] <ScottK> I don't recall the details.
[16:46] <mitya57> ah, stack overflow fix, I see
[16:47] <mitya57> will cherry-pick that when I have time
[16:47] <mitya57> though we first need to remove 5.3.1 from utopic-proposed
[17:22] <kdeuser56> latest utopic-plasma5 iso: when attempting to open partition manager it says: KDEInit could not launch ". Could not open library '/usr/lib/x86_64-linux-gnu/libkdeinit5_:(/usr/lib/x86_64-linux-gnu/libkdeinit5_.so: cannot open shared object file: No such file or directory)
[21:53]  * ScottK wonders if 3 minutes from bug filed to wontfix is a record.
[22:15]  * Riddell blogs https://blogs.kde.org/2014/09/05/akademy-day-0-photo-blog