mail/mutt: Update to version 2.4.2
This release fixes several minor bugs. The most interesting one is a
sporadic compose-menu prompt to update attachment encoding, occurring with
recent Linux kernels. See commit 9196c96e for more details.
The full set of changes are:
190ee83d Fix minor manual errors.
97e7e5f3 Fix <get-attachment> to remove attachments upon compose abort.
0df49f39 Fix <get-attachment> to use $tmpdraftdir.
9196c96e Change attachment stamping to use stat st_mtime by default.
55fed13f Fix OpenBSD build on sr.ht.
d74acef9 Fix Arch build on sr.ht:
aad2dde2 Fix minor typo in UPDATING file
4fc103f0 Set GPGME key flags when getting candidates.
cad/apio: Update 1.5.0 => 1.5.1
* Clarify LICENSE [0]
[0] https://github.com/FPGAwars/apio/issues/778
* Fix USE_PYTHON=concurrent when only one of Python 2 or 3 is supported
AND not using flavors does not make any sense (by portlint(1))
* Replace custom shebang fixing with standard one
Approved by: yuri@ (maintainer)
Differential Revision: https://reviews.freebsd.org/D59210
cad/apio: Update 1.5.0 => 1.5.1
* Clarify LICENSE [0]
[0] https://github.com/FPGAwars/apio/issues/778
* Fix USE_PYTHON=concurrent when only one of Python 2 or 3 is supported
AND not using flavors does not make any sense (by portlint(1))
* Replace custom shebang fixing with standard one
Approved by: yuri@ (maintainer)
Differential Revision: https://reviews.freebsd.org/D59210
[lldb-dap] Return an error on evaluation failure (#219245)
We currently return an error response a command doesn't exist. We should
do the same when a command fails. This allow the client differentiate
failed commands and hint them properly.
Delay starting HTML output until we are sure that we have some data
to offer to the user, either from a manual page file that can actually
be opened or at least a list of links to pages matching the user's query.
When no information whatsoever can be accessed, always return
HTTP 400 Bad Request (e.g. for an unsupported, nonexistent, or unreadable
path or an invalid architecture) or HTTP 500 Internal Server Error (e.g.
for a system call failure, an inaccessible or invalid configuration file,
an inaccessible directory, or a corrupt database).
This also prepares for pledge(2)/unveil(2) improvements by making it
possible to invoke these system calls after open(2)ing the chosen
manual page file.
