[Trac] Re: ticket types and custom fields

[Noah Kantrowitz]

rupert thurner wrote:

(1) we find it very handy to work with links prefilling some fields,
where also the type can be specified. and (2) if the user changes the
type, why not reloading the ticket-ui?


Because HTML has no provision for this. See earlier comment about JS.

--Noah



signature.asc
Description: OpenPGP digital signature

[Trac] Re: ticket types and custom fields

[rupert thurner]

(1) we find it very handy to work with links prefilling some fields,
where also the type can be specified. and (2) if the user changes the
type, why not reloading the ticket-ui?

On Jun 3, 1:44 am, "Noah Kantrowitz" <[EMAIL PROTECTED]> wrote:
> > -Original Message-
> > From: trac-users@googlegroups.com [mailto:[EMAIL PROTECTED]
> > On Behalf Of [EMAIL PROTECTED]
> > Sent: Monday, June 02, 2008 4:21 PM
> > To: trac-users@googlegroups.com
> > Subject: [Trac] ticket types and custom fields
>
> > Hello,
>
> > considering all the plugins that try to hide, extend, modify or play
> > with the custom properties of a ticket, and also reading through the
> > resent discussion about the trac core I have a simple question to
> > understand a design decision.
> > If I remember correctly trac started with only one ticket type. later
> > this was extended to distinguish between all different types with all
> > the helper plugins showing up to manage the custom fields. While ticket
> > types are a good idea, I find it rather interesting, that I have to
> > hide
> > fields in order to get other, completely unrelated types. Why don't you
> > expose a real basic API to construct different tickets types where
> > every
> > type will have to add fileds in order to be useful. The Ticketing
> > system
>
> Huge fundamental problem: At the time the ticket UI is loaded, we have no
> idea what type the ticket is. Either you need to put a screen before the
> main ticket UI where you select a type, or you do the whole thing
> client-side with JavaScript. Trac maintains a policy of not requiring
> JavaScript for actual functionality (just makes existing functions faster),
> so #2 is right out. This leaves #1, which would be annoying as all get out.
> If you have another option please share it though.
>
> --Noah- Hide quoted text -
>
> - Show quoted text -
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "Trac 
Users" group.
To post to this group, send email to trac-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/trac-users?hl=en
-~--~~~~--~~--~--~---

[Trac] Re: Multi project

[Noah Kantrowitz]

Macbane wrote:

Hi,

I have read some of the proposals, for multi project trac. How do
people feel about it, because trac is fine for a small project but
breaks down when you get to a stage where you are working on many
projects at once. Is trac going to support those features or stay the
way it is? How do users feel about it.


The very brief overview is that there are some plugins and 3rd-party 
tools around now that do "heavyweight" multi-project support. This means 
each project gets its own Environment. The flavor it looks like Trac 
core will adopt is a much lighter-weight system where most of the tables 
just get an extra "project" column, and the UI is restructured a bit. 
Both options have their ups and downs, and I think both will exist in 
parallel for a while at least.


--Noah



signature.asc
Description: OpenPGP digital signature

[Trac] Multi project

[Macbane]

Hi,

I have read some of the proposals, for multi project trac. How do
people feel about it, because trac is fine for a small project but
breaks down when you get to a stage where you are working on many
projects at once. Is trac going to support those features or stay the
way it is? How do users feel about it.

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "Trac 
Users" group.
To post to this group, send email to trac-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/trac-users?hl=en
-~--~~~~--~~--~--~---

[Trac] Re: ticket types and custom fields

[Noah Kantrowitz]

> -Original Message-
> From: trac-users@googlegroups.com [mailto:[EMAIL PROTECTED]
> On Behalf Of [EMAIL PROTECTED]
> Sent: Monday, June 02, 2008 4:21 PM
> To: trac-users@googlegroups.com
> Subject: [Trac] ticket types and custom fields
> 
> 
> Hello,
> 
> considering all the plugins that try to hide, extend, modify or play
> with the custom properties of a ticket, and also reading through the
> resent discussion about the trac core I have a simple question to
> understand a design decision.
> If I remember correctly trac started with only one ticket type. later
> this was extended to distinguish between all different types with all
> the helper plugins showing up to manage the custom fields. While ticket
> types are a good idea, I find it rather interesting, that I have to
> hide
> fields in order to get other, completely unrelated types. Why don't you
> expose a real basic API to construct different tickets types where
> every
> type will have to add fileds in order to be useful. The Ticketing
> system

Huge fundamental problem: At the time the ticket UI is loaded, we have no
idea what type the ticket is. Either you need to put a screen before the
main ticket UI where you select a type, or you do the whole thing
client-side with JavaScript. Trac maintains a policy of not requiring
JavaScript for actual functionality (just makes existing functions faster),
so #2 is right out. This leaves #1, which would be annoying as all get out.
If you have another option please share it though.

--Noah


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "Trac 
Users" group.
To post to this group, send email to trac-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/trac-users?hl=en
-~--~~~~--~~--~--~---

[Trac] ticket types and custom fields

[trac]

Hello,

considering all the plugins that try to hide, extend, modify or play 
with the custom properties of a ticket, and also reading through the 
resent discussion about the trac core I have a simple question to 
understand a design decision.
If I remember correctly trac started with only one ticket type. later 
this was extended to distinguish between all different types with all 
the helper plugins showing up to manage the custom fields. While ticket 
types are a good idea, I find it rather interesting, that I have to hide 
fields in order to get other, completely unrelated types. Why don't you 
expose a real basic API to construct different tickets types where every 
type will have to add fileds in order to be useful. The Ticketing system 
itself would be one of the users of this API, adding the current set of 
fields. If this is a performance issue [1], why not having different 
tables for every different configured ticket type. You could reuse the 
current ticket page UI as a generic UI for every ticket type, but 
different plugins could override these with a different custom UI. The 
only problem with this approach is, that you can not change from one 
type to another. The ticketing system may still have a custom field 
"type" to distinguish between a bug and an enhancement. But other types, 
like requirements, tasks, tests, inventory and so on are generally not 
changed from on type into another. In these rare cases, one could still 
simply refer/reference to a new ticket of different type. I can't see a 
reason, why I should change unrelated types, esp. since we have the 
workflow.

The ticket numbering is the same as the subversion revision. It is a 
number nothing else and it should be unique between all ticket types 
simply for the ease of use.

 From what I can see, and also use in my setup, trac is exetended in 
many ways to include completely different types in one setup, and the 
common sence for all types in my setup is, that the have a number, a 
subject a description, the time/author fields and history of changes. 
Nothing else. Every other field, like resolution, severity, version 
milestone and so on is specific to one of multiple types.

I'm not a real python / trac developer. I'm simply trying to fit trac 
into our process and I often come across this question. If you think 
about core features of trac, make the ability to manage types and 
tickets, crossreferencing between tickets (e.g duplicates, and 
references), workflows and permissions the core feature. The ticketing 
itself is already a module build upon the core.

There are a lot of discussions about new fields. In this minimalistic 
approach, trac does not enforce a set of fields, even not the so called 
standard fields. It will mange as many fileds the user will configure.

Sorry if this is already common sence between the developers. I did not 
follow every discussion on the list due to lack of time, but I was 
thinking about a new ticket type today, and hit that "hide" fields issue 
again.

Best regards
Dirk

[1] I can remember a previous discussion, about the database design for 
custom ticket fields and performance issues.

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "Trac 
Users" group.
To post to this group, send email to trac-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/trac-users?hl=en
-~--~~~~--~~--~--~---

[Trac] Re: tracLinks suggestion...

[trac]

Hi,

I'm having similar requirements. I'm looking into a XML based storage 
under source control and then a plugin to grab and format the 
information from there. Something similar is already done in the 
TestCaseManagementPlugin [1], but there the information of the stored 
XML is used for automatic ticket creation and reporting.

I have not yet thought about a linking or automated WIKI page creation 
from the source, esp. how to distinguish between the different branched 
versions of the requierements. With the XML information at hand, one 
could also generate a requirements traceability matrix and a lot of 
other nice things. But this is only in my head. I have no code to show.

The reason for keeping the requirements with the software under source 
control, is simply that requirements change. Except bug fixing, every 
version of the software exposes a different set of requirements since 
every checkin will extend or modify the current set of requirements. 
Since you can not easily create wiki pages that follow your software 
versions (e.g. see the discussion about the trac documentation itself) 
it is necessary to store the information under source control.

Best regards
Dirk

[1] http://trac-hacks.org/wiki/TestCaseManagementPlugin

[EMAIL PROTECTED] schrieb:
> On Jun 2, 5:02 pm, "Erik Bray" <[EMAIL PROTECTED]> wrote:
>   
>> I don't know about you, but I just keep all my requirements in the
>> wiki itself.  Usually as a bullet list, so I suppose I can't link to a
>> specific requirement.  But I can see, "See requirement 123" and link
>> to the appropriate page.  I'm not saying that necessarily suits your
>> needs, but it sounds to me like you're getting over-complicated.
>> 
>
> Wish it were that simple.  I can't actually put the requirements into
> the wiki.  I have to export them from a controlled location, this
> "solution" I am after is post export.  I suppose I could find a way to
> export to wiki mark-up. some how.  I want the wiki-version of the
> requirement to be up to date with the source control version, which is
> generated auto-magically by the requirements tools.  Seems to me the
> pinch point is that export, I should transform to wiki markup at that
> point, update/check into source control, and #include it in an
> appropriate wiki page.
>
> I will let you know.
> >
>
>
>   


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "Trac 
Users" group.
To post to this group, send email to trac-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/trac-users?hl=en
-~--~~~~--~~--~--~---

[Trac] Re: tracLinks suggestion...

[Noah Kantrowitz]

> -Original Message-
> From: trac-users@googlegroups.com [mailto:[EMAIL PROTECTED]
> On Behalf Of [EMAIL PROTECTED]
> Sent: Monday, June 02, 2008 3:20 PM
> To: Trac Users
> Subject: [Trac] Re: tracLinks suggestion...
> 
> 
> On Jun 2, 5:02 pm, "Erik Bray" <[EMAIL PROTECTED]> wrote:
> > I don't know about you, but I just keep all my requirements in the
> > wiki itself.  Usually as a bullet list, so I suppose I can't link to
> a
> > specific requirement.  But I can see, "See requirement 123" and link
> > to the appropriate page.  I'm not saying that necessarily suits your
> > needs, but it sounds to me like you're getting over-complicated.
> 
> Wish it were that simple.  I can't actually put the requirements into
> the wiki.  I have to export them from a controlled location, this
> "solution" I am after is post export.  I suppose I could find a way to
> export to wiki mark-up. some how.  I want the wiki-version of the
> requirement to be up to date with the source control version, which is
> generated auto-magically by the requirements tools.  Seems to me the
> pinch point is that export, I should transform to wiki markup at that
> point, update/check into source control, and #include it in an
> appropriate wiki page.
> 

What format does it use? The Include macro uses the mimeview renderer
framework, so if you invent a MIME type and write something to convert its
format to HTML, you are set. Just put anchors in the generated HTML and you
can do things like wiki:Requirements#R123.

--Noah



--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "Trac 
Users" group.
To post to this group, send email to trac-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/trac-users?hl=en
-~--~~~~--~~--~--~---

[Trac] Re: tracLinks suggestion...

[yoheeb]

On Jun 2, 5:02 pm, "Erik Bray" <[EMAIL PROTECTED]> wrote:
> I don't know about you, but I just keep all my requirements in the
> wiki itself.  Usually as a bullet list, so I suppose I can't link to a
> specific requirement.  But I can see, "See requirement 123" and link
> to the appropriate page.  I'm not saying that necessarily suits your
> needs, but it sounds to me like you're getting over-complicated.

Wish it were that simple.  I can't actually put the requirements into
the wiki.  I have to export them from a controlled location, this
"solution" I am after is post export.  I suppose I could find a way to
export to wiki mark-up. some how.  I want the wiki-version of the
requirement to be up to date with the source control version, which is
generated auto-magically by the requirements tools.  Seems to me the
pinch point is that export, I should transform to wiki markup at that
point, update/check into source control, and #include it in an
appropriate wiki page.

I will let you know.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "Trac 
Users" group.
To post to this group, send email to trac-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/trac-users?hl=en
-~--~~~~--~~--~--~---

[Trac] Re: tracLinks suggestion...

[Erik Bray]

On Mon, Jun 2, 2008 at 4:56 PM,  <[EMAIL PROTECTED]> wrote:
>
> Hi all,
>
> this may be a question for the dev group, but thought I would field it
> here first, since it has both a "approach" and implementation part.
> Sorry for the Length of this post.
>
> I want to link to requirements in the wiki, I see a few ways to do
> this:
>
> put the requirements in source control, as text, and #include them in
> a wiki "requirements" page named for the document.  I can then
> references the requirement in the docuement, and link to the page.
> The disadvantage of this is, I can't link directly to the requirement
> itself, unless:
>  if it is text based, I could technically link to a specific line #,
> or even a range, and highlight it.  The flaw with this of course, is
> if anyone inserts, or deletes a line, it breaks.  This would be
> awesome of someone has a way to manage this issue.  I bet there would
> be a way to script the file on commit, and update the wiki globally
> with a batch replace, just not sure on the reliability.
>
> Next option I thought of, and I don't know about feasibility, or if
> it's just a bad idea.  if I exported my requirements, and imported
> them into the trac database, I could use a query link, and query on
> the field(s) that is unique to the requirement.  This would
> essentially link to a query that always returns exactly one result.
> but then I need to figure out how to actually display the requirement/
> text, in theory could have a link to an image, or of course, links to
> other requirements, or trac items...etc. as well as the text.  plus I
> really want the whole document, just focused on the requirement
> itself.
>
> Another option, just export each requirement to it's own text file,
> named by requirement ID.  put all requirements for a single
> requirement "document" in a directory named for the requirement
> document:
> /trunk/docs/requirements/gui_requirements/1.txt, 2.txt, 3.txt...N.txt
> etc.  They could have reference to the other documents as needed:
>  say, in 2.txt:
>  "to align with the requirement in /trunk/docs/requirements/
> system_requirements/[EMAIL PROTECTED] we shall"  should show up as a link
> in trac, I think, unless I need to preface it with src: which would be
> ok too I guess
>
> Finally, I was thinking, my requirements documents could be text
> based, I could use some magic post commit script on subversion to
> update the file properties to have the line Starting line # for each
> requirement, and dynamically build the line# link mentioned up in the
> first option.  most likely actually generating a "TOC" type page, with
> the line# links that is actually displayed for each requirement
> document.  so, the  would
> just link to the "requirement" document, and reference the identifier
> by NAME, then the TOC page gets shown, user clicks on the requirement
> by NAME, and ends up in the correct line #, even if that number
> changes.
>

I don't know about you, but I just keep all my requirements in the
wiki itself.  Usually as a bullet list, so I suppose I can't link to a
specific requirement.  But I can see, "See requirement 123" and link
to the appropriate page.  I'm not saying that necessarily suits your
needs, but it sounds to me like you're getting over-complicated.

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "Trac 
Users" group.
To post to this group, send email to trac-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/trac-users?hl=en
-~--~~~~--~~--~--~---

[Trac] Re: Mylyn Integration of Custom Workflow Actions

[Chris]

That token error would be "Missing or invalid form token. Do you have
cookies enabled?"
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "Trac 
Users" group.
To post to this group, send email to trac-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/trac-users?hl=en
-~--~~~~--~~--~--~---

[Trac] Mylyn Integration of Custom Workflow Actions

[Chris]

Referencing this old post:
http://groups.google.com/group/trac-users/browse_thread/thread/4a1bbdb8b89f3881/47e9458f5657b557?lnk=gst&q=mylyn#47e9458f5657b557

I have a custom workflow where the actions are not showing. Does
anyone know if this is a Mylyn, Trac, or XMLRPC plugin bug? Any
workarounds besides using the built-in browser? Using the built-in
browser I get a "token" error that states cookies aren't enabled.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "Trac 
Users" group.
To post to this group, send email to trac-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/trac-users?hl=en
-~--~~~~--~~--~--~---

[Trac] Re: Merge wiki pages - not a collision solution

[Jeff Hammel]

On Mon, Jun 02, 2008 at 01:00:48PM -0700, Noah Kantrowitz wrote:
> 
> > -Original Message-
> > From: trac-users@googlegroups.com [mailto:[EMAIL PROTECTED]
> > On Behalf Of Thomas Moschny
> > Sent: Monday, June 02, 2008 9:48 AM
> > To: trac-users@googlegroups.com
> > Subject: [Trac] Re: Merge wiki pages - not a collision solution
> > 
> > 
> > 2008/6/2, Noah Kantrowitz <[EMAIL PROTECTED]>:
> > > Check both into subversion and use that (or git, hg, etc). A wiki is
> > not
> > > designed for that kind of complex document management.
> > 
> > Well, if Trac stored the wiki contents within the repository
> > [1], it could even support such 'complex' tasks. Ikiwiki [2] does
> > that, for example, even in a distributed way.
> > 
> 
> I said quite clearly that this is an option, and that we have opted to not
> do it this way for a number of important reasons. These are detailed in the
> link I gave. If you want a subversion-backed wiki, use a subversion-backed
> wiki, I don't see why this is a problem. Trac doesn't have to fill every
> possible niche ever :P
> 
> --Noah

For what its worth from a first time mailer to this list, I am glad trac does 
not import its wiki pages into an svn repo by default.  For my mileage, this 
would be clunkier (but I'm sure I have different wiki needs than others).

Jeff

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "Trac 
Users" group.
To post to this group, send email to trac-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/trac-users?hl=en
-~--~~~~--~~--~--~---

[Trac] tracLinks suggestion...

[yoheeb]

Hi all,

this may be a question for the dev group, but thought I would field it
here first, since it has both a "approach" and implementation part.
Sorry for the Length of this post.

I want to link to requirements in the wiki, I see a few ways to do
this:

put the requirements in source control, as text, and #include them in
a wiki "requirements" page named for the document.  I can then
references the requirement in the docuement, and link to the page.
The disadvantage of this is, I can't link directly to the requirement
itself, unless:
  if it is text based, I could technically link to a specific line #,
or even a range, and highlight it.  The flaw with this of course, is
if anyone inserts, or deletes a line, it breaks.  This would be
awesome of someone has a way to manage this issue.  I bet there would
be a way to script the file on commit, and update the wiki globally
with a batch replace, just not sure on the reliability.

Next option I thought of, and I don't know about feasibility, or if
it's just a bad idea.  if I exported my requirements, and imported
them into the trac database, I could use a query link, and query on
the field(s) that is unique to the requirement.  This would
essentially link to a query that always returns exactly one result.
but then I need to figure out how to actually display the requirement/
text, in theory could have a link to an image, or of course, links to
other requirements, or trac items...etc. as well as the text.  plus I
really want the whole document, just focused on the requirement
itself.

Another option, just export each requirement to it's own text file,
named by requirement ID.  put all requirements for a single
requirement "document" in a directory named for the requirement
document:
/trunk/docs/requirements/gui_requirements/1.txt, 2.txt, 3.txt...N.txt
etc.  They could have reference to the other documents as needed:
  say, in 2.txt:
 "to align with the requirement in /trunk/docs/requirements/
system_requirements/[EMAIL PROTECTED] we shall"  should show up as a link
in trac, I think, unless I need to preface it with src: which would be
ok too I guess

Finally, I was thinking, my requirements documents could be text
based, I could use some magic post commit script on subversion to
update the file properties to have the line Starting line # for each
requirement, and dynamically build the line# link mentioned up in the
first option.  most likely actually generating a "TOC" type page, with
the line# links that is actually displayed for each requirement
document.  so, the  would
just link to the "requirement" document, and reference the identifier
by NAME, then the TOC page gets shown, user clicks on the requirement
by NAME, and ends up in the correct line #, even if that number
changes.

I think I just answered my own question, but would love some feedback
on this, especially if anyone has done anything like it.

Thanks.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "Trac 
Users" group.
To post to this group, send email to trac-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/trac-users?hl=en
-~--~~~~--~~--~--~---

[Trac] Re: Merge wiki pages - not a collision solution

[Noah Kantrowitz]

> -Original Message-
> From: trac-users@googlegroups.com [mailto:[EMAIL PROTECTED]
> On Behalf Of Thomas Moschny
> Sent: Monday, June 02, 2008 9:48 AM
> To: trac-users@googlegroups.com
> Subject: [Trac] Re: Merge wiki pages - not a collision solution
> 
> 
> 2008/6/2, Noah Kantrowitz <[EMAIL PROTECTED]>:
> > Check both into subversion and use that (or git, hg, etc). A wiki is
> not
> > designed for that kind of complex document management.
> 
> Well, if Trac stored the wiki contents within the repository
> [1], it could even support such 'complex' tasks. Ikiwiki [2] does
> that, for example, even in a distributed way.
> 

I said quite clearly that this is an option, and that we have opted to not
do it this way for a number of important reasons. These are detailed in the
link I gave. If you want a subversion-backed wiki, use a subversion-backed
wiki, I don't see why this is a problem. Trac doesn't have to fill every
possible niche ever :P

--Noah


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "Trac 
Users" group.
To post to this group, send email to trac-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/trac-users?hl=en
-~--~~~~--~~--~--~---

[Trac] Re: Merge wiki pages - not a collision solution

[Thomas Moschny]

2008/6/2, Noah Kantrowitz <[EMAIL PROTECTED]>:
> Check both into subversion and use that (or git, hg, etc). A wiki is not
> designed for that kind of complex document management.

Well, if Trac stored the wiki contents within the repository
[1], it could even support such 'complex' tasks. Ikiwiki [2] does
that, for example, even in a distributed way.

- Thomas

[1] see e.g. http://trac.edgewall.org/wiki/WhySQLite
[2] http://ikiwiki.info/

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "Trac 
Users" group.
To post to this group, send email to trac-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/trac-users?hl=en
-~--~~~~--~~--~--~---

[Trac] Re: Merge wiki pages - not a collision solution

[yoheeb]

On Jun 2, 12:35 pm, "Duany Espindola" <[EMAIL PROTECTED]>
wrote:
> Thank you Noah!
>
> I will do this using svn or "diff and patch" commands.
> I think more people have de same problem that I have. Maybe I make a plug-in
> when I take a vacation.
>
> Att
>
> Duany César (Brazil)


vacation?  I thought that was an urban legend!  Hehe.  Sorry I didn't
fully understand what you were asking, I think I did, but it seem it
was a case of what you were saying, and what you really wanted didn't
come together correctly in my fragmented hard drive :)

I will be using this same strategy in a different context.  I expect
to export controlled documents AS wiki pages, or in reality, to
"include" macro them into paged dedicated to them.  They need to be
versioned, and actually will be versioned in multiple spots...the
source tool, and again in the Subversion repository.  then, yes, the
diff tool works just fine.  Which is really handy when we feature
branch, then decide to bring them back, as these are requirements,
design, and user manual documents.  Good luck.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "Trac 
Users" group.
To post to this group, send email to trac-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/trac-users?hl=en
-~--~~~~--~~--~--~---

[Trac] Re: Merge wiki pages - not a collision solution

[Noah Kantrowitz]

See http://trac-hacks.org/wiki/PrivateTicketsPlugin?format=txt for an
example of how you can do this nicely.

 

--Noah

 

From: trac-users@googlegroups.com [mailto:[EMAIL PROTECTED] On
Behalf Of Duany Espindola
Sent: Monday, June 02, 2008 10:40 AM
To: trac-users@googlegroups.com
Subject: [Trac] Re: Merge wiki pages - not a collision solution

 

Yupy!
That is the solution I´m looking for. hehehe
Thank you!
I should have thought of that before !

Att,

Duany César

On Mon, Jun 2, 2008 at 2:31 PM, Noah Kantrowitz <[EMAIL PROTECTED]> wrote:

No. Again, you are misusing a wiki when you want a version control system.
You can use the Include macro to pull text from the VCS into the wiki if you
still want to show it there as well.

 

--Noah

 

From: trac-users@googlegroups.com [mailto:[EMAIL PROTECTED] On
Behalf Of Duany Espindola
Sent: Monday, June 02, 2008 10:30 AM


To: trac-users@googlegroups.com

Subject: [Trac] Re: Merge wiki pages - not a collision solution

 

Thank you too, but   
I think this solution not works for me because the TRAC wiki pages are
not text files.
For view this pages in text files we need do a export command. 
I want know if a plug-in could do that, something like this: "trac-admin
myEnv wiki merge PageA[1:4]  PageB "

Att,

Duany César

On Mon, Jun 2, 2008 at 1:16 PM, <[EMAIL PROTECTED]> wrote:


On Jun 2, 9:01 am, "Duany Espindola" <[EMAIL PROTECTED]> wrote:
> Thank you, *but* it is not the solution that I'm looking for.
> This tool works for common files, but I need one that works in wiki-pages
> into a TRAC environment.
>
> Someone have another idea ?
> --
> Duany César (Brazil)
>

> On Mon, Jun 2, 2008 at 9:08 AM, Jani Tiainen <[EMAIL PROTECTED]> wrote:
>
> > Duany Espindola kirjoitti:


> > > Hi, everybody!
>
> > > I have bean looking for a solution for two weeks for my problem
and
> > > this forum is my last try.
> > > I had two equal wiki pages: PageA and PageB. So I make changes in
> > > PageA and different changes in PageB. Now I need merge the changes in
> > > PageA in the PageB.
> > > I read a lot things about merge wiki pages in collision case, but
I
> > > don't know how to resolve my problem and I will be happy if anyone
help
> > me.
>

> > There is tool called "diff3" that can help you to merge and make
> > conflicts correctly provided that PageA and PageB do have common
> > preceding version. See for example 
>
> > --
> > Jani Tiainen 

I don't understand how this is not a solution to  your problem.  You
want to merge/diff, use a merge/diff tool.  vimdiff,
winmerge, ...etc.  you just have to point to the actual files of the
wiki pages instead of at the rendered level.  The only other thing I
can think of, is to do one of the following:
 open both files in edit mode in separate brower windows/tabs and:
 visually merged the changes throught the file, or
 export both to plain text, use a diff tool to see the differences,
then manually cut and paste the changes into the wiki edit mode
window(s)

otherwise, I guess I don't fully understand what it is you are trying
to accomplish by the term "merge".

 




-- 
Duany César S. Espindola

 

 




-- 
Duany César S. Espindola


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "Trac 
Users" group.
To post to this group, send email to trac-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/trac-users?hl=en
-~--~~~~--~~--~--~---

[Trac] Re: Merge wiki pages - not a collision solution

[Duany Espindola]

Yupy!
That is the solution I´m looking for. hehehe
Thank you!
I should have thought of that before !

Att,

Duany César

On Mon, Jun 2, 2008 at 2:31 PM, Noah Kantrowitz <[EMAIL PROTECTED]> wrote:

>  No. Again, you are misusing a wiki when you want a version control
> system. You can use the Include macro to pull text from the VCS into the
> wiki if you still want to show it there as well.
>
>
>
> --Noah
>
>
>
> *From:* trac-users@googlegroups.com [mailto:[EMAIL PROTECTED] *On
> Behalf Of *Duany Espindola
> *Sent:* Monday, June 02, 2008 10:30 AM
> *To:* trac-users@googlegroups.com
> *Subject:* [Trac] Re: Merge wiki pages – not a collision solution
>
>
>
> Thank you too, but
> I think this solution not works for me because the TRAC wiki pages are
> not text files.
> For view this pages in text files we need do a export command.
> I want know if a plug-in could do that, something like this: "*trac-admin
> myEnv wiki merge PageA[1:4]  PageB* "
>
> Att,
>
> Duany César
>
> On Mon, Jun 2, 2008 at 1:16 PM, <[EMAIL PROTECTED]> wrote:
>
>
> On Jun 2, 9:01 am, "Duany Espindola" <[EMAIL PROTECTED]> wrote:
> > Thank you, *but* it is not the solution that I'm looking for.
> > This tool works for common files, but I need one that works in wiki-pages
> > into a TRAC environment.
> >
> > Someone have another idea ?
> > --
> > Duany César (Brazil)
> >
>
> > On Mon, Jun 2, 2008 at 9:08 AM, Jani Tiainen <[EMAIL PROTECTED]> wrote:
> >
> > > Duany Espindola kirjoitti:
>
> > > > Hi, everybody!
> >
> > > > I have bean looking for a solution for two weeks for my problem
> and
> > > > this forum is my last try.
> > > > I had two equal wiki pages: PageA and PageB. So I make changes in
> > > > PageA and different changes in PageB. Now I need merge the changes in
> > > > PageA in the PageB.
> > > > I read a lot things about merge wiki pages in collision case, but
> I
> > > > don't know how to resolve my problem and I will be happy if anyone
> help
> > > me.
> >
> > > There is tool called "diff3" that can help you to merge and make
> > > conflicts correctly provided that PageA and PageB do have common
> > > preceding version. See for example  >
> >
> > > --
> > > Jani Tiainen
>
> I don't understand how this is not a solution to  your problem.  You
> want to merge/diff, use a merge/diff tool.  vimdiff,
> winmerge, ...etc.  you just have to point to the actual files of the
> wiki pages instead of at the rendered level.  The only other thing I
> can think of, is to do one of the following:
>  open both files in edit mode in separate brower windows/tabs and:
>  visually merged the changes throught the file, or
>  export both to plain text, use a diff tool to see the differences,
> then manually cut and paste the changes into the wiki edit mode
> window(s)
>
> otherwise, I guess I don't fully understand what it is you are trying
> to accomplish by the term "merge".
>
>
>
>
>
>
> --
> Duany César S. Espindola
>
> >
>


-- 
Duany César S. Espindola

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "Trac 
Users" group.
To post to this group, send email to trac-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/trac-users?hl=en
-~--~~~~--~~--~--~---

[Trac] Re: Merge wiki pages - not a collision solution

[Noah Kantrowitz]

Any time you think "branch/merge" you shouldn't be using a wiki pretty much.
There are some wikis that are based about VCSs, but Trac has shied away from
that for a long list of reasons (see TighterSubversionIntegration). The Trac
project itself is now having problems related to this, and so we are looking
to move docs into Subversion for exactly this reason. Hopefully we will be
able to produce a workflow and UI for this that other projects can use as
well.

 

--Noah

 

From: trac-users@googlegroups.com [mailto:[EMAIL PROTECTED] On
Behalf Of Duany Espindola
Sent: Monday, June 02, 2008 10:35 AM
To: trac-users@googlegroups.com
Subject: [Trac] Re: Merge wiki pages - not a collision solution

 

Thank you Noah!

I will do this using svn or "diff and patch" commands.
I think more people have de same problem that I have. Maybe I make a plug-in
when I take a vacation.

Att

Duany César (Brazil)

On Mon, Jun 2, 2008 at 1:30 PM, Noah Kantrowitz <[EMAIL PROTECTED]> wrote:

Check both into subversion and use that (or git, hg, etc). A wiki is not
designed for that kind of complex document management.

 

--Noah

 

From: trac-users@googlegroups.com [mailto:[EMAIL PROTECTED] On
Behalf Of Duany Espindola
Sent: Monday, June 02, 2008 4:08 AM
To: trac-users@googlegroups.com
Subject: [Trac] Merge wiki pages - not a collision solution

 

Hi, everybody!

I have bean looking for a solution for two weeks for my problem and this
forum is my last try.
I had two equal wiki pages: PageA and PageB. So I make changes in PageA
and different changes in PageB. Now I need merge the changes in PageA in the
PageB.
I read a lot things about merge wiki pages in collision case, but I
don't know how to resolve my problem and I will be happy if anyone help me.

Att,

Duany César (Brazil)

 

 

 




-- 
Duany César S. Espindola


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "Trac 
Users" group.
To post to this group, send email to trac-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/trac-users?hl=en
-~--~~~~--~~--~--~---

[Trac] Re: Merge wiki pages - not a collision solution

[Duany Espindola]

Thank you Noah!

I will do this using svn or "diff and patch" commands.
I think more people have de same problem that I have. Maybe I make a plug-in
when I take a vacation.

Att

Duany César (Brazil)

On Mon, Jun 2, 2008 at 1:30 PM, Noah Kantrowitz <[EMAIL PROTECTED]> wrote:

>  Check both into subversion and use that (or git, hg, etc). A wiki is not
> designed for that kind of complex document management.
>
>
>
> --Noah
>
>
>
> *From:* trac-users@googlegroups.com [mailto:[EMAIL PROTECTED] *On
> Behalf Of *Duany Espindola
> *Sent:* Monday, June 02, 2008 4:08 AM
> *To:* trac-users@googlegroups.com
> *Subject:* [Trac] Merge wiki pages – not a collision solution
>
>
>
> Hi, everybody!
>
> I have bean looking for a solution for two weeks for my problem and
> this forum is my last try.
> I had two equal wiki pages: PageA and PageB. So I make changes in PageA
> and different changes in PageB. Now I need merge the changes in PageA in the
> PageB.
> I read a lot things about merge wiki pages in collision case, but I
> don't know how to resolve my problem and I will be happy if anyone help me.
>
> Att,
>
> Duany César (Brazil)
>
>
>
> >
>


-- 
Duany César S. Espindola

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "Trac 
Users" group.
To post to this group, send email to trac-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/trac-users?hl=en
-~--~~~~--~~--~--~---

[Trac] Re: Merge wiki pages - not a collision solution

[Noah Kantrowitz]

No. Again, you are misusing a wiki when you want a version control system.
You can use the Include macro to pull text from the VCS into the wiki if you
still want to show it there as well.

 

--Noah

 

From: trac-users@googlegroups.com [mailto:[EMAIL PROTECTED] On
Behalf Of Duany Espindola
Sent: Monday, June 02, 2008 10:30 AM
To: trac-users@googlegroups.com
Subject: [Trac] Re: Merge wiki pages - not a collision solution

 

Thank you too, but   
I think this solution not works for me because the TRAC wiki pages are
not text files.
For view this pages in text files we need do a export command. 
I want know if a plug-in could do that, something like this: "trac-admin
myEnv wiki merge PageA[1:4]  PageB "

Att,

Duany César

On Mon, Jun 2, 2008 at 1:16 PM, <[EMAIL PROTECTED]> wrote:


On Jun 2, 9:01 am, "Duany Espindola" <[EMAIL PROTECTED]> wrote:
> Thank you, *but* it is not the solution that I'm looking for.
> This tool works for common files, but I need one that works in wiki-pages
> into a TRAC environment.
>
> Someone have another idea ?
> --
> Duany César (Brazil)
>

> On Mon, Jun 2, 2008 at 9:08 AM, Jani Tiainen <[EMAIL PROTECTED]> wrote:
>
> > Duany Espindola kirjoitti:
> > > Hi, everybody!
>
> > > I have bean looking for a solution for two weeks for my problem
and
> > > this forum is my last try.
> > > I had two equal wiki pages: PageA and PageB. So I make changes in
> > > PageA and different changes in PageB. Now I need merge the changes in
> > > PageA in the PageB.
> > > I read a lot things about merge wiki pages in collision case, but
I
> > > don't know how to resolve my problem and I will be happy if anyone
help
> > me.
>
> > There is tool called "diff3" that can help you to merge and make
> > conflicts correctly provided that PageA and PageB do have common
> > preceding version. See for example 
>
> > --
> > Jani Tiainen

I don't understand how this is not a solution to  your problem.  You
want to merge/diff, use a merge/diff tool.  vimdiff,
winmerge, ...etc.  you just have to point to the actual files of the
wiki pages instead of at the rendered level.  The only other thing I
can think of, is to do one of the following:
 open both files in edit mode in separate brower windows/tabs and:
 visually merged the changes throught the file, or
 export both to plain text, use a diff tool to see the differences,
then manually cut and paste the changes into the wiki edit mode
window(s)

otherwise, I guess I don't fully understand what it is you are trying
to accomplish by the term "merge".

 




-- 
Duany César S. Espindola


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "Trac 
Users" group.
To post to this group, send email to trac-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/trac-users?hl=en
-~--~~~~--~~--~--~---

[Trac] Re: Merge wiki pages – not a collision solu tion

[Duany Espindola]

Thank you too, but
I think this solution not works for me because the TRAC wiki pages are
not text files.
For view this pages in text files we need do a export command.
I want know if a plug-in could do that, something like this: "*trac-admin
myEnv wiki merge PageA[1:4]  PageB* "

Att,

Duany César

On Mon, Jun 2, 2008 at 1:16 PM, <[EMAIL PROTECTED]> wrote:

>
> On Jun 2, 9:01 am, "Duany Espindola" <[EMAIL PROTECTED]> wrote:
> > Thank you, *but* it is not the solution that I'm looking for.
> > This tool works for common files, but I need one that works in wiki-pages
> > into a TRAC environment.
> >
> > Someone have another idea ?
> > --
> > Duany César (Brazil)
> >
> > On Mon, Jun 2, 2008 at 9:08 AM, Jani Tiainen <[EMAIL PROTECTED]> wrote:
> >
> > > Duany Espindola kirjoitti:
> > > > Hi, everybody!
> >
> > > > I have bean looking for a solution for two weeks for my problem
> and
> > > > this forum is my last try.
> > > > I had two equal wiki pages: PageA and PageB. So I make changes in
> > > > PageA and different changes in PageB. Now I need merge the changes in
> > > > PageA in the PageB.
> > > > I read a lot things about merge wiki pages in collision case, but
> I
> > > > don't know how to resolve my problem and I will be happy if anyone
> help
> > > me.
> >
> > > There is tool called "diff3" that can help you to merge and make
> > > conflicts correctly provided that PageA and PageB do have common
> > > preceding version. See for example  >
> >
> > > --
> > > Jani Tiainen
>
> I don't understand how this is not a solution to  your problem.  You
> want to merge/diff, use a merge/diff tool.  vimdiff,
> winmerge, ...etc.  you just have to point to the actual files of the
> wiki pages instead of at the rendered level.  The only other thing I
> can think of, is to do one of the following:
>  open both files in edit mode in separate brower windows/tabs and:
>  visually merged the changes throught the file, or
>  export both to plain text, use a diff tool to see the differences,
> then manually cut and paste the changes into the wiki edit mode
> window(s)
>
> otherwise, I guess I don't fully understand what it is you are trying
> to accomplish by the term "merge".
> >
>


-- 
Duany César S. Espindola

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "Trac 
Users" group.
To post to this group, send email to trac-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/trac-users?hl=en
-~--~~~~--~~--~--~---

[Trac] Re: BitNami Trac Installer now for Windows too :)

[Eirik Schwenke]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Antonio Santos skrev 02-06-2008 17:57:
| Hi folks,
|
| I just released the BitNami Trac Stack for Windows today. For those of
| you that didn't read any previous mail about this, the Stack is an
| easy to use installer which installs and configures Trac and its
| dependencies: Apache, SQLite, Subversion and Python.
|
| Until now only Linux and OSX versions were available, so I'm happy to
| announce that it will work on Windows too from now on. The installer
| won't mess with anything in the system (no path or registry needs to
| be modified) and it's open source, distributed under the Apache 2.0
| license.
|
| Our goal is to make open source applications as easy to use as
| possible (we have installers for other projects like Liferay, Drupal,
| WordPress, etc.)

(...)

A noble goal indeed. I'm a bit confused about the license issue though -- in
this mail it appears you license the installer under the apache 2.0 license,
and the various software under its respective licenses -- but from the
bitnami.org homepage it appears you re-license the entire stack to the apache
license ?

~  "Open Source
~   All Bitnami Stacks are free to download and use under the terms of the
~   Apache License 2.0"

I realise this might just be a simplification for end-users -- but as
especially the Gnu Public/lesser Gnu Public licenses have some very specific
demands on (re)distributors it's something you can't really gloss over.

I was unable to find any clarification on this in your faq, or a quick browse
of your site/forums, including:

http://bitnami.org/article/bitnami-easy-to-install-open-source-applications
http://bitnami.org/faq

The individual stacks do list licences, such as:

~  http://bitnami.org/stack/wordpress
~  http://bitnami.org/stack/wampstack

But it would appear there's no link to the source-code code for eg mysql, which
I assume you distribute under the GPL ? As for the wampstack, I again assume
you distribute apache under apl, php under the php licence and and the
installer under apl?


I just thought this was an issue that might need a little bit more attention on
your otherwise beautiful and very useful site. On a side note; what are you
using for managing the content on your site ?


Best regards,

- --
~ .---.  Eirik Schwenke <[EMAIL PROTECTED]>
( NSD ) Harald Hårfagresgate 29Rom 150
~ '---'  N-5007 Bergentlf: (555) 889 13

~  GPG-key at pgp.mit.edu  Id 0x8AA3392C
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFIRCrYxUW7FIqjOSwRAnMuAJ9uKWpnk0tbAV5EgIav8Yn9el/wGgCeIJLA
UreZ1SK4i9nVkPtBqSJtETs=
=gmYr
-END PGP SIGNATURE-

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "Trac 
Users" group.
To post to this group, send email to trac-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/trac-users?hl=en
-~--~~~~--~~--~--~---

[Trac] Re: How to configure trac | new user

[Erik Bray]

On Sun, Jun 1, 2008 at 11:19 PM, Ravi Kochar <[EMAIL PROTECTED]> wrote:
> 2) How can I import data from excel in trac.

There's no easy answer to this, as it's highly dependent on how the
spreadsheet is formatted.  But I've had to do this a few times
before--I asked the maintainer of the spreadsheet to make sure that
each column properly corresponded to a specific ticket field.  Then I
had them export it as CSV, and wrote a simple script to insert tickets
into the database for each row in the spreadsheet.

Erik

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "Trac 
Users" group.
To post to this group, send email to trac-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/trac-users?hl=en
-~--~~~~--~~--~--~---

[Trac] Re: Merge wiki pages - not a collision solution

[Noah Kantrowitz]

Check both into subversion and use that (or git, hg, etc). A wiki is not
designed for that kind of complex document management.

 

--Noah

 

From: trac-users@googlegroups.com [mailto:[EMAIL PROTECTED] On
Behalf Of Duany Espindola
Sent: Monday, June 02, 2008 4:08 AM
To: trac-users@googlegroups.com
Subject: [Trac] Merge wiki pages - not a collision solution

 

Hi, everybody!

I have bean looking for a solution for two weeks for my problem and this
forum is my last try.
I had two equal wiki pages: PageA and PageB. So I make changes in PageA
and different changes in PageB. Now I need merge the changes in PageA in the
PageB.
I read a lot things about merge wiki pages in collision case, but I
don't know how to resolve my problem and I will be happy if anyone help me.

Att,

Duany César (Brazil)




--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "Trac 
Users" group.
To post to this group, send email to trac-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/trac-users?hl=en
-~--~~~~--~~--~--~---

[Trac] Re: Merge wiki pages – not a collision solu tion

[yoheeb]

On Jun 2, 9:01 am, "Duany Espindola" <[EMAIL PROTECTED]> wrote:
> Thank you, *but* it is not the solution that I'm looking for.
> This tool works for common files, but I need one that works in wiki-pages
> into a TRAC environment.
>
> Someone have another idea ?
> --
> Duany César (Brazil)
>
> On Mon, Jun 2, 2008 at 9:08 AM, Jani Tiainen <[EMAIL PROTECTED]> wrote:
>
> > Duany Espindola kirjoitti:
> > > Hi, everybody!
>
> > > I have bean looking for a solution for two weeks for my problem and
> > > this forum is my last try.
> > > I had two equal wiki pages: PageA and PageB. So I make changes in
> > > PageA and different changes in PageB. Now I need merge the changes in
> > > PageA in the PageB.
> > > I read a lot things about merge wiki pages in collision case, but I
> > > don't know how to resolve my problem and I will be happy if anyone help
> > me.
>
> > There is tool called "diff3" that can help you to merge and make
> > conflicts correctly provided that PageA and PageB do have common
> > preceding version. See for example 
>
> > --
> > Jani Tiainen

I don't understand how this is not a solution to  your problem.  You
want to merge/diff, use a merge/diff tool.  vimdiff,
winmerge, ...etc.  you just have to point to the actual files of the
wiki pages instead of at the rendered level.  The only other thing I
can think of, is to do one of the following:
 open both files in edit mode in separate brower windows/tabs and:
  visually merged the changes throught the file, or
  export both to plain text, use a diff tool to see the differences,
then manually cut and paste the changes into the wiki edit mode
window(s)

otherwise, I guess I don't fully understand what it is you are trying
to accomplish by the term "merge".
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "Trac 
Users" group.
To post to this group, send email to trac-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/trac-users?hl=en
-~--~~~~--~~--~--~---

[Trac] BitNami Trac Installer now for Windows too :)

[Antonio Santos]

Hi folks,

I just released the BitNami Trac Stack for Windows today. For those of
you that didn't read any previous mail about this, the Stack is an
easy to use installer which installs and configures Trac and its
dependencies: Apache, SQLite, Subversion and Python.

Until now only Linux and OSX versions were available, so I'm happy to
announce that it will work on Windows too from now on. The installer
won't mess with anything in the system (no path or registry needs to
be modified) and it's open source, distributed under the Apache 2.0
license.

Our goal is to make open source applications as easy to use as
possible (we have installers for other projects like Liferay, Drupal,
WordPress, etc.)

The stack is downloadable from http://www.bitnami.org/stack/trac , and
there are forums to ask for help or give feedback at
http://www.bitnami.org/forums

Cheers!

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "Trac 
Users" group.
To post to this group, send email to trac-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/trac-users?hl=en
-~--~~~~--~~--~--~---

[Trac] Re: Description_default and blank separating lines

[lfrancis]

Is there no way to set description_default = "foo" + two line feeds +
"morefoo", etc. in  Trac.ini?

On May 28, 5:16 pm, lfrancis <[EMAIL PROTECTED]> wrote:
> I'm setting description_default to equal [Description], [Steps to
> reproduce], [Expected results], [Actual results] in my trac.ini and
> can't figure out how to insert blank lines between them, lines in
> the .ini are ignored.
>
> --This is what I want:
>
> [Description]
>
> [Steps to reproduce]
>
> 1.
> 2.
> 3.
> 4.
>
> [Expected results]
>
> [Actual results]
>
> --And this is what I actually get in the description field:
>
> [Description]
> [Steps to reproduce]
> 1.
> 2.
> 3.
> [Expected results]
> [Actual results]
>
> Thanks in advance!
>
> -Lewis
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "Trac 
Users" group.
To post to this group, send email to trac-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/trac-users?hl=en
-~--~~~~--~~--~--~---

[Trac] Re: Merge wiki pages – not a collision solu tion

[Duany Espindola]

Thank you, *but* it is not the solution that I'm looking for.
This tool works for common files, but I need one that works in wiki-pages
into a TRAC environment.

Someone have another idea ?
-- 
Duany César (Brazil)

On Mon, Jun 2, 2008 at 9:08 AM, Jani Tiainen <[EMAIL PROTECTED]> wrote:

>
> Duany Espindola kirjoitti:
> > Hi, everybody!
> >
> > I have bean looking for a solution for two weeks for my problem and
> > this forum is my last try.
> > I had two equal wiki pages: PageA and PageB. So I make changes in
> > PageA and different changes in PageB. Now I need merge the changes in
> > PageA in the PageB.
> > I read a lot things about merge wiki pages in collision case, but I
> > don't know how to resolve my problem and I will be happy if anyone help
> me.
>
> There is tool called "diff3" that can help you to merge and make
> conflicts correctly provided that PageA and PageB do have common
> preceding version. See for example 
>
> --
> Jani Tiainen
>
> >
>

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "Trac 
Users" group.
To post to this group, send email to trac-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/trac-users?hl=en
-~--~~~~--~~--~--~---

[Trac] Re: TracSvnPoliciesPlugin problem

[Robert C Corsaro]

rupert thurner wrote:
> could you tell if policiesplug would be possible in conjunction with
> mercurial, and http://www.trac-hacks.org/wiki/HgTimelinePlugin as
> well?
> 

There would need to be modifications for it to work on mercurial.  I 
would gladly commit a patch.  The way it works now is that symlinks to a 
master svn-hook plugin are created in the svn hooks directory.  I'm not 
an avid hg user, so I'm not sure how it works, but it's probably 
similar.  If this does become more generic, maybe we could rename the 
svn-hook file.  Or maybe there is a different hook wrapper for each type 
of repo.

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "Trac 
Users" group.
To post to this group, send email to trac-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/trac-users?hl=en
-~--~~~~--~~--~--~---

[Trac] Re: Spam [Trac] post-commit hook adding to ticket, but not sending e-mail

[Robert C Corsaro]

David Deller wrote:

> I'm trying to get post-commit hook working. It adds the SVN comment to  
> the ticket, but it doesn't send the e-mail automatically. 


There is an SVNPoliciesPlugin that does what you want and even has a 
configuration admin page.  I can help you set it up if you want.  You 
can check it out with 'svn co 
http://code.optaros.com/svn/oforge/trunk/plugins/svnpoliciesplugin'.

There is a README in the svnpolicies dir.


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "Trac 
Users" group.
To post to this group, send email to trac-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/trac-users?hl=en
-~--~~~~--~~--~--~---

[Trac] Re: Trac installation and templates issue

[Emmanuel Blot]

> Currently the folder /usr/share/trac/templates does not exist. The trac
> folder is empty.

This does not match the Debian package

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "Trac 
Users" group.
To post to this group, send email to trac-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/trac-users?hl=en
-~--~~~~--~~--~--~---

[Trac] Re: Merge wiki pages – not a collision solu tion

[Jani Tiainen]

Duany Espindola kirjoitti:
> Hi, everybody!
> 
> I have bean looking for a solution for two weeks for my problem and 
> this forum is my last try.
> I had two equal wiki pages: PageA and PageB. So I make changes in 
> PageA and different changes in PageB. Now I need merge the changes in 
> PageA in the PageB.
> I read a lot things about merge wiki pages in collision case, but I 
> don't know how to resolve my problem and I will be happy if anyone help me.

There is tool called "diff3" that can help you to merge and make 
conflicts correctly provided that PageA and PageB do have common 
preceding version. See for example 

-- 
Jani Tiainen

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "Trac 
Users" group.
To post to this group, send email to trac-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/trac-users?hl=en
-~--~~~~--~~--~--~---

[Trac] Re: Trac installation and templates issue

[Gael Poffet]

Problem solved. I have uninstall trac and re-install  it and the missing files 
have been created.
Thanks for help.
I will check for the used version on Debian.




Gael Poffet
Ingénieur HES
+41  (0)78 707 32 64
[EMAIL PROTECTED]



Idael Software
Rue des Pêcheurs 8A
1400 Yverdon-les-Bains
024 / 426 38 89
http://www.idael.ch

  Pensez à l’environnement, n’imprimez pas vos emails pour rien, utilisez une 
solution de gestion documentaire !!




-Original Message-
From: trac-users@googlegroups.com [mailto:[EMAIL PROTECTED] On Behalf Of 
Emmanuel Blot
Sent: lundi 2 juin 2008 11:37
To: trac-users@googlegroups.com
Subject: [Trac] Re: Trac installation and templates issue


> For information, I'm running Trac on Debian, installed with apt-get
> install command so the current version is 0.10.3-1etch2

Is this file readable: /usr/share/trac/templates/header.cs ?

BTW, I would not recommend to install 0.10.3 has it is known to have
some issues. I'm not sure what the debian maintainers have changed in
this release (from the official 0.10.3 release), but you may have some
issues with it.




--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "Trac 
Users" group.
To post to this group, send email to trac-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/trac-users?hl=en
-~--~~~~--~~--~--~---

[Trac] Merge wiki pages – not a collision solution

[Duany Espindola]

Hi, everybody!

I have bean looking for a solution for two weeks for my problem and this
forum is my last try.
I had two equal wiki pages: PageA and PageB. So I make changes in PageA
and different changes in PageB. Now I need merge the changes in PageA in the
PageB.
I read a lot things about merge wiki pages in collision case, but I
don't know how to resolve my problem and I will be happy if anyone help me.

Att,

Duany César (Brazil)

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "Trac 
Users" group.
To post to this group, send email to trac-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/trac-users?hl=en
-~--~~~~--~~--~--~---

[Trac] Re: Trac installation and templates issue

[Gael Poffet]

Currently the folder /usr/share/trac/templates does not exist. The trac
folder is empty.


-Original Message-
From: trac-users@googlegroups.com [mailto:[EMAIL PROTECTED] On
Behalf Of Emmanuel Blot
Sent: lundi 2 juin 2008 11:37
To: trac-users@googlegroups.com
Subject: [Trac] Re: Trac installation and templates issue


> For information, I'm running Trac on Debian, installed with apt-get
> install command so the current version is 0.10.3-1etch2

Is this file readable: /usr/share/trac/templates/header.cs ?

BTW, I would not recommend to install 0.10.3 has it is known to have
some issues. I'm not sure what the debian maintainers have changed in
this release (from the official 0.10.3 release), but you may have some
issues with it.




--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "Trac 
Users" group.
To post to this group, send email to trac-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/trac-users?hl=en
-~--~~~~--~~--~--~---

[Trac] Re: trac authentication problem again...

[Alex da Franca]

Am 02.06.2008 um 12:18 schrieb Emmanuel Blot:
>
> This is consistent with the expected behaviour: applying the
> authentication rules to the whole project (that is /trac instead of
> /trac/login, see above) forces authentication whatever the Trac page
> you're trying to browse.

which is exactly what I want for this project and which used to work  
like a charme until the upgrade :-(


> If you do want to click on "login" first, use
> the documented path: 

Ok, I am trying that now.
thanks for the suggestion.

>
>
>> what do I need to change in that case. what do I need for
>> "AuthBasicProvider" ?
>
> I think that AuthBasicProvider can be omitted (default config) with
> htpasswd file authentication. Read the Apache 2.2 documentation for
> further details, from http://httpd.apache.org/...

yes, the default is "file" and that is exactly what I am using. so it  
should work.
it used to work until now.
:-(


thanks for the help


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "Trac 
Users" group.
To post to this group, send email to trac-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/trac-users?hl=en
-~--~~~~--~~--~--~---

[Trac] Re: trac authentication problem again...

[Emmanuel Blot]

> 
> 
>
> it seems to work from the webserver side of things, as I can clear all
> my cached logins in the browser and it asks me for the username and
> password and allows me to proceed. However trac then only displays the
> content as if I was "anonymous" without the option to "login"

This is consistent with the expected behaviour: applying the
authentication rules to the whole project (that is /trac instead of
/trac/login, see above) forces authentication whatever the Trac page
you're trying to browse. If you do want to click on "login" first, use
the documented path: 

> what do I need to change in that case. what do I need for
> "AuthBasicProvider" ?

I think that AuthBasicProvider can be omitted (default config) with
htpasswd file authentication. Read the Apache 2.2 documentation for
further details, from http://httpd.apache.org/...

Cheers,
Manu

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "Trac 
Users" group.
To post to this group, send email to trac-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/trac-users?hl=en
-~--~~~~--~~--~--~---

[Trac] Re: trac authentication problem again...

[Alex da Franca]

Am 02.06.2008 um 11:25 schrieb Emmanuel Blot:

>
>> does that sound familiar to anyone?
>
> Which authentication scheme do you use in your Apache config?
> If your Apache release has been upgraded from 2.0.x to 2.2.x you may
> have to edit your configuration file to match the new Apache
> authentication settings - I'm thinking about directives such as
> "AuthBasicProvider" for example.

many thanks for taking the time, Manu.

I use basic http authentication (or at least I am trying to do so,  
maybe my trac isn't properly recognizing that ?)

in my apache site config I have:


   AuthType Basic
   AuthName "Trac"
   AuthUserFile /var/tracpw/trac.htpasswd
   Require valid-user
   Options FollowSymLinks
   Order allow,deny
   Allow from all


it seems to work from the webserver side of things, as I can clear all  
my cached logins in the browser and it asks me for the username and  
password and allows me to proceed. However trac then only displays the  
content as if I was "anonymous" without the option to "login"

btw, how can I display that "login" link at the top. It doesn't show up.
on other trac environmets (on another server) it does and I can't  
figure out what is different, regarding login.

I am not exactly sure from which apache version to which I updated,  
but it can very well be, that it was not 2.2 before.
what do I need to change in that case. what do I need for  
"AuthBasicProvider" ?

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "Trac 
Users" group.
To post to this group, send email to trac-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/trac-users?hl=en
-~--~~~~--~~--~--~---

[Trac] Re: Trac installation and templates issue

[Emmanuel Blot]

> For information, I'm running Trac on Debian, installed with apt-get
> install command so the current version is 0.10.3-1etch2

Is this file readable: /usr/share/trac/templates/header.cs ?

BTW, I would not recommend to install 0.10.3 has it is known to have
some issues. I'm not sure what the debian maintainers have changed in
this release (from the official 0.10.3 release), but you may have some
issues with it.

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "Trac 
Users" group.
To post to this group, send email to trac-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/trac-users?hl=en
-~--~~~~--~~--~--~---

[Trac] Trac installation and templates issue

[Gael]

Hi,
I'm just getting mad with the following installation issue. When I run
the "trac-admin /usr/share/trac initenv" it asks me the templates
directory. If I keep the default value or if I give an other folder I
always have this error message:

/usr/share/trac/templates doesn't look like a Trac templates directory

I have search during a long time a solution on the web but I can't
find anything. If someone can give me some clues it woud be great.

For information, I'm running Trac on Debian, installed with apt-get
install command so the current version is 0.10.3-1etch2

Thanks

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "Trac 
Users" group.
To post to this group, send email to trac-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/trac-users?hl=en
-~--~~~~--~~--~--~---

[Trac] Re: trac authentication problem again...

[Emmanuel Blot]

> does that sound familiar to anyone?

Which authentication scheme do you use in your Apache config?
If your Apache release has been upgraded from 2.0.x to 2.2.x you may
have to edit your configuration file to match the new Apache
authentication settings - I'm thinking about directives such as
"AuthBasicProvider" for example.

HTH,
Manu

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "Trac 
Users" group.
To post to this group, send email to trac-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/trac-users?hl=en
-~--~~~~--~~--~--~---

[Trac] Re: How to configure trac | new user

[Emmanuel Blot]

> 1) Configure - How I can add fields (Release, Owner, tester)
Read TracTicketsCustomFields wiki page.

Cheers,
Manu

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "Trac 
Users" group.
To post to this group, send email to trac-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/trac-users?hl=en
-~--~~~~--~~--~--~---

[Trac] trac authentication problem again...

[Alex da Franca]

Hi list,

I recently "dist-upgraded" my debian and since then I can't log into  
trac anymore as registered user.
I used to have it set up, so that my apache config has the trac  
location protected with basic authentication.
but every time I log in, trac sees me as "anonymous" and not as the  
user, which logged in.
I have cleared the passwords of the browser and I can confirm, that  
the location is password protected and I need to enter name and  
password, but still I can see in the trac log file, that the requests  
come from "anonymous" and I can only reach whatever I have set to be  
accessible for "anonymous".

Unfortunately I am not exactly sure, whether it is something, caused  
by trac update or the dist-upgrade of the debian system. The update of  
debian changed lots including the mysql version, but not the apache  
config, as I did skip that step. I needed to upgrade the trac  
environment as I got a "database too new" and in that go I also  
updated trac to the latest trunk (it already was 0.12 before, when it  
worked)

does that sound familiar to anyone?
it must be a very simple stupid thing which is wrong (hopefully) but I  
can't figure it out at the moment. been striggling with it the last  
two days...
pls help ;-)
TIA

alex

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "Trac 
Users" group.
To post to this group, send email to trac-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/trac-users?hl=en
-~--~~~~--~~--~--~---

[Trac] Re: TracSvnPoliciesPlugin problem

[Culapov Andrei]

We designed this plugin to work with trac 0.11. For example the
templates are all genshi. I don't think that it will work for trac
0.10.4 but you can give it a try.


On Sun, Jun 1, 2008 at 12:15 AM, Brett <[EMAIL PROTECTED]> wrote:
>
> This is a side question, but is the TracSvnPoliciesPlugin only
> compatible with Trac 0.11, or can I use it with 0.10.4?
>
>
> Brett
>
>
>
> On May 31, 1:37 pm, "Culapov Andrei" <[EMAIL PROTECTED]> wrote:
>> We made the plugin to work only with svn. So sorry, but no.
>>
>> On Fri, May 30, 2008 at 10:30 PM, rupert thurner
>>
>> <[EMAIL PROTECTED]> wrote:
>>
>> > could you tell if policiesplug would be possible in conjunction with
>> > mercurial, andhttp://www.trac-hacks.org/wiki/HgTimelinePluginas
>> > well?
>>
>> > rupert.
>>
>> > On May 22, 4:10 pm, Robert C Corsaro <[EMAIL PROTECTED]> wrote:
>> >> >> On Wed, May 21, 2008 at 10:36 PM, Pablo Fabregat
>> >> >> <[EMAIL PROTECTED]> wrote:
>> >> >>> Hi all,
>>
>> >> >>> I managed to get this plugin installed and it throws no errors... but
>> >> >> when i do a commit, whatever policy i put, nothing happens, it just 
>> >> >> commits,
>> >> >> and i can tell that the hook's being executed (it's in 
>> >> >> /usr/bin/svn-hook)
>> >> >> because i edited that script to throw an error and, it does...
>> >> >>> i'm almost done with this! :O
>>
>> >> >>> any ideas ?
>> >> >>> thanks in advance!
>>
>> >> We worked this out on IRC, but the solution was to copy the
>> >> svnpolicies/bin/svn-hook to /usr/local/bin overwriting the setuptools
>> >> wrapper script.  I'm working on a fix.
> >
>

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "Trac 
Users" group.
To post to this group, send email to trac-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/trac-users?hl=en
-~--~~~~--~~--~--~---

[Trac] Re: Installing TagsPlugin

[Michael Schmarck]

Hi!

On Sun, Jun 1, 2008 at 11:19 AM, Alec Thomas <[EMAIL PROTECTED]> wrote:
>
> Enable debug logging and check the logs.
>
> Is your Trac installation using Genshi 0.5dev? This is required.

I had Genshi 0.4 installed. After installing 0.5 from SVN,
everything is fine.

Thanks a lot,
Michael

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "Trac 
Users" group.
To post to this group, send email to trac-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/trac-users?hl=en
-~--~~~~--~~--~--~---