Obsolete Releases > SME 8.x Contribs
Installing Contribs in sme without internet access
mealogav:
--- Quote ---As I've said I think there is still some repositories that technically should be included in my local repos to get a full update
--- End quote ---
I deduce this because I have done a fresh install of sme8 from the current i386 iso burnt to CD on a server with internet access. It then needed 340MB of updates.
Also I have done a fresh install of sme8 from the same CD on a server with NO internet access. Then modified yum to update from my local repos with local rsync'd copies of the following repositories iso (don't think iso is necessary), smeaddons, smecontribs, smeextras, smeos, smeupdates. It updated only 250MB of updates.
According to the how to http://wiki.contribs.org/Yum_offline_updating I might need to add both the base and addons repositories. Anyone know for sure?
mmccarn:
If I do this:
cd /etc/e-smith/db/yum_repositories/defaults
grep -ril enabled *
I get these results, which I think definitively indicates which repos are enabled by default:
base/status
smeaddons/status
smeextras/status
smeos/status
smeupdates/status
updates/status
There are in my experience lots of updates in base and updates to components used in the SME server that are not re-hosted in the smeos and smeaddons repos.
--- Quote ---The how to at http://wiki.contribs.org/Yum_local_repository sets a new repos called "smeupdates-local". I'm just wondering now how can this possibly change the behaviour of the "normal" updating operation?
--- End quote ---
If you create duplicate "-local" versions for your local repos with status=enabled, then set "status=disabled" on all of the originals, you should get normal updates using the -local repos and avoid the problems with the automatically reappearing MirrorList entries.
mealogav:
Thanks. I was just basing my thoughts on the How To at http://wiki.contribs.org/Yum_offline_updating , that suggests the base and addons repos as well as the smeos, smeaddons and smeupdates repos.
Yeah - I see now how the db of repositories work - I initially was assuming that yum would only use the repos names originally configured, but in fact I now understand that it uses whatever repositories are defined (and enabled) in the db.
So creating "-local" named ones sounds like the best idea and then you can switch between them by enabling / disabling as you suggest.
Just one thing though, won't the "signal-event post-upgrade" process re-enable the disabled MirrorList sites as per the default settings? I'll check this out myself tonight.
Update
The code in "/etc/e-smith/db/yum_repositories/migrate" used to rebuild the repos db entries doesn't change the enabled / disabled status. So this is obviously the right way to setup local yum repositories and be able to easily switch between local repos and remote repos (from MirrorLists) updating.
Thanks mmccarn.
Gavin
Navigation
[0] Message Index
[*] Previous page
Go to full version