Created attachment 1143895 [details]
Output of dnf list installed | grep @@commandline
Description of problem:
Packages are marked to originate from @@commandline when they are actually from fedora repo.
I do have 1815 packages of the base OS system that are marked to be from @@commandline.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1."dnf list installed |grep @@commandline > list.txt"
see http://fpaste.org/349637/ or attachment
Just a few packages that I really installed manually.
Output of "dnf history userinstalled" is totally different, and lists just a few programs that I really installed manually.
Packages updated by `dnf system-upgrade` are listed as "@@commandline" in `dnf list installed`. That probably is the cause.
Same issue when ugrading from F24 to F25.
*** Bug 1370087 has been marked as a duplicate of this bug. ***
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
The problem should be fixed by refactor of system-upgrade plugin. In future probably we can download packages to repository cache and after reboot run saved transaction with downloaded rpms. It should provide information about origin of installed rpms.
Issue still persists when upgrading from Fedora 25 to Fedora 26 (Beta).
dnf reinstall fixes it for individual packages, for example:
dnf list GeoIP.x86_64
Last metadata expiration check: 12:07:09 ago on Tue 20 Jun 2017 21:15:47 AEST.
GeoIP.x86_64 1.6.11-1.fc26 @@commandline
dnf reinstall GeoIP.x86_64
dnf list GeoIP.x86_64
Last metadata expiration check: 12:07:41 ago on Tue 20 Jun 2017 21:15:47 AEST.
GeoIP.x86_64 1.6.11-1.fc26 @fedora
I created a pull-request that should help with issue (https://github.com/rpm-software-management/dnf-plugins-extras/pull/97).
Same here after upgrade from F25 to F26.
I used the documented / recommended upgrade method:
1 - sudo dnf system-upgrade download --refresh --releasever=26
2 - sudo dnf system-upgrade reboot
This is a real bummer, as I wanted to see what packages are installed from third party repos (rpmfusion, copr...).
dnf-2.6.3-1.fc26 dnf-plugins-extras-2.0.2-1.fc26 has been submitted as an update to Fedora 26. https://bodhi.fedoraproject.org/updates/FEDORA-2017-4813633f96
(In reply to Fedora Update System from comment #9)
> dnf-2.6.3-1.fc26 dnf-plugins-extras-2.0.2-1.fc26 has been submitted as an
> update to Fedora 26.
Is this update expected to fix the bug for already updated Fedora instances, or will it only apply to system-upgrades ran after installing the update?
The patch doesn't have a power to rewrite a history, but with this patch ``dnf system-upgrade`` will store correct origin of packages after next Fedora system upgrade.
(In reply to Jaroslav Mracek from comment #11)
> The patch doesn't have a power to rewrite a history, but with this patch
> ``dnf system-upgrade`` will store correct origin of packages after next
> Fedora system upgrade.
Thanks for this clarification.
dnf-2.6.3-1.fc26, dnf-plugins-extras-2.0.2-1.fc26 has been pushed to the Fedora 26 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-4813633f96
dnf-2.6.3-1.fc26, dnf-plugins-extras-2.0.2-1.fc26 has been pushed to the Fedora 26 stable repository. If problems still persist, please make note of it in this bug report.
Is there a workaround to fix @@command repo RPMs to be correct fedora repo aside from dnf reinstall of all @@commandline packages after upgrade to FC26?
Not easy way, but after updates installing, the repo will change. Just wait till new updates appears.
(In reply to Jaroslav Mracek from comment #16)
> Not easy way, but after updates installing, the repo will change. Just wait
> till new updates appears.
As I just updated last week that may take a while so maybe just cron a reinstall of everything @@commandline.
I have fedora-updates and fedora-updates-testing repos enabled, and ...
... can confirm that at this time, if I do "dnf list installed", a bunch of packages are listed as sourced from "@@updates" and "@@updates-testing" (and @@rpmfusion-* which I also use).