Martin Pool wrote:
> ** Summary changed:
>
> - error with --auto feature turned on with bzr 2.0.0-2
> + "Win32 file urls start with file:///x:/, where x is a valid drive letter" error in _win32_local_path_from_url in auto_upload_hook
>
So I think this is actually a bug in bzr-upload, and what is happening
is that committing to that branch wants to push the changes to the
remote site, and then upload those to yet another location. However from
the sound of it, we don't actually have *access* to that location,
because it is given as a file:/// url on the remote host.
I don't know if there is much bzr can do...
affects bzr-upload
John
=:->
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Martin Pool wrote: local_path_ from_url in auto_upload_hook
> ** Summary changed:
>
> - error with --auto feature turned on with bzr 2.0.0-2
> + "Win32 file urls start with file:///x:/, where x is a valid drive letter" error in _win32_
>
So I think this is actually a bug in bzr-upload, and what is happening
is that committing to that branch wants to push the changes to the
remote site, and then upload those to yet another location. However from
the sound of it, we don't actually have *access* to that location,
because it is given as a file:/// url on the remote host.
I don't know if there is much bzr can do...
affects bzr-upload
John
=:->
-----BEGIN PGP SIGNATURE----- enigmail. mozdev. org/
KAM8ACgkQJdeBCY SNAAOMvQCeLaAQN fi3c3HuimWD1xNA ThQk qbNLMQEO0sBBwet COloyyro
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://
iEYEARECAAYFAkr
QmsAoNcM/
=edy6
-----END PGP SIGNATURE-----