[10:01:02 CST(-0600)] <apetro__> and now it really is Thursday
[10:01:17 CST(-0600)] <apetro__> today's project: adding un-favoriting capability to Favorites
[10:01:35 CST(-0600)] <apetro__> with possible detour to migrate a CVS repo to Git.
[10:01:56 CST(-0600)] <tlev> note there is a topic branch for favorites
[10:05:50 CST(-0600)] <apetro__> I do love me some topic branches
[10:06:21 CST(-0600)] <apetro__> I may resist the urge to create an unfavorite sub-topic-branch branched off that topic branch
[12:39:23 CST(-0600)] <apetro__> so, banging my head against intportal database initialization again, of course
[12:40:03 CST(-0600)] <jwennmacher> what's the issue?
[12:41:17 CST(-0600)] <apetro__> check this out:
[12:42:27 CST(-0600)] <apetro__> https://gist.github.com/8339551
[12:43:21 CST(-0600)] <apetro__> https://gist.github.com/8339567
[12:43:36 CST(-0600)] <apetro__> (loving Sublime Gist support, incidentally)
[12:44:31 CST(-0600)] <apetro__> what I think I'm doing is successfully importing a favorite-lo user, successfully importing a fragment definition pointing at that user, and then failing in importing a fragment-layout pointing at that user
[12:44:43 CST(-0600)] <jwennmacher> did you look at the reports in target?
[12:45:04 CST(-0600)] <apetro__> yes, that's where those two gists are coming from
[12:45:43 CST(-0600)] <apetro__> former is the data-import.txt tightened down to show the relevant successes and failure, latter is the file specifically about the failing-to-import fragment layout definition
[12:45:45 CST(-0600)] <jwennmacher> no detailed text file?
[12:46:18 CST(-0600)] <apetro__> https://gist.github.com/apetro/8339567 ? 
[12:46:43 CST(-0600)] <jwennmacher> yep
[12:47:37 CST(-0600)] <jwennmacher> what is your quickstart_entities/user/favorite-lo.user.xml file? Also look at the users table and see if that user is or is not present
[12:54:48 CST(-0600)] <apetro__> jwennmacher thanks, found it. had overlooked that `username` attribute hidden amongst the XML namespace cruft
[12:55:32 CST(-0600)] <apetro__> somehow I thought the username was implied from the filename. maybe should be an error or warning when it doesn't match the expectation set by the filename. added that check to my ever-growing list of rainy day projects.