Due to an unfortunate mistake made by whoever bumped it last, net-misc/clusterssh-4.03.03 is still using the sources for 4.01_05 This is due to MODULE_VERSION still being defined as =4.01_05 This can be verified by looking in the Manifest: grep tar /usr/portage/net-misc/clusterssh/Manifest | cut -f1-3 -d" " DIST App-ClusterSSH-4.01_05.tar.gz 71502 This unfortunate mistake ultimately means you'll have to -r1 bump and destabilize at a minimum. Joys! Additionally, an important element to working with CPAN modules is ensuring their versions are normalised, because upstream versioning and Gentoo versioning are incompatible in surprising ways. 4.01_05 for instance should be in Gentoo as 4.10.500 4.03_03 should respectively be in Gentoo as 4.30.300 4.03_06 should likewise be in Gentoo as 4.30.600 The reason for this is, the "_" is considered "invisible", not significant by perl. So the above numbers are really just 4.0105 , 4.0303 and 4.0306 respectively. However, should upstream ever publish: 4.10_5 That would be 4.105 , and gentoo would consider that the same as 4.0105 And if upstream were to ever publish 4.02, gentoo would consider that smaller than 4.0105 Hence, we need to normalise the floats to decimals for consistency, and so: 4.01_05 -> 4.010500 -> 4/010/500 -> 4.10.500 4.03_03 -> 4.030300 -> 4/030/300 -> 4.30.300 4.03_06 -> 4.030600 -> 4/030/600 -> 4.30.600 At least, that is how it is under perl herd =) https://wiki.gentoo.org/wiki/Project:Perl/How_to_version-bump_dev-perl#Bumping_a_package https://wiki.gentoo.org/wiki/Project:Perl/perl-herd#Version_numbers_in_Gentoo_perl_ebuilds
Thanks for these thorough point and explanation which I agree with. clusterssh-4.30.600.ebuild is in tree now, maybe in a few open a STABLEREQ and we can get rid of the old ebuild ;)
