Jeremy Chadwick

Oh, one thing I should add: fb2k x64 **is not** compatible with x86/32-bit fb2k components. So users may want to consider using `choco install --forcex86 foobar2000` even on x64 systems...

That's a fair point! I suppose an alternate solution might be to make a separate foobar2000-x64 package and submit that to the Chocolatey folks for review. Otherwise, yeah, an in-place...

> > fdm -n -f test.fdm.conf does not complain about this questionable syntax, but the man page implies it should be considered invalid: > > [...] > > Mmm, why/what?...

Another one to add to the list as an example of where uninstaller exit codes are important: `winget uninstall mirc`. This one is amusing in itself, as it uses the...

> > The uninstaller exits with an exit code of 1223 > > The NSIS exit codes are 0 for success, 1 for user cancel and 2 for cancelled by...

Got bit by this today when trying to build mdbook-katex. Is there a reason you have to dynamically apply a diff during software build, rather than just having it pre-applied?...

I should add that the Cygwin and MSYS2 logic is correct, but might want `BINARY=asm6f.exe` since both environments support standard Windows binaries ending in `.exe`. Issue https://github.com/freem/asm6f/issues/23 indirectly points this...

@freem This is now in a very good state. I have personally tested building on: * MSYS2 MINGW64 (gcc) * MSYS2 CLANG64 (Clang) * MSYS2 UCRT64 (gcc and Clang) *...

`superiotool` output is not helpful here, sorry to say. It gives me "some ideas" (specifically that one of the chips does live on SMBus, as "0x2e" looks like a slave...

Great! I've put in a request to Supermicro. They usually take anywhere from 5 to 10 business days to respond to these type of requests. If I don't get a...