Closed Efadd closed 2 years ago
Under the gpg call.
The screenshot you've given really isn't that informative, it appears to show the command to install python and the output from reinstalling devkitPro pacman. You can just copy text from your terminal & paste it here within code tags as I've done here
I've checked a fresh install on aarch64 and it's working fine for me. You can try purging the install & starting over.
Purge the failed install
sudo apt-get remove devkitpro-pacman --purge
sudo rm -fr /opt/devkitpro
Install from scratch. Make sure you've deleted devkitpro-pacman.arm64.deb if you have it already
wget https://github.com/devkitPro/pacman/releases/download/v1.0.2/devkitpro-pacman.arm64.deb
sudo gdebi devkitpro-pacman.arm64.deb
This is the output from my fresh install and what I'd expect to see.
$ sudo gdebi devkitpro-pacman.arm64.deb
[sudo] password for davem:
Reading package lists... Done
Building dependency tree
Reading state information... Done
Reading state information... Done
devkitPro package manager
A lightly customised build of arch pacman used to manage the tools and libraries maintained and distributed by devktPro.
Do you want to install the software package? [y/N]:y
/usr/bin/gdebi:113: FutureWarning: Possible nested set at position 1
c = findall("[[(](\S+)/\S+[])]", msg)[0].lower()
Selecting previously unselected package devkitpro-pacman.
(Reading database ... 189993 files and directories currently installed.)
Preparing to unpack devkitpro-pacman.arm64.deb ...
Unpacking devkitpro-pacman (1.0.2) ...
Setting up devkitpro-pacman (1.0.2) ...
gpg: /opt/devkitpro/pacman/etc/pacman.d/gnupg/trustdb.gpg: trustdb created
gpg: no ultimately trusted keys found
gpg: starting migration from earlier GnuPG versions
gpg: porting secret keys from '/opt/devkitpro/pacman/etc/pacman.d/gnupg/secring.gpg' to gpg-agent
gpg: migration succeeded
gpg: Generating pacman keyring master key...
gpg: key B0E06584C8BE71F8 marked as ultimately trusted
gpg: directory '/opt/devkitpro/pacman/etc/pacman.d/gnupg/openpgp-revocs.d' created
gpg: revocation certificate stored as '/opt/devkitpro/pacman/etc/pacman.d/gnupg/openpgp-revocs.d/AB898846290BF1936D67A9DBB0E06584C8BE71F8.rev'
gpg: Done
==> Updating trust database...
gpg: marginals needed: 3 completes needed: 1 trust model: pgp
gpg: depth: 0 valid: 1 signed: 0 trust: 0-, 0q, 0n, 0m, 0f, 1u
==> Appending keys from devkitpro.gpg...
==> Locally signing trusted keys in keyring...
-> Locally signing key 032F4C9D0B8FF3BC84019B7862C7609ADA219C60...
-> Locally signing key BC26F752D25B92CE272E0F44F7FD5492264BB9D0...
==> Importing owner trust values...
gpg: setting ownertrust to 4
gpg: setting ownertrust to 4
==> Updating trust database...
gpg: marginals needed: 3 completes needed: 1 trust model: pgp
gpg: depth: 0 valid: 1 signed: 2 trust: 0-, 0q, 0n, 0m, 0f, 1u
gpg: depth: 1 valid: 2 signed: 0 trust: 0-, 0q, 0n, 2m, 0f, 0u
:: Synchronising package databases...
dkp-libs 155.5 KiB 2.37M/s 00:00 [##################################################################] 100%
dkp-linux 18.5 KiB 0.00B/s 00:00 [##################################################################] 100%
Just as a matter of interest, which particular ARM based chromebook are you using?
A Lenovo C330, and that worked! Thanks!
I've installed Ubuntu Bionic on my ARM-based Chromebook and the custom pacman build won't install, and
the regular (edit: this is not "regular" pacman. This is a pacmanesqe front-end for apt. I'll attach a screenshot with the error, but I also had to nano make the conf file, with just some new lines to give nano something to save. Any suggestions?https://gitlab.com/TriVoxel/deb-pacman/-/releases
) pacman deb build can't find the devkitPro repos