Alpine Package Keeper - Revision history

Apropos: /* World */ fix relative link

2026-03-22T03:22:28Z

World: fix relative link

← Older revision		Revision as of 03:22, 22 March 2026
Line 104:		Line 104:
	There can be only one line with a given package NAME in the file and except the package NAME, all the other options are optional.		There can be only one line with a given package NAME in the file and except the package NAME, all the other options are optional.

	* '''!''' is used for [[#~~Masking a specific package~~\|masking a specific package]]		* '''!''' is used for [[#Package masking\|masking a specific package]]
	* '''@tag''' allows apk to use the [[Repositories#Tagged_repository\|tagged repository]] for the named package		* '''@tag''' allows apk to use the [[Repositories#Tagged_repository\|tagged repository]] for the named package
	* '''[<>~=]version''' are used for [[#Package pinning\|package pinning]].		* '''[<>~=]version''' are used for [[#Package pinning\|package pinning]].

Prabuanand: removed some repetitions to reduce the content

2026-02-19T07:39:33Z

removed some repetitions to reduce the content

← Older revision		Revision as of 07:39, 19 February 2026
Line 213:		Line 213:
	== apk audit ==		== apk audit ==

	The audit applet ~~audits~~ the system or specified directories for changes compared to the package database. The ~~default option~~ is ~~to audit configuration files only. Options are available to audit all system files or to audit specified directories~~ to detect unauthorized modifications or to identify files/paths to [[Alpine_local_backup#Include_special_files/folders_to_the_apkovl\|include them in apkovl]].		The audit applet examines the system or specified directories for changes compared to the package database. The purpose of audit is to detect unauthorized modifications or to identify files/paths to [[Alpine_local_backup#Include_special_files/folders_to_the_apkovl\|include them in apkovl]].

	These flags determine ~~which files audit applet will examine i.e~~ '''scope''' of the audit.		These flags determine the '''scope''' of the audit i.e which files are examined:
	--backup (Default): Files flagged as configuration/protected		--backup (Default): Files flagged as configuration/protected
	--system: Files provided by packages but ignores new/untracked files and configuration files.		--system: Files provided by packages but ignores new/untracked files and configuration files.
	--full: All package tracked files and all newly added files/directories.		--full: All package tracked files and all newly added files/directories.

	When the audit exits with code 99 but produces no output,change the scope and re-run the audit with option --full --details to reveal the output.		When the audit exits with code 99 but produces no output, change the scope and re-run the audit with option --full --details to reveal the output.

	The following flags modify the output and provide additional information:		The following flags modify the output and provide additional information:
Line 229:		Line 229:
	The packages flag is useful to repair all packages with modified files, by using the command:{{Cmd\|<nowiki># apk audit --packages -q \| xargs apk fix</nowiki>}}		The packages flag is useful to repair all packages with modified files, by using the command:{{Cmd\|<nowiki># apk audit --packages -q \| xargs apk fix</nowiki>}}

	By default, the output format is one file per line, for each modified file. A character is printed indicating the line type, followed by a space, then either the affected path or the metadata details. The metadata details ~~usually appears~~ above the relevant file/path.		By default, the output format is one file per line, for each modified file. A character is printed indicating the line type, followed by a space, then either the affected path or the metadata details. The metadata details appear above the relevant file/path.

	An optional <path> can be added to limit the audit to a specific directory. The example output below illustrates most of the options explained above.		An optional <path> can be added to limit the audit to a specific directory. The example output below illustrates most of the options explained above.

Prabuanand: moved the exit code section and added wikilink

2026-02-19T07:30:46Z

moved the exit code section and added wikilink

← Older revision		Revision as of 07:30, 19 February 2026
Line 69:		Line 69:
	\|style="background:black; color:white" colspan=2 align=center \|Miscellaneous		\|style="background:black; color:white" colspan=2 align=center \|Miscellaneous
	\|-		\|-
	\|audit\|\| Audit system for changes		\|[[#apk audit\|audit]]\|\| Audit system for changes
	\|-		\|-
	\|stats \|\| Show statistics about repositories and installations		\|stats \|\| Show statistics about repositories and installations
Line 219:		Line 219:
	--system: Files provided by packages but ignores new/untracked files and configuration files.		--system: Files provided by packages but ignores new/untracked files and configuration files.
	--full: All package tracked files and all newly added files/directories.		--full: All package tracked files and all newly added files/directories.

			When the audit exits with code 99 but produces no output,change the scope and re-run the audit with option --full --details to reveal the output.

	The following flags modify the output and provide additional information:		The following flags modify the output and provide additional information:
Line 228:		Line 230:

	By default, the output format is one file per line, for each modified file. A character is printed indicating the line type, followed by a space, then either the affected path or the metadata details. The metadata details usually appears above the relevant file/path.		By default, the output format is one file per line, for each modified file. A character is printed indicating the line type, followed by a space, then either the affected path or the metadata details. The metadata details usually appears above the relevant file/path.

	~~Exit Codes are affected by the scope:~~
	~~1 (or 0): Audit completed and found no discrepancies~~
	~~99: The audit found discrepancies, but not printed.~~

	~~For exit code 99 with no output, change the scope and re-run the audit with options like --full --details.~~

	An optional <path> can be added to limit the audit to a specific directory. The example output below illustrates most of the options explained above.		An optional <path> can be added to limit the audit to a specific directory. The example output below illustrates most of the options explained above.

Prabuanand: clarified on the scope of the audit as this word is not part of the man page

2026-02-19T07:04:51Z

clarified on the scope of the audit as this word is not part of the man page

← Older revision		Revision as of 07:04, 19 February 2026
Line 215:		Line 215:
	The audit applet audits the system or specified directories for changes compared to the package database. The default option is to audit configuration files only. Options are available to audit all system files or to audit specified directories to detect unauthorized modifications or to identify files/paths to [[Alpine_local_backup#Include_special_files/folders_to_the_apkovl\|include them in apkovl]].		The audit applet audits the system or specified directories for changes compared to the package database. The default option is to audit configuration files only. Options are available to audit all system files or to audit specified directories to detect unauthorized modifications or to identify files/paths to [[Alpine_local_backup#Include_special_files/folders_to_the_apkovl\|include them in apkovl]].

	These flags determine which files audit applet will examine.		These flags determine which files audit applet will examine i.e '''scope''' of the audit.
	--backup (Default): ~~Only audits files~~ flagged as configuration/protected ~~(those listed in protected_paths.d).~~		--backup (Default): Files flagged as configuration/protected
	--system: ~~Audits all files~~ provided by packages ~~(integrity check)~~ but ignores new/untracked files and ~~skips~~ configuration files.		--system: Files provided by packages but ignores new/untracked files and configuration files.
	--full: ~~The most comprehensive scan. Use this option to audit all~~ package tracked files and ~~to report~~ all newly added files/directories.		--full: All package tracked files and all newly added files/directories.

	~~Exit Codes:~~
	~~Exit Code 1 (or 0): The audit completed and found no discrepancies within the specified scope.~~
	Exit Code 99: The audit found discrepancies, but they are not being printed because they fall outside the current filter (e.g., a system file was modified but you didn't use --full). If you see 99 with no output, re-run with --full --details.

	The following flags modify the output and provide additional information:		The following flags modify the output and provide additional information:
Line 233:		Line 229:
	By default, the output format is one file per line, for each modified file. A character is printed indicating the line type, followed by a space, then either the affected path or the metadata details. The metadata details usually appears above the relevant file/path.		By default, the output format is one file per line, for each modified file. A character is printed indicating the line type, followed by a space, then either the affected path or the metadata details. The metadata details usually appears above the relevant file/path.

	An optional <path> can be added to limit the audit to a specific directory ~~in all the above cases as can be seen in the~~ example output below.		Exit Codes are affected by the scope:
			1 (or 0): Audit completed and found no discrepancies
			99: The audit found discrepancies, but not printed.

			For exit code 99 with no output, change the scope and re-run the audit with options like --full --details.

			An optional <path> can be added to limit the audit to a specific directory. The example output below illustrates most of the options explained above.

	<pre>		<pre>

Prabuanand: added example along with explanations

2026-02-19T06:45:05Z

added example along with explanations

@@ Line 213: / Line 213: @@
 == apk audit ==
-The audit applet audits the system or specified directories for changes compared to the package database. The default option is to audit configuration files only. Options are available to audit all system files or to audit specified directories and files or packages.
+The audit applet audits the system or specified directories for changes compared to the package database. The default option is to audit configuration files only. Options are available to audit all system files or to audit specified directories to detect unauthorized modifications or to identify files/paths to [[Alpine_local_backup#Include_special_files/folders_to_the_apkovl|include them in apkovl]].
 == apk query ==

Prabuanand: moved the error related to info command to troubleshooting section and added apk audit

2026-02-19T04:04:01Z

moved the error related to info command to troubleshooting section and added apk audit

@@ Line 210: / Line 210: @@
 Only when the above command is run, the changes will take effect on next reboot.
 == apk query ==
@@ Line 281: / Line 285: @@
 /sbin/lbu is owned by alpine-conf-x.x-rx
 </pre>
 ===  Check Dependencies ===
@@ Line 567: / Line 561: @@
 Check the [https://irclogs.alpinelinux.org/%23alpine-linux-2026-02.log IRC logs] dated 2026-02-18 for an example on how this error was temporarily resolved.
 == See also ==

Prabuanand: added note to file a bug

2026-02-18T13:12:42Z

added note to file a bug

@@ Line 502: / Line 502: @@
 The above error message may occur in [[Edge|Edge]] branch in certain other situations, even if all the necessary [[Repositories|repositories]] are enabled. Temporary non-availability of the packages from the repositories can occur, when software packages are [https://build.alpinelinux.org/ rebuilt]. You may want to wait for some time to try again.
 === ERROR: unsatisfiable constraints ===
@@ Line 568: / Line 552: @@
 If {{ic|apk del btrbk}} is issued, the package {{Pkg|btrfs-progs}} will be automatically removed from system as the constraint {{Pkg|btrfs-progs}} does not exist in {{Path|/etc/apk/world}}.
 == See also ==

Prabuanand: fixed typo

2026-02-18T06:44:12Z

fixed typo

← Older revision		Revision as of 06:44, 18 February 2026
Line 511:		Line 511:
	</Pre>		</Pre>

	The above message can be due to version conflicts caused by a software package present in the [[#~~world~~\|world]] file.		The above message can be due to version conflicts caused by a software package present in the [[#World\|world]] file.

	To identify the offending software package, take a backup of the world file, then take stuff out of world until the upgrade works. Or alternatively, begin with a minimal version of world file and add things until it breaks again.		To identify the offending software package, take a backup of the world file, then take stuff out of world until the upgrade works. Or alternatively, begin with a minimal version of world file and add things until it breaks again.

Prabuanand: added warning about alpine-base

2026-02-18T06:18:25Z

added warning about alpine-base

← Older revision		Revision as of 06:18, 18 February 2026
Line 109:		Line 109:

	The commands {{ic\|apk add foo}} and {{ic\|apk del bar}} manipulate the desired state by adding or removing packages <code>foo</code>, <code>bar</code> respectively as a dependency constraint in {{Path\|/etc/apk/world}}. If the {{Path\|/etc/apk/world}} is edited manually, run the command [[#apk fix\|apk fix]] to apply the changes.		The commands {{ic\|apk add foo}} and {{ic\|apk del bar}} manipulate the desired state by adding or removing packages <code>foo</code>, <code>bar</code> respectively as a dependency constraint in {{Path\|/etc/apk/world}}. If the {{Path\|/etc/apk/world}} is edited manually, run the command [[#apk fix\|apk fix]] to apply the changes.

			{{Warning\|When manually editing world file, do not remove the meta package entry '''alpine-base''' or other important entries like '''linux-*''' etc. Doing so may render the system unbootable.}}

	Every constraint listed in {{Path\|/etc/apk/world}} must be solvable in order for the system to be considered correct, and no transaction may be committed that is incorrect. If apk cannot verify the correctness of the requested change, it will back out adding the constraint before attempting to change what packages are actually installed on the system. Thus apk will never [[#ERROR:_unsatisfiable_constraints\|commit]] a change to the system that leaves it unbootable.		Every constraint listed in {{Path\|/etc/apk/world}} must be solvable in order for the system to be considered correct, and no transaction may be committed that is incorrect. If apk cannot verify the correctness of the requested change, it will back out adding the constraint before attempting to change what packages are actually installed on the system. Thus apk will never [[#ERROR:_unsatisfiable_constraints\|commit]] a change to the system that leaves it unbootable.

	{{Warning\| The option {{ic\|force-broken-world}}, will delete world constraints until a solution without conflicts is found to boot. This does not allow installation of packages with unjustifiable dependencies. Using this will likely result in unexpected removal of some packages.}}		{{Warning\|The option {{ic\|force-broken-world}}, will delete world constraints until a solution without conflicts is found to boot. This does not allow installation of packages with unjustifiable dependencies. Using this will likely result in unexpected removal of some packages.}}

	== Update Package list ==		== Update Package list ==

Prabuanand: /* Huh? Error reporter did not find the broken constraints. */

2026-02-18T05:59:08Z

Huh? Error reporter did not find the broken constraints.

← Older revision		Revision as of 05:59, 18 February 2026
Line 501:		Line 501:
	The above error message may occur in [[Edge\|Edge]] branch in certain other situations, even if all the necessary [[Repositories\|repositories]] are enabled. Temporary non-availability of the packages from the repositories can occur, when software packages are [https://build.alpinelinux.org/ rebuilt]. You may want to wait for some time to try again.		The above error message may occur in [[Edge\|Edge]] branch in certain other situations, even if all the necessary [[Repositories\|repositories]] are enabled. Temporary non-availability of the packages from the repositories can occur, when software packages are [https://build.alpinelinux.org/ rebuilt]. You may want to wait for some time to try again.

	=== Huh? Error reporter did not find the broken constraints.===		=== Huh? Error reporter did not find the broken constraints===

	When [[Upgrading Alpine Linux to a new release branch]] you may receive the below message:		When [[Upgrading Alpine Linux to a new release branch]] you may receive the below message:

← Older revision		Revision as of 06:18, 18 February 2026
Line 109:		Line 109:

	The commands {{ic\|apk add foo}} and {{ic\|apk del bar}} manipulate the desired state by adding or removing packages <code>foo</code>, <code>bar</code> respectively as a dependency constraint in {{Path\|/etc/apk/world}}. If the {{Path\|/etc/apk/world}} is edited manually, run the command [[#apk fix\|apk fix]] to apply the changes.		The commands {{ic\|apk add foo}} and {{ic\|apk del bar}} manipulate the desired state by adding or removing packages <code>foo</code>, <code>bar</code> respectively as a dependency constraint in {{Path\|/etc/apk/world}}. If the {{Path\|/etc/apk/world}} is edited manually, run the command [[#apk fix\|apk fix]] to apply the changes.

			{{Warning\|When manually editing world file, do not remove the meta package entry '''alpine-base''' or other important entries like '''linux-*''' etc. Doing so may render the system unbootable.}}

	Every constraint listed in {{Path\|/etc/apk/world}} must be solvable in order for the system to be considered correct, and no transaction may be committed that is incorrect. If apk cannot verify the correctness of the requested change, it will back out adding the constraint before attempting to change what packages are actually installed on the system. Thus apk will never [[#ERROR:_unsatisfiable_constraints\|commit]] a change to the system that leaves it unbootable.		Every constraint listed in {{Path\|/etc/apk/world}} must be solvable in order for the system to be considered correct, and no transaction may be committed that is incorrect. If apk cannot verify the correctness of the requested change, it will back out adding the constraint before attempting to change what packages are actually installed on the system. Thus apk will never [[#ERROR:_unsatisfiable_constraints\|commit]] a change to the system that leaves it unbootable.

	{{Warning\| The option {{ic\|force-broken-world}}, will delete world constraints until a solution without conflicts is found to boot. This does not allow installation of packages with unjustifiable dependencies. Using this will likely result in unexpected removal of some packages.}}		{{Warning\|The option {{ic\|force-broken-world}}, will delete world constraints until a solution without conflicts is found to boot. This does not allow installation of packages with unjustifiable dependencies. Using this will likely result in unexpected removal of some packages.}}

	== Update Package list ==		== Update Package list ==