I have always wondered what to do with these files particularly when I
don't understand the application they apply to.
Clearly they're included for a reason.
By accepting in ignorance could I cause mayhem?

Regards
--
faeychild
Running kde on 6.6.43-desktop-1.mga9 kernel.
Mageia release 9 (Official) for x86_64

--- MBSE BBS v1.1.0 (Linux-x86_64)
* Origin: A noiseless patient Spider (2:250/1@fidonet)

Hello faeychild!

Wednesday August 07 2024 23:13, faeychild wrote to All:

I have always wondered what to do with these files particularly when I
don't understand the application they apply to. Clearly they're
included for a reason. By accepting in ignorance could I cause mayhem?

These usually like abcde.conf.rpmnew "Could" replace the original default
files of the same name (i..e., as abcde,conf) usually sitting in /etc but
could also be elsewhere.

You should look at them comparing the old (starting with - with the new
lines (starting with +).

Then you have the options of keep the old, keep the rpmnew (with that
final extension) or replace old with the new.


Have I explained it OK ?



Vincent


SEEN-BY: 25/0 21 250/0 1 2 3 4 5 8 13 14 15 263/0 362/6 467/4 712/1321

On 2024-08-07 18:13, faeychild wrote:

I have always wondered what to do with these files particularly when I
don't understand the application they apply to.
Clearly they're included for a reason.
By accepting in ignorance could I cause mayhem?

Regards

These usually concern config files, which Mageia avoids replacing
without user permission if possible.

Mayhem? That may be a little strong, but it depends on how heavily
customized your system is.

For example, the recent sddm update included a new config file.
Accepting it replaced the existing file, re-setting any settings you
might have made to the defaults. In my case, that meant autologin was
turned off, and I had to go to MCC to turn it back on again.

That was relatively benign, but another time I accepted an rpmnew for
sane, and promptly lost ability to access my scanner. I had to
re-install it to get it back.

Another sddm update, I think for Mageia 8, fixed a problem with the
defaults that sddm wasn't remembering the last user to log in. If you
left it alone, you had to input the user name each time. Accepting the
new config file fixed that, but again, any defaults that you may have
changed before the update had to be changed back again.

So, like many things, the answer of should you or shouldn't you do
anything is "it depends." Usually, the safest option is to leave it
alone, but by doing so you may miss out on fixing the issue that
prompted the update.

TJ

--- MBSE BBS v1.1.0 (Linux-x86_64)
* Origin: A noiseless patient Spider (2:250/1@fidonet)

The rpmnew is the new default file for the program that got updated. It
will Not contain all of the changes you made to that file in setting up
that program for your particular system. If you replace the old copy
with this new one (mv gabble.conf.rpmnew gabble.conf) you will lose all
of the changes you made to gabble.conf previously to get the program
gabble to behave the way you wanted it to. (for example, if you replaced wpa_supplicant.conf with wpa_supplicant.conf.rpmnew you would lose all
the passwords and wireless AP names stored in wpa_supplicant.conf. Since
I have about a hundred such setups--I travel a lot-- it would be a
disaster to lose them all.

However what you can do is to do a diff between them, and stick in the
new stuff in the .rpmnew file into the old file. if you (or your OS
never made any changes to the file, then repace the old with the new.

If you have no idea what that file is for (you have no idea what
gabble.conf is), do the diff to see what changes there are between the
two and then decide what you want to do. swap the new for the old, leave
the old in place, or copy the important changes in the new to the old,
or copy the changes made in the old by you or the OS to the new.




On 2024-08-08, TJ <TJ@noneofyour.business> wrote:

On 2024-08-07 18:13, faeychild wrote:

I have always wondered what to do with these files particularly when I
don't understand the application they apply to.
Clearly they're included for a reason.
By accepting in ignorance could I cause mayhem?

Regards

These usually concern config files, which Mageia avoids replacing
without user permission if possible.

Mayhem? That may be a little strong, but it depends on how heavily customized your system is.

For example, the recent sddm update included a new config file.
Accepting it replaced the existing file, re-setting any settings you
might have made to the defaults. In my case, that meant autologin was
turned off, and I had to go to MCC to turn it back on again.

That was relatively benign, but another time I accepted an rpmnew for
sane, and promptly lost ability to access my scanner. I had to
re-install it to get it back.

Another sddm update, I think for Mageia 8, fixed a problem with the
defaults that sddm wasn't remembering the last user to log in. If you
left it alone, you had to input the user name each time. Accepting the
new config file fixed that, but again, any defaults that you may have changed before the update had to be changed back again.

So, like many things, the answer of should you or shouldn't you do
anything is "it depends." Usually, the safest option is to leave it
alone, but by doing so you may miss out on fixing the issue that
prompted the update.

TJ

--- MBSE BBS v1.1.0 (Linux-x86_64)
* Origin: A noiseless patient Spider (2:250/1@fidonet)

On 8/8/24 22:39, TJ wrote:

So, like many things, the answer of should you or shouldn't you do
anything is "it depends." Usually, the safest option is to leave it
alone, but by doing so you may miss out on fixing the issue that
prompted the update.

TJ

I suspected much of this. Depends can strike terror.
But, OK If it's a program I don't use then leave it.
I think the last one was SSH which I haven't used and the config file
would be meaningless to me anyway

regards

--
faeychild
Running kde on 6.6.43-desktop-1.mga9 kernel.
Mageia release 9 (Official) for x86_64


--- MBSE BBS v1.1.0 (Linux-x86_64)
* Origin: A noiseless patient Spider (2:250/1@fidonet)

On 2024-08-08, faeychild <faeychild@nomail.afraid.org> wrote:

On 8/8/24 22:39, TJ wrote:

So, like many things, the answer of should you or shouldn't you do
anything is "it depends." Usually, the safest option is to leave it
alone, but by doing so you may miss out on fixing the issue that
prompted the update.

TJ

I suspected much of this. Depends can strike terror.
But, OK If it's a program I don't use then leave it.
I think the last one was SSH which I haven't used and the config file
would be meaningless to me anyway

I would strongly hope that if you use your computer to interact with
some other computer you use ssh to do so.

regards

--- MBSE BBS v1.1.0 (Linux-x86_64)
* Origin: A noiseless patient Spider (2:250/1@fidonet)

On 9/8/24 10:11, William Unruh wrote:

I would strongly hope that if you use your computer to interact with
some other computer you use ssh to do so.

regards

So would I. My interactions are through web portals.
Although Thunderbird uses SSL
These are the limits of my computer to computer interaction

regards
--
faeychild
Running kde on 6.6.43-desktop-1.mga9 kernel.
Mageia release 9 (Official) for x86_64


--- MBSE BBS v1.1.0 (Linux-x86_64)
* Origin: A noiseless patient Spider (2:250/1@fidonet)