[Samba] Updated samba 4.16.2 RPM build tools at https://github.com/nkadel/samba4repo

Nico Kadel-Garcia nkadel at gmail.com
Sun Jun 19 16:46:04 UTC 2022

On Sun, Jun 19, 2022 at 6:42 AM <vincent at cojot.name> wrote:
> Also, it's in the EPEL8 FAQ and the way to get the missing package in
> RHEL8 is documented there:
> https://fedoraproject.org/wiki/EPEL/FAQ#RHEL_8_has_binaries_in_the_release,_but_is_missing_some_corresponding_-devel_package._How_do_I_build_a_package_that_needs_that_missing_-devel_package?

I've previously submitted the suggested bug reports. This has been
going on since RHEL 8 was published. It's more apparent now because
RHEL 8 caught up with the current Samba. talloc, and ldb releases, and
I'd hoped that I could finally use the RHEL: published RPMs and speed
up my testing cycles. I can't precisely because of these deliberate
exclusions, and it makes my building and testing of development rigs
of Samba much more difficult.

"Build the missing -devel package" is not very helpful.   I do build
it myself, and have been doing so for years, and it's gotten tiresome.
The exclusions cannot be accidental, they've been occurring since at
least the initial release of RHEL 8. It also cannot be accidental that
CentOS, RockyLinux, and AlmaLinux are mirroring the practice. his
problem is not a one-off or an oversignt. This has been going on for
at least 3 years. I've bug reported it before to Red Hat. The last
time I got a meaningful response, it concerned the similar problem of
lmdb-devel, which they finally relented and included in their standard

Vincent, I'm sorry to be so snarky about Red Hat's behavior, but it's
hindering my long-active work to provide production capable, fully
featured Samba releases rather than the feature stripped releases Red
Hat has elected to publish. I've been publishing ports of Samba to
commercial operating systems since.... 1995, way back with SunOS
4.1.4, well before Red Hat's first release. I bring it up here so that
other folks dealing with RHEL and Samba know what is going on, and
understand that Red Hat is hindering Samba development work in this
fashion. If it were once, I'd chalk it up to an accidental packaging
exclusion. But it's been 3 years and two major operating system
releases now. It may not be malice, but it's not supportive.

Generally, I've been a big Red Hat fan and supporter of it for
servers. I've personally deployed approximately 20,000 Red Hat
systems, and I've been publishing Samba backports for RHEL since...
2013. This is an ongoing problem caused by a very specific Red Hat
policy. I bring it up here for the Samba developers to be very
specifically aware of. It's not a general architectural problem for
RHEL and its clones. That makes it seem deliberate, and it's been
going on so long that it's hard to understand it as anything but a
deliberate hindrance.

Nico Kadel-Garcia

More information about the samba mailing list