Bzr Error Paths Are Not Version
don't understand. rob1:ratlas2 rbur004$ bzr checkout bzr+ssh:///~rob-burrowes/ratlas/trunk rob1:ratlas2 rbur004$cd trunk/ruby_extension ... Edit lots of files ... rob1:ruby_extension rbur004$ bzr commit bzr+ssh:///~rob-burrowes/ratlas/trunk bzr: ERROR: Path(s) are not versioned: "ruby_extension/bzr+ssh://~rob-burrowes/ratlas/trunk" Using bzr diff gives a long list of file changes, so bzr knows the files have changed. What should I be doing that I'm not? Question information Language: English Edit question Status: Solved For: Bazaar Edit question Assignee: No assignee Edit question Solved by: Rob Burrowes Solved: 2007-12-10 Last query: 2007-12-10 Last reply: Related bugs Link existing bug Related FAQ: None Link to a FAQ Rob Burrowes (rob-burrowes) said on 2007-12-10: #1 Ok, stupid question. I should have used bzr commit -m "Blah" . to explicitly commit this directories changes and didn't have to specify the repository address. Jon Loldrup (loldrup) said on 2010-11-05: #2 I had the same error, and also omitting the URL solved the problem (I had the -m "comment" on all the time). But.. If this error really is about the user supplying the URL when it is not needed, then why do we get that error message? There must be a better explanation, or the error message is severely misguiding. Marius Kruger (amanica) said on 2010-11-05: #3 @Jon The commit command takes a list of files/directories to commit, so if you give it anything that is not files it knows about it will complain. See `bzr commit --help` for more info. Is it the custom for any other version control systems to supply a target repo as an argument to commit? Vincent Ladeuil (vila) said on 2010-11-06: #4 To complete Marius answer: commit, by default, commit the changes for all the modified files. But on certain occasions you want to do a partial commit, so you can specify which of the modified files or dirs you want to commit. The url you give *is* a valid path so you could have a file with such a name, but if you provide a path that doesn't exist or does a typo in the path, it's hard to understand that you specified an url instead. Especially when, like in the case reported here, the commit is done from a subdirectory so bzr "helpfully" added ruby_extension in front of ruby_extension/bzr+ssh://~rob-burrowes/ratlas/trunk which is *not* anymore a valid url to recognize... History Link existing bug Create bug report Link to a FAQ Create a new FAQ To post a message you must log i
which may be semi-permanent can also be controlled through the environment. BZR_EMAIL¶ Override the email id used by Bazaar. Typical format: "John Doe " See also the email configuration option. BZR_PROGRESS_BAR¶ Override the progress display. Possible values are "none" or "text". If the value is "none" then no progress bar is displayed. The value "text" draws the ordinary command line progress bar. BZR_SIGQUIT_PDB¶ Control whether SIGQUIT behaves normally or invokes a breakin debugger. 0 = Standard SIGQUIT behavior (normally, exit with a core dump) 1 = Invoke breakin debugger (default) BZR_HOME¶ Override the home directory https://answers.launchpad.net/bzr/+question/19768 used by Bazaar. BZR_SSH¶ Select a different SSH implementation. BZR_PDB¶ Control whether to launch a debugger on error. 0 = Standard behavior 1 = Launch debugger BZR_REMOTE_PATH¶ Path to the Bazaar executable to use when using the bzr+ssh protocol. See also the bzr_remote_path configuration option. BZR_EDITOR¶ Path to the editor Bazaar should use for commit messages, etc. BZR_LOG¶ Location of the Bazaar http://doc.bazaar.canonical.com/beta/en/user-reference/configuration-help.html log file. You can check the current location by running bzr version. The log file contains debug information that is useful for diagnosing or reporting problems with Bazaar. Setting this to NUL on Windows or /dev/null on other platforms will disable logging. BZR_PLUGIN_PATH¶ The path to the plugins directory that Bazaar should use. If not set, Bazaar will search for plugins in: the user specific plugin directory (containing the user plugins), the bzrlib directory (containing the core plugins), the site specific plugin directory if applicable (containing the site plugins). If BZR_PLUGIN_PATH is set in any fashion, it will change the the way the plugin are searched. As for the PATH variables, if multiple directories are specified in BZR_PLUGIN_PATH they should be separated by the platform specific appropriate character (‘:' on Unix, ‘;' on windows) By default if BZR_PLUGIN_PATH is set, it replaces searching in user. However it will continue to search in core and site unless they are explicitly removed. If you need to change the order or remove one of these directories, you should use special values: -user, -core, -site will
Translation patches Feature #4741 Improve Bazaar repositories error message in case to use shared repository Added by Joe Julian over 6 years http://www.redmine.org/issues/4741 ago. Updated almost 5 years ago. Status:NewStart date:2009-02-21Priority:NormalDue date:Assignee:Toshi MARUYAMA% Done:0%Category:SCMTarget https://lists.ubuntu.com/archives/bazaar/2011q1/071667.html version:Candidate for next major release Resolution: Description This was originally miscategorized as Feature #2799.This is a common use case as it prevents the standard trunk/branch/tag development structure. A shared repository created with bzr init-repo errors when running ruby script/runner "Repository.fetch_changesets" -e production I get bzr error these messages back:bzr: ERROR: Not a branch: "[...]/project_container/.bzr/branch/".bzr: ERROR: Not a branch: "[...]/project_container/.bzr/branch/". If we point at a sub-tree, there's still no support for branches. There are 2 ways to identify the shared repository: bzr info will list 'shared repository: .' .bzr/repository exists. If the path points to a shared repo, some file tree should bzr error paths be built. Branches can be identified by a similar combination of techniques: bzr info will list the root repository as 'shared repository' .bzr/branch exists. Sub branches: bzr info will list the root repository as 'shared repository' and the parent branch as 'parent branch' As an example, let's examine the following repo:[...] In summary, if the path is a repo, scan the directory tree for directories containing .bzr/branch and run bzr info on those directories. Use that output to find out which branch is the parent and use that information to build the element tree. I don't know how to do this in ruby, but hopefully someone can take this analysis and put something together. Related issues Related to Redmine - Feature #2799: Support for Bazaar's shared reposetories (created with in... New 2009-02-21 Related to Redmine - Defect #7984: Confusing revisions links on repository root New 2011-03-24 Related to Redmine - Patch #9129: Improve wording of Git repository note at project setting Closed 20
-0500, Eric Siegerman wrote: > On Tue, 2011-02-15 at 09:17 -0600, John Arbash Meinel wrote: > > One thing you can try is to change it to a url, so do: > > > > bzr mv file:////2010-11__2010-12-17%3A17%3A06%2B00%3A00.jpg > > 2010-11__201012171706.jpg > > I tried a few variants of that, but none of them worked > (/tmp/bt2 is a test standalone branch): > $ bzr mv file:///tmp/bt2/foo%3abar foo-bar > bzr: ERROR: Could not rename foo%3abar => foo-bar: file:/tmp/bt2/foo > %3abar is not versioned. > > $ bzr mv file://localhost/tmp/bt2/foo%3abar foo-bar > bzr: ERROR: Could not rename foo%3abar => foo-bar: > file:/localhost/tmp/bt2/foo%3abar is not versioned. > > $ bzr mv file://localhost//tmp/bt2/foo%3abar foo-bar > bzr: ERROR: Path "/tmp/bt2/file:/localhost/tmp/bt2/foo%3abar" is not > a child of path "//tmp/bt2" > > If I typed the ":" directly instead of escaping it as "%3a", I > got the corresponding error message in each case. Thanks for giving them a try. I'm afraid my situation was one of "it has to be sorted in the next 3 mins" so there was no time for a play. I guess I should revert in a branch of the branch and try some things. > This did work, however: > $ mv foo:bar foo-bar > $ bzr mv --auto > foo:bar => foo-bar OK, this one is new to me. I just did the mv in the shell and then add. Ruins the history, but suffices since the situation is us using Bazaar to provide a shared filestore not a project version control system. > $ bzr ci '-mmoved' > Committing to: /tmp/bt2/ > renamed foo:bar => foo-bar > Committed revision 2. Whilst talking of Bazaar purposes, Bazaar Explorer assumes that any Bazaar branch is a project version control entity that is likely publishable on Launchpad. Given that we are using Bazaar as a private and confidential shared filestore, it would be good to get rid of the buttons about "publishing to Launchpad". Is there a way of doing this? -- Russel. ============================================================================= Dr Russel Winder t: +44 20 7585 2200 voip: sip:russel.winder at ekiga.net 41 Buck