Bug 1202705 - Extension selection can't be changed during install
Extension selection can't be changed during install
Status: NEW
Classification: openSUSE
Product: PUBLIC SUSE Linux Enterprise Micro 5.3
Classification: openSUSE
Component: Installation
unspecified
Other Other
: P5 - None : Normal
: ---
Assigned To: E-mail List
Jiri Srain
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2022-08-24 14:05 UTC by Robert Simai
Modified: 2022-10-17 13:02 UTC (History)
2 users (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---
mfilka: needinfo? (jtomasiak)


Attachments
screenshot: select extensions (36.33 KB, image/png)
2022-08-24 14:05 UTC, Robert Simai
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Robert Simai 2022-08-24 14:05:40 UTC
Created attachment 861031 [details]
screenshot: select extensions

In the context of #1202702, I hit "back" a few times to remove an extension but it's apparently not possible to change selection once the system is registered. I'll attach a screenshot to illustrate.

I'd expect to be able to either change the setting or a meaningful note that explains the options.
Comment 1 Michal Filka 2022-08-25 07:23:32 UTC
@Lada: is it bug or feature? Can it somehow be influenced e.g. by the account properties used for registration.
Comment 2 Ladislav Slezák 2022-09-01 08:25:15 UTC
There are basically two problems:

1. The suseconnect-ng API does not expose the functionality for deregistering
   an add-on or the complete system to YaST.

   Jacek, would that be possible? I guess it should not be difficult and
   we already had some requests for this...

2. How to visually indicate that the add-on will be deregistered.

   Currently there is only a simple on/off check box. We would need a new
   state for that like we have in the package manager, the to be deleted
   packages have a special icon for that.
Comment 3 Jacek Tomasiak 2022-09-01 14:53:16 UTC
Re #1, if the logic would be the same as `SUSEConnect -d [-p <product]` then it should not be a problem to expose this to YaST. Please create an issue on https://github.com/SUSE/connect-ng and propose some API (i.e. how you want to call this).
Comment 4 Michal Filka 2022-09-08 08:18:07 UTC
@Ladislav:
Could you define such API suitable for yast needs? We can then clearly define trello pbi.
Comment 5 Ladislav Slezák 2022-09-15 14:07:39 UTC
Created API proposal at https://github.com/SUSE/connect-ng/issues/148
Comment 6 Michal Filka 2022-09-20 09:19:07 UTC
@Jacek
See the API proposal linked from comment#5. Once the issue is solved we can implement it on the YaST side. Putting you into needinfo until then.
Comment 7 Jacek Tomasiak 2022-09-22 13:05:13 UTC
Proposed implementation in suseconnect-ng: https://github.com/SUSE/connect-ng/pull/153

@Ladislav: how do you plan to handle this wrt the old (ruby) SUSEConnect? Will you only expect this new API in new version?
Comment 8 Michal Filka 2022-09-29 07:06:26 UTC
@Ladislav:
see comment#7 thanks
Comment 9 Ladislav Slezák 2022-10-17 13:02:57 UTC
(Oops, sorry I overlooked this.)

The proposal looks good.

I'd expect the API only in the new package for future SLE15-SP5, no need for backporting to SP4.