I did some quick tests and the removal behavior seems good to me.
Still I have doubts about these changes since I fear we will face some more hidden troubles.
Also be aware these changes will affect the yum behavior when used from the command line.
I would gladly review the PR, but before releasing the packages we need a big effort from the quality team 
Itās possible to set those options from a shell wrapper
yum --setopt=...
ā¦the problem here is we have a python wrapper 
/sbin/e-smith/pkgaction
@davidep, I will need some help (disclosure: Iām not a developer 
).
I was about to ask if the system commands (yum, rpmā¦) executed by the server-manager were aware of the locale context: now I know they use the language set at web login.
It is working almost well with rpm, as it gives a clean output, but there are some cases (nethserver-ftp) where it does not give accurate information on whatrequires a specific package.
Help with regex
Now Iām trying with /usr/bin/yum -C --assumeno remove $@ . If you can help on getting a proper regex pattern to match all the packages shown on Keeping package: lines (regardless of language), because I am tempted to the ugliness of forcing the language at runtime 
.
ā> Keeping package: nethserver-samba-2.0.0-1.ns7.noarch due to nethserver-samba-audit-1.1.0-1.ns7.noarch
Some troublemakers:
// translation pattern: msgstr āā> č½Æ件å
%s.%s.%s.%s-%s å°č¢« %sā
// translation pattern: msgstr āā> äæēč½Æ件å
ļ¼%s ē±äŗ %sā
ā> č½Æ件å
nethserver-mysql.noarch.0.1.1.0-1.ns7 å°č¢« å é¤
ā> äæēč½Æ件å
ļ¼nethserver-mysql-1.1.0-1.ns7.noarch ē±äŗ nethserver-samba-audit-1.1.0-1.ns7.noarch
// translation pattern: msgstr āā> A(z) %s.%s %s:%s-%s csomaggal a kƶvetkezÅ tƶrtĆ©nik: %sā
// translation pattern: msgstr āā> A(z) %s Csomag megtartĆ”sa a kƶvetkezÅ miatt: %sā
ā> A(z) nethserver-mysql.noarch 0:1.1.0-1.ns7 csomaggal a kƶvetkezÅ tƶrtĆ©nik: tƶrƶlve
ā> A(z) nethserver-mysql-1.1.0-1.ns7.noarch Csomag megtartĆ”sa a kƶvetkezÅ miatt: nethserver-samba-audit-1.1.0-1.ns7.noarch
ā Manteniendo paquete: nethserver-samba-2.0.0-1.ns7.noarch debido a nethserver-samba-audit-1.1.0-1.ns7.noarch
ā> BalĆÄek nethserver-samba-2.0.0-1.ns7.noarch ponechĆ”n, protože: nethserver-samba-audit-1.1.0-1.ns7.noarch
Help with permissions
If a shell script under /usr/libexec/nethserver/ needs to run under sudo when called from server-manager, do I need to set an acl on the file (for running tests)? how?
No hurry.
P.S. Donāt know if there is something in the yum python API that can be implemented to run at runtime without changing yum.conf
Now you are! 
Iād write a shell wrapper that invokes yum command by setting the environment variable LANG=C.
This would help on building a matching regex pattern.
No, permissions should be as usual (root,root,0755).
IIRC we already do it:
@davidep, thanks for the tips.
Iām holding the changes and thinking to dismiss them due to some quirks, as @giacomo feared.
From the UI seems to work well, but we may find packages with Āæcircular dependencies? difficulting its removal from CLI, or other quircks:
What are your thoughts?
First of all, kudos!
I dināt have the patience to dig into the web interface code like you did!
Circular dependencies on dkms packages can happen, but pfring-dkms comes from ntopng repository and, honestly, that package is crap.
I think both are correct.
Really no idea on this, but I saw this kind of strange behaviors long time ago when testing auto removal tools for yum.
IMHO package removal is a not-resolved problem and create a simple web interface for it is even more difficult
Iād like to continue this discussion here gathering some thoughts about the current topic
What do you think to leave the āremoveā activities in the CLI only, dropping the DELETE button?
@ambassadors_group
I am in favor of such an option provided there will be documentation available on how to un-install nethserver modules.
I understand the default āyum uninstall packagenameā but I donāt know the official module packages.
It would be nice to see a wikipage with all the nethserver modules and how to install and de-install then through the commandline.
Indeed, we need to document the command correctly and list the packages to uninstall
I donāt think that to drop the delete button is a good idea. Nethserver claims to be easy to handle as itās biggest advantage. To be able to install a package with a few clicks, but you canāt get rid of it without CLI? IMO bad manner. For those who just want to disable the installed package and donāt care about fragments that will remain it is good the way it is. And I think there are some of them.
Maybe an addtional notice, that for a full remove you have to go to CLI is an option.
Something like: āPlease be aware, that this option only remove the neth-package. If you want to do a full remove, please reffer to the deinstallation notes in the wiki.ā
I wouldnāt remove that button! Yes, as @giacomo said in the other topic, the Enterprise version does not have it, but the Enterprise version has also the config backup on cloud and factory reset in embedded systems: reinstalling from scratch and restoring the configuration is available out of the box 
Documenting the right packages to remove is difficult: information must be consistent. Iād prefer trying to fix the group compositions and RPM dependencies, so that removals are not disruptive.
I consider such removals as bugs and they should be fixed, if possible.
The software center is a huge piece of code, but the signal wonāt be good to remove the uninstall button IMHO.
If you have a bug, please correct it, it sounds simple
I totally agreeā¦
The delete button is clearā¦ And the guy who access the Netserver webgui is a sysadmin or at least an advanced userā¦ not a children.
sureā¦but the list of deleted rpm must be clear, the removal of dependencies must be the same like with the CLI, and of course when you remove nethserver-mysql, mysql itself should be removed (for example) and unfortunately a lot of nethserver-* rpm of course.
The current behaviour just does not look consistent.
The nethserver-webproxy example can be installed and it installs squid etcā¦ But when you remove it, nethserver-nextcloud is removed too. This is highly unwanted behavior and has nothing to do with being a sysadmin or not.
Perhaps doing it makes little sense. What does that involve?
Does the behaviour is the same with the cli ?
@stephdl: ermmm dunno shrucks
I must test this. If it is doing the same in webinterface and cli, then still IMO it is a bad thing that by removing a proxy, nextcloud gets removed tooā¦
I agree: it doesnāt look consistent but it is 
Yes it does.
This is how yum groups work.
Now I see it was a bad design decision to use yum groups as software module, my bad.
I donāt any viable alternative right now.