=== Kissaki is now known as Kissaki^0ff [01:13] jml or others, i'm just thinking about afc's suggestion that the format not be numbered 2.0 [01:13] poolie: what's the alternative suggestion? [01:14] well, his is to just give them arbitrary sequence numbers [01:16] interesting. [01:16] what's the advantage? [01:17] well [01:17] suppose we bump development-7 to be called 2.0 now [01:17] what happens if (unlikely but possible) we discover we need to change it for the real 2.0 [01:17] also, it's a bit unfortunate that just saying "this is supported" requires a new name [01:18] "it never works the first time", right? :) [01:19] that sort of thing [01:19] poolie: why is a name-change to indicate support level unfortunate? [01:21] does it affect the end-user, or is it more of a conflating-concepts thing? [01:21] well, it requires some work for us and for our users [01:21] so it's possibly waste [01:21] *nod* [01:22] from a #launchpad support perspective, formats matching release numbers _really_ helps. [01:22] things like people asking why they can't read a particular branch? [01:22] yeah. [01:23] or why stacking doesn't work. [01:23] or what have you. [01:24] poolie: hmm. it would also make reading graphs like these easier -- https://lpstats.canonical.com/graphs/RepositoryFormats/ -- if we actually used the UI format name on the graph. [01:29] mm [01:30] the other thing there is that you're reporting the repository format, and there are various independently versioned components [01:32] yes. [01:32] subjectively, it feels like repo fmt is the one that bites most often. [01:33] we also report the branch format in a different graph. [01:33] it's also the one that changes most [01:33] * fullermd isn't sure he buys THAT... [01:33] both most often and most substantially [01:33] I think we've had more branch formats... [01:35] fullermd: well, that's easy enough to verify/falsify. [01:36] Don't you go muddying the discussion with facts... [02:00] poolie: so I guess that wasn't a very conclusive discussion :) [02:01] jml, actually it was a bit helpful [02:01] i wrote an email [02:01] i'd like if you would read it [02:02] I saw the email just after I hit enter :) [02:02] I'll read it now [02:02] poolie: * a set of formats for which this is the best recommended format [02:02] is that supposed to be 'a set of versions' or similar? [02:02] yes [02:03] cool. [02:11] i'm going to sign off for a while [02:11] what did you think, in a nutshell? [02:11] poolie: extremely helpful map of the problem space :) [02:11] poolie: I think 2.0mk1 or whatever would work well. [02:12] 2.0 mark twain :) [02:12] poolie: not 100% sure about the creation UI. [02:12] btw thanks (to whoever) made merge reviews quote the parent post [02:12] poolie: that's almost certainly abentley. [02:14] poolie: I think the thing w/ creation UI is that you should almost always never have to think about format in order to get the optimal experience. [02:14] but that's kind of a separate discussion. [02:14] "what does it take to get a supported format to be the default?" [02:14] jml, poolie: It wasn't me, but it's in-line with my ideas. [02:15] jml, i agree [02:16] we could take the tack that we'll just always hide it so it doesn't matter how they're named [02:16] but that's not realistic [02:16] so we need to improve both sides [02:16] yep [02:17] so maybe a thing to think about with naming is, under what circumstances does a user need to identify a format? [02:17] Has anyone here used guppy [02:17] anyway I really want to go and do Saturday things. [02:17] particularly, I want some yerba maté [02:17] me too [02:17] is it possible to pass it an known object and see how big it is? [02:31] I'm a little confused about the state of the bzr-git plugin [02:32] http://bazaar-vcs.org/BzrForeignBranches/Git says the latest version is 0.3.2 but https://launchpad.net/bzr-git/+download just has 0.1.0 [02:47] Dozer reliably crashes Firefox. Nice. :D === mwhudson_ is now known as mwhudson [05:23] jelmer: I just got a fairly verbose exception from CachingRevisionMetadata [05:30] jelmer: 384192, similar to 324970 [05:33] hello folks [05:33] i scoured the man file, i promise-- how do i ask a bzr binary what version it is? :) [05:33] johnjosephbachir: bzr --version [05:34] nope -- that's for the version of the tree i believe [05:34] no [05:34] try it :p [05:34] oh actually, it's not a flag [05:34] at least, it's not mentioned in the man page [05:34] (i was looking at --versionED) [05:35] whoops-- my bzr is barfing on an error, that's the problem [05:35] sorry for the bother [05:36] (although-- it is true that that flag isn't mentioned in the man page) [05:38] perhaps [05:38] it a relatively common option for all UNIX programs [05:38] (along with -v) === abentley1 is now known as abentley [07:52] johnjosephbachir: fwiw --version is mentioned in "bzr help global-options" [07:52] okay, cool === abentley1 is now known as abentley === Kissaki^0ff is now known as Kissaki [10:05] jfroy: You awake? [10:05] yeah [10:05] wow [10:05] when do you sleep? [10:05] not much :/ [10:06] oh [10:06] and when I can :p [10:06] sorry to hear that :/ [10:06] lol it's fine :p [10:06] but, on the other hand, not ;) [10:07] so what do you think of uninstalling both the fink and MacPorts versions of my SVN and then reinstalling via MacPorts? [10:07] do you think that will solve my problems? [10:07] it might [11:08] jfroy: Hmm... MacPorts even had trouble updating subversion [11:08] So I tried uninstalling it [11:08] Reinstalling it now (which will also bring it from 1.5.5 to 1.6.2) [11:08] yeah [11:09] I'm going to bed now, but, hopefully that will solve your problem [11:09] alright [11:09] thanks for your help :) [11:09] np [11:19] jfroy: thanks for your suggestion to joschan, unfortunately it seems he didn't pay attention :/ [11:28] mwhudson or beuno: ping [11:30] Oh, right, it's Saturday. Oh well. [12:12] Peng_: tentative hello [12:13] mwhudson: Good morning. [12:14] Peng_: you're right about not being good at timezones then :) [12:14] (it's 23:14 here) [12:14] :P [12:14] I always say "Good morning". For me, it *is* morning locally, but I'm probably gonna go to bed soon. :P [12:15] mwhudson: Anyway, the ping was just because I want bug #382765 to be on someone's radar, because Loggerhead uses a deprecated bzrlib API that may soon be removed from bzr.dev. [12:15] Launchpad bug 382765 in loggerhead "history.py uses deprecated ProgressBarStack" [High,Triaged] https://launchpad.net/bugs/382765 [12:15] mwhudson: Kind of unnecessary, since everyone reads bugmail, but it's too late to take it back now. :P [12:16] there's a branch about this right? [12:16] mwhudson: No. [12:17] mwhudson: beuno has a branch about other deprecated stuff, but not this. [12:17] ah [12:18] ah, i misunderstood your comment :) [12:19] i'm fairly sure just deleting the stuff in loggerhead will be fine [12:19] but i'll make sure on monday :) [12:20] mwhudson: Thank you. :) === thekorn_ is now known as thekorn [15:37] Hi, I have a personal repository, I branched it on my laptop and desktop. Trying to push from my laptop I got this error "bzr: ERROR: These branches have diverged." [15:48] hey folks, im wondering if bzr supports specifying the revision in the url like subversion does, eg: 'bzr branch lp:something@123' to get revision 123 of lp:something [15:49] sidnei: bzr branch -r 123 lp:something [15:50] jpds: yeah, that much i know, just wondering because subversion supports the alternative @rev format [15:55] * sidnei considers filing a feature request [15:55] sidnei: it's been talked about in the past [16:11] LarstiQ: so what was the conclusion? yagni? [16:13] sidnei: don't clearly recall [16:17] knowing the bzr style it would probably end up being something pedantically correct like "lp:something?r=123" [16:17] Not that there is anything wrong with pedantic correctness. [16:25] * LarstiQ heads to Amsterdam [16:29] $ bzr missing --remember sftp://cel/var/bzr/leo/perl/IPC-PerlSSH/ [16:29] bzr: ERROR: no such option: --remember [16:29] ^-- what do I mean there..? I thought it had a --remember [16:31] * LeoNerd goes for vim .bzr/branch/branch.conf === abentley1 is now known as abentley === Isaiah1 is now known as Isaiah === Mez is now known as phail === phail is now known as Mez [19:30] Is there a way I can lock a folder or repo so that only one person can make edits? There's some areas in our repo that unforunately cannot be merged easily, so it would be nice if there's a way to "remind" others that committing is not allowed for a folder at that moment. === Kissaki is now known as Kissaki^0ff === Kissaki^0ff is now known as Kissaki