aptitude and aptitude-robot are not supported components. They are packages provided by the community as part of the universe repository.
While the implementation of phased updates in apt versions prior to 2.4.6 would work there, the current version does not. Implementing phased updates in aptitude for the current algorithm is out of scope, as aptitude does not use the apt resolver where the keep-back is implemented, and a generic API to handle phasing is not yet exposed in apt.
Switching to the policy based pinning as documented before should make aptitude respect pinning more, however, aptitude is not a reliable tool that respects your choices like that (its solver will happily suggest solutions violating your wishes; it also generally is too happy to remove packages), so you do not want to use it in an automated setting.
I recall/see again a mention of aptitude:
aptitude and aptitude-robot are not supported components. They are packages provided by the community as part of the universe repository.
While the implementation of phased updates in apt versions prior to 2.4.6 would work there, the current version does not. Implementing phased updates in aptitude for the current algorithm is out of scope, as aptitude does not use the apt resolver where the keep-back is implemented, and a generic API to handle phasing is not yet exposed in apt.
Switching to the policy based pinning as documented before should make aptitude respect pinning more, however, aptitude is not a reliable tool that respects your choices like that (its solver will happily suggest solutions violating your wishes; it also generally is too happy to remove packages), so you do not want to use it in an automated setting.