I used pkg list entire command , and i got the output for version column as follows :
0.5.11-0.175.1.0.0.24.2.
How to find the SRU from this?
Can we upgrade/ downgrade to a particular SRU ?
SRU is an abbreviation for Support Repository Update, installing new package versions from the support repo for that OS, much like installing a patch cluster for older Solaris releases.
The various fields in the version is explained in Oracle Solaris Package Versioning.
Oracle only makes SRUs available to customers with support contracts - if you have a support contract you can read more about SRU's in the Oracle Support Knowledgebase at Solaris 11 Support Repositories Explained, and see what fixes are available in each SRU for Solaris 11.1 and Solaris 11.2.
If you run 'pkg info entire' it will show the SRU name in human readable format also (if you have installed from the support repo - otherwise it shows the Release info). The 4th digit in 0.175.1.0.0.24.2 is the SRU number
In the example above it is the base Solaris 11.1 release - no SRU has been installed yet.
If an SRU had been installed on top of that you'd get a version like 0.5.11-0.175.1.21.4.1 (aka Oracle Solaris 11.1 SRU21.4.1)
You can easily upgrade to an SRU but you can't downgrade unless you have an older Boot Environment (BE) from which to upgrade to the SRU you want.
Related
Is there a postgres and keycloak version compatibility matrix? What is the latest postgres version compatible with Keycloak 20 ?
Unfortunately, there's no any matrix. In docs just a short and outdated list and some comments in Github discussions on why it's outdated.
Meanwhile, DB version for Java apps always depends on JDBC driver version.
So, the easiest way to find out what version of PostgreSQL is suitable for KC release is to take a look at versions of JDBC driver and PostgreSQL that specified in pom.xml. Switch to a release tag in the official repository, e.g. https://github.com/keycloak/keycloak/blob/20.0.3/pom.xml#L149-L150
The documentation here suggests Version 10.
The developer commits and issues only mention postgresql without versions. It doesn't matter which version you use, as long as it's supported!
See here for supported versions:
Supported versions
If you want you use the new CRS versions you need at least 2.9.6 of libapache2-mod-security2. see:
https://coreruleset.org/installation/
Is this possible on Debian11? I searched for backports but couldn't find any method on getting this version. Default Debian 11 Version 2.9.3
If you want you use the new CRS versions you need at least 2.9.6 of libapache2-mod-security2. see: https://coreruleset.org/installation/
Thanks, we (CRS team) should add some links to this documentation.
Is this possible on Debian11? I searched for backports but couldn't find any method on getting this version. Default Debian 11 Version 2.9.3
We are working on it, that Debian 11 accepts this version too. Actually, the Debian's package source repository already has the patched 2.9.3:
https://salsa.debian.org/modsecurity-packaging-team/modsecurity-apache/-/blob/bullseye/debian/changelog
You can download that and make an own package.
If you want to avoid to make a custom/own package, follow this link, and you can try the Digitalwave's ModSecurity repository. There you can find the 2.9.6 for Debian 10, 11, Ubuntu 18.04, 20,04 and 22.04.
Note: I'm CRS developer, and Debian maintainer. I made the packages for Debian too.
I have searched the interwebs for PostgreSQL 10.4 (32 & 64) for Linux platforms and Windows platforms but have been unable to locate any binaries to download. All I can find is the 10.5 version (or 9.x). Any ideas on where to look?
Thanks!
As mentioned in Versioning policy,
the rightmost number denotes the minor release, so 10.5 is the most recent release of PostgreSQL 10:
Minor releases are numbered by increasing the last part of the
version number. Beginning with PostgreSQL 10, this is the second part
of the version number, e.g. 10.0 to 10.1; for older versions this is
the third part of the version number, e.g. 9.5.3 to 9.5.4
10.(x-1) is generally made unavailable as soon as 10.x is released, because 10.(x-1) is the same set of programs, but with known bugs not yet fixed: it should not be prefered over a more recent version.
In most cases, the will to install a specific outdated minor release is due to not knowing the version numbering policy.
I'm working on an app that is only compatible with postgreSQL 9.4.5 and my current version is 9.5.2
Is there any way to download the older version? I can't seem to find it.
I found older versions here but they're meant for Solaris.
The answer in https://stackoverflow.com/a/31261608/1949363 describes in great detail how to do a downgrade. Does it work for you?
In terms downloading old versions, 9.4 is available on brew
$ brew search postgresql#9.4
postgresql#9.4
i would like to know, based on what rpm packages upgrade i can upgrade my RHEL version 5.11 to 6.x
We can't use re-installation of RHEL 6.x, so wanted an option(s) to upgrade to RHEL 6.x from 5.x by upgrading all needful packages.
By upgrading kernal or core rhel release rpm, can we upgrade to latest?
Please let me know details. Thank you.
In place upgrades between 4, 5, and 6 are not supported by RedHat and you risk impacting the support that you pay for by doing so. The only supported upgrade path is from 6 to 7. The expectation is that an upgrade path will continue in future releases.
You state that you cannot re-install but don't state why. Is it because the criticality of the system or is it because of the configuration of the application? I'm guessing the latter and that the system is not all that critical (because otherwise you wouldn't want to impact your support agreement). With that said, there is a way to upgrade and the procedure is provided by RedHat but, again, it is not supported by them.
The link is: In place upgrade