Bug 115811 - Resin startup doesn't sort version numbers correctly
Summary: Resin startup doesn't sort version numbers correctly
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Red Hat Web Application Framework
Classification: Retired
Component: installation
Version: nightly
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Dennis Gregorovic
QA Contact: Jon Orris
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2004-02-16 11:31 UTC by Daniel Berrangé
Modified: 2007-04-18 17:03 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2005-03-17 16:55:04 UTC
Embargoed:


Attachments (Terms of Use)

Description Daniel Berrangé 2004-02-16 11:31:08 UTC
Description of problem:
[root@camden root]# ls /opt/resin 
2.1.10  2.1.20  2.1.300  2.1.4  2.1.40
[root@camden root]# /bin/ls -d /opt/resin/* | sort -r | head -1
/opt/resin/2.1.40
[root@camden root]# 

It should have picked '2.1.300'.

It needs to be doing a numeric sort on the 3rd field, and only look
for files named 2.1.x 

Something like the following adapted code should work:

/bin/ls -d /opt/resin/2.1.* | sort -t . -k 3 -n -r | head -1

This is also relevant for tomcat.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Dennis Gregorovic 2004-02-23 21:33:27 UTC
@40729

Comment 2 Dennis Gregorovic 2005-03-17 16:55:04 UTC
closing old tickets


Note You need to log in before you can comment on or make changes to this bug.