The guix-daemon does the hashing, so guix-daemon would have to be fixed to override integrity checks (and it would have to be patched retroactively in every time-travel). Noone likes touching guix-daemon (until it is rewritten in Guile), so I can imagine it would be frustrating.
Now ftfy is not in Guix, but if Software Heritage deleted the data, their customers might be equally frustrated. It is SWH’s obligation to delete the data, but looking at how rare GDPR action is and how frequently Icecat’s TPRB add-on lays bare GDPR violations, if they do not follow the obligation, there likely will not be legal action or the legal action can be dismissed somehow. The problem is, such inaction by SWH may be relevant for Guix’ Code of Conduct, as pointed out by MSavoritias. Regards, Florian
