Question when trying to build AnduinOS 2.0 ISO

[badwahaha]

There's no discusstion forum at AiursoftWeb/AnduinOS-2. So I post the question here.

The variable TARGET_PACKAGE_REMOVE is exported in argu.sh with comment "Packages will be uninstalled during the installation process". However the only reference i can find is in "Generating manifest for filesystem-desktop" block in build.sh
for pkg in $TARGET_PACKAGE_REMOVE; do
sudo sed -i "/^$pkg /d" image/casper/filesystem.manifest-desktop
done
Where is the command to remove the packages in TARGET_PACKAGE_REMOVE? If i add firefox-esr and transmission-gtk in the list, will they be removed during installation as well?

[badwahaha]

After asking AI, the conclusion is that Ubiquity itself will remove the packages.

Firefox seems to be installed via package firefox-anduinos. I can't find the transmission package name, maybe contained in anduinos-desktop-apps?

Will they be removed by Ubiquity if I put them in the TARGET_PACKAGE_REMOVE list?

[Anduin2017]

Yes you are correct. It's ubiquity handling this.

Every package you mentioned in TARGET_PACKAGE_REMOVE WILL be removed after installing by ubiquity.

[badwahaha]

BTW: it says SSL handshake failed Error code 525 when visiting https://packages.aiursoft.com/

[Anduin2017]

Oh... I made a mistake.

There should never be packages.aiursoft.com

The correct value is always packages.anduinos.com.

Please help me correct.

[badwahaha]

I have added my own mod in the mods folder. Task of my own mod is to install necessary apps from the repository, install local stored deb apps, restore app config files, config customized keyboard shortcut and so on.

Most of the script were created by AI. There were always different errors and the make process broke. After talking with AI and updating the script, I have to re-run the make process from very beginning. It was quite time-consuming consider my 10-years old laptop. So far I haven't ever created successully the ISO.

Is it possible to skip some already successfully finished steps in the script? For example, debootstrap is time-consuming and has been finished without any problem. I tried to comment the download_base_system line in build.sh. But again errors like following. (I temporarily commented the exit 1 line in makefile since i am running AnduinOS 1.4.2)

Error: Host codename 'questing' != target 'resolute'
Build machine must run the same Ubuntu release as the target ISO.
[MAKE] All required packages are already installed.
[MAKE] Building current language...
[ OK ] Bind signal...
[ OK ] Bind signal succeeded
[ OK ] Cleaning up previous build...
umount: new_building_os/sys: not mounted.
umount: new_building_os/sys: not mounted.
umount: new_building_os/proc: not mounted.
umount: new_building_os/proc: not mounted.
umount: new_building_os/dev: not mounted.
umount: new_building_os/dev: not mounted.
umount: new_building_os/run: not mounted.
umount: new_building_os/run: not mounted.
[ OK ] Clean up build artifacts succeeded
[ OK ] Reloading systemd daemon...
[ OK ] Reload systemd daemon succeeded
[ OK ] Mounting /dev /run from host to build dir...
mount: new_building_os/dev: mount point does not exist.
dmesg(1) may have more information after failed mount system call.
[ OK ] Umount before exit...
umount: /home/xx/Downloads/AnduinOS-2-master/new_building_os/sys: no mount point specified.
umount: /home/xx/Downloads/AnduinOS-2-master/new_building_os/sys: no mount point specified.
umount: /home/xx/Downloads/AnduinOS-2-master/new_building_os/proc: no mount point specified.
umount: /home/xx/Downloads/AnduinOS-2-master/new_building_os/proc: no mount point specified.
umount: /home/xx/Downloads/AnduinOS-2-master/new_building_os/dev: no mount point specified.
umount: /home/xx/Downloads/AnduinOS-2-master/new_building_os/dev: no mount point specified.
umount: /home/xx/Downloads/AnduinOS-2-master/new_building_os/run: no mount point specified.
umount: /home/xx/Downloads/AnduinOS-2-master/new_building_os/run: no mount point specified.
[ OK ] Umount before exit succeeded
make: *** [makefile:65: current] Error 32
=== Cleaning up mounts ===
=== Removes the custom sudoers block ===
removed '/etc/sudoers.d/ma-build'
Done

[samwhelp]

@badwahaha

I'm writing a reply, it will take some time.

[samwhelp]

@badwahaha

About this error message

Error: Host codename 'questing' != target 'resolute'
Build machine must run the same Ubuntu release as the target ISO.

from the makefile:Code Snippet.

	@host=$$(lsb_release -cs); \
	target=$$(grep -oP 'export TARGET_UBUNTU_VERSION="\K[^"]+' args.sh); \
	if [ "$$host" != "$$target" ]; then \
	  echo "Error: Host codename '$$host' != target '$$target'"; \
	  echo "Build machine must run the same Ubuntu release as the target ISO."; \
	  exit 1; \
	fi

and you mentioned

(I temporarily commented the exit 1 line in makefile since i am running AnduinOS 1.4.2)

Suggestion

When compiling AnduinOS-2, it is recommended that you build the system at the same version level.

Solution 1

Therefore, it is recommended that you first install a new Ubuntu 26.04 or AnduinOS 2.0,

and then compile AnduinOS-2 in this environment(Host) to create an ISO file.

Alternatively, you can use Docker to create a new Ubuntu 26.04 environment to compile AnduinOS-2.

Solution 2

If you want to compile AnduinOS-2 on AnduinOS 1.4 (Ubuntu 25.10),

you need to install a newer version of debootstrap to support Ubuntu 26.04 (resolute).

However, this method may carry the risk of compilation failure.
For example:GRUB; because the GRUB used to compile the ISO uses the host's GRUB.

The following are the reference instructions to manually install debootstrap.

Manually install debootstrap

run to download debootstrap_1.0.142ubuntu1_all.deb

wget -c 'https://archive.ubuntu.com/ubuntu/pool/main/d/debootstrap/debootstrap_1.0.142ubuntu1_all.deb'

run to install debootstrap_1.0.142ubuntu1_all.deb

sudo dpkg -i debootstrap_1.0.142ubuntu1_all.deb

show

Selecting previously unselected package debootstrap.
(Reading database ... 126957 files and directories currently installed.)
Preparing to unpack debootstrap_1.0.142ubuntu1_all.deb ...
Unpacking debootstrap (1.0.142ubuntu1) ...
dpkg: dependency problems prevent configuration of debootstrap:
 debootstrap depends on distro-info; however:
  Package distro-info is not installed.

dpkg: error processing package debootstrap (--install):
 dependency problems - leaving unconfigured
Processing triggers for man-db (2.13.1-1) ...
Errors were encountered while processing:
 debootstrap

then run to install missing package

sudo apt-get install -f

show

Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Correcting dependencies... Done
Solving dependencies... Done
The following additional packages will be installed:
  distro-info
Suggested packages:
  shunit2
The following NEW packages will be installed:
  distro-info
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
1 not fully installed or removed.
Need to get 20.3 kB of archives.
After this operation, 81.9 kB of additional disk space will be used.
Do you want to continue? [Y/n]

run to view version

debootstrap --version

show

debootstrap 1.0.142ubuntu1

check

file /usr/share/debootstrap/scripts/resolute

show

/usr/share/debootstrap/scripts/resolute: symbolic link to gutsy

This version of debootstrap supports resolute (ubuntu 26.04).

Next

I will then write another reply to explain another issue you mentioned, which will take some time.

[samwhelp]

@badwahaha

Regarding what you mentioned

Is it possible to skip some already successfully finished steps in the script? For example, debootstrap is time-consuming and has been finished without any problem.

Currently, it appears that AnduinOS-2's script creation mechanism does not include this feature.

However, you can copy build.sh to multiple files and then rewrite it into individual key steps.

This allows you to manually break it down into different steps for execution.

Execution process overview

Here's a general description of the key execution flow.

First, a new basic system will be created using debootstrap.

Next, the scripts to be executed in the chroot environment will be copied to the new_building_os/root/mods directory.

You can refer to the code snippet.

    sudo cp -r $SCRIPT_DIR/mods new_building_os/root/mods
    sudo cp $SCRIPT_DIR/args.sh   new_building_os/root/mods/args.sh
    sudo cp $SCRIPT_DIR/shared.sh new_building_os/root/mods/shared.sh

Next, new_building_os/root/mods/install_all_mods.sh will be executed in the chroot environment.

    sudo chroot new_building_os /usr/bin/env DEBIAN_FRONTEND=${DEBIAN_FRONTEND:-readline} /root/mods/install_all_mods.sh -

The script new_building_os/root/mods/install_all_mods.sh will execute each of the various mods.

After all mods completes its execution in the chroot environment,

it exits chroot,

and then completes the subsequent actions, packaging the new system into an ISO file.

Execute in different steps

Therefore, you can rewrite the scripts to do different key actions.

[samwhelp]

Tricks for developing mods

Develop Mods in chroot

You can first set up a new system, then enter the chroot environment to execute your various mods scripts.

• Example: demo-develop-mods-in-chroot

Develop Mods in Host

Or you can execute the mods script directly in the host environment.

• Example: demo-develop-mods-in-host

The difference between the examples demo-develop-mods-in-chroot and demo-develop-mods-in-host lies in the different folder hierarchy placed in args.sh and shared.sh.

Actually, AnduinOS-2 can be rewritten so that args.sh and shared.sh are placed in the same folder hierarchy in both the Host and chroot environments.

Tricks

We will use the example of demo-develop-mods-in-host to illustrate the tricks for developing single mods.

Let's first look at the complete content of the script demo-develop-mods-in-host/mods/20-demo-develop/install.sh.

#!/usr/bin/env bash


set -e                  # exit on error
set -o pipefail         # exit on pipeline error
set -u                  # treat unset variable as error


BASE_DIR_PATH="$(dirname "$(readlink -f "$0")")"
LIBS_DIR_PATH="$(realpath "$BASE_DIR_PATH/../..")"


##
## * uncomment these two line when developing
## * comment these two line when releasing
##
source "$LIBS_DIR_PATH/args.sh"
source "$LIBS_DIR_PATH/shared.sh"




print_ok "Demo Installing..."

apt install -y \
    nano \
    micro \
    vim \
    neovim \
    --no-install-recommends
judge "Install extra packages"

By simply adding the following lines, you can develop and test mods independently in the host environment.

BASE_DIR_PATH="$(dirname "$(readlink -f "$0")")"
LIBS_DIR_PATH="$(realpath "$BASE_DIR_PATH/../..")"


##
## * uncomment these two line when developing
## * comment these two line when releasing
##
source "$LIBS_DIR_PATH/args.sh"
source "$LIBS_DIR_PATH/shared.sh"

Adding the above lines allows you to test the process by executing sudo ./install.sh or sudo bash install.sh.

If you want to compile AnduinOS-2, you need to comment out the two lines starting with "source" and change them as follows.

BASE_DIR_PATH="$(dirname "$(readlink -f "$0")")"
LIBS_DIR_PATH="$(realpath "$BASE_DIR_PATH/../..")"


##
## * uncomment these two line when developing
## * comment these two line when releasing
##
#source "$LIBS_DIR_PATH/args.sh"
#source "$LIBS_DIR_PATH/shared.sh"

[samwhelp]

@badwahaha

I refactored the code based on AnduinOS-2 and created a sample called demo-build-steps.

Implementing the concept I mentioned in my previous reply.

The process of creating an ISO file can be broken down into several key steps for execution.

Of course, the original single-step process for creating a complete ISO file is also available.

This sample is provided solely for learning purposes.

Perhaps this sample can help you understand these concepts.

Link

• live-custom-ubuntu-from-scratch
• AnduinOS
• AnduinOS-2