Updating site to latest commit (6080b20)

23.4.0/extension_points/yum_repository_poller.html

@@ -312,7 +312,7 @@ <h1 id="searchResultTitle" class="search-results-title hide"></h1>
 
 
 <article class="markdown"><h1 id="yum-repository-poller">Yum Repository Poller</h1>
-<p><strong>Note:</strong> This plugin is available for GoCD servers running on Linux nodes having repoquery installed (part of the <a href="https://linux.die.net/man/1/yum-utils">yum-utils</a> package, <a href="https://manpages.ubuntu.com/manpages/focal/en/man1/yum-utils.1.html">Ubuntu</a>, <a href="https://rpmfind.net/linux/rpm2html/search.php?query=yum-utils&amp;system=centos">CentOS</a>)</p>
+<p><strong>Note:</strong> This plugin is available for GoCD servers running on Linux nodes having repoquery installed (part of the <a href="https://manpages.ubuntu.com/manpages/focal/en/man1/yum-utils.1.html">yum-utils</a> package, <a href="https://manpages.ubuntu.com/manpages/lunar/en/man1/yum-utils.1.html">Ubuntu</a>, <a href="https://rpmfind.net/linux/rpm2html/search.php?query=yum-utils&amp;system=centos">CentOS</a>)</p>
 <h2 id="introduction">Introduction</h2>
 <p>The Yum repository poller is a <a href="package_repository_extension.html">package material</a> plugin capable of polling yum repositories for rpm packages. Prior to GoCD <code>23.1.0</code> the plugin came bundled with GoCD, however can now be downloaded for installation <a href="https://github.com/gocd/gocd-yum-repository-poller-plugin/releases/latest">at GitHub</a>.</p>
 <p>GoCD server interacts with this plugin via package material plugin interfaces. The plugin makes use of a command similar to the following to poll the server. So it does not depend on the files that yum depends on e.g. files under /etc/yum.repos.d</p>
@@ -326,15 +326,15 @@ <h2 id="introduction">Introduction</h2>
 <h3 id="repository-definition">Repository definition</h3>
 <p>Repo URL must be a valid http, https or file URL. This plugin looks for the presence of <strong>$REPO_URL/repodata/[repomd.xml]</strong> to ascertain validity. Basic authentication (user:password@domain/path) is supported for http and https repositories.</p>
 <h3 id="package-definition">Package definition</h3>
-<p>In case of this plugin, the package definition is completely determined by the package spec. The package spec may be in any of the following formats. Please refer to the <a href="https://linux.die.net/man/1/repoquery">repoquery man page</a> for details.</p>
+<p>In case of this plugin, the package definition is completely determined by the package spec. The package spec may be in any of the following formats. Please refer to the <a href="https://manpages.ubuntu.com/manpages/focal/en/man1/repoquery.1.html">repoquery man page</a> for details.</p>
 <pre tabindex="0"><code>name
 name.arch
 name-ver
 name-ver-rel
 name-ver-rel.arch
 name-epoch:ver-rel.arch
 epoch:name-ver-rel.arch
-</code></pre><p><a href="https://linux.die.net/man/7/glob">Shell glob patterns</a> may also be used. For example, say we have a component under development getting ready for release of version 1.2.0. We cut a branch for the release and bump up the version on trunk/master to 1.3.0. Thus, a package generated by trunk/master may look like mycomp-1.3.0-b72349-noarch.rpm while that generated by branch may look like mycomp-1.2.0-b72344-noarch.rpm. Now if we have a deployment pipeline that is only interested in 1.2 series packages, the package spec needs to be mycomp-1.2.* rather than just mycomp.</p>
+</code></pre><p><a href="https://man7.org/linux/man-pages/man7/glob.7.html">Shell glob patterns</a> may also be used. For example, say we have a component under development getting ready for release of version 1.2.0. We cut a branch for the release and bump up the version on trunk/master to 1.3.0. Thus, a package generated by trunk/master may look like mycomp-1.3.0-b72349-noarch.rpm while that generated by branch may look like mycomp-1.2.0-b72344-noarch.rpm. Now if we have a deployment pipeline that is only interested in 1.2 series packages, the package spec needs to be mycomp-1.2.* rather than just mycomp.</p>
 <h3 id="package-metadata">Package Metadata</h3>
 <p>The following <a href="https://ftp.osuosl.org/pub/rpm/max-rpm/s1-rpm-inside-tags.html">rpm metadata</a> is accessed by the plugin</p>
 <ol>
@@ -387,7 +387,7 @@ <h3 id="creating-and-publishing-rpms">Creating and Publishing RPMs</h3>
 <ul>
 <li><a href="https://www.ibm.com/developerworks/library/l-rpm1/#building-your-first-rpm">Building an RPM using rpmbuild and SPEC file</a></li>
 <li><a href="https://github.com/jordansissel/fpm/wiki">Building using fpm</a></li>
-<li><a href="https://www.thegeekdiary.com/how-to-create-yum-repository-in-centos-rhel/">Tutorial</a> to set up a local yum repository using <a href="https://linux.die.net/man/8/createrepo">createrepo</a>. Publishing to a yum repo simply involves uploading/copying over a new package revision at the correct location and running <code>createrepo --update</code></li>
+<li><a href="https://www.thegeekdiary.com/how-to-create-yum-repository-in-centos-rhel/">Tutorial</a> to set up a local yum repository using createrepo. Publishing to a yum repo simply involves uploading/copying over a new package revision at the correct location and running <code>createrepo --update</code></li>
 </ul>
 <h3 id="notes">Notes</h3>
 <ol>