fedpkg request-branch epel10
Could not execute request_branch: This package is already an EL package, therefore it cannot be in EPEL. If this is a mistake....

Are you sure, to go to EPEL? How do I request a branch?

If it's an EL package, where is it?

I looked here:
https://mirror.stream.centos.org/10-stream/ (under BaseOS, AppStream and CRB) and didn't see it yet.

I made the request because an attempt to build rgb failed with "No matching package to install: 'pkgconfig(xorg-macros) >= 1.8'", which is something that this package normally provides.

Perhaps something has changed since the last CentOS Stream 10 compose?

Looking at https://composes.stream.centos.org/stream-10/production/latest-CentOS-Stream/compose/metadata/rpms.json it would seem that it should be in CRB. Maybe it's only just been added. I guess I need to wait a bit.

OK, so xorg-x11-util-macros *is* in CRB, but only for aarch64, not other arches.

I'll need to ask around to find out why that is and what to do about it.

I don't think that this package belongs to EPEL. It has always been a fundamental part of any Linux distribution as long as X11 is part of it. 

So I assume it will appear in EL10 soon

It seems that it is not intended to ship xorg-x11-util-macros in EL10, and the package was removed a while ago but somehow aarch64 got missed.

This merge request should remove it from aarch64:
https://gitlab.com/redhat/centos-stream/release-engineering/pungi-centos/-/merge_requests/798

That's expected to take around a week to propagate through the system and into a compose, so once that's done it should be possible to request the epel10 branch successfully.

I think there's a lot of things that are normally present in most Linux distributions that will not be included in EL10. I heard firefox will not be included for instance: https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org/message/AITD4DL54GVDNMYIKD2CLDJIBQ2NIQJJ/

> I don't think that this package belongs to EPEL. It has always been a fundamental part of any Linux distribution as long as X11 is part of it.

That's exactly what is changing in RHEL 10.

https://www.redhat.com/en/blog/rhel-10-plans-wayland-and-xorg-server

Once the removal of xorg-x11-util-macros is reflected in a new compose, the epel10 branch request will be able to go through.  However, I don't know how useful that package will be without the rest of the xorg server stack.  So far I've only seen people that want the stack to be available, but not people stepping up to maintain it in EPEL.  It may be more prudent to focus effort on helping upstreams port to wayland (or at least xwayland) rather than attempting to keep xorg server around, but that is an individual determination each contributor can make for themselves.

I will provide this small package for some reasons: 
 * No big effort to maintain
 * Very low in the stack so maybe needed more than something up

So next step for me is to wait for the epel10 beach to be available

(In reply to Carl George 🤠 from comment #7)
> > I don't think that this package belongs to EPEL. It has always been a fundamental part of any Linux distribution as long as X11 is part of it.
> 
> That's exactly what is changing in RHEL 10.
> 
> https://www.redhat.com/en/blog/rhel-10-plans-wayland-and-xorg-server

Please note that we are removing the _Xorg_ server, we are not removing X11, that's an important distinction to make.

X11 in Red Hat Enterprise Linux 10 is still supported through Xwayland, a full fledge X11 server.

Since xorg-x11-util-macros is a build dependency of multiple packages available in CentOS Stream 10, I started the process to make it available in CRB.

As José and Olivier have already mentioned, we plan on shipping this in CRB for RHEL 10.

For people that have a package that still depends on it: long term, it might make sense to see if you can switch to a more modern build system than autotools, for example meson, to do these things for you. That's what for example upstream Xwayland did.

If you go for CBR then I as fedora and EPEL package manager are out of the game and do not have to do anything. Right?

Yes, as far as I know, no action is required from your side @tilmann

Correct, once xorg-x11-util-macros is fully added to CRB, then it becomes ineligible for EPEL.  EPEL packages will then be able to build against it, solving for the real goal here.  Since Niels confirmed that is the plan, this bug can be closed.

For posterity, here is the issue tracking the package being added.

https://issues.redhat.com/browse/RHEL-57593