Bug: dotOrg deployment script seems to be breaking on specific themes.

[vcanales]

trafficstars

Quick summary

The dotOrg deployment script has started failing a few weeks back, when ran from trunk automatically. It seems to be related to a few themes, although it might not be a theme-specific problem. In both of the cases below, the failure was caused by I theme that was not the one being merged with changes.

# https://github.com/Automattic/themes/actions/runs/10369537313/job/28705485018#step:3:88
Updated to revision 238646.
A         deploy/expo/1.2
➤ Copying theme 'expo/' version '1.2' to svn repository... 
sed: can't read s/, auto-loading-homepage//g: No such file or directory
svn: E205001: Try 'svn help delete' for more information
svn: E205001: Not enough arguments provided
➤ Committing files...
svn: E195023: Commit failed (details follow):
svn: E195023: Changing directory '/home/runner/work/themes/themes/deploy/expo/1.2' is forbidden by the server
svn: E175013: Access to '/!svn/rvr/23[86](https://github.com/Automattic/themes/actions/runs/10369537313/job/28705485018#step:3:87)46/expo/1.0' forbidden
Commit failed.

# https://github.com/Automattic/themes/actions/runs/10369537313/job/28705485018#step:3:52
Updated to revision 237096.
A         deploy/maverick/1.0.1
➤ Copying theme 'maverick/' version '1.0.1' to svn repository... 
sed: can't read s/, auto-loading-homepage//g: No such file or directory
svn: E205001: Try 'svn help delete' for more information
svn: E205001: Not enough arguments provided
➤ Committing files...
svn: E195023: Commit failed (details follow):
svn: E195023: Changing directory '/home/runner/work/themes/themes/deploy/maverick/1.0.1' is forbidden by the server
svn: E175013: Access to '/!svn/rvr/237096/maverick/1.0.0' forbidden
Commit failed.

Steps to reproduce

Trigger the dotOrg deployment on trunk.

A clear and concise description of what you expected to happen.

No response

What actually happened

No response

Impact

All

Available workarounds?

No but the platform is still usable

If the above answer is "Yes...", outline the workaround.

No response

Platform (Simple and/or Atomic)

No response

Logs or notes

No response