From mboxrd@z Thu Jan 1 00:00:00 1970 From: ng0 Subject: packaging the meta-searchenging searx fails at python-requests[socks] Date: Sat, 07 Jan 2017 15:32:42 +0000 Message-ID: <877f66sx5x.fsf@wasp.i-did-not-set--mail-host-address--so-tickle-me> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:54811) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cPsyr-0003n2-0e for guix-devel@gnu.org; Sat, 07 Jan 2017 10:32:30 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cPsyn-0002jD-Te for guix-devel@gnu.org; Sat, 07 Jan 2017 10:32:29 -0500 Received: from aibo.runbox.com ([91.220.196.211]:60751) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1cPsyn-0002iW-Mu for guix-devel@gnu.org; Sat, 07 Jan 2017 10:32:25 -0500 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 Hi, I have messed up my old searx branch and started new, visible here where you can also download the individual commits as patches etc. The python package definitions probably need to be cleaned up, please do no comment on the parts of the searx package which include a long commented section, I am aware of it and will clean it up before the next run, ideally I will add the dependencies and make it run at least one, if not all, optional tests. My problem is of a different nature right now. I am stuck with getting it to find python-requests. requirements.txt of searx includes this line[0]: requests[socks]==2.12.4 which should mean, build requests with propagated PySocks (socks) input. Okay, I have tried to add an modified PySocks which is more or less active maintained but is one version ahead of the version defined by requests here[1]: PySocks==1.5.6 Where I am packaging instead PySocks 1.5.7: https://pagure.io/guix-dev/c/7a2c54bd29b3cdea183919aad837cf71552d0d88?branch=searx2 I'm not sure what lead me to packaging of PySocks in september. I've tried to patch the requirements.txt to allow a different (or all) PySocks versions but this didn't work out. [0]: https://github.com/asciimoo/searx/blob/master/requirements.txt [1]: https://github.com/kennethreitz/requests/blob/master/requirements.txt -- ♥Ⓐ ng0 -- https://www.inventati.org/patternsinthechaos/