bikramjit, if you can help us clean it up I will personally buy you a beer. Seriously
Here's the deal: the way to run package tests is pretty simple right now, just take a look at how we do it on jenkins. Essentially all you have to do is checkout the workspace in a VM (DO NOT RUN IT ON YOUR BOX) and then:
mvn -f bigtop-tests/test-execution/package/pom.xml clean verify
You have to make sure that REPO_FILE_URL points to one of the same repo files you'd wget/curl in order to install Bigtop's trunk from here: http://bigtop01.cloudera.org:8080/view/Bigtop-trunk/job/Bigtop-trunk-Repository/
Once the package tests are done running you'll see the results of the testing in bigtop-tests/test-execution/package/target/failsafe-reports/*.xml
You can go line by line trying to see what's wrong or you can use one of the visualization tools.
The basic idea is to update the .xml manifest files that we have under bigtop-tests/test-artifacts/package/src/main/resources to match what's currently inside of the packages. For not its mostly little stuff like metadata not matching, etc. But every bit helps.
Finally, I would really appreciate if you could start up a wiki summarizing your experience doing package manifest cleanup. Future Bigtop contributors will buy you beer
And of course it is totally ok to drop by. Reach out to me via email to set date/time.