Avoid use of linux.die.net URLs

content/extension_points/yum_repository_poller.md

@@ -7,7 +7,7 @@ title: Yum Repository Poller
 
 # Yum Repository Poller
 
-**Note:** This plugin is available for GoCD servers running on Linux nodes having repoquery installed (part of the [yum-utils](https://linux.die.net/man/1/yum-utils) package, [Ubuntu](https://manpages.ubuntu.com/manpages/focal/en/man1/yum-utils.1.html), [CentOS](https://rpmfind.net/linux/rpm2html/search.php?query=yum-utils&system=centos))
+**Note:** This plugin is available for GoCD servers running on Linux nodes having repoquery installed (part of the [yum-utils](https://manpages.ubuntu.com/manpages/focal/en/man1/yum-utils.1.html) package, [Ubuntu](https://manpages.ubuntu.com/manpages/lunar/en/man1/yum-utils.1.html), [CentOS](https://rpmfind.net/linux/rpm2html/search.php?query=yum-utils&system=centos))
 
 ## Introduction
 
@@ -33,7 +33,7 @@ Repo URL must be a valid http, https or file URL. This plugin looks for the pres
 
 ### Package definition
 
-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 [repoquery man page](https://linux.die.net/man/1/repoquery) for details.
+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 [repoquery man page](https://manpages.ubuntu.com/manpages/focal/en/man1/repoquery.1.html) for details.
 
 ```
 name
@@ -45,7 +45,7 @@ name-epoch:ver-rel.arch
 epoch:name-ver-rel.arch
 ```
 
-[Shell glob patterns](https://linux.die.net/man/7/glob) 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.
+[Shell glob patterns](https://man7.org/linux/man-pages/man7/glob.7.html) 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.
 
 ### Package Metadata
 
@@ -126,7 +126,7 @@ Although the support for package as material in GoCD isn't concerned with how th
 
 - [Building an RPM using rpmbuild and SPEC file](https://www.ibm.com/developerworks/library/l-rpm1/#building-your-first-rpm)
 - [Building using fpm](https://github.com/jordansissel/fpm/wiki)
-- [Tutorial](https://www.thegeekdiary.com/how-to-create-yum-repository-in-centos-rhel/) to set up a local yum repository using [createrepo](https://linux.die.net/man/8/createrepo). Publishing to a yum repo simply involves uploading/copying over a new package revision at the correct location and running `createrepo --update`
+- [Tutorial](https://www.thegeekdiary.com/how-to-create-yum-repository-in-centos-rhel/) 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 `createrepo --update`
 
 ### Notes