=== spiv_ is now known as spiv === mwhudson_ is now known as mwhudson === jam1 is now known as jam [09:48] hi, i want to navigate our bazaar repo, similar to svn list [09:49] but when i try bzr ls , i get ERROR: Not a branch.... location is a repository. [09:49] how do you do it then? [10:01] espressobuff: as it says, it needs a branch, not just a repository [10:02] a repository is a store of data, a branch is the actual graph of history [10:02] so, eg, `bzr ls lp:bzr` works fine, because that references an actual remote branch [10:07] mgz: thanks. but i want to navigate the repo to search something that i might be interested in [10:07] what's the correct way to do that then? [10:08] without a branch which references the repo, you don't have anything to navigate [10:09] there are ways to inspect repo contents, but nearly all the time what you care about is branches [10:09] is there something specific you're trying to do? [10:10] can you give example of a repo vs branch? sorry i'm a total bzr newbie (from svn) [10:12] espressobuff: http://doc.bazaar.canonical.com/bzr.2.5/en/user-guide/core_concepts.html [10:13] but for example, I have ~/bzr which is a shared repo, and under that I have ~/bzr/2.5 which is a branch and a bunch of other branches [10:18] so repo is the root of branch(es)? as in svn, we usually have "trunk" and "branches" as branches of a project? [10:19] anyway, what i'm trying to do is that, say i can "bzr co bzr://bzr/data/bzr/dir1/dir2/dir3/dir4/trunk" [10:19] see also http://doc.bazaar.canonical.com/migration/en/survival/bzr-for-svn-users.html [10:19] and then do "bzr ls bzr://bzr/data/bzr/dir1/dir2/dir3/dir4/" just fine [10:20] espressobuff: no, you can't [10:20] that's a very svn thing to do [10:20] but i want to see the content of, say "bzr://bzr/data/bzr/" [10:20] well, you can, but not in the way you're thinking [10:20] really what you want is to just branch trunk locally, then use ls [10:21] can you give the actual command, in relation to my example? thanks [10:22] not without knowing what you've actualyl got, but generally, `bzr branch remote-location` [10:22] which gets you a local copy to work on. [10:35] ugh, sorry, maybe i just need to read up more to override my old svn concept === bsd1 is now known as bsd === iBasic is now known as BasicOSX === jordan__ is now known as jordan [19:17] is there any way to coerce bzr into accepting filenames with backslashes [19:39] eridu: no, unfortunately not [19:39] eridu: there is an old bug report about this [19:39] eridu: http://pad.lv/81844 [19:39] Launchpad bug 81844 in Bazaar "backslash in filename causes InvalidEntryName etc" [Medium,Confirmed] [19:39] this breaks the git bridge for a project I want to hack on [19:49] it's a fairly hard bug to fix, there are assumptions in a number of places in bzr that / and \ are path valid path separators [19:50] well, perhaps not hard.. mostly just time-consuming I think :) [19:54] why not os.path.sep? [19:54] really I guess you'd want to forbid them in most cases but accept them if they appear [19:56] it's a ROYALLY STUPID idea to EVER have \ in a path component [19:57] eridu: that means it becomes impossible to use some repositories on both Windows and POSIX/Mac [19:57] SamB: I wouldn't have put it in, but this project literally has a file named '\' [19:57] jelmer: I caught that just after sending it [19:58] ideally bzr should just use one path separator internally ("/"), and accept "\" as a path separator too on windows [19:58] it is equally stupid to have / in a path component, of course, but since no major platform allows it ... [19:58] translating it from \ to / and from \ to / where necessary [19:58] but that means there are a fair number of code paths you have to update [19:59] SamB: I'm sure you can find a unicode character that looks enough like a forward slash if you really want to :) [20:03] That's what unicode is FOR, after all. The old 7-bit ways of making confusing filenames are SO last century. [20:10] fullermd: 😜