tracd not working after OS upgrade from rhel 6.10 to 7.6

[Rakesh kumar]

HI,

We have upgraded the OS from rhel 6.10 to 7.6.

Not abe to start the trac, Its giving the error while starting the trac

Traceback (most recent call last):
  File "/bin/tracd", line 5, in <module>
    from pkg_resources import load_entry_point
  File "/usr/lib/python2.7/site-packages/pkg_resources.py", line 3007, in <module>
    working_set.require(__requires__)
  File "/usr/lib/python2.7/site-packages/pkg_resources.py", line 728, in require
    needed = self.resolve(parse_requirements(requirements))
  File "/usr/lib/python2.7/site-packages/pkg_resources.py", line 626, in resolve
    raise DistributionNotFound(req)
pkg_resources.DistributionNotFound: Trac==1.2.2

Thanks,

Rakesh kumar

[RjOllos]

Did you install Trac using the RedHat package manager, or using easy_install/pip?

- Ryan 

[Ryan Ollos]

Either way, you may want to just reinstall

* Uninstall/reinstall using package manager, or

* $ pip uninstall Trac

  $ pip install Trac==1.2.2

If the latter, consider installing the latest 1.2.x, which is 1.2.5.

https://trac.edgewall.org/wiki/TracDownload#Trac12StableRelease

- Ryan

[Jeff McKenna]

+1 for Ryan's recommendation for using Trac 1.2.5 now in production.

I spent a few weeks of effort trying to upgrade my production Trac instances to 1.4.1 (and of course saw the many users reporting issues with that upgrade, and the response of 'see installation guide'), but in the end I found that the most-recent I could upgrade to and still have all plugins working in production is the 1.2.5 release.  

Hope that helps someone else.

-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/CA%2BBGpn88JoLG%3D6bSbLen6YH%3D6rfxzzGY8sBF2DgrTqUxqbdWwg%40mail.gmail.com.

[RjOllos]

On Tuesday, March 3, 2020 at 9:59:29 AM UTC-8, Jeff McKenna wrote:

+1 for Ryan's recommendation for using Trac 1.2.5 now in production.

I spent a few weeks of effort trying to upgrade my production Trac instances to 1.4.1 (and of course saw the many users reporting issues with that upgrade, and the response of 'see installation guide'), but in the end I found that the most-recent I could upgrade to and still have all plugins working in production is the 1.2.5 release. 

What issues did you see reported with the upgrade? I haven't noticed more issues reported that we've encountered with previous major releases, and many issues are due to users not following the upgrade procedure describe on TracUpgrade.

There are some plugin compatibility issues, but that's separate from the Trac upgrade. Which plugins are you using that aren't compatible?

 

To unsubscribe from this group and stop receiving emails from it, send an email to trac-users+unsubscribe@googlegroups.com.

[Jun Omae]

Hi,

On Sat, Feb 29, 2020 at 2:19 AM Rakesh kumar <rakes...@gmail.com> wrote:
>
> HI,
>
> We have upgraded the OS from rhel 6.10 to 7.6.
>
> Not abe to start the trac, Its giving the error while starting the trac
>
> Traceback (most recent call last):
> File "/bin/tracd", line 5, in <module>

^^^^^^^^^^

tracd is normally installed to /usr/bin/tracd (or ${prefix}/bin/tracd
if virtualenv).
Otherwise, /usr/sbin/tracd is located if trac rpm package is used.
(refs. https://centos.pkgs.org/7/epel-x86_64/trac-1.0.13-1.el7.noarch.rpm.html)

I guess that you're manually copied tracd to /bin directory.

Instead, remove /bin/tracd file and try to use /usr/bin/tracd.

--
Jun Omae <jun...@gmail.com> (大前 潤)

[Jeff McKenna]

Hi Ryan,

I tried to explain here that what I found is that the latest release that supports all plugins is 1.2.5 from my testing.   Indeed there are plugin issues with 1.4.1 which is my point, and why I recommend to others to go with 1.2.5 (and save yourself 2 weeks of effort, spend that time on a beach instead) until the plugins catchup to 1.4.x

-jeff

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/CA%2BBGpn88JoLG%3D6bSbLen6YH%3D6rfxzzGY8sBF2DgrTqUxqbdWwg%40mail.gmail.com.

--

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/ccc9b1aa-7917-4108-ae4e-29cd4887b2b8%40googlegroups.com.

[Ryan Ollos]

On Tue, Mar 3, 2020 at 3:10 PM Jeff McKenna <jeffm...@gmail.com> wrote:

Hi Ryan,

I tried to explain here that what I found is that the latest release that supports all plugins is 1.2.5 from my testing.   Indeed there are plugin issues with 1.4.1 which is my point, and why I recommend to others to go with 1.2.5 (and save yourself 2 weeks of effort, spend that time on a beach instead) until the plugins catchup to 1.4.x

-jeff

Understood. I was asking which plugins you are using that aren't compatible with 1.4.