devel/py-mediafile: Update to 0.17.0 Changes: https://github.com/beetbox/mediafile/releases https://mediafile.readthedocs.io/en/latest/changelog.htmld707e225d5
Port details
devel/py-mediafile 0.17.0
Handle low-level interfacing for files tags
- Maintainer
- sunpoet@FreeBSD.org
- Packages
- latest: 0.17.0
- Upstream
- up to date
- Last update
- to 0.17.0 · d707e225d5
- Quarterly
- 2026Q4: 0.17.0
- WWW
- https://mediafile.readthedocs.io/en/latest/
- Links
- cgit · VuXML
Unaddressed and VuXML only (0)
No unaddressed CVE and nothing reported by
pkg audit for the packaged version 0.17.0.Fixed (0)
No VuXML entries for this package.
Problem reports (0) · open in Bugzilla, most recently changed first
None.
Commits (19)
devel/py-mediafile: Update to 0.16.2 Changes: https://github.com/beetbox/mediafile/releases https://mediafile.readthedocs.io/en/latest/changelog.htmlf3148b5a77
devel/py-mediafile: Update to 0.16.0 Changes: https://github.com/beetbox/mediafile/releases https://mediafile.readthedocs.io/en/latest/changelog.html645d5f9c72
devel/py-mediafile: Update to 0.14.0 Changes: https://github.com/beetbox/mediafile/releases https://mediafile.readthedocs.io/en/latest/changelog.html2f56627983
devel/py-mediafile: Update version requirement of RUN_DEPENDS - Bump PORTREVISION for package change7f2ea96ad3
devel/py-mediafile: Update to 0.13.0 Changes: https://github.com/beetbox/mediafile/blob/master/docs/index.rst#changelog https://mediafile.readthedocs.io/en/latest/#changelogdc22e8f771
devel/py-mediafile: Update to 0.12.0 - Update WWW - Add LICENSE_FILE - Take maintainership Changes: https://github.com/beetbox/mediafile/blob/master/docs/index.rst#changelog https://mediafile.readthedocs.io/en/latest/#changelog66cb4bd2b3
Returning all my ports to the pool. - Unfortunately I have no time to maintain them anymore.53feed73dd
devel/py-mediafile: Fix BUILD_DEPENDS from pyproject.toml: [build-system] requires = ["flit_core >=2,<4"] build-backend = "flit_core.buildapi" Approved by: portmgr (blanket) With hat: python Reference: https://github.com/beetbox/mediafile/blob/v0.11.0/pyproject.toml#L1-L3bd392ab692
all: remove explicit versions in USES=python for "3.x+"
The logic in USES=python will automatically convert this to 3.8+ by
itself.
Adjust two ports that only had Python 3.7 mentioned but build fine
on Python 3.8 too.
finance/quickfix: mark BROKEN with PYTHON
libtool: compile: c++ -DHAVE_CONFIG_H -I. -I../.. -I -I. -I.. -I../.. -I../C++ -DLIBICONV_PLUG -DPYTHON_MAJOR_VERSION=3 -Wno-unused-variable -Wno-maybe-uninitialized -O2 -pipe -DLIBICONV_PLUG -fstack-protector-strong -fno-strict-aliasing -DLIBICONV_PLUG -Wall -ansi -Wno-unused-command-line-argument -Wpointer-arith -Wwrite-strings -Wno-overloaded-virtual -Wno-deprecated-declarations -Wno-deprecated -std=c++0x -MT _quickfix_la-QuickfixPython.lo -MD -MP -MF .deps/_quickfix_la-QuickfixPython.Tpo -c QuickfixPython.cpp -fPIC -DPIC -o .libs/_quickfix_la-QuickfixPython.o
warning: unknown warning option '-Wno-maybe-uninitialized'; did you mean '-Wno-uninitialized'? [-Wunknown-warning-option]
QuickfixPython.cpp:175:11: fatal error: 'Python.h' file not found
^~~~~~~~~~
1 warning and 1 error generated.
Reviewed by: portmgr, vishwin, yuri
Differential Revision: <https://reviews.freebsd.org/D40568>3d9a815d9cUSE_PYTHON=pep517: bump PORTREVISION1730e97e04
Revert "Mk/Uses/python.mk: Fix USE_PYTHON=pep517: always compile and install bytecode" Despite installer's default behaviour to compile and install bytecode, we are not doing so going forward at stage/package time. [0] During initial development and qualification of PEP-517 framework support, compiling and installing bytecode at stage/package time was considered, but was found problematic, fragile and ultimately unreliable, both currently and historically (with USE_PYTHON=distutils), due to our fixed plist requirement. While the living binary distribution format (wheel) specification [1] says to compile bytecode, that is in the pure Python package management context (pip, etc); nuance always exists when interacting with "system" package management. Additionally, "bytecode is an implementation detail of the CPython interpreter. No guarantees are made that bytecode will not be added, removed, or changed between versions of Python," thus "should not be considered to work across Python VMs or Python releases." [2] This is important to ensuring correctness for those ports specifying NO_ARCH. Instead of compiling and installing bytecode at stage/package time, there is a WIP, review D34739, that compiles and installs bytecode at install time instead, using triggers. The aforementioned build_fs_violations will be investigated. This reverts commit de6965254c3a007efcf697c3d455b54d2aeb2383. With hat: python Approved by: tcberner (mentor, portmgr) Reference: https://wiki.freebsd.org/Python/PEP-517 [0] https://packaging.python.org/en/latest/specifications/binary-distribution-format/ [1] https://docs.python.org/3/library/dis.html [2]f5890bd3cb
Mk/Uses/python.mk: Fix USE_PYTHON=pep517: always compile and install bytecode
- While I'm here, use long options for easier reading [1][2]
- Bump PORTREVISION of dependent ports (USE_PYTHON=pep517) for package change
It fixes build_fs_violation of dependent ports in poudriere (with -t flag).
It is also the default behavior of installer [2].
from py-sphinx log:
=>> Checking for staging violations... done
=>> Error: Filesystem touched during stage (files must install to ${STAGEDIR}):
extra: usr/local/lib/python3.9/site-packages/importlib_metadata/__pycache__
=>> Cleaning up wrkdir
from installer documentation:
--compile-bytecode
Possible choices: 0, 1, 2
generate bytecode for the specified optimization level(s) (default=0, 1)
--no-compile-bytecode
don’t generate bytecode for installed modules
Default: False
With hat: python
Reference: https://pypa-build.readthedocs.io/en/stable/ [1]
https://installer.pypa.io/en/stable/cli/installer/ [2]de6965254cdevel/py-mediafile: Fix build dependency. Reported by: vishwin13aa953e86
devel/py-mediafile: Update to 0.11.005af9fe1fc
*/*: rename CHEESESHOP to PYPI in MASTER_SITES PR: 267994 Differential revision: D37518 Approved by: bapt77d68471ad
Remove WWW entries moved into port Makefiles Commit b7f05445c00f has added WWW entries to port Makefiles based on WWW: lines in pkg-descr files. This commit removes the WWW: lines of moved-over URLs from these pkg-descr files. Approved by: portmgr (tcberner)fb16dfecae
Add WWW entries to port Makefiles It has been common practice to have one or more URLs at the end of the ports' pkg-descr files, one per line and prefixed with "WWW:". These URLs should point at a project website or other relevant resources. Access to these URLs required processing of the pkg-descr files, and they have often become stale over time. If more than one such URL was present in a pkg-descr file, only the first one was tarnsfered into the port INDEX, but for many ports only the last line did contain the port specific URL to further information. There have been several proposals to make a project URL available as a macro in the ports' Makefiles, over time. This commit implements such a proposal and moves one of the WWW: entries of each pkg-descr file into the respective port's Makefile. A heuristic attempts to identify the most relevant URL in case there is more than one WWW: entry in some pkg-descr file. URLs that are not moved into the Makefile are prefixed with "See also:" instead of "WWW:" in the pkg-descr files in order to preserve them. There are 1256 ports that had no WWW: entries in pkg-descr files. These ports will not be touched in this commit. The portlint port has been adjusted to expect a WWW entry in each port Makefile, and to flag any remaining "WWW:" lines in pkg-descr files as deprecated. Approved by: portmgr (tcberner)b7f05445c0
devel/py-mediafile: Add version 0.9.0 to the tree. - necessary to update audio/beets to 1.6.0ee32940aab