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.9 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, 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 2C3AF29C3F for ; Wed, 12 Jun 2024 20:15:11 +0200 (CEST) Received: from smtp4-g21.free.fr ([212.27.42.4]) by 9front; Wed Jun 12 14:11:50 -0400 2024 Received: from cixi.localnet (unknown [IPv6:2a01:e0a:bc7:f350:cf9c:9fd5:f3b0:3fae]) (Authenticated sender: tnemeth@free.fr) by smtp4-g21.free.fr (Postfix) with ESMTPSA id 6A5AD19F553 for <9front@9front.org>; Wed, 12 Jun 2024 20:11:48 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=free.fr; s=smtp-20201208; t=1718215908; bh=GGB0eVKEjn6ElnG3gLbyem3Ri4ehZAa5ULtIab+3A1M=; h=From:To:Subject:Date:In-Reply-To:References:From; b=qn5a0e7KXPfpIMrWrP/BoLxdlICkgSt40fRprY3KWZYS428YvrakqIJREhoDEPnsG wNwLeHpp3EGSihmWlY8JF3nnEX5+HsSOl4/7hK3GT6J5iNMOTajE0Ia7+gNEZqqhNT 93RTeED2Fd7dzN2a4D8Ho+wT+glLEIckd9io0kM8PmJiacfC1W0qSaXT7ggNqJsYUp /SwFpNLADDcRJ5F5nFNAcyv6QKrSsED9iuUzJ88OF5USXjRGkxvz3UVDAkUnlpC6ug iAPcsSX8u2F4AvDNuDeAcWWajoJjhe/l1U3oVb8kiTHkNyGlgzqTsx87IKCrOcEpGP S8NTyRdH+dA7Q== From: Thomas Nemeth To: 9front@9front.org Date: Wed, 12 Jun 2024 20:11:48 +0200 Message-ID: <8418174.T7Z3S40VBb@cixi> Organization: =?UTF-8?B?ZMOpc29yZ2FuaXPDqWU=?= In-Reply-To: References: <1890322.tdWV9SEqCh@cixi> <4959876.31r3eYUQgx@cixi> MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="iso-8859-1" List-ID: <9front.9front.org> List-Help: X-Glyph: ➈ X-Bullshit: dependency method high-performance metadata-oriented manager Subject: Re: [9front] Staying up-to-date Reply-To: 9front@9front.org Precedence: bulk Le mercredi 12 juin 2024 19:56:15 CEST, vous avez =E9crit : > sure, but my point is that automations like this are not supported by > 9front developers, and *will* sooner or later lead to unexpected > non-diagnosable errors. > as long as you're prepared for this risk i don't see anything that > would hinder automation. > the fqa script is an example, which does not contain a single bit of > error handling ;) Indeed :) I stumble upon them a lot of time. Eg, since a few days, while doing a "mk install" in /sys/src: ar vu /arm64/lib/ape/libap.a _assert.7 abort.7 abs.7 atof.7 atoi.7 atol.7=20 atoll.7 bsearch.7 calloc.7 clock.7 ctype.7 difftime.7 div.7 getenv.7=20 putenv.7 isalnum.7 itoa.7 itol.7 ldiv.7 mbwc.7 memccpy.7 memchr.7 memcmp.7= =20 mktime.7 mkstemp.7 qsort.7 raise.7 rand.7 strcat.7 strchr.7 strcmp.7=20 strcoll.7 strcpy.7 strcspn.7 strftime.7 strlen.7 strncat.7 strncmp.7=20 strncpy.7 strnlen.7 strpbrk.7 strrchr.7 strspn.7 strstr.7 strtod.7 strtok. 7 strtol.7 strtoll.7 strtoul.7 strtoull.7 strxfrm.7 toupper.7 strdup.7 ar: /arm64/lib/ape/libap.a not in archive format mk: ar vu /arm64/lib/ape/libap.a ... : exit status=3Dar 24249: error mk: for(i in gen ... : exit status=3Drc 24234: mk 24235: error mk: for (i in ... : exit status=3Drc 24227: mk 24232: error mk: cd lib mk install : exit status=3Dmk 24224: error mk: mk lib.install mk ... : exit status=3Drc 24222: mk 24223: error mk: date for (i ... : exit status=3Drc 23407: mk 24220: error /sys/src%=20 To the point of wondering if my filesystem is corrupted. Only trying to compile the kernel: file system made mkpaqfs: read failed: bootfs/arm64/bin/9660srv: phase error -- type=20 mismatch mkpaqfs: could not read directory: bootfs/arm64/bin/auth: phase error --=20 type mismatch mkpaqfs: could not read directory: bootfs/arm64/bin/aux: phase error --=20 type mismatch mkpaqfs: read failed: bootfs/arm64/bin/cfs: phase error -- type mismatch mkpaqfs: could not read directory: bootfs/arm64/bin/disk: phase error --=20 type mismatch mkpaqfs: read failed: bootfs/arm64/bin/dossrv: phase error -- type=20 mismatch mkpaqfs: read failed: bootfs/arm64/bin/cwfs64x: phase error -- type=20 mismatch mkpaqfs: could not read directory: bootfs/arm64/bin/ip: phase error --=20 type mismatch mkpaqfs: read failed: bootfs/arm64/bin/ls: phase error -- type mismatch mkpaqfs: read failed: bootfs/arm64/bin/mntgen: phase error -- type=20 mismatch mkpaqfs: could not read directory: bootfs/arm64/bin/ndb: phase error --=20 type mismatch mkpaqfs: read failed: bootfs/arm64/bin/hjfs: phase error -- type mismatch mkpaqfs: read failed: bootfs/arm64/bin/tlsclient: phase error -- type=20 mismatch mkpaqfs: read failed: bootfs/arm64/bin/nusb/usbd: phase error -- type=20 mismatch mkpaqfs: read failed: bootfs/arm64/bin/nusb/ether: phase error -- type=20 mismatch =2E./port/mkrootall \ paqfs __objtype_bin_paqfs /arm64/bin/paqfs\ factotum __objtype_bin_auth_factotum /arm64/bin/auth/factotum\ bootfs.paq bootfs_paq bootfs.paq\ boot boot boot\ >pi3.root.s =2E./port/mkrootc \ paqfs __objtype_bin_paqfs /arm64/bin/paqfs\ factotum __objtype_bin_auth_factotum /arm64/bin/auth/factotum\ bootfs.paq bootfs_paq bootfs.paq\ boot boot boot\ >pi3.rootc.c 7c -FTVw pi3.rootc.c cp: can't stat boot: file does not exist: 'boot' cannot open: file does not exist: 'mkroot.30532.out' =2E./port/mkrootall:29: < can't open: mkroot.30532.out: file does not exist= :=20 'mkroot.30532.out' mk: ../port/mkrootall \ ... : exit status=3Dmkrootall 30532: file does no= t=20 exist: 'mkroot.30532.out', deleting 'pi3.root.s'pi3.root.s: file does not=20 exist: 'pi3.root.s' /sys/src/9/bcm64%=20