Bug 995396 - rpmlint ignors NetworkEnabled option if not verbose
rpmlint ignors NetworkEnabled option if not verbose
Status: NEW
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: rpmlint (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: rc
: ---
Assigned To: Thomas Woerner
BaseOS QE Security Team
Depends On:
  Show dependency treegraph
Reported: 2013-08-09 05:15 EDT by Fredrik Axelsson
Modified: 2017-09-14 08:09 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Fredrik Axelsson 2013-08-09 05:15:33 EDT
Description of problem:
Setting the option NetworkEnabled to False is ignored if -v (verbose) is not also set.

Version-Release number of selected component (if applicable):
rpmlint version 0.94

How reproducible:

Steps to Reproduce:
1. service network stop
2. rpmlint -o "NetworkEnabled False" some_package.rpm

Actual results:
Warning about invalid-url even though NetworkEnabled is set to False:

some_package.x86_64: W: invalid-url URL: http://example.com ...

Expected results:
No warning about invalid url.

Additional info:
Think bug is in /usr/share/rpmlint/AbstractCheck.py
The method AbstractCheck.check_url only checks for self.network_enabled if self.verbose is set.
Comment 2 RHEL Product and Program Management 2013-10-13 19:16:52 EDT
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unable to address this
request at this time.

Red Hat invites you to ask your support representative to
propose this request, if appropriate, in the next release of
Red Hat Enterprise Linux.

Note You need to log in before you can comment on or make changes to this bug.