Changes

From SME Server

Update contribs

920 bytes added, 17:10, 15 December 2018
Add notes on correcting yum source after using smedev, smetest or smecontribs-testing
=== Problems ===
 
==== smeupdates-testing ====
You might be directed in the forums or in bugzilla to install an update to a package from the smedev, smetest, or smeupdates-testing repository. Once the developer is confident that the update works and solves the problem, it gets "released" to smeupdates or smecontribs. In this case, yumcheck.sh will continue to look for updates only in original repo until you have installed the "released" version from the correct repository.
 
Assuming you have been directed to update "smeserver-php-scl" from the "smecontribs-testing" repository, you would "correct" the package once it is released by running:<syntaxhighlight lang="bash">
yum --enablerepo=smecontribs reinstall smeserver-php-scl
</syntaxhighlight>Note: "yum reinstall" works only for identical package versions. If smecontribs has a newer version, you can get it using "yum --enablerepo=smecontribs update smeserver-php-scl"
==== Changed Dependencies ====
</syntaxhighlight>
The objective is to upate update only the package or packages that are blocking safe updates using yumcheck.sh. If updating as above (with only the indicated repository enabled) includes too many packages, you might need to add package names to the update command. If the indicated packages include dependencies from other repositories you may need to enable those other repositories.
The epel repository, for example, contains many useful packages (fail2ban, nodejs, roundcube, imapsync, and many more) - but "yum --enablerepo=epel update" would break horde and php on a SME server. In that case you would add the affected package to the update command:<syntaxhighlight lang="bash">
|disablecache=1
|noresultsmessage="Bug not found"
|headers=show}} [[Category:Howto]] [[Category:Tools]] [[Category:Updating]]

Navigation menu