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 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 331A4216C8 for ; Wed, 27 Mar 2024 16:18:56 +0100 (CET) Received: from mail.posixcafe.org ([45.76.19.58]) by 9front; Wed Mar 27 11:16:05 -0400 2024 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=posixcafe.org; s=20200506; t=1711552533; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=Smdxewn9TZUokUfFeMyYw/u6de2ARp1qib9DlJ4KlWE=; b=EMR56pn83yoziXVSYJxxP/OA6FbXyq4jYOISzULc37Sgh+ScUtfrbPSL1Ebl3mRuAm5RWL tZbqhWOWtnFksaGF5OxTigrqHSfr+U8HZmxMqRhZysaPN1mV9lqMKp9KKHm20KYLc4MAJk Uyf3ghZDUsYJnRzbsbPNbNa71RdP6ic= Received: from [192.168.168.200] ( [207.45.82.38]) by mail.posixcafe.org (OpenSMTPD) with ESMTPSA id 6fe2678a (TLSv1.3:TLS_AES_256_GCM_SHA384:256:NO) for <9front@9front.org>; Wed, 27 Mar 2024 10:15:33 -0500 (CDT) Message-ID: <691efaa3-c195-4938-8a58-e76bc9a4eeaa@posixcafe.org> Date: Wed, 27 Mar 2024 10:16:02 -0500 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird To: 9front@9front.org References: Content-Language: en-US From: Jacob Moody In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit List-ID: <9front.9front.org> List-Help: X-Glyph: ➈ X-Bullshit: responsive information strategy Subject: Re: [9front] Error compiling libc/amd64/main9.s and/or main9p.s Reply-To: 9front@9front.org Precedence: bulk For what it's worth it's really not you being dumb, this is a flaw in how we distribute information. Our information channels are well detached from our update channels. I think this is the 10th or so time someone has stumbled in to this, so I am glad sl added it to the fqa. We've discussed a solution to this a few times but nothing has stuck. Let me give an idea then and we can find something that sticks. Maybe /sys/lib/sysupdate (not attached to the path) could have a file named after a commit with specific update instructions. Sysupdate could then get the list of commits it is updating through, and cat out those files from that directory. Thanks, moody