Old installers don't install

[peter-devoil]

Several people have had issues trying to install old versions of apsim on new computers. The main issue seems be that VS runtimes refuse to install, failing to see that VS2019 includes previous versions.

It would be useful to be able to have zip files for each version without the installer. For reference, the old svn revision numbers are:

[zur003]

It looks like there is a sort of workaround for the old installers. Run the installer from a command line, but add a "/C" option. This will extract ApsimSetup.msi, Install.bat, and setup.exe into a designated folder. What "normally" happens is Install.bat runs setup.exe, which in turn does the check for support libraries, then runs ApsimSetup.msi. However, you can just run AspimSetup.msi directly and thereby bypass the check for the support libraries.

[peter-devoil]

@hol430 - are the installers on apsim.info, or on the old bob ftp area? .msi files would be easier for users than zip files..

[hol430]

Neither - we rescued them from Bob before he was decommissioned but haven't uploaded them to apsim.info yet, as the server doesn't have nearly enough disk space. We still have the installers for the major version number increments - 7.0, 7.1, 7.2, etc.

[peter-devoil]

Just links to the released versions would be good for the moment.

[hol430]

We also have installers for 6.0 and 6.1 - do you know the release date and revision numbers for these versions?

Version Name	Version Number	Release Date	Download Link
Merge in changes to maize validation set	Apsim7.10-r4192	2020-04-23	Windows x86_64
APSIM 7.10	Apsim7.10-r4159	2018-04-01	Windows x86_64
APSIM 7.9	Apsim7.9-r4047	2017-06-14	Windows x86_64
APSIM 7.8	Apsim7.8-r3868	2016-03-29	Windows x86_64
APSIM 7.7	Apsim7.7-r3616	2014-12-16	Windows x86_64
APSIM 7.6	Apsim7.6-r3377	2014-03-24	Windows x86_64
APSIM 7.5	Apsim7.5-r3009	2013-04-15	Windows x86_64
APSIM 7.4	Apsim7.4-r2287	2012-02-13	Windows x86_64
APSIM 7.3	Apsim7.3-r1388	2011-02-27	Windows x86_64
APSIM 7.2	Apsim7.2-r1017	2010-08-23	Windows x86_64
APSIM 7.1	Apsim7.1-r700	2009-11-14	Windows x86_64
APSIM 7.0	Apsim7.0-r402	2009-04-26	Windows x86_64

[peter-devoil]

They're in an older svn tree (http://apsrunet.apsim.info/svn/development) that you may not have brought over to git - so the r numbers are incomparable.

From what I can tell, the release dates are 15/5/2008 for 6.1, and 27/3/2008 for 6.0

[hol430]

Ah ok, thanks for that. Out of interest, what made you switch svn trees?

[peter-devoil]

I think the old directory structure had become too cumbersome - too many subdirs that were organised the wrong way for new tools (like "makefiles").

[zur003]

I think the old point releases really ought to be archived on data.csiro.au, where they can be given a "permanent" URI.

[hol430]

What's the process for getting our stuff on data.csiro.au?

[hol430]

@zur003 for some reason running the installer with /C argument just runs the installer as normal. If I run with /?, I get a list of arguments which doesn't include /C. I'm using Apsim7.10-r4193.apsimsetup.exe - does this only work with the older installers?

[zur003]

Yes, only the older ones prior to the switch to InnoSetup (late 2017?) will honour the /C argument.

[zur003]

If you do need to unpack the InnoSetup installers, there are a couple of utilities available for that (innounp, innoextract).

[hol430]

Do people have this problem with the newer installers? Just wondering if it's worth providing .msi files alongside every installer we create.

[peter-devoil]

@zur003 - regarding archival - I kept a CD of the old svn repository after we stopped using it. Does anyone even have a cupboard I can put it in?

[zur003]

@peter-devoil CDs have had a pretty long useful life, but it's going to get progressively harder to find drives as the years go by. I suggest we consider archiving (some of) this stuff on the CSIRO data store, along with copies of the point-release installers.

[peter-devoil]

Here's the link - 900Mb.

[zur003]

@peter-devoil @hol353 - I'm looking into putting this stuff on the CSIRO data portal. What are the IP considerations? Should access be public or restricted? My current assumption is that the old installers should be made publicly accessible, but I'm less sure about the SVN repository of source code. And what about non-CSIRO members of the Apsim Consortium? Are they OK with this? Is this something the Reference Panel needs to consider? Should I ignore all the IP niceties and plunge ahead?

[hol353]

All IP for releases and repo belongs to the APSIM Initiative - not CSIRO. Don't know if that impacts CSIRO's ability to store this on CSIRO storage. My view is that all historical releases and repo should be publically available given that the current repo is on GitHub and all current releases are publically available. @sarahcleary what do you think?

[hol353]

It's actually probably just tidier if we buy a bit more space on apsim-dev (which we have to do anyway) and put it there. Keeps all AI stuff together rather than scattered over different computers and storage locations. We're only talking about 1Gb - tiny.

[hol430]

Well we have ~250GB of legacy installers on Neil's hard drive which need to go somewhere.

[sarahcleary]

@hol353 - in answer to your question above. I can't see any issues with making them publicly available - given they are old releases but only to current licensees. Please include a note making it clear that these are only accessible if you have a current APSIM Licence.

[peter-devoil]

I suspect this issue is resolved now - the installers are available on the upgrade page; has anybody uploaded the "old stuff" to the csiro data store?

[hol430]

As far as I know, it's all still sitting on a disk in toowoomba. @zur003 what is the process for getting these old files up onto data.csiro.au?

[zur003]

The process for getting data on the CSIRO Data Access Portal is described at https://confluence.csiro.au/display/dap/Deposit+and+Manage+Data. I never quite got around to doing this, partly because I was uncertain exactly what needed to be archived: just the old point releases or some to all of the other builds?

[her123]

I could take a look at it.

[her123]

Published at https://data.csiro.au/dap/landingpage?pid=csiro:45020 Just waiting for final step.

[her123]

This is the link for the collection https://doi.org/10.25919/5eeb2a56eced7 @hol353 Can you check that I have selected the correct license (GPL) Choices are:

*CSIRO Binary Software Licence The Software is licensed under a standard CSIRO Binary Software Licence, subject to any additional conditions notified as part ...

*CSIRO Open Source Software Licence (Based on MIT/BSD Open Source Licence) This licence releases the Software as 'open source'. It reflects the terms of the BSD/MIT open source software licences, with...

*GPLv3 Licence with CSIRO Disclaimer This licence releases the Software as 'open source' under the GPLv3 licence, with a specific CSIRO liability disclaimer includ...

Also: The attribution statement. Should this include more people? If so, them who?

[hol353]

Tagging @sarahcleary FYI. In reality APSIM is released under the APSIM Initiative license not GPL. Can we change this on the CSIRO Data Access Portal?

@her123 Can we add additional releases to the data access portal? Would have been nice to include all releases back to 1.6 which I have somewhere.

[hol353]

Also, the attribution statement should just say APSIM Initiative not me and Neil.

[her123]

The licensing only has those three options. It could be clarified in some other comments. Yes. Other versions can be added. I'll fix the attribution statement.

[hol353]

I thought once it was published it was made readonly.

[her123]

I can edit but because it's public it needs re-approval to publish.

[her123]

I can also assign to someone else to make edits.

[zur003]

@her123 - Thanks for taking this on.

[sarahcleary]

thanks @her123 and @hol353. Will look into it the licensing conditions of the CSIRO Data Access Portal. Needs to ensure that the licence conditions of the non-commercial APSIM Licence overrides these T&Cs.

[sarahcleary]

This may be more appropriate: https://confluence.csiro.au/pages/viewpage.action?pageId=267124796 - CSIRO Open Source Software Licence (Based on MIT/BSD Open Source Licence)

The Software may contain third party material obtained by CSIRO under licence. Your rights to such material as part of the Software under this agreement is subject to any separate licence terms identified by CSIRO as part of the Software release - including as part of the Supplementary Licence, or as a separate file.

[sarahcleary]

@her123 - Just for clarity - what is the benefit of putting these files on CSIRO's DAP?

[her123]

@sarahcleary - There were suggestions that this makes it easier for people to find old versions and provides a doi reference for them.

[hol353]

I'm not sure that they are easier to find. It is more intuitive to find them on www.apsim.info. The only tiny advantage I can see is that you get a DOI and a permanent URL. Do we really want them on the CSIRO DAP?

[sarahcleary]

@her123 - if we are going to utilise CSIRO DAP - I will need to approach CSIRO contracts and find out if it's possible. So, will let you, @hol353, @peter-devoil etc.. discuss if this is the best technical solution. Given the time of year (EOFY), contracts will be busy so will take a week or two to get an answer, I suspect.

[zur003]

Hi Neville,

It looks a bit like Pete was pointing only to the old svn archives, not the installers. I don’t think we’d want the source on the data store. The git repository already includes the revision history back to April 2009. Perhaps Pete was looking for a better way to archive the source revisions from before then, but I don’t think data.csiro.au is the place for that.

Eric Zurcher Software Developer | Grazplan Project | CSIRO Eric.Zurcher@csiro.aumailto:Eric.Zurcher@csiro.au | 02 6246 5143 | 0415 631 421

From: Neville notifications@github.com Sent: Friday, 19 June 2020 9:41 AM To: APSIMInitiative/APSIMClassic APSIMClassic@noreply.github.com Cc: Zurcher, Eric (A&F, Black Mountain) Eric.Zurcher@csiro.au; Mention mention@noreply.github.com Subject: Re: [APSIMInitiative/APSIMClassic] Old installers don't install (#1842)

This is the link for the collection https://doi.org/10.25919/5eeb2a56eced7 @hol353https://github.com/hol353 Can you check that I have selected the correct license (GPL) Choices are:

*CSIRO Binary Software Licence The Software is licensed under a standard CSIRO Binary Software Licence, subject to any additional conditions notified as part ...

*CSIRO Open Source Software Licence (Based on MIT/BSD Open Source Licence) This licence releases the Software as 'open source'. It reflects the terms of the BSD/MIT open source software licences, with...

*GPLv3 Licence with CSIRO Disclaimer This licence releases the Software as 'open source' under the GPLv3 licence, with a specific CSIRO liability disclaimer includ...

Also: The attribution statement. Should this include more people? If so, them who?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://github.com/APSIMInitiative/APSIMClassic/issues/1842#issuecomment-646358080, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AC2UHLCYBGRHWPTFO75JT2LRXKQXRANCNFSM4MPVYCFQ.

[peter-devoil]

(Update) It appears the vc_redist runtime isn't installing. The msi installer downloads an empty installation that it claims "is changed since published".

[zur003]

Version 7.5? That really is turning back the clock! I think the only way to deal with this is to manually download and install the old VC++ runtimes. For 7.5, it appears that runtimes for both VC++ 2008 and VC++ 2010 are required. Interestingly enough, the install log provides the URLs where these can be obtained, but doesn't follow through with actually running those installers. This probably has something to do with both being well past their 10-year support lifespans.

In addition to the URLs appearing in the logs, Microsoft provides access to old VC runtimes at https://docs.microsoft.com/en-US/cpp/windows/latest-supported-vc-redist .

I can verify that this works, and with the old runtimes installed you can still party with Apsim 7.5 like it's 2013.