6 commits - rel-eng/packages spacecmd/spacecmd.spec spacecmd/src
by aparsons
rel-eng/packages/spacecmd | 2 -
spacecmd/spacecmd.spec | 14 +++++++-
spacecmd/src/lib/errata.py | 17 +++++++++-
spacecmd/src/lib/misc.py | 61 ++++++++++++++++++++----------------
spacecmd/src/lib/softwarechannel.py | 15 ++++++++
5 files changed, 79 insertions(+), 30 deletions(-)
New commits:
commit 2f36316501da376e91406e6fa749d0bc43ae78ab
Author: Aron Parsons <aparsons(a)redhat.com>
Date: Thu Mar 3 17:47:20 2011 -0500
Automatic commit of package [spacecmd] release [1.4.1-1].
diff --git a/rel-eng/packages/spacecmd b/rel-eng/packages/spacecmd
index 894cb6d..cf34e5b 100644
--- a/rel-eng/packages/spacecmd
+++ b/rel-eng/packages/spacecmd
@@ -1 +1 @@
-1.3.8-1 spacecmd/
+1.4.1-1 spacecmd/
diff --git a/spacecmd/spacecmd.spec b/spacecmd/spacecmd.spec
index 6c23e18..b1d5bcc 100644
--- a/spacecmd/spacecmd.spec
+++ b/spacecmd/spacecmd.spec
@@ -4,7 +4,7 @@
%endif
Name: spacecmd
-Version: 1.4.0
+Version: 1.4.1
Release: 1%{?dist}
Summary: Command-line interface to Spacewalk and Satellite servers
@@ -61,6 +61,18 @@ touch %{buildroot}/%{python_sitelib}/spacecmd/__init__.py
%doc %{_mandir}/man1/spacecmd.1.gz
%changelog
+* Thu Mar 03 2011 Aron Parsons <aparsons(a)redhat.com> 1.4.1-1
+- spacecmd: log channel access issues in debug mode only (aparsons(a)redhat.com)
+- spacecmd: ignore channel failures introduced by organizations when caching
+ packages (aparsons(a)redhat.com)
+- spacecmd: print a summary list of all errata (name, synopsis, date)
+ (aparsons(a)redhat.com)
+- spacecmd: ignore channel failures introduced by organizations when caching
+ errata (aparsons(a)redhat.com)
+- spacecmd: delete child channels first in softwarechannel_delete
+ (aparsons(a)redhat.com)
+- Bumping package versions for 1.4 (tlestach(a)redhat.com)
+
* Thu Jan 27 2011 Aron Parsons <aparsons(a)redhat.com> 1.3.8-1
- added configchannel_backup function (john(a)vanzantvoort.org)
commit d84f5974bc070a670df6e2bb0014dbab61fbfdfb
Author: Aron Parsons <aparsons(a)redhat.com>
Date: Thu Mar 3 16:37:10 2011 -0500
spacecmd: log channel access issues in debug mode only
diff --git a/spacecmd/src/lib/misc.py b/spacecmd/src/lib/misc.py
index 7fb48d5..6be4d59 100644
--- a/spacecmd/src/lib/misc.py
+++ b/spacecmd/src/lib/misc.py
@@ -459,7 +459,7 @@ def generate_errata_cache(self, force=False):
errata = \
self.client.channel.software.listErrata(self.session, c)
except:
- logging.warning('No access to %s' % c)
+ logging.debug('No access to %s' % c)
continue
for erratum in errata:
@@ -511,7 +511,7 @@ def generate_package_cache(self, force=False):
packages = \
self.client.channel.software.listAllPackages(self.session, c)
except:
- logging.warning('No access to %s' % c)
+ logging.debug('No access to %s' % c)
continue
for p in packages:
commit 736ec00f3d5e8242e11139997b84f01f784ae7d1
Author: Aron Parsons <aparsons(a)redhat.com>
Date: Thu Mar 3 16:32:55 2011 -0500
spacecmd: ignore channel failures introduced by organizations when caching packages
diff --git a/spacecmd/src/lib/misc.py b/spacecmd/src/lib/misc.py
index 5072a4d..7fb48d5 100644
--- a/spacecmd/src/lib/misc.py
+++ b/spacecmd/src/lib/misc.py
@@ -459,6 +459,7 @@ def generate_errata_cache(self, force=False):
errata = \
self.client.channel.software.listErrata(self.session, c)
except:
+ logging.warning('No access to %s' % c)
continue
for erratum in errata:
@@ -506,8 +507,12 @@ def generate_package_cache(self, force=False):
channels = [c.get('label') for c in channels]
for c in channels:
- packages = \
- self.client.channel.software.listAllPackages(self.session, c)
+ try:
+ packages = \
+ self.client.channel.software.listAllPackages(self.session, c)
+ except:
+ logging.warning('No access to %s' % c)
+ continue
for p in packages:
if not p.get('name') in self.all_packages_short:
commit 8cd1189ec1b098b49500c414dc95fdd3920b13a0
Author: Aron Parsons <aparsons(a)redhat.com>
Date: Thu Mar 3 16:23:00 2011 -0500
spacecmd: print a summary list of all errata (name, synopsis, date)
diff --git a/spacecmd/src/lib/errata.py b/spacecmd/src/lib/errata.py
index 76ff30b..7fa77b1 100644
--- a/spacecmd/src/lib/errata.py
+++ b/spacecmd/src/lib/errata.py
@@ -20,7 +20,9 @@
# NOTE: the 'self' variable is an instance of SpacewalkShell
+from operator import itemgetter
import xmlrpclib
+
from spacecmd.utils import *
def help_errata_list(self):
@@ -38,6 +40,18 @@ def do_errata_list(self, args, doreturn=False):
####################
+def help_errata_summary(self):
+ print 'errata_summary: Print a summary of all errata'
+ print 'usage: errata_summary'
+
+def do_errata_summary(self, args):
+ self.generate_errata_cache()
+
+ map(print_errata_summary, sorted(self.all_errata.values(),
+ key = itemgetter('advisory_name')))
+
+####################
+
def help_errata_apply(self):
print 'errata_apply: Apply an erratum to all affected systems'
print 'usage: errata_apply ERRATA|search:XXX ...'
@@ -417,7 +431,8 @@ def do_errata_search(self, args, doreturn=False):
for name in self.all_errata.keys():
if re.search(query, name, re.I) or \
- re.search(query, self.all_errata[name]['synopsis'], re.I):
+ re.search(query, self.all_errata[name]['advisory_synopsis'],
+ re.I):
match = self.all_errata[name]
diff --git a/spacecmd/src/lib/misc.py b/spacecmd/src/lib/misc.py
index dda91eb..5072a4d 100644
--- a/spacecmd/src/lib/misc.py
+++ b/spacecmd/src/lib/misc.py
@@ -464,10 +464,11 @@ def generate_errata_cache(self, force=False):
for erratum in errata:
if erratum.get('advisory_name') not in self.all_errata:
self.all_errata[erratum.get('advisory_name')] = \
- { 'id' : erratum.get('id'),
- 'type' : erratum.get('advisory_type'),
- 'date' : erratum.get('date'),
- 'synopsis' : erratum.get('advisory_synopsis') }
+ { 'id' : erratum.get('id'),
+ 'advisory_name' : erratum.get('advisory_name'),
+ 'advisory_type' : erratum.get('advisory_type'),
+ 'date' : erratum.get('date'),
+ 'advisory_synopsis' : erratum.get('advisory_synopsis') }
self.errata_cache_expire = \
datetime.now() + timedelta(self.ERRATA_CACHE_TTL)
commit 6b9ca5669c628082e563e00a2fad6401ccc620eb
Author: Aron Parsons <aparsons(a)redhat.com>
Date: Thu Mar 3 16:02:25 2011 -0500
spacecmd: ignore channel failures introduced by organizations when caching errata
diff --git a/spacecmd/src/lib/misc.py b/spacecmd/src/lib/misc.py
index 1bf5f5f..dda91eb 100644
--- a/spacecmd/src/lib/misc.py
+++ b/spacecmd/src/lib/misc.py
@@ -256,7 +256,7 @@ def do_login(self, args):
and not self.options.password:
try:
sessionfile = open(session_file, 'r')
-
+
# read the session (format = username:session)
for line in sessionfile:
parts = line.split(':')
@@ -455,11 +455,14 @@ def generate_errata_cache(self, force=False):
channels = [c.get('label') for c in channels]
for c in channels:
- errata = \
- self.client.channel.software.listErrata(self.session, c)
+ try:
+ errata = \
+ self.client.channel.software.listErrata(self.session, c)
+ except:
+ continue
for erratum in errata:
- if erratum.get('advisory_name') not in self.all_errata:
+ if erratum.get('advisory_name') not in self.all_errata:
self.all_errata[erratum.get('advisory_name')] = \
{ 'id' : erratum.get('id'),
'type' : erratum.get('advisory_type'),
@@ -477,8 +480,8 @@ def generate_errata_cache(self, force=False):
def save_errata_cache(self):
- save_cache(self.errata_cache_file,
- self.all_errata,
+ save_cache(self.errata_cache_file,
+ self.all_errata,
self.errata_cache_expire)
@@ -513,8 +516,8 @@ def generate_package_cache(self, force=False):
if not longname in self.all_packages:
self.all_packages[longname] = p.get('id')
-
- # keep a reverse dictionary so we can lookup package names by ID
+
+ # keep a reverse dictionary so we can lookup package names by ID
self.all_packages_by_id = \
dict( (v, k) for k, v in self.all_packages.iteritems() )
@@ -531,15 +534,15 @@ def generate_package_cache(self, force=False):
def save_package_caches(self):
# store the cache to disk to speed things up
save_cache(self.packages_short_cache_file,
- self.all_packages_short,
+ self.all_packages_short,
self.package_cache_expire)
-
- save_cache(self.packages_long_cache_file,
- self.all_packages,
+
+ save_cache(self.packages_long_cache_file,
+ self.all_packages,
self.package_cache_expire)
- save_cache(self.packages_by_id_cache_file,
- self.all_packages_by_id,
+ save_cache(self.packages_by_id_cache_file,
+ self.all_packages_by_id,
self.package_cache_expire)
@@ -602,8 +605,8 @@ def generate_system_cache(self, force=False):
def save_system_cache(self):
- save_cache(self.system_cache_file,
- self.all_systems,
+ save_cache(self.system_cache_file,
+ self.all_systems,
self.system_cache_expire)
@@ -640,15 +643,15 @@ def load_caches(self, server):
(self.all_errata, self.errata_cache_expire) = \
load_cache(self.errata_cache_file)
- # load self.all_packages_short from disk
+ # load self.all_packages_short from disk
(self.all_packages_short, self.package_cache_expire) = \
load_cache(self.packages_short_cache_file)
- # load self.all_packages from disk
+ # load self.all_packages from disk
(self.all_packages, self.package_cache_expire) = \
load_cache(self.packages_long_cache_file)
- # load self.all_packages_by_id from disk
+ # load self.all_packages_by_id from disk
(self.all_packages_by_id, self.package_cache_expire) = \
load_cache(self.packages_by_id_cache_file)
@@ -767,7 +770,7 @@ def expand_systems(self, args):
except ValueError:
# just a system name
systems.append(item)
-
+
matches = filter_results(self.get_system_names(), systems)
return matches + system_ids
commit d1052d7f94f9f1a3055ef5bbaf3ff627cc133048
Author: Aron Parsons <aparsons(a)redhat.com>
Date: Thu Mar 3 14:44:46 2011 -0500
spacecmd: delete child channels first in softwarechannel_delete
diff --git a/spacecmd/src/lib/softwarechannel.py b/spacecmd/src/lib/softwarechannel.py
index b475366..af4994b 100644
--- a/spacecmd/src/lib/softwarechannel.py
+++ b/spacecmd/src/lib/softwarechannel.py
@@ -340,7 +340,20 @@ def do_softwarechannel_delete(self, args):
if not self.user_confirm('Delete these channels [y/N]:'): return
- for channel in to_delete:
+ # delete child channels first to avoid errors
+ parents = []
+ children = []
+
+ all_channels = self.client.channel.listSoftwareChannels(self.session)
+
+ for channel in all_channels:
+ if channel.get('label') in to_delete:
+ if channel.get('parent_label'):
+ children.append(channel.get('label'))
+ else:
+ parents.append(channel.get('label'))
+
+ for channel in children + parents:
self.client.channel.software.delete(self.session, channel)
####################
13 years, 1 month
backend/satellite_tools
by Michael Mraka
backend/satellite_tools/reposync.py | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
New commits:
commit c80b2410a4f16f304cbe599f1872fb4c0963d76f
Author: Michael Mraka <michael.mraka(a)redhat.com>
Date: Thu Mar 3 15:58:57 2011 +0100
679109 - localpath must be defined in except block
fixing
error: rpmts_HdrFromFdno: MD5 digest: BAD
Expected(d89999554a6046d7c9842d6fbe32e5a7) != (1a6542ee1f2e66a0c307ed2eefe83f84)
(50, 'Unable to load package', 'Invalid information uploaded to the server')
Traceback (most recent call last):
File "/usr/bin/spacewalk-repo-sync", line 69, in ?
...
File
"/usr/lib/python2.4/site-packages/spacewalk/satellite_tools/reposync.py", line
191, in import_packages
finally_remove(localpath)
UnboundLocalError: local variable 'localpath' referenced before assignment
diff --git a/backend/satellite_tools/reposync.py b/backend/satellite_tools/reposync.py
index 174f0cf..2fc46a0 100644
--- a/backend/satellite_tools/reposync.py
+++ b/backend/satellite_tools/reposync.py
@@ -168,11 +168,12 @@ class RepoSync:
is_non_local_repo = (url.find("file://") < 0)
# try/except/finally doesn't work in python 2.4 (RHEL5), so here's a hack
def finally_remove(path):
- if is_non_local_repo:
+ if is_non_local_repo and path:
os.remove(path)
for (index, what) in enumerate(to_process):
pack, to_download, to_link = what
+ localpath = None
try:
self.print_msg("%d/%d : %s" % (index+1, num_to_process, pack.getNVREA()))
if to_download:
13 years, 1 month
Changes to 'refs/tags/spacewalk-schema-1.4.7-1'
by Michael Mraka
Tag 'spacewalk-schema-1.4.7-1' created by Michael Mraka <michael.mraka(a)redhat.com> at 2011-03-03 14:13 +0000
Tagging package [spacewalk-schema] version [1.4.7-1] in directory [schema/spacewalk/].
Changes since spacewalk-selinux-1.4.1-1:
Jan Pazdziora (1):
Stopping nightly builds on Fedora 13.
Michael Mraka (3):
468690 - added index to rhnVirtualization.uuid
upgrade script for rhnVirtualization.uuid index
Automatic commit of package [spacewalk-schema] release [1.4.7-1].
---
rel-eng/build-missing-builds-in-koji.sh | 2 +-
rel-eng/packages/spacewalk-schema | 2 +-
rel-eng/tito.props | 2 +-
schema/spacewalk/common/tables/rhnVirtualInstance.sql | 4 ++++
schema/spacewalk/spacewalk-schema.spec | 6 +++++-
schema/spacewalk/upgrade/spacewalk-schema-1.3-to-spacewalk-schema-1.4/008-rhnVirtualization.sql | 3 +++
6 files changed, 15 insertions(+), 4 deletions(-)
---
13 years, 1 month
rel-eng/packages schema/spacewalk
by Michael Mraka
rel-eng/packages/spacewalk-schema | 2 +-
schema/spacewalk/spacewalk-schema.spec | 6 +++++-
2 files changed, 6 insertions(+), 2 deletions(-)
New commits:
commit 2cd4cfbee2e7a083972a256e8ed2927e0dfd46c5
Author: Michael Mraka <michael.mraka(a)redhat.com>
Date: Thu Mar 3 15:13:17 2011 +0100
Automatic commit of package [spacewalk-schema] release [1.4.7-1].
diff --git a/rel-eng/packages/spacewalk-schema b/rel-eng/packages/spacewalk-schema
index bc82667..04b4c5e 100644
--- a/rel-eng/packages/spacewalk-schema
+++ b/rel-eng/packages/spacewalk-schema
@@ -1 +1 @@
-1.4.6-1 schema/spacewalk/
+1.4.7-1 schema/spacewalk/
diff --git a/schema/spacewalk/spacewalk-schema.spec b/schema/spacewalk/spacewalk-schema.spec
index 87fb4ec..64e9572 100644
--- a/schema/spacewalk/spacewalk-schema.spec
+++ b/schema/spacewalk/spacewalk-schema.spec
@@ -2,7 +2,7 @@ Name: spacewalk-schema
Group: Applications/Internet
Summary: Oracle SQL schema for Spacewalk server
-Version: 1.4.6
+Version: 1.4.7
Release: 1%{?dist}
Source0: %{name}-%{version}.tar.gz
@@ -66,6 +66,10 @@ rm -rf $RPM_BUILD_ROOT
%{_mandir}/man1/spacewalk-sql*
%changelog
+* Thu Mar 03 2011 Michael Mraka <michael.mraka(a)redhat.com> 1.4.7-1
+- upgrade script for rhnVirtualization.uuid index
+- 468690 - added index to rhnVirtualization.uuid
+
* Fri Feb 25 2011 Jan Pazdziora 1.4.6-1
- Need to return new at the end of a trigger function.
13 years, 1 month
2 commits - schema/spacewalk
by Michael Mraka
schema/spacewalk/common/tables/rhnVirtualInstance.sql | 4 ++++
schema/spacewalk/upgrade/spacewalk-schema-1.3-to-spacewalk-schema-1.4/008-rhnVirtualization.sql | 3 +++
2 files changed, 7 insertions(+)
New commits:
commit 63a29bbc93b47465851b130a797e879c0e061840
Author: Michael Mraka <michael.mraka(a)redhat.com>
Date: Thu Mar 3 15:07:05 2011 +0100
upgrade script for rhnVirtualization.uuid index
diff --git a/schema/spacewalk/upgrade/spacewalk-schema-1.3-to-spacewalk-schema-1.4/008-rhnVirtualization.sql b/schema/spacewalk/upgrade/spacewalk-schema-1.3-to-spacewalk-schema-1.4/008-rhnVirtualization.sql
new file mode 100644
index 0000000..56d9c7f
--- /dev/null
+++ b/schema/spacewalk/upgrade/spacewalk-schema-1.3-to-spacewalk-schema-1.4/008-rhnVirtualization.sql
@@ -0,0 +1,3 @@
+CREATE INDEX rhn_vi_uuid_idx
+ ON rhnVirtualInstance (uuid)
+ TABLESPACE [[64k_tbs]];
commit 136da793d9460e94f9b79594b53de7f02008f435
Author: Michael Mraka <michael.mraka(a)redhat.com>
Date: Thu Mar 3 15:04:11 2011 +0100
468690 - added index to rhnVirtualization.uuid
diff --git a/schema/spacewalk/common/tables/rhnVirtualInstance.sql b/schema/spacewalk/common/tables/rhnVirtualInstance.sql
index 61e2edc..10ab243 100644
--- a/schema/spacewalk/common/tables/rhnVirtualInstance.sql
+++ b/schema/spacewalk/common/tables/rhnVirtualInstance.sql
@@ -44,5 +44,9 @@ CREATE INDEX rhn_vi_vsid_idx
ON rhnVirtualInstance (virtual_system_id)
TABLESPACE [[64k_tbs]];
+CREATE INDEX rhn_vi_uuid_idx
+ ON rhnVirtualInstance (uuid)
+ TABLESPACE [[64k_tbs]];
+
CREATE SEQUENCE rhn_vi_id_seq;
13 years, 1 month
rel-eng/build-missing-builds-in-koji.sh rel-eng/tito.props
by Jan Pazdziora
rel-eng/build-missing-builds-in-koji.sh | 2 +-
rel-eng/tito.props | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
New commits:
commit 8f3d1c285d6d50c095da514ce3feec226b984c3e
Author: Jan Pazdziora <jpazdziora(a)redhat.com>
Date: Thu Mar 3 12:13:37 2011 +0100
Stopping nightly builds on Fedora 13.
diff --git a/rel-eng/build-missing-builds-in-koji.sh b/rel-eng/build-missing-builds-in-koji.sh
index b8d22e1..e8be278 100755
--- a/rel-eng/build-missing-builds-in-koji.sh
+++ b/rel-eng/build-missing-builds-in-koji.sh
@@ -6,7 +6,7 @@ if [ "$(basename $0)" == "build-missing-builds-in-brew.sh" ] ; then
KOJI_MISSING_BUILD_BREW_ARG="--brew"
TITO_BUILD_ARG="--cvs-release"
else
- TAGS="dist-5E-sw-1.4-candidate dist-6E-sw-1.4-candidate dist-f13-sw-1.4-candidate dist-f14-sw-1.4-candidate"
+ TAGS="dist-5E-sw-1.4-candidate dist-6E-sw-1.4-candidate dist-f14-sw-1.4-candidate"
TITO_BUILD_ARG="--koji-release"
FEDORA_UPLOAD=1
fi
diff --git a/rel-eng/tito.props b/rel-eng/tito.props
index 0c9a1ba..954d450 100644
--- a/rel-eng/tito.props
+++ b/rel-eng/tito.props
@@ -5,7 +5,7 @@ changelog_with_email = 0
changelog_do_not_remove_cherrypick = 0
[koji]
-autobuild_tags = dist-5E-sw-1.4-candidate dist-6E-sw-1.4-candidate dist-f13-sw-1.4-candidate dist-f14-sw-1.4-candidate
+autobuild_tags = dist-5E-sw-1.4-candidate dist-6E-sw-1.4-candidate dist-f14-sw-1.4-candidate
[dist-5E-sw-1.4-candidate]
disttag = .el5
13 years, 1 month
Changes to 'refs/tags/spacewalk-selinux-1.4.1-1'
by Jan Pazdziora
Tag 'spacewalk-selinux-1.4.1-1' created by Jan Pazdziora <jpazdziora(a)redhat.com> at 2011-03-03 09:46 +0000
Tagging package [spacewalk-selinux] version [1.4.1-1] in directory [selinux/spacewalk-selinux/].
Changes since spacewalk-backend-1.4.16-1:
Jan Pazdziora (2):
Apache should not be able to read the rpm database.
Automatic commit of package [spacewalk-selinux] release [1.4.1-1].
Tomas Lestach (2):
fixed typo in kickstart.script.summary and post.jsp.summary
fixing previous typo in all StringResource files
---
java/code/src/com/redhat/rhn/frontend/strings/jsp/StringResource_bn_IN.xml | 6 +++---
java/code/src/com/redhat/rhn/frontend/strings/jsp/StringResource_de.xml | 4 ++--
java/code/src/com/redhat/rhn/frontend/strings/jsp/StringResource_en_US.xml | 4 ++--
java/code/src/com/redhat/rhn/frontend/strings/jsp/StringResource_es.xml | 4 ++--
java/code/src/com/redhat/rhn/frontend/strings/jsp/StringResource_fr.xml | 4 ++--
java/code/src/com/redhat/rhn/frontend/strings/jsp/StringResource_gu.xml | 4 ++--
java/code/src/com/redhat/rhn/frontend/strings/jsp/StringResource_hi.xml | 4 ++--
java/code/src/com/redhat/rhn/frontend/strings/jsp/StringResource_it.xml | 4 ++--
java/code/src/com/redhat/rhn/frontend/strings/jsp/StringResource_ja.xml | 4 ++--
java/code/src/com/redhat/rhn/frontend/strings/jsp/StringResource_ko.xml | 4 ++--
java/code/src/com/redhat/rhn/frontend/strings/jsp/StringResource_pa.xml | 4 ++--
java/code/src/com/redhat/rhn/frontend/strings/jsp/StringResource_pt_BR.xml | 4 ++--
java/code/src/com/redhat/rhn/frontend/strings/jsp/StringResource_ru.xml | 4 ++--
java/code/src/com/redhat/rhn/frontend/strings/jsp/StringResource_ta.xml | 4 ++--
java/code/src/com/redhat/rhn/frontend/strings/jsp/StringResource_zh_CN.xml | 4 ++--
java/code/src/com/redhat/rhn/frontend/strings/jsp/StringResource_zh_TW.xml | 4 ++--
rel-eng/packages/spacewalk-selinux | 2 +-
selinux/spacewalk-selinux/spacewalk-selinux.spec | 5 ++++-
selinux/spacewalk-selinux/spacewalk.te | 5 +++++
19 files changed, 43 insertions(+), 35 deletions(-)
---
13 years, 1 month
rel-eng/packages selinux/spacewalk-selinux
by Jan Pazdziora
rel-eng/packages/spacewalk-selinux | 2 +-
selinux/spacewalk-selinux/spacewalk-selinux.spec | 5 ++++-
2 files changed, 5 insertions(+), 2 deletions(-)
New commits:
commit 40f5f9313ec6043a8a1e8753cd92cc76f8c0900a
Author: Jan Pazdziora <jpazdziora(a)redhat.com>
Date: Thu Mar 3 10:46:37 2011 +0100
Automatic commit of package [spacewalk-selinux] release [1.4.1-1].
diff --git a/rel-eng/packages/spacewalk-selinux b/rel-eng/packages/spacewalk-selinux
index b125c71..7cf3eb6 100644
--- a/rel-eng/packages/spacewalk-selinux
+++ b/rel-eng/packages/spacewalk-selinux
@@ -1 +1 @@
-1.3.2-1 selinux/spacewalk-selinux/
+1.4.1-1 selinux/spacewalk-selinux/
diff --git a/selinux/spacewalk-selinux/spacewalk-selinux.spec b/selinux/spacewalk-selinux/spacewalk-selinux.spec
index 3db7578..4cf8af4 100644
--- a/selinux/spacewalk-selinux/spacewalk-selinux.spec
+++ b/selinux/spacewalk-selinux/spacewalk-selinux.spec
@@ -7,7 +7,7 @@
%define modulename spacewalk
Name: spacewalk-selinux
-Version: 1.4.0
+Version: 1.4.1
Release: 1%{?dist}
Summary: SELinux policy module supporting Spacewalk Server
@@ -113,6 +113,9 @@ fi
%attr(0755,root,root) %{_sbindir}/%{name}-enable
%changelog
+* Thu Mar 03 2011 Jan Pazdziora 1.4.1-1
+- Apache should not be able to read the rpm database.
+
* Mon Jan 24 2011 Jan Pazdziora 1.3.2-1
- Adding explicit append allow for sqlplus.
13 years, 1 month
selinux/spacewalk-selinux
by Jan Pazdziora
selinux/spacewalk-selinux/spacewalk.te | 5 +++++
1 file changed, 5 insertions(+)
New commits:
commit 6ff276c80bc1ebf8f3def613a300885e9f88b9ba
Author: Jan Pazdziora <jpazdziora(a)redhat.com>
Date: Thu Mar 3 10:05:31 2011 +0100
Apache should not be able to read the rpm database.
When processing rhnpush requests on the server side, we read rpm
file headers by creating (readonly) rpm transaction. On RHEL 6 it
tries to read /var/lib/rpm/Packages. But it does not need it to
just parse the file header, and we do not want to allow httpd_t
to have access to (for example) list of installed packages and
their versions.
Addressing
avc: denied { search } for pid=10689 comm="httpd" name="rpm" dev=dm-0 ino=1179651 scontext=unconfined_u:system_r:httpd_t:s0 tcontext=system_u:object_r:rpm_var_lib_t:s0 tclass=dir
avc: denied { getattr } for pid=10689 comm="httpd" path="/var/lib/rpm" dev=dm-0 ino=1179651 scontext=unconfined_u:system_r:httpd_t:s0 tcontext=system_u:object_r:rpm_var_lib_t:s0 tclass=dir
avc: denied { open } for pid=10689 comm="httpd" name="Packages" dev=dm-0 ino=1179656 scontext=unconfined_u:system_r:httpd_t:s0 tcontext=system_u:object_r:rpm_var_lib_t:s0 tclass=file
diff --git a/selinux/spacewalk-selinux/spacewalk.te b/selinux/spacewalk-selinux/spacewalk.te
index 8f56c6c..f62b454 100644
--- a/selinux/spacewalk-selinux/spacewalk.te
+++ b/selinux/spacewalk-selinux/spacewalk.te
@@ -17,6 +17,7 @@ require {
type initrc_t;
type system_mail_t;
type nfs_t;
+ type rpm_var_lib_t;
}
type spacewalk_install_log_t;
@@ -79,3 +80,7 @@ optional_policy(`
filetrans_pattern(oracle_sqlplus_t, spacewalk_db_install_log_t, spacewalk_sqlplus_spool_log_t, file)
allow oracle_sqlplus_t spacewalk_db_install_log_t:file append;
')
+
+# rpm_dontaudit_search_db(httpd_t) is not available on RHELs
+dontaudit httpd_t rpm_var_lib_t:dir list_dir_perms;
+dontaudit httpd_t rpm_var_lib_t:file read_file_perms;
13 years, 1 month
java/code
by Tomas Lestach
java/code/src/com/redhat/rhn/frontend/strings/jsp/StringResource_bn_IN.xml | 6 +++---
java/code/src/com/redhat/rhn/frontend/strings/jsp/StringResource_de.xml | 4 ++--
java/code/src/com/redhat/rhn/frontend/strings/jsp/StringResource_es.xml | 4 ++--
java/code/src/com/redhat/rhn/frontend/strings/jsp/StringResource_fr.xml | 4 ++--
java/code/src/com/redhat/rhn/frontend/strings/jsp/StringResource_gu.xml | 4 ++--
java/code/src/com/redhat/rhn/frontend/strings/jsp/StringResource_hi.xml | 4 ++--
java/code/src/com/redhat/rhn/frontend/strings/jsp/StringResource_it.xml | 4 ++--
java/code/src/com/redhat/rhn/frontend/strings/jsp/StringResource_ja.xml | 4 ++--
java/code/src/com/redhat/rhn/frontend/strings/jsp/StringResource_ko.xml | 4 ++--
java/code/src/com/redhat/rhn/frontend/strings/jsp/StringResource_pa.xml | 4 ++--
java/code/src/com/redhat/rhn/frontend/strings/jsp/StringResource_pt_BR.xml | 4 ++--
java/code/src/com/redhat/rhn/frontend/strings/jsp/StringResource_ru.xml | 4 ++--
java/code/src/com/redhat/rhn/frontend/strings/jsp/StringResource_ta.xml | 4 ++--
java/code/src/com/redhat/rhn/frontend/strings/jsp/StringResource_zh_CN.xml | 4 ++--
java/code/src/com/redhat/rhn/frontend/strings/jsp/StringResource_zh_TW.xml | 4 ++--
15 files changed, 31 insertions(+), 31 deletions(-)
New commits:
commit f2ddbaa3fee9a5dc4005bfaac9c9026ef939d72f
Author: Tomas Lestach <tlestach(a)redhat.com>
Date: Thu Mar 3 10:39:28 2011 +0100
fixing previous typo in all StringResource files
diff --git a/java/code/src/com/redhat/rhn/frontend/strings/jsp/StringResource_bn_IN.xml b/java/code/src/com/redhat/rhn/frontend/strings/jsp/StringResource_bn_IN.xml
index daa8087..c4f06eb 100644
--- a/java/code/src/com/redhat/rhn/frontend/strings/jsp/StringResource_bn_IN.xml
+++ b/java/code/src/com/redhat/rhn/frontend/strings/jsp/StringResource_bn_IN.xml
@@ -11328,7 +11328,7 @@ Please note that some manual configuration of these scripts may still be require
You can access the network in this section, but you must use IP addresses (name service has not been configured at this point). For more details on
kickstart pre scripts, please refer to the <strong>Red Hat Enterprise Linux System Administration Guide.</strong>
<br/><br/>
-You can also edit the post script for this kickstart below. First, commands related to @@PRODUCT_NAME@@ will automatically be performed (for example, esystem registration to @@PRODUCT_NAME@@).
+You can also edit the post script for this kickstart below. First, commands related to @@PRODUCT_NAME@@ will automatically be performed (for example, system registration to @@PRODUCT_NAME@@).
Next, the non-chroot post script will be executed, and finally the post script will be executed. For more details on kickstart post scripts, please refer to
the <strong>Red Hat Enterprise Linux System Administration Guide.</strong></source>
<context-group name="ctx">
@@ -11338,7 +11338,7 @@ the <strong>Red Hat Enterprise Linux System Administration Guide.</stro
এই সময়ে নেটওয়ার্ক ব্যবহার করার জন্য IP ঠিকানা ব্যবহার করা আবশ্যক (name পরিসেবা এই সময়ে কনফিগার করা হয় না)। Kickstart প্রি-স্ক্রিপ্ট সম্পর্কে জানতে
<strong>Red Hat Enterprise Linux System Administration Guide.</strong> পড়ুন।
<br/><br/>
-চিহ্নিত kickstart-র পোস্ট-স্ক্রিপ্ট অংশ আপনি নীচে পরিবর্তন করতে পারবেন। @@PRODUCT_NAME@@ সংক্রান্ত কমান্ডগুলি প্রথমে নির্বাহিত হবে (উদাহরণস্বরূপ esystem registration to @@PRODUCT_NAME@@)।
+চিহ্নিত kickstart-র পোস্ট-স্ক্রিপ্ট অংশ আপনি নীচে পরিবর্তন করতে পারবেন। @@PRODUCT_NAME@@ সংক্রান্ত কমান্ডগুলি প্রথমে নির্বাহিত হবে (উদাহরণস্বরূপ system registration to @@PRODUCT_NAME@@)।
এর পরে, নন-chroot পোস্ট-স্ক্রিপ্ট অংশ চালিত হবে এবং সর্বশেষ পোস্ট-স্ক্রিপ্ট অংশ নির্বাহিত হবে। Kickstart-র পোস্ট-স্ক্রিপ্ট অংশ সম্বন্ধে অধিক জানতে অনুগ্রহ করে
<strong>Red Hat Enterprise Linux System Administration Guide</strong> পড়ুন।</target></trans-unit>
@@ -11407,7 +11407,7 @@ the <strong>Red Hat Enterprise Linux System Administration Guide.</stro
<trans-unit id="post.jsp.summary">
- <source>You can edit the post script for this kickstart below. First, commands related to @@PRODUCT_NAME@@ will automatically be performed (for example, esystem registration to @@PRODUCT_NAME@@). Next, the non-chroot post script will be executed, and finally the post script will be executed. For more details on kickstart post scripts, please refer to the <strong>Red Hat Enterprise Linux System Administration Guide.</strong></source>
+ <source>You can edit the post script for this kickstart below. First, commands related to @@PRODUCT_NAME@@ will automatically be performed (for example, system registration to @@PRODUCT_NAME@@). Next, the non-chroot post script will be executed, and finally the post script will be executed. For more details on kickstart post scripts, please refer to the <strong>Red Hat Enterprise Linux System Administration Guide.</strong></source>
<context-group name="ctx">
<context context-type="sourcefile">/rhn/kickstart/KickstartPostEdit.do</context>
</context-group>
diff --git a/java/code/src/com/redhat/rhn/frontend/strings/jsp/StringResource_de.xml b/java/code/src/com/redhat/rhn/frontend/strings/jsp/StringResource_de.xml
index b95933c..d6a5209 100644
--- a/java/code/src/com/redhat/rhn/frontend/strings/jsp/StringResource_de.xml
+++ b/java/code/src/com/redhat/rhn/frontend/strings/jsp/StringResource_de.xml
@@ -11344,7 +11344,7 @@ Bitte beachten Sie, dass m&ouml;glicherweise noch einige manuelle Konfigurat
You can access the network in this section, but you must use IP addresses (name service has not been configured at this point). For more details on
kickstart pre scripts, please refer to the <strong>Red Hat Enterprise Linux System Administration Guide.</strong>
<br/><br/>
-You can also edit the post script for this kickstart below. First, commands related to @@PRODUCT_NAME@@ will automatically be performed (for example, esystem registration to @@PRODUCT_NAME@@).
+You can also edit the post script for this kickstart below. First, commands related to @@PRODUCT_NAME@@ will automatically be performed (for example, system registration to @@PRODUCT_NAME@@).
Next, the non-chroot post script will be executed, and finally the post script will be executed. For more details on kickstart post scripts, please refer to
the <strong>Red Hat Enterprise Linux System Administration Guide.</strong></source>
<context-group name="ctx">
@@ -11423,7 +11423,7 @@ Anschlie&szlig;end wird das nicht-chroot Post-Skript ausgef&uuml;hrt, un
<trans-unit id="post.jsp.summary">
- <source>You can edit the post script for this kickstart below. First, commands related to @@PRODUCT_NAME@@ will automatically be performed (for example, esystem registration to @@PRODUCT_NAME@@). Next, the non-chroot post script will be executed, and finally the post script will be executed. For more details on kickstart post scripts, please refer to the <strong>Red Hat Enterprise Linux System Administration Guide.</strong></source>
+ <source>You can edit the post script for this kickstart below. First, commands related to @@PRODUCT_NAME@@ will automatically be performed (for example, system registration to @@PRODUCT_NAME@@). Next, the non-chroot post script will be executed, and finally the post script will be executed. For more details on kickstart post scripts, please refer to the <strong>Red Hat Enterprise Linux System Administration Guide.</strong></source>
<context-group name="ctx">
<context context-type="sourcefile">/rhn/kickstart/KickstartPostEdit.do</context>
</context-group>
diff --git a/java/code/src/com/redhat/rhn/frontend/strings/jsp/StringResource_es.xml b/java/code/src/com/redhat/rhn/frontend/strings/jsp/StringResource_es.xml
index 2e07a1d..820b33c 100644
--- a/java/code/src/com/redhat/rhn/frontend/strings/jsp/StringResource_es.xml
+++ b/java/code/src/com/redhat/rhn/frontend/strings/jsp/StringResource_es.xml
@@ -11340,7 +11340,7 @@ Por favor tenga en cuenta que podría ser necesario configurar manualmente estos
You can access the network in this section, but you must use IP addresses (name service has not been configured at this point). For more details on
kickstart pre scripts, please refer to the <strong>Red Hat Enterprise Linux System Administration Guide.</strong>
<br/><br/>
-You can also edit the post script for this kickstart below. First, commands related to @@PRODUCT_NAME@@ will automatically be performed (for example, esystem registration to @@PRODUCT_NAME@@).
+You can also edit the post script for this kickstart below. First, commands related to @@PRODUCT_NAME@@ will automatically be performed (for example, system registration to @@PRODUCT_NAME@@).
Next, the non-chroot post script will be executed, and finally the post script will be executed. For more details on kickstart post scripts, please refer to
the <strong>Red Hat Enterprise Linux System Administration Guide.</strong></source>
<context-group name="ctx">
@@ -11418,7 +11418,7 @@ el <strong>Manual de administración del sistema Red Hat Enterprise Linux.
<trans-unit id="post.jsp.summary">
- <source>You can edit the post script for this kickstart below. First, commands related to @@PRODUCT_NAME@@ will automatically be performed (for example, esystem registration to @@PRODUCT_NAME@@). Next, the non-chroot post script will be executed, and finally the post script will be executed. For more details on kickstart post scripts, please refer to the <strong>Red Hat Enterprise Linux System Administration Guide.</strong></source>
+ <source>You can edit the post script for this kickstart below. First, commands related to @@PRODUCT_NAME@@ will automatically be performed (for example, system registration to @@PRODUCT_NAME@@). Next, the non-chroot post script will be executed, and finally the post script will be executed. For more details on kickstart post scripts, please refer to the <strong>Red Hat Enterprise Linux System Administration Guide.</strong></source>
<context-group name="ctx">
<context context-type="sourcefile">/rhn/kickstart/KickstartPostEdit.do</context>
</context-group>
diff --git a/java/code/src/com/redhat/rhn/frontend/strings/jsp/StringResource_fr.xml b/java/code/src/com/redhat/rhn/frontend/strings/jsp/StringResource_fr.xml
index c65155f..f93dde0 100644
--- a/java/code/src/com/redhat/rhn/frontend/strings/jsp/StringResource_fr.xml
+++ b/java/code/src/com/redhat/rhn/frontend/strings/jsp/StringResource_fr.xml
@@ -11342,7 +11342,7 @@ Veuillez noter qu'une configuration manuelle de ces scripts peut toujours être
You can access the network in this section, but you must use IP addresses (name service has not been configured at this point). For more details on
kickstart pre scripts, please refer to the <strong>Red Hat Enterprise Linux System Administration Guide.</strong>
<br/><br/>
-You can also edit the post script for this kickstart below. First, commands related to @@PRODUCT_NAME@@ will automatically be performed (for example, esystem registration to @@PRODUCT_NAME@@).
+You can also edit the post script for this kickstart below. First, commands related to @@PRODUCT_NAME@@ will automatically be performed (for example, system registration to @@PRODUCT_NAME@@).
Next, the non-chroot post script will be executed, and finally the post script will be executed. For more details on kickstart post scripts, please refer to
the <strong>Red Hat Enterprise Linux System Administration Guide.</strong></source>
<context-group name="ctx">
@@ -11421,7 +11421,7 @@ Le script post non-chroot sera ensuite exécuté et le script post sera enfin ex
<trans-unit id="post.jsp.summary">
- <source>You can edit the post script for this kickstart below. First, commands related to @@PRODUCT_NAME@@ will automatically be performed (for example, esystem registration to @@PRODUCT_NAME@@). Next, the non-chroot post script will be executed, and finally the post script will be executed. For more details on kickstart post scripts, please refer to the <strong>Red Hat Enterprise Linux System Administration Guide.</strong></source>
+ <source>You can edit the post script for this kickstart below. First, commands related to @@PRODUCT_NAME@@ will automatically be performed (for example, system registration to @@PRODUCT_NAME@@). Next, the non-chroot post script will be executed, and finally the post script will be executed. For more details on kickstart post scripts, please refer to the <strong>Red Hat Enterprise Linux System Administration Guide.</strong></source>
<context-group name="ctx">
<context context-type="sourcefile">/rhn/kickstart/KickstartPostEdit.do</context>
</context-group>
diff --git a/java/code/src/com/redhat/rhn/frontend/strings/jsp/StringResource_gu.xml b/java/code/src/com/redhat/rhn/frontend/strings/jsp/StringResource_gu.xml
index e4f6727..59c83f9 100644
--- a/java/code/src/com/redhat/rhn/frontend/strings/jsp/StringResource_gu.xml
+++ b/java/code/src/com/redhat/rhn/frontend/strings/jsp/StringResource_gu.xml
@@ -11329,7 +11329,7 @@ Please note that some manual configuration of these scripts may still be require
You can access the network in this section, but you must use IP addresses (name service has not been configured at this point). For more details on
kickstart pre scripts, please refer to the <strong>Red Hat Enterprise Linux System Administration Guide.</strong>
<br/><br/>
-You can also edit the post script for this kickstart below. First, commands related to @@PRODUCT_NAME@@ will automatically be performed (for example, esystem registration to @@PRODUCT_NAME@@).
+You can also edit the post script for this kickstart below. First, commands related to @@PRODUCT_NAME@@ will automatically be performed (for example, system registration to @@PRODUCT_NAME@@).
Next, the non-chroot post script will be executed, and finally the post script will be executed. For more details on kickstart post scripts, please refer to
the <strong>Red Hat Enterprise Linux System Administration Guide.</strong></source>
<context-group name="ctx">
@@ -11408,7 +11408,7 @@ the <strong>Red Hat Enterprise Linux System Administration Guide.</stro
<trans-unit id="post.jsp.summary">
- <source>You can edit the post script for this kickstart below. First, commands related to @@PRODUCT_NAME@@ will automatically be performed (for example, esystem registration to @@PRODUCT_NAME@@). Next, the non-chroot post script will be executed, and finally the post script will be executed. For more details on kickstart post scripts, please refer to the <strong>Red Hat Enterprise Linux System Administration Guide.</strong></source>
+ <source>You can edit the post script for this kickstart below. First, commands related to @@PRODUCT_NAME@@ will automatically be performed (for example, system registration to @@PRODUCT_NAME@@). Next, the non-chroot post script will be executed, and finally the post script will be executed. For more details on kickstart post scripts, please refer to the <strong>Red Hat Enterprise Linux System Administration Guide.</strong></source>
<context-group name="ctx">
<context context-type="sourcefile">/rhn/kickstart/KickstartPostEdit.do</context>
</context-group>
diff --git a/java/code/src/com/redhat/rhn/frontend/strings/jsp/StringResource_hi.xml b/java/code/src/com/redhat/rhn/frontend/strings/jsp/StringResource_hi.xml
index c394041..dc70ab7 100644
--- a/java/code/src/com/redhat/rhn/frontend/strings/jsp/StringResource_hi.xml
+++ b/java/code/src/com/redhat/rhn/frontend/strings/jsp/StringResource_hi.xml
@@ -11329,7 +11329,7 @@ Please note that some manual configuration of these scripts may still be require
You can access the network in this section, but you must use IP addresses (name service has not been configured at this point). For more details on
kickstart pre scripts, please refer to the <strong>Red Hat Enterprise Linux System Administration Guide.</strong>
<br/><br/>
-You can also edit the post script for this kickstart below. First, commands related to @@PRODUCT_NAME@@ will automatically be performed (for example, esystem registration to @@PRODUCT_NAME@@).
+You can also edit the post script for this kickstart below. First, commands related to @@PRODUCT_NAME@@ will automatically be performed (for example, system registration to @@PRODUCT_NAME@@).
Next, the non-chroot post script will be executed, and finally the post script will be executed. For more details on kickstart post scripts, please refer to
the <strong>Red Hat Enterprise Linux System Administration Guide.</strong></source>
<context-group name="ctx">
@@ -11408,7 +11408,7 @@ the <strong>Red Hat Enterprise Linux System Administration Guide.</stro
<trans-unit id="post.jsp.summary">
- <source>You can edit the post script for this kickstart below. First, commands related to @@PRODUCT_NAME@@ will automatically be performed (for example, esystem registration to @@PRODUCT_NAME@@). Next, the non-chroot post script will be executed, and finally the post script will be executed. For more details on kickstart post scripts, please refer to the <strong>Red Hat Enterprise Linux System Administration Guide.</strong></source>
+ <source>You can edit the post script for this kickstart below. First, commands related to @@PRODUCT_NAME@@ will automatically be performed (for example, system registration to @@PRODUCT_NAME@@). Next, the non-chroot post script will be executed, and finally the post script will be executed. For more details on kickstart post scripts, please refer to the <strong>Red Hat Enterprise Linux System Administration Guide.</strong></source>
<context-group name="ctx">
<context context-type="sourcefile">/rhn/kickstart/KickstartPostEdit.do</context>
</context-group>
diff --git a/java/code/src/com/redhat/rhn/frontend/strings/jsp/StringResource_it.xml b/java/code/src/com/redhat/rhn/frontend/strings/jsp/StringResource_it.xml
index 87d456d..8880b27 100644
--- a/java/code/src/com/redhat/rhn/frontend/strings/jsp/StringResource_it.xml
+++ b/java/code/src/com/redhat/rhn/frontend/strings/jsp/StringResource_it.xml
@@ -11326,7 +11326,7 @@ Please note that some manual configuration of these scripts may still be require
You can access the network in this section, but you must use IP addresses (name service has not been configured at this point). For more details on
kickstart pre scripts, please refer to the <strong>Red Hat Enterprise Linux System Administration Guide.</strong>
<br/><br/>
-You can also edit the post script for this kickstart below. First, commands related to @@PRODUCT_NAME@@ will automatically be performed (for example, esystem registration to @@PRODUCT_NAME@@).
+You can also edit the post script for this kickstart below. First, commands related to @@PRODUCT_NAME@@ will automatically be performed (for example, system registration to @@PRODUCT_NAME@@).
Next, the non-chroot post script will be executed, and finally the post script will be executed. For more details on kickstart post scripts, please refer to
the <strong>Red Hat Enterprise Linux System Administration Guide.</strong></source>
<context-group name="ctx">
@@ -11405,7 +11405,7 @@ la <strong>Red Hat Enterprise Linux System Administration Guide.</stron
<trans-unit id="post.jsp.summary">
- <source>You can edit the post script for this kickstart below. First, commands related to @@PRODUCT_NAME@@ will automatically be performed (for example, esystem registration to @@PRODUCT_NAME@@). Next, the non-chroot post script will be executed, and finally the post script will be executed. For more details on kickstart post scripts, please refer to the <strong>Red Hat Enterprise Linux System Administration Guide.</strong></source>
+ <source>You can edit the post script for this kickstart below. First, commands related to @@PRODUCT_NAME@@ will automatically be performed (for example, system registration to @@PRODUCT_NAME@@). Next, the non-chroot post script will be executed, and finally the post script will be executed. For more details on kickstart post scripts, please refer to the <strong>Red Hat Enterprise Linux System Administration Guide.</strong></source>
<context-group name="ctx">
<context context-type="sourcefile">/rhn/kickstart/KickstartPostEdit.do</context>
</context-group>
diff --git a/java/code/src/com/redhat/rhn/frontend/strings/jsp/StringResource_ja.xml b/java/code/src/com/redhat/rhn/frontend/strings/jsp/StringResource_ja.xml
index 807bad0..f16315f 100644
--- a/java/code/src/com/redhat/rhn/frontend/strings/jsp/StringResource_ja.xml
+++ b/java/code/src/com/redhat/rhn/frontend/strings/jsp/StringResource_ja.xml
@@ -11327,7 +11327,7 @@ Please note that some manual configuration of these scripts may still be require
You can access the network in this section, but you must use IP addresses (name service has not been configured at this point). For more details on
kickstart pre scripts, please refer to the <strong>Red Hat Enterprise Linux System Administration Guide.</strong>
<br/><br/>
-You can also edit the post script for this kickstart below. First, commands related to @@PRODUCT_NAME@@ will automatically be performed (for example, esystem registration to @@PRODUCT_NAME@@).
+You can also edit the post script for this kickstart below. First, commands related to @@PRODUCT_NAME@@ will automatically be performed (for example, system registration to @@PRODUCT_NAME@@).
Next, the non-chroot post script will be executed, and finally the post script will be executed. For more details on kickstart post scripts, please refer to
the <strong>Red Hat Enterprise Linux System Administration Guide.</strong></source>
<context-group name="ctx">
@@ -11406,7 +11406,7 @@ the <strong>Red Hat Enterprise Linux System Administration Guide.</stro
<trans-unit id="post.jsp.summary">
- <source>You can edit the post script for this kickstart below. First, commands related to @@PRODUCT_NAME@@ will automatically be performed (for example, esystem registration to @@PRODUCT_NAME@@). Next, the non-chroot post script will be executed, and finally the post script will be executed. For more details on kickstart post scripts, please refer to the <strong>Red Hat Enterprise Linux System Administration Guide.</strong></source>
+ <source>You can edit the post script for this kickstart below. First, commands related to @@PRODUCT_NAME@@ will automatically be performed (for example, system registration to @@PRODUCT_NAME@@). Next, the non-chroot post script will be executed, and finally the post script will be executed. For more details on kickstart post scripts, please refer to the <strong>Red Hat Enterprise Linux System Administration Guide.</strong></source>
<context-group name="ctx">
<context context-type="sourcefile">/rhn/kickstart/KickstartPostEdit.do</context>
</context-group>
diff --git a/java/code/src/com/redhat/rhn/frontend/strings/jsp/StringResource_ko.xml b/java/code/src/com/redhat/rhn/frontend/strings/jsp/StringResource_ko.xml
index c6fed7c..c15ca8b 100644
--- a/java/code/src/com/redhat/rhn/frontend/strings/jsp/StringResource_ko.xml
+++ b/java/code/src/com/redhat/rhn/frontend/strings/jsp/StringResource_ko.xml
@@ -11326,7 +11326,7 @@ Please note that some manual configuration of these scripts may still be require
You can access the network in this section, but you must use IP addresses (name service has not been configured at this point). For more details on
kickstart pre scripts, please refer to the <strong>Red Hat Enterprise Linux System Administration Guide.</strong>
<br/><br/>
-You can also edit the post script for this kickstart below. First, commands related to @@PRODUCT_NAME@@ will automatically be performed (for example, esystem registration to @@PRODUCT_NAME@@).
+You can also edit the post script for this kickstart below. First, commands related to @@PRODUCT_NAME@@ will automatically be performed (for example, system registration to @@PRODUCT_NAME@@).
Next, the non-chroot post script will be executed, and finally the post script will be executed. For more details on kickstart post scripts, please refer to
the <strong>Red Hat Enterprise Linux System Administration Guide.</strong></source>
<context-group name="ctx">
@@ -11403,7 +11403,7 @@ the <strong>Red Hat Enterprise Linux System Administration Guide.</stro
<trans-unit id="post.jsp.summary">
- <source>You can edit the post script for this kickstart below. First, commands related to @@PRODUCT_NAME@@ will automatically be performed (for example, esystem registration to @@PRODUCT_NAME@@). Next, the non-chroot post script will be executed, and finally the post script will be executed. For more details on kickstart post scripts, please refer to the <strong>Red Hat Enterprise Linux System Administration Guide.</strong></source>
+ <source>You can edit the post script for this kickstart below. First, commands related to @@PRODUCT_NAME@@ will automatically be performed (for example, system registration to @@PRODUCT_NAME@@). Next, the non-chroot post script will be executed, and finally the post script will be executed. For more details on kickstart post scripts, please refer to the <strong>Red Hat Enterprise Linux System Administration Guide.</strong></source>
<context-group name="ctx">
<context context-type="sourcefile">/rhn/kickstart/KickstartPostEdit.do</context>
</context-group>
diff --git a/java/code/src/com/redhat/rhn/frontend/strings/jsp/StringResource_pa.xml b/java/code/src/com/redhat/rhn/frontend/strings/jsp/StringResource_pa.xml
index ff77949..9890b30 100644
--- a/java/code/src/com/redhat/rhn/frontend/strings/jsp/StringResource_pa.xml
+++ b/java/code/src/com/redhat/rhn/frontend/strings/jsp/StringResource_pa.xml
@@ -11328,7 +11328,7 @@ Please note that some manual configuration of these scripts may still be require
You can access the network in this section, but you must use IP addresses (name service has not been configured at this point). For more details on
kickstart pre scripts, please refer to the <strong>Red Hat Enterprise Linux System Administration Guide.</strong>
<br/><br/>
-You can also edit the post script for this kickstart below. First, commands related to @@PRODUCT_NAME@@ will automatically be performed (for example, esystem registration to @@PRODUCT_NAME@@).
+You can also edit the post script for this kickstart below. First, commands related to @@PRODUCT_NAME@@ will automatically be performed (for example, system registration to @@PRODUCT_NAME@@).
Next, the non-chroot post script will be executed, and finally the post script will be executed. For more details on kickstart post scripts, please refer to
the <strong>Red Hat Enterprise Linux System Administration Guide.</strong></source>
<context-group name="ctx">
@@ -11407,7 +11407,7 @@ the <strong>Red Hat Enterprise Linux System Administration Guide.</stro
<trans-unit id="post.jsp.summary">
- <source>You can edit the post script for this kickstart below. First, commands related to @@PRODUCT_NAME@@ will automatically be performed (for example, esystem registration to @@PRODUCT_NAME@@). Next, the non-chroot post script will be executed, and finally the post script will be executed. For more details on kickstart post scripts, please refer to the <strong>Red Hat Enterprise Linux System Administration Guide.</strong></source>
+ <source>You can edit the post script for this kickstart below. First, commands related to @@PRODUCT_NAME@@ will automatically be performed (for example, system registration to @@PRODUCT_NAME@@). Next, the non-chroot post script will be executed, and finally the post script will be executed. For more details on kickstart post scripts, please refer to the <strong>Red Hat Enterprise Linux System Administration Guide.</strong></source>
<context-group name="ctx">
<context context-type="sourcefile">/rhn/kickstart/KickstartPostEdit.do</context>
</context-group>
diff --git a/java/code/src/com/redhat/rhn/frontend/strings/jsp/StringResource_pt_BR.xml b/java/code/src/com/redhat/rhn/frontend/strings/jsp/StringResource_pt_BR.xml
index 72b1982..e6d99e4 100644
--- a/java/code/src/com/redhat/rhn/frontend/strings/jsp/StringResource_pt_BR.xml
+++ b/java/code/src/com/redhat/rhn/frontend/strings/jsp/StringResource_pt_BR.xml
@@ -11333,7 +11333,7 @@ Please note that some manual configuration of these scripts may still be require
You can access the network in this section, but you must use IP addresses (name service has not been configured at this point). For more details on
kickstart pre scripts, please refer to the <strong>Red Hat Enterprise Linux System Administration Guide.</strong>
<br/><br/>
-You can also edit the post script for this kickstart below. First, commands related to @@PRODUCT_NAME@@ will automatically be performed (for example, esystem registration to @@PRODUCT_NAME@@).
+You can also edit the post script for this kickstart below. First, commands related to @@PRODUCT_NAME@@ will automatically be performed (for example, system registration to @@PRODUCT_NAME@@).
Next, the non-chroot post script will be executed, and finally the post script will be executed. For more details on kickstart post scripts, please refer to
the <strong>Red Hat Enterprise Linux System Administration Guide.</strong></source>
<context-group name="ctx">
@@ -11412,7 +11412,7 @@ o <strong>Guia de Administração de Sistemas Red Hat Enterprise Li
<trans-unit id="post.jsp.summary">
- <source>You can edit the post script for this kickstart below. First, commands related to @@PRODUCT_NAME@@ will automatically be performed (for example, esystem registration to @@PRODUCT_NAME@@). Next, the non-chroot post script will be executed, and finally the post script will be executed. For more details on kickstart post scripts, please refer to the <strong>Red Hat Enterprise Linux System Administration Guide.</strong></source>
+ <source>You can edit the post script for this kickstart below. First, commands related to @@PRODUCT_NAME@@ will automatically be performed (for example, system registration to @@PRODUCT_NAME@@). Next, the non-chroot post script will be executed, and finally the post script will be executed. For more details on kickstart post scripts, please refer to the <strong>Red Hat Enterprise Linux System Administration Guide.</strong></source>
<context-group name="ctx">
<context context-type="sourcefile">/rhn/kickstart/KickstartPostEdit.do</context>
</context-group>
diff --git a/java/code/src/com/redhat/rhn/frontend/strings/jsp/StringResource_ru.xml b/java/code/src/com/redhat/rhn/frontend/strings/jsp/StringResource_ru.xml
index 462e1b8..8833af1 100644
--- a/java/code/src/com/redhat/rhn/frontend/strings/jsp/StringResource_ru.xml
+++ b/java/code/src/com/redhat/rhn/frontend/strings/jsp/StringResource_ru.xml
@@ -11323,7 +11323,7 @@ Please note that some manual configuration of these scripts may still be require
You can access the network in this section, but you must use IP addresses (name service has not been configured at this point). For more details on
kickstart pre scripts, please refer to the <strong>Red Hat Enterprise Linux System Administration Guide.</strong>
<br/><br/>
-You can also edit the post script for this kickstart below. First, commands related to @@PRODUCT_NAME@@ will automatically be performed (for example, esystem registration to @@PRODUCT_NAME@@).
+You can also edit the post script for this kickstart below. First, commands related to @@PRODUCT_NAME@@ will automatically be performed (for example, system registration to @@PRODUCT_NAME@@).
Next, the non-chroot post script will be executed, and finally the post script will be executed. For more details on kickstart post scripts, please refer to
the <strong>Red Hat Enterprise Linux System Administration Guide.</strong></source>
<context-group name="ctx">
@@ -11402,7 +11402,7 @@ the <strong>Red Hat Enterprise Linux System Administration Guide.</stro
<trans-unit id="post.jsp.summary">
- <source>You can edit the post script for this kickstart below. First, commands related to @@PRODUCT_NAME@@ will automatically be performed (for example, esystem registration to @@PRODUCT_NAME@@). Next, the non-chroot post script will be executed, and finally the post script will be executed. For more details on kickstart post scripts, please refer to the <strong>Red Hat Enterprise Linux System Administration Guide.</strong></source>
+ <source>You can edit the post script for this kickstart below. First, commands related to @@PRODUCT_NAME@@ will automatically be performed (for example, system registration to @@PRODUCT_NAME@@). Next, the non-chroot post script will be executed, and finally the post script will be executed. For more details on kickstart post scripts, please refer to the <strong>Red Hat Enterprise Linux System Administration Guide.</strong></source>
<context-group name="ctx">
<context context-type="sourcefile">/rhn/kickstart/KickstartPostEdit.do</context>
</context-group>
diff --git a/java/code/src/com/redhat/rhn/frontend/strings/jsp/StringResource_ta.xml b/java/code/src/com/redhat/rhn/frontend/strings/jsp/StringResource_ta.xml
index 79d4049..7e1b3d4 100644
--- a/java/code/src/com/redhat/rhn/frontend/strings/jsp/StringResource_ta.xml
+++ b/java/code/src/com/redhat/rhn/frontend/strings/jsp/StringResource_ta.xml
@@ -11329,7 +11329,7 @@ Please note that some manual configuration of these scripts may still be require
You can access the network in this section, but you must use IP addresses (name service has not been configured at this point). For more details on
kickstart pre scripts, please refer to the <strong>Red Hat Enterprise Linux System Administration Guide.</strong>
<br/><br/>
-You can also edit the post script for this kickstart below. First, commands related to @@PRODUCT_NAME@@ will automatically be performed (for example, esystem registration to @@PRODUCT_NAME@@).
+You can also edit the post script for this kickstart below. First, commands related to @@PRODUCT_NAME@@ will automatically be performed (for example, system registration to @@PRODUCT_NAME@@).
Next, the non-chroot post script will be executed, and finally the post script will be executed. For more details on kickstart post scripts, please refer to
the <strong>Red Hat Enterprise Linux System Administration Guide.</strong></source>
<context-group name="ctx">
@@ -11408,7 +11408,7 @@ the <strong>Red Hat Enterprise Linux System Administration Guide.</stro
<trans-unit id="post.jsp.summary">
- <source>You can edit the post script for this kickstart below. First, commands related to @@PRODUCT_NAME@@ will automatically be performed (for example, esystem registration to @@PRODUCT_NAME@@). Next, the non-chroot post script will be executed, and finally the post script will be executed. For more details on kickstart post scripts, please refer to the <strong>Red Hat Enterprise Linux System Administration Guide.</strong></source>
+ <source>You can edit the post script for this kickstart below. First, commands related to @@PRODUCT_NAME@@ will automatically be performed (for example, system registration to @@PRODUCT_NAME@@). Next, the non-chroot post script will be executed, and finally the post script will be executed. For more details on kickstart post scripts, please refer to the <strong>Red Hat Enterprise Linux System Administration Guide.</strong></source>
<context-group name="ctx">
<context context-type="sourcefile">/rhn/kickstart/KickstartPostEdit.do</context>
</context-group>
diff --git a/java/code/src/com/redhat/rhn/frontend/strings/jsp/StringResource_zh_CN.xml b/java/code/src/com/redhat/rhn/frontend/strings/jsp/StringResource_zh_CN.xml
index 7105fbe..058b71c 100644
--- a/java/code/src/com/redhat/rhn/frontend/strings/jsp/StringResource_zh_CN.xml
+++ b/java/code/src/com/redhat/rhn/frontend/strings/jsp/StringResource_zh_CN.xml
@@ -11337,7 +11337,7 @@ Kickstart 侧写的引导装载程序和分区选项,有可能覆盖用户定
You can access the network in this section, but you must use IP addresses (name service has not been configured at this point). For more details on
kickstart pre scripts, please refer to the <strong>Red Hat Enterprise Linux System Administration Guide.</strong>
<br/><br/>
-You can also edit the post script for this kickstart below. First, commands related to @@PRODUCT_NAME@@ will automatically be performed (for example, esystem registration to @@PRODUCT_NAME@@).
+You can also edit the post script for this kickstart below. First, commands related to @@PRODUCT_NAME@@ will automatically be performed (for example, system registration to @@PRODUCT_NAME@@).
Next, the non-chroot post script will be executed, and finally the post script will be executed. For more details on kickstart post scripts, please refer to
the <strong>Red Hat Enterprise Linux System Administration Guide.</strong></source>
<context-group name="ctx">
@@ -11416,7 +11416,7 @@ kickstart 前脚本的内容可以在 <strong>《红帽企业版 Linux 系
<trans-unit id="post.jsp.summary">
- <source>You can edit the post script for this kickstart below. First, commands related to @@PRODUCT_NAME@@ will automatically be performed (for example, esystem registration to @@PRODUCT_NAME@@). Next, the non-chroot post script will be executed, and finally the post script will be executed. For more details on kickstart post scripts, please refer to the <strong>Red Hat Enterprise Linux System Administration Guide.</strong></source>
+ <source>You can edit the post script for this kickstart below. First, commands related to @@PRODUCT_NAME@@ will automatically be performed (for example, system registration to @@PRODUCT_NAME@@). Next, the non-chroot post script will be executed, and finally the post script will be executed. For more details on kickstart post scripts, please refer to the <strong>Red Hat Enterprise Linux System Administration Guide.</strong></source>
<context-group name="ctx">
<context context-type="sourcefile">/rhn/kickstart/KickstartPostEdit.do</context>
</context-group>
diff --git a/java/code/src/com/redhat/rhn/frontend/strings/jsp/StringResource_zh_TW.xml b/java/code/src/com/redhat/rhn/frontend/strings/jsp/StringResource_zh_TW.xml
index 20e5aca..967a5e0 100644
--- a/java/code/src/com/redhat/rhn/frontend/strings/jsp/StringResource_zh_TW.xml
+++ b/java/code/src/com/redhat/rhn/frontend/strings/jsp/StringResource_zh_TW.xml
@@ -11325,7 +11325,7 @@ Please note that some manual configuration of these scripts may still be require
You can access the network in this section, but you must use IP addresses (name service has not been configured at this point). For more details on
kickstart pre scripts, please refer to the <strong>Red Hat Enterprise Linux System Administration Guide.</strong>
<br/><br/>
-You can also edit the post script for this kickstart below. First, commands related to @@PRODUCT_NAME@@ will automatically be performed (for example, esystem registration to @@PRODUCT_NAME@@).
+You can also edit the post script for this kickstart below. First, commands related to @@PRODUCT_NAME@@ will automatically be performed (for example, system registration to @@PRODUCT_NAME@@).
Next, the non-chroot post script will be executed, and finally the post script will be executed. For more details on kickstart post scripts, please refer to
the <strong>Red Hat Enterprise Linux System Administration Guide.</strong></source>
<context-group name="ctx">
@@ -11404,7 +11404,7 @@ the <strong>Red Hat Enterprise Linux System Administration Guide.</stro
<trans-unit id="post.jsp.summary">
- <source>You can edit the post script for this kickstart below. First, commands related to @@PRODUCT_NAME@@ will automatically be performed (for example, esystem registration to @@PRODUCT_NAME@@). Next, the non-chroot post script will be executed, and finally the post script will be executed. For more details on kickstart post scripts, please refer to the <strong>Red Hat Enterprise Linux System Administration Guide.</strong></source>
+ <source>You can edit the post script for this kickstart below. First, commands related to @@PRODUCT_NAME@@ will automatically be performed (for example, system registration to @@PRODUCT_NAME@@). Next, the non-chroot post script will be executed, and finally the post script will be executed. For more details on kickstart post scripts, please refer to the <strong>Red Hat Enterprise Linux System Administration Guide.</strong></source>
<context-group name="ctx">
<context context-type="sourcefile">/rhn/kickstart/KickstartPostEdit.do</context>
</context-group>
13 years, 1 month