If we happen to miss a sync for whatever reason there could be gaps in the ostree history. Adding --depth=-1 will make sure that the entire history for the ref is in the target repo. --- roles/bodhi2/backend/files/new-updates-sync | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/roles/bodhi2/backend/files/new-updates-sync b/roles/bodhi2/backend/files/new-updates-sync index 35c9d58..6ccc8cc 100755 --- a/roles/bodhi2/backend/files/new-updates-sync +++ b/roles/bodhi2/backend/files/new-updates-sync @@ -145,7 +145,7 @@ def sync_ostree(dst, ref): else: logger.info('Syncing OSTree to %s, ref %s: %s -> %s', dst, ref, src_commit, dst_commit) - cmd = ['ostree', 'pull-local', '--verbose', '--repo', + cmd = ['ostree', 'pull-local', '--verbose', '--depth=-1', '--repo', dst, ATOMICSOURCE, ref] out = run_command(cmd) cmd = ['ostree', 'summary', '--verbose', '--repo', dst, '--update']
If we happen to miss a sync for whatever reason there could be gaps in the ostree history. Adding --depth=-1 will make sure that the entire history for the ref is in the target repo.
roles/bodhi2/backend/files/new-updates-sync | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/roles/bodhi2/backend/files/new-updates-sync b/roles/bodhi2/backend/files/new-updates-sync index 35c9d58..6ccc8cc 100755 --- a/roles/bodhi2/backend/files/new-updates-sync +++ b/roles/bodhi2/backend/files/new-updates-sync @@ -145,7 +145,7 @@ def sync_ostree(dst, ref): else: logger.info('Syncing OSTree to %s, ref %s: %s -> %s', dst, ref, src_commit, dst_commit)
cmd = ['ostree', 'pull-local', '--verbose','--repo',
cmd = ['ostree', 'pull-local', '--verbose','--depth=-1', '--repo', dst, ATOMICSOURCE, ref] out = run_command(cmd) cmd = ['ostree', 'summary', '--verbose', '--repo', dst, '--update']
+1
Oh I see +1
On 10 November 2017 at 17:28, Patrick マルタインアンドレアス Uiterwijk puiterwijk@redhat.com wrote:
If we happen to miss a sync for whatever reason there could be gaps in the ostree history. Adding --depth=-1 will make sure that the entire history for the ref is in the target repo.
roles/bodhi2/backend/files/new-updates-sync | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/roles/bodhi2/backend/files/new-updates-sync b/roles/bodhi2/backend/files/new-updates-sync index 35c9d58..6ccc8cc 100755 --- a/roles/bodhi2/backend/files/new-updates-sync +++ b/roles/bodhi2/backend/files/new-updates-sync @@ -145,7 +145,7 @@ def sync_ostree(dst, ref): else: logger.info('Syncing OSTree to %s, ref %s: %s -> %s', dst, ref, src_commit, dst_commit)
cmd = ['ostree', 'pull-local', '--verbose','--repo',
cmd = ['ostree', 'pull-local', '--verbose','--depth=-1', '--repo', dst, ATOMICSOURCE, ref] out = run_command(cmd) cmd = ['ostree', 'summary', '--verbose', '--repo', dst, '--update']
+1 _______________________________________________ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-leave@lists.fedoraproject.org
Is something missing from this email?
On 10 November 2017 at 17:26, Dusty Mabe dusty@dustymabe.com wrote:
sync script: copy history of ostree ref _______________________________________________ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-leave@lists.fedoraproject.org
infrastructure@lists.fedoraproject.org
-
Dusty Mabe -
Patrick マルタインアンドレアス Uiterwijk -
Stephen John Smoogen