Dan Nicholson
Dan Nicholson
I was trying to run the ostree testsuite unprivileged in podman using fuse-overlayfs and the sysroot immutability handling fails with `EIO` rather than `EPERM`, `ENOTSUPP` or `ENOTTY`. To wit: ```...
We use a couple custom metadata keys at Endless and I often can't remember their names. I currently run `ostree show --raw` and then pick out the keys from the...
If the caller requests `subdirs` in the pull options, then static deltas should not be used since they explicitly asked for a partial tree. There's probably a tradeoff there where...
The handling of the `subdirs` pull option allows a single file to be fetched rather than a directory, but it's not documented anywhere. Both the `subdirs` pull option (and older...
The metadata size limit is currently [defined](https://github.com/ostreedev/ostree/blob/c6c3c5ae9fbeaaa2207149ed348109400b88314e/src/libostree/ostree-core.h#L38) as 10 MB and is documented as an arbitrary limit. Unfortunately, flathub has hit that limit for the summary file and has had...
This is similar to git-describe(1) in that it takes a commit checksum and describes the commit in terms of refs. This is useful if you have a repository with a...
Currently flat-manager only uses the repo secret to verify the JWT used for authenticated requests. The token itself is created by the authorization server. It would be better if flat-manager...
Make a couple more config parameters optional.
By default, ostree places a 10MB maximum size when pulling metadata files. This includes summary files, which can be very large for flatpak repos since they contain considerable per-ref metadata....
I'm not sure the best way to do this, but it would be nice to expose the options variant (or some subset of it) from `ostree_repo_pull_with_options` in the various install...