[Touch-packages] [Bug 1988819] Re: When apt keeps back packages due to phased updates, it should list them separately

@juliank Thanks for the tip about machine id. May I also ask, for repeatability, is there an official/supported way to run (unit) tests on the upgrade logic alone, say, by feeding `/var/lib/dpkg/status`, index files and maybe some environment variables/APT::* preferences to `apt- get` and then runn

[Touch-packages] [Bug 1988819] Re: When apt keeps back packages due to phased updates, it should list them separately

To add a data point and save others from preventable headaches, I encountered a related bug and reported it here: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/2017399 If anyone cares, here are my two cents regarding phased updates: https://github.com/xwcal/ubuntu-apt-bug#a-short-critique-of

[Touch-packages] [Bug 2017399] Re: `apt-get -s upgrade` calculates the upgrade differently depending on whether InRelease files are present in the cache

@juliank Thanks for confirming my guess regarding Phased-Update- Percentage. However, I don't think I have gained any better understanding of the role Release/InRelease files play in the upgrade calculation (I assume by "Archive:" you meant "Suite:"?). Doesn't the file naming scheme (managed by ap

[Touch-packages] [Bug 2017399] [NEW] `apt-get -s upgrade` calculates the upgrade differently depending on whether InRelease files are present in the cache

Public bug reported: # Background I have an in-house package manager that downloads packages from mirrors in parallel and maintains a versioned local repo. It has worked well since 2019. However, during a recent migration from 18.04 to 22.04 I encountered a strange bug: the install step keeps f