Bug 1972910

Summary:	Please branch and build nextcloud-client for epel8-next
Product:	[Fedora] Fedora EPEL	Reporter:	Michel Lind <michel>
Component:	nextcloud-client	Assignee:	Germano Massullo (Thetra) <germano.massullo>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	epel8	CC:	carl, claudiorodrigo, comzeradd, germano.massullo, gwync, jan.public, mailinglists, nb, nonamedotc, pasik, taaem
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	nextcloud-client-3.2.0-1.el8.next	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-07-01 01:33: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:	1914423

Description Michel Lind 2021-06-16 20:37:48 UTC

Description of problem:
EPEL8-Next trackes CentOS Stream (which will become the next RHEL/CentOS), and Stream has a newer version of Qt.

Qt-using packages (including nextcloud-client) will thus need to be rebuilt; please branch and build per the FAQ. The dependencies should be ready (they are in build overrides right now)

Alternatively, could you add me to the ACL so I can build nextcloud-client once its dependencies are ready?
https://src.fedoraproject.org/rpms/nextcloud-client/settings#usersgroups-tab

FAS: salimma

Committer access is enough, or collaborator access on epel* branches. But I'm also happy to comaintain as a package admin; I use Nextcloud heavily on Fedora too.

If I'm getting only committer or collaborator access, please also add the epel-packagers-sig group as collaborator on epel*

References:
https://fedoraproject.org/wiki/EPEL_Next#FAQ
https://fedoraproject.org/wiki/EPEL/Packagers

Comment 1 Germano Massullo (Thetra) 2021-06-16 21:20:24 UTC

Added as commit access.
Please keep in mind that we have one single spec file that fits all branches, thanks to macros usage. So you should commit everything in master and then merge to other branches
Requested repo: https://pagure.io/releng/fedora-scm-requests/issue/34729
Why epel-packagers-sig group is needed as collaborator on epel*? How this should be enabled?

Comment 2 Michel Lind 2021-06-29 16:15:51 UTC

(In reply to Germano Massullo from comment #1)
> Added as commit access.
> Please keep in mind that we have one single spec file that fits all
> branches, thanks to macros usage. So you should commit everything in master
> and then merge to other branches
> Requested repo: https://pagure.io/releng/fedora-scm-requests/issue/34729
> Why epel-packagers-sig group is needed as collaborator on epel*? How this
> should be enabled?

Sorry, somehow this bug did not end up on the epel tracker and I did not notice the follow-up.

epel-packagers-sig is an initiative by the EPEL SIG to make it easier to maintain packages in EPEL - it's similar to how a lot of Python packages are comaintained by the Python SIG.

You can just add epel-packagers-sig to the ACL (use group, not user). The reason for making it a collaborator rather than a committer is to limit the access of SIG members to branches starting with epel* -- in case primary maintainers prefer that SIG members don't have access to the Fedora branches. Otherwise, adding the epel-packagers-sig group as a committer also works.

Comment 3 Fedora Update System 2021-06-29 17:06:13 UTC

FEDORA-EPEL-NEXT-2021-cf83059c94 has been submitted as an update to Fedora EPEL 8 Next. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-NEXT-2021-cf83059c94

Comment 4 Fedora Update System 2021-06-30 04:30:31 UTC

FEDORA-EPEL-NEXT-2021-cf83059c94 has been pushed to the Fedora EPEL 8 Next testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-NEXT-2021-cf83059c94

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

Comment 5 Fedora Update System 2021-07-01 01:33:14 UTC

FEDORA-EPEL-NEXT-2021-cf83059c94 has been pushed to the Fedora EPEL 8 Next stable repository.
If problem still persists, please make note of it in this bug report.