Nicola: do you know if that branch was pushed with 1.14rc2 (and never any older version)? If so this is expected behaviour (unfortunately), not another case of this bug.
Even with 1.14rc2 on both the client and the server you will still get this error from stacked branches pushed with older bzr versions, because those versions can push stacked branches that are incomplete. i.e. the "AbsentContentFactory" error is the symptom, not the bug. The bug occurs silently during "push", but is only noticed later when doing a pull/merge/etc.
(We should improve the server to give a better error to the client in this scenario, because presumably old clients will keep creating stacked branches for a while to come, but we should track that in a separate bug.)
Nicola: do you know if that branch was pushed with 1.14rc2 (and never any older version)? If so this is expected behaviour (unfortunately), not another case of this bug.
Even with 1.14rc2 on both the client and the server you will still get this error from stacked branches pushed with older bzr versions, because those versions can push stacked branches that are incomplete. i.e. the "AbsentContentF actory" error is the symptom, not the bug. The bug occurs silently during "push", but is only noticed later when doing a pull/merge/etc.
(We should improve the server to give a better error to the client in this scenario, because presumably old clients will keep creating stacked branches for a while to come, but we should track that in a separate bug.)