From Fedora Project Wiki
< Changes
(→Scope) |
|||
| (3 intermediate revisions by 2 users not shown) | |||
| Line 22: | Line 22: | ||
== Current status == | == Current status == | ||
[[Category: | [[Category:ChangeAnnounced]] | ||
<!-- When your change proposal page is completed and ready for review and announcement --> | <!-- When your change proposal page is completed and ready for review and announcement --> | ||
<!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler --> | <!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler --> | ||
| Line 40: | Line 40: | ||
ON_QA -> change is fully code complete | ON_QA -> change is fully code complete | ||
--> | --> | ||
* [Announced] | * [https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org/thread/L5KQWEMARAUK6LSOY6GOAOO3C3UAOEWW/ Announced] | ||
* [ | * [https://discussion.fedoraproject.org/t/f41-change-proposal-fedora-repoquery-tool-self-contained/126066 Discussion thread] | ||
* FESCo issue: <will be assigned by the Wrangler> | * FESCo issue: <will be assigned by the Wrangler> | ||
* Tracker bug: <will be assigned by the Wrangler> | * Tracker bug: <will be assigned by the Wrangler> | ||
| Line 47: | Line 47: | ||
== Detailed Description == | == Detailed Description == | ||
fedora-repoquery | fedora-repoquery has been in development for a while, and with the 0.7 release now | ||
should be polished enough now to be included in Fedora for broader usage. | should be polished enough now to be included in Fedora for broader usage. | ||
See the [https://github.com/juhp/fedora-repoquery#readme readme] file for usage examples. | See the [https://github.com/juhp/fedora-repoquery#readme readme] file for usage examples. | ||
== Feedback == | |||
A [https://copr.fedorainfracloud.org/coprs/petersen/fedora-repoquery/ copr] repo has been available for some time. | |||
I am aware of fedrq which is somewhat similar to fedora-repoquery, but has a different design and emphasis. | I am aware of fedrq which is somewhat similar to fedora-repoquery, but has a different design and emphasis. | ||
The biggest difference being that fedora-repoquery | The biggest difference being that fedora-repoquery uses conventional repoquery options and can show repo timestamps, | ||
and also tells you by default in which specific repo a partcular package lives. | and also tells you by default in which specific repo a partcular package lives. | ||
<!-- Summarize the feedback from the community and address why you chose not to accept proposed alternatives. This section is optional for all change proposals but is strongly suggested. Incorporating feedback here as it is raised gives FESCo a clearer view of your proposal and leaves a good record for the future. If you get no feedback, that is useful to note in this section as well. For innovative or possibly controversial ideas, consider collecting feedback before you file the change proposal. --> | <!-- Summarize the feedback from the community and address why you chose not to accept proposed alternatives. This section is optional for all change proposals but is strongly suggested. Incorporating feedback here as it is raised gives FESCo a clearer view of your proposal and leaves a good record for the future. If you get no feedback, that is useful to note in this section as well. For innovative or possibly controversial ideas, consider collecting feedback before you file the change proposal. --> | ||
| Line 64: | Line 65: | ||
== Scope == | == Scope == | ||
* Proposal owners: | * Proposal owners: | ||
** get package review approved ([https://bugzilla.redhat.com/show_bug.cgi?id=2295191 bugzilla review]) | ** get package review approved ([https://bugzilla.redhat.com/show_bug.cgi?id=2295191 bugzilla review]) [done] | ||
** build package for Rawhide and current releases | ** build package for Rawhide and current releases [done] | ||
** fix any bugs or issues reported by community | ** fix any bugs or issues reported by community | ||
<!-- What work do the feature owners have to accomplish to complete the feature in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?--> | <!-- What work do the feature owners have to accomplish to complete the feature in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?--> | ||
| Line 97: | Line 98: | ||
* sudo dnf install fedora-repoquery | * sudo dnf install fedora-repoquery | ||
* fedora-repoquery --help | * fedora-repoquery --help | ||
* | * fedora-repoquery 41 podman | ||
<!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
Latest revision as of 09:41, 21 July 2024
fedora-repoquery tool
This is a proposed Change for Fedora Linux.
This document represents a proposed Change. As part of the Changes process, proposals are publicly announced in order to receive community feedback. This proposal will only be implemented if approved by the Fedora Engineering Steering Committee.
This document represents a proposed Change. As part of the Changes process, proposals are publicly announced in order to receive community feedback. This proposal will only be implemented if approved by the Fedora Engineering Steering Committee.
Summary
fedora-repoquery is a small commandline tool for doing repoqueries of Fedora, EPEL, eln, and Centos Stream package repositories. It wraps dnf repoquery separating the cached repo data under separate repo names for faster cached querying. Repoqueries are frequently used by Fedora developers and users, so a more powerful tool like this is generally useful.
Owner
- Name: Jens Petersen
- Email: <petersen@redhat.com>
Current status
- Targeted release: Fedora Linux 41
- Last updated: 2024-07-21
- Announced
- Discussion thread
- FESCo issue: <will be assigned by the Wrangler>
- Tracker bug: <will be assigned by the Wrangler>
- Release notes tracker: <will be assigned by the Wrangler>
Detailed Description
fedora-repoquery has been in development for a while, and with the 0.7 release now should be polished enough now to be included in Fedora for broader usage. See the readme file for usage examples.
Feedback
A copr repo has been available for some time.
I am aware of fedrq which is somewhat similar to fedora-repoquery, but has a different design and emphasis. The biggest difference being that fedora-repoquery uses conventional repoquery options and can show repo timestamps, and also tells you by default in which specific repo a partcular package lives.
Benefit to Fedora
fedora-repoquery is a useful tool for users and developers to query different Fedora, EPEL and Centos Stream versions.
Scope
- Proposal owners:
- get package review approved (bugzilla review) [done]
- build package for Rawhide and current releases [done]
- fix any bugs or issues reported by community
- Other developers:
- Release engineering: #Releng issue number
- Policies and guidelines: N/A (not needed for this Change)
- Trademark approval: N/A (not needed for this Change)
- Alignment with the Fedora Strategy:
Upgrade/compatibility impact
Early Testing (Optional)
https://copr.fedorainfracloud.org/coprs/petersen/fedora-repoquery/
How To Test
- sudo dnf install fedora-repoquery
- fedora-repoquery --help
- fedora-repoquery 41 podman
User Experience
Users will have the benefit of a flexible repoquery tool with which they can check versions of packages etc in different release versions of Fedora, EPEL, Centos Stream, and eln.
Dependencies
Contingency Plan
- Contingency mechanism: (What to do? Who will do it?) N/A (not a System Wide Change)
- Contingency deadline: N/A (not a System Wide Change)
- Blocks release? N/A (not a System Wide Change), Yes/No
Documentation
https://github.com/juhp/fedora-repoquery#readme