So when we pointed the thing that makes new ostrees to the "correct" location we started a new ostree repo that knows nothing about the old ostree history. I just did an upgrade and here is what I'm looking at: [vagrant@vanilla-f24atomic ~]$ sudo rpm-ostree status TIMESTAMP (UTC) VERSION ID OSNAME REFSPEC 2016-07-24 20:14:21 24.4 c4b2c5e08d fedora-atomic fedora-atomic:fedora-atomic/24/x86_64/docker-host * 2016-06-15 09:57:04 24.39 2c7d41e8a6 fedora-atomic fedora-atomic:fedora-atomic/24/x86_64/docker-host so what I was on was 24.39 and the upgrade went to 24.4. are we ok with this? I think the solution would be to delete the ostree at the new (correct) location and cp the contents of the old ostree into place and go from there. The alternative is to just leave it and eventually the version # will be greater than 39 again. Dusty _______________________________________________ cloud mailing list cloud@xxxxxxxxxxxxxxxxxxxxxxx https://lists.fedoraproject.org/admin/lists/cloud@xxxxxxxxxxxxxxxxxxxxxxx
