related to https://github.com/gokrazy/gokrazy/issues/264
Currently, both the gokrazy/firmware and the gokrazy/kernel.rpi repository
contain an overlays directory. The desired state is that only gokrazy/kernel.rpi
contains an overlays directory, as that is the repository from which the
overlays are built (whereas the are only copied into the firmware repository).
To prevent confusion between different versions, the packer now returns an error
instead of silently overwriting files on the boot partition when there are
multiple sources for a file.
Before this change, the packer created an empty directory unconditionally,
which resulted in surprising errors in programs like breakglass.
closes https://github.com/gokrazy/breakglass/issues/19
The /var directory is meant to hold data that changes (see hier(7)).
With the previous behavior, users had to bind-mount a writable
and persistent directory over /var, for example as documented in
https://gokrazy.org/packages/docker-containers/
With this commit, there is one fewer hurdle to get podman running.
The sumdb/dirhash package was built to work with extracted Go module zip files,
but we are working with directories on local disk (working copies).
So, to reflect what the Go tool would see as source code,
we now use the same code.
Specifically, the old approach failed with symbolic links to directories,
because it treated them as regular files (Go module zips do not contain
irregular files such as symlinks).
prior to this commit SBOMs would have inconsistency in their hashing on
the configuration file.
The representation of the config file in fact would differ at certain
stages of the gok commands lifecycle, where at packer running time,
an extra InternalCompatibilityFlag, Sudo, would be added in memory
(while that not being the case at `gok sbom` time),
resulting in a differing config and as such differing SBOM hashes, same
goes for the differing pointer addresses that were skew the hashing
results.
This is now fixed by using the SudoOrDefault() accessor,
as well as converting the config into a string before computing the hash,
to avoid differing pointer problems.
A bug was triggered when the file system contained two directories with the same
basename, because all directories were incorrectly associated with the root
directory.
fixes https://github.com/gokrazy/tools/issues/58
This can happen when adding a program called "hello",
when the default config already pulls in github.com/gokrazy/hello.
The previous error message was confusing and non-deterministic,
because it contained the name of whichever package happens to be
validated first.
This is not a real fix. I still haven't figured out why a `connection
reset by peer` happens in the first place. `target.Reboot()` will still
block for a bit before giving up. At least it doesn't falsely report a
fail now.
Also moved canc() up so the terminal isn't littered with `[update boot
file system] 0.00% of 16 MiB, uploading at 0 B/s` during the wait.
Related: https://github.com/gokrazy/gokrazy/issues/199
We do this by using the dirhash package, but filtering out any hidden
files (starting with .) and using hash/fnv because we are not interested in
cryptographically secure hashes of local directory contents, just whether the
contents changed.
fixes https://github.com/gokrazy/gokrazy/issues/171
