Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

xmlsec version is incompatible on Fedora Rawhide #1995

Closed
Mab879 opened this issue Jun 26, 2023 · 8 comments
Closed

xmlsec version is incompatible on Fedora Rawhide #1995

Mab879 opened this issue Jun 26, 2023 · 8 comments
Assignees

Comments

@Mab879
Copy link
Member

Mab879 commented Jun 26, 2023

Description of Problem:

Creating guides (and maybe other functionally) is currently broken on Fedora Rawhide. This appears to be related to the version of xmlsec in rawhide.

OpenSCAP Version:

1.3.8

Operating System & Version:

Fedora Rawhide as of 2023-06-26

Steps to Reproduce:

  1. oscap xccdf generate guide --profile stig /usr/share/xml/scap/ssg/content/ssg-rhel8-ds.xml > guide.html

Actual Results:

The guide fails to be created.

func=xmlSecCheckVersionExt:file=xmlsec.c:line=202:obj=unknown:subj=unknown:error=19:invalid version:mode=abi compatible;expected minor version=2;real minor version=3;expected subminor version=37;real subminor version=0
OpenSCAP Error: Loaded xmlsec library version is not compatible. [/builddir/build/BUILD/openscap-1.3.8/src/source/signature.c:142]
Invalid signature in SCAP Source Datastream (1.3) content in /usr/share/xml/scap/ssg/content/ssg-rhel8-ds.xml [/builddir/build/BUILD/openscap-1.3.8/src/XCCDF/xccdf_session.c:848]

Expected Results:

The guide is created

Additional Information / Debugging Steps:

rpm -iq xmlsec1
xmlsec1-1.2.37-4.fc39.x86_64
@Mab879 Mab879 changed the title xmlsec verison is incampatible on Rawhide xmlsec verison is incampatible on Fedora Rawhide Jun 26, 2023
@jan-cerny jan-cerny changed the title xmlsec verison is incampatible on Fedora Rawhide xmlsec version is incompatible on Fedora Rawhide Jun 26, 2023
@evgenyz
Copy link
Contributor

evgenyz commented Jun 26, 2023

@evgenyz
Copy link
Contributor

evgenyz commented Jun 26, 2023

So, it has been built with 1.2.37 but the runtime .so version is 1.3.0 for some reason? At the same time the package is of version 1.2.37. That's very weird.

@evgenyz
Copy link
Contributor

evgenyz commented Jun 26, 2023

So, it has been built with 1.2.37 but the runtime .so version is 1.3.0?

Hmm, or is it the other way around?

@evgenyz
Copy link
Contributor

evgenyz commented Jun 26, 2023

Oh, just how lucky we are: https://bugzilla.redhat.com/show_bug.cgi?id=2187631. Perfect timing, #@$^%@&#$!

@evgenyz
Copy link
Contributor

evgenyz commented Jun 27, 2023

I guess I'd have to rebuild it.

@evgenyz
Copy link
Contributor

evgenyz commented Jun 27, 2023

@Mab879
Copy link
Member Author

Mab879 commented Jun 29, 2023

On the latest rawhide (as of 29 June 2023) this issue appears to be resolved.

@jan-cerny
Copy link
Member

Yes, the problem no longer appears in our test runs, see eg. ComplianceAsCode/content#10787 where the jobs on Rawhide pass.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants