Package Details: python2-pip 20.3.4-1

Git Clone URL: https://aur.archlinux.org/python2-pip.git (read-only, click to copy)
Package Base: python2-pip
Description: The PyPA recommended tool for installing Python packages
Upstream URL: https://pip.pypa.io/
Licenses: MIT
Submitter: tallero
Maintainer: tallero (truocolo)
Last Packager: truocolo
Votes: 4
Popularity: 0.021719
First Submitted: 2022-09-30 01:06 (UTC)
Last Updated: 2024-02-17 17:39 (UTC)

Required by (3)

Sources (1)

Latest Comments

1 2 3 Next › Last »

LaughingMan commented on 2024-04-21 19:15 (UTC)

Package fails to build with the error "ModuleNotFoundError: No module named 'setuptools'" unless you happen to have python-setuptools installed.

Yes, that's the Python 3 version, which gets called for some reason.

sl1pkn07 commented on 2024-02-17 15:32 (UTC) (edited on 2024-02-17 15:38 (UTC) by sl1pkn07) 

package() {
  local \
    _bash_completions="${pkgdir}/usr/share/bash-completion/completions" \
    _fish_completions="${pkgdir}/usr/share/fish/vendor_completions.d" \
    _site_packages

  _site_packages=$("${_py}" -c "import site; print(site.getsitepackages()[0])")

  cd "${_pkg}-${pkgver}" || exit
  "${_py}" setup.py install \
    --prefix=/usr \
    --root="${pkgdir}"

  mv "${pkgdir}/usr/bin/${_pkg}" "$pkgdir/usr/bin/${_pkg}2"
  sed "s|#!/usr/bin/env python$|#!/usr/bin/env ${_py}|" \
    -i "${pkgdir}/${_site_packages}/pip/__init__.py"

  "${_py}" -m compileall "${pkgdir}/${_site_packages}/${_pkg}/__init__.py"
  install -Dm644 LICENSE.txt "${pkgdir}/usr/share/licenses/${pkgbase}/LICENSE"
  install -Dm644 -t "${pkgdir}/usr/share/man/man1" "docs/build/man-${_pkg}2/"*

  PYTHONPATH="${pkgdir}/${_site_packages}" "${pkgdir}/usr/bin/${_pkg}2" completion --bash | install -Dm644 /dev/stdin "${_bash_completions}/${_pkg}2"
  PYTHONPATH="${pkgdir}/${_site_packages}" "${pkgdir}/usr/bin/${_pkg}2" completion --fish | install -Dm644 /dev/stdin "${_fish_completions}/${_pkg}2.fish"
}

# vim:set sw=2 sts=-1 et:

sl1pkn07 commented on 2024-02-17 15:09 (UTC)

install: cannot create directory '/bash-completion': Permission denied

tallero commented on 2024-02-15 17:55 (UTC) (edited on 2024-02-15 17:55 (UTC) by tallero)

I am aware it may seem issues reported on this page are being neglected but they're not.

Let's be clear: the package works normally when building manually, yet I agree there is space for changes.

The reason this is taking so long to be solved is arm build fails on a subdependency.

I am currently bound to solve an almost 30 year long GRUB bug to access the x86 machine and I'm very near fixing that nasty bug though.

TJM commented on 2024-02-13 15:10 (UTC) (edited on 2024-02-13 15:12 (UTC) by TJM)

@tallero Actually, it crashed my AUR helper even with checkdepends disabled. I've opened an issue to the upstream, but I'm not sure whether it will be fixed. ¯\(ツ)/¯

Score_Under commented on 2024-02-13 14:50 (UTC) (edited on 2024-02-13 14:52 (UTC) by Score_Under)

The _pshare variable doesn't work for me; since it's in a single local command, they all get set at the same time (when local executes), so _pshare is undeclared at the time it is used and causes makepkg to attempt (and fail) to write to a /bash-completion directory outside pkgdir.

I have worked around all the initial build issues by adding the following to the end of the PKGBUILD (because that's what's simplest for my current build script setup):

_old_pkg_f=$(declare -f package)
package()
{
  _pshare="${pkgdir}/usr/share"
  unset -f package
  eval "$_old_pkg_f"
  package "$@"
}

makedepends+=(python-setuptools)
checkdepends=()

check() { :; }

Summary of issues:

  1. Circular dependency (addressed beforehand)
  2. Missing python3 setuptools dependency
  3. local variables being declared simultaneously but written with the assumption that they are declared one after the other.

Compare:

#!/usr/bin/env bash
x(){
  a=b b=$a
  echo $b
}
x

vs

#!/usr/bin/env bash
x(){
  local a=b b=$a
  echo $b
}
x

note how adding local breaks the function. (make sure a & b are unset between runs of this if you're pasting rather than running as scripts)

It's also worth noting that some packages no longer exist inside or outside of the AUR:

  • python2-virtualenv
  • python2-pytest-rerunfailures
  • python2-pytest-xdist
  • python2-scripttest

tallero commented on 2024-02-08 07:00 (UTC) (edited on 2024-02-08 07:10 (UTC) by tallero)

@TJM: as written below, you first build and install without checkdepends and then you rebuild after checkdepends are installed.

In case, yes, as far as I remember this has always been the procedure even when these packages were in the binary repos.

On a sidenote, binary repos should currently instead have a non-checkdepends loop on python-build/python-setuptools after it has been chosen to adapt recipes of python-setuptools deps to use python-build instead of their old native install method (being python-build mostly a front-end to other packaging suites), but you only notice if you try to build the whole tree from sources.

So, if you seem to end up with a seemingly dependency loop it could probably be an issue of your aur helper.

Up to last time I've checked nobody has ever fixed the checkdepends loops in AUR helpers and as far as I know there are no more actively developed AUR helpers, except for the one I'm writing for the Ur, which still does not include dependencies trees parsing.

TJM commented on 2024-02-08 05:42 (UTC)

It appears that this package has a dependency on itself. Is this an error or is there a bootstrap package that can break the loop?

truocolo commented on 2024-02-05 16:35 (UTC) (edited on 2024-02-05 16:45 (UTC) by truocolo)

c0del1ar:

please read the comment below, and check the activity tracker there linked.

It's monday morning guys, I asked you on saturday night to be chill.

I mean, sundays are for the packages software, not for the software packages.

1 2 3 Next › Last »