Package Details: pyenv-virtualenv 1:1.2.4-1

Git Clone URL: https://aur.archlinux.org/pyenv-virtualenv.git (read-only, click to copy)
Package Base: pyenv-virtualenv
Description: pyenv plugin to manage virtualenv (a.k.a. python-virtualenv)
Upstream URL: https://github.com/pyenv/pyenv-virtualenv
Keywords: pyenv virtualenv
Licenses: MIT
Submitter: russo79
Maintainer: darkfish
Last Packager: darkfish
Votes: 34
Popularity: 0.37
First Submitted: 2015-11-15 10:31 (UTC)
Last Updated: 2024-07-22 05:16 (UTC)

Pinned Comments

darkfish commented on 2023-01-10 15:10 (UTC)

1.2.0 from upstream released. This package now installs under /usr/share/pyenv/plugins

Latest Comments

« First ‹ Previous 1 2 3 Next › Last »

ayr-ton commented on 2019-04-02 17:21 (UTC)

Thanks, @lans9831 :-)

quebin31 commented on 2019-04-02 16:13 (UTC) (edited on 2019-04-02 16:15 (UTC) by quebin31)

I added a fix for the issue with BASH_SOURCE pointing to /usr/libexec, using the patch file from pull #308, solving the issue #307, now there's no need to link/copy pyenv-virtualenv-realpath to /usr/libexec.

ayr-ton commented on 2019-02-14 03:06 (UTC)

I think it still need some tweaks. Will fix it with a version “-3” tomorrow.

ayr-ton commented on 2019-02-14 01:33 (UTC) (edited on 2019-02-14 01:38 (UTC) by ayr-ton)

@teyras @raugturi New version from pyenv-virtualenv community that should solves our issue :-)

ayr-ton commented on 2019-02-13 22:28 (UTC)

yyuu from pyenv-virtualenv community is working on a fix. Will wait for it so I could update the package with the proper fix.

ayr-ton commented on 2019-02-13 15:08 (UTC)

Issue reported here: https://github.com/pyenv/pyenv-virtualenv/issues/302

On the case pyenv-virtualenv community suggest something we could accomplish following the packages best practices I will apply on the package. Or, if they release a new version with a fix will update the package as well.

Best!

ayr-ton commented on 2019-02-13 15:00 (UTC)

@teyras If pyenv-virtualenv-realpath it should not exists on /usr/libexec/ I could not apply the workaround @raugturi proposed on the PKGBUILD. Will report a bug on pyenv-virtualenv GitHub page.

Teyras commented on 2019-02-12 21:10 (UTC) (edited on 2019-02-12 21:10 (UTC) by Teyras)

The error reported by @raugturi was introduced in this commit: https://github.com/pyenv/pyenv-virtualenv/commit/e0a1e9b35c2be386dbd91e686e57864690323a22

Using the BASH_SOURCE env variable leads to pyenv-virtualenv looking for /usr/libexec/pyenv-virtualenv-realpath, which does not (and should not) exist.

I'm not 100% sure who should address this error (PKGBUILD author or pyenv community)...

raugturi commented on 2019-02-12 08:04 (UTC) (edited on 2019-02-12 08:12 (UTC) by raugturi)

@ayr-ton I just created a copy of this file https://github.com/pyenv/pyenv-virtualenv/blob/master/libexec/pyenv-virtualenv-realpath at /usr/libexec/pyenv-virtualenv-realpath.

I'll dig into it more tomorrow to see if I can find out specifically which step it fails on when the file is missing though, because if my shell has a realpath function already (and it must have at some point) then this file shouldn't be required.

Update: It looks like realpath is part of coreutils. So I'll look at my machine more tomorrow and try to figure out why it's failing. This may just be a bug on my laptop and not a problem with the package.

ayr-ton commented on 2019-02-11 22:30 (UTC)

@raugturi Hey, could you describe the exact commands did you run to perform this workaround so I could see how to replicate this on the PKBUILD? Thanks for your time on this.

« First ‹ Previous 1 2 3 Next › Last »