Bug 1743186
| Summary: | Rebase createrepo_c to at least 0.14 | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 8 | Reporter: | Tomas Kopecek <tkopecek> | 
| Component: | createrepo_c | Assignee: | amatej | 
| Status: | CLOSED ERRATA | QA Contact: | Radek Bíba <rbiba> | 
| Severity: | unspecified | Docs Contact: | Katerina Nemcova <knemcova> | 
| Priority: | high | ||
| Version: | 8.2 | CC: | jblazek, knemcova, mdomonko, rbiba | 
| Target Milestone: | rc | Keywords: | Rebase, Triaged | 
| Target Release: | 8.0 | Flags: | pm-rhel:
                mirror+ | 
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | createrepo_c-0.15.1-1.el8 | Doc Type: | Enhancement | 
| Doc Text: | .The  `createrepo_c` utility now skips packages whose metadata contains the disallowed control characters
To ensure a valid XML, the package metadata must not contain any control characters, with the exception of:
* the horizontal tab
* the newline character
* the carriage return character
With this update, the `createrepo_c` utility does not include packages with metadata containing disallowed control characters in a newly created repository, and returns the following error message:
----
C_CREATEREPOLIB: Critical: Cannot dump XML for PACKAGE_NAME (PACKAGE_SUM): Forbidden control chars found (ASCII values <32 except 9, 10 and 13)
---- | Story Points: | --- | 
| Clone Of: | Environment: | ||
| Last Closed: | 2020-04-28 15:39:34 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: | |||
| Bug Depends On: | |||
| Bug Blocks: | 1755139 | ||
| 
        
          Description
        
        
          Tomas Kopecek
        
        
        
        
        
          2019-08-19 09:42:56 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-2020:1620 |