We just had such a case in our data center on precise. That has a backported postgresql-common 154 installed, postgresql-9.1 from precise, and a backported p-9.3. Upgrading 9.3 after 9.1 works ok, as p-common's _link_manpages() takes care of the transition in that direction. But upgrading 9.1 after 9.3 fails because precise's postgresql-9.1 still ships pg_basebackup.1.gz in the server package and alternative group. But at that time -9.3 will already have transitioned it to the psql.1.gz alternative group.
We just had such a case in our data center on precise. That has a backported postgresql-common 154 installed, postgresql-9.1 from precise, and a backported p-9.3. Upgrading 9.3 after 9.1 works ok, as p-common's _link_manpages() takes care of the transition in that direction. But upgrading 9.1 after 9.3 fails because precise's postgresql-9.1 still ships pg_basebackup.1.gz in the server package and alternative group. But at that time -9.3 will already have transitioned it to the psql.1.gz alternative group.
A quick workaround is
sudo update-alternatives --remove psql.1.gz /usr/share/ postgresql/ 9.3/man/ man1/psql. 1.gz
sudo apt-get -f install
This will hold until you upgrade 9.3 and then 9.1 again, at which point the same workaround will apply again.