You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bigtop.apache.org by "Wing Yew Poon (JIRA)" <ji...@apache.org> on 2013/07/19 23:56:48 UTC
[jira] [Created] (BIGTOP-1033) itest-common:
Wing Yew Poon created BIGTOP-1033:
-------------------------------------
Summary: itest-common:
Key: BIGTOP-1033
URL: https://issues.apache.org/jira/browse/BIGTOP-1033
Project: Bigtop
Issue Type: Bug
Components: Tests
Affects Versions: 0.6.0
Reporter: Wing Yew Poon
Assignee: Wing Yew Poon
Fix For: 0.7.0
This issue pertains to bigtop-test-framework, not bigtop-tests.
When running the package tests, specifically upgrade tests, on debian platforms, doing "env DEBIAN_FRONTEND=noninteractive apt-get -y install ${pkg.name}" is not enough. dpkg will prompt you as to what to do about conf files that have been modified, and the tests will fail because they don't respond to the prompts.
According to http://raphaelhertzog.com/2010/09/21/debian-conffile-configuration-file-managed-by-dpkg/, you can use --force-conf* options; in particular
--force-confold: do not modify the current configuration file, the new version is installed with a .dpkg-dist suffix. With this option alone, even configuration files that you have not modified are left untouched. You need to combine it with --force-confdef to let dpkg overwrite configuration files that you have not modified.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira