[suggest] Latest XML::LibXSLT needed

[David Steinbrunner]

Hello all,

The XML::LibXSLT and XML::LibXML packages in rpmforge are currently
incompatible. See the following as evidence:

[Mon May 03 19:19:18 2010] [error] This version of XML::LibXSLT requires
XML::LibXML 1.6 (ABI 1), which is incompatible with currently installed
XML::LibXML 1.70 (ABI 2). Please upgrade XML::LibXSLT, XML::LibXML, or both!
at
/usr/lib64/perl5/vendor_perl/5.8.8/x86_64-linux-thread-multi/XML/LibXML.pm
line 49.\nBEGIN failed--compilation aborted at
/usr/lib64/perl5/vendor_perl/5.8.8/x86_64-linux-thread-multi/XML/LibXSLT.pm
line 7.\nCompilation failed in require at
/usr/lib/perl5/site_perl/5.8.8/Album/Apache/AuthCookie.pm line 32.\nBEGIN
failed--compilation aborted at
/usr/lib/perl5/site_perl/5.8.8/Album/Apache/AuthCookie.pm line
32.\nCompilation failed in require at (eval 4) line 3.\n

The version of XML::LibXSLT that is available is 1.62 while the buildlogs
show that version 1.66 is the latest version that has tried to be built.

Here is the error from the buildlog:

error: Failed build dependencies:
perl(XML::LibXML) >= 1.60 is needed by
perl-XML-LibXSLT-1.66-1.el5.rf.x86_64

This is similar to the batch of issues I pointed out on the users list with
the subject "Perl module build issues":

http://lists.rpmforge.net/pipermail/users/2010-April/002963.html
http://lists.rpmforge.net/pipermail/users/2010-April/002964.html

I never saw a reply to those and it does not appear the issues have been
resolved.

In any case, it appears XML::LibXSLT version 1.70 is required to match the
version of XML::LibXML that is available. Hopefully in the process of being
built the newer XML::LibXML will be seen so the build will be successful.

Thanks,

--
David Steinbrunner

[David Steinbrunner]

Hello all,

The XML::LibXSLT and XML::LibXML packages in rpmforge are currently
incompatible. See the following as evidence:

[Mon May 03 19:19:18 2010] [error] This version of XML::LibXSLT requires
XML::LibXML 1.6 (ABI 1), which is incompatible with currently installed
XML::LibXML 1.70 (ABI 2). Please upgrade XML::LibXSLT, XML::LibXML, or both!
at
/usr/lib64/perl5/vendor_perl/5.8.8/x86_64-linux-thread-multi/XML/LibXML.pm
line 49.\nBEGIN failed--compilation aborted at
/usr/lib64/perl5/vendor_perl/5.8.8/x86_64-linux-thread-multi/XML/LibXSLT.pm
line 7.\nCompilation failed in require at
/usr/lib/perl5/site_perl/5.8.8/Album/Apache/AuthCookie.pm line 32.\nBEGIN
failed--compilation aborted at
/usr/lib/perl5/site_perl/5.8.8/Album/Apache/AuthCookie.pm line
32.\nCompilation failed in require at (eval 4) line 3.\n

The version of XML::LibXSLT that is available is 1.62 while the buildlogs
show that version 1.66 is the latest version that has tried to be built.

Here is the error from the buildlog:

error: Failed build dependencies:
perl(XML::LibXML) >= 1.60 is needed by
perl-XML-LibXSLT-1.66-1.el5.rf.x86_64

This is similar to the batch of issues I pointed out on the users list with
the subject "Perl module build issues":

http://lists.rpmforge.net/pipermail/users/2010-April/002963.html
http://lists.rpmforge.net/pipermail/users/2010-April/002964.html

I never saw a reply to those and it does not appear the issues have been
resolved.

In any case, it appears XML::LibXSLT version 1.70 is required to match the
version of XML::LibXML that is available. Hopefully in the process of being
built the newer XML::LibXML will be seen so the build will be successful.

Thanks,

--
David Steinbrunner

[David Steinbrunner]

Hello all,

The XML::LibXSLT and XML::LibXML packages in rpmforge are currently
incompatible. See the following as evidence:

[Mon May 03 19:19:18 2010] [error] This version of XML::LibXSLT requires
XML::LibXML 1.6 (ABI 1), which is incompatible with currently installed
XML::LibXML 1.70 (ABI 2). Please upgrade XML::LibXSLT, XML::LibXML, or both!
at
/usr/lib64/perl5/vendor_perl/5.8.8/x86_64-linux-thread-multi/XML/LibXML.pm
line 49.\nBEGIN failed--compilation aborted at
/usr/lib64/perl5/vendor_perl/5.8.8/x86_64-linux-thread-multi/XML/LibXSLT.pm
line 7.\nCompilation failed in require at
/usr/lib/perl5/site_perl/5.8.8/Album/Apache/AuthCookie.pm line 32.\nBEGIN
failed--compilation aborted at
/usr/lib/perl5/site_perl/5.8.8/Album/Apache/AuthCookie.pm line
32.\nCompilation failed in require at (eval 4) line 3.\n

The version of XML::LibXSLT that is available is 1.62 while the buildlogs
show that version 1.66 is the latest version that has tried to be built.

Here is the error from the buildlog:

error: Failed build dependencies:
perl(XML::LibXML) >= 1.60 is needed by
perl-XML-LibXSLT-1.66-1.el5.rf.x86_64

This is similar to the batch of issues I pointed out on the users list with
the subject "Perl module build issues":

http://lists.rpmforge.net/pipermail/users/2010-April/002963.html
http://lists.rpmforge.net/pipermail/users/2010-April/002964.html

I never saw a reply to those and it does not appear the issues have been
resolved.

In any case, it appears XML::LibXSLT version 1.70 is required to match the
version of XML::LibXML that is available. Hopefully in the process of being
built the newer XML::LibXML will be seen so the build will be successful.

Thanks,

--
David Steinbrunner

[David Steinbrunner]

Hello all,

The XML::LibXSLT and XML::LibXML packages in rpmforge are currently
incompatible. See the following as evidence:

[Mon May 03 19:19:18 2010] [error] This version of XML::LibXSLT requires
XML::LibXML 1.6 (ABI 1), which is incompatible with currently installed
XML::LibXML 1.70 (ABI 2). Please upgrade XML::LibXSLT, XML::LibXML, or both!
at
/usr/lib64/perl5/vendor_perl/5.8.8/x86_64-linux-thread-multi/XML/LibXML.pm
line 49.\nBEGIN failed--compilation aborted at
/usr/lib64/perl5/vendor_perl/5.8.8/x86_64-linux-thread-multi/XML/LibXSLT.pm
line 7.\nCompilation failed in require at
/usr/lib/perl5/site_perl/5.8.8/Album/Apache/AuthCookie.pm line 32.\nBEGIN
failed--compilation aborted at
/usr/lib/perl5/site_perl/5.8.8/Album/Apache/AuthCookie.pm line
32.\nCompilation failed in require at (eval 4) line 3.\n

The version of XML::LibXSLT that is available is 1.62 while the buildlogs
show that version 1.66 is the latest version that has tried to be built.

Here is the error from the buildlog:

error: Failed build dependencies:
perl(XML::LibXML) >= 1.60 is needed by
perl-XML-LibXSLT-1.66-1.el5.rf.x86_64

This is similar to the batch of issues I pointed out on the users list with
the subject "Perl module build issues":

http://lists.rpmforge.net/pipermail/users/2010-April/002963.html
http://lists.rpmforge.net/pipermail/users/2010-April/002964.html

I never saw a reply to those and it does not appear the issues have been
resolved.

In any case, it appears XML::LibXSLT version 1.70 is required to match the
version of XML::LibXML that is available. Hopefully in the process of being
built the newer XML::LibXML will be seen so the build will be successful.

Thanks,

--
David Steinbrunner

[David Steinbrunner]

Hello all,

The XML::LibXSLT and XML::LibXML packages in rpmforge are currently
incompatible. See the following as evidence:

[Mon May 03 19:19:18 2010] [error] This version of XML::LibXSLT requires
XML::LibXML 1.6 (ABI 1), which is incompatible with currently installed
XML::LibXML 1.70 (ABI 2). Please upgrade XML::LibXSLT, XML::LibXML, or both!
at
/usr/lib64/perl5/vendor_perl/5.8.8/x86_64-linux-thread-multi/XML/LibXML.pm
line 49.\nBEGIN failed--compilation aborted at
/usr/lib64/perl5/vendor_perl/5.8.8/x86_64-linux-thread-multi/XML/LibXSLT.pm
line 7.\nCompilation failed in require at
/usr/lib/perl5/site_perl/5.8.8/Album/Apache/AuthCookie.pm line 32.\nBEGIN
failed--compilation aborted at
/usr/lib/perl5/site_perl/5.8.8/Album/Apache/AuthCookie.pm line
32.\nCompilation failed in require at (eval 4) line 3.\n

The version of XML::LibXSLT that is available is 1.62 while the buildlogs
show that version 1.66 is the latest version that has tried to be built.

Here is the error from the buildlog:

error: Failed build dependencies:
perl(XML::LibXML) >= 1.60 is needed by
perl-XML-LibXSLT-1.66-1.el5.rf.x86_64

This is similar to the batch of issues I pointed out on the users list with
the subject "Perl module build issues":

http://lists.rpmforge.net/pipermail/users/2010-April/002963.html
http://lists.rpmforge.net/pipermail/users/2010-April/002964.html

I never saw a reply to those and it does not appear the issues have been
resolved.

In any case, it appears XML::LibXSLT version 1.70 is required to match the
version of XML::LibXML that is available. Hopefully in the process of being
built the newer XML::LibXML will be seen so the build will be successful.

Thanks,

--
David Steinbrunner

[David Steinbrunner]

Post by David Steinbrunner
The XML::LibXSLT and XML::LibXML packages in rpmforge are currently
[Mon May 03 19:19:18 2010] [error] This version of XML::LibXSLT requires
XML::LibXML 1.6 (ABI 1), which is incompatible with currently installed
XML::LibXML 1.70 (ABI 2). Please upgrade XML::LibXSLT, XML::LibXML, or both!
at /usr/lib64/perl5/vendor_perl/5.8.8/x86_64-linux-thread-multi/XML/LibXML.pm
line 49.\nBEGIN failed--compilation aborted at
/usr/lib64/perl5/vendor_perl/5.8.8/x86_64-linux-thread-multi/XML/LibXSLT.pm
line 7.\nCompilation failed in require at
/usr/lib/perl5/site_perl/5.8.8/Album/Apache/AuthCookie.pm line 32.\nBEGIN
failed--compilation aborted at
/usr/lib/perl5/site_perl/5.8.8/Album/Apache/AuthCookie.pm line
32.\nCompilation failed in require at (eval 4) line 3.\n
The version of XML::LibXSLT that is available is 1.62 while the buildlogs show
that version 1.66 is the latest version that has tried to be built.
perl(XML::LibXML) >= 1.60 is needed by
perl-XML-LibXSLT-1.66-1.el5.rf.x86_64
This is similar to the batch of issues I pointed out on the users list with
http://lists.rpmforge.net/pipermail/users/2010-April/002963.html
http://lists.rpmforge.net/pipermail/users/2010-April/002964.html
I never saw a reply to those and it does not appear the issues have been
resolved.
In any case, it appears XML::LibXSLT version 1.70 is required to match the
version of XML::LibXML that is available. Hopefully in the process of being
built the newer XML::LibXML will be seen so the build will be successful.

The buildlogs show no change here.

I was recently talking to someone about rpmforge in general and they
mentioned this same exact issue so I'm not the only one that has run into
this, just the only one that has reported it.

--
David Steinbrunner

[Christoph Maser]

Post by David Steinbrunner

Post by David Steinbrunner
The XML::LibXSLT and XML::LibXML packages in rpmforge are currently
[Mon May 03 19:19:18 2010] [error] This version of XML::LibXSLT requires
XML::LibXML 1.6 (ABI 1), which is incompatible with currently installed
XML::LibXML 1.70 (ABI 2). Please upgrade XML::LibXSLT, XML::LibXML, or both!
at /usr/lib64/perl5/vendor_perl/5.8.8/x86_64-linux-thread-multi/XML/LibXML.pm
line 49.\nBEGIN failed--compilation aborted at
/usr/lib64/perl5/vendor_perl/5.8.8/x86_64-linux-thread-multi/XML/LibXSLT.pm
line 7.\nCompilation failed in require at
/usr/lib/perl5/site_perl/5.8.8/Album/Apache/AuthCookie.pm line 32.\nBEGIN
failed--compilation aborted at
/usr/lib/perl5/site_perl/5.8.8/Album/Apache/AuthCookie.pm line
32.\nCompilation failed in require at (eval 4) line 3.\n
The version of XML::LibXSLT that is available is 1.62 while the buildlogs show
that version 1.66 is the latest version that has tried to be built.
perl(XML::LibXML) >= 1.60 is needed by
perl-XML-LibXSLT-1.66-1.el5.rf.x86_64
This is similar to the batch of issues I pointed out on the users list with
http://lists.rpmforge.net/pipermail/users/2010-April/002963.html
http://lists.rpmforge.net/pipermail/users/2010-April/002964.html
I never saw a reply to those and it does not appear the issues have been
resolved.
In any case, it appears XML::LibXSLT version 1.70 is required to match the
version of XML::LibXML that is available. Hopefully in the process of being
built the newer XML::LibXML will be seen so the build will be successful.

The buildlogs show no change here.
I was recently talking to someone about rpmforge in general and they
mentioned this same exact issue so I'm not the only one that has run into
this, just the only one that has reported it.
--
David Steinbrunner

I had another look at this. perl-XML-LibXML is shipped in base so we
should not have it in the repo in the first place at least for RHEL5/C5.
Since there is a incomptible change in the new perl-XML-LibXML
overwriting the version from base is no option.

As I am for a much more strict policy at rpmforge I vote for a complete
removal of perl-XML-LibXMl and perl-XML-LibXSLT or at most provide an
old version for perl-XML-LibXSLT wich works with the perl-XML-LibXML
version from base. It is much better to not have a particular piece then
to have a broken version.


Chris

[Steve Huff]

Post by Christoph Maser
As I am for a much more strict policy at rpmforge I vote for a complete
removal of perl-XML-LibXMl and perl-XML-LibXSLT or at most provide an
old version for perl-XML-LibXSLT wich works with the perl-XML-LibXML
version from base. It is much better to not have a particular piece then
to have a broken version.

Chris,

i did some digging into this (see SVN r8817), and we need at the very minimum:

perl-XML-LibXML <= 1.69
perl-XML-LibXML-Common (bring it back from the vault)
perl-XML-LibXSLT <= 1.63

and we need Dag to remove any later versions from the repo.

if we want to roll all the way back to the versions from upstream, we have to go back to perl-XML-LibXSLT <= 1.59 (there's already a spec for this in SVN). for packages that are as widely used as these, i'm OK with offering versions that replace packages from upstream, since their absence is really crippling.

-shuff

--
If this were played upon a stage now, I could condemn it as an improbable fiction. - Fabian, Twelfth Night, III,v
http://five.sentenc.es

-------------- next part --------------
A non-text attachment was scrubbed...
Name: PGP.sig
Type: application/pgp-signature
Size: 195 bytes
Desc: This is a digitally signed message part
Url : http://lists.repoforge.org/pipermail/users/attachments/20100607/732c97ae/attachment.bin

[Christoph Maser]

Post by Steve Huff

Post by Christoph Maser
As I am for a much more strict policy at rpmforge I vote for a complete
removal of perl-XML-LibXMl and perl-XML-LibXSLT or at most provide an
old version for perl-XML-LibXSLT wich works with the perl-XML-LibXML
version from base. It is much better to not have a particular piece then
to have a broken version.

Chris,
perl-XML-LibXML <= 1.69
perl-XML-LibXML-Common (bring it back from the vault)
perl-XML-LibXSLT <= 1.63
and we need Dag to remove any later versions from the repo.
if we want to roll all the way back to the versions from upstream, we
have to go back to perl-XML-LibXSLT <= 1.59 (there's already a spec
for this in SVN). for packages that are as widely used as these, i'm
OK with offering versions that replace packages from upstream, since
their absence is really crippling.
-shuff

Well as I said I am for a very strict policy. I would rather start over
and never ever package anything which is in base after the lessons
learned so far.

Post by Steve Huff
From what i see in the buildlogs/repo there never was perl-XML-LibXML

available from rpmforge before the version 1.70 and the only version for
perl-XML-LibXSLT is 1.59. So remove perl-XML-LibXM do nothing with
perl-XML-LibXML-Common (the packages are available) and we're done.

[Dag Wieers]

Post by Christoph Maser

Post by Steve Huff

Post by Christoph Maser
As I am for a much more strict policy at rpmforge I vote for a complete
removal of perl-XML-LibXMl and perl-XML-LibXSLT or at most provide an
old version for perl-XML-LibXSLT wich works with the perl-XML-LibXML
version from base. It is much better to not have a particular piece then
to have a broken version.

perl-XML-LibXML <= 1.69
perl-XML-LibXML-Common (bring it back from the vault)
perl-XML-LibXSLT <= 1.63
and we need Dag to remove any later versions from the repo.
if we want to roll all the way back to the versions from upstream, we
have to go back to perl-XML-LibXSLT <= 1.59 (there's already a spec
for this in SVN). for packages that are as widely used as these, i'm
OK with offering versions that replace packages from upstream, since
their absence is really crippling.

Well as I said I am for a very strict policy. I would rather start over
and never ever package anything which is in base after the lessons
learned so far.

Post by Steve Huff
From what i see in the buildlogs/repo there never was perl-XML-LibXML

available from rpmforge before the version 1.70 and the only version for
perl-XML-LibXSLT is 1.59. So remove perl-XML-LibXM do nothing with
perl-XML-LibXML-Common (the packages are available) and we're done.

Indeed, the change that triggered a rebuild of this package (which was
explicitely excluded) was:

http://svn.rpmforge.net/viewvc/rpmforge/trunk/rpms/perl-XML-LibXML/perl-XML-LibXML.spec?r1=8221&r2=8518

which happened very recently (1/2/2010).

In the future when something is explicitely disabled (with a description)
it's best to not change it without discussing it.

### EL4 and EL5 ship with perl-XML-LibXML 1.58
# ExcludeDist: el4 el5

I agree with Cristoph that in the future I would prefer seeing 2
repositories, one which does not replace packages, and another that
replaces packages and is consistent in itself (pulling those packages to
fullfil requirements).

[Dag Wieers]

Post by Christoph Maser

Post by Steve Huff

Post by Christoph Maser
As I am for a much more strict policy at rpmforge I vote for a complete
removal of perl-XML-LibXMl and perl-XML-LibXSLT or at most provide an
old version for perl-XML-LibXSLT wich works with the perl-XML-LibXML
version from base. It is much better to not have a particular piece then
to have a broken version.

perl-XML-LibXML <= 1.69
perl-XML-LibXML-Common (bring it back from the vault)
perl-XML-LibXSLT <= 1.63
and we need Dag to remove any later versions from the repo.
if we want to roll all the way back to the versions from upstream, we
have to go back to perl-XML-LibXSLT <= 1.59 (there's already a spec
for this in SVN). for packages that are as widely used as these, i'm
OK with offering versions that replace packages from upstream, since
their absence is really crippling.

Well as I said I am for a very strict policy. I would rather start over
and never ever package anything which is in base after the lessons
learned so far.

Post by Steve Huff
From what i see in the buildlogs/repo there never was perl-XML-LibXML

available from rpmforge before the version 1.70 and the only version for
perl-XML-LibXSLT is 1.59. So remove perl-XML-LibXM do nothing with
perl-XML-LibXML-Common (the packages are available) and we're done.

Indeed, the change that triggered a rebuild of this package (which was
explicitely excluded) was:

http://svn.rpmforge.net/viewvc/rpmforge/trunk/rpms/perl-XML-LibXML/perl-XML-LibXML.spec?r1=8221&r2=8518

which happened very recently (1/2/2010).

In the future when something is explicitely disabled (with a description)
it's best to not change it without discussing it.

### EL4 and EL5 ship with perl-XML-LibXML 1.58
# ExcludeDist: el4 el5

I agree with Cristoph that in the future I would prefer seeing 2
repositories, one which does not replace packages, and another that
replaces packages and is consistent in itself (pulling those packages to
fullfil requirements).

[Dag Wieers]

Post by Christoph Maser

Post by Steve Huff

Post by Christoph Maser
As I am for a much more strict policy at rpmforge I vote for a complete
removal of perl-XML-LibXMl and perl-XML-LibXSLT or at most provide an
old version for perl-XML-LibXSLT wich works with the perl-XML-LibXML
version from base. It is much better to not have a particular piece then
to have a broken version.

perl-XML-LibXML <= 1.69
perl-XML-LibXML-Common (bring it back from the vault)
perl-XML-LibXSLT <= 1.63
and we need Dag to remove any later versions from the repo.
if we want to roll all the way back to the versions from upstream, we
have to go back to perl-XML-LibXSLT <= 1.59 (there's already a spec
for this in SVN). for packages that are as widely used as these, i'm
OK with offering versions that replace packages from upstream, since
their absence is really crippling.

Well as I said I am for a very strict policy. I would rather start over
and never ever package anything which is in base after the lessons
learned so far.

Post by Steve Huff
From what i see in the buildlogs/repo there never was perl-XML-LibXML

available from rpmforge before the version 1.70 and the only version for
perl-XML-LibXSLT is 1.59. So remove perl-XML-LibXM do nothing with
perl-XML-LibXML-Common (the packages are available) and we're done.

Indeed, the change that triggered a rebuild of this package (which was
explicitely excluded) was:

http://svn.rpmforge.net/viewvc/rpmforge/trunk/rpms/perl-XML-LibXML/perl-XML-LibXML.spec?r1=8221&r2=8518

which happened very recently (1/2/2010).

In the future when something is explicitely disabled (with a description)
it's best to not change it without discussing it.

### EL4 and EL5 ship with perl-XML-LibXML 1.58
# ExcludeDist: el4 el5

I agree with Cristoph that in the future I would prefer seeing 2
repositories, one which does not replace packages, and another that
replaces packages and is consistent in itself (pulling those packages to
fullfil requirements).

[Dag Wieers]

Post by Christoph Maser

Post by Steve Huff

Post by Christoph Maser
As I am for a much more strict policy at rpmforge I vote for a complete
removal of perl-XML-LibXMl and perl-XML-LibXSLT or at most provide an
old version for perl-XML-LibXSLT wich works with the perl-XML-LibXML
version from base. It is much better to not have a particular piece then
to have a broken version.

perl-XML-LibXML <= 1.69
perl-XML-LibXML-Common (bring it back from the vault)
perl-XML-LibXSLT <= 1.63
and we need Dag to remove any later versions from the repo.
if we want to roll all the way back to the versions from upstream, we
have to go back to perl-XML-LibXSLT <= 1.59 (there's already a spec
for this in SVN). for packages that are as widely used as these, i'm
OK with offering versions that replace packages from upstream, since
their absence is really crippling.

Well as I said I am for a very strict policy. I would rather start over
and never ever package anything which is in base after the lessons
learned so far.

Post by Steve Huff
From what i see in the buildlogs/repo there never was perl-XML-LibXML

available from rpmforge before the version 1.70 and the only version for
perl-XML-LibXSLT is 1.59. So remove perl-XML-LibXM do nothing with
perl-XML-LibXML-Common (the packages are available) and we're done.

Indeed, the change that triggered a rebuild of this package (which was
explicitely excluded) was:

http://svn.rpmforge.net/viewvc/rpmforge/trunk/rpms/perl-XML-LibXML/perl-XML-LibXML.spec?r1=8221&r2=8518

which happened very recently (1/2/2010).

In the future when something is explicitely disabled (with a description)
it's best to not change it without discussing it.

### EL4 and EL5 ship with perl-XML-LibXML 1.58
# ExcludeDist: el4 el5

I agree with Cristoph that in the future I would prefer seeing 2
repositories, one which does not replace packages, and another that
replaces packages and is consistent in itself (pulling those packages to
fullfil requirements).

[Dag Wieers]

Post by Christoph Maser

Post by Steve Huff

Post by Christoph Maser
As I am for a much more strict policy at rpmforge I vote for a complete
removal of perl-XML-LibXMl and perl-XML-LibXSLT or at most provide an
old version for perl-XML-LibXSLT wich works with the perl-XML-LibXML
version from base. It is much better to not have a particular piece then
to have a broken version.

perl-XML-LibXML <= 1.69
perl-XML-LibXML-Common (bring it back from the vault)
perl-XML-LibXSLT <= 1.63
and we need Dag to remove any later versions from the repo.
if we want to roll all the way back to the versions from upstream, we
have to go back to perl-XML-LibXSLT <= 1.59 (there's already a spec
for this in SVN). for packages that are as widely used as these, i'm
OK with offering versions that replace packages from upstream, since
their absence is really crippling.

Well as I said I am for a very strict policy. I would rather start over
and never ever package anything which is in base after the lessons
learned so far.

Post by Steve Huff
From what i see in the buildlogs/repo there never was perl-XML-LibXML

available from rpmforge before the version 1.70 and the only version for
perl-XML-LibXSLT is 1.59. So remove perl-XML-LibXM do nothing with
perl-XML-LibXML-Common (the packages are available) and we're done.

Indeed, the change that triggered a rebuild of this package (which was
explicitely excluded) was:

http://svn.rpmforge.net/viewvc/rpmforge/trunk/rpms/perl-XML-LibXML/perl-XML-LibXML.spec?r1=8221&r2=8518

which happened very recently (1/2/2010).

In the future when something is explicitely disabled (with a description)
it's best to not change it without discussing it.

### EL4 and EL5 ship with perl-XML-LibXML 1.58
# ExcludeDist: el4 el5

I agree with Cristoph that in the future I would prefer seeing 2
repositories, one which does not replace packages, and another that
replaces packages and is consistent in itself (pulling those packages to
fullfil requirements).

[Christoph Maser]

Post by Steve Huff

Post by Christoph Maser
As I am for a much more strict policy at rpmforge I vote for a complete
removal of perl-XML-LibXMl and perl-XML-LibXSLT or at most provide an
old version for perl-XML-LibXSLT wich works with the perl-XML-LibXML
version from base. It is much better to not have a particular piece then
to have a broken version.

Chris,
perl-XML-LibXML <= 1.69
perl-XML-LibXML-Common (bring it back from the vault)
perl-XML-LibXSLT <= 1.63
and we need Dag to remove any later versions from the repo.
if we want to roll all the way back to the versions from upstream, we
have to go back to perl-XML-LibXSLT <= 1.59 (there's already a spec
for this in SVN). for packages that are as widely used as these, i'm
OK with offering versions that replace packages from upstream, since
their absence is really crippling.
-shuff

Well as I said I am for a very strict policy. I would rather start over
and never ever package anything which is in base after the lessons
learned so far.

Post by Steve Huff
From what i see in the buildlogs/repo there never was perl-XML-LibXML

available from rpmforge before the version 1.70 and the only version for
perl-XML-LibXSLT is 1.59. So remove perl-XML-LibXM do nothing with
perl-XML-LibXML-Common (the packages are available) and we're done.

[Christoph Maser]

Post by Steve Huff

Post by Christoph Maser
As I am for a much more strict policy at rpmforge I vote for a complete
removal of perl-XML-LibXMl and perl-XML-LibXSLT or at most provide an
old version for perl-XML-LibXSLT wich works with the perl-XML-LibXML
version from base. It is much better to not have a particular piece then
to have a broken version.

Chris,
perl-XML-LibXML <= 1.69
perl-XML-LibXML-Common (bring it back from the vault)
perl-XML-LibXSLT <= 1.63
and we need Dag to remove any later versions from the repo.
if we want to roll all the way back to the versions from upstream, we
have to go back to perl-XML-LibXSLT <= 1.59 (there's already a spec
for this in SVN). for packages that are as widely used as these, i'm
OK with offering versions that replace packages from upstream, since
their absence is really crippling.
-shuff

Well as I said I am for a very strict policy. I would rather start over
and never ever package anything which is in base after the lessons
learned so far.

Post by Steve Huff
From what i see in the buildlogs/repo there never was perl-XML-LibXML

available from rpmforge before the version 1.70 and the only version for
perl-XML-LibXSLT is 1.59. So remove perl-XML-LibXM do nothing with
perl-XML-LibXML-Common (the packages are available) and we're done.

[Christoph Maser]

Post by Steve Huff

Post by Christoph Maser
As I am for a much more strict policy at rpmforge I vote for a complete
removal of perl-XML-LibXMl and perl-XML-LibXSLT or at most provide an
old version for perl-XML-LibXSLT wich works with the perl-XML-LibXML
version from base. It is much better to not have a particular piece then
to have a broken version.

Chris,
perl-XML-LibXML <= 1.69
perl-XML-LibXML-Common (bring it back from the vault)
perl-XML-LibXSLT <= 1.63
and we need Dag to remove any later versions from the repo.
if we want to roll all the way back to the versions from upstream, we
have to go back to perl-XML-LibXSLT <= 1.59 (there's already a spec
for this in SVN). for packages that are as widely used as these, i'm
OK with offering versions that replace packages from upstream, since
their absence is really crippling.
-shuff

Well as I said I am for a very strict policy. I would rather start over
and never ever package anything which is in base after the lessons
learned so far.

Post by Steve Huff
From what i see in the buildlogs/repo there never was perl-XML-LibXML

available from rpmforge before the version 1.70 and the only version for
perl-XML-LibXSLT is 1.59. So remove perl-XML-LibXM do nothing with
perl-XML-LibXML-Common (the packages are available) and we're done.

[Christoph Maser]

Post by Steve Huff

Post by Christoph Maser
As I am for a much more strict policy at rpmforge I vote for a complete
removal of perl-XML-LibXMl and perl-XML-LibXSLT or at most provide an
old version for perl-XML-LibXSLT wich works with the perl-XML-LibXML
version from base. It is much better to not have a particular piece then
to have a broken version.

Chris,
perl-XML-LibXML <= 1.69
perl-XML-LibXML-Common (bring it back from the vault)
perl-XML-LibXSLT <= 1.63
and we need Dag to remove any later versions from the repo.
if we want to roll all the way back to the versions from upstream, we
have to go back to perl-XML-LibXSLT <= 1.59 (there's already a spec
for this in SVN). for packages that are as widely used as these, i'm
OK with offering versions that replace packages from upstream, since
their absence is really crippling.
-shuff

Well as I said I am for a very strict policy. I would rather start over
and never ever package anything which is in base after the lessons
learned so far.

Post by Steve Huff
From what i see in the buildlogs/repo there never was perl-XML-LibXML

available from rpmforge before the version 1.70 and the only version for
perl-XML-LibXSLT is 1.59. So remove perl-XML-LibXM do nothing with
perl-XML-LibXML-Common (the packages are available) and we're done.

[Steve Huff]

Post by Christoph Maser
As I am for a much more strict policy at rpmforge I vote for a complete
removal of perl-XML-LibXMl and perl-XML-LibXSLT or at most provide an
old version for perl-XML-LibXSLT wich works with the perl-XML-LibXML
version from base. It is much better to not have a particular piece then
to have a broken version.

Chris,

i did some digging into this (see SVN r8817), and we need at the very minimum:

perl-XML-LibXML <= 1.69
perl-XML-LibXML-Common (bring it back from the vault)
perl-XML-LibXSLT <= 1.63

and we need Dag to remove any later versions from the repo.

if we want to roll all the way back to the versions from upstream, we have to go back to perl-XML-LibXSLT <= 1.59 (there's already a spec for this in SVN). for packages that are as widely used as these, i'm OK with offering versions that replace packages from upstream, since their absence is really crippling.

-shuff

--
If this were played upon a stage now, I could condemn it as an improbable fiction. - Fabian, Twelfth Night, III,v
http://five.sentenc.es

-------------- next part --------------
A non-text attachment was scrubbed...
Name: PGP.sig
Type: application/pgp-signature
Size: 195 bytes
Desc: This is a digitally signed message part
Url : http://lists.repoforge.org/pipermail/users/attachments/20100607/732c97ae/attachment-0001.bin

[Steve Huff]

Post by Christoph Maser
As I am for a much more strict policy at rpmforge I vote for a complete
removal of perl-XML-LibXMl and perl-XML-LibXSLT or at most provide an
old version for perl-XML-LibXSLT wich works with the perl-XML-LibXML
version from base. It is much better to not have a particular piece then
to have a broken version.

Chris,

i did some digging into this (see SVN r8817), and we need at the very minimum:

perl-XML-LibXML <= 1.69
perl-XML-LibXML-Common (bring it back from the vault)
perl-XML-LibXSLT <= 1.63

and we need Dag to remove any later versions from the repo.

if we want to roll all the way back to the versions from upstream, we have to go back to perl-XML-LibXSLT <= 1.59 (there's already a spec for this in SVN). for packages that are as widely used as these, i'm OK with offering versions that replace packages from upstream, since their absence is really crippling.

-shuff

--
If this were played upon a stage now, I could condemn it as an improbable fiction. - Fabian, Twelfth Night, III,v
http://five.sentenc.es

-------------- next part --------------
A non-text attachment was scrubbed...
Name: PGP.sig
Type: application/pgp-signature
Size: 195 bytes
Desc: This is a digitally signed message part
Url : http://lists.repoforge.org/pipermail/users/attachments/20100607/732c97ae/attachment-0002.bin

[Steve Huff]

Post by Christoph Maser
As I am for a much more strict policy at rpmforge I vote for a complete
removal of perl-XML-LibXMl and perl-XML-LibXSLT or at most provide an
old version for perl-XML-LibXSLT wich works with the perl-XML-LibXML
version from base. It is much better to not have a particular piece then
to have a broken version.

Chris,

i did some digging into this (see SVN r8817), and we need at the very minimum:

perl-XML-LibXML <= 1.69
perl-XML-LibXML-Common (bring it back from the vault)
perl-XML-LibXSLT <= 1.63

and we need Dag to remove any later versions from the repo.

if we want to roll all the way back to the versions from upstream, we have to go back to perl-XML-LibXSLT <= 1.59 (there's already a spec for this in SVN). for packages that are as widely used as these, i'm OK with offering versions that replace packages from upstream, since their absence is really crippling.

-shuff

--
If this were played upon a stage now, I could condemn it as an improbable fiction. - Fabian, Twelfth Night, III,v
http://five.sentenc.es

-------------- next part --------------
A non-text attachment was scrubbed...
Name: PGP.sig
Type: application/pgp-signature
Size: 195 bytes
Desc: This is a digitally signed message part
Url : http://lists.repoforge.org/pipermail/users/attachments/20100607/732c97ae/attachment-0003.bin

[Steve Huff]

Post by Christoph Maser
As I am for a much more strict policy at rpmforge I vote for a complete
removal of perl-XML-LibXMl and perl-XML-LibXSLT or at most provide an
old version for perl-XML-LibXSLT wich works with the perl-XML-LibXML
version from base. It is much better to not have a particular piece then
to have a broken version.

Chris,

i did some digging into this (see SVN r8817), and we need at the very minimum:

perl-XML-LibXML <= 1.69
perl-XML-LibXML-Common (bring it back from the vault)
perl-XML-LibXSLT <= 1.63

and we need Dag to remove any later versions from the repo.

if we want to roll all the way back to the versions from upstream, we have to go back to perl-XML-LibXSLT <= 1.59 (there's already a spec for this in SVN). for packages that are as widely used as these, i'm OK with offering versions that replace packages from upstream, since their absence is really crippling.

-shuff

--
If this were played upon a stage now, I could condemn it as an improbable fiction. - Fabian, Twelfth Night, III,v
http://five.sentenc.es

-------------- next part --------------
A non-text attachment was scrubbed...
Name: PGP.sig
Type: application/pgp-signature
Size: 195 bytes
Desc: This is a digitally signed message part
URL: <http://lists.repoforge.org/pipermail/users/attachments/20100607/732c97ae/attachment.sig>

[Christoph Maser]

Post by David Steinbrunner

Post by David Steinbrunner
The XML::LibXSLT and XML::LibXML packages in rpmforge are currently
[Mon May 03 19:19:18 2010] [error] This version of XML::LibXSLT requires
XML::LibXML 1.6 (ABI 1), which is incompatible with currently installed
XML::LibXML 1.70 (ABI 2). Please upgrade XML::LibXSLT, XML::LibXML, or both!
at /usr/lib64/perl5/vendor_perl/5.8.8/x86_64-linux-thread-multi/XML/LibXML.pm
line 49.\nBEGIN failed--compilation aborted at
/usr/lib64/perl5/vendor_perl/5.8.8/x86_64-linux-thread-multi/XML/LibXSLT.pm
line 7.\nCompilation failed in require at
/usr/lib/perl5/site_perl/5.8.8/Album/Apache/AuthCookie.pm line 32.\nBEGIN
failed--compilation aborted at
/usr/lib/perl5/site_perl/5.8.8/Album/Apache/AuthCookie.pm line
32.\nCompilation failed in require at (eval 4) line 3.\n
The version of XML::LibXSLT that is available is 1.62 while the buildlogs show
that version 1.66 is the latest version that has tried to be built.
perl(XML::LibXML) >= 1.60 is needed by
perl-XML-LibXSLT-1.66-1.el5.rf.x86_64
This is similar to the batch of issues I pointed out on the users list with
http://lists.rpmforge.net/pipermail/users/2010-April/002963.html
http://lists.rpmforge.net/pipermail/users/2010-April/002964.html
I never saw a reply to those and it does not appear the issues have been
resolved.
In any case, it appears XML::LibXSLT version 1.70 is required to match the
version of XML::LibXML that is available. Hopefully in the process of being
built the newer XML::LibXML will be seen so the build will be successful.

The buildlogs show no change here.
I was recently talking to someone about rpmforge in general and they
mentioned this same exact issue so I'm not the only one that has run into
this, just the only one that has reported it.
--
David Steinbrunner

I had another look at this. perl-XML-LibXML is shipped in base so we
should not have it in the repo in the first place at least for RHEL5/C5.
Since there is a incomptible change in the new perl-XML-LibXML
overwriting the version from base is no option.

As I am for a much more strict policy at rpmforge I vote for a complete
removal of perl-XML-LibXMl and perl-XML-LibXSLT or at most provide an
old version for perl-XML-LibXSLT wich works with the perl-XML-LibXML
version from base. It is much better to not have a particular piece then
to have a broken version.


Chris

[Christoph Maser]

Post by David Steinbrunner

Post by David Steinbrunner
The XML::LibXSLT and XML::LibXML packages in rpmforge are currently
[Mon May 03 19:19:18 2010] [error] This version of XML::LibXSLT requires
XML::LibXML 1.6 (ABI 1), which is incompatible with currently installed
XML::LibXML 1.70 (ABI 2). Please upgrade XML::LibXSLT, XML::LibXML, or both!
at /usr/lib64/perl5/vendor_perl/5.8.8/x86_64-linux-thread-multi/XML/LibXML.pm
line 49.\nBEGIN failed--compilation aborted at
/usr/lib64/perl5/vendor_perl/5.8.8/x86_64-linux-thread-multi/XML/LibXSLT.pm
line 7.\nCompilation failed in require at
/usr/lib/perl5/site_perl/5.8.8/Album/Apache/AuthCookie.pm line 32.\nBEGIN
failed--compilation aborted at
/usr/lib/perl5/site_perl/5.8.8/Album/Apache/AuthCookie.pm line
32.\nCompilation failed in require at (eval 4) line 3.\n
The version of XML::LibXSLT that is available is 1.62 while the buildlogs show
that version 1.66 is the latest version that has tried to be built.
perl(XML::LibXML) >= 1.60 is needed by
perl-XML-LibXSLT-1.66-1.el5.rf.x86_64
This is similar to the batch of issues I pointed out on the users list with
http://lists.rpmforge.net/pipermail/users/2010-April/002963.html
http://lists.rpmforge.net/pipermail/users/2010-April/002964.html
I never saw a reply to those and it does not appear the issues have been
resolved.
In any case, it appears XML::LibXSLT version 1.70 is required to match the
version of XML::LibXML that is available. Hopefully in the process of being
built the newer XML::LibXML will be seen so the build will be successful.

The buildlogs show no change here.
I was recently talking to someone about rpmforge in general and they
mentioned this same exact issue so I'm not the only one that has run into
this, just the only one that has reported it.
--
David Steinbrunner

I had another look at this. perl-XML-LibXML is shipped in base so we
should not have it in the repo in the first place at least for RHEL5/C5.
Since there is a incomptible change in the new perl-XML-LibXML
overwriting the version from base is no option.

As I am for a much more strict policy at rpmforge I vote for a complete
removal of perl-XML-LibXMl and perl-XML-LibXSLT or at most provide an
old version for perl-XML-LibXSLT wich works with the perl-XML-LibXML
version from base. It is much better to not have a particular piece then
to have a broken version.


Chris

[Christoph Maser]

Post by David Steinbrunner

Post by David Steinbrunner
The XML::LibXSLT and XML::LibXML packages in rpmforge are currently
[Mon May 03 19:19:18 2010] [error] This version of XML::LibXSLT requires
XML::LibXML 1.6 (ABI 1), which is incompatible with currently installed
XML::LibXML 1.70 (ABI 2). Please upgrade XML::LibXSLT, XML::LibXML, or both!
at /usr/lib64/perl5/vendor_perl/5.8.8/x86_64-linux-thread-multi/XML/LibXML.pm
line 49.\nBEGIN failed--compilation aborted at
/usr/lib64/perl5/vendor_perl/5.8.8/x86_64-linux-thread-multi/XML/LibXSLT.pm
line 7.\nCompilation failed in require at
/usr/lib/perl5/site_perl/5.8.8/Album/Apache/AuthCookie.pm line 32.\nBEGIN
failed--compilation aborted at
/usr/lib/perl5/site_perl/5.8.8/Album/Apache/AuthCookie.pm line
32.\nCompilation failed in require at (eval 4) line 3.\n
The version of XML::LibXSLT that is available is 1.62 while the buildlogs show
that version 1.66 is the latest version that has tried to be built.
perl(XML::LibXML) >= 1.60 is needed by
perl-XML-LibXSLT-1.66-1.el5.rf.x86_64
This is similar to the batch of issues I pointed out on the users list with
http://lists.rpmforge.net/pipermail/users/2010-April/002963.html
http://lists.rpmforge.net/pipermail/users/2010-April/002964.html
I never saw a reply to those and it does not appear the issues have been
resolved.
In any case, it appears XML::LibXSLT version 1.70 is required to match the
version of XML::LibXML that is available. Hopefully in the process of being
built the newer XML::LibXML will be seen so the build will be successful.

The buildlogs show no change here.
I was recently talking to someone about rpmforge in general and they
mentioned this same exact issue so I'm not the only one that has run into
this, just the only one that has reported it.
--
David Steinbrunner

I had another look at this. perl-XML-LibXML is shipped in base so we
should not have it in the repo in the first place at least for RHEL5/C5.
Since there is a incomptible change in the new perl-XML-LibXML
overwriting the version from base is no option.

As I am for a much more strict policy at rpmforge I vote for a complete
removal of perl-XML-LibXMl and perl-XML-LibXSLT or at most provide an
old version for perl-XML-LibXSLT wich works with the perl-XML-LibXML
version from base. It is much better to not have a particular piece then
to have a broken version.


Chris

[Christoph Maser]

Post by David Steinbrunner

Post by David Steinbrunner
The XML::LibXSLT and XML::LibXML packages in rpmforge are currently
[Mon May 03 19:19:18 2010] [error] This version of XML::LibXSLT requires
XML::LibXML 1.6 (ABI 1), which is incompatible with currently installed
XML::LibXML 1.70 (ABI 2). Please upgrade XML::LibXSLT, XML::LibXML, or both!
at /usr/lib64/perl5/vendor_perl/5.8.8/x86_64-linux-thread-multi/XML/LibXML.pm
line 49.\nBEGIN failed--compilation aborted at
/usr/lib64/perl5/vendor_perl/5.8.8/x86_64-linux-thread-multi/XML/LibXSLT.pm
line 7.\nCompilation failed in require at
/usr/lib/perl5/site_perl/5.8.8/Album/Apache/AuthCookie.pm line 32.\nBEGIN
failed--compilation aborted at
/usr/lib/perl5/site_perl/5.8.8/Album/Apache/AuthCookie.pm line
32.\nCompilation failed in require at (eval 4) line 3.\n
The version of XML::LibXSLT that is available is 1.62 while the buildlogs show
that version 1.66 is the latest version that has tried to be built.
perl(XML::LibXML) >= 1.60 is needed by
perl-XML-LibXSLT-1.66-1.el5.rf.x86_64
This is similar to the batch of issues I pointed out on the users list with
http://lists.rpmforge.net/pipermail/users/2010-April/002963.html
http://lists.rpmforge.net/pipermail/users/2010-April/002964.html
I never saw a reply to those and it does not appear the issues have been
resolved.
In any case, it appears XML::LibXSLT version 1.70 is required to match the
version of XML::LibXML that is available. Hopefully in the process of being
built the newer XML::LibXML will be seen so the build will be successful.

The buildlogs show no change here.
I was recently talking to someone about rpmforge in general and they
mentioned this same exact issue so I'm not the only one that has run into
this, just the only one that has reported it.
--
David Steinbrunner

I had another look at this. perl-XML-LibXML is shipped in base so we
should not have it in the repo in the first place at least for RHEL5/C5.
Since there is a incomptible change in the new perl-XML-LibXML
overwriting the version from base is no option.

As I am for a much more strict policy at rpmforge I vote for a complete
removal of perl-XML-LibXMl and perl-XML-LibXSLT or at most provide an
old version for perl-XML-LibXSLT wich works with the perl-XML-LibXML
version from base. It is much better to not have a particular piece then
to have a broken version.


Chris

[David Steinbrunner]

Post by David Steinbrunner
The XML::LibXSLT and XML::LibXML packages in rpmforge are currently
[Mon May 03 19:19:18 2010] [error] This version of XML::LibXSLT requires
XML::LibXML 1.6 (ABI 1), which is incompatible with currently installed
XML::LibXML 1.70 (ABI 2). Please upgrade XML::LibXSLT, XML::LibXML, or both!
at /usr/lib64/perl5/vendor_perl/5.8.8/x86_64-linux-thread-multi/XML/LibXML.pm
line 49.\nBEGIN failed--compilation aborted at
/usr/lib64/perl5/vendor_perl/5.8.8/x86_64-linux-thread-multi/XML/LibXSLT.pm
line 7.\nCompilation failed in require at
/usr/lib/perl5/site_perl/5.8.8/Album/Apache/AuthCookie.pm line 32.\nBEGIN
failed--compilation aborted at
/usr/lib/perl5/site_perl/5.8.8/Album/Apache/AuthCookie.pm line
32.\nCompilation failed in require at (eval 4) line 3.\n
The version of XML::LibXSLT that is available is 1.62 while the buildlogs show
that version 1.66 is the latest version that has tried to be built.
perl(XML::LibXML) >= 1.60 is needed by
perl-XML-LibXSLT-1.66-1.el5.rf.x86_64
This is similar to the batch of issues I pointed out on the users list with
http://lists.rpmforge.net/pipermail/users/2010-April/002963.html
http://lists.rpmforge.net/pipermail/users/2010-April/002964.html
I never saw a reply to those and it does not appear the issues have been
resolved.
In any case, it appears XML::LibXSLT version 1.70 is required to match the
version of XML::LibXML that is available. Hopefully in the process of being
built the newer XML::LibXML will be seen so the build will be successful.

The buildlogs show no change here.

I was recently talking to someone about rpmforge in general and they
mentioned this same exact issue so I'm not the only one that has run into
this, just the only one that has reported it.

--
David Steinbrunner

[David Steinbrunner]

Post by David Steinbrunner
The XML::LibXSLT and XML::LibXML packages in rpmforge are currently
[Mon May 03 19:19:18 2010] [error] This version of XML::LibXSLT requires
XML::LibXML 1.6 (ABI 1), which is incompatible with currently installed
XML::LibXML 1.70 (ABI 2). Please upgrade XML::LibXSLT, XML::LibXML, or both!
at /usr/lib64/perl5/vendor_perl/5.8.8/x86_64-linux-thread-multi/XML/LibXML.pm
line 49.\nBEGIN failed--compilation aborted at
/usr/lib64/perl5/vendor_perl/5.8.8/x86_64-linux-thread-multi/XML/LibXSLT.pm
line 7.\nCompilation failed in require at
/usr/lib/perl5/site_perl/5.8.8/Album/Apache/AuthCookie.pm line 32.\nBEGIN
failed--compilation aborted at
/usr/lib/perl5/site_perl/5.8.8/Album/Apache/AuthCookie.pm line
32.\nCompilation failed in require at (eval 4) line 3.\n
The version of XML::LibXSLT that is available is 1.62 while the buildlogs show
that version 1.66 is the latest version that has tried to be built.
perl(XML::LibXML) >= 1.60 is needed by
perl-XML-LibXSLT-1.66-1.el5.rf.x86_64
This is similar to the batch of issues I pointed out on the users list with
http://lists.rpmforge.net/pipermail/users/2010-April/002963.html
http://lists.rpmforge.net/pipermail/users/2010-April/002964.html
I never saw a reply to those and it does not appear the issues have been
resolved.
In any case, it appears XML::LibXSLT version 1.70 is required to match the
version of XML::LibXML that is available. Hopefully in the process of being
built the newer XML::LibXML will be seen so the build will be successful.

The buildlogs show no change here.

I was recently talking to someone about rpmforge in general and they
mentioned this same exact issue so I'm not the only one that has run into
this, just the only one that has reported it.

--
David Steinbrunner

[David Steinbrunner]

Post by David Steinbrunner
The XML::LibXSLT and XML::LibXML packages in rpmforge are currently
[Mon May 03 19:19:18 2010] [error] This version of XML::LibXSLT requires
XML::LibXML 1.6 (ABI 1), which is incompatible with currently installed
XML::LibXML 1.70 (ABI 2). Please upgrade XML::LibXSLT, XML::LibXML, or both!
at /usr/lib64/perl5/vendor_perl/5.8.8/x86_64-linux-thread-multi/XML/LibXML.pm
line 49.\nBEGIN failed--compilation aborted at
/usr/lib64/perl5/vendor_perl/5.8.8/x86_64-linux-thread-multi/XML/LibXSLT.pm
line 7.\nCompilation failed in require at
/usr/lib/perl5/site_perl/5.8.8/Album/Apache/AuthCookie.pm line 32.\nBEGIN
failed--compilation aborted at
/usr/lib/perl5/site_perl/5.8.8/Album/Apache/AuthCookie.pm line
32.\nCompilation failed in require at (eval 4) line 3.\n
The version of XML::LibXSLT that is available is 1.62 while the buildlogs show
that version 1.66 is the latest version that has tried to be built.
perl(XML::LibXML) >= 1.60 is needed by
perl-XML-LibXSLT-1.66-1.el5.rf.x86_64
This is similar to the batch of issues I pointed out on the users list with
http://lists.rpmforge.net/pipermail/users/2010-April/002963.html
http://lists.rpmforge.net/pipermail/users/2010-April/002964.html
I never saw a reply to those and it does not appear the issues have been
resolved.
In any case, it appears XML::LibXSLT version 1.70 is required to match the
version of XML::LibXML that is available. Hopefully in the process of being
built the newer XML::LibXML will be seen so the build will be successful.

The buildlogs show no change here.

I was recently talking to someone about rpmforge in general and they
mentioned this same exact issue so I'm not the only one that has run into
this, just the only one that has reported it.

--
David Steinbrunner

[David Steinbrunner]

Post by David Steinbrunner
The XML::LibXSLT and XML::LibXML packages in rpmforge are currently
[Mon May 03 19:19:18 2010] [error] This version of XML::LibXSLT requires
XML::LibXML 1.6 (ABI 1), which is incompatible with currently installed
XML::LibXML 1.70 (ABI 2). Please upgrade XML::LibXSLT, XML::LibXML, or both!
at /usr/lib64/perl5/vendor_perl/5.8.8/x86_64-linux-thread-multi/XML/LibXML.pm
line 49.\nBEGIN failed--compilation aborted at
/usr/lib64/perl5/vendor_perl/5.8.8/x86_64-linux-thread-multi/XML/LibXSLT.pm
line 7.\nCompilation failed in require at
/usr/lib/perl5/site_perl/5.8.8/Album/Apache/AuthCookie.pm line 32.\nBEGIN
failed--compilation aborted at
/usr/lib/perl5/site_perl/5.8.8/Album/Apache/AuthCookie.pm line
32.\nCompilation failed in require at (eval 4) line 3.\n
The version of XML::LibXSLT that is available is 1.62 while the buildlogs show
that version 1.66 is the latest version that has tried to be built.
perl(XML::LibXML) >= 1.60 is needed by
perl-XML-LibXSLT-1.66-1.el5.rf.x86_64
This is similar to the batch of issues I pointed out on the users list with
http://lists.rpmforge.net/pipermail/users/2010-April/002963.html
http://lists.rpmforge.net/pipermail/users/2010-April/002964.html
I never saw a reply to those and it does not appear the issues have been
resolved.
In any case, it appears XML::LibXSLT version 1.70 is required to match the
version of XML::LibXML that is available. Hopefully in the process of being
built the newer XML::LibXML will be seen so the build will be successful.

The buildlogs show no change here.

I was recently talking to someone about rpmforge in general and they
mentioned this same exact issue so I'm not the only one that has run into
this, just the only one that has reported it.

--
David Steinbrunner