From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org
X-Spam-Level: *
X-Spam-Status: No, score=1.3 required=5.0 tests=RDNS_NONE autolearn=no
	autolearn_force=no version=3.4.4
Received: (qmail 28258 invoked from network); 1 Jul 2021 06:08:11 -0000
Received: from unknown (HELO 1ess.inri.net) (216.126.196.35)
  by inbox.vuxu.org with ESMTPUTF8; 1 Jul 2021 06:08:11 -0000
Received: from mimir.eigenstate.org ([206.124.132.107]) by 1ess; Tue Jun 29 20:47:22 -0400 2021
Received: from stockyard.org (ue.tmodns.net [172.58.230.185])
	by mimir.eigenstate.org (OpenSMTPD) with ESMTPSA id 25af6bf7 (TLSv1.2:ECDHE-RSA-AES256-SHA:256:NO)
	for <9front@9front.org>;
	Tue, 29 Jun 2021 17:47:07 -0700 (PDT)
Message-ID: <874C070E5393B7D02BE9121F6E10F268@eigenstate.org>
To: 9front@9front.org
Date: Tue, 29 Jun 2021 20:47:04 -0400
From: ori@eigenstate.org
In-Reply-To: <C95B14D1-4085-4F93-A382-BDF95BFAA5AF@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
List-ID: <9front.9front.org>
List-Help: <http://lists.9front.org>
X-Glyph: ➈
X-Bullshit: structured method app configuration-scale generator 
Subject: Re: [9front] inconsistencies after a sysupdate
Reply-To: 9front@9front.org
Precedence: bulk

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.