Best way to upgrade Trac data from 0.12.3 to 1.4.0 (latest stable version)?

[Mr. Smith]

Here's our situation. We currently have a single Trac 0.12.3 instance hosted by RepositoryHosting.com. We want to self-host, but it's a hassle to install old Trac versions.

What is the right way to get our data from 0.12.3 upgraded by or for a Trac 1.4 installation?

I just have no idea here — we don't host the Trac ourselves.

[RjOllos]

Be sure to read through TracUpgrade:

https://trac.edgewall.org/wiki/TracUpgrade

Use the hotcopy trac-admin command to create a backup:

https://trac.edgewall.org/wiki/TracBackup 

Keep a copy of this backup around in case something goes wrong in the next steps.

You can use the environment backup created by hotcopy in your new Trac installation. I suggest first getting an empty (without your data) Trac 1.4 installation setup and working, then copying over your environment and running the upgrade steps. You'll need to decide which database and webserver you wish to use.

https://trac.edgewall.org/wiki/TracInstall

- Ryan

[Michael Klobe]

On Tuesday, March 3, 2020 at 1:18:14 PM UTC-6, RjOllos wrote:

On Tuesday, March 3, 2020 at 11:09:38 AM UTC-8, Mr. Smith wrote:

What is the right way to get our data from 0.12.3 upgraded by or for a Trac 1.4 installation?

Be sure to read through TracUpgrade:

https://trac.edgewall.org/wiki/TracUpgrade

We are in the same boat, sadly. I read through the (nice) upgrade wiki but one thing isn't clear to me: do we need to install stepwise (0.12 -> 1.0 -> 1.2 -> 1.4) or can we leap from 0.12 to 1.4 in a single bound?

Thanks!

-mck

[Ryan Ollos]

You can install Trac 1.4 and `trac-admin $env upgrade` will upgrade an environment from 0.12. No need to stepwise through each major release. 

[Jeff McKenna]

Hi mck,

My advice having gone through that attempt and spent weeks on it: I advise you aim to jump to Trac 1.2.5 first (I spent weeks trying to get all of my production extensions to work with 1.4 unsuccessfully - I wish I would have saved that effort and spent my time instead on a beach for a week ha).   Update months later: I'm still running Trac 1.2.5 and very happy with that - I am aiming to let extension developers catch up to 1.4 changes and then I will attempt the big 1.4 upgrade next calendar year on my production server.

Short story: start with the jump to 1.2.5, it is very solid and will support your enabled extensions; you may just end up staying there awhile. 

-jeff

--
You received this message because you are subscribed to the Google Groups "Trac Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to trac-users+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/trac-users/c0cea357-f391-4bc0-b9cc-b68373dc75eb%40googlegroups.com.

[Jeff McKenna]

Update: I have successfully upgraded to Trac 1.4.2 (from 1.2.5) and all
plugins today on my server instance. I want to send a thank-you to Ryan
and everyone involved in the Trac project. (for plugins, the key was to
often use the trunk version, to work with 1.4.2 Also checking the Trac
log was extremely helpful, and setting the "log_level", for debugging)

Thanks again!

-jeff



--
Jeff McKenna
MapServer Consulting and Training Services
co-founder of FOSS4G
http://gatewaygeo.com/

On 2020-05-24 9:59 a.m., Jeff McKenna wrote:
> Hi mck,
>
> My advice having gone through that attempt and spent weeks on it: I
> advise you aim to jump to Trac 1.2.5 first (I spent weeks trying to get
> all of my production extensions to work with 1.4 unsuccessfully - I wish
> I would have saved that effort and spent my time instead on a beach for
> a week ha).   Update months later: I'm still running Trac 1.2.5 and very
> happy with that - I am aiming to let extension developers catch up to
> 1.4 changes and then I will attempt the big 1.4 upgrade next calendar
> year on my production server.
>
> Short story: start with the jump to 1.2.5, it is very solid and will
> support your enabled extensions; you may just end up staying there awhile.
>
> -jeff
>
>
>
>
>
>
> On Thu, May 21, 2020 at 6:19 PM 'Michael Klobe' via Trac Users
> <trac-...@googlegroups.com <mailto:trac-...@googlegroups.com>> wrote:
>
> On Tuesday, March 3, 2020 at 1:18:14 PM UTC-6, RjOllos wrote:
>
> On Tuesday, March 3, 2020 at 11:09:38 AM UTC-8, Mr. Smith wrote:
>

> *What is the right way to get our data from 0.12.3 upgraded
> /by or for /a Trac 1.4 installation?*

>
> Be sure to read through TracUpgrade:
> https://trac.edgewall.org/wiki/TracUpgrade
> <https://trac.edgewall.org/wiki/TracUpgrade>
>
>
> We are in the same boat, sadly. I read through the (nice) upgrade
> wiki but one thing isn't clear to me: do we need to install stepwise
> (0.12 -> 1.0 -> 1.2 -> 1.4) or can we leap from 0.12 to 1.4 in a
> single bound?
>
> Thanks!
> -mck
>
> --
> You received this message because you are subscribed to the Google
> Groups "Trac Users" group.
> To unsubscribe from this group and stop receiving emails from it,
> send an email to trac-users+...@googlegroups.com

> <mailto:trac-users+...@googlegroups.com>.

> To view this discussion on the web visit
> https://groups.google.com/d/msgid/trac-users/c0cea357-f391-4bc0-b9cc-b68373dc75eb%40googlegroups.com

> <https://groups.google.com/d/msgid/trac-users/c0cea357-f391-4bc0-b9cc-b68373dc75eb%40googlegroups.com?utm_medium=email&utm_source=footer>.
>