RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1854339 - Provide Judy-devel package in EPEL-8
Summary: Provide Judy-devel package in EPEL-8
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: Judy
Version: CentOS Stream
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Michal Schorm
QA Contact: RHEL CS Apps Subsystem QE
URL:
Whiteboard:
Depends On:
Blocks: 1842644
TreeView+ depends on / blocked
 
Reported: 2020-07-07 08:43 UTC by Fabio Alessandro Locati
Modified: 2021-02-15 02:51 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-11-09 15:43:43 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
CentOS 17828 0 None None None 2020-11-03 13:47:26 UTC
Fedora Pagure fedora-infrastructure issue 9414 0 None None None 2020-10-26 14:21:22 UTC

Description Fabio Alessandro Locati 2020-07-07 08:43:40 UTC 
I'm trying to build stress-ng in EPEL-8, but it requires Judy.
To be precise, in the SPEC file, I have a `BuildRequires:  Judy-devel`.

As for the conversation I had on IRC with mschorm, I'm opening this bug.

Thanks a lot
Comment 1 Paul Howarth 2020-07-07 08:49:47 UTC 
Judy (but not Judy-devel) is supplied in the AppStream repository on EL-8.2.

In EL-8.1 Judy-devel was included in the PowerTools/CRB repositories but it is gone in EL-8.2.

I don't think it's allowable to package Judy for EPEL-8 but maybe mschorm knows otherwise?
Comment 2 Michal Schorm 2020-07-07 09:57:10 UTC 
I'm now investigating an option to use the "Judy-devel" from the CRB fro this purpose.

> In EL-8.1 Judy-devel was included in the PowerTools/CRB repositories
> but it is gone in EL-8.2.
Yes, that what I've just noticed and I already begun steps to fix it.

> I don't think it's allowable to package Judy for EPEL-8 but maybe mschorm knows otherwise?
I'm not much of an EPEL packager, I don't know the EPEL rules better than anyone else who read them a few times.
I'd stick in general to a rule to NOT add content to EPEL which already is available in RHEL 8 or worse - it would confict with it.
However I've just begun so this ain't final decision from far.

I'm going to observer simmilar tickets and consult some strategy how to avoid maintaining the same package for the same product on multiple places. That would surely by unfortunate.

I'll take this BZ under my wings until then.
Comment 3 Paul Howarth 2020-07-07 10:40:53 UTC 
Regarding similar tickets, it looks a bit like libssh2 (https://bugzilla.redhat.com/show_bug.cgi?id=1792625).
Comment 4 Ben Cotton 2020-08-11 13:45:42 UTC 
This bug appears to have been reported against 'rawhide' during the Fedora 33 development cycle.
Changing version to 33.
Comment 5 Christopher Brown 2020-09-07 20:36:30 UTC 
Hi Michal,

(In reply to Michal Schorm from comment #2)

> I'm going to observer simmilar tickets and consult some strategy how to
> avoid maintaining the same package for the same product on multiple places.
> That would surely by unfortunate.
> 
> I'll take this BZ under my wings until then.

Any news on this?
Comment 6 jakub.jedelsky 2020-10-26 13:41:47 UTC 
Hello, any update on the package? I'm missing Judy-devel in EL8 as well. Thanks.
Comment 7 Christopher Brown 2020-10-26 14:23:28 UTC 
Hey Jakub,

(In reply to Jakub Jedelsky from comment #6)
> Hello, any update on the package? I'm missing Judy-devel in EL8 as well.
> Thanks.

Thanks for the nudge. I've opened a Pagure ticket to get some feedback from Fedora Infra as we've not heard back from Michal yet.
Comment 8 Kevin Fenzi 2020-10-26 15:14:54 UTC 
The centos Devel repo was added to handle cases like this. 

See https://wiki.centos.org/FAQ/develrepo
Comment 9 Christopher Brown 2020-10-26 15:35:41 UTC 
(In reply to Kevin Fenzi from comment #8)
> The centos Devel repo was added to handle cases like this. 
> 
> See https://wiki.centos.org/FAQ/develrepo

Thanks Kevin, will work to get something submitted there.
Comment 10 Kevin Fenzi 2020-11-01 19:46:00 UTC 
Can we close this now? or do we need it open for some reason?
Comment 11 Christopher Brown 2020-11-03 13:47:44 UTC 
(In reply to Kevin Fenzi from comment #10)
> Can we close this now? or do we need it open for some reason?

I can close this now I have opened a bug at the CentOS bug tracker, thanks.
Comment 12 Carl George 🤠 2020-11-07 19:37:19 UTC 
Sorry for the confusion, but the process has changed.  We are now tracking these requests here in bugzilla.  Since this bug already exists, I'm just going to move it to the right product/version.

The develrepo page [0] had outdated information about opening bugs in the CentOS bug tracker, but I've updated it now to reflect the current process, which is described in detail on a different page [1].

Once RHEL accepts adding this to CRB, it will be added to CentOS Stream PowerTools and CentOS Linux Devel (at which point it will be available for EPEL packages to build against).

[0] https://wiki.centos.org/FAQ/develrepo
[1] https://wiki.centos.org/FAQ/CentOS8/UnshippedPackages
Comment 14 Josh Boyer 2020-11-09 12:30:42 UTC 
Judy-devel is already available in RHEL in the Code Ready Builder repository.  It's part of the mariadb-devel module.

[jwboyer@vader ~]$ sudo yum module enable mariadb-devel
Updating Subscription Management repositories.
Last metadata expiration check: 0:05:14 ago on Mon 09 Nov 2020 07:24:18 AM EST.
Dependencies resolved.
================================================================================
 Package           Architecture     Version             Repository         Size
================================================================================
Enabling module streams:
 mariadb-devel                      10.3                                       

Transaction Summary
================================================================================

Is this ok [y/N]: y
Complete!
[jwboyer@vader ~]$ sudo yum install Judy-devel
Updating Subscription Management repositories.
Last metadata expiration check: 0:05:27 ago on Mon 09 Nov 2020 07:24:18 AM EST.
Dependencies resolved.
================================================================================
 Package    Arch   Version       Repository                                Size
================================================================================
Installing:
 Judy-devel x86_64 1.0.5-18.module+el8+2765+cfa4f87b
                                 codeready-builder-for-rhel-8-x86_64-rpms  76 k
Installing dependencies:
 Judy       x86_64 1.0.5-18.module+el8+2765+cfa4f87b
                                 rhel-8-for-x86_64-appstream-rpms         131 k
Enabling module streams:
 mariadb           10.3                                                        

Transaction Summary
================================================================================
Install  2 Packages

Total download size: 206 k
Installed size: 746 k
Comment 16 Carl George 🤠 2020-11-09 15:38:24 UTC 
Non-default module stream are not available in the EPEL8 buildroot.  This request is specifically for adding the non-modular RPM to CRB to make it available in the EPEL8 buildroot.

RPMs from non-default module streams are eligible to be added to EPEL [0], but in this case that would be quite complicated because the base Judy package is available in a default module stream.  Anyone looking to add Judy-devel to EPEL8 will need to significantly modify the spec file to import it under a different name and not produce the Judy binary package.  It would also ideally be kept in sync with the RHEL spec file for library compatibility.

[0] https://fedoraproject.org/wiki/EPEL/GuidelinesAndPolicies#Policy
Comment 17 Josh Boyer 2020-11-09 15:43:43 UTC 
(In reply to Carl George 🤠 from comment #16)
> Non-default module stream are not available in the EPEL8 buildroot.  This
> request is specifically for adding the non-modular RPM to CRB to make it
> available in the EPEL8 buildroot.

There is no non-modular Judy build.

> RPMs from non-default module streams are eligible to be added to EPEL [0],
> but in this case that would be quite complicated because the base Judy
> package is available in a default module stream.  Anyone looking to add
> Judy-devel to EPEL8 will need to significantly modify the spec file to
> import it under a different name and not produce the Judy binary package. 
> It would also ideally be kept in sync with the RHEL spec file for library
> compatibility.
> 
> [0] https://fedoraproject.org/wiki/EPEL/GuidelinesAndPolicies#Policy
Comment 18 Christopher Brown 2020-11-09 17:00:03 UTC 
I think we just continue to provide workaround to not include Judy.

Whilst it still builds, it seems that upstream is rather inactive with the last release 11 years ago.
Comment 19 Carl George 🤠 2020-11-09 17:19:29 UTC 
Upon closer inspection, I was mistaken, Judy-devel is available in the EPEL8 buildroot.  I created a scratch build [0] based on the epel8 spec file [1], but with the conditional around the Judy-devel build requirement removed.  The build was able to install Judy-devel and build against it.

Lesson learned, it's no longer true that only default module streams are available to EPEL builds.  I'll work on getting some documentation about exactly which modules streams are available in the EPEL buildroot.

[0] https://koji.fedoraproject.org/koji/taskinfo?taskID=55248866
[1] https://src.fedoraproject.org/rpms/stress-ng/blob/epel8/f/stress-ng.spec
Comment 20 Christopher Brown 2020-11-10 10:31:47 UTC 
(In reply to Carl George 🤠 from comment #19)
> Upon closer inspection, I was mistaken, Judy-devel is available in the EPEL8
> buildroot.  I created a scratch build [0] based on the epel8 spec file [1],
> but with the conditional around the Judy-devel build requirement removed. 
> The build was able to install Judy-devel and build against it.

Thanks everyone, I have submitted updates as appropriate.
Note You need to log in before you can comment on or make changes to this bug.