Changes

From SME Server
Jump to navigationJump to search
m
Line 33: Line 33:     
4. Best practice is to select a Bug that need verifying, See [[Dashboard|the Dashboard]] in the wiki, update the package with the uopdated rpm listed in the Bug   
 
4. Best practice is to select a Bug that need verifying, See [[Dashboard|the Dashboard]] in the wiki, update the package with the uopdated rpm listed in the Bug   
  # yum update e-smith-base --enablerepo=smeupdatestesting (ONLY this)
+
  # yum update e-smith-base --enablerepo=smeupdates-testing (ONLY this)
    
5. Now for the fly in the ointment - sometimes, rarely, there will be a package in /smetest that fixes a borked update in smeupdates-testing, that situation can arise with any update, these will appear in smeupdates-testing eventually, it is alwways a good idea to check in /smetest for a later version of a package.
 
5. Now for the fly in the ointment - sometimes, rarely, there will be a package in /smetest that fixes a borked update in smeupdates-testing, that situation can arise with any update, these will appear in smeupdates-testing eventually, it is alwways a good idea to check in /smetest for a later version of a package.
3,054

edits

Navigation menu