Laurence Rochfort: > > Hello Laurence, > > > > these versions are ok. There has been no change during Spacewalk 2.9 > > development in these packages. If you look into .spec you can see > > Version: 2.9.0 here but it is just a result of an automatic version > > bump so the first real change in the package would increased version to > > 2.9.1. > > > > Let's check latest tagged versions: > > $ cd spacewalk.git > > $ git checksout SPACEWALK-2.9 > > $ for t in spacewalk-proxy-installer spacewalk-config > > spacewalk-setup-postgresql spacewalk-proxy-selinux perl-Satcon spacewalk-2 > > spacewalk-proxy-docs spacewalk-proxy-html ; do git tag | grep $t | tail -1 > > ; done > > spacewalk-proxy-installer-2.8.6-1 > > spacewalk-config-2.8.5-1 > > spacewalk-setup-postgresql-2.8.4-1 > > spacewalk-proxy-selinux-2.8.3-1 > > perl-Satcon-2.8.2-1 > > spacewalk-2.8.2-1 > > spacewalk-proxy-docs-2.8.2-1 > > spacewalk-proxy-html-2.8.2-1 > > Thanks for the explanation, Michael. > > I do wonder if having the main Spacewalk 2.9 package have a version of > 2.8 is a little confusing for a sys admin who's not so familiar with > Spacewalk? > > If I were to ask yum which version of Spacewalk I have installed and it > says 2.8, or the main package version didn't match all the others, then > it might be confusing and cause me to try to upgrade?
Hello Laurence, Well, that's actually a good point. I've rebuilt spacewalk package both in 2.9 branch and master to reflect the repository version.> > Just a thought. > > -- > Cheers, > Laurence. Regards, -- Michael Mráka System Management Engineering, Red Hat _______________________________________________ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel