5,576
edits
Changes
Jump to navigation
Jump to search
Line 88:
Line 88: − Here are two examples that Ian resolved during SME 9.0+ − + − cp /mirrors/centos/6/os/i386/Packages/libtevent-0* /build/smeserver/repo/testing/9/smeupdates-testing/i386/RPMS/ + + + + + + + + + + + + + + + +
→RPM dependencies
The os, updates, and updates-testing repos are included so we can stage the packages we are going to release without actually having to release them. Normally the updates-testing repo is used for verification (testing is for developer testing). During the ISO release schedule (usually very short) we hold moving packages to updates-testing until I have the ISO built.
The os, updates, and updates-testing repos are included so we can stage the packages we are going to release without actually having to release them. Normally the updates-testing repo is used for verification (testing is for developer testing). During the ISO release schedule (usually very short) we hold moving packages to updates-testing until I have the ISO built.
=====Examples of dependencies=====
cp /mirrors/rpmforge/redhat/el6/en/i386/dag/RPMS/perl-Taint-Util-0.08-1.el6.rf.i686.rpm /build/smeserver/repo/testing/9/smetest/i386/RPMS/
cp /mirrors/rpmforge/redhat/el6/en/i386/dag/RPMS/perl-Taint-Util-0.08-1.el6.rf.i686.rpm /build/smeserver/repo/testing/9/smetest/i386/RPMS/
cp /mirrors/centos/6/os/i386/Packages/libtevent-0* /build/smeserver/repo/testing/9/smeupdates-testing/i386/RPMS/
This shows that on the buildsys the /mirrors has the main upstream repos and they will normally hold the RPM needed to resolve the dependency. You need to get it into smeupdates-testing, but it is safer to first copy the RPM to smetest and check that all is well.
This shows that on the buildsys the /mirrors has the main upstream repos and they will normally hold the RPM needed to resolve the dependency. You need to get it into smeupdates-testing, but it is safer to first copy the RPM to smetest and check that all is well.
=====Rpm update cycle=====
If an RPM is released during the update cycle:<br />
smetest->smeupdates-testing->updates
If an RPM is only needed for a new ISO and never needed as an update (before the ISO is released) :<br />
/mirrors->smeupdates-testing->smeos
Note that you don't put it into smeos, that is taken care of by the build scripts.
=====What are smeos/smeextras=====
* Every package that needs to be in the ISO will go into smeos, '''by the buildsys.'''
* Packages that are needed for building the ISO, but not actually needed in the ISO, will be in smeextras
====RPM QA verification====
====RPM QA verification====