On 2021-11-09 19:26, Chris Carr wrote: > - please could you explain why it is not suitable for inclusion in > bullseye? What is it that I am not seeing or experiencing in my daily > use of it?
Problem is, that Trac (up to version 1.4) used to be a Python 2 program. Python 2 is not supported anymore (or only in a very limited way), so many dependencies for Trac are removed from Debian. It was impossible to keep Trac with Python 2 in Debian. Now Trac (>= 1.5) is based on Python 3, but the new code is not yet considered stable by upstream. I hoped, that there were a Trac release 1.6 just in time for Debian 11, e.g. around 2021-01, but Trac development happens a little bit slower even than Debians. > Also, please could you recommend an alternative ticket management > package that is included in bullseye. Preferably one that will import > my trac db so I don't have to re-enter 11 years of history. If Trac works fine for you (it does for me!), just stay with Debian 10, e.g. in a systemd-nspawn or docker container. That's what we do in my company: We run a server with Debian 11 and a systemd-nspawn container of Debian 10 with Trac and PostgreSQL on it. As soon as Trac 1.6 is released, I'll try to get it into Debian, as well as some of the plugins, and hopefully it will be part of Debian 12. Cheers
