Repository management in Linux CLI - Commands & Configuration

Introduction

Managing repositories on a Linux system helps you organize and access software packages easily. It solves the problem of installing, updating, and removing software in a controlled way.

When you want to install new software that is not already on your system.

When you need to update existing software to the latest version.

When you want to remove software cleanly without leftover files.

When you want to check which software packages are installed.

When you want to add or remove software sources to get different versions.

Commands

This command refreshes the list of available software packages from the repositories. It ensures your system knows about the latest versions.

Terminal

sudo apt update

Expected Output

Hit:1 http://archive.ubuntu.com/ubuntu focal InRelease

Get:2 http://archive.ubuntu.com/ubuntu focal-updates InRelease [114 kB]

Get:3 http://archive.ubuntu.com/ubuntu focal-backports InRelease [101 kB]

Fetched 215 kB in 1s (300 kB/s)

Reading package lists... Done

This command installs the 'curl' package, a tool to transfer data from or to a server. It downloads and sets up the software on your system.

Terminal

sudo apt install curl

Expected Output

Reading package lists... Done

Building dependency tree       

Reading state information... Done

The following NEW packages will be installed:

  curl

0 upgraded, 1 newly installed, 0 to remove and 5 not upgraded.

Need to get 159 kB of archives.

After this operation, 456 kB of additional disk space will be used.

Get:1 http://archive.ubuntu.com/ubuntu focal/main amd64 curl amd64 7.68.0-1ubuntu2.7 [159 kB]

Fetched 159 kB in 1s (200 kB/s)

Selecting previously unselected package curl.

(Reading database ... 210000 files and directories currently installed.)

Preparing to unpack .../curl_7.68.0-1ubuntu2.7_amd64.deb ...

Unpacking curl (7.68.0-1ubuntu2.7) ...

Setting up curl (7.68.0-1ubuntu2.7) ...

Processing triggers for man-db (2.9.1-1) ...

This command lists all installed packages and filters the list to show only those with 'curl' in the name. It confirms that curl is installed.

Terminal

apt list --installed | grep curl

Expected Output

curl/focal-updates,focal-security,now 7.68.0-1ubuntu2.7 amd64 [installed]

→

--installed - Lists only installed packages

This command removes the 'curl' package from your system. It deletes the software but keeps configuration files.

Terminal

sudo apt remove curl

Expected Output

Reading package lists... Done

Building dependency tree       

Reading state information... Done

The following packages will be REMOVED:

  curl

0 upgraded, 0 newly installed, 1 to remove and 5 not upgraded.

After this operation, 456 kB disk space will be freed.

Do you want to continue? [Y/n] y

(Reading database ... 210500 files and directories currently installed.)

Removing curl (7.68.0-1ubuntu2.7) ...

Processing triggers for man-db (2.9.1-1) ...

Key Concept

If you remember nothing else from repository management, remember: always update your package list before installing or upgrading software.

Common Mistakes

Trying to install software without running 'sudo apt update' first

The system may not know about the latest packages and fail to find or install the software.

Run 'sudo apt update' before installing new packages to refresh the package list.

Removing software without checking dependencies

Removing a package might break other software that depends on it.

Check dependencies with 'apt depends package-name' before removing important software.

Using 'apt remove' when you want to completely delete software including config files

'apt remove' leaves configuration files behind, which might cause conflicts later.

Use 'sudo apt purge package-name' to remove software and its configuration files.

Summary

Use 'sudo apt update' to refresh the list of available software packages.

Install software with 'sudo apt install package-name' and verify installation with 'apt list --installed'.

Remove software cleanly with 'sudo apt remove package-name' or 'sudo apt purge package-name' to delete configs.

Practice

1. What is the purpose of the git init command in repository management?

easy

A. To add files to the staging area

B. To check the status of the repository

C. To upload changes to a remote repository

D. To create a new Git repository in the current directory

Solution

1. Step 1: Understand the role of git init

   This command sets up a new Git repository by creating necessary files and folders in the current directory.

2. Step 2: Differentiate from other commands

   git add stages files, git push uploads changes, and git status shows repository state, so they do not create a repository.

3. Final Answer:

   To create a new Git repository in the current directory -> Option D

4. Quick Check:

   git init creates repo [OK]

Hint: Remember: init means start a new repo [OK]

Common Mistakes:

• Confusing git init with git add
• Thinking git init uploads files
• Using git init to check status

2. Which of the following is the correct syntax to add all changed files to the staging area in Git?

easy

A. git add .

B. git add *

C. git add -all

D. git add --commit

Solution

1. Step 1: Identify the command to stage all changes

   git add . stages all changes in the current directory and subdirectories.

2. Step 2: Check other options for correctness

   git add * may not include hidden files, git add -all is invalid, and git add --commit is not a valid option.

3. Final Answer:

   git add . -> Option A

4. Quick Check:

   git add . stages all files [OK]

Hint: Use dot (.) to add all files in current folder [OK]

Common Mistakes:

• Using git add * which misses hidden files
• Typing invalid options like -all
• Confusing git add with commit commands

3. What will be the output of the command git status immediately after running git init in a new directory?

medium

A. fatal: not a git repository (or any of the parent directories): .git

B. On branch main
nothing to commit, working tree clean

C. On branch main
No commits yet
nothing to commit (create/copy files and use "git add" to track)

D. On branch master
nothing to commit, working tree clean

Solution

1. Step 1: Understand initial state after git init

   After initializing, the repository has no commits yet, so git status shows "No commits yet" and instructions to add files.

2. Step 2: Check branch name and messages

   Modern Git uses "main" as default branch, and the message includes "nothing to commit (create/copy files and use \"git add\" to track)".

3. Final Answer:

   On branch main No commits yet nothing to commit (create/copy files and use "git add" to track) -> Option C

4. Quick Check:

   New repo status shows no commits yet [OK]

Hint: New repo shows 'No commits yet' on main branch [OK]

Common Mistakes:

• Expecting 'master' branch instead of 'main'
• Thinking working tree is clean immediately
• Confusing error message with valid status

4. You ran git commit -m "Initial commit" but got the error: nothing to commit, working tree clean. What is the most likely cause?

medium

A. The repository is not initialized

B. You forgot to run git add to stage files before committing

C. The commit message is missing quotes

D. You need to run git push first

Solution

1. Step 1: Analyze the error message meaning

   The message means there are no staged changes to commit, so Git has nothing to save.

2. Step 2: Identify missing step before commit

   Files must be staged using git add before committing; skipping this causes the error.

3. Final Answer:

   You forgot to run git add to stage files before committing -> Option B

4. Quick Check:

   Stage files before commit [OK]

Hint: Always add files before commit [OK]

Common Mistakes:

• Trying to push before committing
• Ignoring the need to stage files
• Assuming commit message syntax error

5. You cloned a repository and want to update your local copy with the latest changes from the remote. Which sequence of commands correctly achieves this?

hard

A. git fetch origin; git merge origin/main

B. git pull origin main; git add .

C. git push origin main; git commit -m "update"

D. git clone origin; git commit -m "update"

Solution

1. Step 1: Understand how to update local repo from remote

   git fetch origin downloads changes from remote without merging, then git merge origin/main applies those changes to your current branch.

2. Step 2: Check other options for correctness

   git pull origin main combines fetch and merge but git add . after pull is unnecessary; git push uploads changes, not updates; git clone is for initial copy, not update.

3. Final Answer:

   git fetch origin; git merge origin/main -> Option A

4. Quick Check:

   Fetch then merge updates local repo [OK]

Hint: Fetch then merge to update local repo safely [OK]

Common Mistakes:

• Using push instead of pull to update
• Running add after pull unnecessarily
• Trying to clone again to update