Comment 4 for bug 1446552

@BrianMurray: Not anymore, unfortunately.

How I originally reproduced it was:

- Create a testing package (doesn't have to really contain anything) that just installs 1 file into /usr/share/testpackage/, and have it depend on some packages.
- Put that package on a private repository (which is also configured for APT and unattended-upgrades)
- Install the package using `apt-get install testingpackage`
- Update the package as follows: 1. Add a dependency which is not yet installed on your machine (and is also not in the security-repository). Up the version number, and add it to the private repository.
- Run `unattended-upgrade --debug --apt-debug 2>&1 | tee output.txt`.
- Verify the package was not updated (missing dependency).
- Host the dependency on your private APT server as well (1-1 copy).
- Run `unattended-upgrade --debug --apt-debug 2>&1 | tee output.txt`.
- Verify the package was not updated (missing dependency).
- Re-build the dependency with a higher version number, and add it to your private APT repository.
- Run `unattended-upgrade --debug --apt-debug 2>&1 | tee output.txt`.
- Verify the package was now upgraded.

With the proposed patch, the upgrade would already succeed after hosting the exact copy on the private APT repository.

If needed I could probably figure out how to reproduce this again, but it would take me quite some time, as I'd have to set-up everything again. Hopefully my description of the case is enough for you to reproduce this.

Let me know if you need my help in reproducing.