Tested in a clean focal chroot. The dependency resolution works as expected, allowing the package to be installed without pulling in all of GNOME, but only if the "universe" repository component is enabled. If I have only "main" enabled, then dependency resolution fails with the following:
# apt install screen-resolution-extra
Reading package lists... Done
Building dependency tree... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
screen-resolution-extra : Depends: policykit-1-gnome but it is not installable or gnome-shell but it is not going to be installed or polkit-1-auth-agent
E: Unable to correct problems, you have held broken packages.
I'm not sure if there's a reason apt doesn't just fall back to selecting gnome-shell when policykit-1-gnome isn't available, due to being in a disabled repository. Perhaps this might be expected behavior, but since there is a change in behavior compared to how the dependencies were previously set up, I'm not sure if the change is appropriate for an SRU. At least for default desktop installations, I imagine the difference wouldn't be noticeable, since gnome-shell would already be installed.
Tested in a clean focal chroot. The dependency resolution works as expected, allowing the package to be installed without pulling in all of GNOME, but only if the "universe" repository component is enabled. If I have only "main" enabled, then dependency resolution fails with the following:
# apt install screen- resolution- extra
Reading package lists... Done
Building dependency tree... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies: resolution- extra : Depends: policykit-1-gnome but it is not installable or
gnome- shell but it is not going to be installed or
polkit- 1-auth- agent
screen-
E: Unable to correct problems, you have held broken packages.
I'm not sure if there's a reason apt doesn't just fall back to selecting gnome-shell when policykit-1-gnome isn't available, due to being in a disabled repository. Perhaps this might be expected behavior, but since there is a change in behavior compared to how the dependencies were previously set up, I'm not sure if the change is appropriate for an SRU. At least for default desktop installations, I imagine the difference wouldn't be noticeable, since gnome-shell would already be installed.