| Summary: | gh (github-cli) - The CLI for GitHub; NEW PKG REQUEST | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Kristoffer Grundström <lovaren> |
| Component: | New RPM package request | Assignee: | All Packagers <pkg-bugs> |
| Status: | NEW --- | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | Normal | CC: | davidwhodgins, fri, lovaren |
| Version: | Cauldron | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | gh | CVE: | |
| Status comment: | |||
| Attachments: |
Proposal spec file
New proposal spec file |
||
|
Description
Kristoffer Grundström
2022-09-26 20:39:54 CEST
Latest version of it is 2.16.1, but it needs to have an update in our spec file to either ignore the vendor archive or to use mod=mod I think. Feel free to push an update for it once it's fixed. If anyone does import this, please give the package a real name. gh will be impossible to search in bugzilla. (In reply to David Walser from comment #3) > If anyone does import this, please give the package a real name. gh will be > impossible to search in bugzilla. github-cli ? https://groups.google.com/g/linux.debian.bugs.dist/c/G9kHRwVAz6Q Both the package and the command should be renamed. github-cli seems to be the best option. CC:
(none) =>
davidwhodgins Yeah, that would be good. I'm familiar with gh from having seen it in Fedora's updates-announce, as they have it packaged. It has had a few security updates already. We should probably have an official policy against two letter package names, honestly. It makes it impossible to track for security issues. We already had a package named rt, which should have been named request-tracker, that I dropped because it had been missing security updates for years, because the rt name made it impossible to track or have any visibility into. The package could still have "Provides: gh" so that "urpmi gh" would still work. Thank you Kristoffer for this suggestion. Usual plug: "Assigning this package request to all packagers collectively. On a voluntary basis, one of them might, if there are no license or other legal issues, want to integrate it to the distribution and maintain it for bug and security fixes. You Kristoffer might also want to join the packager team to maintain this piece of software: see https://wiki.mageia.org/en/Becoming_a_Mageia_Packager" Assignee:
bugsquad =>
pkg-bugs Ping! Can this be released before the stable release of 9 or does it have to wait until Cauldron is once again reopened/unfrozen? I believe new packages can be introduced in a released Mageia version in the updates repositories. Like pending nvidia-newfeature. CC:
(none) =>
fri The updates policy is available at https://wiki.mageia.org/en/Updates_policy For new packages, which are an exception to the rules, they are allowed when they are required for a security or bug fix update for an existing package, or it's required to support new hardware. |