Source: https://foxhop.net/f3cf047c-2f95-11f1-8298-e86a64d24d78/trac-upgrade-and-migration
Snapshot: 2026-05-25T01:47:30Z
Generator: Remarkbox 1527ef7

This is a thread snapshot. The living document lives at the source URI above — it may have been edited, extended, or replied-to since.

Scan for living source

Trac Upgrade and Migration

We need to perform the following tasks:

Possible solutions to migrate tickets from old Trac project to new Trac project:

setup development env from hot-copy of prod

  1. create hot-copy of trac:

    trac-admin /path/to/projenv hotcopy /path/to/backupdir
  2. create a tar archive of hot backup:

    tar -czvf trac-2013-07-2.tar.gz /cars/archive/trac-hot-copy-backup
  3. on your workstation scp tar archive:

    cd ~
    mkdir trac
    cd trac
    scp old-server:/cars/archive/trac-2013-07-2.tar.gz .
  4. unarchive:

    tar xzvf trac-2013-07-2.tar.gz
  5. create virtualenv:

    cd trac-hot-copy-backup
    virtualenv .env
    source .env/bin/activate
  6. install Genshi==0.6 because Trac==0.12.2 breaks with Genshi==0.7:

    pip install Genshi==0.6
  7. install Trac==0.12.2:

    pip install Trac==0.12.2
  8. test setup:

    tracd --port=8800 --env-parent-dir ~/trac/
  9. open browser to http://127.0.0.1:8800

upgrade from Trac==0.12.2 to Trac==1.0.0

  1. bring hot-copy tracd server offline

  2. Update the Trac Code to Trac==1.0:

    # optional, but these directories are no longer used 
    #rm -rf ~/trac/trac-hot-copy-backup/htdocs/ ~/trac/trac-hot-copy-backup/templates/
    pip install Trac==1.0
  3. Upgrade the Trac environment:

    trac-admin ~/trac/trac-hot-copy-backup upgrade
    trac-admin ~/trac/trac-hot-copy-backup wiki upgrade
  4. test setup:

    tracd --port=8800 --env-parent-dir ~/trac/

upgrade again from Trac==1.0.0 to Trac==1.0.1

  1. bring hot-copy tracd server offline

  2. Update the Trac Code to Trac==1.0.1:

    # optional, but these directories are no longer used 
    #rm -rf ~/trac/trac-hot-copy-backup/htdocs/ ~/trac/trac-hot-copy-backup/templates/
    pip install Trac==1.0.1
  3. Upgrade the Trac environment:

    trac-admin ~/trac/trac-hot-copy-backup upgrade
    trac-admin ~/trac/trac-hot-copy-backup wiki upgrade
  4. test setup:

    tracd --port=8800 --env-parent-dir ~/trac/

dump ticket tables from hot-copy and import to new project

  1. move to db directory:

    cd ~/trac/trac-hot-copy-backup/db
  2. dump each table related to tickets:

    sqlite3 trac.db ".dump ticket" > trac_ticket.sql
    sqlite3 trac.db ".dump ticket_change" > trac_ticket_change.sql
    sqlite3 trac.db ".dump ticket_custom" > trac_ticket_custom.sql
    sqlite3 trac.db ".dump ticket_template_store" > trac_ticket_template_store.sql
    sqlite3 trac.db ".dump attachment" > trac_attachment.sql
    sqlite3 trac.db ".dump milestone" > trac_milestone.sql
    sqlite3 trac.db ".dump pastes" > trac_pastes.sql
  3. copy *.sql to the new trac project db directory

  4. become trac user:

    sudo su - trac
    bash
  5. import the tables:

    cat trac_ticket.sql | sqlite3 trac.db
    cat trac_ticket_change.sql | sqlite3 trac.db
    cat trac_ticket_custom.sql | sqlite3 trac.db
    cat trac_ticket_template_store.sql | sqlite3 trac.db
    cat trac_attachment.sql | sqlite3 trac.db
    cat trac_milestone.sql | sqlite3 trac.db
    cat trac_pastes.sql | sqlite3 trac.db
  6. copy files/attachments directory from hot-copy to new Trac project. Make sure owner:group is trac:trac:

    chown -R trac:trac files/attachments

trac database tables and explanations

attachment

KEEP - meta data for attachment files. Also need underlying attachment directory.

auth_cookie

DROP - cookie session data for logged in users

cache

DROP - only record: 901198563trac.wiki.api.WikiSystem.pages

component

DROP - we plan to create new components via config management

enum

DROP - we plan to create new enums (priority, severity, ticket_type, resolution) via config management

milestone

KEEP - we have 7 records that need to be moved, Trac defaults to Milestone 1, 2, 3, 4

node_change

DROP - empty

pastes

KEEP - we need to install paste plugin

permission

DROP - we don't need to migrate old permissions. we need a plan to place in config management

report

DROP - we don't need old reports. we might want to back them up as examples

repository

DROP - empty

revision

DROP - empty

session

DROP - session data for when people logged in and what they did to the trac system

session_attribute

DROP - session data for when people logged in and what they did to the trac system

subtickets

KEEP but DROP - we might need to transform this data to work with new subticket plugin

system

DROP - version numbers of plugins and modules

ticket

KEEP - tickets

ticket_change

KEEP - ticket history

ticket_custom

DROP - ticket custom fields, lots of garbage from old plugins. We will be generating a migration from subticket to new childticket plugin that will insert into this table.

ticket_template_store

KEEP - ticket templates which auto fill body message with text, discuss this

version

DROP - empty

wiki

DROP - discuss, we could migrate everything or we could migrate some pages

subtickets migration to child ticket plugin

dump out the data and edit with vim

sqlite3 trac.db
sqlite> .mode csv
sqlite> .out trac_subtickets.csv
sqlite> SELECT child,parent FROM subtickets;
sqlite> .exit
vim trac_subtickets.csv

run the following search and replace transformations:

%s/,/,"parent","#/g
%s/$/");/g
%s/^/INSERT INTO "ticket_custom" VALUES(/g

rename

cp trac_subtickets.csv trac_ticket_children.sql

Source: https://foxhop.net/f3cf047c-2f95-11f1-8298-e86a64d24d78/trac-upgrade-and-migration
Snapshot: 2026-05-25T01:47:30Z
Generator: Remarkbox 1527ef7