Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1738533

Summary: rpm -V failed for /etc/cups/cups-browsed.conf
Product: Red Hat Enterprise Linux 8 Reporter: Tomas Pelka <tpelka>
Component: cups-filtersAssignee: Zdenek Dohnal <zdohnal>
Status: CLOSED ERRATA QA Contact: Petr Sklenar <psklenar>
Severity: medium Docs Contact:
Priority: medium    
Version: 8.1CC: psklenar, thozza
Target Milestone: rcFlags: pm-rhel: mirror+
Target Release: 8.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-11-05 20:59:18 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 Tomas Pelka 2019-08-07 11:48:27 UTC
Description of problem:
I'm not really sure how important this is but TPS verification test (rpm -V) shows issue with /etc/cups/cups-browsed.conf

cups-filters.aarch64: /etc/cups/cups-browsed.conf S.5....T. c [tps:B]

TPS verify test analysis tags:
  tps:a -- verify errors on both arches
  tps:b -- verify error on file not present in alternative arch
  tps:c -- verify error on preferred binary/ELF file
  tps:d -- significant type of verify error


Version-Release number of selected component (if applicable):
cups-filters-1.20.0-16.el8

How reproducible:
100%

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
I can see it on all arches. Seems like not a new failure (can see it in -14.el8_0.1 version too) but could be bogus too.

Comment 1 Zdenek Dohnal 2019-08-07 13:41:31 UTC
Hi Tomas,

thank you for reporting the issue! 

Actually it is like that because of %post scriptlet, which works with cups-browsed.conf after installation. It adds info about cups-browsed not being part of CUPS and possibly moving 'BrowsePoll' directive from cupsd.conf to cups-browsed.conf.

The scriptlet main purpose was el6->el7 migration, but it is harmless in rhel8 (probably it helps if someone upgrades from el6 -> el8, but that's unsupported).

I can remove that scriptlet when cups-filters will get update in RHEL 8, if it breaks testing and causes troubles (cups-filters has errata for 8.1).

Is it okay, Petr?

And I'll fix it in Fedora too.

Comment 2 Petr Sklenar 2019-08-07 13:47:27 UTC
lets remove it as el6>el8 is not supported.

Comment 9 errata-xmlrpc 2019-11-05 20:59:18 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:3393