From owner-freebsd-current@freebsd.org Fri May 26 17:58:54 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 79756D8399F for ; Fri, 26 May 2017 17:58:54 +0000 (UTC) (envelope-from carpeddiem@gmail.com) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 594E31CFF for ; Fri, 26 May 2017 17:58:54 +0000 (UTC) (envelope-from carpeddiem@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id 55B0AD8399E; Fri, 26 May 2017 17:58:54 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 55526D8399D for ; Fri, 26 May 2017 17:58:54 +0000 (UTC) (envelope-from carpeddiem@gmail.com) Received: from mail-io0-x234.google.com (mail-io0-x234.google.com [IPv6:2607:f8b0:4001:c06::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 1F79E1CFE; Fri, 26 May 2017 17:58:54 +0000 (UTC) (envelope-from carpeddiem@gmail.com) Received: by mail-io0-x234.google.com with SMTP id p24so13910592ioi.0; Fri, 26 May 2017 10:58:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=RPEpfhf+YaIxGNad8eGXWZFhxqd/M9cV7me2csZsOx4=; b=n8l7rbWkz74+qQ3+R4rTC2a3E8MNLiw7Dw/92TGMhscF1igILP/QlqGXeZIRhsOTjj 3ev+9eQMxlTu63wlam/TWXPfNgsQ+jiOPVyG5mBUvAgtCOhL6sPk409+JsXoz31+m09r UKYMh0mb8nTV5eFQq8mRpLKnH8c7vICDpiSRQUquhZfCWtaGuawyYH30M0l9Bd3Jjq3b eDElLEG4ciSEwHkl1R0fdj6hxCP+oGkRYjyOoo8l6IBSwj65wudBvABptc9mQfPsQVt/ F6NpAxjM9YXuDzHnzgj6Dn2bJCaTmdpX8DSvmQjX9xr8ClzQDhISUldRId6XD6maqTcS rEwg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=RPEpfhf+YaIxGNad8eGXWZFhxqd/M9cV7me2csZsOx4=; b=FZY1dUimrZTZjbhO5LOAD40Rf8GVSlBQKaRZQGMMkOPuGfklRberDvJMN5ig2HBJ2S 2QvB+qi7S+flETu4YTOPURxvo7lilfd0O6V9s0TDLQTqdTlZBpcjfX1hXMZ83omWAM1G j5kDJNIz2MSHPVNRZ8gTeRejj9EkNdjLA5+usQ6SUScpbEw0jk0cRBaJqX2S+dmNeDPM V7oqRcCNQ25/e2fX1/P7SIDbQ19Y/nEw9VGLrAnJn22OOg5ABqUn9M68EG74zDZ7kX3s PMxEkByukNBhZe8NCXo4KWTafMVueAf14mwwZYypxhTTsfB7EMCc9YgKuJjGUS65sC2r TkzQ== X-Gm-Message-State: AODbwcAGaIUHNkXXRHKRqZYebsBrpqxHYfc8/9zZ2YM2qSK/LG1KMMZs 616S6lQHoA1Ny8zff8u/Ghv67JXAuuUE X-Received: by 10.107.1.70 with SMTP id 67mr3046584iob.159.1495821533466; Fri, 26 May 2017 10:58:53 -0700 (PDT) MIME-Version: 1.0 Sender: carpeddiem@gmail.com Received: by 10.107.169.201 with HTTP; Fri, 26 May 2017 10:58:32 -0700 (PDT) In-Reply-To: <20170526161817.GD43031@home.opsec.eu> References: <20170526161817.GD43031@home.opsec.eu> From: Ed Maste Date: Fri, 26 May 2017 13:58:32 -0400 X-Google-Sender-Auth: JAldiuWw1LIqsSuOThWbYZ3eqVA Message-ID: Subject: Re: (head users) 64-bit inodes: Packages heads up and Poudriere errors To: Kurt Jaeger Cc: Bryan Drewery , "current@freebsd.org" Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 May 2017 17:58:54 -0000 On 26 May 2017 at 12:18, Kurt Jaeger wrote: > Hi! > >> For those running FreeBSD head, the ABI was majorly changed in r318736 >> for 64-bit inodes. This change was *backwards compatible* but not >> *forward compatible*. This is normal and expected. > > Is any fall-out from this change already handled or is it wise > to wait a few more days ? All fallout I'm aware of is due to either taking a shortcut and skipping the reboot after installing the new kernel, or running a custom kernel without COMPAT_FREEBSD11 in the config (required to support running the old world on the new kernel). Both of these are (now) explicitly called out in UPDATING. So as long as those steps are followed it should be fine.