Revert "[clang][driver][darwin] Hold onto full triples in Darwin SDKPlatformInfo (#200896)" (#202010)
This doesn't work for 32 bit arm because that usually gets converted to
thumb-apple-os, and that doesn't match arm-apple-os from
SDKSettings.json.
This reverts commit b89bb06afd069aa1b5e9f05ab692b3e6b41318c0.
py-uvicorn: updated to 0.49.0
0.49.0
Bump httptools minimum version to 0.8.0
Consume duplicate forwarding headers in ProxyHeadersMiddleware (reverses the 0.48.0 behavior of ignoring them)
Revert "ftp/surge: remove, dupplicate of www/surge"
This reverts commit 07508310021e4d52e154090563ae4c0b4812ee23.
We agreed with olgeni at FreeBSD.org that this port stays.
gcc15-gnat: update to 15.2.0nb2
* Update common patches from upstream gcc15 package
* Update libgnat BSD socket implementation
* Improve using builtin binutils version on NetBSD 11
* Fix tasking implementation on NetBSD
- now GNAT does not use alternate stack for tasking
on NetBSD: see pthread CAVEATS
- add affinity/ceiling support
ansible-core: updated to 2.21.0
v2.21.0
Major Changes
- ``ansible-galaxy install`` and ``ansible-galaxy collection install|download`` - collections that declare a ``requires_ansible`` version that is not compatible with the running ansible-core version are now excluded from installation and download by default. In previous versions, ansible-galaxy would install such collections even if doing so resulted in an error at load time. To restore the previous behavior, set ``COLLECTIONS_ON_ANSIBLE_VERSION_MISMATCH`` to ``ignore`` in your configuration. (https://github.com/ansible/ansible/issues/78539)
- action plugins - Actions can directly register variables at several precedence layers using the ``register_host_variables`` method on ``ActionBase``. Previously, variable registration could only be simulated by user action plugins by returning ``ansible_facts`` with insecure fact injection.
- register projections - The ``register`` task keyword allows mapping multiple variable names to Jinja expressions to transform task results and other variables. The mapping form can replace many usages of ``set_fact`` and allows order-independent chained access to other variable expressions within the same task.
- task implicit object - A new ``_task`` implicit object is available for use in ``register`` and task conditional expressions (e.g., ``failed_when``). The result of the current task can be accessed via the ``_task.result`` property, without the use of ``register``. Under a loop, ``_task.result`` is the most recently completed result and ``_task.loop_result`` provides access to accumulated loop results. The ``_task.polymorphic_result`` property provides compatibility with classic name-only ``register`` in loops. The value is the result of the most recent loop iteration, then becomes the final list loop result once the loop is complete.
