On older systems, /etc/yum/vars is not created by the yum package. In fact, /etc/yum/vars isn't supported on older systems anyway. This patch will optionally create /etc/yum/vars before setting releasever. --- configserver/examples/katello-register.xml | 2 ++ 1 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/configserver/examples/katello-register.xml b/configserver/examples/katello-register.xml index 7e55687..cc49e5a 100644 --- a/configserver/examples/katello-register.xml +++ b/configserver/examples/katello-register.xml @@ -205,6 +205,8 @@ def audrey_var(name, default=None):
def setup_releasever(): + if not os.path.isdir('/etc/yum/vars'): + os.mkdir('/etc/yum/vars') fp = open("/etc/yum/vars/releasever", "r+") fp.write(audrey_var("RELEASEVER")) fp.close()
On 12/04/12 14:07 -0400, James Laska wrote:
On older systems, /etc/yum/vars is not created by the yum package. In fact, /etc/yum/vars isn't supported on older systems anyway. This patch will optionally create /etc/yum/vars before setting releasever.
Not reviewing patch, just a request. Could I ask that people add to their project .git/config: [format] subjectprefix = PATCH <project-name>
This just makes it easier for someone looking at the list to identify where a given patch applies, so they have an idea if it is something shoudl look at (or just plain which repo to apply it to). We largely do this, but not everyone knows, since the group continues to grow and change. Thanks,
-j
On Thu, 2012-04-12 at 15:12 -0400, Jason Guiditta wrote:
On 12/04/12 14:07 -0400, James Laska wrote:
On older systems, /etc/yum/vars is not created by the yum package. In fact, /etc/yum/vars isn't supported on older systems anyway. This patch will optionally create /etc/yum/vars before setting releasever.
Not reviewing patch, just a request. Could I ask that people add to their project .git/config: [format] subjectprefix = PATCH <project-name>
This just makes it easier for someone looking at the list to identify where a given patch applies, so they have an idea if it is something shoudl look at (or just plain which repo to apply it to). We largely do this, but not everyone knows, since the group continues to grow and change. Thanks,
Thanks for the suggestion Jason. I'll try to do this for future patches to aeolus-devel.
Thanks, James
aeolus-devel@lists.fedorahosted.org