Hi,
The VM running common-lisp.net 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).
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.
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 common-lisp.net manual monitoring of our dependencies.
These projects have Trac projects:
armedbear bknr cl-darcs cl-irc cl-markdown cl-openid cl-test-grid cl-trane cl-weblocks clfswm clo cmucl elephant f2cl fset gsharp isidorus mcclim movitz nio oct ucw usocket
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?
Regards,
On Oct 9, 2020, at 21:30, Erik Huelsmann ehuels@gmail.com wrote:
Hi,
The VM running common-lisp.net 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).
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.
After discussion on #common-lisp.net, the preliminary solution to this conundrum is to use the local customized python27 installation that I created under /srv/trac to maintain the Trac services.
More details to follow.
Cmucl's use of trac is mostly historical. We never moved the issues from trac to gitlab (no automated tools? Too lazy?). It's not used for anything else after migrating to gitlab. So they're only useful from an historical view where a release note or commit message references an issue.
I would be sad to see it go, but I'm not going to block any one from removing it.
On Fri, Oct 9, 2020 at 12:31 PM Erik Huelsmann ehuels@gmail.com wrote:
Hi,
The VM running common-lisp.net 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).
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.
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 common-lisp.net manual monitoring of our dependencies.
These projects have Trac projects:
armedbear bknr cl-darcs cl-irc cl-markdown cl-openid cl-test-grid cl-trane cl-weblocks clfswm clo cmucl elephant f2cl fset gsharp isidorus mcclim movitz nio oct ucw usocketSo 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?
Regards,
-- Bye,
Erik.
http://efficito.com -- Hosted accounting and ERP. Robust and Flexible. No vendor lock-in.
Hi Erik,
usocket can be ignore here, as it doesn't have any useful data on Trac. Thanks for your maintenance work.
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.
--Chun
On Oct 10, 2020, at 03:30, Erik Huelsmann ehuels@gmail.com wrote:
Hi,
The VM running common-lisp.net http://common-lisp.net/ 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).
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.
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 common-lisp.net http://common-lisp.net/ manual monitoring of our dependencies.
These projects have Trac projects:
armedbear bknr cl-darcs cl-irc cl-markdown cl-openid cl-test-grid cl-trane cl-weblocks clfswm clo cmucl elephant f2cl fset gsharp isidorus mcclim movitz nio oct ucw usocketSo 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?
Regards,
-- Bye,
Erik.
http://efficito.com http://efficito.com/ -- Hosted accounting and ERP. Robust and Flexible. No vendor lock-in.
-
Chun Tian -
Erik Huelsmann -
Mark Evenson -
Raymond Toy