Re: Why do we have an older version number for today's atomic compose? compose?

2016-09-07 Thread Kushal Das
On 06/09/16, Micah Abbott wrote: > It looks like the ostree composes had the version numbering reset on July > 20. > > # ostree pull --commit-metadata-only --depth=-1 > fedora-atomic:fedora-atomic/24/x86_64/docker-host > > 68 metadata, 0 content objects fetched; 7 KiB transferred in 32 seconds

Re: Why do we have an older version number for today's atomic compose? compose?

2016-09-06 Thread Dusty Mabe
On 09/06/2016 10:27 AM, Micah Abbott wrote: > > It looks like the ostree composes had the version numbering reset on > July 20. > > # ostree pull --commit-metadata-only --depth=-1 > fedora-atomic:fedora-atomic/24/x86_64/docker-host > > 68 metadata, 0 content objects fetched; 7 KiB transferre

Re: Why do we have an older version number for today's atomic compose? compose?

2016-09-06 Thread Micah Abbott
On 09/05/2016 11:12 AM, Kushal Das wrote: Hi, After an *atomic host upgrade* in an atomic host. Deployments: ● fedora-atomic:fedora-atomic/24/x86_64/docker-host Version: 24.35 (2016-09-05 01:23:02) Commit: 5832e43bcf2054a46169442557d4348d38e280161955c4bcd83b19db6649a5df O

Re: Why do we have an older version number for today's atomic compose? compose?

2016-09-05 Thread Dusty Mabe
On 09/05/2016 02:06 PM, Kushal Das wrote: > On 05/09/16, Kushal Das wrote: >> Hi, >> >> After an *atomic host upgrade* in an atomic host. >> >> Deployments: >> ● fedora-atomic:fedora-atomic/24/x86_64/docker-host >>Version: 24.35 (2016-09-05 01:23:02) >> Commit: >> 5832e43bcf2054a

Re: Why do we have an older version number for today's atomic compose? compose?

2016-09-05 Thread Kushal Das
On 05/09/16, Kushal Das wrote: > Hi, > > After an *atomic host upgrade* in an atomic host. > > Deployments: > ● fedora-atomic:fedora-atomic/24/x86_64/docker-host >Version: 24.35 (2016-09-05 01:23:02) > Commit: > 5832e43bcf2054a46169442557d4348d38e280161955c4bcd83b19db6649a5df >