[00:24] <grex23> yo
[00:25] <MenZa> Huh.
[01:03] <Pricey> Leaving that on bazhang?
[01:03] <bazhang> Pricey, going to PM
[01:04] <Pricey> Offline.
[01:04] <bazhang> yep
[01:30] <MenZa> I'll speak to xeer.
[01:30] <MenZa> (in PM)
[01:32] <MenZa> Unresponsive.
[01:37] <MenZa> ubottu: tell xeer about coc
[01:37] <MenZa> ubottu: tell xeer about guidelines
[01:38] <MenZa> He's responding, but he's not being very accepting of what I'm telling him.
[01:38] <bazhang> quelle surprise
[01:39] <MenZa> Indeed.
[01:39] <MenZa> I'd like some advice for what to do here, bazhang
[01:39] <MenZa> Erm, well
[01:39] <MenZa> Let's see what happens in the future
[01:39] <MenZa> He
[01:39] <bazhang> not sure MenZa
[01:40] <MenZa> He's agreed to abide by the CoC and the Guidelines in the future
[01:40] <MenZa> So we'll see what happens
[01:40] <bazhang> seems like it got hot quite quickly
[01:40] <MenZa> If I see digitalaxis around, I'll make sure to grab him to tell him it's been resolved.
[01:40] <MenZa> I'm not too happy to see a user have an issue, wait for a long time, then quit before it was even resolved.
[01:40] <MenZa> (with another user, that is)
[01:40] <MenZa> It makes me a sad panda :(
[01:41] <bazhang> heh
[01:41] <MenZa> The amount of ops around these hours has been far too scarce lately.
[01:41]  * MenZa hopes it gets better.
[01:41] <bazhang> it was resolved though
[01:41] <MenZa> Aye.
[01:41] <bazhang> yep. normally I am working at this time
[01:41] <MenZa> I still think I'd be left with a sense of "the ops don't care" if I'd been digitalaxis.
[01:42] <MenZa> bazhang: Did you see my entry on ubuntu-irc@lists?
[01:42] <bazhang> MenZa, yep
[01:42] <MenZa> good good
[01:42] <MenZa> I had issues /last/ night as well.
[01:42] <bazhang> whoa
[01:43] <MenZa> Yeah.
[03:35] <elky> oh no it's not
[03:36] <maco> thats alias jfgi
[03:36] <elky> !google
[03:36] <maco> or at least, thats where i think itd go
[03:36] <elky> !jfgi
[03:36] <elky> decide which lmgtfy should go
[03:37] <maco> id say the second
[03:37] <bazhang> yep
[03:37] <maco> since the first is "youre trying to be helpful but thats not how we do it" and the second is "you're being a sarcastic jerkwad"
[04:07] <elky> !-jfgi
[04:08] <elky> !lmgtfy is <alias> noob
[04:08] <elky> !lmgtfy
[05:39] <MenZa> ubottu: whoami
[05:39] <MenZa> @whoami
[05:40] <MenZa> Hmm.
[09:05] <MenZa> !empathy
[09:07] <MenZa> !no, !empathy <reply> Empathy is the default instant messaging and video client for GNOME. Since Karmic, it has been the default client in Ubuntu (replacing Pidgin).
[09:07] <MenZa> keke.
[09:11] <tsimpson> !no, !empathy <reply> Empathy is the default instant messaging and video client for GNOME. Since Karmic, it has been the default client in Ubuntu (replacing Pidgin).
[09:11] <tsimpson> !no, !empathy is <reply> Empathy is the default instant messaging and video client for GNOME. Since Karmic, it has been the default client in Ubuntu (replacing Pidgin).
[09:12] <tsimpson> !no, empathy is <reply> Empathy is the default instant messaging and video client for GNOME. Since Karmic, it has been the default client in Ubuntu (replacing Pidgin).
[09:12]  * tsimpson kick starts brain
[09:12] <tsimpson> !empathy
[09:30]  * MenZa nods at tsimpson
[09:31] <MenZa> jussi01: Same issues the past two nights :(
[09:31] <jussi01> MenZa: huh?
[09:31] <MenZa> jussi01: My last mailing list thread.
[09:31] <MenZa> Noone was available for a while.
[09:32] <jussi01> MenZa: yes, we are putting measures in place to deal with it.
[09:32] <MenZa> \o/ jussi01
[09:32] <MenZa> jussi01: I just thought I'd let you know; I wasn't criticising you for not dealing with it quick enough. It's perfectly cool you guys have some time to settle in first :)
[09:33] <jussi01> MenZa: its a matter of getting proceedural changes into place first.
[09:33] <MenZa> 'swhat I meant.
[10:31] <elky> MenZa, a word of advice: having a private word to people is less pressure than announcing to a mailing list.
[10:32] <MenZa> elky: I'm a very open-minded person. I don't necessarily imply it's the most terrible thing in the world if I ship off something to a mailing list. It was also to get second opinions on the issue.
[10:33] <elky> MenZa, it's not a terrible thing, but the public nature *does* put pressure on people
[10:34] <elky> just speaking from experience having been in several public governance roles
[10:34] <MenZa> elky: I'm sure you're familiar with Linus' Law---I think it applies in this case, too. I'm not calling the IRC Council out saying "these guys are doing a bad job, jeez" at all; I'm merely stating what I think is an issue, and ask for more opinions on them, and to allow for discussion of the matter.
[10:37] <MenZa> I've always been a big fan of openness, and I don't think it's a problem that people know these things. nor should it be for anyone, unless I'm specifically acusing them of something.
[10:37] <elky> MenZa, i'm saying that a heads up first is good manners and allows people to manage the pressures of such roles. i'm not saying don't mention it, i'm saying be considerate
[10:39] <MenZa> elky: I don't see why such an e-mail couldn't be considered a "heads up". It's perfectly okay for the IRC Council not to be aware of such a problem, considering most of them (from memory) aren't online at that point. the same pretty much goes for the previous IRC Council.
[10:39] <MenZa> I see a problem, I point it out, it's acknowledged and dealt with when such an action is required or possible to implement.
[10:40] <elky> MenZa, you're not giving the IRCC much credit if you think they're not aware of timezones that are not well covered. you're not giving them a heads up that you want to start a discussion by starting said discussion out of the blue.
[10:42] <MenZa> elky: I wouldn't tell any member of any council to remember what timezones their subordinates (for a lack of a better term) are in. Nor would I tell them to pull the entire weightload of the cart they're supposed to be responsible for.
[10:43] <elky> MenZa, the council is aware and was aware before your email. had you tried to give them a heads up, they likely would have told you so.
[10:44] <MenZa> elky: so much for the openness I've always been advocating. where was my opportunity to say I would be available at those times anyway for the period x to y?
[10:45] <MenZa> (in terms of conflict resolution, not +o flags)
[10:45] <MenZa> or other operators, for that sake
[10:45] <elky> MenZa, openness doesn't mean that things cannot be discussed privately evar or the world will implode.
[10:45] <elky> MenZa, openness does not nullify the concept of manners, forewarning or other courtesies.
[10:46] <elky> i should hope nobody within our community is subject to a presidential communications standard. not even Mark.
[10:47] <MenZa> elky: I don't disagree, but I still don't quite understand /how/ sending an e-mail to a mailing list could be considered uncourteous in any way.
[10:48] <gord> sending a mail to a mailing list makes it an "offical" "recorded" "thing", removes any sense of casualness
[10:49] <MenZa> gord: I think that's one way of perceiving it
[10:49] <elky> MenZa, depends what impression that mail gives. my response was pertinent to your claiming to not be putting pressure on the new IRCC and offering a suggestion as to how you could have avoided putting pressure on them
[10:49] <MenZa> What is this, ubuntu-irc-announce-secret-docs?
[10:49] <MenZa> elky: that's an interpretation
[10:49] <elky> since i'll guarantee that your mail *DID* put pressure on them.
[10:49] <MenZa> elky: it certainly wasn't my intention.
[10:49] <MenZa> as I also accounted for in a reply to jussi's mail
[10:49] <elky> and i'll guarantee that based on my experiences in said roles.
[10:50] <jussi01> I think elky is right to a point, and so is gord. It would have been better, IMHO, to first send a mail to the ircc list.
[10:50]  * elky knows she's right :P
[10:51] <MenZa> I haven't held such a role in any foss (or online) community before, but I have in real-life organisations. sending an e-mail pointing out a problem to our mailing list was never an issue for me, or anyone else involved.
[10:51] <elky> you've got no idea the weight that's been lifted this past week. not only here, but also for the national australian body which i've decided to take a year off standing for
[10:51] <MenZa> elky: I know how much work is involved in these things.
[10:53] <MenZa> and I'm not questioning the good work that's being done in any way; on the contrary, I appreciate it greatly
[10:54] <elky> MenZa, you've not demonstrated that understanding to me. you have demonstrated that your experiences differ greatly to mine, and my experiences include the IRCC.
[10:55] <MenZa> elky: what you're currently demonstrating is arrogance and a sense of superiority.
[10:55] <MenZa> can't we keep it civil?
[10:55] <MenZa> I understand your views, and I see they differ from mine.
[10:56] <MenZa> Just because I have a different perception of how community dynamics function, I can /understand/ your views.
[10:57] <MenZa> I don't want this to turn into a nasty argument or ruin our personal relationship though, so I'll drop it here
[10:57] <MenZa> elky: I'll consider my move differently next time and take this into account, however -- trust that.
[10:57] <MenZa> (this != our argument, but you and gord's shared views)
[10:57] <elky> MenZa, well, you've already called me arrogant and told me i have a sense of superiority for explaining a POV that you neglected to observe.
[10:58] <elky> so sorry, but you've already overstepped a line.
[10:59] <gord> guys, this is getting personal and counter-productive
[10:59] <MenZa> it is
[10:59] <MenZa> I apologise, elky
[10:59] <MenZa> genuinely. I did cross a line.
[10:59] <elky> yes, insults tend to do that to discussions. apology accepted.
[10:59] <MenZa> :)
[11:05] <jussi01> Im off, laters.
[11:05] <tsimpson> see you later \o
[11:05] <bazhang> bye
[11:06] <MenZa> <o jussi01
[11:06] <MenZa> s/fail/nofail
[11:42] <nalioth> MenZa: #ubuntu-irc-council exists for a reason
[11:43] <MenZa> nalioth: My immediate comment would be that I might want other opinions on it than those of the IRCC, but I really don't want to do this all over again :)
[13:34] <bazhang> gp trolling multiple channels?
[14:39] <bazhang> bittwist appears to be running two bots in #ubuntu ragebot and wirebot, all are offline now and he/she has not responded to me
[14:40] <bazhang> err prior to going offline
[17:20] <h00k> ...wrong button, apologies
[20:23] <LimCore> hi, what is that:  #ubuntu You're banned from that channel You're banned from that channel
[20:25] <Flannel> LimCore: You're banned from #ubuntu
[20:26] <LimCore> Flannel: when / what / why?
[20:29] <Flannel> LimCore: The 21st of this month (five or so days ago)
[20:30] <LimCore> and how that happened? past the log
[20:33] <LimCore> This is all I said on Ubuntu in last week according to my log: <LimCore>  anyone did setup a VPN on Ubuntu client + Ubuntu server? <LimCore>  TopCat: hwinfo is a gui? <LimCore>  TopCat: last time I usaed mac os, it forced me to watch stupid commercialls on the DVD I bought (WTF?) <LimCore>  ok technically it didnt forced me to *watch* it,  but it force computer to display it with no option to skip   <LimCore>  Good job ubuntu
[20:33] <LimCore> so what is going on? :)
[20:39] <LimCore> can someone tell me why I am now banned?
[20:40] <LimCore> Flannel: based on that paste, do you know why I am banned?
[20:44] <Flannel> LimCore: No, I'm looking, but don't see anything.  There's probably some information missing or something.
[20:45] <LimCore> who banned me then?
[20:46] <LimCore> perhaps saying somewhere ELSE, not in #ubuntu*, that I do not like ubuntu or something about ubutnu - can give a ban in #ubuntu ?
[20:46] <LimCore> altohught that seems to be fundamentally wrong and very Chinese like ;)  Can this be the case?
[20:46] <Flannel> LimCore: I'm not going to speculate
[20:47] <LimCore> is there a rule that would make above expression of opinions a bannable offence?
[20:48] <Flannel> LimCore: Why?  Is that what you were doing on the 21st?  Would you like to fill us in?
[20:49] <LimCore> No I asked now just a question, about rules
[20:51] <LimCore> apparently noone here now to respond to this question? Ok I can wait.
[20:51] <Flannel> Again, I'm not going to speculate about this instance.  However, making statements regarding Ubuntu is your business, not ours.  There are always exceptions, but you're free to opine as long as it's within whatever channels guidelines.
[20:51] <mneptok> @login
[20:51] <LimCore> Flannel: can you check who banned me? Then I can address this issue to a person that probably knows the reason behind this
[20:52] <LimCore> ok I bet ikonia or mneptok
[20:53] <mneptok> why do you think i banned you?
[20:54] <LimCore> mneptok: dunno. I dont see any reason for me to be now banned in #ubuntu. So I must guess, afair only you and/or ikonia ever banned me in #ubuntu*
[20:55] <LimCore> actually I do hope this is some mistake
[20:55] <mneptok> well, your memory is faulty. i never banned you.
[20:55] <LimCore> mneptok: who set my ban in #ubuntu-offtopic?
[20:55] <mneptok> baz_hang did. then removed the ban. elk_y overruled that decision, based on your continued behavior. ikonia then banned you when you dodged the ban.
[20:55] <mneptok> (in #u)
[20:56] <LimCore> you now say about offtopic?
[20:56] <LimCore> well offtopic is not important. What about main channel?
[20:56] <mneptok> i was speaking about the main channel
[20:56] <Flannel> I'm not sure I see a point to this discussion anyway
[20:57] <LimCore> actually ikonia unbanned me around 18th or so
[20:57] <Flannel> LimCore: Nov 24th
[20:57] <LimCore> ok, who gaved me the most recent ban and why?
[20:58] <Flannel> LimCore: We don't know why, that's already been established.
[20:58] <mneptok> 2008-11-11T12:21:35 *** LimCore (LimCore!n=rafal@unaffiliated/limcore) has left #ubuntu (requested by elkbuntu: "Bazhang has been overruled. Your continued misbehaviour is tiring and you *definately* already know better. You are being banned indefinately.")
[20:58] <Flannel> LimCore: I can't make up a reason, but given your history, I don't think it was without cause.
[20:59] <LimCore> ok that was a year ago
[20:59] <LimCore> and recently, indeed on Nov24 (2009) I was unbanned. Now I am banned again
[21:00] <mneptok> the ban may have been removed to free space in the banlist.
[21:00] <mneptok> and yes, it was a year ago. but it says "you are banned indefinitely"
[21:00] <LimCore> right, and then ikonia removed it
[21:00] <mneptok> the ban may have been removed to free space in the banlist. (x2)
[21:01] <Flannel> mneptok: No, the ban was not removed accidentally.
[21:01] <LimCore> it was removed on purpose
[21:01] <LimCore> as I was pm'ed by ikonia
[21:01] <LimCore> since that time and now I did nothing "wrong", I said like 5 lines in #ubuntu and now I come back after xmas and I am banned again :o
[21:02] <Flannel> LimCore: Again, when ikonia returns we'll all know why you were banned on the 21st, until then, I don't think there's any reason for you to remain here.
[21:02] <mneptok> the current ban was set by ikonia. so i find it unlikely he deliberately unbanned you only to ban you again.
[21:02] <LimCore> mneptok: well ikonia PM'ed me saying I am being unbanned, I would paste the log but that is not polite. What you think I am making this up?
[21:03] <mneptok> i'm not going to second guess anyone. neither you nor ikonia.
[21:04] <mneptok> but since you say that i have banned you, and the bantracker never shows such an action, i have good reason to believe your memory may be faulty.
[21:04] <Flannel> LimCore: We've covered this.  You were unbanned on purpose (in November), and then banned again on purpose on the 21st.  At this point, I can't tell you why you were banned on the 21st.
[21:04] <LimCore> mneptok: you are some high rank admin or something right? do you mind me asking you again, should it be any grounds for ban in #ubuntu what given user personally thinks, or says OUTSIDE of #ubuntu* in relation to ubuntu? Yes, this is question about freedom of speach vs ubuntu IRC rules
[21:04] <Flannel> mneptok: Just drop it
[21:05] <mneptok> LimCore: i have no "rank" greater than any other ops'.
[21:05] <LimCore> mneptok: yes it was my mistake, sorry about saying that previously
[21:05] <mneptok> LimCore: as Flannel says, you need to talk to ikonia
[21:05] <LimCore> ok I will
[21:07] <Flannel> LimCore: If there's nothing else we can help you with, please part so we can perform business in this channel more effectively.  I'll make sure ikonia follows up, and you'll be kept in the loop.
[21:07] <LimCore> but since I did not did almost absolutelly nothing in #ubuntu , it could mean that after all actions outside #ubuntu lead to this; In such a case, this is quite dissapointing in relation to freedom of speach imho
[21:07] <jpds> wut.
[21:09] <Flannel> I'll take this opportunity to remind everyone to comment on your bans when they're not blatantly obvious (from the log with the ban in the BT)!
[21:25] <nalioth> i would like to take this opportunity to remind folks that bans are not "fire and forget", and that most bans shouldn't last more than 24h
[21:52] <ardchoille> there's a user in #ubunt by the nick of DrManhattan that is asking how to get unbanned in #ubuntu. I referred him here but it doesn't look like he's interested
[21:53] <ardchoille> I warned him about ban evasion also
[21:54] <Myrtti> Im on my mobile so my hands are tied due to technical restrictions
[21:56] <DrManhattan> so how long do bans usually last in #ubuntu?
[21:56] <DrManhattan> for using the evil f word
[21:57] <jpds> It seems you've dealt with MenZa and bazhang in the past.
[21:57] <jpds> You'll have to ask them.
[21:58] <DrManhattan> i guess i'll have to find out. Thanks.
[21:59] <jpds> ...


[04:10] <bshah> err... in kdeplasma-addons somehow scim stuffs are back
[04:11] <bshah> fixeroo-ing
[04:15] <bshah> done
[11:34] <clivejo> bshah: regarding kdeplasma-addons it had a broken merger due to previous changes
[11:34] <bshah> oh
[11:35] <bshah> clivejo: still broken? or fixed?
[11:35] <clivejo> I dont know
[11:35] <clivejo> Phil added those files to the install file
[11:35] <clivejo> http://anonscm.debian.org/cgit/pkg-kde/plasma/kdeplasma-addons.git/commit/?h=kubuntu_unstable&id=192a9daf4dec90a34391f79c5f4e6fc4f661923d
[11:36] <bshah> this should not be in _unstable for sure..
[11:36] <bshah> as in master it was removed
[11:36] <clivejo> how is it removed?
[11:37] <bshah> was moved to plasma-workspace
[11:37] <bshah> err..
[11:37] <bshah> plasma-desktop
[11:37] <bshah> clivejo: https://quickgit.kde.org/?p=kdeplasma-addons.git&a=commit&h=c24ceb9eaf11795b750118c68a479da3303de2bd
[11:52] <doko> sitter, Riddell: does kubuntu care about https://launchpad.net/ubuntu/+source/plasma-widget-mail/0.3.1-0ubuntu9 ?
[11:53] <Riddell> doko: no it's kdelibs4 stuff.  note neither me nor sitter are spending much time on kubuntu currently
[11:57] <doko> Riddell, yeah, I noticed :-/ is there still anybody caring?
[11:58] <Riddell> doko: you can try sgclark, yofel, clivejo
[12:00] <clivejo> doko: what the problem with it?
[12:00] <yofel> that's not even in the packageset, so we "technically" never even supported that?
[12:00] <yofel> would be one reason why we didn't know about it at least
[12:01] <doko> clivejo, well, see the link above
[12:01] <clivejo> ah FTBFS
[12:02] <doko> clivejo, yofel: there's also a problem with kde4libs (main), wanting some dozen new deps in main ... see http://people.canonical.com/~ubuntu-archive/component-mismatches-proposed.svg
[12:02] <yofel> bshah, clivejo: FWIW, I have no idea why I added scim back - maybe it got in during the debian merge..?
[12:02] <bshah> maybe...
[12:03] <clivejo> yofel: I dont know either, just got fed up with KCI blaming me for it
[12:03] <clivejo> I attempted to fix it
[12:03] <clivejo> the changelog is a mess
[12:04] <yofel> doko: hm, we'll look at that. That's far too much
[12:05] <clivejo> yofel: how come there is so much UNRELEASED stuff?
[12:05] <yofel> we never released it?
[12:05] <clivejo> should we not start getting it released?
[12:06] <yofel> sure, find someone that does it
[12:06] <yofel> I'll have time over the weekend - I hope
[12:07] <yofel> I wonder if we should tag frameworks as released so we can work on 5.19
[12:07] <yofel> I can generate packages from a tag..
[12:09] <yofel> doko: regarding time, there's at least 3 of us devs left that care. But with all of us doing this in our free time only and working on some 300 packages things are not exactly going well.
[12:09] <yofel> we should be able to reduce that amount next release - I hope...
[12:11] <yofel> doko: and regarding plasma-widget-mail.. kill it please
[12:11] <doko> yofel, please file a bug report to remove it, and subscribe ubuntu-archive
[12:12] <yofel> ack
[12:15] <clivejo> yofel: I dont think I can do anything more with apps, the remaining ones are beyond me.  Anything else I can do?
[12:15] <yofel> clivejo: set frameworks to released, tag it and start with 5.19
[12:16] <yofel> or maybe a rebuild test would be a good idea before that
[12:16] <yofel> I would have to do that anyway
[12:17] <clivejo> set framewords to release, and tag it, I dont know how to do that
[12:18] <yofel> ok, I'll do it
[12:19] <clivejo> if you walk me through it then Ill know for again :/
[12:19] <yofel> I can c&p what I do myself at least
[12:19] <yofel> oh right
[12:20] <clivejo> yeah please c&p
[12:20] <yofel> testing 14.04 would be a thing - if you can afford the bandwidth
[12:20] <yofel> in kubuntu-automation: /git-clone-all -t /tmp/fwrb/ -r frameworks
[12:21] <clivejo> 14.04?
[12:21] <davmor2> clivejo: 14.04.4 release is today
[12:23] <clivejo> davmor2: I’m dyslexic, numbers mean very little to me, especially remembering them!  What is at 14.04.4?
[12:24] <yofel> clivejo: http://iso.qa.ubuntu.com/qatracker/milestones/356/builds
[12:24] <davmor2> clivejo: the forth point release for trusty LTS
[12:24] <clivejo> ah
[12:25] <clivejo> I was wondering why the bot was announcing iso builds
[12:25] <clivejo> That explains it
[12:26] <davmor2> clivejo: and then next week 16.04 beta1 testing kicks in \o/
[12:26] <clivejo> Im afraid all of my boxes are on Senile
[12:27] <clivejo> yofel: fwrb = frame works re build?
[12:28] <yofel> right
[12:28] <clivejo> I wish I could watch you
[12:28] <clivejo> I bet you have tons of tricks to save time
[12:31] <yofel> not really... or at least nothing I conciously think about. I do a lot of on-the-fly shell scripting if anything
[12:34]  * highvoltage warps in
[12:35] <clivejo> no running in the hallways!
[12:35] <highvoltage> rules are there to be broken.
[12:35] <yofel> hence the warp? ^^
[12:37] <clivejo> yofel: are you still cloning?
[12:37] <yofel> just finished
[12:38] <yofel> next: cd /tmp/fwrb; do-all git checkout kubuntu_xenial_archive; do-all git-buildpackage-ppa -s 50
[12:38] <yofel> oh dang, failing on uscan
[12:38] <clivejo> highvoltage: davmor2 is looking for 14.04.4 testers :)
[12:38] <clivejo> cause 5.19 is out?
[12:38] <yofel> yeah, let me figure out an rsync command
[12:39] <clivejo> ppa50 ?
[12:39] <clivejo> or is that a special number?
[12:39] <highvoltage> davmor2: cool, I'm syncing kubuntu 14.04.4 20160217.1 and will give it a spin through its test cases
[12:39] <yofel> $something_that's_definitely_higher_than_anything_in_the_ppa
[12:39] <yofel> = 50
[12:39] <davmor2> highvoltage: awesome
[12:39] <clivejo> Id pick 99
[12:39] <clivejo> :P
[12:41] <clivejo> yofel: is that a bug in uscan, or designed that way for a reason?
[12:41] <yofel> I think there's a bug report in debian for that
[12:42] <yofel> IIRC
[12:43] <clivejo> oh, International Integrated Reporting Council (IIRC) CEO Paul Druckman plans to step down this year.
[12:44] <yofel> lol
[12:44] <clivejo> yofel: do you do a package list refresh?
[12:44] <yofel> no, the current one is 5.18, is it not?
[12:45]  * yofel stares at the screen while oxygen-icons downloads.......
[12:45] <clivejo> how did you so the rsync?
[12:46] <clivejo> do
[12:46] <Riddell> ovidiu-florin: ping?
[12:46] <clivejo> teach me master yoda
[12:48] <yofel> I'll tell you that once it's done
[12:48] <clivejo> :/
[12:49] <clivejo> ae you cheating? :P
[12:50] <yofel> rsync -avh ftpubuntu@depot.kde.org:/srv/ftp/pub/kde/stable/frameworks/5.18/ build-area; mv build-area/portingAids/* build-area/
[12:50] <yofel> also fetches the zips though if you're concerned about bandwidth (I'm not)
[12:50] <Riddell> how do I edit kubuntu.org? https://www-admin.kubuntu.org/ isn't working
[12:51] <yofel> Riddell: https://kubuntu.org/wp-admin - you'll need to be in the webadmin team on LP
[12:52] <yofel> meh, stupid uscan
[12:52] <clivejo> yofel: so you are just grabbing a copy of all the frameworks tarballs?
[12:52] <yofel> yes
[12:53] <clivejo> yofel: I think I staged those so should have them all locally
[12:53] <clivejo> for me Id just have to pull all changes from debian git
[12:54] <yofel> right, we'll I didn#t
[12:54] <clivejo> yofel: just thinking :P
[12:54] <yofel> uscan workaround: cd build-area; for file in *.xz; do ln -s $file ${file%-*}_5.18.0.orig.tar.xz; done; cd ..
[12:57] <clivejo> if I do a "do-all git pull"; would that work?
[12:58] <clivejo> eak qtbase5 has another update today
[13:00] <clivejo> yofel: Im gonna go for lunch, but post the commands so I can see the process
[13:00] <yofel> sure
[13:00] <clivejo> I think I see what you are doing
[13:02] <yofel> right now running git-buildpackage-ppa again
[13:02] <yofel> some tarballs need renames though, so I'll do that once the run completes and re-run it
[13:08] <BluesKaj> Hiyas all
[14:17] <highvoltage> is it normal for kubuntu to have the lock screen enabled in the live session?
[14:18] <yofel> I'm fairly certain that's a bug that we never fixed
[14:19] <BluesKaj> highvoltage, just turn itoff if it bothers you :-)
[14:44] <sgclark> morning
[15:02] <Riddell> highvoltage: can't be as bad as tanglu which I just discovered has lockscreen and blank password doesn't work
[15:02] <Riddell> ximion: how do I get round that? ^^
[15:08] <ximion> Riddell: on the live-cd?
[15:08] <ximion> blank password should work, but actually, the lockscreen should be disabled
[15:09] <ximion> are you using the development version (dasyatis, T4), or the stable version (chromodoris, T3)
[15:09] <ximion> in the latter case, try "live" as password
[15:09] <Riddell> ximion: stable, chromodoris, on virtualbox
[15:09] <Riddell> ximion: I see you don't have uefi support in the images, do you get many complaints about that?
[15:11] <ximion> yes, which is the reason why it's a high priority task for the next release: https://tracker.tanglu.org/T159
[15:11] <ximion> UEFI on the live-cd works well already, but both installers have problems installing Grub correctly
[15:13] <ximion> while most people are fine with disabling UEFI, it's annoying to those who are using it in e.g. multiboot scenarios, and it's generally not nice if it doesn't work - so T4 will have UEFI support, secure boot is a different beast though, and much more complicated to do it right
[16:02] <yofel> clivejo: so, rebuild done and things look fine. Now to the releasing:
[16:02] <yofel> do-all sed -e '1s/UNRELEASED/xenial/' -i debian/changelog
[16:02] <yofel> do-all git commit -am \"Release to xenial\"
[16:02] <yofel> do-all git-tagpkg
[16:02] <yofel> do-all git push origin --follow-tags
[16:02] <yofel> the sed stuff can probably be done with dch -r as well or so
[16:04] <clivejo> who broke kio!!
[16:04] <clivejo> yofel :P
[16:11] <yofel> I break all the things
[16:13] <clivejo> http://qa.kubuntu.co.uk/ppa-status/frameworks/build_status_5.18.0_xenial.html
[16:13] <clivejo> looks ok
[16:15] <yofel> clivejo: push done, you can start with 5.19 if you want
[16:15] <BluesKaj> wasn't able to boot into 16.04 after the last upgrade , the recovery kernel and the older kernels fail as well and the journalctl log wouldn't load in the root VT prompt
[16:16] <yofel> clivejo: I wonder if just merging in master for all repositories would make sense?
[16:16] <yofel> should be next to no diff now that we merged already?
[16:24] <clivejo> debian already have 5.19 done
[16:24] <clivejo> I merged kio as maxy done the new kio gui package better that I did
[16:28] <yofel> then this would be an application of "do-all git merge origin/master" ?
[16:28] <yofel> and figuring out the failures
[16:29] <yofel> + adding changelogs
[16:35] <clivejo> oh good lord
[16:37] <yofel> this would be the last time that we would touch frameworks at all, so it might be worth it
[16:37] <clivejo> but is it wise to mass merge them?
[16:38] <clivejo> I guess try it and see how many conflicts pop up!
[16:38] <yofel> well, you'll have to still read the diff
[16:38] <yofel> but you can also 'do-all git diff' that ^^
[16:39] <clivejo> you want me to do it :P
[16:39] <clivejo> give me enough rope and Ill hang myself!
[16:41] <yofel> as I said earlier, I love doing a lot of on the fly scripting :P
[16:41] <yofel> you can just do it by hand if you want
[16:41] <yofel> frameworks is small enough that it's still reasonable
[16:49] <clivejo> Ill look later, Im in a bit of a foul mood
[16:50] <clivejo> just got all four seasons in the space of an hour
[16:53] <yofel> be happy, here I had grey sky and light mist for 3 days straight now. Kind of depressing -.-
[16:56] <clivejo> I was happily enjoying the sunshine, sawing sticks then there was heavy rain, sleet snow and driving wind
[16:56] <clivejo> got soaked to my skin
[16:57] <yofel> mparillo: did you mark the iso testdays that you did as passed?
[16:59] <yofel> highvoltage: ^
[17:13] <mparillo> yofel: highvoltage: I did, but I did test on a prior release candidate, so my test is no longer on http://iso.qa.ubuntu.com/qatracker/milestones/356/builds
[17:13] <yofel> ok, thanks for testing
[17:13] <yofel> one of the other QA folks did some testing for the new images
[17:14] <mparillo> Basically, it was brief. VMware using their easy install. Tested maybe two apps on each after successful install.
[17:53] <yeehi> Trying to run Kubuntu Xenial in a VM using KVM. It reaches the desktop, but won't install.
[17:54] <yeehi> Error message: libvirt did not detect any UEFI/OVMF firmware image installed on the host
[18:32] <yeehi> Somebody solved the not installing problem mentioned earlier. Thank you! Xenial is now installing in KVM!
[18:48] <mparillo> yeehi: I thought this was the root cause of the Xenial install bug: https://bugs.launchpad.net/hundredpapercuts/+bug/1529450
[18:50] <yeehi> Thanks, mparillo Why do you love Plasma / Kubuntu?
[18:57] <mparillo> Linux in general is what I need to run inside a VM on my work computer. Linux in general allowed me to recover my son's laptop after the Win7 to Win10 upgrade failed. Kubuntu feels to me the lightest KDE distro, and the folks here and on kubuntuforums.net are the best. So I help with Plasma 5, even though it is only now approaching Plasma 4.
[18:58] <mparillo> yeehi: But is sounds as you are successfully installing even though the underlying bug is not solved?
[18:59] <yeehi> The daily today installed beautifully, mparillo!
[18:59] <yeehi> I was very happy
[19:08] <mparillo> TY. I will try myself again soon then.
[19:41] <sgclark> clivejo: ping
[19:41] <clivejo> ong
[19:41] <clivejo> sgclark: pon
[19:42] <sgclark> are you working on kdepim-runtime?
[19:42] <clivejo> not any more
[19:43] <sgclark> ok
[19:55] <sgclark> hmmm FTBFS kdesdk-kioslaves
[19:59] <clivejo> yofel: I merged master -> xenial_archive and I think all of them have conflicts :(
[19:59] <yofel> :S
[20:00] <clivejo> mainly changelog, control and rules
[20:01] <clivejo> but a few symbols and install files to make things interesting
[20:01] <clivejo> wait, should I stage them first?
[20:02] <clivejo> if I bumped to 5.19 that *might* fix a few of the control file conflicts?
[20:05] <sgclark> uh what is going on? kf5 was already merged
[20:05] <yofel> clivejo: just stage it normally then. Not worth the trouble
[20:06] <clivejo> actually I think if I staged first it would get rid of a lot of these conflicts
[20:06] <clivejo> most are :
[20:06] <clivejo> <<<<<<< HEAD
[20:06] <clivejo>                extra-cmake-modules (>= 5.18.0~),
[20:06] <clivejo> [20:06] <clivejo>                extra-cmake-modules (>= 5.19.0~),
[20:06] <clivejo> >>>>>>> master
[20:06] <yofel> I don't think so.. but I wonder what the conflict in rules would be?
[20:06] <sgclark> why are you merging kf5 again?!?!
[20:07] <yofel> ah yeah, that'll happen
[20:07] <yofel> sgclark: I thought merging would be easy...
[20:07] <yofel> well, it's not
[20:07] <sgclark> I a mso confused, do you mean to sync?
[20:07] <yofel> no
[20:08] <sgclark> kf5 merges have already been done, I am so confused ight now
[20:08] <clivejo> the other problems are symbols
[20:08] <sgclark> apps however still have stuff to be done.
[20:08] <yofel> well yes. So I thought just merging in 5.19 should be easier than doing stuff ourselves
[20:08] <yofel> well, wrong idea
[20:08] <yofel> lets revisit that thought next release
[20:08] <sgclark> oh.
[20:08] <sgclark> I see.
[20:09] <clivejo> ours symbols are labelled 5.18+git.... , debians are 5.19
[20:09] <sgclark> yeah symbol headers always seem to conflict
[20:09] <sgclark> and the version bumps will be issue in control
[20:10] <yofel> ah right..
[20:10] <clivejo> I dont mind going through those the fixing manually
[20:10] <yofel> I should not give advice while being absent minded
[20:10] <sgclark> haha
[20:10] <yofel> just stage it yourself. Will be a lot less work
[20:10] <yofel> note: I was already wrong once today XD
[20:10] <clivejo> yofel: is there a way to undo the merge locally, or should I just clear the folder and git clone again#
[20:11] <sgclark> well I merged kdenlive and it has repo in an off infa svn ... that was fun.. NOT
[20:11] <yofel> clivejo: git reset --hard origin/kubuntu_xenial_archive should undo stuff
[20:12] <clivejo> should or definitely ?!? :P
[20:12] <yofel> it won't undo untracked stuff, and I'm not a 100% expert on git behavior
[20:12] <sgclark> yofel: not sure what to do about kdesdk-kioslaves it is not packaging but and actual build fail.
[20:13] <clivejo> HEAD is now at 6604e11 Release to xenial
[20:13] <yofel> file an upstream bug I guess.. and we'll skip it in the upload
[20:13] <sgclark> yofel: ok
[20:13] <clivejo> sgclark: could that be the debian/tmp thingie again?
[20:15] <sgclark> clivejo: mm not sure what you mean. this fails with recipe svn.cpp not sure that has anything to do with debian/tmp
[20:15] <clivejo> $(overridden_command) --destdir=debian/tmp
[20:16] <sgclark> totally unrelated
[20:18] <clivejo> ok
[20:18] <sgclark> no product for kdesdk-kioslaves... on kde bugs
[20:23] <sgclark> yofel: is there a way to delete a super seceded build in a PPA, I messed up and left an epoch that should have been removed. And now a new release will not publish.
[20:24] <yofel> yes, wait like a random time up to half a day until the janitor deletes the files
[20:25] <clivejo> yofel: staging-upload script is failing
[20:25] <yofel> log please
[20:26] <clivejo> in bump-build-dep-versions
[20:26] <clivejo> Expecting property name enclosed in double quotes: line 75 column 1 (char 2736
[20:26] <yofel> o.O
[20:29] <clivejo> did I mention everything seems to be going wrong for me today?
[20:30] <yofel> now you did
[20:30] <clivejo> yofel: https://paste.kde.org/pkjl3r4rg
[20:33] <yofel> urgh
[20:33] <yofel> clivejo: remove the comma at the end of dev-package-name-lists/frameworks-xenial.json line 75
[20:33] <yofel> stupid json being over pedantic
[20:40] <clivejo> ok its staging at the moment
[20:40] <clivejo> should I push that fix to KA?
[20:42] <clivejo> this script doesnt seem to be bumping build depends
[20:42] <clivejo> I thought it outputs a diff?
[20:45] <clivejo> nope, its not bumping them :/
[20:47] <yofel> yes, push it
[20:47] <yofel> the new script hardcodes the versions in the json files
[20:47] <yofel> unless you update *that* first, it won't do anything
[20:47] <yofel> and IIRC there's no automatic way to update those yet
[20:48] <yofel> sed is your friend
[20:49] <clivejo> what json files?
[20:49] <yofel> the one you just fixed
[20:50] <clivejo> "_comment": "This file was generated automatically by dev-package-name-list."
[20:50] <yofel> ah
[20:50] <yofel> does that work *before* you upload stuff yet?
[20:50] <clivejo> LOL Ive deleted the workspace folder
[20:51] <clivejo> should I bump these all manually?
[20:51] <yofel> as I said, sed is your friend
[20:51] <clivejo> I havent pushed the comma fix yet
[20:51] <yofel> or use perl if you're crazy
[20:51] <clivejo> find and replace?
[20:52] <yofel> or that
[20:53] <clivejo> libkf5identitymanagement-dev is apps
[20:53] <clivejo> bump thats to 15.12.1?
[20:54] <clivejo> I guess not, we havent finished those yet, so wont be in the staging PPA
[20:55] <yofel> don't
[20:55] <yofel> actually
[20:55] <yofel> we'll have to make sure apps deps are not higher than 15.08
[20:55] <yofel> or stuff won't build in the archive
[21:01] <yofel> I should probably throw stuff into a clean ppa before uploading..
[21:14] <clivejo> its currently 15.12.0
[21:14] <clivejo> you must have moved that to the staging PPA?
[21:14] <clivejo> Ill bump it to 15.12.1
[21:16] <clivejo> and pushed
[21:17] <clivejo> lets try the staging script agian
[21:17] <clivejo> thats better
[21:22] <yofel> yeah, but that will definiely fail in the archive
[21:23] <yofel> so that's something to be aware of when uploading
[21:39] <sgclark> why are we working on new stuff when we have not finished old stuff?
[21:40] <sgclark> clivejo: marble needs symbols update.
[21:41] <sgclark> so does libkf5kipi
[21:41] <sgclark> and again with libkf5kface
[21:57] <clivejo> hummmmm Debian only do symbols for amd64?
[21:57] <sgclark>  ask them?
[21:58] <sgclark> clivejo: did you research the lintain error on ktp-text-ui? if not you need to.
[21:58] <clivejo> # SymbolsHelper-Confirmed: 4:15.12.0 amd64
[21:58] <clivejo> libmarblewidget-qt5.so.23 libmarblewidget-qt5-23 #MINVER#


[00:24] <Noldorin> zzz
[04:04] <RAOF> Ra raw! The precise unapproved queue now features such unuseful links as http://lplibrarian-private-download.internal:8000/110401053/xen_4.1.2-2ubuntu2_4.1.2-2ubuntu2.2.diff.gz
[04:05]  * ajmitch heard that was being fixed
[04:06] <ajmitch> & apparantly a fix to be deployed tomorrow, if I'm reading the channel log correctly
[04:06] <RAOF> Ok.
[04:07] <RAOF> That'll make today's SRU processing annoying, but if it's fixed tomorrow that's ok.
[04:08] <StevenK> It will get deployed today or tomorrow
[04:09] <StevenK> Depending if my structsub branch passes QA or ends up as a bucket of a fail
[04:09] <RAOF> Heh.
[04:12] <wgrant> RAOF: Bug #1025515
[04:12] <RAOF> Ta
[05:31] <StevenK> RAOF: Colin's fix is deployed.
[05:33] <RAOF> StevenK: Thanks.
[09:47] <jfi> Hello, is there actually an issue with the brz import from svn? https://code.launchpad.net/~jfi/psensor/trunk is stuck since at least 30mn, svn repository is up
[09:50] <mgz> that seems to have in import and revs from yesterday
[09:50] <mgz> what do you think isn't working?
[09:52] <jfi> usually I can request manually an import
[09:52] <jelmer> jfi: are you logged in?
[09:52] <jfi> and there is the message: "The next import is scheduled to run as soon as possible. " in the page since at least 30mn (usually it takes a couple of minutes)
[09:52] <jelmer> jfi: actually, a new import is already scheduled
[09:52] <jfi> jelmer, yes I am logged
[09:53] <jelmer> jfi: so presumably there just is a big queue for the imports
[09:53] <jfi> ok
[10:42] <wgrant> jfi: One of the import machines ran into trouble after a hardware issue yesterday, causing a substantial queue to build up. We've just kicked it and it's started picking up jobs again, so it should clear within a few hours
[13:03] <Saviq> hey, trying to branch lp:ubuntu/precise/totem, getting an error:
[13:03] <Saviq> bzr: ERROR: Revision<EMAIL_ADDRESS>not present in "Graph(StackedParentsProvider(bzrlib.repository._LazyListJoin(([CachingParentsProvider(None)], []))))".
[13:51] <jelmer> Saviq: that's a known issue; disabling the launchpad freshness checker in bzr should work around it
[13:51] <Saviq> jelmer, ok thanks
[16:04] <cecile_> Hello, I'm a developper at OpenERP. We just renewed our openerp-int project (private project) and we are no able to see the page on launchpad anymore.
[16:19] <czajkowski> sinzui: are you about to help on a call here for the next 40/50 mins
[16:25] <sinzui> czajkowski: I reactivated the project for the user. I will see if I can track his email address down to tell him
[16:27] <czajkowski> sinzui: mail is gone to<EMAIL_ADDRESS>[16:27] <czajkowski> sinzui: thanks
[16:34] <Sweetshark> wth? https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1026596 <- how can duplicate/new possible be a sensible state? why does lp allow that?
[16:52] <sinzui> Sweetshark: That is the state of the bug if it were unduplicated. this is bug 317244 and bug 524294
[16:57] <Sweetshark> sinzui: k. thx.
[18:26] <george_e> Is the fix for the problem with the PPA builders deployed yet?
[19:05] <george_e> Anyone know?
[19:10] <LordOfTime> george_e: so you broke PPAs, huh? (points at Ask Ubuntu chat briefly)
[19:10] <LordOfTime> lol, i kid, apparently you're having problems and my logs dont exist, so...
[19:11] <LordOfTime> george_e: is it returning any errors?
[19:11] <george_e> Well, I `dput`-ed a bunch of packages and they aren't showing up anywhere.
[19:11] <LordOfTime> george_e: where'd you dput them?
[19:11] <george_e> LordOfTime: No, I'm not getting anything at all?
[19:11] <george_e> LordOfTime: To ppa:george-edison55/nitroshare
[19:12] <LordOfTime> george_e: according to the build logs for your repo, there's stuff there...
[19:12] <LordOfTime> wonder why its not showing up though
[19:15] <george_e> I'll be AFK for a bit.
[19:15] <george_e> But feel free to ping me.
[21:10] <george_e> Something is still wrong with PPA uploads.
[21:10] <george_e> None of them are showing up anywhere.
[21:13] <czajkowski> george_e: are you seeing any errors?
[21:14] <george_e> None whatsoever.
[21:14] <george_e> This is what I get: http://paste.ubuntu.com/1100875/
[21:15] <dobey> george_e: those weren't uploaded; did you delete all the recipe builds in that ppa?
[21:15] <george_e> I deleted four recipe builds in the PPA.
[21:16] <dobey> george_e: in that pastebin, your packages are not signed with a gpg key that is associated with your account
[21:16] <dobey> george_e: and unfortunately in that case, you don't get an error e-mail
[21:16] <george_e> Oh... so that's the problem.
[21:16] <dobey> yes
[21:16] <dobey> well, that's the first problem
[21:16] <george_e> Thanks for clearing that up.
[21:17] <dobey> i don't think you'll be able to upload as a native package versioned as just 0.2 either
[21:17] <dobey> because it will be older than what was previously uploaded by the recipe
[21:19] <george_e> dobey: Even after deleting the packages?
[21:20] <dobey> george_e: yes; because even if it were uploaded, anyone who installed the older version will not be able to upgrade to the "new" version that is actually older
[21:27] <george_e> dobey: Actually, that's okay. The newest recipe build and the version I'm uploading have identical contents.
[21:27] <george_e> So users who have the package won't see the update...
[21:27] <george_e> ...and those who don't will get the one I'm uploading.
[21:28] <micahg> george_e: it's not ok to allow though since that won't necessarily be the case, you have to upload a different version
[22:31] <Logan_> Can a Launchpad admin please delete the upstream link for https://launchpad.net/ubuntu/+source/fftw3 ? It is currently linked to the python bindings for FFTW, not the actual upstream project.
[22:31] <micahg> Logan_: done
[22:32] <Logan_> micahg: Thanks. :)