On Tuesday, February 5, 2019 at 9:27:27 AM UTC-8, Jun Omae wrote:
>
> On Wed, Feb 6, 2019 at 1:12 AM Clemens Feige <[email protected]> 
> wrote: 
> > 
> > Please find attached the log-file and conf-files, plus my SVN 
> > hook-scripts. In the log the SVN submit was at line 141 (time stamp 
> > 2019-02-05 16:05). 
> > 
> > Concerning explicit synchronization, please note that it basically works 
> > on my site (except the TracBackLinkPlugin sync). I mean that right after 
> > the SVN commit I can see the SVN change-set in the TRAC timeline. This 
> > is why I am assuming that the explicit synchronization is OK. 
> > 
> > I investigated that after the SVN commit the TRAC SQLite-DB has a 
> > corresponding line added in the "revision" table. But nothing is added 
> > to the "backlink" table. 
> > 
> > It might be worth to note that we run our SVN over SSH tunnels. This 
> > means that "trac-admin" will be called (via SVN hook) as the normal user 
> > (not the "www-data" user for the Apache webserver). 
> > 
> > In an experiment running the following command did the sync for 
> > TracBackLinkPlugin, but running as ordinary user did not: 
> > 
> >    trac-admin /data/trac/repos/test/ changeset added "(default)" 157 
> > 
> > Might be a permission problem ... but I cannot find the problem. 
>
> When "trac-admin $ENV changeset added" is executed, the message is 
> logged in trac.log like this. 
>
> 2018-12-12 22:18:11,387 DEBUG: Event changeset_added on repository 
> 'reponame' for changesets (u'1170',) 
>
> However, the message is not existent in your trac.log. 
>
>
> 2019-02-05 16:05:22,706 Trac[api] DEBUG: Trying to render HTML preview 
> using PygmentsRenderer [no annotations] 
> NOW COMES THE SVN COMMIT 
> <==== If your configuration is corrected, the message should be logged 
> here. Please post trac.log with no changes. 
> SVN COMMIT DONE 
> 2019-02-05 16:10:22,178 Trac[main] DEBUG: Dispatching 
> <RequestWithSession "GET '/ticket/4'"> 
>
>
> -- 
> Jun Omae <[email protected]> (大前 潤) 
>


I didn't look too closely at the configuration files yet, but noticed that 
there seems to be a blatant error in the documentation (unless I'm 
completely missing something this morning). Corrected here:
https://trac.edgewall.org/wiki/TracRepositoryAdmin?action=diff&version=51
I didn't look closely at the wiki history, but I probably added that 
section and mixed up the logic.

- 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 [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/trac-users.
For more options, visit https://groups.google.com/d/optout.

Reply via email to