On Tuesday 26 January 2010 17:12:48 Moray Henderson wrote: > Kern Sibbald wrote: > >Hello, > > > >Unfortunately, it is always much more complicated than one would want. > > True from my end too - which is why the patch was in the message body > rather than a real attachment ;-) > > >What you show below looks good to me. > > > >Could you send me the patch as an attachment to avoid all problems with > >mailer > >wrap and such? Thanks. > > Attached properly now. My rpmbuild command still fails with > > mock-chroot> rpmbuild -D 'build_centos5 1' -D 'build_sqlite 1' -ba > bacula.spec > ... > symlinked /usr/lib/debug/usr/lib/libbac.so.1.0.0.debug to > /usr/lib/debug/usr/lib/libbac.so.debug > symlinked /usr/lib/debug/usr/lib/libbacsql.so.1.0.0.debug to > /usr/lib/debug/usr/lib/libbacsql.so.1.debug > 8095 blocks > + /usr/lib/rpm/redhat/brp-compress > + /usr/lib/rpm/redhat/brp-strip-static-archive /usr/bin/strip > + /usr/lib/rpm/redhat/brp-strip-comment-note /usr/bin/strip > /usr/bin/objdump > + /usr/lib/rpm/brp-python-bytecompile > + /usr/lib/rpm/redhat/brp-java-repack-jars > error: Bad owner/group: /builddir/build/SPECS/bacula.spec > > > RPM build errors: > Bad owner/group: /builddir/build/SPECS/bacula.spec > > > Any immediate ideas?
I have never seen that problem before, but then I always build as non-root, so I don't have permission problems. It looks like you are working in some sort of chroot setup, which complicates everything -- you probably need to move /etc/passwd, ... into it. IMO it is much easier to use .rpmmacros to work in your home directory. It takes a few tries to set it up the first time, but after that, it saves using root and possibly wrecking your OS or fiddling with chroots. > I'll have a look when I can, but I'm about to > start a major OS upgrade on a main production server, so I'll be a bit > busy for a while... OK, no problem. Your help and comments are appreciated. > > You should really aim for a .spec in the tarball that works to build the > rpms entirely from that tarball. Unfortunately unless someone takes an interest in working on it, it is pretty unlikely to happen, because getting the spec files working correctly is always a considerable effort, and it is not something that I personally can work on at the same time we are doing a release. Typically within a week or two of the source release Scott produces the RedHat rpms, and at that time everything is in sync. Best regards, Kern > > > Moray. > "To err is human. To purr, feline" ------------------------------------------------------------------------------ The Planet: dedicated and managed hosting, cloud storage, colocation Stay online with enterprise data centers and the best network in the business Choose flexible plans and management services without long-term contracts Personal 24x7 support from experience hosting pros just a phone call away. http://p.sf.net/sfu/theplanet-com _______________________________________________ Bacula-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/bacula-devel
