Description of problem:
When the "yum -q history addon-info last saved_tx" command is used to store transaction data in a file, an attempt to use the resulting file to repeat the transaction fails with an error, because the output contains extra lines.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Run the following command to save the latest transaction to a file:
yum -q history addon-info last saved_tx > latest.yumtx
2. Copy the latest.yumtx file to a machine with identical transaction history, and attempt to repeat the saved transaction:
yum load-transaction latest.yumtx
3. See the error message.
Error: rpmdb ver mismatched saved transaction version, aborting.
The transaction stored in the file is repeated successfully.
Have two simple fixes that are upstream:
1. Produce just the load-ts data when someone runs "yum -q history addon-info saved_tx".
2. Accept the old output in load-ts.
...both are only a couple of lines of changes.
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
Prior to this update, when the "yum -q history addon-info last saved_tx" command was used to store transaction data in a file, an attempt to supply this file to the "yum load-transaction" command in order to repeat the transaction failed with an error, because the output contained extra lines. This update corrects the underlying source code to make sure the "yum -q history addon-info last saved_tx" command produces valid output, and adapts "yum load-transaction" to accept older version of the output as well.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.