[Trac] changeset message in trac.log

[Roger Oberholtzer]

I see that when the post-commit hook in svn runs after a checkin, the
Trac log contains this:

2018-01-16 15:53:39,496 Trac[api] WARNING: Exception caught while
"changeset_modified"
Traceback (most recent call last):
  File "build/bdist.linux-x86_64/egg/tracbacklink/api.py", line 290, in _invoke
return f(*args, **kwargs)
  File "build/bdist.linux-x86_64/egg/tracbacklink/api.py", line 381,
in _changeset_modified
self._resource_deleted('changeset', rev, 'repository',
UnboundLocalError: local variable 'rev' referenced before assignment

I do not see any functionality issue. The changeset shows up in the
timeline. But the message is curious.

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

Re: [Trac] Re: Code Comment messages

[Roger Oberholtzer]

On Tue, Jan 16, 2018 at 5:46 PM, RjOllos  wrote:

>> I don't know what to be looking for in the log.
>
> I would look for the error "Failure sending notification":
> https://github.com/trac-hacks/trac-code-comments-plugin/blob/master/code_comments/notification.py#L109

I do not see that in the log. I limited my search to 'Failure'.

Also see a different CodeComments error. When I click on a comment, I get this:

2018-01-16 15:36:48,289 Trac[main] WARNING: [10.2.10.41] HTTPNotFound:
404 Invalid Changeset Number (No changeset 5031 in the repository),
, referrer
'http://sto-opq-src.scc.se/systems/code-comments'

The /changeset/5031 part looks suspicious. I have a number of svn
repositories defined, and I would expect the changesset to be more
like /changeset/5031/rsoft_library. It seems that it is missing the
repo name.

> The plugin hasn't been modified for the Trac 1.2 notification API changes,
> but should still work because of the legacy support in Trac 1.2. The plugin
> also doesn't have support for AnnouncerPlugin.

I really liked the AnnouncerPlugin. But I have not been using it in
recent Trac versions because so many things did not support it. If I
had to list any Trac feature regression over the years, it has been
the notification system. I know that there has been lots of work in
Trac related to this. But, for me at least, figuring out how best to
use this has been less than obvious. But that's a different topic.


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

Re: [Trac] Re: Merging two Trac instances?

[Ryan Ollos]

On Tue, Jan 16, 2018 at 2:06 PM, W. Martin Borgert 
wrote:

> > * Wiki is simple if there are no page name collisions. You can just
> > export/import using TracAdmin. However, you can also do this by dump/load
> > of the wiki table, and since you have to handle a number of other tables,
> > that is the way to go.
>
> Will export/import include history? If not, I'll go for dump/load.
> I will check name collisions before and do renames if necessary.
>

That's a good point. The trac-admin export will not include history, so you
probably want to use a database dump/load.

You'll also need to move attachments, contained in the environment "files"
directory.

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

Re: [Trac] Re: Merging two Trac instances?

[W. Martin Borgert]

Many thanks for your quick reply!

On 2018-01-16 13:14, RjOllos wrote:
> * Git repository is very simple: Just add the Git repository to the 
> configuration and resync if you have a cached repository type.

Yes, that's what I imagined.

> * Wiki is simple if there are no page name collisions. You can just 
> export/import using TracAdmin. However, you can also do this by dump/load 
> of the wiki table, and since you have to handle a number of other tables, 
> that is the way to go.

Will export/import include history? If not, I'll go for dump/load.
I will check name collisions before and do renames if necessary.

> * Milestones are stored in the database, so you can do a database dump/load 
> of the table, and it will go smooth assuming there are no naming collisions

OK, renames will be necessary anyway for usability.

> * You can dump and reload tickets from the database, but the ticket 
> numbering will change, assuming the ticket numbering of both system started 
> at 1. You could dump the ticket table, change the numbering by an offset 
> and load into the new system. You'll need to modify the attachments, 
> ticket_custom and the ticket_change tables as well, to account for the new 
> ticket ids.

Sounds like the fun part :~)

> * There are some other tables you should be concerned with, like Versions, 
> Priorities ... and other associated with the ticket system. Also, the 
> permissions table. Here is the list of tables:
> https://trac.edgewall.org/wiki/TracDev/DatabaseSchema

This is very helpful!

>  * You can ignore: auth_cookie, cache, node_change, revision. As mentioned, 
> I'd also ignore the repository table and just add the new repository 
> manually.

Yes, there are only few repositories anyway.

> * Users - depends on the authentication mechanism. It might just be a 
> matter of merging htpasswd or htdigest files.

Most users have access to both systems anyway. I'll probably just add
the missing ones manually.

> I'd start with a backup of both systems and start working on a script. Feel 
> free to post here for advice on the script as it progresses. If you refine 
> the script it could be posted as a script on trac-hacks.org, so happy to 
> help you get it refined.

This sounds like the way to go. 

> The trac-admin hotcopy utility can be used to dump the database on the 
> system you are migrating away from.
> 
> Which Trac version and which database type? Do you have plugins installed?

1.2 and PostgreSQL 9.6. There are some plugins, but IIRC, they are all
purely UI related. No tables involved.

Thanks again for the help and all the specific hints!

Cheers

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

[Trac] Re: Merging two Trac instances?

[RjOllos]

On Tuesday, January 16, 2018 at 8:28:57 AM UTC-8, W. Martin Borgert wrote:
>
> Hi, 
>
> I like to Trac instances. Both instances have tickets, wiki, and git 
> repos. 
> I'm using Trac 1.2 with PostgreSQL on Debian stable. 
> I came across 
> https://reinout.vanrees.org/weblog/2009/05/28/merging-trac.html, 
> but it does not talk about tickets, users, milestones, etc. 
> Does anybody know of a more complete recipe? 
>
> TIA! 
>

* Git repository is very simple: Just add the Git repository to the 
configuration and resync if you have a cached repository type.
* Wiki is simple if there are no page name collisions. You can just 
export/import using TracAdmin. However, you can also do this by dump/load 
of the wiki table, and since you have to handle a number of other tables, 
that is the way to go.
* Milestones are stored in the database, so you can do a database dump/load 
of the table, and it will go smooth assuming there are no naming collisions
* You can dump and reload tickets from the database, but the ticket 
numbering will change, assuming the ticket numbering of both system started 
at 1. You could dump the ticket table, change the numbering by an offset 
and load into the new system. You'll need to modify the attachments, 
ticket_custom and the ticket_change tables as well, to account for the new 
ticket ids.
* There are some other tables you should be concerned with, like Versions, 
Priorities ... and other associated with the ticket system. Also, the 
permissions table. Here is the list of tables:
https://trac.edgewall.org/wiki/TracDev/DatabaseSchema
 * You can ignore: auth_cookie, cache, node_change, revision. As mentioned, 
I'd also ignore the repository table and just add the new repository 
manually.
* Users - depends on the authentication mechanism. It might just be a 
matter of merging htpasswd or htdigest files.

I'd start with a backup of both systems and start working on a script. Feel 
free to post here for advice on the script as it progresses. If you refine 
the script it could be posted as a script on trac-hacks.org, so happy to 
help you get it refined.

The trac-admin hotcopy utility can be used to dump the database on the 
system you are migrating away from.

Which Trac version and which database type? Do you have plugins installed?

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

[Trac] Re: No handler matched request to /{ at 0x0458E0F0>

[RjOllos]

On Tuesday, January 16, 2018 at 8:54:58 AM UTC-8, Shad wrote:
>
> Hi,
>
> I tried editing the ticket.html file of my TRAC installation with the 
> following:
>
> 
>
> ...
> ...
> ...
> 
>   https://localhost:8000/project1/wiki/example};>example
> 
>
> I did this manipulation because I wanted to add a link on the ticket page. 
> Thus I created a page in wiki (by name example) and tried adding a 
> reference in the ticket page.
>
> But it gave me the following error:
> No handler matched request to /{ at 0x0458E0F0>
>
> What is that am missing out? Any help is much appreciated.
>
> Thanking you in advance,
>
> Regards, 
> shad
>

You shouldn't have curly brackets around the URL. Also, you can use a 
relative path.


  example
 

You should add customizations through a plugin or site.html. By editing a 
template, you'll have to rebase your changes on ticket.html every time you 
update Trac. Discussed more in:

https://trac.edgewall.org/wiki/TracInterfaceCustomization#SiteAppearance
https://trac.edgewall.org/wiki/TracInterfaceCustomization#ProjectTemplates

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

[Trac] No handler matched request to /{ at 0x0458E0F0>

[Shad]

Hi,

I tried editing the ticket.html file of my TRAC installation with the 
following:



...
...
...

  https://localhost:8000/project1/wiki/example};>example


I did this manipulation because I wanted to add a link on the ticket page. 
Thus I created a page in wiki (by name example) and tried adding a 
reference in the ticket page.

But it gave me the following error:
No handler matched request to /{ at 0x0458E0F0>

What is that am missing out? Any help is much appreciated.

Thanking you in advance,

Regards, 
shad

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

Re: [Trac] TicketTemplate plugin

[Shad]

Ok, thank you for your reply.

Regards,
Shad

On Monday, January 15, 2018 at 5:41:16 PM UTC+1, RjOllos wrote:
>
>
>
> On Mon, Jan 15, 2018 at 5:30 AM, Shad  
> wrote:
>
>> Hi 
>>
>> I have recently installed ticket template plugin into my TRAC 
>> installation.
>>
>> It works perfectly. But one thing I noticed that is when ever I create my 
>> own template or even modify the existing one, the text doesnt translate 
>> itself when the language in the preferences is changed.
>>
>> I.e.; If I write the field names in the description tab in english (For 
>> example Summary: Deatails etc. ) and now if I change the language in the 
>> preferences from english to french, it does not translate the fields within 
>> the description section instead it still reamins in english.
>>
>> Is there something that I am missing out?
>>
>> Any help is much appreciated.
>>
>> Regards,
>> Shad
>>
>
> Only static strings in the HTML/JS/Python code are translated by the 
> mechanism built into Trac. TracTicketTemplate plugin doesn't have a 
> mechanism to translate your template, or any words/phrases in the template.
>
> - 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 post to this group, send email to trac-users@googlegroups.com.
Visit this group at https://groups.google.com/group/trac-users.
For more options, visit https://groups.google.com/d/optout.

Re: [Trac] Re: Code Comment messages

[RjOllos]

On Monday, January 15, 2018 at 12:10:31 AM UTC-8, Roger Oberholtzer wrote:
>
> On Fri, Jan 12, 2018 at 8:27 PM, RjOllos  wrote: 
> > 
> > 
> > On Friday, January 12, 2018 at 2:20:36 AM UTC-8, Roger Oberholtzer 
> wrote: 
> >> 
> >> Have I perhaps missed something in the CodeComment plugin: When a 
> >> comment is added, there is no notification (e.g., e-mail) or entry in 
> >> the timeline. Should there be? 
> >> 
> >> -- 
> >> Roger Oberholtzer 
> > 
> > 
> > This plugin?: 
> > https://github.com/trac-hacks/trac-code-comments-plugin 
>
> That's the one. 
>
> > It should send notifications. If not, I would start by checking the 
> logs. 
> > There is a [code_comments] notify_self option that can be either true or 
> > false. 
>
> I have this in my ini file: 
>
> code_comments.api.codecommentsystem = enabled 
> code_comments.comment_macro.codecommentlinkmacro = enabled 
> code_comments.db.codecommentssetup = enabled 
> code_comments.notification.codecommentchangelistener = enabled 
> code_comments.subscription.subscriptionadmin = disabled 
> code_comments.subscription.subscriptionlisteners = disabled 
> code_comments.subscription.subscriptionmodule = disabled 
> code_comments.ticket_event_listener.updateticketcodecomments = enabled 
> code_comments.web.bundlecommentsredirect = enabled 
> code_comments.web.codecomments = enabled 
> code_comments.web.commentsrest = enabled 
> code_comments.web.deletecommentform = enabled 
> code_comments.web.jsdataforrequests = enabled 
> code_comments.web.listcomments = enabled 
> code_comments.web.mainnavigation = enabled 
> code_comments.web.wikipreview = enabled 
>
> Is there more that can be configured? 
>
> I don't know what to be looking for in the log. 
>

I would look for the error "Failure sending notification":
https://github.com/trac-hacks/trac-code-comments-plugin/blob/master/code_comments/notification.py#L109

The plugin hasn't been modified for the Trac 1.2 notification API changes, 
but should still work because of the legacy support in Trac 1.2. The plugin 
also doesn't have support for AnnouncerPlugin.

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

[Trac] Merging two Trac instances?

[W. Martin Borgert]

Hi,

I like to Trac instances. Both instances have tickets, wiki, and git repos.
I'm using Trac 1.2 with PostgreSQL on Debian stable.
I came across https://reinout.vanrees.org/weblog/2009/05/28/merging-trac.html,
but it does not talk about tickets, users, milestones, etc.
Does anybody know of a more complete recipe?

TIA!

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