Currently I am still using a script I wrote for cooking the groups. The script pulls in the local conary and cooks the group.
>cat conary_local #!/bin/bash export CONARY="/home/bsmith/$(arch)/conary/bin/conary" export CVC="/home/bsmith/$(arch)/conary/bin/cvc" >cat cookgroups #!/bin/bash source ./conary_local time $CVC cook --no-deps --allow-flavor-change 'group-conary-packages[is:x86]' 'group-conary-packages[is:x86_64]' I will work on getting mirrorball configured for building groups on the common label -- Brett C. Smith [email protected] Sr Software Developer Platform Deployment Technologies (919)531-6635 -- x16635 ________________________________________ From: Foresight-devel <[email protected]> on behalf of Michael K. Johnson <[email protected]> Sent: Sunday, March 23, 2014 9:22 AM To: [email protected] Subject: [Foresight-devel] Re: Working around package issues in import On Sat, Mar 22, 2014 at 10:45:47PM -0400, Michael K. Johnson wrote: > I also built a new conary to fix the perl-PerlIO-gzip problem. Brett, buildgroups f20s1-c failed, so I don't know what context you are building the f20s1-c group-conary-packages. How have you been building group-conary-packages so far? This meant that perl-PerlIO-gzip is still failing until we get the new group-conary-packages built. Then it should either succeed or find a new error. ☺ _______________________________________________ Foresight-devel mailing list [email protected] https://lists.foresightlinux.org/mailman/listinfo/foresight-devel _______________________________________________ Foresight-devel mailing list [email protected] https://lists.foresightlinux.org/mailman/listinfo/foresight-devel
