pcmanfm-qt: update to 2.4.1
pkgsrc does not include the change "Set desktop screen explicitly on
Wayland", since it requires a newer version of plasma6-layer-shell-qt
than pkgsrc carries presently and Wayland isn't really supported yet.
pcmanfm-qt-2.4.1 / 2026-08-26
==============================
* Close tabs without close buttons by middle clicking with Qt >= 6.11.
* Workaround for a bad behavior of wlroots.
* Removed the redundant translations CMake file.
* Set desktop file name.
* Removed `<normaloff>` from ui files.
* Updated fsf address.
fctix: add missing ctype abuse fix patches
Two patches from the netbsd-11 ctype-abuse fixes of 2025-12-07 were
listed in distinfo r1.8 but apparently never committed.
https://mail-index.netbsd.org/pkgsrc-changes/2025/12/07/msg335023.html
This should fix bulk build on NetBSD 11.0 hosts, and
should be pulled up to pkgsrc-2026Q2.
nss: update to 3.128.
Changes in NSS 3.128
- Bug 2063360 - Rejoin the table cells the conversion wrapped mid-construct.
- Bug 2063360 - Generate heading anchors and stop the headings linking to themselves.
- Bug 2063360 - Unlink the self-linking headings in the release notes.
- Bug 2063360 - Point documentation cross-references at the dashed anchors.
- Bug 2063360 - Fix doc-lint in the release process.
- Bug 2066375 - Make fuzz tasks selectable with try syntax.
- Bug 2066375 - Build Cryptofuzz in its own CI task.
- Bug 2066604 - fix EC public key encoding in sftk_PutPubKey.
- Bug 2066183 - set CKA_ID on imported private keys.
- Bug 2017925 - Hash prfs need to be evaluated for indicators.
- Bug 2066327 - rename libcrux gyp target.
- Bug 2066415 - Update BoGo tests to disable ML_DSA Default test.
- Bug 2065354 - unify the two clang-format docker images.
- Bug 2056265 - -trust-cert for TLS BoGo tests.
- Bug 2056235 - DTLS1.2/1.3 - silently discard invalid records.
[30 lines not shown]
net/opentofu112: import opentofu112-1.12.6
OpenTofu is an OSS tool for building, changing, and versioning
infrastructure safely and efficiently. OpenTofu can manage existing and
popular service providers as well as custom in-house solutions.
The key features of OpenTofu are:
* Infrastructure as Code: Infrastructure is described using a
high-level configuration syntax. This allows a blueprint of your
datacenter to be versioned and treated as you would any other code.
Additionally, infrastructure can be shared and re-used.
* Execution Plans: OpenTofu has a "planning" step where it generates
an execution plan. The execution plan shows what OpenTofu will do
when you call apply. This lets you avoid any surprises when
OpenTofu manipulates infrastructure.
* Resource Graph: OpenTofu builds a graph of all your resources, and
parallelizes the creation and modification of any non-dependent
resources. Because of this, OpenTofu builds infrastructure as
[9 lines not shown]
net/opentofu111: import opentofu111-1.11.14
OpenTofu is an OSS tool for building, changing, and versioning
infrastructure safely and efficiently. OpenTofu can manage existing and
popular service providers as well as custom in-house solutions.
The key features of OpenTofu are:
* Infrastructure as Code: Infrastructure is described using a
high-level configuration syntax. This allows a blueprint of your
datacenter to be versioned and treated as you would any other code.
Additionally, infrastructure can be shared and re-used.
* Execution Plans: OpenTofu has a "planning" step where it generates
an execution plan. The execution plan shows what OpenTofu will do
when you call apply. This lets you avoid any surprises when
OpenTofu manipulates infrastructure.
* Resource Graph: OpenTofu builds a graph of all your resources, and
parallelizes the creation and modification of any non-dependent
resources. Because of this, OpenTofu builds infrastructure as
[13 lines not shown]
net/opentofu110: import opentofu110-1.10.10
OpenTofu is an OSS tool for building, changing, and versioning
infrastructure safely and efficiently. OpenTofu can manage existing and
popular service providers as well as custom in-house solutions.
The key features of OpenTofu are:
* Infrastructure as Code: Infrastructure is described using a
high-level configuration syntax. This allows a blueprint of your
datacenter to be versioned and treated as you would any other code.
Additionally, infrastructure can be shared and re-used.
* Execution Plans: OpenTofu has a "planning" step where it generates
an execution plan. The execution plan shows what OpenTofu will do
when you call apply. This lets you avoid any surprises when
OpenTofu manipulates infrastructure.
* Resource Graph: OpenTofu builds a graph of all your resources, and
parallelizes the creation and modification of any non-dependent
resources. Because of this, OpenTofu builds infrastructure as
[13 lines not shown]
net/opentofu16: import opentofu16-1.6.3
OpenTofu is an OSS tool for building, changing, and versioning
infrastructure safely and efficiently. OpenTofu can manage existing and
popular service providers as well as custom in-house solutions.
The key features of OpenTofu are:
* Infrastructure as Code: Infrastructure is described using a
high-level configuration syntax. This allows a blueprint of your
datacenter to be versioned and treated as you would any other code.
Additionally, infrastructure can be shared and re-used.
* Execution Plans: OpenTofu has a "planning" step where it generates
an execution plan. The execution plan shows what OpenTofu will do
when you call apply. This lets you avoid any surprises when
OpenTofu manipulates infrastructure.
* Resource Graph: OpenTofu builds a graph of all your resources, and
parallelizes the creation and modification of any non-dependent
resources. Because of this, OpenTofu builds infrastructure as
[13 lines not shown]
net: Remove opentofu
Several opentofu versions will be imported with version suffixes in order to
permit a full migration from Terraform.
Discussed on tech-pkg@ and no negative feedbacks
<https://mail-index.NetBSD.org/tech-pkg/2026/03/04/msg032042.html>
(it took a bit more than a week to import them though, sorry!)
opentofu: Remove, it will be imported as opentofu*
opentofu will be reimported as opentofu16, opentofu110 and opentofu111
in order to permit a complete Terraform to OpenTofu migration in
pkgsrc.
Discussed on tech-pkg@ and no negative feedbacks
<https://mail-index.NetBSD.org/tech-pkg/2026/03/04/msg032042.html>
(it took a bit more than a week to import them though, sorry!)
