Comment 2 for bug 1378245

This is actually reverting back to the previous behavior we had which had the potential of "upgrading" packages out of silo.

Sure you get the dependencies, but the added load of other packages can come in too.

Using main only is not an option as we also have dependencies in universe, the fact that it worked without upgrading unwanted packages might of been just a coincidence with the time of testing (e.g.; just after a new image came out of the oven so all packages were up to date)

The best solution here is to have people state they have new deps and taking care of them prior to running the tool. This is not ideal and I can see this working without any intervention from the user and without disabling any sources if instead of running dist-upgrade you do the following:

- iterate over each binary package in the silo
- if it's not part of the current install list, discard; else add to the "install_list"
- look at the dependencies, add to the "install_list"
- apt install "install_list"