The previous commit had a successful build, whic means that we now
correctly have both 'org.gnome.Baobab' (old name) and 'org.gnome.baobab'
(new name) in the repos, which is what we need long term, but more
importantly, as a hotfix to avoid breaking flatpak update for people who
had 'org.gnome.Baobab' already installed.
This commit now adds back the metadata to mark org.gnome.baobab as a
replacement for org.gnome.Baobab. For that to work, we need latest
flatpak-module-tools installed in the OSBS buildroot to actually get a
successful build.
This reverts commit f8ee4d8dd0.
There appears to be something in 'eol/org.gnome.Baobab' that the
registry is rejecting. Let's try without dots and see if this works
better.
52917228 buildContainer (noarch): open (buildvm-x86-04.iad2.fedoraproject.org) -> FAILED: Fault: <Fault 2001: 'Image build failed. Error in plugin orchestrate_build: {"x86_64": {"tag_and_push": "Command \'[\'skopeo\', \'copy\', \'--authfile=/var/run/secrets/atomic-reactor/v2-registry-dockercfg/.dockercfg\', \'oci:/tmp/tmpmictw3xf/flatpak-oci-image:app/org.gnome.Baobab/x86_64/stable\', \'docker://candidate-registry.fedoraproject.org/eol/org.gnome.Baobab:f32-flatpak-candidate-83731-20201007070318-x86_64\']\' returned non-zero exit status 1."}}. OSBS build id: baobab-f32-c1d99-5'>
The plan is to have org.gnome.Baobab available from the f32 branch, and
org.gnome.baobab from master. Having both the old and new version
available in the repo is needed in order to correctly handle the
rename from org.gnome.Baobab to org.gnome.baobab.
