Bug 259574

Summary: devel/py-distributed: Fails to build in quarterly branch: py38-cloudpickle>=1.5.0 - not found
Product: Ports & Packages Reporter: Robert Clausecker <fuz>
Component: Individual Port(s)Assignee: Po-Chuan Hsieh <sunpoet>
Status: Closed FIXED    
Severity: Affects Many People CC: python
Priority: --- Keywords: needs-patch, needs-qa
Version: LatestFlags: bugzilla: maintainer-feedback? (sunpoet)
koobs: merge-quarterly?
Hardware: Any   
OS: Any   

Description Robert Clausecker freebsd_committer freebsd_triage 2021-10-31 11:05:29 UTC
Build of devel/py-distributed-2021.7.2 (branch 2021Q4) fails in pkg-depends because py38-cloudpickle>=1.5.0 is requested but only version 1.3.0 is provided in ports.

=======================<phase: run-depends    >============================
===>   py38-distributed-2021.7.2 depends on package: py38-click>=6.6 - not found
===>   Installing existing package /packages/All/py38-click-7.1.2.pkg
[13Rarmv7-quarterly-job-04] Installing py38-click-7.1.2...
[13Rarmv7-quarterly-job-04] Extracting py38-click-7.1.2: .......... done
===>   py38-distributed-2021.7.2 depends on package: py38-click>=6.6 - found
===>   Returning to build of py38-distributed-2021.7.2
===>   py38-distributed-2021.7.2 depends on package: py38-cloudpickle>=1.5.0 - not found
===>   Installing existing package /packages/All/py38-cloudpickle-1.3.0.pkg
[13Rarmv7-quarterly-job-04] Installing py38-cloudpickle-1.3.0...
[13Rarmv7-quarterly-job-04] Extracting py38-cloudpickle-1.3.0: .......... done
===>   py38-distributed-2021.7.2 depends on package: py38-cloudpickle>=1.5.0 - not found
*** Error code 1
Comment 1 Kubilay Kocak freebsd_committer freebsd_triage 2021-11-02 01:21:01 UTC
Thank you for the report Robert. 

- cloudpickle dependency was updated to 1.5.0 in ports 52796b1c0 in may

- ports 63c9db38 updated (downdated to 1.3.0) the cloudpickle dependency line in head, yesterday
Comment 2 Robert Clausecker freebsd_committer freebsd_triage 2021-11-02 09:07:25 UTC
(In reply to Kubilay Kocak from comment #1)

I guess it would be easiest to just MFH this update.  Sunpoet@ surely knows more.
Comment 3 Robert Clausecker freebsd_committer freebsd_triage 2022-01-17 16:29:18 UTC
This has been addressed by a patch.