On Tuesday, November 19, 2019 at 8:26:31 PM UTC-8, thos wrote: > > On Tuesday, November 19, 2019 at 10:44:15 AM UTC-6, RjOllos wrote: >> >> >> I tend to push users towards creating a virtualenv and pip install'ing >> all of their packages, so as to have more control and not depend on the OS >> package maintainer in addition to the plugin maintainer. >> >> However, some users do like having the packages maintained by a Debian >> package maintainer, so I'll be interested to hear what others have to say. >> >> - Ryan >> > > I generally agree with the suggestion of using virtualenv, and that's what > we use for build environments. > > In this case we are trying to create a lightweight Docker container, so it > would be nice if the Debian package just worked. For the most part, they > do. Only on the Plugin Admin page is there a "glitch". > > I've diff'd the Debian and pip-install Trac==1.2.3 packages and have > identified a few differences: > > - Debian installs symlinks to jquery content because it is installed > by a separate package. The pip-install package has them embedded. > - jquery versions are different. Debian: 3.3.1, pip-install: 1.11.3 > - jquery-ui versions are different. Debian: 1.12.1, pip-install: 1.11.4 > - jquery time picker versions are also different. > - Several png files are different, and several of the jquery-ui/images > files are missing on Debian. > - jquery-ui-addons.css is different. > > I don't know if jquery is responsible for "unorganized content" on the > Plugin page. >
I very much doubt that jQuery is responsible. I've seen the issue you report using jQuery that ships with Trac. Debian really should not be using a jQuery version other than the one that ships with Trac. We don't know that jQuery 3.x is compatible with Trac, in fact when I've tried using it, I've found changes are needed to Trac JS code. https://trac.edgewall.org/ticket/12858 When this has come up before, I've suggested using jQuery from a CDN when using the Debian install: https://trac.edgewall.org/wiki/TracIni#trac-jquery_location-option > Regarding "apt-get install python-pip" I can reduce its overhead by adding > "--no-install-recommends", which eliminates the dev tools that aren't > needed to (re)install Trac. > > The relevant part of my Dockerfile is now: > > RUN apt-get update; apt-get install -y \ > apache2 \ > libapache2-mod-wsgi \ > libapache2-mod-svn \ > subversion \ > python \ > python-requests \ > trac \ > rsync \ > ; \ > *apt**-get install -y --no-install-recommends python-**pip* ; \ > rm -rf /var/lib/apt/lists/* ; \ > *pip install --ignore-installed --no-deps --no-cache-dir Trac==1.2.3* > > I still install trac via apt-get because it brings in several other > required and recommended dependencies, some of which require compiling. > It's only the trac and tracopt python packages that need to be "refreshed". > The root cause of the problem still eludes me. > > -- 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/94c1b13d-4ab7-4e4d-9849-845f0b04db66%40googlegroups.com.
