So in a koji/mock build, it supplied by the fedora-release pkg that I add to the build group?
Is there some magic to get a new release going? I was expecting/assuming koji shoves what it knows based on tag, common/branches Doug On Tue, May 18, 2010 at 3:45 PM, Jesse Keating <[email protected]> wrote: > On Tue, 2010-05-18 at 15:09 -0400, Doug Reiland wrote: >> Who/how does /etc/rpm.macros.dist get built in the mock environment? >> >> I am building from scm and it doesn't match what I think it should. >> For example, >> >> %fedora 12 >> %dist .fc12 >> %fc12 1 >> >> instead of >> $fedora 13 >> %dist .fc13 >> %fc13 1 >> >> common/branches and rpms/<package>/*/branch look ok. >> -- >> buildsys mailing list >> [email protected] >> https://admin.fedoraproject.org/mailman/listinfo/buildsys > > That generally comes from a *-release package. Within Fedora, it comes > from fedora-release. $ rpm -qf /etc/rpm/macros.dist > fedora-release-13-0.7.noarch > > -- > Jesse Keating > Fedora -- Freedom² is a feature! > identi.ca: http://identi.ca/jkeating > > -- > buildsys mailing list > [email protected] > https://admin.fedoraproject.org/mailman/listinfo/buildsys > -- buildsys mailing list [email protected] https://admin.fedoraproject.org/mailman/listinfo/buildsys
