Bug 1202053

Summary:	Nokogiri was built against LibXML version 2.9.12, but has dynamically loaded 2.9.14
Product:	[openSUSE] openSUSE Distribution	Reporter:	Moritz Duge <duge>
Component:	Ruby	Assignee:	Ruby Devel <ruby-devel>
Status:	NEW ---	QA Contact:	E-mail List <qa-bugs>
Severity:	Normal
Priority:	P5 - None	CC:	dimstar, donald.price, mrueckert, tschmidt, Ulrich.Windl
Version:	Leap 15.4
Target Milestone:	---
Hardware:	Other
OS:	Other
Whiteboard:
Found By:	---	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Moritz Duge 2022-08-02 10:49:59 UTC

Since the libxml2-2-2.9.14 update ruby2.5-rubygem-nokogiri reports:

WARNING: Nokogiri was built against LibXML version 2.9.12, but has dynamically loaded 2.9.14

Reproduction:
ruby -e 'require "nokogiri"'

Please coordinate with bug 1201978.

Comment 1 Marcus Rückert 2022-08-02 11:40:22 UTC

This is not really a bug TBH.

Comment 2 Ulrich Windl 2022-08-08 06:20:23 UTC

I see it, too. When it's "not a bug", then the message is confusing at least.

Comment 3 Dominique Leuenberger 2022-12-07 14:04:28 UTC

(In reply to Marcus Rückert from comment #1)
> This is not really a bug TBH.

imho it is - nokogiri requires a rebuild (or if it does not care, shall shut up)

Comment 4 Don Price 2022-12-20 21:12:52 UTC

I am seeing a similar issue on all of our RMT servers in the public cloud infrastructure.  Our registration sharing service which is invoked every 30 seconds started showing the following warnings when we upgraded from SLES 15 SP3 to SLES 15 SP4:

bundle.ruby2.5[17998]: WARNING: Nokogiri was built against libxml version 2.9.7, but has dynamically loaded 2.9.14
bundle.ruby2.5[17998]: WARNING: Nokogiri was built against libxslt version 1.1.32, but has dynamically loaded 1.1.34

The task completes as expected, but the warnings are bloating our logs - I agree w/ Dominique's comment from Dec. 7th that this warrants a rebuild of Nokogiri.

Comment 5 Stefan Hundhammer 2022-12-21 10:24:11 UTC

It might be just a cosmetic problem, but it confuses a lot of users: They also see those messages on the text console during installation, and of course they think there is something seriously wrong.

At the very least, it's unprofessional to confront an end user with those messages.

Comment 6 Thomas Schmidt 2022-12-21 14:24:25 UTC

I think we cannot control which libxml patchlevel version is installed on the client, to make it match with what was there during build time. But we can skip that warning in RMT, patch will be in the next maintenance release (>2.10).