Hi Werner I'd say it's a JOSM *feature*, not a defect. JOSM correctly detects that the server wasn't able to delete a relation because it was still in use by some other relation.
> Simple workaround: > Remove 73724 first and 73723 with a second changeset. That's how to do it. It isn't a workaround. Regards Karl Am 13.02.2010 10:04, schrieb Werner Hoch: > Hi there, > > I'm not sure if this is a JOSM problem. > > I've tried to delete the relations 73723 and 73724. > 73723 is the only element of 73724. > http://www.openstreetmap.org/browse/relation/73724 > > When I try to upload the change, I get an error message > that 73723 cannot be deleted because it is an element of > 73724. > The complete message is (German): > ----- > Vorbedingung nicht erfüllt > Die Relation 73723 konnte nicht gelöscht werden. Sie wird immer > noch von Relation 73724 referenziert. Bitte laden Sie die Relation > 73724, entfernen Sie die Referenz auf Relation 73723 und laden Sie > erneut hoch. > ------ > > I think that the prerequirements are fullfiled if relation 73724 > is removed, too. > > Simple workaround: > Remove 73724 first and 73723 with a second changeset. > > I'm using JOSM version 2561. > > Regards > Werner > > _______________________________________________ > josm-dev mailing list > [email protected] > http://lists.openstreetmap.org/listinfo/josm-dev > > _______________________________________________ josm-dev mailing list [email protected] http://lists.openstreetmap.org/listinfo/josm-dev
