From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mout-p-201.mailbox.org (mout-p-201.mailbox.org [80.241.56.171]) by sourceware.org (Postfix) with ESMTPS id DDA193858C1F for ; Wed, 22 Mar 2023 10:58:56 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org DDA193858C1F Authentication-Results: sourceware.org; dmarc=pass (p=reject dis=none) header.from=aarsen.me Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=aarsen.me Received: from smtp202.mailbox.org (smtp202.mailbox.org [IPv6:2001:67c:2050:b231:465::202]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-384) server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by mout-p-201.mailbox.org (Postfix) with ESMTPS id 4PhQSs2cPWz9sb4; Wed, 22 Mar 2023 11:58:53 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aarsen.me; s=MBO0001; t=1679482733; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=hDA+Sor7W0s9iMswKRptOfQW3DUwzr0LT7dwaDNYHh8=; b=pNHsEjZB/mX2W5ZtPavxCXIQY998LYrQux4sK6jPVy74YSRwtMSdTZawr1rtF2wPihpVTk ViBiE+RfXxEeCX5MwCSkUCE+HrT73Japl4WuqGHNrp2ygCPnELv3pVXdDkZ2by/GZSRS19 tbqP8rx0ATrQDKPS3KlFyf/Ch9KI28hsG4/29usCTMuCV31sUBONe9wTUhWjfQw6UIwPfF p/cIY21k++rjld7uyX1GT3a/2FYEcLCs6muBD+Kh1AZS+nvKrXsKA6wRTOcFCd+3KQ5ILY yP2U9V4WgDnh0rCD9Ius554X7/33CmuYWZ3ZOK/iQW+jK9yhcQgGzD1+sqEk7g== References: <86sfdy1hqw.fsf@aarsen.me> <0b0d7974-fda0-ea5f-ac11-95ae43faa32e@pfeifer.com> From: Arsen =?utf-8?Q?Arsenovi=C4=87?= To: Gerald Pfeifer Cc: "Frank Ch. Eigler" , overseers@sourceware.org Subject: Re: Please update Texinfo on gcc.gnu.org Date: Wed, 22 Mar 2023 11:39:49 +0100 In-reply-to: <0b0d7974-fda0-ea5f-ac11-95ae43faa32e@pfeifer.com> Message-ID: <861qlhxdat.fsf@aarsen.me> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature" X-Rspamd-Queue-Id: 4PhQSs2cPWz9sb4 X-Spam-Status: No, score=-4.8 required=5.0 tests=BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,KAM_INFOUSMEBIZ,KAM_SHORT,RCVD_IN_DNSWL_LOW,SPF_HELO_NONE,SPF_PASS,TXREP autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org List-Id: --=-=-= Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Gerald Pfeifer writes: > On Tue, 21 Mar 2023, Frank Ch. Eigler wrote: >>> I'd like to request that the server building GCC texinfo-based >>> documentation (which is, AFAIK, gcc.gnu.org) be updated to Texinfo >>> master, currently at commit f12de7a5b383bed0ea29ee34c427679e0f8b9658. >>> [...] >>> Please let me know if there's anything extra that I should do. >> Have you considered getting the shared gccadmin account to build & >> install its private copy of texinfo under its home directory? > > I'm not sure how broadly we want to provide access to the gccadmin=20 > account, software supply chain and such? (In general, not particular=20 > to Arsen at all!) > > I'll try to have a look at installing an updated version of Texinfo > and how to use it for our daily doc builds this coming weekend... > > (Not a big fan of using "random" Git versions in production, though; > any chance for a regular release coming soon?) I'm not sure, I think Gavin sees these changes as new features, hence landing in the next minor release of Texinfo (7.1) or so. I'm not sure there's a well defined timeline for these releases. If you wish, I can ask about it. Thanks for updating the builder script, by the way. Applying the new Texinfo version should be as simple as adding it to $PATH, FWIW. If so desired, I wouldn't mind looking into how to make the buildbot build the docs in order to reduce the amount of code running under gccadmin. Mark suggested we should build both for the lowest supported and the fancy new Texinfo versions. We could set up a pair of builders that build the fancy new Texinfo version (perhaps by having a specification of how to pull a given version, so that we could use a hand-managed commit hash or a dist tarball once we have applicable releases) as well as the lowest supported version (which changes rarely, so we can just put it in the runner Docker images even), and then have the fancy new one use an SSH key stored in a Buildbot secret to update the docs directory via a dedicated user. I use a similar strategy on sr.ht to push to my server: https://git.sr.ht/~arsen/www/tree/master/item/.build.yml Thanks again, have a lovely day. > Gerald PS: For some reason, I didn't get your email delivered, so I needed to scrape it from inbox.s.o and mangle it into my maildir. Did you get a bounce notification? =2D-=20 Arsen Arsenovi=C4=87 --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iOYEARYKAI4WIQT+4rPRE/wAoxYtYGFSwpQwHqLEkwUCZBrfal8UgAAAAAAuAChp c3N1ZXItZnByQG5vdGF0aW9ucy5vcGVucGdwLmZpZnRoaG9yc2VtYW4ubmV0RkVF MkIzRDExM0ZDMDBBMzE2MkQ2MDYxNTJDMjk0MzAxRUEyQzQ5MxAcYXJzZW5AYWFy c2VuLm1lAAoJEFLClDAeosSTlgEA/j5QmUoybMDz7J01HRQCSwyTkqOoUw9P2Mt/ WtYkk7zfAP0aczxAo+3TykPnNbepr7xY9RnSoAFNHjGxqdjirqvHCw== =QFbL -----END PGP SIGNATURE----- --=-=-=--