From mboxrd@z Thu Jan 1 00:00:00 1970 From: ng0@n0.is Subject: Re: the upcoming Great Python2 =?utf-8?B?UHVyZ2Xvv70/77+9?= Date: Mon, 18 Feb 2019 16:54:15 +0000 Message-ID: <20190218165415.odkpx27fnz3ezcwf@uptimegirl.lan> References: <20181226093812.GR2581@macbook41> <20190218095619.GC7206@macbook41> <87o979wftc.fsf@elephly.net> <87h8d1we1v.fsf@elephly.net> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Return-path: Received: from eggs.gnu.org ([209.51.188.92]:43070) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gvmBX-0001O1-R9 for guix-devel@gnu.org; Mon, 18 Feb 2019 11:54:28 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gvmBX-0006jx-5U for guix-devel@gnu.org; Mon, 18 Feb 2019 11:54:27 -0500 Received: from aibo.runbox.com ([91.220.196.211]:41308) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1gvmBW-0006iK-Tk for guix-devel@gnu.org; Mon, 18 Feb 2019 11:54:27 -0500 Received: from [10.9.9.210] (helo=mailfront10.runbox.com) by mailtransmit03.runbox with esmtp (Exim 4.86_2) (envelope-from ) id 1gvmBS-0006Fl-Sr for guix-devel@gnu.org; Mon, 18 Feb 2019 17:54:22 +0100 Received: by mailfront10.runbox.com with esmtpsa (uid:892961 ) (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.82) id 1gvmBM-0007dE-RT for guix-devel@gnu.org; Mon, 18 Feb 2019 17:54:17 +0100 Content-Disposition: inline In-Reply-To: List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: guix-devel@gnu.org Konrad Hinsen transcribed 1.2K bytes: > Hi Ricardo, > > >> "My channel" doesn't exist (because I haven't yet found the time to > >> figure out how to set up and manage a channel, although it's been on my > >> to-do list for a while). > > > > I’d be happy to assist. > > Thanks! I might come back to that offer when I find at least enough time > to figure out precisely what information I might be lacking > (that's meta-lack-of-time). > > >> But... how about splitting off *all* of Python 2 and everything that > >> depends on it into a separate channel, which would then be maintained > >> by a separate team? > > > > Currently this is not feasible, in my opinion, as a lot of packages in > > Guix still depend on Python 2 for some reason or the other. When Python > > 2 reaches EOL, however, I think this would be a reasonable thing to do. > > Sounds good, then the only remaining issue is defining a transition > protocol. What I'd like to avoid is that packages disappear one by one > from Guix and then have to be dug out one by one from Git history for > setting up a Python 2 channel. > > More generally, I think it would be useful to collect in some place all > package definitions that are removed from Guix. For example, a list with > package names plus the last Guix commit that had the package. > > Konrad. > > package number one which will stay on python2: getmail. In exchanges with the maintainer on their mailinglist it was made clear that Charles has no intention to port it to python3, as except for a few minor additions and fixes, getmail is in maintenance mode.. you get releases every now and then.