[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Bazaar branch of Emacs.app

From: Thomas Christensen
Subject: Re: Bazaar branch of Emacs.app
Date: Mon, 14 Apr 2008 09:40:57 +0200
User-agent: Gnus/5.11 (Gnus v5.11) Emacs/22.2.50 (darwin)

Hi emacs-devel

Stefan Monnier <address@hidden> writes:

> I've setup a Bazaar branch (based on Jason's mirror) of Emacs.app.
> Get it from
>    sftp://arch.sv.gnu.org/archives/emacs/bzr/emacs.app
>    http://arch.sv.gnu.org/archives/emacs/bzr/emacs.app
> I recommend you use the "bzr.dev" version of Bzr: it's not blazingly
> fast yet, but it's better than 1.3 for some things.
> I haven't yet been able to build it on my GNU/Linux system: config.h
> says that HAVE_NS is undefined, so it looks like there's something
> broken in the configuration scripts.  Incidentally, the configuration
> needs to be integrated with the ./configure script (currently you're
> expected  to run nextstep/compile which then runs `configure').
> I encourage you to take a look at it, fix it, and when you find
> problems, to add them to nextstep/FOR_RELEASE.

If anyone want to try out the http transport, it will likely fail like

    $ bzr clone http://arch.sv.gnu.org/archives/emacs/bzr/emacs.app
    bzr: ERROR: Transport error: Server refuses to fullfil the request

This is due to bzr trying to get a file named `smart' which isn't
there.  This is OK for bzr if the server told it 404, but the server
at savannah says 403, and bzr stops.

The following patch against bzr.dev will fix it (it works, but I am no
bzr expert).


=== modified file 'bzrlib/transport/http/_urllib2_wrappers.py'
--- bzrlib/transport/http/_urllib2_wrappers.py  2008-03-17 19:53:19 +0000
+++ bzrlib/transport/http/_urllib2_wrappers.py  2008-04-13 00:52:26 +0000
@@ -1305,6 +1305,7 @@
     accepted_errors = [200, # Ok
                        206, # Partial content
+                       403, # Not found (or treat it as such for broken setups)
                        404, # Not found
     """The error codes the caller will handle.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]