[suggest] broken dependencies for some perl modules on RHEL4

[Peter J. Holzer]

[Resent because it was rejected because I used a wrong sender address -
apologies if this turns up twice]

Several perl modules have broken dependencies on rhel4.

For example:

perl-DBD-Pg-2.17.1-1.el4.rf requires perl >= 5.006001
perl-Module-Build-0.3603-1.el4.rf requires perl >= 5.006001
perl-Regexp-Common-2010010201-1.el4.rf requires perl >= 5.00473

However, RHEL4 uses a different numbering scheme:

rpm -q --provides perl
...
perl = 4:5.8.8-2.el4s1

and 4:5.8.8 apparently isn't greater than 5.006001, although it should
be (5.8.8 is 5.008008 in the perl world, but of course RPM cannot know
this).

The culprit seems to be an explicit Requires line in the spec files
which was added a few months ago. Given that 5.006001 is very old and
5.00473 is ancient and older versions were never installed on any RHEL
still supported by rpmforge, these Requires lines could probably be
safely omitted.

I also noted that the SRPM for perl-DBD-Pg-2.17 (didn't look at the
others) now has "el5" in the name. Maybe that was intended only for
RHEL5 and built for the other versions by mistake?

hp
--
_ | Peter J. Holzer | Auf jedem Computer sollte der Satz Ludwigs II
|_|_) | Sysadmin WSR | eingepr?gt stehen: "Ein ewig R?tsel will ich
| | | hjp at wsr.ac.at | bleiben, mir und andern."
__/ | http://www.hjp.at/ | -- Wolfram Heinrich in desd
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://lists.repoforge.org/pipermail/users/attachments/20100607/fedd300c/attachment.bin

[Christoph Maser]

Thanks for reporting Peter. This happens as I replace autogernerated
dependecies by rpmbuild through autogenerated dependencies from CPAN
metadata. I will have a look at it.

Chris

Post by Peter J. Holzer
[Resent because it was rejected because I used a wrong sender address -
apologies if this turns up twice]
Several perl modules have broken dependencies on rhel4.
perl-DBD-Pg-2.17.1-1.el4.rf requires perl >= 5.006001
perl-Module-Build-0.3603-1.el4.rf requires perl >= 5.006001
perl-Regexp-Common-2010010201-1.el4.rf requires perl >= 5.00473
rpm -q --provides perl
...
perl = 4:5.8.8-2.el4s1
and 4:5.8.8 apparently isn't greater than 5.006001, although it should
be (5.8.8 is 5.008008 in the perl world, but of course RPM cannot know
this).
The culprit seems to be an explicit Requires line in the spec files
which was added a few months ago. Given that 5.006001 is very old and
5.00473 is ancient and older versions were never installed on any RHEL
still supported by rpmforge, these Requires lines could probably be
safely omitted.
I also noted that the SRPM for perl-DBD-Pg-2.17 (didn't look at the
others) now has "el5" in the name. Maybe that was intended only for
RHEL5 and built for the other versions by mistake?
hp
_______________________________________________
suggest mailing list
suggest at lists.rpmforge.net
http://lists.rpmforge.net/mailman/listinfo/suggest

[Christoph Maser]

Post by Peter J. Holzer
[Resent because it was rejected because I used a wrong sender address -
apologies if this turns up twice]
Several perl modules have broken dependencies on rhel4.
perl-DBD-Pg-2.17.1-1.el4.rf requires perl >= 5.006001
perl-Module-Build-0.3603-1.el4.rf requires perl >= 5.006001
perl-Regexp-Common-2010010201-1.el4.rf requires perl >= 5.00473
rpm -q --provides perl
...
perl = 4:5.8.8-2.el4s1

Actually it seems you are wrong


yum provides "perl >= 5.006001" gives me this:

perl.x86_64 3:5.8.5-49.el4
base
Matched from:
perl >= 5.006001


Also installing those modules went just fine for me. What exactly is the
problem you are having?

[Peter J. Holzer]

Post by Christoph Maser

Post by Peter J. Holzer
Several perl modules have broken dependencies on rhel4.
perl-DBD-Pg-2.17.1-1.el4.rf requires perl >= 5.006001
perl-Module-Build-0.3603-1.el4.rf requires perl >= 5.006001
perl-Regexp-Common-2010010201-1.el4.rf requires perl >= 5.00473
rpm -q --provides perl
...
perl = 4:5.8.8-2.el4s1

Actually it seems you are wrong

I use up2date, not yum. Can yum access the Redhat repository on RHEL 4?
I never checked, but that might be a good opportunity to switch from
up2date to yum on the older redhat boxes.

Post by Christoph Maser
perl.x86_64 3:5.8.5-49.el4

I have perl = 4:5.8.8-2.el4s1 (from the rhel-x86_64-as-4-webapp-1-beta
channel), but that's an even higher version number, so if 3:5.8.5 is
good enough, 4:5.8.8 should work, too.

Post by Christoph Maser
perl >= 5.006001

No epoch, so a package with epoch 3 or even 4 should be larger in any
case[1]. Indeed, if I download the package and install it with "rpm -U" it
works fine.

Looks like up2date ignores the epoch when comparing version numbers,
which is definitely a bug (although I doubt that Redhat will fix it,
since they switched to yum with RHEL 5).

hp

[1] Which makes the dependency a bit useless.
--
_ | Peter J. Holzer | Auf jedem Computer sollte der Satz Ludwigs II
|_|_) | Sysadmin WSR | eingepr?gt stehen: "Ein ewig R?tsel will ich
| | | hjp at wsr.ac.at | bleiben, mir und andern."
__/ | http://www.hjp.at/ | -- Wolfram Heinrich in desd
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://lists.repoforge.org/pipermail/users/attachments/20100607/48f56466/attachment.bin

[Peter J. Holzer]

Post by Christoph Maser

Post by Peter J. Holzer
Several perl modules have broken dependencies on rhel4.
perl-DBD-Pg-2.17.1-1.el4.rf requires perl >= 5.006001
perl-Module-Build-0.3603-1.el4.rf requires perl >= 5.006001
perl-Regexp-Common-2010010201-1.el4.rf requires perl >= 5.00473
rpm -q --provides perl
...
perl = 4:5.8.8-2.el4s1

Actually it seems you are wrong

I use up2date, not yum. Can yum access the Redhat repository on RHEL 4?
I never checked, but that might be a good opportunity to switch from
up2date to yum on the older redhat boxes.

Post by Christoph Maser
perl.x86_64 3:5.8.5-49.el4

I have perl = 4:5.8.8-2.el4s1 (from the rhel-x86_64-as-4-webapp-1-beta
channel), but that's an even higher version number, so if 3:5.8.5 is
good enough, 4:5.8.8 should work, too.

Post by Christoph Maser
perl >= 5.006001

No epoch, so a package with epoch 3 or even 4 should be larger in any
case[1]. Indeed, if I download the package and install it with "rpm -U" it
works fine.

Looks like up2date ignores the epoch when comparing version numbers,
which is definitely a bug (although I doubt that Redhat will fix it,
since they switched to yum with RHEL 5).

hp

[1] Which makes the dependency a bit useless.
--
_ | Peter J. Holzer | Auf jedem Computer sollte der Satz Ludwigs II
|_|_) | Sysadmin WSR | eingepr?gt stehen: "Ein ewig R?tsel will ich
| | | hjp at wsr.ac.at | bleiben, mir und andern."
__/ | http://www.hjp.at/ | -- Wolfram Heinrich in desd
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://lists.repoforge.org/pipermail/users/attachments/20100607/48f56466/attachment-0001.bin

[Peter J. Holzer]

Post by Christoph Maser

Post by Peter J. Holzer
Several perl modules have broken dependencies on rhel4.
perl-DBD-Pg-2.17.1-1.el4.rf requires perl >= 5.006001
perl-Module-Build-0.3603-1.el4.rf requires perl >= 5.006001
perl-Regexp-Common-2010010201-1.el4.rf requires perl >= 5.00473
rpm -q --provides perl
...
perl = 4:5.8.8-2.el4s1

Actually it seems you are wrong

I use up2date, not yum. Can yum access the Redhat repository on RHEL 4?
I never checked, but that might be a good opportunity to switch from
up2date to yum on the older redhat boxes.

Post by Christoph Maser
perl.x86_64 3:5.8.5-49.el4

I have perl = 4:5.8.8-2.el4s1 (from the rhel-x86_64-as-4-webapp-1-beta
channel), but that's an even higher version number, so if 3:5.8.5 is
good enough, 4:5.8.8 should work, too.

Post by Christoph Maser
perl >= 5.006001

No epoch, so a package with epoch 3 or even 4 should be larger in any
case[1]. Indeed, if I download the package and install it with "rpm -U" it
works fine.

Looks like up2date ignores the epoch when comparing version numbers,
which is definitely a bug (although I doubt that Redhat will fix it,
since they switched to yum with RHEL 5).

hp

[1] Which makes the dependency a bit useless.
--
_ | Peter J. Holzer | Auf jedem Computer sollte der Satz Ludwigs II
|_|_) | Sysadmin WSR | eingepr?gt stehen: "Ein ewig R?tsel will ich
| | | hjp at wsr.ac.at | bleiben, mir und andern."
__/ | http://www.hjp.at/ | -- Wolfram Heinrich in desd
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://lists.repoforge.org/pipermail/users/attachments/20100607/48f56466/attachment-0002.bin

[Peter J. Holzer]

Post by Christoph Maser

Post by Peter J. Holzer
Several perl modules have broken dependencies on rhel4.
perl-DBD-Pg-2.17.1-1.el4.rf requires perl >= 5.006001
perl-Module-Build-0.3603-1.el4.rf requires perl >= 5.006001
perl-Regexp-Common-2010010201-1.el4.rf requires perl >= 5.00473
rpm -q --provides perl
...
perl = 4:5.8.8-2.el4s1

Actually it seems you are wrong

I use up2date, not yum. Can yum access the Redhat repository on RHEL 4?
I never checked, but that might be a good opportunity to switch from
up2date to yum on the older redhat boxes.

Post by Christoph Maser
perl.x86_64 3:5.8.5-49.el4

I have perl = 4:5.8.8-2.el4s1 (from the rhel-x86_64-as-4-webapp-1-beta
channel), but that's an even higher version number, so if 3:5.8.5 is
good enough, 4:5.8.8 should work, too.

Post by Christoph Maser
perl >= 5.006001

No epoch, so a package with epoch 3 or even 4 should be larger in any
case[1]. Indeed, if I download the package and install it with "rpm -U" it
works fine.

Looks like up2date ignores the epoch when comparing version numbers,
which is definitely a bug (although I doubt that Redhat will fix it,
since they switched to yum with RHEL 5).

hp

[1] Which makes the dependency a bit useless.
--
_ | Peter J. Holzer | Auf jedem Computer sollte der Satz Ludwigs II
|_|_) | Sysadmin WSR | eingepr?gt stehen: "Ein ewig R?tsel will ich
| | | hjp at wsr.ac.at | bleiben, mir und andern."
__/ | http://www.hjp.at/ | -- Wolfram Heinrich in desd
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://lists.repoforge.org/pipermail/users/attachments/20100607/48f56466/attachment-0003.bin

[Peter J. Holzer]

Post by Christoph Maser

Post by Peter J. Holzer
Several perl modules have broken dependencies on rhel4.
perl-DBD-Pg-2.17.1-1.el4.rf requires perl >= 5.006001
perl-Module-Build-0.3603-1.el4.rf requires perl >= 5.006001
perl-Regexp-Common-2010010201-1.el4.rf requires perl >= 5.00473
rpm -q --provides perl
...
perl = 4:5.8.8-2.el4s1

Actually it seems you are wrong

I use up2date, not yum. Can yum access the Redhat repository on RHEL 4?
I never checked, but that might be a good opportunity to switch from
up2date to yum on the older redhat boxes.

Post by Christoph Maser
perl.x86_64 3:5.8.5-49.el4

I have perl = 4:5.8.8-2.el4s1 (from the rhel-x86_64-as-4-webapp-1-beta
channel), but that's an even higher version number, so if 3:5.8.5 is
good enough, 4:5.8.8 should work, too.

Post by Christoph Maser
perl >= 5.006001

No epoch, so a package with epoch 3 or even 4 should be larger in any
case[1]. Indeed, if I download the package and install it with "rpm -U" it
works fine.

Looks like up2date ignores the epoch when comparing version numbers,
which is definitely a bug (although I doubt that Redhat will fix it,
since they switched to yum with RHEL 5).

hp

[1] Which makes the dependency a bit useless.
--
_ | Peter J. Holzer | Auf jedem Computer sollte der Satz Ludwigs II
|_|_) | Sysadmin WSR | eingepr?gt stehen: "Ein ewig R?tsel will ich
| | | hjp at wsr.ac.at | bleiben, mir und andern."
__/ | http://www.hjp.at/ | -- Wolfram Heinrich in desd
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
URL: <http://lists.repoforge.org/pipermail/users/attachments/20100607/48f56466/attachment.sig>

[Pavel Kankovsky]

Post by Christoph Maser
perl.x86_64 3:5.8.5-49.el4

3:5.8.5-49.el4 is greater than 5.006001 according to rpm, isn't it?

The dependencies are broken because they do not really check Perl version:
the module expects at least 5.6.1 but any 5.x for x>=1 would satisfy
its dependency perl >= 5.006001.

On the other hand, it is quite unlikely Perl packaged for a certain distro
version would not be good enough for a module packaged for the same distro
version.

[Dave B]

This is definitely broken on RHEL4 w.r.t. up2date .

On everyone one of our machines...


up2date -l

Fetching Obsoletes list for channel: rhel-i386-as-4...

Fetching rpm headers...
########################################

Name Version Rel
Arch
----------------------------------------------------------------------------------------
perl 5.8.5 53.el4
i386
perl-suidperl 5.8.5 53.el4
i386

up2date -u perl

Fetching Obsoletes list for channel: rhel-i386-as-4...

Fetching rpm headers...
########################################

Name Version Rel
A
rch
--------------------------------------------------------------------------------
--------
perl 5.8.5
53.el4
i386


Testing package set / solving RPM inter-dependencies...
There was a package dependency problem. The message was:

Unresolvable chain of dependencies:
perl-DBD-Pg-2.17.1-1.el4.rf requires perl >= 5.006001




--

********************************
David William Botsch
Programmer/Analyst
CNF Computing
botsch at cnf.cornell.edu
********************************

[Jani Ollikainen]

Post by Dave B
This is definitely broken on RHEL4 w.r.t. up2date .
On everyone one of our machines...

Well, tested yum:

Installing:
arj i386 3.10.22-1.el4.rf rpmforge
187 k
replacing unarj.i386 2.63-0.a.2.el4.rf

libmpeg2-utils i386 0.5.1-2.el4.rf rpmforge
32 k
replacing mpeg2dec.i386 0.4.1-2.el4.rf

perl-DBD-mysql i386 4.014-1.el4.rf rpmforge
222 k
replacing perl-DBD-MySQL.i386 4.008-1.el4s1

perl-Date-Manip noarch 5.54-2.el4.rf rpmforge
208 k
replacing perl-DateManip.noarch 5.42a-3

perl-IO-Compress noarch 2.024-1.el4.rf rpmforge
241 k
replacing perl-Compress-Zlib.noarch 2.015-1.el4.rf

Updating:
mtr i386 2:0.78-1.el4.rf rpmforge
79 k
perl-Archive-Zip noarch 1.30-1.el4.rf rpmforge
114 k
Installing for dependencies:
libmpeg2 i386 0.5.1-2.el4.rf rpmforge
137 k

Transaction Summary
=============================================================================
Install 6 Package(s)
Update 2 Package(s)
Remove 0 Package(s)
Total download size: 1.2 M

Those when in a-ok, so then we can argue is the problem in
up2date or in the package .specs.

I think I'll say in the .spec's as up2date is update tool
for RHEL4 and it should understand the packages also.

[Jani Ollikainen]

Post by Dave B
This is definitely broken on RHEL4 w.r.t. up2date .
On everyone one of our machines...

Well, tested yum:

Installing:
arj i386 3.10.22-1.el4.rf rpmforge
187 k
replacing unarj.i386 2.63-0.a.2.el4.rf

libmpeg2-utils i386 0.5.1-2.el4.rf rpmforge
32 k
replacing mpeg2dec.i386 0.4.1-2.el4.rf

perl-DBD-mysql i386 4.014-1.el4.rf rpmforge
222 k
replacing perl-DBD-MySQL.i386 4.008-1.el4s1

perl-Date-Manip noarch 5.54-2.el4.rf rpmforge
208 k
replacing perl-DateManip.noarch 5.42a-3

perl-IO-Compress noarch 2.024-1.el4.rf rpmforge
241 k
replacing perl-Compress-Zlib.noarch 2.015-1.el4.rf

Updating:
mtr i386 2:0.78-1.el4.rf rpmforge
79 k
perl-Archive-Zip noarch 1.30-1.el4.rf rpmforge
114 k
Installing for dependencies:
libmpeg2 i386 0.5.1-2.el4.rf rpmforge
137 k

Transaction Summary
=============================================================================
Install 6 Package(s)
Update 2 Package(s)
Remove 0 Package(s)
Total download size: 1.2 M

Those when in a-ok, so then we can argue is the problem in
up2date or in the package .specs.

I think I'll say in the .spec's as up2date is update tool
for RHEL4 and it should understand the packages also.

[Jani Ollikainen]

Post by Dave B
This is definitely broken on RHEL4 w.r.t. up2date .
On everyone one of our machines...

Well, tested yum:

Installing:
arj i386 3.10.22-1.el4.rf rpmforge
187 k
replacing unarj.i386 2.63-0.a.2.el4.rf

libmpeg2-utils i386 0.5.1-2.el4.rf rpmforge
32 k
replacing mpeg2dec.i386 0.4.1-2.el4.rf

perl-DBD-mysql i386 4.014-1.el4.rf rpmforge
222 k
replacing perl-DBD-MySQL.i386 4.008-1.el4s1

perl-Date-Manip noarch 5.54-2.el4.rf rpmforge
208 k
replacing perl-DateManip.noarch 5.42a-3

perl-IO-Compress noarch 2.024-1.el4.rf rpmforge
241 k
replacing perl-Compress-Zlib.noarch 2.015-1.el4.rf

Updating:
mtr i386 2:0.78-1.el4.rf rpmforge
79 k
perl-Archive-Zip noarch 1.30-1.el4.rf rpmforge
114 k
Installing for dependencies:
libmpeg2 i386 0.5.1-2.el4.rf rpmforge
137 k

Transaction Summary
=============================================================================
Install 6 Package(s)
Update 2 Package(s)
Remove 0 Package(s)
Total download size: 1.2 M

Those when in a-ok, so then we can argue is the problem in
up2date or in the package .specs.

I think I'll say in the .spec's as up2date is update tool
for RHEL4 and it should understand the packages also.

[Jani Ollikainen]

Post by Dave B
This is definitely broken on RHEL4 w.r.t. up2date .
On everyone one of our machines...

Well, tested yum:

Installing:
arj i386 3.10.22-1.el4.rf rpmforge
187 k
replacing unarj.i386 2.63-0.a.2.el4.rf

libmpeg2-utils i386 0.5.1-2.el4.rf rpmforge
32 k
replacing mpeg2dec.i386 0.4.1-2.el4.rf

perl-DBD-mysql i386 4.014-1.el4.rf rpmforge
222 k
replacing perl-DBD-MySQL.i386 4.008-1.el4s1

perl-Date-Manip noarch 5.54-2.el4.rf rpmforge
208 k
replacing perl-DateManip.noarch 5.42a-3

perl-IO-Compress noarch 2.024-1.el4.rf rpmforge
241 k
replacing perl-Compress-Zlib.noarch 2.015-1.el4.rf

Updating:
mtr i386 2:0.78-1.el4.rf rpmforge
79 k
perl-Archive-Zip noarch 1.30-1.el4.rf rpmforge
114 k
Installing for dependencies:
libmpeg2 i386 0.5.1-2.el4.rf rpmforge
137 k

Transaction Summary
=============================================================================
Install 6 Package(s)
Update 2 Package(s)
Remove 0 Package(s)
Total download size: 1.2 M

Those when in a-ok, so then we can argue is the problem in
up2date or in the package .specs.

I think I'll say in the .spec's as up2date is update tool
for RHEL4 and it should understand the packages also.

[Jani Ollikainen]

Post by Dave B
This is definitely broken on RHEL4 w.r.t. up2date .
On everyone one of our machines...

Well, tested yum:

Installing:
arj i386 3.10.22-1.el4.rf rpmforge
187 k
replacing unarj.i386 2.63-0.a.2.el4.rf

libmpeg2-utils i386 0.5.1-2.el4.rf rpmforge
32 k
replacing mpeg2dec.i386 0.4.1-2.el4.rf

perl-DBD-mysql i386 4.014-1.el4.rf rpmforge
222 k
replacing perl-DBD-MySQL.i386 4.008-1.el4s1

perl-Date-Manip noarch 5.54-2.el4.rf rpmforge
208 k
replacing perl-DateManip.noarch 5.42a-3

perl-IO-Compress noarch 2.024-1.el4.rf rpmforge
241 k
replacing perl-Compress-Zlib.noarch 2.015-1.el4.rf

Updating:
mtr i386 2:0.78-1.el4.rf rpmforge
79 k
perl-Archive-Zip noarch 1.30-1.el4.rf rpmforge
114 k
Installing for dependencies:
libmpeg2 i386 0.5.1-2.el4.rf rpmforge
137 k

Transaction Summary
=============================================================================
Install 6 Package(s)
Update 2 Package(s)
Remove 0 Package(s)
Total download size: 1.2 M

Those when in a-ok, so then we can argue is the problem in
up2date or in the package .specs.

I think I'll say in the .spec's as up2date is update tool
for RHEL4 and it should understand the packages also.

[Dave B]

If up2date is broken, fine... unfortunately, I think RHEL4 is in a state
where that particular bug won't be fixed by redhat, now.

So, it would be good if the appropriate packages from rpmforge could be
patched to work around the problem. Once done, please bump the version
numbers so that yum will install the new packages over the ones w. the
incorrect dependencies.

thanks.

On Thu, 2010-06-10 at 12:00 +0100, suggest-request at lists.rpmforge.net

Re: [suggest] broken dependencies for some perl modules on

[Christoph Maser]

Post by Dave B
If up2date is broken, fine... unfortunately, I think RHEL4 is in a state
where that particular bug won't be fixed by redhat, now.
So, it would be good if the appropriate packages from rpmforge could be
patched to work around the problem. Once done, please bump the version
numbers so that yum will install the new packages over the ones w. the
incorrect dependencies.
thanks.

Well this is really a big workload. This line:

find . -name "perl-*" | xargs grep -l "perl .. 5.00"| wc -l

returns 127, so we are talking of ~100 packages to edit.

[Christoph Maser]

Post by Dave B
If up2date is broken, fine... unfortunately, I think RHEL4 is in a state
where that particular bug won't be fixed by redhat, now.
So, it would be good if the appropriate packages from rpmforge could be
patched to work around the problem. Once done, please bump the version
numbers so that yum will install the new packages over the ones w. the
incorrect dependencies.
thanks.

Well this is really a big workload. This line:

find . -name "perl-*" | xargs grep -l "perl .. 5.00"| wc -l

returns 127, so we are talking of ~100 packages to edit.

[Christoph Maser]

Post by Dave B
If up2date is broken, fine... unfortunately, I think RHEL4 is in a state
where that particular bug won't be fixed by redhat, now.
So, it would be good if the appropriate packages from rpmforge could be
patched to work around the problem. Once done, please bump the version
numbers so that yum will install the new packages over the ones w. the
incorrect dependencies.
thanks.

Well this is really a big workload. This line:

find . -name "perl-*" | xargs grep -l "perl .. 5.00"| wc -l

returns 127, so we are talking of ~100 packages to edit.

[Christoph Maser]

Post by Dave B
If up2date is broken, fine... unfortunately, I think RHEL4 is in a state
where that particular bug won't be fixed by redhat, now.
So, it would be good if the appropriate packages from rpmforge could be
patched to work around the problem. Once done, please bump the version
numbers so that yum will install the new packages over the ones w. the
incorrect dependencies.
thanks.

Well this is really a big workload. This line:

find . -name "perl-*" | xargs grep -l "perl .. 5.00"| wc -l

returns 127, so we are talking of ~100 packages to edit.

[Christoph Maser]

Post by Dave B
If up2date is broken, fine... unfortunately, I think RHEL4 is in a state
where that particular bug won't be fixed by redhat, now.
So, it would be good if the appropriate packages from rpmforge could be
patched to work around the problem. Once done, please bump the version
numbers so that yum will install the new packages over the ones w. the
incorrect dependencies.
thanks.

Well this is really a big workload. This line:

find . -name "perl-*" | xargs grep -l "perl .. 5.00"| wc -l

returns 127, so we are talking of ~100 packages to edit.

[Dave B]

Though, perhaps not all of them are broken?

I think both myself and someone else have mentioned just the same 3
packages causing the issue.

On Fri, 2010-06-11 at 12:00 +0100, suggest-request at lists.rpmforge.net

Message: 2
Date: Fri, 11 Jun 2010 09:57:00 +0200
From: Christoph Maser <cmaser at gmx.de>
Subject: Re: [suggest] broken dependencies for some perl modules on
RHEL4
To: suggest at lists.rpmforge.net
Message-ID: <1276243020.12228.36.camel at HUB8071NC4.financial.com>
Content-Type: text/plain; charset="UTF-8"

Post by Dave B
If up2date is broken, fine... unfortunately, I think RHEL4 is in a state
where that particular bug won't be fixed by redhat, now.
So, it would be good if the appropriate packages from rpmforge could be
patched to work around the problem. Once done, please bump the version
numbers so that yum will install the new packages over the ones w. the
incorrect dependencies.
thanks.

find . -name "perl-*" | xargs grep -l "perl .. 5.00"| wc -l
returns 127, so we are talking of ~100 packages to edit.

[Christoph Maser]

Post by Dave B
Though, perhaps not all of them are broken?
I think both myself and someone else have mentioned just the same 3
packages causing the issue.

I was just following the argumentation why they are "broken". I will
have a look at those files when I have some time.


Offtopic:
Could you please not top-post and also all of your replys seem to have
broken references/in-reply-to headers. At last evolution does not sort
them into the thread.

[Christoph Maser]

Post by Dave B
Though, perhaps not all of them are broken?
I think both myself and someone else have mentioned just the same 3
packages causing the issue.

I found and changed perl-DBD-Pg. Wich were the other two?

Chris

[Peter J. Holzer]

Post by Christoph Maser

Post by Dave B
Though, perhaps not all of them are broken?
I think both myself and someone else have mentioned just the same 3
packages causing the issue.

I found and changed perl-DBD-Pg. Wich were the other two?

perl-Module-Build-0.3603-1.el4.rf requires perl >= 5.006001
perl-Regexp-Common-2010010201-1.el4.rf requires perl >= 5.00473

hp
--
_ | Peter J. Holzer | Auf jedem Computer sollte der Satz Ludwigs II
|_|_) | Sysadmin WSR | eingepr?gt stehen: "Ein ewig R?tsel will ich
| | | hjp at wsr.ac.at | bleiben, mir und andern."
__/ | http://www.hjp.at/ | -- Wolfram Heinrich in desd
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://lists.repoforge.org/pipermail/users/attachments/20100617/9c060121/attachment.bin

[Christoph Maser]

Post by Peter J. Holzer

Post by Christoph Maser

Post by Dave B
Though, perhaps not all of them are broken?
I think both myself and someone else have mentioned just the same 3
packages causing the issue.

I found and changed perl-DBD-Pg. Wich were the other two?

perl-Module-Build-0.3603-1.el4.rf requires perl >= 5.006001
perl-Regexp-Common-2010010201-1.el4.rf requires perl >= 5.00473
hp

Thanks, i did push an update for thiose packages.

Chris

[Christoph Maser]

Post by Peter J. Holzer

Post by Christoph Maser

Post by Dave B
Though, perhaps not all of them are broken?
I think both myself and someone else have mentioned just the same 3
packages causing the issue.

I found and changed perl-DBD-Pg. Wich were the other two?

perl-Module-Build-0.3603-1.el4.rf requires perl >= 5.006001
perl-Regexp-Common-2010010201-1.el4.rf requires perl >= 5.00473
hp

Thanks, i did push an update for thiose packages.

Chris

[Christoph Maser]

Post by Peter J. Holzer

Post by Christoph Maser

Post by Dave B
Though, perhaps not all of them are broken?
I think both myself and someone else have mentioned just the same 3
packages causing the issue.

I found and changed perl-DBD-Pg. Wich were the other two?

perl-Module-Build-0.3603-1.el4.rf requires perl >= 5.006001
perl-Regexp-Common-2010010201-1.el4.rf requires perl >= 5.00473
hp

Thanks, i did push an update for thiose packages.

Chris

[Christoph Maser]

Post by Peter J. Holzer

Post by Christoph Maser

Post by Dave B
Though, perhaps not all of them are broken?
I think both myself and someone else have mentioned just the same 3
packages causing the issue.

I found and changed perl-DBD-Pg. Wich were the other two?

perl-Module-Build-0.3603-1.el4.rf requires perl >= 5.006001
perl-Regexp-Common-2010010201-1.el4.rf requires perl >= 5.00473
hp

Thanks, i did push an update for thiose packages.

Chris

[Christoph Maser]

Post by Peter J. Holzer

Post by Christoph Maser

Post by Dave B
Though, perhaps not all of them are broken?
I think both myself and someone else have mentioned just the same 3
packages causing the issue.

I found and changed perl-DBD-Pg. Wich were the other two?

perl-Module-Build-0.3603-1.el4.rf requires perl >= 5.006001
perl-Regexp-Common-2010010201-1.el4.rf requires perl >= 5.00473
hp

Thanks, i did push an update for thiose packages.

Chris

[Peter J. Holzer]

Post by Christoph Maser

Post by Dave B
Though, perhaps not all of them are broken?
I think both myself and someone else have mentioned just the same 3
packages causing the issue.

I found and changed perl-DBD-Pg. Wich were the other two?

perl-Module-Build-0.3603-1.el4.rf requires perl >= 5.006001
perl-Regexp-Common-2010010201-1.el4.rf requires perl >= 5.00473

hp
--
_ | Peter J. Holzer | Auf jedem Computer sollte der Satz Ludwigs II
|_|_) | Sysadmin WSR | eingepr?gt stehen: "Ein ewig R?tsel will ich
| | | hjp at wsr.ac.at | bleiben, mir und andern."
__/ | http://www.hjp.at/ | -- Wolfram Heinrich in desd
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://lists.repoforge.org/pipermail/users/attachments/20100617/9c060121/attachment-0001.bin

[Peter J. Holzer]

Post by Christoph Maser

Post by Dave B
Though, perhaps not all of them are broken?
I think both myself and someone else have mentioned just the same 3
packages causing the issue.

I found and changed perl-DBD-Pg. Wich were the other two?

perl-Module-Build-0.3603-1.el4.rf requires perl >= 5.006001
perl-Regexp-Common-2010010201-1.el4.rf requires perl >= 5.00473

hp
--
_ | Peter J. Holzer | Auf jedem Computer sollte der Satz Ludwigs II
|_|_) | Sysadmin WSR | eingepr?gt stehen: "Ein ewig R?tsel will ich
| | | hjp at wsr.ac.at | bleiben, mir und andern."
__/ | http://www.hjp.at/ | -- Wolfram Heinrich in desd
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://lists.repoforge.org/pipermail/users/attachments/20100617/9c060121/attachment-0002.bin

[Peter J. Holzer]

Post by Christoph Maser

Post by Dave B
Though, perhaps not all of them are broken?
I think both myself and someone else have mentioned just the same 3
packages causing the issue.

I found and changed perl-DBD-Pg. Wich were the other two?

perl-Module-Build-0.3603-1.el4.rf requires perl >= 5.006001
perl-Regexp-Common-2010010201-1.el4.rf requires perl >= 5.00473

hp
--
_ | Peter J. Holzer | Auf jedem Computer sollte der Satz Ludwigs II
|_|_) | Sysadmin WSR | eingepr?gt stehen: "Ein ewig R?tsel will ich
| | | hjp at wsr.ac.at | bleiben, mir und andern."
__/ | http://www.hjp.at/ | -- Wolfram Heinrich in desd
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://lists.repoforge.org/pipermail/users/attachments/20100617/9c060121/attachment-0003.bin

[Peter J. Holzer]

Post by Christoph Maser

Post by Dave B
Though, perhaps not all of them are broken?
I think both myself and someone else have mentioned just the same 3
packages causing the issue.

I found and changed perl-DBD-Pg. Wich were the other two?

perl-Module-Build-0.3603-1.el4.rf requires perl >= 5.006001
perl-Regexp-Common-2010010201-1.el4.rf requires perl >= 5.00473

hp
--
_ | Peter J. Holzer | Auf jedem Computer sollte der Satz Ludwigs II
|_|_) | Sysadmin WSR | eingepr?gt stehen: "Ein ewig R?tsel will ich
| | | hjp at wsr.ac.at | bleiben, mir und andern."
__/ | http://www.hjp.at/ | -- Wolfram Heinrich in desd
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
URL: <http://lists.repoforge.org/pipermail/users/attachments/20100617/9c060121/attachment.sig>

[Christoph Maser]

Post by Dave B
Though, perhaps not all of them are broken?
I think both myself and someone else have mentioned just the same 3
packages causing the issue.

I was just following the argumentation why they are "broken". I will
have a look at those files when I have some time.


Offtopic:
Could you please not top-post and also all of your replys seem to have
broken references/in-reply-to headers. At last evolution does not sort
them into the thread.

[Christoph Maser]

Post by Dave B
Though, perhaps not all of them are broken?
I think both myself and someone else have mentioned just the same 3
packages causing the issue.

I found and changed perl-DBD-Pg. Wich were the other two?

Chris

[Christoph Maser]

Post by Dave B
Though, perhaps not all of them are broken?
I think both myself and someone else have mentioned just the same 3
packages causing the issue.

I was just following the argumentation why they are "broken". I will
have a look at those files when I have some time.


Offtopic:
Could you please not top-post and also all of your replys seem to have
broken references/in-reply-to headers. At last evolution does not sort
them into the thread.

[Christoph Maser]

Post by Dave B
Though, perhaps not all of them are broken?
I think both myself and someone else have mentioned just the same 3
packages causing the issue.

I found and changed perl-DBD-Pg. Wich were the other two?

Chris

[Christoph Maser]

Post by Dave B
Though, perhaps not all of them are broken?
I think both myself and someone else have mentioned just the same 3
packages causing the issue.

I was just following the argumentation why they are "broken". I will
have a look at those files when I have some time.


Offtopic:
Could you please not top-post and also all of your replys seem to have
broken references/in-reply-to headers. At last evolution does not sort
them into the thread.

[Christoph Maser]

Post by Dave B
Though, perhaps not all of them are broken?
I think both myself and someone else have mentioned just the same 3
packages causing the issue.

I found and changed perl-DBD-Pg. Wich were the other two?

Chris

[Christoph Maser]

Post by Dave B
Though, perhaps not all of them are broken?
I think both myself and someone else have mentioned just the same 3
packages causing the issue.

I was just following the argumentation why they are "broken". I will
have a look at those files when I have some time.


Offtopic:
Could you please not top-post and also all of your replys seem to have
broken references/in-reply-to headers. At last evolution does not sort
them into the thread.

[Christoph Maser]

Post by Dave B
Though, perhaps not all of them are broken?
I think both myself and someone else have mentioned just the same 3
packages causing the issue.

I found and changed perl-DBD-Pg. Wich were the other two?

Chris

[Peter J. Holzer]

[Resent because it was rejected because I used a wrong sender address -
apologies if this turns up twice]

Several perl modules have broken dependencies on rhel4.

For example:

perl-DBD-Pg-2.17.1-1.el4.rf requires perl >= 5.006001
perl-Module-Build-0.3603-1.el4.rf requires perl >= 5.006001
perl-Regexp-Common-2010010201-1.el4.rf requires perl >= 5.00473

However, RHEL4 uses a different numbering scheme:

rpm -q --provides perl
...
perl = 4:5.8.8-2.el4s1

and 4:5.8.8 apparently isn't greater than 5.006001, although it should
be (5.8.8 is 5.008008 in the perl world, but of course RPM cannot know
this).

The culprit seems to be an explicit Requires line in the spec files
which was added a few months ago. Given that 5.006001 is very old and
5.00473 is ancient and older versions were never installed on any RHEL
still supported by rpmforge, these Requires lines could probably be
safely omitted.

I also noted that the SRPM for perl-DBD-Pg-2.17 (didn't look at the
others) now has "el5" in the name. Maybe that was intended only for
RHEL5 and built for the other versions by mistake?

hp
--
_ | Peter J. Holzer | Auf jedem Computer sollte der Satz Ludwigs II
|_|_) | Sysadmin WSR | eingepr?gt stehen: "Ein ewig R?tsel will ich
| | | hjp at wsr.ac.at | bleiben, mir und andern."
__/ | http://www.hjp.at/ | -- Wolfram Heinrich in desd
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://lists.repoforge.org/pipermail/users/attachments/20100607/fedd300c/attachment-0001.bin

[Christoph Maser]

Thanks for reporting Peter. This happens as I replace autogernerated
dependecies by rpmbuild through autogenerated dependencies from CPAN
metadata. I will have a look at it.

Chris

Post by Peter J. Holzer
[Resent because it was rejected because I used a wrong sender address -
apologies if this turns up twice]
Several perl modules have broken dependencies on rhel4.
perl-DBD-Pg-2.17.1-1.el4.rf requires perl >= 5.006001
perl-Module-Build-0.3603-1.el4.rf requires perl >= 5.006001
perl-Regexp-Common-2010010201-1.el4.rf requires perl >= 5.00473
rpm -q --provides perl
...
perl = 4:5.8.8-2.el4s1
and 4:5.8.8 apparently isn't greater than 5.006001, although it should
be (5.8.8 is 5.008008 in the perl world, but of course RPM cannot know
this).
The culprit seems to be an explicit Requires line in the spec files
which was added a few months ago. Given that 5.006001 is very old and
5.00473 is ancient and older versions were never installed on any RHEL
still supported by rpmforge, these Requires lines could probably be
safely omitted.
I also noted that the SRPM for perl-DBD-Pg-2.17 (didn't look at the
others) now has "el5" in the name. Maybe that was intended only for
RHEL5 and built for the other versions by mistake?
hp
_______________________________________________
suggest mailing list
suggest at lists.rpmforge.net
http://lists.rpmforge.net/mailman/listinfo/suggest

[Christoph Maser]

Post by Peter J. Holzer
[Resent because it was rejected because I used a wrong sender address -
apologies if this turns up twice]
Several perl modules have broken dependencies on rhel4.
perl-DBD-Pg-2.17.1-1.el4.rf requires perl >= 5.006001
perl-Module-Build-0.3603-1.el4.rf requires perl >= 5.006001
perl-Regexp-Common-2010010201-1.el4.rf requires perl >= 5.00473
rpm -q --provides perl
...
perl = 4:5.8.8-2.el4s1

Actually it seems you are wrong


yum provides "perl >= 5.006001" gives me this:

perl.x86_64 3:5.8.5-49.el4
base
Matched from:
perl >= 5.006001


Also installing those modules went just fine for me. What exactly is the
problem you are having?

[Pavel Kankovsky]

Post by Christoph Maser
perl.x86_64 3:5.8.5-49.el4

3:5.8.5-49.el4 is greater than 5.006001 according to rpm, isn't it?

The dependencies are broken because they do not really check Perl version:
the module expects at least 5.6.1 but any 5.x for x>=1 would satisfy
its dependency perl >= 5.006001.

On the other hand, it is quite unlikely Perl packaged for a certain distro
version would not be good enough for a module packaged for the same distro
version.

[Dave B]

This is definitely broken on RHEL4 w.r.t. up2date .

On everyone one of our machines...


up2date -l

Fetching Obsoletes list for channel: rhel-i386-as-4...

Fetching rpm headers...
########################################

Name Version Rel
Arch
----------------------------------------------------------------------------------------
perl 5.8.5 53.el4
i386
perl-suidperl 5.8.5 53.el4
i386

up2date -u perl

Fetching Obsoletes list for channel: rhel-i386-as-4...

Fetching rpm headers...
########################################

Name Version Rel
A
rch
--------------------------------------------------------------------------------
--------
perl 5.8.5
53.el4
i386


Testing package set / solving RPM inter-dependencies...
There was a package dependency problem. The message was:

Unresolvable chain of dependencies:
perl-DBD-Pg-2.17.1-1.el4.rf requires perl >= 5.006001




--

********************************
David William Botsch
Programmer/Analyst
CNF Computing
botsch at cnf.cornell.edu
********************************

[Dave B]

If up2date is broken, fine... unfortunately, I think RHEL4 is in a state
where that particular bug won't be fixed by redhat, now.

So, it would be good if the appropriate packages from rpmforge could be
patched to work around the problem. Once done, please bump the version
numbers so that yum will install the new packages over the ones w. the
incorrect dependencies.

thanks.

On Thu, 2010-06-10 at 12:00 +0100, suggest-request at lists.rpmforge.net

Re: [suggest] broken dependencies for some perl modules on

[Dave B]

Though, perhaps not all of them are broken?

I think both myself and someone else have mentioned just the same 3
packages causing the issue.

On Fri, 2010-06-11 at 12:00 +0100, suggest-request at lists.rpmforge.net

Message: 2
Date: Fri, 11 Jun 2010 09:57:00 +0200
From: Christoph Maser <cmaser at gmx.de>
Subject: Re: [suggest] broken dependencies for some perl modules on
RHEL4
To: suggest at lists.rpmforge.net
Message-ID: <1276243020.12228.36.camel at HUB8071NC4.financial.com>
Content-Type: text/plain; charset="UTF-8"

Post by Dave B
If up2date is broken, fine... unfortunately, I think RHEL4 is in a state
where that particular bug won't be fixed by redhat, now.
So, it would be good if the appropriate packages from rpmforge could be
patched to work around the problem. Once done, please bump the version
numbers so that yum will install the new packages over the ones w. the
incorrect dependencies.
thanks.

find . -name "perl-*" | xargs grep -l "perl .. 5.00"| wc -l
returns 127, so we are talking of ~100 packages to edit.

[Peter J. Holzer]

[Resent because it was rejected because I used a wrong sender address -
apologies if this turns up twice]

Several perl modules have broken dependencies on rhel4.

For example:

perl-DBD-Pg-2.17.1-1.el4.rf requires perl >= 5.006001
perl-Module-Build-0.3603-1.el4.rf requires perl >= 5.006001
perl-Regexp-Common-2010010201-1.el4.rf requires perl >= 5.00473

However, RHEL4 uses a different numbering scheme:

rpm -q --provides perl
...
perl = 4:5.8.8-2.el4s1

and 4:5.8.8 apparently isn't greater than 5.006001, although it should
be (5.8.8 is 5.008008 in the perl world, but of course RPM cannot know
this).

The culprit seems to be an explicit Requires line in the spec files
which was added a few months ago. Given that 5.006001 is very old and
5.00473 is ancient and older versions were never installed on any RHEL
still supported by rpmforge, these Requires lines could probably be
safely omitted.

I also noted that the SRPM for perl-DBD-Pg-2.17 (didn't look at the
others) now has "el5" in the name. Maybe that was intended only for
RHEL5 and built for the other versions by mistake?

hp
--
_ | Peter J. Holzer | Auf jedem Computer sollte der Satz Ludwigs II
|_|_) | Sysadmin WSR | eingepr?gt stehen: "Ein ewig R?tsel will ich
| | | hjp at wsr.ac.at | bleiben, mir und andern."
__/ | http://www.hjp.at/ | -- Wolfram Heinrich in desd
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://lists.repoforge.org/pipermail/users/attachments/20100607/fedd300c/attachment-0002.bin

[Christoph Maser]

Thanks for reporting Peter. This happens as I replace autogernerated
dependecies by rpmbuild through autogenerated dependencies from CPAN
metadata. I will have a look at it.

Chris

Post by Peter J. Holzer
[Resent because it was rejected because I used a wrong sender address -
apologies if this turns up twice]
Several perl modules have broken dependencies on rhel4.
perl-DBD-Pg-2.17.1-1.el4.rf requires perl >= 5.006001
perl-Module-Build-0.3603-1.el4.rf requires perl >= 5.006001
perl-Regexp-Common-2010010201-1.el4.rf requires perl >= 5.00473
rpm -q --provides perl
...
perl = 4:5.8.8-2.el4s1
and 4:5.8.8 apparently isn't greater than 5.006001, although it should
be (5.8.8 is 5.008008 in the perl world, but of course RPM cannot know
this).
The culprit seems to be an explicit Requires line in the spec files
which was added a few months ago. Given that 5.006001 is very old and
5.00473 is ancient and older versions were never installed on any RHEL
still supported by rpmforge, these Requires lines could probably be
safely omitted.
I also noted that the SRPM for perl-DBD-Pg-2.17 (didn't look at the
others) now has "el5" in the name. Maybe that was intended only for
RHEL5 and built for the other versions by mistake?
hp
_______________________________________________
suggest mailing list
suggest at lists.rpmforge.net
http://lists.rpmforge.net/mailman/listinfo/suggest

[Christoph Maser]

Post by Peter J. Holzer
[Resent because it was rejected because I used a wrong sender address -
apologies if this turns up twice]
Several perl modules have broken dependencies on rhel4.
perl-DBD-Pg-2.17.1-1.el4.rf requires perl >= 5.006001
perl-Module-Build-0.3603-1.el4.rf requires perl >= 5.006001
perl-Regexp-Common-2010010201-1.el4.rf requires perl >= 5.00473
rpm -q --provides perl
...
perl = 4:5.8.8-2.el4s1

Actually it seems you are wrong


yum provides "perl >= 5.006001" gives me this:

perl.x86_64 3:5.8.5-49.el4
base
Matched from:
perl >= 5.006001


Also installing those modules went just fine for me. What exactly is the
problem you are having?

[Pavel Kankovsky]

Post by Christoph Maser
perl.x86_64 3:5.8.5-49.el4

3:5.8.5-49.el4 is greater than 5.006001 according to rpm, isn't it?

The dependencies are broken because they do not really check Perl version:
the module expects at least 5.6.1 but any 5.x for x>=1 would satisfy
its dependency perl >= 5.006001.

On the other hand, it is quite unlikely Perl packaged for a certain distro
version would not be good enough for a module packaged for the same distro
version.

[Dave B]

This is definitely broken on RHEL4 w.r.t. up2date .

On everyone one of our machines...


up2date -l

Fetching Obsoletes list for channel: rhel-i386-as-4...

Fetching rpm headers...
########################################

Name Version Rel
Arch
----------------------------------------------------------------------------------------
perl 5.8.5 53.el4
i386
perl-suidperl 5.8.5 53.el4
i386

up2date -u perl

Fetching Obsoletes list for channel: rhel-i386-as-4...

Fetching rpm headers...
########################################

Name Version Rel
A
rch
--------------------------------------------------------------------------------
--------
perl 5.8.5
53.el4
i386


Testing package set / solving RPM inter-dependencies...
There was a package dependency problem. The message was:

Unresolvable chain of dependencies:
perl-DBD-Pg-2.17.1-1.el4.rf requires perl >= 5.006001




--

********************************
David William Botsch
Programmer/Analyst
CNF Computing
botsch at cnf.cornell.edu
********************************

[Dave B]

If up2date is broken, fine... unfortunately, I think RHEL4 is in a state
where that particular bug won't be fixed by redhat, now.

So, it would be good if the appropriate packages from rpmforge could be
patched to work around the problem. Once done, please bump the version
numbers so that yum will install the new packages over the ones w. the
incorrect dependencies.

thanks.

On Thu, 2010-06-10 at 12:00 +0100, suggest-request at lists.rpmforge.net

Re: [suggest] broken dependencies for some perl modules on

[Dave B]

Though, perhaps not all of them are broken?

I think both myself and someone else have mentioned just the same 3
packages causing the issue.

On Fri, 2010-06-11 at 12:00 +0100, suggest-request at lists.rpmforge.net

Message: 2
Date: Fri, 11 Jun 2010 09:57:00 +0200
From: Christoph Maser <cmaser at gmx.de>
Subject: Re: [suggest] broken dependencies for some perl modules on
RHEL4
To: suggest at lists.rpmforge.net
Message-ID: <1276243020.12228.36.camel at HUB8071NC4.financial.com>
Content-Type: text/plain; charset="UTF-8"

Post by Dave B
If up2date is broken, fine... unfortunately, I think RHEL4 is in a state
where that particular bug won't be fixed by redhat, now.
So, it would be good if the appropriate packages from rpmforge could be
patched to work around the problem. Once done, please bump the version
numbers so that yum will install the new packages over the ones w. the
incorrect dependencies.
thanks.

find . -name "perl-*" | xargs grep -l "perl .. 5.00"| wc -l
returns 127, so we are talking of ~100 packages to edit.

[Peter J. Holzer]

[Resent because it was rejected because I used a wrong sender address -
apologies if this turns up twice]

Several perl modules have broken dependencies on rhel4.

For example:

perl-DBD-Pg-2.17.1-1.el4.rf requires perl >= 5.006001
perl-Module-Build-0.3603-1.el4.rf requires perl >= 5.006001
perl-Regexp-Common-2010010201-1.el4.rf requires perl >= 5.00473

However, RHEL4 uses a different numbering scheme:

rpm -q --provides perl
...
perl = 4:5.8.8-2.el4s1

and 4:5.8.8 apparently isn't greater than 5.006001, although it should
be (5.8.8 is 5.008008 in the perl world, but of course RPM cannot know
this).

The culprit seems to be an explicit Requires line in the spec files
which was added a few months ago. Given that 5.006001 is very old and
5.00473 is ancient and older versions were never installed on any RHEL
still supported by rpmforge, these Requires lines could probably be
safely omitted.

I also noted that the SRPM for perl-DBD-Pg-2.17 (didn't look at the
others) now has "el5" in the name. Maybe that was intended only for
RHEL5 and built for the other versions by mistake?

hp
--
_ | Peter J. Holzer | Auf jedem Computer sollte der Satz Ludwigs II
|_|_) | Sysadmin WSR | eingepr?gt stehen: "Ein ewig R?tsel will ich
| | | hjp at wsr.ac.at | bleiben, mir und andern."
__/ | http://www.hjp.at/ | -- Wolfram Heinrich in desd
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://lists.repoforge.org/pipermail/users/attachments/20100607/fedd300c/attachment-0003.bin

[Christoph Maser]

Thanks for reporting Peter. This happens as I replace autogernerated
dependecies by rpmbuild through autogenerated dependencies from CPAN
metadata. I will have a look at it.

Chris

Post by Peter J. Holzer
[Resent because it was rejected because I used a wrong sender address -
apologies if this turns up twice]
Several perl modules have broken dependencies on rhel4.
perl-DBD-Pg-2.17.1-1.el4.rf requires perl >= 5.006001
perl-Module-Build-0.3603-1.el4.rf requires perl >= 5.006001
perl-Regexp-Common-2010010201-1.el4.rf requires perl >= 5.00473
rpm -q --provides perl
...
perl = 4:5.8.8-2.el4s1
and 4:5.8.8 apparently isn't greater than 5.006001, although it should
be (5.8.8 is 5.008008 in the perl world, but of course RPM cannot know
this).
The culprit seems to be an explicit Requires line in the spec files
which was added a few months ago. Given that 5.006001 is very old and
5.00473 is ancient and older versions were never installed on any RHEL
still supported by rpmforge, these Requires lines could probably be
safely omitted.
I also noted that the SRPM for perl-DBD-Pg-2.17 (didn't look at the
others) now has "el5" in the name. Maybe that was intended only for
RHEL5 and built for the other versions by mistake?
hp
_______________________________________________
suggest mailing list
suggest at lists.rpmforge.net
http://lists.rpmforge.net/mailman/listinfo/suggest

[Christoph Maser]

Post by Peter J. Holzer
[Resent because it was rejected because I used a wrong sender address -
apologies if this turns up twice]
Several perl modules have broken dependencies on rhel4.
perl-DBD-Pg-2.17.1-1.el4.rf requires perl >= 5.006001
perl-Module-Build-0.3603-1.el4.rf requires perl >= 5.006001
perl-Regexp-Common-2010010201-1.el4.rf requires perl >= 5.00473
rpm -q --provides perl
...
perl = 4:5.8.8-2.el4s1

Actually it seems you are wrong


yum provides "perl >= 5.006001" gives me this:

perl.x86_64 3:5.8.5-49.el4
base
Matched from:
perl >= 5.006001


Also installing those modules went just fine for me. What exactly is the
problem you are having?

[Pavel Kankovsky]

Post by Christoph Maser
perl.x86_64 3:5.8.5-49.el4

3:5.8.5-49.el4 is greater than 5.006001 according to rpm, isn't it?

The dependencies are broken because they do not really check Perl version:
the module expects at least 5.6.1 but any 5.x for x>=1 would satisfy
its dependency perl >= 5.006001.

On the other hand, it is quite unlikely Perl packaged for a certain distro
version would not be good enough for a module packaged for the same distro
version.

[Dave B]

This is definitely broken on RHEL4 w.r.t. up2date .

On everyone one of our machines...


up2date -l

Fetching Obsoletes list for channel: rhel-i386-as-4...

Fetching rpm headers...
########################################

Name Version Rel
Arch
----------------------------------------------------------------------------------------
perl 5.8.5 53.el4
i386
perl-suidperl 5.8.5 53.el4
i386

up2date -u perl

Fetching Obsoletes list for channel: rhel-i386-as-4...

Fetching rpm headers...
########################################

Name Version Rel
A
rch
--------------------------------------------------------------------------------
--------
perl 5.8.5
53.el4
i386


Testing package set / solving RPM inter-dependencies...
There was a package dependency problem. The message was:

Unresolvable chain of dependencies:
perl-DBD-Pg-2.17.1-1.el4.rf requires perl >= 5.006001




--

********************************
David William Botsch
Programmer/Analyst
CNF Computing
botsch at cnf.cornell.edu
********************************

[Dave B]

If up2date is broken, fine... unfortunately, I think RHEL4 is in a state
where that particular bug won't be fixed by redhat, now.

So, it would be good if the appropriate packages from rpmforge could be
patched to work around the problem. Once done, please bump the version
numbers so that yum will install the new packages over the ones w. the
incorrect dependencies.

thanks.

On Thu, 2010-06-10 at 12:00 +0100, suggest-request at lists.rpmforge.net

Re: [suggest] broken dependencies for some perl modules on

[Dave B]

Though, perhaps not all of them are broken?

I think both myself and someone else have mentioned just the same 3
packages causing the issue.

On Fri, 2010-06-11 at 12:00 +0100, suggest-request at lists.rpmforge.net

Message: 2
Date: Fri, 11 Jun 2010 09:57:00 +0200
From: Christoph Maser <cmaser at gmx.de>
Subject: Re: [suggest] broken dependencies for some perl modules on
RHEL4
To: suggest at lists.rpmforge.net
Message-ID: <1276243020.12228.36.camel at HUB8071NC4.financial.com>
Content-Type: text/plain; charset="UTF-8"

Post by Dave B
If up2date is broken, fine... unfortunately, I think RHEL4 is in a state
where that particular bug won't be fixed by redhat, now.
So, it would be good if the appropriate packages from rpmforge could be
patched to work around the problem. Once done, please bump the version
numbers so that yum will install the new packages over the ones w. the
incorrect dependencies.
thanks.

find . -name "perl-*" | xargs grep -l "perl .. 5.00"| wc -l
returns 127, so we are talking of ~100 packages to edit.

[Peter J. Holzer]

[Resent because it was rejected because I used a wrong sender address -
apologies if this turns up twice]

Several perl modules have broken dependencies on rhel4.

For example:

perl-DBD-Pg-2.17.1-1.el4.rf requires perl >= 5.006001
perl-Module-Build-0.3603-1.el4.rf requires perl >= 5.006001
perl-Regexp-Common-2010010201-1.el4.rf requires perl >= 5.00473

However, RHEL4 uses a different numbering scheme:

rpm -q --provides perl
...
perl = 4:5.8.8-2.el4s1

and 4:5.8.8 apparently isn't greater than 5.006001, although it should
be (5.8.8 is 5.008008 in the perl world, but of course RPM cannot know
this).

The culprit seems to be an explicit Requires line in the spec files
which was added a few months ago. Given that 5.006001 is very old and
5.00473 is ancient and older versions were never installed on any RHEL
still supported by rpmforge, these Requires lines could probably be
safely omitted.

I also noted that the SRPM for perl-DBD-Pg-2.17 (didn't look at the
others) now has "el5" in the name. Maybe that was intended only for
RHEL5 and built for the other versions by mistake?

hp
--
_ | Peter J. Holzer | Auf jedem Computer sollte der Satz Ludwigs II
|_|_) | Sysadmin WSR | eingepr?gt stehen: "Ein ewig R?tsel will ich
| | | hjp at wsr.ac.at | bleiben, mir und andern."
__/ | http://www.hjp.at/ | -- Wolfram Heinrich in desd
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
URL: <http://lists.repoforge.org/pipermail/users/attachments/20100607/fedd300c/attachment.sig>

[Christoph Maser]

Thanks for reporting Peter. This happens as I replace autogernerated
dependecies by rpmbuild through autogenerated dependencies from CPAN
metadata. I will have a look at it.

Chris

Post by Peter J. Holzer
[Resent because it was rejected because I used a wrong sender address -
apologies if this turns up twice]
Several perl modules have broken dependencies on rhel4.
perl-DBD-Pg-2.17.1-1.el4.rf requires perl >= 5.006001
perl-Module-Build-0.3603-1.el4.rf requires perl >= 5.006001
perl-Regexp-Common-2010010201-1.el4.rf requires perl >= 5.00473
rpm -q --provides perl
...
perl = 4:5.8.8-2.el4s1
and 4:5.8.8 apparently isn't greater than 5.006001, although it should
be (5.8.8 is 5.008008 in the perl world, but of course RPM cannot know
this).
The culprit seems to be an explicit Requires line in the spec files
which was added a few months ago. Given that 5.006001 is very old and
5.00473 is ancient and older versions were never installed on any RHEL
still supported by rpmforge, these Requires lines could probably be
safely omitted.
I also noted that the SRPM for perl-DBD-Pg-2.17 (didn't look at the
others) now has "el5" in the name. Maybe that was intended only for
RHEL5 and built for the other versions by mistake?
hp
_______________________________________________
suggest mailing list
suggest at lists.rpmforge.net
http://lists.rpmforge.net/mailman/listinfo/suggest

[Christoph Maser]

Post by Peter J. Holzer
[Resent because it was rejected because I used a wrong sender address -
apologies if this turns up twice]
Several perl modules have broken dependencies on rhel4.
perl-DBD-Pg-2.17.1-1.el4.rf requires perl >= 5.006001
perl-Module-Build-0.3603-1.el4.rf requires perl >= 5.006001
perl-Regexp-Common-2010010201-1.el4.rf requires perl >= 5.00473
rpm -q --provides perl
...
perl = 4:5.8.8-2.el4s1

Actually it seems you are wrong


yum provides "perl >= 5.006001" gives me this:

perl.x86_64 3:5.8.5-49.el4
base
Matched from:
perl >= 5.006001


Also installing those modules went just fine for me. What exactly is the
problem you are having?

[Pavel Kankovsky]

Post by Christoph Maser
perl.x86_64 3:5.8.5-49.el4

3:5.8.5-49.el4 is greater than 5.006001 according to rpm, isn't it?

The dependencies are broken because they do not really check Perl version:
the module expects at least 5.6.1 but any 5.x for x>=1 would satisfy
its dependency perl >= 5.006001.

On the other hand, it is quite unlikely Perl packaged for a certain distro
version would not be good enough for a module packaged for the same distro
version.

[Dave B]

This is definitely broken on RHEL4 w.r.t. up2date .

On everyone one of our machines...


up2date -l

Fetching Obsoletes list for channel: rhel-i386-as-4...

Fetching rpm headers...
########################################

Name Version Rel
Arch
----------------------------------------------------------------------------------------
perl 5.8.5 53.el4
i386
perl-suidperl 5.8.5 53.el4
i386

up2date -u perl

Fetching Obsoletes list for channel: rhel-i386-as-4...

Fetching rpm headers...
########################################

Name Version Rel
A
rch
--------------------------------------------------------------------------------
--------
perl 5.8.5
53.el4
i386


Testing package set / solving RPM inter-dependencies...
There was a package dependency problem. The message was:

Unresolvable chain of dependencies:
perl-DBD-Pg-2.17.1-1.el4.rf requires perl >= 5.006001




--

********************************
David William Botsch
Programmer/Analyst
CNF Computing
botsch at cnf.cornell.edu
********************************

[Dave B]

If up2date is broken, fine... unfortunately, I think RHEL4 is in a state
where that particular bug won't be fixed by redhat, now.

So, it would be good if the appropriate packages from rpmforge could be
patched to work around the problem. Once done, please bump the version
numbers so that yum will install the new packages over the ones w. the
incorrect dependencies.

thanks.

On Thu, 2010-06-10 at 12:00 +0100, suggest-request at lists.rpmforge.net

Re: [suggest] broken dependencies for some perl modules on

[Dave B]

Though, perhaps not all of them are broken?

I think both myself and someone else have mentioned just the same 3
packages causing the issue.

On Fri, 2010-06-11 at 12:00 +0100, suggest-request at lists.rpmforge.net

Message: 2
Date: Fri, 11 Jun 2010 09:57:00 +0200
From: Christoph Maser <cmaser at gmx.de>
Subject: Re: [suggest] broken dependencies for some perl modules on
RHEL4
To: suggest at lists.rpmforge.net
Message-ID: <1276243020.12228.36.camel at HUB8071NC4.financial.com>
Content-Type: text/plain; charset="UTF-8"

Post by Dave B
If up2date is broken, fine... unfortunately, I think RHEL4 is in a state
where that particular bug won't be fixed by redhat, now.
So, it would be good if the appropriate packages from rpmforge could be
patched to work around the problem. Once done, please bump the version
numbers so that yum will install the new packages over the ones w. the
incorrect dependencies.
thanks.

find . -name "perl-*" | xargs grep -l "perl .. 5.00"| wc -l
returns 127, so we are talking of ~100 packages to edit.