Bug 1595541

Summary: Remove libvncserver package from EPEL 7
Product: [Fedora] Fedora EPEL Reporter: Petr Pisar <ppisar>
Component: libvncserverAssignee: Rex Dieter <rdieter>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: epel7CC: negativo17, rdieter
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-07-06 07:35:15 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 Petr Pisar 2018-06-27 05:56:04 UTC
Red Hat Enterprise Linux 7 delivers libvcnserver package. Because of that EPEL 7 cannot deliver the same package <https://fedoraproject.org/wiki/EPEL/GuidelinesAndPolicies#Policy>. Please remove libvncserver package from EPEL 7 repository.

Comment 2 Simone Caronni 2018-07-03 08:56:55 UTC
Please revert the change, this is a limited arch package for ppc64. I will update it to the current base that is in RHEL:

libvncserver-0.9.9-11.el7.src.rpm --> libvncserver-0.9.9-0.11.el7.src.rpm

Comment 3 Petr Pisar 2018-07-03 09:12:16 UTC
Then change EPEL build in the way (ExcludeArch: x86_64, ppc64le) that it does not overlap with architectures supported by RHEL.

Comment 4 Simone Caronni 2018-07-03 09:23:26 UTC
This is not overlapping at all, that's why the package guidelines state to prepend the release with a "0.". The official package will always win:

https://fedoraproject.org/wiki/EPEL:Packaging#Limited_Arch_Packages

Comment 5 Simone Caronni 2018-07-03 09:24:03 UTC
Excerpt:

"Change the release of the package to have a leading 0. EXAMPLE: RHEL has foobar-1.0-1, you change it to foobar-1.0-0.1 for EPEL.

Add a Changelog entry that the package was added to EPEL and has a 0 leading version to keep it older than RHEL."

Comment 6 Simone Caronni 2018-07-03 09:24:42 UTC
So this is exactly the state it was (it was just missing an update to 0.9.9-11 (0.9.9-0.11).

Comment 7 Simone Caronni 2018-07-03 09:59:50 UTC
Well, actually with the recent updates is:

libvncserver-0.9.9-12.el7_5.src.rpm --> libvncserver-0.9.9-0.12.el7_5.src.rpm

Comment 8 Simone Caronni 2018-07-03 10:06:52 UTC
I updated it but it's blocked in Koji:

https://koji.fedoraproject.org/koji/taskinfo?taskID=27998743

"BuildError: package libvncserver is blocked for tag epel7-testing-candidate"

Sorry for the double spam, I'm updating both the releng ticket and this bug; don't know which one I should update.

Comment 9 Rex Dieter 2018-07-03 13:23:04 UTC
Sorry about the confusion, can you please add a .spec comment near the top somewhere for posterity?

Comment 10 Simone Caronni 2018-07-03 14:39:21 UTC
Sure, absolutely, actually it was written in the changelog, but I will make it clear at the top.

Can you update / close the relevant releng ticket and unblock koji?

https://pagure.io/releng/issue/7605

Comment 11 Simone Caronni 2018-07-06 07:35:15 UTC
Block removed, rebuilding and pushing the libvncserver update for ppc64. Thanks.