How to Back Up and Restore Installed Packages in Ubuntu

Reinstalling Ubuntu can often feel like starting from scratch, a tedious cycle of finding applications, adding repositories, and reinstalling software one by one. While older tools like Aptik offered automation, the good news is you don’t need them anymore! Ubuntu’s native dpkg package manager provides a robust, built-in solution for efficient Ubuntu package management. This guide will walk tech-savvy users through leveraging dpkg commands to effortlessly back up and restore your entire software environment, streamlining your workflow and making Linux software recovery a breeze.

Streamline Your Ubuntu Reinstalls: The dpkg and apt Way

Why dpkg is Your Go-To for Ubuntu Package Management

The frustration of setting up a fresh Ubuntu installation can be immense. Hunting down every application, meticulously adding PPAs (Personal Package Archives), and individually installing software is a significant time sink. While tools like Aptik once served this purpose, they are no longer actively maintained. Fortunately, you don’t need third-party utilities to manage your installed packages effectively. Ubuntu’s core dpkg package manager, combined with apt, offers powerful capabilities to automate this entire process. You can back up your entire installed software list and restore it seamlessly, ensuring a consistent setup across reinstalled or new systems.

Mastering Ubuntu Software Recovery: A Step-by-Step Guide

1. Generate Your Installed Package List with dpkg

The foundational step in backing up your Ubuntu software environment is to create a comprehensive list of all currently installed packages. This list acts as a blueprint for your future system.

dpkg --get-selections > packages.list

Once this command completes, a file named packages.list will be generated in your current directory. You can inspect its contents using cat packages.list. This plain text file contains every package installed via dpkg or apt, marked either as ‘install’ or ‘hold’.

Pro Tip: For auditing purposes or comparing package sets between different machines, you can copy this packages.list file to a USB stick, external drive, or secure cloud storage. Later, use diff old_packages.list new_packages.list to see what packages have been added or removed over time or between systems.

2. Secure Your Software Repositories and PPAs (Crucial for Third-Party Apps)

While your packages.list file records *what* was installed, it doesn’t always remember *where* it came from. Many popular applications—such as Google Chrome, VirtualBox, Spotify, or VS Code—are installed from third-party repositories or PPAs. Without backing up these sources, Ubuntu won’t know where to fetch these applications during restoration, leading to missing software. This step is vital for robust PPA backup Ubuntu strategies.

sudo cp -r /etc/apt/sources.list* ~/sources-backup/
sudo cp -r /etc/apt/trusted.gpg* ~/sources-backup/

Let’s break down what these critical commands achieve:

• /etc/apt/sources.list: This is the primary file defining Ubuntu’s default software repositories.
• /etc/apt/sources.list.d/: This directory holds individual .list files for additional PPAs and third-party sources you’ve integrated into your system.
• /etc/apt/trusted.gpg*: These files contain cryptographic keys used to verify the authenticity and integrity of packages downloaded from these repositories, ensuring your system’s security.
• cp -r ... ~/sources-backup/: This command recursively copies all relevant files and directories into a new folder named sources-backup within your home directory, consolidating your repository configuration.

3. Reinstall Applications Using Your dpkg Package List

After a fresh Ubuntu installation (or when setting up a new system), it’s time to bring back your customized software environment. Copy your saved packages.list file back to your home directory on the new system, then execute the following commands:

sudo dpkg --set-selections < packages.list
sudo apt update
sudo apt dselect-upgrade

Here’s a detailed explanation of each command’s role:

• dpkg --set-selections < packages.list: This command reads your backup list and instructs dpkg which packages should be marked for installation or removal on the new system. It essentially pre-configures dpkg with your desired package state.
• sudo apt update: This command refreshes Ubuntu’s local package index. It fetches the latest information about available packages and their versions from all configured repositories, ensuring that apt knows what software can be installed.
• sudo apt dselect-upgrade: This is the workhorse command. It initiates the actual installation process, reviewing the packages marked for installation by dpkg and fetching them from the updated repositories. It intelligently resolves dependencies and installs everything from your list, mimicking your previous setup.

Depending on the number of applications you had installed and your internet connection speed, this comprehensive restoration process might take some time to complete.

4. Restore Your Custom Repositories and PPA Keys

If you followed Step 2, the final piece of your Linux software recovery puzzle is to restore your backed-up PPAs and repository keys. This ensures that apt can correctly locate and install all your third-party applications (like Google Chrome, VirtualBox, Spotify, or VS Code) and keep them updated.

First, copy the sources-backup folder back to its original system location:

sudo cp -r ~/sources-backup/* /etc/apt/

Next, update Ubuntu’s package index again to register these newly restored repositories:

sudo apt update

To confirm that your PPAs and third-party sources are correctly recognized and active, you can list the contents of the sources.list.d directory:

ls /etc/apt/sources.list.d/

Conclusion: Efficient Linux Software Recovery Made Easy

Reclaiming your personalized Ubuntu software environment after a fresh installation doesn’t have to be a daunting task. By harnessing the power of Ubuntu’s built-in dpkg and apt tools, you gain a reliable and efficient method for Ubuntu package management. Moving beyond outdated solutions like Aptik, these native commands offer a straightforward path to backing up and restoring your installed applications. Following these steps will not only save you countless hours of manual reinstallation but also ensure that your system is consistently set up the way you like it, complete with all your essential third-party software and PPAs.

FAQ

Question 1: Why shouldn’t I use Aptik for Ubuntu package backup anymore?

Answer 1: Aptik, while a useful tool in its time, is no longer actively maintained. This means it may not be compatible with newer Ubuntu versions, could contain unpatched security vulnerabilities, or simply cease to function as expected. Ubuntu’s native dpkg and apt commands, as demonstrated in this guide, provide a robust, reliable, and officially supported method for package backup and restoration without relying on external, deprecated software.

Question 2: Does this method back up my personal data, configurations, or Snap/Flatpak applications?

Answer 2: No, this method primarily backs up the *list* of packages installed via dpkg/apt and your system’s software repository configurations. It does NOT back up your personal files (documents, photos, etc.), application-specific configuration files (which are typically in your home directory under ~/.config or ~/.* hidden files), or applications installed via alternative packaging systems like Snap or Flatpak. For a complete system backup including personal data and configurations, you would need a separate backup strategy involving tools like rsync, Timeshift, or cloud synchronization services. Snaps and Flatpaks also have their own distinct backup and restoration procedures.

Question 3: What if some packages fail to install during the restoration process?

Answer 3: If some packages fail to install during the sudo apt dselect-upgrade step, it’s often due to a missing repository, a broken dependency, or an unavailable package version. First, double-check that you successfully restored all your custom repositories and PPAs (Step 4) and ran sudo apt update. If issues persist, you can try running sudo apt -f install or sudo dpkg --configure -a to fix broken dependencies. Individual problematic packages can also be identified from the error messages and debugged manually. Regularly checking your packages.list against your current installed packages can also help identify discrepancies early.

Read the original article