I tried to go too far with updating MacPorts' signify to sync it with upstream's 1.64 release (e.g. https://cvsweb.openbsd.org/src/usr.bin/signify?sort=File) there is some breakage and stupid me pushed to the wrong branch (I created a new branch locally, yet apparently forgot to check it out as I sometimes do, being an error prone human, so the push with the breakage went to the master branch, which I then reverted *sigh* all up there on GitHub for the world to see).
Meanwhile, there have been some changes upstream which aren't simply resolved by removing the sha2.c file from the Makefile; so it's going to take more effort to rectify and my second shift for the day is over in fewer than 30 minutes, so I don't think that is going to happen!
Could have been worse? At least I didn't tag a new release from the botched push? Still embarrassing to have things which should have stayed as a local screw up, get synced to a publicly viewable repo, particularly with security critical code.
This workflow, I sincerely despise. I doubt I will ever be OK with GitHub. Git is bad enough and in this particular instance as I am also working with CVS it's just kind of staggering when I think back to the decades and decades of coding I have done and how many problems are tripping over the version control tools, instead of actually coding.
ティージェーグレェ
npub1k3…zkcx3
2026-09-05 22:37:52 UTC
Author Public Key
npub1k3cx6w0vu5tshrrkfl3ftrd0826e779zgdqy0u8wglylhcy22pks9zkcx3Seen on
wss://relay.momostr.pinkPublished at
2026-09-05 22:37:52 UTCEvent JSON
{
"id": "78bf7eb55af1955c99bc87f281a1d369dfd42ccba41cacc41872766e7bf59322",
"pubkey": "b4706d39ece5170b8c764fe2958daf3ab59f78a2434047f0ee47c9fbe08a506d",
"created_at": 1788647872,
"kind": 1,
"tags": [
[
"proxy",
"https://snac.bsd.cafe/teajaygrey/p/1788647872.321164",
"web"
],
[
"proxy",
"https://snac.bsd.cafe/teajaygrey/p/1788647872.321164",
"activitypub"
],
[
"L",
"pink.momostr"
],
[
"l",
"pink.momostr.activitypub:https://snac.bsd.cafe/teajaygrey/p/1788647872.321164",
"pink.momostr"
],
[
"-"
]
],
"content": "I tried to go too far with updating MacPorts' signify to sync it with upstream's 1.64 release (e.g. https://cvsweb.openbsd.org/src/usr.bin/signify?sort=File) there is some breakage and stupid me pushed to the wrong branch (I created a new branch locally, yet apparently forgot to check it out as I sometimes do, being an error prone human, so the push with the breakage went to the master branch, which I then reverted *sigh* all up there on GitHub for the world to see).\n\nMeanwhile, there have been some changes upstream which aren't simply resolved by removing the sha2.c file from the Makefile; so it's going to take more effort to rectify and my second shift for the day is over in fewer than 30 minutes, so I don't think that is going to happen!\n\nCould have been worse? At least I didn't tag a new release from the botched push? Still embarrassing to have things which should have stayed as a local screw up, get synced to a publicly viewable repo, particularly with security critical code.\n\nThis workflow, I sincerely despise. I doubt I will ever be OK with GitHub. Git is bad enough and in this particular instance as I am also working with CVS it's just kind of staggering when I think back to the decades and decades of coding I have done and how many problems are tripping over the version control tools, instead of actually coding.",
"sig": "340917135d0292f48b61fcf316001103aa7f44fdc9763408becf530b417bb1df2550d3e121aba4d65c1010b09b39608e512af493ef574a099c6879efa3c136fe"
}