Resolving node conflicts as "deleted" is broken

[bilbo]

I encountered a conflict - I deleted some nodes that were referenced by a way outside of download region. When uploading I got conflict (my version was deleted, their was not deleted). I resoved conflict for all nodes to be "deleted" (so these nodes got deleted also from the other way that I previously have not known of) - however, the way (which now have the conflicting nodes removed) was not marked for upload, so after solving all the conflicts, I got them again.

When marking node as "deleted" in conflict, it must be removed from all known ways also.

[bilbo]

Also, if you try running "simplify" on the way outside download region, you get some exceptions saying you have deleted referenced node ...

[skyper]

Still an issue

Only way to upload is to download all parent ways.

[Hb---]

Replying to skyper:

Only way to upload is to download all parent ways.

I consider this as positive feature in JOSM. Otherwise the conflict resolution dialog would be able to destroy an undetermined amount of data on the OSM server. So this ticket should be wontfix.

[GerdP]

It's the OSM API that doesn't allow to delete a node which is referenced in parents (ways or relations). So, if JOSM doesn't know about the parents it will always generate changesets which will be rejected by the API. Only when you download the parents it will generate the necessary update/delete statements for the parent objects.
I think tested version of JOSM (r17428 is current) will download the parents unless you don't want that. Not sure how it behaved 10 years ago.

[Don-vip]

Ticket not clear with the 10-year timelapse. Please open a new one with a recent version of JOSM is a related problem is not already tracked in another ticket.

[skyper]

There was a problem in forgetting to update the additional ways which where downloaded by the sync but I just rechecked and everything works fine mean-while.