non port: security/py-securesystemslib/Makefile |
Number of commits found: 26 |
Saturday, 9 Mar 2024
|
15:22 Po-Chuan Hsieh (sunpoet)
security/py-securesystemslib: Convert to USE_PYTHON=pytest
Approved by: portmgr (blanket)
With hat: python
52a31bf |
Saturday, 16 Dec 2023
|
13:11 Muhammad Moinur Rahman (bofh)
security/py-securesystemslib: Unbreak
ce6ea74 |
Tuesday, 5 Dec 2023
|
17:29 Muhammad Moinur Rahman (bofh)
security/py-securesystemslib: Update version 0.30.0=>0.31.0
Changelog:
https://github.com/secure-systems-lab/securesystemslib/releases/tag/v0.31.0
1183e14 |
Wednesday, 4 Oct 2023
|
13:05 Muhammad Moinur Rahman (bofh)
security/py-securesystemslib: Update version 0.29.0=>0.30.0
Changelog:
https://github.com/secure-systems-lab/securesystemslib/releases/tag/v0.30.0
2d5d125 |
Friday, 29 Sep 2023
|
14:19 Po-Chuan Hsieh (sunpoet)
*: Replace USES=pycryptography* with USE_PYTHON=cryptography{,_build,_test}
- Introduce USE_PYTHON=cryptography{,_build,_test}
- Switch all 96 ports from USES=pycryptography to with
USE_PYTHON=cryptography{,_build,_test}
- Remove Mk/Uses/pycryptography.mk
PR: 273727
Approved by: tcberner (portmgr)
Exp-run by: antoine
3754fc5 |
Monday, 11 Sep 2023
|
06:17 Muhammad Moinur Rahman (bofh)
security/py-securesystemslib: Update version 0.28.0=>0.29.0
Changelog:
https://github.com/secure-systems-lab/securesystemslib/releases/tag/v0.29.0
146e777 |
Saturday, 22 Jul 2023
|
07:46 Tobias C. Berner (tcberner)
framework: convert tree to use USES=pycryptography
A future commit will update to security/py-cryptography will introduce a
rust dependency.
PR: 254853
b28a739 |
Tuesday, 27 Jun 2023
|
19:34 Rene Ladan (rene)
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>
3d9a815 |
Wednesday, 19 Apr 2023
|
18:17 Muhammad Moinur Rahman (bofh)
security/py-securesystemslib: Update version 0.27.0=>0.28.0
Changelog:
https://github.com/secure-systems-lab/securesystemslib/releases/tag/v0.28.0
1f0077e |
Tuesday, 4 Apr 2023
|
18:29 Antoine Brodin (antoine)
USE_PYTHON=pep517: bump PORTREVISION
1730e97 |
Thursday, 30 Mar 2023
|
15:56 Muhammad Moinur Rahman (bofh)
security/py-securesystemslib: Update version 0.26.0=>0.27.0
Changelog:
https://github.com/secure-systems-lab/securesystemslib/releases/tag/v0.27.0
2d80e55 |
Sunday, 5 Feb 2023
|
19:05 Charlie Li (vishwin)
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]
f5890bd |
18:16 Po-Chuan Hsieh (sunpoet)
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]
de69652 |
Thursday, 2 Feb 2023
|
12:20 Muhammad Moinur Rahman (bofh)
security/py-securesystemslib: Update version 0.25.0=>0.26.0
- Change to pep517 from distutils
Relnotes:
https://github.com/secure-systems-lab/securesystemslib/releases/tag/v0.26.0
b996d35 |
Wednesday, 11 Jan 2023
|
15:58 Dmitry Marakasov (amdmi3)
*/*: rename CHEESESHOP to PYPI in MASTER_SITES
PR: 267994
Differential revision: D37518
Approved by: bapt
77d6847 |
Saturday, 5 Nov 2022
|
14:19 Muhammad Moinur Rahman (bofh)
security/py-securesystemslib: Update version 0.23.0=>0.25.0
Relnotes:
https://github.com/secure-systems-lab/securesystemslib/releases/tag/v0.25.0
132aedc |
Wednesday, 7 Sep 2022
|
21:10 Stefan Eßer (se)
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)
b7f0544 |
Saturday, 7 May 2022
|
21:37 Muhammad Moinur Rahman (bofh)
security/py-securesystemslib: Update version 0.22.0=>0.23.0
Relnotes:
https://github.com/secure-systems-lab/securesystemslib/releases/tag/v0.23.0
7821f0e |
Wednesday, 27 Apr 2022
|
11:42 Dmitry Marakasov (amdmi3)
security/py-securesystemslib: switch to USES=pytest, fix tests
Reported by: reprise
Approved by: portmgr blanket
d7176a1 |
Saturday, 12 Mar 2022
|
10:28 Muhammad Moinur Rahman (bofh)
security/py-securesystemslib: Update 0.22.0
- Change MASTER_SITES to CHEESESHOP
Relnotes:
https://github.com/secure-systems-lab/securesystemslib/releases/tag/v0.22.0
13453b3 |
Tuesday, 8 Mar 2022
|
02:09 Muhammad Moinur Rahman (bofh)
*/*: Take maintainership
bc808e2 |
Monday, 7 Mar 2022
|
19:07 Rene Ladan (rene)
all: return koobs' ports to the pool after safekeeping his commit bit.
3d89f95 |
Wednesday, 7 Apr 2021
|
08:09 Mathieu Arnold (mat)
One more small cleanup, forgotten yesterday.
Reported by: lwhsu
cf118cc |
Tuesday, 6 Apr 2021
|
14:31 Mathieu Arnold (mat)
Remove # $FreeBSD$ from Makefiles.
305f148 |
Monday, 28 Dec 2020
|
23:02 antoine
Drop python 2.7 support from a few ports
With hat: portmgr
|
Tuesday, 14 May 2019
|
09:25 koobs
[NEW PORT] security/py-securesystemslib: Cryptographic and general-purpose
routines
securesystemslib supports public-key and general-purpose cryptography,
such as ECDSA, Ed25519, RSA, SHA256, SHA512, etc. Most of the
cryptographic operations are performed by the cryptography and PyNaCl
libraries, but verification of Ed25519 signatures can be done in pure
Python.
WWW: https://github.com/secure-systems-lab/securesystemslib
[1] https://github.com/secure-systems-lab/securesystemslib/issues/166
[2] https://github.com/secure-systems-lab/securesystemslib/issues/167
|
Number of commits found: 26 |