Comment 14 for bug 1981672

It's documented in the discourse thread (Discourse is where Ubuntu documentation lives) You have not provided evidence that it does not work for you. APT itself has test cases that proof that *it does* work.

Note that newer apt versions (2.4.6, 2.5.1) will install more phased updates

- as phasing only applies to upgrades, not to new installs, so if you `apt install phased`, you'll get the phased version, regardless of your setting,
- or if there is a phased=1 security update and a phased=2 update, you'll get phased=2 even if it's phasing at 0.

You can restore previous behavior by setting APT::Get::Phase-Policy to true; but note that this can cause the `apt install` command to fail to install packages, see bug 1979244 for more details.

All other phased updates should show as being kept back in the upgrade output.

If you want to move this further you'll have to provide one of the following:

- A reproducer
- A log that shows a phased update being installed that should not be, including the command that installed the update and any debug output

Either must be accompanied by a tarball containing:

- /etc/apt
- /var/lib/dpkg/status
- /var/lib/apt

You also want to check yourself that

- `apt-config dump` shows `APT::Get::Never-Include-Phased-Updates "false";`
- `apt-config dump` shows no entry, or a negative one, for `APT::Get::Always-Include-Phased-Updates`

If you use update-manager it's not entirely clear how this interacts with the new phasing code in 2.4.6, so you might also/instead have to set

`Update-Manager::Never-Include-Phased-Updates "false";`

As documented in the discourse post.