You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I noticed this when updating texlive_core, which uses both a patchset and a PATCH function. The PATCH function failed (because it needs autoconf 2.72 apparently) and HaikuPorter resetted the internal git repo back to ORIGIN, effectively discarding the patchset commits. The flag.patchset file was not deleted, however, so that results in an inconsistent state.
Do we need a new tag that is applied after the patchset and reset to that instead if it is present, or could we just reset to HEAD instead when the PATCH function fails? If the resetting to ORIGIN is retained, at least the flag.patchset should be removed in this case.
The text was updated successfully, but these errors were encountered:
I noticed this when updating
texlive_core
, which uses both a patchset and a PATCH function. The PATCH function failed (because it needs autoconf 2.72 apparently) and HaikuPorter resetted the internal git repo back to ORIGIN, effectively discarding the patchset commits. Theflag.patchset
file was not deleted, however, so that results in an inconsistent state.Do we need a new tag that is applied after the patchset and reset to that instead if it is present, or could we just reset to HEAD instead when the PATCH function fails? If the resetting to ORIGIN is retained, at least the
flag.patchset
should be removed in this case.The text was updated successfully, but these errors were encountered: