https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=266680
Bug 266680 depends on bug 254853, which changed state.
Bug 254853 Summary: security/py-cryptography: Update to 41.0.3
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254853
What|Removed |Added
--
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=266680
Bug 266680 depends on bug 254853, which changed state.
Bug 254853 Summary: security/py-cryptography: Update to 41.0.3
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254853
What|Removed |Added
--
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=266680
--- Comment #22 from Charlie Li ---
(In reply to Li-Wen Hsu from comment #16)
Anyone who sets legacy for the cryptography DEFAULT_VERSIONS is a consumer.
While not visible on say FreshPorts or anything that tracks the default
DEFAULT_VERSIO
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=266680
--- Comment #21 from Enji Cooper ---
(In reply to Li-Wen Hsu from comment #16)
We will need to come up with a story around these -legacy vs non-legacy
consumers: the -legacy ones will need to be marked broken on >=3.x and the
non-legacy on
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=266680
Li-Wen Hsu changed:
What|Removed |Added
Resolution|--- |FIXED
Status|In Progress
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=266680
Bug 266680 depends on bug 254853, which changed state.
Bug 254853 Summary: security/py-cryptography: Update to 41.0.3
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254853
What|Removed |Added
--
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=266680
--- Comment #20 from László Károlyi ---
(In reply to commit-hook from comment #19)
Can confirm this patch/update works, it fixed my policyd-spf (that uses
py-openssl) problem.
Cheers,
László
--
You are receiving this mail because:
You a
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=266680
--- Comment #19 from commit-h...@freebsd.org ---
A commit in branch main references this bug:
URL:
https://cgit.FreeBSD.org/ports/commit/?id=11e8f3c89438ceef19d425937a4e9de5085f9002
commit 11e8f3c89438ceef19d425937a4e9de5085f9002
Author:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=266680
Li-Wen Hsu changed:
What|Removed |Added
Assignee|ports-b...@freebsd.org |lw...@freebsd.org
Status|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=266680
Li-Wen Hsu changed:
What|Removed |Added
Blocks||273473
Referenced Bugs:
https://bug
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=266680
bagas changed:
What|Removed |Added
CC||bagas1...@mail.ru
--- Comment #17 from bag
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=266680
--- Comment #16 from Li-Wen Hsu ---
(In reply to Charlie Li from comment #15)
I think it's not hurry now, as currently there is no consumer of
py-cryptography-legacy or the direct consumer of legacy py-openssl (which uses
py-cryptography-le
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=266680
--- Comment #15 from Charlie Li ---
Not so fast.
Since we have both mainline and legacy cryptography ports, with a
DEFAULT_VERSIONS knob to boot, this port actually has to provide both versions,
gated on the set DEFAULT_VERSIONS. Different
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=266680
Jonathan Chen changed:
What|Removed |Added
CC||j...@chen.org.nz
--- Comment #14 f
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=266680
László Károlyi changed:
What|Removed |Added
CC||las...@karolyi.hu
--- Comment #13
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=266680
--- Comment #12 from Enji Cooper ---
Hi sunpoet -- is there a reason why the patches you're posting (for this and
bug 254853) aren't making it into the ports tree?
--
You are receiving this mail because:
You are on the CC list for the bug
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=266680
Po-Chuan Hsieh changed:
What|Removed |Added
CC||sunp...@freebsd.org
--- Comment #
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=266680
Enji Cooper changed:
What|Removed |Added
Summary|security/py-openssl: Update |security/py-openssl: Update
18 matches
Mail list logo
