It sounds like Michael Mundy fixed an issue in Makefile.common, but he didn't commit his change, either because he doesn't have write access to dev_container or because he knows that Tom prefers not to have random people make changes to that file.

Who is the right person to assign this to? Tom is on vacation, and I know Bob O. is overloaded. I could commit the change but can't easily test that it works.

Thanks,

Nomi

Begin forwarded message:

From: "Michael Mundy (JIRA)" <help@kbase.us>

Subject: [JIRA] (KBASE-147) MK_CONFIG rule in Makefile.common fails with no such file or directory error

Date: June 27, 2013 7:15:25 AM PDT

To: nlharris@lbl.gov

Michael Mundy created  KBASE-147 MK_CONFIG rule in Makefile.common fails with no such file or directory error Issue Type:  Bug Assignee: Meghan Drake Components: service Created: 27/Jun/13 9:14 AM Description: Line 32 of tools/Makefile.common has this rule: MK_CONFIG = $(TOOL_DIR)/mkcfg but in the tools directory the name of the script is mkcfg.pl. When running "make deploy" in KBaseFBAModeling that gives this error: /home/mmundy/kb/runtime/bin/perl ../../tools//mkcfg Can't open perl script "../../tools//mkcfg": No such file or directory make: *** [deploy-cfg] Error 2 I updated Makefile.common with the correct name of the script and the rule worked. I didn't see a dev_container service in the list to assign this issue. Project: KBase Priority:  Minor Reporter: Michael Mundy

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

_______________________________________________
Release-team mailing list
Release-team@lists.kbase.us
https://lists.kbase.us/mailman/listinfo/release-team