Bug 1691279

Summary: perl-DBD-SQLite is missing LICENSE file [perl:5.24 perl:5.26]
Product: Red Hat Enterprise Linux 8 Reporter: Jitka Plesnikova <jplesnik>
Component: perl-DBD-SQLiteAssignee: Martin Kyral <mkyral>
Status: CLOSED ERRATA QA Contact: RHEL CS Apps Subsystem QE <rhel-cs-apps-subsystem-qe>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 8.0CC: bnater, jorton, jplesnik, mkyral, perl-maint-list, ppisar, qe-baseos-daemons, tcallawa
Target Milestone: rcKeywords: EasyFix
Target Release: 8.1   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: perl-DBD-SQLite-1.58-2.module+el8.1.0+2940+55ca6856 perl-DBD-SQLite-1.58-2.module+el8.1.0+2940+f62455ee Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: 1691243 Environment:
Last Closed: 2019-11-05 20:44:41 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Jitka Plesnikova 2019-03-21 10:22:19 UTC 
+++ This bug was initially created as a clone of Bug #1691243 +++

Description of problem:
README of the package in question reads:

COPYRIGHT
    The bundled SQLite code in this distribution is Public Domain.
...

    This program is free software; you can redistribute it and/or modify it
    under the same terms as Perl itself.

    The full text of the license can be found in the LICENSE file included
    with this module.

However, there is no such file shipped with the package:

# rpm -ql perl-DBD-SQLite | grep LIC
#

Version-Release number of selected component (if applicable):
perl-DBD-SQLite-1.58-1*

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

--- Additional comment from Jitka Plesnikova on 2019-03-21 10:20:20 UTC ---

It will be fixed by adding '%license LICENSE' into %files section in spec.
Comment 6 errata-xmlrpc 2019-11-05 20:44:41 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2019:3337