This is a beta release, only for testing, and not yet supported - do not
use for production repos. Note that this is a major - breaking -
release, and is not compatible with existing repos.
OK kn@
Same fix as the borg 1.1 one except that borg 1.2 uses ports py-msgpack
which has more consumers than borg 1.2, hence the separate commit.
$ borg init -e none ./repo ; echo $?
Unknown integrity data version 0 in integrity.1
0
msgpack-python messed up __BYTE_ORDER handling, but only on sparc64 using
ports GCC 8.4.0; macppc base clang 13 is fine.
msgpack-python got fixed, pull the PR and bump borg 1.2.
Teste on little endian amd64/base-clang and big endian macppc/base-clang,
sparc64/ports-gcc.
OK bket
$ borg init -e none ./repo ; echo $?
Unknown integrity data version 0 in integrity.1
0
borg 1.1.x bundles msgpack-python, which messed up __BYTE_ORDER handling,
but only on sparc64 using ports GCC 8.4.0; macppc base clang 13 is fine.
msgpack-python got fixed, borg's 1.1-maint branch merged it, pull the PR.
borgbackup/1.2 and py-msgpack will get the same fix but in a different
commit as py-msgpack has more consumers than borg 1.2.
Tested on little endian amd64/base-clang and big endian macppc/base-clang,
sparc64/ports-gcc.
OK bket
Although this update plays nicely with releases from the 1.1 branch, and
strictly taken, nothing special is required for upgrading, the old
version is retained by splitting into 1.1 and 1.2 subdirectories. This
gives users the opportunity to update their scripts.
Changelog, including upgrade and compatibility notes, can be found at
https://github.com/borgbackup/borg/blob/1.2.0/docs/changes.rst#version-120-2022-02-22-220222--.
Thanks to Martin Ziemer <horrad AT horrad DOT de> for testing.
OK sthen@
if a port needs 2.x then set MODPY_VERSION=${MODPY_DEFAULT_VERSION_2}.
This commit doesn't change any versions currently used; it may be that
some ports have MODPY_DEFAULT_VERSION_2 but don't require it, those
should be cleaned up in the course of updating ports where possible.
Python module ports providing py3-* packages should still use
FLAVOR=python3 so that we don't have a mixture of dependencies some
using ${MODPY_FLAVOR} and others not.
Bugfix release. Noticeable change is that the latest supported
msgpack-python release is bundled. Changelog can be found at
https://github.com/borgbackup/borg/blob/1.1.10/docs/changes.rst#version-1110-2019-05-16
Switching to the bundled version of msgpack-python makes sense as the
version in ports is in need of an update: msgpack-python has been
renamed by its upstream, and borgbackup was seemingly the only port
unable to cope with this renaming, thus blocking an update.
OK kn@
lang/python port module. I've not yet come up with a port that
would not need this and one can always set MODPY_TESTDEP to "no"
to prevent the module from touching TEST_DEPENDS.
Idea from afresh1 who pointed out the cpan module already does this.
aja "I support this move."
OK sthen@
lang/python/python.port.mk revision 1.102 and 1.103 added
MODPY_TEST_LOCALE and MODPY_PYTEST respectively, nicely wrapping up the
usual pytest dance.
This removes hand-rolled do-tests from all 70 ports by setting
MODPY_PYTEST=Yes and MODPY_TEST_LOCALE as well as HOME=${WRKDIR} to TESTENV
as needed.
From Kurt Mosiejczuk <kurt at cranky dot work>, thanks!
OK sthen
maintainer Björn Ketelaars
CVE-2017-15914: Incorrect implementation of access controls allows
remote users to override repository restrictions in Borg servers. A user
able to access a remote Borg SSH server is able to circumvent access
controls post-authentication. Affected releases: 1.1.0, 1.1.1, 1.1.2.
Releases 1.0.x are NOT affected.
