databases/py-dbt-semantic-interfaces: fix build by relaxing upper limit on dependency Reported by: fallout Approved by: portmgr (unbreak; blanket)cc89c98e78
Port details
databases/py-dbt-semantic-interfaces0.10.5_1
Shared semantic layer definitions that dbt-core and MetricFlow use
- Maintainer
- patmaddox@FreeBSD.org
- Packages
- py312-dbt-semantic-interfaces 0.10.5_1
- Upstream
- up to date
- CPE
- none, CVEs only via VuXML
- WWW
- https://github.com/dbt-labs/dbt-semantic-interfaces
- Links
- cgit · VuXML
Unaddressed (0) · The CVE record lists this version as affected, no VuXML entry names the CVE
None. There is no CVE without a VuXML entry for this version.
VuXML only (0) · listed, port not fixed yet
None.
pkg audit reports nothing for this version.Fixed (0)
No VuXML entries for this package.
Commits (16)
databases/py-dbt-semantic-interfaces: Update dependency This is done in preparation for upgrading devel/py-importlib-metadata to 9.X branch Approved by: portmgr (blanket)0bfa28c569
databases/py-dbt-semantic-interfaces: Update to 0.10.5 Approved by: dch (mentor) Closes: https://github.com/freebsd/freebsd-ports/pull/555729d170778
databases/py-dbt-semantic-interfaces: Allow build with py-more-itertools 11.0.0+ - Bump PORTREVISION for package changec8f846919b
databases/py-dbt-semantic-interfaces: Allow build with py-click 8.3.0+ - Bump PORTREVISION for package change Obtained from: https://github.com/dbt-labs/dbt-semantic-interfaces/commit/6a6176e08c6e36ad8f9b47c6364aaa8cbc408fe0849cab89b4
databases/py-dbt-semantic-interfaces: Fix BUILD_DEPENDS and its usage - Fix BUILD_DEPENDS: py-hatch is not needed - Fix BUILD_DEPENDS usage: it should depend on the package, not the executable from pyproject.toml: [build-system] requires = ["hatchling"] Reference: https://github.com/dbt-labs/dbt-semantic-interfaces/blob/v0.10.0/pyproject.toml#L35-L36 Approved by: portmgr (blanket) With hat: python59e320a965
databases/py-dbt-semantic-interfaces: Update 0.8.3 => 0.10.0 Changelogs: https://github.com/dbt-labs/dbt-semantic-interfaces/releases/tag/v0.8.4 https://github.com/dbt-labs/dbt-semantic-interfaces/releases/tag/v0.8.5 https://github.com/dbt-labs/dbt-semantic-interfaces/releases/tag/v0.9.1 https://github.com/dbt-labs/dbt-semantic-interfaces/releases/tag/v0.9.2 https://github.com/dbt-labs/dbt-semantic-interfaces/releases/tag/v0.10.0 PR: 290343ceeb370778
databases/py-dbt-semantic-interfaces: Update to 0.8.3 Changelog: https://github.com/dbt-labs/dbt-semantic-interfaces/releases PR: 28311713f3fd0142
databases/py-dbt-semantic-interfaces: Fix RUN_DEPENDS usage Approved by: portmgr (blanket) With hat: python2748ef5f44
devel/py-pyyaml: Move devel/py-yaml to devel/py-pyyaml - Bump PORTREVISION of dependent ports for dependency change1a80ec7c22
databases/py-dbt-semantic-interfaces: Update to 0.5.1 Changelog: https://github.com/dbt-labs/dbt-semantic-interfaces/releases/tag/v0.5.1 PR: 276452d49e8fb670
devel/py-python-dateutil: Move devel/py-dateutil to devel/py-python-dateutil - Convert to USE_PYTHON=pep517 - Bump PORTREVISION of dependent ports for dependency change - While I'm here, update audio/py-pyradio to use PYTHON_PKGNAMEPREFIX instead of PKGNAMEPREFIX for *_DEPENDS84a372ad5f
databases/py-dbt-semantic-interfaces: Fix build by correcting dependency
This fails:
RUN_DEPENDS= ${PYTHON_PKGNAMEPREFIX}pydantic>=1.10,<2,1:devel/py-pydantic@${PY_FLAVOR}
That's probably because pydantic has comma in its version and it isn't properly handled:
py39-pydantic-1.10.13,1
Approved by: portmgr (unbreak)dc1f6bd068devel/py-pydantic: bump PORTEPOCHd10746733e
databases/py-dbt-semantic-interfaces: Update version 0.2.0=>0.4.1 Committed with modification for py-importlib-metadata. Buzz me if it creates trouble. Changelog: https://github.com/dbt-labs/dbt-semantic-interfaces/releases/tag/v0.4.1 PR: 275583 Approved by: submitter is maintainer15ce413d89
databases/py-dbt-semantic-interfaces: new port dbt-semantic-interfaces contains the shared semantic classes, default validation, and tests designed to be used by both the dbt-core and MetricFlow projects. By centralizing these shared resources, we aim to maintain consistency and reduce code duplication across both projects. Features: - Protocols for shared semantic classes: Define the interfaces and common attributes that must be implemented by the objects in both projects. - Validation: Ensure that the objects comply with the expected structure and constraints. - Tests: Ensure that the objects' behavior is consistent and correct across both projects. PR: 274581 Author: Pat Maddox <pat@patmaddox.com>433ffc21d6