On Wed, Oct 14, 2009 at 10:13:33AM -0400, Michael K. Johnson wrote: > We're definitely getting closer to being able to do the import. > My current plan is to try to set aside time next week to start > a test import into a throwaway repository, making sure that > things are sane before committing stuff that should live forever. > :)
I guess I should report progress: if you are following Conary commits via http://lists.rpath.com/mailman/listinfo/conary-commits or http://hg.rpath.com/conary or http://hg.rpath.com/conary/rss-log or http://bitbucket.org/rpathsync/conary/ you have seen a lot of commit traffic. It is practically all related to this. Some of it is stuff that we already knew needed to be done for these RPM "capsules", and other bits are specifically driven by test imports of real RPMs into throwaway repositories. Some work has been done elsewhere; for example, a recent rMake new feature is an important part of this work; rMake now looks at /usr/bin/conary to determine which python to use for rMake in the chroot. I'm sorry I forgot to follow up earlier -- it's because of being so busy doing test/fix cycles. (And it's not just me, as you can tell if you look at the commits!) So right now, the most direct way to follow progress is to follow Conary commits... :) Separately, Andy diagnosed the problem with anaconda templates that is shared between Mark's work on updating anaconda for fl:2 and the work that needs to be done for anaconda for Boots. See https://issues.rpath.com/browse/RMK-1006 for more details. I know that a lack of a progress report can give the impression of a lack of progress, so I wanted to report at least some of the progress that has been made here. _______________________________________________ Foresight-devel mailing list Foresight-devel@lists.rpath.org http://lists.rpath.org/mailman/listinfo/foresight-devel
