So my systems recently updated to rsync 3.4.3, and as soon as that happened my backup system - which does incremental backups using multiple --compare-dest= arguments - started to fail on anything but a full backup.
-
So my systems recently updated to rsync 3.4.3, and as soon as that happened my backup system - which does incremental backups using multiple --compare-dest= arguments - started to fail on anything but a full backup.
Revert to 3.4.1 and it works.
So I go look at the source in GitHub to see what might have changed, because there doesn't seem to be anything relevant in the changelog.
Since 3.4.1, 36 commits by "tridge and claude"
Oh for fuck's sakes.
-
So my systems recently updated to rsync 3.4.3, and as soon as that happened my backup system - which does incremental backups using multiple --compare-dest= arguments - started to fail on anything but a full backup.
Revert to 3.4.1 and it works.
So I go look at the source in GitHub to see what might have changed, because there doesn't seem to be anything relevant in the changelog.
Since 3.4.1, 36 commits by "tridge and claude"
Oh for fuck's sakes.
-
So my systems recently updated to rsync 3.4.3, and as soon as that happened my backup system - which does incremental backups using multiple --compare-dest= arguments - started to fail on anything but a full backup.
Revert to 3.4.1 and it works.
So I go look at the source in GitHub to see what might have changed, because there doesn't seem to be anything relevant in the changelog.
Since 3.4.1, 36 commits by "tridge and claude"
Oh for fuck's sakes.
@JeremiahFieldhaven
Oh damn it all. Tridge has fallen -
So my systems recently updated to rsync 3.4.3, and as soon as that happened my backup system - which does incremental backups using multiple --compare-dest= arguments - started to fail on anything but a full backup.
Revert to 3.4.1 and it works.
So I go look at the source in GitHub to see what might have changed, because there doesn't seem to be anything relevant in the changelog.
Since 3.4.1, 36 commits by "tridge and claude"
Oh for fuck's sakes.
@JeremiahFieldhaven Christ if it’s coming for rsync of all things software is clearly done
-
@JeremiahFieldhaven Christ if it’s coming for rsync of all things software is clearly done
@sinbad @JeremiahFieldhaven What an idiotic thing to do to a piece of software with a venerable past and whose key feature is its reliability. All these OSS maintainers just burning decades of trust over a perceived 10-ish % “efficiency gain” with snowballing amounts of evidence to the contrary, and a looming bubble implosion on the horizon.
-
So my systems recently updated to rsync 3.4.3, and as soon as that happened my backup system - which does incremental backups using multiple --compare-dest= arguments - started to fail on anything but a full backup.
Revert to 3.4.1 and it works.
So I go look at the source in GitHub to see what might have changed, because there doesn't seem to be anything relevant in the changelog.
Since 3.4.1, 36 commits by "tridge and claude"
Oh for fuck's sakes.
@JeremiahFieldhaven aw, goddamnit!
-
So my systems recently updated to rsync 3.4.3, and as soon as that happened my backup system - which does incremental backups using multiple --compare-dest= arguments - started to fail on anything but a full backup.
Revert to 3.4.1 and it works.
So I go look at the source in GitHub to see what might have changed, because there doesn't seem to be anything relevant in the changelog.
Since 3.4.1, 36 commits by "tridge and claude"
Oh for fuck's sakes.
@JeremiahFieldhaven Tridge is using AI? LOL, that's damn funny to be honest. Also I thought he only worked on core Samba code. Maybe he should only work on core Samba code.
-
So my systems recently updated to rsync 3.4.3, and as soon as that happened my backup system - which does incremental backups using multiple --compare-dest= arguments - started to fail on anything but a full backup.
Revert to 3.4.1 and it works.
So I go look at the source in GitHub to see what might have changed, because there doesn't seem to be anything relevant in the changelog.
Since 3.4.1, 36 commits by "tridge and claude"
Oh for fuck's sakes.
@JeremiahFieldhaven Well this has unlocked a new horror.
-
So my systems recently updated to rsync 3.4.3, and as soon as that happened my backup system - which does incremental backups using multiple --compare-dest= arguments - started to fail on anything but a full backup.
Revert to 3.4.1 and it works.
So I go look at the source in GitHub to see what might have changed, because there doesn't seem to be anything relevant in the changelog.
Since 3.4.1, 36 commits by "tridge and claude"
Oh for fuck's sakes.
@JeremiahFieldhaven Whoooaah whoa whoa. Actual Tridge would never really actually break something (in that way).
A tridgeposter…?
-
So my systems recently updated to rsync 3.4.3, and as soon as that happened my backup system - which does incremental backups using multiple --compare-dest= arguments - started to fail on anything but a full backup.
Revert to 3.4.1 and it works.
So I go look at the source in GitHub to see what might have changed, because there doesn't seem to be anything relevant in the changelog.
Since 3.4.1, 36 commits by "tridge and claude"
Oh for fuck's sakes.
@JeremiahFieldhaven no! Not rsync! How many of my beloved cli programs must fall to ai slop development?!?!
-
So my systems recently updated to rsync 3.4.3, and as soon as that happened my backup system - which does incremental backups using multiple --compare-dest= arguments - started to fail on anything but a full backup.
Revert to 3.4.1 and it works.
So I go look at the source in GitHub to see what might have changed, because there doesn't seem to be anything relevant in the changelog.
Since 3.4.1, 36 commits by "tridge and claude"
Oh for fuck's sakes.
@JeremiahFieldhaven Do people not even read or test the output of these agents when using them? I've used them as a crutch, but never as a replacement, so I can at least understand what the output is before I push it to someone to review. It's more of a finding the spoons and the hours of typing away to finish something I want done so I can use it. I wish the same could be said of all these people inflicting unvetted changes on untold thousands or even millions of users.
-
@sinbad @JeremiahFieldhaven What an idiotic thing to do to a piece of software with a venerable past and whose key feature is its reliability. All these OSS maintainers just burning decades of trust over a perceived 10-ish % “efficiency gain” with snowballing amounts of evidence to the contrary, and a looming bubble implosion on the horizon.
@distractal @sinbad @JeremiahFieldhaven Though I'm not sure how much the 10-ish % "efficiency gain" is when I can ask an agent to solve a problem for me in 5-15 minutes, or I can spend literally hours poring over a code base to understand what I need to do to fix it myself.
-
M monkee@other.li shared this topic
