Sometime within the last 24 hrs (I think) the F27 branch for Atomic Host got reset.
Previously there were multiple commits on the branch, but as of today there is only one commit from Sept 1.
# ostree remote add --no-gpg-verify custom https://kojipkgs.fedoraproject.org/compose/atomic/27/ # ostree pull --commit-metadata-only --depth=-1 custom:fedora/27/x86_64/atomic-host 2 metadata, 0 content objects fetched; 775 B transferred in 1 seconds # ostree log fedora/27/x86_64/atomic-host commit fb3870488a644e179ba2ac587ee693ce4203e703e3e39c67257f479a1e28bf1c Date: 2017-09-01 16:41:54 +0000 Version: 27.20170901.n.1 (no subject)
Metadata Update from @dustymabe: - Issue tagged with: infra
A new commit appeared today, but any history is gone:
# ostree log fedora/27/x86_64/atomic-host commit 4d915abfddb40362ba0b2f6270f010cf832c054c0356021d24cceb3ce80b9d56 Date: 2017-09-15 13:56:28 +0000 Version: 27.20170915.n.0 (no subject) commit fb3870488a644e179ba2ac587ee693ce4203e703e3e39c67257f479a1e28bf1c Date: 2017-09-01 16:41:54 +0000 Version: 27.20170901.n.1 (no subject)
yes this is a problem with the signing we did yesterday. Apparently the tool also set's the ref when it performs a signature. @puiterwijk is adding an option to the tool to allow us to tell it not to do that in cases like this.
Metadata Update from @dustymabe: - Issue assigned to puiterwijk
This has been resolved, and should sync out in the next 30 minutes.
Metadata Update from @puiterwijk: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.