[Bug 276478] Mk/*: Build with a clean environment

2024-01-22 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=276478

Marcin Cieślak  changed:

   What|Removed |Added

 CC||sa...@saper.info

--- Comment #3 from Marcin Cieślak  ---
What does it mean that "build on host" is demoted?

@Tijl: I think TERM should be explicitly left out. I am not sure if the colors
are that important (for example, I like to diff good/failed build logs to find
out what went wrong and ANSI color sequences make it diffiult or ugly).

-- 
You are receiving this mail because:
You are on the CC list for the bug.


[Bug 276359] security/py-flask-saml: Update to 0.5.1

2024-01-22 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=276359

--- Comment #2 from John W. O'Brien  ---
(In reply to commit-hook from comment #1)

Thanks for taking this, Wen.

It looks like the commit that landed is a little different than the patch I
prepared when it comes to security/py-pysaml* in RUN_DEPENDS. I'm inclined to
believe this was a mistake, since "pysaml24>=6.5.0<5" is self-evidently
unsatisfiable.

 .if ${PYTHON_REL} < 30900
RUN_DEPENDS+=  
${PYTHON_PKGNAMEPREFIX}pysaml26>=6.5.0:security/py-pysaml26@${PY_FLAVOR}
 .else
RUN_DEPENDS+=  
${PYTHON_PKGNAMEPREFIX}pysaml2>=6.5.0:security/py-pysaml2@${PY_FLAVOR}
 .endif

Flask-SAML itself claims support for Python 3.8 or higher. PySAML, on the other
hand, dropped support for 3.8 as of 7.4.0. security/py-pysaml26 still satisfies
the ">=6.5.0" dependency and supports 3.8.

What's your perspective?

-- 
You are receiving this mail because:
You are on the CC list for the bug.