Bug 169922 - dev-perl/XML-LibXML-1.62.001-r1 collides with dev-perl/XML-LibXML-XPathContext-0.07
|
Bug#:
169922
|
Product: Gentoo Linux
|
Version: unspecified
|
Platform: x86
|
|
OS/Version: Linux
|
Status: RESOLVED
|
Severity: normal
|
Priority: P2
|
|
Resolution: FIXED
|
Assigned To: perl@gentoo.org
|
Reported By: RonnyPeine@gmx.de
|
|
Component: Ebuilds
|
|
|
URL:
|
|
Summary: dev-perl/XML-LibXML-1.62.001-r1 collides with dev-perl/XML-LibXML-XPathContext-0.07
|
|
Keywords:
|
|
Status Whiteboard:
|
|
Opened: 2007-03-08 11:40 0000
|
If i want to update dev-perl/XML-LibXML to version 1.62.001-r1 then i get a
collision with dev-perl/XML-LibXML-XPathContext-0.07 because both packages
provide the file:
/usr/lib/perl5/vendor_perl/5.8.8/i686-linux-thread-multi/XML/LibXML/XPathContext.pm
For reproduction you only need the FEATURE collision-protect in make.conf.
Reproducible: Always
From XML-LibXML Changes file:
1.61
- get{Elements,Children}By{TagName,TagNameNS,LocalName} now
obey wildcards '*', getChildrenByLocalName was added.
- XML::LibXML::XPathContext merged in
Looks like XML-LibXML-XPathContext can be removed, as every arch which has this
package keyworded also has >=XML-LibXML-1.61 keyworded.
(In reply to comment #1)
> From XML-LibXML Changes file:
>
> 1.61
> - get{Elements,Children}By{TagName,TagNameNS,LocalName} now
> obey wildcards '*', getChildrenByLocalName was added.
> - XML::LibXML::XPathContext merged in
>
> Looks like XML-LibXML-XPathContext can be removed, as every arch which has this
> package keyworded also has >=XML-LibXML-1.61 keyworded.
>
This would be fine by me. Ebuilds depending on XML-LibXML-XPathContext should
be changed accordingly to only depend on >=XML-LibXML-1.61 or older XML-LibXML
with XML-LibXML-XPathContext.
updating ebuilds right now for >=xml-libxml-1.61 (since its stable on all
relevant arch's). will be package masking xpath* shortly.
XML-LibXML-XPathContext package masked for removal.
(In reply to comment #4)
> XML-LibXML-XPathContext package masked for removal.
>
This was quick. Thanks for your work :)
p.mask'd and marked for removal, bringing this bug to a close. Thanks!