[users] dropbox package severely broken

[Robin Bowes]

Hi,

I did a fresh install of CentOS 5.4 using cobbler with a mirror of
RPMForge enabled, and I've found that the dropbox package [1] is pulled
in as a dependency.

In short, it looks like the autoreqprov is detecting all the binaries in
the package and producing a crazy "Provides" list.

Rebuilding the RPM from the Spec file with 'AutoReqProv: no' fixes it.

In the meantime, the current package (dated May 2) should be pulled from
the repo - it breaks thing.

R.

[Robin Bowes]

Post by Robin Bowes
Hi,
I did a fresh install of CentOS 5.4 using cobbler with a mirror of
RPMForge enabled, and I've found that the dropbox package [1] is pulled
in as a dependency.

[1] http://packages.sw.be/dropbox/dropbox-0.7.110-1.el5.rf.x86_64.rpm

[Steve Huff]

Post by Robin Bowes
Rebuilding the RPM from the Spec file with 'AutoReqProv: no' fixes it.
In the meantime, the current package (dated May 2) should be pulled from
the repo - it breaks thing.

thanks for your report, Robin; i've committed the change in SVN, and it'll be fixed in the next rebuild. i don't have the necessary access to pull the package from the repo, though, so in the interim you should use a yum exclude to work around the issue.

-steve
--
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/20100510/f41be680/attachment.bin

[Dag Wieers]

Post by Steve Huff

Post by Robin Bowes
Rebuilding the RPM from the Spec file with 'AutoReqProv: no' fixes it.
In the meantime, the current package (dated May 2) should be pulled from
the repo - it breaks thing.

thanks for your report, Robin; i've committed the change in SVN, and
it'll be fixed in the next rebuild. i don't have the necessary access
to pull the package from the repo, though, so in the interim you should
use a yum exclude to work around the issue.

I have made a rebuild which will only be available in 24 hours, but I
looked at the package and I don't like it. Libraries should not go in
/usr/libexec/dropbox and the python eggdrops should not be tagged as build
against python 2.5 on RHEL5.

Did anyone look at the license for redistributing dropbox ?

[Robin Bowes]

Post by Dag Wieers

Post by Steve Huff

Post by Robin Bowes
Rebuilding the RPM from the Spec file with 'AutoReqProv: no' fixes it.
In the meantime, the current package (dated May 2) should be pulled from
the repo - it breaks thing.

thanks for your report, Robin; i've committed the change in SVN, and
it'll be fixed in the next rebuild. i don't have the necessary access
to pull the package from the repo, though, so in the interim you
should use a yum exclude to work around the issue.

I have made a rebuild which will only be available in 24 hours, but I
looked at the package and I don't like it. Libraries should not go in
/usr/libexec/dropbox and the python eggdrops should not be tagged as
build against python 2.5 on RHEL5.
Did anyone look at the license for redistributing dropbox ?

My main problem with this package was that I didn't actually choose to
install it at all - it got pulled in to a fresh kickstart install
(cobbler, with RPMForge repo enabled) because of all the duplicate
binary libraries that are bundled with it. Basically, those libraries
shouldn't be bundled, they should be added as a dependencies to the RPM
so the official packages are used.

R.

[Christoph Maser]

Post by Robin Bowes
My main problem with this package was that I didn't actually choose to
install it at all - it got pulled in to a fresh kickstart install
(cobbler, with RPMForge repo enabled) because of all the duplicate
binary libraries that are bundled with it. Basically, those libraries
shouldn't be bundled, they should be added as a dependencies to the RPM
so the official packages are used.
R.

You really should not use rpmforge at install time since anaconda does
not support repository protection/priorities. Actually I have the
opinion that one should not use rpmforge repo directly at all but
instead cherry pick stuff you need in your own in-house repo.

Chris

[Dag Wieers]

Post by Robin Bowes

Post by Dag Wieers

Post by Steve Huff

Post by Robin Bowes
Rebuilding the RPM from the Spec file with 'AutoReqProv: no' fixes it.
In the meantime, the current package (dated May 2) should be pulled from
the repo - it breaks thing.

thanks for your report, Robin; i've committed the change in SVN, and
it'll be fixed in the next rebuild. i don't have the necessary access
to pull the package from the repo, though, so in the interim you
should use a yum exclude to work around the issue.

I have made a rebuild which will only be available in 24 hours, but I
looked at the package and I don't like it. Libraries should not go in
/usr/libexec/dropbox and the python eggdrops should not be tagged as
build against python 2.5 on RHEL5.
Did anyone look at the license for redistributing dropbox ?

My main problem with this package was that I didn't actually choose to
install it at all - it got pulled in to a fresh kickstart install
(cobbler, with RPMForge repo enabled) because of all the duplicate
binary libraries that are bundled with it. Basically, those libraries
shouldn't be bundled, they should be added as a dependencies to the RPM
so the official packages are used.

That it is a bad package requires no further explanation :-)

[Christoph Maser]

Post by Robin Bowes
My main problem with this package was that I didn't actually choose to
install it at all - it got pulled in to a fresh kickstart install
(cobbler, with RPMForge repo enabled) because of all the duplicate
binary libraries that are bundled with it. Basically, those libraries
shouldn't be bundled, they should be added as a dependencies to the RPM
so the official packages are used.
R.

You really should not use rpmforge at install time since anaconda does
not support repository protection/priorities. Actually I have the
opinion that one should not use rpmforge repo directly at all but
instead cherry pick stuff you need in your own in-house repo.

Chris

[Dag Wieers]

Post by Robin Bowes

Post by Dag Wieers

Post by Steve Huff

Post by Robin Bowes
Rebuilding the RPM from the Spec file with 'AutoReqProv: no' fixes it.
In the meantime, the current package (dated May 2) should be pulled from
the repo - it breaks thing.

thanks for your report, Robin; i've committed the change in SVN, and
it'll be fixed in the next rebuild. i don't have the necessary access
to pull the package from the repo, though, so in the interim you
should use a yum exclude to work around the issue.

I have made a rebuild which will only be available in 24 hours, but I
looked at the package and I don't like it. Libraries should not go in
/usr/libexec/dropbox and the python eggdrops should not be tagged as
build against python 2.5 on RHEL5.
Did anyone look at the license for redistributing dropbox ?

My main problem with this package was that I didn't actually choose to
install it at all - it got pulled in to a fresh kickstart install
(cobbler, with RPMForge repo enabled) because of all the duplicate
binary libraries that are bundled with it. Basically, those libraries
shouldn't be bundled, they should be added as a dependencies to the RPM
so the official packages are used.

That it is a bad package requires no further explanation :-)

[Christoph Maser]

Post by Robin Bowes
My main problem with this package was that I didn't actually choose to
install it at all - it got pulled in to a fresh kickstart install
(cobbler, with RPMForge repo enabled) because of all the duplicate
binary libraries that are bundled with it. Basically, those libraries
shouldn't be bundled, they should be added as a dependencies to the RPM
so the official packages are used.
R.

You really should not use rpmforge at install time since anaconda does
not support repository protection/priorities. Actually I have the
opinion that one should not use rpmforge repo directly at all but
instead cherry pick stuff you need in your own in-house repo.

Chris

[Dag Wieers]

Post by Robin Bowes

Post by Dag Wieers

Post by Steve Huff

Post by Robin Bowes
Rebuilding the RPM from the Spec file with 'AutoReqProv: no' fixes it.
In the meantime, the current package (dated May 2) should be pulled from
the repo - it breaks thing.

thanks for your report, Robin; i've committed the change in SVN, and
it'll be fixed in the next rebuild. i don't have the necessary access
to pull the package from the repo, though, so in the interim you
should use a yum exclude to work around the issue.

I have made a rebuild which will only be available in 24 hours, but I
looked at the package and I don't like it. Libraries should not go in
/usr/libexec/dropbox and the python eggdrops should not be tagged as
build against python 2.5 on RHEL5.
Did anyone look at the license for redistributing dropbox ?

My main problem with this package was that I didn't actually choose to
install it at all - it got pulled in to a fresh kickstart install
(cobbler, with RPMForge repo enabled) because of all the duplicate
binary libraries that are bundled with it. Basically, those libraries
shouldn't be bundled, they should be added as a dependencies to the RPM
so the official packages are used.

That it is a bad package requires no further explanation :-)

[Christoph Maser]

Post by Robin Bowes
My main problem with this package was that I didn't actually choose to
install it at all - it got pulled in to a fresh kickstart install
(cobbler, with RPMForge repo enabled) because of all the duplicate
binary libraries that are bundled with it. Basically, those libraries
shouldn't be bundled, they should be added as a dependencies to the RPM
so the official packages are used.
R.

You really should not use rpmforge at install time since anaconda does
not support repository protection/priorities. Actually I have the
opinion that one should not use rpmforge repo directly at all but
instead cherry pick stuff you need in your own in-house repo.

Chris

[Dag Wieers]

Post by Robin Bowes

Post by Dag Wieers

Post by Steve Huff

Post by Robin Bowes
Rebuilding the RPM from the Spec file with 'AutoReqProv: no' fixes it.
In the meantime, the current package (dated May 2) should be pulled from
the repo - it breaks thing.

thanks for your report, Robin; i've committed the change in SVN, and
it'll be fixed in the next rebuild. i don't have the necessary access
to pull the package from the repo, though, so in the interim you
should use a yum exclude to work around the issue.

I have made a rebuild which will only be available in 24 hours, but I
looked at the package and I don't like it. Libraries should not go in
/usr/libexec/dropbox and the python eggdrops should not be tagged as
build against python 2.5 on RHEL5.
Did anyone look at the license for redistributing dropbox ?

My main problem with this package was that I didn't actually choose to
install it at all - it got pulled in to a fresh kickstart install
(cobbler, with RPMForge repo enabled) because of all the duplicate
binary libraries that are bundled with it. Basically, those libraries
shouldn't be bundled, they should be added as a dependencies to the RPM
so the official packages are used.

That it is a bad package requires no further explanation :-)

[Christoph Maser]

Post by Robin Bowes
My main problem with this package was that I didn't actually choose to
install it at all - it got pulled in to a fresh kickstart install
(cobbler, with RPMForge repo enabled) because of all the duplicate
binary libraries that are bundled with it. Basically, those libraries
shouldn't be bundled, they should be added as a dependencies to the RPM
so the official packages are used.
R.

You really should not use rpmforge at install time since anaconda does
not support repository protection/priorities. Actually I have the
opinion that one should not use rpmforge repo directly at all but
instead cherry pick stuff you need in your own in-house repo.

Chris

[Dag Wieers]

Post by Robin Bowes

Post by Dag Wieers

Post by Steve Huff

Post by Robin Bowes
Rebuilding the RPM from the Spec file with 'AutoReqProv: no' fixes it.
In the meantime, the current package (dated May 2) should be pulled from
the repo - it breaks thing.

thanks for your report, Robin; i've committed the change in SVN, and
it'll be fixed in the next rebuild. i don't have the necessary access
to pull the package from the repo, though, so in the interim you
should use a yum exclude to work around the issue.

I have made a rebuild which will only be available in 24 hours, but I
looked at the package and I don't like it. Libraries should not go in
/usr/libexec/dropbox and the python eggdrops should not be tagged as
build against python 2.5 on RHEL5.
Did anyone look at the license for redistributing dropbox ?

My main problem with this package was that I didn't actually choose to
install it at all - it got pulled in to a fresh kickstart install
(cobbler, with RPMForge repo enabled) because of all the duplicate
binary libraries that are bundled with it. Basically, those libraries
shouldn't be bundled, they should be added as a dependencies to the RPM
so the official packages are used.

That it is a bad package requires no further explanation :-)

[Robin Bowes]

Post by Dag Wieers

Post by Steve Huff

Post by Robin Bowes
Rebuilding the RPM from the Spec file with 'AutoReqProv: no' fixes it.
In the meantime, the current package (dated May 2) should be pulled from
the repo - it breaks thing.

thanks for your report, Robin; i've committed the change in SVN, and
it'll be fixed in the next rebuild. i don't have the necessary access
to pull the package from the repo, though, so in the interim you
should use a yum exclude to work around the issue.

I have made a rebuild which will only be available in 24 hours, but I
looked at the package and I don't like it. Libraries should not go in
/usr/libexec/dropbox and the python eggdrops should not be tagged as
build against python 2.5 on RHEL5.
Did anyone look at the license for redistributing dropbox ?

My main problem with this package was that I didn't actually choose to
install it at all - it got pulled in to a fresh kickstart install
(cobbler, with RPMForge repo enabled) because of all the duplicate
binary libraries that are bundled with it. Basically, those libraries
shouldn't be bundled, they should be added as a dependencies to the RPM
so the official packages are used.

R.

[Robin Bowes]

Post by Dag Wieers

Post by Steve Huff

Post by Robin Bowes
Rebuilding the RPM from the Spec file with 'AutoReqProv: no' fixes it.
In the meantime, the current package (dated May 2) should be pulled from
the repo - it breaks thing.

thanks for your report, Robin; i've committed the change in SVN, and
it'll be fixed in the next rebuild. i don't have the necessary access
to pull the package from the repo, though, so in the interim you
should use a yum exclude to work around the issue.

I have made a rebuild which will only be available in 24 hours, but I
looked at the package and I don't like it. Libraries should not go in
/usr/libexec/dropbox and the python eggdrops should not be tagged as
build against python 2.5 on RHEL5.
Did anyone look at the license for redistributing dropbox ?

My main problem with this package was that I didn't actually choose to
install it at all - it got pulled in to a fresh kickstart install
(cobbler, with RPMForge repo enabled) because of all the duplicate
binary libraries that are bundled with it. Basically, those libraries
shouldn't be bundled, they should be added as a dependencies to the RPM
so the official packages are used.

R.

[Robin Bowes]

Post by Dag Wieers

Post by Steve Huff

Post by Robin Bowes
Rebuilding the RPM from the Spec file with 'AutoReqProv: no' fixes it.
In the meantime, the current package (dated May 2) should be pulled from
the repo - it breaks thing.

thanks for your report, Robin; i've committed the change in SVN, and
it'll be fixed in the next rebuild. i don't have the necessary access
to pull the package from the repo, though, so in the interim you
should use a yum exclude to work around the issue.

I have made a rebuild which will only be available in 24 hours, but I
looked at the package and I don't like it. Libraries should not go in
/usr/libexec/dropbox and the python eggdrops should not be tagged as
build against python 2.5 on RHEL5.
Did anyone look at the license for redistributing dropbox ?

My main problem with this package was that I didn't actually choose to
install it at all - it got pulled in to a fresh kickstart install
(cobbler, with RPMForge repo enabled) because of all the duplicate
binary libraries that are bundled with it. Basically, those libraries
shouldn't be bundled, they should be added as a dependencies to the RPM
so the official packages are used.

R.

[Robin Bowes]

Post by Dag Wieers

Post by Steve Huff

Post by Robin Bowes
Rebuilding the RPM from the Spec file with 'AutoReqProv: no' fixes it.
In the meantime, the current package (dated May 2) should be pulled from
the repo - it breaks thing.

thanks for your report, Robin; i've committed the change in SVN, and
it'll be fixed in the next rebuild. i don't have the necessary access
to pull the package from the repo, though, so in the interim you
should use a yum exclude to work around the issue.

I have made a rebuild which will only be available in 24 hours, but I
looked at the package and I don't like it. Libraries should not go in
/usr/libexec/dropbox and the python eggdrops should not be tagged as
build against python 2.5 on RHEL5.
Did anyone look at the license for redistributing dropbox ?

My main problem with this package was that I didn't actually choose to
install it at all - it got pulled in to a fresh kickstart install
(cobbler, with RPMForge repo enabled) because of all the duplicate
binary libraries that are bundled with it. Basically, those libraries
shouldn't be bundled, they should be added as a dependencies to the RPM
so the official packages are used.

R.

[Dag Wieers]

Post by Steve Huff

Post by Robin Bowes
Rebuilding the RPM from the Spec file with 'AutoReqProv: no' fixes it.
In the meantime, the current package (dated May 2) should be pulled from
the repo - it breaks thing.

thanks for your report, Robin; i've committed the change in SVN, and
it'll be fixed in the next rebuild. i don't have the necessary access
to pull the package from the repo, though, so in the interim you should
use a yum exclude to work around the issue.

I have made a rebuild which will only be available in 24 hours, but I
looked at the package and I don't like it. Libraries should not go in
/usr/libexec/dropbox and the python eggdrops should not be tagged as build
against python 2.5 on RHEL5.

Did anyone look at the license for redistributing dropbox ?

[Dag Wieers]

Post by Steve Huff

Post by Robin Bowes
Rebuilding the RPM from the Spec file with 'AutoReqProv: no' fixes it.
In the meantime, the current package (dated May 2) should be pulled from
the repo - it breaks thing.

thanks for your report, Robin; i've committed the change in SVN, and
it'll be fixed in the next rebuild. i don't have the necessary access
to pull the package from the repo, though, so in the interim you should
use a yum exclude to work around the issue.

I have made a rebuild which will only be available in 24 hours, but I
looked at the package and I don't like it. Libraries should not go in
/usr/libexec/dropbox and the python eggdrops should not be tagged as build
against python 2.5 on RHEL5.

Did anyone look at the license for redistributing dropbox ?

[Dag Wieers]

Post by Steve Huff

Post by Robin Bowes
Rebuilding the RPM from the Spec file with 'AutoReqProv: no' fixes it.
In the meantime, the current package (dated May 2) should be pulled from
the repo - it breaks thing.

thanks for your report, Robin; i've committed the change in SVN, and
it'll be fixed in the next rebuild. i don't have the necessary access
to pull the package from the repo, though, so in the interim you should
use a yum exclude to work around the issue.

I have made a rebuild which will only be available in 24 hours, but I
looked at the package and I don't like it. Libraries should not go in
/usr/libexec/dropbox and the python eggdrops should not be tagged as build
against python 2.5 on RHEL5.

Did anyone look at the license for redistributing dropbox ?

[Dag Wieers]

Post by Steve Huff

Post by Robin Bowes
Rebuilding the RPM from the Spec file with 'AutoReqProv: no' fixes it.
In the meantime, the current package (dated May 2) should be pulled from
the repo - it breaks thing.

thanks for your report, Robin; i've committed the change in SVN, and
it'll be fixed in the next rebuild. i don't have the necessary access
to pull the package from the repo, though, so in the interim you should
use a yum exclude to work around the issue.

I have made a rebuild which will only be available in 24 hours, but I
looked at the package and I don't like it. Libraries should not go in
/usr/libexec/dropbox and the python eggdrops should not be tagged as build
against python 2.5 on RHEL5.

Did anyone look at the license for redistributing dropbox ?

[Robin Bowes]

Hi,

I did a fresh install of CentOS 5.4 using cobbler with a mirror of
RPMForge enabled, and I've found that the dropbox package [1] is pulled
in as a dependency.

In short, it looks like the autoreqprov is detecting all the binaries in
the package and producing a crazy "Provides" list.

Rebuilding the RPM from the Spec file with 'AutoReqProv: no' fixes it.

In the meantime, the current package (dated May 2) should be pulled from
the repo - it breaks thing.

R.

[Robin Bowes]

Post by Robin Bowes
Hi,
I did a fresh install of CentOS 5.4 using cobbler with a mirror of
RPMForge enabled, and I've found that the dropbox package [1] is pulled
in as a dependency.

[1] http://packages.sw.be/dropbox/dropbox-0.7.110-1.el5.rf.x86_64.rpm

[Steve Huff]

Post by Robin Bowes
Rebuilding the RPM from the Spec file with 'AutoReqProv: no' fixes it.
In the meantime, the current package (dated May 2) should be pulled from
the repo - it breaks thing.

thanks for your report, Robin; i've committed the change in SVN, and it'll be fixed in the next rebuild. i don't have the necessary access to pull the package from the repo, though, so in the interim you should use a yum exclude to work around the issue.

-steve
--
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/20100510/f41be680/attachment-0001.bin

[Robin Bowes]

Hi,

I did a fresh install of CentOS 5.4 using cobbler with a mirror of
RPMForge enabled, and I've found that the dropbox package [1] is pulled
in as a dependency.

In short, it looks like the autoreqprov is detecting all the binaries in
the package and producing a crazy "Provides" list.

Rebuilding the RPM from the Spec file with 'AutoReqProv: no' fixes it.

In the meantime, the current package (dated May 2) should be pulled from
the repo - it breaks thing.

R.

[Robin Bowes]

Post by Robin Bowes
Hi,
I did a fresh install of CentOS 5.4 using cobbler with a mirror of
RPMForge enabled, and I've found that the dropbox package [1] is pulled
in as a dependency.

[1] http://packages.sw.be/dropbox/dropbox-0.7.110-1.el5.rf.x86_64.rpm

[Steve Huff]

Post by Robin Bowes
Rebuilding the RPM from the Spec file with 'AutoReqProv: no' fixes it.
In the meantime, the current package (dated May 2) should be pulled from
the repo - it breaks thing.

thanks for your report, Robin; i've committed the change in SVN, and it'll be fixed in the next rebuild. i don't have the necessary access to pull the package from the repo, though, so in the interim you should use a yum exclude to work around the issue.

-steve
--
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/20100510/f41be680/attachment-0002.bin

[Robin Bowes]

Hi,

I did a fresh install of CentOS 5.4 using cobbler with a mirror of
RPMForge enabled, and I've found that the dropbox package [1] is pulled
in as a dependency.

In short, it looks like the autoreqprov is detecting all the binaries in
the package and producing a crazy "Provides" list.

Rebuilding the RPM from the Spec file with 'AutoReqProv: no' fixes it.

In the meantime, the current package (dated May 2) should be pulled from
the repo - it breaks thing.

R.

[Robin Bowes]

Post by Robin Bowes
Hi,
I did a fresh install of CentOS 5.4 using cobbler with a mirror of
RPMForge enabled, and I've found that the dropbox package [1] is pulled
in as a dependency.

[1] http://packages.sw.be/dropbox/dropbox-0.7.110-1.el5.rf.x86_64.rpm

[Steve Huff]

Post by Robin Bowes
Rebuilding the RPM from the Spec file with 'AutoReqProv: no' fixes it.
In the meantime, the current package (dated May 2) should be pulled from
the repo - it breaks thing.

thanks for your report, Robin; i've committed the change in SVN, and it'll be fixed in the next rebuild. i don't have the necessary access to pull the package from the repo, though, so in the interim you should use a yum exclude to work around the issue.

-steve
--
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/20100510/f41be680/attachment-0003.bin

[Robin Bowes]

Hi,

I did a fresh install of CentOS 5.4 using cobbler with a mirror of
RPMForge enabled, and I've found that the dropbox package [1] is pulled
in as a dependency.

In short, it looks like the autoreqprov is detecting all the binaries in
the package and producing a crazy "Provides" list.

Rebuilding the RPM from the Spec file with 'AutoReqProv: no' fixes it.

In the meantime, the current package (dated May 2) should be pulled from
the repo - it breaks thing.

R.

[Robin Bowes]

Post by Robin Bowes
Hi,
I did a fresh install of CentOS 5.4 using cobbler with a mirror of
RPMForge enabled, and I've found that the dropbox package [1] is pulled
in as a dependency.

[1] http://packages.sw.be/dropbox/dropbox-0.7.110-1.el5.rf.x86_64.rpm

[Steve Huff]

Post by Robin Bowes
Rebuilding the RPM from the Spec file with 'AutoReqProv: no' fixes it.
In the meantime, the current package (dated May 2) should be pulled from
the repo - it breaks thing.

thanks for your report, Robin; i've committed the change in SVN, and it'll be fixed in the next rebuild. i don't have the necessary access to pull the package from the repo, though, so in the interim you should use a yum exclude to work around the issue.

-steve
--
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/20100510/f41be680/attachment.sig>