[merge] from unstable into stable

support/sherpa-manager.source

@@ -7765,11 +7765,11 @@ GenerateReportFooter()
 		fi
 
 		if [[ -e "$REPORT_FLAGS_PATH"/result-aborted ]]; then
-			DisplayAsIndentQuotedInfoItem "($(TextBrightRed aborted))" 'last action was aborted'
+			DisplayAsIndentQuotedInfoItem "($(TextBrightRed aborted))" 'previous action was aborted'
 		fi
 
 		if [[ -e "$REPORT_FLAGS_PATH"/result-failed ]]; then
-			DisplayAsIndentQuotedInfoItem "($(TextBrightRed failed))" 'last action failed'
+			DisplayAsIndentQuotedInfoItem "($(TextBrightRed failed))" 'previous action failed'
 		fi
 
 		if [[ -e "$REPORT_FLAGS_PATH"/status-inactive ]]; then
@@ -7821,7 +7821,7 @@ GenerateReportFooter()
 		fi
 
 		if [[ -e "$REPORT_FLAGS_PATH"/result-ok ]]; then
-			DisplayAsIndentQuotedInfoItem "($(TextBrightGreen OK))" 'last action was successful'
+			DisplayAsIndentQuotedInfoItem "($(TextBrightGreen OK))" 'previous action was successful'
 		fi
 
 		if [[ -e "$REPORT_FLAGS_PATH"/status-active ]]; then
@@ -9574,7 +9574,7 @@ _QPKG:uninstall_()
 		z=$?
 
 		if [[ $z -eq 0 ]]; then
-			# ALERT: beware of `qpkg_cli --remove`, it removes the QPKG installation path around 10-20 seconds after execution. If sherpa has moved-on and starts an install, `qpkg_cli` will remove the newly created QPKG installation path partway through the installation. So, check if QPKG is to be installed: if this is the case, don't use `qpkg_cli --remove`.
+			# WARNING: beware of `qpkg_cli --remove`, it removes the QPKG installation path around 10-20 seconds after execution. If sherpa has moved-on and starts an install, `qpkg_cli` will remove the newly created QPKG installation path partway through the installation. So, check if QPKG is to be installed: if this is the case, don't use `qpkg_cli --remove`.
 			[[ -e /sbin/qpkg_cli ]] && ! QPKGs-ACinstall-to.Exist "$qpkg_name" && /sbin/qpkg_cli --remove "$qpkg_name" &> /dev/null
 			SaveActionResultToLog QPKG "$qpkg_name" uninstall '' ok
 			/sbin/rmcfg "$qpkg_name" -f /etc/config/qpkg.conf
@@ -10445,7 +10445,7 @@ ClearQpkgAppCenterNotifier()
 QpkgServiceResultWasOk()
 	{
 
-	# Returns true if last action for this package is `ok`.
+	# Returns true if previous action for this package is `ok`.
 
 	# Input:
 	#   $qpkg_name (global) = QPKG name
@@ -11243,7 +11243,7 @@ QpkgGetServiceAction()
 	#   $qpkg_name (global, default) = target QPKG name.
 
 	# Output:
-	#   $stdout = last action requested.
+	#   $stdout = previous action requested.
 	#   $? = 0 (found), !0 (not-found)
 
 	local a=${1:-${qpkg_name:?${FUNCNAME[0]}'()': undefined package name}}

workshop/ideas.txt

@@ -1,5 +1,3 @@
-* Show currently selected git branch with 'enabled' and 'autoupdate' settings.
-
 * Check OOM killed pids against inactive daemons and report as-such on status report.
 
 * Takes 3.5 to 6 seconds to build QPKG states on Laura.

workshop/issues.txt

@@ -1,9 +1,5 @@
 Observed issues:
 
-	* Bazarr can take 4-5 minutes to start.
-		- 'start' shows as failed but daemon is running.
-		- Need to extend timeouts for this QPKG
-
 	* 'sherpa enable-auto-update active' is not running 'enable-auto-update' action.
 
 	* Near the end of installing IPKs, monitored download path can remain at non-zero size while packages complete installation.