Ahh.. That's what it checks. No need. My problem then is I haven't been using do-release-upgrade to do updates for a long time.
I have a ton of complicated dependencies that always seem to fail on upgrade, so I've been manually replacing the codename in /etc/apt/sources.list for each upgrade.
So this isn't strictly a duplicate, but it might be for all intents and purposes though if a decision is made to use a different means of obtaining this information. I can understand if this is a wontfix though.
If this is to be corrected, the obvious way that occurs to me though is to pull the files specifying the OS version information (i.e. /etc/debian_version /etc/lsb-release /usr/lib/os-release) into their own package and change it once per release and use the install date of that package.
Ahh.. That's what it checks. No need. My problem then is I haven't been using do-release-upgrade to do updates for a long time.
I have a ton of complicated dependencies that always seem to fail on upgrade, so I've been manually replacing the codename in /etc/apt/ sources. list for each upgrade.
So this isn't strictly a duplicate, but it might be for all intents and purposes though if a decision is made to use a different means of obtaining this information. I can understand if this is a wontfix though.
If this is to be corrected, the obvious way that occurs to me though is to pull the files specifying the OS version information (i.e. /etc/debian_version /etc/lsb-release /usr/lib/ os-release) into their own package and change it once per release and use the install date of that package.