GUI update from 25 to 26, dnf still looking at f25 repos

[Richard Shaw]

I just upgraded my "spare" laptop (that's literally the hostname!) and I
ran into one small problem and one larger problem it seems.

The small problem. I keep my own repository of certain packages not
available through other means on my main desktop accessed though
autofs//nfs.

The software center was able to access the metadata during the download
phase but system-upgrade apparently didn't download the packages assuming
they were local. I remember filing a bug for this with fedup...

The bigger issue is everything says Fedora 26 (/etc/fedora-release) and
Gnome system information, but when I run dnf it's still looking at the
Fedora 25 repos.

Where does dnf look for $releasever?

Thanks,
Richard

[Ed Greshko]

On 07/16/17 20:09, Richard Shaw wrote:
> I just upgraded my "spare" laptop (that's literally the hostname!) and I ran into
> one small problem and one larger problem it seems.
>
> The small problem. I keep my own repository of certain packages not available
> through other means on my main desktop accessed though autofs//nfs.
>
> The software center was able to access the metadata during the download phase but
> system-upgrade apparently didn't download the packages assuming they were local. I
> remember filing a bug for this with fedup...
>
> The bigger issue is everything says Fedora 26 (/etc/fedora-release) and Gnome
> system information, but when I run dnf it's still looking at the Fedora 25 repos.
>
> Where does dnf look for $releasever?

Looking at the man page for dnf.conf

$releasever
          Refers to the release version of operating system  which  DNF  derives
          from information available in RPMDB.

Is it possible you have multiple entries for fedora-release?

Or, maybe a "rpmdb --rebuilddb" will fix things?

[Richard Shaw]

On Sun, Jul 16, 2017 at 8:31 AM, Ed Greshko  wrote:
> On 07/16/17 20:09, Richard Shaw wrote:
> > I just upgraded my "spare" laptop (that's literally the hostname!) and I
>
> ran into
> > one small problem and one larger problem it seems.
> >
> > The small problem. I keep my own repository of certain packages not
>
> available
> > through other means on my main desktop accessed though autofs//nfs.
> >
> > The software center was able to access the metadata during the download
>
> phase but
> > system-upgrade apparently didn't download the packages assuming they
>
> were local. I
> > remember filing a bug for this with fedup...
> >
> > The bigger issue is everything says Fedora 26 (/etc/fedora-release) and
>
> Gnome
> > system information, but when I run dnf it's still looking at the Fedora
>
> 25 repos.
> > Where does dnf look for $releasever?
>
> Looking at the man page for dnf.conf
>    $releasever
>       Refers to the release version of operating system  which  DNF
>
> derives
>           from information available in RPMDB.
>
> Is it possible you have multiple entries for fedora-release?

That was it! I guess system-upgrade uses a pretty big hammer and doesn't
worry about multiple packages being installed.

Thanks,
Richard

[Ed Greshko]

On 07/16/17 22:13, Richard Shaw wrote:
> On Sun, Jul 16, 2017 at 8:31 AM, Ed Greshko <[e-mail]
> > wrote:
> On 07/16/17 20:09, Richard Shaw wrote:
> > I just upgraded my "spare" laptop (that's literally the hostname!) and I ran into
> > one small problem and one larger problem it seems.
> >
> > The small problem. I keep my own repository of certain packages not available
> > through other means on my main desktop accessed though autofs//nfs.
> >
> > The software center was able to access the metadata during the download phase but
> > system-upgrade apparently didn't download the packages assuming they were
> local. I
> > remember filing a bug for this with fedup...
> >
> > The bigger issue is everything says Fedora 26 (/etc/fedora-release) and Gnome
> > system information, but when I run dnf it's still looking at the Fedora 25 repos.
> >
> > Where does dnf look for $releasever?
> >
>
> Looking at the man page for dnf.conf
>
>        $releasever
>           Refers to the release version of operating system  which  DNF  derives
>           from information available in RPMDB.
>
> Is it possible you have multiple entries for fedora-release?
>
>
> That was it! I guess system-upgrade uses a pretty big hammer and doesn't worry
> about multiple packages being installed.

Good...

You may want to run "dnf check --duplicates" to see if there are any additional
issues.  What happened to you should not have happened.  The operative word being
"should".  :-)

[Joe Zeff]

On 07/16/2017 05:09 AM, Richard Shaw wrote:
> The bigger issue is everything says Fedora 26 (/etc/fedora-release) and 
> Gnome system information, but when I run dnf it's still looking at the 
> Fedora 25 repos.
>
> Where does dnf look for $releasever?

I remember running across this, once.  It took me several readings of a 
man page, but I finally figured out that it looks at the version number 
of the .rpm, not what's actually in the file.  Run this:

dnf list installed fedora-release

and make sure you have the one for fc26 only, because if the database 
shows both fc25 and fc26, dnf will only look at the first one returned 
and think you're running F 25.