Package Details: coreboot-utils-git 4.9.r1447.ge54c15aa729-1

Git Clone URL: https://aur.archlinux.org/coreboot-utils-git.git (read-only)
Package Base: coreboot-utils-git
Description: Tools and utilities to work with coreboot firmware
Upstream URL: https://www.coreboot.org/
Licenses: GPL
Submitter: anatolik
Maintainer: anatolik (mytbk)
Last Packager: anatolik
Votes: 11
Popularity: 0.084741
First Submitted: 2014-11-17 18:57
Last Updated: 2019-04-28 04:01

Latest Comments

1 2 3 Next › Last »

lisu_ml commented on 2019-08-27 12:23

This time the build fails with:

fatal: repository '/tmp/tmp.nUMmTUBl5r/coreboot-utils-git/ffs.git' does not exist
fatal: clone of '/tmp/tmp.nUMmTUBl5r/coreboot-utils-git/ffs.git' into submodule path '/tmp/tmp.nUMmTUBl5r/coreboot-utils-git/src/coreboot/3rdparty/ffs' failed
Failed to clone '3rdparty/ffs' a second time, aborting

eimis commented on 2019-08-10 18:16

fails with

go: cannot determine module path for source directory /tmp/yay/coreboot-utils-git/src/coreboot (outside GOPATH, no import comments)

je-vv commented on 2019-04-29 01:29

Yes it works !! Though I had to remove prior local copies of the repos, since for some reason when building coreboot, makepkg was always installing 4.8.r2370.gaaced4a932-1, instead of 4.9.r1447.ge54c15aa729-1, even though pkgver=4.9.r1447.ge54c15aa729. But by removing old repos, now everything works...

anatolik commented on 2019-04-28 04:02

je-vv@, could you please try now?

je-vv commented on 2019-04-27 23:16

getting the same fatal: pathspec 'coreboot' did not match any files as reported by @lisu_ml

lisu_ml commented on 2019-04-27 21:56

I'm actually now getting something different:

==> Extracting sources...
  -> Creating working copy of coreboot git repo...
Cloning into 'coreboot'...
done.
  -> Creating working copy of blobs git repo...
Cloning into 'blobs'...
done.
  -> Creating working copy of nvidia-cbootimage git repo...
Cloning into 'nvidia-cbootimage'...
done.
  -> Creating working copy of vboot git repo...
Cloning into 'vboot'...
done.
  -> Creating working copy of arm-trusted-firmware git repo...
Cloning into 'arm-trusted-firmware'...
done.
  -> Creating working copy of chrome-ec git repo...
Cloning into 'chrome-ec'...
done.
  -> Creating working copy of libhwbase git repo...
Cloning into 'libhwbase'...
done.
  -> Creating working copy of libgfxinit git repo...
Cloning into 'libgfxinit'...
done.
  -> Creating working copy of fsp git repo...
Cloning into 'fsp'...
done.
  -> Creating working copy of opensbi git repo...
Cloning into 'opensbi'...
done.
==> Starting prepare()...
fatal: pathspec 'coreboot' did not match any files
==> ERROR: A failure occurred in prepare().
    Aborting...

anatolik commented on 2019-04-25 20:40

lisu_ml@ the build problem is fixed

lisu_ml commented on 2019-04-24 20:27

It doesn't build again:

==> Starting prepare()...
Submodule 'arm-trusted-firmware' (/tmp/tmp.mG5bqjnWBa/coreboot-utils-git/arm-trusted-firmware.git) registered for path '3rdparty/arm-trusted-firmware'
Submodule '3rdparty/blobs' (/tmp/tmp.mG5bqjnWBa/coreboot-utils-git/blobs.git) registered for path '3rdparty/blobs'
Submodule '3rdparty/chromeec' (/tmp/tmp.mG5bqjnWBa/coreboot-utils-git/chrome-ec.git) registered for path '3rdparty/chromeec'
Submodule '3rdparty/fsp' (/tmp/tmp.mG5bqjnWBa/coreboot-utils-git/fsp.git) registered for path '3rdparty/fsp'
Submodule 'libgfxinit' (/tmp/tmp.mG5bqjnWBa/coreboot-utils-git/libgfxinit.git) registered for path '3rdparty/libgfxinit'
Submodule 'libhwbase' (/tmp/tmp.mG5bqjnWBa/coreboot-utils-git/libhwbase.git) registered for path '3rdparty/libhwbase'
Submodule 'opensbi' (/tmp/tmp.mG5bqjnWBa/coreboot-utils-git/opensbi.git) registered for path '3rdparty/opensbi'
Submodule 'vboot' (/tmp/tmp.mG5bqjnWBa/coreboot-utils-git/vboot.git) registered for path '3rdparty/vboot'
fatal: No url found for submodule path 'coreboot' in .gitmodules
==> ERROR: A failure occurred in prepare().
    Aborting...

anatolik commented on 2018-12-02 00:36

lisu_ml, it was an issue with the package. I fixed it.

lisu_ml commented on 2018-12-01 22:13

It does now, it was probably upstream issue.