Yes, I noticed the extra “…” which was clearly wrong… but I have no idea how they get in there. As said, I’ve got the error from an automatic update attempt.
Overnight, a new automatic update attempt was successful. I don’t know if someone has solved the problem in the meantime or if there is (still) some strange bug somewhere, which causes the problem to occur “randomly”.