[Trac] modpython project is dead... What impact on trac development?
Hello, I've just read Graham Dumpleton post on his blog [http://blog.dscpl.com.au/2010/06/modpython-project-is-now-officially.html] announcing the death of modpython project. I wonder if it will have major (or minor) impact on the trac development ? Thank you. Crusty Applesniffer -- You received this message because you are subscribed to the Google Groups Trac Users group. To post to this group, send email to trac-us...@googlegroups.com. To unsubscribe from this group, send email to trac-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/trac-users?hl=en.
Re: [Trac] modpython project is dead... What impact on trac development?
mod_WSGI On Wed, Jun 23, 2010 at 16:27, Crusty Applesniffer crusty.applesnif...@free.fr wrote: Hello, I've just read Graham Dumpleton post on his blog [http://blog.dscpl.com.au/2010/06/modpython-project-is-now-officially.html] announcing the death of modpython project. I wonder if it will have major (or minor) impact on the trac development ? Thank you. Crusty Applesniffer -- You received this message because you are subscribed to the Google Groups Trac Users group. To post to this group, send email to trac-us...@googlegroups.com. To unsubscribe from this group, send email to trac-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/trac-users?hl=en. -- http://zoomquiet.org 人生苦短? Pythonic! -- You received this message because you are subscribed to the Google Groups Trac Users group. To post to this group, send email to trac-us...@googlegroups.com. To unsubscribe from this group, send email to trac-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/trac-users?hl=en.
Re: [Trac] modpython project is dead... What impact on trac development?
On 23 Jun 2010, at 10:27, Crusty Applesniffer crusty.applesnif...@free.fr wrote: I wonder if it will have major (or minor) impact on the trac development ? Given that there are many ways to serve Trac from Apache, with better performances and less troubles (fastcgi, wsgi, ...) I don't think it matters that much, except for admins who would have to upgrade on day or another. 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-us...@googlegroups.com. To unsubscribe from this group, send email to trac-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/trac-users?hl=en.
Re: [Trac] modpython project is dead... What impact on trac development?
This is my case :( On the other side, I am always happy to learn new things :) Thank you, Crusty Applesniffer On 6/23/2010 10:53 AM, Emmanuel Blot wrote: On 23 Jun 2010, at 10:27, Crusty Applesniffercrusty.applesnif...@free.fr wrote: I wonder if it will have major (or minor) impact on the trac development ? Given that there are many ways to serve Trac from Apache, with better performances and less troubles (fastcgi, wsgi, ...) I don't think it matters that much, except for admins who would have to upgrade on day or another. 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-us...@googlegroups.com. To unsubscribe from this group, send email to trac-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/trac-users?hl=en.
RE: [Trac] modpython project is dead... What impact on trac development?
On 23 Jun 2010, at 10:27, Crusty Applesniffer crusty.applesnif...@free.fr wrote: I wonder if it will have major (or minor) impact on the trac development ? On 6/23/2010 10:53 AM, Emmanuel Blot wrote: Given that there are many ways to serve Trac from Apache, with better performances and less troubles (fastcgi, wsgi, ...) I don't think it matters that much, except for admins who would have to upgrade on day or another. Cheers, Manu. -Original Message- From: trac-users@googlegroups.com [mailto:trac-us...@googlegroups.com] On Behalf Of Crusty Applesniffer Sent: 23 June 2010 09:56 To: trac-users@googlegroups.com Subject: Re: [Trac] modpython project is dead... What impact on trac development? This is my case :( On the other side, I am always happy to learn new things :) Thank you, Crusty Applesniffer Is it about time that all the prominent pointers to mod_python on t.e.o were downgraded or removed? People still seem to be opting for mod_python because it comes first... http://trac.edgewall.org/wiki/HowToContribute seems to encourage us to edit the t.e.o pages so I may have a go at this a bit later on when I'm not at work. ~ mark c -- You received this message because you are subscribed to the Google Groups Trac Users group. To post to this group, send email to trac-us...@googlegroups.com. To unsubscribe from this group, send email to trac-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/trac-users?hl=en.
Re: [Trac] modpython project is dead... What impact on trac development?
Quoting Crusty Applesniffer crusty.applesnif...@free.fr: I've just read Graham Dumpleton post on his blog [http://blog.dscpl.com.au/2010/06/modpython-project-is-now-officially.html] announcing the death of modpython project. I wonder if it will have major (or minor) impact on the trac development ? I've never used mod_python, but mod_wsgi, which is the recommended method, AFAIK. -- You received this message because you are subscribed to the Google Groups Trac Users group. To post to this group, send email to trac-us...@googlegroups.com. To unsubscribe from this group, send email to trac-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/trac-users?hl=en.
[Trac] Genshi UnicodeEncodeError
Hi, I wrote a macro which checks if a text is well-formed, i.e. if it was inserted as required for our project. For this purpose I used some regular expressions. My problem is that sometimes, when the expression can't be matched, I become the following error: Trac Error Genshi UnicodeEncodeError error while rendering template (unknown template location) I also should mention that it only occurs with the 0.11.7 version but not with the 0.11.7.1dev-r0, for instance. What should I do to solve the problem? Regards, Rodrik. -- You received this message because you are subscribed to the Google Groups Trac Users group. To post to this group, send email to trac-us...@googlegroups.com. To unsubscribe from this group, send email to trac-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/trac-users?hl=en.
[Trac] Write-access to the svn repository via the source browser
Dear Trac-Users list, As mentioned briefly on IRC (my username is pipern), we'd like to provide our Trac users with the ability to write to the svn repository via their web browser, through the source browser. We're interested in svn only at the moment. It's already been discussed a little over the last few years as http://trac.edgewall.org/ticket/2956 That ticket is mostly about 'Upload file', but we'd also like to have: * Rename * Delete * mkdir * Maybe edit for simple text files We'll be doing this work ourselves eventually, but it would be ideal for us if we could fund the development so that we can do it at the same time as other work. Is anyone (from core development team, or anyone else) interested in taking this as a paid job, or otherwise, and working with us to create a plugin on Trac-Hacks ? It may end up being a plugin + patch, I suppose. It would be great to discuss this feature here (and/or maybe http://trac.edgewall.org/ticket/2956 ?), and if anyone wants to talk to use about taking it as a paid job, please get in touch with me directly. Regards, Nick PS. Sorry for the disclaimer block that is probably going to appear below my .sig. -- nick.pi...@logica.com | www.logica.com Logica UK Limited, registered in England Wales (registered number 947968) Registered Office: 250 Brook Drive, Green Park, Reading RG2 6UA, United Kingdom Please help Logica to respect the environment by not printing this email / Pour contribuer comme Logica au respect de l'environnement, merci de ne pas imprimer ce mail / Bitte drucken Sie diese Nachricht nicht aus und helfen Sie so Logica dabei, die Umwelt zu schützen. / Por favor ajude a Logica a respeitar o ambiente nao imprimindo este correio electronico. This e-mail and any attachment is for authorised use by the intended recipient(s) only. It may contain proprietary material, confidential information and/or be subject to legal privilege. It should not be copied, disclosed to, retained or used by, any other party. If you are not an intended recipient then please promptly delete this e-mail and any attachment and all copies and inform the sender. Thank you. -- You received this message because you are subscribed to the Google Groups Trac Users group. To post to this group, send email to trac-us...@googlegroups.com. To unsubscribe from this group, send email to trac-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/trac-users?hl=en.
[Trac] Help with new trac 12 plugin upgrade
I am trying to port all of the plugins I maintain to trac 12 (Timing and Estimation and Estimator primarily). The issue I am having is this: When I was managing transactions myself a single sql statement throwing an exception was not an issue. As such I could take certain actions that were valid for a specific backend and invalid for other backends, and by handling this error, the upgrade process would still go through. An example: updating the sequences in postgresql to contain the new correct value (after manually inserting rows with new ids). This is not necessary and invalid in sqllite but seemed necessary in Postgresql, so that there would not be duplicate ids. Another example is checking for table existence. Given there is not cross platform way to do this, the easiest I had been able to come up with was to select a row from it, and if that succeeds the table exists, otherwise it is false. Is there anyway to get a second, out of transaction connection (yes I know all the inherent dangers of this)? Are there better backend methods to be using? Is there a way to not have a single exception on a connection invalidate the entire transaction? Do I just need to write special cased update code based on the database backend type I am connecting to? Thanks for the advice, Russ -- You received this message because you are subscribed to the Google Groups Trac Users group. To post to this group, send email to trac-us...@googlegroups.com. To unsubscribe from this group, send email to trac-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/trac-users?hl=en.
[Trac] LDAP plugin advice, user details
Hi all, The number of projects we have here is growing and I'm getting an increasing number of complaints from users about having to fill in their details repeatedly in the user preferences. I use apache and mod_ldap to authenticate. Trac running over mod_python. Looking on trac-hacks there are a number of LDAP plugins, does anyone use any of them just to pull user data from LDAP (Active Directory) rather than authentication as well? Any advice appreciated. Simon -- You received this message because you are subscribed to the Google Groups Trac Users group. To post to this group, send email to trac-us...@googlegroups.com. To unsubscribe from this group, send email to trac-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/trac-users?hl=en.
Re: [Trac] Help with new trac 12 plugin upgrade
Russ,
On 22/06/10 16:43, bobbysmith007 wrote:
I am trying to port all of the plugins I maintain to trac 12 (Timing and
Estimation and Estimator primarily).
We've been thinking about this too. I asked a couple of questions on
IRC, but not come up with anything great yet.
Attached is what we have so far, but it's not at all good. Mostly kind
of a hack to make it work for now...
I think the dbhelper.py layer functions are not so necessary these days,
and it could be easier to read without them?
(note the revision numbers are not those of trac-hacks.org)
Regards,
Nick
--
nick.pi...@logica.com | www.logica.com
Logica UK Limited, registered in England Wales (registered number 947968)
Registered Office: 250 Brook Drive, Green Park, Reading RG2 6UA, United
Kingdom
Sorry for this disclaimer:
Index:
trunk/plugins/open/timingandestimationplugin/timingandestimationplugin/api.py
===
---
trunk/plugins/open/timingandestimationplugin/timingandestimationplugin/api.py
(revision 325)
+++
trunk/plugins/open/timingandestimationplugin/timingandestimationplugin/api.py
(revision 452)
@@ -72,6 +72,6 @@
# Legacy support hack (supports upgrades from 0.1.6 to 0.1.7)
if self.db_installed_version == 0:
+report_version = dbhelper.db_table_exists(self, 'report_version');
bill_date = dbhelper.db_table_exists(self, 'bill_date');
-report_version = dbhelper.db_table_exists(self, 'report_version');
if bill_date and report_version:
self.db_installed_version = 1
Index:
trunk/plugins/open/timingandestimationplugin/timingandestimationplugin/dbhelper.py
===
---
trunk/plugins/open/timingandestimationplugin/timingandestimationplugin/dbhelper.py
(revision 325)
+++
trunk/plugins/open/timingandestimationplugin/timingandestimationplugin/dbhelper.py
(revision 452)
@@ -2,58 +2,31 @@
def get_all(com, sql, *params):
Executes the query and returns the (description, data)
-db = com.env.get_db_cnx()
+db = com.env.get_read_db()
cur = db.cursor()
desc = None
data = None
-try:
-cur.execute(sql, params)
-data = list(cur.fetchall())
-desc = cur.description
-db.commit();
-except Exception, e:
-com.log.error('There was a problem executing sql:%s \n \
-with parameters:%s\nException:%s'%(sql, params, e));
-db.rollback();
-try:
-db.close()
-except:
-pass
-
+cur.execute(sql, params)
+data = list(cur.fetchall())
+desc = cur.description
return (desc, data)
def execute_non_query(com, sql, *params):
Executes the query on the given project
-db = com.env.get_db_cnx()
+@com.env.with_transaction()
+def do_execute(db):
+cur = db.cursor()
+cur.execute(sql, params)
+
+def get_first_row(com, sql, *params):
+ Returns the first row of the query results as a tuple of values (or
None)
+db = com.env.get_read_db()
cur = db.cursor()
try:
cur.execute(sql, params)
-db.commit()
+return cur.fetchone()
except Exception, e:
com.log.error('There was a problem executing sql:%s \n \
-with parameters:%s\nException:%s'%(sql, params, e));
-db.rollback();
-try:
-db.close()
-except:
-pass
-
-def get_first_row(com, sql,*params):
- Returns the first row of the query results as a tuple of values (or
None)
-db = com.env.get_db_cnx()
-cur = db.cursor()
-data = None;
-try:
-cur.execute(sql, params)
-data = cur.fetchone();
-db.commit();
-except Exception, e:
-com.log.error('There was a problem executing sql:%s \n \
-with parameters:%s\nException:%s'%(sql, params, e));
-db.rollback()
-try:
-db.close()
-except:
-pass
-return data;
+with parameters:%s\nException:%s'%(sql, params, e))
+return None
def get_scalar(com, sql, col=0, *params):
@@ -66,39 +39,21 @@
def execute_in_trans(com, *args):
-db = com.env.get_db_cnx()
-cur = db.cursor()
-result = True
-try:
+@com.env.with_transaction()
+def do_execute(db):
+cur = db.cursor()
for sql, params in args:
cur.execute(sql, params)
-db.commit()
-except Exception, e:
-com.log.error('There was a problem executing sql:%s \n \
-with parameters:%s\nException:%s'%(sql, params, e));
-db.rollback();
-result = e
-try:
-db.close()
-except:
-pass
-return result
+return True
def db_table_exists(com, table):
-db = com.env.get_db_cnx()
-sql = SELECT * FROM %s LIMIT 1 % table;
-cur = db.cursor()
-has_table = True;
-try:
-cur.execute(sql)
-db.commit()
-except Exception, e:
-
[Trac] Commit changes too many file's age/revision stats
In the source browser for the new trac 0.12, I'm having a really strange issue: in one of my repos, commits are frequently setting the age/revision statistic of file and directories that were not a part of the commit. It's not just a few files and directories, it's nearly every file and directory in the entire source tree that gets its revision changed to the latest one. svn info still gives me the correct Last Changed Rev for the affected files and directories, so I have no idea how trac is getting its wrong information for these files. I've done trac-admin repository resync to rebuild the cached data, and I still get the same bad revisions and change dates. I'm using the trac-admin changeset notification right now, but it was happening when I still had the per-page-update stuff running. The one thing about this repo that's strange is that its trunk was svn mv'd from a branch of a different project. We use the normal multi-project svn setup, where the root of svn is a bunch of projects, and under each project dir we have trunk, branches, tags. We made this new project by svn mkdir'ing the project base, svn mv'ing the branch into the project trunk, and then making the branch and tag dirs. I know that's broken our ability to view changes from before the move, so maybe it's also somehow breaking the revision/age info in the viewer? That doesn't seem like it should be related, but I really don't know what is going on. If I can provide any other info that might be helpful, I'd be happy to. It's pretty annoying having the Rev and Age columns of the source browser being broken. -- You received this message because you are subscribed to the Google Groups Trac Users group. To post to this group, send email to trac-us...@googlegroups.com. To unsubscribe from this group, send email to trac-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/trac-users?hl=en.
Re: [Trac] Help with new trac 12 plugin upgrade
Hello, The post and this answer is probably belonging to Trac-dev, but anyway... On 6/22/2010 5:43 PM, bobbysmith007 wrote: I am trying to port all of the plugins I maintain to trac 12 (Timing and Estimation and Estimator primarily). The issue I am having is this: When I was managing transactions myself a single sql statement throwing an exception was not an issue. As such I could take certain actions that were valid for a specific backend and invalid for other backends, and by handling this error, the upgrade process would still go through. If you're talking about the upgrade process only, then you have to realize that there's anyway no global transaction going on. For most backends (well, any except PostgreSQL), most of the changes happening during an upgrade like creating a new table, adding a column, etc. will do an implicit commit and can't be rollbacked. See http://trac.edgewall.org/changeset/9568 in particular. An example: updating the sequences in postgresql to contain the new correct value (after manually inserting rows with new ids). This is not necessary and invalid in sqllite but seemed necessary in Postgresql, so that there would not be duplicate ids. Bitten has this problem as well, IIRC. Would be nice to have a standard way to handle this, which is what http://trac.edgewall.org/ticket/8575 is about. There's an update_sequence function you could try, and if that works, this could be turned into a patch which would add corresponding dummy functions for the other backends... Another example is checking for table existence. Given there is not cross platform way to do this, the easiest I had been able to come up with was to select a row from it, and if that succeeds the table exists, otherwise it is false. We have some code that does something like that (getting a list of tables) in trac/test.py, in the reset_*_db methods. Feel free to propose a patch moving this to trac/db/util.py. Is there anyway to get a second, out of transaction connection (yes I know all the inherent dangers of this)? No, but as explained above, you don't really need this in the context of an upgrade. -- Christian Are there better backend methods to be using? Is there a way to not have a single exception on a connection invalidate the entire transaction? Do I just need to write special cased update code based on the database backend type I am connecting to? Thanks for the advice, Russ -- You received this message because you are subscribed to the Google Groups Trac Users group. To post to this group, send email to trac-us...@googlegroups.com. To unsubscribe from this group, send email to trac-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/trac-users?hl=en.
Re: [Trac] Commit changes too many file's age/revision stats
On 6/23/2010 7:08 PM, tsuraan wrote: In the source browser for the new trac 0.12, I'm having a really strange issue: in one of my repos, commits are frequently setting the age/revision statistic of file and directories that were not a part of the commit. It's not just a few files and directories, it's nearly every file and directory in the entire source tree that gets its revision changed to the latest one. svn info still gives me the correct Last Changed Rev for the affected files and directories, so I have no idea how trac is getting its wrong information for these files. I've done trac-admin repository resync to rebuild the cached data, and I still get the same bad revisions and change dates. I'm using the trac-admin changeset notification right now, but it was happening when I still had the per-page-update stuff running. The one thing about this repo that's strange is that its trunk was svn mv'd from a branch of a different project. We use the normal multi-project svn setup, where the root of svn is a bunch of projects, and under each project dir we have trunk, branches, tags. We made this new project by svn mkdir'ing the project base, svn mv'ing the branch into the project trunk, and then making the branch and tag dirs. I know that's broken our ability to view changes from before the move, so maybe it's also somehow breaking the revision/age info in the viewer? That doesn't seem like it should be related, but I really don't know what is going on. If I can provide any other info that might be helpful, I'd be happy to. It's pretty annoying having the Rev and Age columns of the source browser being broken. This sounds a lot like http://trac.edgewall.org/ticket/3470 can you have a look? -- Christian -- You received this message because you are subscribed to the Google Groups Trac Users group. To post to this group, send email to trac-us...@googlegroups.com. To unsubscribe from this group, send email to trac-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/trac-users?hl=en.
[Trac] Multiple repository changeset support (0.12)
In trac 0.12, a project can have multiple repositories. It seems like the changeset:number links only go to the main repo though, so if you have two repos configured, you'll only get changeset links working with one of them. So far I've seen two places where this is a problem: if you browse to .../changeset/number, it selects the default repository for you, and gives an error if the changeset isn't in that repository. The second place is on the wiki/tickets; a changeset link isn't clickable if the changeset isn't in the primary repository. I think the first problem could be fixed by having the base changeset request handler iterate through configured repos until it sees one where the desired changeset is present. I assume that is done somewhere in versioncontrol/web_ui/changeset.py, but I'm not having much luck actually finding the code that would need to be changed. Assuming that bit can be changed, would the second part (the dead links being replaced by no link at all) just resolve itself? I'll be hunting around in the changeset.py code for where the default repo is chosen, but if anybody has any better pointers, I'd love to hear them. 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-us...@googlegroups.com. To unsubscribe from this group, send email to trac-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/trac-users?hl=en.
Re: [Trac] Write-access to the svn repository via the source browser
Hello, On 6/23/2010 6:39 PM, Piper, Nick wrote: Dear Trac-Users list, As mentioned briefly on IRC (my username is pipern), we'd like to provide our Trac users with the ability to write to the svn repository via their web browser, through the source browser. We're interested in svn only at the moment. It's already been discussed a little over the last few years as http://trac.edgewall.org/ticket/2956 That ticket is mostly about 'Upload file', but we'd also like to have: * Rename * Delete Delete really? Then don't forget to add a Resurrect button as well ;-) * mkdir * Maybe edit for simple text files There's also an intermediate level I'm quite interested to implement myself, as I think this will ease contributions of small fixes: it's the possibility to edit the content and then produce a patch, eventually with the possibility to save it as an attachment to a ticket. Doing the upload side (or any of the other write operation you suggest below) is a bit more involved, as for doing it well it would require to extend the trac.versioncontrol.api. We'll be doing this work ourselves eventually, but it would be ideal for us if we could fund the development so that we can do it at the same time as other work. In any case, it would be nice to contribute the code back, in one form or another (plugin or patch). -- Christian -- You received this message because you are subscribed to the Google Groups Trac Users group. To post to this group, send email to trac-us...@googlegroups.com. To unsubscribe from this group, send email to trac-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/trac-users?hl=en.
[Trac] Re: Commit changes too many file's age/revision stats
This sounds a lot likehttp://trac.edgewall.org/ticket/3470can you have a look? Yeah, that looks like the same thing; the files that haven't been changed in that repo are getting the age/last changed of the latest insert, and the ones that have been changed do have correct info. Somehow I had missed the pattern, but it looks right. I wonder if this would also be fixed (in my case) by a real fix to the other question I've recently posted: the secondary repo in this configuration is the one that the files were moved from, so if trac could see the changesets for all the files that haven't been changed yet, maybe it would just fix itself. -- You received this message because you are subscribed to the Google Groups Trac Users group. To post to this group, send email to trac-us...@googlegroups.com. To unsubscribe from this group, send email to trac-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/trac-users?hl=en.
Re: [Trac] Multiple repository changeset support (0.12)
On 6/23/2010 7:42 PM, tsuraan wrote: In trac 0.12, a project can have multiple repositories. It seems like the changeset:number links only go to the main repo though, so if you have two repos configured, you'll only get changeset links working with one of them. So far I've seen two places where this is a problem: if you browse to .../changeset/number, it selects the default repository for you, and gives an error if the changeset isn't in that repository. The second place is on the wiki/tickets; a changeset link isn't clickable if the changeset isn't in the primary repository. I think the first problem could be fixed by having the base changeset request handler iterate through configured repos until it sees one where the desired changeset is present. I assume that is done somewhere in versioncontrol/web_ui/changeset.py, but I'm not having much luck actually finding the code that would need to be changed. Assuming that bit can be changed, would the second part (the dead links being replaced by no link at all) just resolve itself? I'll be hunting around in the changeset.py code for where the default repo is chosen, but if anybody has any better pointers, I'd love to hear them. Thanks! It seems you missed the intended ways to refer to changesets in the non-default repository. A good excuse for you is that apparently http://trac.edgewall.org/wiki/TracLinks#VersionControlrelatedlinks lacks a discussion of the syntax for linking to changesets... The changeset:number and /changeset/number URLs are supposed to be fully backward compatible with pre-existing 0.11 environments. If you migrate a pre-0.12 single repository environment to 0.12, nothing has changed (leaving aside the joy of backward incompatible changes in the trac.versioncontrol.api, of course ;-) ). Even if you add *more* repositories to such a pre-existing environment, the old links should still continue to work. When you have multiple repositories, you can unambiguously access anything (file or changeset) using the repository name as a prefix to the paths. Changesets support a restricted path syntax since 0.11 (or even earlier?) to only show the changes below the given path (/changeset/number/path and changeset:number/path ... and [number/path] as well), so in the case of multiple repositories, that path has to start with the repository name. Now, it's true that this design mostly came from the days when we were mainly thinking about Subversion as a backend. There, all the revisions numbers are identical between difference repositories, but of course a r100 in one repository has nothing in common with a r100 in another repository, so in this case it's necessary to qualify which repository one is talking about. Not so with Mercurial and Git, where you can be reasonably confident that e.g. a changeset f1f422a1053e in one repository would be *exactly* the same as a changeset f1f422a1053e if that one is found in another repository (a clone for example). So yes, in the latter case, it would make sense to be able to specify only the changeset number and let Trac find the appropriate changeset among the active repositories. -- Christian -- You received this message because you are subscribed to the Google Groups Trac Users group. To post to this group, send email to trac-us...@googlegroups.com. To unsubscribe from this group, send email to trac-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/trac-users?hl=en.
[Trac] Re: Multiple repository changeset support (0.12)
Now, it's true that this design mostly came from the days when we were mainly thinking about Subversion as a backend. There, all the revisions numbers are identical between difference repositories, but of course a r100 in one repository has nothing in common with a r100 in another repository, so in this case it's necessary to qualify which repository one is talking about. Not so with Mercurial and Git, where you can be reasonably confident that e.g. a changeset f1f422a1053e in one repository would be *exactly* the same as a changeset f1f422a1053e if that one is found in another repository (a clone for example). So yes, in the latter case, it would make sense to be able to specify only the changeset number and let Trac find the appropriate changeset among the active repositories. In my case, I have a trac project that's based off a new project whose trunk was svn mv'd from a branch on a different project. I loaded the wiki and tickets from the other project, and we're in the process of deleting bugs from both projects that are no longer applicable. We then have two problems with changesets, where it would be nice if trac could figure out which repo has which changeset. One is that all the old tickets refer to the changesets in the original project, which is visible to trac, but the changesets aren't clickable because the default repo doesn't have those changesets. The other issue is that history browsing is broken: trac can't walk back in history between the two repos. svn log shows the revisions correctly for the files, but since trac doesn't see the changesets in the primary repo, and it doesn't know that the secondary repo is a valid place to look, it doesn't allow me to traverse into the other repo. If there were some way I could unify the changesets in trac to allow smart choosing based off a changeset number, I would think that would help my case. I don't think what I've done is common enough to be of general use, but it would at least be nice for me. -- You received this message because you are subscribed to the Google Groups Trac Users group. To post to this group, send email to trac-us...@googlegroups.com. To unsubscribe from this group, send email to trac-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/trac-users?hl=en.
[Trac] Re: Doubts!!!
I installed Trac. I even accessed the trac browsing through my browser by typing: # Tracd-p 8080 / srv/trac/repositorios/projeto1 I went on my browser and told: http://localhost:8080 Appeared to list Project1, Project1 came in and went into the trac wiki. Now, I know some tool to access the trac integrated with svn (TortoiseSVN) because I already have it installed on client machines (windows) and the SVN server is installed on the server also has installed the trac. I'm on the road? The TracExplorer help me (for windows)? On 10 jun, 01:37, igormuzetti igormuze...@gmail.com wrote: Personally, I could install trac on Suse 11.1 by downloading the package it (. Tar.gz) through this link:http://trac.edgewall.org/wiki/TracDownload and installing the same hand, now I try to configure it and start using it. On 9 jun, 18:56, igormuzetti igormuze...@gmail.com wrote: Thanks! I managed to install Trac using the link:http://software.opensuse.org/search?q=tracbaseproject=openSUSE% 3A11.2 Has anyone heard of Trac Explorer? A plugin for integration with Subversion on windows? Not know what I should set in when SVN- Settings- Scripts-hook Inssue ...- Add- Add new server tell the directory created in C: \ track and then I click OK, then I must inform the server address track? That I do not 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-us...@googlegroups.com. To unsubscribe from this group, send email to trac-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/trac-users?hl=en.
Re: [Trac] Re: Doubts!!!
What exactly are you asking? On 24/6/2010 7:31 AM, igormuzetti wrote: I installed Trac. I even accessed the trac browsing through my browser by typing: # Tracd-p 8080 / srv/trac/repositorios/projeto1 I went on my browser and told: http://localhost:8080 Appeared to list Project1, Project1 came in and went into the trac wiki. Now, I know some tool to access the trac integrated with svn (TortoiseSVN) because I already have it installed on client machines (windows) and the SVN server is installed on the server also has installed the trac. I'm on the road? The TracExplorer help me (for windows)? On 10 jun, 01:37, igormuzettiigormuze...@gmail.com wrote: Personally, I could install trac on Suse 11.1 by downloading the package it (. Tar.gz) through this link:http://trac.edgewall.org/wiki/TracDownload and installing the same hand, now I try to configure it and start using it. On 9 jun, 18:56, igormuzettiigormuze...@gmail.com wrote: Thanks! I managed to install Trac using the link:http://software.opensuse.org/search?q=tracbaseproject=openSUSE% 3A11.2 Has anyone heard of Trac Explorer? A plugin for integration with Subversion on windows? Not know what I should set in when SVN- Settings- Scripts-hook Inssue ...- Add- Add new server tell the directory created in C: \ track and then I click OK, then I must inform the server address track? That I do not 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-us...@googlegroups.com. To unsubscribe from this group, send email to trac-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/trac-users?hl=en.
Re: [Trac] Write-access to the svn repository via the source browser
We have gone a little ways down this path of allowing constrained operations against the underlying subversion repository, primarily for copying/tagging things so far, although we also like the idea of supporting the simple edit via the web browser as well. That's worked out fairly well, although what we have done is probably a little too tied to our specific use case to release as a plugin. We'd be open to helping on a generic plugin though. One thing that we ended up doing as part of getting this working is to use svnmucc under the covers because we're often wanting to do multiple copies in a single commit and svnmucc allows us to accomplish that. We generate the input file that svnmucc will read from within Trac and then run svnmucc via a subprocess call. On Wed, Jun 23, 2010 at 10:49 AM, Christian Boos cb...@neuf.fr wrote: Hello, On 6/23/2010 6:39 PM, Piper, Nick wrote: Dear Trac-Users list, As mentioned briefly on IRC (my username is pipern), we'd like to provide our Trac users with the ability to write to the svn repository via their web browser, through the source browser. We're interested in svn only at the moment. It's already been discussed a little over the last few years as http://trac.edgewall.org/ticket/2956 That ticket is mostly about 'Upload file', but we'd also like to have: * Rename * Delete Delete really? Then don't forget to add a Resurrect button as well ;-) * mkdir * Maybe edit for simple text files There's also an intermediate level I'm quite interested to implement myself, as I think this will ease contributions of small fixes: it's the possibility to edit the content and then produce a patch, eventually with the possibility to save it as an attachment to a ticket. Doing the upload side (or any of the other write operation you suggest below) is a bit more involved, as for doing it well it would require to extend the trac.versioncontrol.api. We'll be doing this work ourselves eventually, but it would be ideal for us if we could fund the development so that we can do it at the same time as other work. In any case, it would be nice to contribute the code back, in one form or another (plugin or patch). -- Christian -- You received this message because you are subscribed to the Google Groups Trac Users group. To post to this group, send email to trac-us...@googlegroups.com. To unsubscribe from this group, send email to trac-users+unsubscr...@googlegroups.comtrac-users%2bunsubscr...@googlegroups.com . For more options, visit this group at http://groups.google.com/group/trac-users?hl=en. -- You received this message because you are subscribed to the Google Groups Trac Users group. To post to this group, send email to trac-us...@googlegroups.com. To unsubscribe from this group, send email to trac-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/trac-users?hl=en.
