Line 201: |
Line 201: |
| yum remove {{#var:smecontribname}} {{#var:contribname}}-src | | yum remove {{#var:smecontribname}} {{#var:contribname}}-src |
| | | |
− | prior to smeserver-nextcloud you will also need to remove nextcloud package from Exclude, this is a one liner to do so
| + | then if you have a rpm named nextcloud |
− | db yum_repositories setprop smecontribs Exclude $(db yum_repositories getprop smecontribs Exclude |awk '{gsub (/\ynextcloud,?\y|\y,?nextcloud\y/, "", $1)}1') | + | rpm -q nextcloud |
| + | then do |
| + | rpm -e --justdb nextcloud |
| | | |
− | alternative would be to do
| + | this will remove the rpm from the db, without trashing your current app install and config. |
− | db yum_repositories getprop smecontribs Exclude
| + | |
− | nextcloud,randomthing
| + | those folders will then remain |
− | and recopy the result without nextcloud
| + | * /usr/share/nextcloud : software and config |
− | db yum_repositories setprop smecontribs Exclude randomthing
| + | * /home/e-smith/files/nextcloud : user data |
− | or simply do the following if nextcloud is the only package | + | |
− | db yum_repositories delprop smecontribs Exclude
| + | also you will have mariadb or mariadb105 with nextcloud db and user. |
| + | |
| + | and finally, db configuration with entry for nextcloud. |
| + | |
| + | of all of those remains as is a simple reinstall of the contrib will bring back nextcloud running. |
| + | |
| + | In case of deleting either the db or part of the software folder upon reinstalling the contrib it will just stall in the process to avoid to have db and software version not in sync. |
| | | |
| === Release schedule === | | === Release schedule === |