Re: bkd bug (or change of behaviour) in 3.2.1

Just a heads up that this is still not fixed in 3.2.3. Did it get added to 
your buglist?

Bit me again, and I ended up googling to my own bug report to find the 
solution :)

Andrew Walrond

On Sunday 20 Jun 2004 14:40, Andrew Walrond wrote:
> Hi guys,
>
> This one had me puzzled for a while :)
>
> I've just moved some parent repos from a server running bk-3.0.4 to another
> running bk-3.2.1.
>
> I have a user called bitkeeper, and have my parent repos in bitkeepers home
> directory, /home/bitkeeper/
>
> I allow anonymous public access by running a bkd from the home directory in
> the usual way, and private push access via ssh with bitkeepers' shell set
> to bkd.
>
> Ok, all seemed to be working as before; I can clone/push/pull the rubyx
> repo from my laptop using the url bk://bitkeeper@xxxxxxxxxxxxxxxxxxx/rubyx
>
> BUT
>
> If I try to clone the repo (or pull into and existing clone) on the same
> server that hosts the parent repo, it fails like this:
>
> (I am in my home directory on cenedra)
>
> bk clone bk://bitkeeper@xxxxxxxxxxxxxxxxxxx/rubyx
> ERROR-cannot cd to rubyx (illegal, nonexistant or not package root)
>
> HOWEVER
>
> If I remove the bitkeeper@, it works;
>
> bk clone bk://cenedra.walrond.org/rubyx
>   -> file://home/andrew/rubyx
> ...
>
> Pulls also work, but of course I would need the bitkeeper@ in order to push
> via ssh/bkd
>
> So I guess it's getting confused about which transport to use when the url
> resolves to the local machine. Worked fine with 3.0.4
>
> Hope that's useful
>
> Andrew Walrond
> _______________________________________________
> Bitkeeper-users mailing list
> Bitkeeper-users@xxxxxxxxxxxx
> http://bitmover.com/mailman/listinfo/bitkeeper-users
> To unsubscribe from this list, go to the above URL, follow instruction at
> the bottom of the web page.
_______________________________________________
Bitkeeper-users mailing list
Bitkeeper-users@xxxxxxxxxxxx
http://bitmover.com/mailman/listinfo/bitkeeper-users
To unsubscribe from this list, go to the above URL, follow instruction at the 
bottom of the web page.