On Wed, Jan 08, 2014 at 12:19:37PM +0000, António Meireles wrote: > meanwhile latest conary=@fl:2-devel is not building... in the past i was > being reverting 3 upstream commits - '757a858', '2c2ca3e', 'bfbd22a' > because with them applied i wasn't been able to get rmake to work at all > [rmake was complaining about not being able to find 'suitable contexts' on > startup] . *If* we take those reverts off conary would, naturally, build > and work nicelly but rmake shouldn't work, as is, on any box with that > conary on the rmake host. Michael, can you confirm that this is is still an > issue or that it has been fixed en passant by recent conary commits, and if > so take a look plz ? [ i don't see any moves in rmake side that would had > helped in that front]
Current rmake and conary are known to work with each other. The config work in conary temporarily broke rmake but that was fixed. The resolver cache I need to unrevert in rmake but there is a configuration option to turn it off if it breaks (useresolvercache) so if it breaks we can file an RMK issue and temporarily turn it off until the issue is resolved. _______________________________________________ Foresight-devel mailing list [email protected] https://lists.foresightlinux.org/mailman/listinfo/foresight-devel
