Upgrading from 23 to 24

[Frank Elsner]

Hello,

my upgrade attempt from Fedora 23 to Fedora 24 gave the folling error:

# dnf system-upgrade download --refresh --releasever=24
RPM Fusion for Fedora 24 - Free - Updates       453 kB/s | 185 kB     00:00    
Adobe Systems Incorporated                       10 kB/s | 1.8 kB     00:00    
RPM Fusion for Fedora 24 - Nonfree - Updates    340 kB/s |  95 kB     00:00    
RPM Fusion for Fedora 24 - Free                 506 kB/s | 260 kB     00:00    
RPM Fusion for Fedora 24 - Nonfree              248 kB/s |  62 kB     00:00    
Error: cannot install both kernel-PAE-4.6.4-301.fc24.i686 and
kernel-PAE-4.6.4-201.fc23.i686
(try to add '--allowerasing' to command line to replace conflicting packages)

Is it save to use the option '--allowerasing'?

4.6.4-201.fc23.i686+PAE, which would be deleted is the current running kernel.
When will the delete happen? Hopefully later with the "dnf system-upgrade
reboot".


Thanks in advance, 
Frank Elsner

[Jon Ingason]

Den 2016-07-28 kl. 10:47, skrev Frank Elsner:
>  Hello,
>  
>  my upgrade attempt from Fedora 23 to Fedora 24 gave the folling error:
>  
>  # dnf system-upgrade download --refresh --releasever=24
>  RPM Fusion for Fedora 24 - Free - Updates       453 kB/s | 185 kB     00:00    
>  Adobe Systems Incorporated                       10 kB/s | 1.8 kB     00:00    
>  RPM Fusion for Fedora 24 - Nonfree - Updates    340 kB/s |  95 kB     00:00    
>  RPM Fusion for Fedora 24 - Free                 506 kB/s | 260 kB     00:00    
>  RPM Fusion for Fedora 24 - Nonfree              248 kB/s |  62 kB     00:00    
>  Error: cannot install both kernel-PAE-4.6.4-301.fc24.i686 and
> kernel-PAE-4.6.4-201.fc23.i686
>  (try to add '--allowerasing' to command line to replace conflicting packages)
>  
>  Is it save to use the option '--allowerasing'?
>  
>  4.6.4-201.fc23.i686+PAE, which would be deleted is the current running kernel.
>  When will the delete happen? Hopefully later with the "dnf system-upgrade
> reboot". 
How many kernel is in /boot ?
Check the contents of /etc/dnf/dnf.conf. The parameter
"installonly_limit" is usually 3 just to guarantee that you don't delete
the running kernel.

Did you do "dnf update --refresh" before you started system upgrade?
>  
>  
>  Thanks in advance, 
>  Frank Elsner
>  --
>  users mailing list
>  users(a)lists.fedoraproject.org
>  To unsubscribe or change subscription options:
>  https://lists.fedoraproject.org/admin/lists/[e-mail]
>  Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
>  Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
>  Have a question? Ask away: http://ask.fedoraproject.org
>   

-- 
Regards

Jon Ingason

[Frank Elsner]

On Thu, 28 Jul 2016 11:20:23 +0200 Jon Ingason wrote:
>  Den 2016-07-28 kl. 10:47, skrev Frank Elsner:
>  > Hello,
>  > 
>  > my upgrade attempt from Fedora 23 to Fedora 24 gave the folling error:
>  > 
>  > # dnf system-upgrade download --refresh --releasever=24
>  > RPM Fusion for Fedora 24 - Free - Updates       453 kB/s | 185 kB     00:00    
>  > Adobe Systems Incorporated                       10 kB/s | 1.8 kB     00:00    
>  > RPM Fusion for Fedora 24 - Nonfree - Updates    340 kB/s |  95 kB     00:00    
>  > RPM Fusion for Fedora 24 - Free                 506 kB/s | 260 kB     00:00    
>  > RPM Fusion for Fedora 24 - Nonfree              248 kB/s |  62 kB     00:00    
>  > Error: cannot install both kernel-PAE-4.6.4-301.fc24.i686 and
> kernel-PAE-4.6.4-201.fc23.i686
>  > (try to add '--allowerasing' to command line to replace conflicting
> packages)
>  > 
>  > Is it save to use the option '--allowerasing'?
>  > 
>  > 4.6.4-201.fc23.i686+PAE, which would be deleted is the current running kernel.
>  > When will the delete happen? Hopefully later with the "dnf system-upgrade
> reboot".
>  
>  How many kernel is in /boot ? 
# ls -1 /boot/vm*
/boot/vmlinuz-0-rescue-3b68290512b34ff1a95c8473ec84025a
/boot/vmlinuz-4.5.7-200.fc23.i686+PAE
/boot/vmlinuz-4.5.7-202.fc23.i686+PAE
/boot/vmlinuz-4.6.4-201.fc23.i686+PAE

# uname -r
4.6.4-201.fc23.i686+PAE

>  Check the contents of /etc/dnf/dnf.conf. The parameter
>  "installonly_limit" is usually 3 just to guarantee that you don't delete
>  the running kernel. 
installonly_limit=3

>  Did you do "dnf update --refresh" before you started system
> upgrade? 
Yes.


--Frank Elsner

[Jon Ingason]

Den 2016-07-28 kl. 12:09, skrev Frank Elsner:
>  On Thu, 28 Jul 2016 11:20:23 +0200 Jon Ingason wrote:
> > Den 2016-07-28 kl. 10:47, skrev Frank Elsner:
> >> Hello,
> >>
> >> my upgrade attempt from Fedora 23 to Fedora 24 gave the folling error:
> >>
> >> # dnf system-upgrade download --refresh --releasever=24
> >> RPM Fusion for Fedora 24 - Free - Updates       453 kB/s | 185 kB     00:00    
> >> Adobe Systems Incorporated                       10 kB/s | 1.8 kB     00:00    
> >> RPM Fusion for Fedora 24 - Nonfree - Updates    340 kB/s |  95 kB     00:00    
> >> RPM Fusion for Fedora 24 - Free                 506 kB/s | 260 kB     00:00    
> >> RPM Fusion for Fedora 24 - Nonfree              248 kB/s |  62 kB     00:00    
> >> Error: cannot install both kernel-PAE-4.6.4-301.fc24.i686 and
> kernel-PAE-4.6.4-201.fc23.i686
> >> (try to add '--allowerasing' to command line to replace conflicting
> packages)
> >>
> >> Is it save to use the option '--allowerasing'?
> >>
> >> 4.6.4-201.fc23.i686+PAE, which would be deleted is the current running kernel.
> >> When will the delete happen? Hopefully later with the "dnf system-upgrade
> reboot".
> >
> > How many kernel is in /boot ?
>  
>  # ls -1 /boot/vm*
>  /boot/vmlinuz-0-rescue-3b68290512b34ff1a95c8473ec84025a
>  /boot/vmlinuz-4.5.7-200.fc23.i686+PAE
>  /boot/vmlinuz-4.5.7-202.fc23.i686+PAE
>  /boot/vmlinuz-4.6.4-201.fc23.i686+PAE
>  
>  # uname -r
>  4.6.4-201.fc23.i686+PAE
>  
> > Check the contents of /etc/dnf/dnf.conf. The parameter
> > "installonly_limit" is usually 3 just to guarantee that you don't
> delete
> > the running kernel.
>  
>  installonly_limit=3
>  
> > Did you do "dnf update --refresh" before you started system upgrade?
>  
>  Yes.
>  
>  
>  --Frank Elsner
>   
Well then I would add "--allowerasing".

-- 
Regards

Jon Ingason

[Jaroslav Mracek]

I have a question to your request:

Do you have in /etc/dnf/dnf.conf following line:

installonly_limit=3

Did you made ``dnf upgrade --fresh`` before system-upgrade attempt?

Do you run the newest kernel on your system?

If some of the answers were no it could be a reason why you have the issue. 

If you will upgrade running kernel the replacement should take place during the reboot,
therefore theoretically it should be save. 

On other hand any time when you perform the system-upgrade you have to consider a risk of
malfunction of your upgraded system. Therefore back-up or snapshot could be handy.

Jaroslav



> Hello,
>
> my upgrade attempt from Fedora 23 to Fedora 24 gave the folling error:
>
> .# dnf system-upgrade download --refresh --releasever=24
> RPM Fusion for Fedora 24 - Free - Updates       453 kB/s | 185 kB     00:00    
> Adobe Systems Incorporated                       10 kB/s | 1.8 kB     00:00    
> RPM Fusion for Fedora 24 - Nonfree - Updates    340 kB/s |  95 kB     00:00    
> RPM Fusion for Fedora 24 - Free                 506 kB/s | 260 kB     00:00    
> RPM Fusion for Fedora 24 - Nonfree              248 kB/s |  62 kB     00:00    
> Error: cannot install both kernel-PAE-4.6.4-301.fc24.i686 and
> kernel-PAE-4.6.4-201.fc23.i686
> (try to add '--allowerasing' to command line to replace conflicting packages)
>
> Is it save to use the option '--allowerasing'?
>
> 4.6.4-201.fc23.i686+PAE, which would be deleted is the current running kernel.
> When will the delete happen? Hopefully later with the "dnf system-upgrade
> reboot".
>
>  
Thanks in advance, 
Frank Elsner
--
users mailing list
users(a)lists.fedoraproject.org
To unsubscribe or change subscription options:
https://lists.fedoraproject.org/admin/lists/[e-mail]
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

[Frank Elsner]

On Thu, 28 Jul 2016 05:57:57 -0400 (EDT) Jaroslav Mracek wrote:
>  I have a question to your request:
>  
>  Do you have in /etc/dnf/dnf.conf following line:
>  
>  installonly_limit=3 
Yes.

>  Did you made ``dnf upgrade --fresh`` before system-upgrade attempt?
Yes

>  Do you run the newest kernel on your system? 
Yes

>  If some of the answers were no it could be a reason why you have the
> issue. 
>  
>  If you will upgrade running kernel the replacement should take place during the reboot,
> therefore theoretically it should be save.  
Sounds good.

>  On other hand any time when you perform the system-upgrade you have
> to consider a risk of malfunction of your upgraded system. Therefore back-up or snapshot
> could be handy. 
Of course.


--Frank Elsner

[Frank Elsner]

On Thu, 28 Jul 2016 12:16:03 +0200 Frank Elsner wrote:
>  On Thu, 28 Jul 2016 05:57:57 -0400 (EDT) Jaroslav Mracek wrote:
>  > I have a question to your request:
>  > 
>  > Do you have in /etc/dnf/dnf.conf following line:
>  > 
>  > installonly_limit=3
>  
>  Yes.
>  
>  > Did you made ``dnf upgrade --fresh`` before system-upgrade attempt?
>  
>  Yes
>  
>  > Do you run the newest kernel on your system?
>  
>  Yes
>  
>  > If some of the answers were no it could be a reason why you have the issue. 
>  > 
>  > If you will upgrade running kernel the replacement should take place during the
> reboot, therefore theoretically it should be save. 
>  
>  Sounds good. 
Let me add: 

After "dnf system-upgrade download --refresh --releasever=24 --allowerasing"
I still have the running kernel in /boot.

Therefore it IS save.


Thanks to all, Frank

[Samuel Sieb]

On 07/28/2016 06:01 AM, Frank Elsner wrote:
>  After "dnf system-upgrade download --refresh --releasever=24
> --allowerasing"
>  I still have the running kernel in /boot.
>  
That's because the upgrade hasn't actually been run yet.  All that does 
is download the packages to the hard drive.  I'm a little concerned that 
the upgrade will actually fail because the running kernel during the 
upgrade process will be the one that is supposed to be erased.

I wonder why there's a conflict between the kernel packages.