On 03/29/2013, Adam Williamson wrote: > Sure, we knew it was yum. But working around the problem using an F18 yum build wouldn't be a good way to go about things, because it's not like we can ship F19 or even the final Alpha with an F18 yum build. What I had in mind was running yum.fc18 on the machine doing the compose, but putting yum.fc19 into the composed result, just like any other .fc19 package. This would be a kind of "bootstrap" operation: use the old tool yum.fc18, but the new data yum.fc19, to produce the new result. I believe this had a fair chance of working to produce a .fc19 compose which was valid for testing, including being "the right size". -- -- test mailing list test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
