Bug 30459 - drakrpm-update: message about which post-update configuration file to use is confusing
Summary: drakrpm-update: message about which post-update configuration file to use is ...
Status: REOPENED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 9
Hardware: All Linux
Priority: Normal minor
Target Milestone: ---
Assignee: Mageia tools maintainers
QA Contact:
URL: https://postimg.cc/HJg0gz0f
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-05-21 09:08 CEST by Omnio Torr
Modified: 2024-08-27 19:06 CEST (History)
2 users (show)

See Also:
Source RPM: rpmdrake-6.32-1.mga8.src.rpm
CVE:
Status comment:


Attachments
drakrpm message about config files (213.28 KB, image/png)
2022-05-21 09:10 CEST, Omnio Torr
Details
message about rpmnew (196.89 KB, image/png)
2022-07-26 09:51 CEST, Omnio Torr
Details

Description Omnio Torr 2022-05-21 09:08:24 CEST
Description of problem:


Of course, different users have different levels of knowledge about package management (and not all the users are native English speakers). Simplified, I guess, the theory sounds like: "rpmsave" files are always the old configuration files and "rpmnew" files are always the new files. But when a beginner user sees a message like "If unsure, keep the current file (remove .rpmsave)" (s)he might think that "the current file" means the existing (old) file - especially since the message suggests to "keep" it. Changing the message to something like "If unsure, use the new file (remove .rpmsave)" should avoid this confusion. 


Screenshot: https://postimg.cc/HJg0gz0f
Comment 1 Omnio Torr 2022-05-21 09:10:40 CEST
Created attachment 13265 [details]
drakrpm message about config files
Comment 2 Lewis Smith 2022-05-22 21:32:47 CEST
Thank you for the comment.
Indeed, I always thought "keep the current file (remove .rpmsave)" *did* mean 'keep what you previously had', despite the contrary implication of the last bit. The screenshot was useful: the whole message is admittedly not very clear.

Assigning to the Mageiatools group.

Summary: drakrpm-update: message about configuration files may be confusing => drakrpm-update: message about which post-update configuration file to use is confusing
Assignee: bugsquad => mageiatools
Severity: normal => minor

Comment 3 Morgan Leijström 2022-05-22 22:34:26 CEST
I have reported this previously as

Bug 4671 - Dialog about changed configuration files after updating is unclear - please rephrase

CC: (none) => fri

Comment 4 Barry Jackson 2022-05-23 12:33:12 CEST
There is also no explanation of what "do nothing" means.

I have always assumed that it changes nothing and keeps the original file.

This has always been and still is very confusing even for native English speakers.

/OT but related..
The graphical display used to initially show part of each file in view, with the available space split into 3 sections, but more recently it only shows the diff with the others collapsed, as in the screen shot at #1 above.

It is not at all obvious now that the other sections can be expanded and viewed especially if you have never seen it the original way.

CC: (none) => zen25000

Comment 5 Morgan Leijström 2022-05-23 13:36:35 CEST
Also the diff format is incomprehensible for normal users.

There should at least be a link to how to decode that, by normal eyes, mess.
Comment 6 Omnio Torr 2022-07-26 09:50:43 CEST
I'm attaching a second screenshot, this one showing the complementary case of the "rpmnew" file. Why am I doing this: in the first screenshot "the current file" refers to the new configuration file. However, in the second screenshot, "the current file" means the old configuration file. I guess we should either have a consistent meaning of the term "current" across cases or (better) get rid of "current" and use "old/new" instead.
Comment 7 Omnio Torr 2022-07-26 09:51:52 CEST
Created attachment 13349 [details]
message about rpmnew
Comment 8 Marja Van Waes 2024-08-22 23:01:15 CEST
We stopped supporting Mageia 8 almost 8 months ago 
https://blog.mageia.org/en/2023/12/30/mageia-8-end-of-life/

That means we also stopped fixing Mageia 8 bugs and that this bug report needs to be closed, regardless of whether it was fixed for Mageia 8 or not.

If this particular bug did not get fixed for Mageia 8, then we do regret that.

If this issue is still present in Mageia 9 or cauldron, then please reopen this report, write a comment and adjust the "Version:" field.

If you are not yet a member of one or our teams, then please consider becoming one. https://wiki.mageia.org/en/Contributing
Mageia is a community project, meaning that we, the users, make Mageia together.

The more active contributors we have, the more bug reports will get fixed.
Besides, being active in a team can be very rewarding. It was and is certainly rewarding to me :-D

Status: NEW => RESOLVED
Resolution: (none) => OLD

Comment 9 Omnio Torr 2024-08-27 17:43:03 CEST
Just these days I encountered these messages again (on Mageia 9, of course). Reopening.

Resolution: OLD => (none)
Version: 8 => 9
Status: RESOLVED => REOPENED

Comment 10 Morgan Leijström 2024-08-27 19:06:32 CEST
At least we should have a link to a wiki page on how to interprete the information.

Note You need to log in before you can comment on or make changes to this bug.