Unfortunately, with Trac version 1.5, you have to download the Trac code, make some modifications, and then install it.
This task can be easily done by someone familiar with Python, but I think there are parts that are difficult for ordinary users to do. I installed Trac 1.5 on Python 3.7 (as mentioned before, after making some code modifications). However, I am aware that many packages that Trac depends on do not yet support Python 3.10. We recommend using a version of Python less than 3.10 if possible. ------------------------------------------------------------------------ ------------------------------------ There is a future society, but my future is not what others do. Dept. of Information Science, Graduate School, Korea National Open University 2022년 9월 7일 (수) 오후 9:50, Roger Oberholtzer <roger.oberholt...@gmail.com>님이 작성: > On Wed, Aug 17, 2022 at 2:26 AM RjOllos <rjol...@gmail.com> wrote: > > > > > > > > On Tuesday, August 16, 2022 at 12:00:21 AM UTC-7 Roger Oberholtzer wrote: > >> > >> On Mon, Aug 15, 2022 at 11:10 PM RjOllos <rjo...@gmail.com> wrote: > >> > > >> > > >> > > >> > On Monday, August 15, 2022 at 1:50:22 AM UTC-7 Roger Oberholtzer > wrote: > >> >> > >> >> I'm getting pressure from our IT guys about the software on our Trac > >> >> server being a bit old. I decided to freeze it because the OS > >> >> maintainers (openSUSE) were aggressively removing Pytthon2 stuff. I > >> >> did not want to chance that anything went away or otherwise stopped > >> >> working. At some point I need to start updates again. That's my local > >> >> issue. > >> >> > >> >> I am trying to decide the best approach to take here. If I could > >> >> identify the Python packages that are used directly by Trac, perhaps > I > >> >> could just maintain those on this system, and let the rest get > updated > >> >> as needed. I know that the Python packages needed depends on what I > >> >> have enabled. And what additional things I have added. But does > anyone > >> >> know the Python packages required by Trac itself? Other than the core > >> >> Python release itself. > >> > > >> > > >> > Are you running Trac 1.4.x? > >> > >> 1.2.3. > >> > >> > The dependencies are listed on the TracInstall page. > >> > https://trac.edgewall.org/wiki/TracInstall#MandatoryDependencies > >> > >> Ok. I knew about that, but I forgot. It was what I was looking for. > > > > > > For 1.2, see: > > https://trac.edgewall.org/wiki/1.2/TracInstall > > > > > > -- > > You received this message because you are subscribed to the Google > Groups "Trac Users" group. > > To unsubscribe from this group and stop receiving emails from it, send > an email to trac-users+unsubscr...@googlegroups.com. > > To view this discussion on the web visit > https://groups.google.com/d/msgid/trac-users/fb0ed9b5-2305-4256-8193-8fe4665ffb21n%40googlegroups.com > . > > I have decided to try Trac 1.5 as the system on which this runs was > forced to move to Python3. Or, one can say that Python2 is difficult > to use on this system. > > Anyway, when I tried to install Trac 1.5x with this command: > > pip install https://download.edgewall.org/trac/Trac-latest-dev.tar.gz > > I get this: > > ---%<---- > > Collecting https://download.edgewall.org/trac/Trac-latest-dev.tar.gz > Downloading https://download.edgewall.org/trac/Trac-latest-dev.tar.gz > (5.4 MB) > ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 5.4/5.4 MB 705.8 kB/s eta > 0:00:00 > Preparing metadata (setup.py) ... error > error: subprocess-exited-with-error > > × python setup.py egg_info did not run successfully. > │ exit code: 1 > ╰─> [8 lines of output] > Traceback (most recent call last): > File "<string>", line 2, in <module> > File "<pip-setuptools-caller>", line 34, in <module> > File "/tmp/pip-req-build-h350rf4p/setup.py", line 32, in <module> > from trac.dist import get_l10n_trac_cmdclass > File "/tmp/pip-req-build-h350rf4p/trac/dist.py", line 30, in > <module> > from jinja2.ext import babel_extract as jinja2_extractor > ModuleNotFoundError: No module named 'jinja2' > [end of output] > > note: This error originates from a subprocess, and is likely not a > problem with pip. > error: metadata-generation-failed > > × Encountered error while generating package metadata. > ╰─> See above for output. > > note: This is an issue with the package mentioned above, not pip. > hint: See above for details. > > ---%<---- > > I think Jinja should be installed as part of this. But something > cannot be found. > > I'm using Python 3.10 for all this as it is the current default on my > openSUSE Tumbleweed Linux system. > > -- > Roger Oberholtzer > > -- > You received this message because you are subscribed to the Google Groups > "Trac Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to trac-users+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/trac-users/CANkOqwNLEq5su3%3DGkE0W1uLXoN9Ur9NjePwcoZ9e9q88bKnehg%40mail.gmail.com > . > -- You received this message because you are subscribed to the Google Groups "Trac Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to trac-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/trac-users/CAPCiUfxx80cyUzu6SxwWOtNuOn%3DW8dcre86e6uOpKeh5nbFJ%2Bw%40mail.gmail.com.
