[wpkg-users] Issues with publishing Java 8u102 over wpkg

[Steve Kersley]

That's nasty.  Well, hopefully my incorrect guess didn't cause anyone any problems - thanks for researching and responding...

This change also breaks our (messy and kludgy) uninstall method, which loops through previous version numbers attempting to uninstall any that are still installed.  Should be able to tweak it though to use a different ID for versions >99.

Steve.

-----Original Message-----
From: Malte Starostik [mailto:wpkg at xodtsoq.de] 
Sent: 12 September 2016 12:37
To: wpkg-users at lists.wpkg.org
Cc: Steve Kersley <steve.kersley at keble.ox.ac.uk>; Mendim Uka <Mendim.Uka at esag.ch>
Subject: Re: [wpkg-users] Issues with publishing Java 8u102 over wpkg

On Monday 12 September 2016 10:28:45 Steve Kersley wrote:
> Just a guess, but as the SHORTUPDATEVER has rolled over to 3 digits, I 
> assume that the ID generated is wrong.  Try removing the zero from in 
> front of the variable:
> 
> <check type="uninstall" condition="exists"
> path="{26A24AE4-039D-4CA4-87B4-2F83218%shortupdatever%F0}"
> 

In fact, someone at Oracle was apparently having a rather misanthropic day and went the way of maximum surprise:

{26A24AE4-039D-4CA4-87B4-2F83218092F0} 8.92 32 bit and {26A24AE4-039D-4CA4-87B4-2F86418092F0} 8.92 64 bit turn to {26A24AE4-039D-4CA4-87B4-2F32180102F0} 8.102 32 bit and {26A24AE4-039D-4CA4-87B4-2F64180102F0} 8.102 64 bit

Note how -2F8 in the UUID's last part became just -2F

They did *not* go from 092F0 to 102F0 in the end. Nor 092 to 0A2 to kind of make use of the hexadecimal charset.  Nah.  Gotta really surprise packagers instead.

Kind regards,
Malte