9front - general discussion about 9front
 help / color / mirror / Atom feed
From: alex <alex9-ml@proton.me>
To: 9front@9front.org
Subject: Re: [9front] System not up to date / in sync with repo after "sysupdate"
Date: Sat, 22 Jun 2024 09:22:30 +0000	[thread overview]
Message-ID: <5E2GP9xzjKnZ0Ph4UMEt4BlyTRlPnpyvEdX_2sLOO6GYgPpLCS8TDvxqmPb4z84ZmCmVk_2d-5kqBYDbnQcXfSamHCvBqBJQLm3SMDc3I04=@proton.me> (raw)
In-Reply-To: <1d5a8764-5157-44a4-b44e-c407360782a8@posixcafe.org>

Hello moody, 

is there any way I could find out or narrow down the cause? Would it be possible to boot from USB with a nightly build, copy /dist/plan9front/.git from there to another USB drive and copy it from there to the local install? (I would like to avoid a new installation if this phenomenon occurs.)

Thank you and best regards, 
Alex


Jacob Moody <moody@posixcafe.org> schrieb am Freitag, 21. Juni 2024 um 21:49:

> On 6/21/24 12:58, alex wrote:
> 
> > Hello Arne, please excuse my late response and thank you very much for your help! :) I've tried to revert but it fails and since I don't know whether my data will be lost when reinstalling from iso every release (maybe I would need to ream my disk every time), I've got myself a used Dell Latitude where it worked fine. Maybe I should stick with Intel to learn and switch to ARM64 / RISC-V when I halfway know what I'm doing.. Many thanks again and best regards, Alex
> 
> 
> We'll need to know how it's failing. It's likely that for some reason your .git is borked, so as Arne suggested you should
> bootstrap just the /dist/plan9front/.git from something like the latest iso, then git/revert, then pull new commits.
> 
> Also we do not have a working RISC-V release, so not sure what you're talking about there. The use of arm64 should have no impact on this.
> 
> 
> Thanks,
> moody

  reply	other threads:[~2024-06-22  9:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-21 17:58 alex
2024-06-21 19:49 ` Jacob Moody
2024-06-22  9:22   ` alex [this message]
2024-06-22 14:29     ` ori
  -- strict thread matches above, loose matches on Subject: below --
2024-05-28  9:24 alex-ml
2024-05-29 17:40 ` Arne Meyer

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='5E2GP9xzjKnZ0Ph4UMEt4BlyTRlPnpyvEdX_2sLOO6GYgPpLCS8TDvxqmPb4z84ZmCmVk_2d-5kqBYDbnQcXfSamHCvBqBJQLm3SMDc3I04=@proton.me' \
    --to=alex9-ml@proton.me \
    --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).