[opensuse-buildservice] Local build of package
Hi all! Please read the last paragraph of [1]. Is the situation really that bad? Isn't there a more simple way how to do the local build? What is --local-package switch for? I thought it is for building packages outside of the working copy, but it seems it isn't ... [1] http://v3.sk/~lkundrak/blog/entries/inspiron-12-opensuse.html -- Best Regards / S pozdravom, Pavol RUSNAK SUSE LINUX, s.r.o openSUSE Boosters Team Lihovarska 1060/12 PGP 0xA6917144 19000 Praha 9, CR prusnak[at]suse.cz http://www.suse.cz -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Am Montag, 9. November 2009 18:20:23 schrieb Pavol Rusnak:
Hi all!
Please read the last paragraph of [1]. Is the situation really that bad? Isn't there a more simple way how to do the local build? What is --local-package switch for? I thought it is for building packages outside of the working copy, but it seems it isn't ...
you can also use plain "build" script together with any repository or plain rpmbuild call. --local-package is when you do not want to have sources uploaded in a project, but you want to build it like part of the project on your workstation.
[1] http://v3.sk/~lkundrak/blog/entries/inspiron-12-opensuse.html
-- Adrian Schroeter SUSE Linux Products GmbH email: adrian@suse.de -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Mon, Nov 09, 2009 at 06:20:23PM +0100, Pavol Rusnak wrote:
Please read the last paragraph of [1]. Is the situation really that bad? Isn't there a more simple way how to do the local build? What is --local-package switch for? I thought it is for building packages outside of the working copy, but it seems it isn't ...
[1] http://v3.sk/~lkundrak/blog/entries/inspiron-12-opensuse.html
'mock' is Fedora's version of our 'build' package. You don't need a build service account to use it. Cheers, Michael. -- Michael Schroeder mls@suse.de SUSE LINUX Products GmbH, GF Markus Rex, HRB 16746 AG Nuernberg main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);} -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On 11/09/2009 06:41 PM, Michael Schroeder wrote:
'mock' is Fedora's version of our 'build' package. You don't need a build service account to use it.
Using 'build' ends with "*** /media/dvd/suse does not exist". Reading manpage reveals that one has to mount DVD media with RPMs. AFAIK mock can download all packages it needs using yum, so it hardly can be advertised as an alternative. We can try to hack 'osc build' (this would probably involve some server-side hacking) to be able to build locally and without OBS account. -- Best Regards / S pozdravom, Pavol RUSNAK SUSE LINUX, s.r.o openSUSE Boosters Team Lihovarska 1060/12 PGP 0xA6917144 19000 Praha 9, CR prusnak[at]suse.cz http://www.suse.cz -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Mon, Nov 09, 2009 at 06:58:28PM +0100, Pavol Rusnak wrote:
On 11/09/2009 06:41 PM, Michael Schroeder wrote:
'mock' is Fedora's version of our 'build' package. You don't need a build service account to use it.
Using 'build' ends with "*** /media/dvd/suse does not exist". Reading manpage reveals that one has to mount DVD media with RPMs. AFAIK mock can download all packages it needs using yum, so it hardly can be advertised as an alternative. We can try to hack 'osc build' (this would probably involve some server-side hacking) to be able to build locally and without OBS account.
As the name 'osc' suggests, it is intended for building build service packages. Don't try to misuse it for things it's not designed for. You should rather improve 'build' instead. Cheers, Michael. -- Michael Schroeder mls@suse.de SUSE LINUX Products GmbH, GF Markus Rex, HRB 16746 AG Nuernberg main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);} -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Nov 09, 09 19:02:36 +0100, Michael Schroeder wrote:
On Mon, Nov 09, 2009 at 06:58:28PM +0100, Pavol Rusnak wrote:
On 11/09/2009 06:41 PM, Michael Schroeder wrote:
'mock' is Fedora's version of our 'build' package. You don't need a build service account to use it.
I'd love to add this feature to obs!
Using 'build' ends with "*** /media/dvd/suse does not exist". Reading manpage reveals that one has to mount DVD media with RPMs. AFAIK mock can download all packages it needs using yum, so it hardly can be advertised as an alternative. We can try to hack 'osc build' (this would probably involve some server-side hacking) to be able to build locally and without OBS account.
As the name 'osc' suggests, it is intended for building build service packages. Don't try to misuse it for things it's not designed for. You should rather improve 'build' instead.
Why should the osc design forbid such local builds? As far as I can see, it can be implemented with read-only guest access (fate#306192) on the server side. The rest in osc itself should be simple. Call it 'osc mock' ? cheers, JW- -- o \ Juergen Weigert paint it green! __/ _=======.=======_ <V> | jw@suse.de back to ascii! __/ _---|____________\/ \ | 0911 74053-508 __/ (____/ /\ (/) | _____________________________/ _/ \_ vim:set sw=2 wm=8 SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On 11/09/2009 07:42 PM, Juergen Weigert wrote:
As the name 'osc' suggests, it is intended for building build service packages. Don't try to misuse it for things it's not designed for. You should rather improve 'build' instead.
AFAIK osc stands for openSUSE Commander, so there is no connection to BuildService directly from its name :-)
Why should the osc design forbid such local builds?
As far as I can see, it can be implemented with read-only guest access (fate#306192) on the server side. The rest in osc itself should be simple. Call it 'osc mock' ?
I would stick to 'osc build'. Osc has already A LOTS of subcommands and options. -- Best Regards / S pozdravom, Pavol RUSNAK SUSE LINUX, s.r.o openSUSE Boosters Team Lihovarska 1060/12 PGP 0xA6917144 19000 Praha 9, CR prusnak[at]suse.cz http://www.suse.cz -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Am Montag, 9. November 2009 19:42:37 schrieb Juergen Weigert:
On Nov 09, 09 19:02:36 +0100, Michael Schroeder wrote:
On Mon, Nov 09, 2009 at 06:58:28PM +0100, Pavol Rusnak wrote:
On 11/09/2009 06:41 PM, Michael Schroeder wrote:
'mock' is Fedora's version of our 'build' package. You don't need a build service account to use it.
I'd love to add this feature to obs!
We have it since a long time. Even before obs and it is an advantage IMHO that you do not need the complexity of the OBS infrastructure, if you don't need it's features.
Using 'build' ends with "*** /media/dvd/suse does not exist". Reading manpage reveals that one has to mount DVD media with RPMs. AFAIK mock can download all packages it needs using yum, so it hardly can be advertised as an alternative. We can try to hack 'osc build' (this would probably involve some server-side hacking) to be able to build locally and without OBS account.
As the name 'osc' suggests, it is intended for building build service packages. Don't try to misuse it for things it's not designed for. You should rather improve 'build' instead.
Why should the osc design forbid such local builds?
As far as I can see, it can be implemented with read-only guest access (fate#306192) on the server side. The rest in osc itself should be simple. Call it 'osc mock' ?
Where is the sense to create high load on our server, if you do not like to use it's functionality ? if you just want to build offline, just use the offline tool. Where is the advantage to use the online tool to do the same job as the offline tool ? -- Adrian Schroeter SUSE Linux Products GmbH email: adrian@suse.de -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Am Montag, 9. November 2009 19:56:30 schrieb Pavol Rusnak:
On 11/09/2009 07:42 PM, Juergen Weigert wrote: ..
Why should the osc design forbid such local builds?
As far as I can see, it can be implemented with read-only guest access (fate#306192) on the server side. The rest in osc itself should be simple. Call it 'osc mock' ?
I would stick to 'osc build'. Osc has already A LOTS of subcommands and options.
Creating buildinfo can create high load on the server. We will not scale good if this is used without sense. -- Adrian Schroeter SUSE Linux Products GmbH email: adrian@suse.de -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Nov 09, 09 19:56:31 +0100, Adrian Schröter wrote:
Am Montag, 9. November 2009 19:42:37 schrieb Juergen Weigert:
On Nov 09, 09 19:02:36 +0100, Michael Schroeder wrote:
On Mon, Nov 09, 2009 at 06:58:28PM +0100, Pavol Rusnak wrote:
On 11/09/2009 06:41 PM, Michael Schroeder wrote:
'mock' is Fedora's version of our 'build' package. You don't need a build service account to use it.
I'd love to add this feature to obs!
We have it since a long time. Even before obs and it is an advantage IMHO that you do not need the complexity of the OBS infrastructure, if you don't need it's features.
No, we dont. The scenario is this: I see a package in the build service, want to check out a copy, fix a bug, compile, test, ... and afterwards I want to send a patch, check in or submit. We don't have THAT, afaik.
if you just want to build offline, just use the offline tool. Where is the advantage to use the online tool to do the same job as the offline tool ?
What offline tool do you have in mind? puzzled, JW- -- o \ Juergen Weigert paint it green! __/ _=======.=======_ <V> | jw@suse.de back to ascii! __/ _---|____________\/ \ | 0911 74053-508 __/ (____/ /\ (/) | _____________________________/ _/ \_ vim:set sw=2 wm=8 SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Am Montag, 9. November 2009 22:04:44 schrieb Juergen Weigert:
On Nov 09, 09 19:56:31 +0100, Adrian Schröter wrote:
Am Montag, 9. November 2009 19:42:37 schrieb Juergen Weigert:
On Nov 09, 09 19:02:36 +0100, Michael Schroeder wrote:
On Mon, Nov 09, 2009 at 06:58:28PM +0100, Pavol Rusnak wrote:
On 11/09/2009 06:41 PM, Michael Schroeder wrote:
'mock' is Fedora's version of our 'build' package. You don't need a build service account to use it.
I'd love to add this feature to obs!
We have it since a long time. Even before obs and it is an advantage IMHO that you do not need the complexity of the OBS infrastructure, if you don't need it's features.
No, we dont.
The scenario is this: I see a package in the build service, want to check out a copy, fix a bug, compile, test, ... and afterwards I want to send a patch, check in or submit.
We don't have THAT, afaik.
osc branch & osc sr ? yes, you need an account for that and we want this if you contribute.
if you just want to build offline, just use the offline tool. Where is the advantage to use the online tool to do the same job as the offline tool ?
What offline tool do you have in mind?
build Seriously, you all would cry if suddenly the speed of api.o.o would decrease a lot and plenty of timeout errors do appear on all kind of osc operations. And that for no good reason at all. -- Adrian Schroeter SUSE Linux Products GmbH email: adrian@suse.de -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Nov 09, 09 22:24:27 +0100, Adrian Schröter wrote:
I see a package in the build service, want to check out a copy, fix a bug, compile, test, ... and afterwards I want to send a patch, check in or submit.
We don't have THAT, afaik.
osc branch & osc sr ? yes, you need an account for that and we want this if you contribute.
That creates the branch on the server before working on it, and unless I prevent it manually, the server wastes cpu cycles trying to build half baken packages in my branched project.
if you just want to build offline, just use the offline tool. Where is the advantage to use the online tool to do the same job as the offline tool ?
What offline tool do you have in mind? build
Works for 'I see a package on my DVD' or on SUSE NFS server, but not for 'I see a package in the build service'. Not a useful community tool.
Seriously, you all would cry if suddenly the speed of api.o.o would decrease a lot and plenty of timeout errors do appear on all kind of osc operations. And that for no good reason at all.
This is true, but I don't see the connection. Why would building at client side decrease server speed? api.o.o does not even know that my package exists. cheers, JW- -- o \ Juergen Weigert paint it green! __/ _=======.=======_ <V> | jw@suse.de back to ascii! __/ _---|____________\/ \ | 0911 74053-508 __/ (____/ /\ (/) | _____________________________/ _/ \_ vim:set sw=2 wm=8 SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Am Montag, 9. November 2009 22:48:57 schrieb Juergen Weigert:
On Nov 09, 09 22:24:27 +0100, Adrian Schröter wrote:
I see a package in the build service, want to check out a copy, fix a bug, compile, test, ... and afterwards I want to send a patch, check in or submit.
We don't have THAT, afaik.
osc branch & osc sr ? yes, you need an account for that and we want this if you contribute.
That creates the branch on the server before working on it, and unless I prevent it manually, the server wastes cpu cycles trying to build half baken packages in my branched project.
... you mix different things. No one forces you to submit half backen things. But it would be even better if you don't use our resources at all, if you want an offline build.
if you just want to build offline, just use the offline tool. Where is the advantage to use the online tool to do the same job as the offline tool ?
What offline tool do you have in mind?
build
Works for 'I see a package on my DVD' or on SUSE NFS server, but not for 'I see a package in the build service'. Not a useful community tool.
either offline or community. The redhat tool is also offline only. If you don't want to use OBS, you can still submit via mail or bugzilla. But if you submit via OBS, the receiver shall see the build results before accepting.
Seriously, you all would cry if suddenly the speed of api.o.o would decrease a lot and plenty of timeout errors do appear on all kind of osc operations. And that for no good reason at all.
This is true, but I don't see the connection. Why would building at client side decrease server speed? api.o.o does not even know that my package exists.
because package download for the chroot may happen via api and creating the buildinfo can be quite expensive job (a lot IO on main server). bye adrian -- Adrian Schroeter SUSE Linux Products GmbH email: adrian@suse.de -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Mon, Nov 09, 2009 at 10:48:57PM +0100, Juergen Weigert wrote:
On Nov 09, 09 22:24:27 +0100, Adrian Schröter wrote:
build
Works for 'I see a package on my DVD' or on SUSE NFS server, but not for 'I see a package in the build service'. Not a useful community tool.
The original thread is *not* about the build service (but on the buildservice list for some unknown reason). If you want to start a new thread, use a different subject. Cheers, Michael. -- Michael Schroeder mls@suse.de SUSE LINUX Products GmbH, GF Markus Rex, HRB 16746 AG Nuernberg main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);} -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Why do we need two tools? Here're some questions and comments that come to my mind: * osc has already a local build option. * build and osc build both setup a local chroot * for documentation it's easier to describe only one tool and not two. * Do both share the same libraries and routines? Or do we reinvent the wheel everytime? * build uses the local media - why can't osc do the same * osc calculates the build dependencies on the server, build on the local machine. Why can't an osc local build do it on the local machine? I'm not getting yet why we need two tools. The build service has changed many ways we used to work - let's continue to thing out of the box, Andreas -- Andreas Jaeger, Program Manager openSUSE, aj@{novell.com,opensuse.org} Twitter: jaegerandi | Identica: jaegerandi SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Maxfeldstr. 5, 90409 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
On Tue, Nov 10, 2009 at 10:32:44AM +0100, Andreas Jaeger wrote:
* osc has already a local build option. * build and osc build both setup a local chroot
Huh? 'osc build' simply calls 'build' to do the real building. Cheers, Michael. -- Michael Schroeder mls@suse.de SUSE LINUX Products GmbH, GF Markus Rex, HRB 16746 AG Nuernberg main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);} -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Am Dienstag, 10. November 2009 10:32:44 schrieb Andreas Jaeger:
Why do we need two tools? Here're some questions and comments that come to my mind:
There no two tools. "build" is used for doing the actual building, can work standalone. "osc build" is doing all necessary interactions with the server (let him calculate dependencies and downloads needed packages) and calls the usual build script afterwards. no code overlap, just cleanly modularised.
* osc has already a local build option. * build and osc build both setup a local chroot * for documentation it's easier to describe only one tool and not two. * Do both share the same libraries and routines? Or do we reinvent the wheel everytime? * build uses the local media - why can't osc do the same * osc calculates the build dependencies on the server, build on the local machine. Why can't an osc local build do it on the local machine?
Because all packages from projects (or their meta data + project configs) would be needed on local workstation. seriously, this is a non-topic, we have a clean seperation and no code overlap. If someone is unhappy with the offline functionality, please enhance the build script. But so far no single reason was raised here what build isn't able to do when doing offline building. -- Adrian Schroeter SUSE Linux Products GmbH email: adrian@suse.de -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Tuesday 10 November 2009 10:48:23 Michael Schroeder wrote:
On Tue, Nov 10, 2009 at 10:32:44AM +0100, Andreas Jaeger wrote:
* osc has already a local build option. * build and osc build both setup a local chroot
Huh? 'osc build' simply calls 'build' to do the real building.
Ah, that was the missing link! Still, we speak so much about "osc" that I wonder whether we should enhance it so that people have one tool to do everything. Much easier documentation wise. Thanks, Andreas -- Andreas Jaeger, Program Manager openSUSE, aj@{novell.com,opensuse.org} Twitter: jaegerandi | Identica: jaegerandi SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Maxfeldstr. 5, 90409 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
participants (5)
-
Adrian Schröter -
Andreas Jaeger -
Juergen Weigert -
Michael Schroeder -
Pavol Rusnak