IIUC, currently the way things are set up we don't pull updated rpms unless we explicitly tag them into the f26-atomic tag: https://pagure.io/pungi-fedora/blob/f26/f/fedora-atomic.conf#_41.

We could either

1. tag things we want into the f26-atomic tag
2. modify it so that we pull from all updates, which has risks of breaking things since a lot of people aren't pushing updates and testing media creation with them

I honestly see benefits and negatives of both sides. WDYT?

$ koji tag-pkg f26-atomic ostree-2017.9-2.fc26
ActionNotAllowed: tag requires admin permission

currently, we have to get someone to do that for us. I think I might be able to get access in the future once I go through the process. See comment; I just need to start that process.

In the mean time, can you make sure that's the only rpm we need tagged? i.e. we don't need any other dependencies tagged. Once confirmed we can get someone to tag it for us.

Well, we do the switch to libcurl here, but that should be fine. If it doesn't work we can back it out.

@pbrobinson tagged this for us:

$ koji latest-build f26-atomic ostree
Build                                     Tag                   Built by
----------------------------------------  --------------------  ----------------
ostree-2017.9-2.fc26

ok, so next problem we hit here is that ostree is not in the "Cloud" variant :( - I have added a few PRs to try to fix this.

• https://pagure.io/fedora-comps/pull-request/153
• https://pagure.io/pungi-fedora/pull-request/308
• https://pagure.io/pungi-fedora/pull-request/309

Testing it now

Testing it now

worked - https://koji.stg.fedoraproject.org/compose/branched/Fedora-Atomic-26-20170804.n.4/logs/x86_64/Atomic/ostree_installer-1/lorax.log

all PRs merged. Tomorrow's run should contain the updated ostree.