I have an unlocked package with custom object
Person__c and field
Account__c as a lookup on the account.
I tried installing this package in an org where
Person__c object is already available with
Account__c field it failed with the following error
There is already a Child Relationship named Persons on Account.
Person__c.Account__c: There is already a Child Relationship named Persons on Account.
Is it the expected behavior or it is a platform bug?
I believed unlocked package could be used as a replacement of changeset or Ant-Migration tool as mentioned here : https://sfdc-db-gmail.github.io/unlocked-packages/faq-unlocked-pkgs.html