From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp1 ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms11 with LMTPS id 6OliDMmFE2A8MQAA0tVLHw (envelope-from ) for ; Fri, 29 Jan 2021 03:49:29 +0000 Received: from aspmx1.migadu.com ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp1 with LMTPS id iCIMCMmFE2BuBwAAbx9fmQ (envelope-from ) for ; Fri, 29 Jan 2021 03:49:29 +0000 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 aspmx1.migadu.com (Postfix) with ESMTPS id 9D2E9940430 for ; Fri, 29 Jan 2021 03:49:28 +0000 (UTC) Received: from localhost ([::1]:40464 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1l5Kml-0002D0-Bj for larch@yhetil.org; Thu, 28 Jan 2021 22:49:27 -0500 Received: from eggs.gnu.org ([2001:470:142:3::10]:55358) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1l5Kmc-0002Cp-IP for guix-devel@gnu.org; Thu, 28 Jan 2021 22:49:18 -0500 Received: from mail-qk1-x72a.google.com ([2607:f8b0:4864:20::72a]:36134) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1l5Kma-0002Sf-QY for guix-devel@gnu.org; Thu, 28 Jan 2021 22:49:18 -0500 Received: by mail-qk1-x72a.google.com with SMTP id 19so7623322qkh.3 for ; Thu, 28 Jan 2021 19:49:16 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:to:cc:subject:references:date:in-reply-to:message-id :user-agent:mime-version:content-transfer-encoding; bh=43ETIoipk060wzpySXotFWM2SNgHGnrs671TOKDX3Co=; b=LMcvWBcqq04bSH0UJfGr7mW2bXsNA8908dNy0mbi4XrXcp0JxHlben8xyuqlLm9MXl P3QQ0g+ffSMmyy3xnuqqrWVXzReRbITgOX7QCymteinNeVmFzpAP9ehatONPbvs5cQQL dWbpIEEdU0/FVmjSiO9c5M52XP50l9MPBGCt3rDGm4Aa22A5qcaAfr0Q7iaDHY6Jv2K5 YlHV6gL5lTZVDxz96jXFp9ksE5K7XWe2FI5ZDCPGdSth8kktuwTnfIkT8M84hSZ5BOwY 6Esca/cypzuf2Kvzntv23V1DOgy4mj4IFOLzYI4XFhtmKyr1A/NyU6jpWMP+oS68inAn DBOA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:references:date:in-reply-to :message-id:user-agent:mime-version:content-transfer-encoding; bh=43ETIoipk060wzpySXotFWM2SNgHGnrs671TOKDX3Co=; b=lZEmkf2i+YrC23kDmQWqhmEGtsFDJYlbr24WJBITvs+71D8Ifkq8zyMZyELzp4NNz9 LbD9dUdTyNxKhQ8WWQ2Kb+L7uqjXOr+v5+Qz0O3pjkETsO0gK8r4qgSqd/p9oZuotofL ANXkBW71F7aIPb8Cj5Qh2cwvoYqJCUZVRk7jRsWBi+UrXbs6lqOJRIACoUpaOpzpBqcw B/aWS4b7NsWbJn7K3OnBrG2pxmW0pGJKO57YI0TXoKE/wxvEJssRIpe0XKS8AhvCz3Pj hMLNF6Xvs/V5+z6RORViiXowzKYamr2XbdwhVOEKTRSKOxu9thyzZhDcohnwkdKdP9GA 8few== X-Gm-Message-State: AOAM532zTxrbG98SmeoKtYMLMEikSDb6BD7XhW5ep2VnMw126RzR0BBj h9icJaQ7eaopHcwmsPZLd2dqUJJ7Bbs= X-Google-Smtp-Source: ABdhPJzmWvmdLkxK4C7nPNLwmcrNWl8tzDG0tAbeKoK8lvBjaqZLYx210PO4r/w0eto2N30COeFitw== X-Received: by 2002:a37:4fc4:: with SMTP id d187mr2543380qkb.200.1611892155289; Thu, 28 Jan 2021 19:49:15 -0800 (PST) Received: from hurd (dsl-10-141-243.b2b2c.ca. [72.10.141.243]) by smtp.gmail.com with ESMTPSA id c12sm4923891qkg.118.2021.01.28.19.49.13 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 28 Jan 2021 19:49:14 -0800 (PST) From: Maxim Cournoyer To: zimoun Subject: Re: Python 2 EOL starts to break packages References: <86pn1pgf7z.fsf@gmail.com> Date: Thu, 28 Jan 2021 22:49:13 -0500 In-Reply-To: <86pn1pgf7z.fsf@gmail.com> (zimoun's message of "Thu, 28 Jan 2021 18:10:08 +0100") Message-ID: <87pn1oxv0m.fsf@gmail.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.1 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Received-SPF: pass client-ip=2607:f8b0:4864:20::72a; envelope-from=maxim.cournoyer@gmail.com; helo=mail-qk1-x72a.google.com X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: guix-devel@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: Guix Devel Errors-To: guix-devel-bounces+larch=yhetil.org@gnu.org Sender: "Guix-devel" X-Migadu-Flow: FLOW_IN X-Migadu-Spam-Score: -3.05 Authentication-Results: aspmx1.migadu.com; dkim=pass header.d=gmail.com header.s=20161025 header.b=LMcvWBcq; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (aspmx1.migadu.com: domain of guix-devel-bounces@gnu.org designates 209.51.188.17 as permitted sender) smtp.mailfrom=guix-devel-bounces@gnu.org X-Migadu-Queue-Id: 9D2E9940430 X-Spam-Score: -3.05 X-Migadu-Scanner: scn0.migadu.com X-TUID: cRVnz3zl5taT Hi Simon, zimoun writes: [...] > Removing =E2=80=99python2-setuptools=E2=80=99 from Guix could break some = other packages. > Maybe? Who knows? ;-) > > Instead, a plan could be: > > a) move all the =E2=80=99python2-=E2=80=99 to their own module > say (gnu packages python2-xyz) > b) pin the ones which breaks; pin meaning =C2=ABnot use package-with-pyt= hon2=C2=BB=20 > c) fix a deadline announcing the remove of availability at user level > d) after this date, hide all the python2 packages > e) remove case per case these hidden python2 packages I think that's more involved than it needs to be. Here's how I've been slowly getting at the Python 2 issues: Whenever I update a Python package that breaks its Python 2 variant, I look at the dependencies of those variants with 'guix refresh -l python2-something'. If all the dependents are purely python2 variants themselves, then I proceed to remove them all from the package collection. If instead some non-python2 variant package depends on it, I research if that package could be updated to make it Python 3 compatible. If yes, then problem solved. Otherwise we need to ping upstream and keep it for a little longer before it gets removed. > Today, it does not make sense to have =E2=80=99python2-setuptools=E2=80= =99 in a manifest > file or type =E2=80=98guix install python2-setuptools=E2=80=99. So it sh= ould not be > possible and raise =E2=80=9Cpackage does not exist=E2=80=9D. However, I = could have a > custom package that depends on =E2=80=99python2-setuptools=E2=80=99 so it= should be > accessible via =E2=80=9C#:use-modules (gnu packages python2-xyz)=E2=80=9D. Let's apply this to the current case: $ guix refresh -l python2-setuptools Building the following 3 packages would ensure 7 dependent packages are rebuilt: python2-behave-web-api@1.0.6 grocsvs@0.2.6.1-1.ecd956a syncthing-gtk@0.9.4.4 The python2-behave-web-api is not a concern (there's an existing python-behave-web-api package), but the others are. There's an issue about syncthing-gtk reliance on Python 2 at https://github.com/kozec/syncthing-gtk/issues/568. For grocsvs I've just commented at https://github.com/grocsvs/grocsvs/issues/6. If the upstream are not willing to budge, the packages can be removed after a grace period (6 months, I'd say). Does that help? Maxim