From: ori@eigenstate.org
To: 9front@9front.org
Subject: Re: [9front] inconsistencies after a sysupdate
Date: Tue, 29 Jun 2021 20:47:04 -0400 [thread overview]
Message-ID: <874C070E5393B7D02BE9121F6E10F268@eigenstate.org> (raw)
In-Reply-To: <C95B14D1-4085-4F93-A382-BDF95BFAA5AF@gmail.com>
Quoth Xiao-Yong Jin <meta.jxy@gmail.com>:
>
>
> > On Jun 28, 2021, at 1:33 PM, ori@eigenstate.org wrote:
> >
> > Quoth Xiao-Yong Jin <meta.jxy@gmail.com>:
> >>
> >> So git/walk is wrong. How do I fix this?
> >
> >
> > What are the permissions on those files? We had
> > some issues where we would:
> >
> > 1) set permissions overly tightly when updating
> > (644/755, rather than 664, 775), so that
> > future updates would not be able to modify
> > those files.
>
> After going through all the files in .git/fs/object/658757*/tree,
> I found out that the permission of the files,
> /sys/src/cmd/?c/reg.c
> were 644 with user/group sys/sys, which glenda couldn't write.
>
> So I guess what happened was that, while git/pull, the update
> of the files /sys/src/cmd/?c/reg.c failed with permission error,
> and likely the error handling was not good enough for this case,
> which left the state inconsistent.
>
Yeah. That just happened to me on my laptop,
which gets sysupdated less frequently than
my CPU server.
For anyone else that runs into permission
errors when sysupdating:
chmod g+w /path/to/files
git/revert /path/to/files
and make sure you update git:
cd /sys/src/cmd/git && mk install
Apologies for these teething troubles; this
is really the first time we've had a repo
owned by $user, but updated by $otheruser,
and I clearly didn't get permissions right
in that case.
I think these issues have been shaken out
now -- thanks for bearing with me.
next prev parent reply other threads:[~2021-07-01 6:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-28 17:18 Xiao-Yong Jin
2021-06-28 18:33 ` ori
2021-06-28 18:57 ` Xiao-Yong Jin
2021-06-30 0:47 ` ori [this message]
2021-07-04 23:53 ` kvik
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=874C070E5393B7D02BE9121F6E10F268@eigenstate.org \
--to=ori@eigenstate.org \
--cc=9front@9front.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).