Hello,
unfortunately I can't find the right mail thread for this topic, but I
think this has been discussed here before.
The reason why I write: I saw that the problem in pkgsrc-current is
already solved:
```
author mrg <[email protected]> 2023-01-14 21:11:35 +0000
committer mrg <[email protected]> 2023-01-14 21:11:35 +0000
commit 711c521efb49e012473a36e4ec6cb6e2b986bf27 (patch)
tree 32122313d729b8bdf33986ef144ca20da283f547 /net/net-snmp
parent 4f05f5067c807a4435646f0040d96b1cfcb8c779 (diff)
handle merged inpcb code since 9.99.104:
http://mail-index.netbsd.org/source-changes/2022/10/28/msg141800.html
```
Is it possible and allowed by policy to aim for a pull-up of the patch
for pkgsrc-2022Q4? I know that 2023Q1 is practically around the corner,
and nothing should stop me from setting up a local patch to 2022Q4 for
myself. Nevertheless, net-snmp alone on my small limited pkglist is
responsible as (in)direct dependency for the failure of the buids of
about 150 packages, including Ejabberd, RabbitMQ and Pandoc. So this
might be affecting other users too?
Kind regards
Matthias
