On 07/10/2017 01:41 PM, Patrick Uiterwijk wrote:
> On Mon, Jul 10, 2017 at 7:26 PM, Dusty Mabe <dusty(a)dustymabe.com> wrote:
>> On 07/10/2017 01:23 PM, Kevin Fenzi wrote:
>>> On 07/07/2017 03:48 PM, Dusty Mabe wrote:
>>>> For https://pagure.io/atomic-wg/issue/291
we'd like to create a
>>>> from the last fedora 25 commit to the fedora 26 commits we are releasing.
>>>> we don't yet have a unified repo structure we need to pull the last
>>>> commit into the fedora 26 repo. Can someone with appropriate permissions
>>>> following procedure on a machine that has the ostree repos mounted:
>>>> 1. change directory to the equivalent of
>>>> 2. take note of permissions of files within those directories
>>>> 3. ostree --repo=./26/ pull-local ./25/
>>>> ostree --repo=./26/ show
>>>> 4. make sure permissions are still right for files within those
>>>> 5. Send me the output of running those two commands.
>>> Sure, +1 here.
>>> Does this need to be done at a time no updates pushes are going? Or does
>>> it matter?
>> Usually I would say yes just to be careful, but I don't think we have bodhi
>> up to f26 creating ostrees yet do we?
> Given that this does not touch any existing objects and refs (only
> creating new ones), I think it should be fine to do at anytime.
> Do note that this is missing the commands to actually create the
> static diff, but I am going to guess you've kept those out until the
> output can be verified.
The static delta will get created by the push_two_week script. See this PR
All we need is for the commit to exist in the repo and the script should do
the rest. Any problems with this approach?
Automation, great. I'm okay with that.
>> I am okay with this change given its low risk, and will start the
>> procedure with my +1.