I am working on developing an software.
I have installed the v1.0 on my machine running solaris 10,
and I want to upgrade to version 1.1 tha has some new function.
I do not want to uninstall version 1.0 but upgrade to version 1.1.
How do I make a patch?
Writing a script or using some patch tools?
If you are asking about Solaris patches, i.e. those appling to SVR4 packages, I guess only Solaris engineering is able to build and deliver them as there is no standard/documented format I'm aware of. The new version of Solaris (11) is going to abandon this patching method anyway to the new pkg mechanism.
If you want a new version not to replace the older one, I guess the simplest way would be to have them to install in different directories. eg: /opt/zhangli/v1.0 and /opt/zhangli/v1.1. Any packaging format would support that.
Related
The newest AnyLogic version is not supported by my current AnyLogic license. The license only supports up to 8.3.3. However, I do wish to install AnyLogic on another computer and activate it with my license. However, surprisingly I could not find downloads of earlier AnyLogic versions. Does anyone know if and where I can find these earlier versions, and whether I perhaps can downgrade a newer AnyLogic version?
https://www.anylogic.com/files/anylogic-professional-8.3.3.exe
For any version, just put the version you want and you will likely be able to download it
if using mac:
https://www.anylogic.com/files/anylogic-professional-8.3.3.dmg
In addition to Felipe's answer, you can always ask
support#anylogic.com
if you need very old versions. I believe that AL7.x is not available online anymore but they happily send the installers if you need them.
now that they release v0.5.0 the question is how can I upgrade from 0.4.6 to 0.5.0 without loosing all my packages? is there even a way. Or if there is no easy way, how have people done it? What is the best way to do it?
Other question is, is it worth it or do I need to upgrade? What are the benefits or why I should not upgrade (yet)? Is there problems with Atom and other packages?
Yes there is quest same question already, but it is for older version and I thought if something has changed on upgrading.
You can go into your .julia/v0.4 folder and copy the REQUIRE file to the v0.5 folder. Then when you Pkg.update() your packages should automatically install.
There are very many upgrades (broadcast syntax, arraypoclypse, string changes, etc.), and many packages may stop supporting v0.4 for this reason. I would recommend you start upgrading soon. Juno has already released its v0.5 version, so when you update it should be compatible.
We've been using a shipping API via our Unix server, specifically SCO Openserver 5.0.7, for a little over a year.
Our system generates XML files, sends them to the server using the lwp-request command, receives the response, interprets it, and processes it as needed by our system.
The exact command we use is:
lwp-request -m POST https://url.com < REQUESTFILE.XML > RESPONSEFILE.XML
The shipping company is upgrading all servers to require TLS 1.2, and now I get
500 SSL negotiation failed:
as a response when using this command.
I'm not sure how to go about making our system compatible.
Do I need to update Perl? (Current version is v5.8.8 built for i586-pc-sco3.2v5.0). If so, what is the minimum version to use TLS 1.2?
Do I need to update LWP? I believe my LWP version is 5.805 (got this using perl -MLWP -le "print(LWP->VERSION)")
Do I need to go into the lwp-request script and manually modify it?
Or is there perhaps another command that does an equivalent job using TLS 1.2?
Given your very old version of Perl (5.8.8, where 5.8.9 was release 2008) and LWP (5.805, 5.806 was released 2007) on a very old OS (SCO OpenServer 5.0.7, last update around 2009) it is likely that you are also running a very old version of OpenSSL. TLS 1.2 was only specified in 2008 and got available in OpenSSL only with 1.0.1 which was released 03/2012, i.e. several years after any software updates to your system.
You can check it it with openssl version and my guess is that it says something about version 0.9.8, i.e. way too old.
To make TLS 1.2 work on this old system you would need to compile a newer version of OpenSSL (at least the latest 1.0.1) and rebuild the Perl modules interfacing with OpenSSL so that they use this new version. Depending on your setup this might be Crypt::SSLeay or Net::SSLeay. And given how old your system is it is not unlikely that you run in various problems with compiling simply because most don't expect that somebody tries to compile newer software on outdated systems. Thus it might just be easier to upgrade everything to a recent and supported OS instead of trying to fight with an old system.
JProfiler agent seems to require glibc 2.7, but Centos has glibc 2.5. Has anyone successfully compiled the jprofiler agent for glibc 2.5 or did previous version of JProfiler create agents with 2.5?
Actul error is
Error occurred during initialization of VM
Could not find agent library /opt/jprofiler/bin/linux-x64/libjprofilerti.so in absolute path, with error: /lib64/libc.so.6: version `GLIBC_2.7' not found (required by /opt/jprofiler/bin/linux-x64/libjprofilerti.so)
The problem is that JProfiler you are using has been built on a system with glibc-2.7 (or later).
In general, UNIX systems support backwards compatibility (code compiled on an older system continues to work on a newer one), but not forward compatibility (you can't expect code built on a newer system to work on an older one).
Your choices are: upgrade your version of glibc, or obtain a different build of JProfiler (that was built on glibc-2.5 based system or older).
That's actually a regression in 7.0.1, an easy workaround is to use 7.0:
http://download.ej-technologies.com/jprofiler/jprofiler_linux_7_0.tar.gz
We'll fix this dependency problem shortly (my company develops JProfiler). Thanks for letting us know.
Does anyone know how to install a Vista UPGRADE edition to a virtual machine? Id like to use it for testing with older versions of .NET, but it wont let me install the upgrade version. I'd rather not have to install XP and then Upgrade it. Its a licensed legal copy with CD-Key and all. It just wont install to an empty VM because its an Upgrade version.
Thanks
WARNING: The following does violate your EULA
Install Vista without using a serial number and choose the basic edition and also unselect auto activate.
After install, reinstall and now you can use your serial number and perform an upgrade.
See Paul Thurrot's site for more in depth information.