Bug 790963 - repoclosure return code ambiguities
Summary: repoclosure return code ambiguities
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: yum-utils
Version: 6.2
Hardware: All
OS: Linux
low
low
Target Milestone: rc
: ---
Assignee: Valentina Mukhamedzhanova
QA Contact: BaseOS QE Security Team
URL:
Whiteboard:
Depends On:
Blocks: 1499211
TreeView+ depends on / blocked
 
Reported: 2012-02-15 20:03 UTC by jcpunk
Modified: 2017-12-06 10:29 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-12-06 10:29:07 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description jcpunk 2012-02-15 20:03:42 UTC
Description of problem: It is difficult to, in an automated fashion, determine if a repository contains all the necessary dependencies.  Repoclosure returns 0 if it was able to parse the repository - even if the repository is missing dependencies.


Version-Release number of selected component (if applicable):yum-utils-1.1.30-6.el6


How reproducible: always


Steps to Reproduce:
1. make a repo with missing dependencies
2. run repoclosure
3. echo $?
4. make a repo containing no missing dependencies
5. run repoclosure
6. echo $?
  
Actual results:
$? is 0 both times


Expected results:
The value of $? should not be the same as the whole purpose of repoclosure is to locate missing dependencies.

Additional info:

Comment 2 RHEL Program Management 2012-07-10 06:02:26 UTC
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.

Comment 3 RHEL Program Management 2012-07-11 02:12:13 UTC
This request was erroneously removed from consideration in Red Hat Enterprise Linux 6.4, which is currently under development.  This request will be evaluated for inclusion in Red Hat Enterprise Linux 6.4.

Comment 4 RHEL Program Management 2012-09-07 05:14:59 UTC
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.

Comment 5 Zdeněk Pavlas 2013-04-19 10:26:53 UTC
commit 79ec81e2221d7d22f969758c3813811c6a7b7f2a
Author: Zdenek Pavlas <zpavlas>
Date:   Fri Apr 19 12:24:18 2013 +0200

    exit(1) on unresolved deps.  BZ 790963

diff --git a/repoclosure.py b/repoclosure.py
index e5aae1b..e33aafa 100755
--- a/repoclosure.py
+++ b/repoclosure.py
@@ -298,6 +298,8 @@ def main():
                 req = '%s %s' % (req, v)
             
             my.logger.info('     %s' % req)
+    if baddeps:
+        sys.exit(1)
 
 if __name__ == "__main__":
     try:

Comment 8 RHEL Program Management 2013-10-14 00:48:01 UTC
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.

Comment 12 Jan Kurik 2017-12-06 10:29:07 UTC
Red Hat Enterprise Linux 6 is in the Production 3 Phase. During the Production 3 Phase, Critical impact Security Advisories (RHSAs) and selected Urgent Priority Bug Fix Advisories (RHBAs) may be released as they become available.

The official life cycle policy can be reviewed here:

http://redhat.com/rhel/lifecycle

This issue does not meet the inclusion criteria for the Production 3 Phase and will be marked as CLOSED/WONTFIX. If this remains a critical requirement, please contact Red Hat Customer Support to request a re-evaluation of the issue, citing a clear business justification. Note that a strong business justification will be required for re-evaluation. Red Hat Customer Support can be contacted via the Red Hat Customer Portal at the following URL:

https://access.redhat.com/


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