On Wed, Jan 09, 2019 at 11:42:31AM +0100, Fabiano Fidêncio wrote: > The upgrade feature does *not* inidcate whether the upgrade path is > supported or not. It indicates that this realease is considered a newer > version than the listed versions. 'indicate', 'release' > > This reverts commit 335cd8c70e0edadaaa1b5aefa8f138b5839a9639. > > Signed-off-by: Fabiano Fidêncio <fidencio@xxxxxxxxxx> > --- > data/os/centos.org/centos-7.0.xml.in | 1 + > 1 file changed, 1 insertion(+) > > diff --git a/data/os/centos.org/centos-7.0.xml.in b/data/os/centos.org/centos-7.0.xml.in > index c3f45a2..20422f2 100644 > --- a/data/os/centos.org/centos-7.0.xml.in > +++ b/data/os/centos.org/centos-7.0.xml.in > @@ -8,6 +8,7 @@ > <_vendor>CentOS</_vendor> > <family>linux</family> > <distro>centos</distro> > + <upgrades id="http://centos.org/centos/6.5"/> Shouldn't it be latest centos 6 release though? For the revert, Acked-by: Christophe Fergeau <cfergeau@xxxxxxxxxx> as this can be done in another commit Christophe > <clones id="http://redhat.com/rhel/7.6"/> > > <release-date>2014-07-07</release-date> > -- > 2.19.2 > > _______________________________________________ > Libosinfo mailing list > Libosinfo@xxxxxxxxxx > https://www.redhat.com/mailman/listinfo/libosinfo
Attachment:
signature.asc
Description: PGP signature
_______________________________________________ Libosinfo mailing list Libosinfo@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libosinfo
