Re: [Trac] how can all tickets be deleted at once?
yeap, it worked! i thought on foreign key constraints and was a bit afraid of just deleting the records. but it works proper. the result can be seen under test environment http://ec2-54-247-30-133.eu-west-1.compute.amazonaws.com/newproject/report/10 thanks a lot. -- You received this message because you are subscribed to the Google Groups "Trac Users" group. To view this discussion on the web visit https://groups.google.com/d/msg/trac-users/-/Zy46KWRxasEJ. To post to this group, send email to trac-users@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: Even though path is correct, I get an error "bash: git-receive-pack: command not found."
> > I tried to pust to the remote repository >> > Should be : I tried to PUSH to the remote repository > > >> -- You received this message because you are subscribed to the Google Groups "Trac Users" group. To view this discussion on the web visit https://groups.google.com/d/msg/trac-users/-/Iz73XNjgec4J. To post to this group, send email to trac-users@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: Even though path is correct, I get an error "bash: git-receive-pack: command not found."
>
> I described the whole process how I got this working without the errors
>> when I tried to pust to the remote repository, in the hopes it might help
>> someone else. I could have been here till the cows came in, if it hadn't
>> been for matthew Caron and his constant help.
>
>
>>
>> At the Server :
>
>
>> I restored the server boot disk from an earlier backup, and started over
>> again by getting the osx installer from the git official site.
>
> --
>
> Latest stable release (download installer)
>
> 1.7.11.1
>
> Release Notes (2012-06-21)
>
>
>> http://git-scm.com/download/mac
>
> --
>
>
>> Double clicked on the installer from the git site, installed and
>> restarted the server. After it came up to speed I checked :
>
>
>> $ which git
>
> ---> /usr/local/git/bin/git
>
>
>> Which shows a non standard path as you can see.
>
>
>> The OSX Server (Snow Leopard) configuration that I am using, has one
>> local admin user with a home directory. The other users are not local
>> users, but LDAPv3 users, so they exist for the purposes of authentication,
>> etc., and have no home directories assigned to them, which is where the
>> problem with the 'interactive shell path' vs the 'non-interactive shell
>> path' comes into play.
>
>
>> I don't know where the main system wide 'non-interactive shell path' is
>> set at, but one place I was able to set the 'non-interactive shell path' is
>> at ~/.bashrc . Since I did not have a home directory on the server, there
>> was no way to access ~/.bashrc in order to add the git path. So with this
>> problem in mind, I created a home directory for myself and added a
>> ~/.bashrc file.
>
>
>> I noticed that if I SSH into the remote server via
>
>
>> local $ ssh roscoe@192.168.1.45
>
>
>> then try to get the $PATH via :
>
>
>> server:~ roscoe $ echo $PATH
>
> --->
>> /usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/local/git/bin:/usr/X11/bin
>
>
>> the path that is returned is the 'interactive shell path'. Good so far...
>
>
>> But if instead of logging into the server via ssh, I just issue a remote
>> command (as shown below), then I get the 'non-interactive shell path',
>> which is different from the one above...
>
>
>> $ ssh roscoe@192.168.1.45 'echo $PATH;'
>
> ---> /usr/bin:/bin:/usr/sbin:/sbin
>
>
>> So with this problem in mind (this is a little repetitious, but bare with
>> me), I created a home directory for myself on the server and added a
>> ~/.bashrc file with the following contents, with the last two lines only
>> used during testing...
>
>
>> # (BEGIN) ~/.bashrc
>
> GIT_PATH=/usr/local/git/bin
>
> PATH=$PATH:${GIT_PATH}
>
> export PATH
>
>
>> echo -e "GIT_PATH = ${GIT_PATH} : path set in /Users/roscoe/.bashrc"
>
> echo -e "Called from : /Users/roscoe/.bashrc \nThe current path is :
>> ${PATH}"
>
> # (_END_) ~/.bashrc
>
>
>>
>> On the next command, I get the correct value for the 'non-interactive
>> shell path', which includes '/usr/local/git/bin', hallelujah...
>
>
>> $ ssh roscoe@192.168.1.45 'echo $PATH;'
>
> ---> /usr/bin:/bin:/usr/sbin:/sbin:/usr/local/git/bin
>
>
>> If I now SSH into the server, I notice below that the path I added in
>> ~/.bashrc does not create a duplicate entry in the 'interactive shell path'
>
>
>> SSH into the server, then check the 'interactive shell path'
>
>
>> $ ssh roscoe@192.168.1.45
>
> ---> Password:
>
>
>> server:~ roscoe $ echo $PATH
>
> --->
>> /usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/local/git/bin:/usr/X11/bin
>
>
>> server:~ roscoe $
>
>
>> Sure enough, everything appears OK now. I will test this out !
>
>
>> $ cd 'data/git/sandbox/tmp/'
>
>
>> $ pwd
>
> ---> data/git/sandbox/tmp
>
>
>> $ git status
>
> ---> # On branch master
>
> ---> nothing to commit (working directory clean)
>
>
>> Made some slight changes to the file 'projects/www/index.php' in order to
>> get a valid change in status
>
>
>> $ git status
>
> ---> # On branch master
>
> ---> # Changes not staged for commit:
>
> ---> # (use "git add ..." to update what will be committed)
>
> ---> # (use "git checkout -- ..." to discard changes in working
>> directory)
>
> ---> #
>
> ---> # modified: projects/www/index.php
>
> ---> #
>
> ---> no changes added to commit (use "git add" and/or "git commit -a")
>
>
>> $ git add projects/www/index.php
>
>
>> $ git status
>
> ---> # On branch master
>
> ---> # Changes to be committed:
>
> ---> # (use "git reset HEAD ..." to unstage)
>
> ---> #
>
> ---> # modified: projects/www/index.php
>
> ---> #
>
>
>> $ cd 'data/git/sandbox/tmp/'
>
>
>> $ git status
>
> ---> # On branch master
>
> ---> # Changes to be committed:
>
> ---> # (use "git reset HEAD ..." to unstage)
>
> ---> #
>
> ---> # modified: projects/www/index.php
>
> ---> #
>
>
>> $ git commit -m "Testing to overcome remote origin problems."
>
> ---> [master da64db1] Testing to overcome remote origin problems.
>
> ---> 1 files cha
[Trac] Re: how can all tickets be deleted at once?
Another method is using the xmlrpc plugin:
import xmlrpclib
proxyURL = ...
p = xmlrpclib.ServerProxy(proxyURL)
all_ids = p.ticket.query('id != 0')
p.ticket.delete(all_ids)
This code is not tested but I used similar snippets extensivley,
no problems ...
Greetings
Reinhard
P.S.: The xmlrpc plugin is really good for many purposes!
--
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
trac-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/trac-users?hl=en.
Re: [Trac] Re: Do people use mod_python or mod_wsgi these days, on Windows with Apache?
Hi > It would be nice if the next drop of the Bitnami trac stack included not > only Python 2.7 (instead of 2.6 which it is currently) but also had an > Apache 2.4 version. We configure Trac to work with Apache and mod_wsgi and currently there is not a mod_wsgi version for Windows for Apache 2.4. > I have a feature request for the Bitnami Trac Stack. It would be great if it > was a bit more of a"Batteries Included" version of trac with more plugins > pre-installed out of box. Most users need a bunch more plugins, including > user-management to add and create users, and their permissions, defaulting > to apache htpasswd auth backend, right out of the box. It is surprising > that user-configuration requires a Trac plugin to be added, and manually > configured, before I can even add a user to my installation.It was a lot > easier to get going than manually installing Mod_Wsgi into Apache, then > getting Trac going purely with Easy-install and setup.py, etc etc. > Yes, we are considering adding the user-management plugin. However there so many possible configuration that we will need to preconfigure it with the most used by users. But more and more users are requesting it so this is something that will add to the BitNami stack. > It might be a bit selfish of me to wish that TracMercurial and Mercurial > itself get added to the base Bitnami Trac Stack, but at least on Windows, > those are hard to get going. Regarding adding Mercurial and TracMercurial plugin in the stack, we really appreciate your feedback and requests :) our development is driven by the our users requests so we are glad of hearing your suggestions. It is already something that we would like to implement. However it is not as simple, also we may find incompatibilities if for instance if we upgrade to Python 2.7. There are not official Mercurial installer for this version of Python. Apart of that it seems that Git is getting more attraction and even it seems that it has been consider to make it the official repository for Trac 1.x. Best regards, Victoria. > Warren > > > On Tuesday, June 26, 2012 1:42:22 PM UTC-4, Dave Huang wrote: >> >> Does anyone have a solution for Apache 2.4.x on Windows with Python 2.7? >> It seems like everything mentioned so far is Apache 2.2, but I'd like to >> move to 2.4 for IPv6 support (while Apache has had IPv6 support for a long >> time, it's been disabled in the official Windows builds up until 2.4, for >> reasons that I didn't pay much attention to). I'm currently running Apache >> 2.2, Python 2.7, and mod_wsgi, and it's working well, and I'd like to stick >> with mod_wsgi. However, the mod_wsgi website doesn't seem to have any >> binaries compatible with Apache 2.4. I guess I could try compiling it >> myself... >> -- >> Name: Dave Huang > > -- > You received this message because you are subscribed to the Google Groups > "Trac Users" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/trac-users/-/7arGaoPQkk4J. > > To post to this group, send email to trac-users@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. -- 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 trac-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/trac-users?hl=en.
Re: [Trac] Re: troubleshooting tips for TracMercurial: Lost in the cracks.
On Tue, Jun 26, 2012 at 4:34 PM, Warren Postma wrote: > I replied to the group with a new subject. Sorry I should have replied to > this thread. > > My setup is: > > > Windows Server 2008 R2, > Bitnami Trac Stack (all 32 bit) with Apache 2.2, Python 2.6 > Mercurial binaries from http://mercurial.selenic.com/wiki/Download > -> https://bitbucket.org/tortoisehg/thg-winbuild/downloads/mercurial-2.2.2.win32-py2.6.exe > (installed via registry hacks) > Already replied in BitNami answers and in the subject you created in the group. > > Warren > > > On Monday, June 25, 2012 1:41:18 PM UTC-4, Christian Boos wrote: >> >> Hello Warren, >> >> >> On 6/25/2012 7:12 PM, Warren Postma wrote: >> > I've followed everything you've written at this wiki topic: >> > http://trac.edgewall.org/wiki/TracMercurial >> > >> > Currently stuck with non-working Tracmercurial plugin, on a bitnami >> > trac stack install from http://bitnami.org/stack/trac >> > on windows. >> > >> > I believe I'm hitting some of the weirdness you discuss in your wiki >> > about Mercurial and it's .pyd extensions and something >> > about the mod_wsgi environment is breaking Mercurial, or breaking >> > TracMercurial when it tries to import the hg python modules. >> > >> > The following code works fine from the bitnami-stac version of python >> > 2.6 on my system: >> > >> > from mercurial import ui, hg >> > path = 'D:/Code/wpCode/RentalPoint10-wp' >> > repo = hg.repository(ui.ui(), path) >> > print path,"Repository info:" >> > print repr(repo), "object len: ",len(repo) >> > >> > >> > The logs show that the TracMercurial .egg is being loaded by trac. >> > First I get an exception to do with *demandimport. * >> > I disabled*demandimport *in *mercurial* by replacing the real Mercurial >> > demandimport.py unit with this code: >> > >> > >> > # demandimport.py - disabled by warren. >> > >> > ''' >> > demandimport - disabled in code by warren. >> > ''' >> > >> > def enable(): >> > "does nothing" >> > pass >> > >> > def disable(): >> > "does nothing" >> > pass >> > >> > >> > >> > >> > Now Trac starts up without any errors, and yet, the Mercurial plugin >> > does not register itself. I'm not knowledgeable enough about Trac, or >> > even Apache, yet, to further debug this. >> > >> > If you could point me at another wiki topic or two to help me figure out >> > what I need to learn about Trac, or apache, or mod_wsgi to continue >> > troubleshooting, I'd appreciate it. >> > >> > My python knowledge is pretty good, mercurial knowledge as a user is >> > pretty good, and ability to read python and figure it out, is good >> > enough, I think I can figure this out. >> > >> > Maybe I will need to log a bug in the Trac project bug tracker for this >> > issue. Or maybe the issue is actually in the Bitnami stack. >> > Or maybe it's Python's weird half-support for mercurial's "Library.zip" >> > file. I'd like to find out which open source project needs a bug >> > logged, and log it. Is this a mercurial bug? Python bug? Trac? :-) >> > >> > Warren >> > >> >> First you should have sent this to trac-users, as you might just have >> caught the attention of someone who had already troubleshooted this. >> >> Then the crucial information which is missing is how did you installed >> Mercurial itself? From an installer (which one?), from source, etc. >> As you hint at a "Library.zip" I suspect the problem might be related to >> the installation itself, but you also say that from the Bitnami >> python.exe, Mercurial seems to work fine, so... before I can try to >> reproduce your issue, please provide detailed information about your >> setup. >> >> I've seen you've created a question on BitNami OSQA site, let's see what >> they have to say, but I'm fully supportive about the idea to bundle >> Mercurial in this stack, at least on Windows ;-) >> >> -- Christian >> > > On Monday, June 25, 2012 1:41:18 PM UTC-4, Christian Boos wrote: >> >> Hello Warren, >> >> >> On 6/25/2012 7:12 PM, Warren Postma wrote: >> > I've followed everything you've written at this wiki topic: >> > http://trac.edgewall.org/wiki/TracMercurial >> > >> > Currently stuck with non-working Tracmercurial plugin, on a bitnami >> > trac stack install from http://bitnami.org/stack/trac >> > on windows. >> > >> > I believe I'm hitting some of the weirdness you discuss in your wiki >> > about Mercurial and it's .pyd extensions and something >> > about the mod_wsgi environment is breaking Mercurial, or breaking >> > TracMercurial when it tries to import the hg python modules. >> > >> > The following code works fine from the bitnami-stac version of python >> > 2.6 on my system: >> > >> > from mercurial import ui, hg >> > path = 'D:/Code/wpCode/RentalPoint10-wp' >> > repo = hg.repository(ui.ui(), path) >> > print path,"Repository info:" >> > print repr(repo), "object len: ",len(repo) >> > >> > >> > The logs show that the TracMe
Re: [Trac] Re: Even though path is correct, I get an error "bash: git-receive-pack: command not found."
On 06/26/2012 09:44 PM, mbs400 wrote: Matthew, I ran these on the server as you suggested $ cd /usr/local/bin $ sudo ln -s /usr/local/git/bin/* . but the error is still there. It's possible that /usr/local/bin is not in the noninteractive login path. -- Matthew Caron, Build Engineer Sixnet, a Red Lion business | www.sixnet.com +1 (518) 877-5173 x138 office -- 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 trac-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/trac-users?hl=en.
Re: [Trac] Installing TracMercurial and its dependencies (such as Mercurial itself) into an all-32-bit bitnami trac stack on Windows 2008R2 64 bit.
Hi On Tue, Jun 26, 2012 at 4:31 PM, Warren Postma wrote: > I have Trac up and working, and the subversion integration that comes in the > Bitnami Trac Stack is working fine. Apache 2.2 and its http-auth features > are working fine. So far so good. It gets painful when I try to get > TracMercurial going. > > I've asked a question at answers.bitnami.org that contains some details on > these problems I'm having getting TracMercurial running, including the error > messages etc: > http://answers.bitnami.org/questions/5591/how-can-i-install-the-mercurial-plugin-into-the-bitnami-trac-stack > I managed to install TracMercurial plugin the BitNami Trac Stack. I have added the steps I followed in answers.bitnami.org. Basically what I did: - Registry the version of python included in the stack. ( In the BitNami forum I include the registerpython.py script that I used) - Install this version of Mercurial: https://bitbucket.org/tortoisehg/thg-winbuild/downloads/mercurial-2.2.2.win32-py2.6.exe - Download the Trac mercurial plugin for Trac 0.12 (this is very important) - Restart the servers and the plugin appears in the plugins list. > The TracMercurial wiki installation page has most of the information people > need, and I've been following it religiously. What I think I should have > done first, is ask here on Trac-Users about how I should have gotten Python > installed, as > a dependency. I tried everything on the wiki installation page, including: > > 1. Grabbing binary bits from TortoiseHG or Mercurial installations elsewhere > on my system. This causes me to run into various problems such as Python > version mismatches (Bitnami trac stack is at 2.6, recent TortoiseHG and > Mercurial-command-line binary installs on Windows, are on python 2.7). > > 2. Trying to do Easy_Install Mercurial. This gets me stuck at the famous > vcvarsall.bat problem. (such > as http://stackoverflow.com/questions/2272786/python-issueunable-to-find-vcvarsall-bat ) > > 3. What actually seemed to work (queue rejoicing) was to grab this file ( > https://bitbucket.org/tortoisehg/thg-winbuild/downloads/mercurial-2.2.2.win32-py2.6.exe > ) and run it. First it complains that it can't find the Bitnami python 2.6 > install location, because Bitnami Trac Stack doesn't create the right > registry keys. Well, a little registry hacking and we're away. > The third method is the right one and as you mention you need first to register the BitNami Python version. > Once installed, via method #3 above, the PYTHON environment seems to work, > and mercurial codebase seems to work, that is, I can execute code that > imports hg and ui from mercurial , and create an hg repo object, and do > things with it. However > I then get stuck with the errors as shown in the answers.bitnami.org > question above, which are twofold. The first error is that the > demandimport.py module fails at runtime, like this error which comes out in > the trac.log: > > File "C:\\Program Files\\BitNami Trac > Stack\\python\\lib\\site-packages\\mercurial\\demandimport.py", line 87, in > __getattribute__ > return getattr(self._module, attr) > AttributeError: 'module' object has no attribute 'directives' > > If I just get rid of the demandimport.py implementation and replace it with > two functions with pass as the function body, I get the whole thing up and > running with no more errors in my trac.log, but, yet, I have no mercurial > repository type visible in the drop-down-list of available repository types, > just subversion types. Also, if I try to change my primary repo from type > svn to type hg, I get this error message on my main Trac project webpage at > runtime: > I'm understanding that you get this error when installing the plugin. Or do you get them later when using it? Also I was yesterday playing a bit with it and I got that error. I could be because mercurial was not correcly installed or because you are not using the right version of the plugin for your Trac installation. > Then, I get mercurial modules put into Python 2.6, and I get this error: > > (Unsupported version control system "hg": DLL load failed: > The specified module could not be found.). > > Such errors do not get reproduced as python stack tracebacks in the hg.log, > so I have a broken Python 2.6 based Mercurial installation. The most > promising tip in the TracMercurial Wiki is something to do with the > library.zip that is distributed along with Mercurial. I tried to follow > the steps there (unzip library.zip and then add it to the path) but was > unable to figure out the second part of that (how do I add something to the > path, for just the mercurial parts of my python installation). > It maybe also that Python is not correctly registered and that is why Mercurial is not correctly installed (with that version of python) > So, maybe I'm close; Maybe I just need to get that "unzip library.zip" step > and "add a directory to sys.path" part worked out. Or maybe I've broken > thing
RE: [Trac] Migrating Trac?: From 0.11.4 to 12.2, from Ubuntu 10.4 to 12.04, from python2.6 to python2.7
Cooke, Mark wrote (Wednesday, June 27, 2012 12:00 PM): > > I did the transition from 0.11.4 to 0.12.2 a while ago. > > The old system was a Solaris box and the new one a SLES-10.3. > > No problems so far. Just copied the ENV to the new machine, > > ran "trac-admin upgrade" and that's it. > > Are you using the sqlite dB backend? That is stored in the env folder. yes, it's sufficient for my purposes. ;-) > Using a different dB backend such as PostgreSQL would require more work... of course ... Bye, Berny -- 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 trac-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/trac-users?hl=en.
Re: [Trac] how can all tickets be deleted at once?
On 06/27/2012 09:24 AM, christoph müller wrote:
> this process is not for the usual bugtracking. but...
>
> I'm testing trac for its ability to help in the process of building a
> classification system for information management (records
> management).
>
> trac could be an exciting tool. I like it especially the possibility to
> create sql queries.
>
> with the ticketimportplugin I read the structure into tickets.
>
> users can submit their comments.
>
> because the import gives not always the desired result, sometimes several
> attempts are necessary.
>
> deleting all tickets at once would be a great help instead of set up the trac
> project new.
>
This is a code snippet from the email2trac package (delete_spam)
if you replace Spame with '*' vertyhing should work.
def new_delete_spam(parameters):
"""
This only works for trac versions higher or equal then 0.10
"""
debug = int(parameters['debug'])
DRY_RUN = parameters['DRY_RUN']
VERBOSE = parameters['VERBOSE']
project = parameters['project']
env = Environment(project, create=0)
db = env.get_db_cnx()
cursor = db.cursor()
cursor.execute("SELECT id FROM ticket WHERE component = 'Spam';")
while 1:
row = cursor.fetchone()
if not row:
break
spam_id = row[0]
if debug or DRY_RUN or VERBOSE:
print "Deleting ticket %s" %spam_id
try:
tkt = Ticket(env, spam_id, db)
except util.TracError, detail:
print detail
continue
if DRY_RUN:
print 'DRY_RUN: tkt.delete()'
else:
tkt.delete()
--
* Bas van der Vliese-mail: b...@sara.nl *
* SARA - Academic Computing Services Amsterdam, The Netherlands *
smime.p7s
Description: S/MIME Cryptographic Signature
Re: [Trac] how can all tickets be deleted at once?
Can you directly access the database? If so, there are 3 tables that store ticket information. ticket, ticket_history and i guess ticket_custom for the custom fields. Just try a : Delete from ticket; Delete from ticket_history; Delete from ticket_custom; On Jun 27, 2012 7:16 AM, "christoph müller" wrote: > this process is not for the usual bugtracking. but... > > I'm testing trac for its ability to help in the process of building a > classification system for information management (records management). > > trac could be an exciting tool. I like it especially the possibility to > create sql queries. > > with the ticketimportplugin I read the structure into tickets. > > users can submit their comments. > > because the import gives not always the desired result, sometimes several > attempts are necessary. > > deleting all tickets at once would be a great help instead of set up the > trac project new. > > thanks for your comments. > > -- > You received this message because you are subscribed to the Google Groups > "Trac Users" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/trac-users/-/knE-obnu7-4J. > To post to this group, send email to trac-users@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. > -- 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 trac-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/trac-users?hl=en.
[Trac] how can all tickets be deleted at once?
this process is not for the usual bugtracking. but... I'm testing trac for its ability to help in the process of building a classification system for information management (records management). trac could be an exciting tool. I like it especially the possibility to create sql queries. with the ticketimportplugin I read the structure into tickets. users can submit their comments. because the import gives not always the desired result, sometimes several attempts are necessary. deleting all tickets at once would be a great help instead of set up the trac project new. thanks for your comments. -- You received this message because you are subscribed to the Google Groups "Trac Users" group. To view this discussion on the web visit https://groups.google.com/d/msg/trac-users/-/knE-obnu7-4J. To post to this group, send email to trac-users@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] Migrating Trac?: From 0.11.4 to 12.2, from Ubuntu 10.4 to 12.04, from python2.6 to python2.7
> -Original Message- > From: trac-users@googlegroups.com On Behalf Of Voelker, Bernhard > Sent: 27 June 2012 08:05 > To: trac-users@googlegroups.com > Subject: RE: [Trac] Migrating Trac?: From 0.11.4 to 12.2, > from Ubuntu 10.4 to 12.04, from python2.6 to python2.7 > > cburn wrote (Wednesday, June 27, 2012 1:00 AM): > > Greetings, > > > > If anyone has docs how to migrate a Trac environment from one > > server to another under the following conditions, I'd much > > appreciate it: > > > > From Old server (Ubuntu 10.04) to new server (Ubuntu 12.04) > > From Trac 0.11.4 to 12.2 > > From Old server running python2.6 to new server running python2.7 > > > My guess is that I need to an upgrade on the old server first, > > then do a hotcopy and copy over the upgraded environment to the > > new server. I searched for suggestions but didn't find anything > > matching my specific case. Is this even possible? > > > > Any suggestions would be much appreciated. > > I did the transition from 0.11.4 to 0.12.2 a while ago. > The old system was a Solaris box and the new one a SLES-10.3. > No problems so far. Just copied the ENV to the new machine, > ran "trac-admin upgrade" and that's it. Are you using the sqlite dB backend? That is stored in the env folder. Using a different dB backend such as PostgreSQL would require more work... ~ mark c > Have a nice day, > Berny > -- 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 trac-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/trac-users?hl=en.
RE: [Trac] Migrating Trac?: From 0.11.4 to 12.2, from Ubuntu 10.4 to 12.04, from python2.6 to python2.7
cburn wrote (Wednesday, June 27, 2012 1:00 AM): > Greetings, > > If anyone has docs how to migrate a Trac environment from one > server to another under the following conditions, I'd much > appreciate it: > > From Old server (Ubuntu 10.04) to new server (Ubuntu 12.04) > From Trac 0.11.4 to 12.2 > From Old server running python2.6 to new server running python2.7 > My guess is that I need to an upgrade on the old server first, > then do a hotcopy and copy over the upgraded environment to the > new server. I searched for suggestions but didn't find anything > matching my specific case. Is this even possible? > > Any suggestions would be much appreciated. I did the transition from 0.11.4 to 0.12.2 a while ago. The old system was a Solaris box and the new one a SLES-10.3. No problems so far. Just copied the ENV to the new machine, ran "trac-admin upgrade" and that's it. Have a nice day, Berny -- 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 trac-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/trac-users?hl=en.
