I have had a lot of problems after an upgrade of roundup.

I am on PPC linux, using the standalone server and the 'anydbm' backend; I had upgraded from the stable roundup-0.7.6 to the stable roundup-1.4.4 .

No pages were available from the server, and I was getting the message:
"A problem was encountered processing your request. The tracker maintainers have been notified of the problem." on every attempted access.

I eventually got a backtrace (via e-mail) which showed this on its last line:

ValueError: No permission "Web Registration" defined

Google could find me nothing on this precise message (so I am working on the basis that there are not many people in the same boat), but some of the information that I did turn up made me think that the problem was 'old-style templates' and the need to 'update the installed tracker instances'. See 'Please update roundup ebuild to a newer version' http://bugs.gentoo.org/34314 .

I couldn't find much information about old-style templates, but it seems that the templates before version 0.8 are old-style, and the ones from then on are not. I am fairly sure that old-style template use 'config.py' and UPPER-CASE and the current templates use 'config.ini' and lower-case.

A vital piece of documentation is /usr/share/doc/roundup-1.4.4/upgrading.txt.bz2 , though I can't find a stanza that deals with my problem. I suspect that at some point prior to version 1.4.4 the techniques needed to update instances (also called trackers) have become bit-rotten from want of use.

In particular, the commands:

roundup-admin migrate   
roundup-admin genconfig <tracker-home>

did not work for me and evinced the same error message as in the presenting complaint.

Here are a few ideas that might help the next person. Whilst this might not be for the faint of heart, the average Gentoo user should find it a piece of cake. Assume that you are working with a tracker called 'support' either for real or as a scratch example.

1. Show your current settings with a command like:

grep ^[A-Z] support/config.py

2. Delete these files:

rm support/__init__.py
rm support/__init__.pyc
rm support/__init__.pyo
rm support/config.py
rm support/config.pyc
rm support/config.pyo
rm support/dbinit.py
rm support/dbinit.pyc
rm support/dbinit.pyo
rm support/detectors/__init__.py
rm support/detectors/__init__.pyo
rm support/detectors/messagesummary.pyo
rm support/detectors/nosyreaction.pyo
rm support/detectors/statusauditor.pyo
rm support/detectors/userauditor.pyo
rm support/interfaces.py
rm support/interfaces.pyc
rm support/interfaces.pyo
rm support/select_db.py
rm support/select_db.pyc
rm support/select_db.pyo

3. Generate a blank tracker with a command like

roundup-admin install

and giving a junk tracker_home et cetera.

4. From that tracker copy these files and directories to your existing tracker with a command like:

cp -a config.ini extensions hmtl initial_data.py schema.py ../support

5. Using the info you saved in step 1, edit the lines in config.ini that refer to the web, the mailhost and e-mail addresses.

6. copy the file 'backend_name' to your existing tracker with a command like:

cp db/backend_name ../support/db

Now, I am not saying the you are done, nor that these steps are correct and/or sufficient. but this may help to get you started!

Grateful for any suggestions and/or further info.

This is/was covered in the upgrading howto. You should compare the
shipped schema.py with the one in the existing tracker and add any
missing definitions.