Date: Sat, 17 Apr 2021 21:33:59 GMT From: "Danilo G. Baio" <dbaio@FreeBSD.org> To: doc-committers@FreeBSD.org, dev-commits-doc-all@FreeBSD.org Subject: git: a4f1e08526 - main - books/porters-handbook: Add a note about portsmon out of service Message-ID: <202104172133.13HLXxn3040059@gitrepo.freebsd.org>
next in thread | raw e-mail | index | archive | help
The branch main has been updated by dbaio (ports committer): URL: https://cgit.FreeBSD.org/doc/commit/?id=a4f1e08526d618f47bee327ea018408ce480e8af commit a4f1e08526d618f47bee327ea018408ce480e8af Author: Danilo G. Baio <dbaio@FreeBSD.org> AuthorDate: 2021-04-17 21:29:45 +0000 Commit: Danilo G. Baio <dbaio@FreeBSD.org> CommitDate: 2021-04-17 21:33:08 +0000 books/porters-handbook: Add a note about portsmon out of service Maybe soon portsmon can be fixed, so just let a note to inform users that this resource is currently not working. Approved by: debdrup, mat and ygy (docs) --- .../content/en/books/porters-handbook/keeping-up/_index.adoc | 5 +++++ .../content/en/books/porters-handbook/upgrading/_index.adoc | 5 +++++ 2 files changed, 10 insertions(+) diff --git a/documentation/content/en/books/porters-handbook/keeping-up/_index.adoc b/documentation/content/en/books/porters-handbook/keeping-up/_index.adoc index b92aa1bac5..90929c9877 100644 --- a/documentation/content/en/books/porters-handbook/keeping-up/_index.adoc +++ b/documentation/content/en/books/porters-handbook/keeping-up/_index.adoc @@ -80,3 +80,8 @@ Another handy resource is the http://portsmon.FreeBSD.org[FreeBSD Ports Monitori To get started, use the http://portsmon.FreeBSD.org/portoverview.py[Overview of One Port] search page to find all the information about a port. This is the only resource available that maps PR entries to portnames. PR submitters do not always include the portname in their Synopsis, although we would prefer that they did. So, `portsmon` is a good place to find out whether an existing port has any PRs filed against it, any build errors, or if a new port the porter is considering creating has already been submitted. + +[NOTE] +====== +The FreeBSD Ports Monitoring System (portsmon) is currently not working due to latest Python updates. +====== diff --git a/documentation/content/en/books/porters-handbook/upgrading/_index.adoc b/documentation/content/en/books/porters-handbook/upgrading/_index.adoc index cff0c810d8..dc01bd897b 100644 --- a/documentation/content/en/books/porters-handbook/upgrading/_index.adoc +++ b/documentation/content/en/books/porters-handbook/upgrading/_index.adoc @@ -37,6 +37,11 @@ The next step is to see if there is an update already pending. To do this, there However, sometimes people forget to put the name of the port into the Summary field in an unambiguous fashion. In that case, try searching in the `Comment` field in the `Detailled Bug Information` section, or try the crossref:keeping-up[portsmon,FreeBSD Ports Monitoring System] (also known as `portsmon`). This system attempts to classify port PRs by portname. To search for PRs about a particular port, use the http://portsmon.FreeBSD.org/portoverview.py[Overview of One Port]. +[NOTE] +====== +The FreeBSD Ports Monitoring System (portsmon) is currently not working due to latest Python updates. +====== + If there is no pending PR, the next step is to send an email to the port's maintainer, as shown by `make maintainer`. That person may already be working on an upgrade, or have a reason to not upgrade the port right now (because of, for example, stability problems of the new version), and there is no need to duplicate their work. Note that unmaintained ports are listed with a maintainer of `ports@FreeBSD.org`, which is just the general ports mailing list, so sending mail there probably will not help in this case. If the maintainer asks you to do the upgrade or there is no maintainer, then help out FreeBSD by preparing the update! Please do this by using the man:diff[1] command in the base system.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?202104172133.13HLXxn3040059>