bzr 2.5.0 - Problem with https+webdav

[Vincent Ladeuil]

>>>>> Andreas Sommer <andreas.sommer87 at googlemail.com> writes:

<snip/>
    >> 
    >> Can you retry the same command with the -Dhttp debug parameter added ?
    >> 
    >> It's probably best to file a bug to track the issue so you can attach
    >> the relevant part of the .bzr.log file (where -Dhttp will output more
    >> info), 'bzr version' will tell you where the .bzr.log file is on your
    >> machine.

    > Okay, should I file a bug in bzr-webdav or in bzr? As webdav uses bzr's
    > urllib wrappers, I think it should go into bzr.

Either one will do, we can re-target if needed once we understand the
root cause (which is still quite mysterious to me).

<snip/>

    >> > Any ideas? (Does anyone else use webdav?)

Using webdav requires setup on the server side, since bzr+ssh is a
better solution most people install bzr on the server and don't bother
with webdav. Therefore, very few people use wedav ;)

    >> 
    >> Did you upgrade anything else than bzr itself, did you have a working
    >> setup before that, is there some unusual pattern regarding the access
    >> rights for the files/dirs there ?
    >> 
    >> '400' is the error code for 'Bad Request'... could it be that somehow
    >> the webdav server part is configured in such a way that it's not enabled
    >> there ?
    >> 
    >> Are you may be pushing to a new path where webdav is not configured ?

    > I have a setup that worked perfectly fine between bzr 2.0 and 2.5b1.

    >> > Note that I patched the webdav module to work with bzr 2.5 - was just a
    >> > missing function parameter, so that cannot cause the problem:
    >> > https://code.launchpad.net/~andidog/bzr-webdav/trunk
    >> > <https://code.launchpad.net/%7Eandidog/bzr-webdav/trunk>
    >> 
    >> I've commented there, thanks for that.

    > Thanks for having a look.

Thanks to you for clarifying the issue there,

       Vincent