[Systers-dev] LP-bzr bug

Jennifer Redman jenred at gmail.com
Tue Jul 13 10:31:54 PDT 2010


Hi Vid,

On Mon, Jul 12, 2010 at 11:52 AM, स्वक्ष <vid at svaksha.com> wrote:

> Hi All,
>
> Earlier while using LP I got the "bzr: ERROR: Not a branch" message
> frequently, which I sorted with this:
>
> http://www.mail-archive.com/launchpad-users@lists.launchpad.net/msg00591.html
>
> Searching led me to some bugs on the "Not a branch" issue -- a know
> bug, still open in LP.  (sorry, I dont have the links handy atm) .
>

> After following the suggestion I was able to push to LP but only
> temporarily -- The .bazaar file ownership reverts to root with each
> system shutdown and since then I am unable to push or pull anything
> from LP.
> "Permission denied (publickey). bzr: ERROR: Connection closed: please
> check connectivity and permissions (and try -Dhpss if further
> diagnosis is required)".
>

Your user should be the owner of the branch when you create it -- unless you
are trying to create a branch as root?

Also remember we worked on a similar problem on dev.systers.org -- same
permissions problem.

"On many unixes setting the permissions of the base directory to 02770 will
allow the group to access the repository, and will let the group ownership
be inherited when new directories are created underneath." - From:
http://wiki.bazaar.canonical.com/SharedRepositoryTutorial

If changing the perms to 02770 doesn't not fix the problem, I recommend
going through these step-by-step instructions.

http://doc.bazaar.canonical.com/bzr.dev/en/user-guide/starting_a_project.html

to verify that you have not made any configuration mistakes.


Jen

To contribute to this conversation, send mail to <=?UTF-8?B?4KS44KWN4KS14KSV4KWN4KS3?= >


More information about the Systers-dev mailing list