we are using Epic Games P4 proxy to get our own version of their engine source. To do so we have a workspace pointing to the virtual stream release-latest-minimal. This stream has parents called release-latest and release-4.25.3 (all virtual) being childs of release-4.25, which is the most recent released version. The child streams of the release stream lock themselves to the last stable CL by using the ChangeView field in the stream spec.
We have the following problem with this:
- We have our workspace which was synced to a previous version (4.25.1 at that point) where the ChangeView field of the stream spec was pointing to a different CL
- Now we want to sync the changes to upgrade to 4.25.3 by syncing release-latest-minimal which has a new CL in its ChangeView field
- Doing a normal sync does nothing, no files are updated
- Doing a force sync pulls all files again, but also only until the revision of the CL before the change. So we don't get any new revisions since the last sync
This could potentially be resolved by generating a new workspace for each version, because a new workspace of release-latest-minimal will sync all revision up to the current CL mentioned in ChangeView. But this would be very inconvenient because it would require us to download way more data than necessary. So our question would be if there are any known bugs or issues with this? Are there any hints/tips how we can solve this? We want to find out if this is a problem of P4V or Epic's proxy.
PS: We attached the client and stream spec. The current ChangeView wants to sync to CL 13942748 but we only ever get CL 13594126 (the one from sync before this, version 4.25.1).
Thanks and cheers,