Page

python setup.py build

python-dev
hg clone http://hg.python.org/tracker/roundup
hg clone ssh://hg@hg.python.org/tracker/roundup
cd roundup
hg up bugs.python.org
sudo python setup.py install --prefix /opt/tracker-roundup/
sudo apt-get install postgresql
# Database administrative login by UNIX sockets
##local   all         postgres                          ident
local   all         postgres                          trust

# TYPE  DATABASE    USER        CIDR-ADDRESS          METHOD

# "local" is for Unix domain socket connections only
##local   all         all                               ident
local   all         all                               trust
# IPv4 local connections:
##host    all         all         127.0.0.1/32          md5
host    all         all         127.0.0.1/32          trust
# IPv6 local connections:
##host    all         all         ::1/128               md5
host    all         all         ::1/128               trust
sudo /etc/init.d/postgresql reload
sudo su - postgres
/Library/PostgreSQL/9.x/bin/pg_ctl restart -D /Library/PostgreSQL/9.x/data
$ psql -U postgres
postgres=# create user roundup;
postgres=# alter user roundup with createdb;
sudo pg_dropcluster --stop 9.1 main
sudo pg_upgradecluster 8.4 main
The PostgreSQL server failed to start. Please check the log output:
FATAL:  could not create shared memory segment: Invalid argument
DETAIL:  Failed system call was shmget(key=5432001, size=34922496, 03600).
HINT:  This error usually means that PostgreSQL's request for a shared memory segment exceeded your kernel's SHMMAX parameter.  You can either reduce the request size or reconfigure the kernel with larger SHMMAX.  To reduce the request size (currently 34922496 bytes), reduce PostgreSQL's shared memory usage, perhaps by reducing shared_buffers or max_connections.
        If the request size is already small, it's possible that it is less than your kernel's SHMMIN parameter, in which case raising the request size or reconfiguring SHMMIN is called for.
sysctl -a | grep -i shm
kernel.shmmax = 34922496
/etc/sysctl.d/30-postgresql-shm.conf
sudo sysctl -p
sudo sysctl kernel.shmmax=34922496
sudo apt-get install python-psycopg2
tar xzf psycopg2-2.3.2.tar.gz
cd psycopg2-2.3.2/
python setup.py build
sudo python setup.py install
sudo apt-get install python-dev
sudo apt-get install libpq-dev
hg clone http://hg.python.org/tracker/python-dev
hg clone ssh://hg@hg.python.org/tracker/python-dev
cd python-dev
hg clone http://hg.python.org/tracker/django-gae2django/
hg clone http://hg.python.org/tracker/rietveld/
cd python-dev
hg clone ssh://hg@hg.python.org/tracker/django-gae2django/
hg clone ssh://hg@hg.python.org/tracker/rietveld/
cd django-gae2django
hg up bugs.python.org
cd ..
cd rietveld
hg up bugs.python.org
cd instances/python-dev
mkdir db
echo postgresql > db/backend_name
roundup-admin init
debug = debugmail.txt
[mail]
[web]
debug = on
/opt/tracker-roundup/bin/roundup-admin -i <your python-dev directory> init
roundup.hyperdb.DatabaseError: FATAL:  password authentication failed for user "roundup"
roundup.configuration.OptionUnsetError: MAIL_DOMAIN is not set and has no default
/opt/tracker-roundup/bin/roundup-server -p 9999 python-dev=<your python-dev directory>
alias start-roundup='/opt/tracker-roundup/bin/roundup-server -p 9999 python-dev=<your python-dev directory>'
alias admin-roundup='/opt/tracker-roundup/bin/roundup-admin -i <your python-dev directory>'
.bashrc
~/.profile
/opt/tracker-roundup/bin/roundup-admin -i <your python-dev directory>
Roundup 1.4.10 ready for input.
Type "help" for help.
roundup> display user8
...
roundup> set user8 roles=Developer
roundup> commit
roundup>
[django]
secret_key = <the_secret_key>
cd rietveld
python manage.py syncdb
cd ..
PYTHONPATH=detectors/:/opt/tracker-roundup/lib/python2.7/site-packages/ python scripts/initrietveld
python manage.py runserver
scripts/addpatchsets
django.db.utils.DatabaseError: column codereview_repository.guid does not exist
LINE 1: ...itory"."url", "codereview_repository"."owner_id", "coderevie...
$ psql -U roundup
psql (9.1.4)
Type "help" for help.

roundup=> \d codereview_repository
     Table "public.codereview_repository"
... check here if some column is missing and if it is drop the table ...
roundup=> drop table codereview_repository cascade;
NOTICE:  drop cascades to constraint codereview_branch_repo_id_fkey on table codereview_branch
DROP TABLE
roundup=> \q

$ cd rietveld
$ python manage.py syncdb
Creating tables ...
Creating table codereview_repository
Installing custom SQL ...
Installing indexes ...
No fixtures found.
$ cd ..
$ PYTHONPATH=detectors/:/opt/tracker-roundup/lib/python2.7/site-packages/ python scripts/initrietveld
wget http://pypi.python.org/packages/source/i/irc/irc-5.0.1.zip
unzip irc-5.0.1.zip
cd irc-5.0.1/
sudo python setup.py install
cd ..

wget http://www.catb.org/~esr/irker/irker-1.15.tar.gz
tar -zxvf irker-1.15.tar.gz
ImportError: No module named hgtools.plugins
sudo python setup.py install
detectors/config.ini
[irker]
channels = irc://chat.freenode.net/python-dev
cd irker-1.15/
./irkerd &
./irkerd -d3
/opt/tracker-roundup/bin/roundup-admin -i <your python-dev directory>
roundup> list user
roundup> display userXXX
roundup> set userXXX roles=User,Developer
roundup> commit
roundup> set issueXXX messages=+YYY
roundup> commit
hg clone http://hg.python.org/tracker/jython/

-  ⇤ ← Revision 54 as of 2012-05-26 20:55:44 → 
  Size: 22671
  Editor: MartinvonLoewis
  Comment: Drop mentioning of M2Crypto and BeautifulSoup. Add Rietveld instructions.
+   ← Revision 56 as of 2012-12-14 10:11:45 → ⇥
  Size: 20757
  Editor: EzioMelotti
  Comment: wiki restore 2013-01-23
-Deletions are marked like this.
+Additions are marked like this.
 Line 1:
-This page describes how to enhance Python bug tracker instance at http://bugs.python.org/ To find some stuff to work on, look at the issues in [[http://psf.upfronthosting.co.za/roundup/meta/|meta tracker]] and DesiredTrackerFeatures page.
+This page describes how to enhance Python bug tracker instance at http://bugs.python.org/ To find some stuff to work on, look at the issues in [[http://psf.upfronthosting.co.za/roundup/meta/|meta tracker]] and [[DesiredTrackerFeatures|DesiredTrackerFeatures]] page.
-Line 7:
+Line 9:
-bugs.python.org is a [[http://roundup.sourceforge.net|Roundup tracker]] instance named `python-dev`. Below is a HowTo to get the similar setup for development on your machine.
+bugs.python.org is a [[http://www.roundup-tracker.org/|Roundup tracker]] instance named `python-dev`. Below is a [[HowTo|HowTo]] to get the similar setup for development on your machine.
-Line 12:
+Line 15:
- * Roundup, from the vendor branch used for python-dev (see below).

 * PostgreSQL for use as backend database.

 * Installation of psycopg.

 * A checkout of the spambayes_integration (instructions are given below).

 * A checkout of the python-dev instance from python's subversion repository (instructions are given below).
+ * Roundup

 * PostgreSQL for use as backend database

 * psycopg

 * the python-dev instance


== Tracker repos ==


All the Mercurial repositories used for the tracker can be found at http://hg.python.org/tracker/, and they are:


 * '''roundup''': a clone of the original Roundup with our modifications;
 * '''python-dev''': the instances used on bugs.python.org;
 * '''meta''': the instance used for the meta tracker;
 * '''jython''': the instance used for the jython tracker;
 * '''setuptools''': the instance used for the setuptools tracker;
 * '''rietveld''': a clone of Rietveld used to do reviews on the bug tracker;
 * '''django-gae2django''': a clone of django-gae2django necessary for rietveld;
-Line 24:
+Line 42:
-For python-dev, we use a slightly modified version of Roundup which has
some features that are not yet in the core Roundup. To keep track of
the changes, we keep a vendor branch of roundup.

Check out [[http://svn.python.org/view/tracker|/tracker]] from the python subversion repository:
 * Read-only checkout
{{{
  svn co http://svn.python.org/projects/tracker
}}}
 * Or if you have write access to repository
{{{
  svn co svn+ssh://pythondev@svn.python.org/tracker
}}}

The tracker directory contains the roundup source and the instances (e.g. python-dev, spambayes, jython, meta tracker).

cd in the tracker/roundup-src dir and install Roundup using setup.py (note: you might need privileges to run this command):

{{{
  cd roundup-src
  sudo python setup.py install --prefix /opt/tracker-roundup/
}}}
+The [[http://hg.python.org/tracker/roundup/|roundup]] repo is a clone of http://roundup.hg.sourceforge.net/hgweb/roundup/roundup that contains an additional branch named "bugs.python.org" that contains some modification we made to Roundup.


To get a clone of roundup use:


 * Read-only clone
 {{{
hg clone http://hg.python.org/tracker/roundup
}}}

 * Read/Write clone (if you have write access to the repository)
 {{{
hg clone ssh://hg@hg.python.org/tracker/roundup
}}}



Before installing roundup, '''remember to change branch''', otherwise the instances won't work:


{{{
cd roundup
hg up bugs.python.org
}}}


To install roundup use:


{{{
sudo python setup.py install --prefix /opt/tracker-roundup/
}}}
-Line 49:
+Line 80:
-For the python-dev tracker instance we use PostgreSQL as backend
database. Roundup has support for many different databases for backend
(anydbm, metakit, MySQL, PostgreSQL, SQLite...), but for the python-dev
instance, PostgreSQL was selected as it has the best performance for
large installations. Also, for performance reasons, there is at least
one place in the python-dev instance that has a hardcoded dependency
on the backend being an SQL-based one, so you do need PostgreSQL even
for development work (another SQL-based backend might work, but this
has not been tested). I recommend that you run postgreSQL to make your
development environment behave exactly like the environment the real
tracker runs in.

Details on how to install PostgreSQL is outside the scope of this Wiki
Page ({{{sudo apt-get install postgresql}}} should be enough). 
Both version 7.4 and 8.1 of PostgreSQL has been tested without
any known problems. It has been reported that 8.2, 8.3, 8.4, and 9.1 work well.

Access configuration of postgresql can be tricky. You need to make
sure that the user you're running roundup as (your unix/windows user)
has access to the postgresql database you intend to use for roundup,
as the postgresql user you've configured in roundup's configuration.

For a development environment with no demands on security, the easiest
way to configure this is probably to allow all users to connect as any
database user as long as the request originates from the local
host. This can be accomplished editing pg_hba.conf (usually found in
/etc/postgresql/8.x/main/ in Linux or /Library/PostgreSQL/9.x/data/ in Mac OS X -- you might need privileges to edit it). The end of the
file should look like this (the four changed lines are preceded by ##):
+For the python-dev tracker instance we use PostgreSQL as backend database. Roundup has support for many different databases for backend (anydbm, metakit, MySQL, PostgreSQL, SQLite...), but for the python-dev instance, PostgreSQL was selected as it has the best performance for large installations. Also, for performance reasons, there is at least one place in the python-dev instance that has a hardcoded dependency on the backend being an SQL-based one, so you do need PostgreSQL even for development work (another SQL-based backend might work, but this has not been tested). I recommend that you run postgreSQL to make your development environment behave exactly like the environment the real tracker runs in.


Details on how to install PostgreSQL is outside the scope of this Wiki Page ({{{sudo apt-get install postgresql}}} should be enough). Both version 7.4 and 8.1 of PostgreSQL has been tested without any known problems. It has been reported that 8.2, 8.3, 8.4, and 9.1 work well.


Access configuration of postgresql can be tricky. You need to make sure that the user you're running roundup as (your unix/windows user) has access to the postgresql database you intend to use for roundup, as the postgresql user you've configured in roundup's configuration.


For a development environment with no demands on security, the easiest way to configure this is probably to allow all users to connect as any database user as long as the request originates from the local host. This can be accomplished editing pg_hba.conf (usually found in /etc/postgresql/8.x/main/ in Linux or /Library/PostgreSQL/9.x/data/ in Mac OS X -- you might need privileges to edit it). The end of the file should look like this (the four changed lines are preceded by ##):
-Line 96:
+Line 114:
-'''PLEASE NOTE''': This is not a secure configuration on a multi-user
machine.

After the change in pg_hba.conf, reload your postgreSQL database to
make sure it knows about your new access
configuration. Something similar to
+'''PLEASE NOTE''': This is not a secure configuration on a multi-user machine.


After the change in pg_hba.conf, reload your postgreSQL database to make sure it knows about your new access configuration. Something similar to
-Line 105:
+Line 124:
-Line 107:
+Line 128:
 On Mac OS X, do {{{sudo su - postgres}}}. Then use pg_ctl to restart the server:
-Line 113:
+Line 139:
-Create a database user that is allowed to create databases. This user
will be used when roundup connects to the database.
+Create a database user that is allowed to create databases. This user will be used when roundup connects to the database.
-Line 122:
+Line 152:
-Line 124:
+Line 155:
-Line 126:
+Line 158:
-Line 128:
+Line 161:
-. Remove the new default cluster using {{{sudo pg_dropcluster --stop 9.1 main}}};

3. Update the old clusted with {{{sudo pg_upgradecluster 8.4 main}}};
+. Remove the new default cluster using {{{sudo pg_dropcluster --stop 9.1 main}}};


3. Update the old clusted with {{{sudo pg_upgradecluster 8.4 main}}};
-Line 133:
+Line 169:
-Line 140:
+Line 178:
-you check the value of shmmax with {{{sysctl -a | grep -i shm}}}.
You can change the value permanently adding {{{kernel.shmmax = 34922496}}} in {{{/etc/sysctl.d/30-postgresql-shm.conf}}} and running {{{sudo sysctl -p}}} to apply the changes, or temporarily with {{{sudo sysctl kernel.shmmax=34922496}}}.
+you check the value of shmmax with {{{sysctl -a | grep -i shm}}}. You can change the value permanently adding {{{kernel.shmmax = 34922496}}} in {{{/etc/sysctl.d/30-postgresql-shm.conf}}} and running {{{sudo sysctl -p}}} to apply the changes, or temporarily with {{{sudo sysctl kernel.shmmax=34922496}}}.
-Line 145:
+Line 185:
-Line 147:
+Line 188:
-Line 148:
+Line 190:
-Line 151:
+Line 195:
-Line 152:
+Line 198:
-Line 158:
+Line 206:
-Line 159:
+Line 209:
- * "fatal error: Python.h: No such file or directory", you need to {{{sudo apt-get install python-dev}}};
 * "fatal error: libpq-fe.h: No such file or directory", you need to {{{sudo apt-get install libpq-dev}}};
+ * "fatal error: Python.h: No such file or directory", you need to {{{sudo apt-get install python-dev}}};
 * "fatal error: libpq-fe.h: No such file or directory", you need to {{{sudo apt-get install libpq-dev}}};
-Line 163:
+Line 217:
-== Checkout spambayes_integration ==

If you don't want to install SpamBayes, you have to use a [[#SpamBayes_dummy_configuration |dummy configuration]].

'''Note''': If you followed [[#Installing_Roundup|the instructions]] and checked out {{{http://svn.python.org/projects/tracker}}} you can '''skip this step'''.

The !SpamBayes detector is '''optional''', but you must still check out the {{{spambayes_integration}}} instance.

You can get a checkout of {{{spambayes_integration}}} with:
{{{
  svn co http://svn.python.org/projects/tracker/instances/spambayes_integration
}}}

If you do intend to use it, you will need to also [[#SpamBayesSetup | install SpamBayes proper and configure it appropriately]].
-Line 180:
+Line 220:
-'''Note''': If you followed [[#Installing_Roundup|the instructions]] and checked out {{{http://svn.python.org/projects/tracker}}} you can '''skip this step'''.

The [[http://svn.python.org/view/tracker/instances/python-dev/ |python-dev]] tracker instance is version-controlled with subversion,
and resides in the python subversion repository.

{{{
  svn co http://svn.python.org/projects/tracker/instances/python-dev
}}}

Keep in mind that the python-dev instance has relative symlinks to {{{../../spambayes_integration/[...]}}},
so if you did separate checkouts and your directory layout is different you have to update these links:
{{{
extensions/spambayes.py -> ../../spambayes_integration/extensions/spambayes.py

detectors/spambayes.py -> ../../spambayes_integration/detectors/spambayes.py

}}}
+To get a clone of the [[http://hg.python.org/tracker/python-dev/|python-dev]] tracker instance use:


 * Read-only clone
 {{{
hg clone http://hg.python.org/tracker/python-dev
}}}

 * Read/Write clone (if you have write access to the repository)
 {{{
hg clone ssh://hg@hg.python.org/tracker/python-dev
}}}
-Line 200:
+Line 238:
-Running the Rietveld code review tool is optional. If you want to work on it,
check out

{{{
  hg clone http://hg.python.org/tracker/django-gae2django/
  hg clone http://hg.python.org/tracker/rietveld/
}}}

In addtion, Django needs to be installed; e.g. the Django 1.2 or 1.3 Debian packages work fine.
+Running the Rietveld code review tool is optional. If you want to work on it, check out the django-gae2django and rietveld clones in the python-dev/ directory:


 * Read-only clone
 {{{
cd python-dev
hg clone http://hg.python.org/tracker/django-gae2django/
hg clone http://hg.python.org/tracker/rietveld/
}}}

 * Read/Write clone (if you have write access to the repository)
 {{{
cd python-dev
hg clone ssh://hg@hg.python.org/tracker/django-gae2django/
hg clone ssh://hg@hg.python.org/tracker/rietveld/
}}}



After getting the clones '''remember to update the branches to bugs.python.org''':


{{{
cd django-gae2django
hg up bugs.python.org
cd ..
cd rietveld
hg up bugs.python.org
}}}


In addition, Django needs to be installed; e.g. the Django 1.2 or 1.3 Debian packages work fine.
-Line 212:
+Line 275:
-Now enter the python-dev directory, and create the 'db' directory (not
in svn as it's just to much fuzz to keep it there - every time you run
''roundup-admin init'' it is removed and recreated, confusing svn who
wants to keep its .svn directory intact), as well as the
db/backend_name file which decides which backend (i.e. database type)
to use:
+Now enter the python-dev directory, and create the 'db' directory, as well as the db/backend_name file which decides which backend (i.e. database type) to use:
-Line 225:
+Line 288:
-Copy python-dev/config.ini.template into config.ini, and modify it
according to your site. Pay special attention to settings marked with
''NO DEFAULT''. However, if you've configure your PostgreSQL as above,
most settings should be OK.

If you need to do development on the '''busybody''' or '''tellteam''' detectors,
copy detectors/config.ini.template into detectors/config.ini, and
adjust the e-mail addresses accordingly.
+Note: the db dir contains all the messages and files attached to issues, and it's removed and recreated every time you run {{{roundup-admin init}}}.


Copy python-dev/config.ini.template into config.ini, and modify it according to your site. Pay special attention to settings marked with ''NO DEFAULT''. However, if you've configure your PostgreSQL as above, most settings should be OK.


If you need to do development on the '''busybody''' or '''tellteam''' detectors, copy detectors/config.ini.template into detectors/config.ini, and adjust the e-mail addresses accordingly.
-Line 235:
+Line 299:
-Line 238:
+Line 304:
-at the end of the {{{[mail]}}} section.  The mail will just be saved on the file you specify.

If you want to see the tracebacks in the browser instead of having them sent by email,
at the end of the {{{[web]}}} section set
+at the end of the {{{[mail]}}} section. The mail will just be saved on the file you specify.


If you want to see the tracebacks in the browser instead of having them sent by email, at the end of the {{{[web]}}} section set
-Line 246:
+Line 316:
-<<Anchor(ciavc)>> The '''CIA.vc''' detector sends emails about issue changes
and is on by default. Disable it by adding a {{{return}}} to its init() function (detectors/cia.py):

{{{
 def init(db):
     return # <--
     db.issue.react('create', sendcia)
     db.issue.react('set', sendcia)
}}}
-Line 258:
+Line 319:
-Line 262:
+Line 327:
-Line 264:
+Line 330:
-Line 266:
+Line 333:
-Line 267:
+Line 335:
- * "{{{roundup.hyperdb.DatabaseError: FATAL:  password authentication failed for user "roundup"}}}" check again pg_hba.conf;
 * "{{{roundup.configuration.OptionUnsetError: MAIL_DOMAIN is not set and has no default}}}" set the option in python-dev/config.ini, [mail] section, domain;

'''Note''': it is possible to set the [mail] domain to "NO DEFAULT" to make the {{{init}}} work.
However Roundup needs a mail server to send mails so you'll need to configure at the least the admin mail later on.
It might be possible to have Roundup work with no mails at all, but the right configuration is still unknown (feel free to experiment with it!).
+ * "{{{roundup.hyperdb.DatabaseError: FATAL:  password authentication failed for user "roundup"}}}" check again pg_hba.conf;
 * "{{{roundup.configuration.OptionUnsetError: MAIL_DOMAIN is not set and has no default}}}" set the option in python-dev/config.ini, [mail] section, domain;
-Line 276:
+Line 343:
-Line 280:
+Line 351:
-Line 281:
+Line 353:
-Line 284:
+Line 358:
-Line 285:
+Line 361:
-Line 288:
+Line 366:
-Line 290:
+Line 370:
-You should now be able to browse http://localhost:9999/python-dev/ and
get a roundup instance that looks just like http://bugs.python.org, except for some missing new values for fields like Stages and Keywords. It's possible to replace '''initial_data.py'''  with an [[attachment:initial_data_updated.py | updated version]] so that your fields will have values that match those currently present in the Python Tracker.
+You should now be able to browse http://localhost:9999/python-dev/ and get a roundup instance that looks just like http://bugs.python.org, except for some missing new values for fields like Stages and Keywords. It's possible to replace '''initial_data.py''' with an [[TrackerDevelopment?action=AttachFile&do=view&target=initial_data_updated.py|updated version]] so that your fields will have values that match those currently present in the Python Tracker.
-Line 295:
+Line 376:
-Create an user from User->register in the left sidebar.
You can then use roundup-admin to set developer privileges for it:
+Create an user from User->register in the left sidebar. You can then use roundup-admin to set developer privileges for it:
-Line 308:
+Line 391:
-Line 310:
+Line 394:
-== SpamBayes Setup ==
If you intend to use the !SpamBayes detector to weed out spam from your tracker you will need to install it and start an instance of its {{{core_server}}} application.
Briefly:

 * Download and install at least version 1.1a4 of the [[http://sourceforge.net/projects/spambayes|SpamBayes source]] from !SourceForge.  If you are running on Windows '''do not''' use the binary installer!
 * Establish a basic configuration, e.g.:

Devote a directory to it, e.g.:
{{{
 SBDIR=/usr/local/spambayes/core_server  # or whatever...
 mkdir -p $SBDIR
}}}
Create an INI file:
{{{
 cd $SBDIR
 cat > bayescustomize.ini <<EOF
[globals]
verbose:False

[Headers]
include_evidence:True
include_score:True

[Tokenizer]
record_header_absence:True
summarize_email_prefixes:True
summarize_email_suffixes:True
mine_received_headers:True
x-pick_apart_urls:True
x-fancy_url_recognition:False
x-lookup_ip:True
lookup_ip_cache:$SBDIR/dnscache.pck
max_image_size:100000
crack_image_cache:$SBDIR/imagecache.pck

crack_images:True
image_size:True
ocr_engine:gocr
[Classifier]
use_bigrams:False

[Categorization]
ham_cutoff:0.2
spam_cutoff:0.85

[Storage]
persistent_storage_file:$SBDIR/hammie.db
persistent_use_database:pickle
messageinfo_storage_file:$SBDIR/messageinfo.fs

[html_ui]
display_score:True
EOF
}}}
Finally, run it:
{{{
 BAYESCUSTOMIZE=$SBDIR/bayescustomize.ini core_server.py -m XMLRPCPlugin
}}}
 * If you are seeing image spam (this seems not to be a problem with wiki spam - yet), download and install [[http://jocr.sourceforge.net/|GOCR]].
-Line 372:
+Line 397:
-The Roundup and Rietveld data are stored in the same Postgres database. After the Roundup tables have been created, run

{{{
  cd rietveld
  python manage.py syncdb
  cd ..
  python scripts/initrietveld
}}}
+The Roundup and Rietveld data are stored in the same Postgres database. After the Roundup tables have been created, add to python-dev/config.ini:





{{{
[django]
secret_key = <the_secret_key>
}}}


To generate the secret key you can use an online django secret key generator, or just put an arbitrary string.


Before continuing make sure to check with "hg branch" that the branch is "bugs.python.org" on both the rietveld and the django-gae2django clones.


{{{
cd rietveld
python manage.py syncdb
cd ..
PYTHONPATH=detectors/:/opt/tracker-roundup/lib/python2.7/site-packages/ python scripts/initrietveld
}}}
-Line 383:
+Line 426:
-Line 385:
+Line 429:
-{{{
  python manage.py runserver
}}}

This will run Rietveld by default on port 8000. Alternatively to the development server, you can
also configure your web server to run rietveld.wsgi under the /review URL.

Rietveld patchset creation is an offline activity. If you have new patches in your tracker instance,
run

{{{
  scripts/addpatchsets
}}}

== Common Problems ==

=== SpamBayes dummy configuration ===
Incomplete/Missing !SpamBayes setup:: In your detectors/config.ini file set {{{spambayes_uri}}} to a syntactically valid, but nonexistent URI, e.g.:

{{{
    spambayes_uri = "http://localhost:9999/nobodyhere"
}}}

Another workaround is to:

1. disable the {{{sb_is_spam}}} function in extensions/spambayes.py adding a {{{return False}}}:
  {{{
def sb_is_spam(obj):
    return False  # <- add this
    cutoff_score = float(obj._db.config.detectors['SPAMBAYES_SPAM_CUTOFF'])
   }}}
2. disable the {{{may_view_spam.__call__}}} method in schema.py adding a {{{return True}}}:
  {{{
     def __call__(self, db, userid, itemid):
         return True  # <- add this
         cutoff_score = float(db.config.detectors['SPAMBAYES_SPAM_CUTOFF'])
  }}}
3. disable the {{{is_spam}}} function in detectors/sendmail.py adding a {{{return False}}}:
  {{{
def is_spam(db, msgid):
    """Return true if message has a spambayes score above
    db.config.detectors['SPAMBAYES_SPAM_CUTOFF']. Also return true if
    msgid is None, which happens when there are no messages (i.e., a
    property-only change)"""
    return False  # <- add this
    if not msgid:
  }}}

'''Note:''' this is just a workaround, and these changes will be visible with {{{svn diff}}}, so pay attention to not commit them accidentally.  A better fix would be to add a config option to enable/disable spambayes.

Check [[http://mail.python.org/pipermail/tracker-discuss/2008-February/001549.html |other available workarounds]].

=== Misbehaving detectors ===
Problematic detectors may be disabled by [[#ciavc |returning from their init() function]], as was the case of detectors/audit2to3.py (no longer present). Note that this would be a temporary solution before a graceful fix became available. Reporting issues with local instances is the best way help solving the problem.
+{{{
python manage.py runserver
}}}


This will run Rietveld by default on port 8000. Alternatively to the development server, you can also configure your web server to run rietveld.wsgi under the /review URL.


Rietveld patchset creation is an offline activity. If you have new patches in your tracker instance, run





{{{
scripts/addpatchsets
}}}


If you get errors like:


{{{
django.db.utils.DatabaseError: column codereview_repository.guid does not exist
LINE 1: ...itory"."url", "codereview_repository"."owner_id", "coderevie...
}}}


you can try to remove the table(s) from the database and re-run syncdb and initrietveld:


{{{
$ psql -U roundup
psql (9.1.4)
Type "help" for help.

roundup=> \d codereview_repository
     Table "public.codereview_repository"
... check here if some column is missing and if it is drop the table ...
roundup=> drop table codereview_repository cascade;
NOTICE:  drop cascades to constraint codereview_branch_repo_id_fkey on table codereview_branch
DROP TABLE
roundup=> \q

$ cd rietveld
$ python manage.py syncdb
Creating tables ...
Creating table codereview_repository
Installing custom SQL ...
Installing indexes ...
No fixtures found.
$ cd ..
$ PYTHONPATH=detectors/:/opt/tracker-roundup/lib/python2.7/site-packages/ python scripts/initrietveld
}}}


== irker setup ==


irkerd is a daemon that sends notification on IRC whenever a message is added or an issue is created, and replaces the CIA.vc service.


You will need:


* irker: http://www.catb.org/esr/irker/


* the irc package: http://pypi.python.org/pypi/irc/


To install them you can use:


{{{
wget http://pypi.python.org/packages/source/i/irc/irc-5.0.1.zip
unzip irc-5.0.1.zip
cd irc-5.0.1/
sudo python setup.py install
cd ..

wget http://www.catb.org/~esr/irker/irker-1.15.tar.gz
tar -zxvf irker-1.15.tar.gz
}}}


If you get the error {{{ImportError: No module named hgtools.plugins}}} during the {{{sudo python setup.py install}}}, you can try the command again and it should automagically work.


Make sure that you have listed the address of the channels that should receive the messages in {{{detectors/config.ini}}}, e.g.:


{{{
[irker]
channels = irc://chat.freenode.net/python-dev
}}}


To start irker use:


{{{
cd irker-1.15/
./irkerd &
}}}


You can also use {{{./irkerd -d3}}} to see debugging messages.
-Line 442:
+Line 545:
-Line 444:
+Line 548:
-Line 446:
+Line 551:
-Since the Python Tracker is a slightly modified version of [[http://www.roundup-tracker.org |Roundup]], both Roundup's [[http://www.roundup-tracker.org/docs.html |Documentation]] and [[http://issues.roundup-tracker.org/ |issue tracker]] contain relevant information about how the Python Tracker works and problems one might find working with its code.
+Since the Python Tracker is a slightly modified version of [[http://www.roundup-tracker.org|Roundup]], both Roundup's [[http://www.roundup-tracker.org/docs.html|Documentation]] and [[http://issues.roundup-tracker.org/|issue tracker]] contain relevant information about how the Python Tracker works and problems one might find working with its code.
-Line 450:
+Line 557:
-Line 451:
+Line 559:
-Line 455:
+Line 565:
-Line 456:
+Line 567:
-Line 460:
+Line 573:
-Line 461:
+Line 575:
-Line 465:
+Line 581:
-Line 466:
+Line 583:
-Line 470:
+Line 589:
-Users have limited privileges and can edit just some of the fields in the issue page.  Developers can edit all the fields and remove msgs and files.  Coordinators can also mark/unmark messages as spam and change some of the settings of other users (e.g. if they submitted the contributor agreement).
+Users have limited privileges and can edit just some of the fields in the issue page. Developers can edit all the fields and remove msgs and files. Coordinators can also mark/unmark messages as spam and change some of the settings of other users (e.g. if they submitted the contributor agreement).
-Line 473:
+Line 595:
-Line 477:
+Line 601:
-The message will be added back in the right position.
(This should be equivalent to b.p.o/issueXXX?@action=edit&@add@messages=YYY, but this doesn't seem to work.)
+The message will be added back in the right position. (This should be equivalent to b.p.o/issueXXX?@action=edit&@add@messages=YYY, but this doesn't seem to work.)
-Line 483:
+Line 608:
-A [[http://psf.upfronthosting.co.za/roundup/meta/ |Meta Tracker]] is available for  handling bugs and features requests for the [[http://bugs.python.org/ |Python Tracker]].
+A [[http://psf.upfronthosting.co.za/roundup/meta/|Meta Tracker]] is available for handling bugs and features requests for the [[http://bugs.python.org/|Python Tracker]].
-Line 487:
+Line 614:
-See [[TrackerDevelopmentVirtualEnv]].

== Learn more About the Importer(s) ==

http://svn.python.org/projects/tracker/importer/README.rst has some information about the importer(s) written to convert sourceforge data into roundup data.
+See [[TrackerDevelopmentVirtualEnv|TrackerDevelopmentVirtualEnv]].
-Line 495:
+Line 620:
-Public test instance of the Python tracker: http://bot.bio.br/python-dev/  (currently offine)
+Public test instance of the Python tracker: http://bot.bio.br/python-dev/ (currently offine)
-Line 499:
+Line 626:
-Currently the email system is disabled (redirected to file), so people interested in having an account there to test new features should email [[http://mail.python.org/mailman/listinfo/tracker-discuss|tracker-discuss]] to get one. Maintained by DanielDiniz.
+Currently the email system is disabled (redirected to file), so people interested in having an account there to test new features should email [[http://mail.python.org/mailman/listinfo/tracker-discuss|tracker-discuss]] to get one. Maintained by [[DanielDiniz|DanielDiniz]].
-Line 504:
+Line 632:
-Line 506:
+Line 635:
-Line 508:
+Line 638:
-Line 509:
+Line 640:
-Line 520:
+Line 653:
-Currently the email system is disabled (redirected to file), so people interested in having an account there to test new features should email [[http://mail.python.org/mailman/listinfo/tracker-discuss|tracker-discuss]] to get one. Maintained by DanielDiniz.

There is also a list of additional DesiredTrackerFeatures for which no patches yet exist.

= Getting Your Own jython Tracker =

To set up a local jython tracker, please follow instructions for python-dev tracker with following exceptions:

 * There is no need for !BeautifulSoup and !M2Crypto
+Currently the email system is disabled (redirected to file), so people interested in having an account there to test new features should email [[http://mail.python.org/mailman/listinfo/tracker-discuss|tracker-discuss]] to get one. Maintained by [[DanielDiniz|DanielDiniz]].


There is also a list of additional [[DesiredTrackerFeatures|DesiredTrackerFeatures]] for which no patches yet exist.


= Getting Your Own Jython Tracker =


To set up a local Jython tracker, please follow instructions for python-dev tracker with following exceptions:
-Line 532:
+Line 668:
- * The code for jython tracker can be checked out using the command:

{{{
  svn co http://svn.python.org/projects/tracker/instances/jython
}}}
+ * The repository for Jython tracker can be cloned with:





{{{
hg clone http://hg.python.org/tracker/jython/
}}}
-Line 539:
+Line 680:
-CategoryTracker CategoryDevelopmentProcess
+[[CategoryTracker|CategoryTracker]] [[CategoryDevelopmentProcess|CategoryDevelopmentProcess]]

Page

User

Getting Your Own python-dev Tracker

Requirements

Tracker repos

Installing Roundup

Install and configure PostgreSQL

Upgrading PostgreSQL from 8.4 to 9.1

Installing psycopg or psycopg2

Checkout the python-dev instance

Checkout the Rietveld integration

Configure your Development Roundup Instance

Rietveld Setup

irker setup

Resources for Tracker Development

Getting Help

Using roundup-admin

The Meta Tracker

Setting Up an Instance in a VirtualEnv

The Test Tracker

The Experimental Tracker

Getting Your Own Jython Tracker