Comment 1 for bug 918754

There is a second manifestation for this bug. I took ownership the old team and manually added branch policies the new team. I Merge thought it completed, but the DB reported an Integrity error. Looks like it is impossible to merge a team with another team if they both have visibility policies for a project. OOPS-190f295665ef293127cdd356371fc0c4

  IntegrityError: duplicate key value violates unique constraint "branchvisibilitypolicy__unq"

    Traceback (most recent call last):
  Module lp.services.job.runner, line 267, in runJobHandleError
    self.runJob(job)
  Module lp.services.job.runner, line 225, in runJob
    job.run()
  Module lp.registry.model.persontransferjob, line 437, in run
    reviewer=self.reviewer)
  Module lp.registry.model.person, line 4067, in merge
    return self._merge(from_person, to_person, reviewer)
  Module lp.registry.model.person, line 4259, in _merge
    src_tab, src_col, to_person.id, src_col, from_person.id))
  Module lp.services.database.sqlbase, line 619, in execute
    self._result = self._connection.execute(query)
  Module storm.databases.postgres, line 261, in execute
    return Connection.execute(self, statement, params, noresult)
  Module storm.database, line 238, in execute
    raw_cursor = self.raw_execute(statement, params)
  Module storm.databases.postgres, line 271, in raw_execute
    return Connection.raw_execute(self, statement, params)
  Module storm.database, line 322, in raw_execute
    self._check_disconnect(raw_cursor.execute, *args)
  Module storm.database, line 371, in _check_disconnect
    return function(*args, **kwargs)
IntegrityError: duplicate key value violates unique constraint "branchvisibilitypolicy__unq"