From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.toke.dk (mail.toke.dk [IPv6:2a0c:4d80:42:2001::664]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id 482DB3CB35 for ; Fri, 21 Feb 2020 06:20:50 -0500 (EST) From: Toke =?utf-8?Q?H=C3=B8iland-J=C3=B8rgensen?= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=toke.dk; s=20161023; t=1582284047; bh=jNMF1qhGB/NlWga9jPhHn+Bl62CEORCY1mEapbj2p54=; h=From:To:Subject:In-Reply-To:References:Date:From; b=K1pKlxnAwuebJ3EDbFLzcgbUnlDdYJmLN1z4FIIY0ZmAOncj3GmUq0qISs6sCB1jS XdoJ9qeqmfIPONlEvay0mFxnoIqI7Sq843af7XpW/4ppA0Bxdz3/6bM07ldNa16GO3 UH48Zbgu0J/q4b7eHec/3LUF+mH4POoiANJeyoIpmle1t9iy9KwqbrCkkit98dtkix 3HwR1lt5io1RHdujkIZ4Dfp2GiWGZMDCarQat+9L7d9lPujQTnfbWuRkwd78evKhNo mMDduqqpkT9IUTxPoJlUG+tNnAXbTHqz+/Dcavu5k1Fw+SgSxGY1Z0MVMW9BC+k37U mN7k81VTJ95VQ== To: Rich Brown , bloat@lists.bufferbloat.net In-Reply-To: <146A9AC4-7EA6-4759-A4D1-D0613C6B650D@gmail.com> References: <146A9AC4-7EA6-4759-A4D1-D0613C6B650D@gmail.com> Date: Fri, 21 Feb 2020 12:20:47 +0100 X-Clacks-Overhead: GNU Terry Pratchett Message-ID: <87tv3ktcds.fsf@toke.dk> MIME-Version: 1.0 Content-Type: text/plain Subject: Re: [Bloat] macOS Catalina causes 'hugo serve' to segfault... X-BeenThere: bloat@lists.bufferbloat.net X-Mailman-Version: 2.1.20 Precedence: list List-Id: General list for discussing Bufferbloat List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Feb 2020 11:20:50 -0000 Rich Brown writes: > I took a deep breath, and upgraded my macOS machine to Catalina. I > knew it would cause problems, and it did. Most were small, or simply > annoying. > > One of the flat tires is the ancient version of hugo (0.16) which I > had been keeping around to rebuild the bufferbloat.net site. It now > segfaults reliably (instead of only a third of the time when I was > running Sierra (10.12)) > > I just posted a message on the Hugo forum (a Discourse forum!) asking > for guidance. > https://discourse.gohugo.io/t/convert-a-0-16-site-to-modern-hugo-syntax/23579 Some background for this (for those who don't know or may have forgotten): The reason we ended up freezing on Hugo 0.16 was that the Hugo devs dropped the support for the wiki-style internal links which we were using. I seem to recall they were also being somewhat unhelpful in considering any suggestions to reinstate / keep that support around. Looking at that thread, I don't really get the feeling that they're any more helpful now :/ As an alternative, maybe it'll be possible to build a new version of the 0.16 Hugo binary with a newer Go runtime? I very much doubt that the segfault is because of the Hugo code itself... -Toke