[iola-conversion-tool] Bug in Datatracker Agenda Code?

Alexa Morris <amorris@amsl.com> Fri, 02 March 2012 19:17 UTC

Return-Path: <amorris@amsl.com>
X-Original-To: iola-conversion-tool@ietfa.amsl.com
Delivered-To: iola-conversion-tool@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B6BE421F8557 for <iola-conversion-tool@ietfa.amsl.com>; Fri, 2 Mar 2012 11:17:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.088
X-Spam-Level:
X-Spam-Status: No, score=-2.088 tagged_above=-999 required=5 tests=[AWL=0.511, BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HA9rYpSrGHTB for <iola-conversion-tool@ietfa.amsl.com>; Fri, 2 Mar 2012 11:17:07 -0800 (PST)
Received: from mail.amsl.com (mail.amsl.com [IPv6:2001:1890:123a::1:14]) by ietfa.amsl.com (Postfix) with ESMTP id 3B2FF21F8555 for <iola-conversion-tool@ietf.org>; Fri, 2 Mar 2012 11:17:07 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id 26DD512C856 for <iola-conversion-tool@ietf.org>; Fri, 2 Mar 2012 11:17:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c8a.amsl.com ([127.0.0.1]) by localhost (c8a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wczD-B6wllck for <iola-conversion-tool@ietf.org>; Fri, 2 Mar 2012 11:17:07 -0800 (PST)
Received: from [192.168.0.195] (c-76-102-55-37.hsd1.ca.comcast.net [76.102.55.37]) by c8a.amsl.com (Postfix) with ESMTPSA id F3B4612C830 for <iola-conversion-tool@ietf.org>; Fri, 2 Mar 2012 11:17:06 -0800 (PST)
From: Alexa Morris <amorris@amsl.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Date: Fri, 2 Mar 2012 11:17:06 -0800
Message-Id: <8F28AC7A-8D1D-465C-A92B-DCC07197DADF@amsl.com>
To: iola-conversion-tool@ietf.org
Mime-Version: 1.0 (Apple Message framework v1084)
X-Mailer: Apple Mail (2.1084)
Subject: [iola-conversion-tool] Bug in Datatracker Agenda Code?
X-BeenThere: iola-conversion-tool@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Discussion of the IOLA / DB Schema Conversion Tool Project <iola-conversion-tool.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/iola-conversion-tool>, <mailto:iola-conversion-tool-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/iola-conversion-tool>
List-Post: <mailto:iola-conversion-tool@ietf.org>
List-Help: <mailto:iola-conversion-tool-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/iola-conversion-tool>, <mailto:iola-conversion-tool-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Mar 2012 19:17:07 -0000

There seems to be a small bug affecting Datatracker agenda code, because both the technical and the admin plenary agendas are being written to the same location.  I uploaded the admin agenda yesterday and then uploaded the technical plenary agenda, only to find that the technical plenary agenda went into the admin plenary slot. See here: https://datatracker.ietf.org/meeting/83/agenda.txt

Let me know if you need additional information to research this. 

Thanks,
Alexa


----------
Alexa Morris / Executive Director / IETF
48377 Fremont Blvd., Suite 117, Fremont, CA  94538
Phone: +1.510.492.4089 / Fax: +1.510.492.4001
Email: amorris@amsl.com

Managed by Association Management Solutions (AMS)
Forum Management, Meeting and Event Planning
www.amsl.com <http://www.amsl.com/>