Search Criteria
Package Details: pixiecore-git r353.64f6de6-2
Package Actions
| Git Clone URL: | https://aur.archlinux.org/pixiecore-git.git (read-only, click to copy) |
|---|---|
| Package Base: | pixiecore-git |
| Description: | An all-in-one tool for easy netbooting |
| Upstream URL: | https://godoc.org/go.universe.tf/netboot/pixiecore |
| Keywords: | ipxe netboot pxe |
| Licenses: | Apache |
| Conflicts: | pixiecore |
| Provides: | pixiecore |
| Submitter: | xotkot |
| Maintainer: | naritanara |
| Last Packager: | naritanara |
| Votes: | 4 |
| Popularity: | 0.000053 |
| First Submitted: | 2018-07-30 10:17 (UTC) |
| Last Updated: | 2023-09-17 17:47 (UTC) |
Dependencies (4)
- binutils (make)
- gcc (gcc-gitAUR, gccrs-gitAUR, gcc11AUR, gcc-snapshotAUR) (make)
- git (git-gitAUR, git-glAUR) (make)
- go (go-gitAUR, gcc-go-gitAUR, go-sylixosAUR, gcc-go-snapshotAUR, gcc-go) (make)
Latest Comments
onde2rock2 commented on 2023-02-27 19:32 (UTC)
Does not build. But it is a quick fix, upstream branch changed from
mastertomainthurstylark commented on 2022-01-17 05:56 (UTC)
NBD, looks like there's a build failure caused by upstream as well, so it's not just the prepare function at the moment :P
sanerb commented on 2022-01-17 05:24 (UTC)
@thurstylark looks like that changed that advisory; it used to be explicitly recommended to not include it as a makedepends. i'll have to clean up my packages over the next week or so.
thurstylark commented on 2022-01-17 05:15 (UTC) (edited on 2022-01-17 05:23 (UTC) by thurstylark)
This package requires the
gitpackage to be added to makedepends. Currently this package fails to build in a clean chroot. Reference: https://wiki.archlinux.org/title/VCS_package_guidelines#GuidelinesAlso the prepare function fails because the initramfs patch has been adopted upstream: https://github.com/danderson/netboot/pull/128
Also your flyspray server is borked :P
ZenithCC commented on 2021-06-18 01:37 (UTC)
A PR#128 was merged in the upstream recently. It seems that the patch is not needed now.
sanerb commented on 2021-06-10 19:23 (UTC)
@ZenithCC-
Thanks for OODing this, I would have never noticed the breakage otherwise.
Upstream is more or less dead as it's not really maintained, so I've had to patch it myself. Should be working now.