[00:10] <mkanat> I'm getting this when trying to upgrade to the newest loggerhead: bzr: ERROR: KnitPackRepository('file:///home/mkanat/loggerhead/.bzr/repository/')
[00:10] <mkanat> is not compatible with
[00:10] <mkanat> KnitPackRepository('http://bazaar.launchpad.net/%7Eloggerhead-team/loggerhead/trunk-rich/.bzr/repository/')
[00:13] <mkanat> I had to upgrade my local repo to a rich-root-pack. The error message was pretty unclear. Thankfully the URL was helpful! :-)
[00:18] <mkanat> Okay, so I figured all that out on my own. :-)
[00:18] <mkanat> Later, folks!
[01:51] <igc> morning
[03:01]  * igc lunch
[03:35] <gotgenes> Is anyone still working on bzr GTK?
[09:24] <j^> hi, a question, i have two bzr repositories (created from two svn repositories) one is a fork of the other, so i know at which point it was forked from the other project, i want to merge them to get the common history. is that possible how would it do that, trying bzr merge -r 0..HEAD it will move all directories in the repository root and add new once
[09:32] <rowinggolfer> hello.
[09:32] <rowinggolfer> what do I  do about this?
[09:32] <rowinggolfer> bzr: ERROR: bzrlib.errors.TooManyConcurrentRequests: The medium '<bzrlib.smart.medium.SmartSSHClientMedium object at 0x20bf310>' has reached its concurrent request limit. Be sure to finish_writing and finish_reading on the currently open request.
[09:36] <hmeland> j^: The two svn repositories have different UUIDs, right?  If so, bzr's revision IDs will be different even for revisions that are identical (i.e. from before the fork), making merging difficult at best.
[09:37] <Peng_> rowinggolfer: That error message is really useless -- it could be caused by anything, like a segfault. You'll need to provide more details. What details exactly I'm not sure.
[09:38] <hmeland> You might have more luck managing such a merge within git, which I understand use a revision's content to establish that revision's identity.
[09:39] <j^> hmeland, yes two svn servers, but in the end i want history of repository1 + repository2 i know at which point they are  the same, i can also just take repository1 up to the revision they are the same and add repository2 if thats possible
[09:40] <lifeless> j^ I'd use bzr-svn to get r1 imported, then tailor to finish the job
[09:41] <hmeland> j^: I guess you could rebase the post-fork revisions from repo 1 onto the fork-point revision from repo 2 (or vice versa), but the file-ids in the two branches are likely different.
[09:43] <hmeland> ...unless bzr-svn has some nifty option to derive file-ids from another tree, like "bzr add --file-ids-from"?
[09:44] <rowinggolfer> Peng - my network went down during the commit.
[09:44] <rowinggolfer> hang on... I'll pastebin the entire thing
[09:45] <rowinggolfer> http://pastebin.ubuntu.com/183497/
[09:46] <rowinggolfer> Peng_ you'll note I tried to unlock and check stuff also.
[10:01] <rowinggolfer> so any ideas?
[10:02] <rowinggolfer> bzr check of both the local and remote branches are error free.
[10:02] <rowinggolfer> but bzr push gives me
[10:02] <rowinggolfer> Using saved location: bzr+ssh://rowinggolfer@bazaar.launchpad.net/~rowinggolfer/rowinggolfer/trunk/
[10:02] <rowinggolfer> bzr: ERROR: Permission denied: "/~rowinggolfer/rowinggolfer/trunk"
[10:02] <rowinggolfer> is that a lock issue?
[10:02] <rowinggolfer> or a problem with the launchpad server?
[10:06] <hmeland> I'd guess the latter.
[10:06] <hmeland> You could of course try "bzr break-lock".
[10:07] <rowinggolfer> I have done that.
[10:07] <Peng_> A bad lock shouldn't result in permission errors. :\
[10:07] <Peng_> rowinggolfer: "bzr break-lock bzr+ssh://rowinggolfer@bazaar.launchpad.net/~rowinggolfer/rowinggolfer/trunk/"?
[10:07] <Peng_> rowinggolfer: No projected called "rowinggolfer" exists. That's probably the source of your error.
[10:08] <Peng_> Err, project*
[10:08] <rowinggolfer> hmmm.
[10:08] <rowinggolfer> 98 previous commits with the same credentials.
[10:09] <Peng_> rowinggolfer: FWIW, there's a decent chance that your original TooManyConcurrentRequests error has been fixed in a newer version.
[10:09] <Peng_> rowinggolfer: 98 commits to a project called "rowinggolfer"?
[10:09] <rowinggolfer> the project is called openmolar
[10:10] <rowinggolfer> I am confused also.
[10:11] <rowinggolfer> ah, you're looking at line 85... I tried that given the odd url coming back at me
[10:12] <rowinggolfer> for some reason... the save location is wrong.
[10:12] <rowinggolfer> how the hell has that happened?
[10:29] <rowinggolfer> problem solved.
[11:09] <jelmer> msg nickserv identify 8596jrv
[11:09] <jelmer> crap
[11:09] <Peng_> You should type it in a non-channel tab, just to be safe.
[11:10] <pygi> jelmer: lol
[11:10]  * jelmer sighs
[11:10] <jelmer> time to change my nickserv password...
[11:10] <Peng_> I commend you for your non-horrible password, though.
[11:10] <Peng_> Unlike mine..
[13:34] <pygi> beuno: hi
[13:34] <pygi> me and jelmer had some talk about loggerhead serving branches
[13:34] <pygi> and we have two feature suggestions:
[13:34] <pygi> smartserver integration and per-branch authorization functionality
[16:30] <bialix> what is "bzr pony"?
[16:31] <poolie_> bialix: hello
[16:31] <bialix> hi poolie
[16:31] <poolie_> it's a silly expression for "I want everything" -- http://www.google.es/search?q="want+a+pony"
[16:31] <poolie_> i can trim it
[16:32] <LarstiQ> gotgenes: yes
[16:32] <LarstiQ> oh hmm, was scrolled up
[16:33] <bialix> poolie: I'm still can got it re bzr
[16:33] <bialix> can't
[16:33] <fullermd> Wait, my copy of bzr.dev doesn't have a pony   :(
[16:33] <Peng_> I missed ponies?!
[16:35] <bialix> it seems so
[16:36] <poolie_> it just means "i want every feature"
[16:36] <poolie_> it's not a very helpful statement, just something andrew? said here
[16:37] <poolie_> thanks for reading them though!
[16:37] <poolie_> it's pretty rough
[16:37] <Peng_> I want Bazaar to churn butter like git does!
[16:37] <bialix> I want it all, I want it now? Queen
[16:37] <fullermd> git churns butter?  That explains the smell...
[16:38] <Peng_> Oddly enough, it can only churn butter on Windows.
[16:38] <Peng_> On *nix, it just gets all dried out and creepy.
[16:39] <bialix> pollie_: perhaps I'm very curious person
[16:41] <poolie_> :)
[16:42] <bialix> poolie: is there some announce of upcoming public release of lp?
[16:45] <bialix> I mean some semi-official article?
[16:49] <bialix> address book is interesting idea
[16:53] <bialix> pollie,jam: thx for talking with Gary about QBzr. His new idea is really fresh move.
[17:03] <LarstiQ> bialix: where did you encounter that pony?
[17:04]  * LarstiQ briefly checked mail, planet and identi.ca
[17:04] <bialix> http://doc.bazaar-vcs.org/devnotes/wishlist.html
[17:05] <bialix> i wanna pony as well
[17:06] <LarstiQ> ah
[17:06] <LarstiQ> thanks
[17:20] <awilkins> lifeless: Ping?
[22:13] <lifeless> awilkins: pong
[22:50] <vadi21> Would bzr-gtk be updated in the bzr ppa sometime? It's not working with the current version in it for a pair of days
[23:10] <Pilky> are the docs for bzrlib linked to from the site the most up to date or is there a more up to date set that aren't quite as patchy in the bzr repo?
[23:30] <lifeless> -> au
[23:37] <Pilky> lifeless: you're one of the bzr devs right?
[23:41] <Peng_> Pilky: Yes.
[23:41] <Peng_> Unless you're a troll, in which case lifeless who? :D
[23:41] <Pilky> lol
[23:41] <Pilky> I'm trying to figure out how the hell committing works in bzrlib
[23:42] <Pilky> I mean, I understand how to commit from the integrating with bzr document
[23:42] <Peng_> You could follow cmd_commit from bzrlib/builtins.py
[23:43] <Pilky> but the commit method on mutabletree isn't documented and it looks like the arguments are got from the commit class
[23:44] <Pilky> Peng_: it's not as much finding out how as finding out what arguments committing takes
[23:45] <Peng_> Sorry, I don't know anything.
[23:45] <Pilky> i.e. This isn't documented: http://starship.python.net/crew/mwh/bzrlibapi/bzrlib.mutabletree.MutableTree.html#commit
[23:45] <Pilky> this is: http://starship.python.net/crew/mwh/bzrlibapi/bzrlib.commit.Commit.html#commit
[23:45] <Pilky> but it seems when committing the former is used