[Bug]: Nextcloud Updater requires write permission for python

⚠️ This issue respects the following points: ⚠️

• This is a bug, not a question or a configuration/webserver/proxy issue.
• This issue is not already reported on Github OR Nextcloud Community Forum (I've searched it).
• Nextcloud Server is up to date. See Maintenance and Release Schedule for supported versions.
• I agree to follow Nextcloud's Code of Conduct.

Bug description

Hello dear developers,

Nextcloud Server Version 32.0.0

Issue:
I try to update the server to 32.0.1, via CLI with "sudo -u own-cloud */php/8.3/bin/php -d memory_limit=6096M */updater.phar"

Error:
Nextcloud Updater - version: v32.0.0beta1-13-gf6e4a9e dirty

Current version is 32.0.0.

Update to Nextcloud 32.0.1 available. (channel: "stable")
Following file will be downloaded automatically: https://download.nextcloud.com/server/releases/nextcloud-32.0.1.zip
Open changelog ↗

Steps that will be executed:
[ ] Check for expected files
[ ] Check for write permissions
[ ] Create backup
[ ] Downloading
[ ] Verify integrity
[ ] Extracting
[ ] Enable maintenance mode
[ ] Replace entry points
[ ] Delete old files
[ ] Move new files in place
[ ] Done

Start update? [y/N] y

Info: Pressing Ctrl-C will finish the currently running step and then stops the updater.

[✔] Check for expected files
[✘] Check for write permissions failed
The following places can not be written to:
python3
python
python3.10
python3
python
python3.10
python3
python
python3.10

Update failed. To resume or retry just execute the updater again.

How can I mitigate this? All permissions and ownerships are set properly. Python should as I researched not be a requirement for the update process. Is this right?

Thank you in advance for your help and development in general!

Best

Steps to reproduce

I try to update the server to 32.0.1, via CLI with "sudo -u own-cloud */php/8.3/bin/php -d memory_limit=6096M */updater.phar"

Expected behavior

Update properly via CLI.

Nextcloud Server version

32

Operating system

Debian/Ubuntu

PHP engine version

PHP 8.3

Web server

Nginx

Database engine version

MariaDB

Is this bug present after an update or on a fresh install?

Updated from a MINOR version (ex. 32.0.1 to 32.0.2)

Are you using the Nextcloud Server Encryption module?

None

What user-backends are you using?

• Default user-backend (database)
• LDAP/ Active Directory
• SSO - SAML
• Other

Configuration report

List of activated Apps

Nextcloud Signing status

Nextcloud Logs

Additional info

No response

The payload names no source file or test; start at the write-permission check used by updater.phar and reproduce the CLI update command under the own-cloud user. Trace why the check reports python, python3, and python3.10 paths, then add or update coverage so a normal 32.0.0 to 32.0.1 CLI update no longer fails on unrelated Python paths.