Modify ↓
Opened 3 years ago
Closed 3 years ago
#4476 closed defect (fixed)
Deleted nodes cause an conflict if the data is redownloaded
| Reported by: | anonymous | Owned by: | team |
|---|---|---|---|
| Priority: | critical | Component: | Core |
| Version: | latest | Keywords: | |
| Cc: |
Description
r2933 introduced a bug that when you have deleted a node from a way, and then redownload the area, the deleted node causes a conflict, although no-one had edited the node.
If the user has deleted a node, and it is redownloaded with the same version, there should not be a conflict, and the node should remain deleted.
Only if the version differs, there should be a conflict, as then someone else has edited it since it was deleted locally.
Attachments (0)
Change History (2)
comment:1 Changed 3 years ago by mjulius
comment:2 Changed 3 years ago by mjulius
- Resolution set to fixed
- Status changed from new to closed
fixed in r2935
Note: See
TracTickets for help on using
tickets.



No, the whole point of the change was that JOSM detects a conflict if a node that has been deleted locally is still used by a way downloaded from the server.
But, it should not do this when that way is already part of the local dataset.