Bug 224603

Summary: Portsmon is broken: The latest Python updated failed
Product: Services Reporter: Trix Farrar <trix>
Component: PortsmonAssignee: Mark Linimon <linimon>
Status: Closed Overcome By Events    
Severity: Affects Some People CC: droso, schaiba, truckman
Priority: ---    
Version: unspecified   
Hardware: Any   
OS: Any   

Description Trix Farrar 2017-12-26 19:03:22 UTC
Portsmon reports appear to have been broken since an October 2017 update to Python.  A thread was posted to FreeBSD forums on 22 October noting a failure:

https://forums.freebsd.org/threads/62932/

Mr. Linimon stated, on the thread, that the best way to reach him about this would be via Bugzilla or e-mail.

A search in Bugzilla showed no PRs, that I could find, regarding this issue so I'm filing one.

Step to reproduce: Use a web browser to open http://portsmon.freebsd.org/portoverview.py?category=sysutils&portname=docker
Comment 1 Kubilay Kocak freebsd_committer freebsd_triage 2020-03-24 08:03:25 UTC
*** Bug 228147 has been marked as a duplicate of this bug. ***
Comment 2 Kubilay Kocak freebsd_committer freebsd_triage 2020-03-24 08:03:28 UTC
*** Bug 239555 has been marked as a duplicate of this bug. ***
Comment 3 Kubilay Kocak freebsd_committer freebsd_triage 2020-03-24 08:03:33 UTC
*** Bug 244209 has been marked as a duplicate of this bug. ***
Comment 4 Kubilay Kocak freebsd_committer freebsd_triage 2020-03-24 08:03:38 UTC
*** Bug 245028 has been marked as a duplicate of this bug. ***
Comment 5 Gian-Simon Purkert 2020-04-21 13:48:28 UTC
The error is:

The latest Python updated failed. I intend to repair this post-BSDCan 2019 -- mcl

link:
http://portsmon.freebsd.org/portsconcordanceformaintainer.py?maintainer=ports%40FreeBSD.org
Comment 6 Mark Linimon freebsd_committer freebsd_triage 2023-08-07 17:46:36 UTC
Unfortunately I have not worked on portsmon in several years.

If someone wants to take it over, please contact me offline.