Incorrect source repository (from_repo) after system upgrade #1851
Assignees
Labels
Priority: HIGH
Triaged
Someone on the DNF 5 team has read the issue and determined the next steps to take
Milestone
Comments
jan-kolarik
added
the
Triaged
|
Also valid for all offline transactions. |
m-blaha
added a commit
that referenced
this issue
Feb 13, 2025
Currently, when replaying a stored transaction, all RPM files are placed into a single `@stored_transaction` repository. This can be confusing, especially during a system upgrade, which also uses stored transactions. With this patch, local RPM files from stored transactions are placed to the repository they originally came from. Fixes: #1851
m-blaha
added a commit
that referenced
this issue
Feb 14, 2025
Currently, when replaying a stored transaction, all RPM files are placed into a single `@stored_transaction` repository. This can be confusing, especially during a system upgrade, which also uses stored transactions. With this patch, local RPM files from stored transactions are placed to the repository they originally came from. Fixes: #1851
m-blaha
added a commit
that referenced
this issue
Feb 18, 2025
Currently, when replaying a stored transaction, all RPM files are placed into a single `@stored_transaction` repository. This can be confusing, especially during a system upgrade, which also uses stored transactions. With this patch, local RPM files from stored transactions are placed to the repository they originally came from. Fixes: #1851
m-blaha
added a commit
that referenced
this issue
Feb 19, 2025
Currently, when replaying a stored transaction, all RPM files are placed into a single `@stored_transaction` repository. This can be confusing, especially during a system upgrade, which also uses stored transactions. With this patch, local RPM files from stored transactions are placed to the repository they originally came from. Fixes: #1851
m-blaha
added a commit
that referenced
this issue
Feb 19, 2025
Currently, when replaying a stored transaction, all RPM files are
placed into a single `@stored_transaction` repository. The user can see
this artifitial repository when checking from which repositories the
installed packages came:
❯ dnf repoquery --installed --queryformat="%{full_nevra} %{from_repo}\n"
vlc-plugin-gstreamer-1:3.0.21-15.fc40.x86_64 @stored_transaction
This can be confusing, especially during a system upgrade, which also
uses stored transactions.
With this patch, local RPM files from stored transactions are
placed to the repository they originally came from:
❯ dnf repoquery --installed --queryformat="%{full_nevra} %{from_repo}\n"
vlc-plugin-gstreamer-1:3.0.21-15.fc40.x86_64 updates
Fixes: #1851
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
After system upgrade with dnf5, the
from_repoattribute for all installed packages contains@stored_transactionvalue. This is confusing to the users. The attribute should contain id of the repository the package really came from.See
dnf repoquery --installed --queryformat="%{full_nevra} %{from_repo}\n"on the upgraded system.The text was updated successfully, but these errors were encountered: