AnduinOS APKG package sources.

The following AnduinOS packages explicitly replace or conflict with Ubuntu's official packages. Every Ubuntu package name appears exactly once — there is no overlap.

User cannot install both. Dpkg removes the Ubuntu package at install time.

Defined in anduinos-desktop-core as alternative Depends. The AnduinOS version is listed first (preferred), but the user can apt install ubuntu-X to switch back.

These replace Ubuntu files without removing the Ubuntu package.

anduinos-desktop → anduinos-desktop-core → anduinos-no-snapd triggers:

anduinos-desktop  ──Conflicts──→  ubuntu-desktop
                              →  yaru-theme-gnome-shell
                              →  update-notifier, update-notifier-common
                              →  update-manager, update-manager-core
                              →  ubuntu-release-upgrader-core, ubuntu-release-upgrader-gtk
                              →  whoopsie
      │
      ├─Depends──→ anduinos-desktop-core
      │            └─Depends──→ anduinos-session | ubuntu-session | gnome-session
      │                       → firmware-sof-anduinos | firmware-sof-signed
      │                       → alsa-ucm-conf-anduinos | alsa-ucm-conf
      │                       → anduinos-rime
      │
      ├─Depends──→ anduinos-no-snapd  ──Conflicts──→ snapd
      │
      └─Recommends─→ anduinos-software-properties-common
                   → anduinos-software-properties-gtk  (resolute only)

Total: 23 Ubuntu packages removed or pinned out.

These ship files or declare dependencies without replacing any Ubuntu package.

Each package is built via the GitLab CI pipeline (.gitlab-ci.yml). Packages use the Aiursoft.Apkg.Sdk and can be built locally with:

apkg publish

All external sources must be checked at least once per month to keep packages from falling behind upstream. This section is the step-by-step checklist.

Run through this table each month. If anything has changed upstream, follow the detailed steps in the matching section below.

Three packages clone a git repo and pin to a specific commit hash. Both the commit hash and the .aosproj PackageVersion must be updated together.

# Fluent GTK theme (mirrored on gitlab.aiursoft.com)
git ls-remote https://gitlab.aiursoft.com/mirror/fluent-gtk-theme.git HEAD

# Fluent icon theme (mirrored on gitlab.aiursoft.com)
git ls-remote https://gitlab.aiursoft.com/mirror/fluent-icon-theme.git HEAD

# ALSA UCM Conf (upstream: alsa-project/alsa-ucm-conf)
git ls-remote https://github.com/alsa-project/alsa-ucm-conf.git HEAD

Compare the returned HEAD hash against the pinned commit in each download.sh. If different, an update is available.

For ALSA UCM Conf, check the upstream configure.ac for the version. For Fluent packages, check GitHub releases for the current upstream version (informational — not encoded in PackageVersion).

For each outdated package, update two files:

1. download.sh — update the *_COMMIT variable to the new HEAD hash
2. *.aosproj — bump the Debian revision suffix in <PackageVersion> (e.g. -1 → -2)

Example diff for Fluent GTK theme:

# download.sh
-FLUENT_GTK_COMMIT="9fc5291"
+FLUENT_GTK_COMMIT="a1b2c3d"

# anduinos-fluent-gtk-theme.aosproj
-<PackageVersion>2.0.0~beta1-1+$(SuiteShortName)</PackageVersion>
+<PackageVersion>2.0.0~beta1-2+$(SuiteShortName)</PackageVersion>

cd <package-dir>
apkg publish

firmware-sof-anduinos now derives from Ubuntu's firmware-sof-signed package at build time, then replaces the unpacked SOF payload with a newer Intel sof-bin release tarball. This keeps file ownership, upgrades, and removals under dpkg instead of a post-install rsync.

Visit sof-bin releases and compare the latest tag against SOF_VERSION in firmware-sof-anduinos/download.sh.

Update two files:

# download.sh
-SOF_VERSION="2025.12"
+SOF_VERSION="2026.03"   # update to new release tag

# firmware-sof-anduinos.aosproj
-<PackageVersion>2.0.0~beta1+$(UpstreamVersion)-1+$(SuiteShortName)</PackageVersion>
+<PackageVersion>2.0.0~beta1+$(UpstreamVersion)-2+$(SuiteShortName)</PackageVersion>   # bump the Debian revision

The downloaded Intel tarball and extracted cache under deploy/ are not committed — the CI regenerates them at build time via download.sh.

cd firmware-sof-anduinos
apkg publish

These are resolved dynamically at build time: the resolver (lib/resolve-gnome-ext.py) queries extensions.gnome.org for the best compatible version for each target GNOME Shell version. This means extension code is always up-to-date on every build — no monthly check needed for the extension code itself.

However, two things still need attention:

This file maps Ubuntu suite codenames to GNOME Shell major versions. It must be updated whenever:

• A new Ubuntu release ships (new suite codename + new GNOME Shell version)
• An existing Ubuntu point-release updates its GNOME Shell version (rare)

To check:

# For each supported suite, check what GNOME Shell version Ubuntu ships:
apt-cache policy gnome-shell  # (run on each supported Ubuntu release)

If a mismatch is found, update lib/gnome-versions.sh:

declare -A GNOME_TARGETS=(
    [noble]=46      # Ubuntu 24.04 LTS
    [questing]=49   # Ubuntu 25.10
    [resolute]=50   # Ubuntu 26.04 LTS
    # ^ update or add entries as needed
)

Then CI rebuilds all 19 extension packages automatically — the new GNOME version will be picked up by the resolver on the next build.

Each extension's .aosproj uses a unified <PackageVersion> of 2.0.0~beta2-1+$(SuiteShortName). Bump the Debian revision suffix (e.g. -1 → -2) when packaging changes. The resolver fetches the latest extension code at build time, so the extension code itself is always up-to-date regardless of the package version.

-<PackageVersion>2.0.0~beta2-1+$(SuiteShortName)</PackageVersion>
+<PackageVersion>2.0.0~beta2-2+$(SuiteShortName)</PackageVersion>

gnome-shell-extension-desktop-icons-ng-anduinos explicitly conflicts with Ubuntu's gnome-shell-extension-desktop-icons-ng (same UUID ding@rastersoft.com). It also carries a custom metadata.patch in its deploy directories. When the upstream DING extension releases a new version, verify the patch still applies cleanly.

Six packages derive from upstream .deb packages at build time via UpstreamUrl:

These are rebuilt by CI and pull the latest upstream source at build time, so the upstream base stays up-to-date. firmware-sof-anduinos still needs the separate Intel release check from section C.

Monthly check: confirm the mirrors (https://mirror.aiursoft.com/ubuntu and Mozilla APT) are syncing correctly. No code changes needed unless the upstream changes the package name or the mirror URL changes.

These URLs are not on a monthly schedule, but should be reviewed whenever infrastructure changes:

When doing a full monthly triage, follow this order — earlier packages are dependencies of later ones:

1. Fluent icon theme + Fluent GTK theme (no deps)
2. ALSA UCM Conf + SOF firmware (alsa-ucm-conf depends on nothing; SOF recommends alsa-ucm-conf but doesn't build-depend on it)
3. GNOME Shell extension version audits (no cross-deps)
4. GNOME version map update (triggers extension rebuilds)
5. Ubuntu-derived packages (no cross-deps; build picks up latest)
6. Meta-packages — rebuild last (anduinos-desktop, anduinos-desktop-core, anduinos-gnome-extensions, anduinos-theme)

For each updated package, push to master — CI runs apkg publish && apkg push automatically.