IETF Logo Mail Archive

Re: [Tools-discuss] Datatracker 8.3.1 deployed

Carsten Bormann <cabo@tzi.org> Mon, 29 August 2022 12:00 UTC

Return-Path: <cabo@tzi.org>
X-Original-To: tools-discuss@ietfa.amsl.com
Delivered-To: tools-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 698B2C15259C for <tools-discuss@ietfa.amsl.com>; Mon, 29 Aug 2022 05:00:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.906
X-Spam-Level:
X-Spam-Status: No, score=-6.906 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
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 s5lQ_dNom-iF for <tools-discuss@ietfa.amsl.com>; Mon, 29 Aug 2022 05:00:38 -0700 (PDT)
Received: from gabriel-smtp.zfn.uni-bremen.de (gabriel-smtp.zfn.uni-bremen.de [IPv6:2001:638:708:32::15]) (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 9E244C15256D for <tools-discuss@ietf.org>; Mon, 29 Aug 2022 05:00:38 -0700 (PDT)
Received: from [192.168.217.124] (p5089abf5.dip0.t-ipconnect.de [80.137.171.245]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-smtp.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4MGTXc3sQ1zDCdd; Mon, 29 Aug 2022 14:00:32 +0200 (CEST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.7\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <bafdfadc-e988-bb9d-9f80-634621d7fc0b@nostrum.com>
Date: Mon, 29 Aug 2022 14:00:32 +0200
Cc: tools-discuss <tools-discuss@ietf.org>
X-Mao-Original-Outgoing-Id: 683467232.078214-9dcac5a8ae88d114c316f4a0dd26642b
Content-Transfer-Encoding: quoted-printable
Message-Id: <3B0D2196-0A52-42CE-9306-D58E9D31C026@tzi.org>
References: <bafdfadc-e988-bb9d-9f80-634621d7fc0b@nostrum.com>
To: Robert Sparks <rjsparks@nostrum.com>
X-Mailer: Apple Mail (2.3608.120.23.2.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/tools-discuss/vHtyuh-o8lYcfWOP5ns9H9uKZ1Q>
Subject: Re: [Tools-discuss] Datatracker 8.3.1 deployed
X-BeenThere: tools-discuss@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: IETF Tools Discussion <tools-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tools-discuss>, <mailto:tools-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tools-discuss/>
List-Post: <mailto:tools-discuss@ietf.org>
List-Help: <mailto:tools-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tools-discuss>, <mailto:tools-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 29 Aug 2022 12:00:41 -0000

We used to get these messages below.

Have we rationalized them away?
Am I looking into the wrong place?

(I’m trying to find which datatracker release broke bibxml generation for I-Ds.
Unfortunately, there is no bread crumb left by datatracker in these file.)

Grüße, Carsten


> On 2022-05-26, at 17:53, Robert Sparks <rjsparks@nostrum.com> wrote:
> 
> See https://github.com/ietf-tools/datatracker/releases for what changed.
> 
> RjS
> 
> ___________________________________________________________
> Tools-discuss mailing list - Tools-discuss@ietf.org
> This list is for discussion, not for action requests or bug reports.
> * Report datatracker and mailarchive bugs to: datatracker-project@ietf.org
> * Report tools.ietf.org bugs to: webmaster@tools.ietf.org
> * Report all other bugs or issues to: ietf-action@ietf.org
> List info (including how to Unsubscribe): https://www.ietf.org/mailman/listinfo/tools-discuss

v2.23.0 | Report a Bug | By Email