Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

TASK: diagnose UNKNOWN packages in DBS #136

Closed
yselkowitz opened this issue Jun 15, 2023 · 1 comment
Closed

TASK: diagnose UNKNOWN packages in DBS #136

yselkowitz opened this issue Jun 15, 2023 · 1 comment
Assignees

Comments

@yselkowitz
Copy link
Collaborator

What does the ELN SIG need to do?

DBS currently lists some packages as UNKNOWN, iow neither eln or eln-extras. So far, it seems most of these packages fall into a few categories:

  • Placeholders (as defined in CR-input)
  • Packages with different SRPM names in Fedora and ELN (e.g. freeipa/ipa)
  • Packages which failed to buildSRPMfromSCM for RHEL/EPEL/ELN (e.g. kasumi prior to being fixed)

However, there are a few packages (e.g. catch2, gengetopt, unifdef) which do not fall into any of these categories, and their reason for being so listed is unclear. The one common theme so far is that they were never (successfully) built by DBS; the only ELN builds listed in koji were done manually.

We should go through all the "unknown" packages, make sure there aren't any other kasumi-like cases, understand why each is so listed, and try to see if there is a better way of categorizing them.

@yselkowitz
Copy link
Collaborator Author

Currently, all UNKNOWN packages fall into the first two categories above.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants