+++ This bug was initially created as a clone of Bug #217318 +++ 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
Fixed in m17n-db-1_3_3-39_fc6, pushed for updates.
Our Version 41dee6d06743b83a6950d5d0a500cef6 m17n-db-1.3.4.tar.gz - our extracted srpm from m17n-db-1.3.4-3.fc7.src.rpm Upstream version 41dee6d06743b83a6950d5d0a500cef6 m17n-db-1.3.4.tar.gz - upstream tar.gz from http://www.m17n.org/m17n-lib-download/m17n-db-1.3.4.tar.gz Both the md5sums checksums are matching, hence resolving this bug.