Convert RPM to TXZ
Turn RPM archives into TXZ. 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 archive.Paths, times and permissions stay. The package header is left out.
What you get
One TXZ file: a tar archive compressed with xz. It holds the files the RPM installs.
Each file keeps its path, its time and its permissions, so the layout inside the archive matches the layout the package would install.
What it leaves behind
The header of the RPM is not copied. That means the package name, the dependencies and the install scripts are not in the TXZ.
Only the installed files are carried over. The archive holds those files and nothing else from the package.
RPM and TXZ.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
XZ Tar Archive
XZ-compressed tar archives. Smaller than gzip, common for source releases.
- Extensions
- .txz
- MIME type
- application
/x -xz - Kind
- Archives
In your code.The same RPM to TXZ conversion through the API, for your app or your agent.
$ cv convert archive.rpm archive.txz$ cv convert archive.rpm archive.txzQuestions.What people ask about RPM to TXZ.
It contains the files the package installs, stored in a tar archive and compressed with xz. Their paths, times and permissions are kept.
No. The install scripts are part of the header, and the header is left out.
No. The dependency information is in the header, which is not copied into the TXZ.
Yes. The result is one TXZ file.