Introduction

Keeping your Soplos Linux system updated is crucial for security, stability, and to enjoy the latest software features. Being based on Debian Testing, Soplos receives frequent package updates.

Understanding Updates

What Gets Updated?

When you update your Soplos Linux system, several components may receive updates:

  • System Packages: Core operating system components and libraries
  • Applications: Installed software and user programs
  • Linux Kernel: The core of the operating system
  • Drivers: Hardware support and firmware
  • Security Patches: Critical fixes for vulnerabilities

Types of Updates

Security Updates: High-priority updates that fix security vulnerabilities. These should be installed as soon as possible to protect your system.
  • Security Updates: Fix vulnerabilities and security issues
  • Bug Fixes: Resolve problems and improve stability
  • Feature Updates: Add new functionality to software
  • Version Upgrades: Major version changes with new features

Debian Testing & Rolling Release

Soplos Linux is based on Debian Testing, which follows a partial rolling release model. This means:

  • You receive newer software versions more frequently than stable distributions
  • Updates are tested but may occasionally introduce minor issues
  • No need for major distribution upgrades - your system evolves continuously
  • Balance between cutting-edge and stability

Graphical Method: Soplos Welcome

The easiest way to update your system is through the Soplos Welcome tool, which comes pre-installed on all editions (Tyron, Tyson, and Boro).

Soplos Welcome - Software Tab
Soplos Welcome Software tab showing Update and Upgrade buttons
  • Open Soplos Welcome from the applications menu.
  • Go to the Software tab.
  • You will find two main buttons at the top:
    • Update Repositories: Refreshes the list of available packages (equivalent to apt update).
    • Upgrade All: Installs all available updates for your system and applications (equivalent to apt upgrade).
  • Click "Update Repositories" first and wait for it to finish.
  • Then click "Upgrade All" to apply the changes.
Note: You will be asked for your administrator (root/sudo) password to perform these actions.

Advanced Method: Terminal

If you prefer full control or are used to Debian/Ubuntu, you can use the terminal. Soplos Linux uses the APT package manager.

Basic Commands

Open your favorite terminal and run:

Terminal

sudo apt update && sudo apt upgrade -y
  • sudo apt update: Refreshes the repository list.
  • sudo apt upgrade: Installs the newest versions of installed packages.
  • -y: Automatically accepts confirmations (optional).

Understanding APT Output

When you run apt upgrade, you'll see output like this:

Example Output

Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
The following packages will be upgraded:
  firefox libc6 python3
3 upgraded, 0 newly installed, 0 to remove and 2 not upgraded.

Here's what each line means:

  • X upgraded: Number of packages that will be updated
  • Y newly installed: New packages required as dependencies
  • Z to remove: Packages that need to be removed
  • N not upgraded: Packages that are "kept back" (see Troubleshooting)

Full Upgrade

Sometimes you may need to use full-upgrade instead of upgrade:

Terminal

sudo apt full-upgrade
Difference: apt upgrade never removes packages, while apt full-upgrade can install or remove packages if needed to complete the upgrade. Use full-upgrade when packages are kept back.

Cleanup (Optional)

To remove packages that are no longer needed (orphaned dependencies):

Terminal

sudo apt autoremove

Troubleshooting Common Issues

Held/Kept Back Packages

If you see packages "kept back" during an upgrade:

Example

The following packages have been kept back:
  linux-image-amd64 linux-headers-amd64
0 upgraded, 0 newly installed, 0 to remove and 2 not upgraded.

Solution: Use sudo apt full-upgrade to install these packages.

Dependency Conflicts

If you encounter dependency issues:

Terminal

# Try to fix broken dependencies
sudo apt --fix-broken install

# If that doesn't work, try:
sudo dpkg --configure -a
sudo apt update
sudo apt upgrade

Locked Database

Error: "Could not get lock /var/lib/dpkg/lock"

Important: Make sure no other package manager is running (including Soplos Welcome) before proceeding.

Terminal

# Check if apt is running
ps aux | grep apt

# If nothing important is running, remove the lock:
sudo rm /var/lib/dpkg/lock
sudo rm /var/lib/dpkg/lock-frontend
sudo dpkg --configure -a

Failed Updates

If an update fails midway:

Terminal

# Reconfigure failed packages
sudo dpkg --configure -a

# Clean package cache
sudo apt clean

# Try updating again
sudo apt update
sudo apt upgrade

Automatic Updates

You can configure automatic security updates using unattended-upgrades:

Terminal

# Install unattended-upgrades
sudo apt install unattended-upgrades

# Enable automatic updates
sudo dpkg-reconfigure -plow unattended-upgrades
Debian Testing Consideration: Since Soplos is based on Debian Testing, automatic updates should be configured carefully. It's generally recommended to review updates manually to avoid potential issues with large changes.

For most users, manual updates are recommended to maintain better control over system changes.

Update Frequency & Best Practices

Recommended Schedule

Since Soplos is based on Debian Testing (partial Rolling Release), it is recommended to check for updates:

  • Daily: Check for security updates
  • Weekly: Perform system updates to keep the system current
  • Monthly: Consider using apt full-upgrade for major updates
  • Before installing new software: To avoid dependency conflicts

Before Updating: Checklist

  • Save your work: Close important applications
  • Check disk space: Ensure you have at least 1-2GB free
  • Review backups: Especially before major updates (see Backup section)
  • Time permitting: Don't update when working on critical tasks

After Updating

  • Kernel updates: Reboot if the kernel was updated
  • Service updates: Some services may need restart
  • Clean cache: Run sudo apt autoremove periodically
Important: Being a "Testing" base, large updates can sometimes arrive. It is good practice to have backups (see Backup section) before performing massive system updates.
Pro Tip: Check /var/log/apt/history.log to see your update history and troubleshoot issues.