<html><head><meta http-equiv="Content-Type" content="text/html; charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Hi Erik,<div class=""><br class=""></div><div class="">usocket can be ignore here, as it doesn't have any useful data on Trac. Thanks for your maintenance work.</div><div class=""><br class=""></div><div class="">P. S. I believe, by using "pyenv", any needed version of Python can be easily installed locally and be used for specific purposes without considering Debian packaging policy.</div><div class=""><br class=""></div><div class="">--Chun<br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On Oct 10, 2020, at 03:30, Erik Huelsmann <<a href="mailto:ehuels@gmail.com" class="">ehuels@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class=""><div class="">Hi,</div><div class=""><br class=""></div><div class="">The VM running <a href="http://common-lisp.net/" class="">common-lisp.net</a> needs an O/S upgrade: the host is running Debian Stretch which has gone EOL in July (but is receiving LTS updates for specific components). Due to package compatibility issues, the upgrade needs to go directly to Debian Bullseye (skipping Debian Buster).</div><div class=""><br class=""></div><div class="">We have a dependency problem with this upgrade: Debian Buster - which we'll skip - was the last to support Python 2.7. We depend on Python 2.7 for the following services: Trac, Mailman2.1, ViewVC and greylistd. All other services either don't depend on Python, or have Python3 compatible versions in Debian Bullseye. For Mailman2.1 we have a "simple" solution: migration to Mailman3. Mailman3 is a totally new application coming from the developers of Mailman2.1. For greylistd we will be able to either find an alternative or we can stop greylisting entirely. For ViewVC, we hope to see a release soonish which supports Python3 (and its inclusion in Debian); in its repository, there's support for Python3 already, as is the required Python3 support for the Subversion bindings.</div><div class=""><br class=""></div><div class="">This leaves us with just Trac which has been removed from Debian because of its Python 2.7 dependency. Looking at its homepage, there doesn't seem to be a Python3 compatible release yet. I really want to be running OS packages, because those include (security) releases when issues are found -- which saves the <a href="http://common-lisp.net/" class="">common-lisp.net</a> manual monitoring of our dependencies.</div><div class=""><br class=""></div><div class="">These projects have Trac projects:</div><div class=""><br class=""></div><div class=""> armedbear<br class=""> bknr<br class=""> cl-darcs<br class=""> cl-irc<br class=""> cl-markdown<br class=""> cl-openid<br class=""> cl-test-grid<br class=""> cl-trane<br class=""> cl-weblocks<br class=""> clfswm<br class=""> clo<br class=""> cmucl<br class=""> elephant<br class=""> f2cl<br class=""> fset<br class=""> gsharp<br class=""> isidorus<br class=""> mcclim<br class=""> movitz<br class=""> nio<br class=""> oct<br class=""> ucw<br class=""> usocket</div><div class=""><br class=""></div><div class="">So what's our next step? Do we go looking for a Trac alternative? Does anybody have contacts with the Trac team and can consult with them about their plans?</div><div class=""><br class=""></div><div class=""><br class=""></div><div class="">Regards,<br class=""></div><div class=""><br class="">-- <br class=""><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr" class="">Bye,<div class=""><br class=""></div><div class="">Erik.</div><div class=""><br class=""></div><div class=""><a href="http://efficito.com/" target="_blank" class="">http://efficito.com</a> -- Hosted accounting and ERP.</div><div class="">Robust and Flexible. No vendor lock-in.</div></div></div></div></div>
</div></blockquote></div><br class=""></div></body></html>