Bug 2178695 - keepalived json support tied to sha1 in spec
Summary: keepalived json support tied to sha1 in spec
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: keepalived
Version: 9.2
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Ryan O'Hara
QA Contact: cluster-qe@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-03-15 15:22 UTC by Juraj Hrdlica
Modified: 2023-07-07 12:49 UTC (History)
1 user (show)

Fixed In Version: keepalived-2.2.8-3.el9
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-07-07 12:49:34 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-151954 0 None None None 2023-03-15 15:25:09 UTC

Description Juraj Hrdlica 2023-03-15 15:22:56 UTC
Description of problem:
If keepalived were to be built without "sha1" it would also get built without JSON support
and
if it were to be built without JSON support, it is not doable without also building it without sha1.

Actual keepalived.spec:
%build
%configure \
...
    %{?with_sha1:--enable-sha1} \
    %{?with_sha1:--enable-json} \ #the issue is this line
...

Expected keepalived.spec:
%build
%configure \
...
    %{?with_sha1:--enable-sha1} \
    %{?with_json:--enable-json} \
...

Version-Release number of selected component (if applicable):
keepalived-2.2.4-6.el9

Comment 2 Ryan O'Hara 2023-03-24 16:11:46 UTC
Original BZ requesting JSON support:

https://bugzilla.redhat.com/show_bug.cgi?id=2129819

Comment 3 Ryan O'Hara 2023-07-07 12:49:34 UTC
I fixed this in the most recent RHEL9 build. I didn't bother to mention it in the changelog nor do I believe we need to mention it in the errata because it was harmless and did not affect customers in any way. This was purely an issue of being correcting the spec file. The only way someone would notice this is if they were building packages with conditionals.


Note You need to log in before you can comment on or make changes to this bug.