3 ms·
Note that this code actually turns phase-updates ON. To turn them OFF: Update-Manager::Never-Include-Phased-Updates; APT::Get::Never-Include-Phased-Updates
by PBondurant 4y ago
Note that this code actually turns phase-updates ON. To turn them OFF:
Update-Manager::Never-Include-Phased-Updates;
APT::Get::Never-Include-Phased-Updates: True;
- proactivesvcs 4y agoPerhaps the advice is bad because this doesn't appear to be mentioned in the documentation.
- soneil 4y agoAs I understand it, either 'always' or 'never' actually solve OP's problem. (edit: was both/and - both sounds like a bad idea.) "always include" effectively puts you in phase 0 - if an update is being phased, you're an eager beaver. "never include" effectively puts you in phase 100 - if an update is being phased, you'll wait until the phasing is complete. AIUI OP's problem isn't that he wants these updates on day 0, it's that he wants his environments to be consistent with each other, which either of these options would provide.