From: "Toke Høiland-Jørgensen" <toke@toke.dk>
To: Rich Brown <richb.hanover@gmail.com>, bloat@lists.bufferbloat.net
Subject: Re: [Bloat] macOS Catalina causes 'hugo serve' to segfault...
Date: Fri, 21 Feb 2020 12:20:47 +0100 [thread overview]
Message-ID: <87tv3ktcds.fsf@toke.dk> (raw)
In-Reply-To: <146A9AC4-7EA6-4759-A4D1-D0613C6B650D@gmail.com>
Rich Brown <richb.hanover@gmail.com> 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
next prev parent reply other threads:[~2020-02-21 11:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-20 19:14 Rich Brown
2020-02-21 11:20 ` Toke Høiland-Jørgensen [this message]
2020-02-21 13:51 ` Rich Brown
2020-02-22 12:26 ` Toke Høiland-Jørgensen
2020-02-22 12:39 ` Rich Brown
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.bufferbloat.net/postorius/lists/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87tv3ktcds.fsf@toke.dk \
--to=toke@toke.dk \
--cc=bloat@lists.bufferbloat.net \
--cc=richb.hanover@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox