buildroot icon indicating copy to clipboard operation
buildroot copied to clipboard

Package buildroot for xen-api and related packages

Results 69 buildroot issues
Sort by recently updated
recently updated
newest added

RPM has an 'Obsoletes' tag which indicates that a new package replaces a previous package of a different name. This should be translated to the 'Replaces' tag in debian/control. http://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces

bug

makedeb asks the RPM library for the contents of the %build and %install rules in the spec file. RPM expands macros and interprets conditionals in these rules before returning the...

bug

Current failures on SRPMS: - [ ] configure-without-libdir-spec - [ ] hardcoded-library-path - [ ] invalid-license - [ ] invalid-url - [x] macro-in-%changelog - [ ] macro-in-comment - [ ]...

bug

This matches the Debian packaging guidelines better: public Python files should be in site-lib; private ones should be in /usr/lib/.

work item

Installing the SM code in the standard python place is probably the right thing to do but xapi now fails to find them on CentOS in /usr/lib/xapi/sm. We need to...

We currently don't specify version constraints on most of our package dependencies. We should add them, to prevent people from installing packages on unsuitable systems. For instance, we should mark...

work item

Most of our spec files hard code the Python library installation path to /usr/lib/python2.6/site-packages. We should be using the %python_sitelib macro, as described here: http://fedoraproject.org/wiki/Packaging:Python On Debian, Python package installation...

bug

We build some packages, such as libvirt, because historically we needed to tweak them. In many cases these tweaks are no longer needed so we can use the distribution packages.

enhancement

mock --resultdir= puts all mock's output, including its logs and rebuilt SRPMs, into We use this option to save the RPMs into the output directory, but we should copy only...

enhancement