[01:03] <spiv> Hmm, I think I just found a hack to improve the test suite time by about 10%.
[01:06] <poolie> nice
[01:10] <poolie> what was it?
[01:12] <lifeless> rm -r <some dir>
[01:14] <spiv> Yep, seems to work: have _check_safety_net just open .bzr/checkout/dirstate directly and compare the raw bytes to its known pristine state, rather than open_workingtree and check .last_revision()
[01:14] <spiv> Which perhaps hints we can optimise opening a working tree a little more, but this is easier ;)
[01:16] <spiv> (And perhaps we can improve further by just using stat, but that's probably not worth the complexity)
[01:31] <poolie> indeed
[01:31] <poolie> +1
[01:41] <spiv> Hmm, I thought I'd targetted that branchbuilder patch to lp:bzr/2.4.  I wonder if I entered lp:bzr/2.4 into the text field without also clicking the radio button...
[01:48] <poolie> :/
[01:48] <poolie> spiv your branch has conflicts
[01:48] <poolie> so you probably need to resubmit anyhow
[01:48] <poolie> or fix it before mine completes
[02:03] <spiv> poolie: thanks, looking now
[02:06] <spiv> Oh, lp:bzr/2.4 is the same as lp:bzr.  I got the impression that we'd split them already.
[02:08] <spiv> Just in time to avoid resubmitting :)
[02:15] <poolie> we were meant to have split but vila hasn't done it
[02:15] <poolie> maybe we should
[06:29] <vila> poolie, spiv: lp:bzr shouldn't be the same as lp:bzr/2.4 AIUI, at least I've seen poolie sending a cleanup on lp:bzr and that's ok, the plan is to open lp:bzr as 2.5dev1. A few commits before that won't matter.
[06:31] <vila> poolie: I think we should keep the minimum API to 2.4.0 for a little while so plugin authors can focus on releasing for 2.4 without having to handle 2.5
[06:38] <vila> poolie: Does delaying the API bump sounds ok ?
[06:39] <spiv> vila: Well, https://launchpad.net/+branch/bzr/2.4 still resolves to ~bzr-pqm/bzr/bzr.dev
[06:40] <poolie> vila, i'm not sure what you mean
[06:40] <poolie> there might have been api changes on trunk that would not be appropriate post-final-beta
[06:41] <poolie> if that's true, we should branch off 2.4 from a previous revision
[06:41] <vila> spiv: eerk
[06:41] <spiv> vila: Poking around I see there is a lp:~bzr-pqm/bzr/2.4, but that's not where lp:bzr/2.4 resolves to
[06:41] <poolie> possibly we should branch from the revision tag anyhow
[06:41] <vila> poolie: no no
[06:41] <vila> spiv: yup, that's the bit I missed, hopefully we can fix that without losas
[06:41] <vila> poolie: there is no known API break that I know
[06:43] <vila> poolie: I'm talking about bumping to 2.5. Last time we did this bump early, I don't want to make it *too* early
[06:44] <vila> at a minimum, not when opening for 2.5dev1
[06:44] <poolie> you're talking about when to change the api version vs the library version?
[06:44] <vila> After 2.4.0 sounds about right
[06:44] <vila> yes
[06:44] <poolie> i think the separate api version is almost a null concept
[06:44] <vila> ha
[06:44] <poolie> iow i think people should just depend on the implementation version
[06:45] <poolie> i don't think the api version is reliable enough to be worth while
[06:46] <poolie> i don't think the api version is reliable enough to be worth while
[06:46] <vila> hmm, ok, in this case we should decide if we deprecate that and make it widely known
[06:46] <poolie> there is a bug complaining about it
[06:46] <vila> so in the short term, I can just open 2.5dev1 and leave it at that (and also fix the lp:bzr/2.4 associated branch)
[06:48] <poolie> can we be more concrete?
[06:48] <poolie> i think the actions are
[06:48] <poolie>  - branch off bzr/2.4 from trunk
[06:48] <poolie> - increment the version in trunk
[06:48] <poolie> ...?
[06:48] <poolie> - add pqm configuration for 2.4 if needed?
[06:48] <vila> branch off and pqm are already done
[06:49] <vila> and I have a branch to switch to 2.5dev1 where I should commit and land
[06:49] <poolie> but the 2.4 series in lp is pointing at the wrong branch?
[06:49] <poolie> - add news and other document stubs
[06:49] <vila> last, lp:bzr/2.4 should point to lp:~bzr-pqm/bzr/2.4
[06:50] <poolie> right
[06:50] <vila> yup, document stubs are uncommitted but done
[06:51] <vila> I need to create a 2.5 series and some milestones on lp
[06:52] <vila> (while ensuring doc/developers/releasing.txt is still up to date)
[06:59] <poolie> ok, thanks for taking care of it
[07:11] <poolie> vila, babune seems unreachable
[07:11] <vila> restarted
[07:12] <poolie> i was wondering if spiv's changes would have made things faster
[07:13] <vila> which ones ?
[07:14] <poolie> he did a thing to make selftest faster at checking whether it needs to make a new scratch directory
[07:14] <vila> hmm, just looking at it
[07:14] <spiv> vila: r6020
[07:14] <vila> but the dirstate doesn't protect against repository changes
[07:15] <vila> we talked about making the branch/repo read-only but I don't think we ever implemented that
[07:18] <spiv> It's no weaker than the check it replaces
[07:18] <spiv> Which was just wt.last_revision() == 'null:'
[07:18] <vila> spiv: yup, just saw that
[07:18] <jam> morning all
[07:18] <vila> spiv: may be it should :)
[07:19] <spiv> vila: well, maybe
[07:19] <spiv> vila: except that this check has proved quite sufficient for years
[07:19] <poolie> hi there jam
[07:19] <spiv> So I think probably the effort to make it stricter is probably not worth it :)
[07:19] <vila> spiv: did you see it trigger often ?
[07:19] <vila> I know I never did
[07:19] <spiv> vila: a better question is:
[07:20] <poolie> is this about the guard wt above the tests?
[07:20] <spiv> vila: did you ever see a problem that a stricter check would have avoided or helped with?
[07:20] <spiv> vila: I never have.
[07:20]  * vila nods
[07:20] <poolie> it's a little kludgy that it's even there
[07:29]  * spiv -> gone for the day
[07:43] <poolie> bye spiv
[07:50] <vila> poolie: all done, 2.5dev1 sent to pqm
[07:51] <vila> there will probably some tweaks needed to move news entries from 2.4 to 2.5 for the ones landed since the fork
[07:59] <poolie> ok good, thanks
[07:59] <poolie> jam, how are you?
[08:07] <Riddell> good morning
[08:09] <poolie> hi Riddell, how are you?
[08:09] <jam> poolie: doing pretty good
[08:09] <jam> did you enjoy your vacation?
[08:09] <jam> seems you were productive on the flight back againg
[08:10] <poolie> i did
[08:10] <poolie> it was pretty good
[08:10] <poolie> i got a bit closer to getting usertest to do what i want too
[08:10] <poolie> i hope to get back to that tomorrow or wednesday
[08:11] <poolie> jam, how did you go with the performance bug that was affecting linaro?
[08:12] <jam> poolie: bzr-svn peak memory issues? I got a little ways, but mostly I have to learn the bzr-svn codebase a bit
[08:13] <jam> they are unblocked for now, because of the manual improt
[08:13] <jam> import
[08:14] <Riddell> poolie: I'm bright and breezy and looking forward to another exciting week of bzr
[08:14] <poolie> :) great
[08:15] <poolie> any topics in particular? something on the developer guide perhaps?
[08:15] <poolie> jam, so what's next for you?
[08:15] <jam> I was hoping to meet up with Jelmer today
[08:15] <jam> once he wakes up
[08:15] <jam> and finish the "is branch up-to-date" stuff
[08:15] <poolie> did you see his mail? he won't be back for another day
[08:15] <poolie> *2 days
[08:16] <poolie> vila, according to the wiki you're pp this week; will that fit with your RM work?
[08:16] <Riddell> poolie: yes I began looking at the packaging guide, I'll make some changes to it.  although the main problem with it is working out how to sensibly split the UDD stuff and the traditional packaging stuff (which mostly isn't in it)
[08:17] <poolie> yes, that is a big question
[08:17] <poolie> depending a bit on how much this is supposed to be a description of the future vs practically useful today
[08:21] <poolie> spiv's selftest change doesn't seem to have especially made a visible change on babune
[08:21] <poolie> but, there is a fair bit of noise
[08:21] <poolie> oh, it did on maverick
[08:21] <poolie> http://babune.ladeuil.net:24842/job/selftest-chroot-maverick/buildTimeTrend
[08:21] <poolie> perhaps natty just ran when the machine was busy
[08:30] <vila> poolie: argh, how did I manage to miss that :(
[08:31] <vila> poolie: don't answer :)
[08:31] <poolie> which bit?
[08:31] <vila> pp'ing this week
[08:31] <poolie> oh that's ok
[08:31] <vila> yeah, the queue is pretty short
[08:34] <vila> poolie: regarding spiv change: yeah, looks noticeable on maverick and lucid but not on natty
[08:35] <vila> they run serialized and the machine was quiet otherwise so, a priori, no external noise
[08:35] <vila> we'll see if the progress persists but it's a good improvement
[08:51] <jam> maxb: ping for great justice! (Actually just to ask you what happened to your code that checks if a package-import branch is up-to-date.)
[08:57] <jam> maxb: I found: https://code.launchpad.net/~jelmer/bzr-builddeb/check-udd-status
[08:57] <jam> but jelmer said you made it much faster by avoiding launchpadlib
[08:57] <jam> and I don't see a ~maxb branch of bzr-builddeb
[08:58] <poolie> jam i wonder what the action is on lp ssh performance
[08:59] <poolie> since it's partly just waiting for it to get to the top of the queue
[09:02] <jam> poolie: the last state-of-the-losa report said it was being worked on
[09:02] <poolie> oh, really
[09:02] <jam> (getting ha proxy at least)
[09:02] <poolie> that's great
[09:03] <poolie> i rebuilt on natty and it did get faster
[09:03] <poolie> so, go spiv
[09:03] <jam> "Partial de-spof of codehosting in process "
[09:03] <jam> I'm inferring a bit there
[09:03] <jam> but haproxy would be getting rid of a SPOF
[15:37] <bigjools> can anyone help with this please http://pastebin.ubuntu.com/641976/ - bzr switch thinks  that something I just branched is not a branch :(
[15:57] <maxb> bigjools: I'd guess that your current checkout is a checkout of a local branch since deleted?
[15:58] <bigjools> maxb: gah, yes
[15:58] <bigjools> thanks
[15:58] <bigjools> what a weird error though
[15:58] <maxb> well, ish
[15:59] <bigjools> I guess it would help if I'd realised it was referring to a different branch to the one I just tried to switch to!  /o\
[15:59] <maxb> It's a perfectly sensible error, but thrown from too low-level a point in the code, and not decorated with suitably informative context
[16:58] <muep> hello
[17:00] <muep> is there something roughly equivalent to git fetch origin && git log master..origin/master in bzr?
[17:01] <muep> I'd like to see the changelog before I actually apply the new upstream changes
[17:03] <AuroraBorealis> just branch upstream and do a bzr log on it?
[17:04] <AuroraBorealis> bzr branch <orgin> && bzr log <orgin> or something
[17:07] <maxb> muep: 'bzr missing --theirs-only' ?
[17:08] <muep> looks somewhat what I am looking for
[17:20] <muep> is it safe to mv a directory to which I have cloned an upstream bzr-using project?
[17:24] <muep> I currently have just trunk cloned in src/emacs/ and I guess to get other local branches I would need to get some other directory
[17:24] <muep> so I though I should maybe move my current copy to src/emacs/trunk and branch my local branches from that alongside it
[20:16] <jamdahl> Hey guys, I'm having a problem with bzr explorer not launching from its shortcut
[20:17] <jamdahl> anytime I try to open bzrw.exe, nothing happens
[20:26] <AuroraBorealis> is the launch argument like this? "C:\Program Files (x86)\Bazaar\bzr.exe" explorer
[20:36] <jamdahl> not exactly"C:\Program Files (x86)\Bazaar\bzrw.exe" explorer
[20:36] <AuroraBorealis> should still work. whats bzr.log say?
[20:36] <AuroraBorealis> should be in your documents folder
[20:36] <AuroraBorealis> .bzr.log i think
[20:37] <jamdahl>  Mon 2011-07-11 16:36:30 -0400 0.041  bazaar version: 2.2.3 0.041  bzr arguments: [u'explorer'] 0.044  looking for plugins in C:/Users/jamdahl/AppData/Roaming/bazaar/2.0/plugins 0.044  looking for plugins in C:/Program Files (x86)/Bazaar/plugins 0.125  encoding stdout as osutils.get_user_encoding() 'cp1252' 0.255  loading explorer extensions for clothes ['Bazaar support', 'Register on Launchpad'] 0.255  explorer extensions provided by th
[20:37] <jamdahl> gah, limit to length
[20:37] <AuroraBorealis> pastebin
[20:37] <AuroraBorealis> that shiz
[20:38] <jamdahl> http://pastebin.com/q81TeHum
[20:39] <AuroraBorealis> hmm weird
[20:41] <jamdahl> when I run bzr explorer from command line I get the same NoRepositoryPresent: No repository present: "file:///C:/" line
[20:42] <AuroraBorealis> is it trying to autoload a repository?
[20:42] <AuroraBorealis> try deleting your config for bzr explorer and see if that fixes it
[20:43] <jamdahl> Where is it?  I've tried deleting the folder in appdata/roaming
[20:45] <jamdahl> that was the first thing I tried when reinstalling failed... pesky config files...
[20:45] <AuroraBorealis> yeah
[20:45] <AuroraBorealis> its %appdata%/Roaming/Bazaar
[20:46] <jamdahl> Yep, I've deleted that and if I run bazaar explorer it will regenerate that directory but still doesn't launch a gui
[20:49] <AuroraBorealis> are you running the latest version of both bzr and explorer?
[20:49] <jamdahl> thankfully I can call pretty much everything else in bzr and qbzr from the command line
[20:49] <AuroraBorealis> i dunno what its doing trying to load C:
[20:50] <jamdahl> I'm using one of the standalone packages
[20:50] <jamdahl> if I have the wrong version of python it isn't my fault :P
[20:51] <jamdahl> and it's not exactly the latest version but I'm downloading that now
[20:51] <jamdahl> I was using 2.2.3
[20:51] <jamdahl> downloading 2.3.3 now
[20:52] <AuroraBorealis> it comes bundled with python so you don't need that
[20:53] <jamdahl> That's what I'm saying :P
[20:55] <jamdahl> updating to latest version of bzr did not change anything
[20:56] <AuroraBorealis> hmm =/ i dunno
[20:56] <jamdahl> aha
[20:57] <jamdahl> I've been writing a plugin for excel to use bzr for VBA version control
[20:57] <jamdahl> it got a bit messy at ttimes
[20:57] <jamdahl> apparently at one point it did an init on the c drive
[20:57] <jamdahl> apprently bazaar didn't like that and tried to autoload it or somethign
[20:57] <jamdahl> deleting the repo in the c drive fixed it
[20:58] <AuroraBorealis> nice =)
[21:03] <jamdahl> too bad I can't find a satisfactory tool to diff sheets themselves
[21:06] <jamdahl> anyway, thanks for the help aurora
[21:06] <Noldorin> is it possible to edit old commit messages?
[21:24] <maxb> Noldorin: no
[21:24] <Noldorin> maxb, is this feature being considered? i know it was at some point.
[21:24] <AuroraBorealis> dunno why you would want to
[21:24] <Noldorin> AuroraBorealis, typos in past messages, basically
[21:24] <Noldorin> AuroraBorealis, or accidental misinformation
[21:25] <maxb> Noldorin: The immutability of revisions is pretty much baked deep into the fundamental precepts of bzr (and git and hg)
[21:26] <maxb> The only way that I can see it could ever be implemented is via some sort of "No, actually I meant ..." metadata attached to future revisions, which masked the appearance of earlier revisions in the UI
[21:26] <Noldorin> maxb, that's not what i heard. was talking to one of the guys who designed the bzr system, a couple of years ago here, and he said it would be possible
[21:26] <Noldorin> maxb, he said it would be hard and require some changes to the way hashing was done or something, but possible
[21:26] <maxb> Sounds like you should ask him then :-)
[21:27] <maxb> But in any case, it's definitely a Hard Problem, and I've not heard of anyone seeking to address it recently
[21:28] <Noldorin> maxb, oh yeah, i totally agree it's non-trivial :-)
[21:28] <Noldorin> maxb, was discussed briefly on the mailing list before i think...wish i knew the guy's name i once talked to.
[21:28] <spiv> maxb: to be precise, I think it'd be possible to have that metadata not necessarily be "attached to future revisions"
[21:28] <maxb> The benefit seems quite low compared to the necessary expenditure of effort, which makes it a feature fairly unlikely to be worked on
[21:29] <spiv> maxb: but it would need to be stored in the repo somehow, and we'd need to figure out how/when to transmit it efficiently, etc.
[21:29] <maxb> Hi spiv
[21:29]  * maxb now has jubany access :-)
[21:30] <spiv> maxb: yay!
[21:30] <Noldorin> maxb, possibly, though bzr is fairly mature these days...there can't be *that* many more important thigns?
[21:30] <Noldorin> well, perhaps there are
[21:31] <Noldorin> maxb, spiv right, so what's making the problem trickier than simply editing the metadata file for the repo with the new comit message?
[21:32] <maxb> Suppose you edit the embedded metadata of a revision in one repository... how does bzr know it needs propagating to other repositories?
[21:33] <maxb> How do you manage the auditability of such changes - or otherwise prevent them from being done maliciously?
[21:33] <Noldorin> maxb, a simple boolean flag? either per branch or per revision
[21:33] <maxb> boolean? What happens when I want to edit my edit? :-)
[21:33] <spiv> Noldorin: "per branch" doesn't work, a repository can be used by many branches, and the number can change over time
[21:34] <maxb> And what about if two people edit a revision in conflicting ways?
[21:34] <spiv> (And similarly a revision can be propogated any number of times)
[21:34] <Noldorin> maxb, spiv ok, so i'm being naive. the only thing that would really work is versioning the commit messages *themselves* :-P
[21:34] <Noldorin> having each commit message essentially as a file
[21:35] <Noldorin> maxb, that would seem to solve all those issues
[21:35] <spiv> Noldorin: you could prototype that approach as a plugin
[21:36] <Noldorin> spiv, oh yes?
[21:36] <maxb> Of course, once you start down this path, people will want to edit metadata other than messages :-)
[21:36] <spiv> Noldorin: store the extra info in a secondary store next to the regular repo
[21:36] <spiv> Noldorin: and hook into bzr's fetch etc logic to do the propagation the way you envisage
[21:37] <spiv> Noldorin: I think that it'd be an interesting (and useful) way to prototype it.  I also think you'll find it's harder than it looks ;)
[21:37] <Noldorin> spiv, no doubt it will be quite hard, yeah. good suggestion though
[21:37] <Noldorin> spiv, just thinking, would the functionality really be so different to bzr tags?
[21:38] <spiv> There *might* be one or two points in bzrlib that don't make it as easy to write that plugin as it ought to be -- file a bug if you find them, they can be fixed.
[21:38] <spiv> It is different to tags, because tags are per-branch
[21:38] <spiv> (and not versioned either :P)
[21:39] <Noldorin> spiv, the tags list is simply merged in the case of a conflict i suppose?
[21:40] <spiv> See bzrlib/tag.py; if there's a conflict bzr reports it and lets the user sort it out basically.
[21:41] <spiv> And tag deletion isn't propagated.
[21:41] <Noldorin> spiv, in terms of merges you mean?
[21:41] <spiv> (See also https://bugs.launchpad.net/bzr/+bugs?field.tag=tags)
[21:42] <spiv> Noldorin: well try it yourself: make a test branch with two commits, branch it, and do 'bzr tag foo -r1' in one and 'bzr tag foo -r2' in the other
[21:42] <spiv> Noldorin: and see what happens if you try push/pull/merge between those
[21:46] <Noldorin> spiv, right
[21:46] <AuroraBorealis> what should i include in a bug report for bzr explorer?
[21:46] <AuroraBorealis> just my bzr log?
[21:46] <Noldorin> spiv, so wouldn't it be easier just to patch the source rather than do a plugin?
[21:46] <Noldorin> spiv, since i'd really want to modify the metadata structure. otherwise it owuld work too differently to an intended working version
[21:47] <spiv> Hmm, much of it would be the same, and it would probably avoid requiring a new repo format if you did it as a plugin that used a secondary store.
[21:48] <Noldorin> spiv, yeah, we'll see...
[21:48] <Noldorin> brb for now
[21:48] <spiv> I guess it would be easier to patch bzr proper, but it's also harder for people to test a patch
[21:48] <Noldorin> cheers for the info
[21:48] <Noldorin> spiv, yeah, so it might not get known as quickly
[21:48] <Noldorin> hmm
[21:48] <Noldorin> i'll consider. bye for now
[21:48] <spiv> And I don't think it would be *that* much easier.
[21:48] <spiv> I might be wrong :)
[22:04] <putrycy> hi! Let's assume that I am working on some project. In some point in the past I gave the source to my friend. He has been coding and how he is sending the modified source to me. In the meantime I made some changes too
[22:04] <putrycy> what is the simpliest way to merge?
[22:04] <putrycy> From my point of view of course
[22:05] <spiv> putrycy: how did they send the modified source to you?
[22:05] <putrycy> only source files
[22:05] <spiv> Ah.
[22:05] <putrycy> they don't have access to the repository
[22:05] <spiv> Ideally you'd have been using bzr branches from the start.
[22:05] <putrycy> nor they use bazaar
[22:06] <putrycy> so, I should make a branch usning the received source files?
[22:06] <spiv> Still, in your case the best you can do is basically make a branch starting from the revision they started from
[22:06] <spiv> (i.e. 'bzr branch -r 1234 my-branch friend-branch')
[22:07] <spiv> then in friend-branch apply their changes (copy their version of the source files into it)
[22:07] <spiv> then commit that, and then use 'bzr merge' to merge that back into my-branch
[22:08] <putrycy> OK, I get it, thank you very much
[22:08] <putrycy> btw isn't there anything like patch in bazaar?
[22:08] <spiv> You're welcome.
[22:08] <spiv> Sure, the 'bzrtools' plugin adds a 'bzr patch' command
[22:08] <putrycy> and does it resolve my problem too?
[22:09] <spiv> But you said you had entire source files, not patches?
[22:09] <putrycy> yes, of course
[22:09] <putrycy> just looking for the simpliest way to merege
[22:10] <putrycy> It would be perfect If I could make patch using the source tree and the branch from that they started development
[22:10] <putrycy> and then just apply the patches
[22:10] <spiv> Sure, you can use 'bzr diff' to generate patches, but I don't think it'd be easier (I don't think it'd be significantly harder either)
[22:11] <spiv> If you already have patches, then just applying the patches is almost certainly the way to go.
[22:11] <putrycy> I have to try out both to find out...
[22:22] <sidnei> so, how easy is it to split a bzr branch while keeping history?
[22:30] <putrycy> yesterday i noticed some strange (for me) bahaviour: bzr didn't want to add any files to the repository if there was a .svn directory in the same director what an added file
[22:30] <putrycy> could somebody explain it to me? And how to overcome it?
[22:39] <dupondje> https://bugs.launchpad.net/ubuntu/+source/bzr/+bug/809048 any idea whats broken ?
[22:39] <ubot5`> Ubuntu bug 809048 in bzr (Ubuntu) "bzr crashed with AttributeError in stopTest(): '_TypeEqualityDict' object has no attribute 'clear'" [Undecided,New]
[22:44] <lifeless> dupondje: what python version ?
[22:44] <lifeless> putrycy: you have bzr-svn installed
[22:45] <lifeless> putrycy: so that is detecting you have an svn checkout there and is working with that instead
[22:46] <dupondje> Python 2.7.2+ (default, Jul 10 2011, 09:48:58)
[22:46] <dupondje> ubuntu oneiric
[22:47] <lifeless> dupondje: I suspect testcase.__dict__ isn't what it used to be in earlier pythons ;)
[23:02] <poolie> hi all


 Do you think telling Ben64 to pay attention if he wants to play op is an acceptable comment for a support channel?
[09:59] <reisio> obviously, why else would I have said it
[10:00] <reisio> do you think it's acceptable for people to badger people _giving support_ and _receiving support_
[10:00] <IdleOne> I see. Well your ban is now 3 months long.  I am swamped atm
[10:11] <reisio> sure
[10:11] <bazhang> ok thanks
[10:12] <bazhang> see you then
[10:12] <reisio> and you :)
[11:30] <jrib> so what's with the "hi i'm here and ready to ddos" thing?  Some post on a social media site or something?
[11:30] <ikonia> dunno
 at tanagra
[11:33] <bazhang> mernolio
 i tried to start darmok at tanagra but it won't run
[11:35] <bazhang> at +1 and #u respectively
[11:36] <jrib> bonus for star trek reference but he didn't stop...
[12:02] <ikonia> jrib: the ban I set a few minutes ago should already catch that
[12:02] <jrib> ikonia: aren't you filtering by nick?
[12:02] <ikonia> no, ident
[12:03] <ikonia> yes, I am I screwed up
[12:03] <ikonia> well spotted
[12:03] <ikonia> thanks jrib
[13:12]  * LjL is leaving for vacation. Will often connect, but be unable to work on the bots that run from the server at home (I think it's only one FloodBot at this point that's of concern to you), while of course I will still be able to access the ones on ubottu.com.
[13:29] <ikonia> hello dicaxa
[13:30] <ikonia> dicaxa: hello ?
[13:30] <dicaxa> I would pound you in the ass if I wanted to catch alcoholism.
[13:30] <ikonia> ahh
[13:30] <dicaxa> Suck off an amputee
[13:30] <ikonia> dicaxa: could you stop for a moment please.
[13:30] <ikonia> dicaxa: do you know the rules of using the ubuntu channels ?
[16:23] <IdleOne> If idoru is catching those "hi i'm here and ready to ddos" in other channels it means that when they do it i n #ubuntu and don't get a kline it is because they are not doing it in other channels where idoru is. Really think we need to ask staff to bring idoru into #ubuntu again.
[16:24] <DJones> If it wasn't for Dr_Willis as support in #u, we could just set a ban on *_*@* in #u, that would seem solve the problem
[16:24] <Myrtti> "lol"
[16:25] <DJones> IdleOne: I think idoru coming back might be a short term answer
[16:25] <ikonia> it's not exactly massive problem though
[16:25] <ikonia> just kick them out
[16:25] <ikonia> they aren't doing anything to cause a problem
[16:25] <Myrtti> it's not a problem for you *now*
[16:25] <Myrtti> it was quite bad few nights ago
[16:25] <IdleOne> it was a massive problem two days ago
[16:26] <ikonia> Myrtti: sure, but if you just keep knocking them out of the channel, it's not a problem
[16:26] <DJones> If they get left in the channel, they seem to be disruptive
[16:27] <DJones> If I see one, I remove & they don't appear to rejoin, I'm assuming that they end up klined from other channels so never get the chance to come back and cause problems
[16:27] <IdleOne> I know we had some problems with idoru way back when, but aiui she has been upgraded some and false klines should no longer be an issue.
[16:28] <ikonia> idoru is just doing the same as us though, kicking them out of the channel
[17:00] <DJones> Is that right though, does idoru just kick from the channel, or does it consolidate spam/trolling from multiple channels and then remove/kline netwrok wide
[17:02] <Myrtti> it doesn't kick from the channel, it kills network wide
[17:05] <DJones> That was what I thought, basiclly consolidates network wide spam and kicks from freenode, if thats all it does, I can't see any reason not to have it in #u
[17:07] <DJones> If it doesn't conflict with what ubottu does, I can't see any conflict
[17:07] <Myrtti> what might happen more is if someone posts the same question with /amsg to several channels
[17:07] <Myrtti> like #debian and #ubuntu and some others at the same time, it might interpret it as spam
[17:10] <DJones> Which technically, probably would be considered spam, if it was Ubuntu related I'd expect it in #ubuntu, if it was debian releated then in #debian, if they post post the same thing in both channels, then they're their own worst enemies
[17:46]  * DJones wonders if LjL-Alps is skiing down them & irc'ing at the same time :) DON'T DO IT
[17:46] <IdleOne> if you do, pics!
[17:47] <DJones> Is that before/after and without/with plaster casts
[17:48] <IdleOne> I'm flexible
[17:49] <DJones> :) You're not the one falling off a mountain
[20:43] <LjL-Alps> HisaoNakai: hi
[20:43] <HisaoNakai> -sigh- hi, LjL-Alps :(
[20:44] <LjL-Alps> HisaoNakai: seems some of our ops hate nickname-based practical jokes
[20:44] <LjL-Alps> you can't blame them, after all the times i used that sort of joke, it gets tiring
[20:44] <HisaoNakai> Um, hi folks. Just got IP banned from #ubuntu-offtopic (not sure if intentionally or unintentionally) for playing what I consider to be a minor prank. op concerned - ikonia . Humbly wish to know whether 1. it was knowingly or not so, 2. whether it has a time limit, 3. whether or not it is considered a mite excessive, and 4. whether clean past record has any bearings on it. Sincerely.
[20:45] <HisaoNakai> LjL-Alps - Ah.
[20:45] <HisaoNakai> I dunno, man, straight off IP ban seems a bit excessive. It was pretty immature, yeah, but IP ban? wat.
[20:45] <LjL-Alps> HisaoNakai: i'll do something that's usually not done here, and override that ban immediately. note the op involved may reinstate it once he comes back
[20:46] <ikonia> I won't
[20:46] <ikonia> I just find the tripe being spewed offensive
[20:46] <ikonia> and it's tiresome
[20:46] <HisaoNakai> Thank you and my apologies, LjL-Alps , ikonia .
[20:46] <HisaoNakai> :S
[20:48] <LjL-Alps> HisaoNakai: no problem, have fun
[20:48]  * HisaoNakai bows
[22:29] <k1l_> does anyone know whats up with that ddos script in #ubuntu? if my log is correct its 51 so far last days
[23:28] <ikonia> hello dolphin-man
[23:28] <dolphin-man> hi
[23:28] <ikonia> what's up? how can we help ?
[23:32] <ikonia> dolphin-man: hello ?
[23:35] <ikonia> dolphin-man: if you don't need anything could you please part the channel and come back if/when you do need something
[23:35] <dolphin-man> one sec, i am one the phone but ill be off on in a a sec, and then ill present my issue
[23:35] <ikonia> no problem
[23:42] <ikonia> dolphin-man: probably best you part the channel and come back when you are off the phone
[23:42] <ikonia> (please)
[23:48] <ikonia> ahh welcome back dolphin-man
[23:48] <ikonia> all finished ?
[23:50] <ikonia> dolphin-man: hello ?
[23:54] <ikonia> dolphin-man: are you free now ?
[23:54] <ikonia> @mark #ubuntu-ops dolphin-man back to trolling behaviour joining #ubuntu-ops but not speaking, clearly at keyboard to rejoin
[23:56] <ikonia> hello dolphin-man are you off the phone/free now ?
[23:56] <dolphin-man> sorry was on the phone, you kept kicking me so i kept hitting the up key and enter
[23:56] <ikonia> dolphin-man: why ?
[23:56] <ikonia> dolphin-man: I clearly said "do not rejoin until you can talk"
[23:56] <ikonia> why did you keep rejoining ?
[23:56] <ikonia> anyway - how can we help ?
[23:56] <dolphin-man> I didn't read what you said, i just saw I was kicked
[23:56] <dolphin-man> oh okay
[23:56] <dolphin-man> yes
[23:57] <dolphin-man> I'm wondering how to become a ubuntu op
[23:57] <dolphin-man> also ikonia
[23:57] <ikonia> not doing the behaviour you've been doing is a good start
[23:57] <dolphin-man> @mark is a reference to mark shuttleworth?
[23:57] <ikonia> behaviour
[23:57] <ikonia> no, it's a mark in our logs
[23:57] <ikonia> as in comment
[23:58] <ikonia> !canibeanop | dolphin-man
[23:58] <dolphin-man> If I make a large donation to Canonical would I stand a better chance?
[23:58] <ikonia> dolphin-man: if you read that info that should give you anything you need
[23:58] <ikonia> no, money won't change anything
[23:58] <ikonia> but you're welcome to donate
[23:58] <dolphin-man> ok
[23:59] <ikonia> anything else ?
[23:59] <dolphin-man> yeah, i want to create a new account from the command line
[23:59] <ikonia> then ask in #ubuntu
[23:59] <dolphin-man> but for some reason its not working correctly anymore
[23:59] <ikonia> that's the technical support channel
[23:59] <dolphin-man> oh okay
[23:59] <dolphin-man> i didnt know you dont use ubuntu


[00:10] <balloons> popey, not yet. But I will re-run once fixed
[00:20] <Guest4112> where can i find help with developing a quickfixj applicaiton on ubuntu does anyone know?
[00:21] <Guest4112> I'm trying to debug a quickfixj connection issue
[02:53] <nipuna> Hello there, I'm a new developer hoping to take part in the scopes showdown, right now I'm having trouble with setting up the emulator
[02:54] <nipuna> Could someone please tell me why the devices tab says, "The device is currently booting..." Even when the emulator is up and running?
[02:54] <nipuna> Pressing the refresh button does not do any change either.
[03:02] <nipuna> appdevs
[09:32] <JamesTait> Good morning all!  Happy Tuesday, and happy Pancake Day! 🙌
[09:45] <nik90> popey, ping
[09:50] <popey> hello nik90
[09:50] <popey> Sorry for bugspam
[09:50] <nik90> popey, nah I like seeing these small papercut bugs :)
[09:50] <popey> :)
[09:50] <nik90> about bug https://bugs.launchpad.net/ubuntu-clock-app/+bug/1543496, I think with the UC 1.3 migration it is mostly gone.
[09:50] <ubot5`> Launchpad bug 1543496 in Ubuntu Clock App "‘Shutter’ effect animation on title bar when opening bottom edge should not be present." [Undecided,New]
[09:51] <popey> Great!
[09:51] <popey> I was copy/pasting bugs from a design review doc, so sorry if I missed things which are fixed but not landed.
[09:51] <nik90> About https://bugs.launchpad.net/ubuntu-clock-app/+bug/1543476, may I ask why you want the clear button to be shown?
[09:51] <ubot5`> Launchpad bug 1543476 in Ubuntu Clock App "stopwatch: Start & Clear should be visible before stopwatch started" [Undecided,New]
[09:51] <nik90> oh these are from design review?
[09:52] <popey> yes
[09:52] <nik90> I was under the impression that the new design doc only shows a "start" button in the stopwatch page.
[09:52] <popey> These come from updated design specs for buttons
[09:52] <popey> which I'm attempting to get access to for you
[09:52] <nik90> Ok. I will target all these bugs against the 3.7 milestone which is intended for MWC.
[09:53] <popey> Awesome, thank you nik90
[09:53]  * popey files one more
[09:53] <nik90> the new design is more or less done thanks to bartosz and michael predotka.
[09:53] <nik90> will follow up with them about what's left.
[09:53] <popey> Apologies if there's a lack of detail. if you have any more questions which are design specific we can poke JMulholland :)
[09:53] <popey> his name is all over this  😃
[09:54] <nik90> sure, no problemo
[09:54] <popey> JMulholland: specifically, could you tell me what colour is appropriate for https://bugs.launchpad.net/ubuntu-clock-app/+bug/1543501 ?
[09:55] <ubot5`> Launchpad bug 1543501 in Ubuntu Clock App "settings: wrong font colour (purple) for section titles" [Undecided,New]
[10:41] <davidcalle> popey: what's your solution for Marvin to interact with the app? I'm looking into autopilot for scopes and I'm not fond of it. Not for running tests, just a sequence of taps on the screen.
[10:48] <popey> davidcalle: good question. currently don't have a solution
[10:49] <popey> davidcalle: would like a really simple streamlined way of injecting presses, press-hold and swipe
[10:50] <popey> dpm: am i right in saying there's currently no possible way to run x86 unity8 on any known device?
[10:50] <popey> (specifically installing clicks in said environment)
[10:57] <popey> (which I assume is why you're using debs)
[11:01] <popey> Pondering if it's really worth pushing fat packages to the store, given nobody uses them on x86 devices
[11:06] <davmor2> davidcalle: lego mindstorm robotic arm?
[11:07] <davidcalle> davmor2: :D
[11:07] <davmor2> popey: I think that is mostly because you don't have access to the click store from the desktop so people use the ppa that they can install though right?
[11:08] <davmor2> popey: might be different if more people were trialling unity8 on desktop maybe
[11:11] <popey> davmor2: You do have access to the click store on some builds I've seen, but installing clicks fails
[11:11] <dpm> popey, I'm not sure I understand the question, but here's what I did, in case that helps:
[11:11] <popey> davmor2: I don't think we're ever going to support clicks on the desktop
[11:11] <popey> dpm: my point is about having fat (armhf/i386/amd64) clicks in the store
[11:11] <dpm> - installed the unity8-mir-desktop-session package (or whichever the right name is) on my xenial desktop
[11:11] <dpm> ah, I see where you come from
[11:12] <popey> We used to have an image that worked, but now we don't seem to be able to install clicks on the desktop so why bother putting x86 builds in the store?
[11:12] <dpm> not that I know of, but best to ask kgunn or pmcgowan
[11:12] <popey> "Snappy will fix this" of course (c) ogra
[11:12] <popey> okay
[11:12] <dpm> popey, we've never been able to install clicks on the desktop to the best of my knowledge
[11:12] <popey> ditto
[11:13] <popey> We could save space on user devices by doing thin packages
[11:13] <popey> (only a few are fat)
[11:13] <dpm> at least when I used to run the unity8 in LXC session a while ago, click was not working, and there were no plans to make it work
[11:13] <dpm> ok
[11:13] <beuno> yeah, so we have think packages now for snappy
[11:13] <popey> They were uploaded fat only because the assumption was there that at some point soon there'd be a click desktop
[11:13] <dpm> yeah
[11:14] <popey> But if that won't happen then we can save space and bandwidth
[11:14] <beuno> I don't think it'll happen for clicks, no
[11:14] <dpm> popey, yeah, I'd say let's remove the fat clicks and think of a way to do it when we move to snaps for core apps
[11:14] <dpm> I mean let's trim the fat, not remove them :)
[11:15] <popey>  😃
[11:23] <popey> Ok, will do for next set of uploads.
[11:25]  * popey looks for a dholbach
[11:43] <dholbach> popey, which app is it?
[11:43] <popey> file manager
[11:43] <dholbach> sure, let me take a look
[11:44] <popey> thanks :)
[11:44] <popey> you can leave when you're done ㋛
[11:49] <dholbach> done
[11:52]  * popey hugs dholbach
[11:53]  * dholbach hugs popey back
[14:07] <faenil> popey: hey, isn't the calendar supposed to have a local calendar instance?
[14:08] <faenil> or do I have to add an online calendar to be able to save anything?
[14:08] <ogra_> faenil, there used to be a "Personal" calendar
[14:08] <ogra_> (local instance)
[14:08] <faenil> yeah...I remember that
[14:09] <popey> click kebab, tick personal calendar
[14:09] <popey> sorry, faenil click kebab, choose calendars, tick personal one
[14:10] <popey> (on a hangout, biab)
[14:11] <karni> kebab.. now I'm hugry
[14:12] <popey> :)
[14:13] <faenil> popey: there's on Add online calenda
[14:13] <faenil> ok
[14:13] <faenil> I reset configs and caches, fyi
[14:16] <popey> faenil: you dont see personal at all?
[14:17] <popey> faenil: wonder if this is to blame http://bazaar.launchpad.net/~ubuntu-calendar-dev/ubuntu-calendar-app/trunk/revision/753
[14:17] <faenil> popey: nope
[14:17]  * faenil clicks
[14:18] <faenil> popey: cannot read "collectionId" of undefined
[14:18] <popey> can you file a bug please faenil ?
[14:19] <ogra_> popey, i doubt that ... thats only for the "New Event"
[14:19] <ogra_> iirc that Personal calendar even comes from syncevolution
[14:19] <faenil> popey: I wanted to understand if it's because I reset config,cache and .local/share folders
[14:20] <popey> well, i still see it here, and I didnt do that
[14:20] <popey> so quite likely
[14:20] <ogra_> (you get it on desktop too if you use a fresh evolution install)
[14:20] <popey> I don't know if this is a calendar or evolution issue
[14:21] <faenil> also, adding a new calendar returns a QDbusError
[14:21] <faenil> this is on Xenial+Unity8 on laptop
[14:21] <popey> ah
[14:22] <popey> you should have said that 15 mins ago :)
[14:23] <faenil> popey: yep, I should have
[14:23] <faenil> doing 3 things at a time decreases my efficiency :)
[14:23] <popey> :)
[14:24] <davmor2> faenil: only 3 pfff ;)
[14:24] <faenil> davmor2: on 3 diff laptops, that's what smashes my brain :D
[14:27] <popey> bartbes: https://code.launchpad.net/~popey/ubuntu-terminal-app/add-control/+merge/282280
[14:27] <popey> bartbes: see comments.. :)
[14:27] <faenil> mmm
[14:27] <faenil> OnlineAccountsUi: unrecognised option '--socket' and 'profile"
[14:27] <faenil> ...
[14:28] <Elleo> popey: would you happen to have an old click of something fairly big like file manager or document viewer or similar? (I'm fixing some UDM stuff with click updates and need a large click I can keep re-updating to test with)
[14:29] <popey> Elleo: i have everything
[14:30] <Elleo> popey: awesome :)
[14:30] <popey> Elleo: http://popey.mooo.com/mirror/clicks/2016/
[14:30] <Elleo> popey: perfect, thanks
[14:31] <popey> np
[14:38] <bartbes> popey: I do think it should highlight, but I really just lack the experience with qml to do it
[14:39] <popey> ditto :)
[14:40] <popey> bartbes: I'll leave a comment
[14:40] <bartbes> well, I've got a launchpad account too :P
[14:46] <popey> bartbes: yeah, i thought you just hated bzr ㋛
[14:47] <bartbes> hate's a strong word, but I'll reply, at least
[14:47] <popey> :)
[14:48] <bartbes> now.. how do I subscribe..
[14:53] <popey> to the merge?
[14:54] <popey> subscribe to the bug I think
[15:05] <faenil> popey: who's working on calendar at the moment?
[15:06] <popey> Nobody consistently full time.
[15:06] <popey> We've had a bunch of patches recently from renatu and gary
[15:07] <faenil> ok, thanks :)
[15:07] <faenil> popey: didn't we move to buteo for calendar as well?
[15:08] <faenil> meanwhile, laptop doesn't have sync-monitor and all the syncevolution stuff installed, that's surely one of thep roblems
[15:08] <popey> faenil: not yet afaiaa
[15:08] <faenil> popey: I see, so buteo is only for contacts atm, right?
[15:08] <popey> yes
[15:09] <faenil> cool, thanks
[15:09]  * faenil installes sync-monitor and all its deps
[15:09] <popey> that would help
[15:10] <faenil> apparmor denials now...dconf permission denied
[15:10] <faenil> aw :(
[15:42] <popey> kenvandine: do you know if there's a plan to add a notification for app updates (like we have for system updates) in system settings?
[15:43] <kenvandine> popey, no solid plan... we want a background service for handling updates
[15:43] <kenvandine> settings can't do that
[15:43] <popey> ah
[15:43] <kenvandine> there was talk ages ago about creating that, but nobody has done it
[15:43] <kenvandine> a background service that also handled actually applying the updates as well as installs from the scope
[15:44] <kenvandine> just providing an API for use to use
[15:44] <kenvandine> like update-manager for the phone :)
[15:44] <kenvandine> us to use
[17:17] <popey> ogra_: if you get a moment, can you pair one of your ouya controllers with your ubuntu phone and reproduce https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1542305 ?
[17:17] <ubot5`> Launchpad bug 1542305 in unity8 (Ubuntu) "Pressing button on bluetooth game pad shuts unity down" [Undecided,Incomplete]
[17:17] <ogra_> popey, thats possible ?!?
[17:17] <popey> yup
[17:17] <ogra_> wow, i didnt know
[17:17] <popey> just want to make sure it's not just me or my device
[17:17] <ogra_> will take a bit til i have some time for that though (and i need to find batteries)
[17:18] <popey> hehe
[17:18] <ogra_> not much in use anymore :)
[17:18] <popey> yeah
[17:18] <popey> one reason why i'm playing with it with ubuntu
[17:18] <ogra_> time that we create an ubuntu-tv unity8 image for it ;)
[17:18] <popey> hah
[17:21] <popey> you're the only person I know who has one
[19:47] <RPiAwesomeness> Does anyone here have experience with the javascript scopes? I'm running into some issue that's crashing it and I don't know how to fix it
[19:47] <RPiAwesomeness> I've tried googling around a bit, but haven't found anything
[19:48] <davidcalle> RPiAwesomeness: what's crashing what? :)
[19:48] <RPiAwesomeness> My scope is crashing
[19:48] <davidcalle> RPiAwesomeness: are you able to start your scope?
[19:48] <RPiAwesomeness> It starts but then freezes up and this is in the console:
[19:48] <RPiAwesomeness> Error: libunity-scopes.so.3: cannot open shared object file: No such file or directory
[19:49] <davidcalle> RPiAwesomeness: which version of Ubuntu are you using?
[19:49] <davidcalle> s/version/release
[19:49] <RPiAwesomeness> 15.10
[19:50] <davidcalle> RPiAwesomeness: running Unity or another desktop?
[19:50] <RPiAwesomeness> Unity
[19:50] <davidcalle> (hold on, feeding baby :))
[19:50] <RPiAwesomeness> No problem :)
[19:54] <davidcalle> RPiAwesomeness: maybe "sudo apt-get install --reinstall libunity-scopes3" could fix it, first time I'm seeing your issue
[19:56] <RPiAwesomeness> davidcalle:  Package libunity-scopes3 is not available, but is referred to by another package
[19:57] <RPiAwesomeness> I reinstalled libunity-scopes1.0 and that resolved that issue but now I'm getting this: "error while loading shared libraries: libboost_system.so.1.55.0: cannot open shared object file: No such file or directory"
[20:06] <RPiAwesomeness> davidcalle: Should I reinstall the SDK? I just updated it, but maybe reinstalling it would make sure everything is up to date?
[20:12] <RPiAwesomeness> davidcalle: Okay, strange. I created a new project with the sample weather scope code and that runs fine
[20:55] <RPiAwesomeness> davidcalle: Well, I got it running. However, now I'm running into a new issue with getting the data from the API I'm trying to use
[20:55] <RPiAwesomeness> That's more of a Node/JS issue than a scope issue though
[22:31] <ahoneybun> I can't get PageHeader to work
[22:31] <ahoneybun> it tells me it is not a Type


[12:07] <ricktimmis[m]> @acheronuk:matrix.org: will give you a nudge when am next on my laptop and we can take a look at what graphics you need, hopefully that'll be later today