Path: csiph.com!feeder.erje.net!2.eu.feeder.erje.net!news.etla.org!aioe.org!bofh.it!news.nic.it!robomod From: Andreas Tille Newsgroups: linux.debian.maint.python,linux.debian.bugs.dist Subject: How to make sure PATH is set correctly (Was: foo FTBFS with dh-python >= 3.20180313) Date: Mon, 07 May 2018 14:10:02 +0200 Message-ID: References: X-Original-To: debian-python@lists.debian.org X-Mailbox-Line: From debian-python-request@lists.debian.org Mon May 7 12:09:05 2018 Old-Return-Path: X-Amavis-Spam-Status: No, score=-4.9 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, FOURLA=0.1, LDO_WHITELIST=-5, MEDS2=2, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=no autolearn_force=no X-Policyd-Weight: using cached result; rate:hard: -6.1 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: NeoMutt/20170113 (1.7.2) X-Mailing-List: archive/latest/15907 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/20180507120848.444pe5k65ybixprj@an3as.eu Approved: robomod@news.nic.it Lines: 81 Organization: linux.* mail to news gateway Sender: robomod@news.nic.it X-Original-Cc: 894213@bugs.debian.org X-Original-Date: Mon, 7 May 2018 14:08:48 +0200 X-Original-Message-ID: <20180507120848.444pe5k65ybixprj@an3as.eu> X-Original-References: <20180426094152.lxnmpce34f3yrtdf@an3as.eu> <20180426100117.km5zao3pr7oftnir@sar0.p1otr.com> <20180430122823.xth6am67pvxkrzxx@an3as.eu> <20180430135751.qvvjmklkvczoj2hs@sar0.p1otr.com> <20180430175210.pwgn6yn7gzucyhw4@an3as.eu> <20180430182913.xpyxaxo5e3nna7nr@sar0.p1otr.com> <20180430211344.jd43a4nw7b2ie7hy@an3as.eu> Xref: csiph.com linux.debian.maint.python:10503 linux.debian.bugs.dist:896534 Hi again, sorry for nagging again but what else than I did in https://salsa.debian.org/med-team/snakemake/blob/master/debian/rules can I do to set PATH in pbuilder. Possibly I've understand all your hints incorrectly - the PATH is just not set inside pbuilder chroot. :-( Kind regards Andreas. On Mon, Apr 30, 2018 at 11:13:44PM +0200, Andreas Tille wrote: > On Mon, Apr 30, 2018 at 08:29:13PM +0200, Piotr Ożarowski wrote: > > [Andreas Tille, 2018-04-30] > > > Hmmm, inside pbuilder chroot the files are installed to > > > > > > /build/snakemake-4.8.0/.pybuild/cpython3_3.6_snakemake/build/bin/snakemake > > > > > > while > > > > > > # pybuild --print build_dir --interpreter python3 > > > /build/snakemake-4.8.0/.pybuild/cpython3_3.6/build > > > > you invoked it outside debian/rules, without --name or PYBUILD_NAME set, > > right? > > Yes, that's right. > > > > I have no idea why since some dh-python version things are different > > > than before but wouldn't it be the best idea to let pybuild set PATH and > > > PYTHONPATH instead of setting it manually by some manual command? > > > > I meant to fix also debian/rules line 11 (you fixed line 21 only) > > I commited my last attemt to Git fixing PATH on both lines. > > I get with this d/rules: > > > ... > raise Exception("snakemake not in PATH. For testing, install snakemake with " > Exception: snakemake not in PATH. For testing, install snakemake with 'pip install -e .'. You should do this in a separate environment (via conda or virtualenv). > > ---------------------------------------------------------------------- > Ran 4 tests in 0.187s > > FAILED (errors=1) > E: pybuild pybuild:336: test: plugin distutils failed with: exit code=1: cd /build/snakemake-4.8.0/.pybuild/cpython3_3.6_snakemake/build; python3.6 -m nose tests > dh_auto_test: pybuild --test --test-nose -i python{version} -p 3.6 returned exit code 13 > make: *** [debian/rules:17: build] Error 25 > dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2 > I: copying local configuration > E: Failed autobuilding of package > I: user script /var/cache/pbuilder/build/cow.11501/tmp/hooks/C99_failed_build starting > root:/# echo $PATH > /usr/sbin:/usr/bin:/sbin:/bin > > > I have no idea why but the PATH does not make it through. > > I confirm if I set > > root:/build/snakemake-4.8.0# export PYBUILD_NAME=snakemake > root:/build/snakemake-4.8.0# pybuild --print build_dir --interpreter python3 > /build/snakemake-4.8.0/.pybuild/cpython3_3.6_snakemake/build > > But why does these variables not end up in the chroot? > > Kind regards > > Andreas. > > -- > http://fam-tille.de > > -- http://fam-tille.de