no such metadata / no such ref errors on the command line

[Alexander Larsson]

On Fri, Apr 6, 2018 at 3:59 AM, Michael Gratton <mike at vee.net> wrote:
> On Thu, Apr 5, 2018 at 5:58 PM, Alexander Larsson <alexl at redhat.com> wrote:

> And now the no "such ref error" has gone away running an update, but both
> search and update are now reporting the same missing metadata object
> instead:
>
>> mjg at payens:~$ flatpak search blah
>> Error updating: No such metadata object
>> 3f97e8db7dffa626bd19b4a763b6a371698c58054877215c00bf1b1d4d00db50.commit
>> No matches found
>> mjg at payens:~$ flatpak update
>> Looking for updates...
>> Updating appstream data for remote gnome-apps-nightly
>> Error updating: No such metadata object
>> 3f97e8db7dffa626bd19b4a763b6a371698c58054877215c00bf1b1d4d00db50.commit
>
> So maybe something went wrong uninstalling the 64 bit version a while back?
> Is there is an issue uninstalling an app or arch that has already been
> removed from a repo?

Hmm, i wonder what that commit is from, can you run:

 grep -r 3f97e8db7dffa626bd19b4a763b6a371698c58054877215c00bf1b1d4d00db50
/var/lib/flatpak/repo/refs/

And see if you have a local ref pointing to it?

-- 
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
 Alexander Larsson                                Red Hat, Inc
       alexl at redhat.com         alexander.larsson at gmail.com