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

generate prescriptions for packages packaged as RPMs in Fedora 35 #168

Closed
3 tasks
mayaCostantini opened this issue Jun 13, 2022 · 5 comments
Closed
3 tasks
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. sig/stack-guidance Categorizes an issue or PR as relevant to SIG Stack Guidance.

Comments

@mayaCostantini
Copy link
Contributor

mayaCostantini commented Jun 13, 2022

See thoth-station/thoth-application#1803 (comment) and this issue should state code on how to do that thoth-station/adviser#1961 (might require changes to conform to the current prescriptions structure and thoth-station/prescriptions#59).

Acceptance criteria

  • Investigate the process of generating this prescription for RPMs
  • Document the missing bits.
  • write a handle based on the investigation.

Additional context:

  • knowledge of RPMs, fedora core.

Originally posted by @fridex in thoth-station/s2i-thoth#231 (comment)

@mayaCostantini mayaCostantini changed the title generate prescriptions for packages packaged as RPMs in Fedora 35 (also might be worth to document this). See https://github.com/thoth-station/thoth-application/issues/1803#issuecomment-878208947 and this issue should state code on how to do that https://github.com/thoth-station/adviser/issues/1961 (might require changes to conform to the current prescriptions structure and https://github.com/thoth-station/prescriptions/issues/59). generate prescriptions for packages packaged as RPMs in Fedora 35 Jun 13, 2022
@mayaCostantini
Copy link
Contributor Author

/sig stack-guidance
/priority important-soon

@sesheta sesheta added sig/stack-guidance Categorizes an issue or PR as relevant to SIG Stack Guidance. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. labels Jun 14, 2022
@mayaCostantini
Copy link
Contributor Author

See thoth-station/adviser#1961 (comment) for the code which was used in the first place to aggregate data about packages packaged as RPMs.

Would it be worth implementing a more generic handler to inform users about the availability of those RPM packages for different distributions? It was specified in the comment above that this would depend on the outcome of thoth-station/thoth-application#1798, has anything been decided yet?

@mayaCostantini
Copy link
Contributor Author

/kind feature

@sesheta sesheta added the kind/feature Categorizes issue or PR as related to a new feature. label Jun 27, 2022
@codificat codificat moved this to 📋 Backlog in Planning Board Sep 24, 2022
@sesheta
Copy link
Member

sesheta commented Sep 25, 2022

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@sesheta sesheta added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Sep 25, 2022
@mayaCostantini
Copy link
Contributor Author

Closing this issue as this feature will likely not be implemented.

Repository owner moved this from 📋 Backlog to ✅ Done in Planning Board Sep 25, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. sig/stack-guidance Categorizes an issue or PR as relevant to SIG Stack Guidance.
Projects
Status: Done
Development

No branches or pull requests

2 participants