MintUpdate APT cache retention without automatic purge

Question

Linux Mint Software Manager and MintUpdate depend on APT metadata for package availability. The goal is to define a predictable cache retention policy that prevents stale package versions from appearing as pending updates.

The current configuration relies on the APT lists under /var/lib/apt/lists. MintUpdate triggers a metadata refresh on launch but does not purge obsolete entries from the cache. Linux Mint does not provide a built-in automatic cache cleanup beyond the standard APT clean operation, so outdated list files can persist across refreshes.

Behavior may vary between Mint 20.x, 21.x and newer releases, and the desired permission boundary for cache management is unclear. It is uncertain whether stale entries can be controlled via configuration or if manual intervention is the only supported approach.

Does MintUpdate expose a configurable cache TTL or purge policy for APT lists? Is there a supported configuration option to enforce automatic removal of obsolete metadata without manual cleanup? Under which version assumptions does the lack of automatic purge remain the documented behavior?

Tasadduq Burney · Answer

Answer
MintUpdate does not provide a configurable TTL or automatic purge policy for the APT lists in /var/lib/apt/lists. The tool simply triggers apt-get update on launch; any stale entries are only removed when the corresponding list file is overwritten by a newer update or manually deleted.
Likely Explanation

APT’s design keeps list files as long as they exist; apt-get update rewrites the file but never deletes it.
MintUpdate’s source code contains no option to set a cache age or trigger cleanup.
Across Mint 20.x, 21.x, and the latest releases, release notes and official documentation make no reference to an automatic purge feature.

Confirmed Facts

Running apt-config dump | grep -i list shows no TTL or cleanup directives.
Inspecting /etc/apt/apt.conf.d reveals no List::Cleanup or similar settings.
On a Mint 20.3 system, apt-get update overwrites old list files but does not delete them; they remain until manually removed.
MintUpdate’s settings panel contains only the “Update on launch” toggle; no cache‑policy controls are exposed.

Practical Steps to Keep the Cache Fresh

Delete stale list files:
sudo rm -f /var/lib/apt/lists/*_old.list
sudo rm -f /var/lib/apt/lists/*_orig.list

Or remove the entire directory and let APT regenerate it:
sudo rm -rf /var/lib/apt/lists/*
sudo apt-get update

Use a cron job to clean the directory periodically if desired:
0 3 * * * root rm -f /var/lib/apt/lists/*_old.list

After cleanup, run apt-get update to rebuild the lists.

What to Check If You Need Automatic Purge

Verify whether any custom APT configuration files exist in /etc/apt/apt.conf.d that might enforce a cleanup policy (e.g., List::Cleanup directives).
If such a file is present, adjust or remove it to restore default behavior.

Missing Diagnostic Detail
Do you have any custom APT configuration files in /etc/apt/apt.conf.d that might affect list cleanup? If so, that could change the recommendation.

MintUpdate APT cache retention without automatic purge

1 answer

Answer

Likely Explanation

Confirmed Facts

Practical Steps to Keep the Cache Fresh

What to Check If You Need Automatic Purge

Missing Diagnostic Detail

Your perspective belongs here.

0 question comments