Ticket #2899 (closed: fixed)

Opened 9 years ago

Last modified 5 years ago

New Windows installs are not recognised as a new version of the same program

Reported by: Martyn Gigg Owned by: Martyn Gigg
Priority: blocker Milestone: Iteration 28
Component: Mantid Keywords:
Cc: Blocked By:
Blocking: Tester: Roman Tolchenov

Description

Since some changes with MantidVersion each time you install a version on windows it gets a completely separate entry in the add/remove programs list, e.g.

  • Mantid 1.28.11164 (Tue, 03 May 2011)
  • Mantid 1.28.11179 (Tue, 03 May 2011)

etc

It needs to go back to being the same program with a different version.

It is most probably the date that is confusing the version comparison

Change History

comment:1 Changed 9 years ago by Martyn Gigg

  • Status changed from new to accepted

comment:2 Changed 9 years ago by Martyn Gigg

  • Status changed from accepted to verify
  • Resolution set to fixed

(In [11211]) Fixes #2899. Remove the date portion from the version string in the Windows installer otherwise the version comparison gets confused when trying to upgrade it.

comment:3 Changed 9 years ago by Roman Tolchenov

  • Status changed from verify to verifying
  • Tester set to Roman Tolchenov

comment:4 Changed 9 years ago by Roman Tolchenov

  • Status changed from verifying to closed

It works (at least on a 64 bit) when version strings are different. But it may not work if the msi files are different but the version strings are the same. This can happen for svn checkins to directories other than Code

comment:5 Changed 5 years ago by Stuart Campbell

This ticket has been transferred to github issue ​3746

Note: See TracTickets for help on using tickets.