danlarkin wrote:

I'm using bazaar version control [0] for my django site.  Developing locally and then (hopefully) pushing up to my webfaction account.  Is it possible to have the bazaar binary installed on the servers?  And set up so that I can push/pull from a repository on my account?  Or do I need to download the source myself and install it.  If so, not a big deal; but other webfaction users might appreciate the option to use bazaar version control as well.

Also, I'd love to have the option to use trac with the bazaar version control plugin [1].


--Dan Larkin


[0] http://bazaar-vcs.org/
[1] https://launchpad.net/trac-bzr

I installed bazaar on your server. I also installed the python cElementTree and paramiko modules.

For the Trac module, can you try to run it on your own ?


Cheers,

Remi.

How I installed trac-bzr on webfaction:

I'm assuming you know how to install a trac application from the webfaction panel.  Do that first.

1) Obtain the trac-bzr sources from https://launchpad.net/trac-bzr/
    a) I used: "wget http://launchpadlibrarian.net/7517262/t … r.gz" but by the time you read this there may be a new version available, so you should get that one.

2) Unpack the sources
    a) I unpacked in ~/src/

3) On a server that you administer this step would be a little easier, but since we're running in a constrained shared-hosting environment we have to get a little bit creative.
    a) Create a symlink in ~/lib/python2.4/ named site-packages pointing to ~/lib/python2.4/
        1) run: "ln -s ~/lib/python2.4 ~/lib/python2.4/site-packages"
    b) The reason we have to do this is because of the limitations of python setuptools, --install-dir seems not to work, so we need to use --prefix, which requires a directory named site-packages.

4) Now install the trac-bzr sources
    a) run: "setup.py install --prefix=/home/danlarkin/lib/python2.4/" from the directory where you unpacked the sources.

5) Now you can delete the symlink
    a) run: rm ~/lib/python2.4/site-packages

6) Now edit the trac.ini file in your trac webapp
    a) I used: "emacs ~/webapps/trac/conf/trac.ini"
    b) Under the [trac] section change "repository_type = svn" to "repository_type = bzr"
    c) Also under [trac] change the "repository_dir" to something along the lines of "/home/USERNAME/bzr"
    d) Add a new section to the bottom of the file called "[components]" and add "tracbzr.* = enabled" underneath it.

7) Create the directory you put for the repository_dir
    a) I used: "mkdir ~/bzr"


Now you can but your bazaar repositories in ~/bzr/ and they'll show up in trac.  Sweet, eh?

P.S. Hopefully I wrote this up right; please correct me if I missed a step or misspoke about something.

--Dan Larkin

How would I go about requesting an install of Bazaar?

Coming across a few django projects using it - so would be a great feature to have.

thanks

Damon

That worked. I am still learning my way around UNIX had not used easy install before.

thanks

Damon

Last edited by dkiesow (2007-12-17 12:37:08)

I'm currently hosted on a shared hosting plan, so I ran into trouble with the above instructions on installing Bazaar (bzr). So here's what worked for me:

*Note: I use python2.5. If you use a different version, then make sure you make the appropriate changes to the commands below. Don't forget to replace each instance of "USERNAME" with your own username. (These instructions are for accounts on *shared hosting*)

1. Check if you have site-packages directory in your Python install.
    RUN: "ls ~/lib/python2.5"

2. If you see "site-packages" listed as one of the results, go to step 3. If not, make the directory:
    RUN: "mkdir ~/lib/python2.5/site-packages"
   
3. Make sure you have the site-packages directory in your Python path.
    RUN: "export PYTHONPATH=/home/USERNAME/lib/python2.5/site-packages"
   
4. Now we're ready to install bzr.
    RUN: "easy_install-2.5 --prefix=/home/USERNAME -s /home/USERNAME/bin/ http://bazaar-vcs.org/releases/src/bzr- … r.gz"
   
*Note: I'm using version 1.5, but there may be a newer version by now. Change the "http://bazaar-vcs.org/releases/src/bzr-[Version/Release].tar.gz" part to match what you want.

5. Sit back and watch the install. (optional)



That should do it. Happy Bzr-ing!

- Mark Ferrer

Last edited by mvferrer (2008-07-21 16:02:11)

sebzur wrote:

Can I please have bazaar installed at my server? It is web63.

You can install bzr into your home directory with the following command:

easy_install-2.5 -d $HOME/lib/python2.5 -s $HOME/bin https://launchpadlibrarian.net/20236262/bzr-1.10.tar.gz

Just copy and paste that into a SSH session - it's that easy!

Regards,

Sean F
--
WebFaction - Agile hosting for everyone
http://webfaction.com - http://twitter.com/webfaction

Are you sure your Trac is using Python2.5? The version installed via our control panel uses Python 2.4, so you'll need to either change the easy_install command above to use 2.4, or change your Trac to use 2.5

Are you sure bzr is installed? I can't get it to work.

[nbv4@web82 utils]$ bzr branch lp:django-openid-auth
-bash: bzr: command not found

sime wrote:

nbv4 wrote:

Are you sure bzr is installed? I can't get it to work.

Have you followed instructions to install it in your home directory? You might also need to adjust your PATH environment variable, something in the form of:

Code:

export PATH=$HOME/bin:$PATH

in your .bashrc file.

Regards,

oh crap sorry I didnt see that post. it's working now. next time maybe i should try reading the thread...

I just looked in your home directory and saw that you're modifying your $PATH in .bash_profile. Try modifying it in your .bashrc instead (since .bash_profile is only used for interactive login sessions).

codercpf wrote:

Ok, that did help the lot (that + ln -s'ing bzrlib to $HOME/lib/python2.4)

Now I get this nice internal error, don't know why, don't know how, stuff like that. I'm googling the lot at the moment, but perhaps people here have heard of it and know the resolve?

Code:

Trac detected an internal error:

TypeError: can't compare datetime.datetime to float

Can you provide any more information about the error? Is there a full traceback? What are you doing immediately before you see the error?

Cool