Bug 1833324 - Build vcftools to EPEL8
Summary: Build vcftools to EPEL8
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: vcftools
Version: epel8
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Filipe Rosset
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-05-08 12:41 UTC by Jun Aruga
Modified: 2020-07-03 00:25 UTC (History)
2 users (show)

Fixed In Version: vcftools-0.1.16-5.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-07-03 00:25:29 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Jun Aruga 2020-05-08 12:41:13 UTC
Description of problem:

Hi vcftools maintainers. Thank you for maintaining vcftools.
Could you build vcftools to EPEL8?
I can see that there is already the EPEL7 build.


Just in case, I would share how to build on EPEL8.

Request the dist-git branch.

```
$ fedpkg request-branch --repo vcftools epel8
```

Then you will get 2 new branches unlike epel7.

* epel8
* epel8-playground

The epel8-playground branch is to build for the epel8-playground target like an EPEL version of Fedora rawhide. The change is immediately updated without using Bodhi. The epel8 branch is to build for both epel8-playground and epel8 target, or only epel8 target. The epel8 branch has package.cfg file to manage it.

My best practice is to ignore epel8-playground branch, then only use epel8 branch, keeping package.cfg.

Cheers,
Jun

Additional info:
https://hackmd.io/@ssmoogen/B1p2QM-eS
https://fedoraproject.org/wiki/EPEL:Packaging
https://fedoraproject.org/wiki/EPEL/FAQ

Comment 1 Jun Aruga 2020-06-08 20:45:26 UTC
I am requesting the EPEL8 branches.

```
$ fedpkg request-branch --repo vcftools epel8
https://pagure.io/releng/fedora-scm-requests/issue/25644
https://pagure.io/releng/fedora-scm-requests/issue/25645
```

Comment 2 Filipe Rosset 2020-06-08 21:13:01 UTC
(In reply to Jun Aruga from comment #1)
> I am requesting the EPEL8 branches.
> 
> ```
> $ fedpkg request-branch --repo vcftools epel8
> https://pagure.io/releng/fedora-scm-requests/issue/25644
> https://pagure.io/releng/fedora-scm-requests/issue/25645
> ```

great, let me know when the branches are OK I can go ahead and build for EL8.

Comment 3 Jun Aruga 2020-06-15 20:27:51 UTC
> great, let me know when the branches are OK I can go ahead and build for EL8.

Now the epel8 branches were created. Please go a head and build for EL8. Thanks for your work.

Comment 4 Fedora Update System 2020-06-16 23:26:41 UTC
FEDORA-EPEL-2020-08c0eb0069 has been submitted as an update to Fedora EPEL 8. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-08c0eb0069

Comment 5 Fedora Update System 2020-06-18 13:29:30 UTC
FEDORA-EPEL-2020-08c0eb0069 has been pushed to the Fedora EPEL 8 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-08c0eb0069

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

Comment 6 Fedora Update System 2020-06-18 14:11:52 UTC
FEDORA-EPEL-2020-08c0eb0069 has been pushed to the Fedora EPEL 8 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-08c0eb0069

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

Comment 7 Fedora Update System 2020-07-03 00:25:29 UTC
FEDORA-EPEL-2020-08c0eb0069 has been pushed to the Fedora EPEL 8 stable repository.
If problem still persists, 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.