Changes between Version 4 and Version 5 of TracRepositoryAdmin


Ignore:
Timestamp:
Oct 7, 2012, 5:32:49 PM (2 years ago)
Author:
trac
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • TracRepositoryAdmin

    v4 v5  
    108108/usr/bin/trac-admin /path/to/env changeset added "$1" "$2"
    109109}}}
     110Note: Ubuntu doesn't seem to like /usr/bin/trac-admin, so just use:
     111{{{#!sh
     112#!/bin/sh
     113export PYTHON_EGG_CACHE="/path/to/dir"
     114trac-admin /path/to/env/ changeset added "$1" "$2"
     115}}}
    110116On Windows (`post-commit.cmd`):
    111117{{{#!application/x-dos-batch
     
    136142}}}
    137143
    138 For Mercurial, add the following entries to the `.hgrc` file of each repository accessed by Trac (if [trac:TracMercurial] is installed in a Trac `plugins` directory, download [source:plugins/0.13/mercurial-plugin/tracext/hg/hooks.py hooks.py] and place it somewhere accessible):
     144For Mercurial, add the following entries to the `.hgrc` file of each repository accessed by Trac (if [trac:TracMercurial] is installed in a Trac `plugins` directory, download [trac:source:mercurial-plugin/tracext/hg/hooks.py hooks.py] and place it somewhere accessible):
    139145{{{#!ini
    140146[hooks]
     
    169175
    170176== Migration from a single-repository setup (Mercurial) == #MigrationMercurial
    171 The following procedure illustrates a typical migration from a Mercurial single-repository setup to multiple repositories. Please note that at the time of writing, no initial resynchronization or any hooks are necessary for Mercurial repositories - see #9485 for more information.
     177The following procedure illustrates a typical migration from a Mercurial single-repository setup to multiple repositories. Please note that at the time of writing, no initial resynchronization or any hooks are necessary for Mercurial repositories - see [trac:ticket:9485 #9485] for more information.
    172178
    173179 1. Upgrade to the latest version of the TracMercurial plugin.