Package wreq-0.1.0.1 is broken due to missing package These broken packages must be rebuilt before they can Setup: The following installed packages are broken because other packages theyĭepend on are missing.
#Install arch linux macbook air 2013 upgrade#
Is there an easy way to force rebuilding of the dependencies? When trying to upgrade to 1.3.0.1-1: I was able to makepkg the PKGBUILD directly from AUR, not using aura, so I think it's a problem with aura. With gpg -recv-key I've added key 1D1F0DC78F173680 to root's, my normal user's, and pacman's (pacman-key). => ERROR: One or more PGP signatures could not be verified!Īura >= Would you like to continue anyway? FAILED (unknown public key 1D1F0DC78F173680) => Verifying source file signatures with gpg.
=> Validating source files with sha512sums. A couple of the packages (python3-xcgf and python3-xcpf) fail because aura fails to recognize the developer's public key (unknown public key):Īura >= Well, building `python3-xcgf` failed.Īura >= Dumping makepkg output in 3. I'm having an issue with installing powerpill using aura. (edited on 18:27 (UTC) by yochananmarqos) Tl dr: Having ghc as a hard dependency means it will be installed erroneously in setups where you already had stack installed, and worryingly may or may not make aura depend on dynamic libraries even if the user is using stack-static or similar tools to avoid that specific issue.
#Install arch linux macbook air 2013 how to#
In the end stack downloading ghc or 'ghc' downloading ghc, both will download it if it isn't there, only difference being stack's download isn't as obviously seen as a package by pacman, so maybe including a print out saying how to remove that downloaded data by stack if you don't want to just remove the package altogether.
That is, to my understanding having 'ghc' as a makedepends right now will force the installation of the ghc package, which you may not have despite having stack (all arch haskell packages are dynamically compiled for example, so in my case I use stack-static instead of 'ghc'), even if it may not be needed. you already have developed with haskell / using stack) the -system-ghc line will always work, even if you don't actually have a system ghc (which ghc supplies). From what I can tell when stack is installed normally before hand (i.e. I'd recommend placing 'ghc' as an optional dependency if at all.
0 kommentar(er)
