python3 added as a rpm dep, even though it is not a true dep

XMLWordPrintable

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major
    • 4.9.0, 4.8.4
    • Affects Version/s: 4.9.0, 4.8.3
    • Component/s: None
    • None

      It seems like a newly added example
      workflow has a few scripts with #!/usr/bin/python3 and makes rpmbuild
      believe there is a python3 dependency. However, those scripts are only
      used inside a container, so they are false positives (that is, a Pegasus
      install does not currently require python3). A potential fix is to add an exclude in the spec file.

            Assignee:
            Mats Rynge
            Reporter:
            Mats Rynge
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: