How to install deb command in Debian

So, you've heard about the .deb file format and how it's the standard way to install software on Debian-based Linux distributions, like Debian itself, Ubuntu, Linux Mint, and others. You might be wondering, "How do I actually *use* a .deb file?" or perhaps you're looking for the command that handles these files. In this article, we're going to dive deep into how to install and manage .deb files using the command line on your Debian system.

The good news is, you likely already have the tools you need installed on a standard Debian system. The primary command-line tool for handling .deb packages is called dpkg. It's the low-level package manager that directly interacts with the .deb files. However, for a more user-friendly experience, especially when dealing with dependencies (other software that your desired program needs to run), you'll often use higher-level tools like apt.

Understanding the `.deb` file

A .deb file is essentially an archive containing the files to be installed, along with metadata about the package (like its name, version, and dependencies). Think of it as a self-contained installation package.

Using `dpkg` to install a `.deb` file

The dpkg command is the foundational tool for package management in Debian. While it's powerful, it doesn't automatically resolve dependencies. If a .deb file requires other packages that aren't installed, dpkg will report an error.

Here's the basic syntax for installing a .deb file using dpkg:


sudo dpkg -i /path/to/your/package.deb

Let's break this down:

sudo: This is crucial. It stands for "superuser do" and allows you to run commands with administrative privileges. Installing software modifies system files, so you need root access.
dpkg: The command-line tool for managing Debian packages.
-i: This flag tells dpkg to "install" the package.
/path/to/your/package.deb: This is the actual location of the .deb file you want to install. Replace this with the correct path on your system. For example, if you downloaded the file to your "Downloads" folder, it might look like ~/Downloads/some-software_1.0_amd64.deb.

Example: Installing a downloaded `.deb` file

Imagine you've downloaded a file named my-cool-app_1.2.3_amd64.deb into your home directory's "Downloads" folder. To install it, you would open your terminal and type:


sudo dpkg -i ~/Downloads/my-cool-app_1.2.3_amd64.deb

After pressing Enter, you'll be prompted for your user password. Type it in (you won't see characters appear on screen for security) and press Enter again.

Dealing with dependency issues with `dpkg`

As mentioned, dpkg itself doesn't fetch missing dependencies. If the installation fails with dependency errors, you'll typically see messages indicating which packages are missing. Don't panic! This is where apt comes in handy.

After running dpkg -i and encountering dependency errors, you can often fix them by running the following command:


sudo apt --fix-broken install

This command tells apt to look for any broken package installations and attempt to resolve their dependencies by downloading and installing them from your configured software repositories. It's a lifesaver!

Using `apt` to install a `.deb` file (the recommended way)

For most users, especially when you're not deeply familiar with package management, using apt is the preferred method for installing .deb files. The apt command is a higher-level package management tool that wraps around dpkg and handles dependency resolution automatically.

Here's how you install a .deb file using apt:


sudo apt install ./path/to/your/package.deb

Let's break this down:

sudo: Again, administrative privileges are needed.
apt: The advanced packaging tool.
install: The action you want apt to perform.
./path/to/your/package.deb: This is the path to your .deb file. The `./` at the beginning is important if the file is in your current directory. If it's in another location, you'd use the full path like ~/Downloads/my-cool-app_1.2.3_amd64.deb.

Why is `apt install ./package.deb` better?

The key advantage here is that apt will automatically check for any missing dependencies required by the .deb file. If it finds any, it will prompt you to confirm their installation and then download them from your configured repositories before proceeding with the installation of your .deb file. This significantly simplifies the process and reduces the chances of encountering errors.

Example: Installing with `apt`

Using the same example file, my-cool-app_1.2.3_amd64.deb in your "Downloads" folder, you would type:


sudo apt install ~/Downloads/my-cool-app_1.2.3_amd64.deb

apt will then do its magic, resolve dependencies, and install the package. You'll likely see output indicating what's being downloaded and installed.

Other useful commands

While installing is the primary goal, you might also want to:

Remove a package

To remove a package that you installed from a .deb file (or from the repositories), you can use apt or dpkg.

Using apt:


sudo apt remove package-name

Using dpkg:


sudo dpkg -r package-name

Replace package-name with the actual name of the software (not the .deb file name).

Purge a package (remove configuration files too)

To completely remove a package and its configuration files, use:

Using apt:


sudo apt purge package-name

Using dpkg:


sudo dpkg -P package-name

List installed packages

To see a list of all installed packages:


dpkg --list


apt list --installed

What if I don't have `apt` or `dpkg`?

On a standard Debian installation, these commands are almost always present. If, for some highly unusual reason, you find they are missing, you would first need to ensure your system has basic tools to download and install other packages. This would typically involve:

Ensuring your sources.list file is correctly configured to point to valid Debian repositories.
Updating your package lists: sudo apt update.
Installing the missing tools: sudo apt install dpkg apt.

However, this is an edge case. For the vast majority of users, dpkg and apt will be readily available.

In summary, while dpkg is the low-level tool that directly handles .deb files, using apt install ./package.deb is the recommended and more convenient method for installing .deb files on Debian because it handles dependency resolution automatically. Happy installing!

Frequently Asked Questions (FAQ)

How do I find the name of the package after installing a .deb file?

You can list installed packages using dpkg --list or apt list --installed. Then, you can search this list for keywords related to the software you installed. For example, if you installed "my-cool-app", you might search the output for "my-cool-app".

Why should I use `apt install ./package.deb` instead of `dpkg -i`?

Using apt install ./package.deb is recommended because apt automatically handles and installs any missing dependencies that the .deb package requires. dpkg -i, on its own, will often fail if dependencies are not met, requiring a separate step to fix them.

What is a dependency in the context of software installation?

A dependency is another piece of software (a library, another program, etc.) that your desired program needs in order to run correctly. If a program has dependencies, they must be installed on your system before the program itself can be used.

Can I install multiple .deb files at once?

Yes, you can specify multiple .deb file paths to the dpkg -i command. For example: sudo dpkg -i file1.deb file2.deb. However, when using apt install, it's generally better to install one .deb file at a time to better manage potential conflicts or dependency issues, although apt can handle multiple arguments in some scenarios.

How to install deb command in Debian