Bug 1173134 - Incorrect description for csmock shellcheck
Summary: Incorrect description for csmock shellcheck
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: csmock
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kamil Dudka
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-12-11 13:54 UTC by Michael S.
Modified: 2015-02-14 02:53 UTC (History)
1 user (show)

Fixed In Version: cswrap-1.2.1-1.el6
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-02-03 12:02:52 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
Fix for the summary (813 bytes, application/mbox)
2014-12-11 13:54 UTC, Michael S.
no flags Details

Description Michael S. 2014-12-11 13:54:01 UTC
Created attachment 967241 [details]
Fix for the summary

Description of problem:
$ yum search shellcheck
============================================================================================= N/S matched: shellcheck =============================================================================================
csmock-plugin-shellcheck.noarch : csmock plug-in providing the support for Pylint.

The summary is incorrect. Here is a patch.

Comment 1 Kamil Dudka 2014-12-11 14:57:22 UTC
Thanks for the patch!  I have pushed it upstream:

https://git.fedorahosted.org/cgit/csmock.git/commit/?id=cb16525a

... and to Fedora:

http://pkgs.fedoraproject.org/cgit/csmock.git/commit/?id=77947541
http://pkgs.fedoraproject.org/cgit/csmock.git/commit/?id=d6b719cd
http://pkgs.fedoraproject.org/cgit/csmock.git/commit/?id=fd66585d
http://pkgs.fedoraproject.org/cgit/csmock.git/commit/?id=034d9414

To ssh://kdudka.org/csmock
   9c1a4cd..7794754  el6 -> el6
   62e724d..d6b719c  epel7 -> epel7
   62e724d..d6b719c  f19 -> f19
   62e724d..d6b719c  f20 -> f20
   960b52a..fd66585  f21 -> f21
   63c37f4..034d941  master -> master

It is probably not worth submitting an update fixing this bug only.

Comment 2 Fedora Update System 2015-01-27 12:06:23 UTC
cswrap-1.2.1-1.el7, csdiff-1.1.3-1.el7, csmock-1.6.1-1.el7 has been submitted as an update for Fedora EPEL 7.
https://admin.fedoraproject.org/updates/FEDORA-EPEL-2015-0359/cswrap-1.2.1-1.el7,csdiff-1.1.3-1.el7,csmock-1.6.1-1.el7

Comment 3 Fedora Update System 2015-01-27 12:06:29 UTC
cswrap-1.2.1-1.fc21, csdiff-1.1.3-1.fc21, csmock-1.6.1-1.fc21 has been submitted as an update for Fedora 21.
https://admin.fedoraproject.org/updates/FEDORA-2015-0961/cswrap-1.2.1-1.fc21,csdiff-1.1.3-1.fc21,csmock-1.6.1-1.fc21

Comment 4 Fedora Update System 2015-01-27 12:06:37 UTC
cswrap-1.2.1-1.fc20, csdiff-1.1.3-1.fc20, csmock-1.6.1-1.fc20 has been submitted as an update for Fedora 20.
https://admin.fedoraproject.org/updates/FEDORA-2015-0904/cswrap-1.2.1-1.fc20,csdiff-1.1.3-1.fc20,csmock-1.6.1-1.fc20

Comment 5 Fedora Update System 2015-01-27 12:07:20 UTC
cswrap-1.2.1-1.el6, csdiff-1.1.3-1.el6, csmock-1.6.1-1.el6 has been submitted as an update for Fedora EPEL 6.
https://admin.fedoraproject.org/updates/FEDORA-EPEL-2015-0388/cswrap-1.2.1-1.el6,csdiff-1.1.3-1.el6,csmock-1.6.1-1.el6

Comment 6 Fedora Update System 2015-02-03 12:02:52 UTC
cswrap-1.2.1-1.fc21, csdiff-1.1.3-1.fc21, csmock-1.6.1-1.fc21 has been pushed to the Fedora 21 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 7 Fedora Update System 2015-02-03 12:04:24 UTC
cswrap-1.2.1-1.fc20, csdiff-1.1.3-1.fc20, csmock-1.6.1-1.fc20 has been pushed to the Fedora 20 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 8 Fedora Update System 2015-02-14 02:51:39 UTC
cswrap-1.2.1-1.el7, csdiff-1.1.3-1.el7, csmock-1.6.1-1.el7 has been pushed to the Fedora EPEL 7 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 9 Fedora Update System 2015-02-14 02:53:34 UTC
cswrap-1.2.1-1.el6, csdiff-1.1.3-1.el6, csmock-1.6.1-1.el6 has been pushed to the Fedora EPEL 6 stable repository.  If problems still persist, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.