Description of problem: Our m17n-db-1.3.3 is not using upstream's tarball. :-( Steps to Reproduce: 1. md5sum m17n-db-1.3.3.tar.gz Actual results: cc7645216d8eedaecb05d7c55a324c0a m17n-db-1.3.3.tar.gz Expected results: a2aec22334c108565cc466d80a66292c m17n-db-1.3.3.tar.gz Additional info: We should always ship the unmodified pristine upstream source.
Hi Jens, The changes in MD5's can be due to the fact that we ship si-wijesekera-without-predit our tarball, whereas the upstream ships it with the preedit. When contributing to the upstream, I have mentioned this point. Thanks, Mayank
Yep that is the point of this bug: all changes should be made as patches applied in the spec file, not by modifying the tarball.
Fixed in m17n-db-1_3_3-41_fc7
it is fixed, checked with m17n-db-1_3_3-41.fc7