[Patch] wrong order of deleted relations at upload

[malenki]

Problem
JOSM doesn't create a sensible order at upload of relations to be deleted.

How users are affected
When cleaning up relations by deleting nested relations.
Example: deleting all three: a relation C that contains a relation B that contains a relation A
JOSM does order arrange the order of to-be-deleted relations by alphabet.
This is a problem since now JOSM uploads deleted relation A first but assumes/gets told by the server relation B and C are still existing so returns with
<Precondition failed: The relation $number_of_A is used in relation $number_of_B.>

[simon04]

In my opinion, the OSM API (project at ​https://github.com/openstreetmap/openstreetmap-website) should take care of this situation.

[malenki]

Reported it there - and it got "solved" quite speedily: ​https://github.com/openstreetmap/openstreetmap-website/issues/688

[simon04]

We fix JOSM's upload ordering – patch attached.

[Don-vip]

Is it not a duplicate of #7157 ? And maybe we should address #6373 as well at the same time.

[simon04]

Ticket #7157 has been marked as a duplicate of this ticket.

[simon04]

In 6776/josm:

fix #9624 - Create a sensible upload order of relations to be deleted

This fixes "Precondition failed: The relation X is used in relation Y" when X and Y are to be deleted

[Don-vip]

Ticket #8139 has been marked as a duplicate of this ticket.