Closed marek22k closed 3 months ago
Workaround:
$ pyenv global system
If the global Python version is not used, a number of errors appear:
$yay -S vrms-arch-git Sync Dependency (1): pyalpm-0.10.6-5 AUR Explicit (1): vrms-arch-git-2.0.1.r0.g637e123-1 :: PKGBUILD up to date, skipping download: vrms-arch-git 1 vrms-arch-git (Build Files Exist) ==> Packages to cleanBuild? ==> [N]one [A]ll [Ab]ort [I]nstalled [No]tInstalled or (1 2 3, 1-3, ^4) ==> 1 vrms-arch-git (Build Files Exist) ==> Diffs to show? ==> [N]one [A]ll [Ab]ort [I]nstalled [No]tInstalled or (1 2 3, 1-3, ^4) ==> ==> Making package: vrms-arch-git 2.0.1.r0.g637e123-1 (Wed 29 Nov 2023 10:19:56 PM UTC) ==> Retrieving sources... -> Updating vrms-arch git repo... ==> WARNING: Skipping verification of source file PGP signatures. ==> Validating source files with sha256sums... vrms-arch ... Skipped :: (1/1) Parsing SRCINFO: vrms-arch-git resolving dependencies... looking for conflicting packages... Packages (1) pyalpm-0.10.6-5 Total Installed Size: 0.20 MiB :: Proceed with installation? [Y/n] (1/1) checking keys in keyring [######################] 100% (1/1) checking package integrity [######################] 100% (1/1) loading package files [######################] 100% (1/1) checking for file conflicts [######################] 100% (1/1) checking available disk space [######################] 100% :: Running pre-transaction hooks... (1/1) Checking Arch News with Informant ... There are no unread news items :: Processing package changes... (1/1) installing pyalpm [######################] 100% :: Running post-transaction hooks... (1/1) Arming ConditionNeedsUpdate... ==> Making package: vrms-arch-git 2.0.1.r0.g637e123-1 (Wed 29 Nov 2023 10:19:58 PM UTC) ==> Checking runtime dependencies... ==> Checking buildtime dependencies... ==> Retrieving sources... -> Updating vrms-arch git repo... ==> Validating source files with sha256sums... vrms-arch ... Skipped ==> Removing existing $srcdir/ directory... ==> Extracting sources... -> Creating working copy of vrms-arch git repo... Cloning into 'vrms-arch'... done. ==> Starting pkgver()... ==> Updated version: vrms-arch-git 2.0.2.r19.gd5fb44c-1 ==> Sources are ready. ==> Making package: vrms-arch-git 2.0.2.r19.gd5fb44c-1 (Wed 29 Nov 2023 10:20:00 PM UTC) ==> Checking runtime dependencies... ==> Checking buildtime dependencies... ==> WARNING: Using existing $srcdir/ tree ==> Starting pkgver()... ==> Removing existing $pkgdir/ directory... ==> Starting build()... /home/marek/.pyenv/versions/3.12.0/bin/python: No module named build ==> ERROR: A failure occurred in build(). Aborting... -> error making: vrms-arch-git-exit status 4 -> Failed to install the following packages. Manual intervention is required: vrms-arch-git - exit status 4
$python --version Python 3.12.0 $/usr/bin/python --version Python 3.11.6
After running pip3 install build another errors appears:
pip3 install build
$yay -S vrms-arch-git AUR Explicit (1): vrms-arch-git-2.0.1.r0.g637e123-1 :: PKGBUILD up to date, skipping download: vrms-arch-git 1 vrms-arch-git (Build Files Exist) ==> Packages to cleanBuild? ==> [N]one [A]ll [Ab]ort [I]nstalled [No]tInstalled or (1 2 3, 1-3, ^4) ==> 1 vrms-arch-git (Build Files Exist) ==> Diffs to show? ==> [N]one [A]ll [Ab]ort [I]nstalled [No]tInstalled or (1 2 3, 1-3, ^4) ==> ==> Making package: vrms-arch-git 2.0.1.r0.g637e123-1 (Wed 29 Nov 2023 10:21:27 PM UTC) ==> Retrieving sources... -> Updating vrms-arch git repo... ==> WARNING: Skipping verification of source file PGP signatures. ==> Validating source files with sha256sums... vrms-arch ... Skipped :: (1/1) Parsing SRCINFO: vrms-arch-git ==> Making package: vrms-arch-git 2.0.1.r0.g637e123-1 (Wed 29 Nov 2023 10:21:28 PM UTC) ==> Checking runtime dependencies... ==> Checking buildtime dependencies... ==> Retrieving sources... -> Updating vrms-arch git repo... ==> Validating source files with sha256sums... vrms-arch ... Skipped ==> Removing existing $srcdir/ directory... ==> Extracting sources... -> Creating working copy of vrms-arch git repo... Cloning into 'vrms-arch'... done. ==> Starting pkgver()... ==> Updated version: vrms-arch-git 2.0.2.r19.gd5fb44c-1 ==> Sources are ready. ==> Making package: vrms-arch-git 2.0.2.r19.gd5fb44c-1 (Wed 29 Nov 2023 10:21:31 PM UTC) ==> Checking runtime dependencies... ==> Checking buildtime dependencies... ==> WARNING: Using existing $srcdir/ tree ==> Starting pkgver()... ==> Removing existing $pkgdir/ directory... ==> Starting build()... * Getting build dependencies for wheel... running egg_info creating src/vrms_arch.egg-info writing src/vrms_arch.egg-info/PKG-INFO writing dependency_links to src/vrms_arch.egg-info/dependency_links.txt writing entry points to src/vrms_arch.egg-info/entry_points.txt writing top-level names to src/vrms_arch.egg-info/top_level.txt writing manifest file 'src/vrms_arch.egg-info/SOURCES.txt' reading manifest file 'src/vrms_arch.egg-info/SOURCES.txt' adding license file 'LICENSE.md' writing manifest file 'src/vrms_arch.egg-info/SOURCES.txt' ERROR Missing dependencies: wheel ==> ERROR: A failure occurred in build(). Aborting... -> error making: vrms-arch-git-exit status 4 -> Failed to install the following packages. Manual intervention is required: vrms-arch-git - exit status 4
If you use makepkg to build and install vrms as a system package, then yes, you should use the system's Python, not some virtual environment and not some other Python version located elsewhere.
makepkg
vrms
Workaround:
If the global Python version is not used, a number of errors appear:
After running
pip3 install build
another errors appears: