phases: fix advanceboundary behavior when targetphase !=0
Changeset was properly removed from upper phase but was not explicitly added to
target phase. If advanced changesets had not pwasnt in target phase they was
considered public (0-phase).
$ "$TESTDIR/hghave" unix-permissions || exit 80
$ hg init a
$ echo a > a/a
$ hg -R a ci -A -m a
adding a
$ hg clone a b
updating to branch default
1 files updated, 0 files merged, 0 files removed, 0 files unresolved
$ echo b > b/b
$ hg -R b ci -A -m b
adding b
$ chmod 100 a/.hg/store
$ hg -R b push a
pushing to a
abort: could not lock repository a: Permission denied
[255]
$ chmod 700 a/.hg/store