Bug 2344701

ote that since evolution-data-server is in c10s we would need to build the matching version of evolution, the one in f41 is too new

*note

This might be a stupid question, but anyway, how do you "branch & build" for the epel10, please? These things used to be automatic in the past, or at least I do not recall I did anything with it in the past.

gnome-sig added with a commit access, the same for the evolution-ews project. No idea why it was not there before.

(In reply to Milan Crha from comment #3)
> how do you "branch & build" for the epel10, please?

Responding to myself: it's

    fedpkg request-branch epel10

It created almost empty branch. I've no idea what to do next (probably copy the files from the fXY branch), but the ucrrent evolution-data-server version in RHEL 10 is 3.52.4, thus you need the same evolution series (3.52.x), which is `f40` branch.

I added you as a `collaborator` for the epel* branches in the evolution and evolution-ews. I guess that's all I should do here. Thank you.

(In reply to Milan Crha from comment #5)
> (In reply to Milan Crha from comment #3)
> > how do you "branch & build" for the epel10, please?
> 
> Responding to myself: it's
> 
>     fedpkg request-branch epel10
> 
> It created almost empty branch. I've no idea what to do next (probably copy
> the files from the fXY branch), but the ucrrent evolution-data-server
> version in RHEL 10 is 3.52.4, thus you need the same evolution series
> (3.52.x), which is `f40` branch.
> 
> I added you as a `collaborator` for the epel* branches in the evolution and
> evolution-ews. I guess that's all I should do here. Thank you.

Thank you! I'm also in the GNOME SIG, so I can also use that access - but being in the ACL helps I guess to indicate who is doing what. Can you make me the EPEL Bugzilla assignee so you don't have to deal with EPEL bugs?

Branching and building is not automatic in EPEL - Evolution was part of CentOS Stream / RHEL proper so this was not an issue previously, but got dropped because webkitgtk was removed.

❯ fedrq pkgs evolution -b c9s
evolution-3.40.4-11.el9.src
evolution-3.40.4-11.el9.x86_64


and in EPEL for each release maintainers have to opt in, because a lot of dependencies might no longer make sense (also we don't want to make people have to support packages for the entire lifecycle unless they opt in) - you can imagine this does make bootstrapping trickier :)

So yeah - please make me the EPEL assignee for bugzillas for both this and evolution-ews, and I'll reopen this for now until I can build the update, thanks

Okay, set you as the EPEL bugzilla assignee in evo, evo-ews and libpst.

I do not know how to auto-CC me on the EPEL bugs, thus feel free to CC me on them, because they can be relevant for the upstream too.

(In reply to Milan Crha from comment #7)
> Okay, set you as the EPEL bugzilla assignee in evo, evo-ews and libpst.
> 
> I do not know how to auto-CC me on the EPEL bugs, thus feel free to CC me on
> them, because they can be relevant for the upstream too.

I think all package maintainers get cc:ed anyway, so you should be good to go. Thanks again!

FEDORA-EPEL-2025-5e6251ec41 (evolution-3.52.4-2.el10_1 and evolution-ews-3.52.4-1.el10_1) has been submitted as an update to Fedora EPEL 10.1.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-5e6251ec41

FEDORA-EPEL-2025-75f13b9c70 (evolution-3.52.4-2.el10_0 and evolution-ews-3.52.4-1.el10_0) has been submitted as an update to Fedora EPEL 10.0.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-75f13b9c70

FEDORA-EPEL-2025-5e6251ec41 (evolution-3.52.4-2.el10_1 and evolution-ews-3.52.4-1.el10_1) has been pushed to the Fedora EPEL 10.1 stable repository.
If problem still persists, please make note of it in this bug report.

FEDORA-EPEL-2025-75f13b9c70 (evolution-3.52.4-2.el10_0 and evolution-ews-3.52.4-1.el10_0) has been pushed to the Fedora EPEL 10.0 stable repository.
If problem still persists, please make note of it in this bug report.