12:24 p.m.
I tried to update my Operative system (fedora 32) to new version fedora 34
After the execution of the automatic procedure (download and restart) .
On the information .... the computer show still : (Fedora 32 Workstation
Edition) ...
Why is this happening ..
What does this mean ??
Thank you for having some information about it ...
Angelo
7:10 a.m.
it is someone that can give me a clue to understand because after I
upgraded Fedora to 34,
I still continue to read Fedora 32 on the information <the setting> of my
computer ?
Is it really still Fedora 32 or is it only a bad information, that I
receive ?
Thank you
Angelo
On Fri, May 14, 2021 at 8:24 PM Angelo Moreschini <mrangelo.fedora(a)gmail.com>
wrote:
I tried to update my Operative system (fedora 32) to new version
fedora 34
After the execution of the automatic procedure (download and restart) .
On the information .... the computer show still : (Fedora 32 Workstation
Edition) ...
Why is this happening ..
What does this mean ??
Thank you for having some information about it ...
Angelo
7:28 a.m.
2021-05-16 14:10 UTC+02:00, Angelo Moreschini <mrangelo.fedora(a)gmail.com>:
it is someone that can give me a clue to understand because after I
upgraded Fedora to 34,
I still continue to read Fedora 32 on the information <the setting> of my
computer ?
Is it really still Fedora 32 or is it only a bad information, that I
receive ?
What does
cat /etc/redhat-release
say?
Did you follow the instructions here:
https://docs.fedoraproject.org/en-US/quick-docs/dnf-system-upgrade/ ?
Andras
12:36 a.m.
thank you Andras,
The answer is :
*<Fedora release 32 (Thirty Two)>*
seems the upgrading didn't work ...
--------------
I used automatic upgrading for get Fedora 30, 31 and Fedora 32.. ,
In these cas I simply pushed the <button> <Restart & Update>, that is
down
the label
<Fedora xx Now Available>...
---
For upgrading to Fedora 34 that is no good (why ?).
Can you suggest to me how I can better control the automatic process (to
upgrading) ??
Thank you
Angelo
On Sun, May 16, 2021 at 3:29 PM Andras Simon <szajmi(a)gmail.com> wrote:
2021-05-16 14:10 UTC+02:00, Angelo Moreschini
<mrangelo.fedora(a)gmail.com>:
> it is someone that can give me a clue to understand because after I
> upgraded Fedora to 34,
> I still continue to read Fedora 32 on the information <the setting> of my
> computer ?
>
> Is it really still Fedora 32 or is it only a bad information, that I
> receive ?
What does
cat /etc/redhat-release
say?
Did you follow the instructions here:
https://docs.fedoraproject.org/en-US/quick-docs/dnf-system-upgrade/ ?
Andras
_______________________________________________
users mailing list -- users(a)lists.fedoraproject.org
To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam on the list, report it:
https://pagure.io/fedora-infrastructure
12:59 a.m.
On 20/05/2021 13:36, Angelo Moreschini wrote:
thank you Andras,
The answer is :
_*<Fedora release 32 (Thirty Two)>*_
seems the upgrading didn't work ...
--------------
I used automatic upgrading for get Fedora 30, 31 and Fedora 32.. ,
In these cas I simply pushed the <button> <Restart & Update>, that is
down the label
<Fedora xx Now Available>...
---
For upgrading to Fedora 34 that is no good (why ?).
Can you suggest to me how I can better control the automatic process (to upgrading) ??
Are you using the Workstation edition of Fedora? And, if so, are you using the GUI of
Gnome
to perform the upgrade?
I don't use that method since I prefer to watch as much of the process as possible.
You may also wish to go from F32 to F33 first.
What I would do you your case is the following.
From a terminal session.....
sudo dnf update (to make sure your current system is fully updated)
sudo dnf install dnf-plugin-system-upgrade (just to make sure you have the plug-in
installed)
if packages have been updated, then reboot just to make sure changes have taken
effect.
Then, again from the terminal.
sudo dnf system-upgrade download --releasever=34 (or 33 if you want to do it in
increments)
when complete
sudo dnf system-upgrade reboot
The system will boot and show the F32 kernel to start with but the upgrade process should
begin.
Consult https://docs.fedoraproject.org/en-US/quick-docs/dnf-system-upgrade/ if a package
issue is
preventing the upgrade from proceeding without additional parameters being added to the
upgrade
command. A common problem is an issue with a non-fedora repo/package.
--
Remind me to ignore comments which aren't germane to the thread.
8:49 a.m.
thank you very much Ed,
I made the manual procedure..,
(using the shutdown -r now -to reboot after sudo dnf system-upgrade
download --releasever=33 )
but after I give the last command :<sudo dnf system-upgrade reboot>
I got the error message : :
\Error: system is not ready for upgrade
:-(
I remember that I renounced to upgrade to Fedora 33
because I had already this problem
...
what it is possible to do ??
thank you
Angelo
On Thu, May 20, 2021 at 8:59 AM Ed Greshko <ed.greshko(a)greshko.com> wrote:
On 20/05/2021 13:36, Angelo Moreschini wrote:
> thank you Andras,
>
> The answer is :
> _*<Fedora release 32 (Thirty Two)>*_
>
> seems the upgrading didn't work ...
> --------------
> I used automatic upgrading for get Fedora 30, 31 and Fedora 32.. ,
> In these cas I simply pushed the <button> <Restart & Update>, that
is
down the label
> <Fedora xx Now Available>...
> ---
> For upgrading to Fedora 34 that is no good (why ?).
>
> Can you suggest to me how I can better control the automatic process (to
upgrading) ??
Are you using the Workstation edition of Fedora? And, if so, are you using
the GUI of Gnome
to perform the upgrade?
I don't use that method since I prefer to watch as much of the process as
possible.
You may also wish to go from F32 to F33 first.
What I would do you your case is the following.
From a terminal session.....
sudo dnf update (to make sure your current system is fully updated)
sudo dnf install dnf-plugin-system-upgrade (just to make sure you have
the plug-in installed)
if packages have been updated, then reboot just to make sure changes have
taken
effect.
Then, again from the terminal.
sudo dnf system-upgrade download --releasever=34 (or 33 if you want to do
it in increments)
when complete
sudo dnf system-upgrade reboot
The system will boot and show the F32 kernel to start with but the upgrade
process should begin.
Consult
https://docs.fedoraproject.org/en-US/quick-docs/dnf-system-upgrade/ if a
package issue is
preventing the upgrade from proceeding without additional parameters being
added to the upgrade
command. A common problem is an issue with a non-fedora repo/package.
--
Remind me to ignore comments which aren't germane to the thread.
_______________________________________________
users mailing list -- users(a)lists.fedoraproject.org
To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam on the list, report it:
https://pagure.io/fedora-infrastructure
8:55 a.m.
On 20/05/2021 21:49, Angelo Moreschini wrote:
thank you very much Ed,
I made the manual procedure..,
(using the shutdown -r now -to reboot after sudo dnf system-upgrade download
--releasever=33 )
but after I give the last command :<sudo dnf system-upgrade reboot>
I got the error message : :
\Error: system is not ready for upgrade
:-(
I remember that I renounced to upgrade to Fedora 33
because I had already this problem
...
what it is possible to do ??
Oh, so you've seen this error before?
The error message is seems rather vague. Is there anything in the journal that may shed
some light?
How about your current disk space?
--
Remind me to ignore comments which aren't germane to the thread.
11:29 a.m.
this is the situation... :
angelo_dev@pluto:~$ df
Filesystem 1K-blocks Used Available Use%
Mounted on
devtmpfs 4020632 0 4020632 0%
/dev
tmpfs 4039784 21324 4018460 1%
/dev/shm
tmpfs 4039784 1876 4037908 1%
/run
/dev/mapper/fedora_localhost--live-root 71724152 59738420 8299332 88% /
tmpfs 4039784 108 4039676 1%
/tmp
/dev/sdb3 999320 233288 697220 26%
/boot
/dev/mapper/fedora_localhost--live-home 131562500 23224776 101611684 19%
/home
/dev/sdb2 204580 20884 183696 11%
/boot/efi
tmpfs 807956 136 807820 1%
/run/user/1000
/dev/sdc1 15622672 828656 14794016 6%
/run/media/angelo_dev/F772-9C6B
What can you suggest ?
On Thu, May 20, 2021 at 4:56 PM Ed Greshko <ed.greshko(a)greshko.com> wrote:
On 20/05/2021 21:49, Angelo Moreschini wrote:
> thank you very much Ed,
>
> I made the manual procedure..,
> (using the shutdown -r now -to reboot after sudo dnf system-upgrade
download --releasever=33 )
>
> but after I give the last command :<sudo dnf system-upgrade reboot>
> I got the error message : :
> \Error: system is not ready for upgrade
>
>
> :-(
>
> I remember that I renounced to upgrade to Fedora 33
> because I had already this problem
>
> ...
> what it is possible to do ??
Oh, so you've seen this error before?
The error message is seems rather vague. Is there anything in the journal
that may shed
some light?
How about your current disk space?
--
Remind me to ignore comments which aren't germane to the thread.
_______________________________________________
users mailing list -- users(a)lists.fedoraproject.org
To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam on the list, report it:
https://pagure.io/fedora-infrastructure
1 p.m.
On 21/05/2021 00:29, Angelo Moreschini wrote:
this is the situation... :
angelo_dev@pluto:~$ df
Filesystem 1K-blocks Used Available Use% Mounted on
devtmpfs 4020632 0 4020632 0% /dev
tmpfs 4039784 21324 4018460 1% /dev/shm
tmpfs 4039784 1876 4037908 1% /run
/dev/mapper/fedora_localhost--live-root 71724152 59738420 8299332 88% /
tmpfs 4039784 108 4039676 1% /tmp
/dev/sdb3 999320 233288 697220 26% /boot
/dev/mapper/fedora_localhost--live-home 131562500 23224776 101611684 19% /home
/dev/sdb2 204580 20884 183696 11% /boot/efi
tmpfs 807956 136 807820 1% /run/user/1000
/dev/sdc1 15622672 828656 14794016 6%
/run/media/angelo_dev/F772-9C6B
What can you suggest ?
That looks fine.
I did forget to ask a question.
When you ran
sudo dnf system-upgrade download --releasever=33
What was the output after that command finished?
--
Remind me to ignore comments which aren't germane to the thread.
10:33 p.m.
On 21/05/2021 02:00, Ed Greshko wrote:
On 21/05/2021 00:29, Angelo Moreschini wrote:
> this is the situation... :
>
> angelo_dev@pluto:~$ df
> Filesystem 1K-blocks Used Available Use% Mounted on
> devtmpfs 4020632 0 4020632 0% /dev
> tmpfs 4039784 21324 4018460 1% /dev/shm
> tmpfs 4039784 1876 4037908 1% /run
> /dev/mapper/fedora_localhost--live-root 71724152 59738420 8299332 88% /
> tmpfs 4039784 108 4039676 1% /tmp
> /dev/sdb3 999320 233288 697220 26% /boot
> /dev/mapper/fedora_localhost--live-home 131562500 23224776 101611684 19% /home
> /dev/sdb2 204580 20884 183696 11% /boot/efi
> tmpfs 807956 136 807820 1%
/run/user/1000
> /dev/sdc1 15622672 828656 14794016 6%
/run/media/angelo_dev/F772-9C6B
>
> What can you suggest ?
That looks fine.
I did forget to ask a question.
When you ran
sudo dnf system-upgrade download --releasever=33
What was the output after that command finished?
FWIW, I am upgrading an F32 VM to F33 and you should see....
Running transaction check
Transaction check succeeded.
Running transaction test
Transaction test succeeded.
Complete!
Transaction saved to /var/lib/dnf/system-upgrade/system-upgrade-transaction.json.
Download complete! Use 'dnf system-upgrade reboot' to start the upgrade.
To remove cached metadata and transaction use 'dnf system-upgrade clean'
The downloaded packages were saved in cache until the next successful transaction.
You can remove cached packages by executing 'dnf clean packages'.
--
Remind me to ignore comments which aren't germane to the thread.
3:22 a.m.
reading the documentation (
https://docs.fedoraproject.org/en-US/quick-docs/dnf-system-upgrade/) I see
there can be dependencies problems.
the option < --allowerasing> allows to delete SW that can give problems....
I have to try this even if it is dangerous
but before that I need a good backup of my data ... and so I have to
postpone the upgrade of fedora.
Thank you for trying to help me :-)
Angelo
On Fri, May 21, 2021 at 6:34 AM Ed Greshko <ed.greshko(a)greshko.com> wrote:
On 21/05/2021 02:00, Ed Greshko wrote:
> On 21/05/2021 00:29, Angelo Moreschini wrote:
>> this is the situation... :
>>
>> angelo_dev@pluto:~$ df
>> Filesystem 1K-blocks Used Available
Use% Mounted on
>> devtmpfs 4020632 0 4020632 0%
/dev
>> tmpfs 4039784 21324 4018460 1%
/dev/shm
>> tmpfs 4039784 1876 4037908 1%
/run
>> /dev/mapper/fedora_localhost--live-root 71724152 59738420 8299332 88%
/
>> tmpfs 4039784 108 4039676 1%
/tmp
>> /dev/sdb3 999320 233288 697220 26%
/boot
>> /dev/mapper/fedora_localhost--live-home 131562500 23224776 101611684
19% /home
>> /dev/sdb2 204580 20884 183696 11%
/boot/efi
>> tmpfs 807956 136 807820 1%
/run/user/1000
>> /dev/sdc1 15622672 828656 14794016
6% /run/media/angelo_dev/F772-9C6B
>>
>> What can you suggest ?
>
> That looks fine.
>
> I did forget to ask a question.
>
> When you ran
>
> sudo dnf system-upgrade download --releasever=33
>
> What was the output after that command finished?
>
FWIW, I am upgrading an F32 VM to F33 and you should see....
Running transaction check
Transaction check succeeded.
Running transaction test
Transaction test succeeded.
Complete!
Transaction saved to
/var/lib/dnf/system-upgrade/system-upgrade-transaction.json.
Download complete! Use 'dnf system-upgrade reboot' to start the upgrade.
To remove cached metadata and transaction use 'dnf system-upgrade clean'
The downloaded packages were saved in cache until the next successful
transaction.
You can remove cached packages by executing 'dnf clean packages'.
--
Remind me to ignore comments which aren't germane to the thread.
_______________________________________________
users mailing list -- users(a)lists.fedoraproject.org
To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam on the list, report it:
https://pagure.io/fedora-infrastructure
3:27 a.m.
On 2021-05-21 1:22 a.m., Angelo Moreschini wrote:
reading the documentation
(https://docs.fedoraproject.org/en-US/quick-docs/dnf-system-upgrade/
<https://docs.fedoraproject.org/en-US/quick-docs/dnf-system-upgrade/>) I
see there can be dependencies problems.
the option < |--allowerasing> allows to delete SW that can give
problems....
|
|I have to try this even if it is dangerous|
It's not really dangerous. It will show you a list of what will be
deleted and unless you've been doing strange things, it won't be
deleting anything critical. I have often had to add that option for
upgrades.
|but before that I need a good backup of my data ... and so I have to
postpone the upgrade of fedora.|
A backup is always a good idea.
4:25 a.m.
On 21/05/2021 16:22, Angelo Moreschini wrote:
reading the documentation
(https://docs.fedoraproject.org/en-US/quick-docs/dnf-system-upgrade/
<https://docs.fedoraproject.org/en-US/quick-docs/dnf-system-upgrade/>) I see there
can be dependencies problems.
the option < |--allowerasing> allows to delete SW that can give problems....
|
|
|
|I have to try this even if it is dangerous|
|but before that I need a good backup of my data ... and so I have to postpone the
upgrade of fedora.|
|
|
|Thank you for trying to help me :-)|
If you post the output showing the actual errors it will make it easier for others on the
list to suggest solutions.
Ed
--
Remind me to ignore comments which aren't germane to the thread.
3:33 p.m.
On 5/20/21 6:49 AM, Angelo Moreschini wrote:
(using the shutdown -r now -to reboot after sudo dnf system-upgrade
download --releasever=33 )
but after I give the last command :<sudo dnf system-upgrade reboot>
I got the error message : :
\Error: system is not ready for upgrade
There is a bug report that suggests that the error message you're
describing can occur if "sudo dnf system-upgrade reboot" is not the step
immediately following "sudo dnf system-upgrade download".
https://github.com/rpm-software-management/dnf-plugin-system-upgrade/issu...
I don't see the output of "sudo dnf system-upgrade download
--releasever=34" on your system in this thread. If there were conflicts
that require --allowerasing, you should see them there. Could you post
the output of the download command? (And if it doesn't report any
errors, then run "sudo dnf system-upgrade reboot" next.)
1076
days inactive
1084
days old
13 comments
5 participants
participants (5)
-
Andras Simon -
Angelo Moreschini -
Ed Greshko -
Gordon Messmer -
Samuel Sieb