11 May
2006
11 May
'06
08:19
On Thursday 11 May 2006 11:59, Michael Schroeder wrote: > On Thu, May 11, 2006 at 11:50:28AM +0400, Dmitry Mishin wrote: > > now I have following issues: > > 1) From log: > > + /usr/src/packages/SOURCES/install-configs /usr/src/packages/SOURCES > > /usr/src/packages/BUILD/kernel-source-2.6.16_28_ve026test009 1.1 > > /var/tmp/rpm-tmp.75797: line 46: > > /usr/src/packages/SOURCES/install-configs: Permission denied > > error: Bad exit status from /var/tmp/rpm-tmp.75797 (%build) > > Seems that file permissions are not preserved during upload. > > Yes, all files are set to 644. Please add a "chmod" statement > to your specfile. Strange issue. At the same time, + /usr/src/packages/SOURCES/guards x86_64 executed without errors. What did I miss? OpenVZ SUSE kernel is indeed SUSE kernel with OpenVZ patch. If it will be required to add multiple chroots in each kernel-*.spec, special for buildservice, it is not good for us. Does anybody tried to build SUSE kernel in buildservice? > > > 2) trigger-rebuild doesn't work > > Frontend issue, the backend supports it but it's currently a noop > in the fronend. > > > 3) Is it possible to specify target on per package base, not per-project? > > At least, enable/disable them for some packages. > > The target configuration (aka repository search paths) is always > global to a project. But we plan to add support for disableing > targets/architectures on a per package base. > > > 4) FC5 > > x86_64 expansion error nothing provides autoconf > > Is it known bug? It's status? > > Nobody has uploaded the FC5 x86_64 rpms into the system. I'm > actually a bit surprised that you got the error message, the > backend should just ignore the architecture. I'll check the code... > > Cheers, > Michael. -- Thanks, Dmitry.