wi-fi question

[David]

Trying to update my Rawhide WS install from a wi-fi connection.

A generic ping-test alleges I have a 16.24 Mbps average download speed.

I am getting some curl errors when I try to update, and something about
mirrors not
found or Rawhide Modular not found.

I would assume they are temporarily down.

However, all three browsers I am using are acting flakey, especially with
Gmail.    Chromium
crashes quickly.    I am in Gnome Web now.

Any suggestions ?

David Locklear

[David]

For whatever reason, dnf update eventually worked ( another self-healed
cure ? )

Anyways, here are two errors:

Upgrading        : grub2-efi-x64-1:2.06~rc1-3.fc35.x86_64
                                    159/498
                               warning: /boot/grub2/grubenv created as
/boot/grub2/grubenv.rpmnew

Upgrading        : grub2-efi-x64-1:2.06~rc1-3.fc35.x86_64
                                      159/498
                                 warning: /boot/grub2/grubenv created as
/boot/grub2/grubenv.rpmnew

250 packages updated.

Is it safe to re-start, or should I leave the computer on and do another
update tomorrow ?

That was likely the largest wi-fi update I have ever done.      I used to
have a reliable access to ethernet
before the COVID hysteria.

David Locklear

[Richard Ryniker]

>  Upgrading        : grub2-efi-x64-1:2.06~rc1-3.fc35.x86_64                                                 159/498 
>                           warning: /boot/grub2/grubenv created as /boot/grub2/grubenv.rpmnew
>
>   Upgrading        : grub2-efi-x64-1:2.06~rc1-3.fc35.x86_64                                                 159/498 
>                             warning: /boot/grub2/grubenv created as /boot/grub2/grubenv.rpmnew

I do not think these are errors.  I have seen similar warnings in the
past, and think this just indicates some file in the new package would
replace an earlier file that appears to contain some modifications.
Instead of replacing the (possibly modified) file, the new version is
stored with the ".rpmnew" suffix.  The user can then explore the
difference between the old and new files, and decide what should be done.

The purpose is surely to prevent an update causing something to break
due to loss of local configuration data.

This is why we see a modern preference to place local configuration data
in small files added to something-or-other-conf.d directories.  Because
these pieces are new (i.e. not part of a package, but local to a system)
and dynamically included by a configuratioin process, they will not
produce this warning message when a package update occurs.

[stan]

On Sat, 27 Mar 2021 17:56:08 -0400
Richard Ryniker  wrote:
> > From David, not quoted:
> >      Upgrading        : grub2-efi-x64-1:2.06~rc1-3.fc35.x86_64
> >                                            159/498 warning:
> > /boot/grub2/grubenv created as /boot/grub2/grubenv.rpmnew
> >   Upgrading        : grub2-efi-x64-1:2.06~rc1-3.fc35.x86_64
> >                                         159/498 warning:
> >
> > /boot/grub2/grubenv created as /boot/grub2/grubenv.rpmnew
>
> I do not think these are errors.  I have seen similar warnings in the
> past, and think this just indicates some file in the new package would
> replace an earlier file that appears to contain some modifications.
> Instead of replacing the (possibly modified) file, the new version is
> stored with the ".rpmnew" suffix.  The user can then explore the
> difference between the old and new files, and decide what should be
> done.
>
> The purpose is surely to prevent an update causing something to break
> due to loss of local configuration data.
>
> This is why we see a modern preference to place local configuration
> data in small files added to something-or-other-conf.d directories.
> Because these pieces are new (i.e. not part of a package, but local
> to a system) and dynamically included by a configuratioin process,
> they will not produce this warning message when a package update
> occurs.

This.  There is a command that the user can run after the update, and
it will find all of these and present them to the user with a little
mini menu with single letter commands, like D for a diff of the two
configuration files, accept the new one, retain the old one, etc.

[Ed Greshko]

On 29/03/2021 03:03, stan via test wrote:
> This.  There is a command that the user can run after the update, and
> it will find all of these and present them to the user with a little
> mini menu with single letter commands

The command you reference is rpmconf.

[stan]

On Mon, 29 Mar 2021 03:37:56 +0800
Ed Greshko  wrote:
> On 29/03/2021 03:03, stan via test wrote:
> > This.  There is a command that the user can run after the update,
> > and it will find all of these and present them to the user with a
> > little mini menu with single letter commands
>
> The command you reference is rpmconf.

Thanks Ed, I couldn't remember it, even though I remembered using it
after I saw it mentioned on the mailing list.