Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 575872 - dev-ruby/nokogiri fails to detect LibXML change
Summary: dev-ruby/nokogiri fails to detect LibXML change
Status: UNCONFIRMED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Gentoo Ruby Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-02-28 09:49 UTC by Anton Bolshakov
Modified: 2023-07-11 17:38 UTC (History)
4 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Anton Bolshakov 2016-02-28 09:49:18 UTC
Hi,

After recent upgrade, I'm getting the following warning message:
WARNING: Nokogiri was built against LibXML version 2.9.2, but has dynamically loaded 2.9.3

I tried to run both emerge @preserved-rebuild and revdep-rebuild but it does not trigger the rebuild.

The current ebuild has RDEPEND >=dev-libs/libxml2-2.9.2:= and DEPEND >=dev-libs/libxml2-2.9.2 which might overwrite the := logic.

You should probably change it to the usual:
DEPEND=".."
RDEPEND="${DEPEND}"
Comment 1 Hans de Graaff gentoo-dev Security 2016-02-29 19:34:49 UTC
I think the problem is that libxml2 does not have sub-slots at the moment, so the := dependency is currently without effect. I'm not sure if the maintainers are willing to add a sub-slot, cc-ing them.
Comment 2 Pacho Ramos gentoo-dev 2016-02-29 19:49:48 UTC
I am unsure if we should add a subslot for this concrete case. It looks to me that nokogiri is too strict warning about that (in fact, our recent 2.9.2-rX revisions were really really close to 2.9.3) :/ 

This looks similar to bug 517908, that shows another example of a reverse dep being too strict and warning and dying without really needing to do so.
Comment 3 Hans de Graaff gentoo-dev Security 2016-02-29 20:15:01 UTC
(In reply to Pacho Ramos from comment #2)
> I am unsure if we should add a subslot for this concrete case. It looks to
> me that nokogiri is too strict warning about that (in fact, our recent
> 2.9.2-rX revisions were really really close to 2.9.3) :/ 
> 
> This looks similar to bug 517908, that shows another example of a reverse
> dep being too strict and warning and dying without really needing to do so.

nokogiri only prints a warning, but that is annoying enough. In my case this generates a bunch of cron emails that should not be sent due to normally being empty.

It might be better to simply patch out the warning in the nokogiri ebuild.
Comment 4 Gilles Dartiguelongue (RETIRED) gentoo-dev 2016-03-05 17:40:19 UTC
So I was about to say that libxml2 needs not a subslot but I cannot say that because it's soversion is clearly nothing you would expect to be correct. So while I have not encountered a problem that would require libxml2 rebuilds in the years I have been using Gentoo, it does not mean there is no need for it.
Comment 5 Jonathan Lovelace 2016-07-30 01:51:49 UTC
This warning makes =dev-ruby/rspec-core-3.3.2-r1 fail its tests (specifically the test "RSpec behaves like library wide checks issues no warnings when the spec files are loaded") if dev-libs/libxml2 has been upgraded since dev-ruby/nokogiri was built.