From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <9front-bounces@9front.inri.net> X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-0.6 required=5.0 tests=DKIM_INVALID,DKIM_SIGNED, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.4 Received: from 9front.inri.net (9front.inri.net [168.235.81.73]) by inbox.vuxu.org (Postfix) with ESMTP id 521BD2156F for ; Sat, 22 Jun 2024 11:24:22 +0200 (CEST) Received: from mail-4027.protonmail.ch ([185.70.40.27]) by 9front; Sat Jun 22 05:22:42 -0400 2024 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=proton.me; s=nf5tgzj37rbvtnntx7idbbffuy.protonmail; t=1719048153; x=1719307353; bh=VIPDkcM7UFb77UoOx6PR5loCNVFW3DYRPQVfofwizL4=; h=Date:To:From:Subject:Message-ID:In-Reply-To:References: Feedback-ID:From:To:Cc:Date:Subject:Reply-To:Feedback-ID: Message-ID:BIMI-Selector; b=BgC/BddV9GXzZAYVlVfrEI74s/LjbIxve2IfJ1Kcun6R8Z/B89RyiaKWthJjqOzJe 7aLwmKIJAcS/A8irLsUdlPWPN011fLdpmqNOyeHrd9xHMQBwg5cwaclXRjsqsv8gED asWUZjKd4vIfMe2oBn1ZwMOtOlXKvU9x//3vgNYECFiYBwKut7K2muixumH6l1SIDs UDZk4vetm4J1HPNRsDc773KHDNvtrVllP4AWSQ1QKKRMsoz90ehbIUqYoorPII/6Dl voCmPnpyum7+tHcV0kSUFLUPB2Ct0ZzM6IhaPH9/h0/wfcNiMywoJUMdsvDv/qaM6r Vp+jNapJ+06Rw== Date: Sat, 22 Jun 2024 09:22:30 +0000 To: 9front@9front.org From: alex Message-ID: <5E2GP9xzjKnZ0Ph4UMEt4BlyTRlPnpyvEdX_2sLOO6GYgPpLCS8TDvxqmPb4z84ZmCmVk_2d-5kqBYDbnQcXfSamHCvBqBJQLm3SMDc3I04=@proton.me> In-Reply-To: <1d5a8764-5157-44a4-b44e-c407360782a8@posixcafe.org> References: <1d5a8764-5157-44a4-b44e-c407360782a8@posixcafe.org> Feedback-ID: 112555570:user:proton X-Pm-Message-ID: 9f35c1655256830f7c4fa9d0ea5b8a987b670b3c MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable List-ID: <9front.9front.org> List-Help: X-Glyph: ➈ X-Bullshit: distributed compliant realtime STM package CSS solution Subject: Re: [9front] System not up to date / in sync with repo after "sysupdate" Reply-To: 9front@9front.org Precedence: bulk Hello moody,=20 is there any way I could find out or narrow down the cause? Would it be pos= sible to boot from USB with a nightly build, copy /dist/plan9front/.git fro= m 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,=20 Alex Jacob Moody schrieb am Freitag, 21. Juni 2024 um 21:4= 9: > On 6/21/24 12:58, alex wrote: >=20 > > 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 whet= her 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 Latitud= e 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 a= nd best regards, Alex >=20 >=20 > We'll need to know how it's failing. It's likely that for some reason you= r .git is borked, so as Arne suggested you should > bootstrap just the /dist/plan9front/.git from something like the latest i= so, then git/revert, then pull new commits. >=20 > Also we do not have a working RISC-V release, so not sure what you're tal= king about there. The use of arm64 should have no impact on this. >=20 >=20 > Thanks, > moody