Re: [Trac] Re: Help: trac.* components appear as individual plugins on admin page
On Thursday, November 21, 2019 at 3:32:35 AM UTC-8, Jun Omae wrote:
>
> Hi,
>
> On 2019/11/21 14:10, thos wrote:
> > Found the problem.
> >
> > In the Debian distribution, the "Trac-1.2.3.egg-info" directory is
> missing the SOURCES.txt file. A RECORD file will also do.
> >
> > One of them needs to be present for "get_sources" to associate the
> bundled plug-ins as part of the same overall "Trac 1.2.3" plugin. From
> trac.util (__init__.py):
>
> Thanks for the investigating.
>
> I think the Trac debian package should have *.egg-info/SOURCES.txt file.
> Searching the SOURCES.txt file in debian packages, several packages have
> SOURCES.txt file.
>
> https://packages.debian.org/file:.egg-info/SOURCES.txt
>
> (If *.dist-info structure is used, RECORD file must be included. [2])
>
> However, according to The Internal Structure of Python Eggs [1], it seems
> that it is
> possible to have no SOURCES.txt file in egg-info structure.
>
> Work around:
>
> diff --git a/trac/util/__init__.py b/trac/util/__init__.py
> index 1d3485e09..8808ebf90 100644
> --- a/trac/util/__init__.py
> +++ b/trac/util/__init__.py
> @@ -700,6 +700,7 @@ def get_sources(path):
> """Return a dictionary mapping Python module source paths to the
> distributions that contain them.
> """
> +path = os.path.normpath(os.path.abspath(path))
> sources = {}
> for dist in find_distributions(path, only=True):
> if not dist.has_metadata('top_level.txt'):
> @@ -717,6 +718,18 @@ def get_sources(path):
> for row in reader if
> any(row[0].startswith(top)
> for top in
> toplevels))
> continue
> +for top in toplevels:
> +dir_ = os.path.normpath(os.path.join(dist.location,
> + top.rstrip('/')))
> +if not os.path.isdir(dir_):
> +continue
> +for root, dirs, files in os.walk(dir_):
> +for filename in files:
> +if not filename.endswith('.py'):
> +continue
> +filename = os.path.join(root, filename)
> +sources[filename[len(path):].strip(os.sep)
> +.replace(os.sep, '/')] =
> dist
> return sources
>
>
>
>
> BTW, I noticed that Trac debian package has a weird file,
> /usr/lib/python2.7/dist-packages/plugin1/__init__.py.
> I believe that is an issue of the package.
>
> $ dpkg -L trac | grep /plugin1/
> /usr/lib/python2.7/dist-packages/plugin1/__init__.py
>
>
> [1]
> https://svn.python.org/projects/sandbox/trunk/setuptools/doc/formats.txt
> [2]
> https://www.python.org/dev/peps/pep-0376/#one-dist-info-directory-per-installed-distribution
>
>
>
> --
> Jun Omae (大前 潤)
>
Created a ticket for this fix:
https://trac.edgewall.org/ticket/13231
- Ryan
--
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/6bd819d5-50f9-4a58-b81c-fc0baa1c7f36%40googlegroups.com.
Re: [Trac] Re: Help: trac.* components appear as individual plugins on admin page
Hi,
On 2019/11/21 14:10, thos wrote:
Found the problem.
In the Debian distribution, the "Trac-1.2.3.egg-info" directory is missing the
SOURCES.txt file. A RECORD file will also do.
One of them needs to be present for "get_sources" to associate the bundled plug-ins as
part of the same overall "Trac 1.2.3" plugin. From trac.util (__init__.py):
Thanks for the investigating.
I think the Trac debian package should have *.egg-info/SOURCES.txt file.
Searching the SOURCES.txt file in debian packages, several packages have
SOURCES.txt file.
https://packages.debian.org/file:.egg-info/SOURCES.txt
(If *.dist-info structure is used, RECORD file must be included. [2])
However, according to The Internal Structure of Python Eggs [1], it seems that
it is
possible to have no SOURCES.txt file in egg-info structure.
Work around:
diff --git a/trac/util/__init__.py b/trac/util/__init__.py
index 1d3485e09..8808ebf90 100644
--- a/trac/util/__init__.py
+++ b/trac/util/__init__.py
@@ -700,6 +700,7 @@ def get_sources(path):
"""Return a dictionary mapping Python module source paths to the
distributions that contain them.
"""
+path = os.path.normpath(os.path.abspath(path))
sources = {}
for dist in find_distributions(path, only=True):
if not dist.has_metadata('top_level.txt'):
@@ -717,6 +718,18 @@ def get_sources(path):
for row in reader if any(row[0].startswith(top)
for top in toplevels))
continue
+for top in toplevels:
+dir_ = os.path.normpath(os.path.join(dist.location,
+ top.rstrip('/')))
+if not os.path.isdir(dir_):
+continue
+for root, dirs, files in os.walk(dir_):
+for filename in files:
+if not filename.endswith('.py'):
+continue
+filename = os.path.join(root, filename)
+sources[filename[len(path):].strip(os.sep)
+.replace(os.sep, '/')] = dist
return sources
BTW, I noticed that Trac debian package has a weird file,
/usr/lib/python2.7/dist-packages/plugin1/__init__.py.
I believe that is an issue of the package.
$ dpkg -L trac | grep /plugin1/
/usr/lib/python2.7/dist-packages/plugin1/__init__.py
[1] https://svn.python.org/projects/sandbox/trunk/setuptools/doc/formats.txt
[2]
https://www.python.org/dev/peps/pep-0376/#one-dist-info-directory-per-installed-distribution
--
Jun Omae (大前 潤)
--
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/e6a44cbd-f37f-6112-1153-0aff8ed98653%40gmail.com.
[Trac] Re: Help: trac.* components appear as individual plugins on admin page
Found the problem.
In the Debian distribution, the "Trac-1.2.3.egg-info" directory is missing
the SOURCES.txt file. A RECORD file will also do.
One of them needs to be present for "get_sources" to associate the bundled
plug-ins as part of the same overall "Trac 1.2.3" plugin. From trac.util
(__init__.py):
if dist.has_metadata('SOURCES.txt'): # *.egg-info/SOURCES.txt
sources.update((src, dist)
for src in dist.get_metadata_lines('SOURCES.txt')
if any(src.startswith(top) for top in toplevels))
continue
if dist.has_metadata('RECORD'): # *.dist-info/RECORD
reader = csv.reader(StringIO(dist.get_metadata('RECORD')))
sources.update((row[0], dist)
for row in reader if any(row[0].startswith(top)
for top in toplevels))
Since neither of them exists, sources = {}, and "find_distribution()"
inside "get_plugin_info()" assumes the plugin is part of a plain python
file:
if dist is None:
# This is a plain Python source file, not an egg
dist = pkg_resources.Distribution(project_name=name,
version='',
location=module.__file__)
The upshot to all of this is that the Plugin page shows a long list of
plugins:
['trac.notification.prefs', 'trac.search.web-ui',
'trac.versioncontrol.web-ui.browser', 'trac.ticket.notification',
'trac.versioncontrol.web-ui.log', 'trac.resource',
'trac.notification.mail', 'trac.admin.web-ui', 'trac.notification.api',
'trac.attachment', 'trac.cache', 'tracopt.versioncontrol.svn.svn-fs',
'trac.wiki.admin', 'trac.wiki.parser', 'trac.web.session',
'tracopt.perm.authz-policy', 'trac.ticket.admin', 'trac.mimeview.rst',
'trac.ticket.api', 'trac.wiki.web-ui', 'trac.mimeview.api',
'trac.ticket.default-workflow', 'trac.prefs.web-ui', 'trac.admin.api',
'trac.mimeview.pygments', 'trac.mimeview.patch', 'trac.versioncontrol.api',
'trac.db.api', 'trac.web.chrome', 'trac.wiki.interwiki',
'trac.timeline.web-ui', 'trac.about',
'trac.versioncontrol.web-ui.changeset', 'trac.perm', 'trac.ticket.roadmap',
'tracopt.ticket.clone', 'trac.wiki.macros', 'trac.web.main',
'trac.wiki.api', 'TracIniAdminPanel', 'trac.wiki.web-api',
'tracopt.ticket.deleter', 'trac.ticket.query',
'tracopt.ticket.commit-updater', 'trac.wiki.intertrac', 'trac.web.auth',
'trac.db.sqlite-backend', 'trac.admin.console',
'trac.versioncontrol.svn-authz', 'trac.ticket.web-ui',
'tracopt.perm.config-perm-provider', 'trac.ticket.model',
'tracopt.versioncontrol.git.git-fs', 'trac.versioncontrol.admin',
'trac.env', 'trac.ticket.batch', 'trac.config',
'tracopt.versioncontrol.svn.svn-prop', 'trac.ticket.report', 'TracSVNAuthz']
Rather than what it should list:
['TracIniAdminPanel', 'Trac', 'TracSVNAuthz']
On Wednesday, November 20, 2019 at 12:30:27 PM UTC-6, RjOllos wrote:
>
>
>
> On Monday, November 18, 2019 at 3:09:26 PM UTC-8, thos wrote:
>>
>> I will continue to explore what might be different. Could you point me to
>> where in Trac the "Plugin" page is generated? That might give clues as to
>> why the grouping is wrong. Of course the problem could be elsewhere (e.g.
>> plugin registration) and I'm willing to do a little digging. It's just odd
>> that no errors are produced.
>>
>
> Would be great if you could investigate in the code, maybe get to the
> bottom of this. The dictionary for the view is populated here:
>
>
> https://trac.edgewall.org/browser/tags/trac-1.2.3/trac/about.py?marks=71#L69
>
> The plugin info is created here:
> https://trac.edgewall.org/browser/tags/trac-1.2.3/trac/loader.py#L136
>
> Could you provide a listing of the directory structures for the apt-get
> and pip installs, in /usr/lib/python2.7/dist-packages and in
> /usr/local/lib/python2.7/dist-packages, respectively?
>
> Thanks,
> - Ryan
>
--
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/5d462b40-3c0c-4ed9-b853-a28f26665017%40googlegroups.com.
[Trac] Re: Help: trac.* components appear as individual plugins on admin page
On Monday, November 18, 2019 at 3:09:26 PM UTC-8, thos wrote: > > I will continue to explore what might be different. Could you point me to > where in Trac the "Plugin" page is generated? That might give clues as to > why the grouping is wrong. Of course the problem could be elsewhere (e.g. > plugin registration) and I'm willing to do a little digging. It's just odd > that no errors are produced. > Would be great if you could investigate in the code, maybe get to the bottom of this. The dictionary for the view is populated here: https://trac.edgewall.org/browser/tags/trac-1.2.3/trac/about.py?marks=71#L69 The plugin info is created here: https://trac.edgewall.org/browser/tags/trac-1.2.3/trac/loader.py#L136 Could you provide a listing of the directory structures for the apt-get and pip installs, in /usr/lib/python2.7/dist-packages and in /usr/local/lib/python2.7/dist-packages, respectively? Thanks, - Ryan -- 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/f704b9ad-24d7-4662-9c37-fcc41985620c%40googlegroups.com.
Re: [Trac] Re: Help: trac.* components appear as individual plugins on admin page
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.
Re: [Trac] Re: Help: trac.* components appear as individual plugins on admin page
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. 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/f12549df-8afc-4838-9258-fea0cef94c2f%40googlegroups.com.
Re: [Trac] Re: Help: trac.* components appear as individual plugins on admin page
On Tuesday, November 19, 2019 at 1:16:46 AM UTC-8, hasienda wrote: > > Just to throw in a thought: > > Would providing Trac DEB-packages be useful? > I've been a couple of times before near doing some serious Debian > developer work but never did the final step. > > Recently I've moved to a rather powerful private cluster computing > structure, that would benefit from useful tasks like building packages. > So how do your, Ryan, and others feel about a repository, that could > provide more recent Trac and even development versions via apt rather then > pip & Co.? > > Steffen > > Mit freundlichem Gruß > > Steffen Hoffmann Hi Steffen, Good to hear from you. 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 -- 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/0fc182c2-1a03-4da2-9cff-0ec41ac8a88b%40googlegroups.com.
Re: [Trac] Re: Help: trac.* components appear as individual plugins on admin page
Am 19. November 2019 00:09:25 MEZ schrieb thos : >Ryan, > >I am a long-time Trac user, but new to this group. I appreciate your >attentiveness. > >We are trying to create lightweight containers for multiple Trac/SVN >instances, and having all of the development binaries pulled in by pip >is >undesirable. We also need control over when we upgrade resources. > >One difference is that apt-get puts the python packages in >/usr/lib/python2.7/dist-packages, while pip puts them in >/usr/local/lib/python2.7/dist-packages. (This is from memory so may be >off >a bit.) Also, the --force-reinstall doesn't actually remove the >system-installed packages. > >I will continue to explore what might be different. Could you point me >to >where in Trac the "Plugin" page is generated? That might give clues as >to >why the grouping is wrong. Of course the problem could be elsewhere >(e.g. >plugin registration) and I'm willing to do a little digging. It's just >odd >that no errors are produced. > >Thanks. > >-Tom > >On Monday, November 18, 2019 at 9:37:50 AM UTC-6, RjOllos wrote: >> >> >> >> On Sunday, November 17, 2019 at 10:24:24 PM UTC-8, thos wrote: >>> >>> I have some additional information to provide. In my Dockerfile: >>> >>> FROM debian:buster-slim >>> >>> ENV SITE_DIR /var/www/repos >>> ENV LANG C.UTF-8 >>> >>> RUN apt-get update; apt-get install -y \ >>> apache2 \ >>> libapache2-mod-wsgi \ >>> libapache2-mod-svn \ >>> subversion \ >>> python \ >>> trac \ >>> rsync \ >>> ; \ >>> rm -rf /var/lib/apt/lists/* >>> >>> There seems to be an issue with the package distribution. If I add >pip to >>> the installed packages and use it to force a reinstall of Trac, then >the >>> problem goes away: >>> >>> RUN apt-get update; apt-get install -y \ >>> apache2 \ >>> libapache2-mod-wsgi \ >>> libapache2-mod-svn \ >>> subversion \ >>> python \ >>> * python**-pip \* >>> trac \ >>> rsync \ >>> ; \ >>> rm -rf /var/lib/apt/lists/* ; \ >>> >>> * pip install --force-reinstall Trac==1.2.3* >>> >>> The problem with this solution is that python-pip carries a lot of >>> baggage with it (compilers, developer libraries, etc.) >>> >>> Perhaps there is a missing dependency in the trac.deb package? >>> >> >> I've seen the behavior during development and reinstall has always >fixed >> the issue, as you've noted. I'm unsure about the cause. >> >> Maybe a diff of the files installed by apt-get vs pip would provide a >clue? >> >> Another advantage of installing with pip is that you can get the >latest >> Trac, 1.2.5 or 1.4.0, rather than relying on the Debian package >managers to >> update the distribution. >> >> - Ryan >> > >-- >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/e702bc84-b634-4459-af0d-94c954ae066d%40googlegroups.com. Just to throw in a thought: Would providing Trac DEB-packages be useful? I've been a couple of times before near doing some serious Debian developer work but never did the final step. Recently I've moved to a rather powerful private cluster computing structure, that would benefit from useful tasks like building packages. So how do your, Ryan, and others feel about a repository, that could provide more recent Trac and even development versions via apt rather then pip & Co.? Steffen Mit freundlichem Gruß Steffen Hoffmann -- 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/003E17EE-5D0A-4772-8206-A96E10190591%40web.de.
[Trac] Re: Help: trac.* components appear as individual plugins on admin page
Ryan, I am a long-time Trac user, but new to this group. I appreciate your attentiveness. We are trying to create lightweight containers for multiple Trac/SVN instances, and having all of the development binaries pulled in by pip is undesirable. We also need control over when we upgrade resources. One difference is that apt-get puts the python packages in /usr/lib/python2.7/dist-packages, while pip puts them in /usr/local/lib/python2.7/dist-packages. (This is from memory so may be off a bit.) Also, the --force-reinstall doesn't actually remove the system-installed packages. I will continue to explore what might be different. Could you point me to where in Trac the "Plugin" page is generated? That might give clues as to why the grouping is wrong. Of course the problem could be elsewhere (e.g. plugin registration) and I'm willing to do a little digging. It's just odd that no errors are produced. Thanks. -Tom On Monday, November 18, 2019 at 9:37:50 AM UTC-6, RjOllos wrote: > > > > On Sunday, November 17, 2019 at 10:24:24 PM UTC-8, thos wrote: >> >> I have some additional information to provide. In my Dockerfile: >> >> FROM debian:buster-slim >> >> ENV SITE_DIR /var/www/repos >> ENV LANG C.UTF-8 >> >> RUN apt-get update; apt-get install -y \ >> apache2 \ >> libapache2-mod-wsgi \ >> libapache2-mod-svn \ >> subversion \ >> python \ >> trac \ >> rsync \ >> ; \ >> rm -rf /var/lib/apt/lists/* >> >> There seems to be an issue with the package distribution. If I add pip to >> the installed packages and use it to force a reinstall of Trac, then the >> problem goes away: >> >> RUN apt-get update; apt-get install -y \ >> apache2 \ >> libapache2-mod-wsgi \ >> libapache2-mod-svn \ >> subversion \ >> python \ >> * python**-pip \* >> trac \ >> rsync \ >> ; \ >> rm -rf /var/lib/apt/lists/* ; \ >> >> * pip install --force-reinstall Trac==1.2.3* >> >> The problem with this solution is that python-pip carries a lot of >> baggage with it (compilers, developer libraries, etc.) >> >> Perhaps there is a missing dependency in the trac.deb package? >> > > I've seen the behavior during development and reinstall has always fixed > the issue, as you've noted. I'm unsure about the cause. > > Maybe a diff of the files installed by apt-get vs pip would provide a clue? > > Another advantage of installing with pip is that you can get the latest > Trac, 1.2.5 or 1.4.0, rather than relying on the Debian package managers to > update the distribution. > > - Ryan > -- 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/e702bc84-b634-4459-af0d-94c954ae066d%40googlegroups.com.
[Trac] Re: Help: trac.* components appear as individual plugins on admin page
On Sunday, November 17, 2019 at 10:24:24 PM UTC-8, thos wrote: > > I have some additional information to provide. In my Dockerfile: > > FROM debian:buster-slim > > ENV SITE_DIR /var/www/repos > ENV LANG C.UTF-8 > > RUN apt-get update; apt-get install -y \ > apache2 \ > libapache2-mod-wsgi \ > libapache2-mod-svn \ > subversion \ > python \ > trac \ > rsync \ > ; \ > rm -rf /var/lib/apt/lists/* > > There seems to be an issue with the package distribution. If I add pip to > the installed packages and use it to force a reinstall of Trac, then the > problem goes away: > > RUN apt-get update; apt-get install -y \ > apache2 \ > libapache2-mod-wsgi \ > libapache2-mod-svn \ > subversion \ > python \ > * python**-pip \* > trac \ > rsync \ > ; \ > rm -rf /var/lib/apt/lists/* ; \ > > * pip install --force-reinstall Trac==1.2.3* > > The problem with this solution is that python-pip carries a lot of baggage > with it (compilers, developer libraries, etc.) > > Perhaps there is a missing dependency in the trac.deb package? > I've seen the behavior during development and reinstall has always fixed the issue, as you've noted. I'm unsure about the cause. Maybe a diff of the files installed by apt-get vs pip would provide a clue? Another advantage of installing with pip is that you can get the latest Trac, 1.2.5 or 1.4.0, rather than relying on the Debian package managers to update the distribution. - Ryan -- 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/2e8d73f4-5742-48b5-9eb5-39637e0fa702%40googlegroups.com.
[Trac] Re: Help: trac.* components appear as individual plugins on admin page
I have some additional information to provide. In my Dockerfile: FROM debian:buster-slim ENV SITE_DIR /var/www/repos ENV LANG C.UTF-8 RUN apt-get update; apt-get install -y \ apache2 \ libapache2-mod-wsgi \ libapache2-mod-svn \ subversion \ python \ trac \ rsync \ ; \ rm -rf /var/lib/apt/lists/* There seems to be an issue with the package distribution. If I add pip to the installed packages and use it to force a reinstall of Trac, then the problem goes away: RUN apt-get update; apt-get install -y \ apache2 \ libapache2-mod-wsgi \ libapache2-mod-svn \ subversion \ python \ * python**-pip \* trac \ rsync \ ; \ rm -rf /var/lib/apt/lists/* ; \ * pip install --force-reinstall Trac==1.2.3* The problem with this solution is that python-pip carries a lot of baggage with it (compilers, developer libraries, etc.) Perhaps there is a missing dependency in the trac.deb package? -- 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/38ce0d30-9a8c-4962-8a5b-876ec2c7a789%40googlegroups.com.
