Requirement is to download software from Centos 5.4. When I do yum install , I get the latest version and not the one available for Centos 5.4.
How do I configure yum to download only from 5.4 repo?
As I said in my answer to your other question you need to find a repository that has a maintained, static entry for 5.4.
Most repositories have just one repository for each major version and upgrade it as new minor versions are released. But some keep specific repositories for each version independently (at least for a little while).
I would start with checking whether your current repository has an explicitly 5.4 repository (by using the URL in the yum.conf or /etc/yum.repos.d/*.repo file for the repository).
If that doesn't work out you get to try other mirrors as listed on the CentOS mirrors website.
As a fallback, and I encourage you to try to find a valid mirror first, you can find this sort of minor version specific repository on http://vault.centos.org.
Related
Previously I am developing applications with JavaFX in Oracle Java SE shipped by Red Hat but it seems it is no longer offered as in https://access.redhat.com/articles/3253281. However, it seems that the OpenJDK coming from rhel-7-server-rpms repository does not come with JavaFX.
Are there better ways instead of just installing packages from outside the repositories provided by Red Hat? I don't want to test each environment with self-compiled OpenJFX binary one by one.
Oracle provide RPMs you can download:
http://www.oracle.com/technetwork/java/javase/downloads/jdk8-downloads-2133151.html
Those RPMs are not in a YUM repository that you could just point your red hat boxes to.
You can download the RPMs and create your own rum repository, then add your custom repository to the yum repository list for each of your target machines and after that use yum to install the rpms to your boxes. You would need to restrict this so that it isn't fully open to the public I think (to meet Oracle Java distribution requirements).
If you built your own version of the Java SE which included JavaFX from OpenJFX sources (or you can find a package for your target OS which somebody else has built), then you could host that in an unrestricted manner in your own repository (or any other public repository out there), or pull the package from a public repository if somebody else has already put it there.
If you don't need a repository, and can just scp the rpms to the relevant machines then you can directly install the rpms on the machines without setting up your own custom repository.
If you package your application as a self-contained application, then the application install bundle itself will include the JRE, so you don't need to worry about installing that separately on the machine (and also don't potentially run into situations where the user has installed a runtime version which is not compatible or tested with your code). Perhaps that is a preferred path for you.
I don't know RedHat's policy for OpenJDK releases and builds to their repositories. It would be nice if they included JavaFX in their OpenJDK distributions in their repositories or provided a separate package for OpenJFX, similar to what Ubuntu do. Perhaps they might include JavaFX in their OpenJDK 9 distributions. They have info on RHEL Support for OpenJDK 9, so maybe they say something there (I can't read it as I am not a RHEL subscriber). If you have a support contract with Redhat and the info isn't available on their site, then you could ping them and ask them about OpenJFX JavaFX distributions hosted in their repository (to see if they are there or not or if they have a plan to put them there).
At present we are on Apache/2.2.15 (UNIX) version. To fix the vulnerabilities we are suggested to upgrade to new version. I got new version from online using "wget" command and followed steps mentioned on this link http://httpd.apache.org/docs/2.2/install.html#download.
Once I am done, checked version using httpd -v. It gives me old version Apache/2.2.15 (UNIX). If I check using /usr/local/apache2/bin/httpd - v. It gives me new version. Did I successfully upgraded the version or not? If not what should I do?
I tried "yum install httpd" - It says "Nothing to do".
You now have two versions of Apache installed. You have the one installed with the system package manager (yum) in /usr/sbin/httpd. You have one installed manually in /usr/local/apache2/....
Which one you get will be determined entirely by which path you use.
In general, mixing system-managed packages with manually installed packages is a recipe for trouble. If you want to stick with the newer version in /usr/local, you should remove the system version, and realize that you will lose some manageability. For example, you will no longer be able to use yum install ... to install new Apache modules, and you will not be able to verify the installed files using tools like rpmverify.
If your distribution currently has Apache 2.2.x, that suggests your distribution is fairly old. For example, RHEL (and CentOS) 7 (and similar variants) have version 2.4.6 packaged, so you may want to update your host to something newer than whatever you're running now.
Yes, its successfully upgraded as per the screenshot.
httpd 2.2.15 is the version with RHEL 6 repository, here HTTPD_HOME is /etc/httpd (Highest version provided for HTTPD via RPM RHEL 6 is 2.2.15)
httpd 2.4.6 is the version with EPEL-HTTPD24 repository, here HTTPD_HOME is /usr/local/apache2/
I'm attempting to migrate from a GitLab 7.1.0 (Source) installation (on Centos6) to latest omnibus (on Centos7) using these instructions:
https://docs.gitlab.com/omnibus/update/README.html#upgrading-from-non-omnibus-postgresql-to-an-omnibus-installation-using-a-backup
Essentially it boils down to:
Set up a new machine,
Install the omnibus version on the new machine that matches your source version,
Do an "backup" from the source version,
Restore that backup into the omnibus version,
update the omnibus version to latest.
I'm stuck on #2. I've added the GitLab repo, but the oldest version of the "gitlab-ce" package available is 7.10.0. Also they're named weirdly, e.g. "7.10.0~omnibus-1", "7.10.0~omnibus.1-1", etc. instead of simply "7.13.0-ce.0.el7".
What are my options? If I install 7.13.0 Omnibus from the repo then try to restore a backup from 7.1.0 into it, should I expect that to work? Will I lose data?
Is there a 7.1.0 omnibus RPM available somewhere?
If the new machine needs to be Centos6 in order to install a 7.1.0 omnibus package then I can reimage.
If you look in the official RPM repo it looks like 7.10 is the oldest version of the omnibus available for CentOS.
I think your best option is to perform the source upgrade outlined in 6.x-or-7.x-to-7.14.md which should let you upgrade to v7.14. Then you can resume the normal "upgrade source installation to omnibus installation" method you found.
Also, in case it's helpful, the docs repo has incremental source upgrade procedures for many more versions.
I have installed OpenSUSE 12.1 installed on machine.
and i have postgresql-contrib-8.3.11-0.1.i586.rpm,postgresql-devel-8.3.11-0.1.i586.rpm, postgresql-docs-8.3.11-0.1.i586.rpm,postgresql-libs-8.3.11-0.1.i586.rpm,postgresql-server-8.3.11-0.1.i586.rpm..
I want to installed postgresql 8.3 version based on above packages..but when i installed with this command .it shows an error.
opnsu121:/ # rpm -Uvh postgresql-server-8.3.11-0.1.i586.rpm
error: Failed dependencies:
postgresql = 8.3 is needed by postgresql-server-8.3.11-0.1.i586
Even i am not able to find postgresql 8.3 base version as i think the above one is update.i have gone throgh the download.openSUSE.orf,ftp.openSUSE.org..
http://download.opensuse.org/update/11.0/rpm/i586/..
but not able to find what i need..so please help on this,
If at all possible, use YaST or whatever package manager SuSE uses to install the current version of PostgreSQL. From the repository it looks like that's 9.1.1.
If you specifically need PostgreSQL 8.3, I'd recommend using the distro-independent installer from EnterpriseDB. That should work fine on SuSE 12.2. If your organisation has particularly restrictive and unsafe version policies that force you to use old versions with known bugs, you can get 8.3.14 for 32-bit Linux here and 8.3.11 for 32-bit Linux here.
If you have issues with using the well-tested and known-to-work EnterpriseDB binary installer versions of PostgreSQL, your other option (and a good one) is to install from source code. Download the PostgreSQL 8.3.18 sources from the FTP site, then:
sudo mkdir -p /opt/postgresql93
sudo chown `id -un` /opt/postgresql93
./configure --prefix=/opt/postgresql93
make
make install
after which you can use /opt/postgresql93/bin/initdb (see initdb manual) to create a database and /opt/postgresql93/bin/pg_ctl (see pg_ctl manual) to start/stop it, as per the PostgreSQL documentation.
Don't try to force packages from an old version of SuSE to install on your new version. It'll probably result in an increasing tree of dependencies and end in pain.
If at all possible, try to convince your company that their policy of requiring a specific minor version (eg 8.4.14 not just "8.4.x") of PostgreSQL is unsafe and counterproductive. They're forcing you to do dirty hacks or hand-compile unique, custom installs just for your setup in order to avoid using well tested builds that contain extra bug fixes. Requiring approval before upgrading from 8.3 to 8.4/9.0/9.1/etc makes sense as there are feature and backward compatibility changes that require careful testing, but requiring approval before upgrading from 8.3.14 to 8.3.18 is counterproductive. Minor version upgrades of PostgreSQL are very conservative; you should stay up to date with the latest minor release.
hurray...I got the answer..
I have got the package below:
postgresql-contrib-8.3.11-0.1.i586.rpm, postgresql-devel-8.3.11-0.1.i586.rpm,postgresql-docs-8.3.11-0.1.i586.rpm,postgresql-libs-8.3.11-0.1.i586.rpm,postgresql-server-8.3.11-0.1.i586.rpm from the below link:
http://download.opensuse.org/update/12.1/i586/
and the one more package which i have struggled to get is:
postgresql-8.3.11-0.1.i586.rpm with the following link:
http://rpm.pbone.net/index.php3/stat/4/idpl/17194424/dir/opensuse_11.x/com/postgresql-8.3.11-0.1.i586.rpm.html
with all above packages i have installed using..
rpm -ivh packagename
if there is a dependency then rpm -ivh --nodeps packagename
great..its done..
I have a server currently running RHEL 5.1, and I would like to upgrade it to RHEL 5.4. The server is not connected to the Internet, so I don't think I can use "yum update".
How would I be able to upgrade my server, and is it just a small-scale upgrade, like Windows patches, leaving everything on the server intact, or would it delete everything that was on the server?
Thank you.
Regards,
Rayne
I haven't actually tried this myself, but you should be able to use an installation disc for RHEL 5.4 to upgrade even if you are off-line (although you'll need to get on-line somewhere to download the disk image). Once you have the RHEL 5.4 disc, you should be able to follow the instructions here:
How do I use yum to update or install packages for Red Hat Enterprise Linux 5 from a customized repository?
to update your system. Basically, you create a custom repository on you hard drive with the rpm files from the disk and point yum at it or use the disc directly.
Good luck.
Of course if you can put the server temporarily on-line and just use the on-line repositories, after updating all the packages in your 5.1 distribution, you'll have all the same files as if you installed 5.4. At least that's what I remember happening. I had a 5.0 installation that I kept updated and when I compared them they seemed to be the same as the 5.3 version (current at the time) although during boot, my system said it was still 5.0
Rayne,
I used to work on DOE classified systems that could never touch the public internet. There is a very easy way to do this as mentioned. Just use the ISO as a repo, and for my example to work, it needs to be a DVD image. (The way around that using disk {1,2,3} is to copy the files from each disk onto the local disk or a storage device)
You will need to install createrepo which for me involved two dependencies.
createrepo
deltarpm
python-deltarpm
mkdir -p /mnt/iso/rhel54
mount -o loop /path/to/rhel5.4.iso /mnt/iso/rhel54
cd /mnt/iso
createrepo .
It will look like this:
[root#hostname iso]# createrepo .
44/20586 - rhel54/HighAvailability/Packages/PyQt4-4.6.2-8.el6.x86_64.rpm
Create /etc/yum.repos.d/rayne.repo and add
[Rayne-repo]
baseurl=file:///mnt/iso/
enabled=1
gpgcheck=0
Then run yum update
The update from RHEL 5.1 to RHEL 5.4 is not a small one, not like Windows patches. You can read the release notes, but you will end up with a newer kernel in the end and a ton of updates to the packages. I have not upgraded from 5.X to 5.Y+3 before, it's always been incremental (5.1 to 5.2). At any rate, this should work for you.