I just noticed that my newly upgraded system is still checking the Fedora 35 repos when I run 'dnf update'. Not confirmed yet, but I suspect it's because I still have fedora-release-35 installed.
$ rpm -q fedora-release fedora-release-35-36.noarch fedora-release-36-17.noarch
Anyone else seen this?
On 5/14/22 12:25, Ian Pilcher wrote:
I just noticed that my newly upgraded system is still checking the Fedora 35 repos when I run 'dnf update'. Not confirmed yet, but I suspect it's because I still have fedora-release-35 installed.
$ rpm -q fedora-release fedora-release-35-36.noarch fedora-release-36-17.noarch
Anyone else seen this?
I haven't upgraded yet, but you're right about what's happening. Instead of checking the contents of /etc/fedora-release, it just checks to see which version is installed. If, for some reason, the older version isn't removed from the database, it will see it first and assume that's the version of Fedora you're using. Just remove the older version (which isn't really installed anyway) and you're good to go.
On 5/14/22 15:00, Joe Zeff wrote:
I haven't upgraded yet, but you're right about what's happening. Instead of checking the contents of /etc/fedora-release, it just checks to see which version is installed. If, for some reason, the older version isn't removed from the database, it will see it first and assume that's the version of Fedora you're using. Just remove the older version (which isn't really installed anyway) and you're good to go.
On further examination, I had a whole bunch of duplicate packages in the RPM database. It looks as if none of the old FC35 packages were removed from the database during the upgrade. Very odd.
Fortunately, 'dnf reinstall --allowerasing `rpm -qa | grep fc36`' seems to have cleaned things up.
On Sat, 2022-05-14 at 16:25 -0500, Ian Pilcher wrote:
On 5/14/22 15:00, Joe Zeff wrote:
I haven't upgraded yet, but you're right about what's happening. Instead of checking the contents of /etc/fedora-release, it just checks to see which version is installed. If, for some reason, the older version isn't removed from the database, it will see it first and assume that's the version of Fedora you're using. Just remove the older version (which isn't really installed anyway) and you're good to go.
On further examination, I had a whole bunch of duplicate packages in the RPM database. It looks as if none of the old FC35 packages were removed from the database during the upgrade. Very odd.
Fortunately, 'dnf reinstall --allowerasing `rpm -qa | grep fc36`' seems to have cleaned things up.
You can find duplicates with this (from the Release Notes):
$ sudo dnf repoquery --duplicates
poc
On 5/14/22 14:25, Ian Pilcher wrote:
On 5/14/22 15:00, Joe Zeff wrote:
I haven't upgraded yet, but you're right about what's happening. Instead of checking the contents of /etc/fedora-release, it just checks to see which version is installed. If, for some reason, the older version isn't removed from the database, it will see it first and assume that's the version of Fedora you're using. Just remove the older version (which isn't really installed anyway) and you're good to go.
On further examination, I had a whole bunch of duplicate packages in the RPM database. It looks as if none of the old FC35 packages were removed from the database during the upgrade. Very odd.
That sounds like something failed during the upgrade. Can you check the logs? There's a system-upgrade command that finds the right logs for you. "dnf system-upgrade log"
-
Ian Pilcher -
Joe Zeff -
Patrick O'Callaghan -
Samuel Sieb