Bug 1556915 - Review Request: golang-github-nightlyone-lockfile - Handle locking via pid files
Summary: Review Request: golang-github-nightlyone-lockfile - Handle locking via pid files
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: Package Review
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Jakub Čajka
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-03-15 14:12 UTC by Jan Chaloupka
Modified: 2018-03-25 21:49 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-03-25 21:49:04 UTC
Type: ---
Embargoed:
jcajka: fedora-review+


Attachments (Terms of Use)

Description Jan Chaloupka 2018-03-15 14:12:42 UTC
Spec URL: https://jchaloup.fedorapeople.org/reviews/golang-github-nightlyone-lockfile/golang-github-nightlyone-lockfile.spec

SRPM URL: https://jchaloup.fedorapeople.org/reviews/golang-github-nightlyone-lockfile/golang-github-nightlyone-lockfile-0-0.1.20180315gite83dc5e.fc24.src.rpm

Description: Handle locking via pid files

Fedora Account System Username: jchaloup

Koji: http://koji.fedoraproject.org/koji/taskinfo?taskID=25725535

$ rpmlint golang-github-nightlyone-lockfile-0-0.1.20180315gite83dc5e.fc24.src.rpm golang-github-nightlyone-lockfile-devel-0-0.1.20180315gite83dc5e.fc24.noarch.rpm
golang-github-nightlyone-lockfile.src: W: spelling-error Summary(en_US) pid -> peed, dip, pud
golang-github-nightlyone-lockfile.src: W: spelling-error %description -l en_US pid -> peed, dip, pud
golang-github-nightlyone-lockfile.src: W: no-%build-section
golang-github-nightlyone-lockfile-devel.noarch: W: spelling-error Summary(en_US) pid -> peed, dip, pud
golang-github-nightlyone-lockfile-devel.noarch: W: spelling-error %description -l en_US pid -> peed, dip, pud
golang-github-nightlyone-lockfile-devel.noarch: W: hidden-file-or-dir /usr/share/gocode/src/github.com/nightlyone/lockfile/.goipath
golang-github-nightlyone-lockfile-devel.noarch: E: zero-length /usr/share/gocode/src/github.com/nightlyone/lockfile/.goipath
2 packages and 0 specfiles checked; 1 errors, 6 warnings.

Comment 1 Jakub Čajka 2018-03-16 12:37:30 UTC
LGTM

Comment 2 Gwyn Ciesla 2018-03-16 13:08:03 UTC
(fedrepo-req-admin):  The Pagure repository was created at https://src.fedoraproject.org/rpms/golang-github-nightlyone-lockfile

Comment 3 Fedora Update System 2018-03-16 23:25:31 UTC
golang-github-nightlyone-lockfile-0-0.1.20180316gite83dc5e.fc27 has been submitted as an update to Fedora 27. https://bodhi.fedoraproject.org/updates/FEDORA-2018-78d49a4344

Comment 4 Fedora Update System 2018-03-16 23:25:39 UTC
golang-github-nightlyone-lockfile-0-0.1.20180316gite83dc5e.fc28 has been submitted as an update to Fedora 28. https://bodhi.fedoraproject.org/updates/FEDORA-2018-328d594b2d

Comment 5 Fedora Update System 2018-03-17 19:30:24 UTC
golang-github-nightlyone-lockfile-0-0.1.20180316gite83dc5e.fc28 has been pushed to the Fedora 28 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-2018-328d594b2d

Comment 6 Fedora Update System 2018-03-17 20:39:06 UTC
golang-github-nightlyone-lockfile-0-0.1.20180316gite83dc5e.fc27 has been pushed to the Fedora 27 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-2018-78d49a4344

Comment 7 Fedora Update System 2018-03-25 21:49:04 UTC
golang-github-nightlyone-lockfile-0-0.1.20180316gite83dc5e.fc27 has been pushed to the Fedora 27 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.