Re: Issue tracker not working

Hello Gianluca:

In message <[email protected]>,
Gianluca Ferrazzano writes:
>I took a look and we are using the classic template and I am working on 
>a copy at the moment

Good. I won't be available tomorrow, and wanted to make sure that this
wasn't a production issue.

>We did the Python 2-3 changes first to install the 2.2.0 roundup 
>version, but I went from 1.3.3 to 2.2.0 as I thought the reason it was 
>not working was because it was not fully updated.

Once you have done the 2-3 changes, only 2.2.0 or newer will work.
Anything earlier will fail to run.

How are you running Roundup?

  * stand alone server?
  * under another web server? which one: nginx, apache, lighttpd, other?
  * are you using a wsgi gateway like uwsgi or gnuicorn?
  * mod_python? (not suggested)
  * some other way?

There may be something in the upgrade path that we missed for a
particular deployment method. It's unlikely that the problem you have
is dependent on how you run Roundup, but this is an odd error inside
of Roundup so....

For testing purposes, you can use the stand alone server
(roundup-server).

Also while we are at it, what OS are you using?

It looks like you are using python 3.7 which is a bit old.

Is /usr/local/lib/python3.7 a Python virtual environment used for
installing Roundup? If not please create a virtual environment to
isolate your system Python install from the Roundup install.

>I am trying to access the home page, searching for specific issue 
>numbers works fine

Good.

>/tracker/status and /tracker/index?@columns=title both dont work

Hmm, you get the same traceback? Neither of those should be calling
reldate.

>i dont get an error when running, roundup-admin -i 
>tracker/home/directory display issue1

Good.

>I see so the problem could be with reldate, ok I will take a look and 
>see if theres anything I can do

Well the problem isn't with reldate. Reldate is getting an invalid
argument and complaining. The problem is that invalid value
(self._value).

I hate to suggest it, but at this point I would reset your
test copy to production. Then try the upgrade in stages:

   1.3.3 to 1.5.0 (using Python 2)
   1.5.0 to 1.6.1 (using Python 2)
   1.6.1 to 2.0.0 (and convert to Python 3)
   2.0.0 to 2.3.0 (Python 3 (2.3.0 was release a couple of weeks ago))

and test after every stage. It's possible the upgrade directions are
missing something that is needed in your environment. They could also
be unclear and lead you down the wrong path.

Have a great day.

--
				-- rouilj
John Rouillard
===========================================================================
My employers don't acknowledge my existence much less my opinions.