Red Hat Bugzilla – Bug 217318
m17n-db not using upstream tarball
Last modified: 2007-11-30 17:11:50 EST
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
We should always ship the unmodified pristine upstream source.
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
When contributing to the upstream, I have mentioned this point.
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