balbes150

do not confuse the general testing process on a clean system and the installation of any unnecessary junk that is not needed for the selected specific image (platform) into one pile.

Why install something that is not needed???? The correct system check is to record a clean image and carry out all the steps strictly according to the initial instructions, on a completely clean \ new system.

IMHo - all these checks and the "problems" found in patches have no practical use. A practical test of applying a patch to the source code, with a detailed indication of exactly which part of the patch code is not applied. You can see an example in the Libreelec build system. There is a detailed patch overlay log and you can immediately see which piece of patch code is problematic. This is especially true for large patches with a large number of fix points in different places. Now there is a patch overlay log in the build log, and there is only scanty information there, which makes it difficult to understand where the problem is in patches, especially if there are many changes in one file.

Please note that these are packages that he is trying to install into the host system, i.e. these dependencies are written somewhere as mandatory for the host system where the build is launched. The assembly with GIT-Master works fine on the same host system, i.e. all the packages and dependencies necessary for the assembly system to work are already installed and the assembly works without problems. But the NEXT version is trying to install all this extra junk. You can easily reproduce it yourself. Take any ARM device (power and other parameters do not matter), run for example from SD\USB a ready-made Armbian Jammy image for this device and see what happens when you try to start building any image.

I looked at the table by the link. I don't understand what practical use it is? "No description of mbox" - has no use. "rebase" - it is not clear why. the rest of the items are the same. does not do the main thing - does not check the error when using patches https://rpardini.github.io/linux/armbian-next-media-6.1-20221220.html

I tried armbian-next to run a native build (on an ARM device), and got errors. Why is a bunch of unnecessary shit being put on ARM (snap, gcc-riscv, etc.)? 👉] Reading package lists... [👉] Building dependency tree... [👉] Reading state information... [👉] Package ccze is not available, but is referred to by another package. [👉] This may mean that the package is missing, has been obsoleted, or [👉] is only available from another source [👉] Package python3-pip is not available, but is referred to by another package. [👉] This may mean that the package is missing, has been obsoleted, or [👉] is only available from another source [👉] Package distcc is not available, but is referred to by another package. [👉] This may mean that the package is missing, has been obsoleted, or [👉] is only available from another source [👉] No apt package "axel", but there is a snap with that name. [👉] Try "snap install axel" [👉] No apt package "tree", but there is a snap with that name. [👉] Try "snap install tree" [👉] E: Package 'distcc' has no installation candidate [👉] E: Package 'python3-pip' has no installation candidate [👉] E: Unable to locate package python2-dev [👉] E: Package 'ccze' has no installation candidate [👉] E: Unable to locate package colorized-logs [👉] E: Unable to locate package tree [👉] E: Unable to locate package pbzip2 [👉] E: Unable to locate package axel [👉] E: Unable to locate package crossbuild-essential-armel [👉] E: Unable to locate package crossbuild-essential-amd64 [👉] E: Unable to locate package gcc-riscv64-linux-gnu [👉] --> 🧽 78: 3365 - 3365 - 3365: hBE: trap: main_trap_handler [ ERR and 100 trap_manager_error_handled: short_stack:/home/user/armbian-build-next/lib/functions/logging/runners.sh:186 ] [💥] 👆👆👆 Showing logfile above 👆👆👆 [ /home/user/armbian-build-next/.tmp/logs-599221b8-4094-41cf-af68-4d18190ab396/004.000.prepare_host.log ] [💥] Error occurred in main shell [ code 100 at /home/user/armbian-build-next/lib/functions/logging/runners.sh:186 run_host_command_logged_raw() --> ./lib/functions/logging/runners.sh:186 run_host_command_logged() --> ./lib/functions/logging/runners.sh:169 host_apt_get() --> ./lib/functions/logging/runners.sh:139 host_apt_get_install() --> ./lib/functions/logging/runners.sh:132 install_host_side_packages() --> ./lib/functions/host/host-utils.sh:60 install_host_dependencies() --> ./lib/functions/host/prepare-host.sh:291 prepare_host() --> ./lib/functions/host/prepare-host.sh:111 do_with_logging() --> ./lib/functions/logging/logging.sh:112 main_default_build_single() --> ./lib/functions/main/default-build.sh:27 cli_standard_build_run() --> ./lib/functions/cli/cli-build.sh:16 armbian_cli_run_command() --> ./lib/functions/cli/utils-cli.sh:121 cli_entrypoint() --> ./lib/functions/cli/entrypoint.sh:154 main() --> ./compile.sh:52