Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • P pleroma-support
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 40
    • Issues 40
    • List
    • Boards
    • Service Desk
    • Milestones
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • PleromaPleroma
  • pleroma-support
  • Issues
  • #81
Closed
Open
Issue created Nov 09, 2022 by a a@Ninmi

Accidental root pull when updating

So after probably re-reading the update instructions a couple of times, I still seem to have managed to fail on the first step and pull changes as (presumably) root on my previous update.

First I chowned the .git directory back to pleroma:pleroma as instructed in the #pleroma channel and I was allowed to pull, but the pull failed to unlink and create a bunch of files, breaking the web front end. I then asked if it's okay to just chown the entire pleroma directory, and was given green light (later realizing this was actually a step in the install guide). The problem is now that even after performing get reset --hard to get rid of unnecessary changes (as instructed by #pleroma), I suspect the ownership issues are still keeping a ton of files red in my git status. I assume I need to simply force the pull somehow? It won't pull normally as it says I would be "overwriting files".

Thank you in advance.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking