[00:08] <cody-somerville> lifeless, 108 queries/external actions issued in 1.91 seconds
[00:08] <cody-somerville> AJAX Log ↓
[00:09] <lifeless> cool thanks
[00:24] <nigelb> woah, https://code.launchpad.net/~launchpad-pqm/launchpad/devel just timeout'd for me
[00:24] <wgrant> nigelb: Probably got caught on a branch scanner lock.
[00:24] <wgrant> :(
[00:24] <nigelb> wgrant: want the OOPS-ID?
[00:25] <wgrant> There's already a bug, and it will show up on the reports in an hour.
[00:25] <nigelb> okay
[00:26] <nigelb> "oh-oh-pick-me-pick-me" heh, interesting branch name :)
[00:32] <nigelb> I call today a success. I wrote a test case entirely on my own without help :D
[00:34] <nigelb> I was about to ping wallworld :/
[00:35] <nigelb> Could someone review https://code.launchpad.net/~nigelbabu/launchpad/spec-sub-sort/+merge/63315 for me please? :)
[00:36] <wgrant> He's still around.
[00:36] <wgrant> We're on a call at the moment.
[00:37] <nigelb> Okay, I'll wait for later :)
[00:47] <jelmer> mwhudson: yep, that's the only failing test left
[00:47] <jelmer> mwhudson: I don't think anything significant has changed
[00:49] <mwhudson> jelmer: do you understand what the test is trying to test?
[00:51] <jelmer> mwhudson: I think I understand what it's trying to do, but the actual result surprises me
[00:52] <mwhudson> jelmer: me too i guess!
[00:52] <mwhudson> jelmer: as james_w said, has there been any change like breaking locks silently when there is no process with that pid any more?
[00:53] <jelmer> mwhudson: I missed James' comments, but that sounds plausible
[00:53] <mwhudson> although
[00:54] <mwhudson> i don't think that actually applies here
[00:56] <nigelb> wallyworld: hey
[00:56] <wallyworld> nigelb: hi. otp. will be finished soon
[00:57] <nigelb> cool
[00:58] <mwhudson> jelmer: ui factory changes might also affect this
[00:59] <mwhudson> PullerWorkerUIFactory.get_boolean is a thing of ... something
[00:59] <mwhudson> debugging integration test failures is always such a pain
[01:00] <jelmer> mwhudson: that's a good point
[01:01] <mwhudson> although i'd naively think that changes would result in the other test failing, i.e. not breaking the lock when it should be broken
[01:02] <lifeless> mmm
[01:02] <lifeless> so we're moving soon to multiple bzr+ssh servers
[01:02] <lifeless> we can't assume a pid lookup on the machine is authoritative
[01:02] <jelmer> mwhudson: I bet it's confirm_action, which now defaults to true
[01:02] <mwhudson> jelmer: yes
[01:03] <mwhudson> jelmer: i've just found the same code :)
[01:03] <wallyworld> nigelb: available now :-)
[01:03] <mwhudson> jelmer: it looks like there might be a saner mechanism to achieve the desired results too, perhaps
[01:03] <nigelb> wallyworld: could you review https://code.launchpad.net/~nigelbabu/launchpad/spec-sub-sort/+merge/63315 ? :)
[01:03] <mwhudson> jelmer: this confirmation_id thing
[01:04] <mwhudson> jelmer: does this mean that break_lock() will unconditionally break now in a script?
[01:04] <jelmer> mwhudson: seems likely, SilentUIFactory (which the UI factory the puller code installs derives from) has a confirm_action implementation that returns True
[01:05] <mwhudson> i wonder if that's an intended consequence
[01:07]  * wallyworld shakes fist at irc - keeps disconnecting
[01:22] <jelmer> mwhudson: hmm, seems like this roughly the right place.. now I have a hanging twisted "thing", which is presumably caused by waiting for the lock to go away
[01:24] <mwhudson> jelmer: the lock holding process should be killed
[01:24] <mwhudson> jelmer: the callback called 'cleanup' in _run_with_destination_locked
[01:34] <jelmer> mwhudson: my neck is twisted from trying to follow everything that's going on here; thanks for the help so far, I'll have a closer look tomorrow
[01:34] <mwhudson> jelmer: yeah, it's very confusing
[01:34] <mwhudson> partly that's fairly inherent in what's being tested, but i'm sure it goes above and beyond what's required
[01:35] <mwhudson> this was the first difficult code i wrote for canonical btw :)
[01:36] <nigelb> wallyworld_: run lint, meaning run the tests?
[01:38] <nigelb> wallyworld_: I ran the test I added
[01:38] <jelmer> mwhudson: :) well, it is neat this sort of thing is actually tested
[01:39] <mwhudson> jelmer: yeah, and it seems like it caught a genuine issue too!
[01:50] <wallyworld_> nigelb: sorry, was otp again. lint checks that the code syntax etc is as expected. you run bin/lint
[01:51] <wallyworld_> nigelb: the output will highlight issues with adherence to the coding standards
[01:51] <nigelb> wallyworld_: ahh, doing that now
[01:51] <wallyworld_> nigelb: it will detect which files have changed and only run against those
[01:52] <wallyworld_> nigelb: also, there's a jslint for any javascript stuff you do
[01:54] <nigelb> aha
[01:57] <nigelb> wallyworld_: okay, I updated the branch with lint changes and the other changes you mentioned
[01:58] <wallyworld_> nigelb: thanks. looking now.
[02:04] <wallyworld_> nigelb: thanks for doing those changes. for next time you would then include the lint output in the merge proposal description, along with the other sections from the template as discussed. i just need jtv to sign off on it now since i'm only an apprentice reviewer
[02:05] <nigelb> wallyworld_: awesome, thanks.  Could you also land it once its signed off? I'm not Canonical......yet.
[02:05] <wallyworld_> nigelb: no problem at all. will do :-)
[02:27] <nigelb> lifeless: Updated the code for readability as you suggested.
[02:27] <lifeless> thanks
[02:33] <wallyworld_> sinzui: i'm confused. i'd love a chat if you had 5 minutes. otherwise i'll ping you later
[03:18] <LPCIBot> Project windmill-db-devel build #359: STILL FAILING in 44 min: https://lpci.wedontsleep.org/job/windmill-db-devel/359/
[03:18] <sinzui> wallyworld_: I am back now
[03:19] <wallyworld_> sinzui: mumble?
[03:24] <lifeless> http://research.microsoft.com/en-us/projects/trinity/ is interesting
[03:59] <sinzui> wallyworld_: I think the windmill test failures are still caused the broken spinner I reported. Either my fix failed, or it is not being tested on jenkins yet
[04:02] <wgrant> sinzui: It's in jenkins now.
[04:03] <wgrant> AssertionError: Failure in lp/registry/javascript/tests/test_structural_subscription.html.test_title_ellipsisification: test_title_ellipsisification: failed.
[04:03] <LPCIBot> Project windmill-devel build #169: STILL FAILING in 45 min: https://lpci.wedontsleep.org/job/windmill-devel/169/
[04:03] <wgrant> Aha.
[04:04] <sinzui> wgrant: test_title_ellipsisification failed because the header and title were reversed. I think I fixed that
[04:04] <wgrant> Apparently not :(
[04:06] <sinzui> wgrant: oh good, it does not have my branch yet
[04:08] <wgrant> sinzui: Hm? Build #169 had your "Use standard events [...]" rev.
[04:19] <sinzui> wgrant: I do not see how test_hide_comment and test_personpicker can reliably work since they are missing the complete signal in the test
[04:20] <wgrant> Heh
[04:26] <sinzui> Looks like the complete signal is broken in test_picker after a merge
[04:30] <nigelb> heh, I did think that lifeless's first mail looked sparse.
[04:41] <jtv> hi wallyworld_!
[04:42] <jtv> Any reviews today?
[04:42] <wallyworld_> jtv: hi. there's one so far and one oops tools branch i'm not too familiar with so it's hard to offer anything constructive
[04:43] <jtv> In that case, ask lots of questions!
[04:43] <jtv> You'd be amazed how smart you can look by asking the right stupid question.  :)
[04:43] <jtv> Ever read Surely You're Joking Mr Feynman?
[04:43] <wallyworld_> jtv: ok. the review requested it be done by a member of the oops tools dev team. is it ok that i do it?
[04:43] <wallyworld_> no, haven't read that :-)
[04:44] <jtv> I don't think we're part of the oops tools dev team, no.
[04:44] <jtv> You must read Feynman's autobiographies.  He worked on the Manhattan Project.
[04:44] <wallyworld_> sounds interesting
[04:45] <jtv> He was a bit of a junior type then, but when it was discovered that due to army secrecy rules, the uranium factory hadn't been told about things like "for heaven's sake don't stack it all up, and not on the other side of the wall either!" they just sent him.
[04:45] <wallyworld_> hah
[04:45] <jtv> So there he went, young scientist, knowing nothing of industrial processes and construction.  "What, me, little Richard!?"
[04:46] <jtv> And at the factory, he's the first Manhattan Project scientist they ever see.
[04:46] <jtv> So they think he's some kind of inhuman genius who knows everything.
[04:46] <jtv> And they show him the blueprints to the factory, in rapid-fire succession.
[04:46] <jtv> He thinks he recognizes a recurring mark on the blueprints.  May be a valve.
[04:47] <jtv> But by that time he's several blueprints in, so he can't very well ask "so what's this then, a valve?"
[04:47] <jtv> Instead, he bluffs.
[04:47] <jtv> Points at one, goes "what happens when this valve here gets stuck?"
[04:47] <jtv> —expecting them to say "er… Mr Feynman, you know that's a door, right?"
[04:48] <jtv> Instead, they go "well, in that case…"
  When that valve blocks, everything goes!"
[04:50] <jtv> Anyway, better let the oops-tools review lie then.
[04:50] <jtv> At least we got a nice story out of it.  :)
[04:58] <wallyworld_> jtv: as long as he didn't say "wonder what this big red button does, let's find out..."
[04:59] <jtv> Well he did some of those in his life as well, in his way.
[04:59] <jtv> He also came up with this neat trick:
[04:59] <jtv> Science conference.  Late to book.  All hotels are full.
[04:59] <jtv> So he booked himself and another professor into a room at a hotel that, er, specialized in short stays.
[05:00] <jtv> As in, "you want to stay a _whole_ _night_!?"
[05:01] <jtv> wallyworld_: what's the last you saw?
[05:01] <wallyworld_> jtv: last review request?
[05:02] <jtv> No I mean, what was the last thing you saw before your IRC connection blinked?
[05:02] <jtv> StevenK, wgrant: mind if I delete all DSDJobs on dogfood and restart the app server?
[05:03] <wallyworld_> jtv: it's been blinking all day for some reason :-(
[05:03] <wallyworld_> the last thing was At least we got a nice story out of it.  :)
[05:03] <jtv> Probably because I gave up on wifi and stopped blinking.  Someone has to do it.
[05:03] <jtv> Ah OK, I'll leave the other story for another time then.  Or you can read the book.  :)
[05:04] <wallyworld_> s/book/ebook
[05:05] <wgrant> jtv: I just killed the appserver and deleted all the PackageCopyJobs to let the DB patches apply. I'm dealing with the DB directly now, so you can start it up.
[05:05] <jtv> wgrant: can you delete all dsdjobs while you're at it?  Or I can do it if that's more convenient.
[05:06] <wgrant> jtv: I'm currently in the middle of fti.py, so not really convenient for me to do that right now.
[05:06] <jtv> OK I'll do it
[05:06] <jtv> And done.
[05:07] <jtv> And I'll start the app server.
[05:08] <wgrant> Hm, doesn't seem to be running?
[05:09] <wgrant> Oh, you're making?
[05:11] <jtv> Trying.
[05:11] <jtv> Failing.
[05:11] <jtv> KeyError: u'../images/mute.png'
[05:14] <jtv> A file that does seem to exist — but not in branches on my own machine.
[05:15] <wgrant> That was added recently... what was it that filed? Spriteutil?
[05:15] <wgrant> failed.
[05:17] <wgrant> HM, indeed.
[05:18] <wgrant> jtv: Works now.
[05:19] <wgrant> jtv: I moved icon-sprites.positioning out of the way.
[05:19] <wgrant> It rebuild it and completed OK.
[05:19]  * wgrant makes start.
[05:20] <wgrant> It's up.
[05:20] <jtv> Thanks.
[05:21] <jtv> How did you know how to fix that?
[05:22] <wgrant> I saw the new sprites added this morning, guessed that one of the caches was out of date.
[05:29] <jtv> Then I wonder why "make" didn't see that.
[05:29] <wgrant> No idea.
[05:29] <wgrant> Our Makefile is a bit crap.
[05:30]  * wallyworld__ just had a kernel panic - lost a big loong email :-(
[05:32] <wgrant> jtv: I need to bounce the appserver soonish.
[05:35] <jtv> wgrant: fine with me
[05:37] <wgrant> jtv: It's back.
[05:37] <jtv> thz
[05:38] <jtv> wgrant: mind if I sync some packages?
[05:39] <wgrant> jtv: Not at all.
[05:39] <jtv> Then let's find out if I broke that.
[05:39] <wgrant> wallyworld__: I've fixed the project picker to mostly work, I think.
[05:39] <wallyworld__> wgrant: excellent
[05:40] <wgrant> wallyworld__: Have a look at https://bugs.dogfood.launchpad.net/launchpad/+bug/1234. It now uses icons, ranks properly, and doesn't search description, and puts exact name matches first.
[05:40] <_mup_> Bug #1234: Gina is an unmaintainable mess of command line options, environment variables and shell scripts <lp-foundations> <Launchpad itself:Fix Released by debonzi> < https://launchpad.net/bugs/1234 >
[05:40] <wgrant> So it's a bit less unusalbe.
[05:40] <wgrant> Although still ugly because of lazr-js's icon positioning.
[05:40]  * wallyworld__ looks
[05:46] <wallyworld> wgrant: i'm searching for "firefox" and it's been going over a couple of minutes now with now result
[05:46] <wgrant> wallyworld: Took 3.2s for me.
[05:46] <wallyworld> hmmm. i'll try again
[05:46] <wgrant> DF is not the most stunningly reliable entity in the universe.
[05:48] <wgrant> We possibly still want affiliation.
[05:48] <wallyworld> yeah the gods are against me today. still no luck
[05:48] <wgrant> But like with team search, they are far more likely to be unique and searchable.
[05:48] <wgrant> Huh.
[05:48] <wgrant> Does 'launchpad' work?
[05:49] <wallyworld> i'll look
[05:49] <wallyworld> works in a fashion - "Too many matches, please narrow your search"
[05:49] <wgrant> Which picker is this?
[05:50] <wallyworld> project picker on https://bugs.launchpad.net/launchpad/+bug/1234/+choose-affected-product
[05:50] <_mup_> Bug #1234: Gina is an unmaintainable mess of command line options, environment variables and shell scripts <lp-foundations> <Launchpad itself:Fix Released by debonzi> < https://launchpad.net/bugs/1234 >
[05:50] <wgrant> WTF, which one is that.
[05:50] <wgrant> It's a different one.
[05:50] <wgrant> Try the one in the task row on the bugtask index.
[05:50] <wgrant> While I track down why we have two product pickers.
[05:50] <wallyworld> one uses "project" the other "product"
[05:51] <wallyworld> in the title
[05:51] <wgrant> Oh, no, they are the same vocab.
[05:51] <wgrant> But you were trying on production...
[05:51] <wgrant> And yes, they have different titles.
[05:51] <wgrant> That's fixed locally.
[05:52] <wallyworld> no luck with the dogfood one one the bagtask row
[05:52] <wgrant> Sure it's dogfood this time? :)
[05:52] <wallyworld> might just be me
[05:52] <wallyworld> yep :-)
[05:54]  * wallyworld has to run away for a bit to pick up the kid and buy dinner. wife is out so i can get whatever junk food i want :-D
[05:54] <wgrant> Heh
[05:54] <wallyworld> mmmm. lasagne sounds good
[05:54] <wallyworld> wgrant: i've also found a couple of person picker implementations :-/
[05:55] <wgrant> wallyworld: There are a few pillar pickers.
[05:55] <wgrant> Hm.
[05:55] <wgrant> Now the product picker is hanging for me too.
[05:55] <wgrant> Except it also hangs Chromium's developer console.
[05:57] <StevenK> wallyworld: How is lasagne junk food? :-)
[06:19] <wgrant> stub: We can't do FTI column rebuilds live, can we?
[06:35] <wgrant> wallyworld (when you're back): I tried a couple of quick changes to make the picker less ugly: http://people.canonical.com/~wgrant/launchpad/project-picker/before.png vs http://people.canonical.com/~wgrant/launchpad/project-picker/after.png
[06:36] <wgrant> StevenK: What do you think?
[06:36] <wgrant> It's possibly less easily scannable due to the lack of indentation on the summary.
[06:36] <wgrant> But I think it's better.
[06:37] <StevenK> I think slangasek has been asking me hard questions.
[06:37] <wgrant> Oh?
[06:37] <wgrant> Ah, there.
[06:37] <StevenK> wgrant: I prefer after
[06:37] <StevenK> It looks cleaner, but I share your concern.
[06:38] <wgrant> But the old one is fugly, so meh.
[06:47] <jtv> wallyworld: with a heavy heart I voted Disapprove on that MP.  By the way, when you do a "code*" review, please always point out what the asterisk means!
[06:54] <nigelb> jtv: yeah, I noticed.
[06:54] <nigelb> jtv: I agree with your reason to disapprove, but this is part of 2 bugs I fixed sorting.  This means both of them needs to be re-reviewed.  The other one landed in production already.
[06:54] <wallyworld> jtv: i had no idea sorting was so involved
[06:55] <jtv> nigelb: I'm writing that email at the moment.  It'd be nice to have this solved.
[06:55] <wallyworld> wgrant: i like the after shot - the way the description text is left aligned reall yhelps
[06:55] <wgrant> wallyworld: I'm also getting rid of the margin at the bottom.
[06:55] <wgrant> Needs some lazr-js CSS changes :(
[06:56] <wallyworld> wgrant: i think the preferred approach is to override the styles in lp
[06:56] <jtv> wallyworld: there's some weird stuff out there.  Letters that you convert to upper-case and back to lower and they're not what you started with; scanning the string backwards for tie-breakers; letters that change position in the alphabet based on use-case; letters that need to be read in one order, written in another order, and sorted in yet another one.
[06:56] <wgrant> wallyworld: Probably.
[06:57] <wallyworld> jtv: so what's best preactice for sorting?
[06:57] <nigelb> I'm curious though, how'd we solve this for bug subscriptions. Aren't they also sorted alphabetically?
[06:57] <jtv> wallyworld: and my all-time favourite: i/I are not a lower-case/upper-case pair in Turkish.
[06:57] <wallyworld> wgrant: doing it that way was what curtis wanted for the badge styling
[06:57] <wgrant> wallyworld: Yeah, but this is probably slightly different.
[06:57] <wallyworld> jtv: wtf? how so?
[06:57] <wgrant> wallyworld: anyway, I can probably override this in LP using :empty.
[06:58] <wallyworld> wgrant: you then don't need to do a lazr-js mp :-)
[06:58] <wgrant> style-3.0.css makes me sad.
[06:58] <wallyworld> me too
[07:00] <jtv> wallyworld: there's no single solution, and the partial solutions all basically sort of hope that you won't be mixing languages.  Good technical practice includes "don't try to deal with letters as such because you can't imagine the horrors in the dungeon dimensions beyond ASCII," "don't think you understand what .upper() and .lower() do," "don't talk to foreigners," and "let somebody else take care of it."
[07:00] <nigelb> Note to self: Don't touch sorting bugs.
[07:00] <wallyworld> i like the last one best :-)
[07:01] <wallyworld> nigelb: it all seemed so easy before jtv pointed out a few realities :-)
[07:01] <jtv> wallyworld: oh, about Turkish?  They have a sensible but incompatible system where i/İ form a pair, and there's another pair without the dot that I can't figure out how to type right now.  Note how in both pairs, one letter is ASCII and the other isn't.
[07:02] <nigelb> wallyworld: True that.  I only just fixed one bug this way because it was tagged easy and then I went ahead and fixed specifcations too
[07:02] <nigelb> Now I have to re-fix the sorting bugs I've touched
[07:02] <nigelb> After we bikeshed on the best way to fix this :D
[07:02] <wallyworld> nigelb: well whoever tagged it as easy knows as little as you and me about the problem :-)
[07:02] <jtv> nigelb: /me nods emphatically :)
[07:02] <nigelb> true, that.
[07:02] <jtv> Somebody tagged this as easy?  Amusing.
[07:02] <jtv> It _seems_ easy.
[07:03] <nigelb> Not this.  Someone tagged sorting the sprints as easy
[07:03] <nigelb> From there I found the specifications one
[07:03] <wallyworld> jtv: so does keeping one's wife happy, but their both roads frought with danger
[07:03] <nigelb> I fixed both but without the lower(), so it wasn't really fixed
[07:03] <wallyworld> s/their/they're
[07:03] <nigelb> So, I refixed sprints with .lower() and this was an attempt to fix specifications
[07:04] <nigelb> Now I have to do this all over again :)
[07:04] <wgrant> jtv: For a proper solution we surely need to define a collation for each text field, and somehow use them all together nicely.
[07:04] <wgrant> That sounds like fun.
[07:04] <jtv> wallyworld: funny you should mention that, given that mine was born with a different script than I, but bilingual where one language is "officially" written in a script I had to teach her.
[07:05] <jtv> wgrant: not sure that doing it per field is the solution.  I suspect we'll always have a bit of a weird mix, with some ordering coming out of the DB and other ordering happening in Python.
[07:06] <jtv> postgres now supports per-column collation, but I was one of the ones who did not support that idea.
[07:07] <jtv> I feel that basically, sorting for display and sorting for computer use are different tasks just like e.g. rendering integers as strings for both are.
[07:07] <jtv> But does anyone listen?  No, and I can't blame them.
[07:08] <wallyworld> wgrant: do you hear anything?
[07:08]  * jtv presses caps lock and prepares to repeat
[07:08] <wallyworld> :-P
[07:09] <jtv-aol> I SAID…
[07:10] <jtv> nigelb: truly sorry to be such a spoilsport; on the bright side, I hope we can get a better solution.
[07:12] <nigelb> jtv: that's what I'm thinking too :)
[07:12] <jtv> wallyworld: fwiw Turkish is apparently sort of the standard smoke-test language for locale handling.  It's got just enough differences from ASCII to trip you up, but not enough to be completely alien to programmers who use mostly ASCII.
[07:12] <nigelb> jtv: I don't mind refixing things if its "THE FIX" :)
[07:13] <jtv> The email just went out.
[07:13] <wallyworld> hah. time to learm turkish
[07:13] <wgrant> Yay, qbzr works again.
[07:13] <StevenK> nigelb: THE FIX, NO I REALLY MEAN IT THIS TIME.
[07:13] <lifeless> jtv: fwiw there is other code with the collation limit defect you point out
[07:13] <jtv> Limit?
[07:13] <nigelb> StevenK: Yeah, that one.  It would be the third fix for this bug :)
[07:14] <wgrant> lifeless: I think it's possibly everything else in Launchpad ever.
[07:14] <lifeless> jtv: so I don't think blocking this localised improvement for a global one is necessary
[07:14] <wgrant> wallyworld: extra-form-buttons... do you know why the height: 3em is there?
[07:14] <wallyworld> is stles-3.0.css?
[07:14] <wgrant> Yes.
[07:14] <wgrant> You added it in 12641.6.30
[07:15] <wallyworld> wgrant: not sure now. to make it work :-)
[07:15] <wgrant> I guess I'll just remove it and check both users.
[07:15] <jtv> lifeless: we could go there, but then we'd want to make the sort order determinate again, and before you know it we're still re-inventing the wheel.
[07:16] <lifeless> jtv: huh?
[07:16] <wallyworld> wgrant: sorry i can't recall exactly. i guess without it it would have rendered too squashed or something
[07:16] <lifeless> jtv: I don't follow
[07:16] <wallyworld> or too tall
[07:16] <lifeless> jtv: we have *identical* (barring variable names) code to the code nigelb proposed elsewhere.
[07:16] <lifeless> jtv: how is accepting his patch tied to wheel reinvention ?
[07:17] <nigelb> lifeless: sprints
[07:17] <jtv> lifeless: sorting a bunch of strings is hairy, but determinate.  Converting to lower case and then sorting is simple, but indeterminate.  It's not disastrous, but if you test for sorting "a" vs. "A"…
[07:17] <nigelb> at least that I know of.
[07:18] <lifeless> jtv: I accept that assertion. I don't follow the chain of causation
[07:19] <lifeless> nigelb: loggerhead, mailman, sprints, persons, branches
[07:19] <lifeless> at least
[07:19] <nigelb> woah.
[07:19] <nigelb> that's a lot.
[07:19] <lifeless> maybe
[07:19] <lifeless> 7 call sites a *truely trivial* grep found
[07:19] <lifeless> I didn't look for multiline sorts
[07:19] <lifeless> so I'd expect more - maybe 15 or 20
[07:20] <lifeless> not huge in the scheme of things, but there may be more where its not obvious that we've done a lower()
[07:20] <nigelb> hrm, just a doubt though.  How often are the strings of the kind that we have a problem with?
[07:20] <nigelb> Like, are all the fields UTF-8 in the db?
[07:21] <lifeless> most are yes
[07:21] <lifeless> some have narrower constraints
[07:21] <jtv> There's plenty of ascii-only identifiers, even if the columns may be Unicode.
[07:22] <lifeless> dispaly names are generally free form, the url components are all tightly limited subsets of ascii
[07:22] <lifeless> anyhow
[07:22] <lifeless> its 6:30 pm
[07:22] <lifeless> I'm not really here
[07:23] <lifeless> I just don't think we should block a temporary improvement for a larger change we haven't yet made that may require reversing this patch at that later date.
[07:23] <lifeless> unless it would be *worse* today, (in which case its not a temporary improvement)
[07:24] <wgrant> wallyworld: Ah, turns out you just converted it from inline styles.
[07:24] <wallyworld> wgrant: right. makes sense
[07:31] <jtv> lifeless: it's better in some ways, worse in others — and to some extent we just don't know.  General good practice says "don't do this."
[07:31] <jtv> But see the mailing list.  Martin's got some good comments.
[07:34] <nigelb> so we write a wrapper and then fix this problem systematically?
[07:34] <nigelb> fix the wrapper step by step I guess
[07:35] <stub> wgrant: We can. What fti change where you thinking of?
[07:35] <wgrant> stub: Dropping product.description from product.fti.
[07:37] <wgrant> AFAICT it's as deprioritised as it can get, and it's still bad.
[07:37] <wgrant> Dropping it yields better results.
[07:37] <wgrant> name/displayname/title/summary should cover all the important data.
[07:37] <wgrant> description is more of a homepage.
[07:40] <stub> Why is converting a string to lowercase and sorting indeterminate?
[07:40] <stub> I don't think any lower() functions invoke random()
[07:40] <wgrant> stub: lower('foo') == lower('Foo')
[07:41] <stub> ok
[07:41] <stub> So the correct thing to do in most cases would be to sort by (lower(foo), foo)?
[07:42] <jtv> Well it wouldn't work for Thai, for instance.
[07:42] <lifeless> or not worry
[07:42] <stub> or in en_GB locale we trust?
[07:42] <jtv> Exactly.
[07:42] <jtv> If we use en_GB, or en_US, it's fine.
[07:42] <stub> jtv: Why would that give indeterminate results with Thai?
[07:42] <jtv> But currently we seem to use C, which isn't.
[07:42] <jtv> stub: not indeterminate in that case, just wrong.
[07:43] <stub> Sure, but any collation will be wrong when sorting a set of strings in mixed languages, which is what Launchpad needs to do most of the time. So we have to make a best attempt.
[07:43] <jtv> Yes, and I think the best attempt is what you say: use en_GB or some other human-readable locale.
[07:43] <jtv> Instead of trying to simulate its properties by hand.
[07:44] <stub> en_GB is just insensitive sorting or maybe sorting on (lower(foo), foo) under the hood, or at least it seems that way under Linux.
[07:45] <jtv> It also falls back on unicode collation.
[07:45] <stub> but using locales for sorting was bad in the past, because they only cared about their native alphabets and you ended up with stupid things like 'all japanese strings compare equal'
[07:45] <jtv> en_US.UTF-8 gives me correct sorting for a bunch of non-English strings:
[07:45] <jtv> กา  เก  คา  เค  a  A  b  B  Ξ  ξ  Ω  ω  б  Б  г  Г
[07:46] <wgrant> wallyworld__: Does U1 still use lazr-js, or are we down to just L[SP]?
[07:46] <stub> Cool. If they have fixed that now, we should probably switch to en_?? locale when we migrate to PG 9.x
[07:46] <jtv> What's the connection to the PG upgrade?
[07:47] <jtv> (I forgot most of this discussion)
[07:47] <stub> jtv: We have to rebuild all the databases etc.
[07:47] <jtv> Why?
[07:47] <stub> jtv: I'd rather do that once rather than twice :)
[07:47] <jtv> Indexes?
[07:48] <stub> Actually, we might not have to rebuild if pgmigrator works for us. But we still need to wait if we go that route as we would need locale specific indexes rather than rebuilding the database in a particular locale.
[07:49] <stub> So we either dump and restore with a new locale, or rebuild all our indexes with our preferred locale and keep the DB itself in the C locale. I think :)
[07:49] <jtv> Could we get away with changing the python collation separately?
[07:49] <stub> I don't think we want to do all our sorting client side.
[07:50] <jtv> No, but I wonder how much user-visible sorting of freeform strings we do in the DB.
[07:50] <stub> Most places it won't matter as the field we are sorting on is restricted to lowercase ascii.
[07:51] <jtv> Exactly.  We care here about user-visible sorting of freeform strings.
[07:52] <stub> So maybe we should stick to C locale in the DB for speed :-) (although we would need to measure that - what was slower 5 years ago may no longer be the case)
[07:53] <jtv> Maybe this is actually one of those applications for per-column collations.  :)
[07:53] <jtv> (But that's 9.0 I think)
[07:55] <jtv> I suspect fully-collated sorts will still be slower, but maybe we should treat DB sorting more as being for machine consumption.
[07:55] <jtv> With a few exceptions such as batching queries.
[07:55] <stub> wgrant: That one is a 'possibly, but very problematic'. We need to drop and recreate a trigger, which is fast enough if we manage to grab a lock but grabbing the lock is problematic. And then we need to apply a db patch *to the slaves only* during the next rollout that updates the trigger.
[07:56] <lifeless> wgrant: relatedly isd have deropped lazr.restful
[07:57] <wgrant> lifeless: Oh really?
[07:57] <lifeless> jtv: stub: I think we could tolerate different collations in db and python - for a given dataset we're only going to sort in one of (db, python) I expect.
[07:57] <stub> jtv: I think we will shoot ourselves in the foot if people need to remember to set the default collation order before issuing a query, and I'm not sure if it is possible to do something like ORDER BY name IN LOCALE C, displayname IN LOCALE en_US (or if we would want to do that)
[07:57] <jtv> I agree — I think any problems from that are going to be more along the lines of the symptom that led to nigelb's patch.
[07:58] <stub> lifeless: Yes. Apart from case insensitive, the vast majority of the time nobody will even notice.
[07:58] <stub> jtv: Which I haven't followed :)
[07:58] <jtv> stub: see launchpad-dev list
[08:00] <jtv> I suspect we're going to run into this very rarely with database queries: we tend to rely on different orderings there anyway.
[08:05] <stub> Ordering by distribution may be an issue when we have lots from derived distros (AAALinux). Person.displayname is the only other issue, and we should really be ordering using the functional index for that purpose to strip out punctuation etc. (>> l33t d00d <<)
[08:05] <lifeless> yes
[08:05] <lifeless> however
[08:06] <stub> If it is really only those cases, yer. I guess stick with C locale and override for the rare cases.
[08:06] <lifeless> subscribers-to-an-object - small #
[08:06] <lifeless> person vocabs - huge #'s
[08:06] <lifeless> huge #'s we need db sort for
[08:07] <stub> Functional indexes win there if they have fixed the bug I reported in... erm... 8.1? 7.4?
[08:07] <wgrant> Grar embedded copies of YUI.
[08:07] <wgrant> STAB
[08:08] <stub> (ORDERING BY displayname_sort(displayname) would hit the functional index, but there is a deeply embedded but that caused displayname_sort(displayname) to be reevaluated for every retrieved row.
[08:09] <stub> Need to retest with modern PG...
[08:10] <lifeless> stub: it will still do that
[08:10] <lifeless> stub: remember the performance hit on package versions functional index
[08:10] <jtv> That overhead of functional indexes still hasn't gone away?
[08:11] <jtv> Or is there a gotcha like "you must declare your function as pure or else"?
[08:11] <lifeless> I think its tied to the same node-may-differ thing that makes from-index queries impossible
[08:12] <stub> jtv: I need to check. It was confirmed as a bug, but deeply entrenched and Tom wasn't sure how to fix it. It was still there at least one release later.
[08:13] <stub> (check by creating a stable function with a RAISE NOTICE in it, and seeing if the messages are spit out to the logs when queries are hitting the functional index)
[08:14] <stub> lifeless: Thinking of PG 9.1 rather than 8.4.
[08:14] <stub> Lots of juicy bugfixes and features coming up
[08:17] <jtv> I wonder if maybe the re-evaluation is tied to the liveness check (where you need to access a tuple in the table just to see whether it's visible, even if the index has everything else you need)
[08:17] <lifeless> stub: ah yes
[08:17] <lifeless> jtv: thats what I was referring to ;)
[08:17] <jtv> Oh
[08:17] <lifeless> jtv: I forgot the terminology
[08:17] <stub> jtv: I don't know. My eyes just glaze over at a certain point :)
[08:18] <jtv> lifeless: that's alright, I don't know the terminology either
[08:18] <jtv> Oh blast.  PQM merge failure: test_bug_views.py
[08:20] <wallyworld__> wgrant: i thin kU1 may use lazr-js but not sure, sorry
[08:20] <wgrant> wallyworld__: You broke the lazr-js build :(
[08:20] <wgrant> Traceback (most recent call last):
[08:20] <wgrant>   File "bin/yuimeta", line 17, in <module>
[08:20] <wgrant>     import lazr.js.meta
[08:20] <wgrant>   File "/home/wgrant/Development/lazr-js/trunk/src-py/lazr/js/meta.py", line 9, in <module>
[08:20] <wgrant>     from lazr.js.build import SRC_DIR
[08:20] <wgrant> ImportError: cannot import name SRC_DIR
[08:20] <wgrant> From a fresh make.
[08:20] <wallyworld__> huh? works locally i swar
[08:20] <wallyworld__> i'm using it in lp now
[08:20]  * wallyworld__ checks
[08:21] <wgrant> wallyworld__: This is outside LP.
[08:22] <wallyworld__> hmm. ok. still waiting for editor to start. having computer issues today
[08:23] <wgrant> Any hints on running its tests?
[08:23] <wgrant> I s/SRC_DIR/DEFAULT_SRC_DIR/ and it built, but doesn't seem to work very well.
[08:24] <wallyworld__> wgrant: that import is indeed wrong
[08:28] <wgrant> wallyworld__: There are also some bugs in your new linkfication code.
[08:28] <wgrant> And I think we might need to entirely customise the rendering anyway.
[08:28] <wallyworld__> what bugs?
[08:28] <jtv> gmb: you seem to have a devel/db-devel merge conflict with Gary.
[08:28] <wgrant> wallyworld__: "<a class = '" + css + "' href=javascript:void(0)></a>");
[08:29] <wgrant> wallyworld__: Odd spacing around the class, you're using string concatenation rather than addClass, no quotes around the href, and the href should probably be the real value.
[08:29] <wgrant> li_title.appendChild('&nbsp(')
[08:29] <wgrant> Entities need to end with a semicolon.
[08:29] <wallyworld__> wgrant: i don't want href as the real value.
[08:30] <wallyworld__> i use an onclick handler to open the link
[08:30] <wgrant> Oh?
[08:30] <wgrant> Sure.
[08:30] <wgrant> But it's going to look bad in the status bar.
[08:30] <wallyworld__> it all seems to work in practice
[08:30] <wgrant> Having the right href there won't hurt, and it will make it clearer what it's doing. This point is arguable.
[08:30] <wgrant> The quotes are not :)
[08:31] <wgrant> I'm trying to think how to implement my prettification properly.
[08:31] <wgrant> It needs the image to be part of the title a/span.
[08:31] <wgrant> And needs a custom class on that a/span.
[08:31] <wgrant> And needs the margin reduced.
[08:31] <wgrant> Which seems incompatible with not breaking landscape.
[08:32] <wallyworld__> wgrant: i've merged in the compile fix. i'll do the other things a bit later - i have to take the kid to his violin concert. lord have mercy on my soul
[08:32] <wgrant> Haha.
[08:32] <wgrant> Thanks.
[08:32] <wallyworld__> my ears hurt already
[08:32] <wgrant> (brave, letting a child learn the violin)
[08:32] <wallyworld__> thanks for the input on the js
[08:32] <wallyworld__> yep
[08:37] <StevenK> I love the sound of the violin.
[08:43] <jtv> Peacefully crackling in an open fire.
[08:45] <StevenK> No!
[08:55] <gmb> Anyone dealing with that PQM failure?
[08:55] <wallyworld__> StevenK: i like the sounds of a violin played *well*. not by a 10 year old. have you ever heard a cat being strangled? it's worse than that. now off to my ears' implending doom
[08:56] <gmb> Ah, looks like it's mine and Gary's code fighting.
[08:56] <gmb> And jtv just saw the same thing.
[08:56]  * gmb goes to fix it.
[09:43] <LPCIBot> Project windmill-devel build #170: STILL FAILING in 1 hr 9 min: https://lpci.wedontsleep.org/job/windmill-devel/170/
[10:02] <poolie> lifeless: so the reason i didn't truncate it is it wasn't obvious
[10:02] <poolie> firstly if you can just truncate it and still attach it as a message
[10:03] <poolie> secondly how to do that in python
[10:03] <lifeless> well
[10:03] <lifeless> perhaps I'm being naive
[10:03] <lifeless> I would take the incoming mail as a string
[10:03] <lifeless> take the first 64K which is pretty sure to get all the headers
[10:03] <lifeless> and attach that as a original.txt file
[10:03] <poolie> that could work
[10:04] <poolie> avoids the issue of what would be valid as a mime message
[10:04] <poolie> fyi it has already been stored to the librian by the time this crash occurs
[10:05] <poolie> there might be some other higher limit there
[10:05] <lifeless> it has ?
[10:05] <lifeless> I looked at fromEmail which things it may not have been
[10:05] <lifeless> librarian can store ISOs
[10:05] <lifeless> brb
[10:34] <gmb> Apologies for the continuing breakage on db-devel. I've fixed the conflict but am now getting test failures.
[11:37] <gmb> Oh, obvious failure is obvious.
[11:37]  * gmb facepalms, fixes.
[11:47] <stub> I've been in Thailand too long. "I've not really succeed in describing it in understandable English."
[11:52] <nigelb> So, what's the consensus on the sort thing that jtv raised on the list?
[11:53] <nigelb> On reading the mail threads, I couldn't really find a consensus.
[12:07] <stub> nigelb: I think consensus was that we should be running our Python stuff in a known locale and using locale aware sort routines.
[12:07] <nigelb> stub: hrm, so I can act on that information and update my MP?
[12:07] <stub> nigelb: Not sure how that applies to your immediate problem ;)
[12:07] <nigelb> hah
[12:08] <stub> Might want to confirm that my consensus is not just an over inflated opinion :)
[12:08] <stub> jtv has dropped off though. lifeless might still be alive.
[12:09] <nigelb> Nah, I think I'll pick this up again tomorrow morning
[12:09] <nigelb> Or, reply to the thread :)
[12:35] <wallyworld_> wgrant: the cleaned up js has now merged. it includes the change to show the href in the status bar
[12:36] <wgrant> wallyworld_: Ah, great, thanks!
[12:37] <wallyworld_> wgrant: well, i should never have did it like that in the first place
[12:37] <wgrant> wallyworld_: http://people.canonical.com/~wgrant/launchpad/project-picker/after.png is what it actually looks like now (previous one was hacked in Chromium), but I need to work out how best to do it without breaking Landscape.
[12:38] <wgrant> That will be a job for next week, I suppose.
[12:38] <wallyworld_> wgrant: also, i am redoing the link rendering, but in a lp override of the renderUI method. the lazr-js version is a "well it works generically" thing.
[12:38] <wgrant> wallyworld_: Ah, so we can easily override that?
[12:38] <wgrant> wallyworld_: That will make things easier.
[12:39] <wallyworld_> wgrant: yes, i wrote it so that it worked "out of the box" in lazr-js but easily overridden in lp
[12:39] <wallyworld_> wgrant: the new screenshot loks good
[12:39] <wgrant> Excellent.
[12:40] <wgrant> Yeah, I removed the excess padding and restricted the description to one line and used the custom icon if present and aligned the icons like normal links
[12:40] <wgrant> Looks a bit less scrappy.
[12:40] <wallyworld_> wgrant: i'm doing a base lp picker implementation which overrides lazr-js picker and provides the extra rendering. person picker and friends will use that instead of the lazrjs one
[12:41] <wgrant> wallyworld_: Great.
[12:41] <wallyworld_> ui work takes to much time / tweaking :-)
[12:41] <wgrant> It does, but it makes us look less pathetic.
[12:44] <wallyworld_> can't argue there
[12:45] <jelmer> mwhudson: thanks for the hints yesterday, managed to nail down the issue - properly implementing confirm_action seems to've done it.
[13:01] <LPCIBot> Project windmill-db-devel build #360: STILL FAILING in 50 min: https://lpci.wedontsleep.org/job/windmill-db-devel/360/
[14:08] <deryck> Morning, everyone.
[14:36] <flacoste> morning deryck!
[14:56] <danilos> matsubara, hi, I wonder if you've managed to uncover any terrible issues with staging code regarding bug subscriptions? (as asked about by Gary)
[15:06] <matsubara> danilos, I didn't start the ET yet.
[15:07]  * danilos ponders a few seconds before he figures out that ET is extra-terrestrial... nor, ETA with a missing A... but exploratory-testing :)
[15:07] <danilos> is not*
[15:08] <danilos> matsubara, ok, thanks
[15:23] <LPCIBot> Project db-devel build #609: FAILURE in 34 min: https://lpci.wedontsleep.org/job/db-devel/609/
[15:35] <sinzui> wallyworld: I approved picker-click-item-detail
[15:38] <jcsackett> sinzui: i saw the bug on yui tests; it's assigned to me now, and today is largely clear to take care of it.
[15:40] <sinzui> jcsackett: I just forwared you an email. wallyworld is concerned that he isworking in lazr picker and you create a new one.
[15:41] <wgrant> I am leaving my further picker improvements until one of your implementations wins :/
[15:42] <sinzui> jcsackett: I think we want to investigate these failures: https://lpci.wedontsleep.org/job/windmill-db-devel/359/#showFailuresLink
[15:42] <sinzui> I think we should invite deryckto adjudicate
[15:42] <jcsackett> sinzui: agreed. also, i now need to check my source tree, because my windmill tests are not running.
[15:43] <jcsackett> i ran layer=windmill and got no failures; this should have been picked up. :-/
[15:43] <sinzui> jcsackett: did you see the tests actually run?
[15:43] <jcsackett> sinzui: i saw many tests run.
[15:43] <jcsackett> it looked like all yui/windmill tests had run and passed.
[15:44]  * jcsackett considers whether the personpicker link in branch should just be rolled back.
[15:45] <sinzui> Is saw lp/app/javascript/tests/test_picker.html pass, but it does not now. the test is different after the merge beause other people also worked on that file
[15:46] <wgrant> sinzui: When I checked a month ago that passed everywhere except Windmill. Even in the same browser, it passed fine if not run under Windmill.
[15:46] <wgrant> That may not still be the case.
[15:50] <sinzui> bugger. I think I need to investigate pywebkit again as an alternative browser to run yuitest
[15:52] <jcsackett> sinzui: which do you think works better for us? prepare a branch to fix stuff that may take a bit, or roll back the link-in?
[15:52] <jcsackett> (assuming doing so fixes some of these tests).
[15:54] <sinzui> jcsackett: does rolling back mean you concede your implementaion? Isn't your design the one recommended by deryck?
[15:54] <jcsackett> sinzui: deryck thought that creating a proper widget would be easier than shimming picker.create. i think that's still true.
[15:54] <jcsackett> i'm not rolling back the creation of the personpicker; just rolling back the changes that plug it into the UI, pending the problems brought up.
[15:55] <jcsackett> alternatively, we just need more branches to patch these holes.
[15:55] <jcsackett> but it would seem that there's a level of brokeness currently introduced we should rollback before plugging things back in.
[15:56] <sinzui> jcsackett: lets rollback then
[15:56] <jcsackett> sinzui: dig.
[15:56] <jcsackett> sinzui: bit of time to chat? might be quicker to make sure i'm on the same page. :-)
[15:58] <gary_poster> matsubara, hi.  did my email make sense?  any confusions?
[15:59] <matsubara> gary_poster, yes, it made sense. I'm testing right now. found some small issues, I'll put everything on the wiki once I'm done
[15:59] <gary_poster> awesome, thanks matsubara
[16:00] <jcsackett> hm. sinzui, nevermind the rollback. i misread some email. the second person-picker branch didn't land, so anything wrong with the picker is not yet in the tree.
[16:00] <jcsackett> or rather, not yet in the YUI in the tree.
[16:00] <jcsackett> so i'll see about fixing some of this today in a new branch.
[16:01] <jcsackett> lord, i fail at typing. "not yet in the web UI in the tree." there. that's right.
[16:08] <sinzui> jcsackett: I cannot see anyone's typing errors :)
[16:09]  * sinzui is not sure he see conjugation
[16:13]  * jcsackett laughs.
[16:14] <jcsackett> so, sinzui, have a bit of time to chat?
[16:15] <sinzui> in a moment
[16:17] <jcsackett> sure.
[16:26] <sinzui> jcsackett: I can talk now
[16:42] <bac> hi matsubara
[16:42] <matsubara> hi bac
[17:01] <flacoste> bac: do you feel like reviewing a largish branch (lots of delete on it)?
[17:02] <flacoste> it's over 1500 lines
[17:02] <flacoste> the core changes is less than 500 lines
[17:03] <flacoste> a permission change that had a lot of tests fallout
[17:11] <timrc> abentley, thanks for the quick turn around time on those api changes!
[17:11] <abentley> timrc: no problem.  Enjoy.'
[17:20] <matsubara> gary_poster, danilos: I broke the +subscriptions page heh
[17:29] <danilos> matsubara, it probably wasn't you! ;)
[17:29] <danilos> matsubara, (iow, we broke it :))
[17:29] <danilos> anyway, I am out for the week, file bugs and I'll be looking at them on Monday
[17:31] <matsubara> danilos, https://bugs.launchpad.net/launchpad/+bug/792445
[17:31] <_mup_> Bug #792445: It's possible to create the same subscription over and over again <exploratory-testing> <story-better-bug-notification> <Launchpad itself:Triaged> < https://launchpad.net/bugs/792445 >
[17:39] <gmb> Any bzr-savvy people know what this means? "bzrlib.errors.BzrCheckError: Internal check failed: Cannot add revision(s) to repository: missing referenced chk root keys: [StaticTuple('sha1:d34f39faee56e120a83e7cec4fe01c4fd5fd32f6',)]
[17:39] <gmb> "
[17:39] <gmb> It's what caused the latest build failure on db-devel.
[17:40] <matsubara> gary_poster, I wrote down some of my findings in https://dev.launchpad.net/QA/ExploratoryTesting/BugSubscriptionFeature at the bottom (Second round of testing). there were 3 other issues when I did the initial testing but they were fixed after the staging update. I'm going for lunch now and will continue testing later on and file bugs, etc
[18:27] <gary_poster> matsubara, cool, thanks
[18:27] <gary_poster> subscribe/unsubscribe for anonymous is good catch
[18:28] <gary_poster> Creating multiple identical subscriptions is not a problem in my book
[18:29] <gary_poster> If you don't allow it, then you get into weird situations
[18:29] <gary_poster> like disallowing modification of a subscription because it would make it just like an existing one
[18:29] <gary_poster> and that might even just be a transitional step while you adjust things
[18:29] <gary_poster> batching is a separate aspect of this
[18:30] <gary_poster> Having many, many pertinent subscriptions is a broken use case IMO; supporting it gracefully is a low priority IMO
[18:31] <bac> flacoste: sure, i'll be glad to look at it
[18:32] <flacoste> bac: thanks a million
[18:32] <flacoste> bac: https://code.launchpad.net/~flacoste/launchpad/bug-365098/+merge/63305
[18:35] <flacoste> bac: important changes are in canonical.launchpad.security,  lib/lp/registry/model/sourcepackage.py, lib/lp/registry/interfaces/sourcepackage.py andlib/lp/registry/tests/test_sourcepackage.py
[18:35] <bac> thanks flacoste.  just reading your MP
[18:35] <flacoste> rest are tests fallout
[19:33] <deryck> abentley, did you spend any interrupt time on the burn down lists today?
[19:34] <abentley> deryck: no, not yet.
[19:34] <deryck> abentley, I just caught them all up.  if you could take a quick peak before you EOD, they should be good for yellow squad next week.
[19:34] <abentley> deryck: cool.
[19:34] <deryck> thanks, man!
[19:49] <flacoste> deryck: didn't somebody fix something similar to bug 410864 recently?
[19:49] <_mup_> Bug #410864: 'choose a source package' suggests undefined when search has too many results <LAZR Javascript Library:Triaged> < https://launchpad.net/bugs/410864 >
[19:49] <flacoste> or sinzui?
[19:50] <deryck> flacoste, yes, henning did.
[19:50] <flacoste> deryck: could he or you validate that this one is also fixed and mark it as so?
[19:50] <flacoste> as such
[19:51] <deryck> flacoste, sure.
[19:51] <deryck> flacoste, I'll try to look today, and if not, ask him Monday.
[19:53] <deryck> flacoste, looking at his diff, I would imagine it covers all pickers.  he changed picker.js in our tree.
[20:16] <deryck> flacoste, yeah, I did some qa.  it's definitely fixed.
[20:17] <SpamapS> flacoste: So, I can't file bugs against the packages in principia
[20:17] <SpamapS> "haproxy" does not exist in Principia Ensemble. Please choose a different package. If you're unsure, please select "I don't know"
[20:17] <SpamapS> flacoste: is this because its checking to see if there is at least one build?
[20:19] <flacoste> SpamapS: yes, that's bug 781993
[20:19] <_mup_> Bug #781993: cannot file bugs on source packages that have not been published <bugs> <escalated> <not-pie-critical> <principia> <stakeholders> <Launchpad itself:In Progress by flacoste> < https://launchpad.net/bugs/781993 >
[20:20] <SpamapS> flacoste: "me too'd" and subscribed, thanks.
[20:35] <timrc> lifeless, I submitted a merge proposal for #724740, I currently have cody-somerville taking a look, but is there someone within the LP org that will also need to review?
[20:35] <_mup_> Bug #724740: setting a ppa private cannot be done over the API <api> <oem-services> <ppa> <Launchpad itself:In Progress by timrchavez> < https://launchpad.net/bugs/724740 >
[20:36] <cody-somerville> timrc, I imagine lifeless might be sleeping right now.
[20:36] <cody-somerville> timrc, However, the answer is probably yes.
[20:37] <timrc> cody-somerville, he never sleeps
[20:37] <abentley> timrc: if he's asleep at 7:37 his time, he's sleeping in.
[20:38] <cody-somerville> I'm always asleep at 7:37.
[20:38] <timrc> cody-somerville, that's because you go to bed at 5
[20:45] <lifeless> it is saturday ;)
[20:45] <lifeless> cats have been running rampant for an hour now
[20:45] <lifeless> timrc: yes, one of the LP reviewers will need to review
[20:46] <statik> lifeless: since you are here, a very quick question: the GPG validation microservice that you asked for prototype implementations of, I would like clarification of the exposed API
[20:47] <lifeless> shoot
[20:47] <statik> "takes crypt text in and returns the signer, cleartext". Does that mean that the service is expected to have the private keys available to it?
[20:47] <lifeless> oh
[20:47] <statik> i'm mixed up about whether this is a decryption service or a gpg validation service
[20:47] <lifeless> so thats a lingo thing
[20:48] <lifeless> the crypt text is the signed document
[20:48] <statik> perfect
[20:48] <statik> and the cleartext is the content that was wrapped in the signature?
[20:48] <lifeless> or for detached sigs (but I don't think we do them today) it would be (the signature, text) tuple.
[20:48] <lifeless> statik: yes, thats right
[20:48] <statik> lifeless, thanks! I'll update the wiki
[20:49] <lifeless> thank you
[20:51] <abentley> lifeless: AIUI, documents can have multiple signed parts.  Maybe you want a list of signer/cleartexts?
[20:51] <lifeless> abentley: for our use cases today I believe that that would be an error
[20:52] <lifeless> they are - coc, source package uploads, control-of-signature proof.
[20:52] <lifeless> s/signature/key/
[20:58] <maxb> This is very weird. bac just closed bug 296365. The bug is linked to question 75760. LP sent me an email about linked bug status changing, but the textual message included in the email is not the one bac entered as comment #8, it's the one sinzui entered as comment #5 two years ago!
[20:58] <_mup_> Bug #296365: oops when responding to merge proposal review via email <email> <lp-foundations> <oops> <Launchpad itself:Invalid> < https://launchpad.net/bugs/296365 >
[20:59] <abentley> deryck: I'm doing the interrupt stuff now, and it's mostly very clean, but I think you forgot about RT.
[20:59] <deryck> abentley, I looked.  it looked like all spam to me, and I didn't see instructions on how to deal with it....
[20:59] <bac> maxb: that is odd
[20:59] <deryck> abentley, so I made a note to ask mrevell next week.
[21:00] <abentley> deryck: Oh.  I've been hitting "resolve" and setting the status to "deleted".
[21:00] <deryck> abentley, ah, ok.  that makes sense.
[21:00] <deryck> abentley, I'll do that as well from now on.
[21:15] <lifeless> deryck: what was the relevation ?
[21:15] <deryck> lifeless, that critical is not drop-everything-and-do-it-now but do-next.
[21:15] <lifeless> right
[21:16] <deryck> or rather do-fist when pulling new work
[21:16] <lifeless> uhm, I guess we failed to really communicate that change
[21:16] <deryck> yeah, I think so.
[21:16] <lifeless> critical as drop-everying-work-24-hours doesn't really make sense
[21:16] <deryck> I sort of knew it, but it didn't make sense.
[21:17] <deryck> we've ingrained critical as don't-stop-til-it's-fixed work for so long, it's hard to get free of that.
[21:17] <lifeless> fwiw as I understand Ubuntu's use of critical it is identical to ours
[21:17] <lifeless> *incidents* are don't stop :)
[21:17] <lifeless> but they are often not code bugs
[21:18] <deryck> it makes perfect sense when you realize the high bugs list is so long it's useless.  you need a real high category.  that's how I think of it now.
[21:18] <lifeless> yeah
[21:18] <deryck> useless is a bit strongly worded, but I hope you get my meaning
[21:18] <lifeless> does this interact with that hi pressure discussion we had last week?
[21:19] <deryck> yes, I feel better about marking ui regression bugs critical now, given that understanding of critical.
[21:19] <lifeless> cool
[21:20] <deryck> I would bet I am not allow in lp devs in not understanding this, too.
[21:20] <deryck> I think about bugs and statuses a lot and missed the direct meaning.
[21:21] <lifeless> we updated our docs when we shuffled this around back in oh feb
[21:21] <lifeless> perhaps you could check that its clear enough to carry the message, and perhaps even mail the list with pointers ?
[21:21] <lifeless> I'd hate for other folk to be unnecessarily stressed
[21:21] <deryck> sure.
[21:22] <deryck> I think its the way "burn the list to 0" meshes with the status that is confusing.
[21:22] <deryck> we beat the drum of clearing the list, as if this is don't-stop work, but in reality we're queuing up the next queue.
[21:22] <deryck> now I understand the next queue needs to be small enough to manage.  I'm not arguing over that.
[21:23] <deryck> and FWIW, people don't get meaning from wiki pages much.  it's more the day to day conversations.
[21:23] <lifeless> So the idea is that normally there will be approximately nothing in critical
[21:23] <lifeless> but if we have to queue jump some task, it will go into critical
[21:24] <lifeless> and get picked up by the next free engineer in a maintenance squad
[21:24] <deryck> sure, I get that.  but that's more in line with a stop-the-line and do this work flow, then what we have now.
[21:24] <deryck> it's the world 3-5 months from now, not now. ;)
[21:24] <lifeless> right
[21:24] <lifeless> we gotta clear the decks
[21:24] <deryck> sure, agreed.
[21:24] <lifeless> lots of bird poop piled up :)
[21:24] <deryck> indeed :0
[21:24] <deryck> :)
[21:42] <flacoste> SpamapS: nice blog post on ensemble!
[21:42] <flacoste> we now really need to fix these LP bugs as people will report bugs on principia!
[21:44] <SpamapS> Heh, yeah.
[21:44] <SpamapS> Maybe I should change the pre-bug-report text to make it clear you can't report against a formula yet?
[22:48] <LPCIBot> Project windmill-db-devel build #361: STILL FAILING in 1 hr 7 min: https://lpci.wedontsleep.org/job/windmill-db-devel/361/


[08:06] <pizzadude> hi, i upgraded from 16.04 to 16.10 and the sound indicator is just a slider
[08:06] <pizzadude> theres no play/pause
[08:06] <pizzadude> any way to fix this?
[08:09] <alkisg> For me it's a slider in 16.04 too
[08:12] <pizzadude> isn't there supposed to be play/pause?
[08:12] <pizzadude> i remember that being in 16.04
[08:12] <alkisg> Maybe it depends on the menu style? I'm using the redmont one
[08:12] <alkisg> I've also seen it in unity
[08:12] <alkisg> I don't remember if I've seen it on mate
[08:13] <pizzadude> so theres no play / pause for you?
[08:13] <alkisg> no
[08:13] <pizzadude> ok
[08:13] <pizzadude> hmm thats weird
[08:14] <pizzadude> also after the upgrade to 16.10 my wifi wouldn't work until i plugged in my ethernet cable and unplugged it
[08:14] <pizzadude> lol
[08:14] <alkisg> You wanted an non-LTS release :D
[08:14] <pizzadude> yeah
[08:14] <pizzadude> well i guess that's what non-LTS releases are like
[08:14] <pizzadude> broken and stuff :P
[08:14] <alkisg> Yup
[08:15] <pizzadude> oh well, im gonna upgrade to 17.04 right now because #yolo
[08:15] <alkisg> Haha
[08:15] <alkisg> That should fix everything :D
[08:15] <pizzadude> cya
[08:15] <pizzadude> yep
[08:15] <alkisg> bb
[08:15] <pizzadude> and introduce more problems maybe :P
[12:30] <Ceri_Philippe> good afternoon from France
[13:00] <nomic> .zz.
[14:02] <ouroumov_> flexiondotorg, hello. Do you know if a Failed Mandatory test on the QA tracker is enough to block a release? (If there's also someone else who cleared the test)
[14:03] <flexiondotorg> What bug?
[14:03] <ouroumov_> https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1047384
[14:03] <ouroumov_> http://iso.qa.ubuntu.com/qatracker/milestones/374/builds/144359/testcases/1451/results
[18:25] <cardboard-> Hello?
[18:26] <cardboard-> Hello?
[18:28] <at1984> ich brauche hilfe
[18:29] <at1984> wie kann ich wine auf ubuntu mate 16.04 installieren
[21:52] <Guest48642> Hello,May I ask question? About Software Boutique.
[21:53] <DarkPsydeLord> go ahead
[21:54] <Guest48642> Is it a known issue with some program when installing, encounter drive space warning. Even after I've already ran the resizing?
[21:58] <Guest48642> I tried both Rasp-config/advance/resize and fdisk /dev/mmcblk0 (on two separate time). Afterward, I ran Software Boutique, and it ask me to "Free up space" needing 40 more mb
[21:59] <Guest48642> Also, Thank you for listening
[22:04] <DarkPsydeLord> so this is rpi related
[22:05] <Guest48642> sorry, first time posting. Yes.
[22:05] <Guest48642> To ask it another way, not all apps within App Boutique are Armv7 compatible?
[22:10] <Guest48642> Thank you for taking time out to reply. Sorry to have bother y'all. I'll let myself out.
[22:58] <winfred> jo


[00:42]  * cyphermox -> back
[02:10] <imgbot> [02:25] <cyphermox> err
[02:53] <jhodapp> cyphermox, can I get a silo for line 78 please?
[03:10] <imgbot> [03:17] <charles> ah bfiller, thanks for picking up silo 12
[03:25] <imgbot> [03:25] <imgbot> [04:03] <cyphermox> jhodapp: certainly
[04:15] <imgbot> [04:15] <imgbot> [08:09] <vila> trainguards: It seems that devel-poposed #74 mako and #81 krillin fail to install on phones in the lab, is this known ?
[08:18] <sil2100> vila: hey, what do you mean 'fail to install'?
[08:18] <sil2100> vila: yeah, I heard some info from other people about that
[08:18] <jibel> vila, yes someone said that too on the ML
[08:19] <vila> sil2100: yeah, what jibel said + I'm seeing makos and krillins stuck at:
[08:19] <vila> 2015/01/23 05:25:19 Rebooting into recovery to flash
[08:19] <vila> + adb -s 04ed727c929709ba wait-for-device
[08:19] <sil2100> Let me see what landed
[08:20] <vila> sil2100: thanks
[08:22] <sil2100> vila, jibel: damn, this image had a lot - a new lxc, new udev, new lightdm, new gcc/glibc
[08:23] <vila> meh, and tha's #82 for krillins soryy
[08:42] <sil2100> Damn, my current device is busy so to say, as I'm testing Qt5.4 on it
[08:42] <sil2100> But let me re-flash and try seeing what's up
[09:01] <mzanetti> sil2100: good morning. sorry have to ask for a reconfig of 14. seems we have systemsettings-components dep in there
[09:09] <sil2100> mzanetti: done o/
[09:11] <mzanetti> sil2100: thank man
[09:30] <popey> aaaargh
[09:32] <popey> I give up.
[09:33] <sil2100> popey: awww!
[09:33] <sil2100> Google hangout problems?
[09:43] <pstolowski> trainguards hello, can you check the changes in landing-15 and land it?
[09:50] <sil2100> pstolowski: hey! Been in a meeting, dealing with this in a moment :)
[09:50] <ogra_> silly browser
[09:50] <pstolowski> sil2100, thanks
[09:56] <vila> sil2100: any news on the devel-proposed images ?
[09:57] <sil2100> vila: not yet, only recently I got my phone bricked, will investigate a bit in a moment
[09:57] <vila> sil2100: ack
[09:57] <sil2100> (had trainguard stuff to do)
[09:58] <dbarth> hi trainguards; silo 017 (vivid) can be deleted, we landed the branch from another silo already
[09:59] <sil2100> dbarth: ACK
[10:01] <sil2100> pstolowski: looking good, publishing - took a while since someone sorted debian/control dependencies ;)
[10:03] <pstolowski> sil2100, np.. oh, let me take a look what's unapproved
[10:04] <pstolowski> sil2100, one branch got updated in the meantime.. approved now
[10:11] <sil2100> Updated?
[10:11] <sil2100> pstolowski: if a branch got updated we'd need the packages rebuilt
[10:12] <sil2100> pstolowski: otherwise not only will we be landing outdated stuff, but also the merge will fail
[10:13] <pstolowski> sil2100, uh, you're right, thanks!
[10:30] <mzanetti> sil2100: hey, yesterday kgunn added u-s-c to my silo, but then we pulled it out again because it wasn't ready. Now I have the package in the silo and it fails to build: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-014/+packages
[10:30] <mzanetti> is that a problem?
[10:30] <mzanetti> the others seem to build fine
[10:33] <sil2100> mzanetti: u-s-c seems to build fine there - but let me remove it from the PPA for you, if you want
[10:33] <sil2100> In the past it was done by CI Train, but after some modification the train stopped doing that
[10:35] <mzanetti> ah, ok
[10:35] <sil2100> mzanetti: you want me to delete it?
[10:36] <mzanetti> sil2100: to be clear, u-s-c stands for unity-system-compositor
[10:36] <sil2100> Aaaa
[10:36] <mzanetti> not the ubuntu-settings-components package in there
[10:36] <mzanetti>  :D
[10:36] <sil2100> ... ;)
[10:36] <mzanetti> only saw it now that it matches for both :D
[10:36] <sil2100> Ok, should I remove the compositor then?
[10:36] <mzanetti> yes please
[10:37] <sil2100> mzanetti: it's normal it fails to build on those two arches btw.
[10:37] <sil2100> Missind mir deps IIRC
[10:37] <mzanetti> right. just caused the dashboard to report the silo as failed
[10:37] <mzanetti> so I wasn't quite sure about it
[10:40] <dbarth> ogra_: ping? sorry to bother you again; it's about the signon extension
[10:41] <ogra_> dbarth, yeah, sorry i'll try to get to it today, snappy is keeping me busy, havent worked on phone stuff this year yet
[10:43] <dbarth> ogra_: ok, nw and thanks for taling that on your plate; i just want to make sure it's on your radar
[10:43] <dbarth> let me know if you need me to do anything else
[10:44] <ogra_> you, bzoltan_ and silo11 are on my phone radar for today :)
[10:47] <rsalveti> ogra_: do you know if someone already investigated why we can't boot the latest image?
[10:47] <rsalveti> vivid
[10:48] <ogra_> rsalveti, see devel
[10:48] <pstolowski> sil2100, i have rebuilt and retested the affected package in silo 15, should be good now
[11:01] <bzoltan_> ogra_:  so no chance to push an update for the sdk seeds
[11:03] <ogra_> bzoltan_, oh, why ? what happened ?
[11:05] <bzoltan_> ogra_:  Sorry ... I though you write to me that "silo11 are on my phone radar for today" ... I missed the "and"
[11:27] <sil2100> jibel: hey, regarding the regression in gallery... does it only happen when the SD card is full of pictures, or is it also the same case when the internal storage is full?
[11:28] <jibel> sil2100, it works better with internal storage, but you cannot store as many photos than on a 16G SD Card. And maybe it's faster too.
[11:28] <sil2100> jibel: ah, ok, since I was wondering if actually backing up SD support will help
[11:29] <sil2100> (for me lack of SD support in gallery or camera would be basically a ship stopper)
[11:30] <jibel> sil2100, it's also a ship stopper if you have support but it doesn't work
[11:30] <sil2100> Yeah, just saying that reverting won't help, as we need this fixed anyway
[11:30] <jibel> sil2100, I think someone from bfiller's team should have a look, if there is no obvious fix revert and reland it in a later milestone
[11:31] <sil2100> It's up for management to decide, but for me that's a rather crucial feature from the POV of a customer
[11:31] <sil2100> Just saying
[11:31] <victorp> sil2100, hi
[11:31] <sil2100> victorp: hey!
[11:32] <victorp> so we cant ship as it is now
[11:32] <sil2100> victorp: what's the decision? Can we ship without no support for SD-cards in gallery?
[11:32] <victorp> I am not sure that is true about not having sd support for camera and gallery
[11:32] <sil2100> *without
[11:32] <jibel> sil2100, you'll have the case where users take the SD card from a previous phone, already loaded with photos and it'll just won't work
[11:33] <sil2100> jibel: I'm not saying we want to release it like it is now, I'm saying we don't want to release it with no support as well
[11:33] <victorp> sil2100, it is not great but we cant ship a broken phone
[11:33] <victorp> sil2100, right but if we back it out, that doesnt mean we should not keep working on it
[11:33] <sil2100> Sure
[11:34] <victorp> maybe wait til bfiller and pmcgowan are up, but I am for backing it out at the mo
[11:36] <sil2100> From what I see it's around since some time, so we'll have to wait for bfiller anyway since I probably can't revert it 'the packaging way'
[11:36] <sil2100> Too many changes inbetween
[11:36] <sil2100> We'll need bfiller to revert it himself
[11:38] <ogra_> victorp, sil2100, i once understood that we wanted to wait with implementing SD access in apps until the new planned SD card framework is there ... seems that didnt happen
[11:38] <ogra_> (so that not all apps have their own implementation of accessing the card)
[11:39] <victorp> sil2100, I think sd card support on the gallery and camera just landed though
[11:40] <victorp> but yeah, might more "commenting" code out..
[11:40] <victorp> what I dont understand is why the camera freezes at boot.. what is the camera doing with the sd card?
[11:41] <sil2100> victorp: right, but sadly it landed with a full vivid sync, so with many many changes - best if bfiller just removes the SD bits and leaves all other bugfixes
[11:43] <ogra_> victorp, on "boot" or on app startup ?
[11:43] <victorp> app startup
[11:43] <victorp> sil2100, ah yes, ofcourse
[11:43] <victorp> forgot that..
[11:43] <victorp> sil2100, maybe there is a quick fix
[11:44]  * victorp hope
[11:44] <victorp> s
[12:03] <bzoltan_> sil2100:  the sil10 is mature for publishing ... it brings cool feature
[12:04] <sil2100> ;)
[12:04] <sil2100> Oh, upgrade notification!
[12:04]  * sil2100 publishes
[12:05] <mzanetti> sil2100: something is still wrong on silo 14... the ppa and the spreadsheet hold unity8 and ubuntu-settings-components
[12:05] <mzanetti> while the dashboard shows unity8 and ubuntu-system-compositor
[12:05] <sil2100> huh
[12:05] <sil2100> mzanetti: did you reconfigure after removing ubuntu-system-compositor?
[12:05] <mzanetti> sil2100: no, you did today morning
[12:05] <mzanetti> haven't changed the spreadsheet since
[12:06] <mzanetti> then the dashboard actually was fine
[12:06] <sil2100> mzanetti: hm, maybe it didn't 'catch it'
[12:06] <mzanetti> but now after it finished building the dashboard is wrong again
[12:06] <sil2100> Let me retry
[12:07] <mzanetti> I tried to reconfig now in the hope it would just update the dashboard without actually changing the silo. but wouldn't allow me
[12:09] <mzanetti> now it looks better, thanks
[12:10] <sil2100> Not sure what happened before that
[12:10] <sil2100> yw!
[12:11] <sergiusens> victorp: sil2100 the camera doesn't need to land in vivid, just in the click store; the landing into the archive is a legacy part of a process
[12:11] <sil2100> sergiusens: yep, I know
[12:12] <sergiusens> and it an update to the app requires no image build
[12:12] <sergiusens> of course that doesn't solve first boot xp
[12:30] <sil2100> tvoss: hmm
[12:49]  * sil2100 goes off to lunch
[12:49] <sil2100> o/
[13:07] <brendand> sil2100, i need something on the spreadsheet to indicate a row concerns a click package landing
[13:08] <brendand> sil2100, will it contain the full name of the click package?
[13:09] <brendand> sil2100, i can always check it ends with .click
[13:11] <rsalveti> sil2100: ogra_: so what can we do with lxc?
[13:11] <rsalveti> should we revert that? wait stgraber to show up?
[13:12] <ogra_> i would do the latter
[13:12] <rsalveti> would be nice to fix that before the weekend starts
[13:13] <ogra_> yep
[13:18] <jibel> bfiller, I'm rejecting silo 009, the dialer crashed.
[13:36] <rsalveti> tvoss: lool: you need to update lxc-android-config at https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu-rtm/landing-017
[13:36] <rsalveti> there was another upload in RTM since that package got available in there
[13:36] <rsalveti> 11 days ago :-)
[13:36] <tvoss> rsalveti, ah, thanks for the hint
[13:39] <brendand> sil2100, can you confirm that lines for click packages will have a 'request ID'?
[13:48] <Ursinha> brendand: how are you using citrain for clicks if that sends packages to PPAs? how is that going to work? (honest question)
[13:49] <brendand> Ursinha, sil2100 is dealing with the citrain side of things. i'm just modifying the code to create trello cards
[13:51] <Ursinha> sil2100: are you modifying citrain to also build clicks?
[13:53] <Ursinha> sil2100: from the last time I've spoken with robru, he was intending to work on the last bits to migrate away from the spreadsheet, adding more functionality to citrain means more things will have to be put in place to support the migration. if he's already aware of this change then it's fine :)
[13:53] <om26er> Chipaca, Hi!
[13:54] <Chipaca> om26er: verily!
[13:54] <jibel> Ursinha, no, the goal is to just store the information in the spreadsheet so we can track landings of click packages, devices and custom tarballs.
[13:54] <om26er> Chipaca, can you help me with silo 7 testing ?
[13:54] <Chipaca> om26er: sure
[13:54] <jibel> Ursinha, nothing fancy
[13:54] <Ursinha> jibel: thanks for the information
[13:54] <Chipaca> om26er: what are you looking to test?
[13:55] <om26er> Chipaca, what exactly do I need to verify the fix ? Also do I not need to run the TestPlan for it ? (As its not linked in the spreadsheet)
[13:55] <om26er> well, more or less I need to verify the bug is fixed.
[13:55] <Chipaca> om26er: you can run the test plan if you want, but it doesn't cover the issue this fixes
[13:55] <Chipaca> right
[13:55] <Chipaca> om26er: well, in a deep sense the bug is _not_ fixed
[13:55] <Chipaca> om26er: but i can show you how to reproduce it, and show you that after this change you can no longer reproduce it
[13:56] <Chipaca> om26er: we do still have further work to do on this, but it's big enough that we decided to release with this change first, which makes it a lot less likely
[13:57] <om26er> Chipaca, from what I understand we are fixing the issue to some extend. So perhaps the steps should be added to the TestPlan as well ?
[13:58] <om26er> *extent rather.
[13:58] <Chipaca> om26er: maybe, but i'm not sure it's a good idea. let me help you do it this time, and if you think it's reasonable as part of a test plan i'll do it
[13:58] <sil2100> rsalveti, ogra_: so the package at fault was lxc in the end?
[13:59] <sil2100> rsalveti, ogra_: we could prepare everything for a revert and wait for stgraber to appear
[13:59] <ogra_> sil2100, yes, we're waiting for stgraber
[13:59] <sil2100> brendand: it won't have an UID I think, since it's just a hack - you need to have that?
[13:59] <lool> rsalveti, tvoss: Thanks
[13:59] <ogra_> might just be that we need to simply adjust something in our setup for the new version
[13:59] <lool> rsalveti: yeah I didn't notice because I was dpkg -i installating it
[14:00] <sil2100> Ursinha: no, the CI Train will not build clicks ;) No modifications in the train, it's just a convinience thing requested by QA
[14:01] <Ursinha> sil2100: understood, thanks :) though the spreadsheet will now be used to track these requests, so we will have to add same functionality to the spreadsheet replacement UI to allow that
[14:02] <sil2100> Ursinha: sure, but that's not critical to have right now, it's a new addition that doesn't have to be covered instantly
[14:02] <brendand> sil2100, it would make things easier for me but if it makes things much harder for you i can always work around it
[14:02] <Ursinha> brendand: sil2100, that's fine, really, I'm just trying to make sure that changes are well communicated so there are no surprises after
[14:04] <sil2100> brendand: hm, let me think about that, since the UID would have to be auto-generated here
[14:04] <sil2100> But it's doable
[14:05] <jibel> Ursinha, the goal is to use the same workflow for any type of landing independently of the format of the packages.
[14:05] <Ursinha> jibel: that's what we want to do :)
[14:05] <jibel> Ursinha, good :)
[14:06] <om26er> Chipaca, ok, I'll wait for the procedure to verify the fix.
[14:07] <Chipaca> om26er: it's short-form described in the spreadsheet
[14:08] <Chipaca> om26er: let me know if that's not enough
[14:11] <om26er> Chipaca, that is not clear enough. which 'push client' should be running ?
[14:12] <pstolowski> trainguards hello, can we get a silo for line #82?
[14:15] <sil2100> boiko: could you top-approve https://code.launchpad.net/~thomas-voss/location-service/allow-for-disabling-providers/+merge/241707 ?
[14:15] <sil2100> boiko: wait
[14:15] <sil2100> boiko: https://code.launchpad.net/~boiko/telephony-service/rtm-fix_1398427/+merge/246996 I meant
[14:15] <sil2100> (wrong paste in the pastebin)
[14:15] <boiko> sil2100: yep
[14:15] <sil2100> Thanks
[14:16]  * mzanetti disagrees
[14:17] <sil2100> pstolowski: should be assigned!
[14:17] <mzanetti> boiko: hmm strange... I'm quite sure I approved them already yesterday
[14:18] <Chipaca> om26er: stop ubuntu-push-client && /usr/lib/ubuntu-push-client -log_level debug
[14:20] <Chipaca> om26er: stop ubuntu-push-client && /usr/lib/ubuntu-push-client/ubuntu-push-client -log_level debug
[14:20] <Chipaca> om26er: sorry for the first one :)
[14:21] <om26er> Chipaca, I figure that. But how do I actually verify the bug/fix ? Is there a way to create dummy push notifications ?
[14:22] <Chipaca> om26er: ah! give me a moment please
[14:24] <Chipaca> om26er: on the phone, assuming you have telegram installed, do:
[14:24] <Chipaca> gdbus call -e -d com.ubuntu.PushNotifications -o /com/ubuntu/PushNotifications/com_2eubuntu_2etelegram --method com.ubuntu.PushNotifications.Register com.ubuntu.telegram_telegram
[14:24] <Chipaca> om26er: take the token that returns, and on a computer where you have network and push checked out, do:
[14:25] <Chipaca> ./scripts/unicast  -H push.ubuntu.com TokenTokenToken== com.ubuntu.telegram_telegram '"potato"'
[14:25] <Chipaca> om26er: you should see that arrive in the push client and be handed off to the helper
[14:26] <Chipaca> (the helper isn't going to like it, but you should see it get that far)
[14:36] <lool> rsalveti, tvoss: Uploaded lxc-android-config rtm9 rebased on rtm archive version
[14:36] <lool> tvoss: is this in the QA pipeline already?
[14:36] <tvoss> lool, let me check
[14:36] <tvoss> lool, should be
[14:39] <popey> jibel: davmor2 we need to postpone music app testing till monday for translation updates, but clock still needs doing :)
[14:40] <alf_> cihelp: Hi! All mir mako builders seem to either be offline or stuck. Any idea what's going on?
[14:41] <jibel> popey, OK, that reminds me that the card had not been created. Where can I grab the click package for the clock app?
[14:41] <davmor2> popey: I'll add aticket now and jump on it after I finish the sanity on 209 should be about 45 minutes or so
[14:41] <jibel> davmor2, I can take the clock
[14:41] <jibel> just finished adb
[14:42] <davmor2> jibel: ah okay I think popey has an etherpad with manual tests iirc
[14:42] <davmor2> or was that just music
[14:42] <popey> jibel: http://pad.ubuntu.com/kY99vztlmS is the clock details - changelog from nik90 and link to click package contained in there
[14:43] <jibel> popey, nice, thanks!
[14:43] <om26er> Chipaca, do these logs look good? I haven't received a notification with or without the silo. https://pastebin.canonical.com/124100/
[14:44] <Chipaca> om26er: you got the notification, right there in the logs
[14:44] <Chipaca> 2015/01/23 14:42:15.885873 DEBUG posted unicast notification BkgDh6MOEeSf9/oWPmWXaQ== for com.ubuntu.telegram_telegram.
[14:45] <om26er> Chipaca, aah, so Nothing in the UI was expected ? hmm.
[14:45] <Chipaca> om26er: the message itself was rubbish (literally the word "potato"), so it wasn't translated into something you would see in the UI
[14:45] <Chipaca> om26er: karni might be able to give you a better string that'd translate into something you can see
[14:45] <Chipaca> om26er: him being the telegram guy :)
[14:45] <Chipaca> om26er: but for this issue, just that is enough
[14:46] <Chipaca> om26er: now, those logs are from the fixed version
[14:46] <popey> davmor2: tests are in the source, linked from the pad
[14:46] <popey> thanks chaps!
[14:46] <Chipaca> om26er: give it a go with the non-fixed (you don't need to re-register)
[14:46] <Chipaca> om26er: i'm off to fetch my kids from school, but will be back in ~1h
[14:47] <vila> alf_: see topic, the current devel-proposed image is broken
[14:47] <vila> sil2100: any update ?
[14:48] <sil2100> vila: we're waiting for stgraber to appear, since it's the new lxc causing touble
[14:48] <vila> sil2100: ack
[14:48] <alf_> vila: ah, thanks
[14:48] <sil2100> The decision has been made to wait and not revert for now
[14:48] <om26er> Chipaca, ok, I think its not really working after doing the thing with wireless network
[14:49] <Chipaca> om26er: what does 'nmcli nm' say? are you connected to the network?
[14:49] <om26er> Chipaca, connected
[14:49] <Chipaca> om26er: can i see the logs?
[14:50] <om26er> Chipaca, https://pastebin.canonical.com/124101/
[14:51] <Chipaca> om26er: hm, give it a few, it should sort it out
[14:51] <Chipaca> i've got to run
[14:52] <om26er> sure
[15:01] <jhodapp> sil2100, I can't seem to find my spreadsheet entry anymore that I added last night for vivid silo 25...I think it got eaten
[15:02] <sil2100> huh
[15:02] <sil2100> jhodapp: we had some strangeness happening with the spreadsheet indeed
[15:02] <sil2100> hm
[15:03] <jhodapp> lol, I still have my silo :)
[15:03] <sil2100> jhodapp: will you be able to add it once again? Sorry about that, I'll connect it to the silo ;)
[15:03] <jhodapp> sure thing
[15:03] <sil2100> The spreadsheet only holds additional info (like description and comments) and is only used in the assignment phase
[15:05] <jhodapp> sil2100, line 88
[15:05] <sil2100> jhodapp: thanks!
[15:05] <sil2100> jhodapp: hooking it up
[15:05] <jhodapp> no thank you :)
[15:07] <sil2100> jhodapp: should be hooked up again ;)
[15:10] <ted> trainguards, Could I get silos for lines 85/86 please? rtm/vivid
[15:11] <sil2100> ted: sure! In the middle of that ;)
[15:11] <ted> Heh, cool, thanks!
[15:13] <sil2100> ted: yw! So, I assigned the vivid one but remember that you have url-dispatcher in silo 003 already
[15:13] <sil2100> RTM assigned without any conflicts
[15:13] <ted> sil2100, Yeah, silo3 is to that they can test the trusted session changes. I don't expect that to land for a while.
[15:27] <dbarth> o/ trainguard on line 69 please
[15:34] <u_glide> Hello guys! Does autopilot able to introspect QQuickWidget (http://doc.qt.io/qt-5/qquickwidget.html) ?
[15:55] <oSoMoN> trainguards: can silo 8 be published please?
[16:03] <sil2100> o/
[16:05] <jibel> popey, I still have AP tests to run but manual verification of the clock app looks good. I'll give you the final result later today.
[16:06] <nik90> jibel: Yay :)
[16:07] <popey> jibel: excellent. nice work nik90 :)
[16:11] <Chipaca> om26er: back. how's things?
[16:21] <ogra_> pmcgowan, could you categorize bug 1413622 i would like to do the seed change in the same package upload as for bug 1392380
[16:23] <sil2100> brendand: hey, just had a moment to take a look at the UID thing and sadly it would be a bit risky to add
[16:23] <sil2100> brendand: since even though the addition of that could be possible, but it would then require us to change a lot of the spreadsheet code - which carries potential risk of everything breaking badly
[16:24] <pmcgowan> ogra_, all set
[16:24] <ogra_> thx
[16:26] <brendand> sil2100, ok i'll have to think of a workaround then
[16:27] <brendand> sil2100, see i have a check in my code to see if the uid is there, surely for a good reason
[16:27] <brendand> sil2100, got to see if i can remove it somehow
[16:27] <sil2100> brendand: you could do it contitionally (as a hack) and check for UID and if no UID is there, then look for the [non-citrain] string somewhere
[16:27] <sil2100> brendand: I'm still trying to move it to a different column btw.
[16:35] <sil2100> ogra_: do you have a short moment for a packaging ACK?  https://ci-train.ubuntu.com/job/ubuntu-landing-013-2-publish/lastSuccessfulBuild/artifact/packaging_changes_dbus-test-runner_15.04.0+15.04.20150116-0ubuntu1.diff
[16:35] <Chipaca> om26er: I'm back. how's things?
[16:36] <ogra_> sil2100, do we have that version in rtm ?
[16:36] <ogra_> or is that for vivid only
[16:36] <om26er> Chipaca, I replied, internet failed me. https://pastebin.canonical.com/124120/
[16:36] <sil2100> ogra_: vivid only for now
[16:36] <om26er> Chipaca, it never detected network
[16:37] <Chipaca> om26er: from the log, it carried on trying to detect it though
[16:37] <om26er> Chipaca, but internet was there, working just fine. Is there an "expected" time that would happen ?
[16:37] <ogra_> sil2100, ACK then
[16:38] <sil2100> ogra_: thanks!
[16:39] <Chipaca> om26er: i don't know what's going on, then. What "that" do you mean wrt "time that would happen"?
[16:43] <om26er> Chipaca, hmm, now it seems to work sometimes, fails the other. Which I guess is expected as this is not a full fix ?
[16:43] <Chipaca> om26er: i would've expected you to see it fail only rarely
[16:43] <Chipaca> om26er: so it's interesting that you're able to make it fail, unless you're doing more than the "for i in `seq 5`; do frob the network" thing
[16:44] <om26er> Chipaca, in 5 attempts it failed twice.
[16:47] <Chipaca> om26er: and without the fix?
[16:48] <om26er> Chipaca, I think I was reading the logs wrong. This has been working, right.
[16:52] <om26er> Chipaca, I'll re-try without the silo and evaluate the different, will update you when I am done. Sorry for the confusion.
[16:54] <Chipaca> om26er: no worries, it's a relief. Thank you and looking forward to it.
[16:55] <om26er> Chipaca, what does this DEBUG message mean:
[16:55] <om26er> connectivity: connection check says: false
[16:56] <om26er> there is no internet or that it stopped looking for connection ?
[16:59] <oSoMoN> trainguards: can I have an RTM silo for line 91, please?
[17:06] <sil2100> tvoss: https://code.launchpad.net/~thomas-voss/dbus-cpp/fix-1396985/+merge/243063 <- needs approval
[17:06] <popey> dpm: will you be around to do a clock upload (assuming jibel has finished testing soon)
[17:11] <Chipaca> om26er: 'connection check says: false' means it tried to download a file from the internet and failed, meaning that although network manager thinks it's connected, it's not
[17:11] <Chipaca> om26er: sorry for the delay responding, didn't see the popup
[17:11] <om26er> no problem, I was in a call.
[17:20] <popey> dpm: actually, don't worry, it won't be ready till a bit later or even over the weekend
[17:45] <om26er> Chipaca, I have done some thorough testing now. The overall situation does not seem to change with or without the silo. On some reconnects it just does not detect the network connection even after a few minutes.
[17:46] <Chipaca> om26er: can i have debug logs for when it didn't work, please?
[17:47] <om26er> Chipaca, https://pastebin.canonical.com/124130/
[17:48] <cyphermox> robru: don't hesitate to ping me if you need help with landings.
[17:48] <Chipaca> om26er: how many times were you reconnecting the network during that test run?
[17:48] <Chipaca> om26er: looks like 62 times, from the logs
[17:48] <om26er> Chipaca, yes, with a loop, with sequence of 5
[17:49] <om26er> Chipaca, my point is, it was pretty much the same without the silo as well.
[17:49] <robru> cyphermox: thanks
[17:50] <Chipaca> om26er: are you sure you actually had network at the end, there? my AP needed restarting after I'd done this a few times (not sure i reached 60+ reconnections)
[17:51] <Chipaca> om26er: could you also pastebin the one _without_ the ppa?
[17:52] <Chipaca> om26er: (fwiw, i see no evidence of a deadlocked client in those logs, although it's probably academic if it's decided not to connect)
[17:54] <om26er> Chipaca, the problem is it does not detect the internet, not talking any deadlocks.
[17:54] <om26er> Chipaca, I have had that cleared, would need to get fresh logs without silo.
[17:54] <Chipaca> om26er: ok. are you sure you had internet though? because it tried to download that page and failed with a network error
[17:55] <Chipaca> it'll retry after a number of seconds, as long as network manager still thinks it's connected
[17:55] <Chipaca> or it should :)
[17:55] <om26er> Chipaca, I think it retries after exact 1min so if it didn't find internet when the connection was established, it never does even after a minute.
[17:56] <om26er> Chipaca, also internet should be working, its the same wifi as my laptop and IRC never disconnected.
[17:57] <Chipaca> om26er: 10 minutes
[17:58] <Chipaca> om26er: 10 minutes between web checks
[17:58] <om26er> "not connected after 1m0s; giving up"
[17:58] <Chipaca> om26er: you can configure that, specifying e.g. -recheck_timeout=1m
[17:58] <Chipaca> om26er: that's about account-polld, not the webcheck
[17:59] <Chipaca> push client asks for a hardware wakeup, waits a bit for the network, goes back to sleep
[17:59] <Chipaca> not related to this
[17:59] <om26er> Chipaca, The code change doesn't seem to regress anything, so perhaps it could have something to do with my internet
[18:00] <Chipaca> om26er: i really want to know why you got stuck now :)
[18:00] <Chipaca> om26er: can we do another run, changing some config values?
[18:01] <om26er> Chipaca, "yes we can"
[18:01] <Chipaca> om26er: probably easiest if you edit the config file, in /etc/xdg/ubuntu-push-client
[18:01] <Chipaca> om26er: double everything that looks like a time, except for recheck_timeout :)
[18:01] <Chipaca> or maybe i pastebin a config file
[18:02] <Chipaca> gimme a sec
[18:02] <tvoss> sil2100, done
[18:03] <Chipaca> om26er: https://pastebin.canonical.com/124135/
[18:03] <Chipaca> ooh, look, it's nearly beer o'clock
[18:04] <om26er> Chipaca, just restart the client ?
[18:04] <Chipaca> om26er: yup
[18:07] <sil2100> o/
[18:07] <robru> sil2100: goodnight
[18:08] <sil2100> robru: I'll still be around to finish up some discussions and e-mails, but I published the 2 silos above and leaving everything else in your hands
[18:08] <sil2100> robru: remember, in case you don't feel too well, ping cyphermox
[18:08] <sil2100> :)
[18:09] <robru> sil2100: ok thanks
[18:10] <om26er> Chipaca, it might have something to do with my network, in another tab if I login to the phone, even the ping to google.com sometimes just timesout.
[18:11] <Chipaca> om26er: or the phone getting confused because of all the network frobbing
[18:11] <Chipaca> om26er: you might need to reboot it (or the router)
[18:11] <Chipaca> om26er: sorry :)
[18:11] <Chipaca> my router just refused to give it an ip after i'd tested this a number of times
[18:16] <Chipaca> om26er: i'm afraid i've got to go start the evening routine here at home. I'll check back in a while, but won't be able to sit down for a few hours.
[18:17] <om26er> Chipaca, alright, I think this is not something that needs to land immediately ? so perhaps if not today, we can land early next week.
[18:17] <Chipaca> om26er: the sooner the better, as this is breaking telegram for some people, but if we can't make it today we can't
[18:21] <robru> cyphermox: when are you taking your lunch?
[18:23] <cyphermox> robru: thirty minutes or so from now, I have a coquille saint-jacques in the oven :)
[18:24] <robru> cyphermox: ah ok. let me know when you get back and then I'll go
[18:24] <cyphermox> don't hesitate, I'll eat in front of my computer
[18:28] <tvoss> brendand, you still around?
[18:57] <om26er> Chipaca, for, when you get back https://pastebin.canonical.com/124147/
[18:58] <om26er> Chipaca, that is after the changes you suggested to the config. So I am pretty confident, my network aint the only problem.
[19:05] <imgbot> [19:14] <om26er> cyphermox, Hi!
[19:14] <cyphermox> om26er: howdy sir
[19:15] <om26er> cyphermox, if i connect bluetooth to my car and play a song that works fine the first time but if I disconnect it and reconnect the bluetooth the sound stutters and lags.
[19:15] <om26er> cyphermox, but I don't see that issue with my bluetooth headsets. which is bluetooth 3.0
[19:16] <om26er> cyphermox, is there a way to check the bluetooth version of my car through terminal or something ? also what logs should I try to gather ?
[19:17] <cyphermox> maybe bluez-test-device <address> info tells you? I don't remember if that's an actual command
[19:19] <cyphermox> om26er: that or hciconfig -a, but in reality it's not a straightforward "you have this version", but usually rather a case of what features are provided
[19:19] <cyphermox> oh wait, since you're asking about the car, that would be more hcitool inq <address>
[19:19] <kenvandine> rsalveti, i passed by silo 18 again... i'll rebuild it again once this is merged
[19:20] <rsalveti> kenvandine: thanks, no worries, sorry not yet done with it
[19:20] <kenvandine> no worries
[19:32] <om26er> cyphermox, what does that translate to:
[19:32] <om26er> clock offset: 0x0d01	class: 0x240408
[19:32] <cyphermox> "wrong command", that just says what kind of device it is
[19:35] <cyphermox> om26er: I'm sorry, clearly I can't do this from memory
[19:35] <cyphermox> I think you want hcitool info instead... otherwise I wouldn't know how to get the information
[19:36] <cyphermox> om26er: thing is, even that might not really help, because the stuttering could be due to something completely different
[19:36] <om26er> cyphermox, ok. But can you please look through this syslog: http://paste.ubuntu.com/9839085/
[19:36] <cyphermox> you're streaming audio from the phone to the car?
[19:36] <cyphermox> oh
[19:36] <om26er> cyphermox, yes, local mp3 in the phone through bluetooth.
[19:37] <om26er> yes it started Skipping when I reconnected the bluetooth and played the song.
[19:37] <cyphermox> insufficient signal maybe?
[19:37] <cyphermox> does it ever pick it back up or does it keep skipping for a long while>
[19:37] <cyphermox> ?
[19:38] <om26er> cyphermox, I am inside the car, so very close to the system.
[19:38] <om26er> cyphermox, it keeps on skipping
[19:38] <cyphermox> om26er: have you filed a bug about it?
[19:39] <om26er> cyphermox, never had the change to sit in the car with a laptop previously :)
[19:39] <cyphermox> I'd have to dig in pulseaudio code to figure out why it would skip
[19:39] <om26er> cyphermox, it happens with both mako and krillin FWIW.
[19:41] <cyphermox> ok
[19:41] <om26er> cyphermox, can you tell me which package to report the bug against ?
[19:41] <cyphermox> om26er: please open the bug against bluez
[19:42] <cyphermox> since you said your test was working with a bluetooth headset, it's likely not pulse... and probably not bluez either
[19:44] <cyphermox> om26er: if you're up to doing more testing, it would be nice to compare the output of hcitool lq <address> before and after suspend for the car, and for the headset
[19:45] <om26er> yeah, I am testing (and collecting more logs)
[20:19] <om26er> cyphermox, Ok. I reported the bug. Attached hcidump,  syslog and link quality. bug 1414142
[20:20] <om26er> brb
[20:25] <imgbot> [20:25] <imgbot> [21:12] <ogra_> cyphermox, if you find some time ... ^^
[21:12] <cyphermox> of course
[21:12] <cyphermox> ogra_: are you adding a proper fr_CA keyboard layout? :D
[21:13] <ogra_> dunno, did canda switch to bosinan or croatian recently ?
[21:13] <ogra_> or emoji ?
[21:13] <ogra_> :)
[21:14] <cyphermox> ouh, shiny.
[21:14] <cyphermox> unfortunately, all silos are taken
[21:14] <ogra_> dang
[21:14] <ogra_> ok
[21:14] <cyphermox> kenvandine: rsalveti: can we drop the bluetooth agent rework thing for now?
[21:14] <cyphermox> (or better yet, can we just land it? :)
[21:15] <ogra_> cyphermox, err, wait, i need rtm
[21:15] <cyphermox> ah
[21:15] <kenvandine> it would need a rebuild first
[21:15] <kenvandine> or drop it
[21:15] <cyphermox> well it's for RTM so nevermind
[21:15] <kenvandine> i should have another settings landing tonight still, so i was holding off rebuilding 18
[21:15] <cyphermox> kenvandine: ack
[21:15] <ogra_> yeah, there are a few free ones
[21:15] <cyphermox> ogra_: how come you didn't set the spreadsheet accordingly?
[21:16] <ogra_> did i not ?
[21:16]  * ogra_ checks
[21:16] <cyphermox> has it already landed in vivid?
[21:16] <ogra_> sorry
[21:16] <ogra_> no
[21:16] <ogra_> its a seed change
[21:16] <cyphermox> no worries, but it explains the issue
[21:16] <cyphermox> ok
[21:16] <ogra_> i'll line up the vivid seeds on the weekend
[21:18] <cyphermox> ok
[21:20] <ogra_> merci !
[21:25] <cyphermox> ogra_: np!
[22:15] <pmcgowan> om26er, woot!
[22:16] <om26er> ;)
[22:29] <charles> trainguards, the MP for ubuntu-rtm/landing-012 is top-approved now, so publishing now shouldn't block on "some merges are unapproved"
[22:30] <cyphermox> bfiller: Kaleo: you know camera-app is already in another silo? just want to make sure before I override that warning.
[22:31] <cyphermox> charles: ok
[22:32] <bfiller> cyphermox: yup that's fine
[22:32] <cyphermox> charles: it will take a bit even if I refresh it's not top-approved for me...
[22:32] <charles> ...? /me re-looks
[22:32] <bfiller> cyphermox: you can ignore warning
[22:33] <cyphermox> ok
[22:33] <charles> cyphermox, you're correct, looks like the URL I passed to wellark to top-approve was the vivid MP rather than the rtm MP
[22:41] <robru> cyphermox: charles: btw if this happens again, the publish log will say specifically which MPs need to be approved: https://ci-train.ubuntu.com/job/ubuntu-rtm-landing-012-2-publish/31/console
[22:42] <charles> robru, ty :)
[22:42] <robru> charles: you're welcome
[22:42] <robru> charles: and that's linked from the dashboard, since the train-guard may not think to send you the link
[22:44] <Kaleo> cyphermox, ??
[22:46] <cyphermox> robru: you're back
[22:46] <robru> cyphermox: oh yeah sorry, i have a pounding headache
[22:48] <cyphermox> no worries
[22:48]  * cyphermox gets back to his soup
[23:03] <robru> ogra_: no qa for rtm 15?
[23:20] <robru> cyphermox: https://ci-train.ubuntu.com/job/ubuntu-rtm-landing-004-2-publish/lastSuccessfulBuild/artifact/packaging_changes_ubuntu-download-manager_0.9+15.04.20150123~rtm-0ubuntu1.diff need a core dev ack when you get a sec
[23:20] <cyphermox> sure
[23:24] <cyphermox> robru: go
[23:24] <robru> th
[23:24] <robru> thx


[07:34] <dholbach> good morning
[11:36] <notgary> Does anyone here know how I can have a regular event added to the Fridge Calendar (http://fridge.ubuntu.com/calendars/)?
[15:45] <holstein> notgary: regular?
[15:46] <notgary> holstein, I've got it figured out now.
[15:46] <holstein> cheers!