How to Install and Uninstall perl-Test-CheckChanges.noarch Package on Red Hat Enterprise Linux 9 (RHEL 9)

Last updated: July 04,2024

1. Install "perl-Test-CheckChanges.noarch" package

This guide let you learn how to install perl-Test-CheckChanges.noarch on Red Hat Enterprise Linux 9 (RHEL 9)


    
        
            $
        

        
            
                sudo dnf update
            
                    
    
    Copied


    
        
            $
        

        
            
                sudo dnf install
            
                        
                perl-Test-CheckChanges.noarch
            
                    
    
    Copied

2. Uninstall "perl-Test-CheckChanges.noarch" package

Please follow the instructions below to uninstall perl-Test-CheckChanges.noarch on Red Hat Enterprise Linux 9 (RHEL 9):


    
        
            $
        

        
            
                sudo dnf remove
            
                        
                perl-Test-CheckChanges.noarch
            
                    
    
    Copied


    
        
            $
        

        
            
                sudo dnf autoremove
            
                    
    
    Copied

3. Information about the perl-Test-CheckChanges.noarch package on Red Hat Enterprise Linux 9 (RHEL 9)

Last metadata expiration check: 1:59:57 ago on Mon Feb 26 07:04:30 2024.
Available Packages
Name : perl-Test-CheckChanges
Version : 0.14
Release : 34.el9
Architecture : noarch
Size : 26 k
Source : perl-Test-CheckChanges-0.14-34.el9.src.rpm
Repository : epel
Summary : Check that the Changes file matches the distribution
URL : https://metacpan.org/release/Test-CheckChanges
License : GPL+ or Artistic
Description : This module checks that your Changes file has an entry for the current version
: of the Module being tested. The version information for the distribution being
: tested is taken out of the Build data, or if that is not found, out of the
: Makefile. It then attempts to open, in order, a file with the name Changes or
: CHANGES. The Changes file is then parsed for version numbers. If one and only
: one of the version numbers matches, the test passes; otherwise the test fails.
: A message with the current version is printed if the test passes; otherwise
: diagnostic messages are printed to help explain the failure.