Hi, is it possible to build SuSE kernels in buildservice? ----------------------------------------------------------------- I have the following modifications for kernel-bigsmp.spec: 23c23 < Release: 28 ---
Release: 1.1
----- building kernel-bigsmp.spec (user abuild) ----------------------------------------------------------------- ----------------------------------------------------------------- chmod: cannot access `/usr/src/packages/SOURCES/make-symsets': No such file or directory error: Architecture is not included: x86_64 full log may be accessed at home:openvz/kernel/ -- Thanks, Dmitry.
On Wed, May 10, 2006 at 07:44:07PM +0400, Dmitry Mishin wrote:
is it possible to build SuSE kernels in buildservice? ----------------------------------------------------------------- I have the following modifications for kernel-bigsmp.spec: 23c23 < Release: 28 ---
Release: 1.1
----- building kernel-bigsmp.spec (user abuild) ----------------------------------------------------------------- ----------------------------------------------------------------- chmod: cannot access `/usr/src/packages/SOURCES/make-symsets': No such file or directory error: Architecture is not included: x86_64
full log may be accessed at home:openvz/kernel/
This error happened because the build started when only a part of the sources were uploaded. The current situation is the correct one: The build service doesn't build a package at all ;-). Unfortunatelly the error handling is a bit bad, so you don't see the cause of this in the user interface. What's going on is this: your sources contain multiple specfiles, so the build service doesn't know which to use. In this case, it checks if only one specfile starts with the package name. If this is the case, it uses this specfile, otherwise (as it is the case with your package), it is an error and no package gets built. To resolve this, you should rename your package to "kernel-source". To build the kernel flavors, create new packages "kernel-default" and so on and use the "source link" mechanism to link the "kernel-source" sources into the kernel-flavor packages. Cheers, Michael. -- Michael Schroeder mls@suse.de main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);}
Thanks, 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. 2) trigger-rebuild doesn't work 3) Is it possible to specify target on per package base, not per-project? At least, enable/disable them for some packages. 4) FC5 x86_64 expansion error nothing provides autoconf Is it known bug? It's status? On Wednesday 10 May 2006 20:29, Michael Schroeder wrote:
On Wed, May 10, 2006 at 07:44:07PM +0400, Dmitry Mishin wrote:
is it possible to build SuSE kernels in buildservice? ----------------------------------------------------------------- I have the following modifications for kernel-bigsmp.spec: 23c23 < Release: 28 ---
Release: 1.1
----------------------------------------------------------------- ----- building kernel-bigsmp.spec (user abuild) ----------------------------------------------------------------- ----------------------------------------------------------------- chmod: cannot access `/usr/src/packages/SOURCES/make-symsets': No such file or directory error: Architecture is not included: x86_64
full log may be accessed at home:openvz/kernel/
This error happened because the build started when only a part of the sources were uploaded.
The current situation is the correct one: The build service doesn't build a package at all ;-). Unfortunatelly the error handling is a bit bad, so you don't see the cause of this in the user interface.
What's going on is this: your sources contain multiple specfiles, so the build service doesn't know which to use. In this case, it checks if only one specfile starts with the package name. If this is the case, it uses this specfile, otherwise (as it is the case with your package), it is an error and no package gets built.
To resolve this, you should rename your package to "kernel-source". To build the kernel flavors, create new packages "kernel-default" and so on and use the "source link" mechanism to link the "kernel-source" sources into the kernel-flavor packages.
Cheers, Michael.
-- Thanks, Dmitry.
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.
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. -- Michael Schroeder mls@suse.de main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);}
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.
On Thu, May 11, 2006 at 12:19:10PM +0400, Dmitry Mishin wrote:
> > 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?
The specfile contains:
%(chmod +x %_sourcedir/{arch-symbols,guards,config-subst,check-for-config-changes,kabi-checks})
> 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.
I don't understand this. What multiple chroots?
> Does anybody tried to build SUSE kernel
> in buildservice?
Where's the problem?
Cheers,
Michael.
--
Michael Schroeder mls@suse.de
main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);}
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.
I don't understand this. What multiple chroots?
chmods, sorry
Does anybody tried to build SUSE kernel in buildservice?
Where's the problem?
problem is that there is no `chmod +x install-configs` in SUSE kernel-source.spec
Cheers, Michael.
-- Thanks, Dmitry.
On Thu, May 11, 2006 at 02:12:28PM +0400, Dmitry Mishin wrote:
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.
I don't understand this. What multiple chroots?
chmods, sorry
Does anybody tried to build SUSE kernel in buildservice?
Where's the problem?
problem is that there is no `chmod +x install-configs` in SUSE kernel-source.spec
Well, that's a bug in the specfile, the other specfiles have it. Just add it. Cheers, Michael. -- Michael Schroeder mls@suse.de main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);}
Where's the problem?
problem is that there is no `chmod +x install-configs` in SUSE kernel-source.spec
Well, that's a bug in the specfile, the other specfiles have it. Just add it. Already done, should I post respective bug to bugzilla also?
To build the kernel flavors, create new packages "kernel-default" and so on and use the "source link" mechanism to link the "kernel-source" sources into the kernel-flavor packages. How to perform this?
-- Thanks, Dmitry.
On Thu, May 11, 2006 at 02:31:25PM +0400, Dmitry Mishin wrote:
Where's the problem?
problem is that there is no `chmod +x install-configs` in SUSE kernel-source.spec
Well, that's a bug in the specfile, the other specfiles have it. Just add it. Already done, should I post respective bug to bugzilla also?
No need, I'll talk to the kernel maintaines.
To build the kernel flavors, create new packages "kernel-default" and so on and use the "source link" mechanism to link the "kernel-source" sources into the kernel-flavor packages.
How to perform this?
There's "Link Package from other Project" right under "Add Package". Enter "home:openvz" as name of the original project and "kernel-source" as name of the package. The press "create link". Oh wait, this doesn't work, as you can't enter the package name. Stupid interface, I'll talk with the frontend folks. Just send me the list of packages you need and I'll create the links. Cheers, Michael. -- Michael Schroeder mls@suse.de main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);}
participants (2)
-
Dmitry Mishin -
Michael Schroeder