How to work from behind proxies ? (with patch providing a partial solution)

[John Arbash Meinel]

Vincent LADEUIL wrote:

...

> So I wrote a plugin for that.  It is running now, at least to the
> point to be able to 'bzr push bzr.dev'. It requires:
> - a DAV enabled web server,
> - pycurl,
> - patching  bzr  to  allows  directories  to  be  used  for  http
>   transports (1),
> - patching  bzr to  allows  http test  servers  to specify  their
>   request handler (2),
> 
> I would like to publish it and need guidance on how to do that on
> launchpad (especially the 'hosted *on* launchpad part).

1) Make sure you have an account with launchpad. If you don't go here:
   https://launchpad.net/+login
   And sign up for a new account.

2) Setup an ssh key to connect to launchpad. only ssh-keys are supported
for bazaar.launchpad.net
   $ ssh-keygen

   Go to your user account (click your name in the upper right) the
   url will be:
   https://launchpad.net/people/<username>

   Add an ssh key, there is a link on the left, but the url is:
   https://launchpad.net/people/<username>/+editsshkeys

   Register a new project:
   https://launchpad.net/products/+new

Probably you will want to add the product to the "bazaar" project.

3) Publish the new branch:

   $ bzr push --create-prefix \
      sftp://<username>@bazaar.launchpad.net/~<username>/<project>/trunk

   You should only need --create-prefix the first time you create a new
   project in your user directory.

   At this point, you should be able to go to:
   http://launchpad.net/products/<product>
   And see that you have a newly started project.

   It takes a while to propagate, but I believe the branch will be
   available from:
   http://bazaar.launchpad.net/~<username>/<project>/trunk

   ('trunk' is arbitrary, just a name for the branch)

> 
> I'm  implementing an http  DAV test  server but  would appreciate
> early feedback  on the existing  work (hence the need  to publish
> it).
> 
>     >>> And as you didn't answer to the other points in the
>     >>> original mail, does that mean that you consider using
>     >>> pycurl from behind a restricted firewall not worth the
>     >>> effort ?  Or is it just that sftp is better considering
>     >>> my encryption requirement ?
> 
>     jam> I think pulling over pycurl and https is very good.  And
>     jam> I think we should handle proxies for pycurl.
> 
>     vila> Ok.
> 
>     jam> But from other comments, it already works.
> 
>     vila> Strange, it was not in my case (I mean respecting the
>     vila> http_proxy env variable).
> 
> <cough> Setting HHTPS_PROXY (note caps) works. <blush>

Well, I hope it is 'HTTPS_PROXY' :)

> 
>     jam> It just doesn't work with password support.
> 
> Which can be  circumvented by embedding user and  password in the
> URL which will do the trick for now.
> 
>     vila> I'll dig deeper to get a better understanding then.
> 
> The   only  remaining   problem   was  that   my   H  server   is
> self-authenticated  which  still requires  me  to lower  security
> settings of libcurl (3).
> 
> Thanks in advance,
> 
>        Vincent
> 
> (1)(2)(3): Few lines patches to  bzr.dev, what is the best way to
>          get them reviewed ?


Just send us a diff or bundle. If you branched directly from bzr.dev, it
should be as easy as:

bzr bundle > ../mychanges.patch

But you may need to do:
bzr bundle http://bazaar-vcs.org/bzr/bzr.dev > ../mychanges.patch

And send it here.

John
=:->

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 254 bytes
Desc: OpenPGP digital signature
Url : https://lists.ubuntu.com/archives/bazaar/attachments/20060821/76e4cc16/attachment.pgp