Skip to content
This repository has been archived by the owner on Aug 31, 2023. It is now read-only.

馃悰 Windows: "EPERM: operation not permitted, unlink rome.exe" #4554

Open
1 task done
elijaholmos opened this issue Jun 7, 2023 · 3 comments
Open
1 task done
Labels
S-To triage Status: user report of a possible bug that needs to be triaged

Comments

@elijaholmos
Copy link

Environment information

See #4046

What happened?

My previous issue, #4046, was closed as completed; however, I continue to face this issue.

I've noticed that Prisma recently published a release which addressed a similar problem. The issue reference is prisma/prisma#14626

Expected result

See #4046

Code of Conduct

  • I agree to follow Rome's Code of Conduct
@elijaholmos elijaholmos added the S-To triage Status: user report of a possible bug that needs to be triaged label Jun 7, 2023
@ematipico
Copy link
Contributor

Does this issue occur when you want to upgrade from 10 to 11? Or also from 11 to 12?

@elijaholmos
Copy link
Author

Yeah, I'm using the latest version of Rome right now. When trying to upgrade (or downgrade) versions with yarn, I get the EPERM error.

@ematipico
Copy link
Contributor

Thank you. I don't have a Windows machine, and usually don't use yarn.

I might have understood what the issue is, but I don't know how to fix it yet. Hopefully I will find something. Sorry if that bothers your work environment, it's good that at least there's a workaround

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
S-To triage Status: user report of a possible bug that needs to be triaged
Projects
None yet
Development

No branches or pull requests

2 participants