This indeed happened because PeterR has no account on Wikidata. This is a known shortcoming of the current repo update mechanisms.

The solution for this seems to be described in T143486, thus I'm not sure what value this ticket has over T143486.

In T143485#2580529, @hoo wrote:

The solution for this seems to be described in T143486, thus I'm not sure what value this ticket has over T143486.

This is mainly a (perceived) user problem report .. it may be resolved by the solution described in T143486 or by some other solution. It can serve as test case for a patch. The dependencies indicate how they relate.

Personally, I find it's an advantage if these two are split.
*Sometimes there are so many things discussed in one thread that some or all of the problems get buried, forgotten and reported over and over
*Sometimes the solution is mentioned on the side and thus no plan is made to implement implement it.

I guess I should have made a new ticket after the discussion T143742 instead of changing the header on T125768.

Obviously, if you prefer to have as much as possible in one ticket .. I can change my approach. What does Lydia think of it?

When a bug is reported I find it most useful to find the source of it and an action plan and then adapt the description and heading accordingly.

I think this works well when everything can be determined and resolved with a single action plan in a relatively short period of time.

Personally, I had some problems finding relevant issues and solutions in the threads of T87764 possibly as many are buried in questions I don't understand or explanations that seem peripheral to me.