Trac is very different from Fossil though: Fossil is version control software with "embedded" wiki and issue tracker, while Trac is a wiki and issue tracker which can, optionally, interface with one or more external vcs systems. Fossil stores the wiki and issue data in the repository itself (SQLite), while Trac stores it in an external database (PostgreSQL, MySQL etc.. SQLite would probably work too!).

I don't mean an application with tickets, source control and wiki.

I wanted to express (implement) tickets as wiki pages, and store them in source control; instead of 3 separate concepts.

BTW, I don't like how trac tickets work - it's impossible to do agile (statistical) planning with them.