Laurent Minost wrote:
For the information, I had some problems with rpm -Uvh otrs ( on
latest 2.2.1 to 2.2.2 upgrade ) while upgrading with modified files
of the 2.2.1 rpm presents ( we customise some files to our needs)
and these files were not upgraded to the 2.2.2 version, even not
a .
Hi,
For the information, I had some problems with rpm -Uvh otrs ( on latest
2.2.1 to 2.2.2 upgrade ) while upgrading with modified files of the
2.2.1 rpm presents ( we customise some files to our needs) and these
files were not upgraded to the 2.2.2 version, even not a .rpmnew
or .rpmsave was crea
I finally got it to work by running rpm -U Then adding the --force to
it. I'm not sure why, but this seemed to install everything and now it
works.
Thank you to those that provided feedback and help.
-Jeff
Nils Breunese (Lemonbit) wrote:
Laurent Minost wrote:
Same as Nils, everything went
Laurent Minost wrote:
Same as Nils, everything went OK when I upgraded from 2.2.1 to
2.2.2 with the two SQL statements addon provided on the download
page ( done on Fedora 7 and RedHat EL4).
But as a difference, I prefer using a new OTRS install by backuping
old dirs/SQL dump then rpm -e
Laurent,
When we began using OTRS, the newest version they had for Fedora was
only supported up to Fedora Core 3. I'm interested in upgrading to
either Fedora 7 or Fedora 6. However, do you have any suggestions or
possibly even a basic summary of steps that I can do to make sure that
all exi
Jeff,
Same as Nils, everything went OK when I upgraded from 2.2.1 to 2.2.2
with the two SQL statements addon provided on the download page ( done
on Fedora 7 and RedHat EL4).
But as a difference, I prefer using a new OTRS install by backuping old
dirs/SQL dump then rpm -e old otrs package and the
Hi Nils,
I did check the escalation_response_time and escalation_solution_time
tables, they're there. When I run those commands in MySQL again, I get
an "ERROR 1060: Duplicate column name 'escalation_response_time'" and
the same for escalation_solution_time.
I did restart the processes as ne
Laurent,
I read the announcement. If you read my email I explicitly state that I
ran the script:
cat DBUpdate-to-2.2.2.sql | mysql -f -u root otrs
But, I still get the error that this is supposed to fix.
Whenever I do an update/upgrade, I do the following:
1. rpm -U filename
2. Then, I r
Jeff Shepherd wrote:
I decided to upgrade our OTRS installation on Fedora 3 from 2.2.1
to 2.2.2. After downloading the RPM, then running:
rpm -U otrs-2.2.2-01.i386.rpm
I ran the MySQL update script that you're supposed to run:
cat DBUpdate-to-2.2.2.sql | mysql -f -u root otrs
However,
Hi Jeff,
I think you need to read this announcement on top of the download page :
http://otrs.org/download/
interested links :
-
http://faq.otrs.org/otrs/public.pl?Action=PublicFAQ&CategoryID=33&ItemID=192
- http://lists.otrs.org/pipermail/announce/2007/76.html
Best regards,
Laurent MINOST
Hello,
I decided to upgrade our OTRS installation on Fedora 3 from 2.2.1
to 2.2.2. After downloading the RPM, then running:
rpm -U otrs-2.2.2-01.i386.rpm
I ran the MySQL update script that you're supposed to run:
cat DBUpdate-to-2.2.2.sql | mysql -f -u root otrs
However,
11 matches
Mail list logo
