Ever had one of those moments where Linux tells you:
“Everything is up to date.”
…and you sit there thinking:
“Then why is Google Chrome still yelling at me to update?”
Yeah. Same.
Welcome to one of those quiet little Linux quirks that doesn’t get talked about much — but once you see it, you can’t unsee it.
Let’s break it down.
This comes down to the difference between apt upgrade vs –with-new-pkgs, a detail most Linux users never realize.
🔍 The Problem
Why apt upgrade says everything is updated (but it isn’t)
You run your usual update:
sudo apt update && sudo apt upgrade
Everything completes successfully. No errors. No warnings.
System is happy. Life is good.
Then you open Chrome (or some other app), and it says:
“Update available”
Now you’re thinking:
- Did something fail?
- Did apt miss something?
- Is Linux lying to me?
Short answer:
👉 Linux didn’t lie. It just didn’t do everything.
🧠 The Reason (Simple Explanation)
What apt upgrade actually does (and why it skips updates)
The key is this command:
apt upgrade
This command is intentionally conservative.
It will:
- Upgrade existing packages
- NOT install new dependencies
- NOT remove anything
In other words:
It updates what it can… without changing the system too much.
That’s great for stability.
But here’s the catch:
👉 Some updates require new dependencies.
When that happens, apt upgrade simply says:
“Nope. Not touching that.”
…and skips the update entirely.
⚖️ The Difference
apt upgrade vs –with-new-pkgs (what Linux Mint does differently)
Now here’s where things get interesting.
Linux Mint’s Update Manager doesn’t just run apt upgrade.
It effectively runs:
apt upgrade --with-new-pkgs
That one small addition:
--with-new-pkgs
changes everything.
Now APT is allowed to:
- Install new dependencies
- Complete updates that were previously skipped
That’s why:
👉 Mint updates Chrome… while your terminal doesn’t.
Same system. Same repos. Different behavior.
🔧 The Fix
If you want your terminal to behave like Linux Mint’s Update Manager, run this:
sudo apt upgrade --with-new-pkgs
That’s it.
No magic. No reinstalling. No voodoo.
Just one extra flag.
🍖 Real Talk (Bytes, Bread, Barbecue Style)
Think of it like this:
apt upgrade= “I’ll reheat what’s already on the plate.”--with-new-pkgs= “Let me grab a few extra ingredients and cook it right.”
Sometimes you don’t need extra ingredients.
Sometimes… you do.
And Chrome? Chrome always wants extra ingredients.
🚀 The RepoRover Solution
This exact behavior is why I added something new to RepoRover.
(Download it here! bytesbreadbbq.com/reporover)
👉 APT Update Modes (new in v1.3.0)
You now get two options:
🛡️ Safe Mode
- Runs:
apt upgrade - Conservative
- No new dependencies
- Good for quick, low-risk updates
🚀 Full Mode
- Runs:
apt upgrade --with-new-pkgs - Allows dependency changes
- Matches Linux Mint Update Manager behavior
- Updates things that Safe Mode might skip
🧠 When should you use each?
- Use Safe Mode when:
- You want minimal system changes
- You’re doing routine updates
- Use Full Mode when:
- Something didn’t update (hello Chrome 👋)
- You want everything fully up to date
- You want Mint-like behavior
🧩 Conclusion
Linux didn’t fail.
APT didn’t break.
Nothing is wrong.
👉 It was just being cautious.
Once you understand the difference, everything makes sense:
- Terminal = safe by default
- Mint Update Manager = slightly more aggressive
- RepoRover = gives you the choice
And honestly?
Choice is the whole point of Linux. You should be able to choose apt upgrade vs with-new-pkgs.
❓ FAQ
Why does apt upgrade not update everything?
Because it avoids installing new dependencies, so some updates are skipped.
What does apt upgrade –with-new-pkgs do?
It allows APT to install new dependencies required for updates.
Is apt upgrade safe?
Yes, it is the most conservative update method and avoids system changes.
Why does Linux Mint update more packages?
Because its Update Manager uses –with-new-pkgs behavior.
What exactly is APT?
APT is a Linux package manager. You can read its history here: APT History
🔥 Final Thought
If you’ve ever run:
“Everything is up to date”
…and immediately didn’t believe it…
Now you know why 😄