2:09 p.m.
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.
2:45 p.m.
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
buildsys(a)lists.fedoraproject.org
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
3:04 p.m.
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 <jkeating(a)redhat.com> 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
> buildsys(a)lists.fedoraproject.org
> 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
buildsys(a)lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/buildsys
3:05 p.m.
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 <jkeating(a)redhat.com> 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
> buildsys(a)lists.fedoraproject.org
> 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
buildsys(a)lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/buildsys
2:48 p.m.
On Tuesday 18 May 2010 02:09:43 pm 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.
fedora-release provides it
and RHEL-6 and up its provided in redhat-release
Dennis
5:57 p.m.
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,
If you wanted your own, look at adding a package to the build and srpm-build
build groups in a build tag. I use "buildsys-macros" for that whenever fedora-
release or epel-release is not available, of which you can find a few examples
here:
Custom kolab repository:
http://mirror.nl.ergo-project.org/repositories/feature-el5-
kolab/SRPMS/buildsys-macros-5-1.el5.kolab.src.rpm
Ruby 1.9.1 feature development:
http://mirror.nl.ergo-project.org/repositories/feature-f12-
ruby-1.9.1/SRPMS/buildsys-macros-12-1.fc12.fr191.src.rpm
-- Jeroen
5101
days inactive
5101
days old
buildsys@lists.fedoraproject.org
5 comments
4 participants
participants (4)
-
Dennis Gilmore -
Doug Reiland -
Jeroen van Meeuwen -
Jesse Keating