Fix Package Versioning Issues on Linux

15 minutes
  • 3 Learning Objectives

About this Hands-on Lab

On Red Hat, `dnf` helps you install packages and then continues to aid in the management of these packages after their install. One of the key features of `dnf` (and `yum` before it) is that it tracks not just the package itself, but also how the package relates to its dependencies — and the things that depend on this. `dnf versionlock` gives you even greater control of the package/dependency relationship, letting you lock packages to specific versions, preventing updates. In this lab, you’ll explore how versionlocking works in relation to your `ruby` package.

_This lab is not approved or sponsored by Red Hat._

Learning Objectives

Successfully complete this lab by achieving the following learning objectives:

Reproduce the Issue

Attempt to update ruby, or install ruby 2.5.9 directly.

Review versionlock

Use the dnf versionlock command to discover and resolve any locked versions of ruby.

Attempt to Update ruby

Install ruby 2.5.9.

Additional Resources

A legacy ruby application is hosted on an app server. The server has been pulled out of production in preparation for an update to both the application and the underlying infrastructure; however, when you attempt to actually update ruby to version 2.5.9, the server indicates there is no update. When you run a ruby -v it indicates ruby is still on version 2.5.3.

Discover the reason ruby is not updating, resolve the issue, and install ruby 2.5.9.

This lab is not approved or sponsored by Red Hat.

What are Hands-on Labs

Hands-on Labs are real environments created by industry experts to help you learn. These environments help you gain knowledge and experience, practice without compromising your system, test without risk, destroy without fear, and let you learn from your mistakes. Hands-on Labs: practice your skills before delivering in the real world.

Sign In
Welcome Back!

Psst…this one if you’ve been moved to ACG!

Get Started
Who’s going to be learning?