bump(x11/thunderbird): 128.8.0

[TomJo2000]

closes #23615

Trying to figure out what actually failed.
Did a test build of aarch64 locally and it worked.

[licy183]

Trying to figure out what actually failed. Did a test build of aarch64 locally and it worked.

Possible due to out of disk space.

[TomJo2000]

Unfortunately the build log in the auto update workflow is too long by the time it gets to thunderbird so I don't have any way to confirm that.

[twaik]

Probably we should make cleanup threshold bigger. Or make it force cleanup without checking for disk space, anyways CI does not reuse build folders.

[TomJo2000]

Probably we should make cleanup threshold bigger. Or make it force cleanup without checking for disk space, anyways CI does not reuse build folders.

I don't think it's an issue of the threshold itself.
That is mostly guesswork.
But shouldn't it also automatically do a cleaning run before build a big package?

termux-packages/scripts/big-pkgs.list

Line 16 in ce2ccbf

thunderbird

termux-packages/scripts/updates/utils/termux_pkg_upgrade_version.sh

Lines 112 to 134 in ce2ccbf

	local big_package=false
	while IFS= read -r p; do
	if [[ "${p}" == "${TERMUX_PKG_NAME}" ]]; then
	big_package=true
	break
	fi
	done < "${TERMUX_SCRIPTDIR}/scripts/big-pkgs.list"
	if [[ "${big_package}" == "true" ]]; then
	"${TERMUX_SCRIPTDIR}/scripts/run-docker.sh" ./clean.sh
	fi
	if ! "${TERMUX_SCRIPTDIR}/scripts/run-docker.sh" ./build-package.sh -C -a "${TERMUX_ARCH}" -i "${TERMUX_PKG_NAME}"; then
	if [[ "${big_package}" == "true" ]]; then
	"${TERMUX_SCRIPTDIR}/scripts/run-docker.sh" ./clean.sh
	fi
	git checkout -- "${TERMUX_PKG_BUILDER_DIR}"
	termux_error_exit "ERROR: failed to build."
	fi
	if [[ "${big_package}" == "true" ]] || [[ "${force_cleanup}" == "true" ]]; then
	"${TERMUX_SCRIPTDIR}/scripts/run-docker.sh" ./clean.sh
	fi

I'm not sure that that is working as intended.
I'll check if I can pull the raw logs from the CI run.

[TomJo2000]

Trying to figure out what actually failed. Did a test build of aarch64 locally and it worked.

Possible due to out of disk space.

Call it a hunch.
I think you were completely right about that.

[twaik]

Wait a sec. For some reason I put the check in the wrong place. Weird thing. I'll move it.

[TomJo2000]

Wait a sec. For some reason I put the check in the wrong place. Weird thing. I'll move it.

Open a PR, I have some other ideas.
Like adding a print out to clean.sh stating that it is being run, and conditionally what triggered it (e.g. big packages/cleanup flag)