https://pagure.io/atomic-wg/issue/336
Each ref only has one commit in it now:
```
Fri Sep 15 11:43:42 UTC 2017
Testing 27 fedora/27/x86_64/atomic-host at
https://kojipkgs.fedoraproject.org/compose/atomic/27/
1 metadata, 0 content objects fetched; 569 B transferred in 1 seconds
checking 2017-09-01 '27.20170901.n.1' fb38704... GOOD!
error: Commit fb3870488a644e179ba2ac587ee693ce4203e703e3e39c67257f479a1e28bf1c has no
parent
Fri Sep 15 11:43:44 UTC 2017
Testing 27 fedora/27/ppc64le/atomic-host at
https://kojipkgs.fedoraproject.org/compose/atomic/27/
1 metadata, 0 content objects fetched; 569 B transferred in 1 seconds
checking 2017-09-03 '27.20170903.n.0' 4436083... GOOD!
error: Commit 44360832d299b2cf6ca33f4199b3e47613aa22de14784c37ec9b2e4478e1429e has no
parent
Fri Sep 15 11:43:46 UTC 2017
Testing 27 fedora/27/aarch64/atomic-host at
https://kojipkgs.fedoraproject.org/compose/atomic/27/
1 metadata, 0 content objects fetched; 569 B transferred in 1 seconds
checking 2017-09-02 '27.20170902.n.0' fc7a9e5... GOOD!
error: Commit fc7a9e5378ba2c8f2b22f746dc8f56f0588eb637f8a3a5439e25cfd5d9f16371 has no
parent
Fri Sep 15 11:43:48 UTC 2017
Testing 27 fedora/27/x86_64/workstation at
https://kojipkgs.fedoraproject.org/compose/ostree/27/
1 metadata, 0 content objects fetched; 569 B transferred in 1 seconds
checking 2017-09-12 '27.20170911.n.1' 80d7094... GOOD!
error: Commit 80d709452bf8a24e722e8af5e81f9046c991200384d1bd44a7415c1fbf1e5b06 has no
parent
```
You can see this at
http://ostree-signed-commit-checker-fooplay.origin.dustymabe.com/
Kevin did sign commits for me yesterday but I don't think that should have caused us
to lose history.
This is not a huge deal since f27 is not released, but I would like to find out why we
lost history
so it doesn't happen again.
Dusty