RE: [Trac] Upgrading from Trac 0.11 to Trac 1.0

[Jiang, Victor (Ext)]

Hi All,

 

I want to use Trac to bind SVN, I installed the pysvn,  it did not work. I cannot get subversion-python package(OS is RHEL5.4), can someone provide me the package!

 

 

 

 

Best regards,

 

Victor Jiang

 

 

From: trac-...@googlegroups.com [mailto:trac-...@googlegroups.com] On Behalf Of Mete Kural
Sent: Friday, September 28, 2012 7:28 AM
To: trac-...@googlegroups.com
Subject: [Trac] Upgrading from Trac 0.11 to Trac 1.0

 

Hello All,

 

In the Trac Upgrade documentation, I saw the steps specific to a given Trac version section: http://trac.edgewall.org/wiki/TracUpgrade#a6.StepsspecifictoagivenTracversion

There is a section titled "Upgrading from Trac 0.11 to Trac 0.12" and a section titled "Upgrading from Trac 0.12 to Trac 1.0". I was wondering if this had any implication that it's better to first upgrade from 0.11 to 0.12 and then upgrade from 0.12 to 1.0 in two steps. Is it better that I do that rather than upgrading from 0.11 to 1.0 directly, or does it not matter at all?

 

Meanwhile, my full Trac System Information is:

 

Trac:	0.11
Python:	2.5.2 (r252:60911, Mar 27 2008, 17:57:18) [MSC v.1310 32 bit (Intel)]
setuptools:	0.6c8
SQLite:	3.3.4
pysqlite:	2.3.2
Genshi:	0.5.1
Subversion:	1.5.0 (r31699)
jQuery:	1.2.3

 

Thanks in advance!
-Mete

--
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/-/dHDYiGR_jw4J.
To post to this group, send email to trac-...@googlegroups.com.
To unsubscribe from this group, send email to trac-users+...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/trac-users?hl=en.

[Steffen Hoffmann]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 28.09.2012 11:05, Jiang, Victor (Ext) wrote:
> Hi All,
>
>
>
> I want to use Trac to bind SVN, I installed the pysvn, it did not work.
> I cannot get subversion-python package(OS is RHEL5.4), can someone
> provide me the package!

Did you care to read Trac wiki docs? They actually explain a lot, i.e.
they explicitly state:

Note that Trac doesn't use ​PySVN, neither does it work yet with the
newer ctype-style bindings.

Why did you even try?


If you can't find you own distro's packages, how about Bitnami's Trac
stack [2]:

Include all the dependencies necessary to run the application, such as
Apache, SQLite, Python and Subversion.

Once I tried it on Windows - very convenient to have it just setup in a
few minutes.

Steffen Hoffmann


[1] http://trac.edgewall.org/wiki/TracInstall#MandatoryDependencies
[2] http://bitnami.org/stack/trac
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAlBlycIACgkQ31DJeiZFuHfeEACeOrB8+ZKyO/CK8m61VLHphTFm
dIIAnj0VeXrscZ/Si3KaIk476tO0X/xD
=NsCA
-----END PGP SIGNATURE-----

[Steffen Hoffmann]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 28.09.2012 01:28, Mete Kural wrote:
> Is it better that I do that rather than upgrading from 0.11 to 1.0
> directly, or does it not matter at all?

Doesn't matter. Technically you're doing the same with the two-step as
well as the single-step approach.

Follow the documentation and read both migration documents then.

Steffen Hoffmann

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAlBlyhkACgkQ31DJeiZFuHeBzwCfboliLu6zBLsSJ9zrOFTS61z8
aD8AniquadfdGzEAZmQs7vYu3TGCXM3D
=PvI2
-----END PGP SIGNATURE-----

[Mete Kural]

Hello All,

Does anyone have any input they can provide regarding my original question:

In the Trac Upgrade documentation, I saw the steps specific to a given Trac version section: http://trac.edgewall.org/wiki/TracUpgrade#a6.StepsspecifictoagivenTracversion

There is a section titled "Upgrading from Trac 0.11 to Trac 0.12" and a section titled "Upgrading from Trac 0.12 to Trac 1.0". I was wondering if this had any implication that it's better to first upgrade from 0.11 to 0.12 and then upgrade from 0.12 to 1.0 in two steps. Is it better that I do that rather than upgrading from 0.11 to 1.0 directly, or does it not matter at all?

Meanwhile, my full Trac System Information is:

Trac:	0.11
Python:	2.5.2 (r252:60911, Mar 27 2008, 17:57:18) [MSC v.1310 32 bit (Intel)]
setuptools:	0.6c8
SQLite:	3.3.4
pysqlite:	2.3.2
Genshi:	0.5.1
Subversion:	1.5.0 (r31699)
jQuery:	1.2.3

Thanks a bunch!
-Mete

[Steffen Hoffmann]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 28.09.2012 18:14, Mete Kural wrote:
> Hello All,
>
> Does anyone have any input they can provide regarding my original question:

What more do you expect? How could it be more clear?

I already told you, that it's technically equal. Doing two steps saves
you nothing, so I would always do it in one and follow both advisories,
0.11 --> 0.12 and 0.12 --> 1.0 . It's not more complicated than that.

Of course you should check any Trac plugin you might use for
compatibility with Trac 1.0 before. If you have no working backup of
your Trac environments, and you run into issues during the upgrade,
there's no sane way to downgrade - so you'll be possibly doomed. Read
the docs as a whole, and follow advise given there.

Steffen Hoffmann
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAlBl3wUACgkQ31DJeiZFuHdqTwCfXXHT0BN15PAD4s5YVQ0VA5kN
+foAniuuqgvCjB8zkg2TwpPAbnMdN6DS
=/GIs
-----END PGP SIGNATURE-----

[Mete Kural]

Hello Stefan,

I'm very sorry, I missed that email from you. The other issue being
mixed in that thread threw me off and I wasn't careful enough to see
that your email was related to my issue. I apologize.

OK, I understand now. I will go straight from 0.11 to 1.0 then and
consider both advisories in 0.11 -> 0.12 and 0.12 to 1.0.

Regarding your comment on the Trac plugins, I only have that Trac
testing plugin that adds a "TestManagement" tab in the Trac UI. I hope
it will not have any issues with 1.0.

Thanks,
Mete

[RjOllos]

On Friday, September 28, 2012 10:56:16 AM UTC-7, Mete Kural wrote:

Regarding your comment on the Trac plugins, I only have that Trac 
testing plugin that adds a "TestManagement" tab in the Trac UI. I hope
it will not have any issues with 1.0.

Is that TestManagerForTrac (1)? Well, regardless of what plugin it is, if you value the functionality of the plugin, it is always advisable to review open tickets, such as (2), and see if there will be a any showstoppers for you. I have a "staging" instance of Trac alongside my production instance and upgrade the staging instance to test out plugins first.

(1) http://trac-hacks.org/wiki/TestManagerForTracPlugin 

(2) http://trac-hacks.org/report/9?COMPONENT=TestManagerForTracPlugin

[Jai]

All,

 

I need help in sorting the below issue.

 

after coping mysql data from old server running trac 0.11 to new server running Trac 1.0, I get below error after running the command

 

[root@svnserver ]# trac-admin /usr/local/Trac-projects/XXX upgrade --no-backup

The upgrade failed. Please fix the issue and try again.

OperationalError: (1050, "Table 'repository' already exists")

 

And again when we run the same command its gives ;-

 

[root@svnserver Trac-projects]# trac-admin /usr/local/Trac-projects/XXX upgrade --no-backup

The upgrade failed. Please fix the issue and try again.

 

ProgrammingError: (1146, "Table 'XXXTrac.revision' doesn't exist")

 

 

Any help !!!

[Cooke, Mark]

> -----Original Message-----
> From: trac-...@googlegroups.com
> [mailto:trac-...@googlegroups.com] On Behalf Of Jai
> Sent: 10 October 2012 12:28
> To: trac-...@googlegroups.com
> Subject: [Trac] Re: Upgrading from Trac 0.11 to Trac 1.0
>
> All,
>
> I need help in sorting the below issue.
>
> after coping mysql data from old server running trac 0.11 to
> new server running Trac 1.0, I get below error after running
> the command
>
> [root@svnserver ]# trac-admin /usr/local/Trac-projects/XXX
> upgrade --no-backup

...so you are on a *nix flavour of some sort?

> The upgrade failed. Please fix the issue and try again.
>
> OperationalError: (1050, "Table 'repository' already exists")
>
> And again when we run the same command its gives ;-
>
> [root@svnserver Trac-projects]# trac-admin
> /usr/local/Trac-projects/XXX upgrade --no-backup
>
> The upgrade failed. Please fix the issue and try again.
>
> ProgrammingError: (1146, "Table 'XXXTrac.revision' doesn't exist")
>
> Any help !!!

Hmm, if you just start Trac does it complain that the environment needs upgrading?

Have you tested that a clean new environment works OK?

Do you have any plugins installed? Did they create any tables? Do you have versions that work for Trac 1.0 installed so that they can also update their environments?

~ mark c

[Jai Prakash Sharma]

I'm running CentOS 6.3 64 bit with Python 2.6 & MySQL 5.5.

It's a new clean environment. I have in total 8 projects and all 7 projects got upgraded and working fine. I'm facing this problem with one project. I see in the problematic project there is one additional folder called attachment, which is not there in any other project.

Thanks & Regards,

Jai

--
You received this message because you are subscribed to the Google Groups "Trac Users" group.

To post to this group, send email to trac-...@googlegroups.com.
To unsubscribe from this group, send email to trac-users+...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/trac-users?hl=en.

DISCLAIMER
This email is intended only for the person or the entity to whom it is addressed and may contain information which is confidential and privileged. Any review, retransmission, dissemination or any other use of the said information by person or entities other than intended recipient is unauthorized and prohibited. If you are not the intended recipient, please delete this email and contact the sender.

[RjOllos]

On Wednesday, October 10, 2012 5:59:19 AM UTC-7, Jai Prakash Sharma wrote:

I'm running CentOS 6.3 64 bit with Python 2.6 & MySQL 5.5.

It's a new clean environment. I have in total 8 projects and all 7 projects got upgraded and working fine. I'm facing this problem with one project. I see in the problematic project there is one additional folder called attachment, which is not there in any other project.

You may want to take a read through http://trac.edgewall.org/wiki/TracUpgrade#to1.0, which points out some problems related to attachments that can occur during the upgrade. 

[Steffen Hoffmann]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 26.10.2012 23:24, RjOllos wrote:
> one additional folder called attachment

- From own upgrade experience I know, that the (old) attachment folder is
not cleared, if you had files in it, that were not registered with Trac
(attachment Trac db table). I had ScreenshotsPlugin [1] configured to
put its files in, so on final upgrade to 1.0 the upgrade script
complained about not migrate-able data in the path that prevented folder
removal, and I was advised to have a look and remove it manually to
clean the situation. I moved screenshots folder to new location below
files, deleted non-empty attachment folder - done.

Steffen Hoffmann


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

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAlCLcl0ACgkQ31DJeiZFuHdUOQCgmP8xfUs3gIpSRzDOYCM6HG0z
FawAoILO4PD8OGnHtLXx5onpQd46Xxrg
=FwRM
-----END PGP SIGNATURE-----