Ticket #1087 (closed defect: fixed)

Opened 11 years ago

Last modified 11 years ago

Problems with 1.2.0 RPM build from git

Reported by: Jake Davis <[email protected]…> Owned by:
Priority: minor Milestone: Bcfg2 1.2.1 Release (Bugfix)
Component: bcfg2-server Version: 1.0
Keywords: Cc: [email protected]


While attempting to build rpms from a git checkout of the v1.2.0 tag following these instructions:

After "cd redhat; make" I get this error:

 error: File
 /root/VCS/git/bcfg2.davisj/redhat/build/bcfg2-1.2.0.tar.gz: No such
 file or directory
    make: *** [buildrpmdist] Error 1

And this one:

    RPM build errors:
        Installed (but unpackaged) file(s) found:
    make: *** [buildrpmdist] Error 1

The following patch seems to resolve both errors.

index 7533b98..f8f7795 100644
--- a/redhat/Makefile
+++ b/redhat/Makefile
@@ -22,7 +22,7 @@ VERSION := $(shell cat VERSION)
 RELEASE := $(shell cat RELEASE)
 DIRNAME := $(shell echo $${PWD})
 DIRBASE := $(shell basename $${PWD})
diff --git a/redhat/ b/redhat/
index be2375c..92593a5 100644
--- a/redhat/
+++ b/redhat/
@@ -205,6 +205,7 @@ fi
 %dir %{python_sitelib}/Bcfg2

Not that in later revisions of HEAD I also had to add "%{_sbindir}/bcfg2-test" to redhat/


Change History

comment:1 Changed 11 years ago by Jake Davis <[email protected]…>

Also, the bcfg2-web rpm that is built when using the misc/bcfg2.spec file from a tarball is not created when following the instructions to build from a git checkout.

comment:2 Changed 11 years ago by m4z <[email protected]…>

comment:3 Changed 11 years ago by

  • Owner changed from desai to
  • Status changed from new to assigned

comment:4 Changed 11 years ago by

  • Status changed from assigned to closed
  • Resolution set to fixed

WARNING! You need to establish a session before you can create or edit tickets. Otherwise the ticket will get treated as spam.


Add a comment

Modify Ticket

Change Properties
<Author field>
as closed
The resolution will be deleted. Next status will be 'reopened'

E-mail address and user name can be saved in the Preferences.

Note: See TracTickets for help on using tickets.