I happened to be checking servers patch levels lately, and found some odd results on my zcm server. SPident reports that mono isn't up to date for what should be in SLES10SP2. From SPident:
Code:
SLE-10-i386-SP2         22  0.8%    596 68.7%     153   (2875 20.7%)
  - CASA  1.7.1550-0 < 1.7.1464-21.3
  - bytefx-data-mysql  2.0.1-18.1 < 1.2.2-12.20
  - ibm-data-db2  2.0.1-18.1 < 1.2.2-12.20
  - mono-basic  2.0-6.6.noarch < 1.2.2-13.13.i586
  - mono-core  2.0.1-18.1 < 1.2.2-12.20
  - mono-data  2.0.1-18.1 < 1.2.2-12.20
  - mono-data-firebird  2.0.1-18.1 < 1.2.2-12.20
  - mono-data-oracle  2.0.1-18.1 < 1.2.2-12.20
  - mono-data-postgresql  2.0.1-18.1 < 1.2.2-12.20
  - mono-data-sqlite  2.0.1-18.1 < 1.2.2-12.20
  - mono-data-sybase  2.0.1-18.1 < 1.2.2-12.20
  - mono-devel  2.0.1-18.1 < 1.2.2-12.20
  - mono-extras  2.0.1-18.1 < 1.2.2-12.20
  - mono-locale-extras  2.0.1-18.1 < 1.2.2-12.20
  - mono-nunit  2.0.1-18.1 < 1.2.2-12.20
  - mono-web  2.0.1-18.1 < 1.2.2-12.20
  - mono-winforms  2.0.1-18.1 < 1.2.2-12.20
  - translation-update-af  10.0.0-0.11 < 10.0.0-0.16
  - translation-update-gu  10.0.0-0.11 < 10.0.0-0.16
  - translation-update-mr  10.0.0-0.11 < 10.0.0-0.16
  - translation-update-xh  10.0.0-0.11 < 10.0.0-0.16
  - translation-update-zu  10.0.0-0.11 < 10.0.0-0.16
now 2.0.1-18.1 seems newer than 1.2.2-12.20 to me, and CASA's 1.7.1550-0 seems newer than 1.7.1464-21.3. SPident doesn't seem to think so; is SPident using MS Excel math here, or am I missing something? Should I ignore these, or try to bring them (down) to what SLES10SP2 wants them to be at?