Re: Few Fedora 20 ProjectAtomic VM questions

[Colin Walters <walters verbum org>]

On Wed, Jun 11, 2014, at 12:47 PM, Andy Grimm wrote:
>
> I didn't get this message, but got a similarly disappointing one (from
> the 20140609 image):  "error: No such metadata object: ...."  I assume
> that if you fix the problem with your broken remote, you'll see this
> message next.  This is my (possibly incorrect) interpretation:  when
> an atomic image is built, it doesn't contain the whole commit history
> (as that would be quite large).  "ostree log" tries to track back
> through the latest commit's ancestors, but it can only see commits
> that you've pulled in since creating this instance.  Rather than
> simply exiting or saying "I don't have a local copy of any ancestors
> beyond this point" in some nice way, it barfs an error.  Not exactly
> user-friendly, but it does make sense.

That is a perfectly accurate summary =)

The reason I haven't fixed this is that the commit log doesn't actually
have anything *useful*.  What should it contain?  There's a lot of
potential answers to that - package-level diffs?  We have that in the
rpmdb though.

There's the timestamp, which is important.  Also, the commit object
itself though is the source of GPG signatures, and I think that's
something we probably should show and offer to verify.

We also have the possibility to download *only* the commit objects from
a repo, but that would require a bit of work as the ostree pull process
assumes that if it has a commit object it has the entire tree it
references.

Anyways this thread was sufficient motivation to write a patch =)  
Review appreciated!
https://bugzilla.gnome.org/show_bug.cgi?id=731538