Dusty Mabe

hit this today with the `fwupd` package (more specifically `fwupdate-efi`) : ``` [root@dhcp137-98 ~]# rpm-ostree install fwupd ... error: Unpacking fwupdate-efi-8-2.fc26.x86_64: Unsupported path: /boot/efi; See https://github.com/projectatomic/rpm-ostree/issues/233 ```

another example of this is trying to package layer cuda from [nvidia](https://developer.download.nvidia.com/compute/cuda/repos/rhel7/x86_64/). The `cuda-license` package has files in /usr/local/: ``` Overlaying... error: Checking out cuda-license-9-0-9.0.176-1.x86_64: openat: No such file or...

> Why don't I see the Unsupported path: message PR to resolve that here: https://github.com/projectatomic/rpm-ostree/pull/1090/files

I'm not opposed to storing some more information in the `src/config`. Obviously @jlebon knows this space very well and I'd be interested in his thoughts here.

I think the problem is introduced with the addition of the `--tag reprovision` argument. Otherwise I think the code is acting appropriately.

I guess there are a few options here: 1. switch new style to have both digest and image fields 2. switch old style to just image (with digest embedded) 3....

is `doozer` the only consumer of either of these? If that's the case it looks like `doozer` can already handle either (am I understanding correctly)? If that's true we could...

> OK so actually there is another consideration here. > > With the pipeline changes I'm working on, all the container images we push will be manifest lists to Quay.io....

I'm sorry for not looking at this sooner. I'd like to not drop the existing workflow. I do have some local modifications to make things still work that I'd like...

> Just working on moving the upload outside the vm as discussed with Colin. If the image is in the local builds dir and also in the meta.json then you...