Fwd: Update Issue

[Carlos AT]

Hello everyone, first time on this list.

I am on the 26 version and recentrly noticed that I wasn't getting the 
27 update. At first I tryied to check through the Software Center, 
which displays the the message:
> Unable to get list of updates

Then I attempted to update through the terminal. Got the following 
error even after cleanning the dnf:
> Problem: package kernel-modules-extra-4.11.8-200.fc25.x86_64 requires 
> kernel-uname-r = 4.11.8-200.fc25.x86_64

Could anybody help me out?

Update Issue

[Sam Varshavchik]

Carlos AT writes:
> Hello everyone, first time on this list.
>
> I am on the 26 version and recentrly noticed that I wasn't getting the
> 27 update. At first I tryied to check through the Software Center,
> which displays the the message:
> > Unable to get list of updates
>
> Then I attempted to update through the terminal. Got the following
> error even after cleanning the dnf:
> > Problem: package kernel-modules-extra-4.11.8-200.fc25.x86_64 requires
> > kernel-uname-r = 4.11.8-200.fc25.x86_64
>
> Could anybody help me out?

Perhaps that's because Fedora 27 is not released yet.

You also need to figure out which version of Fedora you're on. You claimed  
that you're on 26, but your error message indicates that you're on 25.

Update Issue

[Carlos AT]

I mistook the beta realese by the final one '---.  Thanks Sam.

I installed the 25th version last year and have upgraded to the 26th 
one when it was realesed. The old kernel still appear at the boot.

Follow a screenshot of the terminal.

On Sat, Nov 11, 2017 at 5:06 PM, Sam Varshavchik 
 wrote:
> Carlos AT writes:
> > Hello everyone, first time on this list.
> >
> > I am on the 26 version and recentrly noticed that I wasn't getting 
> > the
> > 27 update. At first I tryied to check through the Software Center,
> > which displays the the message:
> > > Unable to get list of updates
> >
> > Then I attempted to update through the terminal. Got the following
> > error even after cleanning the dnf:
> > > Problem: package kernel-modules-extra-4.11.8-200.fc25.x86_64
> >
> > requires
> > > kernel-uname-r = 4.11.8-200.fc25.x86_64
> >
> > Could anybody help me out?
>
> Perhaps that's because Fedora 27 is not released yet.
>
> You also need to figure out which version of Fedora you're on. You 
> claimed that you're on 26, but your error message indicates that 
> you're on 25.
> _______________________________________________
> users mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]

Update Issue

[Sam Varshavchik]

Carlos AT writes:
> I mistook the beta realese by the final one '---.  Thanks Sam.
>
> I installed the 25th version last year and have upgraded to the 26th
> one when it was realesed. The old kernel still appear at the boot.
>
> Follow a screenshot of the terminal.

My update-to-date 26 has only 4.13 kernels installed now. The kernel  
packages have been updated many times, and the 4.13 kernels are the only  
kernels anyone should have installed, on an up-to-date system, at this time.

The reference in your message to some 4.11 kernel package suggests to me  
that your packages got screwed up, at some point.

Each kernel version consists of, at least, three packages that have matching  
versions and releases: kernel, kernel-core, and kernel-modules. There are a  
few other optional subpackages, like kernel-headers, that might be installed.

Use the "uname -a" command to see which kernel version and release you  
successfully booted.

Use the "rpm -qa 'kernel*' | sort" command to see a list of kernel packages  
installed.

You will need to figure out which good kernel installs you have. At the bare  
minimum, you should have kernel, kernel-core, and kernel-modules packages  
installed for whatever kernel version 'uname -a' shows. That goes without  
saying, since you won't be able to boot, otherwise.

Then, ideally, you should have one or two earlier versions of the kernel  
also properly installed.

Any other 'kernel*' packages you see, especially the ones that are much  
older, are most certainly a result of some earlier upgrade problem you had,  
that left some garbage behind. You should be able to manually get rid of  
them with 'rpm -e'. Afterwards, "dnf upgrade" should be able to proceed.

Also, once 27 is released, "dnf upgrade" won't really upgrade you to 27. You  
will need to use fedup for that.

Update Issue

[Silvia Sánchez]

Hello,

There's a DNF plugin to update the system. More information here:
https://fedoramagazine.org/upgrading-fedora-25-fedora-26

Kind regards,
Silvia

On 12 November 2017 at 16:16, Sam Varshavchik  wrote:
> Carlos AT writes:
>
> I mistook the beta realese by the final one '---.  Thanks Sam.
> > I installed the 25th version last year and have upgraded to the 26th
> > one when it was realesed. The old kernel still appear at the boot.
> >
> > Follow a screenshot of the terminal.
>
> My update-to-date 26 has only 4.13 kernels installed now. The kernel
> packages have been updated many times, and the 4.13 kernels are the only
> kernels anyone should have installed, on an up-to-date system, at this time.
>
> The reference in your message to some 4.11 kernel package suggests to me
> that your packages got screwed up, at some point.
>
> Each kernel version consists of, at least, three packages that have
> matching versions and releases: kernel, kernel-core, and kernel-modules.
> There are a few other optional subpackages, like kernel-headers, that might
> be installed.
>
> Use the "uname -a" command to see which kernel version and release you
> successfully booted.
>
> Use the "rpm -qa 'kernel*' | sort" command to see a list of kernel
> packages installed.
>
> You will need to figure out which good kernel installs you have. At the
> bare minimum, you should have kernel, kernel-core, and kernel-modules
> packages installed for whatever kernel version 'uname -a' shows. That goes
> without saying, since you won't be able to boot, otherwise.
>
> Then, ideally, you should have one or two earlier versions of the kernel
> also properly installed.
>
> Any other 'kernel*' packages you see, especially the ones that are much
> older, are most certainly a result of some earlier upgrade problem you had,
> that left some garbage behind. You should be able to manually get rid of
> them with 'rpm -e'. Afterwards, "dnf upgrade" should be able to proceed.
>
> Also, once 27 is released, "dnf upgrade" won't really upgrade you to 27.
> You will need to use fedup for that.
>
> users mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]