Updating A NST System - Revision history

Paul Blankenbaker: /* How do I report repository errors? */

2010-10-14T23:57:19Z

How do I report repository errors?

← Older revision		Revision as of 19:57, 14 October 2010
Line 75:		Line 75:

	'''*WARNING*''' Make sure you explicitly list the packages you want to update, otherwise '''MANY UNWANTED UPDATES MIGHT OCCUR!'''		'''*WARNING*''' Make sure you explicitly list the packages you want to update, otherwise '''MANY UNWANTED UPDATES MIGHT OCCUR!'''

			= What Packages Have Signature Issues =

			== jre x86_64 ==

			There is a issue with the Java Run Time package (jre) on the x86_64 architecture that prevents the package from being signed. When new updates become available for this package, your system will fail to install them unless you specify the ''--nogpgcheck'' option. For example:

			[root@probe-eth0 ~]# yum update
			Loaded plugins: fastestmirror, filter-data, keys, list-data, presto, refresh-
			: packagekit
			Loading mirror speeds from cached hostfile
			* NstRepo: networksecuritytoolkit.org
			* fedora: mirror.fdcservers.net
			* updates: mirror.steadfast.net
			Skipping filters plugin, no data
			Setting up Update Process
			Resolving Dependencies
			Skipping filters plugin, no data
			--> Running transaction check
			---> Package jre.x86_64 0:1.6.0_22-fcs set to be updated
			---> Package nst-jre.noarch 0:1.6.0_22-2.nst13 set to be updated
			--> Finished Dependency Resolution

			Dependencies Resolved

			================================================================================
			Package Arch Version Repository Size
			================================================================================
			Updating:
			jre x86_64 1.6.0_22-fcs NstRepo 19 M
			nst-jre noarch 1.6.0_22-2.nst13 NstRepo 11 k

			Transaction Summary
			================================================================================
			Upgrade 2 Package(s)

			Total size: 19 M
			Is this ok [y/N]: y
			Downloading Packages:


			Package jre-1.6.0_22-fcs.x86_64.rpm is not signed
			[root@probe-eth0 ~]#

			When this happens (it should only happen on 64 bit machines), you need to upgrade the ''jre'' and the ''nst-jre'' package (which depends on the ''jre'' package) using the ''--nogpgcheck'' option as shown below:

			[root@probe-eth0 ~]# yum --nogpgcheck update jre nst-jre
			Loaded plugins: fastestmirror, filter-data, keys, list-data, presto, refresh-
			: packagekit
			Loading mirror speeds from cached hostfile
			* NstRepo: networksecuritytoolkit.org
			* fedora: mirror.fdcservers.net
			* updates: mirror.steadfast.net
			Skipping filters plugin, no data
			Setting up Update Process
			Resolving Dependencies
			Skipping filters plugin, no data
			--> Running transaction check
			---> Package jre.x86_64 0:1.6.0_22-fcs set to be updated
			---> Package nst-jre.noarch 0:1.6.0_22-2.nst13 set to be updated
			--> Finished Dependency Resolution

			Dependencies Resolved

			=================================================================================
			Package Arch Version Repository Size
			=================================================================================
			Updating:
			jre x86_64 1.6.0_22-fcs NstRepo 19 M
			nst-jre noarch 1.6.0_22-2.nst13 NstRepo 11 k

			Transaction Summary
			=================================================================================
			Upgrade 2 Package(s)

			Total size: 19 M
			Is this ok [y/N]: y
			Downloading Packages:
			Running rpm_check_debug
			Running Transaction Test
			Transaction Test Succeeded
			Running Transaction
			Updating : jre-1.6.0_22-fcs.x86_64 1/4
			Unpacking JAR files...
			rt.jar...
			jsse.jar...
			charsets.jar...
			localedata.jar...
			plugin.jar...
			javaws.jar...
			deploy.jar...
			Updating : nst-jre-1.6.0_22-2.nst13.noarch 2/4
			Cleanup : nst-jre-1.6.0_21-2.nst13.noarch 3/4
			Cleanup : jre-1.6.0_21-fcs.x86_64 4/4

			Updated:
			jre.x86_64 0:1.6.0_22-fcs nst-jre.noarch 0:1.6.0_22-2.nst13

			Complete!
			[root@probe-eth0 ~]#

	= How do I report repository errors? =		= How do I report repository errors? =

Paul Blankenbaker: /* How do I report a Fedora repository error? */

2009-10-02T13:14:40Z

How do I report a Fedora repository error?

← Older revision		Revision as of 09:14, 2 October 2009
Line 81:		Line 81:

	Try: https://fedoraproject.org/wiki/Bugzilla		Try: https://fedoraproject.org/wiki/Bugzilla


	=== rubygem* - Missing Dependency Issue ===		=== rubygem* - Missing Dependency Issue ===

Paul Blankenbaker: /* rubygem* - Missing Dependency Issue */

2009-10-02T13:14:06Z

rubygem* - Missing Dependency Issue

← Older revision		Revision as of 09:14, 2 October 2009
Line 87:		Line 87:
	The "''Missing Dependency''" issue related to the ''rubygem*'' packages has been reported.		The "''Missing Dependency''" issue related to the ''rubygem*'' packages has been reported.

	The bug entry can be found at: https://bugzilla.redhat.com/show_bug.cgi?id=~~503909 (then again, maybe this isn't the same error).~~		The bug entry can be found at: https://bugzilla.redhat.com/show_bug.cgi?id=526839

	== How do I report a NST repository error? ==		== How do I report a NST repository error? ==

Paul Blankenbaker: /* How do I report a Fedora repository error? */

2009-10-02T13:09:49Z

How do I report a Fedora repository error?

← Older revision		Revision as of 09:09, 2 October 2009
Line 81:		Line 81:

	Try: https://fedoraproject.org/wiki/Bugzilla		Try: https://fedoraproject.org/wiki/Bugzilla


			=== rubygem* - Missing Dependency Issue ===

			The "''Missing Dependency''" issue related to the ''rubygem*'' packages has been reported.

			The bug entry can be found at: https://bugzilla.redhat.com/show_bug.cgi?id=503909 (then again, maybe this isn't the same error).

	== How do I report a NST repository error? ==		== How do I report a NST repository error? ==

Paul Blankenbaker: /* How do I report a Fedora repository error? */

2009-10-02T13:03:27Z

How do I report a Fedora repository error?

← Older revision		Revision as of 09:03, 2 October 2009
Line 80:		Line 80:
	== How do I report a Fedora repository error? ==		== How do I report a Fedora repository error? ==

	~~Not sure yet - but will be tracking this down~~.		Try: https://fedoraproject.org/wiki/Bugzilla

	== How do I report a NST repository error? ==		== How do I report a NST repository error? ==

Paul Blankenbaker: /* What Package Issues Might I See After Updating? */

2009-10-02T00:56:57Z

What Package Issues Might I See After Updating?

← Older revision		Revision as of 20:56, 1 October 2009
Line 91:		Line 91:

	The following describes some of the packages which require a NST ''tweak''.		The following describes some of the packages which require a NST ''tweak''.

			== Why do I see JavaScript errors when using the NST WUI? ==

			When the '''nstwui''' package is updated (or whenever the '''nstmenu -m update''' command is run), you may see one or more of the following issues:

			* JavaScript errors may appear in your browser when using the NST WUI.

			* The menu bar at the top of the NST WUI may fail to render.

			This condition may occur frequently as the '''nstwui''' package is frequently updated.

			This condition occurs because the files cached by your browser are out of sync with the newly updated files on the NST system.

			To recover from this issue, you can try a "forced reload" of the page (hold down the Shift key and press the ''Reload'' icon in Firefox - use the Control key in Internet Explorer).

			If that doesn't work, try clearing your browser's cache.

	== Why can't I run '''yumex''' as root? ==		== Why can't I run '''yumex''' as root? ==

Rwh: /* From the Command Line */

2009-10-01T18:52:48Z

From the Command Line

← Older revision		Revision as of 14:52, 1 October 2009
Line 8:		Line 8:
	== From the Command Line ==		== From the Command Line ==

	yum update		[root@sprint ~]# yum update

	Or, if there are missing dependencies:		Or, if there are missing dependencies:

	yum --skip-broken update		[root@sprint ~]# yum --skip-broken update

	== From the Fluxbox Desktop ==		== From the Fluxbox Desktop ==

Paul Blankenbaker: /* What Package Issues Might I See After Updating? */

2009-10-01T18:51:50Z

What Package Issues Might I See After Updating?

← Older revision		Revision as of 14:51, 1 October 2009
Line 87:		Line 87:

	= What Package Issues Might I See After Updating? =		= What Package Issues Might I See After Updating? =

			Depending upon what packages are updated on your system, you may see some issues after performing a system update. Many of this issues can be accounted for by applying the necessary NST ''tweaks'' by invoking the '''nstpostupdate''' command after performing your '''yum''' update.

			The following describes some of the packages which require a NST ''tweak''.

	== Why can't I run '''yumex''' as root? ==		== Why can't I run '''yumex''' as root? ==

Paul Blankenbaker at 18:48, 1 October 2009

2009-10-01T18:48:36Z

← Older revision		Revision as of 14:48, 1 October 2009
Line 76:		Line 76:
	'''*WARNING*''' Make sure you explicitly list the packages you want to update, otherwise '''MANY UNWANTED UPDATES MIGHT OCCUR!'''		'''*WARNING*''' Make sure you explicitly list the packages you want to update, otherwise '''MANY UNWANTED UPDATES MIGHT OCCUR!'''

			= How do I report repository errors? =

	= How do I report a Fedora repository error? =		== How do I report a Fedora repository error? ==

	Not sure yet - but will be tracking this down.		Not sure yet - but will be tracking this down.

	= How do I report a NST repository error? =		== How do I report a NST repository error? ==

	The easiest way is to post a message to the [https://sourceforge.net/projects/nst/forums/forum/361524 NST Forum] at SourceForge.		The easiest way is to post a message to the [https://sourceforge.net/projects/nst/forums/forum/361524 NST Forum] at SourceForge.

			= What Package Issues Might I See After Updating? =

			== Why can't I run '''yumex''' as root? ==

			The default installation of Fedora's '''yumex''' package does not allow one to start '''yumex''' as the ''root'' user.

			There is a NST ''tweak'' which patches the '''yumex''' package to adjust for this. This will be applied automatically for you if you run the '''nstpostupdate''' command. However, if you don't want to reset your system passwords and apply this tweak individually, you may do so by running the following command:

			[root@sprint ~]# /etc/nst/tweaks/10nst-config-yumex.tweak
			[root@sprint ~]#

Paul Blankenbaker: /* What Should I Do After Updating A NST System? */

2009-10-01T18:37:49Z

What Should I Do After Updating A NST System?

← Older revision		Revision as of 14:37, 1 October 2009
Line 34:		Line 34:
	[[Image:Warning.png‎]] NOTE: It is a good idea to stop network monitoring services ('''ntop''', '''snort''', etc) before invoking the above command.		[[Image:Warning.png‎]] NOTE: It is a good idea to stop network monitoring services ('''ntop''', '''snort''', etc) before invoking the above command.

	~~Running this command multiple times should not harm your system configuration.~~ This command will do the following:		This command will do the following:

	* Make you reset the encrypted system passwords (it runs the '''nstpasswd''' script). This is necessary if a package update from Fedora resets or clears a system password. This will replace existing '''ssh''' keys and reset passwords for many different applications (if you had individually set passwords you will need to do so again).		* Make you reset the encrypted system passwords (it runs the '''nstpasswd''' script). This is necessary if a package update from Fedora resets or clears a system password. This will replace existing '''ssh''' keys and reset passwords for many different applications (if you had individually set passwords you will need to do so again).