tests_perl_critic_freenode.txt

tests/autoyast/autoyast_reboot.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/autoyast/autoyast_reboot.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/autoyast/autoyast_verify.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/autoyast/autoyast_verify.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/autoyast/clone.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/autoyast/clone.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/autoyast/console.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/autoyast/console.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/autoyast/login.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/autoyast/login.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/autoyast/logs.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/autoyast/logs.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/autoyast/repos.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/autoyast/repos.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/autoyast/verify_btrfs.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/autoyast/verify_btrfs.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/autoyast/verify_firewalld.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/autoyast/verify_firewalld.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/autoyast/wicked.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/autoyast/wicked.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/autoyast/verify_btrfs_clone.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/autoyast/verify_btrfs_clone.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/autoyast/prepare_profile.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/autoyast/prepare_profile.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/autoyast/verify_disk_as_pv.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/autoyast/verify_disk_as_pv.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/autoyast/verify_disk_as_pv_clone.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/autoyast/verify_disk_as_pv_clone.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/autoyast/installation.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/autoyast/installation.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/autoyast/verify_ext4.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/autoyast/verify_ext4.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/boot/boot_to_desktop.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/boot/boot_to_desktop.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/boot/grub_test_snapshot.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/boot/grub_test_snapshot.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/boot/qa_net_boot_from_hdd.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/boot/qa_net_boot_from_hdd.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/boot/snapper_rollback.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/boot/snapper_rollback.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/boot/uefi_bootmenu.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/boot/uefi_bootmenu.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/boot/boot_from_pxe.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/caasp/create_autoyast.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/caasp/create_autoyast.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/caasp/create_autoyast.pm: Used module XML::Simple at line 17, column 1.  XML::Simple tries to coerce complex XML documents into perl data structures. This leads to overcomplicated structures and unexpected behavior. Use a proper DOM parser instead like XML::LibXML, XML::TreeBuilder, XML::Twig, or Mojo::DOM.  (Severity: 4)
tests/caasp/filesystem_ro.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/caasp/filesystem_ro.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/caasp/first_boot.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/caasp/first_boot.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/caasp/journal_check.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/caasp/journal_check.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/caasp/libzypp_config.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/caasp/libzypp_config.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/caasp/nfs_client.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/caasp/nfs_client.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/caasp/nfs_client.pm: Using $a or $b outside sort() at line 52, column 16.  $a and $b are special package variables for use in sort() and related functions. Declaring them as lexicals like "my $a" may break sort(). Use different variable names.  (Severity: 4)
tests/caasp/nfs_client.pm: Using $a or $b outside sort() at line 55, column 13.  $a and $b are special package variables for use in sort() and related functions. Declaring them as lexicals like "my $a" may break sort(). Use different variable names.  (Severity: 4)
tests/caasp/nfs_client.pm: Using $a or $b outside sort() at line 58, column 16.  $a and $b are special package variables for use in sort() and related functions. Declaring them as lexicals like "my $a" may break sort(). Use different variable names.  (Severity: 4)
tests/caasp/nfs_client.pm: Using $a or $b outside sort() at line 81, column 16.  $a and $b are special package variables for use in sort() and related functions. Declaring them as lexicals like "my $a" may break sort(). Use different variable names.  (Severity: 4)
tests/caasp/nfs_client.pm: Using $a or $b outside sort() at line 84, column 13.  $a and $b are special package variables for use in sort() and related functions. Declaring them as lexicals like "my $a" may break sort(). Use different variable names.  (Severity: 4)
tests/caasp/nfs_client.pm: Using $a or $b outside sort() at line 87, column 16.  $a and $b are special package variables for use in sort() and related functions. Declaring them as lexicals like "my $a" may break sort(). Use different variable names.  (Severity: 4)
tests/caasp/nfs_client.pm: Using $a or $b outside sort() at line 107, column 16.  $a and $b are special package variables for use in sort() and related functions. Declaring them as lexicals like "my $a" may break sort(). Use different variable names.  (Severity: 4)
tests/caasp/nfs_client.pm: Using $a or $b outside sort() at line 110, column 13.  $a and $b are special package variables for use in sort() and related functions. Declaring them as lexicals like "my $a" may break sort(). Use different variable names.  (Severity: 4)
tests/caasp/nfs_client.pm: Using $a or $b outside sort() at line 113, column 13.  $a and $b are special package variables for use in sort() and related functions. Declaring them as lexicals like "my $a" may break sort(). Use different variable names.  (Severity: 4)
tests/caasp/oci_install.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/caasp/oci_password.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/caasp/oci_register.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/caasp/oci_register.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/caasp/one_line_checks.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/caasp/one_line_checks.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/caasp/overlayfs.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/caasp/overlayfs.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/caasp/rcshell_start.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/caasp/rcshell_start.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/caasp/rebootmgr.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/caasp/rebootmgr.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/caasp/register_and_check.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/caasp/register_and_check.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/caasp/register_toolchain.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/caasp/register_toolchain.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/caasp/services_enabled.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/caasp/services_enabled.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/caasp/shift_version.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/caasp/shift_version.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/caasp/stack_add_remove.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/caasp/stack_add_remove.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/caasp/stack_bootstrap.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/caasp/stack_bootstrap.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/caasp/stack_configure.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/caasp/stack_configure.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/caasp/stack_conformance.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/caasp/stack_conformance.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/caasp/stack_finalize.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/caasp/stack_finalize.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/caasp/stack_kubernetes.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/caasp/stack_kubernetes.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/caasp/stack_reboot.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/caasp/stack_reboot.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/caasp/stack_worker.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/caasp/stack_worker.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/caasp/transactional_update.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/caasp/transactional_update.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/caasp/stack_update.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/caasp/stack_update.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/caasp/stack_cap.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/caasp/stack_cap.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/caasp/stack_initialize.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/caasp/stack_initialize.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/caasp/oci_keyboard.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/caasp/oci_overview.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/caasp/oci_overview.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/caasp/oci_role.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/caasp/stack_admin.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/caasp/stack_admin.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/console/a2ps.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/console/a2ps.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/console/acpi.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/console/acpi.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/console/aide_check.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/console/aide_check.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/console/apache_nss.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/console/apache_nss.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/console/apache_ssl.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/console/apache_ssl.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/console/aplay.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/console/aplay.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/console/autoyast_removed.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/console/autoyast_removed.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/console/bind.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/console/bind.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/console/btrfs_autocompletion.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/console/btrfs_autocompletion.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/console/btrfs_qgroups.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/console/btrfs_qgroups.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/console/btrfs_send_receive.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/console/btrfs_send_receive.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/console/check_locked_package.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/console/check_locked_package.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/console/clamav.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/console/clamav.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/console/command_not_found.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/console/command_not_found.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/console/console_reboot.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/console/console_reboot.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/console/consoletest_finish.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/console/consoletest_finish.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/console/consoletest_setup.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/console/consoletest_setup.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/console/copy_iso_to_external_drive.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/console/copy_iso_to_external_drive.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/console/cron.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/console/cron.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/console/cryptsetup.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/console/cryptsetup.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/console/curl_https.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/console/curl_https.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/console/curl_ipv6.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/console/curl_ipv6.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/console/dns_srv.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/console/dns_srv.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/console/docker.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/console/docker.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/console/docker_compose.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/console/docker_compose.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/console/docker_image.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/console/docker_image.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/console/docker_image_rpm.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/console/docker_image_rpm.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/console/docker_runc.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/console/docker_runc.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/console/dovecot_ssl.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/console/dovecot_ssl.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/console/dstat.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/console/dstat.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/console/enable_usb_repo.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/console/enable_usb_repo.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/console/fetchmail_ssl.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/console/fetchmail_ssl.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/console/firewall_enabled.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/console/firewall_enabled.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/console/force_scheduled_tasks.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/console/force_scheduled_tasks.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/console/git.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/console/git.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/console/glibc_sanity.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/console/glibc_sanity.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/console/gpg.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/console/gpg.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/console/gpt_ptable.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/console/gpt_ptable.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/console/hostname.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/console/hostname.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/console/http_srv.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/console/http_srv.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/console/import_gpg_keys.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/console/import_gpg_keys.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/console/install_otherDE_pattern.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/console/install_otherDE_pattern.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/console/install_packages.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/console/install_packages.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/console/install_single_package.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/console/install_single_package.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/console/installation_snapshots.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/console/installation_snapshots.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/console/integration_services.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/console/integration_services.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/console/ipsec_tools_h2h.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/console/ipsec_tools_h2h.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/console/java.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/console/journalctl.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/console/journald_fss.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/console/journald_fss.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/console/kdump_and_crash.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/console/kdump_and_crash.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/console/kdump_disabled.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/console/kdump_disabled.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/console/kubeadm.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/console/kubeadm.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/console/libmicrohttpd.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/console/libmicrohttpd.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/console/libsolv_installcheck.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/console/libsolv_installcheck.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/console/lock_package.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/console/lvm_thin_check.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/console/machinery.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/console/machinery.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/console/mailx_ssl.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/console/mailx_ssl.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/console/mariadb.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/console/mariadb.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/console/mdadm.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/console/mdadm.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/console/mta.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/console/mta.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/console/mtab.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/console/mtab.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/console/mutt_ssl.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/console/mutt_ssl.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/console/mysql_odbc.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/console/mysql_srv.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/console/mysql_srv.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/console/nano.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/console/nano.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/console/ncurses.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/console/ncurses.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/console/network_hostname.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/console/network_hostname.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/console/ntp_client.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/console/ntp_client.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/console/openqa_review.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/console/openqa_review.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/console/openssl_alpn.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/console/openssl_alpn.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/console/openvswitch.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/console/openvswitch.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/console/openvswitch_ssl.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/console/openvswitch_ssl.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/console/orphaned_packages_check.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/console/orphaned_packages_check.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/console/patterns.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/console/patterns.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/console/pcre.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/console/pcre.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/console/php7.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/console/php7_mysql.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/console/php7_postgresql.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/console/postfix_tls.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/console/postfix_tls.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/console/postgresql_server.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/console/postgresql_server.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/console/pulpito.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/console/pulpito.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/console/puppet.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/console/puppet.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/console/qam_verify_package_install.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/console/qam_verify_package_install.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/console/qam_zypper_patch.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/console/qam_zypper_patch.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/console/rabbitmq.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/console/rabbitmq.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/console/rails.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/console/rails.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/console/repo_orphaned_packages_check.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/console/repo_orphaned_packages_check.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/console/rmt.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/console/rootless.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/console/rootless.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/console/rsync.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/console/rsync.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/console/rt_devel_packages.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/console/rt_devel_packages.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/console/rt_is_realtime.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/console/rt_is_realtime.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/console/rt_peak_pci.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/console/rt_peak_pci.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/console/rt_preempt_test.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/console/rt_preempt_test.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/console/runc.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/console/runc.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/console/salt.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/console/salt.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/console/scc_deregistration.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/console/scc_deregistration.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/console/shells.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/console/shells.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/console/shibboleth.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/console/skopeo.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/console/skopeo.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/console/sle15_workarounds.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/console/sle15_workarounds.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/console/sle2docker.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/console/sle2docker.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/console/snapper_cleanup.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/console/snapper_cleanup.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/console/snapper_create.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/console/snapper_create.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/console/snapper_jeos_cli.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/console/snapper_jeos_cli.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/console/snapper_thin_lvm.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/console/snapper_thin_lvm.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/console/snapper_undochange.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/console/snapper_undochange.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/console/snapper_used_space.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/console/snapper_used_space.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/console/ssh_cleanup.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/console/ssh_cleanup.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/console/ssh_pubkey.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/console/ssh_pubkey.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/console/sshd.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/console/sshd.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/console/sshd_running.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/console/sshd_running.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/console/sshfs.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/console/sshfs.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/console/steamcmd.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/console/steamcmd.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/console/suseconnect_scc.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/console/suseconnect_scc.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/console/sysctl.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/console/sysctl.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/console/syslog.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/console/syslog.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/console/system_prepare.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/console/system_prepare.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/console/systemd_testsuite.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/console/teuthology.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/console/teuthology.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/console/textinfo.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/console/textinfo.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/console/umoci.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/console/umoci.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/console/unzip.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/console/unzip.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/console/update_alternatives.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/console/update_alternatives.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/console/upgrade_snapshots.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/console/upgrade_snapshots.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/console/validate_packages_and_patterns.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/console/validate_packages_and_patterns.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/console/validate_pcm_aws.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/console/validate_pcm_aws.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/console/validate_pcm_azure.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/console/validate_pcm_azure.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/console/vim.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/console/vim.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/console/w3m_https.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/console/w3m_https.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/console/weechat.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/console/weechat.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/console/wget_https.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/console/wget_https.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/console/wget_ipv6.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/console/wget_ipv6.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/console/xfce_gnome_deps.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/console/xfce_gnome_deps.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/console/xorg_vt.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/console/xorg_vt.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/console/yast2_apparmor.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/console/yast2_apparmor.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/console/yast2_bootloader.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/console/yast2_bootloader.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/console/yast2_clone_system.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/console/yast2_clone_system.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/console/yast2_cmdline.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/console/yast2_cmdline.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/console/yast2_dm_crypt.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/console/yast2_dm_crypt.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/console/yast2_dns_server.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/console/yast2_dns_server.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/console/yast2_ftp.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/console/yast2_ftp.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/console/yast2_http.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/console/yast2_http.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/console/yast2_i.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/console/yast2_i.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/console/yast2_lan.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/console/yast2_lan.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/console/yast2_lan_hostname.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/console/yast2_lan_hostname.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/console/yast2_nfs_client.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/console/yast2_nfs_client.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/console/yast2_nfs_server.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/console/yast2_nfs_server.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/console/yast2_nis.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/console/yast2_nis.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/console/yast2_ntpclient.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/console/yast2_ntpclient.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/console/yast2_samba.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/console/yast2_samba.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/console/yast2_snapper_ncurses.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/console/yast2_snapper_ncurses.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/console/yast2_tftp.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/console/yast2_tftp.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/console/yast2_vnc.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/console/yast2_vnc.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/console/yast2_xinetd.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/console/yast2_xinetd.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/console/yast_scc.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/console/yast_scc.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/console/znc.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/console/znc.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/console/zypper_add_repos.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/console/zypper_add_repos.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/console/zypper_ar.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/console/zypper_ar.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/console/zypper_disable_deltarpm.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/console/zypper_disable_deltarpm.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/console/zypper_in.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/console/zypper_in.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/console/zypper_info.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/console/zypper_lifecycle.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/console/zypper_lifecycle.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/console/zypper_lr.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/console/zypper_lr.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/console/zypper_moo.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/console/zypper_moo.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/console/zypper_ref.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/console/zypper_ref.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/console/check_default_network_manager.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/console/check_default_network_manager.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/console/yast2_proxy.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/console/zbar.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/console/zbar.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/console/sysstat.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/console/sysstat.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/console/zypper_lifecycle_toolchain.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/console/zypper_lifecycle_toolchain.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/console/zypper_lr_validate.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/console/zypper_lr_validate.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/console/ant.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/console/ant.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/feature/feature_console/deregister.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/feature/feature_console/suseconnect.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/feature/feature_console/suseconnect.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/feature/feature_console/zypper_crit_sec_fix_only.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/feature/feature_console/zypper_releasever.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/feature/feature_console/zypper_releasever.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/fips/curl_fips_rc4_seed.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/fips/curl_fips_rc4_seed.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/fips/ecryptfs_fips.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/fips/ecryptfs_fips.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/fips/fips_setup.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/fips/fips_setup.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/fips/mozilla_nss/apache_nssfips.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/fips/mozilla_nss/apache_nssfips.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/fips/mozilla_nss/firefox_nss.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/fips/mozilla_nss/firefox_nss.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/fips/openssh/openssh_fips.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/fips/openssh/openssh_fips.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/fips/openssl/openssl_fips_alglist.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/fips/openssl/openssl_fips_alglist.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/fips/openssl/openssl_fips_hash.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/fips/openssl/openssl_fips_hash.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/fips/openssl/openssl_pubkey_dsa.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/fips/openssl/openssl_pubkey_dsa.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/fips/openssl/openssl_pubkey_rsa.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/fips/openssl/openssl_pubkey_rsa.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/fips/openssl/openssl_fips_cipher.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/fips/openssl/openssl_fips_cipher.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/fixup/enable_firewall.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/fixup/enable_firewall.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/fixup/network_configuration.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/fixup/network_configuration.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/gnuhealth/gnuhealth_client_first_time.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/gnuhealth/gnuhealth_client_first_time.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/gnuhealth/gnuhealth_client_install.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/gnuhealth/gnuhealth_client_install.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/gnuhealth/gnuhealth_client_preconfigure.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/gnuhealth/gnuhealth_client_preconfigure.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/gnuhealth/gnuhealth_install.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/gnuhealth/gnuhealth_install.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/gnuhealth/gnuhealth_setup.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/gnuhealth/gnuhealth_setup.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/ha/barrier_init.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/ha/barrier_init.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/ha/check_after_reboot.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/ha/check_after_reboot.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/ha/check_logs.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/ha/check_logs.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/ha/cluster_md.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/ha/cluster_md.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/ha/clvmd_lvmlockd.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/ha/clvmd_lvmlockd.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/ha/dlm.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/ha/dlm.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/ha/drbd_passive.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/ha/drbd_passive.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/ha/fencing.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/ha/fencing.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/ha/firewall_disable.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/ha/firewall_disable.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/ha/ha_cluster_init.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/ha/ha_cluster_init.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/ha/ha_cluster_join.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/ha/ha_cluster_join.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/ha/iscsi_client.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/ha/iscsi_client.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/ha/prepare_shutdown.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/ha/prepare_shutdown.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/ha/sle15_workarounds.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/ha/sle15_workarounds.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/ha/vg.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/ha/vg.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/ha/wait_barriers.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/ha/wait_barriers.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/ha/watchdog.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/ha/watchdog.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/ha/check_hawk.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/ha/check_hawk.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/ha/filesystem.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/ha/filesystem.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/ha/upgrade_from_sle11sp4_workarounds.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/ha/upgrade_from_sle11sp4_workarounds.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/hpc/barrier_init.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/hpc/barrier_init.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/hpc/before_test.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/hpc/conman.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/hpc/conman.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/hpc/ganglia_client.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/hpc/ganglia_server.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/hpc/genders.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/hpc/genders.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/hpc/hwloc.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/hpc/mrsh_master.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/hpc/mrsh_master.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/hpc/mrsh_slave.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/hpc/mrsh_slave.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/hpc/munge_master.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/hpc/munge_slave.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/hpc/pdsh_master.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/hpc/pdsh_master.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/hpc/pdsh_slave.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/hpc/pdsh_slave.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/hpc/powerman.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/hpc/powerman.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/hpc/product_migration.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/hpc/rasdaemon.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/hpc/rasdaemon.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/hpc/slurm_master.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/hpc/slurm_master.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/hpc/slurm_slave.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/hpc/slurm_slave.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/installation/accept_license.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/installation/accept_license.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/installation/add_update_test_repo.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/installation/add_update_test_repo.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/installation/addon_products.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/installation/addon_products.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/installation/addon_products.pm: Using $a or $b outside sort() at line 49, column 16.  $a and $b are special package variables for use in sort() and related functions. Declaring them as lexicals like "my $a" may break sort(). Use different variable names.  (Severity: 4)
tests/installation/addon_products.pm: Using $a or $b outside sort() at line 67, column 56.  $a and $b are special package variables for use in sort() and related functions. Declaring them as lexicals like "my $a" may break sort(). Use different variable names.  (Severity: 4)
tests/installation/first_boot.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/installation/first_boot.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/installation/addon_products_via_SCC_yast2.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/installation/addon_products_via_SCC_yast2.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/installation/addon_products_yast2.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/installation/addon_products_yast2.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/installation/autoyast_reboot.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/installation/autoyast_reboot.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/installation/await_install.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/installation/await_install.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/installation/boot_encrypt.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/installation/boot_encrypt.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/installation/boot_into_snapshot.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/installation/boot_into_snapshot.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/installation/boot_s390.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/installation/boot_windows.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/installation/boot_windows.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/installation/bootloader.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/installation/bootloader.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/installation/partitioning.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/installation/installation_overview.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/installation/bootloader_uefi.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/installation/bootloader_uefi.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/installation/bootloader_zkvm.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/installation/change_desktop.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/installation/data_integrity.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/installation/data_integrity.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/installation/disable_grub_graphics.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/installation/online_repos.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/installation/online_repos.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/installation/bootloader_hyperv.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/installation/disk_activation.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/installation/disk_activation.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/installation/disk_space_fill.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/installation/disk_space_release.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/installation/dud_addon.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/installation/dud_addon.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/installation/encrypted_volume_activation.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/installation/finish_desktop.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/installation/finish_desktop.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/installation/partitioning_lvm.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/installation/hostname_inst.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/installation/installation_enlargeswap.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/installation/installation_enlargeswap.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/installation/installation_mode.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/installation/addon_products_sle.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/installation/addon_products_sle.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/installation/addon_products_sle.pm: Using $a or $b outside sort() at line 50, column 16.  $a and $b are special package variables for use in sort() and related functions. Declaring them as lexicals like "my $a" may break sort(). Use different variable names.  (Severity: 4)
tests/installation/addon_products_sle.pm: Using $a or $b outside sort() at line 51, column 27.  $a and $b are special package variables for use in sort() and related functions. Declaring them as lexicals like "my $a" may break sort(). Use different variable names.  (Severity: 4)
tests/installation/addon_products_sle.pm: Using $a or $b outside sort() at line 64, column 12.  $a and $b are special package variables for use in sort() and related functions. Declaring them as lexicals like "my $a" may break sort(). Use different variable names.  (Severity: 4)
tests/installation/addon_products_sle.pm: Using $a or $b outside sort() at line 65, column 23.  $a and $b are special package variables for use in sort() and related functions. Declaring them as lexicals like "my $a" may break sort(). Use different variable names.  (Severity: 4)
tests/installation/addon_products_sle.pm: Using $a or $b outside sort() at line 74, column 12.  $a and $b are special package variables for use in sort() and related functions. Declaring them as lexicals like "my $a" may break sort(). Use different variable names.  (Severity: 4)
tests/installation/installation_overview_before.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/installation/installcheck.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/installation/installcheck.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/installation/installer_desktopselection.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/installation/installer_desktopselection.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/installation/installer_timezone.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/installation/installer_timezone.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/installation/iscsi_configuration.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/installation/iscsi_configuration.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/installation/isosize.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/installation/isosize.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/installation/keyboard_selection.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/installation/kubeadm_settings.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/installation/live_installation.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/installation/live_installation.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/installation/livecd_network_settings.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/installation/logpackages.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/installation/logs_from_installation_system.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/installation/logs_from_installation_system.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/installation/mediacheck.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/installation/mediacheck.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/installation/memtest.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/installation/memtest.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/installation/mouse_hide.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/installation/mouse_hide.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/installation/multipath.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/installation/multipath.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/installation/network_configuration.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/installation/system_role.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/installation/system_role.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/installation/partitioning_crypt_no_lvm.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/installation/partitioning_crypt_no_lvm.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/installation/partitioning_expert.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/installation/partitioning_filesystem.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/installation/partitioning_filesystem.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/installation/partitioning_finish.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/installation/partitioning_finish.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/installation/partitioning_firstdisk.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/installation/partitioning_full_lvm.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/installation/partitioning_guided.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/installation/partitioning_iscsi.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/installation/partitioning_iscsi.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/installation/grub_test.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/installation/grub_test.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/installation/partitioning_lvm_thin_provisioning.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/installation/partitioning_raid.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/installation/partitioning_resize_root.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/installation/partitioning_splitusr.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/installation/partitioning_splitusr.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/installation/partitioning_togglehome.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/installation/partitioning_togglehome.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/installation/partitioning_warnings.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/installation/post_zdup.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/installation/post_zdup.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/installation/reboot_after_installation.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/installation/reboot_after_installation.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/installation/reboot_eject_cd.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/installation/reboot_eject_cd.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/installation/reconnect_s390.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/installation/releasenotes.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/installation/releasenotes.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/installation/releasenotes.pm: Using $a or $b outside sort() at line 92, column 16.  $a and $b are special package variables for use in sort() and related functions. Declaring them as lexicals like "my $a" may break sort(). Use different variable names.  (Severity: 4)
tests/installation/releasenotes.pm: Using $a or $b outside sort() at line 93, column 28.  $a and $b are special package variables for use in sort() and related functions. Declaring them as lexicals like "my $a" may break sort(). Use different variable names.  (Severity: 4)
tests/installation/releasenotes_origin.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/installation/releasenotes_origin.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/installation/rescuesystem.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/installation/rescuesystem.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/installation/rescuesystem_validate_131.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/installation/rescuesystem_validate_131.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/installation/rescuesystem_validate_sle.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/installation/rescuesystem_validate_sle.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/installation/scc_registration.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/installation/scc_registration.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/installation/secure_boot.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/installation/select_patterns_and_packages.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/installation/select_patterns_and_packages.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/installation/setup_online_repos.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/installation/setup_online_repos.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/installation/setup_zdup.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/installation/setup_zdup.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/installation/skip_disk_activation.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/installation/skip_disk_activation.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/installation/skip_registration.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/installation/skip_registration.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/installation/sles4sap_product_installation_mode.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/installation/sles4sap_product_installation_mode.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/installation/sles4sap_wizard.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/installation/sles4sap_wizard.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/installation/sles4sap_wizard_nw.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/installation/sles4sap_wizard_nw.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/installation/sles4sap_wizard_swpm.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/installation/sles4sap_wizard_swpm.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/installation/sles4sap_wizard_trex.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/installation/sles4sap_wizard_trex.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/installation/ssh_key_setup.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/installation/start_install.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/installation/bootloader_s390.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/installation/system_workarounds.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/installation/system_workarounds.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/installation/upgrade_select.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/installation/upgrade_select.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/installation/upgrade_select_opensuse.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/installation/upgrade_select_opensuse.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/installation/user_import.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/installation/user_settings.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/installation/user_settings_root.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/installation/win10_firstboot.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/installation/win10_firstboot.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/installation/win10_installation.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/installation/win10_installation.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/installation/win10_reboot.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/installation/win10_reboot.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/installation/win10_shutdown.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/installation/win10_shutdown.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/installation/zdup.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/installation/zdup.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/installation/bootloader_spvm.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/installation/bootloader_spvm.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/installation/bootloader_svirt.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/installation/disable_grub_timeout.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/installation/welcome.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/installation/caasp_roleconf.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/iscsi/iscsi_client.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/iscsi/iscsi_client.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/iscsi/iscsi_server.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/iscsi/iscsi_server.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/jeos/diskusage.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/jeos/diskusage.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/jeos/grub2_gfxmode.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/jeos/grub2_gfxmode.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/jeos/mount_by_label.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/jeos/mount_by_label.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/jeos/record_machine_id.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/jeos/record_machine_id.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/jeos/revive_xen_domain.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/jeos/revive_xen_domain.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/jeos/root_fs_size.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/jeos/root_fs_size.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/jeos/prepare_rpi_image.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/jeos/prepare_rpi_image.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/jeos/glibc_locale.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/jeos/glibc_locale.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/jeos/firstrun.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/jeos/firstrun.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/kernel/boot_ltp.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/kernel/change_kernel.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/kernel/change_kernel.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/kernel/create_junkfile_ltp.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/kernel/ib_tests.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/kernel/ib_tests.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/kernel/install_kotd.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/kernel/install_kotd.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/kernel/mellanox_config.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/kernel/mellanox_config.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/kernel/mellanox_ofed.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/kernel/mellanox_ofed.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/kernel/nvmftests.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/kernel/nvmftests.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/kernel/proc_sys_dump.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/kernel/qa_test_klp.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/kernel/run_ltp.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/kernel/trinity.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/kernel/trinity.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/kernel/update_kernel.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/kernel/virtio_console.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/kernel/write_random.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/kernel/shutdown_ltp.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/kernel/install_ltp.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/kubic/disk_boot.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/kubic/disk_boot.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/kubic/networking.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/kubic/networking.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/kubic/repositories.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/kubic/repositories.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/linuxrc/system_boot.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/linuxrc/system_boot.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/locale/keymap_or_locale.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/locale/keymap_or_locale.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/migration/post_upgrade.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/migration/reboot_to_upgrade.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/migration/reboot_to_upgrade.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/migration/record_disk_info.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/migration/version_switch_origin_system.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/migration/version_switch_upgrade_target.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/migration/sle12_online_migration/minimal_patch.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/migration/sle12_online_migration/minimal_patch.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/migration/sle12_online_migration/online_migration_setup.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/migration/sle12_online_migration/online_migration_setup.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/migration/sle12_online_migration/post_migration.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/migration/sle12_online_migration/post_migration.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/migration/sle12_online_migration/register_system.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/migration/sle12_online_migration/register_system.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/migration/sle12_online_migration/register_without_ltss.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/migration/sle12_online_migration/register_without_ltss.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/migration/sle12_online_migration/snapper_rollback.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/migration/sle12_online_migration/snapper_rollback.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/migration/sle12_online_migration/yast2_migration.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/migration/sle12_online_migration/yast2_migration.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/migration/sle12_online_migration/zypper_migration.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/migration/sle12_online_migration/zypper_migration.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/migration/sle12_online_migration/zypper_patch.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/migration/sle12_online_migration/zypper_patch.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/migration/sle12_online_migration/pre_migration.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/migration/sle12_online_migration/pre_migration.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/networkd/networkd_bridge.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/networkd/networkd_bridge.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/networkd/networkd_dhcp.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/networkd/networkd_dhcp.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/networkd/networkd_init.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/networkd/networkd_init.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/networkd/networkd_vlan.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/networkd/networkd_vlan.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/nfv/hugepages_config.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/nfv/hugepages_config.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/nfv/prepare_env.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/nfv/prepare_env.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/nfv/run_integration_tests.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/nfv/run_integration_tests.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/nfv/run_performance_tests.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/nfv/run_performance_tests.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/nfv/trex_installation.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/nfv/trex_installation.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/nfv/trex_runner.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/nfv/trex_runner.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/publiccloud/prepare_tools.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/publiccloud/prepare_tools.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/publiccloud/az_accelerated_net.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/publiccloud/az_accelerated_net.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/publiccloud/ipa.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/publiccloud/ipa.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/publiccloud/run_ltp.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/publiccloud/run_ltp.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/publiccloud/upload_image.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/publiccloud/upload_image.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/qa_automation/acceptance.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/qa_automation/acceptance.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/qa_automation/acceptance_all.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/qa_automation/acceptance_all.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/qa_automation/acceptance_fs_stress.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/qa_automation/acceptance_fs_stress.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/qa_automation/acceptance_process_stress.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/qa_automation/acceptance_process_stress.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/qa_automation/acceptance_sched_stress.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/qa_automation/acceptance_sched_stress.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/qa_automation/install_test_suite.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/qa_automation/install_test_suite.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/qa_automation/kernel_autotest.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/qa_automation/kernel_autotest.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/qa_automation/kernel_kexec.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/qa_automation/kernel_kexec.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/qa_automation/kernel_libhugetlbfs.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/qa_automation/kernel_libhugetlbfs.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/qa_automation/kernel_lmbench.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/qa_automation/kernel_lmbench.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/qa_automation/kernel_ltp_aio_stress.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/qa_automation/kernel_ltp_aio_stress.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/qa_automation/kernel_ltp_aiodio.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/qa_automation/kernel_ltp_aiodio.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/qa_automation/kernel_ltp_commands.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/qa_automation/kernel_ltp_commands.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/qa_automation/kernel_ltp_connectors.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/qa_automation/kernel_ltp_connectors.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/qa_automation/kernel_ltp_containers.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/qa_automation/kernel_ltp_containers.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/qa_automation/kernel_ltp_controllers.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/qa_automation/kernel_ltp_controllers.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/qa_automation/kernel_ltp_dio.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/qa_automation/kernel_ltp_dio.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/qa_automation/kernel_ltp_fcntl_locktests.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/qa_automation/kernel_ltp_fcntl_locktests.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/qa_automation/kernel_ltp_filecaps.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/qa_automation/kernel_ltp_filecaps.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/qa_automation/kernel_ltp_fs.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/qa_automation/kernel_ltp_fs.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/qa_automation/kernel_ltp_fs_perms_simple.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/qa_automation/kernel_ltp_fs_perms_simple.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/qa_automation/kernel_ltp_fstests.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/qa_automation/kernel_ltp_fstests.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/qa_automation/kernel_ltp_fsx.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/qa_automation/kernel_ltp_fsx.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/qa_automation/kernel_ltp_hugetlb.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/qa_automation/kernel_ltp_hugetlb.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/qa_automation/kernel_ltp_input.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/qa_automation/kernel_ltp_input.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/qa_automation/kernel_ltp_ipc.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/qa_automation/kernel_ltp_ipc.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/qa_automation/kernel_ltp_kernel_misc.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/qa_automation/kernel_ltp_kernel_misc.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/qa_automation/kernel_ltp_leapsec.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/qa_automation/kernel_ltp_leapsec.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/qa_automation/kernel_ltp_math.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/qa_automation/kernel_ltp_math.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/qa_automation/kernel_ltp_mm.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/qa_automation/kernel_ltp_mm.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/qa_automation/kernel_ltp_openposix.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/qa_automation/kernel_ltp_openposix.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/qa_automation/kernel_ltp_pipes.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/qa_automation/kernel_ltp_pipes.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/qa_automation/kernel_ltp_pty.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/qa_automation/kernel_ltp_pty.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/qa_automation/kernel_ltp_quickhit.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/qa_automation/kernel_ltp_quickhit.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/qa_automation/kernel_ltp_sched.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/qa_automation/kernel_ltp_sched.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/qa_automation/kernel_ltp_syscalls.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/qa_automation/kernel_ltp_syscalls.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/qa_automation/kernel_ltp_timers.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/qa_automation/kernel_ltp_timers.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/qa_automation/kernel_lvm2.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/qa_automation/kernel_lvm2.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/qa_automation/kernel_lvm2_120.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/qa_automation/kernel_lvm2_120.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/qa_automation/kernel_lynis.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/qa_automation/kernel_lynis.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/qa_automation/kernel_memeat.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/qa_automation/kernel_memeat.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/qa_automation/kernel_memtester.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/qa_automation/kernel_memtester.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/qa_automation/kernel_multipath.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/qa_automation/kernel_multipath.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/qa_automation/kernel_newburn_1h.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/qa_automation/kernel_newburn_1h.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/qa_automation/kernel_xfstests.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/qa_automation/kernel_xfstests.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/qa_automation/kernel_zswap.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/qa_automation/kernel_zswap.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/qa_automation/patch_and_reboot.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/qa_automation/prepare_qa_repo.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/qa_automation/prepare_qa_repo.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/qa_automation/qa_run.pm source OK
tests/qa_automation/userspace_apache2_mod_perl.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/qa_automation/userspace_apache2_mod_perl.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/qa_automation/userspace_apparmor.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/qa_automation/userspace_apparmor.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/qa_automation/userspace_apparmor_profiles.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/qa_automation/userspace_apparmor_profiles.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/qa_automation/userspace_bind.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/qa_automation/userspace_bind.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/qa_automation/userspace_bzip2.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/qa_automation/userspace_bzip2.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/qa_automation/userspace_coreutils.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/qa_automation/userspace_coreutils.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/qa_automation/userspace_cpio.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/qa_automation/userspace_cpio.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/qa_automation/userspace_cpp_32bit.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/qa_automation/userspace_cpp_32bit.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/qa_automation/userspace_cracklib.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/qa_automation/userspace_cracklib.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/qa_automation/userspace_findutils.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/qa_automation/userspace_findutils.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/qa_automation/userspace_ftpload.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/qa_automation/userspace_ftpload.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/qa_automation/userspace_gzip.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/qa_automation/userspace_gzip.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/qa_automation/userspace_indent.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/qa_automation/userspace_indent.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/qa_automation/userspace_net_snmp.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/qa_automation/userspace_net_snmp.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/qa_automation/userspace_nfs.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/qa_automation/userspace_nfs.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/qa_automation/userspace_nfs_v4.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/qa_automation/userspace_nfs_v4.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/qa_automation/userspace_openssh.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/qa_automation/userspace_openssh.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/qa_automation/userspace_openssl.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/qa_automation/userspace_openssl.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/qa_automation/userspace_php5.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/qa_automation/userspace_php5.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/qa_automation/userspace_php7.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/qa_automation/userspace_php7.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/qa_automation/userspace_postfix.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/qa_automation/userspace_postfix.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/qa_automation/userspace_sharutils.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/qa_automation/userspace_sharutils.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/qa_automation/userspace_systemd.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/qa_automation/userspace_systemd.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/qa_automation/xfstests_device.pm source OK
tests/qa_automation/xfstests_install.pm source OK
tests/qa_automation/xfstests_logs.pm source OK
tests/qa_automation/xfstests_prepare_boot.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/qa_automation/xfstests_prepare_boot.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/qa_automation/xfstests_prepare_env.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/qa_automation/xfstests_prepare_env.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/qa_automation/xfstests_prepare_issue_case.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/qa_automation/xfstests_prepare_issue_case.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/qa_automation/xfstests_prepare_testsuite.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/qa_automation/xfstests_prepare_testsuite.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/qa_automation/xfstests_run_btrfs.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/qa_automation/xfstests_run_btrfs.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/qa_automation/xfstests_run_ext4.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/qa_automation/xfstests_run_ext4.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/qa_automation/xfstests_run_generic.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/qa_automation/xfstests_run_generic.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/qa_automation/xfstests_run_issue_case.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/qa_automation/xfstests_run_issue_case.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/qa_automation/xfstests_run_shared.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/qa_automation/xfstests_run_shared.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/qa_automation/xfstests_run_xfs.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/qa_automation/xfstests_run_xfs.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/qa_automation/execute_test_run.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/qa_automation/execute_test_run.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/qa_automation/userspace_samba.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/qa_automation/userspace_samba.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/qam-minimal/check_logs.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/qam-minimal/check_logs.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/qam-minimal/install_patterns.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/qam-minimal/install_patterns.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/qam-minimal/update_minimal.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/qam-minimal/update_minimal.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/qam-minimal/install_update.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/qam-teradata/teradata.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/remote/remote_controller.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/remote/remote_controller.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/remote/remote_target.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/remote/remote_target.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/rescuecd/rescuecd.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/rescuecd/rescuecd.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/rt/kmp_modules.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/rt/kmp_modules.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/security/apparmor/aa_autodep.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/security/apparmor/aa_autodep.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/security/apparmor/aa_complain.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/security/apparmor/aa_complain.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/security/apparmor/aa_easyprof.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/security/apparmor/aa_easyprof.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/security/apparmor/aa_enforce.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/security/apparmor/aa_enforce.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/security/apparmor/aa_genprof.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/security/apparmor/aa_genprof.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/security/apparmor/aa_logprof.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/security/apparmor/aa_logprof.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/security/apparmor/aa_notify.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/security/apparmor/aa_notify.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/security/apparmor/aa_status.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/security/apparmor/aa_status.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/security/openscap/oscap_generating_fix.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/security/openscap/oscap_generating_fix.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/security/openscap/oscap_generating_report.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/security/openscap/oscap_generating_report.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/security/openscap/oscap_info.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/security/openscap/oscap_info.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/security/openscap/oscap_oval_scanning.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/security/openscap/oscap_oval_scanning.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/security/openscap/oscap_remediating_offline.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/security/openscap/oscap_remediating_offline.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/security/openscap/oscap_remediating_online.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/security/openscap/oscap_remediating_online.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/security/openscap/oscap_result_datastream.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/security/openscap/oscap_result_datastream.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/security/openscap/oscap_setup.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/security/openscap/oscap_setup.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/security/openscap/oscap_source_datastream.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/security/openscap/oscap_source_datastream.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/security/openscap/oscap_validating.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/security/openscap/oscap_validating.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/security/openscap/oscap_xccdf_scanning.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/security/openscap/oscap_xccdf_scanning.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/security/selinux/selinux_setup.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/security/selinux/selinux_setup.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/security/selinux/selinux_smoke.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/security/selinux/selinux_smoke.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/security/selinux/sestatus.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/security/selinux/sestatus.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/ses/deepsea_cluster_deploy.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/ses/deepsea_cluster_deploy.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/ses/deepsea_testsuite.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/ses/deepsea_testsuite.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/ses/install_ses.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/ses/install_ses.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/ses/nodes_preparation.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/ses/nodes_preparation.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/ses/openattic.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/ses/openattic.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/shutdown/grub_set_bootargs.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/shutdown/grub_set_bootargs.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/shutdown/hyperv_upload_assets.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/shutdown/shutdown.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/shutdown/shutdown.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/shutdown/svirt_upload_assets.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/shutdown/cleanup_before_shutdown.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/shutdown/cleanup_before_shutdown.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/slenkins/slenkins_control.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/slenkins/slenkins_control.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/slenkins/slenkins_control_network.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/slenkins/slenkins_control_network.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/slenkins/login.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/slenkins/login.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/slenkins/slenkins_node.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/slenkins/slenkins_node.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/slepos/adminserver_configured.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/slepos/boot_image.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/slepos/build_images_kiwi.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/slepos/build_offline_images_creator.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/slepos/build_offline_images_kiwi.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/slepos/check_services.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/slepos/download_images.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/slepos/prepare.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/slepos/register_images.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/slepos/run_posInitAdminserver.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/slepos/run_posInitBranchserver.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/slepos/run_possyncimages.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/slepos/use_smt_for_kiwi.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/slepos/wait.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/slepos/wait.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/slepos/zypper_add_repo.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/slepos/zypper_install_adminserver.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/slepos/zypper_install_branchserver.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/slepos/zypper_install_imageserver.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/sles4sap/netweaver_ascs_install.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/sles4sap/netweaver_ascs_install.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/sles4sap/patterns.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/sles4sap/patterns.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/sles4sap/sapconf.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/sles4sap/sapconf.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/sles4sap/saptune.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/sles4sap/saptune.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/sles4sap/desktop_icons.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/sles4sap/desktop_icons.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/sles4sap/hana_test.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/sles4sap/hana_test.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/sles4sap/netweaver_ascs.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/sles4sap/netweaver_ascs.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/sles4sap/wizard_hana_install.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/sles4sap/wizard_hana_install.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/support_server/boot.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/support_server/boot.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/support_server/configure.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/support_server/configure.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/support_server/login.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/support_server/login.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/support_server/setup.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/support_server/setup.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/support_server/wait_children.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/support_server/wait_children.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/sysauth/sssd.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/sysauth/sssd.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/toolchain/gcc_compilation.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/toolchain/gcc_compilation.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/toolchain/gcc_fortran_compilation.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/toolchain/gcc_fortran_compilation.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/toolchain/install.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/toolchain/install.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/update/check_system_is_updated.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/update/check_system_is_updated.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/update/prepare_system_for_update_tests.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/update/prepare_system_for_update_tests.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/update/updates_packagekit_gpk.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/update/updates_packagekit_gpk.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/update/updates_packagekit_kde.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/update/updates_packagekit_kde.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/update/zypper_clear_repos.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/update/zypper_clear_repos.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/update/zypper_up.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/update/zypper_up.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/update/patch_sle.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/update/patch_sle.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/virt_autotest/guest_installation_run.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/virt_autotest/guest_migration_base.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/virt_autotest/guest_migration_config_virtualization_env.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/virt_autotest/guest_migration_config_virtualization_env.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/virt_autotest/guest_migration_dst.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/virt_autotest/guest_migration_dst.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/virt_autotest/guest_migration_dst.pm: Subroutine called with "&" sigil at line 51, column 5.  See page 175 of PBP.  (Severity: 4)
tests/virt_autotest/guest_migration_source_install_guest.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/virt_autotest/guest_migration_source_install_guest.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/virt_autotest/guest_migration_source_migrate.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/virt_autotest/guest_migration_source_migrate.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/virt_autotest/guest_migration_source_nfs_setup.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/virt_autotest/guest_migration_source_nfs_setup.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/virt_autotest/guest_migration_src.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/virt_autotest/guest_migration_src.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/virt_autotest/guest_migration_src.pm: Subroutine called with "&" sigil at line 103, column 37.  See page 175 of PBP.  (Severity: 4)
tests/virt_autotest/guest_migration_target_nfs_setup.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/virt_autotest/guest_migration_target_nfs_setup.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/virt_autotest/guest_upgrade_run.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/virt_autotest/host_upgrade_base.pm source OK
tests/virt_autotest/host_upgrade_generate_run_file.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/virt_autotest/host_upgrade_step2_run.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/virt_autotest/host_upgrade_step2_run.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/virt_autotest/host_upgrade_step3_run.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/virt_autotest/host_upgrade_step3_run.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/virt_autotest/install_package.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/virt_autotest/login_console.pm source OK
tests/virt_autotest/multi_machine_job_base.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/virt_autotest/proxymode_conn_slave.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/virt_autotest/proxymode_init_pxe_install.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/virt_autotest/proxymode_login_proxy.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/virt_autotest/proxymode_redirect_serial.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/virt_autotest/proxymode_redirect_serial.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/virt_autotest/pvusb_run.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/virt_autotest/reboot_and_wait_up.pm source OK
tests/virt_autotest/reboot_and_wait_up_normal.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/virt_autotest/setup_console_on_host.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/virt_autotest/setup_kvm_serial_console.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/virt_autotest/setup_xen_serial_console.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/virt_autotest/switch_version_and_reload_needle.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/virt_autotest/update_package.pm source OK
tests/virt_autotest/virt_autotest_base.pm: Subroutine "new" called using indirect syntax at line 43, column 21.  See page 349 of PBP.  (Severity: 5)
tests/virt_autotest/virt_utils.pm: Subroutine called with "&" sigil at line 50, column 24.  See page 175 of PBP.  (Severity: 4)
tests/virt_autotest/virt_utils.pm: Subroutine called with "&" sigil at line 109, column 29.  See page 175 of PBP.  (Severity: 4)
tests/virt_autotest/virt_v2v_dst.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/virt_autotest/virt_v2v_dst.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/virt_autotest/virt_v2v_src.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/virt_autotest/virt_v2v_src.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/virt_autotest/virt_v2v_src.pm: Subroutine called with "&" sigil at line 36, column 5.  See page 175 of PBP.  (Severity: 4)
tests/virt_autotest/reboot_and_wait_up_upgrade.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/virtualization/libvirtlxc_setup.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/virtualization/libvirtlxc_setup.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/virtualization/prepare.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/virtualization/prepare.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/virtualization/virt_install.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/virtualization/virt_install.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/virtualization/virt_top.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/virtualization/virt_top.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/virtualization/virtman_install.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/virtualization/virtman_install.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/virtualization/virtman_storage.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/virtualization/virtman_storage.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/virtualization/virtman_view.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/virtualization/virtman_view.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/virtualization/virtman_virtualnet.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/virtualization/virtman_virtualnet.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/virtualization/yast_virtualization.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/virtualization/yast_virtualization.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/virtualization/syscontainer_image_test.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/virtualization/syscontainer_image_test.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/virtualization/xen/dom_metrics.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/virtualization/xen/dom_metrics.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/virtualization/xen/guest_management.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/virtualization/xen/guest_management.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/virtualization/xen/hotplugging.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/virtualization/xen/hotplugging.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/virtualization/xen/patch_and_reboot.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/virtualization/xen/patch_and_reboot.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/virtualization/xen/prepare_guests.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/virtualization/xen/prepare_guests.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/virtualization/xen/save_and_restore.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/virtualization/xen/save_and_restore.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/wicked/before_test.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/wicked/before_test.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/wicked/locks_init.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/wicked/locks_init.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/wicked/advanced/ref/t01_gre_tunnel_legacy.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/wicked/advanced/ref/t01_gre_tunnel_legacy.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/wicked/advanced/ref/t02_gre_tunnel_xml.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/wicked/advanced/ref/t02_gre_tunnel_xml.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/wicked/advanced/ref/t03_sit_tunnel_legacy.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/wicked/advanced/ref/t03_sit_tunnel_legacy.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/wicked/advanced/ref/t04_sit_tunnel_xml.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/wicked/advanced/ref/t04_sit_tunnel_xml.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/wicked/advanced/ref/t05_ipip_tunnel_legacy.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/wicked/advanced/ref/t05_ipip_tunnel_legacy.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/wicked/advanced/ref/t06_ipip_tunnel_xml.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/wicked/advanced/ref/t06_ipip_tunnel_xml.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/wicked/advanced/ref/t07_tun_interface_legacy.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/wicked/advanced/ref/t07_tun_interface_legacy.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/wicked/advanced/ref/t08_tun_interface_xml.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/wicked/advanced/ref/t08_tun_interface_xml.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/wicked/advanced/ref/t09_tap_interface_legacy.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/wicked/advanced/ref/t09_tap_interface_legacy.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/wicked/advanced/ref/t10_tap_interface_xml.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/wicked/advanced/ref/t10_tap_interface_xml.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/wicked/advanced/ref/t11_bridge_interface_legacy.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/wicked/advanced/ref/t11_bridge_interface_legacy.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/wicked/advanced/ref/t12_bridge_interface_xml.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/wicked/advanced/ref/t12_bridge_interface_xml.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/wicked/advanced/sut/t01_gre_tunnel_legacy.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/wicked/advanced/sut/t01_gre_tunnel_legacy.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/wicked/advanced/sut/t02_gre_tunnel_xml.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/wicked/advanced/sut/t02_gre_tunnel_xml.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/wicked/advanced/sut/t03_sit_tunnel_legacy.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/wicked/advanced/sut/t03_sit_tunnel_legacy.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/wicked/advanced/sut/t04_sit_tunnel_xml.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/wicked/advanced/sut/t04_sit_tunnel_xml.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/wicked/advanced/sut/t05_ipip_tunnel_legacy.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/wicked/advanced/sut/t05_ipip_tunnel_legacy.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/wicked/advanced/sut/t06_ipip_tunnel_xml.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/wicked/advanced/sut/t06_ipip_tunnel_xml.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/wicked/advanced/sut/t07_tun_interface_legacy.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/wicked/advanced/sut/t07_tun_interface_legacy.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/wicked/advanced/sut/t08_tun_interface_xml.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/wicked/advanced/sut/t08_tun_interface_xml.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/wicked/advanced/sut/t09_tap_interface_legacy.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/wicked/advanced/sut/t09_tap_interface_legacy.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/wicked/advanced/sut/t10_tap_interface_xml.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/wicked/advanced/sut/t10_tap_interface_xml.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/wicked/advanced/sut/t11_bridge_interface_legacy.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/wicked/advanced/sut/t11_bridge_interface_legacy.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/wicked/advanced/sut/t12_bridge_interface_xml.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/wicked/advanced/sut/t12_bridge_interface_xml.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/wicked/startandstop/ref/t01_standalone_card_ifdown_ifreload.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/wicked/startandstop/ref/t01_standalone_card_ifdown_ifreload.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/wicked/startandstop/ref/t02_bridge_ifreload.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/wicked/startandstop/ref/t02_bridge_ifreload.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/wicked/startandstop/ref/t03_bridge_ifup_ifreload.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/wicked/startandstop/ref/t03_bridge_ifup_ifreload.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/wicked/startandstop/ref/t04_bridge_ifup_remove_all_config_ifreload.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/wicked/startandstop/ref/t04_bridge_ifup_remove_all_config_ifreload.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/wicked/startandstop/ref/t05_bridge_ifup_remove_one_config_ifreload.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/wicked/startandstop/ref/t05_bridge_ifup_remove_one_config_ifreload.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/wicked/startandstop/ref/t06_bridge_ifdown_create_new_config_ifreload_ifdown_ifup.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/wicked/startandstop/ref/t06_bridge_ifdown_create_new_config_ifreload_ifdown_ifup.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/wicked/startandstop/ref/t07_bridge_ifdown_remove_one_config_ifreload_ifdown_ifup.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/wicked/startandstop/ref/t07_bridge_ifdown_remove_one_config_ifreload_ifdown_ifup.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/wicked/startandstop/ref/t08_sit_tunnel_ifdown.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/wicked/startandstop/ref/t08_sit_tunnel_ifdown.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/wicked/startandstop/ref/t09_openvpn_tunnel_ifdown.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/wicked/startandstop/ref/t09_openvpn_tunnel_ifdown.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/wicked/startandstop/ref/t10_vlan_ifup_all_ifdown_one_card.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/wicked/startandstop/ref/t10_vlan_ifup_all_ifdown_one_card.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/wicked/startandstop/sut/t01_standalone_card_ifdown_ifreload.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/wicked/startandstop/sut/t01_standalone_card_ifdown_ifreload.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/wicked/startandstop/sut/t02_bridge_ifreload.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/wicked/startandstop/sut/t02_bridge_ifreload.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/wicked/startandstop/sut/t03_bridge_ifup_ifreload.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/wicked/startandstop/sut/t03_bridge_ifup_ifreload.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/wicked/startandstop/sut/t04_bridge_ifup_remove_all_config_ifreload.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/wicked/startandstop/sut/t04_bridge_ifup_remove_all_config_ifreload.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/wicked/startandstop/sut/t05_bridge_ifup_remove_one_config_ifreload.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/wicked/startandstop/sut/t05_bridge_ifup_remove_one_config_ifreload.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/wicked/startandstop/sut/t06_bridge_ifdown_create_new_config_ifreload_ifdown_ifup.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/wicked/startandstop/sut/t06_bridge_ifdown_create_new_config_ifreload_ifdown_ifup.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/wicked/startandstop/sut/t08_sit_tunnel_ifdown.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/wicked/startandstop/sut/t08_sit_tunnel_ifdown.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/wicked/startandstop/sut/t09_openvpn_tunnel_ifdown.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/wicked/startandstop/sut/t09_openvpn_tunnel_ifdown.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/wicked/startandstop/sut/t10_vlan_ifup_all_ifdown_one_card.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/wicked/startandstop/sut/t10_vlan_ifup_all_ifdown_one_card.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/wicked/startandstop/sut/t07_bridge_ifdown_remove_one_config_ifreload_ifdown_ifup.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/wicked/startandstop/sut/t07_bridge_ifdown_remove_one_config_ifreload_ifdown_ifup.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/wicked/basic/ref/t01_basic.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/wicked/basic/ref/t01_basic.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/wicked/basic/ref/t02_static_addresses_legacy.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/wicked/basic/ref/t02_static_addresses_legacy.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/wicked/basic/ref/t03_static_addresses_xml.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/wicked/basic/ref/t03_static_addresses_xml.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/wicked/basic/ref/t04_dynamic_addresses_legacy.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/wicked/basic/ref/t04_dynamic_addresses_legacy.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/wicked/basic/ref/t05_dynamic_addresses_xml.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/wicked/basic/ref/t05_dynamic_addresses_xml.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/wicked/basic/ref/t06_static_routes_legacy.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/wicked/basic/ref/t06_static_routes_legacy.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/wicked/basic/ref/t07_static_routes_xml.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/wicked/basic/ref/t07_static_routes_xml.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/wicked/basic/sut/t03_static_addresses_xml.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/wicked/basic/sut/t03_static_addresses_xml.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/wicked/basic/sut/t07_static_routes_xml.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/wicked/basic/sut/t07_static_routes_xml.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/wicked/basic/sut/t01_basic.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/wicked/basic/sut/t01_basic.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/wicked/basic/sut/t02_static_addresses_legacy.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/wicked/basic/sut/t02_static_addresses_legacy.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/wicked/basic/sut/t04_dynamic_addresses_legacy.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/wicked/basic/sut/t04_dynamic_addresses_legacy.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/wicked/basic/sut/t05_dynamic_addresses_xml.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/wicked/basic/sut/t05_dynamic_addresses_xml.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/wicked/basic/sut/t06_static_routes_legacy.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/wicked/basic/sut/t06_static_routes_legacy.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/ImageMagick.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/amarok.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/amarok.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/awesome_menu.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/awesome_menu.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/awesome_reconfigure_openqa.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/awesome_reconfigure_openqa.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/awesome_xterm.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/awesome_xterm.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/chrome.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/chrome.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/chromium.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/chromium.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/desktop_mainmenu.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/desktop_mainmenu.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/desktop_runner.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/desktop_runner.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/dolphin.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/dolphin.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/enlightenment_first_start.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/enlightenment_first_start.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/enlightenment_reconfigure_openqa.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/enlightenment_reconfigure_openqa.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/eog.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/eog.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/firefox.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/firefox_audio.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/firefox_audio.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/gdm_session_switch.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/gdm_session_switch.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/gedit.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/gedit.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/ghostscript.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/gimp.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/gimp.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/glxgears.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/glxgears.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/gnome_control_center.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/gnome_control_center.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/gnome_music.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/gnome_music.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/gnome_terminal.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/gnome_terminal.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/gnome_tweak_tool.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/gnome_tweak_tool.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/hexchat.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/hexchat.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/hexchat_ssl.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/hexchat_ssl.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/inkscape.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/inkscape.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/kate.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/kate.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/keyboard_layout_gdm.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/keyboard_layout_gdm.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/khelpcenter.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/khelpcenter.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/kontact.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/kontact.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/libcamgm.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/libcamgm.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/lxqt_reconfigure_openqa.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/lxqt_reconfigure_openqa.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/mate_reconfigure_openqa.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/mate_reconfigure_openqa.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/mate_terminal.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/mate_terminal.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/midori.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/midori.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/multi_users_dm.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/multi_users_dm.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/nautilus.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/nautilus.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/oocalc.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/oocalc.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/ooffice.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/ooffice.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/oomath.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/oomath.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/reboot_and_install.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/reboot_and_install.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/reboot_gnome.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/reboot_gnome.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/reboot_icewm.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/reboot_icewm.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/reboot_kde.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/reboot_kde.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/reboot_lxde.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/reboot_lxde.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/reboot_plasma5.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/reboot_plasma5.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/reboot_xfce.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/reboot_xfce.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/rhythmbox.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/rhythmbox.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/ristretto.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/ristretto.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/seahorse.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/seahorse.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/seahorse_sshkey.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/seahorse_sshkey.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/smt.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/smt_disconnect_external.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/smt_disconnect_internal.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/smt_disconnect_prepare.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/smt_disconnect_prepare.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/ssh_key_check.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/ssh_key_check.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/ssh_key_verify.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/start_wayland_plasma5.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/start_wayland_plasma5.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/steam.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/steam.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/stunnel.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/stunnel.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/systemsettings.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/systemsettings.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/systemsettings5.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/systemsettings5.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/terminology.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/terminology.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/thunar.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/thunar.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/thunderbird.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/thunderbird.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/user_defined_snapshot.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/user_defined_snapshot.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/user_gui_login.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/user_gui_login.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/vlc.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/vlc.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/vnc_two_passwords.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/vnc_two_passwords.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/window_system.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/window_system.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/wine.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/wine.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/wireshark.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/x11_login.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/x11_login.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/x11_setup.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/x11_setup.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/x3270_ssl.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/xchat.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/xchat.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/xfce4_appfinder.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/xfce4_appfinder.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/xfce4_terminal.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/xfce4_terminal.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/xfce_lightdm_logout_login.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/xfce_lightdm_logout_login.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/xfce_notification.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/xfce_notification.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/xterm.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/xterm.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/yast2_snapper.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/yast2_snapper.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/gnucash.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/gnucash.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/nis_client.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/nis_client.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/yast2_lan_restart.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/yast2_lan_restart.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/yast2_lan_restart_devices.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/yast2_lan_restart_devices.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/nis_server.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/nis_server.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/evolution.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/evolution.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/sshxterm.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/sshxterm.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/brasero/brasero_launch.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/brasero/brasero_launch.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/empathy/empathy_irc.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/empathy/empathy_irc.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/evince/evince_find.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/evince/evince_find.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/evince/evince_open.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/evince/evince_open.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/evince/evince_rotate_zoom.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/evince/evince_rotate_zoom.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/evince/evince_view.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/evince/evince_view.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/evolution/evolution_mail_imap.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/evolution/evolution_mail_imap.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/evolution/evolution_mail_pop.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/evolution/evolution_mail_pop.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/evolution/evolution_meeting_imap.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/evolution/evolution_meeting_imap.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/evolution/evolution_meeting_pop.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/evolution/evolution_meeting_pop.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/evolution/evolution_prepare_servers.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/evolution/evolution_prepare_servers.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/evolution/evolution_timezone_setup.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/evolution/evolution_timezone_setup.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/evolution/evolution_smoke.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/evolution/evolution_smoke.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/firefox/firefox_appearance.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/firefox/firefox_appearance.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/firefox/firefox_developertool.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/firefox/firefox_developertool.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/firefox/firefox_downloading.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/firefox/firefox_downloading.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/firefox/firefox_extensions.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/firefox/firefox_extensions.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/firefox/firefox_flashplayer.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/firefox/firefox_flashplayer.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/firefox/firefox_fullscreen.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/firefox/firefox_fullscreen.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/firefox/firefox_gnomeshell.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/firefox/firefox_gnomeshell.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/firefox/firefox_headers.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/firefox/firefox_headers.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/firefox/firefox_html5.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/firefox/firefox_html5.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/firefox/firefox_localfiles.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/firefox/firefox_localfiles.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/firefox/firefox_mhtml.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/firefox/firefox_mhtml.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/firefox/firefox_pagesaving.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/firefox/firefox_pagesaving.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/firefox/firefox_passwd.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/firefox/firefox_passwd.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/firefox/firefox_pdf.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/firefox/firefox_pdf.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/firefox/firefox_rss.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/firefox/firefox_rss.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/firefox/firefox_smoke.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/firefox/firefox_smoke.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/firefox/firefox_ssl.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/firefox/firefox_ssl.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/firefox/firefox_urlsprotocols.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/firefox/firefox_urlsprotocols.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/firefox/firefox_private.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/firefox/firefox_private.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/firefox/firefox_changesaving.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/firefox/firefox_changesaving.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/firefox/firefox_emaillink.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/firefox/firefox_emaillink.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/firefox/firefox_extcontent.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/firefox/firefox_extcontent.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/firefox/firefox_plugins.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/firefox/firefox_plugins.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/gedit/gedit_about.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/gedit/gedit_about.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/gedit/gedit_launch.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/gedit/gedit_launch.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/gedit/gedit_save.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/gedit/gedit_save.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/gnomeapps/aa_disable_updates.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/gnomeapps/aa_disable_updates.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/gnomeapps/aisleriot.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/gnomeapps/aisleriot.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/gnomeapps/baobab.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/gnomeapps/baobab.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/gnomeapps/cheese.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/gnomeapps/cheese.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/gnomeapps/dconf_editor.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/gnomeapps/dconf_editor.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/gnomeapps/epiphany.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/gnomeapps/epiphany.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/gnomeapps/file_roller.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/gnomeapps/file_roller.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/gnomeapps/gnome_2048.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/gnomeapps/gnome_2048.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/gnomeapps/gnome_books.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/gnomeapps/gnome_books.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/gnomeapps/gnome_builder.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/gnomeapps/gnome_builder.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/gnomeapps/gnome_calculator.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/gnomeapps/gnome_calculator.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/gnomeapps/gnome_calendar.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/gnomeapps/gnome_calendar.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/gnomeapps/gnome_characters.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/gnomeapps/gnome_characters.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/gnomeapps/gnome_clocks.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/gnomeapps/gnome_clocks.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/gnomeapps/gnome_contacts.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/gnomeapps/gnome_contacts.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/gnomeapps/gnome_dictionary.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/gnomeapps/gnome_dictionary.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/gnomeapps/gnome_documents.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/gnomeapps/gnome_documents.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/gnomeapps/gnome_font_viewer.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/gnomeapps/gnome_font_viewer.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/gnomeapps/gnome_games.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/gnomeapps/gnome_games.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/gnomeapps/gnome_logs.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/gnomeapps/gnome_logs.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/gnomeapps/gnome_maps.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/gnomeapps/gnome_maps.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/gnomeapps/gnome_multi_writer.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/gnomeapps/gnome_multi_writer.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/gnomeapps/gnome_news.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/gnomeapps/gnome_news.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/gnomeapps/gnome_photos.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/gnomeapps/gnome_photos.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/gnomeapps/gnome_recipes.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/gnomeapps/gnome_recipes.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/gnomeapps/gnome_screenshot.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/gnomeapps/gnome_screenshot.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/gnomeapps/gnome_system_monitor.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/gnomeapps/gnome_system_monitor.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/gnomeapps/gnome_taquin.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/gnomeapps/gnome_taquin.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/gnomeapps/gnome_todo.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/gnomeapps/gnome_todo.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/gnomeapps/gnome_weather.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/gnomeapps/gnome_weather.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/gnomeapps/polari.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/gnomeapps/polari.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/gnomeapps/vinagre.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/gnomeapps/vinagre.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/gnomecase/gnome_classic_switch.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/gnomecase/gnome_classic_switch.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/gnomecase/gnome_window_switcher.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/gnomecase/gnome_window_switcher.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/gnomecase/login_test.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/gnomecase/login_test.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/gnomecase/nautilus_cut_file.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/gnomecase/nautilus_cut_file.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/gnomecase/nautilus_permission.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/gnomecase/nautilus_permission.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/gnomecase/application_starts_on_login.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/gnomecase/application_starts_on_login.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/gnomecase/change_password.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/gnomecase/change_password.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/gnomecase/gnome_default_applications.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/gnomecase/gnome_default_applications.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/gnomecase/nautilus_open_ftp.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/gnomecase/nautilus_open_ftp.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/gnote/gnote_edit_format.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/gnote/gnote_edit_format.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/gnote/gnote_first_run.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/gnote/gnote_first_run.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/gnote/gnote_link_note.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/gnote/gnote_link_note.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/gnote/gnote_rename_title.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/gnote/gnote_rename_title.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/gnote/gnote_search_all.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/gnote/gnote_search_all.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/gnote/gnote_search_body.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/gnote/gnote_search_body.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/gnote/gnote_search_title.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/gnote/gnote_search_title.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/gnote/gnote_undo_redo.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/gnote/gnote_undo_redo.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/groupwise/groupwise.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/groupwise/groupwise.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/libreoffice/libreoffice_default_theme.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/libreoffice/libreoffice_default_theme.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/libreoffice/libreoffice_double_click_file.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/libreoffice/libreoffice_double_click_file.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/libreoffice/libreoffice_mainmenu_favorites.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/libreoffice/libreoffice_mainmenu_favorites.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/libreoffice/libreoffice_open_specified_file.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/libreoffice/libreoffice_open_specified_file.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/libreoffice/libreoffice_pyuno_bridge.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/libreoffice/libreoffice_pyuno_bridge.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/libreoffice/libreoffice_pyuno_bridge_no_evolution_dep.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/libreoffice/libreoffice_pyuno_bridge_no_evolution_dep.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/libreoffice/libreoffice_recent_documents.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/libreoffice/libreoffice_recent_documents.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/libreoffice/libreoffice_mainmenu_components.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/libreoffice/libreoffice_mainmenu_components.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/network/NM_wpa2_enterprise.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/network/hwsim_wpa2_enterprise_setup.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/network/yast2_network_use_nm.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/pidgin/clean_pidgin.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/pidgin/clean_pidgin.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/pidgin/pidgin_IRC.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/pidgin/pidgin_IRC.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/pidgin/prep_pidgin.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/pidgin/prep_pidgin.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/piglit/piglit.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/remote_desktop/onetime_vncsession_multilogin_failed.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/remote_desktop/onetime_vncsession_multilogin_failed.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/remote_desktop/onetime_vncsession_xvnc_java.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/remote_desktop/onetime_vncsession_xvnc_java.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/remote_desktop/onetime_vncsession_xvnc_remmina.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/remote_desktop/onetime_vncsession_xvnc_remmina.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/remote_desktop/onetime_vncsession_xvnc_tigervnc.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/remote_desktop/onetime_vncsession_xvnc_tigervnc.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/remote_desktop/persistent_vncsession_xvnc.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/remote_desktop/persistent_vncsession_xvnc.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/remote_desktop/vino_client.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/remote_desktop/vino_client.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/remote_desktop/vino_screensharing_available.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/remote_desktop/vino_screensharing_available.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/remote_desktop/vino_server.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/remote_desktop/vino_server.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/remote_desktop/x11_forwarding_openssh.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/remote_desktop/x11_forwarding_openssh.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/remote_desktop/xdmcp_gdm.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/remote_desktop/xdmcp_gdm.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/remote_desktop/xdmcp_xdm.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/remote_desktop/xdmcp_xdm.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/shotwell/shotwell_edit.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/shotwell/shotwell_edit.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/shotwell/shotwell_export.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/shotwell/shotwell_export.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/shotwell/shotwell_import.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/shotwell/shotwell_import.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/tomboy/tomboy_AlreadyRunning.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/tomboy/tomboy_AlreadyRunning.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/tomboy/tomboy_Hotkeys.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/tomboy/tomboy_Hotkeys.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/tomboy/tomboy_Print.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/tomboy/tomboy_Print.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/tomboy/tomboy_TestFindFunctionalityInSearchAllNotes.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/tomboy/tomboy_TestFindFunctionalityInSearchAllNotes.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/tomboy/tomboy_TestUndoRedoFeature.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/tomboy/tomboy_TestUndoRedoFeature.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/totem/totem_launch.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/totem/totem_launch.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/tracker/clean_tracker.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/tracker/clean_tracker.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/tracker/prep_tracker.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/tracker/prep_tracker.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/tracker/tracker_mainmenu.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/tracker/tracker_mainmenu.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/tracker/tracker_open_apps.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/tracker/tracker_open_apps.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/tracker/tracker_pref_starts.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/tracker/tracker_pref_starts.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/tracker/tracker_search_in_nautilus.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/tracker/tracker_search_in_nautilus.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/tracker/tracker_starts.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/tracker/tracker_starts.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/tracker/tracker_searchall.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/tracker/tracker_searchall.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/tracker/tracker_by_command.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/tracker/tracker_by_command.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/tracker/tracker_info.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/tracker/tracker_info.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/toolkits/fltk.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/toolkits/fltk.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/toolkits/gtk2.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/toolkits/gtk2.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/toolkits/gtk3.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/toolkits/gtk3.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/toolkits/motif.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/toolkits/motif.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/toolkits/prepare.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/toolkits/prepare.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/toolkits/qt4.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/toolkits/qt4.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/toolkits/qt5.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/toolkits/qt5.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/toolkits/swing.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/toolkits/swing.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/toolkits/tk.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/toolkits/tk.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/toolkits/x11.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/toolkits/x11.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/ibus/ibus_clean.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/ibus/ibus_clean.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/ibus/ibus_installation.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/ibus/ibus_installation.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/ibus/ibus_test_ch.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/ibus/ibus_test_ch.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/ibus/ibus_test_jp.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/ibus/ibus_test_jp.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/x11/ibus/ibus_test_kr.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/x11/ibus/ibus_test_kr.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/xfstests/enable_kdump.pm source OK
tests/xfstests/generate_report.pm source OK
tests/xfstests/install.pm source OK
tests/xfstests/partition.pm source OK
tests/xfstests/run.pm source OK
tests/yast2_gui/yast2_bootloader.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/yast2_gui/yast2_bootloader.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/yast2_gui/yast2_datetime.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/yast2_gui/yast2_datetime.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/yast2_gui/yast2_firewall.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/yast2_gui/yast2_firewall.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/yast2_gui/yast2_hostnames.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/yast2_gui/yast2_hostnames.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/yast2_gui/yast2_lang.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/yast2_gui/yast2_lang.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/yast2_gui/yast2_network_settings.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/yast2_gui/yast2_network_settings.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/yast2_gui/yast2_software_management.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/yast2_gui/yast2_software_management.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/yast2_gui/yast2_users.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/yast2_gui/yast2_users.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/yast2_gui/yast2_control_center.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/yast2_gui/yast2_control_center.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/network/openvpn_client.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/network/openvpn_client.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/network/openvpn_server.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/network/openvpn_server.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/network/salt_master.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/network/salt_master.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/network/salt_minion.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/network/salt_minion.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/network/setup_multimachine.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/network/setup_multimachine.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
tests/network/vsftpd.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
tests/network/vsftpd.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
products/caasp/main.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
products/kubic/main.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
products/opensuse/main.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
products/sle/main.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
products/sle/main.pm: Using $a or $b outside sort() at line 326, column 12.  $a and $b are special package variables for use in sort() and related functions. Declaring them as lexicals like "my $a" may break sort(). Use different variable names.  (Severity: 4)
products/sle/main.pm: Using $a or $b outside sort() at line 327, column 23.  $a and $b are special package variables for use in sort() and related functions. Declaring them as lexicals like "my $a" may break sort(). Use different variable names.  (Severity: 4)
products/sle/main.pm: Using $a or $b outside sort() at line 346, column 12.  $a and $b are special package variables for use in sort() and related functions. Declaring them as lexicals like "my $a" may break sort(). Use different variable names.  (Severity: 4)
products/sle/main.pm: Using $a or $b outside sort() at line 347, column 13.  $a and $b are special package variables for use in sort() and related functions. Declaring them as lexicals like "my $a" may break sort(). Use different variable names.  (Severity: 4)
products/sle/main.pm: Using $a or $b outside sort() at line 348, column 27.  $a and $b are special package variables for use in sort() and related functions. Declaring them as lexicals like "my $a" may break sort(). Use different variable names.  (Severity: 4)
products/sle/main.pm: Using $a or $b outside sort() at line 348, column 45.  $a and $b are special package variables for use in sort() and related functions. Declaring them as lexicals like "my $a" may break sort(). Use different variable names.  (Severity: 4)
products/sle/main.pm: Using $a or $b outside sort() at line 349, column 23.  $a and $b are special package variables for use in sort() and related functions. Declaring them as lexicals like "my $a" may break sort(). Use different variable names.  (Severity: 4)
products/sle/main.pm: Using $a or $b outside sort() at line 349, column 45.  $a and $b are special package variables for use in sort() and related functions. Declaring them as lexicals like "my $a" may break sort(). Use different variable names.  (Severity: 4)
lib/apachetest.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
lib/apachetest.pm: Variable declared in conditional statement at line 67, column 9.  Declare variables outside of the condition.  (Severity: 4)
lib/apparmortest.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
lib/bootloader_setup.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
lib/btrfs_test.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
lib/caasp_controller.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
lib/console_yasttest.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
lib/consoletest.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
lib/ctcs2_to_junit.pm: Subroutine "new" called using indirect syntax at line 48, column 20.  See page 349 of PBP.  (Severity: 5)
lib/data_integrity_utils.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
lib/hpcbase.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
lib/installation_user_settings.pm source OK
lib/installbasetest.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
lib/iscsi.pm source OK
lib/isotovideo.pm source OK
lib/kdump_utils.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
lib/kdump_utils.pm: Using $a or $b outside sort() at line 50, column 16.  $a and $b are special package variables for use in sort() and related functions. Declaring them as lexicals like "my $a" may break sort(). Use different variable names.  (Severity: 4)
lib/kdump_utils.pm: Using $a or $b outside sort() at line 51, column 25.  $a and $b are special package variables for use in sort() and related functions. Declaring them as lexicals like "my $a" may break sort(). Use different variable names.  (Severity: 4)
lib/kdump_utils.pm: Using $a or $b outside sort() at line 52, column 13.  $a and $b are special package variables for use in sort() and related functions. Declaring them as lexicals like "my $a" may break sort(). Use different variable names.  (Severity: 4)
lib/kernel.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
lib/kernel.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
lib/linuxrc.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
lib/mailtest.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
lib/main_ltp.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
lib/mm_network.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
lib/mm_network.pm: <>/<<>>/readline/readdir/each result not explicitly assigned in while condition at line 29, column 5.  When used alone in a while condition, the <>/<<>> operator, readline, readdir, and each functions assign their result to $_, but do not localize it. Assign the result to an explicit lexical variable instead (my $line = <...>, my $dir = readdir ...).  (Severity: 4)
lib/mm_tests.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
lib/network_utils.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
lib/networkdbase.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
lib/openscaptest.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
lib/power_action_utils.pm source OK
lib/proxymode.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
lib/qam.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
lib/repo_tools.pm source OK
lib/rescuecdstep.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
lib/selenium.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
lib/serial_terminal.pm source OK
lib/suseconnect_register.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
lib/suseconnect_register.pm: Variable declared in conditional statement at line 55, column 9.  Declare variables outside of the condition.  (Severity: 4)
lib/suseconnect_register.pm: Variable declared in conditional statement at line 56, column 9.  Declare variables outside of the condition.  (Severity: 4)
lib/susedistribution.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
lib/upload_system_log.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
lib/virtmanager.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
lib/windows_utils.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
lib/y2_common.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
lib/y2snapper_common.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
lib/yast2_shortcuts.pm source OK
lib/yast2_widget_utils.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
lib/y2x11test.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
lib/ipmi_backend_utils.pm: Subroutine called with "&" sigil at line 230, column 34.  See page 175 of PBP.  (Severity: 4)
lib/ipmi_backend_utils.pm: Subroutine called with "&" sigil at line 234, column 9.  See page 175 of PBP.  (Severity: 4)
lib/ipmi_backend_utils.pm: Subroutine called with "&" sigil at line 242, column 24.  See page 175 of PBP.  (Severity: 4)
lib/ipmi_backend_utils.pm: Subroutine called with "&" sigil at line 243, column 59.  See page 175 of PBP.  (Severity: 4)
lib/ipmi_backend_utils.pm: Subroutine called with "&" sigil at line 249, column 9.  See page 175 of PBP.  (Severity: 4)
lib/wickedbase.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
lib/xml_utils.pm: No package matching the module filename at line 1, column 1.  A Perl module file is expected to contain a matching package name, so it can be used after loading it from the filesystem. A module file that doesn't contain a matching package name usually indicates an error.  (Severity: 4)
lib/xml_utils.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
lib/y2lan_restart_common.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
lib/hacluster.pm: Variable declared in conditional statement at line 217, column 5.  Declare variables outside of the condition.  (Severity: 4)
lib/opensusebasetest.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
lib/utils.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
lib/version_utils.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
lib/xen.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
lib/y2logsstep.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
lib/installsummarystep.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
lib/migration.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
lib/partition_setup.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
lib/x11test.pm source OK
lib/autoyast.pm source OK
lib/registration.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
lib/registration.pm: Using $a or $b outside sort() at line 652, column 12.  $a and $b are special package variables for use in sort() and related functions. Declaring them as lexicals like "my $a" may break sort(). Use different variable names.  (Severity: 4)
lib/registration.pm: Using $a or $b outside sort() at line 653, column 47.  $a and $b are special package variables for use in sort() and related functions. Declaring them as lexicals like "my $a" may break sort(). Use different variable names.  (Severity: 4)
lib/registration.pm: Using $a or $b outside sort() at line 653, column 65.  $a and $b are special package variables for use in sort() and related functions. Declaring them as lexicals like "my $a" may break sort(). Use different variable names.  (Severity: 4)
lib/registration.pm: Using $a or $b outside sort() at line 653, column 71.  $a and $b are special package variables for use in sort() and related functions. Declaring them as lexicals like "my $a" may break sort(). Use different variable names.  (Severity: 4)
lib/sles4sap.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
lib/caasp.pm source OK
lib/main_common.pm: Using $a or $b outside sort() at line 700, column 12.  $a and $b are special package variables for use in sort() and related functions. Declaring them as lexicals like "my $a" may break sort(). Use different variable names.  (Severity: 4)
lib/main_common.pm: Using $a or $b outside sort() at line 701, column 16.  $a and $b are special package variables for use in sort() and related functions. Declaring them as lexicals like "my $a" may break sort(). Use different variable names.  (Severity: 4)
lib/main_common.pm: Using $a or $b outside sort() at line 701, column 44.  $a and $b are special package variables for use in sort() and related functions. Declaring them as lexicals like "my $a" may break sort(). Use different variable names.  (Severity: 4)
lib/main_common.pm: Using $a or $b outside sort() at line 702, column 17.  $a and $b are special package variables for use in sort() and related functions. Declaring them as lexicals like "my $a" may break sort(). Use different variable names.  (Severity: 4)
lib/main_common.pm: Using $a or $b outside sort() at line 703, column 41.  $a and $b are special package variables for use in sort() and related functions. Declaring them as lexicals like "my $a" may break sort(). Use different variable names.  (Severity: 4)
lib/main_common.pm: Using $a or $b outside sort() at line 703, column 80.  $a and $b are special package variables for use in sort() and related functions. Declaring them as lexicals like "my $a" may break sort(). Use different variable names.  (Severity: 4)
lib/LTP/TestInfo.pm source OK
lib/publiccloud/azure.pm source OK
lib/publiccloud/ec2.pm source OK
lib/publiccloud/gce.pm source OK
lib/publiccloud/basetest.pm: Missing strict or warnings at line 1, column 1.  The strict and warnings pragmas are important to avoid common pitfalls and deprecated/experimental functionality. Make sure each script or module contains "use strict; use warnings;" or a module that does this for you.  (Severity: 4)
lib/publiccloud/instance.pm source OK
lib/publiccloud/provider.pm source OK