what is the difference between update and upgrade? [closed] - upgrade

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 5 years ago.
Improve this question
In apt-get command, what is the major effects of update and upgrade?
I didn't see any difference besides the wording.
It seems like update is about system package whereas upgrade is about software package. If that is the case, how to tell which is system package and which is software package?

From man apt
update
update is used to resynchronize the package index files from their
sources. The indexes of available packages are fetched from the
location(s) specified in /etc/apt/sources.list...
...
upgrade
upgrade is used to install the newest versions of all packages
currently installed on the system from the sources enumerated in
/etc/apt/sources.list. Packages currently installed with new
In simple words: apt-get update will update apt's database, the list of available packages (and version's date and number). Where apt-get dist-upgrade will upgrade all packages installed in your system (... if date and/or version differ).

update updates the list of available packages and their versions, but it does not install or upgrade any new packages.
upgrade actually installs newer versions of the packages you have.

The main objectives of update is to provide bug and errors fixes to present existing system....
The main objectives of upgrade is to introducing new features and functionalities to an existing system...
Upgrading involves transforming old system into newer version.....

Difference between update and upgrade is as:
Update make changes to an app or operating system in such a way that it not affects its core structure. Like bug fixes, security patches, adding support for drivers and new hardware, etc can be termed as Update.
While when set of changes made to a software are significant and substantial enough then is called as Upgrade.
Updates are smaller than upgrades. Like update of OS can be of few hundred megabytes, but upgrade of OS can be of several Gigabyte.
Updates take smaller time than Upgrades. It could take several hours to upgrade complete system.
Updates are always free while upgrade can cost you.
An upgrade can result in change in software version while update will not change version of software.

Related

Installing specific kubernetes version on Centos [closed]

Closed. This question is not about programming or software development. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 2 months ago.
Improve this question
I'm trying to install certain version of kubernetes, using yum package manager (In give example I'm trying to install 1.21.8, however yum does not find given package version)
yum install kubelet-1.21.8-0 kubeadm-1.21.8-0 kubectl-1.21.8-0
I also tried like this:
yum install kubelet-1.21.8 kubeadm-1.21.8 kubectl-1.21.8
Output:
No package available
If your trying to install a specific version of the package it is enough to define it during the yum install command as below :
yum install -y kubelet-<version> kubectl-<version> kubeadm-<version>
Please check when you are installing kubernetes version 1.21.8-00, kubernetes-cni package should be (>= 0.8.7) version to satisfy dependency requirements.
So, the final command looks like this:
yum install -y kubelet-1.21.8-00 kubectl-1.21.8-00 kubeadm-1.21.8-00 kubernetes-cni-0.8.7
To verify the version the below command
kubelet --version / kubeadm version / kubectl version.
Note : Add kubernetes source in /etc/yum.repos.d/kubernetes.repo file. And also make sure your Kubernetes version is compatible with the Docker containers engine version to avoid compatibility problems.

PostgreSQL for Debian vs Redhat (Centos) [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 3 years ago.
Improve this question
PostgreSQL 11 works more efficiently in debian or redhat. Accordingly, I will choose a server and plan training. What are the advantages and disadvantages. Which operating system does the Postgres committee like?
There is no PostgreSQL committee. There is core, but they don't determine which operating systems are supported.
From the documentation (you probably read that):
A platform (that is, a CPU architecture and operating system combination) is considered supported by the PostgreSQL development community if the code contains provisions to work on that platform and it has recently been verified to build and pass its regression tests on that platform. Currently, most testing of platform compatibility is done automatically by test machines in the PostgreSQL Build Farm. If you are interested in using PostgreSQL on a platform that is not represented in the build farm, but on which the code works or can be made to work, you are strongly encouraged to set up a build farm member machine so that continued compatibility can be assured.
In general, PostgreSQL can be expected to work on these CPU architectures: x86, x86_64, IA64, PowerPC, PowerPC 64, S/390, S/390x, Sparc, Sparc 64, ARM, MIPS, MIPSEL, and PA-RISC. Code support exists for M68K, M32R, and VAX, but these architectures are not known to have been tested recently. It is often possible to build on an unsupported CPU type by configuring with --disable-spinlocks, but performance will be poor.
PostgreSQL can be expected to work on these operating systems: Linux (all recent distributions), Windows (Win2000 SP4 and later), FreeBSD, OpenBSD, NetBSD, macOS, AIX, HP/UX, and Solaris. Other Unix-like systems may also work but are not currently being tested. In most cases, all CPU architectures supported by a given operating system will work.
The majority of hackers use Linux, but there are people who develop on FreeBSD, MacOS or Windows.
If you know that PostgreSQL works most efficiently on certain Linux distributions, you know more than I do.
When choosing an operating system for PostgreSQL, I would proceed like this:
List the operating systems you are familiar with (or for which your organization has skilled administrators).
Exclude all operating systems for which there is not more than one animal in the buildfarm.
Exclude Windows.
Then pick any of these.

the procedure entry point sprintf_s could not be located in DLL [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 3 years ago.
Improve this question
We are using windows XP SP3 version "PosReady" which is still supported by MS.
We have several old computers running on this OS.
Recently we have problem with any software using msvcrt.dll.
Constantly this message popup shows:
"the procedure entry point sprintf_s could not be located in DLL msvcrt.dll".
Tried removing and reinstalling all MS visual C++ run times but it did not help.
Any help is appreciated.
Thanks,
There was an express update pushed through Windows Update yesterday (FEB-16), that solves the issue and is listed in my installed updates as:
Security Update for Windows XP (KB4487085-v2)
So it seems the issue was in the first version of that update.
Microsoft in 4487085 states:
This update was rereleased February 15, 2019 to address a known issue that occurred when you installed the original February 12, 2019 version of the update.
and
After you install the originally released version of this security update (from February 12, 2019), applications that use the msvcrt.dll dynamic link library (DLL) do not load properly.
Uninstall the Windows XP updates that were pushed out February 12.
Windows update, via the "shield" in task bar, notified me that there were updates. I installed them and after reboot had the issue described here. So, pretty obvious what the problem was. I used "Add/Remove Programs" to uninstall the nine or so updates that were showing for that date.
Most of the updates affected .NET libraries and I think that's where the problem is. The newest MSVCRT.DLL on my system is from 2012, even when the updates were still installed, so messing with them won't help.
Ideally, MS will fix this, but if not, we're almost out of support anyway. Don't forget to disable automatic updates or the problem will come back.

How to upgrade Julia to v0.5.0?

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.

Using Installshield with TeamCity and MSBuild [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 4 years ago.
Improve this question
I am using TeamCity to build and prepare a Windows Forms application. I've got a few projects in the solution, one of these being the .isproj which is an Installshield Project. I'm using the free developer version that Installshield so nicely provide for us.
However, TeamCity obviously can't build this, because the box doesn't have Installshield installed.
I can't install the same version because it requires Visual Studio, which is a bit of a pain.
Does anyone know if there is a free version that we could use on our Build Server to generate the artefacts for release?
I am not sure if InstallShield LE is available in the VS Express edition, which you could install on your build machine.
Another alternative would be to use another tool, for example Advanced Installer also has integration with VS and full command line support, so you can integrate it in your build machine. Also, you can install it separately on the build machine, without any edition of VS. It has the "Simple" project in the free edition, any other project types require a commercial license.