Bug 1794424

Summary: [PATCH] Add SPEC support for riscv (riscv64, RISC-V 64-bit)
Product: [Fedora] Fedora Reporter: David Abdurachmanov <david.abdurachmanov>
Component: kernel-headersAssignee: Justin M. Forbes <jforbes>
Status: CLOSED CURRENTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 32CC: jeremy, jforbes, pbrobinson
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-05-06 20:31:14 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1553405    
Attachments:
Description Flags
SPEC changes none

Description David Abdurachmanov 2020-01-23 14:58:21 UTC 
Created attachment 1654860 [details]
SPEC changes

I would like to upstream SPEC file changes from Fedora/RISCV [0]. See attached patch for details. The patch itself is minor and have not changed in a long time in Fedora/RISCV.

[0] https://fedoraproject.org/wiki/Architectures/RISC-V
Comment 1 Ben Cotton 2020-02-11 17:27:23 UTC 
This bug appears to have been reported against 'rawhide' during the Fedora 32 development cycle.
Changing version to 32.
Comment 2 Fedora Program Management 2021-04-29 16:02:43 UTC 
This message is a reminder that Fedora 32 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 32 on 2021-05-25.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '32'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 32 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.
Comment 3 Justin M. Forbes 2021-05-06 20:31:14 UTC 
This was done some time ago.