From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 9FF5A1382C5 for ; Fri, 12 Jun 2020 13:45:23 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id DF0F2E08F3; Fri, 12 Jun 2020 13:45:15 +0000 (UTC) Received: from mail-ed1-f45.google.com (mail-ed1-f45.google.com [209.85.208.45]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 94B5BE084A for ; Fri, 12 Jun 2020 13:45:15 +0000 (UTC) Received: by mail-ed1-f45.google.com with SMTP id w7so6477107edt.1 for ; Fri, 12 Jun 2020 06:45:15 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=2sde0I9x9bSqmrT/ik4M4GZRZltUsSapQZ28eaGNNb8=; b=NFJocKhvQivy7biEpeZYtwe88I6z72rl1f0TmKcSsUGiFtgWFjE8N0erXoqgp9S6bH +isZFWeuMvNkWsDS6arw6lk+pfBr/dgt/CrujRnWhcQcVyvfW4cxF+5v5ELFzdPYXMeN XCK9rIIF9yipfDsPnyaZPa5W5RkSsjbKPx7akUKSyqmtBkipZ+ThaHCwwjcIENojKbEU FOxn9eaW1kLTeaffWNizeUdehsWSDrZKGqCYpeeyCWJK/ETJ8OpVy5UoFCd2FizMsNDI IWhn65k6pHDGUC7mGpzQDcAo8o3dj5IuT/iK2nLFFDrs5HChMH0HSk+z2KU00tPBUIs/ b9xw== X-Gm-Message-State: AOAM533hJM6TkyQ7AoBNtwlvkG7323bfKdYDRug6T0FPD4Ppj0v6vF9e A+XlSnXsdPC0QUXsOIicEL9M+v22ze9Xevssb2yLZcS7 X-Google-Smtp-Source: ABdhPJwqP509+K7LyXM8JFSXLLWNYKhFweHzKeOkqr2fqiwqCviLNzGFaCjsABJNzlDat5SM2Ix6FKb8G9mn+ppNbmQ= X-Received: by 2002:a50:cd17:: with SMTP id z23mr11473995edi.326.1591969513755; Fri, 12 Jun 2020 06:45:13 -0700 (PDT) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply MIME-Version: 1.0 References: <9ed9c401-7066-9c6d-8ce4-2ee94a1b903e@web.de> <20200611091031.770b9102@digimed.co.uk> <53e40310-7ee0-a3a1-d500-ed0b81c10bf4@web.de> <621b4819-e581-51a3-44e3-3bee51814d5d@web.de> In-Reply-To: From: Rich Freeman Date: Fri, 12 Jun 2020 09:45:02 -0400 Message-ID: Subject: Re: [gentoo-user] "masked by: EAPI 7" trying up update "portage" - how to proceed To: gentoo-user@lists.gentoo.org Content-Type: text/plain; charset="UTF-8" X-Archives-Salt: 847e9ed8-2ab3-4657-a419-9c8aaf7f94e2 X-Archives-Hash: a68549b8defd2c06d470a038afebe847 On Fri, Jun 12, 2020 at 2:40 AM n952162 wrote: > > Presumably, 13.0, unless some process had already made the 13.0 -> 17.0 > jump without my knowledge. Ok, you're in fairly uncharted waters. The impact is mainly to gcc so if you haven't updated that then most likely nothing is broken yet, and you can probably update portage safely because it doesn't use gcc. However, you probably should rebuild libtool and then the toolchain after switching to a newer gcc. > > Well, yes, but it's really pretty onerous. If you have gentoo in > embedded systems, you've got to spend considerable administrative effort > in each one just maintaining the status quo. > > I mean, there's no competition to gentoo, of course. But a design goal > could be to have a one-step sync, of some sort. In such a situation you're probably better off managing that system more like a docker container. Build the entire image off-host from scratch instead of trying to upgrade it in place, and just migrate whatever data you have. You can still use Gentoo so that everything is tailored/etc, but you'd be generating a completely new image from scratch and just flashing it, vs trying to do updates on an embedded system. You really can't reliably do infrequent in-place updates on Gentoo systems. Sure, you can go a few months between updates, but the 17.0 profile came out in 2017... -- Rich