Difference between revisions of "Remi-safe"
From SME Server
Jump to navigationJump to searchUnnilennium (talk | contribs) |
Unnilennium (talk | contribs) m (Protected "Remi-safe": for security purpose this repo should remains enabled and visible ([edit=sysop] (indefinite) [move=sysop] (indefinite))) |
||
(6 intermediate revisions by 2 users not shown) | |||
Line 1: | Line 1: | ||
− | <noinclude>{{Warning box|msg=Copy the configuration setting to your server as is, do not modify anything as that might harm your installation. remi-safe has only additonal packages for base repository and Software Collections. It should not conflict with base installation and should be safe to use enabled.}} | + | <noinclude>{{Warning box|msg=Copy the configuration setting to your server as is, do not modify anything as that might harm your installation. Starting SME9, remi-safe has only additonal packages for base repository and Software Collections. It should not conflict with base installation and should be safe to use enabled.}} |
Below you find the installation command for the {{PAGENAME}} repository which can be entered on the SME Server shell. | Below you find the installation command for the {{PAGENAME}} repository which can be entered on the SME Server shell. | ||
<onlyinclude> | <onlyinclude> | ||
− | + | issue the following command on the SME Server shell: | |
/sbin/e-smith/db yum_repositories set remi-safe repository \ | /sbin/e-smith/db yum_repositories set remi-safe repository \ | ||
Name 'Remi - safe' \ | Name 'Remi - safe' \ |
Latest revision as of 19:10, 12 October 2017
Below you find the installation command for the Remi-safe repository which can be entered on the SME Server shell.
issue the following command on the SME Server shell:
/sbin/e-smith/db yum_repositories set remi-safe repository \ Name 'Remi - safe' \ BaseURL 'http://rpms.famillecollet.com/enterprise/$releasever/safe/$basearch/' \ EnableGroups no \ GPGCheck yes \ GPGKey http://rpms.famillecollet.com/RPM-GPG-KEY-remi \ Visible yes \ status enabled
After adding it to the database updating the configuration file is required:
signal-event yum-modify