Enable Community Repository - Revision history

Prabuanand: blanked the redirect page as per Help:Editing#Redirect

2025-10-03T15:57:38Z

blanked the redirect page as per Help:Editing#Redirect

← Older revision		Revision as of 15:57, 3 October 2025
Line 1:		Line 1:
	#REDIRECT [[Repositories#Enabling_the_community_repository]]		#REDIRECT [[Repositories#Enabling_the_community_repository]]

	~~{{Delete\|This should be covered in: https://wiki.alpinelinux.org/wiki/Repositories}}~~

	Alpine software repositories have main packages and contributions made. Each Alpine release has two branches of repositories. The '''/community''' repository of each Alpine release contains community supported packages that were accepted from the '''/testing''' repository. Only '''/main''' repository of each version of Alpine release are supported for some Main Alpine Developers and Man Powers.

	* '''Main packages''' are the Alpine package software that have direct support and updates from the Alpine core and main team, also have official documentation. Are always available for all releases and will have substitutions if some are not continued from upstream. Commonly those packages are selected due their responsibility and stability respecting upstream availability. Packages from ''testing'' that performs well or are mature goes to ''main'' branch.

	* '''Community packages''' are those made by users in team with the official developers and well near integrated to the Alpine packages. Those have supported by those user contributions and could end if the user also ends respect with Alpine work, but may be removed in a future release due lack of support by upstream author. Packages from ''testing'' that are accept goes to ''community'' branch.

	* '''Testing''' packages come into testing or edge repositories and are those made by any contributor on Alpine, the edge, this branch of repository has no release linked or related of Alpine. Those are in ''edge'' and when accepted goes to ''testing''.

	~~== Using community repositories ==~~

	~~The '''community''' repository was introduced with Alpine Linux version 3.3.~~

	~~To enable the repository, edit the file {{Path\|/etc/apk/repositories}} and add (or uncomment) a line that points to the "community" directory.~~

	~~Its format is:~~

	~~<code>'''https://<mirror-server>/alpine/<version>/community'''</code>~~

	~~{{Tip\|A usable editor is {{Pkg\|nano}}, and it can be installed with <code>apk add nano</code>.}}~~

	~~After enabling the community repository, one needs to update the index of available packages with:~~
	~~{{Cmd\|apk update}}~~
	~~And then it's possible to install packages from the community repository.~~

	~~=== Adding community repositories with a script ===~~

	~~The following commands will add the main and community repositories for the Alpine version you're using. It will overwrite your existing repository settings.~~

	~~{{cmd\|cat > /etc/apk/repositories << EOF; $(echo)~~
	~~<nowiki>~~
	~~https://dl-cdn.alpinelinux.org/alpine/v$(cut -d'.' -f1,2 /etc/alpine-release)/main/~~
	~~https://dl-cdn.alpinelinux.org/alpine/v$(cut -d'.' -f1,2 /etc/alpine-release)/community/~~
	~~https://dl-cdn.alpinelinux.org/alpine/edge/testing/~~
	~~</nowiki>~~
	~~EOF~~
	}}

	~~Dont forget to run this after:.~~
	~~{{Cmd\|apk update}}~~

	~~== Using specific package versions ==~~

	~~You can specify or pin "sticky" package versions like this:~~

	* <code><nowiki>apk add packagename=1.2.3-suffix</nowiki></code>
	* <code><nowiki>apk add 'packagename<1.2.3-suffix'</nowiki></code>

	~~That will upgrade these packages only until the specified version.~~

	~~It's then safe to use <code>apk upgrade</code> to upgrade all packages, while packages with versions will remain on the specified version.~~

	~~To set a minimum version just add <code>…</code>.~~

	~~{{Warning\|Pinning a package to an exact version carries the risk that the package will be dropped from the repo, and at some time can't be downloaded anymore (e.g. during boot or Dockerfile build).~~

	~~The official recommendation can be read here, citation below.~~
	~~Alternately, you could simply set a minimum package version~~
	~~instead of an exact version.~~

	~~We don't at the moment have resources to store all built packages~~
	~~indefinitely in our infrastructure. Thus we currently keep only~~
	~~the latest for each stable branch.~~
	}}

	~~== Using testing repositories ==~~

	The '''testing''' repository was introduced with Alpine Linux edge development. To enable the repository, edit the file {{Path\|/etc/apk/repositories}} using an editor ({{Pkg\|nano}} for instance) and add a line that points to the "testing" directory, formatted as in:

	~~<code>'''https://<mirror-server>/alpine/edge/testing'''</code>~~

	~~After enabling the testing repository, one needs to obtain the latest index of available packages with:~~
	~~{{Cmd\|apk update}}~~

	~~Inexperienced users should not enable this.~~

	~~=== Using packages from testing (edge) ===~~

	Never pin packages from the "edge" branch of the alpine package repo, as these are in test and may be revoked. (At pkgs.alpinelinux.org/packages, click "edge" and change it to the alpine image version you use, and click "search" again.)

	~~Inexperienced users should not enable this.~~



	~~= See also =~~

	~~[[Category:Package Manager]]~~

Ptrcnull: redirect to Repositories#Enabling_the_community_repository

2022-07-31T08:36:17Z

redirect to Repositories#Enabling_the_community_repository

← Older revision		Revision as of 08:36, 31 July 2022
Line 1:		Line 1:
			#REDIRECT [[Repositories#Enabling_the_community_repository]]

	{{Delete\|This should be covered in: https://wiki.alpinelinux.org/wiki/Repositories}}		{{Delete\|This should be covered in: https://wiki.alpinelinux.org/wiki/Repositories}}

Encode: This should be covered in Repositories now & Package_management#Holding_a_specific_package_back

2022-06-27T01:50:50Z

This should be covered in Repositories now & Package_management#Holding_a_specific_package_back

← Older revision		Revision as of 01:50, 27 June 2022
Line 1:		Line 1:
			{{Delete\|This should be covered in: https://wiki.alpinelinux.org/wiki/Repositories}}

	Alpine software repositories have main packages and contributions made. Each Alpine release has two branches of repositories. The '''/community''' repository of each Alpine release contains community supported packages that were accepted from the '''/testing''' repository. Only '''/main''' repository of each version of Alpine release are supported for some Main Alpine Developers and Man Powers.		Alpine software repositories have main packages and contributions made. Each Alpine release has two branches of repositories. The '''/community''' repository of each Alpine release contains community supported packages that were accepted from the '''/testing''' repository. Only '''/main''' repository of each version of Alpine release are supported for some Main Alpine Developers and Man Powers.

CindRoberta: /* Adding community repositories with a script */

2022-03-27T04:17:21Z

Adding community repositories with a script

← Older revision		Revision as of 04:17, 27 March 2022
Line 30:		Line 30:
	{{cmd\|cat > /etc/apk/repositories << EOF; $(echo)		{{cmd\|cat > /etc/apk/repositories << EOF; $(echo)
	<nowiki>		<nowiki>
	https://dl-cdn.alpinelinux.org/alpine/v$(~~cat /etc/alpine-release \|~~ cut -d'.' -f1,2)/main/		https://dl-cdn.alpinelinux.org/alpine/v$(cut -d'.' -f1,2 /etc/alpine-release)/main/
	https://dl-cdn.alpinelinux.org/alpine/v$(~~cat /etc/alpine-release \|~~ cut -d'.' -f1,2)/community/		https://dl-cdn.alpinelinux.org/alpine/v$(cut -d'.' -f1,2 /etc/alpine-release)/community/
	https://dl-cdn.alpinelinux.org/alpine/edge/testing/		https://dl-cdn.alpinelinux.org/alpine/edge/testing/
	</nowiki>		</nowiki>
	EOF		EOF

	}}		}}

Iair1234: Change repositories url to include: https (as per its format). added trailing / to make the request faster

2022-02-09T01:32:45Z

Change repositories url to include: https (as per its format). added trailing / to make the request faster

← Older revision		Revision as of 01:32, 9 February 2022
Line 30:		Line 30:
	{{cmd\|cat > /etc/apk/repositories << EOF; $(echo)		{{cmd\|cat > /etc/apk/repositories << EOF; $(echo)
	<nowiki>		<nowiki>
	~~http~~://dl-cdn.alpinelinux.org/alpine/v$(cat /etc/alpine-release \| cut -d'.' -f1,2)/main		https://dl-cdn.alpinelinux.org/alpine/v$(cat /etc/alpine-release \| cut -d'.' -f1,2)/main/
	~~http~~://dl-cdn.alpinelinux.org/alpine/v$(cat /etc/alpine-release \| cut -d'.' -f1,2)/community		https://dl-cdn.alpinelinux.org/alpine/v$(cat /etc/alpine-release \| cut -d'.' -f1,2)/community/
	~~http~~://dl-cdn.alpinelinux.org/alpine/edge/testing		https://dl-cdn.alpinelinux.org/alpine/edge/testing/
	</nowiki>		</nowiki>
	EOF		EOF

Mckaygerhard: remove newbie reference to stop the discussion

2022-01-06T13:42:21Z

remove newbie reference to stop the discussion

← Older revision		Revision as of 13:42, 6 January 2022
Line 7:		Line 7:

	* '''Testing''' packages come into testing or edge repositories and are those made by any contributor on Alpine, the edge, this branch of repository has no release linked or related of Alpine. Those are in ''edge'' and when accepted goes to ''testing''.		* '''Testing''' packages come into testing or edge repositories and are those made by any contributor on Alpine, the edge, this branch of repository has no release linked or related of Alpine. Those are in ''edge'' and when accepted goes to ''testing''.

	~~For further information check [[Alpine_newbie#APK\|Alpine newbie APK]] section wiki page.~~

	== Using community repositories ==		== Using community repositories ==
Line 87:		Line 85:

	= See also =		= See also =

	* [[Alpine_newbie#APK\|Alpine newbie APK]]

	[[Category:Package Manager]]		[[Category:Package Manager]]

Ethanpil: /* Using community repositories */

2021-11-18T01:04:41Z

Using community repositories

@@ Line 25: / Line 25: @@
 {{Cmd|apk update}}
 And then it's possible to install packages from the community repository.
 == Using specific package versions ==

Sb1: /* Using community repositories */

2021-05-08T10:13:10Z

Using community repositories

← Older revision		Revision as of 10:13, 8 May 2021
Line 14:		Line 14:
	The '''community''' repository was introduced with Alpine Linux version 3.3.		The '''community''' repository was introduced with Alpine Linux version 3.3.

	To enable the repository, edit the file {{Path\|/etc/apk/repositories}} and add (or uncomment) a line that points to the "community" directory. Its format is:		To enable the repository, edit the file {{Path\|/etc/apk/repositories}} and add (or uncomment) a line that points to the "community" directory.

			Its format is:

	<code>'''https://<mirror-server>/alpine/<version>/community'''</code>		<code>'''https://<mirror-server>/alpine/<version>/community'''</code>

Sb1: sorting

2021-05-08T10:09:24Z

sorting

← Older revision		Revision as of 10:09, 8 May 2021
Line 3:		Line 3:

	* '''Main packages''' are the Alpine package software that have direct support and updates from the Alpine core and main team, also have official documentation. Are always available for all releases and will have substitutions if some are not continued from upstream. Commonly those packages are selected due their responsibility and stability respecting upstream availability. Packages from ''testing'' that performs well or are mature goes to ''main'' branch.		* '''Main packages''' are the Alpine package software that have direct support and updates from the Alpine core and main team, also have official documentation. Are always available for all releases and will have substitutions if some are not continued from upstream. Commonly those packages are selected due their responsibility and stability respecting upstream availability. Packages from ''testing'' that performs well or are mature goes to ''main'' branch.

	* '''Community packages''' are those made by users in team with the official developers and well near integrated to the Alpine packages. Those have supported by those user contributions and could end if the user also ends respect with Alpine work, but may be removed in a future release due lack of support by upstream author. Packages from ''testing'' that are accept goes to ''community'' branch.		* '''Community packages''' are those made by users in team with the official developers and well near integrated to the Alpine packages. Those have supported by those user contributions and could end if the user also ends respect with Alpine work, but may be removed in a future release due lack of support by upstream author. Packages from ''testing'' that are accept goes to ''community'' branch.

	* '''Testing''' packages come into testing or edge repositories and are those made by any contributor on Alpine, the edge, this branch of repository has no release linked or related of Alpine. Those are in ''edge'' and when accepted goes to ''testing''.		* '''Testing''' packages come into testing or edge repositories and are those made by any contributor on Alpine, the edge, this branch of repository has no release linked or related of Alpine. Those are in ''edge'' and when accepted goes to ''testing''.

Line 22:		Line 24:
	And then it's possible to install packages from the community repository.		And then it's possible to install packages from the community repository.

	=== Using specific ~~version from testing or another version =~~==		== Using specific package versions ==

	You can ~~set~~ "sticky" versions like this:		You can specify or pin "sticky" package versions like this:

	* <code><nowiki>apk add packagename=1.2.3-suffix</nowiki></code>		* <code><nowiki>apk add packagename=1.2.3-suffix</nowiki></code>
	* <code><nowiki>apk add 'packagename<1.2.3-suffix'</nowiki></code>		* <code><nowiki>apk add 'packagename<1.2.3-suffix'</nowiki></code>

	That will upgrade packages only until the specified version. ~~You can~~ then ~~safely~~ use <code>apk upgrade</code> to upgrade all packages, while packages with versions will remain ~~with their~~ version. To set a minimum version just ~~use~~ …		That will upgrade these packages only until the specified version.

			It's then safe to use <code>apk upgrade</code> to upgrade all packages, while packages with versions will remain on the specified version.

			To set a minimum version just add <code>…</code>.

			{{Warning\|Pinning a package to an exact version carries the risk that the package will be dropped from the repo, and at some time can't be downloaded anymore (e.g. during boot or Dockerfile build).

			The official recommendation can be read here, citation below.
			Alternately, you could simply set a minimum package version
			instead of an exact version.

			We don't at the moment have resources to store all built packages
			indefinitely in our infrastructure. Thus we currently keep only
			the latest for each stable branch.
			}}

	== Using testing repositories ==		== Using testing repositories ==
Line 48:		Line 65:
	Inexperienced users should not enable this.		Inexperienced users should not enable this.

	~~== NOTES about using package versions ==~~

	Pinning a package to an exact version carries the risk that the package will be dropped from the repo, and your Dockerfile will fail to build in the future. The official recommendation can be read here, citation below.

	~~Alternately, you could simply set a minimum package version instead of an exact version.~~

	~~We don't at the moment have resources to store all built packages indefinitely in our infrastructure. Thus we currently keep only the latest for each stable branch.~~

	= See also =		= See also =

Sb1: /* Using community repositories */

2021-05-08T09:52:46Z

Using community repositories

← Older revision		Revision as of 09:52, 8 May 2021
Line 12:		Line 12:
	The '''community''' repository was introduced with Alpine Linux version 3.3.		The '''community''' repository was introduced with Alpine Linux version 3.3.

	To enable the repository, edit the file {{Path\|/etc/apk/repositories}} and add (or uncomment) a line that points to the "community" directory~~, formatted as in~~:		To enable the repository, edit the file {{Path\|/etc/apk/repositories}} and add (or uncomment) a line that points to the "community" directory. Its format is:

	<code>'''https://<mirror-server>/alpine/<version>/community'''</code>		<code>'''https://<mirror-server>/alpine/<version>/community'''</code>

	~~The~~ usable editor ({{Pkg\|nano}} can be installed with <code>apk add nano</code>~~, for instance~~.		{{Tip\|A usable editor is {{Pkg\|nano}}, and it can be installed with <code>apk add nano</code>.}}

	After enabling the community repository, one needs to ~~obtain~~ the ~~latest~~ index of available packages with:		After enabling the community repository, one needs to update the index of available packages with:
	{{Cmd\|apk update}}		{{Cmd\|apk update}}
			And then it's possible to install packages from the community repository.

	=== Using specific version from testing or another version ===		=== Using specific version from testing or another version ===