Symantec Drive Encryption for Linux installer cannot always automatically install packages using yum
book
Article ID: 162227
calendar_today
Updated On:
Products
Drive Encryption
Issue/Introduction
The Symantec Drive Encryption for Linux installer tries to install missing packages using yum but sometimes yum cannot find the exact package that is required.
The error messages displayed during installation will show the exact packages that are required and whether they can be installed automatically using yum.
For example, kernel-devel cannot be installed automatically by the installer using yum on CentOS 6.4 x64 and CentOS 6.5 x64.
Below is the complete list of messages when trying to install Symantec Drive Encryption for Linux 10.3.2 MP10 on CentOS 6.5 x64:
# bash pgp_desktop_10.3.2.21165_linux_el6_x86_64.bsx Checking if dkms is installed...no
Checking if dkms can be installed with yum...no
Checking if gcc is installed...no
Checking if gcc can be installed with yum...yes
Checking if make is installed...yes
Checking if patch is installed...no
Checking if patch can be installed with yum...yes
Checking if kernel headers are found...no
Checking if kernel-devel-2.6.32-431.el6.x86_64 can be installed with yum...no
-----------------------------------------------------------------------
*** ERROR ***
The following packages cannot be found with YUM:
kernel-devel-2.6.32-431.el6.x86_64 dkms
Cause
This occurs because the installer looks for specific package versions which are not available to yum. For example, the kernel-devel package that yum will install when called by the Symantec Drive Encryption for Linux installer is version 2.6.32-573 not version 2.6.32-431: # yum list kernel-devel
Available Packages
kernel-devel.x86_64 2.6.32-573.1.1.el6 updates
Resolution
When the Symantec Drive Encryption for Linux installer cannot find a correct package it is necessary to install it prior to running the installer.
For example, the correct kernel-devel package needs to be installed prior to installing Symantec Drive Encryption for Linux on CentOS 6.4 x64 and 6.5 x64.
Note that it is important that the filename of the rpm package matches exactly what the Symantec Drive Encryption for Linux installer is looking for, otherwise the installer will not recognize that the package is installed. This can be seen with the kernel-devel package for Symantec Drive Encryption for Linux 10.3.2 MP1 on CentOS 6.4 x64. The package is available here: http://vault.centos.org/6.4/centosplus/x86_64/Packages/kernel-devel-2.6.32-358.el6.centos.plus.x86_64.rpm
While this is the correct version of kernel-devel, the filename contains "centos.plus" and will not be recognized by the installer. Instead, a file with the exact name must be used, such as this: http://ftp.scientificlinux.org/linux/scientific/6.4/x86_64/os/Packages/kernel-devel-2.6.32-358.el6.x86_64.rpm
As an example, to install Symantec Drive Encryption for Linux 10.3.2 MP10 on CentOS 6.5 x64 installed with the Minimum installation media, follow these steps:
1. Install perl. This will install perl.x86_64 4:5.10.1-141.el6: # yum install perl
2. Install DKMS (Dynamic Kernel Module Support). The Symantec Drive Encryption for Linux installer cannot install this automatically: # rpm -Uvh http://linux.dell.com/dkms/permalink/dkms-2.2.0.3-1.noarch.rpm
3. Install kernel-devel. Note that the filename matches exactly what the installer expects to see: # rpm -Uvh http://vault.centos.org/6.4/cr/x86_64/Packages/kernel-devel-2.6.32-431.el6.x86_64.rpm
4. Install Symantec Drive Encryption for Linux 10.3.2 MP10: # bash pgp_desktop_10.3.2.21165_linux_el6_x86_64.bsx Checking if dkms is installed...yes Checking if gcc is installed...no
Checking if gcc can be installed with yum...yes
Checking if make is installed...yes
Checking if patch is installed...no
Checking if patch can be installed with yum...yes
Checking if kernel headers are found...yes
Determining packages to install...
Installing packages... Installing pgp-libs pgpwde pgpwde-kmod-source
5. When the installation is complete you will see this: Installion complete. You will need to reboot the system for these changes to take effect.