Sometimes you may need to extract and install Aspera HSTS RPM package manually instead of using a package manager such as RPM Package Manager or DNF. This situation commonly occurs when:
-
You do not have root privileges, so you cannot run rpm -i.
-
You need to inspect or extract specific files from an RPM without installing the whole package.
-
You are working inside a container, minimal Linux environment, or restricted system where the RPM database cannot be modified.
-
You want to deploy software into a custom directory rather than the standard system paths.
In these cases, the RPM file can be treated as an archive. The utility rpm2cpio converts the RPM package into a CPIO archive, which can then be extracted using the standard Linux cpio command.
- Download the rpm file from https://www.ibm.com/products/aspera/downloads
- Perform a raw extraction of the rpm file.
| rpm2cpio ibm-aspera-hsts-<version>-linux-64-release.rpm | cpio -idmv -D /opt/software |
-
- -D is the destination folder where the extracted files are stored. In this case it is saving it to the /opt/software folder
- It creates subfolders /opt/software/opt/aspera and creates files in there.
- It also extracts some files to /opt/software/usr/ and /opt/software/bin/ sub folders.
- Paste the license file in /opt/software/opt/aspera/etc/aspera-license
- Check "/opt/software/opt/aspera/bin/ascp -A"
Thats it - Aspera HSTS has been installed.
You can test transfer from a ascp Client. Make sure to add the -S option in the client to point to the correct location of the ascp binaries in the server.
ascp -S /opt/software/opt/aspera/bin/ascp <source-file> user@<dest-url>:/