Re: [Rfc-markdown] 1.6.15: Emergency fix for latest bib.ietf.org breakage

Robert Sparks <rjsparks@nostrum.com> Wed, 03 August 2022 14:03 UTC

Return-Path: <rjsparks@nostrum.com>
X-Original-To: rfc-markdown@ietfa.amsl.com
Delivered-To: rfc-markdown@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A73AEC14F726; Wed, 3 Aug 2022 07:03:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.088
X-Spam-Level:
X-Spam-Status: No, score=-7.088 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_HI=-5, T_SCC_BODY_TEXT_LINE=-0.01, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nostrum.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Pceww0RnpEdX; Wed, 3 Aug 2022 07:03:47 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9D7CAC15A72E; Wed, 3 Aug 2022 07:03:47 -0700 (PDT)
Received: from [192.168.1.114] ([47.186.48.51]) (authenticated bits=0) by nostrum.com (8.17.1/8.17.1) with ESMTPSA id 273E3kO9051054 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Wed, 3 Aug 2022 09:03:47 -0500 (CDT) (envelope-from rjsparks@nostrum.com)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nostrum.com; s=default; t=1659535427; bh=z/ObvL6QHD4A7CgeHHCLAsAzvAsdQTXwTNgbPm1dDV8=; h=Date:Subject:From:To:Cc:References:In-Reply-To; b=Do1Q1qP7PCfKBvbNGjyjRUDyidQXWZzkgewtdeymdtYrvjDlIpWGxN0TTQB18YsBy 9L1mgzzFLrA/HdnHEZat/XdbVthCxKLfwXxHgT+iag5VQ5pWqI0ACgBy4mg9KyQ0zR 5g/nLioWzyyIGPUIC48geHsDLUMXxnwSwigjh4Do=
X-Authentication-Warning: raven.nostrum.com: Host [47.186.48.51] claimed to be [192.168.1.114]
Message-ID: <6055802a-ccad-c8a0-7fee-e14b7ec83abb@nostrum.com>
Date: Wed, 03 Aug 2022 09:03:41 -0500
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:91.0) Gecko/20100101 Thunderbird/91.11.0
Content-Language: en-US
From: Robert Sparks <rjsparks@nostrum.com>
To: rfc-markdown@ietf.org, Carsten Bormann <cabo@tzi.org>
Cc: tools-discuss <tools-discuss@ietf.org>
References: <E26BB3B4-BB3A-41BF-B5AC-F4ABCF0EFD33@tzi.org> <3aef48db-181d-f652-bf90-79a944b486f0@nostrum.com>
In-Reply-To: <3aef48db-181d-f652-bf90-79a944b486f0@nostrum.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-markdown/FFBj-Gc2_Hw2ujzP95dLYrl_l6s>
Subject: Re: [Rfc-markdown] 1.6.15: Emergency fix for latest bib.ietf.org breakage
X-BeenThere: rfc-markdown@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "rfc-markdown is a discussion list for people writing I-Ds and RFCs in Markdown and the authors of the tools used for that." <rfc-markdown.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rfc-markdown>, <mailto:rfc-markdown-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rfc-markdown/>
List-Post: <mailto:rfc-markdown@ietf.org>
List-Help: <mailto:rfc-markdown-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rfc-markdown>, <mailto:rfc-markdown-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Aug 2022 14:03:51 -0000

(Resending from the correct address)

On 8/3/22 8:54 AM, Robert Sparks wrote:
> fwiw - That breakage should be removed in short order.
>
> On 8/2/22 4:46 AM, Carsten Bormann wrote:
>> I just pushed kramdown-rfc 1.6.15, which works around the new DOCTYPE 
>> breakage in bib.ietf.org.
>>
>> As usual, install via
>>
>>     gem update
>>
>> (sudo required on some systems).
>>
>> More about the content of that release later.
>>
>> Grüße, Carsten
>>