Bug 1822191

Summary:	Review Request: golang-gitlab-flimzy-testy - Go testing utilities
Product:	[Fedora] Fedora	Reporter:	Fabian Affolter <mail>
Component:	Package Review	Assignee:	Robert-André Mauchin 🐧 <eclipseo>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	rawhide	CC:	eclipseo, package-review
Target Milestone:	---	Flags:	eclipseo: fedora-review+
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-07-07 00:59:28 UTC	Type:	---
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:	1801758, 1822187
Bug Blocks:

Description Fabian Affolter 2020-04-08 13:06:33 UTC

Spec URL: https://fab.fedorapeople.org/packages/SRPMS/golang-gitlab-flimzy-testy.spec
SRPM URL: https://fab.fedorapeople.org/packages/SRPMS/golang-gitlab-flimzy-testy-0.1.1-1.fc31.src.rpm

Project URL: https://gitlab.com/flimzy/testy

Description:
Grab-bag of Go testing utilities.

Koji scratch build:
fails due to missing dependency

rpmlint output:
$ rpmlint golang-gitlab-flimzy-testy-0.1.1-1.fc31.src.rpm 
golang-gitlab-flimzy-testy.src: W: no-%build-section
1 packages and 0 specfiles checked; 0 errors, 1 warnings.

$ rpmlint golang-gitlab-flimzy-testy-devel-0.1.1-1.fc31.noarch.rpm 
golang-gitlab-flimzy-testy-devel.noarch: W: hidden-file-or-dir /usr/share/gocode/src/gitlab.com/flimzy/testy/.goipath
1 packages and 0 specfiles checked; 0 errors, 1 warnings.

Fedora Account System Username: fab

Comment 1 Robert-André Mauchin 🐧 2020-06-21 15:53:46 UTC

 - Latest version is 0.2.1 

 - Gitlab is supported by the macros, just use:

# https://gitlab.com/flimzy/testy
%global goipath         gitlab.com/flimzy/testy
Version:                0.2.1
%global tag             v0.2.1

 - License ok
 - Builds in mock
 - No rpmlint errors
 - Conforms to Packaging Guidelines

Package approved. Please bump to the latest version.

Comment 2 Gwyn Ciesla 2020-06-24 13:54:38 UTC

(fedscm-admin):  The Pagure repository was created at https://src.fedoraproject.org/rpms/golang-gitlab-flimzy-testy

Comment 3 Fedora Update System 2020-06-28 16:35:20 UTC

FEDORA-2020-73218a1a2c has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2020-73218a1a2c

Comment 4 Fedora Update System 2020-06-28 16:54:22 UTC

FEDORA-2020-efe62f63db has been submitted as an update to Fedora 31. https://bodhi.fedoraproject.org/updates/FEDORA-2020-efe62f63db

Comment 5 Fedora Update System 2020-06-29 01:18:54 UTC

FEDORA-2020-efe62f63db has been pushed to the Fedora 31 testing repository.
In short time you'll be able to install the update with the following command:
`sudo dnf install --enablerepo=updates-testing --advisory=FEDORA-2020-efe62f63db \*`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-efe62f63db

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 6 Fedora Update System 2020-06-29 01:27:08 UTC

FEDORA-2020-73218a1a2c has been pushed to the Fedora 32 testing repository.
In short time you'll be able to install the update with the following command:
`sudo dnf install --enablerepo=updates-testing --advisory=FEDORA-2020-73218a1a2c \*`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-73218a1a2c

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 7 Fedora Update System 2020-07-07 00:59:28 UTC

FEDORA-2020-efe62f63db has been pushed to the Fedora 31 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 8 Fedora Update System 2020-07-07 01:05:47 UTC

FEDORA-2020-73218a1a2c has been pushed to the Fedora 32 stable repository.
If problem still persists, please make note of it in this bug report.