Closed ivan-hc closed 5 months ago
I'm stuck, I cannot compile packages from AUR
I've solved the issue with my workflows.
Also the build script on my fork is this
#!/usr/bin/env bash
# DOWNLOAD THE ARCHIVE
wget https://github.com/ivan-hc/junest/releases/download/continuous/junest-x86_64.tar.gz
# SET APPDIR AS A TEMPORARY $HOME DIRECTORY, THIS WILL DO ALL WORK INTO THE APPDIR
HOME="$(dirname "$(readlink -f $0)")"
# DOWNLOAD AND INSTALL JUNEST (DON'T TOUCH THIS)
git clone https://github.com/fsquillace/junest.git ~/.local/share/junest
./.local/share/junest/bin/junest setup -i junest-x86_64.tar.gz
# BYPASS SIGNATURE CHECK LEVEL
#sed -i 's/#SigLevel/SigLevel/g' ./.junest/etc/pacman.conf
#sed -i 's/Required DatabaseOptional/Never/g' ./.junest/etc/pacman.conf
# UPDATE ARCH LINUX IN JUNEST
./.local/share/junest/bin/junest -- sudo pacman -Syy
./.local/share/junest/bin/junest -- sudo pacman --noconfirm -Syu
# INSTALL YAY
./.local/share/junest/bin/junest -- sudo pacman --noconfirm -Rcns yay
./.local/share/junest/bin/junest -- sudo pacman --noconfirm -S --needed git base-devel
./.local/share/junest/bin/junest -- git clone https://aur.archlinux.org/yay.git
cd yay
echo yes | $HOME/.local/share/junest/bin/junest -- makepkg -si
cd ..
yayver=$(cat ./yay/PKGBUILD | grep "pkgver=" | head -1 | cut -c 8-)
./.local/share/junest/bin/junest -- sudo pacman --noconfirm -U ./yay/yay-"$yayver"*.zst ./yay/yay-debug-"$yayver"*.zst
# DEBLOAT
./.local/share/junest/bin/junest -- sudo pacman --noconfirm -Rcns base-devel go
echo yes | ./.local/share/junest/bin/junest -- sudo pacman -Scc
echo -e 'SUCCESS!\n'
@fsquillace I suggest you to keep updated your build using a script the way I do
Hey @ivan-hc thanks for the headsup. I updated the junest repo db with the latest yay
version. If you run sudo pacman -Sy yay
it should install the new version available. I should be able to fix the issue by periodically run the travis for this repo https://github.com/fsquillace/junest-aur-repo
Hi @fsquillace , the inbuilt YAY version is outdated and not compatible with the new PacMan release.
On my fork, at https://github.com/ivan-hc/junest I've solved like this (to update my releases):
note the steps where I remove
base-devel
again As you already know, I create AppImages based on JuNest and this night I received a lot of errors in my workflowsHowever, I still facing issues in build backages from AUR. I don't know if this is a YAY fault or something is changed in AUR about key signatures or something. See my latest workflows to build GIMP DEVEL https://github.com/ivan-hc/GIMP-appimage/actions/workflows/GIMP-DEVELOPER.yml