<?xml version="1.0" encoding="iso-8859-1"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
  "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
<link rel="home" title="HomePage" href="HomePage.html" />
<link rel="help" title="HowToUseWiki" href="HowToUseWiki.html" />
<link rel="copyright" title="GNU General Public License" href="http://www.gnu.org/copyleft/gpl.html#SEC1" />
<link rel="author" title="The PhpWiki Programming Team" href="http://phpwiki.org/ThePhpWikiProgrammingTeam" />
<meta http-equiv="Content-Style-Type" content="text/css" />
<meta http-equiv="Content-Language" content="en" />
<meta name="robots" content="noindex,nofollow" />
<meta name="language" content="en" />
<meta name="document-type" content="Public" />
<meta name="document-rating" content="General" />
<meta name="generator" content="PhpWiki" />
<meta name="PHPWIKI_VERSION" content="1.3.14" />

<link rel="stylesheet" type="text/css" charset="iso-8859-1" href="phpwiki-printer.css" />
<title>PhpWiki - FAQ on helping with updates-testing</title>
</head>
<body>

<div id="header">
  
<!-- Page title -->
<h1>FAQ on helping with updates-testing</h1>
</div>
<div id="content">



<div class="wikitext"><h4>Q: What help is required in verifying packages in updates-testing?</h4>
<p class="tightenable">The purpose of testing packages in updates-testing is to check whether the upgraded
rpms break an SME Server due to some side-effect. It is not necessary to
verify the actual fix, although if this is done it should be noted.</p>
<p class="tightenable">In the wiki it is summarised as &quot;Use the package as normal and publish the results.&quot;</p>
<p class="tightenable">In the Fedora Legacy wiki it says<br />
&quot;Could you use the package, as appropriate for the package, without problems&quot; <br />
And for more detail<br />
&quot;The time needed to test a package will vary for each package. The steps
needed will also vary. For example, for a simple application, you may
just use it for a few minutes as you normally would, and verify that it
works for the normal tasks you do with that application. On the other
hand, for a kernel update, you would want to run it for a least a couple
of days to see if any problems develop before reporting success.&quot;</p>
<p class="tightenable">As the Fedora Legacy project can not detail the testing required it would be hard for the SME Server community to do this, although this could be a goal for the future.</p>
<p class="tightenable">Even a single test per package would increase the confidence that the updates are good. Preferably a lot more would be done - but we don't yet have the test cases.</p>
<h4>Q: How does one get the updates applied for testing using yum (from updates-testing)</h4>
<p class="tightenable bottom">if you have the latest yum installed then the updates-testing section should be commented out</p>
<pre class="tightenable top">
#[updates-testing]
#name=SME Server $releasever updates-testing
#baseurl=<a href="http://mirror.contribs.org/smeserver/releases/$releasever/updates-testing/i386/" target="" class="namedurl"><span style="white-space: nowrap"><img src="images/http.png" alt="" class="linkicon" border="0" />http://mirror.contribs.org/smeserver/releases/$releasever/updates-testing/i386/</span></a>
#gpgcheck=0</pre>
<p class="tightenable bottom">remove the #'s to enable updates-testing. They can then be installed as
usual. To see the available updates</p>
<ul><li class="tightenable top"># yum list</li>
</ul>
<h4>Q: if a problem is found, how does one &quot;rollback&quot; the changes ?</h4>
<p class="tightenable top bottom">You can find the old RPM from the mirrors, and install it with
rpm's -oldpackage as shown here for cvs.</p>
<ul><li class="tightenable top"># rpm -Uvh --oldpackage  cvs-1.11.1p1-7es02.i386.rpm</li>
</ul>
<h4>Q Is &quot;no problems found&quot; the kind of feedback you are looking for, or do you only want feedback when a problem is found?<br /></h4>
<p class="tightenable top">Examples are:<br />
<a href="http://bugs.contribs.org/bug_view_page.php?bug_id=0000248" target="" class="namedurl"><span style="white-space: nowrap"><img src="images/http.png" alt="" class="linkicon" border="0" />http://bugs.contribs.org/bug_view_page.php?bug_id=0000248</span></a> <br />
<a href="http://bugs.contribs.org/bug_view_page.php?bug_id=0000259" target="" class="namedurl"><span style="white-space: nowrap"><img src="images/http.png" alt="" class="linkicon" border="0" />http://bugs.contribs.org/bug_view_page.php?bug_id=0000259</span></a> <br /></p>
<p class="tightenable bottom">Please add a bug note for each package tested even if it is 'no problems
found'.
In 95+% of cases the feedback will be 'no problems found' as the updates have
some testing before reaching this far.
It is good when the Bug Report can give some details about what is tested.</p>
</div>

<div id="footer">  <hr class="printer" noshade="noshade" />
<p class="editdate">Owner: &quot;wellsi&quot;  Last edited on September 30, 2005  3:03 pm by &quot;wellsi&quot;</p>
</div>

</div>
<!-- Add your Disclaimer here -->
</body>
</html>
