Convert RPM to 7Z
Turn RPM archives into 7Z. The files the package installs are kept with their paths, times and permissions.
Converted in an isolated sandbox on our serversDeleted after 24 hours
Drop RPM files on the dialor turn it to pick what to do
The files from an RPM, in one 7Z.The installed files keep their paths, times and permissions. The package header is left out.
What you get
One 7Z archive that holds the files the RPM installs. Each file keeps its path, its time and its permissions, so the folder layout matches what the package would put on a system.
7Z is an archive format with strong LZMA compression.
What it leaves behind
The header of the RPM. That means the package name, the dependencies and the install scripts are not in the 7Z. Only the files themselves are carried over.
If you need those details, keep the original RPM next to the archive.
When it fails
If the file cannot be parsed, the conversion stops with
input_corrupted. This happens when the RPM is damaged or is not a readable package.For other archive conversions, see every RPM conversion or every 7Z conversion.
RPM and 7Z.What each format is.
The formats
RPM Package
Packages for Red Hat, Fedora and SUSE. A header in front of a compressed cpio archive.
- Extensions
- .rpm
- MIME type
- application
/x -rpm - Kind
- Archives
7-Zip Archive
7-Zip archives with strong LZMA compression.
- Extensions
- .7z
- MIME type
- application
/x -7z -compressed - Kind
- Archives
In your code.The same RPM to 7Z conversion through the API, for your app or your agent.
$ cv convert archive.rpm archive.7z$ cv convert archive.rpm archive.7zQuestions.What people ask about RPM to 7Z.
Yes. The files keep their paths, times and permissions.
No. The header is left out, and the install scripts are part of it, along with the package name and dependencies.
No. It produces one 7Z file that holds the package's files. Nothing is installed.
The file could not be parsed. The conversion stops with input_corrupted when it cannot read the package.