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/ap
I am migrating a long-standing Trac environment from macOS to a Docker
container. Both configurations use Trac 1.2.3, and after careful migration,
everything seems to be working.
However, the Plugins page of the Admin tab shows all of the different
trac.* components as separate plugins rather t
Lack of notification for deletion, addition and renaming of components is
fine (in fact, this makes sense to me). But more importantly I now feel
more confident that deleting a component as admin, won't adversely affect
existing tickets!
Thank you for your comprehensive research and reply!
Best
On Thursday, November 14, 2019 at 4:06:07 AM UTC-8, Tasos Papastylianou
wrote:
>
> Thank you Ryan!
> The Trac version is 1.2.2
>
> T.
>
For the component field, the ticket will continue to have the deleted entry
and it will be inserted as an option in the select list. For example, I
deleted "
On Thursday, November 14, 2019 at 11:42:22 PM UTC-8, Mo wrote:
>
> Thank you very much.
> I think it's a good idea to use such a requirements_file, eventhough I
> still think it's part of a package manager to populate such a file after a
> '*pip
> install*', just like every rpm, apt, yum or po
On Thursday, November 14, 2019 at 2:44:56 AM UTC-8, Jun Omae wrote:
>
> On Thu, Nov 14, 2019 at 7:31 PM Mo wrote:
> > 2019-11-14 11:25:31,252 Trac[env] ERROR: Component componentdependencies.componentdependency.ComponentDependencyPlugin> failed
> with
>
> That's a ComponentDependencyPlugin i
