Fyra Wiki - User contributions [en]

Terra

2023-11-29T10:20:09Z

Madomado: /* Installation */ new section

[[Category:Fyra Labs]]
'''Terra''', originally known as the Andaman Common repositories, is a collection of rolling-release Fedora repositories by [[Fyra Labs]] that includes commonly-used programs not packaged in the main Fedora repositories. Its sources are public in [https://github.com/terrapkg/packages a GitHub repository] and it is powered by [[Andaman]] and [[Subatomic]].

It is hosted on https://repos.fyralabs.com/terra38 and packages are provided for both x86_64 and arm64 architectures.

The development process, guidelines and policies are thoroughly documented in the [https://developer.fyralabs.com/terra/contributing Fyra Labs devdocs].

== Installation ==
Use <code>config-manager</code> from <code>dnf-plugins-core</code> to add the repository:
<syntaxhighlight lang="sh">
sudo dnf install dnf-plugins-core
sudo dnf config-manager --add-repo https://terra.fyralabs.com/terra.repo
</syntaxhighlight>

After that, you might also want to install the <code>terra-release</code> package, which automatically manages the Terra installation even when there are any changes (like migrations) to the infrastructure.

== Development ==
Terra is built on the [[Andaman]] toolchain, which makes it much easier to create, maintain and build packages compared with Koji. When updates are pushed to the main branches, GitHub actions automatically calls anda to build the corresponding package. If the build succeeds, it will then be uploaded to the actual server that hosts all the RPM packages. The process of uploading and processing the RPM package is done by the [[Subatomic]] client and server respectively. Finally, no matter if the build process failed or succeed, the build will be recorded by sending a request to [[Madoguchi]], a server for recording package information.

The above process repeats for each push event happening in the GitHub repository with the following conditions:
* The push happens in a branch with an open pull request with no merge conflicts; or
* The push happens in the <code>f*</code> branch

For those push events, the manifest task is first run which detects the files changed in the push, and a build is issued for each package with changes. Unless otherwise specified in the anda configuration file, each anda project that has changes in its directory will have its own build job for both the x86_64 and the arm64 (aka. aarch64) architectures. The x86_64 build jobs use the workers provided by GitHub, and the aarch64 workers are provided by Fyra Labs.

Manual requests for builds are also supported and it is sometimes used when packages are required to be rebuilt.

=== Updates ===
Most projects in Terra contains a <code>update.rhai</code> AndaX script that denotes how the latest version of the package is obtained. Every 30 minutes, <code>anda update</code> is run in GitHub CI. If a version different from the one in the spec file is detected, anda automatically bumps the package, and a new commit will be created for all the package updates and pushed to the main branch (<code>f38</code>). Additionally, the commit is also cloned to the other branches (such as <code>f37</code>) and also pushed. If the cloning process fails (usually due to conflicts), the updates will not be done for the other branches.

Nightly packages are excluded from the above process and they have a separate workflow for the <code>anda update</code> process which runs daily.

== History ==
After [[Andaman]] was created, the [[Ultramarine]] Project has migrated their repositories into GitHub monorepos. However, a setup was preferred where packages can be shared between both Ultramarine Linux and [[TauOS]], and even other Fedora distributions. This led to the creation of the '''Andaman Common Repositories''', also known as the '''Andaman Subatomic Repositories'''. The original GitHub organisation name was ''andaman-common-pkgs'', and the repository for ''Fedora Extras 37'' was located at <code><nowiki>https://subatomic.fyralabs.com/fe37</nowiki></code>. It was then renamed to ''Andaman Common Packages 37'' and was moved to <code><nowiki>https://subatomic.fyralabs.com/ad37</nowiki></code>. It was later finally renamed to Terra, and now contains many common packages not found in the Fedora repositories.

== External Links ==
* Website: https://terra.fyralabs.com
* Repology: https://repology.org/repository/terra_38
* Monorepo: https://github.com/terrapkg/packages
* RPMs: https://repos.fyralabs.com/terra38
* Devdocs: https://developer.fyralabs.com/terra

Andaman

2023-09-17T07:45:05Z

Madomado: /* Installation */ add instructions on how to install anda

[[Category:Fyra Labs]]
[[Category:Projects]]
'''Andaman''', often abbreviated as '''anda''', is a modern package build toolchain designed to
simplify building different package formats for different projects in the same repository.
It mainly supports monorepo setups, especially ones with CI support like GitHub. It currently supports building RPMs, OCI images and Flatpak packages.
It is written by [[Ultramarine Linux]] originally<ref group="note">The original GitHub repository was located at https://github.com/Ultramarine-Linux/anda, but now it redirects to [https://github.com/FyraLabs/anda the new URL].</ref> and [[Fyra Labs]] with the Rust programming language.

Anda's simplicity makes the packaging process seamless and it is most notably used in [[Terra]].

== Installation ==
On systems with [[Terra]], you can install it with <code>sudo dnf5 in anda</code> (or dnf).

On systems with [[w:Rust (Programming langauge)#Cargo|Cargo]], you can install it with <code>cargo install anda</code>.

Alternatively you can also manually download the sources from GitHub:
<syntaxhighlight lang="bash">
git clone https://github.com/FyraLabs/anda
cd anda
git checkout 0.1.18
cargo install --path .
</syntaxhighlight>

== Mechanisms ==
Currently, Anda is simply a meta-build system that calls upon other build systems to build and distribute packages. It reads the project manifest in <code>anda.hcl</code> and calls the corresponding build system to build the package. Multiple projects can be included in a single repository (known as a ''monorepo'') recursively in different directories. The root directory contains a main configuration file (also <code>anda.hcl</code>) and the configurations will be inherited. All the other <code>anda.hcl</code> files in its subdirectory can independently represent multiple ''projects'', and multiple ways to build a package can be specified in each project. Once properly configured, a project can be built by <code>anda build ''subdirectory_path''/''project_name''</code>.

All configurations should be written in the HashiCorp Configuration Language with the filename <code>anda.hcl</code> and will be parsed in <code>anda-config</code>.

=== Building process ===
When Anda needs to build RPMs, it first loads all the <code>anda.hcl</code> configuration files, then run all executable <code>pre_script</code>s.
Then, Anda will build RPMs, Flatpak, Podman and Docker artifacts, then run the build scripts and finally the <code>post_script</code>s.

All the scripts in Anda can either be a command that can be executed with <code>sh -c</code>, or a path to an AndaX script with the extension <code>.rhai</code>.
Other package types are processed as follows:
* ''RPM'': Anda calls either <code>mock</code> or <code>rpmbuild</code> depending on the <code>--rpm_builder</code> option which defaults to <code>mock</code>.
* ''Flatpak'': The manifest is read using the <code>flatpak</code> crate and the application is built using <code>flatpak-builder</code>. As of 0.1.17, the output is always located at <code>.flatpak-builder/build/</code>, as opposed to <code>anda-build/</code> used by other package types.
* ''Docker''/''Podman'': Anda calls <code>docker build</code> or <code>podman build</code>.

=== AndaX ===
'''AndaX''' is an embedded scripting system powered by [https://rhai.rs Rhai]. It is mainly for supporting automatic updates, but it is also the scripting system used behind
<code>pre_script</code> and <code>post_script</code>.

AndaX loads all the Rhai module script files from the following paths:
* <code>/usr/lib/anda/</code>
* <code>/usr/local/lib/anda/</code>
* <code>/usr/lib64/anda/</code>
* <code>/usr/local/lib64/anda/</code>
* <code>~/.local/lib/anda/</code>

The following static modules (built into AndaX directly) are also available:
* <code>io</code>
* <code>tsunagu</code>
* <code>kokoro</code>
* <code>tenshi</code>
* <code>anda::rpmbuild</code>
* <code>anda::cfg</code>

Most if not all of the functions in the above static modules are well-documented in [https://developer.fyralabs.com/terra/autoupdate DevDocs].
You can pass labels into the AndaX executor during with the <code>--labels</code> command-line argument. A label is a key-value pair that can be used to tag packages (is it a nightly package?), adding special variables, etc. Different labels should be separated by commas, like so: <code>--labels commit_sha=abc1234,environment=gh_ci,key_value_pair=k=v</code>, which will be parsed to:
<syntaxhighlight lang="json">
{
"commit_sha": "abc1234",
"environment": "gh_ci",
"key_value_pair": "k=v"
}
</syntaxhighlight>

=== Automatic Updates ===
: See also: [https://developer.fyralabs.com/terra/autoupdate Fyra Developer: Terra autoupdate] for the supported functions in AndaX
Anda has refined support over automatically updating packages via the <code>anda update</code> command. The command finds all the projects with the file <code>update.rhai</code> in the same directory or if the configuration file has the <code>update</code> property set to a value:
<syntaxhighlight lang="js">
project project_name {
update = "path/to/update_script.rhai"
labels {
a = "1"
}
}
</syntaxhighlight>
Then, AndaX executes the scripts in parallel, where each update script gets its own thread. This greatly reduces the time required to fetch package versions. Note that Rhai does not support asynchronous programming. Around 200 update scripts in Terra can be processed under a second.

Projects can also be filtered by adding <code>--filters key=value,key2=value2</code> to the command. For example, the update script for the above project will be executed for <code>--filters a=1</code> or even without filters related to <code>a</code>, but it won't be executed for <code>--filters a=2</code>.

== Configuration ==
Andaman uses the HashiCorp Configuration Language (HCL) for its configuration format, known for being used in software by HashiCorp such as Terraform, Consul, Vault and Packer. Its syntax is similar to UCL and NGINX's configuration format.

Consider the following. for <code>{ }</code> and <code>""</code>, they represent, respectively, an dictionary (empty by default) with keys and string values, and a string with no default value. Unless otherwise stated, all the attributes are optional.
<syntaxhighlight lang="js">
config {
mock_config = "" // default mock config for `anda build -c custom_mock_config`
strip_prefix = "" // strip prefix to form new project alias
strip_suffix = "" // strip suffix to form new project alias
project_regex = ""
}
project "project_name" { // the string quote is optional
rpm {
spec = "path/to/file.spec" // REQUIRED
sources = "."
package = ""
pre_script = "rpm_pre.rhai"
post_script = "rpm_post.rhai"
mock_config = ""
enable_scm = false
scm_opts { }
config { }
plugin_opts { }
macros { }
opts { }
}
podman tagname {
dockerfile = ""
import = ""
tag_latest = false
context = "" // REQUIRED
version = ""
}
docker tagname {
dockerfile = ""
import = ""
tag_latest = false
context = "" // REQUIRED
version = ""
}
flatpak {
manifest = "path/to/manifest.yml" // REQUIRED
pre_script = ""
post_script = ""
}
pre_script = "pre.rhai"
post_script = "post.rhai"
env { }
alias = [] // array of strings
scripts = [] // array of paths to AndaX scripts
labels { }
update = "update.rhai"
arches = ["x86_64", "aarch64"]
}
</syntaxhighlight>

== History ==
=== umpkg ===
In the very beginning, the [[Ultramarine]] Project had been using Koji for building RPM packages. Koji is the packaging system used by the [[wikipedia:Fedora Project|Fedora Project]]. However, Koji's sophistication makes it difficult to create and maintain RPM packages — it was said that the only person in the Ultramarine team who actually knew how to use Koji was the lead developer, [[Cappy Ishihara]]. Cappy was annoyed by the sheer complexity of building and uploading packages to Koji and made [[umpkg]], a packaging toolchain that runs on Mock and Koji. The creation of umpkg made it easier to create and maintain packages. However, umpkg still tightly integrates with Koji and uses the Koji API to trigger builds. Thus, an entirely new CI server was proposed.

=== RPM Frontend ===
The Ultramarine Project started work on Andaman on 9 Jun, 2022.
The name Andaman refers to the [[wikipedia:Andaman Sea|Andaman Sea]] next to Thailand, and follows the naming patterns for other projects related to Ultramarine.
Initially, Anda was written as a custom RPM frontend as an alternative to DNF that is similar to that of an AUR helper. However, there were issues with rust and RPM support.

=== CI Server ===
Anda was then rewritten as a CI Server that handles builds via BuildKit, stores artifacts and build infos, and later included a frontend to the server.
However, it slowly turned into a massive feature creep of projects.

=== Final rewrite ===
Thus, Anda was rewritten again and it finally became a build system for various package formats.

=== Terra ===
: Main Article: [[Terra]]
After the creation of Anda, the Ultramarine Project has migrated their repositories into [https://github.com/Ultramarine-Linux/ultramarine-pkgs GitHub monorepos]. However, a repository containing packages for not only Ultramarine Linux, but also all other Fedora distributions was wanted so that packages can be shared between both Ultramarine Linux and [[TauOS]], which led to the creation of the '''Andaman Common Repositories''', also known as the '''Andaman Subatomic Repositories'''.<ref group="note">The original GitHub organisation was called "andaman-common-pkgs", and the original repository url was <code><nowiki>https://subatomic.fyralabs.com/ad37/</nowiki></code>.</ref> It was later renamed to '''[[Terra]]''', and now contains many common packages not found in the Fedora repositories.

== Notes ==
<references group="note"/>

== See Also ==
* [[Terra]]
* [[Subatomic]]

Madomado

2023-07-08T16:48:10Z

Madomado: Madomado modifies manually Madonuko, Madoguchi.

{{Copy edit|for=grammar|date=June 2023}}
'''Madomado''', also known as '''Mado''', is not a ''mado'' (<ruby>窓<rt>まど</rt></ruby>, Japanese for "window"), and has nothing to do with ''mado''s.
Mado is responsible for partially the development of [[Ultramarine Linux]].
Consequently, after the acquisition, Mado is a DevOps Engineer in [[Fyra Labs]] and is responsible for numerous projects,
most notably [[Terra]], [[Andaman]], and [[Madoguchi]].
== Madonuko ==
'''Madonuko''', Madomado's original character, is not a ''mado'', and has nothing to do with ''mado''s.
Instead, Madonuko is a ''nuko'' (ぬこ, Japanese slang for "cat").
Madomado is not Madonuko, because if Madomado is Madonuko, mado is nuko, and thus
''mado'' is ''nuko'' (a window is a cat). But, ''mado'' is not ''nuko'' (a window is not a cat), so Mado's assumption is false. (Proof by contradiction)
However, Mado is an element of the set ''nuko''. In other words, Mado is a ''nuko''.
Despite that, it is still ok to use the name Madonuko to refer to Madomado.
== Madoguchi ==
: Main article: [[Madoguchi]]
'''Madoguchi''', a creation by Madomado, is not a ''mado'', and has nothing to do with ''mado''s.
Instead, Madoguchi is a ''guchi'' (愚痴, Japanese for "complaint"? <del>Or maybe Gu*** handbags?</del>). Except, Madoguchi, also known as '''Mg''' (which, contrary to popular opinions, is not made out of magnesium, and has nothing to do with magnesium), is not a ''guchi'', and has nothing to do with ''guchi''s. Instead, Madoguchi (<ruby>窓口<rt>まどぐち</rt></ruby>, Japanese for "ticket window", literal meaning "window mouth") is an API server for <del>Mado</del> things related to [[Terra]]. Mado made it so that Repology can redirect dumb entities like Mado to the corresponding package sources hosted on GitHub. The name Madoguchi refers to the [[wikipedia:MARS (ticket reservation system)#Outline|JR green ticket windows]] (''Midori no Madoguchi'', みどりの<ruby>窓口<rt>まどぐち</rt></ruby>) in Japan serving people with all sorts of tickets.
Please note that Madoguchi does not sell tickets for ''mado''s, ''guchi''s (whether the handbags or the complaints), or food (because Mado ate all of them).
Madoguchi is created and maintained by mostly Madomado. Madomado uses special ingredients to make Madoguchi, including oxygen and [[wikipedia:Dihydrogen monoxide parody|dihydrogen monoxide]], illustrated by the following chemical reaction:
4Fe + 3O₂ + 2''n''H₂O → 2Fe₂O₃·''n''H₂O
which results in the product ''hydrated iron(III) oxide'', commonly known as [[wikipedia:Rust (programming language)|rust]].

Andaman

2023-06-26T11:43:20Z

Madomado: /* Mechanisms */ Document more technical details

[[Category:Fyra Labs]]
[[Category:Projects]]
'''Andaman''', often abbreviated as '''anda''', is a modern package build toolchain designed to
simplify building different package formats for different projects in the same repository.
It mainly supports monorepo setups, especially ones with CI support like GitHub. It currently supports building RPMs, OCI images and Flatpak packages.
It is written by [[Ultramarine Linux]] originally<ref group="note">The original GitHub repository was located at https://github.com/Ultramarine-Linux/anda, but now it redirects to [https://github.com/FyraLabs/anda the new URL].</ref> and [[Fyra Labs]] with the Rust programming language.

Anda's simplicity makes the packaging process seamless and it is most notably used in [[Terra]].

== Mechanisms ==
Currently, Anda is simply a meta-build system that calls upon other build systems to build and distribute packages. It reads the project manifest in <code>anda.hcl</code> and calls the corresponding build system to build the package. Multiple projects can be included in a single repository (known as a ''monorepo'') recursively in different directories. The root directory contains a main configuration file (also <code>anda.hcl</code>) and the configurations will be inherited. All the other <code>anda.hcl</code> files in its subdirectory can independently represent multiple ''projects'', and multiple ways to build a package can be specified in each project. Once properly configured, a project can be built by <code>anda build ''subdirectory_path''/''project_name''</code>.

All configurations should be written in the HashiCorp Configuration Language with the filename <code>anda.hcl</code> and will be parsed in <code>anda-config</code>.

=== Building process ===
When Anda needs to build RPMs, it first loads all the <code>anda.hcl</code> configuration files, then run all executable <code>pre_script</code>s.
Then, Anda will build RPMs, Flatpak, Podman and Docker artifacts, then run the build scripts and finally the <code>post_script</code>s.

All the scripts in Anda can either be a command that can be executed with <code>sh -c</code>, or a path to an AndaX script with the extension <code>.rhai</code>.
Other package types are processed as follows:
* ''RPM'': Anda calls either <code>mock</code> or <code>rpmbuild</code> depending on the <code>--rpm_builder</code> option which defaults to <code>mock</code>.
* ''Flatpak'': The manifest is read using the <code>flatpak</code> crate and the application is built using <code>flatpak-builder</code>. As of 0.1.17, the output is always located at <code>.flatpak-builder/build/</code>, as opposed to <code>anda-build/</code> used by other package types.
* ''Docker''/''Podman'': Anda calls <code>docker build</code> or <code>podman build</code>.

=== AndaX ===
'''AndaX''' is an embedded scripting system powered by [https://rhai.rs Rhai]. It is mainly for supporting automatic updates, but it is also the scripting system used behind
<code>pre_script</code> and <code>post_script</code>.

AndaX loads all the Rhai module script files from the following paths:
* <code>/usr/lib/anda/</code>
* <code>/usr/local/lib/anda/</code>
* <code>/usr/lib64/anda/</code>
* <code>/usr/local/lib64/anda/</code>
* <code>~/.local/lib/anda/</code>

The following static modules (built into AndaX directly) are also available:
* <code>io</code>
* <code>tsunagu</code>
* <code>kokoro</code>
* <code>tenshi</code>
* <code>anda::rpmbuild</code>
* <code>anda::cfg</code>

Most if not all of the functions in the above static modules are well-documented in [https://developer.fyralabs.com/terra/autoupdate DevDocs].
You can pass labels into the AndaX executor during with the <code>--labels</code> command-line argument. A label is a key-value pair that can be used to tag packages (is it a nightly package?), adding special variables, etc. Different labels should be separated by commas, like so: <code>--labels commit_sha=abc1234,environment=gh_ci,key_value_pair=k=v</code>, which will be parsed to:
<syntaxhighlight lang="json">
{
"commit_sha": "abc1234",
"environment": "gh_ci",
"key_value_pair": "k=v"
}
</syntaxhighlight>

=== Automatic Updates ===
: See also: [https://developer.fyralabs.com/terra/autoupdate Fyra Developer: Terra autoupdate] for the supported functions in AndaX
Anda has refined support over automatically updating packages via the <code>anda update</code> command. The command finds all the projects with the file <code>update.rhai</code> in the same directory or if the configuration file has the <code>update</code> property set to a value:
<syntaxhighlight lang="js">
project project_name {
update = "path/to/update_script.rhai"
labels {
a = "1"
}
}
</syntaxhighlight>
Then, AndaX executes the scripts in parallel, where each update script gets its own thread. This greatly reduces the time required to fetch package versions. Note that Rhai does not support asynchronous programming. Around 200 update scripts in Terra can be processed under a second.

Projects can also be filtered by adding <code>--filters key=value,key2=value2</code> to the command. For example, the update script for the above project will be executed for <code>--filters a=1</code> or even without filters related to <code>a</code>, but it won't be executed for <code>--filters a=2</code>.

== Configuration ==
Andaman uses the HashiCorp Configuration Language (HCL) for its configuration format, known for being used in software by HashiCorp such as Terraform, Consul, Vault and Packer. Its syntax is similar to UCL and NGINX's configuration format.

Consider the following. for <code>{ }</code> and <code>""</code>, they represent, respectively, an dictionary (empty by default) with keys and string values, and a string with no default value. Unless otherwise stated, all the attributes are optional.
<syntaxhighlight lang="js">
config {
mock_config = "" // default mock config for `anda build -c custom_mock_config`
strip_prefix = "" // strip prefix to form new project alias
strip_suffix = "" // strip suffix to form new project alias
project_regex = ""
}
project "project_name" { // the string quote is optional
rpm {
spec = "path/to/file.spec" // REQUIRED
sources = "."
package = ""
pre_script = "rpm_pre.rhai"
post_script = "rpm_post.rhai"
mock_config = ""
enable_scm = false
scm_opts { }
config { }
plugin_opts { }
macros { }
opts { }
}
podman tagname {
dockerfile = ""
import = ""
tag_latest = false
context = "" // REQUIRED
version = ""
}
docker tagname {
dockerfile = ""
import = ""
tag_latest = false
context = "" // REQUIRED
version = ""
}
flatpak {
manifest = "path/to/manifest.yml" // REQUIRED
pre_script = ""
post_script = ""
}
pre_script = "pre.rhai"
post_script = "post.rhai"
env { }
alias = [] // array of strings
scripts = [] // array of paths to AndaX scripts
labels { }
update = "update.rhai"
arches = ["x86_64", "aarch64"]
}
</syntaxhighlight>

== History ==
=== umpkg ===
In the very beginning, the [[Ultramarine]] Project had been using Koji for building RPM packages. Koji is the packaging system used by the [[wikipedia:Fedora Project|Fedora Project]]. However, Koji's sophistication makes it difficult to create and maintain RPM packages — it was said that the only person in the Ultramarine team who actually knew how to use Koji was the lead developer, [[Cappy Ishihara]]. Cappy was annoyed by the sheer complexity of building and uploading packages to Koji and made [[umpkg]], a packaging toolchain that runs on Mock and Koji. The creation of umpkg made it easier to create and maintain packages. However, umpkg still tightly integrates with Koji and uses the Koji API to trigger builds. Thus, an entirely new CI server was proposed.

=== RPM Frontend ===
The Ultramarine Project started work on Andaman on 9 Jun, 2022.
The name Andaman refers to the [[wikipedia:Andaman Sea|Andaman Sea]] next to Thailand, and follows the naming patterns for other projects related to Ultramarine.
Initially, Anda was written as a custom RPM frontend as an alternative to DNF that is similar to that of an AUR helper. However, there were issues with rust and RPM support.

=== CI Server ===
Anda was then rewritten as a CI Server that handles builds via BuildKit, stores artifacts and build infos, and later included a frontend to the server.
However, it slowly turned into a massive feature creep of projects.

=== Final rewrite ===
Thus, Anda was rewritten again and it finally became a build system for various package formats.

=== Terra ===
: Main Article: [[Terra]]
After the creation of Anda, the Ultramarine Project has migrated their repositories into [https://github.com/Ultramarine-Linux/ultramarine-pkgs GitHub monorepos]. However, a repository containing packages for not only Ultramarine Linux, but also all other Fedora distributions was wanted so that packages can be shared between both Ultramarine Linux and [[TauOS]], which led to the creation of the '''Andaman Common Repositories''', also known as the '''Andaman Subatomic Repositories'''.<ref group="note">The original GitHub organisation was called "andaman-common-pkgs", and the original repository url was <code><nowiki>https://subatomic.fyralabs.com/ad37/</nowiki></code>.</ref> It was later renamed to '''[[Terra]]''', and now contains many common packages not found in the Fedora repositories.

== Notes ==
<references group="note"/>

== See Also ==
* [[Terra]]
* [[Subatomic]]

Andaman

2023-06-12T10:41:17Z

Madomado: note original creation

Andaman

2023-06-12T10:37:19Z

Madomado: /* Terra */ fix wrong repo url in note

Terra

2023-06-12T10:35:16Z

Madomado: /* History */ summary on how Terra was created

[[Category:Fyra Labs]]
'''Terra''', originally known as the Andaman Common repositories, is a collection of rolling-release Fedora repositories by [[Fyra Labs]] that includes commonly-used programs not packaged in the main Fedora repositories. Its sources are public in [https://github.com/terrapkg/packages a GitHub repository] and it is powered by [[Andaman]] and [[Subatomic]].

It is hosted on https://repos.fyralabs.com/terra38 and packages are provided for both x86_64 and arm64 architectures.

The development process, guidelines and policies are thoroughly documented in the [https://developer.fyralabs.com/terra/contributing Fyra Labs devdocs].

== Development ==
Terra is built on the [[Andaman]] toolchain, which makes it much easier to create, maintain and build packages compared with Koji. When updates are pushed to the main branches, GitHub actions automatically calls anda to build the corresponding package. If the build succeeds, it will then be uploaded to the actual server that hosts all the RPM packages. The process of uploading and processing the RPM package is done by the [[Subatomic]] client and server respectively. Finally, no matter if the build process failed or succeed, the build will be recorded by sending a request to [[Madoguchi]], a server for recording package information.

The above process repeats for each push event happening in the GitHub repository with the following conditions:
* The push happens in a branch with an open pull request with no merge conflicts; or
* The push happens in the <code>f*</code> branch

For those push events, the manifest task is first run which detects the files changed in the push, and a build is issued for each package with changes. Unless otherwise specified in the anda configuration file, each anda project that has changes in its directory will have its own build job for both the x86_64 and the arm64 (aka. aarch64) architectures. The x86_64 build jobs use the workers provided by GitHub, and the aarch64 workers are provided by Fyra Labs.

Manual requests for builds are also supported and it is sometimes used when packages are required to be rebuilt.

=== Updates ===
Most projects in Terra contains a <code>update.rhai</code> AndaX script that denotes how the latest version of the package is obtained. Every 30 minutes, <code>anda update</code> is run in GitHub CI. If a version different from the one in the spec file is detected, anda automatically bumps the package, and a new commit will be created for all the package updates and pushed to the main branch (<code>f38</code>). Additionally, the commit is also cloned to the other branches (such as <code>f37</code>) and also pushed. If the cloning process fails (usually due to conflicts), the updates will not be done for the other branches.

Nightly packages are excluded from the above process and they have a separate workflow for the <code>anda update</code> process which runs daily.

== History ==
After [[Andaman]] was created, the [[Ultramarine]] Project has migrated their repositories into GitHub monorepos. However, a setup was preferred where packages can be shared between both Ultramarine Linux and [[TauOS]], and even other Fedora distributions. This led to the creation of the '''Andaman Common Repositories''', also known as the '''Andaman Subatomic Repositories'''. The original GitHub organisation name was ''andaman-common-pkgs'', and the repository for ''Fedora Extras 37'' was located at <code><nowiki>https://subatomic.fyralabs.com/fe37</nowiki></code>. It was then renamed to ''Andaman Common Packages 37'' and was moved to <code><nowiki>https://subatomic.fyralabs.com/ad37</nowiki></code>. It was later finally renamed to Terra, and now contains many common packages not found in the Fedora repositories.

== External Links ==
* Website: https://terra.fyralabs.com
* Repology: https://repology.org/repository/terra_38
* Monorepo: https://github.com/terrapkg/packages
* RPMs: https://repos.fyralabs.com/terra38
* Devdocs: https://developer.fyralabs.com/terra

Andaman

2023-06-12T10:25:03Z

Madomado: /* Terra */ add history

Terra

2023-06-11T03:24:52Z

Madomado: init

[[Category:Fyra Labs]]
'''Terra''', originally known as the Andaman Common repositories, is a collection of rolling-release Fedora repositories by [[Fyra Labs]] that includes commonly-used programs not packaged in the main Fedora repositories. Its sources are public in [https://github.com/terrapkg/packages a GitHub repository] and it is powered by [[Andaman]] and [[Subatomic]].

It is hosted on https://repos.fyralabs.com/terra38 and packages are provided for both x86_64 and arm64 architectures.

The development process, guidelines and policies are thoroughly documented in the [https://developer.fyralabs.com/terra/contributing Fyra Labs devdocs].

== Development ==
Terra is built on the [[Andaman]] toolchain, which makes it much easier to create, maintain and build packages compared with Koji. When updates are pushed to the main branches, GitHub actions automatically calls anda to build the corresponding package. If the build succeeds, it will then be uploaded to the actual server that hosts all the RPM packages. The process of uploading and processing the RPM package is done by the [[Subatomic]] client and server respectively. Finally, no matter if the build process failed or succeed, the build will be recorded by sending a request to [[Madoguchi]], a server for recording package information.

The above process repeats for each push event happening in the GitHub repository with the following conditions:
* The push happens in a branch with an open pull request with no merge conflicts; or
* The push happens in the <code>f*</code> branch

For those push events, the manifest task is first run which detects the files changed in the push, and a build is issued for each package with changes. Unless otherwise specified in the anda configuration file, each anda project that has changes in its directory will have its own build job for both the x86_64 and the arm64 (aka. aarch64) architectures. The x86_64 build jobs use the workers provided by GitHub, and the aarch64 workers are provided by Fyra Labs.

Manual requests for builds are also supported and it is sometimes used when packages are required to be rebuilt.

=== Updates ===
Most projects in Terra contains a <code>update.rhai</code> AndaX script that denotes how the latest version of the package is obtained. Every 30 minutes, <code>anda update</code> is run in GitHub CI. If a version different from the one in the spec file is detected, anda automatically bumps the package, and a new commit will be created for all the package updates and pushed to the main branch (<code>f38</code>). Additionally, the commit is also cloned to the other branches (such as <code>f37</code>) and also pushed. If the cloning process fails (usually due to conflicts), the updates will not be done for the other branches.

Nightly packages are excluded from the above process and they have a separate workflow for the <code>anda update</code> process which runs daily.

== External Links ==
* Website: https://terra.fyralabs.com
* Repology: https://repology.org/repository/terra_38
* Monorepo: https://github.com/terrapkg/packages
* RPMs: https://repos.fyralabs.com/terra38
* Devdocs: https://developer.fyralabs.com/terra

Andaman

2023-06-10T09:16:02Z

Madomado: /* Configuration */ add section; /* History */ add more info related to rewrites

Ultramarine

2023-06-10T04:43:36Z

Madomado: redirect to Ultramarine Linux

#REDIRECT [[Ultramarine Linux]]

Anda

2023-06-10T04:42:20Z

Madomado: redirect to Andaman

#REDIRECT [[Andaman]]

Andaman

2023-06-10T04:16:20Z

Madomado: init

[[Category:Fyra Labs]]
'''Andaman''', often abbreviated as '''anda''', is a modern packaged build toolchain designed to
simplify building different package formats for different projects in the same repository.
It mainly supports monorepo setups, especially ones with CI support like GitHub. It currently supports building RPMs, OCI images and Flatpak packages.
It is written by [[Fyra Labs]] with the Rust programming language.

== Mechanisms ==
Currently, Anda is simply a meta-build system that calls upon other build systems to build and distribute packages. It reads the project manifest in <code>anda.hcl</code>
and calls the corresponding build system to build the package. Multiple projects can be included in a single repository (known as a ''monorepo'') recursively in different directories. The root directory contains a main configuration file (also <code>anda.hcl</code>) and the configurations will be inherited. All the other <code>anda.hcl</code> files in its subdirectory can independently represent multiple ''projects'', and multiple ways to build a package can be specified in each project. Once properly configured, a project can be built by <code>anda build ''subdirectory_path''/''project_name''</code>.

=== AndaX ===
'''AndaX''' is an embedded scripting system powered by [https://rhai.rs Rhai]. It is mainly for supporting automatic updates, but it is also the scripting system used behind
<code>pre_script</code> and <code>post_script</code>.

=== Automatic Updates ===
Anda has refined support over automatically updating packages via the <code>anda update</code> command. The command finds all the projects with the file <code>update.rhai</code> in the same directory or if the configuration file has the <code>update</code> property set to a value:
<syntaxhighlight lang="hcl">
project proj_name {
update = "path/to/update_script.rhai"
labels {
a = "1"
}
}
</syntaxhighlight>
Then, AndaX executes the script. Projects can also be filtered by adding <code>--filters key=value,key2=value2</code> to the command.
For example, the above project will be ran for <code>--filters a=1</code> or even without filters regarding the key <code>a</code>, but
it will be filtered for <code>--filters a=2</code>.

== History ==

The name Andaman refers to the [[wikipedia:Andaman Sea|Andaman Sea]] next to Thailand, and follows the [[Ultramarine Linux|Ultramarine]] marine naming usage.

Madomado

2023-06-09T16:47:44Z

Madomado: /* Madoguchi */ add chemical equation

{{Copy edit|for=grammar|date=June 2023}}

'''Madomado''', also known as '''Mado''', is not a ''mado'' (<ruby>窓<rt>まど</rt></ruby>, Japanese for "window"), and has nothing to do with ''mado''s.
Mado is responsible for partially the development of [[Ultramarine Linux]].
Consequently, after the acquisition, Mado is a DevOps Engineer in [[Fyra Labs]] and is responsible for numerous projects,
most notably [[Terra]], [[Andaman]], and [[Madoguchi]].

== Madonuko ==
Madomado's original character is '''Madonuko'''. Madonuko is not a ''mado'', and has nothing to do with ''mado''s.
Instead, Madonuko is a ''nuko'' (ぬこ, Japanese slang for "cat").

Madomado is not Madonuko, because if Madomado is Madonuko, mado is nuko, and thus
''mado'' is ''nuko'' (a window is a cat). But, ''mado'' is not ''nuko'' (a window is not a cat), so Mado's assumption is false. (Proof by contradiction)
However, Mado is an element of the set ''nuko''. In other words, Mado is a ''nuko''.

Despite that, it is still ok to use the name Madonuko to refer to Madomado.

== Madoguchi ==
: Main article: [[Madoguchi]]
Madomado also made '''Madoguchi'''. Madoguchi is not a ''mado'', and has nothing to do with ''mado''s.
Instead, Madoguchi is a ''guchi'' (愚痴, Japanese for "complaint"? <del>Or maybe Gu*** handbags?</del>). Except, Madoguchi is not a ''guchi'', and has nothing to do with ''guchi''s. Instead, Madoguchi (<ruby>窓口<rt>まどぐち</rt></ruby>, Japanese for "ticket window", literal meaning "window mouth") is an API server for <del>Mado</del> things related to [[Terra]]. Mado made it so that Repology can redirect dumb entities like Mado to the corresponding package sources hosted on GitHub. The name Madoguchi refers to the [[wikipedia:MARS (ticket reservation system)#Outline|JR green ticket windows]] (''Midori no Madoguchi'', みどりの<ruby>窓口<rt>まどぐち</rt></ruby>) in Japan serving people with all sorts of tickets.

Please note that Madoguchi does not sell tickets for ''mado''s, ''guchi''s (whether the handbags or the complaints), or food (because Mado ate all of them).

Madoguchi is created and maintained by mostly Madomado. Madomado uses special ingredients to make Madoguchi, including oxygen and [[wikipedia:Dihydrogen monoxide parody|dihydrogen monoxide]], illustrated by the following chemical reaction:

4Fe + 3O₂ + 2''n''H₂O → 2Fe₂O₃·''n''H₂O

which results in the product ''hydrated iron(III) oxide'', commonly known as [[wikipedia:Rust (programming language)|rust]].

Ultramarine Linux

2023-06-09T14:34:07Z

Madomado: add section /* Philosophy */

[[Category:Fyra Labs]]
'''Ultramarine Linux''' is a [[wikipedia:Fedora|Fedora]]-based [[wikipedia:Linux|Linux]] distribution designed to be easy to use for everyone, from beginners to tech enthusiasts.
It provides sane-defaults such that "it just works" and minimal configurations are required before users can start using the system.

It comes with 4 editions, namely the Flagship Edition, the GNOME Edition, the Pantheon Edition, and the KDE Plasma Edition.
It also comes with several tweaks preapplied to make initial setup and daily usage seamless.

The Ultramarine Linux distribution is created and maintained by the '''Ultramarine Project''', which is led by '''Cappy Ishihara''' started in 2021, and later acquired by [[Fyra Labs]].

== Editions ==
=== CuteFish ===
Before the release of Ultramarine 37, the [[CuteFish]] Edition was provided but later deprecated due to CuteFish DE's lack of
development and (consequently) its buggy behaviour and broken dependencies. It was then removed and replaced by the KDE Plasma Edition.

=== Flagship ===
The Flagship Edition provides an elegant and simple interface with [[wikipedia:Budgie (desktop environment)|Budgie DE]].
The Budgie version used was packaged in the Ultramarine repository until Ultramarine 37, but it will switch to the one in the Fedora official repositories by Ultramarine 38.

=== GNOME ===
The GNOME Edition provides an intuitive layout with [[wikipedia:GNOME|GNOME]].

=== KDE Plasma ===
The KDE Plasma Edition is provided since the release of Ultramarine 37 and it comes with Latte dock. Its layout is heavily inspired by [[wikipedia:Pop!_OS|Pop!_OS]].
However, Latte dock was removed in Ultramarine 38 due to negative feedback and its buggy behaviour and replaced by the default KDE Plasma theme.

=== Pantheon ===
The Pantheon Edition provides the default desktop of [[wikipedia:Elementary OS|Elementary OS]], Pantheon DE.
The version in [[Terra]] was used since Ultramarine 37 as it was removed from the Fedora 37 repositories.


== Philosophy ==
Ultramarine Project, the team behind the development of Ultramarine Linux and its side projects, has the goal of making Ultramarine Linux an operating system that "just works", meaning customizations and tweaks don't have to be applied manually and things should work out of the box.

In addition to user experience, the infrastructure of the Project is also designed to be developer-friendly. One notable example is [[Terra]], which allows much easier creation and maintenance of RPM packages with the help of automatic updates when compared with Fedora.

== Features ==
Ultramarine Linux comes with a few repositories preinstalled, including [[wikipedia:RPM Fusion|RPM Fusion]], [[wikipedia:Flathub|Flathub]] and [[Terra]].
It also has its own repository with its sources [https://github.com/Ultramarine-Linux/ultramarine-pkgs/ hosted on GitHub] and powered by [[Andaman]].
The packages were hosted separately with their own git repository on a self-hosted GitLab instance and later GitHub, packaged using [[umpkg]].

It uses the [[wikipedia:Anaconda (installer)|Anaconda installer]], but it is said that there will be a custom installer.<ref group="note">The TUI installer <code>libcappy</code> is working but unused.</ref> A welcome program for a better out-of-the-box experience is also planned and it is a work in progress.[https://github.com/Ultramarine-Linux/tauri-welcome]

== History ==
=== The Acquisition of the Ultramarine Project ===
[[Fyra Labs]] acquired the Ultramarine Project on 12 October, 2022 as agreed by both sides which
brought numerous advantages to the development of Ultramarine since both sides had been lacking manpower. After the acquisition, the team started work on numerous projects
which greatly changed the infrastructure and shaped the development of Ultramarine 37, making it arguably the biggest release.

=== The development of umpkg and Andaman ===
: Main Article: [[Andaman]]
Ultramarine had been using Koji for its own repository just like Fedora itself, but it made package maintenance difficult to do with its sheer complexity, which
led to the creation of [[umpkg]] by the Ultramarine Project. It reduces burden on packaging software and uploading them to the Koji server. However,
the sophisticated part (Koji itself) was still there, so a packaging tool was proposed. After the acquisition, the team started to work on
[[Andaman]] (aka. <code>anda</code>), which was originally intended to be a package manager, but later rewritten as a package build toolchain.

== Notes ==
<references group="note" />

User:Jade

2023-06-08T23:25:50Z

Madomado: Use redirection

#REDIRECT [[Jaiden Riordan]]

Madomado

2023-06-07T15:14:56Z

Madomado: add section /* Madoguchi */

Ultramarine Linux

2023-06-07T14:39:21Z

Madomado: init

[[Category:Fyra Labs]]
'''Ultramarine Linux''' is a [[wikipedia:Fedora|Fedora]]-based [[wikipedia:Linux|Linux]] distribution designed to be easy to use for everyone, from beginners to tech enthusiasts.
It comes with 4 editions, namely the Flagship Edition, the GNOME Edition, the Pantheon Edition, and the KDE Plasma Edition.
It comes with several tweaks preapplied to make initial setup and daily usage seamless.

Its development led by '''Cappy Ishihara''' started in 2021, and was later acquired by [[Fyra Labs]].

== Editions ==
=== CuteFish ===
Before the release of Ultramarine 37, Ultramarine provided [[CuteFish]] Edition which was later deprecated due to CuteFish DE's lack of
development and (consequently) its buggy behaviour and later its broken dependencies. It was removed and replaced by the KDE Plasma Edition.

=== Flagship ===
The Flagship Edition provides an elegant and simple interface with [[wikipedia:Budgie (desktop environment)|Budgie DE]].
The Budgie version used was packaged in the Ultramarine repository until Ultramarine 37, but it will switch to the one in the Fedora official repositories by Ultramarine 38.

=== GNOME ===
The GNOME Edition provides an intuitive layout with [[wikipedia:GNOME|GNOME]].

=== KDE Plasma ===
The KDE Plasma Edition is provided since the release of Ultramarine 37 and it comes with Latte dock. Its layout is heavily inspired by [[wikipedia:Pop!_OS|Pop!_OS]].
However, Latte dock will be removed in Ultramarine 38 due to negative feedback and its buggy behaviour.

=== Pantheon ===
The Pantheon Edition provides the default desktop of [[wikipedia:Elementary OS|Elementary OS]], Pantheon DE.
It uses the version in [[Terra]] since Ultramarine 37 as it was removed from the Fedora 37 repositories.


== Features ==
Ultramarine Linux comes with a few repositories preinstalled, including [[wikipedia:RPM Fusion|RPM Fusion]], [[wikipedia:Flathub|Flathub]] and [[Terra]].
It also has its own repository with its sources [hosted on GitHub https://github.com/Ultramarine-Linux/ultramarine-pkgs/] and powered by [[Andaman]].
The packages were hosted separately with their own git repository on a self-hosted GitLab instance and later GitHub, packaged using [[umpkg]].

It uses the [[wikipedia:Anaconda (installer)|Anaconda installer]], but it is said that there will be a custom installer.<ref group="note">The TUI installer <code>libcappy</code> is working but unused.</ref> A welcome program for a better out-of-the-box experience is also planned and it is a work in progress.[https://github.com/Ultramarine-Linux/tauri-welcome]

== History ==
=== The Acquisition of the Ultramarine Project ===
[[Fyra Labs]] acquired the Ultramarine Project on 12 October, 2022 as agreed by both sides which
brought numerous advantages to the development of Ultramarine since both sides had been lacking manpower. After the acquisition, the team started work on numerous projects
which greatly changed the infrastructure and shaped the development of Ultramarine 37, making it arguably the biggest release.

=== The development of umpkg and Andaman ===
: Main Article: [[Andaman]]
Ultramarine had been using Koji for its own repository just like Fedora itself, but it made package maintenance difficult to do with its sheer complexity, which
led to the creation of [[umpkg]] by the Ultramarine Project. It reduces burden on packaging software and uploading them to the Koji server. However,
the sophisticated part (Koji itself) was still there, so a packaging tool was proposed. After the acquisition, the team started to work on
[[Andaman]] (aka. <code>anda</code>), which was originally intended to be a package manager, but later rewritten as a package build toolchain.

== Notes ==
<references group="note" />

Madomado

2023-06-07T12:58:44Z

Madomado: Madomado created the page Madomado for Madomado. The page Madomado is not a ''mado'', has nothing to do with ''mado''s, and it does not talk about ''mado''s.

'''Madomado''', also known as '''Mado''', is not a ''mado'' (<ruby>窓<rt>まど</rt></ruby>, Japanese for "window"), and has nothing to do with ''mado''s.
Mado is responsible for partially the development of [[Ultramarine Linux]].
Consequently, after the acquisition, Mado is a DevOps Engineer in [[Fyra Labs]] and is responsible for numerous projects,
most notably [[Terra]], [[Andaman]], and [[Madoguchi]].

== Madonuko ==

Mado's original character is '''Madonuko'''. Madonuko is not a ''mado'', and has nothing to do with ''mado''s.
Instead it is a ''nuko'' (ぬこ, Japanese slang for "cat").

Madomado is not Madonuko, because if Madomado is Madonuko, mado is nuko, and thus
''mado'' is ''nuko'' (a window is a cat). But, ''mado'' is not ''nuko'' (a window is not a cat), so Mado's assumption is false. (Proof by contradiction)
However, Mado is an element of the set ''nuko''. In other words, Mado is a ''nuko''.

Category:Fyra Labs

2023-06-07T12:34:33Z

Madomado: create

Fyra Labs

2023-06-07T12:34:23Z

Madomado: init

[[Category:Fyra Labs]]

Fyra Labs is a company that strikes to mainly create advanced technology that prioritizes privacy and security. It mainly provides open-source and user-centric products.

== History ==

== Projects ==

=== tauOS ===
[[tauOS]] is an operating system designed to be easy to use. It is still under heavy development.

=== Ultramarine Linux ===
[[Ultramarine Linux]] is an Fedora-based, stable, easy-to-use Linux distribution designed to stay out of your way.
It has a wide range of target users, and comes with several tweaks preapplied to make initial setup and daily usage seamless.

=== Terra ===
[[Terra]] is an RPM repository for software that goes beyond what's available in Fedora.
It is rolling-release and its infrastructure allows software to be easily packaged and maintained afterwards.