search for: debug_packag

...y RRD bindings Name: RubyRRDtool Version: 0.6.0 Release: 1 Epoch: 1 License: MIT Group: Application/Development Source0: %{name}-%{version}.tgz URL: http://rubyforge.org/projects/rubyrrdtool/ BuildRoot: %{_tmppath}/%{name}-root Requires: rrdtool, ruby BuildRequires: ruby, gcc, rrdtool-devel %define debug_package %{nil} %description RRD bindings for Ruby. %prep %setup -q %build ruby extconf.rb make %install install -D -m0644 RRDtool.so %{buildroot}/usr/lib/ruby/site_ruby/1.8/i386-linux/RRDtool.so %clean rm -rf %{buildroot} %post %postun %files %defattr(-, root, root) /usr/lib/ruby/site_ruby/1.8/i38...

...(in ~/.rpmmacros) and $TMPPATH (xz called by > find-debuginfo.sh uses it) and more parts of the build process used my > custom tmppath. But dwz still uses large temporary files in /tmp. > >> >> >> and if you do not need the debug packages, add >> >> %_enable_debug_packages 0 >> >> into your .rpmmacros file >> >> -- >> LF >> > > I tried disabling the debug packages but then rpmbuild just leaves the > debuginfo in the binaries and I ended up with a 30GB binary rpm. > > -A That sounds like the package hasn't...

Hi, Nux! Can you re-paste this cfg? The url is outdated. - robin On Tue, Dec 30, 2014 at 2:30 AM, Nux! <nux at li.nux.ro> wrote: > Hi, > > Here's how my epel-7-i386.cfg mock file looks like: > http://fpaste.org/164110/19877702/raw/ > > Do note the 32bit packages are unofficial and unsupported. RedHat does not > support 32bit in EL7. > > HTH > Lucian >

...seful for --resultdir variable subst config_opts['macros']['%dist'] = '.el7' config_opts['macros']['%vendor'] = 'Your Name Here' config_opts['macros']['%packager'] = 'username at example.org' config_opts['macros']['%debug_package'] = '%{nil}' config_opts['yum.conf'] = """ [main] cachedir=/var/cache/yum debuglevel=1 reposdir=/dev/null logfile=/var/log/yum.log retries=20 obsoletes=1 gpgcheck=0 assumeyes=1 syslog_ident=mock syslog_device= # repos [base] name=BaseOS baseurl=http://buildlogs...

Hi, All I test with ctdb-1.2.0-18.1, and there is a corefile. I want to analyze the corefile, but can't find the ctdb debuginfo. Could you tell me where to find the ctdb debuginfo? -- Best Regards. Yu Liao

Hello. What's the proper way to remove *all symbols* from ELF binaries when building packages with rpmbuild on CentOS? Seems that an out of the box rpmbuild install only discards debugging symbols (strip -g). That's the default configuration for %__os_install_post on CentOS, the step in charge on stripping binaries: $ rpmbuild --showrc (..) -14: __os_install_post

...he error. How can I tell >> rpmbuild to use an alternative temporary file location? > > Try to change %_tmppath in /usr/lib/rpm/macros or build in mock and place the whole chroot on a larger drive (/etc/mock/site-defaults.cfg). and if you do not need the debug packages, add %_enable_debug_packages 0 into your .rpmmacros file -- LF

...al machines to +libvirt-managed KVM, or Red Hat Enterprise Virtualization. It can import a +variety of guest operating systems from libvirt-managed hosts and VMware ESX. + + +%prep +%setup -q -n %{name}-v%{version} + +%build +%{__perl} Build.PL +./Build + +# Perl doesn't need debuginfo +%define debug_package %{nil} + +%install +rm -rf $RPM_BUILD_ROOT +./Build install \ + --destdir $RPM_BUILD_ROOT \ + --installdirs vendor \ + --install_path locale=%{_datadir}/locale \ + --install_path confdoc=%{_mandir}/man5 + +# Create lib directory, used for holding software to be installed in guests +sta...

modified ovirt-node-image for inclusion in Fedora Removes ovirt-node-image-pxe sub package adds get-ovirt-node-image script adds generate-ovirt-node-pxe-tree script (replaces subpackage) moved all the scripts/tools into tools subdir adds new rpm, ovirt-node-recipe includes tools, manifests, and ks file/recipe Process for building upstream ovirt node packages.... 1. Build ovir-node.rpm in koji

The following two patches fixes / reimplements the oVirt appliance project, installing the entire oVirt stack including all server and node components on one machine. These patches are intended to be checked out and used to build the appliance rpm, after which it is installed provides the /usr/sbin/ovirt-appliance-ctrl script to install/uninstall the appliance. The first patch merely removes