MigrationBot: Backfill (v3.0 review queue): added to the review queue

2026-09-22T05:42:32Z

Backfill (v3.0 review queue): added to the review queue

← Older revision		Revision as of 05:42, 22 September 2026
Line 34:		Line 34:
	[[Category:Linux\|030]]		[[Category:Linux\|030]]
	[[Category:Migrated from cypat.guide]]		[[Category:Migrated from cypat.guide]]
			[[Category:Pending review]]

MigrationBot: Import from cypat.guide: docs/linux/advanced_application_updates.md

2026-09-18T17:06:06Z

Import from cypat.guide: docs/linux/advanced_application_updates.md

New page

{{Submit}}

Author(s): Matthias Lee (ml2322) <br /> Last Updated: 9-10-2025

<br />
{| class="mw-collapsible mw-collapsed wikitable" style="width:100%"
! Recommended Prerequisites (click to expand)
|-
|

* Intermediate application updates

|}

=== Some problems with APT ===

==== Malicious Sources ====

Previously, we learned about missing or incomplete APT sources. However, not only can there be missing or inadequate sources, there could also be malicious sources that tell APT to download software from sources controlled by bad actors. Additionally, even if not malicious, unwanted sources facilitate the downloading of unwanted software and should be removed. To look for apt sources, you can check in <code>/etc/apt/sources.list</code> for any source line that does not seem to be official. Generally, all official sources will include ubuntu or the name of your distro. To be sure, you can take baselines of the this file on a clean copy of the OS and compare them. However, malicious sources don't have to be here, as apt allows for additional sources to be listed in files in <code>/etc/apt/sources.list.d</code>. Usually, this directory is empty or contains a readme of some sort, so if there's anything else in there it may be a malicious or unwanted sources. Some programs like firefox or docker require additional sources if they are to be installed with apt, so before removing a source, check and make sure that it is not required.

==== Unmet dependencies and broken packages ====

Sometimes, if the wrong package is installed or a dependency is not met, apt can enter a state where it can not function properly due to unmet dependencies. If this happens, you can run <code>apt --fix-broken install</code>. This will make apt attempt to resolve unmet dependencies and restore proper functionality. Cases like this usually happen due to installing the wrong package straight from a <code>.deb</code> file or because apt was using the wrong sources. Therefore, if you can't fix the problem with <code>apt --fix-broken install</code>, try removing any weird packages, ensuring your apt sources are set properly, running <code>apt update</code>, and then trying <code>apt --fix-broken install</code> again.

==== dpkg reconfigure ====

Another common issue that can come up with apt is that if the process is killed during the installation, update, or removal of a package, the package can become improperly configured, and apt will refuse to work. The solution is very simple however, as you can simply run <code>dpkg --force-all --configure -a</code>, and dpkg will resolve any errors, and apt should be restored.

====== Further Reading ======

* https://linuxsimply.com/linux-basics/package-management/package-manager-comparison/dpkg-vs-apt/
* https://askubuntu.com/questions/1473619/so-why-do-people-still-use-dpkg-when-there-is-apt

[[Category:Linux|030]]
[[Category:Migrated from cypat.guide]]

Draft:Advanced Application Updates - Revision history

MigrationBot: Backfill (v3.0 review queue): added to the review queue

MigrationBot: Import from cypat.guide: docs/linux/advanced_application_updates.md