portlist.tcl: illegal byte sequence

[Joshua Root]

On 27/12/2025 06:19, Jason Liu wrote:
> Is this a common occurrence that other people have seen happen before? 

I've never seen any other reports of this happening with files in 
MacPorts base. We're familiar with "illegal byte sequence" errors in the 
context of running tools like sed, but that happens when LANG or 
LC_CTYPE is set to use an encoding that does not match the file 
contents. Base makes sure to use UTF-8 for everything (and if it didn't, 
any resulting problems would presumably affect everyone).

> Could this also be (perhaps tangentially) related to my previous 
> message/thread, regarding "Strange curl4/openssl3 error messages when 
> building a local port", where I had to deactivate/reactivate the 
> openssl3 port to fix a libssl.3.dylib where the first eight bytes were 
> somehow all zero?
It certainly seems possible.

- Josh