ティージェーグレェ on Nostr: Thanks to neverpanic, my PR to update MacPorts' signify has been merged! But now I'm ...
Thanks to neverpanic, my PR to update MacPorts' signify has been merged!
But now I'm listed as a maintainer and repology.org has this as a ding against me because it tracks signify version numbers from some different downstream aimed at Linux.
There is no signify-portable branch and thus no authoritative signify version.
MacPorts' is basically updated from OpenBSD's sources from December 2024 now.
How to fix this?
Submit a PR to repology?
Start a signify-portable project? That seems like a nightmare I don't want to tackle.
Ignore it? I'm leaning towards ignoring.
At least, for now.
Published at
2024-12-27 17:14:50Event JSON
{
"id": "0d7a75dbdb33b3e32ac86432ad63abebdc12360a1705092e129f8e697d07e1ab",
"pubkey": "7814eb61d529a8c09a01a90fc8704f91b555b14364d260929570c18832dc23b0",
"created_at": 1735319690,
"kind": 1,
"tags": [
[
"proxy",
"https://snac.bsd.cafe/teajaygrey/p/1735319690.079195",
"activitypub"
]
],
"content": "Thanks to neverpanic, my PR to update MacPorts' signify has been merged!\n\nBut now I'm listed as a maintainer and repology.org has this as a ding against me because it tracks signify version numbers from some different downstream aimed at Linux.\n\nThere is no signify-portable branch and thus no authoritative signify version.\n\nMacPorts' is basically updated from OpenBSD's sources from December 2024 now.\n\nHow to fix this?\n\nSubmit a PR to repology?\n\nStart a signify-portable project? That seems like a nightmare I don't want to tackle.\n\nIgnore it? I'm leaning towards ignoring.\n\nAt least, for now.\n",
"sig": "9f53abc9eeb208e4ad279e1bc3f0f3ebccc0a99bdaeb07a760c9dea816bb1be62e394a5692b6d2e8bef4e36090fbb21bf6852fad10bc0a58d01a940eff752653"
}