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 414B3138334 for ; Fri, 6 Dec 2019 13:53:03 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 943D7E08F4; Fri, 6 Dec 2019 13:52:58 +0000 (UTC) Received: from mail-pf1-f169.google.com (mail-pf1-f169.google.com [209.85.210.169]) (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 58D4BE08A8 for ; Fri, 6 Dec 2019 13:52:58 +0000 (UTC) Received: by mail-pf1-f169.google.com with SMTP id x184so1951022pfb.3 for ; Fri, 06 Dec 2019 05:52:58 -0800 (PST) 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=6cmNuJHBEhoXuX8B/eE6USw7pfVznQnnkk9I+rCrTyM=; b=lscTJpDVB5/oeVgst2g+SUoCcs4T7lu0HB6AYZlR6nWpX9qTOs+L4S1jKXKbIbvYNz NgSUVUm2HKI0qxpqnTpAEQ/Powm7sK/6NcWZsx1vy0mLVvozHJ2nW76ULF722UguPBtU Clyh61T/zFBS+aYUwO4r3t5BeXmKScvtx/s4UcZWJIVjYrQW8+qw6Yym0y4q25f5/Zuw +E8egAaivOtdyoDe5E65LVEiHLOAr3JRYk1b35e9RL44ylNmhGx8TfZcqrDAkkvUN5p1 78CNmPsxhwRY1JGUY5/JbtA+9aIJg7AFh936jeHScdZ1l+i9j8ORxxuzj020KMzaLykc m65g== X-Gm-Message-State: APjAAAUlB17sC1H7c3NUuBtJUysMulFAKmYuYw/jTC1LZL9EzJTRvtgb xFzsAK+x4DOu4umzAbG5hT5Srye1Kku3rGOEbdatQ40k X-Google-Smtp-Source: APXvYqz1D7+WaqEMa8tUoV4q52ngEQPMPM6wVvzpT4zaa4a3v8W5vdk3c659j+/GXA3urngt8EqjSkladiCmP4XOHsw= X-Received: by 2002:aa7:968b:: with SMTP id f11mr14779190pfk.209.1575640376849; Fri, 06 Dec 2019 05:52:56 -0800 (PST) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply MIME-Version: 1.0 References: <51dddccd576fb1203457a09f305bac5a48eaae6c.camel@gentoo.org> <20f5820a902edd121bd49195c4adc2f5cea84fa8.camel@gentoo.org> <33a433c0-b547-7be6-f61a-1cf29b92328a@gentoo.org> In-Reply-To: <33a433c0-b547-7be6-f61a-1cf29b92328a@gentoo.org> From: Rich Freeman Date: Fri, 6 Dec 2019 08:52:45 -0500 Message-ID: Subject: Re: [gentoo-dev] unsanctioned python 2.7 crusade To: gentoo-dev Content-Type: text/plain; charset="UTF-8" X-Archives-Salt: 76831013-8ff2-417c-9df2-15013d1db4a5 X-Archives-Hash: c4434c90741b6a1971c608573d6dde9b On Fri, Dec 6, 2019 at 8:06 AM Thomas Deutschmann wrote: > > Sure, if packages don't work anymore or are blocking something, we will > start last-rite process. But for the sabnzbd example (I haven't looked > closely on any other package from that list) there isn't anything > blocking and it's a working piece of software. The only thing which > stands out is: It's a Py2-only package. > Well, that's simple enough. If the python maintainers intend to remove python2 then they need to remove anything that depends on it at the same time. Otherwise all those packages are going to break anyway and users just end up with a mess of error messages due to a broken depgraph. That said, as I've already commented I think it makes more sense to mask the reverse dependencies at the same time as masking python2 itself. And of course for something this big it wouldn't have hurt to announce the plans and what was going to get masked so that mistakes could get caught. Even though it is just a mask it is still a bit disruptive to have packages masked/unmasked because of incorrect identification of reverse/optional deps. Ultimately though it is up to the python2 maintainers to decide when they want to remove it. If others want to step up and replace them as python2 maintainers and they have a reasonable plan for keeping it working that would seem like the approach that would make the most people happy. We can't force people to maintain python2 if they don't want to. -- Rich