Bug 1476525

Summary: vst-amsynth-plugin summary typo
Product: [Fedora] Fedora Reporter: Martin Tarenskeen <m.tarenskeen>
Component: amsynthAssignee: Alexandre Moine <nobrakal>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: low Docs Contact:
Priority: unspecified    
Version: 26CC: m.tarenskeen, nobrakal
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: amsynth-1.8.0-2.fc26 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-08-10 16:53:43 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:

Description Martin Tarenskeen 2017-07-29 22:12:29 UTC 
Description of problem:
vst-amsynth-plugin is described as "Amsynth lv2 plugin" in Summary

Version-Release number of selected component (if applicable):
1.8.0-1.fc26.*.rpm

How reproducible:
Always

Steps to Reproduce:
(after installing vst-amsynth-plugin)
$ rpm -qi vst-amsynth-plugin | grep Summary

or:
$ dnf search vst-amsynth-plugin
  
Actual results:
> Summary     : Amsynth lv2 plugin

Expected results:
> Summary     : Amsynth vst plugin

Additional info:
It's just a simple typo in the specfile :-)
Comment 1 Alexandre Moine 2017-08-01 20:18:56 UTC 
Hi,

Thank you for the report :)
I just send an update that will fix it.
Comment 2 Fedora Update System 2017-08-03 00:52:48 UTC 
amsynth-1.8.0-2.fc26 has been pushed to the Fedora 26 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-87778715de
Comment 3 Fedora Update System 2017-08-10 16:53:43 UTC 
amsynth-1.8.0-2.fc26 has been pushed to the Fedora 26 stable repository. If problems still persist, please make note of it in this bug report.