This thing just doesn’t work at all. It’s a client for a site that has been dead for 7 years.

I really want to say we should just put this one out of its misery, but I guess it has one connection to a package we might conceivably want to work in Nixpkgs through ofxclient and ledger-autosync. There’s a report here: egh/ledger-autosync#141.

I see a few options here:

1. Send a PR to ledger-autosync moving it to the more modern ofxtools; it looks like there isn’t that much code or API surface being exercised, although it would be a compatibility‐breaking change because they pass a configuration file directly to ofxclient. This would be firmly supererogatory FOSS ecosystem behaviour and I don’t at all expect you to actually do it.

2. Patch ofxhome out of ofxclient, send a probably‐futile upstream PR to the same maintainer’s other dormant project. But that might be gnarly and it’s possible they’re quite coupled.

3. Keep this zombie package alive just for its reverse dependencies.

4. Remove ledger-autosync entirely (but apparently even in its current state it does still work with downloaded OFX files).

Do you have any inclinations here? I don’t have any desire to block doing 3 as this is clearly an improvement on the status quo, but this kind of rot does make me wish we could take the opportunity to apply a little pressure on the ecosystem here. Don’t burn yourself out sending patches to random upstreams though :) It seems like ledger-autosync still has users and still works, so it’s probably best to just keep this building for now and hope that someone who actually cares migrates ledger-autosync to ofxtools.

Result of nixpkgs-review pr 327239 run on x86_64-linux 1

Merging this for now; hopefully downstreams will catch up in time. Thanks!