Do we want to go from installing man pages by default to not installing them by default?

I don't plan on committing this without a better understanding of why it's happening. Adding yuri, since he made a similar change recently.

For some reason, the upstream mod file changed. https://pkg.ftfl.ca/data/15amd64-default/2025-03-06_10h57m00s/logs/errors/termshot-0.2.12_1.log

It fails to build. Do you need a dependency on multimedia/v4l_compat?

Committed.

Update Canna patches

Also bump japanese/mozc-server.

Emacs 30.1 is released. I will put the PORTREVISION bumps in a separate review. Minor changes will be required when HIROSE yuuji updates the canna patch.

There are a few other instances of HTTP/2.0 in the tree.

This can't build because there is no distinfo file.

Looks like I didn't need to commandeer the review to make changes.

Minor tweaks mostly to improve formatting.

Mk/Uses: Update EMACS_VER to 30.1

Update for RC1

Yes, this information is in other report entries, so this can be closed.

Could you confirm that it also builds fine on 14 and that all reverse dependencies also build fine? My grep shows these ports as the reverse dependencies:

audio/owntone
audio/umurmur
dns/bind9-devel
dns/bind918
dns/bind920
dns/knot-resolver
dns/knot3
dns/nsd
databases/postgis31
databases/postgis33
databases/postgis34
databases/postgis35
databases/postgresql-cstore_fdw
dns/unbound
graphics/mapserver
net/frr10
net/frr9
net-im/purple-googlechat
net-mgmt/collectd5
net/nmsg
net/ocserv
polish/libgadu
net-mgmt/riemann-c-client
science/py-tensorflow
net/sie-nmsg
net/teddycloud
x11-toolkits/libshumate

Sounds good. You also need to bump PORTREVSION.

Should the patch be removed from other JDK ports as well?

In D48698#1111309, @michaelo wrote:

Will leave time until Saturday and then will merge.

Looks good. Ideally, we would confirm that the reverse dependencies [0] are good.

Looks good, but we should also hear from @sunpoet. (That's always implied when I approve changes to a port someone else maintains.)

In the commit log, you say,

List also the Python version limitation since none is documented.

If you're feeling motivated:

• it might be helpful (at some point) to upstream the patch
• see if portfmt -D Makefile has anything useful to say about the formatting.

It's not such a big deal in these particular cases, but as a matter of principle, I felt it was worth mentioning that pushing another committer's review without first discussing it with the committer can lead to problems. Is the commit really ready? Is the commit log ready? (Without using something like git arc Phabricator can mess with the commit log.) Are there any other commits that must be committed first?

Rather than have a messy commit log, it's best (from my perspective) to leave things as they are now.

@carlavilla, in the future, could you please not commit my work without discussing it with me first?

Incorporate correction spotted by Pau Amma