Convert RPM to TGZ
Turn RPM archives into TGZ. 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 of an RPM in a TGZ.The installed files go into one gzipped tar archive.
What you get
One TGZ file that holds the files the RPM installs. Each file keeps its path, its time and its permissions.
The files are stored in a tar archive and compressed with gzip. That is the form in which source code is often shipped.
What it leaves behind
The header of the RPM is left out. That is the part with the package name, the dependencies and the install scripts. Only the files remain.
The conversion has no options. You pick the RPM and get the TGZ.
When it stops
If the RPM cannot be parsed, the conversion stops with
input_corrupted. No TGZ is produced in that case.For other archive conversions, see every RPM conversion or every TGZ conversion.
RPM and TGZ.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
Gzipped Tar Archive
Gzip-compressed tar archives, the way source code ships.
- Extensions
- .tgz
- MIME type
- application
/gzip - Kind
- Archives
In your code.The same RPM to TGZ conversion through the API, for your app or your agent.
$ cv convert archive.rpm archive.tgz$ cv convert archive.rpm archive.tgzQuestions.What people ask about RPM to TGZ.
Yes. The files keep their paths, their times and their permissions.
No. The header is left out, and the package name is part of it.
No. The install scripts are in the header, and the header is left out of the TGZ.
The file could not be parsed. The conversion stops with input_corrupted when that happens.