Jonathon Anderson

libassuan-devel ``` cd cmd/config_defaults && go build -ldflags="-X 'github.com/hpcng/warewulf/internal/pkg/warewulfconf.ConfigFile=./etc/warewulf.conf'\ -X 'github.com/hpcng/warewulf/internal/pkg/node.ConfigFile=./etc/nodes.conf'"\ -mod vendor -tags "containers_image_openpgp containers_image_ostree" -o ../../config_defaults go build -o ./wwapid internal/app/api/wwapid/wwapid.go # github.com/mtrmac/gpgme /usr/bin/ld: cannot find -lassuan collect2:...

@MatthewHink I was able to install the packages. My point is that they need to be listed as BuildRequires in the spec file.

@mslacken would you still expect the remaining items in the 4.4.0 milestone to be included in later RCs, or should they get moved to the 4.5.0 milestone (or otherwise)? https://github.com/hpcng/warewulf/milestone/3

I have as-yet been unable to build ipxe using `ipxe-update.sh`, but this is true before the changes as well. I tried using ipxe v1.21.1 explicitly, but then I got a...

@mslacken I've updated the x86_64 builds for ipxe, and I also added a new feature to `ipxe-update.sh` to allow an EMBED script to be supplied. (This is not used for...

The panic appears to be coming from https://go.googlesource.com/go/+/go1.1.1/src/pkg/crypto/sha256/sha256.go

It sounds like this occurred during a disk-full event. Can this be caught and handled without exposing a panic / traceback to the end user?

I'll take a look. Thanks, @gustavoberman!

This may be helped / alleviated with #819.

@griznog what'd you think of this?