Bug 2025889

Summary: Please branch and build backintime in epel8, epel9
Product: [Fedora] Fedora EPEL Reporter: Mark E. Fuller <mark.e.fuller>
Component: backintimeAssignee: Raphael Groner <projects.rg>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: epel8CC: carl, johannes.lips, projects.rg, rosset.filipe
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: backintime-1.3.1-3.el8 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-12-02 01:39:12 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 Mark E. Fuller 2021-11-23 10:04:07 UTC
Please branch and build backintime in epel8.
Build has been tested on COPR: https://copr.fedorainfracloud.org/coprs/fuller/backintime/

Comment 1 hannes 2021-11-23 12:27:34 UTC
Hi, 
thanks for the report and also for the mail. The issue is that I am not using any EPEL distro and thus are not able to test anything. Of course I would be more than happy if someone else would like to maintain it in EPEL.

Sorry, that I currently can't do more, since I am pretty busy with my dayjob, which is not related to Linux.

Hannes

Comment 2 Raphael Groner 2021-11-23 12:37:04 UTC
In case of epel8, I could take my chance as co-maintainer. But there's less sense except in case of RHEL8 combination due to CentOS 8 is announced for EOL (without Stream) shortly 2021-12-31. 
Currently I don't personally see any usefulness for epel9 as the currently unstable development branch.

Comment 3 Mark E. Fuller 2021-11-23 12:52:59 UTC
I would be interested in helping to do this - I currently have access to EL8 systems would like to get involved with packaging and maintaining

Comment 4 Raphael Groner 2021-11-23 16:00:27 UTC
Thanks for your interest. In assumption your FAS is fuller I noticed you're not sponsored yet for packager group. Packaging and maintaining is only possible for members of that packager group, as a general policy in Fedora project. You may want to go through the process to get sponsored from someone available, I can't do because I'm no sponsor though.

Comment 5 Raphael Groner 2021-11-23 16:12:28 UTC
New branches requested.
epel8 https://pagure.io/releng/fedora-scm-requests/issue/38116
epel9 https://pagure.io/releng/fedora-scm-requests/issue/38117

Please tell me how to request for centos-stream as also mentioned with builds in your COPR.

Comment 6 Mark E. Fuller 2021-11-23 16:21:45 UTC
I am now yet familiar with the details of the Fedora build system, but am able to work with spec files and COPR builds - one of the suggested routes to joining the packagers is to become a co-maintainer, which I would be happy to do for backintime if anyone would be will to sponsor me.

As for the centos-stream, I do not yet know how this works in the pagure issues - I only know that COPR provides the chroots for CentOS Stream 8 and 9 and my build is successful when selecting these.

Comment 7 Raphael Groner 2021-11-23 17:34:56 UTC
In case of sponsoring I'd suggest you look around existing package reviews, try to give qualified comments there and/or file your own first review request with mentioning the need to get sponsored, to give a chance for available sponsors to notice your preference. That would be according to policy.

Back to topic. Successful build in epel8, so I'll create a bodhi update.

Comment 8 Fedora Update System 2021-11-23 17:37:28 UTC
FEDORA-EPEL-2021-95fb4c3672 has been submitted as an update to Fedora EPEL 8. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-95fb4c3672

Comment 9 Raphael Groner 2021-11-23 17:41:29 UTC
Well, epel9 branch does not seem to be fully ready yet for new builds.

Could not execute build: Unknown build target: epel9-candidate

Comment 10 Carl George 🤠 2021-11-23 20:46:11 UTC
> But there's less sense except in case of RHEL8 combination due to CentOS 8 is announced for EOL (without Stream) shortly 2021-12-31.

EPEL8 builds are still useful for CentOS Stream 8 (maintained until 2024), RHEL8 (maintained until 2029), and RHEL8 clones (maintained until 2029).

> Please tell me how to request for centos-stream as also mentioned with builds in your COPR.

EPEL builds almost always work fine on CentOS Stream.  It doesn't diverge that much from RHEL.  If you do find a situation where a library change in CentOS Stream affects an EPEL build, you can rebuild it in EPEL Next to get a working build, before rebuilding it in the main EPEL ~6 months later when the same change shows up in RHEL.

https://docs.fedoraproject.org/en-US/epel/epel-about-next/

> Well, epel9 branch does not seem to be fully ready yet for new builds.

Correct, we haven't created the epel9 build target yet.  Stay tuned to the epel-devel mailing list for an announcement soon.  We are evaluating a few options for the rollout.

https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org/thread/NH4CM6MAVUTUH35NDM53PTKCHODSEP6F/

Comment 11 Fedora Update System 2021-11-24 02:10:00 UTC
FEDORA-EPEL-2021-95fb4c3672 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-2021-95fb4c3672

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

Comment 12 Raphael Groner 2021-11-24 09:03:08 UTC
Hi Carl George, thanks for your clear explanation of Stream. That's what I was expecting. :)

In case of epel9, as said I'm not really convinced to currently start with stable packages in this early design phase. Feel free to build there also when dedicated build target is ready and if you have different opinion.

Comment 13 Fedora Update System 2021-12-02 01:39:12 UTC
FEDORA-EPEL-2021-95fb4c3672 has been pushed to the Fedora EPEL 8 stable repository.
If problem still persists, please make note of it in this bug report.