the user want to have the one that's compatible with all the others he has. for it to be the same version.
if there's any packages that has multiple subpackages, and it's backported, and one of it's subpackages will be added as a new dependency with updates, then you'd have a problem.
this is exactly why we need to have stricter requires in any case. so that this would not happen. if it doesn't work for backported version, it should say so, or backported version should say so.
the user want to have the one that's compatible with all the others he has. for it to be the same version.
if there's any packages that has multiple subpackages, and it's backported, and one of it's subpackages will be added as a new dependency with updates, then you'd have a problem.
this is exactly why we need to have stricter requires in any case. so that this would not happen. if it doesn't work for backported version, it should say so, or backported version should say so.