Comment 35 for bug 2020604

OK just a question about pinning since we would prefer to minimize changes to user systems. When we follow the instructions from Steve's message on:

 https://wiki.ubuntu.com/Testing/EnableProposed

which sets the pin priority for proposed to 400, the page says to run a simulated apt upgrade to verify that no packages are scheduled for upgrade. However when we try that we see 11 upgrade-able packages.

We can get that number to 0 if we set the pin priority to something less than that of /var/lib/dpkg/status, i.e., to something less than 100. But is that correct?

If we comment out all the pin restrictions we see 44 proposed packages scheduled for upgrade. Is that because some of the proposed packages aren't controlled by /var/lib/dpkg/status?