Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Directory out of date error #95

Closed
richard-muvirimi opened this issue May 29, 2022 · 1 comment · Fixed by #96
Closed

Directory out of date error #95

richard-muvirimi opened this issue May 29, 2022 · 1 comment · Fixed by #96
Assignees
Labels
type:bug Something isn't working.
Milestone

Comments

@richard-muvirimi
Copy link
Contributor

richard-muvirimi commented May 29, 2022

Describe the bug

I get a directory out of date using the action for some strange reason. I did look into the possible causes and this Stackover Issue seems to address the issue.

Additional context

This might be an svn related issue refusing to commit files because of a date mismatch. using bash only, I resolved this by just running svn update before the commit. I have not added the steps to reproduce as it happens on a fresh commit, might be times from git. Have attached a snippet of the error message.

➤ Committing files...
Adding         tags/1.0.4
svn: E155011: Commit failed (details follow):
svn: E155011: Directory '/home/runner/svn-force-reinstall/tags/1.0.4' is out of date
svn: E175014: Precondition on '/!svn/rvr/2733523/force-reinstall/trunk' failed
Error: Process completed with exit code 1.
@richard-muvirimi richard-muvirimi changed the title Directory out of date Directory out of date error May 29, 2022
@vikrampm1 vikrampm1 moved this to Incoming in Open Source Practice May 30, 2022
@vikrampm1 vikrampm1 moved this from Incoming to In Progress in Open Source Practice May 30, 2022
@vikrampm1 vikrampm1 added the type:bug Something isn't working. label May 30, 2022
@jeffpaul jeffpaul moved this from In Progress to In Review in Open Source Practice Jun 2, 2022
@jeffpaul jeffpaul added this to the Future Release milestone Jun 2, 2022
@dinhtungdu
Copy link
Contributor

In theory, we don't need to run svn update but if there are commits from other plugins that chime in, we'll need to sync again before committing.

Repository owner moved this from In Review to Merged in Open Source Practice Jun 2, 2022
@jeffpaul jeffpaul modified the milestones: Future Release, 2.2.0 Jun 3, 2022
@dinhtungdu dinhtungdu modified the milestones: 2.2.0, 2.1.1 Aug 11, 2022
@vikrampm1 vikrampm1 moved this from Merged to Done/Released in Open Source Practice Nov 24, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type:bug Something isn't working.
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

4 participants