[10:06] <neXyon> awesome: http://pastebin.com/Nf8JBdvq :-(
[10:12] <vila> neXyon: shot in the dark: do you have a working tree with at least one revision here (as opposed to a just-created-never-committed one) ?
[10:12] <fullermd> That sounds familiar.
[10:13] <neXyon> vila: I just did a bzr branch, that's the cause?
[10:13] <fullermd> Though hazy enough that whatever it's reminding me of is well before 2.5...
[10:13] <vila> neXyon: what does 'bzr revno' says ? And 'bzr info' ?
[10:13] <fullermd> Is there a working tree there?
[10:15] <neXyon> I deleted the directory and branching again atm, will tell you then
[10:16] <vila> I suspect (as fullermd) that you have a branch with no working tree (i.e. the directory contains only a '.bzr' dir)
[10:17] <fullermd> Great minds think alike.
[10:17] <fullermd> And vila gets lucky sometimes, too.
[10:17] <vila> . o O (Glad I re-read his remark until I realized he meant *no* wt there )
[10:19] <neXyon> vila: yes true, only a .bzr dir
[10:19] <fullermd> On the one hand, it might point at the error.  Though, on the other, the command being run seems like something that might be embedded in a build script, not something you'd just come up with manually.
[10:21] <vila> so, first of all, this is a bug, at the very least a friendly error message should be displayed, not a traceback, so please file it at http://pad.lv/fb/bzr
[10:22] <vila> neXyon: now, what's your use case ?
[10:23] <neXyon> vila: I just did as http://doc.bazaar.canonical.com/latest/en/mini-tutorial/#creating-your-own-copy-of-another-branch told me to
[10:23] <vila> neXyon: and then, a workaround would be to do 'bzr checkout .' to create a working tree there
[10:23] <neXyon> vila: bzr init-repo stellarium; bzr branch lp:stellarium stellarium
[10:23] <vila> err, are you sure you didn't do 'bzr init-repo --no-trees' ?
[10:24] <vila> and my question is: why do you run 'bzr version-info' ?
[10:24] <neXyon> vila: the zsh does
[10:24] <vila> eeerk
[10:25] <neXyon> and no, I didn't add any --no-trees :D
[10:25] <vila> who told it to do that ? ;)
[10:25]  * vila scratches head
[10:25] <neXyon> the grml zsh configuration :D
[10:25] <fullermd> I never trust something with that few vowels.
[10:25] <vila> bzr branch creates a working tree by default
[10:25] <neXyon> so why didn't do it in this case?
[10:25] <neXyon> +it
[10:26] <vila> hehe, *you* tell me :)
[10:26] <vila> bzr alias ?
[10:26] <neXyon> how could I? xD
[10:26] <vila> neXyon: :)
[10:26] <vila> because it's probably caused by some setting on your side
[10:27] <vila> and my crystal ball is currently being checked in this place I cannot name
[10:27] <neXyon> nah, I have no alias for it and I also didn't change any bzr configuration
[10:28] <vila> so, back to previous question: 'bzr info -v' ?
[10:29] <neXyon> ah, sure
[10:29] <neXyon> vila: http://pastebin.com/03ddtbQE
[10:30] <vila> 'brz config' ?
[10:32] <neXyon> vila: nothing special there: http://pastebin.com/RPADTTY0
[10:33] <neXyon> Name Mail and IRCnick got changed by me before pasting ;)
[10:35] <vila> ls -lR .bzr
[10:37] <neXyon> vila: http://pastebin.com/wsKuASVA
[10:38] <vila> puzzling...
[10:38] <vila> so, there is indeed no working tree, get one with 'bzr  checkout .'
[10:39] <neXyon> yeah, that might fix it, but what about the bug that it isn't there as it should be? :D
[10:39] <vila> I don't understand how this can happen :-/ Try looking into in ~/.bzr.log ?
[10:39] <vila> s/ in / /
[10:39] <vila> gotta go soon
[10:41] <neXyon> vila: nothing special there
[10:41] <neXyon> the checkout however fixed it
[10:42] <vila> it should have happened at 'bzr branch' time, everybody is relying on it :)
[10:42] <vila> I know of only two ways to avoid it: 'bzr init-repo --no-trees' and 'bzr branch --no-tree'
[10:43] <vila> and your 'ls -lR' says you didn't use 'bzr init-repo --no-trees'...
[10:43] <fullermd> Once upon a time, --no-trees was the default for init-repo.  But that was a _long_ time ago.
[10:44] <vila> fullermd: and is reflected by a 'no_working_trees' file under .bzr/repository
[10:44] <fullermd> To be sure, it is a _little_ odd to make a shared repo, then have one branch in the root of it...
[10:44] <neXyon> vila: yes the log tells I didn't do it too
[10:45] <neXyon> fullermd: so what's the expected way to start developing on a launchpad project?
[10:45] <neXyon> fullermd: if it's not "bzr init-repo stellarium; bzr branch lp:stellarium stellarium"?
[10:45] <vila> it *is*, that's why it's puzzling, that's what everybody does :)
[10:46] <neXyon> xD
[10:46]  * fullermd peers at vila.
[10:46] <fullermd> Nobody I've ever met...
[10:46] <neXyon> fullermd: it's not? what else?
[10:46] <fullermd> (although, meeting other bzr users would require that I leave my cave in the first place, but still...)
[10:47] <fullermd> Generally, you'd have a branch in its own dir under the repo, not colocated with the repo root.  Otherwise, where would you put the second branch that would share space and make the shared repo be pointful anyway?
[10:47] <fullermd> But it's not something that should _break_ anything.  I think.
[10:48] <fullermd> Oh ho.  Back up.
[10:48] <fullermd> Yes, it is.
[10:48] <vila> eeerk, 'bzr init-repo xxx; *cd* xxx ; bzr branch lp:xx yyy'
[10:48] <fullermd> I can reproduce it.  If I bzr init-repo something, then bzr branch $SRC something, I wind up with a treeless branch.
[10:48] <fullermd> (lp: having nothing to do with it)
[10:49] <fullermd> So it's a behavioral oddity when the bzrdir exists.
[10:49] <vila> neXyon: you need to *CD* into the repo before branching
[10:50]  * vila nods @ fullermd, that's another bug (unless there is a rationale for it (doubtly))
[10:50] <vila> could also be a fallout from an unrelated fix
[10:50] <fullermd> It's probably a 2nd or 3rd order consequence of some other sensible behavior that nobody ever ran into.
[10:50] <neXyon> hah, so we found the bug :D
[10:51] <fullermd> Man, we should write some more wrong docs; think of all the extra bugs we could find!
[10:51] <vila> neXyon: roughly, you create a shared repo if you intend to create several branches (so they will share their revisions)
[10:51] <mgrandi> this seems like the weird thing i had if you try to make a branch a shared repo
[10:51] <vila> if you want a single branch, no need for a shared repo
[10:51] <mgrandi> you get really weird state
[10:51] <neXyon> vila: and how to create a not shared repo? xD
[10:52] <vila> just 'bzr branch'
[10:52] <vila> no 'init-repo'
[10:52]  * vila gone
[10:52] <fullermd> neXyon: You don't need to explicitly create a repo if you don't want a shared one.
[10:52] <neXyon> vila: I just want to develop somewhere; stay in sync with trunk and probably at some point be able to push the changes to trunk :)
[10:53] <neXyon> so I just had to run "bzr branch lp:stellarium stellarium" ?
[10:53] <fullermd> Might as well just ignore it.  If down the line you start having several branches around and want to switch them to sharing a repo, that's easy enough to do then.
[10:53] <fullermd> Correct.
[10:54] <mgrandi> don't even need to specify the 'stellarium', by default it creates that folder
[10:55] <neXyon> I first had a "bzr checkout lp:stellarium" is it possible to change that to a "bzr branch lp:stellarium"?
[10:55] <fullermd> You can use 'bzr unbind' if you avoid thinking too carefully about the semantics.
[10:56] <fullermd> Or something under 'reconfigure'.  I'd have to dig around to figure out what.
[10:56] <neXyon> fullermd: can I still keep it up to date with trunk after the unbind?
[10:56] <fullermd> Sure, just 'pull' whenever.
[10:59] <neXyon> awesome, well as it works currently with the shared repo, I'll leave it as it is :)
[10:59] <neXyon> fullermd: shall I report that bug somewhere or will you handle it?
[11:00] <fullermd> I can file it I guess.
[11:01] <neXyon> fullermd: if you wish, sure; otherwise I could too
[11:03] <fullermd> Well, I wouldn't want to steal your LP karma.
[11:04] <neXyon> fullermd: whatever that is xD
[11:05] <neXyon> nah, I know it, but no clue what it's for
[11:05] <fullermd> Neither do I.  But it's a number, so it MUST be important.
[11:30] <neXyon> fullermd: so? looks like we're both too lazy :)
[11:52] <fullermd> Laziness is a virtue.
[12:32] <jave> is someone having success using bzr on the fedora 17 prerelease?
[19:49] <AmberJ> Is there a way to search for when few consecutive lines of code were added to the repo?
[19:49] <AmberJ> I want to find the revision when those lines were added.
[19:58] <AmberJ> Nevermind, I used "Change to this file" in launchpad web GUI to find what I was looking for.
[19:58] <AmberJ> Though this was more of manual searching.