From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-0.8 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id C885CC31E40 for ; Mon, 10 Jun 2019 16:58:50 +0000 (UTC) Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 9E46220859 for ; Mon, 10 Jun 2019 16:58:50 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 9E46220859 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=redhat.com Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=qemu-devel-bounces+qemu-devel=archiver.kernel.org@nongnu.org Received: from localhost ([::1]:48428 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1haNdB-0005cd-RN for qemu-devel@archiver.kernel.org; Mon, 10 Jun 2019 12:58:49 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]:47824) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1haNcU-0004yG-5X for qemu-devel@nongnu.org; Mon, 10 Jun 2019 12:58:07 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1haNcT-00065g-6C for qemu-devel@nongnu.org; Mon, 10 Jun 2019 12:58:06 -0400 Received: from mx1.redhat.com ([209.132.183.28]:51920) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1haNcT-00065I-0v for qemu-devel@nongnu.org; Mon, 10 Jun 2019 12:58:05 -0400 Received: from smtp.corp.redhat.com (int-mx07.intmail.prod.int.phx2.redhat.com [10.5.11.22]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id E4F52368A5; Mon, 10 Jun 2019 16:57:55 +0000 (UTC) Received: from localhost (ovpn-116-9.gru2.redhat.com [10.97.116.9]) by smtp.corp.redhat.com (Postfix) with ESMTP id 4DF4F1001B30; Mon, 10 Jun 2019 16:57:55 +0000 (UTC) Date: Mon, 10 Jun 2019 13:57:53 -0300 From: Eduardo Habkost To: Peter Maydell Message-ID: <20190610165753.GA5927@habkost.net> References: <20190607211544.7964-1-ehabkost@redhat.com> <20190610131105.GJ22416@habkost.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Scanned-By: MIMEDefang 2.84 on 10.5.11.22 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.30]); Mon, 10 Jun 2019 16:58:04 +0000 (UTC) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 209.132.183.28 Subject: [Qemu-devel] Ubuntu Trusty as supported build platform (was Re: [PULL 0/8] Python queue, 2019-06-07) X-BeenThere: qemu-devel@nongnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: QEMU Developers , Cleber Rosa Errors-To: qemu-devel-bounces+qemu-devel=archiver.kernel.org@nongnu.org Sender: "Qemu-devel" On Mon, Jun 10, 2019 at 02:21:57PM +0100, Peter Maydell wrote: > On Mon, 10 Jun 2019 at 14:11, Eduardo Habkost wrote: > > > > On Mon, Jun 10, 2019 at 01:58:50PM +0100, Peter Maydell wrote: > > > Hi. This fails to build on one of my buildtest machines: > > > > > > ERROR: Cannot use 'python3', Python 2 >= 2.7 or Python 3 >= 3.5 is required. > > > Use --python=/path/to/python to specify a supported Python. > > > > > > The machine has python 2.7.6 and 3.4.3. (It's an Ubuntu trusty > > > box; it's one of the gcc compile farm machines so upgrades to its > > > OS are not really under my control.) > > > > Ubuntu 16.04 LTS (Xenial) was released in April 2016. Doesn't > > that mean Trusty is not a supported build platform since April > > 2018? > > Possibly, but as I say the gcc compile farm is what it is. > Regardless of the strict letter of the deprecation policy, > when we start running into issues with the set of build test > machines I tend to feel we may be being a bit over-hasty in > deprecating things. I understand this as a request to make Trusty a supported build platform. Can we please update the documentation to reflect that, then? -- Eduardo