Updating A NST System

How Do I Update Packages On A NST System?

From the NST WUI

• From the menu bar, select: "System|Downloads & Updates|NST Package Update Management".
• Press the "Update NST System" button.

From the Command Line

yum update

Or, if there are missing dependencies:

yum --skip-broken update

From the Fluxbox Desktop

Need menu sequence for yumex and maybe others.

From the GNOME Desktop

Need menu sequence for yumex and maybe others.

What Should I Do After Updating A NST System?

Depending upon what packages are updated on the system, you may need to run the command:

nstliveinst -m post-update

There is a alias provided which run the above command and can be invoked via:

nstpostupdate

Running this command multiple times should not harm your system configuration. 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.

• Rebuild the Fluxbox and NST WUI menus in case applications were added or removed from the system.

• Run the scripts found under the /etc/nst/tweaks directory to apply some post installation adjustments to some Fedora packages (for example, the yumex package needs to be tweaked in order to allow the root user the ability to start the application).

What Are My Options For Resolving Missing Dependency Errors?

The Fedora repositories had proved to be pretty reliable for us for about 6 months during development. However, (shortly after the NST v2.11.0 release), Fedora introduced a repository error in which the Fedora Updates repository was in a bad state (only a subset of the necessary files were moved from the Testing area to the Updates area).

This resulted in a Missing Dependency error when updating a system:

[root@sprint ~]# yum update
Loaded plugins: fastestmirror, refresh-packagekit

... omitted yum output ...

Error: Missing Dependency: rubygem(activesupport) = 2.3.2 is needed by package rubygem-rails-2.3.2-3.fc11.noarch (installed)
 You could try using --skip-broken to work around the problem
 You could try running: package-cleanup --problems
                        package-cleanup --dupes
                        rpm -Va --nofiles --nodigest
[root@sprint ~]#

Using --skip-broken

The easiest way to work around this problem is to include the --skip-broken option.

yum --skip-broken update

Enabling the "Fedora Testing" Repository

In some cases (like the rubygem missing dependency issue), the problem is due to the fact that only a subset of the necessary files were moved from the Fedora Testing repository into the Fedora Updates area. If you know this is the case, you can enable the Fedora Testing area when updating these packages.

For example, to work around the rubygem issue on 2009-10-01, the following command can be run:

yum --enablerepo=updates-testing update rubygem*

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

How do I report a Fedora repository error?

Not sure yet - but will be tracking this down.

How do I report a NST repository error?

The easiest way is to post a message to the NST Forum at SourceForge.