Red Hat Bugzilla – Bug 190292
RFE: Module::Build has been upgraded to 0.28
Last modified: 2007-11-30 17:11:31 EST
Description of problem:
Module::Build has been upgraded to 0.28, this one does not depend on an old
version of YAML, so YAML can be upgraded too.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
I see that you are pushing a new version of perl-Module-Build into mock, but I'm
wondering if increasing the epoch is the correct solution here. At the next
minor release of this package, there will be four digits in the minor version
again - and the same problems shows up. As a consequence you have to up the
epoch a lot of times going forward, and automatic dependency resolving becomes
How about using 0.2800 as the version of the package instead of 1:0.28? This
will be greater than the existing 0.26xx package which is there today.
But I guess this has to be applied consequently, and that probably means that
the automatic resolving of perl dependendcies in rpm should be considered
I really don't like having different version numbers than upstream (even if it
is just an extra 00). Ideally, upstream should be educated in rpm's idea of
(In reply to comment #2)
> I really don't like having different version numbers than upstream (even if it
> is just an extra 00). Ideally, upstream should be educated in rpm's idea of
> version comparison.
Can we get them to listen? Seems like there is a bug in the META.yml of the
upstream package too, since it doesn't list YAML as a requirement or a recommends.
0.2801 is out
Thanks for the heads up.