Re: [Tools-discuss] bibxml3 database reload frequency
Kent Watsen <kent+ietf@watsen.net> Thu, 20 August 2020 22:24 UTC
Return-Path: <010001740df92895-fbde9921-36cf-455c-a1a6-4dbd2f32ebfd-000000@amazonses.watsen.net>
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 24ECC3A145B for <tools-discuss@ietfa.amsl.com>; Thu, 20 Aug 2020 15:24:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.894
X-Spam-Level:
X-Spam-Status: No, score=-1.894 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H5=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=amazonses.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wTlcvwip7v6a for <tools-discuss@ietfa.amsl.com>; Thu, 20 Aug 2020 15:24:28 -0700 (PDT)
Received: from a48-92.smtp-out.amazonses.com (a48-92.smtp-out.amazonses.com [54.240.48.92]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1C75D3A145A for <tools-discuss@ietf.org>; Thu, 20 Aug 2020 15:24:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple; s=224i4yxa5dv7c2xz3womw6peuasteono; d=amazonses.com; t=1597962267; h=From:Message-Id:Content-Type:Mime-Version:Subject:Date:In-Reply-To:Cc:To:References:Feedback-ID; bh=GuUlu7pu/7OENaT01QgCqKpPYDX1jnUZ5If2FwSgCzM=; b=dffTKBYwR9AEA0wooFVU2FmGGqyaIs+M9/yoYvGy7u8109hD0YYcdAEp8PLdZEIZ 0xtSE3yIyzxyCLzPZ664isCusT4fxDbDPt+dQV36VQnanD8nya+J7S3sKY6DyTHBIXs 1DKt7jkhlxncJt3Pl/sx3k3ltF7sEDeK+8bvaHdo=
From: Kent Watsen <kent+ietf@watsen.net>
Message-ID: <010001740df92895-fbde9921-36cf-455c-a1a6-4dbd2f32ebfd-000000@email.amazonses.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_A96F3FF7-203A-4E96-952F-B87553D7B4AF"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.80.23.2.2\))
Date: Thu, 20 Aug 2020 22:24:26 +0000
In-Reply-To: <5d239c70-0124-c4d4-5dd2-8e712c7b14cd@levkowetz.com>
Cc: tools-discuss@ietf.org
To: Henrik Levkowetz <henrik@levkowetz.com>
References: <010001740c9e6adf-5f978dea-f19a-4298-8376-b82bf3be0835-000000@email.amazonses.com> <5d239c70-0124-c4d4-5dd2-8e712c7b14cd@levkowetz.com>
X-Mailer: Apple Mail (2.3608.80.23.2.2)
X-SES-Outgoing: 2020.08.20-54.240.48.92
Feedback-ID: 1.us-east-1.DKmIRZFhhsBhtmFMNikgwZUWVrODEw9qVcPhqJEI2DA=:AmazonSES
Archived-At: <https://mailarchive.ietf.org/arch/msg/tools-discuss/Tndn1LeyLi7dlRiVKyYkIP3ip5s>
Subject: Re: [Tools-discuss] bibxml3 database reload frequency
X-BeenThere: tools-discuss@ietf.org
X-Mailman-Version: 2.1.29
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: Thu, 20 Aug 2020 22:24:30 -0000
Hi Henrik and Carsten - thanks for the responses! It worked, and then it didn’t. Too late for me now, but you should know, I think datatracker's cache may need to be cleared befor each run... Below for details. K My adventure: I first updated my XML, e.g.: <xi:include href="https://datatracker.ietf.org/doc/bibxml3/reference.I-D.ietf-netconf-crypto-types.xml”/> But my locally compiled drafts continued to load the *previous* version (-17) of the crypto-types draft (though I submitted -18 a few hours ago). So I ran `xml2rfc —clear-cache`, after which the current (-18) revision showed. Yeah! Thinking that I conquered it, I submitted the dependent drafts, but looking at the uploaded documents, I see the previous version again. For instance, the references section of the just-uploaded -13 of the “trust-anchors” draft shows -17 for the “crypto-types” draft: https://tools.ietf.org/html/draft-ietf-netconf-trust-anchors-13#ref-I-D.ietf-netconf-crypto-types <https://tools.ietf.org/html/draft-ietf-netconf-trust-anchors-13#ref-I-D.ietf-netconf-crypto-types> Oh, well, can’t win them all. K. > On Aug 20, 2020, at 12:36 PM, Henrik Levkowetz <henrik@levkowetz.com> wrote: > > Hi Kent, > > On 2020-08-20 18:05, Kent Watsen wrote: >> >> Hi Tools Team. >> >> How often is https://xml2rfc.tools.ietf.org/public/rfc/bibxml3 >> rebuilt? Is there a way to have it rebuild more often and/or for >> draft authors to externally prompt it to rebuild? > > THe short answers, which won't help you are: Once per day, and sorry, no. > > The answer that I believe will help you is this: > > Please use the draft bibxml references under datatracker.ietf.org/doc/bibxml3/ > instead. Those are generated on-the-fly and will reflect a new submission > at once. > > You can use the old form > > https://datatracker.ietf.org/doc/bibxml3/reference.I-D.draft-ietf-netconf-crypto-types.xml > > but also a simplified form that omits the 'reference.I-D.' part: > > https://datatracker.ietf.org/doc/bibxml3/draft-ietf-netconf-crypto-types.xml > > > Best regards, > > Henrik > >> >> See below for background info. >> >> Thanks, >> Kent >> >> >> Background: >> >> I have one draft depending on another. The new <relref> element is used, but the resulting hyperlinks point to the previous version of the referenced draft (before it was updated ~1 hour ago). >> >> Looking at https://xml2rfc.tools.ietf.org/public/rfc <https://xml2rfc.tools.ietf.org/public/rfc>, I see that “bibxml3” hasn’t been updated for roughly one day: >> >> bibxml3/ 19-Aug-2020 00:49 >> >> Note that the timestamp for “bibxml” (without the ‘3’) is roughly 24 hours newer: >> >> bibxml/ 20-Aug-2020 00:45 >> >> In any case, the hyperlinks produced by the <relref> elements are all resolving to the previous version of the referenced draft. I tried `xml2rfc —clear-cache`, but I think the source issue is with https://xml2rfc.tools.ietf.org/public/rfc/bibxml3 not having updated… >> >> How often is https://xml2rfc.tools.ietf.org/public/rfc/bibxml3 built? Is there a way to prompt it to reload? >> >> >> >> ___________________________________________________________ >> Tools-discuss mailing list >> Tools-discuss@ietf.org >> https://www.ietf.org/mailman/listinfo/tools-discuss >> >> Please report datatracker.ietf.org and mailarchive.ietf.org >> bugs at http://tools.ietf.org/tools/ietfdb >> or send email to datatracker-project@ietf.org >> >> Please report tools.ietf.org bugs at >> http://tools.ietf.org/tools/issues >> or send email to webmaster@tools.ietf.org >> >
- [Tools-discuss] bibxml3 database reload frequency Kent Watsen
- Re: [Tools-discuss] bibxml3 database reload frequ… Carsten Bormann
- Re: [Tools-discuss] bibxml3 database reload frequ… Henrik Levkowetz
- Re: [Tools-discuss] bibxml3 database reload frequ… Kent Watsen
- Re: [Tools-discuss] bibxml3 database reload frequ… Kent Watsen
- Re: [Tools-discuss] bibxml3 database reload frequ… Carsten Bormann
- Re: [Tools-discuss] bibxml3 database reload frequ… Julian Reschke
- Re: [Tools-discuss] bibxml3 database reload frequ… Carsten Bormann
- Re: [Tools-discuss] bibxml3 database reload frequ… Henrik Levkowetz
- Re: [Tools-discuss] bibxml3 database reload frequ… Henrik Levkowetz
- Re: [Tools-discuss] bibxml3 database reload frequ… Carsten Bormann
- Re: [Tools-discuss] bibxml3 database reload frequ… Julian Reschke
- Re: [Tools-discuss] bibxml3 database reload frequ… Henrik Levkowetz
- Re: [Tools-discuss] bibxml3 database reload frequ… Carsten Bormann
- Re: [Tools-discuss] bibxml3 database reload frequ… Henrik Levkowetz
- Re: [Tools-discuss] bibxml3 database reload frequ… Carsten Bormann
- Re: [Tools-discuss] bibxml3 database reload frequ… Henrik Levkowetz