Bug 1213959 - Previously Used Repositories status display is now missing "Disable"
Summary: Previously Used Repositories status display is now missing "Disable"
Status: RESOLVED FIXED
Alias: None
Product: openSUSE Distribution
Classification: openSUSE
Component: Installation (show other bugs)
Version: Leap 15.5
Hardware: x86-64 openSUSE Leap 15.5
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: E-mail List
QA Contact: Jiri Srain
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-08-03 18:59 UTC by Brian W
Modified: 2023-08-23 12:30 UTC (History)
0 users

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Brian W 2023-08-03 18:59:51 UTC
During a distribution upgrade, an important step is to deal with previously used repositories. Online documentation shows this step in section 12.1.3, step 5. Documentation link is here: https://doc.opensuse.org/documentation/leap/startup/html/book-startup/cha-update-osuse.html

What happened prior to Leap 15.3 was the Toggle Status button cycled through three options: Delete, Keep, and Disable. For Leap 15.4 and 15.5, The displayed options are only Delete and Keep. However, there are still three states, as repeatedly pressing Toggle Status will show you. First press of Toggle Status changes the display to Keep; second press the display stays Keep; third press the display returns to Delete.

If I Toggle Status twice on some repositories then finish the upgrade, I find those repositories marked Disabled (but not properly shown as Disabled) all present and disabled. Therefore, the Disable state still exists.

Please fix the display to show all three states, as the Disable state is quite useful. I prefer to Disable nonstandard repositories so I can update them after the upgrade is finished.
Comment 1 Michal Filka 2023-08-04 09:20:56 UTC
Fixed in yast2-installation 4.6.6. The fix will appear in Tumbleweed first.
Comment 2 Brian W 2023-08-04 14:03:57 UTC
Many thanks for the fix!