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.
@JeremiahFieldhaven the amount of crap that’s broken after 3.4.1 is just wow
https://github.com/RsyncProject/rsync/issues -
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 i had to review/rewrite some AI written code the other day. (That i was handed)
The problem it was solving was a well known one, and it was only solving the smallest subset of it.
The code could compile and run, but:
- because i have some domain knowledge i could see that the output was not correct
- it's sync feature was not satisfactory, at all
- the code was some of the worst I have seen in a long, long time things were split in ways that made absolutely no sense -
@JeremiahFieldhaven i had to review/rewrite some AI written code the other day. (That i was handed)
The problem it was solving was a well known one, and it was only solving the smallest subset of it.
The code could compile and run, but:
- because i have some domain knowledge i could see that the output was not correct
- it's sync feature was not satisfactory, at all
- the code was some of the worst I have seen in a long, long time things were split in ways that made absolutely no sense@JeremiahFieldhaven I don't understand how anyone trusts the output of these things.
Yes, you can ask for small examples of things, of you are too lazy to open man pages, etc.
But putting any trust in the code these things spew out without thoroughly reading and understanding every line is incomprehensible to me. And when i do this, i tend to find I'd have been much better off just sitting it myself.
-
@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.
@chris Learning is forever but a Claude Code subscription bills monthly.
-
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 I feel like being lazy to actually go through updates often on my arch install has been paying off lately
-
@JeremiahFieldhaven I don't understand how anyone trusts the output of these things.
Yes, you can ask for small examples of things, of you are too lazy to open man pages, etc.
But putting any trust in the code these things spew out without thoroughly reading and understanding every line is incomprehensible to me. And when i do this, i tend to find I'd have been much better off just sitting it myself.
Well it's simple, you just don't look at it and pretend because you got AN output it is correct cause "the AI" told you so.
People see "AI" as an authority figure and therefore assume it is correct without checking...
-
@JeremiahFieldhaven the amount of crap that’s broken after 3.4.1 is just wow
https://github.com/RsyncProject/rsync/issues@byte @JeremiahFieldhaven Did anyone fork it yet?
-
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 ffs. This is exactly why I've been worried about updating this laptop!
-
@JeremiahFieldhaven Some of these commits are repairing defective generated code with other generated code.....
🫣@Ferdi_Scholten @JeremiahFieldhaven
seriously? are we at that stage now?
-
@glassresistor @distractal @sinbad @JeremiahFieldhaven I must not know what any of that means, or I wouldn't have said it. You remind me of my brother, who compared my computer use with his gambling addiction. I'm sure those things are the same thing.
@chris Just like I'm sure that saying cognitive surrender is not something a person can "fight" and saying that fighting depression with a chatbot is likely to make the depression worse in the long term is the same as comparing using a computer to gambling.
Jesus Christ, get over yourself.
-
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 cc @gryphonmyers for the list
-
@glassresistor @distractal @sinbad @JeremiahFieldhaven I must not know what any of that means, or I wouldn't have said it. You remind me of my brother, who compared my computer use with his gambling addiction. I'm sure those things are the same thing.
@chris @glassresistor @distractal @sinbad @JeremiahFieldhaven yeah, they literally are the same thing. The "hooked" loop. https://pivot-to-ai.com/2025/06/05/generative-ai-runs-on-gambling-addiction-just-one-more-prompt-bro/
-
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.
-
@byte @JeremiahFieldhaven Did anyone fork it yet?
-
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 The alternative from stapelberg seems reasonable https://michael.stapelberg.ch/posts/2026-05-24-minimal-memory-safe-go-rsync-vulns/
-
@JeremiahFieldhaven Christ if it’s coming for rsync of all things software is clearly done
@sinbad @JeremiahFieldhaven
It's in `curl` also, see https://codeberg.org/small-hack/open-slopware#networking. Not that I fully agree with the sentiment of that list, but it is useful to keep track of such things -
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 I've seen the post on linkedin announcing a few rsync fixes, which didn't mention using Claude. Devs are sometimes very disappointing.
-
@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.
@me @JeremiahFieldhaven he's the original author of rsync so I guess he still has some things to say about its development. Sad to see this tbh.
-
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 You might want to check openrsync:
https://www.freshports.org/net/openrsync -
Well it's simple, you just don't look at it and pretend because you got AN output it is correct cause "the AI" told you so.
People see "AI" as an authority figure and therefore assume it is correct without checking...
@agowa338 @JeremiahFieldhaven one of the first, and to this day, best, analogies I've ever heard of asking an LLM something is that people pray to it to solve whatever issue they are having
