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>
Borgbackup pins the exact, full, patch-level based version range
and the prior borgbackup 1.2.3 wanted to have at most msgpack 1.0.4.
Update to 1.2.4 which allows msgpack 1.0.5, and pin the exact msgpack
version in our depends to "fail early".
And other changes including bug fixes:
https://github.com/borgbackup/borg/blob/1.2.4/docs/changes.rst#version-124-2023-03-24
based on a
PR: 270665
Submitted by: otis@
As in-depth soft robustness measure, add relevant warning comments to
devel/py-msgpack/Makefile, and while there, clean up the python:3.6+
to just a bare python because 3.6 and older are long gone from ports.
This avoids build failures when, for instance, BORG_NEW_PASSWORD
is set to another password than the one used by the self-tests.
Reported by: SimpleRezo <simplerezo@gmail.com>
PR: 266821
Not bumping PORTREVISION because this only affects the execution
of self-tests, which is pass (then the change is irrelevant) or fail
(then there is no package or installed port and PORTREVISION would
serve no purpose).
Commit b7f05445c0 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)
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)
Building as non-root often inherits the "nobody" user's would-be home
directory, "/nonexistent", which is just that. Provide something blank
in the WRKDIR instead.
Reported by: Juraj Lutter (otis@)
Unrelated to, but still mentioned for...
PR: 264816
Take maintainership, because original maintainer asked for a new
maintainer, https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264816#c10
¡Muchas gracias, José! Thanks for maintaining the port thus far.
If there is a potential maintainer who is using BorgBackup at scale,
I will be happy to pass maintainership on.
Update to v1.2.2 [1, was for 1.2.1],
preserve the earlier 1.1.18 version (also with manpages and self-tests added,
hence bumping PORTREVISION) as py-borgbackup11, and document this in UPDATING.
ChangeLog: https://www.borgbackup.org/releases/borg-1.2.html
Add self-tests [1] to both 1.1 and 1.2, including
- a smoke test in post-install in order to always run it
- "make test" support (requires network access for tox)
PR: 264816 [1]
Reported by: rob2g2-freebsd@bitbert.com [1]
Add manual pages to both 1.1 and 1.2. [2]
PR: 263269 [2]
Reported by: courtney.hicks1@icloud.com [2]
This reverts commit 9db903a89b because
it does not fix the situation for lack of a PORTREVISION bump.
Let us use the opportunity to fix the real bug instead.
Now with xxhash fixed as of 0.8.1_2, drop 9db903a89, and
bump PORTREVISION so we flush out the old garbage packages.
A simple web search would have brought up that static_assert() is
a C11 convenience macro defined in <assert.h>, and a detailed
search would have turned up that this had been fixed in xxhash
before.
While here, add a smoke test to post-install.
Proper fix was
Reported by: Thierry Dussuet <thierry.dussuet@protonmail.com>
PR: 265060
MFH: 2022Q3
Newer python versions (after 3.8.7) have changed the names of extension
shared libraries from ".so" to e.g. ".cpython-38.so". So for the FUSE
option, now check for the py-llfuse package instead of the dynamic
library llfuse.so.
Approved by: jjuanino@gmail.com (maintainer)
PR: 253907
MFH: 2021Q
- Bump PORTREVISION for dependency change
remko@ notified me that there is runtime issue with msgpack 0.6.1.
And upstream has added version check to the repository that will terminate for unsupported msgpack.
- Update RUN_DEPENDS
- Bump PORTREVISION for package change
Bump msgpack requirement to 0.5.6 which is the only acceptable 0.5.x version [1].
PR: 227717
Reported by: <iron.udjin@gmail.com>
Submitted by: sunpoet (myself)
Approved by: Jose Garcia Juanino <jjuanino@gmail.com>
Reference: https://github.com/borgbackup/borg/issues/3753 [1]
This can be removed with newer liblz4 since the file format has been changed back to ASCII.
PR: 225235
Submitted by: Jose Garcia Juanino <jjuanino@gmail.com> (maintainer)
Reference: https://github.com/lz4/lz4/pull/454
Ports using USE_PYTHON=distutils are now flavored. They will
automatically get flavors (py27, py34, py35, py36) depending on what
versions they support.
There is also a USE_PYTHON=flavors for ports that do not use distutils
but need FLAVORS to be set. A USE_PYTHON=noflavors can be set if
using distutils but flavors are not wanted.
A new USE_PYTHON=optsuffix that will add PYTHON_PKGNAMESUFFIX has been
added to cope with Python ports that did not have the Python
PKGNAMEPREFIX but are flavored.
USES=python now also exports a PY_FLAVOR variable that contains the
current python flavor. It can be used in dependency lines when the
port itself is not python flavored. For example, deskutils/calibre.
By default, all the flavors are generated. To only generate flavors
for the versions in PYTHON2_DEFAULT and PYTHON3_DEFAULT, define
BUILD_DEFAULT_PYTHON_FLAVORS in your make.conf.
In all the ports with Python dependencies, the *_DEPENDS entries MUST
end with the flavor so that the framework knows which to build/use.
This is done by appending '@${PY_FLAVOR}' after the origin (or
@${FLAVOR} if in a Python module with Python flavors, as the content
will be the same). For example:
RUN_DEPENDS= ${PYTHON_PKGNAMEPREFIX}six>0:devel/py-six@${PY_FLAVOR}
PR: 223071
Reviewed by: portmgr, python
Sponsored by: Absolight
Differential Revision: https://reviews.freebsd.org/D12464
